Le 18/07/2013 23:38, Harry Hoffman a écrit :

Sorry, it was typed very quickly. Go to the cfengine site and find their yum repository link.
Take the URL from there and use it to add a local repo in cobbler. Make sure to select "keep local".
Then you'll have a cfengine repo. Edit your profile and add the repo from available repos to included repos.
Then choose cfengine-community in your package selection in the kickstart, at either the profile or system level.
Make sense? I might have some cobbler terms wrong, I'm on the train and not looking at it directly.

Ok, I did my own local repo containing cfengine-community package and added it to my cobbler profile .
the thing that I was missing is that I added the installation of cfengine-community package in %package section of the kickstart template for that profile, and it kept telling me that cfengine-community package installation was skiped because not present ! then I realised that it needed to be put in post install snippet, when my local repository could finally be known by the installed system . now it works fine .

 After the package is installed you need a snippet to have it bootstrap. Since this is a post install step the package is already installed so you just need to call cf-agent like you show below.
I believe you still need either a failsafe or update cf file on the installed system. I can check if you need.

since 3.2.0 there's no need to copy failsafe or update cf file, cf footnote at http://blog.normation.com/en/2012/01/03/interactive-key-exchange-with-cfengine/
"Since the version 3.2.0, if you are willing to automatically accept keys from the clients on the servers, you don’t need to copy any promises on the client, the bootstrap procedure from the Nova edition has been backported in the community edition; and it uses its own embedded promises"

I documented my own way to do it at:
http://www-public.it-sudparis.eu/~procacci/dok/doku.php?id=docpublic:systemes:linux:cfengine3&#bootstrap_cfengine_from_cobbler

thanks

Cheers,
Harry

jehan procaccia <jehan.procaccia@tem-tsp.eu> wrote:

it's not clear to what you mean by "add a repo line" !?
what I did so far is put cfengine rpm package into cobbler this way:

[root@cobbler2 f19-x86_64-perso]# ls
cfengine-community-3.5.1-1.x86_64.rpm
[root@cobbler2 f19-x86_64-perso]# createrepo .
#cobbler repo add --name=f19-x86_64-perso 
--mirror=/var/www/cobbler/repo_mirror/f19-x86_64-perso

is it why you meant by "add a repo line" ?
now for the 1st step, where can I tell the install process to install 
that package ? in cobbler , in kickstart, how ?

regarding the next step (2) => bootstrap the cfengine client, in 
cfengine3 is it really necessary to copy failsafe.cf ?
a /var/cfengine/bin/cf-agent --bootstrap --policy-server X.X.X.X would 
be enough no ?
but again, how can I tell cobbler to run that step2  after step1 
(install cfengine package) is completed ?

thanks .
Le 18/07/2013 22:27, Harry Hoffman a écrit :

Hi Jehan,

Add a repo line for the cfengine repository,

Assuming a cfengine3 deployment copy over your failsafe.cf (via a
snippet) to bootstrap the process


Cheers,
Harry

On 07/18/2013 04:08 PM, jehan procaccia wrote:

I use cobbler 2.4 to install fedora19 stations
I want to be able to install cfengine (todays latest rpm package 3.5.1)
via cobbler .
what is the best practice to do that ?
I suspect the necessity of:
1) a personnal/local repository containing cfengine-3.5.1 package
2) a snippet or post install to force a yum install of cfengine from
that repo
3) a post install script command to bootstrap the client station
(register the client to cfengine policyserver)
I also heard of triggers ... is there a documentation/howto do that ?
Thanks.
_______________________________________________
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler

_______________________________________________
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler