-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathstatus-2019-10-29.html
393 lines (354 loc) · 35.4 KB
/
status-2019-10-29.html
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
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
<!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="[email protected]" />
<meta name="description" content="Meeting information #cloud-init: Cloud-init bi-weekly status, 29 Oct at 16:20 — 17:38 UTC Full logs at [[http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-10-29-16.20.log.html]] Meeting summary Previous Actions The discussion about "Previous Actions" started at 16:26. LINK: https://cloud-init.github.io/status-2019-10-08.html#status-2019-10-08 …" />
<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, 29 Oct at 16:20 — 17:38 UTC Full logs at [[http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-10-29-16.20.log.html]] Meeting summary Previous Actions The discussion about "Previous Actions" started at 16:26. LINK: https://cloud-init.github.io/status-2019-10-08.html#status-2019-10-08 …"/>
<meta property="og:locale" content="en_US"/>
<meta property="og:url" content="https://cloud-init.github.io/status-2019-10-29.html"/>
<meta property="og:type" content="article"/>
<meta property="article:published_time" content="2019-10-29 16:20: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-2019-10-29">Cloud-init bi-weekly status</h1>
<p>
Posted on Tue 29 October 2019 in <a href="https://cloud-init.github.io/category/status-meeting-minutes.html">status-meeting-minutes</a>
• 12 min read
</p>
</header>
<div>
<h2>Meeting information</h2>
<ul>
<li>#cloud-init: Cloud-init bi-weekly status, 29 Oct at 16:20 — 17:38 UTC</li>
<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-10-29-16.20.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-10-29-16.20.log.html</a>]]</li>
</ul>
<h2>Meeting summary</h2>
<h3>Previous Actions</h3>
<p>The discussion about "Previous Actions" started at 16:26.</p>
<ul>
<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-10-08.html#status-2019-10-08">https://cloud-init.github.io/status-2019-10-08.html#status-2019-10-08</a> </li>
<li><strong>LINK</strong>: <a href="https://lists.launchpad.net/cloud-init/msg00229.html">https://lists.launchpad.net/cloud-init/msg00229.html</a> </li>
</ul>
<h3>Recent Changes</h3>
<p>The discussion about "Recent Changes" started at 16:36.</p>
<h3>In-progress Development</h3>
<p>The discussion about "In-progress Development" started at 16:41.</p>
<ul>
<li><strong>LINK</strong>: <a href="https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin">https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin</a> </li>
<li><strong>LINK</strong>: <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a> </li>
<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368507">https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368507</a> </li>
<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/365641">https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/365641</a> </li>
</ul>
<h3>Community Charter</h3>
<p>The discussion about "Community Charter" started at 16:49.</p>
<ul>
<li><strong>LINK</strong>: <a href="https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin">https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin</a> </li>
</ul>
<h3>Upcoming meetings</h3>
<p>The discussion about "Upcoming meetings" started at 16:57.</p>
<h3>Upcoming Releases</h3>
<p>The discussion about "Upcoming Releases" started at 16:58.</p>
<ul>
<li><strong>LINK</strong>: <a href="https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/">https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/</a> </li>
</ul>
<h3>Office Hours (next ~30 mins)</h3>
<p>The discussion about "Office Hours (next ~30 mins)" started at 17:00.</p>
<ul>
<li><strong>ACTION</strong>: cloud-init upstream discuss where/how/if to host documentation supported cloud-init versions for debian/suse/redhat/ubuntu/freebsd etc.</li>
<li><strong>ACTION</strong>: cloud-init upstream discuss where/how/if to host documentation on supported and planned schedule for cloud-init versions for debian/suse/redhat/ubuntu/freebsd etc.</li>
<li><strong>LINK</strong>: <a href="https://github.com/cloud-init/ubuntu-sru/blob/master/manual/ec2-sru-19.2.36.ubuntu2.txt">https://github.com/cloud-init/ubuntu-sru/blob/master/manual/ec2-sru-19.2.36.ubuntu2.txt</a> </li>
<li><strong>ACTION</strong>: mailing list update to cloud-init community about procedure/timeline for migration to github</li>
</ul>
<h2>Vote results</h2>
<h2>Done items</h2>
<ul>
<li>(none)</li>
</ul>
<h2>People present (lines said)</h2>
<ul>
<li>blackboxsw (130)</li>
<li>tribaal (34)</li>
<li>meetingology (8)</li>
<li>ubot5 (7)</li>
<li>Odd_Bloke (2)</li>
<li>chillysurfer (1)</li>
<li>rharper (0)</li>
</ul>
<h2>Full Log</h2>
<p>16:20 <code><blackboxsw></code> #startmeeting Cloud-init bi-weekly status</p>
<p>16:20 <code><meetingology></code> Meeting started Tue Oct 29 16:20:09 2019 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:20 <code><meetingology></code> </p>
<p>16:20 <code><meetingology></code> Available commands: action commands idea info link nick</p>
<p>16:20 <code><blackboxsw></code> Boo! Welcome to the Halloween edition of cloud-init bi-weekly status meeting</p>
<p>16:20 <code><blackboxsw></code> #chair rharper</p>
<p>16:20 <code><meetingology></code> Current chairs: blackboxsw rharper</p>
<p>16:20 <code><blackboxsw></code> #chair Odd_Bloke</p>
<p>16:20 <code><meetingology></code> Current chairs: Odd_Bloke blackboxsw rharper</p>
<p>16:21 <code><blackboxsw></code> cloud-init upstream uses this meeting as a platform for community updates, feature/bug discussions, and an opportunity to get some extra input on current development.</p>
<p>16:21 <code><blackboxsw></code> shamefully I think we wall missed last week's status. So let's celebrate today instead to catch up with where cloud-init development is headed</p>
<p>16:22 <code><blackboxsw></code> So that we don't forget, let's set the topic for next status meeting.</p>
<p>16:22 <code><blackboxsw></code> Odd_Bloke: rharper does 11/12 look good?</p>
<p>16:22 <code><blackboxsw></code> as in, no holidays etc?</p>
<p>16:25 <code><blackboxsw></code> ok topic updated. Any concerns we can change it and send out an email to the mailing list</p>
<p>16:26 <code><blackboxsw></code> Feel free to interject at any time. Our typical format is the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Upcoming Meetings, Office Hours (~30 mins).</p>
<p>16:26 <code><blackboxsw></code> #topic Previous Actions</p>
<p>16:26 <code><blackboxsw></code> I have three actions from last meeting</p>
<p>16:26 <code><blackboxsw></code> #link <a href="https://cloud-init.github.io/status-2019-10-08.html#status-2019-10-08">https://cloud-init.github.io/status-2019-10-08.html#status-2019-10-08</a></p>
<p>16:28 * blackboxsw blackboxsw verify cpc image builds are unpaused/unblocked for Azure (we were able to confirm the the CPC clound image builds for Azure were on time for the two cloud-init SRUs and worked that communication side-channel with Microsoft.</p>
<p>16:28 <code><blackboxsw></code> We also established a point of contact via email for continued cloud image status updates</p>
<p>16:29 * blackboxsw cloud-init upstream review <a href="https://code.launchpad.net/~ahosmanmsft/cloud-init/+git/cloud-init/+merge/372957">https://code.launchpad.net/~ahosmanmsft/cloud-init/+git/cloud-init/+merge/372957</a> . This branch is getting a bit of review work. It's looking pretty good and I expect we'll land it this week or next (Azure continuous integration testing support) Thanks ahosmanMSFT</p>
<p>16:30 <code><chillysurfer></code> nice, good work ahosmanMSFT</p>
<p>16:30 * blackboxsw upstream cloud-init email about 19.3 release date . rharper just sent out a message to announce the 19.3 upstream release date. on 11/05. <a href="https://lists.launchpad.net/cloud-init/msg00229.html">https://lists.launchpad.net/cloud-init/msg00229.html</a></p>
<p>16:30 <code><blackboxsw></code> #link <a href="https://lists.launchpad.net/cloud-init/msg00229.html">https://lists.launchpad.net/cloud-init/msg00229.html</a></p>
<p>16:30 <code><blackboxsw></code> thx chillysurfer :)</p>
<p>16:31 <code><blackboxsw></code> anyone with vested interested in getting branches into the 19.3 upstream release please ping us in this channel or the mailinglist to get branches reviewed and landed by Tuesday of next week</p>
<p>16:31 <code><blackboxsw></code> As a note, we are planning a 19.4 release by end of year too, so ~6 weeks later we can get branches into 19.4 that miss the 19.3 release date</p>
<p>16:33 <code><blackboxsw></code> and for those that aren't aware cloud-init's upstream releases generally are not feature-based but time based. Our goal is 4 time-based releases per year having the versioning schema <code><YEAR></code>.<code><minor_release_number></code> where minor_release_number will be [1-4]</p>
<p>16:34 <code><blackboxsw></code> if there are significant features that are near completion at a given timed release we will try our best to get those features/fixes vetted and landed.</p>
<p>16:35 <code><blackboxsw></code> shortly after each upstream release, we will publish that cloud-init version to the Ubuntu devel release (codenamed named Focal Fossa) our copr repos and SRU into Xenial, Bionic and Eoan.</p>
<p>16:35 <code><blackboxsw></code> ok long-winded. But I think that was our actions from last cloud-init status meeting.</p>
<p>16:35 <code><blackboxsw></code> next topic</p>
<p>16:36 <code><blackboxsw></code> #topic Recent Changes</p>
<p>16:37 <code><blackboxsw></code> The following branches have landed in tip since last meeting: via git log --since 2019-10-08</p>
<p>16:37 <code><blackboxsw></code> - net/netplan: use ipv6-mtu key for specifying ipv6 mtu values</p>
<p>16:37 <code><blackboxsw></code> - Fix usages of yaml, and move yaml_dump to safeyaml.dumps. (LP: #1849640)</p>
<p>16:37 <code><blackboxsw></code> - exoscale: Increase url_max_wait to 120s. [Chris Glass]</p>
<p>16:37 <code><blackboxsw></code> - net/sysconfig: fix available check on SUSE distros</p>
<p>16:37 <code><blackboxsw></code> [Robert Schweikert] (LP: #1849378)</p>
<p>16:37 <code><blackboxsw></code> - docs: Fix incorrect Azure IMDS IP address [Joshua Powers] (LP: #1849508)</p>
<p>16:37 <code><blackboxsw></code> - introduce .travis.yml</p>
<p>16:37 <code><ubot5></code> Launchpad bug 1849640 in cloud-init "security scan reported insecure yaml load method usage in latest cloud-init code" [Undecided,Fix committed] <a href="https://launchpad.net/bugs/1849640">https://launchpad.net/bugs/1849640</a></p>
<p>16:37 <code><blackboxsw></code> - net: enable infiniband support in eni and sysconfig renderers</p>
<p>16:37 <code><blackboxsw></code> [Darren Birkett] (LP: #1847114)</p>
<p>16:37 <code><ubot5></code> Launchpad bug 1849378 in cloud-init "sysconfig renderer not detected on SLE distros" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1849378">https://launchpad.net/bugs/1849378</a></p>
<p>16:37 <code><blackboxsw></code> - guestcust_util: handle special characters in config file [Xiaofeng Wang]</p>
<p>16:37 <code><blackboxsw></code> - fix some more typos in comments [Dominic Schlegel]</p>
<p>16:37 <code><ubot5></code> Launchpad bug 1849508 in cloud-init "Azure IMDS documentation wrong about IP address" [High,Fix committed] <a href="https://launchpad.net/bugs/1849508">https://launchpad.net/bugs/1849508</a></p>
<p>16:37 <code><blackboxsw></code> - replace any deprecated log.warn with log.warning</p>
<p>16:37 <code><blackboxsw></code> [Dominic Schlegel] (LP: #1508442)</p>
<p>16:37 <code><blackboxsw></code> - net: handle openstack dhcpv6-stateless configuration</p>
<p>16:37 <code><blackboxsw></code> [Harald Jensås] (LP: #1847517)</p>
<p>16:37 <code><ubot5></code> Launchpad bug 1847114 in cloud-init "Infiniband network devices not configured correctly on Ubuntu" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1847114">https://launchpad.net/bugs/1847114</a></p>
<p>16:37 <code><blackboxsw></code> - Add .venv/ to .gitignore [Dominic Schlegel]</p>
<p>16:37 <code><blackboxsw></code> - Small typo fixes in code comments. [Dominic Schlegel]</p>
<p>16:37 <code><blackboxsw></code> - cloud_test/lxd: Retry container delete a few times</p>
<p>16:37 <code><blackboxsw></code> - Add Support for e24cloud to Ec2 datasource. (LP: #1696476)</p>
<p>16:37 <code><ubot5></code> Launchpad bug 1508442 in python-watcherclient "LOG.warn is deprecated" [Low,In progress] <a href="https://launchpad.net/bugs/1508442">https://launchpad.net/bugs/1508442</a></p>
<p>16:37 <code><ubot5></code> Launchpad bug 1847517 in cloud-init "cloudinit/net/sysconfig.py write incorrect config for dhcp-stateless openstack subnets" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1847517">https://launchpad.net/bugs/1847517</a></p>
<p>16:37 <code><ubot5></code> Launchpad bug 1696476 in cloud-init "Identification of e24cloud platform as using Ec2 datasource" [Low,Fix committed] <a href="https://launchpad.net/bugs/1696476">https://launchpad.net/bugs/1696476</a></p>
<p>16:39 <code><blackboxsw></code> some good incremental improvements on SuSE, FreeBSD,Ubuntu Azure, Ec2, OpenStack and Exoscale</p>
<p>16:40 <code><blackboxsw></code> Thanks Dominic, Robert, XiaoFeng, Harald and Darren and Scott for the contibutions this round!</p>
<p>16:41 <code><blackboxsw></code> #topic In-progress Development</p>
<p>16:41 <code><blackboxsw></code> #link <a href="https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin">https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin</a></p>
<p>16:42 <code><blackboxsw></code> We keep track of most of cloud-init's development efforts on the cloud-init and curtin trello board above.</p>
<p>16:43 <code><blackboxsw></code> And the active review queue for cloud-init is a good representation of what should land shortly.</p>
<p>16:43 <code><blackboxsw></code> #link <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a></p>
<p>16:44 <code><blackboxsw></code> The following work-streams are currently in progress:</p>
<p>16:44 <code><blackboxsw></code> - CI for Azure (thanks ahosmanMSFT)</p>
<p>16:44 <code><blackboxsw></code> - Openstack networking v2 support (which allows openstack to talk v2 network config 'netplan' )</p>
<p>16:45 <code><blackboxsw></code> - Azure async disk mounts</p>
<p>16:45 <code><blackboxsw></code> - cloud-init boot performance improvements</p>
<p>16:46 <code><blackboxsw></code> As features related to those streams make progress we'll be updating the trello board and dragging cards to the done lane</p>
<p>16:47 <code><blackboxsw></code> There are also a number of branches for FreeBSD support up that we need to shepherd and merge I think</p>
<p>16:48 <code><blackboxsw></code> #link <a href="https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368507">https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368507</a></p>
<p>16:48 <code><blackboxsw></code> #link <a href="https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/365641">https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/365641</a></p>
<p>16:48 <code><blackboxsw></code> We'll be able to review some of the outstanding branches during Office hours today</p>
<p>16:49 <code><blackboxsw></code> #topic Community Charter</p>
<p>16:50 <code><blackboxsw></code> This point in the meeting is essentially an open reminder of the ongoing community charter work and low hanging fruit that everyone is invited to participate in.</p>
<p>16:51 <code><blackboxsw></code> We has a list of tasks/features and bugs that are considered low-hanging-fruit and highly decoupled work items that anyone is welcome to grab. They are listed in the "Community low hanging fruit" column on our trello board</p>
<p>16:51 <code><blackboxsw></code> #link <a href="https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin">https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin</a></p>
<p>16:52 <code><blackboxsw></code> Our current community goal is to scrub, update and correct all datasource docs seen @ <a href="https://cloudinit.readthedocs.io/en/latest/topics/datasources.html">https://cloudinit.readthedocs.io/en/latest/topics/datasources.html</a></p>
<p>16:52 <code><tribaal></code> That's nice!</p>
<p>16:52 <code><blackboxsw></code> all help is appreciated especially from the datasource owners</p>
<p>16:52 <code><blackboxsw></code> \o tribaal.</p>
<p>16:52 <code><tribaal></code> o/</p>
<p>16:53 <code><tribaal></code> sorry, I'm following along, didn't mean to interrupt</p>
<p>16:53 <code><blackboxsw></code> additionally there is a really long tail of work needed to update each cloud-init config module (cloudinit/config/cc_*py) with a json schema definition.</p>
<p>16:55 <code><blackboxsw></code> There are around 50 modules that would need a jsonschema definition so that we can promote our <code>cloud-init devel schema</code> command to it can properly vet any #cloud-config a user provides to annotate user errors</p>
<p>16:55 <code><blackboxsw></code> any help grabbing individualy config modules and adding that would really add value to cloud-init to help users solve their own errors as invalid #cloud-config is one of our highest frequency issues</p>
<p>16:56 <code><blackboxsw></code> example <a href="https://trello.com/c/NENad4m3/1172-schema-add-initial-schema-definition-for-ccpowerstatechange">https://trello.com/c/NENad4m3/1172-schema-add-initial-schema-definition-for-ccpowerstatechange</a></p>
<p>16:56 <code><blackboxsw></code> no worries, interruptions welcome</p>
<p>16:56 <code><blackboxsw></code> think that about wraps up community charter.</p>
<p>16:56 <code><blackboxsw></code> two to topics to go</p>
<p>16:57 <code><blackboxsw></code> #topic Upcoming meetings</p>
<p>16:57 <code><blackboxsw></code> I already updated the topic. 2 weeks from today 11/05 10:15 utc cloud-init status. We'll be here; feel free to drop in</p>
<p>16:58 <code><blackboxsw></code> #topic Upcoming Releases</p>
<p>16:59 <code><blackboxsw></code> Again cloud-init upstream 19.3 scheduled to be cut next Tuesday 11/05 at EOD. Raise awareness in #cloud-init IRC channel or on the mailing list for bugs and feature branches that need attention prior to cutting the release</p>
<p>16:59 <code><blackboxsw></code> Immediately after release, we'll publish to Ubuntu's devel release Focal Fossa and our copr repo</p>
<p>16:59 <code><tribaal></code> nice! this answers one of the questions I had coming in today :)</p>
<p>16:59 <code><blackboxsw></code> #link <a href="https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/">https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/</a></p>
<p>16:59 <code><blackboxsw></code> good deal tribaal</p>
<p>17:00 <code><blackboxsw></code> and again, upstream will schedulae 19.4 release probably ~6 weeks after 19.3 so not long to wait if folks miss 19.3</p>
<p>17:00 <code><blackboxsw></code> <em>schedule</em> even</p>
<p>17:00 <code><blackboxsw></code> #topic Office Hours (next ~30 mins)</p>
<p>17:01 <code><blackboxsw></code> bring your bugs, discussions, features, concerns here about cloud-init life the universe and everything. upstream will spend this time actively grooming the review queue to see if we can't unblock developers</p>
<p>17:02 <code><tribaal></code> blackboxsw: I suspect the plan for y'all is to SRU 19.3 into the various Ubuntues after it lands in focal?</p>
<p>17:03 <code><tribaal></code> my latest bugfix, although small, impacts one of our customers so I'd like to give them a heads up in that direction</p>
<p>17:03 <code><blackboxsw></code> tribaal: yep sorry, I mentioned earlier, but should have mentioned in the last topic</p>
<p>17:03 <code><tribaal></code> no worries</p>
<p>17:03 <code><tribaal></code> it's the logical follow-up to a release - so it was surely implied</p>
<p>17:04 <code><blackboxsw></code> SRU will be scheduled shortly after 19.3 upstream cut I presume. We prefer to keep time between SRUs smaller to make the verification more manageable</p>
<p>17:04 <code><tribaal></code> blackboxsw: do you know how/when cloud-init lands in other distros, as a matter of curiosity?</p>
<p>17:04 <code><blackboxsw></code> I think now that Ubuntu Eoan is released and post-release dust is settling we'll have bandwidth to cover that</p>
<p>17:05 <code><blackboxsw></code> tribaal: robjo knows for SLES. otubo (hrm not here today) is managing RHEL/CentOS release schedules</p>
<p>17:06 <code><blackboxsw></code> and debian is trying to shore up to 19.X I believe.</p>
<p>17:06 <code><tribaal></code> ack</p>
<p>17:06 <code><blackboxsw></code> but I think other distros are delayed (for good reasons: testing/validation/stability/etc).</p>
<p>17:07 <code><tribaal></code> sure, that would make sense</p>
<p>17:07 <code><tribaal></code> more QA is good :)</p>
<p>17:07 * blackboxsw finds myself wanting a current support matrix on cloudinit.readthedocs.io</p>
<p>17:07 <code><blackboxsw></code> or somewhere</p>
<p>17:07 <code><tribaal></code> that would be incredibly useful to us :)</p>
<p>17:08 <code><blackboxsw></code> agreed. Maybe we can take an action to at least discuss what that would look like (and where to host it)</p>
<p>17:08 <code><tribaal></code> tracking where and when our new datasource is available is a bit of a mystery right now :)</p>
<p>17:08 <code><tribaal></code> (except for Ubuntus)</p>
<p>17:09 <code><blackboxsw></code> #action cloud-init upstream discuss where/how/if to host documentation supported cloud-init versions for debian/suse/redhat/ubuntu/freebsd etc.</p>
<p>17:09 * meetingology cloud-init upstream discuss where/how/if to host documentation supported cloud-init versions for debian/suse/redhat/ubuntu/freebsd etc.</p>
<p>17:09 <code><tribaal></code> blackboxsw: another question since I have the mic: would it be useful to you to add us to your CI pipeline?</p>
<p>17:09 <code><blackboxsw></code> we can come back with some kindof answer for that question (as I end up doing more work like lxc launch distroX) frequently to try to see</p>
<p>17:11 <code><tribaal></code> blackboxsw: cool - but that's more a measure rather than an expected date right? so it wouldn't help our marketing people to plan blog posts for instance (which is why I'm asking this in the first place - we have some comms ready to go around a feature that requires the new datasource)</p>
<p>17:11 <code><blackboxsw></code> tribaal: I think it would be useful to extend our cloudinit/tests/cloud_tests to allow us to manually kick off exoscale runs during SRU validation. Especially if you are finding that our upstream changes are breaking your platform</p>
<p>17:12 <code><blackboxsw></code> tribaal: yeah let me restate the action then</p>
<p>17:12 <code><blackboxsw></code> #action cloud-init upstream discuss where/how/if to host documentation on supported and planned schedule for cloud-init versions for debian/suse/redhat/ubuntu/freebsd etc.</p>
<p>17:12 * meetingology cloud-init upstream discuss where/how/if to host documentation on supported and planned schedule for cloud-init versions for debian/suse/redhat/ubuntu/freebsd etc.</p>
<p>17:12 <code><blackboxsw></code> per scheduling we at least could start filling in some gaps there on cloud-init planned distro releases</p>
<p>17:13 <code><tribaal></code> blackboxsw: so, you're basically never breaking our platform - clearly :) But being part of the SRU validation would be good maybe. I don't know how much work that is however (I don't know what I'm asking).</p>
<p>17:13 <code><tribaal></code> is that something we can do ourselves?</p>
<p>17:13 <code><tribaal></code> (code wise at least)</p>
<p>17:14 <code><blackboxsw></code> tribaal: codewise, if you are talking about manual tests, we generally run something like the following:</p>
<p>17:14 <code><blackboxsw></code> #link <a href="https://github.com/cloud-init/ubuntu-sru/blob/master/manual/ec2-sru-19.2.36.ubuntu2.txt">https://github.com/cloud-init/ubuntu-sru/blob/master/manual/ec2-sru-19.2.36.ubuntu2.txt</a></p>
<p>17:15 <code><blackboxsw></code> if you wanted to write up an example manual sru test and propose it to <a href="https://github.com/cloud-init/ubuntu-sru/">https://github.com/cloud-init/ubuntu-sru/</a></p>
<p>17:15 <code><blackboxsw></code> you could follow the examples in <a href="https://github.com/cloud-init/ubuntu-sru/blob/master/manual/ec2-sru-19.2.36.ubuntu2.txt">https://github.com/cloud-init/ubuntu-sru/blob/master/manual/ec2-sru-19.2.36.ubuntu2.txt</a></p>
<p>17:15 <code><blackboxsw></code> oops wrong paste</p>
<p>17:15 <code><blackboxsw></code> you could follow the examples in : <a href="https://github.com/cloud-init/ubuntu-sru/tree/master/sru-templates/manual">https://github.com/cloud-init/ubuntu-sru/tree/master/sru-templates/manual</a></p>
<p>17:16 <code><tribaal></code> oh, I see</p>
<p>17:16 <code><tribaal></code> so thankfully it's only manual in the "manually run a script" sense :)</p>
<p>17:16 <code><blackboxsw></code> and create one for exoscale. that's lowest hanging fruit I think. that'd increase chances of including a manual test in the SRU process. but, we might have to ping you for a recommendation on who could run that on our behalf</p>
<p>17:17 <code><tribaal></code> yes, that would work (myself, and a handful of colleagues would be happy to I guess)</p>
<p>17:17 <code><blackboxsw></code> that's lowest hanging fruit. next step up would be to add a platform definition that can automatically drive Exoscale like ahosmanMSFT has for Azure in progress at <a href="https://code.launchpad.net/~ahosmanmsft/cloud-init/+git/cloud-init/+merge/372957">https://code.launchpad.net/~ahosmanmsft/cloud-init/+git/cloud-init/+merge/372957</a></p>
<p>17:18 <code><blackboxsw></code> having the cloud_tests platform definition would allow us our you to more easily extend a jenkins CI job to drive the cloud tests</p>
<p>17:19 <code><tribaal></code> ah nice, that makes sense</p>
<p>17:19 <code><blackboxsw></code> tribaal: the manual SRU verification script writing really helps (but is not mandatory) prior to extending tests/cloud_tests. having a manual script helps codify what we really might need to do to fully support a platform in tests/cloud_tests.</p>
<p>17:20 <code><tribaal></code> yeah that sounds like a good first step, and we can expand later on if/when needed</p>
<p>17:24 <code><blackboxsw></code> +1 tribaal</p>
<p>17:24 <code><blackboxsw></code> btw good deal that you were able to run into Odd_Bloke on your travels. Always good to see a familiar face</p>
<p>17:24 <code><tribaal></code> yeah that was a crazy coincidence</p>
<p>17:25 <code><tribaal></code> my brother got married in Odd_Bloke 's backyard :)</p>
<p>17:25 <code><tribaal></code> I wish we could do cross-company colocated sprints :P</p>
<p>17:26 <code><blackboxsw></code> heh, I think we can call those #cloud-init-summits :)</p>
<p>17:26 <code><tribaal></code> ohhh yeah :)</p>
<p>17:26 <code><tribaal></code> when's the next one?</p>
<p>17:26 <code><blackboxsw></code> we'll have to get invites together for the next one (Fall 2020)</p>
<p>17:27 <code><tribaal></code> noted :)</p>
<p>17:29 <code><blackboxsw></code> Ohh right and BIG NEWS that I forgot to highlight: cloud-init <em>is</em> moving from launchpad to github. We discussed this at the last cloud-init summit a couple of weeks ago.</p>
<p>17:29 <code><blackboxsw></code> Odd_Bloke: and rharper have been working on getting initial travis.yml together for allowing travis to run our CI tests.</p>
<p>17:30 <code><tribaal></code> ohhh big news indeed!</p>
<p>17:30 <code><Odd_Bloke></code> That has, indeed, landed. You can see it at <a href="https://github.com/cloud-init/cloud-init/blob/master/.travis.yml">https://github.com/cloud-init/cloud-init/blob/master/.travis.yml</a> (it's also in the Launchpad git repo, we're still syncing from there to GH ATM :).</p>
<p>17:31 <code><Odd_Bloke></code> And you can see that we're green at <a href="https://travis-ci.org/cloud-init/cloud-init">https://travis-ci.org/cloud-init/cloud-init</a></p>
<p>17:31 <code><blackboxsw></code> We are currently sorting out the rest of our CI, but the expectation for the community is that we'll soon have an announcement and simple procedure to get folks contributing with pull requests @ <a href="https://github.com/cloud-init/cloud-init">https://github.com/cloud-init/cloud-init</a> instead of posting branch review requests at <a href="https://git.launchpad.net/cloud-init">https://git.launchpad.net/cloud-init</a></p>
<p>17:31 <code><tribaal></code> very nice!</p>
<p>17:33 <code><blackboxsw></code> There will likely be a small transition set of steps needed for existing launchpad users to authenticate their github account because of the Canonical's contributor license agreement (CLA). But we are sorting that imminently</p>
<p>17:33 <code><tribaal></code> ah that would make sese yeah</p>
<p>17:34 <code><blackboxsw></code> we'll make every effort to reduce the amount of work for in-flight branches and get landed what we can prior to that transition to github. So, expect before next cloud-init status meeting that we have details about the switch</p>
<p>17:35 <code><blackboxsw></code> #action mailing list update to cloud-init community about procedure/timeline for migration to github</p>
<p>17:35 * meetingology mailing list update to cloud-init community about procedure/timeline for migration to github</p>
<p>17:36 <code><blackboxsw></code> we really want to leverage the active github community, public CI results, and ease of use and github is the best path forward for that</p>
<p>17:36 <code><blackboxsw></code> thanks Odd_Bloke and rharper for all the work there so far</p>
<p>17:38 <code><blackboxsw></code> well. I think that about wraps the status meeting for this episode. Hope Halloween has more treat than trick for folks. See you next 11/05 16:15 UTC.</p>
<p>17:38 <code><blackboxsw></code> thanks for participating chillysurfer & tribaal</p>
<p>17:38 <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>