/srv/irclogs.ubuntu.com/2014/12/02/#cloud-init.txt

=== harlowja_ is now known as harlowja_away
=== shardy_z is now known as shardy
=== zz_gondoi is now known as gondoi
john-davidgeHello everyone o/18:18
john-davidgeI 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:19
JayFI don't believe so; but IMBW18:20
john-davidgeInteresting. Specifically I'm interested in using an IPv6 address instead of the default. Perhaps this will require a change to cloud inti18:23
john-davidge*init18:23
harmw_ipv6 metadata? 18:25
=== harmw_ is now known as harmw
harmwhow whre you planning that?18:25
JayFOooh. Fancy.18:26
JayFI like IPv6, would be interesting to hear how you get it working :)18:27
harmw^ +1 :)18:27
john-davidgeso 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 working18:27
john-davidgeI'll do some more poking around and see what needs doing. Will keep you updated :)18:28
JayFWell you can always use configdrive with cloud-init18:29
JayFand just get rid of the metadata service18:29
JayFif you wanted to just not have to worry about that piece of it today18:29
=== harlowja_away is now known as harlowja_
john-davidgeJayF: True, but I'm trying to cover all the bases for now.18:33
harmwI'm running IP6 cloud atm18:33
harmwwith only metadata on V418:33
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 images18:36
john-davidgeharlowja_: 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
JayFwell, unless you use configdrive18:37
JayFthe metadata service is how user_data gets to the node :)18:37
JayFso you have a bit of a bootstrapping problem18:38
harlowja_yup :)18:38
JayFyou have to make the default (last IP in v4 link local) work or patch your images to have a different cloud-init config18:38
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-davidgeHmm, very true18:39
john-davidgeWhat is the liklihood that cloud-init could adopt an IPv6 default as well as the current IPv4 default?18:40
john-davidgeAnd 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 happens18:41
harlowja_and where said change would occur18:41
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:42
harlowja_although idk what ipv6 default that should use :-P18:44
john-davidgeharlowja_: Thanks! Will poke around with it in the morning18:45
harlowja_k18:45
john-davidgeharlowja_: Yes that's another debate!18:45
john-davidgeI was thinking the easist might be the v4-in-v6 of the current default18:46
john-davidgePerhaps ::ffff:a9fe:a9fe18:48
harlowja_maybe18:51
harlowja_so then it'd be interseting to try that18:51
harlowja_if u are stuck on ec2, that might be hard18:51
harlowja_since u need somewhere that provides an ipv6 metadata service18:51
john-davidgeharlowja_: I'm on OpenStack, so I can do what I want! :D18:52
harlowja_kk18:52
john-davidgeharlowja_: Will give it a go and report my findings tomorrow. 7pm here in the UK so I'm clocking off for the day18:52
harlowja_kk18:52
harlowja_cool18:52
john-davidgeThanks for your help!18:52
harlowja_may the force be with u :-P18:53
harlowja_ha18:53
john-davidgeAlways!18:53
tennishi... Where are the various files with "#cloud-config" supposed to live?21:34
harlowja_define live?22:04
harlowja_u can place them wherever u want22:04
smosero/ just wanted to say hello.22:33
smosertennis_, they live in /etc/cloud/cloud.cfg.d/whatever.cfg22:33
smoseror you can put them in as user-data.22:34
=== harlowja_ is now known as harlowja_away
=== harlowja_away is now known as harlowja_
tennis_smoser: How does that relate to /etc/cloud/config.cfg?  That is, does /etc/cloud/cloud.cfg get ignored? 23:16
=== gondoi is now known as zz_gondoi

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!