46f44b8669
I hit a situation in a new cloud where I had defined two flavors with
the same amount of RAM "opendev-control" and "opendev". The config
had min-ram set [1] with a flavor-name of "opendev" -- I expected it
to match the exact name first, but nodepool was choosing
"opendev-control".
I guess the default order returned by the cloud is flavorid [2]. I'd
propose that sorting on a tuple of (ram, name) -- so that we match
names in alphabetical order -- is a more intuitive way to run the
match.
Documentation is updated, and a release note added.
[1] which actually we didn't want, really, because we wanted to
exactly match the flavor:
https://review.opendev.org/c/openstack/project-config/+/870677
[2] https://docs.openstack.org/api-ref/compute/?expanded=list-flavors-detail#list-flavors
Change-Id: I268dd598ca9f1b617c5062b41ad27d0305df60b9
11 lines
462 B
YAML
11 lines
462 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
In the OpenStack driver, when using ```min-ram``` in combination
|
|
with a ```flavor-name```, the first flavor to be found that
|
|
satisfied the ```min-ram``` requirements and contained the
|
|
substring ``flavor-name``` would be used. The order of the
|
|
flavors to be searched was dependent on what the cloud returned.
|
|
From this release, the available flavors are now alphabetically
|
|
sorted before matching ```flavor-name```.
|