diff options
Diffstat (limited to 'docs/installation-instructions/verification.rst')
| -rw-r--r-- | docs/installation-instructions/verification.rst | 70 |
1 files changed, 40 insertions, 30 deletions
diff --git a/docs/installation-instructions/verification.rst b/docs/installation-instructions/verification.rst index 0ff56322..81e4c8e4 100644 --- a/docs/installation-instructions/verification.rst +++ b/docs/installation-instructions/verification.rst @@ -1,40 +1,43 @@ Verifying the Setup ------------------- -Once the deployment has finished, the OPNFV deployment can be accessed via the Undercloud node. From -the jump host ssh to the Undercloud host and become the stack user. Alternativly ssh keys have been -setup such that the root user on the jump host can ssh to Undercloud directly as the stack user. For -convenience a utility script has been provided to look up the undercloud's ip address and ssh to the -undercloud all in one command. An optional user name can be passed to indicate whether to connect as -the stack or root user. The stack user is default if a username is not specified. +Once the deployment has finished, the OPNFV deployment can be accessed via the +undercloud node. From the jump host ssh to the undercloud host and become the +stack user. Alternativly ssh keys have been setup such that the root user on +the jump host can ssh to undercloud directly as the stack user. For +convenience a utility script has been provided to look up the undercloud's ip +address and ssh to the undercloud all in one command. An optional user name can +be passed to indicate whether to connect as the stack or root user. The stack +user is default if a username is not specified. | ``opnfv-util undercloud root`` | ``su - stack`` -Once connected to Undercloud as the stack user look for two keystone files that can be used to -interact with the undercloud and the overcloud. Source the appropriate RC file to interact with -the respective OpenStack deployment. +Once connected to undercloud as the stack user look for two keystone files that +can be used to interact with the undercloud and the overcloud. Source the +appropriate RC file to interact with the respective OpenStack deployment. -| ``source stackrc`` (Undercloud) -| ``source overcloudrc`` (Overcloud / OPNFV) +| ``source stackrc`` (undercloud) +| ``source overcloudrc`` (overcloud / OPNFV) -The contents of these files include the credentials for the administrative user for Undercloud and -OPNFV respectivly. At this point both Undercloud and OPNFV can be interacted with just as any -OpenStack installation can be. Start by listing the nodes in the undercloud that were used -to deploy the overcloud. +The contents of these files include the credentials for the administrative user +for undercloud and OPNFV respectivly. At this point both undercloud and OPNFV +can be interacted with just as any OpenStack installation can be. Start by +listing the nodes in the undercloud that were used to deploy the overcloud. | ``source stackrc`` | ``openstack server list`` -The control and compute nodes will be listed in the output of this server list command. The IP -addresses that are listed are the control plane addresses that were used to provision the nodes. -Use these IP addresses to connect to these nodes. Initial authentication requires using the -user heat-admin. +The control and compute nodes will be listed in the output of this server list +command. The IP addresses that are listed are the control plane addresses that +were used to provision the nodes. Use these IP addresses to connect to these +nodes. Initial authentication requires using the user heat-admin. | ``ssh heat-admin@192.0.2.7`` -To begin creating users, images, networks, servers, etc in OPNFV source the overcloudrc file or -retrieve the admin user's credentials from the overcloudrc file and connect to the web Dashboard. +To begin creating users, images, networks, servers, etc in OPNFV source the +overcloudrc file or retrieve the admin user's credentials from the overcloudrc +file and connect to the web Dashboard. You are now able to follow the `OpenStack Verification`_ section. @@ -42,7 +45,8 @@ You are now able to follow the `OpenStack Verification`_ section. OpenStack Verification ---------------------- -Once connected to the OPNFV Dashboard make sure the OPNFV target system is working correctly: +Once connected to the OPNFV Dashboard make sure the OPNFV target system is +working correctly: 1. In the left pane, click Compute -> Images, click Create Image. @@ -55,25 +59,31 @@ Once connected to the OPNFV Dashboard make sure the OPNFV target system is worki 5. Enter a name "internal", click Next. -6. Enter a subnet name "internal_subnet", and enter Network Address ``172.16.1.0/24``, click Next. +6. Enter a subnet name "internal_subnet", and enter Network Address + ``172.16.1.0/24``, click Next. 7. Now go to Project -> Compute -> Instances, click Launch Instance. -8. Enter Instance Name "first_instance", select Instance Boot Source "Boot from image", - and then select Image Name "cirros". +8. Enter Instance Name "first_instance", select Instance Boot Source + "Boot from image", and then select Image Name "cirros". -9. Click Launch, status will cycle though a couple states before becoming "Active". +9. Click Launch, status will cycle though a couple states before becoming + "Active". 10. Steps 7 though 9 can be repeated to launch more instances. -11. Once an instance becomes "Active" their IP addresses will display on the Instances page. +11. Once an instance becomes "Active" their IP addresses will display on the + Instances page. -12. Click the name of an instance, then the "Console" tab and login as "cirros"/"cubswin:)" +12. Click the name of an instance, then the "Console" tab and login as + "cirros"/"cubswin:)" -13. To verify storage is working, click Project -> Compute -> Volumes, Create Volume +13. To verify storage is working, + click Project -> Compute -> Volumes, Create Volume 14. Give the volume a name and a size of 1 GB -15. Once the volume becomes "Available" click the dropdown arrow and attach it to an instance. +15. Once the volume becomes "Available" click the dropdown arrow and attach it + to an instance. Congratulations you have successfully installed OPNFV! |