History

Sphicas, Phil (ps3910) c5044663e0 Add apparmor profiles on genesis node in multinode gate The bootactions which will be deployed via Drydock on nodes need to be performed on Genesis node as well. This should be done as part of pre-genesis setup before genesis.sh is executed. This patchset allows apparmor profiles to be staged on the genesis node in the same manner as seccomp profiles. Change-Id: I418c955a131dc8e23ab5f4d900ae5ea4f7985468 Reference: https://review.opendev.org/644824		2019-08-14 17:48:16 -07:00
..
airship_gate	Add apparmor profiles on genesis node in multinode gate	2019-08-14 17:48:16 -07:00
registry	Fix: various documentation and URL fixes	2018-09-24 12:53:27 +02:00
README.rst	Clarify doc for multinode gate	2019-05-22 11:48:15 -05:00
gate.sh	Improve VM failure data collection	2019-07-01 14:04:47 -05:00
setup_gate.sh	(multinode) Besteffort to disable brnetfilter	2019-07-12 07:00:23 -05:00

README.rst

Gates

Airship-in-a-bottle contains the multi_node_gates utility to aid developers and automation of Airship. These tools are found in tools/multi_node_gates.

Setup and Use

First time, and only needed once per node, ./setup_gate.sh will prepare the node for use by setting up the necessary users, virsh and some dependencies.
gate.sh is the starting point to run each of the named gates, found in ./airship_gate/manifests, e.g.:
```
$ ./gate.sh multinode_genesis
```
where the argument for the gate.sh script is the filename of the json file in ./airship_gate/manifests without the json extension. if you run the script without any arguments:
```
$ ./gate.sh
```
then it will by default stand up a four-node Airship cluster.

Each of the defined manifests used for the gate defines a virtual machine configuration, and the steps to run as part of that gate. Additional information found in each file is a configuration that targets a particular set of Airship site configurations, which in some of the provided manifests are found in the deployment_files/site directory.

Other Utilities

Several useful utilities are found in ./airship_gate/bin to facilitate interactions with the VMs created. These commands are effectively wrapped scripts providing the functionality of the utility they wrap, but also incorporating the necessary identifying information needed for a particular run of a gate. E.g.:

$ ./airship_gate/bin/ssh.sh n0