1.23.0 release notes and updates

- Create 1.23.0 release notes and link it in necessary topics - Update deprecation notices - Update release roadmap - Update component versions - Update upgrade process with correct versions - Update release notes landing page with new features
canonical · Aug 6, 2024 · 40ffb67 · 40ffb67
1 parent 4f06ffa
commit 40ffb67
Show file tree

Hide file tree

Showing 7 changed files with 177 additions and 31 deletions.
diff --git a/.custom_wordlist.txt b/.custom_wordlist.txt
@@ -124,6 +124,7 @@ HW
 HWE
 HVAC
 IAM
+IBT
 idmapped
 IDR
 IME
@@ -157,6 +158,7 @@ Livepatch
 LLVMpipe
 LMA
 localhost
+logcat
 LTS
 LXC
 LXD
@@ -328,6 +330,7 @@ Uber
 upscaling
 FSR
 FidelityFX
+ubuntu
 uSampler
 vTextureCoord
 vec

diff --git a/howto/update/upgrade-anbox.md b/howto/update/upgrade-anbox.md
@@ -106,10 +106,10 @@ If you don't run any of the services in a high availability configuration, upgra
 
 To upgrade all charms, run the following commands:
 
-    juju refresh --channel=1.22/stable anbox-cloud-dashboard
-    juju refresh --channel=1.22/stable anbox-stream-gateway
-    juju refresh --channel=1.22/stable anbox-stream-agent
-    juju refresh --channel=1.22/stable coturn
+    juju refresh --channel=1.23/stable anbox-cloud-dashboard
+    juju refresh --channel=1.23/stable anbox-stream-gateway
+    juju refresh --channel=1.23/stable anbox-stream-agent
+    juju refresh --channel=1.23/stable coturn
     juju refresh --channel=latest/stable nats
 
 ```{note}
@@ -122,19 +122,19 @@ Since the NATS charm has been overhauled to use the modern charm framework (Ops
 
 The AMS service needs to be updated independently of the other service components to ensure minimal down time. The charm can be upgraded by running the following command.
 
-    juju refresh --channel=1.22/stable ams
+    juju refresh --channel=1.23/stable ams
 
 ### Upgrade LXD
 
 As the last step, you have to upgrade the LXD cluster. Upgrading LXD will not restart running instances but it's recommended to take a backup before continuing.
 
 As the first step, you need to upgrade the AMS node controller by running:
 
-    juju refresh --channel=1.22/stable ams-node-controller
+    juju refresh --channel=1.23/stable ams-node-controller
 
 Once the upgrade is completed, you can continue upgrading LXD:
 
-    juju refresh --channel=1.22/stable lxd
+    juju refresh --channel=1.23/stable lxd
 
 In some cases, specifically when you maintain bigger LXD clusters or want to keep a specific set of LXD nodes active until users have dropped, it makes sense to run the upgrade process manually on a per node basis. To enable this, you can set the following configuration option for the LXD charm before running the refresh command above:
 

diff --git a/reference/component-versions.md b/reference/component-versions.md
@@ -5,6 +5,67 @@ This documents the versions of the different components for each Anbox Cloud rel
 
 Not all components are updated with each release. When components are not updated, they are marked with `n/a` below.
 
+## 1.23.0
+
+### Charms
+
+#### Ubuntu 22.04
+
+| Name | Channel | Revision |
+|----------|--------------|--------------|
+| `anbox-cloud-dashboard` | `1.23/stable` | ? |
+| `ams-node-controller` | `1.23/stable` | ? |
+| `coturn` | `1.23/stable` | ? |
+| `ams` | `1.23/stable` | ? |
+| `aar` | `1.23/stable` | ? |
+| `anbox-stream-gateway` | `1.23/stable` | ? |
+| `ams-lxd` | `1.23/stable` | ? |
+| `anbox-stream-agent` | `1.23/stable` | ? |
+| `nats ` | `latest/stable` | 11 |
+
+#### Ubuntu 20.04 (Deprecated)
+
+| Name | Channel | Revision |
+|----------|--------------|--------------|
+| `anbox-cloud-dashboard` | `1.23/stable` | ? |
+| `ams-node-controller` | `1.23/stable` | ? |
+| `coturn` | `1.23/stable` | ? |
+| `ams` | `1.23/stable` | ? |
+| `aar` | `1.23/stable` | ? |
+| `anbox-stream-gateway` | `1.23/stable` | ? |
+| `ams-lxd` | `1.23/stable` | ? |
+| `anbox-stream-agent` | `1.23/stable` | ? |
+| `nats ` | `latest/stable` | 11 |
+
+### Bundles
+
+| Name | Channel | Revision |
+|----------|--------------|--------------|
+| `anbox-cloud` | `1.23/stable` | ? |
+| `anbox-cloud-core` | `1.23/stable` | ? |
+
+### Snaps
+
+| Name |  Channel | Version |
+|----------|--------------|---------|
+| `ams`    | `1.23/stable` | 1.23.0 |
+| `aar`    | `1.23/stable` | 1.23.0 |
+| `ams-node-controller` | `1.23/stable` | 1.23.0 |
+| `anbox-cloud-dashboard` | `1.23/stable` | 1.23.0 |
+| `anbox-stream-agent` | `1.23/stable` | 1.23.0 |
+| `anbox-stream-gateway` | `1.23/stable` | 1.23.0 |
+
+### Anbox images
+
+| Name | Version |
+|----------|--------------|
+| `jammy:android13:amd64` | 1.23.0 |
+| `jammy:android13:arm64` | 1.23.0 |
+| `jammy:android12:amd64` | 1.23.0 |
+| `jammy:android12:arm64` | 1.23.0 |
+| `jammy:aaos13:amd64`    | 1.23.0 |
+| `jammy:aaos13:arm64`    | 1.23.0 |
+
 ## 1.22.2
 
 ### Charms
@@ -19,12 +80,13 @@ N/A
 
 | Name |  Channel | Version |
 |----------|--------------|---------|
-| `ams`    | `1.22/stable` | 1.22.2 |
-| `aar`    | `1.22/stable` | 1.22.2 |
-| `ams-node-controller` | `1.22/stable` | 1.22.2 |
-| `anbox-cloud-dashboard` | `1.22/stable` | 1.22.2 |
-| `anbox-stream-agent` | `1.22/stable` | 1.22.2 |
-| `anbox-stream-gateway` | `1.22/stable` | 1.22.2 |
+| `ams`    | `1.23/stable` | 1.23.0 |
+| `aar`    | `1.23/stable` | 1.23.0 |
+| `ams-node-controller` | `1.23/stable` | 1.23.0 |
+| `anbox-cloud-dashboard` | `1.23/stable` | 1.23.0 |
+| `anbox-stream-agent` | `1.23/stable` | 1.23.0 |
+| `anbox-stream-gateway` | `1.23/stable` | 1.23.0 |
+| `anbox-cloud-appliance` | `1.23/stable` | 1.23.0 |
 
 
 ### Anbox images

diff --git a/reference/deprecation-notices.md b/reference/deprecation-notices.md
@@ -2,16 +2,25 @@
 
 This document contains a list of deprecation notices for Anbox Cloud and its components.
 
-## Ubuntu 20.04 (focal)
-
-Support for Ubuntu 20.04 (focal) is deprecated in 1.22.0 and is planned to be removed in Anbox Cloud 1.24.0.
+## Node controller
+*Deprecated in 1.23.0* ; *Removal in 1.24.0*
 
-## EmuGL
-
-Support for the EmuGL renderer is deprecated in 1.22.0 and planned to be removed in Anbox Cloud 1.23.0. Starting with 1.22.0, VirGL will be the default renderer for NVIDIA GPUs with driver version 545 and later.
+Use of node controller to manage the port forwarding from an instance to expose a service is deprecated in 1.23.0. Instead, the Anbox Management Service (AMS) will use a LXD proxy device to manage the port forwarding.
 
+(sec-appliance-deprecation)=
 ## Anbox Cloud Appliance
+*Deprecated in 1.22.0* ; *Removal in 1.24.2*
 
 The Anbox Cloud Appliance is being reworked and the current implementation is deprecated in 1.22.0. Existing installations of the current implementation will receive updates until Anbox Cloud 1.24.2. Starting from 1.23.0, new installations will receive the new implementation of the appliance.
 
   The new implementation of the appliance will no longer use the Juju charmed operators internally but package all necessary service components directly within the snap. This helps to simplify the installation process and reduce overall footprint.
+
+## Ubuntu 20.04 (focal)
+*Deprecated in 1.22.0* ; *Removal in 1.24.0*
+
+Support for Ubuntu 20.04 (focal) is deprecated in 1.22.0 and is planned to be removed in Anbox Cloud 1.24.0.
+
+## EmuGL
+*Deprecated in 1.22.0* ; *Removal in 1.23.0*
+
+Support for the EmuGL renderer is deprecated in 1.22.0 and planned to be removed in Anbox Cloud 1.23.0. Starting with 1.22.0, VirGL will be the default renderer for NVIDIA GPUs with driver version 545 and later.
diff --git a/reference/release-notes/1.23.0.md b/reference/release-notes/1.23.0.md
@@ -0,0 +1,76 @@
+---
+orphan: true
+---
+# 1.23.0
+
+The Anbox Cloud team is pleased to announce the release of Anbox Cloud 1.23.0.
+
+Please see [component versions](https://anbox-cloud.io/docs/reference/component-versions) for a list of updated components.
+
+## New features & improvements
+
+### Core stack improvements
+
+* The Anbox Cloud Appliance is overhauled to deliver a much simpler and streamlined version. This new version of the appliance is made available using the [snap epoch feature](https://snapcraft.io/docs/snap-epochs). Existing installations of the appliance are not affected but the old snap with `epoch=0` is {ref}`deprecated <sec-appliance-deprecation>`. For all new installations of the appliance, use the `epoch=1` snap. See the [appliance installation tutorial](https://documentation.ubuntu.com/anbox-cloud/en/latest/tutorial/installing-appliance/) for instructions.
+    * The `anbox-cloud-appliance` status command now displays the initialisation status of the appliance and its version. <!--AC-2513-->
+
+* Anbox Cloud now offers a way to connect to remote Android instances securely using the Android Debug Bridge (ADB). You can set up an ADB connection using the dashboard or the CLI. See {ref}`howto-access-instance` for more information.
+
+* Android Automotive OS based images are full supported starting from this release and no longer considered an experimental feature.<!--AC-2660-->
+
+### Streaming improvements
+
+< List enhancements to streaming stack here. >
+
+### Dashboard improvements
+
+The Anbox Cloud dashboard has the following improvements:
+
+* The *Instances* and the *Sessions* pages and their functionalities are merged to provide an enhanced user experience while streaming.
+
+* The initial VHAL values upon joining a stream are now captured as a default. You can revert to these values using the *Reset* button, when needed.
+
+### Other
+
+* All Anbox Cloud charms now install Snaps directly from the Snap Store instead of using deb packages. Existing installations automatically switch to snap refresh from the store on upgrade.<!--AC-2523-->
+* Android security updates for August 2024 (see [Android Security Bulletin - August 2024](https://source.android.com/docs/security/bulletin/2024-08-01) for more information).
+* The Android WebView has been updated to [127.0.6533.84](https://chromereleases.googleblog.com/2024/07/chrome-for-android-update_30.html).
+* Our documentation is now hosted at [documentation.ubuntu.com](https://documentation.ubuntu.com/anbox-cloud/en/latest). Previous documentation links from the [earlier website](https://anbox-cloud.io) will be redirected to new targets.
+
+    The documentation source is hosted at the public [Anbox Cloud documentation repository on GitHub](https://github.com/canonical/anbox-cloud-docs). We welcome all contributions to the Anbox Cloud documentation using this repository. See [Contribute to Anbox Cloud documentation](https://documentation.ubuntu.com/anbox-cloud/en/latest/contribute/landing/) for more information.
+
+## Removed functionality
+
+< List features that were part of Anbox Cloud so far or that were on the deprecation path for a while and have been removed for the current release >
+
+## Deprecations
+
+* Use of a node controller to manage port forwarding from an instance is deprecated, starting with this release. In 1.23.0, the node controller will still be used for the full Anbox Cloud deployment. For the appliance, the Anbox Management Service (AMS) now uses a LXD proxy device to manage the port forwarding from an instance to expose a service externally or internally.
+
+  In the 1.24.0 release, the node controller will be fully replaced with LXD proxy device for both regular and appliance deployments.<!--AC--2487-->
+
+## Known issues
+
+* WiFi support is not available with Android 14 vendor images. This issue will be fixed in the 1.23.1 release. <!--AC-2647-->
+
+## Bug fixes
+- [LP 2058004](https://bugs.launchpad.net/anbox-cloud/+bug/2058004) Deploying Anbox Cloud dashboard fails when using AMI that has a Ubuntu Pro subscription.
+- [LP 2065281](https://bugs.launchpad.net/anbox-cloud/+bug/2065281) Android 13 unable to use Vulkan 1.3 despite Vulkan 1.3 being supported.
+- [LP 2067314](https://bugs.launchpad.net/anbox-cloud/+bug/2067314) Current `amc shell` is a plain bash shell and will not source any common profile scripts.
+- [LP 2067316](https://bugs.launchpad.net/anbox-cloud/+bug/2067316) The `pprof` endpoint exposed by AMS for profiling heap allocations does not expose `allocs` handler.
+- [LP 2072955](https://bugs.launchpad.net/anbox-cloud/+bug/2072955) Unable to add an image on Anbox Cloud Appliance.
+- [LP 2067252](https://bugs.launchpad.net/anbox-cloud/+bug/2067252) Incorrect  `Error: api extension "zip_archive_support" not supported` error while creating an application.
+- [LP 2069021](https://bugs.launchpad.net/anbox-cloud/+bug/2069021) Updating the AMS SDK to 1.21.0 prevents building the AMS client.
+- [LP 2070252](https://bugs.launchpad.net/anbox-cloud/+bug/2070252) When running the Marvel Battle application, the following logs flooded the Anbox logcat:
+    ```
+    06-13 12:12:16.403 3221 3221 D SensorMonitor: Temperature Sensor value changed
+    06-13 12:12:16.408 3221 3221 D SensorMonitor: Temperature Sensor value changed
+    06-13 12:12:16.413 3221 3221 D SensorMonitor: Temperature Sensor value  changed
+    ```
+- [LP 2072367](https://bugs.launchpad.net/anbox-cloud/+bug/2072367) When initialising the Anbox Cloud Appliance, if you provide an empty public address, invalid STUN/TURN server details are generated.
+- [LP 2075494](https://bugs.launchpad.net/anbox-cloud/+bug/2075494) The streaming screen does not rotate when using client side upscaling.
+- [LP 2071903](https://bugs.launchpad.net/anbox-cloud/+bug/2071903) Stream gateway swagger API is missing `/1.0/sessions POST` documentation.
+
+## Upgrade instructions
+
+See [Upgrade Anbox Cloud](https://anbox-cloud.io/docs/howto/update/upgrade-anbox) or [Upgrade the Anbox Cloud Appliance](https://anbox-cloud.io/docs/howto/update/upgrade-appliance) for instructions on how to update your Anbox Cloud deployment to the 1.23.0 release.
diff --git a/reference/release-notes/release-notes.md b/reference/release-notes/release-notes.md
@@ -10,31 +10,27 @@ The following dates for upcoming releases are not final and could vary depending
 
 | Tentative Release date | Planned release version |
 |----|----|
-| August 14 2024 | Anbox Cloud 1.23.0 |
 | September 18 2024 | Anbox Cloud 1.23.1 |
 | October 16 2024 | Anbox Cloud 1.23.2 |
+| November 14 2024 | Anbox Cloud 1.24.0 |
 
 ## Recent releases
 
 | Release date   |  Release notes  |
 |----|----|
-| July 18 2024 | [Anbox Cloud 1.22.2](https://discourse.ubuntu.com/t/46495) |
+| August 14 2024 | [Anbox Cloud 1.23.0](1.23.0.md) |
+| July 18 2024 | [Anbox Cloud 1.22.2](1.22.2.md) |
 | June 13 2024 | [Anbox Cloud 1.22.1](1.22.1.md) |
 | May 15 2024 | [Anbox Cloud 1.22.0](1.22.0.md) |
 
-### What's new in 1.22.x?
+### What's new in 1.23.x?
 
 Along with bug fixes and general improvements, Anbox Cloud 1.22.x includes:
 
-* Support for 64-bit only systems
-* Support for custom images
-* Support for Vulkan 1.3 for Android 13 images
-* VirGL as the default renderer
-* Stream-enabled instance creation
-* Upgrade to NVIDIA 550 driver series
-* Support for pointer lock
-* VHAL enhancements
+* Improved Anbox Cloud Appliance
+* Seamless ADB connections to remote Android instances
 * Dashboard improvements
+* Improved documentation delivery
 * Android security updates
 
 ## Older releases

diff --git a/reference/roadmap.md b/reference/roadmap.md
@@ -15,6 +15,6 @@ Anbox Cloud follows a defined release cycle with frequent minor and patch releas
 
 | Release | Target Date | What to expect| 
 |---------|-------------|---------------|
-| 1.23.0 | August 14 2024 | * Improvements to VHAL support<br/> *Overhaul of Anbox Cloud Appliance snap<br/>  * AAOS enhancements<br/> * Support for multiple subclusters in the web dashboard<br/> * Android security updates for August 2024<br/> * Bug fixes|
 | 1.23.1 | September 18 2024 | * Android security updates for September 2024<br/> * Bug fixes |
 | 1.23.2 | October 16 2024 | * Android security updates for October 2024<br/> * Bug fixes |
+| 1.24.0 | November 13 2024 | * VHAL improvements<br/> *Support for Bluetooth in AAOS<br/> * Support for generic application streaming<br/> * Vibration support with the streaming SDK<br/> * IBT integration<br/> * Android security updates for November 2024<br/> * Bug fixes