meltcloud

Appearance

Network Profiles ​

Network Profiles configure Machines to integrate into your network fabric according to the common Uplink Topologies.

TIP

Network Profiles are optional:

By default – when no Network Profile is assigned – the Machine will try to obtain IP address configuration on each interface using DHCP.

For single attached networks this default behaviour is sufficient, so you won't need any Network Profile.

Each Network Profile consists of one or more Links. For each physical interface that requires a different configuration, create a new Link.

Examples:

  • You have two physical interfaces and want to dedicate one for workload traffic and one for storage traffic. In this case, you will create two links: one Link for Workload and one Link for Storage, with one physical interface per each Link.
  • You have four physical interfaces and want to bond two for workload traffic, and bond the other two for storage traffic. In this case, you will create two links: one Link for Workload and one Link for Storage, with two physical interfaces per each Link.

A Link consists of the following parts:

Schema Network Profile

Each Link has an Uplink Configuration that defines how to connect to the outside world using physical interfaces. You can configure:

  • Single physical interface
    Use when no specific redundancy or aggregation requirements exist.

  • Multiple physical interfaces
    Bond multiple physical interfaces together. By default, interfaces operate in active/standby mode for failover. Alternatively, you can enable LACP (802.3ad) for link aggregation.

Important: The configuration must match your switch configuration for proper operation.

The Link itself is implemented as a VLAN-aware Linux bridge and provides the flexibility to dynamically attach multiple VLAN-based networks as needed.

Host Networking ​

For each Link, Host networking determines whether the Kubernetes node itself participates directly in a given network. When enabled:

  • Native VLAN
    The node automatically obtains IP configuration via DHCP for the native VLAN on the bridge interface.

  • Additional VLANs
    The node creates a VLAN sub-interface per configured VLAN and obtains IP configuration via DHCP for each.

Note: Whether a host should actively participate in a given network depends on your requirements. We’re happy to assist you in designing the right integration.

WARNING

At least one Link requires Host Networking in order to allow the Machine to communicate with Nest.

When enabling Host Networking, be aware to check that all the required DHCP options are set to fully configure the host.

Be especially careful when using more than one Link with Host Networking/DHCP enabled: The following DHCP options should only be provided on a single link to not cause conflicts:

  • Default gateway (otherwise, the host will have multiple default gateways)
  • Domain name (otherwise, the host might have conflicting domain names)
  • DNS server (otherwise, the host will have duplicate DNS servers, which causes Warnings)
  • NTP servers (otherwise, the host will have duplicate NTP servers)

Jump right here to create your first Network Profile.