Calamari RESTful API¶

Summary¶

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.

Owners¶

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

Interested Parties¶

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

Current Status¶

Calamari has implemented roughly 30% on the functionality of the RADOS CLI tool ceph
Calamari has implemented 0% or the RBD and RGW command line tools.

See here for a detail list of coverage TODO

Features planned for our next release which will be frozen end of Jan. 2015
Multi-cluster in UI
Multi-user
CRUSH management implemented in API

Detailed Description¶

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

Work items¶

1. re-definition of Calamari as being the control plane for Ceph, minus the GUI.
2. goals of the API (CLI functionaly parity with higher-level semantics)
3. intended uses of API (GUI, OpenStack Horizon, interaction with other tools like blivet, libstorage etc)
4. Current API functionality status
5. Plans for Calamari 1.3 API
6. opportunities for communnity involvement

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