[09:12] <niluje> hi, any idea when cloud-init will be released? :p
[13:26] <smoser> niluje, :-(.
[13:28] <niluje> don't be sad :(
[13:28] <niluje> what did I tell wrong :(
[13:35] <smoser> you just pointed out how delinquent i am
[13:36] <smoser> i really do feel like we're rpobably acceptably in a release-able state.
[13:39] <smoser> it just always gets put on the back burner.
[13:40] <smoser> niluje, is there something in particular you're wanting from a release ? other than just a stamp ?
[13:42] <niluje> a stamp and a hope to see it eventually included in distribs
[13:46] <smoser> thats quite reasonable.
[19:33] <smoser> rharper, done with our gce instance for the moment.
[19:33] <smoser> https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/329387
[19:33] <rharper> smoser: k
[19:33] <smoser> well... done. you can kill it.
[19:34] <rharper> fwiw, a 17.04 instance (and I've not launched another xenial) it was like 3 seconds
[19:34] <smoser> it seems to me that their metadata service caches. and first hits to it are in fact slow.
[19:34] <rharper> so *bad* luck
[19:34] <rharper> y
[19:35] <smoser> you can see it. cd /home/ubuntu/cloud-init
[19:35] <smoser>  python3 -m cloudinit.sources.DataSourceGCE
[19:35] <rharper> smoser: if you're touching, we should switch HTTP header to the current preferred
[19:35] <rharper> Metadata-Flavor: Google
[19:36] <rharper> https://cloud.google.com/compute/docs/storing-retrieving-metadata#querying
[19:39] <blackboxsw> smoser: think I've addressed all schema subcommand branch comments: https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/329233
[19:39] <blackboxsw> updated the branch description to capture all changes
[19:42] <smoser> "This header indicates that the request was sent with the intention of retrieving metadata values, rather than unintentionally from an insecure source,"
[19:43] <smoser> yeah... that provides security. only rootkits that can change their headers can hit that md.
[20:44] <smoser> rharper, can you re-submit your comment to https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/329397
[20:44] <smoser> (just copy from https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/329152)
[20:45] <smoser> err..
[20:45] <smoser> https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/329387
[20:53] <smoser> blackboxsw, i approved https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/329233
[20:53] <smoser> but c-i needs to
[20:53]  * smoser out
[20:53] <blackboxsw> smoser: thanks. see ya
[21:47] <rharper> smoser: ok
[21:49] <rharper> smoser: done
[22:04] <sabari> smoser: rharper: I was finally able to fix the missing dns-namservers on eth0 in the ENI file (nova instance with config drive on Ubuntu 16.04) using a custom nova patch.
[22:04] <sabari>  I did this in nova http://paste.openstack.org/raw/619103/ which results in the following network_data.json http://paste.openstack.org/raw/619101/
[22:05] <rharper> sabari: \o/
[22:06] <sabari> I am not sure if this is right but it fixed my problem for now. Since the upstream patch that smoser referred https://review.openstack.org/#/c/467699/ needs a corresponding cloud-init fix that is yet to be merged.
[22:10] <sabari> I will file a LP bug just to track this issue. Feel free to close it if you feel it's already being worked upon.
[22:10] <blackboxsw> sabari: that'd be super
[22:10] <blackboxsw> it helps us track/prioritize
[22:31] <sabari> Filed https://bugs.launchpad.net/cloud-init/+bug/1712440
[22:31] <ubot5> Ubuntu bug 1712440 in cloud-init "Missing dns-nameservers in eth0 with config drive on openstack instance" [Undecided,New]
[22:32] <sabari> blackboxsw: ^:)
[22:48] <blackboxsw> +1 sabari
[22:48] <blackboxsw> thanks