Sahara/SaharaCI

Warning: the page contains outdated information. The Sahara CI previously provided by Mirantis is now (since Pike) disabled and the structure and naming of the jobs evolved.

Sahara CI

Sahara CI infrastructure

Sahara CI contains Jenkins, Zuul, Nodepool and server with Devstack, where running Jenkins slaves. Jenkins is controlled for the most part by Zuul which determines what jobs are run when. Nodepool deploys and manages a pool of slaves images on a Devstack server for use in Jenkins jobs.

Jenkins is available by address: https://sahara.mirantis.com/jenkins
Zuul status is available by address: https://sahara.mirantis.com/zuul
Auth using launchpad.net SSO.

For installing Sahara CI use Puppet scripts, which are placed in repo: https://github.com/savanna-project/savanna-ci/tree/master/config/deploy-ci
During installation you must specify some parameters for Jenkins, Zuul and Nodepool (see: https://github.com/savanna-project/savanna-ci/blob/master/config/deploy-ci/README.rst). After that will be run Puppet scripts, which install Jenkins, Zuul and Nodepool.

Sahara CI configuration

All configuration files and scripts are placed in repo: http://github.com/stackforge/sahara-ci-config

For configuring Jenkins jobs uses Jenkins Job Builder system with YAML files. Jobs should be created and reconfigured through Jenkins Job Builder to avoid conflicts and unexpected changes. JJB is installed in virtual environment on Sahara Jenkins server.

For Zuul and Nodepool use settings, which configured to VM with Devstack.

Zuul triggers

Sahara CI supports stable/juno and master branches. Zuul triggers jobs on patch sets to the next repos:
- http://github.com/openstack/sahara
- http://github.com/openstack/sahara-dashboard
- http://github.com/openstack/python-saharaclient
- http://github.com/openstack/sahara-image-elements

For openstack/sahara and openstack/python-saharaclient repos will be triggered jobs with integration tests for all Sahara plugins. Each job named based on network provider, Sahara infrastructure engine, plugin name, run mode and scenario test:
gate-project-network-plugin[-aio][-scenario]
Basically Sahara runs in distributed mode, but if suffix 'aio' is specified, then Sahara runs in all in one mode. Scenario tests are enabled only for master branch now.

Sahara Dashboard is integrated into Horizon now. So, for openstack/horizon repo will be triggered job:
- gate-ui-tests
For openstack/sahara-dashboard repo will be triggered job with UI tests:
- gate-uitests-tests
Sahara UI tests are disabled now.

For openstack/sahara-image-elements repo will be triggered jobs, which build image using disk-image-builder for each Sahara plugin at first and then run integration tests:
- dib-nova-direct-hdp_1-aio
- dib-nova-heat-hdp_2
- dib-nova-direct-spark-aio
- dib-nova-direct-spark-aio-scenario
- dib-neutron-direct-vanilla_1-centos-aio
- dib-neutron-direct-vanilla_1-fedora-aio
- dib-neutron-direct-vanilla_1-ubuntu-aio
- dib-neutron-heat-vanilla_2.4-centos
- dib-neutron-heat-vanilla_2.4-fedora
- dib-neutron-heat-vanilla_2.4-ubuntu
- dib-neutron-heat-vanilla_2.6-centos-scenario
- dib-neutron-heat-vanilla_2.6-fedora-scenario
- dib-neutron-heat-vanilla_2.6-ubuntu-scenario
- dib-nova-direct-cdh-centos-aio
- dib-nova-direct-cdh-ubuntu-aio

Additionally, openstackgerrit bot writes info about changes in gerrit to #savanna channel at freenode.

Sahara/SaharaCI

Contents

Sahara CI

Sahara CI infrastructure

Sahara CI configuration

Zuul triggers