The cloud-init automatically configures NetMRI and Sandbox virtual appliances with user-defined parameters. Currently, automatic configuration is possible for deployments of OpenStack 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.

When setting up a NetMRI instance in OpenStack, you can pass the configuration file to the NetMRI VM in various methods. The file format is dependent on the method selected. These methods consist of the following:

YAML Format Examples

The following are examples of YAML-formatted configuration file content from the NetMRI and Sandbox configurations:

Configuring NetMRI with a Static IP Address for the MGMT Interface

#infoblox-config

default_admin_password: "admin_password"

server_name: test-vm

db_name: this_test_db

mgmt_port:

    v4_addr: 192.168.1.10

    v4_netmask: 255.255.255.0

    v4_gw: 192.168.1.1

    v6_addr: 2002::10

    v6_prefix: 64

    v6_gw: 2002::1

    primary_dns_server: 192.168.1.1

    secondary_dns_server: 2002::1

    search_domains:

        - mgmt.domain

        - mgmt.local

scan_port:

    v4_addr: 192.168.2.10

    v4_netmask: 255.255.255.0

    v4_gw: 192.168.2.1

    v6_addr: 2003::10

    v6_prefix: 64

    v6_gw: 2003::1

    primary_dns_server: 192.168.2.1

    secondary_dns_server: 2003::1

    search_domains:

        - scan.domain

        - scan.local

time:

    server_1: time.local

    timezone: Etc/UTC

Configuring MGMT Interface IP for NetMRI using DHCP

#infoblox-config

default_admin_password: "admin_password"

server_name: test-vm

db_name: this_test_db

mgmt_port:

    v4_use_dhcp: true

    v6_use_dhcp: true

    primary_dns_server: 192.168.1.1

    secondary_dns_server: 2002::1

    search_domains:

        - mgmt.domain

        - mgmt.local

scan_port:

    v4_addr: 192.168.2.10

    v4_netmask: 255.255.255.0

    v4_gw: 192.168.2.1

    v6_addr: 2003::10

    v6_prefix: 64

    v6_gw: 2003::1

    primary_dns_server: 192.168.2.1

    secondary_dns_server: 2003::1

    search_domains:

        - scan.domain

        - scan.local

time:

    server_1: time.local

    timezone:Etc/UTC

Configuring Sandbox with a Static IP Address for the MGMT Interface

#infoblox-config

default_admin_password: "admin_password"

server_name: test-vm

mgmt_port:

    v4_addr: 192.168.1.10

    v4_netmask: 255.255.255.0

    v4_gw: 192.168.1.1

    v6_addr: 2002::10

    v6_prefix: 64

    v6_gw: 2002::1

    primary_dns_server: 192.168.1.1

    secondary_dns_server: 2002::1

    search_domains:

        - mgmt.domain

        - mgmt.local

time:

    server_1: time.local

    timezone: Etc/UTC

Configuring DHCP IP for MGMT Interface in a Sandbox

#infoblox-config

default_admin_password: "admin_password"

server_name: test-vm

mgmt_port:

mgmt_port:

    v4_use_dhcp: true

    v6_use_dhcp: true

    primary_dns_server: 192.168.1.1

    secondary_dns_server: 2002::1

    search_domains:

        - mgmt.domain

        - mgmt.local

time:

    server_1: time.local

    timezone:Etc/UTC

XML Format Example

The following is an example of XML-formatted configuration file content:

<?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 Base64 encoding.