We have 1 new bvmhost and 1 old one which can be deployed for either new systems or to spread the load out over from the existing bvmhosts.
Metadata Update from @mohanboddu: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: low-gain, low-trouble, ops
I'd like to help on this
Existing bvmhost-x86:
bvmhost-x86-01.stg.iad2.fedoraproject.org bvmhost-x86-02.stg.iad2.fedoraproject.org bvmhost-x86-03.stg.iad2.fedoraproject.org
New bvmhost-x86:
bvmhost-x86-04.stg.iad2.fedoraproject.org bvmhost-x86-05.stg.iad2.fedoraproject.org
There's 2 methods to do this:
either:
Destroy the old vm and adjust ansible and re-run playbook to recreate it. or migrate the existing vm and then adjust ansible so it's correct.
oh, and you can see whats on what host by looking in ansible or /var/log/virthost-lists.out on batcave01 bvmhost-x86-04.stg is older repurposed machine, so moving to bvmhost-x86-05.stg first might be best
bvmhost-x86-01.stg.iad2.fedoraproject.org: 165418.0/257578 mem(unused/total) 27/64 cpus(unused/total) bvmhost-x86-02.stg.iad2.fedoraproject.org: 48708.0/63046 mem(unused/total) 21/32 cpus(unused/total) bvmhost-x86-03.stg.iad2.fedoraproject.org: 156637.0/246749 mem(unused/total) 25/64 cpus(unused/total) bvmhost-x86-04.stg.iad2.fedoraproject.org: 124394/124394 mem(unused/total) 48/48 cpus(unused/total) bvmhost-x86-05.stg.iad2.fedoraproject.org: 361905/361905 mem(unused/total) 96/96 cpus(unused/total)
so moving off 02 to 05 should be priorty
@mobrien were you gonna work on this one?
I can also take it, it's not urgent, but would be good to get done.
We just need to get this done. Either @mobrien or myself will try and get it done.
[backlog refinement]
nirik and mobrien will do this when time allows
I reinstalled bvmhost-x86-05.stg with rhel9, then migrated all the guests fron 02 off to it.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.