commit | 793bb7609adbfb7a8bfb98257d28ed180dbea4ba | [log] [tgz] |
---|---|---|
author | Luciano P. Sabenca(luciano.sabenca@movile.com) <luciano.sabenca@movile.com> | Mon Jul 14 13:58:38 2014 -0300 |
committer | Ignasi Barrera <nacx@apache.org> | Mon Jul 28 15:31:11 2014 +0200 |
tree | 1765642c8b4a0d5200a8186889ee24082ad70e44 | |
parent | d3019282e94279ff885e60a3be07af83468a782d [diff] |
JCLOUDS-624 - Fixed bug in ListNodes To fix this bug, I used the approach debated in the above issue: create new methods to do the operation using an ExecutorService provided by the user.The the old methods are still working, but now the operations in those methods are not concurrent anymore.
This is the jclouds Chef API. It provides access to the different flavours of the Chef server API:
It currently supports versions 0.9, 0.10 and 11 of the standard Chef server APIs, and an initial and very basic (still in progress) implementation of the user and organization API of the Enterprise Chef.
Also provides a set of utility methods to combine Chef features with the jclouds Compute service, allowing users to customize the bootstrap process and manage the configuration of the deployed nodes.
You will find all documentation in www.jclouds.org