[chef] Re: Re: Re: Re: Re: remote Node concept?

[Adam Jacob < >]

On Mon, Apr 12, 2010 at 7:28 AM, Patrick Debois 
<
 >
 wrote:
> Msf,
>
> From what I read from your mail, this is what I was thinking: making
> run_command, open4, system and so one ssh/remote aware. The caveat is that a
> lot of logic in scripts is handled by ruby internal code that you can't
> simply make ssh aware unless you implement it as a command line (f.i. copy
> files over ssh (handled in ruby code) instead of 'scp ...' command).
> Therefore I was thinking of flagging recipes with the remote execute
> capability flag : meaning it handles everything by commandline commands.
>
> Anyone else interested?

I think this is probably dangerous, and at the very least fraught with
peril - and also, it might be totally awesome.

What I don't understand is where the use case is.  If the issue is
that the devices themselves are closed (say a switch, or a load
balancer, etc.) a smaller amount of effort could probably be expended
to get a full fledged Chef resource and provider that work for the
device.

It feels to me like what you want is a mash-up of what Capistrano
provides (in terms of push-ability and quick hacking) and the
resources that exist in Chef.  Which you can have, but the easy path
would be to have ruby on the devices under management.

Is the real problem here just that you don't want ruby installed everywhere?

Adam

-- 
Opscode, Inc.
Adam Jacob, CTO
T: (206) 508-7449 E: