General deployment parameters

General deployment parameters

The tables in this section outline the general configuration parameters that you can define for your deployment model through the Model Designer web UI. Consult the Define the deployment model section for the complete procedure.

The General deployment parameters wizard includes the following sections:

  • Basic deployment parameters cover basic deployment parameters

  • Services deployment parameters define the platform you need to generate the model for

  • Networking deployment parameters cover the generic networking setup for a dedicated management interface and two interfaces for the workload. The two interfaces for the workload are in bond and have tagged sub-interfaces for the Control plane (Control network/VLAN) and Data plane (Tenant network/VLAN) traffic. The PXE interface is not managed and is leaved to default DHCP from installation. Setups for the NFV scenarios are not covered and require manual configuration.

Basic deployment parameters


Default JSON output


Cluster name

cluster_name: deployment_name

The name of the cluster that will be used as cluster/<cluster_name>/ in the project directory structure

Cluster domain

cluster_domain: deploy-name.local

The name of the domain that will be used as part of the cluster FQDN

Public host

public_host: ${_param:openstack_proxy_address}

The name or IP address of the public endpoint for the deployment

Reclass repository


The URL to your project Git repository containing your models

Cookiecutter template URL


The URL to the Cookiecutter template repository

Cookiecutter template branch

cookiecutter_template_branch: master

The branch of the Cookiecutter template repository to use, master by default. Use refs/tags/<mcp_version> to generate the model that corresponds to a specific MCP release version. For example, 2017.12. Other possible values include stable and testing.

Shared Reclass URL

shared_reclass_url: ssh://

The URL to the shared system model to be used as a Git submodule for the MCP cluster

MCP version

mcp_version: stable

Version of MCP to use, stable by default. Enter the release version number, for example, 2017.12. Other possible values are: nightly, testing. For nightly, use cookiecutter_template_branch: master.

Cookiecutter template credentials

cookiecutter_template_credentials: gerrit

Credentials to Gerrit to fetch the Cookiecutter templates repository. The parameter is used by Jenkins

Deployment type

deployment_type: physical

The supported deployment types include:

  • Physical for the OpenStack platform

  • Physical and Heat for the Kubernetes platform

Publication method

publication_method: email

The method to obtain the template. Available options include:

  • Send to the e-mail address

  • Commit to repository

Services deployment parameters


Default JSON output



  • platform: openstack_enabled

  • platform: kubernetes_enabled

The platform to generate the model for:

  • The OpenStack platform supports OpenContrail, StackLight LMA, Ceph, CI/CD, and OSS sub-clusters enablement. If the OpenContrail is not enabled, the model will define OVS as a network engine.

  • The Kubernetes platform supports StackLight LMA and CI/CD sub-clusters enablement, OpenContrail networking, and presupposes Calico networking. To use the default Calico plugin, uncheck the OpenContrail enabled check box.

StackLight enabled

stacklight_enabled: 'True'

Enables a StackLight LMA sub-cluster.

Gainsight service enabled

gainsight_service_enabled: 'False'

Enables support for the Salesforce/Gainsight service

Salesforce notifications enabled

sf_notifications_enabled: 'False'

Enables sending of Alertmanager notifications to Salesforce

Ceph enabled

ceph_enabled: 'True'

Enables a Ceph sub-cluster.

CI/CD enabled

cicd_enabled: 'True'

Enables a CI/CD sub-cluster.

OSS enabled

oss_enabled: 'True'

Enables an OSS sub-cluster.

Benchmark node enabled

bmk_enabled: 'False'

Enables a benchmark node. False, by default.

Barbican enabled

barbican_enabled: 'False'

Enables the Barbican service

Back end for Barbican

barbican_backend: dogtag

The back end for Barbican

Networking deployment parameters


Default JSON output


DNS Server 01


The IP address of the dns01 server

DNS Server 02


The IP address of the dns02 server

Deploy network subnet


The IP address of the deploy network with the network mask

Deploy network gateway


The IP gateway address of the deploy network

Control network subnet


The IP address of the control network with the network mask

Tenant network subnet


The IP address of the tenant network with the network mask

Tenant network gateway


The IP gateway address of the tenant network

Control VLAN

control_vlan: '10'

The Control plane VLAN ID

Tenant VLAN

tenant_vlan: '20'

The Data plane VLAN ID

NTP servers Added since 2019.2.6 update,

The comma-separated list of Network Time Protocol (NTP) servers. You can also configure multiple NTP servers as required, for example,,,