action #168177
closed
coordination #167054: [epic] Run more workloads in CC-compliant PRG2 to be less affected by CC related network changes
Migrate critical VM based services needing access to CC-services to CC areas
Added by okurz 8 months ago.
Updated about 1 month ago.
Category:
Feature requests
Description
Motivation¶
non-compliant NUE2 based production VMs might become problematic due to #165282 so we should evaluate which VMs we can migrate and where and execute accordingly.
Acceptance criteria¶
-
AC1: Critical VM based services needing access to CC-services are running from CC areas where reasonable
-
AC2: Users can access the services using location independant CNAME records where applicable as in before
Suggestions¶
-
DONE Wait for #168174
-
DONE Try out with non-critical changes, e.g. tumblesle
- Decide which VMs and/or services should be migrated considering the alternative #168133. At time of writing we have 10 VMs on osiris+qamaster
- Prepare DHCP+DNS changes in https://gitlab.suse.de/OPS-Service/salt/
See suggestions from #168174-3 about how to migrateMigrate VMs from qamaster to a (temporary) service hypervisor running on a free OSD openQA worker, e.g. w38+w39- Move VMs to openplatform
- Copied from action #167057: Run more standard, qemu OSD openQA jobs in CC-compliant PRG2 and none in NUE2 size:S added
- Subject changed from Evacuate critical VM based services needing access to CC-services to CC areas to Migrate critical VM based services needing access to CC-services to CC areas
- Description updated (diff)
- Assignee set to okurz
- Target version changed from Ready to Tools - Next
- Subject changed from Migrate critical VM based services needing access to CC-services to CC areas to Migrate critical VM based services needing access to CC-services to CC areas size:M
- Description updated (diff)
- Status changed from New to Workable
- Status changed from Workable to Blocked
- Target version changed from Tools - Next to Ready
- Assignee changed from okurz to mkittler
assigning to mkittler to track blocker tickets for now
As today the network access rules have been put in place to prevent access to sensitive data we can see the problems that are linked to that.
Today actually regarding monitoring it seems it's weird that there was a short data outage but by now at least data from OSD itself shows up just fine on https://monitor.qa.suse.de/d/nRDab3Jiz/openqa-jobs-test?orgId=1&from=now-7d&to=now so it's really traffic from OSD (CC) to non-CC monitor is coming through ok it seems. With that it's less critical to move ressources like monitor.qa.suse.de
- Description updated (diff)
- Subject changed from Migrate critical VM based services needing access to CC-services to CC areas size:M to Migrate critical VM based services needing access to CC-services to CC areas
Based on discussion with szarate we should refine and re-estimate the ticket. Better split into multiple S-sized-tasks, e.g. split into "support migration of other people's VMs" and "our own critical service workloads" excluding any "personal toy VMs" :)
- Assignee changed from mkittler to okurz
- Target version changed from Ready to future
- Status changed from Blocked to Feedback
- Target version changed from future to Ready
Perhaps it helps to discuss it on a call? (not necessarily the whole team) Or if you feel differently about it we need to find another solution for the epic
- Status changed from Feedback to Blocked
- Target version changed from Ready to future
- Status changed from Blocked to Resolved
#173674 resolved, all subtasks resolved
- Target version changed from future to Ready
Also available in: Atom
PDF