...

• Introduction

• License

• Deployment Architecture

• Pre-Installation Requirements

  • Hardware Requirements

  • Network Requirements

  • Bare Metal Node Requirements

  • Software Requirements

• Installation High-Level Overview

  • Install Local Controller

  • Creating CRDs for Bare Metal Hosts

  • Running

  • Virtual Deployment Guide

    • Standard Deployment Overview

    • Snapshot Deployment Overview

    • Special Requirements for Virtual Deployments

    • Install Jump Host

    • Verifying the Setup - VMs

  • Upstream Deployment Guide

    • Upstream Deployment Key Features

    • Special Requirements for Upstream Deployments

    • Scenarios and Deploy Settings for Upstream Deployments

    • Including Upstream Patches with Deployment

    • Running

    • Interacting with Containerized Overcloud

• Verifying the Setup as defined in the Akraino validation feature project plus any additional testing specific to the blue print

...

Compute server Software Requirements:

Local The local controller will install all the software in compute servers right from OS, the software required to bring up the Kubernetes cluster

Network Prerequisites:

Please sure you have 3 distinguished networks 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.

Installation High-Level Overview

Connect Local Controller to baremetal hosts as described in Deployment Architecture section.

Install software for Local Controller, by booting from ICN ISO device.

...

Installation is two-step process and everything starts with one command "make install"

• 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

Preconfiguration for the local controller.

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"
      }
    }
  ]
}

Baremetal 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

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.

...