CORD : VTN Configuration Guide

This page describes network configurations consumed by the VTN application with an example of two compute nodes setup depicted in the figure below. In the example, compute-02 has an additional bridge br-mgmt which connects the management network and the br-int, so that a virtual instance running in this node has an ability to access the management network directly if needed. The latest sample config file can be downloaded from here.

Sample network-cfg.json

 {
    "apps" : {
        "org.opencord.vtn" : {
            "cordvtn" : {
                "publicGateways" : [
                    {
                        "gatewayIp" : "10.6.1.193",
                        "gatewayMac" : "02:42:0a:06:01:01"
                    }
                ],
                "localManagementIp" : "172.27.0.1/24",
                "ovsdbPort" : "6640",
                "ssh" : {
                    "sshPort" : "22",
                    "sshUser" : "root",
                    "sshKeyFile" : "/root/node_key"
                },
                "nodes" : [
                    {
                        "hostname" : "compute-01",
                        "hostManagementIp" : "10.90.0.64/24",
                        "dataPlaneIp" : "192.168.199.1/24",
                        "dataPlaneIntf" : "mlx0",
                        "bridgeId" : "of:0000000000000001"
                     },
                     {
                        "hostname" : "compute-02",
                        "hostManagementIp" : "10.90.0.65/24",
                        "hostManagementIface" : "veth1",
                        "dataPlaneIp" : "192.168.199.2/24",
                        "dataPlaneIntf" : "mlx0",
                        "bridgeId" : "of:0000000000000002"
                     }
                ]
            }
        }
    }
}

Public gateways

               "publicGateways" : [
                    {
                        "gatewayIp" : "10.6.1.193",
                        "gatewayMac" : "02:42:0a:06:01:01"
                    }
                ],

publicGateways: Public subnet gateway IP address and MAC address, which are managed by vRouter. This information is required for VTN to proxy ARP request.

SSH credentials

               "ssh" : {
                    "sshPort" : "22",
                    "sshUser" : "root",
                    "sshKeyFile" : "/root/node_key"
                },

ssh: SSH access information. VTN uses SSH exec channel to configure network interfaces on the compute nodes. It assumes that the supplied key pair is added to the authorized_keys on compute nodes, so that the head node can SSH to compute nodes without password.
sshPort: SSH port.
sshUser: User with the authorized key.
sshKeyFile: The location of the SSH private key.

OVSDB port

"ovsdbPort" : "6640",

ovsdbPort: OVSDB server listen port. During the compute node bootstrap, VTN tries to connect to the OVSDB server on the compute nodes to configure OVS. OVSDB server needs to be set to passive mode and listen to this port number for the client session.

Local management IP

"localManagementIp" : "172.27.0.1/24",

localManagementIp: Local management network gateway IP address in CIDR notation. This IP address is to be assigned to the br-int and also used when you create a MANAGEMENT_LOCAL type network, which enables for the virtual instance to be accessed from the host machine. Refer to here for how to use local management network.

Compute nodes

               "nodes" : [
                    {
                        "hostname" : "compute-01",
                        "hostManagementIp" : "10.90.0.64/24",
                        "dataPlaneIp" : "192.168.199.1/24",
                        "dataPlaneIntf" : "mlx0",
                        "bridgeId" : "of:0000000000000001"
                     },
                    {
                        "hostname" : "compute-02",
                        "hostManagementIp" : "10.90.0.65/24",
                        "hostManagementIface" : "veth1",
                        "dataPlaneIp" : "192.168.199.2/24",
                        "dataPlaneIntf" : "mlx0",
                        "bridgeId" : "of:0000000000000002"
                     }
                ]

nodes: Information of compute nodes. Used for node bootstrapping.
hostname: The unique hostname of the compute node.
hostManagementIp: Management network IP address.
hostManagementIface(optional): Interface name connected to the management network. Note that VTN does not create br-mgmt bridge nor veth pair for you.
dataPlaneIp: Data network IP address.
dataPlaneIntf: Data network interface name.
bridgeId: The unique device ID of the integration bridge.