Versions Compared

Key

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

...

User required to provide the IPMI information of the edge server they required to connect to the local controller by editing node json 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

Code Block
languagejs
titlenode.json.sample
linenumberstrue
{
  "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:

  • 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

Local controller network configuration Reference:


Kubernetes Dashboard

Kubernetes Dashboard runs on the Local Controller. It is accessed via a web browser. kubectl proxy should be running. The Dashboard is brought up by with the dashboard-deployment yaml file. This file must refer to the images in the local Docker repository (see "spec: container: image:"). There should also be a K8S service account created for an admin-user. The token for Dashboard login is created from the admin-user secrets.

...