[06:39] <frankieonuonga> Hi folks, I am looking to use cloud init to create some containers on my machine but can not seem to find some documentation in regards as what should seat in user-data and meta-data
[10:51] <harmw> smoser: if you happen to see RaginBajin, please have him checkout https://code.launchpad.net/~harmw/cloud-init/freebsd
[12:41] <harmw> RaginBajin: ping
[12:41] <RaginBajin> harmw: pong
[12:42] <harmw> https://code.launchpad.net/~harmw/cloud-init/freebsd
[12:42] <harmw> could you check out that branch?
[12:43] <harmw> eg. create a new image (with oz), boot and instance with it, install bzr, checkout that branch and run tools/build-freebsd (or whatever I called it)
[12:43] <RaginBajin> sure. 
[12:44] <RaginBajin> I haven't used oz before, so I'll have to look up the howto
[12:45] <harmw> ok, its on github
[12:45] <harmw> and you'd probably want to add some of my patches as well
[12:45] <harmw> https://github.com/clalancette/oz/pull/168/commits
[12:47] <RaginBajin> Cool. I'll take a gander at it here in a few. 
[12:47] <harmw> hm, I also made a change in Guest.py that's addressed in the tickettracker on github...
[12:47] <harmw> something regarding symlinks
[12:58] <harmw> RaginBajin: I'm looking forward to seeing your results :)
[13:35] <smoser> pquerna, thanks. thats definitely something i'm interetsed in getting right. are you involed in the openstack bluerpint ?
[14:57] <pquerna> smoser: mostly indirectly, other people at rackspace are working on the nova/ironic side of it
[14:58] <pquerna> smoser: happy to push feedback through non-spec view channels if helpful :)
[14:58] <pquerna> s/view/review/
[14:59] <smoser> we have a team at canonical who is also in need of networking information format
[14:59] <smoser> and i would like to use one format and not have 2.
[14:59] <smoser> my comment on that review was wrt mtu
[15:00] <smoser> i think it really should be in there, and canonical is wanting/needing to describe bond interfaces.
[15:01] <pquerna> yup, makes sense.
[15:01] <pquerna> JoshG sits 8.9 feet from me in the SF office
[15:05] <pquerna> smoser: one thing we are looking at adding is a services: [] chunk in the format.  first pass is to add DNS servers, but we were also thinking of adding NTP and maybe even local apt mirror etc as a url in there.
[15:05] <smoser> oh yeah, and multiple ip addresses per nic. (my comment there). 
[15:05] <smoser> hm..
[15:05] <smoser> i originally had kind of done vendor_data to be a way to provide information like that.
[15:06] <smoser> and had envisioned 'mirrors' to be something that would put there.
[15:06] <pquerna> right
[15:06] <smoser> mirrors:
[15:06] <smoser>  http://archive.ubuntu.com/ubuntu: ['http://ubuntu.localmirror/ubuntu/']
[15:07] <smoser> something like that. but yeah, i agree that you do want something there. 
[15:07] <smoser> i even commented on vendor_data that we could use that as a way to experiment on things before they got into the metadata service proper
[15:07] <pquerna> yes
[15:08] <pquerna> we are very likely going to deploy it into vendor_data.json first
[15:08] <smoser> yeah, cool. and i'm ok with having cloud-init read it from there if its there, and let choose that over meta-data or something.
[16:49] <harmw> RaginBajin: any luck yet or should I just upload an image instead?
[17:27] <RaginBajin> harmw: Not yet.. I've been distracted a bit 
[17:33] <harmw> :)
[19:40] <harmw> smoser: would you like me to bug you again about cirros' new buildroot? :p
[21:28] <pquerna> JoshNang: so
[21:28] <pquerna> JoshNang: MTUs on things: ethernet is obvious, but should it also be a field on the VLAN and/or bonds?
[21:29] <pquerna> JoshNang: trying to find docs on what linux does when MTU on eth0 is 1500 but bond or vlan has a higher value.
[21:58] <JoshNang> so i've seen a couple references to the vlan defaulting to the NIC's MTU if they're different (on blogs/articles), but can't find that in any docs
[22:12] <pquerna> smoser: for multiple IPs, is having N network {} defs OK, or were you thinking of having an array of IPs inside the network?