Re:Migrating away from Puppet to cdist (Python3)
by Game_Ender on Wednesday January 04, 2012 @12:54AM
(#3422997)
It appears that all the target configuration is done the old fashioned way with shell scripts run on the target machine. The Python3 code runs on the hose machine and decides what scripts to run where. The code base (according to sloccount) is 55% python and 45% shell.
Re:Migrating away from Puppet to cdist (Python3)
by viraptor on Wednesday January 04, 2012 @03:52AM
(#3423339)
I looked through the docs, but couldn't find anything interesting regarding exchanging data between nodes. Everything seems to be isolated and the only real exchange seems to be possible in local script generators. How do you do stuff like "find all running frontend nodes and put them into this config file", or "find a database node and create a config with credentials valid for that node" using cdist?
Re:Migrating away from Puppet to cdist (Python3)
by eolamey on Thursday January 05, 2012 @04:54AM
(#3428114)
I haven't looked at puppet in a while, but I think this feature is only possible in chef, where each node can execute search queries on the chef server. It is actually one of the reasons I prefer chef to puppet.
I guess since the developers of the tools are coming from the puppet world, they did not think about implementing it.
Wether this kind of feature should be implemented in the CM tool is another debate :)
Re:Migrating away from Puppet to cdist (Python3)
by subway on Thursday January 05, 2012 @05:28AM
(#3428176)
Puppet provides a mechanism called Exported Resources allowing nodes to provide bits of config for use by other nodes. For example I presently export Nagios check resources for webservices on my web nodes, which are collected by my Nagios server for building it's config.
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?
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.
We searched and found cdist. We're very much enjoying it. The reasons he lists for switching against Puppet resonated with me very much.
Plus, it's written in Python3, which might be a turn off for some, but it's a pretty cool demonstration that python3 is making its way in the wild.