Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
outlinetrue
Introduction

...

Hostname

CPU Model

Memory

Storage

1GbE: NIC#, VLAN,

(Connected

extreme 480 switch)

10GbE: NIC# VLAN, Network

(Connected with IZ1 switch)

Jump

Intel

2xE5-2699

64GB

3TB (Sata)
180 (SSD)

IF0: VLAN 110 (DMZ)
IF1: VLAN 111 (Admin)

IF2: VLAN 112 (Private)
VLAN 114 (Management)
IF3: VLAN 113 (Storage)
VLAN 1115 (Public)


Jump server Software Requirements:

...

Hostname

CPU Model

Memory

Storage

1GbE: NIC#, VLAN,

(Connected

extreme 480 switch)

10GbE: NIC# VLAN, Network

(Connected with IZ1 switch)

node1

Intel

2xE5-2699

64GB

3TB (Sata)
180 (SSD)

IF0: VLAN 110 (DMZ)
IF1: VLAN 111 (Admin)

IF2: VLAN 112 (Private)
VLAN 114 (Management)
IF3: VLAN 113 (Storage)
VLAN 1115 (Public)

node2

Intel

2xE5-2699

64GB

3TB (Sata)
180 (SSD)

IF0:  VLAN 110 (DMZ)
IF1: VLAN 111 (Admin)

IF2: VLAN 112 (Private)
VLAN 114 (Management)
IF3: VLAN 113 (Storage)
VLAN 1115 (Public)

node3

Intel

2xE5-2699

64GB

3TB (Sata)
180 (SSD)

IF0: VLAN 110 (DMZ)
IF1: VLAN 111 (Admin)

IF2: VLAN 112 (Private)
VLAN 114 (Management)
IF3: VLAN 113 (Storage)
VLAN 1115 (Public)


Compute server Software Requirements:

...

Code Block
languagejs
titleuser_config.sh
linenumberstrue
#!/bin/bash

#Local controller - Bootstrap cluster DHCP connection
#BS_DHCP_INTERFACE defines the interfaces, to which ICN DHCP deployment will bind
#e.g. export BS_DHCP_INTERFACE="ens513f0"
export BS_DHCP_INTERFACE=

#BS_DHCP_INTERFACE_IP defines the IPAM for the ICN DHCP to be managed.
#e.g. export BS_DHCP_INTERFACE_IP="172.31.1.1/24"
export BS_DHCP_INTERFACE_IP=

#Ironic#Edge Metal3Location settings for provisioning network
#Interface to which Ironic provision network to be connected
#Net B - Provisioning Network
#e.g. export IRONIC_INTERFACE="enp4s0f1"
export IRONIC_INTERFACE=

#Ironic Metal3 setting for IPMI LAN NetworkProvider Network configuration
#Net A - Provider Network
#If provider having specific Gateway and DNS server details in the edge location
#export PROVIDER_NETWORK_GATEWAY="10.10.110.1"
export PROVIDER_NETWORK_GATEWAY=
#export PROVIDER_NETWORK_DNS="8.8.8.8"
export PROVIDER_NETWORK_DNS=

#Ironic Metal3 settings for provisioning network
#Interface to which Ironic IPMI LAN should bindprovision network to be connected
#Net B - Provisioning Network
#e.g. export IRONIC_IPMI_INTERFACE="enp4s0f0enp4s0f1"
export IRONIC_IPMI_INTERFACE=

#Ironic #InterfaceMetal3 IPsetting for theIPMI LAN Network
#Interface to which Ironic IPMI LAN, ICN verfiy the should bind
#Net C - IPMI LAN ConnectionNetwork
#e.g. export IRONIC_IPMI_INTERFACE_IP="10.10.110.20"
#Net C - IPMI LAN Network
enp4s0f0"
export IRONIC_IPMI_INTERFACE_IP=

#Edge#Interface LocationIP Providerfor Networkthe configurationIPMI #NetLAN, AICN -verfiy Providerthe NetworkLAN #IfConnection provideris havingactive specificor Gateway and DNS server details in the edge location
#export PROVIDER_NETWORK_GATEWAYnot
#e.g. export IRONIC_IPMI_INTERFACE_IP="10.10.110.120"
#Net C - IPMI LAN Network
export PROVIDERIRONIC_NETWORK_GATEWAY=
#export PROVIDER_NETWORK_DNS="8.8.8.8"
export PROVIDER_NETWORK_DNS=IPMI_INTERFACE_IP=

Running

After configuring, Node inventory file and setting files. Please run "make install" from the ICN parent directory as shown below:

...

  1. All the software required to run the bootstrap cluster is being downloaded and installed
  2. Kubernetes cluster to maintain the Bootstrap cluster and all the servers in the edge location is installed
  3. Metla3 Metal3 specific network configuration such as local DHCP server networking for each edge location, Ironic networking for both provisioning network and IPMI LAN network is identifiedare identified and created
  4. Metal3 is launched with IPMI configuration as configured in "user_config.sh" and provision the Baremetal servers using IPMI LAN network. For more information refer the Debugging Failure section
  5. Metal3 launch verification run without a timeout of 60 mins, by checking the status of all the servers being provisioned or not,
    1. All servers are provisioned parallelly. For example, if your deployment is having 10 servers in the edge location. All the 10 servers are provisioned at the same time
    2. Metal3 launch verification take care of checking all the servers are provisioned, the network interfaces are up and provisioned with provider network gateway and DNS server
    3. Metal3 launch verification checks the status of all servers given in user_config.sh to make sure all the servers are provisioned. For example, if 8 servers are provisioned and 2 servers are not provisioned, Launch verification make sure all servers are provisioned before launch Kubernetes clusters on those servers

Virtual Deployment Guide

Standard Deployment Overview

...