• Guido Trotter's avatar
    Get rid of the default_hypervisor slot · 066f465d
    Guido Trotter authored
    Currently we have both a default_hypervisor and an enabled_hypervisors
    list. The former is only settable at cluster init time, while the latter
    can be changed with cluster modify.
    This becomes cumbersome in a few ways: at cluster init time for example
    if we pass in a list of enabled hypervisors which doesn't include the
    "default" xen-pvm one, we're also forced to pass a default hypervisor,
    or an error will be reported. It is also currently possible to disable
    the default hypervisor in cluster-modify (with unknown results).
    In order to avoid this we get rid of this field altogether, and define
    the "first" enabled hypervisor as the default one. This allows ease of
    changing which one is the default, and at the same time maintains
    At configuration upgrade we make sure that the old default is first in
    the list, so that 2.0 cluster defaults are preserved.
    Signed-off-by: default avatarGuido Trotter <ultrotter@google.com>
    Reviewed-by: default avatarIustin Pop <iustin@google.com>
objects.py 26.5 KB