Feature request: Add ability to specify the desired kernel for the Juju-allocated MAAS machines

Bug #2003711 reported by Vladimir Grevtsev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Wishlist
Unassigned

Bug Description

In most cases, all machines are expected to be deployed with the GA kernel. However, that’s not always the case, and the operator could have a necessity to deploy the machine with the HWE or low-latency kernels.

Currently, it could be only achieved by setting up the “min_hwe_kernel” parameter in the specific machine option before the deployment: https://discourse.charmhub.io/uploads/default/optimized/2X/d/dc7feb9d2e7e525566cf6d4eda4161fc46436e00_2_1380x428.png

However, this method has its own disadvantages:

- operator can’t use IaC approach for tracking the desired configuration
- this is “minimum” kernel, which means that the HWE kernel will be deployed only if the specified distro is requested (e.g, in case of hwe-20.04 HWE will be deployed only if Focal is requested; but if Jammy is requested upon deployment - it will be with the GA kernel)

Meanwhile, MAAS “deploy” endpoint ( /MAAS/api/2.0/machines/{system_id}/op-deploy ) has a field for specifying the kernel explicitly during the deployment:

hwe_kernel (string ): Optional. If present, this parameter specified the kernel to be used on the machine

Could we consider adding another constraint and/or provider-level config option to control the desired kernel version using Juju?

Changed in juju:
importance: Undecided → Wishlist
milestone: none → 3.2-backlog
status: New → Triaged
Revision history for this message
Alan Baghumian (alanbach) wrote :

I cannot agree more!

This would be a great feature to have! I understand we can mark the minimum kernel from MAAS, however it would be more flexible to achieve this from Juju.

tags: added: constraints kernal maas-provider
Changed in juju:
milestone: 3.2-backlog → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.