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:30] Narinder Gupta |
joid:b_userguide [2016/02/11 05:07] (current) Narinder Gupta [Access the openstack dashboard:] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | OPNFV Brahmaputra User Guide: | + | ====== OPNFV Brahmaputra User Guide: ====== |
- | Installation Guide | + | ===== Installation Guide ===== |
- | Post installation guide | ||
- | User Guide: | + | ===== Post installation guide ===== |
- | Access the openstack dashboard: | + | ===== User Guide: ===== |
- | open a browser http://<vip>/ for Intel pod5 http://10.4.1.21/ | + | ==== OPNFV requirements: ==== |
- | crendtials: admin/openstack | + | |
- | Command line: | + | * Installers shall support the deployment of OpenStack with High-Availability (for those components that support it in Liberty) on 3 or more control nodes. Functest tests should be able to verify that the HA is enabled and functional. |
- | source ./cloud/admin-openrc | + | * Hitless hardware upgrade: Increase size of a deployment in terms of compute nodes (add additional compute nodes) without service interruption. This requirement doesn't mandate upgrade/increasing the size of the control node cluster. |
- | openstack role list | + | * Automatically populate discovered servers into install tool (reduce user-intervention to a minimum). |
- | openstack user list | + | * Installers should support a common configuration file per platform/role, so that the installed OS can be customized for hardware and role. |
+ | * Neutron DHCP servers should be configured in HA per tenant. | ||
+ | * SDN Controller layer 3 forwarding support. | ||
+ | * Support layer 1/2 networking configuration. | ||
+ | * Support logical networks for target system. | ||
+ | * Support L3-neutron agent as an option for L3. | ||
+ | * Provide isolated compute node resources for CEPH OSD. | ||
+ | * Installers should track/control all versions of all components pulled from external sources (user should be able to identify the versions and origins of all software components deployed). | ||
+ | * Common ability to input site, topology, and server information. | ||
+ | * User-configurable parameters available via config files. | ||
+ | * Allow assignment of different roles to servers, so that hardware and software can be configured according to the role. | ||
+ | * Deployment tool to provide for automatic device discovery. | ||
+ | * Installers should configure NTP servers on the servers for clock synchronization. | ||
+ | * Installers to be agnostic to type of hard drives used. | ||
+ | * Installers should install ssh keys on servers so that key-based login can be used for administration. | ||
+ | * Ability to install with upstream artifacts. | ||
+ | * Installers should supply a script or set of scripts ("deploy.sh") | ||
+ | * 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). | ||
- | glance image-list | + | ==== 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. | ||
- | nova list | + | http://<vip>/ for Intel pod5 http://10.4.1.21/ |
+ | credentials: admin / openstack | ||
- | keystone tenanant-list | + | === Command line: === |
+ | |||
+ | * source ./cloud/admin-openrc | ||
+ | * openstack role list | ||
+ | * openstack user list | ||
+ | * glance image-list | ||
+ | * nova list | ||
+ | * keystone tenanant-list | ||
- | OPNFV requirements: | + | ==== 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. | ||
- | 1. | + | 1. MAAS deployment |
- | MAAS deployment | + | |
- | 1. MAAS deplyment | + | |
In case you are troubleshoot the deployment of 02-maasdeploy.sh then please look into logs during run time of any errors. Possible errors could be. | In case you are troubleshoot the deployment of 02-maasdeploy.sh then please look into logs during run time of any errors. Possible errors could be. | ||
a) Hardware does not support the virtualization. Please enable the virtualization in BIOS and rerun | a) Hardware does not support the virtualization. Please enable the virtualization in BIOS and rerun | ||
Line 57: | 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 | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||