David Lutterkort wrote:
On Thu, 2009-07-09 at 16:21 -0400, Itamar Heim wrote:
On the general discussion - yes, stateless is great. Yet there aren't a lot of stateless projects/organization out there.
That's a very important lesson we learned with the stateless project[1]
- for some applications and some users it's a perfect fit and exactly
what they want, but for many others it's not.
This requires educating the market, and is viewed more as a deficiency of ec2 that a philosophy. There are various use cases of cloud, if we are discussing self provisioning, we can't expect any user will know to configure everything in stateless, configure shared/network storage for files/db/etc.
In the general case, it takes a serious amount of work to make a stateless deployment work; in my mind the issue of stateless/stateful VM's is orthogonal to cloud, I don't see it as directly related to cloud as Bob does. (Don't get me wrong, I would love if the world consisted of stateless machines all with properly managed setups and configurations)
We should keep in mind that libcloud will have to follow what users want and use, and we should not design something like 'all VM's are stateless' into the API.
To get the API started, it's perfectly fine to only support the EC2 stateless model, but we need to keep an open mind as we encounter other clouds.
I say make it a parameter at creation, and let impls throw exceptions.
-- bk