Tin Lam 5ae0bff97c Zuul v3 cross repo dependency and gate entrypoint
This patch set performs the ground work to use the zuul v3 ansible
scripts from openstack-helm-infra in the main openstack-helm repo.

Co-Authored-By: Pete Birley <pete@port.direct>
Co-Authored-By: Tin Lam <tin@irrational.io>

Depends-On: I376da8940ed085b7575dd528ec4082f42da1748c

Change-Id: I692c7c3a5102e69ad1fb271f73fea223642deb62
2017-11-22 18:05:12 +00:00
..
2017-10-05 09:19:49 -05:00
2017-10-08 06:44:45 +00:00
2017-08-21 13:55:53 -05:00
2017-10-11 18:01:44 -05:00
2017-09-22 20:32:21 +00:00
2017-05-20 11:17:45 -05:00

Openstack-Helm Gate Scripts

These scripts are used in the OpenStack-Helm Gates and can also be run locally to aid development and for demonstration purposes. Please note that they assume full control of a machine, and may be destructive in nature, so should only be run on a dedicated host.

Supported Platforms

Currently supported host platforms are:
  • Ubuntu 16.04
  • CentOS 7
  • Fedora 25

Usage (Single Node)

The Gate scripts use the setup_gate.sh as an entrypoint and are controlled by environment variables, an example of use to run the basic integration test is below:

export INTEGRATION=aio
export INTEGRATION_TYPE=basic
export PVC_BACKEND=ceph
./tools/gate/setup_gate.sh

Usage (Multi Node)

To use for a multinode deployment you simply need to set a few extra environment variables:

export INTEGRATION=multi
export INTEGRATION_TYPE=basic
export PVC_BACKEND=ceph
#IP of primary node:
export PRIMARY_NODE_IP=1.2.3.4
#IP's of subnodes:
export SUB_NODE_IPS="1.2.3.5 1.2.3.6 1.2.3.7"
#Location of SSH private key to use with subnodes:
export SSH_PRIVATE_KEY=/etc/nodepool/id_rsa
./tools/gate/setup_gate.sh

Options

You can also export some additional environment variables prior to running the ./tools/gate/setup_gate.sh that tweak aspects of the deployment.

Rather than ceph, you may use a nfs based backend. This option is especially useful on old or low spec machines, though is not currently supported with Linux Kernels >=4.10:

export PVC_BACKEND=nfs
export GLANCE=pvc

It is also possible to customise the CNI used in the deployment:

export KUBE_CNI=calico # or "canal" "weave" "flannel"
export CNI_POD_CIDR=192.168.0.0/16

If you wish to deploy using Armada then you just need to export the following variable:

export INTEGRATION_TYPE=armada