=== shardy_afk is now known as shardy
[08:19] <openstackgerrit> XiaBing Yao proposed openstack/cloud-init: Update stackforge to openstack  https://review.openstack.org/237452
[09:29] <Odd_Bloke> smoser: https://code.launchpad.net/~daniel-thewatkins/cloud-init/lp1460715/+merge/274897 is ready for re-review. :)
[13:10] <smoser> Odd_Bloke, so, one pick.
[13:10] <smoser> if we can avoid the fork, if there is data in /sys it seems fastest to read it from there.
[13:10] <smoser> doesnt it ?
[13:14] <Odd_Bloke> smoser: I'm happy to move to that; I was thinking that (a) blockdev will maintain an interface whereas /sys might change, and (b) blockdev might be available on platforms (BSD?) where /sys is not.
[13:14] <smoser> b is almost certainly true
[13:15] <smoser> but generally i dont think sys is a moving target
[13:15] <smoser> i have a few other comments i'll put in review.
[13:17] <mwak> hello
[13:17] <smoser> hey
[13:19] <mwak> I created a PR yesterday to merge the Scaleway datasource into cloud-init, https://code.launchpad.net/~edouardb/cloud-init/scaleway-datasource/+merge/274861. Any idea of the ETA to get it merged :) ?
[15:14] <smoser> mwak, i reviewed. let me know if you n eed any helip.
[15:14] <smoser> help
[15:25] <mwak> smoser: thx!
[15:30] <mwak> smoser: a) b) c) concerning d, is it possible to do that in another PR as we do not use that atm
[15:30] <mwak> *Alright for a/b/c
[15:32] <smoser> sure. if its not there, no point in looking for it.  i'd think it'd be great if you have it though.
[15:55] <natorious> smoser: I'd been thinking more about network json and am not 100% that base.BaseOpenStackSource.network_config should return json data
[15:55] <smoser> :)
[15:56] <natorious> as is, it returns a network conf file when not network_json
[15:56] <natorious> so should we process the network_json into a file to return specific to ea distro?
[15:57] <natorious> also been throwing around the idea of vendor plugins and how they would fit into all this
[15:57] <natorious> that is extensibility based on cloud providers specific feature set
[16:19] <smoser> natorious, well, there is no 'file' that is specific to each distro
[16:19] <smoser> unless you consider a tarball. but even then, not really
[16:20] <smoser> ie, /etc/sysconfig/ you'd potentially have to write and delete multiple files
[16:20] <natorious> right
[16:20] <natorious> so passing content as network config as currently is is needing some eyes
[20:40] <smoser> natorious, around ?
[20:42] <smoser> http://paste.ubuntu.com/12879626/
[20:42] <smoser> something to think about %
[20:42] <smoser> ^
[22:55] <natorious> smoser: your talking to the right guy then ;)
[22:56] <natorious> so, persistent datasource w/ the openstack metadata service could call the same module for doing them after init
[22:56] <natorious> thats the idea anyways
[22:57] <natorious> I believe the intel osic cloud thats being spun up w/ have onmetal resources for all of us to play with
[22:57] <natorious> whenever that comes around