Skip to content

Releases: vmware/vic-product

vSphere Integrated Containers Appliance v1.4.3

17 Sep 02:19
@DanielXiao DanielXiao
v1.4.3
deedb98
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 Appliance v1.4.3

What's in the Release Notes

Download

Official vSphere Integrated Containers release: http://www.vmware.com/go/download-vic

Open-source vSphere Integrated Containers project download location: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.4.3-6240-deedb985.ova

Filesize (vic-v1.4.3-6240-deedb985.ova) = 3407800320
SHA256 (vic-v1.4.3-6240-deedb985.ova) = 914d373fca75fbccd76dfb53a9939910e120466c5e944f8a50ce190c56000c34
SHA1 (vic-v1.4.3-6240-deedb985.ova) = ae672f81a4ecbd9a041b98ea33f7f0614b1676b6
MD5 (vic-v1.4.3-6240-deedb985.ova) = dac10f8eab16f52e5429a1cbdb15a36f

This OVA contains the following component versions:

--admiral v1.4.3 \
--harbor https://storage.googleapis.com/harbor-releases/harbor-offline-installer-v1.5.3.tgz  \
--vicengine https://storage.googleapis.com/vic-engine-releases/vic_v1.4.3.tar.gz \
--vicmachineserver v1.4.3
--vicui https://storage.googleapis.com/vic-ui-releases/vic_ui_v1.4.3.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.

Changes

Full list of changes from 1.4.2.

New Features

vSphere Integrated Containers 1.4.3 includes the following new features:

  • Automatic installation or upgrade of the vSphere Integrated Containers plug-in for the vSphere Client during deployment and upgrade of the appliance. Read more.
  • Added VM-Host Affinity option to the Create Virtual Container Host wizard. Read more.
  • Added vic-machine create --no-proxy option to skip proxying for certain URLs or domains. Read more.
  • Added shell auto-complete function to vic-machine. Read more.

Enhancements

vSphere Integrated Containers 1.4.3 includes the following improvements:

  • Added vCenter Server thumbprint verification to the initialization process during deployment and upgrade of the appliance, to improve security. Read more.
  • Added appliance address and version information in the vSphere Integrated Containers plug-in for the vSphere Client. Read more.
  • Improved the specification of a routing destination and gateway for the management network in the Create Virtual Container Host wizard. Read more.
  • Added VM ID to the output of vic-machine create and inspect. Read more.
  • Removed UI packages from vSphere Integrated Containers Engine bundle. Read more.
  • Bug fixes listed in Resolved Issues below.

Resolved Issues

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

  • Using FQDN when generating certificates for dch-photon results in a <nil> certificate. #925
    When generating certificates for use with dch-photon, if you use an FQDN in the -vic-ip parameter the resulting certificate is invalid.

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

Known Issues

With the exception of the resolved issue above, v1.4.3 has the same known issues as v1.4.2.

View all

  • Appliance upgrade script does not support FQDN addresses for the old appliance #1731
    When you run the script to upgrade the vSphere Integrated Containers appliance, the script prompts you for the FQDN or IP address of the old version of the appliance. However, the script only supports IP addresses for the appliance, and does not support FQDN addresses. You can use FQDN for vCenter Server addresses.

  • Appliance services are not available if accessed through NAT or a reverse proxy. #1172
    The Getting Started page of the appliance includes links to the services running on the appliance. These links are constructed assuming that users connect to the appliance by using its IP or FQDN, and that it is not hidden behind NAT or a reverse proxy.

    Workaround: Add the FDQN by which the appliance identifies itself to the /etc/hosts file of the client machine, pointing to the translated IP address that the client sees.

  • vSphere Client shows warnings when you attempt legitimate operations on the appliance VM. #1184
    If you attempt to perform operations on the appliance VM, for example migrate it, move it to a new folder, or restart it, you see a warning that the the VM is managed by Solution vSphere Integrated Containers-H5Client.

    Workaround: Ignore the warnings and click Yes to proceed with the operation.


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 are available in the LICENSE file.

Assets 2
Loading

vSphere Integrated Containers Appliance v1.4.2

23 Jul 10:55
@DanielXiao DanielXiao
v1.4.2
4ee4939
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 Appliance v1.4.2

What's in the Release Notes

Download

Official vSphere Integrated Containers release: http://www.vmware.com/go/download-vic

Open-source vSphere Integrated Containers project download location: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.4.2-5659-4ee49390.ova

Filesize (vic-v1.4.2-5659-4ee49390.ova) = 3868856320
SHA256 (vic-v1.4.2-5659-4ee49390.ova) = 6ee254f7c56af0f7118e0f5f41031aa9a3577083c51a880f2d4fe8aa7a11738c
SHA1 (vic-v1.4.2-5659-4ee49390.ova) = 7ac67caa81ea8e36b97ec7ac62644fb65a7461c6
MD5 (vic-v1.4.2-5659-4ee49390.ova) = d5e0a614470ec27d01c5dd3f601884ad

This OVA contains the following component versions:

--admiral v1.4.1 \
--harbor https://storage.googleapis.com/harbor-releases/harbor-offline-installer-v1.5.2.tgz  \
--vicengine https://storage.googleapis.com/vic-engine-releases/vic_v1.4.1.tar.gz \
--vicmachineserver v1.4.1

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. For information about upgrading the plug-in, see Upgrade the vSphere Client Plug-Ins on vCenter Server for Windows or Upgrade the vSphere Client Plug-Ins on vCenter Server Appliance.
  • 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.1.

New Features

This release includes the bug fixes listed below.

Enhancements

This release includes the bug fixes listed below.

Resolved Issues

Bumped up Clair to 2.0.4 in vSphere Integrated Containers Registry, fixed issue #5231 (Clair stuck in a loop: "could not branch Ubuntu repository". See vSphere Integrated Containers Registry 1.5.2

Additionally, the following other issues have been addressed:

  • Deploying the OVA with ovftool results in warnings about file size mismatch. #1166
    If you use ovftool to deploy the appliance, the process ends with the error Wrong file size specified in OVF descriptor for 'vic-disk1.vmdk' and 'vic-disk2.vmdk'. However the deployment succeeds.
  • The automated upgrade script marks moved disks as independent #1884
    During the automated upgrade process, disks were marked as independent disks, preventing them from being included in future snapshots.

Known Issues

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

View all

  • Appliance upgrade script does not support FQDN addresses for the old appliance #1731
    When you run the script to upgrade the vSphere Integrated Containers appliance, the script prompts you for the FQDN or IP address of the old version of the appliance. However, the script only supports IP addresses for the appliance, and does not support FQDN addresses. You can use FQDN for vCenter Server addresses.

  • Using FQDN when generating certificates for dch-photon results in a <nil> certificate. #925
    When generating certificates for use with dch-photon, if you use an FQDN in the -vic-ip parameter the resulting certificate is invalid.

    Workaround: Always specify an IP address in the -vic-ip parameter.

  • Appliance services are not available if accessed through NAT or a reverse proxy. #1172
    The Getting Started page of the appliance includes links to the services running on the appliance. These links are constructed assuming that users connect to the appliance by using its IP or FQDN, and that it is not hidden behind NAT or a reverse proxy.

    Workaround: Add the FDQN by which the appliance identifies itself to the /etc/hosts file of the client machine, pointing to the translated IP address that the client sees.

  • vSphere Client shows warnings when you attempt legitimate operations on the appliance VM. #1184
    If you attempt to perform operations on the appliance VM, for example migrate it, move it to a new folder, or restart it, you see a warning that the the VM is managed by Solution vSphere Integrated Containers-H5Client.

    Workaround: Ignore the warnings and click Yes to proceed with the operation.


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 are available in the LICENSE file.

Assets 2
Loading

vSphere Integrated Containers Appliance v1.4.2-rc3

23 Jul 02:22
@zjs zjs
v1.4.2-rc3
4ee4939
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 Appliance v1.4.2-rc3 Pre-release
Pre-release

What's in the Release Notes

Download

Download location: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.4.2-rc3-5647-4ee49390.ova

This OVA contains the following component versions:

--admiral v1.4.1 \
--harbor https://storage.googleapis.com/harbor-releases/harbor-offline-installer-v1.5.2-RC1.tgz \
--vicengine https://storage.googleapis.com/vic-engine-releases/vic_v1.4.1.tar.gz \
--vicmachineserver v1.4.1

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.

Changes

Full list of changes from 1.4.1.

New Features

This release includes the bug fixes listed below.

Enhancements

This release includes the bug fixes listed below.

Resolved Issues

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

Additionally, the following other issues have been addressed:

  • Deploying the OVA with ovftool results in warnings about file size mismatch. #1166
    If you use ovftool to deploy the appliance, the process ends with the error Wrong file size specified in OVF descriptor for 'vic-disk1.vmdk' and 'vic-disk2.vmdk'. However the deployment succeeds.
  • The automated upgrade script marks moved disks as independent #1884
    During the automated upgrade process, disks were marked as independent disks, preventing them from being included in future snapshots.

Known Issues

With the exception of the resolved issue above, v1.4.2-rc3 has the same known issues as v1.4.1.

View all

  • Appliance upgrade script does not support FQDN addresses for the old appliance #1731
    When you run the script to upgrade the vSphere Integrated Containers appliance, the script prompts you for the FQDN or IP address of the old version of the appliance. However, the script only supports IP addresses for the appliance, and does not support FQDN addresses. You can use FQDN for vCenter Server addresses.

  • Using FQDN when generating certificates for dch-photon results in a <nil> certificate. #925
    When generating certificates for use with dch-photon, if you use an FQDN in the -vic-ip parameter the resulting certificate is invalid.

    Workaround: Always specify an IP address in the -vic-ip parameter.

  • Appliance services are not available if accessed through NAT or a reverse proxy. #1172
    The Getting Started page of the appliance includes links to the services running on the appliance. These links are constructed assuming that users connect to the appliance by using its IP or FQDN, and that it is not hidden behind NAT or a reverse proxy.

    Workaround: Add the FDQN by which the appliance identifies itself to the /etc/hosts file of the client machine, pointing to the translated IP address that the client sees.

  • vSphere Client shows warnings when you attempt legitimate operations on the appliance VM. #1184
    If you attempt to perform operations on the appliance VM, for example migrate it, move it to a new folder, or restart it, you see a warning that the the VM is managed by Solution vSphere Integrated Containers-H5Client.

    Workaround: Ignore the warnings and click Yes to proceed with the operation.


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 are available in the LICENSE file.

Assets 2
Loading

vSphere Integrated Containers Appliance v1.4.2-rc2

20 Jul 03:23
@zjs zjs
v1.4.2-rc2
247225e
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 Appliance v1.4.2-rc2 Pre-release
Pre-release

What's in the Release Notes

Download

Download location: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.4.2-rc2-5630-247225e7.ova

This OVA contains the following component versions:

--admiral v1.4.1 \
--harbor https://storage.googleapis.com/harbor-releases/harbor-offline-installer-v1.5.2-RC1.tgz \
--vicengine https://storage.googleapis.com/vic-engine-releases/vic_v1.4.1.tar.gz \
--vicmachineserver v1.4.1

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.

Changes

Full list of changes from 1.4.1.

New Features

This release includes the bug fixes listed below.

Enhancements

This release includes the bug fixes listed below.

Resolved Issues

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

Additionally, the following other issues have been addressed:

  • Deploying the OVA with ovftool results in warnings about file size mismatch. #1166
    If you use ovftool to deploy the appliance, the process ends with the error Wrong file size specified in OVF descriptor for 'vic-disk1.vmdk' and 'vic-disk2.vmdk'. However the deployment succeeds.

Known Issues

With the exception of the resolved issue above, v1.4.2-rc2 has the same known issues as v1.4.1.

View all

  • Appliance upgrade script does not support FQDN addresses for the old appliance #1731
    When you run the script to upgrade the vSphere Integrated Containers appliance, the script prompts you for the FQDN or IP address of the old version of the appliance. However, the script only supports IP addresses for the appliance, and does not support FQDN addresses. You can use FQDN for vCenter Server addresses.

  • Using FQDN when generating certificates for dch-photon results in a <nil> certificate. #925
    When generating certificates for use with dch-photon, if you use an FQDN in the -vic-ip parameter the resulting certificate is invalid.

    Workaround: Always specify an IP address in the -vic-ip parameter.

  • Appliance services are not available if accessed through NAT or a reverse proxy. #1172
    The Getting Started page of the appliance includes links to the services running on the appliance. These links are constructed assuming that users connect to the appliance by using its IP or FQDN, and that it is not hidden behind NAT or a reverse proxy.

    Workaround: Add the FDQN by which the appliance identifies itself to the /etc/hosts file of the client machine, pointing to the translated IP address that the client sees.

  • vSphere Client shows warnings when you attempt legitimate operations on the appliance VM. #1184
    If you attempt to perform operations on the appliance VM, for example migrate it, move it to a new folder, or restart it, you see a warning that the the VM is managed by Solution vSphere Integrated Containers-H5Client.

    Workaround: Ignore the warnings and click Yes to proceed with the operation.


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 are available in the LICENSE file.

Assets 2
Loading

vSphere Integrated Containers Appliance v1.4.2-rc1

20 Jul 03:22
@zjs zjs
v1.4.2-rc1
01961f2
Compare
Choose a tag to compare
vSphere Integrated Containers Appliance v1.4.2-rc1 Pre-release
Pre-release

What's in the Release Notes

Download

Download location: (pending)

This OVA contains the following component versions:

--admiral v1.4.1 \
--harbor https://storage.googleapis.com/harbor-releases/harbor-offline-installer-v1.5.2-RC1.tgz \
--vicengine https://storage.googleapis.com/vic-engine-releases/vic_v1.4.1.tar.gz \
--vicmachineserver v1.4.1

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.

Changes

Full list of changes from 1.4.1.

New Features

This release includes the bug fixes listed below.

Enhancements

This release includes the bug fixes listed below.

Resolved Issues

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

Additionally, the following other issues have been addressed:

  • Deploying the OVA with ovftool results in warnings about file size mismatch. #1166
    If you use ovftool to deploy the appliance, the process ends with the error Wrong file size specified in OVF descriptor for 'vic-disk1.vmdk' and 'vic-disk2.vmdk'. However the deployment succeeds.

Known Issues

With the exception of the resolved issue above, v1.4.2-rc1 also has the same known issues as v1.4.1.

View all

  • Appliance upgrade script does not support FQDN addresses for the old appliance #1731
    When you run the script to upgrade the vSphere Integrated Containers appliance, the script prompts you for the FQDN or IP address of the old version of the appliance. However, the script only supports IP addresses for the appliance, and does not support FQDN addresses. You can use FQDN for vCenter Server addresses.

  • Using FQDN when generating certificates for dch-photon results in a <nil> certificate. #925
    When generating certificates for use with dch-photon, if you use an FQDN in the -vic-ip parameter the resulting certificate is invalid.

    Workaround: Always specify an IP address in the -vic-ip parameter.

  • Appliance services are not available if accessed through NAT or a reverse proxy. #1172
    The Getting Started page of the appliance includes links to the services running on the appliance. These links are constructed assuming that users connect to the appliance by using its IP or FQDN, and that it is not hidden behind NAT or a reverse proxy.

    Workaround: Add the FDQN by which the appliance identifies itself to the /etc/hosts file of the client machine, pointing to the translated IP address that the client sees.

  • vSphere Client shows warnings when you attempt legitimate operations on the appliance VM. #1184
    If you attempt to perform operations on the appliance VM, for example migrate it, move it to a new folder, or restart it, you see a warning that the the VM is managed by Solution vSphere Integrated Containers-H5Client.

    Workaround: Ignore the warnings and click Yes to proceed with the operation.


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 are available in the LICENSE file.

Assets 2
Loading

vSphere Integrated Containers Appliance v1.4.1

03 Jul 17:49
@zjs zjs
v1.4.1
ad7eb5f
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 Appliance v1.4.1

What's in the Release Notes

Download

Official vSphere Integrated Containers release: http://www.vmware.com/go/download-vic

Open-source vSphere Integrated Containers project download location: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.4.1-5547-ad7eb5f8.ova

Filesize (vic-v1.4.1-5547-ad7eb5f8.ova) = 3402752000
SHA256 (vic-v1.4.1-5547-ad7eb5f8.ova) = fd8b0dc0fbb555a1e4ff1a29425b3cfdb7260ce95f6e8b41c7ce2bb024112133
SHA1 (vic-v1.4.1-5547-ad7eb5f8.ova) = b579b12a2cc639c797f602713ed7ff9c506a37b7
MD5 (vic-v1.4.1-5547-ad7eb5f8.ova) = ed072929426d16c51ad5363ea449af2a

This OVA contains the following component versions:

--admiral vic_v1.4.1 \
--harbor https://storage.googleapis.com/harbor-releases/harbor-offline-installer-v1.5.1.tgz \
--vicengine https://storage.googleapis.com/vic-engine-releases/vic_v1.4.1.tar.gz \
--vicmachineserver v1.4.1

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.

Changes

Full list of changes from 1.4.0.

New Features

This release includes the bug fixes and enhancements listed below.

Enhancements

See the enhancements for the following vSphere Integrated Containers components:

Resolved Issues

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

Additionally, the following other issues have been addressed:

  • The OVF now uses the VMXNET3 adapter. #1746
    Previously, the E1000 adapter was used.
  • The OVF now uses distinct property keys for registry and management ports. #1642
    Previously, the OVF used similar keys for the registry and management ports causing a collision when deploying via the vSphere H5 client. (Note: please refer to the vSphere documentation for information about which vSphere H5 Client versions support deployment of OVAs.)

Known Issues

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

View all

  • The automated upgrade script marks moved disks as independent #1884
    During the automated upgrade process, disks were marked as independent disks, preventing them from being included in future snapshots. This is fixed in vSphere Integrated Containers 1.4.2.

  • Appliance upgrade script does not support FQDN addresses for the old appliance #1731
    When you run the script to upgrade the vSphere Integrated Containers appliance, the script prompts you for the FQDN or IP address of the old version of the appliance. However, the script only supports IP addresses for the appliance, and does not support FQDN addresses. You can use FQDN for vCenter Server addresses.

  • Using FQDN when generating certificates for dch-photon results in a <nil> certificate. #925
    When generating certificates for use with dch-photon, if you use an FQDN in the -vic-ip parameter the resulting certificate is invalid.

    Workaround: Always specify an IP address in the -vic-ip parameter.

  • Appliance services are not available if accessed through NAT or a reverse proxy. #1172
    The Getting Started page of the appliance includes links to the services running on the appliance. These links are constructed assuming that users connect to the appliance by using its IP or FQDN, and that it is not hidden behind NAT or a reverse proxy.

    Workaround: Add the FDQN by which the appliance identifies itself to the /etc/hosts file of the client machine, pointing to the translated IP address that the client sees.

  • vSphere Client shows warnings when you attempt legitimate operations on the appliance VM. #1184
    If you attempt to perform operations on the appliance VM, for example migrate it, move it to a new folder, or restart it, you see a warning that the the VM is managed by Solution vSphere Integrated Containers-H5Client.

    Workaround: Ignore the warnings and click Yes to proceed with the operation.

  • Deploying the OVA with ovftool results in warnings about file size mismatch. #1166
    If you use ovftool to deploy the appliance, the process ends with the error Wrong file size specified in OVF descriptor for 'vic-disk1.vmdk' and 'vic-disk2.vmdk'. However the deployment succeeds.

    Workaround: Ignore the error message.


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 are available in the LICENSE file.

Assets 2
Loading

vSphere Integrated Containers Appliance v1.4.1-rc3

02 Jul 16:37
@zjs zjs
v1.4.1-rc3
7ce70c6
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 Appliance v1.4.1-rc3 Pre-release
Pre-release

What's in the Release Notes

Download

Download location: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.4.1-rc3-5526-7ce70c63.ova

This OVA contains the following component versions:

--admiral v1.4.1-rc3 \
--harbor https://storage.googleapis.com/harbor-releases/harbor-offline-installer-v1.5.1.tgz \
--vicengine https://storage.googleapis.com/vic-engine-releases/vic_v1.4.1-rc2.tar.gz \
--vicmachineserver v1.4.1-rc2

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.

Changes

Full list of changes from 1.4.0.

New Features

This release includes the bug fixes and enhancements listed below.

Enhancements

See the enhancements for the following vSphere Integrated Containers components:

Resolved Issues

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

Additionally, the following other issues have been addressed:

  • The OVF now uses the VMXNET3 adapter. #1746
    Previously, the E1000 adapter was used.
  • The OVF now uses distinct property keys for registry and management ports. #1642
    Previously, the OVF used similar keys for the registry and management ports causing a collision when deploying via the vSphere H5 client. (Note: please refer to the vSphere documentation for information about which vSphere H5 Client versions support deployment of OVAs.)

Known Issues

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

View all

  • Appliance upgrade script does not support FQDN addresses for the old appliance #1731
    When you run the script to upgrade the vSphere Integrated Containers appliance, the script prompts you for the FQDN or IP address of the old version of the appliance. However, the script only supports IP addresses for the appliance, and does not support FQDN addresses. You can use FQDN for vCenter Server addresses.

  • Using FQDN when generating certificates for dch-photon results in a <nil> certificate. #925
    When generating certificates for use with dch-photon, if you use an FQDN in the -vic-ip parameter the resulting certificate is invalid.

    Workaround: Always specify an IP address in the -vic-ip parameter.

  • Appliance services are not available if accessed through NAT or a reverse proxy. #1172
    The Getting Started page of the appliance includes links to the services running on the appliance. These links are constructed assuming that users connect to the appliance by using its IP or FQDN, and that it is not hidden behind NAT or a reverse proxy.

    Workaround: Add the FDQN by which the appliance identifies itself to the /etc/hosts file of the client machine, pointing to the translated IP address that the client sees.

  • vSphere Client shows warnings when you attempt legitimate operations on the appliance VM. #1184
    If you attempt to perform operations on the appliance VM, for example migrate it, move it to a new folder, or restart it, you see a warning that the the VM is managed by Solution vSphere Integrated Containers-H5Client.

    Workaround: Ignore the warnings and click Yes to proceed with the operation.

  • Deploying the OVA with ovftool results in warnings about file size mismatch. #1166
    If you use ovftool to deploy the appliance, the process ends with the error Wrong file size specified in OVF descriptor for 'vic-disk1.vmdk' and 'vic-disk2.vmdk'. However the deployment succeeds.

    Workaround: Ignore the error message.


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 are available in the LICENSE file.

Assets 2
Loading

vSphere Integrated Containers Appliance v1.4.1-rc2

29 Jun 01:07
@zjs zjs
v1.4.1-rc2
f2fdac7
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 Appliance v1.4.1-rc2 Pre-release
Pre-release

What's in the Release Notes

Download

Download location: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.4.1-rc2-5496-f2fdac75.ova

This OVA contains the following component versions:

--admiral v1.4.1-rc2 \
--harbor https://storage.googleapis.com/harbor-releases/harbor-offline-installer-v1.5.1.tgz \
--vicengine https://storage.googleapis.com/vic-engine-releases/vic_v1.4.1-rc2.tar.gz \
--vicmachineserver v1.4.1-rc2

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.

Changes

Full list of changes from 1.4.0.

New Features

This release includes the bug fixes and enhancements listed below.

Enhancements

See the enhancements for the following vSphere Integrated Containers components:

Resolved Issues

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

Additionally, the following other issues have been addressed:

  • The OVF now uses the VMXNET3 adapter. #1746
    Previously, the E1000 adapter was used.
  • The OVF now uses distinct property keys for registry and management ports. #1642
    Previously, the OVF used similar keys for the registry and management ports causing a collision when deploying via the vSphere H5 client. (Note: please refer to the vSphere documentation for information about which vSphere H5 Client versions support deployment of OVAs.)

Known Issues

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

View all

  • Appliance upgrade script does not support FQDN addresses for the old appliance #1731
    When you run the script to upgrade the vSphere Integrated Containers appliance, the script prompts you for the FQDN or IP address of the old version of the appliance. However, the script only supports IP addresses for the appliance, and does not support FQDN addresses. You can use FQDN for vCenter Server addresses.

  • Using FQDN when generating certificates for dch-photon results in a <nil> certificate. #925
    When generating certificates for use with dch-photon, if you use an FQDN in the -vic-ip parameter the resulting certificate is invalid.

    Workaround: Always specify an IP address in the -vic-ip parameter.

  • Appliance services are not available if accessed through NAT or a reverse proxy. #1172
    The Getting Started page of the appliance includes links to the services running on the appliance. These links are constructed assuming that users connect to the appliance by using its IP or FQDN, and that it is not hidden behind NAT or a reverse proxy.

    Workaround: Add the FDQN by which the appliance identifies itself to the /etc/hosts file of the client machine, pointing to the translated IP address that the client sees.

  • vSphere Client shows warnings when you attempt legitimate operations on the appliance VM. #1184
    If you attempt to perform operations on the appliance VM, for example migrate it, move it to a new folder, or restart it, you see a warning that the the VM is managed by Solution vSphere Integrated Containers-H5Client.

    Workaround: Ignore the warnings and click Yes to proceed with the operation.

  • Deploying the OVA with ovftool results in warnings about file size mismatch. #1166
    If you use ovftool to deploy the appliance, the process ends with the error Wrong file size specified in OVF descriptor for 'vic-disk1.vmdk' and 'vic-disk2.vmdk'. However the deployment succeeds.

    Workaround: Ignore the error message.


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 are available in the LICENSE file.

Assets 2
Loading

vSphere Integrated Containers Appliance v1.4.1-rc1

23 Jun 06:51
@zjs zjs
v1.4.1-rc1
f52b38e
Compare
Choose a tag to compare
vSphere Integrated Containers Appliance v1.4.1-rc1 Pre-release
Pre-release

What's in the Release Notes

Download

Download location: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.4.1-rc1-5422-f52b38e5.ova

This OVA contains the following component versions:

--admiral v1.4.1-rc1 \
--harbor https://storage.googleapis.com/harbor-releases/harbor-offline-installer-v1.5.1.tgz \
--vicengine https://storage.googleapis.com/vic-engine-releases/vic_v1.4.1-rc1.tar.gz \
--vicmachineserver v1.4.1-rc1

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.

Changes

Full list of changes from 1.4.0.

New Features

This release includes the bug fixes and enhancements listed below.

Enhancements

See the enhancements for the following vSphere Integrated Containers components:

Resolved Issues

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

Known Issues

  • After restarting the OVA, the Management Portal becomes inaccessible.
    There is no known work-around for this issue at this time.

v1.4.1-rc1 also has the same known issues as v1.4.0.

View all

  • Appliance upgrade script does not support FQDN addresses for the old appliance #1731
    When you run the script to upgrade the vSphere Integrated Containers appliance, the script prompts you for the FQDN or IP address of the old version of the appliance. However, the script only supports IP addresses for the appliance, and does not support FQDN addresses. You can use FQDN for vCenter Server addresses.

  • Using FQDN when generating certificates for dch-photon results in a <nil> certificate. #925
    When generating certificates for use with dch-photon, if you use an FQDN in the -vic-ip parameter the resulting certificate is invalid.

    Workaround: Always specify an IP address in the -vic-ip parameter.

  • Appliance services are not available if accessed through NAT or a reverse proxy. #1172
    The Getting Started page of the appliance includes links to the services running on the appliance. These links are constructed assuming that users connect to the appliance by using its IP or FQDN, and that it is not hidden behind NAT or a reverse proxy.

    Workaround: Add the FDQN by which the appliance identifies itself to the /etc/hosts file of the client machine, pointing to the translated IP address that the client sees.

  • vSphere Client shows warnings when you attempt legitimate operations on the appliance VM. #1184
    If you attempt to perform operations on the appliance VM, for example migrate it, move it to a new folder, or restart it, you see a warning that the the VM is managed by Solution vSphere Integrated Containers-H5Client.

    Workaround: Ignore the warnings and click Yes to proceed with the operation.

  • Deploying the OVA with ovftool results in warnings about file size mismatch. #1166
    If you use ovftool to deploy the appliance, the process ends with the error Wrong file size specified in OVF descriptor for 'vic-disk1.vmdk' and 'vic-disk2.vmdk'. However the deployment succeeds.

    Workaround: Ignore the error message.


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 are available in the LICENSE file.

Assets 2
Loading

vSphere Integrated Containers Appliance v1.4.0

08 May 04:16
@andrewtchin andrewtchin
v1.4.0
f168720
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 Appliance v1.4.0

What's in the Release Notes

New Features

vSphere Integrated Containers appliance 1.4.0 includes the following new features in this release:

Download Binaries

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:

  • Tagging the appliance fails when vCenter password contains colon. #1080
    When registering the appliance with the Platform Services Controller, registration fails with the error Failed to locate VIC Appliance. Please check the vCenter Server provided and try again. This problem results from an issue in vSphere 6.5u1, and occurs if the vCenter Single Sign-On password contains a colon (:).
  • vSphere Integrated Containers appliance support bundle does not include Management Portal logs. #225
    Workaround: Download the Management Portal logs manually.

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

  • The automated upgrade script marks moved disks as independent #1884
    During the automated upgrade process, disks were marked as independent disks, preventing them from being included in future snapshots. This is fixed in vSphere Integrated Containers 1.4.2.

  • Appliance upgrade script does not support FQDN addresses for the old appliance #1731
    When you run the script to upgrade the vSphere Integrated Containers appliance, the script prompts you for the FQDN or IP address of the old version of the appliance. However, the script only supports IP addresses for the appliance, and does not support FQDN addresses. You can use FQDN for vCenter Server addresses.

  • Using FQDN when generating certificates for dch-photon results in a <nil> certificate. #925
    When generating certificates for use with dch-photon, if you use an FQDN in the -vic-ip parameter the resulting certificate is invalid.

    Workaround: Always specify an IP address in the -vic-ip parameter.

  • Appliance services are not available if accessed through NAT or a reverse proxy. #1172
    The Getting Started page of the appliance includes links to the services running on the appliance. These links are constructed assuming that users connect to the appliance by using its IP or FQDN, and that it is not hidden behind NAT or a reverse proxy.

    Workaround: Add the FDQN by which the appliance identifies itself to the /etc/hosts file of the client machine, pointing to the translated IP address that the client sees.

  • vSphere Client shows warnings when you attempt legitimate operations on the appliance VM. #1184
    If you attempt to perform operations on the appliance VM, for example migrate it, move it to a new folder, or restart it, you see a warning that the the VM is managed by Solution vSphere Integrated Containers-H5Client.

    Workaround: Ignore the warnings and click Yes to proceed with the operation.

  • Deploying the OVA with ovftool results in warnings about file size mismatch. #1166
    If you use ovftool to deploy the appliance, the process ends with the error Wrong file size specified in OVF descriptor for 'vic-disk1.vmdk' and 'vic-disk2.vmdk'. However the deployment succeeds.

    Workaround: Ignore the error message.

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