Remove "deployment/", which is now in its own repo,
starlingx/virtual-deployment.
Story: 2010807
Task: 48291
Signed-off-by: Davlet Panech <davlet.panech@windriver.com>
Change-Id: I267e7b58e8a3b3c69c6a7122dbba5ab314275261
Change for Libvirt the "compute" personality to "worker".
Story: 2004022
Task: 28799
Depends-On: https://review.openstack.org/#/c/628341
Change-Id: Icba19b252b22765c7f64990fd92af19cb748fd6a
Signed-off-by: Abraham Arce <abraham.arce.moreno@intel.com>
Standard Controller can be configured as:
- Controller Storage
- Dedicated Storage
This includes reusing same function to create and destroy
compute nodes for the added storage nodes, renamed to:
- create_node
- destroy_node
Story: 2004780
Task: 28996
Change-Id: I00745db16c936c11564dbc961728e86a541cc907
Signed-off-by: Abraham Arce <abraham.arce.moreno@intel.com>
All In One can be configured as:
- Simplex
- Duplex
Story: 2004780
Task: 28996
Change-Id: I8a1ec35a525babdc44fe0df65fa58d49257d83f4
Signed-off-by: Abraham Arce <abraham.arce.moreno@intel.com>
Combine setup_allinone.sh and setup_standard_controller.sh to have one
single setup script to configure via input parameter allinone and
standardcontroller configurations:
- setup_configuration.sh
- destroy_configuration.sh
Change-Id: Id29d3eeeff43f0c0f43ab710a1179eaacdfb330d
Signed-off-by: Abraham Arce <abraham.arce.moreno@intel.com>
The default name of the first controller is controller-0
Change-Id: I3dc2221d8ec062677f0d69f99916868d5180e24f
Story: 2004088
Task: 28135
Signed-off-by: zhangkunpeng <zhang.kunpeng@99cloud.net>
Fix typo and align the line identation
Change-Id: I0acafb4638019b1301ffc1d4ce1b4ec6c74157fc
Signed-off-by: Felipe de Jesus Ruiz Garcia <felipe.de.jesus.ruiz.garcia@intel.com>
In the event that someone clones the stx-tools repo without
fore-knowledge of the wiki, this is handy. The author prepares this
commit from the experience doing just that.
Related-Bug: #1790716
Change-Id: If3d1e250e1c2c246ac894117fc649d6f145f22f1
Signed-off-by: Michel Thebeau <michel.thebeau@windriver.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>