Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1154253

Summary: [RFE][cinder]: Cinder Objects
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: openstack-cinderAssignee: Eric Harney <eharney>
Status: CLOSED ERRATA QA Contact: nlevinki <nlevinki>
Severity: high Docs Contact:
Priority: medium    
Version: unspecifiedCC: eharney, markmc, scohen, yeylon, yrabl
Target Milestone: Upstream M3Keywords: CodeChange, FutureFeature, OtherQA
Target Release: 7.0 (Kilo)   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/cinder/+spec/cinder-objects
Whiteboard: upstream_milestone_kilo-3 upstream_definition_approved upstream_status_implemented
Fixed In Version: openstack-cinder-2015.1.0-2.el7ost Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-05 13:14:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description RHOS Integration 2014-10-18 04:07:26 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/cinder/+spec/cinder-objects.

Description:

The goal of this blueprint is to introduce objects into cinder.  An object is used to bundle data with methods that can operate on them.  The plan is to represent the following concepts as objects: volumes, snapshots, volume_type, qos_specs, quota, reservation, backup, consistencygroup, cgsnapshot, and others.

By using objects, the code will be insulated from the actual database schema, making it easier rolling upgrades.  Objects can be used to pass data over RPC and allow lazy-loading of data directly from the database or over RPC.

Specification URL (additional information):

None

Comment 6 errata-xmlrpc 2015-08-05 13:14:59 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2015:1548