Calamari - How to implement high-level stories in an intelligent API¶

Summary¶

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"

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"

Owners¶

• Gregory Meno (Red Hat)
• Name (Affiliation)
• Name

Interested Parties¶

• Name (Affiliation)
• Name (Affiliation)
• Name

Current Status¶

Detailed Description¶

Work items¶

Coding tasks¶

1. Task 1
2. Task 2
3. Task 3

Build / release tasks¶

1. Task 1
2. Task 2
3. Task 3

Documentation tasks¶

1. Task 1
2. Task 2
3. Task 3

Deprecation tasks¶

1. Task 1
2. Task 2
3. Task 3