Calamari - How to implement high-level stories in an intelligent API » History » Version 1
Jessica Mack, 07/06/2015 09:53 PM
| 1 | 1 | Jessica Mack | h1. Calamari - How to implement high-level stories in an intelligent API |
|---|---|---|---|
| 2 | |||
| 3 | h3. Summary |
||
| 4 | |||
| 5 | In this blueprint I will discuss a concrete example that is currently implemented in calamari. Updating attributes of a ceph pool so that we don't cause large amounts of data movement. I will show the relevant bits of the system where the fine-grained details are gathered, where we encode heuristics for being smart about ceph, and how it all hangs together to support a user story "as an administrator I want to be able to grow the pg_num of a pool without disturbing IO traffic to that pool" |
||
| 6 | |||
| 7 | After that I will look at a set of yet to be implemented stories that I consider interesting and discuss what needs to happen in each component of calamari for one of these stories: "as an administrator I want to get alerts when OSDs are likely to fail" |
||
| 8 | |||
| 9 | h3. Owners |
||
| 10 | |||
| 11 | * Gregory Meno (Red Hat) |
||
| 12 | * Name (Affiliation) |
||
| 13 | * Name |
||
| 14 | |||
| 15 | h3. Interested Parties |
||
| 16 | |||
| 17 | * Name (Affiliation) |
||
| 18 | * Name (Affiliation) |
||
| 19 | * Name |
||
| 20 | |||
| 21 | h3. Current Status |
||
| 22 | |||
| 23 | h3. Detailed Description |
||
| 24 | |||
| 25 | h3. Work items |
||
| 26 | |||
| 27 | h4. Coding tasks |
||
| 28 | |||
| 29 | # Task 1 |
||
| 30 | # Task 2 |
||
| 31 | # Task 3 |
||
| 32 | |||
| 33 | h4. Build / release tasks |
||
| 34 | |||
| 35 | # Task 1 |
||
| 36 | # Task 2 |
||
| 37 | # Task 3 |
||
| 38 | |||
| 39 | h4. Documentation tasks |
||
| 40 | |||
| 41 | # Task 1 |
||
| 42 | # Task 2 |
||
| 43 | # Task 3 |
||
| 44 | |||
| 45 | h4. Deprecation tasks |
||
| 46 | |||
| 47 | # Task 1 |
||
| 48 | # Task 2 |
||
| 49 | # Task 3 |