As a user I would like to use CAPI functionality for full life cycle management for creating OCP workload clusters from an OCP management cluster.

Note: Support for VMs and bare-metal servers 

Standard CAPI Types needed in order to cover this functionality:

• CAPI Infrastructure provider - in order to communicate with the machines before the deployment process.  
• CAPI  bootstrap provider - Responsible for deployment.
• CAPI Control plan Provider - Responsible for the Upgrade / config changes / Delete / with all the scale functions(in/out/up/down). 

Additional guidelines & requirements:

• A Workload cluster deployment on OpenStack VMs and BareMetal servers:

• OS Images 
• Registry
• Assisted installer service(Stolostron-engine)
• Setup DNS & DHCP service
• Pull secret
• etc.. 

• Upgrade the versions for the workload cluster:

• Generate Discovery ISO & Boot Discovery ISO(current implementation - long term to change into raw image)
• Add additional nodes 

• Update the existing workload cluster

• Scale in / out.

• Scale up / Down.

• Delete.  

Adding here also the Sylva & OTC  Requirements:

https://docs.google.com/spreadsheets/d/15VnNVVDwQ2SpsR-0HAPGK1bu581tYI85CR5w8ZV9MAc/edit?gid=1787713061#gid=1787713061 

Why does the customer need this? (List the business requirements here) ? 

Customer needs the product to be Sylva compliant, which dictates CAPI functionality

List any affected packages or components. ? 

Affected component is MCE