[2.5] No way in data to tell if image can be registered as KVM host

[Steve Rydz]

When deploying machines, there is an option for registering as KVM host. This is only supposed to apply to bionic and newer versions of Ubuntu.

In the data there is no way to simply check if the version of Ubuntu is modern enough so versions have to be hard-coded in the client side code.

[Mike Pontillo (mpontillo)]

More generally, we should consider each custom action on deployment (such as deploying a MAAS-managed KVM host or a rack controller) to be associated with a specific set of supported images.

That is, rather than having "deploy KVM" be something the UI "just knows" is a MAAS feature, we should consider modeling that as an endpoint that provides a list of custom deployment options that MAAS could make use of.

[Martin Storey (cassiocassio)]

That's an excellent idea to generalise this.

- for KVM we are discussing -preventing- deploys with unsupported Series

- I think some suggested that you should be able to proceed with warnings - which is this case I would disagree with - we want Microclouds to be a "it just works" feature.

- But I can imagine that other features might need supported=allowed / unsupported=dissallowed / and unsupported=proceed with warning...

[Mike Pontillo (mpontillo)]

I agree with the hesitation around "proceed with warnings"; if someone wants to deploy KVM on something other than Bionic, I would prefer an active mechanism, such as requiring the user to acknowledge their choice of trying an unsupported release. (From the API we do this occasionally with a `force=true` parameter.) The use case is "we are having an issue and we want to see if it happens on release X, but we don't want to change the MAAS code".

[Adam Collard (adam-collard)]

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team