Bug 1343769 - INTEL OSP 10 FEAT Swift Erasure Code
Summary: INTEL OSP 10 FEAT Swift Erasure Code
Keywords:
Status: CLOSED DUPLICATE of bug 1337340
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-swift
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Pete Zaitcev
QA Contact: nlevinki
URL:
Whiteboard:
Depends On:
Blocks: 1334442
TreeView+ depends on / blocked
 
Reported: 2016-06-07 21:43 UTC by Rob Armstrong
Modified: 2016-06-08 12:31 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-08 12:31:26 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Rob Armstrong 2016-06-07 21:43:30 UTC
1.	Feature Overview: Support for Swift Erasure Coding, which became available as of Liberty
 a)	Name of feature: INTEL OSP 10 FEAT Swift Erasure Code

 b)	Feature Description: Erasure coding means that for some data sets the cloud operator can offer tremendous savings in storage media while still providing very high durability.  

 2.	Feature Details:
 a)	Architectures:
64-bit Intel E
Power
System/390

 b)	Bugzilla Dependencies:

 c)	Drivers or hardware dependencies:

 d)	Upstream acceptance information: 

 e)	External links:

 f)	Severity (H,M,L):  H
High (required for Hardware Enablement)
Medium
Low

 g)	Feature Needed by:

 3.	Business Justification:  (Some partners prefer to include this information in Comment #1, so it can be made private if the bug is opened to other partners.)

 a)	Why is this feature needed?

 b)	What hardware does this enable?

 c)	Is this hardware on-board in a system (eg, LOM) or an add-on card?

 d)	Business impact?

 e)	Other business drivers:

 4.	Primary contact at Red Hat, email, phone (chat)

Phone Number
 5.	Primary contact at Partner, email, phone (chat)
Rob Armstrong
Robert.h.armstrong@intel.com
Phone Number 503-887-3687

Comment 2 Sean Cohen 2016-06-08 12:31:26 UTC

*** This bug has been marked as a duplicate of bug 1337340 ***


Note You need to log in before you can comment on or make changes to this bug.