2024-12-11T05:44:19.223Z

<nizamial09> Hey @Artem Torubarov good to meet you here.. i'll tag a couple of interested parties here. 

@epuertat @Afreen

2024-12-11T05:45:04.162Z

<nizamial09> Hey @Artem Torubarov good to meet you here.. i'll tag a couple of interested parties here. 

@Ernesto Puerta @Afreen

2024-12-11T08:54:29.925Z

<Redouane> Hi @Artem Torubarov it was nice to meet you in person in cephalocon and to discuss about this interesting project. I'll share the project with more members of the team to see get more feedback and to see how can we start collaborating on this 🙂

2024-12-11T08:55:06.799Z

<Redouane> Hi @Artem Torubarov it was nice to meet you in person in cephalocon and to discuss about this interesting topic. I'll share the project with more members of the team to get more feedback and to see how can we start collaborating on this 🙂

2024-12-11T12:00:18.146Z

<Ernesto Puerta> Hey @Artem Torubarov! Welcome to the Dashboard community!

We should definitely have a detailed overview/discussion about that. Do you already have some public architecture doc (etherpad, Google Doc, whatever) to start with?

I'd like to understand some design decisions (e.g.: gRPC is a great way to serialize and enforce structured data, but many L4/L7 load balancers don't work well with it, like AWS EC2 ELB). Also the ceph-mgr provides a caching layer that improves ceph-mon isolation from management workloads (something not possible with librados/go-ceph alone).

2024-12-11T12:37:54.818Z

<Artem Torubarov> unfortunately there is no documentation besides README at the moment. The plan is to have both gRPC and http (rest) APIs. There will be not much overhead in supporting 2 apis because REST is generated automatically from gRPC with <https://github.com/grpc-ecosystem/grpc-gateway>

I was not aware of potential caching problem. If in the future the new api becomes a single entry point for all clients (web, CLI) probably we can also port some caching or rate-limiting logic from mgr into new api.

I am happy to answer any questions here or we can also setup a call.

2024-12-11T17:09:17.308Z

<Ernesto Puerta> Got it! Thanks a lot for the clarification, Artem! Do you have any current use-case for this API? In order to analyze any scalability issues.

2024-12-11T17:33:27.762Z

<Artem Torubarov> it is hard to use api in its current state because only few endpoints are implemented. We have in mind the following API clients when it will be fully implemented:
• existing or custom web dashboard
• day-two operation tools and automation scripts
• some 3rd party systems to manage quota/billing/usage/etc…

2024-12-11T17:33:58.882Z

<Artem Torubarov> it is hard to use api in its current state because only few endpoints are implemented. We have in mind the following API clients when it will be fully implemented:
• existing or custom web dashboard
• day-two operation tools and automation scripts
• some 3rd party systems to manage quota/billing/usage/users/etc…