[OpenStack] Juju ignores per-model credentials when searching for flavors

[Pedro Guimarães]

Juju 2.7.4 (channel=edge)

Running juju multi-model and I have a per-project (hence, per-model on Juju) flavors. Those flavors are mapped to different physical hosts.

I added credentials for that specific model, different from bootstrap credentials.

However, Juju cannot see those specific flavors. It can only spawn the flavors that are an interesection between whatever present on Juju controller's credentials and on target model.

The right approach here would be to juju controllers to ditch entirely its own credentials and only use model's.

[Richard Harding (rharding)]

Juju has the idea that regions of the cloud can have different instance types. This seems like an odd modeling of split tenants in this way. Would it be more appropriate to look at a region distinction vs a per cred/flavors split?

[Pedro Guimarães (pguimaraes)]

@rharding Hi, so, this is sth that we are seeing customers request at design on top of OpenStack: add all nodes to a single region and set up Host Aggregates which will separate hosts by functions.

The problem is that tenants won't know about that. For that, they need to have a way to request VMs and always get them to the right hosts (e.g. dev team, goes to dev hosts).

That link between cloud administration and users is flavors.
That is why it is important to get it right on Juju as well. Juju needs to be able to deploy from its tenant into other tenants, which may have private flavors only for them.

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.