Change in Configure access security for instances

Updated key description

Change-Id: Ia6f59f663bffa79d9c6b14bbf5b23d0d04dcd148
Closes-Bug:#1506985
This commit is contained in:
syed ahsan shamim zaidi 2015-10-23 08:44:11 +00:00
parent 0a19ec6d09
commit f7d3e19d75
2 changed files with 10 additions and 0 deletions

View File

@ -10,6 +10,11 @@ You can create at least one key pair for each project. You can use the key
pair for multiple instances that belong to that project. If you generate pair for multiple instances that belong to that project. If you generate
a key pair with an external tool, you can import it into OpenStack. a key pair with an external tool, you can import it into OpenStack.
.. note::
A key pair belongs to an individual user, not to a project.
To share a key pair across multiple users, each user
needs to import that key pair.
If an image uses a static root password or a static key set (neither is If an image uses a static root password or a static key set (neither is
recommended), you must not provide a key pair when you launch the recommended), you must not provide a key pair when you launch the
instance. instance.

View File

@ -20,6 +20,11 @@ it into OpenStack. The key pair can be used for multiple instances that
belong to a project. For more information, see the section belong to a project. For more information, see the section
:ref:`dashboard_import_keypair`. :ref:`dashboard_import_keypair`.
.. note::
A key pair belongs to an individual user, not to a project.
To share a key pair across multiple users, each user
needs to import that key pair.
When an instance is created in OpenStack, it is automatically assigned a When an instance is created in OpenStack, it is automatically assigned a
fixed IP address in the network to which the instance is assigned. This fixed IP address in the network to which the instance is assigned. This
IP address is permanently associated with the instance until the IP address is permanently associated with the instance until the