Introduce a formal class model for block mapping

Registered by Daniel Berrange on 2013-01-15

A number of the virt driver APIs accept a 'block_device_mapping' parameter. This is a dict with a variety of (pretty much entirely undocumented) parameters. The lack of documentation makes life very hard for maintainers trying to ensure correct support for the block device mappings. The same problem has historically existed with the network info parameters too and has been addressed by defining a formal data model (nova.network.model.*) for the data. The same kind of formal class model should be introduced for the block device mapping data.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Drafting
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

If you are still working on this, please re-submit via nova-specs. If not, please mark as obsolete, and add a quick comment to describe why. --johnthetubaguy (20th April 2014)

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.