[[cfengine3]]
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
docpublic:systemes:linux:cfengine3 [2013/07/19 13:21] PROCACCIA [install client] |
docpublic:systemes:linux:cfengine3 [2013/12/24 15:14] (current) procacci@tem-tsp.eu [references] |
||
|---|---|---|---|
| Line 18: | Line 18: | ||
| * http:// | * http:// | ||
| * http:// | * http:// | ||
| + | * https:// | ||
| ===== install server ===== | ===== install server ===== | ||
| Line 93: | Line 94: | ||
| ===== install client ===== | ===== install client ===== | ||
| - | here we install manually cfengine package on the client (next we'll do it automatically via [[.: | + | here we install manually cfengine package on the client (next we'll do it [[.: |
| < | < | ||
| Line 456: | Line 457: | ||
| * https:// | * https:// | ||
| + | in our kickstart template we call 2 snippets to do the job | ||
| + | < | ||
| + | [root@cobbler2 cobbler]# grep disi kickstarts/ | ||
| + | $SNIPPET(' | ||
| + | $SNIPPET(' | ||
| + | </ | ||
| + | those snippet repectlively install cfengine and then bootstrap the client the easy way since the version 3.2.0, if you are willing to automatically accept keys from the clients , cf http:// | ||
| + | |||
| + | < | ||
| + | [root@cobbler2 snippets]# cat disi_post_install_packages | ||
| + | yum -y install cfengine-community | ||
| + | yum -y install autofs | ||
| + | |||
| + | [root@cobbler2 snippets]# cat disi_cfengine_bootstrap | ||
| + | # start cfengine3 registration | ||
| + | / | ||
| + | # end cfengine3 registration | ||
| + | </ | ||
