Main Page
Revision as of 21:08, 22 September 2010 by AnneGentle (talk)
OpenStack Open Source Cloud Wiki
The OpenStack Open Source Cloud Mission: to produce the ubiquitous Open Source Cloud Computing platform that will meet the needs of public and private clouds regardless of size, by being simple to implement and massively scalable.
This wiki is intended to provide a repository and initial forum for discussions, requirements, and architectural development in progress.
Foundation documents
- Open - What openness means to us.
- Governance - How we will govern all OpenStack projects.
- Release Schedule - Dates for upcoming release milestones
Development
- Blueprints are complete
- Coding Standards
- [[[LifeWithBzrAndLaunchpad|| Learning bzr and Launchpad ]]]
- [[[HowToContribute|| How to Contribute ]]]
- Weekly Release Meeting
- Getting the Code (using Launchpad and bzr)
- Planet OpenStack - Aggregation of community and developer blogs around OpenStack.
- Install Instructions
Compute (Nova)
- Project on Launchpad
- Team and mailing list
- Developer documentation
- Detailed discussion of Launchpad blueprints
- Design Tenets - Some of the basic principles we are following.
- Overview High level overview of the different components and how they interact.
- Requirements
- Use Cases - These describe the high-level functional requirements, subsequently decomposed into detailed component requirements. Each requirement begins as a simple function (e.g., Add new server). These are then decomposed via data flow diagrams to show the data and processing requirements placed upon each component in order to support the basic function. These should follow the template in SpecTemplate.
- Architectural - These describe the interface requirements for each component, starting at the external API and working inward.
- Non-functional - These describe the basic, non-functional requirements which are priorities for the architecture (e.g., scalability, easy of use). Each basic requirement is then decomposed into detailed requirements via specification of the manner of testing to be used to measure compliance to that requirement (e.g., specific load tests, length of install, etc.)
