Scott,
Thank you for your answer. I had actually reached the solution of wget-
ing files for every single suite. I should have posted that, avoiding
you the burden of the answer. Sorry for that. My first use of these
files is to keep the matching between our remote EC2 machines and our
local Eucalyptus ones, trying to make sure they are based on exactly
the same base images, and this file is just perfect for that, a plain
'grep' doing the trick (it is actually in that context I detected the
bug mentioned above).
Yes, definitely my argument was referring to better keep N very small
files + one small file than querying (N+1) very small files each time.
By the way, not that it impacted me, but I noticed some
"irregularities" in the naming of beta and alpha releases. For
example, for Lucid you used "alpha-1", "beta-1" in the path an "beta1"
in the filename. Then, still in Lucid, you provided another path,
"beta1". Now go to Maverick and you again have "alpha-1" path with no
"alpha1" name. Is that supposed to be the logic from now on? I mean a
'SUITE-server-uec-ARCH.tar.gz' generic name, whatever the release,
specifics being given by the path?
Thanks again for all your work Scott. It definitely made our life
easier. Ubuntu rocks!
On Aug 30, 5:29 pm, Scott Moser <smo...@ubuntu.com> wrote:
> On Sat, 28 Aug 2010, Thierry wrote:
> > Actually, while I am at it, why not add the equivalent of
> >
http://uec-images.ubuntu.com/query/lucid/server/released-dl.txt, but
> > for all distributions in /query directly?
> Well, I was just trying to avoid duplication of data, and aiding people to
> get really only what they need/want rather than everything. Its not
> perfect, and the overhead of multiple requests is probably worse than one
> request for more data since we're dealing with pretty small files.
> The usage that I was designing for was basically people pollinghttp://uec-images.ubuntu.com/query/released.latest.txt, and determining
> if they were out of date based on that data. If so, they would do further
> queries to figure out what actions needed to be done.
> That said:
> http://uec-images.ubuntu.com/query/released.latest.txt
> gives you a row for each unique build in the released 'stream'.
> The 'released' stream contains builds labeled 'alpha-*', 'beta-*', and
> 'rc', and 'release'. The other stream is the 'daily' stream.
> The primary key for a build is a combination of the 4 fields:
> suite, build_name, label, serial.
> ie:
> hardy server release 20100827
> That line above tells you that you can find download data for that build
> by readinghttp://uec-images.ubuntu.com/query/<suite>/<build_name>/<stream>-dl.txthttp://uec-images.ubuntu.com/query/hardy/server/released-dl.txt
> That file has 7 fields
> The first 4 of the key (suite, build_name, label, serial)
> Followed by arch, path, and 'suggested name'.
> So, by walking each row in the released.latest.txt, and getting the
> appropriate released-dl.txt, you can get the data you want.
> Ie, this will get you what you wanted:
> burl="http://uec-images.ubuntu.com/query"; str="released"
> wget -q "${burl}/${str}.latest.txt" -O - |
> while read suite bn lab ser; do
> wget -q -O - "${burl}/${suite}/${bn}/${str}-dl.txt" ;
> done
> Alternatively, the data on uec-images is available via rsync. So, the
> following will also get you want you want:
> rsync -a uec-images.ubuntu.com::uec-images/query .
> cat query/*/*/released-dl.txt
