Searching for results...

No results

Your search did not match anything from Mirantis documentation.
Check your spelling or try different keywords.

An error occurred

An error occurred while using the search.
Try your search again or contact us to let us know about it.

Newer documentation is now live.You are currently reading an older version.

Switch to latest✕

Host OS configuration management workflow

Available since MCC 2.26.0 (17.1.0 and 16.1.0) TechPreview

The workflow of the host operating system (OS) configuration API that use modules provided by MOSK or custom modules is as follows:

If you are a module consumer

1. Select one of the following options:

   • If you do not intend to use custom modules, skip to step 2.

   • If you intend to use custom modules:

     1. Contact the module creator to obtain the link to the module and its SHA256.

     2. Add the module to an existing HostOSConfigurationModules (hocm) object or create a new hocm object. For details, see HostOSConfigurationModules and Add a custom module to a MOSK deployment.

2. Add the configuration of the MOSK or custom module to an existing HostOSConfiguration (hoc) object or create a new hoc object with the following details:

   1. Add the required configuration details of the module.

   2. Set the selector for machines to apply the configuration.

   For details, see HostOSConfiguration along with HostOSConfiguration and HostOSConfigurationModules concepts.

3. Optional. Retrigger the same successfully applied module configuration. For details, see Retrigger a module configuration.

If you are a custom module creator

1. Create a custom configuration module as required. For reference, see Format and structure of a module package and Modules provided by MOSK.

2. Publish the module in a repository from which the cloud operator can fetch the module.

3. Share the module details with the cloud operator.

The following diagram illustrates the high-level overview of the host OS configuration operations API: