Skip to content
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

Analysis: IP discovery of vch create endpoint for H5C plugin #6551

Closed
jak-atx opened this issue Oct 11, 2017 · 3 comments
Closed

Analysis: IP discovery of vch create endpoint for H5C plugin #6551

jak-atx opened this issue Oct 11, 2017 · 3 comments
Assignees
Labels
area/ui The Virtual Container Host administration UI team/lifecycle

Comments

@jak-atx
Copy link
Contributor

jak-atx commented Oct 11, 2017

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.

@jak-atx jak-atx added area/ui The Virtual Container Host administration UI team/lifecycle labels Oct 11, 2017
@jak-atx jak-atx changed the title Analysis: IP discovery from H5C plugin Analysis: IP discovery of vch create endpoint for H5C plugin Oct 11, 2017
@jak-atx jak-atx added this to the Sprint 19 Lifecycle milestone Oct 11, 2017
@jak-atx jak-atx self-assigned this Oct 12, 2017
@jak-atx
Copy link
Contributor Author

jak-atx commented Oct 13, 2017

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)

@andrewtchin @zjs @hickeng @cristianfalcone

@jak-atx
Copy link
Contributor Author

jak-atx commented Oct 18, 2017

Currently investigation Component Manager to see if this is an API that we can use to find the vic service by name or ID.

@jak-atx
Copy link
Contributor Author

jak-atx commented Oct 20, 2017

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ui The Virtual Container Host administration UI team/lifecycle
Projects
None yet
Development

No branches or pull requests

1 participant