| Summary: | [RFE][swift]: Erasure code ring | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | RHOS Integration <rhos-integ> |
| Component: | openstack-swift | Assignee: | RHOS Maint <rhos-maint> |
| Status: | CLOSED UPSTREAM | QA Contact: | Dafna Ron <dron> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | unspecified | CC: | derekh, markmc, scohen, sgordon, yeylon, zaitcev |
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | https://blueprints.launchpad.net/swift/+spec/ec-ring | ||
| Whiteboard: | upstream_milestone_ongoing upstream_status_not-started upstream_definition_approved | ||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-06-30 19:19:07 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 16:43:11 UTC
A EC Ring has to be configured the default and the same battery of tests that QE uses to test regular Swift ought to be run against such cluster. This way we do not depend on Policy stuff to work. Note that when we have EC, we'll have to use replication for account and containers for a good while, so it's going to be mixed cluster that way. Not necessarily by a policy, however. (In reply to Pete Zaitcev from comment #3) > A EC Ring has to be configured the default and the same battery of > tests that QE uses to test regular Swift ought to be run against > such cluster. This way we do not depend on Policy stuff to work. > Pete, can you you please add configuration instructions or a list for a guide on how to configure EC ring as oppose to regular swift? please note that QE install's swift using packstack. > Note that when we have EC, we'll have to use replication for > account and containers for a good while, so it's going to be > mixed cluster that way. Not necessarily by a policy, however. what do you mean by good while? (In reply to Dafna Ron from comment #4) > Pete, can you you please add configuration instructions or a list for a > guide on how to configure EC ring as oppose to regular swift? please note > that QE install's swift using packstack. I will, when it becames available (e.g. delivered for review by the Box and Intel folks at least). > > Note that when we have EC, we'll have to use replication for > > account and containers for a good while, so it's going to be > > mixed cluster that way. Not necessarily by a policy, however. > > what do you mean by good while? A few releases or perhaps indefinitely. As far as I know, there's no plan to create EC databases for accounts and containers. The size of SQLite files we create is not large enough to make it viable. i opened a blueprint for cli implementation https://blueprints.launchpad.net/python-swiftclient/+spec/erasure-code |