Juju seems to ignore openstack image constraints

[Krassi]

We are using Juju to provision applications in a private OpenStack cloud. The image that we have specified when generating the image metadata has some constraints (in OpenStack), that require at least an 'm1.small' flavor. When deploying an application Juju seems to ignore those OpenStack image constraints and tries to use the 'm1.tiny' flavor to provision the instances. While this can be worked around by explicitly specifying the constraints of the image, I think that Juju should be able to handle the default case.

[John A Meinel (jameinel)]

Where are those constraints listed? You can always deploy applications with
their own constraints (juju deploy app --constraints mem=X).

What usually interprets the image constraints? Euca tools, etc? Or are they
intended that Openstack's internal scheduling would use them, but you can
override them?

On Wed, Apr 12, 2017 at 12:31 PM, Krassi <email address hidden> wrote:

> Public bug reported:
>
> We are using Juju to provision applications in a private OpenStack
> cloud. The image that we have specified when generating the image
> metadata has some constraints (in OpenStack), that require at least an
> 'm1.small' flavor. When deploying an application Juju seems to ignore
> those OpenStack image constraints and tries to use the 'm1.tiny' flavor
> to provision the instances. While this can be worked around by
> explicitly specifying the constraints of the image, I think that Juju
> should be able to handle the default case.
>
> ** Affects: juju
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1682050
>
> Title:
> Juju seems to ignore openstack image constraints
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1682050/+subscriptions
>

[Krassi (kvalev)]

When uploading a new OpenStack image you can specify two 'constraints' - minimum disk size and minimum memory size required to boot the image. You can then query OpenStack to retrieve the values, see https://docs.openstack.org/developer/glance/glanceapi.html#list-available-images-in-more-detail (the min_disk and min_ram properties). When manually launching a new OpenStack instance, after the image is selected, OpenStack disables all flavors that do not fulfill those two requirements and I expected that Juju does the same, but it does not.

Those constraints cannot be overridden and are validated by OpenStack whenever you start a new instance (independent whether this is done via UI or API).

I know about the the --constraints argument, this is what we are currently using to work around this issue, but I think that Juju can be a bit more clever and take the min_disk and min_ram requirements into account.

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

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