Bug 1041233

Summary:	[RFE][nova]: Introduce a formal class model for block mapping
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	RFEs	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	markmc, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/nova/+spec/block-mapping-model
Whiteboard:	upstream_milestone_none upstream_status_unknown upstream_definition_drafting
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 17:30:05 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description RHOS Integration 2013-12-12 14:01:41 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/block-mapping-model.

Description:

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.

Specification URL (additional information):

None