-
Notifications
You must be signed in to change notification settings - Fork 15
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
Add sap hana scale up cost optimized and performance optimized discovery #3152
Conversation
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.
Looking good overall.
Some comments.
I see that tests and storybook updates are missing
lib/trento/discovery/payloads/cluster/cluster_discovery_payload.ex
Outdated
Show resolved
Hide resolved
120cb10
to
41d8bce
Compare
675fc2b
to
c2ea5e4
Compare
8d51e5b
to
c808f5f
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.
hey @EMaksy
The backend is all good (maybe I wrote some small nitpick).
I have written comments about the frontend. Small details, but I would like to fix them
90016ad
to
d54a8e6
Compare
d54a8e6
to
dca3a9d
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.
Green light!
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.
Nothing to add.
Just for me to better understand:
- perf opt and cost opt are only related to hana scale up (not scale out)
- definition rule is: no additional sids -> perf opt, some additional sids -> cost opt
Am I getting it right?
Yes, you are right! |
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.
LGTM, just one minor thing that I happened to see 👍
Very good job!
}; | ||
|
||
export const getClusterScenarioLabel = (type) => | ||
clusterScenarioLabels[type] || ''; |
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.
Do we need the ||
? Doesn't it work the same with just the access to the object?
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.
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.
Fair enough 😄
For the future remember that we can also use get
from lodash for better default semantics 👍
Thank you!
Description
This pr now adds a scenario discovery, with this, as a user I can see which HANA scale-up scenario I'm running on a cluster.
Main features.
Note: Scale out and ASCS/ERS untouched.
Preview
ClusterList view:

HostList view:

ClusterDetails View Cost Opt:

ClusterDetails View Perf. Opt.

How was this tested?