Difference between revisions of "Obsolete:NetworkUsecases"

Revision as of 17:42, 26 July 2011

The goal here is to agree on a set of increasingly sophisticated OpenStack networking use cases that we can use as milestones to track our progress during the Diablo period.

While some use cases involve dependencies on other network projects, we can start out by defining them on a per-project basis. Dependencies on other project should be called out when possible.

Quantum Roadmap

New in Diablo-3 Deliverable (initial deliverable):
- Web services API for defining L2 Network connectivity.
- Client CLI
- Works with vif-plugging in Nova's D-3 release (interface-ids determined by vif-plugging-driver).
- New Plugins: Open vSwitch (libvirt + XenServer)
- Initial unit test suite.
Potential Diablo-6 Deliverable:
- API Extensions framework
- Full Nova Integration: API extension to expose interface-ids, new NetworkManager class that uses Quantum.
- Basic API Authentication
- New plugins: Cisco Plugin, VMware-compatible plugin, Hyper-V-compatible plugin.
- System test framework
- Install Packaging

@@ Line 4: / Line 4: @@
 While some use cases involve dependencies on other network projects, we can start out by defining them on a per-project basis.   Dependencies on other project should be called out when possible.
-== Quantum ==
+== Quantum Roadmap ==
-* [completed 6/10/11] Milestone 0: create/delete networks, create/delete ports, attach/detach interfaces via CLI API client
+* New in Diablo-3 Deliverable (initial deliverable):
-** requires api core, api auth, core daemon, abstract plugin, cli API client, and a simple "fake" plugin.
+** Web services API for defining L2 Network connectivity.
-* [completed 6/10/11] Milestone 1: Ability to replicate nova's flat or vlan using CLI API client.
+** Client CLI
-** requires Milestone 0, plus integration with nova, and at least one "real" open-source plugin.
+** Works with vif-plugging in Nova's D-3 release (interface-ids determined by vif-plugging-driver).
-** does not require multi-nic in nova, api extensions, client gui.
+** New Plugins: Open vSwitch (libvirt + [[XenServer]])
-** Note: makes no assumption about how IP addresses are assigned to VMs.
+** Initial unit test suite.
-** Note: vlan model will not provide NAT gateway, as currently is the case with nova.
+* Potential Diablo-6 Deliverable:
-* Milestone 2: GUI demo of Milestone 1
+** API Extensions framework
-** requires Milestone 1 and GUI client
+** Full Nova Integration: API extension to expose interface-ids, new [[NetworkManager]] class that uses Quantum.
-* Milestone 3:  Integrate with a non-nova "external service".
+** Basic API Authentication
-** requires milestone 1, plus an available non-nova service.
+** New plugins: Cisco Plugin, VMware-compatible plugin, Hyper-V-compatible plugin.
-** DHCP service from Melange seems like a good candidate if it is ready.
+** System test framework
-** Note: this could also service as an early "multi-service" container use case for donabe.
+** Install Packaging
-** Ideally, we would have a GUI that could configure "instances" of the other service as well.
-* Milestone 4: Demonstrate API Extension
-** requires API extension work, plus at least one open-source plugin that exposes an extension.
-* Milestone 5: Multi-tier application
-** requires milestone 1, plus multi-nic in nova.
-== Network Flows ==
-This is an attempt to diagram possible flows between the network services and a service like Nova that may consume this. This is put up as a strawman to consider. The goal is to narrow down the possible flows so that when these independent services are built they interact based on an agreed to model.
- [[attachment:NetworkFlows.pdf]]
-Again, this is a strawman discussion can take place at:
-[http://etherpad.openstack.org/network-flows Network Flows Etherpad discussion]