Releases: vmware-archive/admiral
vic_v1.3.0
Docker hub image: https://hub.docker.com/r/vmware/admiral/ vic_v1.3.0
New Features
This release provides the following new features and enhancements:
- vSphere Integrated Containers Management Portal now uses the Docker Events REST API to display the status of containers and hosts as close as possible to the status reported by the underlying hosts.
- vSphere Integrated Containers Management Portal now supports VCH container network definitions with the
--container-network-ip-rangein a non-CIDR format. For more information, see Configure Container Networks.
Resolved Issues
The following issues found in previous versions have been fixed in 1.3.0:
- Spawning container using container networks may fail when using VCH. #228
In some cases the VCH where the container is being provisioned, for some reason, returns a very big response (>10MB) when doing an INSPECT on that just provisioned container. And since Admiral expects a relatively small answer (<32KB) that big response can't be stored. The problematic part of the big response is the HostConfig.PortBindings section, because it includes all the system ports with an actual empty configuration. The fix consist of ignoring all the useless system ports in the Admiral side, unless until the issue is fixed in the VCH side. - Admiral UI failed to load a particular user (or group) when there are many users (or groups) on PSC #225
When having available more than 100 users that start with the same prefix (e.g. user1, user10, user11, user100, user101, user1000, etc.), it may happen that when searching for a particular user (e.g. user1) the response from PSC does not contain the desired one. The fix consist of adding to the list of matching users and groups returned by PSC also the exact match of the search criteria if it's an actual user or group. - Admiral's containers page loads slowly #219
When having a large amount of containers, scrolling down the Container page keeps refreshing and loads new content pretty slowly. - Project rename breaks Harbor registry functionalities #218
The project name cannot be renamed as the repository was stored in the default registry (Harbor) with the project name.
Known Issues
docker execalways returns 0 and ignores the exit code of processes. vic/#5692docker execalways returns 0, even if you specify-it. This issue is potentially due to a delay in vSphere host synchronization. If you configure command-based health checks in vSphere Integrated Containers Management Portal, the health checks are always successful for containers that are provisioned on affected VCHs, even if the user-specified command does not exist in the scope of the container. This is because command-based health checks are considered to be successful if the exit code of that command is 0.
Download Binaries
- Official VMware vSphere Integrated Containers 1.3.0 release: http://www.vmware.com/go/download-vic
- Open-source Admiral project: an Admiral container image is available on Docker Hub.
Installation
- For instructions about how to deploy the vSphere Integrated Containers appliance, see Deploy the vSphere Integrated Containers Appliance.
- For instructions about how to deploy open-source Admiral, see the Admiral Wiki.
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.
Hotfix 3 for vRA 7.3
Bump up xenon version Testing done: - Run Admiral unit tests - Run Admiral integration tests - Run Container Service integration tests Change-Id: Iafb44a6f73b9060816eb0e7778166332b895e4e5 Reviewed-on: http://bellevue-ci.eng.vmware.com:8080/23621 Bellevue-Verified: e_vcoauto_glob_1 <[email protected]> Closures-Verified: e_vcoauto_glob_1 <[email protected]> Reviewed-by: e_vcoauto_glob_1 <[email protected]> CS-Verified: e_vcoauto_glob_1 <[email protected]> Upgrade-Verified: e_vcoauto_glob_1 <[email protected]>
Hotfix 2 for vRA 7.2
Enable Registry tests Docker Hub search returns different numbers of results, so make the tests handle this. Change-Id: I9dce2af061278d3378132fd9693f9fcf3ac58ce4 Reviewed-on: http://bellevue-ci.eng.vmware.com:8080/13251 Compute-Verified: jenkins <[email protected]> Closures-Verified: jenkins <[email protected]> Bellevue-Verified: jenkins <[email protected]> Reviewed-by: Angel Ivanov <[email protected]> CS-Verified: jenkins <[email protected]> Upgrade-Verified: e_vcoauto_glob_1 <[email protected]> Reviewed-on: http://bellevue-ci.eng.vmware.com:8080/23676 Bellevue-Verified: e_vcoauto_glob_1 <[email protected]> Closures-Verified: e_vcoauto_glob_1 <[email protected]> Reviewed-by: e_vcoauto_glob_1 <[email protected]> CS-Verified: e_vcoauto_glob_1 <[email protected]>
v1.2.2
Docker hub image: https://hub.docker.com/r/vmware/admiral/ v1.2.2
If you are looking for the latest VIC release at the moment, check the release vic_v1.2.1.
New Features
-
Increased the security by default by TLSv1.0. More information here.
-
Increased the security by default by not allowing access to plain HTTP registries. More information here.
Resolved Issues
Various bug fixes and improvements.
Known Issues
No known issues at the time of writing.
Installation
- For instructions about how to deploy open-source Admiral, see the Admiral Wiki.
vic_v1.2.1
Docker hub image: https://hub.docker.com/r/vmware/admiral/ vic_v1.2.1
New Features
This is a patch release that adds no new features.
Resolved Issues
The following issues found in previous versions have been fixed in 1.2.1:
- Fixed issue in the PSC integration module to make the solution user handling tenant aware.
Known Issues
No known issues at the time of writing.
Installation
- For instructions about how to deploy the vSphere Integrated Containers appliance, see Deploy the vSphere Integrated Containers Appliance.
- For instructions about how to deploy open-source Admiral, see the Admiral Wiki.
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.
vic_v1.2.0
Docker hub image: https://hub.docker.com/r/vmware/admiral/ vic_v1.2.0
New Features
- Authentication and authorization, implementing vCenter Single Sign On across components and role-based access control at the project level. Read more
- Full integration of the vSphere Integrated Containers Registry and Management Portal user interfaces. Read more
- Container security with trusted content and scanning for security vulnerabilities, with policies set per project. Read more
Resolved Issues
The following issues found in previous versions have been fixed in 1.2.0:
- VCHs disappear from Admiral UI. #96
If you add more than 10 VCHs to Admiral, after some time some VCHs disappear from the UI. This issue does not occur with fewer than 10 VCHs. If you have approximately 10 to 20 hosts, the issue might appear. The issue always appears if you have more than 50 VCHs. - Time changes in the appliance VM cause vSphere Integrated Containers Management Portal not to function correctly. #77
If, after deploying the vSphere Integrated Containers appliance, the system clock changes while vSphere Integrated Containers Management Portal is starting, all operations fail with the messageOperation already expired, will not queue. - Shared data volumes are not supported. #vic/2303
vSphere Integrated Containers Engine does not support shared data volumes, meaning that multiple containers cannot share a common vSphere volume. As a consequence, using vSphere Integrated Containers Management Portal to provision applications that include containers that share volumes fails when using vSphere Integrated Containers Engine, with the errorServer error from portlayer: Failed to lock the file. Do not design or import such templates in vSphere Integrated Containers Management Portal and do not attempt to deploy applications based on such templates when using vSphere Integrated Containers Engine.
Known Issues
No known issues at the time of writing.
Download Binaries
- Official VMware vSphere Integated Containers 1.2.0 release: http://www.vmware.com/go/download-vic
- Open-source Admiral project: an Admiral container image is available on Docker Hub.
Installation
- For instructions about how to deploy the vSphere Integrated Containers appliance, see Deploy the vSphere Integrated Containers Appliance.
- For instructions about how to deploy open-source Admiral, see the Admiral Wiki.
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.
vra_v7.3_hotfix-1: Remove explicit deletion of query task when results are processed
Hotfix 1 for vRA 7.3
vic_v1.1.1
Docker hub image: https://hub.docker.com/r/vmware/admiral/ vic_v1.1.1
Resolved Issues
The following issues found in Admiral / vSphere Integrated Containers Management Portal1.1.0 have been fixed in 1.1.1:
- Cannot move a placement to a different project. #90
After you create a placement, you cannot move it to a different project, meaning that you cannot assign placements that are created by default when you add a VCH. The value is changed in the dialog, but the change is not applied when you save. - Cannot log in to Management tab in vSphere Integrated Containers UI. #91
After deploying the vSphere Integrated Containers appliance, you can log in to the Registry tab in the vSphere Integrated Containers UI, but you cannot log in to Management tab.
Known Issues
-
VCHs disappear from Admiral UI. #96
If you add more than 10 VCHs to Admiral, after some time some VCHs disappear from the UI. This issue does not occur with fewer than 10 VCHs. If you have approximately 10 to 20 hosts, the issue might appear. The issue always appears if you have more than 50 VCHs. -
Time changes in the appliance VM cause vSphere Integrated Containers Management Portal not to function correctly. #77
If, after deploying the vSphere Integrated Containers appliance, the system clock changes while vSphere Integrated Containers Management Portal is starting, all operations fail with the messageOperation already expired, will not queue.Workaround: Connect to the vSphere Integrated Containers appliance by using SSH, and run
systemctl restart admiral.serviceto restart the management portal service. -
Shared data volumes are not supported. #vic/2303
vSphere Integrated Containers Engine does not support shared data volumes, meaning that multiple containers cannot share a common vSphere volume. As a consequence, using vSphere Integrated Containers Management Portal to provision applications that include containers that share volumes fails when using vSphere Integrated Containers Engine, with the errorServer error from portlayer: Failed to lock the file. Do not design or import such templates in vSphere Integrated Containers Management Portal and do not attempt to deploy applications based on such templates when using vSphere Integrated Containers Engine.
Download Binaries
Open-source Admiral project: TBD
Documentation
- For instructions about how to deploy and use Admiral, see https://github.com/vmware/admiral/wiki.
- If you are using vSphere Integrated Containers Management Portal, see the documentation at https://www.vmware.com/support/pubs/vsphere-integrated-containers-pubs.html.
Open Source Components
The copyright statements and licenses applicable to the open source software components distributed in vSphere Integrated Containers Management Portal are available in the LICENSE file.
vic_v1.1.0
Docker hub image: https://hub.docker.com/r/vmware/admiral/ vic_v1.1.0
Known Issues
-
Time changes in the appliance VM cause vSphere Integrated Containers Management Portal not to function correctly. #77
If, after deploying the vSphere Integrated Containers appliance, the system clock changes while vSphere Integrated Containers Management Portal is starting, all operations fail with the messageOperation already expired, will not queue.Workaround: Connect to the vSphere Integrated Containers appliance by using SSH, and run
systemctl restart admiral.serviceto restart the management portal service. -
Shared data volumes are not supported. #vic/2303
vSphere Integrated Containers Engine does not support shared data volumes, meaning that multiple containers cannot share a common vSphere volume. As a consequence, using vSphere Integrated Containers Management Portal to provision applications that include containers that share volumes fails when using vSphere Integrated Containers Engine, with the errorServer error from portlayer: Failed to lock the file. Do not design or import such templates in vSphere Integrated Containers Management Portal and do not attempt to deploy applications based on such templates when using vSphere Integrated Containers Engine.
v0.9.2 release
Docker hub image: https://hub.docker.com/r/vmware/admiral/ 0.9.2
Binaries: https://bintray.com/vmware/admiral/admiral/0.9.2
CLI binaries: https://bintray.com/vmware/admiral/admiral-cli/0.9.1
Changelog:
- Various bug fixes related to document and service replication consistency in an SSL enabled cluster environment. Minor UI bug fixes.