airship-in-a-bottle/tools/multi_nodes_gate
Egorov, Stanislav (se6518) 22cbd89a6d Extract hyperkube before promenade
Prepare hyperkube binary before running promenade container.
This is to simplify procedure when using hyperkube image.

Change-Id: I04dfdef1247e7d1701e673e53132e6a9208d3c64
2019-06-27 15:32:02 +00:00
..
airship_gate Extract hyperkube before promenade 2019-06-27 15:32:02 +00: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