Blueprint assignments for “tuskar”
This listing shows the assignment of work for blueprints currently associated with tuskar. 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 → 9 of 9 specifications | First • Previous • Next • Last |
| Priority | Name | Definition | Delivery | Assignee | Drafter | Approver |
|---|---|---|---|---|---|---|
| 5 Essential | As a developer I would like to utilize TripleO Heat templates for provisioning the Overcloud | 0 Approved | 0 Unknown | Marios Andreou | Martyn Taylor | |
| 4 High | Add Patch support to the API | 0 Approved | 0 Unknown | Martyn Taylor | Martyn Taylor | |
| 4 High | tripleo-tuskar-functional-test-suite | 0 Approved | 0 Unknown | Robert Collins | ||
| 4 High | Use Keystone Trusts to avoid storing user credentials | 0 Approved | 0 Unknown | Rohan | Rohan | Ladislav Smola |
| 3 Medium | Allow tagging of nodes | 0 Approved | 0 Unknown | Jaromir Coufal | Robert Collins | |
| 2 Low | Add a model for Conditions into the API | 5 New | 0 Unknown | Jaromir Coufal | ||
| 1 Undefined | Plan REST API Refinements for Template Backed Storage | 3 Drafting | 0 Unknown | Jay Dobies | Jay Dobies | |
| 1 Undefined | Enable py33 voting in jenkins gating | 5 New | 0 Unknown | Xurong Yang | Xurong Yang | |
| 1 Undefined | Update documentation to reflect recent API changes | 5 New | 0 Unknown | Petr Blaho |
| 1 → 9 of 9 specifications | First • Previous • Next • Last |
