On Fri, Nov 9, 2012 at 4:55 PM, Swartzlander, Ben < ben.swartzlan...@netapp.com> wrote: > This sounds less like an Essex->Folsom upgrade issue and more like an old version->new version issue. We made some changes to the driver in the Folsom timeframe and backported those changes to Essex, but we never provided an upgrade path for users of the old driver to move to the new driver.
True. You would have the same problem when upgrading from Essex-created datasets to any post-Essex release. This check is on Folsom branch and (Cinder) master. It is not present on Essex branch. https://github.com/openstack/nova/blob/stable/folsom/nova/volume/netapp.py#L254 > What's needed is for a script to go through all the datasets and set the metadata field for the OpenStack project appropriately. I wrote a simple script to make few SOAP calls (attached) to update dataset meta-data. > If there are few enough datasets, this could be done manually I suppose. I would be interested to know how can you do it with existing tools ?? Regards, Brano Zarnovican PS: Even if the driver worked after metadata fix, I still could not get snapshots. We are missing "flex_clone" licence :(
-- Mailing list: https://launchpad.net/~openstack-volume Post to : openstack-volume@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-volume More help : https://help.launchpad.net/ListHelp