pods could be created with maxmem > mem

Bug #1863357 reported by Andrea Ieri on 2020-02-14

This bug report will be marked for expiration in 56 days if no further activity occurs. (find out why)

This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

Pods are currently created with mem == maxmem. The consequence is that if a pod needs to subsequently be resized (which is likely to happen at some point during the life of a cloud), it will have to be stopped and started. Having a higher maxmem would allow operators to live-update ram in pods, reducing downtime. For this reason it would be great if maas allowed pods to be composed with a higher maxmem value, and possibly set it by default to something reasonable.

Alberto Donato (ack) wrote :

You can set memory (and cpu) overcommit in the settings tab of the POD once it's been added to maas.

Setting a higher overcommit ratio will increase the maximum "available" memory and let you set a higher limit for VMs.

Would that work for your use case?

Changed in maas:
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers