Bug 1041233 - [RFE][nova]: Introduce a formal class model for block mapping
Summary: [RFE][nova]: Introduce a formal class model for block mapping
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/nova...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 14:01 UTC by RHOS Integration
Modified: 2015-03-19 17:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 17:30:05 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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
Note You need to log in before you can comment on or make changes to this bug.