User Tools

Site Tools


joid:ci_integration

This is an old revision of the document!


Propositions for Joid integration in CI

Prerequisites

Jump host preparation

The jumphost must be a flavor of Ubuntu The following things must be set on the jumphost before starting any deploy:

  • One extra repo (repository ppa:juju/stable)
  • applications must be installed
    • libvirt-bin
    • git
    • iptables-persistent
    • bridge-utils
    • vlan
  • The network must also be set to host 3 bridges (TO BE DISCUSSED)
    • brAdm
    • brData
    • brStorage

Pod parameters

The pod admin must also set a few parameters

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=yes

### 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

No you can launch jenkins

Details of jenkins job

Jenkins parameters

Now install parameters are hard coded in the install script, this will be set by jenkins soon:

JOID_MODE=ha JOID_RELEASE=liberty JOID_SDN_CONTROLLER=odl

Cleanup steps

The cleanup is done at each depploy in the script

joid/ci_integration.1450372879.txt.gz · Last modified: 2015/12/17 17:21 by David Blaisonneau