Status towards using OSU OSL for GitLab CI

[Andrew Bartlett]

I've been looking into what the critical blockers are before we can
fire up the runners at OSU OSL for more than tests.

My current task list (which is what I'm working on, in this order) is:
 - provide API keys to cloud_checker.py so it can terminate old
Openstack hosts
 - test operation with only API keys and not original passwords

The next step would be
 - Reconfigure runner limits to per-cloud and to match our OSU OSL
quota
 - Work out link or otherwise between 
https://gitlab.com/samba-team/gitlab-runner/ansible-role-gitlab-runner/-/blob/master/vars/docker-machine/osu-osl.yml
 and 
https://gitlab.com/samba-team/gitlab-runner/samba-cloud-autobuild/-/blob/master/gitlab-ci/cloud_images.yml
 - engage with SFC via the PLC to get commercial terms with OSU OSL
agreed.

In terms of our fallback position:

I would note that while it would not be ideal to allow all our jobs to
run at Rackspace, the cost increase ($700 per month I think - 150,000
[avarage mins] / 60 [mins per hour] * 0.28 [price for smaller rackspace
VMs]) is not great, but not nightmare stuff either.

Andrew Bartlett
 
-- 
Andrew Bartlett (he/him)       https://samba.org/~abartlet/
Samba Team Member (since 2001) https://samba.org
Samba Team Lead, Catalyst IT   https://catalyst.net.nz/services/samba

Samba Development and Support, Catalyst IT - Expert Open Source
Solutions