Table of Contents | ||
---|---|---|
|
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
...
ICN strives to automate the process of installing the local cluster controller to the greatest degree possible–"zero touch installation". Most of the work is done simply by booting up the jump host (Local Controller) from the ISO image. Once booted, the controller is fully provisioned and begins to inspect and provision baremetal servers, until the cluster is entirely configured.
This document show step by step to configure the network, and deployment architecture for ICN BP.
License
Apache license v2.0
Deployment Architecture
The local controller is provisioned with the Metal3 Baremetal Operator and Ironic, which enable provisioning of Baremetal servers. The controller has three network connections to the baremetal servers: network A connects baremetal servers (to internet?)servers, network B is a private network used for provisioning the baremetal servers, and network C is the IPMI network, used for control during provisioning. In addition, the baremetal hosts connect to the network D, the SRIOV network.
In some deployment model, you can combine Net C and Net A to be the same networks, but developer should take care of IP Address management between Net A and IPMI address of the server.
Pre-installation Requirements
Local controller:
Local controller will reside in the jump server to run the Metal3 operator, Binary provisioning agent operator and Binary provisioning agent restapi controller.
Jump server Hardware Requirements
...
Local controller: at least three network interfaces.
Baremetal hosts: four network interfaces, including one IPMI interface.US
Four or more hubs, with cabling, to connect four networks.
Jump server Software Requirements:
ICN ISO (on bootable device, e.g., USB flash drive)
Images for provisioning bare metal hosts
Compute K8s cluster :
Installation High-Level Overview
...