Revision fd07c6b3
b/doc/admin.rst | ||
---|---|---|
1 | 1 |
Ganeti administrator's guide |
2 | 2 |
============================ |
3 | 3 |
|
4 |
Documents Ganeti version 2.0
|
|
4 |
Documents Ganeti version |version|
|
|
5 | 5 |
|
6 | 6 |
.. contents:: |
7 | 7 |
|
... | ... | |
173 | 173 |
gnt-backup import -n TARGET_NODE -t DISK_TEMPLATE \ |
174 | 174 |
--src-node=NODE --src-dir=DIR INSTANCE_NAME |
175 | 175 |
|
176 |
Most of the options available for the command *gnt-instance add* are
|
|
177 |
supported here too. |
|
176 |
Most of the options available for the command :command:`gnt-instance
|
|
177 |
add` are supported here too.
|
|
178 | 178 |
|
179 | 179 |
High availability features |
180 | 180 |
-------------------------- |
... | ... | |
262 | 262 |
in the same way. |
263 | 263 |
|
264 | 264 |
Accessing an instance's console |
265 |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
|
265 | 266 |
|
266 | 267 |
The command to access a running instance's console is:: |
267 | 268 |
|
... | ... | |
281 | 282 |
Cluster-wide debugging |
282 | 283 |
~~~~~~~~~~~~~~~~~~~~~~ |
283 | 284 |
|
284 |
The *gnt-cluster* command offers several options to run tests or
|
|
285 |
execute cluster-wide operations. For example:: |
|
285 |
The :command:`gnt-cluster` command offers several options to run tests
|
|
286 |
or execute cluster-wide operations. For example::
|
|
286 | 287 |
|
287 | 288 |
gnt-cluster command |
288 | 289 |
gnt-cluster copyfile |
... | ... | |
291 | 292 |
gnt-cluster getmaster |
292 | 293 |
gnt-cluster version |
293 | 294 |
|
294 |
See the man page *gnt-cluster* to know more about their usage. |
|
295 |
See the man page :manpage:`gnt-cluster` to know more about their usage. |
b/doc/design-2.0.rst | ||
---|---|---|
1558 | 1558 |
|
1559 | 1559 |
These are only the basic variables we are thinking of now, but more |
1560 | 1560 |
may come during the implementation and they will be documented in the |
1561 |
``ganeti-os-api`` man page. All these variables will be available to
|
|
1562 |
all scripts. |
|
1561 |
:manpage:`ganeti-os-api` man page. All these variables will be
|
|
1562 |
available to all scripts.
|
|
1563 | 1563 |
|
1564 | 1564 |
Some scripts will need a few more information to work. These will have |
1565 | 1565 |
per-script variables, such as for example: |
b/doc/iallocator.rst | ||
---|---|---|
223 | 223 |
|
224 | 224 |
No allocations should be made on nodes having either the ``drained`` |
225 | 225 |
or ``offline`` flags set. More details about these of node status |
226 |
flags is available in the manpage *ganeti(7)*.
|
|
226 |
flags is available in the manpage :manpage:`ganeti(7)`.
|
|
227 | 227 |
|
228 | 228 |
|
229 | 229 |
Respone message |
b/doc/install.rst | ||
---|---|---|
1 | 1 |
Ganeti installation tutorial |
2 | 2 |
============================ |
3 | 3 |
|
4 |
Documents Ganeti version 2.0
|
|
4 |
Documents Ganeti version |version|
|
|
5 | 5 |
|
6 | 6 |
.. contents:: |
7 | 7 |
|
... | ... | |
450 | 450 |
apt-get install debootstrap dump kpartx |
451 | 451 |
|
452 | 452 |
Alternatively, you can create your own OS definitions. See the manpage |
453 |
*ganeti-os-interface*.
|
|
453 |
:manpage:`ganeti-os-interface`.
|
|
454 | 454 |
|
455 | 455 |
Initializing the cluster |
456 | 456 |
++++++++++++++++++++++++ |
Also available in: Unified diff