Issue #3: Plan for Hardware Split between Stging & Prod - metrics-for-apps

fedora-infra / metrics-for-apps

#3 Plan for Hardware Split between Stging & Prod

Closed Sep 27, 2021 by dkirwan. Opened Jul 12, 2021 by amoloney.

Story Time
As a backend user/developer/team member,
I want to know how to split the hardware needed for the installation,
so that I can create a staging and production cluster for better testing

Acceptance Criteria
* DNS entries are created by copying batcave file , patching the changes and emailing them to sys-admins to apply in prod
* Patch is accepted

Background
There is not enough hardware to cover all roles needed, so we need to capitalise on using VMs in certain roles to maximise the coverage & performance

Metadata Update from @amoloney:
- Issue set to the milestone: Openshift 4 Installed
- Issue tagged with: prioritised

Jul 12, 2021

dkirwan commented Jul 14, 2021

We've got our DNS updates for the staging boxes merged into the dns repo on the batcave01.
Got our staging vmhost dns changes in also

dkirwan commented Jul 14, 2021

PR to add dhcp/pxeboot config for the vmhosts https://pagure.io/fedora-infra/ansible/pull-request/686

dkirwan commented Jul 15, 2021

We had to close/revert PR 686 above, work will continue in 690 instead: https://pagure.io/fedora-infra/ansible/pull-request/690

Edited Jul 15, 2021 by dkirwan

dkirwan commented Jul 15, 2021

Have a further dns patch in review: https://gist.github.com/davidkirwan/ecc1c135b6f2c82b1ef337ebdcd8414b

kevin commented Jul 15, 2021

Pushed the dns patch.

dkirwan commented Jul 19, 2021

Thanks @kevin !

Creating new ticket to capture the work of actually creating the staging control plane vm's