[01:15] why isn’t `blkid` mocked? basically, why do I have to run tests as root on debian? ;_; === harlowja is now known as harlowja_away === praneshp_ is now known as praneshp === evilissimo|afk is now known as evilissimo === praneshp_ is now known as praneshp === praneshp_ is now known as praneshp [12:46] ping [12:46] !ping [12:46] hey harlowja_away === zz_gondoi is now known as gondoi === evilissimo is now known as evilissimo|afk === harlowja_away is now known as harlowja [19:02] hi harlowja [19:02] linuxgeek_ howdy [19:02] harlowja, fairly well, thanks. [19:03] re yesterday's thingy on the cloudinit. with a trusty ubuntu cloud image [19:03] i was able to test the http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/examples/cloud-config-boot-cmds.txt [19:03] and it works [19:03] woot [19:03] there is another cloud image which is vmdk fedora 19 [19:04] k [19:04] that one might not have cloud-init built in, or does it? [19:04] and that is not able to reach the metadata service url http://169.254.169.254 [19:04] hence the userdata also does not work [19:05] how is it that one image works while the other does not [19:05] is this specific to how the image is built? [19:05] yes it does have cloud-init in it [19:05] i can see the cloud directory in /var/lib and cloud-init.log in /var/log [19:06] so it is a cloud-init enabled image [19:06] it is likely more how the image was built, what firewall settings (?) could be by default on [19:06] that should be the only difference really [19:06] ok [19:06] and those differences could stop it from contacting 169 [19:07] is this a internal url? [19:07] define internal ;) [19:07] lol :-) [19:07] its a special IP [19:07] internal = within the instance and not going outside [19:08] not usually [19:08] http://stackoverflow.com/a/7499376 is an idea of what it does [19:08] but it varies depending on the cloud u are on (the exact details vary) [19:08] openstack clouds do it differently than amazon and so-on... [19:09] so its 'special' [19:10] yes o~s and ec2 is so different [19:11] and i have o~s based cloud env [19:11] i read http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AESDG-chapter-instancedata.html [19:11] and the stackoverflow post. [19:12] so it says ec2 knows what instance is making the request and it knows the info abt the instance [19:12] right, openstack is the same [19:12] so ec2 can return the metadata that is requested [19:12] right [19:13] so this happens even before the request reaches the special ip? [19:13] right, it happens during vm building time [19:13] so my guess is if it works for one image and not another, then its an image thign [19:13] ok [19:13] thats my gut feeling [19:13] i'm not sure what the solution is though ;) [19:14] the flow is, the instance makes a request to the special ip based on the userdata injected to it [19:14] and before that happens, neutron, nova, make it possible for that special IP to be directed somewhere [19:14] the openstack sees this request and knows which instance is sending this request [19:14] ya [19:14] and sends back some data [19:15] and that goes through the pipes and pops back up in the instance [19:15] the instance thinks it talked to a magic 169 address and was none-the-wiser [19:15] ^ pipe magic [19:16] is it nova neutron which plays a role in routing the request to the special ip via the nova/neutron security groups and rules? [19:17] both afaik [19:17] i'm planning to convert the trusty.img file [which works] to a trusty.vmdk and test [19:17] i believe nova is the endpoint and has the instance data, neutron sets up the plumbing [19:17] so both are involved [19:19] i browsed through the o~s docs and the net too, i did not find details about how nova and neutron play a role in the metadata part. do you happen to know of a doc or a guide which talks about this? [19:19] i do not, but if u jump in #openstack-neutron channel u might find someone who does [19:19] there should be something somewhere i would think [19:21] have u used qemu-img convert? [19:21] i have [19:21] sure, i'm on the neutron channel. i'll ask arnd for the docs [19:21] cool, have u converted a .img file to .vmdk? [19:22] negative, i haven't touched vmdk stuff :) [19:22] i have done raw -> qcow2 and qcow2 -> raw [19:22] but not vmdk stuff [19:22] linuxgeek_ mestery on the neutron channel should be able to find something [19:23] i thought arnd was more in glance (maybe different arnaud) [19:23] or maybe someone else, haha [19:23] haha, yep sure. === gondoi is now known as zz_gondoi === praneshp_ is now known as praneshp