Enhanced luna functionality

This section contains hard-core-i-know-what-i-am-doing recipes to offer enhanced functionality.

luna controller using dhcp-relay on another subnet

situation: two networks, where nodes are in a separate routable network as where the controller resides. The nodes can get DHCP response through a relay.

  • the controller needs a network wherein it resides. This could be any network, for now we use ctrl-network after renaming the default cluster network:
luna network rename cluster ctrl-network
  • stop dhcp on the ctrl-network:
luna network change --dhcp n ctrl-network
  • create a new network for the remote nodes:
luna network add -N <a.b.c.d/xx> --dhcp y --ds <dhcp range start> --de <dhcp range end> --gw <gateway/ip of router> --gm 10 cluster
  • configure the provision interface of e.g. compute group to be in the new network:
luna group change --if BOOTIF -N cluster compute
  • boot the nodes


luna controller to automatically boot nodes, use the mac address as node name base, while using a dhcp pool

Note: supported in luna 2.1

  • make sure that bind is the owner/has write access for the files in /var/named/*
chown named.named /var/named/*
  • assuming that the cluster network has already enabled dhcp, set the dhcp_nodes_in_pool:
luna network change --dnip y cluster
  • make sure there is only one group, e.g. compute, and have this group set the provisioning interface to dhcp
luna group change --if BOOTIF -dhcp y compute
  • enable the use of mac address as host name base while ensuring automatic node name detection:
luna cluster change --cm y --co y --nx y
  • boot the nodes


Luna controllers in HA setup, with distant routed node networks and remote shadows

As the title explains, this is quite a complex scenario where the on-premise setup comprises of a set of networks and more remote networks where a luna shadow is active for provisioning. The latter is a typical approach for cloud configurations. This setup configuration can be nearly completely achieved out-of-the-box during the installation, with a few extra steps to include the routed distant node network.

This example is merely here to show case what could be achieved and what challenging setups are supported.