← Back to team overview

openstack team mailing list archive

Re: Migrate volume from Essex to Folsom

 

Pablo,

All the logic for device mappings its on the database, so be sure to
replicate (carefull no to overlap volumes id) all your volume data from the
table :

- volumes
- volumes metadata

An the most important one:

- block_device_mappings

On this tables is where actually resides the conection parameters for the
LUN and the connection method (driver specs)

{"driver_volume_type": "iscsi", "data": {"device_path":
"/dev/disk/by-path/ip-10.1.1.100:3260-iscsi-iqn.1992-08.com.netapp:sn.1874337601-lun-0",
"target_discovered": false, "target_iqn":
"iqn.1992-08.com.netapp:sn.1874337601", "target_portal": "10.1.1.100:3260",
"volume_id": 26, "target_lun": "0"}}

This info is what nova uses to trigger the isciadm commands to attach the
lun to the VM when volume_attach() is called,

And dont you forget to respect all the metadata and types values on the
tables:

volume_types
volume_types_extra_specs

And the values matches the ones that you have dumped on the migrated volume

With all of this you should be good to go without issues

Best

Lean
Mercadolibre Cloudbuilders Team


On Wed, Jul 3, 2013 at 6:24 PM, pablo fernandez
<fernandezpablo85@xxxxxxxxx>wrote:

> Hi list!
>
> I'm working on a company that has 2 openstack clouds, an essex
> installation and a folsom one. I'm trying to migrate a netApp volume from
> one to the other, checking the required fields in the database to copy the
> metadata. Obviously both volumes would be detached.
>
> Any advice on this? Has somebody already tried it (and hopefully
> succeeded). It's really important for us in order to upgrade our openstack
> version, you'll understand it's impossible for us to do a "flip-the-switch"
> migration.
>
> Thanks a lot.
>
> Pablo
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>

Follow ups

References