Ardana Entry Scale Cloud with VSA and DCN Example

The input files in this example deploy a DCN cloud that has the following characteristics:

Control Planes

• A single control plane consisting of five servers that co-host all of the required services.

Resource Pools

• One compute Node

• Three VSA Nodes

• One DCN VRS-G Node

• One VSC Host for Running a VSC

Additional resource nodes can be added to the configuration.

Minimal Swift Resources are provided by the control plane

Deployer Node

This configuration runs the lifecycle-manager (formerly referred to as the deployer) on a control plane node. You need to include this node address in your servers.yml definition. This function does not need a dedicated network.

An example set of servers are defined in data/servers.yml. You will need to modify this file to reflect your specific environment.

Networking

The example requires the following networks:

IPMI/iLO network, connected to the deployer and the IPMI/iLO ports of all servers

A pair of bonded NICs which are used by the following networks:

• External API - This is the network that users will use to make requests to the cloud
• External GW - This is the network that will be used to access the outside world using floating IPs
• Guest - This is the network that will carry traffic between VMs on private networks within the cloud
• Cloud Management - This is the network that will be used for all internal traffic between the cloud services. This network is also used to install and configure the nodes and for iSCSI traffic as well. This network needs to be on an untagged VLAN

Note that the EXTERNAL_API network must be reachable from the EXTERNAL_GW network if you want VMs to be able to make API calls to the cloud.

An example set of networks are defined in data/networks.yml. You will need to modify this file to reflect your environment.

The example uses the devices hed3 & hed4 as a bonded network for all services. If you need to modify these for your environment they are defined in data/net_interfaces.yml The network devices eth3 & eth4 are renamed to devices hed4 & hed5 using the PCI bus mappings secified in data/nic_mappings.yml. You may need to modify the PCI bus addresses to match your system.

Local Storage

All servers should present a single OS disk, protected by a RAID controller. This disk needs to be at least 512GB in capacity. VSA appliance deployed on a host is expected to consume ~40 GB of disk space from host root disk for ephemeral storage to run VSA VM. In addition the example configures one additional disk depending on the role of the server:

• Controllers: /dev/sdb is configured to be used by Swift
• Compute Servers and VSC-Host nodes: /dev/sdb is configured as an additional Volume Group to be used for VM storage
• VSA Servers: /dev/sdc is configured for VSA data storage and /dev/sdb is configured for VSA cache (required only for adaptive-optimization)

Note that VSA can be deployed with adaptive optimization (AO) or without AO. AO allows built-in storage tiering for VSA. It is recommended to use SSD disk for AO.

Additional disks can be configured for any of these roles by editing the corresponding data/disks_*.yml file