[shykes]

That's exactly what Cloudlets does. http://github.com/dotcloud/cloudlets

[PabloOsinaga]

That's nice. seems to be the infrastructure required for building such system. question is how do you come about building the manifests? Users need to do that???

[sayhello]

I think there needs to be a higher level abstraction.

Blueprint is a nice step in that direction: make a change and dump out the environment.

Perhaps what we need is a system that compiles to that manifest, or to chef/puppet.

Setting up systems is a complex task that neither puppet nor chef solve, they make it less daunting, but it still is a real pain to do so!

[PabloOsinaga]

or is your perspective that something as simple as this https://github.com/dotcloud/cloudlets/blob/master/sample.clo...

would work?

Wound't the system become a nightmare once I start installing/changing stuff in the machine in a very organic way?

Meaning, I'd have to go and maintain that manifest???

[shykes]

In practice, most of the work happens in the base image. Future versions simply extend the manifest with a few extra lines.

Ideally you want to "compile down" to cloudlets. With smart change management tools you can make it really simple for the user. That sounds exactly like Stackrocket's cup of tea :)

[PabloOsinaga]

OK - I see. This is a PaaS play in a way, but one that offers a bit more of flexibilty/componentization than the "traditional" PaaS's

I was thinking more along the lines of something truly generic.

[sayhello]

Didn't see your comment. Yes indeed, that's exactly what we're working towards =)