=== shardy is now known as shardy_lunch
=== shardy_lunch is now known as shardy
[18:05] <smoser> rharper, powersj i'm running "full" run of lxc and nocloud against my current https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/333059
[18:07] <rharper> nice
[18:07] <smoser> hmm.
[18:08] <smoser> i tihnk that launchpad got hosed on that
[18:08] <smoser> it doesn't knwo of any of muh newer pushes
[18:08] <smoser> oh wait.
[18:08] <smoser> stale page
[18:16] <smoser> and look at this:
[18:16] <smoser>  21 files changed, 319 insertions(+), 327 deletions(-)
[22:23] <bdx> hello
[22:24] <bdx> are there any examples out there of network interface configuration for the nocloud datasource
[22:24] <bdx> ?
[22:25] <bdx> for example, does network device configuration get its own file, network-config?
[22:25] <bdx> or do I add it in with the meta-data with a top level header "network:"
[22:25] <bdx> few discrepancies it would be nice to clear up
[22:28] <bdx> oh .. nm
[22:28] <bdx> just found it
[22:29] <bdx> in the docs :P
[22:30] <dpb1> :)
[22:35] <smoser> bdx: network-config
[22:35] <smoser> and no top level 'network' key (since that is implied as ait is in 'network-config')
[22:36] <bdx> smoser: yeah ... I think I'm hitting a possible bug see line 3 http://paste.ubuntu.com/25875749/
[22:37] <bdx> I think I'm setting it correctly
[22:37] <bdx> I'm doing as you (and the docs) say
[22:37] <bdx> and it seems to be taking it, but like, not taking it
[22:38] <bdx> network-config < http://paste.ubuntu.com/25875757/
[22:40] <bdx> possibly there is something I need to do to make the network-config run after the creation of the device...
[22:40] <bdx> possibly I need to use version 2
[22:54] <bdx> ahh, I think I see whats going on
[22:54] <bdx> I need to target an existing mac address
[22:56] <bdx> cloud-init isn't creating a new device, its configuring an existing device
[23:00] <bdx> oh, yea!
[23:02] <bdx> the key thing was that I had to create the vm with a defined mac address ANDd have attached a config drive with network-config with the same mac address I used when creating the vm
[23:03] <bdx> yeah, nm
[23:03] <bdx> still didn't work
[23:07] <bdx> so, whats I did find
[23:07] <bdx> is that when I made the mac address of the vm match the mac address in the network-config, I get a clean cloud-init log
[23:07] <bdx> http://paste.ubuntu.com/25875903/
[23:08] <bdx> so cloud-init is finding the device now
[23:08] <bdx> it seems
[23:08] <bdx> it still isn't getting configured though