[18:18] <john-davidge> Hello everyone o/
[18:19] <john-davidge> I have a question. Is it possible to change the 'magic' IP (169.254.169.254) cloud init uses to access EC2-style meta data with a config option?
[18:20] <JayF> I don't believe so; but IMBW
[18:23] <john-davidge> Interesting. Specifically I'm interested in using an IPv6 address instead of the default. Perhaps this will require a change to cloud inti
[18:23] <john-davidge> *init
[18:25] <harmw_> ipv6 metadata? 
[18:25] <harmw> how whre you planning that?
[18:26] <JayF> Oooh. Fancy.
[18:27] <JayF> I like IPv6, would be interesting to hear how you get it working :)
[18:27] <harmw> ^ +1 :)
[18:27] <john-davidge> so I'm testing for cloud environments running on IPv6-only networks, and I'm trying to figure out what changes (if any) are needed to get cloud-init working
[18:28] <john-davidge> I'll do some more poking around and see what needs doing. Will keep you updated :)
[18:29] <JayF> Well you can always use configdrive with cloud-init
[18:29] <JayF> and just get rid of the metadata service
[18:29] <JayF> if you wanted to just not have to worry about that piece of it today
[18:33] <john-davidge> JayF: True, but I'm trying to cover all the bases for now.
[18:33] <harmw> I'm running IP6 cloud atm
[18:33] <harmw> with only metadata on V4
[18:36] <harlowja_> john-davidge so u can change it; the problem is that it needs to get the config from somewhere to change that value in the first place ;)
[18:36] <harlowja_> unless u have control over your images
[18:37] <john-davidge> harlowja_: Does that have to be changed on an image-by-image basis, or can it be passed at startup via user-data or similar?
[18:37] <JayF> well, unless you use configdrive
[18:37] <JayF> the metadata service is how user_data gets to the node :)
[18:38] <JayF> so you have a bit of a bootstrapping problem
[18:38] <harlowja_> yup :)
[18:38] <JayF> you have to make the default (last IP in v4 link local) work or patch your images to have a different cloud-init config
[18:39] <harlowja_> john-davidge the issue is 'passed at startup via user-data' (how does this data get to the image if not by the metadata service)?
[18:39] <john-davidge> Hmm, very true
[18:40] <john-davidge> What is the liklihood that cloud-init could adopt an IPv6 default as well as the current IPv4 default?
[18:41] <john-davidge> And does anyone know who I'd need to talk to about that?
[18:41] <harlowja_> u talking to the right people i think ;)
[18:41] <harlowja_> http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/cloudinit/sources/DataSourceEc2.py is where the ec2 stuff happens
[18:41] <harlowja_> and where said change would occur
[18:42] <harlowja_> http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/cloudinit/sources/DataSourceEc2.py#L42 could likely just have a ipv6 url, and it might 'just work'
[18:44] <harlowja_> although idk what ipv6 default that should use :-P
[18:45] <john-davidge> harlowja_: Thanks! Will poke around with it in the morning
[18:45] <harlowja_> k
[18:45] <john-davidge> harlowja_: Yes that's another debate!
[18:46] <john-davidge> I was thinking the easist might be the v4-in-v6 of the current default
[18:48] <john-davidge> Perhaps ::ffff:a9fe:a9fe
[18:51] <harlowja_> maybe
[18:51] <harlowja_> so then it'd be interseting to try that
[18:51] <harlowja_> if u are stuck on ec2, that might be hard
[18:51] <harlowja_> since u need somewhere that provides an ipv6 metadata service
[18:52] <john-davidge> harlowja_: I'm on OpenStack, so I can do what I want! :D
[18:52] <harlowja_> kk
[18:52] <john-davidge> harlowja_: Will give it a go and report my findings tomorrow. 7pm here in the UK so I'm clocking off for the day
[18:52] <harlowja_> kk
[18:52] <harlowja_> cool
[18:52] <john-davidge> Thanks for your help!
[18:53] <harlowja_> may the force be with u :-P
[18:53] <harlowja_> ha
[18:53] <john-davidge> Always!
[21:34] <tennis> hi... Where are the various files with "#cloud-config" supposed to live?
[22:04] <harlowja_> define live?
[22:04] <harlowja_> u can place them wherever u want
[22:33] <smoser> o/ just wanted to say hello.
[22:33] <smoser> tennis_, they live in /etc/cloud/cloud.cfg.d/whatever.cfg
[22:34] <smoser> or you can put them in as user-data.
[23:16] <tennis_> smoser: How does that relate to /etc/cloud/config.cfg?  That is, does /etc/cloud/cloud.cfg get ignored?