Default Swift ring deployment by TripleO are error-prone
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Christian Schwede |
Bug Description
There are a few problems today when deploying an overcloud with Swift using TripleO.
- only a single device per node is deployed
- this device is just a directory; locally available disks aren't used
- mount_check is disabled; this results in writing data to the root device
- adding a new node or replacing an existing one will result in inconsistent rings, because rings are created locally on each node and nodes don't know the "history"
- manually managed rings are overwritten on each deployment
- the ringbuilder doesn't know how to handle storage policies, for example to support Erasure Coding
A discussion how to improve this has been started on openstack-dev:
http://
Changed in tripleo: | |
assignee: | nobody → Christian Schwede (cschwede) |
status: | New → In Progress |
Changed in tripleo: | |
importance: | Undecided → High |
milestone: | none → ongoing |
Changed in tripleo: | |
milestone: | ongoing → newton-3 |
Changed in tripleo: | |
milestone: | newton-3 → newton-rc1 |
Changed in tripleo: | |
milestone: | newton-rc1 → ocata-1 |
milestone: | ocata-1 → newton-rc2 |
Changed in tripleo: | |
milestone: | newton-rc2 → ocata-1 |
Changed in tripleo: | |
milestone: | ocata-1 → ocata-2 |
Changed in tripleo: | |
milestone: | ocata-2 → ocata-3 |
Changed in tripleo: | |
milestone: | ocata-3 → ocata-rc1 |
Changed in tripleo: | |
milestone: | ocata-rc1 → ocata-rc2 |
Related fix proposed to branch: master /review. openstack. org/358643
Review: https:/