Is your feature request related to a problem? Please describe.
vcsim does not currently handle calls from the VSLM GlobalObjectManager, which means it's currently impossible to use vcsim to test those code that uses them.
Describe the solution you'd like
It should be fairly straightforward to add a simulator implementation for VslmVStorageObjectManager and register it as a handler for the /vslm/sdk path. Most of the endpoints are largely the same as the existing VcenterVStorageObjectManager, although there are additional endpoints that the local version does not support.
The only problem I can think of offhand with that approach is that a struct that handles VslmVStorageObjectManager needs to share the same set of objects as the existing VcenterVStorageObjectManager. This makes it difficult to use the simulator's RegisterSDK method to add the handler. There is also an ordering dependency which means that the setup might have to happen as part of initially configuring the VStorageObjectManager.
Is your feature request related to a problem? Please describe.
vcsimdoes not currently handle calls from the VSLMGlobalObjectManager, which means it's currently impossible to use vcsim to test those code that uses them.Describe the solution you'd like
It should be fairly straightforward to add a simulator implementation for
VslmVStorageObjectManagerand register it as a handler for the/vslm/sdkpath. Most of the endpoints are largely the same as the existingVcenterVStorageObjectManager, although there are additional endpoints that the local version does not support.The only problem I can think of offhand with that approach is that a struct that handles
VslmVStorageObjectManagerneeds to share the same set of objects as the existingVcenterVStorageObjectManager. This makes it difficult to use the simulator'sRegisterSDKmethod to add the handler. There is also an ordering dependency which means that the setup might have to happen as part of initially configuring theVStorageObjectManager.