-
Notifications
You must be signed in to change notification settings - Fork 5.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mgr/dashboard: cluster upgrade start UI #52493
Conversation
Some Nits: Are we checking two times if the update is available? once when we load the upgrade page and once we are opening the modal for upgrade, can't we just pass data from parent component to child and use it? Also set the default height and width of modal to size you think it will require. |
f88786c
to
33f4efb
Compare
We need to subscribe again to see which versions are available. So probably I can update the message as |
33f4efb
to
9443352
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've made some modifications in the review. If you follow that, you can avoid the duplicated api call.
Also the upgrade-start
component you created should really be upgrade-form
component and it should be inside upgrade/upgrade-form
folder rather than existing in the same folder as upgrade
.
Also it is missing the unit-test file. You should also create that and push it.
src/pybind/mgr/dashboard/frontend/src/app/ceph/cluster/upgrade/upgrade-start-modal-component.ts
Outdated
Show resolved
Hide resolved
this.upgradeInfo$ = this.upgradeService.list(); | ||
this.upgradeInfoError$ = this.upgradeInfo$?.pipe( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we don't need to do this again. We can pass the versions from the upgrade.component where we are actually doing the subscription. so on this file you can introduce a variable called versions
to catch the params that are send from upgrade component.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the help here @nizamial09 ! I've addressed the suggestions.
src/pybind/mgr/dashboard/frontend/src/app/ceph/cluster/upgrade/upgrade-start-modal-component.ts
Outdated
Show resolved
Hide resolved
src/pybind/mgr/dashboard/frontend/src/app/ceph/cluster/upgrade/upgrade-start-modal-component.ts
Outdated
Show resolved
Hide resolved
src/pybind/mgr/dashboard/frontend/src/app/ceph/cluster/upgrade/upgrade-start-modal-component.ts
Outdated
Show resolved
Hide resolved
src/pybind/mgr/dashboard/frontend/src/app/ceph/cluster/upgrade/upgrade.component.ts
Outdated
Show resolved
Hide resolved
src/pybind/mgr/dashboard/frontend/src/app/shared/constants/app.constants.ts
Outdated
Show resolved
Hide resolved
...ybind/mgr/dashboard/frontend/src/app/ceph/cluster/upgrade/upgrade-start-modal-component.html
Outdated
Show resolved
Hide resolved
...ybind/mgr/dashboard/frontend/src/app/ceph/cluster/upgrade/upgrade-start-modal-component.html
Outdated
Show resolved
Hide resolved
...ybind/mgr/dashboard/frontend/src/app/ceph/cluster/upgrade/upgrade-start-modal-component.html
Outdated
Show resolved
Hide resolved
9443352
to
df3e7f0
Compare
df3e7f0
to
f32212d
Compare
jenkins test make check |
Nit: |
jenkins test dashboard cephadm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @avanthakkar , overall looks good to me and is working so I'll approve it!
But I agree with Nizam's comment which hasn't been taking into account yet, I think this should be done:
Also the upgrade-start component you created should really be upgrade-form component and it should be inside upgrade/upgrade-form folder rather than existing in the same folder as upgrade.
Also it is missing the unit-test file. You should also create that and push it.
yeah missed that, will do unit test and move start modal component under |
Fixes: https://tracker.ceph.com/issues/61928 Signed-off-by: avanthakkar <avanjohn@gmail.com>
f32212d
to
31055fa
Compare
Done! |
Done! |
jenkins test make check |
Fixes: https://tracker.ceph.com/issues/61928
Signed-off-by: avanthakkar avanjohn@gmail.com
Screencast.from.2023-07-24.15-39-08.webm
Contribution Guidelines
To sign and title your commits, please refer to Submitting Patches to Ceph.
If you are submitting a fix for a stable branch (e.g. "pacific"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.
Checklist
Show available Jenkins commands
jenkins retest this please
jenkins test classic perf
jenkins test crimson perf
jenkins test signed
jenkins test make check
jenkins test make check arm64
jenkins test submodules
jenkins test dashboard
jenkins test dashboard cephadm
jenkins test api
jenkins test docs
jenkins render docs
jenkins test ceph-volume all
jenkins test ceph-volume tox
jenkins test windows