Skip to content

Conversation

@xinyanw409
Copy link
Contributor

Currently in ConnectEx() we hardcoding snapshotRef as empty string, which is not resonable. This pr updates ConnectEx() and adds the snapshotRef parameter.

Fix issue #11

snapshotRef:
A managed object reference to the snapshot of the virtual machine whose disks will be accessed with this connection. Specifying this property is only meaningful if the vmxSpec property in connectParams is set as well.

@lintongj
Copy link
Contributor

lintongj commented Dec 1, 2021

@xinyanw409 why there is no issue in the use case of velero-plugin-for-vsphere?

@xinyanw409
Copy link
Contributor Author

@xinyanw409 why there is no issue in the use case of velero-plugin-for-vsphere?
Specifying snapshotRef is only meaningful if the vmxSpec property in connectParams is set as well. In the use case of velero-plugin-for-vsphere we set vmxSpec as empty so there is no influence.

@lintongj
Copy link
Contributor

lintongj commented Dec 2, 2021

Would you please run end-to-end test of velero-plugin-for-vsphere with your change, so that make sure no regression is introduced?

@xinyanw409
Copy link
Contributor Author

Would you please run end-to-end test of velero-plugin-for-vsphere with your change, so that make sure no regression is introduced?

I've made astrolabe to pick the change locally and there is no compile issue. But it seems that plugin side can't pick up the change locally if there are two layers(vritual-disk/astrolabe). To run the e2e precheck I need to merge this change first.

@lintongj
Copy link
Contributor

Would you please run end-to-end test of velero-plugin-for-vsphere with your change, so that make sure no regression is introduced?

I've made astrolabe to pick the change locally and there is no compile issue. But it seems that plugin side can't pick up the change locally if there are two layers(vritual-disk/astrolabe). To run the e2e precheck I need to merge this change first

plugin side should be able to pickup a pending change in virtual-disks without merging it first. BTW, I don't think you need to pick up the change locally in astrolabe as vsphere-specific code, IVD PE/PETM, has been moved to plugin. Let me know if you still have any questions.

Copy link
Contributor

@lintongj lintongj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please test it e2e and update result.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants