Deploy OpenContrail 4.1 for OpenStack¶

This section provides instructions on how to manually deploy OpenContrail 4.1 on your OpenStack-based MCP cluster.

To deploy OpenContrail 4.1 on an OpenStack-based MCP cluster:

1. Log in to the Salt Master node.

2. Run the following basic states to prepare the OpenContrail nodes:

   salt -C 'ntw* or nal*' saltutil.refresh_pillar
   salt -C 'I@opencontrail:database' saltutil.sync_all
   salt -C 'I@opencontrail:database' state.sls salt.minion,linux,ntp,openssh
   

3. Deploy and configure Keepalived and HAProxy:

   salt -C 'I@opencontrail:database' state.sls keepalived,haproxy
   

4. Deploy and configure Docker:

   salt -C 'I@opencontrail:database' state.sls docker.host
   

5. Create configuration files for OpenContrail:

   salt -C 'I@opencontrail:database' state.sls opencontrail exclude=opencontrail.client
   

6. Start the OpenContrail Docker containers:

   salt -C 'I@opencontrail:database' state.sls docker.client
   

7. Verify the status of the OpenContrail service:

   salt -C 'I@opencontrail:database' cmd.run 'doctrail all contrail-status'
   

   In the output, the services status should be active or backup.

   Note

   It may take some time for all services to finish initializing.

8. Configure the OpenContrail resources:

   salt -C 'I@opencontrail:client and not I@opencontrail:compute' state.sls opencontrail.client
   

9. Apply the following states to deploy the OpenContrail vRouters:

   salt -C 'cmp*' saltutil.refresh_pillar
   salt -C 'I@opencontrail:compute' saltutil.sync_all
   salt -C 'I@opencontrail:compute' state.highstate exclude=opencontrail.client
   salt -C 'I@opencontrail:compute' cmd.run 'reboot'
   salt -C 'I@opencontrail:compute' state.sls opencontrail.client
   

10. After you deploy an OpenContrail-based MCP cluster:

    1. Navigate to the OpenContrail web UI as described in MCP Operations Guide: Access the OpenContrail web UI.
    2. Verify that Monitor > Infrastructure > Dashboard displays actual information about all OpenContrail nodes configured and deployed on your MCP cluster.