-
Notifications
You must be signed in to change notification settings - Fork 0
feature/CSTACKEX-65: Aggregate selection logic for creating ONTAP Volume in StoragePool creation workflow #24
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
base: main
Are you sure you want to change the base?
Conversation
…NTAP Volume creation
| throw new CloudRuntimeException("No aggregates are assigned to SVM " + svmName); | ||
| } | ||
| // Set the aggregates which are according to the storage requirements | ||
| int maxAvailableAggregateSpace = storage.getSize().intValue(); |
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.
Since size isn’t assigned before connect executes, the process cannot succeed.
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.
Storage is already assigned but the other comment makes sense, aggregate selection should be in Volume creation code. So, have modified the code accordingly
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.
Let’s go over the code in the scrum meeting. My review was limited to the merged changes and the code review raised, so I’d appreciate your input on the code as it appears in your IDE.
| // Set the aggregates which are according to the storage requirements | ||
| int maxAvailableAggregateSpace = storage.getSize().intValue(); | ||
| Aggregate aggrChosen = null; | ||
| for (Aggregate aggr : aggrs) { |
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.
Why does the connect method handle aggregate selection? This logic should ideally reside in the volume creation process.
rajiv-jain-netapp
left a comment
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.
lets have online review
Description
This PR...
Has changes to choose an aggregate based on the max available space while creating ontap volume for Primary StoragePool creation.
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
Test-1: With Default aggregate sizes in 2vSim ONTAP Cluster




Test-2: After expanding one aggr's size