User Tools

Site Tools


joid:get_started

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
joid:get_started [2016/01/08 23:07]
Iben Rodriguez
joid:get_started [2016/01/13 18:00] (current)
Iben Rodriguez adding jenkins job naming convention
Line 21: Line 21:
   * Setup create JJB Jenkins Job Builder Script for your pod in your lab   * Setup create JJB Jenkins Job Builder Script for your pod in your lab
   * Test and iterate JJB script to deploy MaaS and Juju VMs on Jumphost to complete JOID Setup   * Test and iterate JJB script to deploy MaaS and Juju VMs on Jumphost to complete JOID Setup
 +
 +==== Jenkins Job Naming Convention ==== 
 +
 + - Based on scenario naming we can get joid options naming convention:
 +     ​os-<​controller>​-<​nfvfeature>​-<​mode>​[-<​extrastuff>​]
 + - With parameters:
 +     ​controller=(nosdn|odl_l3|odl_l2|onos|ocl)
 +        No odl_l3 today
 +     ​nfvfeature=(kvm|ovs|dpdk|nofeature)
 +        '​_'​ list separated.
 +     ​mode=(ha|noha)
 +     ​extrastuff=(none)
 +        Optional field - Not used today
 + 
 +Actual scenario list:
 +
 +  - '​os-nosdn-nofeature-noha':​
 +    - auto-trigger-name:​ '​brahmaputra-trigger-daily-disabled'​
 +  - '​os-nosdn-nofeature-ha':​
 +    - auto-trigger-name:​ '​brahmaputra-trigger-daily-disabled'​
 +  - '​os-odl_l2-nofeature-ha':​
 +    - auto-trigger-name:​ '​joid-{scenario}-{pod}-trigger'​
 +  - '​os-odl_l2-nofeature-noha':​
 +    - auto-trigger-name:​ '​brahmaputra-trigger-daily-disabled'​
 +  - '​os-onos-nofeature-ha':​
 +    - auto-trigger-name:​ '​brahmaputra-trigger-daily-disabled'​
 +  - '​os-onos-nofeature-noha':​
 +    - auto-trigger-name:​ '​brahmaputra-trigger-daily-disabled'​
 +
  
 =====   ​Enable MAAS ===== =====   ​Enable MAAS =====
Line 77: Line 106:
 This section will guide you how to configure joid to your environment to deploy OPNFV platform. This section will guide you how to configure joid to your environment to deploy OPNFV platform.
   * Make sure you have environments.yaml in ~/joid/ci directory. If it does not exist then most likely you have not used the above method to deploy MAAS. In that case please copy the file manually.   * Make sure you have environments.yaml in ~/joid/ci directory. If it does not exist then most likely you have not used the above method to deploy MAAS. In that case please copy the file manually.
-  * make sure all changes ​in bundle file ./​odl/​juju-deployer/​ovs-odl-ha.yaml ​has the correct information. If no then i would request you to modify the ~/​joid/​ci/​01-deploybundle.sh ​file to modify for your lab. +  * verify the info in all 3x4 = 12 yaml configuration files (for example): 
-  * make sure there to modify the 01-deploymentbundle.sh file for each environment +  * ~/joid/ci/​odl/​juju-deployer/​ovs-odl-ha.yaml 
-  * For Example: ​ vi ci/nosdn/​01-deploybundle.sh +  * modify the deploy bundle shell script for each of the 4 network controllers to add your lab: 
 +  * ~/joid/ci/nosdn/​01-deploybundle.sh 
 +  * ~/​joid/​ci/​odl/​01-deploybundle.sh 
 +  * ~/joid/ci/onos/​01-deploybundle.sh 
 +  * ~/​joid/​ci/​opencontrail/​01-deploybundle.sh
  
   '' ​   '' ​
Line 96: Line 128:
   ''​   ''​
 ===== Run the deployment using JOID ===== ===== Run the deployment using JOID =====
 +When the machines in the lab are ready to be powered on and booted we can continue.
 +
 Once you have modified the above sections then deployment will be very easy. Please do the following: Once you have modified the above sections then deployment will be very easy. Please do the following:
  
joid/get_started.1452294478.txt.gz · Last modified: 2016/01/08 23:07 by Iben Rodriguez