fdbe8eb60d
This PS adds loopback device support to the gate scripts. Rather than using simple loopback devices we use iscsi to allow is to target the created devices via the bus they are connected to. An arbitary number of devices of a desired size can be created, and controlled via env vars. Change-Id: I05fb7f3a1564bc36903aed2c46ed996bb8cc57c8 |
||
---|---|---|
.. | ||
funcs | ||
basic_launch.sh | ||
dump_logs.sh | ||
helm_dry_run.sh | ||
kubeadm_aio.sh | ||
openstack_aio_launch.sh | ||
provision_gate_worker_node.sh | ||
README.rst | ||
setup_gate_worker_nodes.sh | ||
setup_gate.sh | ||
whitespace.sh |
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
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