It would be good to also produce such an index for clouds where we don't publish images, so that juju use is seamless everywhere. I've talked with ben & scott about using query2 for use with non-ec2 images, though its still not ideal, at the moment its focused fairly verbose with extraneous things and embedded build references across multiple files (http://cloud-images.ubuntu.com/query2/server/ec2.json). For openstack servers its possible we can glean some useful information from the glance server (http://docs.openstack.org/developer/glance/glanceapi.html#list-available-images-in-more-detail), but the contents of such are adhoc. At a minimum we need to know its ubuntu and its release series for a given image.
It would be good to also produce such an index for clouds where we don't publish images, so that juju use is seamless everywhere. I've talked with ben & scott about using query2 for use with non-ec2 images, though its still not ideal, at the moment its focused fairly verbose with extraneous things and embedded build references across multiple files (http:// cloud-images. ubuntu. com/query2/ server/ ec2.json). For openstack servers its possible we can glean some useful information from the glance server (http:// docs.openstack. org/developer/ glance/ glanceapi. html#list- available- images- in-more- detail), but the contents of such are adhoc. At a minimum we need to know its ubuntu and its release series for a given image.