From a95ef23b595b51f9da95352e221af7a3e658542a Mon Sep 17 00:00:00 2001 From: darrenchan Date: Wed, 28 Jan 2015 16:28:12 +1100 Subject: [PATCH] Fixed minor typo in the training guide Fixed minor typographical error and broken links. Change-Id: I74a1aec3fa9c7964bbb9114d997fa9386b86db31 backport: none Closes-Bug: #1414969 --- .../common/section_overview-horizon-cli.xml | 29 +++++++++---------- 1 file changed, 14 insertions(+), 15 deletions(-) diff --git a/doc/training-guides/common/section_overview-horizon-cli.xml b/doc/training-guides/common/section_overview-horizon-cli.xml index 4d883539..52c10917 100644 --- a/doc/training-guides/common/section_overview-horizon-cli.xml +++ b/doc/training-guides/common/section_overview-horizon-cli.xml @@ -157,13 +157,13 @@ group rules to enable users to ping and SSH to the instances. To do so, you either add rules to the default security group or add a security group with rules. For information, seethe section called “Add security group rules”. + xlink:href="http://docs.openstack.org/user-guide/content/sdk_configure_instances.html" + >the section called “Create and manage security group rules”. Keypairs are SSH credentials that are injected into images when they are launched. For this to work, the image must contain the cloud-init package. For information, seethe section called “Add keypairs”. + xlink:href="http://docs.openstack.org/user-guide/content/sdk_configure_instances.html" + >the section called “Add a keypair”. Add security group rules The following procedure shows you how to add rules to the default security group. @@ -339,8 +339,8 @@ $ chmod 0600 MY_PRIV_KEY.pem - Use the ssh-addcommand to make the keypair known to - SSH: + Use the ssh-add command to make the + keypair known to SSH: $ ssh-add MY_PRIV_KEY.pem @@ -414,9 +414,8 @@ Security groups are a kind of cloud firewall that define which incoming network traffic should be forwarded to instances. For details, seethe section called “Add security group - rules”. + xlink:href="http://docs.openstack.org/user-guide/content/sdk_configure_instances.html" + >the section called “Create and manage security groups”. If you have not created any specific security groups, @@ -1409,18 +1408,18 @@ arguments that you used to create the rule. - To delete the security rule that you created inStep 3.a: + To delete the security rule that you added as described inCreate and manage security group rules: $ nova secgroup-delete-rule SEC_GROUP_NAME tcp 22 22 0.0.0.0/0 - To delete the security rule that you created inStep 3.b: + To delete the security group that you created as described inCreate and manage security groups: $ nova secgroup-delete-group-rule --ip_proto tcp