Configure Eucalyptus / Configure Network Modes |
This topic provides configuration instructions for Eucalyptus EDGE network mode. Eucalyptus requires network connectivity between its clients (end-users) and the cloud components (e.g., CC, CLC, and Walrus).
To configure Eucalyptus for EDGE mode, most networking configuration is handled through settings in a global Cloud Controller (CLC) property file.
The /etc/eucalyptus/eucalyptus.conf file contains some network-related options in the “Networking Configuration” section. These options use the prefix VNET_. The most commonly used VNET options are described in the following table.
The most commonly used VNET options are described in the following table.
Option | Description | Component |
---|---|---|
VNET_BRIDGE | This is the name of the bridge interface to which instances' network interfaces should attach. A physical interface that can reach the CC must be attached to this bridge. Common setting for KVM is br0. | Node Controller |
VNET_DHCPDAEMON | The ISC DHCP executable to use. This is set to a distro-dependent value by packaging. The internal default is /usr/sbin/dhcpd3. | Node Controller |
VNET_MODE | The networking mode in which to run. The same mode must be specified on all CCs and NCs
in your cloud. Valid values: EDGE |
All CCs and NCs |
VNET_PRIVINTERFACE | The name of the network interface that is on the same network as the NCs.
Default: eth0 |
Node Controller |
VNET_PUBINTERFACE | This is the name of the network interface
that is connected to the same network as the CC. Depending on the hypervisor's
configuration this may be a bridge or a physical interface that is attached to the
bridge.
Default: eth0 |
Node Controller |
You must edit eucalyptus.conf on the Cluster Controller (CC) and Node Controller (NC) hosts. You must also create a JSON file and upload it the Cloud Controller (CLC).
To configure the rest of the EDGE mode parameters, you must create a network.json configuration file. Later in the installation process you will Upload the Network JSON Configuration File to the CLC.
The following example is for a setup with one cluster (AZ), called PARTI00, with a flat network topology.
{ "InstanceDnsDomain": "eucalyptus.internal", "InstanceDnsServers": ["10.1.1.254"], "MacPrefix": "d0:0d", "PublicIps": [ "10.111.101.84", "10.111.101.91", "10.111.101.92", "10.111.101.93" ], "Subnets": [ ], "Clusters": [ { "Name": "PARTI00", "Subnet": { "Name": "10.111.0.0", "Subnet": "10.111.0.0", "Netmask": "255.255.0.0", "Gateway": "10.111.0.1" }, "PrivateIps": [ "10.111.101.94", "10.111.101.95" ] }, ] }
For a multi-cluster deployment, add an additional cluster to your configuration for each cluster you have. The following example has an two clusters, PARTI00 and PARTI01.
{ "InstanceDnsDomain": "eucalyptus.internal", "InstanceDnsServers": ["10.1.1.254"], "PublicIps": [ "10.111.101.84", "10.111.101.91", "10.111.101.92", "10.111.101.93" ], "Subnets": [ ], "Clusters": [ { "Name": "PARTI00", "MacPrefix": "d0:0d", "Subnet": { "Name": "10.111.0.0", "Subnet": "10.111.0.0", "Netmask": "255.255.0.0", "Gateway": "10.111.0.1" }, "PrivateIps": [ "10.111.101.94", "10.111.101.95" ] }, { "Name": "PARTI01", "MacPrefix": "d0:0d", "Subnet": { "Name": "10.111.0.0", "Subnet": "10.111.0.0", "Netmask": "255.255.0.0", "Gateway": "10.111.0.1" }, "PrivateIps": [ "10.111.101.96", "10.111.101.97" ] } ] }