From e48fb0c8057735b345f60e3b37a5f7c8ee8099da Mon Sep 17 00:00:00 2001 From: Joao Fernandes Date: Wed, 25 Jan 2017 18:01:16 -0800 Subject: [PATCH] Add release notes for ucp 2.0.2 beta 2 --- datacenter/ucp/2.1/guides/release-notes.md | 77 ++++++++++++++++++++-- 1 file changed, 73 insertions(+), 4 deletions(-) diff --git a/datacenter/ucp/2.1/guides/release-notes.md b/datacenter/ucp/2.1/guides/release-notes.md index 51ca69f8d9..17bb88ddf6 100644 --- a/datacenter/ucp/2.1/guides/release-notes.md +++ b/datacenter/ucp/2.1/guides/release-notes.md @@ -10,6 +10,75 @@ known issues for the latest UCP version. You can then use [the upgrade instructions](install/upgrade.md), to upgrade your installation to the latest release. +## Version 2.1.0 beta 2 + +(25 Jan 2017) + +This version of UCP extends the functionality provided by Docker Engine 1.13. +Before installing or upgrading this version, you need to install Docker Engine 1.13 +in the nodes that you plan to manage with UCP. + +**New features** + +* Core + * You can now deploy secrets using Compose for Services + +* UI/UX + * You can now view and manage Stacks (Compose v3 applications consisting of + services, volumes, and networks) directly from the UI + * The HTTP Routing Mesh settings page now contains a table of all services + using HRM, with details on parameters and health status + * Admins can now view team membership in a user's details screen + * You can now customize session timeouts length in Authentication config screen + * Can now mount `tmpfs` or existing local volumes to a service via the UI + * Added numerous tooltips throughout the UI + +**Bug fixes** + +* Core + * Promoting a worker to a manager no longer requires manually pulling + down `ucp-metrics` image on the node (fixes known beta1 issue) + * Fixed an error in which `_ping` calls were causing multiple TCP connections + to open up on the cluster + * Fixed an issue in which UCP install occasionally failed with the error + "failed to change temp password" + * Defining multiple HRM networks with overlapping subnets now correctly causes + the HTTP Routing Mesh `ucp-hrm` service to fail. + * Fixed an issue where multiple rapid updates of HTTP Routing Mesh configuration + would not register correctly + * With HTTP Routing Mesh, using the "default" backend option with an empty + external route now works correctly + * Volumes label-based access control now correctly supports volumes created + via the `mount` format flag + +* UI/UX + * Installing DTR no longer fails when "Enable scheduling on UCP controllers and + DTR nodes" is unchecked. + * HTTP Routing Mesh configuration status messages are now temporary and no + longer overlap with text on a service's details screen. + * Publishing a port to both TCP and UDP in a service via UI now works correctly + * Removed Internal Scheme option when publishing a hostname route + * Nodes now stay sorted after clicking a parameter to sort by in the Nodes screen + * Metrics on the Nodes screen no longer incorrectly show `-` instead of 0% or 100% + * In service deploy/edit screens, secrets have been moved to Environments tab + +**Known issues** + +When deploying compose files that use secrets, you need to specify all the parameters +for the service like: + +```none +secrets: + - source: "foo" + target: "foo" + uid: "0" + gid: "0" + mode: 0400 +``` + +UCP returns an error if you only use the name of the secret. + + ## Version 2.1.0 beta 1 (10 Jan 2017) @@ -55,10 +124,10 @@ Docker Engine 1.13 in the nodes that you plan to manage with UCP. **Known Issues** -* Promoting a worker to manager causes the promotion process to hang or take a -very long time, because the node will not pull the `ucp-metrics` image correctly. -The workaround is to use `docker pull docker/ucp-metrics:2.1.0-beta1` on all -nodes that you plan to promote to manager. +* Promoting a worker to manager causes the promotion process to hang or take a +very long time, because the node will not pull the `ucp-metrics` image correctly. +The workaround is to use `docker pull docker/ucp-metrics:2.1.0-beta1` on all +nodes that you plan to promote to manager. * Dashboard metrics may show inaccurately high usage values when using an AWS template based deployment