Would we follow the procedure detailed here and send an email to cloud-announce?

It seems we could do this at any time but I'm not fully aware if we have some Cloud VPS users that are depending heavily on Jessie at this moment. In any case, the fallout might be more tasks to re-enable it temporarily so someone can create a Jessie VM.

Announced here:

https://lists.wikimedia.org/pipermail/cloud-announce/2019-March/000145.html

The Integration project will need to keep creating Jessie VMs for a bit.

In T218119#5034071, @Andrew wrote:

This image is now private to the 'admin' project, with shared access extended to the 'integration' and 'testlabs' projects.
Adding access to a project looks like this:

root@cloudcontrol1003:~# source ~/novaenv.sh 
root@cloudcontrol1003:~# glance member-create 957af495-1244-4b05-9f4f-cf68dccb1422 testlabs
+--------------------------------------+-----------+---------+
| Image ID                             | Member ID | Status  |
+--------------------------------------+-----------+---------+
| 957af495-1244-4b05-9f4f-cf68dccb1422 | testlabs  | pending |
+--------------------------------------+-----------+---------+
root@cloudcontrol1003:~# glance member-update 957af495-1244-4b05-9f4f-cf68dccb1422 testlabs accepted
+--------------------------------------+-----------+----------+
| Image ID                             | Member ID | Status   |
+--------------------------------------+-----------+----------+
| 957af495-1244-4b05-9f4f-cf68dccb1422 | testlabs  | accepted |
+--------------------------------------+-----------+----------+

Cool, could you please document this somewhere? perhaps https://wikitech.wikimedia.org/wiki/Portal:Cloud_VPS/Admin/VM_images

https://wikitech.wikimedia.org/wiki/Portal:Cloud_VPS/Admin/VM_images#Private_Images

I just enabled Jessie in 'security-tools' so they can test existing Jessie deployments