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 2 years ago by dkirwan. Opened 2 years ago 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

2 years ago

dkirwan commented 2 years ago

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 2 years ago

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

dkirwan commented 2 years ago

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

Edited 2 years ago by dkirwan

dkirwan commented 2 years ago

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

kevin commented 2 years ago

Pushed the dns patch.

dkirwan commented 2 years ago

Thanks @kevin !

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