| commit | 7f029db1c7b618494b47adb39d04aebebec726c3 | [log] [tgz] |
|---|---|---|
| author | Ignasi Barrera <ignasi.barrera@abiquo.com> | Tue May 14 08:28:56 2013 +0200 |
| committer | Ignasi Barrera <ignasi.barrera@abiquo.com> | Tue May 14 23:39:45 2013 +0200 |
| tree | ee12f95a96085c425c69bb3a95e075bb02fb5aa8 | |
| parent | 8a1a423c455ed0511094a7cbc1a9b32074b4795e [diff] |
JCLOUDS-3: Bootstrap nodes in a custom environment Added the environment where the nodes in a group must be created in the bootstrap data bag. This way the configuration is persisted and can be used between runs, such as the node run list. To accomodate the new bootstrap parameter, the method in the ChefService used to create the data bag has been refactored and a the new BootstrapConfig object has been created. This way, we'll be able to extend the information in the bootstrap databag in the future without changing the ChefService interface.
This is the jclouds Chef api. It provides access to the different flavours of the Chef server api:
It currently supports versions 0.9 and 0.10 of the standard Chef server apis, and an initial and very basic (still in progress) implementation of the user and organization api of the Hosted and Private Chef flavours.
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