Blueprint assignments for “networking-midonet”
This listing shows the assignment of work for blueprints currently associated with networking-midonet. The drafter is responsible for getting the specification correctly written up and approved. The approver is usually the person who would sign off on the specification.
| 1 → 6 of 6 specifications | First • Previous • Next • Last |
| Priority | Name | Definition | Delivery | Assignee | Drafter | Approver |
|---|---|---|---|---|---|---|
| 3 Medium | MidoNet implementation of Tap-as-a-Service | 0 Approved | 9 Needs Code Review | Yoichiro Iura | Ryu Ishimoto | Ryu Ishimoto |
| 1 Undefined | Border GW API for MidoNet | 5 New | 0 Unknown | Irena Berezovsky | ||
| 1 Undefined | Tool to sync data between Neutron and MidoNet | 5 New | 0 Unknown | Ryu Ishimoto | ||
| 1 Undefined | Dynamic Routing in MidoNet | 5 New | 0 Unknown | Ryu Ishimoto | ||
| 1 Undefined | Keystone v3 Support | 5 New | 0 Unknown | Ryu Ishimoto | ||
| 1 Undefined | Make the Neutron API task-based and async for MidoNet | 5 New | 0 Unknown | Ryu Ishimoto |
| 1 → 6 of 6 specifications | First • Previous • Next • Last |
