Description

This article explains the start and shutdown order of CSO (Contrail Service Orchestration) VMs (Virtual Machines).

This is useful for kernel upgrades or for troubleshooting purposes where you are controlling the start and shutdown order of the VMs.

Solution

If Microservices VM is started first, it looks for connection/status of Maria DB (which is part of infra VM) and if infra VM is not running, Microservices would fail to come up/timeout.

For simplicity, each and every service connection is not explained in this document.

Start order:

central/regional infravm
central/regional elkvm
central/regional lbvm
central/regional sblb
central/regional contrail analytics
central/regional k8mastervm
central/regional msvm

Shutdown order:

central/regional msvm
central/regional k8mastervm
central/regional contrail analytics
central/regional sblb
central/regional lbvm
central/regional elkvm
central/regional infravm

Recommendation: Once the VM starts, you can login and check the status of all the services (using commands: kubectl get pods and service --status-all ) to make sure all services are up before starting another VM in order.