From: libcloud-list-bounces@redhat.com [mailto:libcloud-list- bounces@redhat.com] On Behalf Of Bryan Kearney
...
Can we assume a verb such as "persist" which in the case of EC2 will rebundle? It may be wierd since the default behaviour for RHEV-M may be persist-on.
[IH] RHEV-M support setting a node as 'stateless', which means it will not save changes. BUT, since we don't support live snapshots for now, user has to specify before launching the VM this run is not stateless so changes will be saved. Once we have live snapshots, we can go either way.
On the general discussion - yes, stateless is great. Yet there aren't a lot of stateless projects/organization out there. 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. As for use cases, If we take lab management for example, they almost always have to save state, since they want to save the snapshot with the bug that was reproduced, and associate that snapshot to BZ for a developer to be able to investigate further, etc.