[14:54] <harmw> hm ,smoser 
[14:54] <harmw> I'm reading some doc about openstack/glance
[14:54] <harmw> glance image-create --location http://download.cirros-cloud.net/0.3.2/cirros-0.3.2-x86_64-disk.img --name "CirrOS 0.3.2 - Minimalist - 64-bit - Cloud Based Image" --is-public true --container-format bare --disk-format qcow2
[14:54] <harmw> 'we' should have a cirros-latest for that
[14:54] <harmw> *perhaps
[14:55] <smoser> what is cirros-latest ?
[14:55] <smoser> ah. as in the '--location'.
[14:55] <harmw> like, the latest stable version
[14:56] <smoser> well, yes. and you can read this resopnse however you'd like.
[14:56] <smoser> feel free to assert i'm abusing a monopoly.
[14:56] <smoser> i'd like to get things using simplestreams.
[14:57] <harmw> monopoly? :)
[14:57] <smoser> as it can securely download said image
[14:57] <harmw> ah, its a python lib?
[14:57] <smoser> (abusing cirros to further simplestreams)
[14:57] <smoser> a library and metadata format
[14:57] <harmw> hmk
[14:57] <smoser> http://download.cirros-cloud.net/streams/v1/
[14:58] <smoser> but anyway, i've been hesitant to make easy "just download cirros" that didn't use that.
[14:58] <harmw> looks nice
[14:58] <smoser> the data there is easily mirrorable (sstream-mirror)
[14:58] <smoser> we have it for cloud-images.ubuntu.com also.
[14:59] <smoser> and then, there is a tool http://bazaar.launchpad.net/~smoser/simplestreams/example-sync/files
[14:59] <smoser> that mirrors that into your glance.
[14:59] <smoser> and "sync"s it easily.
[14:59] <harmw> so its specific to glance/cloud stuff?
[14:59] <harmw> the whole simplestreams stuff, that is
[14:59] <smoser> not relaly. its just nice data
[14:59] <harmw> k
[14:59] <smoser> its data that describes downloads
[15:00] <harmw> looks nice, yes, json stuff
[15:00] <harmw> indeed
[15:00] <smoser> and sstream-sync mirrors that data to your local glance.
[15:00] <smoser> (knowing that it wants 'disk1.img' and such)
[15:00] <harmw> yea
[15:00] <harmw> you've looked at my buildroot branch lately btw?
[15:03] <smoser> no. i have not. i will. i need to do that.
[15:03] <smoser> and to get ppc64el merged in too.
[15:03] <harmw> oeh nice
[15:03] <smoser> err.. ppc64 big endian
[15:03] <smoser> i have that building
[15:03] <smoser> but it doesn't see virtio devices
[15:03] <smoser> er.. network virtio disk i think works.
[15:05] <harmw> you happen to know the defacto way of connecting compute nodes to an openstack environment over wan?
[15:07] <smoser> no. i dont.
[15:07] <harmw> google to the rescue! :p
[15:33] <CatKiller> Hi there! I've still have some issues with cloud-init. I can now use the correct data source in the image, but it does not seem to be able to access the source.
[15:33] <CatKiller> However, once the virtual machine has booted (without the cloud-init configuration so using password login)
[15:33] <CatKiller> I can access the metadataserver fine
[15:33] <CatKiller> I've pasted a full log there: http://bpaste.net/show/PAx9ZnCbT6N5D2QuR5pU/
[15:34] <CatKiller> My guess is that it can't reach the metadata server as the NIC is not yet configured (NIC is probably configured afterwards by upstart/systemd). Could that be it?
[15:35] <CatKiller> If so, is there a way when installing cloud-init to bring up the network interfaces before the VM boots?
[15:35] <CatKiller> To make this image I installed Ubuntu desktop in a KVM session, and ran "sudo apt-get install cloud-init", changed the data source to "OpenStack" only (this is going to run exclusively on OpenStack) and booted the image in openstack.