Differences

This shows you the differences between two versions of the page.

--- joid:b_installguide [2016/01/20 06:10]
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''
+or
+''git clone -b stable/brahmaputra https://gerrit.opnfv.org/gerrit/p/joid.git''
 ''cd joid/ci''
@@ Line 78: / Line 82: @@
 ===   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.
+. Assigned tag "compute" to at least two compute nodes server.
+. Assgined tag "control" to at least three control nodes server.
+. copy MAAS API key and paste in ~/.juju/environments.yaml at appropriate place.
+. 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
  ''mkdir maas/intel/pod7/''
@@ Line 87: / Line 101: @@
 deployment.yaml  environments.yaml  interfaces.host  lxc-add-more-interfaces
 ==== deployment.yaml file ====
@@ Line 95: / Line 110: @@
-==== modify ====
+==== modify deployment.yaml ====
 This file has been used to configure your maas and bootstrap node in a VM. Comments in the file are self explanatory and we expect fill up the information according to match lab infrastructure information. Sample deployment.yaml can be found at [[https://gerrit.opnfv.org/gerrit/gitweb?p=joid.git;a=blob;f=ci/maas/intel/pod5/deployment.yaml]]
+=== modify joid/ci/01-deploybundle.sh ===
+under section case $3 add the intelpod7 section and make sure you have information provided correctly.
+Before example consider your network has 192.168.1.0/24 your default network. and eth1 is on public network which will be used to assign the floating ip.
+     'intelpod7' )
+        # As per your lab vip address list be deafult uses 10.4.1.11 - 10.4.1.20
+         sed -i -- 's/10.4.1.1/192.168.1.2/g' ./bundles.yaml
+        # Choose the external port to go out from gateway to use.
+         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 ===
+under section case $1 add the intelpod7 section and make sure you have information provided correctly.
+      'intelpod7' )
+        cp maas/intel/pod7/deployment.yaml ./deployment.yaml
+        ;;
+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.
+    'intelpod7' )
+        maas refresh
+        enableautomodebyname eth2 AUTO "10.4.9.0/24" compute || 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.

Wiki

User Tools

Site Tools

Differences

Page Tools