Skip to content
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

Merged
merged 1 commit into from
Aug 1, 2023

Conversation

avanthakkar
Copy link
Contributor

@avanthakkar avanthakkar commented Jul 17, 2023

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

Checklist

  • Tracker (select at least one)
    • References tracker ticket
    • Very recent bug; references commit where it was introduced
    • New feature (ticket optional)
    • Doc update (no ticket needed)
    • Code cleanup (no ticket needed)
  • Component impact
    • Affects Dashboard, opened tracker ticket
    • Affects Orchestrator, opened tracker ticket
    • No impact that needs to be tracked
  • Documentation (select at least one)
    • Updates relevant documentation
    • No doc update is appropriate
  • Tests (select at least one)
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

@avanthakkar avanthakkar requested a review from a team as a code owner July 17, 2023 18:15
@avanthakkar avanthakkar requested review from pereman2 and nizamial09 and removed request for a team July 17, 2023 18:15
@cloudbehl
Copy link
Contributor

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.

@avanthakkar
Copy link
Contributor Author

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.

We need to subscribe again to see which versions are available. So probably I can update the message as
Fetching the available versions? Not sure if I can @input these versions. wdyt? @nizamial09
Sure will do some resizing for text and modal.

Copy link
Member

@nizamial09 nizamial09 left a 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.

Comment on lines 42 to 43
this.upgradeInfo$ = this.upgradeService.list();
this.upgradeInfoError$ = this.upgradeInfo$?.pipe(
Copy link
Member

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.

Copy link
Contributor Author

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.

@cloudbehl
Copy link
Contributor

The version IMO needs to be in ascending order.

image

@avanthakkar
Copy link
Contributor Author

The version IMO needs to be in ascending order.

image

Done!

@avanthakkar
Copy link
Contributor Author

jenkins test make check

@cloudbehl
Copy link
Contributor

Nit: New versions -> New version

@nizamial09
Copy link
Member

jenkins test dashboard cephadm

Copy link
Contributor

@Pegonzal Pegonzal left a 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.

@avanthakkar
Copy link
Contributor Author

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 upgrade-form

Fixes: https://tracker.ceph.com/issues/61928
Signed-off-by: avanthakkar <avanjohn@gmail.com>
@avanthakkar
Copy link
Contributor Author

Nit: New versions -> New version

Done!

@avanthakkar
Copy link
Contributor Author

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.

Done!

@avanthakkar
Copy link
Contributor Author

jenkins test make check

@Pegonzal Pegonzal merged commit 172133f into ceph:main Aug 1, 2023
11 of 13 checks passed
@Pegonzal Pegonzal deleted the cluster-upgrade-ui branch August 1, 2023 08:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants