The cloud-init automatically configures NetMRI and Sandbox virtual appliances with user-defined parameters. Currently, automatic configuration is possible for deployments of OpenStack, Proxmox, and AWS. YAML and XML formats are supported for cloud-init configurations, but only the most essential cloud-init configuration fields are supported. For details about the valid fields for each option, refer to the Configuring Network Interfaces section.
You can pass the configuration file to the NetMRI VM in different ways when setting up a NetMRI instance in OpenStack. The file format depends on the way chosen. These ways include the following:
Using direct text input or upload of the configuration file accessible via network. The text or file must use the YAML format. This method is enabled by default cluster-wide in an OpenStack environment, although there may be some distributions that disable it.
Using the Configuration Drive (i.e., virtual CD-ROM). You provide the configuration file as described above and specify an additional Configuration Drive option. The file is automatically placed in an ISO image that appears to the VM as a CDROM drive.
Using the OVF transport method. The configuration file must be an XML file of the OVF schema type, encoded in the Base 64 encoding. For more information, see Using OVF Transport Method of Passing Configuration File to NetMRI VM Instance.
The following are examples of configuration file content formatted using YAML:
#infoblox-config
default_admin_password: "admin_password"
server_name: your_server_name
role: standalone
db_name: your_db_name
dns:
dns_server_1: dns.fqdn.com
dns_search_1: dns_search_string_1
mgmt_port:
v4_addr: mgmt_port_IP_address
v4_netmask: net_mask
v4_gw: gateway_IP_address
v6_addr: v6_address
v6_prefix: 64
v6_gw: v6_address
scan_port:
v4_addr: scan_port_IP_address
v4_netmask: net_mask
v4_gw: gateway_IP_address
v6_addr: v6_address
v6_prefix: 64
v6_gw: v6_address
time:
server_1: timeserver_IP_address
region: your_region
zone: your_city
Below is an example of the configuration file content in the XML format:
<?xml version="1.0" encoding="UTF-8"?>
<Environment xmlns="http://schemas.dmtf.org/ovf/environment/1"
xmlns:oe="http://schemas.dmtf.org/ovf/environment/1">
<PropertySection>
<Property oe:key="user-data"
oe:value="I2luZm9ibG94LWNvbmZpZwpkZWZhdWx0X2FkbWluX3Bhc3N3b3JkOiAiYWRtaW5fcGFzc3dvcmQiCnNlcnZlcl9uYW1lOiB5b3VyX3NlcnZlcl9uYW1lCnJvbGU6IHN0YW5kYWxvbmUKZGJfbmFtZTogeW91cl9kYl9uYW1lCmRuczoKICBkbnNfc2VydmVyXzE6IGRucy5mcWRuLmNvbQogIGRuc19zZWFyY2hfMTogZG5zX3NlYXJjaF9zdHJpbmdfMQptZ210X3BvcnQ6CiAgdjRfYWRkcjogbWdtdF9wb3J0X0lQdjRfYWRkcmVzcwogIHY0X25ldG1hc2s6IG1nbXRfcG9ydF9uZXRtYXNrCiAgdjRfZ3c6IG1nbXRfSVB2Nl9nYXRld2F5X2FkZHJlc3MKICB2Nl9hZGRyOiBtZ210X3BvcnRfSVB2Nl9hZGRyZXNzCiAgdjZfcHJlZml4OiBtZ210X3BvcnRfSVB2Nl9wcmVmaXgKICB2Nl9ndzogc2Nhbl9JUHY0X2dhdGV3YXlfYWRkcmVzcwpzY2FuX3BvcnQ6CiAgdjRfYWRkcjogc2Nhbl9wb3J0X0lQdjRfYWRkcmVzcwogIHY0X25ldG1hc2s6IHNjYW5fcG9ydF9uZXRtYXNrCiAgdjRfZ3c6IHNjYW5fSVB2NF9nYXRld2F5X2FkZHJlc3MKICB2Nl9hZGRyOiBzY2FuX3BvcnRfSVB2Nl9hZGRyZXNzCiAgdjZfcHJlZml4OiBzY2FuX3BvcnRfSVB2Nl9wcmVmaXgKICB2Nl9ndzogc2Nhbl9JUHY2X2dhdGV3YXlfYWRkcmVzcwp0aW1lOgogIHNlcnZlcl8xOiB0aW1lc2VydmVyX0lQX2FkZHJlc3MKICByZWdpb246IHlvdXJfcmVnaW9uCiAgem9uZTogeW91cl9jaXR5"/>
</PropertySection>
</Environment>
Note
The value of the user-data key here is of the same format as the configuration above but encoded in the Base64 encoding.