On Fri, Sep 9, 2016 at 6:47 PM, Kevin Fenzi <kevin@xxxxxxxxx> wrote: > On Fri, 9 Sep 2016 11:14:31 +0530 > Kushal Das <mail@xxxxxxxxxxxx> wrote: > >> On 08/09/16, Kevin Fenzi wrote: >> > On Tue, 6 Sep 2016 11:24:14 -0500 >> > Adam Miller <maxamillion@xxxxxxxxxxxxxxxxx> wrote: >> > >> > > On Sat, Sep 3, 2016 at 12:58 PM, Kevin Fenzi <kevin@xxxxxxxxx> >> > > wrote: >> > > > On Thu, 1 Sep 2016 11:43:11 -0500 >> > > > Adam Miller <maxamillion@xxxxxxxxxxxxxxxxx> wrote: >> > > > >> > > >> Hello all, >> > > >> I recently wrote a request/proposal to the websites team >> > > >> for a "latest" download URL[0] for the Atomic Host release >> > > >> artifacts such that someone could always point to the latest >> > > >> URL and it would return whatever the most recently released >> > > >> Two Wee Atomic Host image was. It was suggested that the >> > > >> websites might not be the best place for this so I was curious >> > > >> how I might best go about adding this to >> > > >> download.fedoraproject.org (or where ever might be more >> > > >> appropriate). >> > > > >> > > > So is this a static link that we just need to make once? Or is >> > > > it something that would change with every 2 week release? >> > > >> > > It would change every 2 week release. Is there any way to have it >> > > auto-generated via fedmsg data? The needed information is sent to >> > > fedmsg currently. >> > >> > Well, not easily, but we could come up with something I suppose. >> > >> > We do have some automation that runs based on fedmsg and could run >> > ansible, but I'd be concerned that this config would then be outside >> > our ansible repo. I suppose we could setup something to commit and >> > push too, but not sure how accident prone that might end up being. >> > >> > What does a two week atomic download url look like right now? >> > >> Below are few links from the latest release. >> >> https://download.fedoraproject.org/pub/alt/atomic/stable/CloudImages/x86_64/images/Fedora-Atomic-24-20160820.0.x86_64.qcow2 >> https://download.fedoraproject.org/pub/alt/atomic/stable/CloudImages/x86_64/images/Fedora-Atomic-24-20160820.0.x86_64.raw.xz >> https://download.fedoraproject.org/pub/alt/atomic/stable/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-24-20160820.0.x86_64.vagrant-virtualbox.box >> https://download.fedoraproject.org/pub/alt/atomic/stable/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-24-20160820.0.x86_64.vagrant-libvirt.box > > Can we adjust the compose script to just make in that same directory > some links that replace the '20160820.0' with 'latest' ? then we can > just have the web point to 'latest' versions and done? I proposed that for the release script originally and releng was against the idea so I went this route. :) -AdamM > > kevin > > _______________________________________________ > infrastructure mailing list > infrastructure@xxxxxxxxxxxxxxxxxxxxxxx > https://lists.fedoraproject.org/admin/lists/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx > _______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
