Updated the man pages for the cdist trigger and preos
This commit is contained in:
parent
eb78d9b034
commit
66db5acc32
2 changed files with 6 additions and 4 deletions
|
@ -26,7 +26,7 @@ For example, to create ubuntu PreOS:
|
||||||
|
|
||||||
$ cdist preos ubuntu /preos/preos-ubuntu -b -C \
|
$ cdist preos ubuntu /preos/preos-ubuntu -b -C \
|
||||||
-k ~/.ssh/id_rsa.pub -p /preos/pxe-ubuntu \
|
-k ~/.ssh/id_rsa.pub -p /preos/pxe-ubuntu \
|
||||||
-t "/usr/bin/curl 192.168.111.5:3000/install/"
|
-t "/usr/bin/curl 192.168.111.5:3000/cdist/install/"
|
||||||
|
|
||||||
For more info about available options see cdist manual page.
|
For more info about available options see cdist manual page.
|
||||||
|
|
||||||
|
@ -156,7 +156,7 @@ Tipical use case for using PreOS and trigger command include the following steps
|
||||||
|
|
||||||
$ cdist preos ubuntu /preos/ubuntu -b -C \
|
$ cdist preos ubuntu /preos/ubuntu -b -C \
|
||||||
-k ~/.ssh/id_rsa.pub -p /preos/pxe \
|
-k ~/.ssh/id_rsa.pub -p /preos/pxe \
|
||||||
-t "/usr/bin/curl 192.168.111.5:3000/install/"
|
-t "/usr/bin/curl 192.168.111.5:3000/cdist/install/"
|
||||||
|
|
||||||
#. Configure dhcp server and tftp server.
|
#. Configure dhcp server and tftp server.
|
||||||
|
|
||||||
|
|
|
@ -13,8 +13,10 @@ This command starts trigger server at management node, for example:
|
||||||
This will start cdist trigger server in verbose mode. cdist trigger server accepts
|
This will start cdist trigger server in verbose mode. cdist trigger server accepts
|
||||||
simple requests for configuration and for installation:
|
simple requests for configuration and for installation:
|
||||||
|
|
||||||
* :strong:`/cdist/install/.*` for installation
|
* :strong:`/cdist/install/` for installation
|
||||||
* :strong:`/cdist/config/.*` for configuration.
|
* :strong:`/cdist/config/` for configuration.
|
||||||
|
|
||||||
|
Other configuration parameters are the same as in like cdist config (See `cdist <man1/cdist.html>`_).
|
||||||
|
|
||||||
Machines can then trigger cdist trigger server with appropriate requests.
|
Machines can then trigger cdist trigger server with appropriate requests.
|
||||||
If the request is, for example, for installation (:strong:`/cdist/install/`)
|
If the request is, for example, for installation (:strong:`/cdist/install/`)
|
||||||
|
|
Loading…
Reference in a new issue