mcp2-dhcp-server

A DHCP server driven by MCP 2.0 server metadata (from Dimension Data CloudControl)

Note: This is a work-in-progress and has received only limited testing. It is not production-ready yet.

Configuration

Create mcp2-dhcp-server.yml:

mcp:
  user: "my_mcp_user"
  password: "my_mpc_password"
  region: "AU"

network:
  interface: eth0 # Specify the interface to listen on (for now, only a single interface is supported).
  vlan_id: "42837f37-a0fd-4544-a800-416a1d33f672"
  service_ip: 192.168.70.12
  start_ip: 192.168.70.20
  end_ip: 192.168.70.30

PXE / iPXE

If you're using iPXE, add the following to mcp2-dhcp-server.yml:

ipxe:
  enable: true
  port: 4777 # The TCP port used by the IPXE server (e.g. coreos-ixpe-server). Usually matches boot_script below.
  boot_image: "undionly.kpxe"
  boot_script: "http://192.168.220.10:4777/?profile=development"

boot_image is the name of the initial iPXE boot image file (relative to /var/lib/tftpboot) sent to regular PXE clients.
PXE clients will load this image via TFTP (from the server where mcp2-dhcp-server is running).
When they load this image, iPXE will send a second discovery packet with a user class of iPXE.
boot_script is the URL of the iPXE script (HTTP or TFTP) sent to iPXE clients.

If you're trying to boot CoreOS, consider using coreos-ipxe-server.

Overriding configuration with server tags

You can customise PXE / iPXE behaviour in CloudControl by giving a server one or more of the following tags:

pxe_boot_image (optional) - if specified, overrides the name of the initial PXE boot image to use (relative to /var/lib/tftpboot on the TFTP server).
ipxe_profile (optional) - if specified, overrides the name of the iPXE profile to use (equivalent to specifying ipxe_boot_script = http://{network.service_ip}:{ipxe.port}:4777/?profile={ipxe_profile}).
ipxe_boot_script (optional) - if specified, overrides the URL of the iPXE boot script to use (also overrides ipxe_profile).

Installation

See here for instructions.

Prerequisites

Ansible v2.2 or higher
Terraform v0.9.x or higher
terraform-provider-ddcloud

Net-bootable image

Download the image files here and unzip them.
Upload the .ovf, .vmdk, and .mf files to CloudControl and import them as a client image (ensure that "Import without Guest OS Customization" is checked, see here for details).

Net-bootable image (create your own)

Create a VM using VMWare Workstation or VMWare fusion (ensure it has 1 disk and 1 network adapter, with hardware version <= 10).
Do not install an operating system (leave the disk completely empty).
Close VMWare, and use ovftool to convert the virtual machine to OVF format (ovftool myserver.vmx ovf/myserver.ovf).
Upload the .ovf, .vmdk, and .mf files to CloudControl and import them as a client image (ensure that "Import without Guest OS Customization" is checked, see here for details).

Putting it all together

Deploy a new server from your client image, and start it. Network boot should proceed automatically.

# README