Add an override variable for the DISK file location for each node in a
virtual lab. Introduced the ability to set disk file location for all
nodes in a config file. (was hardcoded to /var/lib/libvirt/images)
This enhancement enables better utilization of the host's disk
resources, allowing for more complex deployments such as
'Distributed Cloud'.
Test plan:
PASS: pylint, flake8, bashate
PASS: Regression for default and madcloud examples
PASS: Able to change what is storage and how many are applied
PASS: Copy default.yaml and modify values of disk directories for nodes
and compare to default.yaml
Story: 2010816
Task: 48397
Change-Id: If19404ed151739c4abcbd5f2c3b9fb62132ed6fe
Signed-off-by: Bailey Henry <Henry.Bailey@windriver.com>
ifconfig and brctl are deprecated commands.
They are replaced with ip command.
Story: 2004646
Task: 28597
Change-Id: I24e2d53ae7f8b866eef665a85d1785df0527c82a
Signed-off-by: Felipe de Jesus Ruiz Garcia <felipe_57@live.com.mx>
Signed-off-by: Felipe de Jesus Ruiz Garcia <felipe.de.jesus.ruiz.garcia@intel.com>
The INTERNAL and EXTERNAL networks configured by destroy and setup
network scripts are inverted with reference to the default
config_controller selections as well as the wiki
StarlingX/Installation_Guide_Virtual_Environment/Controller_Storage.
The most pressing concern in this is that what was actually the internal
management network was being nat'd.
Also, under normal testing it is not recommended to address the internal
management network from the virtualization host. There are unlikely to be
configurations that will have external devices addressing the management
network.
Delete what was "EXTERNAL", actually internal, and rename "INTERNAL" to
be EXTERNAL.
Related-Bug: #1790716
Change-Id: I08f9e7712fed120001c864903880e13e9478764d
Signed-off-by: Michel Thebeau <michel.thebeau@windriver.com>
* Split the network setup/teardown bits into their own scripts
so you can shoot yourself in the foot with intention
rather then unexpectedly.
* Cowardly refuse to configure a network if the first interface name exists
* Change the default bridge name to stxbr
* Make the network variables all configurable via the environment
* Don't make assumptions about where ISOIMAGE is located
* Include a basic doc that outlines the differences from existing
installation steps. (Needs more!)
Change-Id: Ic46c03a09da97765b9f6bfe07e089efa38738993
Signed-off-by: Dean Troyer <dtroyer@gmail.com>