Cinder

Independent Database for Driver

Asked by Amol

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?

Question information

Language:
English Edit question
Status:
Solved
For:
Cinder Edit question
Assignee:
No assignee Edit question
Solved by:
John Griffith
Solved:
Last query:
Last reply:
Revision history for this message
Best John Griffith (john-griffith) said : 		#1

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

Revision history for this message
Amol (amolj-1306) said : 		#3

Thanks John Griffith, that solved my question.