The tables in this section outline the product configuration parameters including infrastructure, CI/CD, OpenContrail, OpenStack, Kubernetes, Stacklight LMA, and Ceph hosts details. You can configure your product infrastructure for the deployment model through the Model Designer web UI. Consult the Define the deployment model section for the complete procedure.
The Product deployment parameters wizard includes the following sections:
Section | Default JSON output | Description |
---|---|---|
Infra kvm01 hostname |
infra_kvm01_hostname: kvm01 |
The hostname of the first KVM node |
Infra kvm01 control address |
infra_kvm01_control_address: 10.0.1.241 |
The IP address of the first KVM node on the control network |
Infra kvm01 deploy address |
infra_kvm01_deploy_address: 10.0.0.241 |
The IP address of the first KVM node on the management network |
Infra kvm02 hostname |
infra_kvm02_hostname: kvm02 |
The hostname of the second KVM node |
Infra kvm02 control address |
infra_kvm02_control_address: 10.0.1.242 |
The IP address of the second KVM node on the control network |
Infra kvm02 deploy address | infra_kvm02_deploy_address: 10.0.0.242 |
The IP address of the second KVM node on the management network |
Infra kvm03 hostname |
infra_kvm03_hostname: kvm03 |
The hostname of the third KVM node |
Infra kvm03 control address |
infra_kvm03_control_address: 10.0.1.243 |
The IP address of the third KVM node on the control network |
Infra kvm03 deploy address |
infra_kvm03_deploy_address: 10.0.0.243 |
The IP address of the third KVM node on the management network |
Infra KVM VIP address | infra_kvm_vip_address: 10.0.1.240 |
The virtual IP address of the KVM cluster |
Infra deploy NIC | infra_deploy_nic: eth0 |
The NIC used for PXE of the KVM hosts |
Infra primary first NIC | infra_primary_first_nic: eth1 |
The first NIC in the KVM bond |
Infra primary second NIC | infra_primary_second_nic: eth2 |
The second NIC in the KVM bond |
Infra bond mode | infra_bond_mode: active-backup |
The bonding mode for the KVM nodes. Available options include:
To decide which bonding mode best suits the needs of your deployment, you can consult the official Linux bonding documentation. |
OpenStack compute count | openstack_compute_count: '100' |
The number of compute nodes to be generated. The naming convention
for compute nodes is cmp000 - cmp${openstack_compute_count} .
If the value is 100 , for example, the host names for the compute
nodes expected by Salt include cmp000 , cmp001 , …, cmp100 . |
Section | Default JSON output | Description |
---|---|---|
CI/CD control node01 address |
cicd_control_node01_address: 10.0.1.91 |
The IP address of the first CI/CD control node |
CI/CD control node01 hostname |
cicd_control_node01_hostname: cid01 |
The hostname of the first CI/CD control node |
CI/CD control node02 address |
cicd_control_node02_address: 10.0.1.92 |
The IP address of the second CI/CD control nod |
CI/CD control node02 hostname |
cicd_control_node02_hostname: cid02 |
The hostname of the second CI/CD control node |
CI/CD control node03 address |
cicd_control_node03_address: 10.0.1.93 |
The IP address of the third CI/CD control node |
CI/CD control node03 hostname |
cicd_control_node03_hostname: cid03 |
The hostname of the third CI/CD control node |
CI/CD control VIP address | cicd_control_vip_address: 10.0.1.90 |
The virtual IP address of the CI/CD control cluster |
CI/CD control VIP hostname | cicd_control_vip_hostname: cid |
The hostname of the CI/CD control cluster |
Section | Default JSON output | Description |
---|---|---|
OSS address | oss_address: ${_param:stacklight_monitor_address} |
VIP address of the OSS cluster |
OSS node01 address |
oss_node01_addres: ${_param:stacklight_monitor01_address} |
The IP address of the first OSS node |
OSS node02 address |
oss_node02_addres: ${_param:stacklight_monitor02_address} |
The IP address of the second OSS node |
OSS node03 address |
oss_node03_addres: ${_param:stacklight_monitor03_address} |
The IP address of the third OSS node |
OSS OpenStack auth URL | oss_openstack_auth_url: http://172.17.16.190:5000/v3 |
OpenStack auth URL for OSS tools |
OSS OpenStack username | oss_openstack_username: admin |
Username for access to OpenStack |
OSS OpenStack password | oss_openstack_password: nova |
Password for access to OpenStack |
OSS OpenStack project | oss_openstack_project: admin |
OpenStack project name |
OSS OpenStack domain ID | oss_openstack_domain_id: default |
OpenStack domain ID |
OSS OpenStack SSL verify | oss_openstack_ssl_verify: 'False' |
OpenStack SSL verification mechanism |
OSS OpenStack certificate | oss_openstack_cert: '' |
OpenStack plain CA certificate |
OSS OpenStack credentials path | oss_openstack_credentials_path: /srv/volumes/rundeck/storage |
OpenStack credentials path |
OSS OpenStack endpoint type | oss_openstack_endpoint_type: public |
Interface type of OpenStack endpoint for service connections |
OSS Rundeck external datasource enabled | oss_rundeck_external_datasource_enabled: False |
Enabled external datasource (PostgreSQL) for Rundeck |
OSS Rundeck forward iframe | rundeck_forward_iframe: False |
Forward iframe of Rundeck through proxy |
OSS Rundeck iframe host | rundeck_iframe_host: ${_param:openstack_proxy_address} |
IP address for Rundeck configuration for proxy |
OSS Rundeck iframe port | rundeck_iframe_port: ${_param:haproxy_rundeck_exposed_port} |
Port for Rundeck through proxy |
OSS Rundeck iframe ssl | rundeck_iframe_ssl: False |
Secure Rundeck iframe with SSL |
OSS webhook from | oss_webhook_from: TEXT |
Required. Notification email sender. |
OSS webhook recipients | oss_webhook_recipients: TEXT |
Required. Notification email recipients. |
OSS Pushkin SMTP host | oss_pushkin_smtp_host: 127.0.0.1 |
The address of SMTP host for alerts notifications |
OSS Pushkin SMTP port | oss_pushkin_smtp_port: 587 |
The address of SMTP port for alerts notifications |
OSS notification SMTP with TLS | oss_pushkin_smtp_use_tls: 'True' |
Enable using of the SMTP server under TLS (for alert notifications) |
OSS Pushkin email sender password | oss_pushkin_email_sender_password: password |
The sender-mail password for alerts notifications |
SFDC auth URL | N/A | Authentication URL for the Salesforce service.
For example, sfdc_auth_url: https://login.salesforce.com/services/oauth2/token |
SFDC username | N/A | Username for logging in to the Salesforce service.
For example, sfdc_username: user@example.net |
SFDC password | N/A | Password for logging in to the Salesforce service.
For example, sfdc_password: secret |
SFDC consumer key | N/A | Consumer Key in Salesforce required for Open Authorization (OAuth).
For example, sfdc_consumer_key: example_consumer_key |
SFDC consumer secret | N/A | Consumer Secret from Salesforce required for OAuth.
For example, sfdc_consumer_secret: example_consumer_secret |
SFDC organization ID | N/A | Salesforce Organization ID in Salesforce required for OAuth.
For example, sfdc_organization_id: example_organization_id . |
SFDC environment ID | sfdc_environment_id: 0 |
The cloud ID in Salesforce |
SFDC Sandbox enabled | sfdc_sandbox_enabled: True |
Sandbox environments are isolated from production Salesforce clouds.
Enable sandbox to use it for testing and evaluation purposes. Verify
that you specify the correct sandbox-url value in the
sfdc_auth_url parameter. Otherwise, set the parameter to False. |
OSS CIS username | oss_cis_username: ${_param:oss_openstack_username} |
CIS username |
OSS CIS password | oss_cis_password: ${_param:oss_openstack_password} |
CIS password |
OSS CIS OpenStack auth URL | oss_cis_os_auth_url: ${_param:oss_openstack_auth_url} |
CIS OpenStack authentication URL |
OSS CIS OpenStack endpoint type | oss_cis_endpoint_type: ${_param:oss_openstack_endpoint_type} |
CIS OpenStack endpoint type |
OSS CIS project | oss_cis_project: ${_param:oss_openstack_project} |
CIS OpenStack project |
OSS CIS domain ID | oss_cis_domain_id: ${_param:oss_openstack_domain_id} |
CIS OpenStack domain ID |
OSS CIS certificate | oss_cis_cacert: ${_param:oss_openstack_cert} |
OSS CIS certificate |
OSS CIS jobs repository | oss_cis_jobs_repository: https://github.com/Mirantis/rundeck-cis-jobs.git |
CIS jobs repository |
OSS CIS jobs repository branch | oss_cis_jobs_repository_branch: master |
CIS jobs repository branch |
OSS Security Audit username | oss_security_audit_username: ${_param:oss_openstack_username} |
Security audit service username |
OSS Security Audit password | oss_security_audit_password: ${_param:oss_openstack_password} |
Security Audit service password |
OSS Security Audit auth URL | name: oss_security_audit_os_auth_url: ${_param:oss_openstack_auth_url} |
Security Audit service authentication URL |
OSS Security Audit project | oss_security_audit_project: ${_param:oss_openstack_project} |
Security Audit project name |
OSS Security Audit user domain ID | oss_security_audit_user_domain_id: ${_param:oss_openstack_domain_id} |
Security Audit user domain ID |
OSS Security Audit project domain ID | oss_security_audit_project_domain_id: ${_param:oss_openstack_domain_id} |
Security Audit project domain ID |
OSS Security Audit OpenStack credentials path | oss_security_audit_os_credentials_path: ${_param:oss_openstack_credentials_path} |
Path to credentials for OpenStack cloud for the Security Audit service |
OSS Cleanup service Openstack credentials path | oss_cleanup_service_os_credentials_path: ${_param:oss_openstack_credentials_path} |
Path to credentials for OpenStack cloud for the Cleanup service |
OSS Cleanup service username | oss_cleanup_username: ${_param:oss_openstack_username} |
Cleanup service username |
OSS Cleanup service password | oss_cleanup_password: ${_param:oss_openstack_password} |
Cleanup service password |
OSS Cleanup service auth URL | oss_cleanup_service_os_auth_url: ${_param:oss_openstack_auth_url} |
Cleanup service authentication URL |
OSS Cleanup service project | oss_cleanup_project: ${_param:oss_openstack_project} |
Cleanup service project name |
OSS Cleanup service project domain ID | oss_cleanup_project_domain_id: ${_param:oss_openstack_domain_id} |
Cleanup service project domain ID |
Section | Default JSON output | Description |
---|---|---|
OpenContrail analytics address | opencontrail_analytics_address: 10.0.1.30 |
The virtual IP address of the OpenContrail analytics cluster |
OpenContrail analytics hostname | opencontrail_analytics_hostname: nal |
The hostname of the OpenContrail analytics cluster |
OpenContrail analytics node01 address |
opencontrail_analytics_node01_address: 10.0.1.31 |
The virtual IP address of the first OpenContrail analytics node on the control network |
OpenContrail analytics node01 hostname |
opencontrail_analytics_node01_hostname: nal01 |
The hostname of the first OpenContrail analytics node on the control network |
OpenContrail analytics node02 address |
opencontrail_analytics_node02_address: 10.0.1.32 |
The virtual IP address of the second OpenContrail analytics node on the control network |
OpenContrail analytics node02 hostname |
opencontrail_analytics_node02_hostname: nal02 |
The hostname of the second OpenContrail analytics node on the control network |
OpenContrail analytics node03 address |
opencontrail_analytics_node03_address: 10.0.1.33 |
The virtual IP address of the third OpenContrail analytics node on the control network |
OpenContrail analytics node03 hostname |
opencontrail_analytics_node03_hostname: nal03 |
The hostname of the second OpenContrail analytics node on the control network |
OpenContrail control address | opencontrail_control_address: 10.0.1.20 |
The virtual IP address of the OpenContrail control cluster |
OpenContrail control hostname | opencontrail_control_hostname: ntw |
The hostname of the OpenContrail control cluster |
OpenContrail control node01 address |
opencontrail_control_node01_address: 10.0.1.21 |
The virtual IP address of the first OpenContrail control node on the control network |
OpenContrail control node01 hostname |
opencontrail_control_node01_hostname: ntw01 |
The hostname of the first OpenContrail control node on the control network |
OpenContrail control node02 address |
opencontrail_control_node02_address: 10.0.1.22 |
The virtual IP address of the second OpenContrail control node on the control network |
OpenContrail control node02 hostname |
opencontrail_control_node02_hostname: ntw02 |
The hostname of the second OpenContrail control node on the control network |
OpenContrail control node03 address |
opencontrail_control_node03_address: 10.0.1.23 |
The virtual IP address of the third OpenContrail control node on the control network |
OpenContrail control node03 hostname |
opencontrail_control_node03_hostname: ntw03 |
The hostname of the third OpenContrail control node on the control network |
OpenContrail router01 address |
opencontrail_router01_address: 10.0.1.100 |
The IP address of the first OpenContrail gateway router for BGP |
OpenContrail router01 hostname |
opencontrail_router01_hostname: rtr01 |
The hostname of the first OpenContrail gateway router for BGP |
OpenContrail router02 address |
opencontrail_router02_address: 10.0.1.101 |
The IP address of the second OpenContrail gateway router for BGP |
OpenContrail router02 hostname |
opencontrail_router02_hostname: rtr02 |
The hostname of the second OpenContrail gateway router for BGP |
Section | Default JSON output | Description |
---|---|---|
Compute primary first NIC | compute_primary_first_nic: eth1 |
The first NIC in the OpenStack compute bond |
Compute primary second NIC | compute_primary_second_nic: eth2 |
The second NIC in the OpenStack compute bond |
Compute bond mode | compute_bond_mode: active-backup |
The bond mode for the compute nodes |
OpenStack compute rack01 hostname |
openstack_compute_rack01_hostname: cmp |
The compute hostname prefix |
OpenStack compute rack01 single subnet |
openstack_compute_rack01_single_subnet: 10.0.0.1 |
The Control plane network prefix for compute nodes |
OpenStack compute rack01 tenant subnet |
openstack_compute_rack01_tenant_subnet: 10.0.2 |
The data plane netwrok prefix for compute nodes |
OpenStack control address | openstack_control_address: 10.0.1.10 |
The virtual IP address of the control cluster on the control network |
OpenStack control hostname | openstack_control_hostname: ctl |
The hostname of the VIP control cluster |
OpenStack control node01 address |
openstack_control_node01_address: 10.0.1.11 |
The IP address of the first control node on the control network |
OpenStack control node01 hostname |
openstack_control_node01_hostname: ctl01 |
The hostname of the first control node |
OpenStack control node02 address |
openstack_control_node02_address: 10.0.1.12 |
The IP address of the second control node on the control network |
OpenStack control node02 hostname |
openstack_control_node02_hostname: ctl02 |
The hostname of the second control node |
OpenStack control node03 address |
openstack_control_node03_address: 10.0.1.13 |
The IP address of the third control node on the control network |
OpenStack control node03 hostname |
openstack_control_node03_hostname: ctl03 |
The hostname of the third control node |
OpenStack database address | openstack_database_address: 10.0.1.50 |
The virtual IP address of the database cluster on the control network |
OpenStack database hostname | openstack_database_hostname: dbs |
The hostname of the VIP database cluster |
OpenStack database node01 address |
openstack_database_node01_address: 10.0.1.51 |
The IP address of the first database node on the control network |
OpenStack database node01 hostname |
openstack_database_node01_hostname: dbs01 |
The hostname of the first database node |
OpenStack database node02 address |
openstack_database_node02_address: 10.0.1.52 |
The IP address of the second database node on the control network |
OpenStack database node02 hostname |
openstack_database_node02_hostname: dbs02 |
The hostname of the second database node |
OpenStack database node03 address |
openstack_database_node03_address: 10.0.1.53 |
The IP address of the third database node on the control network |
OpenStack database node03 hostname |
openstack_database_node03_hostname: dbs03 |
The hostname of the third database node |
OpenStack message queue address | openstack_message_queue_address: 10.0.1.40 |
The vitrual IP address of the message queue cluster on the control network |
OpenStack message queue hostname | openstack_message_queue_hostname: msg |
The hostname of the VIP message queue cluster |
OpenStack message queue node01 address |
openstack_message_queue_node01_address: 10.0.1.41 |
The IP address of the first message queue node on the control network |
OpenStack message queue node01 hostname |
openstack_message_queue_node01_hostname: msg01 |
The hostname of the first message queue node |
OpenStack message queue node02 address |
openstack_message_queue_node02_address: 10.0.1.42 |
The IP address of the second message queue node on the control network |
OpenStack message queue node02 hostname |
openstack_message_queue_node02_hostname: msg02 |
The hostname of the second message queue node |
OpenStack message queue node03 address |
openstack_message_queue_node03_address: 10.0.1.43 |
The IP address of the third message wueue node on the control network |
OpenStack message queue node03 hostname |
openstack_message_queue_node03_hostname: msg03 |
The hostname of the third message queue node |
OpenStack benchmark node01 address |
openstack_benchmark_node01_address: 10.0.1.95 |
The IP address of a benchmark node on the control network |
OpenStack benchmark node01 hostname | openstack_benchmark_node01_hostname: bmk01 |
The hostname of a becnhmark node |
Openstack octavia enabled | False |
Enable the Octavia Load Balancing-as-a-Service for OpenStack. Requires OVS OpenStack to be enabled as a networking engine in Infrastructure related parameters. |
OpenStack proxy address | openstack_proxy_address: 10.0.1.80 |
The virtual IP address of a proxy cluster on the control network |
OpenStack proxy hostname | openstack_proxy_hostname: prx |
The hostname of the VIP proxy cluster |
OpenStack proxy node01 address |
openstack_proxy_node01_address: 10.0.1.81 |
The IP address of the first proxy node on the control network |
OpenStack proxy node01 hostname |
openstack_proxy_node01_hostname: prx01 |
The hostname of the first proxy node |
OpenStack proxy node02 address |
openstack_proxy_node02_address: 10.0.1.82 |
The IP address of the second proxy node on the control network |
OpenStack proxy node02 hostname |
openstack_proxy_node02_hostname: prx02 |
The hostname of the second proxy node |
OpenStack version | openstack_version: pike |
The version of OpenStack to be deployed |
Manila enabled | False |
Enable the Manila OpenStack Shared File Systems service |
Manila share backend | LVM |
Enable the LVM Manila share backend |
Manila lvm volume name | manila-volume |
The Manila LVM volume name |
Manila lvm devices | /dev/sdb,/dev/sdc |
The comma-separated paths to the Manila LVM devices |
Ironic enabled | false |
Enable OpenStack Ironic. For the deployment details, see Deploy Ironic. |
Tenant Telemetry enabled | false |
Enable Tenant Telemetry based on Ceilometer, Aodh, Panko, and Gnocchi.
Disabled by default. If enabled, you can select the Gnocchi aggregation
storage type for metrics: Tenant Telemetry does not support integration with StackLight LMA. |
Gnocchi aggregation storage | gnocchi_aggregation_storage: file |
Storage for aggregated metrics |
Designate enabled | designate_enabled: 'False' |
Enables OpenStack DNSaaS based on Designate |
Designate backend | designate_backend: powerdns |
The DNS backend for Designate |
OpenStack internal protocol | openstack_internal_protocol: http |
The protocol on internal OpenStack endpoints |
Section | Default JSON output | Description |
---|---|---|
Calico enable nat |
calico_enable_nat: 'True' |
If selected, NAT will be enabled for Calico |
Calico netmask | 16 |
The netmask of the Calico network |
Calico network | 192.168.0.0 |
The network that is used for the Kubernetes containers |
etcd SSL | etcd_ssl: 'True' |
If selected, the SSL for etcd will be enabled |
Kubernetes virtlet enabled | False |
Optional. Virtlet enables Kubernetes to run virtual machines. For the enablement details, see Enable Virtlet. Virtlet with OpenContrail is available as technical preview. Use such configuration for testing and evaluation purposes only. |
Kubernetes externaldns enabled | False |
If selected, ExternalDNS will be deployed. For details, see: Deploy ExternalDNS for Kubernetes. |
Kubernetes metrics server enabled | False |
If selected, the metrics-server add-on will be deployed to enable
horizontal pod autoscaling.
For details, see: Enable horizontal pod autoscaling. |
Kubernetes rbd monitors | 10.0.1.66:6789,10.0.1.67:6789,10.0.1.68:6789 |
A comma-separated list of the Ceph RADOS Block Device (RBD) monitors in a Ceph cluster that will be connected to Kubernetes. This parameter becomes available if you select the Kubernetes rbd enabled option in the Infrastructure parameters section. |
Kubernetes rbd pool | kubernetes |
A pool in a Ceph cluster that will be connected to Kubernetes. This parameter becomes available if you select the Kubernetes rbd enabled option in the Infrastructure parameters section. |
Kubernetes rbd user id | kubernetes |
A Ceph RBD user ID of a Ceph cluster that will be connected to Kubernetes. This parameter becomes available if you select the Kubernetes rbd enabled option in the Infrastructure parameters section. |
Kubernetes rbd user key | kubernetes_key |
A Ceph RBD user key of a Ceph cluster that will be connected to Kubernetes. This parameter becomes available if you select the Kubernetes rbd enabled option in the Infrastructure parameters section. |
Kubernetes compute node01 hostname |
cmp01 |
The hostname of the first Kubernetes compute node |
Kubernetes compute node01 deploy address | 10.0.0.101 |
The IP address of the first Kubernetes compute node |
Kubernetes compute node01 single address |
10.0.1.101 |
The IP address of the first Kubernetes compute node on the Control plane |
Kubernetes compute node01 tenant address |
10.0.2.101 |
The tenant IP address of the first Kubernetes compute node |
Kubernetes compute node02 hostname |
cmp02 |
The hostname of the second Kubernetes compute node |
Kubernetes compute node02 deploy address |
10.0.0.102 |
The IP address of the second Kubernetes compute node on the deploy network |
Kubernetes compute node02 single address |
10.0.1.102 |
The IP address of the second Kubernetes compute node on the control plane |
Kubernetes control address | 10.0.1.10 |
The Keepalived VIP of the Kubernetes control nodes |
Kubernetes control node01 address |
10.0.1.11 |
The IP address of the first Kubernetes controller node |
Kubernetes control node01 deploy address |
10.0.0.11 |
The IP address of the first Kubernetes control node on the deploy network |
Kubernetes control node01 hostname | ctl01 |
The hostname of the first Kubernetes controller node |
Kubernetes control node01 tenant address |
10.0.2.11 |
The tenant IP address of the first Kubernetes controller node |
Kubernetes control node02 address |
10.0.1.12 |
The IP address of the second Kubernetes controller node |
Kubernetes control node02 deploy address |
10.0.0.12 |
The IP address of the second Kubernetes control node on the deploy network |
Kubernetes control node02 hostname |
ctl02 |
The hostname of the second Kubernetes controller node |
Kubernetes control node02 tenant address |
10.0.2.12 |
The tenant IP address of the second Kubernetes controller node |
Kubernetes control node03 address |
10.0.1.13 |
The IP address of the third Kubernetes controller node |
Kubernetes control node03 tenant address |
10.0.2.13 |
The tenant IP address of the third Kubernetes controller node |
Kubernetes control node03 deploy address |
10.0.0.13 |
The IP address of the third Kubernetes control node on the deploy network |
Kubernetes control node03 hostname |
ctl03 |
The hostname of the third Kubernetes controller node |
OpenContrail public ip range | 10.151.0.0/16 |
The public floating IP pool for OpenContrail |
Opencontrail private ip range | 10.150.0.0/16 |
The range of private OpenContrail IPs used for pods |
Kubernetes keepalived vip interface | ens4 |
The Kubernetes interface used for the Keepalived VIP |
Section | Default JSON output | Description |
---|---|---|
StackLight LMA log address | stacklight_log_address: 10.167.4.60 |
The virtual IP address of the StackLight LMA logging cluster |
StackLight LMA log hostname | stacklight_log_hostname: log |
The hostname of the StackLight LMA logging cluster |
StackLight LMA log node01 address |
stacklight_log_node01_address: 10.167.4.61 |
The IP address of the first StackLight LMA logging node |
StackLight LMA log node01 hostname |
stacklight_log_node01_hostname: log01 |
The hostname of the first StackLight LMA logging node |
StackLight LMA log node02 address |
stacklight_log_node02_address: 10.167.4.62 |
The IP address of the second StackLight LMA logging node |
StackLight LMA log node02 hostname |
stacklight_log_node02_hostname: log02 |
The hostname of the second StackLight LMA logging node |
StackLight LMA log node03 address |
stacklight_log_node03_address: 10.167.4.63 |
The IP address of the third StackLight LMA logging node |
StackLight LMA log node03 hostname |
stacklight_log_node03_hostname: log03 |
The hostname of the third StackLight LMA logging node |
StackLight LMA monitor address | stacklight_monitor_address: 10.167.4.70 |
The virtual IP address of the StackLight LMA monitoring cluster |
StackLight LMA monitor hostname | stacklight_monitor_hostname: mon |
The hostname of the StackLight LMA monitoring cluster |
StackLight LMA monitor node01 address |
stacklight_monitor_node01_address: 10.167.4.71 |
The IP address of the first StackLight LMA monitoring node |
StackLight LMA monitor node01 hostname |
stacklight_monitor_node01_hostname: mon01 |
The hostname of the first StackLight LMA monitoring node |
StackLight LMA monitor node02 address |
stacklight_monitor_node02_address: 10.167.4.72 |
The IP address of the second StackLight LMA monitoring node |
StackLight LMA monitor node02 hostname |
stacklight_monitor_node02_hostname: mon02 |
The hostname of the second StackLight LMA monitoring node |
StackLight LMA monitor node03 address |
stacklight_monitor_node03_address: 10.167.4.73 |
The IP address of the third StackLight LMA monitoring node |
StackLight LMA monitor node03 hostname |
stacklight_monitor_node03_hostname: mon03 |
The hostname of the third StackLight LMA monitoring node |
StackLight LMA telemetry address | stacklight_telemetry_address: 10.167.4.85 |
The virtual IP address of a StackLight LMA telemetry cluster |
StackLight LMA telemetry hostname | stacklight_telemetry_hostname: mtr |
The hostname of a StackLight LMA telemetry cluster |
StackLight LMA telemetry node01 address |
stacklight_telemetry_node01_address: 10.167.4.86 |
The IP address of the first StackLight LMA telemetry node |
StackLight LMA telemetry node01 hostname |
stacklight_telemetry_node01_hostname: mtr01 |
The hostname of the first StackLight LMA telemetry node |
StackLight LMA telemetry node02 address |
stacklight_telemetry_node02_address: 10.167.4.87 |
The IP address of the second StackLight LMA telemetry node |
StackLight LMA telemetry node02 hostname |
stacklight_telemetry_node02_hostname: mtr02 |
The hostname of the second StackLight LMA telemetry node |
StackLight LMA telemetry node03 address | stacklight_telemetry_node03_address: 10.167.4.88 |
The IP address of the third StackLight LMA telemetry node |
StackLight LMA telemetry node03 hostname | stacklight_telemetry_node03_hostname: mtr03 |
The hostname of the third StackLight LMA telemetry node |
Long-term storage type | stacklight_long_term_storage_type: prometheus |
The type of the long-term storage Warning InfluxDB, including InfluxDB Relay and remote storage adapter, is deprecated in the Q4`18 MCP release and will be removed in the next release. |
OSS webhook login ID | oss_webhook_login_id: 13 |
The webhook login ID for alerts notifications |
OSS webhook app ID | oss_webhook_app_id: 24 |
The webhook application ID for alerts notifications |
Gainsight account ID | N/A | The customer account ID in Salesforce |
Gainsight application organization ID | N/A | Mirantis organization ID in Salesforce |
Gainsight access key | N/A | The access key for the Salesforce Gainsight service |
Gainsight CSV upload URL | N/A | The URL to Gainsight API |
Gainsight environment ID | N/A | The customer environment ID in Salesforce |
Gainsight job ID | N/A | The job ID for the Salesforce Gainsight service |
Gainsight login | N/A | The login for the Salesforce Gainsight service |
Section | Default JSON output | Description |
---|---|---|
Ceph RGW address | ceph_rgw_address: 172.16.47.75 |
The IP address of the Ceph RGW storage cluster |
Ceph RGW hostname | ceph_rgw_hostname: rgw |
The hostname of the Ceph RGW storage cluster |
Ceph MON node01 address |
ceph_mon_node01_address: 172.16.47.66 |
The IP address of the first Ceph MON storage node |
Ceph MON node01 hostname |
ceph_mon_node01_hostname: cmn01 |
The hostname of the first Ceph MON storage node |
Ceph MON node02 address |
ceph_mon_node02_address: 172.16.47.67 |
The IP address of the second Ceph MON storage node |
Ceph MON node02 hostname |
ceph_mon_node02_hostname: cmn02 |
The hostname of the second Ceph MON storage node |
Ceph MON node03 address |
ceph_mon_node03_address: 172.16.47.68 |
The IP address of the third Ceph MON storage node |
Ceph MON node03 hostname |
ceph_mon_node03_hostname: cmn03 |
The hostname of the third Ceph MON storage node |
Ceph RGW node01 address |
ceph_rgw_node01_address: 172.16.47.76 |
The IP address of the first Ceph RGW node |
Ceph RGW node01 hostname |
ceph_rgw_node01_hostname: rgw01 |
The hostname of the first Ceph RGW storage node |
Ceph RGW node02 address |
ceph_rgw_node02_address: 172.16.47.77 |
The IP address of the second Ceph RGW storage node |
Ceph RGW node02 hostname |
ceph_rgw_node02_hostname: rgw02 |
The hostname of the second Ceph RGW storage node |
Ceph RGW node03 address |
ceph_rgw_node03_address: 172.16.47.78 |
The IP address of the third Ceph RGW storage node |
Ceph RGW node03 hostname |
ceph_rgw_node03_hostname: rgw03 |
The hostname of the third Ceph RGW storage node |
Ceph OSD node count | ceph_osd_node_count: 3 |
The number of OSD hosts |
OSD padding with zeros | osd_padding_with_zeros: 'True' |
Enables padding with zeros when generating Ceph OSD host names. For
example, name the node as osd001 if enabled, otherwise, osd1 |
Ceph OSD count | ceph_osd_count: 10 |
The number of OSDs |
Ceph OSD rack01 hostname |
ceph_osd_rack01_hostname: osd |
The OSD rack01 hostname |
Ceph OSD single address ranges | ceph_osd_single_address_ranges |
The control plane network ranges for Ceph OSDs. A comma-separated list
of IP ranges, for example,
172.16.10.101-172.16.10.200,172.16.20.101-172.16.20.200 |
Ceph OSD backend address ranges | ceph_osd_backend_address_ranges |
The cluster network ranges for Ceph OSDs, used to replicate the OSDs
data. A comma-separated list of IP ranges, for example,
172.16.10.101-172.16.10.200,172.16.20.101-172.16.20.200 |
Ceph OSD deploy address ranges | ceph_osd_deploy_address_ranges |
The deploy network ranges for Ceph OSDs. A comma-separated list of IP
ranges, for example,
172.16.10.101-172.16.10.200,172.16.20.101-172.16.20.200 |
Ceph OSD rack01 single subnet |
ceph_osd_rack01_single_subnet: 172.16.47 |
The control plane network prefix for Ceph OSDs |
Ceph OSD rack01 backend subnet |
ceph_osd_rack01_backend_subnet: 172.16.48 |
The deploy network prefix for Ceph OSDs |
Ceph public network | ceph_public_network: 172.16.47.0/24 |
The IP address of Ceph public network with the network mask |
Ceph cluster network | ceph_cluster_network: 172.16.48.70/24 |
The IP address of Ceph cluster network with the network mask |
Ceph OSD block DB size | ceph_osd_block_db_size: 20 |
The Ceph OSD block DB size in GB |
Ceph OSD primary first NIC | ceph_osd_primary_first_nic: eth1 |
The first NIC of Ceph OSD bond used for Ceph communication |
Ceph OSD primary second NIC | ceph_osd_primary_second_nic: eth2 |
The second NIC of Ceph OSD bond used for Ceph communication |
Ceph OSD bond mode | ceph_osd_bond_mode: active-backup |
The bonding mode for Ceph OSD communication |
Ceph OSD data disks | ceph_osd_data_disks: /dev/vdd,/dev/vde |
The list of OSD data disks |
Ceph OSD journal or block DB disks | ceph_osd_journal_or_block_db_disks: /dev/vdb,/dev/vdc |
The list of journal or block disks |