To reduce the deployment time and eliminate possible human errors, Mirantis recommends that you use the semi-automated approach to the MCP DriveTrain deployment as described in this section.
Caution
The execution of the CLI commands used in the MCP Deployment
Guide requires root privileges. Therefore, unless explicitly
stated otherwise, run the commands as a root user or use
sudo.
The deployment of MCP DriveTrain bases on the bootstrap automation of the Salt Master node. On a Reclass model creation, you receive the configuration drives by the email that you specified during the deployment model generation.
Depending on the deployment type, you receive the following configuration drives:
cfg01 VM that is used in cloud-init to set up a virtual machine
with Salt Master, MAAS provisioner, Jenkins server, and local Git server
installed on it.| # | Description |
|---|---|
| 1 | Manually deploy and configure the Foundation node as described in Prerequisites for MCP DriveTrain deployment. |
| 2 | Create the deployment model using the Model Designer web UI as described in Create a deployment metadata model. |
| 3 | Obtain the pre-built ISO configuration drive(s) with the Reclass deployment metadata model to you email. If required, customize and regenerate the configuration drives as described in Generate configuration drives manually. |
| 4 | Bootstrap the APT node. Optional, for an offline deployment only. For details, see: Deploy the APT node. |
| 5 | Bootstrap the Salt Master node that contains MAAS provisioner, Jenkins server, and local Git server. For details, see: Deploy the Salt Master node. |
| 6 | Deploy the remaining bare metal servers using the MAAS provisioner. For details, see: Provision physical nodes using MAAS and Deploy physical nodes. |
| 7 | Deploy MCP CI/CD using Jenkins as described in Deploy CI/CD. |