You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Details:
The H5C vch wizard needs to know the IP of the vic-machine-service API endpoint. We need to figure out how to 'discover' this IP address since it cannot be statically set (per George) because of the dhcp option.
The text was updated successfully, but these errors were encountered:
Discussions with @jooskim led me this open issue which seems like it may be a good way for us to be able to discover the OVA VM and its IP based on the OS Guest Name which we do have access to in the VM MOB properties. vmware/vic-product#920
An alternative could possibly be to piggy-back on the additional properties to be added for phone home. vmware/vic-product#911. Although we need more verification on if we are able to get this into some VM properties that the H5 plugin can access. Initial tests using tags have not been successful thus far. #5678 (comment)
Per @zjs Update on the component manager investigation: between 5.5 and 6.0, that functionality was moved into the platform services controller.
I was told, off the record, that it was conceived for the sort of use case we have, but probably isn't something we'll be able to actually use (or want to) due to questionable design/implementation decisions.
[5:46]
It sounds like vmware/vic-product#920 might be our best bet.
Details:
The H5C vch wizard needs to know the IP of the vic-machine-service API endpoint. We need to figure out how to 'discover' this IP address since it cannot be statically set (per George) because of the dhcp option.
The text was updated successfully, but these errors were encountered: