OCP/Telco Definition of Done
Epic Template descriptions and documentation.

<--- Cut-n-Paste the entire contents of this description into your new Epic --->

Epic Goal

• A separate machine pool or (better) machine information (since this is a single instance) should be editable from the install config. The machine information should be specified for the GCP bootstrap machine.

Why is this important?

• The addition of hyperdisk-balanced and pd-balanced disk types has expanded the available types of control plane nodes. The bootstrap machine uses the same disk type and instance type as the control plane nodes (specified in the install config). Prior to the addition of hyperdisk-balanced and pd-balanced types, the bootstrap machine could/would only use the pd-ssd disk type. 

Scenarios

1. [Current] 

   controlPlane:
     architecture: amd64
     hyperthreading: Enabled
     name: master
     platform:
       gcp:
         type:
           n4-standard-16
         osDisk:
           diskType: hyperdisk-balanced
           DiskSizeGB: 100
    

   The settings above will create a bootstrap node that also has the instance type of `n4-standard-16`. 

1. [future] 

   bootstrap:
     architecture: amd64
     hyperthreading: Enabled
     name: bootstrap
     platform:
       gcp:
         type:
           n2-standard-16
         osDisk:
           diskType: pd-ssd
           DiskSizeGB: 30
    

   The settings above would create the bootstrap node with the n2 instance type and pd-ssd disk type. If the example also uses the control plane section in [1], then the control plane nodes would have the n4 instance types and hyperdisk-balanced disk types.  

Acceptance Criteria

• The GCP Bootstrap Machine information should be independent of the control plane machine pool.

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions::

1. Should it be an entire machine pool (since it is only one machine) or should it be a single machine entry?

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>