Synnefo » snf-ganeti » ganeti-local

- core changes, which affect the master daemon/job queue/locking or

  all/most logical units

- logical unit/feature changes

Core changes

============

  gnt-node group-del <group> # delete an empty group

  gnt-node group-list # list node groups

  gnt-node group-rename <oldname> <newname> # rename a group

  gnt-node add -g <group> # add a node to a certain group

  gnt-node modify -g <group> # move a node to a new group

  - The cluster will have a default group, which will initially be

  - Instance allocation will happen to the cluster's default group

    RAPI). Iallocator will be only passed the nodes belonging to that

    group.

  - Moving an instance between groups can only happen via an explicit

Other work and future changes

+++++++++++++++++++++++++++++

Commands which allow selection of sets of resources (for example

Initially node groups won't be taggable objects, to simplify the first

implementation, but we expect this to be easy to add in a future version

won't implement this in the first version, but we'll evaluate it for the

future, if we see scalability problems on big multi-group clusters.

we expect groups to be the basis for this, allowing for example a

each group. In some cases this will mean that inter-group move operation

will be necessarily performed with instance downtime, unless the

hypervisor has block-migrate functionality, and we implement support for

cluster state. While this is still acceptable for smaller clusters where

a small number of allocations/removal are presumed to occur between two

periodic capacity calculations, on bigger clusters where we aim to

node will not invalidate the capacity, as we're more interested in “at

least available” correctness, not “at most available”.

If a partial node query is done (e.g. just for the node free space), and

the returned values don't match with the cache, then the entire node

A job's priority can never go below -20. If a job hits priority -20, it

must acquire its locks in blocking mode.

a restart or crash of the master daemon.

Priorities also need to be considered inside the locking library to

netutils: Utilities for handling common network tasks

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Cluster initialization

~~~~~~~~~~~~~~~~~~~~~~

Privilege Separation

--------------------

Implementation

~~~~~~~~~~~~~~

Security Domains

~~~~~~~~~~~~~~~~

1. Public: ``0755`` respectively ``0644``

2. Ganeti wide: shared between the daemons (gntdaemons)

So for point 3 this tables shows the correlation of the sets to groups

and their users:

Set Group      Users                          Description

=== ========== ============================== ==========================

A   gntrapi    gntrapi, gntmasterd            Share data between

B   gntadmins  gntrapi, gntmasterd, *users*   Shared between users who

                                              needs to call gntmasterd

C   gntconfd   gntconfd, gntmasterd           Share data between

D   gntmasterd gntmasterd                     masterd only; Currently

                                              only to redistribute the

                                              configuration, has access

  gnt-node {add|remove}

  gnt-instance {console}

permissions.

Assuming it follows the defaults: ``gnt${daemon}`` for user and