vSphere Integrated Containers UI v1.3.1

v1.3.0...v1.3.1

New Features

vSphere Integrated Containers Plug-In for vSphere Client includes the following new features in this release:

• Usability improvements in the Create Virtual Container Host wizard in the vSphere Integrated Containers Plug-In for vSphere Client:

  • Separated the Security and Registry Access settings into distinct pages.
  • Improved the automatic granting of permissions to the Operations User account.

• Bug fixes listed in Resolved Issues below.

Resolved Issues

The following issues that were documented as known issues in previous releases have been fixed in 1.3.1:

• Not all accessible port groups are displayed in the network selector. #310
  This has been fixed.
• Generated vic-machine command includes incorrect --volume-stores option. #251
  In the Summary page of the Create VCH wizard, if you configured a volume store, the generated vic-machine command includes the option --volume-stores. This should be --volume-store. Attempting to run the generated command results in the error Incorrect Usage: flag provided but not defined: -volume-stores.
• Configure Networks page does not load if no distributed port groups exist. #275
  In the Configure Networks page of the Create VCH wizard, if your vCenter Server setup does not include any distributed port groups, the page does not populate and you cannot continue with the deployment of the VCH.
• Compute resource selector does not work with two empty clusters in inventory. #274
  In the Compute Capacity page of the Create VCH wizard, if your vCenter Server inventory includes at least two empty clusters, the compute resource selector does not populate and you cannot continue with the deployment of the VCH.

See also the resolved issues sections of the release notes for each of the other vSphere Integrated Containers components:

• vSphere Integrated Containers Appliance
• vSphere Integrated Containers Engine

There are no changes to vSphere Integrated Containers Registry or Management Portal in this release. See the full list of all issues fixed in 1.3.1 for all components (requires Zenhub plug-in for Github).

Known Issues

The following issues affect the vSphere Integrated Containers plug-in for vSphere Client 1.3.1:

• OVA endpoint appears as null in plug-in when deploying multiple instances of the vSphere Integrated Containers appliance. #365
  The plug-in installer marks only the exact vSphere Integrated Containers appliance that it shipped with as being managed by the plug-in and does not mark any other appliances as such. This can cause some unexpected behaviors such as the OVA endpoint appearing as null if you deploy multiple appliances to the same vCenter Server instance.

  Workaround: Make sure that you complete the plug-in installation after you have registered an appliance with the Platform Services Controller before you deploy another instance of the appliance. You must run the plug-in installer for every appliance that you deploy.

• VCH inventory list and create wizard fails to load when vCenter Server session expires. #228
  If the vCenter server authentication session expires, reloading the VCH inventory list hangs with the error Could not find any VIC appliance VM. Attempts to create a VCH fail with the error Error creating VCH.

  Workaround: Reload the browser session and re-authenticate to vCenter Server.

• Plug-in does not appear after successful installation and restart of the vSphere Client services. #299
  If you have successfully installed the plug-in and restarted the vSphere Client services and you do not see the plug-in in the vSphere Client, you might be encountering an SSL certificate mismatch issue. This can occur if the root CA on the vCenter Server Virtual Appliance is updated, either by upgrading to a newer build of vSphere or by running the VMCA Certificate Manager.

  Workaround: See https://kb.vmware.com/kb/52540.

• Plug-in upgrade script incorrectly warns that you are trying to install an older version. #183
  When you run the plug-in upgrade script to upgrade from 1.2.x to 1.3.x, the output warns you that You are trying to install plugins of an older or same version even when you are installing a later version of the plug-in. This does not apply to upgrades from 1.3.0 to 1.3.1.

  Workaround: Ignore the warning and enter yes to proceed with the upgrade.

Download Binaries

• Official VMware vSphere Integated Containers 1.3.1 release: http://www.vmware.com/go/download-vic.
• Open-source vSphere Integrated Containers UI project: https://storage.googleapis.com/vic-ui-releases/vic_ui_v1.3.1.tar.gz

Installation

• For instructions about how to deploy the vSphere Integrated Containers appliance and install the vSphere Client plug-in, see Deploy the vSphere Integrated Containers Appliance and Installing the vSphere Client Plug-Ins.
• For instructions about how to upgrade the vSphere Integrated Containers appliance and upgrade the vSphere Client plug-in, see Upgrade the vSphere Integrated Containers Appliance, Upgrade the vSphere Client Plug-Ins on vCenter Server for Windows, and Upgrade the vSphere Client Plug-Ins on vCenter Server Appliance.

Using vSphere Integrated Containers

For more details on using vSphere Integrated Containers see the end user documentation at https://vmware.github.io/vic-product/#documentation.

• Overview of vSphere Integrated Containers
• Install, Deploy, and Maintain the vSphere Integrated Containers Infrastructure
• Configure and Manage vSphere Integrated Containers
• Develop Container Applications with vSphere Integrated Containers

Open Source Components

The copyright statements and licenses applicable to the open source software components distributed in vSphere Integrated Containers Engine are available in the LICENSE file.