/srv/irclogs.ubuntu.com/2017/08/22/#cloud-init.txt

nilujehi, any idea when cloud-init will be released? :p09:12
smoserniluje, :-(.13:26
nilujedon't be sad :(13:28
nilujewhat did I tell wrong :(13:28
smoseryou just pointed out how delinquent i am13:35
smoseri really do feel like we're rpobably acceptably in a release-able state.13:36
smoserit just always gets put on the back burner.13:39
smoserniluje, is there something in particular you're wanting from a release ? other than just a stamp ?13:40
nilujea stamp and a hope to see it eventually included in distribs13:42
smoserthats quite reasonable.13:46
smoserrharper, done with our gce instance for the moment.19:33
smoserhttps://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/32938719:33
rharpersmoser: k19:33
smoserwell... done. you can kill it.19:33
rharperfwiw, a 17.04 instance (and I've not launched another xenial) it was like 3 seconds19:34
smoserit seems to me that their metadata service caches. and first hits to it are in fact slow.19:34
rharperso *bad* luck19:34
rharpery19:34
smoseryou can see it. cd /home/ubuntu/cloud-init19:35
smoser python3 -m cloudinit.sources.DataSourceGCE19:35
rharpersmoser: if you're touching, we should switch HTTP header to the current preferred19:35
rharperMetadata-Flavor: Google19:35
rharperhttps://cloud.google.com/compute/docs/storing-retrieving-metadata#querying19:36
blackboxswsmoser: think I've addressed all schema subcommand branch comments: https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/32923319:39
blackboxswupdated the branch description to capture all changes19:39
smoser"This header indicates that the request was sent with the intention of retrieving metadata values, rather than unintentionally from an insecure source,"19:42
smoseryeah... that provides security. only rootkits that can change their headers can hit that md.19:43
smoserrharper, can you re-submit your comment to https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/32939720:44
smoser(just copy from https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/329152)20:44
smosererr..20:45
smoserhttps://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/32938720:45
smoserblackboxsw, i approved https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/32923320:53
smoserbut c-i needs to20:53
* smoser out20:53
blackboxswsmoser: thanks. see ya20:53
rharpersmoser: ok21:47
rharpersmoser: done21:49
sabarismoser: 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:04
rharpersabari: \o/22:05
sabariI 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:06
sabariI 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
blackboxswsabari: that'd be super22:10
blackboxswit helps us track/prioritize22:10
sabariFiled https://bugs.launchpad.net/cloud-init/+bug/171244022:31
ubot5Ubuntu bug 1712440 in cloud-init "Missing dns-nameservers in eth0 with config drive on openstack instance" [Undecided,New]22:31
sabariblackboxsw: ^:)22:32
blackboxsw+1 sabari22:48
blackboxswthanks22:48

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