| Table of Contents | ||
|---|---|---|
|
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
Developer Guide and Troubleshooting
Utilization of Images
Post-deployment Configuration
Debugging Failures
Reporting a Bug
Uninstall Guide
Troubleshooting
Error Message Guide
Maintenance
Blue Print Package Maintenance
- Software maintenance
- Hardware maintenance
- Blue Print Deployment Maintenance
Frequently Asked Questions
License
References
Definitions, acronyms and abbreviations
Introduction
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). Once booted, the controller is fully provisioned and begins to inspect and provision baremetal servers, until the cluster is entirely configured.
...