CI compute resources

[vveralag]

Created by Gitlab User parkerer: In order to setup CI the project will need computer resources. The options I evaluated are:

• Github cloud runners
• CaaS (https://intel.sharepoint.com/sites/caascustomercommunity)
• Manage servers ourselves (vm or physical)

Intel policy prohibits use of github cloud runners on Intel private repositories so that is not currently a viable options for Eowyn.

CaaS is an on-premises cloud compute option at Intel for running workloads in containers. They currently offer Rancher projects (https://rancher.com/) to shared compute clusters in Munich, Folsom, and Santa Clara. Eowyn project responsibilities would be creating and managing Kubernetes workloads, which for CI should be a single docker image.

Managing servers ourselves, VM or physical, incurs additional work and responsibility without providing benefit so my recommendation is CaaS.

To use CaaS for CI we need to:

1. Request a Rancher project (https://intel.sharepoint.com/sites/caascustomercommunity/SitePages/Rancher-Projects.aspx).
   • Requires and IAP ID
2. Create a docker image for CI runners.
   • Need to decide how to handle secrets. Known options are making them part of the image or letting github handle them if using github actions.
   • If we need a custom image I do not know where it would be stored. There may be a registry we can use already, or we may need an Eowyn specific registry. If needed we can get a Harbor project (https://intel.sharepoint.com/sites/caascustomercommunity/SitePages/Harbor-Registry.aspx).
3. Launch workload(s) in Rancher.
   • There might be some additional networking setup required to connect the runners with github.com.

After that the remaining CI setup should be roughly the same for any compute resource option.

1. Register the runners with the github project (or other CI tool).
2. Configure the CI.

[vveralag]

Commented by Gitlab User danielcm: assigned to Gitlab User parkerer

[vveralag]

Commented by Gitlab User danielcm: changed due date to December 31, 2021

[vveralag]

Commented by Gitlab User parkerer: As far as compute resources go this is complete.

[vveralag]

Commented by Gitlab User danielcm: added to epic &1

[vveralag]

Commented by Gitlab User danielcm: Gitlab User parkerer can you create the issues in gitlab for all this work to happen. I agree resources computation is done, we need to translate this into an actual action plan.