-
Notifications
You must be signed in to change notification settings - Fork 92
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
Document how client handles multiple OVAs on a single VC #1356
Comments
There is information about the steps that are required when deploying more than one appliance in vmware/vic-ui#365. |
@renmaosheng, now that we have the automated install/upgrade of the client plug-in, what happens if you deploy more than one VIC appliance on the same vCenter Server instance? |
See also #1952 for the investigation into the impact of having multiple appliances on a single VC. |
Related to #1941, which addresses the new automated install of the plug-ins. |
Some changes in plug-in installation/upgrade behaviour are listed in #1952, which is in 1.4.3. |
Moving back to To Do, pending the completion of #1952. |
It looks like two of the issues from Epic #1952 are in 1.4.3, the other two are slated for 1.5.0. |
Per conversation with @jooskim, we should document how the VIC client handles multiple VIC appliances being registered with the same vCenter Server instance.
The text was updated successfully, but these errors were encountered: