[docs] Improve documentation about OpenStack Storage nodes and rolls
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Confirmed
|
Medium
|
Fuel Documentation Team |
Bug Description
Need to improve information about Storaghe
- Improve architecural info in http://
- Add a chapter to the Planning Guide about "Designing Storage for your Environment"
- Improve Terminology articles about Swift, Cinder, Ceph, etc
- Add information to the Operations Guide about administering and troubleshooting your Storage roles/nodes
- Add information to the Operations Guide about measuring and improving the performance of your Storage roles/nodes
- Be sure that adequate supporting information is available for filling in the Storage-related configuration screens:
- http://
- http://
- http://
The information needs to be complete, although it can link to Community docs for details as appropriate
tags: | added: docs |
Changed in fuel: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
assignee: | nobody → Meg McRoberts (dreidellhasa) |
milestone: | none → 5.1 |
summary: |
- Improve documentation about OpenStack Storage nodes and rolls + [docs] Improve documentation about OpenStack Storage nodes and rolls |
Changed in fuel: | |
milestone: | 5.1 → 6.0 |
Changed in fuel: | |
milestone: | 6.0 → 6.1 |
Changed in fuel: | |
assignee: | Meg McRoberts (dreidellhasa) → Fuel Documentation Team (fuel-docs) |
milestone: | 6.1 → 7.0 |
Changed in fuel: | |
milestone: | 7.0 → 8.0 |
tags: | added: area-docs |
An important point often emerging from interaction with users on IRC is mostly about Ceph.
Users sometimes ask to improve the operating guide with some Ceph basic troubleshooting on MOS.
I suggest also to significantly expand the part explaining Ceph in the planning guide and add some advices, like that with Ceph storage, raw images is reccomended, and why that.
An option in the settings that is not covered at all is "Use qcow2 format for images". It's important to add some notes, because the checkbox's label is confusing users.