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

Provide the plugin user with more visibility into the available VCH Management API servers #572

Open
wjun opened this issue Aug 23, 2018 · 0 comments
Assignees
Labels
component/plugin/h5c The plugin for the vSphere HTML5 client kind/enhancement Behavior that was intended, but we want to make better severity/3-moderate Medium usability or functional impact. Potentially has an inconvenient workaround.

Comments

@wjun
Copy link
Contributor

wjun commented Aug 23, 2018

As described in vmware/vic-product#1952, provide the plugin user with more visibility into the available VCH Management API servers.

This likely involves replacing the initial landing page of the plugin which currently has a single-row datagrid. (Or removing that page entirely and adding a tab on the next page of the plugin, between "Summary" and "Container Hosts" which provides information about the available OVAs.)

This may involve allowing a user to select which of several compatible OVAs should be used.

@zjs zjs added kind/enhancement Behavior that was intended, but we want to make better component/plugin/h5c The plugin for the vSphere HTML5 client severity/3-moderate Medium usability or functional impact. Potentially has an inconvenient workaround. labels Aug 30, 2018
@zjs zjs changed the title Provide the plugin user with more visibility into the available plugins Provide the plugin user with more visibility into the available VCH Management API servers Aug 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/plugin/h5c The plugin for the vSphere HTML5 client kind/enhancement Behavior that was intended, but we want to make better severity/3-moderate Medium usability or functional impact. Potentially has an inconvenient workaround.
Projects
None yet
Development

No branches or pull requests

3 participants