Independent Database for Driver

asked 2013-12-09 04:54:21 -0600

amolj-1306 gravatar image

Some driver might need to store the mapping between the ID of volume fomr the backend service and Cinder Volume ID. This can be incorporated as being one field in the existing database volumes table (e.g. provider_id?) or can have a separate database of its own to store some more information. Just like plugins in neutron have their own database can the driver in the cinder have their own database?

edit retag flag offensive close merge delete

3 answers

Sort by ยป oldest newest most voted

answered 2013-12-17 08:30:27 -0600

amolj-1306 gravatar image

Thanks John Griffith, that solved my question.

edit flag offensive delete link more

answered 2013-12-13 15:30:07 -0600

The concept of each driver having it's own DB or DB table even is something we've tried to avoid and I'd like to continue to do so. There are a number of ways to map ID's between the backend device and Cinder.

One common method is to use the Cinder-UUID for the volume-name on the backend. Another option that some folks have used is to create a mapping using VolumeAdminMetadata

edit flag offensive delete link more

answered 2013-12-16 09:51:10 -0600

amolj-1306 gravatar image

There is only one method inside cinder.db called 'volume_admin_metadata_update' which creates admin metadata for the volume. But it needs the context as an argument. This context is not passed on to the driver. I understand driver is not required to know the context. However, how can driver create the admin metadata?

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2013-12-09 04:54:21 -0600

Seen: 75 times

Last updated: Dec 17 '13