Blueprint assignments for “essex”
This listing shows the assignment of work for blueprints currently associated with essex. 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 → 12 of 12 specifications | First • Previous • Next • Last |
| Priority | Name | Definition | Delivery | Assignee | Drafter | Approver |
|---|---|---|---|---|---|---|
| 5 Essential | Melange API | 0 Approved | 11 Implemented | |||
| 5 Essential | Melange Client interface | 0 Approved | 11 Implemented | |||
| 5 Essential | Melange IPAM Services | 0 Approved | 11 Implemented | Troy Toman | ||
| 4 High | Provide a delayed delete capability for IPs | 0 Approved | 11 Implemented | |||
| 4 High | Move Melange client to a separate repo | 0 Approved | 11 Implemented | raxnetworking | ||
| 4 High | MAC address tracking and assignment | 0 Approved | 11 Implemented | |||
| 3 Medium | Interfaces API Clean up | 0 Approved | 11 Implemented | Rajaram Mallya | Troy Toman | |
| 3 Medium | Melange API Extensions | 0 Approved | 11 Implemented | |||
| 3 Medium | Melange Notifications | 0 Approved | 11 Implemented | |||
| 3 Medium | Create Static Routes and tie them to IP blocks | 0 Approved | 11 Implemented | |||
| 2 Low | Melange IP address allocation polices | 0 Approved | 11 Implemented | |||
| 1 Undefined | Create new API calls to manage Nova interfaces | 0 Approved | 11 Implemented | raxnetworking |
| 1 → 12 of 12 specifications | First • Previous • Next • Last |
