Revision e8a3bf18
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 |
|
b/doc/install.rst | ||
---|---|---|
181 | 181 |
(xend-relocation-address '') |
182 | 182 |
(xend-relocation-hosts-allow '^192\\.168\\.3\\.[0-9]+$') |
183 | 183 |
|
184 |
The last line assumes that all your nodes have secondary IPs in the |
|
184 |
|
|
185 |
The second line assumess that the hypervisor parameter |
|
186 |
``migration_port`` is set 8002, otherwise modify it to match. The last |
|
187 |
line assumes that all your nodes have secondary IPs in the |
|
185 | 188 |
192.168.3.0/24 network, adjust it accordingly to your setup. |
186 | 189 |
|
187 | 190 |
.. admonition:: Debian |
b/man/gnt-cluster.sgml | ||
---|---|---|
359 | 359 |
</listitem> |
360 | 360 |
</varlistentry> |
361 | 361 |
<varlistentry> |
362 |
<term>chroot</term> |
|
363 |
<listitem> |
|
364 |
<para> |
|
365 |
a simple chroot manager that starts chroot based on a |
|
366 |
script at the root of the filesystem holding the |
|
367 |
chroot |
|
368 |
<varlistentry> |
|
362 | 369 |
<term>fake</term> |
363 | 370 |
<listitem> |
364 | 371 |
<para> |
... | ... | |
376 | 383 |
</para> |
377 | 384 |
|
378 | 385 |
<para> |
386 |
The <option>--hypervisor-parameters</option> option allows you |
|
387 |
to set default hypervisor specific parameters for the |
|
388 |
cluster. The format of this option is the name of the |
|
389 |
hypervisor, followed by a colon and a comma-separated list of |
|
390 |
key=value pairs. The keys available for each hypervisors are |
|
391 |
detailed in the <citerefentry> |
|
392 |
<refentrytitle>gnt-instance</refentrytitle> |
|
393 |
<manvolnum>8</manvolnum> </citerefentry> man page, in the |
|
394 |
<command>add</command> command plus the following parameters |
|
395 |
which are only configurable globally (at cluster level): |
|
396 |
|
|
397 |
<variablelist> |
|
398 |
<varlistentry> |
|
399 |
<term>migration_port</term> |
|
400 |
<listitem> |
|
401 |
<simpara>Valid for the Xen PVM and KVM hypervisors.</simpara> |
|
402 |
|
|
403 |
<para> |
|
404 |
This options specifies the TCP port to use for |
|
405 |
live-migration. For Xen, the same port should be |
|
406 |
configured on all nodes in |
|
407 |
the <filename>/etc/xen/xend-config.sxp</filename> |
|
408 |
file, under the |
|
409 |
key <quote>xend-relocation-port</quote>. |
|
410 |
</para> |
|
411 |
</listitem> |
|
412 |
</varlistentry> |
|
413 |
</variablelist> |
|
414 |
|
|
415 |
</para> |
|
416 |
|
|
417 |
<para> |
|
379 | 418 |
The <option>--backend-parameters</option> option allows you to set |
380 | 419 |
the default backend parameters for the cluster. The parameter |
381 | 420 |
format is a comma-separated list of key=value pairs with the |
... | ... | |
417 | 456 |
</para> |
418 | 457 |
|
419 | 458 |
<para> |
420 |
The <option>--hypervisor-parameters</option> option allows you |
|
421 |
to set default hypervisor specific parameters for the |
|
422 |
cluster. The format of this option is the name of the |
|
423 |
hypervisor, followed by a colon and a comma-separated list of |
|
424 |
key=value pairs. The keys available for each hypervisors are |
|
425 |
detailed int the <citerefentry> |
|
426 |
<refentrytitle>gnt-instance</refentrytitle> |
|
427 |
<manvolnum>8</manvolnum> </citerefentry> man page, in the |
|
428 |
<command>add</command> command. |
|
429 |
</para> |
|
430 |
|
|
431 |
<para> |
|
432 | 459 |
The <option>--nic-parameters</option> option allows you to set |
433 | 460 |
the default nic parameters for the cluster. The parameter |
434 | 461 |
format is a comma-separated list of key=value pairs with the |
b/man/gnt-instance.sgml | ||
---|---|---|
505 | 505 |
</listitem> |
506 | 506 |
</varlistentry> |
507 | 507 |
|
508 |
<varlistentry> |
|
509 |
<term>migration_port</term> |
|
510 |
<listitem> |
|
511 |
<simpara>Valid for the Xen PVM and KVM hypervisors.</simpara> |
|
512 |
|
|
513 |
<para> |
|
514 |
This options specifies the TCP port to use for |
|
515 |
live-migration. Note that this shouldn't (usually) |
|
516 |
be changed at the instance level, but only at |
|
517 |
cluster-level. |
|
518 |
</para> |
|
519 |
</listitem> |
|
520 |
</varlistentry> |
|
521 |
|
|
522 | 508 |
</variablelist> |
523 | 509 |
|
524 | 510 |
</para> |
525 | 511 |
|
526 | 512 |
<para> |
527 |
</para> |
|
528 |
|
|
529 |
<para> |
|
530 | 513 |
The <option>--iallocator</option> option specifies the instance |
531 | 514 |
allocator plugin to use. If you pass in this option the allocator |
532 | 515 |
will select nodes for this instance automatically, so you don't need |
Also available in: Unified diff