hooks.rst 19.4 KB
Newer Older
1
2
3
Ganeti customisation using hooks
================================

Iustin Pop's avatar
Iustin Pop committed
4
Documents Ganeti version 2.6
5
6
7
8
9
10

.. contents::

Introduction
------------

11
12
13
14
15
In order to allow customisation of operations, Ganeti runs scripts in
sub-directories of ``@SYSCONFDIR@/ganeti/hooks``. These sub-directories
are named ``$hook-$phase.d``, where ``$phase`` is either ``pre`` or
``post`` and ``$hook`` matches the directory name given for a hook (e.g.
``cluster-verify-post.d`` or ``node-add-pre.d``).
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67

This is similar to the ``/etc/network/`` structure present in Debian
for network interface handling.

Organisation
------------

For every operation, two sets of scripts are run:

- pre phase (for authorization/checking)
- post phase (for logging)

Also, for each operation, the scripts are run on one or more nodes,
depending on the operation type.

Note that, even though we call them scripts, we are actually talking
about any executable.

*pre* scripts
~~~~~~~~~~~~~

The *pre* scripts have a definite target: to check that the operation
is allowed given the site-specific constraints. You could have, for
example, a rule that says every new instance is required to exists in
a database; to implement this, you could write a script that checks
the new instance parameters against your database.

The objective of these scripts should be their return code (zero or
non-zero for success and failure). However, if they modify the
environment in any way, they should be idempotent, as failed
executions could be restarted and thus the script(s) run again with
exactly the same parameters.

Note that if a node is unreachable at the time a hooks is run, this
will not be interpreted as a deny for the execution. In other words,
only an actual error returned from a script will cause abort, and not
an unreachable node.

Therefore, if you want to guarantee that a hook script is run and
denies an action, it's best to put it on the master node.

*post* scripts
~~~~~~~~~~~~~~

These scripts should do whatever you need as a reaction to the
completion of an operation. Their return code is not checked (but
logged), and they should not depend on the fact that the *pre* scripts
have been run.

Naming
~~~~~~

68
The allowed names for the scripts consist of (similar to *run-parts*)
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
upper and lower case, digits, underscores and hyphens. In other words,
the regexp ``^[a-zA-Z0-9_-]+$``. Also, non-executable scripts will be
ignored.


Order of execution
~~~~~~~~~~~~~~~~~~

On a single node, the scripts in a directory are run in lexicographic
order (more exactly, the python string comparison order). It is
advisable to implement the usual *NN-name* convention where *NN* is a
two digit number.

For an operation whose hooks are run on multiple nodes, there is no
specific ordering of nodes with regard to hooks execution; you should
assume that the scripts are run in parallel on the target nodes
(keeping on each node the above specified ordering).  If you need any
kind of inter-node synchronisation, you have to implement it yourself
in the scripts.

Execution environment
~~~~~~~~~~~~~~~~~~~~~

The scripts will be run as follows:

- no command line arguments

- no controlling *tty*

- stdin is actually */dev/null*

- stdout and stderr are directed to files

102
- PATH is reset to :pyeval:`constants.HOOKS_PATH`
103
104
105
106
107

- the environment is cleared, and only ganeti-specific variables will
  be left


Michael Hanselmann's avatar
Michael Hanselmann committed
108
All information about the cluster is passed using environment
109
110
111
112
113
114
115
116
117
variables. Different operations will have sligthly different
environments, but most of the variables are common.

Operation list
--------------

Node operations
~~~~~~~~~~~~~~~

118
OP_NODE_ADD
119
120
121
122
123
+++++++++++

Adds a node to the cluster.

:directory: node-add
124
:env. vars: NODE_NAME, NODE_PIP, NODE_SIP, MASTER_CAPABLE, VM_CAPABLE
125
126
127
128
:pre-execution: all existing nodes
:post-execution: all nodes plus the new node


129
OP_NODE_REMOVE
130
131
++++++++++++++

132
133
134
Removes a node from the cluster. On the removed node the hooks are
called during the execution of the operation and not after its
completion.
135
136
137
138

:directory: node-remove
:env. vars: NODE_NAME
:pre-execution: all existing nodes except the removed node
139
:post-execution: all existing nodes
140
141
142
143
144
145
146

OP_NODE_SET_PARAMS
++++++++++++++++++

Changes a node's parameters.

:directory: node-modify
147
:env. vars: MASTER_CANDIDATE, OFFLINE, DRAINED, MASTER_CAPABLE, VM_CAPABLE
148
149
150
:pre-execution: master node, the target node
:post-execution: master node, the target node

151
152
153
154
155
156
157
158
159
160
OP_NODE_MIGRATE
++++++++++++++++

Relocate secondary instances from a node.

:directory: node-migrate
:env. vars: NODE_NAME
:pre-execution: master node
:post-execution: master node

161

162
163
164
Node group operations
~~~~~~~~~~~~~~~~~~~~~

165
OP_GROUP_ADD
166
167
168
169
170
171
172
173
174
++++++++++++

Adds a node group to the cluster.

:directory: group-add
:env. vars: GROUP_NAME
:pre-execution: master node
:post-execution: master node

175
176
177
178
179
180
181
182
183
184
OP_GROUP_SET_PARAMS
+++++++++++++++++++

Changes a node group's parameters.

:directory: group-modify
:env. vars: GROUP_NAME, NEW_ALLOC_POLICY
:pre-execution: master node
:post-execution: master node

185
OP_GROUP_REMOVE
186
187
188
189
190
191
192
193
194
195
196
+++++++++++++++

Removes a node group from the cluster. Since the node group must be
empty for removal to succeed, the concept of "nodes in the group" does
not exist, and the hook is only executed in the master node.

:directory: group-remove
:env. vars: GROUP_NAME
:pre-execution: master node
:post-execution: master node

197
OP_GROUP_RENAME
198
199
200
201
202
203
204
205
206
+++++++++++++++

Renames a node group.

:directory: group-rename
:env. vars: OLD_NAME, NEW_NAME
:pre-execution: master node and all nodes in the group
:post-execution: master node and all nodes in the group

207
208
209
210
211
212
213
214
215
216
OP_GROUP_EVACUATE
+++++++++++++++++

Evacuates a node group.

:directory: group-evacuate
:env. vars: GROUP_NAME, TARGET_GROUPS
:pre-execution: master node and all nodes in the group
:post-execution: master node and all nodes in the group

217

218
219
220
221
Instance operations
~~~~~~~~~~~~~~~~~~~

All instance operations take at least the following variables:
222
INSTANCE_NAME, INSTANCE_PRIMARY, INSTANCE_SECONDARY,
223
224
225
226
227
228
229
230
231
INSTANCE_OS_TYPE, INSTANCE_DISK_TEMPLATE, INSTANCE_MEMORY,
INSTANCE_DISK_SIZES, INSTANCE_VCPUS, INSTANCE_NIC_COUNT,
INSTANCE_NICn_IP, INSTANCE_NICn_BRIDGE, INSTANCE_NICn_MAC,
INSTANCE_DISK_COUNT, INSTANCE_DISKn_SIZE, INSTANCE_DISKn_MODE.

The INSTANCE_NICn_* and INSTANCE_DISKn_* variables represent the
properties of the *n* -th NIC and disk, and are zero-indexed.


232
233
OP_INSTANCE_CREATE
++++++++++++++++++
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257

Creates a new instance.

:directory: instance-add
:env. vars: ADD_MODE, SRC_NODE, SRC_PATH, SRC_IMAGES
:pre-execution: master node, primary and secondary nodes
:post-execution: master node, primary and secondary nodes

OP_INSTANCE_REINSTALL
+++++++++++++++++++++

Reinstalls an instance.

:directory: instance-reinstall
:env. vars: only the standard instance vars
:pre-execution: master node, primary and secondary nodes
:post-execution: master node, primary and secondary nodes

OP_BACKUP_EXPORT
++++++++++++++++

Exports the instance.

:directory: instance-export
258
:env. vars: EXPORT_MODE, EXPORT_NODE, EXPORT_DO_SHUTDOWN, REMOVE_INSTANCE
259
260
261
:pre-execution: master node, primary and secondary nodes
:post-execution: master node, primary and secondary nodes

262
OP_INSTANCE_STARTUP
263
+++++++++++++++++++
264
265
266
267

Starts an instance.

:directory: instance-start
268
:env. vars: FORCE
269
270
271
272
273
274
275
276
:pre-execution: master node, primary and secondary nodes
:post-execution: master node, primary and secondary nodes

OP_INSTANCE_SHUTDOWN
++++++++++++++++++++

Stops an instance.

277
:directory: instance-stop
278
:env. vars: TIMEOUT
279
280
281
282
283
284
285
286
287
:pre-execution: master node, primary and secondary nodes
:post-execution: master node, primary and secondary nodes

OP_INSTANCE_REBOOT
++++++++++++++++++

Reboots an instance.

:directory: instance-reboot
288
:env. vars: IGNORE_SECONDARIES, REBOOT_TYPE, SHUTDOWN_TIMEOUT
289
290
291
:pre-execution: master node, primary and secondary nodes
:post-execution: master node, primary and secondary nodes

292
OP_INSTANCE_SET_PARAMS
293
++++++++++++++++++++++
294
295
296
297

Modifies the instance parameters.

:directory: instance-modify
298
:env. vars: NEW_DISK_TEMPLATE, RUNTIME_MEMORY
299
300
301
302
303
304
:pre-execution: master node, primary and secondary nodes
:post-execution: master node, primary and secondary nodes

OP_INSTANCE_FAILOVER
++++++++++++++++++++

305
Failovers an instance. In the post phase INSTANCE_PRIMARY and
306
INSTANCE_SECONDARY refer to the nodes that were repectively primary
307
and secondary before failover.
308
309

:directory: instance-failover
310
:env. vars: IGNORE_CONSISTENCY, SHUTDOWN_TIMEOUT, OLD_PRIMARY, OLD_SECONDARY, NEW_PRIMARY, NEW_SECONDARY
311
:pre-execution: master node, secondary node
Iustin Pop's avatar
Iustin Pop committed
312
:post-execution: master node, primary and secondary nodes
313
314
315
316

OP_INSTANCE_MIGRATE
++++++++++++++++++++

317
Migrates an instance. In the post phase INSTANCE_PRIMARY and
318
INSTANCE_SECONDARY refer to the nodes that were repectively primary
319
and secondary before migration.
320

321
:directory: instance-migrate
322
:env. vars: MIGRATE_LIVE, MIGRATE_CLEANUP, OLD_PRIMARY, OLD_SECONDARY, NEW_PRIMARY, NEW_SECONDARY
323
:pre-execution: master node, secondary node
Iustin Pop's avatar
Iustin Pop committed
324
:post-execution: master node, primary and secondary nodes
325
326
327
328
329
330
331
332


OP_INSTANCE_REMOVE
++++++++++++++++++

Remove an instance.

:directory: instance-remove
333
:env. vars: SHUTDOWN_TIMEOUT
334
:pre-execution: master node
Iustin Pop's avatar
Iustin Pop committed
335
:post-execution: master node, primary and secondary nodes
336
337
338
339
340
341
342
343

OP_INSTANCE_GROW_DISK
+++++++++++++++++++++

Grows the disk of an instance.

:directory: disk-grow
:env. vars: DISK, AMOUNT
Iustin Pop's avatar
Iustin Pop committed
344
345
:pre-execution: master node, primary and secondary nodes
:post-execution: master node, primary and secondary nodes
346
347
348
349
350
351
352
353
354
355
356

OP_INSTANCE_RENAME
++++++++++++++++++

Renames an instance.

:directory: instance-rename
:env. vars: INSTANCE_NEW_NAME
:pre-execution: master node, primary and secondary nodes
:post-execution: master node, primary and secondary nodes

357
358
359
360
361
362
OP_INSTANCE_MOVE
++++++++++++++++

Move an instance by data-copying.

:directory: instance-move
363
:env. vars: TARGET_NODE, SHUTDOWN_TIMEOUT
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
:pre-execution: master node, primary and target nodes
:post-execution: master node, primary and target nodes

OP_INSTANCE_RECREATE_DISKS
++++++++++++++++++++++++++

Recreate an instance's missing disks.

:directory: instance-recreate-disks
:env. vars: only the standard instance vars
:pre-execution: master node, primary and secondary nodes
:post-execution: master node, primary and secondary nodes

OP_INSTANCE_REPLACE_DISKS
+++++++++++++++++++++++++

Replace the disks of an instance.

:directory: mirrors-replace
:env. vars: MODE, NEW_SECONDARY, OLD_SECONDARY
:pre-execution: master node, primary and new secondary nodes
:post-execution: master node, primary and new secondary nodes

387
388
389
390
391
392
393
394
395
396
OP_INSTANCE_CHANGE_GROUP
++++++++++++++++++++++++

Moves an instance to another group.

:directory: instance-change-group
:env. vars: TARGET_GROUPS
:pre-execution: master node
:post-execution: master node

397

398
399
400
Cluster operations
~~~~~~~~~~~~~~~~~~

401
OP_CLUSTER_POST_INIT
402
403
++++++++++++++++++++

404
405
This hook is called via a special "empty" LU right after cluster
initialization.
406
407
408
409
410
411

:directory: cluster-init
:env. vars: none
:pre-execution: none
:post-execution: master node

412
OP_CLUSTER_DESTROY
Luca Bigliardi's avatar
Luca Bigliardi committed
413
414
++++++++++++++++++

415
416
The post phase of this hook is called during the execution of destroy
operation and not after its completion.
Luca Bigliardi's avatar
Luca Bigliardi committed
417
418
419
420
421
422

:directory: cluster-destroy
:env. vars: none
:pre-execution: none
:post-execution: master node

423
424
OP_CLUSTER_VERIFY_GROUP
+++++++++++++++++++++++
425

426
Verifies all nodes in a group. This is a special LU with regard to
427
428
429
430
431
hooks, as the result of the opcode will be combined with the result of
post-execution hooks, in order to allow administrators to enhance the
cluster verification procedure.

:directory: cluster-verify
432
:env. vars: CLUSTER, MASTER, CLUSTER_TAGS, NODE_TAGS_<name>
433
:pre-execution: none
434
:post-execution: all nodes in a group
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455

OP_CLUSTER_RENAME
+++++++++++++++++

Renames the cluster.

:directory: cluster-rename
:env. vars: NEW_NAME
:pre-execution: master-node
:post-execution: master-node

OP_CLUSTER_SET_PARAMS
+++++++++++++++++++++

Modifies the cluster parameters.

:directory: cluster-modify
:env. vars: NEW_VG_NAME
:pre-execution: master node
:post-execution: master node

456
457
Virtual operation :pyeval:`constants.FAKE_OP_MASTER_TURNUP`
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
458

459
460
This doesn't correspond to an actual op-code, but it is called when the
master IP is activated.
461
462

:directory: master-ip-turnup
463
:env. vars: MASTER_NETDEV, MASTER_IP, MASTER_NETMASK, CLUSTER_IP_VERSION
464
465
466
:pre-execution: master node
:post-execution: master node

467
468
Virtual operation :pyeval:`constants.FAKE_OP_MASTER_TURNDOWN`
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
469

470
471
This doesn't correspond to an actual op-code, but it is called when the
master IP is deactivated.
472
473

:directory: master-ip-turndown
474
:env. vars: MASTER_NETDEV, MASTER_IP, MASTER_NETMASK, CLUSTER_IP_VERSION
475
476
477
:pre-execution: master node
:post-execution: master node

478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493

Obsolete operations
~~~~~~~~~~~~~~~~~~~

The following operations are no longer present or don't execute hooks
anymore in Ganeti 2.0:

- OP_INIT_CLUSTER
- OP_MASTER_FAILOVER
- OP_INSTANCE_ADD_MDDRBD
- OP_INSTANCE_REMOVE_MDDRBD


Environment variables
---------------------

494
495
496
497
Note that all variables listed here are actually prefixed with *GANETI_*
in order to provide a clear namespace. In addition, post-execution
scripts receive another set of variables, prefixed with *GANETI_POST_*,
representing the status after the opcode executed.
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534

Common variables
~~~~~~~~~~~~~~~~

This is the list of environment variables supported by all operations:

HOOKS_VERSION
  Documents the hooks interface version. In case this doesnt match
  what the script expects, it should not run. The documents conforms
  to the version 2.

HOOKS_PHASE
  One of *PRE* or *POST* denoting which phase are we in.

CLUSTER
  The cluster name.

MASTER
  The master node.

OP_CODE
  One of the *OP_* values from the list of operations.

OBJECT_TYPE
  One of ``INSTANCE``, ``NODE``, ``CLUSTER``.

DATA_DIR
  The path to the Ganeti configuration directory (to read, for
  example, the *ssconf* files).


Specialised variables
~~~~~~~~~~~~~~~~~~~~~

This is the list of variables which are specific to one or more
operations.

535
536
537
CLUSTER_IP_VERSION
  IP version of the master IP (4 or 6)

538
539
540
INSTANCE_NAME
  The name of the instance which is the target of the operation.

541
542
543
INSTANCE_BE_x,y,z,...
  Instance BE params. There is one variable per BE param. For instance, GANETI_INSTANCE_BE_auto_balance

544
545
546
INSTANCE_DISK_TEMPLATE
  The disk type for the instance.

547
548
549
NEW_DISK_TEMPLATE
  The new disk type for the instance.

550
551
552
553
554
555
556
557
558
INSTANCE_DISK_COUNT
  The number of disks for the instance.

INSTANCE_DISKn_SIZE
  The size of disk *n* for the instance.

INSTANCE_DISKn_MODE
  Either *rw* for a read-write disk or *ro* for a read-only one.

559
560
561
562
563
564
INSTANCE_HV_x,y,z,...
  Instance hypervisor options. There is one variable per option. For instance, GANETI_INSTANCE_HV_use_bootloader

INSTANCE_HYPERVISOR
  The instance hypervisor.

565
566
567
568
569
570
571
572
573
574
575
576
INSTANCE_NIC_COUNT
  The number of NICs for the instance.

INSTANCE_NICn_BRIDGE
  The bridge to which the *n* -th NIC of the instance is attached.

INSTANCE_NICn_IP
  The IP (if any) of the *n* -th NIC of the instance.

INSTANCE_NICn_MAC
  The MAC address of the *n* -th NIC of the instance.

577
578
579
INSTANCE_NICn_MODE
  The mode of the *n* -th NIC of the instance.

580
581
582
583
INSTANCE_OS_TYPE
  The name of the instance OS.

INSTANCE_PRIMARY
584
585
586
587
  The name of the node which is the primary for the instance. Note that
  for migrations/failovers, you shouldn't rely on this variable since
  the nodes change during the exectution, but on the
  OLD_PRIMARY/NEW_PRIMARY values.
588

589
INSTANCE_SECONDARY
590
591
592
593
  Space-separated list of secondary nodes for the instance. Note that
  for migrations/failovers, you shouldn't rely on this variable since
  the nodes change during the exectution, but on the
  OLD_SECONDARY/NEW_SECONDARY values.
594
595
596
597
598
599
600
601
602
603

INSTANCE_MEMORY
  The memory size (in MiBs) of the instance.

INSTANCE_VCPUS
  The number of virtual CPUs for the instance.

INSTANCE_STATUS
  The run status of the instance.

604
605
606
607
608
609
MASTER_CAPABLE
  Whether a node is capable of being promoted to master.

VM_CAPABLE
  Whether the node can host instances.

610
611
612
613
614
615
MASTER_NETDEV
  Network device of the master IP

MASTER_IP
  The master IP

616
617
618
MASTER_NETMASK
  Netmask of the master IP

619
620
621
INSTANCE_TAGS
  A space-delimited list of the instance's tags.

622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
NODE_NAME
  The target node of this operation (not the node on which the hook
  runs).

NODE_PIP
  The primary IP of the target node (the one over which inter-node
  communication is done).

NODE_SIP
  The secondary IP of the target node (the one over which drbd
  replication is done). This can be equal to the primary ip, in case
  the cluster is not dual-homed.

FORCE
  This is provided by some operations when the user gave this flag.

IGNORE_CONSISTENCY
  The user has specified this flag. It is used when failing over
  instances in case the primary node is down.

ADD_MODE
  The mode of the instance create: either *create* for create from
  scratch or *import* for restoring from an exported image.

SRC_NODE, SRC_PATH, SRC_IMAGE
  In case the instance has been added by import, these variables are
  defined and point to the source node, source path (the directory
  containing the image and the config file) and the source disk image
  file.

NEW_SECONDARY
  The name of the node on which the new mirror component is being
654
655
656
  added (for replace disk). This can be the name of the current
  secondary, if the new mirror is on the same secondary. For
  migrations/failovers, this is the old primary node.
657
658

OLD_SECONDARY
659
  The name of the old secondary in the replace-disks command. Note that
660
  this can be equal to the new secondary if the secondary node hasn't
661
662
663
664
665
666
  actually changed. For migrations/failovers, this is the new primary
  node.

OLD_PRIMARY, NEW_PRIMARY
  For migrations/failovers, the old and respectively new primary
  nodes. These two mirror the NEW_SECONDARY/OLD_SECONDARY variables
667

668
669
670
EXPORT_MODE
  The instance export mode. Either "remote" or "local".

671
672
673
674
675
676
677
678
679
680
EXPORT_NODE
  The node on which the exported image of the instance was done.

EXPORT_DO_SHUTDOWN
  This variable tells if the instance has been shutdown or not while
  doing the export. In the "was shutdown" case, it's likely that the
  filesystem is consistent, whereas in the "did not shutdown" case,
  the filesystem would need a check (journal replay or full fsck) in
  order to guarantee consistency.

681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
REMOVE_INSTANCE
  Whether the instance was removed from the node.

SHUTDOWN_TIMEOUT
  Amount of time to wait for the instance to shutdown.

TIMEOUT
  Amount of time to wait before aborting the op.

OLD_NAME, NEW_NAME
  Old/new name of the node group.

GROUP_NAME
  The name of the node group.

NEW_ALLOC_POLICY
  The new allocation policy for the node group.

699
700
701
702
703
704
CLUSTER_TAGS
  The list of cluster tags, space separated.

NODE_TAGS_<name>
  The list of tags for node *<name>*, space separated.

705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
Examples
--------

The startup of an instance will pass this environment to the hook
script::

  GANETI_CLUSTER=cluster1.example.com
  GANETI_DATA_DIR=/var/lib/ganeti
  GANETI_FORCE=False
  GANETI_HOOKS_PATH=instance-start
  GANETI_HOOKS_PHASE=post
  GANETI_HOOKS_VERSION=2
  GANETI_INSTANCE_DISK0_MODE=rw
  GANETI_INSTANCE_DISK0_SIZE=128
  GANETI_INSTANCE_DISK_COUNT=1
  GANETI_INSTANCE_DISK_TEMPLATE=drbd
  GANETI_INSTANCE_MEMORY=128
  GANETI_INSTANCE_NAME=instance2.example.com
  GANETI_INSTANCE_NIC0_BRIDGE=xen-br0
  GANETI_INSTANCE_NIC0_IP=
  GANETI_INSTANCE_NIC0_MAC=aa:00:00:a5:91:58
  GANETI_INSTANCE_NIC_COUNT=1
  GANETI_INSTANCE_OS_TYPE=debootstrap
  GANETI_INSTANCE_PRIMARY=node3.example.com
729
  GANETI_INSTANCE_SECONDARY=node5.example.com
730
731
732
733
734
735
  GANETI_INSTANCE_STATUS=down
  GANETI_INSTANCE_VCPUS=1
  GANETI_MASTER=node1.example.com
  GANETI_OBJECT_TYPE=INSTANCE
  GANETI_OP_CODE=OP_INSTANCE_STARTUP
  GANETI_OP_TARGET=instance2.example.com
736
737

.. vim: set textwidth=72 :
738
739
740
741
.. Local Variables:
.. mode: rst
.. fill-column: 72
.. End: