Let me expand on the reasons for our wish to deploy the
cookbooks from S3:
1) Stability: S3 has better availability than Github. We've seen
instances that failed to start because of a Github outage.
2) Flexibility: We would like to have all source code for our
systems in a single repository, including the cookbooks. But
currently we cannot easily do this as Scalarium needs the cookbooks
to be top-level in a separate repository.
3) Speed: As the size and history of our cookbook repository grows,
so does the startup time of our instances.
To sum up: We would love to see cookbook deployment from S3.
That is a newly created cloud right? We didn't rollout this
feature globally yet, just to all Infopark accounts which is
restricted to existing clouds. Every new cloud will get the default
agent with the old code. We will make this the default over the
I updated this new cloud to use the updated agent too, so it
should work now.