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

Merge branch Feature/auto-vic-ui-plugin #1947

Closed
wants to merge 5 commits into from

Conversation

wjun
Copy link
Contributor

@wjun wjun commented Aug 20, 2018

We switch ui plugin registration from running manual commands of install.sh or upgrade.sh to automation. A set of rest apis are hosted on the VIC appliance fileserver. During the appliance initialization, index.html page will send a post request to the plugin install api, which will prepare the plugin and register the plugin to vCenter.

A thumbprint verification page is shown to enhance security, e.g. a wrong vCenter or a man-in-the-middle attack.

In case there is an old ui plugin in vCenter already, the new VIC appliance will overwrite the old ui plugin and register a new one.

UI plugin registration is also integrated into upgrade.sh, so the UI plugin can be upgraded as well when running upgrade.sh for VIC appliance upgrade.

With UI plugin auto registration, we do not need the manual ui install/upgrade.sh scripts and vic-ui-* commands anymore, which are removed by PR vmware/vic#8219

Towards: vmware/vic-product#1432

Jason Morris and others added 4 commits August 20, 2018 09:44
Updates the vendored vmware/vic repo to version
v1.4.0. Also adjusts dep configuration to prune unused
packages. Progress to vmware#1433.
…mware#1799)

Introduces caching of the vic-ui plugin artifacts as a component
of the ova. Updates the fileserver provisioner to package vic-ui
with the correct version numbers.

Creates the Fileserver Thumbprint API to return the
thumbprint of a given target ip address or fqdn.
Also refactors the fileserver main process into
main.go, and creates the routes/ and tasks/
sub-packages.

Moves vic-ui plugin dependencies to fileserver. This includes:
 - vic/lib/install/ova
 - vic/lib/install/plugin
- vic/tagvm/
Additionally, refactors ovatools/vic-ui/ui/ui.go to plugin.go that
doesn't include any CLI flags.

Automates the plugin install process and improves
logging in the fileserver:
 - Add trace.Op logging to fileserver tasks
 - Require vcenter thumprint on psc registration
 - Install VIC UI plugins in the initialization process
 - Attaches a managed tag to the Appliance VM
 - Performs a plugin install during the appliance upgrade
   process using the /plugin API.

Fixes vmware#1433, vmware#637, vmware#1720, vmware#1702 and vmware#1789.
Adds a new modal for thumbprint validation to the 
Getting Started Page in the Fileserver.
Fixes vmware/vic-ui#465
* Refactor register tests to use thumbprint

tmp

* [BROKEN] Robot testing

* Refacotr UI plugin registration test cases

* Revert "Refacotr UI plugin registration test cases"

This reverts commit c17d914.

* Revert "Revert "Refacotr UI plugin registration test cases""

This reverts commit f63b61d.

* fixup! Refacotr UI plugin registration test cases

* fixup! Refacotr UI plugin registration test cases
@wjun wjun requested review from zjs and a user August 20, 2018 03:09
@zjs
Copy link
Member

zjs commented Aug 20, 2018

In the vic-ui repo, we made some bug fixes to avoid issues with passwords that contained special characters (vmware/vic-ui#558). It looks like some of the affected files were removed from that repo and added to this one as a part of this automation work.

We should see if any of the changes made to the old files in vic-ui are applicable to this PR.

@zjs
Copy link
Member

zjs commented Aug 21, 2018

It seems like this change invalidates some of the information in BUILD.md. We should correct that file to reflect the new relationship between components. (As a reminder, this will require a new PR targeting the feature branch.)

Filed #1951 for this.

@ghost
Copy link

ghost commented Aug 21, 2018

Same question as in the vic repo: why is this being merged from a fork branch?
Otherwise, looks good.

@wjun
Copy link
Contributor Author

wjun commented Aug 22, 2018

@zjs since ui/install.sh|upgrade.sh|uninstall.sh will be removed after ui registration automation, vmware/vic-ui#558 will not exist anymore.
@morris-jason The reason I forked is the feature branch has rebase conflict, so I can solve the conflict and merge to master branch directly within one pr. @zjs is this ok, or we usually solve conflict on the feature branch first, and then merge feature branch into master branch? please advice. Thanks.

@zjs
Copy link
Member

zjs commented Aug 22, 2018

fixup! vic-ui robot tests (#1911) 1b59e25

It seems like this should be submitted to the feature branch, instead of just added directly to this PR.

@wjun
Copy link
Contributor Author

wjun commented Aug 27, 2018

Move to the feature branch directly at #1979

@wjun wjun closed this Aug 27, 2018
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.

4 participants