To use this example file, paste the text below into a text editor and save with a .yaml file extension.
msw-deployment:deployment:
sites:
- name: <SITE_NAME>
site-parameters:
deployment-id: <DEPLOYMENT_ID>
fixed-ips: true
mdm-certificate-id: <MDM CERTIFICATE>
networking:
subnets:
- cidr: <MGMT_CIDR>
default-gateway: <MGMT_DEFAULT_GW>
dns-servers:
- <LIST_OF_DNS_SERVER_IP_ADDRESSES>
identifier: <MGMT_IDENTIFIER>
vim-network: <MGMT_NETWORK_NAME>
- cidr: <SIG_CIDR>
default-gateway: <SIG_DEFAULT_GW>
identifier: <SIG_IDENTIFIER>
vim-network: <SIG_NETWORK_NAME>
# The 2nd and 3rd signaling subnets are optional and for MCP only.
# MCP can be deployed with 1-3 signaling subnets to split signaling traffic as required.
- cidr: <SIG2_CIDR>
default-gateway: <SIG2_DEFAULT_GW>
identifier: <SIG2_IDENTIFIER>
vim-network: <SIG2_NETWORK_NAME>
- cidr: <SIG3_CIDR>
default-gateway: <SIG3_DEFAULT_GW>
identifier: <SIG3_IDENTIFIER>
vim-network: <SIG3_NETWORK_NAME>
- cidr: <CLUSTER_CIDR>
# The cluster default-gateway attribute is optional and can be omitted.
default-gateway: <CLUSTER_DEFAULT_GW>
identifier: <CLUSTER_IDENTIFIER>
vim-network: <CLUSTER_NETWORK_NAME>
services:
ntp-servers:
- <NTP_SERVER_IP_ADDRESS_1>
- <NTP_SERVER_IP_ADDRESS_2>
site-id: DC1
timezone: <DEPLOYMENT_TIMEZONE>
vim-configuration:
vsphere:
connection:
allow-insecure: true
password-id: <VSPHERE_PASSWORD_ID>
server: <VSPHERE_SERVER_ADDRESS>
username: <VSPHERE_USERNAME>
datacenter: <VSPHERE_DATACENTER>
folder: ""
reserve-resources: false
resource-pool-name: <VSPHERE_RESOURCES>
vnfcs:
- cluster-configuration:
count: 3
instances:
- name: <DEPLOYMENT_ID>-mdm-1
ssh:
authorized-keys:
- ssh-rsa <PUBLIC_KEY_VALUE>
private-key-id: <PRIVATE_KEY_ID>
- name: <DEPLOYMENT_ID>-mdm-2
ssh:
authorized-keys:
- ssh-rsa <PUBLIC_KEY_VALUE>
private-key-id: <PRIVATE_KEY_ID>
- name: <DEPLOYMENT_ID>-mdm-3
ssh:
authorized-keys:
- ssh-rsa <PUBLIC_KEY_VALUE>
private-key-id: <PRIVATE_KEY_ID>
name: <DEPLOYMENT_ID>-mdm
networks:
- ip-addresses:
ip:
- <MDM_1_MGMT_IP_ADDRESS>
- <MDM_2_MGMT_IP_ADDRESS>
- <MDM_3_MGMT_IP_ADDRESS>
name: <VNFC_MGMT_NETWORK_NAME>
subnet: <MGMT_IDENTIFIER>
traffic-types:
- management
product-options:
mdm:
consul-token: <MDM_CONSUL_TOKEN>
custom-topology: |-
{
"member_groups": [
{
"group_name": "DNS",
"neighbors": []
},
{
"group_name": "RVT-tsn.DC1",
"neighbors": []
},
{
"group_name": "RVT-mcp.DC1",
"neighbors": []
}
]
}
type: mdm
version: <MDM_VERSION>
vim-configuration:
vsphere:
deployment-size: <VSPHERE_MDM_DEPLOYMENT_SIZE>
- cluster-configuration:
count: 3
instances:
- name: <DEPLOYMENT_ID>-tsn-1
ssh:
authorized-keys:
- ssh-rsa <PUBLIC_KEY_VALUE>
private-key-id: <PRIVATE_KEY_ID>
- name: <DEPLOYMENT_ID>-tsn-2
ssh:
authorized-keys:
- ssh-rsa <PUBLIC_KEY_VALUE>
private-key-id: <PRIVATE_KEY_ID>
- name: <DEPLOYMENT_ID>-tsn-3
ssh:
authorized-keys:
- ssh-rsa <PUBLIC_KEY_VALUE>
private-key-id: <PRIVATE_KEY_ID>
name: <DEPLOYMENT_ID>-tsn
networks:
- ip-addresses:
ip:
- <TSN_1_MGMT_IP_ADDRESS>
- <TSN_2_MGMT_IP_ADDRESS>
- <TSN_3_MGMT_IP_ADDRESS>
name: <VNFC_MGMT_NETWORK_NAME>
subnet: <MGMT_IDENTIFIER>
traffic-types:
- management
- ip-addresses:
ip:
- <TSN_1_INTERNAL_SIG_IP_ADDRESS>
- <TSN_2_INTERNAL_SIG_IP_ADDRESS>
- <TSN_3_INTERNAL_SIG_IP_ADDRESS>
name: <VNFC_INTERNAL_SIG_NETWORK_NAME>
subnet: <SIG_IDENTIFIER>
traffic-types:
- internal
product-options:
tsn:
cds-addresses:
- <TSN_1_INTERNAL_SIG_IP_ADDRESS>
- <TSN_2_INTERNAL_SIG_IP_ADDRESS>
- <TSN_3_INTERNAL_SIG_IP_ADDRESS>
primary-user-password-id: <PRIMARY_USER_PASSWORD_ID>
secrets-private-key-id: <SECRETS_PRIVATE_KEY_ID>
type: tsn
version: <TSN_VERSION>
vim-configuration:
vsphere:
deployment-size: <VSPHERE_TSN_DEPLOYMENT_SIZE>
- cluster-configuration:
count: 3
instances:
- name: <DEPLOYMENT_ID>-mcp-1
ssh:
authorized-keys:
- ssh-rsa <PUBLIC_KEY_VALUE>
private-key-id: <PRIVATE_KEY_ID>
- name: <DEPLOYMENT_ID>-mcp-2
ssh:
authorized-keys:
- ssh-rsa <PUBLIC_KEY_VALUE>
private-key-id: <PRIVATE_KEY_ID>
- name: <DEPLOYMENT_ID>-mcp-3
ssh:
authorized-keys:
- ssh-rsa <PUBLIC_KEY_VALUE>
private-key-id: <PRIVATE_KEY_ID>
name: <DEPLOYMENT_ID>-mcp
networks:
- ip-addresses:
ip:
- <MCP_1_MGMT_IP_ADDRESS>
- <MCP_2_MGMT_IP_ADDRESS>
- <MCP_3_MGMT_IP_ADDRESS>
name: <VNFC_MGMT_NETWORK_NAME>
subnet: <MGMT_IDENTIFIER>
traffic-types:
- management
# There are multiple allowed traffic schemes for MCP signalling traffic.
# This example is for full signalling traffic separation.
- ip-addresses:
ip:
- <MCP_1_INTERNAL_SIG_IP_ADDRESS>
- <MCP_2_INTERNAL_SIG_IP_ADDRESS>
- <MCP_3_INTERNAL_SIG_IP_ADDRESS>
name: <VNFC_INTERNAL_SIG_NETWORK_NAME>
subnet: <SIG_IDENTIFIER>
traffic-types:
- internal
- ip-addresses:
ip:
- <MCP_1_SIP_SIG_IP_ADDRESS>
- <MCP_2_SIP_SIG_IP_ADDRESS>
- <MCP_3_SIP_SIG_IP_ADDRESS>
name: <VNFC_SIP_SIG_NETWORK_NAME>
subnet: <SIG2_IDENTIFIER>
traffic-types:
- sip
- ip-addresses:
ip:
- <MCP_1_HTTP_SIG_IP_ADDRESS>
- <MCP_2_HTTP_SIG_IP_ADDRESS>
- <MCP_3_HTTP_SIG_IP_ADDRESS>
name: <VNFC_HTTP_SIG_NETWORK_NAME>
subnet: <SIG3_IDENTIFIER>
traffic-types:
- http
- ip-addresses:
ip:
- <MCP_1_CLUSTER_IP_ADDRESS>
- <MCP_2_CLUSTER_IP_ADDRESS>
- <MCP_3_CLUSTER_IP_ADDRESS>
name: <VNFC_CLUSTER_NETWORK_NAME>
subnet: <CLUSTER_IDENTIFIER>
traffic-types:
- cluster
product-options:
custom:
cds-addresses:
- <TSN_1_INTERNAL_SIG_IP_ADDRESS>
- <TSN_2_INTERNAL_SIG_IP_ADDRESS>
- <TSN_3_INTERNAL_SIG_IP_ADDRESS>
nodetool-password-id: <NOEDETOOL_PASSWORD_ID>
primary-user-password-id: <PRIMARY_USER_PASSWORD_ID>
secrets-private-key-id: <GENERATED_PRIVATE_KEY_ID>
type: mcp
version: <MCP_VERSION>
vim-configuration:
vsphere:
deployment-size: <VSPHERE_MCP_DEPLOYMENT_SIZE>