Re:Migrating away from Puppet to cdist (Python3)
by astrodust on Tuesday January 03, 2012 @11:45PM
(#3422797)
So cdist requires python on the target server, or does it somehow roll its own once hooked in? Or is Python only used for the front-end?
[ Parent
| on HN ]
Re:Migrating away from Puppet to cdist (Python3)
by FraaJad on Wednesday January 04, 2012 @12:09AM
(#3422876)
From the posted link:
> "In cdist we only use a posix shell on the target plus common UNIX tools (like find, rm, grep), as defined by POSIX."
Re:Migrating away from Puppet to cdist (Python3)
by rdtsc on Wednesday January 04, 2012 @08:40AM
(#3424030)
Presumably once they ssh in they can install python in a virtualenv or do anything they want basically. I would imagine this would be only a bootstrap problem.
Re:Migrating away from Puppet to cdist (Python3)
by rdtsc on Wednesday January 04, 2012 @11:09AM
(#3424600)
Hmm, why the downvotes?
Re:Migrating away from Puppet to cdist (Python3)
by obtu on Wednesday January 04, 2012 @11:36AM
(#3424724)
A few people have clarified what runs where, and you're ignoring them with an irrelevant and misleading point. To clarify, Python is not used on the slaves.
Re:Migrating away from Puppet to cdist (Python3)
by rdtsc on Wednesday January 04, 2012 @12:05PM
(#3424857)
I wanted to know if "doesn't run on the target" means a bootstrap dependency only. After the target has been setup for configuration I don't see a reason why Python, Ruby or anything can't be installed in a sand-boxed environment.