From: libcloud-list-bounces@redhat.com [mailto:libcloud-list- bounces@redhat.com] On Behalf Of Bob McWhirter I think that'd make sense.
Would it make sense (or be possible) to make RHEV-M non-persist until/ unless someone triggers a 'persist' operation?
[IH] it does today.
And for RHEV-M, would persist not just save the image, but blow it into the template library, similar to how bundling puts it into the image library in EC2?
[IH] RHEV-M supports both modes. But even for stateless VMs, it still creates an instance for them (COW from the template), since you are not supposed to launch same VM multiple times with exact same parameters. For Linux, you can configure this as pxe/parameters/etc. For windows, it is a bit harder, since for domain membership, you need to "initialize" each VM and join it to the domain, exchange passwords for the computer account, etc. We can abstract this differentiation in an external API, but for "regular" virtualization use cases, it is needed. (and don't forget all "regular" virtualization use cases are also called "cloud" today, since it is the current buzz)