This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
joid:b_userguide [2016/02/11 04:56] Narinder Gupta |
joid:b_userguide [2016/02/11 05:07] (current) Narinder Gupta [Access the openstack dashboard:] |
||
|---|---|---|---|
| Line 32: | Line 32: | ||
| * Installers should support offline deployment. Jump host may have Internet access, but the installers should support offline installation on target hosts during the deployment phase (either manually or automatically). | * Installers should support offline deployment. Jump host may have Internet access, but the installers should support offline installation on target hosts during the deployment phase (either manually or automatically). | ||
| - | Access the openstack dashboard: | + | ==== Access the openstack dashboard: ==== |
| + | Users can access the dashboard from the jumpshot directly. If you are working on jumpshot then please open a web browser on the jumpshot and start accessing the openstack dashboard. | ||
| - | open a browser http://<vip>/ for Intel pod5 http://10.4.1.21/ | + | http://<vip>/ for Intel pod5 http://10.4.1.21/ |
| - | crendtials: admin/openstack | + | credentials: admin / openstack |
| - | Command line: | + | === Command line: === |
| + | |||
| * source ./cloud/admin-openrc | * source ./cloud/admin-openrc | ||
| * openstack role list | * openstack role list | ||
| Line 46: | Line 48: | ||
| ==== Troubleshooting: ==== | ==== Troubleshooting: ==== | ||
| + | |||
| JOID is combination of MAAS and JUJU tools which do the OPNFV deployment on bare metal as well as on virtual machine. | JOID is combination of MAAS and JUJU tools which do the OPNFV deployment on bare metal as well as on virtual machine. | ||
| Line 73: | Line 76: | ||
| MAAS API key has been listed. | MAAS API key has been listed. | ||
| c) deployment stuck at long time and timeout: | c) deployment stuck at long time and timeout: | ||
| + | use command juju status --format=tabular and make sure all services container got an ip and they are executing some code. There is no service in the error state. | ||
| + | | ||
| 3. Openstack deployment | 3. Openstack deployment | ||
| - | |||