In a traditional model, i think it would do. But here we are trying to acheive following. 1. No copy from any source to ephimeral storage of hypervisor 2. Boot time less than a minute for 750 gb image 3. Image will be updated ever 5 minutes(close to cdp) 4. Image coming from zfs store So typically we want to boot directly from a zfs clone, which needs file kind of an access.since that was blocked due to security reasons, we are thinking if we can some how restrict and build some kind of whitelisting mechanism to take file access.. Sent from Samsung tablet -------- Original message -------- From Caitlin Bestler <caitlin.bestler at nexenta.com> Date: 16/10/2013 22:22 (GMT+05:30) To openstack at lists.openstack.org Subject Re: [Openstack] [openstack][nova][glance] Avoid Image Copying On 10/16/2013 2:58 AM, Srujana C P wrote: > Hi, > > We have a requirement wherein we will clone an image and register the > cloned image into glance from file location using x-image-meta-location. > However, file location option has been removed for security reasons. > > So, We are planning to include two parameters in glance.conf , which > enables file access according to configurable parameter and allow access > to specific directories. > Why isn't the ability to clone cinder volumes an adequate solution for this? That capability already exists. _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack at lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack/attachments/20131016/ee77ce47/attachment.html>