Blueprint assignments for “pike”
This listing shows the assignment of work for blueprints currently associated with pike. 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 |
|---|---|---|---|---|---|---|
| 4 High | Use push style notifications for all server->agent information | 0 Approved | 11 Implemented | Kevin Benton | Kevin Benton | Ihar Hrachyshka |
| 2 Low | Allow instance-ingress bandwidth limiting | 0 Approved | 11 Implemented | Slawek Kaplonski | Slawek Kaplonski | Miguel Angel Ajo |
| 2 Low | API for l2 agent extensions (+ovs flow management) | 0 Approved | 11 Implemented | David Shaughnessy | Miguel Angel Ajo | |
| 2 Low | Port data plane status | 0 Approved | 11 Implemented | Carlos Goncalves | Carlos Goncalves | Armando Migliaccio |
| 2 Low | Support agentless driver in neutron-dynamic-routing | 7 Obsolete | 5 Started | Yang Yu | Yang Yu | vikram.choudhary |
| 2 Low | Implement l2pop driver functionality in l2 agent | 7 Obsolete | 1 Not started | venkata anil | Kevin Benton |
| 1 → 6 of 6 specifications | First • Previous • Next • Last |
