Re: Adding symbolic links for "current" images
Hi Mohammed,
On Thu Nov 17, 2016 at 11:08:13 -0500, Mohammed Naser wrote:
> Hi everyone,
>
> We currently have CI in place to watch for new images which are being
> released by vendors, launch them on our cloud, run a small smoke test
> and then publish them. This allows us to get up-to-date images
> quickly and automatically on our OpenStack cloud.
>
> At the moment, this workflow breaks with Debian (slightly) because
> there is no single URL which will always point to the latest version,
> while we do have the /current/ folder, you must still know the exact
> release number in order to proceed.
>
> Would it be possible to introduce some symbolic links to point to the
> newest release in /current/, something similar to this:
>
> /current/debian-current-openstack-amd64.qcow2 points to
> /8.6.1/debian-8.6.1-openstack-amd64.qcow2
>
> That way, /current/ only points to current and whoever wants to hit
> the tagged releases can go to them directly. If we point our CI to
> /current/, that's good enough for us as well.
While i can understand your intention here, i am not that much thrilled
about the link you are proposing. I will explain why.
With a /current/ link a lot of people (who might then do the same thing
as you want to do) will be surprised, once we release Debian Stretch
(Debian 9), and suddenly have a major version change.
What i would be willing to accept thought, would be a
/current-8/debian-current-openstack-amd64.qcow2 link which points to the
latest Debian Jessie image. That way people will not need to ajust their
scripts once we do a point release for minor updates of the images.
Cheers,
Martin
--
Martin Zobel-Helas <zobel@debian.org> Debian System Administrator
Debian & GNU/Linux Developer Debian Listmaster
http://about.me/zobel Debian Webmaster
GPG Fingerprint: 6B18 5642 8E41 EC89 3D5D BDBB 53B1 AC6D B11B 627B
Reply to: