joid:b_installguide
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
joid:b_installguide [2016/01/20 06:26] Narinder Gupta |
joid:b_installguide [2016/02/10 21:49] (current) Narinder Gupta [Configure JOID for your lab] |
||
|---|---|---|---|
| Line 73: | Line 73: | ||
| ''git clone https://gerrit.opnfv.org/gerrit/p/joid.git'' | ''git clone https://gerrit.opnfv.org/gerrit/p/joid.git'' | ||
| + | |||
| + | or | ||
| + | |||
| + | ''git clone -b stable/brahmaputra https://gerrit.opnfv.org/gerrit/p/joid.git'' | ||
| ''cd joid/ci'' | ''cd joid/ci'' | ||
| Line 78: | Line 82: | ||
| === Enable MAAS === | === Enable MAAS === | ||
| + | If you have already enabled maas for your environment and installed it then there is no need to enabled it again or install it. If you have patches from previous MAAS enablement then you can apply it here. | ||
| + | |||
| + | NOTE: If MAAS is pre installed without 02-maasdeploy.sh then please do the following and skip rest of the step to enable MAAS. | ||
| + | 1. Assigned tag "compute" to at least two compute nodes server. | ||
| + | 2. Assgined tag "control" to at least three control nodes server. | ||
| + | 3. copy MAAS API key and paste in ~/.juju/environments.yaml at appropriate place. | ||
| + | 4. Run command cp ~/.juju/environments.yaml ./joid/ci/ | ||
| + | | ||
| + | If enabling first time then follow it further. | ||
| + | |||
| * Create a directory in maas/<company name>/<pod number>/ for example | * Create a directory in maas/<company name>/<pod number>/ for example | ||
| ''mkdir maas/intel/pod7/'' | ''mkdir maas/intel/pod7/'' | ||
| Line 87: | Line 101: | ||
| deployment.yaml environments.yaml interfaces.host lxc-add-more-interfaces | deployment.yaml environments.yaml interfaces.host lxc-add-more-interfaces | ||
| + | | ||
| ==== deployment.yaml file ==== | ==== deployment.yaml file ==== | ||
| Line 109: | Line 124: | ||
| sed -i -- 's/# "ext-port": "eth1"/ "ext-port": "eth1"/g' ./bundles.yaml | sed -i -- 's/# "ext-port": "eth1"/ "ext-port": "eth1"/g' ./bundles.yaml | ||
| ;; | ;; | ||
| + | |||
| + | NOTE: If you are using seprate data network then add this line below also along with other changes. which represents network 10.4.9.0/24 will be used for data network for openstack | ||
| + | |||
| + | sed -i -- 's/#os-data-network: 10.4.8.0\/21/os-data-network: 10.4.9.0\/24/g' ./bundles.yaml | ||
| === modify joid/ci/02-maasdeploy.sh === | === modify joid/ci/02-maasdeploy.sh === | ||
| Line 119: | Line 138: | ||
| NOTE: If you are using VLAN tags or more network for data and storage then make sure you modify the case $1 section under Enable vlan interface with maas appropriately. In the example below eth2 has been used as separate data network for tenants in openstack with network 10.4.9.0/24 on compute and control nodes. | NOTE: If you are using VLAN tags or more network for data and storage then make sure you modify the case $1 section under Enable vlan interface with maas appropriately. In the example below eth2 has been used as separate data network for tenants in openstack with network 10.4.9.0/24 on compute and control nodes. | ||
| - | 'intelpod6' ) | + | 'intelpod7' ) |
| maas refresh | maas refresh | ||
| enableautomodebyname eth2 AUTO "10.4.9.0/24" compute || true | enableautomodebyname eth2 AUTO "10.4.9.0/24" compute || true | ||
| enableautomodebyname eth2 AUTO "10.4.9.0/24" control || true | enableautomodebyname eth2 AUTO "10.4.9.0/24" control || true | ||
| ;; | ;; | ||
| + | |||
| + | |||
| + | ==== Deployment of OPNFV using JOID: ==== | ||
| + | Once you have done the change in above section then run the following commands to do the automatic deployments. | ||
| + | === MAAS Install === | ||
| + | |||
| + | After integrating the changes as mentioned above run the MAAS install. Suppose you name the integration lab as intelpod7 then run the below commands to start the MAAS deployment. | ||
| + | |||
| + | ./02-maasdeploy.sh intelpod7 | ||
| + | |||
| + | === OPNFV Install === | ||
| + | |||
| + | ./deploy.sh -o liberty -s odl -t ha -l intelpod7 -f none | ||
| + | | ||
| + | NOTE: Possible options are as follows: | ||
| + | choose which sdn controller to use. | ||
| + | [-s <nosdn|odl|opencontrail|onos>] | ||
| + | nosdn: openvswitch only and no other SDN. | ||
| + | odl: OpenDayLight Lithium version. | ||
| + | opencontrail: OpenContrail SDN can be installed with Juno Openstack today. | ||
| + | onos: ONOS framework as SDN. | ||
| + | | ||
| + | [-t <nonha|ha|tip>] | ||
| + | nonha: NO HA mode of Openstack | ||
| + | ha: HA mode of openstack. | ||
| + | [-o <juno|liberty>] | ||
| + | juno: Juno Openstack | ||
| + | liberty: Liberty version of openstack. | ||
| + | [-l <default|intelpod5>] etc... | ||
| + | default: For virtual deployment where installation will be done on KVM created using ./02-maasdeploy.sh | ||
| + | intelpod5: Install on bare metal OPNFV pod5 of Intel lab. | ||
| + | intelpod6 | ||
| + | orangepod2 | ||
| + | .. | ||
| + | .. | ||
| + | <your pod>: if you make changes as per your pod above then please use that. | ||
| + | [-f <ipv6|none>] | ||
| + | none: no special feature will be enabled. | ||
| + | ipv6: ipv6 will be enabled for tenant in openstack. | ||
| + | | ||
| + | ==== Troubleshoot ==== | ||
| + | By default debug is enabled in script and error messages will be printed on ssh terminal where you are running the scripts. | ||
| + | |||
| + | To access of any control or compute nodes. | ||
| + | juju ssh <service name> | ||
| + | for example to login into openstack-dashboard container. | ||
| + | juju ssh openstack-dashboard/0 | ||
| + | juju ssh nova-compute/0 | ||
| + | juju ssh neutron-gateway/0 | ||
| + | |||
| + | By default juju will add the Ubuntu user keys for authentication into the deployed server and only ssh access will be available. | ||
| + | |||
| + | |||
| + | |||
joid/b_installguide.1453271183.txt.gz ยท Last modified: 2016/01/20 06:26 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
