Synnefo » snf-ganeti » ganeti-local

``plj0`` is a fourcc that details the message content. It stands for plain

- ``msg`` contains a JSON-encoded query, its fields are:

  - ``protocol``, integer, is the confd protocol version (initially

    just ``constants.CONFD_PROTOCOL_VERSION``, with a value of 1)

  - ``type``, integer, is the query type. For example "node role by

    name" or "node primary ip by instance ip". Constants will be

    provided for the actual available query types

  - ``query`` is a multi-type field (depending on the ``type`` field):

    - it can be missing, when the request is fully determined by the

      ``type`` field

    - it can contain a string which denotes the search key: for

      example an IP, or a node name

    - it can contain a dictionary, in which case the actual details

      vary further per request type

  - ``rsalt``, string, is the required response salt; the client must

    use it to recognize which answer it's getting.

- ``salt`` must be the current unix timestamp, according to the

  client; servers should refuse messages which have a wrong timing,

  according to their configuration and clock

- ``hmac`` is an hmac signature of salt+msg, with the cluster hmac key

- ``plj0`` the message type magic fourcc, as discussed above

- ``msg`` contains a JSON-encoded answer, its fields are:

  - ``protocol``, integer, is the confd protocol version (initially

    just constants.CONFD_PROTOCOL_VERSION, with a value of 1)

  - ``status``, integer, is the error code; initially just ``0`` for

    'ok' or ``1`` for 'error' (in which case answer contains an error

    detail, rather than an answer), but in the future it may be

    expanded to have more meanings (e.g. ``2`` if the answer is

    compressed)

  - ``answer``, is the actual answer; its type and meaning is query

    specific: for example for "node primary ip by instance ip" queries

    name" queries it will be an integer which encodes the role

    (master, candidate, drained, offline) according to constants

- ``salt`` is the requested salt from the query; a client can use it

  to recognize what query the answer is answering.

- ``hmac`` is an hmac signature of salt+msg, with the cluster hmac key