...
Install OS om VM's, and let them get base-configuration.
...
A good starting-point now would be to create all the VM's which should be your infrastructure and then tank them with an OS and the "role::base" class. This way you can see that all installations goes fine, and that they recieve appropriate networking configuration for all their interfaces.
There are some hierakeys that you should populate to ease the trasition a little:
- ntnuopenstack::oldcontrollers
- A hash with 'controller-name':'controller-ip' pairs for each of the old controllers.
- profile::networks::management::ipv4::prefix::extra
- The IPv4 prefix for the old management network.
- profile::interfaces::IFNAME::routes:
- In the node-specific hiera-file for all hosts having a leg in the storage-network you should add an extra route to the old storage-network if this network is separate from the new. (Probably only applies for skylow and skyhigh)
Start installing services in the VM's
The first services to install should be:
- General infrastructure
- When installing new ceph-mons it is important that the old monitors knows about the new one first. Pay attention to the installation article.
- Machine management (if these services is not provided externally)
- Configuration management (if these services is not provided externally)
- Monitoring
At this point you should have the base infrastructure in place. If you register the old controllers in hiera (the key ntnuopenstack::oldcontrollers, which should be a hash where the key is the controller-name and the value is the controllers management IP) they will be configured as haproxy-backends in the new infrastructure.
If there is a migration from old to new networks at the same time, the old machines (controllers, storage and compute) needs to get some routes to the new networks. This way they will be able to use the new services
Migrate traffic trough the new infrastructure
When the loadbalancers is installed, and have at least one backend for every service (the old controllers can for now be good backends for the openstack services) you can start to route traffic trough the loadbalancers.
- By setting the keys "profile::openstack::endpoint::*" in hiera to 'https://*whatevernameyouplantouse*' in the old controllers the endpoint-catalog will be updated to point to these names.
- If you do not want TLS on the API's you can use http in the link; but in this case the keys profile::haproxy::management::apicert and profile::haproxy::services::apicert have to be unset. The haproxy responds with an empty response if it is configures for TLS but gets a cleartext request.
- TODO: What about rabbit?
- TODO: something else?
Install openstack services
When traffic passes trough the loadbalancers it is straightforward to install openstack services
...
(Prepare for migration)
(Re)install compute
(Re)install storage
Decommision old controllers
...
on the VM's. When installing a new API node puppet will make sure to configure the loadbalancers to include it in their configuration. You should thus now install the following roles on vm's:
- openstack::cinder
- openstack::glance
- openstack::heat::api
- openstack::heat::engine
- openstack::horizon
- openstack::keystone
- openstack::neutron::api
- openstack::nova::api
- openstack::nova::services
You should now also install one or more physical nodes with the role "openstack::neutron::net" which will handle our user's traffic.
Migrate away from the old networks
To migrate away from the old networks you would need to reinstall the compute and storage machines when they move to the new networks.
Reinstall compute
- Migrate all VM's to another compute-host
- Move the machine to new VLAN's
- Reinstall the compute-node.
Reinstall storage
- Disable ceph rebalancing.
- Move the machine to new VLAN's, and reinstall it without having OSD's listed in the hierafile.
- Add the old OSD's like described in this article.
- Enable ceph rebalancing.
Decommision old controllers
Decommisioning of the old controllers can be done when all the services are delivered from other machines. Follow these steps:
- Stop the ceph manager and monitors on a controller.
- Remove this controller from the ceph cluster.
- Migrate routers and DHCP agents to new neutron network nodes.
- Gracefully shut down the machine to allow it to leave the galera cluster nicely.
- Deregister all agents and services this controller had in openstack.