Ubuntu Metal-as-a-Service (MAAS) allows treating physical servers like virtual machines in the cloud. It allows connecting and commissioning physical servers easily even after the initial setup of an environment. In conjunction with the Juju service orchestration software MaaS will enable dynamic deployment of complex OpenStack services with ease and confidence. Juju is a service orchestrator provided by Ubuntu that can be used on top of MaaS and supports the deployment of complex service like OpenStack. Juju orchestration software packages can be installed on MAAS server:
The OpenStack hardware requirements vary a great deal, depending on the desired target deployment type, storage backend choices and services co-location policies. Bare minimal OpenStack setup with MAAS and Juju can be deployed on three physical servers, yet high-availability mode for all OpenStack services (ie N+1 resilience where possible) would need 28 service units (if no service co-location is imposed).
Absolute minimal setup for an OpenStack installation that can be supported by STRATEGIC Service Store consists of 3 physical servers: MAAS server, single OpenStack controller node and one Compute node. Typical patterns for minimal OpenStack deployments are:
- Evaluation/testing setup with local storage: 1x MAAS node + 1x Controller node + 1x Compute node
- Production grade setup with SAN backed storage: 1x MAAS node + 3x HA Controller nodes + 2x Compute nodes
- Production grade setup with scale-out Ceph storage backend: 1x MAAS node + 3x HA Controller nodes + 3x Ceph storage nodes + 2x Compute nodes
The OpenStack server nodes require at least two physical network interface ports/trunks (1Gbit speed or better), together with VLAN capable core-switch and router hardware.
MAAS server depends on network access to servers out-of-band BMC IPMI hardware management interfaces, in order to control their power state – which is required for MaaS operation.
Networked storage backends for production grade deployments – using iSCSI or FiberChannel SAN or Ceph backends – need additional high-speed and dedicated network trunks (FC 8Gbit or 10Gbit Ethernet) for better stability and performance.
For gateway network security and Service Store API connection tunneling firewall and VPN devices/services are also needed.