airship
/
airship-in-a-bottle
Code Issues Proposed changes
airship-in-a-bottle/tools/multi_nodes_gate
History
Bryan Strassner c2bec17529 Add build vm to multinode_genesis 
Adds the needed changes to multinode_genesis to bring it in line with
multinode_deploy.  Removes the multinode_genesis_slim, as it is just a
duplicate of the multinode_genesis with some tweaked memory sizes, and
provides no alternate flow of steps.

Change-Id: I4946fe5f2bc23f863de2aa8a187b0488fe66843b
 		2018-10-15 16:16:18 -05:00
..
airship_gate Add build vm to multinode_genesis 2018-10-15 16:16:18 -05:00
registry Fix: various documentation and URL fixes 2018-09-24 12:53:27 +02:00
README.rst Update chart references to newer versions 2018-09-05 10:15:01 -05:00
gate.sh Definition for virtual site deployment 2018-07-30 14:12:54 +00:00
setup_gate.sh Fixed permission issue to run as non-root 2018-09-14 23:01:18 +00: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.

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