Davlet Panech ed39639459 Add github mirror job
Add upload-git-mirror post job to mirror this repo from
opendev.org to github.com.

Generated-by: Amazon Q Developer (Kiro)
Change-Id: Iaf62aee7f80895b9b2c227c154bfab9568cddf89
Signed-off-by: Davlet Panech <davlet.panech@windriver.com>
2026-05-04 17:20:52 -04:00
2024-04-05 16:52:09 -04:00
2023-06-28 09:46:20 -04:00
2026-05-04 17:20:52 -04:00
2023-10-30 17:09:37 +00:00
2023-08-11 13:50:12 +00:00

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 parameters passed via terminal to define the StarlingX system:

  • Controller All-in-one
  • Controller
  • Compute
  • Storage

These parameters are used to create the virtual machines, the network interfaces and completly install StarlingX.

The script will create a number of virtual machines depending on the setup chosen:

  • 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: 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.

S
Description
Scripts for installing StarlingX in virtualized environments
Readme
1.5 MiB
Languages
Python 54.2%
Shell 45.8%