On Wed, May 01, 2013 at 08:40:22PM +0200, Martijn Rijkeboer wrote:
> 
> > Trying to work through the tutorial with this and I'm a bit confused
> > about where files are being installed. This isn't helped by the tutorials
> > seeming to be for older versions (we can't really do much about that),
> > but the current set of @samples don't seem to make a lot of sense,
> > I'll see if I can work out what's going on, but I get the impression
> > @sample'ing things into inputs/ is fairly wrong..
> 
> I agree that @sample'ing files is fairly wrong, but some people were really
> strong about it. I would rather instruct the user in the README how to do
> a basic setup or refer to the "Cfengine Quick Start Guide".

I was one of those 'strong' 'coz community cfengine doesn't need any
manual action, so why do we need it?

Anyway, if a user should do something manually, then guarantee
pkg tools won't scream bullshit about some file unable to delete.

> It could be as simple as:
> 
>   To setup a policy hub perform the following steps:
>   1. Create key-pair and necessary directories by executing cf-key
>   2. Copy sample configuration files to /var/cfengine/masterfiles
>   3. Edit configuration files accordingly
>   4. Bootstrap hub with cf-agent --bootstrap --policy-server <own IP>
    ^ why is this in policy hub if this is client? yes, even policy hub
      would like to have agent but if you want to make such steps then
      move them to right section

>   To setup a client perform the following steps:
>   1. Create key-pair and necessary directories by executing cf-key
>   2. Bootstrap client with cf-agent --bootstrap --policy-server <hub IP>
> 
> During bootstrapping the files are copied from the masterfiles directory
> on the policy host to the inputs directory on the clients. When the files
> are successfully copied the host is bootstrapped.

If you want to have a polichy hub... ;)

Please let it be commited, only if it would be in the ports tree
more people using OpenBSD could help and test.

jirib

Reply via email to