-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathstatus-2017-11-13.html
303 lines (264 loc) · 22.1 KB
/
status-2017-11-13.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
<!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: Office Hours (next 30 minutes), 13 Nov at 16:03 — 17:01 UTC Full logs at [[http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-11-13-16.03.log.html]] Meeting summary Recent Changes The discussion about "Recent Changes" started at 16:04 LINK: http://paste.ubuntu.com/25954862 …" />
<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: Office Hours (next 30 minutes), 13 Nov at 16:03 — 17:01 UTC Full logs at [[http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-11-13-16.03.log.html]] Meeting summary Recent Changes The discussion about "Recent Changes" started at 16:04 LINK: http://paste.ubuntu.com/25954862 …"/>
<meta property="og:locale" content="en_US"/>
<meta property="og:url" content="https://cloud-init.github.io/status-2017-11-13.html"/>
<meta property="og:type" content="article"/>
<meta property="article:published_time" content="2017-11-13 16:03: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-2017-11-13">Cloud-init bi-weekly status</h1>
<p>
Posted on Mon 13 November 2017 in <a href="https://cloud-init.github.io/category/status-meeting-minutes.html">status-meeting-minutes</a>
• 7 min read
</p>
</header>
<div>
<h2>Meeting information</h2>
<ul>
<li>#cloud-init: Office Hours (next 30 minutes), 13 Nov at 16:03 — 17:01 UTC</li>
<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-11-13-16.03.log.html">http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-11-13-16.03.log.html</a>]]</li>
</ul>
<h2>Meeting summary</h2>
<h3>Recent Changes</h3>
<p>The discussion about "Recent Changes" started at 16:04</p>
<ul>
<li><strong>LINK</strong>: <a href="http://paste.ubuntu.com/25954862/">http://paste.ubuntu.com/25954862/</a> </li>
<li><strong>LINK</strong>: <a href="https://github.com/canonical-server/dev-summary/blob/master/doc/2017-10-31.md">https://github.com/canonical-server/dev-summary/blob/master/doc/2017-10-31.md</a> </li>
<li><strong>LINK</strong>: <a href="https://github.com/canonical-server/dev-summary/blob/master/doc/2017-11-07.md">https://github.com/canonical-server/dev-summary/blob/master/doc/2017-11-07.md</a> </li>
</ul>
<h3>In Progress Development</h3>
<p>The discussion about "In Progress Development" started at 16:10</p>
<ul>
<li><strong>LINK</strong>: <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a> </li>
</ul>
<h3>Office Hours next 30 minutes</h3>
<p>The discussion about "Office Hours next 30 minutes" started at 16:13</p>
<ul>
<li><strong>LINK</strong>: <a href="https://jenkins.ubuntu.com/server/view/cloud-init/">https://jenkins.ubuntu.com/server/view/cloud-init/</a> </li>
<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bug/1731619">https://bugs.launchpad.net/cloud-init/+bug/1731619</a> </li>
<li><strong>LINK</strong>: <a href="http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html?highlight=nocloud">http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html?highlight=nocloud</a></li>
<li>SRU queued for release today</li>
</ul>
<h2>Vote results</h2>
<h2>Done items</h2>
<ul>
<li>(none)</li>
</ul>
<h2>People present (lines said)</h2>
<ul>
<li>blackboxsw (53)</li>
<li>robjo (20)</li>
<li>smoser (17)</li>
<li>via (10)</li>
<li>meetingology (3)</li>
<li>ubot5 (2)</li>
<li>powersj (1)</li>
<li>rharper (1)</li>
</ul>
<h2>Full Log</h2>
<p>16:03 <code><blackboxsw</code>> #startmeeting Cloud-init bi-weekly status</p>
<p>16:03 <code><meetingology</code>> Meeting started Mon Nov 13 16:03:13 2017 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:03 <code><meetingology</code>> </p>
<p>16:03 <code><meetingology</code>> Available commands: action commands idea info link nick</p>
<p>16:03 <code><powersj</code>> o/</p>
<p>16:03 <code><blackboxsw</code>> time change got to us</p>
<p>16:04 <code><blackboxsw</code>> #topic Recent Changes</p>
<p>16:05 <code><blackboxsw</code>> hey folks. thanks for joining just pulling together the content for the last couple weeks of work for the cloud-init project</p>
<p>16:06 <code><smoser</code>> <a href="http://paste.ubuntu.com/25954862/">http://paste.ubuntu.com/25954862/</a></p>
<p>16:06 <code><smoser</code>> $ git log a90a8b1cb3104ee3250ac79d6e25a9ff4f527baa.. | log2dch | sed 's,^ ,,' | pastebinit</p>
<p>16:06 <code><blackboxsw</code>> most of the ubuntu-side of the house was involved in handling the SRU of 17.1 into ubuntu and handling any discovered regressions</p>
<p>16:06 <code><blackboxsw</code>> Published cloud-init packages to Bionic Beaver release</p>
<p>16:06 <code><blackboxsw</code>> Update Gentoo Linux support to "rc-service" scripts as "service" is deprecated, thanks to ckonstanski!</p>
<p>16:06 <code><blackboxsw</code>> Detected and fixed a pre-release regression of resizefs when root path is specified by UUID on the kernel cmdline (LP: #1725067)</p>
<p>16:06 <code><ubot5</code>> Launchpad bug 1725067 in cloud-init (Ubuntu Zesty) "cloud-init resizefs fails when booting with root=PARTUUID=" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1725067">https://launchpad.net/bugs/1725067</a></p>
<p>16:06 <code><blackboxsw</code>> #link <a href="http://paste.ubuntu.com/25954862/">http://paste.ubuntu.com/25954862/</a></p>
<p>16:07 <code><blackboxsw</code>> #info SRU queued for release today</p>
<p>16:07 <code><blackboxsw</code>> Here's the cloud-init content we published for the last two weeks:</p>
<p>16:07 <code><blackboxsw</code>> #link <a href="https://github.com/canonical-server/dev-summary/blob/master/doc/2017-10-31.md">https://github.com/canonical-server/dev-summary/blob/master/doc/2017-10-31.md</a></p>
<p>16:07 <code><blackboxsw</code>> #link <a href="https://github.com/canonical-server/dev-summary/blob/master/doc/2017-11-07.md">https://github.com/canonical-server/dev-summary/blob/master/doc/2017-11-07.md</a></p>
<p>16:09 <code><blackboxsw</code>> last week we handled an EC2 behavior regression for xenial, whereby we didn't want to change cloud-init to configure all nics based on ec2 metadata, we will only configure the primary nice</p>
<p>16:09 <code><blackboxsw</code>> last week we handled an EC2 behavior regression for xenial, whereby we didn't want to change cloud-init to configure all nics based on ec2 metadata, we will only configure the primary NIC</p>
<p>16:09 <code><blackboxsw</code>> with those SRU regresssions fixed and published to master, we expect cloud-init 17.1 updated in Xenial,Zesty and Artful today</p>
<p>16:10 <code><blackboxsw</code>> #topic In Progress Development</p>
<p>16:10 <code><blackboxsw</code>> smoser: rharper anything here?</p>
<p>16:10 <code><smoser</code>> #link <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a></p>
<p>16:11 <code><smoser</code>> robjo has done a couple fixes for SuSE and i've pulled a few of them.</p>
<p>16:11 <code><smoser</code>> he has one up i saw yestderday for ntpSuSE</p>
<p>16:11 <code><smoser</code>> others ther.e we've been delinquent due to some distractions recently.</p>
<p>16:11 <code><rharper</code>> blackboxsw: nothing new for me at the moment</p>
<p>16:12 <code><smoser</code>> and chad had one up for clean and status</p>
<p>16:12 <code><blackboxsw</code>> btw thx robjo ckonstanski and Dave Mulford for the fixes over the last iteration. We also expect that a couple VMware branches for the OVF datasource will last this week or next</p>
<p>16:12 <code><smoser</code>> which is nice.</p>
<p>16:13 <code><robjo</code>> moving the meeting an hour foward while we are on Standard time or is this a one time occurance, did I miss an announcement?</p>
<p>16:13 <code><blackboxsw</code>> #topic Office Hours (next 30 minutes)</p>
<p>16:14 <code><robjo</code>> lp#1731619, chrony support, should that also be driven through ntp config or should there be a new config option?</p>
<p>16:14 <code><blackboxsw</code>> so we'll hang out with eyes on this channel for any burning questions/bugs/questions</p>
<p>16:14 <code><smoser</code>> robjo: well, the meeting is listed in UTC time</p>
<p>16:14 <code><smoser</code>> that pays no attention to US legislation to change clocks at random points in the year :)</p>
<p>16:15 <code><robjo</code>> oK, my fault when I added it to my calendar, eay enough to fix ;)</p>
<p>16:15 <code><smoser</code>> but the humans here were also affected :)</p>
<p>16:15 <code><blackboxsw</code>> heh, anyone opposed to shifting this meeting time +30 from now during the next few months?</p>
<p>16:15 <code><blackboxsw</code>> as the meeting now collides w/ another meeting for us</p>
<p>16:15 <code><blackboxsw</code>> :/</p>
<p>16:16 <code><blackboxsw</code>> officially 16:30 UTC?</p>
<p>16:17 <code><robjo</code>> Well, I'd prefer to either follow the "randomness" clock manipulation or not follow it</p>
<p>16:19 <code><robjo</code>> meaning don't change the meeting time because there exists a conflict when standard time switches to daylight savings or vice versa, becaus if you do that you might as well follow the silliness of the government to begin with</p>
<p>16:19 <code><blackboxsw</code>> fair point. ok let's keep the new time as is.</p>
<p>16:20 <code><blackboxsw</code>> we've discussed side-channel, we can shift our meetings out of the way of this</p>
<p>16:20 <code><blackboxsw</code>> so robjo +1</p>
<p>16:20 <code><blackboxsw</code>> 16:00 UTC</p>
<p>16:24 <code><blackboxsw</code>> also related to CI side, powersj and rharper spent quite a bit of time w/ our continuous integration infrastructure fixing/addressing memory & storage pressure issues to make sure we avoid intermittent false test failures due to timeouts or system resource contention</p>
<p>16:24 <code><blackboxsw</code>> #link <a href="https://jenkins.ubuntu.com/server/view/cloud-init/">https://jenkins.ubuntu.com/server/view/cloud-init/</a></p>
<p>16:28 <code><via</code>> is there a way to use metadata in the cloud-init file? specifically, if i want to use the aws-provided instance id in an attribute</p>
<p>16:28 <code><robjo</code>> OK, back to my question about chrony: lp#1731619, chrony support, should that also be driven through ntp config or should there be a new config option?</p>
<p>16:28 <code><via</code>> like configuring the chef node name to have my instance id in it</p>
<p>16:32 <code><blackboxsw</code>> #link <a href="https://bugs.launchpad.net/cloud-init/+bug/1731619">https://bugs.launchpad.net/cloud-init/+bug/1731619</a></p>
<p>16:32 <code><ubot5</code>> Launchpad bug 1731619 in cloud-init "Support chrony as a client for ntp" [Undecided,New]</p>
<p>16:33 <code><blackboxsw</code>> it's a good bug, we've had a couple of discussions about ntpd versus timesyncd for different system environments</p>
<p>16:34 <code><blackboxsw</code>> current implementation of cc_ntp module is to return False ('ntp' not installable) on certain known environments where we know we want systemd timesyncd to run instead by default</p>
<p>16:34 <code><smoser</code>> via: i think what your asking is (i htink) covered in <a href="https://trello.com/c/AYaCdQyT">https://trello.com/c/AYaCdQyT</a></p>
<p>16:35 <code><via</code>> well, i'm trying to do it in a yaml cloud-config file</p>
<p>16:35 <code><smoser</code>> right. as it is right now, via you cann't reference anything from the metadata.</p>
<p>16:35 <code><via</code>> does that mean i need to use #jinja and if so how does that play with #cloud-config ?</p>
<p>16:35 <code><via</code>> oh</p>
<p>16:36 <code><via</code>> bummer</p>
<p>16:36 <code><via</code>> should i just switch to a shell script?</p>
<p>16:36 <code><smoser</code>> but we'd hope to implement that.</p>
<p>16:36 <code><smoser</code>> via: thats really the only way right now. and then in the shell scripty you'd have to query the metadata service yourself.</p>
<p>16:36 <code><via</code>> okay, damn</p>
<p>16:36 <code><via</code>> thanks</p>
<p>16:36 <code><blackboxsw</code>> robjo: we think that's a good approach/feature suggestion. We could add chrony template files etc like the ntp templates, and we might be able to have the distro report what time sync daemon it wants to run</p>
<p>16:36 <code><smoser</code>> basically... we realize what you're asking is quite helpful and reasonable but dont have a way to do it right now</p>
<p>16:36 <code><smoser</code>> but we do plan on implementing it.</p>
<p>16:37 <code><via</code>> no worries, i'm stuck on an ancient version anyway</p>
<p>16:38 <code><robjo</code>> blackboxsw: That was my thinking, move the "service_name" setting to the distro as "time_service_name" and then drive cc_ntp based on that</p>
<p>16:39 <code><robjo</code>> since with a third option the black/white decision being made today will no longer work</p>
<p>16:39 <code><blackboxsw</code>> +1 robjo yeah. rharper was chatting about this potential approach as well</p>
<p>16:39 <code><robjo</code>> look there is also grey ;)</p>
<p>16:39 <code><blackboxsw</code>> heh yeah</p>
<p>16:40 <code><robjo</code>> Next question.... network config.</p>
<p>16:40 <code><blackboxsw</code>> yeah might have to 'grow' an override option in cc_ntp module eventually</p>
<p>16:41 <code><blackboxsw</code>> as those grey use-cases come up (per bugs/requests ;) )</p>
<p>16:41 <code><robjo</code>> A long timi ago the RHEL implementation was re-written to use sysconfig renderer, but RHEL sysconfig and SLE sysconfig are different, why wouldn't they be</p>
<p>16:42 <code><robjo</code>> that also implies that the openSUSE/SLES implementation for network config rendering still uses the "old" implementation and thus produces a warning in the log file</p>
<p>16:43 * blackboxsw is looking for the warning generated</p>
<p>16:43 <code><robjo</code>> this would imply some refactoring is in order if we want to move openSUSE/SLES to using the newer API to render the network config</p>
<p>16:44 <code><robjo</code>> blackboxsw: "apply_network_config is not currently implemented "</p>
<p>16:44 <code><robjo</code>> "for distribution '%s'. Attempting to use apply_network"</p>
<p>16:45 <code><blackboxsw</code>> ahh. right-o</p>
<p>16:45 <code><robjo</code>> the question from my point would be is, when I want to implement the SUSE bits am I also on the hook for the refactoring part or can I get some help with that? which of course will make my life easier ;)</p>
<p>16:47 <code><robjo</code>> And yes, I realize a bug will need to be filed, but I haven't figured out how to formulate this nicely</p>
<p>16:47 <code><blackboxsw</code>> robjo: I think we should be able to help out a bit with that refactor to make sure it's cleaner and easier to maintain.</p>
<p>16:47 <code><robjo</code>> OK :)</p>
<p>16:50 <code><blackboxsw</code>> there are a couplengeneric distro fixes which need to get designed (just like in the datasources) to make the common distro classes a bit easier to maintain as well as making classes a bit more modular and more easily tested.</p>
<p>16:51 <code><blackboxsw</code>> we still haven't landed some of the common datasource changes we had talked about during the Summit because we've been avoiding risk during the 17.1 release. But, similar/minor architecture changes should start taking shape here for datasources and distros now that we see a light at the end of the tunnel on the release.</p>
<p>16:52 <code><blackboxsw</code>> we'll keep our eyes open for discussions/suggestions from folks</p>
<p>16:54 <code><robjo</code>> Speaking of data sources, for the SUSE Container As A Service Platform, we implemented a data source to read from local disk, is that something that would be of interest upstream? Yes, this might seem silly but in our use case it makes perfect sense ;)</p>
<p>16:56 <code><blackboxsw</code>> robjo: I'm curious how different that datasource would be from nocloud datasource</p>
<p>16:56 <code><blackboxsw</code>> <a href="http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html">http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html</a>?highlight=nocloud</p>
<p>16:56 <code><blackboxsw</code>> #link <a href="http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html">http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html</a>?highlight=nocloud</p>
<p>16:56 <code><blackboxsw</code>> which allows for providing local data instead of dealing with metadata</p>
<p>16:56 <code><blackboxsw</code>> well network metadata</p>
<p>16:57 <code><robjo</code>> I wasn't really involved, just accepted the patch to the package and have not done a comparison to nocloud, but I'll take a look</p>
<p>17:00 <code><blackboxsw</code>> good deal.... think we are at the top of the hour... so I'll probably end meeting now</p>
<p>17:01 <code><blackboxsw</code>> thanks via robjo rharper powersj & smoser. next meeting 2 weeks same early time</p>
<p>17:01 <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>