airship
/
airship-in-a-bottle
Code Issues Proposed changes
airship-in-a-bottle/tools/multi_nodes_gate
History
Drew Walters 0b74e917b3 multinode: Add Shipyard test site stage 
This change adds a script that enables the ability to add a site test
stage to a manifest. The Shipyard test site action runs Helm tests for a
deployed site.

Change-Id: I77c123c89fe1e780ede899fa3cc6d2a726f74f49
 		2019-06-20 12:11:12 -05:00
..
airship_gate multinode: Add Shipyard test site stage 2019-06-20 12:11:12 -05: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 Definition for virtual site deployment 2018-07-30 14:12:54 +00:00
setup_gate.sh make bridge-nf configurations persistent 2019-05-29 15:36:09 -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

  1. 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.

  2. 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