Bug 1614641

Name of function:
OCP on OSP Bare Metal

User story:
As a system administrator, I need to be able to deploy OCP clusters on bare metal and increase the number of the container apps hosted per bare metal node (vs. each hypervisor node running VMs) so that I can boost CPU performance and lower disk and network latency.  

Purpose of function:
With this feature, customers will deploy OCP clusters on bare metal nodes through the use of director, although in OSP 14, director will install the operating system only and will not perform the full  OpenStack deployment,  Director may also be used to manage bare metal nodes where OCP will be deployed.  

(Note that the integration with OSP structure is out of scope for OSP 14.)

Work required (from detail plan):
Procedural 
------
OCP installer (check if already documented?)

How to install director client (already documented?)

How to use director to install OCP
How to configure and set up the cluster, compute, and infrastructure nodes

Test - log in to the OCP cluster, try out setup, run command(s) to determine if services are enabled correctly
How to scale a node
------

Conceptual 
------
What information to assemble to be ready for configuration
how many cluster, compute, and infrastructure nodes
Name of OCP clusters
Any OCP specific configurations
(OCP requirements already documented?)
What are the network requirements from OCP? (post OCP 4.0 might be different)
What are the hardware requirements (OCP current runs on any hardware RHEL runs on)
OCP operator needs to understand Director
------

Reference
------
Link to existing Director documentation as optional reference material
------