[magnum] Transition Ussuri to EM

This transition the ussuri branch to extended maintenance.
Changes for bugfixes and things the team deems important are
still encouraged, but there will no longer be official releases
off of the branch.

Please +1 if the team is ready for us to proceed with this
transition, or -1 if there are any final backports currently in
flight that we should wait for. For the latter case, please
update the patch with the new commit hash after doing a final
release to get those changes out so we know to proceed with the
transition.

Change-Id: I09197f6dd4c8a7e0f41fbaf7d6c9f7a6e39b2726

deliverables/ussuri/magnum-ui.yaml

@@ -14,6 +14,10 @@ releases:
     projects:
       - repo: openstack/magnum-ui
         hash: 4a561a93742d3c9cfa5c243601e89515cfd7d155
+  - version: ussuri-em
+    projects:
+      - repo: openstack/magnum-ui
+        hash: 4a561a93742d3c9cfa5c243601e89515cfd7d155
 branches:
   - name: stable/ussuri
     location: 6.0.0

deliverables/ussuri/magnum.yaml

@@ -6,22 +6,23 @@ type: service
 repository-settings:
   openstack/magnum: {}
 cycle-highlights:
-  - Support Helm v3 to install all magnum installed charts. Support for Helm v2
-    client will be removed in X release.
+  - Support Helm v3 to install all magnum installed charts. Support
+    for Helm v2 client will be removed in X release.
   - A new config option ``post_install_manifest_url`` is added to support
-    installing cloud provider/vendor specific manifest after deploying a
-    kuberbetes cluster.
-  - A new ``--merge-labels`` boolean flag can be used to merge user labels at
-    cluster/nodegroup scope with cluster template/cluster labels.
-  - Cloud admin users now can do rolling upgrade on behalf of end users to do
-    urgent security patching.
-  - Magnum now cascade deletes all the load balancers before deleting the
-    cluster, not only including load balancers for the cluster services and
-    ingresses, but also those for Kubernetes API/etcd endpoints.
+    installing cloud provider/vendor specific manifest after deploying
+    a kuberbetes cluster.
+  - A new ``--merge-labels`` boolean flag can be used to merge user
+    labels at cluster/nodegroup scope with cluster template/cluster
+    labels.
+  - Cloud admin users now can do rolling upgrade on behalf of end users
+    to do urgent security patching.
+  - Magnum now cascade deletes all the load balancers before deleting
+    the cluster, not only including load balancers for the cluster services
+    and ingresses, but also those for Kubernetes API/etcd endpoints.
   - Magnum supports updating the k8s cluster health status via the Magnum
-    cluster update API so that a controller (e.g. magnum-auto-healer) running
-    inside the k8s cluster can call the Magnum update API to update the cluster
-    health status.
+    cluster update API so that a controller (e.g. magnum-auto-healer)
+    running inside the k8s cluster can call the Magnum update API to
+    update the cluster health status.
 releases:
   - version: 10.0.0.0rc1
     projects:
@@ -40,6 +41,10 @@ releases:
     projects:
       - repo: openstack/magnum
         hash: 9c9a84f6690d11356212070b4c5221c8c3e7777d
+  - version: ussuri-em
+    projects:
+      - repo: openstack/magnum
+        hash: 9c9a84f6690d11356212070b4c5221c8c3e7777d
 branches:
   - name: stable/ussuri
     location: 10.0.0.0rc1

deliverables/ussuri/python-magnumclient.yaml

@@ -19,6 +19,10 @@ releases:
     projects:
       - repo: openstack/python-magnumclient
         hash: 6d1a386e401095c169b069ac7d30930038159de3
+  - version: ussuri-em
+    projects:
+      - repo: openstack/python-magnumclient
+        hash: 6d1a386e401095c169b069ac7d30930038159de3
 branches:
   - name: stable/ussuri
     location: 3.0.0