History

Artur Korzeniewski ece78c448d Ceph subnet_range calculation improvement

Gate scripts are trying to calculate the SUBNET_RANGE basing on IP address
of default interface. There is ipcalc tool used.
The issue is that based on infra datacenter selected to run the VM gate,
the default interface can have address with /32 network.

If IP has /32 network, the ipcalc would not calculate the network address,
for example 192.168.0.0/24, which is needed for ceph to be configured.

As a workaround, try to change the /32 to /24 after getting the IP of the
default interface, and then calculate the network address.

Change-Id: Ia2858c6a2b4c56fbc42ef06b5f157625a56beb3c

2017-10-10 18:19:10 +02:00

files

Add Rally Chart

2017-10-05 09:19:49 -05:00

funcs

Ceph subnet_range calculation improvement

2017-10-10 18:19:10 +02:00

launch-osh

Implement LDAP chart

2017-10-05 18:49:58 +00:00

openstack

Preparation for Neutron Linuxbridge gate

2017-09-12 10:23:57 +02:00

dump_logs.sh

gate: cleanup 'helm serve'

2017-10-08 06:44:45 +00:00

helm_dry_run.sh

Gate: Heat functional test

2017-08-21 13:55:53 -05: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

Ceph: RadosGW

2017-09-06 23:35:47 -05:00

setup_gate_worker_nodes.sh

Disk targeting

2017-09-22 20:32:21 +00:00

setup_gate.sh

Add Rally Chart

2017-10-05 09:19:49 -05:00

vars.sh

Add Rally Chart

2017-10-05 09:19:49 -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

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