...
- Compute - As before
- Storage - As before
- Network - Dedicated nodes for handling the user-traffic. All virtual routers and related network functions are running here.
- Infra/Api - KVM hosts which hosts VM's for all the tasks the old manager/monitor/controllers were doing, except for networking. They hosts VM's we use for:
- Openstack - All the services we actually want to run
- cinder: Runs the cinder api, and the scheduler and volume services.
- glance: Runs the glance-api and the glance-registry services
- heatapi: Runs the heat API
- heatengine: Runs the workers performing tasks needed by openstack heat
- horizon: Hosts the openstack web-based dashboard (horizon)
- keystone: Hosts the openstack keystone service, which is used for authentication
- neutronapi: Hosts the neutron api's
- novaapi: Hosts the nova api
- novaservices: Hosts the nova scheduler, vncproxies etc.
- Machine management - All the services we need to install and manage our machines (both physical an virtual).
- dhcp: DHCP and TFTP servers; handing out addresses and boot-images to our physical and virtual machines.
- shiftleader: Our dashboard used for administering the machines.
- Configuration management - All the services used for our configuration management.
- postgres: Hosts the postgres database used by the puppetdb
- puppet: Our puppetmasters
- puppetca: The puppet certificate authority (We only have one of these machines)
- puppetdb: The puppet database service. Stores node information and statistics
- General infrastructure - General infrastructure services hused by multiple of our machines.
- adminlb and servicelb: HAProxy load-balancers load-balancing traffic to our services from our own infrastructure and from our users respectively.
- cache: Memcached servers which are used by several of our openstack services.
- cephmon: Ceph monitors. The hosts resposnible for controlling our ceph cluster
- rabbit: Hosts the message-queues which openstack uses to communicate
- mysql: Provides the galera-cluster which acts as openstacks database backend.
- Monitoring - Services which helps us understand whats going on.
- munin: Our munin-masters. Responsible for graphing monitor-data from all our hosts.
- redis: The redis servers, which acts as a key/value store for our sensu monitoring system
- sensu: Our monitoring system which is responsible for notifying us when something breaks.
- Openstack - All the services we actually want to run
...
- Physical machines with at least two NIC's:
- One for installation and management of the machine itself. Should be an access-port (untagged) in the infrastructure VLAN.
- One NIC which is a trunk (have multiple tagged VLANS) which carries the infrastructure VLAN, the storage VLAN and the services VLAN.
- The nodes should be installed with the role "role::kvm" which sets up KVM and networking. Afterwards VM's on this node can be administered trough "Virtual Machine Manager" or any other KVM administration tool over ssh. Remember to add relevant network config for these hosts in hiera. Particulary important are these keys.
Please see this article for a more lengthy explanation.
Install the base-environment on virtual machines