starlingx/virtual-deployment
Code Issues Proposed changes
Scripts for installing StarlingX in virtualized environments
64 Commits 6 Branches 6 Tags 1.4 MiB
Python 54.2%
Shell 45.8%
1e058c0875
Go to file
hutianhao 1e058c0875 Modify install_packages.sh for system without apparmor model 
Add apparmor model to install_packages.sh for deploying simplex
in system without apparmor model.

Closes-Bug: 1821699

Change-Id: Ia3dc596be53376822c6d9639ea9b506a9a5d178e
Signed-off-by: hutianhao <hu.tianhao@99cloud.net>
2019-03-26 08:46:03 +00:00
libvirt Modify install_packages.sh for system without apparmor model 2019-03-26 08:46:03 +00:00
provision repair script simplex_stage-1.sh for deployment 2018-11-23 16:50:11 +08:00
virtualbox Add virtual environemnt deployment scripts 2018-08-30 10:16:53 -05:00
README.rst Standard Controller Configurations 2019-01-21 04:27:34 -06: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.