Calamari RESTful API » History » Version 2
Jessica Mack, 07/01/2015 04:43 AM
| 1 | 1 | Jessica Mack | h1. Calamari RESTful API |
|---|---|---|---|
| 2 | |||
| 3 | h3. Summary |
||
| 4 | |||
| 5 | This session will be an update on the current state of calamari. What calamari is and isn't. What the API currently supports, planned support in the next release, and information on how to integrate with and contribute to Calamari. |
||
| 6 | |||
| 7 | h3. Owners |
||
| 8 | |||
| 9 | 2 | Jessica Mack | * Gregory Meno (Red Hat) |
| 10 | * Name (Affiliation) |
||
| 11 | * Name |
||
| 12 | 1 | Jessica Mack | |
| 13 | h3. Interested Parties |
||
| 14 | |||
| 15 | 2 | Jessica Mack | * Name (Affiliation) |
| 16 | * Name (Affiliation) |
||
| 17 | * Name |
||
| 18 | 1 | Jessica Mack | |
| 19 | h3. Current Status |
||
| 20 | |||
| 21 | Calamari has implemented roughly 30% on the functionality of the RADOS CLI tool ceph |
||
| 22 | Calamari has implemented 0% or the RBD and RGW command line tools. |
||
| 23 | |||
| 24 | See here for a detail list of coverage TODO |
||
| 25 | |||
| 26 | Features planned for our next release which will be frozen end of Jan. 2015 |
||
| 27 | Multi-cluster in UI |
||
| 28 | Multi-user |
||
| 29 | CRUSH management implemented in API |
||
| 30 | |||
| 31 | h3. Detailed Description |
||
| 32 | |||
| 33 | Calamari is a set of services and agents that manage and monitor ceph clusters presented as a high-level API. The UI known as calamari-clients is just a lens into the API it is a way to easily consume the the information about status and to drive the control-plane. Everything that is represented in the GUI is possible because it has implementation in Calamari. The goal of the Calamari API is to provide functional parity with each CLI tool in ceph in a consistent fashion. It provides higher-level semantics so that one request can be mapped to many invocations in the CLI |
||
| 34 | |||
| 35 | h3. Work items |
||
| 36 | |||
| 37 | 2 | Jessica Mack | # re-definition of Calamari as being the control plane for Ceph, minus the GUI. |
| 38 | # goals of the API (CLI functionaly parity with higher-level semantics) |
||
| 39 | # intended uses of API (GUI, OpenStack Horizon, interaction with other tools like blivet, libstorage etc) |
||
| 40 | # Current API functionality status |
||
| 41 | # Plans for Calamari 1.3 API |
||
| 42 | # opportunities for communnity involvement |
||
| 43 | 1 | Jessica Mack | |
| 44 | h4. Coding tasks |
||
| 45 | |||
| 46 | # Task 1 |
||
| 47 | # Task 2 |
||
| 48 | # Task 3 |
||
| 49 | |||
| 50 | h4. Build / release tasks |
||
| 51 | |||
| 52 | # Task 1 |
||
| 53 | # Task 2 |
||
| 54 | # Task 3 |
||
| 55 | |||
| 56 | h4. Documentation tasks |
||
| 57 | |||
| 58 | # Task 1 |
||
| 59 | # Task 2 |
||
| 60 | # Task 3 |
||
| 61 | |||
| 62 | h4. Deprecation tasks |
||
| 63 | |||
| 64 | # Task 1 |
||
| 65 | # Task 2 |
||
| 66 | # Task 3 |