Table of Contents
outline true

Introduction

...

Other Installation Requirements

Jump Host

...

Requirements  <--- SM comment "Is jump host same as jump server? if yes, better to use same nomenclature thru out the doc" >>>

Jump server required to be installed with Ubuntu 18.04 server, and have 3 distinguished networks as shown in figure 11  <--- SM comment "This is redundant, is captured under HW and SW requirements" >>>

Jump server Hardware Requirements

...

<--- SM comment "DMZ may not mean anything to customer. Lets be consistent. Can we replace IF0, IF1 etc with Net A, Net BThis is redundant, is captured under HW and SW requirements" >>>

Jump server Software Requirements:

...

Please refer the figure 1, for all the network requirement in ICN BP

Please make sure you have 3 distinguished networks net - Net A, Net B and Net C as mentioned in figure 1. Local controller uses the Net B and Net C to provision the Baremetal servers to do the OS provisioning.

...

Compute server Software Requirements:

The local controller will install all the software in compute servers right from OS, the software required to bring up the Kubernetes clustercluster <--- SM comment "local controller installs OS on compute servers?" >>>

Execution Requirements (Bare Metal Only)

ICN BP check all the precondition and execution requirements for both Baremetal and VM deploymentdeployment <--- SM comment "Heading indicates only Baremetal but the text here mentions both types of deployments including VM" >>>

Installation High-Level Overview

...

• Installation of the local controller in the edge location.
• Installation of Compute cluster to run the workload invoked by the local controller in the edge location.

Baremetal Deployment Guide

Install Bare Metal

...

Jump Host <--- SM comment "Is Jump Host same as local Controller? The high level installation overview never mentions installing jump host" >>>

Creating a Node Inventory File

Preconfiguration for the local controller. <--- SM comment "local Controller or jump host? Please use one nomenclature. changing names is confusing" >>>

User required to provide the IPMI information of the edge server they required to connect to the local controller by editing node JSON sample file in the directory icn/deploy/metal3/scripts/nodes.json.sample as below. If you want to increase nodes, just add another array

{
  "nodes": [
    {
      "name": "edge01-node01",
      "ipmi_driver_info": {
        "username": "admin",
        "password": "admin",
        "address": "10.10.10.11"
      },
      "os": {
        "image_name": "bionic-server-cloudimg-amd64.img",
        "username": "ubuntu",
        "password": "mypasswd"
      }
    },
     {
      "name": "edge01-node02",
      "ipmi_driver_info": {
        "username": "admin",
        "password": "admin",
        "address": "10.10.10.12"
      },
      "os": {
        "image_name": "bionic-server-cloudimg-amd64.img",
        "username": "ubuntu",
        "password": "mypasswd"
      }
    }
  ]
}

Local controller Metal3 configuration Reference:

...

       <--- SM comment "Since we are doing a 3 compute node installation; it will be better to include 3 nodes in the json sample file above." >>>

• node: The array of nodes required to add to local controller
• name: Name of the Baremetal to be provisioned by Metal3, and this name will be the hostname for the machine, once it is provisioned
• ipmi_driver_info: IPMI driver info is a json field, currently holds the IPMI information required for Ironic to send the IPMI tool command
  • username: BMC username required to be provided for Ironic
  • password: BMC password required to be provided for Ironic
  • address: BMC server IPMI LAN IP address
• os: Baremetal machine OS information is a json field, currently holds the image name to be provisioned, username name and password for the login.
  • image_name: images name should be in qcow2 format
  • username: login username for the OS provisioned
  • password: login password for the OS provisioned

...

Frequently Asked Questions

How to setup IPMI?

First, make sure the IPMI tool is installed in your servers, if not install them using apt install ipmitool

Then, check for the ipmitool information of each servers using the command "ipmitool lan print 1"

If the above command doesn't show the IPMI information, then setup the IPMI static IP address using following instruction

• Mostly easy way to set up IPMI topology in your lab setup is by using IPMI tool. 
• Using IPMI tool - https://www.thomas-krenn.com/en/wiki/Configuring_IPMI_under_Linux_using_ipmitool
• IPMI information can be considered during the BIOS setting as well.

BMC web console url is not working?

...