Correct, if you wish to automate against PB you would need to leverage a custom image that precludes the password change requirement; however, I believe they are moving towards supporting things such as SSH keys, user-data via cloud-init, and other things that would alleviate this long term. It certainly puts a wrinkle in any full automation.
At the moment, we're building the tooling that would allow automation to start to happen -- working in things like Ansible, Libcloud, Fog, along with base libraries for their current API. Currently, users build custom images and then automate against the API if doing infrastructure automation. On Tue, Mar 31, 2015 at 1:40 PM, Ignasi Barrera <[email protected]> wrote: > Option 2 sounds like the way to go. If we do that, then any user that > wants to automate stuff when deploying to ProfitBricks with jclouds will > have to use a custom image that should have been created before, right? > Out of curiosity, how are your users (PB users) automating stuff? > > Thanks for joining the discussion and for your help @baldwinSPC > <https://github.com/baldwinSPC>! > > — > Reply to this email directly or view it on GitHub > <https://github.com/jclouds/jclouds-labs/pull/145#issuecomment-88237905>. > --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/pull/145#issuecomment-88494446
