openstack/freezer
Code Issues Proposed changes

Change "Openstack" to "OpenStack"

Browse Source 
According to the word choice convention in
http://docs.openstack.org/contributor-guide/writing-style/word-choice.html
We should use OpenStack instead of Openstack.

Change-Id: I834055528e6f343c113c96a70a7a2f265a0a1703
This commit is contained in:
liyanhang 2016-10-25 23:38:29 +08:00 committed by Jeremy Liu
parent 42f1517b56
commit e254dfae00
4 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.rst
View File

@ -728,7 +728,7 @@ related to the storage
Example: ssh-username, ssh-port Example: ssh-username, ssh-port
For swift storage you should provide additional parameter called 'osrc' For swift storage you should provide additional parameter called 'osrc'
Osrc should be a path to file with Openstack Credentials like:: Osrc should be a path to file with OpenStack Credentials like::
unset OS_DOMAIN_NAME unset OS_DOMAIN_NAME
export OS_AUTH_URL=http://url:5000/v3 export OS_AUTH_URL=http://url:5000/v3
@ -1087,7 +1087,7 @@ optional arguments:
--noverbose The inverse of --verbose --noverbose The inverse of --verbose
--nowatch-log-file The inverse of --watch-log-file --nowatch-log-file The inverse of --watch-log-file
--os-identity-api-version OS_IDENTITY_API_VERSION, --os_auth_ver OS_IDENTITY_API_VERSION --os-identity-api-version OS_IDENTITY_API_VERSION, --os_auth_ver OS_IDENTITY_API_VERSION
Openstack identity api version, can be 1, 2, 2.0 or 3 OpenStack identity api version, can be 1, 2, 2.0 or 3
--overwrite With overwrite removes files from restore path before --overwrite With overwrite removes files from restore path before
restore. restore.
--path-to-backup PATH_TO_BACKUP, -F PATH_TO_BACKUP --path-to-backup PATH_TO_BACKUP, -F PATH_TO_BACKUP

4
doc/source/user/freezer-agent.rst
View File

@ -422,7 +422,7 @@ Example:
ssh-username, ssh-port ssh-username, ssh-port
For swift storage you should provide additional parameter called 'osrc' Osrc For swift storage you should provide additional parameter called 'osrc' Osrc
should be a path to file with Openstack Credentials like: should be a path to file with OpenStack Credentials like:
.. code:: bash .. code:: bash
@ -795,7 +795,7 @@ Optional Arguments
--noverbose The inverse of --verbose --noverbose The inverse of --verbose
--nowatch-log-file The inverse of --watch-log-file --nowatch-log-file The inverse of --watch-log-file
--os-identity-api-version OS_IDENTITY_API_VERSION, --os_auth_ver OS_IDENTITY_API_VERSION --os-identity-api-version OS_IDENTITY_API_VERSION, --os_auth_ver OS_IDENTITY_API_VERSION
Openstack identity api version, can be 1, 2, 2.0 or 3 OpenStack identity api version, can be 1, 2, 2.0 or 3
--overwrite With overwrite removes files from restore path before --overwrite With overwrite removes files from restore path before
restore. restore.
--path-to-backup PATH_TO_BACKUP, -F PATH_TO_BACKUP --path-to-backup PATH_TO_BACKUP, -F PATH_TO_BACKUP

2
specs/python-freezerclient.rst
View File

@ -13,7 +13,7 @@ Include the URL of your launchpad blueprint:
* https://blueprints.launchpad.net/freezer/+spec/freezerclient * https://blueprints.launchpad.net/freezer/+spec/freezerclient
Freezer needs to align to the other Openstack projects and have a dedicated Freezer needs to align to the other OpenStack projects and have a dedicated
repo/client to communicate with the API and the storage media. repo/client to communicate with the API and the storage media.
Problem description Problem description

2
specs/tenant_based_backups.rst
View File

@ -128,7 +128,7 @@ Possible options:
- We can add an additional option called data_input_type, setting the default to fs (file system) or stream and use tenant as backup mode - We can add an additional option called data_input_type, setting the default to fs (file system) or stream and use tenant as backup mode
- When restoring, would probably good to recreate the tenant resources with a tenant name provided by the user (i.e. provided by Openstack environment variable like the OS_TENANT_NAME var). This has the advantage to recreate the resources with a different tenant in case is needed. - When restoring, would probably good to recreate the tenant resources with a tenant name provided by the user (i.e. provided by OpenStack environment variable like the OS_TENANT_NAME var). This has the advantage to recreate the resources with a different tenant in case is needed.
- Does the Cinder volumes needs to be attached to the VMs, in case they were when the backup was taken? - Does the Cinder volumes needs to be attached to the VMs, in case they were when the backup was taken?