joid:b_userguide
Differences
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:52] 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 ===== |
| - | ===== | + | |
| - | ==== OPNFV requirements: | + | ===== User Guide: ===== |
| - | ==== | + | |
| + | ==== OPNFV requirements: ==== | ||
| * 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. | * 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. | ||
| - | * | ||
| * 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. | * 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. | ||
| - | * | ||
| * Automatically populate discovered servers into install tool (reduce user-intervention to a minimum). | * Automatically populate discovered servers into install tool (reduce user-intervention to a minimum). | ||
| - | * | ||
| * Installers should support a common configuration file per platform/role, so that the installed OS can be customized for hardware and role. | * 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. | * Neutron DHCP servers should be configured in HA per tenant. | ||
| - | * | ||
| * SDN Controller layer 3 forwarding support. | * SDN Controller layer 3 forwarding support. | ||
| - | * | ||
| * Support layer 1/2 networking configuration. | * Support layer 1/2 networking configuration. | ||
| - | * | ||
| * Support logical networks for target system. | * Support logical networks for target system. | ||
| - | * | ||
| * Support L3-neutron agent as an option for L3. | * Support L3-neutron agent as an option for L3. | ||
| - | * | ||
| * Provide isolated compute node resources for CEPH OSD. | * 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). | * 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. | * Common ability to input site, topology, and server information. | ||
| - | * | ||
| * User-configurable parameters available via config files. | * 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. | * 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. | * Deployment tool to provide for automatic device discovery. | ||
| - | * | ||
| * Installers should configure NTP servers on the servers for clock synchronization. | * Installers should configure NTP servers on the servers for clock synchronization. | ||
| - | * | ||
| * Installers to be agnostic to type of hard drives used. | * 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. | * Installers should install ssh keys on servers so that key-based login can be used for administration. | ||
| - | * | ||
| * Ability to install with upstream artifacts. | * Ability to install with upstream artifacts. | ||
| - | * | ||
| * Installers should supply a script or set of scripts ("deploy.sh") | * 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). | * 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 | + | |
| - | openstack role list | + | * source ./cloud/admin-openrc |
| - | openstack user list | + | * openstack role list |
| + | * openstack user list | ||
| + | * glance image-list | ||
| + | * nova list | ||
| + | * keystone tenanant-list | ||
| - | glance image-list | + | ==== Troubleshooting: ==== |
| - | nova list | ||
| - | |||
| - | keystone tenanant-list | ||
| - | |||
| - | |||
| - | |||
| - | 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 102: | 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 | ||
| - | |||
| - | |||
| - | |||
| - | |||
joid/b_userguide.1455166368.txt.gz · Last modified: 2016/02/11 04:52 by Narinder Gupta
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
