/srv/irclogs.ubuntu.com/2018/08/06/#cloud-init.txt

htaccessare there any other docs about https://cloudinit.readthedocs.io/en/latest/topics/examples.html#adding-a-yum-repository besides this? I want to know if i can point gpgkey: at a url rather than a file03:21
htaccessfound it here https://www.zetta.io/en/help/articles-tutorials/cloud-init-reference/03:32
TJ-I'm trying to diagnose why a Vagrant ubuntu/bionic64 image isn't accessing the userdata in the 2nd box, and I can't find any docs on how that is expected to happen. /run/cloud-init/cloud-init-generator.log reports "...enabled but no datasource found, disabling"10:26
TJ-OK, seems that vagrant-libvirt is setting the wrong disk type ('raw' instead of 'qcow2').11:22
otuboHey guys, any plans to have a NetworkManeger renderer for cloud-init in a near future?14:44
dpb1 netplan can render to nm14:49
TJ-otubo: the cloud-init package (on Ubuntu 18.04) has a NM hook14:49
dpb1read here: https://cloudinit.readthedocs.io/en/latest/topics/network-config.html14:50
TJ-otubo: I see /etc/NetworkManager/dispatcher.d/hook-network-manager in the cloud-init package14:50
otubodpb1: TJ- thanks I'll take a look14:51
powersjo/15:59
blackboxsw#startmeeting Cloud-init bi-weekly status meeting16:04
meetingologyMeeting started Mon Aug  6 16:04:05 2018 UTC.  The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.16:04
meetingologyAvailable commands: action commands idea info link nick16:04
dpb1o/16:04
blackboxswhi folks, let's kickoff another cloud-init status meeting. Welcome back. Lot's of summer vacations disrupting our typical meeting schedule.16:04
blackboxswOur last meeting's minutes should be up on our github site16:05
blackboxsw#link https://cloud-init.github.io/16:05
blackboxswfor this meeting we'll go through the following topics: previous actions, recent work, in-progress development and office hours16:07
blackboxsw#topic Previous Actions16:09
blackboxswfrom our last meeting we had a couple of actions to carry over16:09
blackboxswwe landed the folowing branch which added support for a datasource to re-write network config across each boot.  https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/34800016:10
blackboxsw#action rharper: and I need to review https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/33390416:10
meetingologyACTION: rharper: and I need to review https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/33390416:10
blackboxswthe above is still a carryover16:10
blackboxswthat's all for actions from last meeting16:11
blackboxsw#topic Recent Changes16:11
blackboxswthe following has landed in cloud-init tip:16:12
blackboxsw* oracle: fix detect_openstack to report True on OracleCloud.com DMI data (LP: #1784685)16:13
blackboxsw* tests: improve LXDInstance trying to workaround or catch bug.*16:13
blackboxsw* update_metadata re-config on every boot comments and tests not quite right [Mike Gerdts]16:13
blackboxsw* docs: note in rtd about avoiding /tmp when writing files16:13
blackboxsw* ubuntu,centos,debian: get_linux_distro to align with platform.dist16:13
blackboxsw* Fix boothook docs on environment variable name (INSTANCE_I -> INSTANCE_ID) (Marc Tamsky)16:13
blackboxsw* update_metadata: a datasource can support network re-config every boot16:13
ubot5Launchpad bug 1784685 in cloud-init "Oracle: cloud-init openstack local detection too strict for oracle cloud" [High,Fix committed] https://launchpad.net/bugs/178468516:13
blackboxsw* tests: drop salt-minion integration test16:13
blackboxsw* Retry on failed import of gpg receive keys.16:13
blackboxsw* tools: Fix run-container when neither source or binary package requested.16:13
blackboxsw* docs: Fix a small spelling error (Oz N Tiram)16:13
blackboxsw* tox: use simplestreams from git repository rather than bzr.16:13
blackboxswgenerally speaking we had been spending some cycles on a stable release update (SRU) for cloud-init into Xenial and Bionic with top of tree cloud-init.16:14
blackboxswnotably, we discovered a potential regression in Oracle datasource detection of their OpenStack implementation so that fix is queued for publish into xenial and bionic16:15
blackboxsw18.3-9 is what folks are looking for. in xenial/bionic/cosmic for latest cloud-init containing all the above fixes16:15
blackboxswAlso powersj has been working on an auto-lander for cloud-init branches to get a few of us out of the way once a branch hits acceptm16:16
blackboxswAlso powersj has been working on an auto-lander for cloud-init branches to get a few of us out of the way once a branch hits "Approved" status.16:16
blackboxsw#link https://jenkins.ubuntu.com/server/job/admin-lp-git-autoland/16:16
powersjyep that is live and with a recent fix to remove the extra "Author" line now16:16
powersjhopefully it is saving blackboxsw, smoser, and rharper time ;)16:16
blackboxswpowersj: can you explain what it does (so I don't have to type)16:17
blackboxsw:)16:17
powersjIf a merge request is put in the "Approved" state, it will get test merged with the master branch16:17
powersjthe tests will run the same as during a review and verify that it can merge cleanly16:17
powersjthe commit message will get linted to verify it fits our format16:18
powersjand if everything looks good, get merged in and pushed to master16:18
blackboxswthanks for that work powersj. it looks/works great so far.16:18
blackboxsw#topic In-progress Development16:19
blackboxswAll our current work is visible at the following trello board16:19
blackboxsw#link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin16:19
blackboxswI expect we'll have a couple of branches landed shortly in the following areas:16:20
blackboxsw- smoser is working: A datasource specific to Oracle, because of their specific implementation of Openstack. Oracle will no longer use just stock DataSourceOpenStack.16:21
blackboxsw- I16:21
blackboxsw- I'm trying to wrap up a branch for Azure to write network data from their IMDS per-boot16:21
blackboxsw#link https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/34870416:22
blackboxsw- Joyent (SmartOS) per-boot network config review16:22
blackboxsw  - a couple netplan config option bugs for bionic ++16:23
blackboxsw- and standardize instance-data sourcing in #cloud-config files (like referencing the hostname as detected from instance metadata)16:24
blackboxswI think that probably wraps it up for stuff in progress16:24
blackboxswanything I'm missing?16:24
blackboxsw... without further ado16:25
blackboxsw#topic Office Hource (next ~30 mins)16:25
blackboxsweyes will float on this channel for any bug/feature discussions, review requests  etc. any cloud-init topic is acceptable.16:26
blackboxswa number of us are going to be prepping for a cloud-init summit meeting in the weeks to come.  A number of attendees from various vendors and clouds are attending as well to do a bit of planning on what cloud-init should look like next year. If folks get a chance, think about any feature or topic suggestions that would benefit cloud-init users and we'll see if we can discuss them at the summit.16:28
blackboxswwhile I'm at it, I think I'll set the topic to next status meeting time so folks know it's coming.16:31
=== blackboxsw changed the topic of #cloud-init to: Reviews: http://bit.ly/ci-reviews | Meeting minutes: https://goo.gl/mrHdaj | Next status meeting: Monday 8/20 16:00 UTC | cloud-init 18.3 released (06/20/2018)
blackboxswalso just noticed the following branch, which admitedly is a bit stale, but adds hyperv logging via kvp. kinda cool for stuffing data into the registry on windows vms. Might have to get a review on that before the next status meeting.16:39
blackboxsw#link https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742.16:39
blackboxswit looks a bit noisy on the debug front with adding out/err messages for all subp calls, but other than that fairly straight forward.16:39
blackboxswlooks like that's a wrap for today.17:03
blackboxsw#link https://cloud-init.github.io   for meeting minutes17:03
blackboxswsee you next time: 2 weeks from today17:04
blackboxsw#endmeeting17:04
meetingologyMeeting ended Mon Aug  6 17:04:11 2018 UTC.17:04
meetingologyMinutes:        http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-08-06-16.04.moin.txt17:04
blackboxswsmoser: I'm not quite sure how to handle your comments that DataSourceAzure._is_platform_viable should be a separate function in the Azure module. Ultimately, what I want is for get_data to call _is_platform_viable  prior to re-running the private _get_data on a given datasource instance. If we separate it out to only a module function instead of a class method, then we may have to deal with importing the right function18:11
blackboxswper module in the DataSource parent class when running get_data().   I could see wrapping the module function as a classmethod so we have that class method available to us when we are operating on the DataSource.get_data() call of _is_platform_viable. Having the separate module function does ease testability without all the other datasource setup required so I'm +1 on the approach: separate function plus18:11
blackboxswDataSource._is_platform_viable.18:11
blackboxswLong term, I want all datasources to have an is_platform_viable publc method we can call to quick-check DMI/SMBIOS/environment for 'maybe' before attempting to walk metadata services (because that costs more). is_platform_viable would only do the quick sniff/test ds-identify(cloud-id) does and exit False if known not-compatible18:13
blackboxswif we surface that method as a public class method, we can also easily test if via CLI to ensure platform changes didn't break cloud-init python datasource detection18:14
smoserblackboxsw: having all datasources have a 'is_platform_viable' is a reasonable goal for sure.18:37
smoseri was just suggesting that that method is either a @classmethod18:38
smoserand/or it simply (for ease of test) wraps a _is_platform_viable18:38
smoserin the .py file18:38
blackboxsw+1 smoser thanks. so you don't like side-effect in Azure.network_config to remove cpc image netplan yaml. I tend to agree, what since get_data has side-effects, and needs to be run before network_config anyway, why not do maybe_remove_ubuntu_network_config_scripts19:30
blackboxswafter we detect we are on azure19:30
blackboxswwow thinkos.   maybe_remove_ubuntu_network_config_scripts from network_config -> _get_data19:31
smoseris DataSource.activate too late ?19:32
blackboxswchecking,19:32
blackboxswI think that should be good19:33
blackboxswbah wrong, ok can't do it at activate timeframe as we are attempting to generate network config in init-local, ds.activate doesn't happen until init stage.  So, we'd have collisions with cloud-init's netplan from IMDS and /etc/netplan/90-hotplug-azure.yaml21:31
blackboxswwhich we are trying to remove21:31
blackboxswduring network-config generation21:31
blackboxswok I'll move it to _get_data and out of network config at least. But not sure where a better home would be for this call.21:34

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