Architecture Design Guide restructure work items
Contents
Architecture Design Guide Restructure
Do not modify the current guide in openstack-manuals/docs/arch-design. Commit your work to the draft directory openstack-manuals/docs/arch-design-draft.
- Please ensure your commit messages references the blueprint: Implements: blueprint arch-guide-restructure
Resources
Deliverables
To assign yourself a task, put your name next to the task and reference the review URL. Change the status to complete when the task is completed.
Pike
- Focus on writing the Design chapter
- Highest priority is completing the storage and networking sections
- Complete other sections in the Design chapter
- Develop a use case template
- Remove arch content from the ops guide since it has been migrated to the arch guide
- Archive the current arch guide
Ocata
- Complete compute section in Design chapter
- Publish draft guide to openstack-manuals (TBC)
Newton
- Migrate http://docs.openstack.org/ops-guide/architecture.htm content to the Arch Guide under the relevant sections:
- architecture.rst (Darren) https://review.openstack.org/#/c/324179/ Merged
- arch_storage.rst (Darren) https://review.openstack.org/#/c/324179/ Merged
- arch_scaling.rst (Darren) https://review.openstack.org/#/c/324179/ Merged
- arch_provision.rst <- Change title to planning and move to the Arch Guide (Darren)
- arch_network_design.rst <- Move to network Section in Arch Guide. (Shaun)
- arch_example_thoughts.rst <- Decide what to do with this content
- arch_example_network.rst <- Move to network Section in Arch Guide (Shaun)
- arch_example_neutron.rst <- Move to network Section in Arch Guide (Shaun)
- arch_compute_nodes.rst (Darren) https://review.openstack.org/#/c/324179/ Merged
- arch_cloud_controller.rst <- Move to control plane section DONE (Darren)
Chapter/Section tasks
To assign yourself a task, put your name next to the section or task and reference the review URL. Change the status to DONE when the task is completed.
Chapter | Section | Sub-section | Assignee | Bug number | Progress |
---|---|---|---|---|---|
Overview | |||||
Use cases | Development cloud | Design model | |||
Use cases | Development cloud | Requirements | |||
Use cases | Development cloud | Reference Architecture | |||
Use cases | General compute cloud | Design model | |||
Use cases | General compute cloud | Requirements | |||
Use cases | General compute cloud | Reference Architecture | |||
Use cases | Web scale cloud | Design model | |||
Use cases | Web scale cloud | Requirements | |||
Use cases | Public cloud | Reference Architecture | |||
Use cases | Public cloud | Design model | |||
Use cases | Public cloud | Requirements | |||
Use cases | Public cloud | Reference Architecture | |||
Use cases | Network Function Virtualization (NFV) cloud | Design model | |||
Use cases | Network Function Virtualization (NFV) cloud | Requirements | |||
Use cases | Network Function Virtualization (NFV) cloud | Reference Architecture | |||
High Availability | |||||
Capacity planning and scaling | The Starting Point | ||||
Capacity planning and scaling | Adding Cloud Controller Nodes | ||||
Capacity planning and scaling | Segregating Your Cloud | ||||
Capacity planning and scaling | Scalable Hardware | ||||
Design | Compute service | Ben Silverman | https://review.openstack.org/#/c/400525/4 | ||
Design | Storage | ||||
Design | Networking | Shaun O'Meara | https://review.openstack.org/#/c/391465/ MERGED | ||
Design | Identity service | ||||
Design | Image service | ||||
Design | Control plane | ||||
Design | Cloud Management Platform tools | ||||