Allow use of Placement Aggregates to limit tenant instance placement
Bug #1920982 reported by
Vern Hart
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Charm Guide |
Fix Released
|
Undecided
|
Unassigned | ||
OpenStack Nova Cloud Controller Charm |
Fix Released
|
Wishlist
|
James Vaughn | ||
Ussuri |
Fix Committed
|
Undecided
|
Unassigned | ||
Victoria |
Fix Committed
|
Undecided
|
Unassigned | ||
Wallaby |
Fix Committed
|
Undecided
|
Unassigned | ||
Xena |
Fix Committed
|
Undecided
|
Unassigned |
Bug Description
A customer requires using filter_tenant_id in host aggregates to limit where a customer can deploy instances. To do this, we require adding limit_tenants_
In short:
[scheduler]
enable_
limit_
This could be implemented as a config directive to the charm (maybe limit_tenants_
tags: | added: good-first-bug |
tags: | removed: onboarding |
Changed in charm-nova-cloud-controller: | |
assignee: | nobody → Hernan Garcia (hernandanielg) |
Changed in charm-nova-cloud-controller: | |
status: | Triaged → In Progress |
Changed in charm-nova-cloud-controller: | |
assignee: | Hernan Garcia (hernandanielg) → James Vaughn (jmcvaughn) |
Changed in charm-nova-cloud-controller: | |
milestone: | none → 22.04 |
Changed in charm-nova-cloud-controller: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Triaged to wishlist as this is a feature request.
> This could be implemented as a config directive to the charm (maybe limit_tenants_ to_placement_ aggregate, boolean, default=False) and, if True, set the above two lines in the [scheduler] section of nova.conf.
Yes, this is a very reasonable approach. This would be a good "first bug/feature" type piece of work.