[15:03] <elro> does it matter that ebs root image amis are not available in ubuntu-images-eu?
[16:32] <kim0> elro: what do you mean by "does it matter"
[16:33] <elro> kim0: I assumed it was there so that it used repositories within the ec2 region
[16:33] <kim0> elro: the instance gets the correct ec2 repos configured for it, as it boots
[16:34] <elro> ah, ok fine. I guess ubuntu-images-eu is only there for historical reasons now
[17:16] <smoser> elro, i'm confused.
[17:17] <smoser> "does it matter that ebs root image amis are not available in ubuntu-images-eu?"
[17:17] <smoser> what does that mean
[17:17] <smoser> there are most certainly ubuntu ebs root images in the eu-west-1 region
[17:32] <elro> smoser: when launching an instance from the aws management console, if I filter AMIs by Instance-Store Images and "ubuntu-images-eu" I get results, but not when I filter by EBS Images and "ubuntu-images-eu"
[17:33] <smoser> ah.
[17:33] <smoser> i would not filter by that
[17:33] <smoser> :)
[17:33] <smoser> i'm not exactly sure how the filtering works.
[17:33] <smoser> but released images for the eu-west-1 region
[17:34] <smoser> will all be named with "ubuntu-images/"
[17:34] <smoser> instance-store images have a "manifest path" (that is just not something relevant to ebs root instances).
[17:34] <smoser> and that manifest path will be: ubuntu-images-eu
[17:34] <smoser> 1 of 2 things is happening so that your instance-store search works
[17:35] <smoser> a.) it searches manifest path
[17:35] <smoser> b.) it searches only 'name', but if there is no name, uses 'manifest-path'.
[17:35] <smoser> if 'b' is the reason, then you're only seeing older images.
[17:36] <smoser> easiest way to get which image you want is to go to http://uec-images.ubuntu.com/release or http://cloud.ubuntu.com/ami/
[17:36] <smoser> kim0, do you load uec-images.ubuntu.com/query on every page load of http://cloud.ubuntu.com/ami/ ?
[17:36] <kim0> smoser: nope
[17:36] <kim0> smoser: it's updated every hour
[17:36] <smoser> why is it slow to load.
[17:37] <smoser> theres a good 3 seconds on my system of "processing" before it shows something
[17:37] <kim0> hmm
[17:38] <smoser> elro, ^
[17:39] <elro> thanks smoser
[17:39] <smoser> elro, if you're interested in doing this programatically, then there is data at http://uec-images.ubuntu.com/query that you can use.
[17:40] <smoser> that is what kim0's page reads from
[17:58] <kim0> smoser: Here's the code that generates the json table with release data http://bazaar.launchpad.net/~kim0/+junk/cloudubuntu/view/head:/amilocator/views.py
[17:58] <kim0> smoser: The releasesTable method.
[17:59] <kim0> I think @cache_page(60 * 60 * 1) is not doing what I thought it would
[17:59] <smoser> so you see that slow load also
[17:59] <kim0> I thought it would cache the functions output server side for fast responses
[17:59] <kim0> smoser: to me it's sometimes fast (0.5) sometimes take 3s
[18:00] <kim0> when I put a wget in a shell for loop .. it's consistently fast (0.5)
[18:00] <smoser> http://code.djangoproject.com/ticket/1015
[18:00] <smoser> that looks old though
[18:01] <kim0> hmm I think I have it
[18:01] <kim0> http://cloud.ubuntu.com/wp-content/themes/uecv2/ami-locator.php >> slow
[18:02] <kim0> http://cloud.ubuntu.com/ami-locator/releasesTable >> fast
[18:02] <elro> Anyone know what the DEVPATHS line of /etc/ebsmount.conf should be for it to work on ec2?
[18:02] <kim0> in development, we had written ami-locator.php (server side proxy), it's still being used, although it doesn't have to
[18:02] <kim0> I'll try to switch to direct connections .. should hopefully be faster