Page History

...

<--- 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:

...

• 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

...