Reference Architectures
OpenStack has many choices for Hypervisor, Network Model, User Model, API, Storage System, OS, Packaging, etc. To keep up with Openstack's expansion, we need to document and automatically test configurations which OpenStack supports.
We need to document existing configurations (for instance a rackspace-style system might be: flat networking, openstack api, local storage, xen server, glance, puppet deployment scripts) and then have a integrated testing system which completes end-to-end tests Jenkins: provisioning physical hardware with XenServer, deploying via PXE, configure using puppet, running openstack smoketests against cluster.
Once we have these architectures documented and automated, we can verify that trunk works as expected now and with each commit to trunk. Since most developers don't have develop against all combinations of hypervisors/
When merging new features (such as support for LXC, VMware, Ceph, IPv6) in OpenStack, the testing team should work on adding the ability to verify the new features in existing and potentially new reference architectures.
In addition, we can save developer time by allow testing an arbitrary branch against all reference architectures.
This extends upon https:/
Blueprint information
- Status:
- Complete
- Approver:
- Vish Ishaya
- Priority:
- High
- Drafter:
- Jesse Andrews
- Direction:
- Approved
- Assignee:
- Anthony Young
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Informational
- Milestone target:
- None
- Started by
- Anthony Young
- Completed by
- Thierry Carrez
Whiteboard
This has no associated code so I don't know if there is a huge need to track this in a blueprint. --vish
Work Items
Dependency tree
* Blueprints in grey have been implemented.
