Go to file

Daniel Caires d3f4d23f59 Changes to make AIO-DX setup work

-Minimal changes so the script works for the
installation of a AIO-DX setup type.
-Addition of a lab_setup2 for the configuration
of the controller-1.
-Change of serial port configuration so VMs can boot
without the need of a socat connection.

Regression: AIO-SX successfully provisioned using
modified code.

Test Plan:
PASS: StarlingX is succesful deployed in a AIO Duplex
configuration.
PASS: Both controllers are set with TCP as Port Mode
in serial ports configuration.

Story: 2005051
Task: 48261
Task: 48275

Change-Id: I5fd5c6d413270867424a30768b0ad7ff91d296b8
Signed-off-by: Daniel Caires <daniel.caires@encora.com>

2023-07-20 14:15:40 -03:00

libvirt

Merge "Modify controller_allinone.xml for deploying simplex in AMD environment"

2019-04-18 14:55:33 +00:00

provision

repair script simplex_stage-1.sh for deployment

2018-11-23 16:50:11 +08:00

requirements

Adding pylint to /virtualbox/pybox

2023-06-30 12:12:01 -03:00

virtualbox

Changes to make AIO-DX setup work

2023-07-20 14:15:40 -03:00

.gitreview

Add .gitreview file

2023-06-28 09:46:20 -04:00

.zuul.yaml

Adding unit tests in pybox python scripts.

2023-07-03 15:37:12 -03:00

pylint.rc

Assigned local port doesn't stop installation

2023-07-05 11:24:17 -03:00

README.rst

Standard Controller Configurations

2019-01-21 04:27:34 -06:00

tox.ini

Adding unit tests in pybox python scripts.

2023-07-03 15:37:12 -03:00

README.rst

StarlingX Deployment in Virtualized Environments

A StarlingX system can be installed in a variety of platforms with the following deployment options:

Standard Controller
- Dedicated Storage
- Controller Storage
All-in-one
- Duplex
- Simplex

Deployment options uses a variety of configurations based on 3 node identities:

Controller
Storage
Compute

Standard Controller :: Dedicated Storage

The software installation workflow for an initial Ceph-backed block storage on dedicated storage nodes is:

Controller-0 Installation and Provisioning
Controller-1 / Compute Host / Storage Host Installation
Controller-1 Provisioning
Provider Network Configuration
Compute Host Provisioning
Storage Host Provisioning

Standard Controller :: Controller Storage

The software installation workflow for an initial LVM-backed block storage on controller nodes is:

Controller-0 Installation
Controller-0 and System Provisioning
Controller-1 / Compute Host Installation
Controller-1 Provisioning
Compute Host Provisioning

All-in-one :: Duplex

The software installation workflow for two combined controller / compute nodes is:

Controller-0 Installation and Provisioning
Controller-1 Installation and Provisioning

All-in-one :: Simplex

The software installation workflow for a single combined controller / compute node is:

Controller-0 Installation and Provisioning

Virtualization Environments

The available virtualization products where StarlingX has been deployed are:

VirtualBox
Libvirt/QEMU

Directory: libvirt

Deployment under Libvirt/QEMU uses a set of xml files to define the node identity:

Controller All-in-one
Controller
Compute
Storage

These nodes are used to create the virtual machines and the network interfaces to setup the StarlingX system:

Setup Simplex
- 1 Controller
Setup Duplex
- 2 Controllers
Setup Controller Storage
- 2 Controllers
- 2 Computes
Setup Dedicated Storage
- 2 Controllers
- 2 Computes
- 2 Storages

Directory: virtualbox

Deployment under VirtualBox uses a set of configuration files to define the StarlingX system:

All-in-one Configuration
Standard Controller Configuration

These configurations files are used to create the virtual machines and the network interfaces from a single script:

Setup VM

Directory: provision

A set of scripts are provided to automate the provisioning of data interfaces and local storage resources for the compute function for StarlingX Duplex or Simplex.