-
Notifications
You must be signed in to change notification settings - Fork 29
Feature branch for array integration. #1122
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
Can change the location
- Fix error handling in parseSize function - Fix potential infinite loop in StreamDisk with labeled break - Fix goroutine leaks in ExecuteCommandWithProgress
…VM/datastore discovery
… related ops, Auto detect arrays on target env so that discovery is easy for the user, Create UI to trigger the flow and understand the basic flow.
- Integrated ArrayCreds UI management components - Added ArrayCredsMapping CRD for vendor-based storage migration - Merged storage SDK enhancements (Pure Storage support) - Combined auto-discovery features from both branches - Resolved conflicts in CRDs, controllers, and go.mod files
|
This PR has too many files to review (>50 files). |
|
Connected to Huly®: VJAIL-950 |
|
Bito Automatic Review Skipped - Large PR |
Signed-off-by: K Suhas Pai <suhas@platform9.com>
|
Bito Automatic Review Skipped - Large PR |
My guess is there is a race condition after we rescan, esxi needs time to fully initialize the device after it appears, but we start the process as soon as the path is created. This is befor the VAAI XCOPY
learning: ESXI is extremely slow, we need to make these calls asynchronous
|
Bito Automatic Review Skipped - Large PR |
Signed-off-by: K Suhas Pai <suhas@platform9.com>
|
Bito Automatic Review Skipped - Large PR |
1 similar comment
|
Bito Automatic Review Skipped - Large PR |
05b5693 to
11e85c8
Compare
|
Bito Automatic Review Skipped - Large PR |
Signed-off-by: K Suhas Pai <suhas@platform9.com>
|
Bito Automatic Review Skipped - Large PR |
What this PR does / why we need it
Which issue(s) this PR fixes
(optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged)fixes #
Special notes for your reviewer
Testing done
please add testing details (logs, screenshots, etc.)