1.22.0 release updates

howto/update/upgrade-anbox.md

@@ -56,13 +56,7 @@ The deployed Juju charms need to be upgraded next.
 
 [note type="information" status="Note"]
 
-- You can find a list of all charm, snap and Debian package versions for each Anbox Cloud release in the [component versions](https://discourse.ubuntu.com/t/component-versions/21413) overview. This also includes the charm and bundle revisions and channels for each release.
-
-- Starting with the 1.14 release, all charms come from [Charmhub](https://charmhub.io) and use the concept of [channels](https://snapcraft.io/docs/channels) to track particular versions. The instructions below address how to upgrade from a 1.13.x release, where charms were still from the old Juju charm store. The `--channel=1.21/stable` argument instructs Juju to switch to the latest [Charmhub](https://charmhub.io) version of the charm and track the right channel.
-
-- With the 1.14 release, the name of the `lxd` charm changed to `ams-lxd`. If you run a deployment older than 1.14 and want to upgrade, add `--switch=ams-lxd` to the upgrade command to make Juju switch to the new charm. The charm itself remains identical with the same functionality and features.
-
-- Starting with the 1.15 release, Anbox Management Service (AMS) enforces TLS 1.3 on its HTTPS endpoint. Images older than 1.15.0 will fail to reach AMS in this case. To still allow older images to work with AMS, you can temporarily enable TLS 1.2 support again in AMS by setting the `force_tls12` [configuration option of the AMS charm](https://charmhub.io/ams/configure?channel=1.15/stable#force_tls12).
+- You can find a list of all charm, snap, bundle and Debian package versions for each Anbox Cloud release in the [component versions](https://discourse.ubuntu.com/t/component-versions/21413) overview. This also includes the charm and bundle revisions and channels for each release.
 
 - If you want to deploy a particular revision of a charm, you can do so by adding `--revision=<rev>` to the `juju upgrade-charm` command.
 
@@ -95,7 +89,7 @@ The Anbox Application Registry (AAR) can be updated independently of the other s
 
 To upgrade the registry, run
 
-    juju refresh --channel=1.21/stable aar
+    juju refresh --channel=1.22/stable aar
 
 ### Upgrade control plane
 
@@ -124,19 +118,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.21/stable ams
+    juju refresh --channel=1.22/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.21/stable ams-node-controller
+    juju refresh --channel=1.22/stable ams-node-controller
 
 Once the upgrade is completed, you can continue upgrading LXD:
 
-    juju refresh --channel=1.21/stable lxd
+    juju refresh --channel=1.22/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:
 

index.md

@@ -159,6 +159,7 @@ Thinking about using Anbox Cloud for your next project? [Get in touch!](https://
 | 2 | reference/webrtc-streamer | [WebRTC streamer](https://discourse.ubuntu.com/t/webrtc-streamer/30195)|
 | 2 | reference/prometheus | [Prometheus metrics](https://discourse.ubuntu.com/t/prometheus-metrics/19521)|
 | 2 | reference/perf-benchmarks | [Performance benchmarks](https://discourse.ubuntu.com/t/performance-benchmarks/24709)|
+| 2 | reference/deprecation-notices | [Deprecations](tbd)|
 | 2 | reference/license-information | [License information](https://discourse.ubuntu.com/t/license-information/36649) |
 | 2 | reference/glossary | [Glossary](https://discourse.ubuntu.com/t/glossary/26204)|
 | 0 | | |

reference/component-versions.md

@@ -2,6 +2,70 @@ 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, this is called out in the [release notes](https://discourse.ubuntu.com/t/release-notes/17842) and components are marked with `n/a` below.
 
+## 1.22.0
+
+### Charms
+
+#### Ubuntu 22.04
+
+| Name | Channel | Revision |
+|----------|--------------|--------------|
+| `anbox-cloud-dashboard` | `1.22/stable` | 417 |
+| `ams-node-controller` | `1.22/stable` | 425 |
+| `coturn` | `1.22/stable` | 419 |
+| `ams` | `1.22/stable` | 449 |
+| `aar` | `1.22/stable` | 426 |
+| `anbox-stream-gateway` | `1.22/stable` | 435 |
+| `ams-lxd` | `1.22/stable` | 422 |
+| `anbox-stream-agent` | `1.22/stable` | 430 |
+| `nats ` | `latest/stable` | 11 |
+
+#### Ubuntu 20.04 (Deprecated)
+
+| Name | Channel | Revision |
+|----------|--------------|--------------|
+| `anbox-cloud-dashboard` | `1.22/stable` | 416 |
+| `ams-node-controller` | `1.22/stable` | 424 |
+| `coturn` | `1.22/stable` | 418 |
+| `ams` | `1.22/stable` | 448 |
+| `aar` | `1.22/stable` | 425 |
+| `anbox-stream-gateway` | `1.22/stable` | 434 |
+| `ams-lxd` | `1.22/stable` | 421 |
+| `anbox-stream-agent` | `1.22/stable` | 429 |
+| `nats ` | `latest/stable` | 11 |
+
+### Bundles
+
+| Name | Channel | Revision |
+|----------|--------------|--------------|
+| `anbox-cloud` | `1.22/stable` | 234 |
+| `anbox-cloud-core` | `1.22/stable` | 242 |
+
+### Snaps
+
+| Name |  Channel | Version |
+|----------|--------------|---------|
+| `ams`    | `1.22/stable` | 1.22.0 |
+| `aar`    | `1.22/stable` | 1.22.0 |
+| `ams-node-controller` | `1.22/stable` | 1.22.0 |
+| `anbox-cloud-dashboard` | `1.22/stable` | 1.22.0 |
+| `anbox-stream-agent` | `1.22/stable` | 1.22.0 |
+| `anbox-stream-gateway` | `1.22/stable` | 1.22.0 |
+| `anbox-cloud-appliance` | `1.22/stable` | 1.22.0 |
+
+
+### Anbox images
+
+| Name | Version |
+|----------|--------------|
+| `jammy:android13:amd64` | 1.22.0 |
+| `jammy:android13:arm64` | 1.22.0 |
+| `jammy:android12:amd64` | 1.22.0 |
+| `jammy:android12:arm64` | 1.22.0 |
+| `jammy:aaos13:amd64` (Experimental)    | 1.22.0 |
+| `jammy:aaos13:arm64` (Experimental)   | 1.22.0 |
+
+
 ## 1.21.2
 
 ### Charms

reference/deprecation-notices.md

@@ -0,0 +1,12 @@
+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.
+
+## 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.
+
+## Anbox Cloud Appliance gets new implementation
+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.

reference/release-notes/release-notes.md

@@ -7,28 +7,28 @@ The following dates for upcoming releases are not final and could vary depending
 
 | Tentative Release date | Planned release version |
 |----|----|
-| May 15 2024 | Anbox Cloud 1.22.0 |
 | June 13 2024 | Anbox Cloud 1.22.1 |
 | July 17 2024 | Anbox Cloud 1.22.2 |
+| August 14 2024 | Anbox Cloud 1.23.0 |
 
 ## Recent releases
 
 | Release date   |  Release notes  |
 |----|----|
-| April 18 2024 | [Anbox Cloud 1.21.2](https://discourse.ubuntu.com/t/44276) |
-| March 13 2024 | [Anbox Cloud 1.21.1](https://discourse.ubuntu.com/t/43279) |
-| February 14 2024 | [Anbox Cloud 1.21.0](https://discourse.ubuntu.com/t/42429) |
+| May 15 2024 | [Anbox Cloud 1.22.0](tbd) |
 
-### What's new in 1.21.x?
+### What's new in 1.22.x?
 
-Along with bug fixes and general improvements, Anbox Cloud 1.21.x includes:
+Along with bug fixes and general improvements, Anbox Cloud 1.22.x includes:
 
-* Android Automotive OS (AAOS) images
-* Alpha support for Vehicle Hardware Abstraction Layer (VHAL)
-* Full support for Vulkan on NVIDIA GPUs
-* Experimental video upscaling on the client side
-* System tracing for Android
-* Improvements to Anbox Management Service (AMS) API responses
+* 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
 * Dashboard improvements
 * Android security updates
 
@@ -39,6 +39,9 @@ Along with bug fixes and general improvements, Anbox Cloud 1.21.x includes:
 |  Release date  |  Release notes  |
 |----|----|
 | January 17 2024 | [Anbox Cloud 1.20.2](https://discourse.ubuntu.com/t/41686) |
+| February 14 2024 | [Anbox Cloud 1.21.0](https://discourse.ubuntu.com/t/42429) |
+| March 13 2024 | [Anbox Cloud 1.21.1](https://discourse.ubuntu.com/t/43279) |
+| April 18 2024 | [Anbox Cloud 1.21.2](https://discourse.ubuntu.com/t/44276) |
 
 ## 2023
 |  Release date  |  Release notes  |

reference/roadmap.md

@@ -12,6 +12,6 @@ Anbox Cloud follows a defined release cycle with frequent minor and patch releas
 
 | Release | Target Date | What to expect| 
 |---------|-------------|---------------|
-| 1.22.0 | May 15 2024 | * Support for custom Android system images<br/> * Support for 64 bit only ARM/x86 systems<br/>* Stability improvements for AAOS images and VHAL<br/>* VirGL enabled by default for NVIDIA GPUs<br/>* Update to NVIDIA 550 driver series<br/>* Android security updates for May 2024<br/> * Bug fixes |
 | 1.22.1 | June 13 2024 | * Android security updates for June 2024<br/> * Bug fixes |
 | 1.22.2 | July 18 2024 | * Android security updates for July 2024<br/> * Bug fixes |
+| 1.23.0 | August 14 2024 | * AAOS enhancements<br/> * Support for multiple subclusters in the web dashboard<br/> * Android security updates for August 2024<br/> * Bug fixes|

reference/sdks.md

@@ -71,6 +71,7 @@ Having these two components makes it easier to plug your own software in the SDK
 | Send commands to the Android container           |        ✓       |
 | Game pad support                                 |        ✓       |
 | Camera support                                   |        ✓       |
+| Pointer lock (Experimental)                                     |        ✓       |
 | Sensor support                                   |                 |
 | Location support                                 |        ✓       |
 | Supported platforms                              |       All       |