From d871edc2c624dc78238fcdf7e7e397291e229453 Mon Sep 17 00:00:00 2001 From: Shilla Saebi Date: Tue, 4 Feb 2014 01:05:30 -0500 Subject: [PATCH] cleanup of ch_openstack_images removed: to name given to the instance changed sentence - additional to addition, (in addition) added key after public Change-Id: I5cb22fece1e868503bda35c4f1da1d43ea64c4ee --- doc/image-guide/ch_openstack_images.xml | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/doc/image-guide/ch_openstack_images.xml b/doc/image-guide/ch_openstack_images.xml index 51d9a39928..fb3d5c9a70 100644 --- a/doc/image-guide/ch_openstack_images.xml +++ b/doc/image-guide/ch_openstack_images.xml @@ -302,7 +302,7 @@ key If you are unable or unwilling to install cloud-init inside the guest, you can write a custom script to - fetch the public and add it to a user account. + fetch the public key and add it to a user account. To fetch the ssh public key and add it to the root account, edit the /etc/rc.local file and add the following lines before the line @@ -357,16 +357,15 @@ done
Process user data and other metadata (cloud-init) - In additional the ssh public key, an image may need to + In addition to the ssh public key, an image may need to retrieve additional information from OpenStack, such as user data that the user submitted when requesting the image. For example, you might want to set the - host name of the instance to name given to the instance - when it is booted. Or, you might wish to configure your - image so that it executes user data content as a script on - boot. + host name of the instance when it is booted. Or, you might + wish to configure your image so that it executes user data + content as a script on boot. This information is accessible through the metadata service or the