This is an old revision of the document!
Please follow HOW TO here: https://wiki.opnfv.org/wiki/jenkins#how_to_connect_servers_from_labs_to_opnfv_jenkins
The jumphost must be a flavor of Ubuntu The following things must be set on the jumphost before starting any deploy:
git
bridge-utils
vlan
brAdm
brData
brStorage
All those pre-requisits can be managed bu Master MAAS.
Now you can launch jenkins
Jenkins fixes those parameters:
SDN_CONTROLLER=nosdn HA_MODE=ha OS_RELEASE=liberty OPNFV_FEATURE=none
None today, but CEPH options may be set here.
The cleanup is done at each deploy in the script
The pod admin can set a few parameters
sudo -s jenkins mkdir ~/joid_config cat << EOF > ~/joid_config/config.sh ### Set Pod name export POD_DC=orange export POD_NUM=pod2 # This must be the same name as the one configured in joid deployment files export POD_NAME=\$POD_DC\$POD_NUM ### Reinstall MAAS at each jenkins deploy export MAAS_REINSTALL=true ### Set passwords export MAAS_USER=ubuntu export MAAS_PASSWORD=ubuntu export OS_ADMIN_PASSWORD=openstack ### Set CEPH parameters # disks to use by ceph (comma separated list) export CEPH_DISKS=/dev/sdb,/dev/sdc # format or not disk before using ceph (must be done the first time) export CEPH_REFORMAT=false EOF
Testing MAAS deploy is not the core of CI tests, so to gain time, MAAS reinstall can be disabled by setting local parameter MAAS_REINSTALL=false. Juju will be cleaned and all nodes managed will return in ready mode.