-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
Enable unified limits in 18.0
-
False
-
-
False
-
Not Selected
-
Proposed
-
Proposed
-
To Do
-
OSP-14490 - Large scale scheduling
-
Proposed
-
Proposed
-
-
This epic is about supporting unified limits in OSP18.
- backport the Epoxy changes to Antelope downstream
- finish the discussion from https://issues.redhat.com/browse/OSPRH-150?focusedId=25256435&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-25256435 about how to automate
- the greenfield enablement of unified limits (e.g. what will be our defaults and how the human specifies them)
- the adoption from 17.1 to 18.0.x and transform the legacy limits to unified limits
- the upgrade from 18.0.[0-3?] to 18.0.x and transform the legacy limits to unified limits
- QE all the above implementation
- Document all the above
We will need to create stories accordingly.
==
Old description :
We need a procedure that:
- changes nova's quota driver via the OpenStackControlPlane CR
- which services needs the drive config? api, conductor, scheduler or we need to config compute too?
- describe how to manually define default limits for greenfield
- describe how to manually migrate existing quota config for adoption
- or backport the nova-manage limit command to Antelope from Bobcat
- or state that unified limits only supposed to be enabled on greenfield as day one operation
- describe that no defined limit means 0 quota for that resource
https://docs.openstack.org/nova/latest/admin/unified-limits.html
https://docs.openstack.org/nova/latest/cli/nova-manage.html#limits-migrate-to-unified-limits
- split from
-
OSPRH-150 Configure unified limits
- Backlog