-
Notifications
You must be signed in to change notification settings - Fork 29
Update Azure NetApp management and add NFS protocol version #86
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
Update Azure NetApp management and add NFS protocol version #86
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.
Did a simple test of this PR to confirm CDP Azure deployment works correctly.
Steps for test:
- CDP Azure definition included a CML workspace with default root volume size
- Confirmed that Azure NetApp Volume was created with NFSv3 protocol type. Expected from updates.
- Confirmed that {{run__azure_netapp_nfs_mount}} was set and used during the "Construct CDP ML Workspace configurations" task in runtime.
- ML workspace was successfully deployed and Filesystem ID listed in Workspace details matches the NetApp volume mount path.
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.
Hit an error during the environment teardown. Seems to be related to the changes made in roles/runtime/tasks/initialize_base.yml. See inline comment for details.
11778fb to
86b519f
Compare
|
Thanks @wmudge - commit 86b519f resolved the teardown error in platform. I hit another error during infrastructure teardown where the NetApp Capacity Pool could not be removed due to nested resources still being present. When I re-ran teardown this completed successfully so I suspect this is either an eventual consistency issue or a wait is needed on a previous task (e.g. Remove Azure NetApp Volume in cloudera.exe.infrastructure teardown_azure_storage.yml Snippet of error message is below. |
|
I suspect this is an eventual consistency issue and will need to add a guard condition. Still looking into it! |
…structure and CML usage Signed-off-by: Webster Mudge <[email protected]>
Signed-off-by: Webster Mudge <[email protected]>
86b519f to
0db07c2
Compare
Signed-off-by: Webster Mudge <[email protected]>
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.
@wmudge - confirmed that both setup and teardown of Azure environment with CML workspace now works with your latest changes. Looks good.
Signed-off-by: Webster Mudge <[email protected]>
Signed-off-by: Webster Mudge [email protected]