8000
Skip to content

Store changed config keys as pending when they are immutable on running instances #14813

@vosdev

Description

@vosdev

I often run into errors changing configuration that can only be changed when the instance is stopped.

I would like to request a feature that allows us to change these options regardless of the state of the instance.

Failed updating memory limit: Cannot increase memory size beyond boot time size when VM is running (Boot time size 8192MiB, new size 12288MiB)

After making a configuration change that is currently not allowed, the configuration can be temporarily stored in a volatile.pending.* key, to be automatically applied when the instance stops.

(In the case of my memory example, this would be volatile.pending.limits.memory: 12GiB)

Of course this is just a quick suggestion of a possible solution.

What does this fix?

The current way of work is to poweroff my instance, wait for it to power down, make the config change, power on instance. This is slow and gives you quite some downtime.

This strength of this feature would allow you to make a change to the instance and either reboot it for minimal downtime, or schedule a reboot at 03:00 in the morning so no one will notice the downtime.

Metadata

Metadata

Assignees

No one assigned

    Labels

    MaybeUndecided whether in scope for the project
    No fields configured for Feature.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0