openstack/openstack-helm

History

portdirect a8d3dc5428 Gate: Increase service start timeouts This PS increases the timeouts for services, mariadb in particular, to come up. Change-Id: I335eb7034176b65e6d6fdf43cff3a0112d5e50d0		2017-12-20 09:27:14 -05:00
..
files	Add Rally Chart	2017-10-05 09:19:49 -05:00
funcs	Update names of helm test pods for openstack services	2017-12-14 14:03:12 +00:00
launch-osh	Update names of helm test pods for openstack services	2017-12-14 14:03:12 +00:00
openstack	Remove keypair after vm launch script	2017-11-16 13:37:47 -08:00
playbooks	Docs: Updated developer documentation to use -infra repo	2017-12-06 14:52:16 -06:00
dump_logs.sh	Fix dumps_log playbook	2017-11-25 01:25:27 +00:00
helm_dry_run.sh	Fixed helm_dry_run path issue	2017-11-27 14:52:28 +00:00
kubeadm_aio.sh	Gate: Heat functional test	2017-08-21 13:55:53 -05:00
provision_gate_worker_node.sh	Gate: Heat functional test	2017-08-21 13:55:53 -05:00
README.rst	Parameterize charts for NFS in gate	2017-10-11 18:01:44 -05:00
setup_gate_worker_nodes.sh	Disk targeting	2017-09-22 20:32:21 +00:00
setup_gate.sh	Zuul v3 cross repo dependency and gate entrypoint	2017-11-22 18:05:12 +00:00
vars.sh	Gate: Increase service start timeouts	2017-12-20 09:27:14 -05:00
whitespace.sh	Add a whitespace check script	2017-05-20 11:17:45 -05:00

README.rst

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