We want to keep it around as an option but by request only.
Description
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Open | None | T197804 Puppet: forbid new Python2 code | |||
Open | None | T218426 Upgrade various Cloud VPS Python 2 scripts to Python 3 | |||
Resolved | BUG REPORT | Bstorm | T218423 Add python 3 packages to openstack::clientpackages::common | ||
Open | None | T232677 Remove support for Debian Jessie in Cloud Services | |||
Resolved | Andrew | T218119 Disable jessie VM creation in VPS |
Event Timeline
Comment Actions
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.
Comment Actions
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 | +--------------------------------------+-----------+----------+
Comment Actions
Cool, could you please document this somewhere? perhaps https://wikitech.wikimedia.org/wiki/Portal:Cloud_VPS/Admin/VM_images
Comment Actions
I just enabled Jessie in 'security-tools' so they can test existing Jessie deployments