* Compute nodes to run guest operating systems [installation guide](https://support.ba.infn.it/redmine/projects/automaticocp/wiki/ComputePuppetIAAS)
## Setup
### Setup Requirements
This module assumes nodes running Ubuntu 14.04 (Trusty) with either Puppet Enterprise or Puppet. Puppet must have pluginsync, trusted_node_data and storeconfigs enabled.
This module assumes nodes running Ubuntu 14.04 (Trusty) with either Puppet Enterprise or Puppet.
More information related to the setup requirement are available in the present guide [Setup requirements](https://support.ba.infn.it/redmine/projects/automaticocp/wiki/TestbedPuppet)
This module depends on Hiera.
### Beginning with puppet-iaas
To ensure high availability, three storage nodes, three controller nodes and two endpoint nodes must be deployed, be sure to have eight available servers.
### Beginning with iaas module
To ensure high availability, three Service nodes, three Storage nodes, two Controller nodes and two Network nodes must be deployed, be sure to have ten available servers. In addition, a number of Compute nodes are also to be available for the deployment.
## Usage
### Hiera Configuration
The nodes should be deployed in the following order : Service nodes, Storage nodes, Controller nodes, Network nodes and then Compute nodes.
The first step to using the iaas-puppet module is to configure hiera with settings specific to your installation. In this module, the `examples` directory contains sample common.yaml file with all of the settings required by this module, as well as node configuration samples to test your deployment with. These configuration options include network settings, locations of specific nodes, and passwords. If any of these settings are undefined or not properly set, your deployment may fail.
### Hiera Configuration
The first step to using the iaas module is to configure hiera with specific settings pointing to your installation.
In this module, the `examples` directory contains sample 'common.yaml' file with all of the settings required by this module.
These configuration options include Service settings, Storage settings, Network settings, OpenStack core settings and related passwords.
If any of these settings are undefined or not properly set, your deployment may fail.
### Site configuration
You then have to write your `site.pp` according to your deployment. Below is an example :
The second step to using the iaas module is to configure manifest file with specific settings pointing to your installation.
In this module, the `examples` directory contains sample 'site.pp' file according to your deployment.
These configuration options include Service variables and node-specific configuration settings.
If any of these settings are undefined or not properly set, your deployment may fail.
node /^compute-\d+.iaas$/ {
include 'iaas::role::compute'
}
```
### Node balancing
The nodes should be deployed in the following order : storage nodes, endpoints, controllers and then compute nodes.
In order to balance requests across the different nodes, HAproxy and Keepalived have to be configured properly. Make sure also that node hostname con be asily resolved.
### Balancing the endpoint nodes
## References
In order to balance requests across the different endpoints nodes, several solutions could be imagined but I believe that DNS Round-Robin is the easiest solution.
In order to devop and test the module and its components, the following official guides and sites have been considered:
