Skip to content

Releases: vmware/vic-ui

vSphere Integrated Containers UI v1.4.1

22 Jun 20:20
@lmalvins lmalvins
v1.4.1
6d1dc3c
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
vSphere Integrated Containers UI v1.4.1

What's in the Release Notes

Download Binaries

Open-source vSphere Integrated Containers UI project: https://storage.googleapis.com/vic-ui-releases/vic_ui_v1.4.1.tar.gz

Installation and Upgrade

IMPORTANT:

  • vSphere Integrated Containers 1.4.2 includes version 1.4.1 of the vSphere Integrated Containers plug-in for vSphere Client. If you are upgrading vSphere Integrated Containers from version 1.4.1 to 1.4.2, you must still upgrade the client plug-in after you upgrade the appliance. This is so that the plug-in registers correctly with the upgraded appliance. If you do not upgrade the plug-in after upgrading the appliance to 1.4.2, the vSphere Integrated Containers view does not appear in the vSphere Client.
  • If you use vSphere 6.7 update 1 or later, you must use vSphere Integrated Containers 1.4.3 or later. Due to significant changes in the HTML5 vSphere Client in version 6.7 update 1, previous versions of the vSphere Integrated Containers plug-in for the vSphere Client do not work with that version.

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.

Changes

Full list of changes from 1.4.0.

New Features

This release includes the enhancements and bug fixes listed below.

Enhancements

This release includes the following enhancements to existing features:

  • A confirmation message is now shown when copying CLI commands #442
    When copying a CLI command on the Summary page of the VCH Creation Wizard, a confirmation message is now shown.

Resolved Issues

The following issues that were documented as known issues in previous releases or reported by customers have been fixed in v1.4.1:

  • Port groups under a network folder don't show up in the VCH Creation Wizard #389
    The Configure Networks page of the VCH Creation Wizard did not display port groups located in network folders.
  • VCH Creation Wizard hangs on Configure Networks page #504
    In some environments, the Configure Networks page of the VCH Creation Wizard would fail to load.

Additionally, the following other issues have been addressed:

  • The Compute Capacity page of the VCH Creation Wizard no longer includes extraneous information about hosts. #440
    Previously, host status information (e.g., "reboot required") was incorrectly included in this component in some cases.
  • The Compute Capacity page of the VCH Creation Wizard correctly handles empty clusters #448
    Previously, names of empty clusters were displayed as blank.
  • The Networks page of the VCH Creation Wizard now allows selection of the IP Range setting. #462
    Previously,
    the IP Range radio button was not clickable on all systems and could only be reached by tabbing.
  • The Summary page of the VCH Creation Wizard now shows the port associated with insecure registries. #467
    Previously, the Summary page showed only the address for each registry.

See also the resolved issues for each of the vSphere Integrated Containers components:

Known Issues

With the exception of issues resolved above, v1.4.1 has the same known issues as v1.4.0.

View all
  • Create Virtual Container Host wizard plugin throws a parsing error when you specify only the gateway for the management or client networks. #vic/7602
    When you provide a gateway for the management or client network, it is mandatory to provide at least one routing destination. The Create Virtual Container Host wizard does not conform to this behavior and has two separate fields for the Gateway and Routing destinations. If you do not fill in both the fields correctly, the wizard reports a parsing error.

See also the known issues for each of the vSphere Integrated Containers components:

Open Source Components

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

Assets 2
Loading

vSphere Integrated Containers UI v1.4.0

04 May 16:38
@lmalvins lmalvins
v1.4.0
a4f1012
Compare
Choose a tag to compare
vSphere Integrated Containers UI v1.4.0

v1.3.1...v1.4.0

What's in the Release Notes

New Features

Stability improvements and bug fixes.

Download Binaries

Open-source vSphere Integrated Containers UI project: https://storage.googleapis.com/vic-ui-releases/vic_ui_v1.4.0.tar.gz

Installation and Upgrade

IMPORTANT: If you use vSphere 6.7 update 1 or later, you must use vSphere Integrated Containers 1.4.3 or later. Due to significant changes in the HTML5 vSphere Client in version 6.7 update 1, previous versions of the vSphere Integrated Containers plug-in for the vSphere Client do not work with that version.

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.

Resolved Issues

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

  • 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.
  • 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.
  • 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.
  • 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.

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

Known Issues

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

  • Create Virtual Container Host wizard plugin throws a parsing error when you specify only the gateway for the management or client networks. #vic/7602
    When you provide a gateway for the management or client network, it is mandatory to provide at least one routing destination. The Create Virtual Container Host wizard does not conform to this behavior and has two separate fields for the Gateway and Routing destinations. If you do not fill in both the fields correctly, the wizard reports a parsing error.

See also the known issues for each of the vSphere Integrated Containers components:

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.

Assets 2
Loading

vSphere Integrated Containers UI v1.4.0-rc3

24 Apr 21:27
@lmalvins lmalvins
v1.4.0-rc3
f2088ba
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
vSphere Integrated Containers UI v1.4.0-rc3 Pre-release
Pre-release

v1.3.1...v1.4.0-rc3

New Features

Stability improvements and bug fixes.

Download Binaries

Open-source vSphere Integrated Containers UI project: https://storage.googleapis.com/vic-ui-releases/vic_ui_v1.4.0-rc3.tar.gz

Installation and Upgrade

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.

NOTE: This documentation is a work-in-progress and has not yet been fully updated for 1.4.0.

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.

Resolved Issues

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

  • 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.
  • 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.
  • 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.
  • 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.

Known Issues

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

None at time of writing.

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

Assets 2
Loading

vSphere Integrated Containers UI v1.4.0-rc2

24 Apr 21:28
@lmalvins lmalvins
v1.4.0-rc2
7130fd3
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
vSphere Integrated Containers UI v1.4.0-rc2 Pre-release
Pre-release

v1.3.1...v1.4.0-rc2

Assets 2
Loading

vSphere Integrated Containers Engine Version 1.5.0 Dev

17 Apr 14:04
@mhagen-vmware mhagen-vmware
v1.5.0-dev
150ca12
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
vSphere Integrated Containers Engine Version 1.5.0 Dev Pre-release
Pre-release

This release tagged with the dev tag for the master branch and future release version. It will also serve as the location for our pre-release software bundles.

Assets 2
Loading

vSphere Integrated Containers UI v1.4.0-rc1

16 Apr 22:15
@jak-atx jak-atx
v1.4.0-rc1
c9d356f
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
vSphere Integrated Containers UI v1.4.0-rc1 Pre-release
Pre-release

v1.3.1...v1.4.0-rc1

New Features

Stability improvements and bug fixes.

Download Binaries

Open-source vSphere Integrated Containers UI project: https://storage.googleapis.com/vic-ui-releases/vic_ui_v1.4.0-rc1.tar.gz

Installation and Upgrade

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.

NOTE: This documentation is a work-in-progress and has not yet been fully updated for 1.4.0.

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.

Resolved Issues

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

  • 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.
  • 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.
  • 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.
  • 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.

Known Issues

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

None at time of writing.

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

Assets 2
Loading

vSphere Integrated Containers UI v1.3.1

05 Feb 15:30
@mdubya66 mdubya66
v1.3.1
2802645
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
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:

  • 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:

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

Installation

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.

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.

Assets 2
Loading

vSphere Integrated Containers UI v1.3.1-rc2

02 Feb 23:12
@jooskim jooskim
v1.3.1-rc2
2802645
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
vSphere Integrated Containers UI v1.3.1-rc2 Pre-release
Pre-release

v1.3.1-rc1...v1.3.1-rc2

Assets 2
Loading

vSphere Integrated Containers UI v1.3.1-rc1

19 Jan 21:26
@jak-atx jak-atx
v1.3.1-rc1
6988138
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
vSphere Integrated Containers UI v1.3.1-rc1 Pre-release
Pre-release

v1.3.0...v1.3.1-rc1

Assets 2
Loading

vSphere Integrated Containers UI v1.3.0

10 Jan 16:03
@jak-atx jak-atx
v1.3.0
b506b97
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
vSphere Integrated Containers UI v1.3.0

v1.3.0-rc1...v1.3.0

New Features

Create Virtual Container Host wizard in the vSphere Integrated Containers plug-in for the HTML5 vSphere Client. This feature allows you to deploy VCHs interactively, directly from the vSphere Client. Read more

Known Issues

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

  • 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.

    Workaround: Manually edit the generated command to correct the option name to --volume-store.

  • Plug-in upgrade script incorrectly warns that you are trying to install an older version. #183
    When you run the plug-in upgrade script, 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.

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

  • 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.

    Workaround: Delete the empty clusters from the vCenter Server inventory.

  • 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.

    Workaround: Create at least two distributed port groups, for the bridge and public networks.

  • Virtual Container Hosts view is empty in versions of Chrome older than version 56. #187
    If you go to the Virtual Container Hosts view of the vSphere Integrated Containers plug-in in an older version of Chrome, the VCH list is empty. If you right-click in the browser and select Inspect, you see an Uncaught TypeError.

    Workaround: Upgrade Chrome to a version greater than version 56.

Download Binaries

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.

Using vSphere Integrated Containers

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

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.

Assets 2
Loading