chef-rundeck
chef-rundeck copied to clipboard
oswaldlabs
Adding an option to get only envs and nodes.
Adding a env_node_only (i.e. -e) option. Uses the Chef RESTful API to first get envs, and their nodes. This is faster than getting all node objects and querying them. Allows hundreds of Chef nodes to be available in Rundeck quickly.
Cost:
- Some information is lost (e.g. machine type etc.).
- Machine name is set to unix for any machine.
Usage example: sudo ./chef-rundeck -c /home/chef/.chef/knife.rb -u username -w http://servername:4040 -e
PS: I am new to git/ruby
Hi, I dont work with Chef /Rundeck in my current job and am not up to date on the latest changes. However have received mails from a couple of people asking how to access the PR (since it was closed). The Rundeck bridge was very slow for more than a couple of hundred nodes. We had this problem for the couple of hundred Windows nodes which were coordinated from Rundeck, and so I had to add this switch*. Cc'ing Etienne, who sent a mail few weeks back, in case he has any input on whether the PR was useful. Thanks, Sriram
- https://groups.google.com/forum/#!topic/rundeck-discuss/7b0xHnJpfP8
On Mon, Aug 19, 2013 at 1:16 PM, Brian Scott [email protected]:
@sriramgd https://github.com/sriramgd @josephholstenhttps://github.com/josephholsten @leftathome https://github.com/leftathome Do we still need this PR?
— Reply to this email directly or view it on GitHubhttps://github.com/oswaldlabs/chef-rundeck/pull/10#issuecomment-22888207 .
Anecdotal evidence suggests that supporting partial search has solved this issue for others, and doesn't introduce a significantly different collection / rendering code path in the process. My preference is to stick with that approach. Objections?
