Start an MCP OpenStack environment after a power-off

Start an MCP OpenStack environment after a power-offΒΆ

This section instructs on how to correctly start an MCP OpenStack environment after it was powered off.

If you have Ceph in your MCP cluster, start it as described in Start a Ceph cluster.

To start an MCP OpenStack environment:

  1. Start the kvm01 node hosting the dbs01 node.

  2. Start the kvm02 node hosting the dbs02 node.

  3. Start the kvm03 node hosting the dbs03 node.

    Note

    By default, the autostart option is enabled for the host nodes. Therefore, all VMs they host will start automatically.

    Otherwise, start the database server nodes in the following strict order:

    1. Start the dbs01 node.

    2. Start the dbs02 node.

    3. Start the dbs03 node.

  4. Verify that the cluster is up. In case of issues, restore the cluster as described in Restore a Galera cluster.

  5. Start the RabbitMQ server msg nodes.

  6. Verify that the cluster is up. In case of issues, proceed with Troubleshoot RabbitMQ.

  7. Start the gtw nodes.

  8. Start the OpenStack controller ctl nodes.

  9. Start the bare metal bmt nodes.

  10. For the OpenContrail deployments, start the nal and ntw nodes.

  11. Verify that the cluster is up. In case of issues, proceed with Troubleshoot OpenContrail.

  12. Start the proxy prx nodes.

  13. Start the StackLight LMA mon, mtr, and log nodes.

  14. Start the StackLight OSS cid nodes.