Clarify doc for multinode gate
This explains more clearly the default behavior for the gate.sh multinode testing script. Change-Id: I28e90c5fb8b4c8fd2dbc9f9e7da547a26d31b769
This commit is contained in:
parent
b6c000258a
commit
f0d4308126
|
@ -33,6 +33,11 @@ Setup and Use
|
||||||
|
|
||||||
where the argument for the gate.sh script is the filename of the json file
|
where the argument for the gate.sh script is the filename of the json file
|
||||||
in ./airship_gate/manifests without the json extension.
|
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
|
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
|
configuration, and the steps to run as part of that gate. Additional
|
||||||
|
|
Loading…
Reference in New Issue