airship-in-a-bottle/tools/multi_nodes_gate
SKELS, KASPARS (ks3019) 2eb94c51ab Cert/key related improvements to gate-multinode
* Adds new config option GATE_SSH_KEYS to enable user provided SSH key-pair.
  This applies to both virtmgr and access to virtual nodes

* Adds new config option USE_EXISTING_SECRETS to use already existing
  manifests for certificates and SSH key files

Change-Id: Ic77c7f5cc526dacc137dfe5b97b8fa32e728324e
2019-03-12 21:39:23 +00:00
..
airship_gate Cert/key related improvements to gate-multinode 2019-03-12 21:39:23 +00: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