Jump to: navigation, search

Difference between revisions of "Architecture Design Guide work items"

(Chapter 9. Legal requirements)
(Chapter 5 Operator requirements)
Line 51: Line 51:
* 5.3 Selecting hardware
* 5.3 Selecting hardware
**Selecting the right hardware - servers, switches, and how they integrate
**Selecting the right hardware - servers, switches, and how they integrate
** Consolidate http://docs.openstack.org/arch-design/generalpurpose-architecture.html, http://docs.openstack.org/arch-design/compute-focus-architecture.html, http://docs.openstack.org/arch-design/storage-focus-architecture.html
** Consolidate http://docs.openstack.org/arch-design/generalpurpose-architecture.html, http://docs.openstack.org/arch-design/compute-focus-architecture.html, http://docs.openstack.org/arch-design/storage-focus-architecture.html (Darren Chan, reivew TBA)
* 5.4 integration with external IDP
* 5.4 integration with external IDP
* 5.5 Upgrades?http://docs.openstack.org/arch-design/multi-site-operational-considerations.html#upgrades
* 5.5 Upgrades?http://docs.openstack.org/arch-design/multi-site-operational-considerations.html#upgrades

Revision as of 01:24, 22 December 2015

Architecture Design Guide Reorganization

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-mitaka-reorg
  • If you need diagrams, ping darrenc.




Global tasks

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.

  • Rewrite abstract - Shilla Saebi
  • Markup glossary terms
  • How about we condense the use case information as a chapter at the start of the book, and mention hybrid as the main focus in the guide?
  • Mention http://docs.openstack.org/openstack-ops/content/cloud_controller_design.html
  • Would including a generic architecture design planning template in an appendix be useful or relevant?
  • Considerations when designing an OpenStack cloud in a development, staged or production environment

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 complete when the task is completed.

Chapter 1. Introduction

  • 1.2 How this book is organized (Njira Perci, https://review.openstack.org/260045/, In Progress)
    • Rewrite this section mentioning the book follows a structure that system architects would use in developing cloud architecture design documents
  • 1.3 Why and How we wrote this book - Shilla Saebi
    • Include section?

Chapter 2 Identifying stakeholders

  • Describe who the internal and external stakeholders are, and the impact they may have on business requirements and architecture design.

Chapter 3 Functional Requirements

Chapter 4 User requirements

Chapter 5 Operator requirements

Chapter 6 Capacity planning and scaling

http://docs.openstack.org/arch-design/generalpurpose-technical-considerations.html#designing-network-resources, http://docs.openstack.org/arch-design/network-focus-technical-considerations.html, http://docs.openstack.org/arch-design/network-focus-architecture.html#tunable-networking-components, http://docs.openstack.org/arch-design/multi-site-architecture.html#networking, http://docs.openstack.org/arch-design/hybrid-user-requirements.html#network-considerations, http://docs.openstack.org/arch-design/hybrid-architecture.html,

Chapter 7. High Availability

Chapter 8. Security requirements

Chapter 9. Legal requirements

Chapter 10. Example architectures

(reflecting concepts and terminology described in previous chapters)