As seen previosuly in this document, there are a number of components which require an IP address which are automatically deployed on an Edge Compute Stack host in order to provide the services at an edge location. This option requires you to edit the boot media being used to deploy the Edge Compute Stack host to provide IP addresses from the initial bring up of the Edge Compute Stack host.

Prerequisites

  • Downloaded and created boot media for deploying the Edge Compute Stack host

  • 3 IP addresses for Infrastructure Components

  • 1 IP address for worker node configuration

  • Subnet Mask Information

  • Default Gateway Information

  • DNS Server(s) Information

Note:

If using the ISO deployment method you will need to extract the ISO contents, edit the KS.cfg file as outlined below and re-write the ISO file ready to be used, the instructions for this vary depending on your client computer operating system and is not currently part of this document.

Procedure

  1. Edit the KS.CFG file found in the root of the created deployment media with a plain text editor, Visual Studio Code is recommended.
  2. Find the area that starts:# Optional: Static IP Address Configuration#
  3. Uncomment the lines after the instructions which starts with EC_INFRAVISOR_STATIC_IPAM_FILE 
    # ----------------------------------------------------------------------------
# Optional: Static IP Address Configuration
# ----------------------------------------------------------------------------
# - By default, DHCP sets the IP address, subnet mask, and default gateway
# - Optionally configure static ip addresses using below config where:
# - range[0]  = Host IP
# - range[1]  = Infravisor pod
# - range[2]  = Infravisor pod
# -----------------------------------------------------------------------------
EC_INFRAVISOR_STATIC_IPAM_FILE="$ECS_WORK_DIR/static_ipam.json"
cat <<EOT > $EC_INFRAVISOR_STATIC_IPAM_FILE
{
    "range": ["10.211.35.74", "10.211.35.75", "10.211.35.76"],
    "netmask": "255.255.252.0",
    "gateway": "10.211.32.1",
    "dns": ["10.211.56.141", "10.211.81.141"]
}
EOT
  4. Edit each of the addresses in the range section to provide a range of addresses which can be used for the core infrastructure components with the first address being used for the ECS Host Hypervisor Management Network and the following addresses being used for core infrastructure components.
  5. Edit the netmask entry to provide the network mask for this network.
  6. Edit the gateway entry to provide the default gateway for this network.
  7. Edit the dns entry to provide one or multiple dns servers, multiple dns servers can be provided in the following format:
    "dns": ["8.8.8.8", "9.9.9.9"]
  8. Save the KS.CFG file.
  9. Eject the media and deploy the image as per Deploying Edge Hosts

Results

Your infrastructure will be deployed using the static IP address information provided.

Example: Completed Example

A completed example of this configuration is provided below:

EC_INFRAVISOR_STATIC_IPAM_FILE="$ECS_WORK_DIR/static_ipam.json"
cat <<EOT > $EC_INFRAVISOR_STATIC_IPAM_FILE
{
    "range": ["10.211.35.74", "10.211.35.75", "10.211.35.76"],
    "netmask": "255.255.252.0",
    "gateway": "10.211.32.1",
    "dns": ["10.211.56.141", "10.211.81.141"]
}
EOT

What to do next

As part of the Edge Compute Stack deployment a kubernetes worker node is provisioned, this by default uses a DHCP address but can be changed to provide a static IP address as found in Enabling a static IP address for the default worker node.