Ceph » mgr » Dashboard

My 2 cents,

I'm for option 2 as it makes the focus more obvious thx to the left blue bar.

If I may, having the ceph version reported would be helpful.

Erwan Velu wrote:

I'm for option 2 as it makes the focus more obvious thx to the left blue bar.

Thanks for the feedback!

If I may, having the ceph version reported would be helpful.

For security purposes, this information should only be visible to authenticated users. Being able to determine a service's version number makes it easier for remote attackers to perform an exploit.

FWIW, I too would be in favor of Option#2.

Thanks for attaching the source image. The license terms are described here: https://unsplash.com/license
Even though not strictly necessary, I suggest to give credit to the image author as outlined on that page.

+1 for Option 2.

Option #2 looks awesome! Well done.

Hi, My name is Aditya, a GSoC applicant, I have submitted my draft proposal on the project idea CEPH dashboard UI enhancements and this is one of the issues under it.
Can you suggest any starting point for this issue??

Bhaskar Aditya wrote:

Hi, My name is Aditya, a GSoC applicant, I have submitted my draft proposal on the project idea CEPH dashboard UI enhancements and this is one of the issues under it.

Bhaskar Aditya Jha

Can you suggest any starting point for this issue??

Bhaskar Aditya wrote:

Hi, My name is Aditya, a GSoC applicant, I have submitted my draft proposal on the project idea CEPH dashboard UI enhancements and this is one of the issues under it.
Can you suggest any starting point for this issue??

Hi Bhaskar,

Welcome to Ceph project!

1. You should first have a Ceph cluster running. That will give you a running back-end (Python server) and front-end (Angular).
2. For front-end development, it's highly recommend that you skip the Angular website statically served by the back-end and use one with Just-in-Time compilation (npm start). That will refresh the front-end on every code change you make, which heavily reduces the time to get feedback from you code changes.
3. Once you have that environment ready, I suggest you to find the login component src/pybind/mgr/dashboard/frontend/src/app/core/auth/login and start playing with it and seeing how it react to changes.
4. This ticket includes all technical information required (background image, color definitions and a layout proposal) for completing the task.
5. Note: While option 2 seemed to be the preferred, feel free to come up with either or even both if you want to demo both designs. Additionally, feel free to provide your own inputs/hints to improve the login page.

Let me know if you have any issues with this! (you can reach out to ceph-dashboard team in OFTC IRC #ceph-dashboard room).

Hi, I have already submitted a PR for this :(, around 7 days ago. https://github.com/ceph/ceph/pull/34079

Lenz Grimmer wrote:

Thanks for attaching the source image. The license terms are described here: https://unsplash.com/license
Even though not strictly necessary, I suggest to give credit to the image author as outlined on that page.

Here's the appropriate credits information:

<a href="https://unsplash.com/photos/Lu9z9qS8I_Q">Photo</a> by <a href="https://unsplash.com/@gaspanik">Masaaki Komori</a> on <a href="https://unsplash.com/">Unsplash</a>