Revision e8a3bf18 doc/design-2.1.rst
b/doc/design-2.1.rst | ||
---|---|---|
544 | 544 |
"classes" in the future. Instance classes is not a feature we plan |
545 | 545 |
implementing in 2.1, though. |
546 | 546 |
|
547 |
|
|
548 |
Global hypervisor parameters |
|
549 |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
|
550 |
|
|
551 |
Current State and shortcomings |
|
552 |
++++++++++++++++++++++++++++++ |
|
553 |
|
|
554 |
Currently all hypervisor parameters are modifiable both globally |
|
555 |
(cluster level) and at instance level. However, there is no other |
|
556 |
framework to held hypervisor-specific parameters, so if we want to add |
|
557 |
a new class of hypervisor parameters that only makes sense on a global |
|
558 |
level, we have to change the hvparams framework. |
|
559 |
|
|
560 |
Proposed changes |
|
561 |
++++++++++++++++ |
|
562 |
|
|
563 |
We add a new (global, not per-hypervisor) list of parameters which are |
|
564 |
not changeable on a per-instance level. The create, modify and query |
|
565 |
instance operations are changed to not allow/show these parameters. |
|
566 |
|
|
567 |
Furthermore, to allow transition of parameters to the global list, and |
|
568 |
to allow cleanup of inadverdently-customised parameters, the |
|
569 |
``UpgradeConfig()`` method of instances will drop any such parameters |
|
570 |
from their list of hvparams, such that a restart of the master daemon |
|
571 |
is all that is needed for cleaning these up. |
|
572 |
|
|
573 |
Also, the framework is simple enough that if we need to replicate it |
|
574 |
at beparams level we can do so easily. |
|
575 |
|
|
576 |
|
|
547 | 577 |
Non bridged instances support |
548 | 578 |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
549 | 579 |
|
Also available in: Unified diff