System Requirements

Before you begin the installation, your system must meet the following requirements.

Infrastructure

Minimum Node Specification

Deployer node

  • (v)CPU: 4
  • Memory: 4GB
  • Storage: 40GB

CaaS Platform worker node

  • (v)CPU: 6

  • Memory: 16GB

  • Storage: 80GB

    If the work node is used as Compute node, sizing should be determined by the target workloads on the compute node.

SES node

  • (v)CPU: 6
  • Memory: 16GB
  • Storage: 80GB

Cluster size

A minimal CaaS Platform cluster requires one administration node, one master node and two worker nodes.

SUSE Containerized OpenStack enrolls CaaS Platform work nodes for two different purposes: control plane where the Airship and OpenStack services run and compute nodes where customer workloads are hosted.

For a minimal cloud, you should plan one worker node for the control plane, and one or more worker nodes as OpenStack compute nodes.

For a high availability (HA) cloud, we recommend three worker nodes designated for the Airship and OpenStack control plane, and additional worker nodes allocated for compute. For detailed information about scale profiles, see Configure Cloud Scale Profile.

Network Requirements

  • CaaS Platform networking

    Create necessary CaaS Platform networks before deploying SUSE Containerized OpenStack. Separating traffic by function is recommended but not required.

  • Storage Network

    A separate storage network can be created to isolate storage traffic. This separate network should be present on the Caas Platform and ses_config.yml mon_host: section.

  • Tunnel Network

    A network defined by its network interface. It must be up and have an IP address defined. This is used for tunneling VXLAN traffic for tenant VMs within the cloud.

  • External Network

    A network defined by its network interface. This interface should not have an IP address defined (will not be accessible when cloud deployed). The network interface should be configured ‘BOOTPROTO=none’ and active.

    Note

    If installing on VMware infrastructure, make sure this network has security set to allow promiscuous mode and forged transmit.

  • VIP for Airship and OpenStack

    Virtual IP address will be assigned to Pods allowing ingress to Airship and OpenStack services. The ingress IP assignments for these services must be on a subnet present on the Caas Platform nodes and an IP that is not currently in use. VIPs are configured in env/extravars. See Configure the VIP that will be used for OpenStack service public endpoints for information about vars for VIPs.

  • DNS

    Installing SUSE Containerized OpenStack updates /etc/hosts on all CaaS Platform nodes and Deployer. If expanding testing beyond these devices, we recommend using DNS for sharing this data. It is possible to configure the Deployer with dnsmasq to supply DNS functionality, but this is beyond the scope of this preview.

Distributed Virtual Routing (DVR) is not supported in this Technology Preview.

Only flat networks are supported in SUSE Containerized OpenStack Cloud.

Note

Network configuration examples can be found in Advanced Users