-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathstatus-2018-03-19.html
More file actions
377 lines (338 loc) · 30.6 KB
/
status-2018-03-19.html
File metadata and controls
377 lines (338 loc) · 30.6 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
<!DOCTYPE html>
<html lang="english">
<head>
<link href='//fonts.googleapis.com/css?family=Source+Sans+Pro:300,400,700,400italic' rel='stylesheet' type='text/css'>
<link rel="stylesheet" type="text/css" href="https://cloud-init.github.io/theme/stylesheet/style.min.css">
<link rel="stylesheet" type="text/css" href="https://cloud-init.github.io/theme/pygments/github.min.css">
<link rel="stylesheet" type="text/css" href="https://cloud-init.github.io/theme/font-awesome/css/font-awesome.min.css">
<link href="https://cloud-init.github.io/feeds/all.atom.xml" type="application/atom+xml" rel="alternate" title="Cloud-init Info Atom">
<link rel="shortcut icon" href="/theme/img/favicon.ico" type="image/x-icon">
<link rel="icon" href="/theme/img/favicon.ico" type="image/x-icon">
<!-- Google Analytics -->
<script type="text/javascript">
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
})(window,document,'script','//www.google-analytics.com/analytics.js','ga');
ga('create', 'UA-50554247-3', 'auto');
ga('send', 'pageview');
</script>
<!-- End Google Analytics -->
<meta charset="utf-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<meta name="HandheldFriendly" content="True" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta name="robots" content="index, follow" />
<!-- Chrome, Firefox OS and Opera -->
<meta name="theme-color" content="#2c001e">
<!-- Windows Phone -->
<meta name="msapplication-navbutton-color" content="#2c001e">
<!-- iOS Safari -->
<meta name="apple-mobile-web-app-capable" content="yes">
<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent">
<!-- Microsoft EDGE -->
<meta name="msapplication-TileColor" content="#2c001e">
<meta name="author" content="chad.smith@canonical.com" />
<meta name="description" content="Meeting information #cloud-init: Cloud-init bi-weekly status meeting, 19 Mar at 16:02 — 17:09 UTC Full logs at [[http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-03-19-16.02.log.html]] Meeting summary Recent Changes The discussion about "Recent Changes" started at 16:05. LINK: http://trello.com/b/hFtWKUn3/daily-cloud-init-curtin …" />
<meta name="keywords" content="">
<meta property="og:site_name" content="Cloud-init Info"/>
<meta property="og:title" content="Cloud-init bi-weekly status"/>
<meta property="og:description" content="Meeting information #cloud-init: Cloud-init bi-weekly status meeting, 19 Mar at 16:02 — 17:09 UTC Full logs at [[http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-03-19-16.02.log.html]] Meeting summary Recent Changes The discussion about "Recent Changes" started at 16:05. LINK: http://trello.com/b/hFtWKUn3/daily-cloud-init-curtin …"/>
<meta property="og:locale" content="en_US"/>
<meta property="og:url" content="https://cloud-init.github.io/status-2018-03-19.html"/>
<meta property="og:type" content="article"/>
<meta property="article:published_time" content="2018-03-19 16:02:00+00:00"/>
<meta property="article:modified_time" content=""/>
<meta property="article:author" content="https://cloud-init.github.io/author/chadsmithcanonicalcom.html">
<meta property="article:section" content="status-meeting-minutes"/>
<meta property="og:image" content="/images/cloud-init-orange.svg">
<title>Cloud-init Info – Cloud-init bi-weekly status</title>
</head>
<body>
<aside>
<div>
<a href="https://cloud-init.github.io">
<img src="/images/cloud-init-orange.svg" alt="Cloud-init" title="Cloud-init">
</a>
<h1><a href="https://cloud-init.github.io">Cloud-init</a></h1>
<p>Make your cloud images be all they can be</p>
<nav>
<ul class="list">
<li><a href="https://cloudinit.readthedocs.org/" target="_blank">Docs</a></li>
<li><a href="https://cloud-init.io" target="_blank">Overview</a></li>
<li><a href="https://cloudinit.readthedocs.io/en/latest/topics/hacking.html" target="_blank">Hacking</a></li>
<li><a href="https://jenkins.ubuntu.com/server/view/cloud-init/" target="_blank">CI builds</a></li>
<li><a href="https://launchpad.net/cloud-init" target="_blank">Code</a></li>
</ul>
</nav>
<ul class="social">
<li><a class="sc-github" href="https://github.com/cloud-init" target="_blank"><i class="fa fa-github"></i></a></li>
<li><a class="sc-wechat" href="https://webchat.freenode.net/?channels=cloud-init" target="_blank"><i class="fa fa-wechat"></i></a></li>
</ul>
</div>
</aside>
<main>
<nav>
<a href="https://cloud-init.github.io">Home</a>
<a href="/archives.html">Archives</a>
<a href="/categories.html">Categories</a>
<a href="/tags.html">Tags</a>
<a href="https://cloud-init.github.io/feeds/all.atom.xml">Atom</a>
</nav>
<article class="single">
<header>
<h1 id="status-2018-03-19">Cloud-init bi-weekly status</h1>
<p>
Posted on Mon 19 March 2018 in <a href="https://cloud-init.github.io/category/status-meeting-minutes.html">status-meeting-minutes</a>
• 11 min read
</p>
</header>
<div>
<h2>Meeting information</h2>
<ul>
<li>#cloud-init: Cloud-init bi-weekly status meeting, 19 Mar at 16:02 — 17:09 UTC</li>
<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-03-19-16.02.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-03-19-16.02.log.html</a>]]</li>
</ul>
<h2>Meeting summary</h2>
<h3>Recent Changes</h3>
<p>The discussion about "Recent Changes" started at 16:05.</p>
<ul>
<li><strong>LINK</strong>: <a href="http://trello.com/b/hFtWKUn3/daily-cloud-init-curtin">http://trello.com/b/hFtWKUn3/daily-cloud-init-curtin</a> </li>
</ul>
<h3>In-progress Development</h3>
<p>The discussion about "In-progress Development" started at 16:12.</p>
<ul>
<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~lp-markusschade/cloud-init/+git/cloud-init">https://code.launchpad.net/~lp-markusschade/cloud-init/+git/cloud-init</a> </li>
<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~lp-markusschade/cloud-init/+git/cloud-init/+merge/338439">https://code.launchpad.net/~lp-markusschade/cloud-init/+git/cloud-init/+merge/338439</a> </li>
<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/341662">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/341662</a> </li>
</ul>
<h3>Office hours (next ~30 mins)</h3>
<p>The discussion about "Office hours (next ~30 mins)" started at 16:43.</p>
<ul>
<li><strong>LINK</strong>: <a href="https://trello.com/c/vD1em9WP/698-jenkins-job-to-run-tox-tip-pylint-weekly-pin-all-lint-versions-otherwise">https://trello.com/c/vD1em9WP/698-jenkins-job-to-run-tox-tip-pylint-weekly-pin-all-lint-versions-otherwise</a> </li>
<li><strong>LINK</strong>: <a href="https://cloud-init.github.io">https://cloud-init.github.io</a> </li>
</ul>
<h2>Vote results</h2>
<h2>Done items</h2>
<ul>
<li>(none)</li>
</ul>
<h2>People present (lines said)</h2>
<ul>
<li>blackboxsw (85)</li>
<li>smoser (57)</li>
<li>stanguturi (16)</li>
<li>ubot5` (8)</li>
<li>ajorg (5)</li>
<li>rharper (5)</li>
<li>dpb1 (4)</li>
<li>meetingology (3)</li>
</ul>
<h2>Full Log</h2>
<p>16:02 <code><blackboxsw></code> #startmeeting Cloud-init bi-weekly status meeting</p>
<p>16:02 <code><meetingology></code> Meeting started Mon Mar 19 16:02:30 2018 UTC. The chair is blackboxsw. Information about MeetBot at <a href="http://wiki.ubuntu.com/meetingology.">http://wiki.ubuntu.com/meetingology.</a></p>
<p>16:02 <code><meetingology></code> </p>
<p>16:02 <code><meetingology></code> Available commands: action commands idea info link nick</p>
<p>16:03 <code><blackboxsw></code> ok, let's kick off this cloud-init bi-weekly meeting. welcome all!</p>
<p>16:04 <code><dpb1></code> o/</p>
<p>16:04 <code><blackboxsw></code> it's been a busy couple weeks for a few of us w/ planning meetings and vacation, but let's see what progress we've made on cloud-init.</p>
<p>16:05 <code><blackboxsw></code> #topic Recent Changes</p>
<p>16:05 <code><dpb1></code> smoser vacation specifically</p>
<p>16:05 <code><blackboxsw></code> hehe. Generally we're tracking high-points of what lands in our trello board</p>
<p>16:05 <code><blackboxsw></code> #link <a href="http://trello.com/b/hFtWKUn3/daily-cloud-init-curtin">http://trello.com/b/hFtWKUn3/daily-cloud-init-curtin</a></p>
<p>16:06 <code><blackboxsw></code> but from changelogs folks have made progress on azure, vmware and FreeBSD deployment targets</p>
<p>16:06 <code><blackboxsw></code> - netplan: render bridge port-priority values (LP: #1735821)</p>
<p>16:06 <code><blackboxsw></code> - net: recognize iscsi root cases without ip= on kernel command line.</p>
<p>16:06 <code><blackboxsw></code> (LP: #1752391)</p>
<p>16:06 <code><blackboxsw></code> - util: Fix subp regression. Allow specifying subp command as a string.</p>
<p>16:06 <code><blackboxsw></code> (LP: #1755965)</p>
<p>16:06 <code><blackboxsw></code> - This commit fixes get_hostname on the AzureDataSource.</p>
<p>16:06 <code><blackboxsw></code> [Douglas Jordan] (LP: #1754495)</p>
<p>16:06 <code><ubot5</code>>` Launchpad bug 1735821 in nplan (Ubuntu Artful) "netplan needs bridge port-priority support" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1735821">https://launchpad.net/bugs/1735821</a></p>
<p>16:06 <code><blackboxsw></code> - shellify: raise TypeError on bad input.</p>
<p>16:06 <code><blackboxsw></code> - FreeBSD: Set hostname to FQDN. [Dominic Schlegel] (LP: #1753499)</p>
<p>16:06 <code><blackboxsw></code> - Make salt minion module work on FreeBSD.</p>
<p>16:06 <code><blackboxsw></code> [Dominic Schlegel] (LP: #1721503)</p>
<p>16:06 <code><ubot5</code>>` Launchpad bug 1752391 in cloud-init "cloud-init does not recognize initramfs provided network config in all cases" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1752391">https://launchpad.net/bugs/1752391</a></p>
<p>16:06 <code><blackboxsw></code> - set_hostname: When present in metadata, set it before network bringup.</p>
<p>16:06 <code><blackboxsw></code> (LP: #1746455) VMWare</p>
<p>16:06 <code><ubot5</code>>` Launchpad bug 1755965 in cloud-init "util.subp regression: no longer accept commands as string" [High,Fix committed] <a href="https://launchpad.net/bugs/1755965">https://launchpad.net/bugs/1755965</a></p>
<p>16:06 <code><blackboxsw></code> - cc_snap: Add new module to install and configure snapd and snap</p>
<p>16:06 <code><blackboxsw></code> packages.</p>
<p>16:06 <code><blackboxsw></code> - doc: fix all warnings issued by 'tox -e doc'</p>
<p>16:06 <code><blackboxsw></code> - tests: Make pylint happy and fix python2.6 uses of assertRaisesRegex.</p>
<p>16:06 <code><ubot5</code>>` Launchpad bug 1755965 in cloud-init "duplicate for #1754495 util.subp regression: no longer accept commands as string" [High,Fix committed] <a href="https://launchpad.net/bugs/1755965">https://launchpad.net/bugs/1755965</a></p>
<p>16:06 <code><blackboxsw></code> - tests: fix run_tree and bddeb</p>
<p>16:06 <code><blackboxsw></code> - tests: Fix some warnings in tests that popped up with newer python.</p>
<p>16:06 <code><ubot5</code>>` Launchpad bug 1753499 in cloud-init "hostname in FreeBSD should prefere FQDN" [Undecided,Fix committed] <a href="https://launchpad.net/bugs/1753499">https://launchpad.net/bugs/1753499</a></p>
<p>16:06 <code><blackboxsw></code> - tests: fix flakes warning for unused variable</p>
<p>16:06 <code><blackboxsw></code> - tests: patch leaked stderr messages from snap unit tests</p>
<p>16:06 <code><ubot5</code>>` Launchpad bug 1721503 in cloud-init "salt module not able to be used on FreeBSD" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1721503">https://launchpad.net/bugs/1721503</a></p>
<p>16:06 <code><blackboxsw></code> - tests: Centralize and re-use skipTest based on json schema presense.</p>
<p>16:06 <code><ubot5</code>>` Launchpad bug 1746455 in cloud-init "cloud-init vSphere cloud provider DHCP unique hostname issue" [High,Fix committed] <a href="https://launchpad.net/bugs/1746455">https://launchpad.net/bugs/1746455</a></p>
<p>16:08 <code><blackboxsw></code> a big thanks to dojordan (Azure) and Dominic Schlegel (FreeBSD) for patching some gaps in support as cloud-init master progresses</p>
<p>16:10 <code><blackboxsw></code> On the ubuntu side of the house we got tip of tree published into Bionic thusday & friday, we are awaiting cloud-image builds which look like they are stale at 03-15-2018. once those builds are published, all clouds should be getting latest cloud-init on Bionic</p>
<p>16:11 <code><blackboxsw></code> I think that's probably it for 'done' work. We have a few things in flight at the moment</p>
<p>16:12 <code><blackboxsw></code> #topic In-progress Development</p>
<p>16:13 <code><blackboxsw></code> Ubuntu is getting a number of new cloud-config modules:</p>
<p>16:13 <code><blackboxsw></code> - new cc_snap module (deprecated cc_snappy and cc_snap_config modules) the ability to install and manage snap package</p>
<p>16:14 <code><blackboxsw></code> - new cc_ubuntu_drivers: support to install 3rd party drivers on install</p>
<p>16:15 <code><blackboxsw></code> - new cc_ubuntu_advantage: manage Ubuntu Advantage subscriptions for services such as Extended Security Mainenance (trusty), canonical livepatch and FIPS PPAs</p>
<p>16:15 <code><blackboxsw></code> these should be landing in the week(s) to come</p>
<p>16:15 <code><blackboxsw></code> and cc_snap landed already</p>
<p>16:17 <code><blackboxsw></code> also there are a couple of branches that we are trying to wrap up for first class chrony support (per rharper, inspired by robjo's work)</p>
<p>16:17 <code><rharper></code> blackboxsw: smoser: on the lander emails, the subject could include the git hash (or branch name); it's currently only in the body;</p>
<p>16:17 <code><smoser></code> rharper: i had suggested to blackboxsw that it should acutally change to <em>not</em> send a subject. so it threads in your email reader with the other MP mails.</p>
<p>16:18 <code><rharper></code> heh</p>
<p>16:18 <code><blackboxsw></code> maybe we can toggle between the two modulus 2 :)</p>
<p>16:18 <code><rharper></code> sorry, didn't meant to disturb the flow</p>
<p>16:19 <code><rharper></code> continue</p>
<p>16:19 <code><blackboxsw></code> yeah, we've also touched a little bit of our code landing automation this last week. powersj also is working on a git lander plugin that we might be able to use to automate landing of approved branches w/ tox test runs</p>
<p>16:19 <code><blackboxsw></code> anything to free up developer time will give us more time for reviews/code</p>
<p>16:19 <code><ajorg></code> should vendor-specific modules be shipped in a separate package?</p>
<p>16:20 <code><smoser></code> vendor specific modules ?</p>
<p>16:20 <code><ajorg></code> ubuntu_advantage</p>
<p>16:22 <code><blackboxsw></code> good question/point. I hand't thought about that separation as a lot of the modules cloud-init delivers support a subset of distros</p>
<p>16:23 <code><blackboxsw></code> each module has a distro attribute defined as to whether or not it will even run</p>
<p>16:23 <code><blackboxsw></code> so we have spacewalk, zypper_repos etc</p>
<p>16:24 <code><smoser></code> and cloud.cfg is rendered based on knowledge of the distro</p>
<p>16:24 <code><smoser></code> so ubuntu_advantage wont even be in the list of config modules</p>
<p>16:24 <code><smoser></code> having a static config module list is WIN in this case (but pain elsewhere)</p>
<p>16:25 <code><smoser></code> at some point whe may have a more dynamic config module list.</p>
<p>16:25 <code><smoser></code> but anyway... at the moment the only cost to non-ubuntu of that module being shipped is bytes on disk.</p>
<p>16:26 <code><blackboxsw></code> if/when we do define that more dynamic config module list, I'd like us also to look at having configurable/separate plugin directories defined for folks providing vendor-specific content.</p>
<p>16:26 <code><ajorg></code> agree that having a more dynamic config module list is prerequisite to being able to parcel out modules to other packages</p>
<p>16:26 <code><blackboxsw></code> so that we don't expect folks to add plugins directly into /usr/lib/python3/dist-packages/cloudinit/config/ for instance</p>
<p>16:26 <code><smoser></code> yeah. at the point when it is dynamic, the module would still declare its support for a list of distros and would be filtered out.</p>
<p>16:29 * ajorg is satisfied</p>
<p>16:30 <code><blackboxsw></code> :). the only other thing I can think of in progress two more datasources softlayer cloud support by smoser and hetzner cloud</p>
<p>16:30 <code><blackboxsw></code> so cloud-init is getting it's grubby hands into a couple of more clouds shortly.</p>
<p>16:31 <code><blackboxsw></code> s/it's/its/</p>
<p>16:31 <code><blackboxsw></code> it's nice to see the adoption continue to grow</p>
<p>16:31 <code><smoser></code> looks like someone followed up on hetzner</p>
<p>16:31 <code><smoser></code> so that hopefully is ready to land</p>
<p>16:31 <code><blackboxsw></code> #link <a href="https://code.launchpad.net/~lp-markusschade/cloud-init/+git/cloud-init">https://code.launchpad.net/~lp-markusschade/cloud-init/+git/cloud-init</a></p>
<p>16:32 <code><blackboxsw></code> rharper: also has a couple of branches to allow cloud-init to work a bit better when rendering netplan configuration</p>
<p>16:33 <code><blackboxsw></code> I <em>think</em> that's all for in-progress development at the moment.</p>
<p>16:33 <code><smoser></code> man we need to fix that pylint thing.</p>
<p>16:33 <code><smoser></code> did you mention ?</p>
<p>16:33 <code><rharper></code> blackboxsw: yeah, I just pushed a fix for v1 global dns entries to get rendered under interfaces without any dns configuration</p>
<p>16:33 <code><blackboxsw></code> Anything else that should be noted by anyone?</p>
<p>16:33 <code><blackboxsw></code> #link <a href="https://code.launchpad.net/~lp-markusschade/cloud-init/+git/cloud-init/+merge/338439">https://code.launchpad.net/~lp-markusschade/cloud-init/+git/cloud-init/+merge/338439</a></p>
<p>16:33 <code><blackboxsw></code> oops</p>
<p>16:34 <code><smoser></code> cloudinit/config/cc_puppet.py:143: [W1505(deprecated-method), handle] Using deprecated method readfp()</p>
<p>16:34 <code><blackboxsw></code> #link <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/341662">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/341662</a></p>
<p>16:34 <code><smoser></code> that needs fixing. it has come to us due to a new version of some of our tox environemnts. we do not fully pin the versions , only the top level packages. Ie, pylint's dependencies changed, but we only pin pylint version.</p>
<p>16:35 <code><blackboxsw></code> yeah how much should we freeze our deps?</p>
<p>16:35 <code><blackboxsw></code> it's kindof annoying to have your branch locally pass ci, and a fresh build of CI deps fail when you try to land</p>
<p>16:36 <code><blackboxsw></code> but I don't really know whether it's worth us 'pinning' everything</p>
<p>16:36 <code><smoser></code> i think pinning everything is generally the best practice for this sort of thing now.</p>
<p>16:37 <code><smoser></code> oh my.</p>
<p>16:37 <code><blackboxsw></code> so if we pin the world, should we also just make it a habit to occasionally tox -e tip-pylint?</p>
<p>16:37 <code><smoser></code> blackboxsw: did you know you accidently fixed that in trunk ?</p>
<p>16:38 <code><blackboxsw></code> smoser: I know I intentionally added a pylint ignore on that to come back and address it today.</p>
<p>16:38 <code><ajorg></code> i tend to believe it's better to stay current and take your punches a few at a time so you don't have a major upset when you have to upgrade.</p>
<p>16:38 <code><smoser></code> oh ko. i see.</p>
<p>16:39 <code><smoser></code> ajorg: well, sor tof. if you have c-i that you want to be green, and consider it bad when it is not, then you dont want dude-on-the-internet to break you</p>
<p>16:40 <code><smoser></code> there is the "good" break, where new upload to pypi identifies some lingering bug</p>
<p>16:40 <code><blackboxsw></code> +1 ajorg, but I'm good (on avoiding a avalanche) if we agree to run tip-pylint target fairy regularly to avoid the landslide</p>
<p>16:40 <code><smoser></code> but also the "bad" break where some upload breaks your c-i for invalid reason.</p>
<p>16:42 <code><smoser></code> one huge advantage to pinning is the ability to re-create things.</p>
<p>16:42 <code><blackboxsw></code> it definitely felt like last week was a lot of c-i breaks for changes unrelated to the code up for review</p>
<p>16:42 <code><smoser></code> ie, if you were looking to it bisect something...</p>
<p>16:42 <code><smoser></code> git bisect</p>
<p>16:43 <code><blackboxsw></code> I should transition to the office hours topic so we can continue discussion</p>
<p>16:43 <code><smoser></code> you can't really do that if trunk from a point in the past does not pass C-I because an external dependency changed.</p>
<p>16:43 <code><smoser></code> sure we can transition to office hours.</p>
<p>16:43 <code><blackboxsw></code> #topic Office hours (next ~30 mins)</p>
<p>16:43 <code><smoser></code> but yeah... i want c-i on tip to not just start failing.</p>
<p>16:44 <code><stanguturi></code> @blackboxsw, I have couple of requests. First, <a href="https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1724128">https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1724128</a> discussed this in last meeting as well. Any help is greatly appreciated</p>
<p>16:44 <code><ubot5</code>>` Ubuntu bug 1724128 in open-vm-tools (Ubuntu) "Need a Success / Failure notification mechanism when cloud-init finishes." [Undecided,New]</p>
<p>16:44 <code><blackboxsw></code> that's fair. smoser can we maybe add a jenkins job to run tip-pylint then weekly. So, we don't have a huge backlog of lint failures against tip?</p>
<p>16:45 <code><smoser></code> blackboxsw: i'mi fine with that... thats why we added the tip-* targets. so it was easy enough to keep current.</p>
<p>16:45 <code><blackboxsw></code> +1 smoser I'll put a card up for that</p>
<p>16:46 <code><smoser></code> stanguturi: your suggestion there is not a bad idea at all.</p>
<p>16:46 <code><blackboxsw></code> #link <a href="https://trello.com/c/vD1em9WP/698-jenkins-job-to-run-tox-tip-pylint-weekly-pin-all-lint-versions-otherwise">https://trello.com/c/vD1em9WP/698-jenkins-job-to-run-tox-tip-pylint-weekly-pin-all-lint-versions-otherwise</a></p>
<p>16:46 <code><smoser></code> the desire to have cloud-init tell the platform/datasource that it failed or succeeded is valid.</p>
<p>16:47 <code><smoser></code> with MAAS, that his done via reporting</p>
<p>16:47 <code><blackboxsw></code> stanguturi: hiya. I think we talked after that meeting about trying to allow the datasource to subscribe to a callback when cloud-init exists</p>
<p>16:47 <code><blackboxsw></code> stanguturi: hiya. I think we talked after that meeting about trying to allow the datasource to subscribe to a callback when cloud-init exits</p>
<p>16:47 <code><smoser></code> cloud-init reports status and results via a Reporter.</p>
<p>16:47 <code><smoser></code> dojordan (i think) had also put up a request for a reproter module on azure.</p>
<p>16:47 <code><smoser></code> so we <em>do</em> kind of have the function you're after in place.</p>
<p>16:48 <code><stanguturi></code> smoser: ok. Any inputs / examples of using it will be really great.</p>
<p>16:50 <code><smoser></code> stanguturi: well, the reporter interface is pretty simple. you can cloudinit/reporting/handlers.py</p>
<p>16:51 <code><smoser></code> blackboxsw: <a href="http://paste.ubuntu.com/p/6KjDX8WHQH/">http://paste.ubuntu.com/p/6KjDX8WHQH/</a></p>
<p>16:51 <code><smoser></code> did you intend boht of those changes ?</p>
<p>16:51 <code><stanguturi></code> smoser: ok. Then do I need to write a new handler for our DataSource?</p>
<p>16:52 <code><smoser></code> stanguturi: well you write a reporting Handler, ankd then either system confi or optionally datasource config would turn that reporter on.</p>
<p>16:52 <code><blackboxsw></code> wow smoser, no</p>
<p>16:52 <code><blackboxsw></code> wow, ok, I'll put up a branch to fix that</p>
<p>16:52 <code><stanguturi></code> smoser: ok. Will work on that.</p>
<p>16:52 <code><smoser></code> ok.</p>
<p>16:53 <code><stanguturi></code> I have another quick request about <a href="https://code.launchpad.net/~sankaraditya/cloud-init/+git/cloud-init/+ref/set_hwclock_module">https://code.launchpad.net/~sankaraditya/cloud-init/+git/cloud-init/+ref/set_hwclock_module</a></p>
<p>16:53 <code><smoser></code> stanguturi: do you find this is actually needed ?</p>
<p>16:53 <code><smoser></code> to my knowledge the only time anyone would ever set their hardware clock to something other than UTC would be dual booting with windows.</p>
<p>16:54 <code><smoser></code> which i can't seem to believe is all that a common situation in VMs</p>
<p>16:54 <code><stanguturi></code> smoser: Yeah. We need this for 'VMware guest customization workflow'.</p>
<p>16:54 <code><dpb1></code> smoser: oh man, I hope not</p>
<p>16:54 <code><stanguturi></code> smoser: if you think, this is not worth for the base cloud-init modules, I can modify to do this change in our datasource specific modules.</p>
<p>16:54 <code><smoser></code> stanguturi: does it actually solve a <em>current</em> problem for you ?</p>
<p>16:55 <code><stanguturi></code> smoser: For 'VMware managed VMs', customers can specify in the specification file if they want UTC or localtime for the hardware clock.</p>
<p>16:55 <code><smoser></code> or one that originally came in from a decade ago</p>
<p>16:55 <code><stanguturi></code> smoser: Our existing customization (non cloud-init) engine does it. If we want to move to cloud-init, we want to port all our changes from our engine to our datasource in cloud-init.</p>
<p>16:55 <code><smoser></code> hm... so my sugestion is really to stop allowing that :)</p>
<p>16:56 <code><stanguturi></code> smoser: Oh ok. Can you please add a comment to that merge request just for the record.</p>
<p>16:56 <code><smoser></code> i very well could be wrong</p>
<p>16:56 <code><smoser></code> but the only time that i ever had to deal with this was when dual booting</p>
<p>16:56 <code><smoser></code> with windows specifically</p>
<p>16:57 <code><stanguturi></code> smoser: ok.</p>
<p>16:57 <code><smoser></code> am i wrong there ?</p>
<p>16:57 <code><smoser></code> i really <em>could</em> be.</p>
<p>16:58 <code><stanguturi></code> smoser: I can discuss this within our team. But to be on par with our existing engine, want to port the changes.</p>
<p>16:58 <code><smoser></code> and even if you get it wrong, generally speaking you havhe some sort of ntpdate or ntp that will fix your system clock anyway.</p>
<p>16:58 <code><smoser></code> stanguturi: yeah. i understand that.</p>
<p>16:58 <code><stanguturi></code> I have another request. For Ubuntu 18.04, we are planning to set 'disable_vmware_customization' flag to False by default in /etc/cloud/cloud.cfg file.</p>
<p>16:59 <code><stanguturi></code> Want to know your opinion, shall we set it in cloud-init installation phase or request Ubuntu maintainers to set it in 18.04</p>
<p>17:00 <code><stanguturi></code> smoser: And when is the cloud-init 18.2 scheduled for release? 3/22?</p>
<p>17:01 <code><blackboxsw></code> probably a good time for us to bring that up</p>
<p>17:01 <code><smoser></code> yeah. whoops.</p>
<p>17:01 <code><smoser></code> :)</p>
<p>17:01 <code><smoser></code> 18.2 is scheduled for 3/22 (thursday)</p>
<p>17:02 <code><blackboxsw></code> We cloud-init 18.2 have it scheduled for an arbitrary 3/22 date, we'd like to slip that out to next week Tuesday 3/27</p>
<p>17:02 <code><smoser></code> but amoung our internall team we decided to push that to 3/27</p>
<p>17:02 <code><stanguturi></code> smoser: ok. Thanks for the update.</p>
<p>17:02 <code><blackboxsw></code> there a a few in flight branches, azure, softlayer etc that we'd like to get in and get tested before 18.2</p>
<p>17:02 <code><smoser></code> we will send an email today or tomrrow witih "pending release" like subject like we've done before.</p>
<p>17:03 <code><blackboxsw></code> dpb1: others any objections to cutting the 18.2 release on Tuesday 3/27?</p>
<p>17:03 <code><dpb1></code> none</p>
<p>17:04 * blackboxsw adds the upcoming date to the topic</p>
<p>17:05 <code><blackboxsw></code> ... ok, folks interested in discussing today?</p>
<p>17:08 <code><blackboxsw></code> #link <a href="https://cloud-init.github.io">https://cloud-init.github.io</a></p>
<p>17:09 <code><blackboxsw></code> The above link will have our captured logs for this meeting.</p>
<p>17:09 <code><blackboxsw></code> thanks again for tuning in</p>
<p>17:09 <code><blackboxsw></code> #endmeeting</p>
<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>
</div>
<div class="tag-cloud">
<p>
</p>
</div>
<div class="addthis_relatedposts_inline">
</article>
<footer>
<p>© </p>
<p>Powered by <a href="http://getpelican.com" target="_blank">Pelican</a> - <a href="https://github.com/alexandrevicenzi/flex" target="_blank">Flex</a> theme by <a href="http://alexandrevicenzi.com" target="_blank">Alexandre Vicenzi</a></p> </footer>
</main>
<script type="application/ld+json">
{
"@context" : "http://schema.org",
"@type" : "Blog",
"name": " Cloud-init Info ",
"url" : "https://cloud-init.github.io",
"image": "/images/cloud-init-orange.svg",
"description": "Cloud-init project updates and general information"
}
</script>
</body>
</html>