Editing [scheduler] section of nova.conf
Bug #1908740 reported by
Andrey Grebennikov
This bug report is a duplicate of:
Bug #1920982: Allow use of Placement Aggregates to limit tenant instance placement.
Edit
Remove
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Nova Cloud Controller Charm |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
Feature request for supporting the optiosn of Nova in the [scheduler] section:
enable_
https:/
limit_tenants_
https:/
This is required by the customer in order to support isolating the aggregates based on the image metadata parameters in the flavors, and also supporting "dedicated host" usecase alternative to AWS.
Alternatively, we can allow to put arbitrary values to the "scheduler" section of nova.conf in the same way it's done with the "default" section already.
| summary: |
- Support for "enable_isolated_aggregate_filtering" option + Editing [scheduler] section of nova.conf |
| Changed in charm-nova-cloud-controller: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
| tags: |
added: field-medium removed: customer-found |
Revision history for this message
| Andrey Grebennikov (agrebennikov) wrote | #1 |
| tags: | removed: field-medium |
Revision history for this message
| Billy Olsen (billy-olsen) wrote | #2 |
To post a comment you must log in.
added field-medim