diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..51a25e4 --- /dev/null +++ b/.gitignore @@ -0,0 +1,3 @@ +*.pyc +output +*.pid diff --git a/Flex b/Flex new file mode 160000 index 0000000..229ad20 --- /dev/null +++ b/Flex @@ -0,0 +1 @@ +Subproject commit 229ad20d36f093d8a6d4526aa67d22d34812ee02 diff --git a/Makefile b/Makefile new file mode 100644 index 0000000..6c07a8f --- /dev/null +++ b/Makefile @@ -0,0 +1,125 @@ +PY?=python +PELICAN?=pelican +PELICANOPTS= + +BASEDIR=$(CURDIR) +INPUTDIR=$(BASEDIR)/content +OUTPUTDIR=$(BASEDIR)/output +CONFFILE=$(BASEDIR)/pelicanconf.py +PUBLISHCONF=$(BASEDIR)/publishconf.py + +FTP_HOST=localhost +FTP_USER=anonymous +FTP_TARGET_DIR=/ + +SSH_HOST=localhost +SSH_PORT=22 +SSH_USER=root +SSH_TARGET_DIR=/var/www + +S3_BUCKET=my_s3_bucket + +CLOUDFILES_USERNAME=my_rackspace_username +CLOUDFILES_API_KEY=my_rackspace_api_key +CLOUDFILES_CONTAINER=my_cloudfiles_container + +DROPBOX_DIR=~/Dropbox/Public/ + +GITHUB_PAGES_BRANCH=gh-pages + +DEBUG ?= 0 +ifeq ($(DEBUG), 1) + PELICANOPTS += -D +endif + +RELATIVE ?= 0 +ifeq ($(RELATIVE), 1) + PELICANOPTS += --relative-urls +endif + +help: + @echo 'Makefile for a pelican Web site ' + @echo ' ' + @echo 'Usage: ' + @echo ' make html (re)generate the web site ' + @echo ' make clean remove the generated files ' + @echo ' make regenerate regenerate files upon modification ' + @echo ' make publish generate using production settings ' + @echo ' make serve [PORT=8000] serve site at http://localhost:8000' + @echo ' make serve-global [SERVER=0.0.0.0] serve (as root) to $(SERVER):80 ' + @echo ' make devserver [PORT=8000] start/restart develop_server.sh ' + @echo ' make stopserver stop local server ' + @echo ' make ssh_upload upload the web site via SSH ' + @echo ' make rsync_upload upload the web site via rsync+ssh ' + @echo ' make dropbox_upload upload the web site via Dropbox ' + @echo ' make ftp_upload upload the web site via FTP ' + @echo ' make s3_upload upload the web site via S3 ' + @echo ' make cf_upload upload the web site via Cloud Files' + @echo ' make github upload the web site via gh-pages ' + @echo ' ' + @echo 'Set the DEBUG variable to 1 to enable debugging, e.g. make DEBUG=1 html ' + @echo 'Set the RELATIVE variable to 1 to enable relative urls ' + @echo ' ' + +html: + $(PELICAN) $(INPUTDIR) -o $(OUTPUTDIR) -s $(CONFFILE) $(PELICANOPTS) + +clean: + [ ! -d $(OUTPUTDIR) ] || rm -rf $(OUTPUTDIR) + +regenerate: + $(PELICAN) -r $(INPUTDIR) -o $(OUTPUTDIR) -s $(CONFFILE) $(PELICANOPTS) + +serve: +ifdef PORT + cd $(OUTPUTDIR) && $(PY) -m pelican.server $(PORT) +else + cd $(OUTPUTDIR) && $(PY) -m pelican.server +endif + +serve-global: +ifdef SERVER + cd $(OUTPUTDIR) && $(PY) -m pelican.server 80 $(SERVER) +else + cd $(OUTPUTDIR) && $(PY) -m pelican.server 80 0.0.0.0 +endif + + +devserver: +ifdef PORT + $(BASEDIR)/develop_server.sh restart $(PORT) +else + $(BASEDIR)/develop_server.sh restart +endif + +stopserver: + $(BASEDIR)/develop_server.sh stop + @echo 'Stopped Pelican and SimpleHTTPServer processes running in background.' + +publish: + $(PELICAN) $(INPUTDIR) -o $(OUTPUTDIR) -s $(PUBLISHCONF) $(PELICANOPTS) + +ssh_upload: publish + scp -P $(SSH_PORT) -r $(OUTPUTDIR)/* $(SSH_USER)@$(SSH_HOST):$(SSH_TARGET_DIR) + +rsync_upload: publish + rsync -e "ssh -p $(SSH_PORT)" -P -rvzc --delete $(OUTPUTDIR)/ $(SSH_USER)@$(SSH_HOST):$(SSH_TARGET_DIR) --cvs-exclude + +dropbox_upload: publish + cp -r $(OUTPUTDIR)/* $(DROPBOX_DIR) + +ftp_upload: publish + lftp ftp://$(FTP_USER)@$(FTP_HOST) -e "mirror -R $(OUTPUTDIR) $(FTP_TARGET_DIR) ; quit" + +s3_upload: publish + s3cmd sync $(OUTPUTDIR)/ s3://$(S3_BUCKET) --acl-public --delete-removed --guess-mime-type --no-mime-magic --no-preserve + +cf_upload: publish + cd $(OUTPUTDIR) && swift -v -A https://auth.api.rackspacecloud.com/v1.0 -U $(CLOUDFILES_USERNAME) -K $(CLOUDFILES_API_KEY) upload -c $(CLOUDFILES_CONTAINER) . + +github: publish + ghp-import -m "Generate Pelican site" -b $(GITHUB_PAGES_BRANCH) $(OUTPUTDIR) + git push origin $(GITHUB_PAGES_BRANCH):master --force + git push origin source + +.PHONY: html help clean regenerate serve serve-global devserver stopserver publish ssh_upload rsync_upload dropbox_upload ftp_upload s3_upload cf_upload github diff --git a/archives.html b/archives.html deleted file mode 100644 index 64b6971..0000000 --- a/archives.html +++ /dev/null @@ -1,268 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Archives - - - - -
- - - -
-
-

Archives

-
-
-
-
Tue 29 June 2021
-
Cloud-init bi-weekly status
-
Tue 15 June 2021
-
Cloud-init bi-weekly status
-
Tue 01 June 2021
-
Cloud-init bi-weekly status
-
Tue 18 May 2021
-
Cloud-init bi-weekly status
-
Tue 06 April 2021
-
Cloud-init bi-weekly status
-
Tue 23 March 2021
-
Cloud-init bi-weekly status
-
Tue 09 March 2021
-
Cloud-init bi-weekly status
-
Tue 23 February 2021
-
Cloud-init bi-weekly status
-
Tue 17 November 2020
-
Cloud-init bi-weekly status
-
Tue 08 September 2020
-
Cloud-init bi-weekly status
-
Tue 25 August 2020
-
Cloud-init bi-weekly status
-
Tue 28 July 2020
-
Cloud-init bi-weekly status
-
Tue 14 July 2020
-
Cloud-init bi-weekly status
-
Tue 30 June 2020
-
Cloud-init bi-weekly status
-
Tue 16 June 2020
-
Cloud-init bi-weekly status
-
Tue 02 June 2020
-
Cloud-init bi-weekly status
-
Tue 19 May 2020
-
Cloud-init bi-weekly status
-
Tue 05 May 2020
-
Cloud-init bi-weekly status
-
Tue 14 April 2020
-
Cloud-init bi-weekly status
-
Tue 31 March 2020
-
Cloud-init bi-weekly status
-
Tue 10 March 2020
-
Cloud-init bi-weekly status
-
Tue 18 February 2020
-
Cloud-init bi-weekly status
-
Tue 04 February 2020
-
Cloud-init bi-weekly status
-
Tue 21 January 2020
-
Cloud-init bi-weekly status
-
Tue 07 January 2020
-
Cloud-init bi-weekly status
-
Tue 10 December 2019
-
Cloud-init bi-weekly status
-
Tue 26 November 2019
-
Cloud-init bi-weekly status
-
Tue 29 October 2019
-
Cloud-init bi-weekly status
-
Tue 08 October 2019
-
Cloud-init bi-weekly status
-
Mon 09 September 2019
-
Cloud-init bi-weekly status
-
Mon 19 August 2019
-
Cloud-init bi-weekly status
-
Mon 05 August 2019
-
Cloud-init bi-weekly status
-
Mon 22 July 2019
-
Cloud-init bi-weekly status
-
Mon 08 July 2019
-
Cloud-init bi-weekly status
-
Mon 24 June 2019
-
Cloud-init bi-weekly status
-
Mon 10 June 2019
-
Cloud-init bi-weekly status
-
Tue 28 May 2019
-
Cloud-init bi-weekly status
-
Mon 13 May 2019
-
Cloud-init bi-weekly status
-
Mon 28 January 2019
-
Cloud-init bi-weekly status
-
Mon 07 January 2019
-
Cloud-init bi-weekly status
-
Mon 10 December 2018
-
Cloud-init bi-weekly status
-
Mon 26 November 2018
-
Cloud-init bi-weekly status
-
Mon 12 November 2018
-
Cloud-init bi-weekly status
-
Mon 29 October 2018
-
Cloud-init bi-weekly status
-
Mon 15 October 2018
-
Cloud-init bi-weekly status
-
Tue 25 September 2018
-
Cloud-init bi-weekly status
-
Tue 04 September 2018
-
Cloud-init bi-weekly status
-
Mon 20 August 2018
-
Cloud-init bi-weekly status
-
Mon 06 August 2018
-
Cloud-init bi-weekly status
-
Mon 02 July 2018
-
Cloud-init bi-weekly status
-
Mon 18 June 2018
-
Cloud-init bi-weekly status
-
Tue 29 May 2018
-
Cloud-init bi-weekly status
-
Mon 14 May 2018
-
Cloud-init bi-weekly status
-
Mon 30 April 2018
-
Cloud-init bi-weekly status
-
Mon 16 April 2018
-
Cloud-init bi-weekly status
-
Mon 02 April 2018
-
Cloud-init bi-weekly status
-
Mon 19 March 2018
-
Cloud-init bi-weekly status
-
Mon 05 March 2018
-
Cloud-init bi-weekly status
-
Fri 16 February 2018
-
Cloud-init bi-weekly status
-
Mon 22 January 2018
-
Cloud-init bi-weekly status
-
Mon 08 January 2018
-
Cloud-init bi-weekly status
-
Mon 11 December 2017
-
Cloud-init bi-weekly status
-
Mon 13 November 2017
-
Cloud-init bi-weekly status
-
Mon 30 October 2017
-
Cloud-init bi-weekly status
-
Mon 16 October 2017
-
Cloud-init bi-weekly status
-
Mon 02 October 2017
-
Cloud-init bi-weekly status
-
Mon 18 September 2017
-
Cloud-init bi-weekly status
-
Tue 05 September 2017
-
Cloud-init github.io details
-
Tue 05 September 2017
-
Cloud-init bi-weekly status
-
-
-
- - -
- - - - - - - - \ No newline at end of file diff --git a/author/chadsmithcanonicalcom.html b/author/chadsmithcanonicalcom.html deleted file mode 100644 index 443a556..0000000 --- a/author/chadsmithcanonicalcom.html +++ /dev/null @@ -1,390 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Posts by chad.smith@canonical.com: - - - - -
- - - - - -
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 29 June 2021 in status-meeting-minutes - - - • 2 min read -

-
-
-

Meeting information

- -

Meeting summary

- -

People present (lines …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 15 June 2021 in status-meeting-minutes - - - • 2 min read -

-
-
-

Meeting information

- -

Meeting summary

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 01 June 2021 in status-meeting-minutes - - - • 2 min read -

-
-
-

Meeting information

- -

Meeting summary

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 18 May 2021 in status-meeting-minutes - - - • 2 min read -

-
-
-

Meeting information

- -

Meeting summary

-

People present (lines said)

-
    -
  • blackboxsw (12)
  • -
  • paride (4)
  • -
  • smoser (4)
  • -
  • meetingology (2)
  • -
  • ubot5 (1 …
-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 06 April 2021 in status-meeting-minutes - - - • 2 min read -

-
-
-

Meeting information

- -

Meeting summary

-

People present (lines said)

-
    -
  • hamalq (7)
  • -
  • blackboxsw (6)
  • -
  • falcojr (3)
  • -
  • meetingology (2)
  • -
  • Odd_Bloke (1 …
-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 23 March 2021 in status-meeting-minutes - - - • 2 min read -

-
-
-

Meeting information

- -

Meeting summary

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 09 March 2021 in status-meeting-minutes - - - • 3 min read -

-
-
-

Meeting information

- -

Meeting summary

- -

People present (lines …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 23 February 2021 in status-meeting-minutes - - - • 2 min read -

-
-
-

Meeting information

- -

Meeting summary

- -

People present (lines …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 17 November 2020 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://discourse.ubuntu.com/t/cloud-init-statue-11-17-20/19391 - LINK: https://github.com/canonical/cloud-init/pull/655 i'd …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 08 September 2020 in status-meeting-minutes - - - • 5 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-08-25.html#status-2020-08-25

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:21 …

-
- Continue reading -
-
- - - - - - - -
- - - - - - - - \ No newline at end of file diff --git a/author/chadsmithcanonicalcom2.html b/author/chadsmithcanonicalcom2.html deleted file mode 100644 index a3a33c2..0000000 --- a/author/chadsmithcanonicalcom2.html +++ /dev/null @@ -1,391 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Posts by chad.smith@canonical.com: - - - - -
- - - - - -
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 25 August 2020 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:27.

-

Recent Changes

-

The …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 28 July 2020 in status-meeting-minutes - - - • 3 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-07-14.html#status-2020-07-14

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:58 …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 14 July 2020 in status-meeting-minutes - - - • 5 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-06-30.html#status-2020-06-30

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:55 …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 30 June 2020 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-06-16.html#status-2020-06-16

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:28 …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 16 June 2020 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:24.

-

In-progress Development

-

The …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 02 June 2020 in status-meeting-minutes - - - • 8 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:24.

-

Recent Changes

-

The …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 19 May 2020 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-05-05.html#status-2020-05-05

-

#cloud-init pull-requests https://git.io/JeVed | Meeting minutes: https://goo.gl …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 05 May 2020 in status-meeting-minutes - - - • 4 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:20.

-

Recent Changes

-

The …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 14 April 2020 in status-meeting-minutes - - - • 4 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-03-31.html#status-2020-03-31

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:23 …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 31 March 2020 in status-meeting-minutes - - - • 4 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-03-10.html#status-2020-03-10

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:22 …

-
- Continue reading -
-
- - - - - - - -
- - - - - - - - \ No newline at end of file diff --git a/author/chadsmithcanonicalcom3.html b/author/chadsmithcanonicalcom3.html deleted file mode 100644 index 19e2d15..0000000 --- a/author/chadsmithcanonicalcom3.html +++ /dev/null @@ -1,392 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Posts by chad.smith@canonical.com: - - - - -
- - - - - -
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 10 March 2020 in status-meeting-minutes - - - • 9 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-02-18.html#status-2020-02-18

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:24 …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 18 February 2020 in status-meeting-minutes - - - • 5 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-02-04.html#status-2020-02-04

-

Previous Actions

-

The discussion about "Previous Actions" started at 17:37 …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 04 February 2020 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Previous Actions

-

The discussion about "Previous Actions" started at 17:27.

-

Recent Changes

-

The …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 21 January 2020 in status-meeting-minutes - - - • 5 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Previous Actions

-

The discussion about "Previous Actions" started at 17:50.

-
    -
  • LINK: bugs.launchpad …
-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 07 January 2020 in status-meeting-minutes - - - • 11 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2019-12-10.html#status-2019-12-10

-

Previous Actions

-

The discussion about "Previous Actions" started at 17:36 …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 10 December 2019 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 17:22.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 26 November 2019 in status-meeting-minutes - - - • 9 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 17:28.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 29 October 2019 in status-meeting-minutes - - - • 12 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:26.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 08 October 2019 in status-meeting-minutes - - - • 9 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:23.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 09 September 2019 in status-meeting-minutes - - - • 5 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2019-08-19.html#status-2019-08-19

-

Previous actions

-

The discussion about "Previous actions" started at 16:30 …

-
- Continue reading -
-
- - - - - - - -
- - - - - - - - \ No newline at end of file diff --git a/author/chadsmithcanonicalcom4.html b/author/chadsmithcanonicalcom4.html deleted file mode 100644 index 00827eb..0000000 --- a/author/chadsmithcanonicalcom4.html +++ /dev/null @@ -1,391 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Posts by chad.smith@canonical.com: - - - - -
- - - - - -
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 19 August 2019 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2019-08-05.html#status-2019-08-05

-

cloud-init Reviews: http://bit.ly/ci-reviews | Meeting minutes: https://goo.gl …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 05 August 2019 in status-meeting-minutes - - - • 5 min read -

-
-
-

Meeting information

- -

Meeting summary

-

#cloud-init Reviews: http://bit.ly/ci-reviews | Meeting minutes: https://goo.gl/mrHdaj | Next status meeting Aug 19 16:15 …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 22 July 2019 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:17.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 08 July 2019 in status-meeting-minutes - - - • 10 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:18.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 24 June 2019 in status-meeting-minutes - - - • 10 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:23.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 10 June 2019 in status-meeting-minutes - - - • 11 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:23.

-

Recent Changes

-

The …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 28 May 2019 in status-meeting-minutes - - - • 4 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 15:27.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 13 May 2019 in status-meeting-minutes - - - • 14 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:31.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 28 January 2019 in status-meeting-minutes - - - • 5 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:27.

-
    -
  • ACTION: carry over blackboxsw close and land Openstack …
-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 07 January 2019 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:38.

- -
- Continue reading -
-
- - - - - - - -
- - - - - - - - \ No newline at end of file diff --git a/author/chadsmithcanonicalcom5.html b/author/chadsmithcanonicalcom5.html deleted file mode 100644 index 375ec3b..0000000 --- a/author/chadsmithcanonicalcom5.html +++ /dev/null @@ -1,398 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Posts by chad.smith@canonical.com: - - - - -
- - - - - -
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 10 December 2018 in status-meeting-minutes - - - • 4 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:13.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 26 November 2018 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io - LINK: https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427 - LINK: https://code …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 12 November 2018 in status-meeting-minutes - - - • 4 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:20.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 29 October 2018 in status-meeting-minutes - - - • 4 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:22.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 15 October 2018 in status-meeting-minutes - - - • 9 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:18.

- -

Recent Changes

-

The …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 25 September 2018 in status-meeting-minutes - - - • 5 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:09.

-

Recent Changes

-

The discussion about "Recent Changes …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 04 September 2018 in status-meeting-minutes - - - • 5 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/ - LINK: https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin - LINK: https://powersj.github.io/post …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 20 August 2018 in status-meeting-minutes - - - • 4 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:13.

-

Recent Changes

-

The discussion about "Recent Changes …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 06 August 2018 in status-meeting-minutes - - - • 5 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:09.

-
    -
  • ACTION: rharper …
-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 02 July 2018 in status-meeting-minutes - - - • 4 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:09.

- -
- Continue reading -
-
- - - - - - - -
- - - - - - - - \ No newline at end of file diff --git a/author/chadsmithcanonicalcom6.html b/author/chadsmithcanonicalcom6.html deleted file mode 100644 index 21f7e30..0000000 --- a/author/chadsmithcanonicalcom6.html +++ /dev/null @@ -1,393 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Posts by chad.smith@canonical.com: - - - - -
- - - - - -
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 18 June 2018 in status-meeting-minutes - - - • 8 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:11.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 29 May 2018 in status-meeting-minutes - - - • 10 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:09.

-

Recent Changes …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 14 May 2018 in status-meeting-minutes - - - • 7 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:09.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 30 April 2018 in status-meeting-minutes - - - • 12 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:07.

-

#cloud-init Reviews: http://bit.ly/ci-reviews | Meeting …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 16 April 2018 in status-meeting-minutes - - - • 8 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent-changes

-

The discussion about "Recent-changes" started at 16:04.

-

In-progresss Development

-

The discussion about "In-progresss Development" started at …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 02 April 2018 in status-meeting-minutes - - - • 5 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:08.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 19 March 2018 in status-meeting-minutes - - - • 11 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:05.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 05 March 2018 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent Changes

-

The discussion about "Recent Changes" started at 17:02.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Fri 16 February 2018 in status-meeting-minutes - - - • 7 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent changes

-

The discussion about "Recent changes" started at 16:08.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 22 January 2018 in status-meeting-minutes - - - • 8 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent changes

-

The discussion about "Recent changes" started at 16:10.

- -
- Continue reading -
-
- - - - - - - -
- - - - - - - - \ No newline at end of file diff --git a/author/chadsmithcanonicalcom7.html b/author/chadsmithcanonicalcom7.html deleted file mode 100644 index 17c26a6..0000000 --- a/author/chadsmithcanonicalcom7.html +++ /dev/null @@ -1,359 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Posts by chad.smith@canonical.com: - - - - -
- - - - - -
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 08 January 2018 in status-meeting-minutes - - - • 11 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent changes

-

The discussion about "Recent changes" started at 16:04.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 11 December 2017 in status-meeting-minutes - - - • 13 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:07.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 13 November 2017 in status-meeting-minutes - - - • 7 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:04

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 30 October 2017 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent Changes

-

The discussion about “Recent Changes” started at 16:04.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 16 October 2017 in status-meeting-minutes - - - • 4 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:08

-

In Progress Development

-

The discussion about "In Progress Development …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 02 October 2017 in status-meeting-minutes - - - • 10 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent Changes / Highlights

-

The discussion about "Recent Changes / Highlights" started at 16:06.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 18 September 2017 in status-meeting-minutes - - - • 3 min read -

-
-
-

Meeting information

- -

Meeting summary

- -

Release Preparation

-

The discussion …

-
- Continue reading -
-
-
-
-
-

Cloud-init github.io details

-

- Posted on Tue 05 September 2017 in Background - - - • 1 min read -

-
-
-

Cloud-init project info page

-

Cloud-init dev team created a github.io project page based on pelican and Flex theme to host cloud-init status meeting notes.

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 05 September 2017 in status-meeting-minutes - - - • 1 min read -

-
-
-

Meeting information

-

* #cloud-init: cloud-init status meeting, 05 Sep at 16:30 — 16:30 UTC

-

Meeting summary

-

LINK: https://public.etherpad-mozilla.org/p/cloud-init-meeting

-

*Recent Changes(16:35)

-
    -
  • integration of robjo's opensuse items
  • -
  • summit results posted to mailing list https://lists.launchpad.net/cloud-init/msg00094.html
  • -
-

LINK: https://lists.launchpad.net …

-
- Continue reading -
-
- - - - - - - -
- - - - - - - - \ No newline at end of file diff --git a/authors.html b/authors.html deleted file mode 100644 index 312ca75..0000000 --- a/authors.html +++ /dev/null @@ -1,131 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Authors - - - - -
- - - -
-
-

Authors

-
-
- -
-
- - -
- - - - - - - - \ No newline at end of file diff --git a/categories.html b/categories.html deleted file mode 100644 index ca30ac5..0000000 --- a/categories.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Categories - - - - -
- - - -
-
-

Categories

-
-
- -
-
- - -
- - - - - - - - \ No newline at end of file diff --git a/category/background.html b/category/background.html deleted file mode 100644 index a6e90cb..0000000 --- a/category/background.html +++ /dev/null @@ -1,146 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Category Background - - - - -
- - - - - -
-
-

Cloud-init github.io details

-

- Posted on Tue 05 September 2017 in Background - - - • 1 min read -

-
-
-

Cloud-init project info page

-

Cloud-init dev team created a github.io project page based on pelican and Flex theme to host cloud-init status meeting notes.

-
- Continue reading -
-
- - - - - - - -
- - - - - - - - \ No newline at end of file diff --git a/category/status-meeting-minutes.html b/category/status-meeting-minutes.html deleted file mode 100644 index 41668cd..0000000 --- a/category/status-meeting-minutes.html +++ /dev/null @@ -1,390 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Category status-meeting-minutes - - - - -
- - - - - -
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 29 June 2021 in status-meeting-minutes - - - • 2 min read -

-
-
-

Meeting information

- -

Meeting summary

- -

People present (lines …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 15 June 2021 in status-meeting-minutes - - - • 2 min read -

-
-
-

Meeting information

- -

Meeting summary

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 01 June 2021 in status-meeting-minutes - - - • 2 min read -

-
-
-

Meeting information

- -

Meeting summary

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 18 May 2021 in status-meeting-minutes - - - • 2 min read -

-
-
-

Meeting information

- -

Meeting summary

-

People present (lines said)

-
    -
  • blackboxsw (12)
  • -
  • paride (4)
  • -
  • smoser (4)
  • -
  • meetingology (2)
  • -
  • ubot5 (1 …
-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 06 April 2021 in status-meeting-minutes - - - • 2 min read -

-
-
-

Meeting information

- -

Meeting summary

-

People present (lines said)

-
    -
  • hamalq (7)
  • -
  • blackboxsw (6)
  • -
  • falcojr (3)
  • -
  • meetingology (2)
  • -
  • Odd_Bloke (1 …
-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 23 March 2021 in status-meeting-minutes - - - • 2 min read -

-
-
-

Meeting information

- -

Meeting summary

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 09 March 2021 in status-meeting-minutes - - - • 3 min read -

-
-
-

Meeting information

- -

Meeting summary

- -

People present (lines …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 23 February 2021 in status-meeting-minutes - - - • 2 min read -

-
-
-

Meeting information

- -

Meeting summary

- -

People present (lines …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 17 November 2020 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://discourse.ubuntu.com/t/cloud-init-statue-11-17-20/19391 - LINK: https://github.com/canonical/cloud-init/pull/655 i'd …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 08 September 2020 in status-meeting-minutes - - - • 5 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-08-25.html#status-2020-08-25

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:21 …

-
- Continue reading -
-
- - - - - - - -
- - - - - - - - \ No newline at end of file diff --git a/category/status-meeting-minutes2.html b/category/status-meeting-minutes2.html deleted file mode 100644 index d452a84..0000000 --- a/category/status-meeting-minutes2.html +++ /dev/null @@ -1,391 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Category status-meeting-minutes - - - - -
- - - - - -
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 25 August 2020 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:27.

-

Recent Changes

-

The …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 28 July 2020 in status-meeting-minutes - - - • 3 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-07-14.html#status-2020-07-14

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:58 …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 14 July 2020 in status-meeting-minutes - - - • 5 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-06-30.html#status-2020-06-30

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:55 …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 30 June 2020 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-06-16.html#status-2020-06-16

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:28 …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 16 June 2020 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:24.

-

In-progress Development

-

The …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 02 June 2020 in status-meeting-minutes - - - • 8 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:24.

-

Recent Changes

-

The …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 19 May 2020 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-05-05.html#status-2020-05-05

-

#cloud-init pull-requests https://git.io/JeVed | Meeting minutes: https://goo.gl …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 05 May 2020 in status-meeting-minutes - - - • 4 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:20.

-

Recent Changes

-

The …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 14 April 2020 in status-meeting-minutes - - - • 4 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-03-31.html#status-2020-03-31

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:23 …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 31 March 2020 in status-meeting-minutes - - - • 4 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-03-10.html#status-2020-03-10

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:22 …

-
- Continue reading -
-
- - - - - - - -
- - - - - - - - \ No newline at end of file diff --git a/category/status-meeting-minutes3.html b/category/status-meeting-minutes3.html deleted file mode 100644 index aaf7604..0000000 --- a/category/status-meeting-minutes3.html +++ /dev/null @@ -1,392 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Category status-meeting-minutes - - - - -
- - - - - -
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 10 March 2020 in status-meeting-minutes - - - • 9 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-02-18.html#status-2020-02-18

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:24 …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 18 February 2020 in status-meeting-minutes - - - • 5 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-02-04.html#status-2020-02-04

-

Previous Actions

-

The discussion about "Previous Actions" started at 17:37 …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 04 February 2020 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Previous Actions

-

The discussion about "Previous Actions" started at 17:27.

-

Recent Changes

-

The …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 21 January 2020 in status-meeting-minutes - - - • 5 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Previous Actions

-

The discussion about "Previous Actions" started at 17:50.

-
    -
  • LINK: bugs.launchpad …
-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 07 January 2020 in status-meeting-minutes - - - • 11 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2019-12-10.html#status-2019-12-10

-

Previous Actions

-

The discussion about "Previous Actions" started at 17:36 …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 10 December 2019 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 17:22.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 26 November 2019 in status-meeting-minutes - - - • 9 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 17:28.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 29 October 2019 in status-meeting-minutes - - - • 12 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:26.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 08 October 2019 in status-meeting-minutes - - - • 9 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:23.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 09 September 2019 in status-meeting-minutes - - - • 5 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2019-08-19.html#status-2019-08-19

-

Previous actions

-

The discussion about "Previous actions" started at 16:30 …

-
- Continue reading -
-
- - - - - - - -
- - - - - - - - \ No newline at end of file diff --git a/category/status-meeting-minutes4.html b/category/status-meeting-minutes4.html deleted file mode 100644 index 4a526b1..0000000 --- a/category/status-meeting-minutes4.html +++ /dev/null @@ -1,391 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Category status-meeting-minutes - - - - -
- - - - - -
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 19 August 2019 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2019-08-05.html#status-2019-08-05

-

cloud-init Reviews: http://bit.ly/ci-reviews | Meeting minutes: https://goo.gl …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 05 August 2019 in status-meeting-minutes - - - • 5 min read -

-
-
-

Meeting information

- -

Meeting summary

-

#cloud-init Reviews: http://bit.ly/ci-reviews | Meeting minutes: https://goo.gl/mrHdaj | Next status meeting Aug 19 16:15 …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 22 July 2019 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:17.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 08 July 2019 in status-meeting-minutes - - - • 10 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:18.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 24 June 2019 in status-meeting-minutes - - - • 10 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:23.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 10 June 2019 in status-meeting-minutes - - - • 11 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:23.

-

Recent Changes

-

The …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 28 May 2019 in status-meeting-minutes - - - • 4 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 15:27.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 13 May 2019 in status-meeting-minutes - - - • 14 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:31.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 28 January 2019 in status-meeting-minutes - - - • 5 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:27.

-
    -
  • ACTION: carry over blackboxsw close and land Openstack …
-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 07 January 2019 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:38.

- -
- Continue reading -
-
- - - - - - - -
- - - - - - - - \ No newline at end of file diff --git a/category/status-meeting-minutes5.html b/category/status-meeting-minutes5.html deleted file mode 100644 index b16022e..0000000 --- a/category/status-meeting-minutes5.html +++ /dev/null @@ -1,398 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Category status-meeting-minutes - - - - -
- - - - - -
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 10 December 2018 in status-meeting-minutes - - - • 4 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:13.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 26 November 2018 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io - LINK: https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427 - LINK: https://code …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 12 November 2018 in status-meeting-minutes - - - • 4 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:20.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 29 October 2018 in status-meeting-minutes - - - • 4 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:22.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 15 October 2018 in status-meeting-minutes - - - • 9 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:18.

- -

Recent Changes

-

The …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 25 September 2018 in status-meeting-minutes - - - • 5 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:09.

-

Recent Changes

-

The discussion about "Recent Changes …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 04 September 2018 in status-meeting-minutes - - - • 5 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/ - LINK: https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin - LINK: https://powersj.github.io/post …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 20 August 2018 in status-meeting-minutes - - - • 4 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:13.

-

Recent Changes

-

The discussion about "Recent Changes …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 06 August 2018 in status-meeting-minutes - - - • 5 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:09.

-
    -
  • ACTION: rharper …
-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 02 July 2018 in status-meeting-minutes - - - • 4 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:09.

- -
- Continue reading -
-
- - - - - - - -
- - - - - - - - \ No newline at end of file diff --git a/category/status-meeting-minutes6.html b/category/status-meeting-minutes6.html deleted file mode 100644 index 190e467..0000000 --- a/category/status-meeting-minutes6.html +++ /dev/null @@ -1,393 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Category status-meeting-minutes - - - - -
- - - - - -
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 18 June 2018 in status-meeting-minutes - - - • 8 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:11.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 29 May 2018 in status-meeting-minutes - - - • 10 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:09.

-

Recent Changes …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 14 May 2018 in status-meeting-minutes - - - • 7 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:09.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 30 April 2018 in status-meeting-minutes - - - • 12 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:07.

-

#cloud-init Reviews: http://bit.ly/ci-reviews | Meeting …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 16 April 2018 in status-meeting-minutes - - - • 8 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent-changes

-

The discussion about "Recent-changes" started at 16:04.

-

In-progresss Development

-

The discussion about "In-progresss Development" started at …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 02 April 2018 in status-meeting-minutes - - - • 5 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:08.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 19 March 2018 in status-meeting-minutes - - - • 11 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:05.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 05 March 2018 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent Changes

-

The discussion about "Recent Changes" started at 17:02.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Fri 16 February 2018 in status-meeting-minutes - - - • 7 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent changes

-

The discussion about "Recent changes" started at 16:08.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 22 January 2018 in status-meeting-minutes - - - • 8 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent changes

-

The discussion about "Recent changes" started at 16:10.

- -
- Continue reading -
-
- - - - - - - -
- - - - - - - - \ No newline at end of file diff --git a/category/status-meeting-minutes7.html b/category/status-meeting-minutes7.html deleted file mode 100644 index b2be97c..0000000 --- a/category/status-meeting-minutes7.html +++ /dev/null @@ -1,341 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Category status-meeting-minutes - - - - -
- - - - - -
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 08 January 2018 in status-meeting-minutes - - - • 11 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent changes

-

The discussion about "Recent changes" started at 16:04.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 11 December 2017 in status-meeting-minutes - - - • 13 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:07.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 13 November 2017 in status-meeting-minutes - - - • 7 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:04

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 30 October 2017 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent Changes

-

The discussion about “Recent Changes” started at 16:04.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 16 October 2017 in status-meeting-minutes - - - • 4 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:08

-

In Progress Development

-

The discussion about "In Progress Development …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 02 October 2017 in status-meeting-minutes - - - • 10 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent Changes / Highlights

-

The discussion about "Recent Changes / Highlights" started at 16:06.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 18 September 2017 in status-meeting-minutes - - - • 3 min read -

-
-
-

Meeting information

- -

Meeting summary

- -

Release Preparation

-

The discussion …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 05 September 2017 in status-meeting-minutes - - - • 1 min read -

-
-
-

Meeting information

-

* #cloud-init: cloud-init status meeting, 05 Sep at 16:30 — 16:30 UTC

-

Meeting summary

-

LINK: https://public.etherpad-mozilla.org/p/cloud-init-meeting

-

*Recent Changes(16:35)

-
    -
  • integration of robjo's opensuse items
  • -
  • summit results posted to mailing list https://lists.launchpad.net/cloud-init/msg00094.html
  • -
-

LINK: https://lists.launchpad.net …

-
- Continue reading -
-
- - - - - - - -
- - - - - - - - \ No newline at end of file diff --git a/cloud-init-githubio-details.html b/cloud-init-githubio-details.html deleted file mode 100644 index 9beb1da..0000000 --- a/cloud-init-githubio-details.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init github.io details - - - - -
- - - -
-
- -

Cloud-init github.io details

-

- Posted on Tue 05 September 2017 in Background - - • 1 min read -

-
- - -
-

Cloud-init project info page

-

Cloud-init dev team created a github.io project page based on pelican and Flex theme to host cloud-init status meeting notes.

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/content/details.md b/content/details.md new file mode 100644 index 0000000..c8e69bb --- /dev/null +++ b/content/details.md @@ -0,0 +1,8 @@ +Title: Cloud-init github.io details +Date: 2017-09-05 16:30:00 +Category: Background + +Cloud-init project info page +---------------------------- + +Cloud-init dev team created a github.io project page based on pelican and Flex theme to host cloud-init status meeting notes. diff --git a/images/cloud-init-orange.svg b/content/images/cloud-init-orange.svg similarity index 100% rename from images/cloud-init-orange.svg rename to content/images/cloud-init-orange.svg diff --git a/content/status-2017-09-05.md b/content/status-2017-09-05.md new file mode 100644 index 0000000..858b471 --- /dev/null +++ b/content/status-2017-09-05.md @@ -0,0 +1,62 @@ +Title: Cloud-init bi-weekly status +Date: 2017-09-05 16:30:00 +Category: status-meeting-minutes +Slug: status-2017-09-05 + +Meeting information +------------------- + +`* #cloud-init: cloud-init status meeting, 05 Sep at 16:30 — 16:30 UTC` + +Meeting summary +--------------- + +*LINK:* + +`* `**`Recent Changes`**` (16:35)` + + * integration of robjo's opensuse items + * summit results posted to mailing list https://lists.launchpad.net/cloud-init/msg00094.html + +*LINK:* + +`* `**`In Progress Development`**` (16:38)` + + * *LINK:* + * *LINK:* + * Opensuse builds: *LINK:* + * Ongoing SRU for ubuntu: *LINK:* + * Meetingology to join for next meeting + +`* `**`Open Discussion- cloud-init versioning`**` (16:41)` + + * Will target a new versioned release Sept 21st + * cloud-init will have major.minor versioning represented by <2-digit-year>.. The version will be 1-based and increment with each quarterly release. + * *ACTION* smoser to write to mailing list with that as the plan and suggesting the target release date of 17.1 on the Sept 21. + * cloud-init releases will target quarterly cycles + +`* `**`Office Hours`**` (15:15)` + + +Vote results +------------ + +Done items +---------- + +`* (none)` + +People present (lines said) +--------------------------- + +`* blackboxsw` +`* smoser` +`* powersj` +`* rharper` +`* dpb1` + +Full Log +-------- + +*LINK:* + diff --git a/content/status-2017-09-18.md b/content/status-2017-09-18.md new file mode 100644 index 0000000..0700bd4 --- /dev/null +++ b/content/status-2017-09-18.md @@ -0,0 +1,200 @@ +Title: Cloud-init bi-weekly status +Date: 2017-09-18 16:04:00 UTC +Category: status-meeting-minutes +Slug: status-2017-09-18 + +Meeting information +---------------- + * \#cloud-init: cloud-init status meeting, 18 Sep at 16:04 — 16:27 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-09-18-16.04.log.html](http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-09-18-16.04.log.html)]] + + + +Meeting summary +---------------- + + * **LINK**: [https://public.etherpad-mozilla.org/p/cloud-init-meeting](https://public.etherpad-mozilla.org/p/cloud-init-meeting) + * **LINK**: [https://lists.launchpad.net/cloud-init/msg00100.html](https://lists.launchpad.net/cloud-init/msg00100.html) +### Release Preparation +The discussion about "Release Preparation" started at 16:08. + + * '''Release Preparation''' (16:08) + * * **LINK**: [http://bit.ly/ci-reviews](http://bit.ly/ci-reviews) + +### Open Discussion +The discussion about "Open Discussion" started at 16:14. + + * * **LINK**: [https://launchpad.net/bugs/1717598](https://launchpad.net/bugs/1717598) + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * smoser (41) + * blackboxsw (8) + * ubot5 (4) + * ajorg (4) + * robjo (4) + * meetingology (3) + * dpb1 (3) + * rharper (1) + + + +Full Log +---------------- + + + 16:04 ` \#startmeeting cloud-init status meeting + + 16:04 ` Meeting started Mon Sep 18 16:04:28 2017 UTC. The chair is smoser. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:04 ` + + 16:04 ` Available commands: action commands idea info link nick + + 16:05 ` hiya o/ + + 16:05 ` o/ + + 16:05 ` \#link [https://public.etherpad-mozilla.org/p/cloud-init-meeting](https://public.etherpad-mozilla.org/p/cloud-init-meeting) + + 16:05 ` hello + + 16:05 ` so that contains a agenda that we'd been following + + 16:06 ` \#link [https://lists.launchpad.net/cloud-init/msg00100.html](https://lists.launchpad.net/cloud-init/msg00100.html) + + 16:07 ` sorry for slow going here. + + 16:08 ` shoot + + 16:08 ` \#topic Release Preparation + + 16:08 ` \#subtopic Release Preparation + + 16:08 ` hm.. + + 16:09 ` anyway + + 16:09 ` [https://lists.launchpad.net/cloud-init/msg00100.html](https://lists.launchpad.net/cloud-init/msg00100.html) + + 16:09 ` that is the primariy point of this meeting for today. + + 16:09 ` The goal is to make a release named 17.1 on Thursday of this week. + + 16:09 ` strange + + 16:09 ` We have landed several branches in the last few days, and have 2 more to land at least. + + 16:10 ` from [http://bit.ly/ci-reviews](http://bit.ly/ci-reviews) + + 16:10 ` meetingology │ Available commands: action commands idea info link nick + + 16:10 ` something to look into. :) + + 16:10 ` \#link [http://bit.ly/ci-reviews](http://bit.ly/ci-reviews) + + 16:10 ` the two we consider needs to be integrated are + + 16:10 ` [https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/330875](https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/330875) + + 16:10 ` [https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/330880](https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/330880) + + 16:11 ` and Chad's (the first) is the one we're looking at now. + + 16:11 ` or that is the one that is non-trivial + + 16:11 ` does anyone here wnat to raise other bugs or MP that they believe should be pulled ? + + 16:12 ` ... + + 16:12 ` ajorg, i think its best to hold off on some of yours until after release. + + 16:13 ` anyone have anything else ? + + 16:13 ` msaika (vmware) pinged on a branch a couple days ago. but I think there is a little of discussion/re-work that's needed there before we land + + 16:13 ` smoser: I assume you mean the instance identity one, in which case I agree. + + 16:13 ` (in either case I'd agree) + + 16:13 ` and simpletable + + 16:13 ` yeah + + 16:14 ` ok. so that is where we are. we are still targettin a release on Thursday. + + 16:14 ` other than that, i thinkw e move on to open discussion or office hours + + 16:14 ` \#topic Open Discussion + + 16:14 ` anyone have anything for this ? + + 16:14 ` Customer has run into an issue where we run out of threads during the user script phase, should generally set TasksMax in the service file, i.e. is that of interest upstream? + + 16:15 ` we are still testing, but that appears to be the solution for this particular problem + + 16:15 ` robjo, i dont have an immediate objection to that idea. + + 16:16 ` could you open a bug ? + + 16:16 ` sure + + 16:17 ` i dont think that we'd want to pull that change in right now, but it otherwise seems reasonable at frist b lush. + + 16:18 ` anything else ? + + 16:18 ` Agreed, do't think this is sufficiently urgent for Thursday's release, it can wait until the next one + + 16:19 ` were there other bugs that we should consider high enough prio to deserve landing a fix in the release? + + 16:20 ` ajorg, the only 2 that i'm aware of are linked in those mp. i can dig the numbers + + 16:21 ` * bug 1717598 + + 16:21 ` bug 1717598 in cloud-init (Ubuntu) "Traceback when passing user-data on GCE" [High,In progress] [https://launchpad.net/bugs/1717598](https://launchpad.net/bugs/1717598) + + 16:21 ` * bug 1717627 + + 16:21 ` bug 1717627 in cloud-init "permission denied when executing dhclient in Ec2 datasource" [High,In progress] [https://launchpad.net/bugs/1717627](https://launchpad.net/bugs/1717627) + + 16:21 ` ok + + 16:22 ` Anything else? other wise i'll call this meeting done and hang around for office hours for the next 30 m inutes at least. + + 16:22 ` thanks for attending / feedback, robjo and ajorg + + 16:23 ` \#link [https://launchpad.net/bugs/1717598](https://launchpad.net/bugs/1717598) + + 16:23 ` Ubuntu bug 1717598 in cloud-init (Ubuntu) "Traceback when passing user-data on GCE" [High,In progress] + + 16:24 ` \#link[https://launchpad.net/bugs/1717627](https://launchpad.net/bugs/1717627) + + 16:24 ` Ubuntu bug 1717627 in cloud-init "permission denied when executing dhclient in Ec2 datasource" [High,In progress] + + 16:24 ` just in case + + 16:24 ` duno whats up with the bot.... again + + 16:27 ` ok. well, lets move on + + 16:27 ` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2017-10-02.md b/content/status-2017-10-02.md new file mode 100644 index 0000000..545e49f --- /dev/null +++ b/content/status-2017-10-02.md @@ -0,0 +1,480 @@ +Title: Cloud-init bi-weekly status +Date: 2017-10-02 16:05:00 UTC +Category: status-meeting-minutes +Slug: status-2017-10-02 + +Meeting information +---------------- + * \#cloud-init: cloud-init, 02 Oct at 16:05 — 17:29 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-10-02-16.05.log.html](http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-10-02-16.05.log.html)]] + + + +Meeting summary +---------------- + +### Recent Changes / Highlights +The discussion about "Recent Changes / Highlights" started at 16:06. + + * **LINK**: [https://lists.launchpad.net/cloud-init/msg00106.html](https://lists.launchpad.net/cloud-init/msg00106.html) + * **LINK**: [https://launchpad.net/cloud-init/+milestone/17.2](https://launchpad.net/cloud-init/+milestone/17.2) + * please target bugs to the next release + +### In Progress Development / Highlights +The discussion about "In Progress Development / Highlights" started at 16:09. + + * **LINK**: [http://bit.ly/ci-reviews](http://bit.ly/ci-reviews) + * **LINK**: ? + * **LINK**: [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + * **LINK**: [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/taskLimit](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/taskLimit) that's the branch for the task limit + * **LINK**: [https://bugs.launchpad.net/cloud-init](https://bugs.launchpad.net/cloud-init) + * **LINK**: [http://bit.ly/ci-reviews](http://bit.ly/ci-reviews) + +### Open Discussion / Office Hours +The discussion about "Open Discussion / Office Hours" started at 16:17. + + * **LINK**: [http://paste.ubuntu.com/25661692/](http://paste.ubuntu.com/25661692/) + * **LINK**: [http://paste.ubuntu.com/25661714/](http://paste.ubuntu.com/25661714/) + * **LINK**: [https://bugs.launchpad.net/cloud-init/+bug/1720841](https://bugs.launchpad.net/cloud-init/+bug/1720841) + * **LINK**: [https://bugs.launchpad.net/cloud-init/+bug/1720841](https://bugs.launchpad.net/cloud-init/+bug/1720841) + * **LINK**: [https://code.launchpad.net/~ajorgens/cloud-init/+git/cloud-init/+merge/330525](https://code.launchpad.net/~ajorgens/cloud-init/+git/cloud-init/+merge/330525) ;-) + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * smoser (88) + * ajorg (51) + * rharper (28) + * blackboxsw (25) + * robjo (4) + * ubot5 (3) + * meetingology (3) + + + +Full Log +---------------- + + + 16:05 ` \#startmeeting cloud-init + + 16:05 ` Meeting started Mon Oct 2 16:05:47 2017 UTC. The chair is smoser. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:05 ` + + 16:05 ` Available commands: action commands idea info link nick + + 16:06 ` \#topic Recent Changes / Highlights + + 16:06 ` hm.. + + 16:06 ` 17.1 released [https://lists.launchpad.net/cloud-init/msg00106.html](https://lists.launchpad.net/cloud-init/msg00106.html) + + 16:06 ` thats the biggest thing and only thing i have for this topic + + 16:06 ` \#link [https://lists.launchpad.net/cloud-init/msg00106.html](https://lists.launchpad.net/cloud-init/msg00106.html) + + 16:06 ` horay for a release, thanks to those who contributed. + + 16:07 ` \o/ + + 16:07 ` 17.2 is set for 2017-12-14 + + 16:08 ` [https://launchpad.net/cloud-init/+milestone/17.2](https://launchpad.net/cloud-init/+milestone/17.2) + + 16:08 ` yay! + + 16:08 ` feel free to target bugs to that release. + + 16:08 ` \#link [https://launchpad.net/cloud-init/+milestone/17.2](https://launchpad.net/cloud-init/+milestone/17.2) + + 16:08 ` \#info please target bugs to the next release + + 16:09 ` does that do anyting ? + + 16:09 ` in the meeting summary, it does + + 16:09 ` smoser: the links showed up in meeting minutes last time + + 16:09 ` k. i always expected the bot to tell me that in a pm + + 16:09 ` meetingology didn't echo though + + 16:09 ` well, smoser may have to do those + + 16:09 ` \#topic In Progress Development / Highlights + + 16:09 ` same. but something is up that needs attention. + + 16:10 ` I'll properly handle it when publishing + + 16:10 ` cool + + 16:11 ` Merge Proposals + + 16:11 ` \#link [http://bit.ly/ci-reviews](http://bit.ly/ci-reviews) + + 16:11 ` there are some there for sure. i know that robjo has some he's interested in, and i think ajorg's instance-identity deserves a look + + 16:12 ` as well as simpletable for 17.2 + + 16:12 ` I'd be grateful for both, yes. + + 16:12 ` i am looking at the 'networkd' one which is a blocker as currently Ubuntu does not work properly on azure + + 16:12 ` we should have more bandwidth this week + + 16:12 ` and all sysstemd-networkd systems will not work properly on CloudStack. + + 16:12 ` anything else there? + + 16:13 ` The task limit increase has been tested and solves our problem, thus merging would be great + + 16:13 ` robjo, yeah. athat does seem unlikely to cause issue + + 16:13 ` Trello Board + + 16:13 ` \# [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + + 16:13 ` \#link ? + + 16:13 ` \#link [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + + 16:14 ` [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/taskLimit](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/taskLimit) that's the branch for the task limit + + 16:15 ` Sorry, I can never find the link for the open merge proposals :( problem exists between the keyboard and the chair + + 16:16 ` will get eyes on that today robjo as your addZypper is about wrapped + + 16:16 ` Bugs + + 16:16 ` \#link [https://bugs.launchpad.net/cloud-init](https://bugs.launchpad.net/cloud-init) + + 16:16 ` just mostly pointers... above. + + 16:16 ` for Ubuntu in 16.04, there is one SRU in progress that blackboxsw and i need to verify today + + 16:16 ` and then we will be soon looking at doing an SRU of 17.1-ish + + 16:17 ` Thanks, still in europe, my day is about done, will pick it up tomorrow + + 16:17 ` robjo, link is in topic + + 16:17 ` [http://bit.ly/ci-reviews](http://bit.ly/ci-reviews) + + 16:17 ` ok. so open discussion i guess. no w? + + 16:17 ` \#topic Open Discussion / Office Hours + + 16:17 ` we'll hang around and pay attention to pings and discussion fro the next 30 minutes or so. + + 16:18 ` and after that, feel free to ping. + + 16:19 ` I'm writing a unit test for a bugfix I'm preparing to submit. It works, but it's slow because readurl retries and waits a second each time + + 16:20 ` I'm a bit of a mock / patch newb. Anyone can help me see how to patch that argument? + + 16:20 ` you can feel free to mock readurl + + 16:20 ` and set its return_value and look at calls + + 16:21 ` then you dont have to httppretty. + + 16:21 ` The only thing I want to change about it is the sleep though. Is there a straightforward way to just change one arg? + + 16:21 ` tests/unittests/test_handler/test_handler_chef.py is an example and tests/unittests/test_datasource/test_maas.py + + 16:21 ` I think + + 16:21 ` Hmm, I could do that, yeah. Would be sufficient for this. + + 16:22 ` I'd still like to know if there's an easy way to just change one argument to something that gets called somewhere else. + + 16:22 ` you could also mock the time.sleep from url_helper + + 16:22 ` hahaha, yes. that's what I need to do. + + 16:22 ` ajorg: if you want to mock the sleep you can decorate the test_ method with @mock.patch(time.sleep) + + 16:22 ` we're suggesting other ways generally because there isn't :) at least that i know of. + + 16:23 ` that's cool, patching time.sleep will do nicely + + 16:24 ` is there an integration test that looks at what lands on the console? + + 16:24 ` (going back to my question from before the meeting) + + 16:25 ` no. there coudl be on the nocloud-kvm backend + + 16:25 ` but i think there is no console access currently on lxd + + 16:25 ` and i think that we do not collect console access on nocloud-kvm + + 16:25 ` but as you suggest we should for sure + + 16:25 ` k + + 16:26 ` I wondered if systemd might be swallowing my output, or maybe python (boothook in this case is a python script) is making a strange choice when it sets up logging. + + 16:27 ` certainly possible; I know there were issues with cloud-init starting before say rsyslog on non-systemd boots + + 16:28 ` and the python logging has changed w.r.t the default configuration; cloud-init main sort of expects this transition as it starts up in init-local and it has not yet read the cloud-config for logging configuration yet, so it reads that and then does some replay + + 16:28 ` interesting + + 16:29 ` ajorg, you're writing to stdout/err with logging from a boothook ? + + 16:29 ` at least I would have thought cloud-init-output.log would contain my logs though, since it's more a redirect of stderr and stdout, right? + + 16:29 ` yeah + + 16:29 ` correct + + 16:29 ` this is from a bootcmd ? + + 16:29 ` no, \#cloud-boothook + + 16:29 * rharper hasn't used boothook + + 16:29 ` hm.. + + 16:30 ` boothooks are super useful + + 16:32 ` smoser: when do boot_hooks run ? local ? net ? + + 16:33 ` I'm not sure yet where stdout/err for boot hooks occur, but you can dump each from the units via: journalctl -u cloud-init-local.service (or cloud-init.service) + + 16:33 ` "This is the earliest hook available. Note, that there is no mechanism provided for running only once" + + 16:34 ` I'm checking the code now (local/pre-local maybe)? + + 16:34 ` yeah, saw that; it runs in-image scripts programs + + 16:34 ` I did that too, and don't see anything. + + 16:34 ` (journalctl) + + 16:34 ` you should see some output + + 16:34 ` but not seeing your hook in there ? + + 16:34 ` I can tell by other means that the hook ran + + 16:34 ` just don't see that it printed anything + + 16:35 ` my prime suspect if systemd can't do something bad here is that python makes some decision about not actually logging. + + 16:35 ` and I need to be more explicit that it should log + + 16:36 ` so, the boot_hook will sub out each part, I see no capture on the stderr/stdout ; so I would expect those to go to whatever is currently capturing those; + + 16:37 ` s/sub/subprocess + + 16:38 ` yup, that's what I expect too, and what I recall seeing on Amazon Linux + + 16:38 ` since it's using cloud-init's util.subp, there *should* be a debug level message saying 'Running command %s with allowed return codes %s' which maches a path to the boothook + + 16:38 ` I would expect to see that in the cloud-init.log + + 16:39 ` [http://paste.ubuntu.com/25661692/](http://paste.ubuntu.com/25661692/) + + 16:39 ` yup, I do see that + + 16:39 ` the output of script, I *think* should go to cloud-init-output.log + + 16:39 ` i'm testing ^ on serverstack now. + + 16:39 ` i verified the commands run on lxd but not look at console there. + + 16:39 ` thanks + + 16:40 ` actually.. yeah, BOOTHOOK does run, but doesnt seem to have stdout tied to same place as bootcmd + + 16:41 ` oh? + + 16:41 ` I'm slightly surprised it's not just me + + 16:42 ` [http://paste.ubuntu.com/25661714/](http://paste.ubuntu.com/25661714/) + + 16:42 ` it really should be in the journal/console if stdout is not redirected to a file, cloud-init-local service + + 16:43 ` that reproduces in lxc + + 16:44 ` smoser: in your instance on serverstack, do you see your BOOTHOOK in journalctl -b -u cloud-init-local.service ? + + 16:44 ` ajorg, please go ahead and open a bug. + + 16:44 ` cool (not cool :-P) + + 16:44 ` will do + + 16:44 ` \# journalctl -b -u cloud-init.service | grep BOOT + + 16:44 ` Oct 02 16:37:41 a5 cloud-init[121]: BOOTCMD: Mon, 02 Oct 2017 16:37:41 +0000: a5 + + 16:44 ` ^ that is from lxd + + 16:45 ` and what about the welcome message from cloud-init ? + + 16:45 ` i think not. + + 16:45 ` bootcmd does: util.subp(cmd, env=env, capture=False) ; where boot_hook does: util.subp([filepath], env=env) + + 16:46 ` yeah, so boot_hook definitely swallowed. and should not be. + + 16:47 ` yeah + + 16:49 ` [https://bugs.launchpad.net/cloud-init/+bug/1720841](https://bugs.launchpad.net/cloud-init/+bug/1720841) + + 16:49 ` Ubuntu bug 1720841 in cloud-init "Output from boothook is not logged" [Undecided,New] + + 16:50 ` Meanwhile I need to setup more explicit logging from that boothook anyway, so I'm okay. + + 16:51 ` \#link [https://bugs.launchpad.net/cloud-init/+bug/1720841](https://bugs.launchpad.net/cloud-init/+bug/1720841) + + 16:51 ` Ubuntu bug 1720841 in cloud-init "Output from boothook is not logged" [Medium,Confirmed] + + 16:55 ` Here's another one, which I've confirmed with a unit test and proposed a patch: [https://bugs.launchpad.net/cloud-init/+bug/1720844](https://bugs.launchpad.net/cloud-init/+bug/1720844) + + 16:55 ` Ubuntu bug 1720844 in cloud-init "UrlError from \#include aborts stage" [Undecided,New] + + 16:55 ` (what is this \#link thing you're doing there?) + + 16:55 ` well, the bot is supposed to care and do somethign with it. + + 16:56 ` but /me thinks it doesnt work right :) + + 16:56 ` ajorg: since meetingology is still active, the theory is it is keeping track of links during this meeting + + 16:56 ` (during the meeting) + + 16:56 ` ah, okay + + 16:57 ` I think simpletable is completely ready to merge, btw. Any objections? [https://code.launchpad.net/~ajorgens/cloud-init/+git/cloud-init/+merge/330525](https://code.launchpad.net/~ajorgens/cloud-init/+git/cloud-init/+merge/330525) + + 16:57 ` The theory is it writes the meeting notes out for us so we can publish to [https://cloud-init.github.io](https://cloud-init.github.io) + + 16:57 ` \#link [https://code.launchpad.net/~ajorgens/cloud-init/+git/cloud-init/+merge/330525](https://code.launchpad.net/~ajorgens/cloud-init/+git/cloud-init/+merge/330525) ;-) + + 16:57 ` geg + + 16:57 ` heh + + 16:58 ` ajorg: I think we were good on that changeset, and we only wanted to wait post 17.1 cut to avoid potential regression + + 16:59 ` great + + 16:59 ` I'm +1 on that will give it a spin today and then I think we can land it + + 17:01 ` blackboxsw, ajorg my thoughts on the simpletable... + + 17:01 ` here it comes... + + 17:01 ` :-P + + 17:01 ` :) + + 17:02 ` i would like to have a machine friendly output available + + 17:02 ` human friendly is good, but machine friendly solves the actual goal of writing the stuff. + + 17:02 ` So I modified it to display *exactly* as prettytable did + + 17:02 ` oh really. + + 17:02 ` wow + + 17:02 ` which is admittedly not machine friendly + + 17:02 ` not especially + + 17:02 ` then i guess i can't object at all. + + 17:02 ` but it's at least as good as prettytable + + 17:03 ` in that its backwards compat + + 17:03 ` right. + + 17:03 ` ^ this was my goal, to get you to not object + + 17:03 ` i still think we should probaly additionally write some machine friendly json + + 17:03 ` agreed, that would be better + + 17:03 ` i tihnk having something human friendly is good though + + 17:03 ` as i know *I* look at that output + + 17:04 ` it meets my goal of not depending on prettytable + + 17:04 ` and parsing json would be less nice + + 17:04 ` yeah + + 17:05 ` so based on your assertion that it outputs the same as pretty table, i have no objections. only future hopes. + + 17:05 ` and i do agree dropping pretty table is nice + + 17:05 ` winning + + 17:06 ` smoser: yeah I was wondering how we generally expect people/machines to parse cloud-init-output.log. Right now it's kindof hard to do machine parsing of cloud-init-output.log. + + 17:07 ` blackboxsw, yeah. cloud-init-output.log is not intended to be machine friendly. + + 17:07 ` do we know already of non-human consumers of the formatting in cloud-init.output.log? + + 17:07 ` but the console actually has value in having machien friendly things on it. + + 17:08 ` my feeling is if you have access to /var/log/cloud-init.log, then you could very easily have written whatever you wanted to another file that was purely machine friendly. + + 17:08 ` was wondering where we would intend to dump machine-friendly json + + 17:08 ` yeah + + 17:08 ` but the console (/dev/ttyS0) boot log is different + + 17:08 ` in that it can give you a couple things you'd not find easy access to + + 17:09 ` a.) ssh public keys for the system (providing out of band communication of this data) + + 17:09 ` b.) network configuration info: providn useful bits of data on how you might get to this system + + 17:10 ` systemd makes it "fun" to get that data to the console in a safe way + + 17:12 ` ugh yes. systemd like to stomp all over your consoles. + + 17:19 ` ok so did we want to iterate on simpletable to dump json, or just look for cloud-init to write supplementary json files under /run/cloud-init + + 17:20 ` .. after we land ajorg's branch + + 17:21 ` I think it's a good idea to dump json fragments to console for some things, but I suspect smoser will still not want to break anyone who might be using the tables, so probably best to land my branch as-is + + 17:23 ` yeah, i agree with ajorg. for now, we can just take a replacement that drops prettytable + + 17:23 ` there are improvments to be done there, but this is a simple win + + 17:29 ` we'll go ahead and end meeting here. + + 17:29 ` i'll still be around. thanks all! + + 17:29 ` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) diff --git a/content/status-2017-10-16.md b/content/status-2017-10-16.md new file mode 100644 index 0000000..b939856 --- /dev/null +++ b/content/status-2017-10-16.md @@ -0,0 +1,201 @@ +Title: Cloud-init bi-weekly status +Date: 2017-10-16 16:06:00 UTC +Category: status-meeting-minutes +Slug: status-2017-10-16 + +Meeting information +---------------- + * \#cloud-init: Office Hours, 16 Oct at 16:06 — 17:03 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-10-16-16.06.log.html](http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-10-16-16.06.log.html)]] + + + +Meeting summary +---------------- + + +### Recent Changes + +The discussion about "Recent Changes" started at 16:08 + +### In Progress Development + +The discussion about "In Progress Development" started at 16:13 + + * **LINK**: [http://bit.ly/ci-reviews](http://bit.ly/ci-reviews) + * **LINK**: [https://trello.com/c/wROS4mKT/458-sru-171](https://trello.com/c/wROS4mKT/458-sru-171) + * **LINK**: [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1722668](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1722668) + * **LINK**: [https://gist.github.com/smoser/49444542158f2e5f88f1/#file-lxc-pstart-md](https://gist.github.com/smoser/49444542158f2e5f88f1/#file-lxc-pstart-md) + * **LINK**: [https://bugs.launchpad.net/cloud-init/+bug/1722992](https://bugs.launchpad.net/cloud-init/+bug/1722992) + +### Office Hours + +The discussion about "Office Houres" started at 16:25 + + * open season for discussions, bug requests, review requests for the next 30 mins + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (49) + * smoser (8) + * ubot5 (3) + * meetingology (3) + * rharper (3) + + + +Full Log +---------------- + + + 16:06 ` \#startmeeting Cloud-init bi-weekly status + + 16:06 ` Meeting started Mon Oct 16 16:06:51 2017 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:06 ` + + 16:06 ` Available commands: action commands idea info link nick + + 16:08 ` \#topic Recent Changes + + 16:08 ` Ok last couple of weeks for our team were + + 16:08 ` Ok last couple of weeks for our team were + + 16:08 ` Ok last couple of weeks for our team were 'impacted' by a couple of work conferences for planning next release of cloud-init/curtin etc. + + 16:08 ` o/ + + 16:09 ` so things felt a bit slow. but folks have still made some good progress. + + 16:09 ` Some changes that have landed in master: + + 16:09 ` Robert Schweikert: suse cloud-config module to add zypper repos and zypp config + + 16:09 ` Robert Schweikert: Allow cloud-init.final stage to spawn infinite processes + + 16:09 ` Andrew Jorgensen: Remove prettytable dependency + + 16:09 ` Fix dhcp parsing in Artful of networkd leases for CloudStack and Azure + + 16:09 ` Updated packaging copyright file (LP: \#1718681) + + 16:09 ` Launchpad bug 1718681 in cloud-init "Package copyright file omits Apache 2 license" [High,Fix committed] [https://launchpad.net/bugs/1718681](https://launchpad.net/bugs/1718681) + + 16:10 ` o/ + + 16:10 ` thanks a lot for the contributions on that front folks. There have been a couple of work items that fell out of our conferences related to Ubuntu artful and systemd/networkd support so we've been workin those + + 16:11 ` on the testing front we've re-enable tox support for integration tests + + 16:11 ` and Ubuntu-only has queued a 17.1 SRU release/update into xenial and zesty + + 16:12 ` smoser: rharper powersj anyone else anything else I'm missing on recent changes? + + 16:12 ` blackboxsw: that sounds right + + 16:13 ` ok. next topic + + 16:13 ` \#topic In progress development + + 16:14 ` As mentioned, we are walking through the Ubuntu xenial/zesty SRU validation process, so I excpect we will have a release update published this week + + 16:14 * blackboxsw grabs the trello card link + + 16:14 ` \#link [https://trello.com/c/wROS4mKT/458-sru-171](https://trello.com/c/wROS4mKT/458-sru-171) + + 16:15 ` This card will move to the Done lane once we've finished publishing + + 16:16 ` I know powersj has been working the integration test front for KVM as time permits. There will be some upcoming changes there to get us more complex storage/network testing on kvm + + 16:16 ` I know smoser is also working on a couple of Azure-related fixes for artful as well. + + 16:16 ` anything else to add there? + + 16:17 ` [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1722668](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1722668) + + 16:17 ` nothing from me + + 16:17 ` Ubuntu bug 1722668 in cloud-init (Ubuntu) "Azure: bouncing of network device/publishing of hostname fails on artful" [Critical,Confirmed] + + 16:17 ` \#link [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1722668](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1722668) + + 16:18 ` thx + + 16:18 ` that one i'm working on, and then also been trying to get lxc/mount-image-callback + + 16:19 ` the use we ahve for 'lxc-proposed-snapshot' and also for 'mount-image-callback' + + 16:19 ` Also in the same vein of improving dev testing of Ubuntu or really any lxc image is that work smoser referenced above. + + 16:20 ` smoser: is that worth a link at the moment or does it still need polish? + + 16:20 ` [https://gist.github.com/smoser/49444542158f2e5f88f1/](https://gist.github.com/smoser/49444542158f2e5f88f1/)\#file-lxc-pstart-md + + 16:20 ` sweet + + 16:20 ` \#link [https://gist.github.com/smoser/49444542158f2e5f88f1/](https://gist.github.com/smoser/49444542158f2e5f88f1/)\#file-lxc-pstart-md + + 16:20 ` right now that is only known to work on lxc 2.18 + + 16:21 ` i think we can make it work with earlier versions, and would like to make it work with xenial (2.02.. maybe) + + 16:22 ` yeah I just got my artful box up and was going to use that for the SRU verification + + 16:22 ` also, I think we were going to peek at a solution for the following bug: + + 16:22 ` \#link [https://bugs.launchpad.net/cloud-init/+bug/1722992](https://bugs.launchpad.net/cloud-init/+bug/1722992) + + 16:22 ` Ubuntu bug 1722992 in cloud-init "On the latest centos 7 release, we are unable to resize our instances filesystems" [Medium,Confirmed] + + 16:23 ` so there might be some minor changes for the OpenStack/MAAS and ConfigDrive datasources + + 16:24 ` ok anything else in "In progress development"? + + 16:24 ` I know we have a queue of active reviews we need to get through. I was expecting we'll have bandwidth for that after this SRU push. + + 16:24 ` \#link [http://bit.ly/ci-reviews](http://bit.ly/ci-reviews) + + 16:25 ` \#topic Office Hours + + 16:26 ` \#info open season for discussions, bug requests, review requests for the next 30 mins + + 16:29 ` thanks blackboxsw + + 16:34 ` no prob. I was peeking around at puppet this weekend.... might have a branch puppet local(masterless deployment) to put up this week + + 16:34 ` I sort of got distracted by shiny objects while trying to write an SRU test for our existing puppet + + 16:34 ` config module + + 17:01 ` ok two more SRU tests left to write for Azure and datasourceOVF. then we can start validation for the upload + + 17:02 ` office hours coming to a close. but we'll still float in here as always. Happy Monday folks + + 17:02 ` just ping us directly by IRC nick if you aren't getting a response otherwise. + + 17:03 ` tanks again. + + 17:03 ` thanks even + + 17:03 ` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) diff --git a/content/status-2017-10-30.md b/content/status-2017-10-30.md new file mode 100644 index 0000000..ed77639 --- /dev/null +++ b/content/status-2017-10-30.md @@ -0,0 +1,276 @@ +Title: Cloud-init bi-weekly status +Date: 2017-10-30 16:03:00 UTC +Category: status-meeting-minutes +Slug: status-2017-10-30 + +Meeting information +---------------- + * \#cloud-init: Open Discussion / Office Hours (30 mins), 30 Oct at 16:03 — 17:00 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-10-30-16.03.log.html](http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-10-30-16.03.log.html)]] + + +Meeting summary +--------------- + +### Recent Changes + +The discussion about “Recent Changes” started at 16:04. + + * **LINK**: [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1721847](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1721847) + +### In Progess Development + +The discussion about “In Progress Development” started at 16:17. + + * **LINK**: [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + * **LINK**: [https://launchpad.net/bugs/1728152](https://launchpad.net/bugs/1728152) + +### Open Discussion / Office Hours (30 mins) + +The discussion about “Recent Changes” started at 16:30. + + * *LINK:* + + + +Vote results +------------ + +Done items +---------- + + +Meeting summary +---------------- + + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (61) + * smoser (10) + * ubot5 (8) + * powersj (6) + * robjo (6) + * meetingology (3) + * rharper (2) + * ckonstanski (1) + + + +Full Log +---------------- + + + 16:03 ` \#startmeeting cloud-init bi-weekly status + + 16:03 ` Meeting started Mon Oct 30 16:03:09 2017 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:03 ` + + 16:03 ` Available commands: action commands idea info link nick + + 16:04 ` \#topic In Progress Development + + 16:04 ` So, the last couple weeks have been fairly busy with Ubuntu an SRU processs for Xenial, Zesty and the new Artful release + + 16:05 ` our SRU process bug captures most of that work + + 16:05 ` \#LINK [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1721847](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1721847) + + 16:05 ` Ubuntu bug 1721847 in cloud-init (Ubuntu Zesty) "sru cloud-init 2017-10-06 (17.1-18-gd4f70470-0ubuntu1)" [Medium,Fix committed] + + 16:07 ` our teams uncovered at least one bug during verification testing + + 16:07 ` LINK [https://bugs.launchpad.net/cloud-init/+bug/1725067](https://bugs.launchpad.net/cloud-init/+bug/1725067) + + 16:07 ` Ubuntu bug 1725067 in cloud-init (Ubuntu Artful) "cloud-init resizefs fails when booting with root=PARTUUID=" [Medium,Fix committed] + + 16:08 ` The former bug we have now resolved. This SRU will not be published until we resolve one other bug for EC2-specfic environments to ensure we retain behavior to always bring up dhcp4 on the primary nic + + 16:09 ` I don't think we have created a bug for the ec2 issue yet (it affects artful only) instances with only private ipv4 addresses allocated will not have dhcp4 config'd for that instance + + 16:10 ` We'll link a bug for the above today + + 16:10 ` other work on cloud-init... paste coming + + 16:11 ` * Fix systemd mount target due to busy device or already mounted (LP: \#1718287) + + 16:11 ` * Fix simpleteable object as output string (LP: \#1722566) + + 16:11 ` * Fix netplan bridge stp boolean (LP: \#1721157) + + 16:11 ` * Fix cc_ntp to allow empty configuration "ntp:". Fix ntp integration test to provide valid empty ntp config (LP: 1724951) + + 16:11 ` * Fixed cc_lxd to allow for missing bridge definitions in lxd cloud-config + + 16:11 ` * Dropped fastestmirror plugin for CentOS tests + + 16:11 ` * Numerous test and CI stability improvements + + 16:11 ` Launchpad bug 1718287 in cloud-init "systemd mount targets fail due to device busy or already mounted" [High,Fix committed] [https://launchpad.net/bugs/1718287](https://launchpad.net/bugs/1718287) + + 16:11 ` Launchpad bug 1722566 in cloud-init "ci-info: `" [Medium,Fix committed] [https://launchpad.net/bugs/1722566](https://launchpad.net/bugs/1722566) + + 16:11 ` Launchpad bug 1721157 in cloud-init "netplan render drops bridge_stp setting" [High,Fix committed] [https://launchpad.net/bugs/1721157](https://launchpad.net/bugs/1721157) + + 16:11 ` Launchpad bug 1724951 in cloud-init "Ntp schema definition permits empty ntp cloud-config, but code disallows" [Medium,In progress] [https://launchpad.net/bugs/1724951](https://launchpad.net/bugs/1724951) + + 16:13 ` Also we got a couple of gentoo commits from ckonstanski to Use "rc-service" rather than "service". Thanks again + + 16:13 ` \o/ + + 16:14 ` You're welcome, though those were just tiny toy commits to get me indocrinated into the launchpad process. Getting NTP tests to work in gentoo will be more significant. + + 16:15 ` ckonstanski: testing always is time-consuming, but totally worth it. We are still trying build our unit test coverage up so we don't get suprises on different platforms/clouds when sparsely tested modules run. Thanks again + + 16:16 ` oops sorry about the topic for the above ... that should have been the following + + 16:16 ` \#topic Recent Changes + + 16:16 ` anything else for recent changes that have landed rharper powersj or others? + + 16:17 ` nope + + 16:17 ` blackboxsw: not yet + + 16:17 ` ok then let's move to next topic + + 16:17 ` \#meetingstatus In Progress Development + + 16:17 ` for real. + + 16:18 ` ok so we are wrapping up that one Ec2 bug that was raised by Sargun on friday (which affects Artful) + + 16:18 ` When we have that branch in place, we can kick our final validation of the cloud-init 17.1 updates to Xenial Zesty and Artful. + + 16:19 ` I know smoser just uploaded cloud-init to the newly opened Bionic release as well + + 16:19 ` We will be hitting the review queue a bit this week to wrap up content that we want landed once master is open for more dyna + + 16:20 ` We will be hitting the review queue a bit this week to wrap up content that we want landed once master is open for more significant changesets + + 16:21 ` we've been a little risk averse during the SRU release process + + 16:21 ` As always please watch our trello board for progress on anything we are working + + 16:21 ` LINK [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + + 16:22 ` need that \# + + 16:22 ` \#LINK [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + + 16:22 ` ahh thanks oops + + 16:23 ` speaking of reviews thanks for the help so far blackboxsw , now that my schedule should be a bit less crazy I'd like to get back to [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/addZyppRepos](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/addZyppRepos) + + 16:23 ` Our focus as well for the upcoming work in cloud-init is to increase continuous integration coverage and tooling around cloud-init to make sure we can keep delivering stability across releases + + 16:24 ` since I cannotreproduce the issue the bot has locally and I don't really understand the problem some more help is needed + + 16:24 ` ahh hiya robjo + + 16:24 ` that looks merged + + 16:24 ` robjo: good to hear, we'll watch for updates. + + 16:25 ` smoser went and fixed the flake8 issues + + 16:25 ` robjo: do you mean another branch? + + 16:25 ` blackboxsw: no, that branch, but bot thinks " Needs Fixing ", I just don't get why + + 16:26 ` yeah per robjo's work cloud-init folks can also configure zypper repos . We landed it Sept 21st. (So it's in cloud-init 17.1) + + 16:26 ` commit cc1475d07b9d0727012634ee9c7a914d67b051f5 + + 16:26 ` Author: Robert Schweikert ` + + 16:26 ` Date: Thu Sep 21 11:58:28 2017 -0400 + + 16:27 ` Oh, so it did get merged, missed that, never mind + + 16:27 ` as powersj mentioned, I think it was a flake8 CI test issue, so we just fixed the minor issue and landed it as it wasn't a significant content change + + 16:28 ` cloudinit/config/cc_zypper_add_repo.py:15:1: H306: imports not in alphabetical order (cloudinit.util, cloudinit.config.schema.get_schema_doc) + + 16:28 ` much appreciated, still a bit concerning that the flake8 issue did not show up locally :( + + 16:28 ` thx powersj + + 16:29 ` is correct way [https://paste.ubuntu.com/25852643/](https://paste.ubuntu.com/25852643/) + + 16:29 ` SO flake8 has serious issue with the definition of alpha order :( + + 16:30 ` ;) + + 16:30 ` ok anything else for "In Progress Development" if not we'll transition to the next topic + + 16:30 ` \#topic Open Discussion / Office Hours (30 mins) + + 16:31 ` ok we'll hang out in channel if anyone has topics, bugs or features they want to discuss or need some feedback on + + 16:35 ` and as always thanks for contributions folks. It's really great to work on a project where there is so much interest and investment + + 16:42 ` blackboxsw: hey. i'm back now. did you open a bug? + + 16:42 ` i can do so now if you have not. + + 16:43 ` smoser: I haven't done that yet, was just working out the fix + + 16:43 ` please do, then we can link it here + + 16:43 ` ok. i'll do so. and i realized a comment you were making about artful. + + 16:43 ` that we could go leave artful configuring all nics it saw. + + 16:43 ` right, because we allow change of behavior in artful right? + + 16:44 ` as that isn't necessarily "broken" behavior. + + 16:44 ` yeah. i didnt understand that when you said it. + + 16:44 ` ahh, I get you. Right, just that the new behavior of configuring all nics is acceptable as new behavior, but not for Xenial. It's just that artful is slightly busted for local-only ipv4 + + 16:45 ` i think it might be easiest both in terms of fixing and in terms of keeping things in our head if we just keep the same behavior everywhere for now. + + 16:46 ` that is... make artful act like xenial in only configuring one nic + + 16:48 ` blackboxsw: actually i dont think there is any reason why we shoudlnt just use bug 1728152 + + 16:48 ` bug 1728152 in cloud-init "IPv4 and IPv6 Dual Stack Does Not work when instance is not assigned public IPv4 address" [High,In progress] [https://launchpad.net/bugs/1728152](https://launchpad.net/bugs/1728152) + + 16:48 ` unless you disagree + + 16:51 ` +1 smoser + + 16:52 ` lets use that bug + + 16:59 ` \#LINK [https://launchpad.net/bugs/1728152](https://launchpad.net/bugs/1728152) + + 16:59 ` Ubuntu bug 1728152 in cloud-init "EC2 IPv4 and IPv6 Dual Stack Does Not work when instance is not assigned public IPv4 address" [High,In progress] + + 16:59 ` ok looks like we are good for the status meeting + + 17:00 ` thanks for joining all. see you in two weeks + + 17:00 ` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) diff --git a/content/status-2017-11-13.md b/content/status-2017-11-13.md new file mode 100644 index 0000000..541477d --- /dev/null +++ b/content/status-2017-11-13.md @@ -0,0 +1,288 @@ +Title: Cloud-init bi-weekly status +Date: 2017-11-13 16:03:00 UTC +Category: status-meeting-minutes +Slug: status-2017-11-13 + +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](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/](http://paste.ubuntu.com/25954862/) + * **LINK**: [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) + * **LINK**: [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) + +### In Progress Development + +The discussion about "In Progress Development" started at 16:10 + + * **LINK**: [http://bit.ly/ci-reviews](http://bit.ly/ci-reviews) + +### Office Hours next 30 minutes + +The discussion about "Office Hours next 30 minutes" started at 16:13 + + * **LINK**: [https://jenkins.ubuntu.com/server/view/cloud-init/](https://jenkins.ubuntu.com/server/view/cloud-init/) + * **LINK**: [https://bugs.launchpad.net/cloud-init/+bug/1731619](https://bugs.launchpad.net/cloud-init/+bug/1731619) + * **LINK**: [http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html?highlight=nocloud](http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html?highlight=nocloud) + * SRU queued for release today + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (53) + * robjo (20) + * smoser (17) + * via (10) + * meetingology (3) + * ubot5 (2) + * powersj (1) + * rharper (1) + + + +Full Log +---------------- + + + 16:03 ` \#startmeeting Cloud-init bi-weekly status + + 16:03 ` Meeting started Mon Nov 13 16:03:13 2017 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:03 ` + + 16:03 ` Available commands: action commands idea info link nick + + 16:03 ` o/ + + 16:03 ` time change got to us + + 16:04 ` \#topic Recent Changes + + 16:05 ` hey folks. thanks for joining just pulling together the content for the last couple weeks of work for the cloud-init project + + 16:06 ` [http://paste.ubuntu.com/25954862/](http://paste.ubuntu.com/25954862/) + + 16:06 ` $ git log a90a8b1cb3104ee3250ac79d6e25a9ff4f527baa.. | log2dch | sed 's,^ ,,' | pastebinit + + 16:06 ` most of the ubuntu-side of the house was involved in handling the SRU of 17.1 into ubuntu and handling any discovered regressions + + 16:06 ` Published cloud-init packages to Bionic Beaver release + + 16:06 ` Update Gentoo Linux support to "rc-service" scripts as "service" is deprecated, thanks to ckonstanski! + + 16:06 ` Detected and fixed a pre-release regression of resizefs when root path is specified by UUID on the kernel cmdline (LP: \#1725067) + + 16:06 ` Launchpad bug 1725067 in cloud-init (Ubuntu Zesty) "cloud-init resizefs fails when booting with root=PARTUUID=" [Medium,Fix committed] [https://launchpad.net/bugs/1725067](https://launchpad.net/bugs/1725067) + + 16:06 ` \#link [http://paste.ubuntu.com/25954862/](http://paste.ubuntu.com/25954862/) + + 16:07 ` \#info SRU queued for release today + + 16:07 ` Here's the cloud-init content we published for the last two weeks: + + 16:07 ` \#link [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) + + 16:07 ` \#link [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) + + 16:09 ` 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 + + 16:09 ` 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 + + 16:09 ` with those SRU regresssions fixed and published to master, we expect cloud-init 17.1 updated in Xenial,Zesty and Artful today + + 16:10 ` \#topic In Progress Development + + 16:10 ` smoser: rharper anything here? + + 16:10 ` \#link [http://bit.ly/ci-reviews](http://bit.ly/ci-reviews) + + 16:11 ` robjo has done a couple fixes for SuSE and i've pulled a few of them. + + 16:11 ` he has one up i saw yestderday for ntpSuSE + + 16:11 ` others ther.e we've been delinquent due to some distractions recently. + + 16:11 ` blackboxsw: nothing new for me at the moment + + 16:12 ` and chad had one up for clean and status + + 16:12 ` 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 + + 16:12 ` which is nice. + + 16:13 ` moving the meeting an hour foward while we are on Standard time or is this a one time occurance, did I miss an announcement? + + 16:13 ` \#topic Office Hours (next 30 minutes) + + 16:14 ` lp\#1731619, chrony support, should that also be driven through ntp config or should there be a new config option? + + 16:14 ` so we'll hang out with eyes on this channel for any burning questions/bugs/questions + + 16:14 ` robjo: well, the meeting is listed in UTC time + + 16:14 ` that pays no attention to US legislation to change clocks at random points in the year :) + + 16:15 ` oK, my fault when I added it to my calendar, eay enough to fix ;) + + 16:15 ` but the humans here were also affected :) + + 16:15 ` heh, anyone opposed to shifting this meeting time +30 from now during the next few months? + + 16:15 ` as the meeting now collides w/ another meeting for us + + 16:15 ` :/ + + 16:16 ` officially 16:30 UTC? + + 16:17 ` Well, I'd prefer to either follow the "randomness" clock manipulation or not follow it + + 16:19 ` 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 + + 16:19 ` fair point. ok let's keep the new time as is. + + 16:20 ` we've discussed side-channel, we can shift our meetings out of the way of this + + 16:20 ` so robjo +1 + + 16:20 ` 16:00 UTC + + 16:24 ` 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 + + 16:24 ` \#link [https://jenkins.ubuntu.com/server/view/cloud-init/](https://jenkins.ubuntu.com/server/view/cloud-init/) + + 16:28 ` 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 + + 16:28 ` 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? + + 16:28 ` like configuring the chef node name to have my instance id in it + + 16:32 ` \#link [https://bugs.launchpad.net/cloud-init/+bug/1731619](https://bugs.launchpad.net/cloud-init/+bug/1731619) + + 16:32 ` Launchpad bug 1731619 in cloud-init "Support chrony as a client for ntp" [Undecided,New] + + 16:33 ` it's a good bug, we've had a couple of discussions about ntpd versus timesyncd for different system environments + + 16:34 ` 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 + + 16:34 ` via: i think what your asking is (i htink) covered in [https://trello.com/c/AYaCdQyT](https://trello.com/c/AYaCdQyT) + + 16:35 ` well, i'm trying to do it in a yaml cloud-config file + + 16:35 ` right. as it is right now, via you cann't reference anything from the metadata. + + 16:35 ` does that mean i need to use \#jinja and if so how does that play with \#cloud-config ? + + 16:35 ` oh + + 16:36 ` bummer + + 16:36 ` should i just switch to a shell script? + + 16:36 ` but we'd hope to implement that. + + 16:36 ` via: thats really the only way right now. and then in the shell scripty you'd have to query the metadata service yourself. + + 16:36 ` okay, damn + + 16:36 ` thanks + + 16:36 ` 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 + + 16:36 ` basically... we realize what you're asking is quite helpful and reasonable but dont have a way to do it right now + + 16:36 ` but we do plan on implementing it. + + 16:37 ` no worries, i'm stuck on an ancient version anyway + + 16:38 ` 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 + + 16:39 ` since with a third option the black/white decision being made today will no longer work + + 16:39 ` +1 robjo yeah. rharper was chatting about this potential approach as well + + 16:39 ` look there is also grey ;) + + 16:39 ` heh yeah + + 16:40 ` Next question.... network config. + + 16:40 ` yeah might have to 'grow' an override option in cc_ntp module eventually + + 16:41 ` as those grey use-cases come up (per bugs/requests ;) ) + + 16:41 ` 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 + + 16:42 ` 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 + + 16:43 * blackboxsw is looking for the warning generated + + 16:43 ` 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 + + 16:44 ` blackboxsw: "apply_network_config is not currently implemented " + + 16:44 ` "for distribution '%s'. Attempting to use apply_network" + + 16:45 ` ahh. right-o + + 16:45 ` 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 ;) + + 16:47 ` And yes, I realize a bug will need to be filed, but I haven't figured out how to formulate this nicely + + 16:47 ` 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. + + 16:47 ` OK :) + + 16:50 ` 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. + + 16:51 ` 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. + + 16:52 ` we'll keep our eyes open for discussions/suggestions from folks + + 16:54 ` 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 ;) + + 16:56 ` robjo: I'm curious how different that datasource would be from nocloud datasource + + 16:56 ` [http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html](http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html)?highlight=nocloud + + 16:56 ` \#link [http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html](http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html)?highlight=nocloud + + 16:56 ` which allows for providing local data instead of dealing with metadata + + 16:56 ` well network metadata + + 16:57 ` 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 + + 17:00 ` good deal.... think we are at the top of the hour... so I'll probably end meeting now + + 17:01 ` thanks via robjo rharper powersj & smoser. next meeting 2 weeks same early time + + 17:01 ` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) diff --git a/content/status-2017-12-11.md b/content/status-2017-12-11.md new file mode 100644 index 0000000..8a380e2 --- /dev/null +++ b/content/status-2017-12-11.md @@ -0,0 +1,528 @@ +Title: Cloud-init bi-weekly status +Date: 2017-12-11 16:05:00 UTC +Category: status-meeting-minutes +Slug: status-2017-12-11 + +Meeting information +---------------- + * \#cloud-init: Cloud-init 'bi-weekly' status meeting, 11 Dec at 16:05 — 17:22 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-12-11-16.05.log.html](http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-12-11-16.05.log.html)]] + + + +Meeting summary +---------------- + +### Recent Changes +The discussion about "Recent Changes" started at 16:07. + + * **LINK**: [https://lists.launchpad.net/cloud-init/msg00114.html](https://lists.launchpad.net/cloud-init/msg00114.html) + * **LINK**: [http://cloud-init.github.io](http://cloud-init.github.io) + +### In-progress Development +The discussion about "In-progress Development" started at 16:15. + + * **LINK**: [http://bit.ly/ci-reviews](http://bit.ly/ci-reviews) + * **LINK**: [https://code.launchpad.net/~paul-meyer/cloud-init/+git/cloud-init/+merge/334989](https://code.launchpad.net/~paul-meyer/cloud-init/+git/cloud-init/+merge/334989) + * **LINK**: [https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/335034](https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/335034) + +### Office Hours (for next 30 mins) +The discussion about "Office Hours (for next 30 mins)" started at 16:38. + + * **LINK**: [http://pastebin.ubuntu.com/26075842/](http://pastebin.ubuntu.com/26075842/) + * **LINK**: [http://paste.ubuntu.com/26164503/](http://paste.ubuntu.com/26164503/) + * **ACTION**: blackboxsw bring up any updates in instance-data.json fields for discussion about common use-cases/patterns + + + +Vote results +---------------- + + + + +Action items, by person +---------------- + + * blackboxsw + * blackboxsw bring up any updates in instance-data.json fields for discussion about common use-cases/patterns + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (83) + * smoser (54) + * ajorg (38) + * robjo (32) + * ubot5 (7) + * meetingology (4) + * powersj (2) + * dpb1 (2) + * rharper (2) + + + +Full Log +---------------- + + + 16:05 ` \#startmeeting Cloud-init 'bi-weekly' status meeting + + 16:05 ` Meeting started Mon Dec 11 16:05:16 2017 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:05 ` + + 16:05 ` Available commands: action commands idea info link nick + + 16:05 ` thanks for hosting blackboxsw + + 16:05 ` no problemo. + + 16:05 ` happy holidays folks and thanks for joining. + + 16:07 ` \#topic Recent Changes + + 16:07 ` As mentioned @ our 17.1 release, we're promising more frequent cloud-init releases. + + 16:08 ` smoser has mailed the list informing cloud-init interested parties that we are targeting a 17.2 release for Thursday this week + + 16:08 ` It's been a few weeks since we've hosted the meeting (I think we missed last meeting), so I'll post some of the development that has landed in trunk + + 16:08 ` \#link [https://lists.launchpad.net/cloud-init/msg00114.html](https://lists.launchpad.net/cloud-init/msg00114.html) + + 16:09 ` * All integration tests now function with the nocloud-kvm backend + + 16:09 ` * Fix apport for cloud-name options (LP: \#1722564) + + 16:09 ` * Improve warning message when templates aren't found (Robert Schweikert) (LP: \#1730135) + + 16:09 ` * Perform null checks for enabled/disabled Red Hat repos (Dave Mulford) + + 16:09 ` * Fix openSUSE and SLES setup of /etc/hosts (Robert Schweikert) (LP: \#1731022) + + 16:09 ` * Catch UrlError when \#include'ing URLs (Andrew Jorgensen) + + 16:09 ` Launchpad bug 1722564 in Apport "apport question will not accept multi-character responses" [Undecided,Confirmed] [https://launchpad.net/bugs/1722564](https://launchpad.net/bugs/1722564) + + 16:09 ` Launchpad bug 1730135 in openstack-dev-sandbox ""Too much rain in Sydney"" [Undecided,New] [https://launchpad.net/bugs/1730135](https://launchpad.net/bugs/1730135) + + 16:09 ` Launchpad bug 1731022 in cloud-init "host template expansion does not work on SUSE distros" [High,Fix committed] [https://launchpad.net/bugs/1731022](https://launchpad.net/bugs/1731022) + + 16:09 ` ajorg replied with a request for [https://code.launchpad.net/~ajorgens/cloud-init/+git/cloud-init/+merge/329657](https://code.launchpad.net/~ajorgens/cloud-init/+git/cloud-init/+merge/329657) + + 16:09 ` that fell on deaf ears + + 16:09 ` * Released stable release update (SRU) of 17.1-27-geb292c18 (LP: \#1721847) + + 16:09 ` * Cleanup dhclient background process after EC2 network discovery. + + 16:09 ` * ntp: fix configuration template rendering for openSUSE and SLES (Robert Schweikert) LP: \#1726572 + + 16:09 ` * fix manually running cloud-init after upgrade (LP: \#1732917) + + 16:09 ` Launchpad bug 1721847 in cloud-init (Ubuntu Artful) "sru cloud-init 2017-10-06 (17.1-18-gd4f70470-0ubuntu1) updated to (17.1-27-geb292c18)" [Medium,Fix released] [https://launchpad.net/bugs/1721847](https://launchpad.net/bugs/1721847) + + 16:09 ` Launchpad bug 1726572 in cloud-init "ntp config handling inconsistent for SLES and openSUSE" [Medium,Fix committed] [https://launchpad.net/bugs/1726572](https://launchpad.net/bugs/1726572) + + 16:09 ` Launchpad bug 1732917 in cloud-init "17.1 update breaks EC2 nodes" [High,Fix committed] [https://launchpad.net/bugs/1732917](https://launchpad.net/bugs/1732917) + + 16:09 ` truth + + 16:09 ` ajorg: i will review shortly + + 16:09 ` * Queued upstream for merge into Bionic + + 16:09 ` * Queued 17.1.46 SRU for Xenial, Zesty, and Artful + + 16:09 ` * Fix EC2 race on sandboxed dhclient's pidfile during tempdir teardown (LP: \#1735331) + + 16:09 ` * Enable Bionic in Integration Tests + + 16:09 ` * Create LXD and KVM Integration Tests in Jenkins + + 16:09 ` Launchpad bug 1735331 in cloud-init "ec2: zesty tempfile sandbox dhclient.pid file can't be created" [High,Fix committed] [https://launchpad.net/bugs/1735331](https://launchpad.net/bugs/1735331) + + 16:10 ` As of end of last week, we are trying to blitz the review queue and dust off anything that has been sitting too long + + 16:12 ` So a couple fixes went into Amazon's initial network setup, IPv6 support is live for Ubuntu series Xenial, Zesty, Artful and Bionic + + 16:13 ` cool + + 16:14 ` heh I blew that last topic. it should have been \#topic Recent Changes. + + 16:14 ` anyway I'll fix it in the logs when I publish + + 16:15 ` As always , for historical docs from this meeting check this link + + 16:15 ` \#link [http://cloud-init.github.io](http://cloud-init.github.io) + + 16:15 ` \#topic In-progress Development + + 16:15 ` So we have an active queue that is pretty healthy still + + 16:15 ` \#link [http://bit.ly/ci-reviews](http://bit.ly/ci-reviews) + + 16:16 ` smoser: rharper are we still trying to get through that queue as best we can for 17.2 or when do we think the window closes there? + + 16:16 ` i think we can spend some more time on queue today. + + 16:16 ` but that is about it really. + + 16:16 ` yeah, want some settle 'bake' time before the 17.2 cut on Thursday + + 16:17 ` We saw a couple Azure branches come in late last week.... Are there any branches folks are really excited about landing this week (today tomorrow?) + + 16:18 ` I had hoped to get through a couple of Robert's as they don't seem very contentious. + + 16:19 ` the reporter bit seems pretty reasonable + + 16:19 ` other than its not actually used anywhere in the mp + + 16:19 ` ie, its non-contentious to add a reporter, but adding code that is not used is of not a lot of use :) + + 16:19 ` true + + 16:20 ` which mp is being discussed? + + 16:20 ` ([https://code.launchpad.net/~paul-meyer/cloud-init/+git/cloud-init/+merge/334989](https://code.launchpad.net/~paul-meyer/cloud-init/+git/cloud-init/+merge/334989)) + + 16:20 ` \#link [https://code.launchpad.net/~paul-meyer/cloud-init/+git/cloud-init/+merge/334989](https://code.launchpad.net/~paul-meyer/cloud-init/+git/cloud-init/+merge/334989) + + 16:21 ` thanks + + 16:23 ` With the upcoming holidays I expect things will be pretty slow after mid-next week, so we won't likely be landing a lot before the first of the new year. + + 16:25 ` If it's slow for you more time to review open merge proposals ;) + + 16:25 ` This week we are also trying to get an SRU into ubuntu xenial, zesty and artful for some VMware/OVF datasource fixes for ds-identify and for pre-cusomization marker files courtesty (smoser & maitriyee) + + 16:26 ` *courtesy* rather + + 16:26 ` ajorg: you could ping matthew on [https://code.launchpad.net/~yeazelm/cloud-init/+git/cloud-init/+merge/331897](https://code.launchpad.net/~yeazelm/cloud-init/+git/cloud-init/+merge/331897) + + 16:27 ` yup + + 16:27 ` and I know powersj is working on EC2 integration test support for cloud-init + + 16:27 ` yep! + + 16:27 ` Hoping to have an initial MP up this week + + 16:27 ` it's gonna be excellent to automatically test these releases + + 16:28 ` powersj: rharper smoser anything else in progress? + + 16:28 ` nothing here + + 16:28 ` oh very nice. + + 16:28 ` powersj: \o/ + + 16:28 ` just the things that are in teh review queue. i put up one this morning for tmp file leakage + + 16:28 ` [https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/335034](https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/335034) + + 16:29 ` i think the yeazelm mp probably is just missing somethign simple bug haven't spent any time on it. + + 16:29 ` ahh also we landed the initial /run/cloud-init/instance-data.json which we had talked about with larsks. It captures all metadata and userdata and some standardized properties which could help people script instance data. + + 16:29 ` yeah, that is neat. + + 16:30 ` Yeah, we have yet to write up docs on using it (and we have an inprogress branch to allow using jinja templates in \#cloud-config modules). But I don't expect this to land by 17.2 + + 16:31 ` did we? that's great! + + 16:32 ` yeah only basic standardized properties currently. + 'local-hostname': self.get_hostname(), + + 16:32 ` 592 + 'instance-id': self.get_instance_id(), + + 16:32 ` 593 + 'cloud-name': self.cloud_name, + + 16:32 ` 594 + 'region': self.region, + + 16:32 ` 595 + 'availability-zone': self.availability_zone}} + + 16:32 ` is that basically a re-implementation of python-ec2metadata? [https://github.com/SUSE/Enceladus/tree/master/ec2utils/ec2metadata](https://github.com/SUSE/Enceladus/tree/master/ec2utils/ec2metadata) + + 16:32 ` but it's a first pass. We expect to add more + + 16:33 ` robjo: kindof, though generalized for all datasources + + 16:34 ` robjo: long term, it's expected to be more than just ec2; rather a common baseline of instance metadata independent the actual cloud, but , IIRC, having a cloud-specific area (or at least access to the raw data) + + 16:34 ` it leaves a json-foramatted file containing any vendor data and user-data plus generalized/standardized fields extracted from that content which can be expected on all clouds + + 16:35 ` problem with "all" clouds is that Azure is very different + + 16:35 ` since each datasource has that data already, it's essentially just formating it in a consumable file that others could levereage + + 16:35 ` although one can argue that a "name" is an id it still looks weird when 'instance-id' and is a name + + 16:36 ` agreed robjo, some datasources may not provide different/less content. + + 16:36 ` ajorg: [http://paste.ubuntu.com/26164503/](http://paste.ubuntu.com/26164503/) + + 16:36 ` Is that one of the Azure differences? name vs. instance-id? + + 16:36 ` thats a demo of instance-data.json + + 16:36 ` yes, azure has names no numbers + + 16:37 ` it's more about "user expectations" as a "name" is an "identifier" + + 16:37 ` I'll check that azure run now. I think I linked it to the branch originally + + 16:37 ` ok I think it's probably a good to transition to open office hours now for the next 30 mins + + 16:38 ` what is 'name' versus 'instance-id' comment ? + + 16:38 ` ajorg: ? + + 16:38 ` \#topic Office Hours (for next 30 mins) + + 16:38 ` feel free to continue the discussion now + + 16:38 ` I'd just caution of making the assumption that we can stick the information from that data sources straight into another format and then call it "generic instance information" + + 16:38 ` smoser: re robjo's comment about "Azure is very different" + + 16:39 ` oh. yes. ok. + + 16:39 ` azure instance-data + + 16:39 ` \#link [http://pastebin.ubuntu.com/26075842/](http://pastebin.ubuntu.com/26075842/) + + 16:39 ` smoser: standup + + 16:39 ` yeah, they do have a 'id' + + 16:40 ` \#link [http://paste.ubuntu.com/26164503/](http://paste.ubuntu.com/26164503/) + + 16:40 ` from DMI? + + 16:40 ` Which is useless in any any command + + 16:40 ` from the cd i think. + + 16:41 ` robjo: ah, so the ID is unique (is it?) but can't be used to call any Azure APIs? + + 16:41 ` in EC2 the instance-id is useful to me if I want to run "aws" commands, but the instance ID shown in the pastebin is useless for any "az" command + + 16:41 ` ajorg: correct + + 16:41 ` in the "az" tools everything is a name + + 16:42 ` and thus to make the data cloud-init produces useful the -id should be the name of the VM + + 16:42 ` then I can parse that information and use it if I need to deal with the API + + 16:43 ` hm. + + 16:43 ` but providing that ID as its is basically just sticking information into the json to "fill a field" which is somewhat counter to the point I'd say + + 16:43 ` robjo: there's a uniqueness constraint on the name too? but per-account or at-a-time or what? + + 16:43 ` i odnt knwo. although it is insteresting thought. + + 16:43 ` the issue is 'instance-id' is supposed to be an instance id + + 16:43 ` not a user provided name that can be provided mutliple times in a row. + + 16:44 ` i realize name is per-group unique, but if i + + 16:44 ` a.) launch + + 16:44 ` a.) launch 'foobar' + + 16:44 ` There is a uniqueness constraint in that one cannot run a VM with the same "name" in the same resource group + + 16:44 ` so the question is if that ID provides global uniqueness, or if it provides a reference to the instance to be used via APIs + + 16:44 ` b.) create capture + + 16:44 ` c.) delete foobar + + 16:44 ` d.) launch foobar + + 16:44 ` then 'd' wont look new + + 16:45 ` yes, it will it just takes a long time in Azure until the backend reaches "eventual" consistency and knows "foorbar" has been deleted previously + + 16:45 ` It seems clear enough that cloud-init is looking for a unique ID + + 16:45 ` But a user might want either, and probably an ID for API use. + + 16:47 ` Well if we provide a format of the data that is exposed to the user via documentation and expected to be used by the user than at that point, IMHO, user needs have higher priority than what cloud-init is looking for + + 16:47 ` To decide which APIs to use, a script has to first look at which cloud it's on, so it has a chance to decide which value to use. + + 16:47 ` that cloud-init uses the id to make decisions about "pre-once", "per-always" is a different topic + + 16:49 ` Well that then kind of defeats the "generic instance information" claim, IMHO + + 16:49 ` you are basically saying 1.) look for the framework and then decide if on that framework the "generic instance information" is useful or not + + 16:50 ` 2.) If you happen to be on a platform where the "generic instance information" is not useful, go and collect your own + + 16:50 ` From a user perspective that is not very nice, IMHO + + 16:51 ` oh, I was presuming we'd also include the Azure name, not that we'd include only a useless instance-id in that case. + + 16:51 ` clouds that don't have a name, wouldn't include a value for it. + + 16:52 ` the pastebin only has the ID + + 16:52 ` right, I'm saying we should add the name + + 16:53 ` This is why I am pointing out that "generic instance information" is not necessarily so easy to come by + + 16:54 ` robjo: ultimately, I'd like the generalized content surfaced in instance-data.json to be something that external user's could get value from and script against. This first pass was a stripped down approach to some of that content. + + 16:54 ` we could add 'name' and have it be none yes. + + 16:55 ` the not-yet-written doc will state that consumers should not be confused by new field names. + + 16:55 ` There are some fixes that need to be proposed to all datasources to better standardize on things like public vs private addresses, external hostnames etc. Those I expect will come in subsequent passes. + + 16:55 ` it might be worth considering the concept of "equivalent instance information" where the entries in the json files get names/keys that are generic across all cloud frameworks and provide the euivalent information/usefulness to the user + + 16:55 ` but inside the 'v1', then content of a key will not change. + + 16:55 ` robjo: that's a fair point, imho + + 16:55 ` but 'instance-id' is in fact 'instance-id'. not 'name'. + + 16:55 ` robjo: I think that is the intent of those 'v1' standardized fields. + + 16:56 ` note that lxd shares the same generic problem in this regard as azure. it uses user-provided name for instance-id. but does not provide an actual instance id of any sort. + + 16:56 ` right per name/instance-id discussion, they feel separate, and I think there is value in adding a separate 'name' as smoser mentioned + + 16:58 ` Lets look at it from an API perspective, if I were to use the .json file wouldn't it be nice if I could just say json.load().get{'instance_api_id') + + 16:58 ` for EC2 that returns the instance-id, for Azure it gives me the name + + 16:59 ` part of the idea of cloud-init is to keep the ugly details of the cloud framework away from the user + + 16:59 ` if we were talking about the value of "region" we'd certainly want to yield the value that's useful for API calls. + + 17:00 ` so why would the .json data then retrieve from that idea and make the user know if I am in EC2 I need to use instance-id and if I am in Azure I need to use instance-name? + + 17:01 ` ajorg: agreed + + 17:01 ` it seems somewhat non-sense that azure gives an instance a unique id, but cannot take that in as an identifier to the instance. + + 17:02 ` AWS, GCE, and Azure all have the concept of "region" , not certain how IBM is handling that part in their setup but that may not be of interest to us at this point + + 17:02 ` your point is good though. but instance-id i really think needs to be a unique identifier (as much as possible) for this *instance* + + 17:02 ` It sounded like smoser's 'v1' comment was meant to imply we could have a 'v2' that yields data differently than 'v1'. + + 17:02 ` softlayer has "datacenters" + + 17:03 ` smoser: I agree, but that's the way it is + + 17:03 ` at some point, ajorg we will of course realize that we're all idiots + + 17:03 ` and wonder What were we thinking! + + 17:03 ` and have a 'v2' + + 17:04 ` `<-- it takes some of us longer than others to realize that + + 17:05 ` smoser: you're not convinced that today is that day? + + 17:05 ` i try to keep acknowledgement of that fact to be more than a few days later + + 17:06 ` good to let it sink in first :-) + + 17:06 ` (compared to when i notice it, to allow for additional occurences) + + 17:06 ` I'm not going to say it has to be changed, but I do think at the very least the azure name should be available. + + 17:07 ` I think this discussion definitely sheds light on the fact that we should continue to bring these standardized instance-data discussions to this meeting for a quick feedback loop from you guys as it evolves :) + + 17:07 ` :) + + 17:08 ` \#action blackboxsw bring up any updates in instance-data.json fields for discussion about common use-cases/patterns + + 17:08 * meetingology blackboxsw bring up any updates in instance-data.json fields for discussion about common use-cases/patterns + + 17:08 ` and it doesn't seem harmful to have the name only if the cloud provides one, just as if the cloud doesn't have a concept of an availability zone we'll skip that too. + + 17:09 ` +1 + + 17:10 ` well i think this about wraps up our meeting for today + + 17:10 ` any other topics for today? + + 17:11 ` I pinged Matt Yeazel, but he didn't respond yet. + + 17:11 ` i think 'api-id' would lmake sense as a name. + + 17:11 ` so nothing more from my end + + 17:11 ` smoser: or 'api-instance-id' + + 17:12 ` that just seems confusing. + + 17:12 ` hm.. + + 17:12 ` i see why you want the 'instance' portion there, but the thing i dont like is that implies that this is 'per instance' + + 17:12 ` well, it's an API instance identifier. + + 17:13 ` which in fact it is not. + + 17:13 ` hm. + + 17:13 ` Ah, okay, that's true, but if the cloud doesn't have a unique way to identify the instance to the API... + + 17:13 ` yeah + + 17:14 ` someone should check that assumption... how do you refer to terminated instances? or how are they identified in logs? + + 17:16 ` smoser: I just worry that someone's going to say "but in my API an API ID is this other thing" + + 17:17 ` yeah before surfacing something like that we'd need to vet it + + 17:17 ` In general I think there are enough differences between clouds that it's probably a losing battle to try to come up with something that's one-size-fits-all. + + 17:17 ` The goal was to make the information available more readily than by calling out to metadata services, right? + + 17:18 ` It's much harder to implement meta-data pulling for every cloud than to implement some logic that pulls the right value out of a JSON object, so it's still a big improvement even if it can't provide a unified view. + + 17:21 ` anywho, I should go do other things. + + 17:21 ` ajorg: yes that is the primary goal: more easily access cloud-provided metadata + + 17:21 ` if there is low-hanging fruit we can standardize I'm +1 on the concept + + 17:22 ` that's where the standard 'v1' key came from + + 17:22 ` but yeah I also don't think cloud-init needs to boil the ocean and standardize all fields + + 17:22 ` we'll capture what low-hanging fruit we can + + 17:22 ` and it'll take time + + 17:22 ` ok. Thanks for the great discusssions/suggestions ajorg and robjo. keep 'em coming + + 17:22 ` think I'll end meeting now + + 17:22 ` until next time... + + 17:22 ` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) diff --git a/content/status-2018-01-08.md b/content/status-2018-01-08.md new file mode 100644 index 0000000..064c056 --- /dev/null +++ b/content/status-2018-01-08.md @@ -0,0 +1,443 @@ +Title: Cloud-init bi-weekly status +Date: 2018-01-08 16:03:00 UTC +Category: status-meeting-minutes +Slug: status-2018-01-08 + +Meeting information +---------------- + * \#cloud-init: Cloud-inin bi-weekly status meeting, 08 Jan at 16:03 — 17:15 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-01-08-16.03.log.html](http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-01-08-16.03.log.html)]] + + + +Meeting summary +---------------- + +### Recent changes +The discussion about "Recent changes" started at 16:04. + + * **LINK**: [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + * **LINK**: [https://cloudinit.readthedocs.io/en/latest/topics/tests.html\#ec2](https://cloudinit.readthedocs.io/en/latest/topics/tests.html\#ec2) + +### In-progress Development +The discussion about "In-progress Development" started at 16:22. + + * **LINK**: [https://trello.com/c/AYaCdQyT](https://trello.com/c/AYaCdQyT) + * **LINK**: [https://trello.com/c/xyqxyOxg](https://trello.com/c/xyqxyOxg) + * **LINK**: [https://trello.com/c/AYaCdQyT/21-cloud-init-query-standardized-json-information](https://trello.com/c/AYaCdQyT/21-cloud-init-query-standardized-json-information) + +### Office Hours (next 30 minutes) +The discussion about "Office Hours (next 30 minutes)" started at 16:46. + + * **LINK**: [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/334992](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/334992) + * **LINK**: [http://jinja.pocoo.org/docs/2.10/api/\#policies](http://jinja.pocoo.org/docs/2.10/api/\#policies) + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (99) + * ajorg (45) + * smoser (19) + * rharper (9) + * robjo (5) + * powersj (4) + * meetingology (3) + * smoser1 (2) + * ubot5 (1) + + + +Full Log +---------------- + + + 16:03 `` \#startmeeting Cloud-inin bi-weekly status meeting + + 16:03 `` Meeting started Mon Jan 8 16:03:53 2018 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:03 `` + + 16:03 `` Available commands: action commands idea info link nick + + 16:04 `` Happy 2018 cloud-initers! Thanks ajorg for helping kick us off. + + 16:04 `` Welcome back from break hope the holidays were good for folks. + + 16:09 `` \#topic Recent changes + + 16:04 `` It + + 16:05 `` It's been a while since we've held the meeting due to holidays and vacation time. So, not a ton of content to report for the last bit. Digging up those details now + + 16:06 `` Testing of 17.2 on EC2, Azure, and GCE and release to Ubuntu Bionic + + 16:06 `` Complete 17.1.46 SRU to Ubuntu Xenial, Zesty, and Artful + + 16:06 `` Fix documentation around 'init' mode for modules subcommand (LP: \#1736600) + + 16:06 `` Tooling to merge community authored branches into master + + 16:06 `` Launchpad bug 1736600 in cloud-init "CLI: cloud-init modules -h documents unsupported --mode init" [Low,Fix committed] [https://launchpad.net/bugs/1736600](https://launchpad.net/bugs/1736600) + + 16:07 `` So the canonical side of the team worked a bit on getting the latest SRU updates 17.1.46 into Xenial, Zesty and artful. The testing and verification of that release took a bit of time, but we are getting better(faster) + + 16:07 `` I think this last SRU only took us 2 weeks instead of 4 weeks. so that frees up more time on upstream reviews and increasing cloud-init's velocity + + 16:07 `` great + + 16:08 `` we also added team tools for streamlining community authored branches. so that we stop slowing folks down :/ + + 16:08 `` then the only problem is the reviewer :) + + 16:10 `` Also 17.2 release was 'cut' prior to Christmas break, this opened master up for more changes to land. so we've pulled in good fixes for VMWare NoCloud and SLES + + 16:11 `` digging up the changests now. + + 16:11 `` Also, keep in touch with our active development and the "done" lane on trello. It's out bookkeeper for anything we are working and Done represents anything landed + + 16:11 `` \#link [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + + 16:13 `` so high-level content that landed between 17.1.46 and 17.2: + + 16:14 `` * CLI added the clean and status subcommands + + 16:14 `` * Support for identifying OVF datasource provided by VMware + + 16:14 `` * NoCloudKVM tests now run in continuous integration + + 16:14 `` * Formalize DataSource get_data and related properties + + 16:14 `` * Remove prettytable dependency and introduce simpletable + + 16:14 `` * VMWare pre and post-customization script support + + 16:15 `` Thanks ajorg I think you were the author of note on simpletable stuff, it's nice to drop dependencies where we can to increase speed of cloud-init + + 16:15 `` it was done selfishly + + 16:15 `` we dislike taking on new dependencies :-) + + 16:17 `` and thanks to robjo(suse) maitree(vmware) too and dojordan and Ryan McCabe(redhat) for recent branches too + + 16:17 `` :) + + 16:18 `` Post our 17.2 release we've started work on improved integration..... I think we just got powersj's ec2 integration tests landed right johs? + + 16:18 `` josh even + + 16:18 `` \o/ yep! + + 16:18 `` nice + + 16:19 `` sweet, so an extra security blanked for us when we have significant changesets landed in master to ensure ec2 is happy. + + 16:19 `` powersj: what are out plans for continuous integration frequency + + 16:19 `` with ec2 specifically + + 16:19 `` Can those integration tests be run by others with EC2 accounts? + + 16:19 `` ajorg: yes they can + + 16:19 `` I am working on the jenkins jobs this week and hope to have a weekly run as well as a manual run for backport testing + + 16:19 `` I'll get the cmdline + + 16:19 `` thanks! + + 16:20 `` tox -e citests -m tests.cloud_tests run --os-name=artful --platform=ec2 --preserve-data --data-dir=../results --verbose + + 16:20 `` or something like that + + 16:20 `` got it + + 16:20 `` thanks! + + 16:20 `` powersj: documented it too I think + + 16:20 `` getting link + + 16:20 `` [https://cloudinit.readthedocs.io/en/latest/topics/tests.html\#ec2](https://cloudinit.readthedocs.io/en/latest/topics/tests.html\#ec2) + + 16:20 `` \#link [https://cloudinit.readthedocs.io/en/latest/topics/tests.html\#ec2](https://cloudinit.readthedocs.io/en/latest/topics/tests.html\#ec2) + + 16:20 `` :) + + 16:21 `` excellent work Josh + + 16:21 `` thanks for all the reviews :) + + 16:21 `` anything else I'm missing about landed work? rharper powersj smoser1 ? + + 16:22 `` otherwise next topic + + 16:22 `` blackboxsw: nothing from me + + 16:22 `` \#topic In-progress Development + + 16:23 `` So we've got a fairly healthy review queue that we need to get through as we get the year started.... + + 16:24 `` we also have a few things we are in flight currently: + + 16:24 `` - continuous integration improvements per powersj + + 16:24 `` - dropping dependence on ifup ifdown utils where possible as that's not supported (or installed in some cases) in systemd world + + 16:24 `` blackboxsw: wow. sorry, missing. + + 16:25 `` who is that smoser1 guy anyway + + 16:25 `` yeah, i didnt see anything missing sorry. + + 16:25 `` wonder how that happened. + + 16:25 `` welcome ;) + + 16:25 `` - netplan improvements per rharper and jinja template support for all cloud-config modules + + 16:26 `` - and softlayer support per smoser + + 16:27 `` know the Azure guys are also posting a couple branches on getting a pre-provisioning setup going for thier datasource which looks pretty exciting + + 16:27 `` I can't think of anything else off the top of my head. + + 16:28 `` chrony support + + 16:28 `` we're only talking feature work in this topic? + + 16:29 `` any in progress development to highlight is fair game. bug work. refactoring, feature etc + + 16:29 `` +10 robjo and again thanks for working with us getting all those branches up and (hopefully soon) landed + + 16:29 `` what does "jinja template support for all cloud-config modules" mean? + + 16:31 `` I'd guess most modules don't need templating? + + 16:31 `` ajorg: two things. 1. since we have now landed /run/cloud-instance/instance-data.json to store metadata/userdata it'd be that \#cloud-config can new be specified with \#\# template:jinja header and could leverage anything jinjia has to offer plus sourcing any of the instance-data.json metadata fields + + 16:33 `` Ah, right. Is that not being done above the module level? + + 16:33 `` so if people have repetitive or template-driven content in the runcmd or write_files portion or their \#cloud-config they'd be able to leverage jinja templates etc + + 16:33 `` ajorg: yes, above the module level. + + 16:33 `` ajorg: not anywhere in cloud-config currently + + 16:33 `` one sec I misunderstood the question + + 16:33 `` smoser: can you clarify what you mean? + + 16:33 `` I mean, shouldn't \#cloud-config template expansion happen before the module sees the config? + + 16:34 `` blackboxsw: we could/should also allow other part types to be rendered + + 16:34 `` ttps://trello.com/c/xyqxyOxg + + 16:35 `` er... bad url. in 2 ways + + 16:35 `` The the part handler would be the one to do that expansion. + + 16:35 `` [https://trello.com/c/AYaCdQyT](https://trello.com/c/AYaCdQyT) + + 16:35 `` ahh ok, right that makes sense. I think the cut I made was limited in focus to cloud-config modules and custom scripts supporting the \#\# template:jinja header.. but nothing would preclude handling other parts + + 16:36 `` so the link to my WIP branch was + + 16:36 `` \#link [https://trello.com/c/xyqxyOxg](https://trello.com/c/xyqxyOxg) + + 16:36 `` and the general feature per smoser + + 16:36 `` \#link [https://trello.com/c/AYaCdQyT/21-cloud-init-query-standardized-json-information](https://trello.com/c/AYaCdQyT/21-cloud-init-query-standardized-json-information) + + 16:36 `` Is there a design doc of some kind of this? + + 16:37 `` not yet.. but we probably should have a spec as it'd be a good template for the docs we'll need to write + + 16:38 `` scott captured most of the use cases we'd be going for in that last trello link above + + 16:38 `` Small example of where some clarity is needed: if Jinja is interpreting {foo} in a user-script, what will it do when it sees a shell variable ${foo} + + 16:38 `` ? + + 16:39 `` you declare that the content is a jinja template + + 16:39 `` if you provide it something that is not renderable as a jinja template + + 16:39 `` then it will fail + + 16:39 `` it requires input to explicitly say "this is jinja". it does not just attempt to render anything. + + 16:39 `` (unless explicitly told to) + + 16:39 `` some brief working examples are in the description of the branch @ [https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/334030](https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/334030) + + 16:40 `` Sure. But as a content author, I need to know if Jinja is going to try to render ${foo} or not. + + 16:40 `` then as a content author you can read jinja docs :) + + 16:40 `` jinja would try to render {{ foo }} + + 16:40 `` :- + + 16:41 `` ajorg: we'll document a simple case, and we can even document "for shell, you'll have to be aware that ...." + + 16:41 `` but we're not going to document all of jinja + + 16:41 `` I see. + + 16:42 `` My understanding was that Jinja was highly customizable in what it interpreted and how, so that it's important to document how you've configured it to work. + + 16:42 `` and since to burden is on the \#cloud-config or script writer to provide the header \#\# template: jinja\n\#cloud-config\n they *should* understand what they are doing + + 16:42 `` we won't implicitly run the \#cloud-config through jinja + + 16:43 `` I get that, no problem, what I'm saying is that Jinja is an engine that you configure to do something, not a markup that always does the same thing for everyone. + + 16:43 `` Am I making any sense? + + 16:44 `` understood (though I thought it was fairly constrained it it's application and functionality). We'll make sure that the mechanism by which jinja operates is well documented and confined as best we can... for our own sanity we don't want that template engine to be too flexible... too many tough support use cases + + 16:45 `` ok anything else for "In progress development" otherwise we can move to Office hours for 30 mins + + 16:46 `` \#topic Office Hours (next 30 minutes) + + 16:47 `` robjo: you've got quite a few branches of goodness up for us to review. Any prioritization on those branches or just take them as we can? + + 16:47 `` I don't think there are issues w.r.t jinja and shell; they use different variable escape methods, jinja uses {{ variable/expression }}; and it doesn't consume $ AFAIK, ajorg do you know differently ? + + 16:48 `` \#link [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/334992](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/334992) + + 16:48 `` I'm guessing is top of the list + + 16:48 `` I saw {instance_id} at [https://trello.com/c/AYaCdQyT/21-cloud-init-query-standardized-json-information](https://trello.com/c/AYaCdQyT/21-cloud-init-query-standardized-json-information) so I assumed it was being customized to look for { instead of {{ + + 16:48 `` blackboxsw: The chrony support should probably be the last as it will take longer over all and more back and forth + + 16:48 `` (for one thing) + + 16:49 `` rharper: also, there's the whole question of the "extends" feature + + 16:50 `` We integrated Jinja into an internal tool a few years back and we spent a very long time making sure the loaders did the right thing. + + 16:50 `` ajorg: I thought I read somewhere that you couldn't exend jinja for custom functions. maybe I was mistaken + + 16:50 `` I am also not certain that the "re-write everything" on the first go around for chrony is really what we want to do initially + + 16:50 `` blackboxsw: I don't think I'm referring to custom functions + + 16:51 `` That's probably where we ant to end up, but I am not certain that a "step function" approach is in order + + 16:51 `` ajorg: hrm, I've always seen {{ variable }} or {% expression %}; so maybe blackboxsw can just update the templates; + + 16:51 `` the examples in the cards + + 16:52 `` rharper: sure, that would have helped in this case. + + 16:52 `` If we do go down the route of the step function I'll need more gudance then in rharper's comments + + 16:52 `` blackboxsw: I was referring to the ability of one template to extend another. + + 16:53 `` blackboxsw: and the question of where does the engine look when it's asked to extend another template. It can be tricky. + + 16:54 `` yeah I honestly hadn't gotten past step one of handling the template markup within an existing single template. so this may need a bit of thought/work + + 16:55 `` Personally, I'd be a lot happier with limiting things to Python format() templates, even though it means you can't have loops, but I won't get in the way as long as we're cognizant of the problems we can run into by accepting the full power of an advanced engine like Jinja. + + 16:56 `` i'm not opposed to allowing \#\# template: python-format + + 16:56 `` heh + + 16:56 `` honestly. + + 16:56 `` you can pick a differnt name if you dont like that one. + + 16:57 `` but we already use jinja, so it makes sense to support jinja + + 16:57 * smoser has to run. sorry. + + 16:57 `` I do feel that supplying the template means the user is opting in; and specifically if we've got a good way to provide dry-run based on a instance.json and a script; that certainly can help folks work out the kinks in the template of their choosing + + 16:57 `` I'm really not opposed so much as wary of the extensive power of the thing + + 16:58 `` ajorg: that's a fair warning; given you've experience here; help drawing the line is most welcome + + 16:58 `` I'm trying to think of a way to read in /etc/shadow using Jinja, you know? + + 16:58 `` well, cloud-init is root anyhow; so, what's the deal with that ? + + 16:59 `` ajorg: heh, right though you can read that with your runcmd section in \#cloud-config :) + + 16:59 `` If I can come up with a way to do it that doesn't make it look obvious that I'm doing it, and then post that as something others can copy, or use with \#include `` then I win. + + 16:59 `` I don't think jinja makes that any more troublesome + + 17:00 `` folks already wget | bash with shell they don't understand either + + 17:00 `` I suspect Jijna makes it more opaque. + + 17:01 `` The answer to "what file does Jinja read when I use {% extends foo %}" is a very lengthy "it depends" + + 17:02 `` anyway, I've said my piece + + 17:03 * ajorg is a bit of a template naysayer. + + 17:05 `` +1, there's one in every group. We'll try to keep that in mind as this feature evolves + + 17:05 `` :) + + 17:06 `` nice + + 17:06 `` :-) + + 17:06 `` any pet bugs, new features or burning reviews that need mention? + + 17:07 `` ajorg: we could do something simple like disable the extends option via policies + + 17:07 `` it looks like + + 17:08 `` \#link [http://jinja.pocoo.org/docs/2.10/api/\#policies](http://jinja.pocoo.org/docs/2.10/api/\#policies) + + 17:08 `` or maybe I'm misunderstanding the issue I'll read up more on it + + 17:08 `` thanks + + 17:09 `` It looked like [https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/334074](https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/334074) was blocking [https://code.launchpad.net/~yeazelm/cloud-init/+git/cloud-init/+merge/331897](https://code.launchpad.net/~yeazelm/cloud-init/+git/cloud-init/+merge/331897) but shouldn't be anymore. + + 17:09 `` I'll remind Matt to try it again now. + + 17:13 `` thanks good dela + + 17:13 `` dela + + 17:13 `` deal + + 17:13 `` geez + + 17:14 `` on that note. I think it's time for coffee + + 17:14 `` and time to end the meeting + + 17:14 `` Happy New Year again folks. Good to be back in the office. + + 17:15 `` thanks again for the chat, until next time.. + + 17:15 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) diff --git a/content/status-2018-01-22.md b/content/status-2018-01-22.md new file mode 100644 index 0000000..1ed616e --- /dev/null +++ b/content/status-2018-01-22.md @@ -0,0 +1,352 @@ +Title: Cloud-init bi-weekly status +Date: 2018-01-22 16:08:00 UTC +Category: status-meeting-minutes +Slug: status-2018-01-22 + +Meeting information +---------------- + * \#cloud-init: Cloud-init bi-weekly status meeting, 22 Jan at 16:08 — 17:16 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-01-22-16.08.log.html](http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-01-22-16.08.log.html)]] + + + +Meeting summary +---------------- + +### Recent changes +The discussion about "Recent changes" started at 16:10. + + * **LINK**: [https://github.com/boto/botocore/issues/1351](https://github.com/boto/botocore/issues/1351) + * **LINK**: [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + +### In-progress Development +The discussion about "In-progress Development" started at 16:24. + + * **LINK**: [https://code.launchpad.net/~dojordan/cloud-init/+git/cloud-init/+merge/334341](https://code.launchpad.net/~dojordan/cloud-init/+git/cloud-init/+merge/334341) + * **LINK**: [https://jenkins.ubuntu.com/server/view/cloud-init/job/cloud-init-ci-nightly/](https://jenkins.ubuntu.com/server/view/cloud-init/job/cloud-init-ci-nightly/) + +### Office Hours (next 30 minutes) +The discussion about "Office Hours (next 30 minutes)" started at 16:45. + + * **LINK**: [http://paste.ubuntu.com/26438334/](http://paste.ubuntu.com/26438334/) + * **LINK**: [http://paste.ubuntu.com/26438334/](http://paste.ubuntu.com/26438334/) + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (83) + * smoser (23) + * ajorg (16) + * powersj (10) + * ubot5 (6) + * meetingology (3) + * rharper (1) + + + +Full Log +---------------- + + + 16:08 `` \#startmeeting Cloud-init bi-weekly status meeting + + 16:08 `` Meeting started Mon Jan 22 16:08:22 2018 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:08 `` + + 16:08 `` Available commands: action commands idea info link nick + + 16:08 `` certianly ajorg :) (on office hours) + + 16:09 `` Welcome to another episode of cloud-init bi-weekly status. We'll chat about about cloud-init updates and in progress work, and we'l drop into office hours for ongoing discussions/bug work etc. + + 16:10 `` \#topic Recent changes + + 16:11 `` Just walking through git-log for what we have committed in the last couple of weeks, here's the brief summary + + 16:12 `` thx smoser + + 16:12 `` - shorten the message in the exception per powersj feedback + + 16:12 `` - Use the same botocore session so the patched changes stick. + + 16:12 `` - fix bad use of % + + 16:12 `` - Fix console_log, improve comments and raise PlatformError on. + + 16:12 `` - tests: Fix EC2 Platform to return console output as bytes. + + 16:12 `` - tests: remove zesty as supported OS to test [Joshua Powers] + + 16:12 `` - Do not log warning on config files that represent None. (LP: \#1742479) + + 16:12 `` Launchpad bug 1742479 in cloud-init (Ubuntu) "setting manual_cache_clean causes warning" [Medium,Fix released] [https://launchpad.net/bugs/1742479](https://launchpad.net/bugs/1742479) + + 16:12 `` - tests: Use git hash pip dependency format for pylxd. + + 16:12 `` - tests: add integration requirements text file [Joshua Powers] + + 16:12 `` - MAAS: add check_instance_id based off oauth tokens. (LP: \#1712680) + + 16:12 `` - tests: update apt sources list test [Joshua Powers] + + 16:12 `` - tests: clean up image properties [Joshua Powers] + + 16:12 `` - tests: rename test ssh keys to avoid appearance of leaking private keys. + + 16:12 `` Launchpad bug 1712680 in maas-images "cloud-init re-generates network config every reboot overwriting manual admin changes on CentOS." [Undecided,New] [https://launchpad.net/bugs/1712680](https://launchpad.net/bugs/1712680) + + 16:12 `` [Joshua Powers] + + 16:12 `` - tests: Enable AWS EC2 Integration Testing [Joshua Powers] + + 16:12 `` - cli: cloud-init clean handles symlinks (LP: \#1741093) + + 16:12 `` Launchpad bug 1741093 in cloud-init "cloud-init clean traceback on instance dir symlink" [Low,Fix committed] [https://launchpad.net/bugs/1741093](https://launchpad.net/bugs/1741093) + + 16:13 `` What's being patched in botocore? + + 16:13 `` So a number of changes went into integration test related work, separating out requirements files. + + 16:14 `` MAASDatasource now also has smarted cache handling based on oauth token renewal from the maas server + + 16:14 `` so botocore is used by integration tests only as a mechanism to talk to the instance under test... looking back at the specifics here + + 16:14 `` it might have just been shuffling out how and where we define the dependency + + 16:14 `` blackboxsw: (my 'paste' to you was bad... [http://paste.ubuntu.com/26438113/](http://paste.ubuntu.com/26438113/) is better, showing only those on master, not my local branch that was currently checked out ) + + 16:15 `` heh, oopsie daisy let's paste again inline then + + 16:15 `` - tests: remove zesty as supported OS to test [Joshua Powers] + + 16:15 `` - Do not log warning on config files that represent None. (LP: \#1742479) + + 16:15 `` - tests: Use git hash pip dependency format for pylxd. + + 16:15 `` - tests: add integration requirements text file [Joshua Powers] + + 16:15 `` - MAAS: add check_instance_id based off oauth tokens. (LP: \#1712680) + + 16:15 `` - tests: update apt sources list test [Joshua Powers] + + 16:15 `` - tests: clean up image properties [Joshua Powers] + + 16:15 `` - tests: rename test ssh keys to avoid appearance of leaking private keys. + + 16:15 `` [Joshua Powers] + + 16:15 `` - tests: Enable AWS EC2 Integration Testing [Joshua Powers] + + 16:15 `` - cli: cloud-init clean handles symlinks (LP: \#1741093) + + 16:15 `` Launchpad bug 1742479 in cloud-init (Ubuntu) "setting manual_cache_clean causes warning" [Medium,Fix released] [https://launchpad.net/bugs/1742479](https://launchpad.net/bugs/1742479) + + 16:15 `` Launchpad bug 1712680 in maas-images "cloud-init re-generates network config every reboot overwriting manual admin changes on CentOS." [Undecided,New] [https://launchpad.net/bugs/1712680](https://launchpad.net/bugs/1712680) + + 16:15 `` Launchpad bug 1741093 in cloud-init "cloud-init clean traceback on instance dir symlink" [Low,Fix committed] [https://launchpad.net/bugs/1741093](https://launchpad.net/bugs/1741093) + + 16:15 `` ok the real deal, that looks better + + 16:16 `` ahh ajorg that interim commit message on botocore was about integration tests caching the session information during testing so we don't recreate that session with every ssh connection to the instance + + 16:16 `` just a little time savings per review comments on powersj branch I believe + + 16:17 `` okay, so nothing that needs to get upstreamed to botocore? + + 16:17 `` I don't think so, powersj smoser I have vague recollection of someone filing an upstream botocore issue. did we have to do that for something else though? + + 16:18 `` [https://github.com/boto/botocore/issues/1351](https://github.com/boto/botocore/issues/1351) + + 16:18 `` that was the issue smoser put in ^ + + 16:18 `` nice recall powersj thanks. + + 16:18 `` \#link [https://github.com/boto/botocore/issues/1351](https://github.com/boto/botocore/issues/1351) + + 16:20 `` ajorg: you can read that bug. imo they have a data loss error, but not one that they can easily fix without causing failures in places that previously ran fine. + + 16:20 `` I'll ask them to re-open it. + + 16:21 `` At the very least they should answer your last. + + 16:21 `` thanks. + + 16:22 `` Generally anything significant that we have landed (and any inprogress work) should be available at the following link. + + 16:22 `` \#link [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + + 16:23 `` anything else we should note over the last couple weeks? + + 16:23 `` otherwise I'll switch to ongoing work topic + + 16:24 `` \#topic In-progress Development + + 16:25 `` As you may have seen last week, we've gotten through a few passes and discussions around dojordan's branch to define pre-provisioning + + 16:25 `` \#link [https://code.launchpad.net/~dojordan/cloud-init/+git/cloud-init/+merge/334341](https://code.launchpad.net/~dojordan/cloud-init/+git/cloud-init/+merge/334341) + + 16:26 `` some of that discussion resulted in a new context manager: EphemeralDHCPv4 to support a sandboxed dhclient request on an instance. + + 16:27 `` this context manager affects Ec2 datasource a bit as it encapsulates all of the dhcp request ->` EphemeralIPV4Network calls that Ec2 was doing + + 16:28 `` there may be a couple other datasources that follow suit with this type of sandboxed dhcp request in weeks to come + + 16:28 `` glad it turned out to be generally useful rather than only specifically to ec2 + + 16:28 `` absolutely + + 16:30 `` Some other in-progress bits look like we might try focusing a bit more on chrony support and gettting robjo's branches some more eyes. + + 16:31 `` and some work on Ubuntu snappy support per the snappy and snap config modules. + + 16:31 `` dojordan: i just put one comment on your mp. /me thanks dojordan again for his patience. + + 16:32 `` rharper: smoser powersj anything more in the immediate pipeline that I'm missing/ + + 16:32 `` ? + + 16:32 `` blackboxsw: we should get the EphemeralDHCP thingy into the digital ocean datasource also. + + 16:32 `` blackboxsw: a reply to the network discussion on the list from the azure folks and robjo + + 16:32 `` I took another look at [https://code.launchpad.net/~yeazelm/cloud-init/+git/cloud-init/+merge/331897](https://code.launchpad.net/~yeazelm/cloud-init/+git/cloud-init/+merge/331897) and saw that origin/master seems to be failing some of the integration tests too. + + 16:32 `` (at least for me, locally, on a 16.04 instance) + + 16:32 `` ahhh right forgot about all your work there rharper, thanks! + + 16:33 `` ajorg: [https://jenkins.ubuntu.com/server/view/cloud-init/job/cloud-init-ci-nightly/](https://jenkins.ubuntu.com/server/view/cloud-init/job/cloud-init-ci-nightly/) + + 16:33 `` that is nigytly run of trunk + + 16:33 `` \#link [https://jenkins.ubuntu.com/server/view/cloud-init/job/cloud-init-ci-nightly/](https://jenkins.ubuntu.com/server/view/cloud-init/job/cloud-init-ci-nightly/) + + 16:34 `` I'll try blackholing IMDS on my instance. Could be that's interfering with something. + + 16:35 `` it is red, but 218 (green) and 219 (red) used the same git has on trunk (5cc0b19b8). + + 16:35 `` I'll follow up during office hours + + 16:36 `` can you give me example of your failures ? we had "disk full" errors recently on our jenkins, so that might be the cause of the issue for 291. + + 16:36 `` s/291/219/ + + 16:36 `` I don't remember seeing that traceback recently. w/ warning messages present in cloud-init + + 16:36 `` powersj: ? can you explain lxc timeout failure at + + 16:36 `` [https://jenkins.ubuntu.com/server/view/cloud-init/job/cloud-init-ci-nightly/219/consoleFull](https://jenkins.ubuntu.com/server/view/cloud-init/job/cloud-init-ci-nightly/219/consoleFull) + + 16:37 `` smoser: we discovered that our qemu-migration test was installing lxd from the archive and causing conflicts with the snap installed lxd + + 16:37 `` I have a message to christian to prevent it, and I have already cleaned it up + + 16:37 `` so new runs should pass + + 16:37 `` 2018-01-22 16:19:03,550 - tests.cloud_tests - WARNING - test case: modules/ssh_import_id failed TestSshImportId.test_no_stages_errors with: AssertionError: 1 != 0 : errors ['(\'ssh-import-id\', ProcessExecutionError("Unexpected error while running command.\\nCommand: [\'sudo\', \'-Hu\', \'ubuntu\', \'ssh-import-id\', \'gh:powersj\', \'lp:smoser\']\\nExit code: 1\\nReason: -\\nStdout: -\\nStderr: -",))'] were encountered in stage m + + 16:38 `` hm.. well, that will hit launchpad.net over https + + 16:38 `` cloud-init-output.log probaly has more info (should be collected) + + 16:38 `` the actual error is: File "/var/lib/jenkins/slaves/torkoal/workspace/cloud-init-ci-nightly/tests/cloud_tests/platforms/instances.py", line 142, in _wait_for_system + + 16:38 `` raise OSError('timeout: after {}s system not started'.format(time)) + + 16:38 `` it is because when the qemu tests installed lxd it didn't initialize lxd networking + + 16:38 `` so no IP is received + + 16:39 `` ajorg: would you have had outbound access to launchpad https ? if not, then that'd be expected failure. + + 16:40 `` oh, and i guess 'gh:powersj' (github) + + 16:40 `` smoser: I'll check some things, but in short yes. Maybe lxc is being weird? + + 16:40 `` i dont like our user names in that test though... + + 16:40 `` smoser: we could use the bot instead + + 16:42 `` smoser: it's a public ec2 instance with no special outbound rules, and I can connect to public https sites from a normal session. + + 16:44 `` hrm, ok let's chat about what we can do to anonymize or drop that type of test data if we can + + 16:44 `` probably time to kick over to office hours + + 16:45 `` \#topic Office Hours (next 30 minutes) + + 16:45 `` powersj: well, i think i'd prefer some public key that we state "no one has the private key for this." + + 16:46 `` obviously we could lie about that, but one would *expect* that you and I would gain access to the system using our public keys. + + 16:46 `` it doens't make me feel a lot better that a bot could/can. + + 16:47 `` Is there a way to limit integration testing to a specific test? + + 16:47 `` Feel free to bring up any topic/bugs/branches/features you'd like discussion on. We can also continue our discussion on the ssh key imports in teting + + 16:47 `` (takes a long time to run the full suite) + + 16:48 `` ajorg: yes + + 16:48 `` (reverse-i-search)`cloud_t': python3 -m tests.cloud_tests run --os-name=artful --platform=nocloud-kvm --preserve-data --data-dir=../results --verbose -t modules/locale -t modules/set_password + + 16:48 `` thanks, that should help + + 16:48 `` ajorg: you can specify the test names (like modules/set_password) and modules/locale in this test + + 16:48 `` yeah those are short ones I frequently test with + + 16:49 `` [http://paste.ubuntu.com/26438334/](http://paste.ubuntu.com/26438334/) + + 16:49 `` that is what i use. and yeah... we've discussed that integration test could be easier to run :) + + 16:49 `` \#link [http://paste.ubuntu.com/26438334/](http://paste.ubuntu.com/26438334/) + + 16:49 `` nice 1 + + 16:51 `` smoser: to have a public key we know nobody has a private key for would that mean we'd need a separate github account (or maybe just an additional key associated w/ our bot account in gh + + 16:51 * blackboxsw checks github for authorizing multiple keys. + + 16:51 `` hrm, that wouldn't work as we need gh:ubuntu-server-bot (one key) n/m + + 16:52 `` I've got meetings most of today, so I'll have to follow up later. thanks everyone! + + 16:52 `` thanks ajorg + + 16:59 `` so, bot account for the time being is better than powersj owning the testing world ;) + + 16:59 `` but I'm not too concerned about it as this are supposed to be throw away instances + + 16:59 `` but I'm not too concerned about it as there instances under test are supposed to be throw away instances + + 17:00 `` *these instances*.... anyway + + 17:04 `` blackboxsw: right. it would require users on both those services . + + 17:14 `` alrighty. think we're at the close of office hours. Last call? + + 17:16 `` Thanks for your time and contributions to cloud-init folks! + + 17:16 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) diff --git a/content/status-2018-04-02.md b/content/status-2018-04-02.md new file mode 100644 index 0000000..d199ee4 --- /dev/null +++ b/content/status-2018-04-02.md @@ -0,0 +1,241 @@ +Title: Cloud-init bi-weekly status +Date: 2018-04-02 16:05:00 UTC +Category: status-meeting-minutes +Slug: status-2018-04-02 + +Meeting information +---------------- + * \#cloud-init: bi-weekly status meeting, 02 Apr at 16:05 — 17:03 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-04-02-16.05.log.html](http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-04-02-16.05.log.html)]] + + + +Meeting summary +---------------- + +### Recent Changes +The discussion about "Recent Changes" started at 16:08. + + * **LINK**: [https://lists.launchpad.net/cloud-init/msg00145.html](https://lists.launchpad.net/cloud-init/msg00145.html) + * **LINK**: [https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/fix/cc_resizefs_on_zfs_root](https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/fix/cc_resizefs_on_zfs_root) + +### In-progress Development +The discussion about "In-progress Development" started at 16:19. + + * **LINK**: [https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/fix/cc_resizefs_on_zfs_root](https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/fix/cc_resizefs_on_zfs_root) + * **LINK**: [https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/342007](https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/342007) + * **LINK**: [https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/342428](https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/342428) + * **LINK**: [https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/342010](https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/342010) + * **LINK**: [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + +### Office Hours (next ~30 minutes) +The discussion about "Office Hours (next ~30 minutes)" started at 16:27. + + * **LINK**: [https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/339438](https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/339438) + * **LINK**: [https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/339438](https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/339438) + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (64) + * rharper (14) + * ubot5 (3) + * meetingology (3) + * powersj (2) + + + +Full Log +---------------- + + + 16:05 `` \#startmeeting bi-weekly status meeting + + 16:05 `` Meeting started Mon Apr 2 16:05:50 2018 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:05 `` + + 16:05 `` Available commands: action commands idea info link nick + + 16:06 `` Welcome to the post-Easter episode of cloud-init's status meeting 🐰 + + 16:06 `` Today's meeting will probably be light as we are fairly light on attendees given various holiday schedules + + 16:07 `` o/ + + 16:07 `` nice rabbit ears + + 16:07 `` heya! As always, we'll go through recent changes, in progress work and ~30 minutes of office hours + + 16:08 `` feel free to interject and ask quesitons at any time. + + 16:08 `` \#topic Recent Changes + + 16:09 `` Here's a brief run down of what we have committed to master in the last couple weeks + + 16:10 `` - Support for setting hostname from metadata prior to network bringup. + + 16:10 `` This fixes vsphere multi-vm deployments all coming up with the same + + 16:10 `` 'ubuntu' hostname. [LP: \#1746455]([http://pad.lv/1746455](http://pad.lv/1746455)) + + 16:10 `` - Support initramfs iscsi root so network devices aren't disconnected + + 16:10 `` before shutdown + + 16:10 `` - Added cloud-config module `cc_snap` which enables loading snap + + 16:10 `` assertions, configuring snapd and installing snap packages on Ubuntu. + + 16:10 `` Launchpad bug 1746455 in cloud-init "cloud-init vSphere cloud provider DHCP unique hostname issue" [High,Fix released] + + 16:10 `` Deprecated `cc_snappy` and `cc_snap_config` modules. + + 16:10 `` - Make salt minion work on FreeBSD (Dominic Schlegel) + + 16:10 `` [LP:\#1721503]([http://pad.lv/1721503](http://pad.lv/1721503)) + + 16:10 `` - Simplify compound conditionals (Rémy Léone) + + 16:10 `` Launchpad bug 1721503 in cloud-init "salt module not able to be used on FreeBSD" [Medium,Fix released] + + 16:10 `` - Change some list creation and population to literals (Rémy Léone) + + 16:10 `` - Add puppet 4 support configurable in `cc_puppet` module (Romanos + + 16:10 `` Skiadas) + + 16:10 `` - Fix datasouce Azure `get_hostname` function for hostname bounce + + 16:10 `` (Douglas Jordan) [LP:\#1754495]([http://pad.lv/1754495](http://pad.lv/1754495)) + + 16:10 `` - OpenNebula datasource now uses network config v2 to support IPv6 + + 16:10 `` Launchpad bug 1755965 in cloud-init (Ubuntu) "duplicate for \#1754495 util.subp regression: no longer accept commands as string" [Critical,Fix released] + + 16:10 `` config (Akihiko Ota) + + 16:10 `` - Add Hetzner Cloud datasource support (Markus Schade) + + 16:11 `` The highlights of this work that will affect various clouds: hostname setting before network bringup, in cloud-init's init-local stage. + + 16:12 `` so if your cloud's metadata provides hostname information (per your instance creation) that hostname gets set before any potential dhcp discovery on the instance. This is a big win for Azure and may allow us to avoid/deprecate some of the hostname_bounce functionality + + 16:13 `` which was baked in to re-dhcp in order to publish updated hostname information to DDNS + + 16:14 `` We also have landed support for two new clouds: Hetzner Cloud and IBMCloud. A big thanks to Markus Schade for the Hetzner work there and smoser for the IBMCloud datasource + + 16:15 `` do3meli (Dominic Schlegel) has also been on a blitz fixing and updating a lot of FreeBSD support in cloud-init tip so thank you sir for that work as well. + + 16:16 `` We've just also landed some zfs resize support by rharper as well that should be making it's way into your friendly neighborhood Ubuntu Bionic series in a cloud near you + + 16:16 `` anything else I'm missing on rharper or powersj ? + + 16:16 `` ahh hold the phone + + 16:16 `` blackboxsw: well, not my zfs-resize + + 16:17 `` but I do have some fixes for it + + 16:17 `` [https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/fix/cc_resizefs_on_zfs_root](https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/fix/cc_resizefs_on_zfs_root) + + 16:17 `` We officially released cloud-init 18.2 in master. There is an 18.2 tag in the repo for folks wanting to take an early cut of it. + + 16:17 `` our ci-test backend normally runs with zfs, it's not right now so it missed a couple edge cases that we need to handle + + 16:18 `` Per cloud-init 18.2 here is an email sent to the cloud-init mailing list describing the details: [https://lists.launchpad.net/cloud-init/msg00145.html](https://lists.launchpad.net/cloud-init/msg00145.html) + + 16:18 `` \#link [https://lists.launchpad.net/cloud-init/msg00145.html](https://lists.launchpad.net/cloud-init/msg00145.html) + + 16:18 `` \#link [https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/fix/cc_resizefs_on_zfs_root](https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/fix/cc_resizefs_on_zfs_root) + + 16:19 `` \#topic In-progress Development + + 16:20 `` The upstream team has released 18,2 to Bionic as of last week, and we started an Ubuntu SRU process into Xenial and Artful. + + 16:21 `` We expect the 18.2 to be present in Xenial and Artful within 2 weeks in your cloud, so if you are waiting on a feature, it won't be very long. + + 16:22 `` Also in-progress are some of rharper's zfs fixes, and some exception callback cleanup that will affect Azure, EC2, OpenStack and Scaleway clouds. + + 16:22 `` \#link [https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/fix/cc_resizefs_on_zfs_root](https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/fix/cc_resizefs_on_zfs_root) + + 16:22 `` \#link [https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/342007](https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/342007) + + 16:23 `` And we are doing our part to finally purge net-tools dependencies from cloud-init (in favor of iproute2) + + 16:23 `` \#link [https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/342428](https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/342428) + + 16:24 `` blackboxsw: I responded to your ip -6 route q from last week, did you see that ? + + 16:24 `` rharper: haven't yet, but I'll grab those comments today for sure (I think I missed some of your earlier review comments) + + 16:24 `` ok + + 16:25 `` the tl;dr for that one is that you want this: ip -6 route list table all + + 16:25 `` ahh excellent, I was wondering why we were missing content for local routes etc + + 16:25 `` right + + 16:25 `` thanks + + 16:25 `` np + + 16:26 `` also, on our continuous integration front , powersj has put up a branch that I'd like to see us land with some ssh improvements + + 16:26 `` \#link [https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/342010](https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/342010) + + 16:26 `` :) yep + + 16:26 `` any other in-progress work worth noting? + + 16:27 `` Intereseted parties can always track our public trello board for a glimpse of what we are working on + + 16:27 `` \#link [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + + 16:27 `` \#topic Office Hours (next ~30 minutes) + + 16:28 `` We'll all have eyes glued to the screen for the next 30 minutes for rants, feature discussion and bug work. + + 16:29 `` With that, the floor is open for any topics. Thanks for tuning in. + + 16:30 `` My day today will be Ubuntu SRU(stable release update)-related, so I'm getting on rharper's zfs branch now and they running a couple manual tests on ec2/azure/openstack + + 16:30 `` +1 + + 16:30 `` oh, the ntp-spec update is ready for review and testing + + 16:31 `` [https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/339438](https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/339438) + + 16:32 `` ahh +1 we want that in too + + 16:32 `` \#link [https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/339438](https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/339438) + + 17:02 `` Alrighty, happy spring break all. + + 17:02 `` Next meeting will be two weeks from today. + + 17:03 `` powersj: rharper 4/16 look good for folks? + + 17:03 `` +1 from me + + 17:03 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2018-04-16.md b/content/status-2018-04-16.md new file mode 100644 index 0000000..5bf7678 --- /dev/null +++ b/content/status-2018-04-16.md @@ -0,0 +1,295 @@ +Title: Cloud-init bi-weekly status +Date: 2018-04-16 16:01:00 UTC +Category: status-meeting-minutes +Slug: status-2018-04-16 + +Meeting information +---------------- + * \#cloud-init: Cloud-init bi-weekly status meeting, 16 Apr at 16:01 — 18:11 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-04-16-16.01.log.html](http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-04-16-16.01.log.html)]] + + + +Meeting summary +---------------- + +### Recent-changes +The discussion about "Recent-changes" started at 16:04. + + +### In-progresss Development +The discussion about "In-progresss Development" started at 16:11. + + * **LINK**: [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + * **LINK**: [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1759406](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1759406) + * **LINK**: [https://bugs.launchpad.net/bugs/1570997](https://bugs.launchpad.net/bugs/1570997) + * **LINK**: [https://trello.com/c/JVaXSfpo/749-eol-fix-for-ssh-file](https://trello.com/c/JVaXSfpo/749-eol-fix-for-ssh-file) + * **LINK**: [https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/343123](https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/343123) + +### Office Hours (next ~30 mins) +The discussion about "Office Hours (next ~30 mins)" started at 16:23. + + * **LINK**: [https://bugs.launchpad.net/cloud-init/+bug/1667735](https://bugs.launchpad.net/cloud-init/+bug/1667735) implements proper protocol negotiation over the serial port. The lack of this has caused problems with KVM at times too. + * **LINK**: [https://bugs.launchpad.net/cloud-init/+bug/1746605](https://bugs.launchpad.net/cloud-init/+bug/1746605) adressess times when cloud-init and other software may be trying to use the metadata serial port at the same time. This is purely a bug fix. + * **LINK**: [https://bugs.launchpad.net/cloud-init/+bug/1763480](https://bugs.launchpad.net/cloud-init/+bug/1763480) makes it so that cloud-init doesn't stack trace and exit when there is no customer_metadata. This is an unlikely case, but something that is hit when you are testing things that don't need ssh keys, etc. + * **LINK**: [https://bugs.launchpad.net/cloud-init/+bug/1763512](https://bugs.launchpad.net/cloud-init/+bug/1763512) finishes off the partial implementation of sdc:routes support. Previously, we didn't publish the required information to VMs, so it is fair to consider this a new feature. + * **LINK**: [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1763511](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1763511) is probably the most incompatible change. New ephemeral disks will get ext4 instead of ext3, which is needed for larger disks that seem to be getting more common. + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (54) + * smoser (17) + * rharper (13) + * mgerdts (10) + * ubot5` (10) + * cyphermox (3) + * meetingology (3) + * dpb1 (1) + + + +Full Log +---------------- + + + 16:01 `` \#startmeeting Cloud-init bi-weekly status meeting + + 16:01 `` Meeting started Mon Apr 16 16:01:49 2018 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:01 `` + + 16:01 `` Available commands: action commands idea info link nick + + 16:02 `` o/ + + 16:03 `` Hi folks, welcome to cloud-init's bi-weekly status meeting. Feel free to interject at any time or bring up branches/bugs/questions over the next 30-60 mins. We'll have a number of folks around to get eyes and/or keyboards onto any problems. + + 16:03 `` o/ + + 16:04 `` As always we'll go through the following topics (feel free to suggest others): Recent-changes, In-progress Development, and ~30 mins Office Hours) + + 16:04 `` \#topic Recent-changes + + 16:06 `` a quick rundown of the hi level changes landed: + + 16:06 `` Prune integration test artifacts + + 16:06 `` Add support for LXD 3.0, fix pylxd integration test dependency + + 16:06 `` Fix Ubuntu proposed integration test CI job + + 16:06 `` Fix ec2 validation of instance-data.json network info + + 16:06 `` Do not retry optional userdata on 404 (LP: \#1702160) + + 16:06 `` Add explicit cloud-init package dependency on isc-dhcp-client (LP: \#1759307) + + 16:06 `` Launchpad bug 1702160 in cloud-init "OpenStack datasource should not retry user-data on 404" [Medium,Fix released] [https://launchpad.net/bugs/1702160](https://launchpad.net/bugs/1702160) + + 16:06 `` Launchpad bug 1759307 in cloud-init (Ubuntu) "missing dependency on isc-dhcp-client (dhclient)" [Medium,Fix released] [https://launchpad.net/bugs/1759307](https://launchpad.net/bugs/1759307) + + 16:08 `` additionally from most recent commits we have: + + 16:08 `` tools: Fix make-tarball cli tool usage for development + + 16:08 `` renderer: support unicode in render_from_file. + + 16:08 `` Implement ntp client spec with auto support for distro selection + + 16:08 `` Apport: add Brightbox, IBM, LXD, and OpenTelekomCloud to list of clouds. + + 16:08 `` tests: fix ec2 integration network metadata validation + + 16:08 `` tests: fix integration tests to support lxd 3.0 release + + 16:08 `` correct documentation to match correct attribute name usage. + + 16:08 `` cc_resizefs, util: handle no /dev/zfs + + 16:09 `` Last week rharper found and fixed a regression in zfs resize behavior that was blocking our ubuntu SRU + + 16:09 `` We have uploaded those fixes, as well as rharper's ntp spec changes (which should incorporate a number of robjo's opensuse/sles needs too) + + 16:10 `` anything else notable that I'm missing gentlemen? + + 16:10 `` If not, I'll jump to in-progress development + + 16:11 `` \#topic In-progresss Development + + 16:13 `` So, on the ubuntu side of the house we are about to approve the cloud-init 18.2 SRU (Stable release update) into xenial and artful. Just one more validation run and we should be good to see 18.2.4 on xenial, artful. Ubuntu Bionic is already a few commits beyond that. + + 16:13 `` On Ubuntu as well we are beating the drop to the Bionic LTS (Long term release) feature/bug freeze. + + 16:14 `` This week marks the last week for use to get fixes into Bioinic images before that release is cut. + + 16:14 `` so we'll be heads down on any Bionic-specific changes that need to get in. + + 16:14 `` Feel free to checkout our trello board @ + + 16:14 `` \#link [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + + 16:15 `` we track all tasks we are working on in public view there so if there are any questions you can ping one of us here about our development efforts + + 16:17 `` additional tasks that are in flight: bash-autocompletion for cloud-init CLI (rhaper). dropping ifconfig and route in favor of 'ip' (bbsw), and moving openstack datasource to cloud-init's local stage + + 16:17 `` (smoser) + + 16:17 `` also a couple of bugs to fix such as \#1570997 + + 16:17 `` \#link [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1759406](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1759406) + + 16:17 `` Ubuntu bug 1759406 in cloud-init (Ubuntu) "sru cloud-init (17.2-35-gf576b2a2-0ubuntu1~16.04.1 update to 18.2-4-g05926e48-0ubuntu1)" [Medium,Confirmed] + + 16:17 `` oops paste fail: + + 16:17 `` \#link [https://bugs.launchpad.net/bugs/1570997](https://bugs.launchpad.net/bugs/1570997) + + 16:17 `` Ubuntu bug 1570997 in ssh-import-id (Ubuntu Xenial) "fail if HOME environment variable is not set" [Low,Fix committed] + + 16:18 `` I think that about wraps in-progress development, anything else that should be noted smoser rharper ? + + 16:18 `` I think you covered it + + 16:18 `` ssh-import-id is not relally at all related to cloud-init + + 16:19 `` thanks blackboxsw + + 16:19 `` oops grabbed the wrong one, was thinking about this card + + 16:19 `` \#link [https://trello.com/c/JVaXSfpo/749-eol-fix-for-ssh-file](https://trello.com/c/JVaXSfpo/749-eol-fix-for-ssh-file) + + 16:19 `` right. + + 16:21 `` also of note, in some of our SRU testing we found time-tracking gaps in cloud-init analyze tracking on Azure. rharper put of a logging tracker fix to avoid those tracking gaps + + 16:21 `` \#link [https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/343123](https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/343123) + + 16:21 `` i'll point out one thing i just finished up with... + + 16:22 `` for testing ubuntu, the [https://github.com/cloud-init/ubuntu-sru/](https://github.com/cloud-init/ubuntu-sru/) has 'get-proposed-cloudimg' and 'lxc-proposed-snapshot' + + 16:22 `` which now work more like each other.l and can do more than just upgrade cloud-init. + + 16:23 `` thanks smoser. Great tools to quicken dev-test cycles and make cloud-init development easier. That wraps up what we've been up to. We can probably move to the open forum for any discussions folks want to have + + 16:23 `` \#topic Office Hours (next ~30 mins) + + 16:24 `` We'll be hanging out here for anyone who wants more eyes on a review, feature discussions or bug triage.... + + 16:28 `` mgerdts: i'm poking at the branch i think i shoudl be able to get something. + + 16:29 `` I'm working on a bunch of fixes for things that have turned up on bhyve with SmartOS. Since we are looking to transition from KVM to bhyve, we will need to provide updates at least as far back as xenial and probably trusty. Is the process for this any more complicated than get the fixes in master, then cherry-pick the fixes into branches? + + 16:29 `` thanks @smoser + + 17:09 `` mgerdts: we preferrer not to cherry; rather we release master back to xenial via our SRU (Stable Release Update) process; however, we spend a lot of effort to not modify existing behavior on prevlous SRU releases; so if the changes to support bhyve can be done in a compatible way (working with either) that'd be best; worst-case, we patch in release specific bahvior into the release branch. + + 17:13 `` Pretty much everything that I've got queued up is fully compatible. + + 17:14 `` [https://bugs.launchpad.net/cloud-init/+bug/1667735](https://bugs.launchpad.net/cloud-init/+bug/1667735) implements proper protocol negotiation over the serial port. The lack of this has caused problems with KVM at times too. + + 17:14 `` Ubuntu bug 1667735 in cloud-init (Ubuntu Trusty) "cloud-init doesn't retry metadata lookups and hangs forever if metadata is down" [Medium,Confirmed] + + 17:15 `` [https://bugs.launchpad.net/cloud-init/+bug/1746605](https://bugs.launchpad.net/cloud-init/+bug/1746605) adressess times when cloud-init and other software may be trying to use the metadata serial port at the same time. This is purely a bug fix. + + 17:15 `` Ubuntu bug 1746605 in cloud-init "DataSourceSmartOS needs locking" [Medium,Confirmed] + + 17:15 `` I hit it when rc.local and cloud-init were both trying to get metadata. + + 17:17 `` [https://bugs.launchpad.net/cloud-init/+bug/1763480](https://bugs.launchpad.net/cloud-init/+bug/1763480) makes it so that cloud-init doesn't stack trace and exit when there is no customer_metadata. This is an unlikely case, but something that is hit when you are testing things that don't need ssh keys, etc. + + 17:17 `` Ubuntu bug 1763480 in cloud-init "DataSourceSmartOS list() should always return a list" [Medium,Confirmed] + + 17:18 `` [https://bugs.launchpad.net/cloud-init/+bug/1763512](https://bugs.launchpad.net/cloud-init/+bug/1763512) finishes off the partial implementation of sdc:routes support. Previously, we didn't publish the required information to VMs, so it is fair to consider this a new feature. + + 17:18 `` Ubuntu bug 1763512 in cloud-init "DataSourceSmartOS ignores sdc:routes" [Medium,Confirmed] + + 17:19 `` [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1763511](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1763511) is probably the most incompatible change. New ephemeral disks will get ext4 instead of ext3, which is needed for larger disks that seem to be getting more common. + + 17:19 `` Ubuntu bug 1763511 in cloud-init (Ubuntu) "DataSourceSmartOS should default to ext4" [Undecided,New] + + 17:21 `` I think that's all that I have in the works right now. Do any of these sound like they would be problematic as far back as Xenial? + + 17:29 `` new features are OK ,bug fixes are fine as well; I think that different filesystem is somewhat tricky + + 17:30 `` i think i'm generally ok with the different filesystem. + + 17:31 `` if the reason is that simply ext3 can't handle super-big + + 17:31 `` yeah, that doesn't seem so user-visible w.r.t configuration; + + 17:32 `` we could ensure being more backward compat if we checked the size of the disk and made an ext4 if >` that-size + + 17:32 `` then there'd less issue + + 17:32 `` but more complication and future we'd be stuck with that + + 17:32 `` yeah, it wouldn't have worked on ext3 then it would be fine to use ext4 + + 17:32 `` so i'd rather really just bite the bulleet + + 17:32 `` it could be a metadata flag that the Datasource looks for + + 17:32 `` rather than describing to pepole forever "well, if your disk is `< X you'll get ext3 otherwise ext4" + + 17:49 `` rharper: got time for a netplan global dns hangout? + + 17:49 `` y + + 17:49 `` I want to make sure I'm reading the tea leaves right + + 17:52 `` mgerdts: [http://paste.ubuntu.com/p/5qdtFzY8w7/](http://paste.ubuntu.com/p/5qdtFzY8w7/) + + 17:52 `` ok rharper I'm in cloud-init hangout + + 17:52 `` that makes tests pass. and i think the changes to the code path are right + + 17:52 `` ok + + 17:52 `` brt + + 17:54 `` it is still hacked in a sense that the response only deals with fp.read(1) rather than possibly anything that read more than 1. + + 17:56 `` blackboxsw: rharper: what's this about netplan global dns? + + 17:57 `` cyphermox: converting network v1 syntax from maas into something that works with netplan which doesn't have "dns" unbound to any interfaces + + 17:57 `` ok + + 17:57 `` maas I believe has fixed this for 2.4.x + + 17:58 `` they no longer will emit the type: nameserver but legacy maas would have that, so we've a branch that stuffs them in reasonable places under defined interfaces which don't already have DNS values + + 17:58 `` cyphermox: just SRU validation w.r.t. [https://bugs.launchpad.net/cloud-init/+bug/1750884](https://bugs.launchpad.net/cloud-init/+bug/1750884) + + 17:59 `` Ubuntu bug 1750884 in cloud-init "[2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution" [Medium,Fix released] + + 17:59 `` all good + + 18:11 `` ooops, and /me forgot the end the epic meeting + + 18:11 `` thx rharper for the chat + + 18:11 `` \#endmeetiung + + 18:11 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2018-04-30.md b/content/status-2018-04-30.md new file mode 100644 index 0000000..f9e196c --- /dev/null +++ b/content/status-2018-04-30.md @@ -0,0 +1,412 @@ +Title: Cloud-init bi-weekly status +Date: 2018-04-30 16:04:00 UTC +Category: status-meeting-minutes +Slug: status-2018-04-30 + +Meeting information +---------------- + * \#cloud-init: Cloud-init bi-weekly status meeting, 30 Apr at 16:04 — 17:14 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-04-30-16.04.log.html](http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-04-30-16.04.log.html)]] + + + +Meeting summary +---------------- + +### Recent Changes +The discussion about "Recent Changes" started at 16:07. + + +### \#cloud-init Reviews: [http://bit.ly/ci-reviews](http://bit.ly/ci-reviews) | Meeting minutes: [https://goo.gl/mrHdaj](https://goo.gl/mrHdaj) | Next status meeting: Monday 5/14 16:00 UTC | cloud-init 18.2 released (03/28/2018) +The discussion about "\#cloud-init Reviews: [http://bit.ly/ci-reviews](http://bit.ly/ci-reviews) | Meeting minutes: [https://goo.gl/mrHdaj](https://goo.gl/mrHdaj) | Next status meeting: Monday 5/14 16:00 UTC | cloud-init 18.2 released (03/28/2018)" started at 16:08. + + * **LINK**: [https://jenkins.ubuntu.com/server/job/cloud-init-integration-proposed-b/](https://jenkins.ubuntu.com/server/job/cloud-init-integration-proposed-b/) + * **LINK**: [https://code.launchpad.net/~cloud-init-dev/cloud-init/+git/cloud-init/+ref/master/+activereviews](https://code.launchpad.net/~cloud-init-dev/cloud-init/+git/cloud-init/+ref/master/+activereviews) + +### In-progresss Development +The discussion about "In-progresss Development" started at 16:21. + + * **LINK**: [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1767412](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1767412) + * **LINK**: [https://code.launchpad.net/~jocha/cloud-init/+git/cloud-init/+merge/344192](https://code.launchpad.net/~jocha/cloud-init/+git/cloud-init/+merge/344192) + * **LINK**: [https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/344181](https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/344181) + * **LINK**: [https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/344198](https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/344198) + +### Office Hours (next ~30 mins) +The discussion about "Office Hours (next ~30 mins)" started at 16:31. + + * **LINK**: [https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712](https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712) + * **LINK**: [https://github.com/SUSE/Enceladus/tree/master/cloud-netconfig](https://github.com/SUSE/Enceladus/tree/master/cloud-netconfig) + * **ACTION**: blackboxsw to have discussions w/ team on datasource maintaining network on each reboot per [https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712](https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712) + * **LINK**: [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538) + * **LINK**: [https://hackmd.io/M1Tae41PQBC7a9qMsurTJw](https://hackmd.io/M1Tae41PQBC7a9qMsurTJw)?both + * **LINK**: [https://cloud-init.github.io/](https://cloud-init.github.io/) + + + +Vote results +---------------- + + + + +Action items, by person +---------------- + + * blackboxsw + * blackboxsw to have discussions w/ team on datasource maintaining network on each reboot per [https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712](https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712) + * mgerdts + * blackboxsw to have discussions w/ team on datasource maintaining network on each reboot per [https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712](https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712) + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (113) + * mgerdts (21) + * ubot5 (12) + * akik (5) + * stanguturi (4) + * meetingology (4) + * robjo (3) + + + +Full Log +---------------- + + + 16:04 `` \#startmeeting Cloud-init bi-weekly status meeting + + 16:04 `` Meeting started Mon Apr 30 16:04:15 2018 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:04 `` + + 16:04 `` Available commands: action commands idea info link nick + + 16:04 `` hi folks, sorry for the mis-representation of when our cloud-init status meeting date. It's time for another episode/update of the happenings in cloud-init. + + 16:05 `` Next meeting will be in two weeks: May 7th + + 16:05 `` at 16:00 UTC + + 16:06 `` The last couple weeks on the upstream side of the house has been a big push to get testing and stability into master for the Ubuntu Bionic release freeze + + 16:06 `` ... I'd better start with the topic + + 16:07 `` \#topic Recent Changes + + 16:07 `` The last couple weeks on the upstream side of the house has been a big push to get testing and stability into master for the Ubuntu Bionic release freeze. + + 16:07 `` May 7th would be 1 week from today that should be May 14th + + 16:07 `` robjo: gah, I did it again. Thank you... glad someone's listening. Next cloud-init status meeting Monday May 14th 16:00 UTC + + 16:08 `` \#topic \#cloud-init Reviews: [http://bit.ly/ci-reviews](http://bit.ly/ci-reviews) | Meeting minutes: [https://goo.gl/mrHdaj](https://goo.gl/mrHdaj) | Next status meeting: Monday 5/14 16:00 UTC | cloud-init 18.2 released (03/28/2018) + + 16:08 `` ok topic agrees in channel now, so I don't botch it at the end of meeting + + 16:09 `` Along with a blitz for stability in Bionic the following changes have been shepherded into tip of master + + 16:09 `` - Add reporting events and log_time around early source of blocking time + + 16:09 `` [Ryan Harper] + + 16:09 `` - IBMCloud: recognize provisioning environment during debug boots. + + 16:09 `` (LP: \#1767166) + + 16:09 `` - net: detect unstable network names and trigger a settle if needed + + 16:09 `` [Ryan Harper] (LP: \#1766287) + + 16:09 `` - IBMCloud: improve documentation in datasource. + + 16:09 `` Launchpad bug 1767166 in cloud-init (Ubuntu) "IBMCloud datasource does not recognize provisioning in debug mode." [Medium,Confirmed] [https://launchpad.net/bugs/1767166](https://launchpad.net/bugs/1767166) + + 16:09 `` - sysconfig: dhcp6 subnet type should not imply dhcpv4 [Vitaly Kuznetsov] + + 16:09 `` - packages/debian/control.in: add missing dependency on iproute2. + + 16:09 `` Launchpad bug 1766287 in cloud-init (Ubuntu) "18.04 minimal images on GCE intermittently fail to set up networking " [Undecided,In progress] [https://launchpad.net/bugs/1766287](https://launchpad.net/bugs/1766287) + + 16:09 `` (LP: \#1766711) + + 16:09 `` - DataSourceSmartOS: add locking of serial device. + + 16:09 `` [Mike Gerdts] (LP: \#1746605) + + 16:09 `` - DataSourceSmartOS: sdc:hostname is ignored [Mike Gerdts] (LP: \#1765085) + + 16:09 `` Launchpad bug 1766711 in cloud-init (Ubuntu Bionic) "cloud-init missing dependency on iproute2" [Medium,Fix committed] [https://launchpad.net/bugs/1766711](https://launchpad.net/bugs/1766711) + + 16:09 `` - DataSourceSmartOS: list() should always return a list + + 16:09 `` [Mike Gerdts] (LP: \#1763480) + + 16:09 `` Launchpad bug 1746605 in cloud-init "DataSourceSmartOS needs locking" [Medium,Fix committed] [https://launchpad.net/bugs/1746605](https://launchpad.net/bugs/1746605) + + 16:09 `` - schema: in validation, raise ImportError if strict but no jsonschema. + + 16:09 `` - set_passwords: Add newline to end of sshd config, only restart if + + 16:09 `` updated. (LP: \#1677205) + + 16:09 `` Launchpad bug 1765085 in cloud-init "DataSourceSmartOS ignores sdc:hostname" [Medium,Fix committed] [https://launchpad.net/bugs/1765085](https://launchpad.net/bugs/1765085) + + 16:09 `` - pylint: pay attention to unused variable warnings. + + 16:09 `` - doc: Add documentation for AliYun datasource. [Junjie Wang] + + 16:09 `` - Schema: do not warn on duplicate items in commands. (LP: \#1764264) + + 16:09 `` Launchpad bug 1763480 in cloud-init "DataSourceSmartOS list() should always return a list" [Medium,Fix committed] [https://launchpad.net/bugs/1763480](https://launchpad.net/bugs/1763480) + + 16:09 `` Launchpad bug 1677205 in cloud-init "cloud-init eats final EOL of sshd_config" [Medium,Fix committed] [https://launchpad.net/bugs/1677205](https://launchpad.net/bugs/1677205) + + 16:09 `` Launchpad bug 1764264 in juju 2.3 "bionic cloud-init 18.2 WARNING Juju's 'runcmd' stanza" [High,Triaged] [https://launchpad.net/bugs/1764264](https://launchpad.net/bugs/1764264) + + 16:10 `` the general theme has been: new IBMCloud datasource support for cloud-init, SmartOS datasource work by mgerdts, and some json schema improvements + + 16:12 `` so background on IBM, is that their support used to be ConfigDrive based datasource only, but there is now some additional support for different IBM boot/provisioning stages, hence a new datasource that can support different boot modew + + 16:12 `` *boot modes + + 16:14 `` over the last two weeks we've landed an SRU into xenial and artful: 18.2-4-g05926e48-0ubuntu1~16.04.1 and bionic sits at 18.2-14-g6d48d265-0ubuntu1 + + 16:15 `` On the SmartOS side, my changes are driven by our adoption of bhyve (moving away from kvm/qemu). qemu provides a dhcp server VMs could fall back to if could-init was missing or misbehaving. bhyve doesn't have that, so I've been working on getting cloud-init to be more stable with the bhyve serial metadata service. + + 16:15 `` Also, to our continuous integration on jenkins we now have an additional test for proposed packages in ubuntu for the bionic release to make sure ubuntu doesn't break across pending upgrades + + 16:15 `` \#link [https://jenkins.ubuntu.com/server/job/cloud-init-integration-proposed-b/](https://jenkins.ubuntu.com/server/job/cloud-init-integration-proposed-b/) + + 16:16 `` that integration tests hits the suite of platforms lxd, kvm and ec2 + + 16:16 `` excellent mgerdts, and thanks for the blitz on these branches + + 16:17 `` looks like there are a few still in our review queue that we'll be able to get through once the dust settles on the bionic release (which should be this week) + + 16:17 `` \#link [https://code.launchpad.net/~cloud-init-dev/cloud-init/+git/cloud-init/+ref/master/+activereviews](https://code.launchpad.net/~cloud-init-dev/cloud-init/+git/cloud-init/+ref/master/+activereviews) + + 16:19 `` Is now the right time to discuss bug 1765801, or is that later? + + 16:19 `` bug 1765801 in cloud-init "network should be optionally reconfigured on every boot" [Undecided,Confirmed] [https://launchpad.net/bugs/1765801](https://launchpad.net/bugs/1765801) + + 16:20 `` I think over the last 2 weeks there have been a couple of requests in channel for how someone goes about getting newer cloud init into RHEL7, if anyone on the line today knows the contact point or process for that it'd be helpful. larsks doesn't seem to be around + + 16:20 `` mgerdts: probably in about 10 mins. thanks for brining it up + + 16:20 `` hopefully less. + + 16:20 `` ok I think that's it for recent changes, next topic (in-progress dev, then office hours (and bug discussion)) + + 16:21 `` \#topic In-progresss Development + + 16:21 `` We'll make this one short: + + 16:22 `` for ubuntu : bionic just went feature freeze last week, our team has a couple of IBM-related cheanges that we are pulling together for a quick SRU into xenial/artful to handle upgrade path from configdrive ->` IBMCloud that we are working on the beginning of this week + + 16:22 `` we are also trying to wrap up validation of a Bionic SRU per the following bug + + 16:22 `` \#link [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1767412](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1767412) + + 16:22 `` Launchpad bug 1767412 in cloud-init (Ubuntu Bionic) "SRU cloud-init 18.2-27-g6ef92c98-0ubuntu1" [Medium,Fix committed] + + 16:23 `` which grabs a number of the updates I listed in the last topic + + 16:23 `` since Ubuntu tends to sync all changes from tip into each release stream + + 16:23 `` Is there any chance the SmartOS changes can piggy back on that IBM SRU + + 16:24 `` asked too soon - I see they are mentioned in that bug. + + 16:25 `` mgerdts: no worries. good ask. probably not for this IBM SRU into xenial/artful which is going to be an exception to our update rule and only be a single cherry pick, but planning a folllowup SRU in about 2 weeks which will pull all changes from tip into artful/xenial/bionic/chunky releases + + 16:25 `` ok + + 16:25 `` the cherry pick is to fasttrack it for IBM into xenial with minimal risk. + + 16:25 `` and we want to pull in all your changes if we can (and perform additional validation) + + 16:25 `` so the next SRU is our target + + 16:26 `` Also inprogress is some more Azure work on pre-provisioning that should land shortly: + + 16:26 `` \#link [https://code.launchpad.net/~jocha/cloud-init/+git/cloud-init/+merge/344192](https://code.launchpad.net/~jocha/cloud-init/+git/cloud-init/+merge/344192) + + 16:27 `` as well as some builddeb fixes and network configuration printout fixes from smoser + + 16:29 `` smoser and rharper also worked out some issues on specific google regions where cloud-init was getting hit by a race condition. Cloud-init started up before the kernel/udev was able to rename network devices to stable names like ens4 etc, so cloud-init's network configuration written ended up breaking because it represented devices like eth0 etc. + + 16:29 `` there are a couple of branches in flight to fix this issue: + + 16:29 `` \#link [https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/344181](https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/344181) + + 16:30 `` \#link [https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/344198](https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/344198) + + 16:30 `` ok I think that's it for in-progress work. So we'll head to office hours so we can chat bugs, branches reviews etc + + 16:31 `` \#topic Office Hours (next ~30 mins) + + 16:31 `` We'll be hanging out here for anyone who wants more eyes on a review, feature discussions or bug triage.... + + 16:32 `` well, some of us will be :) a couple of us are at a feature planning conference for the week. + + 16:33 `` In [https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712](https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712) smoser said that he was concerned about how this would interact with eventual network hotplug + + 16:34 `` There doesn't seem to be a timeline for network hotplug and the lack of network autoreconfig on reboot is has popped up a couple times in the past week. This is just with a couple early adopters and internal users. + + 16:34 `` \#link [https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712](https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712) + + 16:35 `` just to track it in the meeting + + 16:35 `` So coming up with some mechanism to make this work soon is pretty important to us. + + 16:35 `` gotcha, will be sure to do that in the future. + + 16:35 * blackboxsw reads up on that link + + 16:35 `` no worries, I'm pedantic :) + + 16:36 `` That's how you got chosen to run the meeting, I suppose. :) + + 16:36 `` yeah network hotplug will have a long tail as far as feature develpment (agreed). I believe it's on our charter for this next quarter. but that's what is being discussed this week + + 16:37 `` heh on meeting comment ;) too true + + 16:39 `` so mgerdts your branch allows metadata to set maintain_network to allow cloud-init to control network configuration each reboot with a True value + + 16:39 `` ? + + 16:39 `` yes + + 16:39 `` if it's not set to true in our metadata, the traditional behavior stays. + + 16:40 `` That is, in the default path, any customization that someone does in the guest will not get whacked. + + 16:41 `` cloud-netconfig handles hotplug [https://github.com/SUSE/Enceladus/tree/master/cloud-netconfig](https://github.com/SUSE/Enceladus/tree/master/cloud-netconfig) contributions for other distros welcome + + 16:42 `` nice reference robjo + + 16:42 `` \#link [https://github.com/SUSE/Enceladus/tree/master/cloud-netconfig](https://github.com/SUSE/Enceladus/tree/master/cloud-netconfig) + + 16:43 `` We currently have no GCE specific information but that is easy enough to add. The GCE guest environment handles this and we use the GCE guest environment code in our images in GCE + + 16:43 `` mgerdts: so can a user turn off that feature on an instance once they've already deployed, or is it create-time only + + 16:43 `` It can be flipped at any time, in the current implementation. + + 16:44 `` current implementation is only in a development branch + + 16:47 `` mgerdts: the only things I can see being an issue with the maintain network in cloud-init is that we are adding the cost of another function call && metdata dict parse to look for a signal about maintaining the network. I agree that cloud-init having granularity between is_new_instance vs just re-do network, is something that cloud-init should have. + + 16:48 `` we probably need to discuss this too with rharper about what short-term vision we can get to while we await our network hotplug support in cloud-init proper + + 16:49 `` I'd tend to agree that waiting on fully baked hotplug solution is probably too long in this case + + 16:49 `` as that runway will be at least 2 months I'd think + + 16:50 `` ok, I'll take an action item to resolve this if we can by next meeting + + 16:50 `` Not only that, but support for it will likely require changes in the host as well. We tend not to do host updates very often, so it could be a year or more after the feature is available in images before it will be useful. + + 16:51 `` \#action blackboxsw to have discussions w/ team on datasource maintaining network on each reboot per [https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712](https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712) + + 16:51 * meetingology blackboxsw to have discussions w/ team on datasource maintaining network on each reboot per [https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712](https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712) + + 16:51 `` thanks + + 16:51 `` good topic. + + 16:52 `` Is there another place that is good to catch up with larsks or other people that can offer guidance on for redhat/centos? + + 16:52 `` let's see, anything else folks want to chat about? stagnant reviews, bugs of interest etc? + + 16:53 * blackboxsw looks at the last cloud-init community summit attendees list to see if rhel folks have another contacts that was supposed to replace larsks + + 16:53 `` Chad, Is it possible that someone from cloud-init team can take a look at [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538) + + 16:53 `` Launchpad bug 1766538 in cloud-init (Ubuntu) "network customization with cloud-init does not work on Ubuntu18.04 Beta2 Server" [Undecided,Confirmed] + + 16:55 `` mgerts, ryan mccabe is a potential contact too, looks like he's not here either today. + + 16:56 `` ok, thanks + + 16:56 `` hrm, yeah not certain what mechanism is used to get cloud-init updated into RedHat mgerdts. Maybe filing a redhat bug about the request + + 16:57 `` mgerdts: [https://bugzilla.redhat.com/](https://bugzilla.redhat.com/) maybe + + 16:58 `` stanguturi: yes we can, we are trying to sort and understand any bugs against Bionic that we can + + 16:58 `` ok, I can try that. + + 16:58 `` \#link [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538) + + 16:58 `` Launchpad bug 1766538 in cloud-init (Ubuntu) "network customization with cloud-init does not work on Ubuntu18.04 Beta2 Server" [Undecided,Confirmed] + + 16:58 `` blackboxsw: Thanks + + 17:00 `` stanguturi: ok, so this is netplan + cloud-init related right? + + 17:00 `` blackboxsw: Yes. + + 17:01 `` what does network hotplug mean in cloud-init context? + + 17:02 * blackboxsw tries to remember what vmware datasource does, (like writing files direct to network /etc/network/interfaces.d) + + 17:02 `` akik: [https://hackmd.io/M1Tae41PQBC7a9qMsurTJw](https://hackmd.io/M1Tae41PQBC7a9qMsurTJw)?both is a shared document for comment on hotplug in cloud-init + + 17:02 `` \#link [https://hackmd.io/M1Tae41PQBC7a9qMsurTJw](https://hackmd.io/M1Tae41PQBC7a9qMsurTJw)?both + + 17:03 * blackboxsw looks to see if there was a better doc hrm + + 17:03 `` blackboxsw: Oh. But in the case of netplan, why does cloud-init remembers? + + 17:04 `` blackboxsw: does it mean that cloud-init stays running, waiting for new network interfaces to appear? + + 17:04 `` akik: right, it would mean that you wouldn't have to reboot cloud-init if devices get added at a later time (post-boot) + + 17:05 `` cloud-init would listen to some sort of event channel and react, re-write, and apply network config to add new devices + + 17:06 `` would it do the same thing as you could do with ansible or puppet? sorry i'm trying to understand why you would do it with cloud-init + + 17:08 `` akik: you would try to do it with cloud-init if you didn't want to rely on additional configuration management solutions if the only thing you needed was network config to reflect reality (not full system configuration and system automation) + + 17:09 * blackboxsw has more puppet/chef background than ansible. + + 17:09 `` cloud-init does currently detect and write network configuration based on what the user/cloud-metadata tell us is the proper config for the instance + + 17:10 `` i only thought of cloud-init to do the initial configuration + + 17:10 `` so it would follow that if the metadata could dynamically tell the instance that network config has changed, cloud-init should probably try to react to that to fix the config to match the updated network configuration + + 17:11 `` akik: correct. cloud-init current only handle initial boot config and leaves the rest up whatever mechanism someone uses to update detailed config after that boot + + 17:11 `` ok thanks + + 17:12 `` akik: and we'd make that feature configurable (handle hotplug:True/False) so if users have other services handling hotplug cloud-init wouldn't collide + + 17:13 `` ok I think we're hitting the end of office hours. please feel free to continue discussion, we all poke around here throughout the day as our primary means of communication + + 17:13 `` thanks robjo akik stanguturi and mgerdts for the lively discussion + + 17:13 `` stanguturi: I'll dig up more info on that bug today + + 17:13 `` thank you + + 17:13 `` as always notes will be here + + 17:14 `` \#link [https://cloud-init.github.io/](https://cloud-init.github.io/) + + 17:14 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2018-05-14.md b/content/status-2018-05-14.md new file mode 100644 index 0000000..2240da7 --- /dev/null +++ b/content/status-2018-05-14.md @@ -0,0 +1,293 @@ +Title: Cloud-init bi-weekly status +Date: 2018-05-14 16:05:00 UTC +Category: status-meeting-minutes +Slug: status-2018-05-14 + +Meeting information +---------------- + * \#cloud-init: Cloud-init bi-weekly status meeting, 14 May at 16:05 — 17:03 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-05-14-16.05.log.html](http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-05-14-16.05.log.html)]] + + + +Meeting summary +---------------- + +### Recent Changes +The discussion about "Recent Changes" started at 16:09. + + * **LINK**: [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + +### In-progress Development +The discussion about "In-progress Development" started at 16:19. + + +### Office Hours (next ~30 mins) +The discussion about "Office Hours (next ~30 mins)" started at 16:29. + + * **LINK**: [https://pastebin.ubuntu.com/p/266CyDt9gD/](https://pastebin.ubuntu.com/p/266CyDt9gD/) + * **LINK**: [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538) + * **LINK**: [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/emptyStageOK](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/emptyStageOK) + * **LINK**: [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/noLnxDistro](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/noLnxDistro) + * **LINK**: [https://bugs.launchpad.net/cloud-init/+bug/1745235](https://bugs.launchpad.net/cloud-init/+bug/1745235) + * **ACTION**: blackboxsw review distro dection and empty modules list + * **ACTION**: robjo review existing chrony support in master per rharper's work + * **ACTION**: blackboxsw carryover network hotplug vs network maintenance on reboot-only + + + +Vote results +---------------- + + + + +Action items, by person +---------------- + + * blackboxsw + * blackboxsw review distro dection and empty modules list + * blackboxsw carryover network hotplug vs network maintenance on reboot-only + * rharper + * robjo review existing chrony support in master per rharper's work + * robjo + * robjo review existing chrony support in master per rharper's work + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (73) + * robjo (14) + * ubot5 (9) + * meetingology (6) + * stanguturi (2) + * rharper (1) + + + +Full Log +---------------- + + + 16:05 `` \#startmeeting Cloud-init bi-weekly status meeting + + 16:05 `` Meeting started Mon May 14 16:05:28 2018 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:05 `` + + 16:05 `` Available commands: action commands idea info link nick + + 16:08 `` welcome folks to another cloud-init status meeting. This forum is used to communicate the recent changes, current development efforts and host open office hours to help get quick discussion on bugs, branches or features of interest to anyone developing (or consuming) cloud-init. + + 16:09 `` We'll go through a couple of topics as usual (Recent changes, In-progress Development, Office Hours), if there are any additional topics needed just let me know. + + 16:09 `` \#topic Recent Changes + + 16:10 `` We track our upstream work publicly on trello. Feel free to participate or ask questions about any feature work that is seen up there if there are concerns. + + 16:11 `` \#link [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + + 16:11 `` We have landed the following work items: beware the paste :) + + 16:11 `` * Completed release of 18.2 to Ubuntu Bionic, Artful, and Xenial + + 16:11 `` * Implement bash completion script for cloud-init command line + + 16:11 `` * Improved Softlayer datasource documentation + + 16:11 `` * net: Depend on iproute2's ip instead of net-tools ifconfig or route + + 16:11 `` * Accept-ra unset by default (LP: \#1732002) + + 16:11 `` * Command collect-logs will only include most recent boot's journal (LP: \#1766335) + + 16:11 `` * FreeBSD: Invoke growfs on ufs filesystems such that it does not prompt. (LP: \#1404745) + + 16:11 `` Launchpad bug 1732002 in systemd (Ubuntu) "cloud images in lxc get ipv6 address" [Undecided,New] [https://launchpad.net/bugs/1732002](https://launchpad.net/bugs/1732002) + + 16:11 `` * Azure: poll_imds fixes to only report 'ready' state once during pre-provisioning from Joshua Chan (LP: \#1765214) + + 16:11 `` * DataSourceSmartOS: fix hang when metadata service is down from Mike Gerdts (LP: \#1667735) + + 16:12 `` Launchpad bug 1766335 in cloud-init "Running cloud-init collect-logs inside a chroot is not possible" [Medium,Fix committed] [https://launchpad.net/bugs/1766335](https://launchpad.net/bugs/1766335) + + 16:12 `` * DataSourceSmartOS: change default fs on ephemeral disk from ext3 to ext4 from Mike Gerdts (LP: \#1763511) + + 16:12 `` * pycodestyle: Fix invalid escape sequences in string literals + + 16:12 `` Launchpad bug 1404745 in cloud-init "cloud-init's growfs/resize fails with gpart dependency on FreeBSD" [Undecided,Fix committed] [https://launchpad.net/bugs/1404745](https://launchpad.net/bugs/1404745) + + 16:12 `` Launchpad bug 1765214 in cloud-init "Multiple success messages sent to Azure Fabric if reboot occurs during pre-provisioning" [Medium,Fix committed] [https://launchpad.net/bugs/1765214](https://launchpad.net/bugs/1765214) + + 16:12 `` Launchpad bug 1667735 in cloud-init (Ubuntu Trusty) "cloud-init doesn't retry metadata lookups and hangs forever if metadata is down" [Medium,Confirmed] [https://launchpad.net/bugs/1667735](https://launchpad.net/bugs/1667735) + + 16:12 `` Launchpad bug 1763511 in cloud-init (Ubuntu) "DataSourceSmartOS should default to ext4" [Medium,Fix released] [https://launchpad.net/bugs/1763511](https://launchpad.net/bugs/1763511) + + 16:14 `` A big thank you to community involvement again. Thanks jocha(Microsoft) and mgerdts(Joyent) for the recent branch work supporting Azure and SmartOS clouds respectively + + 16:16 `` We also went through another round of StableReleaseUpdates for Ubuntu on Xenial and Artful to pull in IBMCloud platform fixes. putting Xenial and artful at 18.2-4-g05926e48-0ubuntu~16.04.2 | ~17.10.2 + + 16:18 `` I think that's about it for completed development... + + 16:19 `` \#topic In-progress Development + + 16:21 `` There are a couple of items being worked actively at the moment: + + 16:22 `` * SRU of cloud-init tip into bionic (should land today or tomorrow) 18.2-27-g6ef92c98-0ubuntu1~18.04.1 + + 16:23 `` * SmartOs datasource detection improvements + + 16:23 `` * Moving OpenStack datasource to get detected earlier at 'local' stange instead of 'network' stage using ephemeral dhcp client + + 16:26 `` * read_file_or_url fixes returing text content in all cases + + 16:26 `` * various upstream bug fixes + + 16:27 `` * powersj: is also investigating a move to a centralized library for our cloud testing. + + 16:29 `` blackboxsw: w.r.t. Depend on iproute2's ip instead of net-tools ifconfig or route was this a merge of iproute2tools branch? I don't recall seeing a merge notification but am way behind in e-mail + + 16:29 `` think that about captures what upstream is working on. I think we can transition to office hours for ~30 mins for anyone to bring up ideas of interest + + 16:29 `` \#topic Office Hours (next ~30 mins) + + 16:29 `` hi robjo, checking status there + + 16:30 `` I know we landed one branch on that topic + + 16:31 `` robjo: so we had a couple branches to packaging dependencies in ubuntu to call out iproute2 specifically as a hard package dependency. + + 16:32 `` robjo: and the code changes (which took in some of your branch content and review comments) landed in rev 6d48d265a0548a2dc23e587f2a335d4e38e8db90 + + 16:32 `` OK, so I can delete my branch + + 16:32 `` [https://pastebin.ubuntu.com/p/266CyDt9gD/](https://pastebin.ubuntu.com/p/266CyDt9gD/) + + 16:34 `` thanks, so we'll get that in 18.3? + + 16:34 `` robjo: yes I think i marked you co-author on that branch and pulled in all your changes to cloudinit/config/cc_disable_ec2_metadata.py + + 16:34 `` 2 + + 16:34 `` thanks again for that, sorry for the back and forth as I hadn't seen your original branch. + + 16:35 `` robjo: definitely in 18.3 + + 16:35 `` it landed a week or two after the 18.2 cut. + + 16:35 `` @blackboxsw, Can someone please provide inputs for the bug [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538) One of our team members has uploaded the necessary log files to the bug. + + 16:35 `` Ubuntu bug 1766538 in cloud-init (Ubuntu) "network customization with cloud-init does not work on Ubuntu18.04 Beta2 Server" [Undecided,New] + + 16:38 `` OK, so lets also revisit some of the other stuff I have floating about as I just did the 18.2 package for openSUSE and SLES and noticed that I am once again scarring a lot of patches :( + + 16:39 `` blackboxsw: [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/emptyStageOK](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/emptyStageOK) should be back in your court, did you get notification? + + 16:40 `` blackboxsw: [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/noLnxDistro](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/noLnxDistro) pending since January this may have some merge conflicts now as I had to fiddle quite a bit with the patch in my package + + 16:41 `` stanguturi: looking + + 16:41 `` I think rharper is working on a different approach to [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/chrony](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/chrony) when can we expect that? + + 16:42 `` and does rharper account for the fact that ntp has a different service name on different distributions? + + 16:43 `` \#link [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538) + + 16:43 `` Ubuntu bug 1766538 in cloud-init (Ubuntu) "network customization with cloud-init does not work on Ubuntu18.04 Beta2 Server" [Undecided,New] + + 16:43 `` \#link [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/emptyStageOK](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/emptyStageOK) + + 16:43 `` ahh robjo hadn't, was on vacation Friday, will grab that/close out today + + 16:43 `` \#link [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/noLnxDistro](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/noLnxDistro) + + 16:44 `` robjo: re: ntp/chrony, that's landed, including service names for different distros; I pulled unittests and scenarios from your branch; please look over master and see if we're missing anything from your branch w.r.t use-case/scenario + + 16:45 `` rharper: OK, if it's landed I can at least throw my branch away, and yes, will take a look at master, I take it this will be another in 18.3 item? + + 16:46 `` stanguturi: ok thanks for the logs on that bug, looks like network config parsing is falling over and OVF datasource isn't being detected [https://pastebin.ubuntu.com/p/qVJxDJWZRV/](https://pastebin.ubuntu.com/p/qVJxDJWZRV/) + + 16:47 `` @blackboxsw, Oh . Thanks. Will check with him about the test setup and update the bug. Thanks. + + 16:48 `` updated the bug with a comment there + + 16:48 `` thanks stanguturi + + 16:50 `` robjo: correct as well for ntp/chrony, we held off landing it in 18.2 because of risk + + 16:50 `` it was one of the first branches landed after the cut + + 16:51 `` ok, leaves the [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/noLnxDistro](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/noLnxDistro) implementation of distro detection as things I'd like to get resolved, others to be addressed maybe in 2 weeks ;) + + 16:51 `` ok noLnxDistro.... I'm updating the commit comment robjo to the trailing LP: \#`` + + 16:51 `` claiming a review slot on that now + + 16:53 `` good unit test coverage, thanks for that + + 16:54 `` np + + 16:55 `` ok this can be reviewed today, not sure if why we don't already have a get_linux_distro utility somewhere, but I'll poke around today for context + + 16:55 `` ahh ahh, thanks for the bug robjo ok + + 16:56 `` the context is that the Python implementation is going away and has been deprecated + + 16:56 `` \#link [https://bugs.launchpad.net/cloud-init/+bug/1745235](https://bugs.launchpad.net/cloud-init/+bug/1745235) + + 16:56 `` Ubuntu bug 1745235 in cloud-init "distribution detection" [Undecided,New] + + 16:56 `` thanks again + + 16:56 `` changing that status and will help you get that landed + + 16:56 `` good one + + 16:58 `` OK, blackboxsw is on the hook for two things this week ;) distro detection and the empty modules list + + 16:58 `` \#action blackboxsw review distro dection and empty modules list + + 16:58 * meetingology blackboxsw review distro dection and empty modules list + + 16:58 * robjo on the hook to look at chrony support in master and report back to rharper + + 16:58 `` \#action robjo review existing chrony support in master per rharper's work + + 16:58 * meetingology robjo review existing chrony support in master per rharper's work + + 16:59 `` official now :) + + 16:59 `` now if I only reviewed previous meeting's action items.... checking now + + 17:00 `` 16:51 `` \#action blackboxsw to have discussions w/ team on datasource maintaining network on each reboot per [https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712](https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712) + + 17:01 `` ok per last meeting, we have held a couple of discussions on hotplug vs. maintaining network only on reboot. on first blush it looks like we'd need to have these mutually exclusive, but we are just started to iron our what we want to do for our initial hotplug support in cloud-init and have to have a followup discussion about how to support both approaches + + 17:02 `` \#action blackboxsw carryover network hotplug vs network maintenance on reboot-only + + 17:02 * meetingology blackboxsw carryover network hotplug vs network maintenance on reboot-only + + 17:02 `` well that was the only action item from last meeting looks like + + 17:02 `` ok I think that wraps up today's meeting. + + 17:02 `` any other parting shots folks? + + 17:03 `` Thanks again for your time. It's always a pleasure. + + 17:03 `` Next meeting two weeks, same bat time... + + 17:03 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2018-06-18.md b/content/status-2018-06-18.md new file mode 100644 index 0000000..3847552 --- /dev/null +++ b/content/status-2018-06-18.md @@ -0,0 +1,343 @@ +Title: Cloud-init bi-weekly status +Date: 2018-06-18 16:08:00 UTC +Category: status-meeting-minutes +Slug: status-2018-06-18 + +Meeting information +---------------- + * \#cloud-init: Cloud-init bi-weekly status meeting, 18 Jun at 16:08 — 17:23 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-06-18-16.08.log.html](http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-06-18-16.08.log.html)]] + + + +Meeting summary +---------------- + +### Previous Actions +The discussion about "Previous Actions" started at 16:11. + + * **LINK**: [https://cloud-init.github.io/status-2018-05-29.html\#status-2018-05-29](https://cloud-init.github.io/status-2018-05-29.html\#status-2018-05-29) + * **ACTION**: blackboxsw review distro dection and empty modules list [ DONE ] both robjo's branches are landed as of friday of last week. + * **ACTION**: blackboxsw carryover network hotplug vs network maintenance on reboot-only + * **LINK**: [https://hackmd.io/NUUO4nndS4CXTItl8Rs6Nw](https://hackmd.io/NUUO4nndS4CXTItl8Rs6Nw) + * **LINK**: expectation is to get the foundation landed this week + * **LINK**: [https://trello.com/c/Yp6VG2lP/837-eventpolicy-foundation-for-joyent-and-azure-coldplug](https://trello.com/c/Yp6VG2lP/837-eventpolicy-foundation-for-joyent-and-azure-coldplug) + * **LINK**: [https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+ref/feature/maintain-network-on-boot](https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+ref/feature/maintain-network-on-boot) + * **LINK**: [https://hackmd.io/aODzXfa_TOikNtYBLt8erA](https://hackmd.io/aODzXfa_TOikNtYBLt8erA) + * **LINK**: [https://hackmd.io/aODzXfa_TOikNtYBLt8erA](https://hackmd.io/aODzXfa_TOikNtYBLt8erA) + +### Recent Changes +The discussion about "Recent Changes" started at 16:27. + + * **LINK**: [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + +### Cloud-init 18.3 release +The discussion about "Cloud-init 18.3 release" started at 16:36. + + +### Office Hours (next ~30 mins) +The discussion about "Office Hours (next ~30 mins)" started at 16:46. + + * **ACTION**: rhaper/blackboxsw review [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904) + * **LINK**: [https://cloud-init.github.io/](https://cloud-init.github.io/) + + + +Vote results +---------------- + + + + +Action items, by person +---------------- + + * blackboxsw + * blackboxsw review distro dection and empty modules list [ DONE ] both robjo's branches are landed as of friday of last week. + * blackboxsw carryover network hotplug vs network maintenance on reboot-only + * rhaper/blackboxsw review [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904) + * robjo + * blackboxsw review distro dection and empty modules list [ DONE ] both robjo's branches are landed as of friday of last week. + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (83) + * robjo (14) + * rharper (10) + * ubot5 (7) + * smoser (7) + * meetingology (6) + + + +Full Log +---------------- + + + 16:08 `` \#startmeeting Cloud-init bi-weekly status meeting + + 16:08 `` Meeting started Mon Jun 18 16:08:07 2018 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:08 `` + + 16:08 `` Available commands: action commands idea info link nick + + 16:09 `` Hi folks and welcome. We've got a big week this week as we are planning on a cloud-init release. So we will have an additional topic in today's agenda + + 16:09 `` o/ + + 16:10 `` it's been a few weeks, due to holiday schedules/travel, our agenda will be as following: Previous Actions, Recent Changes, In-progress develepment, cloud-init release 18.3 and office hours + + 16:11 `` \#topic Previous Actions + + 16:11 `` last action items are listed in our meeting minutes at the following url: + + 16:11 `` \#link [https://cloud-init.github.io/status-2018-05-29.html\#status-2018-05-29](https://cloud-init.github.io/status-2018-05-29.html\#status-2018-05-29) + + 16:12 `` \#ACTION blackboxsw review distro dection and empty modules list [ DONE ] both robjo's branches are landed as of friday of last week. + + 16:12 * meetingology blackboxsw review distro dection and empty modules list [ DONE ] both robjo's branches are landed as of friday of last week. + + 16:13 `` that was a carryover from the meeting before I believe. + + 16:13 `` \#ACTION blackboxsw carryover network hotplug vs network maintenance on reboot-only + + 16:13 * meetingology blackboxsw carryover network hotplug vs network maintenance on reboot-only + + 16:14 `` I think this was the only other unresolved action. Our team has had mutliple followup discussions internally and with mgerts from Joyent/SmartOs as well + + 16:14 `` smoser: and rharper drew up a hackmd doc related to this work here: + + 16:14 `` \#link [https://hackmd.io/NUUO4nndS4CXTItl8Rs6Nw](https://hackmd.io/NUUO4nndS4CXTItl8Rs6Nw) + + 16:15 `` We've come to a conclusion on a common near-term approach that will support cold-plug scenarios by allowing datasources to claim whether or not they will re-render networking on a boot event. This would allow cloud-init to react to network metadata changes across boot and enable/disable those devices accordingly + + 16:16 `` a WIP branch is available here + + 16:16 `` \#link expectation is to get the foundation landed this week + + 16:16 `` and tracked in trello here + + 16:16 `` \#link [https://trello.com/c/Yp6VG2lP/837-eventpolicy-foundation-for-joyent-and-azure-coldplug](https://trello.com/c/Yp6VG2lP/837-eventpolicy-foundation-for-joyent-and-azure-coldplug) + + 16:17 `` Note that the metdata ins EC2 is "stale", AFIK, or at least some parts of the data are stale, i.e. they only get refreshed on instance restart + + 16:17 `` is it instance restart or "re DHCP" ? + + 16:17 `` ie, bounce the interface ? + + 16:17 `` \#link [https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+ref/feature/maintain-network-on-boot](https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+ref/feature/maintain-network-on-boot) + + 16:18 `` robjo: that is correct. + + 16:18 `` so a re-read of the metadata on EC2 delivers no/maybe limited new information + + 16:18 `` robjo: well, network information is updated. + + 16:18 `` user-data is only updatable on stop ->` start in ec2 + + 16:18 `` rharper: AFAIK new metadat gets pick up on instance restart + + 16:19 `` ok + + 16:19 `` I know the IID also only gets updated on stop-start + + 16:19 `` certainly in Azure that's the case. you have to stop the instance before changing attached network interfaces and then bring instance online again + + 16:20 `` Yes, in Azure adding network interfaces is not dynamic + + 16:20 `` meaning cannot happen while an instance is running + + 16:21 `` adding IPs in azure is an online thing, but even azure's network metadata is limited in that it doesn't tell you whether a network interface is static or dynamic. examples here: + + 16:21 `` [https://hackmd.io/aODzXfa_TOikNtYBLt8erA](https://hackmd.io/aODzXfa_TOikNtYBLt8erA) + + 16:21 `` \#link [https://hackmd.io/aODzXfa_TOikNtYBLt8erA](https://hackmd.io/aODzXfa_TOikNtYBLt8erA) + + 16:22 `` Also for Azure there exists the "problem" of accelerated networking, i.e. SR-IOV + + 16:23 `` when accelerated networking is on the SR-IOV interface gets the same MAC address as the "Synthetic nic" + + 16:23 `` well, they "solved" it by having the kernel auto bond =/ + + 16:23 `` the SR-IOV interface gets bound to the synthetic nic in the kernel, that was a patch that went into the kernel 6-9 months ago + + 16:23 `` AFAICT, the sriov device just magically comes and goes as it will + + 16:24 `` so, one shouldn't worry about the silent bonding ... (I'm being a bit sarcastic here) + + 16:24 `` yes, but the interface still shows up, so if output from "ip" command is read one has two devices with the same MAC address, only one of which should be configured + + 16:25 `` we ignore any of the mlx4 driver devices + + 16:25 `` yes they show up + + 16:25 `` OK + + 16:25 `` but the directive we got was to ignore them; and DHCP on the netvsc ones + + 16:25 `` ...so think that's all I had on action items from previous meeting. + + 16:26 `` shall we go to next topic? + + 16:26 `` And that of course works until Msft gets a better HW deal from Intel or someone else for their network cards ;) + + 16:26 `` heh + + 16:26 `` robjo: indeed + + 16:27 `` \#topic Recent Changes + + 16:27 `` due to a couple vacations and some work travel it's been a slightly slower couple weeks below are the cloud-init changes that have gone in: + + 16:28 `` - lxd: Delete default network and detach device if lxd-init created them. + + 16:28 `` (LP: \#1776958) + + 16:28 `` - openstack: avoid unneeded metadata probe on non-openstack platforms + + 16:28 `` [Chad Smith] (LP: \#1776701) + + 16:28 `` - stages: fix tracebacks if a module stage is undefined or empty + + 16:28 `` [Robert Schweikert] (LP: \#1770462) + + 16:28 `` - Be more safe on string/bytes when writing multipart user-data to disk. + + 16:28 `` Launchpad bug 1776958 in cloud-init "error creating lxdbr0." [Medium,Fix committed] [https://launchpad.net/bugs/1776958](https://launchpad.net/bugs/1776958) + + 16:28 `` (LP: \#1768600) + + 16:28 `` - Fix get_proc_env for pids that have non-utf8 content in environment. + + 16:28 `` Launchpad bug 1776701 in cloud-init "ec2: xenial unnecessary openstack datasource probes during discovery" [High,Fix committed] [https://launchpad.net/bugs/1776701](https://launchpad.net/bugs/1776701) + + 16:28 `` (LP: \#1775371) + + 16:28 `` - tests: fix salt_minion integration test on bionic and later [Chad Smith] + + 16:28 `` - tests: provide human-readable integration test summary when --verbose + + 16:28 `` [Chad Smith] + + 16:28 `` Launchpad bug 1770462 in cloud-init "Allow empty stages" [Low,Fix committed] [https://launchpad.net/bugs/1770462](https://launchpad.net/bugs/1770462) + + 16:28 `` - tests: skip chrony integration tests on lxd running artful or older + + 16:28 `` [Chad Smith] + + 16:28 `` Launchpad bug 1768600 in cloud-init "UTF-8 support in User Data (text/x-shellscript) is broken" [Medium,Fix committed] [https://launchpad.net/bugs/1768600](https://launchpad.net/bugs/1768600) + + 16:28 `` - test: add optional --preserve-instance arg to integraiton tests + + 16:28 `` [Chad Smith] + + 16:28 `` Launchpad bug 1775371 in cloud-init "cloud-init (18.2) fails on decoding proc1 env" [Medium,Fix committed] [https://launchpad.net/bugs/1775371](https://launchpad.net/bugs/1775371) + + 16:28 `` - netplan: fix mtu if provided by network config for all rendered types + + 16:28 `` [Chad Smith] (LP: \#1774666) + + 16:28 `` Launchpad bug 1774666 in netplan.io (Ubuntu Cosmic) "Bond interfaces stuck at 1500 MTU on Bionic" [Undecided,Confirmed] [https://launchpad.net/bugs/1774666](https://launchpad.net/bugs/1774666) + + 16:28 `` - tests: remove pip install workarounds for pylxd, take upstream fix. + + 16:28 `` - subp: support combine_capture argument. + + 16:28 `` - tests: ordered tox dependencies for pylxd install [Chad Smith] + + 16:28 `` - util: add get_linux_distro function to replace platform.dist + + 16:28 `` [Robert Schweikert] (LP: \#1745235) + + 16:28 `` - pyflakes: fix unused variable references identified by pyflakes 2.0.0. + + 16:28 `` Launchpad bug 1745235 in cloud-init "distribution detection" [Medium,Fix committed] [https://launchpad.net/bugs/1745235](https://launchpad.net/bugs/1745235) + + 16:28 `` thanks again Robert for the contributions here getting cloud-init in order :) + + 16:30 `` we've also just pushed a release of cloud-init tip into Ubuntu Cosmic. + + 16:30 `` so all latest changes are in the development series + + 16:32 `` I think that about wraps it + + 16:32 `` \#topc In-progress Development + + 16:32 `` As always, we track ongoing work publicly at + + 16:32 `` \#link [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + + 16:33 `` we've got some cold-plug network rendering handling that will be queued for this week, mgerts is working on enabling cold-plug network rendering support on boot for SmartOS, and there is a followup for Azure to do the same + + 16:34 `` cloud-init squad is going to be setting up an SRU into Xenial, Artful and Bionic this week as well + + 16:34 `` to sync latest qualified cloud-init into those Ubuntu series + + 16:35 `` blackboxsw: thinking out loud.. + + 16:35 `` if we're going to release 18.3 on thursday + + 16:35 `` might as well just hold off on sru until then + + 16:35 `` (wait on 18.3 release?) + + 16:36 `` yeha + + 16:36 `` yeah even + + 16:36 `` which brings us to our next topic + + 16:36 `` \#topic Cloud-init 18.3 release + + 16:37 `` I hadn't seen any responsed to your email scott to cloud-init@lists.launchpad.net. Does anyone have any feature pressing that we'd like to get into this release + + 16:38 `` estimated release would be Thusday of this week + + 16:39 `` I'd whimsically like to include the azure cold-plug stuff, but that means getting those two branches in shape today for a thorough review/test cycle + + 16:39 `` s/whimsically/opportunitically/ + + 16:39 `` heh I give up + + 16:42 `` did we want to pull this in? [https://code.launchpad.net/~paul-meyer/cloud-init/+git/cloud-init/+merge/334989](https://code.launchpad.net/~paul-meyer/cloud-init/+git/cloud-init/+merge/334989) + + 16:45 `` If there are any pressing bugs or features that need to be in 18.3 we'd like to see them up for review by Wednesday of this week so that we can cut our upstream release. Feel free to send an email to the list cloud-init@lists.launchpad.net or this channel if your branch needs to get some eyes. + + 16:46 `` we'll SRU 18.3 then into Xenial, Artful and Bionic after a complete round of testing. + + 16:46 `` \#topic Office Hours (next ~30 mins) + + 16:46 `` :D After 18.3 but before the workshop: [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904) + + 16:47 `` Folks are around for further discussion on any cloud-init topics of interest + + 16:47 `` then maybe at the workshop we can come up with a way to move SLES & openSUSE to sysconfig renderer + + 16:48 `` good topic idea + + 16:48 `` \#ACTION rhaper/blackboxsw review [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904) + + 16:48 * meetingology rhaper/blackboxsw review [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904) + + 17:22 `` thanks again folks. catch you next time. + + 17:23 `` minutes will be published to the link below + + 17:23 `` \#link [https://cloud-init.github.io/](https://cloud-init.github.io/) + + 17:23 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2018-07-02.md b/content/status-2018-07-02.md new file mode 100644 index 0000000..a6027db --- /dev/null +++ b/content/status-2018-07-02.md @@ -0,0 +1,218 @@ +Title: Cloud-init bi-weekly status +Date: 2018-07-02 16:05:00 UTC +Category: status-meeting-minutes +Slug: status-2018-07-02 + +Meeting information +---------------- + * \#cloud-init: Cloud-init bi-weekly status meeting, 02 Jul at 16:05 — 17:02 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-07-02-16.05.log.html](http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-07-02-16.05.log.html)]] + + + +Meeting summary +---------------- + + **LINK**: [https://cloud-init.github.io/](https://cloud-init.github.io/) +### Previous Actions +The discussion about "Previous Actions" started at 16:09. + + * **LINK**: [https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348000](https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348000) + * **ACTION**: haper/blackboxsw review [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904) [CARRYOVER] + +### Recent Changes +The discussion about "Recent Changes" started at 16:15. + + * **LINK**: [https://lists.launchpad.net/cloud-init/msg00164.html](https://lists.launchpad.net/cloud-init/msg00164.html) + +### In-progress Development +The discussion about "In-progress Development" started at 16:21. + + * **LINK**: [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + * **LINK**: [https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/](https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/) + * **LINK**: [https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348704](https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348704) + +### Office Hours (next ~30 mins) +The discussion about "Office Hours (next ~30 mins)" started at 16:31. + + * **LINK**: [https://cloud-init.github.io/](https://cloud-init.github.io/) + + + +Vote results +---------------- + + + + +Action items, by person +---------------- + + * blackboxsw + * haper/blackboxsw review [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904) [CARRYOVER] + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (60) + * meetingology (4) + * ubot5 (3) + * danMS_ (1) + * mgerdts (1) + + + +Full Log +---------------- + + + 16:05 `` \#startmeeting Cloud-init bi-weekly status meeting + + 16:05 `` Meeting started Mon Jul 2 16:05:44 2018 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:05 `` + + 16:05 `` Available commands: action commands idea info link nick + + 16:06 `` hi folks, just kicking off another cloud-init status meeting to communicate the recent events in cloud-init land. + + 16:06 `` welcome to all, feel free to interrupt as we go through the agenda. As always cloud-init status minutes will live at the following url + + 16:07 `` \#link [https://cloud-init.github.io/](https://cloud-init.github.io/) + + 16:07 `` The meeting agenda is as follows: + + 16:08 `` agenda: Previous Actions, Recent Changes, In-progress develepment and office hours (~30 minutes) + + 16:09 `` \#topic Previous Actions + + 16:09 `` Last meeting we have a couple of actions to look over: + + 16:10 `` \#ACTION blackboxsw carryover network hotplug vs network maintenance on reboot-only + + 16:10 `` \#ACTION blackboxsw carryover network hotplug vs network maintenance on reboot-only [DONE] + + 16:11 `` we held multiple meetings, including discussion with mgerdts on a SmartOS solution for handling regenerating network configuration per-boot when a user selects this behavior + + 16:12 `` We have just landed a supporting branch in cloud-init tip to enable datasources to define what events (BOOT vs BOOT_NEW_INSTANCE) they will react to when generating network config. + + 16:12 `` \#link [https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348000](https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348000) + + 16:13 `` that should give a foundation for other datasources to write/change network config across boots, instead of allowing network config to remain static based on cloud-init's initial network configuration + + 16:13 `` the 2nd action .. + + 16:14 `` \#ACTION haper/blackboxsw review [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904) [CARRYOVER] + + 16:14 * meetingology haper/blackboxsw review [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904) [CARRYOVER] + + 16:14 `` I'd like to carry this one over. We got a bit bogged down in SRU, CentOs stuff last week and we shold be able to get some eyes on this branch + + 16:14 `` I think that's it for actions. + + 16:15 `` \#topic Recent Changes + + 16:16 `` Below is a list of changes landed in cloud-init tip or package publishing that has occured for the project: + + 16:16 `` * our 18.3 release was cut from tip if you caught the email on that mailing list + + 16:16 `` Congrats all for a great effort at improving quality and adding more datasource/cloud support + + 16:17 `` \#link [https://lists.launchpad.net/cloud-init/msg00164.html](https://lists.launchpad.net/cloud-init/msg00164.html) + + 16:17 `` ^ in case you didn't get the message + + 16:18 `` * we also publish 18.3 release into Ubuntu Cosmic and started a stable release update (SRU) to publish 18.3 in to xenial, artful, bionic + + 16:18 `` published* + + 16:19 `` expectations are that xenial, artful and bionic will have 18.3 after this week of testing + + 16:20 `` the remaining changes landed in tip are: + + 16:20 `` - update_metadata: a datasource can support network re-config every boot + + 16:20 `` [Chad Smith] + + 16:20 `` - tests: drop salt-minion integration test (LP: \#1778737) + + 16:20 `` - Retry on failed import of gpg receive keys. + + 16:20 `` - tools: Fix run-container when neither source or binary package requested. + + 16:20 `` - docs: Fix a small spelling error. [Oz N Tiram] + + 16:20 `` - tox: use simplestreams from git repository rather than bzr. + + 16:20 `` Launchpad bug 1778737 in cloud-init "salt-minion test needs fixing" [Undecided,Fix committed] [https://launchpad.net/bugs/1778737](https://launchpad.net/bugs/1778737) + + 16:20 `` - release 18.3 [Chad Smith] (LP: \#1777743) + + 16:20 `` - docs: represent sudo:false in docs for user_groups config module + + 16:20 `` [Chad Smith] + + 16:20 `` - Explicitly prevent `sudo` access for user module + + 16:20 `` Launchpad bug 1777743 in cloud-init "Release 18.3" [Undecided,Fix released] [https://launchpad.net/bugs/1777743](https://launchpad.net/bugs/1777743) + + 16:20 `` [Jacob Bednarz] (LP: \#1771468) + + 16:20 `` Launchpad bug 1771468 in cloud-init "Allow a way to explicitly disable sudo for a user" [Undecided,Fix released] [https://launchpad.net/bugs/1771468](https://launchpad.net/bugs/1771468) + + 16:21 `` next topic + + 16:21 `` \#topic In-progress Development + + 16:22 `` Our ongoing development is always listed publicly at the following trello board + + 16:22 `` \#link [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + + 16:23 `` We are going to be focused on SRU validation for Ubuntu this week which should take up the majority of the week. + + 16:23 `` At the end of this SRU process we will also rebuild centos binaries in our copr repo + + 16:23 `` \#link [https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/](https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/) + + 16:24 `` so that folks in other envs will have access to latest bits if their distro/cloud doesn't have that update + + 16:24 `` Also, specfic to mgerdts and danMS_ there is a branch in progress for Azure support to regenerate network-config for all interfaces on each boot. + + 16:25 `` \#link [https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348704](https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348704) + + 16:25 `` mgerdts: might like it only as another example of a datasource managing network config across boots + + 16:26 `` Thanks. Will look at that soon. + + 16:26 `` no prob, sorry for all the pings :) + + 16:26 `` will take a look too and spk to paulmey + + 16:27 `` also smoser is working on implementing an OCIC datasource (Oracle Cloud Infrastructure Classic) + + 16:31 `` think that wraps it up for this week. + + 16:31 `` \#topic Office Hours (next ~30 mins) + + 16:31 `` there should be a couple of eyes on this channel for discusssions, questions, bug requests etc that might need a bit more attention. + + 16:33 `` again, thanks for tuning in and helping make cloud-init better! + + 16:33 `` meeting minutes will ultimately show at + + 16:33 `` \#link [https://cloud-init.github.io/](https://cloud-init.github.io/) + + 17:02 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2018-08-06.md b/content/status-2018-08-06.md new file mode 100644 index 0000000..b0b7e0c --- /dev/null +++ b/content/status-2018-08-06.md @@ -0,0 +1,213 @@ +Title: Cloud-init bi-weekly status +Date: 2018-08-06 16:04:00 UTC +Category: status-meeting-minutes +Slug: status-2018-08-06 + +Meeting information +---------------- + * \#cloud-init: Cloud-init bi-weekly status meeting, 06 Aug at 16:04 — 17:04 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-08-06-16.04.log.html](http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-08-06-16.04.log.html)]] + + + +Meeting summary +---------------- + + **LINK**: [https://cloud-init.github.io/](https://cloud-init.github.io/) +### Previous Actions +The discussion about "Previous Actions" started at 16:09. + + * **ACTION**: rharper: and I need to review [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904) + +### Recent Changes +The discussion about "Recent Changes" started at 16:11. + + * **LINK**: [https://jenkins.ubuntu.com/server/job/admin-lp-git-autoland/](https://jenkins.ubuntu.com/server/job/admin-lp-git-autoland/) + +### In-progress Development +The discussion about "In-progress Development" started at 16:19. + + * **LINK**: [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + * **LINK**: [https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348704](https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348704) + +### Office Hource (next ~30 mins) +The discussion about "Office Hource (next ~30 mins)" started at 16:25. + + * **LINK**: [https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742.](https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742.) + * **LINK**: [https://cloud-init.github.io](https://cloud-init.github.io) for meeting minutes + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (59) + * powersj (6) + * meetingology (4) + * ubot5 (1) + * dpb1 (1) + + + +Full Log +---------------- + + + 16:04 `` \#startmeeting Cloud-init bi-weekly status meeting + + 16:04 `` Meeting started Mon Aug 6 16:04:05 2018 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:04 `` + + 16:04 `` Available commands: action commands idea info link nick + + 16:04 `` o/ + + 16:04 `` hi folks, let's kickoff another cloud-init status meeting. Welcome back. Lot's of summer vacations disrupting our typical meeting schedule. + + 16:05 `` Our last meeting's minutes should be up on our github site + + 16:05 `` \#link [https://cloud-init.github.io/](https://cloud-init.github.io/) + + 16:07 `` for this meeting we'll go through the following topics: previous actions, recent work, in-progress development and office hours + + 16:09 `` \#topic Previous Actions + + 16:09 `` from our last meeting we had a couple of actions to carry over + + 16:10 `` we 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/348000](https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348000) + + 16:10 `` \#action rharper: and I need to review [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904) + + 16:10 * meetingology rharper: and I need to review [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904) + + 16:10 `` the above is still a carryover + + 16:11 `` that's all for actions from last meeting + + 16:11 `` \#topic Recent Changes + + 16:12 `` the following has landed in cloud-init tip: + + 16:13 `` * oracle: fix detect_openstack to report True on OracleCloud.com DMI data (LP: \#1784685) + + 16:13 `` * tests: improve LXDInstance trying to workaround or catch bug.* + + 16:13 `` * update_metadata re-config on every boot comments and tests not quite right [Mike Gerdts] + + 16:13 `` * docs: note in rtd about avoiding /tmp when writing files + + 16:13 `` * ubuntu,centos,debian: get_linux_distro to align with platform.dist + + 16:13 `` * Fix boothook docs on environment variable name (INSTANCE_I ->` INSTANCE_ID) (Marc Tamsky) + + 16:13 `` * update_metadata: a datasource can support network re-config every boot + + 16:13 `` Launchpad bug 1784685 in cloud-init "Oracle: cloud-init openstack local detection too strict for oracle cloud" [High,Fix committed] [https://launchpad.net/bugs/1784685](https://launchpad.net/bugs/1784685) + + 16:13 `` * tests: drop salt-minion integration test + + 16:13 `` * Retry on failed import of gpg receive keys. + + 16:13 `` * tools: Fix run-container when neither source or binary package requested. + + 16:13 `` * docs: Fix a small spelling error (Oz N Tiram) + + 16:13 `` * tox: use simplestreams from git repository rather than bzr. + + 16:14 `` generally 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:15 `` notably, we discovered a potential regression in Oracle datasource detection of their OpenStack implementation so that fix is queued for publish into xenial and bionic + + 16:15 `` 18.3-9 is what folks are looking for. in xenial/bionic/cosmic for latest cloud-init containing all the above fixes + + 16:16 `` Also 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 acceptm + + 16:16 `` Also 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 `` \#link [https://jenkins.ubuntu.com/server/job/admin-lp-git-autoland/](https://jenkins.ubuntu.com/server/job/admin-lp-git-autoland/) + + 16:16 `` yep that is live and with a recent fix to remove the extra "Author" line now + + 16:16 `` hopefully it is saving blackboxsw, smoser, and rharper time ;) + + 16:17 `` powersj: can you explain what it does (so I don't have to type) + + 16:17 `` :) + + 16:17 `` If a merge request is put in the "Approved" state, it will get test merged with the master branch + + 16:17 `` the tests will run the same as during a review and verify that it can merge cleanly + + 16:18 `` the commit message will get linted to verify it fits our format + + 16:18 `` and if everything looks good, get merged in and pushed to master + + 16:18 `` thanks for that work powersj. it looks/works great so far. + + 16:19 `` \#topic In-progress Development + + 16:19 `` All our current work is visible at the following trello board + + 16:19 `` \#link [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + + 16:20 `` I expect we'll have a couple of branches landed shortly in the following areas: + + 16:21 `` - 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 `` - I + + 16:21 `` - I'm trying to wrap up a branch for Azure to write network data from their IMDS per-boot + + 16:22 `` \#link [https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348704](https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348704) + + 16:22 `` - Joyent (SmartOS) per-boot network config review + + 16:23 `` - a couple netplan config option bugs for bionic ++ + + 16:24 `` - and standardize instance-data sourcing in \#cloud-config files (like referencing the hostname as detected from instance metadata) + + 16:24 `` I think that probably wraps it up for stuff in progress + + 16:24 `` anything I'm missing? + + 16:25 `` ... without further ado + + 16:25 `` \#topic Office Hource (next ~30 mins) + + 16:26 `` eyes will float on this channel for any bug/feature discussions, review requests etc. any cloud-init topic is acceptable. + + 16:28 `` a 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:31 `` while I'm at it, I think I'll set the topic to next status meeting time so folks know it's coming. + + 16:39 `` also 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 `` \#link [https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742.](https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742.) + + 16:39 `` it looks a bit noisy on the debug front with adding out/err messages for all subp calls, but other than that fairly straight forward. + + 17:03 `` looks like that's a wrap for today. + + 17:03 `` \#link [https://cloud-init.github.io](https://cloud-init.github.io) for meeting minutes + + 17:04 `` see you next time: 2 weeks from today + + 17:04 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2018-08-20.md b/content/status-2018-08-20.md new file mode 100644 index 0000000..914c9f4 --- /dev/null +++ b/content/status-2018-08-20.md @@ -0,0 +1,180 @@ +Title: Cloud-init bi-weekly status +Date: 2018-08-20 16:09:00 UTC +Category: status-meeting-minutes +Slug: status-2018-08-20 + +Meeting information +---------------- + * \#cloud-init: Cloud-init bi-weekly status meeting, 20 Aug at 16:09 — 17:04 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-08-20-16.09.log.html](http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-08-20-16.09.log.html)]] + + + +Meeting summary +---------------- + +### Previous Actions +The discussion about "Previous Actions" started at 16:13. + + +### Recent Changes +The discussion about "Recent Changes" started at 16:13. + + +### In-progress Development +The discussion about "In-progress Development" started at 16:21. + + * **LINK**: [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + +### Office Hource (next ~30 mins) +The discussion about "Office Hource (next ~30 mins)" started at 16:27. + + * **LINK**: [https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742](https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742) + * **ACTION**: rharper/blackboxsw close out on this review before cloud-init summit [https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742](https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742) + + + +Vote results +---------------- + + + + +Action items, by person +---------------- + + * blackboxsw + * rharper/blackboxsw close out on this review before cloud-init summit [https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742](https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742) + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (39) + * ubot5 (5) + * paulmey (5) + * meetingology (4) + + + +Full Log +---------------- + + + 16:09 `` \#startmeeting Cloud-init bi-weekly status meeting + + 16:09 `` Meeting started Mon Aug 20 16:09:08 2018 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:09 `` + + 16:09 `` Available commands: action commands idea info link nick + + 16:09 `` For those around, let's kickoff another cloud-init status meeting. Feel free to interrupt as we go through the agenda for today. + + 16:10 `` agenda: Previous Actions, Recent Changes, In-progress development and office hours (~30 minutes) + + 16:13 `` \#topic Previous Actions + + 16:13 `` nothing to speak of here as far as I recall. + + 16:13 `` \#topic Recent Changes + + 16:14 `` We have recently landed the following content in tip of cloud-init over the last 2 weeks + + 16:14 `` - Add datasource Oracle Compute Infrastructure (OCI). + + 16:14 `` - azure: allow azure to generate network configuration from IMDS per boot. + + 16:14 `` - Scaleway: Add network configuration to the DataSource [Louis Bouchard] + + 16:14 `` - docs: Fix example cloud-init analyze command to match output. + + 16:14 `` [Wesley Gao] + + 16:14 `` - netplan: Correctly render macaddress on a bonds and bridges when + + 16:14 `` provided. (LP: \#1784699) + + 16:14 `` - tools: Add 'net-convert' subcommand command to 'cloud-init devel'. + + 16:14 `` - redhat: remove ssh keys on new instance. (LP: \#1781094) + + 16:14 `` Launchpad bug 1784699 in cloud-init "cloud-init not setting mac address for bond or bridge in bionic" [Medium,Fix committed] [https://launchpad.net/bugs/1784699](https://launchpad.net/bugs/1784699) + + 16:15 `` - Use typeset or local in profile.d scripts. (LP: \#1784713) + + 16:15 `` - OpenNebula: Fix null gateway6 [Akihiko Ota] (LP: \#1768547) + + 16:15 `` Launchpad bug 1781094 in cloud-init "cloud.cfg.tmpl should not include "ssh_deletekeys: 0"" [Medium,Fix committed] [https://launchpad.net/bugs/1781094](https://launchpad.net/bugs/1781094) + + 16:15 `` Launchpad bug 1784713 in cloud-init (Ubuntu) "cloud-init profile.d files use bash-specific builtin "local"" [Low,Confirmed] [https://launchpad.net/bugs/1784713](https://launchpad.net/bugs/1784713) + + 16:15 `` Launchpad bug 1768547 in cloud-init (Ubuntu) "OpenNebula DataSource adds null gateway6 to netplan config" [Medium,Confirmed] [https://launchpad.net/bugs/1768547](https://launchpad.net/bugs/1768547) + + 16:15 `` most notable is the new datasource for Oracle and Azure datasource now emitting network configuration per boot. + + 16:21 `` new Ubuntu cosmic images should contain 18.3-24-gf6249277-0ubuntu1 with the lastest patches + + 16:21 `` \#topic In-progress Development + + 16:23 `` The team in general is perparing for the cloud-init summit conference which will be the second half of this week with cloud and distro vendors so we'll probably be landing a couple more branches in preparation for talks/demos there. + + 16:23 `` *preparing* rather + + 16:24 `` Our trello board is a good representation of any existing work we are "Doing" + + 16:24 `` \#link [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + + 16:26 `` recently powersj has also moved our jenkins server around to a new network so there has been a good bit of work getting all things jenkins back up and running behind the new proxies/firewalls etc. + + 16:26 `` thanks for the heavy lift powersj + + 16:27 `` I think that wraps up all things cloud-init.... + + 16:27 `` \#topic Office Hource (next ~30 mins) + + 16:28 `` We'll have eyes on this channel for any quips, complaints, bug, feature or branch discussions for the next half hour + + 16:28 `` Otherwise, we'll be excited to see a few of you again in this year's cloud-init summit.\ + + 16:28 `` Hi all, I'd like to request a review for this MP: [https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742](https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742) (attached to LP: \#1722959) + + 16:28 `` Launchpad bug 1722959 in cloud-init "Implement Key-Value Pair Telemetry for Azure" [Undecided,In progress] [https://launchpad.net/bugs/1722959](https://launchpad.net/bugs/1722959) + + 16:29 `` Hoping we can get this merged sometime soon. :-) + + 16:29 `` Hi paulmey thanks for the ping on this. + + 16:29 `` \#link [https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742](https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742) + + 16:30 `` \#action rharper/blackboxsw close out on this review before cloud-init summit [https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742](https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742) + + 16:30 * meetingology rharper/blackboxsw close out on this review before cloud-init summit [https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742](https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742) + + 16:30 `` that has gotten dusty, thank you + + 16:31 `` I'll start a review in earnest now + + 16:31 `` Thanks. The dust is mostly mine... Andy has been working on this, but he's in a different time zone, so I'm still pushing it... + + 16:31 `` 😉 + + 16:32 `` paulmey: I'll try spinning up an azure vm to test this out + + 16:34 `` let me know if you need anything + + 17:04 `` ok thanks folks for tuning in. See you next time + + 17:04 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2018-09-04.md b/content/status-2018-09-04.md new file mode 100644 index 0000000..7e91011 --- /dev/null +++ b/content/status-2018-09-04.md @@ -0,0 +1,215 @@ +Title: Cloud-init bi-weekly status +Date: 2018-09-04 16:08:00 UTC +Category: status-meeting-minutes +Slug: status-2018-09-04 + +Meeting information +---------------- + * \#cloud-init: Cloud-init bi-weekly status meeting, 04 Sep at 16:08 — 17:01 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-09-04-16.08.log.html](http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-09-04-16.08.log.html)]] + + + +Meeting summary +---------------- + + **LINK**: [https://cloud-init.github.io/](https://cloud-init.github.io/) + **LINK**: [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + **LINK**: [https://powersj.github.io/post/cloud-init-summit18/](https://powersj.github.io/post/cloud-init-summit18/) +### In-progress Development +The discussion about "In-progress Development" started at 16:22. + + * **LINK**: [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin)?menu=filter&filter=cloud-init + * **LINK**: [https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/353740](https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/353740) + +### Office Hource (next ~30 mins) +The discussion about "Office Hource (next ~30 mins)" started at 16:30. + + +### Active review queue scrub (and open discussion/office hours) +The discussion about "Active review queue scrub (and open discussion/office hours)" started at 16:41. + + * **LINK**: [https://code.launchpad.net/~praween/cloud-init/+git/cloud-init/+merge/353733](https://code.launchpad.net/~praween/cloud-init/+git/cloud-init/+merge/353733) + * **LINK**: [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904) + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (60) + * smoser (8) + * meetingology (3) + * marcoceppi (2) + * ubot5 (1) + + + +Full Log +---------------- + + + 16:08 `` \#startmeeting Cloud-init bi-weekly status meeting + + 16:08 `` Meeting started Tue Sep 4 16:08:21 2018 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:08 `` + + 16:08 `` Available commands: action commands idea info link nick + + 16:08 `` rharper: oddly enough, that didn't work. root wasn't set + + 16:08 `` I'll bother you all after the meeting + + 16:08 `` or during marcoceppi :) sorry for the delay folks, I lost internet for a bit and just got it back up. + + 16:09 `` let's kickoff the bi-weekly status meeting and see what discussion we have for today + + 16:09 `` Our agenda is the following: Previous Actions, Recent Changes, In-progress development and office hours (~30 minutes) + + 16:09 `` \#topic Previous Actions + + 16:10 `` the only logged action per last meeting was the following: + + 16:10 `` rharper/blackboxsw close out on this review before cloud-init summit [https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742](https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742) + + 16:11 `` we were able to land that branch at the cloud-init summit 2 weeks ago and also landed a followup fix for a lock race condition related to that changeset + + 16:11 `` so we can cross that one off the list + + 16:11 `` .... and for those following from home. our meeting minutes from the last status meeting are here + + 16:11 `` \#link [https://cloud-init.github.io/](https://cloud-init.github.io/) + + 16:13 `` Also generically we had a number of action items that came out of our Seattle cloud-init summit with various cloud and distribution partners. Our team will be having a review meeting to discuss some of those actions/decisions and ultimately convert them into trello work items on our board + + 16:13 `` \#link [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + + 16:16 `` \#topic Recent Changes + + 16:17 `` Over the last couple weeks Microsoft hosted a very producting Cloud-init Summit conference in Seattle. A number of clouds and distribution vendors participated to set goals for the cloud-init upstream project. powersj wrote up a nice post to capture some of that work. Thank you all for partipating and helping to improve cloud-init + + 16:17 `` \#link [https://powersj.github.io/post/cloud-init-summit18/](https://powersj.github.io/post/cloud-init-summit18/) + + 16:19 `` also the following changes landed upstream: + + 16:21 `` - Add unit tests for config/cc_ssh.py [Francis Ginther] + + 16:21 `` - Fix the built-in cloudinit/tests/helpers:skipIf + + 16:21 `` - read-version: enhance error message [Joshua Powers] + + 16:21 `` - hyperv_reporting_handler: simplify threaded publisher + + 16:21 `` - VMWare: Fix a network config bug in vm with static IPv4 and no gateway. + + 16:21 `` [Pengpeng Sun] (LP: \#1766538) + + 16:21 `` - logging: Add logging config type hyperv for reporting via Azure KVP + + 16:21 `` [Andy Liu] + + 16:21 `` Launchpad bug 1766538 in cloud-init (Ubuntu) "network customization with cloud-init does not work on Ubuntu18.04 Beta2 Server" [Medium,Confirmed] [https://launchpad.net/bugs/1766538](https://launchpad.net/bugs/1766538) + + 16:22 `` \#topic In-progress Development + + 16:23 `` as always, check our board if there are questions about what we are working on the cloud-init side of the house. any cloud-init cards will have a cloud-init label + + 16:23 `` \#link [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin)?menu=filter&filter=cloud-init + + 16:24 `` we are working a couple of fixes for Oracle as well as the following features that could be interesting to folks: + + 16:24 `` - the ability to use jinja templating in cloud-config or user-scripts to reference any standardized instance meta data cloud-init consumes + + 16:26 `` - allowing new ssh user config in \#cloud-config to specify a ssh-redirect-user, which would allow someone to disable an existing ssh user and provide a redirect message mentioning which username is the preferred default user + + 16:28 `` - ryan is working on refactoring the sysconfig renderer align multiple distros, so that we don't have slightly different implementations in cloud-init for each distribution + + 16:28 `` \#link [https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/353740](https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/353740) + + 16:29 `` beyond that, there a number of new contibutions that have been generated by some of the amazon folks that we plan on reviewing and landing for better amazon linux support + + 16:30 `` thanks again for all the good work. I think we'll transition to the open forum for any discussion/feature/bug work. + + 16:30 `` \#topic Office Hource (next ~30 mins) + + 16:31 `` we'll have eyes on this channel for the next 30 mins. any topic is acceptable; big or small. Bugs, discussions, features, complaints etc. + + 16:31 `` o/ + + 16:31 `` sorry for the interrupt earlier :) + + 16:40 `` Since we have a clear discussion docket for office hours... At the summit we decided maybe it would be a good idea to try reviewing our active review queue to keep the momentum going there and avoid stale branches sitting unresolved for a while. + + 16:41 `` smoser: rharper you gents up for taking a swing at our review queue in this forum to see if we can prioritize what needs landing/response etc? + + 16:41 `` \#topic Active review queue scrub (and open discussion/office hours) + + 16:42 `` sure. + + 16:42 `` I wanted to see if we could land Praveen's branch for Amazon linux support. + + 16:42 `` \#link [https://code.launchpad.net/~praween/cloud-init/+git/cloud-init/+merge/353733](https://code.launchpad.net/~praween/cloud-init/+git/cloud-init/+merge/353733) + + 16:42 `` their CI needs a new makefile target "sources" + + 16:43 `` I suggested that maybe they add that functionality into ./packages/brpm instead of just the commands on the cli + + 16:44 `` since we use brpm in our ci too. .... + + 16:44 `` Praveen had agreed at the summit to make some changes to extend brpm with a new cmdline option to do this work. But I don't see anything pushed. I'd like to mark this work in progress and comment to that affect. sound good? + + 16:46 `` blackboxsw: that sounds good + + 16:49 `` smoser: ok [https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/354001](https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/354001) I'll grab today after this meeting so we can land all the leaky unit tests. geez man + + 16:49 * blackboxsw grabs the review slot + + 16:50 `` I believe robert's branch is tabled until ryan's sysconfig branch is landed + + 16:50 `` \#link [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904) + + 16:50 `` ^ should we mark this 'work in progress' as it's blocked? or maybe just leave it in the active queue + + 16:51 `` blackboxsw: your needs information still stands right? + + 16:51 `` lets move it to work-in-progress and ask for response and also ask if it is sitll necessary (unless you know that it is or is not) + + 16:52 `` and suggest that it will need to be re-worked. + + 16:53 `` smoser: that sounds good. my 'needs information' on that is resolved/read/discussed already. so I should abstain for the moment until the rework + + 16:57 `` ok couple more minutes... any additional reviews we should look at in earnest now? + + 16:58 `` I kinda want to hold on [https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392](https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392) until we have our summit retro meeting today + + 16:59 `` here's a short one. [https://code.launchpad.net/~otubo/cloud-init/+git/cloud-init/+merge/353436.](https://code.launchpad.net/~otubo/cloud-init/+git/cloud-init/+merge/353436.) should we mark this 'work in progress' until smoser's review comments are addressed and unit tests added? + + 16:59 `` blackboxsw: yeah. i'll do that. + + 17:00 `` ok thanks. and I think that'll about wrap it for today. If we don't resolve the other community reviews by next status meeting, we can continue chipping away at this queue then. + + 17:01 `` I'll post the minutes to cloudinit.github.io just after this. + + 17:01 `` blackboxsw: i'm loking at rharper's mp now for the system config + + 17:01 `` ok I'll get your review on [https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/354001](https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/354001) now + + 17:01 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2018-09-25.md b/content/status-2018-09-25.md new file mode 100644 index 0000000..300b436 --- /dev/null +++ b/content/status-2018-09-25.md @@ -0,0 +1,201 @@ +Title: Cloud-init bi-weekly status +Date: 2018-09-25 16:05:00 UTC +Category: status-meeting-minutes +Slug: status-2018-09-25 + +Meeting information +---------------- + * \#cloud-init: Cloud-init bi-weekly status meeting, 25 Sep at 16:05 — 17:10 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-09-25-16.05.log.html](http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-09-25-16.05.log.html)]] + + + +Meeting summary +---------------- + +### Previous Actions +The discussion about "Previous Actions" started at 16:09. + + +### Recent Changes +The discussion about "Recent Changes" started at 16:10. + + +### In-Progress development +The discussion about "In-Progress development" started at 16:15. + + * **LINK**: [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + +### 18.4 Release Schedule +The discussion about "18.4 Release Schedule" started at 16:26. + + * **LINK**: [https://code.launchpad.net/~cloud-init-dev/cloud-init/+git/cloud-init/+ref/master/+activereviews](https://code.launchpad.net/~cloud-init-dev/cloud-init/+git/cloud-init/+ref/master/+activereviews) + * **LINK**: [https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/](https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/) + +### Office hours (next ~30 mins) +The discussion about "Office hours (next ~30 mins)" started at 16:31. + + * **LINK**: [https://cloud-init.github.io](https://cloud-init.github.io) + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (54) + * ubot5 (6) + * meetingology (3) + * rharper (2) + + + +Full Log +---------------- + + + 16:05 `` \#startmeeting Cloud-init bi-weekly status meeting + + 16:05 `` Meeting started Tue Sep 25 16:05:46 2018 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:05 `` + + 16:05 `` Available commands: action commands idea info link nick + + 16:06 `` Hi cloud-init folks, time to kickoff our bi-weekly(ish) status meeting. As mentioned on the mailing list we pushed this meeting out until today so we could have a discussion about the 18.4 upstream release which is scheduled for this Thursday. + + 16:07 `` I just updated the topic to reflect the 18.4 release date, Sept 27th EOD. + + 16:08 `` for today's meeting we have the following agenda: Previous Actions, Recent Changes, In-progress development and 18.4 release discussion/office hours/ (~30 minutes) + + 16:09 `` \#topic Previous Actions + + 16:09 * blackboxsw reviews our notes from Sept11 @ [https://cloud-init.github.io](https://cloud-init.github.io) + + 16:10 `` No actions listed in previous meeting so we'll move to the next topic + + 16:10 `` \#topic Recent Changes + + 16:12 `` Last week, we had some travel and planning discussions for cloud-init which took a few cycles out of our upstream landed content, but we were able to review and land a few items over the last couple weeks. Below is the list of changes that have landed in upstream cloud-init master. I expect we'll publish 18.4 release this week to Ubuntu Cosmic, so any changes below will be present in our next public release. + + 16:12 `` - pylint: ignore warning assignment-from-no-return for _write_network + + 16:12 `` - stages: Fix bug causing datasource to have incorrect sys_cfg. + + 16:12 `` ([LP: \#1787459]([https://bugs.launchpad.net/bugs/1787459](https://bugs.launchpad.net/bugs/1787459))) + + 16:12 `` - Remove dead-code _write_network distro implementations. + + 16:12 `` - net_util: ensure static configs have netmask in translate_network result + + 16:12 `` [Thomas Berger] ([LP: \#1792454]([https://bugs.launchpad.net/bugs/1792454](https://bugs.launchpad.net/bugs/1792454))) + + 16:12 `` - Fall back to root:root on syslog permissions if other options fail. + + 16:12 `` Ubuntu bug 1787459 in cloud-init (Ubuntu) "datasource.sys_cfg gets different values in local stage and after." [Medium,Confirmed] + + 16:12 `` [Robert Schweikert] + + 16:12 `` - tests: Add mock for util.get_hostname. [Robert Schweikert] ([LP: \#1792799]([https://bugs.launchpad.net/bugs/1792799](https://bugs.launchpad.net/bugs/1792799))) + + 16:12 `` - ds-identify: doc string cleanup. + + 16:12 `` - OpenStack: Support setting mac address on bond. + + 16:12 `` Ubuntu bug 1792454 in cloud-init "Network configuration broken for some distributions with OpenNebula, EC2, Azure" [High,Fix committed] + + 16:12 `` [Fabian Wiesel] ([LP: \#1682064]([https://bugs.launchpad.net/bugs/1682064](https://bugs.launchpad.net/bugs/1682064))) + + 16:12 `` - bash_completion/cloud-init: fix shell syntax error. + + 16:12 `` Ubuntu bug 1792799 in cloud-init "Host environment bleeds into test for mirror access testing" [Undecided,Fix committed] + + 16:12 `` - EphemeralIPv4Network: Be more explicit when adding default route. + + 16:12 `` ([LP: \#1792415]([https://bugs.launchpad.net/bugs/1792415](https://bugs.launchpad.net/bugs/1792415))) + + 16:12 `` Ubuntu bug 1682064 in cloud-init "cloud-init should support config bond mac address " [Medium,Fix committed] + + 16:12 `` - OpenStack: support reading of newer versions of metdata. + + 16:12 `` - OpenStack: fix bug causing 'latest' version to be used from network. + + 16:12 `` ([LP: \#1792157]([https://bugs.launchpad.net/bugs/1792157](https://bugs.launchpad.net/bugs/1792157))) + + 16:12 `` Ubuntu bug 1792415 in cloud-init (Ubuntu) "WARNINGs and failures in log on OVH public cloud" [Medium,Confirmed] + + 16:12 `` Ubuntu bug 1792157 in cloud-init (Ubuntu) "cloud-init uses openstack latest version due to decoding bug" [Medium,In progress] + + 16:13 `` Thank you again Robert, Thomas and Fabian for continued contributions to cloud-init upstream. Things are looking really good for the upcoming release + + 16:15 `` \#topic In-Progress development + + 16:16 `` We are beating the drum toward the 18.4 release, as such, we are going to focus more on low-risk changes and bug fixes as we close in on the 18.4 upstream cutoff. + + 16:17 `` All of the work we have planned lives over on our trello board. + + 16:18 `` \#link [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + + 16:19 `` In our doing and review lane I expect we'll have a couple branches landing for standardizing and generalizing /run/cloud/instance-data.json on all clouds, and a couple of new cloud-init CLI commands 'cloud-init query' and 'cloud-id' to surface standardized instance-data on any cloud platform + + 16:20 `` post-18.4 release rharper has been doing some excellent work adding hotplug network support to OpenStack. I expect we'll be landing his branches shortly after we cut 18.4 + + 16:21 `` blackboxsw: thanks; it's been super interesting + + 16:21 `` this should give us an excellent example of reacting to changing metadata on a given platform, which hopefully other datasources will be able to adopt. + + 16:25 `` As far as additional content for the release, I'll also be circling an email around to the mailing list (cloud-init@lists.launchpad.net ) to describe existing instance data that cloud-init publishes. We are looking for input on common instance meta data that folks would like to see generalized across clouds. + + 16:26 `` I think about wraps up our current dev tasks. + + 16:26 `` \#topic 18.4 Release Schedule + + 16:27 `` As mentioned earlier, we would like to cut 18.4 upstream release and tag it at end of day on Thursday, Sept 27th. + + 16:27 `` We will be looking at the active review queue for any branches with the 'Needs review' status. + + 16:28 `` \#link [https://code.launchpad.net/~cloud-init-dev/cloud-init/+git/cloud-init/+ref/master/+activereviews](https://code.launchpad.net/~cloud-init-dev/cloud-init/+git/cloud-init/+ref/master/+activereviews) + + 16:28 `` If there are branches or bugs that you think need attention, please don't hesitate to mail the mailing list, or ping in this channel to get attention + + 16:29 `` After thursday, we'll be performing some additional manual and automated integration tests and we will plan on publishing 18.4 to Ubuntu Cosmic. + + 16:29 `` As a service, we also will publish that 18.4 release to the following copr repo for those centos-inclined individuals :) + + 16:30 `` \#link [https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/](https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/) + + 16:30 `` For each upstream release we sync that release to the 'el-testing' repo. + + 16:31 `` Daily upstream snapshots are also available at [https://copr.fedorainfracloud.org/coprs/g/cloud-init/cloud-init-dev/](https://copr.fedorainfracloud.org/coprs/g/cloud-init/cloud-init-dev/) + + 16:31 `` \#topic Office hours (next ~30 mins) + + 16:33 `` I think that about wraps the fire hose of content for our meeting. For the next 30 mins we should have eyes on this channel to discuss the finer points of life as well as anything cloud-init related. Bring your bugs, gripes, requests, reviews and/or discussions and we'll get a good answer for you. + + 16:33 * blackboxsw is going to hitup the review queue at the moment so see if there are some cloud-init branches we can clear out. + + 16:45 `` +1 + + 17:09 `` ok that about wraps it for today. + + 17:10 `` minutes will be published to the following link. Thanks again folks! See you next time + + 17:10 `` \#link [https://cloud-init.github.io](https://cloud-init.github.io) + + 17:10 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2018-10-15.md b/content/status-2018-10-15.md new file mode 100644 index 0000000..f759431 --- /dev/null +++ b/content/status-2018-10-15.md @@ -0,0 +1,340 @@ +Title: Cloud-init bi-weekly status +Date: 2018-10-15 16:15:00 UTC +Category: status-meeting-minutes +Slug: status-2018-10-15 + +Meeting information +---------------- + * \#cloud-init: Cloud-init bi-weekly status, 15 Oct at 16:15 — 17:00 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-10-15-16.15.log.html](http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-10-15-16.15.log.html)]] + + + +Meeting summary +---------------- + +### Previous Actions +The discussion about "Previous Actions" started at 16:18. + + * **LINK**: [https://cloud-init.github.io/](https://cloud-init.github.io/) + +### Recent Changes +The discussion about "Recent Changes" started at 16:19. + + * **LINK**: [https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html\#using-instance-data](https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html\#using-instance-data) + +### In-Progress Development +The discussion about "In-Progress Development" started at 16:28. + + * **LINK**: trello.com/b/hFtWKUn3/daily-cloud-init-curtin + +### Office hours (next ~30 mins) +The discussion about "Office hours (next ~30 mins)" started at 16:35. + + * **LINK**: [https://bugs.launchpad.net/cloud-init/+bug/1794399](https://bugs.launchpad.net/cloud-init/+bug/1794399) + * **ACTION**: Sort and review azure RHEL branch related to ephemeral dhcp handling of dhclient [https://bugs.launchpad.net/cloud-init/+bug/1794399](https://bugs.launchpad.net/cloud-init/+bug/1794399) + * **ACTION**: paulmey to dig up reference to proposed patch for [https://bugs.launchpad.net/cloud-init/+bug/1794399](https://bugs.launchpad.net/cloud-init/+bug/1794399) + + + +Vote results +---------------- + + + + +Action items, by person +---------------- + + * paulmey + * paulmey to dig up reference to proposed patch for [https://bugs.launchpad.net/cloud-init/+bug/1794399](https://bugs.launchpad.net/cloud-init/+bug/1794399) + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (89) + * paulmey (22) + * ubot5 (13) + * meetingology (5) + * smoser (2) + + + +Full Log +---------------- + + + 16:15 `` \#startmeeting Cloud-init bi-weekly status + + 16:15 `` Meeting started Mon Oct 15 16:15:41 2018 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:15 `` + + 16:15 `` Available commands: action commands idea info link nick + + 16:17 `` hi guys and gals. Today marks a belated cloud-init status meeting we use to provide a forum where folks from the cloud-init community can keep up to date on latest cloud-init developments and tap a shoulder if bugs or features need discussion/attention. + + 16:17 `` Next meeting will be two weeks from now on October 29th. at 16:00 UTC (as in the topic of this channel) + + 16:18 `` Today's meeting will go through the typical topics: Previous Actions, Recent Changes, In-progress development and Office hours + + 16:18 `` \#topic Previous Actions + + 16:19 `` No unresolved actions from last meeting on Sept 25th. + + 16:19 `` For those interested our previous meeting minutes are at the following: + + 16:19 `` \#link [https://cloud-init.github.io/](https://cloud-init.github.io/) + + 16:19 `` \#topic Recent Changes + + 16:20 `` There has been a lot of work put into cloud-init over the last couple of weeks due to the timing of the Ubuntu Cosmic (18.10) series final freeze and release schedule + + 16:21 `` We managed to squeeze in a couple of features into 18.4 as well as improved some of Ubuntu's automated testing for StableReleaseUpdates (SRUs). + + 16:22 `` Beyond the 18.4 public upstream release (which is in Ubuntu Cosmic). We have the following commits that have landed since the last status meeting. + + 16:22 `` - tests: allow skipping an entire cloud_test without running. + + 16:22 `` - tests: disable lxd tests on cosmic + + 16:22 `` - cii-tests: use unittest2.SkipTest in ntp_chrony due to new deps + + 16:22 `` - lxd: adjust to snap installed lxd. + + 16:22 `` - docs: surface experimental doc in instance-data.json + + 16:22 `` - tests: fix ec2 integration tests. process meta_data instead of meta-data + + 16:22 `` - Add support for Infiniband network interfaces (IPoIB). [Mark Goddard] + + 16:22 `` - cli: add cloud-init query subcommand to query instance metadata + + 16:22 `` - tools/tox-venv: update for new features. + + 16:22 `` - pylint: ignore warning assignment-from-no-return for _write_network + + 16:22 `` - stages: Fix bug causing datasource to have incorrect sys_cfg. + + 16:22 `` ([LP: \#1787459]([https://bugs.launchpad.net/bugs/1787459](https://bugs.launchpad.net/bugs/1787459))) + + 16:22 `` - Remove dead-code _write_network distro implementations. + + 16:22 `` - net_util: ensure static configs have netmask in translate_network result + + 16:22 `` [Thomas Berger] ([LP: \#1792454]([https://bugs.launchpad.net/bugs/1792454](https://bugs.launchpad.net/bugs/1792454))) + + 16:22 `` Ubuntu bug 1787459 in cloud-init (Ubuntu) "datasource.sys_cfg gets different values in local stage and after." [Medium,Fix released] + + 16:22 `` - Fall back to root:root on syslog permissions if other options fail. + + 16:22 `` [Robert Schweikert] + + 16:22 `` Ubuntu bug 1792454 in cloud-init "Network configuration broken for some distributions with OpenNebula, EC2, Azure" [High,Fix released] + + 16:22 `` - tests: Add mock for util.get_hostname. [Robert Schweikert] ([LP: \#1792799]([https://bugs.launchpad.net/bugs/1792799](https://bugs.launchpad.net/bugs/1792799))) + + 16:22 `` - ds-identify: doc string cleanup. + + 16:22 `` Ubuntu bug 1792799 in cloud-init "Host environment bleeds into test for mirror access testing" [Undecided,Fix released] + + 16:22 `` - OpenStack: Support setting mac address on bond. + + 16:22 `` - bash_completion/cloud-init: fix shell syntax error. + + 16:22 `` - EphemeralIPv4Network: Be more explicit when adding default route. + + 16:22 `` ([LP: \#1792415]([https://bugs.launchpad.net/bugs/1792415](https://bugs.launchpad.net/bugs/1792415))) + + 16:22 `` - OpenStack: support reading of newer versions of metdata. + + 16:22 `` - OpenStack: fix bug causing 'latest' version to be used from network. + + 16:22 `` Ubuntu bug 1792415 in cloud-init (Ubuntu) "WARNINGs and failures in log on OVH public cloud" [Medium,Fix released] + + 16:22 `` ([LP: \#1792157]([https://bugs.launchpad.net/bugs/1792157](https://bugs.launchpad.net/bugs/1792157))) + + 16:22 `` Ubuntu bug 1792157 in cloud-init (Ubuntu) "cloud-init uses openstack latest version due to decoding bug" [Medium,Fix released] + + 16:23 `` - Correct spelling in an error message (udevadm). [Katie McLaughlin] + + 16:23 `` - tests: meta_data key changed to meta-data in ec2 instance-data.json + + 16:23 `` ([LP: \#1797231]([https://bugs.launchpad.net/bugs/1797231](https://bugs.launchpad.net/bugs/1797231))) + + 16:23 `` - tests: fix kvm integration test to assert flexible config-disk path + + 16:23 `` ([LP: \#1797199]([https://bugs.launchpad.net/bugs/1797199](https://bugs.launchpad.net/bugs/1797199))) + + 16:23 `` - tools: Add cloud-id command line utility + + 16:23 `` - instance-data: Add standard keys platform and subplatform. Refactor ec2. + + 16:23 `` - net: ignore nics that have "zero" mac address. ([LP: \#1796917]([https://bugs.launchpad.net/bugs/1796917](https://bugs.launchpad.net/bugs/1796917))) + + 16:23 `` - tests: fix apt_configure_primary to be more flexible + + 16:23 `` Ubuntu bug 1797231 in cloud-init "ec2 integration test failure on changed instance-data.json" [High,Fix committed] + + 16:23 `` - Ubuntu: update sources.list to comment out deb-src entries. ([LP: \#74747]([https://bugs.launchpad.net/bugs/74747](https://bugs.launchpad.net/bugs/74747))) + + 16:23 `` - release 18.4 ([LP: \#1795741]([https://bugs.launchpad.net/bugs/1795741](https://bugs.launchpad.net/bugs/1795741))) + + 16:23 `` Ubuntu bug 1797199 in cloud-init "kvm integration test failures due to invalid config-disk path" [High,Fix committed] + + 16:23 `` Ubuntu bug 1796917 in cloud-images "cloud-init fails to run on latest cosmic minimal image" [High,Fix released] + + 16:23 `` Ubuntu bug 74747 in cloud-init (Ubuntu Bionic) "Default sources.list file has source packages enabled by default" [Medium,Confirmed] + + 16:23 `` Ubuntu bug 1795741 in cloud-init (Ubuntu) "Release 18.4" [Medium,Fix released] + + 16:26 `` If you get a chance, it's worth noting that \#cloud-config files can now be presented as a jinja template to the instance by adding a \#\# template: jinja as the first line above the \#cloud-config in your user-data. Any metadata that cloud-init consumes (like cloud-given hostnames, ip addresses, region names etc) can be sourced and rendered in your cloud-config files now. + + 16:27 `` \#link [https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html\#using-instance-data](https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html\#using-instance-data) + + 16:27 `` ^ for more information on instance data and templating + + 16:28 `` \#topic In-Progress Development + + 16:28 `` \#link trello.com/b/hFtWKUn3/daily-cloud-init-curtin + + 16:29 `` Our trello board tracks our current work. The most notable effort is cloud-init network hotplug handling for datasources which is currently being driven by rharper + + 16:30 `` What he is adding is the ability for for a datasource to be configured react to network hotplug events and apply cloud-init determined network configuration on device add/remove + + 16:31 `` This feature will be opt-in and configurable by the end-user to allow cloud-init to own network for any device added or removed after the initial boot. This feature will debut in OpenStack clouds and will shortly be adopted by other cloud/datasource types. + + 16:33 `` Also, smoser and I will be heading to OpenSource Summit Europe next week in Edinburgh, UK. [https://events.linuxfoundation.org/events/open-source-summit-europe-2018/](https://events.linuxfoundation.org/events/open-source-summit-europe-2018/) + + 16:34 `` If you are in town come say hi :) + + 16:35 `` Without further ado, I think that about wraps our status for today + + 16:35 `` \#topic Office hours (next ~30 mins) + + 16:37 `` Almost forgot; as part of the SRU process for for cloud-init to release into Xenial and Bionic, we'll be doing some additional manual and automated testing of cloud-init version 18.4 before publishing to those LTS series. I expect that'll take up a bit of our time this week and next as there is a lot to verify for that release. + + 16:38 `` For the next 30 mins, a few of us will have eyes on the channel for anyone with a desire to talk cloud-init bugs, features or reviews. Thanks again for the contributions and making cloud-init better! + + 16:40 `` Hi blackboxsw + + 16:41 `` Hi paulmey, how're things + + 16:41 `` ? + + 16:41 `` Good! How about yourself? + + 16:41 `` My buddy Jason has a bug open that could use some attention: [https://bugs.launchpad.net/cloud-init/+bug/1794399](https://bugs.launchpad.net/cloud-init/+bug/1794399) + + 16:41 `` Ubuntu bug 1794399 in cloud-init "cloud-init dhcp_discovery() crashes on preprovisioned RHEL 7.6 VM in Azure" [Undecided,New] + + 16:41 `` this is a stopgap fix until we have a pure-python dhcp client + + 16:42 `` it's been a push for the Cosmic release for us, racing to get things sorted, but I think we are on the other side of any fires now :) + + 16:42 `` ahh checking that bug + + 16:42 `` :-) good to hear that + + 16:42 `` it's basically just some more robustness around the handling of dhclient execution + + 16:44 `` it reproed very reliably on RHEL with reprovisioning (changing network etc., maybe slower/faster dhcp response?), but pretty unreproducible outside of that... + + 16:44 `` paulmey: jason made reference to a patch, but I don't see it linked to the bug.... I'm checking the review queue now + + 16:44 `` we saw cloud-init killing or trying to kill the initial process (which has already finished after the util exec) + + 16:45 `` was that bug just a request for us to make cloud-init more resilient in light of forking, or a request to accept a patch + + 16:45 `` let me link the patch... once I find it :-) + + 16:45 `` give me a minute + + 16:46 * blackboxsw documents the link for the meeting bot + + 16:46 `` \#link [https://bugs.launchpad.net/cloud-init/+bug/1794399](https://bugs.launchpad.net/cloud-init/+bug/1794399) + + 16:46 `` Ubuntu bug 1794399 in cloud-init "cloud-init dhcp_discovery() crashes on preprovisioned RHEL 7.6 VM in Azure" [Undecided,New] + + 16:46 * blackboxsw Sort and review azure RHEL branch related to ephemeral dhcp handling of dhclient [https://bugs.launchpad.net/cloud-init/+bug/1794399](https://bugs.launchpad.net/cloud-init/+bug/1794399) + + 16:47 `` \#action Sort and review azure RHEL branch related to ephemeral dhcp handling of dhclient [https://bugs.launchpad.net/cloud-init/+bug/1794399](https://bugs.launchpad.net/cloud-init/+bug/1794399) + + 16:47 * meetingology Sort and review azure RHEL branch related to ephemeral dhcp handling of dhclient [https://bugs.launchpad.net/cloud-init/+bug/1794399](https://bugs.launchpad.net/cloud-init/+bug/1794399) + + 16:48 `` yeah, I wonder if now that 18.4 is cut and released if we want to start banging the drum to get our scapy-based dhclient solution landed in cloud-init proper so we don't have to patchup the ephemeral dhcp work in cloud-init. + + 16:50 `` while you look paulmey, I'll make sure we talk at our standups about what we can do with cloud-init's own dhcp-discovery so we don't have to handle different distro implementations of dhclient. The sandboxed dhclient solution we have felt dirty in the first place. + + 16:51 `` yar... I can't find a reference to it in my mails... I'll need to circle back with Jason. I prototyped the patch and he write some unit tests. I know it's somewhere, just not exactly where... + + 16:51 `` our only concern I thought with using scapy was adding the additional package dependency, (which we wouldn't be able to get released back into Ubuntu Xenial Bionic or Cosmic). But, we can resolve to come of with an approach for the nearterm + + 16:52 `` paulmey: sounds good. :) care if I add a virtual action item for you too to the meeting minutes + + 16:52 `` Sure, no problem + + 16:52 `` at least it'll guarantee we make progress before next meeting + + 16:52 `` \#action paulmey to dig up reference to proposed patch for [https://bugs.launchpad.net/cloud-init/+bug/1794399](https://bugs.launchpad.net/cloud-init/+bug/1794399) + + 16:52 * meetingology paulmey to dig up reference to proposed patch for [https://bugs.launchpad.net/cloud-init/+bug/1794399](https://bugs.launchpad.net/cloud-init/+bug/1794399) + + 16:52 `` Ubuntu bug 1794399 in cloud-init "cloud-init dhcp_discovery() crashes on preprovisioned RHEL 7.6 VM in Azure" [Undecided,New] + + 16:52 `` thanks + + 16:53 `` paulmey: are there other azure related discussions/features that are collecting dust with us that you know of? + + 16:54 `` not yet collecting dust, but I know that Sushant Sharma is going to be coming with some networking-related updates for pre-provisioning like we discussed at the summit + + 16:54 `` he's testing those on real systems right now + + 16:54 `` I know hyperv reporting feature is functional in cloud-init now. and that folks are instrumenting changes in images to support that. + + 16:55 `` ahh right. good to hear + + 16:55 `` we're also talking to SUSE this week to see what the next steps are to get cloud-init functional on Azure + + 16:55 `` ohh neat! + + 16:56 `` I know we still have some work items, but we're prototyping some stuff to get ahead of some testing work + + 16:56 `` funny thing is that I'm hardly doing any of this work. :-) + + 16:56 `` good to see more and more people at MS doing work on cloud-init + + 16:57 `` heh, juggling a lot I'm sure. yeah it is nice to see more devs involved + + 16:58 `` paulmey: thats great to hear wrt suse + + 16:58 `` ok, cool. I'll follow up with Jason and circle back. If anything else comes to fruition before the 29th, I'll send people here to evangalize + + 16:59 `` perfect. Thanks again paulmey + + 16:59 `` and /me agrees it'd be good to have a dhclient in cloud-init for what we need it for. scapy or other. + + 16:59 `` think I'll wrap up this meeting for today + + 16:59 `` (although it's always nice to talk to you guys... feels good being able to say was on IRC this week... :-P) + + 16:59 `` sgtm + + 16:59 `` heh, take care + + 16:59 `` ttyl + + 17:00 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2018-10-29.md b/content/status-2018-10-29.md new file mode 100644 index 0000000..1288599 --- /dev/null +++ b/content/status-2018-10-29.md @@ -0,0 +1,186 @@ +Title: Cloud-init bi-weekly status +Date: 2018-10-29 16:21:00 UTC +Category: status-meeting-minutes +Slug: status-2018-10-29 + +Meeting information +---------------- + * \#cloud-init: Cloud-init bi-weekly status, 29 Oct at 16:21 — 17:09 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-10-29-16.21.log.html](http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-10-29-16.21.log.html)]] + + + +Meeting summary +---------------- + +### Previous Actions +The discussion about "Previous Actions" started at 16:22. + + * **LINK**: [https://cloud-init.github.io/status-2018-10-15.html\#status-2018-10-15](https://cloud-init.github.io/status-2018-10-15.html\#status-2018-10-15) + * **ACTION**: Sort and review azure RHEL branch related to ephemeral dhcp handling of dhclient [https://bugs.launchpad.net/cloud-init/+bug/1794399](https://bugs.launchpad.net/cloud-init/+bug/1794399) + * **ACTION**: blackboxsw, rharper smoser a review on [https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427](https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427) before next status meeting for Azure dhcp. + +### Recent Changes +The discussion about "Recent Changes" started at 16:28. + + * **LINK**: [https://events.linuxfoundation.org/events/open-source-summit-europe-2018/](https://events.linuxfoundation.org/events/open-source-summit-europe-2018/) + +### In-Progress Development +The discussion about "In-Progress Development" started at 16:38. + + * **LINK**: [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + +### Office hours (next ~30 mins) +The discussion about "Office hours (next ~30 mins)" started at 16:44. + + * **LINK**: [https://cloud-init.github.io/](https://cloud-init.github.io/) + + + +Vote results +---------------- + + + + +Action items, by person +---------------- + + * blackboxsw + * blackboxsw, rharper smoser a review on [https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427](https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427) before next status meeting for Azure dhcp. + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (46) + * meetingology (5) + * ubot5 (4) + + + +Full Log +---------------- + + + 16:21 `` \#startmeeting Cloud-init bi-weekly status + + 16:21 `` Meeting started Mon Oct 29 16:21:16 2018 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:21 `` + + 16:21 `` Available commands: action commands idea info link nick + + 16:22 `` hi folks, now marks a 20 minute belated cloud-init status meeting, an opportunity to chat about current and future cloud-init happenings. + + 16:22 `` Today's meeting will go through the typical topics: Previous Actions, Recent Changes, In-progress development and Office hours + + 16:22 `` \#topic Previous Actions + + 16:23 `` Looking over our last meeting minutes, we had a single action + + 16:23 `` \#link [https://cloud-init.github.io/status-2018-10-15.html\#status-2018-10-15](https://cloud-init.github.io/status-2018-10-15.html\#status-2018-10-15) + + 16:24 `` \#action Sort and review azure RHEL branch related to ephemeral dhcp handling of dhclient [https://bugs.launchpad.net/cloud-init/+bug/1794399](https://bugs.launchpad.net/cloud-init/+bug/1794399) + + 16:24 * meetingology Sort and review azure RHEL branch related to ephemeral dhcp handling of dhclient [https://bugs.launchpad.net/cloud-init/+bug/1794399](https://bugs.launchpad.net/cloud-init/+bug/1794399) + + 16:24 `` Ubuntu bug 1794399 in cloud-init "cloud-init dhcp_discovery() crashes on preprovisioned RHEL 7.6 VM in Azure" [Undecided,New] + + 16:25 `` the meeting later showed us we didn't really have a branch referencing that bug, looks like paulmey was able to follow up there to tie the related branch to the bug. So we have something to review now + + 16:27 `` So looks like this is a *carryover* from last meeting, thanks Paul for tying the branch to this bug so we have something to review related to it. The branch is currently waiting on review feedback from cloud-init upstream. So, I'll pull it in for us to review this week + + 16:27 `` \#action blackboxsw, rharper smoser a review on [https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427](https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427) before next status meeting for Azure dhcp. + + 16:27 * meetingology blackboxsw, rharper smoser a review on [https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427](https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427) before next status meeting for Azure dhcp. + + 16:28 `` \#topic Recent Changes + + 16:29 `` over the last week, a number of us have been travelling at either planning meetings for cloud-init or the OpenSource Summit in Europe. + + 16:29 `` \#link [https://events.linuxfoundation.org/events/open-source-summit-europe-2018/](https://events.linuxfoundation.org/events/open-source-summit-europe-2018/) + + 16:30 `` The cloud-init talk had a pretty good turn out at OSS EU. I think we had ~ 100 people in attendance and some good questions about potential support of the following: + + 16:31 `` - Ansible and CFEgine config module support in cloud-initt + + 16:32 `` - better netplan config use-case handling + + 16:33 `` - better vmware integration as well as a request for proxmox (opensource alternative to vmware?) support + + 16:34 `` thanks smoser for a job well done on that talk. + + 16:35 `` beyond the conference highlight, cloud-init tip is being published to Xenial and Bionic on Ubuntu. + + 16:36 `` Expect to see updates published in today's images that will handle template-support for \#cloud-config and user-data scripts and generalized instance-data.json on most recent Ubuntu releases. + + 16:36 `` tip of cloud-init has seen the following changes merged: + + 16:36 `` - instance-data: fallback to instance-data.json if sensitive is absent. + + 16:36 `` ([LP: \#1798189]([https://bugs.launchpad.net/bugs/1798189](https://bugs.launchpad.net/bugs/1798189))) + + 16:36 `` - docs: remove colon from network v1 config example. [Tomer Cohen] + + 16:36 `` - Add cloud-id binary to packages for SUSE [Jason Zions] + + 16:36 `` - systemd: On SUSE ensure cloud-init.service runs before wicked + + 16:36 `` [Robert Schweikert] ([LP: \#1799709]([https://bugs.launchpad.net/bugs/1799709](https://bugs.launchpad.net/bugs/1799709))) + + 16:36 `` - update detection of openSUSE variants [Robert Schweikert] + + 16:36 `` - azure: Add apply_network_config option to disable network from IMDS + + 16:36 `` ([LP: \#1798424]([https://bugs.launchpad.net/bugs/1798424](https://bugs.launchpad.net/bugs/1798424))) + + 16:36 `` Ubuntu bug 1798189 in cloud-init "cloud-init query: /run/cloud/instance-data-sensitive.json not generated on upgrade" [Medium,Fix committed] + + 16:36 `` Ubuntu bug 1799709 in cloud-init "service order is incorrect for SUSE distros" [Undecided,Fix committed] + + 16:36 `` Ubuntu bug 1798424 in cloud-init (Ubuntu) "Xenial Azure: Make generation of network config from IMDS hotplug scripts configurable opt-in" [Undecided,New] + + 16:37 `` Thanks robjo for the commitment to keeping SuSE up to date and fully functional with cloud-init. + + 16:38 `` And thanks Jason and Tomer for the contributions to packaging and docs as well + + 16:38 `` Think that about wraps Recent Changes topic.... + + 16:38 `` \#topic In-Progress Development + + 16:39 `` Check out trello board for a prioritized order of what upstream is working + + 16:39 `` \#link [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + + 16:41 `` There are a couple of community branches in the wings that we'll get reviews on and shepherd into cloud-init proper. Azure has some work to increase efficiency of the detection and reporting during initial boot. + + 16:42 `` smoser is working on supplemental work with meena to handle platform-specializing our cloudinit.net module. + + 16:43 `` and I think we have a couple of branches pulled together for legacy centos6 build support and supporting Azure Gen2 vms. + + 16:43 `` We'll keep the trello board updated as big items come down the pipeline for us. + + 16:44 `` \#topic Office hours (next ~30 mins) + + 16:44 `` so eyes will float on this channel a bit for any questions, concerns, bugs or features. + + 16:45 `` thanks again for your time and contributions folks. + + 17:09 `` alright. guess I'll call it wrap for this meeting. You can tune in to minutes on published github to browse any content that has been discussed at previous status meetings. + + 17:09 `` \#link [https://cloud-init.github.io/](https://cloud-init.github.io/) + + 17:09 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) diff --git a/content/status-2018-11-12.md b/content/status-2018-11-12.md new file mode 100644 index 0000000..9ab0cc8 --- /dev/null +++ b/content/status-2018-11-12.md @@ -0,0 +1,186 @@ +Title: Cloud-init bi-weekly status +Date: 2018-11-12 16:17:00 UTC +Category: status-meeting-minutes +Slug: status-2018-11-12 + +Meeting information +---------------- + * \#cloud-init: Cloud-init bi-weekly status, 12 Nov at 16:17 — 17:27 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-11-12-16.17.log.html](http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-11-12-16.17.log.html)]] + + + +Meeting summary +---------------- + + **LINK**: [https://cloud-init.github.io/](https://cloud-init.github.io/) +### Previous Actions +The discussion about "Previous Actions" started at 16:20. + + * **LINK**: [https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427](https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427) + +### Recent Changes +The discussion about "Recent Changes" started at 16:24. + + +### In-progress Development +The discussion about "In-progress Development" started at 16:30. + + * **LINK**: [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + * **LINK**: [https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/358112](https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/358112) + * **LINK**: [https://bugs.launchpad.net/cloud-init/+bug/1802598](https://bugs.launchpad.net/cloud-init/+bug/1802598) + +### Office Hours (next ~30 minutes) +The discussion about "Office Hours (next ~30 minutes)" started at 16:40. + + * **LINK**: [https://code.launchpad.net/~i.galic/cloud-init/+git/cloud-init/+merge/357723](https://code.launchpad.net/~i.galic/cloud-init/+git/cloud-init/+merge/357723) + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (53) + * ubot5 (3) + * meetingology (3) + + + +Full Log +---------------- + + + 16:17 `` \#startmeeting Cloud-init bi-weekly status + + 16:17 `` Meeting started Mon Nov 12 16:17:50 2018 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:17 `` + + 16:17 `` Available commands: action commands idea info link nick + + 16:18 `` Morning/afternoon folks. Time for another brief episode of cloud-init upstream updates + + 16:18 `` Last meeting was 10/29 and meeting minutes live over on github + + 16:18 `` \#link [https://cloud-init.github.io/](https://cloud-init.github.io/) + + 16:20 `` This meeting is an open forum for cloud-init discussions and status updates, feel free to interject at any time. It really is just a venue by which we can make sure we all have eyes and ears available for discussion on features, bugs or branches if needed. + + 16:20 `` Generally we go through the following topics: Previous Actions, Recent Changes, In-progress Development, and Office hours + + 16:20 `` \#toic Previous Actions + + 16:20 `` \#topic Previous Actions + + 16:21 `` So last meeting we carried in one action, to review the following Azure branch related to DHCP and RHEL race conditions + + 16:21 `` [https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427](https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427) + + 16:22 `` Looks like rharper got a review in and I don't see any updates from Jason Zion (author) in response to that branch + + 16:22 `` thanks rharper + + 16:22 `` I'm marking that branch as 'Work in progress' and commenting that the author should set it back to 'Needs review' when comments have been addressed + + 16:24 `` ok done. No further actions seen + + 16:24 `` \#topic Recent Changes + + 16:24 * blackboxsw digs up changes since 10/28 + + 16:29 `` sorry interrupted. + + 16:29 `` Here are the changes committed: + + 16:29 `` - azure: add udev rules to create cloud-init Gen2 disk name symlinks + + 16:29 `` ([LP: \#1797480]([https://bugs.launchpad.net/bugs/1797480](https://bugs.launchpad.net/bugs/1797480))) + + 16:29 `` - tests: ec2 mock missing httpretty user-data and instance-identity routes + + 16:29 `` - azure: remove /etc/netplan/90-hotplug-azure.yaml when net from IMDS + + 16:29 `` - azure: report ready to fabric after reprovision and reduce logging + + 16:29 `` [asakkurr] ([LP: \#1799594]([https://bugs.launchpad.net/bugs/1799594](https://bugs.launchpad.net/bugs/1799594))) + + 16:29 `` - query: better error when missing read permission on instance-data + + 16:29 `` Ubuntu bug 1797480 in cloud-init "Azure: Support ephemeral disk handling on Gen2 VMs" [High,Fix committed] + + 16:29 `` Ubuntu bug 1799594 in cloud-init "Azure - Report ready during preprovisioning as soon as we get the ReprovisionData" [Undecided,Fix committed] + + 16:29 `` As you can see we are seeing a bit of momentum on azure datasource and some continuous integration cleanup on our side. + + 16:30 `` Thanks asakkurr for pulling that Azure branch together + + 16:30 `` \#topic In-progress Development + + 16:31 `` We track our current cloud-init development publicly on trello + + 16:31 `` \#link [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + + 16:31 `` if there are any questions about certain branches or work feel free to comment in channel or on the linked branches we document there. + + 16:32 `` It looks like the Ubuntu archive for Disco Dingo series is open, so we'll likely be pushing an upload of tip of cloud-init by EOD today to get a new release queued + + 16:33 `` Also to note, I'd like to see us land [https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/358112](https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/358112) to fix an Azure retry on IMDS timeout to avoid cloud-init giving up if the instance boots while IMDS service is down or temporarily unavailable (I've only seen this once on any azure instance) + + 16:33 `` \#link [https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/358112](https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/358112) + + 16:35 `` we also have a fairly deep review queue, so we'll be attacking that in the 2nd half of today's meeting to clear out and respond to some of those merge proposals + + 16:36 `` I also think we have some mailing list threads to start responding to per usage of EphemeralDHCPv4 and EphemeralIPv4Network context managers. + + 16:37 `` I *think* the intent there should be that those context managers ensure that they setup whatever requested network configuration is misssing from a network interface.... so if an interface is 'down' yet has correct address configured, ephemeral* will make sure it is in operable 'up' state . + + 16:37 `` See the following bug for more information: + + 16:38 `` \#link [https://bugs.launchpad.net/cloud-init/+bug/1802598](https://bugs.launchpad.net/cloud-init/+bug/1802598) + + 16:38 `` Ubuntu bug 1802598 in cloud-init "EphemeralIPv4Network: when device has requested existing network config, but link is down, network setup does not bring link up" [Undecided,New] + + 16:39 `` I believe that about wraps it for current in-flight work. I'll drop us into office hours at the point + + 16:40 `` \#topic Office Hours (next ~30 minutes) + + 16:40 `` Cloud-init upstream folks will have eyes on this channel for any discussions. requests, bugs or features folks want to discuss. + + 16:40 `` I'll spend most of this time on reviews to start to clear our review queue (or at least get some responses out to folks for more information)( + + 17:03 `` ok looks like [https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357669](https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357669) is ready for landing. Just kicking off a CI test run on it + + 17:04 `` also the approved version of this branch didn't actually match what Jenkins autolander expected, I've kick the jenkins landing job that should truly land that branch now. [https://code.launchpad.net/~asakkurr/cloud-init/+git/cloud-init/+merge/358422](https://code.launchpad.net/~asakkurr/cloud-init/+git/cloud-init/+merge/358422)' + + 17:25 `` \#link [https://code.launchpad.net/~i.galic/cloud-init/+git/cloud-init/+merge/357723](https://code.launchpad.net/~i.galic/cloud-init/+git/cloud-init/+merge/357723) + + 17:25 `` ok just got through an initial review there too. + + 17:26 `` ok looks like our lander merged [https://code.launchpad.net/~asakkurr/cloud-init/+git/cloud-init/+merge/358422](https://code.launchpad.net/~asakkurr/cloud-init/+git/cloud-init/+merge/358422) + + 17:26 `` and :( [https://jenkins.ubuntu.com/server/job/cloud-init-ci/431/console](https://jenkins.ubuntu.com/server/job/cloud-init-ci/431/console) the CI on jason zion + + 17:27 `` and :( [https://jenkins.ubuntu.com/server/job/cloud-init-ci/431/console](https://jenkins.ubuntu.com/server/job/cloud-init-ci/431/console) the CI on jason zion's branch will take 9 hrs and 51 minutes (because it doesn't have our CI fix for leaked test_ec2 link local unittests which take forever to timeout + + 17:27 `` ok will that about wraps today's status meeting + + 17:27 `` thanks all + + 17:27 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2018-11-26.md b/content/status-2018-11-26.md new file mode 100644 index 0000000..f2a2824 --- /dev/null +++ b/content/status-2018-11-26.md @@ -0,0 +1,232 @@ +Title: Cloud-init bi-weekly status +Date: 2018-11-26 16:18:00 UTC +Category: status-meeting-minutes +Slug: status-2018-11-26 + +Meeting information +---------------- + * \#cloud-init: Cloud-init bi-weekly status, 26 Nov at 16:18 — 17:17 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-11-26-16.18.log.html](http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-11-26-16.18.log.html)]] + + + +Meeting summary +---------------- + + **LINK**: [https://cloud-init.github.io](https://cloud-init.github.io) + **LINK**: [https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427](https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427) + **LINK**: [https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/358881](https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/358881) + **LINK**: c[https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392](https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392) + **LINK**: [https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392](https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392) +### Recent Changes +The discussion about "Recent Changes" started at 16:29. + + +### In-Progress Development +The discussion about "In-Progress Development" started at 16:33. + + * **LINK**: [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + +### Office Hours (next ~30 minutes) +The discussion about "Office Hours (next ~30 minutes)" started at 16:45. + + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (64) + * meena (10) + * rharper (4) + * meetingology (3) + * ubot5 (2) + + + +Full Log +---------------- + + + 16:18 `` \#startmeeting Cloud-init bi-weekly status + + 16:18 `` Meeting started Mon Nov 26 16:18:39 2018 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:18 `` + + 16:18 `` Available commands: action commands idea info link nick + + 16:18 `` Morning/Afternoon folks. welcome to another cloud-init status meeting + + 16:20 `` ... our open forum to advertise current cloud-init developments, giving an opportunity to discuss bugs or features in cloud-init and provide a touch point for the community + + 16:20 `` Generally we go through the following topics: Previous Actions, Recent Changes, In-progress Development, and Office hours + + 16:20 `` \#topic Previous Actions + + 16:20 `` our last meeting's minutes are located here + + 16:21 `` \#link [https://cloud-init.github.io](https://cloud-init.github.io) + + 16:21 `` only thing we carried into that meeting is a an review + + 16:21 `` \#link [https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427](https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427) + + 16:22 `` rharper: had closed out feedback on the review. with a needs fixing. I did see some followup commits there from the author Jason Zion. + + 16:23 `` I think we need to take a look at this again and see if our comments were addressed, I'm marking it "Needs review" + + 16:24 `` I see no other actions carried over... but there was talk last week about a couple of branches so let's add these + + 16:25 `` \#link [https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/358881](https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/358881) + + 16:25 `` ^ disco support + + 16:25 `` \#link c[https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392](https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392) + + 16:25 `` \#link [https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392](https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392) + + 16:25 `` ^ Azure netlink listener + + 16:26 `` ok next topic + + 16:29 `` \#topic Recent Changes + + 16:30 `` - azure: _poll_imds only retry on 404. Fail on Timeout + + 16:30 `` ([LP: \#1803598]([https://bugs.launchpad.net/bugs/1803598](https://bugs.launchpad.net/bugs/1803598))) + + 16:30 `` - resizefs: Prefix discovered devpath with '/dev/' when path does not + + 16:30 `` exist [Igor Galić] + + 16:30 `` Ubuntu bug 1803598 in cloud-init "Do not retry polling IMDS for reprovisiondata during timeout" [Undecided,Fix committed] + + 16:30 `` t'was a slow week with all that Thanksgiving holiday stuff for US-based employees + + 16:30 `` welcome back from the Holidays boys and girls + + 16:31 `` also we were able to publish tip of cloud-init to Ubuntu Disco series + + 16:32 `` cloud-init 18.4-24-g8f812a15-0ubuntu1 has latest and greatest as seen on tip of master + + 16:33 `` \#topic In-Progress Development + + 16:33 `` \#link [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + + 16:34 `` Our trello board tracks our queued and current work for cloud-init, feel free to watch that board for updates on significant cloud-init features/bug-fixes + + 16:34 `` what generally isn't tracked there is reviews on community authored branches + + 16:36 `` per community driven content, we have a number of branches from meena for better FreeBSD support in flight. Great work! and some Azure platform development to react to netlink events during the preprovisioning state. + + 16:36 `` thanks tamilmani_ on the azure work. + + 16:39 `` As a heads up to folks, we are trying to cut an upstream release of cloud-init 18.5 on 12/15/2018. So if there are branches you want to see landed or bugs you need fixed please holler here in this channel or on the mailing list to:cloud-init.lists.launchpad.net + + 16:39 `` We'll send an email to the mailing list requesting for input on the release as well + + 16:39 `` >` blackboxsw what generally isn't tracked there is reviews on community authored branches `<== i did check there first time around, but found nothing that was topical for me + + 16:41 `` Correct meena . I used to capture outstanding community reviews that needed review follow up, but that ended up being out of date all the time. It was easier for us to just use launchpad active review queue instead + + 16:43 `` Now we've tried to adopt the setting of a branch status to 'work in progress' if we are expecting feedback/fixes from the author. And have the author set it back to 'needs review' when it is ready for another round of upstream reviews + + 16:44 `` having trello cards was basically just duplicating what launchpad reviews were designed for, we just need to be more vigilant about grooming the review queue and getting folks the feedback they need + + 16:45 `` might as well switch over to office hours for open discussion etc. + + 16:45 `` \#topic Office Hours (next ~30 minutes) + + 16:45 `` Cloud-init upstream folks will have eyes on this channel for any discussions. requests, bugs or features folks want to discuss. + + 16:45 `` we'll also spend some time actively grooming the branch review queue to see if we can clear out some review debyt + + 16:45 `` we'll also spend some time actively grooming the branch review queue to see if we can clear out some review debt + + 16:46 `` I think smoser mentioned at our team standup this morning he was taking one more review on [https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392](https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392) + + 16:47 `` rharper: if you are done with your review on that tamilmani_ branch can you add a comment that doesn't leave it in "Needs fixing" review state from yoiu? + + 16:48 `` blackboxsw: yes, I'm adding a commit message now, and I'll leave a comment marking approve; + + 16:48 `` excellent. + + 16:48 `` I'm going to give a review to [https://code.launchpad.net/~i.galic/cloud-init/+git/cloud-init/+merge/358876](https://code.launchpad.net/~i.galic/cloud-init/+git/cloud-init/+merge/358876) now + + 16:48 * blackboxsw claims a review slot + + 16:49 `` blackboxsw: did we have a LP for thisone ? + + 16:49 `` the netlink ? + + 16:52 `` ohh, no we did not I don't think. + + 16:52 `` I'll check + + 16:56 `` blackboxsw: i think my (our) patch is ready to be merged + + 16:57 `` rharper: yeah didn't find any bug filed related to Azure and dhcp leak or netlink response etc. + + 16:57 `` (the feature / fix of adding connectivity check to ephemeral network stuff) + + 16:58 `` meena: I think so too. Was just dusting off my memory on that one. I'm going to do a quick test run of setup/teardown and I think that's good. +1 + + 16:58 `` thanks again + + 16:58 `` once that's merged, I'll have a much easier time with splitting out the freebsd network + + 16:59 `` blackboxsw: thank you for showing me how to do the tests properly + + 16:59 `` most welcome. + + 17:00 `` blackboxsw: thanks, me neither; I just didn't want to miss a LP: in the commit message if we had one + + 17:01 `` after this branch lands and tamilmani_'s I probably will go through the motions of us publishing to Ubuntu Disco again, because I want to get a round or two of integration tests on both Azure and AWS with both the ephemeral* changes and the netlink stuff on pristine cloud-images before next week's release + + 17:06 `` meena: you didn't file a bug related to the ephermeraldhcp network connectivity did you? (I'm just double checking as I don't see one) + + 17:07 `` meena: not needed, just didn't want to miss it if it was there (as we'd want to link it in the commit message) + + 17:08 `` blackboxsw: nah, we just "filed" a mailing list thread + + 17:08 `` all good thanks + + 17:09 `` ok I had filed [https://bugs.launchpad.net/cloud-init/+bug/1802598](https://bugs.launchpad.net/cloud-init/+bug/1802598) but we won't tie that to this branch + + 17:09 `` Ubuntu bug 1802598 in cloud-init "EphemeralIPv4Network: when device has requested existing network config, but link is down, network setup does not bring link up" [Undecided,Triaged] + + 17:09 `` it's a bit more about idempotent behavior + + 17:13 `` *nod *nod + + 17:13 `` i didn't think i had fixed it, so i didn't connect them. + + 17:16 `` +1 on your branch meena, it should land within the hour. Just tested it out one more time + + 17:16 `` cool + + 17:16 `` ok I think that about wraps today's meeting timewise. Thanks again for the chat meena. + + 17:16 `` \o/ + + 17:17 `` next meeting is Dec 10, 2018 sameish time + + 17:17 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2018-12-10.md b/content/status-2018-12-10.md new file mode 100644 index 0000000..99a405a --- /dev/null +++ b/content/status-2018-12-10.md @@ -0,0 +1,198 @@ +Title: Cloud-init bi-weekly status +Date: 2018-12-10 16:11:00 UTC +Category: status-meeting-minutes +Slug: status-2018-12-10 + +Meeting information +---------------- + * \#cloud-init: Cloud-init bi-weekly status, 10 Dec at 16:11 — 16:58 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-12-10-16.11.log.html](http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-12-10-16.11.log.html)]] + + + +Meeting summary +---------------- + +### Previous Actions +The discussion about "Previous Actions" started at 16:13. + + * **LINK**: [https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427](https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427) + * **LINK**: [https://cloud-init.github.io/status-2018-11-26.html\#status-2018-11-26](https://cloud-init.github.io/status-2018-11-26.html\#status-2018-11-26) + * **LINK**: [https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392](https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392) + +### Recent Changes +The discussion about "Recent Changes" started at 16:19. + + +### In-Progress Development +The discussion about "In-Progress Development" started at 16:24. + + * **LINK**: [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + * **LINK**: [https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/359876](https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/359876) + +### Cloud-init upstream Release 18.5 +The discussion about "Cloud-init upstream Release 18.5" started at 16:27. + + +### Office Hours (next ~30 minutes) +The discussion about "Office Hours (next ~30 minutes)" started at 16:31. + + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (57) + * meetingology (3) + * ubot5 (2) + * powersj (1) + + + +Full Log +---------------- + + + 16:11 `` \#startmeeting Cloud-init bi-weekly status + + 16:11 `` Meeting started Mon Dec 10 16:11:11 2018 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:11 `` + + 16:11 `` Available commands: action commands idea info link nick + + 16:12 `` Welcome to our biweekly status meeting. The intent is to provide a venue where we can advertise current cloud-init development efforts and a place and time where interested community members can ask questions or raise issues to the upstream development team. + + 16:12 `` Generally we go through the following topics: Previous Actions, Recent Changes, In-progress Development, and Office hours + + 16:13 `` Today we'll add a "Release" topic + + 16:13 `` Let's kick it off + + 16:13 `` \#topic Previous Actions + + 16:14 `` One action we need to carry over from last meeting + + 16:14 `` \#link [https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427](https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427) + + 16:14 `` our followup review is required on this branch to avoid a race condition for DHCP discovery on RHEL + + 16:15 `` I don't think there were any other actions raised last meeting + + 16:15 `` BTW our meeting minutes from last status meeting are here + + 16:15 `` \#link [https://cloud-init.github.io/status-2018-11-26.html\#status-2018-11-26](https://cloud-init.github.io/status-2018-11-26.html\#status-2018-11-26) + + 16:17 `` we did land and publish cloud-init to Disco containing the Azure netlink listener support branch which was raised as an action last meeting. per the following + + 16:17 `` \#link [https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392](https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392) + + 16:19 `` \#topic Recent Changes + + 16:20 `` The following branches landed in cloud-init tip- dhclient-hook: cleanups, tests and fix a bug on 'down' event. + + 16:20 `` - NoCloud: Allow top level 'network' key in network-config. ([LP: \#1798117]([https://bugs.launchpad.net/bugs/1798117](https://bugs.launchpad.net/bugs/1798117))) + + 16:20 `` - ovf: Fix ovf network config generation gateway/routes + + 16:20 `` [Ryan Harper] ([LP: \#1806103]([https://bugs.launchpad.net/bugs/1806103](https://bugs.launchpad.net/bugs/1806103))) + + 16:20 `` - Published Cloud-init v.18.3-41 to Ubuntu Disco + + 16:20 `` - azure: detect vnet migration via netlink media change event + + 16:20 `` [Tamilmani Manoharan] + + 16:20 `` - Azure: fix copy/paste error in error handling when reading azure ovf. + + 16:20 `` [Adam DePue] + + 16:20 `` Ubuntu bug 1798117 in cloud-init (Ubuntu) "juju sends "network" top level key to user.network-config in lxd containers" [Medium,Confirmed] + + 16:20 `` - tests: fix incorrect order of mocks in test_handle_zfs_root. + + 16:20 `` - doc: Change dns_nameserver property to dns_nameservers. [Tomer Cohen] + + 16:20 `` Ubuntu bug 1806103 in cloud-init (Ubuntu) "ovf: network config store routes under nic subnets 'routes' key" [Undecided,New] + + 16:20 `` - OVF: identify label iso9660 filesystems with label 'OVF ENV'. + + 16:20 `` - net: Ephemeral*Network: add connectivity check via URL + + 16:20 `` [Igor Galić] + + 16:21 `` we also published all latest changes to Ubuntu Disco as 18.4-31-gbf791715-0ubuntu1 + + 16:22 `` I missed a couple of other commits to cloud-init + + 16:23 `` - config: On ubuntu select cloud archive mirrors for armel, armhf, arm64. + + 16:23 `` - write_files: add support for appending to files. [James Baxter] + + 16:23 `` Thanks James, Tamilmani, Adam and Tomer for the contributions here and making cloud-init bette + + 16:23 `` r + + 16:24 `` \#topic In-Progress Development + + 16:24 `` We track our current work in the TODO, Doing and Done lanes on trello + + 16:24 `` \#link [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + + 16:25 `` mostly we are trying to wrap up low-hanging-fruit and bug fixes as we have an upstream release scheduled this week for cloud-init 18.5 + + 16:25 `` There is also some significant work ongoing my smoser for vmware and ovf deployment support + + 16:25 `` *by smoser* + + 16:26 `` and rharper has a branch up to fix network metric config handling for subnet routes + + 16:26 `` \#link [https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/359876](https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/359876) + + 16:27 `` think that about wraps in-progress work. + + 16:27 `` \#topic Cloud-init upstream Release 18.5 + + 16:27 `` So, we have our 18.5 upstream release scheduled for this Wednesday 12/13/2018 + + 16:28 `` If there are any feature requests or critical bug fixes that folks are interested, please bring them up either in channel here, or on the mailing list, cloud-init@lists.launchpad.net + + 16:29 `` blackboxsw, ^ is that worth sending to mailing list? + + 16:30 `` powersj: yes. I'll send that email out in the next half hour + + 16:30 `` agreed + + 16:31 `` think that about wraps this status update for this meeting + + 16:31 `` \#topic Office Hours (next ~30 minutes) + + 16:32 `` upstream devs will have eyes on this channel for any concerns, questions or discussions folks want to have about cloud-init. + + 16:32 `` Given the upcoming holidays, I think we will take a break from this meeting as next scheduled time would be the day before Christmas. + + 16:33 `` Next status meeting will be Monday January 7th 16:15 UTC + + 16:41 `` email sent to cloud-init about upcoming release + + 16:58 `` Happy Holiday folks. Looks like we're already starting to use up vacation time. Thanks for tuning in. See you next year! + + 16:58 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2019-01-28.md b/content/status-2019-01-28.md new file mode 100644 index 0000000..553c9b3 --- /dev/null +++ b/content/status-2019-01-28.md @@ -0,0 +1,227 @@ +Title: Cloud-init bi-weekly status +Date: 2019-01-28 16:26:00 UTC +Category: status-meeting-minutes +Slug: status-2019-01-28 + +Meeting information +---------------- + * \#cloud-init: Cloud-init bi-weekly status, 28 Jan at 16:26 — 17:31 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-01-28-16.26.log.html](http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-01-28-16.26.log.html)]] + + + +Meeting summary +---------------- + +### Previous Actions +The discussion about "Previous Actions" started at 16:27. + + * **ACTION**: carry over blackboxsw close and land Openstack metadata handling bug [https://bugs.launchpad.net/cloud-init/+bug/1801364](https://bugs.launchpad.net/cloud-init/+bug/1801364) + +### Recent Changes +The discussion about "Recent Changes" started at 16:36. + + +### In-Progress Development +The discussion about "In-Progress Development" started at 16:47. + + * **LINK**: [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + +### Office Hours (next ~30 minutes) +The discussion about "Office Hours (next ~30 minutes)" started at 16:51. + + * **LINK**: [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/357710](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/357710) merged + * **LINK**: [https://cloud-init.github.io](https://cloud-init.github.io) + + + +Vote results +---------------- + + + + +Action items, by person +---------------- + + * blackboxsw + * carry over blackboxsw close and land Openstack metadata handling bug [https://bugs.launchpad.net/cloud-init/+bug/1801364](https://bugs.launchpad.net/cloud-init/+bug/1801364) + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (60) + * robjo (6) + * ubot5 (6) + * meetingology (4) + + + +Full Log +---------------- + + + 16:26 `` \#startmeeting Cloud-init bi-weekly status + + 16:26 `` Meeting started Mon Jan 28 16:26:28 2019 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:26 `` + + 16:26 `` Available commands: action commands idea info link nick + + 16:27 `` hi cloud-init folks, it's that happy time again to chat about cloud-init upstream. + + 16:27 `` Generally the topics we cover in this status meeting are: Previous Actions, Recent Changes, In-progress Development, and Office hours + + 16:27 `` \#topic Previous Actions + + 16:30 `` previously we had an action to review [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098.](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098.) I think rharper and robjo have a couple of back and forths on this branch. looks like we'll be able to land this + + 16:32 `` and oh noes, we need to followup and resolve the following MD bug on OpenStack [https://bugs.launchpad.net/cloud-init/+bug/1801364](https://bugs.launchpad.net/cloud-init/+bug/1801364) + + 16:32 `` Ubuntu bug 1801364 in cloud-init "persisting OpenStack metadata fails" [Undecided,Confirmed] + + 16:32 `` \#action carry over blackboxsw close and land Openstack metadata handling bug [https://bugs.launchpad.net/cloud-init/+bug/1801364](https://bugs.launchpad.net/cloud-init/+bug/1801364) + + 16:32 * meetingology carry over blackboxsw close and land Openstack metadata handling bug [https://bugs.launchpad.net/cloud-init/+bug/1801364](https://bugs.launchpad.net/cloud-init/+bug/1801364) + + 16:32 `` Well that one was just about an additional empty line which I removed in October + + 16:34 `` ok I'll spend the 2nd half of this meeting going through this again and landing it if no other concerns. \#toostale seeing [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098) + + 16:35 `` it doesn't look on review that there is anything concerning there. + + 16:36 `` ok I think that we it for actions last time. + + 16:36 `` \#topic Recent Changes + + 16:36 `` blackboxsw: There's also [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/357710](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/357710) + + 16:36 `` which appears to be complaining about he commit message + + 16:37 `` robjo: oops autolander rejection, will fix the LP commit message now and make approved (for merging) + + 16:37 `` Server Team CI bot (server-team-bot) wrote on 2019-01-07: \# + + 16:37 `` Commit message lints: + + 16:37 `` - Expected empty line on line 2 of the commit message + + 16:37 `` Can there not be a template in LP for the commit message? + + 16:38 `` I can never remember the formatting intricacies and thus depend on one of you guys to set this + + 16:38 `` robjo: does the 'commit message' on the merge proposal look good to you now [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/357710](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/357710) + + 16:39 `` at the top + + 16:39 `` LGTM, thanks + + 16:39 `` I've clicked approve and it should autoland within ~15 mins + + 16:39 `` great + + 16:40 `` so recent commits to upstream cloud-init + + 16:41 `` - flake8: use ==/!= to compare str, bytes, and int literals + + 16:41 `` [Paride Legovini] + + 16:41 `` - opennebula: exclude EPOCHREALTIME as known bash env variable with a + + 16:41 `` delta [Chad Smith] ([LP: \#1813383]([https://bugs.launchpad.net/bugs/1813383](https://bugs.launchpad.net/bugs/1813383))) + + 16:41 `` - tox: fix disco httpretty dependencies for py37 + + 16:41 `` Ubuntu bug 1813383 in cloud-init "opennebula: fail to sbuild, bash environment var failure EPOCHREALTIME" [Undecided,Fix committed] + + 16:41 `` ha, ircflood boot + + 16:41 `` not sure how far I got in that list of commits + + 16:42 `` - lxd: install zfs-linux instead of zfs meta package + + 16:42 `` 09:41 [Johnson Shi] ([LP: \#1799779]([https://bugs.launchpad.net/bugs/1799779](https://bugs.launchpad.net/bugs/1799779))) + + 16:42 `` 09:41 - net/sysconfig: do not write a resolv.conf file with only the header. + + 16:42 `` 09:41 [Robert Schweikert] + + 16:42 `` 09:41 - net: Make sysconfig renderer compatible with Network Manager. + + 16:42 `` Ubuntu bug 1799779 in cloud-init (Ubuntu Disco) "LXD module installs the wrong ZFS package if it's missing" [Medium,Confirmed] + + 16:42 `` 09:41 [Eduardo Otubo] + + 16:42 `` - cc_set_passwords: Fix regex when parsing hashed passwords + + 16:42 `` 09:41 [Marlin Cremers] ([LP: \#1811446]([https://bugs.launchpad.net/bugs/1811446](https://bugs.launchpad.net/bugs/1811446))) + + 16:42 `` Ubuntu bug 1811446 in cloud-init (Ubuntu) "chpasswd: is mangling certain password hashes" [Undecided,In progress] + + 16:42 `` 09:41 - net: Wait for dhclient to daemonize before reading lease file + + 16:42 `` 09:41 [Jason Zions] ([LP: \#1794399]([https://bugs.launchpad.net/bugs/1794399](https://bugs.launchpad.net/bugs/1794399))) + + 16:42 `` Ubuntu bug 1794399 in cloud-init "cloud-init dhcp_discovery() crashes on preprovisioned RHEL 7.6 VM in Azure" [Undecided,Fix committed] + + 16:42 `` 09:41 - [Azure] Increase retries when talking to Wireserver during metadata walk + + 16:42 `` 09:41 [Jason Zions] + + 16:42 `` 09:41 - Add documentation on adding a datasource. + + 16:42 `` Thanks folks for all the contributions to cloud-init over the last couple of weeks. + + 16:43 `` Additionally, we just published tip of cloud-init to Ubuntu disco (19.04) development release + + 16:44 `` and we have queued that release as well (cloud-init 18.5.17) for SRU (stable release update) into Xenial, Bionic and Cosmic as of Saturday. + + 16:44 `` the SRU process bug can be watched to see when 18.5.17 publishes to 16.04 18.04 and 18.10. (xenial, bionic, cosmic) [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1813346](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1813346) + + 16:44 `` Ubuntu bug 1813346 in cloud-init (Ubuntu) "sru cloud-init (18.4.0 update to 18.5-17-gd1a2fe73) Xenial, Bionic, Cosmic" [Undecided,New] + + 16:46 `` Also we welcome our new QA team member paride to Canonical, he's been working on re-enabling our copr build repos and generally improving the quality of our continuous integration for cloud-init (and other Canonical projects) + + 16:47 `` \#topic In-Progress Development + + 16:47 `` we tracking our ongoing cloud-init upstream work (and backlog) on our Trello board + + 16:47 `` \#link [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + + 16:49 `` the next couple of weeks will likely result in Ubuntu SRU verificantion for that release into xenial, bionic and cosmic. robjo's been working on a few OpenSUSE/sysconfig network handling branches that will likely land. and we'll have a couple of EC2 branches that need to address EC2-Classic network re-configuration across reboots + + 16:50 `` and, as mentioned our upstream copr repo builds will likely be fixed for centos/fedora consumers + + 16:51 `` \#topic Office Hours (next ~30 minutes) + + 16:52 `` So, upsteram devs will have eyes on this channel for any further discussion, bugs or questions about cloud-init. Please use this venue as you see fit to raise awareness of stale branches, bugs etc so we can queue them up for review. + + 16:53 * blackboxsw is going to look over [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098) to see if we can close out on that today + + 17:30 `` [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/357710](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/357710) merged + + 17:30 `` and just approved [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098) + + 17:30 `` thanks robjo + + 17:30 `` I think that about wraps it up for today. thanks again for checking in folks. + + 17:30 `` As always minutes will be posted to cloud-init's github page @ + + 17:31 `` \#link [https://cloud-init.github.io](https://cloud-init.github.io) + + 17:31 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2019-05-13.md b/content/status-2019-05-13.md new file mode 100644 index 0000000..2378da6 --- /dev/null +++ b/content/status-2019-05-13.md @@ -0,0 +1,507 @@ +Title: Cloud-init bi-weekly status +Date: 2019-05-13 16:25:00 UTC +Category: status-meeting-minutes +Slug: status-2019-05-13 + +Meeting information +---------------- + * \#cloud-init: Cloud-init bi-weekly status, 13 May at 16:25 — 17:32 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-05-13-16.25.log.html](http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-05-13-16.25.log.html)]] + + + +Meeting summary +---------------- + +### Previous Actions +The discussion about "Previous Actions" started at 16:31. + + * **LINK**: [https://cloud-init.github.io/status-2019-01-28.html\#status-2019-01-28](https://cloud-init.github.io/status-2019-01-28.html\#status-2019-01-28) + * **LINK**: [https://bugs.launchpad.net/cloud-init/+bug/1801364](https://bugs.launchpad.net/cloud-init/+bug/1801364) + * **ACTION**: Odd_Bloke confirm correct status of [https://bugs.launchpad.net/cloud-init/+bug/1801364](https://bugs.launchpad.net/cloud-init/+bug/1801364) + +### Recent Changes +The discussion about "Recent Changes" started at 16:35. + + * **LINK**: [https://launchpad.net/cloud-init/+milestone/19.1](https://launchpad.net/cloud-init/+milestone/19.1) + +### In-progress Development +The discussion about "In-progress Development" started at 16:46. + + * **LINK**: [https://wiki.ubuntu.com/CloudinitUpdates](https://wiki.ubuntu.com/CloudinitUpdates) + * **LINK**: [https://trello.com/c/oxv61bPl/1099-sru-191-xenial-bionic-cosmic-and-disco](https://trello.com/c/oxv61bPl/1099-sru-191-xenial-bionic-cosmic-and-disco) + * **LINK**: [https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/](https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/) + * **LINK**: [https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367301](https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367301) + * **LINK**: [https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367302](https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367302) + * **LINK**: [https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367297](https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367297) + * **LINK**: [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1828637](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1828637) + * **LINK**: [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + +### Office hours (next ~30 mins) +The discussion about "Office hours (next ~30 mins)" started at 17:02. + + * **LINK**: [https://cloudinit.readthedocs.io/en/latest/topics/tests.html\#](https://cloudinit.readthedocs.io/en/latest/topics/tests.html\#) + * **LINK**: [https://cloud-init.github.io](https://cloud-init.github.io) + * **ACTION**: Odd_Bloke/rharper/AnhVoMSFT followup on recommended approach for getting kernel/userspace timestamp with or without python-dbus package dependency + + + +Vote results +---------------- + + + + +Action items, by person +---------------- + + * AnhVoMSFT + * Odd_Bloke/rharper/AnhVoMSFT followup on recommended approach for getting kernel/userspace timestamp with or without python-dbus package dependency + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (163) + * AnhVoMSFT (20) + * ubot5` (19) + * meetingology (5) + * powersj (3) + + + +Full Log +---------------- + + + 16:25 `` \#startmeeting Cloud-init bi-weekly status + + 16:25 `` Meeting started Mon May 13 16:25:37 2019 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:25 `` + + 16:25 `` Available commands: action commands idea info link nick + + 16:26 `` hi folks, we are restarting the cloud-init community status meeting so we can have a community forum to discuss current cloud-init development and try to improve momentum in the cloud-init project efforts. + + 16:28 `` over the last couple of months we had taken a break from this meeting. But, I think it's shown us that there is demand and usefulness in continuing hosting these meetings. So, from here on, we expect to post the upcoming date of status meetings in this channel's room topic. + + 16:29 `` Again the goal of this meeting is to give people a chance to see what work is currently being performed on upstream cloud-init as well as a forum to discuss or raise concerns or get eyes on potential bugs or features. + + 16:30 `` Generally the topics we would like to cover are the following: (and interjections/suggestions are always welcome + + 16:30 `` topics: Previous Actions, Recent Changes, In-progress Development, Office Hours. + + 16:31 `` \#topic Previous Actions + + 16:32 `` so, looking at our last status minutes from the last meeting, (on Jan 28.... :( ) we had one action carried over + + 16:32 `` \#link [https://cloud-init.github.io/status-2019-01-28.html\#status-2019-01-28](https://cloud-init.github.io/status-2019-01-28.html\#status-2019-01-28) + + 16:33 `` review and land [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098) + + 16:33 `` that's done. as well as an openstack bug... + + 16:33 `` \#link [https://bugs.launchpad.net/cloud-init/+bug/1801364](https://bugs.launchpad.net/cloud-init/+bug/1801364) + + 16:33 `` Ubuntu bug 1801364 in cloud-init "persisting OpenStack metadata fails" [Undecided,Confirmed] + + 16:33 `` Odd_Bloke: has landed this bug, I think it needs to be marked fix committed though + + 16:34 `` Odd_Bloke: is out today at a meeting, but I'll mark that action so we can make sure that bug status is properly reported (if there are no other branches to land for it) + + 16:34 `` \#action Odd_Bloke confirm correct status of [https://bugs.launchpad.net/cloud-init/+bug/1801364](https://bugs.launchpad.net/cloud-init/+bug/1801364) + + 16:34 * meetingology Odd_Bloke confirm correct status of [https://bugs.launchpad.net/cloud-init/+bug/1801364](https://bugs.launchpad.net/cloud-init/+bug/1801364) + + 16:34 `` Ubuntu bug 1801364 in cloud-init "persisting OpenStack metadata fails" [Undecided,Confirmed] + + 16:34 `` That;s about it for actions from previous meeting. + + 16:35 `` \#topic Recent Changes + + 16:36 `` Here we list current content that has landed in cloud-init since last meeting..... because it has been a really long time since last meeting, I'm going to redact this to the last month or so of content to avoid getting banned in this channel for spam + + 16:37 `` - Azure: Return static fallback address as if failed to find endpoint + + 16:37 `` [Jason Zions (MSFT)] + + 16:37 `` - release 19.1 (LP: \#1828479) + + 16:37 `` - freebsd: add chpasswd pkg in the image [Gonéri Le Bouder] + + 16:37 `` - tests: add Eoan release [Paride Legovini] + + 16:37 `` Launchpad bug 1828479 in cloud-init "Release 19.1" [Undecided,Fix released] [https://launchpad.net/bugs/1828479](https://launchpad.net/bugs/1828479) + + 16:37 `` hah, I don't think that worked + + 16:37 `` ok breaking that content up + + 16:37 `` - Azure: Return static fallback address as if failed to find endpoint + + 16:37 `` [Jason Zions (MSFT)] + + 16:37 `` - release 19.1 (LP: \#1828479) + + 16:37 `` - freebsd: add chpasswd pkg in the image [Gonéri Le Bouder] + + 16:37 `` - tests: add Eoan release [Paride Legovini] + + 16:37 `` - cc_mounts: check if mount -a on no-change fstab path + + 16:37 `` [Jason Zions (MSFT)] (LP: \#1825596) + + 16:37 `` - replace remaining occurrences of LOG.warn [Daniel Watkins] + + 16:37 `` Launchpad bug 1825596 in cloud-init "Azure reboot with unformatted ephemeral drive won't mount reformatted volume" [High,Fix released] [https://launchpad.net/bugs/1825596](https://launchpad.net/bugs/1825596) + + 16:37 `` - DataSourceAzure: Adjust timeout for polling IMDS [Anh Vo] + + 16:37 `` - Azure: Changes to the Hyper-V KVP Reporter [Anh Vo] + + 16:37 `` - git tests: no longer show warning about safe yaml. + + 16:37 `` - tools/read-version: handle errors [Chad Miller] + + 16:37 `` - net/sysconfig: only indicate available on known sysconfig distros + + 16:37 `` (LP: \#1819994) + + 16:37 `` - packages: update rpm specs for new bash completion path + + 16:37 `` [Daniel Watkins] (LP: \#1825444) + + 16:37 `` - test_azure: mock util.SeLinuxGuard where needed + + 16:37 `` [Jason Zions (MSFT)] (LP: \#1825253) + + 16:37 `` - setup.py: install bash completion script in new location [Daniel Watkins] + + 16:37 `` - mount_cb: do not pass sync and rw options to mount + + 16:37 `` Launchpad bug 1819994 in Provider for Plainbox - Canonical Certification Server "cloud-init selects sysconfig netconfig renderer if network-manager is installed on Ubuntu" [Critical,Confirmed] [https://launchpad.net/bugs/1819994](https://launchpad.net/bugs/1819994) + + 16:37 `` [Gonéri Le Bouder] (LP: \#1645824) + + 16:37 `` - cc_apt_configure: fix typo in apt documentation [Dominic Schlegel] + + 16:37 `` - Revert "DataSource: move update_events from a class to an instance..." + + 16:37 `` [Daniel Watkins] + + 16:37 `` Launchpad bug 1825444 in cloud-init (Ubuntu) ""make rpm" fails on CentOS after commit 947d3c208" [Undecided,Fix released] [https://launchpad.net/bugs/1825444](https://launchpad.net/bugs/1825444) + + 16:37 `` - Change DataSourceNoCloud to ignore file system label's case. + + 16:37 `` [Risto Oikarinen] + + 16:38 `` Launchpad bug 1825253 in cloud-init "Unit tests with filesystem-related mocks fail in SeLinuxGuard when run on RHEL or CentOS" [Undecided,Fix released] [https://launchpad.net/bugs/1825253](https://launchpad.net/bugs/1825253) + + 16:38 `` Launchpad bug 1645824 in cloud-init "NoCloud source doesn't work on FreeBSD" [Medium,Fix released] [https://launchpad.net/bugs/1645824](https://launchpad.net/bugs/1645824) + + 16:38 `` - cmd:main.py: Fix missing 'modules-init' key in modes dict + + 16:38 `` [Antonio Romito] (LP: \#1815109) + + 16:38 `` - ubuntu_advantage: rewrite cloud-config module + + 16:38 `` - Azure: Treat _unset network configuration as if it were absent + + 16:38 `` [Jason Zions (MSFT)] (LP: \#1823084) + + 16:38 `` - DatasourceAzure: add additional logging for azure datasource [Anh Vo] + + 16:38 `` - cloud_tests: fix apt_pipelining test-cases + + 16:38 `` Launchpad bug 1815109 in cloud-init "cloud-final.service: "cloud-init modules --mode final" exit with "KeyError: 'modules-init'" after upgrade to version 18.2" [Medium,Fix released] [https://launchpad.net/bugs/1815109](https://launchpad.net/bugs/1815109) + + 16:38 `` - Azure: Ensure platform random_seed is always serializable as JSON. + + 16:38 `` [Jason Zions (MSFT)] + + 16:38 `` - net/sysconfig: write out SUSE-compatible IPv6 config [Robert Schweikert] + + 16:38 `` - tox: Update testenv for openSUSE Leap to 15.0 [Thomas Bechtold] + + 16:38 `` Launchpad bug 1823084 in cloud-init "DataSourceAzure doesn't rebuild network-config after reboot" [High,Fix released] [https://launchpad.net/bugs/1823084](https://launchpad.net/bugs/1823084) + + 16:38 `` - net: Fix ipv6 static routes when using eni renderer + + 16:38 `` [Raphael Glon] (LP: \#1818669) + + 16:38 `` Launchpad bug 1818669 in cloud-init "ipv6 static routes configured for eni are incorrect" [Undecided,Fix released] [https://launchpad.net/bugs/1818669](https://launchpad.net/bugs/1818669) + + 16:38 `` - Add ubuntu_drivers config module [Daniel Watkins] + + 16:38 `` - doc: Refresh Azure walinuxagent docs [Daniel Watkins] + + 16:38 `` - tox: bump pylint version to latest (2.3.1) [Daniel Watkins] + + 16:38 `` - DataSource: move update_events from a class to an instance attribute + + 16:38 `` [Daniel Watkins] (LP: \#1819913) + + 16:38 `` - net/sysconfig: Handle default route setup for dhcp configured NICs + + 16:38 `` [Robert Schweikert] (LP: \#1812117) + + 16:38 `` - DataSourceEc2: update RELEASE_BLOCKER to be more accurate + + 16:38 `` Launchpad bug 1819913 in cloud-init "cloud-init on xenial may generate network config on every boot" [Undecided,Fix released] [https://launchpad.net/bugs/1819913](https://launchpad.net/bugs/1819913) + + 16:38 `` [Daniel Watkins] + + 16:38 `` - cloud-init-per: POSIX sh does not support string subst, use sed + + 16:38 `` Launchpad bug 1812117 in cloud-init "route files are not written on SUSE distros" [Undecided,Fix released] [https://launchpad.net/bugs/1812117](https://launchpad.net/bugs/1812117) + + 16:38 `` (LP: \#1819222) + + 16:38 `` - Support locking user with usermod if passwd is not available. + + 16:38 `` Launchpad bug 1819222 in cloud-init "cloud-init-per no longer works due to bashisms" [Undecided,Fix released] [https://launchpad.net/bugs/1819222](https://launchpad.net/bugs/1819222) + + 16:38 `` - Example for Microsoft Azure data disk added. [Anton Olifir] + + 16:38 `` - clean: correctly determine the path for excluding seed directory + + 16:38 `` [Daniel Watkins] (LP: \#1818571) + + 16:38 `` - helpers/openstack: Treat unknown link types as physical + + 16:38 `` Launchpad bug 1818571 in cloud-init "cloud-init clean removes seed directory even when --seed is not specified" [High,Fix released] [https://launchpad.net/bugs/1818571](https://launchpad.net/bugs/1818571) + + 16:38 `` [Daniel Watkins] (LP: \#1639263) + + 16:38 `` Launchpad bug 1639263 in cloud-init " cloud-init Unknown network_data link type: macvtap" [Undecided,Fix released] [https://launchpad.net/bugs/1639263](https://launchpad.net/bugs/1639263) + + 16:38 `` - drop Python 2.6 support and our NIH version detection [Daniel Watkins] + + 16:38 `` - tip-pylint: Fix assignment-from-return-none errors + + 16:38 `` - net: append type:dhcp[46] only if dhcp[46] is True in v2 netconfig + + 16:38 `` [Kurt Stieger] (LP: \#1818032) + + 16:38 `` - cc_apt_pipelining: stop disabling pipelining by default + + 16:38 `` [Daniel Watkins] (LP: \#1794982) + + 16:38 `` - tests: fix some slow tests and some leaking state [Daniel Watkins] + + 16:38 `` Launchpad bug 1818032 in cloud-init "sysconfig renders BOOTPROTO=dhcp even if dhcp=false in v2 network-config" [High,Fix released] [https://launchpad.net/bugs/1818032](https://launchpad.net/bugs/1818032) + + 16:38 `` - util: don't determine string_types ourselves [Daniel Watkins] + + 16:38 `` Launchpad bug 1794982 in cloud-init "drop /etc/apt/apt.conf.d/90cloud-init-pipelining in 16.04+" [Medium,Fix released] [https://launchpad.net/bugs/1794982](https://launchpad.net/bugs/1794982) + + 16:39 `` Azure and SuSE and FreeBSD foks have been quite a bit of work and we have a number of other community contributors to thank this round + + 16:41 `` AnhVoMSFT: jasonzio (MSFT) and robjo (SuSE) thanks again for your efforts + + 16:43 `` Also, as you can see, Canonical added someone to our ranks for cloud-init development. Odd_Bloke is a permanent addition to our team and landing a lot of solid content for cloud-init. + + 16:43 `` welcome Dan! + + 16:43 `` thanks rharper Odd_Bloke powersj blackboxsw for all the reviewing and advice + + 16:44 `` From upstream side of the house, we have cut our first official upstream release of cloud-init. Version 19.1 sports 5 months of development, 24 contributors from 20 top-level domains. Details of that release are sent to our mailinglist and posted to the luanchpad milestone + + 16:44 `` \#link [https://launchpad.net/cloud-init/+milestone/19.1](https://launchpad.net/cloud-init/+milestone/19.1) + + 16:46 `` :) ! it's nice how involved your teams have been thanks again. + + 16:46 `` \#topic In-progress Development + + 16:47 `` So, for the upstream release of 19.1: Canonical has just started our SRU (Stable Release Update) process where we validate the upstream release before pushing it back into earlier Ubuntu series + + 16:47 `` We follow this upstream release process for Ubuntu + + 16:47 `` \#link [https://wiki.ubuntu.com/CloudinitUpdates](https://wiki.ubuntu.com/CloudinitUpdates) + + 16:48 `` I've queue to release branches for review as of Friday 05/10. I have queued Ubuntu Disco and published to disco-proposed pocket already. + + 16:48 `` So if someone deploys disco on your favorite cloud or hardware, you can add a disco-proposed apt source to /etc/apt/sources.list and you sound be able to install and or test 19.1 + + 16:49 `` I made the 19.1.1 SRU cut which included the commitish baa478546d8cac98a706010699d64f8c2f70b5bf which was the tip containing " Azure: Return static fallback address as if failed to find endpoint" as the last commit + + 16:49 `` so jasonzio's latest azure branch made it + + 16:50 `` expectation is that I'll get most of verification done over this week and we can hopefully (pending no SRU regressions discovered) publish to Xenial, Bionic, Cosmic and Disco the beginning of next week (05/20/2019) + + 16:51 `` I just added the following card to track this work, it'll move to DONE when published + + 16:51 `` \#link [https://trello.com/c/oxv61bPl/1099-sru-191-xenial-bionic-cosmic-and-disco](https://trello.com/c/oxv61bPl/1099-sru-191-xenial-bionic-cosmic-and-disco) + + 16:51 `` AnhVoMSFT, thank you for all your contributions + + 16:52 `` is there a package available publicly for 19.1 that we can download and apply it to existing images and run through our perf. regression test? + + 16:52 `` also today, we'll post 19.1 to our copr el-testing repo at + + 16:52 `` \#link [https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/](https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/) + + 16:52 `` for centos. + + 16:53 `` AnhVoMSFT, daily PPA: [https://launchpad.net/~cloud-init-dev/+archive/ubuntu/daily](https://launchpad.net/~cloud-init-dev/+archive/ubuntu/daily) + + 16:53 `` AnhVoMSFT: we have daily repos that + + 16:53 `` thx powersj + + 16:53 * powersj disappears + + 16:54 `` AnhVoMSFT, so that is built from tip of master (which currently contains exactly the same commit set as will be published to each series) + + 16:54 `` AnhVoMSFT: once the following branches are "merged" for each series, xenial-proposed, bionic-proposed, cosmic-proposed will also contain the final bits for each series + + 16:54 `` thanks powersj blackboxsw + + 16:55 `` \#link [https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367301](https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367301) + + 16:55 `` \#link [https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367302](https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367302) + + 16:55 `` \#link [https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367297](https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367297) + + 16:55 `` so when we land those, it should be a matter of an hour or so until ``-proposed is accessible to test those final packages + + 16:56 `` AnhVoMSFT: in the SRU process, we still will have to verify and test those bits before release. There is a tracking bug for the overall process here + + 16:56 `` \#link [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1828637](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1828637) + + 16:56 `` Ubuntu bug 1828637 in cloud-init (Ubuntu) "sru cloud-init (18.5-45 to 19.1.1) Xenial, Bionic, Cosmic, Disco" [Undecided,In progress] + + 16:56 `` ^ this but will go to fix released when we pass verification and publish the SRU + + 16:57 `` which will be promotion from xenial-proposed to xenial-updates for public availability on all images + + 16:57 `` again the estimate on this is probably next week for getting through testing + + 16:58 `` the rest of the cloud-init team is meeting this week for feature planning for the next cycle. But generally we will be tracking our ongoing work @ our public trello board + + 16:59 `` \#link [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + + 17:00 `` If there are there any features or significant gaps that people have interest in that we could try to put on our radar feel free to drop us a line here in channel or on the mailinglist @ cloud-init@lists.launchpad.net + + 17:01 `` I think that about wraps up current in-flight work + + 17:02 `` \#topic Office hours (next ~30 mins) + + 17:03 `` This section is allocated generally for folks to chat about any burning questions that we have. Bring your topics, bugs, feature requests, merge proposals or questions and we'll try getting some eyes or discussion on the + + 17:03 `` *them. + + 17:04 `` Generally we should have a couple cloud-init devs hanging out in channel during this time to help build momentum or unblock folks. Today may be a bit light in attendance due to a remote work trip a number of people are attending. + + 17:04 `` if our next work requires importing another module (python-dbus), are there any guidelines wrt to using additional python modules not currently part of cloudinit package? + + 17:06 `` AnhVoMSFT: generally adding new dependencies is something we try to avoid if possible due to impacting the minimal cloud images with additional dependencies. From ubuntu's perspective we tend to try to look at an ubuntu minimal image to see if the dependency is already there (and that makes things simple for the addition). + + 17:06 `` If new dependency is also something that can be optional instead of strict it makes adding that dependency easier. + + 17:06 `` For example: python-jsonschema is an optional package dependency + + 17:07 `` we bookend the imports in cloud-init with a try/except ImportError: pass and make sure that cloud-init still behaves if it is not there. + + 17:07 `` i will have to look into how to make it optional - certainly we can go that way if that makes thing easier + + 17:07 `` what we are looking at is how to get the kernel init timestamp and systemd init timestamp - both of these are available as KernelTimestamp and UserSpaceTimestamp that are available as part of the systemd's system dbus + + 17:07 `` This type of approach has been helpful in supporting Centos 6 where jsonschema wasn't available in stock images + + 17:08 `` normally you can get those info from "systemctl show", but the issue is systemctl internally use systemd's format_timestamp, which trims the precision down to "seconds" level. (format_timestamp_us would give us what we need) + + 17:11 `` AnhVoMSFT: interesting. since it seems like the dependency is one one or two values and not the full content of python-dbus library/modules I wonder if it might be better to see if those values are available in /proc or /sys somewhere as it might be fairly simple to instrument our own. (and avoid the time cost of importing larger python modules) + + 17:11 `` I guess if we really want to avoid another module, we can use os.stat to key off ctime of /proc and /proc/1 - however, the ctimes of /proc and /proc/1 are a bit earlier than the actual KernelTimestamp and UserSpaceTimestamp. They do have the advantage of being more widely available. Systemd and dbus might not exist on all distros + + 17:11 `` ... at least something to peek at to see if it is low hanging fruit that is easy to handle + + 17:12 `` Right, I would appreciate if someone with more knowledge on Linux systems can provide some advices here + + 17:12 `` the dependency is really on those values, and the dbus library seems a bit overkill for it + + 17:13 `` rharper: Odd_Bloke may have some thoughts on that too. but that conversation may have to wait a bit due to time difference. + + 17:14 `` AnhVoMSFT: again, what call/values would you like to make/get from python-dbus just for clarity + + 17:15 `` bus=dbus.SystemBus() systemd1=bus.get_object('org.freedesktop.systemd1','/org/freedesktop/systemd1') manager=dbus.Interface(systemd1, 'org.freedesktop.systemd1.Manager') props_iface=dbus.Interface(manager,'org.freedesktop.DBus.Properties') props_iface.Get('org.freedesktop.systemd1.Manager','KernelTimestamp') + + 17:15 `` oops - multiline didn't seem to go so well + + 17:15 `` it's all good thx + + 17:16 `` alternately, I support we could shell out via util.subp to make a cli call to handle that to avoid a python package dependency, but again it'd probably be better/faster to avoid that + + 17:17 `` right, we're trying to avoid adding more util.subp call (in fact we have a workitem to reduce the numbers of the existing util.subp call the Azure DS makes) + + 17:18 `` Like mentioned previously, we're looking at the /proc and /proc/1 ctime, they're cheap using the os.stat module and exist in all distros. + + 17:19 `` oops typo "alternatively , I support" /// I suppose + + 17:19 `` yeah that seems like the most non-contentious approach (processing /proc/1 ctime) + + 17:20 `` uncontentious rather + + 17:22 `` another thing we're looking at is cloud-init cloudtests so that we can have some azure cloud test running as part of cloud-init check-in gate + + 17:22 `` excellent! + + 17:23 `` if you guys have any pointers/tips on what it takes to enable cloud-tests please let us know + + 17:23 `` one of our team members will be looking at it + + 17:24 `` any blockers that you are aware of to date? Generally the biggest lift is getting the platform support added to the cloud-tests + + 17:25 `` I know powersj added more CI docs related to this a few months ago at + + 17:25 `` \#link [https://cloudinit.readthedocs.io/en/latest/topics/tests.html\#](https://cloudinit.readthedocs.io/en/latest/topics/tests.html\#) + + 17:25 `` I'll try to see if there was additional documentation tossed around + + 17:26 `` the benefit if Azure platform is added to cloud-init tip is that'd we would likely add some of that testing to our SRU verification process each release we are doing. I'm excited about that + + 17:27 `` right now, it's manual for Azure testing... per something like this [https://github.com/cloud-init/ubuntu-sru/blob/master/manual/azure-sru-18.5.21.txt](https://github.com/cloud-init/ubuntu-sru/blob/master/manual/azure-sru-18.5.21.txt) + + 17:27 `` I'm not aware of any blockers, we just barely started looking at it + + 17:27 `` these links are very helpful, I'll pass them along + + 17:28 `` the above script is tedious to write up, and only is really testing upgrade path and any *new* azure-specific bugs/features that are fixed in the current SRU, since most of the other integration testing covers general case + + 17:28 `` thanks AnhVoMSFT that's good to hear + + 17:29 `` are there any other topics folks have for today's meeting? Otherwise we can adjourn until next meeting + + 17:29 `` next meeting will be May 27th, same time + + 17:30 `` and I'll post status notes for the meeting to our github pages + + 17:30 `` \#link [https://cloud-init.github.io](https://cloud-init.github.io) + + 17:31 `` before I forget. let's get an action to followup on kernel/userspace timestamp discussion + + 17:31 `` thanks blackboxsw + + 17:32 `` \#action Odd_Bloke/rharper/AnhVoMSFT followup on recommended approach for getting kernel/userspace timestamp with or without python-dbus package dependency + + 17:32 * meetingology Odd_Bloke/rharper/AnhVoMSFT followup on recommended approach for getting kernel/userspace timestamp with or without python-dbus package dependency + + 17:32 `` thank you AnhVoMSFT + + 17:32 `` see folks next time, or anytime in channel + + 17:32 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2019-05-28.md b/content/status-2019-05-28.md new file mode 100644 index 0000000..7808027 --- /dev/null +++ b/content/status-2019-05-28.md @@ -0,0 +1,182 @@ +Title: Cloud-init bi-weekly status +Date: 2019-05-28 15:23:00 UTC +Category: status-meeting-minutes +Slug: status-2019-05-28 + +Meeting information +---------------- + * \#cloud-init: Cloud-init bi-weekly status, 28 May at 15:23 — 16:19 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-05-28-15.23.log.html](http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-05-28-15.23.log.html)]] + + + +Meeting summary +---------------- + +### Previous Actions +The discussion about "Previous Actions" started at 15:27. + + * **LINK**: [https://cloud-init.github.io/status-2019-05-13.html\#status-2019-05-13](https://cloud-init.github.io/status-2019-05-13.html\#status-2019-05-13) + +### Recent changes +The discussion about "Recent changes" started at 15:30. + + * **LINK**: [https://discourse.ubuntu.com/t/sru-of-cloud-init-19-1-released/11028/2](https://discourse.ubuntu.com/t/sru-of-cloud-init-19-1-released/11028/2) + * **LINK**: [https://lists.launchpad.net/cloud-init/msg00211.html](https://lists.launchpad.net/cloud-init/msg00211.html) + +### In-progress Development +The discussion about "In-progress Development" started at 15:41. + + * **LINK**: [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + +### Office hours (next ~30 mins) +The discussion about "Office hours (next ~30 mins)" started at 15:44. + + * **LINK**: [https://code.launchpad.net/cloud-init/+activereviews](https://code.launchpad.net/cloud-init/+activereviews) + * **LINK**: [https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082](https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082) + * **ACTION**: blackboxsw discuss with the team about landing the branch [https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082](https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082) + + + +Vote results +---------------- + + + + +Action items, by person +---------------- + + * blackboxsw + * blackboxsw discuss with the team about landing the branch [https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082](https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082) + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (44) + * meetingology (4) + * akik (2) + * ubot5 (2) + + + +Full Log +---------------- + + + 15:23 `` \#startmeeting Cloud-init bi-weekly status + + 15:23 `` Meeting started Tue May 28 15:23:50 2019 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 15:23 `` + + 15:23 `` Available commands: action commands idea info link nick + + 15:23 `` there we go + + 15:24 `` Hey folks, time for another bi-weekly cloud-init status. Welcome all! + + 15:25 `` Generally cloud-init upstream uses this meeting to provide a platform for status updates, raising questions or concerns and feature discussion. All are encouraged to participate as you see fit. + + 15:25 `` Generally the topics we would like to cover are the following: Previous Actions, Recent Changes, In-progress Development, Office Hours + + 15:26 `` without further ado let's jump into it. + + 15:27 `` \#topic Previous Actions + + 15:27 `` From our previous meeting minutes we had a couple of action items that I think are resolved + + 15:27 `` \#link [https://cloud-init.github.io/status-2019-05-13.html\#status-2019-05-13](https://cloud-init.github.io/status-2019-05-13.html\#status-2019-05-13) + + 15:28 * blackboxsw Odd_Bloke confirm correct status of [https://bugs.launchpad.net/cloud-init/+bug/1801364](https://bugs.launchpad.net/cloud-init/+bug/1801364) + + 15:28 `` Launchpad bug 1801364 in cloud-init "persisting OpenStack metadata fails" [Undecided,Confirmed] + + 15:28 `` Dan confirmed that this is the proper bug status and still needs a fix + + 15:28 `` AnhVoMSFT: we had an action related to you "followup on recommended approach for getting kernel/userspace timestamp with or without python-dbus package dependency" + + 15:29 `` I know rharper had a comment or two in channel about this approach. Hopefully AnhVoMSFT you have everything you need there + + 15:29 `` if not, you can feel free to ping us for more discussion on that feature + + 15:30 `` \#topic Recent changes + + 15:31 `` Big news since last bi-weekly status meeting is that we have completed and published 19.1.1 in an SRU into Ubuntu Xenial, Bionic, Cosmic and Disco as of yesterday. + + 15:31 `` Odd_Bloke: wrote up some content and email around this for more context. Thanks Odd_Bloke + + 15:32 `` \#link [https://discourse.ubuntu.com/t/sru-of-cloud-init-19-1-released/11028/2](https://discourse.ubuntu.com/t/sru-of-cloud-init-19-1-released/11028/2) + + 15:33 `` \#link [https://lists.launchpad.net/cloud-init/msg00211.html](https://lists.launchpad.net/cloud-init/msg00211.html) + + 15:38 `` beyond that we have the following upstream commits landed + + 15:39 `` d9b1e5de91..HEAD | log2dch + + 15:39 `` - freebsd: NoCloud data source support [Gonéri Le Bouder] (LP: \#1645824) + + 15:39 `` - Azure: Return static fallback address as if failed to find endpoint + + 15:39 `` [Jason Zions (MSFT)] + + 15:39 `` Launchpad bug 1645824 in cloud-init "NoCloud source doesn't work on FreeBSD" [Medium,Fix committed] [https://launchpad.net/bugs/1645824](https://launchpad.net/bugs/1645824) + + 15:40 `` Thanks again Jason and Gonéri for the commits there. We have a few branches in the wings under review for freebsd and azure that I expect will be landing this week + + 15:41 `` \#topic In-progress Development + + 15:42 `` \#link [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + + 15:43 `` Our upcoming work is set and scheduled on this trello board above. As we grab new significant tasks and dev work for cloud-init we will pull those cards into the doing lane + + 15:44 `` \#topic Office hours (next ~30 mins) + + 15:45 `` This topic is an opportunity for anyone to bring their bugs, features, questions or branches to get some extra eyes or discussion around current development. + + 15:47 `` It is also a slot of time where upstream developers will be spending some time reviewing active branches to unblock community members and help increase velocity of our review queue. + + 15:47 `` \#link [https://code.launchpad.net/cloud-init/+activereviews](https://code.launchpad.net/cloud-init/+activereviews) + + 15:48 * blackboxsw does as review pass on [https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/367315.](https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/367315.) I'm grabbing an active review slot for this now + + 15:52 `` ls + + 15:52 `` sorry + + 16:03 `` yeah this looks good Goneri [https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/367315...](https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/367315...) approved + + 16:03 `` will merge in ~15 + + 16:13 `` smoser: so sorry on the review delay here for the doc change you took over. [https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/343546](https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/343546) + + 16:14 `` just approved with a nit if you are around to push that. if not, I'll get that doc branch merged in tomorrow + + 16:16 `` I think that about wraps this status meeting this week. I think we should take an action to talk about we want to do with this old branch. + + 16:16 `` \#link [https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082](https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082) + + 16:16 `` \#action blackboxsw discuss with the team about landing the branch [https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082](https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082) + + 16:16 * meetingology blackboxsw discuss with the team about landing the branch [https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082](https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082) + + 16:18 `` We'll hold the next cloud-init status meeting on Monday 3/10 + + 16:19 `` and I'll post the status minutes up to [https://cloud-init.github.io](https://cloud-init.github.io) momentarily + + 16:19 `` Thanks again. have a good one guys and gals. + + 16:19 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2019-06-10.md b/content/status-2019-06-10.md new file mode 100644 index 0000000..d9d8023 --- /dev/null +++ b/content/status-2019-06-10.md @@ -0,0 +1,345 @@ +Title: Cloud-init bi-weekly status +Date: 2019-06-10 16:19:00 UTC +Category: status-meeting-minutes +Slug: status-2019-06-10 + +Meeting information +---------------- + * \#cloud-init: Cloud-init bi-weekly status, 10 Jun at 16:19 — 17:31 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-06-10-16.19.log.html](http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-06-10-16.19.log.html)]] + + + +Meeting summary +---------------- + + **LINK**: [https://cloud-init.github.io](https://cloud-init.github.io) +### Previous Actions +The discussion about "Previous Actions" started at 16:23. + + +### Recent Changes +The discussion about "Recent Changes" started at 16:24. + + * **LINK**: [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + +### In Progress Development +The discussion about "In Progress Development" started at 16:30. + + * **LINK**: [https://code.launchpad.net/cloud-init/+activereviews](https://code.launchpad.net/cloud-init/+activereviews) + +### Office Hours +The discussion about "Office Hours" started at 16:45. + + +### Office Hours (next ~30 mins) +The discussion about "Office Hours (next ~30 mins)" started at 16:48. + + * **LINK**: [https://netplan.io/faq\#how-to-go-back-to-ifupdown](https://netplan.io/faq\#how-to-go-back-to-ifupdown) + * **ACTION**: follow up any bugs related to Azure/netplan uninstall in favor ifupdown to see if cloud-init has actionable feature work to ensure proper network renderer is used + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (39) + * rharper (39) + * AnhVoMSFT (29) + * cyphermox (12) + * robjo (6) + * meetingology (4) + * ubot5 (3) + * paride (1) + * Odd_Bloke (1) + + + +Full Log +---------------- + + + 16:19 `` \#startmeeting Cloud-init bi-weekly status + + 16:19 `` Meeting started Mon Jun 10 16:19:45 2019 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:19 `` + + 16:19 `` Available commands: action commands idea info link nick + + 16:19 `` o/ + + 16:20 `` o/ + + 16:20 `` hi cloud-init folks. let's kick off the bi-weekly meeting again + + 16:21 `` our last meeting minutes are hosted on github + + 16:21 `` \#link [https://cloud-init.github.io](https://cloud-init.github.io) + + 16:22 `` welcome all. Generally cloud-init upstream uses this meeting to provide a platform for status updates, raising questions or concerns and feature discussion. All are encouraged to participate as you see fit. + + 16:22 `` our format is the following topics: Previous Actions, Recent Changes, In-progress Development, Office Hours + + 16:23 `` interjections and additional topics are welcome + + 16:23 `` \#topic Previous Actions + + 16:24 `` Checking last meeting's minutes we were clear of old actions. + + 16:24 `` so we'll jump to the next topic this week. + + 16:24 `` \#topic Recent Changes + + 16:26 `` the following commits landedd in cloud-init tip since the last status meeting + + 16:26 `` - Allow identification of OpenStack by Asset Tag + + 16:26 `` [Mark T. Voelker] ([LP: \#1669875]([https://bugs.launchpad.net/bugs/1669875](https://bugs.launchpad.net/bugs/1669875))) + + 16:26 `` - Fix spelling error making 'an Ubuntu' consistent. [Brian Murray] + + 16:26 `` - run-container: centos: comment out the repo mirrorlist [Paride Legovini] + + 16:26 `` - netplan: update netplan key mappings for gratuitous-arp + + 16:26 `` [Ryan Harper] ([LP: \#1827238]([https://bugs.launchpad.net/bugs/1827238](https://bugs.launchpad.net/bugs/1827238))) + + 16:26 `` Launchpad bug 1669875 in OpenStack Compute (nova) "identify openstack vmware platform" [Wishlist,Confirmed] + + 16:26 `` Launchpad bug 1827238 in cloud-init "Machines fail to deploy because cloud-init needs to accept both netplan spellings for grat arp" [Medium,Fix committed] + + 16:30 `` I was poking around out trello board to see if we've moved other cloud-init related content into the done lane, but I think those commits about capture the recent work + + 16:30 `` \#link [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + + 16:30 `` \#topic In Progress Development + + 16:31 `` our active reviews are located here (as mentioned in the topic) + + 16:31 `` \#link [https://code.launchpad.net/cloud-init/+activereviews](https://code.launchpad.net/cloud-init/+activereviews) + + 16:32 `` Goneri: thanks for all the work on freebsd branches, there has been some good momentum there + + 16:32 `` there is ongoing work from Azure datasource that will likely land in the next week or two + + 16:33 `` ^^ "run-container: centos: comment out the repo mirrorlist", only actually relevent when using an http/https proxy, in all the other cases the mirrorlist works as usual + + 16:33 `` and some network-related changes landing shortly + + 16:33 `` paride: thank you paride for the extra note + + 16:33 `` blackboxsw can you share more details on the work from Azure datasource ? Any bug that we can reference? + + 16:33 `` I was thinking [https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/364012](https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/364012) AnhVoMSFT + + 16:35 `` related to sorting out covering the all the network related scenarios so that we configure network in a way that ensures access to IMDS and internet in the face of additional static ips on the same subnet as the primary interface, multiple dhcp interfaces with default routes, + + 16:35 `` I see - I think there potentially needs some bigger change there, as there was some issue around identifying the primary/secondary NIC. We got confirmation from our netwoking team that the first NIC returned is the primary + + 16:35 `` AnhVoMSFT: good to know; that was our observation + + 16:36 `` AnhVoMSFT: [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1815254](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1815254) , related as well; the plan being to put in place some source-based routing; + + 16:36 `` Launchpad bug 1815254 in cloud-init (Ubuntu) "Azure multiple ips prevent access to metadata service" [Undecided,Confirmed] + + 16:38 `` thanks rharper - is that something that should be changed/fixed from cloudinit, or is this more platform related? + + 16:38 `` that's a good question; generally it would be *great* if a platform were to include source-routes and metrics in the config they send + + 16:38 `` if the latter I will file a workitem on our side to go do some research and get the right team to take a look at it + + 16:39 `` currently no cloud does this, rather *some* indicate a *primary* via metadata, and then the OS scripts apply a metric to all non-primary routes to ensure that default routes go to the primary + + 16:39 `` I see - so I guess we can do similarly on Azure since we know what the primary is (first nic returned in IMDS) + + 16:40 `` AnhVoMSFT: so in the short term, I think cloud-init should (where possible with the OS network config) provide additional tuning (likely post-scripts in some cases) to tune the routing for what cloud-init knows is the primary route + + 16:40 `` AnhVoMSFT: yes, I prefer a primary=True or whatever, but it's good enough to have the current behavior documented (in the code) + + 16:40 `` thanks rharper + + 16:40 `` so if it change/breaks, then we know + + 16:44 `` I think that covers our in-progress items for the moment + + 16:45 `` not sure if the bot will listen to me, but just in case + + 16:45 `` Be mindful that in Azure the metadata service may lag behind by minutes w.r.t. secondary IPs on an interface + + 16:45 `` \#topic Office Hours + + 16:45 `` robjo: in general, my awareness is that the instance has to be off line to change vnets and such; and booting back up has been enough time to see IMDS updated, do you see differently ? + + 16:46 `` robjo that is good to know, I will check on that + + 16:46 `` We've had various issues with cloud-netconfig due to the metadata server in Azure being slow and reverted to polling, which of course got us in trouble with API rate limits + + 16:46 `` robjo: interesting + + 16:47 `` We'll here in channel so if youve;; got merges or bugs that need an eye or just questions, fire away + + 16:47 `` robjo feel free to file a bug on that and we will investigate - IMDS is our partner team so we'll get some answer quickly there + + 16:48 `` rharper, a couple things I want to ask for Office Hours + + 16:48 `` AnhVoMSFT: We have been working with Stephen Zarkos on the issues + + 16:48 `` \#topic Office Hours (next ~30 mins) + + 16:48 `` robjo I will ping Stephen and get more detail and see if we have any follow up items + + 16:48 `` sorry folks got pulled away for a bit thx rharper + + 16:48 `` And double checked that the polling direction was OK form the Microsoft perspective before we implemented that + + 16:49 `` I see, glad you're not blocked on it + + 16:50 `` rharper: We always had bug reports that upon reboot not everything was always configured when secondary IP addresses were in play. But theoretically yes upon reboot everything should be there + + 16:50 `` rharper we have a customer who booted up a VM based on 18.04, which uses netplan. Cloudinit wrote a netplan file to the image. He then installed ifupdown, then had some networking change which triggered a mac address change. Upon rebooting, cloudinit tries to use eni, but netplan file was still there, which caused his VM to mess up the network config + + 16:50 `` putting cloud-netconfig into polling mode pretty mush addresses the issues we had reports about + + 16:51 `` AnhVoMSFT: yes; that sounds very likely + + 16:51 `` AnhVoMSFT: did they file a bug? + + 16:51 `` cloud-init net "detects" which service is present + + 16:51 `` I'm checking to see if this should be a bug, or that is expected behavior + + 16:51 `` so if they did not uninstall netplan.io then cloud-init will likely prefer that over eni + + 16:52 `` cloudinit actually prefers eni if ifupdown is installed, I think + + 16:52 `` AnhVoMSFT: so the etc/netplan/*.yaml would only trigger things if netplan is still present; the systemd-generator will read yaml and write out networkd files + + 16:53 `` right, I think the customer's mistake was to not uninstall netplan (or remove any netplan configuration file) after installing ifupdown + + 16:53 `` AnhVoMSFT: right; I think we'll need to see the log and system state, but it sounds like an incomplete uninstall of netplan + + 16:53 `` uninstall of netplan should be enough to make the cloud-init.yaml inert + + 16:54 `` [https://netplan.io/faq\#how-to-go-back-to-ifupdown](https://netplan.io/faq\#how-to-go-back-to-ifupdown) + + 16:54 `` AnhVoMSFT: it *should* have automatically uninstall netplan.io + + 16:54 `` I'm not sure if there is much we can do from the cloudinit side - perhaps if choosing eni, disable the cloud-init netplan yaml + + 16:54 `` AnhVoMSFT: well, we could check writable paths of the renderers + + 16:54 `` rharper I don't think that is the behavior on 18.04 - installing ifupdown will not uninstall netplan + + 16:55 `` AnhVoMSFT: you're right; =( + + 16:55 `` that sort of feels like a bug in the packaging + + 16:55 `` yes, I share the same sentiment + + 16:56 `` I will go ahead and file a bug so even if we don't have a short term action we can still capture the discussion + + 16:57 `` AnhVoMSFT: thanks, I'm pinging in \#netplan and the bug will be great so we can figure out the right plan + + 16:59 `` second question: We have an intern working in our team and as part of warming up in cloudinit he wrote some additional capabilities into cloud-init analyze, adding a "boot" module (in addition to show/blame/dump), which collects timestamps of phases happening during vm booting up, but before cloudinit started, such as kernel initialization, systemd initialization.. + + 17:00 `` this should work for all cloud (he tested in AWE/GCP). Currently only works for distros that uses systemd. He'll try to figure out how to get those counters for freebsd and others + + 17:00 `` rharper since you were the original author of analyze, I'm trying to gauge the interest on this and we're open to suggestions/questions + + 17:01 `` rharper: they can coexist and configure each their own interface, so it's not a conflict. It's no different than coexisting ifupdown and NetworkManager, or also NetworkManager and systemd-networkd + + 17:01 `` AnhVoMSFT: that sounds excellent + + 17:01 `` nice AnhVoMSFT on the commandline extensions! + + 17:01 `` AnhVoMSFT: happy to review branch or Work-in-Progress when it's available + + 17:02 `` thanks rharper blackboxsw we will have that in a branch very soon. + + 17:03 `` cyphermox if that is the case then either the customer or cloudinit needs to make sure the system does not have conflicting configuration for netplan/eni. + + 17:03 `` cyphermox: ok; would you be open to some sort of warning about having config in both or something? I dunno; it's just not a great experience to add the new package, configure it, reboot and not have networking since the same interface was configured (differenlty) in both packages + + 17:03 `` yeah, I'm quite intterested in any additional cli functionality that cloud-init more versatile as a system debug tool + + 17:04 `` *makes cloud-init more versatile* + + 17:04 `` rharper: I'm not opposed to a warning, but that's not necessarily better UX. + + 17:05 `` debconf prompts are quite annoying to have at upgrade, and just writing it out people are likely to miss it altogether + + 17:05 `` (so you wouldn't really gain much) + + 17:05 `` blackboxsw yep that was the goal - we want to be able to deploy 1000 VMs, then use cloud-init analyze output to analyze the 50th/99th percentile of where the timing was spent during system boot, and we need some more insights into phases before cloud-init started as well + + 17:05 `` cyphermox: agreed; having a pointer to suggest cleaning/checking/confirming configs if /etc/netplan/ is non-empty and netplan.io is installed + + 17:06 `` rharper: one option is to parse enough of /etc/network/ to catch mentions of the interface, but that's not necessarily super solid (though it's the best option), because people can rename interfaces in netplan and match by mac + + 17:06 `` might be helpful; though I agree that they may still ignore that; and cloud-init could do some more work to see if an image has multiple renderers available and ensure it didn't leave config for a previous boot around + + 17:07 `` cyphermox: yeah; cloud-init knows more about the config and both formats; we're likely in a better spot to see "you've configured this interface twice" + + 17:08 `` rharper: so in short, I'm not opposed to improving the UX, but I'm not wowed by any solution right now (even mine) + + 17:09 `` cyphermox: that's fair; thanks + + 17:09 `` i think a fix in cloudinit might make most stakeholders happy here. It knows which configuration file it wrote, so it can definitely look for conflicting configurations + + 17:09 `` cyphermox: AnhVoMSFT is going to file the customer bug with details and we can discuss what (if any) improvements are to be made; I suspect cloud-init can help most here + + 17:09 `` yes, I think so too + + 17:09 `` cyphermox: thanks for the input + + 17:09 `` it can't be responsible for everything the customer does though. If customer writes some my-own-netplan.yml, we can't help much + + 17:10 `` rharper: but hey, if someone was to write a check when running netplan apply that there exists config in /etc/network, I wouldn't have much issues merging it + + 17:10 `` AnhVoMSFT: right, we have several "maybe_delete_if" where we verify expected output before we remove things + + 17:10 `` I just know I won't have time to look into this myself in the near future + + 17:10 `` cyphermox: ack + + 17:11 `` I think what will help most is aggressively deprecating and removing ifupdown + + 17:13 `` that said, the best we can realistically do for the time being is to demote it to universe + + 17:13 `` (and that's not going to change anything for UX) + + 17:15 `` we had another instance of someone installing ifupdown2, which had the effect of removing cloud-init on debian/ubuntu 16.04 + + 17:16 `` and totally hosed his system, but that's a different issue altogether + + 17:26 `` s + + 17:27 `` thanks for the good discussion folks, I guess we'll just add an action item to followup on a netplan bug for next time to see where we are at + + 17:31 `` \#action follow up any bugs related to Azure/netplan uninstall in favor ifupdown to see if cloud-init has actionable feature work to ensure proper network renderer is used + + 17:31 * meetingology follow up any bugs related to Azure/netplan uninstall in favor ifupdown to see if cloud-init has actionable feature work to ensure proper network renderer is used + + 17:31 `` ok, I'll post minutes on this. thank you again rharper for driving + + 17:31 `` and for the participation robjo cyphermox and AnhVoMSFT + + 17:31 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2019-06-24.md b/content/status-2019-06-24.md new file mode 100644 index 0000000..23191fb --- /dev/null +++ b/content/status-2019-06-24.md @@ -0,0 +1,344 @@ +Title: Cloud-init bi-weekly status +Date: 2019-06-24 16:18:00 UTC +Category: status-meeting-minutes +Slug: status-2019-06-24 + +Meeting information +---------------- + * \#cloud-init: Cloud-init bi-weekly status, 24 Jun at 16:18 — 17:33 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-06-24-16.18.log.html](http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-06-24-16.18.log.html)]] + + + +Meeting summary +---------------- + +### Previous Actions +The discussion about "Previous Actions" started at 16:23. + + * **LINK**: [https://cloud-init.github.io/status-2019-06-10.html\#status-2019-06-10](https://cloud-init.github.io/status-2019-06-10.html\#status-2019-06-10) + * **LINK**: [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381) + * **ACTION**: Touch base with AnhVoMSFT by next status on priority of [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381) + +### Recent Changes +The discussion about "Recent Changes" started at 16:28. + + +### In Progress Development +The discussion about "In Progress Development" started at 16:31. + + * **LINK**: [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + * **LINK**: [https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/feature/disk_setup_async](https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/feature/disk_setup_async) is the WIP branch + * **LINK**: [https://trello.com/c/TMK5ZDMf/1108-azure-async-disk-mounts](https://trello.com/c/TMK5ZDMf/1108-azure-async-disk-mounts) + * **LINK**: [https://cloud-init.github.io](https://cloud-init.github.io) + + + +Vote results +---------------- + + + + +Action items, by person +---------------- + + * AnhVoMSFT + * Touch base with AnhVoMSFT by next status on priority of [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381) + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (73) + * rharper (23) + * AnhVoMSFT (18) + * nik736 (12) + * ubot5 (4) + * meetingology (4) + + + +Full Log +---------------- + + + 16:18 `` \#startmeeting Cloud-init bi-weekly status + + 16:18 `` Meeting started Mon Jun 24 16:18:34 2019 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:18 `` + + 16:18 `` Available commands: action commands idea info link nick + + 16:19 `` welcome to another episode of cloud-init status updates. + + 16:20 `` 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. + + 16:21 `` our format is the following topics: Previous Actions, Recent Changes, In-progress Development, Office Hours + + 16:21 `` anyone is welcome to participate, interject, make suggestions or ask questions + + 16:22 `` generally we try to host this meeting every two weeks on the day listed in the channel topic + + 16:23 `` \#topic Previous Actions + + 16:23 `` last meeting + + 16:23 `` \#link [https://cloud-init.github.io/status-2019-06-10.html\#status-2019-06-10](https://cloud-init.github.io/status-2019-06-10.html\#status-2019-06-10) + + 16:24 `` we had an action to follow up on any bugs related to installing ifupdown on a system that had netplan installed by default. + + 16:24 `` I believe we did see a bug come in from Azure about that.... checking for that bug id now + + 16:25 `` \#1832381 + + 16:25 `` bug \#1832381 + + 16:25 `` bug 1832381 in cloud-init (Ubuntu) "vm fails to boot due to conflicting network configuration when user switches from netplan to eni" [Undecided,Incomplete] [https://launchpad.net/bugs/1832381](https://launchpad.net/bugs/1832381) + + 16:25 `` \#link [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381) + + 16:25 `` There is an action item on me to attach a log to that bug. Since the incident created by the customer was closed and we did not have permission to share his log, I will need to get a repro and retrieve the log. It's not very easy to trigger a mac address change in Azure these days + + 16:25 `` thanks AnhVoMSFT for this bug + + 16:27 `` ok if we carry over that action item then for next status meeting AnhVoMSFT (just to close the loop if it's important) + + 16:27 `` yep - once I get some help from our networking folks to trigger a mac address change I'll update the bug with more logs + + 16:27 `` \#action Touch base with AnhVoMSFT by next status on priority of [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381) + + 16:27 * meetingology Touch base with AnhVoMSFT by next status on priority of [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381) + + 16:27 `` Ubuntu bug 1832381 in cloud-init (Ubuntu) "vm fails to boot due to conflicting network configuration when user switches from netplan to eni" [Undecided,Incomplete] + + 16:28 `` good deal. that's all we had for actions from last meeting + + 16:28 `` \#topic Recent Changes + + 16:29 `` the following items have landed on tip of cloud-init's master branch + + 16:30 `` - sysconfig: support more bonding options [Penghui Liao] + + 16:30 `` - cloud-init-generator: use libexec path to ds-identify on redhat systems + + 16:30 `` [Ryan Harper] ([LP: \#1833264]([https://bugs.launchpad.net/bugs/1833264](https://bugs.launchpad.net/bugs/1833264))) + + 16:30 `` - tools/build-on-freebsd: update to python3 [Gonéri Le Bouder] + + 16:30 `` Ubuntu bug 1833264 in cloud-init "cloud-init-generator hardcodes path to ds-identify" [Undecided,Fix committed] + + 16:30 `` thanks to Penghui and Gonéri for driving additional changes for cloud-init in this last sessions + + 16:30 `` session* + + 16:31 `` \#topic In Progress Development + + 16:32 `` there a number of longer items for feature work in progress that should see some light soon + + 16:33 `` We track these features in trello as always + + 16:33 `` \#link [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + + 16:33 `` minor fixup for Azure instance-data.json (cloud-init query) for region and availability zone should land today + + 16:34 `` rharper: and blackboxsw are working on Azure-related route tables and async disk mount features + + 16:36 `` is there any bug/discussion item for the async disk mount? + + 16:37 `` AnhVoMSFT: rharper has been testing out systemd unit magic for setting up disk mounts async and initial numbers look good. How to bake that work into cloud-init is the next small hurdle I think. (I thought he mentioned today in our standup a 50% speed increase due to async mounts instead of sync waits) + + 16:38 `` [https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/feature/disk_setup_async](https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/feature/disk_setup_async) is the WIP branch + + 16:39 `` AnhVoMSFT: I expect we'll have something in the next couple of days. + + 16:39 `` orrr right now. thanx rharper + + 16:39 `` that sounds really cool. I'll check it out + + 16:39 * blackboxsw creates a trello card that can be watched for this feature + + 16:40 `` \#link [https://trello.com/c/TMK5ZDMf/1108-azure-async-disk-mounts](https://trello.com/c/TMK5ZDMf/1108-azure-async-disk-mounts) + + 16:41 `` feel free to subscribe to any trello cards folks see that are of interest. you will get an email if the card changes state, like from Doing to Done or if new links are added + + 16:42 `` Odd_Bloke: rharper process question + + 16:42 `` what do you guys think about us turning on voting on trello cards + + 16:42 `` people with interest on a feature/card in our backlog could upvote it and that *could* help drive what features we grab over time + + 16:43 `` dunno, thought it might be something we could toss around to see if that would make sense. the board it public after all + + 16:43 `` *is public* rather + + 16:43 `` maybe; I worry about random +1 without any more context. Platform developers already work with us; and community folks file bugs/merge proposals + + 16:44 `` good point. + + 16:44 `` I'm open to the idea + + 16:45 `` for sure, if it gets interest, we can think about adding that feature. can't hurt to have some additional input, unfounded though it may be. + + 16:45 `` agreed on the usefulness might be limited. You guys are already talking to each other. Platform developers either engage directly on this board or through out of band channel (sync meeting with Canonical product groups, etc...) + + 16:46 `` Perhaps you can try it out for a couple release periods and see how it works out + + 16:46 `` yeah, /me just likes all the shiny objects pretty icons ;) ... need to control myself + + 16:47 `` thx AnhVoMSFT +1. + + 16:48 `` so I think that about wraps in-progress development. I know paride has been tirelessly working on our CI infrastructure to improve quality of CI and false positives for failures due to resource constraints. So big thanks for paride working on our jenkins workers + + 16:48 `` \#topic Office Hours (next ~30 mins) + + 16:49 `` This is an open topic to bring any cloud-init discussions, bugs, concerns or feature requests folks have. + + 16:49 `` In the absence of such topics we spend part of this time grooming the review queue to get back to dev + + 16:50 `` contributors so that they don't have stale branches waiting for input + + 16:50 `` We had a review sent out to add some boot time telemetry collection as part of cloud-init analyze: [https://code.launchpad.net/~samgilson/cloud-init/+git/cloud-init/+merge/368943](https://code.launchpad.net/~samgilson/cloud-init/+git/cloud-init/+merge/368943) + + 16:50 `` thanks AnhVoMSFT I'll grab a review slot on that one now + + 16:51 `` would appreciate some reviews there and also on ideas on how to retrieve similar timestamps for FreeBSD + + 16:51 `` AnhVoMSFT: yes, will review + + 16:51 `` AnhVoMSFT: also, I filed a bug related to the azure telemetry, lemme get it + + 16:51 `` I'll kick off a CI run on that now + + 16:51 `` rharper: ^ + + 16:52 `` Bug 1833731 + + 16:52 `` bug 1833731 in cloud-init "cloud-init analyze output not formatted cleanly on Azure" [Undecided,New] [https://launchpad.net/bugs/1833731](https://launchpad.net/bugs/1833731) + + 16:52 `` AnhVoMSFT: not sure if the branch for review addresses the formatting of the output, but we should take a look to clean it up + + 16:52 `` is there a good way to subscribe to new bugs with a certain keyword/tags? I.e., I would like to auto-subscribe to all bugs that has "Azure" in the bug title + + 16:52 `` rharper: if you get a chance to double check [https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/369199](https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/369199) we might be able to land that too + + 16:53 `` blackboxsw: I asked you some questions, if you've replied, I'll look again + + 16:53 `` rharper: nevermind, I see you already looked at it + + 16:53 `` ah + + 16:53 `` perfect + + 16:53 `` thanks + + 16:53 `` I think we're mostly fine; just a question on return values + + 16:53 * blackboxsw needed to refresh + + 16:54 `` rharper I will take a look at the analyze output and see how we can improve it. If it is a minor change we can add it to the existing review + + 16:54 `` AnhVoMSFT: no need to pull it into the existing stuff + + 16:55 `` I'd prefer a separate targetted fix; which may land independently from the boot stage (which is super interesting on its own) + + 16:55 `` cool - we will do a separate fix then + + 16:55 `` rharper: yeah that concern is clear, we are safe on the processing of region/az in absence of 'imds' key + + 16:55 `` it'll return none + + 16:57 `` by virtue of that last get('location|platformFaultDomain') + + 16:57 `` if either is absent due to any key above being absent, you'll get None as default value + + 16:58 `` blackboxsw: ack + + 17:00 `` Hi there, not sure if this is the right place to ask, but I have problems when creating a new VM, it only happens with the debian cloud image, ubuntu is fine. Booting is stuck at the drm line, the exact line is dependent on the video model type in my libvirt xml but it is basically stuck for 20-30sec and won't continue. It will boot eventually after that time. Thanks so much for any hints. Happy to provide + + 17:00 `` further details. + + 17:02 `` hrm, video model timeouts are a bit out of my wheelhouse :/ + + 17:02 * blackboxsw pokes around a bit in google + + 17:02 `` it seems to be that the lines after it would be about resizing the file system. I am not really sure if this is cloud-init related at all and I am not sure if it actually is caused by the video model or is just taking a bit to get to the next steps + + 17:03 `` nik736: you can run cloud-init analyze show or cloud-init analyze blame to see what cloud-init says it is spending a lot of time on + + 17:03 `` I tried different host systems, Debian 18.04, 19.04, Debian 9, different libvirt versions, different qemu versions, nothing seems to be helping lol + + 17:03 `` (If you have cloud-init v 18 or later in your image I think) + + 17:04 `` ah, ok, thanks, I will look into that + + 17:04 `` nik736: also systemd-analyze blame is a good helper for what is killing boot time + + 17:04 `` do you see any timestamp gap that reflects the 20-30s in cloud-init.log ? + + 17:08 `` nik736: feel free to file a bug and attach logs from the 'cloud-init collect-logs' output (or serial console if available) and /var/log/cloud-init.log if you can get into the instance afterwards + + 17:08 `` thanks for the help, currently looking into it + + 17:11 `` rharper blackboxsw we have some instance deployment where cloud-init is hanging at the command ip route add - any idea how to look further? + + 17:12 `` this does look like a platform problem, so it is more of a question related to networking, rather than cloud-init itself + + 17:14 `` it's super hard to reproduce so the only thing we have so far to work with is logs. I thought the call to ip route add basically adds an entry to the kernel routing table. Is there an interaction with networking involved which might cause it to hang? + + 17:14 `` AnhVoMSFT: I wonder if it's creating a route that breaks connection to IMDS or something else that cloud-init would then do an HTTP get on ? + + 17:17 `` I saw in the log that 2 entries are around 1 minute apart "SUCCESS: searching for local datasources" and "Cloud-init v. 0.7.9 running 'init' at Mon, 24 Jun 2019 17:13:41 +0000. Up 73.67 seconds." I am not sure if this could be it or if this looks fine + + 17:18 `` 0.7.9 is quite old, seeing the full cloud-init.log will be most useful for us to understand what's happening + + 17:19 `` okay, sec + + 17:19 `` rharper that is a good theory. I do see in a good case there's a call to IMDS immediately after that, although that call has a timeout. If it fails we should see more logs coming out of cloud-init. I'll look further into that todya + + 17:20 `` @rharper [https://pastebin.com/fzCSH5kC](https://pastebin.com/fzCSH5kC) + + 17:20 `` AnhVoMSFT: the retry logic in DataSourceAzure is quite long IIRC, so it's quite possible this is the very issue that blackboxsw is working w.r.t ensuring the instances always have a source-ip route to the IMDS + + 17:21 `` rharper indeed it is long, and the log was overly suppressed to avoid log from growing too large while VM was waiting in pre-provisioning state. We are adding back some of the logs (in a smarter way to get enough details while avoiding huge log size) + + 17:22 `` nik736: so, between line 260 and 261 there's a large timedelta; that's *outside* of cloud-init; cloud-init is executed separately 4 times (cloud-init init --local, cloud-init init, cloud-init config --modules, cloud-init config --final) + + 17:23 `` nik736: so if you have a systemd journal, we could see what happens between the end of cloud-init-local.service and cloud-init.service (stage1 and 2); + + 17:23 `` ah, okay, interesting + + 17:23 `` will check + + 17:23 `` or syslog might see stuff between those two time points + + 17:23 * rharper steps away for a bit, please keep sending info here; I'll respond when I;m back + + 17:24 `` nik736 systemd-analyze critical-chain cloud-init.service might help here - I think some systemd service is running right after init-local and just before init and that service is taking time + + 17:25 `` will check, thanks for your help, really appreciate it. + + 17:32 `` I think I'll wrap the meeting here, but we can continue the conversation. Thanks again folks for the discussions + + 17:33 `` next meeting will be July 8th + + 17:33 `` as updated in the topic + + 17:33 `` meeting minutes will be posted to + + 17:33 `` \#link [https://cloud-init.github.io](https://cloud-init.github.io) + + 17:33 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2019-07-08.md b/content/status-2019-07-08.md new file mode 100644 index 0000000..4e4b957 --- /dev/null +++ b/content/status-2019-07-08.md @@ -0,0 +1,378 @@ +Title: Cloud-init bi-weekly status +Date: 2019-07-08 16:16:00 UTC +Category: status-meeting-minutes +Slug: status-2019-07-08 + +Meeting information +---------------- + * \#cloud-init: Cloud-init bi-weekly status, 08 Jul at 16:16 — 17:32 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-07-08-16.16.log.html](http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-07-08-16.16.log.html)]] + + + +Meeting summary +---------------- + +### Previous Actions +The discussion about "Previous Actions" started at 16:18. + + * **LINK**: [https://cloud-init.github.io/status-2019-06-24.html\#status-2019-06-24](https://cloud-init.github.io/status-2019-06-24.html\#status-2019-06-24) + * **ACTION**: query on incomplete [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381) with AnhVoMSFT to see if this needs priority + +### Recent Changes +The discussion about "Recent Changes" started at 16:22. + + +### In Progress Development +The discussion about "In Progress Development" started at 16:27. + + * **LINK**: [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + * **LINK**: [https://trello.com/c/RhevWnHx/1064-azure-imds-handle-multiple-default-routes-static-ips-in-primary-subnet](https://trello.com/c/RhevWnHx/1064-azure-imds-handle-multiple-default-routes-static-ips-in-primary-subnet) + * **LINK**: [https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/369792](https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/369792) + * **LINK**: [https://trello.com/c/TMK5ZDMf/1108-azure-async-disk-mounts](https://trello.com/c/TMK5ZDMf/1108-azure-async-disk-mounts) + * **LINK**: [https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516](https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516) + * **LINK**: [https://wiki.ubuntu.com/CloudinitUpdates](https://wiki.ubuntu.com/CloudinitUpdates) + * **ACTION**: review Azure telemetry branch [https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785](https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785) + * **LINK**: [https://code.launchpad.net/~bitfehler/cloud-init/+git/cloud-init/+merge/369814](https://code.launchpad.net/~bitfehler/cloud-init/+git/cloud-init/+merge/369814) + +### Office Hours (next ~30 mins) +The discussion about "Office Hours (next ~30 mins)" started at 16:48. + + * **LINK**: [https://netplan.io](https://netplan.io) for more info + + + +Vote results +---------------- + + + + +Action items, by person +---------------- + + * AnhVoMSFT + * query on incomplete [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381) with AnhVoMSFT to see if this needs priority + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (89) + * Odd_Bloke (13) + * bitfehler (10) + * tribaal (8) + * AnhVoMSFT (7) + * chad-aws (6) + * meetingology (5) + * ubot5 (3) + * robjo (2) + * rharper (2) + + + +Full Log +---------------- + + + 16:16 `` \#startmeeting Cloud-init bi-weekly status + + 16:16 `` Meeting started Mon Jul 8 16:16:57 2019 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:16 `` + + 16:16 `` Available commands: action commands idea info link nick + + 16:17 `` bitfehler: It works for me on an Ubuntu eoan system, locally. + + 16:17 `` hi folks, welcome to another cloud-init community status meeting. All discussions and interjections welcome. + + 16:17 `` bitfehler: What version of Python 3 are you using? + + 16:17 `` loud-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. + + 16:17 `` our format is the following topics: Previous Actions, Recent Changes, In-progress Development, Office Hours + + 16:17 `` anyone is welcome to participate, interject, make suggestions or ask questions + + 16:18 `` we host the meeting every two weeks at the date and time indicated in the IRC channel topic ^ + + 16:18 `` \#topic Previous Actions + + 16:19 `` I'm looking through our meeting minutes now from the previous meeting + + 16:19 `` \#link [https://cloud-init.github.io/status-2019-06-24.html\#status-2019-06-24](https://cloud-init.github.io/status-2019-06-24.html\#status-2019-06-24) + + 16:19 `` Touch base with AnhVoMSFT by next status on priority of [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381) + + 16:19 `` Ubuntu bug 1832381 in cloud-init (Ubuntu) "vm fails to boot due to conflicting network configuration when user switches from netplan to eni" [Undecided,Incomplete] + + 16:20 `` I think AnhVoMSFT may have been looking to get cloud-init logs on a system reproducing this problem + + 16:20 `` so let's carry this over for next meeting and this bug is marked incomplete until we have some cloud-init logs to debug + + 16:21 `` \#action query on incomplete [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381) with AnhVoMSFT to see if this needs priority + + 16:21 * meetingology query on incomplete [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381) with AnhVoMSFT to see if this needs priority + + 16:21 `` Ubuntu bug 1832381 in cloud-init (Ubuntu) "vm fails to boot due to conflicting network configuration when user switches from netplan to eni" [Undecided,Incomplete] + + 16:21 `` no further actions listed from last meeting + + 16:22 `` \#topic Recent Changes + + 16:22 `` blackboxsw I did hear back from networking on how to trigger mac address change, so I'll work on that this week and get the logs attached + + 16:22 `` excellent AnhVoMSFT thanks! + + 16:22 `` and thanks for joining the meeting + + 16:22 `` the harder it is to reproduce, the better, since it's unlikely to affect that many customers + + 16:22 `` +1 + + 16:23 `` the following are commits that landed in tip of master for cloud-init upstream + + 16:23 `` - Add missing dsname for Hetzner Cloud datasource [Markus Schade] + + 16:24 `` - doc: indicate that netplan is default in Ubuntu now [Daniel Watkins] + + 16:24 `` - azure: add region and AZ properties from imds compute location metadata + + 16:24 `` [Chad Smith] + + 16:24 `` - sysconfig: support more bonding options [Penghui Liao] + + 16:24 `` - cloud-init-generator: use libexec path to ds-identify on redhat systems + + 16:24 `` [Ryan Harper] ([LP: \#1833264]([https://bugs.launchpad.net/bugs/1833264](https://bugs.launchpad.net/bugs/1833264))) + + 16:24 `` - tools/build-on-freebsd: update to python3 [Gonéri Le Bouder] + + 16:24 `` Ubuntu bug 1833264 in cloud-init "cloud-init-generator hardcodes path to ds-identify" [Undecided,Fix committed] + + 16:25 `` though I think the bottom two of those commits I may have reported last meeting + + 16:26 `` beyond that I know that paride has resolved a couple of issues with our CI infrastructure not cleaning up stale containers which would have triggered a number of CI failures over the last few weeks. + + 16:27 `` I think that about wraps 'completed' work in tip. + + 16:27 `` \#topic In Progress Development + + 16:28 `` We mentioned this last meeting, there are a couple of longer features we are working on that will hit cloud-init tip soon. + + 16:28 `` we track our work on trello at the following url + + 16:28 `` \#link [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + + 16:29 `` In trying to enable secondary IP configuration on Azure platforms, we discovered a systemd-networkd bug related to classless routes not getting the appropriate source IP configuration + + 16:29 `` per this card + + 16:29 `` \#link [https://trello.com/c/RhevWnHx/1064-azure-imds-handle-multiple-default-routes-static-ips-in-primary-subnet](https://trello.com/c/RhevWnHx/1064-azure-imds-handle-multiple-default-routes-static-ips-in-primary-subnet) + + 16:30 `` Dan Streetman filed a bug and upstream systemd fix for this [https://github.com/systemd/systemd/issues/12969](https://github.com/systemd/systemd/issues/12969) + + 16:31 `` and he's working on getting that released into Ubuntu Eoan. cloud-init may need a minor fix to only render static IPs if systemd-networkd version contains the latest fix. + + 16:31 `` secondary addresses on azure too, or aws? + + 16:31 `` chad-aws: I also have just pushed a branch for review that will add secondary IPs from AWS's Datasource as well + + 16:31 `` since we had context on the netplan we need to generate that + + 16:31 `` ok + + 16:32 `` \#link [https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/369792](https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/369792) + + 16:33 `` chad-aws: the one question I think we might have to discuss related to the above branch is whether or not cloud-init on older LTSes (Xenial, Bionic) should change behavior to attempt rendering secondary IP information or not (because that would be a change in behavior) + + 16:34 `` generally we try to retain existing behavior on old Ubuntu LTS releases so we don't surprise folks who may have worked around previous limitations of cloud-init (like manually/scripted adding their own secondary IP information) + + 16:35 `` (Note I am not the chad.smith above, but I am interested too.) + + 16:35 `` hehe, yes, I am not talking to myself (blackboxsw == chad.smith) + + 16:36 `` also in progress is rharper's good work on teasing out async mount functionality per the following + + 16:36 `` \#link [https://trello.com/c/TMK5ZDMf/1108-azure-async-disk-mounts](https://trello.com/c/TMK5ZDMf/1108-azure-async-disk-mounts) + + 16:36 `` I think different config files should make different behavior and that's okay. + + 16:36 `` +1 chad-aws + + 16:37 `` the async mount feature is the ability to allow cloud-init defer some disk mounts until later in the cloud-init stages to allow folks to ssh to the vms earlier in the boot process + + 16:38 `` as some systems with lots of mounts may block for a while trying to mount and format disks + + 16:39 `` while this approach is tagged as azure, rharper is approaching it in a generic way that should make this functionality accessible to many platforms + + 16:40 `` paride: rharper Odd_Bloke anything else I'm forgetting in progress? + + 16:40 `` blackboxsw: right; it's changes to cc_disk_setup/cc_mount handling + + 16:40 `` blackboxsw: nothing I can think of + + 16:41 `` we probably should cut an Ubutuu Eoan upload of cloud-init tip soon, but I don't know when that should be scheduled? + + 16:41 `` I'm doing some work to modify the way we determine network config sources, but that shouldn't affect any data sources that don't opt in to it. + + 16:41 `` i looked at it briefly, this involves calling a systemd unit to format/mount - do we report error back to cloud-init ? + + 16:41 * tribaal raises hand + + 16:41 `` is there any rough estimation on where that tip cut would be? + + 16:41 `` tribaal: ahh yes awesome, forgot. tribaal has a new datasource + + 16:41 `` yes, thanks a lot for your reviews everyone + + 16:42 `` nice working with you guys again :) + + 16:42 `` \#link [https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516](https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516) + + 16:42 `` for Exoscale ^ + + 16:42 `` Ideally we'd target the next release for our datasource as well, but of course it's not landed yet so if the cut is e.g. tomorrow it might be a bit tight :) + + 16:42 `` Specifically, if a platform does any networking setup during the initramfs (such as for iSCSI), cloud-init will _only_ consider the initramfs-provided configuration at the moment. + + 16:42 `` tribaal: for eoan, we can just grab tip of master at anypoint for an upload since it + + 16:43 `` is still a development release + + 16:43 `` ack + + 16:43 `` so it's super low weight for our release (and we should do it often) + + 16:43 `` also we have planned/upcoming an SRU into Xenial/Bionic/Disco on July 15th (so next week) + + 16:44 `` as far as SRUs are concerned, would that typically be something that would be backported, or not? + + 16:44 `` I'm making it possible for data sources to specify a different order for the network config sources, so that platforms where iSCSI is the default can have their data source's network config preferred. + + 16:44 `` tribaal: and others: cloud-init SRUs our tip into every release due to an SRU exception that we have with Ubuntu + + 16:44 `` so we upload latest code into each SRU target series for ubuntu + + 16:45 `` though we may patch/disable some functionality that is deemed a change in behavior from previous release + + 16:45 `` blackboxsw: understood, thanks. I'll schedule some time for myself to work on it "full time" as much as possible, so we can make the cut. + + 16:45 `` I'm also splitting apart explicitly-from-the-user cmdline configuration (i.e. network-data=...) from the initramfs-provided values (ip=... or iBFT), so that data sources can be configured to still allow explicit user network configuration to override data source network configuration. + + 16:45 `` here's our SRU process for those interested + + 16:45 `` \#link [https://wiki.ubuntu.com/CloudinitUpdates](https://wiki.ubuntu.com/CloudinitUpdates) + + 16:46 `` so this meeting (and an email to cloud-init mailinglist) will serve as a call for branches/features for SRU. + + 16:46 `` But as I said previously, this is all just refactoring except for the specific places we need this functionality. + + 16:46 `` I sent a merge proposal for adding some more telemetry for Azure: [https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785](https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785) - would appreciate a review. Trying to make it in before next SRU + + 16:46 `` also will send a merge proposal today or tomorrow on the case sensitivity issue when checking is_new_instance + + 16:46 `` if folks are interested in getting a specific feature/bug or branch reviewed/fixed and published, please raise your hand, ping in channel or send email to the mailing list to make sure the need is not forgotten + + 16:47 `` \#action review Azure telemetry branch [https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785](https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785) + + 16:47 * meetingology review Azure telemetry branch [https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785](https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785) + + 16:47 `` i feel a bit awkward stepping in here, but i kind of do + + 16:47 `` AnhVoMSFT: we also have reviewed samgilson's branch on a new cloud-init analyze subcommand for boot performance + + 16:48 `` sorry, i am pretty new to cloud-init, but i did open a merge proposal today + + 16:48 `` bitfehler: no worries, conversations gotta happen :) + + 16:48 `` \#link [https://code.launchpad.net/~bitfehler/cloud-init/+git/cloud-init/+merge/369814](https://code.launchpad.net/~bitfehler/cloud-init/+git/cloud-init/+merge/369814) + + 16:48 `` (Can I do that, or only blackboxsw?) + + 16:48 `` thanks blackboxsw, last I synced with him, Sam is actively working on addressing your comments + + 16:48 `` I'll tick the topic to office hours which is really just open season for discussion or reviews + + 16:48 `` Does anyone know if VMware has any plans to move their source from [https://github.com/vmware/cloud-init-vmware-guestinfo](https://github.com/vmware/cloud-init-vmware-guestinfo) to be included in upstream cloud-init? + + 16:48 `` \#topic Office Hours (next ~30 mins) + + 16:51 `` i think my main question would have been how to best get in touch with you, but i think i found the answer already :) + + 16:51 `` hrm, first I've seen of that robjo . maybe we can ping Sankar on that to see what the motivation is there + + 16:51 `` bitfehler: either here or mail cloud-init@lists.launchpad.net + + 16:52 `` I was just made aware of this last week via "please create a packge' to which my initial answer is No, the VMware code should be in cloud-init proper + + 16:53 `` per vmware,yeah that makes sense for them to try to get that cloud-init datasource upstream. forcing every distro to do their packaging for them is not really the right solution + + 16:54 `` one other thing i was wondering: do you feel a plain systemd-networkd network renderer would make sense? i wrote a very basic one trying to get better cloud-init support for Arch Linux + + 16:54 `` it sort of works, but I am not sure whether this goal worth pursuing? + + 16:57 `` bitfehler: interesting, right so we have netplan render which ultimately renders networkd on our behalf on ubuntu, + + 16:58 `` if direct networkd render is the only way to support network config on Arch linux I don't see why we wouldn't want that.... rharper or Odd_Bloke? (maybe I'm missing the concern) + + 16:59 `` i saw the comments about networkd above, but i am not familiar with netplan. it is another layer in between, right? + + 17:00 `` bitfehler: netplan takes v2 network configuration and renders it for a target backend. The two supported backends ATM are networkd and NetworkManager. + + 17:00 `` [https://netplan.io](https://netplan.io) for more info + + 17:00 `` oh, wow, i overlooked that. so it doesn't need any additional software? + + 17:01 `` it does need netplan + + 17:01 `` oh wait, netplan is a renderer itself, and that supports the two backends + + 17:02 `` Right, netplan is the intended way for cloud-init to render network config for networkd. + + 17:03 `` ok, got it. i guess i could also look into porting netplan to arch then? not sure what an effort that would be + + 17:05 `` IMO, that would be the best way to go, if it's tractable. + + 17:05 `` We ideally wouldn't reimplement netplan's networkd renderer in cloud-init. :) + + 17:05 `` i'll let you know soon ;) + + 17:08 `` I guess this should go both ways. Is there anything AWS EC2 can do better or different? + + 17:25 `` nice chad-aws, sorry I got pulled into a second meeting. chad-aws I did have a question about metadata versioning in aws. + + 17:26 `` how are new features communicated for a new metadata version + + 17:26 `` I reference [https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html) + + 17:26 `` but it didn't have a specific note on the changes added for 2018-09-24 which I used in my branch + + 17:27 `` only the first version that a field was introduced, not that local_ipv4s changed value from string to list in 2018-09-24. + + 17:27 `` so I guess my question is, is there a better source of truth for ec2 metadata values that we should be looking at + + 17:28 `` chad-aws: sorry (I realize that's a question out of left field) + + 17:31 `` I think I'll wrap the meeting here. Thank you all again for the attending this week. + + 17:31 `` thx + + 17:31 `` Again plan for cloud-init 19.2 SRU is scheduled for next week so any features/branches that need landing or review should be raised here or on the mailing list + + 17:32 `` minutes will be posted at [https://cloud-init.github.io](https://cloud-init.github.io) + + 17:32 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2019-07-22.md b/content/status-2019-07-22.md new file mode 100644 index 0000000..10ef4e7 --- /dev/null +++ b/content/status-2019-07-22.md @@ -0,0 +1,304 @@ +Title: Cloud-init bi-weekly status +Date: 2019-07-22 16:15:00 UTC +Category: status-meeting-minutes +Slug: status-2019-07-22 + +Meeting information +---------------- + * \#cloud-init: Cloud-init bi-weekly status, 22 Jul at 16:15 — 17:15 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-07-22-16.15.log.html](http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-07-22-16.15.log.html)]] + + + +Meeting summary +---------------- + +### Previous Actions +The discussion about "Previous Actions" started at 16:17. + + * **LINK**: [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381) + * **ACTION**: rharper to update [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381) status + * **LINK**: [http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-07-08-16.16.html](http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-07-08-16.16.html) + * **ACTION**: rharper to followup with blackboxsw on pushing status minutes up to cloud-init.github.io page + +### Recent Changes +The discussion about "Recent Changes" started at 16:23. + + * **LINK**: [https://discourse.ubuntu.com/t/cloud-init-19-2-release/11873](https://discourse.ubuntu.com/t/cloud-init-19-2-release/11873) + +### In Progress Development +The discussion about "In Progress Development" started at 16:27. + + * **LINK**: [https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368507](https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368507) + * **LINK**: [https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/365641](https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/365641) + * **LINK**: [https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368508](https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368508) + +### In Progress Development +The discussion about "In Progress Development" started at 16:36. + + * **LINK**: [https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516](https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516) + * **LINK**: [https://code.launchpad.net/~xiaofengw/cloud-init/+git/cloud-init/+merge/367889](https://code.launchpad.net/~xiaofengw/cloud-init/+git/cloud-init/+merge/367889) + * **LINK**: [https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/369783](https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/369783) + * **LINK**: [https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/feature/stage_threadpool](https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/feature/stage_threadpool) + +### Office Hours (next ~30 mins) +The discussion about "Office Hours (next ~30 mins)" started at 16:43. + + * **LINK**: [https://copr.fedorainfracloud.org/coprs/g/cloud-init/cloud-init-dev/](https://copr.fedorainfracloud.org/coprs/g/cloud-init/cloud-init-dev/) + * **LINK**: [https://download.opensuse.org/repositories/Cloud:/Tools/](https://download.opensuse.org/repositories/Cloud:/Tools/) + + + +Vote results +---------------- + + + + +Action items, by person +---------------- + + * rharper + * rharper to update [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381) status + * rharper to followup with blackboxsw on pushing status minutes up to cloud-init.github.io page + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * rharper (69) + * Goneri (20) + * meetingology (6) + * Odd_Bloke (5) + * metsuke (4) + * ubot5 (2) + + + +Full Log +---------------- + + + 16:15 `` \#startmeeting Cloud-init bi-weekly status + + 16:15 `` Meeting started Mon Jul 22 16:15:03 2019 UTC. The chair is rharper. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:15 `` + + 16:15 `` Available commands: action commands idea info link nick + + 16:15 `` \o/ + + 16:15 `` \#chair Odd_Bloke + + 16:15 `` Current chairs: Odd_Bloke rharper + + 16:15 `` hi folks, welcome to another cloud-init community status meeting. All discussions and interjections welcome. + + 16:16 `` 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. + + 16:16 `` our format is the following topics: Previous Actions, Recent Changes, In-progress Development, Office Hours + + 16:16 `` anyone is welcome to participate, interject, make suggestions or ask questions + + 16:16 `` we host the meeting every two weeks at the date and time indicated in the IRC channel topic ^ + + 16:17 `` \#topic Previous Actions + + 16:17 `` o/ + + 16:17 `` We had a few previous action items to look at + + 16:18 `` [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381) + + 16:18 `` Ubuntu bug 1832381 in cloud-init (Ubuntu) "vm fails to boot due to conflicting network configuration when user switches from netplan to eni" [Undecided,Incomplete] + + 16:18 `` AnhVoMSFT was looking to collect logs from this scenario; + + 16:19 `` hey! + + 16:19 `` it appears that getting an instance where the MAC address changes is harder so fewer folks trip over this; however, we agreed that cloud-init can track which renderer it used and if it switches it can clean up the config it wrote; + + 16:19 `` \#action rharper to update [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381) status + + 16:19 * meetingology rharper to update [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381) status + + 16:19 `` Ubuntu bug 1832381 in cloud-init (Ubuntu) "vm fails to boot due to conflicting network configuration when user switches from netplan to eni" [Undecided,Incomplete] + + 16:20 `` The other action was to review [https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785](https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785) + + 16:20 `` This was completed the other week while we worked toward the 19.2 release; that branch is currently work-in-progress, awaiting feedback/changes from submitter + + 16:21 `` that's all of the action items from previous meeting + + 16:22 `` previous meeting status found here: + + 16:22 `` \#link [http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-07-08-16.16.html](http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-07-08-16.16.html) + + 16:23 `` normally at the cloud-init.github.io status page; looks like we didn't push the logs there. + + 16:23 `` \#action rharper to followup with blackboxsw on pushing status minutes up to cloud-init.github.io page + + 16:23 * meetingology rharper to followup with blackboxsw on pushing status minutes up to cloud-init.github.io page + + 16:23 `` \#topic Recent Changes + + 16:25 `` % git log --oneline --since 2019-07-08 + + 16:25 `` a02c0c9 (HEAD ->` master, origin/master, origin/HEAD) cloud_tests: updates and fixes + + 16:25 `` 5498107 Fix bug rendering MTU on bond or vlan when input was netplan. + + 16:25 `` b3a87fc net: update net sequence, include wait on netdevs, opensuse netrules path + + 16:25 `` 060b1a1 (tag: 19.2, raharper/release/19.2, release/19.2, fix/fs_setup_custom_command_lp1801790) Release 19.2 + + 16:25 `` 07b1723 net: add rfc3442 (classless static routes) to EphemeralDHCP + + 16:25 `` 1404817 templates/ntp.conf.debian.tmpl: fix missing newline for pools + + 16:25 `` a785462 Support netplan renderer in Arch Linux + + 16:25 `` a066ccd Fix typo in publicly viewable documentation. + + 16:26 `` d9769c4 Add a cdrom size checker for OVF ds to ds-identify + + 16:26 `` 9c47c68 VMWare: Trigger the post customization script via cc_scripts module. + + 16:26 `` a24550a Cloud-init analyze module: Added ability to analyze boot events. + + 16:26 `` a6faf3a Update debian eni network configuration location, retain Ubuntu setting + + 16:26 `` e5f5421 net: skip bond interfaces in get_interfaces + + 16:26 `` 217c893 Fix a couple of issues raised by a coverity scan + + 16:26 `` biggest item in there is the 19.2 release + + 16:26 `` \#link [https://discourse.ubuntu.com/t/cloud-init-19-2-release/11873](https://discourse.ubuntu.com/t/cloud-init-19-2-release/11873) + + 16:26 `` a big thank you from the cloud-init team to everyone who helped contribute to the release + + 16:27 `` do you have time for a little BSD update? + + 16:27 `` Yes, let's talk about In progress developement + + 16:27 `` \#topic In Progress Development + + 16:27 `` Goneri: go ahead + + 16:28 `` \#topic FreeBSD/NetBSD status + + 16:28 `` so there is two active branches, the first one is: [https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368507](https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368507) + + 16:28 `` \#link [https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368507](https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368507) + + 16:29 `` it has started with a tiny fix to address a configuration difference with FreeBSD (there is no chpasswd there) + + 16:29 `` and it's now a slightly bigger refactoring now, I believe it clarify the code base and I would like to land it like that. + + 16:30 `` a discussion is ongoing with rharper on the PR + + 16:30 `` second PR is [https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/365641](https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/365641) + + 16:30 `` \#link [https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/365641](https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/365641) + + 16:30 `` this one is much bigger, and I've just addressed the last comment from rharper, I test it often and it works fine for me + + 16:31 `` if you want to give it a try, I pushed some pre-built images here: [http://bsd-cloud-image.org/](http://bsd-cloud-image.org/) + + 16:31 `` nice! + + 16:31 `` I test it with OpenStack and NoCloud, a friend who maintains CBSD also test it on Bhyve (FreeBSD) + + 16:32 `` finally, the last one is [https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368508](https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368508) + + 16:32 `` \#link [https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368508](https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368508) + + 16:32 `` No active merge request yet because it depends on the two actives PR that I just mentioned + + 16:32 `` this patch brings NetBSD support (7 and 8) + + 16:33 `` I would like to work on OpenBSD later, but it's still a low priority + + 16:34 `` Goneri: thanks for the update + + 16:34 `` finally, I've a bunch of scripts that I use to build my images + + 16:35 `` it's still rather raw, but I would like to integrate that at some point with your CI + + 16:35 `` that's all + + 16:35 `` thanks + + 16:36 `` \#topic In Progress Development + + 16:36 `` \#link [https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516](https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516) + + 16:36 `` Adding a new datasource for Exoscale + + 16:36 `` \#link [https://code.launchpad.net/~xiaofengw/cloud-init/+git/cloud-init/+merge/367889](https://code.launchpad.net/~xiaofengw/cloud-init/+git/cloud-init/+merge/367889) + + 16:36 `` vmware user-defined-scripts + + 16:37 `` \#link [https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/369783](https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/369783) + + 16:37 `` Allow datasources to configure the order of network-config sources + + 16:37 `` \#link [https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/feature/stage_threadpool](https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/feature/stage_threadpool) + + 16:38 `` I'm expecting to have a response to Ryan's review comments on that today, and whatever conclusion we reach shouldn't be too much work to implement. + + 16:38 `` definitely + + 16:38 `` And then I'll have a follow-up to split apart the "cmdline" network data source in to "cmdline" and "initramfs", which are currently conflated. + + 16:39 `` (Neither of these should cause behavioural changes, they're just setting us up for some data source work down the line.) + + 16:40 `` The threadpool branch is a more general approach to handle running modules async from the mainthread; there were some limitations depending on systemd; and there is a desire for more than just disk_setup to run async; this branch I'm working on would allow modules to be tagged async and they run in a separate thread allowing the next module to proceed; we then join at the end of stage to ensure completion of threads; + + 16:41 `` any other upstream development I'm missing? + + 16:43 `` ok, I think that's it then; + + 16:43 `` \#topic Office Hours (next ~30 mins) + + 16:43 `` feel free to ask for help, reviews, discussions on any cloud-init items you're looking at. + + 16:44 `` Is Ubuntu the recommended, or most maintained, distribution of cloud-init? + + 16:46 `` metsuke: hi; cloud-init in Ubuntu is the most-up-to-date as we're both the upstream maintainers (working for Canonical) and handle getting the latest upstream into Ubuntu images + + 16:47 `` metsuke: we also help produce daily rpm builds for RedHat/Centos/Fedora in our copr repo + + 16:47 `` \#link [https://copr.fedorainfracloud.org/coprs/g/cloud-init/cloud-init-dev/](https://copr.fedorainfracloud.org/coprs/g/cloud-init/cloud-init-dev/) + + 16:48 `` \#link [https://download.opensuse.org/repositories/Cloud:/Tools/](https://download.opensuse.org/repositories/Cloud:/Tools/) + + 16:48 `` suse's cloud:Tools keeps a really recent cloud-init as well + + 16:48 `` great, thanks for the info! + + 16:48 `` sure + + 16:49 `` I'm looking to distribute standardized VMs to 100+ sites running ESXi so I'm trying to find the best way to do that =) + + 16:52 `` metsuke: If you have any questions, please don't hesitate to ask in here; we're generally around US working hours, for reference. + + 16:53 `` yes, cloud-init can help keep your base image generic, allowing customization to happen at boot time; + + 16:53 `` thanks, I'm trying to do some preliminary investigation so I have an intelligent question to ask =P + + 17:15 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2019-08-19.md b/content/status-2019-08-19.md new file mode 100644 index 0000000..14fc527 --- /dev/null +++ b/content/status-2019-08-19.md @@ -0,0 +1,254 @@ +Title: Cloud-init bi-weekly status +Date: 2019-08-19 16:18:00 UTC +Category: status-meeting-minutes +Slug: status-2019-08-19 + +Meeting information +---------------- + * \#cloud-init: Cloud-init bi-weekly status, 19 Aug at 16:18 — 17:25 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-08-19-16.18.log.html](http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-08-19-16.18.log.html)]] + + + +Meeting summary +---------------- + + **LINK**: [https://cloud-init.github.io/status-2019-08-05.html\#status-2019-08-05](https://cloud-init.github.io/status-2019-08-05.html\#status-2019-08-05) +### cloud-init Reviews: [http://bit.ly/ci-reviews](http://bit.ly/ci-reviews) | Meeting minutes: [https://goo.gl/mrHdaj](https://goo.gl/mrHdaj) | Next status meeting Sept 2 16:15 UTC | cloud-init v 19.2 (07/17) | [https://bugs.launchpad.net/cloud-init/+filebug](https://bugs.launchpad.net/cloud-init/+filebug) +The discussion about "cloud-init Reviews: [http://bit.ly/ci-reviews](http://bit.ly/ci-reviews) | Meeting minutes: [https://goo.gl/mrHdaj](https://goo.gl/mrHdaj) | Next status meeting Sept 2 16:15 UTC | cloud-init v 19.2 (07/17) | [https://bugs.launchpad.net/cloud-init/+filebug](https://bugs.launchpad.net/cloud-init/+filebug)" started at 16:20. + + +### Previous actions +The discussion about "Previous actions" started at 16:21. + + +### Recent Changes +The discussion about "Recent Changes" started at 16:22. + + +### In-progress Development +The discussion about "In-progress Development" started at 16:25. + + * **LINK**: [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + * **LINK**: [https://code.launchpad.net/cloud-init/+activereviews](https://code.launchpad.net/cloud-init/+activereviews) + * **LINK**: [https://cloud-init.github.io/](https://cloud-init.github.io/) + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (71) + * rharper (9) + * meetingology (5) + * tribaal (4) + * robjo (2) + * ubot5 (1) + * Odd_Bloke (0) + + + +Full Log +---------------- + + + 16:18 `` \#startmeeting Cloud-init bi-weekly status + + 16:18 `` Meeting started Mon Aug 19 16:18:48 2019 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:18 `` + + 16:18 `` Available commands: action commands idea info link nick + + 16:19 `` Hi guys and girls, welcome to cloud-init biweekly status meeting + + 16:19 `` \#chair rharper + + 16:19 `` Current chairs: blackboxsw rharper + + 16:19 `` \#chair Odd_Bloke + + 16:19 `` Current chairs: Odd_Bloke blackboxsw rharper + + 16:19 `` 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. + + 16:19 `` All discussions and interjections are welcome + + 16:19 `` our format is the following topics: Previous Actions, Recent Changes, In-progress Development, Office Hours + + 16:20 `` last meeting's minutes are herer + + 16:20 `` \#link [https://cloud-init.github.io/status-2019-08-05.html\#status-2019-08-05](https://cloud-init.github.io/status-2019-08-05.html\#status-2019-08-05) + + 16:20 `` o/ + + 16:20 `` we host the meeting every two weeks at the date and time indicated in the IRC channel topic ^ + + 16:20 * blackboxsw changes that topic now, since we(I) forgot last time + + 16:20 `` \#topic cloud-init Reviews: [http://bit.ly/ci-reviews](http://bit.ly/ci-reviews) | Meeting minutes: [https://goo.gl/mrHdaj](https://goo.gl/mrHdaj) | Next status meeting Sept 2 16:15 UTC | cloud-init v 19.2 (07/17) | [https://bugs.launchpad.net/cloud-init/+filebug](https://bugs.launchpad.net/cloud-init/+filebug) + + 16:21 `` next meeting in two weeks + + 16:21 `` \#topic Previous actions + + 16:21 `` I see no previous actions raised during last meeting. Woo hoo! + + 16:22 `` \#topic Recent Changes + + 16:22 `` the following are commits that + + 16:22 `` have landed in tip of master for cloud-init since the last meeting: git log --since 2019-08-04 + + 16:22 `` - cloudinit/distros/parsers/sys_conf: add docstring to SysConf + + 16:22 `` [Daniel Watkins] + + 16:22 `` - pyflakes: remove unused variable [Joshua Powers] + + 16:22 `` - Azure: Record boot timestamps, system information, and diagnostic events + + 16:22 `` [Anh Vo] + + 16:22 `` - DataSourceOracle: configure secondary NICs on Virtual Machines + + 16:22 `` [Daniel Watkins] + + 16:22 `` - distros: fix confusing variable names [Daniel Watkins] + + 16:22 `` - azure/net: generate_fallback_nic emits network v2 config instead of v1 + + 16:22 `` [Chad Smith] + + 16:22 `` - Add support for publishing host keys to GCE guest attributes + + 16:22 `` [Rick Wright] + + 16:22 `` - New data source for the Exoscale.com cloud platform [Chris Glass] + + 16:22 `` - doc: remove intersphinx extension [Daniel Watkins] + + 16:22 `` - cc_set_passwords: rewrite documentation [Daniel Watkins] (LP: \#1838794) + + 16:22 `` Launchpad bug 1838794 in cloud-init "Set Passwords documentation describes incorrect behaviour for `password` config key" [Low,Fix committed] [https://launchpad.net/bugs/1838794](https://launchpad.net/bugs/1838794) + + 16:24 `` We have also published commits though " - Azure: Record boot timestamps, system information, and diagnostic events" to Ubuntu Eoan (19.10) (cloud-init v.19.2-13) if folks want a glimpse of those features + + 16:24 `` Many thanks to Azure and GCE folks for their commits and a hi five to tribaal for adding Exoscale + + 16:25 `` \#topic In-progress Development + + 16:25 `` As always, we try to keep most of our work up to date in trello + + 16:25 `` \#link [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + + 16:26 `` cards in the "Reviewing" column should represent the work we expect to have up for review in the short term. + + 16:27 `` rharper is mid-stream on some investigations that will likely lead to significant speed improvements for cloud-init + + 16:28 `` Odd_Bloke: is working on some significant improvements for Oracle's datasource rendering network config + + 16:29 `` and I'm working on getting OpenStack and Ec2 datasources to talk network config v2. + + 16:29 `` beyond that work we have a pretty healther active review queue + + 16:29 `` \#link [https://code.launchpad.net/cloud-init/+activereviews](https://code.launchpad.net/cloud-init/+activereviews) + + 16:31 `` of note, some freebsd work is in flight, gce dns improvements, udev triggers and OVF handling user-defined scripts. + + 16:31 `` We + + 16:32 `` will spend the latter part of this meeting looking over the review queue to see that open branches are in the proper state + + 16:33 `` Also, our plan for this week is to cut a Cloud-init SRU (Stable release update) for upload into xenial, bionic and disco. + + 16:34 `` expectation is that those Ubuntu series will see an update for cloud-init after our ~7 days of testing and verification + + 16:34 `` rharper: Odd_Bloke anything else in flight that we should note here? + + 16:34 `` that looks like everything + + 16:35 `` without further ado, we can transition to office hours + + 16:35 `` \#topic Office Hours (next ~30 mins) + + 16:36 `` We're here for any questions, bugs, discussions people would like to have around cloud-init. This block of time is available for any discussions or requests people may have. + + 16:37 `` We will also spend this time grooming the active review queue to make sure developers get any needed feedback on their active branches. + + 16:37 `` If there are any branches that need more eyes, please bring them up here or make sure they are in the 'Needs review' state in Launchpad + + 16:38 `` blackboxsw: thanks! + + 16:40 `` tribaal: good work. I think Odd_Bloke landed the followup work to enable exoscale datasource config to cloud-init.templates to 'enable' it. And looks like that has landed + + 16:40 `` blackboxsw: I'm happy to help verify SRU bugs when the process is kicked - just let me know + + 16:40 `` so it's 'on' in Eoan, once SRU is kicked off, it'll be in there + + 16:41 `` yep, I need to push an Eoan template to our preprod environment tomorrow to kick the tires, but I don't expect anything funny + + 16:41 `` tribaal: will do. I think the only thing we are waiting on before SRU is landing this ubuntu-drivers branch [https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/371369](https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/371369) + + 16:42 `` any feedback on behavior your in Eoan from you tribaal would be helpful. + + 16:43 `` let's try that in English this time: any feedback on the behavior in your Eoan environment would be helpful tribaal. + + 16:43 `` blackboxsw: haha that's what I inferred :) + + 16:43 `` :) /me hits the review queue + + 16:47 `` rharper: if you get a chance: you've landed [https://git.launchpad.net/cloud-init/commit/](https://git.launchpad.net/cloud-init/commit/)?id=b3a87fc0. Do we also still need the following branch? [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/363571](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/363571) + + 16:48 `` If so, I'll spend this time trying to write up unit tests for this if possible + + 16:48 `` blackboxsw: I don't think so; my branch should include all the needs of that branch + + 16:49 `` and the branch tests the wait_for_physdev as well as updates the opensuse net render paths to account for the udev rule number change + + 16:50 `` that's kindof what I was thinking/hoping. I'll mark it rejected in favor of your commit, and we'll see what robjo thinks on that. We can reopen and try to address the unit test aspect of his branch if still needed. + + 16:50 `` I think we can mark that branch closed + + 16:50 `` robjo: had already looked at the branch before landing + + 16:52 `` ok done + + 16:54 `` thanks Florian for your first commit! [https://code.launchpad.net/~florian-mueller-v/cloud-init/+git/cloud-init/+merge/371298](https://code.launchpad.net/~florian-mueller-v/cloud-init/+git/cloud-init/+merge/371298) ... doc update approved + + 16:58 `` I don't recall having looked at [https://git.launchpad.net/cloud-init/commit/](https://git.launchpad.net/cloud-init/commit/)?id=b3a87fc0 and there was no entry in the bug to remind me that I did. Anyway, I've done so now and yes, this obsoletes [https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/363571](https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/363571) + + 17:00 `` thank you robjo for that + + 17:04 `` robjo: [https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/366667](https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/366667) ; yes, I should have linked to the bug in my MP + + 17:04 `` you did take a look a while back though + + 17:06 `` rharper: I believe you, just cannot remember.... + + 17:06 `` heh, it was a while back + + 17:24 `` I think we should probably wrap up the meeting for this week. I've got one more review to clear. + + 17:24 `` Thanks again all for joining. minutes will be posted to github + + 17:25 `` \#link [https://cloud-init.github.io/](https://cloud-init.github.io/) + + 17:25 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2019-09-09.md b/content/status-2019-09-09.md new file mode 100644 index 0000000..bfa718c --- /dev/null +++ b/content/status-2019-09-09.md @@ -0,0 +1,231 @@ +Title: Cloud-init bi-weekly status +Date: 2019-09-09 16:26:00 UTC +Category: status-meeting-minutes +Slug: status-2019-09-09 + +Meeting information +---------------- + * \#cloud-init: Cloud-init bi-weekly status, 09 Sep at 16:26 — 17:33 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-09-09-16.26.log.html](http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-09-09-16.26.log.html)]] + + + +Meeting summary +---------------- + + **LINK**: [https://cloud-init.github.io/status-2019-08-19.html\#status-2019-08-19](https://cloud-init.github.io/status-2019-08-19.html\#status-2019-08-19) +### Previous actions +The discussion about "Previous actions" started at 16:30. + + +### Recent Changes +The discussion about "Recent Changes" started at 16:31. + + * **LINK**: [https://lists.launchpad.net/cloud-init/msg00170.html](https://lists.launchpad.net/cloud-init/msg00170.html) + * **LINK**: [https://lists.launchpad.net/cloud-init/](https://lists.launchpad.net/cloud-init/) + +### In-progress Development +The discussion about "In-progress Development" started at 16:38. + + * **LINK**: [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + * **LINK**: [https://discourse.ubuntu.com/c/server](https://discourse.ubuntu.com/c/server) + +### Office Hours (next ~30 mins) +The discussion about "Office Hours (next ~30 mins)" started at 16:48. + + * **ACTION**: blackboxsw send email to the list notifying of status meeting day change. + * **LINK**: [https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/](https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/) + + + +Vote results +---------------- + + + + +Action items, by person +---------------- + + * blackboxsw + * blackboxsw send email to the list notifying of status meeting day change. + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (64) + * meetingology (5) + * Odd_Bloke (4) + * ubot5 (2) + * rharper (1) + + + +Full Log +---------------- + + + 16:26 `` \#startmeeting Cloud-init bi-weekly status + + 16:26 `` Meeting started Mon Sep 9 16:26:10 2019 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:26 `` + + 16:26 `` Available commands: action commands idea info link nick + + 16:27 `` Hey folks, welcome to the ~biweekly cloud-init status meeting. + + 16:28 `` \#chair rharper Odd_Bloke + + 16:28 `` Current chairs: Odd_Bloke blackboxsw rharper + + 16:28 `` o/ + + 16:28 `` 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. + + 16:30 `` Feel free to interject at any time. Our typical format is the following: Previous Actions, Recent Changes, In-progress Development, Office Hours (~30 mins) + + 16:30 `` Last meeting's minutes live here: + + 16:30 `` \#link [https://cloud-init.github.io/status-2019-08-19.html\#status-2019-08-19](https://cloud-init.github.io/status-2019-08-19.html\#status-2019-08-19) + + 16:30 `` \#topic Previous actions + + 16:31 `` no actions from last meeting so we'll plow right through to Recent Changes + + 16:31 `` \#topic Recent Changes + + 16:32 `` The following branches have landed in tip since last meeting: via git log --since 2019-08-19 + + 16:32 `` - doc: document doc, create makefile and tox target [Joshua Powers] + + 16:32 `` - .gitignore: ignore files produced by package builds [Daniel Watkins] + + 16:32 `` - docs: fix whitespace, spelling, and line length [Joshua Powers] + + 16:32 `` - docs: remove unnecessary file in doc directory [Joshua Powers] + + 16:32 `` - Oracle: Render secondary vnic IP and MTU values only [Ryan Harper] + + 16:32 `` - exoscale: fix sysconfig cloud_config_modules overrides + + 16:32 `` [Chad Smith] (LP: \#1841454) + + 16:32 `` Launchpad bug 1841454 in cloud-init "Exoscale datasource overwrites *all* cloud_config_modules" [Undecided,Fix committed] [https://launchpad.net/bugs/1841454](https://launchpad.net/bugs/1841454) + + 16:32 `` - net/cmdline: refactor to allow multiple initramfs network config sources + + 16:32 `` [Daniel Watkins] + + 16:32 `` - ubuntu-drivers: call db_x_loadtemplatefile to accept NVIDIA EULA + + 16:32 `` [Chad Smith] (LP: \#1840080) + + 16:32 `` Launchpad bug 1840080 in cloud-init (Ubuntu) "cloud-init cc_ubuntu_drivers does not set up /etc/default/linux-modules-nvidia" [High,Fix released] [https://launchpad.net/bugs/1840080](https://launchpad.net/bugs/1840080) + + 16:32 `` - Add missing \#cloud-config comment on first example in documentation. + + 16:32 `` [Florian Müller] + + 16:32 `` - ubuntu-drivers: emit latelink=true debconf to accept nvidia eula + + 16:32 `` [Chad Smith] (LP: \#1840080) + + 16:32 `` - DataSourceOracle: prefer DS network config over initramfs + + 16:32 `` [Daniel Watkins] + + 16:32 `` - format.rst: add text/jinja2 to list of content types (+ cleanups) + + 16:32 `` [Daniel Watkins] + + 16:32 `` - Add GitHub pull request template to point people at hacking doc + + 16:32 `` [Daniel Watkins] + + 16:34 `` Additionally: we have also cut a stable-18.4 branch from the 18.4 tag as our last supported python2.6 branch. There will be an email sent out to the mailing list about the intent of this branch. It requires a couple of minor fixes to make sure py2.6 support is functional, but this will be reference branch for any distribution that does not have access to py.27 or later. No additional feature development is + + 16:34 `` planned on stable-18.4 + + 16:37 `` a reminder again that python2.6 support was 'dropped' in cloud-init upstream as of the 18.4 release, so expectations for py2.6 support stopped in 18.4 and there is a deprecation plan for py 2.7 as well + + 16:37 `` \#link [https://lists.launchpad.net/cloud-init/msg00170.html](https://lists.launchpad.net/cloud-init/msg00170.html) + + 16:37 `` Again, see the mailinglist for details and updates + + 16:37 `` \#link [https://lists.launchpad.net/cloud-init/](https://lists.launchpad.net/cloud-init/) + + 16:38 `` \#topic In-progress Development + + 16:38 `` Last week or so the team has been working on SRU validation for cloud-init 19.2.24 into Xenial, Bionic and Disco. + + 16:39 `` We have passed all SRU validation tests and our expected pubish date for 19.2.24 is tomorrow for those Ubuntu series + + 16:40 `` good work on validation folks + + 16:41 `` and thanks for extra cloud-init community verification from exoscale, azure and VMware for validation efforts + + 16:42 `` There is additional Oracle, FreeBSD and Azure work in flight at the moment as well as some boot speed improvements and analysis from rharper + + 16:43 `` The following link represents any carded work upstream is tracking. The Doing lane is content or features we expect to land shortly + + 16:43 `` \#link [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + + 16:47 `` Now is probably a good time to also mention that our entire ubuntu server team also reflects our weekly accomplishements over in the ubuntu-server discourse. If there are deeper discussions or questions on various topics or features please join us there as well + + 16:47 `` \#link [https://discourse.ubuntu.com/c/server](https://discourse.ubuntu.com/c/server) + + 16:48 `` I think that about wraps it for in-progress development + + 16:48 `` \#topic Office Hours (next ~30 mins) + + 16:48 `` upstream cloud-init devs will have eyes on this channel for any discussions, questions, bugs or feature work the greater community would like to discuss. + + 16:49 `` During this time, we'll also groom our activereview queue to make sure we try to get review comments out to devs who have active branches. + + 16:49 `` Again, thanks for tuning in + + 16:57 `` Ok just addressed review comments on [https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/372432](https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/372432) . I'm reviewing [https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368507](https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368507) + + 16:59 * blackboxsw also sets the next meeting topic so we don't forget. + + 17:01 `` Odd_Bloke: rharper powersj, I *think* we decided to shift from Mondays to Tuesdays for status meetings to avoid collisions with holidays, vacation work travel etc. Are we doing that for next status meeting, or maybe waiting to discuss that more broadly? + + 17:02 `` Tuesday in two weeks is likely to be a travel day for anyone heading to the cloud-init summit. + + 17:02 `` But Monday is likely to be a swap day for Canonical folks because we're all travelling next week too. + + 17:03 `` hrm right, maybe we wait then and discuss at the summit + + 17:03 `` So I would perhaps suggest skipping the next meeting, and then we can resume on Tuesdays two weeks after the summit? + + 17:03 `` discuss scheduling changes that is + + 17:03 `` sure, let's push/postpone until summit +2 weeks + + 17:05 `` \#action blackboxsw send email to the list notifying of status meeting day change. + + 17:05 * meetingology blackboxsw send email to the list notifying of status meeting day change. + + 17:10 `` +1 Odd_Bloke + + 17:11 `` Also note that the version of cloud-init that has undergone SRU verification is also published to our copr el-testing repo. We only update that repo during upstream cloud-init releases XX.YY and any Ubuntu SRUs so it is much more stable than our daily copr repo. + + 17:11 `` \#link [https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/](https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/) + + 17:33 `` I think that about wraps our cloud-init status meeting for today. I'm wrapping up my review here and will post it to the set_passwords branch. + + 17:33 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2019-10-08.md b/content/status-2019-10-08.md new file mode 100644 index 0000000..e2aa6a1 --- /dev/null +++ b/content/status-2019-10-08.md @@ -0,0 +1,386 @@ +Title: Cloud-init bi-weekly status +Date: 2019-10-08 16:18:00 UTC +Category: status-meeting-minutes +Slug: status-2019-10-08 + +Meeting information +---------------- + * \#cloud-init: Cloud-init bi-weekly status, 08 Oct at 16:18 — 17:54 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-10-08-16.18.log.html](http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-10-08-16.18.log.html)]] + + + +Meeting summary +---------------- + +### Previous Actions +The discussion about "Previous Actions" started at 16:23. + + * **LINK**: [https://cloud-init.github.io/status-2019-09-09.html\#status-2019-09-09](https://cloud-init.github.io/status-2019-09-09.html\#status-2019-09-09) + +### Recent Changes +The discussion about "Recent Changes" started at 16:25. + + * **ACTION**: blackboxsw verify cpc image builds are unpaused/unblocked for Azure + +### In-progress Development +The discussion about "In-progress Development" started at 16:36. + + * **LINK**: [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + * **LINK**: [https://code.launchpad.net/~ahosmanmsft/cloud-init/+git/cloud-init/+merge/372957](https://code.launchpad.net/~ahosmanmsft/cloud-init/+git/cloud-init/+merge/372957) + * **ACTION**: cloud-init upstream review [https://code.launchpad.net/~ahosmanmsft/cloud-init/+git/cloud-init/+merge/372957](https://code.launchpad.net/~ahosmanmsft/cloud-init/+git/cloud-init/+merge/372957) + * **LINK**: [https://trello.com/c/pqA1adVM/1195-investigate-adding-github-travis-ci-to-cloud-init](https://trello.com/c/pqA1adVM/1195-investigate-adding-github-travis-ci-to-cloud-init) + +### Community Charter +The discussion about "Community Charter" started at 16:44. + + * **LINK**: [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + +### Upcoming meetings and releases +The discussion about "Upcoming meetings and releases" started at 16:47. + + * **ACTION**: upstream cloud-init email about 19.3 release date + +### Office Hours (next ~30 mins) +The discussion about "Office Hours (next ~30 mins)" started at 16:52. + + * **ACTION**: revisit python deprecation and report to mailinglist + + + +Vote results +---------------- + + + + +Action items, by person +---------------- + + * ahosmanmsft + * cloud-init upstream review [https://code.launchpad.net/~ahosmanmsft/cloud-init/+git/cloud-init/+merge/372957](https://code.launchpad.net/~ahosmanmsft/cloud-init/+git/cloud-init/+merge/372957) + * blackboxsw + * blackboxsw verify cpc image builds are unpaused/unblocked for Azure + **UNASSIGNED** + * upstream cloud-init email about 19.3 release date + * revisit python deprecation and report to mailinglist + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (110) + * ubot5 (8) + * AnhVoMSFT (8) + * meetingology (8) + * Odd_Bloke (7) + * rharper (3) + * ahosmanmsft (1) + + + +Full Log +---------------- + + + 16:18 `` \#startmeeting Cloud-init bi-weekly status + + 16:18 `` Meeting started Tue Oct 8 16:18:28 2019 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:18 `` + + 16:18 `` Available commands: action commands idea info link nick + + 16:18 `` Welcome back folks o/ And thanks AnhVoMSFT for the ping to get us started + + 16:18 `` \#chair rharper Odd_Bloke + + 16:19 `` \#chair rharper Odd_Bloke + + 16:19 `` Current chairs: Odd_Bloke blackboxsw rharper + + 16:19 `` 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. + + 16:19 `` o/ + + 16:19 `` Thanks for the reminder, Anh. + + 16:19 `` Feel free to interject at any time. Our typical format is the following: Previous Actions, Recent Changes, In-progress Development, Office Hours (~30 mins). + + 16:21 `` For this, and subsequent, status meetings I proposed we add a new topic: Ongoing Community Charter which would give context on the new trello lane we added at the cloud-init summit. + + 16:21 `` Odd_Bloke: rharper AnhVoMSFT does that sound good? We can then better advertise and remind about long-term community involvement projects that are available for anyone + + 16:22 `` I would propose that the last agenda item of any status meeting would be to update the banner to reflect the next status meeting - and perhaps the next ETA for next release / SRU + + 16:22 `` +1 AnhVoMSFT that sounds good too. + + 16:22 `` yep, sounds good on the Community Charter + + 16:22 `` AnhVoMSFT: +1 + + 16:22 `` I think one topic each + + 16:22 `` and end with the next status meeting + + 16:23 `` ok starting to turn the meeting crank + + 16:23 `` \#topic Previous Actions + + 16:23 `` last meeting was 09/09/2019 + + 16:23 `` \#link [https://cloud-init.github.io/status-2019-09-09.html\#status-2019-09-09](https://cloud-init.github.io/status-2019-09-09.html\#status-2019-09-09) + + 16:23 `` meeting minutes at the link above ^ + + 16:24 `` only action was \#action blackboxsw send email to the list notifying of status meeting day change. + + 16:24 `` which was done [https://lists.launchpad.net/cloud-init/msg00224.html](https://lists.launchpad.net/cloud-init/msg00224.html) + + 16:24 `` no further outstanding actions from last meeting + + 16:25 `` \#topic Recent Changes + + 16:25 `` The following branches have landed in tip since last meeting: via git log --since 2019-09-09 + + 16:27 `` - Add RbxCloud datasource [Adam Dobrawy] + + 16:27 `` - get_interfaces: don't exclude bridge and bond members (LP: \#1846535) + + 16:27 `` - Add support for Arch Linux in render-cloudcfg [Conrad Hoffmann] + + 16:27 `` - util: json.dumps on python 2.7 will handle UnicodeDecodeError on binary + + 16:27 `` (LP: \#1801364) + + 16:27 `` Launchpad bug 1846535 in cloud-init "cloud-init 19.2.36 fails with python exception "Not all expected physical devices present ..." during bionic image deployment from MAAS" [Critical,Fix committed] [https://launchpad.net/bugs/1846535](https://launchpad.net/bugs/1846535) + + 16:27 `` Launchpad bug 1801364 in cloud-init "persisting OpenStack metadata fails" [Undecided,Fix committed] [https://launchpad.net/bugs/1801364](https://launchpad.net/bugs/1801364) + + 16:27 `` oopsie daisy + + 16:27 `` :) + + 16:27 `` got kicked on flood. chunking that now + + 16:27 `` - Add RbxCloud datasource [Adam Dobrawy] + + 16:27 `` - get_interfaces: don't exclude bridge and bond members (LP: \#1846535) + + 16:27 `` - Add support for Arch Linux in render-cloudcfg [Conrad Hoffmann] + + 16:27 `` - util: json.dumps on python 2.7 will handle UnicodeDecodeError on binary + + 16:27 `` (LP: \#1801364) + + 16:27 `` - debian/ubuntu: add missing word to netplan/ENI header (LP: \#1845669) + + 16:27 `` - ovf: do not generate random instance-id for IMC customization path + + 16:27 `` Launchpad bug 1845669 in cloud-init "The meaning of "Changes to it will not persist across an instance." in 50-cloud-init.yaml is unclear" [Undecided,Fix committed] [https://launchpad.net/bugs/1845669](https://launchpad.net/bugs/1845669) + + 16:27 `` - sysconfig: only write resolv.conf if network_state has DNS values + + 16:27 `` (LP: \#1843634) + + 16:27 `` - sysconfig: use distro variant to check if available (LP: \#1843584) + + 16:27 `` - systemd/cloud-init.service.tmpl: start after wicked.service + + 16:27 `` Launchpad bug 1843634 in cloud-init (Suse) "cloud-init misconfigure the network on SLES" [Undecided,Incomplete] [https://launchpad.net/bugs/1843634](https://launchpad.net/bugs/1843634) + + 16:27 `` [Robert Schweikert] + + 16:27 `` - docs: fix zstack documentation lints + + 16:28 `` Launchpad bug 1843584 in cloud-init "cloudinit/net/sysconfig.py lacks support for openSUSE 15.x and Tumbleweed" [Medium,Fix committed] [https://launchpad.net/bugs/1843584](https://launchpad.net/bugs/1843584) + + 16:28 `` - analyze/show: remove trailing space in output + + 16:28 `` - Add missing space in warning: "not avalid seed" [Brian Candler] + + 16:28 `` - pylintrc: add 'enter_context' to generated-members list + + 16:28 `` - Add datasource for ZStack platform. [Shixin Ruan] (LP: \#1841181) + + 16:28 `` - docs: organize TOC and update summary of project [Joshua Powers] + + 16:28 `` - tools: make clean now cleans the dev directory, not the system + + 16:28 `` - docs: create cli specific page [Joshua Powers] + + 16:28 `` Launchpad bug 1841181 in cloud-init "add datasource for ZStack" [Low,Fix committed] [https://launchpad.net/bugs/1841181](https://launchpad.net/bugs/1841181) + + 16:28 `` - docs: added output examples to analyze.rst [Joshua Powers] + + 16:28 `` - docs: doc8 fixes for instancedata page [Joshua Powers] + + 16:28 `` - docs: clean up formatting, organize boot page [Joshua Powers] + + 16:28 `` - net: add is_master check for filtering device list (LP: \#1844191) + + 16:28 `` Launchpad bug 1844191 in cloud-init "azure advanced networking sometimes triggers duplicate mac detection" [Critical,Fix committed] [https://launchpad.net/bugs/1844191](https://launchpad.net/bugs/1844191) + + 16:28 `` - docs: more complete list of availability [Joshua Powers] + + 16:28 `` - docs: start FAQ page [Joshua Powers] + + 16:28 `` - docs: cleanup output & order of datasource page [Joshua Powers] + + 16:28 `` - Brightbox: restrict detection to require full domain match .brightbox.com + + 16:28 `` - VMWware: add option into VMTools config to enable/disable custom script. + + 16:28 `` [Xiaofeng Wang] + + 16:28 `` - net,Oracle: Add support for netfailover detection + + 16:28 `` - atomic_helper: add DEBUG logging to write_file (LP: \#1843276) + + 16:28 `` Launchpad bug 1843276 in cloud-init "cloudinit.atomic_helper.write_file should have the same logging as util.write_file" [Low,Fix committed] [https://launchpad.net/bugs/1843276](https://launchpad.net/bugs/1843276) + + 16:29 `` Thanks Brian, Shixin Ruan, Conrad Hoffmann, Adam Dobrawy and robjo for the contributions over the last month! + + 16:29 `` beyond tip commits to cloud-init the upstream team went through two SRUs of cloud-init + + 16:30 `` it's also excellent to see new datasources like the RbxCloud datasource added + + 16:31 `` cloud-init just passed validation for Ubuntu Xenial, Bionic and Disco on the 2nd SRU 19.2-36-g059d049c-0ubuntu2 + + 16:31 `` cloud-images today should have that updated revision in them I blieve + + 16:32 `` there are fixes for both Azure accelerated networking support and handling issues seen on MAAS network bridge configuration + + 16:32 `` on that note the last Azure image we had published was early September, which still didn't have the first SRU + + 16:32 `` is there something going on with the image publishing pipeline again? + + 16:33 `` AnhVoMSFT: the publishing pipeline paused while we sorted the 2nd SRU pass for maas network bridge issues introduced by 19.2-36-g059d049c-0ubuntu1 + + 16:33 `` i see - that makes sense + + 16:34 `` 19.2-36-g059d049c-0ubuntu2 was verified as fixing all support there for both Azure and MAAS datasources and the expectation is that image builds are continuing today but I'll verify that the box is ✔ there on images rebuilding + + 16:34 `` There may also be Azure-specific publication pipeline issues, which we wouldn't necessarily know about off-hand. + + 16:34 `` \#action blackboxsw verify cpc image builds are unpaused/unblocked for Azure + + 16:34 * meetingology blackboxsw verify cpc image builds are unpaused/unblocked for Azure + + 16:34 `` thx Odd_Bloke right + + 16:35 `` looks like Odd_Bloke is already on that verification internally + + 16:35 `` ok so SRU is through verification on our side. cloudimages should be getting latest version of cloud-init for Xenial, Bionic and Disco imminently + + 16:36 `` I think that is *it* for Recent Changes + + 16:36 `` \#topic In-progress Development + + 16:37 `` the SRU verification work took a bit of steam out of our current work in progress as it involved a lot of manual and upgrade scenario tests. + + 16:37 `` But, as always we try to track ongoing work in trello + + 16:37 `` \#link [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + + 16:38 `` there are a number of branches in progress that are of interest: + + 16:39 `` Azure CI for one would be a great add for cloud-init's CI infrastructure + + 16:39 `` [https://code.launchpad.net/~ahosmanmsft/cloud-init/+git/cloud-init/+merge/372957](https://code.launchpad.net/~ahosmanmsft/cloud-init/+git/cloud-init/+merge/372957) + + 16:39 `` we need to get eyes on that this week if we can + + 16:39 `` \#action cloud-init upstream review [https://code.launchpad.net/~ahosmanmsft/cloud-init/+git/cloud-init/+merge/372957](https://code.launchpad.net/~ahosmanmsft/cloud-init/+git/cloud-init/+merge/372957) + + 16:39 * meetingology cloud-init upstream review [https://code.launchpad.net/~ahosmanmsft/cloud-init/+git/cloud-init/+merge/372957](https://code.launchpad.net/~ahosmanmsft/cloud-init/+git/cloud-init/+merge/372957) + + 16:39 `` That would be great + + 16:40 `` there are also a number of freebsd branches that need to close out. + + 16:40 `` and I know Odd_Bloke has started peeking at some initial github integration for CI. + + 16:40 `` Odd_Bloke: any details you want to add about github CI at the moment? + + 16:41 `` I've started iterating on a Travis configuration to run what we currently run in our CI pipeline. + + 16:41 `` Unsurprisingly, setting up linting/unit testing was easy. + + 16:42 `` The other thing we do is run some integration testing from a built deb file. I got as far as being able to successfully sbuild the package in Travis, and ran into some initial stumbling blocks with running lxd. + + 16:42 `` That's as far as I've got, I expect to pick that work back up this week. + + 16:42 `` thanks Odd_Bloke , I've added the following card to trello for those interested. + + 16:43 `` \#link [https://trello.com/c/pqA1adVM/1195-investigate-adding-github-travis-ci-to-cloud-init](https://trello.com/c/pqA1adVM/1195-investigate-adding-github-travis-ci-to-cloud-init) + + 16:43 `` I think that about wraps in progress work. We'll tackle reviews a bit at the end of the meeting + + 16:43 `` ok next topic + + 16:44 `` \#topic Community Charter + + 16:45 `` at the cloud-init summit we decided to highlight community work in trello so that any community member with some dev cycles and interest can join in and contribute to ongoing tasks + + 16:45 `` that lane is now in trello representing low-hanging-fruit content that upstream cloud-init is interested in completing, and that anyone can commit to. + + 16:45 `` \#link [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + + 16:46 `` the lane is labelled "Community low-hanging-fruit" and currently contains a number of doc update work items as well as json schema validation extensions for each cloud-init config module + + 16:47 `` we invite everyone to participate and feel free to grab those items as they have interest + + 16:47 `` we'll revisit this topic in each meeting so folks have context + + 16:47 `` \#topic Upcoming meetings and releases + + 16:48 `` cloud-init upstream has just passed validation of cloud-init 19.2.36-*-ubuntu2 which should approved for upload into Xenial, Disco and Bionic (and queued for Eoan) + + 16:48 `` the cloud build team will be generating images for various clouds imminently and we will confirm that build pipelines are active so platforms get new bits asap + + 16:50 `` 19.3 upstream should by coming shortly, we will update the topic with the expected upstream release date and send an email to the mailing list with the estimated upstream cut + + 16:51 `` \#action upstream cloud-init email about 19.3 release date + + 16:51 * meetingology upstream cloud-init email about 19.3 release date + + 16:52 `` next meeting is Oct 22 + + 16:52 `` same bat time same bat channel + + 16:52 `` \#topic Office Hours (next ~30 mins) + + 16:52 `` we spend this time for reviews, bug triage and cloud-init discussions. + + 16:53 `` upstream devs should have eyes on this channel. Thanks everyone for tuning in + + 16:54 `` have you had a chance to discuss about the python deprecation issue, or did the SRU verification take most of the time since the summit + + 16:58 `` AnhVoMSFT: last week was vacation plus the remainder of us on sru verification . + + 17:00 `` But now we have cleared that hurdle we should we able to discuss it this week. + + 17:00 `` yep, sounds good. + + 17:01 `` \#action revisit python deprecation and report to mailinglist + + 17:01 * meetingology revisit python deprecation and report to mailinglist + + 17:01 `` Good meeting for actions + + 17:54 `` Thanks for the participation folks I'll publish minutes to github + + 17:54 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2019-10-29.md b/content/status-2019-10-29.md new file mode 100644 index 0000000..9652027 --- /dev/null +++ b/content/status-2019-10-29.md @@ -0,0 +1,454 @@ +Title: Cloud-init bi-weekly status +Date: 2019-10-29 16:20:00 UTC +Category: status-meeting-minutes +Slug: status-2019-10-29 + +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](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](https://cloud-init.github.io/status-2019-10-08.html\#status-2019-10-08) + * **LINK**: [https://lists.launchpad.net/cloud-init/msg00229.html](https://lists.launchpad.net/cloud-init/msg00229.html) + +### Recent Changes +The discussion about "Recent Changes" started at 16:36. + + +### In-progress Development +The discussion about "In-progress Development" started at 16:41. + + * **LINK**: [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + * **LINK**: [http://bit.ly/ci-reviews](http://bit.ly/ci-reviews) + * **LINK**: [https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368507](https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368507) + * **LINK**: [https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/365641](https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/365641) + +### Community Charter +The discussion about "Community Charter" started at 16:49. + + * **LINK**: [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + +### Upcoming meetings +The discussion about "Upcoming meetings" started at 16:57. + + +### Upcoming Releases +The discussion about "Upcoming Releases" started at 16:58. + + * **LINK**: [https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/](https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/) + +### Office Hours (next ~30 mins) +The discussion about "Office Hours (next ~30 mins)" started at 17:00. + + * **ACTION**: cloud-init upstream discuss where/how/if to host documentation supported cloud-init versions for debian/suse/redhat/ubuntu/freebsd etc. + * **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. + * **LINK**: [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) + * **ACTION**: mailing list update to cloud-init community about procedure/timeline for migration to github + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (130) + * tribaal (34) + * meetingology (8) + * ubot5 (7) + * Odd_Bloke (2) + * chillysurfer (1) + * rharper (0) + + + +Full Log +---------------- + + + 16:20 `` \#startmeeting Cloud-init bi-weekly status + + 16:20 `` Meeting started Tue Oct 29 16:20:09 2019 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:20 `` + + 16:20 `` Available commands: action commands idea info link nick + + 16:20 `` Boo! Welcome to the Halloween edition of cloud-init bi-weekly status meeting + + 16:20 `` \#chair rharper + + 16:20 `` Current chairs: blackboxsw rharper + + 16:20 `` \#chair Odd_Bloke + + 16:20 `` Current chairs: Odd_Bloke blackboxsw rharper + + 16:21 `` 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. + + 16:21 `` 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 + + 16:22 `` So that we don't forget, let's set the topic for next status meeting. + + 16:22 `` Odd_Bloke: rharper does 11/12 look good? + + 16:22 `` as in, no holidays etc? + + 16:25 `` ok topic updated. Any concerns we can change it and send out an email to the mailing list + + 16:26 `` 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). + + 16:26 `` \#topic Previous Actions + + 16:26 `` I have three actions from last meeting + + 16:26 `` \#link [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) + + 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. + + 16:28 `` We also established a point of contact via email for continued cloud image status updates + + 16:29 * blackboxsw cloud-init upstream review [https://code.launchpad.net/~ahosmanmsft/cloud-init/+git/cloud-init/+merge/372957](https://code.launchpad.net/~ahosmanmsft/cloud-init/+git/cloud-init/+merge/372957) . 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 + + 16:30 `` nice, good work ahosmanMSFT + + 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. [https://lists.launchpad.net/cloud-init/msg00229.html](https://lists.launchpad.net/cloud-init/msg00229.html) + + 16:30 `` \#link [https://lists.launchpad.net/cloud-init/msg00229.html](https://lists.launchpad.net/cloud-init/msg00229.html) + + 16:30 `` thx chillysurfer :) + + 16:31 `` 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 + + 16:31 `` 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 + + 16:33 `` 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 ``.`` where minor_release_number will be [1-4] + + 16:34 `` 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. + + 16:35 `` 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. + + 16:35 `` ok long-winded. But I think that was our actions from last cloud-init status meeting. + + 16:35 `` next topic + + 16:36 `` \#topic Recent Changes + + 16:37 `` The following branches have landed in tip since last meeting: via git log --since 2019-10-08 + + 16:37 `` - net/netplan: use ipv6-mtu key for specifying ipv6 mtu values + + 16:37 `` - Fix usages of yaml, and move yaml_dump to safeyaml.dumps. (LP: \#1849640) + + 16:37 `` - exoscale: Increase url_max_wait to 120s. [Chris Glass] + + 16:37 `` - net/sysconfig: fix available check on SUSE distros + + 16:37 `` [Robert Schweikert] (LP: \#1849378) + + 16:37 `` - docs: Fix incorrect Azure IMDS IP address [Joshua Powers] (LP: \#1849508) + + 16:37 `` - introduce .travis.yml + + 16:37 `` Launchpad bug 1849640 in cloud-init "security scan reported insecure yaml load method usage in latest cloud-init code" [Undecided,Fix committed] [https://launchpad.net/bugs/1849640](https://launchpad.net/bugs/1849640) + + 16:37 `` - net: enable infiniband support in eni and sysconfig renderers + + 16:37 `` [Darren Birkett] (LP: \#1847114) + + 16:37 `` Launchpad bug 1849378 in cloud-init "sysconfig renderer not detected on SLE distros" [Medium,Fix committed] [https://launchpad.net/bugs/1849378](https://launchpad.net/bugs/1849378) + + 16:37 `` - guestcust_util: handle special characters in config file [Xiaofeng Wang] + + 16:37 `` - fix some more typos in comments [Dominic Schlegel] + + 16:37 `` Launchpad bug 1849508 in cloud-init "Azure IMDS documentation wrong about IP address" [High,Fix committed] [https://launchpad.net/bugs/1849508](https://launchpad.net/bugs/1849508) + + 16:37 `` - replace any deprecated log.warn with log.warning + + 16:37 `` [Dominic Schlegel] (LP: \#1508442) + + 16:37 `` - net: handle openstack dhcpv6-stateless configuration + + 16:37 `` [Harald Jensås] (LP: \#1847517) + + 16:37 `` Launchpad bug 1847114 in cloud-init "Infiniband network devices not configured correctly on Ubuntu" [Medium,Fix committed] [https://launchpad.net/bugs/1847114](https://launchpad.net/bugs/1847114) + + 16:37 `` - Add .venv/ to .gitignore [Dominic Schlegel] + + 16:37 `` - Small typo fixes in code comments. [Dominic Schlegel] + + 16:37 `` - cloud_test/lxd: Retry container delete a few times + + 16:37 `` - Add Support for e24cloud to Ec2 datasource. (LP: \#1696476) + + 16:37 `` Launchpad bug 1508442 in python-watcherclient "LOG.warn is deprecated" [Low,In progress] [https://launchpad.net/bugs/1508442](https://launchpad.net/bugs/1508442) + + 16:37 `` Launchpad bug 1847517 in cloud-init "cloudinit/net/sysconfig.py write incorrect config for dhcp-stateless openstack subnets" [Medium,Fix committed] [https://launchpad.net/bugs/1847517](https://launchpad.net/bugs/1847517) + + 16:37 `` Launchpad bug 1696476 in cloud-init "Identification of e24cloud platform as using Ec2 datasource" [Low,Fix committed] [https://launchpad.net/bugs/1696476](https://launchpad.net/bugs/1696476) + + 16:39 `` some good incremental improvements on SuSE, FreeBSD,Ubuntu Azure, Ec2, OpenStack and Exoscale + + 16:40 `` Thanks Dominic, Robert, XiaoFeng, Harald and Darren and Scott for the contibutions this round! + + 16:41 `` \#topic In-progress Development + + 16:41 `` \#link [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + + 16:42 `` We keep track of most of cloud-init's development efforts on the cloud-init and curtin trello board above. + + 16:43 `` And the active review queue for cloud-init is a good representation of what should land shortly. + + 16:43 `` \#link [http://bit.ly/ci-reviews](http://bit.ly/ci-reviews) + + 16:44 `` The following work-streams are currently in progress: + + 16:44 `` - CI for Azure (thanks ahosmanMSFT) + + 16:44 `` - Openstack networking v2 support (which allows openstack to talk v2 network config 'netplan' ) + + 16:45 `` - Azure async disk mounts + + 16:45 `` - cloud-init boot performance improvements + + 16:46 `` As features related to those streams make progress we'll be updating the trello board and dragging cards to the done lane + + 16:47 `` There are also a number of branches for FreeBSD support up that we need to shepherd and merge I think + + 16:48 `` \#link [https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368507](https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368507) + + 16:48 `` \#link [https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/365641](https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/365641) + + 16:48 `` We'll be able to review some of the outstanding branches during Office hours today + + 16:49 `` \#topic Community Charter + + 16:50 `` 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. + + 16:51 `` 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 + + 16:51 `` \#link [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + + 16:52 `` Our current community goal is to scrub, update and correct all datasource docs seen @ [https://cloudinit.readthedocs.io/en/latest/topics/datasources.html](https://cloudinit.readthedocs.io/en/latest/topics/datasources.html) + + 16:52 `` That's nice! + + 16:52 `` all help is appreciated especially from the datasource owners + + 16:52 `` \o tribaal. + + 16:52 `` o/ + + 16:53 `` sorry, I'm following along, didn't mean to interrupt + + 16:53 `` 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. + + 16:55 `` There are around 50 modules that would need a jsonschema definition so that we can promote our `cloud-init devel schema` command to it can properly vet any \#cloud-config a user provides to annotate user errors + + 16:55 `` 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 + + 16:56 `` example [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) + + 16:56 `` no worries, interruptions welcome + + 16:56 `` think that about wraps up community charter. + + 16:56 `` two to topics to go + + 16:57 `` \#topic Upcoming meetings + + 16:57 `` 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 + + 16:58 `` \#topic Upcoming Releases + + 16:59 `` 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 + + 16:59 `` Immediately after release, we'll publish to Ubuntu's devel release Focal Fossa and our copr repo + + 16:59 `` nice! this answers one of the questions I had coming in today :) + + 16:59 `` \#link [https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/](https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/) + + 16:59 `` good deal tribaal + + 17:00 `` and again, upstream will schedulae 19.4 release probably ~6 weeks after 19.3 so not long to wait if folks miss 19.3 + + 17:00 `` *schedule* even + + 17:00 `` \#topic Office Hours (next ~30 mins) + + 17:01 `` 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 + + 17:02 `` blackboxsw: I suspect the plan for y'all is to SRU 19.3 into the various Ubuntues after it lands in focal? + + 17:03 `` my latest bugfix, although small, impacts one of our customers so I'd like to give them a heads up in that direction + + 17:03 `` tribaal: yep sorry, I mentioned earlier, but should have mentioned in the last topic + + 17:03 `` no worries + + 17:03 `` it's the logical follow-up to a release - so it was surely implied + + 17:04 `` 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 + + 17:04 `` blackboxsw: do you know how/when cloud-init lands in other distros, as a matter of curiosity? + + 17:04 `` I think now that Ubuntu Eoan is released and post-release dust is settling we'll have bandwidth to cover that + + 17:05 `` tribaal: robjo knows for SLES. otubo (hrm not here today) is managing RHEL/CentOS release schedules + + 17:06 `` and debian is trying to shore up to 19.X I believe. + + 17:06 `` ack + + 17:06 `` but I think other distros are delayed (for good reasons: testing/validation/stability/etc). + + 17:07 `` sure, that would make sense + + 17:07 `` more QA is good :) + + 17:07 * blackboxsw finds myself wanting a current support matrix on cloudinit.readthedocs.io + + 17:07 `` or somewhere + + 17:07 `` that would be incredibly useful to us :) + + 17:08 `` agreed. Maybe we can take an action to at least discuss what that would look like (and where to host it) + + 17:08 `` tracking where and when our new datasource is available is a bit of a mystery right now :) + + 17:08 `` (except for Ubuntus) + + 17:09 `` \#action cloud-init upstream discuss where/how/if to host documentation supported cloud-init versions for debian/suse/redhat/ubuntu/freebsd etc. + + 17:09 * meetingology cloud-init upstream discuss where/how/if to host documentation supported cloud-init versions for debian/suse/redhat/ubuntu/freebsd etc. + + 17:09 `` blackboxsw: another question since I have the mic: would it be useful to you to add us to your CI pipeline? + + 17:09 `` 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 + + 17:11 `` 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) + + 17:11 `` 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 + + 17:12 `` tribaal: yeah let me restate the action then + + 17:12 `` \#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. + + 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. + + 17:12 `` per scheduling we at least could start filling in some gaps there on cloud-init planned distro releases + + 17:13 `` 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). + + 17:13 `` is that something we can do ourselves? + + 17:13 `` (code wise at least) + + 17:14 `` tribaal: codewise, if you are talking about manual tests, we generally run something like the following: + + 17:14 `` \#link [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) + + 17:15 `` if you wanted to write up an example manual sru test and propose it to [https://github.com/cloud-init/ubuntu-sru/](https://github.com/cloud-init/ubuntu-sru/) + + 17:15 `` you could follow the examples in [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) + + 17:15 `` oops wrong paste + + 17:15 `` you could follow the examples in : [https://github.com/cloud-init/ubuntu-sru/tree/master/sru-templates/manual](https://github.com/cloud-init/ubuntu-sru/tree/master/sru-templates/manual) + + 17:16 `` oh, I see + + 17:16 `` so thankfully it's only manual in the "manually run a script" sense :) + + 17:16 `` 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 + + 17:17 `` yes, that would work (myself, and a handful of colleagues would be happy to I guess) + + 17:17 `` 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 [https://code.launchpad.net/~ahosmanmsft/cloud-init/+git/cloud-init/+merge/372957](https://code.launchpad.net/~ahosmanmsft/cloud-init/+git/cloud-init/+merge/372957) + + 17:18 `` having the cloud_tests platform definition would allow us our you to more easily extend a jenkins CI job to drive the cloud tests + + 17:19 `` ah nice, that makes sense + + 17:19 `` 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. + + 17:20 `` yeah that sounds like a good first step, and we can expand later on if/when needed + + 17:24 `` +1 tribaal + + 17:24 `` btw good deal that you were able to run into Odd_Bloke on your travels. Always good to see a familiar face + + 17:24 `` yeah that was a crazy coincidence + + 17:25 `` my brother got married in Odd_Bloke 's backyard :) + + 17:25 `` I wish we could do cross-company colocated sprints :P + + 17:26 `` heh, I think we can call those \#cloud-init-summits :) + + 17:26 `` ohhh yeah :) + + 17:26 `` when's the next one? + + 17:26 `` we'll have to get invites together for the next one (Fall 2020) + + 17:27 `` noted :) + + 17:29 `` Ohh right and BIG NEWS that I forgot to highlight: cloud-init *is* moving from launchpad to github. We discussed this at the last cloud-init summit a couple of weeks ago. + + 17:29 `` Odd_Bloke: and rharper have been working on getting initial travis.yml together for allowing travis to run our CI tests. + + 17:30 `` ohhh big news indeed! + + 17:30 `` That has, indeed, landed. You can see it at [https://github.com/cloud-init/cloud-init/blob/master/.travis.yml](https://github.com/cloud-init/cloud-init/blob/master/.travis.yml) (it's also in the Launchpad git repo, we're still syncing from there to GH ATM :). + + 17:31 `` And you can see that we're green at [https://travis-ci.org/cloud-init/cloud-init](https://travis-ci.org/cloud-init/cloud-init) + + 17:31 `` 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 @ [https://github.com/cloud-init/cloud-init](https://github.com/cloud-init/cloud-init) instead of posting branch review requests at [https://git.launchpad.net/cloud-init](https://git.launchpad.net/cloud-init) + + 17:31 `` very nice! + + 17:33 `` 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 + + 17:33 `` ah that would make sese yeah + + 17:34 `` 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 + + 17:35 `` \#action mailing list update to cloud-init community about procedure/timeline for migration to github + + 17:35 * meetingology mailing list update to cloud-init community about procedure/timeline for migration to github + + 17:36 `` 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 + + 17:36 `` thanks Odd_Bloke and rharper for all the work there so far + + 17:38 `` 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. + + 17:38 `` thanks for participating chillysurfer & tribaal + + 17:38 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2019-11-26.md b/content/status-2019-11-26.md new file mode 100644 index 0000000..1a3057a --- /dev/null +++ b/content/status-2019-11-26.md @@ -0,0 +1,402 @@ +Title: Cloud-init bi-weekly status +Date: 2019-11-26 17:23:00 UTC +Category: status-meeting-minutes +Slug: status-2019-11-26 + +Meeting information +---------------- + * \#cloud-init: Cloud-init bi-weekly status, 26 Nov at 17:23 — 19:00 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-11-26-17.23.log.html](http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-11-26-17.23.log.html)]] + + + +Meeting summary +---------------- + +### Previous Actions +The discussion about "Previous Actions" started at 17:28. + + * **LINK**: [https://cloud-init.github.io/status-2019-10-29.html\#status-2019-10-29](https://cloud-init.github.io/status-2019-10-29.html\#status-2019-10-29) + * **LINK**: [https://lists.launchpad.net/cloud-init/msg00231.html](https://lists.launchpad.net/cloud-init/msg00231.html) + * **LINK**: [https://cloudinit.readthedocs.io/en/latest/topics/hacking.html](https://cloudinit.readthedocs.io/en/latest/topics/hacking.html) + +### Recent Changes +The discussion about "Recent Changes" started at 17:36. + + +### In-progress Development +The discussion about "In-progress Development" started at 17:39. + + * **LINK**: [https://bugs.launchpad.net/cloud-init/+bug/1854084](https://bugs.launchpad.net/cloud-init/+bug/1854084) + * **LINK**: [https://github.com/canonical/cloud-init/pull/48](https://github.com/canonical/cloud-init/pull/48) + * **LINK**: [https://github.com/canonical/cloud-init/pull/47](https://github.com/canonical/cloud-init/pull/47) + +### Community Charter +The discussion about "Community Charter" started at 17:46. + + * **LINK**: [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + +### Upcoming Meetings +The discussion about "Upcoming Meetings" started at 17:52. + + +### Office Hours (next ~30 mins) +The discussion about "Office Hours (next ~30 mins)" started at 17:52. + + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (124) + * ubot5 (16) + * ahosmanMSFT (5) + * meena (5) + * chillysurfer (5) + * meetingology (4) + * Goneri (1) + * Odd_Bloke (0) + + + +Full Log +---------------- + + + 17:23 `` \#startmeeting Cloud-init bi-weekly status + + 17:23 `` Meeting started Tue Nov 26 17:23:40 2019 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 17:23 `` + + 17:23 `` Available commands: action commands idea info link nick + + 17:24 `` \#chair Odd_Bloke + + 17:24 `` Current chairs: Odd_Bloke blackboxsw + + 17:24 `` Hi folks welcome to another cloud-init status meeting. + + 17:24 `` 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. + + 17:25 `` And as you've likely heard, we are shifting this meeting by +1 hr for the season to avoid meeting collisions with some of the upstream devs + + 17:25 `` I'll set the topic for next meeting so we don't forget + + 17:28 `` so Dec 10th, two weeks from today, same time as today + + 17:28 `` without further ado, let's jump into things + + 17:28 `` 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). + + 17:28 `` \#topic Previous Actions + + 17:28 `` I'm going from our last meeting minutes at the following url + + 17:28 `` \#link [https://cloud-init.github.io/status-2019-10-29.html\#status-2019-10-29](https://cloud-init.github.io/status-2019-10-29.html\#status-2019-10-29) + + 17:29 `` blackboxsw to 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. + + 17:29 `` I did forward the proper Microsoft channel contact to other Microsoft dev teams working on cloud-init + + 17:30 `` so I think thats COMPLETE + + 17:31 `` Also to note is that cloud image builds though are still stale for Azure & Ec2 on focal. There are a couple of bugs in the image build process that Canonical's cloud image team is sorting to get those image builders unblocked + + 17:31 `` Xenial, Bionic, Eoan images all look up to date + + 17:32 `` bug reports and issues are still going to be reported through launchpad right? + + 17:32 `` previous-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. Resolved. Upstream decided that it was going to be a bit of a maintenance cost to have a full table of all distributions and all versions of cloud-init as well as the planned support plan. + + 17:32 `` chillysurfer: +1 yes please do. file away and we'll tackle that + + 17:32 `` blackboxsw: great thanks! + + 17:33 `` previous-action: mailing list update to cloud-init community about procedure/timeline for migration to github. rharper took care of that per + + 17:33 `` \#link [https://lists.launchpad.net/cloud-init/msg00231.html](https://lists.launchpad.net/cloud-init/msg00231.html) + + 17:34 `` Again for folks, we have moved cloud-init upstream to github for code and CI. Launchpad still being used for package build recipes and bugs/ issues + + 17:35 `` If you have signed the CLA (thanks ahosmanMSFT) then we need to link your github account to the Lauchpad username you signed the CLA with. See the hacking doc for more information + + 17:35 `` \#link [https://cloudinit.readthedocs.io/en/latest/topics/hacking.html](https://cloudinit.readthedocs.io/en/latest/topics/hacking.html) + + 17:35 `` Think that wraps actions. + + 17:36 `` \#topic Recent Changes + + 17:36 `` I've been very slowly working towards better freebsd support + + 17:37 `` The following branches have landed in tip since last meeting: via git log --since 10.29.2019 + + 17:37 `` Goneri has moved his network patch over to github, and a NetBSD patch, tok + + 17:37 `` - tools: migrate-lp-user-to-github removes repo_dir if created (\#35) + + 17:37 `` - Correct jumbled documentation for cc_set_hostname module (\#64) + + 17:37 `` [do3meli] (LP: \#1853543) + + 17:37 `` - FreeBSD: fix for get_linux_distro() and lru_cache (\#59) + + 17:37 `` [Igor Galić] (LP: \#1815030) + + 17:37 `` Launchpad bug 1853543 in cloud-init "jumbled documentation for cc_set_hostname module" [Undecided,Fix committed] [https://launchpad.net/bugs/1853543](https://launchpad.net/bugs/1853543) + + 17:37 `` Launchpad bug 1815030 in cloud-init "FreeBSD: Unable to determine distribution" [Undecided,Fix committed] [https://launchpad.net/bugs/1815030](https://launchpad.net/bugs/1815030) + + 17:37 `` bah got kicked. let's try that again + + 17:38 `` - tools: migrate-lp-user-to-github removes repo_dir if created (\#35) + + 17:38 `` 10:37 - Correct jumbled documentation for cc_set_hostname module (\#64) + + 17:38 `` 10:37 [do3meli] (LP: \#1853543) + + 17:38 `` 10:37 - FreeBSD: fix for get_linux_distro() and lru_cache (\#59) + + 17:38 `` 10:37 [Igor Galić] (LP: \#1815030) + + 17:38 `` 10:37 - lp-to-git-users: adding do3meli [Dominic Schlegel] + + 17:38 `` 10:37 - ec2: Add support for AWS IMDS v2 (session-oriented) (\#55) + + 17:38 `` 10:37 - tests: Fix cloudsigma tests when no dmidecode data is present. (\#57) + + 17:38 `` 10:37 - net: IPv6, accept_ra, slaac, stateless (\#51) + + 17:38 `` 10:37 [Harald] (LP: \#1806014, \#1808647) + + 17:38 `` Launchpad bug 1808647 in cloud-init "cloud-init hard codes IPV6_AUTOCONF=no, which prevents EC2 instances from getting a v6 default gateway if NetworkManager is disabled" [Medium,Fix committed] [https://launchpad.net/bugs/1808647](https://launchpad.net/bugs/1808647) + + 17:38 `` Launchpad bug 1806014 in cloud-init "[Centos] IPV6_AUTOCONF=no when using dhcp6" [Medium,Fix committed] [https://launchpad.net/bugs/1806014](https://launchpad.net/bugs/1806014) + + 17:38 `` - docs: Update the configdrive datasource links (\#44) + + 17:38 `` [Joshua Powers] (LP: \#1852461) + + 17:38 `` - lp-to-git-users: adding PengpengSun [Pengpeng Sun] + + 17:38 `` - lp-to-git-users: adding trstringer [Thomas Stringer] + + 17:38 `` - lp-to-git-users: adding hjensas [Harald Jensås] + + 17:38 `` - distro: correctly set usr_lib_exec path for FreeBSD distro (\#40) + + 17:38 `` [Igor Galić] (LP: \#1852491) + + 17:38 `` Launchpad bug 1852461 in cloud-init "Broken links in config-drive docs on RTD" [Medium,Fix committed] [https://launchpad.net/bugs/1852461](https://launchpad.net/bugs/1852461) + + 17:38 `` Launchpad bug 1852491 in cloud-init "usr_lib_exec path is wrong on FreeBSD" [Medium,Fix committed] [https://launchpad.net/bugs/1852491](https://launchpad.net/bugs/1852491) + + 17:38 `` - azure: support secondary ipv6 addresses (\#33) + + 17:38 `` - Fix metadata check when local-hostname is null (\#32) + + 17:38 `` [Mark Goddard] (LP: \#1852100) + + 17:38 `` - Merge pull request \#38 from blackboxsw/cleanup/run-ci-on-pull-request + + 17:38 `` - switch default FreeBSD salt minion pkg from py27 to py36 + + 17:38 `` [Dominic Schlegel] + + 17:38 `` Launchpad bug 1852100 in cloud-init "Cloud-init fails if metadata local-hostname is null" [Undecided,In progress] [https://launchpad.net/bugs/1852100](https://launchpad.net/bugs/1852100) + + 17:38 `` - lp-to-git-users: adding igalic [Igor Galić] + + 17:38 `` - travis: only run CI on pull requests + + 17:38 `` - add data-server dns entry as new metadata server detection [Joshua Hügli] + + 17:38 `` - lp-to-git-users: adding chrisglass [Chris Glass] + + 17:38 `` - lp-to-git-users: adding larsks [Lars Kellogg-Stedman] + + 17:38 `` - Merge pull request \#31 from raharper/fix/pycodestyle-tip + + 17:38 `` - pycodestyle: remove unused local variable + + 17:38 `` - reporting: Using a uuid to enforce uniqueness on the KVP keys. [momousta] + + 17:38 `` - docs: touchups in rtd intro and README.md + + 17:38 `` - doc: update launchpad git refs to github + + 17:38 `` - tools: migrate script needs to write tools/.lp-to-git-user + + 17:38 `` - github: drop pull-request template to prepare for migration + + 17:38 `` - tools: add migrate-lp-user-to-github script to link LP to github + + 17:38 `` - github: new basic project readme + + 17:38 `` - Release 19.3 (LP: \#1851428) + + 17:38 `` Launchpad bug 1851428 in cloud-init "Release 19.3" [Medium,In progress] [https://launchpad.net/bugs/1851428](https://launchpad.net/bugs/1851428) + + 17:38 `` - azure: support matching dhcp route-metrics for dual-stack ipv4 ipv6 + + 17:38 `` (LP: \#1850308) + + 17:38 `` - configdrive: fix subplatform config-drive for /config-drive source + + 17:38 `` [David Kindred] (LP: \#1849731) + + 17:38 `` Launchpad bug 1850308 in cloud-init "cloud-init on azure with dual stack needs to add route-metric for dhcp6 also" [High,Fix committed] [https://launchpad.net/bugs/1850308](https://launchpad.net/bugs/1850308) + + 17:38 `` Launchpad bug 1849731 in cloud-init "Introduction of subplatform around 18.5 broke ConfigDrive" [Undecided,Fix committed] [https://launchpad.net/bugs/1849731](https://launchpad.net/bugs/1849731) + + 17:39 `` - DataSourceSmartOS: reconfigure network on each boot + + 17:39 `` [Mike Gerdts] (LP: \#1765801) + + 17:39 `` - Add config for ssh-key import and consuming user-data [Pavel Zakharov] + + 17:39 `` - net: fix subnet_is_ipv6() for stateless|stateful + + 17:39 `` [Harald Jensås] (LP: \#1848690) + + 17:39 `` - OVF: disable custom script execution by default [Xiaofeng Wang] + + 17:39 `` - cc_puppet: Implement csr_attributes.yaml support [Matthias Baur] + + 17:39 `` Launchpad bug 1765801 in cloud-init "network should be optionally reconfigured on every boot" [Undecided,Fix committed] [https://launchpad.net/bugs/1765801](https://launchpad.net/bugs/1765801) + + 17:39 `` - cloud-init.service: on centos/fedora/redhat wait on + + 17:39 `` NetworkManager.service (LP: \#1843334) + + 17:39 `` - azure: Do not lock user on instance id change + + 17:39 `` [Sam Eiderman] (LP: \#1849677) + + 17:39 `` Launchpad bug 1848690 in cloud-init "subnet_is_ipv6() function does not work for types ipv6_dhcpv6-stateless|stateful" [Undecided,Fix committed] [https://launchpad.net/bugs/1848690](https://launchpad.net/bugs/1848690) + + 17:39 `` Launchpad bug 1843334 in cloud-init "Change location of DHCP leases in CloudStack provider as it doesn't work for RHEL8" [Medium,Fix committed] [https://launchpad.net/bugs/1843334](https://launchpad.net/bugs/1843334) + + 17:39 `` Launchpad bug 1849677 in cloud-init "azure locks existing user if instance id changes" [Medium,Fix committed] [https://launchpad.net/bugs/1849677](https://launchpad.net/bugs/1849677) + + 17:39 `` \#topic In-progress Development + + 17:40 `` Looking into this + + 17:40 `` Launchpad bug 1849677 in cloud-init "azure locks existing user if instance id changes" [Medium,Fix committed] [https://launchpad.net/bugs/1849677](https://launchpad.net/bugs/1849677) + + 17:40 `` Ubuntu bug 1849677 in cloud-init "azure locks existing user if instance id changes" [Medium,Fix committed] + + 17:40 `` As meena mentioned there is a lot of work going on to improve FreeBSD support. + + 17:40 `` Thanks do3meli and meena for that herculean effort + + 17:41 `` ahosmanMSFT: also has be working on getting Azure CI up and running. That branch will land just as soon as this meeting is over + + 17:41 `` we also have landed a significant AWS feature for IMDSv2. + + 17:42 `` It looks like we'll have a bug to sort on that front + + 17:42 `` bug report just opened up + + 17:42 `` [https://bugs.launchpad.net/cloud-init/+bug/1854084](https://bugs.launchpad.net/cloud-init/+bug/1854084) + + 17:42 `` Ubuntu bug 1854084 in cloud-init "Headers no longer passed through read_file_or_url" [Undecided,New] + + 17:42 `` thanks chillysurfer ! + + 17:43 `` will get on that today and confirm + + 17:43 `` blackboxsw: great thanks! let me know what you think when you know some things + + 17:43 `` will do + + 17:44 `` also in the "In progress" topic are the WIP branches that rharper has up to lay ground work for opting in to cloud-init hotplug support + + 17:45 `` \#link [https://github.com/canonical/cloud-init/pull/48](https://github.com/canonical/cloud-init/pull/48) + + 17:45 `` \#link [https://github.com/canonical/cloud-init/pull/47](https://github.com/canonical/cloud-init/pull/47) + + 17:45 `` we'll be trying to pull in hotplug functionality into this cycle, so expect work land on that front before 19.4 I'm guessing + + 17:45 `` sorry I mean version 20.1 + + 17:46 `` ok next topic + + 17:46 `` \#topic Community Charter + + 17:46 `` i want to test Goneri's network [https://github.com/canonical/cloud-init/pull/61](https://github.com/canonical/cloud-init/pull/61) , but a prerequisite to make that easier is [https://github.com/canonical/cloud-init/pull/42](https://github.com/canonical/cloud-init/pull/42) and it appears only rharper knows how to write tests for that part of the code + + 17:47 `` what's hotplug support mean in this context? + + 17:48 `` This Community Charter topic is a placeholder to remind anyone with some spare cycles that as a community anyone can drop in for low-hanging fruit or discrete tasks that will contribute to a better cloud-init + + 17:48 `` the community charter is currently: + + 17:48 `` 1. updated datasource docs + + 17:48 `` 2. get json schema implementation writting for each cloudinit.config.cc_*py module + + 17:49 `` meena, I can generate some prebuilt images with my last patch + + 17:49 `` those items are cards on our trello board in the community low-hanging-fruit lane that anyone grab and work + + 17:49 `` \#link [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + + 17:50 `` ... sorry meena, needed to finish my thought. so we'd like review and closure on 42? + + 17:50 `` >`>` what's hotplug support mean in this context? hotplug network device events currently would be the baseline. + + 17:51 `` so network config would be rewritten as devices show up or disappear + + 17:51 `` if someone opts into cloud-init controlling the running network config post-boot + + 17:52 `` \#topic Upcoming Meetings + + 17:52 `` as set earlier. Dec 10th for another status meeting at this hour + + 17:52 `` \#topic Office Hours (next ~30 mins) + + 17:53 `` This time is a chance for open discussions really on any cloud-init topic. bugs, issues, branches that need review etc. In the absence of other discussion, devs will be hitting the review queue to chip away at existing PRs to keep them from getting stale + + 17:56 `` blackboxsw: yes, please, 42 fix would be good + + 17:59 `` ok looking now + + 17:59 `` ahosmanMSFT: I'm landing your Azure CI first + + 18:04 `` ahosmanMSFT: would you like to provide me with a bit more information in the commit message [https://code.launchpad.net/~ahosmanmsft/cloud-init/+git/cloud-init/+merge/372957](https://code.launchpad.net/~ahosmanmsft/cloud-init/+git/cloud-init/+merge/372957) for enabling Azure integration testing? the 'commit message' in the UI will be the final message shown in cloud-init logs and it might be nice to have a bit more context + + 18:04 `` blackboxsw Adding now + + 18:04 `` thank you sir + + 18:14 `` blackboxsw take a look and let me know if I should add anything + + 18:15 `` Added Azure to cloud tests supporting upstream integration testing. This Implements the inherited platform classes, Azure configurationsto release/platform, and docs on how to run Azure CI. + + 18:44 `` meena: I may come up with an alternative suggestion to address smoser's suggestion to run dmidecode once. it's a bit of a lift though as dmidecode output isn't structured very easy to parse + + 19:00 `` ahh I should close out the meeting + + 19:00 `` Thanks folks for attending. Until next time use the IRC channel or mailing list + + 19:00 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2019-12-10.md b/content/status-2019-12-10.md new file mode 100644 index 0000000..05162f6 --- /dev/null +++ b/content/status-2019-12-10.md @@ -0,0 +1,278 @@ +Title: Cloud-init bi-weekly status +Date: 2019-12-10 17:17:00 UTC +Category: status-meeting-minutes +Slug: status-2019-12-10 + +Meeting information +---------------- + * \#cloud-init: Cloud-init bi-weekly status, 10 Dec at 17:17 — 18:16 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-12-10-17.17.log.html](http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-12-10-17.17.log.html)]] + + + +Meeting summary +---------------- + +### Previous Actions +The discussion about "Previous Actions" started at 17:22. + + * **LINK**: [https://cloud-init.github.io/status-2019-11-26.html\#status-2019-11-26](https://cloud-init.github.io/status-2019-11-26.html\#status-2019-11-26) + +### Recent Changes +The discussion about "Recent Changes" started at 17:28. + + +### In-progress Development +The discussion about "In-progress Development" started at 17:31. + + * **LINK**: [https://lists.launchpad.net/cloud-init/msg00236.html](https://lists.launchpad.net/cloud-init/msg00236.html) + * **LINK**: [https://cloudinit.readthedocs.io/en/latest/topics/hacking.html](https://cloudinit.readthedocs.io/en/latest/topics/hacking.html) + +### Community Charter +The discussion about "Community Charter" started at 17:40. + + * **LINK**: [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + +### Office Hours (next ~30 mins) +The discussion about "Office Hours (next ~30 mins)" started at 17:45. + + * **LINK**: [https://git.io/JeVed](https://git.io/JeVed) + * **ACTION**: rharper confirm no concerns on [https://github.com/canonical/cloud-init/pull/42](https://github.com/canonical/cloud-init/pull/42) and that PR can land. + * **ACTION**: upstream core-devs to decide about whether a PR can land if any upstream dev still has 'requested changes' + + + +Vote results +---------------- + + + + +Action items, by person +---------------- + + * rharper + * rharper confirm no concerns on [https://github.com/canonical/cloud-init/pull/42](https://github.com/canonical/cloud-init/pull/42) and that PR can land. + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (79) + * meetingology (7) + * meena (5) + * ubot5 (3) + * Odd_Bloke (2) + * rharper (1) + + + +Full Log +---------------- + + + 17:17 `` \#startmeeting Cloud-init bi-weekly status + + 17:17 `` Meeting started Tue Dec 10 17:17:14 2019 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 17:17 `` + + 17:17 `` Available commands: action commands idea info link nick + + 17:18 `` Welcome folks to another cloud-init status meeting. Probably the last one of the year I presume due to upcoming Holidays in two weeks + + 17:18 `` \#chair rharper + + 17:18 `` Current chairs: blackboxsw rharper + + 17:18 `` \#chair Odd_Bloke + + 17:18 `` Current chairs: Odd_Bloke blackboxsw rharper + + 17:18 `` o/ + + 17:18 `` 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. + + 17:19 `` Let's start the meeting with setting the next meeting time + + 17:19 `` day/time + + 17:20 `` I think most of upstream is out the last two weeks of December. Shall we try January 7th? + + 17:20 `` Anyone opposed can voice their discontent as I remember the keystrokes to set the topic of the channel ;)_ + + 17:21 `` I also dropped 19.3 upstream release date from the channel topic as "that's soooo November" + + 17:22 `` topics for this round: Feel free to interject/suggest other topics at any time. Our typical format is the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Upcoming Meetings, Office Hours (~30 mins). + + 17:22 `` \#topic Previous Actions + + 17:22 `` \#topic Previous Actions + + 17:23 `` and oops, forgot to publish meeting minutes from last session. + + 17:23 `` doing that now. + + 17:24 `` is it meeting time or did I miss it? + + 17:25 `` meena: It's happening as we speak. + + 17:27 `` ok sorry for the delay. just pushed published meeting minutes + + 17:27 `` \#link [https://cloud-init.github.io/status-2019-11-26.html\#status-2019-11-26](https://cloud-init.github.io/status-2019-11-26.html\#status-2019-11-26) + + 17:27 `` ok so previous actions from last meeting: + + 17:28 `` no unresolved actions listed + + 17:28 `` \#topic Recent Changes + + 17:29 `` found via git log --since 11.26.2019 + + 17:29 `` - dhcp: Support RedHat dhcp rfc3442 lease format for option 121 (\#76) + + 17:29 `` [Eric Lafontaine] (LP: \#1850642) + + 17:29 `` - network_state: handle empty v1 config (\#45) (LP: \#1852496) + + 17:29 `` - Merge pull request \#94 from gaughen/patch-1 [Joshua Powers] + + 17:29 `` - removed a couple of "the"s [gaughen] + + 17:29 `` - docs: fix line length and remove highlighting [Joshua Powers] + + 17:29 `` - docs: Add security.md to readthedocs [Joshua Powers] + + 17:29 `` Launchpad bug 1850642 in cloud-init "No support for classless-static-routes on centos 7" [Medium,Triaged] [https://launchpad.net/bugs/1850642](https://launchpad.net/bugs/1850642) + + 17:29 `` - Multiple file fix for AuthorizedKeysFile config (\#60) [Eduardo Otubo] + + 17:29 `` - Merge pull request \#88 from OddBloke/travis [Joshua Powers] + + 17:29 `` - Revert "travis: only run CI on pull requests" + + 17:29 `` - doc: update links on README.md [Joshua Powers] + + 17:29 `` Launchpad bug 1852496 in cloud-init (Ubuntu) "nocloud network-config mishandles empty config" [Low,In progress] [https://launchpad.net/bugs/1852496](https://launchpad.net/bugs/1852496) + + 17:29 `` - doc: Updates to wording of README.md [Joshua Powers] + + 17:29 `` - Add security.md [Joshua Powers] + + 17:29 `` - setup.py: Amazon Linux sets libexec to /usr/libexec (\#52) + + 17:29 `` [Frederick Lefebvre] + + 17:29 `` - Fix linting failure in test_url_helper (\#83) [Eric Lafontaine] + + 17:29 `` - url_helper: read_file_or_url should pass headers param into readurl + + 17:29 `` (\#66) (LP: \#1854084) + + 17:29 `` - dmidecode: log result *after* stripping n [Igor Galić] + + 17:29 `` - cloud_tests: add azure platform support to integration tests + + 17:29 `` [ahosmanmsft] + + 17:29 `` Launchpad bug 1854084 in cloud-init "Headers no longer passed through read_file_or_url" [Undecided,Fix committed] [https://launchpad.net/bugs/1854084](https://launchpad.net/bugs/1854084) + + 17:31 `` thanks for all the FreeBSD work landing, utility improvements, caching and doc changes. + the dhcp lease format updates + + 17:31 `` \#topic In-progress Development + + 17:32 `` Generally upstream is doing a fair job of getting reviews to the community for PRs, though lately we've been spending a few cycles on SRU validation for cloud-init 19.4.31 into Ubuntu Xenial, Bionic, Disco and Eoan. + + 17:32 `` expectation is that we should be able to clear this SRU validation today/tomorrow and get back onto the review queue in github for cloud-init + + 17:33 `` most major cloud-platforms have passed validation with no regressions, so risk is low with this release + + 17:34 `` oops cloud-init 19.3.41 not 19.4.31 + + 17:35 `` there is plenty of work in flight by meena (FreeBSD improvements) and ahosmanMSFT (Azure instance-id work). that we hope to get reviewed and landed. + + 17:36 `` community notice: Reminder we are working toward a 19.4 upstream release by end of year. So if there are bits/features that you hope to make the cut. please get those branches in shape by next tuesday Decemeber 17th + + 17:36 `` \#link [https://lists.launchpad.net/cloud-init/msg00236.html](https://lists.launchpad.net/cloud-init/msg00236.html) + + 17:37 `` community notice: Also a reminder that cloud-inig 19.4 will be the last release that claims official support for py2.7 + + 17:37 `` in January, tip of cloud-init will be allowed to drift from python2.7 support and tox -e py27 will no longer be exercised by upstream CI + + 17:38 `` Odd_Bloke: or rharper anyything else in-progress at the moment? + + 17:39 `` also, anyone interested in cloud-init development, please run tools/migrate-lp-user-to-github as mentioned in the hacking guide to make sure we can account for the CLA (contributor license agreement) for cloud-init + + 17:39 `` \#link [https://cloudinit.readthedocs.io/en/latest/topics/hacking.html](https://cloudinit.readthedocs.io/en/latest/topics/hacking.html) + + 17:40 `` \#topic Community Charter + + 17:40 `` reminder on 19.4 release covered above, and getting your github account authorized for cloud-init conributions.... + + 17:41 `` Nothing from me! + + 17:41 `` goneri and i have been working on / testing his freebsd render + + 17:42 `` for folks with time to burn and bite-sized branches/fixes. we've got a lane on our trello board that gives a variety of fixes that the community can grab if they are looking for quick suggestions. "Community low-hanging fruit" + + 17:42 `` \#link [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + + 17:42 `` meena: Goneri yes and thanks for the continued efforts there. A lot of good is coming out for cloud-init upstream as a result. + + 17:42 `` Goneri removed a lot of code, but from what i gather, that code is still used elsewhere + + 17:43 `` could someone explain why our where our how + + 17:43 `` as always, any community member is encouraged to review other PRs from devs. All reviews and input welcome. + + 17:44 `` meena: I'm not sure I follow, are you referring to a specific branch? + + 17:44 `` or just where stale snapshots or cloud-init code lives on certain distros? + + 17:45 `` \#topic Office Hours (next ~30 mins) + + 17:45 `` might as well kick the topic and open office hours for general cloud-init discussions, questions, bug/feature work etc. + + 17:46 `` some upstream devs will have eyes/time available for discussion around anything cloud-init. This time will also be spent grooming the active review queue @ [https://git.io/JeVed](https://git.io/JeVed) + + 17:46 `` \#link [https://git.io/JeVed](https://git.io/JeVed) + + 17:48 `` blackboxsw: [https://github.com/canonical/cloud-init/pull/61\#pullrequestreview-329139891](https://github.com/canonical/cloud-init/pull/61\#pullrequestreview-329139891) + + 17:48 `` checking + + 17:52 `` meena: so Distro._bring_up_interface() is called by Distro._bring_up_interfaces() base class via Distro.apply_network + + 17:59 `` which is called from Init.apply_network_config which gets run during "cloud-init init" when network is brought up + + 18:06 `` I think [https://github.com/canonical/cloud-init/pull/42](https://github.com/canonical/cloud-init/pull/42) looks ready to merge. rharper has an outstanding "changes requested" but I believe those have been fixed. rharper I'll defer to you on this one + + 18:08 `` and policy question on reviews: if we get one upstream core-dev +1 can we proceed to land the branch as long as the "changes requested" from other upstream core seem to be resolved? + + 18:09 `` I'd vote that most recent core-dev on the PR that +1's can squash merge if they see that any prior core-dev's concerns seem to be addressed + + 18:12 `` I think I'll add an action for next meeting to make sure we iron out review/merge policy so PRs don't sit stale + + 18:13 `` \#action rharper confirm no concerns on [https://github.com/canonical/cloud-init/pull/42](https://github.com/canonical/cloud-init/pull/42) and that PR can land. + + 18:13 * meetingology rharper confirm no concerns on [https://github.com/canonical/cloud-init/pull/42](https://github.com/canonical/cloud-init/pull/42) and that PR can land. + + 18:14 `` \#action upstream core-devs to decide about whether a PR can land if any upstream dev still has 'requested changes' + + 18:14 * meetingology upstream core-devs to decide about whether a PR can land if any upstream dev still has 'requested changes' + + 18:16 `` ok I *think* that about wraps the meeting. Merry Christmas, Happy Hanukkah, Happy New Year and all that good stuff. See you all online. + + 18:16 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2020-01-07.md b/content/status-2020-01-07.md new file mode 100644 index 0000000..40e5f29 --- /dev/null +++ b/content/status-2020-01-07.md @@ -0,0 +1,414 @@ +Title: Cloud-init bi-weekly status +Date: 2020-01-07 17:30:00 UTC +Category: status-meeting-minutes +Slug: status-2020-01-07 + +Meeting information +---------------- + * \#cloud-init: Cloud-init bi-weekly status, 07 Jan at 17:30 — 18:39 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-01-07-17.30.log.html](http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-01-07-17.30.log.html)]] + + + +Meeting summary +---------------- + + **LINK**: [https://cloud-init.github.io/status-2019-12-10.html\#status-2019-12-10](https://cloud-init.github.io/status-2019-12-10.html\#status-2019-12-10) +### Previous Actions +The discussion about "Previous Actions" started at 17:36. + + * **LINK**: [https://github.com/cloud-init/cloud-init/pulls](https://github.com/cloud-init/cloud-init/pulls) + +### Recent Changes +The discussion about "Recent Changes" started at 17:39. + + * **LINK**: [https://paste.ubuntu.com/p/Cwnn3SbmWQ/](https://paste.ubuntu.com/p/Cwnn3SbmWQ/) + +### In-progress Development +The discussion about "In-progress Development" started at 17:44. + + * **LINK**: [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + +### Community Charter +The discussion about "Community Charter" started at 17:51. + + * **LINK**: [https://bugs.launchpad.net/cloud-init/](https://bugs.launchpad.net/cloud-init/)?field.tag=bitesize + * **ACTION**: bbsw seed initial community charter bitesize bugs + +### Office Hours (next ~30 mins) +The discussion about "Office Hours (next ~30 mins)" started at 18:02. + + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (118) + * robjo (16) + * ubot5 (13) + * Odd_Bloke (11) + * meetingology (6) + * smoser (5) + * rharper (0) + + + +Full Log +---------------- + + + 17:30 `` \#startmeeting Cloud-init bi-weekly status + + 17:30 `` Meeting started Tue Jan 7 17:30:28 2020 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 17:30 `` + + 17:30 `` Available commands: action commands idea info link nick + + 17:30 `` \#chair Odd_Bloke + + 17:30 `` Current chairs: Odd_Bloke blackboxsw + + 17:30 `` \#chair rharper + + 17:30 `` Current chairs: Odd_Bloke blackboxsw rharper + + 17:31 `` Welcome to the first cloud-init community status meeting of 2020. 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. + + 17:31 `` usrdev: I'm not 100% sure from that description, could you file a bug using the link in the topic and attach the output of `cloud-init collect-logs` on an affected instance? + + 17:31 `` We generally have this meeting ever 2 weeks (outside of intermittent holidays)... You can always find the next scheduled meeting in the topic of this channel + + 17:31 `` Let + + 17:31 `` Let + + 17:32 `` Let's schedule the next meeting now as well + + 17:32 `` Any objections to Jan 21 ? + + 17:33 `` Look I'm not late ;) + + 17:33 `` ok topic set for next meeting + + 17:33 `` nope, just me robjo :) welcome to the party + + 17:33 `` as always previous meeting minutes are here. + + 17:33 `` \#link [https://cloud-init.github.io/status-2019-12-10.html\#status-2019-12-10](https://cloud-init.github.io/status-2019-12-10.html\#status-2019-12-10) + + 17:34 `` topics for this round: Feel free to interject/suggest other topics at any time. Our typical format is the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Upcoming Meetings, Office Hours (~30 mins). + + 17:34 `` The move to Tuesday creates a conflict for me for the last 15 minutes of the meeting. Generally I don't think that's an issue as we are often done in less than 1 hour, just pointing out that usually I have to leave 15 minutes early + + 17:34 `` not today ;) + + 17:36 `` +1 robjo. We'll try to keep it snappy :) and if others have conflicts we can certainly touch on shifting the schedule a bit. We generally have a conflict at 1 hr before this meeting, which is the only reason it isn't 1 hr earlier + + 17:36 `` \#topic Previous Actions + + 17:37 `` last round: rharper to confirm [https://github.com/canonical/cloud-init/pull/42](https://github.com/canonical/cloud-init/pull/42) can land. COMPLETED + + 17:37 `` action2: upstream core-devs to decide about whether a PR can land if any upstream dev still has 'requested changes' + + 17:38 `` Odd_Bloke: started writing up a spec/procedure for PR review and he is currently working on adding a documentation addition PR to [http://cloudinit.readthedocs.io](http://cloudinit.readthedocs.io) that will describe the workflow for a PR to get from proposed ->` merged. + + 17:39 `` that PR should likely be up this week for review if folks are watching our review queue + + 17:39 `` \#link [https://github.com/cloud-init/cloud-init/pulls](https://github.com/cloud-init/cloud-init/pulls) + + 17:39 `` No other actions from the previous meeting in December. + + 17:39 `` \#topic Recent Changes + + 17:40 `` recent commits that made it into tip: found via git log --since 12-10-2019 + + 17:41 `` let's see if I get throttled for spam + + 17:41 `` - freebsd: fix create_group() cmd (\#146) [Gonéri Le Bouder] + + 17:41 `` - doc: make apt_update example consistent (\#154) + + 17:41 `` - doc: add modules page toc with links (\#153) (LP: \#1852456) + + 17:41 `` - Add support for the amazon variant in cloud.cfg.tmpl (\#119) + + 17:41 `` [Frederick Lefebvre] + + 17:41 `` Launchpad bug 1852456 in cloud-init "doc: list of modules is no longer present" [Medium,Triaged] [https://launchpad.net/bugs/1852456](https://launchpad.net/bugs/1852456) + + 17:41 `` heh + + 17:41 `` - freebsd: fix create_group() cmd (\#146) [Gonéri Le Bouder] + + 17:41 `` 10:41 - doc: make apt_update example consistent (\#154) + + 17:41 `` 10:41 - doc: add modules page toc with links (\#153) (LP: \#1852456) + + 17:41 `` 10:41 - Add support for the amazon variant in cloud.cfg.tmpl (\#119) + + 17:41 `` 10:41 [Frederick Lefebvre] + + 17:41 `` 10:41 - ci: remove Python 2.7 from CI runs (\#137) + + 17:41 `` 10:41 - modules: drop cc_snap_config config module (\#134) + + 17:41 `` 10:41 - migrate-lp-user-to-github: ensure Launchpad repo exists (\#136) + + 17:41 `` 10:41 - docs: add initial troubleshooting to FAQ (\#104) [Joshua Powers] + + 17:41 `` 10:41 - doc: update cc_set_hostname frequency and descrip (\#109) + + 17:41 `` 10:41 [Joshua Powers] (LP: \#1827021) + + 17:41 `` Launchpad bug 1827021 in cloud-init "SSH Documentation should mention "Host Key"" [Medium,Triaged] [https://launchpad.net/bugs/1827021](https://launchpad.net/bugs/1827021) + + 17:41 `` - ci: emit names of tests run in Travis (\#120) + + 17:41 `` 10:41 - Release 19.4 (LP: \#1856761) + + 17:41 `` Launchpad bug 1856761 in cloud-init "Release 19.4" [Undecided,Fix released] [https://launchpad.net/bugs/1856761](https://launchpad.net/bugs/1856761) + + 17:41 `` 10:41 - rbxcloud: fix dsname in RbxCloud [Adam Dobrawy] (LP: \#1855196) + + 17:41 `` 10:41 - tests: Add tests for value of dsname in datasources [Adam Dobrawy] + + 17:41 `` 10:41 - apport: Add RbxCloud ds [Adam Dobrawy] + + 17:41 `` 10:41 - docs: Updating index of datasources [Adam Dobrawy] + + 17:41 `` Launchpad bug 1855196 in cloud-init "RBXCloud has no dsname defined, so datasource cannot be properly detected." [Low,Triaged] [https://launchpad.net/bugs/1855196](https://launchpad.net/bugs/1855196) + + 17:41 `` 10:41 - docs: Fix anchor of datasource_rbx [Adam Dobrawy] + + 17:41 `` 10:41 - settings: Add RbxCloud [Adam Dobrawy] + + 17:41 `` 10:41 - doc: specify _ over - in cloud config modules + + 17:41 `` 10:41 [Joshua Powers] (LP: \#1293254) + + 17:41 `` Launchpad bug 1293254 in cloud-init "style guide on dashes vs underscores in cloud-init" [Low,Fix released] [https://launchpad.net/bugs/1293254](https://launchpad.net/bugs/1293254) + + 17:42 `` - tools: Detect python to use via env in migrate-lp-user-to-github + + 17:42 `` [Adam Dobrawy] + + 17:42 `` - Partially revert "fix unlocking method on FreeBSD" (\#116) + + 17:42 `` - tests: mock uid when running as root (\#113) + + 17:42 `` [Joshua Powers] (LP: \#1856096) + + 17:42 `` - cloudinit/netinfo: remove unused getgateway (\#111) + + 17:42 `` - docs: clear up apt config sections (\#107) [Joshua Powers] (LP: \#1832823) + + 17:42 `` Launchpad bug 1856096 in cloud-init "unittest failure when running tests as root: no such file or dir: 'ud'" [High,Fix released] [https://launchpad.net/bugs/1856096](https://launchpad.net/bugs/1856096) + + 17:42 `` - doc: add kernel command line option to user data (\#105) + + 17:42 `` [Joshua Powers] (LP: \#1846524) + + 17:42 `` Launchpad bug 1832823 in cloud-init "docs: confusing heading "Add apt repositories"" [Low,Fix released] [https://launchpad.net/bugs/1832823](https://launchpad.net/bugs/1832823) + + 17:42 `` Launchpad bug 1846524 in cloud-init "docs: cloud-init user-data docs should mention kernel cmdline options" [Wishlist,Fix released] [https://launchpad.net/bugs/1846524](https://launchpad.net/bugs/1846524) + + 17:42 `` - config/cloud.cfg.d: update README [Joshua Powers] (LP: \#1855006) + + 17:42 `` - azure: avoid re-running cloud-init when instance-id is byte-swapped + + 17:42 `` (\#84) [AOhassan] + + 17:42 `` - fix unlocking method on FreeBSD [Igor Galić] (LP: \#1854594) + + 17:42 `` - debian: add reference to the manpages [Joshua Powers] + + 17:42 `` - ds_identify: if /sys is not available use dmidecode (\#42) + + 17:42 `` [Igor Galić] (LP: \#1852442) + + 17:42 `` Launchpad bug 1855006 in cloud-init "config/cloud.cfg.d/README says "All files" rather than "*.cfg"" [Low,Fix released] [https://launchpad.net/bugs/1855006](https://launchpad.net/bugs/1855006) + + 17:42 `` - docs: add cloud-id manpage [Joshua Powers] + + 17:42 `` - docs: add cloud-init-per manpage [Joshua Powers] + + 17:42 `` Launchpad bug 1854594 in cloud-init "lock passwd implemented wrong on FreeBSD" [Medium,Fix released] [https://launchpad.net/bugs/1854594](https://launchpad.net/bugs/1854594) + + 17:42 `` - docs: add cloud-init manpage [Joshua Powers] + + 17:42 `` - docs: add additional details to per-instance/once [Joshua Powers] + + 17:42 `` - Merge pull request \#96 from fred-lefebvre/master [Joshua Powers] + + 17:42 `` - Update doc-requirements.txt [Joshua Powers] + + 17:42 `` Launchpad bug 1852442 in cloud-init "ds-identify uses the /sys filesystem which is linux specific and non-portable" [Undecided,Fix released] [https://launchpad.net/bugs/1852442](https://launchpad.net/bugs/1852442) + + 17:42 `` - doc-requirements: add missing dep [Joshua Powers] + + 17:42 `` Ok that should do it. + + 17:42 `` maybe best to just pastebin next time + + 17:43 `` yup + + 17:43 `` lots of doc changes as you can see. dropping python 2.7 automatic testing + + 17:44 `` some additional FreeBSD enablement work landed too (thanks Goneri && meena ) + + 17:44 `` total changelog since last meeting: + + 17:44 `` \#link [https://paste.ubuntu.com/p/Cwnn3SbmWQ/](https://paste.ubuntu.com/p/Cwnn3SbmWQ/) + + 17:44 `` much better + + 17:44 `` \#topic In-progress Development + + 17:45 `` We've dusted off our shoes and will get back into using our Trello board more frequently for the immediate updates for what we are currently working. + + 17:45 `` New Year's resolution and all + + 17:45 `` \#link [https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin](https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin) + + 17:46 `` expect to see more cloud-init cards migrating through the lanes of the board. Expectation as well is that we'll drop the backlog and ideas lanes and keep the board a simple kanban of what is in progress, review and done + + 17:47 `` Also note I'm going to drop the community charter lane and create bugs for each item, tagging them 'bitesize' so that quick drivebys of developers that want to contribute can search bugs for those straightforward tasks + + 17:47 `` that said, some high level goals upstream is working: + + 17:48 `` - cloud-init one-shot daemon work + + 17:48 `` - cloud-init network hotplug handling + + 17:48 `` - boot performance improvements + + 17:49 `` - github automation and tooling improvements for expedited reviews and process + + 17:50 `` I think that plus reviewing the PR active review queues will keep folks busy for the next 2 weeks :) + + 17:51 `` we will likely be adding a cloud-init SRU into xenial, bionic, disco, eoan into the mix as well + + 17:51 `` \#topic Community Charter + + 17:52 `` So generally I'd be pointing to the trello lane "Community low hanging fruit" but I hope to convert those cards to bugs today. So let's say community ongoing efforts fall into two camps" + + 17:53 `` 1. add json schema validation to missing cloudinit/config/cc_*py modules. ( I think there are about 45 remaining modules that need json schema for syntax validation) + + 17:53 `` 2. doc scrub and update for datasources in read the docs + + 17:54 `` All of these items can easily be worked in parallel, which is why they are a good set of tasks for the greater community + + 17:55 `` Expect to find them by searching cloud-init bugs for bitesize tag + + 17:55 `` With bugs remaining in launchpad, would it be a good idea to have things like the schema validation not as bugs but issues in GitHub? + + 17:55 `` that would make them more visible IMHO + + 17:55 `` and those are not really bugs nor is it pressing + + 17:56 `` \#link [https://bugs.launchpad.net/cloud-init/](https://bugs.launchpad.net/cloud-init/)?field.tag=bitesize + + 17:57 `` robjo: good suggestion. I think we were trying to avoid the confusion of having two places for bugs (launchpad bugs and github issues) That is a good point though, and maybe it's worth a mailing list discussion to get others to weight in. + + 17:58 `` I would be -1 on enabling issues, we would spend our entire lives telling people to report in Launchpad instead. + + 17:59 `` I totally understand wanting to separate "bugs" and "development tasks", though. + + 18:00 `` But I don't think we have a _great_ way of doing that which doesn't end up with a confusing experience for bug reporters. + + 18:00 `` True that people will equate issues in GitHub with bugs and thus file problems there rather than launchpad, it's a two edged sword + + 18:00 `` right, I think designation is there. We could also add a link to community charter bugs to the top-level README.md for the github project. Just so there is a close breadcrumb in github to get to those items + + 18:01 `` Our plan is to assess how this is working in a month or two, so if it's not working well then we can figure something else out. + + 18:01 `` I think the designation of "community development tasks" is there by using bitesize tag or some equivalent + + 18:02 `` \#ACTION bbsw seed initial community charter bitesize bugs + + 18:02 * meetingology bbsw seed initial community charter bitesize bugs + + 18:02 `` \#topic Office Hours (next ~30 mins) + + 18:02 `` Well, "community development tasks" is a bit mis-leading, after all the core team should be part of the "community" right? + + 18:03 `` So everything is really a "community development tasks", just that some things are easier than others ;) + + 18:03 `` robjo: yes absolutely. right... I've seen some projects use 'goodfirstbug' or something like that too + + 18:04 `` just something to reduce the barrier to involvement for anyone wanting to contribute + + 18:05 `` and yes, core team should be accountable to work on some of those community charter tasks when time permits + + 18:05 `` Yes, I think it is important to label the "easy" stuff to help people find a place to get started + + 18:05 `` so that hopefully next cloud-init summit we can set a charter for something else + + 18:06 `` just based on experience there are a lot of people that are sensitive to wording and we don't really want to get into the bikeshedding that comes along with such situations + + 18:07 `` for those reading, office hours is a time of open and unstructured discussion. core cloud-init devs will have eyes on the channel to field questions, concerns, feature or bug discussions. Participate at will. In the absence of any ongoing discussions, upstream will groom/review the active review queue @ [https://git.io/JeVed](https://git.io/JeVed) | + + 18:09 `` Honestly losing my mind over this bug: [https://bugs.launchpad.net/cloud-init/+bug/1858615](https://bugs.launchpad.net/cloud-init/+bug/1858615) + + 18:09 `` Ubuntu bug 1858615 in cloud-init "Fail to boot when NoCloud datasource is included" [Undecided,New] + + 18:09 `` The board reboots if you use dmidecode! + + 18:10 `` smoser: As you said, that's a regression. Do you think it follows that the fix should be in cloud-init? + + 18:10 `` Because I don't know how you deal with something that broken from where we are in the stack. :/ + + 18:10 `` (Unless we think this is enough evidence that we can't reliably use dmidecode on aarch64, then I guess it is on us to stop doing that. :( ) + + 18:10 `` This was probably in the e-mail by rharper I have not yet read, but I'll ask anyway ;) + + 18:11 `` I think I had some pending merge proposals in launchpad and patches, did these "magically" make their way into GitHub? DO I need to sort out where hings were? + + 18:11 `` i've heard "board reboots if you use dmidecode" before. + + 18:12 `` and maybe even cloud-init skipped calling dmidecode on aarch64 to avoid that. + + 18:12 `` but that is sheer non-sense + + 18:12 `` Very glad that boards like this are going to be in the walls of every building in 5 years. ;) + + 18:12 `` umm..... fix your hardware ? + + 18:13 `` other dmidecode issues on other hardware here too [https://bugs.launchpad.net/qemu/+bug/1243287](https://bugs.launchpad.net/qemu/+bug/1243287) + + 18:13 `` Ubuntu bug 1243287 in QEMU "[KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail" [Undecided,Fix released] + + 18:13 `` its more forgivable because dmidecode is priviledged but i swear that all it does is *read* /dev/mem + + 18:16 `` robjo: for your pending merge proposals we'd like to see you propose against github if possible. Looking for a run of ./tools/migrate-lp-user-to-github robjo `` to get your github user included as a CLA signer + + 18:17 `` then we have Conributor License Agreement accountability and can start merging those branches on the github side + + 18:17 `` Yesh I haven't migrated to the GitHub repo.... even in 2020 the 24 hour/day limitation remains, darn it ;) + + 18:17 `` I'll get at least my migration to GitHub done this week, possibly even this afternoon + + 18:18 `` heh, absolutely, and actually I mistyped your migrate cmd: ./tools/migrate-lp-user-to-github rjschwei `` + + 18:39 `` ok think that about wraps the meeting for today. Happy new year folks! Thanks for dropping in! + + 18:39 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2020-01-21.md b/content/status-2020-01-21.md new file mode 100644 index 0000000..0dac675 --- /dev/null +++ b/content/status-2020-01-21.md @@ -0,0 +1,205 @@ +Title: Cloud-init bi-weekly status +Date: 2020-01-21 17:42:00 UTC +Category: status-meeting-minutes +Slug: status-2020-01-21 + +Meeting information +---------------- + * \#cloud-init: Cloud-init bi-weekly status, 21 Jan at 17:42 — 18:55 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-01-21-17.42.log.html](http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-01-21-17.42.log.html)]] + + + +Meeting summary +---------------- + + **LINK**: [https://cloud-init.github.io/](https://cloud-init.github.io/) +### Previous Actions +The discussion about "Previous Actions" started at 17:50. + + * **LINK**: bugs.launchpad.net/cloud-init/+bugs?field.tag=bitesize + +### Recent Changes +The discussion about "Recent Changes" started at 17:53. + + +### In-progress Development +The discussion about "In-progress Development" started at 17:57. + + +### Community Charter +The discussion about "Community Charter" started at 18:02. + + * **LINK**: [https://cloudinit.readthedocs.io/en/latest/topics/debugging.html\#manual-sru-verification-procedure](https://cloudinit.readthedocs.io/en/latest/topics/debugging.html\#manual-sru-verification-procedure) + +### Office Hours (next ~30 mins) +The discussion about "Office Hours (next ~30 mins)" started at 18:08. + + * **LINK**: [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1859725](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1859725) + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (58) + * tribaal (3) + * ubot5 (3) + * meetingology (3) + + + +Full Log +---------------- + + + 17:42 `` \#startmeeting Cloud-init bi-weekly status + + 17:42 `` Meeting started Tue Jan 21 17:42:43 2020 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 17:42 `` + + 17:42 `` Available commands: action commands idea info link nick + + 17:43 `` At long last, and a bit late. Time for a brief cloud-init status meeting + + 17:43 `` Coud-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. + + 17:44 `` You can always find the next date and time of the cloud-init status meeting in the topic of this channel. + + 17:45 `` it also serves as a reminder to me that we need to start it as I find it's easy to forget the appointment if it isn't staring us in the face. + + 17:46 `` Let's set next meeting now + + 17:48 `` our previous meeting minutes are recorded on our github site + + 17:49 `` \#link [https://cloud-init.github.io/](https://cloud-init.github.io/) + + 17:49 `` the topics we cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Upcoming Meetings, Office Hours (~30 mins). + + 17:50 `` \#topic Previous Actions + + 17:50 `` Previous \#ACTION bbsw seed initial community charter bitesize bugs ... DONE. + + 17:51 `` 'bitesize' bugs for cloud-init can be found at the following link + + 17:51 `` \#link bugs.launchpad.net/cloud-init/+bugs?field.tag=bitesize + + 17:52 `` These bugs should be easy to work in parallel as well as self-contained bits of work that any member of the community could approach as a small chunk of work + + 17:53 `` we moved from using trello board for tracking these tasks to using launchpad bugs as it eases the ability to search and grab ownership of the specific features/bugs + + 17:53 `` \#topic Recent Changes + + 17:55 `` The following commits landed in tip of master: (found by git log --since 01/07/2020) + + 17:55 `` - Add Rootbox & HyperOne to list of cloud in README (\#176) [Adam Dobrawy] + + 17:55 `` - docs: add proposed SRU testing procedure (\#167) + + 17:55 `` - util: rename get_architecture to get_dpkg_architecture (\#173) + + 17:55 `` - Ensure util.get_architecture() runs only once (\#172) + + 17:55 `` - Only use gpart if it is the BSD gpart (\#131) [Conrad Hoffmann] + + 17:55 `` - freebsd: remove superflu exception mapping (\#166) [Gonéri Le Bouder] + + 17:55 `` - ssh_auth_key_fingerprints_disable test: fix capitalization (\#165) + + 17:55 `` [Paride Legovini] + + 17:55 `` - util: move uptime's else branch into its own boottime function (\#53) + + 17:55 `` [Igor Galić] (LP: \#1853160) + + 17:55 `` - workflows: add contributor license agreement checker (\#155) + + 17:55 `` - net: fix rendering of 'static6' in network config (\#77) (LP: \#1850988) + + 17:55 `` - Make tests work with Python 3.8 (\#139) [Conrad Hoffmann] + + 17:55 `` - fixed minor bug with mkswap in cc_disk_setup.py (\#143) [andreaf74] + + 17:55 `` Launchpad bug 1853160 in cloud-init "uptime code does not work on FreeBSD with python 3" [Medium,Fix committed] [https://launchpad.net/bugs/1853160](https://launchpad.net/bugs/1853160) + + 17:55 `` Launchpad bug 1850988 in cloud-init "[Cloud-init 18.5][CentOS 7 on vSphere] Crash when configuring static dual-stack (IPv4 + IPv6) networking" [Medium,Fix committed] [https://launchpad.net/bugs/1850988](https://launchpad.net/bugs/1850988) + + 17:56 `` Thanks Adam, Conrad, andreaf74, Gonéri and meena for improving cloud-init. + + 17:57 `` \#topic In-progress Development + + 17:58 `` FreeBSD, NetBSD improvements are under heavy development, thanks meena and Goneri for all the PRs put of in that regard. + + 17:58 `` Also robjo has started work on cleanup of sysconfig net rendering per [https://github.com/canonical/cloud-init/pull/162](https://github.com/canonical/cloud-init/pull/162) and a mailing list discussion + + 17:59 `` rharper is also midstream on "cloud-init run as a daemon" mode [https://github.com/canonical/cloud-init/pull/48](https://github.com/canonical/cloud-init/pull/48) which should improve cloud-init startup times by avoiding having to reload python 4 times for each cloud-init stage + + 18:00 `` Also in progress, upstream has started to SRU testing for cloud-init 19.4.33 into Ubuntu Xenial, Bionic and Eoan. + + 18:01 `` We expect to wrap up that testing this week for a publish of cloud-init 19.4.33 to those series + + 18:02 `` \#topic Community Charter + + 18:02 `` As a note, any community member is welcome to participate in SRU testing of cloud-init if those changesets in the SRU affect your cloud platform or features. + + 18:02 `` We have added a guide for SRU testing on Ubuntu here + + 18:03 `` duly noted :) + + 18:03 `` \#link [https://cloudinit.readthedocs.io/en/latest/topics/debugging.html\#manual-sru-verification-procedure](https://cloudinit.readthedocs.io/en/latest/topics/debugging.html\#manual-sru-verification-procedure) + + 18:03 `` :) + + 18:04 `` ahh tribaal we should pull in your PR for manual testing of Exoscale too if you think it's ready [https://github.com/cloud-init/ubuntu-sru/pull/64](https://github.com/cloud-init/ubuntu-sru/pull/64) + + 18:04 `` it's not unfortunately :/ + + 18:05 `` ahh, ok *good*, thought it was waiting on review + + 18:05 `` ok can table that for another SRU (which will be around Feb 14th likely) + + 18:06 `` no worries, happy to help test the current one anyway + + 18:06 `` community notice: we are targeting Feb 18th as our cutoff for upstream cloud-init version 20.1 (which will be SRU'd to Ubuntu Xenial, bionic and Eoan). If there are features of bug fixes that you'd like to get into cloud-init 20.1 please raise them as PRs or discussion on the mailinglist or in channel + + 18:08 `` \#topic Office Hours (next ~30 mins) + + 18:08 `` This time is spent on any cloud-init feature/bug/branch discussions. quetions or concerns and topics are welcome. In the absence of topics we'll groom the review queue. + + 18:09 `` I'm wrapping up some significant change suggestions the networking stuff for sysconfig on [https://github.com/canonical/cloud-init/pull/162](https://github.com/canonical/cloud-init/pull/162) + + 18:10 `` I should have that review done in about an hour + + 18:10 `` I've added myself as the "assignee" to that PR to indicate it as priority for me + + 18:11 `` also, note in SRU testing I've run into a repeated issue with cloud-init's ssh-import-id taking 1 minute to import a single ssh pubkey on Azure bionic advanced networking vms. (2 nics + ipv6 + multiple IPs). I'll be debugging this a bit today to make sure it is not a regression for this cloud-init SRU 19.4.33 + + 18:12 `` if anyone has any feedback or issues associated with this cloud-init v 19.4.33 SRU, they can comment on the SRU bug or raise a new bug or comment in IRC + + 18:12 `` \#link [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1859725](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1859725) + + 18:12 `` Ubuntu bug 1859725 in cloud-init (Ubuntu) "sru cloud-init (19.3.41 to 19.4.33) Xenial, Bionic and Eoan" [Undecided,New] + + 18:55 `` ok, that about wraps today's status meeting. We'll have the next one February 4th to chat again about getting features ready for 20.1 + + 18:55 `` Thanks for tuning in. + + 18:55 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2020-02-04.md b/content/status-2020-02-04.md new file mode 100644 index 0000000..db48db9 --- /dev/null +++ b/content/status-2020-02-04.md @@ -0,0 +1,258 @@ +Title: Cloud-init bi-weekly status +Date: 2020-02-04 17:23:00 UTC +Category: status-meeting-minutes +Slug: status-2020-02-04 + +Meeting information +---------------- + * \#cloud-init: Cloud-init bi-weekly status, 04 Feb at 17:23 — 19:08 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-02-04-17.23.log.html](http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-02-04-17.23.log.html)]] + + + +Meeting summary +---------------- + + **LINK**: [https://cloud-init.github.io/](https://cloud-init.github.io/) +### Previous Actions +The discussion about "Previous Actions" started at 17:27. + + +### Recent Changes +The discussion about "Recent Changes" started at 17:27. + + * **LINK**: [https://paste.ubuntu.com/p/3jQdKZVPcM/](https://paste.ubuntu.com/p/3jQdKZVPcM/) + +### In-progress Development, +The discussion about "In-progress Development," started at 17:32. + + +### In-progress Development +The discussion about "In-progress Development" started at 17:32. + + * **LINK**: [https://github.com/canonical/cloud-init/pulls](https://github.com/canonical/cloud-init/pulls) + +### Community Charter +The discussion about "Community Charter" started at 17:43. + + * **LINK**: [https://bugs.launchpad.net/cloud-init/+bugs](https://bugs.launchpad.net/cloud-init/+bugs)?field.tag=bitesize + +### Office Hours (next ~30 mins) +The discussion about "Office Hours (next ~30 mins)" started at 17:47. + + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (68) + * ahosmanMSFT (10) + * meetingology (5) + * powersj (4) + * ubot5 (3) + * Odd_Bloke (0) + * rharper (0) + + + +Full Log +---------------- + + + 17:23 `` \#startmeeting Cloud-init bi-weekly status + + 17:23 `` Meeting started Tue Feb 4 17:23:28 2020 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 17:23 `` + + 17:23 `` Available commands: action commands idea info link nick + + 17:23 `` morning, afternoon and evening folks. Time for another cloud-init community status meeting + + 17:24 `` \#chair rharper + + 17:24 `` Current chairs: blackboxsw rharper + + 17:24 `` \#chair Odd_Bloke + + 17:24 `` Current chairs: Odd_Bloke blackboxsw rharper + + 17:24 `` Coud-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. + + 17:24 `` The next scheduled status meeting is always listed in the topic of this channel, so feel free to drop in on next session if you miss this one + + 17:25 `` while we're at it I'll update for next status meeting. + + 17:26 `` 2 weeks from today, same bat time, same bat channel + + 17:26 `` Our previous meeting minutes line here: + + 17:26 `` \#link [https://cloud-init.github.io/](https://cloud-init.github.io/) + + 17:26 `` *live here* rather + + 17:27 `` the topics we cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Upcoming Meetings, Office Hours (~30 mins). + + 17:27 `` new topics or intejections are always welcome + + 17:27 `` \#topic Previous Actions + + 17:27 `` From last meeting we had no unresolved actions so we can jump to the next section + + 17:27 `` \#topic Recent Changes + + 17:29 `` found from tip of master with `git log --since 01/21/2020` + + 17:29 `` - sysconfig: distro-specific config rendering for BOOTPROTO option (\#162) + + 17:29 `` [Robert Schweikert] (LP: \#1800854) + + 17:29 `` - cloudinit: replace "from six import X" imports (except in util.py) (\#183) + + 17:29 `` - run-container: use 'test -n' instead of 'test ! -z' (\#202) + + 17:29 `` [Paride Legovini] + + 17:29 `` - net/cmdline: correctly handle static ip= config (\#201) + + 17:29 `` [Dimitri John Ledkov] (LP: \#1861412) + + 17:29 `` Launchpad bug 1800854 in cloud-init "BOTOPROTO handling between RHEL/Centos/Fedora and SUSE distros is different" [Medium,Triaged] [https://launchpad.net/bugs/1800854](https://launchpad.net/bugs/1800854) + + 17:29 `` - Replace mock library with unittest.mock (\#186) + + 17:29 `` - HACKING.rst: update CLA link (\#199) + + 17:29 `` Launchpad bug 1861412 in cloud-init (Ubuntu) "cloud-init crashes with static network configuration" [Undecided,Fix committed] [https://launchpad.net/bugs/1861412](https://launchpad.net/bugs/1861412) + + 17:29 `` - Scaleway: Fix DatasourceScaleway to avoid backtrace (\#128) + + 17:29 `` [Louis Bouchard] + + 17:29 `` - cloudinit/cmd/devel/net_convert.py: add missing space (\#191) + + 17:29 `` - tools/run-container: drop support for python2 (\#192) [Paride Legovini] + + 17:29 `` - Print ssh key fingerprints using sha256 hash (\#188) (LP: \#1860789) + + 17:29 `` - Make the RPM build use Python 3 (\#190) [Paride Legovini] + + 17:29 `` Launchpad bug 1860789 in cloud-init (Ubuntu) "ssh_authkey_fingerprints must use sha256 not md5" [Undecided,Fix committed] [https://launchpad.net/bugs/1860789](https://launchpad.net/bugs/1860789) + + 17:29 `` thought we were going to use pastebin :P + + 17:29 `` heh, that is a good point (I wondered if anyone would call me on that) + + 17:30 `` \#link [https://paste.ubuntu.com/p/3jQdKZVPcM/](https://paste.ubuntu.com/p/3jQdKZVPcM/) + + 17:31 `` generally speaking, dropping use of six since our code based is not python3-only, tooling dropping py2, sysconfig rendering flavors for opensuse, doc fixes and read the docs fixups + + 17:32 `` thanks all for the contributions over the last couple weeks + + 17:32 `` \#topic In-progress Development, + + 17:32 `` \#topic In-progress Development + + 17:32 `` Any existing PRs are up for review at the following url: + + 17:33 `` \#link [https://github.com/canonical/cloud-init/pulls](https://github.com/canonical/cloud-init/pulls) + + 17:33 `` generally speaking we are in the 'long tail' part of a couple of feature-sets: + + 17:34 `` * we are trying to wrap up tooling for our automated CI, publishing processes and documentation for the shift to github from launchpad + + 17:34 `` * we are in progress on cloud-init handling network hotplug for a couple of datasources + + 17:35 `` * in progress on boot speed improvements for various platforms + + 17:36 `` We also recently validated and released cloud-init v 19.4.33 to Xenial, Bionic and Eoan (1/9/2020) + + 17:38 `` Hi @blackboxsw I'm no longer in the provisioning team, but there's an urgency for the cloud test to be resilient. Have you looked at those issues, I can dedicate as much time as needed to this. If you have time, can we tackle this today? + + 17:38 `` there are also a number of PRs in flight for FreeBSD,NetBSD, OpenSUSE and CentOS that need attention so we can better enable those distros + + 17:38 `` azurecloudtest that is + + 17:39 `` hi ahosmanMSFT I can spend some time on office hours here to peek more at it. my individual runs didn't hit the timeouts again, so we might need a reproducer cmdline from you in a new bug maybe? + + 17:39 `` So your able to run all tests successfully without timeout and image not building>` + + 17:40 `` ahosmanMSFT: but yes I can spend a little time on this today. and I think ultimately we'll have to find the tox command line that exhibits this error. I'll go checkout my test run again and see. I don't think I saw the failure. but I might be invoking tests differently than you + + 17:41 `` blackboxsw: hmm that's interesting, thanks let me know + + 17:41 `` same here ahosmanMSFT, can you file a bug with the traceback you see and the tox cmdline you are running? + + 17:41 `` then I know exactly what to look for + + 17:42 `` Sure, will do now + + 17:43 `` cool. + + 17:43 `` ok next topic + + 17:43 `` \#topic Community Charter + + 17:43 `` ok this section is reserved to raise general community work/goals. + + 17:44 `` At last cloud-init summit we raised a couple of general themes of improvements cloud-init would like to achieve + + 17:45 `` These themes fell into two categories for this year: datasource documentation updates and cloud-init json schema validation for the 50+ config modules in cloudinit/config/cc_*py so that we can better raise user-config errors and remove some of cloud-init's "sharp edges" + + 17:45 `` we converted a number of these feature requests in into bugs which can be searched here: + + 17:46 `` \#link [https://bugs.launchpad.net/cloud-init/+bugs](https://bugs.launchpad.net/cloud-init/+bugs)?field.tag=bitesize + + 17:46 `` tasks in this list should be fairly easy one-time bugs for folks with a little time available to help improve cloud-init. + + 17:47 `` we'll revisit this set of bugs/features and the community charter goals near the end of 2020 at the next cloud-init summit + + 17:47 `` \#topic Office Hours (next ~30 mins) + + 17:48 `` this time is spent with cloud-init upstream dev eyes on this channel for any cloud-init feature, bug or implementation discussions. In the absence of such discussions, we'll review the active PRs to try to tidy up the review queue and unblock developers + + 17:49 `` for the moment, I'll look over some Azure test timeouts ahosmanMSFT is seeing + + 17:49 `` any other topics, concerns, bugs, questions are welcome and someone should be around to field them + + 17:50 `` ahosmanMSFT: so timeouts running integration tests, you said you are getting them about half the time? + + 18:48 `` blackboxsw: Yes, I tracked it down to platforms/instance._wait_for_system + + 18:49 `` I invoke it after initializing vm in platform/azurecloudtest/instance.start + + 18:49 `` when removed, everything works as expected + + 18:50 `` looks like it's needed for cloud tests so thought I'd leave it to you, since I don't know how ec2/lxd/... rely on + + 18:50 `` ahosmanMSFT, can you file a bug please with the cli example? + + 18:50 `` that would help us triage and make a proper decision on what change to make + + 18:51 `` powersj, yes, was in the middle of that side tracked by meeting. On it now + + 18:51 `` thanks! + + 19:07 `` aaaand, I should probably wrap the meeting for the day. + + 19:08 `` Thanks all for the time and energy you put into improving cloud-init! See you next time, or anytime in between + + 19:08 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2020-02-18.md b/content/status-2020-02-18.md new file mode 100644 index 0000000..d8375a5 --- /dev/null +++ b/content/status-2020-02-18.md @@ -0,0 +1,195 @@ +Title: Cloud-init bi-weekly status +Date: 2020-02-18 17:35:00 UTC +Category: status-meeting-minutes +Slug: status-2020-02-18 + +Meeting information +---------------- + * \#cloud-init: Cloud-init bi-weekly status, 18 Feb at 17:35 — 18:36 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-02-18-17.35.log.html](http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-02-18-17.35.log.html)]] + + + +Meeting summary +---------------- + + **LINK**: [https://cloud-init.github.io/status-2020-02-04.html\#status-2020-02-04](https://cloud-init.github.io/status-2020-02-04.html\#status-2020-02-04) +### Previous Actions +The discussion about "Previous Actions" started at 17:37. + + +### Recent Changes +The discussion about "Recent Changes" started at 17:38. + + * **LINK**: [https://paste.ubuntu.com/p/28Y8jGTGwr/](https://paste.ubuntu.com/p/28Y8jGTGwr/) + +### In-prgoress Development +The discussion about "In-prgoress Development" started at 17:45. + + +### In-progress Development +The discussion about "In-progress Development" started at 17:45. + + +### cloud-init upstream 20.1 +The discussion about "cloud-init upstream 20.1" started at 17:49. + + +### Community Charter +The discussion about "Community Charter" started at 17:59. + + * **LINK**: [https://bugs.launchpad.net/cloud-init/+bugs](https://bugs.launchpad.net/cloud-init/+bugs)?field.tag=bitesize + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (52) + * meetingology (5) + * Odd_Bloke (3) + * smoser (0) + * rharper (0) + + + +Full Log +---------------- + + + 17:35 `` \#startmeeting Cloud-init bi-weekly status + + 17:35 `` Meeting started Tue Feb 18 17:35:26 2020 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 17:35 `` + + 17:35 `` Available commands: action commands idea info link nick + + 17:35 `` o/ hi cloud-init folks. sorry I botched being able to read calendars last time. + + 17:36 `` let's kick off our cloud-init status meeting. + + 17:36 `` notes from previous meeting are here: + + 17:36 `` \#link [https://cloud-init.github.io/status-2020-02-04.html\#status-2020-02-04](https://cloud-init.github.io/status-2020-02-04.html\#status-2020-02-04) + + 17:37 `` the topics we cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Upcoming Meetings, Office Hours (~30 mins). + + 17:37 `` today I'll add a topic for cloud-init's upstream release 20.1 + + 17:37 `` \#topic Previous Actions + + 17:38 `` Last meeting minutes show no carryover action items. So we can drop into recent changes + + 17:38 `` \#topic Recent Changes + + 17:40 `` We have about 8 commits landed in master since last meeting: found with git log --since 02-04-2020 + + 17:40 `` [https://paste.ubuntu.com/p/28Y8jGTGwr/](https://paste.ubuntu.com/p/28Y8jGTGwr/) + + 17:41 `` some doc fixes, CI fixes for Azure integration testing , swap disk support for cc_disk_setup and freebsd improvements. + + 17:42 `` thanks for contributions there all. I think we still have a long tail of improvements to review for FreeBSD and NetBSD so we'll try to keep the conversation going there.. Thanks meena and do3meli there + + 17:42 `` I mean Goneri + + 17:44 `` \#chair rharper Odd_Bloke smoser + + 17:44 `` Warning: Nick not in channel: rharper + + 17:44 `` Current chairs: Odd_Bloke blackboxsw rharper smoser + + 17:44 `` forgot to set meeting chairs. sry + + 17:45 `` \#topic In-prgoress Development + + 17:45 `` \#topic In-progress Development + + 17:47 `` Odd_Bloke: is currently wrapping up any remaining py2/p3-isms in master branch. Dropping use of 'six' throughout the code. Paride is working on copr-build failures due to the shift to python3 packages. otubo, thanks for the ping back on finding various python3 CentOS packages. We'll also try sorting this this week so cloud-init py3 builds can work on CentOS 7 and 8 + + 17:47 `` If folks didn't see the mailing list Odd_Bloke has a branch up to shift from nosetests ->` pytest [https://lists.launchpad.net/cloud-init/msg00245.html](https://lists.launchpad.net/cloud-init/msg00245.html) + + 17:48 `` we expect to land that after 20.1 releases. Thanks for the reviews there [https://github.com/canonical/cloud-init/pull/211](https://github.com/canonical/cloud-init/pull/211) + + 17:49 `` \#topic cloud-init upstream 20.1 + + 17:50 `` So, today at EOD is upstream release day for cloud-init 20.1. Just another timed release of cloud-init which we strive to make quarterly thoughout the year + + 17:50 `` As mentioned on the mailing list, if there are any branches/PRs that folks really would like to get into 20.1, please raise them here. We will scrub the review queue today and see what makes sense to land for this release. + + 17:52 `` I'll be driving the 20.1 release. + + 17:53 `` We just landed [https://github.com/canonical/cloud-init/pull/204](https://github.com/canonical/cloud-init/pull/204) into master, which is a fix for a (low priority) CVE that we wanted in before cutting the release. + + 17:54 `` I'm going to perform some testing of that change before cutting the release, to determine if any doc changes are required for it and to check if it impacts boot on Azure instances that have a password provided by the Azure fabric. + + 17:54 `` I was just looking over the PR from fred in ec2 land about handling a disabled path for IMDSv2 that looks interesting, but it still needs unit tests [https://github.com/canonical/cloud-init/pull/216/files](https://github.com/canonical/cloud-init/pull/216/files) + + 17:55 `` this would certainly help non-ec2 lookalikes + + 17:55 `` and is a fairly specific fix. + + 17:56 `` we can peek over it during the office hours and see if it makes sense. + + 17:56 `` Thanks Odd_Bloke for driving the 20.1 release. + + 17:56 `` So, again, plan is to cut 20.1 at end of day today. + + 17:58 `` What follows will be a tag and release to Ubuntu Focal to sync tip of master to Ubuntu development release + + 17:59 `` \#topic Community Charter + + 17:59 `` This topic is a placeholder to remind folks of any project-wide development tasks that we are engaging the community in. + + 18:00 `` the general theme at the moment is cloud-config schema definitions for the config modules in cloudinit/config/cc_*py and improving/correct datasource configuration documentation + + 18:00 `` We've queued this work as separate bugs in cloud-init at the following link + + 18:01 `` \#link [https://bugs.launchpad.net/cloud-init/+bugs](https://bugs.launchpad.net/cloud-init/+bugs)?field.tag=bitesize + + 18:01 `` we'll revisit this set of bugs/features and resent community charter goals near the end of 2020 at the next cloud-init summit. If there are suggestions/desires for community themed tasks please feel free to set the direction there. + + 18:02 `` these community tasks are grabbed by any contributor to cloud-init. + + 18:03 `` An example of the schema definitions we are looking to add is the PR in review here. [https://github.com/canonical/cloud-init/pull/152](https://github.com/canonical/cloud-init/pull/152) + + 18:04 `` As always, everyone's review counts. As a project we are trying to also look to 'promote' more core-contributors, with commit rights to the cloud-init project. Reviews count just much as proposing pull requests to the project. + + 18:04 `` thanks again for all the contributions, reviews and bugs that are being contributed to date. It really helps improve this project's use + + 18:05 `` \#topic Office Hours (next ~30 mins) + + 18:07 `` During this topic, please bring up any questions, discussions, bugs or features or paper cuts that need attention. there should be a couple of cloud-init developers with eyes on the channel to actively respond. + + 18:08 `` In leiu of active discussions, we'll hit up the review queue for cloud-init at [https://git.io/JeVed](https://git.io/JeVed) and get ready for the 20.1 release + + 18:09 `` I'm going to see if I can + + 18:09 `` review [https://github.com/canonical/cloud-init/pull/216/files](https://github.com/canonical/cloud-init/pull/216/files) and propose the unit test changes there + + 18:09 `` I think that could be a valid addition for ec2-lookalikes to avoid an unnecessary 2 minute timeout + + 18:09 `` on boot + + 18:19 `` hrm on 2nd thought w/ 216, I think that patch set should be more specific, such as actually testing HTTP status 403 instead of just checking if metadata was None and assuming it was disabled. I'll put a couple of review comments on that as I dig in, but probably not in a state that it could be landed today + + 18:36 `` thanks for tuning in folks. See you next time + + 18:36 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2020-03-10.md b/content/status-2020-03-10.md new file mode 100644 index 0000000..00ee0e9 --- /dev/null +++ b/content/status-2020-03-10.md @@ -0,0 +1,355 @@ +Title: Cloud-init bi-weekly status +Date: 2020-03-10 16:22:00 UTC +Category: status-meeting-minutes +Slug: status-2020-03-10 + +Meeting information +---------------- + * \#cloud-init: Cloud-init bi-weekly status, 10 Mar at 16:22 — 17:45 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-03-10-16.22.log.html](http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-03-10-16.22.log.html)]] + + + +Meeting summary +---------------- + + **LINK**: [https://cloud-init.github.io/status-2020-02-18.html\#status-2020-02-18](https://cloud-init.github.io/status-2020-02-18.html\#status-2020-02-18) +### Previous Actions +The discussion about "Previous Actions" started at 16:24. + + +### Recent Changes +The discussion about "Recent Changes" started at 16:25. + + * **LINK**: [https://wiki.ubuntu.com/FocalFossa/ReleaseSchedule](https://wiki.ubuntu.com/FocalFossa/ReleaseSchedule) + * **LINK**: [https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html\#format-of-instance-data-json](https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html\#format-of-instance-data-json) + +### In-progress Development +The discussion about "In-progress Development" started at 16:37. + + * **LINK**: [https://github.com/canonical/cloud-init/pulls](https://github.com/canonical/cloud-init/pulls) + +### Community Charter and upcoming meeting +The discussion about "Community Charter and upcoming meeting" started at 16:51. + + +### cloud-init pull-requests [https://git.io/JeVed](https://git.io/JeVed) | Meeting minutes: [https://goo.gl/mrHdaj](https://goo.gl/mrHdaj) | Next status meeting March 1 16:15 UTC | 19.4 (Dec 17) drops Py2.7 : origin/stable-19.4 | 20.1 (Feb 18) | [https://bugs.launchpad.net/cloud-init/+filebug](https://bugs.launchpad.net/cloud-init/+filebug) +The discussion about "cloud-init pull-requests [https://git.io/JeVed](https://git.io/JeVed) | Meeting minutes: [https://goo.gl/mrHdaj](https://goo.gl/mrHdaj) | Next status meeting March 1 16:15 UTC | 19.4 (Dec 17) drops Py2.7 : origin/stable-19.4 | 20.1 (Feb 18) | [https://bugs.launchpad.net/cloud-init/+filebug](https://bugs.launchpad.net/cloud-init/+filebug)" started at 16:53. + + * **LINK**: [https://bugs.launchpad.net/cloud-init/+bugs](https://bugs.launchpad.net/cloud-init/+bugs)?field.tag=bitesize + +### Office Hours (next 30 mins) +The discussion about "Office Hours (next 30 mins)" started at 16:58. + + * **LINK**: [https://github.com/canonical/cloud-init/pull/241](https://github.com/canonical/cloud-init/pull/241) + * **LINK**: [https://github.com/canonical/cloud-init/pull/241/files](https://github.com/canonical/cloud-init/pull/241/files) + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (109) + * Odd_Bloke (13) + * tribaal (5) + * meetingology (4) + * AnhVoMSFT (2) + * Goneri (2) + * powersj (1) + * smoser (0) + * rharper (0) + + + +Full Log +---------------- + + + 16:22 `` \#startmeeting Cloud-init bi-weekly status + + 16:22 `` Meeting started Tue Mar 10 16:22:58 2020 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:22 `` + + 16:22 `` Available commands: action commands idea info link nick + + 16:23 `` Hello and welcome to another cloud-init community status meeting. + + 16:23 `` our IRC channel topic carries the next planned status meeting for those that wish to participate. + + 16:23 `` All are welcome and interruptions encouraged + + 16:23 `` \#chair rharper Odd_Bloke smoser + + 16:23 `` Current chairs: Odd_Bloke blackboxsw rharper smoser + + 16:23 `` Previous meeting notes are here + + 16:23 `` \#link [https://cloud-init.github.io/status-2020-02-18.html\#status-2020-02-18](https://cloud-init.github.io/status-2020-02-18.html\#status-2020-02-18) + + 16:24 `` he topics we cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Upcoming Meetings, Office Hours (~30 mins). + + 16:24 `` *the even + + 16:24 `` o/ + + 16:24 `` \#topic Previous Actions + + 16:24 `` \O + + 16:24 `` sorry, have my big head on + + 16:24 `` o/ + + 16:25 `` :). Last meeting had no actions carried over. So I think this topic is a noop this week + + 16:25 `` \#topic Recent Changes + + 16:26 `` recent changes landed in tip of master via git log --since 2020-02-18 [https://paste.ubuntu.com/p/sJVpvjFbPj/](https://paste.ubuntu.com/p/sJVpvjFbPj/) + + 16:27 `` we've added some tooling/actions for github, ec2 IMDSv2 token redacting from logs, alloowing kernel cmdline to tell cloud-init network-config=disabled and not falling back to IMDSv1 on Ec2-proper platform + + 16:28 `` thanks fred-lefebvre for the ec2 IMDS fallback branch and others for some additional driveby doc updates + + 16:29 `` Also, we performed an upload to Ubuntu Focal (20.04) series with latest tip of cloud-init to make sure the development release is up to date with recent features + + 16:30 `` Ubuntu Focal release is currently in feature freeze, so that will affect what patches we pull into Ubuntu Focal at this time as 'new features' would need a Feature Freeze Exception during the stage of Ubuntu development. + + 16:30 `` \#link [https://wiki.ubuntu.com/FocalFossa/ReleaseSchedule](https://wiki.ubuntu.com/FocalFossa/ReleaseSchedule) + + 16:31 `` As Odd_Bloke alluded to just before this meeting, we are trying to keep tip of master + + 16:31 `` open for commits. + + 16:32 `` On the ubuntu-side of the house we will sort cherry picking bug fixes into ubuntu focal during this short feature freeze period of time + + 16:33 `` If there are significant features that your cloud platform really would like to see on the first public release of Ubuntu Focal, then please get ahold of us in channel of on the mailing list to suggest that we shepherd those features in during this freeze. + + 16:33 `` But, generally cloud-init team will continue to follow the SRU process to get updates into Focal after feature freeze is lifted. + + 16:35 `` and again, our SRU test/verification process for Ubuntu will continue to target Xenial, Bionic, Eoan and Focal series for the updates we plan to make in the near future + + 16:37 `` one thing to note in recent changes as well is that we've now added the ability to query distro, kernel, cpu arch, python runtime version and and merged cloud-config to cloud-config jinja templates. So \#cloud-config userdata can be opinionated based on your target distribution or runtime environment. + + 16:37 `` \#link [https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html\#format-of-instance-data-json](https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html\#format-of-instance-data-json) + + 16:37 `` I think that about wraps recent changes + + 16:37 `` \#topic In-progress Development + + 16:38 `` \#link [https://github.com/canonical/cloud-init/pulls](https://github.com/canonical/cloud-init/pulls) + + 16:38 `` our active pulls above is probably the best source of info on features/bugfixes in flight. + + 16:39 `` Though behind the scenes we have held a couple of meetings to determine how much more automation/tooling we need to clean up to improve our github developer process + + 16:39 `` I think Odd_Bloke and I have around 4 PRs that we are hoping to clean up to get a couple of things in place: + + 16:40 `` foremost I believe Odd_Bloke is scrubbing the github review process PR so that we have a good starting point for expectations for every developer, author or committer. + + 16:42 `` I think ultimately the goal there is to make sure committers can provide a set of expectations on active PR reviews to PR authors, so that active developers get better prioritized reviews. + + 16:42 `` we are going to add and enable a number of github actions and workflows that should do the following: + + 16:43 `` - age PRs and add labelling to indicate to reviewers and authors that a review needs attention or it will be automatically closed (after around 4 weeks of languishing) + + 16:43 `` - label/notify steps to signed the contributor license agreement if unsigned + + 16:44 `` - run addtional integration tests on active PRs in CI + + 16:45 `` not sure if I am I missing anything else there. + + 16:45 `` but ideally we'd like to find a process that helps upstream unblock PRs and get review comments faster + + 16:45 `` so, it'll be an iterative process + + 16:46 `` and thanks for the reviews and suggestions so far on [https://github.com/canonical/cloud-init/pull/160](https://github.com/canonical/cloud-init/pull/160) as it is the first cut at trying to document the process + + 16:47 `` Nice! + + 16:48 `` woot. the hope I believe is to land that this week as well as branches like [https://github.com/canonical/cloud-init/pull/164](https://github.com/canonical/cloud-init/pull/164) [https://github.com/canonical/cloud-init/pull/236](https://github.com/canonical/cloud-init/pull/236) and [https://github.com/canonical/cloud-init/pull/125](https://github.com/canonical/cloud-init/pull/125) + + 16:49 `` additionally a gap that we still have vs when we hosted in Launchpad, is our auto-merge Launchpad bug commenting/maintenance: + + 16:49 `` We still have a need for the following: + + 16:49 `` - comment on LP bugs linking to an open github PR + + 16:49 `` - comment on merged commitish in github and Fix Commited state when a PR lands in upstream + + 16:50 `` so we'll be tackling that too in order to make upstream maintainers happier and better advertise fixes to bug filers + + 16:50 `` right now that's all a manual process since we haven't retooled our bug-related tooling + + 16:51 `` \#topic Community Charter and upcoming meeting + + 16:52 `` let's set the status meeting for next session + + 16:52 `` oops and I realize only now that I blew it this week due to daylight savings... meeting wasn't 'supposed' to start until 25 mins from now : / + + 16:53 `` \#topic cloud-init pull-requests [https://git.io/JeVed](https://git.io/JeVed) | Meeting minutes: [https://goo.gl/mrHdaj](https://goo.gl/mrHdaj) | Next status meeting March 1 16:15 UTC | 19.4 (Dec 17) drops Py2.7 : origin/stable-19.4 | 20.1 (Feb 18) | [https://bugs.launchpad.net/cloud-init/+filebug](https://bugs.launchpad.net/cloud-init/+filebug) + + 16:53 `` that's better. + + 16:53 `` it says March 1, is that correct? + + 16:54 `` there :) + + 16:54 `` hah, good I got another participant + + 16:54 `` :) + + 16:54 `` UK will also have their own daylight savings March 29th I believe + + 16:54 `` sorry AnhVoMSFT tribaal :) + + 16:54 `` yeah this time of year always messes with timing. We try to set things in terms of UTC to avoid thrashing + + 16:55 `` but even that fails due to human error (my bad) + + 16:56 `` Other community charter tasks are generally categorized in bugs labelled bitesize + + 16:56 `` \#link [https://bugs.launchpad.net/cloud-init/+bugs](https://bugs.launchpad.net/cloud-init/+bugs)?field.tag=bitesize + + 16:57 `` general topics for this year were tasks that are easily done in parallel, such as json schema addtions and datasource readthe docs updates/corrections and fleshing out. + + 16:57 `` jsonschema example is here for review if anyone wants to take a stab at testing it out. or extending schema for other config modules.[https://github.com/canonical/cloud-init/pull/152](https://github.com/canonical/cloud-init/pull/152) + + 16:58 `` and again all cloud-init contributors are encouraged to review/comment any active cloud-init PRs @ [https://github.com/canonical/cloud-init/pulls](https://github.com/canonical/cloud-init/pulls) the more voices, the better the quality + + 16:58 `` \#topic Office Hours (next 30 mins) + + 16:59 `` During this topic, please bring up any questions, discussions, bugs or features or paper cuts that need attention. there should be a couple of cloud-init developers with eyes on the channel to actively respond. + + 17:00 `` just before the start of this meeting Odd_Bloke was asking about getting the pytest branch landed for cloud-init. (moving off of nosetests as the project is EOL/unmaintained) + + 17:00 `` that's nice. pytest is becoming the de-facto standard these days anyway + + 17:05 `` yeah, didn't want to get stuck using something that becomes unsupported or unsupportable. we don't have the bandwidth in this project to maintain stacks that aren't being looked at by the collective internet ;) + + 17:05 `` blackboxsw: I believe that branch is now only blocked on you removing your "Request changes" review now that we've established that we don't need to hold off on landing things for Feature Freeze. + + 17:05 `` makes total sense :) + + 17:05 `` Odd_Bloke: do you know if rharper did the new-upstream-snapshot into focal already + + 17:05 `` to have a 'clean slate' for the pytest branch landing + + 17:06 `` blackboxsw: We can new-upstream-snapshot from an older commit, I don't believe that's a blocker. + + 17:06 `` Odd_Bloke: not a blocker, but I could do that now as it's 5 mins + + 17:07 `` then we can land right aftr + + 17:07 `` sound good? I see nothing queued [https://launchpad.net/ubuntu/focal/+queue](https://launchpad.net/ubuntu/focal/+queue)?queue_state=3&queue_text=cloud-init + + 17:08 `` Sure, if you're happier doing that. :) + + 17:09 `` I aam :) + + 17:09 `` ok doing that right now + + 17:09 `` then we can start the cherry picking just after + + 17:10 `` Odd_Bloke: I'm adding this as the debian/changelog section title + + 17:10 `` * New upstream snapshot: bug-fix-only feature-freeze-exception + + 17:11 `` instead of * New upstream snapshot: + + 17:11 `` sound reasonable? + + 17:11 `` It isn't bug-fix-only because we have the FFe for a non-bugfix. + + 17:12 `` I was just reading the wiki page that suggested wording, I think, let me take a look. + + 17:13 `` [https://github.com/canonical/cloud-init/pull/241](https://github.com/canonical/cloud-init/pull/241) + + 17:13 `` ahh right, reviewing that now + + 17:13 `` yeah not quite sure how to handle our FFe uploads + + 17:14 `` Oh, if it's only that change, then I don't think we need anything specific in the changelog. We have an FFE bug that we're closing with that upload. + + 17:14 * blackboxsw re-reads [https://wiki.ubuntu.com/FreezeExceptionProcess](https://wiki.ubuntu.com/FreezeExceptionProcess) + + 17:14 `` And that means it's _definitely_ not bug-fix-only, there isn't a single bugfix in there. ;) + + 17:14 `` ok that sounds good, will just keep the New upstream snapshot + + 17:14 `` ok thanks for the review. redoing. + + 17:14 `` Hopefully I'm right and you don't get yelled at. :p + + 17:15 `` better to upload and ask for forgiveness... + + 17:15 `` ehh, unlikely :) it seems like steve and others have been pretty lax about changelog text (or manipulating it after the fact) :) + + 17:15 `` Cool, I'll do the same thing locally to review. + + 17:16 `` Odd_Bloke: force pushed + + 17:16 `` [https://github.com/canonical/cloud-init/pull/241/files](https://github.com/canonical/cloud-init/pull/241/files) + + 17:16 `` blackboxsw: Approved. + + 17:17 `` thanks Odd_Bloke + + 17:17 `` build-and-pushing it up + + 17:18 `` ok onto your pytest branch now + + 17:18 `` while I await the ubuntu "accepted" response email + + 17:20 `` Uploading cloud-init_20.1-10-g71af48df-0ubuntu1.dsc: done. + + 17:21 `` just waiting on review/acceptance + + 17:22 `` community-notice: tip of cloud-init published into Ubuntu Focal (20.04) [ubuntu/focal-proposed] cloud-init 20.1-10-g71af48df-0ubuntu1 (Accepted) + + 17:26 `` ok Odd_Bloke merged at long last [https://github.com/canonical/cloud-init/pull/211](https://github.com/canonical/cloud-init/pull/211) + + 17:26 `` nosetest is dead, long live pytest + + 17:26 `` \o/ + + 17:27 `` blackboxsw: [https://github.com/canonical/cloud-init/pull/239](https://github.com/canonical/cloud-init/pull/239) `<-- another small one for you + + 17:29 `` approve Odd_Bloke and thanks. it is waiting on you for merge (and CI completion) + + 17:30 `` works on my focal box + + 17:30 `` which was broken before + + 17:33 `` Odd_Bloke: [https://github.com/canonical/cloud-init/pull/164](https://github.com/canonical/cloud-init/pull/164) is ready for you I think (labeling in cron) + + 17:33 `` for CLA ! CLA. + + 17:33 `` or do we want that PR to actually ignore certain paths (like doc changes) as not-requiring CLA + + 17:43 `` blackboxsw, could you take a look at [https://github.com/canonical/cloud-init/pull/62](https://github.com/canonical/cloud-init/pull/62) Pleaaaase :-) + + 17:44 `` Goneri: yes, and so sorry about that. + + 17:44 `` np, and Yeah! for pytest :-D + + 17:44 `` ... and that about wraps up on our cloud-init status meeting. :) I'll close it out and post the minutes for next time + + 17:45 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2020-03-31.md b/content/status-2020-03-31.md new file mode 100644 index 0000000..b163493 --- /dev/null +++ b/content/status-2020-03-31.md @@ -0,0 +1,165 @@ +Title: Cloud-init bi-weekly status +Date: 2020-03-31 16:19:00 UTC +Category: status-meeting-minutes +Slug: status-2020-03-31 + +Meeting information +---------------- + * \#cloud-init: cloud-init status meeting, 31 Mar at 16:19 — 17:17 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-03-31-16.19.log.html](http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-03-31-16.19.log.html)]] + + + +Meeting summary +---------------- + + **LINK**: [https://cloud-init.github.io/status-2020-03-10.html\#status-2020-03-10](https://cloud-init.github.io/status-2020-03-10.html\#status-2020-03-10) +### Previous Actions +The discussion about "Previous Actions" started at 16:22. + + +### Recent Changes +The discussion about "Recent Changes" started at 16:23. + + * **LINK**: [https://paste.ubuntu.com/p/55hqVCfnpV/](https://paste.ubuntu.com/p/55hqVCfnpV/) + +### In-progress Development +The discussion about "In-progress Development" started at 16:32. + + +### Community Charter +The discussion about "Community Charter" started at 16:42. + + * **LINK**: [https://bugs.launchpad.net/cloud-init/+bugs](https://bugs.launchpad.net/cloud-init/+bugs)?field.tag=bitesize + +### Office hours (next ~30 mins) +The discussion about "Office hours (next ~30 mins)" started at 16:45. + + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (38) + * meetingology (4) + * rharper (2) + * Goneri (1) + * shibumi (1) + * smoser (0) + * Odd_Bloke (0) + + + +Full Log +---------------- + + + 16:19 `` \#startmeeting cloud-init status meeting + + 16:19 `` Meeting started Tue Mar 31 16:19:14 2020 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:19 `` + + 16:19 `` Available commands: action commands idea info link nick + + 16:19 `` Hello and welcome to another cloud-init community status meeting folks. please feel free to continue any current conversations + + 16:20 `` I'll interleave status meeting notes with existing conversations. + + 16:20 `` \#chair Odd_Bloke smoser rharper + + 16:20 `` Current chairs: Odd_Bloke blackboxsw rharper smoser + + 16:20 `` our IRC channel topic carries the next planned status meeting for those that wish to participate. All are welcome to interject or drive converstation topics here + + 16:21 `` let's set that now. to +2 weeks from now + + 16:21 `` April 14th, same time + + 16:21 `` rharper: thanks! + + 16:22 `` Previous meeting notes are here + + 16:22 `` \#link [https://cloud-init.github.io/status-2020-03-10.html\#status-2020-03-10](https://cloud-init.github.io/status-2020-03-10.html\#status-2020-03-10) + + 16:22 `` The topics we generally cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Upcoming Meetings, Office Hours (~30 mins). + + 16:22 `` \#topic Previous Actions + + 16:23 `` and from last meeting, no previous actions were unaccounted for. + + 16:23 `` \#topic Recent Changes + + 16:24 `` recent changes landed in tip of master via git log --since 2020-03-10 + + 16:24 `` \#link [https://paste.ubuntu.com/p/55hqVCfnpV/](https://paste.ubuntu.com/p/55hqVCfnpV/) + + 16:24 `` shibumi: also, the issue with openstack metadata service not being found is likely related to classless statci route support in the EphemeralDHCP class in cloud-init, we fixed an issue there last fall, [https://github.com/canonical/cloud-init/commit/07b17236be5665bb552c7460102bcd07bf8f2be8](https://github.com/canonical/cloud-init/commit/07b17236be5665bb552c7460102bcd07bf8f2be8) + + 16:24 `` shibumi: long term, we would like to replace dhclient with a python-based one; we've just not had a change to implement a minimal dhclient in python only + + 16:27 `` in that paste or recent changes, some big items have landed since last we 'met': both NetBSD and OpenBSD distro support is now added to cloud-init. vmware support of guest info gc status, SAP Converged cloud gets identified as OpenStack and Ubuntu Focal prioritizing netplan over ifupdown if both are present + + 16:28 `` Also Odd_Bloke has been landing and improving cloud-init automated process with near daily branches. github actions/workflows and docs about review and coding style expectations are landing to make it a lot easier for upstream to help speed contributions and reviews + + 16:29 `` Also, you'll note a lot of dropping python six and other py2-related artifacts from our codebase. Since upstream support is py3.4 or later we can simplify and prune a lot of the vestigial py2 functionality. + + 16:31 `` Ahh I also forgot, Ec2 now by default (Ubuntu Focal or tip of cloud-init) renders full networking, including secondary IPv4/IPv6 addresses, for all interfaces attached to a VM based on network config supplied by IMDS. Old releases of cloud-init used to only render basic networking on the primary (eth0) nic. + + 16:32 `` \#topic In-progress Development + + 16:33 `` thanks Goneri and meena for all your the BSD ongoing development and support work there BTW + + 16:33 * Goneri waves + + 16:38 `` :) upstream is focused a bit on continuing to clean up py2 remnants from tip, adding support for reading netplan configuration from initramfs and continuing to add automation to the github development and release process/tooling to speed reviews. + + 16:39 `` we are also hammering the review queue a bit better than in the past with daily PR assignments to ensure the system remains more efficient + + 16:40 `` thanks again for all the code submits folks! + + 16:41 `` waiting In the wings we will eventually get around to handling the network hotplug solution for cloud-init (if configured) + + 16:42 `` \#topic Community Charter + + 16:43 `` This section is generally reserved to discuss any general community goals for cloud-init. Per last cloud-init summit we discussed prioritizing the following: + + 16:43 `` * json schema validation for each cloudinit/config/cc_*py module + + 16:43 `` * correcting, extending stale datasource documentation under doc/rtd/topics/datasources + + 16:44 `` those tasks are easy to split up and so we set a goal to try to chunk through it this year + + 16:44 `` they are also categorized as bugs for easy pickup/assignment for anyone interested. + + 16:45 `` \#link [https://bugs.launchpad.net/cloud-init/+bugs](https://bugs.launchpad.net/cloud-init/+bugs)?field.tag=bitesize + + 16:45 `` \#topic Office hours (next ~30 mins) + + 16:46 `` thanks for listening to the above...... In this section a couple upstream devs should be available with eyes on the channel for the next 30 minutes for and bug, feature, PR review questions or concerns. + + 16:46 `` again thanks for joining. We'll have this meeting again in 2 weeks + + 16:47 `` I'm going to spend this time working on our cherry-pick script for publishing the Netplan ->` ENI work into Ubuntu Focal today. + + 17:17 `` Thanks for tuning in. + + 17:17 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2020-04-14.md b/content/status-2020-04-14.md new file mode 100644 index 0000000..3ff0a59 --- /dev/null +++ b/content/status-2020-04-14.md @@ -0,0 +1,169 @@ +Title: Cloud-init bi-weekly status +Date: 2020-04-14 16:17:00 UTC +Category: status-meeting-minutes +Slug: status-2020-04-14 + +Meeting information +---------------- + * \#cloud-init: cloud-init status meeting, 14 Apr at 16:17 — 17:12 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-04-14-16.17.log.html](http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-04-14-16.17.log.html)]] + + + +Meeting summary +---------------- + + **LINK**: [https://cloud-init.github.io/status-2020-03-31.html\#status-2020-03-31](https://cloud-init.github.io/status-2020-03-31.html\#status-2020-03-31) +### Recent Changes +The discussion about "Recent Changes" started at 16:23. + + +### In-progress Development +The discussion about "In-progress Development" started at 16:27. + + +### Office hours (next ~30 mins) +The discussion about "Office hours (next ~30 mins)" started at 16:34. + + * **LINK**: [https://github.com/CanonicalLtd/uss-tableflip/pull/45](https://github.com/CanonicalLtd/uss-tableflip/pull/45) I think comments are resolved + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (38) + * meetingology (6) + * powersj (2) + * Goneri (2) + * otubo (1) + * punkgeek (1) + * rharper (1) + * smoser (0) + * powers (0) + * Odd_Bloke (0) + + + +Full Log +---------------- + + + 16:17 `` \#startmeeting cloud-init status meeting + + 16:17 `` Meeting started Tue Apr 14 16:17:46 2020 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:17 `` + + 16:17 `` Available commands: action commands idea info link nick + + 16:18 `` hey folks, time for cloud-init community status meeting + + 16:19 `` \o/ + + 16:19 `` Right on time :-) + + 16:20 `` welcome again to our bi-weekly status meeting feel free to interject comments, questions, suggestions during this status meeting. Generally it is an opportunity for upstream to provide a frequent platform communication and drop-in discussion when a couple of upstream devs are available. + + 16:20 `` \#chair Odd_Bloke smoser rharper powers + + 16:20 `` Warning: Nick not in channel: powers + + 16:20 `` Current chairs: Odd_Bloke blackboxsw powers rharper smoser + + 16:20 `` \#chair powersj + + 16:20 `` Current chairs: Odd_Bloke blackboxsw powers powersj rharper smoser + + 16:20 `` our IRC channel topic carries the next planned status meeting for those that wish to participate. All are welcome to interject or drive converstation topics here + + 16:21 `` any objections to same time on Apr 28th? + + 16:21 `` nah that's a good day given we want to cut 20.2 then + + 16:21 `` ok topic set for next meetin + + 16:22 `` our last meeting minutes can be found on github at + + 16:22 `` \#link [https://cloud-init.github.io/status-2020-03-31.html\#status-2020-03-31](https://cloud-init.github.io/status-2020-03-31.html\#status-2020-03-31) + + 16:23 `` The topics we generally cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Upcoming Meetings, Office Hours (~30 mins). + + 16:23 `` \#topic Previous Actions + + 16:23 `` none listed from last meeting + + 16:23 `` \#topic Recent Changes + + 16:24 `` git commits landed in tip since Mar 31: [https://paste.ubuntu.com/p/VptqRBfVfJ/](https://paste.ubuntu.com/p/VptqRBfVfJ/) found by git log --since 03-31-2020 + + 16:26 `` changes sport doc updates, otubo's cc_mount fix , better url handling for regions which contain underscores in their name and openbsd fixes from Goneri for passwd locks. + + 16:27 `` thanks for the contributions this round folks! + + 16:27 `` \#topic In-progress Development + + 16:30 `` upstream is currently focused on getting in bug fixes, dropping remnants of py2 in tooling reviewing active PRs to get cloud-init in shape for the upcoming 20.2 release + + 16:31 `` community notice: as mentioned in the channel topic, Apr 28th is our upstream release date for 20.2 + + 16:31 `` community notice: we ask that pull requests or bugs that need resolution for 20.2 be up for review by Friday April 24th so there is time to review and merge those fixes. + + 16:32 `` active pulls indended for the release should be up in github at [https://github.com/canonical/cloud-init/pulls](https://github.com/canonical/cloud-init/pulls) + + 16:32 `` *intended* rather + + 16:32 `` \#topic Community Charter + + 16:33 `` his section is generally reserved to discuss any general community goals for cloud-init, at last cloud-init summit we defined those goals as: + + 16:33 `` - datasource doc fixes + + 16:33 `` - json schema validation for each cloudinit/config/cc_*py modules + + 16:34 `` there are feature bugs created for these tasks at [https://bugs.launchpad.net/cloud-init/+bugs](https://bugs.launchpad.net/cloud-init/+bugs)?field.tag=bitesize + + 16:34 `` \#topic Office hours (next ~30 mins) + + 16:35 `` During office hours a couple of upstream devs will have eyes on this channel. Any questions, comments, branch reviews are fair game for discussion. + + 16:36 `` In leiu of active discussions, developers will be grooming the active pull request review queue to unblock branch authors. + + 16:37 `` Odd_Bloke: No it doesn't work. why there is no way to config cloud-init in kvm virtualization rather than iso, like vm xml file? + + 16:37 `` I'm getting through a belated review on [https://github.com/canonical/cloud-init/pull/298](https://github.com/canonical/cloud-init/pull/298) + + 16:42 `` punkgeek: like seeding ovf-env.xml? [https://github.com/canonical/cloud-init/blob/master/doc/sources/ovf/README](https://github.com/canonical/cloud-init/blob/master/doc/sources/ovf/README) + + 16:46 `` punkgeek: you might want to look at virt-install , they recently have added support for providing cloud-config to VMs; virt-install is a wrapper around creating VMs utilizing libvirt as a backend, [https://athinapl.home.blog/2019/08/25/gsoc-2019-cloud-init-configuration-for-virt-manager-virt-install/](https://athinapl.home.blog/2019/08/25/gsoc-2019-cloud-init-configuration-for-virt-manager-virt-install/) + + 16:54 `` punkgeek, or you can take a look at virt-lightning + + 16:54 `` punkgeek, it's basically a CLI to use libvirt+cloud-init + + 17:03 `` Goneri: review done. sorry for the delay on such a minor set of change requests [https://github.com/canonical/cloud-init/pull/298/files\#](https://github.com/canonical/cloud-init/pull/298/files\#) + + 17:09 `` [https://github.com/CanonicalLtd/uss-tableflip/pull/45](https://github.com/CanonicalLtd/uss-tableflip/pull/45) I think comments are resolved + + 17:11 `` I think we are at about the turn of the hour for cloud-init status. I'm going to review [https://github.com/canonical/cloud-init/pull/305](https://github.com/canonical/cloud-init/pull/305) next + + 17:11 `` thanks all for tuning in. see you next time + + 17:12 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) diff --git a/content/status-2020-05-05.md b/content/status-2020-05-05.md new file mode 100644 index 0000000..b99e630 --- /dev/null +++ b/content/status-2020-05-05.md @@ -0,0 +1,156 @@ +Title: Cloud-init bi-weekly status +Date: 2020-05-05 16:16:00 UTC +Category: status-meeting-minutes +Slug: status-2020-05-05 + +Meeting information +---------------- + * \#cloud-init: cloud-init status meeting, 05 May at 16:16 — 17:34 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-05-05-16.16.log.html](http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-05-05-16.16.log.html)]] + + + +Meeting summary +---------------- + + **LINK**: [https://cloud-init.github.io/](https://cloud-init.github.io/) +### Previous Actions +The discussion about "Previous Actions" started at 16:20. + + +### Recent Changes +The discussion about "Recent Changes" started at 16:20. + + * **LINK**: [https://paste.ubuntu.com/p/YMb2Tw3tRD/](https://paste.ubuntu.com/p/YMb2Tw3tRD/) + +### In-progress Development +The discussion about "In-progress Development" started at 16:26. + + * **LINK**: [https://github.com/canonical/cloud-init/pulls](https://github.com/canonical/cloud-init/pulls) + +### Community Charter +The discussion about "Community Charter" started at 16:30. + + * **LINK**: [https://bugs.launchpad.net/cloud-init/+bugs](https://bugs.launchpad.net/cloud-init/+bugs)?field.tag=bitesize + +### Office hours (next ~30 mins) +The discussion about "Office hours (next ~30 mins)" started at 16:33. + + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (38) + * meetingology (4) + * rharper (0) + * Odd_Bloke (0) + * smoser (0) + + + +Full Log +---------------- + + + 16:16 `` \#startmeeting cloud-init status meeting + + 16:16 `` Meeting started Tue May 5 16:16:41 2020 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:16 `` + + 16:16 `` Available commands: action commands idea info link nick + + 16:17 `` good morning, afternoon and evening folks. Welcome to another cloud-init status meeting. + + 16:17 `` \#chair Odd_Bloke smoser rharper + + 16:17 `` Current chairs: Odd_Bloke blackboxsw rharper smoser + + 16:17 `` our IRC channel topic carries the next planned status meeting for those that wish to participate. All are welcome to interject or drive converstation topics here + + 16:18 `` I'll set the next status meeting topic while we are thinking about it. + + 16:18 `` 2 weeks from today, same time 16:15 UTC. + + 16:18 `` May 19th it is. + + 16:19 `` Previous meeting minutes live over on github + + 16:19 `` \#link [https://cloud-init.github.io/](https://cloud-init.github.io/) + + 16:19 `` The topics we generally cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Upcoming Meetings, Office Hours (~30 mins). + + 16:20 `` \#topic Previous Actions + + 16:20 `` Looks like no unresolved actions from last meeting + + 16:20 `` \#topic Recent Changes + + 16:22 `` Below is a list of commits that have landed in tip of master: found via git log --since 2020-03-10 + + 16:22 `` \#link [https://paste.ubuntu.com/p/YMb2Tw3tRD/](https://paste.ubuntu.com/p/YMb2Tw3tRD/) + + 16:23 `` We've had a number of milestones since the last status meeting, Ubuntu Focal Fossa 20.04 was released on Apr 23, cloud-init upstream cut a release 20.2 as well + + 16:23 `` Additionally we have two new hires to the canonical ubuntu-server team that will be participating in cloud-init, curtin and ubuntu-advantage-tools projects + + 16:24 `` We are really excited to have some extra hands on cloud-init from lucasmoura and falcojr. So welcome gentlemen, glad to have the help. + + 16:25 `` They just started yesterday and are going through a bit of onboarding this week, but expect to see them around in cloud-init shortly. I believe they have both landed their first PRs to get added as a contributor to cloud-init. + + 16:26 `` \#topic In-progress Development + + 16:26 `` \#link [https://github.com/canonical/cloud-init/pulls](https://github.com/canonical/cloud-init/pulls) + + 16:27 `` ok active review queue is really getting well maintained now that we've adopted PR assignment. Thanks for helping is land branches quickly folks. + + 16:28 `` Generally upstream has set a couple of long-term goals for cloud-init in the next development cycle + + 16:28 `` - wrap up cloud-init daemon mode (to reduce boot time by loading python only once) + + 16:28 `` - OpenStack network hotplug handling from cloud-init + + 16:29 `` - Potentially a new LXD datasource for handling container deployments + + 16:29 `` - better json schema coverage for the remaining oncovered cloud config modules. + + 16:30 `` \#topic Community Charter + + 16:31 `` We continue to categorize more bitesize bugs in cloud-init. + + 16:31 `` \#link [https://bugs.launchpad.net/cloud-init/+bugs](https://bugs.launchpad.net/cloud-init/+bugs)?field.tag=bitesize + + 16:32 `` These bugs are themed at doc updates and json schema improvements across all of cloud-init, but we continue to seed that bug tag with items which should be easy to drop in and make a lasting impact on cloud-init + + 16:33 `` All cloud-init contributors are encouraged to participate in any part of the cloud-init lifecycle, from bug filing, to fixing, to release testing and PR reviews. Thanks to everyone who continues to build the cloud-init community! + + 16:33 `` \#topic Office hours (next ~30 mins) + + 16:35 `` During this stage we have a some focus time on cloud-init development and community support. Any questions, concerns, reviews or request for help/triage are most welcome. We should have a couple of upstream developers with eyes on this channel. + + 16:36 `` In the absence of discussion, we'll groom the active PR review queue and/or work additional cloud-init dev items. + + 16:38 `` community-notice: Ubuntu plans to release cloud-init version 20.2 to Ubuntu's new development release 20.10 (Groovy Gorilla). We expect to start an Ubuntu StableReleaseUpdate into xenial, bionic, eoan and focal within the next 2 weeks. + + 17:33 `` alrighty, think that about wraps today's status meeting. Happy Cinco De Mayo folks + + 17:34 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2020-05-19.md b/content/status-2020-05-19.md new file mode 100644 index 0000000..9867ab3 --- /dev/null +++ b/content/status-2020-05-19.md @@ -0,0 +1,219 @@ +Title: Cloud-init bi-weekly status +Date: 2020-05-19 16:18:00 UTC +Category: status-meeting-minutes +Slug: status-2020-05-19 + +Meeting information +---------------- + * \#cloud-init: cloud-init status meeting, 19 May at 16:18 — 18:24 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-05-19-16.18.log.html](http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-05-19-16.18.log.html)]] + + + +Meeting summary +---------------- + + **LINK**: [https://cloud-init.github.io/status-2020-05-05.html\#status-2020-05-05](https://cloud-init.github.io/status-2020-05-05.html\#status-2020-05-05) +### \#cloud-init pull-requests [https://git.io/JeVed](https://git.io/JeVed) | Meeting minutes: [https://goo.gl/mrHdaj](https://goo.gl/mrHdaj) | Next status meeting June 16:15 UTC | 20.1 (Feb 18) | 20.2 (Apr 28) | [https://bugs.launchpad.net/cloud-init/+filebug](https://bugs.launchpad.net/cloud-init/+filebug) +The discussion about "\#cloud-init pull-requests [https://git.io/JeVed](https://git.io/JeVed) | Meeting minutes: [https://goo.gl/mrHdaj](https://goo.gl/mrHdaj) | Next status meeting June 16:15 UTC | 20.1 (Feb 18) | 20.2 (Apr 28) | [https://bugs.launchpad.net/cloud-init/+filebug](https://bugs.launchpad.net/cloud-init/+filebug)" started at 16:20. + + +### \#cloud-init pull-requests [https://git.io/JeVed](https://git.io/JeVed) | Meeting minutes: [https://goo.gl/mrHdaj](https://goo.gl/mrHdaj) | Next status meeting June 2 16:15 UTC | 20.1 (Feb 18) | 20.2 (Apr 28) | [https://bugs.launchpad.net/cloud-init/+filebug](https://bugs.launchpad.net/cloud-init/+filebug) +The discussion about "\#cloud-init pull-requests [https://git.io/JeVed](https://git.io/JeVed) | Meeting minutes: [https://goo.gl/mrHdaj](https://goo.gl/mrHdaj) | Next status meeting June 2 16:15 UTC | 20.1 (Feb 18) | 20.2 (Apr 28) | [https://bugs.launchpad.net/cloud-init/+filebug](https://bugs.launchpad.net/cloud-init/+filebug)" started at 16:20. + + +### Previous Actions +The discussion about "Previous Actions" started at 16:21. + + +### Recent Changes +The discussion about "Recent Changes" started at 16:22. + + +### In-progress Development +The discussion about "In-progress Development" started at 16:27. + + +### Community Charter +The discussion about "Community Charter" started at 16:39. + + * **LINK**: [https://bugs.launchpad.net/cloud-init/](https://bugs.launchpad.net/cloud-init/)?field.tag=bitezise + +### Office Hours (next ~30 mins) +The discussion about "Office Hours (next ~30 mins)" started at 16:44. + + * **LINK**: [https://pastebin.com/TG4E8Dft](https://pastebin.com/TG4E8Dft) 19.4-33 (latest 18.04 image on Azure) + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (52) + * AnhVoMSFT (8) + * meetingology (4) + * meena (3) + * Odd_Bloke (2) + * smoser (0) + * rharper (0) + + + +Full Log +---------------- + + + 16:18 `` \#startmeeting cloud-init status meeting + + 16:18 `` Meeting started Tue May 19 16:18:05 2020 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:18 `` + + 16:18 `` Available commands: action commands idea info link nick + + 16:18 `` \#chair Odd_Bloke smoser rharper + + 16:18 `` Current chairs: Odd_Bloke blackboxsw rharper smoser + + 16:18 `` hello cloud-init, welcome to another round cloud-init status updates + + 16:19 `` our IRC channel topic carries the next planned status meeting for those that wish to participate. All are welcome to interject or drive converstation topics here + + 16:19 `` Previous meeting notes are here + + 16:19 `` \#link [https://cloud-init.github.io/status-2020-05-05.html\#status-2020-05-05](https://cloud-init.github.io/status-2020-05-05.html\#status-2020-05-05) + + 16:19 `` and next status meeting should be in 2 weeks time. + + 16:20 `` looks like June 2. I'll set the topic of this irc channel to so that dropins can see a reminder for when that meeting is held + + 16:20 `` \#topic \#cloud-init pull-requests [https://git.io/JeVed](https://git.io/JeVed) | Meeting minutes: [https://goo.gl/mrHdaj](https://goo.gl/mrHdaj) | Next status meeting June 16:15 UTC | 20.1 (Feb 18) | 20.2 (Apr 28) | [https://bugs.launchpad.net/cloud-init/+filebug](https://bugs.launchpad.net/cloud-init/+filebug) + + 16:20 `` \#topic \#cloud-init pull-requests [https://git.io/JeVed](https://git.io/JeVed) | Meeting minutes: [https://goo.gl/mrHdaj](https://goo.gl/mrHdaj) | Next status meeting June 2 16:15 UTC | 20.1 (Feb 18) | 20.2 (Apr 28) | [https://bugs.launchpad.net/cloud-init/+filebug](https://bugs.launchpad.net/cloud-init/+filebug) + + 16:20 `` let's try that instead + + 16:21 `` The topics we generally cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter and Office Hours (~30 mins). + + 16:21 `` I'll jump through each topic, as always interjections, questions or other topics welcome + + 16:21 `` \#topic Previous Actions + + 16:22 `` Nothing brought up as an action in the last meeting so we'll jump to the next topic + + 16:22 `` \#topic Recent Changes + + 16:24 `` The following changes have landed in master; found via git log --since 05-05-2020 [https://paste.ubuntu.com/p/d2qR8pTZNY/](https://paste.ubuntu.com/p/d2qR8pTZNY/) + + 16:26 `` there are a number of commits landed related to dropping additional py2 support from various paths as well as improving pytest fixtures (thx OddBloke) and some json schema definitions added to cc_snap and cc_apt_configure thanks lucasmoura + + 16:27 `` and an additional bit of work from meena to make libc discovery platform independent + + 16:27 `` \#topic In-progress Development + + 16:30 `` Current themes of work for upstream include: continuing to refine a spec on cloud-init daemon mode and hot-plug support, purging python2-isms, improving pytest automation. + + 16:33 `` falcojr: also has a new approach for feature flag definitions/behavior in cloud-init in [https://github.com/canonical/cloud-init/pull/367](https://github.com/canonical/cloud-init/pull/367) This should give us the ability to better codify upstream unconfiguraable cloud-init behavior which may differ on previous releases. + + 16:34 `` falcojr: Odd_Bloke & smoser thanks for good design discussion there. anyone interested feel free to weigh in. + + 16:36 `` Also in-progress work is a cloud-init StableReleaseUpdate planned to publish cloud-init version 20.2 to xenial, bionic, eoan and focal. + + 16:37 `` This will publish latest cloud-init (after verification) to old stable releases + + 16:38 `` the first step before SRU is to upload latest cloud-init to Ubuntu Groovy(20.10). Once this upload is complete, we'll start the SRU process to publish to Xenial, Bionic, Eoan and Focal + + 16:39 `` \#topic Community Charter + + 16:40 `` As discussed at the last cloud-init summit we targeted a couple of streams of work that are easy to work in parallel, making them prime candidates for community involvement. + + 16:41 `` Those streams/themes are: updating and correcting datasource documentation at [https://cloudinit.readthedocs.io/en/latest/topics/datasources.html](https://cloudinit.readthedocs.io/en/latest/topics/datasources.html) + + 16:41 `` and adding jsonschema definitions to any cloudinit.config.cc_* modules + + 16:41 `` any of these bugs are categorized as 'bitesize' and can be searched at the following link + + 16:42 `` \#link [https://bugs.launchpad.net/cloud-init/](https://bugs.launchpad.net/cloud-init/)?field.tag=bitezise + + 16:43 `` a few of us have grabbed schema definitions for a few of the cloud config modules. I think we are up to 11 modules covered (of 50). Thanks all for the progress there. We have it on our roadmap to flesh out as much as we can + + 16:44 `` \#topic Office Hours (next ~30 mins) + + 16:45 `` During this part of the meeting upstream devs should have eyes on the channel for any discussion related to feature, bug or review requests. + + 16:45 `` In the absence of active discussions, the active review queue will be be groomed. + + 16:46 `` for me, I've got to read through [https://github.com/canonical/cloud-init/pull/367](https://github.com/canonical/cloud-init/pull/367) in depth to see if I have any use-cases to add there for feature management + + 17:21 `` so, yeah sorry for the noise Odd_Bloke and falcojr in standup about whether this 'feature' is runtime configurable on/off. It doesn't even make sense for this \#include case. Also I think the merits of falcojr's suggestion to rely on some unique environment variable to determine whether a feature is on or off can and should be encoded in cloud-init proper, instead of relying on patching when releasing to + + 17:21 `` ubuntu/xenial. + + 17:22 `` when we add a new 'feature' to cloud-init upstream. I believe we know what our expectations are for older stable releases at that time. We generally could encode those expectations (at least for ubuntu series which we maintain) that a feature should behave a certain way when we end up releasing to ubuntu/xenial. Avoiding the RELEASE_BLOCKER comment as a reminder for us to manually patch a release wouldn't be + + 17:22 `` necessary in these cases. + + 17:26 `` q question: when I specify a custom data to format/partition the datadisk, it seems like the ephemeral resource disk isn't getting formatted to ext4 anymore. Is this by-design that when the customer specifies disk_setup and fs_setup for additional datadisk they need to also include the fs_setup for ephemeral0 (it seems odd because disk_setup got "merged" properly. I could see the ephemeral0 + + 17:26 `` got partitioned. Yet fs_setup isn't). + + 17:27 `` I am not sure if this is an appropriate topic for Office Hours. I can wait :-) + + 17:30 `` AnhVoMSFT: thx for the question. so, what version of cloud-init and what's the user-data for partitioning that is isn't working as expected? + + 17:31 `` [https://pastebin.com/TG4E8Dft](https://pastebin.com/TG4E8Dft) 19.4-33 (latest 18.04 image on Azure) + + 17:33 `` (paste.ubuntu has been giving me problems today - not sure if it's only me) + + 17:49 `` blackboxsw: no mention of my work on the net refactoring or did i miss that + + 17:53 `` meena: sorry, right that is a large undertaking that you've raised via your PR [https://github.com/canonical/cloud-init/pull/363](https://github.com/canonical/cloud-init/pull/363) + + 17:55 `` yeah, it's my: please teach my software engineering while all i do is code monkeying PR. + + 17:55 `` don't tell no one tho, or else they… might not. + + 17:58 `` blackboxsw: Could you comment on the PR where we're having that feature flag conversation, please? + + 17:58 `` Heh, generally the direction meena is going is toward distro-specific networking subclass to handle network rendering details (as most of our network rendering utility functions are highly distro-dependent + + 17:59 `` Odd_Bloke: yes, I shall. + + 17:59 `` Thanks! + + 18:06 `` Ok, I forgot to close out the meeting. + + 18:07 `` AnhVoMSFT: so I see your instance is properly "waiting" for the presence of ephemeral0 resource disk. trying to get to the bottom of why formatting isn't being addressed there. + + 18:10 `` I see 2020-05-19 17:20:24,072 - cc_mounts.py[DEBUG]: Mapped metadata name ephemeral0 to /dev/disk/cloud/azure_resource + + 18:10 `` 2020-05-19 17:20:24,073 - cc_mounts.py[DEBUG]: changed default device ephemeral0 =>` /dev/disk/cloud/azure_resource-part1 + + 18:16 `` @blackboxsw this is reproducing 100% of the time + + 18:17 `` I'm wondering AnhVoMSFT if the ephemeral0 alias needs to be used instead. something like [https://paste.ubuntu.com/p/7wmMc8drZ3/](https://paste.ubuntu.com/p/7wmMc8drZ3/) + + 18:19 `` I see we've done SRU testing referencing that alias instead of full resource disk path [https://github.com/cloud-init/ubuntu-sru/blob/master/bugs/b59870ca.txt](https://github.com/cloud-init/ubuntu-sru/blob/master/bugs/b59870ca.txt) + + 18:23 `` @blackboxsw, my config is actually having an EXTRA datadisk + + 18:23 `` so in this case the VM is deployed with an additional data disk attached to the VM + + 18:24 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2020-06-02.md b/content/status-2020-06-02.md new file mode 100644 index 0000000..b10a410 --- /dev/null +++ b/content/status-2020-06-02.md @@ -0,0 +1,277 @@ +Title: Cloud-init bi-weekly status +Date: 2020-06-02 16:21:00 UTC +Category: status-meeting-minutes +Slug: status-2020-06-02 + +Meeting information +---------------- + * \#cloud-init: cloud-init status meeting, 02 Jun at 16:21 — 18:08 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-06-02-16.21.log.html](http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-06-02-16.21.log.html)]] + + + +Meeting summary +---------------- + + **LINK**: [https://cloud-init.github.io/](https://cloud-init.github.io/) +### Previous Actions +The discussion about "Previous Actions" started at 16:24. + + +### Recent Changes +The discussion about "Recent Changes" started at 16:27. + + +### In-progress Development +The discussion about "In-progress Development" started at 16:34. + + * **LINK**: [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018) + +### Community Charter +The discussion about "Community Charter" started at 16:47. + + * **LINK**: [https://bugs.launchpad.net/cloud-init/](https://bugs.launchpad.net/cloud-init/)?field.tag=bitezise + +### Office Hours (next ~30 mins) +The discussion about "Office Hours (next ~30 mins)" started at 16:50. + + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (76) + * Odd_Bloke (6) + * knaccc (5) + * meena (5) + * meetingology (4) + * rharper (3) + * ddstreet (1) + * ubot5 (1) + * smoser (0) + + + +Full Log +---------------- + + + 16:21 `` \#startmeeting cloud-init status meeting + + 16:21 `` Meeting started Tue Jun 2 16:21:15 2020 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:21 `` + + 16:21 `` Available commands: action commands idea info link nick + + 16:21 `` hi folks, time for another cloud-init upstream status meeting. + + 16:22 `` we use this meeting to provide a venue for any cloud-init interested parties to keep up to date on current development, release-related info and expedite distributed development where possible. + + 16:22 `` this meeting is a welcome place for interruptions, questions, requests and unrelated discussions at any point. so don't be shy :) + + 16:23 `` \#chair Odd_Bloke smoser rharper + + 16:23 `` Current chairs: Odd_Bloke blackboxsw rharper smoser + + 16:23 `` The topics we generally cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Office Hours (~30 mins). + + 16:24 `` previous meeting minutes live here (and I just saw I forgot to publish last minutes so I pushed them now) + + 16:24 `` \#link [https://cloud-init.github.io/](https://cloud-init.github.io/) + + 16:24 `` \#topic Previous Actions + + 16:25 `` nothing actionable brought up in last meeting on 05/19 + + 16:26 `` Odd_Bloke: ahh we should fix devel with those pkg drops on next upload + + 16:26 `` we did drop that for Xenial, Bionic Eoan and maybe focal too? + + 16:26 `` so an oversight for groovy + + 16:27 `` next topic + + 16:27 `` \#topic Recent Changes + + 16:28 `` the following are commits landed in tip of master found via git log --since 05/19/2020 : [https://paste.ubuntu.com/p/QFvgWhjXY9/](https://paste.ubuntu.com/p/QFvgWhjXY9/) + + 16:28 `` blackboxsw: When you say "next upload" are you referring to the upload you're about to do, or the one after that? + + 16:28 `` Odd_Bloke: if you'd like we can adjust the current upload so that devel, focal, bionic xenial eoan all drop those stale deps + + 16:28 `` I think X, B E have all dropped them + + 16:29 `` so maybe I re-do ubuntu/devel PR Odd_Bloke ? + + 16:29 `` probably good/better/correct to keep all releases on the same footing. + + 16:29 `` blackboxsw: I think it's worth doing, we've uploaded without fixing it a few times before, and we've remembered this time around. + + 16:30 `` yeah sounds good Odd_Bloke I'll re-do that devel PR (and make sure focal drops it too) + + 16:30 `` if needed + + 16:30 `` And it should just be a case of pushing a new commit to your existing branch. + + 16:30 `` Thanks! + + 16:30 `` +1 + + 16:32 `` things of note in the recent commits landed. [https://github.com/canonical/cloud-init/pull/358](https://github.com/canonical/cloud-init/pull/358) Mattew Ruffell improved cc_grub_dpkg to be more dynamic in matching disks instead of a hardcoded device list + + 16:33 `` thanks Matthew + + 16:33 `` and chef_license support [https://github.com/canonical/cloud-init/commit/0919bd46bbd1b12158c369569ec1298bb000dd8a](https://github.com/canonical/cloud-init/commit/0919bd46bbd1b12158c369569ec1298bb000dd8a) + + 16:34 `` thanks bipinbachhao for the config extension there + + 16:34 `` \#topic In-progress Development + + 16:35 `` a couple of new notables in flight at the moment: + + 16:38 `` - falcojr: introduction of feature-flags for cloud-init upstream to give us a toggle to retain original behavior of \#include failures on stable downstream releases. [https://github.com/canonical/cloud-init/pull/367](https://github.com/canonical/cloud-init/pull/367) . Upstream cloud-init will fail loudly and raise an Exception if someone tries to \#include a url which fails. this differs from original cloud-init behavior which was to try our best to get a system up + + 16:38 `` and running, even amid not-critical failures + + 16:39 `` per the above, if downstreams (distributiions) would like to retain a more permissive warn on \#include user-data issues, a cloudinit/feature_overrides.py file would need to be introduced in the downstream + + 16:40 `` - Also meena and Odd_Bloke and others have been working toward a refactor of cloudinit.net modules. Dan added a doc PR to capture this approach [https://github.com/canonical/cloud-init/pull/391](https://github.com/canonical/cloud-init/pull/391) + + 16:41 `` beyond that, there are a number of PRs up from lucas on json schema additions for cloudinit/config/cc_* modules to get better validation of \#cloud-config user-data + + 16:42 `` For ubuntu proper, we have started the StableReleaseUpdate process for cloud-init to publish master into ubuntu/xenial, bionic, eoan and focal releases + + 16:43 `` some of these changes will add the opportunity to enable 'new' features on platforms like Azure + + 16:43 `` and AWS + + 16:43 `` Azure (xenial) will be dropping walinuxagent support + + 16:44 `` AWS will now surface a datasource config option apply_full_imds_network_config boolean + + 16:45 `` if set true in an Ec2(aws) image network configuration from cloud-init can come completely from IMDS for every connected NIC. That config will include all secondary IPv4/IPv6 addressses configured for the machine + + 16:46 `` Upstream has started the Ubuntu SRU process (which generally takes around 10-14 days). We plan to include every commit that has landed in tip of master as of commitish 5f7825e22241423322dbe628de1b00289cf34114 + + 16:46 `` the bug related to this SRU work is here + + 16:46 `` \#link [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018) + + 16:46 `` Ubuntu bug 1881018 in cloud-init (Ubuntu Focal) "sru cloud-init (19.4.33 to 20.2-30) Xenial, Bionic, Eoan and Focal" [Undecided,New] + + 16:47 `` \#topic Community Charter + + 16:48 `` upstream has signed up to get as much of the json schema coverage as we can for cloudinit/config/cc*py modules since invalid \#cloud-config user-data formats tends to have one of the highest incidence of errors (because writing YAML is something humans shouldn't have to do :) ) + + 16:49 `` so we are chopping away at defining JSON schema for as many cloud config modules as possible . there are still plenty to choose from. Anyone can feel free to grab a JSON schema bug and help us with bettering cloud-init + + 16:49 `` bugs are filed for each config module which needs schema definition: + + 16:49 `` \#link [https://bugs.launchpad.net/cloud-init/](https://bugs.launchpad.net/cloud-init/)?field.tag=bitezise + + 16:50 `` a big thanks to lucasmoura for starting to grab a number of these + + 16:50 `` \#topic Office Hours (next ~30 mins) + + 16:50 `` This 'section' of the meeting is a time where a couple of upstream devs will be available in channel for any discussions, questions, bug work or PR reviews. + + 16:51 `` In the absence of discussions/topics here we scrub the review queue. + + 16:51 `` since we are mid-stream on Ubuntu SRU at the moment, I'll be addressing review comments on some of the functional 'upload' branches we've put together + + 16:52 `` and, let's update the topic for next IRC meeting too while we are at it + + 16:59 `` Odd_Bloke: just pushed ubuntu/devel dropping python3-six|unittest2|nose + + 17:01 `` and just re-pushed ubuntu/focal to drop python3-six + + 17:04 `` oops and missed you others. reworking + + 17:12 `` ok re-pushed. focal and devel PRs in shape + + 17:13 `` dropped the following build-deps: python3-six, python3-unittest2, python3-pep8, python3-nose, python3-pyflakes + + 17:20 `` blackboxsw: +1 on the ubuntu/devel upload. + + 17:21 `` whew, think we got all of the dropped deps between the two of us... thanks! + + 17:21 `` Odd_Bloke: thanks focal looks good and sbuilds + + 17:21 `` just finished eoan and building now to test + + 17:23 `` what? me?? + + 17:24 `` well yes indeedy meena, just trying to keep you highlighted as participating in the cloud-init status meeting :) you've thankfully reviewed, pushed and prodded us to talk about cloudinit.net refactor and how best to address it I think :) credit due ;) + + 17:26 `` community notice: upload to Ubuntu groovy of cloud-init master accepted [ubuntu/groovy-proposed] cloud-init 20.2-45-g5f7825e2-0ubuntu1 (Accepted) + + 17:30 `` blackboxsw: One issue with [https://github.com/canonical/cloud-init/pull/412](https://github.com/canonical/cloud-init/pull/412) + + 17:31 `` blackboxsw: i'm just waiting for Odd_Bloke to provide the basic infrastructure so i can start moving code… without that, i have to bug other projects in my … 2 hours of free time per day. + + 17:31 `` blackboxsw: yesterday, i tried to build an android app on my laptop and gave up after an hour. + + 17:35 `` nice review again Odd_Bloke, will reflect that patch to each series. as every other ubuntu/* is missing enabling various cloud datasources beyond just Rbx + + 17:54 `` Odd_Bloke: rharper so Xenial is interesting for datasource config via dpkg + + 17:55 `` We are missing: Hetzner, IBMCloud, Oracle, and RbxCloud + + 17:55 `` one was an oversight on previous SRUs + + 17:55 `` but Oracle and IBMCloud, I'm trying to recall if there is a reason we didn't want to surface either of those datasources as configurable on Xenial + + 17:56 `` a little warning bell is going off in my head + + 17:56 `` Hetzner I thought was 'ok' + + 17:56 `` Oracle currently gets detected as OpenStack on Xenial. + + 17:57 `` IBMCloud and Oracle are sensitive + + 17:57 `` not sure about Hetzner or RbxCloud though + + 17:57 `` upstream Oracle datasource is 'good', but I wasn't sure if there was extra baggage associated with *not* backporting that functionality + + 17:57 `` blackboxsw: I think you might want to check with CPC on those + + 17:58 `` Hetzner is also detected as OpenStack on FreeBSD… but… only thru cloud-init itself, not thru ds-identify + + 18:03 `` (i'm not sure how much of that is my fault having helped a lot with Hetzner and FreeBSD and ds-identify myself) + + 18:03 `` Odd_Bloke thanks for your reply. I managed to fix things in the end, but kinda by cheating. Now my /etc/netplan/50-cloud-init.yaml only contains the IP addresses configuration, and I make the nameservers and search domain apply in the "Global" scope (as reported by systemd-resolve --status) by simply modifying the /etc/resolv.conf file. All configuration survives reboot just fine, and I am no longer + + 18:03 `` scared that resolv.conf will be overwritten because I found a web page that said that "Note: The mode of operation of systemd-resolved is detected automatically, depending on whether /etc/resolv.conf is a symlink to the local stub DNS resolver file or contains server names." Although you said in your message that "cloud-init will regenerate /etc/netplan/50-cloud-init.yaml on each boot, so yes, you don't + + 18:03 `` want to modify that", the OVH instructions directly contradict that and tell me to edit it to add all IP addresses to my interface (see Ubuntu 18.04 section here: [https://docs.ovh.com/gb/en/vps/network-ipaliasing-vps/](https://docs.ovh.com/gb/en/vps/network-ipaliasing-vps/)). I'm therefore very confused about why OVH seem to contradict the instructions that are in that config file, and confused as to what other location I should be editing/creating instead + + 18:06 `` knaccc why do you want to change resolved 'Global' section? + + 18:08 `` heh meena not at fault :) . Just need to make sure we move cloud-platforms to a better way of detecting the right datasource when we can. + + 18:08 `` ddstreet if I put the nameservers and search domain into the /etc/netplan/50-cloud-init.yaml file, it gets ignored completely (i.e. although those configurations show up in systemd-resolve --status against that specific "link", the "Global" nameservers and lack of any search domain in that Global section are taking precedence). Therefore I had to configure nameservers and search domain at the resolv.conf + + 18:08 `` level so that it appeared in the Global section, and then suddenly everything worked for the first time + + 18:08 `` I should tie off our cloud-init status meeting. Thanks folks for all who've attended + + 18:08 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2020-06-16.md b/content/status-2020-06-16.md new file mode 100644 index 0000000..7b2ef57 --- /dev/null +++ b/content/status-2020-06-16.md @@ -0,0 +1,235 @@ +Title: Cloud-init bi-weekly status +Date: 2020-06-16 16:21:00 UTC +Category: status-meeting-minutes +Slug: status-2020-06-16 + +Meeting information +---------------- + * \#cloud-init: cloud-init status meeting, 16 Jun at 16:21 — 17:58 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-06-16-16.21.log.html](http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-06-16-16.21.log.html)]] + + + +Meeting summary +---------------- + + **LINK**: [https://cloud-init.github.io/](https://cloud-init.github.io/) +### Recent Changes +The discussion about "Recent Changes" started at 16:24. + + +### In-progress Development +The discussion about "In-progress Development" started at 16:32. + + * **LINK**: [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018) + * **LINK**: + * **LINK**: [https://github.com/canonical/cloud-init/pull/391](https://github.com/canonical/cloud-init/pull/391) + * **LINK**: [https://github.com/canonical/cloud-init/pull/416\#issuecomment-640032968](https://github.com/canonical/cloud-init/pull/416\#issuecomment-640032968) + * **ACTION**: file feature bug about refactoring startup services + * **ACTION**: mailing list email requesting comment/concerns about a refactor of startup services + +### community charter +The discussion about "community charter" started at 16:54. + + * **LINK**: [https://bugs.launchpad.net/cloud-init/](https://bugs.launchpad.net/cloud-init/)?field.tag=bitezise + +### Office Hours (~next 30 minutes) +The discussion about "Office Hours (~next 30 minutes)" started at 16:59. + + * **LINK**: [https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_puppet.py\#L106](https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_puppet.py\#L106) could this be entirely puppet specific, and no other module does this dance? + * **LINK**: [https://github.com/canonical/cloud-init/blob/master/cloudinit/reporting/events.py\#L84](https://github.com/canonical/cloud-init/blob/master/cloudinit/reporting/events.py\#L84) + * **LINK**: [https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_rsyslog.py\#L210](https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_rsyslog.py\#L210) one more + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (61) + * meena (6) + * meetingology (6) + * AnhVoMSFT (2) + * ubot5 (1) + * cyberpear (1) + * Odd_Bloke (1) + * smoser (0) + * rharper (0) + + + +Full Log +---------------- + + + 16:21 `` \#startmeeting cloud-init status meeting + + 16:21 `` Meeting started Tue Jun 16 16:21:42 2020 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:21 `` + + 16:21 `` Available commands: action commands idea info link nick + + 16:22 `` \#chair smoser Odd_Bloke rharper + + 16:22 `` Current chairs: Odd_Bloke blackboxsw rharper smoser + + 16:22 `` Welcome to the bi-weekly cloud-init status meeting. A place to chat about upstream cloud-init activity/ + + 16:23 `` his meeting is a welcome place for interruptions, questions, requests and unrelated discussions at any point. + + 16:23 `` *this* + + 16:23 `` previous meeting minutes are stored on github + + 16:23 `` \#link [https://cloud-init.github.io/](https://cloud-init.github.io/) + + 16:24 `` The topics we generally cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Office Hours (~30 mins). + + 16:24 `` From the previous meeting we captured no actions, so I'll jump into the next topic + + 16:24 `` \#topic Recent Changes + + 16:25 `` the following are commits merged into cloud-init's upstream master branch: [https://paste.ubuntu.com/p/WdsZXbwwWd/](https://paste.ubuntu.com/p/WdsZXbwwWd/) + + 16:26 `` found via git log --since 06-02-2020 + + 16:29 `` notable changes: util.runparts and subp out of util into subp.py, there are a couple of branches related to improved vmware support, and resolving keyerror issues for users providing network configuration with bridges. + + 16:30 `` also upstream travis CI is now using the commercial travis-ci.com instead of travis-ci-org which should give us better throughput on test runs. + + 16:31 `` community notice: if any PRs created >` 1 week ago have problems with unresolved travis ci runs marked 'in progress' those PRs will likely need to be closed and re-submitted due to the shift in travis-ci endpoints. + + 16:32 `` \#topic In-progress Development + + 16:33 `` Upstream devs are currently working our way through Ubuntu StableReleaseUpdate (SRU) validation to release cloud-init version 20.2.45 to Ubuntu Xenial, Bionic, Eoan and Focal. Thanks falcojr lucasmoura and Odd_Bloke for all the help generating test cases and reviewing SRU-related content. + + 16:34 `` We are about halfway through out testing of this release of cloud-init and expect to be able to wrap this up before next week. + + 16:34 `` To track this release, anyone can subscribe to the SRU process bug + + 16:35 `` \#link [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018) + + 16:35 `` Ubuntu bug 1881018 in cloud-init (Ubuntu) "sru cloud-init (19.4.33 to 20.2-45) Xenial, Bionic, Eoan and Focal" [Undecided,In progress] + + 16:35 `` that bug will go to Fix Released when our upload to ``-updates apt pocket is published + + 16:36 `` Beyond SRU, there is a significant refactor of cloudinit.net* module to define a clear API and push distro-specific content into the distro modules. + + 16:37 `` \#link + + 16:37 `` \#link [https://github.com/canonical/cloud-init/pull/391](https://github.com/canonical/cloud-init/pull/391) + + 16:38 `` Thanks Odd_Bloke for driving that refactor. Those interested should check out the above PR + + 16:39 `` I think that about wraps it. + + 16:40 `` during the util.subp refactor i suggested also looking into centralising service enabling and (re) starting + + 16:41 `` but we kinda glossed over that because of the net refactor + + 16:41 `` meena: good chance to bring that up: let's get that comment link + + 16:43 `` \#link [https://github.com/canonical/cloud-init/pull/416\#issuecomment-640032968](https://github.com/canonical/cloud-init/pull/416\#issuecomment-640032968) + + 16:44 `` meena: your comment was really about re-organizing the ./systemd ./upstart top-level directories and refactoring down into the distros somehow? + + 16:44 `` as that startup service construct is highly distro dependent? + + 16:46 `` If that's the suggestion you are raising for comment, I think it sounds like a reasonable thing to consider. Each distro has it's own way of handling system service management. + + 16:47 `` *nod + + 16:48 `` given the fact that all the systemd/ startup script files are all templates, it indicates that we have a lot of distro-specific uniqueness even across various flavors of linux + + 16:49 `` I think that refactor would be significantly simpler to describe in a distro-level API + + 16:51 `` meena: maybe we file a feature bug against cloud-init so we can prioritize that work. + + 16:51 `` you're right. let's do that + + 16:52 `` we could surface that bug to the mailinglist + + 16:53 `` meena: do you want to do either of those (bug or mailinglist email: subj: Refactor startup service to distro-specific Api) ? + + 16:53 `` \#action file feature bug about refactoring startup services + + 16:53 * meetingology file feature bug about refactoring startup services + + 16:53 `` \#action mailing list email requesting comment/concerns about a refactor of startup services + + 16:53 * meetingology mailing list email requesting comment/concerns about a refactor of startup services + + 16:54 `` I've added actions that we can track by next meeting to see if we can make progress on that discussion + + 16:54 `` ok next topic I think + + 16:54 `` \#topic community charter + + 16:55 `` As always, any aspects of the cloud-init project is open for participation from community members. + + 16:56 `` We thank everyone for contributing bugs @ [https://bugs.launchpad.net/cloud-init/+filebug](https://bugs.launchpad.net/cloud-init/+filebug), reviewing open 'New' bugs that are filed, and reviewing pulls requests @ [https://github.com/canonical/cloud-init/pulls](https://github.com/canonical/cloud-init/pulls) + + 16:57 `` all reviews are welcome on any PRs that are up. and driving feature discussions are also encouraged. Thanks meena for participating on all of those fronts + + 16:59 `` for those just wanting to join in and contribute small pull requests there is a queue of bugs or features that should be a fairly contained set of tasks in our bitesize queue: + + 16:59 `` \#link [https://bugs.launchpad.net/cloud-init/](https://bugs.launchpad.net/cloud-init/)?field.tag=bitezise + + 16:59 `` \#topic Office Hours (~next 30 minutes) + + 17:00 `` This 'section' of the meeting is a time where a couple of upstream devs will be available in channel for any discussions, questions, bug work or PR reviews. + + 17:01 `` In the absence of discussion topics, reviewing the active PRs generally occurs to scrub our queue and unblock conversations. + + 17:02 * blackboxsw addresses some review comments on a CI Ubuntu daily test branch + + 17:22 `` question: is there anyway to only target a particular reporting handler? + + 17:23 `` Right now the Azure DS emits events to the HyperV KVP handler and they also pass through the log handler. For the most part this is fine (and useful). For some larger event message (like compressed log), it does not make sense to emit a large blob of compressed gzip + b64 to the log, is it possible to skip the log handler ? + + 17:30 `` hrm, good question AnhVoMSFT . looking + + 17:33 `` blackboxsw: meena: Note that the service files are selected at package generation time, not at runtime, so it's not entirely clear to me how you would integrate them into the Distro hierarchy. + + 17:42 `` nice suggestion Odd_Bloke + + 17:43 `` AnhVoMSFT: I'm not seeing any filtering config options in reporting: config for handlers. Are you saying you are looking to add compressed object writes to your kvp message message plane? + + 17:44 * cyberpear wondering if there's any collaboration with the ignition folks + + 17:46 `` AnhVoMSFT: I think it's be reasonable to provide a named report handler to ReportEventStack + + 17:46 `` and let ReportEventStack limit what handlers it can emit publish_event to + + 17:48 `` [https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_puppet.py\#L106](https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_puppet.py\#L106) could this be entirely puppet specific, and no other module does this dance? + + 17:50 `` AnhVoMSFT: that'd mean I suppose that report_event would need to accept a new param to limit which handler it calls handler.publish_event for + + 17:50 `` [https://github.com/canonical/cloud-init/blob/master/cloudinit/reporting/events.py\#L84](https://github.com/canonical/cloud-init/blob/master/cloudinit/reporting/events.py\#L84) + + 17:52 `` [https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_rsyslog.py\#L210](https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_rsyslog.py\#L210) one more + + 17:52 `` or maybe you are suggesting that we add the ability for an existing handler to define a set of data types that it accepts (and will silently ignore others)? + + 17:54 `` and here meena [https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_fan.py\#L55-L83](https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_fan.py\#L55-L83) + + 17:58 `` ok I've got to run. time to close the meeting for today. Thanks all for joining in! + + 17:58 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2020-06-30.md b/content/status-2020-06-30.md new file mode 100644 index 0000000..409c27a --- /dev/null +++ b/content/status-2020-06-30.md @@ -0,0 +1,240 @@ +Title: Cloud-init bi-weekly status +Date: 2020-06-30 16:22:00 UTC +Category: status-meeting-minutes +Slug: status-2020-06-30 + +Meeting information +---------------- + * \#cloud-init: cloud-init status meeting, 30 Jun at 16:22 — 17:51 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-06-30-16.22.log.html](http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-06-30-16.22.log.html)]] + + + +Meeting summary +---------------- + + **LINK**: [https://cloud-init.github.io/status-2020-06-16.html\#status-2020-06-16](https://cloud-init.github.io/status-2020-06-16.html\#status-2020-06-16) +### Previous Actions +The discussion about "Previous Actions" started at 16:28. + + +### In-progress Development +The discussion about "In-progress Development" started at 16:31. + + * **LINK**: ACTION: mailing list email requesting comment/concerns about a refactor of startup services + * **LINK**: [https://paste.ubuntu.com/p/fSvwRks86z/](https://paste.ubuntu.com/p/fSvwRks86z/) + +### Recent Changes +The discussion about "Recent Changes" started at 16:34. + + * **LINK**: [https://cloudinit.readthedocs.io/en/latest/topics/hacking.html\#ongoing-refactors](https://cloudinit.readthedocs.io/en/latest/topics/hacking.html\#ongoing-refactors) + * **LINK**: [https://bugs.launchpad.net/cloud-init/+bugs](https://bugs.launchpad.net/cloud-init/+bugs)?field.tag=net-refactor + * **LINK**: [https://github.com/canonical/cloud-init/pull/457](https://github.com/canonical/cloud-init/pull/457) + +### In-progress Development +The discussion about "In-progress Development" started at 16:49. + + * **LINK**: [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018) + +### community charter +The discussion about "community charter" started at 17:02. + + * **LINK**: [https://bugs.launchpad.net/cloud-init/](https://bugs.launchpad.net/cloud-init/)?field.tag=bitesize + * **LINK**: [https://bugs.launchpad.net/cloud-init/+bugs](https://bugs.launchpad.net/cloud-init/+bugs)?field.tag=net-refactor + +### Office Hours (~20 mins) +The discussion about "Office Hours (~20 mins)" started at 17:08. + + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (73) + * meetingology (4) + * ubot5 (1) + * rharper (1) + * smoser (0) + * Odd_Bloke (0) + + + +Full Log +---------------- + + + 16:22 `` \#startmeeting cloud-init status meeting + + 16:22 `` Meeting started Tue Jun 30 16:22:42 2020 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:22 `` + + 16:22 `` Available commands: action commands idea info link nick + + 16:23 `` community notice: time for another bi-weekly (or semi-monthly if you prefer) cloud-init community status meeting + + 16:24 `` \#chair smoser rharper Odd_Bloke + + 16:24 `` Current chairs: Odd_Bloke blackboxsw rharper smoser + + 16:25 `` welcome to another round of cloud-init upstream updates and discussion. We use this meeting as a time to gather to discuss current development of cloud-init, ask and answer questions, and generally expedite development be unblocking devs. All questions. side-conversations and interruptions are welcome + + 16:25 `` last meeting minutes are at the link below + + 16:26 `` \#link [https://cloud-init.github.io/status-2020-06-16.html\#status-2020-06-16](https://cloud-init.github.io/status-2020-06-16.html\#status-2020-06-16) + + 16:26 `` turns out I didn't update the topic for the next meeting time last session. Let's do that now + + 16:26 `` +2 weeks from now, same time + + 16:26 `` July 14th, same UTC time + + 16:27 `` now that that's out of the way, we typically cover the following topics. + + 16:27 `` Previous Actions, Recent Changes, In-progress Development, Community Charter, Office Hours (~30 mins). + + 16:27 `` additionally today, I'll discuss the current cloud-init SRU + + 16:28 `` \#topic Previous Actions + + 16:28 `` topic \#1. our previous meeting minutes logged two actions: + + 16:28 * blackboxsw file feature bug about refactoring startup services + + 16:30 `` I think in further discussion during last meeting, we talked with Odd_Bloke and meena and determined that we can't actually refactor startup services to live in the distro specifically, because these startup service templates actually get determined at cloud-init generator time (before distribution is determined in cloud-init's python code) so trying to specialize startup script content generation in the distro + + 16:30 `` python classes in cloud-init is too late + + 16:30 `` so this action is tabled as /wont-fix + + 16:31 `` that follows as well with the other ACTION: mailing list email requesting comment/concerns about a refactor of startup services + + 16:31 * blackboxsw isn't sure how to close out actions in meetingology syntax/cmds + + 16:31 `` \#topic In-progress Development + + 16:33 `` The following is the set of commits landed in 'master' of cloud-init upstream repo: found with git log --since 06-20-2020 + + 16:33 `` \#link ACTION: mailing list email requesting comment/concerns about a refactor of startup services + + 16:33 `` \#link [https://paste.ubuntu.com/p/fSvwRks86z/](https://paste.ubuntu.com/p/fSvwRks86z/) + + 16:34 `` heh paste error + + 16:34 `` \#topic Recent Changes + + 16:34 * blackboxsw sets appropriate topic for this section + + 16:37 `` so recently Odd_Bloke and a number of BSD folks (meena igalic etc) have gone through a number of discussions and design regarding a refactor of cloudinit.net functions to a cloudinit.distro.networking module as most network-related functionality is highly distro-dependent + + 16:37 `` Odd_Bloke: created an overview of this current refactor work and published it to readthedocs + + 16:37 `` \#link [https://cloudinit.readthedocs.io/en/latest/topics/hacking.html\#ongoing-refactors](https://cloudinit.readthedocs.io/en/latest/topics/hacking.html\#ongoing-refactors) + + 16:38 `` This has been a big effort to get organized and started so many thanks for all those paricipating in this discussion, development and reviews. + + 16:39 `` there are many, functions that need to be refactored from cloudinit.net into the distribution-specialized cloudinit.distro.networking classes. + + 16:40 `` It is work that can be easily done in parallel and there is a tag used to classify each refactor as a "net-refactor" bug in launchpad + + 16:40 `` \#link [https://bugs.launchpad.net/cloud-init/+bugs](https://bugs.launchpad.net/cloud-init/+bugs)?field.tag=net-refactor + + 16:41 `` community notice: we encourage anyone interested in refactoring cloud-init networking functionality to grab and work any of those net-refactor bugs + + 16:41 `` there are a couple of example PRs up that give a good idea of how to get started + + 16:42 `` \#link [https://github.com/canonical/cloud-init/pull/457](https://github.com/canonical/cloud-init/pull/457) + + 16:42 `` and I can't seem to find the other at the moment. + + 16:48 `` besides net-refactor content landing, there have been fixes to Hetzner and RbxCloud datasources, redhat's systemd generator templates, Centos copr build fixes to help RPM build runs and Azure datasource logging. Thanks smoser, paride Moustafa and otubo Adam Dobrawy for contributions this round + + 16:49 `` \#topic In-progress Development + + 16:51 `` Generally the last two weeks have been sunk into upstream testing and validation of cloud-init for SRU (Stable release Update) into Ubuntu Xenial Bionic, Eoan and Focal. + + 16:52 `` 3 to 5 of us have been on verification tasks on various clouds for all Ubuntu releases targeted and all features which affect ubuntu. + + 16:52 `` A thousand thanks rharper Odd_Bloke factor lucasmoura and xiaofeng for working through and validating some of these SRU tasks. + + 16:54 `` Our job is done, and we are awaiting feedback from an automation CI from Canonical solutions QA at the moment which runs through a ton of Openstack networking customer-configurations. It has been in the test queue for a week, and I just saw a successful run from that test harness this morning. That team has told us it looks for 3 successful runs to "pass" so I expect that pass to come shortly as the test runs + + 16:54 `` are currently inprogress. + + 16:55 `` as soon as this test passes we will mark the SRU bug verified and the SRU team will publish bits of cloud-init. + + 16:55 `` \#link [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018) + + 16:55 `` Ubuntu bug 1881018 in cloud-init (Ubuntu) "sru cloud-init (19.4.33 to 20.2-45) Xenial, Bionic, Eoan and Focal" [Undecided,In progress] + + 16:56 `` This SRU has taken about 1+ week longer than normal verification because we hadn't SRU'd cloud-init in around 6 months, so there was a lot more content to verify. + + 16:57 `` Hopefully additional SRUs will be more frequent and less heavy-weight. We are looking into reducing the overhead on this process and will pitch ideas to the cloud-init mailinglist for input + + 16:57 `` Beyond SRU work, the following other work is in progress: + + 16:58 `` * net-refactor formerly mentioned + + 16:58 `` * falcojr into Oracle integration test harness + + 16:58 `` * extending json schema validation for remaining cloud-config modules for better error reporting around invalid user-data + + 17:00 `` Long term work: cloud-init standalone daemon to improve startup time by avoiding reloading python across each cloud-int boot stage, initial networking hot-plug support to which datasources could "opt-in" + + 17:01 `` blackboxsw: =) + + 17:01 `` I think that about wraps this topic. + + 17:01 `` yeah rharper, we've got it on our roadmap. We'd love to see that get in this round. + + 17:02 `` \#topic community charter + + 17:03 `` We have a couple of general themes of features we are working toward as a community this year: + + 17:04 `` * json schema additions for cloudinit.config.cc_* modules to improve user-facing errors on invalid user-data + + 17:04 `` * datasource documentation improvements, updates and corrections + + 17:04 `` * cloudinit.net-refactor work + + 17:05 `` We encourage any interested developers to grab any of these work items related to these features. + + 17:06 `` We have two bug tags which enumerate each component of these work streams: + + 17:07 `` \#link [https://bugs.launchpad.net/cloud-init/](https://bugs.launchpad.net/cloud-init/)?field.tag=bitesize + + 17:07 `` \#link [https://bugs.launchpad.net/cloud-init/+bugs](https://bugs.launchpad.net/cloud-init/+bugs)?field.tag=net-refactor + + 17:08 `` \#topic Office Hours (~20 mins) + + 17:08 `` This 'section' of the meeting is a time where a couple of upstream devs will be available in channel for any discussions, questions, bug work or PR reviews. + + 17:08 `` I think I spent most of the time typing, but will hit the review queue in the absence of any other discussion + + 17:17 `` merged [https://github.com/canonical/cloud-init/pull/461](https://github.com/canonical/cloud-init/pull/461) + + 17:51 `` lucasmoura: one minor change request and description update on the PR requested [https://github.com/canonical/cloud-init/pull/390\#pullrequestreview-440241947](https://github.com/canonical/cloud-init/pull/390\#pullrequestreview-440241947) + + 17:51 `` then we can land this one + + 17:51 `` ok folks, thanks for checking into the cloud-init status meeting. See you in 2 weeks. + + 17:51 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2020-07-14.md b/content/status-2020-07-14.md new file mode 100644 index 0000000..e949aca --- /dev/null +++ b/content/status-2020-07-14.md @@ -0,0 +1,206 @@ +Title: Cloud-init bi-weekly status +Date: 2020-07-14 16:52:00 UTC +Category: status-meeting-minutes +Slug: status-2020-07-14 + +Meeting information +---------------- + * \#cloud-init: cloud-init status meeting, 14 Jul at 16:52 — 17:50 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-07-14-16.52.log.html](http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-07-14-16.52.log.html)]] + + + +Meeting summary +---------------- + + **LINK**: [https://cloud-init.github.io/status-2020-06-30.html\#status-2020-06-30](https://cloud-init.github.io/status-2020-06-30.html\#status-2020-06-30) +### Previous Actions +The discussion about "Previous Actions" started at 16:55. + + +### Recent Changes +The discussion about "Recent Changes" started at 16:56. + + * **LINK**: [https://paste.ubuntu.com/p/6Fn5jy8t46/](https://paste.ubuntu.com/p/6Fn5jy8t46/) + +### In-progress Development +The discussion about "In-progress Development" started at 17:01. + + * **LINK**: [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018) + +### Community Charter +The discussion about "Community Charter" started at 17:08. + + * **LINK**: k [https://bugs.launchpad.net/cloud-init/](https://bugs.launchpad.net/cloud-init/)?field.tag=bitesize + * **LINK**: [https://bugs.launchpad.net/cloud-init/+bugs](https://bugs.launchpad.net/cloud-init/+bugs)?field.tag=net-refactor + * **LINK**: [https://cloudinit.readthedocs.io/en/latest/topics/hacking.html\#ongoing-refactors](https://cloudinit.readthedocs.io/en/latest/topics/hacking.html\#ongoing-refactors) + +### Office Hours (next ~30 mins) +The discussion about "Office Hours (next ~30 mins)" started at 17:13. + + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (52) + * ubot5 (5) + * meetingology (4) + * AnhVoMSFT (2) + * Odd_Bloke (2) + * smoser (0) + * rharper (0) + + + +Full Log +---------------- + + + 16:52 `` \#startmeeting cloud-init status meeting + + 16:52 `` Meeting started Tue Jul 14 16:52:35 2020 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:52 `` + + 16:52 `` Available commands: action commands idea info link nick + + 16:52 `` nvm + + 16:52 `` heh. + + 16:52 `` let's do it since we have an active attendee. + + 16:53 `` i'll make it snappy today + + 16:53 `` sounds good + + 16:53 `` community notice: time for another bi-weekly (or semi-monthly if you prefer) cloud-init community status meeting + + 16:53 `` \#chair rharper Odd_Bloke smoser + + 16:53 `` Current chairs: Odd_Bloke blackboxsw rharper smoser + + 16:53 `` welcome to another round of cloud-init upstream updates and discussion. We use this meeting as a time to gather to discuss current development of cloud-init, ask and answer questions, and generally expedite development be unblocking devs. All questions. side-conversations and interruptions are welcome + + 16:54 `` first order of bizzzznesss. setting the meeting for next time + + 16:54 `` +2 weeks from today + + 16:54 `` July 28th same time (minus 30 mins) + + 16:55 `` previous meeting minutes are here: + + 16:55 `` \#link [https://cloud-init.github.io/status-2020-06-30.html\#status-2020-06-30](https://cloud-init.github.io/status-2020-06-30.html\#status-2020-06-30) + + 16:55 `` The topics we'll cover today: Previous Actions, Recent Changes, In-progress Development, Community Charter, Office Hours (~30 mins). + + 16:55 `` \#topic Previous Actions + + 16:56 `` none seen last session. so we can jump to the next topic + + 16:56 `` \#topic Recent Changes + + 16:56 `` The following commits have been landed on master of upstream branch since last meeting: found via git log --since 2020-06-30 + + 16:57 `` \#link [https://paste.ubuntu.com/p/6Fn5jy8t46/](https://paste.ubuntu.com/p/6Fn5jy8t46/) + + 16:58 `` a bit of cleanup and test coverage work and CI fixups for lxd integratin testing in those commits. + + 16:58 `` Of note: + + 16:59 `` a fix for (LP: \#1456277) thx lucas + + 16:59 `` Launchpad bug 1456277 in cloud-init "cloud-init searches for ec2 mirrors regardless of what cloud its on" [High,Fix committed] [https://launchpad.net/bugs/1456277](https://launchpad.net/bugs/1456277) + + 16:59 `` a fix for (LP: \#1884619) part of the cloudinit.net refactor for thx Odd_Bloke + + 16:59 `` Launchpad bug 1884619 in cloud-init "cloudinit.net refactor: is_physical" [Low,Fix committed] [https://launchpad.net/bugs/1884619](https://launchpad.net/bugs/1884619) + + 16:59 `` and (LP: \#1886531) fix for missing /etc/fstab file path thx rharper + + 16:59 `` Launchpad bug 1886531 in cloud-init "cloud-init status broken in groovy lxd containers" [Medium,Fix committed] [https://launchpad.net/bugs/1886531](https://launchpad.net/bugs/1886531) + + 17:00 `` and thanks paride for fixing our CI tests for lxd-based targets + + 17:01 `` I think that about wraps recent-changes. + + 17:01 `` \#topic In-progress Development + + 17:02 `` I was hoping today we'd be able to finally say cloud-init 20.2 has published and released to Ubuntu Xenial. Bionic, Eoan and Focal. All testing is complete, we have unblocked any of this process on our side and we are awaiting an SRU team representative to review and release the bits into Ubuntu proper. + + 17:03 `` We pinged yesterday and a few hour ago again to get this SRU reviewed and released. Expectation is that it will be released to all Ubuntu series today/tonight, so I'd expect that cloud images see that update in the next day or two. + + 17:04 `` for those watching at home, the folowing bug will be closed as fix-released once cloud-init SRU is published. + + 17:04 `` \#link [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018) + + 17:04 `` Ubuntu bug 1881018 in cloud-init (Ubuntu) "sru cloud-init (19.4.33 to 20.2-45) Xenial, Bionic, Eoan and Focal" [Undecided,In progress] + + 17:06 `` for context, this was a beast of an SRU (as upstream waited too long (~6 months) between to get the SRUs, which involved more verification and complexity. We will make sure to avoid some of this complexity in the future by more frequent SRUs and more requests for community validation I expect. + + 17:07 `` Also, expect that when this SRU is published, and email will be sent to cloud-init@lists.launchpad.net and a discourse post as well as a "community-notice:" banned comment + + 17:08 `` \#topic Community Charter + + 17:08 `` Community driven development is what helps keep cloud-init active, so that you all for your contributions ( PR reviews, bugs, PR development, discussion etc). + + 17:09 `` we have a number of general goals we continue to work toward: + + 17:10 `` - json schema coverage of cloudinit.config.cc_* modules for better error reporting on malformed user-data + + 17:10 `` - datasource documentation updates and content creation needs + + 17:10 `` - cloudinit.net refactor into distro-specific networking subclasses cloudinit.distros.networking + + 17:11 `` Bugs associated with that work are available for anyone to own + + 17:11 `` \#link k [https://bugs.launchpad.net/cloud-init/](https://bugs.launchpad.net/cloud-init/)?field.tag=bitesize + + 17:11 `` \#link [https://bugs.launchpad.net/cloud-init/+bugs](https://bugs.launchpad.net/cloud-init/+bugs)?field.tag=net-refactor + + 17:11 `` And details docs on existing refactor are available here + + 17:12 `` \#link [https://cloudinit.readthedocs.io/en/latest/topics/hacking.html\#ongoing-refactors](https://cloudinit.readthedocs.io/en/latest/topics/hacking.html\#ongoing-refactors) + + 17:13 `` If anyone would like to be involved more than they currently are, please feel free to contact us here in IRC \#cloud-init on Freenode or on the mailing list cloud-init@lists.launchpad.net and we can see how best we can get you "set up" + + 17:13 `` \#topic Office Hours (next ~30 mins) + + 17:13 `` This 'section' of the meeting is a time where a couple of upstream devs will be available in channel for any discussions, questions, bug work or PR reviews. + + 17:14 `` any topics, bugs, PRs or concerns or rotten fruit to throw are all welcome :). In the absence of dicussion, cloud-init PR reviews are prioritized + + 17:18 `` Odd_Bloke: can I merge the following as your squashmerge commit message for PR [https://github.com/canonical/cloud-init/pull/466](https://github.com/canonical/cloud-init/pull/466) [https://paste.ubuntu.com/p/ZRdq4bYWG7/](https://paste.ubuntu.com/p/ZRdq4bYWG7/) I think it fixed LP: \#1884626 + + 17:18 `` Launchpad bug 1884626 in cloud-init "cloudinit.net refactor: wait_for_physdevs" [Low,In progress] [https://launchpad.net/bugs/1884626](https://launchpad.net/bugs/1884626) + + 17:31 `` blackboxsw: You cannot (because I just did ;). + + 17:31 `` :sad trombone: + + 17:43 `` I just reran the RTD doc build and it passed this time (for anyone else who just got that failure email). + + 17:50 `` Ok I think that about wraps the status meeting + + 17:50 `` thanks for tuning in folks + + 17:50 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2020-07-28.md b/content/status-2020-07-28.md new file mode 100644 index 0000000..5097362 --- /dev/null +++ b/content/status-2020-07-28.md @@ -0,0 +1,154 @@ +Title: Cloud-init bi-weekly status +Date: 2020-07-28 16:55:00 UTC +Category: status-meeting-minutes +Slug: status-2020-07-28 + +Meeting information +---------------- + * \#cloud-init: cloud-init status meeting, 28 Jul at 16:55 — 17:56 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-07-28-16.55.log.html](http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-07-28-16.55.log.html)]] + + + +Meeting summary +---------------- + + **LINK**: [https://cloud-init.github.io/status-2020-07-14.html\#status-2020-07-14](https://cloud-init.github.io/status-2020-07-14.html\#status-2020-07-14) +### Previous Actions +The discussion about "Previous Actions" started at 16:58. + + +### Recent Changes +The discussion about "Recent Changes" started at 17:00. + + * **LINK**: [https://paste.ubuntu.com/p/RjZcwtk6Hd/](https://paste.ubuntu.com/p/RjZcwtk6Hd/) + +### In-progress Development +The discussion about "In-progress Development" started at 17:05. + + +### Community Charter +The discussion about "Community Charter" started at 17:11. + + +### Office Hours (next ~30 mins) +The discussion about "Office Hours (next ~30 mins)" started at 17:15. + + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw_ (38) + * meetingology (4) + * rharper (0) + * Odd_Bloke (0) + * smoser (0) + + + +Full Log +---------------- + + + 16:55 `` \#startmeeting cloud-init status meeting + + 16:55 `` Meeting started Tue Jul 28 16:55:17 2020 UTC. The chair is blackboxsw_. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:55 `` + + 16:55 `` Available commands: action commands idea info link nick + + 16:56 `` community notice: time for another bi-weekly (or semi-monthly if you prefer) cloud-init community status meeting + + 16:56 `` \#chair Odd_Bloke smoser rharper + + 16:56 `` Current chairs: Odd_Bloke blackboxsw_ rharper smoser + + 16:57 `` Hello folks, cloud-init community status roundup. We gather here in this IRC channel every 2 weeks to discuss current development tasks and progress on cloud-init. + + 16:57 `` All questions. side-conversations and interruptions are welcome + + 16:58 `` Last meeting minutes live here + + 16:58 `` \#link [https://cloud-init.github.io/status-2020-07-14.html\#status-2020-07-14](https://cloud-init.github.io/status-2020-07-14.html\#status-2020-07-14) + + 16:58 `` he topics we'll cover today: Previous Actions, Recent Changes, In-progress Development, Community Charter, Office Hours (~30 mins). + + 16:58 `` \#topic Previous Actions + + 16:58 `` None found in meeting minutes from last session. + + 16:59 * blackboxsw_ sets the topic for next meeting. + + 16:59 `` +2 weeks from now + + 16:59 `` August 11th 16:15 UTC + + 17:00 `` \#topic Recent Changes + + 17:00 `` The following commits have been landed on master of upstream branch since last meeting: found via git log --since 2020-07-14 + + 17:01 `` \#link [https://paste.ubuntu.com/p/RjZcwtk6Hd/](https://paste.ubuntu.com/p/RjZcwtk6Hd/) + + 17:02 `` features of note: + + 17:02 `` - azure: avoid bouncing hostname if set hostname fails + + 17:03 `` - vmware: new defaults for post customization script overrides on vCloud + + 17:04 `` - azure ValueError raised if JsonDecodeErrors is not available when parsing metadata + + 17:05 `` Thanks Goneri otubo anhVo and dermotbradley for community contributions this round + + 17:05 `` \#topic In-progress Development + + 17:09 `` Current projects for cloud-init are leading us to additional features: + + 17:10 `` - network device hot plug support for cloud-init post-boot + + 17:10 `` - better integration testing on other clouds, Oracle support + + 17:11 `` - extended json schema validation and publishing full static schema versions for external tools + + 17:11 `` \#topic Community Charter + + 17:12 `` The following topics are still topics for ongoing community development: + + 17:13 `` - JSON schema extensions to validate user-data before instance launch: [https://bugs.launchpad.net/cloud-init/](https://bugs.launchpad.net/cloud-init/)?field.tag=bitesize + + 17:13 `` - Datasource documentation and updates + + 17:14 `` - cloudinit.net refactor into distro-specific networking subclasses cloudinit.distros.networking: [https://bugs.launchpad.net/cloud-init/+bugs](https://bugs.launchpad.net/cloud-init/+bugs)?field.tag=net-refactor + + 17:15 `` As always: thank you all for bug contributions, PR submissions, triage and discussion participation. + + 17:15 `` If anyone would like to be involved more than they currently are, please feel free to contact us here in IRC \#cloud-init on Freenode or on the mailing list cloud-init@lists.launchpad.net and we can see how best we can get you "set up" + + 17:15 `` \#topic Office Hours (next ~30 mins) + + 17:17 `` This time of the meeting is really just an open door for any discussions, concerns, bugs, questions or general prodding of upstream devs to make sure existing development work is unblocked where possible. + + 17:17 `` In the absence of discussions, review of existing PRs is addressed. + + 17:56 `` Thanks for tuning in folks. have a good one! + + 17:56 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2020-08-25.md b/content/status-2020-08-25.md new file mode 100644 index 0000000..a478493 --- /dev/null +++ b/content/status-2020-08-25.md @@ -0,0 +1,210 @@ +Title: Cloud-init bi-weekly status +Date: 2020-08-25 16:24:00 UTC +Category: status-meeting-minutes +Slug: status-2020-08-25 + +Meeting information +---------------- + * \#cloud-init: cloud-init status meeting, 25 Aug at 16:24 — 17:13 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-08-25-16.24.log.html](http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-08-25-16.24.log.html)]] + + + +Meeting summary +---------------- + + **LINK**: [https://cloud-init.github.io](https://cloud-init.github.io) +### Previous Actions +The discussion about "Previous Actions" started at 16:27. + + +### Recent Changes +The discussion about "Recent Changes" started at 16:27. + + * **LINK**: [https://paste.ubuntu.com/p/h2qxwKwvFw/](https://paste.ubuntu.com/p/h2qxwKwvFw/) + +### In-progress Development +The discussion about "In-progress Development" started at 16:35. + + * **LINK**: [https://wiki.ubuntu.com/CloudinitUpdates](https://wiki.ubuntu.com/CloudinitUpdates) + +### Community Charter +The discussion about "Community Charter" started at 16:40. + + +### \#cloud-init pull-requests [https://git.io/JeVed](https://git.io/JeVed) | Meeting minutes: [https://goo.gl/mrHdaj](https://goo.gl/mrHdaj) | Next status meeting Sep 8 16:15 UTC | 20.2 (Apr 26) | 20.3 (estimated Aug 19th) [https://bugs.launchpad.net/cloud-init/+filebug](https://bugs.launchpad.net/cloud-init/+filebug) +The discussion about "\#cloud-init pull-requests [https://git.io/JeVed](https://git.io/JeVed) | Meeting minutes: [https://goo.gl/mrHdaj](https://goo.gl/mrHdaj) | Next status meeting Sep 8 16:15 UTC | 20.2 (Apr 26) | 20.3 (estimated Aug 19th) [https://bugs.launchpad.net/cloud-init/+filebug](https://bugs.launchpad.net/cloud-init/+filebug)" started at 16:48. + + * **ACTION**: bbsw add workitem to SRU release process to announce to mailinglist estimated next SRU timeframe + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw_ (58) + * meetingology (5) + * AnhVoMSFT (4) + * falcojr (1) + * smoser (0) + * lucasmoura (0) + * rharper (0) + + + +Full Log +---------------- + + + 16:24 `` \#startmeeting cloud-init status meeting + + 16:24 `` Meeting started Tue Aug 25 16:24:27 2020 UTC. The chair is blackboxsw_. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:24 `` + + 16:24 `` Available commands: action commands idea info link nick + + 16:24 `` \#chair smoser rharper falcojr lucasmoura + + 16:24 `` Current chairs: blackboxsw_ falcojr lucasmoura rharper smoser + + 16:25 `` hey folks, welcome to another cloud-init bi-weekly (or bi-monthly) community status meeting + + 16:25 `` or semi-monthly + + 16:26 `` ... anyhow. We use this platform/channel to discuss latest and greatest cloud-init, as well as ensuring that there are a couple of upstream developers present to field questions or discussion as needed. + + 16:26 `` We gather here in this IRC channel every 2 weeks to discuss current development tasks and progress on cloud-init. All questions and side-conversations welcome + + 16:26 `` we keep our meeting minutes from previous meetings here: + + 16:27 `` \#link [https://cloud-init.github.io](https://cloud-init.github.io) + + 16:27 `` The topics we'll cover today: Previous Actions, Recent Changes, In-progress Development, Community Charter, Office Hours (~30 mins). + + 16:27 `` \#topic Previous Actions + + 16:27 `` Looks like no carryover actions from last meeting + + 16:27 `` \#topic Recent Changes + + 16:30 `` The following changes have landed in tip of master since last meeting (08/14/20). + + 16:30 `` found via git log --since 2020-08-014 + + 16:30 `` \#link [https://paste.ubuntu.com/p/h2qxwKwvFw/](https://paste.ubuntu.com/p/h2qxwKwvFw/) + + 16:31 `` things to note. we *JUST* cut 20.3 upstream release as of 20 seconds ago. Thanks a bunch James(falcojr) for getting the Azure timeout pr up to close out this upstream release. + + 16:31 `` and thanks smoser, rharper and meena for all the reviews and work here. + + 16:34 `` in the last couple weeks we got fixes to reduce boot timeouts for certain azure accelerated network instances, fix oracle datasource retries, handle compressed user-data on juju deployed machines in 'cloud-init query', and early boot dhclient will not attempt to run outside of the /var/tmp sandbox directory if that directory is marked no-exec + + 16:34 `` thanks otubo for that noexec branch + + 16:35 `` \#topic In-progress Development + + 16:36 `` So thanks all for the 20.3 upstream release. We will be tagging that release and pushing that tag to master just after this meeting + + 16:36 `` falcojr: is our release lead for this upstream release and SRU so he'll be working through the release process work items. Thanks falcojr. + + 16:37 `` -next step on the release process is to publish to Ubuntu Groovy (20.10) and then queue up a -proposed cloud-init SRU upload into xenial, bionic and focal. + + 16:37 `` we will then begin the SRU testing (which we hope to keep at around ~7days) + + 16:38 `` as smoser mentioned earlier. cloud-init has to follow this process to update cloud-init in stable Ubuntu releases + + 16:38 `` \#link [https://wiki.ubuntu.com/CloudinitUpdates](https://wiki.ubuntu.com/CloudinitUpdates) + + 16:39 `` An email will be sent to the cloud-init mailinglist notifying the community about the SRU under test in the event that folks have spare cycles to pitch in on some of the verification effort + + 16:40 `` also "in-progress" paride is cleaning up a bunch of automated CI-related failures and lint issues in cloud-init, so expect some branches against cloud-init on that front as well + + 16:40 `` \#topic Community Charter + + 16:41 `` The following topics are still topics for ongoing community development anyone new to cloud-init, or with a bit of time could easily grab one of these bitesized tasks: + + 16:41 `` JSON schema extensions to validate user-data before instance launch: [https://bugs.launchpad.net/cloud-init/](https://bugs.launchpad.net/cloud-init/)?field.tag=bitesize + + 16:41 `` - Datasource documentation and updates + + 16:41 `` - cloudinit.net refactor into distro-specific networking subclasses cloudinit.distros.networking: [https://bugs.launchpad.net/cloud-init/+bugs](https://bugs.launchpad.net/cloud-init/+bugs)?field.tag=net-refactor + + 16:41 `` As always: thank you all for bug contributions, PR submissions, triage and discussion participation. + + 16:41 `` If anyone would like to be involved more than they currently are, please feel free to contact us here in IRC \#cloud-init on Freenode or on the mailing list cloud-init@lists.launchpad.net and we can see how best we can get you "set up" + + 16:42 `` \#topic Office Hours (next ~30 mins) + + 16:42 `` his time of the meeting is really just an open door for any discussions, concerns, bugs, questions or general prodding of upstream devs to make sure existing development work is unblocked where possible. + + 16:42 `` *This time + + 16:42 `` while we're at it with meeting time.... I'll set the next cloud-init status meeting date in the topic of this IRC channel + + 16:42 `` When do you anticipate the next SRU would be? + + 16:43 `` (after 20.3) + + 16:44 `` AnhVoMSFT: thanks for the question. I hope today for 20.3, I think 20.4 will likely align with the next Ubuntu release cycle (20.10) so, October, 2020 + + 16:46 `` as mentioned in passing earlier, we are looking at trying to create an upstream release of cloud-init when any significant feature set has landed in tip to make release verification easier (and hopefull include less sprawling sets of broad commit streams). + + 16:46 `` this ultimately may translated to 4-5 releases per year + + 16:46 `` I expect a frequency of `< 3 months + + 16:48 `` \#topic \#cloud-init pull-requests [https://git.io/JeVed](https://git.io/JeVed) | Meeting minutes: [https://goo.gl/mrHdaj](https://goo.gl/mrHdaj) | Next status meeting Sep 8 16:15 UTC | 20.2 (Apr 26) | 20.3 (estimated Aug 19th) [https://bugs.launchpad.net/cloud-init/+filebug](https://bugs.launchpad.net/cloud-init/+filebug) + + 16:49 `` next status meeting sept 8th, same time ^ + + 16:49 `` Thanks. There's some planned work for Azure's pre-provisioning v2 and will need some change in cloud-init. We're trying to get a sense of when cloud-init SRUs land so that we can communicate the timeline + + 16:52 `` @AnhVoMSFT generally cadence has been ~3 months between SRUs, I think we'd like to see a slightly higher frequency than that because our last SRU was so costly. but I think expectation for this pass is likely 10/15/2020 + + 16:53 `` also, if we are looking to test features in Ubuntu Groovy 20.10 images, they don't require an SRU, so upload to that development release are possible any time (we could do that as frequently as weekly if need be) + + 16:56 `` thanks for the clarification @blackboxsw_ + + 16:57 `` so as of today, I expect we'll have an SRU in October and likely something beginning of Jan + + 16:57 `` I'll take an action for us to communicate via mailinglist the next estimated SRU once this SRU for 20.3 closes out + + 16:59 `` \#action bbsw add workitem to SRU release process to announce to mailinglist estimated next SRU timeframe + + 16:59 * meetingology bbsw add workitem to SRU release process to announce to mailinglist estimated next SRU timeframe + + 16:59 `` and again we hope to have 20.3 SRU complete by next week + + 16:59 `` complete, as in publish the 20.3 SRU for next week into Ubuntu xenial and later + + 17:00 `` I expect today we publish tip of master (20.3) into Ubuntu Groovy (20.10) so expect to see it in your friendly neighborhood ubuntu cloud-images in the next day or two + + 17:04 `` falcojr: I just annotated tag 20.3 and pushed to upstream + + 17:04 `` so we have a signed tag + + 17:04 `` falcojr: so next task is [https://trello.com/c/KxShylli/14-upload-source-tarball-to-launchpad](https://trello.com/c/KxShylli/14-upload-source-tarball-to-launchpad) + + 17:05 `` Cool, I can jump on that + + 17:12 `` ok I think we'll wrap up the status meeting. Thanks all for tuning in! + + 17:13 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2020-09-08.md b/content/status-2020-09-08.md new file mode 100644 index 0000000..792fb2d --- /dev/null +++ b/content/status-2020-09-08.md @@ -0,0 +1,184 @@ +Title: Cloud-init bi-weekly status +Date: 2020-09-08 16:18:00 UTC +Category: status-meeting-minutes +Slug: status-2020-09-08 + +Meeting information +---------------- + * \#cloud-init: cloud-init status meeting, 08 Sep at 16:18 — 17:13 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-09-08-16.18.log.html](http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-09-08-16.18.log.html)]] + + + +Meeting summary +---------------- + + **LINK**: [https://cloud-init.github.io/status-2020-08-25.html\#status-2020-08-25](https://cloud-init.github.io/status-2020-08-25.html\#status-2020-08-25) +### Previous Actions +The discussion about "Previous Actions" started at 16:21. + + +### Recent Changes +The discussion about "Recent Changes" started at 16:25. + + * **LINK**: [https://paste.ubuntu.com/p/NgqncRMG9c/](https://paste.ubuntu.com/p/NgqncRMG9c/) + +### In-progress Development +The discussion about "In-progress Development" started at 16:46. + + * **LINK**: [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1893064](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1893064) + +### Office Hours (next ~30 mins) +The discussion about "Office Hours (next ~30 mins)" started at 16:54. + + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (51) + * meetingology (3) + * amansi26 (3) + * ubot5 (2) + + + +Full Log +---------------- + + + 16:18 `` \#startmeeting cloud-init status meeting + + 16:18 `` Meeting started Tue Sep 8 16:18:47 2020 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 16:18 `` + + 16:18 `` Available commands: action commands idea info link nick + + 16:19 `` \#chairs smoser Odd_Bloke rharper falcojr lucasmoura + + 16:19 `` hey folks. welcome to another public cloud-init status meeting + + 16:19 `` disclaimer: interruptions and side conversations are welcome + + 16:19 `` We use this platform/channel to discuss latest and greatest cloud-init, as well as ensuring that there are a couple of upstream developers present to field questions or discussion as needed. + + 16:20 `` We gather here in this IRC channel every 2 weeks to discuss current development tasks and progress on cloud-init. + + 16:20 `` Previous meeting minutes are here; + + 16:20 `` \#link [https://cloud-init.github.io/status-2020-08-25.html\#status-2020-08-25](https://cloud-init.github.io/status-2020-08-25.html\#status-2020-08-25) + + 16:20 `` The topics we'll cover today: Previous Actions, Recent Changes, In-progress Development, Community Charter, Office Hours (~30 mins). + + 16:21 `` I expect today will be short as the entire Canonical team is involved in cloud-init SRU verification for Ubuntu at the moment + + 16:21 `` \#topic Previous Actions + + 16:22 `` last meeting had an action item we needed to resolve + + 16:22 `` bbsw add workitem to SRU release process to announce to mailinglist estimated next SRU timeframe. + + 16:24 `` this item can be resolved as I've added the content requested to our email template which will be sent out once this SRU completes. + + 16:24 `` I see no other actions from last meeting + + 16:25 `` \#topic Recent Changes + + 16:26 `` The following are upstream commits landed in cloud-init's master branch: + + 16:26 `` \#link [https://paste.ubuntu.com/p/NgqncRMG9c/](https://paste.ubuntu.com/p/NgqncRMG9c/) + + 16:28 `` In the last couple of weeks we cut the upstream 20.3 release (thanks everyone for all the help there). Queued SRU uploads for ubuntu/xenial, bionic and focal release testing. + + 16:28 `` blackboxsw: metadata here will be the configdrive, if my understanding is right? + + 16:30 `` And added some goodness to systemd units and ordering (sort systemd cloud-init-local.service hv_kvp_daemon and systemd: add Before=shutdown.target when Conflicts=shutdown.target is + + 16:30 `` used ) + + 16:30 `` thanks paride and robjo for those commits + + 16:30 `` amansi26: +1 you can see the metadata configured hostname from cloud-init query local-hostname I think + + 16:30 `` amansi26: +1 you can see the metadata configured hostname from `cloud-init query local-hostname` I think + + 16:30 `` amansi26: I was just starting to respond to your bug you linked too + + 16:31 `` I think preserve_hostname: false (which is cloud-init's default behavior ) means cloud-init will read that hostname from metadata and apply it to the system + + 16:31 `` Sure. there is another bug which I observed on a RHEL8 environment: [https://bugs.launchpad.net/cloud-init/+bug/1894837](https://bugs.launchpad.net/cloud-init/+bug/1894837) + + 16:31 `` Ubuntu bug 1894837 in cloud-init "RHEL8 ipv4 IPs not getting set" [Undecided,New] + + 16:35 `` amansi26: sorry cloud-init query local_hostname (\# not with a hyphen) + + 16:35 `` checking 2nd bug + + 16:38 `` so amansi26 you'd like the ability to override the iface_defaults on rhel systems for NM_CONTROLLED to set True instead of false for cloud-init interfaces? + + 16:40 `` generally if cloud-init is rendering network configuration on an instance, it tries to avoid using network manager by default. I think it's worth requesting logs on your bug + + 16:40 `` those cloud-init logs can be obtained using cloud-init collect-logs (which generates a tar.gz file in the current working directory). then attach that to the bug + + 16:41 `` yes, since I was reading the documentation for RHEL8 network configuration, I found that NM_CONTROLLED = yes should be there. but we are passing the value as No. Sure I will attach the logs to the defect + + 16:43 `` thanks amansi26 I responded on that bug too + + 16:46 `` Ok, per the meeting, that wraps \#recent-changes topic I believe + + 16:46 `` \#topic In-progress Development + + 16:48 `` Currently the Canonical team is working hard on SRU verification so we can release cloud-init v. 20.3 to Xenial, Bionic and Focal. It looks like we are done with most major cloud verification and walking through individual verification items. + + 16:50 `` I believe falcojr mentioned this morning we are about 5 of 30ish verification items complete. + + 16:50 `` we are continuing to work this verification as our top priority + + 16:50 `` folks interested should subscribe to updates on our SRU bug + + 16:51 `` \#link [https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1893064](https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1893064) + + 16:51 `` Ubuntu bug 1893064 in cloud-init (Ubuntu) "sru cloud-init (20.2-45 to 20.3-2) Xenial, Bionic, and Focal" [Undecided,In progress] + + 16:53 `` that bug will transition to verification-complete once all verification is done + + 16:54 `` \#topic Community Charter + + 16:54 `` The following topics are still topics for ongoing community development anyone new to cloud-init, or with a bit of time could easily grab one of these bitesized tasks: + + 16:54 `` JSON schema extensions to validate user-data before instance launch: [https://bugs.launchpad.net/cloud-init/](https://bugs.launchpad.net/cloud-init/)?field.tag=bitesize + + 16:54 `` - cloudinit.net refactor into distro-specific networking subclasses cloudinit.distros.networking: [https://bugs.launchpad.net/cloud-init/+bugs](https://bugs.launchpad.net/cloud-init/+bugs)?field.tag=net-refactor + + 16:54 `` If anyone would like to be involved more than they currently are, please feel free to contact us here in IRC \#cloud-init on Freenode or on the mailing list cloud-init@lists.launchpad.net and we can see how best we can get you "set up" + + 16:54 `` \#topic Office Hours (next ~30 mins) + + 16:55 `` this time of the meeting is really just an open door for any discussions, concerns, bugs, questions or general prodding of upstream devs to make sure existing development work is unblocked where possible. + + 16:55 `` in absence of discussions. We actually will be focused on SRU verification tasks today. + + 16:56 `` each of these verification logs and scripts are pushed as pull requests to [https://github.com/cloud-init/ubuntu-sru/pulls](https://github.com/cloud-init/ubuntu-sru/pulls) + + 17:13 `` ok I think that about wraps today's session. Next meeting will be in two weeks, but we'll likely see you in channel earlier. + + 17:13 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2020-11-17.md b/content/status-2020-11-17.md new file mode 100644 index 0000000..41a8c83 --- /dev/null +++ b/content/status-2020-11-17.md @@ -0,0 +1,227 @@ +Title: Cloud-init bi-weekly status +Date: 2020-11-17 17:25:00 UTC +Category: status-meeting-minutes +Slug: status-2020-11-17 + +Meeting information +---------------- + * \#cloud-init: cloud-init status meeting && office hours, 17 Nov at 17:25 — 18:35 UTC + * Full logs at [[[http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-11-17-17.25.log.html](http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-11-17-17.25.log.html)]] + + + +Meeting summary +---------------- + + **LINK**: [https://discourse.ubuntu.com/t/cloud-init-statue-11-17-20/19391](https://discourse.ubuntu.com/t/cloud-init-statue-11-17-20/19391) + **LINK**: [https://github.com/canonical/cloud-init/pull/655](https://github.com/canonical/cloud-init/pull/655) i'd love this too get merged, so we don't have to carry the patch on ports + **LINK**: [https://github.com/canonical/cloud-init/pull/655](https://github.com/canonical/cloud-init/pull/655) + **LINK**: [https://github.com/canonical/cloud-init/pull/647](https://github.com/canonical/cloud-init/pull/647) + **LINK**: [https://github.com/canonical/cloud-init/pull/588\#pullrequestreview-529957360](https://github.com/canonical/cloud-init/pull/588\#pullrequestreview-529957360) + **LINK**: [https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/sources/DataSourceAzure.py\#L1325](https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/sources/DataSourceAzure.py\#L1325) + **LINK**: [https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/config/cc_set_passwords.py\#L163](https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/config/cc_set_passwords.py\#L163) + **LINK**: [https://github.com/canonical/cloud-init/pull/663](https://github.com/canonical/cloud-init/pull/663) + **LINK**: [https://github.com/canonical/cloud-init/pull/659](https://github.com/canonical/cloud-init/pull/659) + **LINK**: [https://github.com/canonical/cloud-init/pulls](https://github.com/canonical/cloud-init/pulls)?q=is%3Apr+is%3Aopen+label%3A%22release+20.4%22 + + + +Vote results +---------------- + + + + +Done items +---------------- + + * (none) + + + +People present (lines said) +---------------- + + * blackboxsw (48) + * AnhVoMSFT (15) + * rharper (7) + * meena (6) + * smoser (3) + * meetingology (3) + * Odd_Bloke (1) + + + +Full Log +---------------- + + + 17:25 `` \#startmeeting cloud-init status meeting && office hours + + 17:25 `` Meeting started Tue Nov 17 17:25:00 2020 UTC. The chair is blackboxsw. Information about MeetBot at [http://wiki.ubuntu.com/meetingology.](http://wiki.ubuntu.com/meetingology.) + + 17:25 `` + + 17:25 `` Available commands: action commands idea info link nick + + 17:25 `` community-notice: hi folks just starting up an our cloud-init satus update and office hours community meeting. + + 17:26 `` As of the cloud-init summit, we decided to try to host these primarily async in discourse to allow folks in other timezones to participate as available. + + 17:26 `` I've just finished posting a status update for cloud-init upstream to [https://discourse.ubuntu.com/t/cloud-init-statue-11-17-20/19391](https://discourse.ubuntu.com/t/cloud-init-statue-11-17-20/19391) + + 17:26 `` \#link [https://discourse.ubuntu.com/t/cloud-init-statue-11-17-20/19391](https://discourse.ubuntu.com/t/cloud-init-statue-11-17-20/19391) + + 17:27 `` \#chairs rharper smoser Odd_Bloke + + 17:28 `` o/ + + 17:28 `` Generally I think this status meeting can be used as a platform for communication and discussion with the community. + + 17:29 `` for this week, as brought up by a few folks in the community, is that we are trying to define a "go" date for the next upstream cloud-init release 20.4. + + 17:30 `` The hope is to target this Friday Nov 20th. as a deadline for requesting specific PRs and reviews that are needed to get features or fixes included in this 20.4 release. + + 17:31 `` so, i just responded to falcojr's email + + 17:32 `` The goal of this date, from an Ubuntu standpoint, is also to be able to SRU (stable release update) and publish this functionality back to Xenial, Bionic and Focal before the end of the calendar year + + 17:32 `` [https://github.com/canonical/cloud-init/pull/655](https://github.com/canonical/cloud-init/pull/655) i'd love this too get merged, so we don't have to carry the patch on ports + + 17:33 `` thanks meena there [https://github.com/canonical/cloud-init/pull/655](https://github.com/canonical/cloud-init/pull/655) ahh I'm too late + + 17:34 `` So, for those who happen to be on this channel now, let's add links to the meeting log and I'll make sure they are also reflected on the discourse post and PRs that need review assessment and hopefully landing before upstream release cut. + + 17:34 `` \#link [https://github.com/canonical/cloud-init/pull/655](https://github.com/canonical/cloud-init/pull/655) + + 17:34 `` rharper or smoser are there any concerns with existing PRs that you are aware of that should be destined for this 20.4 release? + + 17:35 `` rharper, i'd also love your historic knowledge on [https://github.com/canonical/cloud-init/pull/588](https://github.com/canonical/cloud-init/pull/588) but that can wait until after the release + + 17:36 `` rharper: I wanted to put a solid review on the cached ds handling today/tomorrow + + 17:36 `` \#link [https://github.com/canonical/cloud-init/pull/647](https://github.com/canonical/cloud-init/pull/647) + + 17:36 `` I've looked it over a couple times, but wanted to but some investment in the review myself today. + + 17:37 `` AnhVoMSFT: welcome and thanks for peeking in to checkup. If your team also have any hopes for PRs you can pitch us here, discourse or email. + + 17:38 `` I have a quick question on the cc_set_passwords. I'm still looking through the code but if anyone knows this one well and can point me to the right place to look it would be appreciated + + 17:39 `` it seems like if we create an image that previously was deployed with password ABC, but during image preparation we don't delete that user, then when we deploy a VM with that image and specifying a new password DEF, it isn't applied. I.e., the user will still have password ABC + + 17:39 `` blackboxsw: I'm not aware of anything critical PR wise; maybe the networking_cls bits; but not sure if that's ready; + + 17:40 `` from my understanding, that needs to get in + + 17:40 `` AnhVoMSFT: poking around now on that + + 17:41 `` meena: yes; that makes sense; just hadn't looked at the current state of the PR since I last commented; + + 17:42 `` meena: re: 588 (genreate_fallback_config); did you have a specific question you wanted some background on? + + 17:43 `` rharper, search for your name + + 17:44 `` hidden under a "Load more Items" + + 17:44 `` I'll respond + + 17:44 `` so instance-id should have changed on the newly deployed vm, so cc_set_passwords should get retriggered due to [https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_set_passwords.py\#L49](https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_set_passwords.py\#L49) (the default frequency for cc modules). AnhVoMSFT: what the userdata password field you are using? top-level password or chpasswd? + + 17:45 `` this is the user password passed in from ovf + + 17:45 `` as that'd be different code paths I think + + 17:45 `` [https://github.com/canonical/cloud-init/pull/588\#pullrequestreview-529957360](https://github.com/canonical/cloud-init/pull/588\#pullrequestreview-529957360) + + 17:46 `` in a newly created instance without the existing user, I could see the password getting created during the initial useradd call when the user is created + + 17:47 `` however, if the user existed, that code path isn't invoked. There's some code in cc_set_passwords to change the password for existing user, but I'm unsure when it's invoked (or why it's not invoked in the case of azure) + + 17:48 `` AnhVoMSFT: could you provide a paste of redacted userdata from that instance via `sudo cloud-init query userdata`... redacting the specific passwords ? + + 17:49 `` yeah I would have expected a log.debug("Changing password for %s:", users) log + + 17:53 `` let me run the query + + 17:53 `` there's nothing returned (since there's no userdata) + + 17:54 `` looks like the ds Azure is adding the user/password information retrieved from OVF to cfg['defuser'] + + 18:00 `` [https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/sources/DataSourceAzure.py\#L1325](https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/sources/DataSourceAzure.py\#L1325) + + 18:00 `` if I'm reading the code of cc_set_password correctly we will need to add cfg['password'] as well if we want the defuser's password to be changed? + + 18:01 `` rharper: We are treating the networking_cls PR as critical, and AFA(I/we)K it's pretty much ready to land. + + 18:02 `` Odd_Bloke: ok, makes sense + + 18:06 `` blackboxsw: i dont have anything critical. + + 18:06 `` AnhVoMSFT: so normalize_users_groups is what pulls the default_user configuration out of /etc/cloud/cloud.cfg(.d/*) + + 18:06 `` [https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/config/cc_set_passwords.py\#L163](https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/config/cc_set_passwords.py\#L163) + + 18:07 `` that ug_util.extract_default is what should be seeing the passwords set/changed + + 18:07 `` + + 18:08 `` \#669 looks reasonable. + + 18:08 `` yet interestingly. password referenced there is only set from the top-level "password" value [https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/config/cc_set_passwords.py\#L143](https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/config/cc_set_passwords.py\#L143) + + 18:08 `` thanks smoser for that + + 18:08 `` \#link [https://github.com/canonical/cloud-init/pull/663](https://github.com/canonical/cloud-init/pull/663) + + 18:12 `` let me test it out real quick by setting the cfg['password'] key in the ds azure + + 18:12 `` AnhVoMSFT: so, I may be mistaken but if a password key is set on the default_user in system_info (which is what it looks like azure does), then that default password is only used if there is no top-level "password" key provided in merged cloud-config, then and the default_user specific password key is ignored + + 18:12 `` +1 AnhVoMSFT + + 18:13 `` yep that worked + + 18:13 `` it's a one liner change, I'll submit a PR asap + + 18:14 `` AnhVoMSFT: good. ok, I wonder if this ever worked (having the password key hung under default_user scope?) + + 18:14 `` as in, I wonder if there was a regression introduced with some of the is_FreeBSD restructuring + + 18:15 `` I don't think so. customer reported this issue in cloud-init 18.5 and I repro-ed it in master + + 18:15 `` ok, ok. good thanks for that context + + 18:15 `` and checking the recent BSD change it looking completely unrelated + + 18:17 `` ok AnhVoMSFT when the PR is submitted. let's get that queued for this upstream 20.4 if we can + + 18:18 `` do folks have an opinion on whether it helps to add a custom label to active PRs that we intend to land before upstream release like 'upstream-blocker' or 'upstream-release'? + + 18:19 `` just for more public tracking/transparency. not sure if that's helpful or just needless process? + + 18:19 `` do folks have an opinion on whether it helps to add a custom label to active PRs that we intend to land before upstream release like 'upstream-blocker' or 'upstream-release'? + + 18:23 `` I think that would be helpful, yes + + 18:25 `` ok, let's try it out. let's try specific 'release 20.4' and see how that feels to folks. easy enough to drop if it doesn't improve communication + + 18:30 `` also added pickling upgrade test validation PR + + 18:30 `` \#link [https://github.com/canonical/cloud-init/pull/659](https://github.com/canonical/cloud-init/pull/659) + + 18:31 `` ok, last call for cloud-init status / office hours. Any other takers for discussion at the moment? If not I'll close out the meeting in a few mins and publish minutes. + + 18:33 `` my plan is still to publish to cloud-init.github.io status meetings and link it from the primary post at [https://discourse.ubuntu.com/t/cloud-init-status-11-17-20/19391](https://discourse.ubuntu.com/t/cloud-init-status-11-17-20/19391) + + 18:34 `` the following will list prs we hope to work toward landing this week + + 18:34 `` \#link [https://github.com/canonical/cloud-init/pulls](https://github.com/canonical/cloud-init/pulls)?q=is%3Apr+is%3Aopen+label%3A%22release+20.4%22 + + 18:35 `` thanks again for the discussion and suggestions folks. Have a good one! + + 18:35 `` \#endmeeting + + + +Generated by MeetBot 0.1.5 ([http://wiki.ubuntu.com/meetingology](http://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2021-02-23.md b/content/status-2021-02-23.md new file mode 100644 index 0000000..a9e131f --- /dev/null +++ b/content/status-2021-02-23.md @@ -0,0 +1,78 @@ +Title: Cloud-init bi-weekly status +Date: 2021-02-23 17:18:00 UTC +Category: status-meeting-minutes +Slug: status-2021-02-23 + +Meeting information +---------------- + + * \#cloud-init: cloud-init office hours meeting, started by blackboxsw, 23 Feb at 17:18 — 18:00 UTC. + * Full logs at [https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-02-23-17.18.log.html](https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-02-23-17.18.log.html) + + + +Meeting summary +---------------- + + * **LINK**: [https://discourse.ubuntu.com/c/server/cloud-init](https://discourse.ubuntu.com/c/server/cloud-init) (blackboxsw, 17:30) + + + +People present (lines said) +---------------- + + * blackboxsw (17) + * meetingology (2) + * Odd_Bloke (2) + + + +Full log +---------------- + + + 17:18 `` \#startmeeting cloud-init office hours + + 17:18 `` Meeting started at 17:18:36 UTC. The chair is blackboxsw. Information about MeetBot at [https://wiki.ubuntu.com/meetingology](https://wiki.ubuntu.com/meetingology) + + 17:18 `` Available commands: action, commands, idea, info, link, nick + + 17:18 `` o/ + + 17:19 `` community notice: hi folks. We are resuming our much anticipated office hours. Every two weeks at this time. The IRC topic will host our upcoming expected office-hours meeting time. + + 17:19 `` \o Odd_Bloke thx + + 17:19 `` t + + 17:20 `` This meeting will provide an opportunity with multiple upstream cloud-init devs available to discuss bugs, features, ongoing development or answer your existential questions :) + + 17:20 `` We hope to continue this meeting with regular cadence (and calendar reminders) to make sure we hold this time and frequency. + + 17:22 `` I'll send an email to the mailing list (again) announcing this cadence. Again this time if for any discussions, questions or dev/feature topics that folks would like to gab about. + + 17:23 `` We just published a high-level update of what's been happening in the cloud-init space, [https://discourse.ubuntu.com/t/cloud-init-status-02-23-2021/21069.](https://discourse.ubuntu.com/t/cloud-init-status-02-23-2021/21069.) + + 17:25 `` As seen on the mailinglist, Odd_Bloke and falcojr have been trying to tidy up things for the upstream 21.1 timed release. Thanks both of you for driving this work. I believe 21.1 landed, was uploaded to Ubuntu 21.04 (Hirsute). + + 17:26 `` We are also planning on SRUing(StableReleaseUpdate - Ubuntu-speak for uploading) 21.1 plus a feature fix for OVS support into Xenial, Bionic, Focal and Groovy within the next week or two. + + 17:26 `` Yep, I'm currently working through the release announcement process. + + 17:30 `` great Dan. So, TLDR is watch the mailinglist cloud-init@lists.launchpad.net and discourse [https://discourse.ubuntu.com/c/server/cloud-init](https://discourse.ubuntu.com/c/server/cloud-init) for announcements and updates + + 17:30 `` \#link [https://discourse.ubuntu.com/c/server/cloud-init](https://discourse.ubuntu.com/c/server/cloud-init) + + 17:58 `` I think we've about rounded out the office-hours. (I spent that time walking through a sopel-irc bot setup to test out some of the features to see if we can't add some structure to this office-hours engagement (and frankly release announcements too ) + + 17:59 `` Let's set that next office hours for +2 weeks-45 mins from now + + 18:00 `` hopefully by then we have an automated announcer kicking off the notification. + + 18:00 `` Thanks all! + + 18:00 `` \#endmeeting + + + +Generated by MeetBot 0.4.0 ([https://wiki.ubuntu.com/meetingology](https://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2021-03-09.md b/content/status-2021-03-09.md new file mode 100644 index 0000000..678dea4 --- /dev/null +++ b/content/status-2021-03-09.md @@ -0,0 +1,108 @@ +Title: Cloud-init bi-weekly status +Date: 2021-03-09 17:19:00 UTC +Category: status-meeting-minutes +Slug: status-2021-03-09 + +Meeting information +---------------- + + * \#cloud-init: cloud-init bi-weekly office-hours meeting, started by blackboxsw, 09 Mar at 17:19 — 18:38 UTC. + * Full logs at [https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-03-09-17.19.log.html](https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-03-09-17.19.log.html) + + + +Meeting summary +---------------- + + * **LINK**: [https://discourse.ubuntu.com/t/cloud-init-status-03-09-2021/21309](https://discourse.ubuntu.com/t/cloud-init-status-03-09-2021/21309) (blackboxsw, 17:23) + + + +People present (lines said) +---------------- + + * blackboxsw (14) + * falcojr (8) + * beantaxi (7) + * meetingology (3) + * Odd_Bloke (3) + + + +Full log +---------------- + + + 17:19 `` \#startmeeting cloud-init bi-weekly office-hours + + 17:19 `` Meeting started at 17:19:08 UTC. The chair is blackboxsw. Information about MeetBot at [https://wiki.ubuntu.com/meetingology](https://wiki.ubuntu.com/meetingology) + + 17:19 `` Available commands: action, commands, idea, info, link, nick + + 17:19 `` \#char Odd_Bloke falcojr + + 17:19 `` \#chair Odd_Bloke falcojr + + 17:19 `` Current chairs: Odd_Bloke, blackboxsw, falcojr + + 17:20 `` hi cloud-init, sorry for the confusion on the UTC time that I posted in the topic. I had incorrectly set 15:15 UTC instead of 17:15. + + 17:20 `` welcome to the bi-weekly cloud-init office hours + + 17:21 `` This cloud-init status meeting has moved to a more asynchronous posting of high-level happenings in cloud-init to discourse to support timezone differences for all cloud-init developers. + + 17:23 `` We plan on continuing to host these office hours to provide a means for quick communication, questions and discussions with a couple of upstream developers present to help facilite any questions or discussions of interest to folks. + + 17:23 `` For reference, here are the high-level "happenings" in cloud-init upstream over the last two weeks. + + 17:23 `` o/ + + 17:23 `` \#link [https://discourse.ubuntu.com/t/cloud-init-status-03-09-2021/21309](https://discourse.ubuntu.com/t/cloud-init-status-03-09-2021/21309) + + 17:26 `` As of last office-hours I belive upstream had just cut the first 21.1 release in the tip of cloud-init. Canonical will be starting the SRU process this week I believe to publish the 21.1 release (plus a couple of extra fixes which just landed in tip) into Ubuntu Xenial, Bionic, Focal, Groovy and Hirsute. + + 17:41 `` Odd_Bloke: I tried your command and it was helpful. It complained about a missing ssh key, so I shrugged, tried ssh-keygen -t rsa and reran the test, and it passed. I've kicked off a run of all the tests, which I assume will take a bit. + + 17:55 `` beantaxi: Great, thanks for the update! A full run in LXD containers takes ~12mins locally (though I'm probably running on beefier hardware than you're paying EC2 for so YMMV :p). + + 17:55 `` beantaxi: Once you had the output, was it clear that the missing SSH key was the issue? + + 17:55 `` setting the appropriate time for next office hours + + 17:56 `` setting the appropriate time for next office hours Mar 23 17:15 UTC + + 17:57 `` ERROR tests/integration_tests/modules/test_runcmd.py::TestRuncmd::test_runcmd - FileNotFoundError: [Errno 2] No such file or directory: '/home/ubuntu/.ssh/id_rsa.pub' + + 17:57 `` That was the error message + + 17:59 `` tests require an ssh keypair. It'll use your user one by default or you can specify one manually in the integration settings config + + 17:59 `` do an `ssh-keygen` + + 17:59 `` The full test failed with 7 failures: [https://paste.ubuntu.com/p/hcYN7ZDvbs/](https://paste.ubuntu.com/p/hcYN7ZDvbs/) + + 18:00 `` falcojr: Thanks ... I was just showing Odd_Bloke the error message I got before running ssh-keygen, which did indeed solve most of my issues + + 18:01 `` falcojr: Also, this is just me running the existing integration tests on an EC2 instance. Without any of my changes + + 18:01 `` not sure the cause of that first one, but the rest are for code not in ubuntu images yet + + 18:03 `` the version of cloud_init to use is specified by the CLOUD_INIT_SOURCE variable (integration_settings.py...copy this to user_settings.py to easily override defaults) + + 18:03 `` it defaults to NONE which means use whatever image has been released on this platform + + 18:04 `` to test non-released code, changing it to IN_PLACE (only works on LXD) should work + + 18:08 `` you can also set it to ppa:cloud-init-dev/daily , but that won't contain any changes that you're trying to test + + 18:18 `` falcojr: Copying integration_settings.py to user_settings.py and setting CLOUD_INIT_SOURCE=IN_PLACE made all the test_keys_to_console errors clean. There's still that simple_streams error. Do I just need to add a PPA for simplestreams? It looks like requires a file in /etc/apt/sources.list.d, but mine is empty + + 18:23 `` Not sure off the top of my head. Did you pip install the integration_requirements.txt? + + 18:38 * blackboxsw thinks I should about wrap up office hours. Thanks falcojr Odd_Bloke and beantaxi for the discussion there + + 18:38 `` \#endmeeting + + + +Generated by MeetBot 0.4.0 ([https://wiki.ubuntu.com/meetingology](https://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2021-03-23.md b/content/status-2021-03-23.md new file mode 100644 index 0000000..e5edc08 --- /dev/null +++ b/content/status-2021-03-23.md @@ -0,0 +1,90 @@ +Title: Cloud-init bi-weekly status +Date: 2021-03-23 17:22:00 UTC +Category: status-meeting-minutes +Slug: status-2021-03-23 + +Meeting information +---------------- + + * \#cloud-init: cloud-init bi-weekly office-hours meeting, started by Odd_Bloke, 23 Mar at 17:22 — 18:24 UTC. + * Full logs at [https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-03-23-17.22.log.html](https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-03-23-17.22.log.html) + + + +Meeting summary +---------------- + + * **LINK**: [https://discourse.ubuntu.com/t/cloud-init-status-03-23-2021/21490](https://discourse.ubuntu.com/t/cloud-init-status-03-23-2021/21490) (Odd_Bloke, 17:23) + * **LINK**: [https://discourse.ubuntu.com/t/cloud-init-status-03-23-2021/21490](https://discourse.ubuntu.com/t/cloud-init-status-03-23-2021/21490) (blackboxsw, 17:23) + * **LINK**: [https://bugs.launchpad.net/cloud-init/+bug/1724414](https://bugs.launchpad.net/cloud-init/+bug/1724414) (blackboxsw, 17:25) + + + +People present (lines said) +---------------- + + * blackboxsw (11) + * Odd_Bloke (10) + * meetingology (3) + * ubot5 (1) + * falcojr (0) + + + +Full log +---------------- + + + 17:22 `` \#startmeeting cloud-init bi-weekly office-hours + + 17:22 `` Meeting started at 17:22:08 UTC. The chair is Odd_Bloke. Information about MeetBot at [https://wiki.ubuntu.com/meetingology](https://wiki.ubuntu.com/meetingology) + + 17:22 `` Available commands: action, commands, idea, info, link, nick + + 17:22 `` \#chair blackboxsw falcojr + + 17:22 `` Current chairs: Odd_Bloke, blackboxsw, falcojr + + 17:22 `` \0 woot thanks Odd_Bloke + + 17:23 `` Hey folks, the cloud-init committers will be around for the next while, to answer any questions or have any discussions you're interested in having. + + 17:23 `` blackboxsw posted a status update to Discourse earlier today. + + 17:23 `` Here's the discourse post for reference on recent cloud-init events + + 17:23 `` \#link [https://discourse.ubuntu.com/t/cloud-init-status-03-23-2021/21490](https://discourse.ubuntu.com/t/cloud-init-status-03-23-2021/21490) + + 17:23 `` \#link [https://discourse.ubuntu.com/t/cloud-init-status-03-23-2021/21490](https://discourse.ubuntu.com/t/cloud-init-status-03-23-2021/21490) + + 17:23 `` thanks Odd_Bloke + + 17:23 `` Haha + + 17:23 `` Please read it twice. + + 17:24 `` and correct any clerical errors + + 17:25 `` one topic of interested that hamalq brought up yesterday was the "feature" of RedHat and CentOS that automatically prefers fqdn over hostname in \#cloud-config per this bug + + 17:25 `` \#link [https://bugs.launchpad.net/cloud-init/+bug/1724414](https://bugs.launchpad.net/cloud-init/+bug/1724414) + + 17:25 `` Ubuntu bug 1724414 in cloud-init "rhel distro selects FQDN as hostname" [Low,Won't fix] + + 17:26 `` I mentioned we'd bring it up to reflect our opinion on this behavior today after a discussion + + 17:28 `` I think the upstream stance on RedHat and CentOS is that this default behavior on RedHat/CentOS has been in play for a long time and changing that default behavior would be asking to cause problems for the majority of users who may rely on this behavior during system launch. + + 17:28 `` Odd_Bloke: falcojr did we say in this case we'd prefer a new bug which better describes the desired use-case and how current cloud-init doesn't allow for that use-case? + + 17:30 `` that's all the content/discussion I had. I know I needed to get otubo a review today on his resize lvm partition branch [https://github.com/canonical/cloud-init/pull/721](https://github.com/canonical/cloud-init/pull/721) as my stale review was blocking that. + + 17:31 `` We've closed out that bug as Won't Fix; we'd like folks who consider themselves affected by that bug to file a new one which describes their specific problem with the current situation: we can then work to support those requirements. + + 18:24 `` OK, sounds like there's not much to chat about; thanks to any lurkers. :) + + 18:24 `` \#endmeeting + + + +Generated by MeetBot 0.4.0 ([https://wiki.ubuntu.com/meetingology](https://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2021-04-06.md b/content/status-2021-04-06.md new file mode 100644 index 0000000..fb9cd92 --- /dev/null +++ b/content/status-2021-04-06.md @@ -0,0 +1,75 @@ +Title: Cloud-init bi-weekly status +Date: 2021-04-06 16:20:00 UTC +Category: status-meeting-minutes +Slug: status-2021-04-06 + +Meeting information +---------------- + + * \#cloud-init: cloud-init bi-weekly office-hours meeting, started by blackboxsw, 06 Apr at 16:20 — 17:37 UTC. + * Full logs at [https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-04-06-16.20.log.html](https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-04-06-16.20.log.html) + + + +Meeting summary +---------------- + + + + +People present (lines said) +---------------- + + * hamalq (7) + * blackboxsw (6) + * falcojr (3) + * meetingology (2) + * Odd_Bloke (1) + + + +Full log +---------------- + + + 16:20 `` \#startmeeting cloud-init bi-weekly office-hours + + 16:20 `` Meeting started at 16:20:26 UTC. The chair is blackboxsw. Information about MeetBot at [https://wiki.ubuntu.com/meetingology](https://wiki.ubuntu.com/meetingology) + + 16:20 `` Available commands: action, commands, idea, info, link, nick + + 16:21 `` I think by default it should use the current defaults of what's chosen...e.g., true for rhel and false for others + + 16:22 `` Hi cloud-init! This marks another episode of cloud-init community office hours. This time is an opportunity to discuss any cloud-init questions, bugs or topics with cloud-init upstream developers. We try to ensure a couple of devs have eyes on this channel to field any questions/concerns folks may have. + + 16:24 `` o/ + + 16:25 `` Recent happenings in cloud-init space are generally spent on the current SRU validation with Odd_Bloke and falcojr. It looks like we've cleared the last manual validation with that SRU and we will be waiting on a significant automated set of tests to pass before making this release public. [https://discourse.ubuntu.com/t/cloud-init-status-04-06-2021/21691](https://discourse.ubuntu.com/t/cloud-init-status-04-06-2021/21691) + + 16:32 `` thanks falcojr and Odd_Bloke for reviews on [https://github.com/canonical/cloud-init/pull/859](https://github.com/canonical/cloud-init/pull/859) + + 16:36 `` i already did the change as the comment + + 16:37 `` i dont think i can change cloudinit/distros/__init__.py select_hostname though + + 16:38 `` we can change it...we just need to make sure the functionality stays the same if the option isn't specified + + 16:39 `` thats the point since the default for that option is true + + 16:40 `` unless we make the default for it false for other distros + + 16:41 `` yes, we would need to take it into account for all distros, and it would default to false for most + + 16:42 `` +1 + + 16:47 `` i changed that now for distros and rhel + + 17:15 `` i think i got the changes required [https://github.com/canonical/cloud-init/pull/859](https://github.com/canonical/cloud-init/pull/859) + + 17:36 `` thanks folks for attending the office hours. See you all in two weeks. Same time + + 17:37 `` \#endmeeting + + + +Generated by MeetBot 0.4.0 ([https://wiki.ubuntu.com/meetingology](https://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2021-05-18.md b/content/status-2021-05-18.md new file mode 100644 index 0000000..4eaaeec --- /dev/null +++ b/content/status-2021-05-18.md @@ -0,0 +1,86 @@ +Title: Cloud-init bi-weekly status +Date: 2021-05-18 16:32:00 UTC +Category: status-meeting-minutes +Slug: status-2021-05-18 + +Meeting information +---------------- + + * \#cloud-init: cloud-init bi-weekly office-hours meeting, started by blackboxsw, 18 May at 16:32 — 17:26 UTC. + * Full logs at [https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-05-18-16.32.log.html](https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-05-18-16.32.log.html) + + + +Meeting summary +---------------- + + + + +People present (lines said) +---------------- + + * blackboxsw (12) + * paride (4) + * smoser (4) + * meetingology (2) + * ubot5 (1) + * falcojr (1) + + + +Full log +---------------- + + + 16:32 `` \#startmeeting cloud-init bi-weekly office-hours + + 16:32 `` Meeting started at 16:32:21 UTC. The chair is blackboxsw. Information about MeetBot at [https://wiki.ubuntu.com/meetingology](https://wiki.ubuntu.com/meetingology) + + 16:32 `` Available commands: action, commands, idea, info, link, nick + + 16:32 `` smoser, thanks, merged! + + 16:33 `` but as it's not in the server packageset I'll need sponsorship for the upload... + + 16:33 `` community-notice: Let's get back to a more regularly scheduled cloud-init office hours. Every two weeks, feel free to watch the channel topic for the next scheduled time. We'll ensure to have a couple of sets of eyes on this IRC channel. + + 16:35 `` Next office-hours meeting is set for June 1, 17:15 UTC. It is worth us having this recurring meeting to give anyone a chance to drive-by \#cloud-init if they have questions, discussions, bugs or PRs that need attention. + + 16:36 `` Prior to the office hours, we will continue to generate a post with the latest commits to land in cloud-init:master as well as any notable features in progress [https://discourse.ubuntu.com/t/cloud-init-status-05-18-2021/22349](https://discourse.ubuntu.com/t/cloud-init-status-05-18-2021/22349) + + 16:41 `` From upstream standpoint, we were able to cut the time-based release 21.2 on May 6th. And for Ubuntu, we have queued the StableReleaseUpdate (SRU) for 21.2 into Bionic, Focal and Hirsute for which falcojr and Odd_Bloke have been going through verification. + + 16:41 `` Think we need to update the topic for the 21.2 upstream release too. + + 16:42 `` paride: [https://paste.ubuntu.com/p/y3N7wjCG3n/](https://paste.ubuntu.com/p/y3N7wjCG3n/) + + 16:44 `` fudge. + + 16:44 `` but i just noticed your changelog didn't have LP: \#1908452 + + 16:44 `` Launchpad bug 1908452 in MAAS "MAAS stops working and deployment fails after `Loading ephemeral` step" [High,In progress] [https://launchpad.net/bugs/1908452](https://launchpad.net/bugs/1908452) + + 16:45 `` because the commit message said 'Fixes LP:1908452' rather than just 'LP: \#1908452' + + 16:46 `` 'Fixes LP:1908452' almost github; almost LP :/ + + 16:48 `` smoser, argh :/ will update the bug status manually + + 16:48 `` thanks for the upload + + 16:50 * blackboxsw falcojr: do we have a trello board for the SRU 21.2 created? + + 16:50 `` yep, [https://trello.com/b/tBP3Jrwp/sru-cloud-init-212](https://trello.com/b/tBP3Jrwp/sru-cloud-init-212) (just made it public) + + 16:51 `` Thanks a lot + + 16:55 `` Great, I was originally looking at the older trello board for the 21.1. Ok, so I'll grab Softlayer testing as you mentioned at standup today. If you want me to run through other clouds just let me know or hit me up for reviews. + + 17:26 `` Alright, I think that about wraps today's office hours. Next round in two weeks. Thanks for tuning in. + + 17:26 `` \#endmeeting + + + +Generated by MeetBot 0.4.0 ([https://wiki.ubuntu.com/meetingology](https://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2021-06-01.md b/content/status-2021-06-01.md new file mode 100644 index 0000000..5cd9d90 --- /dev/null +++ b/content/status-2021-06-01.md @@ -0,0 +1,57 @@ +Title: Cloud-init bi-weekly status +Date: 2021-06-01 17:25:00 UTC +Category: status-meeting-minutes +Slug: status-2021-06-01 + +Meeting information +---------------- + + * \#cloud-init: cloud-init bi-weekly office hours (~30 mins) meeting, started by blackboxsw, 01 Jun at 17:25 — 19:29 UTC. + * Full logs at [https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-06-01-17.25.log.html](https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-06-01-17.25.log.html) + + + +Meeting summary +---------------- + + * **LINK**: [https://discourse.ubuntu.com/t/cloud-init-status-06-01-2021/22553](https://discourse.ubuntu.com/t/cloud-init-status-06-01-2021/22553) (blackboxsw, 17:29) + + + +People present (lines said) +---------------- + + * blackboxsw (9) + * meetingology (2) + + + +Full log +---------------- + + + 17:25 `` \#startmeeting cloud-init bi-weekly office hours (~30 mins) + + 17:25 `` Meeting started at 17:25:49 UTC. The chair is blackboxsw. Information about MeetBot at [https://wiki.ubuntu.com/meetingology](https://wiki.ubuntu.com/meetingology) + + 17:25 `` Available commands: action, commands, idea, info, link, nick + + 17:28 `` community-notice: office hours meeting starts now. We host this meeting time every two weeks for any drop in discussions for anything cloud-init related. Bring your bugs, feature discussions, gripes and questions and we'll have a couple sets of upstream cloud-init eyes on this channel to field those discussions. + + 17:29 `` highlights of recent upstream commits and project changes are at the url below: + + 17:29 `` \#link [https://discourse.ubuntu.com/t/cloud-init-status-06-01-2021/22553](https://discourse.ubuntu.com/t/cloud-init-status-06-01-2021/22553) + + 17:32 `` Of course, if you managed to join us over here you are already aware of the Freenode IRC politcal climate pushing us to migrate to a more open/friendly IRC network w/ libera.chat. paride is in the process of registering this channel for the cloud-init project so that we can add channel OPS to the upstream cloud-init committers smoser, rharper, Odd_Bloke, falcojr. + + 17:32 `` Once we have channel op status, we plan on adding upcoming dates, milestones and info to the IRC channel title. + + 17:37 `` Also, as upstream, we want to rename the default development branch from 'master' to 'main' to provide more inclusive naming and drop antiquated and exclusive naming conventions. An email will be sent to the cloud-init mailing list explaining the perceived impact of such a default branch rename (which should be minimal). + + 17:37 `` If there are any concerns about this rename impacting business, please raise concerns here, on the discourse post above or on the mailinglist + + 19:29 `` \#endmeeting + + + +Generated by MeetBot 0.4.0 ([https://wiki.ubuntu.com/meetingology](https://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2021-06-15.md b/content/status-2021-06-15.md new file mode 100644 index 0000000..c2bb47c --- /dev/null +++ b/content/status-2021-06-15.md @@ -0,0 +1,79 @@ +Title: Cloud-init bi-weekly status +Date: 2021-06-15 17:17:00 UTC +Category: status-meeting-minutes +Slug: status-2021-06-15 + +Meeting information +---------------- + + * \#cloud-init: cloud-init bi-weekly office-hours meeting, started by blackboxsw, 15 Jun at 17:17 — 19:47 UTC. + * Full logs at [https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-06-15-17.17.log.html](https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-06-15-17.17.log.html) + + + +Meeting summary +---------------- + + * **LINK**: [https://discourse.ubuntu.com/t/cloud-init-status-06-15-2021/22730](https://discourse.ubuntu.com/t/cloud-init-status-06-15-2021/22730) (blackboxsw, 17:25) + * **LINK**: [https://docs.github.com/en/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch\#updating-a-local-clone-after-a-branch-name-changes](https://docs.github.com/en/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch\#updating-a-local-clone-after-a-branch-name-changes) (blackboxsw, 17:37) + + + +People present (lines said) +---------------- + + * blackboxsw (16) + * meetingology (3) + * falcojr (2) + + + +Full log +---------------- + + + 17:17 `` \#startmeeting cloud-init bi-weekly office-hours + + 17:17 `` Meeting started at 17:17:44 UTC. The chair is blackboxsw. Information about MeetBot at [https://wiki.ubuntu.com/meetingology](https://wiki.ubuntu.com/meetingology) + + 17:17 `` Available commands: action, commands, idea, info, link, nick + + 17:20 `` community-notice: Hi cloud-initers, welcome to another office hours meeting. cloud-init committers will be around for the next hour to field any discussions. answer questions or put some eyes on PR reviews or bugs that spark your interest. + + 17:21 `` We host this meeting to unblock, or unstick anybody toying around with cloud-init, as well as to update thecloud-init devs on recent changes in cloud-init upstream + + 17:21 `` \#chair falcojr + + 17:21 `` Current chairs: blackboxsw, falcojr + + 17:25 `` We just published a little discourse post describing that cloud-init upstream version 21.2 has now cleared SRU validation for Ubuntu Bionic(16.04) Focal (20.04) Groovy (20.10) and Hirsute (21.04) [https://discourse.ubuntu.com/t/cloud-init-status-06-15-2021/22730](https://discourse.ubuntu.com/t/cloud-init-status-06-15-2021/22730) + + 17:25 `` \#link [https://discourse.ubuntu.com/t/cloud-init-status-06-15-2021/22730](https://discourse.ubuntu.com/t/cloud-init-status-06-15-2021/22730) + + 17:26 `` in that SRU, were some ssh_key handling improvement, Azure SSH key processing, Azure userdata updated ingested from IMDS and new support for Vultr cloud platform. + + 17:27 `` Thanks all for those contributions! + + 17:30 `` one other interesting thing to note: 4 days ago I was banned from FreeNode. falcojr did this happen to you too? "Connection closed unexpectedly: You are banned from this server- [\#1480] Contact support@freenode.net (2021/6/11 05.18):" + + 17:31 `` blackboxsw: no, that's weird. I know they completely reset everything over there though. + + 17:32 `` hrm maybe they tracked irc nicks that were advertizing moving to Libera.chat is the only thing I can think. will check it out + + 17:33 `` at this point probably just best to cut ties completely + + 17:35 `` yes agreed + + 17:37 `` community-notice: reminder rename upstream/master ->` upstream/main in 2 days. All active PRs will automatically be retargetted. For your local clones for cloud-init it should mean only the following: + + 17:37 `` \#link [https://docs.github.com/en/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch\#updating-a-local-clone-after-a-branch-name-changes](https://docs.github.com/en/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch\#updating-a-local-clone-after-a-branch-name-changes) + + 17:40 `` an email will be sent out to cloud-init@lists.launchpad.net + + 17:40 `` with detailed instructions. + + 19:47 `` \#endmeeting + + + +Generated by MeetBot 0.4.0 ([https://wiki.ubuntu.com/meetingology](https://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/content/status-2021-06-29.md b/content/status-2021-06-29.md new file mode 100644 index 0000000..fb31955 --- /dev/null +++ b/content/status-2021-06-29.md @@ -0,0 +1,60 @@ +Title: Cloud-init bi-weekly status +Date: 2021-06-29 16:23:00 UTC +Category: status-meeting-minutes +Slug: status-2021-06-29 + +Meeting information +---------------- + + * \#cloud-init: cloud-init bi-weekly office-hours meeting, started by blackboxsw, 29 Jun at 16:23 — 17:35 UTC. + * Full logs at [https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-06-29-16.23.log.html](https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-06-29-16.23.log.html) + + + +Meeting summary +---------------- + + * **LINK**: [https://discourse.ubuntu.com/t/cloud-init-status-06-29-2021/22981](https://discourse.ubuntu.com/t/cloud-init-status-06-29-2021/22981) (blackboxsw, 16:27) + + + +People present (lines said) +---------------- + + * blackboxsw (9) + * meetingology (2) + * ubottu (1) + + + +Full log +---------------- + + + 16:23 `` \#startmeeting cloud-init bi-weekly office-hours + + 16:23 `` Meeting started at 16:23:41 UTC. The chair is blackboxsw. Information about MeetBot at [https://wiki.ubuntu.com/meetingology](https://wiki.ubuntu.com/meetingology) + + 16:23 `` Available commands: action, commands, idea, info, link, nick + + 16:25 `` Hi cloud-init devs, Our biweekly office hours meeting has begun. We keep this channel open during the designated time on the channel \#topic for drop in questions, feature or bug discussions and prodding committers folks for reviews. + + 16:27 `` All questions welcome and we'll have a couple of upstream committers with eyes on the channel to field any discussions brought up as best we can. + + 16:27 `` Just prior to this meeting, someone will post recent happenings in cloud-init upstream which may be of value to the community. + + 16:27 `` \#link [https://discourse.ubuntu.com/t/cloud-init-status-06-29-2021/22981](https://discourse.ubuntu.com/t/cloud-init-status-06-29-2021/22981) + + 16:29 `` As far as upstream is concerned, the only schedule detail of note is we are looking to create an official 21.3 upstream release August 28th. Before that time we hope to have some hot plug network device handling functional in cloud-init. + + 16:34 `` my plan today is to get falcojr a review on his foundational hotplug support work at [https://github.com/canonical/cloud-init/pull/919](https://github.com/canonical/cloud-init/pull/919) which should allow cloud-init to support actively interacting with network config utilities to actively enable individual interfaces on device discovery after the network renderers have finished initial network bringup. + + 16:34 `` Pull 919 in canonical/cloud-init "Add new network configurers to bring up interfaces (SC-85)" [Open] + + 17:35 `` ok, that wraps things up for "office hours" for today. Thanks for checking in. + + 17:35 `` \#endmeeting + + + +Generated by MeetBot 0.4.0 ([https://wiki.ubuntu.com/meetingology](https://wiki.ubuntu.com/meetingology)) \ No newline at end of file diff --git a/develop_server.sh b/develop_server.sh new file mode 100755 index 0000000..2661df3 --- /dev/null +++ b/develop_server.sh @@ -0,0 +1,103 @@ +#!/usr/bin/env bash +## +# This section should match your Makefile +## +PY=${PY:-python} +PELICAN=${PELICAN:-pelican} +PELICANOPTS= + +BASEDIR=$(pwd) +INPUTDIR=$BASEDIR/content +OUTPUTDIR=$BASEDIR/output +CONFFILE=$BASEDIR/pelicanconf.py + +### +# Don't change stuff below here unless you are sure +### + +SRV_PID=$BASEDIR/srv.pid +PELICAN_PID=$BASEDIR/pelican.pid + +function usage(){ + echo "usage: $0 (stop) (start) (restart) [port]" + echo "This starts Pelican in debug and reload mode and then launches" + echo "an HTTP server to help site development. It doesn't read" + echo "your Pelican settings, so if you edit any paths in your Makefile" + echo "you will need to edit your settings as well." + exit 3 +} + +function alive() { + kill -0 $1 >/dev/null 2>&1 +} + +function shut_down(){ + PID=$(cat $SRV_PID) + if [[ $? -eq 0 ]]; then + if alive $PID; then + echo "Stopping HTTP server" + kill $PID + else + echo "Stale PID, deleting" + fi + rm $SRV_PID + else + echo "HTTP server PIDFile not found" + fi + + PID=$(cat $PELICAN_PID) + if [[ $? -eq 0 ]]; then + if alive $PID; then + echo "Killing Pelican" + kill $PID + else + echo "Stale PID, deleting" + fi + rm $PELICAN_PID + else + echo "Pelican PIDFile not found" + fi +} + +function start_up(){ + local port=$1 + echo "Starting up Pelican and HTTP server" + shift + $PELICAN --debug --autoreload -r $INPUTDIR -o $OUTPUTDIR -s $CONFFILE $PELICANOPTS & + pelican_pid=$! + echo $pelican_pid > $PELICAN_PID + mkdir -p $OUTPUTDIR && cd $OUTPUTDIR + $PY -m pelican.server $port & + srv_pid=$! + echo $srv_pid > $SRV_PID + cd $BASEDIR + sleep 1 + if ! alive $pelican_pid ; then + echo "Pelican didn't start. Is the Pelican package installed?" + return 1 + elif ! alive $srv_pid ; then + echo "The HTTP server didn't start. Is there another service using port" $port "?" + return 1 + fi + echo 'Pelican and HTTP server processes now running in background.' +} + +### +# MAIN +### +[[ ($# -eq 0) || ($# -gt 2) ]] && usage +port='' +[[ $# -eq 2 ]] && port=$2 + +if [[ $1 == "stop" ]]; then + shut_down +elif [[ $1 == "restart" ]]; then + shut_down + start_up $port +elif [[ $1 == "start" ]]; then + if ! start_up $port; then + shut_down + fi +else + usage +fi diff --git a/fabfile.py b/fabfile.py new file mode 100644 index 0000000..b3a0222 --- /dev/null +++ b/fabfile.py @@ -0,0 +1,92 @@ +from fabric.api import * +import fabric.contrib.project as project +import os +import shutil +import sys +import SocketServer + +from pelican.server import ComplexHTTPRequestHandler + +# Local path configuration (can be absolute or relative to fabfile) +env.deploy_path = 'output' +DEPLOY_PATH = env.deploy_path + +# Remote server configuration +production = 'root@localhost:22' +dest_path = '/var/www' + +# Rackspace Cloud Files configuration settings +env.cloudfiles_username = 'my_rackspace_username' +env.cloudfiles_api_key = 'my_rackspace_api_key' +env.cloudfiles_container = 'my_cloudfiles_container' + +# Github Pages configuration +env.github_pages_branch = "gh-pages" + +# Port for `serve` +PORT = 8000 + +def clean(): + """Remove generated files""" + if os.path.isdir(DEPLOY_PATH): + shutil.rmtree(DEPLOY_PATH) + os.makedirs(DEPLOY_PATH) + +def build(): + """Build local version of site""" + local('pelican -s pelicanconf.py') + +def rebuild(): + """`build` with the delete switch""" + local('pelican -d -s pelicanconf.py') + +def regenerate(): + """Automatically regenerate site upon file modification""" + local('pelican -r -s pelicanconf.py') + +def serve(): + """Serve site at http://localhost:8000/""" + os.chdir(env.deploy_path) + + class AddressReuseTCPServer(SocketServer.TCPServer): + allow_reuse_address = True + + server = AddressReuseTCPServer(('', PORT), ComplexHTTPRequestHandler) + + sys.stderr.write('Serving on port {0} ...\n'.format(PORT)) + server.serve_forever() + +def reserve(): + """`build`, then `serve`""" + build() + serve() + +def preview(): + """Build production version of site""" + local('pelican -s publishconf.py') + +def cf_upload(): + """Publish to Rackspace Cloud Files""" + rebuild() + with lcd(DEPLOY_PATH): + local('swift -v -A https://auth.api.rackspacecloud.com/v1.0 ' + '-U {cloudfiles_username} ' + '-K {cloudfiles_api_key} ' + 'upload -c {cloudfiles_container} .'.format(**env)) + +@hosts(production) +def publish(): + """Publish to production via rsync""" + local('pelican -s publishconf.py') + project.rsync_project( + remote_dir=dest_path, + exclude=".DS_Store", + local_dir=DEPLOY_PATH.rstrip('/') + '/', + delete=True, + extra_opts='-c', + ) + +def gh_pages(): + """Publish to GitHub Pages""" + rebuild() + local("ghp-import -b {github_pages_branch} {deploy_path} -p".format(**env)) diff --git a/feeds/all.atom.xml b/feeds/all.atom.xml deleted file mode 100644 index f548e4d..0000000 --- a/feeds/all.atom.xml +++ /dev/null @@ -1,9615 +0,0 @@ - -Cloud-init Infohttps://cloud-init.github.io/2021-06-29T16:23:00+00:00Cloud-init bi-weekly status2021-06-29T16:23:00+00:002021-06-29T16:23:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2021-06-29:/status-2021-06-29.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init bi-weekly office-hours meeting, started by blackboxsw, 29 Jun at 16:23 &mdash; 17:35 UTC.</li> -<li>Full logs at <a href="https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-06-29-16.23.log.html">https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-06-29-16.23.log.html</a></li> -</ul> -<h2>Meeting summary</h2> -<ul> -<li><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/t/cloud-init-status-06-29-2021/22981">https://discourse.ubuntu.com/t/cloud-init-status-06-29-2021/22981</a> (blackboxsw, 16:27)</li> -</ul> -<h2>People present (lines …</h2><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init bi-weekly office-hours meeting, started by blackboxsw, 29 Jun at 16:23 &mdash; 17:35 UTC.</li> -<li>Full logs at <a href="https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-06-29-16.23.log.html">https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-06-29-16.23.log.html</a></li> -</ul> -<h2>Meeting summary</h2> -<ul> -<li><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/t/cloud-init-status-06-29-2021/22981">https://discourse.ubuntu.com/t/cloud-init-status-06-29-2021/22981</a> (blackboxsw, 16:27)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (9)</li> -<li>meetingology (2)</li> -<li>ubottu (1)</li> -</ul> -<h2>Full log</h2> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #startmeeting cloud-init bi-weekly office-hours</p> -<p>16:23 <code>&lt;meetingology&gt;</code> Meeting started at 16:23:41 UTC. The chair is blackboxsw. Information about MeetBot at <a href="https://wiki.ubuntu.com/meetingology">https://wiki.ubuntu.com/meetingology</a></p> -<p>16:23 <code>&lt;meetingology&gt;</code> Available commands: action, commands, idea, info, link, nick</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> Hi cloud-init devs, Our biweekly office hours meeting has begun. We keep this channel open during the designated time on the channel #topic for drop in questions, feature or bug discussions and prodding committers folks for reviews.</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> All questions welcome and we'll have a couple of upstream committers with eyes on the channel to field any discussions brought up as best we can.</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> Just prior to this meeting, someone will post recent happenings in cloud-init upstream which may be of value to the community.</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> #link <a href="https://discourse.ubuntu.com/t/cloud-init-status-06-29-2021/22981">https://discourse.ubuntu.com/t/cloud-init-status-06-29-2021/22981</a></p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> As far as upstream is concerned, the only schedule detail of note is we are looking to create an official 21.3 upstream release August 28th. Before that time we hope to have some hot plug network device handling functional in cloud-init.</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> my plan today is to get falcojr a review on his foundational hotplug support work at <a href="https://github.com/canonical/cloud-init/pull/919">https://github.com/canonical/cloud-init/pull/919</a> which should allow cloud-init to support actively interacting with network config utilities to actively enable individual interfaces on device discovery after the network renderers have finished initial network bringup.</p> -<p>16:34 <code>&lt;ubottu&gt;</code> Pull 919 in canonical/cloud-init "Add new network configurers to bring up interfaces (SC-85)" [Open]</p> -<p>17:35 <code>&lt;blackboxsw&gt;</code> ok, that wraps things up for "office hours" for today. Thanks for checking in.</p> -<p>17:35 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.4.0 (<a href="https://wiki.ubuntu.com/meetingology">https://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2021-06-15T17:17:00+00:002021-06-15T17:17:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2021-06-15:/status-2021-06-15.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init bi-weekly office-hours meeting, started by blackboxsw, 15 Jun at 17:17 &mdash; 19:47 UTC.</li> -<li>Full logs at <a href="https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-06-15-17.17.log.html">https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-06-15-17.17.log.html</a></li> -</ul> -<h2>Meeting summary</h2> -<ul> -<li><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/t/cloud-init-status-06-15-2021/22730">https://discourse.ubuntu.com/t/cloud-init-status-06-15-2021/22730</a> (blackboxsw, 17:25)</li> -<li><strong>LINK</strong>: <a href="https://docs.github.com/en/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch#updating-a-local-clone-after-a-branch-name-changes">https://docs …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init bi-weekly office-hours meeting, started by blackboxsw, 15 Jun at 17:17 &mdash; 19:47 UTC.</li> -<li>Full logs at <a href="https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-06-15-17.17.log.html">https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-06-15-17.17.log.html</a></li> -</ul> -<h2>Meeting summary</h2> -<ul> -<li><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/t/cloud-init-status-06-15-2021/22730">https://discourse.ubuntu.com/t/cloud-init-status-06-15-2021/22730</a> (blackboxsw, 17:25)</li> -<li><strong>LINK</strong>: <a href="https://docs.github.com/en/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch#updating-a-local-clone-after-a-branch-name-changes">https://docs.github.com/en/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch#updating-a-local-clone-after-a-branch-name-changes</a> (blackboxsw, 17:37)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (16)</li> -<li>meetingology (3)</li> -<li>falcojr (2)</li> -</ul> -<h2>Full log</h2> -<p>17:17 <code>&lt;blackboxsw&gt;</code> #startmeeting cloud-init bi-weekly office-hours</p> -<p>17:17 <code>&lt;meetingology&gt;</code> Meeting started at 17:17:44 UTC. The chair is blackboxsw. Information about MeetBot at <a href="https://wiki.ubuntu.com/meetingology">https://wiki.ubuntu.com/meetingology</a></p> -<p>17:17 <code>&lt;meetingology&gt;</code> Available commands: action, commands, idea, info, link, nick</p> -<p>17:20 <code>&lt;blackboxsw&gt;</code> community-notice: Hi cloud-initers, welcome to another office hours meeting. cloud-init committers will be around for the next hour to field any discussions. answer questions or put some eyes on PR reviews or bugs that spark your interest.</p> -<p>17:21 <code>&lt;blackboxsw&gt;</code> We host this meeting to unblock, or unstick anybody toying around with cloud-init, as well as to update thecloud-init devs on recent changes in cloud-init upstream</p> -<p>17:21 <code>&lt;blackboxsw&gt;</code> #chair falcojr</p> -<p>17:21 <code>&lt;meetingology&gt;</code> Current chairs: blackboxsw, falcojr</p> -<p>17:25 <code>&lt;blackboxsw&gt;</code> We just published a little discourse post describing that cloud-init upstream version 21.2 has now cleared SRU validation for Ubuntu Bionic(16.04) Focal (20.04) Groovy (20.10) and Hirsute (21.04) <a href="https://discourse.ubuntu.com/t/cloud-init-status-06-15-2021/22730">https://discourse.ubuntu.com/t/cloud-init-status-06-15-2021/22730</a></p> -<p>17:25 <code>&lt;blackboxsw&gt;</code> #link <a href="https://discourse.ubuntu.com/t/cloud-init-status-06-15-2021/22730">https://discourse.ubuntu.com/t/cloud-init-status-06-15-2021/22730</a></p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> in that SRU, were some ssh_key handling improvement, Azure SSH key processing, Azure userdata updated ingested from IMDS and new support for Vultr cloud platform.</p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> Thanks all for those contributions!</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> one other interesting thing to note: 4 days ago I was banned from FreeNode. falcojr did this happen to you too? "Connection closed unexpectedly: You are banned from this server- [#1480] Contact support@freenode.net (2021/6/11 05.18):"</p> -<p>17:31 <code>&lt;falcojr&gt;</code> blackboxsw: no, that's weird. I know they completely reset everything over there though.</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> hrm maybe they tracked irc nicks that were advertizing moving to Libera.chat is the only thing I can think. will check it out</p> -<p>17:33 <code>&lt;falcojr&gt;</code> at this point probably just best to cut ties completely</p> -<p>17:35 <code>&lt;blackboxsw&gt;</code> yes agreed</p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> community-notice: reminder rename upstream/master -&gt;` upstream/main in 2 days. All active PRs will automatically be retargetted. For your local clones for cloud-init it should mean only the following:</p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> #link <a href="https://docs.github.com/en/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch#updating-a-local-clone-after-a-branch-name-changes">https://docs.github.com/en/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch#updating-a-local-clone-after-a-branch-name-changes</a></p> -<p>17:40 <code>&lt;blackboxsw&gt;</code> an email will be sent out to cloud-init@lists.launchpad.net</p> -<p>17:40 <code>&lt;blackboxsw&gt;</code> with detailed instructions.</p> -<p>19:47 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.4.0 (<a href="https://wiki.ubuntu.com/meetingology">https://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2021-06-01T17:25:00+00:002021-06-01T17:25:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2021-06-01:/status-2021-06-01.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init bi-weekly office hours (~30 mins) meeting, started by blackboxsw, 01 Jun at 17:25 &mdash; 19:29 UTC.</li> -<li>Full logs at <a href="https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-06-01-17.25.log.html">https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-06-01-17.25.log.html</a></li> -</ul> -<h2>Meeting summary</h2> -<ul> -<li><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/t/cloud-init-status-06-01-2021/22553">https://discourse.ubuntu.com/t/cloud-init-status-06-01-2021/22553</a> (blackboxsw, 17:29 …</li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init bi-weekly office hours (~30 mins) meeting, started by blackboxsw, 01 Jun at 17:25 &mdash; 19:29 UTC.</li> -<li>Full logs at <a href="https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-06-01-17.25.log.html">https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-06-01-17.25.log.html</a></li> -</ul> -<h2>Meeting summary</h2> -<ul> -<li><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/t/cloud-init-status-06-01-2021/22553">https://discourse.ubuntu.com/t/cloud-init-status-06-01-2021/22553</a> (blackboxsw, 17:29)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (9)</li> -<li>meetingology (2)</li> -</ul> -<h2>Full log</h2> -<p>17:25 <code>&lt;blackboxsw&gt;</code> #startmeeting cloud-init bi-weekly office hours (~30 mins)</p> -<p>17:25 <code>&lt;meetingology&gt;</code> Meeting started at 17:25:49 UTC. The chair is blackboxsw. Information about MeetBot at <a href="https://wiki.ubuntu.com/meetingology">https://wiki.ubuntu.com/meetingology</a></p> -<p>17:25 <code>&lt;meetingology&gt;</code> Available commands: action, commands, idea, info, link, nick</p> -<p>17:28 <code>&lt;blackboxsw&gt;</code> community-notice: office hours meeting starts now. We host this meeting time every two weeks for any drop in discussions for anything cloud-init related. Bring your bugs, feature discussions, gripes and questions and we'll have a couple sets of upstream cloud-init eyes on this channel to field those discussions.</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> highlights of recent upstream commits and project changes are at the url below:</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> #link <a href="https://discourse.ubuntu.com/t/cloud-init-status-06-01-2021/22553">https://discourse.ubuntu.com/t/cloud-init-status-06-01-2021/22553</a></p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> Of course, if you managed to join us over here you are already aware of the Freenode IRC politcal climate pushing us to migrate to a more open/friendly IRC network w/ libera.chat. paride is in the process of registering this channel for the cloud-init project so that we can add channel OPS to the upstream cloud-init committers smoser, rharper, Odd_Bloke, falcojr.</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> Once we have channel op status, we plan on adding upcoming dates, milestones and info to the IRC channel title.</p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> Also, as upstream, we want to rename the default development branch from 'master' to 'main' to provide more inclusive naming and drop antiquated and exclusive naming conventions. An email will be sent to the cloud-init mailing list explaining the perceived impact of such a default branch rename (which should be minimal).</p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> If there are any concerns about this rename impacting business, please raise concerns here, on the discourse post above or on the mailinglist</p> -<p>19:29 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.4.0 (<a href="https://wiki.ubuntu.com/meetingology">https://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2021-05-18T16:32:00+00:002021-05-18T16:32:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2021-05-18:/status-2021-05-18.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init bi-weekly office-hours meeting, started by blackboxsw, 18 May at 16:32 &mdash; 17:26 UTC.</li> -<li>Full logs at <a href="https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-05-18-16.32.log.html">https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-05-18-16.32.log.html</a></li> -</ul> -<h2>Meeting summary</h2> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (12)</li> -<li>paride (4)</li> -<li>smoser (4)</li> -<li>meetingology (2)</li> -<li>ubot5 (1 …</li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init bi-weekly office-hours meeting, started by blackboxsw, 18 May at 16:32 &mdash; 17:26 UTC.</li> -<li>Full logs at <a href="https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-05-18-16.32.log.html">https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-05-18-16.32.log.html</a></li> -</ul> -<h2>Meeting summary</h2> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (12)</li> -<li>paride (4)</li> -<li>smoser (4)</li> -<li>meetingology (2)</li> -<li>ubot5 (1)</li> -<li>falcojr (1)</li> -</ul> -<h2>Full log</h2> -<p>16:32 <code>&lt;blackboxsw&gt;</code> #startmeeting cloud-init bi-weekly office-hours</p> -<p>16:32 <code>&lt;meetingology&gt;</code> Meeting started at 16:32:21 UTC. The chair is blackboxsw. Information about MeetBot at <a href="https://wiki.ubuntu.com/meetingology">https://wiki.ubuntu.com/meetingology</a></p> -<p>16:32 <code>&lt;meetingology&gt;</code> Available commands: action, commands, idea, info, link, nick</p> -<p>16:32 <code>&lt;paride&gt;</code> smoser, thanks, merged!</p> -<p>16:33 <code>&lt;paride&gt;</code> but as it's not in the server packageset I'll need sponsorship for the upload...</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> community-notice: Let's get back to a more regularly scheduled cloud-init office hours. Every two weeks, feel free to watch the channel topic for the next scheduled time. We'll ensure to have a couple of sets of eyes on this IRC channel.</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> Next office-hours meeting is set for June 1, 17:15 UTC. It is worth us having this recurring meeting to give anyone a chance to drive-by #cloud-init if they have questions, discussions, bugs or PRs that need attention.</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> Prior to the office hours, we will continue to generate a post with the latest commits to land in cloud-init:master as well as any notable features in progress <a href="https://discourse.ubuntu.com/t/cloud-init-status-05-18-2021/22349">https://discourse.ubuntu.com/t/cloud-init-status-05-18-2021/22349</a></p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> From upstream standpoint, we were able to cut the time-based release 21.2 on May 6th. And for Ubuntu, we have queued the StableReleaseUpdate (SRU) for 21.2 into Bionic, Focal and Hirsute for which falcojr and Odd_Bloke have been going through verification.</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> Think we need to update the topic for the 21.2 upstream release too.</p> -<p>16:42 <code>&lt;smoser&gt;</code> paride: <a href="https://paste.ubuntu.com/p/y3N7wjCG3n/">https://paste.ubuntu.com/p/y3N7wjCG3n/</a></p> -<p>16:44 <code>&lt;smoser&gt;</code> fudge.</p> -<p>16:44 <code>&lt;smoser&gt;</code> but i just noticed your changelog didn't have LP: #1908452</p> -<p>16:44 <code>&lt;ubot5&gt;</code> Launchpad bug 1908452 in MAAS "MAAS stops working and deployment fails after <code>Loading ephemeral</code> step" [High,In progress] <a href="https://launchpad.net/bugs/1908452">https://launchpad.net/bugs/1908452</a></p> -<p>16:45 <code>&lt;smoser&gt;</code> because the commit message said 'Fixes LP:1908452' rather than just 'LP: #1908452'</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> 'Fixes LP:1908452' almost github; almost LP :/</p> -<p>16:48 <code>&lt;paride&gt;</code> smoser, argh :/ will update the bug status manually</p> -<p>16:48 <code>&lt;paride&gt;</code> thanks for the upload</p> -<p>16:50 * blackboxsw falcojr: do we have a trello board for the SRU 21.2 created?</p> -<p>16:50 <code>&lt;falcojr&gt;</code> yep, <a href="https://trello.com/b/tBP3Jrwp/sru-cloud-init-212">https://trello.com/b/tBP3Jrwp/sru-cloud-init-212</a> (just made it public)</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> Thanks a lot</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> Great, I was originally looking at the older trello board for the 21.1. Ok, so I'll grab Softlayer testing as you mentioned at standup today. If you want me to run through other clouds just let me know or hit me up for reviews.</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> Alright, I think that about wraps today's office hours. Next round in two weeks. Thanks for tuning in.</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.4.0 (<a href="https://wiki.ubuntu.com/meetingology">https://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2021-04-06T16:20:00+00:002021-04-06T16:20:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2021-04-06:/status-2021-04-06.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init bi-weekly office-hours meeting, started by blackboxsw, 06 Apr at 16:20 &mdash; 17:37 UTC.</li> -<li>Full logs at <a href="https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-04-06-16.20.log.html">https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-04-06-16.20.log.html</a></li> -</ul> -<h2>Meeting summary</h2> -<h2>People present (lines said)</h2> -<ul> -<li>hamalq (7)</li> -<li>blackboxsw (6)</li> -<li>falcojr (3)</li> -<li>meetingology (2)</li> -<li>Odd_Bloke (1 …</li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init bi-weekly office-hours meeting, started by blackboxsw, 06 Apr at 16:20 &mdash; 17:37 UTC.</li> -<li>Full logs at <a href="https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-04-06-16.20.log.html">https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-04-06-16.20.log.html</a></li> -</ul> -<h2>Meeting summary</h2> -<h2>People present (lines said)</h2> -<ul> -<li>hamalq (7)</li> -<li>blackboxsw (6)</li> -<li>falcojr (3)</li> -<li>meetingology (2)</li> -<li>Odd_Bloke (1)</li> -</ul> -<h2>Full log</h2> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #startmeeting cloud-init bi-weekly office-hours</p> -<p>16:20 <code>&lt;meetingology&gt;</code> Meeting started at 16:20:26 UTC. The chair is blackboxsw. Information about MeetBot at <a href="https://wiki.ubuntu.com/meetingology">https://wiki.ubuntu.com/meetingology</a></p> -<p>16:20 <code>&lt;meetingology&gt;</code> Available commands: action, commands, idea, info, link, nick</p> -<p>16:21 <code>&lt;falcojr&gt;</code> I think by default it should use the current defaults of what's chosen...e.g., true for rhel and false for others</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> Hi cloud-init! This marks another episode of cloud-init community office hours. This time is an opportunity to discuss any cloud-init questions, bugs or topics with cloud-init upstream developers. We try to ensure a couple of devs have eyes on this channel to field any questions/concerns folks may have.</p> -<p>16:24 <code>&lt;Odd_Bloke&gt;</code> o/</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> Recent happenings in cloud-init space are generally spent on the current SRU validation with Odd_Bloke and falcojr. It looks like we've cleared the last manual validation with that SRU and we will be waiting on a significant automated set of tests to pass before making this release public. <a href="https://discourse.ubuntu.com/t/cloud-init-status-04-06-2021/21691">https://discourse.ubuntu.com/t/cloud-init-status-04-06-2021/21691</a></p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> thanks falcojr and Odd_Bloke for reviews on <a href="https://github.com/canonical/cloud-init/pull/859">https://github.com/canonical/cloud-init/pull/859</a></p> -<p>16:36 <code>&lt;hamalq&gt;</code> i already did the change as the comment</p> -<p>16:37 <code>&lt;hamalq&gt;</code> i dont think i can change cloudinit/distros/<strong>init</strong>.py select_hostname though</p> -<p>16:38 <code>&lt;falcojr&gt;</code> we can change it...we just need to make sure the functionality stays the same if the option isn't specified</p> -<p>16:39 <code>&lt;hamalq&gt;</code> thats the point since the default for that option is true</p> -<p>16:40 <code>&lt;hamalq&gt;</code> unless we make the default for it false for other distros</p> -<p>16:41 <code>&lt;falcojr&gt;</code> yes, we would need to take it into account for all distros, and it would default to false for most</p> -<p>16:42 <code>&lt;hamalq&gt;</code> +1</p> -<p>16:47 <code>&lt;hamalq&gt;</code> i changed that now for distros and rhel</p> -<p>17:15 <code>&lt;hamalq&gt;</code> i think i got the changes required <a href="https://github.com/canonical/cloud-init/pull/859">https://github.com/canonical/cloud-init/pull/859</a></p> -<p>17:36 <code>&lt;blackboxsw&gt;</code> thanks folks for attending the office hours. See you all in two weeks. Same time</p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.4.0 (<a href="https://wiki.ubuntu.com/meetingology">https://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2021-03-23T17:22:00+00:002021-03-23T17:22:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2021-03-23:/status-2021-03-23.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init bi-weekly office-hours meeting, started by Odd_Bloke, 23 Mar at 17:22 &mdash; 18:24 UTC.</li> -<li>Full logs at <a href="https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-03-23-17.22.log.html">https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-03-23-17.22.log.html</a></li> -</ul> -<h2>Meeting summary</h2> -<ul> -<li><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/t/cloud-init-status-03-23-2021/21490">https://discourse.ubuntu.com/t/cloud-init-status-03-23-2021/21490</a> (Odd_Bloke, 17:23)</li> -<li><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/t/cloud-init-status-03-23-2021/21490">https://discourse …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init bi-weekly office-hours meeting, started by Odd_Bloke, 23 Mar at 17:22 &mdash; 18:24 UTC.</li> -<li>Full logs at <a href="https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-03-23-17.22.log.html">https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-03-23-17.22.log.html</a></li> -</ul> -<h2>Meeting summary</h2> -<ul> -<li><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/t/cloud-init-status-03-23-2021/21490">https://discourse.ubuntu.com/t/cloud-init-status-03-23-2021/21490</a> (Odd_Bloke, 17:23)</li> -<li><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/t/cloud-init-status-03-23-2021/21490">https://discourse.ubuntu.com/t/cloud-init-status-03-23-2021/21490</a> (blackboxsw, 17:23)</li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bug/1724414">https://bugs.launchpad.net/cloud-init/+bug/1724414</a> (blackboxsw, 17:25)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (11)</li> -<li>Odd_Bloke (10)</li> -<li>meetingology (3)</li> -<li>ubot5 (1)</li> -<li>falcojr (0)</li> -</ul> -<h2>Full log</h2> -<p>17:22 <code>&lt;Odd_Bloke&gt;</code> #startmeeting cloud-init bi-weekly office-hours</p> -<p>17:22 <code>&lt;meetingology&gt;</code> Meeting started at 17:22:08 UTC. The chair is Odd_Bloke. Information about MeetBot at <a href="https://wiki.ubuntu.com/meetingology">https://wiki.ubuntu.com/meetingology</a></p> -<p>17:22 <code>&lt;meetingology&gt;</code> Available commands: action, commands, idea, info, link, nick</p> -<p>17:22 <code>&lt;Odd_Bloke&gt;</code> #chair blackboxsw falcojr</p> -<p>17:22 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke, blackboxsw, falcojr</p> -<p>17:22 <code>&lt;blackboxsw&gt;</code> \0 woot thanks Odd_Bloke</p> -<p>17:23 <code>&lt;Odd_Bloke&gt;</code> Hey folks, the cloud-init committers will be around for the next while, to answer any questions or have any discussions you're interested in having.</p> -<p>17:23 <code>&lt;Odd_Bloke&gt;</code> blackboxsw posted a status update to Discourse earlier today.</p> -<p>17:23 <code>&lt;blackboxsw&gt;</code> Here's the discourse post for reference on recent cloud-init events</p> -<p>17:23 <code>&lt;Odd_Bloke&gt;</code> #link <a href="https://discourse.ubuntu.com/t/cloud-init-status-03-23-2021/21490">https://discourse.ubuntu.com/t/cloud-init-status-03-23-2021/21490</a></p> -<p>17:23 <code>&lt;blackboxsw&gt;</code> #link <a href="https://discourse.ubuntu.com/t/cloud-init-status-03-23-2021/21490">https://discourse.ubuntu.com/t/cloud-init-status-03-23-2021/21490</a></p> -<p>17:23 <code>&lt;blackboxsw&gt;</code> thanks Odd_Bloke</p> -<p>17:23 <code>&lt;Odd_Bloke&gt;</code> Haha</p> -<p>17:23 <code>&lt;Odd_Bloke&gt;</code> Please read it twice.</p> -<p>17:24 <code>&lt;blackboxsw&gt;</code> and correct any clerical errors</p> -<p>17:25 <code>&lt;blackboxsw&gt;</code> one topic of interested that hamalq brought up yesterday was the "feature" of RedHat and CentOS that automatically prefers fqdn over hostname in #cloud-config per this bug</p> -<p>17:25 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/+bug/1724414">https://bugs.launchpad.net/cloud-init/+bug/1724414</a></p> -<p>17:25 <code>&lt;ubot5&gt;</code> Ubuntu bug 1724414 in cloud-init "rhel distro selects FQDN as hostname" [Low,Won't fix]</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> I mentioned we'd bring it up to reflect our opinion on this behavior today after a discussion</p> -<p>17:28 <code>&lt;blackboxsw&gt;</code> I think the upstream stance on RedHat and CentOS is that this default behavior on RedHat/CentOS has been in play for a long time and changing that default behavior would be asking to cause problems for the majority of users who may rely on this behavior during system launch.</p> -<p>17:28 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: falcojr did we say in this case we'd prefer a new bug which better describes the desired use-case and how current cloud-init doesn't allow for that use-case?</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> that's all the content/discussion I had. I know I needed to get otubo a review today on his resize lvm partition branch <a href="https://github.com/canonical/cloud-init/pull/721">https://github.com/canonical/cloud-init/pull/721</a> as my stale review was blocking that.</p> -<p>17:31 <code>&lt;Odd_Bloke&gt;</code> We've closed out that bug as Won't Fix; we'd like folks who consider themselves affected by that bug to file a new one which describes their specific problem with the current situation: we can then work to support those requirements.</p> -<p>18:24 <code>&lt;Odd_Bloke&gt;</code> OK, sounds like there's not much to chat about; thanks to any lurkers. :)</p> -<p>18:24 <code>&lt;Odd_Bloke&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.4.0 (<a href="https://wiki.ubuntu.com/meetingology">https://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2021-03-09T17:19:00+00:002021-03-09T17:19:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2021-03-09:/status-2021-03-09.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init bi-weekly office-hours meeting, started by blackboxsw, 09 Mar at 17:19 &mdash; 18:38 UTC.</li> -<li>Full logs at <a href="https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-03-09-17.19.log.html">https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-03-09-17.19.log.html</a></li> -</ul> -<h2>Meeting summary</h2> -<ul> -<li><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/t/cloud-init-status-03-09-2021/21309">https://discourse.ubuntu.com/t/cloud-init-status-03-09-2021/21309</a> (blackboxsw, 17:23)</li> -</ul> -<h2>People present (lines …</h2><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init bi-weekly office-hours meeting, started by blackboxsw, 09 Mar at 17:19 &mdash; 18:38 UTC.</li> -<li>Full logs at <a href="https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-03-09-17.19.log.html">https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-03-09-17.19.log.html</a></li> -</ul> -<h2>Meeting summary</h2> -<ul> -<li><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/t/cloud-init-status-03-09-2021/21309">https://discourse.ubuntu.com/t/cloud-init-status-03-09-2021/21309</a> (blackboxsw, 17:23)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (14)</li> -<li>falcojr (8)</li> -<li>beantaxi (7)</li> -<li>meetingology (3)</li> -<li>Odd_Bloke (3)</li> -</ul> -<h2>Full log</h2> -<p>17:19 <code>&lt;blackboxsw&gt;</code> #startmeeting cloud-init bi-weekly office-hours</p> -<p>17:19 <code>&lt;meetingology&gt;</code> Meeting started at 17:19:08 UTC. The chair is blackboxsw. Information about MeetBot at <a href="https://wiki.ubuntu.com/meetingology">https://wiki.ubuntu.com/meetingology</a></p> -<p>17:19 <code>&lt;meetingology&gt;</code> Available commands: action, commands, idea, info, link, nick</p> -<p>17:19 <code>&lt;blackboxsw&gt;</code> #char Odd_Bloke falcojr</p> -<p>17:19 <code>&lt;blackboxsw&gt;</code> #chair Odd_Bloke falcojr</p> -<p>17:19 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke, blackboxsw, falcojr</p> -<p>17:20 <code>&lt;blackboxsw&gt;</code> hi cloud-init, sorry for the confusion on the UTC time that I posted in the topic. I had incorrectly set 15:15 UTC instead of 17:15.</p> -<p>17:20 <code>&lt;blackboxsw&gt;</code> welcome to the bi-weekly cloud-init office hours</p> -<p>17:21 <code>&lt;blackboxsw&gt;</code> This cloud-init status meeting has moved to a more asynchronous posting of high-level happenings in cloud-init to discourse to support timezone differences for all cloud-init developers.</p> -<p>17:23 <code>&lt;blackboxsw&gt;</code> We plan on continuing to host these office hours to provide a means for quick communication, questions and discussions with a couple of upstream developers present to help facilite any questions or discussions of interest to folks.</p> -<p>17:23 <code>&lt;blackboxsw&gt;</code> For reference, here are the high-level "happenings" in cloud-init upstream over the last two weeks.</p> -<p>17:23 <code>&lt;Odd_Bloke&gt;</code> o/</p> -<p>17:23 <code>&lt;blackboxsw&gt;</code> #link <a href="https://discourse.ubuntu.com/t/cloud-init-status-03-09-2021/21309">https://discourse.ubuntu.com/t/cloud-init-status-03-09-2021/21309</a></p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> As of last office-hours I belive upstream had just cut the first 21.1 release in the tip of cloud-init. Canonical will be starting the SRU process this week I believe to publish the 21.1 release (plus a couple of extra fixes which just landed in tip) into Ubuntu Xenial, Bionic, Focal, Groovy and Hirsute.</p> -<p>17:41 <code>&lt;beantaxi&gt;</code> Odd_Bloke: I tried your command and it was helpful. It complained about a missing ssh key, so I shrugged, tried ssh-keygen -t rsa and reran the test, and it passed. I've kicked off a run of all the tests, which I assume will take a bit.</p> -<p>17:55 <code>&lt;Odd_Bloke&gt;</code> beantaxi: Great, thanks for the update! A full run in LXD containers takes ~12mins locally (though I'm probably running on beefier hardware than you're paying EC2 for so YMMV :p).</p> -<p>17:55 <code>&lt;Odd_Bloke&gt;</code> beantaxi: Once you had the output, was it clear that the missing SSH key was the issue?</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> setting the appropriate time for next office hours</p> -<p>17:56 <code>&lt;blackboxsw&gt;</code> setting the appropriate time for next office hours Mar 23 17:15 UTC</p> -<p>17:57 <code>&lt;beantaxi&gt;</code> ERROR tests/integration_tests/modules/test_runcmd.py::TestRuncmd::test_runcmd - FileNotFoundError: [Errno 2] No such file or directory: '/home/ubuntu/.ssh/id_rsa.pub'</p> -<p>17:57 <code>&lt;beantaxi&gt;</code> That was the error message</p> -<p>17:59 <code>&lt;falcojr&gt;</code> tests require an ssh keypair. It'll use your user one by default or you can specify one manually in the integration settings config</p> -<p>17:59 <code>&lt;falcojr&gt;</code> do an <code>ssh-keygen</code></p> -<p>17:59 <code>&lt;beantaxi&gt;</code> The full test failed with 7 failures: <a href="https://paste.ubuntu.com/p/hcYN7ZDvbs/">https://paste.ubuntu.com/p/hcYN7ZDvbs/</a></p> -<p>18:00 <code>&lt;beantaxi&gt;</code> falcojr: Thanks ... I was just showing Odd_Bloke the error message I got before running ssh-keygen, which did indeed solve most of my issues</p> -<p>18:01 <code>&lt;beantaxi&gt;</code> falcojr: Also, this is just me running the existing integration tests on an EC2 instance. Without any of my changes</p> -<p>18:01 <code>&lt;falcojr&gt;</code> not sure the cause of that first one, but the rest are for code not in ubuntu images yet</p> -<p>18:03 <code>&lt;falcojr&gt;</code> the version of cloud_init to use is specified by the CLOUD_INIT_SOURCE variable (integration_settings.py...copy this to user_settings.py to easily override defaults)</p> -<p>18:03 <code>&lt;falcojr&gt;</code> it defaults to NONE which means use whatever image has been released on this platform</p> -<p>18:04 <code>&lt;falcojr&gt;</code> to test non-released code, changing it to IN_PLACE (only works on LXD) should work</p> -<p>18:08 <code>&lt;falcojr&gt;</code> you can also set it to ppa:cloud-init-dev/daily , but that won't contain any changes that you're trying to test</p> -<p>18:18 <code>&lt;beantaxi&gt;</code> falcojr: Copying integration_settings.py to user_settings.py and setting CLOUD_INIT_SOURCE=IN_PLACE made all the test_keys_to_console errors clean. There's still that simple_streams error. Do I just need to add a PPA for simplestreams? It looks like requires a file in /etc/apt/sources.list.d, but mine is empty</p> -<p>18:23 <code>&lt;falcojr&gt;</code> Not sure off the top of my head. Did you pip install the integration_requirements.txt?</p> -<p>18:38 * blackboxsw thinks I should about wrap up office hours. Thanks falcojr Odd_Bloke and beantaxi for the discussion there</p> -<p>18:38 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.4.0 (<a href="https://wiki.ubuntu.com/meetingology">https://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2021-02-23T17:18:00+00:002021-02-23T17:18:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2021-02-23:/status-2021-02-23.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init office hours meeting, started by blackboxsw, 23 Feb at 17:18 &mdash; 18:00 UTC.</li> -<li>Full logs at <a href="https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-02-23-17.18.log.html">https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-02-23-17.18.log.html</a></li> -</ul> -<h2>Meeting summary</h2> -<ul> -<li><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/c/server/cloud-init">https://discourse.ubuntu.com/c/server/cloud-init</a> (blackboxsw, 17:30)</li> -</ul> -<h2>People present (lines …</h2><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init office hours meeting, started by blackboxsw, 23 Feb at 17:18 &mdash; 18:00 UTC.</li> -<li>Full logs at <a href="https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-02-23-17.18.log.html">https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-02-23-17.18.log.html</a></li> -</ul> -<h2>Meeting summary</h2> -<ul> -<li><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/c/server/cloud-init">https://discourse.ubuntu.com/c/server/cloud-init</a> (blackboxsw, 17:30)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (17)</li> -<li>meetingology (2)</li> -<li>Odd_Bloke (2)</li> -</ul> -<h2>Full log</h2> -<p>17:18 <code>&lt;blackboxsw&gt;</code> #startmeeting cloud-init office hours</p> -<p>17:18 <code>&lt;meetingology&gt;</code> Meeting started at 17:18:36 UTC. The chair is blackboxsw. Information about MeetBot at <a href="https://wiki.ubuntu.com/meetingology">https://wiki.ubuntu.com/meetingology</a></p> -<p>17:18 <code>&lt;meetingology&gt;</code> Available commands: action, commands, idea, info, link, nick</p> -<p>17:18 <code>&lt;Odd_Bloke&gt;</code> o/</p> -<p>17:19 <code>&lt;blackboxsw&gt;</code> community notice: hi folks. We are resuming our much anticipated office hours. Every two weeks at this time. The IRC topic will host our upcoming expected office-hours meeting time.</p> -<p>17:19 <code>&lt;blackboxsw&gt;</code> \o Odd_Bloke thx</p> -<p>17:19 <code>&lt;blackboxsw&gt;</code> t</p> -<p>17:20 <code>&lt;blackboxsw&gt;</code> This meeting will provide an opportunity with multiple upstream cloud-init devs available to discuss bugs, features, ongoing development or answer your existential questions :)</p> -<p>17:20 <code>&lt;blackboxsw&gt;</code> We hope to continue this meeting with regular cadence (and calendar reminders) to make sure we hold this time and frequency.</p> -<p>17:22 <code>&lt;blackboxsw&gt;</code> I'll send an email to the mailing list (again) announcing this cadence. Again this time if for any discussions, questions or dev/feature topics that folks would like to gab about.</p> -<p>17:23 <code>&lt;blackboxsw&gt;</code> We just published a high-level update of what's been happening in the cloud-init space, <a href="https://discourse.ubuntu.com/t/cloud-init-status-02-23-2021/21069.">https://discourse.ubuntu.com/t/cloud-init-status-02-23-2021/21069.</a></p> -<p>17:25 <code>&lt;blackboxsw&gt;</code> As seen on the mailinglist, Odd_Bloke and falcojr have been trying to tidy up things for the upstream 21.1 timed release. Thanks both of you for driving this work. I believe 21.1 landed, was uploaded to Ubuntu 21.04 (Hirsute).</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> We are also planning on SRUing(StableReleaseUpdate - Ubuntu-speak for uploading) 21.1 plus a feature fix for OVS support into Xenial, Bionic, Focal and Groovy within the next week or two.</p> -<p>17:26 <code>&lt;Odd_Bloke&gt;</code> Yep, I'm currently working through the release announcement process.</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> great Dan. So, TLDR is watch the mailinglist cloud-init@lists.launchpad.net and discourse <a href="https://discourse.ubuntu.com/c/server/cloud-init">https://discourse.ubuntu.com/c/server/cloud-init</a> for announcements and updates</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> #link <a href="https://discourse.ubuntu.com/c/server/cloud-init">https://discourse.ubuntu.com/c/server/cloud-init</a></p> -<p>17:58 <code>&lt;blackboxsw&gt;</code> I think we've about rounded out the office-hours. (I spent that time walking through a sopel-irc bot setup to test out some of the features to see if we can't add some structure to this office-hours engagement (and frankly release announcements too )</p> -<p>17:59 <code>&lt;blackboxsw&gt;</code> Let's set that next office hours for +2 weeks-45 mins from now</p> -<p>18:00 <code>&lt;blackboxsw&gt;</code> hopefully by then we have an automated announcer kicking off the notification.</p> -<p>18:00 <code>&lt;blackboxsw&gt;</code> Thanks all!</p> -<p>18:00 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.4.0 (<a href="https://wiki.ubuntu.com/meetingology">https://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2020-11-17T17:25:00+00:002020-11-17T17:25:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2020-11-17:/status-2020-11-17.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting &amp;&amp; office hours, 17 Nov at 17:25 &mdash; 18:35 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-11-17-17.25.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-11-17-17.25.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/t/cloud-init-statue-11-17-20/19391">https://discourse.ubuntu.com/t/cloud-init-statue-11-17-20/19391</a> - <strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pull/655">https://github.com/canonical/cloud-init/pull/655</a> i'd …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting &amp;&amp; office hours, 17 Nov at 17:25 &mdash; 18:35 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-11-17-17.25.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-11-17-17.25.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/t/cloud-init-statue-11-17-20/19391">https://discourse.ubuntu.com/t/cloud-init-statue-11-17-20/19391</a> - <strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pull/655">https://github.com/canonical/cloud-init/pull/655</a> i'd love this too get merged, so we don't have to carry the patch on ports - <strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pull/655">https://github.com/canonical/cloud-init/pull/655</a> - <strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pull/647">https://github.com/canonical/cloud-init/pull/647</a> - <strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pull/588#pullrequestreview-529957360">https://github.com/canonical/cloud-init/pull/588#pullrequestreview-529957360</a> - <strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/sources/DataSourceAzure.py#L1325">https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/sources/DataSourceAzure.py#L1325</a> - <strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/config/cc_set_passwords.py#L163">https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/config/cc_set_passwords.py#L163</a> - <strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pull/663">https://github.com/canonical/cloud-init/pull/663</a> - <strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pull/659">https://github.com/canonical/cloud-init/pull/659</a> - <strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pulls">https://github.com/canonical/cloud-init/pulls</a>?q=is%3Apr+is%3Aopen+label%3A%22release+20.4%22 </p> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (48)</li> -<li>AnhVoMSFT (15)</li> -<li>rharper (7)</li> -<li>meena (6)</li> -<li>smoser (3)</li> -<li>meetingology (3)</li> -<li>Odd_Bloke (1)</li> -</ul> -<h2>Full Log</h2> -<p>17:25 <code>&lt;blackboxsw&gt;</code> #startmeeting cloud-init status meeting &amp;&amp; office hours</p> -<p>17:25 <code>&lt;meetingology&gt;</code> Meeting started Tue Nov 17 17:25:00 2020 UTC. The chair is blackboxsw. Information about MeetBot at <a href="http://wiki.ubuntu.com/meetingology.">http://wiki.ubuntu.com/meetingology.</a></p> -<p>17:25 <code>&lt;meetingology&gt;</code> </p> -<p>17:25 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>17:25 <code>&lt;blackboxsw&gt;</code> community-notice: hi folks just starting up an our cloud-init satus update and office hours community meeting.</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> As of the cloud-init summit, we decided to try to host these primarily async in discourse to allow folks in other timezones to participate as available.</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> I've just finished posting a status update for cloud-init upstream to <a href="https://discourse.ubuntu.com/t/cloud-init-statue-11-17-20/19391">https://discourse.ubuntu.com/t/cloud-init-statue-11-17-20/19391</a></p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> #link <a href="https://discourse.ubuntu.com/t/cloud-init-statue-11-17-20/19391">https://discourse.ubuntu.com/t/cloud-init-statue-11-17-20/19391</a></p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> #chairs rharper smoser Odd_Bloke</p> -<p>17:28 <code>&lt;rharper&gt;</code> o/</p> -<p>17:28 <code>&lt;blackboxsw&gt;</code> Generally I think this status meeting can be used as a platform for communication and discussion with the community.</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> for this week, as brought up by a few folks in the community, is that we are trying to define a "go" date for the next upstream cloud-init release 20.4.</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> The hope is to target this Friday Nov 20th. as a deadline for requesting specific PRs and reviews that are needed to get features or fixes included in this 20.4 release.</p> -<p>17:31 <code>&lt;meena&gt;</code> so, i just responded to falcojr's email</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> The goal of this date, from an Ubuntu standpoint, is also to be able to SRU (stable release update) and publish this functionality back to Xenial, Bionic and Focal before the end of the calendar year</p> -<p>17:32 <code>&lt;meena&gt;</code> <a href="https://github.com/canonical/cloud-init/pull/655">https://github.com/canonical/cloud-init/pull/655</a> i'd love this too get merged, so we don't have to carry the patch on ports</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> thanks meena there <a href="https://github.com/canonical/cloud-init/pull/655">https://github.com/canonical/cloud-init/pull/655</a> ahh I'm too late</p> -<p>17:34 <code>&lt;blackboxsw&gt;</code> So, for those who happen to be on this channel now, let's add links to the meeting log and I'll make sure they are also reflected on the discourse post and PRs that need review assessment and hopefully landing before upstream release cut.</p> -<p>17:34 <code>&lt;blackboxsw&gt;</code> #link <a href="https://github.com/canonical/cloud-init/pull/655">https://github.com/canonical/cloud-init/pull/655</a></p> -<p>17:34 <code>&lt;blackboxsw&gt;</code> rharper or smoser are there any concerns with existing PRs that you are aware of that should be destined for this 20.4 release?</p> -<p>17:35 <code>&lt;meena&gt;</code> rharper, i'd also love your historic knowledge on <a href="https://github.com/canonical/cloud-init/pull/588">https://github.com/canonical/cloud-init/pull/588</a> but that can wait until after the release</p> -<p>17:36 <code>&lt;blackboxsw&gt;</code> rharper: I wanted to put a solid review on the cached ds handling today/tomorrow</p> -<p>17:36 <code>&lt;blackboxsw&gt;</code> #link <a href="https://github.com/canonical/cloud-init/pull/647">https://github.com/canonical/cloud-init/pull/647</a></p> -<p>17:36 <code>&lt;blackboxsw&gt;</code> I've looked it over a couple times, but wanted to but some investment in the review myself today.</p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: welcome and thanks for peeking in to checkup. If your team also have any hopes for PRs you can pitch us here, discourse or email.</p> -<p>17:38 <code>&lt;AnhVoMSFT&gt;</code> I have a quick question on the cc_set_passwords. I'm still looking through the code but if anyone knows this one well and can point me to the right place to look it would be appreciated</p> -<p>17:39 <code>&lt;AnhVoMSFT&gt;</code> it seems like if we create an image that previously was deployed with password ABC, but during image preparation we don't delete that user, then when we deploy a VM with that image and specifying a new password DEF, it isn't applied. I.e., the user will still have password ABC</p> -<p>17:39 <code>&lt;rharper&gt;</code> blackboxsw: I'm not aware of anything critical PR wise; maybe the networking_cls bits; but not sure if that's ready;</p> -<p>17:40 <code>&lt;meena&gt;</code> from my understanding, that needs to get in</p> -<p>17:40 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: poking around now on that</p> -<p>17:41 <code>&lt;rharper&gt;</code> meena: yes; that makes sense; just hadn't looked at the current state of the PR since I last commented;</p> -<p>17:42 <code>&lt;rharper&gt;</code> meena: re: 588 (genreate_fallback_config); did you have a specific question you wanted some background on?</p> -<p>17:43 <code>&lt;meena&gt;</code> rharper, search for your name</p> -<p>17:44 <code>&lt;rharper&gt;</code> hidden under a "Load more Items"</p> -<p>17:44 <code>&lt;rharper&gt;</code> I'll respond</p> -<p>17:44 <code>&lt;blackboxsw&gt;</code> so instance-id should have changed on the newly deployed vm, so cc_set_passwords should get retriggered due to <a href="https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_set_passwords.py#L49">https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_set_passwords.py#L49</a> (the default frequency for cc modules). AnhVoMSFT: what the userdata password field you are using? top-level password or chpasswd?</p> -<p>17:45 <code>&lt;AnhVoMSFT&gt;</code> this is the user password passed in from ovf</p> -<p>17:45 <code>&lt;blackboxsw&gt;</code> as that'd be different code paths I think</p> -<p>17:45 <code>&lt;meena&gt;</code> <a href="https://github.com/canonical/cloud-init/pull/588#pullrequestreview-529957360">https://github.com/canonical/cloud-init/pull/588#pullrequestreview-529957360</a></p> -<p>17:46 <code>&lt;AnhVoMSFT&gt;</code> in a newly created instance without the existing user, I could see the password getting created during the initial useradd call when the user is created</p> -<p>17:47 <code>&lt;AnhVoMSFT&gt;</code> however, if the user existed, that code path isn't invoked. There's some code in cc_set_passwords to change the password for existing user, but I'm unsure when it's invoked (or why it's not invoked in the case of azure)</p> -<p>17:48 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: could you provide a paste of redacted userdata from that instance via <code>sudo cloud-init query userdata</code>... redacting the specific passwords ?</p> -<p>17:49 <code>&lt;blackboxsw&gt;</code> yeah I would have expected a log.debug("Changing password for %s:", users) log</p> -<p>17:53 <code>&lt;AnhVoMSFT&gt;</code> let me run the query</p> -<p>17:53 <code>&lt;AnhVoMSFT&gt;</code> there's nothing returned (since there's no userdata)</p> -<p>17:54 <code>&lt;AnhVoMSFT&gt;</code> looks like the ds Azure is adding the user/password information retrieved from OVF to cfg['defuser']</p> -<p>18:00 <code>&lt;AnhVoMSFT&gt;</code> <a href="https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/sources/DataSourceAzure.py#L1325">https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/sources/DataSourceAzure.py#L1325</a></p> -<p>18:00 <code>&lt;AnhVoMSFT&gt;</code> if I'm reading the code of cc_set_password correctly we will need to add cfg['password'] as well if we want the defuser's password to be changed?</p> -<p>18:01 <code>&lt;Odd_Bloke&gt;</code> rharper: We are treating the networking_cls PR as critical, and AFA(I/we)K it's pretty much ready to land.</p> -<p>18:02 <code>&lt;rharper&gt;</code> Odd_Bloke: ok, makes sense</p> -<p>18:06 <code>&lt;smoser&gt;</code> blackboxsw: i dont have anything critical.</p> -<p>18:06 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: so normalize_users_groups is what pulls the default_user configuration out of /etc/cloud/cloud.cfg(.d/*)</p> -<p>18:06 <code>&lt;blackboxsw&gt;</code> <a href="https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/config/cc_set_passwords.py#L163">https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/config/cc_set_passwords.py#L163</a></p> -<p>18:07 <code>&lt;blackboxsw&gt;</code> that ug_util.extract_default is what should be seeing the passwords set/changed</p> -<p>18:07 <code>&lt;smoser&gt;</code> </p> -<p>18:08 <code>&lt;smoser&gt;</code> #669 looks reasonable.</p> -<p>18:08 <code>&lt;blackboxsw&gt;</code> yet interestingly. password referenced there is only set from the top-level "password" value <a href="https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/config/cc_set_passwords.py#L143">https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/config/cc_set_passwords.py#L143</a></p> -<p>18:08 <code>&lt;blackboxsw&gt;</code> thanks smoser for that</p> -<p>18:08 <code>&lt;blackboxsw&gt;</code> #link <a href="https://github.com/canonical/cloud-init/pull/663">https://github.com/canonical/cloud-init/pull/663</a></p> -<p>18:12 <code>&lt;AnhVoMSFT&gt;</code> let me test it out real quick by setting the cfg['password'] key in the ds azure</p> -<p>18:12 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: so, I may be mistaken but if a password key is set on the default_user in system_info (which is what it looks like azure does), then that default password is only used if there is no top-level "password" key provided in merged cloud-config, then and the default_user specific password key is ignored</p> -<p>18:12 <code>&lt;blackboxsw&gt;</code> +1 AnhVoMSFT</p> -<p>18:13 <code>&lt;AnhVoMSFT&gt;</code> yep that worked</p> -<p>18:13 <code>&lt;AnhVoMSFT&gt;</code> it's a one liner change, I'll submit a PR asap</p> -<p>18:14 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: good. ok, I wonder if this ever worked (having the password key hung under default_user scope?)</p> -<p>18:14 <code>&lt;blackboxsw&gt;</code> as in, I wonder if there was a regression introduced with some of the is_FreeBSD restructuring</p> -<p>18:15 <code>&lt;AnhVoMSFT&gt;</code> I don't think so. customer reported this issue in cloud-init 18.5 and I repro-ed it in master</p> -<p>18:15 <code>&lt;blackboxsw&gt;</code> ok, ok. good thanks for that context</p> -<p>18:15 <code>&lt;blackboxsw&gt;</code> and checking the recent BSD change it looking completely unrelated</p> -<p>18:17 <code>&lt;blackboxsw&gt;</code> ok AnhVoMSFT when the PR is submitted. let's get that queued for this upstream 20.4 if we can</p> -<p>18:18 <code>&lt;blackboxsw&gt;</code> do folks have an opinion on whether it helps to add a custom label to active PRs that we intend to land before upstream release like 'upstream-blocker' or 'upstream-release'?</p> -<p>18:19 <code>&lt;blackboxsw&gt;</code> just for more public tracking/transparency. not sure if that's helpful or just needless process?</p> -<p>18:19 <code>&lt;blackboxsw&gt;</code> do folks have an opinion on whether it helps to add a custom label to active PRs that we intend to land before upstream release like 'upstream-blocker' or 'upstream-release'?</p> -<p>18:23 <code>&lt;AnhVoMSFT&gt;</code> I think that would be helpful, yes</p> -<p>18:25 <code>&lt;blackboxsw&gt;</code> ok, let's try it out. let's try specific 'release 20.4' and see how that feels to folks. easy enough to drop if it doesn't improve communication</p> -<p>18:30 <code>&lt;blackboxsw&gt;</code> also added pickling upgrade test validation PR</p> -<p>18:30 <code>&lt;blackboxsw&gt;</code> #link <a href="https://github.com/canonical/cloud-init/pull/659">https://github.com/canonical/cloud-init/pull/659</a></p> -<p>18:31 <code>&lt;blackboxsw&gt;</code> ok, last call for cloud-init status / office hours. Any other takers for discussion at the moment? If not I'll close out the meeting in a few mins and publish minutes.</p> -<p>18:33 <code>&lt;blackboxsw&gt;</code> my plan is still to publish to cloud-init.github.io status meetings and link it from the primary post at <a href="https://discourse.ubuntu.com/t/cloud-init-status-11-17-20/19391">https://discourse.ubuntu.com/t/cloud-init-status-11-17-20/19391</a></p> -<p>18:34 <code>&lt;blackboxsw&gt;</code> the following will list prs we hope to work toward landing this week</p> -<p>18:34 <code>&lt;blackboxsw&gt;</code> #link <a href="https://github.com/canonical/cloud-init/pulls">https://github.com/canonical/cloud-init/pulls</a>?q=is%3Apr+is%3Aopen+label%3A%22release+20.4%22</p> -<p>18:35 <code>&lt;blackboxsw&gt;</code> thanks again for the discussion and suggestions folks. Have a good one!</p> -<p>18:35 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2020-09-08T16:18:00+00:002020-09-08T16:18:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2020-09-08:/status-2020-09-08.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 08 Sep at 16:18 &mdash; 17:13 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-09-08-16.18.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-09-08-16.18.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-08-25.html#status-2020-08-25">https://cloud-init.github.io/status-2020-08-25.html#status-2020-08-25</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:21 …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 08 Sep at 16:18 &mdash; 17:13 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-09-08-16.18.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-09-08-16.18.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-08-25.html#status-2020-08-25">https://cloud-init.github.io/status-2020-08-25.html#status-2020-08-25</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:21.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:25.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://paste.ubuntu.com/p/NgqncRMG9c/">https://paste.ubuntu.com/p/NgqncRMG9c/</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:46.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1893064">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1893064</a> </li> -</ul> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 16:54.</p> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (51)</li> -<li>meetingology (3)</li> -<li>amansi26 (3)</li> -<li>ubot5 (2)</li> -</ul> -<h2>Full Log</h2> -<p>16:18 <code>&lt;blackboxsw&gt;</code> #startmeeting cloud-init status meeting</p> -<p>16:18 <code>&lt;meetingology&gt;</code> Meeting started Tue Sep 8 16:18:47 2020 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:18 <code>&lt;meetingology&gt;</code> </p> -<p>16:18 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #chairs smoser Odd_Bloke rharper falcojr lucasmoura</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> hey folks. welcome to another public cloud-init status meeting</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> disclaimer: interruptions and side conversations are welcome</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> We use this platform/channel to discuss latest and greatest cloud-init, as well as ensuring that there are a couple of upstream developers present to field questions or discussion as needed.</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> We gather here in this IRC channel every 2 weeks to discuss current development tasks and progress on cloud-init.</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> Previous meeting minutes are here;</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2020-08-25.html#status-2020-08-25">https://cloud-init.github.io/status-2020-08-25.html#status-2020-08-25</a></p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> The topics we'll cover today: Previous Actions, Recent Changes, In-progress Development, Community Charter, Office Hours (~30 mins).</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> I expect today will be short as the entire Canonical team is involved in cloud-init SRU verification for Ubuntu at the moment</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> last meeting had an action item we needed to resolve</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> bbsw add workitem to SRU release process to announce to mailinglist estimated next SRU timeframe.</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> this item can be resolved as I've added the content requested to our email template which will be sent out once this SRU completes.</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> I see no other actions from last meeting</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> The following are upstream commits landed in cloud-init's master branch:</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> #link <a href="https://paste.ubuntu.com/p/NgqncRMG9c/">https://paste.ubuntu.com/p/NgqncRMG9c/</a></p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> In the last couple of weeks we cut the upstream 20.3 release (thanks everyone for all the help there). Queued SRU uploads for ubuntu/xenial, bionic and focal release testing.</p> -<p>16:28 <code>&lt;amansi26&gt;</code> blackboxsw: metadata here will be the configdrive, if my understanding is right?</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> And added some goodness to systemd units and ordering (sort systemd cloud-init-local.service hv_kvp_daemon and systemd: add Before=shutdown.target when Conflicts=shutdown.target is</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> used )</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> thanks paride and robjo for those commits</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> amansi26: +1 you can see the metadata configured hostname from cloud-init query local-hostname I think</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> amansi26: +1 you can see the metadata configured hostname from <code>cloud-init query local-hostname</code> I think</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> amansi26: I was just starting to respond to your bug you linked too</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> I think preserve_hostname: false (which is cloud-init's default behavior ) means cloud-init will read that hostname from metadata and apply it to the system</p> -<p>16:31 <code>&lt;amansi26&gt;</code> Sure. there is another bug which I observed on a RHEL8 environment: <a href="https://bugs.launchpad.net/cloud-init/+bug/1894837">https://bugs.launchpad.net/cloud-init/+bug/1894837</a></p> -<p>16:31 <code>&lt;ubot5&gt;</code> Ubuntu bug 1894837 in cloud-init "RHEL8 ipv4 IPs not getting set" [Undecided,New]</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> amansi26: sorry cloud-init query local_hostname (# not with a hyphen)</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> checking 2nd bug</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> so amansi26 you'd like the ability to override the iface_defaults on rhel systems for NM_CONTROLLED to set True instead of false for cloud-init interfaces?</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> generally if cloud-init is rendering network configuration on an instance, it tries to avoid using network manager by default. I think it's worth requesting logs on your bug</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> those cloud-init logs can be obtained using cloud-init collect-logs (which generates a tar.gz file in the current working directory). then attach that to the bug</p> -<p>16:41 <code>&lt;amansi26&gt;</code> yes, since I was reading the documentation for RHEL8 network configuration, I found that NM_CONTROLLED = yes should be there. but we are passing the value as No. Sure I will attach the logs to the defect</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> thanks amansi26 I responded on that bug too</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> Ok, per the meeting, that wraps #recent-changes topic I believe</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> Currently the Canonical team is working hard on SRU verification so we can release cloud-init v. 20.3 to Xenial, Bionic and Focal. It looks like we are done with most major cloud verification and walking through individual verification items.</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> I believe falcojr mentioned this morning we are about 5 of 30ish verification items complete.</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> we are continuing to work this verification as our top priority</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> folks interested should subscribe to updates on our SRU bug</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1893064">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1893064</a></p> -<p>16:51 <code>&lt;ubot5&gt;</code> Ubuntu bug 1893064 in cloud-init (Ubuntu) "sru cloud-init (20.2-45 to 20.3-2) Xenial, Bionic, and Focal" [Undecided,In progress]</p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> that bug will transition to verification-complete once all verification is done</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> #topic Community Charter</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> The following topics are still topics for ongoing community development anyone new to cloud-init, or with a bit of time could easily grab one of these bitesized tasks:</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> JSON schema extensions to validate user-data before instance launch: <a href="https://bugs.launchpad.net/cloud-init/">https://bugs.launchpad.net/cloud-init/</a>?field.tag=bitesize</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> - cloudinit.net refactor into distro-specific networking subclasses cloudinit.distros.networking: <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=net-refactor</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> If anyone would like to be involved more than they currently are, please feel free to contact us here in IRC #cloud-init on Freenode or on the mailing list cloud-init@lists.launchpad.net and we can see how best we can get you "set up"</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> this time of the meeting is really just an open door for any discussions, concerns, bugs, questions or general prodding of upstream devs to make sure existing development work is unblocked where possible.</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> in absence of discussions. We actually will be focused on SRU verification tasks today.</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> each of these verification logs and scripts are pushed as pull requests to <a href="https://github.com/cloud-init/ubuntu-sru/pulls">https://github.com/cloud-init/ubuntu-sru/pulls</a></p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> ok I think that about wraps today's session. Next meeting will be in two weeks, but we'll likely see you in channel earlier.</p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2020-08-25T16:24:00+00:002020-08-25T16:24:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2020-08-25:/status-2020-08-25.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 25 Aug at 16:24 &mdash; 17:13 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-08-25-16.24.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-08-25-16.24.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io">https://cloud-init.github.io</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:27.</p> -<h3>Recent Changes</h3> -<p>The …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 25 Aug at 16:24 &mdash; 17:13 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-08-25-16.24.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-08-25-16.24.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io">https://cloud-init.github.io</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:27.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:27.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://paste.ubuntu.com/p/h2qxwKwvFw/">https://paste.ubuntu.com/p/h2qxwKwvFw/</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:35.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://wiki.ubuntu.com/CloudinitUpdates">https://wiki.ubuntu.com/CloudinitUpdates</a> </li> -</ul> -<h3>Community Charter</h3> -<p>The discussion about "Community Charter" started at 16:40.</p> -<h3>#cloud-init pull-requests <a href="https://git.io/JeVed">https://git.io/JeVed</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting Sep 8 16:15 UTC | 20.2 (Apr 26) | 20.3 (estimated Aug 19th) <a href="https://bugs.launchpad.net/cloud-init/+filebug">https://bugs.launchpad.net/cloud-init/+filebug</a></h3> -<p>The discussion about "#cloud-init pull-requests <a href="https://git.io/JeVed">https://git.io/JeVed</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting Sep 8 16:15 UTC | 20.2 (Apr 26) | 20.3 (estimated Aug 19th) <a href="https://bugs.launchpad.net/cloud-init/+filebug">https://bugs.launchpad.net/cloud-init/+filebug</a>" started at 16:48.</p> -<ul> -<li><strong>ACTION</strong>: bbsw add workitem to SRU release process to announce to mailinglist estimated next SRU timeframe</li> -</ul> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw_ (58)</li> -<li>meetingology (5)</li> -<li>AnhVoMSFT (4)</li> -<li>falcojr (1)</li> -<li>smoser (0)</li> -<li>lucasmoura (0)</li> -<li>rharper (0)</li> -</ul> -<h2>Full Log</h2> -<p>16:24 <code>&lt;blackboxsw_&gt;</code> #startmeeting cloud-init status meeting</p> -<p>16:24 <code>&lt;meetingology&gt;</code> Meeting started Tue Aug 25 16:24:27 2020 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:24 <code>&lt;meetingology&gt;</code> </p> -<p>16:24 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:24 <code>&lt;blackboxsw_&gt;</code> #chair smoser rharper falcojr lucasmoura</p> -<p>16:24 <code>&lt;meetingology&gt;</code> Current chairs: blackboxsw_ falcojr lucasmoura rharper smoser</p> -<p>16:25 <code>&lt;blackboxsw_&gt;</code> hey folks, welcome to another cloud-init bi-weekly (or bi-monthly) community status meeting</p> -<p>16:25 <code>&lt;blackboxsw_&gt;</code> or semi-monthly</p> -<p>16:26 <code>&lt;blackboxsw_&gt;</code> ... anyhow. We use this platform/channel to discuss latest and greatest cloud-init, as well as ensuring that there are a couple of upstream developers present to field questions or discussion as needed.</p> -<p>16:26 <code>&lt;blackboxsw_&gt;</code> We gather here in this IRC channel every 2 weeks to discuss current development tasks and progress on cloud-init. All questions and side-conversations welcome</p> -<p>16:26 <code>&lt;blackboxsw_&gt;</code> we keep our meeting minutes from previous meetings here:</p> -<p>16:27 <code>&lt;blackboxsw_&gt;</code> #link <a href="https://cloud-init.github.io">https://cloud-init.github.io</a></p> -<p>16:27 <code>&lt;blackboxsw_&gt;</code> The topics we'll cover today: Previous Actions, Recent Changes, In-progress Development, Community Charter, Office Hours (~30 mins).</p> -<p>16:27 <code>&lt;blackboxsw_&gt;</code> #topic Previous Actions</p> -<p>16:27 <code>&lt;blackboxsw_&gt;</code> Looks like no carryover actions from last meeting</p> -<p>16:27 <code>&lt;blackboxsw_&gt;</code> #topic Recent Changes</p> -<p>16:30 <code>&lt;blackboxsw_&gt;</code> The following changes have landed in tip of master since last meeting (08/14/20).</p> -<p>16:30 <code>&lt;blackboxsw_&gt;</code> found via git log --since 2020-08-014</p> -<p>16:30 <code>&lt;blackboxsw_&gt;</code> #link <a href="https://paste.ubuntu.com/p/h2qxwKwvFw/">https://paste.ubuntu.com/p/h2qxwKwvFw/</a></p> -<p>16:31 <code>&lt;blackboxsw_&gt;</code> things to note. we <em>JUST</em> cut 20.3 upstream release as of 20 seconds ago. Thanks a bunch James(falcojr) for getting the Azure timeout pr up to close out this upstream release.</p> -<p>16:31 <code>&lt;blackboxsw_&gt;</code> and thanks smoser, rharper and meena for all the reviews and work here.</p> -<p>16:34 <code>&lt;blackboxsw_&gt;</code> in the last couple weeks we got fixes to reduce boot timeouts for certain azure accelerated network instances, fix oracle datasource retries, handle compressed user-data on juju deployed machines in 'cloud-init query', and early boot dhclient will not attempt to run outside of the /var/tmp sandbox directory if that directory is marked no-exec</p> -<p>16:34 <code>&lt;blackboxsw_&gt;</code> thanks otubo for that noexec branch</p> -<p>16:35 <code>&lt;blackboxsw_&gt;</code> #topic In-progress Development</p> -<p>16:36 <code>&lt;blackboxsw_&gt;</code> So thanks all for the 20.3 upstream release. We will be tagging that release and pushing that tag to master just after this meeting</p> -<p>16:36 <code>&lt;blackboxsw_&gt;</code> falcojr: is our release lead for this upstream release and SRU so he'll be working through the release process work items. Thanks falcojr.</p> -<p>16:37 <code>&lt;blackboxsw_&gt;</code> -next step on the release process is to publish to Ubuntu Groovy (20.10) and then queue up a -proposed cloud-init SRU upload into xenial, bionic and focal.</p> -<p>16:37 <code>&lt;blackboxsw_&gt;</code> we will then begin the SRU testing (which we hope to keep at around ~7days)</p> -<p>16:38 <code>&lt;blackboxsw_&gt;</code> as smoser mentioned earlier. cloud-init has to follow this process to update cloud-init in stable Ubuntu releases</p> -<p>16:38 <code>&lt;blackboxsw_&gt;</code> #link <a href="https://wiki.ubuntu.com/CloudinitUpdates">https://wiki.ubuntu.com/CloudinitUpdates</a></p> -<p>16:39 <code>&lt;blackboxsw_&gt;</code> An email will be sent to the cloud-init mailinglist notifying the community about the SRU under test in the event that folks have spare cycles to pitch in on some of the verification effort</p> -<p>16:40 <code>&lt;blackboxsw_&gt;</code> also "in-progress" paride is cleaning up a bunch of automated CI-related failures and lint issues in cloud-init, so expect some branches against cloud-init on that front as well</p> -<p>16:40 <code>&lt;blackboxsw_&gt;</code> #topic Community Charter</p> -<p>16:41 <code>&lt;blackboxsw_&gt;</code> The following topics are still topics for ongoing community development anyone new to cloud-init, or with a bit of time could easily grab one of these bitesized tasks:</p> -<p>16:41 <code>&lt;blackboxsw_&gt;</code> JSON schema extensions to validate user-data before instance launch: <a href="https://bugs.launchpad.net/cloud-init/">https://bugs.launchpad.net/cloud-init/</a>?field.tag=bitesize</p> -<p>16:41 <code>&lt;blackboxsw_&gt;</code> - Datasource documentation and updates</p> -<p>16:41 <code>&lt;blackboxsw_&gt;</code> - cloudinit.net refactor into distro-specific networking subclasses cloudinit.distros.networking: <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=net-refactor</p> -<p>16:41 <code>&lt;blackboxsw_&gt;</code> As always: thank you all for bug contributions, PR submissions, triage and discussion participation.</p> -<p>16:41 <code>&lt;blackboxsw_&gt;</code> If anyone would like to be involved more than they currently are, please feel free to contact us here in IRC #cloud-init on Freenode or on the mailing list cloud-init@lists.launchpad.net and we can see how best we can get you "set up"</p> -<p>16:42 <code>&lt;blackboxsw_&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:42 <code>&lt;blackboxsw_&gt;</code> his time of the meeting is really just an open door for any discussions, concerns, bugs, questions or general prodding of upstream devs to make sure existing development work is unblocked where possible.</p> -<p>16:42 <code>&lt;blackboxsw_&gt;</code> *This time</p> -<p>16:42 <code>&lt;blackboxsw_&gt;</code> while we're at it with meeting time.... I'll set the next cloud-init status meeting date in the topic of this IRC channel</p> -<p>16:42 <code>&lt;AnhVoMSFT&gt;</code> When do you anticipate the next SRU would be?</p> -<p>16:43 <code>&lt;AnhVoMSFT&gt;</code> (after 20.3)</p> -<p>16:44 <code>&lt;blackboxsw_&gt;</code> AnhVoMSFT: thanks for the question. I hope today for 20.3, I think 20.4 will likely align with the next Ubuntu release cycle (20.10) so, October, 2020</p> -<p>16:46 <code>&lt;blackboxsw_&gt;</code> as mentioned in passing earlier, we are looking at trying to create an upstream release of cloud-init when any significant feature set has landed in tip to make release verification easier (and hopefull include less sprawling sets of broad commit streams).</p> -<p>16:46 <code>&lt;blackboxsw_&gt;</code> this ultimately may translated to 4-5 releases per year</p> -<p>16:46 <code>&lt;blackboxsw_&gt;</code> I expect a frequency of `&lt; 3 months</p> -<p>16:48 <code>&lt;blackboxsw_&gt;</code> #topic #cloud-init pull-requests <a href="https://git.io/JeVed">https://git.io/JeVed</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting Sep 8 16:15 UTC | 20.2 (Apr 26) | 20.3 (estimated Aug 19th) <a href="https://bugs.launchpad.net/cloud-init/+filebug">https://bugs.launchpad.net/cloud-init/+filebug</a></p> -<p>16:49 <code>&lt;blackboxsw_&gt;</code> next status meeting sept 8th, same time ^</p> -<p>16:49 <code>&lt;AnhVoMSFT&gt;</code> Thanks. There's some planned work for Azure's pre-provisioning v2 and will need some change in cloud-init. We're trying to get a sense of when cloud-init SRUs land so that we can communicate the timeline</p> -<p>16:52 <code>&lt;blackboxsw_&gt;</code> @AnhVoMSFT generally cadence has been ~3 months between SRUs, I think we'd like to see a slightly higher frequency than that because our last SRU was so costly. but I think expectation for this pass is likely 10/15/2020</p> -<p>16:53 <code>&lt;blackboxsw_&gt;</code> also, if we are looking to test features in Ubuntu Groovy 20.10 images, they don't require an SRU, so upload to that development release are possible any time (we could do that as frequently as weekly if need be)</p> -<p>16:56 <code>&lt;AnhVoMSFT&gt;</code> thanks for the clarification @blackboxsw_</p> -<p>16:57 <code>&lt;blackboxsw_&gt;</code> so as of today, I expect we'll have an SRU in October and likely something beginning of Jan</p> -<p>16:57 <code>&lt;blackboxsw_&gt;</code> I'll take an action for us to communicate via mailinglist the next estimated SRU once this SRU for 20.3 closes out</p> -<p>16:59 <code>&lt;blackboxsw_&gt;</code> #action bbsw add workitem to SRU release process to announce to mailinglist estimated next SRU timeframe</p> -<p>16:59 * meetingology bbsw add workitem to SRU release process to announce to mailinglist estimated next SRU timeframe</p> -<p>16:59 <code>&lt;blackboxsw_&gt;</code> and again we hope to have 20.3 SRU complete by next week</p> -<p>16:59 <code>&lt;blackboxsw_&gt;</code> complete, as in publish the 20.3 SRU for next week into Ubuntu xenial and later</p> -<p>17:00 <code>&lt;blackboxsw_&gt;</code> I expect today we publish tip of master (20.3) into Ubuntu Groovy (20.10) so expect to see it in your friendly neighborhood ubuntu cloud-images in the next day or two</p> -<p>17:04 <code>&lt;blackboxsw_&gt;</code> falcojr: I just annotated tag 20.3 and pushed to upstream</p> -<p>17:04 <code>&lt;blackboxsw_&gt;</code> so we have a signed tag</p> -<p>17:04 <code>&lt;blackboxsw_&gt;</code> falcojr: so next task is <a href="https://trello.com/c/KxShylli/14-upload-source-tarball-to-launchpad">https://trello.com/c/KxShylli/14-upload-source-tarball-to-launchpad</a></p> -<p>17:05 <code>&lt;falcojr&gt;</code> Cool, I can jump on that</p> -<p>17:12 <code>&lt;blackboxsw_&gt;</code> ok I think we'll wrap up the status meeting. Thanks all for tuning in!</p> -<p>17:13 <code>&lt;blackboxsw_&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2020-07-28T16:55:00+00:002020-07-28T16:55:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2020-07-28:/status-2020-07-28.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 28 Jul at 16:55 &mdash; 17:56 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-07-28-16.55.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-07-28-16.55.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-07-14.html#status-2020-07-14">https://cloud-init.github.io/status-2020-07-14.html#status-2020-07-14</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:58 …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 28 Jul at 16:55 &mdash; 17:56 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-07-28-16.55.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-07-28-16.55.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-07-14.html#status-2020-07-14">https://cloud-init.github.io/status-2020-07-14.html#status-2020-07-14</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:58.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 17:00.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://paste.ubuntu.com/p/RjZcwtk6Hd/">https://paste.ubuntu.com/p/RjZcwtk6Hd/</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 17:05.</p> -<h3>Community Charter</h3> -<p>The discussion about "Community Charter" started at 17:11.</p> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 17:15.</p> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw_ (38)</li> -<li>meetingology (4)</li> -<li>rharper (0)</li> -<li>Odd_Bloke (0)</li> -<li>smoser (0)</li> -</ul> -<h2>Full Log</h2> -<p>16:55 <code>&lt;blackboxsw_&gt;</code> #startmeeting cloud-init status meeting</p> -<p>16:55 <code>&lt;meetingology&gt;</code> Meeting started Tue Jul 28 16:55:17 2020 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:55 <code>&lt;meetingology&gt;</code> </p> -<p>16:55 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:56 <code>&lt;blackboxsw_&gt;</code> community notice: time for another bi-weekly (or semi-monthly if you prefer) cloud-init community status meeting</p> -<p>16:56 <code>&lt;blackboxsw_&gt;</code> #chair Odd_Bloke smoser rharper</p> -<p>16:56 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw_ rharper smoser</p> -<p>16:57 <code>&lt;blackboxsw_&gt;</code> Hello folks, cloud-init community status roundup. We gather here in this IRC channel every 2 weeks to discuss current development tasks and progress on cloud-init.</p> -<p>16:57 <code>&lt;blackboxsw_&gt;</code> All questions. side-conversations and interruptions are welcome</p> -<p>16:58 <code>&lt;blackboxsw_&gt;</code> Last meeting minutes live here</p> -<p>16:58 <code>&lt;blackboxsw_&gt;</code> #link <a href="https://cloud-init.github.io/status-2020-07-14.html#status-2020-07-14">https://cloud-init.github.io/status-2020-07-14.html#status-2020-07-14</a></p> -<p>16:58 <code>&lt;blackboxsw_&gt;</code> he topics we'll cover today: Previous Actions, Recent Changes, In-progress Development, Community Charter, Office Hours (~30 mins).</p> -<p>16:58 <code>&lt;blackboxsw_&gt;</code> #topic Previous Actions</p> -<p>16:58 <code>&lt;blackboxsw_&gt;</code> None found in meeting minutes from last session.</p> -<p>16:59 * blackboxsw_ sets the topic for next meeting.</p> -<p>16:59 <code>&lt;blackboxsw_&gt;</code> +2 weeks from now</p> -<p>16:59 <code>&lt;blackboxsw_&gt;</code> August 11th 16:15 UTC</p> -<p>17:00 <code>&lt;blackboxsw_&gt;</code> #topic Recent Changes</p> -<p>17:00 <code>&lt;blackboxsw_&gt;</code> The following commits have been landed on master of upstream branch since last meeting: found via git log --since 2020-07-14</p> -<p>17:01 <code>&lt;blackboxsw_&gt;</code> #link <a href="https://paste.ubuntu.com/p/RjZcwtk6Hd/">https://paste.ubuntu.com/p/RjZcwtk6Hd/</a></p> -<p>17:02 <code>&lt;blackboxsw_&gt;</code> features of note:</p> -<p>17:02 <code>&lt;blackboxsw_&gt;</code> - azure: avoid bouncing hostname if set hostname fails</p> -<p>17:03 <code>&lt;blackboxsw_&gt;</code> - vmware: new defaults for post customization script overrides on vCloud</p> -<p>17:04 <code>&lt;blackboxsw_&gt;</code> - azure ValueError raised if JsonDecodeErrors is not available when parsing metadata</p> -<p>17:05 <code>&lt;blackboxsw_&gt;</code> Thanks Goneri otubo anhVo and dermotbradley for community contributions this round</p> -<p>17:05 <code>&lt;blackboxsw_&gt;</code> #topic In-progress Development</p> -<p>17:09 <code>&lt;blackboxsw_&gt;</code> Current projects for cloud-init are leading us to additional features:</p> -<p>17:10 <code>&lt;blackboxsw_&gt;</code> - network device hot plug support for cloud-init post-boot</p> -<p>17:10 <code>&lt;blackboxsw_&gt;</code> - better integration testing on other clouds, Oracle support</p> -<p>17:11 <code>&lt;blackboxsw_&gt;</code> - extended json schema validation and publishing full static schema versions for external tools</p> -<p>17:11 <code>&lt;blackboxsw_&gt;</code> #topic Community Charter</p> -<p>17:12 <code>&lt;blackboxsw_&gt;</code> The following topics are still topics for ongoing community development:</p> -<p>17:13 <code>&lt;blackboxsw_&gt;</code> - JSON schema extensions to validate user-data before instance launch: <a href="https://bugs.launchpad.net/cloud-init/">https://bugs.launchpad.net/cloud-init/</a>?field.tag=bitesize</p> -<p>17:13 <code>&lt;blackboxsw_&gt;</code> - Datasource documentation and updates</p> -<p>17:14 <code>&lt;blackboxsw_&gt;</code> - cloudinit.net refactor into distro-specific networking subclasses cloudinit.distros.networking: <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=net-refactor</p> -<p>17:15 <code>&lt;blackboxsw_&gt;</code> As always: thank you all for bug contributions, PR submissions, triage and discussion participation.</p> -<p>17:15 <code>&lt;blackboxsw_&gt;</code> If anyone would like to be involved more than they currently are, please feel free to contact us here in IRC #cloud-init on Freenode or on the mailing list cloud-init@lists.launchpad.net and we can see how best we can get you "set up"</p> -<p>17:15 <code>&lt;blackboxsw_&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>17:17 <code>&lt;blackboxsw_&gt;</code> This time of the meeting is really just an open door for any discussions, concerns, bugs, questions or general prodding of upstream devs to make sure existing development work is unblocked where possible.</p> -<p>17:17 <code>&lt;blackboxsw_&gt;</code> In the absence of discussions, review of existing PRs is addressed.</p> -<p>17:56 <code>&lt;blackboxsw_&gt;</code> Thanks for tuning in folks. have a good one!</p> -<p>17:56 <code>&lt;blackboxsw_&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2020-07-14T16:52:00+00:002020-07-14T16:52:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2020-07-14:/status-2020-07-14.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 14 Jul at 16:52 &mdash; 17:50 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-07-14-16.52.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-07-14-16.52.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-06-30.html#status-2020-06-30">https://cloud-init.github.io/status-2020-06-30.html#status-2020-06-30</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:55 …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 14 Jul at 16:52 &mdash; 17:50 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-07-14-16.52.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-07-14-16.52.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-06-30.html#status-2020-06-30">https://cloud-init.github.io/status-2020-06-30.html#status-2020-06-30</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:55.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:56.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://paste.ubuntu.com/p/6Fn5jy8t46/">https://paste.ubuntu.com/p/6Fn5jy8t46/</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 17:01.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018</a> </li> -</ul> -<h3>Community Charter</h3> -<p>The discussion about "Community Charter" started at 17:08.</p> -<ul> -<li><strong>LINK</strong>: k <a href="https://bugs.launchpad.net/cloud-init/">https://bugs.launchpad.net/cloud-init/</a>?field.tag=bitesize</li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=net-refactor </li> -<li><strong>LINK</strong>: <a href="https://cloudinit.readthedocs.io/en/latest/topics/hacking.html#ongoing-refactors">https://cloudinit.readthedocs.io/en/latest/topics/hacking.html#ongoing-refactors</a> </li> -</ul> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 17:13.</p> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (52)</li> -<li>ubot5 (5)</li> -<li>meetingology (4)</li> -<li>AnhVoMSFT (2)</li> -<li>Odd_Bloke (2)</li> -<li>smoser (0)</li> -<li>rharper (0)</li> -</ul> -<h2>Full Log</h2> -<p>16:52 <code>&lt;blackboxsw&gt;</code> #startmeeting cloud-init status meeting</p> -<p>16:52 <code>&lt;meetingology&gt;</code> Meeting started Tue Jul 14 16:52:35 2020 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:52 <code>&lt;meetingology&gt;</code> </p> -<p>16:52 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:52 <code>&lt;AnhVoMSFT&gt;</code> nvm</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> heh.</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> let's do it since we have an active attendee.</p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> i'll make it snappy today</p> -<p>16:53 <code>&lt;AnhVoMSFT&gt;</code> sounds good</p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> community notice: time for another bi-weekly (or semi-monthly if you prefer) cloud-init community status meeting</p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> #chair rharper Odd_Bloke smoser</p> -<p>16:53 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw rharper smoser</p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> welcome to another round of cloud-init upstream updates and discussion. We use this meeting as a time to gather to discuss current development of cloud-init, ask and answer questions, and generally expedite development be unblocking devs. All questions. side-conversations and interruptions are welcome</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> first order of bizzzznesss. setting the meeting for next time</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> +2 weeks from today</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> July 28th same time (minus 30 mins)</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> previous meeting minutes are here:</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2020-06-30.html#status-2020-06-30">https://cloud-init.github.io/status-2020-06-30.html#status-2020-06-30</a></p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> The topics we'll cover today: Previous Actions, Recent Changes, In-progress Development, Community Charter, Office Hours (~30 mins).</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> none seen last session. so we can jump to the next topic</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> The following commits have been landed on master of upstream branch since last meeting: found via git log --since 2020-06-30</p> -<p>16:57 <code>&lt;blackboxsw&gt;</code> #link <a href="https://paste.ubuntu.com/p/6Fn5jy8t46/">https://paste.ubuntu.com/p/6Fn5jy8t46/</a></p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> a bit of cleanup and test coverage work and CI fixups for lxd integratin testing in those commits.</p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> Of note:</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> a fix for (LP: #1456277) thx lucas</p> -<p>16:59 <code>&lt;ubot5&gt;</code> Launchpad bug 1456277 in cloud-init "cloud-init searches for ec2 mirrors regardless of what cloud its on" [High,Fix committed] <a href="https://launchpad.net/bugs/1456277">https://launchpad.net/bugs/1456277</a></p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> a fix for (LP: #1884619) part of the cloudinit.net refactor for thx Odd_Bloke</p> -<p>16:59 <code>&lt;ubot5&gt;</code> Launchpad bug 1884619 in cloud-init "cloudinit.net refactor: is_physical" [Low,Fix committed] <a href="https://launchpad.net/bugs/1884619">https://launchpad.net/bugs/1884619</a></p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> and (LP: #1886531) fix for missing /etc/fstab file path thx rharper</p> -<p>16:59 <code>&lt;ubot5&gt;</code> Launchpad bug 1886531 in cloud-init "cloud-init status broken in groovy lxd containers" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1886531">https://launchpad.net/bugs/1886531</a></p> -<p>17:00 <code>&lt;blackboxsw&gt;</code> and thanks paride for fixing our CI tests for lxd-based targets</p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> I think that about wraps recent-changes.</p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> I was hoping today we'd be able to finally say cloud-init 20.2 has published and released to Ubuntu Xenial. Bionic, Eoan and Focal. All testing is complete, we have unblocked any of this process on our side and we are awaiting an SRU team representative to review and release the bits into Ubuntu proper.</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> We pinged yesterday and a few hour ago again to get this SRU reviewed and released. Expectation is that it will be released to all Ubuntu series today/tonight, so I'd expect that cloud images see that update in the next day or two.</p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> for those watching at home, the folowing bug will be closed as fix-released once cloud-init SRU is published.</p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018</a></p> -<p>17:04 <code>&lt;ubot5&gt;</code> Ubuntu bug 1881018 in cloud-init (Ubuntu) "sru cloud-init (19.4.33 to 20.2-45) Xenial, Bionic, Eoan and Focal" [Undecided,In progress]</p> -<p>17:06 <code>&lt;blackboxsw&gt;</code> for context, this was a beast of an SRU (as upstream waited too long (~6 months) between to get the SRUs, which involved more verification and complexity. We will make sure to avoid some of this complexity in the future by more frequent SRUs and more requests for community validation I expect.</p> -<p>17:07 <code>&lt;blackboxsw&gt;</code> Also, expect that when this SRU is published, and email will be sent to cloud-init@lists.launchpad.net and a discourse post as well as a "community-notice:" banned comment</p> -<p>17:08 <code>&lt;blackboxsw&gt;</code> #topic Community Charter</p> -<p>17:08 <code>&lt;blackboxsw&gt;</code> Community driven development is what helps keep cloud-init active, so that you all for your contributions ( PR reviews, bugs, PR development, discussion etc).</p> -<p>17:09 <code>&lt;blackboxsw&gt;</code> we have a number of general goals we continue to work toward:</p> -<p>17:10 <code>&lt;blackboxsw&gt;</code> - json schema coverage of cloudinit.config.cc_* modules for better error reporting on malformed user-data</p> -<p>17:10 <code>&lt;blackboxsw&gt;</code> - datasource documentation updates and content creation needs</p> -<p>17:10 <code>&lt;blackboxsw&gt;</code> - cloudinit.net refactor into distro-specific networking subclasses cloudinit.distros.networking</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> Bugs associated with that work are available for anyone to own</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> #link k <a href="https://bugs.launchpad.net/cloud-init/">https://bugs.launchpad.net/cloud-init/</a>?field.tag=bitesize</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=net-refactor</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> And details docs on existing refactor are available here</p> -<p>17:12 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloudinit.readthedocs.io/en/latest/topics/hacking.html#ongoing-refactors">https://cloudinit.readthedocs.io/en/latest/topics/hacking.html#ongoing-refactors</a></p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> If anyone would like to be involved more than they currently are, please feel free to contact us here in IRC #cloud-init on Freenode or on the mailing list cloud-init@lists.launchpad.net and we can see how best we can get you "set up"</p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> This 'section' of the meeting is a time where a couple of upstream devs will be available in channel for any discussions, questions, bug work or PR reviews.</p> -<p>17:14 <code>&lt;blackboxsw&gt;</code> any topics, bugs, PRs or concerns or rotten fruit to throw are all welcome :). In the absence of dicussion, cloud-init PR reviews are prioritized</p> -<p>17:18 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: can I merge the following as your squashmerge commit message for PR <a href="https://github.com/canonical/cloud-init/pull/466">https://github.com/canonical/cloud-init/pull/466</a> <a href="https://paste.ubuntu.com/p/ZRdq4bYWG7/">https://paste.ubuntu.com/p/ZRdq4bYWG7/</a> I think it fixed LP: #1884626</p> -<p>17:18 <code>&lt;ubot5&gt;</code> Launchpad bug 1884626 in cloud-init "cloudinit.net refactor: wait_for_physdevs" [Low,In progress] <a href="https://launchpad.net/bugs/1884626">https://launchpad.net/bugs/1884626</a></p> -<p>17:31 <code>&lt;Odd_Bloke&gt;</code> blackboxsw: You cannot (because I just did ;).</p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> :sad trombone:</p> -<p>17:43 <code>&lt;Odd_Bloke&gt;</code> I just reran the RTD doc build and it passed this time (for anyone else who just got that failure email).</p> -<p>17:50 <code>&lt;blackboxsw&gt;</code> Ok I think that about wraps the status meeting</p> -<p>17:50 <code>&lt;blackboxsw&gt;</code> thanks for tuning in folks</p> -<p>17:50 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2020-06-30T16:22:00+00:002020-06-30T16:22:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2020-06-30:/status-2020-06-30.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 30 Jun at 16:22 &mdash; 17:51 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-06-30-16.22.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-06-30-16.22.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-06-16.html#status-2020-06-16">https://cloud-init.github.io/status-2020-06-16.html#status-2020-06-16</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:28 …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 30 Jun at 16:22 &mdash; 17:51 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-06-30-16.22.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-06-30-16.22.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-06-16.html#status-2020-06-16">https://cloud-init.github.io/status-2020-06-16.html#status-2020-06-16</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:28.</p> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:31.</p> -<ul> -<li><strong>LINK</strong>: ACTION: mailing list email requesting comment/concerns about a refactor of startup services</li> -<li><strong>LINK</strong>: <a href="https://paste.ubuntu.com/p/fSvwRks86z/">https://paste.ubuntu.com/p/fSvwRks86z/</a> </li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:34.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloudinit.readthedocs.io/en/latest/topics/hacking.html#ongoing-refactors">https://cloudinit.readthedocs.io/en/latest/topics/hacking.html#ongoing-refactors</a> </li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=net-refactor </li> -<li><strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pull/457">https://github.com/canonical/cloud-init/pull/457</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:49.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018</a> </li> -</ul> -<h3>community charter</h3> -<p>The discussion about "community charter" started at 17:02.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/">https://bugs.launchpad.net/cloud-init/</a>?field.tag=bitesize </li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=net-refactor </li> -</ul> -<h3>Office Hours (~20 mins)</h3> -<p>The discussion about "Office Hours (~20 mins)" started at 17:08.</p> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (73)</li> -<li>meetingology (4)</li> -<li>ubot5 (1)</li> -<li>rharper (1)</li> -<li>smoser (0)</li> -<li>Odd_Bloke (0)</li> -</ul> -<h2>Full Log</h2> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #startmeeting cloud-init status meeting</p> -<p>16:22 <code>&lt;meetingology&gt;</code> Meeting started Tue Jun 30 16:22:42 2020 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:22 <code>&lt;meetingology&gt;</code> </p> -<p>16:22 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> community notice: time for another bi-weekly (or semi-monthly if you prefer) cloud-init community status meeting</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> #chair smoser rharper Odd_Bloke</p> -<p>16:24 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw rharper smoser</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> welcome to another round of cloud-init upstream updates and discussion. We use this meeting as a time to gather to discuss current development of cloud-init, ask and answer questions, and generally expedite development be unblocking devs. All questions. side-conversations and interruptions are welcome</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> last meeting minutes are at the link below</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2020-06-16.html#status-2020-06-16">https://cloud-init.github.io/status-2020-06-16.html#status-2020-06-16</a></p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> turns out I didn't update the topic for the next meeting time last session. Let's do that now</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> +2 weeks from now, same time</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> July 14th, same UTC time</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> now that that's out of the way, we typically cover the following topics.</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> Previous Actions, Recent Changes, In-progress Development, Community Charter, Office Hours (~30 mins).</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> additionally today, I'll discuss the current cloud-init SRU</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> topic #1. our previous meeting minutes logged two actions:</p> -<p>16:28 * blackboxsw file feature bug about refactoring startup services</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> I think in further discussion during last meeting, we talked with Odd_Bloke and meena and determined that we can't actually refactor startup services to live in the distro specifically, because these startup service templates actually get determined at cloud-init generator time (before distribution is determined in cloud-init's python code) so trying to specialize startup script content generation in the distro</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> python classes in cloud-init is too late</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> so this action is tabled as /wont-fix</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> that follows as well with the other ACTION: mailing list email requesting comment/concerns about a refactor of startup services</p> -<p>16:31 * blackboxsw isn't sure how to close out actions in meetingology syntax/cmds</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> The following is the set of commits landed in 'master' of cloud-init upstream repo: found with git log --since 06-20-2020</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> #link ACTION: mailing list email requesting comment/concerns about a refactor of startup services</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> #link <a href="https://paste.ubuntu.com/p/fSvwRks86z/">https://paste.ubuntu.com/p/fSvwRks86z/</a></p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> heh paste error</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:34 * blackboxsw sets appropriate topic for this section</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> so recently Odd_Bloke and a number of BSD folks (meena igalic etc) have gone through a number of discussions and design regarding a refactor of cloudinit.net functions to a cloudinit.distro.networking module as most network-related functionality is highly distro-dependent</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: created an overview of this current refactor work and published it to readthedocs</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloudinit.readthedocs.io/en/latest/topics/hacking.html#ongoing-refactors">https://cloudinit.readthedocs.io/en/latest/topics/hacking.html#ongoing-refactors</a></p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> This has been a big effort to get organized and started so many thanks for all those paricipating in this discussion, development and reviews.</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> there are many, functions that need to be refactored from cloudinit.net into the distribution-specialized cloudinit.distro.networking classes.</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> It is work that can be easily done in parallel and there is a tag used to classify each refactor as a "net-refactor" bug in launchpad</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=net-refactor</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> community notice: we encourage anyone interested in refactoring cloud-init networking functionality to grab and work any of those net-refactor bugs</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> there are a couple of example PRs up that give a good idea of how to get started</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> #link <a href="https://github.com/canonical/cloud-init/pull/457">https://github.com/canonical/cloud-init/pull/457</a></p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> and I can't seem to find the other at the moment.</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> besides net-refactor content landing, there have been fixes to Hetzner and RbxCloud datasources, redhat's systemd generator templates, Centos copr build fixes to help RPM build runs and Azure datasource logging. Thanks smoser, paride Moustafa and otubo Adam Dobrawy for contributions this round</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> Generally the last two weeks have been sunk into upstream testing and validation of cloud-init for SRU (Stable release Update) into Ubuntu Xenial Bionic, Eoan and Focal.</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> 3 to 5 of us have been on verification tasks on various clouds for all Ubuntu releases targeted and all features which affect ubuntu.</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> A thousand thanks rharper Odd_Bloke factor lucasmoura and xiaofeng for working through and validating some of these SRU tasks.</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> Our job is done, and we are awaiting feedback from an automation CI from Canonical solutions QA at the moment which runs through a ton of Openstack networking customer-configurations. It has been in the test queue for a week, and I just saw a successful run from that test harness this morning. That team has told us it looks for 3 successful runs to "pass" so I expect that pass to come shortly as the test runs</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> are currently inprogress.</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> as soon as this test passes we will mark the SRU bug verified and the SRU team will publish bits of cloud-init.</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018</a></p> -<p>16:55 <code>&lt;ubot5&gt;</code> Ubuntu bug 1881018 in cloud-init (Ubuntu) "sru cloud-init (19.4.33 to 20.2-45) Xenial, Bionic, Eoan and Focal" [Undecided,In progress]</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> This SRU has taken about 1+ week longer than normal verification because we hadn't SRU'd cloud-init in around 6 months, so there was a lot more content to verify.</p> -<p>16:57 <code>&lt;blackboxsw&gt;</code> Hopefully additional SRUs will be more frequent and less heavy-weight. We are looking into reducing the overhead on this process and will pitch ideas to the cloud-init mailinglist for input</p> -<p>16:57 <code>&lt;blackboxsw&gt;</code> Beyond SRU work, the following other work is in progress:</p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> * net-refactor formerly mentioned</p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> * falcojr into Oracle integration test harness</p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> * extending json schema validation for remaining cloud-config modules for better error reporting around invalid user-data</p> -<p>17:00 <code>&lt;blackboxsw&gt;</code> Long term work: cloud-init standalone daemon to improve startup time by avoiding reloading python across each cloud-int boot stage, initial networking hot-plug support to which datasources could "opt-in"</p> -<p>17:01 <code>&lt;rharper&gt;</code> blackboxsw: =)</p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> I think that about wraps this topic.</p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> yeah rharper, we've got it on our roadmap. We'd love to see that get in this round.</p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> #topic community charter</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> We have a couple of general themes of features we are working toward as a community this year:</p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> * json schema additions for cloudinit.config.cc_* modules to improve user-facing errors on invalid user-data</p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> * datasource documentation improvements, updates and corrections</p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> * cloudinit.net-refactor work</p> -<p>17:05 <code>&lt;blackboxsw&gt;</code> We encourage any interested developers to grab any of these work items related to these features.</p> -<p>17:06 <code>&lt;blackboxsw&gt;</code> We have two bug tags which enumerate each component of these work streams:</p> -<p>17:07 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/">https://bugs.launchpad.net/cloud-init/</a>?field.tag=bitesize</p> -<p>17:07 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=net-refactor</p> -<p>17:08 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (~20 mins)</p> -<p>17:08 <code>&lt;blackboxsw&gt;</code> This 'section' of the meeting is a time where a couple of upstream devs will be available in channel for any discussions, questions, bug work or PR reviews.</p> -<p>17:08 <code>&lt;blackboxsw&gt;</code> I think I spent most of the time typing, but will hit the review queue in the absence of any other discussion</p> -<p>17:17 <code>&lt;blackboxsw&gt;</code> merged <a href="https://github.com/canonical/cloud-init/pull/461">https://github.com/canonical/cloud-init/pull/461</a></p> -<p>17:51 <code>&lt;blackboxsw&gt;</code> lucasmoura: one minor change request and description update on the PR requested <a href="https://github.com/canonical/cloud-init/pull/390#pullrequestreview-440241947">https://github.com/canonical/cloud-init/pull/390#pullrequestreview-440241947</a></p> -<p>17:51 <code>&lt;blackboxsw&gt;</code> then we can land this one</p> -<p>17:51 <code>&lt;blackboxsw&gt;</code> ok folks, thanks for checking into the cloud-init status meeting. See you in 2 weeks.</p> -<p>17:51 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2020-06-16T16:21:00+00:002020-06-16T16:21:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2020-06-16:/status-2020-06-16.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 16 Jun at 16:21 &mdash; 17:58 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-06-16-16.21.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-06-16-16.21.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:24.</p> -<h3>In-progress Development</h3> -<p>The …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 16 Jun at 16:21 &mdash; 17:58 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-06-16-16.21.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-06-16-16.21.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:24.</p> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:32.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018</a> </li> -<li><strong>LINK</strong>: </li> -<li><strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pull/391">https://github.com/canonical/cloud-init/pull/391</a> </li> -<li><strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pull/416#issuecomment-640032968">https://github.com/canonical/cloud-init/pull/416#issuecomment-640032968</a> </li> -<li><strong>ACTION</strong>: file feature bug about refactoring startup services</li> -<li><strong>ACTION</strong>: mailing list email requesting comment/concerns about a refactor of startup services</li> -</ul> -<h3>community charter</h3> -<p>The discussion about "community charter" started at 16:54.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/">https://bugs.launchpad.net/cloud-init/</a>?field.tag=bitezise </li> -</ul> -<h3>Office Hours (~next 30 minutes)</h3> -<p>The discussion about "Office Hours (~next 30 minutes)" started at 16:59.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_puppet.py#L106">https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_puppet.py#L106</a> could this be entirely puppet specific, and no other module does this dance?</li> -<li><strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/blob/master/cloudinit/reporting/events.py#L84">https://github.com/canonical/cloud-init/blob/master/cloudinit/reporting/events.py#L84</a> </li> -<li><strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_rsyslog.py#L210">https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_rsyslog.py#L210</a> one more</li> -</ul> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (61)</li> -<li>meena (6)</li> -<li>meetingology (6)</li> -<li>AnhVoMSFT (2)</li> -<li>ubot5 (1)</li> -<li>cyberpear (1)</li> -<li>Odd_Bloke (1)</li> -<li>smoser (0)</li> -<li>rharper (0)</li> -</ul> -<h2>Full Log</h2> -<p>16:21 <code>&lt;blackboxsw&gt;</code> #startmeeting cloud-init status meeting</p> -<p>16:21 <code>&lt;meetingology&gt;</code> Meeting started Tue Jun 16 16:21:42 2020 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:21 <code>&lt;meetingology&gt;</code> </p> -<p>16:21 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #chair smoser Odd_Bloke rharper</p> -<p>16:22 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw rharper smoser</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> Welcome to the bi-weekly cloud-init status meeting. A place to chat about upstream cloud-init activity/</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> his meeting is a welcome place for interruptions, questions, requests and unrelated discussions at any point.</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> <em>this</em></p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> previous meeting minutes are stored on github</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> The topics we generally cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Office Hours (~30 mins).</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> From the previous meeting we captured no actions, so I'll jump into the next topic</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> the following are commits merged into cloud-init's upstream master branch: <a href="https://paste.ubuntu.com/p/WdsZXbwwWd/">https://paste.ubuntu.com/p/WdsZXbwwWd/</a></p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> found via git log --since 06-02-2020</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> notable changes: util.runparts and subp out of util into subp.py, there are a couple of branches related to improved vmware support, and resolving keyerror issues for users providing network configuration with bridges.</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> also upstream travis CI is now using the commercial travis-ci.com instead of travis-ci-org which should give us better throughput on test runs.</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> community notice: if any PRs created &gt;` 1 week ago have problems with unresolved travis ci runs marked 'in progress' those PRs will likely need to be closed and re-submitted due to the shift in travis-ci endpoints.</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> Upstream devs are currently working our way through Ubuntu StableReleaseUpdate (SRU) validation to release cloud-init version 20.2.45 to Ubuntu Xenial, Bionic, Eoan and Focal. Thanks falcojr lucasmoura and Odd_Bloke for all the help generating test cases and reviewing SRU-related content.</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> We are about halfway through out testing of this release of cloud-init and expect to be able to wrap this up before next week.</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> To track this release, anyone can subscribe to the SRU process bug</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018</a></p> -<p>16:35 <code>&lt;ubot5&gt;</code> Ubuntu bug 1881018 in cloud-init (Ubuntu) "sru cloud-init (19.4.33 to 20.2-45) Xenial, Bionic, Eoan and Focal" [Undecided,In progress]</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> that bug will go to Fix Released when our upload to <code>&lt;ubuntu-release&gt;</code>-updates apt pocket is published</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> Beyond SRU, there is a significant refactor of cloudinit.net* module to define a clear API and push distro-specific content into the distro modules.</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> #link</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> #link <a href="https://github.com/canonical/cloud-init/pull/391">https://github.com/canonical/cloud-init/pull/391</a></p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> Thanks Odd_Bloke for driving that refactor. Those interested should check out the above PR</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> I think that about wraps it.</p> -<p>16:40 <code>&lt;meena&gt;</code> during the util.subp refactor i suggested also looking into centralising service enabling and (re) starting</p> -<p>16:41 <code>&lt;meena&gt;</code> but we kinda glossed over that because of the net refactor</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> meena: good chance to bring that up: let's get that comment link</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> #link <a href="https://github.com/canonical/cloud-init/pull/416#issuecomment-640032968">https://github.com/canonical/cloud-init/pull/416#issuecomment-640032968</a></p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> meena: your comment was really about re-organizing the ./systemd ./upstart top-level directories and refactoring down into the distros somehow?</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> as that startup service construct is highly distro dependent?</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> If that's the suggestion you are raising for comment, I think it sounds like a reasonable thing to consider. Each distro has it's own way of handling system service management.</p> -<p>16:47 <code>&lt;meena&gt;</code> *nod</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> given the fact that all the systemd/ startup script files are all templates, it indicates that we have a lot of distro-specific uniqueness even across various flavors of linux</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> I think that refactor would be significantly simpler to describe in a distro-level API</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> meena: maybe we file a feature bug against cloud-init so we can prioritize that work.</p> -<p>16:51 <code>&lt;meena&gt;</code> you're right. let's do that</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> we could surface that bug to the mailinglist</p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> meena: do you want to do either of those (bug or mailinglist email: subj: Refactor startup service to distro-specific Api) ?</p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> #action file feature bug about refactoring startup services</p> -<p>16:53 * meetingology file feature bug about refactoring startup services</p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> #action mailing list email requesting comment/concerns about a refactor of startup services</p> -<p>16:53 * meetingology mailing list email requesting comment/concerns about a refactor of startup services</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> I've added actions that we can track by next meeting to see if we can make progress on that discussion</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> ok next topic I think</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> #topic community charter</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> As always, any aspects of the cloud-init project is open for participation from community members.</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> We thank everyone for contributing bugs @ <a href="https://bugs.launchpad.net/cloud-init/+filebug">https://bugs.launchpad.net/cloud-init/+filebug</a>, reviewing open 'New' bugs that are filed, and reviewing pulls requests @ <a href="https://github.com/canonical/cloud-init/pulls">https://github.com/canonical/cloud-init/pulls</a></p> -<p>16:57 <code>&lt;blackboxsw&gt;</code> all reviews are welcome on any PRs that are up. and driving feature discussions are also encouraged. Thanks meena for participating on all of those fronts</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> for those just wanting to join in and contribute small pull requests there is a queue of bugs or features that should be a fairly contained set of tasks in our bitesize queue:</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/">https://bugs.launchpad.net/cloud-init/</a>?field.tag=bitezise</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (~next 30 minutes)</p> -<p>17:00 <code>&lt;blackboxsw&gt;</code> This 'section' of the meeting is a time where a couple of upstream devs will be available in channel for any discussions, questions, bug work or PR reviews.</p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> In the absence of discussion topics, reviewing the active PRs generally occurs to scrub our queue and unblock conversations.</p> -<p>17:02 * blackboxsw addresses some review comments on a CI Ubuntu daily test branch</p> -<p>17:22 <code>&lt;AnhVoMSFT&gt;</code> question: is there anyway to only target a particular reporting handler?</p> -<p>17:23 <code>&lt;AnhVoMSFT&gt;</code> Right now the Azure DS emits events to the HyperV KVP handler and they also pass through the log handler. For the most part this is fine (and useful). For some larger event message (like compressed log), it does not make sense to emit a large blob of compressed gzip + b64 to the log, is it possible to skip the log handler ?</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> hrm, good question AnhVoMSFT . looking</p> -<p>17:33 <code>&lt;Odd_Bloke&gt;</code> blackboxsw: meena: Note that the service files are selected at package generation time, not at runtime, so it's not entirely clear to me how you would integrate them into the Distro hierarchy.</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> nice suggestion Odd_Bloke</p> -<p>17:43 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: I'm not seeing any filtering config options in reporting: config for handlers. Are you saying you are looking to add compressed object writes to your kvp message message plane?</p> -<p>17:44 * cyberpear wondering if there's any collaboration with the ignition folks</p> -<p>17:46 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: I think it's be reasonable to provide a named report handler to ReportEventStack</p> -<p>17:46 <code>&lt;blackboxsw&gt;</code> and let ReportEventStack limit what handlers it can emit publish_event to</p> -<p>17:48 <code>&lt;meena&gt;</code> <a href="https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_puppet.py#L106">https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_puppet.py#L106</a> could this be entirely puppet specific, and no other module does this dance?</p> -<p>17:50 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: that'd mean I suppose that report_event would need to accept a new param to limit which handler it calls handler.publish_event for</p> -<p>17:50 <code>&lt;blackboxsw&gt;</code> <a href="https://github.com/canonical/cloud-init/blob/master/cloudinit/reporting/events.py#L84">https://github.com/canonical/cloud-init/blob/master/cloudinit/reporting/events.py#L84</a></p> -<p>17:52 <code>&lt;meena&gt;</code> <a href="https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_rsyslog.py#L210">https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_rsyslog.py#L210</a> one more</p> -<p>17:52 <code>&lt;blackboxsw&gt;</code> or maybe you are suggesting that we add the ability for an existing handler to define a set of data types that it accepts (and will silently ignore others)?</p> -<p>17:54 <code>&lt;blackboxsw&gt;</code> and here meena <a href="https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_fan.py#L55-L83">https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_fan.py#L55-L83</a></p> -<p>17:58 <code>&lt;blackboxsw&gt;</code> ok I've got to run. time to close the meeting for today. Thanks all for joining in!</p> -<p>17:58 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2020-06-02T16:21:00+00:002020-06-02T16:21:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2020-06-02:/status-2020-06-02.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 02 Jun at 16:21 &mdash; 18:08 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-06-02-16.21.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-06-02-16.21.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:24.</p> -<h3>Recent Changes</h3> -<p>The …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 02 Jun at 16:21 &mdash; 18:08 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-06-02-16.21.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-06-02-16.21.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:24.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:27.</p> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:34.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018</a> </li> -</ul> -<h3>Community Charter</h3> -<p>The discussion about "Community Charter" started at 16:47.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/">https://bugs.launchpad.net/cloud-init/</a>?field.tag=bitezise </li> -</ul> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 16:50.</p> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (76)</li> -<li>Odd_Bloke (6)</li> -<li>knaccc (5)</li> -<li>meena (5)</li> -<li>meetingology (4)</li> -<li>rharper (3)</li> -<li>ddstreet (1)</li> -<li>ubot5 (1)</li> -<li>smoser (0)</li> -</ul> -<h2>Full Log</h2> -<p>16:21 <code>&lt;blackboxsw&gt;</code> #startmeeting cloud-init status meeting</p> -<p>16:21 <code>&lt;meetingology&gt;</code> Meeting started Tue Jun 2 16:21:15 2020 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:21 <code>&lt;meetingology&gt;</code> </p> -<p>16:21 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> hi folks, time for another cloud-init upstream status meeting.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> we use this meeting to provide a venue for any cloud-init interested parties to keep up to date on current development, release-related info and expedite distributed development where possible.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> this meeting is a welcome place for interruptions, questions, requests and unrelated discussions at any point. so don't be shy :)</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #chair Odd_Bloke smoser rharper</p> -<p>16:23 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw rharper smoser</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> The topics we generally cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Office Hours (~30 mins).</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> previous meeting minutes live here (and I just saw I forgot to publish last minutes so I pushed them now)</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> nothing actionable brought up in last meeting on 05/19</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: ahh we should fix devel with those pkg drops on next upload</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> we did drop that for Xenial, Bionic Eoan and maybe focal too?</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> so an oversight for groovy</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> next topic</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> the following are commits landed in tip of master found via git log --since 05/19/2020 : <a href="https://paste.ubuntu.com/p/QFvgWhjXY9/">https://paste.ubuntu.com/p/QFvgWhjXY9/</a></p> -<p>16:28 <code>&lt;Odd_Bloke&gt;</code> blackboxsw: When you say "next upload" are you referring to the upload you're about to do, or the one after that?</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: if you'd like we can adjust the current upload so that devel, focal, bionic xenial eoan all drop those stale deps</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> I think X, B E have all dropped them</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> so maybe I re-do ubuntu/devel PR Odd_Bloke ?</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> probably good/better/correct to keep all releases on the same footing.</p> -<p>16:29 <code>&lt;Odd_Bloke&gt;</code> blackboxsw: I think it's worth doing, we've uploaded without fixing it a few times before, and we've remembered this time around.</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> yeah sounds good Odd_Bloke I'll re-do that devel PR (and make sure focal drops it too)</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> if needed</p> -<p>16:30 <code>&lt;Odd_Bloke&gt;</code> And it should just be a case of pushing a new commit to your existing branch.</p> -<p>16:30 <code>&lt;Odd_Bloke&gt;</code> Thanks!</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> +1</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> things of note in the recent commits landed. <a href="https://github.com/canonical/cloud-init/pull/358">https://github.com/canonical/cloud-init/pull/358</a> Mattew Ruffell improved cc_grub_dpkg to be more dynamic in matching disks instead of a hardcoded device list</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> thanks Matthew</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> and chef_license support <a href="https://github.com/canonical/cloud-init/commit/0919bd46bbd1b12158c369569ec1298bb000dd8a">https://github.com/canonical/cloud-init/commit/0919bd46bbd1b12158c369569ec1298bb000dd8a</a></p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> thanks bipinbachhao for the config extension there</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> a couple of new notables in flight at the moment:</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - falcojr: introduction of feature-flags for cloud-init upstream to give us a toggle to retain original behavior of #include failures on stable downstream releases. <a href="https://github.com/canonical/cloud-init/pull/367">https://github.com/canonical/cloud-init/pull/367</a> . Upstream cloud-init will fail loudly and raise an Exception if someone tries to #include a url which fails. this differs from original cloud-init behavior which was to try our best to get a system up</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> and running, even amid not-critical failures</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> per the above, if downstreams (distributiions) would like to retain a more permissive warn on #include user-data issues, a cloudinit/feature_overrides.py file would need to be introduced in the downstream</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> - Also meena and Odd_Bloke and others have been working toward a refactor of cloudinit.net modules. Dan added a doc PR to capture this approach <a href="https://github.com/canonical/cloud-init/pull/391">https://github.com/canonical/cloud-init/pull/391</a></p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> beyond that, there are a number of PRs up from lucas on json schema additions for cloudinit/config/cc_* modules to get better validation of #cloud-config user-data</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> For ubuntu proper, we have started the StableReleaseUpdate process for cloud-init to publish master into ubuntu/xenial, bionic, eoan and focal releases</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> some of these changes will add the opportunity to enable 'new' features on platforms like Azure</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> and AWS</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> Azure (xenial) will be dropping walinuxagent support</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> AWS will now surface a datasource config option apply_full_imds_network_config boolean</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> if set true in an Ec2(aws) image network configuration from cloud-init can come completely from IMDS for every connected NIC. That config will include all secondary IPv4/IPv6 addressses configured for the machine</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> Upstream has started the Ubuntu SRU process (which generally takes around 10-14 days). We plan to include every commit that has landed in tip of master as of commitish 5f7825e22241423322dbe628de1b00289cf34114</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> the bug related to this SRU work is here</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018</a></p> -<p>16:46 <code>&lt;ubot5&gt;</code> Ubuntu bug 1881018 in cloud-init (Ubuntu Focal) "sru cloud-init (19.4.33 to 20.2-30) Xenial, Bionic, Eoan and Focal" [Undecided,New]</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> #topic Community Charter</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> upstream has signed up to get as much of the json schema coverage as we can for cloudinit/config/cc*py modules since invalid #cloud-config user-data formats tends to have one of the highest incidence of errors (because writing YAML is something humans shouldn't have to do :) )</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> so we are chopping away at defining JSON schema for as many cloud config modules as possible . there are still plenty to choose from. Anyone can feel free to grab a JSON schema bug and help us with bettering cloud-init</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> bugs are filed for each config module which needs schema definition:</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/">https://bugs.launchpad.net/cloud-init/</a>?field.tag=bitezise</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> a big thanks to lucasmoura for starting to grab a number of these</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> This 'section' of the meeting is a time where a couple of upstream devs will be available in channel for any discussions, questions, bug work or PR reviews.</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> In the absence of discussions/topics here we scrub the review queue.</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> since we are mid-stream on Ubuntu SRU at the moment, I'll be addressing review comments on some of the functional 'upload' branches we've put together</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> and, let's update the topic for next IRC meeting too while we are at it</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: just pushed ubuntu/devel dropping python3-six|unittest2|nose</p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> and just re-pushed ubuntu/focal to drop python3-six</p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> oops and missed you others. reworking</p> -<p>17:12 <code>&lt;blackboxsw&gt;</code> ok re-pushed. focal and devel PRs in shape</p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> dropped the following build-deps: python3-six, python3-unittest2, python3-pep8, python3-nose, python3-pyflakes</p> -<p>17:20 <code>&lt;Odd_Bloke&gt;</code> blackboxsw: +1 on the ubuntu/devel upload.</p> -<p>17:21 <code>&lt;blackboxsw&gt;</code> whew, think we got all of the dropped deps between the two of us... thanks!</p> -<p>17:21 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: thanks focal looks good and sbuilds</p> -<p>17:21 <code>&lt;blackboxsw&gt;</code> just finished eoan and building now to test</p> -<p>17:23 <code>&lt;meena&gt;</code> what? me??</p> -<p>17:24 <code>&lt;blackboxsw&gt;</code> well yes indeedy meena, just trying to keep you highlighted as participating in the cloud-init status meeting :) you've thankfully reviewed, pushed and prodded us to talk about cloudinit.net refactor and how best to address it I think :) credit due ;)</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> community notice: upload to Ubuntu groovy of cloud-init master accepted [ubuntu/groovy-proposed] cloud-init 20.2-45-g5f7825e2-0ubuntu1 (Accepted)</p> -<p>17:30 <code>&lt;Odd_Bloke&gt;</code> blackboxsw: One issue with <a href="https://github.com/canonical/cloud-init/pull/412">https://github.com/canonical/cloud-init/pull/412</a></p> -<p>17:31 <code>&lt;meena&gt;</code> blackboxsw: i'm just waiting for Odd_Bloke to provide the basic infrastructure so i can start moving code… without that, i have to bug other projects in my … 2 hours of free time per day.</p> -<p>17:31 <code>&lt;meena&gt;</code> blackboxsw: yesterday, i tried to build an android app on my laptop and gave up after an hour.</p> -<p>17:35 <code>&lt;blackboxsw&gt;</code> nice review again Odd_Bloke, will reflect that patch to each series. as every other ubuntu/* is missing enabling various cloud datasources beyond just Rbx</p> -<p>17:54 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: rharper so Xenial is interesting for datasource config via dpkg</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> We are missing: Hetzner, IBMCloud, Oracle, and RbxCloud</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> one was an oversight on previous SRUs</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> but Oracle and IBMCloud, I'm trying to recall if there is a reason we didn't want to surface either of those datasources as configurable on Xenial</p> -<p>17:56 <code>&lt;blackboxsw&gt;</code> a little warning bell is going off in my head</p> -<p>17:56 <code>&lt;blackboxsw&gt;</code> Hetzner I thought was 'ok'</p> -<p>17:56 <code>&lt;blackboxsw&gt;</code> Oracle currently gets detected as OpenStack on Xenial.</p> -<p>17:57 <code>&lt;rharper&gt;</code> IBMCloud and Oracle are sensitive</p> -<p>17:57 <code>&lt;rharper&gt;</code> not sure about Hetzner or RbxCloud though</p> -<p>17:57 <code>&lt;blackboxsw&gt;</code> upstream Oracle datasource is 'good', but I wasn't sure if there was extra baggage associated with <em>not</em> backporting that functionality</p> -<p>17:57 <code>&lt;rharper&gt;</code> blackboxsw: I think you might want to check with CPC on those</p> -<p>17:58 <code>&lt;meena&gt;</code> Hetzner is also detected as OpenStack on FreeBSD… but… only thru cloud-init itself, not thru ds-identify</p> -<p>18:03 <code>&lt;meena&gt;</code> (i'm not sure how much of that is my fault having helped a lot with Hetzner and FreeBSD and ds-identify myself)</p> -<p>18:03 <code>&lt;knaccc&gt;</code> Odd_Bloke thanks for your reply. I managed to fix things in the end, but kinda by cheating. Now my /etc/netplan/50-cloud-init.yaml only contains the IP addresses configuration, and I make the nameservers and search domain apply in the "Global" scope (as reported by systemd-resolve --status) by simply modifying the /etc/resolv.conf file. All configuration survives reboot just fine, and I am no longer</p> -<p>18:03 <code>&lt;knaccc&gt;</code> scared that resolv.conf will be overwritten because I found a web page that said that "Note: The mode of operation of systemd-resolved is detected automatically, depending on whether /etc/resolv.conf is a symlink to the local stub DNS resolver file or contains server names." Although you said in your message that "cloud-init will regenerate /etc/netplan/50-cloud-init.yaml on each boot, so yes, you don't</p> -<p>18:03 <code>&lt;knaccc&gt;</code> want to modify that", the OVH instructions directly contradict that and tell me to edit it to add all IP addresses to my interface (see Ubuntu 18.04 section here: <a href="https://docs.ovh.com/gb/en/vps/network-ipaliasing-vps/">https://docs.ovh.com/gb/en/vps/network-ipaliasing-vps/</a>). I'm therefore very confused about why OVH seem to contradict the instructions that are in that config file, and confused as to what other location I should be editing/creating instead</p> -<p>18:06 <code>&lt;ddstreet&gt;</code> knaccc why do you want to change resolved 'Global' section?</p> -<p>18:08 <code>&lt;blackboxsw&gt;</code> heh meena not at fault :) . Just need to make sure we move cloud-platforms to a better way of detecting the right datasource when we can.</p> -<p>18:08 <code>&lt;knaccc&gt;</code> ddstreet if I put the nameservers and search domain into the /etc/netplan/50-cloud-init.yaml file, it gets ignored completely (i.e. although those configurations show up in systemd-resolve --status against that specific "link", the "Global" nameservers and lack of any search domain in that Global section are taking precedence). Therefore I had to configure nameservers and search domain at the resolv.conf</p> -<p>18:08 <code>&lt;knaccc&gt;</code> level so that it appeared in the Global section, and then suddenly everything worked for the first time</p> -<p>18:08 <code>&lt;blackboxsw&gt;</code> I should tie off our cloud-init status meeting. Thanks folks for all who've attended</p> -<p>18:08 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2020-05-19T16:18:00+00:002020-05-19T16:18:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2020-05-19:/status-2020-05-19.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 19 May at 16:18 &mdash; 18:24 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-05-19-16.18.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-05-19-16.18.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-05-05.html#status-2020-05-05">https://cloud-init.github.io/status-2020-05-05.html#status-2020-05-05</a> </p> -<h3>#cloud-init pull-requests <a href="https://git.io/JeVed">https://git.io/JeVed</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl …</a></h3><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 19 May at 16:18 &mdash; 18:24 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-05-19-16.18.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-05-19-16.18.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-05-05.html#status-2020-05-05">https://cloud-init.github.io/status-2020-05-05.html#status-2020-05-05</a> </p> -<h3>#cloud-init pull-requests <a href="https://git.io/JeVed">https://git.io/JeVed</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting June 16:15 UTC | 20.1 (Feb 18) | 20.2 (Apr 28) | <a href="https://bugs.launchpad.net/cloud-init/+filebug">https://bugs.launchpad.net/cloud-init/+filebug</a></h3> -<p>The discussion about "#cloud-init pull-requests <a href="https://git.io/JeVed">https://git.io/JeVed</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting June 16:15 UTC | 20.1 (Feb 18) | 20.2 (Apr 28) | <a href="https://bugs.launchpad.net/cloud-init/+filebug">https://bugs.launchpad.net/cloud-init/+filebug</a>" started at 16:20.</p> -<h3>#cloud-init pull-requests <a href="https://git.io/JeVed">https://git.io/JeVed</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting June 2 16:15 UTC | 20.1 (Feb 18) | 20.2 (Apr 28) | <a href="https://bugs.launchpad.net/cloud-init/+filebug">https://bugs.launchpad.net/cloud-init/+filebug</a></h3> -<p>The discussion about "#cloud-init pull-requests <a href="https://git.io/JeVed">https://git.io/JeVed</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting June 2 16:15 UTC | 20.1 (Feb 18) | 20.2 (Apr 28) | <a href="https://bugs.launchpad.net/cloud-init/+filebug">https://bugs.launchpad.net/cloud-init/+filebug</a>" started at 16:20.</p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:21.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:22.</p> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:27.</p> -<h3>Community Charter</h3> -<p>The discussion about "Community Charter" started at 16:39.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/">https://bugs.launchpad.net/cloud-init/</a>?field.tag=bitezise </li> -</ul> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 16:44.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://pastebin.com/TG4E8Dft">https://pastebin.com/TG4E8Dft</a> 19.4-33 (latest 18.04 image on Azure)</li> -</ul> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (52)</li> -<li>AnhVoMSFT (8)</li> -<li>meetingology (4)</li> -<li>meena (3)</li> -<li>Odd_Bloke (2)</li> -<li>smoser (0)</li> -<li>rharper (0)</li> -</ul> -<h2>Full Log</h2> -<p>16:18 <code>&lt;blackboxsw&gt;</code> #startmeeting cloud-init status meeting</p> -<p>16:18 <code>&lt;meetingology&gt;</code> Meeting started Tue May 19 16:18:05 2020 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:18 <code>&lt;meetingology&gt;</code> </p> -<p>16:18 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> #chair Odd_Bloke smoser rharper</p> -<p>16:18 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw rharper smoser</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> hello cloud-init, welcome to another round cloud-init status updates</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> our IRC channel topic carries the next planned status meeting for those that wish to participate. All are welcome to interject or drive converstation topics here</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> Previous meeting notes are here</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2020-05-05.html#status-2020-05-05">https://cloud-init.github.io/status-2020-05-05.html#status-2020-05-05</a></p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> and next status meeting should be in 2 weeks time.</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> looks like June 2. I'll set the topic of this irc channel to so that dropins can see a reminder for when that meeting is held</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #topic #cloud-init pull-requests <a href="https://git.io/JeVed">https://git.io/JeVed</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting June 16:15 UTC | 20.1 (Feb 18) | 20.2 (Apr 28) | <a href="https://bugs.launchpad.net/cloud-init/+filebug">https://bugs.launchpad.net/cloud-init/+filebug</a></p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #topic #cloud-init pull-requests <a href="https://git.io/JeVed">https://git.io/JeVed</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting June 2 16:15 UTC | 20.1 (Feb 18) | 20.2 (Apr 28) | <a href="https://bugs.launchpad.net/cloud-init/+filebug">https://bugs.launchpad.net/cloud-init/+filebug</a></p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> let's try that instead</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> The topics we generally cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter and Office Hours (~30 mins).</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> I'll jump through each topic, as always interjections, questions or other topics welcome</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> Nothing brought up as an action in the last meeting so we'll jump to the next topic</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> The following changes have landed in master; found via git log --since 05-05-2020 <a href="https://paste.ubuntu.com/p/d2qR8pTZNY/">https://paste.ubuntu.com/p/d2qR8pTZNY/</a></p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> there are a number of commits landed related to dropping additional py2 support from various paths as well as improving pytest fixtures (thx OddBloke) and some json schema definitions added to cc_snap and cc_apt_configure thanks lucasmoura</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> and an additional bit of work from meena to make libc discovery platform independent</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> Current themes of work for upstream include: continuing to refine a spec on cloud-init daemon mode and hot-plug support, purging python2-isms, improving pytest automation.</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> falcojr: also has a new approach for feature flag definitions/behavior in cloud-init in <a href="https://github.com/canonical/cloud-init/pull/367">https://github.com/canonical/cloud-init/pull/367</a> This should give us the ability to better codify upstream unconfiguraable cloud-init behavior which may differ on previous releases.</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> falcojr: Odd_Bloke &amp; smoser thanks for good design discussion there. anyone interested feel free to weigh in.</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> Also in-progress work is a cloud-init StableReleaseUpdate planned to publish cloud-init version 20.2 to xenial, bionic, eoan and focal.</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> This will publish latest cloud-init (after verification) to old stable releases</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> the first step before SRU is to upload latest cloud-init to Ubuntu Groovy(20.10). Once this upload is complete, we'll start the SRU process to publish to Xenial, Bionic, Eoan and Focal</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> #topic Community Charter</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> As discussed at the last cloud-init summit we targeted a couple of streams of work that are easy to work in parallel, making them prime candidates for community involvement.</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> Those streams/themes are: updating and correcting datasource documentation at <a href="https://cloudinit.readthedocs.io/en/latest/topics/datasources.html">https://cloudinit.readthedocs.io/en/latest/topics/datasources.html</a></p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> and adding jsonschema definitions to any cloudinit.config.cc_* modules</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> any of these bugs are categorized as 'bitesize' and can be searched at the following link</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/">https://bugs.launchpad.net/cloud-init/</a>?field.tag=bitezise</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> a few of us have grabbed schema definitions for a few of the cloud config modules. I think we are up to 11 modules covered (of 50). Thanks all for the progress there. We have it on our roadmap to flesh out as much as we can</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> During this part of the meeting upstream devs should have eyes on the channel for any discussion related to feature, bug or review requests.</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> In the absence of active discussions, the active review queue will be be groomed.</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> for me, I've got to read through <a href="https://github.com/canonical/cloud-init/pull/367">https://github.com/canonical/cloud-init/pull/367</a> in depth to see if I have any use-cases to add there for feature management</p> -<p>17:21 <code>&lt;blackboxsw&gt;</code> so, yeah sorry for the noise Odd_Bloke and falcojr in standup about whether this 'feature' is runtime configurable on/off. It doesn't even make sense for this #include case. Also I think the merits of falcojr's suggestion to rely on some unique environment variable to determine whether a feature is on or off can and should be encoded in cloud-init proper, instead of relying on patching when releasing to</p> -<p>17:21 <code>&lt;blackboxsw&gt;</code> ubuntu/xenial.</p> -<p>17:22 <code>&lt;blackboxsw&gt;</code> when we add a new 'feature' to cloud-init upstream. I believe we know what our expectations are for older stable releases at that time. We generally could encode those expectations (at least for ubuntu series which we maintain) that a feature should behave a certain way when we end up releasing to ubuntu/xenial. Avoiding the RELEASE_BLOCKER comment as a reminder for us to manually patch a release wouldn't be</p> -<p>17:22 <code>&lt;blackboxsw&gt;</code> necessary in these cases.</p> -<p>17:26 <code>&lt;AnhVoMSFT&gt;</code> q question: when I specify a custom data to format/partition the datadisk, it seems like the ephemeral resource disk isn't getting formatted to ext4 anymore. Is this by-design that when the customer specifies disk_setup and fs_setup for additional datadisk they need to also include the fs_setup for ephemeral0 (it seems odd because disk_setup got "merged" properly. I could see the ephemeral0</p> -<p>17:26 <code>&lt;AnhVoMSFT&gt;</code> got partitioned. Yet fs_setup isn't).</p> -<p>17:27 <code>&lt;AnhVoMSFT&gt;</code> I am not sure if this is an appropriate topic for Office Hours. I can wait :-)</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: thx for the question. so, what version of cloud-init and what's the user-data for partitioning that is isn't working as expected?</p> -<p>17:31 <code>&lt;AnhVoMSFT&gt;</code> <a href="https://pastebin.com/TG4E8Dft">https://pastebin.com/TG4E8Dft</a> 19.4-33 (latest 18.04 image on Azure)</p> -<p>17:33 <code>&lt;AnhVoMSFT&gt;</code> (paste.ubuntu has been giving me problems today - not sure if it's only me)</p> -<p>17:49 <code>&lt;meena&gt;</code> blackboxsw: no mention of my work on the net refactoring or did i miss that</p> -<p>17:53 <code>&lt;blackboxsw&gt;</code> meena: sorry, right that is a large undertaking that you've raised via your PR <a href="https://github.com/canonical/cloud-init/pull/363">https://github.com/canonical/cloud-init/pull/363</a></p> -<p>17:55 <code>&lt;meena&gt;</code> yeah, it's my: please teach my software engineering while all i do is code monkeying PR.</p> -<p>17:55 <code>&lt;meena&gt;</code> don't tell no one tho, or else they… might not.</p> -<p>17:58 <code>&lt;Odd_Bloke&gt;</code> blackboxsw: Could you comment on the PR where we're having that feature flag conversation, please?</p> -<p>17:58 <code>&lt;blackboxsw&gt;</code> Heh, generally the direction meena is going is toward distro-specific networking subclass to handle network rendering details (as most of our network rendering utility functions are highly distro-dependent</p> -<p>17:59 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: yes, I shall.</p> -<p>17:59 <code>&lt;Odd_Bloke&gt;</code> Thanks!</p> -<p>18:06 <code>&lt;blackboxsw&gt;</code> Ok, I forgot to close out the meeting.</p> -<p>18:07 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: so I see your instance is properly "waiting" for the presence of ephemeral0 resource disk. trying to get to the bottom of why formatting isn't being addressed there.</p> -<p>18:10 <code>&lt;blackboxsw&gt;</code> I see 2020-05-19 17:20:24,072 - cc_mounts.py[DEBUG]: Mapped metadata name ephemeral0 to /dev/disk/cloud/azure_resource</p> -<p>18:10 <code>&lt;blackboxsw&gt;</code> 2020-05-19 17:20:24,073 - cc_mounts.py[DEBUG]: changed default device ephemeral0 =&gt;` /dev/disk/cloud/azure_resource-part1</p> -<p>18:16 <code>&lt;AnhVoMSFT&gt;</code> @blackboxsw this is reproducing 100% of the time</p> -<p>18:17 <code>&lt;blackboxsw&gt;</code> I'm wondering AnhVoMSFT if the ephemeral0 alias needs to be used instead. something like <a href="https://paste.ubuntu.com/p/7wmMc8drZ3/">https://paste.ubuntu.com/p/7wmMc8drZ3/</a></p> -<p>18:19 <code>&lt;blackboxsw&gt;</code> I see we've done SRU testing referencing that alias instead of full resource disk path <a href="https://github.com/cloud-init/ubuntu-sru/blob/master/bugs/b59870ca.txt">https://github.com/cloud-init/ubuntu-sru/blob/master/bugs/b59870ca.txt</a></p> -<p>18:23 <code>&lt;AnhVoMSFT&gt;</code> @blackboxsw, my config is actually having an EXTRA datadisk</p> -<p>18:23 <code>&lt;AnhVoMSFT&gt;</code> so in this case the VM is deployed with an additional data disk attached to the VM</p> -<p>18:24 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2020-05-05T16:16:00+00:002020-05-05T16:16:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2020-05-05:/status-2020-05-05.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 05 May at 16:16 &mdash; 17:34 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-05-05-16.16.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-05-05-16.16.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:20.</p> -<h3>Recent Changes</h3> -<p>The …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 05 May at 16:16 &mdash; 17:34 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-05-05-16.16.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-05-05-16.16.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:20.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:20.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://paste.ubuntu.com/p/YMb2Tw3tRD/">https://paste.ubuntu.com/p/YMb2Tw3tRD/</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:26.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pulls">https://github.com/canonical/cloud-init/pulls</a> </li> -</ul> -<h3>Community Charter</h3> -<p>The discussion about "Community Charter" started at 16:30.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=bitesize </li> -</ul> -<h3>Office hours (next ~30 mins)</h3> -<p>The discussion about "Office hours (next ~30 mins)" started at 16:33.</p> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (38)</li> -<li>meetingology (4)</li> -<li>rharper (0)</li> -<li>Odd_Bloke (0)</li> -<li>smoser (0)</li> -</ul> -<h2>Full Log</h2> -<p>16:16 <code>&lt;blackboxsw&gt;</code> #startmeeting cloud-init status meeting</p> -<p>16:16 <code>&lt;meetingology&gt;</code> Meeting started Tue May 5 16:16:41 2020 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:16 <code>&lt;meetingology&gt;</code> </p> -<p>16:16 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> good morning, afternoon and evening folks. Welcome to another cloud-init status meeting.</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> #chair Odd_Bloke smoser rharper</p> -<p>16:17 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw rharper smoser</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> our IRC channel topic carries the next planned status meeting for those that wish to participate. All are welcome to interject or drive converstation topics here</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> I'll set the next status meeting topic while we are thinking about it.</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> 2 weeks from today, same time 16:15 UTC.</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> May 19th it is.</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> Previous meeting minutes live over on github</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> The topics we generally cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Upcoming Meetings, Office Hours (~30 mins).</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> Looks like no unresolved actions from last meeting</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> Below is a list of commits that have landed in tip of master: found via git log --since 2020-03-10</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #link <a href="https://paste.ubuntu.com/p/YMb2Tw3tRD/">https://paste.ubuntu.com/p/YMb2Tw3tRD/</a></p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> We've had a number of milestones since the last status meeting, Ubuntu Focal Fossa 20.04 was released on Apr 23, cloud-init upstream cut a release 20.2 as well</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> Additionally we have two new hires to the canonical ubuntu-server team that will be participating in cloud-init, curtin and ubuntu-advantage-tools projects</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> We are really excited to have some extra hands on cloud-init from lucasmoura and falcojr. So welcome gentlemen, glad to have the help.</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> They just started yesterday and are going through a bit of onboarding this week, but expect to see them around in cloud-init shortly. I believe they have both landed their first PRs to get added as a contributor to cloud-init.</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> #link <a href="https://github.com/canonical/cloud-init/pulls">https://github.com/canonical/cloud-init/pulls</a></p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> ok active review queue is really getting well maintained now that we've adopted PR assignment. Thanks for helping is land branches quickly folks.</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> Generally upstream has set a couple of long-term goals for cloud-init in the next development cycle</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - wrap up cloud-init daemon mode (to reduce boot time by loading python only once)</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - OpenStack network hotplug handling from cloud-init</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> - Potentially a new LXD datasource for handling container deployments</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> - better json schema coverage for the remaining oncovered cloud config modules.</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> #topic Community Charter</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> We continue to categorize more bitesize bugs in cloud-init.</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=bitesize</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> These bugs are themed at doc updates and json schema improvements across all of cloud-init, but we continue to seed that bug tag with items which should be easy to drop in and make a lasting impact on cloud-init</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> All cloud-init contributors are encouraged to participate in any part of the cloud-init lifecycle, from bug filing, to fixing, to release testing and PR reviews. Thanks to everyone who continues to build the cloud-init community!</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> #topic Office hours (next ~30 mins)</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> During this stage we have a some focus time on cloud-init development and community support. Any questions, concerns, reviews or request for help/triage are most welcome. We should have a couple of upstream developers with eyes on this channel.</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> In the absence of discussion, we'll groom the active PR review queue and/or work additional cloud-init dev items.</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> community-notice: Ubuntu plans to release cloud-init version 20.2 to Ubuntu's new development release 20.10 (Groovy Gorilla). We expect to start an Ubuntu StableReleaseUpdate into xenial, bionic, eoan and focal within the next 2 weeks.</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> alrighty, think that about wraps today's status meeting. Happy Cinco De Mayo folks</p> -<p>17:34 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2020-04-14T16:17:00+00:002020-04-14T16:17:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2020-04-14:/status-2020-04-14.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 14 Apr at 16:17 &mdash; 17:12 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-04-14-16.17.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-04-14-16.17.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-03-31.html#status-2020-03-31">https://cloud-init.github.io/status-2020-03-31.html#status-2020-03-31</a> </p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:23 …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 14 Apr at 16:17 &mdash; 17:12 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-04-14-16.17.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-04-14-16.17.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-03-31.html#status-2020-03-31">https://cloud-init.github.io/status-2020-03-31.html#status-2020-03-31</a> </p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:23.</p> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:27.</p> -<h3>Office hours (next ~30 mins)</h3> -<p>The discussion about "Office hours (next ~30 mins)" started at 16:34.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://github.com/CanonicalLtd/uss-tableflip/pull/45">https://github.com/CanonicalLtd/uss-tableflip/pull/45</a> I think comments are resolved</li> -</ul> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (38)</li> -<li>meetingology (6)</li> -<li>powersj (2)</li> -<li>Goneri (2)</li> -<li>otubo (1)</li> -<li>punkgeek (1)</li> -<li>rharper (1)</li> -<li>smoser (0)</li> -<li>powers (0)</li> -<li>Odd_Bloke (0)</li> -</ul> -<h2>Full Log</h2> -<p>16:17 <code>&lt;blackboxsw&gt;</code> #startmeeting cloud-init status meeting</p> -<p>16:17 <code>&lt;meetingology&gt;</code> Meeting started Tue Apr 14 16:17:46 2020 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:17 <code>&lt;meetingology&gt;</code> </p> -<p>16:17 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> hey folks, time for cloud-init community status meeting</p> -<p>16:19 <code>&lt;powersj&gt;</code> \o/</p> -<p>16:19 <code>&lt;otubo&gt;</code> Right on time :-)</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> welcome again to our bi-weekly status meeting feel free to interject comments, questions, suggestions during this status meeting. Generally it is an opportunity for upstream to provide a frequent platform communication and drop-in discussion when a couple of upstream devs are available.</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #chair Odd_Bloke smoser rharper powers</p> -<p>16:20 <code>&lt;meetingology&gt;</code> Warning: Nick not in channel: powers</p> -<p>16:20 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw powers rharper smoser</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #chair powersj</p> -<p>16:20 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw powers powersj rharper smoser</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> our IRC channel topic carries the next planned status meeting for those that wish to participate. All are welcome to interject or drive converstation topics here</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> any objections to same time on Apr 28th?</p> -<p>16:21 <code>&lt;powersj&gt;</code> nah that's a good day given we want to cut 20.2 then</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> ok topic set for next meetin</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> our last meeting minutes can be found on github at</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2020-03-31.html#status-2020-03-31">https://cloud-init.github.io/status-2020-03-31.html#status-2020-03-31</a></p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> The topics we generally cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Upcoming Meetings, Office Hours (~30 mins).</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> none listed from last meeting</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> git commits landed in tip since Mar 31: <a href="https://paste.ubuntu.com/p/VptqRBfVfJ/">https://paste.ubuntu.com/p/VptqRBfVfJ/</a> found by git log --since 03-31-2020</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> changes sport doc updates, otubo's cc_mount fix , better url handling for regions which contain underscores in their name and openbsd fixes from Goneri for passwd locks.</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> thanks for the contributions this round folks!</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> upstream is currently focused on getting in bug fixes, dropping remnants of py2 in tooling reviewing active PRs to get cloud-init in shape for the upcoming 20.2 release</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> community notice: as mentioned in the channel topic, Apr 28th is our upstream release date for 20.2</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> community notice: we ask that pull requests or bugs that need resolution for 20.2 be up for review by Friday April 24th so there is time to review and merge those fixes.</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> active pulls indended for the release should be up in github at <a href="https://github.com/canonical/cloud-init/pulls">https://github.com/canonical/cloud-init/pulls</a></p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> <em>intended</em> rather</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> #topic Community Charter</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> his section is generally reserved to discuss any general community goals for cloud-init, at last cloud-init summit we defined those goals as:</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> - datasource doc fixes</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> - json schema validation for each cloudinit/config/cc_*py modules</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> there are feature bugs created for these tasks at <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=bitesize</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> #topic Office hours (next ~30 mins)</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> During office hours a couple of upstream devs will have eyes on this channel. Any questions, comments, branch reviews are fair game for discussion.</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> In leiu of active discussions, developers will be grooming the active pull request review queue to unblock branch authors.</p> -<p>16:37 <code>&lt;punkgeek&gt;</code> Odd_Bloke: No it doesn't work. why there is no way to config cloud-init in kvm virtualization rather than iso, like vm xml file?</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> I'm getting through a belated review on <a href="https://github.com/canonical/cloud-init/pull/298">https://github.com/canonical/cloud-init/pull/298</a></p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> punkgeek: like seeding ovf-env.xml? <a href="https://github.com/canonical/cloud-init/blob/master/doc/sources/ovf/README">https://github.com/canonical/cloud-init/blob/master/doc/sources/ovf/README</a></p> -<p>16:46 <code>&lt;rharper&gt;</code> punkgeek: you might want to look at virt-install , they recently have added support for providing cloud-config to VMs; virt-install is a wrapper around creating VMs utilizing libvirt as a backend, <a href="https://athinapl.home.blog/2019/08/25/gsoc-2019-cloud-init-configuration-for-virt-manager-virt-install/">https://athinapl.home.blog/2019/08/25/gsoc-2019-cloud-init-configuration-for-virt-manager-virt-install/</a></p> -<p>16:54 <code>&lt;Goneri&gt;</code> punkgeek, or you can take a look at virt-lightning</p> -<p>16:54 <code>&lt;Goneri&gt;</code> punkgeek, it's basically a CLI to use libvirt+cloud-init</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> Goneri: review done. sorry for the delay on such a minor set of change requests <a href="https://github.com/canonical/cloud-init/pull/298/files#">https://github.com/canonical/cloud-init/pull/298/files#</a></p> -<p>17:09 <code>&lt;blackboxsw&gt;</code> <a href="https://github.com/CanonicalLtd/uss-tableflip/pull/45">https://github.com/CanonicalLtd/uss-tableflip/pull/45</a> I think comments are resolved</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> I think we are at about the turn of the hour for cloud-init status. I'm going to review <a href="https://github.com/canonical/cloud-init/pull/305">https://github.com/canonical/cloud-init/pull/305</a> next</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> thanks all for tuning in. see you next time</p> -<p>17:12 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2020-03-31T16:19:00+00:002020-03-31T16:19:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2020-03-31:/status-2020-03-31.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 31 Mar at 16:19 &mdash; 17:17 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-03-31-16.19.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-03-31-16.19.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-03-10.html#status-2020-03-10">https://cloud-init.github.io/status-2020-03-10.html#status-2020-03-10</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:22 …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 31 Mar at 16:19 &mdash; 17:17 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-03-31-16.19.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-03-31-16.19.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-03-10.html#status-2020-03-10">https://cloud-init.github.io/status-2020-03-10.html#status-2020-03-10</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:22.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:23.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://paste.ubuntu.com/p/55hqVCfnpV/">https://paste.ubuntu.com/p/55hqVCfnpV/</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:32.</p> -<h3>Community Charter</h3> -<p>The discussion about "Community Charter" started at 16:42.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=bitesize </li> -</ul> -<h3>Office hours (next ~30 mins)</h3> -<p>The discussion about "Office hours (next ~30 mins)" started at 16:45.</p> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (38)</li> -<li>meetingology (4)</li> -<li>rharper (2)</li> -<li>Goneri (1)</li> -<li>shibumi (1)</li> -<li>smoser (0)</li> -<li>Odd_Bloke (0)</li> -</ul> -<h2>Full Log</h2> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #startmeeting cloud-init status meeting</p> -<p>16:19 <code>&lt;meetingology&gt;</code> Meeting started Tue Mar 31 16:19:14 2020 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:19 <code>&lt;meetingology&gt;</code> </p> -<p>16:19 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> Hello and welcome to another cloud-init community status meeting folks. please feel free to continue any current conversations</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> I'll interleave status meeting notes with existing conversations.</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #chair Odd_Bloke smoser rharper</p> -<p>16:20 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw rharper smoser</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> our IRC channel topic carries the next planned status meeting for those that wish to participate. All are welcome to interject or drive converstation topics here</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> let's set that now. to +2 weeks from now</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> April 14th, same time</p> -<p>16:21 <code>&lt;shibumi&gt;</code> rharper: thanks!</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> Previous meeting notes are here</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2020-03-10.html#status-2020-03-10">https://cloud-init.github.io/status-2020-03-10.html#status-2020-03-10</a></p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> The topics we generally cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Upcoming Meetings, Office Hours (~30 mins).</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> and from last meeting, no previous actions were unaccounted for.</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> recent changes landed in tip of master via git log --since 2020-03-10</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> #link <a href="https://paste.ubuntu.com/p/55hqVCfnpV/">https://paste.ubuntu.com/p/55hqVCfnpV/</a></p> -<p>16:24 <code>&lt;rharper&gt;</code> shibumi: also, the issue with openstack metadata service not being found is likely related to classless statci route support in the EphemeralDHCP class in cloud-init, we fixed an issue there last fall, <a href="https://github.com/canonical/cloud-init/commit/07b17236be5665bb552c7460102bcd07bf8f2be8">https://github.com/canonical/cloud-init/commit/07b17236be5665bb552c7460102bcd07bf8f2be8</a></p> -<p>16:24 <code>&lt;rharper&gt;</code> shibumi: long term, we would like to replace dhclient with a python-based one; we've just not had a change to implement a minimal dhclient in python only</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> in that paste or recent changes, some big items have landed since last we 'met': both NetBSD and OpenBSD distro support is now added to cloud-init. vmware support of guest info gc status, SAP Converged cloud gets identified as OpenStack and Ubuntu Focal prioritizing netplan over ifupdown if both are present</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> Also Odd_Bloke has been landing and improving cloud-init automated process with near daily branches. github actions/workflows and docs about review and coding style expectations are landing to make it a lot easier for upstream to help speed contributions and reviews</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> Also, you'll note a lot of dropping python six and other py2-related artifacts from our codebase. Since upstream support is py3.4 or later we can simplify and prune a lot of the vestigial py2 functionality.</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> Ahh I also forgot, Ec2 now by default (Ubuntu Focal or tip of cloud-init) renders full networking, including secondary IPv4/IPv6 addresses, for all interfaces attached to a VM based on network config supplied by IMDS. Old releases of cloud-init used to only render basic networking on the primary (eth0) nic.</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> thanks Goneri and meena for all your the BSD ongoing development and support work there BTW</p> -<p>16:33 * Goneri waves</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> :) upstream is focused a bit on continuing to clean up py2 remnants from tip, adding support for reading netplan configuration from initramfs and continuing to add automation to the github development and release process/tooling to speed reviews.</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> we are also hammering the review queue a bit better than in the past with daily PR assignments to ensure the system remains more efficient</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> thanks again for all the code submits folks!</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> waiting In the wings we will eventually get around to handling the network hotplug solution for cloud-init (if configured)</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> #topic Community Charter</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> This section is generally reserved to discuss any general community goals for cloud-init. Per last cloud-init summit we discussed prioritizing the following:</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> * json schema validation for each cloudinit/config/cc_*py module</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> * correcting, extending stale datasource documentation under doc/rtd/topics/datasources</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> those tasks are easy to split up and so we set a goal to try to chunk through it this year</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> they are also categorized as bugs for easy pickup/assignment for anyone interested.</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=bitesize</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> #topic Office hours (next ~30 mins)</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> thanks for listening to the above...... In this section a couple upstream devs should be available with eyes on the channel for the next 30 minutes for and bug, feature, PR review questions or concerns.</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> again thanks for joining. We'll have this meeting again in 2 weeks</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> I'm going to spend this time working on our cherry-pick script for publishing the Netplan -&gt;` ENI work into Ubuntu Focal today.</p> -<p>17:17 <code>&lt;blackboxsw&gt;</code> Thanks for tuning in.</p> -<p>17:17 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2020-03-10T16:22:00+00:002020-03-10T16:22:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2020-03-10:/status-2020-03-10.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 10 Mar at 16:22 &mdash; 17:45 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-03-10-16.22.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-03-10-16.22.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-02-18.html#status-2020-02-18">https://cloud-init.github.io/status-2020-02-18.html#status-2020-02-18</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:24 …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 10 Mar at 16:22 &mdash; 17:45 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-03-10-16.22.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-03-10-16.22.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-02-18.html#status-2020-02-18">https://cloud-init.github.io/status-2020-02-18.html#status-2020-02-18</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:24.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:25.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://wiki.ubuntu.com/FocalFossa/ReleaseSchedule">https://wiki.ubuntu.com/FocalFossa/ReleaseSchedule</a> </li> -<li><strong>LINK</strong>: <a href="https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html#format-of-instance-data-json">https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html#format-of-instance-data-json</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:37.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pulls">https://github.com/canonical/cloud-init/pulls</a> </li> -</ul> -<h3>Community Charter and upcoming meeting</h3> -<p>The discussion about "Community Charter and upcoming meeting" started at 16:51.</p> -<h3>cloud-init pull-requests <a href="https://git.io/JeVed">https://git.io/JeVed</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting March 1 16:15 UTC | 19.4 (Dec 17) drops Py2.7 : origin/stable-19.4 | 20.1 (Feb 18) | <a href="https://bugs.launchpad.net/cloud-init/+filebug">https://bugs.launchpad.net/cloud-init/+filebug</a></h3> -<p>The discussion about "cloud-init pull-requests <a href="https://git.io/JeVed">https://git.io/JeVed</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting March 1 16:15 UTC | 19.4 (Dec 17) drops Py2.7 : origin/stable-19.4 | 20.1 (Feb 18) | <a href="https://bugs.launchpad.net/cloud-init/+filebug">https://bugs.launchpad.net/cloud-init/+filebug</a>" started at 16:53.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=bitesize </li> -</ul> -<h3>Office Hours (next 30 mins)</h3> -<p>The discussion about "Office Hours (next 30 mins)" started at 16:58.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pull/241">https://github.com/canonical/cloud-init/pull/241</a> </li> -<li><strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pull/241/files">https://github.com/canonical/cloud-init/pull/241/files</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 (109)</li> -<li>Odd_Bloke (13)</li> -<li>tribaal (5)</li> -<li>meetingology (4)</li> -<li>AnhVoMSFT (2)</li> -<li>Goneri (2)</li> -<li>powersj (1)</li> -<li>smoser (0)</li> -<li>rharper (0)</li> -</ul> -<h2>Full Log</h2> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:22 <code>&lt;meetingology&gt;</code> Meeting started Tue Mar 10 16:22:58 2020 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:22 <code>&lt;meetingology&gt;</code> </p> -<p>16:22 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> Hello and welcome to another cloud-init community status meeting.</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> our IRC channel topic carries the next planned status meeting for those that wish to participate.</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> All are welcome and interruptions encouraged</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #chair rharper Odd_Bloke smoser</p> -<p>16:23 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw rharper smoser</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> Previous meeting notes are here</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2020-02-18.html#status-2020-02-18">https://cloud-init.github.io/status-2020-02-18.html#status-2020-02-18</a></p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> he topics we cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Upcoming Meetings, Office Hours (~30 mins).</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> *the even</p> -<p>16:24 <code>&lt;Odd_Bloke&gt;</code> o/</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> \O</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> sorry, have my big head on</p> -<p>16:24 <code>&lt;tribaal&gt;</code> o/</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> :). Last meeting had no actions carried over. So I think this topic is a noop this week</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> recent changes landed in tip of master via git log --since 2020-02-18 <a href="https://paste.ubuntu.com/p/sJVpvjFbPj/">https://paste.ubuntu.com/p/sJVpvjFbPj/</a></p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> we've added some tooling/actions for github, ec2 IMDSv2 token redacting from logs, alloowing kernel cmdline to tell cloud-init network-config=disabled and not falling back to IMDSv1 on Ec2-proper platform</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> thanks fred-lefebvre for the ec2 IMDS fallback branch and others for some additional driveby doc updates</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> Also, we performed an upload to Ubuntu Focal (20.04) series with latest tip of cloud-init to make sure the development release is up to date with recent features</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> Ubuntu Focal release is currently in feature freeze, so that will affect what patches we pull into Ubuntu Focal at this time as 'new features' would need a Feature Freeze Exception during the stage of Ubuntu development.</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> #link <a href="https://wiki.ubuntu.com/FocalFossa/ReleaseSchedule">https://wiki.ubuntu.com/FocalFossa/ReleaseSchedule</a></p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> As Odd_Bloke alluded to just before this meeting, we are trying to keep tip of master</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> open for commits.</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> On the ubuntu-side of the house we will sort cherry picking bug fixes into ubuntu focal during this short feature freeze period of time</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> If there are significant features that your cloud platform really would like to see on the first public release of Ubuntu Focal, then please get ahold of us in channel of on the mailing list to suggest that we shepherd those features in during this freeze.</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> But, generally cloud-init team will continue to follow the SRU process to get updates into Focal after feature freeze is lifted.</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> and again, our SRU test/verification process for Ubuntu will continue to target Xenial, Bionic, Eoan and Focal series for the updates we plan to make in the near future</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> one thing to note in recent changes as well is that we've now added the ability to query distro, kernel, cpu arch, python runtime version and and merged cloud-config to cloud-config jinja templates. So #cloud-config userdata can be opinionated based on your target distribution or runtime environment.</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html#format-of-instance-data-json">https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html#format-of-instance-data-json</a></p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> I think that about wraps recent changes</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> #link <a href="https://github.com/canonical/cloud-init/pulls">https://github.com/canonical/cloud-init/pulls</a></p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> our active pulls above is probably the best source of info on features/bugfixes in flight.</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> Though behind the scenes we have held a couple of meetings to determine how much more automation/tooling we need to clean up to improve our github developer process</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> I think Odd_Bloke and I have around 4 PRs that we are hoping to clean up to get a couple of things in place:</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> foremost I believe Odd_Bloke is scrubbing the github review process PR so that we have a good starting point for expectations for every developer, author or committer.</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> I think ultimately the goal there is to make sure committers can provide a set of expectations on active PR reviews to PR authors, so that active developers get better prioritized reviews.</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> we are going to add and enable a number of github actions and workflows that should do the following:</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> - age PRs and add labelling to indicate to reviewers and authors that a review needs attention or it will be automatically closed (after around 4 weeks of languishing)</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> - label/notify steps to signed the contributor license agreement if unsigned</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> - run addtional integration tests on active PRs in CI</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> not sure if I am I missing anything else there.</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> but ideally we'd like to find a process that helps upstream unblock PRs and get review comments faster</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> so, it'll be an iterative process</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> and thanks for the reviews and suggestions so far on <a href="https://github.com/canonical/cloud-init/pull/160">https://github.com/canonical/cloud-init/pull/160</a> as it is the first cut at trying to document the process</p> -<p>16:47 <code>&lt;tribaal&gt;</code> Nice!</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> woot. the hope I believe is to land that this week as well as branches like <a href="https://github.com/canonical/cloud-init/pull/164">https://github.com/canonical/cloud-init/pull/164</a> <a href="https://github.com/canonical/cloud-init/pull/236">https://github.com/canonical/cloud-init/pull/236</a> and <a href="https://github.com/canonical/cloud-init/pull/125">https://github.com/canonical/cloud-init/pull/125</a></p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> additionally a gap that we still have vs when we hosted in Launchpad, is our auto-merge Launchpad bug commenting/maintenance:</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> We still have a need for the following:</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> - comment on LP bugs linking to an open github PR</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> - comment on merged commitish in github and Fix Commited state when a PR lands in upstream</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> so we'll be tackling that too in order to make upstream maintainers happier and better advertise fixes to bug filers</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> right now that's all a manual process since we haven't retooled our bug-related tooling</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> #topic Community Charter and upcoming meeting</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> let's set the status meeting for next session</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> oops and I realize only now that I blew it this week due to daylight savings... meeting wasn't 'supposed' to start until 25 mins from now : /</p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> #topic cloud-init pull-requests <a href="https://git.io/JeVed">https://git.io/JeVed</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting March 1 16:15 UTC | 19.4 (Dec 17) drops Py2.7 : origin/stable-19.4 | 20.1 (Feb 18) | <a href="https://bugs.launchpad.net/cloud-init/+filebug">https://bugs.launchpad.net/cloud-init/+filebug</a></p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> that's better.</p> -<p>16:53 <code>&lt;AnhVoMSFT&gt;</code> it says March 1, is that correct?</p> -<p>16:54 <code>&lt;tribaal&gt;</code> there :)</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> hah, good I got another participant</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> :)</p> -<p>16:54 <code>&lt;AnhVoMSFT&gt;</code> UK will also have their own daylight savings March 29th I believe</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> sorry AnhVoMSFT tribaal :)</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> yeah this time of year always messes with timing. We try to set things in terms of UTC to avoid thrashing</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> but even that fails due to human error (my bad)</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> Other community charter tasks are generally categorized in bugs labelled bitesize</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=bitesize</p> -<p>16:57 <code>&lt;blackboxsw&gt;</code> general topics for this year were tasks that are easily done in parallel, such as json schema addtions and datasource readthe docs updates/corrections and fleshing out.</p> -<p>16:57 <code>&lt;blackboxsw&gt;</code> jsonschema example is here for review if anyone wants to take a stab at testing it out. or extending schema for other config modules.<a href="https://github.com/canonical/cloud-init/pull/152">https://github.com/canonical/cloud-init/pull/152</a></p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> and again all cloud-init contributors are encouraged to review/comment any active cloud-init PRs @ <a href="https://github.com/canonical/cloud-init/pulls">https://github.com/canonical/cloud-init/pulls</a> the more voices, the better the quality</p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next 30 mins)</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> During this topic, please bring up any questions, discussions, bugs or features or paper cuts that need attention. there should be a couple of cloud-init developers with eyes on the channel to actively respond.</p> -<p>17:00 <code>&lt;blackboxsw&gt;</code> just before the start of this meeting Odd_Bloke was asking about getting the pytest branch landed for cloud-init. (moving off of nosetests as the project is EOL/unmaintained)</p> -<p>17:00 <code>&lt;tribaal&gt;</code> that's nice. pytest is becoming the de-facto standard these days anyway</p> -<p>17:05 <code>&lt;blackboxsw&gt;</code> yeah, didn't want to get stuck using something that becomes unsupported or unsupportable. we don't have the bandwidth in this project to maintain stacks that aren't being looked at by the collective internet ;)</p> -<p>17:05 <code>&lt;Odd_Bloke&gt;</code> blackboxsw: I believe that branch is now only blocked on you removing your "Request changes" review now that we've established that we don't need to hold off on landing things for Feature Freeze.</p> -<p>17:05 <code>&lt;tribaal&gt;</code> makes total sense :)</p> -<p>17:05 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: do you know if rharper did the new-upstream-snapshot into focal already</p> -<p>17:05 <code>&lt;blackboxsw&gt;</code> to have a 'clean slate' for the pytest branch landing</p> -<p>17:06 <code>&lt;Odd_Bloke&gt;</code> blackboxsw: We can new-upstream-snapshot from an older commit, I don't believe that's a blocker.</p> -<p>17:06 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: not a blocker, but I could do that now as it's 5 mins</p> -<p>17:07 <code>&lt;blackboxsw&gt;</code> then we can land right aftr</p> -<p>17:07 <code>&lt;blackboxsw&gt;</code> sound good? I see nothing queued <a href="https://launchpad.net/ubuntu/focal/+queue">https://launchpad.net/ubuntu/focal/+queue</a>?queue_state=3&amp;queue_text=cloud-init</p> -<p>17:08 <code>&lt;Odd_Bloke&gt;</code> Sure, if you're happier doing that. :)</p> -<p>17:09 <code>&lt;blackboxsw&gt;</code> I aam :)</p> -<p>17:09 <code>&lt;blackboxsw&gt;</code> ok doing that right now</p> -<p>17:09 <code>&lt;blackboxsw&gt;</code> then we can start the cherry picking just after</p> -<p>17:10 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: I'm adding this as the debian/changelog section title</p> -<p>17:10 <code>&lt;blackboxsw&gt;</code> * New upstream snapshot: bug-fix-only feature-freeze-exception</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> instead of * New upstream snapshot:</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> sound reasonable?</p> -<p>17:11 <code>&lt;Odd_Bloke&gt;</code> It isn't bug-fix-only because we have the FFe for a non-bugfix.</p> -<p>17:12 <code>&lt;Odd_Bloke&gt;</code> I was just reading the wiki page that suggested wording, I think, let me take a look.</p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> <a href="https://github.com/canonical/cloud-init/pull/241">https://github.com/canonical/cloud-init/pull/241</a></p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> ahh right, reviewing that now</p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> yeah not quite sure how to handle our FFe uploads</p> -<p>17:14 <code>&lt;Odd_Bloke&gt;</code> Oh, if it's only that change, then I don't think we need anything specific in the changelog. We have an FFE bug that we're closing with that upload.</p> -<p>17:14 * blackboxsw re-reads <a href="https://wiki.ubuntu.com/FreezeExceptionProcess">https://wiki.ubuntu.com/FreezeExceptionProcess</a></p> -<p>17:14 <code>&lt;Odd_Bloke&gt;</code> And that means it's <em>definitely</em> not bug-fix-only, there isn't a single bugfix in there. ;)</p> -<p>17:14 <code>&lt;blackboxsw&gt;</code> ok that sounds good, will just keep the New upstream snapshot</p> -<p>17:14 <code>&lt;blackboxsw&gt;</code> ok thanks for the review. redoing.</p> -<p>17:14 <code>&lt;Odd_Bloke&gt;</code> Hopefully I'm right and you don't get yelled at. :p</p> -<p>17:15 <code>&lt;powersj&gt;</code> better to upload and ask for forgiveness...</p> -<p>17:15 <code>&lt;blackboxsw&gt;</code> ehh, unlikely :) it seems like steve and others have been pretty lax about changelog text (or manipulating it after the fact) :)</p> -<p>17:15 <code>&lt;Odd_Bloke&gt;</code> Cool, I'll do the same thing locally to review.</p> -<p>17:16 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: force pushed</p> -<p>17:16 <code>&lt;blackboxsw&gt;</code> <a href="https://github.com/canonical/cloud-init/pull/241/files">https://github.com/canonical/cloud-init/pull/241/files</a></p> -<p>17:16 <code>&lt;Odd_Bloke&gt;</code> blackboxsw: Approved.</p> -<p>17:17 <code>&lt;blackboxsw&gt;</code> thanks Odd_Bloke</p> -<p>17:17 <code>&lt;blackboxsw&gt;</code> build-and-pushing it up</p> -<p>17:18 <code>&lt;blackboxsw&gt;</code> ok onto your pytest branch now</p> -<p>17:18 <code>&lt;blackboxsw&gt;</code> while I await the ubuntu "accepted" response email</p> -<p>17:20 <code>&lt;blackboxsw&gt;</code> Uploading cloud-init_20.1-10-g71af48df-0ubuntu1.dsc: done.</p> -<p>17:21 <code>&lt;blackboxsw&gt;</code> just waiting on review/acceptance</p> -<p>17:22 <code>&lt;blackboxsw&gt;</code> community-notice: tip of cloud-init published into Ubuntu Focal (20.04) [ubuntu/focal-proposed] cloud-init 20.1-10-g71af48df-0ubuntu1 (Accepted)</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> ok Odd_Bloke merged at long last <a href="https://github.com/canonical/cloud-init/pull/211">https://github.com/canonical/cloud-init/pull/211</a></p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> nosetest is dead, long live pytest</p> -<p>17:26 <code>&lt;Odd_Bloke&gt;</code> \o/</p> -<p>17:27 <code>&lt;Odd_Bloke&gt;</code> blackboxsw: <a href="https://github.com/canonical/cloud-init/pull/239">https://github.com/canonical/cloud-init/pull/239</a> `&lt;-- another small one for you</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> approve Odd_Bloke and thanks. it is waiting on you for merge (and CI completion)</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> works on my focal box</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> which was broken before</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: <a href="https://github.com/canonical/cloud-init/pull/164">https://github.com/canonical/cloud-init/pull/164</a> is ready for you I think (labeling in cron)</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> for CLA ! CLA.</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> or do we want that PR to actually ignore certain paths (like doc changes) as not-requiring CLA</p> -<p>17:43 <code>&lt;Goneri&gt;</code> blackboxsw, could you take a look at <a href="https://github.com/canonical/cloud-init/pull/62">https://github.com/canonical/cloud-init/pull/62</a> Pleaaaase :-)</p> -<p>17:44 <code>&lt;blackboxsw&gt;</code> Goneri: yes, and so sorry about that.</p> -<p>17:44 <code>&lt;Goneri&gt;</code> np, and Yeah! for pytest :-D</p> -<p>17:44 <code>&lt;blackboxsw&gt;</code> ... and that about wraps up on our cloud-init status meeting. :) I'll close it out and post the minutes for next time</p> -<p>17:45 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2020-02-18T17:35:00+00:002020-02-18T17:35:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2020-02-18:/status-2020-02-18.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 18 Feb at 17:35 &mdash; 18:36 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-02-18-17.35.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-02-18-17.35.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-02-04.html#status-2020-02-04">https://cloud-init.github.io/status-2020-02-04.html#status-2020-02-04</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 17:37 …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 18 Feb at 17:35 &mdash; 18:36 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-02-18-17.35.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-02-18-17.35.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-02-04.html#status-2020-02-04">https://cloud-init.github.io/status-2020-02-04.html#status-2020-02-04</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 17:37.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 17:38.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://paste.ubuntu.com/p/28Y8jGTGwr/">https://paste.ubuntu.com/p/28Y8jGTGwr/</a> </li> -</ul> -<h3>In-prgoress Development</h3> -<p>The discussion about "In-prgoress Development" started at 17:45.</p> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 17:45.</p> -<h3>cloud-init upstream 20.1</h3> -<p>The discussion about "cloud-init upstream 20.1" started at 17:49.</p> -<h3>Community Charter</h3> -<p>The discussion about "Community Charter" started at 17:59.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=bitesize </li> -</ul> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (52)</li> -<li>meetingology (5)</li> -<li>Odd_Bloke (3)</li> -<li>smoser (0)</li> -<li>rharper (0)</li> -</ul> -<h2>Full Log</h2> -<p>17:35 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>17:35 <code>&lt;meetingology&gt;</code> Meeting started Tue Feb 18 17:35:26 2020 UTC. The chair is blackboxsw. Information about MeetBot at <a href="http://wiki.ubuntu.com/meetingology.">http://wiki.ubuntu.com/meetingology.</a></p> -<p>17:35 <code>&lt;meetingology&gt;</code> </p> -<p>17:35 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>17:35 <code>&lt;blackboxsw&gt;</code> o/ hi cloud-init folks. sorry I botched being able to read calendars last time.</p> -<p>17:36 <code>&lt;blackboxsw&gt;</code> let's kick off our cloud-init status meeting.</p> -<p>17:36 <code>&lt;blackboxsw&gt;</code> notes from previous meeting are here:</p> -<p>17:36 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2020-02-04.html#status-2020-02-04">https://cloud-init.github.io/status-2020-02-04.html#status-2020-02-04</a></p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> the topics we cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Upcoming Meetings, Office Hours (~30 mins).</p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> today I'll add a topic for cloud-init's upstream release 20.1</p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> Last meeting minutes show no carryover action items. So we can drop into recent changes</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>17:40 <code>&lt;blackboxsw&gt;</code> We have about 8 commits landed in master since last meeting: found with git log --since 02-04-2020</p> -<p>17:40 <code>&lt;blackboxsw&gt;</code> <a href="https://paste.ubuntu.com/p/28Y8jGTGwr/">https://paste.ubuntu.com/p/28Y8jGTGwr/</a></p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> some doc fixes, CI fixes for Azure integration testing , swap disk support for cc_disk_setup and freebsd improvements.</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> thanks for contributions there all. I think we still have a long tail of improvements to review for FreeBSD and NetBSD so we'll try to keep the conversation going there.. Thanks meena and do3meli there</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> I mean Goneri</p> -<p>17:44 <code>&lt;blackboxsw&gt;</code> #chair rharper Odd_Bloke smoser</p> -<p>17:44 <code>&lt;meetingology&gt;</code> Warning: Nick not in channel: rharper</p> -<p>17:44 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw rharper smoser</p> -<p>17:44 <code>&lt;blackboxsw&gt;</code> forgot to set meeting chairs. sry</p> -<p>17:45 <code>&lt;blackboxsw&gt;</code> #topic In-prgoress Development</p> -<p>17:45 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>17:47 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: is currently wrapping up any remaining py2/p3-isms in master branch. Dropping use of 'six' throughout the code. Paride is working on copr-build failures due to the shift to python3 packages. otubo, thanks for the ping back on finding various python3 CentOS packages. We'll also try sorting this this week so cloud-init py3 builds can work on CentOS 7 and 8</p> -<p>17:47 <code>&lt;blackboxsw&gt;</code> If folks didn't see the mailing list Odd_Bloke has a branch up to shift from nosetests -&gt;` pytest <a href="https://lists.launchpad.net/cloud-init/msg00245.html">https://lists.launchpad.net/cloud-init/msg00245.html</a></p> -<p>17:48 <code>&lt;blackboxsw&gt;</code> we expect to land that after 20.1 releases. Thanks for the reviews there <a href="https://github.com/canonical/cloud-init/pull/211">https://github.com/canonical/cloud-init/pull/211</a></p> -<p>17:49 <code>&lt;blackboxsw&gt;</code> #topic cloud-init upstream 20.1</p> -<p>17:50 <code>&lt;blackboxsw&gt;</code> So, today at EOD is upstream release day for cloud-init 20.1. Just another timed release of cloud-init which we strive to make quarterly thoughout the year</p> -<p>17:50 <code>&lt;blackboxsw&gt;</code> As mentioned on the mailing list, if there are any branches/PRs that folks really would like to get into 20.1, please raise them here. We will scrub the review queue today and see what makes sense to land for this release.</p> -<p>17:52 <code>&lt;Odd_Bloke&gt;</code> I'll be driving the 20.1 release.</p> -<p>17:53 <code>&lt;Odd_Bloke&gt;</code> We just landed <a href="https://github.com/canonical/cloud-init/pull/204">https://github.com/canonical/cloud-init/pull/204</a> into master, which is a fix for a (low priority) CVE that we wanted in before cutting the release.</p> -<p>17:54 <code>&lt;Odd_Bloke&gt;</code> I'm going to perform some testing of that change before cutting the release, to determine if any doc changes are required for it and to check if it impacts boot on Azure instances that have a password provided by the Azure fabric.</p> -<p>17:54 <code>&lt;blackboxsw&gt;</code> I was just looking over the PR from fred in ec2 land about handling a disabled path for IMDSv2 that looks interesting, but it still needs unit tests <a href="https://github.com/canonical/cloud-init/pull/216/files">https://github.com/canonical/cloud-init/pull/216/files</a></p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> this would certainly help non-ec2 lookalikes</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> and is a fairly specific fix.</p> -<p>17:56 <code>&lt;blackboxsw&gt;</code> we can peek over it during the office hours and see if it makes sense.</p> -<p>17:56 <code>&lt;blackboxsw&gt;</code> Thanks Odd_Bloke for driving the 20.1 release.</p> -<p>17:56 <code>&lt;blackboxsw&gt;</code> So, again, plan is to cut 20.1 at end of day today.</p> -<p>17:58 <code>&lt;blackboxsw&gt;</code> What follows will be a tag and release to Ubuntu Focal to sync tip of master to Ubuntu development release</p> -<p>17:59 <code>&lt;blackboxsw&gt;</code> #topic Community Charter</p> -<p>17:59 <code>&lt;blackboxsw&gt;</code> This topic is a placeholder to remind folks of any project-wide development tasks that we are engaging the community in.</p> -<p>18:00 <code>&lt;blackboxsw&gt;</code> the general theme at the moment is cloud-config schema definitions for the config modules in cloudinit/config/cc_*py and improving/correct datasource configuration documentation</p> -<p>18:00 <code>&lt;blackboxsw&gt;</code> We've queued this work as separate bugs in cloud-init at the following link</p> -<p>18:01 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=bitesize</p> -<p>18:01 <code>&lt;blackboxsw&gt;</code> we'll revisit this set of bugs/features and resent community charter goals near the end of 2020 at the next cloud-init summit. If there are suggestions/desires for community themed tasks please feel free to set the direction there.</p> -<p>18:02 <code>&lt;blackboxsw&gt;</code> these community tasks are grabbed by any contributor to cloud-init.</p> -<p>18:03 <code>&lt;blackboxsw&gt;</code> An example of the schema definitions we are looking to add is the PR in review here. <a href="https://github.com/canonical/cloud-init/pull/152">https://github.com/canonical/cloud-init/pull/152</a></p> -<p>18:04 <code>&lt;blackboxsw&gt;</code> As always, everyone's review counts. As a project we are trying to also look to 'promote' more core-contributors, with commit rights to the cloud-init project. Reviews count just much as proposing pull requests to the project.</p> -<p>18:04 <code>&lt;blackboxsw&gt;</code> thanks again for all the contributions, reviews and bugs that are being contributed to date. It really helps improve this project's use</p> -<p>18:05 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>18:07 <code>&lt;blackboxsw&gt;</code> During this topic, please bring up any questions, discussions, bugs or features or paper cuts that need attention. there should be a couple of cloud-init developers with eyes on the channel to actively respond.</p> -<p>18:08 <code>&lt;blackboxsw&gt;</code> In leiu of active discussions, we'll hit up the review queue for cloud-init at <a href="https://git.io/JeVed">https://git.io/JeVed</a> and get ready for the 20.1 release</p> -<p>18:09 <code>&lt;blackboxsw&gt;</code> I'm going to see if I can</p> -<p>18:09 <code>&lt;blackboxsw&gt;</code> review <a href="https://github.com/canonical/cloud-init/pull/216/files">https://github.com/canonical/cloud-init/pull/216/files</a> and propose the unit test changes there</p> -<p>18:09 <code>&lt;blackboxsw&gt;</code> I think that could be a valid addition for ec2-lookalikes to avoid an unnecessary 2 minute timeout</p> -<p>18:09 <code>&lt;blackboxsw&gt;</code> on boot</p> -<p>18:19 <code>&lt;blackboxsw&gt;</code> hrm on 2nd thought w/ 216, I think that patch set should be more specific, such as actually testing HTTP status 403 instead of just checking if metadata was None and assuming it was disabled. I'll put a couple of review comments on that as I dig in, but probably not in a state that it could be landed today</p> -<p>18:36 <code>&lt;blackboxsw&gt;</code> thanks for tuning in folks. See you next time</p> -<p>18:36 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2020-02-04T17:23:00+00:002020-02-04T17:23:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2020-02-04:/status-2020-02-04.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 04 Feb at 17:23 &mdash; 19:08 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-02-04-17.23.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-02-04-17.23.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 17:27.</p> -<h3>Recent Changes</h3> -<p>The …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 04 Feb at 17:23 &mdash; 19:08 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-02-04-17.23.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-02-04-17.23.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 17:27.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 17:27.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://paste.ubuntu.com/p/3jQdKZVPcM/">https://paste.ubuntu.com/p/3jQdKZVPcM/</a> </li> -</ul> -<h3>In-progress Development,</h3> -<p>The discussion about "In-progress Development," started at 17:32.</p> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 17:32.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pulls">https://github.com/canonical/cloud-init/pulls</a> </li> -</ul> -<h3>Community Charter</h3> -<p>The discussion about "Community Charter" started at 17:43.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=bitesize </li> -</ul> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 17:47.</p> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (68)</li> -<li>ahosmanMSFT (10)</li> -<li>meetingology (5)</li> -<li>powersj (4)</li> -<li>ubot5 (3)</li> -<li>Odd_Bloke (0)</li> -<li>rharper (0)</li> -</ul> -<h2>Full Log</h2> -<p>17:23 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>17:23 <code>&lt;meetingology&gt;</code> Meeting started Tue Feb 4 17:23:28 2020 UTC. The chair is blackboxsw. Information about MeetBot at <a href="http://wiki.ubuntu.com/meetingology.">http://wiki.ubuntu.com/meetingology.</a></p> -<p>17:23 <code>&lt;meetingology&gt;</code> </p> -<p>17:23 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>17:23 <code>&lt;blackboxsw&gt;</code> morning, afternoon and evening folks. Time for another cloud-init community status meeting</p> -<p>17:24 <code>&lt;blackboxsw&gt;</code> #chair rharper</p> -<p>17:24 <code>&lt;meetingology&gt;</code> Current chairs: blackboxsw rharper</p> -<p>17:24 <code>&lt;blackboxsw&gt;</code> #chair Odd_Bloke</p> -<p>17:24 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw rharper</p> -<p>17:24 <code>&lt;blackboxsw&gt;</code> Coud-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>17:24 <code>&lt;blackboxsw&gt;</code> The next scheduled status meeting is always listed in the topic of this channel, so feel free to drop in on next session if you miss this one</p> -<p>17:25 <code>&lt;blackboxsw&gt;</code> while we're at it I'll update for next status meeting.</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> 2 weeks from today, same bat time, same bat channel</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> Our previous meeting minutes line here:</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> <em>live here</em> rather</p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> the topics we cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Upcoming Meetings, Office Hours (~30 mins).</p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> new topics or intejections are always welcome</p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> From last meeting we had no unresolved actions so we can jump to the next section</p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> found from tip of master with <code>git log --since 01/21/2020</code></p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - sysconfig: distro-specific config rendering for BOOTPROTO option (#162)</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> [Robert Schweikert] (LP: #1800854)</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - cloudinit: replace "from six import X" imports (except in util.py) (#183)</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - run-container: use 'test -n' instead of 'test ! -z' (#202)</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> [Paride Legovini]</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - net/cmdline: correctly handle static ip= config (#201)</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> [Dimitri John Ledkov] (LP: #1861412)</p> -<p>17:29 <code>&lt;ubot5&gt;</code> Launchpad bug 1800854 in cloud-init "BOTOPROTO handling between RHEL/Centos/Fedora and SUSE distros is different" [Medium,Triaged] <a href="https://launchpad.net/bugs/1800854">https://launchpad.net/bugs/1800854</a></p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - Replace mock library with unittest.mock (#186)</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - HACKING.rst: update CLA link (#199)</p> -<p>17:29 <code>&lt;ubot5&gt;</code> Launchpad bug 1861412 in cloud-init (Ubuntu) "cloud-init crashes with static network configuration" [Undecided,Fix committed] <a href="https://launchpad.net/bugs/1861412">https://launchpad.net/bugs/1861412</a></p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - Scaleway: Fix DatasourceScaleway to avoid backtrace (#128)</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> [Louis Bouchard]</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - cloudinit/cmd/devel/net_convert.py: add missing space (#191)</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - tools/run-container: drop support for python2 (#192) [Paride Legovini]</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - Print ssh key fingerprints using sha256 hash (#188) (LP: #1860789)</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - Make the RPM build use Python 3 (#190) [Paride Legovini]</p> -<p>17:29 <code>&lt;ubot5&gt;</code> Launchpad bug 1860789 in cloud-init (Ubuntu) "ssh_authkey_fingerprints must use sha256 not md5" [Undecided,Fix committed] <a href="https://launchpad.net/bugs/1860789">https://launchpad.net/bugs/1860789</a></p> -<p>17:29 <code>&lt;powersj&gt;</code> thought we were going to use pastebin :P</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> heh, that is a good point (I wondered if anyone would call me on that)</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> #link <a href="https://paste.ubuntu.com/p/3jQdKZVPcM/">https://paste.ubuntu.com/p/3jQdKZVPcM/</a></p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> generally speaking, dropping use of six since our code based is not python3-only, tooling dropping py2, sysconfig rendering flavors for opensuse, doc fixes and read the docs fixups</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> thanks all for the contributions over the last couple weeks</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development,</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> Any existing PRs are up for review at the following url:</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> #link <a href="https://github.com/canonical/cloud-init/pulls">https://github.com/canonical/cloud-init/pulls</a></p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> generally speaking we are in the 'long tail' part of a couple of feature-sets:</p> -<p>17:34 <code>&lt;blackboxsw&gt;</code> * we are trying to wrap up tooling for our automated CI, publishing processes and documentation for the shift to github from launchpad</p> -<p>17:34 <code>&lt;blackboxsw&gt;</code> * we are in progress on cloud-init handling network hotplug for a couple of datasources</p> -<p>17:35 <code>&lt;blackboxsw&gt;</code> * in progress on boot speed improvements for various platforms</p> -<p>17:36 <code>&lt;blackboxsw&gt;</code> We also recently validated and released cloud-init v 19.4.33 to Xenial, Bionic and Eoan (1/9/2020)</p> -<p>17:38 <code>&lt;ahosmanMSFT&gt;</code> Hi @blackboxsw I'm no longer in the provisioning team, but there's an urgency for the cloud test to be resilient. Have you looked at those issues, I can dedicate as much time as needed to this. If you have time, can we tackle this today?</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> there are also a number of PRs in flight for FreeBSD,NetBSD, OpenSUSE and CentOS that need attention so we can better enable those distros</p> -<p>17:38 <code>&lt;ahosmanMSFT&gt;</code> azurecloudtest that is</p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> hi ahosmanMSFT I can spend some time on office hours here to peek more at it. my individual runs didn't hit the timeouts again, so we might need a reproducer cmdline from you in a new bug maybe?</p> -<p>17:39 <code>&lt;ahosmanMSFT&gt;</code> So your able to run all tests successfully without timeout and image not building&gt;`</p> -<p>17:40 <code>&lt;blackboxsw&gt;</code> ahosmanMSFT: but yes I can spend a little time on this today. and I think ultimately we'll have to find the tox command line that exhibits this error. I'll go checkout my test run again and see. I don't think I saw the failure. but I might be invoking tests differently than you</p> -<p>17:41 <code>&lt;ahosmanMSFT&gt;</code> blackboxsw: hmm that's interesting, thanks let me know</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> same here ahosmanMSFT, can you file a bug with the traceback you see and the tox cmdline you are running?</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> then I know exactly what to look for</p> -<p>17:42 <code>&lt;ahosmanMSFT&gt;</code> Sure, will do now</p> -<p>17:43 <code>&lt;blackboxsw&gt;</code> cool.</p> -<p>17:43 <code>&lt;blackboxsw&gt;</code> ok next topic</p> -<p>17:43 <code>&lt;blackboxsw&gt;</code> #topic Community Charter</p> -<p>17:43 <code>&lt;blackboxsw&gt;</code> ok this section is reserved to raise general community work/goals.</p> -<p>17:44 <code>&lt;blackboxsw&gt;</code> At last cloud-init summit we raised a couple of general themes of improvements cloud-init would like to achieve</p> -<p>17:45 <code>&lt;blackboxsw&gt;</code> These themes fell into two categories for this year: datasource documentation updates and cloud-init json schema validation for the 50+ config modules in cloudinit/config/cc_*py so that we can better raise user-config errors and remove some of cloud-init's "sharp edges"</p> -<p>17:45 <code>&lt;blackboxsw&gt;</code> we converted a number of these feature requests in into bugs which can be searched here:</p> -<p>17:46 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=bitesize</p> -<p>17:46 <code>&lt;blackboxsw&gt;</code> tasks in this list should be fairly easy one-time bugs for folks with a little time available to help improve cloud-init.</p> -<p>17:47 <code>&lt;blackboxsw&gt;</code> we'll revisit this set of bugs/features and the community charter goals near the end of 2020 at the next cloud-init summit</p> -<p>17:47 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>17:48 <code>&lt;blackboxsw&gt;</code> this time is spent with cloud-init upstream dev eyes on this channel for any cloud-init feature, bug or implementation discussions. In the absence of such discussions, we'll review the active PRs to try to tidy up the review queue and unblock developers</p> -<p>17:49 <code>&lt;blackboxsw&gt;</code> for the moment, I'll look over some Azure test timeouts ahosmanMSFT is seeing</p> -<p>17:49 <code>&lt;blackboxsw&gt;</code> any other topics, concerns, bugs, questions are welcome and someone should be around to field them</p> -<p>17:50 <code>&lt;blackboxsw&gt;</code> ahosmanMSFT: so timeouts running integration tests, you said you are getting them about half the time?</p> -<p>18:48 <code>&lt;ahosmanMSFT&gt;</code> blackboxsw: Yes, I tracked it down to platforms/instance._wait_for_system</p> -<p>18:49 <code>&lt;ahosmanMSFT&gt;</code> I invoke it after initializing vm in platform/azurecloudtest/instance.start</p> -<p>18:49 <code>&lt;ahosmanMSFT&gt;</code> when removed, everything works as expected</p> -<p>18:50 <code>&lt;ahosmanMSFT&gt;</code> looks like it's needed for cloud tests so thought I'd leave it to you, since I don't know how ec2/lxd/... rely on</p> -<p>18:50 <code>&lt;powersj&gt;</code> ahosmanMSFT, can you file a bug please with the cli example?</p> -<p>18:50 <code>&lt;powersj&gt;</code> that would help us triage and make a proper decision on what change to make</p> -<p>18:51 <code>&lt;ahosmanMSFT&gt;</code> powersj, yes, was in the middle of that side tracked by meeting. On it now</p> -<p>18:51 <code>&lt;powersj&gt;</code> thanks!</p> -<p>19:07 <code>&lt;blackboxsw&gt;</code> aaaand, I should probably wrap the meeting for the day.</p> -<p>19:08 <code>&lt;blackboxsw&gt;</code> Thanks all for the time and energy you put into improving cloud-init! See you next time, or anytime in between</p> -<p>19:08 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2020-01-21T17:42:00+00:002020-01-21T17:42:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2020-01-21:/status-2020-01-21.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 21 Jan at 17:42 &mdash; 18:55 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-01-21-17.42.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-01-21-17.42.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 17:50.</p> -<ul> -<li><strong>LINK</strong>: bugs.launchpad …</li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 21 Jan at 17:42 &mdash; 18:55 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-01-21-17.42.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-01-21-17.42.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 17:50.</p> -<ul> -<li><strong>LINK</strong>: bugs.launchpad.net/cloud-init/+bugs?field.tag=bitesize </li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 17:53.</p> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 17:57.</p> -<h3>Community Charter</h3> -<p>The discussion about "Community Charter" started at 18:02.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloudinit.readthedocs.io/en/latest/topics/debugging.html#manual-sru-verification-procedure">https://cloudinit.readthedocs.io/en/latest/topics/debugging.html#manual-sru-verification-procedure</a> </li> -</ul> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 18:08.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1859725">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1859725</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 (58)</li> -<li>tribaal (3)</li> -<li>ubot5 (3)</li> -<li>meetingology (3)</li> -</ul> -<h2>Full Log</h2> -<p>17:42 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>17:42 <code>&lt;meetingology&gt;</code> Meeting started Tue Jan 21 17:42:43 2020 UTC. The chair is blackboxsw. Information about MeetBot at <a href="http://wiki.ubuntu.com/meetingology.">http://wiki.ubuntu.com/meetingology.</a></p> -<p>17:42 <code>&lt;meetingology&gt;</code> </p> -<p>17:42 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>17:43 <code>&lt;blackboxsw&gt;</code> At long last, and a bit late. Time for a brief cloud-init status meeting</p> -<p>17:43 <code>&lt;blackboxsw&gt;</code> Coud-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>17:44 <code>&lt;blackboxsw&gt;</code> You can always find the next date and time of the cloud-init status meeting in the topic of this channel.</p> -<p>17:45 <code>&lt;blackboxsw&gt;</code> it also serves as a reminder to me that we need to start it as I find it's easy to forget the appointment if it isn't staring us in the face.</p> -<p>17:46 <code>&lt;blackboxsw&gt;</code> Let's set next meeting now</p> -<p>17:48 <code>&lt;blackboxsw&gt;</code> our previous meeting minutes are recorded on our github site</p> -<p>17:49 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>17:49 <code>&lt;blackboxsw&gt;</code> the topics we cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Upcoming Meetings, Office Hours (~30 mins).</p> -<p>17:50 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>17:50 <code>&lt;blackboxsw&gt;</code> Previous #ACTION bbsw seed initial community charter bitesize bugs ... DONE.</p> -<p>17:51 <code>&lt;blackboxsw&gt;</code> 'bitesize' bugs for cloud-init can be found at the following link</p> -<p>17:51 <code>&lt;blackboxsw&gt;</code> #link bugs.launchpad.net/cloud-init/+bugs?field.tag=bitesize</p> -<p>17:52 <code>&lt;blackboxsw&gt;</code> These bugs should be easy to work in parallel as well as self-contained bits of work that any member of the community could approach as a small chunk of work</p> -<p>17:53 <code>&lt;blackboxsw&gt;</code> we moved from using trello board for tracking these tasks to using launchpad bugs as it eases the ability to search and grab ownership of the specific features/bugs</p> -<p>17:53 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> The following commits landed in tip of master: (found by git log --since 01/07/2020)</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> - Add Rootbox &amp; HyperOne to list of cloud in README (#176) [Adam Dobrawy]</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> - docs: add proposed SRU testing procedure (#167)</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> - util: rename get_architecture to get_dpkg_architecture (#173)</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> - Ensure util.get_architecture() runs only once (#172)</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> - Only use gpart if it is the BSD gpart (#131) [Conrad Hoffmann]</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> - freebsd: remove superflu exception mapping (#166) [Gonéri Le Bouder]</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> - ssh_auth_key_fingerprints_disable test: fix capitalization (#165)</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> [Paride Legovini]</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> - util: move uptime's else branch into its own boottime function (#53)</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> [Igor Galić] (LP: #1853160)</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> - workflows: add contributor license agreement checker (#155)</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> - net: fix rendering of 'static6' in network config (#77) (LP: #1850988)</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> - Make tests work with Python 3.8 (#139) [Conrad Hoffmann]</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> - fixed minor bug with mkswap in cc_disk_setup.py (#143) [andreaf74]</p> -<p>17:55 <code>&lt;ubot5&gt;</code> Launchpad bug 1853160 in cloud-init "uptime code does not work on FreeBSD with python 3" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1853160">https://launchpad.net/bugs/1853160</a></p> -<p>17:55 <code>&lt;ubot5&gt;</code> Launchpad bug 1850988 in cloud-init "[Cloud-init 18.5][CentOS 7 on vSphere] Crash when configuring static dual-stack (IPv4 + IPv6) networking" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1850988">https://launchpad.net/bugs/1850988</a></p> -<p>17:56 <code>&lt;blackboxsw&gt;</code> Thanks Adam, Conrad, andreaf74, Gonéri and meena for improving cloud-init.</p> -<p>17:57 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>17:58 <code>&lt;blackboxsw&gt;</code> FreeBSD, NetBSD improvements are under heavy development, thanks meena and Goneri for all the PRs put of in that regard.</p> -<p>17:58 <code>&lt;blackboxsw&gt;</code> Also robjo has started work on cleanup of sysconfig net rendering per <a href="https://github.com/canonical/cloud-init/pull/162">https://github.com/canonical/cloud-init/pull/162</a> and a mailing list discussion</p> -<p>17:59 <code>&lt;blackboxsw&gt;</code> rharper is also midstream on "cloud-init run as a daemon" mode <a href="https://github.com/canonical/cloud-init/pull/48">https://github.com/canonical/cloud-init/pull/48</a> which should improve cloud-init startup times by avoiding having to reload python 4 times for each cloud-init stage</p> -<p>18:00 <code>&lt;blackboxsw&gt;</code> Also in progress, upstream has started to SRU testing for cloud-init 19.4.33 into Ubuntu Xenial, Bionic and Eoan.</p> -<p>18:01 <code>&lt;blackboxsw&gt;</code> We expect to wrap up that testing this week for a publish of cloud-init 19.4.33 to those series</p> -<p>18:02 <code>&lt;blackboxsw&gt;</code> #topic Community Charter</p> -<p>18:02 <code>&lt;blackboxsw&gt;</code> As a note, any community member is welcome to participate in SRU testing of cloud-init if those changesets in the SRU affect your cloud platform or features.</p> -<p>18:02 <code>&lt;blackboxsw&gt;</code> We have added a guide for SRU testing on Ubuntu here</p> -<p>18:03 <code>&lt;tribaal&gt;</code> duly noted :)</p> -<p>18:03 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloudinit.readthedocs.io/en/latest/topics/debugging.html#manual-sru-verification-procedure">https://cloudinit.readthedocs.io/en/latest/topics/debugging.html#manual-sru-verification-procedure</a></p> -<p>18:03 <code>&lt;blackboxsw&gt;</code> :)</p> -<p>18:04 <code>&lt;blackboxsw&gt;</code> ahh tribaal we should pull in your PR for manual testing of Exoscale too if you think it's ready <a href="https://github.com/cloud-init/ubuntu-sru/pull/64">https://github.com/cloud-init/ubuntu-sru/pull/64</a></p> -<p>18:04 <code>&lt;tribaal&gt;</code> it's not unfortunately :/</p> -<p>18:05 <code>&lt;blackboxsw&gt;</code> ahh, ok <em>good</em>, thought it was waiting on review</p> -<p>18:05 <code>&lt;blackboxsw&gt;</code> ok can table that for another SRU (which will be around Feb 14th likely)</p> -<p>18:06 <code>&lt;tribaal&gt;</code> no worries, happy to help test the current one anyway</p> -<p>18:06 <code>&lt;blackboxsw&gt;</code> community notice: we are targeting Feb 18th as our cutoff for upstream cloud-init version 20.1 (which will be SRU'd to Ubuntu Xenial, bionic and Eoan). If there are features of bug fixes that you'd like to get into cloud-init 20.1 please raise them as PRs or discussion on the mailinglist or in channel</p> -<p>18:08 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>18:08 <code>&lt;blackboxsw&gt;</code> This time is spent on any cloud-init feature/bug/branch discussions. quetions or concerns and topics are welcome. In the absence of topics we'll groom the review queue.</p> -<p>18:09 <code>&lt;blackboxsw&gt;</code> I'm wrapping up some significant change suggestions the networking stuff for sysconfig on <a href="https://github.com/canonical/cloud-init/pull/162">https://github.com/canonical/cloud-init/pull/162</a></p> -<p>18:10 <code>&lt;blackboxsw&gt;</code> I should have that review done in about an hour</p> -<p>18:10 <code>&lt;blackboxsw&gt;</code> I've added myself as the "assignee" to that PR to indicate it as priority for me</p> -<p>18:11 <code>&lt;blackboxsw&gt;</code> also, note in SRU testing I've run into a repeated issue with cloud-init's ssh-import-id taking 1 minute to import a single ssh pubkey on Azure bionic advanced networking vms. (2 nics + ipv6 + multiple IPs). I'll be debugging this a bit today to make sure it is not a regression for this cloud-init SRU 19.4.33</p> -<p>18:12 <code>&lt;blackboxsw&gt;</code> if anyone has any feedback or issues associated with this cloud-init v 19.4.33 SRU, they can comment on the SRU bug or raise a new bug or comment in IRC</p> -<p>18:12 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1859725">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1859725</a></p> -<p>18:12 <code>&lt;ubot5&gt;</code> Ubuntu bug 1859725 in cloud-init (Ubuntu) "sru cloud-init (19.3.41 to 19.4.33) Xenial, Bionic and Eoan" [Undecided,New]</p> -<p>18:55 <code>&lt;blackboxsw&gt;</code> ok, that about wraps today's status meeting. We'll have the next one February 4th to chat again about getting features ready for 20.1</p> -<p>18:55 <code>&lt;blackboxsw&gt;</code> Thanks for tuning in.</p> -<p>18:55 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2020-01-07T17:30:00+00:002020-01-07T17:30:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2020-01-07:/status-2020-01-07.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 07 Jan at 17:30 &mdash; 18:39 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-01-07-17.30.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-01-07-17.30.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-12-10.html#status-2019-12-10">https://cloud-init.github.io/status-2019-12-10.html#status-2019-12-10</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 17:36 …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 07 Jan at 17:30 &mdash; 18:39 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-01-07-17.30.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-01-07-17.30.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-12-10.html#status-2019-12-10">https://cloud-init.github.io/status-2019-12-10.html#status-2019-12-10</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 17:36.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://github.com/cloud-init/cloud-init/pulls">https://github.com/cloud-init/cloud-init/pulls</a> </li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 17:39.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://paste.ubuntu.com/p/Cwnn3SbmWQ/">https://paste.ubuntu.com/p/Cwnn3SbmWQ/</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 17:44.</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>Community Charter</h3> -<p>The discussion about "Community Charter" started at 17:51.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/">https://bugs.launchpad.net/cloud-init/</a>?field.tag=bitesize </li> -<li><strong>ACTION</strong>: bbsw seed initial community charter bitesize bugs</li> -</ul> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 18:02.</p> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (118)</li> -<li>robjo (16)</li> -<li>ubot5 (13)</li> -<li>Odd_Bloke (11)</li> -<li>meetingology (6)</li> -<li>smoser (5)</li> -<li>rharper (0)</li> -</ul> -<h2>Full Log</h2> -<p>17:30 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>17:30 <code>&lt;meetingology&gt;</code> Meeting started Tue Jan 7 17:30:28 2020 UTC. The chair is blackboxsw. Information about MeetBot at <a href="http://wiki.ubuntu.com/meetingology.">http://wiki.ubuntu.com/meetingology.</a></p> -<p>17:30 <code>&lt;meetingology&gt;</code> </p> -<p>17:30 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> #chair Odd_Bloke</p> -<p>17:30 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> #chair rharper</p> -<p>17:30 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw rharper</p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> Welcome to the first cloud-init community status meeting of 2020. 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>17:31 <code>&lt;Odd_Bloke&gt;</code> usrdev: I'm not 100% sure from that description, could you file a bug using the link in the topic and attach the output of <code>cloud-init collect-logs</code> on an affected instance?</p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> We generally have this meeting ever 2 weeks (outside of intermittent holidays)... You can always find the next scheduled meeting in the topic of this channel</p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> Let</p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> Let</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> Let's schedule the next meeting now as well</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> Any objections to Jan 21 ?</p> -<p>17:33 <code>&lt;robjo&gt;</code> Look I'm not late ;)</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> ok topic set for next meeting</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> nope, just me robjo :) welcome to the party</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> as always previous meeting minutes are here.</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2019-12-10.html#status-2019-12-10">https://cloud-init.github.io/status-2019-12-10.html#status-2019-12-10</a></p> -<p>17:34 <code>&lt;blackboxsw&gt;</code> topics for this round: Feel free to interject/suggest other topics 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>17:34 <code>&lt;robjo&gt;</code> The move to Tuesday creates a conflict for me for the last 15 minutes of the meeting. Generally I don't think that's an issue as we are often done in less than 1 hour, just pointing out that usually I have to leave 15 minutes early</p> -<p>17:34 <code>&lt;robjo&gt;</code> not today ;)</p> -<p>17:36 <code>&lt;blackboxsw&gt;</code> +1 robjo. We'll try to keep it snappy :) and if others have conflicts we can certainly touch on shifting the schedule a bit. We generally have a conflict at 1 hr before this meeting, which is the only reason it isn't 1 hr earlier</p> -<p>17:36 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> last round: rharper to confirm <a href="https://github.com/canonical/cloud-init/pull/42">https://github.com/canonical/cloud-init/pull/42</a> can land. COMPLETED</p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> action2: upstream core-devs to decide about whether a PR can land if any upstream dev still has 'requested changes'</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: started writing up a spec/procedure for PR review and he is currently working on adding a documentation addition PR to <a href="http://cloudinit.readthedocs.io">http://cloudinit.readthedocs.io</a> that will describe the workflow for a PR to get from proposed -&gt;` merged.</p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> that PR should likely be up this week for review if folks are watching our review queue</p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> #link <a href="https://github.com/cloud-init/cloud-init/pulls">https://github.com/cloud-init/cloud-init/pulls</a></p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> No other actions from the previous meeting in December.</p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>17:40 <code>&lt;blackboxsw&gt;</code> recent commits that made it into tip: found via git log --since 12-10-2019</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> let's see if I get throttled for spam</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> - freebsd: fix create_group() cmd (#146) [Gonéri Le Bouder]</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> - doc: make apt_update example consistent (#154)</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> - doc: add modules page toc with links (#153) (LP: #1852456)</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> - Add support for the amazon variant in cloud.cfg.tmpl (#119)</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> [Frederick Lefebvre]</p> -<p>17:41 <code>&lt;ubot5&gt;</code> Launchpad bug 1852456 in cloud-init "doc: list of modules is no longer present" [Medium,Triaged] <a href="https://launchpad.net/bugs/1852456">https://launchpad.net/bugs/1852456</a></p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> heh</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> - freebsd: fix create_group() cmd (#146) [Gonéri Le Bouder]</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 - doc: make apt_update example consistent (#154)</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 - doc: add modules page toc with links (#153) (LP: #1852456)</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 - Add support for the amazon variant in cloud.cfg.tmpl (#119)</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 [Frederick Lefebvre]</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 - ci: remove Python 2.7 from CI runs (#137)</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 - modules: drop cc_snap_config config module (#134)</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 - migrate-lp-user-to-github: ensure Launchpad repo exists (#136)</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 - docs: add initial troubleshooting to FAQ (#104) [Joshua Powers]</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 - doc: update cc_set_hostname frequency and descrip (#109)</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 [Joshua Powers] (LP: #1827021)</p> -<p>17:41 <code>&lt;ubot5&gt;</code> Launchpad bug 1827021 in cloud-init "SSH Documentation should mention "Host Key"" [Medium,Triaged] <a href="https://launchpad.net/bugs/1827021">https://launchpad.net/bugs/1827021</a></p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> - ci: emit names of tests run in Travis (#120)</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 - Release 19.4 (LP: #1856761)</p> -<p>17:41 <code>&lt;ubot5&gt;</code> Launchpad bug 1856761 in cloud-init "Release 19.4" [Undecided,Fix released] <a href="https://launchpad.net/bugs/1856761">https://launchpad.net/bugs/1856761</a></p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 - rbxcloud: fix dsname in RbxCloud [Adam Dobrawy] (LP: #1855196)</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 - tests: Add tests for value of dsname in datasources [Adam Dobrawy]</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 - apport: Add RbxCloud ds [Adam Dobrawy]</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 - docs: Updating index of datasources [Adam Dobrawy]</p> -<p>17:41 <code>&lt;ubot5&gt;</code> Launchpad bug 1855196 in cloud-init "RBXCloud has no dsname defined, so datasource cannot be properly detected." [Low,Triaged] <a href="https://launchpad.net/bugs/1855196">https://launchpad.net/bugs/1855196</a></p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 - docs: Fix anchor of datasource_rbx [Adam Dobrawy]</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 - settings: Add RbxCloud [Adam Dobrawy]</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 - doc: specify _ over - in cloud config modules</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 [Joshua Powers] (LP: #1293254)</p> -<p>17:41 <code>&lt;ubot5&gt;</code> Launchpad bug 1293254 in cloud-init "style guide on dashes vs underscores in cloud-init" [Low,Fix released] <a href="https://launchpad.net/bugs/1293254">https://launchpad.net/bugs/1293254</a></p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - tools: Detect python to use via env in migrate-lp-user-to-github</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> [Adam Dobrawy]</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - Partially revert "fix unlocking method on FreeBSD" (#116)</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - tests: mock uid when running as root (#113)</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> [Joshua Powers] (LP: #1856096)</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - cloudinit/netinfo: remove unused getgateway (#111)</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - docs: clear up apt config sections (#107) [Joshua Powers] (LP: #1832823)</p> -<p>17:42 <code>&lt;ubot5&gt;</code> Launchpad bug 1856096 in cloud-init "unittest failure when running tests as root: no such file or dir: 'ud'" [High,Fix released] <a href="https://launchpad.net/bugs/1856096">https://launchpad.net/bugs/1856096</a></p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - doc: add kernel command line option to user data (#105)</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> [Joshua Powers] (LP: #1846524)</p> -<p>17:42 <code>&lt;ubot5&gt;</code> Launchpad bug 1832823 in cloud-init "docs: confusing heading "Add apt repositories"" [Low,Fix released] <a href="https://launchpad.net/bugs/1832823">https://launchpad.net/bugs/1832823</a></p> -<p>17:42 <code>&lt;ubot5&gt;</code> Launchpad bug 1846524 in cloud-init "docs: cloud-init user-data docs should mention kernel cmdline options" [Wishlist,Fix released] <a href="https://launchpad.net/bugs/1846524">https://launchpad.net/bugs/1846524</a></p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - config/cloud.cfg.d: update README [Joshua Powers] (LP: #1855006)</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - azure: avoid re-running cloud-init when instance-id is byte-swapped</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> (#84) [AOhassan]</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - fix unlocking method on FreeBSD [Igor Galić] (LP: #1854594)</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - debian: add reference to the manpages [Joshua Powers]</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - ds_identify: if /sys is not available use dmidecode (#42)</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> [Igor Galić] (LP: #1852442)</p> -<p>17:42 <code>&lt;ubot5&gt;</code> Launchpad bug 1855006 in cloud-init "config/cloud.cfg.d/README says "All files" rather than "*.cfg"" [Low,Fix released] <a href="https://launchpad.net/bugs/1855006">https://launchpad.net/bugs/1855006</a></p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - docs: add cloud-id manpage [Joshua Powers]</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - docs: add cloud-init-per manpage [Joshua Powers]</p> -<p>17:42 <code>&lt;ubot5&gt;</code> Launchpad bug 1854594 in cloud-init "lock passwd implemented wrong on FreeBSD" [Medium,Fix released] <a href="https://launchpad.net/bugs/1854594">https://launchpad.net/bugs/1854594</a></p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - docs: add cloud-init manpage [Joshua Powers]</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - docs: add additional details to per-instance/once [Joshua Powers]</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - Merge pull request #96 from fred-lefebvre/master [Joshua Powers]</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - Update doc-requirements.txt [Joshua Powers]</p> -<p>17:42 <code>&lt;ubot5&gt;</code> Launchpad bug 1852442 in cloud-init "ds-identify uses the /sys filesystem which is linux specific and non-portable" [Undecided,Fix released] <a href="https://launchpad.net/bugs/1852442">https://launchpad.net/bugs/1852442</a></p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - doc-requirements: add missing dep [Joshua Powers]</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> Ok that should do it.</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> maybe best to just pastebin next time</p> -<p>17:43 <code>&lt;robjo&gt;</code> yup</p> -<p>17:43 <code>&lt;blackboxsw&gt;</code> lots of doc changes as you can see. dropping python 2.7 automatic testing</p> -<p>17:44 <code>&lt;blackboxsw&gt;</code> some additional FreeBSD enablement work landed too (thanks Goneri &amp;&amp; meena )</p> -<p>17:44 <code>&lt;blackboxsw&gt;</code> total changelog since last meeting:</p> -<p>17:44 <code>&lt;blackboxsw&gt;</code> #link <a href="https://paste.ubuntu.com/p/Cwnn3SbmWQ/">https://paste.ubuntu.com/p/Cwnn3SbmWQ/</a></p> -<p>17:44 <code>&lt;blackboxsw&gt;</code> much better</p> -<p>17:44 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>17:45 <code>&lt;blackboxsw&gt;</code> We've dusted off our shoes and will get back into using our Trello board more frequently for the immediate updates for what we are currently working.</p> -<p>17:45 <code>&lt;blackboxsw&gt;</code> New Year's resolution and all</p> -<p>17:45 <code>&lt;blackboxsw&gt;</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>17:46 <code>&lt;blackboxsw&gt;</code> expect to see more cloud-init cards migrating through the lanes of the board. Expectation as well is that we'll drop the backlog and ideas lanes and keep the board a simple kanban of what is in progress, review and done</p> -<p>17:47 <code>&lt;blackboxsw&gt;</code> Also note I'm going to drop the community charter lane and create bugs for each item, tagging them 'bitesize' so that quick drivebys of developers that want to contribute can search bugs for those straightforward tasks</p> -<p>17:47 <code>&lt;blackboxsw&gt;</code> that said, some high level goals upstream is working:</p> -<p>17:48 <code>&lt;blackboxsw&gt;</code> - cloud-init one-shot daemon work</p> -<p>17:48 <code>&lt;blackboxsw&gt;</code> - cloud-init network hotplug handling</p> -<p>17:48 <code>&lt;blackboxsw&gt;</code> - boot performance improvements</p> -<p>17:49 <code>&lt;blackboxsw&gt;</code> - github automation and tooling improvements for expedited reviews and process</p> -<p>17:50 <code>&lt;blackboxsw&gt;</code> I think that plus reviewing the PR active review queues will keep folks busy for the next 2 weeks :)</p> -<p>17:51 <code>&lt;blackboxsw&gt;</code> we will likely be adding a cloud-init SRU into xenial, bionic, disco, eoan into the mix as well</p> -<p>17:51 <code>&lt;blackboxsw&gt;</code> #topic Community Charter</p> -<p>17:52 <code>&lt;blackboxsw&gt;</code> So generally I'd be pointing to the trello lane "Community low hanging fruit" but I hope to convert those cards to bugs today. So let's say community ongoing efforts fall into two camps"</p> -<p>17:53 <code>&lt;blackboxsw&gt;</code> 1. add json schema validation to missing cloudinit/config/cc_*py modules. ( I think there are about 45 remaining modules that need json schema for syntax validation)</p> -<p>17:53 <code>&lt;blackboxsw&gt;</code> 2. doc scrub and update for datasources in read the docs</p> -<p>17:54 <code>&lt;blackboxsw&gt;</code> All of these items can easily be worked in parallel, which is why they are a good set of tasks for the greater community</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> Expect to find them by searching cloud-init bugs for bitesize tag</p> -<p>17:55 <code>&lt;robjo&gt;</code> With bugs remaining in launchpad, would it be a good idea to have things like the schema validation not as bugs but issues in GitHub?</p> -<p>17:55 <code>&lt;robjo&gt;</code> that would make them more visible IMHO</p> -<p>17:55 <code>&lt;robjo&gt;</code> and those are not really bugs nor is it pressing</p> -<p>17:56 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/">https://bugs.launchpad.net/cloud-init/</a>?field.tag=bitesize</p> -<p>17:57 <code>&lt;blackboxsw&gt;</code> robjo: good suggestion. I think we were trying to avoid the confusion of having two places for bugs (launchpad bugs and github issues) That is a good point though, and maybe it's worth a mailing list discussion to get others to weight in.</p> -<p>17:58 <code>&lt;Odd_Bloke&gt;</code> I would be -1 on enabling issues, we would spend our entire lives telling people to report in Launchpad instead.</p> -<p>17:59 <code>&lt;Odd_Bloke&gt;</code> I totally understand wanting to separate "bugs" and "development tasks", though.</p> -<p>18:00 <code>&lt;Odd_Bloke&gt;</code> But I don't think we have a <em>great</em> way of doing that which doesn't end up with a confusing experience for bug reporters.</p> -<p>18:00 <code>&lt;robjo&gt;</code> True that people will equate issues in GitHub with bugs and thus file problems there rather than launchpad, it's a two edged sword</p> -<p>18:00 <code>&lt;blackboxsw&gt;</code> right, I think designation is there. We could also add a link to community charter bugs to the top-level README.md for the github project. Just so there is a close breadcrumb in github to get to those items</p> -<p>18:01 <code>&lt;Odd_Bloke&gt;</code> Our plan is to assess how this is working in a month or two, so if it's not working well then we can figure something else out.</p> -<p>18:01 <code>&lt;blackboxsw&gt;</code> I think the designation of "community development tasks" is there by using bitesize tag or some equivalent</p> -<p>18:02 <code>&lt;blackboxsw&gt;</code> #ACTION bbsw seed initial community charter bitesize bugs</p> -<p>18:02 * meetingology bbsw seed initial community charter bitesize bugs</p> -<p>18:02 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>18:02 <code>&lt;robjo&gt;</code> Well, "community development tasks" is a bit mis-leading, after all the core team should be part of the "community" right?</p> -<p>18:03 <code>&lt;robjo&gt;</code> So everything is really a "community development tasks", just that some things are easier than others ;)</p> -<p>18:03 <code>&lt;blackboxsw&gt;</code> robjo: yes absolutely. right... I've seen some projects use 'goodfirstbug' or something like that too</p> -<p>18:04 <code>&lt;blackboxsw&gt;</code> just something to reduce the barrier to involvement for anyone wanting to contribute</p> -<p>18:05 <code>&lt;blackboxsw&gt;</code> and yes, core team should be accountable to work on some of those community charter tasks when time permits</p> -<p>18:05 <code>&lt;robjo&gt;</code> Yes, I think it is important to label the "easy" stuff to help people find a place to get started</p> -<p>18:05 <code>&lt;blackboxsw&gt;</code> so that hopefully next cloud-init summit we can set a charter for something else</p> -<p>18:06 <code>&lt;robjo&gt;</code> just based on experience there are a lot of people that are sensitive to wording and we don't really want to get into the bikeshedding that comes along with such situations</p> -<p>18:07 <code>&lt;blackboxsw&gt;</code> for those reading, office hours is a time of open and unstructured discussion. core cloud-init devs will have eyes on the channel to field questions, concerns, feature or bug discussions. Participate at will. In the absence of any ongoing discussions, upstream will groom/review the active review queue @ <a href="https://git.io/JeVed">https://git.io/JeVed</a> |</p> -<p>18:09 <code>&lt;Odd_Bloke&gt;</code> Honestly losing my mind over this bug: <a href="https://bugs.launchpad.net/cloud-init/+bug/1858615">https://bugs.launchpad.net/cloud-init/+bug/1858615</a></p> -<p>18:09 <code>&lt;ubot5&gt;</code> Ubuntu bug 1858615 in cloud-init "Fail to boot when NoCloud datasource is included" [Undecided,New]</p> -<p>18:09 <code>&lt;Odd_Bloke&gt;</code> The board reboots if you use dmidecode!</p> -<p>18:10 <code>&lt;Odd_Bloke&gt;</code> smoser: As you said, that's a regression. Do you think it follows that the fix should be in cloud-init?</p> -<p>18:10 <code>&lt;Odd_Bloke&gt;</code> Because I don't know how you deal with something that broken from where we are in the stack. :/</p> -<p>18:10 <code>&lt;Odd_Bloke&gt;</code> (Unless we think this is enough evidence that we can't reliably use dmidecode on aarch64, then I guess it is on us to stop doing that. :( )</p> -<p>18:10 <code>&lt;robjo&gt;</code> This was probably in the e-mail by rharper I have not yet read, but I'll ask anyway ;)</p> -<p>18:11 <code>&lt;robjo&gt;</code> I think I had some pending merge proposals in launchpad and patches, did these "magically" make their way into GitHub? DO I need to sort out where hings were?</p> -<p>18:11 <code>&lt;smoser&gt;</code> i've heard "board reboots if you use dmidecode" before.</p> -<p>18:12 <code>&lt;smoser&gt;</code> and maybe even cloud-init skipped calling dmidecode on aarch64 to avoid that.</p> -<p>18:12 <code>&lt;smoser&gt;</code> but that is sheer non-sense</p> -<p>18:12 <code>&lt;Odd_Bloke&gt;</code> Very glad that boards like this are going to be in the walls of every building in 5 years. ;)</p> -<p>18:12 <code>&lt;smoser&gt;</code> umm..... fix your hardware ?</p> -<p>18:13 <code>&lt;blackboxsw&gt;</code> other dmidecode issues on other hardware here too <a href="https://bugs.launchpad.net/qemu/+bug/1243287">https://bugs.launchpad.net/qemu/+bug/1243287</a></p> -<p>18:13 <code>&lt;ubot5&gt;</code> Ubuntu bug 1243287 in QEMU "[KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail" [Undecided,Fix released]</p> -<p>18:13 <code>&lt;smoser&gt;</code> its more forgivable because dmidecode is priviledged but i swear that all it does is <em>read</em> /dev/mem</p> -<p>18:16 <code>&lt;blackboxsw&gt;</code> robjo: for your pending merge proposals we'd like to see you propose against github if possible. Looking for a run of ./tools/migrate-lp-user-to-github robjo <code>&lt;your_GITHUB_USERNAME&gt;</code> to get your github user included as a CLA signer</p> -<p>18:17 <code>&lt;blackboxsw&gt;</code> then we have Conributor License Agreement accountability and can start merging those branches on the github side</p> -<p>18:17 <code>&lt;robjo&gt;</code> Yesh I haven't migrated to the GitHub repo.... even in 2020 the 24 hour/day limitation remains, darn it ;)</p> -<p>18:17 <code>&lt;robjo&gt;</code> I'll get at least my migration to GitHub done this week, possibly even this afternoon</p> -<p>18:18 <code>&lt;blackboxsw&gt;</code> heh, absolutely, and actually I mistyped your migrate cmd: ./tools/migrate-lp-user-to-github rjschwei <code>&lt;YOUR_GITHUB_USERNAME&gt;</code></p> -<p>18:39 <code>&lt;blackboxsw&gt;</code> ok think that about wraps the meeting for today. Happy new year folks! Thanks for dropping in!</p> -<p>18:39 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2019-12-10T17:17:00+00:002019-12-10T17:17:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2019-12-10:/status-2019-12-10.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 10 Dec at 17:17 &mdash; 18:16 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-12-10-17.17.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-12-10-17.17.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 17:22.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-11-26.html#status-2019-11-26">https://cloud-init.github.io/status-2019-11-26.html#status-2019-11-26 …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 10 Dec at 17:17 &mdash; 18:16 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-12-10-17.17.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-12-10-17.17.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 17:22.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-11-26.html#status-2019-11-26">https://cloud-init.github.io/status-2019-11-26.html#status-2019-11-26</a> </li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 17:28.</p> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 17:31.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://lists.launchpad.net/cloud-init/msg00236.html">https://lists.launchpad.net/cloud-init/msg00236.html</a> </li> -<li><strong>LINK</strong>: <a href="https://cloudinit.readthedocs.io/en/latest/topics/hacking.html">https://cloudinit.readthedocs.io/en/latest/topics/hacking.html</a> </li> -</ul> -<h3>Community Charter</h3> -<p>The discussion about "Community Charter" started at 17:40.</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>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 17:45.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://git.io/JeVed">https://git.io/JeVed</a> </li> -<li><strong>ACTION</strong>: rharper confirm no concerns on <a href="https://github.com/canonical/cloud-init/pull/42">https://github.com/canonical/cloud-init/pull/42</a> and that PR can land.</li> -<li><strong>ACTION</strong>: upstream core-devs to decide about whether a PR can land if any upstream dev still has 'requested changes'</li> -</ul> -<h2>Vote results</h2> -<h2>Action items, by person</h2> -<ul> -<li>rharper</li> -<li>rharper confirm no concerns on <a href="https://github.com/canonical/cloud-init/pull/42">https://github.com/canonical/cloud-init/pull/42</a> and that PR can land.</li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (79)</li> -<li>meetingology (7)</li> -<li>meena (5)</li> -<li>ubot5 (3)</li> -<li>Odd_Bloke (2)</li> -<li>rharper (1)</li> -</ul> -<h2>Full Log</h2> -<p>17:17 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>17:17 <code>&lt;meetingology&gt;</code> Meeting started Tue Dec 10 17:17:14 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>17:17 <code>&lt;meetingology&gt;</code> </p> -<p>17:17 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>17:18 <code>&lt;blackboxsw&gt;</code> Welcome folks to another cloud-init status meeting. Probably the last one of the year I presume due to upcoming Holidays in two weeks</p> -<p>17:18 <code>&lt;blackboxsw&gt;</code> #chair rharper</p> -<p>17:18 <code>&lt;meetingology&gt;</code> Current chairs: blackboxsw rharper</p> -<p>17:18 <code>&lt;blackboxsw&gt;</code> #chair Odd_Bloke</p> -<p>17:18 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw rharper</p> -<p>17:18 <code>&lt;rharper&gt;</code> o/</p> -<p>17:18 <code>&lt;blackboxsw&gt;</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>17:19 <code>&lt;blackboxsw&gt;</code> Let's start the meeting with setting the next meeting time</p> -<p>17:19 <code>&lt;blackboxsw&gt;</code> day/time</p> -<p>17:20 <code>&lt;blackboxsw&gt;</code> I think most of upstream is out the last two weeks of December. Shall we try January 7th?</p> -<p>17:20 <code>&lt;blackboxsw&gt;</code> Anyone opposed can voice their discontent as I remember the keystrokes to set the topic of the channel ;)_</p> -<p>17:21 <code>&lt;blackboxsw&gt;</code> I also dropped 19.3 upstream release date from the channel topic as "that's soooo November"</p> -<p>17:22 <code>&lt;blackboxsw&gt;</code> topics for this round: Feel free to interject/suggest other topics 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>17:22 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>17:22 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>17:23 <code>&lt;blackboxsw&gt;</code> and oops, forgot to publish meeting minutes from last session.</p> -<p>17:23 <code>&lt;blackboxsw&gt;</code> doing that now.</p> -<p>17:24 <code>&lt;meena&gt;</code> is it meeting time or did I miss it?</p> -<p>17:25 <code>&lt;Odd_Bloke&gt;</code> meena: It's happening as we speak.</p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> ok sorry for the delay. just pushed published meeting minutes</p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2019-11-26.html#status-2019-11-26">https://cloud-init.github.io/status-2019-11-26.html#status-2019-11-26</a></p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> ok so previous actions from last meeting:</p> -<p>17:28 <code>&lt;blackboxsw&gt;</code> no unresolved actions listed</p> -<p>17:28 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> found via git log --since 11.26.2019</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - dhcp: Support RedHat dhcp rfc3442 lease format for option 121 (#76)</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> [Eric Lafontaine] (LP: #1850642)</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - network_state: handle empty v1 config (#45) (LP: #1852496)</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - Merge pull request #94 from gaughen/patch-1 [Joshua Powers]</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - removed a couple of "the"s [gaughen]</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - docs: fix line length and remove highlighting [Joshua Powers]</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - docs: Add security.md to readthedocs [Joshua Powers]</p> -<p>17:29 <code>&lt;ubot5&gt;</code> Launchpad bug 1850642 in cloud-init "No support for classless-static-routes on centos 7" [Medium,Triaged] <a href="https://launchpad.net/bugs/1850642">https://launchpad.net/bugs/1850642</a></p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - Multiple file fix for AuthorizedKeysFile config (#60) [Eduardo Otubo]</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - Merge pull request #88 from OddBloke/travis [Joshua Powers]</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - Revert "travis: only run CI on pull requests"</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - doc: update links on README.md [Joshua Powers]</p> -<p>17:29 <code>&lt;ubot5&gt;</code> Launchpad bug 1852496 in cloud-init (Ubuntu) "nocloud network-config mishandles empty config" [Low,In progress] <a href="https://launchpad.net/bugs/1852496">https://launchpad.net/bugs/1852496</a></p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - doc: Updates to wording of README.md [Joshua Powers]</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - Add security.md [Joshua Powers]</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - setup.py: Amazon Linux sets libexec to /usr/libexec (#52)</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> [Frederick Lefebvre]</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - Fix linting failure in test_url_helper (#83) [Eric Lafontaine]</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - url_helper: read_file_or_url should pass headers param into readurl</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> (#66) (LP: #1854084)</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - dmidecode: log result <em>after</em> stripping n [Igor Galić]</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - cloud_tests: add azure platform support to integration tests</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> [ahosmanmsft]</p> -<p>17:29 <code>&lt;ubot5&gt;</code> Launchpad bug 1854084 in cloud-init "Headers no longer passed through read_file_or_url" [Undecided,Fix committed] <a href="https://launchpad.net/bugs/1854084">https://launchpad.net/bugs/1854084</a></p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> thanks for all the FreeBSD work landing, utility improvements, caching and doc changes. + the dhcp lease format updates</p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> Generally upstream is doing a fair job of getting reviews to the community for PRs, though lately we've been spending a few cycles on SRU validation for cloud-init 19.4.31 into Ubuntu Xenial, Bionic, Disco and Eoan.</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> expectation is that we should be able to clear this SRU validation today/tomorrow and get back onto the review queue in github for cloud-init</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> most major cloud-platforms have passed validation with no regressions, so risk is low with this release</p> -<p>17:34 <code>&lt;blackboxsw&gt;</code> oops cloud-init 19.3.41 not 19.4.31</p> -<p>17:35 <code>&lt;blackboxsw&gt;</code> there is plenty of work in flight by meena (FreeBSD improvements) and ahosmanMSFT (Azure instance-id work). that we hope to get reviewed and landed.</p> -<p>17:36 <code>&lt;blackboxsw&gt;</code> community notice: Reminder we are working toward a 19.4 upstream release by end of year. So if there are bits/features that you hope to make the cut. please get those branches in shape by next tuesday Decemeber 17th</p> -<p>17:36 <code>&lt;blackboxsw&gt;</code> #link <a href="https://lists.launchpad.net/cloud-init/msg00236.html">https://lists.launchpad.net/cloud-init/msg00236.html</a></p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> community notice: Also a reminder that cloud-inig 19.4 will be the last release that claims official support for py2.7</p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> in January, tip of cloud-init will be allowed to drift from python2.7 support and tox -e py27 will no longer be exercised by upstream CI</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: or rharper anyything else in-progress at the moment?</p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> also, anyone interested in cloud-init development, please run tools/migrate-lp-user-to-github as mentioned in the hacking guide to make sure we can account for the CLA (contributor license agreement) for cloud-init</p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloudinit.readthedocs.io/en/latest/topics/hacking.html">https://cloudinit.readthedocs.io/en/latest/topics/hacking.html</a></p> -<p>17:40 <code>&lt;blackboxsw&gt;</code> #topic Community Charter</p> -<p>17:40 <code>&lt;blackboxsw&gt;</code> reminder on 19.4 release covered above, and getting your github account authorized for cloud-init conributions....</p> -<p>17:41 <code>&lt;Odd_Bloke&gt;</code> Nothing from me!</p> -<p>17:41 <code>&lt;meena&gt;</code> goneri and i have been working on / testing his freebsd render</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> for folks with time to burn and bite-sized branches/fixes. we've got a lane on our trello board that gives a variety of fixes that the community can grab if they are looking for quick suggestions. "Community low-hanging fruit"</p> -<p>17:42 <code>&lt;blackboxsw&gt;</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>17:42 <code>&lt;blackboxsw&gt;</code> meena: Goneri yes and thanks for the continued efforts there. A lot of good is coming out for cloud-init upstream as a result.</p> -<p>17:42 <code>&lt;meena&gt;</code> Goneri removed a lot of code, but from what i gather, that code is still used elsewhere</p> -<p>17:43 <code>&lt;meena&gt;</code> could someone explain why our where our how</p> -<p>17:43 <code>&lt;blackboxsw&gt;</code> as always, any community member is encouraged to review other PRs from devs. All reviews and input welcome.</p> -<p>17:44 <code>&lt;blackboxsw&gt;</code> meena: I'm not sure I follow, are you referring to a specific branch?</p> -<p>17:44 <code>&lt;blackboxsw&gt;</code> or just where stale snapshots or cloud-init code lives on certain distros?</p> -<p>17:45 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>17:45 <code>&lt;blackboxsw&gt;</code> might as well kick the topic and open office hours for general cloud-init discussions, questions, bug/feature work etc.</p> -<p>17:46 <code>&lt;blackboxsw&gt;</code> some upstream devs will have eyes/time available for discussion around anything cloud-init. This time will also be spent grooming the active review queue @ <a href="https://git.io/JeVed">https://git.io/JeVed</a></p> -<p>17:46 <code>&lt;blackboxsw&gt;</code> #link <a href="https://git.io/JeVed">https://git.io/JeVed</a></p> -<p>17:48 <code>&lt;meena&gt;</code> blackboxsw: <a href="https://github.com/canonical/cloud-init/pull/61#pullrequestreview-329139891">https://github.com/canonical/cloud-init/pull/61#pullrequestreview-329139891</a></p> -<p>17:48 <code>&lt;blackboxsw&gt;</code> checking</p> -<p>17:52 <code>&lt;blackboxsw&gt;</code> meena: so Distro._bring_up_interface() is called by Distro._bring_up_interfaces() base class via Distro.apply_network</p> -<p>17:59 <code>&lt;blackboxsw&gt;</code> which is called from Init.apply_network_config which gets run during "cloud-init init" when network is brought up</p> -<p>18:06 <code>&lt;blackboxsw&gt;</code> I think <a href="https://github.com/canonical/cloud-init/pull/42">https://github.com/canonical/cloud-init/pull/42</a> looks ready to merge. rharper has an outstanding "changes requested" but I believe those have been fixed. rharper I'll defer to you on this one</p> -<p>18:08 <code>&lt;blackboxsw&gt;</code> and policy question on reviews: if we get one upstream core-dev +1 can we proceed to land the branch as long as the "changes requested" from other upstream core seem to be resolved?</p> -<p>18:09 <code>&lt;blackboxsw&gt;</code> I'd vote that most recent core-dev on the PR that +1's can squash merge if they see that any prior core-dev's concerns seem to be addressed</p> -<p>18:12 <code>&lt;blackboxsw&gt;</code> I think I'll add an action for next meeting to make sure we iron out review/merge policy so PRs don't sit stale</p> -<p>18:13 <code>&lt;blackboxsw&gt;</code> #action rharper confirm no concerns on <a href="https://github.com/canonical/cloud-init/pull/42">https://github.com/canonical/cloud-init/pull/42</a> and that PR can land.</p> -<p>18:13 * meetingology rharper confirm no concerns on <a href="https://github.com/canonical/cloud-init/pull/42">https://github.com/canonical/cloud-init/pull/42</a> and that PR can land.</p> -<p>18:14 <code>&lt;blackboxsw&gt;</code> #action upstream core-devs to decide about whether a PR can land if any upstream dev still has 'requested changes'</p> -<p>18:14 * meetingology upstream core-devs to decide about whether a PR can land if any upstream dev still has 'requested changes'</p> -<p>18:16 <code>&lt;blackboxsw&gt;</code> ok I <em>think</em> that about wraps the meeting. Merry Christmas, Happy Hanukkah, Happy New Year and all that good stuff. See you all online.</p> -<p>18:16 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2019-11-26T17:23:00+00:002019-11-26T17:23:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2019-11-26:/status-2019-11-26.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 26 Nov at 17:23 &mdash; 19:00 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-11-26-17.23.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-11-26-17.23.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 17:28.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-10-29.html#status-2019-10-29">https://cloud-init.github.io/status-2019-10-29.html#status-2019-10-29 …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 26 Nov at 17:23 &mdash; 19:00 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-11-26-17.23.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-11-26-17.23.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 17:28.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-10-29.html#status-2019-10-29">https://cloud-init.github.io/status-2019-10-29.html#status-2019-10-29</a> </li> -<li><strong>LINK</strong>: <a href="https://lists.launchpad.net/cloud-init/msg00231.html">https://lists.launchpad.net/cloud-init/msg00231.html</a> </li> -<li><strong>LINK</strong>: <a href="https://cloudinit.readthedocs.io/en/latest/topics/hacking.html">https://cloudinit.readthedocs.io/en/latest/topics/hacking.html</a> </li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 17:36.</p> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 17:39.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bug/1854084">https://bugs.launchpad.net/cloud-init/+bug/1854084</a> </li> -<li><strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pull/48">https://github.com/canonical/cloud-init/pull/48</a> </li> -<li><strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pull/47">https://github.com/canonical/cloud-init/pull/47</a> </li> -</ul> -<h3>Community Charter</h3> -<p>The discussion about "Community Charter" started at 17:46.</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 17:52.</p> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 17:52.</p> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (124)</li> -<li>ubot5 (16)</li> -<li>ahosmanMSFT (5)</li> -<li>meena (5)</li> -<li>chillysurfer (5)</li> -<li>meetingology (4)</li> -<li>Goneri (1)</li> -<li>Odd_Bloke (0)</li> -</ul> -<h2>Full Log</h2> -<p>17:23 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>17:23 <code>&lt;meetingology&gt;</code> Meeting started Tue Nov 26 17:23:40 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>17:23 <code>&lt;meetingology&gt;</code> </p> -<p>17:23 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>17:24 <code>&lt;blackboxsw&gt;</code> #chair Odd_Bloke</p> -<p>17:24 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw</p> -<p>17:24 <code>&lt;blackboxsw&gt;</code> Hi folks welcome to another cloud-init status meeting.</p> -<p>17:24 <code>&lt;blackboxsw&gt;</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>17:25 <code>&lt;blackboxsw&gt;</code> And as you've likely heard, we are shifting this meeting by +1 hr for the season to avoid meeting collisions with some of the upstream devs</p> -<p>17:25 <code>&lt;blackboxsw&gt;</code> I'll set the topic for next meeting so we don't forget</p> -<p>17:28 <code>&lt;blackboxsw&gt;</code> so Dec 10th, two weeks from today, same time as today</p> -<p>17:28 <code>&lt;blackboxsw&gt;</code> without further ado, let's jump into things</p> -<p>17:28 <code>&lt;blackboxsw&gt;</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>17:28 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>17:28 <code>&lt;blackboxsw&gt;</code> I'm going from our last meeting minutes at the following url</p> -<p>17:28 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2019-10-29.html#status-2019-10-29">https://cloud-init.github.io/status-2019-10-29.html#status-2019-10-29</a></p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> blackboxsw to 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>17:29 <code>&lt;blackboxsw&gt;</code> I did forward the proper Microsoft channel contact to other Microsoft dev teams working on cloud-init</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> so I think thats COMPLETE</p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> Also to note is that cloud image builds though are still stale for Azure &amp; Ec2 on focal. There are a couple of bugs in the image build process that Canonical's cloud image team is sorting to get those image builders unblocked</p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> Xenial, Bionic, Eoan images all look up to date</p> -<p>17:32 <code>&lt;chillysurfer&gt;</code> bug reports and issues are still going to be reported through launchpad right?</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> previous-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. Resolved. Upstream decided that it was going to be a bit of a maintenance cost to have a full table of all distributions and all versions of cloud-init as well as the planned support plan.</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> chillysurfer: +1 yes please do. file away and we'll tackle that</p> -<p>17:32 <code>&lt;chillysurfer&gt;</code> blackboxsw: great thanks!</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> previous-action: mailing list update to cloud-init community about procedure/timeline for migration to github. rharper took care of that per</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> #link <a href="https://lists.launchpad.net/cloud-init/msg00231.html">https://lists.launchpad.net/cloud-init/msg00231.html</a></p> -<p>17:34 <code>&lt;blackboxsw&gt;</code> Again for folks, we have moved cloud-init upstream to github for code and CI. Launchpad still being used for package build recipes and bugs/ issues</p> -<p>17:35 <code>&lt;blackboxsw&gt;</code> If you have signed the CLA (thanks ahosmanMSFT) then we need to link your github account to the Lauchpad username you signed the CLA with. See the hacking doc for more information</p> -<p>17:35 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloudinit.readthedocs.io/en/latest/topics/hacking.html">https://cloudinit.readthedocs.io/en/latest/topics/hacking.html</a></p> -<p>17:35 <code>&lt;blackboxsw&gt;</code> Think that wraps actions.</p> -<p>17:36 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>17:36 <code>&lt;meena&gt;</code> I've been very slowly working towards better freebsd support</p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> The following branches have landed in tip since last meeting: via git log --since 10.29.2019</p> -<p>17:37 <code>&lt;meena&gt;</code> Goneri has moved his network patch over to github, and a NetBSD patch, tok</p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> - tools: migrate-lp-user-to-github removes repo_dir if created (#35)</p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> - Correct jumbled documentation for cc_set_hostname module (#64)</p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> [do3meli] (LP: #1853543)</p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> - FreeBSD: fix for get_linux_distro() and lru_cache (#59)</p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> [Igor Galić] (LP: #1815030)</p> -<p>17:37 <code>&lt;ubot5&gt;</code> Launchpad bug 1853543 in cloud-init "jumbled documentation for cc_set_hostname module" [Undecided,Fix committed] <a href="https://launchpad.net/bugs/1853543">https://launchpad.net/bugs/1853543</a></p> -<p>17:37 <code>&lt;ubot5&gt;</code> Launchpad bug 1815030 in cloud-init "FreeBSD: Unable to determine distribution" [Undecided,Fix committed] <a href="https://launchpad.net/bugs/1815030">https://launchpad.net/bugs/1815030</a></p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> bah got kicked. let's try that again</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - tools: migrate-lp-user-to-github removes repo_dir if created (#35)</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> 10:37 - Correct jumbled documentation for cc_set_hostname module (#64)</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> 10:37 [do3meli] (LP: #1853543)</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> 10:37 - FreeBSD: fix for get_linux_distro() and lru_cache (#59)</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> 10:37 [Igor Galić] (LP: #1815030)</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> 10:37 - lp-to-git-users: adding do3meli [Dominic Schlegel]</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> 10:37 - ec2: Add support for AWS IMDS v2 (session-oriented) (#55)</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> 10:37 - tests: Fix cloudsigma tests when no dmidecode data is present. (#57)</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> 10:37 - net: IPv6, accept_ra, slaac, stateless (#51)</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> 10:37 [Harald] (LP: #1806014, #1808647)</p> -<p>17:38 <code>&lt;ubot5&gt;</code> Launchpad bug 1808647 in cloud-init "cloud-init hard codes IPV6_AUTOCONF=no, which prevents EC2 instances from getting a v6 default gateway if NetworkManager is disabled" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1808647">https://launchpad.net/bugs/1808647</a></p> -<p>17:38 <code>&lt;ubot5&gt;</code> Launchpad bug 1806014 in cloud-init "[Centos] IPV6_AUTOCONF=no when using dhcp6" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1806014">https://launchpad.net/bugs/1806014</a></p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - docs: Update the configdrive datasource links (#44)</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> [Joshua Powers] (LP: #1852461)</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - lp-to-git-users: adding PengpengSun [Pengpeng Sun]</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - lp-to-git-users: adding trstringer [Thomas Stringer]</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - lp-to-git-users: adding hjensas [Harald Jensås]</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - distro: correctly set usr_lib_exec path for FreeBSD distro (#40)</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> [Igor Galić] (LP: #1852491)</p> -<p>17:38 <code>&lt;ubot5&gt;</code> Launchpad bug 1852461 in cloud-init "Broken links in config-drive docs on RTD" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1852461">https://launchpad.net/bugs/1852461</a></p> -<p>17:38 <code>&lt;ubot5&gt;</code> Launchpad bug 1852491 in cloud-init "usr_lib_exec path is wrong on FreeBSD" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1852491">https://launchpad.net/bugs/1852491</a></p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - azure: support secondary ipv6 addresses (#33)</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - Fix metadata check when local-hostname is null (#32)</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> [Mark Goddard] (LP: #1852100)</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - Merge pull request #38 from blackboxsw/cleanup/run-ci-on-pull-request</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - switch default FreeBSD salt minion pkg from py27 to py36</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> [Dominic Schlegel]</p> -<p>17:38 <code>&lt;ubot5&gt;</code> Launchpad bug 1852100 in cloud-init "Cloud-init fails if metadata local-hostname is null" [Undecided,In progress] <a href="https://launchpad.net/bugs/1852100">https://launchpad.net/bugs/1852100</a></p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - lp-to-git-users: adding igalic [Igor Galić]</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - travis: only run CI on pull requests</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - add data-server dns entry as new metadata server detection [Joshua Hügli]</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - lp-to-git-users: adding chrisglass [Chris Glass]</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - lp-to-git-users: adding larsks [Lars Kellogg-Stedman]</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - Merge pull request #31 from raharper/fix/pycodestyle-tip</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - pycodestyle: remove unused local variable</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - reporting: Using a uuid to enforce uniqueness on the KVP keys. [momousta]</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - docs: touchups in rtd intro and README.md</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - doc: update launchpad git refs to github</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - tools: migrate script needs to write tools/.lp-to-git-user</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - github: drop pull-request template to prepare for migration</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - tools: add migrate-lp-user-to-github script to link LP to github</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - github: new basic project readme</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - Release 19.3 (LP: #1851428)</p> -<p>17:38 <code>&lt;ubot5&gt;</code> Launchpad bug 1851428 in cloud-init "Release 19.3" [Medium,In progress] <a href="https://launchpad.net/bugs/1851428">https://launchpad.net/bugs/1851428</a></p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - azure: support matching dhcp route-metrics for dual-stack ipv4 ipv6</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> (LP: #1850308)</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - configdrive: fix subplatform config-drive for /config-drive source</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> [David Kindred] (LP: #1849731)</p> -<p>17:38 <code>&lt;ubot5&gt;</code> Launchpad bug 1850308 in cloud-init "cloud-init on azure with dual stack needs to add route-metric for dhcp6 also" [High,Fix committed] <a href="https://launchpad.net/bugs/1850308">https://launchpad.net/bugs/1850308</a></p> -<p>17:38 <code>&lt;ubot5&gt;</code> Launchpad bug 1849731 in cloud-init "Introduction of subplatform around 18.5 broke ConfigDrive" [Undecided,Fix committed] <a href="https://launchpad.net/bugs/1849731">https://launchpad.net/bugs/1849731</a></p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> - DataSourceSmartOS: reconfigure network on each boot</p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> [Mike Gerdts] (LP: #1765801)</p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> - Add config for ssh-key import and consuming user-data [Pavel Zakharov]</p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> - net: fix subnet_is_ipv6() for stateless|stateful</p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> [Harald Jensås] (LP: #1848690)</p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> - OVF: disable custom script execution by default [Xiaofeng Wang]</p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> - cc_puppet: Implement csr_attributes.yaml support [Matthias Baur]</p> -<p>17:39 <code>&lt;ubot5&gt;</code> Launchpad bug 1765801 in cloud-init "network should be optionally reconfigured on every boot" [Undecided,Fix committed] <a href="https://launchpad.net/bugs/1765801">https://launchpad.net/bugs/1765801</a></p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> - cloud-init.service: on centos/fedora/redhat wait on</p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> NetworkManager.service (LP: #1843334)</p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> - azure: Do not lock user on instance id change</p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> [Sam Eiderman] (LP: #1849677)</p> -<p>17:39 <code>&lt;ubot5&gt;</code> Launchpad bug 1848690 in cloud-init "subnet_is_ipv6() function does not work for types ipv6_dhcpv6-stateless|stateful" [Undecided,Fix committed] <a href="https://launchpad.net/bugs/1848690">https://launchpad.net/bugs/1848690</a></p> -<p>17:39 <code>&lt;ubot5&gt;</code> Launchpad bug 1843334 in cloud-init "Change location of DHCP leases in CloudStack provider as it doesn't work for RHEL8" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1843334">https://launchpad.net/bugs/1843334</a></p> -<p>17:39 <code>&lt;ubot5&gt;</code> Launchpad bug 1849677 in cloud-init "azure locks existing user if instance id changes" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1849677">https://launchpad.net/bugs/1849677</a></p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>17:40 <code>&lt;ahosmanMSFT&gt;</code> Looking into this</p> -<p>17:40 <code>&lt;ahosmanMSFT&gt;</code> Launchpad bug 1849677 in cloud-init "azure locks existing user if instance id changes" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1849677">https://launchpad.net/bugs/1849677</a></p> -<p>17:40 <code>&lt;ubot5&gt;</code> Ubuntu bug 1849677 in cloud-init "azure locks existing user if instance id changes" [Medium,Fix committed]</p> -<p>17:40 <code>&lt;blackboxsw&gt;</code> As meena mentioned there is a lot of work going on to improve FreeBSD support.</p> -<p>17:40 <code>&lt;blackboxsw&gt;</code> Thanks do3meli and meena for that herculean effort</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> ahosmanMSFT: also has be working on getting Azure CI up and running. That branch will land just as soon as this meeting is over</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> we also have landed a significant AWS feature for IMDSv2.</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> It looks like we'll have a bug to sort on that front</p> -<p>17:42 <code>&lt;chillysurfer&gt;</code> bug report just opened up</p> -<p>17:42 <code>&lt;chillysurfer&gt;</code> <a href="https://bugs.launchpad.net/cloud-init/+bug/1854084">https://bugs.launchpad.net/cloud-init/+bug/1854084</a></p> -<p>17:42 <code>&lt;ubot5&gt;</code> Ubuntu bug 1854084 in cloud-init "Headers no longer passed through read_file_or_url" [Undecided,New]</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> thanks chillysurfer !</p> -<p>17:43 <code>&lt;blackboxsw&gt;</code> will get on that today and confirm</p> -<p>17:43 <code>&lt;chillysurfer&gt;</code> blackboxsw: great thanks! let me know what you think when you know some things</p> -<p>17:43 <code>&lt;blackboxsw&gt;</code> will do</p> -<p>17:44 <code>&lt;blackboxsw&gt;</code> also in the "In progress" topic are the WIP branches that rharper has up to lay ground work for opting in to cloud-init hotplug support</p> -<p>17:45 <code>&lt;blackboxsw&gt;</code> #link <a href="https://github.com/canonical/cloud-init/pull/48">https://github.com/canonical/cloud-init/pull/48</a></p> -<p>17:45 <code>&lt;blackboxsw&gt;</code> #link <a href="https://github.com/canonical/cloud-init/pull/47">https://github.com/canonical/cloud-init/pull/47</a></p> -<p>17:45 <code>&lt;blackboxsw&gt;</code> we'll be trying to pull in hotplug functionality into this cycle, so expect work land on that front before 19.4 I'm guessing</p> -<p>17:45 <code>&lt;blackboxsw&gt;</code> sorry I mean version 20.1</p> -<p>17:46 <code>&lt;blackboxsw&gt;</code> ok next topic</p> -<p>17:46 <code>&lt;blackboxsw&gt;</code> #topic Community Charter</p> -<p>17:46 <code>&lt;meena&gt;</code> i want to test Goneri's network <a href="https://github.com/canonical/cloud-init/pull/61">https://github.com/canonical/cloud-init/pull/61</a> , but a prerequisite to make that easier is <a href="https://github.com/canonical/cloud-init/pull/42">https://github.com/canonical/cloud-init/pull/42</a> and it appears only rharper knows how to write tests for that part of the code</p> -<p>17:47 <code>&lt;meena&gt;</code> what's hotplug support mean in this context?</p> -<p>17:48 <code>&lt;blackboxsw&gt;</code> This Community Charter topic is a placeholder to remind anyone with some spare cycles that as a community anyone can drop in for low-hanging fruit or discrete tasks that will contribute to a better cloud-init</p> -<p>17:48 <code>&lt;blackboxsw&gt;</code> the community charter is currently:</p> -<p>17:48 <code>&lt;blackboxsw&gt;</code> 1. updated datasource docs</p> -<p>17:48 <code>&lt;blackboxsw&gt;</code> 2. get json schema implementation writting for each cloudinit.config.cc_*py module</p> -<p>17:49 <code>&lt;Goneri&gt;</code> meena, I can generate some prebuilt images with my last patch</p> -<p>17:49 <code>&lt;blackboxsw&gt;</code> those items are cards on our trello board in the community low-hanging-fruit lane that anyone grab and work</p> -<p>17:49 <code>&lt;blackboxsw&gt;</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>17:50 <code>&lt;blackboxsw&gt;</code> ... sorry meena, needed to finish my thought. so we'd like review and closure on 42?</p> -<p>17:50 <code>&lt;blackboxsw&gt;</code> &gt;<code>&gt;</code> what's hotplug support mean in this context? hotplug network device events currently would be the baseline.</p> -<p>17:51 <code>&lt;blackboxsw&gt;</code> so network config would be rewritten as devices show up or disappear</p> -<p>17:51 <code>&lt;blackboxsw&gt;</code> if someone opts into cloud-init controlling the running network config post-boot</p> -<p>17:52 <code>&lt;blackboxsw&gt;</code> #topic Upcoming Meetings</p> -<p>17:52 <code>&lt;blackboxsw&gt;</code> as set earlier. Dec 10th for another status meeting at this hour</p> -<p>17:52 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>17:53 <code>&lt;blackboxsw&gt;</code> This time is a chance for open discussions really on any cloud-init topic. bugs, issues, branches that need review etc. In the absence of other discussion, devs will be hitting the review queue to chip away at existing PRs to keep them from getting stale</p> -<p>17:56 <code>&lt;meena&gt;</code> blackboxsw: yes, please, 42 fix would be good</p> -<p>17:59 <code>&lt;blackboxsw&gt;</code> ok looking now</p> -<p>17:59 <code>&lt;blackboxsw&gt;</code> ahosmanMSFT: I'm landing your Azure CI first</p> -<p>18:04 <code>&lt;blackboxsw&gt;</code> ahosmanMSFT: would you like to provide me with a bit more information in the commit message <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> for enabling Azure integration testing? the 'commit message' in the UI will be the final message shown in cloud-init logs and it might be nice to have a bit more context</p> -<p>18:04 <code>&lt;ahosmanMSFT&gt;</code> blackboxsw Adding now</p> -<p>18:04 <code>&lt;blackboxsw&gt;</code> thank you sir</p> -<p>18:14 <code>&lt;ahosmanMSFT&gt;</code> blackboxsw take a look and let me know if I should add anything</p> -<p>18:15 <code>&lt;ahosmanMSFT&gt;</code> Added Azure to cloud tests supporting upstream integration testing. This Implements the inherited platform classes, Azure configurationsto release/platform, and docs on how to run Azure CI.</p> -<p>18:44 <code>&lt;blackboxsw&gt;</code> meena: I may come up with an alternative suggestion to address smoser's suggestion to run dmidecode once. it's a bit of a lift though as dmidecode output isn't structured very easy to parse</p> -<p>19:00 <code>&lt;blackboxsw&gt;</code> ahh I should close out the meeting</p> -<p>19:00 <code>&lt;blackboxsw&gt;</code> Thanks folks for attending. Until next time use the IRC channel or mailing list</p> -<p>19:00 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2019-10-29T16:20:00+00:002019-10-29T16:20:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2019-10-29:/status-2019-10-29.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 29 Oct at 16:20 &mdash; 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></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 29 Oct at 16:20 &mdash; 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>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:20 <code>&lt;meetingology&gt;</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>&lt;meetingology&gt;</code> </p> -<p>16:20 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> Boo! Welcome to the Halloween edition of cloud-init bi-weekly status meeting</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #chair rharper</p> -<p>16:20 <code>&lt;meetingology&gt;</code> Current chairs: blackboxsw rharper</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #chair Odd_Bloke</p> -<p>16:20 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw rharper</p> -<p>16:21 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> So that we don't forget, let's set the topic for next status meeting.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: rharper does 11/12 look good?</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> as in, no holidays etc?</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> ok topic updated. Any concerns we can change it and send out an email to the mailing list</p> -<p>16:26 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> I have three actions from last meeting</p> -<p>16:26 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;chillysurfer&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> thx chillysurfer :)</p> -<p>16:31 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;YEAR&gt;</code>.<code>&lt;minor_release_number&gt;</code> where minor_release_number will be [1-4]</p> -<p>16:34 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> ok long-winded. But I think that was our actions from last cloud-init status meeting.</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> next topic</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> The following branches have landed in tip since last meeting: via git log --since 2019-10-08</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - net/netplan: use ipv6-mtu key for specifying ipv6 mtu values</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - Fix usages of yaml, and move yaml_dump to safeyaml.dumps. (LP: #1849640)</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - exoscale: Increase url_max_wait to 120s. [Chris Glass]</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - net/sysconfig: fix available check on SUSE distros</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> [Robert Schweikert] (LP: #1849378)</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - docs: Fix incorrect Azure IMDS IP address [Joshua Powers] (LP: #1849508)</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - introduce .travis.yml</p> -<p>16:37 <code>&lt;ubot5&gt;</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>&lt;blackboxsw&gt;</code> - net: enable infiniband support in eni and sysconfig renderers</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> [Darren Birkett] (LP: #1847114)</p> -<p>16:37 <code>&lt;ubot5&gt;</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>&lt;blackboxsw&gt;</code> - guestcust_util: handle special characters in config file [Xiaofeng Wang]</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - fix some more typos in comments [Dominic Schlegel]</p> -<p>16:37 <code>&lt;ubot5&gt;</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>&lt;blackboxsw&gt;</code> - replace any deprecated log.warn with log.warning</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> [Dominic Schlegel] (LP: #1508442)</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - net: handle openstack dhcpv6-stateless configuration</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> [Harald Jensås] (LP: #1847517)</p> -<p>16:37 <code>&lt;ubot5&gt;</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>&lt;blackboxsw&gt;</code> - Add .venv/ to .gitignore [Dominic Schlegel]</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - Small typo fixes in code comments. [Dominic Schlegel]</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - cloud_test/lxd: Retry container delete a few times</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - Add Support for e24cloud to Ec2 datasource. (LP: #1696476)</p> -<p>16:37 <code>&lt;ubot5&gt;</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>&lt;ubot5&gt;</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>&lt;ubot5&gt;</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>&lt;blackboxsw&gt;</code> some good incremental improvements on SuSE, FreeBSD,Ubuntu Azure, Ec2, OpenStack and Exoscale</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> Thanks Dominic, Robert, XiaoFeng, Harald and Darren and Scott for the contibutions this round!</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:41 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> And the active review queue for cloud-init is a good representation of what should land shortly.</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> #link <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a></p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> The following work-streams are currently in progress:</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> - CI for Azure (thanks ahosmanMSFT)</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> - Openstack networking v2 support (which allows openstack to talk v2 network config 'netplan' )</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> - Azure async disk mounts</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> - cloud-init boot performance improvements</p> -<p>16:46 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> We'll be able to review some of the outstanding branches during Office hours today</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> #topic Community Charter</p> -<p>16:50 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;tribaal&gt;</code> That's nice!</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> all help is appreciated especially from the datasource owners</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> \o tribaal.</p> -<p>16:52 <code>&lt;tribaal&gt;</code> o/</p> -<p>16:53 <code>&lt;tribaal&gt;</code> sorry, I'm following along, didn't mean to interrupt</p> -<p>16:53 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> no worries, interruptions welcome</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> think that about wraps up community charter.</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> two to topics to go</p> -<p>16:57 <code>&lt;blackboxsw&gt;</code> #topic Upcoming meetings</p> -<p>16:57 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> #topic Upcoming Releases</p> -<p>16:59 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> Immediately after release, we'll publish to Ubuntu's devel release Focal Fossa and our copr repo</p> -<p>16:59 <code>&lt;tribaal&gt;</code> nice! this answers one of the questions I had coming in today :)</p> -<p>16:59 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> good deal tribaal</p> -<p>17:00 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> <em>schedule</em> even</p> -<p>17:00 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>17:01 <code>&lt;blackboxsw&gt;</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>&lt;tribaal&gt;</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>&lt;tribaal&gt;</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>&lt;blackboxsw&gt;</code> tribaal: yep sorry, I mentioned earlier, but should have mentioned in the last topic</p> -<p>17:03 <code>&lt;tribaal&gt;</code> no worries</p> -<p>17:03 <code>&lt;tribaal&gt;</code> it's the logical follow-up to a release - so it was surely implied</p> -<p>17:04 <code>&lt;blackboxsw&gt;</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>&lt;tribaal&gt;</code> blackboxsw: do you know how/when cloud-init lands in other distros, as a matter of curiosity?</p> -<p>17:04 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> tribaal: robjo knows for SLES. otubo (hrm not here today) is managing RHEL/CentOS release schedules</p> -<p>17:06 <code>&lt;blackboxsw&gt;</code> and debian is trying to shore up to 19.X I believe.</p> -<p>17:06 <code>&lt;tribaal&gt;</code> ack</p> -<p>17:06 <code>&lt;blackboxsw&gt;</code> but I think other distros are delayed (for good reasons: testing/validation/stability/etc).</p> -<p>17:07 <code>&lt;tribaal&gt;</code> sure, that would make sense</p> -<p>17:07 <code>&lt;tribaal&gt;</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>&lt;blackboxsw&gt;</code> or somewhere</p> -<p>17:07 <code>&lt;tribaal&gt;</code> that would be incredibly useful to us :)</p> -<p>17:08 <code>&lt;blackboxsw&gt;</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>&lt;tribaal&gt;</code> tracking where and when our new datasource is available is a bit of a mystery right now :)</p> -<p>17:08 <code>&lt;tribaal&gt;</code> (except for Ubuntus)</p> -<p>17:09 <code>&lt;blackboxsw&gt;</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>&lt;tribaal&gt;</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>&lt;blackboxsw&gt;</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>&lt;tribaal&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> tribaal: yeah let me restate the action then</p> -<p>17:12 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> per scheduling we at least could start filling in some gaps there on cloud-init planned distro releases</p> -<p>17:13 <code>&lt;tribaal&gt;</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>&lt;tribaal&gt;</code> is that something we can do ourselves?</p> -<p>17:13 <code>&lt;tribaal&gt;</code> (code wise at least)</p> -<p>17:14 <code>&lt;blackboxsw&gt;</code> tribaal: codewise, if you are talking about manual tests, we generally run something like the following:</p> -<p>17:14 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> oops wrong paste</p> -<p>17:15 <code>&lt;blackboxsw&gt;</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>&lt;tribaal&gt;</code> oh, I see</p> -<p>17:16 <code>&lt;tribaal&gt;</code> so thankfully it's only manual in the "manually run a script" sense :)</p> -<p>17:16 <code>&lt;blackboxsw&gt;</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>&lt;tribaal&gt;</code> yes, that would work (myself, and a handful of colleagues would be happy to I guess)</p> -<p>17:17 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;tribaal&gt;</code> ah nice, that makes sense</p> -<p>17:19 <code>&lt;blackboxsw&gt;</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>&lt;tribaal&gt;</code> yeah that sounds like a good first step, and we can expand later on if/when needed</p> -<p>17:24 <code>&lt;blackboxsw&gt;</code> +1 tribaal</p> -<p>17:24 <code>&lt;blackboxsw&gt;</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>&lt;tribaal&gt;</code> yeah that was a crazy coincidence</p> -<p>17:25 <code>&lt;tribaal&gt;</code> my brother got married in Odd_Bloke 's backyard :)</p> -<p>17:25 <code>&lt;tribaal&gt;</code> I wish we could do cross-company colocated sprints :P</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> heh, I think we can call those #cloud-init-summits :)</p> -<p>17:26 <code>&lt;tribaal&gt;</code> ohhh yeah :)</p> -<p>17:26 <code>&lt;tribaal&gt;</code> when's the next one?</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> we'll have to get invites together for the next one (Fall 2020)</p> -<p>17:27 <code>&lt;tribaal&gt;</code> noted :)</p> -<p>17:29 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;tribaal&gt;</code> ohhh big news indeed!</p> -<p>17:30 <code>&lt;Odd_Bloke&gt;</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>&lt;Odd_Bloke&gt;</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>&lt;blackboxsw&gt;</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>&lt;tribaal&gt;</code> very nice!</p> -<p>17:33 <code>&lt;blackboxsw&gt;</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>&lt;tribaal&gt;</code> ah that would make sese yeah</p> -<p>17:34 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> thanks Odd_Bloke and rharper for all the work there so far</p> -<p>17:38 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> thanks for participating chillysurfer &amp; tribaal</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2019-10-08T16:18:00+00:002019-10-08T16:18:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2019-10-08:/status-2019-10-08.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 08 Oct at 16:18 &mdash; 17:54 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-10-08-16.18.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-10-08-16.18.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:23.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-09-09.html#status-2019-09-09">https://cloud-init.github.io/status-2019-09-09.html#status-2019-09-09 …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 08 Oct at 16:18 &mdash; 17:54 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-10-08-16.18.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-10-08-16.18.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:23.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-09-09.html#status-2019-09-09">https://cloud-init.github.io/status-2019-09-09.html#status-2019-09-09</a> </li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:25.</p> -<ul> -<li><strong>ACTION</strong>: blackboxsw verify cpc image builds are unpaused/unblocked for Azure</li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:36.</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="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> </li> -<li><strong>ACTION</strong>: 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></li> -<li><strong>LINK</strong>: <a href="https://trello.com/c/pqA1adVM/1195-investigate-adding-github-travis-ci-to-cloud-init">https://trello.com/c/pqA1adVM/1195-investigate-adding-github-travis-ci-to-cloud-init</a> </li> -</ul> -<h3>Community Charter</h3> -<p>The discussion about "Community Charter" started at 16:44.</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 and releases</h3> -<p>The discussion about "Upcoming meetings and releases" started at 16:47.</p> -<ul> -<li><strong>ACTION</strong>: upstream cloud-init email about 19.3 release date</li> -</ul> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 16:52.</p> -<ul> -<li><strong>ACTION</strong>: revisit python deprecation and report to mailinglist</li> -</ul> -<h2>Vote results</h2> -<h2>Action items, by person</h2> -<ul> -<li>ahosmanmsft</li> -<li>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></li> -<li>blackboxsw</li> -<li>blackboxsw verify cpc image builds are unpaused/unblocked for Azure - <strong>UNASSIGNED</strong></li> -<li>upstream cloud-init email about 19.3 release date</li> -<li>revisit python deprecation and report to mailinglist</li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (110)</li> -<li>ubot5 (8)</li> -<li>AnhVoMSFT (8)</li> -<li>meetingology (8)</li> -<li>Odd_Bloke (7)</li> -<li>rharper (3)</li> -<li>ahosmanmsft (1)</li> -</ul> -<h2>Full Log</h2> -<p>16:18 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:18 <code>&lt;meetingology&gt;</code> Meeting started Tue Oct 8 16:18:28 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:18 <code>&lt;meetingology&gt;</code> </p> -<p>16:18 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> Welcome back folks o/ And thanks AnhVoMSFT for the ping to get us started</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> #chair rharper Odd_Bloke</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #chair rharper Odd_Bloke</p> -<p>16:19 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw rharper</p> -<p>16:19 <code>&lt;blackboxsw&gt;</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:19 <code>&lt;Odd_Bloke&gt;</code> o/</p> -<p>16:19 <code>&lt;Odd_Bloke&gt;</code> Thanks for the reminder, Anh.</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> Feel free to interject at any time. Our typical format is the following: Previous Actions, Recent Changes, In-progress Development, Office Hours (~30 mins).</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> For this, and subsequent, status meetings I proposed we add a new topic: Ongoing Community Charter which would give context on the new trello lane we added at the cloud-init summit.</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: rharper AnhVoMSFT does that sound good? We can then better advertise and remind about long-term community involvement projects that are available for anyone</p> -<p>16:22 <code>&lt;AnhVoMSFT&gt;</code> I would propose that the last agenda item of any status meeting would be to update the banner to reflect the next status meeting - and perhaps the next ETA for next release / SRU</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> +1 AnhVoMSFT that sounds good too.</p> -<p>16:22 <code>&lt;AnhVoMSFT&gt;</code> yep, sounds good on the Community Charter</p> -<p>16:22 <code>&lt;rharper&gt;</code> AnhVoMSFT: +1</p> -<p>16:22 <code>&lt;rharper&gt;</code> I think one topic each</p> -<p>16:22 <code>&lt;rharper&gt;</code> and end with the next status meeting</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> ok starting to turn the meeting crank</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> last meeting was 09/09/2019</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2019-09-09.html#status-2019-09-09">https://cloud-init.github.io/status-2019-09-09.html#status-2019-09-09</a></p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> meeting minutes at the link above ^</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> only action was #action blackboxsw send email to the list notifying of status meeting day change.</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> which was done <a href="https://lists.launchpad.net/cloud-init/msg00224.html">https://lists.launchpad.net/cloud-init/msg00224.html</a></p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> no further outstanding actions from last meeting</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> The following branches have landed in tip since last meeting: via git log --since 2019-09-09</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> - Add RbxCloud datasource [Adam Dobrawy]</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> - get_interfaces: don't exclude bridge and bond members (LP: #1846535)</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> - Add support for Arch Linux in render-cloudcfg [Conrad Hoffmann]</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> - util: json.dumps on python 2.7 will handle UnicodeDecodeError on binary</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> (LP: #1801364)</p> -<p>16:27 <code>&lt;ubot5&gt;</code> Launchpad bug 1846535 in cloud-init "cloud-init 19.2.36 fails with python exception "Not all expected physical devices present ..." during bionic image deployment from MAAS" [Critical,Fix committed] <a href="https://launchpad.net/bugs/1846535">https://launchpad.net/bugs/1846535</a></p> -<p>16:27 <code>&lt;ubot5&gt;</code> Launchpad bug 1801364 in cloud-init "persisting OpenStack metadata fails" [Undecided,Fix committed] <a href="https://launchpad.net/bugs/1801364">https://launchpad.net/bugs/1801364</a></p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> oopsie daisy</p> -<p>16:27 <code>&lt;AnhVoMSFT&gt;</code> :)</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> got kicked on flood. chunking that now</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> - Add RbxCloud datasource [Adam Dobrawy]</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> - get_interfaces: don't exclude bridge and bond members (LP: #1846535)</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> - Add support for Arch Linux in render-cloudcfg [Conrad Hoffmann]</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> - util: json.dumps on python 2.7 will handle UnicodeDecodeError on binary</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> (LP: #1801364)</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> - debian/ubuntu: add missing word to netplan/ENI header (LP: #1845669)</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> - ovf: do not generate random instance-id for IMC customization path</p> -<p>16:27 <code>&lt;ubot5&gt;</code> Launchpad bug 1845669 in cloud-init "The meaning of "Changes to it will not persist across an instance." in 50-cloud-init.yaml is unclear" [Undecided,Fix committed] <a href="https://launchpad.net/bugs/1845669">https://launchpad.net/bugs/1845669</a></p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> - sysconfig: only write resolv.conf if network_state has DNS values</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> (LP: #1843634)</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> - sysconfig: use distro variant to check if available (LP: #1843584)</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> - systemd/cloud-init.service.tmpl: start after wicked.service</p> -<p>16:27 <code>&lt;ubot5&gt;</code> Launchpad bug 1843634 in cloud-init (Suse) "cloud-init misconfigure the network on SLES" [Undecided,Incomplete] <a href="https://launchpad.net/bugs/1843634">https://launchpad.net/bugs/1843634</a></p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> [Robert Schweikert]</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> - docs: fix zstack documentation lints</p> -<p>16:28 <code>&lt;ubot5&gt;</code> Launchpad bug 1843584 in cloud-init "cloudinit/net/sysconfig.py lacks support for openSUSE 15.x and Tumbleweed" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1843584">https://launchpad.net/bugs/1843584</a></p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - analyze/show: remove trailing space in output</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - Add missing space in warning: "not avalid seed" [Brian Candler]</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - pylintrc: add 'enter_context' to generated-members list</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - Add datasource for ZStack platform. [Shixin Ruan] (LP: #1841181)</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - docs: organize TOC and update summary of project [Joshua Powers]</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - tools: make clean now cleans the dev directory, not the system</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - docs: create cli specific page [Joshua Powers]</p> -<p>16:28 <code>&lt;ubot5&gt;</code> Launchpad bug 1841181 in cloud-init "add datasource for ZStack" [Low,Fix committed] <a href="https://launchpad.net/bugs/1841181">https://launchpad.net/bugs/1841181</a></p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - docs: added output examples to analyze.rst [Joshua Powers]</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - docs: doc8 fixes for instancedata page [Joshua Powers]</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - docs: clean up formatting, organize boot page [Joshua Powers]</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - net: add is_master check for filtering device list (LP: #1844191)</p> -<p>16:28 <code>&lt;ubot5&gt;</code> Launchpad bug 1844191 in cloud-init "azure advanced networking sometimes triggers duplicate mac detection" [Critical,Fix committed] <a href="https://launchpad.net/bugs/1844191">https://launchpad.net/bugs/1844191</a></p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - docs: more complete list of availability [Joshua Powers]</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - docs: start FAQ page [Joshua Powers]</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - docs: cleanup output &amp; order of datasource page [Joshua Powers]</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - Brightbox: restrict detection to require full domain match .brightbox.com</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - VMWware: add option into VMTools config to enable/disable custom script.</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> [Xiaofeng Wang]</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - net,Oracle: Add support for netfailover detection</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - atomic_helper: add DEBUG logging to write_file (LP: #1843276)</p> -<p>16:28 <code>&lt;ubot5&gt;</code> Launchpad bug 1843276 in cloud-init "cloudinit.atomic_helper.write_file should have the same logging as util.write_file" [Low,Fix committed] <a href="https://launchpad.net/bugs/1843276">https://launchpad.net/bugs/1843276</a></p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> Thanks Brian, Shixin Ruan, Conrad Hoffmann, Adam Dobrawy and robjo for the contributions over the last month!</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> beyond tip commits to cloud-init the upstream team went through two SRUs of cloud-init</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> it's also excellent to see new datasources like the RbxCloud datasource added</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> cloud-init just passed validation for Ubuntu Xenial, Bionic and Disco on the 2nd SRU 19.2-36-g059d049c-0ubuntu2</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> cloud-images today should have that updated revision in them I blieve</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> there are fixes for both Azure accelerated networking support and handling issues seen on MAAS network bridge configuration</p> -<p>16:32 <code>&lt;AnhVoMSFT&gt;</code> on that note the last Azure image we had published was early September, which still didn't have the first SRU</p> -<p>16:32 <code>&lt;AnhVoMSFT&gt;</code> is there something going on with the image publishing pipeline again?</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: the publishing pipeline paused while we sorted the 2nd SRU pass for maas network bridge issues introduced by 19.2-36-g059d049c-0ubuntu1</p> -<p>16:33 <code>&lt;AnhVoMSFT&gt;</code> i see - that makes sense</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> 19.2-36-g059d049c-0ubuntu2 was verified as fixing all support there for both Azure and MAAS datasources and the expectation is that image builds are continuing today but I'll verify that the box is ✔ there on images rebuilding</p> -<p>16:34 <code>&lt;Odd_Bloke&gt;</code> There may also be Azure-specific publication pipeline issues, which we wouldn't necessarily know about off-hand.</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> #action blackboxsw verify cpc image builds are unpaused/unblocked for Azure</p> -<p>16:34 * meetingology blackboxsw verify cpc image builds are unpaused/unblocked for Azure</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> thx Odd_Bloke right</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> looks like Odd_Bloke is already on that verification internally</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> ok so SRU is through verification on our side. cloudimages should be getting latest version of cloud-init for Xenial, Bionic and Disco imminently</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> I think that is <em>it</em> for Recent Changes</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> the SRU verification work took a bit of steam out of our current work in progress as it involved a lot of manual and upgrade scenario tests.</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> But, as always we try to track ongoing work in trello</p> -<p>16:37 <code>&lt;blackboxsw&gt;</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:38 <code>&lt;blackboxsw&gt;</code> there are a number of branches in progress that are of interest:</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> Azure CI for one would be a great add for cloud-init's CI infrastructure</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> <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>16:39 <code>&lt;blackboxsw&gt;</code> we need to get eyes on that this week if we can</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> #action 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></p> -<p>16:39 * meetingology 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></p> -<p>16:39 <code>&lt;ahosmanmsft&gt;</code> That would be great</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> there are also a number of freebsd branches that need to close out.</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> and I know Odd_Bloke has started peeking at some initial github integration for CI.</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: any details you want to add about github CI at the moment?</p> -<p>16:41 <code>&lt;Odd_Bloke&gt;</code> I've started iterating on a Travis configuration to run what we currently run in our CI pipeline.</p> -<p>16:41 <code>&lt;Odd_Bloke&gt;</code> Unsurprisingly, setting up linting/unit testing was easy.</p> -<p>16:42 <code>&lt;Odd_Bloke&gt;</code> The other thing we do is run some integration testing from a built deb file. I got as far as being able to successfully sbuild the package in Travis, and ran into some initial stumbling blocks with running lxd.</p> -<p>16:42 <code>&lt;Odd_Bloke&gt;</code> That's as far as I've got, I expect to pick that work back up this week.</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> thanks Odd_Bloke , I've added the following card to trello for those interested.</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> #link <a href="https://trello.com/c/pqA1adVM/1195-investigate-adding-github-travis-ci-to-cloud-init">https://trello.com/c/pqA1adVM/1195-investigate-adding-github-travis-ci-to-cloud-init</a></p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> I think that about wraps in progress work. We'll tackle reviews a bit at the end of the meeting</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> ok next topic</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> #topic Community Charter</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> at the cloud-init summit we decided to highlight community work in trello so that any community member with some dev cycles and interest can join in and contribute to ongoing tasks</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> that lane is now in trello representing low-hanging-fruit content that upstream cloud-init is interested in completing, and that anyone can commit to.</p> -<p>16:45 <code>&lt;blackboxsw&gt;</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:46 <code>&lt;blackboxsw&gt;</code> the lane is labelled "Community low-hanging-fruit" and currently contains a number of doc update work items as well as json schema validation extensions for each cloud-init config module</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> we invite everyone to participate and feel free to grab those items as they have interest</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> we'll revisit this topic in each meeting so folks have context</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> #topic Upcoming meetings and releases</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> cloud-init upstream has just passed validation of cloud-init 19.2.36-*-ubuntu2 which should approved for upload into Xenial, Disco and Bionic (and queued for Eoan)</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> the cloud build team will be generating images for various clouds imminently and we will confirm that build pipelines are active so platforms get new bits asap</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> 19.3 upstream should by coming shortly, we will update the topic with the expected upstream release date and send an email to the mailing list with the estimated upstream cut</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> #action upstream cloud-init email about 19.3 release date</p> -<p>16:51 * meetingology upstream cloud-init email about 19.3 release date</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> next meeting is Oct 22</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> same bat time same bat channel</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> we spend this time for reviews, bug triage and cloud-init discussions.</p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> upstream devs should have eyes on this channel. Thanks everyone for tuning in</p> -<p>16:54 <code>&lt;AnhVoMSFT&gt;</code> have you had a chance to discuss about the python deprecation issue, or did the SRU verification take most of the time since the summit</p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: last week was vacation plus the remainder of us on sru verification .</p> -<p>17:00 <code>&lt;blackboxsw&gt;</code> But now we have cleared that hurdle we should we able to discuss it this week.</p> -<p>17:00 <code>&lt;AnhVoMSFT&gt;</code> yep, sounds good.</p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> #action revisit python deprecation and report to mailinglist</p> -<p>17:01 * meetingology revisit python deprecation and report to mailinglist</p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> Good meeting for actions</p> -<p>17:54 <code>&lt;blackboxsw&gt;</code> Thanks for the participation folks I'll publish minutes to github</p> -<p>17:54 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2019-09-09T16:26:00+00:002019-09-09T16:26:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2019-09-09:/status-2019-09-09.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 09 Sep at 16:26 &mdash; 17:33 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-09-09-16.26.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-09-09-16.26.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-08-19.html#status-2019-08-19">https://cloud-init.github.io/status-2019-08-19.html#status-2019-08-19</a> </p> -<h3>Previous actions</h3> -<p>The discussion about "Previous actions" started at 16:30 …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 09 Sep at 16:26 &mdash; 17:33 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-09-09-16.26.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-09-09-16.26.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-08-19.html#status-2019-08-19">https://cloud-init.github.io/status-2019-08-19.html#status-2019-08-19</a> </p> -<h3>Previous actions</h3> -<p>The discussion about "Previous actions" started at 16:30.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:31.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://lists.launchpad.net/cloud-init/msg00170.html">https://lists.launchpad.net/cloud-init/msg00170.html</a> </li> -<li><strong>LINK</strong>: <a href="https://lists.launchpad.net/cloud-init/">https://lists.launchpad.net/cloud-init/</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:38.</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="https://discourse.ubuntu.com/c/server">https://discourse.ubuntu.com/c/server</a> </li> -</ul> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 16:48.</p> -<ul> -<li><strong>ACTION</strong>: blackboxsw send email to the list notifying of status meeting day change.</li> -<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> -<h2>Vote results</h2> -<h2>Action items, by person</h2> -<ul> -<li>blackboxsw</li> -<li>blackboxsw send email to the list notifying of status meeting day change.</li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (64)</li> -<li>meetingology (5)</li> -<li>Odd_Bloke (4)</li> -<li>ubot5 (2)</li> -<li>rharper (1)</li> -</ul> -<h2>Full Log</h2> -<p>16:26 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:26 <code>&lt;meetingology&gt;</code> Meeting started Mon Sep 9 16:26:10 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:26 <code>&lt;meetingology&gt;</code> </p> -<p>16:26 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> Hey folks, welcome to the ~biweekly cloud-init status meeting.</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> #chair rharper Odd_Bloke</p> -<p>16:28 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw rharper</p> -<p>16:28 <code>&lt;Odd_Bloke&gt;</code> o/</p> -<p>16:28 <code>&lt;blackboxsw&gt;</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:30 <code>&lt;blackboxsw&gt;</code> Feel free to interject at any time. Our typical format is the following: Previous Actions, Recent Changes, In-progress Development, Office Hours (~30 mins)</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> Last meeting's minutes live here:</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2019-08-19.html#status-2019-08-19">https://cloud-init.github.io/status-2019-08-19.html#status-2019-08-19</a></p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> #topic Previous actions</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> no actions from last meeting so we'll plow right through to Recent Changes</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> The following branches have landed in tip since last meeting: via git log --since 2019-08-19</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> - doc: document doc, create makefile and tox target [Joshua Powers]</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> - .gitignore: ignore files produced by package builds [Daniel Watkins]</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> - docs: fix whitespace, spelling, and line length [Joshua Powers]</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> - docs: remove unnecessary file in doc directory [Joshua Powers]</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> - Oracle: Render secondary vnic IP and MTU values only [Ryan Harper]</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> - exoscale: fix sysconfig cloud_config_modules overrides</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> [Chad Smith] (LP: #1841454)</p> -<p>16:32 <code>&lt;ubot5&gt;</code> Launchpad bug 1841454 in cloud-init "Exoscale datasource overwrites <em>all</em> cloud_config_modules" [Undecided,Fix committed] <a href="https://launchpad.net/bugs/1841454">https://launchpad.net/bugs/1841454</a></p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> - net/cmdline: refactor to allow multiple initramfs network config sources</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> [Daniel Watkins]</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> - ubuntu-drivers: call db_x_loadtemplatefile to accept NVIDIA EULA</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> [Chad Smith] (LP: #1840080)</p> -<p>16:32 <code>&lt;ubot5&gt;</code> Launchpad bug 1840080 in cloud-init (Ubuntu) "cloud-init cc_ubuntu_drivers does not set up /etc/default/linux-modules-nvidia" [High,Fix released] <a href="https://launchpad.net/bugs/1840080">https://launchpad.net/bugs/1840080</a></p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> - Add missing #cloud-config comment on first example in documentation.</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> [Florian Müller]</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> - ubuntu-drivers: emit latelink=true debconf to accept nvidia eula</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> [Chad Smith] (LP: #1840080)</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> - DataSourceOracle: prefer DS network config over initramfs</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> [Daniel Watkins]</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> - format.rst: add text/jinja2 to list of content types (+ cleanups)</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> [Daniel Watkins]</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> - Add GitHub pull request template to point people at hacking doc</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> [Daniel Watkins]</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> Additionally: we have also cut a stable-18.4 branch from the 18.4 tag as our last supported python2.6 branch. There will be an email sent out to the mailing list about the intent of this branch. It requires a couple of minor fixes to make sure py2.6 support is functional, but this will be reference branch for any distribution that does not have access to py.27 or later. No additional feature development is</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> planned on stable-18.4</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> a reminder again that python2.6 support was 'dropped' in cloud-init upstream as of the 18.4 release, so expectations for py2.6 support stopped in 18.4 and there is a deprecation plan for py 2.7 as well</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> #link <a href="https://lists.launchpad.net/cloud-init/msg00170.html">https://lists.launchpad.net/cloud-init/msg00170.html</a></p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> Again, see the mailinglist for details and updates</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> #link <a href="https://lists.launchpad.net/cloud-init/">https://lists.launchpad.net/cloud-init/</a></p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> Last week or so the team has been working on SRU validation for cloud-init 19.2.24 into Xenial, Bionic and Disco.</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> We have passed all SRU validation tests and our expected pubish date for 19.2.24 is tomorrow for those Ubuntu series</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> good work on validation folks</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> and thanks for extra cloud-init community verification from exoscale, azure and VMware for validation efforts</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> There is additional Oracle, FreeBSD and Azure work in flight at the moment as well as some boot speed improvements and analysis from rharper</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> The following link represents any carded work upstream is tracking. The Doing lane is content or features we expect to land shortly</p> -<p>16:43 <code>&lt;blackboxsw&gt;</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:47 <code>&lt;blackboxsw&gt;</code> Now is probably a good time to also mention that our entire ubuntu server team also reflects our weekly accomplishements over in the ubuntu-server discourse. If there are deeper discussions or questions on various topics or features please join us there as well</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> #link <a href="https://discourse.ubuntu.com/c/server">https://discourse.ubuntu.com/c/server</a></p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> I think that about wraps it for in-progress development</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> upstream cloud-init devs will have eyes on this channel for any discussions, questions, bugs or feature work the greater community would like to discuss.</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> During this time, we'll also groom our activereview queue to make sure we try to get review comments out to devs who have active branches.</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> Again, thanks for tuning in</p> -<p>16:57 <code>&lt;blackboxsw&gt;</code> Ok just addressed review comments on <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/372432">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/372432</a> . I'm reviewing <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:59 * blackboxsw also sets the next meeting topic so we don't forget.</p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: rharper powersj, I <em>think</em> we decided to shift from Mondays to Tuesdays for status meetings to avoid collisions with holidays, vacation work travel etc. Are we doing that for next status meeting, or maybe waiting to discuss that more broadly?</p> -<p>17:02 <code>&lt;Odd_Bloke&gt;</code> Tuesday in two weeks is likely to be a travel day for anyone heading to the cloud-init summit.</p> -<p>17:02 <code>&lt;Odd_Bloke&gt;</code> But Monday is likely to be a swap day for Canonical folks because we're all travelling next week too.</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> hrm right, maybe we wait then and discuss at the summit</p> -<p>17:03 <code>&lt;Odd_Bloke&gt;</code> So I would perhaps suggest skipping the next meeting, and then we can resume on Tuesdays two weeks after the summit?</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> discuss scheduling changes that is</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> sure, let's push/postpone until summit +2 weeks</p> -<p>17:05 <code>&lt;blackboxsw&gt;</code> #action blackboxsw send email to the list notifying of status meeting day change.</p> -<p>17:05 * meetingology blackboxsw send email to the list notifying of status meeting day change.</p> -<p>17:10 <code>&lt;rharper&gt;</code> +1 Odd_Bloke</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> Also note that the version of cloud-init that has undergone SRU verification is also published to our copr el-testing repo. We only update that repo during upstream cloud-init releases XX.YY and any Ubuntu SRUs so it is much more stable than our daily copr repo.</p> -<p>17:11 <code>&lt;blackboxsw&gt;</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>17:33 <code>&lt;blackboxsw&gt;</code> I think that about wraps our cloud-init status meeting for today. I'm wrapping up my review here and will post it to the set_passwords branch.</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2019-08-19T16:18:00+00:002019-08-19T16:18:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2019-08-19:/status-2019-08-19.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 19 Aug at 16:18 &mdash; 17:25 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-08-19-16.18.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-08-19-16.18.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-08-05.html#status-2019-08-05">https://cloud-init.github.io/status-2019-08-05.html#status-2019-08-05</a> </p> -<h3>cloud-init Reviews: <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl …</a></h3><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 19 Aug at 16:18 &mdash; 17:25 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-08-19-16.18.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-08-19-16.18.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-08-05.html#status-2019-08-05">https://cloud-init.github.io/status-2019-08-05.html#status-2019-08-05</a> </p> -<h3>cloud-init Reviews: <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting Sept 2 16:15 UTC | cloud-init v 19.2 (07/17) | <a href="https://bugs.launchpad.net/cloud-init/+filebug">https://bugs.launchpad.net/cloud-init/+filebug</a></h3> -<p>The discussion about "cloud-init Reviews: <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting Sept 2 16:15 UTC | cloud-init v 19.2 (07/17) | <a href="https://bugs.launchpad.net/cloud-init/+filebug">https://bugs.launchpad.net/cloud-init/+filebug</a>" started at 16:20.</p> -<h3>Previous actions</h3> -<p>The discussion about "Previous actions" started at 16:21.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:22.</p> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:25.</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="https://code.launchpad.net/cloud-init/+activereviews">https://code.launchpad.net/cloud-init/+activereviews</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 (71)</li> -<li>rharper (9)</li> -<li>meetingology (5)</li> -<li>tribaal (4)</li> -<li>robjo (2)</li> -<li>ubot5 (1)</li> -<li>Odd_Bloke (0)</li> -</ul> -<h2>Full Log</h2> -<p>16:18 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:18 <code>&lt;meetingology&gt;</code> Meeting started Mon Aug 19 16:18:48 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:18 <code>&lt;meetingology&gt;</code> </p> -<p>16:18 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> Hi guys and girls, welcome to cloud-init biweekly status meeting</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #chair rharper</p> -<p>16:19 <code>&lt;meetingology&gt;</code> Current chairs: blackboxsw rharper</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #chair Odd_Bloke</p> -<p>16:19 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw rharper</p> -<p>16:19 <code>&lt;blackboxsw&gt;</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:19 <code>&lt;blackboxsw&gt;</code> All discussions and interjections are welcome</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> our format is the following topics: Previous Actions, Recent Changes, In-progress Development, Office Hours</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> last meeting's minutes are herer</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2019-08-05.html#status-2019-08-05">https://cloud-init.github.io/status-2019-08-05.html#status-2019-08-05</a></p> -<p>16:20 <code>&lt;rharper&gt;</code> o/</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> we host the meeting every two weeks at the date and time indicated in the IRC channel topic ^</p> -<p>16:20 * blackboxsw changes that topic now, since we(I) forgot last time</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #topic cloud-init Reviews: <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting Sept 2 16:15 UTC | cloud-init v 19.2 (07/17) | <a href="https://bugs.launchpad.net/cloud-init/+filebug">https://bugs.launchpad.net/cloud-init/+filebug</a></p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> next meeting in two weeks</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> #topic Previous actions</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> I see no previous actions raised during last meeting. Woo hoo!</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> the following are commits that</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> have landed in tip of master for cloud-init since the last meeting: git log --since 2019-08-04</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - cloudinit/distros/parsers/sys_conf: add docstring to SysConf</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> [Daniel Watkins]</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - pyflakes: remove unused variable [Joshua Powers]</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - Azure: Record boot timestamps, system information, and diagnostic events</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> [Anh Vo]</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - DataSourceOracle: configure secondary NICs on Virtual Machines</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> [Daniel Watkins]</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - distros: fix confusing variable names [Daniel Watkins]</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - azure/net: generate_fallback_nic emits network v2 config instead of v1</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> [Chad Smith]</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - Add support for publishing host keys to GCE guest attributes</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> [Rick Wright]</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - New data source for the Exoscale.com cloud platform [Chris Glass]</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - doc: remove intersphinx extension [Daniel Watkins]</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - cc_set_passwords: rewrite documentation [Daniel Watkins] (LP: #1838794)</p> -<p>16:22 <code>&lt;ubot5&gt;</code> Launchpad bug 1838794 in cloud-init "Set Passwords documentation describes incorrect behaviour for <code>password</code> config key" [Low,Fix committed] <a href="https://launchpad.net/bugs/1838794">https://launchpad.net/bugs/1838794</a></p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> We have also published commits though " - Azure: Record boot timestamps, system information, and diagnostic events" to Ubuntu Eoan (19.10) (cloud-init v.19.2-13) if folks want a glimpse of those features</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> Many thanks to Azure and GCE folks for their commits and a hi five to tribaal for adding Exoscale</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> As always, we try to keep most of our work up to date in trello</p> -<p>16:25 <code>&lt;blackboxsw&gt;</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:26 <code>&lt;blackboxsw&gt;</code> cards in the "Reviewing" column should represent the work we expect to have up for review in the short term.</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> rharper is mid-stream on some investigations that will likely lead to significant speed improvements for cloud-init</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: is working on some significant improvements for Oracle's datasource rendering network config</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> and I'm working on getting OpenStack and Ec2 datasources to talk network config v2.</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> beyond that work we have a pretty healther active review queue</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/cloud-init/+activereviews">https://code.launchpad.net/cloud-init/+activereviews</a></p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> of note, some freebsd work is in flight, gce dns improvements, udev triggers and OVF handling user-defined scripts.</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> We</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> will spend the latter part of this meeting looking over the review queue to see that open branches are in the proper state</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> Also, our plan for this week is to cut a Cloud-init SRU (Stable release update) for upload into xenial, bionic and disco.</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> expectation is that those Ubuntu series will see an update for cloud-init after our ~7 days of testing and verification</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> rharper: Odd_Bloke anything else in flight that we should note here?</p> -<p>16:34 <code>&lt;rharper&gt;</code> that looks like everything</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> without further ado, we can transition to office hours</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> We're here for any questions, bugs, discussions people would like to have around cloud-init. This block of time is available for any discussions or requests people may have.</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> We will also spend this time grooming the active review queue to make sure developers get any needed feedback on their active branches.</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> If there are any branches that need more eyes, please bring them up here or make sure they are in the 'Needs review' state in Launchpad</p> -<p>16:38 <code>&lt;tribaal&gt;</code> blackboxsw: thanks!</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> tribaal: good work. I think Odd_Bloke landed the followup work to enable exoscale datasource config to cloud-init.templates to 'enable' it. And looks like that has landed</p> -<p>16:40 <code>&lt;tribaal&gt;</code> blackboxsw: I'm happy to help verify SRU bugs when the process is kicked - just let me know</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> so it's 'on' in Eoan, once SRU is kicked off, it'll be in there</p> -<p>16:41 <code>&lt;tribaal&gt;</code> yep, I need to push an Eoan template to our preprod environment tomorrow to kick the tires, but I don't expect anything funny</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> tribaal: will do. I think the only thing we are waiting on before SRU is landing this ubuntu-drivers branch <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/371369">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/371369</a></p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> any feedback on behavior your in Eoan from you tribaal would be helpful.</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> let's try that in English this time: any feedback on the behavior in your Eoan environment would be helpful tribaal.</p> -<p>16:43 <code>&lt;tribaal&gt;</code> blackboxsw: haha that's what I inferred :)</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> :) /me hits the review queue</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> rharper: if you get a chance: you've landed <a href="https://git.launchpad.net/cloud-init/commit/">https://git.launchpad.net/cloud-init/commit/</a>?id=b3a87fc0. Do we also still need the following branch? <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/363571">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/363571</a></p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> If so, I'll spend this time trying to write up unit tests for this if possible</p> -<p>16:48 <code>&lt;rharper&gt;</code> blackboxsw: I don't think so; my branch should include all the needs of that branch</p> -<p>16:49 <code>&lt;rharper&gt;</code> and the branch tests the wait_for_physdev as well as updates the opensuse net render paths to account for the udev rule number change</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> that's kindof what I was thinking/hoping. I'll mark it rejected in favor of your commit, and we'll see what robjo thinks on that. We can reopen and try to address the unit test aspect of his branch if still needed.</p> -<p>16:50 <code>&lt;rharper&gt;</code> I think we can mark that branch closed</p> -<p>16:50 <code>&lt;rharper&gt;</code> robjo: had already looked at the branch before landing</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> ok done</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> thanks Florian for your first commit! <a href="https://code.launchpad.net/~florian-mueller-v/cloud-init/+git/cloud-init/+merge/371298">https://code.launchpad.net/~florian-mueller-v/cloud-init/+git/cloud-init/+merge/371298</a> ... doc update approved</p> -<p>16:58 <code>&lt;robjo&gt;</code> I don't recall having looked at <a href="https://git.launchpad.net/cloud-init/commit/">https://git.launchpad.net/cloud-init/commit/</a>?id=b3a87fc0 and there was no entry in the bug to remind me that I did. Anyway, I've done so now and yes, this obsoletes <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/363571">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/363571</a></p> -<p>17:00 <code>&lt;blackboxsw&gt;</code> thank you robjo for that</p> -<p>17:04 <code>&lt;rharper&gt;</code> robjo: <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/366667">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/366667</a> ; yes, I should have linked to the bug in my MP</p> -<p>17:04 <code>&lt;rharper&gt;</code> you did take a look a while back though</p> -<p>17:06 <code>&lt;robjo&gt;</code> rharper: I believe you, just cannot remember....</p> -<p>17:06 <code>&lt;rharper&gt;</code> heh, it was a while back</p> -<p>17:24 <code>&lt;blackboxsw&gt;</code> I think we should probably wrap up the meeting for this week. I've got one more review to clear.</p> -<p>17:24 <code>&lt;blackboxsw&gt;</code> Thanks again all for joining. minutes will be posted to github</p> -<p>17:25 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>17:25 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2019-08-05T16:16:00+00:002019-08-05T16:16:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2019-08-05:/status-2019-08-05.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 05 Aug at 16:16 &mdash; 17:06 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-08-05-16.16.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-08-05-16.16.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>#cloud-init Reviews: <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting Aug 19 16:15 …</h3><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 05 Aug at 16:16 &mdash; 17:06 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-08-05-16.16.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-08-05-16.16.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>#cloud-init Reviews: <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting Aug 19 16:15 UTC | cloud-init v 19.2 (07/17) | <a href="https://bugs.launchpad.net/cloud-init/+filebu">https://bugs.launchpad.net/cloud-init/+filebu</a></h3> -<p>The discussion about "#cloud-init Reviews: <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting Aug 19 16:15 UTC | cloud-init v 19.2 (07/17) | <a href="https://bugs.launchpad.net/cloud-init/+filebu">https://bugs.launchpad.net/cloud-init/+filebu</a>" started at 16:19.</p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:20.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-07-22.html#status-2019-07-22">https://cloud-init.github.io/status-2019-07-22.html#status-2019-07-22</a> </li> -</ul> -<h3>In-Progress Development</h3> -<p>The discussion about "In-Progress Development" started at 16:23.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516">https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/370927">https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/370927</a> (doc updates)</li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785">https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785</a> (Azure telemetry)</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> -<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>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:31.</p> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 16:33.</p> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (56)</li> -<li>tribaal (7)</li> -<li>cyphermox (4)</li> -<li>meetingology (4)</li> -<li>ubot5 (1)</li> -<li>rharper (0)</li> -</ul> -<h2>Full Log</h2> -<p>16:16 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:16 <code>&lt;meetingology&gt;</code> Meeting started Mon Aug 5 16:16:04 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:16 <code>&lt;meetingology&gt;</code> </p> -<p>16:16 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:16 <code>&lt;tribaal&gt;</code> o/</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> Heya Chris!</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> Welcome to another cloud-init community status meeting folks.</p> -<p>16:17 * blackboxsw finally back from a much needed vacation and have dug myself out of backlog</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> #chair rharper</p> -<p>16:17 <code>&lt;meetingology&gt;</code> Current chairs: blackboxsw rharper</p> -<p>16:18 <code>&lt;blackboxsw&gt;</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:18 <code>&lt;blackboxsw&gt;</code> All interjections updates and questions welcome</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> we may be a bit light this meeting as well as some folks have holidays and travel that coincide with this meeting</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> our format is the following topics: Previous Actions, Recent Changes, In-progress Development, Office Hours</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> we host the meeting every two weeks at the date and time indicated in the IRC channel topic ^</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> I'll update that topic now as I think we forgot to last meeting</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #topic #cloud-init Reviews: <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting Aug 19 16:15 UTC | cloud-init v 19.2 (07/17) | <a href="https://bugs.launchpad.net/cloud-init/+filebu">https://bugs.launchpad.net/cloud-init/+filebu</a></p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> next meeting will be two weeks from today, same time</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2019-07-22.html#status-2019-07-22">https://cloud-init.github.io/status-2019-07-22.html#status-2019-07-22</a></p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> groking the meeting last episode, looks like rharper needed to update status on <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a></p> -<p>16:20 <code>&lt;ubot5&gt;</code> Ubuntu bug 1832381 in cloud-init (Ubuntu) "vm fails to boot due to conflicting network configuration when user switches from netplan to eni" [Undecided,Incomplete]</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> I think we were awaiting feedback there from AnvoMSFT for a specific reproduce</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> I think we were awaiting feedback there from AnvoMSFT for a specific reproducer</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> so that'll carryover til next meeting if if it a priority</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> the other action from last session was for rharper to ping me on status publishing to github.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> I've pushed meeting minutes from last two cloud-init status meetings up to cloud-init.github.io so we are closed there</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> no other actions seen</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #topic In-Progress Development</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> Upstream 19.2 was cut on 7/17 and there are plans to SRU cloud-init within the next week or two into Xenial, bionic, disco and Eaon. I know that we are waiting on closure of a few branches in tip before we SRU cloud-init tip to Xenial ++</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> tribaal: your exoscale branch I believe is one of the ones we want landed before we start our SRU process</p> -<p>16:24 <code>&lt;tribaal&gt;</code> I was hoping to address Odd_Bloke 's comments today, but that didn't happen. Tomorrow, or "this week" at the very least is my new target.</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516">https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516</a></p> -<p>16:25 <code>&lt;tribaal&gt;</code> Most of the non-blocking comments should be easy - I want to double check the on-reboot behavior on an actual instance though</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> tribaal: excellent, Odd_Bloke was able to get the review in Friday as he knew he'd be on holiday today and wanted to get you feedback</p> -<p>16:25 <code>&lt;tribaal&gt;</code> ack</p> -<p>16:26 <code>&lt;tribaal&gt;</code> (the blocking comment about the copyright header should be trivial as well thankfully :) )</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> yeah agreed</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> we also have the following branches we'd like to get "in" and merged to tip before SRU</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/370927">https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/370927</a> (doc updates)</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785">https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785</a> (Azure telemetry)</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> and some of goneri's FreeBSD support look like they are straight forward for review/landing</p> -<p>16:28 <code>&lt;blackboxsw&gt;</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:28 <code>&lt;blackboxsw&gt;</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:29 <code>&lt;blackboxsw&gt;</code> If anyone else out there today is interested in getting reviews/merges before we SRU to Xenial, please feel free to raise a request in channel here or on the mailing list.</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> Also in progress, I just drew up a minispec for DataSourceOVF so that VMware can support merging configuration sources from IMC and OVF if both are present. This allows OVF datasource to configure both static IP config as well as do ssh user imports (which was previously not possible)</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> As always, our in progress development generally will also be represented on trello</p> -<p>16:31 <code>&lt;blackboxsw&gt;</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:31 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> the following has landed in tip of master since last cloud-init status meeting</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> % git log --oneline --since 2019-07-22</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> - net/cmdline: split interfaces_by_mac and init network config</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> determination [Daniel Watkins]</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> - stages: allow data sources to override network config source order</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> [Daniel Watkins]</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> feel free to ask for help, reviews, discussions on any cloud-init items you're looking at. Otherwise I'll spend some time today getting through the review queue for cloud-init branches.</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> and doing some bug triage</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> thanks tribaal for jumping in BTW.</p> -<p>16:35 <code>&lt;tribaal&gt;</code> blackboxsw: my pleasure :)</p> -<p>16:36 <code>&lt;tribaal&gt;</code> I'm working on the review points in parallel during office hours as well, that should move things forward hopefully.</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> excellent just ping when ready this week and we'll give a quick pass.</p> -<p>16:46 <code>&lt;cyphermox&gt;</code> blackboxsw: yeah, I'm not sure about that eni/netplan conflict; you do need to remove old config from one to the other, otherwise they might fight, but not something I'd expect to break boot.</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> hiya cyphermox. agreed, I <em>think</em> we decided that cloud-init needed to be smart in the transition from netplan -&gt;` eni if someone does that on a system and cloud-init can warn about the behavior change, cleanup old netplan config and render eni in that case.</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> since cloud-init should be smart enough to know what it '</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> used to render</p> -<p>16:49 <code>&lt;cyphermox&gt;</code> ack</p> -<p>16:49 <code>&lt;cyphermox&gt;</code> yeah, now that I think of it we said the exact same thing last meeting, I think</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> +1, I'm just dusting the vacation cobwebs off. so didn't know if something else happened on that front last week</p> -<p>16:52 <code>&lt;cyphermox&gt;</code> well, I recall the convo, that's what I meant</p> -<p>17:06 <code>&lt;blackboxsw&gt;</code> I think that about wraps cloud-init status meeting for today folks. Thanks again. And drop us a line on the mailing list (cloud-init@lists.launchpad.net) or here in IRC anytime with questions/discussions.</p> -<p>17:06 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2019-07-22T16:15:00+00:002019-07-22T16:15:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2019-07-22:/status-2019-07-22.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 22 Jul at 16:15 &mdash; 17:15 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-07-22-16.15.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-07-22-16.15.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:17.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 22 Jul at 16:15 &mdash; 17:15 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-07-22-16.15.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-07-22-16.15.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:17.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a> </li> -<li><strong>ACTION</strong>: rharper to update <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a> status</li> -<li><strong>LINK</strong>: <a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-07-08-16.16.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-07-08-16.16.html</a> </li> -<li><strong>ACTION</strong>: rharper to followup with blackboxsw on pushing status minutes up to cloud-init.github.io page</li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:23.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/t/cloud-init-19-2-release/11873">https://discourse.ubuntu.com/t/cloud-init-19-2-release/11873</a> </li> -</ul> -<h3>In Progress Development</h3> -<p>The discussion about "In Progress Development" started at 16:27.</p> -<ul> -<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> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368508">https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368508</a> </li> -</ul> -<h3>In Progress Development</h3> -<p>The discussion about "In Progress Development" started at 16:36.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516">https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~xiaofengw/cloud-init/+git/cloud-init/+merge/367889">https://code.launchpad.net/~xiaofengw/cloud-init/+git/cloud-init/+merge/367889</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/369783">https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/369783</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/feature/stage_threadpool">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/feature/stage_threadpool</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://copr.fedorainfracloud.org/coprs/g/cloud-init/cloud-init-dev/">https://copr.fedorainfracloud.org/coprs/g/cloud-init/cloud-init-dev/</a> </li> -<li><strong>LINK</strong>: <a href="https://download.opensuse.org/repositories/Cloud:/Tools/">https://download.opensuse.org/repositories/Cloud:/Tools/</a> </li> -</ul> -<h2>Vote results</h2> -<h2>Action items, by person</h2> -<ul> -<li>rharper</li> -<li>rharper to update <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a> status</li> -<li>rharper to followup with blackboxsw on pushing status minutes up to cloud-init.github.io page</li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>rharper (69)</li> -<li>Goneri (20)</li> -<li>meetingology (6)</li> -<li>Odd_Bloke (5)</li> -<li>metsuke (4)</li> -<li>ubot5 (2)</li> -</ul> -<h2>Full Log</h2> -<p>16:15 <code>&lt;rharper&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:15 <code>&lt;meetingology&gt;</code> Meeting started Mon Jul 22 16:15:03 2019 UTC. The chair is rharper. Information about MeetBot at <a href="http://wiki.ubuntu.com/meetingology.">http://wiki.ubuntu.com/meetingology.</a></p> -<p>16:15 <code>&lt;meetingology&gt;</code> </p> -<p>16:15 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:15 <code>&lt;rharper&gt;</code> \o/</p> -<p>16:15 <code>&lt;rharper&gt;</code> #chair Odd_Bloke</p> -<p>16:15 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke rharper</p> -<p>16:15 <code>&lt;rharper&gt;</code> hi folks, welcome to another cloud-init community status meeting. All discussions and interjections welcome.</p> -<p>16:16 <code>&lt;rharper&gt;</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:16 <code>&lt;rharper&gt;</code> our format is the following topics: Previous Actions, Recent Changes, In-progress Development, Office Hours</p> -<p>16:16 <code>&lt;rharper&gt;</code> anyone is welcome to participate, interject, make suggestions or ask questions</p> -<p>16:16 <code>&lt;rharper&gt;</code> we host the meeting every two weeks at the date and time indicated in the IRC channel topic ^</p> -<p>16:17 <code>&lt;rharper&gt;</code> #topic Previous Actions</p> -<p>16:17 <code>&lt;Odd_Bloke&gt;</code> o/</p> -<p>16:17 <code>&lt;rharper&gt;</code> We had a few previous action items to look at</p> -<p>16:18 <code>&lt;rharper&gt;</code> <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a></p> -<p>16:18 <code>&lt;ubot5&gt;</code> Ubuntu bug 1832381 in cloud-init (Ubuntu) "vm fails to boot due to conflicting network configuration when user switches from netplan to eni" [Undecided,Incomplete]</p> -<p>16:18 <code>&lt;rharper&gt;</code> AnhVoMSFT was looking to collect logs from this scenario;</p> -<p>16:19 <code>&lt;Goneri&gt;</code> hey!</p> -<p>16:19 <code>&lt;rharper&gt;</code> it appears that getting an instance where the MAC address changes is harder so fewer folks trip over this; however, we agreed that cloud-init can track which renderer it used and if it switches it can clean up the config it wrote;</p> -<p>16:19 <code>&lt;rharper&gt;</code> #action rharper to update <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a> status</p> -<p>16:19 * meetingology rharper to update <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a> status</p> -<p>16:19 <code>&lt;ubot5&gt;</code> Ubuntu bug 1832381 in cloud-init (Ubuntu) "vm fails to boot due to conflicting network configuration when user switches from netplan to eni" [Undecided,Incomplete]</p> -<p>16:20 <code>&lt;rharper&gt;</code> The other action was to review <a href="https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785">https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785</a></p> -<p>16:20 <code>&lt;rharper&gt;</code> This was completed the other week while we worked toward the 19.2 release; that branch is currently work-in-progress, awaiting feedback/changes from submitter</p> -<p>16:21 <code>&lt;rharper&gt;</code> that's all of the action items from previous meeting</p> -<p>16:22 <code>&lt;rharper&gt;</code> previous meeting status found here:</p> -<p>16:22 <code>&lt;rharper&gt;</code> #link <a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-07-08-16.16.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-07-08-16.16.html</a></p> -<p>16:23 <code>&lt;rharper&gt;</code> normally at the cloud-init.github.io status page; looks like we didn't push the logs there.</p> -<p>16:23 <code>&lt;rharper&gt;</code> #action rharper to followup with blackboxsw on pushing status minutes up to cloud-init.github.io page</p> -<p>16:23 * meetingology rharper to followup with blackboxsw on pushing status minutes up to cloud-init.github.io page</p> -<p>16:23 <code>&lt;rharper&gt;</code> #topic Recent Changes</p> -<p>16:25 <code>&lt;rharper&gt;</code> % git log --oneline --since 2019-07-08</p> -<p>16:25 <code>&lt;rharper&gt;</code> a02c0c9 (HEAD -&gt;` master, origin/master, origin/HEAD) cloud_tests: updates and fixes</p> -<p>16:25 <code>&lt;rharper&gt;</code> 5498107 Fix bug rendering MTU on bond or vlan when input was netplan.</p> -<p>16:25 <code>&lt;rharper&gt;</code> b3a87fc net: update net sequence, include wait on netdevs, opensuse netrules path</p> -<p>16:25 <code>&lt;rharper&gt;</code> 060b1a1 (tag: 19.2, raharper/release/19.2, release/19.2, fix/fs_setup_custom_command_lp1801790) Release 19.2</p> -<p>16:25 <code>&lt;rharper&gt;</code> 07b1723 net: add rfc3442 (classless static routes) to EphemeralDHCP</p> -<p>16:25 <code>&lt;rharper&gt;</code> 1404817 templates/ntp.conf.debian.tmpl: fix missing newline for pools</p> -<p>16:25 <code>&lt;rharper&gt;</code> a785462 Support netplan renderer in Arch Linux</p> -<p>16:25 <code>&lt;rharper&gt;</code> a066ccd Fix typo in publicly viewable documentation.</p> -<p>16:26 <code>&lt;rharper&gt;</code> d9769c4 Add a cdrom size checker for OVF ds to ds-identify</p> -<p>16:26 <code>&lt;rharper&gt;</code> 9c47c68 VMWare: Trigger the post customization script via cc_scripts module.</p> -<p>16:26 <code>&lt;rharper&gt;</code> a24550a Cloud-init analyze module: Added ability to analyze boot events.</p> -<p>16:26 <code>&lt;rharper&gt;</code> a6faf3a Update debian eni network configuration location, retain Ubuntu setting</p> -<p>16:26 <code>&lt;rharper&gt;</code> e5f5421 net: skip bond interfaces in get_interfaces</p> -<p>16:26 <code>&lt;rharper&gt;</code> 217c893 Fix a couple of issues raised by a coverity scan</p> -<p>16:26 <code>&lt;rharper&gt;</code> biggest item in there is the 19.2 release</p> -<p>16:26 <code>&lt;rharper&gt;</code> #link <a href="https://discourse.ubuntu.com/t/cloud-init-19-2-release/11873">https://discourse.ubuntu.com/t/cloud-init-19-2-release/11873</a></p> -<p>16:26 <code>&lt;rharper&gt;</code> a big thank you from the cloud-init team to everyone who helped contribute to the release</p> -<p>16:27 <code>&lt;Goneri&gt;</code> do you have time for a little BSD update?</p> -<p>16:27 <code>&lt;rharper&gt;</code> Yes, let's talk about In progress developement</p> -<p>16:27 <code>&lt;rharper&gt;</code> #topic In Progress Development</p> -<p>16:27 <code>&lt;rharper&gt;</code> Goneri: go ahead</p> -<p>16:28 <code>&lt;Goneri&gt;</code> #topic FreeBSD/NetBSD status</p> -<p>16:28 <code>&lt;Goneri&gt;</code> so there is two active branches, the first one is: <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:28 <code>&lt;rharper&gt;</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:29 <code>&lt;Goneri&gt;</code> it has started with a tiny fix to address a configuration difference with FreeBSD (there is no chpasswd there)</p> -<p>16:29 <code>&lt;Goneri&gt;</code> and it's now a slightly bigger refactoring now, I believe it clarify the code base and I would like to land it like that.</p> -<p>16:30 <code>&lt;Goneri&gt;</code> a discussion is ongoing with rharper on the PR</p> -<p>16:30 <code>&lt;Goneri&gt;</code> second PR is <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:30 <code>&lt;Goneri&gt;</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:30 <code>&lt;Goneri&gt;</code> this one is much bigger, and I've just addressed the last comment from rharper, I test it often and it works fine for me</p> -<p>16:31 <code>&lt;Goneri&gt;</code> if you want to give it a try, I pushed some pre-built images here: <a href="http://bsd-cloud-image.org/">http://bsd-cloud-image.org/</a></p> -<p>16:31 <code>&lt;rharper&gt;</code> nice!</p> -<p>16:31 <code>&lt;Goneri&gt;</code> I test it with OpenStack and NoCloud, a friend who maintains CBSD also test it on Bhyve (FreeBSD)</p> -<p>16:32 <code>&lt;Goneri&gt;</code> finally, the last one is <a href="https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368508">https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368508</a></p> -<p>16:32 <code>&lt;Goneri&gt;</code> #link <a href="https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368508">https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368508</a></p> -<p>16:32 <code>&lt;Goneri&gt;</code> No active merge request yet because it depends on the two actives PR that I just mentioned</p> -<p>16:32 <code>&lt;Goneri&gt;</code> this patch brings NetBSD support (7 and 8)</p> -<p>16:33 <code>&lt;Goneri&gt;</code> I would like to work on OpenBSD later, but it's still a low priority</p> -<p>16:34 <code>&lt;rharper&gt;</code> Goneri: thanks for the update</p> -<p>16:34 <code>&lt;Goneri&gt;</code> finally, I've a bunch of scripts that I use to build my images</p> -<p>16:35 <code>&lt;Goneri&gt;</code> it's still rather raw, but I would like to integrate that at some point with your CI</p> -<p>16:35 <code>&lt;Goneri&gt;</code> that's all</p> -<p>16:35 <code>&lt;rharper&gt;</code> thanks</p> -<p>16:36 <code>&lt;rharper&gt;</code> #topic In Progress Development</p> -<p>16:36 <code>&lt;rharper&gt;</code> #link <a href="https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516">https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516</a></p> -<p>16:36 <code>&lt;rharper&gt;</code> Adding a new datasource for Exoscale</p> -<p>16:36 <code>&lt;rharper&gt;</code> #link <a href="https://code.launchpad.net/~xiaofengw/cloud-init/+git/cloud-init/+merge/367889">https://code.launchpad.net/~xiaofengw/cloud-init/+git/cloud-init/+merge/367889</a></p> -<p>16:36 <code>&lt;rharper&gt;</code> vmware user-defined-scripts</p> -<p>16:37 <code>&lt;rharper&gt;</code> #link <a href="https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/369783">https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/369783</a></p> -<p>16:37 <code>&lt;rharper&gt;</code> Allow datasources to configure the order of network-config sources</p> -<p>16:37 <code>&lt;rharper&gt;</code> #link <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/feature/stage_threadpool">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/feature/stage_threadpool</a></p> -<p>16:38 <code>&lt;Odd_Bloke&gt;</code> I'm expecting to have a response to Ryan's review comments on that today, and whatever conclusion we reach shouldn't be too much work to implement.</p> -<p>16:38 <code>&lt;rharper&gt;</code> definitely</p> -<p>16:38 <code>&lt;Odd_Bloke&gt;</code> And then I'll have a follow-up to split apart the "cmdline" network data source in to "cmdline" and "initramfs", which are currently conflated.</p> -<p>16:39 <code>&lt;Odd_Bloke&gt;</code> (Neither of these should cause behavioural changes, they're just setting us up for some data source work down the line.)</p> -<p>16:40 <code>&lt;rharper&gt;</code> The threadpool branch is a more general approach to handle running modules async from the mainthread; there were some limitations depending on systemd; and there is a desire for more than just disk_setup to run async; this branch I'm working on would allow modules to be tagged async and they run in a separate thread allowing the next module to proceed; we then join at the end of stage to ensure completion of threads;</p> -<p>16:41 <code>&lt;rharper&gt;</code> any other upstream development I'm missing?</p> -<p>16:43 <code>&lt;rharper&gt;</code> ok, I think that's it then;</p> -<p>16:43 <code>&lt;rharper&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:43 <code>&lt;rharper&gt;</code> feel free to ask for help, reviews, discussions on any cloud-init items you're looking at.</p> -<p>16:44 <code>&lt;metsuke&gt;</code> Is Ubuntu the recommended, or most maintained, distribution of cloud-init?</p> -<p>16:46 <code>&lt;rharper&gt;</code> metsuke: hi; cloud-init in Ubuntu is the most-up-to-date as we're both the upstream maintainers (working for Canonical) and handle getting the latest upstream into Ubuntu images</p> -<p>16:47 <code>&lt;rharper&gt;</code> metsuke: we also help produce daily rpm builds for RedHat/Centos/Fedora in our copr repo</p> -<p>16:47 <code>&lt;rharper&gt;</code> #link <a href="https://copr.fedorainfracloud.org/coprs/g/cloud-init/cloud-init-dev/">https://copr.fedorainfracloud.org/coprs/g/cloud-init/cloud-init-dev/</a></p> -<p>16:48 <code>&lt;rharper&gt;</code> #link <a href="https://download.opensuse.org/repositories/Cloud:/Tools/">https://download.opensuse.org/repositories/Cloud:/Tools/</a></p> -<p>16:48 <code>&lt;rharper&gt;</code> suse's cloud:Tools keeps a really recent cloud-init as well</p> -<p>16:48 <code>&lt;metsuke&gt;</code> great, thanks for the info!</p> -<p>16:48 <code>&lt;rharper&gt;</code> sure</p> -<p>16:49 <code>&lt;metsuke&gt;</code> I'm looking to distribute standardized VMs to 100+ sites running ESXi so I'm trying to find the best way to do that =)</p> -<p>16:52 <code>&lt;Odd_Bloke&gt;</code> metsuke: If you have any questions, please don't hesitate to ask in here; we're generally around US working hours, for reference.</p> -<p>16:53 <code>&lt;rharper&gt;</code> yes, cloud-init can help keep your base image generic, allowing customization to happen at boot time;</p> -<p>16:53 <code>&lt;metsuke&gt;</code> thanks, I'm trying to do some preliminary investigation so I have an intelligent question to ask =P</p> -<p>17:15 <code>&lt;rharper&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2019-07-08T16:16:00+00:002019-07-08T16:16:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2019-07-08:/status-2019-07-08.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 08 Jul at 16:16 &mdash; 17:32 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-07-08-16.16.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-07-08-16.16.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:18.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-06-24.html#status-2019-06-24">https://cloud-init.github.io/status-2019-06-24.html#status-2019-06-24 …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 08 Jul at 16:16 &mdash; 17:32 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-07-08-16.16.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-07-08-16.16.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:18.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-06-24.html#status-2019-06-24">https://cloud-init.github.io/status-2019-06-24.html#status-2019-06-24</a> </li> -<li><strong>ACTION</strong>: query on incomplete <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a> with AnhVoMSFT to see if this needs priority</li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:22.</p> -<h3>In Progress Development</h3> -<p>The discussion about "In Progress Development" started at 16:27.</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="https://trello.com/c/RhevWnHx/1064-azure-imds-handle-multiple-default-routes-static-ips-in-primary-subnet">https://trello.com/c/RhevWnHx/1064-azure-imds-handle-multiple-default-routes-static-ips-in-primary-subnet</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/369792">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/369792</a> </li> -<li><strong>LINK</strong>: <a href="https://trello.com/c/TMK5ZDMf/1108-azure-async-disk-mounts">https://trello.com/c/TMK5ZDMf/1108-azure-async-disk-mounts</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516">https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516</a> </li> -<li><strong>LINK</strong>: <a href="https://wiki.ubuntu.com/CloudinitUpdates">https://wiki.ubuntu.com/CloudinitUpdates</a> </li> -<li><strong>ACTION</strong>: review Azure telemetry branch <a href="https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785">https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785</a></li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~bitfehler/cloud-init/+git/cloud-init/+merge/369814">https://code.launchpad.net/~bitfehler/cloud-init/+git/cloud-init/+merge/369814</a> </li> -</ul> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 16:48.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://netplan.io">https://netplan.io</a> for more info</li> -</ul> -<h2>Vote results</h2> -<h2>Action items, by person</h2> -<ul> -<li>AnhVoMSFT</li> -<li>query on incomplete <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a> with AnhVoMSFT to see if this needs priority</li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (89)</li> -<li>Odd_Bloke (13)</li> -<li>bitfehler (10)</li> -<li>tribaal (8)</li> -<li>AnhVoMSFT (7)</li> -<li>chad-aws (6)</li> -<li>meetingology (5)</li> -<li>ubot5 (3)</li> -<li>robjo (2)</li> -<li>rharper (2)</li> -</ul> -<h2>Full Log</h2> -<p>16:16 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:16 <code>&lt;meetingology&gt;</code> Meeting started Mon Jul 8 16:16:57 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:16 <code>&lt;meetingology&gt;</code> </p> -<p>16:16 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:17 <code>&lt;Odd_Bloke&gt;</code> bitfehler: It works for me on an Ubuntu eoan system, locally.</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> hi folks, welcome to another cloud-init community status meeting. All discussions and interjections welcome.</p> -<p>16:17 <code>&lt;Odd_Bloke&gt;</code> bitfehler: What version of Python 3 are you using?</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> loud-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:17 <code>&lt;blackboxsw&gt;</code> our format is the following topics: Previous Actions, Recent Changes, In-progress Development, Office Hours</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> anyone is welcome to participate, interject, make suggestions or ask questions</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> we host the meeting every two weeks at the date and time indicated in the IRC channel topic ^</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> I'm looking through our meeting minutes now from the previous meeting</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2019-06-24.html#status-2019-06-24">https://cloud-init.github.io/status-2019-06-24.html#status-2019-06-24</a></p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> Touch base with AnhVoMSFT by next status on priority of <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a></p> -<p>16:19 <code>&lt;ubot5&gt;</code> Ubuntu bug 1832381 in cloud-init (Ubuntu) "vm fails to boot due to conflicting network configuration when user switches from netplan to eni" [Undecided,Incomplete]</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> I think AnhVoMSFT may have been looking to get cloud-init logs on a system reproducing this problem</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> so let's carry this over for next meeting and this bug is marked incomplete until we have some cloud-init logs to debug</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> #action query on incomplete <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a> with AnhVoMSFT to see if this needs priority</p> -<p>16:21 * meetingology query on incomplete <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a> with AnhVoMSFT to see if this needs priority</p> -<p>16:21 <code>&lt;ubot5&gt;</code> Ubuntu bug 1832381 in cloud-init (Ubuntu) "vm fails to boot due to conflicting network configuration when user switches from netplan to eni" [Undecided,Incomplete]</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> no further actions listed from last meeting</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:22 <code>&lt;AnhVoMSFT&gt;</code> blackboxsw I did hear back from networking on how to trigger mac address change, so I'll work on that this week and get the logs attached</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> excellent AnhVoMSFT thanks!</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> and thanks for joining the meeting</p> -<p>16:22 <code>&lt;AnhVoMSFT&gt;</code> the harder it is to reproduce, the better, since it's unlikely to affect that many customers</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> +1</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> the following are commits that landed in tip of master for cloud-init upstream</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> - Add missing dsname for Hetzner Cloud datasource [Markus Schade]</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> - doc: indicate that netplan is default in Ubuntu now [Daniel Watkins]</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> - azure: add region and AZ properties from imds compute location metadata</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> [Chad Smith]</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> - sysconfig: support more bonding options [Penghui Liao]</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> - cloud-init-generator: use libexec path to ds-identify on redhat systems</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> [Ryan Harper] (<a href="[https://bugs.launchpad.net/bugs/1833264](https://bugs.launchpad.net/bugs/1833264)">LP: #1833264</a>)</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> - tools/build-on-freebsd: update to python3 [Gonéri Le Bouder]</p> -<p>16:24 <code>&lt;ubot5&gt;</code> Ubuntu bug 1833264 in cloud-init "cloud-init-generator hardcodes path to ds-identify" [Undecided,Fix committed]</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> though I think the bottom two of those commits I may have reported last meeting</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> beyond that I know that paride has resolved a couple of issues with our CI infrastructure not cleaning up stale containers which would have triggered a number of CI failures over the last few weeks.</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> I think that about wraps 'completed' work in tip.</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> #topic In Progress Development</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> We mentioned this last meeting, there are a couple of longer features we are working on that will hit cloud-init tip soon.</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> we track our work on trello at the following url</p> -<p>16:28 <code>&lt;blackboxsw&gt;</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:29 <code>&lt;blackboxsw&gt;</code> In trying to enable secondary IP configuration on Azure platforms, we discovered a systemd-networkd bug related to classless routes not getting the appropriate source IP configuration</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> per this card</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> #link <a href="https://trello.com/c/RhevWnHx/1064-azure-imds-handle-multiple-default-routes-static-ips-in-primary-subnet">https://trello.com/c/RhevWnHx/1064-azure-imds-handle-multiple-default-routes-static-ips-in-primary-subnet</a></p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> Dan Streetman filed a bug and upstream systemd fix for this <a href="https://github.com/systemd/systemd/issues/12969">https://github.com/systemd/systemd/issues/12969</a></p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> and he's working on getting that released into Ubuntu Eoan. cloud-init may need a minor fix to only render static IPs if systemd-networkd version contains the latest fix.</p> -<p>16:31 <code>&lt;chad-aws&gt;</code> secondary addresses on azure too, or aws?</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> chad-aws: I also have just pushed a branch for review that will add secondary IPs from AWS's Datasource as well</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> since we had context on the netplan we need to generate that</p> -<p>16:31 <code>&lt;chad-aws&gt;</code> ok</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/369792">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/369792</a></p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> chad-aws: the one question I think we might have to discuss related to the above branch is whether or not cloud-init on older LTSes (Xenial, Bionic) should change behavior to attempt rendering secondary IP information or not (because that would be a change in behavior)</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> generally we try to retain existing behavior on old Ubuntu LTS releases so we don't surprise folks who may have worked around previous limitations of cloud-init (like manually/scripted adding their own secondary IP information)</p> -<p>16:35 <code>&lt;chad-aws&gt;</code> (Note I am not the chad.smith above, but I am interested too.)</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> hehe, yes, I am not talking to myself (blackboxsw == chad.smith)</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> also in progress is rharper's good work on teasing out async mount functionality per the following</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> #link <a href="https://trello.com/c/TMK5ZDMf/1108-azure-async-disk-mounts">https://trello.com/c/TMK5ZDMf/1108-azure-async-disk-mounts</a></p> -<p>16:36 <code>&lt;chad-aws&gt;</code> I think different config files should make different behavior and that's okay.</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> +1 chad-aws</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> the async mount feature is the ability to allow cloud-init defer some disk mounts until later in the cloud-init stages to allow folks to ssh to the vms earlier in the boot process</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> as some systems with lots of mounts may block for a while trying to mount and format disks</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> while this approach is tagged as azure, rharper is approaching it in a generic way that should make this functionality accessible to many platforms</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> paride: rharper Odd_Bloke anything else I'm forgetting in progress?</p> -<p>16:40 <code>&lt;rharper&gt;</code> blackboxsw: right; it's changes to cc_disk_setup/cc_mount handling</p> -<p>16:40 <code>&lt;rharper&gt;</code> blackboxsw: nothing I can think of</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> we probably should cut an Ubutuu Eoan upload of cloud-init tip soon, but I don't know when that should be scheduled?</p> -<p>16:41 <code>&lt;Odd_Bloke&gt;</code> I'm doing some work to modify the way we determine network config sources, but that shouldn't affect any data sources that don't opt in to it.</p> -<p>16:41 <code>&lt;AnhVoMSFT&gt;</code> i looked at it briefly, this involves calling a systemd unit to format/mount - do we report error back to cloud-init ?</p> -<p>16:41 * tribaal raises hand</p> -<p>16:41 <code>&lt;tribaal&gt;</code> is there any rough estimation on where that tip cut would be?</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> tribaal: ahh yes awesome, forgot. tribaal has a new datasource</p> -<p>16:41 <code>&lt;tribaal&gt;</code> yes, thanks a lot for your reviews everyone</p> -<p>16:42 <code>&lt;tribaal&gt;</code> nice working with you guys again :)</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516">https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516</a></p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> for Exoscale ^</p> -<p>16:42 <code>&lt;tribaal&gt;</code> Ideally we'd target the next release for our datasource as well, but of course it's not landed yet so if the cut is e.g. tomorrow it might be a bit tight :)</p> -<p>16:42 <code>&lt;Odd_Bloke&gt;</code> Specifically, if a platform does any networking setup during the initramfs (such as for iSCSI), cloud-init will <em>only</em> consider the initramfs-provided configuration at the moment.</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> tribaal: for eoan, we can just grab tip of master at anypoint for an upload since it</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> is still a development release</p> -<p>16:43 <code>&lt;tribaal&gt;</code> ack</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> so it's super low weight for our release (and we should do it often)</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> also we have planned/upcoming an SRU into Xenial/Bionic/Disco on July 15th (so next week)</p> -<p>16:44 <code>&lt;tribaal&gt;</code> as far as SRUs are concerned, would that typically be something that would be backported, or not?</p> -<p>16:44 <code>&lt;Odd_Bloke&gt;</code> I'm making it possible for data sources to specify a different order for the network config sources, so that platforms where iSCSI is the default can have their data source's network config preferred.</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> tribaal: and others: cloud-init SRUs our tip into every release due to an SRU exception that we have with Ubuntu</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> so we upload latest code into each SRU target series for ubuntu</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> though we may patch/disable some functionality that is deemed a change in behavior from previous release</p> -<p>16:45 <code>&lt;tribaal&gt;</code> blackboxsw: understood, thanks. I'll schedule some time for myself to work on it "full time" as much as possible, so we can make the cut.</p> -<p>16:45 <code>&lt;Odd_Bloke&gt;</code> I'm also splitting apart explicitly-from-the-user cmdline configuration (i.e. network-data=...) from the initramfs-provided values (ip=... or iBFT), so that data sources can be configured to still allow explicit user network configuration to override data source network configuration.</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> here's our SRU process for those interested</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> #link <a href="https://wiki.ubuntu.com/CloudinitUpdates">https://wiki.ubuntu.com/CloudinitUpdates</a></p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> so this meeting (and an email to cloud-init mailinglist) will serve as a call for branches/features for SRU.</p> -<p>16:46 <code>&lt;Odd_Bloke&gt;</code> But as I said previously, this is all just refactoring except for the specific places we need this functionality.</p> -<p>16:46 <code>&lt;AnhVoMSFT&gt;</code> I sent a merge proposal for adding some more telemetry for Azure: <a href="https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785">https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785</a> - would appreciate a review. Trying to make it in before next SRU</p> -<p>16:46 <code>&lt;AnhVoMSFT&gt;</code> also will send a merge proposal today or tomorrow on the case sensitivity issue when checking is_new_instance</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> if folks are interested in getting a specific feature/bug or branch reviewed/fixed and published, please raise your hand, ping in channel or send email to the mailing list to make sure the need is not forgotten</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> #action review Azure telemetry branch <a href="https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785">https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785</a></p> -<p>16:47 * meetingology review Azure telemetry branch <a href="https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785">https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785</a></p> -<p>16:47 <code>&lt;bitfehler&gt;</code> i feel a bit awkward stepping in here, but i kind of do</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: we also have reviewed samgilson's branch on a new cloud-init analyze subcommand for boot performance</p> -<p>16:48 <code>&lt;bitfehler&gt;</code> sorry, i am pretty new to cloud-init, but i did open a merge proposal today</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> bitfehler: no worries, conversations gotta happen :)</p> -<p>16:48 <code>&lt;Odd_Bloke&gt;</code> #link <a href="https://code.launchpad.net/~bitfehler/cloud-init/+git/cloud-init/+merge/369814">https://code.launchpad.net/~bitfehler/cloud-init/+git/cloud-init/+merge/369814</a></p> -<p>16:48 <code>&lt;Odd_Bloke&gt;</code> (Can I do that, or only blackboxsw?)</p> -<p>16:48 <code>&lt;AnhVoMSFT&gt;</code> thanks blackboxsw, last I synced with him, Sam is actively working on addressing your comments</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> I'll tick the topic to office hours which is really just open season for discussion or reviews</p> -<p>16:48 <code>&lt;robjo&gt;</code> Does anyone know if VMware has any plans to move their source from <a href="https://github.com/vmware/cloud-init-vmware-guestinfo">https://github.com/vmware/cloud-init-vmware-guestinfo</a> to be included in upstream cloud-init?</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:51 <code>&lt;bitfehler&gt;</code> i think my main question would have been how to best get in touch with you, but i think i found the answer already :)</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> hrm, first I've seen of that robjo . maybe we can ping Sankar on that to see what the motivation is there</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> bitfehler: either here or mail cloud-init@lists.launchpad.net</p> -<p>16:52 <code>&lt;robjo&gt;</code> I was just made aware of this last week via "please create a packge' to which my initial answer is No, the VMware code should be in cloud-init proper</p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> per vmware,yeah that makes sense for them to try to get that cloud-init datasource upstream. forcing every distro to do their packaging for them is not really the right solution</p> -<p>16:54 <code>&lt;bitfehler&gt;</code> one other thing i was wondering: do you feel a plain systemd-networkd network renderer would make sense? i wrote a very basic one trying to get better cloud-init support for Arch Linux</p> -<p>16:54 <code>&lt;bitfehler&gt;</code> it sort of works, but I am not sure whether this goal worth pursuing?</p> -<p>16:57 <code>&lt;blackboxsw&gt;</code> bitfehler: interesting, right so we have netplan render which ultimately renders networkd on our behalf on ubuntu,</p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> if direct networkd render is the only way to support network config on Arch linux I don't see why we wouldn't want that.... rharper or Odd_Bloke? (maybe I'm missing the concern)</p> -<p>16:59 <code>&lt;bitfehler&gt;</code> i saw the comments about networkd above, but i am not familiar with netplan. it is another layer in between, right?</p> -<p>17:00 <code>&lt;Odd_Bloke&gt;</code> bitfehler: netplan takes v2 network configuration and renders it for a target backend. The two supported backends ATM are networkd and NetworkManager.</p> -<p>17:00 <code>&lt;blackboxsw&gt;</code> <a href="https://netplan.io">https://netplan.io</a> for more info</p> -<p>17:00 <code>&lt;bitfehler&gt;</code> oh, wow, i overlooked that. so it doesn't need any additional software?</p> -<p>17:01 <code>&lt;AnhVoMSFT&gt;</code> it does need netplan</p> -<p>17:01 <code>&lt;bitfehler&gt;</code> oh wait, netplan is a renderer itself, and that supports the two backends</p> -<p>17:02 <code>&lt;Odd_Bloke&gt;</code> Right, netplan is the intended way for cloud-init to render network config for networkd.</p> -<p>17:03 <code>&lt;bitfehler&gt;</code> ok, got it. i guess i could also look into porting netplan to arch then? not sure what an effort that would be</p> -<p>17:05 <code>&lt;Odd_Bloke&gt;</code> IMO, that would be the best way to go, if it's tractable.</p> -<p>17:05 <code>&lt;Odd_Bloke&gt;</code> We ideally wouldn't reimplement netplan's networkd renderer in cloud-init. :)</p> -<p>17:05 <code>&lt;bitfehler&gt;</code> i'll let you know soon ;)</p> -<p>17:08 <code>&lt;chad-aws&gt;</code> I guess this should go both ways. Is there anything AWS EC2 can do better or different?</p> -<p>17:25 <code>&lt;blackboxsw&gt;</code> nice chad-aws, sorry I got pulled into a second meeting. chad-aws I did have a question about metadata versioning in aws.</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> how are new features communicated for a new metadata version</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> I reference <a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html">https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html</a></p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> but it didn't have a specific note on the changes added for 2018-09-24 which I used in my branch</p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> only the first version that a field was introduced, not that local_ipv4s changed value from string to list in 2018-09-24.</p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> so I guess my question is, is there a better source of truth for ec2 metadata values that we should be looking at</p> -<p>17:28 <code>&lt;blackboxsw&gt;</code> chad-aws: sorry (I realize that's a question out of left field)</p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> I think I'll wrap the meeting here. Thank you all again for the attending this week.</p> -<p>17:31 <code>&lt;chad-aws&gt;</code> thx</p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> Again plan for cloud-init 19.2 SRU is scheduled for next week so any features/branches that need landing or review should be raised here or on the mailing list</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> minutes will be posted at <a href="https://cloud-init.github.io">https://cloud-init.github.io</a></p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2019-06-24T16:18:00+00:002019-06-24T16:18:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2019-06-24:/status-2019-06-24.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 24 Jun at 16:18 &mdash; 17:33 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-06-24-16.18.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-06-24-16.18.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:23.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-06-10.html#status-2019-06-10">https://cloud-init.github.io/status-2019-06-10.html#status-2019-06-10 …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 24 Jun at 16:18 &mdash; 17:33 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-06-24-16.18.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-06-24-16.18.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:23.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-06-10.html#status-2019-06-10">https://cloud-init.github.io/status-2019-06-10.html#status-2019-06-10</a> </li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a> </li> -<li><strong>ACTION</strong>: Touch base with AnhVoMSFT by next status on priority of <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a></li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:28.</p> -<h3>In Progress Development</h3> -<p>The discussion about "In Progress Development" started at 16:31.</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="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/feature/disk_setup_async">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/feature/disk_setup_async</a> is the WIP branch</li> -<li><strong>LINK</strong>: <a href="https://trello.com/c/TMK5ZDMf/1108-azure-async-disk-mounts">https://trello.com/c/TMK5ZDMf/1108-azure-async-disk-mounts</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>Action items, by person</h2> -<ul> -<li>AnhVoMSFT</li> -<li>Touch base with AnhVoMSFT by next status on priority of <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a></li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (73)</li> -<li>rharper (23)</li> -<li>AnhVoMSFT (18)</li> -<li>nik736 (12)</li> -<li>ubot5 (4)</li> -<li>meetingology (4)</li> -</ul> -<h2>Full Log</h2> -<p>16:18 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:18 <code>&lt;meetingology&gt;</code> Meeting started Mon Jun 24 16:18:34 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:18 <code>&lt;meetingology&gt;</code> </p> -<p>16:18 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> welcome to another episode of cloud-init status updates.</p> -<p>16:20 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> our format is the following topics: Previous Actions, Recent Changes, In-progress Development, Office Hours</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> anyone is welcome to participate, interject, make suggestions or ask questions</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> generally we try to host this meeting every two weeks on the day listed in the channel topic</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> last meeting</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2019-06-10.html#status-2019-06-10">https://cloud-init.github.io/status-2019-06-10.html#status-2019-06-10</a></p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> we had an action to follow up on any bugs related to installing ifupdown on a system that had netplan installed by default.</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> I believe we did see a bug come in from Azure about that.... checking for that bug id now</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> #1832381</p> -<p>16:25 <code>&lt;rharper&gt;</code> bug #1832381</p> -<p>16:25 <code>&lt;ubot5&gt;</code> bug 1832381 in cloud-init (Ubuntu) "vm fails to boot due to conflicting network configuration when user switches from netplan to eni" [Undecided,Incomplete] <a href="https://launchpad.net/bugs/1832381">https://launchpad.net/bugs/1832381</a></p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a></p> -<p>16:25 <code>&lt;AnhVoMSFT&gt;</code> There is an action item on me to attach a log to that bug. Since the incident created by the customer was closed and we did not have permission to share his log, I will need to get a repro and retrieve the log. It's not very easy to trigger a mac address change in Azure these days</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> thanks AnhVoMSFT for this bug</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> ok if we carry over that action item then for next status meeting AnhVoMSFT (just to close the loop if it's important)</p> -<p>16:27 <code>&lt;AnhVoMSFT&gt;</code> yep - once I get some help from our networking folks to trigger a mac address change I'll update the bug with more logs</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> #action Touch base with AnhVoMSFT by next status on priority of <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a></p> -<p>16:27 * meetingology Touch base with AnhVoMSFT by next status on priority of <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a></p> -<p>16:27 <code>&lt;ubot5&gt;</code> Ubuntu bug 1832381 in cloud-init (Ubuntu) "vm fails to boot due to conflicting network configuration when user switches from netplan to eni" [Undecided,Incomplete]</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> good deal. that's all we had for actions from last meeting</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> the following items have landed on tip of cloud-init's master branch</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> - sysconfig: support more bonding options [Penghui Liao]</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> - cloud-init-generator: use libexec path to ds-identify on redhat systems</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> [Ryan Harper] (<a href="[https://bugs.launchpad.net/bugs/1833264](https://bugs.launchpad.net/bugs/1833264)">LP: #1833264</a>)</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> - tools/build-on-freebsd: update to python3 [Gonéri Le Bouder]</p> -<p>16:30 <code>&lt;ubot5&gt;</code> Ubuntu bug 1833264 in cloud-init "cloud-init-generator hardcodes path to ds-identify" [Undecided,Fix committed]</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> thanks to Penghui and Gonéri for driving additional changes for cloud-init in this last sessions</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> session*</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> #topic In Progress Development</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> there a number of longer items for feature work in progress that should see some light soon</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> We track these features in trello as always</p> -<p>16:33 <code>&lt;blackboxsw&gt;</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:33 <code>&lt;blackboxsw&gt;</code> minor fixup for Azure instance-data.json (cloud-init query) for region and availability zone should land today</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> rharper: and blackboxsw are working on Azure-related route tables and async disk mount features</p> -<p>16:36 <code>&lt;AnhVoMSFT&gt;</code> is there any bug/discussion item for the async disk mount?</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: rharper has been testing out systemd unit magic for setting up disk mounts async and initial numbers look good. How to bake that work into cloud-init is the next small hurdle I think. (I thought he mentioned today in our standup a 50% speed increase due to async mounts instead of sync waits)</p> -<p>16:38 <code>&lt;rharper&gt;</code> <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/feature/disk_setup_async">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/feature/disk_setup_async</a> is the WIP branch</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: I expect we'll have something in the next couple of days.</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> orrr right now. thanx rharper</p> -<p>16:39 <code>&lt;AnhVoMSFT&gt;</code> that sounds really cool. I'll check it out</p> -<p>16:39 * blackboxsw creates a trello card that can be watched for this feature</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> #link <a href="https://trello.com/c/TMK5ZDMf/1108-azure-async-disk-mounts">https://trello.com/c/TMK5ZDMf/1108-azure-async-disk-mounts</a></p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> feel free to subscribe to any trello cards folks see that are of interest. you will get an email if the card changes state, like from Doing to Done or if new links are added</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: rharper process question</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> what do you guys think about us turning on voting on trello cards</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> people with interest on a feature/card in our backlog could upvote it and that <em>could</em> help drive what features we grab over time</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> dunno, thought it might be something we could toss around to see if that would make sense. the board it public after all</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> <em>is public</em> rather</p> -<p>16:43 <code>&lt;rharper&gt;</code> maybe; I worry about random +1 without any more context. Platform developers already work with us; and community folks file bugs/merge proposals</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> good point.</p> -<p>16:44 <code>&lt;rharper&gt;</code> I'm open to the idea</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> for sure, if it gets interest, we can think about adding that feature. can't hurt to have some additional input, unfounded though it may be.</p> -<p>16:45 <code>&lt;AnhVoMSFT&gt;</code> agreed on the usefulness might be limited. You guys are already talking to each other. Platform developers either engage directly on this board or through out of band channel (sync meeting with Canonical product groups, etc...)</p> -<p>16:46 <code>&lt;AnhVoMSFT&gt;</code> Perhaps you can try it out for a couple release periods and see how it works out</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> yeah, /me just likes all the shiny objects pretty icons ;) ... need to control myself</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> thx AnhVoMSFT +1.</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> so I think that about wraps in-progress development. I know paride has been tirelessly working on our CI infrastructure to improve quality of CI and false positives for failures due to resource constraints. So big thanks for paride working on our jenkins workers</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> This is an open topic to bring any cloud-init discussions, bugs, concerns or feature requests folks have.</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> In the absence of such topics we spend part of this time grooming the review queue to get back to dev</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> contributors so that they don't have stale branches waiting for input</p> -<p>16:50 <code>&lt;AnhVoMSFT&gt;</code> We had a review sent out to add some boot time telemetry collection as part of cloud-init analyze: <a href="https://code.launchpad.net/~samgilson/cloud-init/+git/cloud-init/+merge/368943">https://code.launchpad.net/~samgilson/cloud-init/+git/cloud-init/+merge/368943</a></p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> thanks AnhVoMSFT I'll grab a review slot on that one now</p> -<p>16:51 <code>&lt;AnhVoMSFT&gt;</code> would appreciate some reviews there and also on ideas on how to retrieve similar timestamps for FreeBSD</p> -<p>16:51 <code>&lt;rharper&gt;</code> AnhVoMSFT: yes, will review</p> -<p>16:51 <code>&lt;rharper&gt;</code> AnhVoMSFT: also, I filed a bug related to the azure telemetry, lemme get it</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> I'll kick off a CI run on that now</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> rharper: ^</p> -<p>16:52 <code>&lt;rharper&gt;</code> Bug 1833731</p> -<p>16:52 <code>&lt;ubot5&gt;</code> bug 1833731 in cloud-init "cloud-init analyze output not formatted cleanly on Azure" [Undecided,New] <a href="https://launchpad.net/bugs/1833731">https://launchpad.net/bugs/1833731</a></p> -<p>16:52 <code>&lt;rharper&gt;</code> AnhVoMSFT: not sure if the branch for review addresses the formatting of the output, but we should take a look to clean it up</p> -<p>16:52 <code>&lt;AnhVoMSFT&gt;</code> is there a good way to subscribe to new bugs with a certain keyword/tags? I.e., I would like to auto-subscribe to all bugs that has "Azure" in the bug title</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> rharper: if you get a chance to double check <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/369199">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/369199</a> we might be able to land that too</p> -<p>16:53 <code>&lt;rharper&gt;</code> blackboxsw: I asked you some questions, if you've replied, I'll look again</p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> rharper: nevermind, I see you already looked at it</p> -<p>16:53 <code>&lt;rharper&gt;</code> ah</p> -<p>16:53 <code>&lt;rharper&gt;</code> perfect</p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> thanks</p> -<p>16:53 <code>&lt;rharper&gt;</code> I think we're mostly fine; just a question on return values</p> -<p>16:53 * blackboxsw needed to refresh</p> -<p>16:54 <code>&lt;AnhVoMSFT&gt;</code> rharper I will take a look at the analyze output and see how we can improve it. If it is a minor change we can add it to the existing review</p> -<p>16:54 <code>&lt;rharper&gt;</code> AnhVoMSFT: no need to pull it into the existing stuff</p> -<p>16:55 <code>&lt;rharper&gt;</code> I'd prefer a separate targetted fix; which may land independently from the boot stage (which is super interesting on its own)</p> -<p>16:55 <code>&lt;AnhVoMSFT&gt;</code> cool - we will do a separate fix then</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> rharper: yeah that concern is clear, we are safe on the processing of region/az in absence of 'imds' key</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> it'll return none</p> -<p>16:57 <code>&lt;blackboxsw&gt;</code> by virtue of that last get('location|platformFaultDomain')</p> -<p>16:57 <code>&lt;blackboxsw&gt;</code> if either is absent due to any key above being absent, you'll get None as default value</p> -<p>16:58 <code>&lt;rharper&gt;</code> blackboxsw: ack</p> -<p>17:00 <code>&lt;nik736&gt;</code> Hi there, not sure if this is the right place to ask, but I have problems when creating a new VM, it only happens with the debian cloud image, ubuntu is fine. Booting is stuck at the drm line, the exact line is dependent on the video model type in my libvirt xml but it is basically stuck for 20-30sec and won't continue. It will boot eventually after that time. Thanks so much for any hints. Happy to provide</p> -<p>17:00 <code>&lt;nik736&gt;</code> further details.</p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> hrm, video model timeouts are a bit out of my wheelhouse :/</p> -<p>17:02 * blackboxsw pokes around a bit in google</p> -<p>17:02 <code>&lt;nik736&gt;</code> it seems to be that the lines after it would be about resizing the file system. I am not really sure if this is cloud-init related at all and I am not sure if it actually is caused by the video model or is just taking a bit to get to the next steps</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> nik736: you can run cloud-init analyze show or cloud-init analyze blame to see what cloud-init says it is spending a lot of time on</p> -<p>17:03 <code>&lt;nik736&gt;</code> I tried different host systems, Debian 18.04, 19.04, Debian 9, different libvirt versions, different qemu versions, nothing seems to be helping lol</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> (If you have cloud-init v 18 or later in your image I think)</p> -<p>17:04 <code>&lt;nik736&gt;</code> ah, ok, thanks, I will look into that</p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> nik736: also systemd-analyze blame is a good helper for what is killing boot time</p> -<p>17:04 <code>&lt;AnhVoMSFT&gt;</code> do you see any timestamp gap that reflects the 20-30s in cloud-init.log ?</p> -<p>17:08 <code>&lt;rharper&gt;</code> nik736: feel free to file a bug and attach logs from the 'cloud-init collect-logs' output (or serial console if available) and /var/log/cloud-init.log if you can get into the instance afterwards</p> -<p>17:08 <code>&lt;nik736&gt;</code> thanks for the help, currently looking into it</p> -<p>17:11 <code>&lt;AnhVoMSFT&gt;</code> rharper blackboxsw we have some instance deployment where cloud-init is hanging at the command ip route add - any idea how to look further?</p> -<p>17:12 <code>&lt;AnhVoMSFT&gt;</code> this does look like a platform problem, so it is more of a question related to networking, rather than cloud-init itself</p> -<p>17:14 <code>&lt;AnhVoMSFT&gt;</code> it's super hard to reproduce so the only thing we have so far to work with is logs. I thought the call to ip route add basically adds an entry to the kernel routing table. Is there an interaction with networking involved which might cause it to hang?</p> -<p>17:14 <code>&lt;rharper&gt;</code> AnhVoMSFT: I wonder if it's creating a route that breaks connection to IMDS or something else that cloud-init would then do an HTTP get on ?</p> -<p>17:17 <code>&lt;nik736&gt;</code> I saw in the log that 2 entries are around 1 minute apart "SUCCESS: searching for local datasources" and "Cloud-init v. 0.7.9 running 'init' at Mon, 24 Jun 2019 17:13:41 +0000. Up 73.67 seconds." I am not sure if this could be it or if this looks fine</p> -<p>17:18 <code>&lt;rharper&gt;</code> 0.7.9 is quite old, seeing the full cloud-init.log will be most useful for us to understand what's happening</p> -<p>17:19 <code>&lt;nik736&gt;</code> okay, sec</p> -<p>17:19 <code>&lt;AnhVoMSFT&gt;</code> rharper that is a good theory. I do see in a good case there's a call to IMDS immediately after that, although that call has a timeout. If it fails we should see more logs coming out of cloud-init. I'll look further into that todya</p> -<p>17:20 <code>&lt;nik736&gt;</code> @rharper <a href="https://pastebin.com/fzCSH5kC">https://pastebin.com/fzCSH5kC</a></p> -<p>17:20 <code>&lt;rharper&gt;</code> AnhVoMSFT: the retry logic in DataSourceAzure is quite long IIRC, so it's quite possible this is the very issue that blackboxsw is working w.r.t ensuring the instances always have a source-ip route to the IMDS</p> -<p>17:21 <code>&lt;AnhVoMSFT&gt;</code> rharper indeed it is long, and the log was overly suppressed to avoid log from growing too large while VM was waiting in pre-provisioning state. We are adding back some of the logs (in a smarter way to get enough details while avoiding huge log size)</p> -<p>17:22 <code>&lt;rharper&gt;</code> nik736: so, between line 260 and 261 there's a large timedelta; that's <em>outside</em> of cloud-init; cloud-init is executed separately 4 times (cloud-init init --local, cloud-init init, cloud-init config --modules, cloud-init config --final)</p> -<p>17:23 <code>&lt;rharper&gt;</code> nik736: so if you have a systemd journal, we could see what happens between the end of cloud-init-local.service and cloud-init.service (stage1 and 2);</p> -<p>17:23 <code>&lt;nik736&gt;</code> ah, okay, interesting</p> -<p>17:23 <code>&lt;nik736&gt;</code> will check</p> -<p>17:23 <code>&lt;rharper&gt;</code> or syslog might see stuff between those two time points</p> -<p>17:23 * rharper steps away for a bit, please keep sending info here; I'll respond when I;m back</p> -<p>17:24 <code>&lt;AnhVoMSFT&gt;</code> nik736 systemd-analyze critical-chain cloud-init.service might help here - I think some systemd service is running right after init-local and just before init and that service is taking time</p> -<p>17:25 <code>&lt;nik736&gt;</code> will check, thanks for your help, really appreciate it.</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> I think I'll wrap the meeting here, but we can continue the conversation. Thanks again folks for the discussions</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> next meeting will be July 8th</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> as updated in the topic</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> meeting minutes will be posted to</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io">https://cloud-init.github.io</a></p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2019-06-10T16:19:00+00:002019-06-10T16:19:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2019-06-10:/status-2019-06-10.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 10 Jun at 16:19 &mdash; 17:31 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-06-10-16.19.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-06-10-16.19.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io">https://cloud-init.github.io</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:23.</p> -<h3>Recent Changes</h3> -<p>The …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 10 Jun at 16:19 &mdash; 17:31 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-06-10-16.19.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-06-10-16.19.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io">https://cloud-init.github.io</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:23.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:24.</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>In Progress Development</h3> -<p>The discussion about "In Progress Development" started at 16:30.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/cloud-init/+activereviews">https://code.launchpad.net/cloud-init/+activereviews</a> </li> -</ul> -<h3>Office Hours</h3> -<p>The discussion about "Office Hours" started at 16:45.</p> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 16:48.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://netplan.io/faq#how-to-go-back-to-ifupdown">https://netplan.io/faq#how-to-go-back-to-ifupdown</a> </li> -<li><strong>ACTION</strong>: follow up any bugs related to Azure/netplan uninstall in favor ifupdown to see if cloud-init has actionable feature work to ensure proper network renderer is used</li> -</ul> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (39)</li> -<li>rharper (39)</li> -<li>AnhVoMSFT (29)</li> -<li>cyphermox (12)</li> -<li>robjo (6)</li> -<li>meetingology (4)</li> -<li>ubot5 (3)</li> -<li>paride (1)</li> -<li>Odd_Bloke (1)</li> -</ul> -<h2>Full Log</h2> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:19 <code>&lt;meetingology&gt;</code> Meeting started Mon Jun 10 16:19:45 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:19 <code>&lt;meetingology&gt;</code> </p> -<p>16:19 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:19 <code>&lt;rharper&gt;</code> o/</p> -<p>16:20 <code>&lt;Odd_Bloke&gt;</code> o/</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> hi cloud-init folks. let's kick off the bi-weekly meeting again</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> our last meeting minutes are hosted on github</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io">https://cloud-init.github.io</a></p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> welcome all. Generally cloud-init upstream uses this meeting to provide a platform for status updates, raising questions or concerns and feature discussion. All are encouraged to participate as you see fit.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> our format is the following topics: Previous Actions, Recent Changes, In-progress Development, Office Hours</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> interjections and additional topics are welcome</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> Checking last meeting's minutes we were clear of old actions.</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> so we'll jump to the next topic this week.</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> the following commits landedd in cloud-init tip since the last status meeting</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> - Allow identification of OpenStack by Asset Tag</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> [Mark T. Voelker] (<a href="[https://bugs.launchpad.net/bugs/1669875](https://bugs.launchpad.net/bugs/1669875)">LP: #1669875</a>)</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> - Fix spelling error making 'an Ubuntu' consistent. [Brian Murray]</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> - run-container: centos: comment out the repo mirrorlist [Paride Legovini]</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> - netplan: update netplan key mappings for gratuitous-arp</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> [Ryan Harper] (<a href="[https://bugs.launchpad.net/bugs/1827238](https://bugs.launchpad.net/bugs/1827238)">LP: #1827238</a>)</p> -<p>16:26 <code>&lt;ubot5&gt;</code> Launchpad bug 1669875 in OpenStack Compute (nova) "identify openstack vmware platform" [Wishlist,Confirmed]</p> -<p>16:26 <code>&lt;ubot5&gt;</code> Launchpad bug 1827238 in cloud-init "Machines fail to deploy because cloud-init needs to accept both netplan spellings for grat arp" [Medium,Fix committed]</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> I was poking around out trello board to see if we've moved other cloud-init related content into the done lane, but I think those commits about capture the recent work</p> -<p>16:30 <code>&lt;blackboxsw&gt;</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:30 <code>&lt;blackboxsw&gt;</code> #topic In Progress Development</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> our active reviews are located here (as mentioned in the topic)</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/cloud-init/+activereviews">https://code.launchpad.net/cloud-init/+activereviews</a></p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> Goneri: thanks for all the work on freebsd branches, there has been some good momentum there</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> there is ongoing work from Azure datasource that will likely land in the next week or two</p> -<p>16:33 <code>&lt;paride&gt;</code> ^^ "run-container: centos: comment out the repo mirrorlist", only actually relevent when using an http/https proxy, in all the other cases the mirrorlist works as usual</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> and some network-related changes landing shortly</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> paride: thank you paride for the extra note</p> -<p>16:33 <code>&lt;AnhVoMSFT&gt;</code> blackboxsw can you share more details on the work from Azure datasource ? Any bug that we can reference?</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> I was thinking <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/364012">https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/364012</a> AnhVoMSFT</p> -<p>16:35 <code>&lt;rharper&gt;</code> related to sorting out covering the all the network related scenarios so that we configure network in a way that ensures access to IMDS and internet in the face of additional static ips on the same subnet as the primary interface, multiple dhcp interfaces with default routes,</p> -<p>16:35 <code>&lt;AnhVoMSFT&gt;</code> I see - I think there potentially needs some bigger change there, as there was some issue around identifying the primary/secondary NIC. We got confirmation from our netwoking team that the first NIC returned is the primary</p> -<p>16:35 <code>&lt;rharper&gt;</code> AnhVoMSFT: good to know; that was our observation</p> -<p>16:36 <code>&lt;rharper&gt;</code> AnhVoMSFT: <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1815254">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1815254</a> , related as well; the plan being to put in place some source-based routing;</p> -<p>16:36 <code>&lt;ubot5&gt;</code> Launchpad bug 1815254 in cloud-init (Ubuntu) "Azure multiple ips prevent access to metadata service" [Undecided,Confirmed]</p> -<p>16:38 <code>&lt;AnhVoMSFT&gt;</code> thanks rharper - is that something that should be changed/fixed from cloudinit, or is this more platform related?</p> -<p>16:38 <code>&lt;rharper&gt;</code> that's a good question; generally it would be <em>great</em> if a platform were to include source-routes and metrics in the config they send</p> -<p>16:38 <code>&lt;AnhVoMSFT&gt;</code> if the latter I will file a workitem on our side to go do some research and get the right team to take a look at it</p> -<p>16:39 <code>&lt;rharper&gt;</code> currently no cloud does this, rather <em>some</em> indicate a <em>primary</em> via metadata, and then the OS scripts apply a metric to all non-primary routes to ensure that default routes go to the primary</p> -<p>16:39 <code>&lt;AnhVoMSFT&gt;</code> I see - so I guess we can do similarly on Azure since we know what the primary is (first nic returned in IMDS)</p> -<p>16:40 <code>&lt;rharper&gt;</code> AnhVoMSFT: so in the short term, I think cloud-init should (where possible with the OS network config) provide additional tuning (likely post-scripts in some cases) to tune the routing for what cloud-init knows is the primary route</p> -<p>16:40 <code>&lt;rharper&gt;</code> AnhVoMSFT: yes, I prefer a primary=True or whatever, but it's good enough to have the current behavior documented (in the code)</p> -<p>16:40 <code>&lt;AnhVoMSFT&gt;</code> thanks rharper</p> -<p>16:40 <code>&lt;rharper&gt;</code> so if it change/breaks, then we know</p> -<p>16:44 <code>&lt;rharper&gt;</code> I think that covers our in-progress items for the moment</p> -<p>16:45 <code>&lt;rharper&gt;</code> not sure if the bot will listen to me, but just in case</p> -<p>16:45 <code>&lt;robjo&gt;</code> Be mindful that in Azure the metadata service may lag behind by minutes w.r.t. secondary IPs on an interface</p> -<p>16:45 <code>&lt;rharper&gt;</code> #topic Office Hours</p> -<p>16:45 <code>&lt;rharper&gt;</code> robjo: in general, my awareness is that the instance has to be off line to change vnets and such; and booting back up has been enough time to see IMDS updated, do you see differently ?</p> -<p>16:46 <code>&lt;AnhVoMSFT&gt;</code> robjo that is good to know, I will check on that</p> -<p>16:46 <code>&lt;robjo&gt;</code> We've had various issues with cloud-netconfig due to the metadata server in Azure being slow and reverted to polling, which of course got us in trouble with API rate limits</p> -<p>16:46 <code>&lt;rharper&gt;</code> robjo: interesting</p> -<p>16:47 <code>&lt;rharper&gt;</code> We'll here in channel so if youve;; got merges or bugs that need an eye or just questions, fire away</p> -<p>16:47 <code>&lt;AnhVoMSFT&gt;</code> robjo feel free to file a bug on that and we will investigate - IMDS is our partner team so we'll get some answer quickly there</p> -<p>16:48 <code>&lt;AnhVoMSFT&gt;</code> rharper, a couple things I want to ask for Office Hours</p> -<p>16:48 <code>&lt;robjo&gt;</code> AnhVoMSFT: We have been working with Stephen Zarkos on the issues</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:48 <code>&lt;AnhVoMSFT&gt;</code> robjo I will ping Stephen and get more detail and see if we have any follow up items</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> sorry folks got pulled away for a bit thx rharper</p> -<p>16:48 <code>&lt;robjo&gt;</code> And double checked that the polling direction was OK form the Microsoft perspective before we implemented that</p> -<p>16:49 <code>&lt;AnhVoMSFT&gt;</code> I see, glad you're not blocked on it</p> -<p>16:50 <code>&lt;robjo&gt;</code> rharper: We always had bug reports that upon reboot not everything was always configured when secondary IP addresses were in play. But theoretically yes upon reboot everything should be there</p> -<p>16:50 <code>&lt;AnhVoMSFT&gt;</code> rharper we have a customer who booted up a VM based on 18.04, which uses netplan. Cloudinit wrote a netplan file to the image. He then installed ifupdown, then had some networking change which triggered a mac address change. Upon rebooting, cloudinit tries to use eni, but netplan file was still there, which caused his VM to mess up the network config</p> -<p>16:50 <code>&lt;robjo&gt;</code> putting cloud-netconfig into polling mode pretty mush addresses the issues we had reports about</p> -<p>16:51 <code>&lt;rharper&gt;</code> AnhVoMSFT: yes; that sounds very likely</p> -<p>16:51 <code>&lt;rharper&gt;</code> AnhVoMSFT: did they file a bug?</p> -<p>16:51 <code>&lt;rharper&gt;</code> cloud-init net "detects" which service is present</p> -<p>16:51 <code>&lt;AnhVoMSFT&gt;</code> I'm checking to see if this should be a bug, or that is expected behavior</p> -<p>16:51 <code>&lt;rharper&gt;</code> so if they did not uninstall netplan.io then cloud-init will likely prefer that over eni</p> -<p>16:52 <code>&lt;AnhVoMSFT&gt;</code> cloudinit actually prefers eni if ifupdown is installed, I think</p> -<p>16:52 <code>&lt;rharper&gt;</code> AnhVoMSFT: so the etc/netplan/*.yaml would only trigger things if netplan is still present; the systemd-generator will read yaml and write out networkd files</p> -<p>16:53 <code>&lt;AnhVoMSFT&gt;</code> right, I think the customer's mistake was to not uninstall netplan (or remove any netplan configuration file) after installing ifupdown</p> -<p>16:53 <code>&lt;rharper&gt;</code> AnhVoMSFT: right; I think we'll need to see the log and system state, but it sounds like an incomplete uninstall of netplan</p> -<p>16:53 <code>&lt;rharper&gt;</code> uninstall of netplan should be enough to make the cloud-init.yaml inert</p> -<p>16:54 <code>&lt;rharper&gt;</code> <a href="https://netplan.io/faq#how-to-go-back-to-ifupdown">https://netplan.io/faq#how-to-go-back-to-ifupdown</a></p> -<p>16:54 <code>&lt;rharper&gt;</code> AnhVoMSFT: it <em>should</em> have automatically uninstall netplan.io</p> -<p>16:54 <code>&lt;AnhVoMSFT&gt;</code> I'm not sure if there is much we can do from the cloudinit side - perhaps if choosing eni, disable the cloud-init netplan yaml</p> -<p>16:54 <code>&lt;rharper&gt;</code> AnhVoMSFT: well, we could check writable paths of the renderers</p> -<p>16:54 <code>&lt;AnhVoMSFT&gt;</code> rharper I don't think that is the behavior on 18.04 - installing ifupdown will not uninstall netplan</p> -<p>16:55 <code>&lt;rharper&gt;</code> AnhVoMSFT: you're right; =(</p> -<p>16:55 <code>&lt;rharper&gt;</code> that sort of feels like a bug in the packaging</p> -<p>16:55 <code>&lt;AnhVoMSFT&gt;</code> yes, I share the same sentiment</p> -<p>16:56 <code>&lt;AnhVoMSFT&gt;</code> I will go ahead and file a bug so even if we don't have a short term action we can still capture the discussion</p> -<p>16:57 <code>&lt;rharper&gt;</code> AnhVoMSFT: thanks, I'm pinging in #netplan and the bug will be great so we can figure out the right plan</p> -<p>16:59 <code>&lt;AnhVoMSFT&gt;</code> second question: We have an intern working in our team and as part of warming up in cloudinit he wrote some additional capabilities into cloud-init analyze, adding a "boot" module (in addition to show/blame/dump), which collects timestamps of phases happening during vm booting up, but before cloudinit started, such as kernel initialization, systemd initialization..</p> -<p>17:00 <code>&lt;AnhVoMSFT&gt;</code> this should work for all cloud (he tested in AWE/GCP). Currently only works for distros that uses systemd. He'll try to figure out how to get those counters for freebsd and others</p> -<p>17:00 <code>&lt;AnhVoMSFT&gt;</code> rharper since you were the original author of analyze, I'm trying to gauge the interest on this and we're open to suggestions/questions</p> -<p>17:01 <code>&lt;cyphermox&gt;</code> rharper: they can coexist and configure each their own interface, so it's not a conflict. It's no different than coexisting ifupdown and NetworkManager, or also NetworkManager and systemd-networkd</p> -<p>17:01 <code>&lt;rharper&gt;</code> AnhVoMSFT: that sounds excellent</p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> nice AnhVoMSFT on the commandline extensions!</p> -<p>17:01 <code>&lt;rharper&gt;</code> AnhVoMSFT: happy to review branch or Work-in-Progress when it's available</p> -<p>17:02 <code>&lt;AnhVoMSFT&gt;</code> thanks rharper blackboxsw we will have that in a branch very soon.</p> -<p>17:03 <code>&lt;AnhVoMSFT&gt;</code> cyphermox if that is the case then either the customer or cloudinit needs to make sure the system does not have conflicting configuration for netplan/eni.</p> -<p>17:03 <code>&lt;rharper&gt;</code> cyphermox: ok; would you be open to some sort of warning about having config in both or something? I dunno; it's just not a great experience to add the new package, configure it, reboot and not have networking since the same interface was configured (differenlty) in both packages</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> yeah, I'm quite intterested in any additional cli functionality that cloud-init more versatile as a system debug tool</p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> <em>makes cloud-init more versatile</em></p> -<p>17:04 <code>&lt;cyphermox&gt;</code> rharper: I'm not opposed to a warning, but that's not necessarily better UX.</p> -<p>17:05 <code>&lt;cyphermox&gt;</code> debconf prompts are quite annoying to have at upgrade, and just writing it out people are likely to miss it altogether</p> -<p>17:05 <code>&lt;cyphermox&gt;</code> (so you wouldn't really gain much)</p> -<p>17:05 <code>&lt;AnhVoMSFT&gt;</code> blackboxsw yep that was the goal - we want to be able to deploy 1000 VMs, then use cloud-init analyze output to analyze the 50th/99th percentile of where the timing was spent during system boot, and we need some more insights into phases before cloud-init started as well</p> -<p>17:05 <code>&lt;rharper&gt;</code> cyphermox: agreed; having a pointer to suggest cleaning/checking/confirming configs if /etc/netplan/ is non-empty and netplan.io is installed</p> -<p>17:06 <code>&lt;cyphermox&gt;</code> rharper: one option is to parse enough of /etc/network/ to catch mentions of the interface, but that's not necessarily super solid (though it's the best option), because people can rename interfaces in netplan and match by mac</p> -<p>17:06 <code>&lt;rharper&gt;</code> might be helpful; though I agree that they may still ignore that; and cloud-init could do some more work to see if an image has multiple renderers available and ensure it didn't leave config for a previous boot around</p> -<p>17:07 <code>&lt;rharper&gt;</code> cyphermox: yeah; cloud-init knows more about the config and both formats; we're likely in a better spot to see "you've configured this interface twice"</p> -<p>17:08 <code>&lt;cyphermox&gt;</code> rharper: so in short, I'm not opposed to improving the UX, but I'm not wowed by any solution right now (even mine)</p> -<p>17:09 <code>&lt;rharper&gt;</code> cyphermox: that's fair; thanks</p> -<p>17:09 <code>&lt;AnhVoMSFT&gt;</code> i think a fix in cloudinit might make most stakeholders happy here. It knows which configuration file it wrote, so it can definitely look for conflicting configurations</p> -<p>17:09 <code>&lt;rharper&gt;</code> cyphermox: AnhVoMSFT is going to file the customer bug with details and we can discuss what (if any) improvements are to be made; I suspect cloud-init can help most here</p> -<p>17:09 <code>&lt;cyphermox&gt;</code> yes, I think so too</p> -<p>17:09 <code>&lt;rharper&gt;</code> cyphermox: thanks for the input</p> -<p>17:09 <code>&lt;AnhVoMSFT&gt;</code> it can't be responsible for everything the customer does though. If customer writes some my-own-netplan.yml, we can't help much</p> -<p>17:10 <code>&lt;cyphermox&gt;</code> rharper: but hey, if someone was to write a check when running netplan apply that there exists config in /etc/network, I wouldn't have much issues merging it</p> -<p>17:10 <code>&lt;rharper&gt;</code> AnhVoMSFT: right, we have several "maybe_delete_if" where we verify expected output before we remove things</p> -<p>17:10 <code>&lt;cyphermox&gt;</code> I just know I won't have time to look into this myself in the near future</p> -<p>17:10 <code>&lt;rharper&gt;</code> cyphermox: ack</p> -<p>17:11 <code>&lt;cyphermox&gt;</code> I think what will help most is aggressively deprecating and removing ifupdown</p> -<p>17:13 <code>&lt;cyphermox&gt;</code> that said, the best we can realistically do for the time being is to demote it to universe</p> -<p>17:13 <code>&lt;cyphermox&gt;</code> (and that's not going to change anything for UX)</p> -<p>17:15 <code>&lt;AnhVoMSFT&gt;</code> we had another instance of someone installing ifupdown2, which had the effect of removing cloud-init on debian/ubuntu 16.04</p> -<p>17:16 <code>&lt;AnhVoMSFT&gt;</code> and totally hosed his system, but that's a different issue altogether</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> s</p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> thanks for the good discussion folks, I guess we'll just add an action item to followup on a netplan bug for next time to see where we are at</p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> #action follow up any bugs related to Azure/netplan uninstall in favor ifupdown to see if cloud-init has actionable feature work to ensure proper network renderer is used</p> -<p>17:31 * meetingology follow up any bugs related to Azure/netplan uninstall in favor ifupdown to see if cloud-init has actionable feature work to ensure proper network renderer is used</p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> ok, I'll post minutes on this. thank you again rharper for driving</p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> and for the participation robjo cyphermox and AnhVoMSFT</p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2019-05-28T15:23:00+00:002019-05-28T15:23:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2019-05-28:/status-2019-05-28.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 28 May at 15:23 &mdash; 16:19 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-05-28-15.23.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-05-28-15.23.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 15:27.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-05-13.html#status-2019-05-13">https://cloud-init.github.io/status-2019-05-13.html#status-2019-05-13 …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 28 May at 15:23 &mdash; 16:19 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-05-28-15.23.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-05-28-15.23.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 15:27.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-05-13.html#status-2019-05-13">https://cloud-init.github.io/status-2019-05-13.html#status-2019-05-13</a> </li> -</ul> -<h3>Recent changes</h3> -<p>The discussion about "Recent changes" started at 15:30.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/t/sru-of-cloud-init-19-1-released/11028/2">https://discourse.ubuntu.com/t/sru-of-cloud-init-19-1-released/11028/2</a> </li> -<li><strong>LINK</strong>: <a href="https://lists.launchpad.net/cloud-init/msg00211.html">https://lists.launchpad.net/cloud-init/msg00211.html</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 15: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> -</ul> -<h3>Office hours (next ~30 mins)</h3> -<p>The discussion about "Office hours (next ~30 mins)" started at 15:44.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/cloud-init/+activereviews">https://code.launchpad.net/cloud-init/+activereviews</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082">https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082</a> </li> -<li><strong>ACTION</strong>: blackboxsw discuss with the team about landing the branch <a href="https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082">https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082</a></li> -</ul> -<h2>Vote results</h2> -<h2>Action items, by person</h2> -<ul> -<li>blackboxsw</li> -<li>blackboxsw discuss with the team about landing the branch <a href="https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082">https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082</a></li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (44)</li> -<li>meetingology (4)</li> -<li>akik (2)</li> -<li>ubot5 (2)</li> -</ul> -<h2>Full Log</h2> -<p>15:23 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>15:23 <code>&lt;meetingology&gt;</code> Meeting started Tue May 28 15:23:50 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>15:23 <code>&lt;meetingology&gt;</code> </p> -<p>15:23 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>15:23 <code>&lt;blackboxsw&gt;</code> there we go</p> -<p>15:24 <code>&lt;blackboxsw&gt;</code> Hey folks, time for another bi-weekly cloud-init status. Welcome all!</p> -<p>15:25 <code>&lt;blackboxsw&gt;</code> Generally cloud-init upstream uses this meeting to provide a platform for status updates, raising questions or concerns and feature discussion. All are encouraged to participate as you see fit.</p> -<p>15:25 <code>&lt;blackboxsw&gt;</code> Generally the topics we would like to cover are the following: Previous Actions, Recent Changes, In-progress Development, Office Hours</p> -<p>15:26 <code>&lt;blackboxsw&gt;</code> without further ado let's jump into it.</p> -<p>15:27 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>15:27 <code>&lt;blackboxsw&gt;</code> From our previous meeting minutes we had a couple of action items that I think are resolved</p> -<p>15:27 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2019-05-13.html#status-2019-05-13">https://cloud-init.github.io/status-2019-05-13.html#status-2019-05-13</a></p> -<p>15:28 * blackboxsw Odd_Bloke confirm correct status of <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</a></p> -<p>15:28 <code>&lt;ubot5&gt;</code> Launchpad bug 1801364 in cloud-init "persisting OpenStack metadata fails" [Undecided,Confirmed]</p> -<p>15:28 <code>&lt;blackboxsw&gt;</code> Dan confirmed that this is the proper bug status and still needs a fix</p> -<p>15:28 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: we had an action related to you "followup on recommended approach for getting kernel/userspace timestamp with or without python-dbus package dependency"</p> -<p>15:29 <code>&lt;blackboxsw&gt;</code> I know rharper had a comment or two in channel about this approach. Hopefully AnhVoMSFT you have everything you need there</p> -<p>15:29 <code>&lt;blackboxsw&gt;</code> if not, you can feel free to ping us for more discussion on that feature</p> -<p>15:30 <code>&lt;blackboxsw&gt;</code> #topic Recent changes</p> -<p>15:31 <code>&lt;blackboxsw&gt;</code> Big news since last bi-weekly status meeting is that we have completed and published 19.1.1 in an SRU into Ubuntu Xenial, Bionic, Cosmic and Disco as of yesterday.</p> -<p>15:31 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: wrote up some content and email around this for more context. Thanks Odd_Bloke</p> -<p>15:32 <code>&lt;blackboxsw&gt;</code> #link <a href="https://discourse.ubuntu.com/t/sru-of-cloud-init-19-1-released/11028/2">https://discourse.ubuntu.com/t/sru-of-cloud-init-19-1-released/11028/2</a></p> -<p>15:33 <code>&lt;blackboxsw&gt;</code> #link <a href="https://lists.launchpad.net/cloud-init/msg00211.html">https://lists.launchpad.net/cloud-init/msg00211.html</a></p> -<p>15:38 <code>&lt;blackboxsw&gt;</code> beyond that we have the following upstream commits landed</p> -<p>15:39 <code>&lt;blackboxsw&gt;</code> d9b1e5de91..HEAD | log2dch</p> -<p>15:39 <code>&lt;blackboxsw&gt;</code> - freebsd: NoCloud data source support [Gonéri Le Bouder] (LP: #1645824)</p> -<p>15:39 <code>&lt;blackboxsw&gt;</code> - Azure: Return static fallback address as if failed to find endpoint</p> -<p>15:39 <code>&lt;blackboxsw&gt;</code> [Jason Zions (MSFT)]</p> -<p>15:39 <code>&lt;ubot5&gt;</code> Launchpad bug 1645824 in cloud-init "NoCloud source doesn't work on FreeBSD" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1645824">https://launchpad.net/bugs/1645824</a></p> -<p>15:40 <code>&lt;blackboxsw&gt;</code> Thanks again Jason and Gonéri for the commits there. We have a few branches in the wings under review for freebsd and azure that I expect will be landing this week</p> -<p>15:41 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>15:42 <code>&lt;blackboxsw&gt;</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>15:43 <code>&lt;blackboxsw&gt;</code> Our upcoming work is set and scheduled on this trello board above. As we grab new significant tasks and dev work for cloud-init we will pull those cards into the doing lane</p> -<p>15:44 <code>&lt;blackboxsw&gt;</code> #topic Office hours (next ~30 mins)</p> -<p>15:45 <code>&lt;blackboxsw&gt;</code> This topic is an opportunity for anyone to bring their bugs, features, questions or branches to get some extra eyes or discussion around current development.</p> -<p>15:47 <code>&lt;blackboxsw&gt;</code> It is also a slot of time where upstream developers will be spending some time reviewing active branches to unblock community members and help increase velocity of our review queue.</p> -<p>15:47 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/cloud-init/+activereviews">https://code.launchpad.net/cloud-init/+activereviews</a></p> -<p>15:48 * blackboxsw does as review pass on <a href="https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/367315.">https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/367315.</a> I'm grabbing an active review slot for this now</p> -<p>15:52 <code>&lt;akik&gt;</code> ls</p> -<p>15:52 <code>&lt;akik&gt;</code> sorry</p> -<p>16:03 <code>&lt;blackboxsw&gt;</code> yeah this looks good Goneri <a href="https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/367315...">https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/367315...</a> approved</p> -<p>16:03 <code>&lt;blackboxsw&gt;</code> will merge in ~15</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> smoser: so sorry on the review delay here for the doc change you took over. <a href="https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/343546">https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/343546</a></p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> just approved with a nit if you are around to push that. if not, I'll get that doc branch merged in tomorrow</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> I think that about wraps this status meeting this week. I think we should take an action to talk about we want to do with this old branch.</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082">https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082</a></p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> #action blackboxsw discuss with the team about landing the branch <a href="https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082">https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082</a></p> -<p>16:16 * meetingology blackboxsw discuss with the team about landing the branch <a href="https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082">https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082</a></p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> We'll hold the next cloud-init status meeting on Monday 3/10</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> and I'll post the status minutes up to <a href="https://cloud-init.github.io">https://cloud-init.github.io</a> momentarily</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> Thanks again. have a good one guys and gals.</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2019-05-13T16:25:00+00:002019-05-13T16:25:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2019-05-13:/status-2019-05-13.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 13 May at 16:25 &mdash; 17:32 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-05-13-16.25.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-05-13-16.25.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:31.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-01-28.html#status-2019-01-28">https://cloud-init.github.io/status-2019-01-28.html#status-2019-01-28 …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 13 May at 16:25 &mdash; 17:32 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-05-13-16.25.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-05-13-16.25.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:31.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-01-28.html#status-2019-01-28">https://cloud-init.github.io/status-2019-01-28.html#status-2019-01-28</a> </li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</a> </li> -<li><strong>ACTION</strong>: Odd_Bloke confirm correct status of <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</a></li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:35.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://launchpad.net/cloud-init/+milestone/19.1">https://launchpad.net/cloud-init/+milestone/19.1</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:46.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://wiki.ubuntu.com/CloudinitUpdates">https://wiki.ubuntu.com/CloudinitUpdates</a> </li> -<li><strong>LINK</strong>: <a href="https://trello.com/c/oxv61bPl/1099-sru-191-xenial-bionic-cosmic-and-disco">https://trello.com/c/oxv61bPl/1099-sru-191-xenial-bionic-cosmic-and-disco</a> </li> -<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> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367301">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367301</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367302">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367302</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367297">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367297</a> </li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1828637">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1828637</a> </li> -<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>Office hours (next ~30 mins)</h3> -<p>The discussion about "Office hours (next ~30 mins)" started at 17:02.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloudinit.readthedocs.io/en/latest/topics/tests.html#">https://cloudinit.readthedocs.io/en/latest/topics/tests.html#</a> </li> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io">https://cloud-init.github.io</a> </li> -<li><strong>ACTION</strong>: Odd_Bloke/rharper/AnhVoMSFT followup on recommended approach for getting kernel/userspace timestamp with or without python-dbus package dependency</li> -</ul> -<h2>Vote results</h2> -<h2>Action items, by person</h2> -<ul> -<li>AnhVoMSFT</li> -<li>Odd_Bloke/rharper/AnhVoMSFT followup on recommended approach for getting kernel/userspace timestamp with or without python-dbus package dependency</li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (163)</li> -<li>AnhVoMSFT (20)</li> -<li>ubot5` (19)</li> -<li>meetingology (5)</li> -<li>powersj (3)</li> -</ul> -<h2>Full Log</h2> -<p>16:25 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:25 <code>&lt;meetingology&gt;</code> Meeting started Mon May 13 16:25:37 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:25 <code>&lt;meetingology&gt;</code> </p> -<p>16:25 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> hi folks, we are restarting the cloud-init community status meeting so we can have a community forum to discuss current cloud-init development and try to improve momentum in the cloud-init project efforts.</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> over the last couple of months we had taken a break from this meeting. But, I think it's shown us that there is demand and usefulness in continuing hosting these meetings. So, from here on, we expect to post the upcoming date of status meetings in this channel's room topic.</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> Again the goal of this meeting is to give people a chance to see what work is currently being performed on upstream cloud-init as well as a forum to discuss or raise concerns or get eyes on potential bugs or features.</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> Generally the topics we would like to cover are the following: (and interjections/suggestions are always welcome</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> topics: Previous Actions, Recent Changes, In-progress Development, Office Hours.</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> so, looking at our last status minutes from the last meeting, (on Jan 28.... :( ) we had one action carried over</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2019-01-28.html#status-2019-01-28">https://cloud-init.github.io/status-2019-01-28.html#status-2019-01-28</a></p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> review and land <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098</a></p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> that's done. as well as an openstack bug...</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</a></p> -<p>16:33 <code>&lt;ubot5</code>&gt;` Ubuntu bug 1801364 in cloud-init "persisting OpenStack metadata fails" [Undecided,Confirmed]</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: has landed this bug, I think it needs to be marked fix committed though</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: is out today at a meeting, but I'll mark that action so we can make sure that bug status is properly reported (if there are no other branches to land for it)</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> #action Odd_Bloke confirm correct status of <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</a></p> -<p>16:34 * meetingology Odd_Bloke confirm correct status of <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</a></p> -<p>16:34 <code>&lt;ubot5</code>&gt;` Ubuntu bug 1801364 in cloud-init "persisting OpenStack metadata fails" [Undecided,Confirmed]</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> That;s about it for actions from previous meeting.</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> Here we list current content that has landed in cloud-init since last meeting..... because it has been a really long time since last meeting, I'm going to redact this to the last month or so of content to avoid getting banned in this channel for spam</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - Azure: Return static fallback address as if failed to find endpoint</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> [Jason Zions (MSFT)]</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - release 19.1 (LP: #1828479)</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - freebsd: add chpasswd pkg in the image [Gonéri Le Bouder]</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - tests: add Eoan release [Paride Legovini]</p> -<p>16:37 <code>&lt;ubot5</code>&gt;` Launchpad bug 1828479 in cloud-init "Release 19.1" [Undecided,Fix released] <a href="https://launchpad.net/bugs/1828479">https://launchpad.net/bugs/1828479</a></p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> hah, I don't think that worked</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> ok breaking that content up</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - Azure: Return static fallback address as if failed to find endpoint</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> [Jason Zions (MSFT)]</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - release 19.1 (LP: #1828479)</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - freebsd: add chpasswd pkg in the image [Gonéri Le Bouder]</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - tests: add Eoan release [Paride Legovini]</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - cc_mounts: check if mount -a on no-change fstab path</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> [Jason Zions (MSFT)] (LP: #1825596)</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - replace remaining occurrences of LOG.warn [Daniel Watkins]</p> -<p>16:37 <code>&lt;ubot5</code>&gt;` Launchpad bug 1825596 in cloud-init "Azure reboot with unformatted ephemeral drive won't mount reformatted volume" [High,Fix released] <a href="https://launchpad.net/bugs/1825596">https://launchpad.net/bugs/1825596</a></p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - DataSourceAzure: Adjust timeout for polling IMDS [Anh Vo]</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - Azure: Changes to the Hyper-V KVP Reporter [Anh Vo]</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - git tests: no longer show warning about safe yaml.</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - tools/read-version: handle errors [Chad Miller]</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - net/sysconfig: only indicate available on known sysconfig distros</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> (LP: #1819994)</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - packages: update rpm specs for new bash completion path</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> [Daniel Watkins] (LP: #1825444)</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - test_azure: mock util.SeLinuxGuard where needed</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> [Jason Zions (MSFT)] (LP: #1825253)</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - setup.py: install bash completion script in new location [Daniel Watkins]</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - mount_cb: do not pass sync and rw options to mount</p> -<p>16:37 <code>&lt;ubot5</code>&gt;` Launchpad bug 1819994 in Provider for Plainbox - Canonical Certification Server "cloud-init selects sysconfig netconfig renderer if network-manager is installed on Ubuntu" [Critical,Confirmed] <a href="https://launchpad.net/bugs/1819994">https://launchpad.net/bugs/1819994</a></p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> [Gonéri Le Bouder] (LP: #1645824)</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - cc_apt_configure: fix typo in apt documentation [Dominic Schlegel]</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - Revert "DataSource: move update_events from a class to an instance..."</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> [Daniel Watkins]</p> -<p>16:37 <code>&lt;ubot5</code>&gt;` Launchpad bug 1825444 in cloud-init (Ubuntu) ""make rpm" fails on CentOS after commit 947d3c208" [Undecided,Fix released] <a href="https://launchpad.net/bugs/1825444">https://launchpad.net/bugs/1825444</a></p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - Change DataSourceNoCloud to ignore file system label's case.</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> [Risto Oikarinen]</p> -<p>16:38 <code>&lt;ubot5</code>&gt;` Launchpad bug 1825253 in cloud-init "Unit tests with filesystem-related mocks fail in SeLinuxGuard when run on RHEL or CentOS" [Undecided,Fix released] <a href="https://launchpad.net/bugs/1825253">https://launchpad.net/bugs/1825253</a></p> -<p>16:38 <code>&lt;ubot5</code>&gt;` Launchpad bug 1645824 in cloud-init "NoCloud source doesn't work on FreeBSD" [Medium,Fix released] <a href="https://launchpad.net/bugs/1645824">https://launchpad.net/bugs/1645824</a></p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - cmd:main.py: Fix missing 'modules-init' key in modes dict</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> [Antonio Romito] (LP: #1815109)</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - ubuntu_advantage: rewrite cloud-config module</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - Azure: Treat _unset network configuration as if it were absent</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> [Jason Zions (MSFT)] (LP: #1823084)</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - DatasourceAzure: add additional logging for azure datasource [Anh Vo]</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - cloud_tests: fix apt_pipelining test-cases</p> -<p>16:38 <code>&lt;ubot5</code>&gt;` Launchpad bug 1815109 in cloud-init "cloud-final.service: "cloud-init modules --mode final" exit with "KeyError: 'modules-init'" after upgrade to version 18.2" [Medium,Fix released] <a href="https://launchpad.net/bugs/1815109">https://launchpad.net/bugs/1815109</a></p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - Azure: Ensure platform random_seed is always serializable as JSON.</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> [Jason Zions (MSFT)]</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - net/sysconfig: write out SUSE-compatible IPv6 config [Robert Schweikert]</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - tox: Update testenv for openSUSE Leap to 15.0 [Thomas Bechtold]</p> -<p>16:38 <code>&lt;ubot5</code>&gt;` Launchpad bug 1823084 in cloud-init "DataSourceAzure doesn't rebuild network-config after reboot" [High,Fix released] <a href="https://launchpad.net/bugs/1823084">https://launchpad.net/bugs/1823084</a></p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - net: Fix ipv6 static routes when using eni renderer</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> [Raphael Glon] (LP: #1818669)</p> -<p>16:38 <code>&lt;ubot5</code>&gt;` Launchpad bug 1818669 in cloud-init "ipv6 static routes configured for eni are incorrect" [Undecided,Fix released] <a href="https://launchpad.net/bugs/1818669">https://launchpad.net/bugs/1818669</a></p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - Add ubuntu_drivers config module [Daniel Watkins]</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - doc: Refresh Azure walinuxagent docs [Daniel Watkins]</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - tox: bump pylint version to latest (2.3.1) [Daniel Watkins]</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - DataSource: move update_events from a class to an instance attribute</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> [Daniel Watkins] (LP: #1819913)</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - net/sysconfig: Handle default route setup for dhcp configured NICs</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> [Robert Schweikert] (LP: #1812117)</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - DataSourceEc2: update RELEASE_BLOCKER to be more accurate</p> -<p>16:38 <code>&lt;ubot5</code>&gt;` Launchpad bug 1819913 in cloud-init "cloud-init on xenial may generate network config on every boot" [Undecided,Fix released] <a href="https://launchpad.net/bugs/1819913">https://launchpad.net/bugs/1819913</a></p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> [Daniel Watkins]</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - cloud-init-per: POSIX sh does not support string subst, use sed</p> -<p>16:38 <code>&lt;ubot5</code>&gt;` Launchpad bug 1812117 in cloud-init "route files are not written on SUSE distros" [Undecided,Fix released] <a href="https://launchpad.net/bugs/1812117">https://launchpad.net/bugs/1812117</a></p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> (LP: #1819222)</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - Support locking user with usermod if passwd is not available.</p> -<p>16:38 <code>&lt;ubot5</code>&gt;` Launchpad bug 1819222 in cloud-init "cloud-init-per no longer works due to bashisms" [Undecided,Fix released] <a href="https://launchpad.net/bugs/1819222">https://launchpad.net/bugs/1819222</a></p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - Example for Microsoft Azure data disk added. [Anton Olifir]</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - clean: correctly determine the path for excluding seed directory</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> [Daniel Watkins] (LP: #1818571)</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - helpers/openstack: Treat unknown link types as physical</p> -<p>16:38 <code>&lt;ubot5</code>&gt;` Launchpad bug 1818571 in cloud-init "cloud-init clean removes seed directory even when --seed is not specified" [High,Fix released] <a href="https://launchpad.net/bugs/1818571">https://launchpad.net/bugs/1818571</a></p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> [Daniel Watkins] (LP: #1639263)</p> -<p>16:38 <code>&lt;ubot5</code>&gt;` Launchpad bug 1639263 in cloud-init " cloud-init Unknown network_data link type: macvtap" [Undecided,Fix released] <a href="https://launchpad.net/bugs/1639263">https://launchpad.net/bugs/1639263</a></p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - drop Python 2.6 support and our NIH version detection [Daniel Watkins]</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - tip-pylint: Fix assignment-from-return-none errors</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - net: append type:dhcp[46] only if dhcp[46] is True in v2 netconfig</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> [Kurt Stieger] (LP: #1818032)</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - cc_apt_pipelining: stop disabling pipelining by default</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> [Daniel Watkins] (LP: #1794982)</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - tests: fix some slow tests and some leaking state [Daniel Watkins]</p> -<p>16:38 <code>&lt;ubot5</code>&gt;` Launchpad bug 1818032 in cloud-init "sysconfig renders BOOTPROTO=dhcp even if dhcp=false in v2 network-config" [High,Fix released] <a href="https://launchpad.net/bugs/1818032">https://launchpad.net/bugs/1818032</a></p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - util: don't determine string_types ourselves [Daniel Watkins]</p> -<p>16:38 <code>&lt;ubot5</code>&gt;` Launchpad bug 1794982 in cloud-init "drop /etc/apt/apt.conf.d/90cloud-init-pipelining in 16.04+" [Medium,Fix released] <a href="https://launchpad.net/bugs/1794982">https://launchpad.net/bugs/1794982</a></p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> Azure and SuSE and FreeBSD foks have been quite a bit of work and we have a number of other community contributors to thank this round</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: jasonzio (MSFT) and robjo (SuSE) thanks again for your efforts</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> Also, as you can see, Canonical added someone to our ranks for cloud-init development. Odd_Bloke is a permanent addition to our team and landing a lot of solid content for cloud-init.</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> welcome Dan!</p> -<p>16:43 <code>&lt;AnhVoMSFT&gt;</code> thanks rharper Odd_Bloke powersj blackboxsw for all the reviewing and advice</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> From upstream side of the house, we have cut our first official upstream release of cloud-init. Version 19.1 sports 5 months of development, 24 contributors from 20 top-level domains. Details of that release are sent to our mailinglist and posted to the luanchpad milestone</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> #link <a href="https://launchpad.net/cloud-init/+milestone/19.1">https://launchpad.net/cloud-init/+milestone/19.1</a></p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> :) ! it's nice how involved your teams have been thanks again.</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> So, for the upstream release of 19.1: Canonical has just started our SRU (Stable Release Update) process where we validate the upstream release before pushing it back into earlier Ubuntu series</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> We follow this upstream release process for Ubuntu</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> #link <a href="https://wiki.ubuntu.com/CloudinitUpdates">https://wiki.ubuntu.com/CloudinitUpdates</a></p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> I've queue to release branches for review as of Friday 05/10. I have queued Ubuntu Disco and published to disco-proposed pocket already.</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> So if someone deploys disco on your favorite cloud or hardware, you can add a disco-proposed apt source to /etc/apt/sources.list and you sound be able to install and or test 19.1</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> I made the 19.1.1 SRU cut which included the commitish baa478546d8cac98a706010699d64f8c2f70b5bf which was the tip containing " Azure: Return static fallback address as if failed to find endpoint" as the last commit</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> so jasonzio's latest azure branch made it</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> expectation is that I'll get most of verification done over this week and we can hopefully (pending no SRU regressions discovered) publish to Xenial, Bionic, Cosmic and Disco the beginning of next week (05/20/2019)</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> I just added the following card to track this work, it'll move to DONE when published</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> #link <a href="https://trello.com/c/oxv61bPl/1099-sru-191-xenial-bionic-cosmic-and-disco">https://trello.com/c/oxv61bPl/1099-sru-191-xenial-bionic-cosmic-and-disco</a></p> -<p>16:51 <code>&lt;powersj&gt;</code> AnhVoMSFT, thank you for all your contributions</p> -<p>16:52 <code>&lt;AnhVoMSFT&gt;</code> is there a package available publicly for 19.1 that we can download and apply it to existing images and run through our perf. regression test?</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> also today, we'll post 19.1 to our copr el-testing repo at</p> -<p>16:52 <code>&lt;blackboxsw&gt;</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:52 <code>&lt;blackboxsw&gt;</code> for centos.</p> -<p>16:53 <code>&lt;powersj&gt;</code> AnhVoMSFT, daily PPA: <a href="https://launchpad.net/~cloud-init-dev/+archive/ubuntu/daily">https://launchpad.net/~cloud-init-dev/+archive/ubuntu/daily</a></p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: we have daily repos that</p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> thx powersj</p> -<p>16:53 * powersj disappears</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT, so that is built from tip of master (which currently contains exactly the same commit set as will be published to each series)</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: once the following branches are "merged" for each series, xenial-proposed, bionic-proposed, cosmic-proposed will also contain the final bits for each series</p> -<p>16:54 <code>&lt;AnhVoMSFT&gt;</code> thanks powersj blackboxsw</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367301">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367301</a></p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367302">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367302</a></p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367297">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367297</a></p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> so when we land those, it should be a matter of an hour or so until <code>&lt;series&gt;</code>-proposed is accessible to test those final packages</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: in the SRU process, we still will have to verify and test those bits before release. There is a tracking bug for the overall process here</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1828637">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1828637</a></p> -<p>16:56 <code>&lt;ubot5</code>&gt;` Ubuntu bug 1828637 in cloud-init (Ubuntu) "sru cloud-init (18.5-45 to 19.1.1) Xenial, Bionic, Cosmic, Disco" [Undecided,In progress]</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> ^ this but will go to fix released when we pass verification and publish the SRU</p> -<p>16:57 <code>&lt;blackboxsw&gt;</code> which will be promotion from xenial-proposed to xenial-updates for public availability on all images</p> -<p>16:57 <code>&lt;blackboxsw&gt;</code> again the estimate on this is probably next week for getting through testing</p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> the rest of the cloud-init team is meeting this week for feature planning for the next cycle. But generally we will be tracking our ongoing work @ our public trello board</p> -<p>16:59 <code>&lt;blackboxsw&gt;</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>17:00 <code>&lt;blackboxsw&gt;</code> If there are there any features or significant gaps that people have interest in that we could try to put on our radar feel free to drop us a line here in channel or on the mailinglist @ cloud-init@lists.launchpad.net</p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> I think that about wraps up current in-flight work</p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> #topic Office hours (next ~30 mins)</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> This section is allocated generally for folks to chat about any burning questions that we have. Bring your topics, bugs, feature requests, merge proposals or questions and we'll try getting some eyes or discussion on the</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> *them.</p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> Generally we should have a couple cloud-init devs hanging out in channel during this time to help build momentum or unblock folks. Today may be a bit light in attendance due to a remote work trip a number of people are attending.</p> -<p>17:04 <code>&lt;AnhVoMSFT&gt;</code> if our next work requires importing another module (python-dbus), are there any guidelines wrt to using additional python modules not currently part of cloudinit package?</p> -<p>17:06 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: generally adding new dependencies is something we try to avoid if possible due to impacting the minimal cloud images with additional dependencies. From ubuntu's perspective we tend to try to look at an ubuntu minimal image to see if the dependency is already there (and that makes things simple for the addition).</p> -<p>17:06 <code>&lt;blackboxsw&gt;</code> If new dependency is also something that can be optional instead of strict it makes adding that dependency easier.</p> -<p>17:06 <code>&lt;blackboxsw&gt;</code> For example: python-jsonschema is an optional package dependency</p> -<p>17:07 <code>&lt;blackboxsw&gt;</code> we bookend the imports in cloud-init with a try/except ImportError: pass and make sure that cloud-init still behaves if it is not there.</p> -<p>17:07 <code>&lt;AnhVoMSFT&gt;</code> i will have to look into how to make it optional - certainly we can go that way if that makes thing easier</p> -<p>17:07 <code>&lt;AnhVoMSFT&gt;</code> what we are looking at is how to get the kernel init timestamp and systemd init timestamp - both of these are available as KernelTimestamp and UserSpaceTimestamp that are available as part of the systemd's system dbus</p> -<p>17:07 <code>&lt;blackboxsw&gt;</code> This type of approach has been helpful in supporting Centos 6 where jsonschema wasn't available in stock images</p> -<p>17:08 <code>&lt;AnhVoMSFT&gt;</code> normally you can get those info from "systemctl show", but the issue is systemctl internally use systemd's format_timestamp, which trims the precision down to "seconds" level. (format_timestamp_us would give us what we need)</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: interesting. since it seems like the dependency is one one or two values and not the full content of python-dbus library/modules I wonder if it might be better to see if those values are available in /proc or /sys somewhere as it might be fairly simple to instrument our own. (and avoid the time cost of importing larger python modules)</p> -<p>17:11 <code>&lt;AnhVoMSFT&gt;</code> I guess if we really want to avoid another module, we can use os.stat to key off ctime of /proc and /proc/1 - however, the ctimes of /proc and /proc/1 are a bit earlier than the actual KernelTimestamp and UserSpaceTimestamp. They do have the advantage of being more widely available. Systemd and dbus might not exist on all distros</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> ... at least something to peek at to see if it is low hanging fruit that is easy to handle</p> -<p>17:12 <code>&lt;AnhVoMSFT&gt;</code> Right, I would appreciate if someone with more knowledge on Linux systems can provide some advices here</p> -<p>17:12 <code>&lt;AnhVoMSFT&gt;</code> the dependency is really on those values, and the dbus library seems a bit overkill for it</p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> rharper: Odd_Bloke may have some thoughts on that too. but that conversation may have to wait a bit due to time difference.</p> -<p>17:14 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: again, what call/values would you like to make/get from python-dbus just for clarity</p> -<p>17:15 <code>&lt;AnhVoMSFT&gt;</code> bus=dbus.SystemBus() systemd1=bus.get_object('org.freedesktop.systemd1','/org/freedesktop/systemd1') manager=dbus.Interface(systemd1, 'org.freedesktop.systemd1.Manager') props_iface=dbus.Interface(manager,'org.freedesktop.DBus.Properties') props_iface.Get('org.freedesktop.systemd1.Manager','KernelTimestamp')</p> -<p>17:15 <code>&lt;AnhVoMSFT&gt;</code> oops - multiline didn't seem to go so well</p> -<p>17:15 <code>&lt;blackboxsw&gt;</code> it's all good thx</p> -<p>17:16 <code>&lt;blackboxsw&gt;</code> alternately, I support we could shell out via util.subp to make a cli call to handle that to avoid a python package dependency, but again it'd probably be better/faster to avoid that</p> -<p>17:17 <code>&lt;AnhVoMSFT&gt;</code> right, we're trying to avoid adding more util.subp call (in fact we have a workitem to reduce the numbers of the existing util.subp call the Azure DS makes)</p> -<p>17:18 <code>&lt;AnhVoMSFT&gt;</code> Like mentioned previously, we're looking at the /proc and /proc/1 ctime, they're cheap using the os.stat module and exist in all distros.</p> -<p>17:19 <code>&lt;blackboxsw&gt;</code> oops typo "alternatively , I support" /// I suppose</p> -<p>17:19 <code>&lt;blackboxsw&gt;</code> yeah that seems like the most non-contentious approach (processing /proc/1 ctime)</p> -<p>17:20 <code>&lt;blackboxsw&gt;</code> uncontentious rather</p> -<p>17:22 <code>&lt;AnhVoMSFT&gt;</code> another thing we're looking at is cloud-init cloudtests so that we can have some azure cloud test running as part of cloud-init check-in gate</p> -<p>17:22 <code>&lt;blackboxsw&gt;</code> excellent!</p> -<p>17:23 <code>&lt;AnhVoMSFT&gt;</code> if you guys have any pointers/tips on what it takes to enable cloud-tests please let us know</p> -<p>17:23 <code>&lt;AnhVoMSFT&gt;</code> one of our team members will be looking at it</p> -<p>17:24 <code>&lt;blackboxsw&gt;</code> any blockers that you are aware of to date? Generally the biggest lift is getting the platform support added to the cloud-tests</p> -<p>17:25 <code>&lt;blackboxsw&gt;</code> I know powersj added more CI docs related to this a few months ago at</p> -<p>17:25 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloudinit.readthedocs.io/en/latest/topics/tests.html#">https://cloudinit.readthedocs.io/en/latest/topics/tests.html#</a></p> -<p>17:25 <code>&lt;blackboxsw&gt;</code> I'll try to see if there was additional documentation tossed around</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> the benefit if Azure platform is added to cloud-init tip is that'd we would likely add some of that testing to our SRU verification process each release we are doing. I'm excited about that</p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> right now, it's manual for Azure testing... per something like this <a href="https://github.com/cloud-init/ubuntu-sru/blob/master/manual/azure-sru-18.5.21.txt">https://github.com/cloud-init/ubuntu-sru/blob/master/manual/azure-sru-18.5.21.txt</a></p> -<p>17:27 <code>&lt;AnhVoMSFT&gt;</code> I'm not aware of any blockers, we just barely started looking at it</p> -<p>17:27 <code>&lt;AnhVoMSFT&gt;</code> these links are very helpful, I'll pass them along</p> -<p>17:28 <code>&lt;blackboxsw&gt;</code> the above script is tedious to write up, and only is really testing upgrade path and any <em>new</em> azure-specific bugs/features that are fixed in the current SRU, since most of the other integration testing covers general case</p> -<p>17:28 <code>&lt;blackboxsw&gt;</code> thanks AnhVoMSFT that's good to hear</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> are there any other topics folks have for today's meeting? Otherwise we can adjourn until next meeting</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> next meeting will be May 27th, same time</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> and I'll post status notes for the meeting to our github pages</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io">https://cloud-init.github.io</a></p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> before I forget. let's get an action to followup on kernel/userspace timestamp discussion</p> -<p>17:31 <code>&lt;AnhVoMSFT&gt;</code> thanks blackboxsw</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> #action Odd_Bloke/rharper/AnhVoMSFT followup on recommended approach for getting kernel/userspace timestamp with or without python-dbus package dependency</p> -<p>17:32 * meetingology Odd_Bloke/rharper/AnhVoMSFT followup on recommended approach for getting kernel/userspace timestamp with or without python-dbus package dependency</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> thank you AnhVoMSFT</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> see folks next time, or anytime in channel</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2019-01-28T16:26:00+00:002019-01-28T16:26:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2019-01-28:/status-2019-01-28.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 28 Jan at 16:26 &mdash; 17:31 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-01-28-16.26.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-01-28-16.26.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:27.</p> -<ul> -<li><strong>ACTION</strong>: carry over blackboxsw close and land Openstack …</li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 28 Jan at 16:26 &mdash; 17:31 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-01-28-16.26.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-01-28-16.26.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:27.</p> -<ul> -<li><strong>ACTION</strong>: carry over blackboxsw close and land Openstack metadata handling bug <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</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:47.</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>Office Hours (next ~30 minutes)</h3> -<p>The discussion about "Office Hours (next ~30 minutes)" started at 16:51.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/357710">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/357710</a> merged</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>Action items, by person</h2> -<ul> -<li>blackboxsw</li> -<li>carry over blackboxsw close and land Openstack metadata handling bug <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</a></li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (60)</li> -<li>robjo (6)</li> -<li>ubot5 (6)</li> -<li>meetingology (4)</li> -</ul> -<h2>Full Log</h2> -<p>16:26 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:26 <code>&lt;meetingology&gt;</code> Meeting started Mon Jan 28 16:26:28 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:26 <code>&lt;meetingology&gt;</code> </p> -<p>16:26 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> hi cloud-init folks, it's that happy time again to chat about cloud-init upstream.</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> Generally the topics we cover in this status meeting are: Previous Actions, Recent Changes, In-progress Development, and Office hours</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> previously we had an action to review <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098.">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098.</a> I think rharper and robjo have a couple of back and forths on this branch. looks like we'll be able to land this</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> and oh noes, we need to followup and resolve the following MD bug on OpenStack <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</a></p> -<p>16:32 <code>&lt;ubot5&gt;</code> Ubuntu bug 1801364 in cloud-init "persisting OpenStack metadata fails" [Undecided,Confirmed]</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> #action carry over blackboxsw close and land Openstack metadata handling bug <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</a></p> -<p>16:32 * meetingology carry over blackboxsw close and land Openstack metadata handling bug <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</a></p> -<p>16:32 <code>&lt;robjo&gt;</code> Well that one was just about an additional empty line which I removed in October</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> ok I'll spend the 2nd half of this meeting going through this again and landing it if no other concerns. #toostale seeing <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098</a></p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> it doesn't look on review that there is anything concerning there.</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> ok I think that we it for actions last time.</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:36 <code>&lt;robjo&gt;</code> blackboxsw: There's also <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/357710">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/357710</a></p> -<p>16:36 <code>&lt;robjo&gt;</code> which appears to be complaining about he commit message</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> robjo: oops autolander rejection, will fix the LP commit message now and make approved (for merging)</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> Server Team CI bot (server-team-bot) wrote on 2019-01-07: #</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> Commit message lints:</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - Expected empty line on line 2 of the commit message</p> -<p>16:37 <code>&lt;robjo&gt;</code> Can there not be a template in LP for the commit message?</p> -<p>16:38 <code>&lt;robjo&gt;</code> I can never remember the formatting intricacies and thus depend on one of you guys to set this</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> robjo: does the 'commit message' on the merge proposal look good to you now <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/357710">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/357710</a></p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> at the top</p> -<p>16:39 <code>&lt;robjo&gt;</code> LGTM, thanks</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> I've clicked approve and it should autoland within ~15 mins</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> great</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> so recent commits to upstream cloud-init</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> - flake8: use ==/!= to compare str, bytes, and int literals</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> [Paride Legovini]</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> - opennebula: exclude EPOCHREALTIME as known bash env variable with a</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> delta [Chad Smith] (<a href="[https://bugs.launchpad.net/bugs/1813383](https://bugs.launchpad.net/bugs/1813383)">LP: #1813383</a>)</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> - tox: fix disco httpretty dependencies for py37</p> -<p>16:41 <code>&lt;ubot5&gt;</code> Ubuntu bug 1813383 in cloud-init "opennebula: fail to sbuild, bash environment var failure EPOCHREALTIME" [Undecided,Fix committed]</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> ha, ircflood boot</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> not sure how far I got in that list of commits</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> - lxd: install zfs-linux instead of zfs meta package</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> 09:41 [Johnson Shi] (<a href="[https://bugs.launchpad.net/bugs/1799779](https://bugs.launchpad.net/bugs/1799779)">LP: #1799779</a>)</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> 09:41 - net/sysconfig: do not write a resolv.conf file with only the header.</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> 09:41 [Robert Schweikert]</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> 09:41 - net: Make sysconfig renderer compatible with Network Manager.</p> -<p>16:42 <code>&lt;ubot5&gt;</code> Ubuntu bug 1799779 in cloud-init (Ubuntu Disco) "LXD module installs the wrong ZFS package if it's missing" [Medium,Confirmed]</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> 09:41 [Eduardo Otubo]</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> - cc_set_passwords: Fix regex when parsing hashed passwords</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> 09:41 [Marlin Cremers] (<a href="[https://bugs.launchpad.net/bugs/1811446](https://bugs.launchpad.net/bugs/1811446)">LP: #1811446</a>)</p> -<p>16:42 <code>&lt;ubot5&gt;</code> Ubuntu bug 1811446 in cloud-init (Ubuntu) "chpasswd: is mangling certain password hashes" [Undecided,In progress]</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> 09:41 - net: Wait for dhclient to daemonize before reading lease file</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> 09:41 [Jason Zions] (<a href="[https://bugs.launchpad.net/bugs/1794399](https://bugs.launchpad.net/bugs/1794399)">LP: #1794399</a>)</p> -<p>16:42 <code>&lt;ubot5&gt;</code> Ubuntu bug 1794399 in cloud-init "cloud-init dhcp_discovery() crashes on preprovisioned RHEL 7.6 VM in Azure" [Undecided,Fix committed]</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> 09:41 - [Azure] Increase retries when talking to Wireserver during metadata walk</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> 09:41 [Jason Zions]</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> 09:41 - Add documentation on adding a datasource.</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> Thanks folks for all the contributions to cloud-init over the last couple of weeks.</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> Additionally, we just published tip of cloud-init to Ubuntu disco (19.04) development release</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> and we have queued that release as well (cloud-init 18.5.17) for SRU (stable release update) into Xenial, Bionic and Cosmic as of Saturday.</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> the SRU process bug can be watched to see when 18.5.17 publishes to 16.04 18.04 and 18.10. (xenial, bionic, cosmic) <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1813346">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1813346</a></p> -<p>16:44 <code>&lt;ubot5&gt;</code> Ubuntu bug 1813346 in cloud-init (Ubuntu) "sru cloud-init (18.4.0 update to 18.5-17-gd1a2fe73) Xenial, Bionic, Cosmic" [Undecided,New]</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> Also we welcome our new QA team member paride to Canonical, he's been working on re-enabling our copr build repos and generally improving the quality of our continuous integration for cloud-init (and other Canonical projects)</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> #topic In-Progress Development</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> we tracking our ongoing cloud-init upstream work (and backlog) on our Trello board</p> -<p>16:47 <code>&lt;blackboxsw&gt;</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:49 <code>&lt;blackboxsw&gt;</code> the next couple of weeks will likely result in Ubuntu SRU verificantion for that release into xenial, bionic and cosmic. robjo's been working on a few OpenSUSE/sysconfig network handling branches that will likely land. and we'll have a couple of EC2 branches that need to address EC2-Classic network re-configuration across reboots</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> and, as mentioned our upstream copr repo builds will likely be fixed for centos/fedora consumers</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 minutes)</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> So, upsteram devs will have eyes on this channel for any further discussion, bugs or questions about cloud-init. Please use this venue as you see fit to raise awareness of stale branches, bugs etc so we can queue them up for review.</p> -<p>16:53 * blackboxsw is going to look over <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098</a> to see if we can close out on that today</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/357710">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/357710</a> merged</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> and just approved <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098</a></p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> thanks robjo</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> I think that about wraps it up for today. thanks again for checking in folks.</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> As always minutes will be posted to cloud-init's github page @</p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io">https://cloud-init.github.io</a></p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2019-01-07T16:36:00+00:002019-01-07T16:36:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2019-01-07:/status-2019-01-07.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 07 Jan at 16:36 &mdash; 18:02 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-01-07-16.36.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-01-07-16.36.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:38.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/360905">https://code …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 07 Jan at 16:36 &mdash; 18:02 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-01-07-16.36.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-01-07-16.36.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:38.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/360905">https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/360905</a> </li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:42.</p> -<h3>In-Progress Development</h3> -<p>The discussion about "In-Progress Development" started at 16:46.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098</a> is pending since October :( :(</li> -<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>ACTION</strong>: Review robjo's branch today/tomorrow</li> -<li><strong>ACTION</strong>: Review robjo's branch today/tomorrow <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098</a></li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098</a> </li> -<li><strong>ACTION</strong>: review robjo's New bugs and get feedback <a href="https://bit.ly/2C4gEHJ">https://bit.ly/2C4gEHJ</a></li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</a> </li> -<li><strong>LINK</strong>: <a href="https://trello.com/c/bEGsPvTm/1028-updated-cloud-init-ci-review-bot-to-place-a-branch-back-into-needs-review-after-it-receives-a-commit">https://trello.com/c/bEGsPvTm/1028-updated-cloud-init-ci-review-bot-to-place-a-branch-back-into-needs-review-after-it-receives-a-commit</a> </li> -<li><strong>ACTION</strong>: blackboxsw resolve and land fix for <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</a> this week</li> -</ul> -<h3>Office Hours (next ~30 minutes)</h3> -<p>The discussion about "Office Hours (next ~30 minutes)" started at 17:29.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://build.opensuse.org/package/show/Cloud:Tools:Next/cloud-init">https://build.opensuse.org/package/show/Cloud:Tools:Next/cloud-init</a> </li> -</ul> -<h2>Vote results</h2> -<h2>Action items, by person</h2> -<ul> -<li>blackboxsw</li> -<li>blackboxsw resolve and land fix for <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</a> this week</li> -<li>robjo</li> -<li>Review robjo's branch today/tomorrow</li> -<li>Review robjo's branch today/tomorrow <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098</a></li> -<li>review robjo's New bugs and get feedback <a href="https://bit.ly/2C4gEHJ">https://bit.ly/2C4gEHJ</a></li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (62)</li> -<li>robjo (16)</li> -<li>meetingology (7)</li> -<li>ubot5 (6)</li> -<li>rharper (1)</li> -</ul> -<h2>Full Log</h2> -<p>16:36 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:36 <code>&lt;meetingology&gt;</code> Meeting started Mon Jan 7 16:36:15 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:36 <code>&lt;meetingology&gt;</code> </p> -<p>16:36 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> Happy New Year! We shifted the cloud-init status meeting time ... and then I subsequent forgot about it.</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> Hope the break went well for folks. We'll be hosting this meeting bi-weekly to keep folks updated on cloud-init developments</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> Generally the topics we cover in this status meeting are: Previous Actions, Recent Changes, In-progress Development, and Office hours</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> looking over last meeting minutes I see only one action</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> ^ meeting minutes</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/360905">https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/360905</a></p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> ^ this merge proposal from Jason Zions looks like it got updated and resubmitted a few days ago addressing our review comments. Let's get another review on this this week and see where it stands</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> - Upstream release of cloud-init 18.5 and publishing 18.5 to Ubuntu 19.04 (Disco)</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> - ds-identify: fix wrong variable name in ovf_vmware_transport_guestinfo.</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> - Scaleway: Support ssh keys provided inside an instance tag. [PORTE Loïc]</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> - OVF: simplify expected return values of transport functions.</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> - Vmware: Add support for the com.vmware.guestInfo OVF transport.</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> (<a href="[https://bugs.launchpad.net/bugs/1807466](https://bugs.launchpad.net/bugs/1807466)">LP: #1807466</a>)</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> - HACKING.rst: change contact info to Josh Powers</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> - Update to pylint 2.2.2.</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> - Release 18.5 [Ryan Harper] (<a href="[https://bugs.launchpad.net/bugs/1808380](https://bugs.launchpad.net/bugs/1808380)">LP: #1808380</a>)</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> - tests: add Disco release [Joshua Powers]</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> - net: render 'metric' values in per-subnet routes</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> [Ryan Harper] (<a href="[https://bugs.launchpad.net/bugs/1805871](https://bugs.launchpad.net/bugs/1805871)">LP: #1805871</a>)</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> - write_files: add support for appending to files. [James Baxter]</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> - config: On ubuntu select cloud archive mirrors for armel, armhf, arm64.</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> (<a href="[https://bugs.launchpad.net/bugs/1805854](https://bugs.launchpad.net/bugs/1805854)">LP: #1805854</a>)</p> -<p>16:45 <code>&lt;ubot5&gt;</code> Ubuntu bug 1807466 in cloud-init "add support for ovf transport com.vmware.guestInfo" [Medium,Fix committed]</p> -<p>16:45 <code>&lt;ubot5&gt;</code> Ubuntu bug 1808380 in cloud-init "Release 18.5" [Undecided,Fix released]</p> -<p>16:45 <code>&lt;ubot5&gt;</code> Ubuntu bug 1805871 in cloud-init (Ubuntu) "net renderers miss metric value in per-subnet routes" [Undecided,Fix released]</p> -<p>16:45 <code>&lt;ubot5&gt;</code> Ubuntu bug 1805854 in cloud-init "[feature-request] Add non-x86 Ubuntu EC2 mirrors in to default cloud-init configuration" [Medium,Fix released]</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> The above are commits landed in cloud-init since the last status meeting.</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> #topic In-Progress Development</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> As always we try tracking our ongoing cloud-init upstream work (and backlog) on our Trello board</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> #lin <a href="https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin">https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin</a></p> -<p>16:47 <code>&lt;robjo&gt;</code> <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098</a> is pending since October :( :(</p> -<p>16:47 <code>&lt;blackboxsw&gt;</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:47 <code>&lt;blackboxsw&gt;</code> #action Review robjo's branch today/tomorrow</p> -<p>16:47 * meetingology Review robjo's branch today/tomorrow</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> #action Review robjo's branch today/tomorrow <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098</a></p> -<p>16:47 * meetingology Review robjo's branch today/tomorrow <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098</a></p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098</a></p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> ok robjo, we'll have eyes on that today and get you something</p> -<p>16:48 <code>&lt;robjo&gt;</code> Also I filed a number of bugs w.r.t the network rendering some with proposals, for other's I simply have no idea about the best approach, none of these have seen any action</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> thanks for that</p> -<p>16:49 <code>&lt;robjo&gt;</code> then there is the Python 2 utf-8 issue w.r.t. metadata persistence on OpenStack</p> -<p>16:49 <code>&lt;robjo&gt;</code> smoser had supplied a test case, also not action on that issue since whenever .... :(</p> -<p>16:50 <code>&lt;robjo&gt;</code> on that topic the question is still open why that particular data is persisted in teh first place since every access to the APi on OpenStack yields a different result</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> #action review robjo's New bugs and get feedback <a href="https://bit.ly/2C4gEHJ">https://bit.ly/2C4gEHJ</a></p> -<p>16:51 * meetingology review robjo's New bugs and get feedback <a href="https://bit.ly/2C4gEHJ">https://bit.ly/2C4gEHJ</a></p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> robjo: I think we have to sort persistence story for metadata sub-components still. The only reason anything is persisted is for speed of course. OpenStack DS is notably very slow on every call the the md service.</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> robjo: some of that persistence/refresh should/will be addressed in rharper's openstack hotplug branch which would force cloud-init to refresh metadata when hotplug events are seen</p> -<p>16:57 <code>&lt;robjo&gt;</code> Well I have to admit that I do not know how OpenStack and or guest would use the value returned for "random_seed". What I was able to test is that the value is different when the API is aclled</p> -<p>16:59 <code>&lt;robjo&gt;</code> so that could mean that OpenStack keeps the "previously" returned value of "random_seed" until the API is called again and then uses the previous value for whatever hashing is being done to come up with authentication of the guest</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> robjo: is this the bug? <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</a></p> -<p>16:59 <code>&lt;ubot5&gt;</code> Ubuntu bug 1801364 in cloud-init "persisting OpenStack metadata fails" [Undecided,Confirmed]</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</a></p> -<p>17:00 <code>&lt;robjo&gt;</code> but that would imply that any calls to the OpenStack API from the quest must know that random_seed and I doubt that they are using the cache we build with cloud-init</p> -<p>17:00 <code>&lt;robjo&gt;</code> yes, that's the bug</p> -<p>17:03 <code>&lt;rharper&gt;</code> robjo: your <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098</a> was left in Needs Fixing and got tagged WIP; after you updated, it needed to move to Needs Review</p> -<p>17:04 <code>&lt;robjo&gt;</code> Well I am pretty sure I tried to set it back to get another review and from the interface it looked to me that happened.... :(</p> -<p>17:05 <code>&lt;robjo&gt;</code> If I look at the UI it tells me the review was requested from "Scott Moser [2]" on 2018-10-09 and the status is "Pending"</p> -<p>17:15 <code>&lt;blackboxsw&gt;</code> robjo: we're talking side-channel as we were in a meeting anyway. Just added a work item to help us avoid this situation</p> -<p>17:15 <code>&lt;blackboxsw&gt;</code> <a href="https://trello.com/c/bEGsPvTm/1028-updated-cloud-init-ci-review-bot-to-place-a-branch-back-into-needs-review-after-it-receives-a-commit">https://trello.com/c/bEGsPvTm/1028-updated-cloud-init-ci-review-bot-to-place-a-branch-back-into-needs-review-after-it-receives-a-commit</a></p> -<p>17:15 <code>&lt;blackboxsw&gt;</code> this will make reviews which you add commits to pop up on our radar anytime a new commit was added</p> -<p>17:16 <code>&lt;robjo&gt;</code> thanks</p> -<p>17:16 <code>&lt;blackboxsw&gt;</code> then we know what needs attention (as others have hit this issue too0</p> -<p>17:18 <code>&lt;blackboxsw&gt;</code> robjo: we also are talking about we can maybe blacklisting certain metadata elements as not-cacheable. We'll have to add 'cloud-init query' tooling to understand this at some point though.</p> -<p>17:18 <code>&lt;blackboxsw&gt;</code> #action blackboxsw resolve and land fix for <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</a> this week</p> -<p>17:18 * meetingology blackboxsw resolve and land fix for <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</a> this week</p> -<p>17:18 <code>&lt;ubot5&gt;</code> Ubuntu bug 1801364 in cloud-init "persisting OpenStack metadata fails" [Undecided,Confirmed]</p> -<p>17:19 <code>&lt;blackboxsw&gt;</code> though the fix for serialization won't include this blacklisting/cache solution I don't think</p> -<p>17:20 <code>&lt;blackboxsw&gt;</code> Ok I grabbed <a href="https://trello.com/c/7ouGpa0A/1029-openstack-serialization-errors-py27">https://trello.com/c/7ouGpa0A/1029-openstack-serialization-errors-py27</a></p> -<p>17:23 <code>&lt;robjo&gt;</code> There is a patch for a very simplistic approach attached to the bug, that's what I am currently carrying in the SUSE package</p> -<p>17:28 <code>&lt;blackboxsw&gt;</code> +1</p> -<p>17:28 <code>&lt;blackboxsw&gt;</code> ok, so I think that wraps current topic.</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 minutes)</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> upstream devs will have eyes on this channel for any concerns, questions or discussions folks want to have about cloud-init.</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> We've also started going through some of the open reviews</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> raharper is on <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/360905">https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/360905</a> currently. I'll start looking at this <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/360905">https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/360905</a></p> -<p>17:34 <code>&lt;blackboxsw&gt;</code> robjo: can you re-share that opensuse download link for latest cloud-init images generated (I think you had shared once in the past your server team's public/latest/testing downloads of cloud-init)</p> -<p>17:34 <code>&lt;blackboxsw&gt;</code> just for reference while you are here :)</p> -<p>17:34 <code>&lt;blackboxsw&gt;</code> s/images/packages/</p> -<p>17:37 <code>&lt;robjo&gt;</code> <a href="https://build.opensuse.org/package/show/Cloud:Tools:Next/cloud-init">https://build.opensuse.org/package/show/Cloud:Tools:Next/cloud-init</a></p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> thank you sir</p> -<p>17:38 <code>&lt;robjo&gt;</code> currently the same as the released <a href="https://build.opensuse.org/package/show/Cloud:Tools:Next/cloud-init">https://build.opensuse.org/package/show/Cloud:Tools:Next/cloud-init</a></p> -<p>17:38 <code>&lt;robjo&gt;</code> but planningt to move :Next to 18.5 this week</p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> excellent thanks robjo</p> -<p>18:02 <code>&lt;blackboxsw&gt;</code> ok think that wraps up the meeting for today</p> -<p>18:02 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-12-10T16:11:00+00:002018-12-10T16:11:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-12-10:/status-2018-12-10.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 10 Dec at 16:11 &mdash; 16:58 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-12-10-16.11.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-12-10-16.11.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:13.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427">https://code.launchpad.net/~jasonzio/cloud-init/+git …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 10 Dec at 16:11 &mdash; 16:58 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-12-10-16.11.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-12-10-16.11.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:13.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427">https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427</a> </li> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2018-11-26.html#status-2018-11-26">https://cloud-init.github.io/status-2018-11-26.html#status-2018-11-26</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392">https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392</a> </li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:19.</p> -<h3>In-Progress Development</h3> -<p>The discussion about "In-Progress Development" started at 16:24.</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="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/359876">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/359876</a> </li> -</ul> -<h3>Cloud-init upstream Release 18.5</h3> -<p>The discussion about "Cloud-init upstream Release 18.5" started at 16:27.</p> -<h3>Office Hours (next ~30 minutes)</h3> -<p>The discussion about "Office Hours (next ~30 minutes)" started at 16:31.</p> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (57)</li> -<li>meetingology (3)</li> -<li>ubot5 (2)</li> -<li>powersj (1)</li> -</ul> -<h2>Full Log</h2> -<p>16:11 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:11 <code>&lt;meetingology&gt;</code> Meeting started Mon Dec 10 16:11:11 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:11 <code>&lt;meetingology&gt;</code> </p> -<p>16:11 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> Welcome to our biweekly status meeting. The intent is to provide a venue where we can advertise current cloud-init development efforts and a place and time where interested community members can ask questions or raise issues to the upstream development team.</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> Generally we go through the following topics: Previous Actions, Recent Changes, In-progress Development, and Office hours</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> Today we'll add a "Release" topic</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> Let's kick it off</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> One action we need to carry over from last meeting</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427">https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427</a></p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> our followup review is required on this branch to avoid a race condition for DHCP discovery on RHEL</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> I don't think there were any other actions raised last meeting</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> BTW our meeting minutes from last status meeting are here</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2018-11-26.html#status-2018-11-26">https://cloud-init.github.io/status-2018-11-26.html#status-2018-11-26</a></p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> we did land and publish cloud-init to Disco containing the Azure netlink listener support branch which was raised as an action last meeting. per the following</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392">https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392</a></p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> The following branches landed in cloud-init tip- dhclient-hook: cleanups, tests and fix a bug on 'down' event.</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - NoCloud: Allow top level 'network' key in network-config. (<a href="[https://bugs.launchpad.net/bugs/1798117](https://bugs.launchpad.net/bugs/1798117)">LP: #1798117</a>)</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - ovf: Fix ovf network config generation gateway/routes</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> [Ryan Harper] (<a href="[https://bugs.launchpad.net/bugs/1806103](https://bugs.launchpad.net/bugs/1806103)">LP: #1806103</a>)</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - Published Cloud-init v.18.3-41 to Ubuntu Disco</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - azure: detect vnet migration via netlink media change event</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> [Tamilmani Manoharan]</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - Azure: fix copy/paste error in error handling when reading azure ovf.</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> [Adam DePue]</p> -<p>16:20 <code>&lt;ubot5&gt;</code> Ubuntu bug 1798117 in cloud-init (Ubuntu) "juju sends "network" top level key to user.network-config in lxd containers" [Medium,Confirmed]</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - tests: fix incorrect order of mocks in test_handle_zfs_root.</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - doc: Change dns_nameserver property to dns_nameservers. [Tomer Cohen]</p> -<p>16:20 <code>&lt;ubot5&gt;</code> Ubuntu bug 1806103 in cloud-init (Ubuntu) "ovf: network config store routes under nic subnets 'routes' key" [Undecided,New]</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - OVF: identify label iso9660 filesystems with label 'OVF ENV'.</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - net: Ephemeral*Network: add connectivity check via URL</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> [Igor Galić]</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> we also published all latest changes to Ubuntu Disco as 18.4-31-gbf791715-0ubuntu1</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> I missed a couple of other commits to cloud-init</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> - config: On ubuntu select cloud archive mirrors for armel, armhf, arm64.</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> - write_files: add support for appending to files. [James Baxter]</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> Thanks James, Tamilmani, Adam and Tomer for the contributions here and making cloud-init bette</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> r</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> #topic In-Progress Development</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> We track our current work in the TODO, Doing and Done lanes on trello</p> -<p>16:24 <code>&lt;blackboxsw&gt;</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:25 <code>&lt;blackboxsw&gt;</code> mostly we are trying to wrap up low-hanging-fruit and bug fixes as we have an upstream release scheduled this week for cloud-init 18.5</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> There is also some significant work ongoing my smoser for vmware and ovf deployment support</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> <em>by smoser</em></p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> and rharper has a branch up to fix network metric config handling for subnet routes</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/359876">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/359876</a></p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> think that about wraps in-progress work.</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> #topic Cloud-init upstream Release 18.5</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> So, we have our 18.5 upstream release scheduled for this Wednesday 12/13/2018</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> If there are any feature requests or critical bug fixes that folks are interested, please bring them up either in channel here, or on the mailing list, cloud-init@lists.launchpad.net</p> -<p>16:29 <code>&lt;powersj&gt;</code> blackboxsw, ^ is that worth sending to mailing list?</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> powersj: yes. I'll send that email out in the next half hour</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> agreed</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> think that about wraps this status update for this meeting</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 minutes)</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> upstream devs will have eyes on this channel for any concerns, questions or discussions folks want to have about cloud-init.</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> Given the upcoming holidays, I think we will take a break from this meeting as next scheduled time would be the day before Christmas.</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> Next status meeting will be Monday January 7th 16:15 UTC</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> email sent to cloud-init about upcoming release</p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> Happy Holiday folks. Looks like we're already starting to use up vacation time. Thanks for tuning in. See you next year!</p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-11-26T16:18:00+00:002018-11-26T16:18:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-11-26:/status-2018-11-26.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 26 Nov at 16:18 &mdash; 17:17 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-11-26-16.18.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-11-26-16.18.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io">https://cloud-init.github.io</a> - <strong>LINK</strong>: <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427">https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427</a> - <strong>LINK</strong>: <a href="https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/358881">https://code …</a></p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 26 Nov at 16:18 &mdash; 17:17 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-11-26-16.18.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-11-26-16.18.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io">https://cloud-init.github.io</a> - <strong>LINK</strong>: <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427">https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427</a> - <strong>LINK</strong>: <a href="https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/358881">https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/358881</a> - <strong>LINK</strong>: c<a href="https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392">https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392</a> - <strong>LINK</strong>: <a href="https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392">https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392</a> </p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:29.</p> -<h3>In-Progress Development</h3> -<p>The discussion about "In-Progress Development" started at 16:33.</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>Office Hours (next ~30 minutes)</h3> -<p>The discussion about "Office Hours (next ~30 minutes)" started at 16:45.</p> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (64)</li> -<li>meena (10)</li> -<li>rharper (4)</li> -<li>meetingology (3)</li> -<li>ubot5 (2)</li> -</ul> -<h2>Full Log</h2> -<p>16:18 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:18 <code>&lt;meetingology&gt;</code> Meeting started Mon Nov 26 16:18:39 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:18 <code>&lt;meetingology&gt;</code> </p> -<p>16:18 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> Morning/Afternoon folks. welcome to another cloud-init status meeting</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> ... our open forum to advertise current cloud-init developments, giving an opportunity to discuss bugs or features in cloud-init and provide a touch point for the community</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> Generally we go through the following topics: Previous Actions, Recent Changes, In-progress Development, and Office hours</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> our last meeting's minutes are located here</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io">https://cloud-init.github.io</a></p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> only thing we carried into that meeting is a an review</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427">https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427</a></p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> rharper: had closed out feedback on the review. with a needs fixing. I did see some followup commits there from the author Jason Zion.</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> I think we need to take a look at this again and see if our comments were addressed, I'm marking it "Needs review"</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> I see no other actions carried over... but there was talk last week about a couple of branches so let's add these</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/358881">https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/358881</a></p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> ^ disco support</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> #link c<a href="https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392">https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392</a></p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392">https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392</a></p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> ^ Azure netlink listener</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> ok next topic</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> - azure: _poll_imds only retry on 404. Fail on Timeout</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> (<a href="[https://bugs.launchpad.net/bugs/1803598](https://bugs.launchpad.net/bugs/1803598)">LP: #1803598</a>)</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> - resizefs: Prefix discovered devpath with '/dev/' when path does not</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> exist [Igor Galić]</p> -<p>16:30 <code>&lt;ubot5&gt;</code> Ubuntu bug 1803598 in cloud-init "Do not retry polling IMDS for reprovisiondata during timeout" [Undecided,Fix committed]</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> t'was a slow week with all that Thanksgiving holiday stuff for US-based employees</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> welcome back from the Holidays boys and girls</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> also we were able to publish tip of cloud-init to Ubuntu Disco series</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> cloud-init 18.4-24-g8f812a15-0ubuntu1 has latest and greatest as seen on tip of master</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> #topic In-Progress Development</p> -<p>16:33 <code>&lt;blackboxsw&gt;</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:34 <code>&lt;blackboxsw&gt;</code> Our trello board tracks our queued and current work for cloud-init, feel free to watch that board for updates on significant cloud-init features/bug-fixes</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> what generally isn't tracked there is reviews on community authored branches</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> per community driven content, we have a number of branches from meena for better FreeBSD support in flight. Great work! and some Azure platform development to react to netlink events during the preprovisioning state.</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> thanks tamilmani_ on the azure work.</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> As a heads up to folks, we are trying to cut an upstream release of cloud-init 18.5 on 12/15/2018. So if there are branches you want to see landed or bugs you need fixed please holler here in this channel or on the mailing list to:cloud-init.lists.launchpad.net</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> We'll send an email to the mailing list requesting for input on the release as well</p> -<p>16:39 <code>&lt;meena&gt;</code> &gt;<code>blackboxsw what generally isn't tracked there is reviews on community authored branches</code>&lt;== i did check there first time around, but found nothing that was topical for me</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> Correct meena . I used to capture outstanding community reviews that needed review follow up, but that ended up being out of date all the time. It was easier for us to just use launchpad active review queue instead</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> Now we've tried to adopt the setting of a branch status to 'work in progress' if we are expecting feedback/fixes from the author. And have the author set it back to 'needs review' when it is ready for another round of upstream reviews</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> having trello cards was basically just duplicating what launchpad reviews were designed for, we just need to be more vigilant about grooming the review queue and getting folks the feedback they need</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> might as well switch over to office hours for open discussion etc.</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 minutes)</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> Cloud-init upstream folks will have eyes on this channel for any discussions. requests, bugs or features folks want to discuss.</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> we'll also spend some time actively grooming the branch review queue to see if we can clear out some review debyt</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> we'll also spend some time actively grooming the branch review queue to see if we can clear out some review debt</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> I think smoser mentioned at our team standup this morning he was taking one more review on <a href="https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392">https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392</a></p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> rharper: if you are done with your review on that tamilmani_ branch can you add a comment that doesn't leave it in "Needs fixing" review state from yoiu?</p> -<p>16:48 <code>&lt;rharper&gt;</code> blackboxsw: yes, I'm adding a commit message now, and I'll leave a comment marking approve;</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> excellent.</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> I'm going to give a review to <a href="https://code.launchpad.net/~i.galic/cloud-init/+git/cloud-init/+merge/358876">https://code.launchpad.net/~i.galic/cloud-init/+git/cloud-init/+merge/358876</a> now</p> -<p>16:48 * blackboxsw claims a review slot</p> -<p>16:49 <code>&lt;rharper&gt;</code> blackboxsw: did we have a LP for thisone ?</p> -<p>16:49 <code>&lt;rharper&gt;</code> the netlink ?</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> ohh, no we did not I don't think.</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> I'll check</p> -<p>16:56 <code>&lt;meena&gt;</code> blackboxsw: i think my (our) patch is ready to be merged</p> -<p>16:57 <code>&lt;blackboxsw&gt;</code> rharper: yeah didn't find any bug filed related to Azure and dhcp leak or netlink response etc.</p> -<p>16:57 <code>&lt;meena&gt;</code> (the feature / fix of adding connectivity check to ephemeral network stuff)</p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> meena: I think so too. Was just dusting off my memory on that one. I'm going to do a quick test run of setup/teardown and I think that's good. +1</p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> thanks again</p> -<p>16:58 <code>&lt;meena&gt;</code> once that's merged, I'll have a much easier time with splitting out the freebsd network</p> -<p>16:59 <code>&lt;meena&gt;</code> blackboxsw: thank you for showing me how to do the tests properly</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> most welcome.</p> -<p>17:00 <code>&lt;rharper&gt;</code> blackboxsw: thanks, me neither; I just didn't want to miss a LP: in the commit message if we had one</p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> after this branch lands and tamilmani_'s I probably will go through the motions of us publishing to Ubuntu Disco again, because I want to get a round or two of integration tests on both Azure and AWS with both the ephemeral* changes and the netlink stuff on pristine cloud-images before next week's release</p> -<p>17:06 <code>&lt;blackboxsw&gt;</code> meena: you didn't file a bug related to the ephermeraldhcp network connectivity did you? (I'm just double checking as I don't see one)</p> -<p>17:07 <code>&lt;blackboxsw&gt;</code> meena: not needed, just didn't want to miss it if it was there (as we'd want to link it in the commit message)</p> -<p>17:08 <code>&lt;meena&gt;</code> blackboxsw: nah, we just "filed" a mailing list thread</p> -<p>17:08 <code>&lt;blackboxsw&gt;</code> all good thanks</p> -<p>17:09 <code>&lt;blackboxsw&gt;</code> ok I had filed <a href="https://bugs.launchpad.net/cloud-init/+bug/1802598">https://bugs.launchpad.net/cloud-init/+bug/1802598</a> but we won't tie that to this branch</p> -<p>17:09 <code>&lt;ubot5&gt;</code> Ubuntu bug 1802598 in cloud-init "EphemeralIPv4Network: when device has requested existing network config, but link is down, network setup does not bring link up" [Undecided,Triaged]</p> -<p>17:09 <code>&lt;blackboxsw&gt;</code> it's a bit more about idempotent behavior</p> -<p>17:13 <code>&lt;meena&gt;</code> <em>nod </em>nod</p> -<p>17:13 <code>&lt;meena&gt;</code> i didn't think i had fixed it, so i didn't connect them.</p> -<p>17:16 <code>&lt;blackboxsw&gt;</code> +1 on your branch meena, it should land within the hour. Just tested it out one more time</p> -<p>17:16 <code>&lt;meena&gt;</code> cool</p> -<p>17:16 <code>&lt;blackboxsw&gt;</code> ok I think that about wraps today's meeting timewise. Thanks again for the chat meena.</p> -<p>17:16 <code>&lt;meena&gt;</code> \o/</p> -<p>17:17 <code>&lt;blackboxsw&gt;</code> next meeting is Dec 10, 2018 sameish time</p> -<p>17:17 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-11-12T16:17:00+00:002018-11-12T16:17:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-11-12:/status-2018-11-12.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 12 Nov at 16:17 &mdash; 17:27 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-11-12-16.17.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-11-12-16.17.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:20.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427">https://code …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 12 Nov at 16:17 &mdash; 17:27 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-11-12-16.17.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-11-12-16.17.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:20.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427">https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427</a> </li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:24.</p> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:30.</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="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/358112">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/358112</a> </li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bug/1802598">https://bugs.launchpad.net/cloud-init/+bug/1802598</a> </li> -</ul> -<h3>Office Hours (next ~30 minutes)</h3> -<p>The discussion about "Office Hours (next ~30 minutes)" started at 16:40.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~i.galic/cloud-init/+git/cloud-init/+merge/357723">https://code.launchpad.net/~i.galic/cloud-init/+git/cloud-init/+merge/357723</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 (53)</li> -<li>ubot5 (3)</li> -<li>meetingology (3)</li> -</ul> -<h2>Full Log</h2> -<p>16:17 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:17 <code>&lt;meetingology&gt;</code> Meeting started Mon Nov 12 16:17:50 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:17 <code>&lt;meetingology&gt;</code> </p> -<p>16:17 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> Morning/afternoon folks. Time for another brief episode of cloud-init upstream updates</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> Last meeting was 10/29 and meeting minutes live over on github</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> This meeting is an open forum for cloud-init discussions and status updates, feel free to interject at any time. It really is just a venue by which we can make sure we all have eyes and ears available for discussion on features, bugs or branches if needed.</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> Generally we go through the following topics: Previous Actions, Recent Changes, In-progress Development, and Office hours</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #toic Previous Actions</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> So last meeting we carried in one action, to review the following Azure branch related to DHCP and RHEL race conditions</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427">https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427</a></p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> Looks like rharper got a review in and I don't see any updates from Jason Zion (author) in response to that branch</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> thanks rharper</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> I'm marking that branch as 'Work in progress' and commenting that the author should set it back to 'Needs review' when comments have been addressed</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> ok done. No further actions seen</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:24 * blackboxsw digs up changes since 10/28</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> sorry interrupted.</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> Here are the changes committed:</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> - azure: add udev rules to create cloud-init Gen2 disk name symlinks</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> (<a href="[https://bugs.launchpad.net/bugs/1797480](https://bugs.launchpad.net/bugs/1797480)">LP: #1797480</a>)</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> - tests: ec2 mock missing httpretty user-data and instance-identity routes</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> - azure: remove /etc/netplan/90-hotplug-azure.yaml when net from IMDS</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> - azure: report ready to fabric after reprovision and reduce logging</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> [asakkurr] (<a href="[https://bugs.launchpad.net/bugs/1799594](https://bugs.launchpad.net/bugs/1799594)">LP: #1799594</a>)</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> - query: better error when missing read permission on instance-data</p> -<p>16:29 <code>&lt;ubot5&gt;</code> Ubuntu bug 1797480 in cloud-init "Azure: Support ephemeral disk handling on Gen2 VMs" [High,Fix committed]</p> -<p>16:29 <code>&lt;ubot5&gt;</code> Ubuntu bug 1799594 in cloud-init "Azure - Report ready during preprovisioning as soon as we get the ReprovisionData" [Undecided,Fix committed]</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> As you can see we are seeing a bit of momentum on azure datasource and some continuous integration cleanup on our side.</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> Thanks asakkurr for pulling that Azure branch together</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> We track our current cloud-init development publicly on trello</p> -<p>16:31 <code>&lt;blackboxsw&gt;</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:31 <code>&lt;blackboxsw&gt;</code> if there are any questions about certain branches or work feel free to comment in channel or on the linked branches we document there.</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> It looks like the Ubuntu archive for Disco Dingo series is open, so we'll likely be pushing an upload of tip of cloud-init by EOD today to get a new release queued</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> Also to note, I'd like to see us land <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/358112">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/358112</a> to fix an Azure retry on IMDS timeout to avoid cloud-init giving up if the instance boots while IMDS service is down or temporarily unavailable (I've only seen this once on any azure instance)</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/358112">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/358112</a></p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> we also have a fairly deep review queue, so we'll be attacking that in the 2nd half of today's meeting to clear out and respond to some of those merge proposals</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> I also think we have some mailing list threads to start responding to per usage of EphemeralDHCPv4 and EphemeralIPv4Network context managers.</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> I <em>think</em> the intent there should be that those context managers ensure that they setup whatever requested network configuration is misssing from a network interface.... so if an interface is 'down' yet has correct address configured, ephemeral* will make sure it is in operable 'up' state .</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> See the following bug for more information:</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/+bug/1802598">https://bugs.launchpad.net/cloud-init/+bug/1802598</a></p> -<p>16:38 <code>&lt;ubot5&gt;</code> Ubuntu bug 1802598 in cloud-init "EphemeralIPv4Network: when device has requested existing network config, but link is down, network setup does not bring link up" [Undecided,New]</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> I believe that about wraps it for current in-flight work. I'll drop us into office hours at the point</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 minutes)</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> Cloud-init upstream folks will have eyes on this channel for any discussions. requests, bugs or features folks want to discuss.</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> I'll spend most of this time on reviews to start to clear our review queue (or at least get some responses out to folks for more information)(</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> ok looks like <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357669">https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357669</a> is ready for landing. Just kicking off a CI test run on it</p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> also the approved version of this branch didn't actually match what Jenkins autolander expected, I've kick the jenkins landing job that should truly land that branch now. <a href="https://code.launchpad.net/~asakkurr/cloud-init/+git/cloud-init/+merge/358422">https://code.launchpad.net/~asakkurr/cloud-init/+git/cloud-init/+merge/358422</a>'</p> -<p>17:25 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~i.galic/cloud-init/+git/cloud-init/+merge/357723">https://code.launchpad.net/~i.galic/cloud-init/+git/cloud-init/+merge/357723</a></p> -<p>17:25 <code>&lt;blackboxsw&gt;</code> ok just got through an initial review there too.</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> ok looks like our lander merged <a href="https://code.launchpad.net/~asakkurr/cloud-init/+git/cloud-init/+merge/358422">https://code.launchpad.net/~asakkurr/cloud-init/+git/cloud-init/+merge/358422</a></p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> and :( <a href="https://jenkins.ubuntu.com/server/job/cloud-init-ci/431/console">https://jenkins.ubuntu.com/server/job/cloud-init-ci/431/console</a> the CI on jason zion</p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> and :( <a href="https://jenkins.ubuntu.com/server/job/cloud-init-ci/431/console">https://jenkins.ubuntu.com/server/job/cloud-init-ci/431/console</a> the CI on jason zion's branch will take 9 hrs and 51 minutes (because it doesn't have our CI fix for leaked test_ec2 link local unittests which take forever to timeout</p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> ok will that about wraps today's status meeting</p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> thanks all</p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-10-29T16:21:00+00:002018-10-29T16:21:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-10-29:/status-2018-10-29.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 29 Oct at 16:21 &mdash; 17:09 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-10-29-16.21.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-10-29-16.21.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:22.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2018-10-15.html#status-2018-10-15">https://cloud-init.github.io/status-2018-10-15.html#status-2018-10-15 …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 29 Oct at 16:21 &mdash; 17:09 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-10-29-16.21.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-10-29-16.21.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:22.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2018-10-15.html#status-2018-10-15">https://cloud-init.github.io/status-2018-10-15.html#status-2018-10-15</a> </li> -<li><strong>ACTION</strong>: Sort and review azure RHEL branch related to ephemeral dhcp handling of dhclient <a href="https://bugs.launchpad.net/cloud-init/+bug/1794399">https://bugs.launchpad.net/cloud-init/+bug/1794399</a></li> -<li><strong>ACTION</strong>: blackboxsw, rharper smoser a review on <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427">https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427</a> before next status meeting for Azure dhcp.</li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:28.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://events.linuxfoundation.org/events/open-source-summit-europe-2018/">https://events.linuxfoundation.org/events/open-source-summit-europe-2018/</a> </li> -</ul> -<h3>In-Progress Development</h3> -<p>The discussion about "In-Progress Development" started at 16:38.</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>Office hours (next ~30 mins)</h3> -<p>The discussion about "Office hours (next ~30 mins)" started at 16:44.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </li> -</ul> -<h2>Vote results</h2> -<h2>Action items, by person</h2> -<ul> -<li>blackboxsw</li> -<li>blackboxsw, rharper smoser a review on <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427">https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427</a> before next status meeting for Azure dhcp.</li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (46)</li> -<li>meetingology (5)</li> -<li>ubot5 (4)</li> -</ul> -<h2>Full Log</h2> -<p>16:21 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:21 <code>&lt;meetingology&gt;</code> Meeting started Mon Oct 29 16:21:16 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:21 <code>&lt;meetingology&gt;</code> </p> -<p>16:21 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> hi folks, now marks a 20 minute belated cloud-init status meeting, an opportunity to chat about current and future cloud-init happenings.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> Today's meeting will go through the typical topics: Previous Actions, Recent Changes, In-progress development and Office hours</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> Looking over our last meeting minutes, we had a single action</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2018-10-15.html#status-2018-10-15">https://cloud-init.github.io/status-2018-10-15.html#status-2018-10-15</a></p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> #action Sort and review azure RHEL branch related to ephemeral dhcp handling of dhclient <a href="https://bugs.launchpad.net/cloud-init/+bug/1794399">https://bugs.launchpad.net/cloud-init/+bug/1794399</a></p> -<p>16:24 * meetingology Sort and review azure RHEL branch related to ephemeral dhcp handling of dhclient <a href="https://bugs.launchpad.net/cloud-init/+bug/1794399">https://bugs.launchpad.net/cloud-init/+bug/1794399</a></p> -<p>16:24 <code>&lt;ubot5&gt;</code> Ubuntu bug 1794399 in cloud-init "cloud-init dhcp_discovery() crashes on preprovisioned RHEL 7.6 VM in Azure" [Undecided,New]</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> the meeting later showed us we didn't really have a branch referencing that bug, looks like paulmey was able to follow up there to tie the related branch to the bug. So we have something to review now</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> So looks like this is a <em>carryover</em> from last meeting, thanks Paul for tying the branch to this bug so we have something to review related to it. The branch is currently waiting on review feedback from cloud-init upstream. So, I'll pull it in for us to review this week</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> #action blackboxsw, rharper smoser a review on <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427">https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427</a> before next status meeting for Azure dhcp.</p> -<p>16:27 * meetingology blackboxsw, rharper smoser a review on <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427">https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427</a> before next status meeting for Azure dhcp.</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> over the last week, a number of us have been travelling at either planning meetings for cloud-init or the OpenSource Summit in Europe.</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> #link <a href="https://events.linuxfoundation.org/events/open-source-summit-europe-2018/">https://events.linuxfoundation.org/events/open-source-summit-europe-2018/</a></p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> The cloud-init talk had a pretty good turn out at OSS EU. I think we had ~ 100 people in attendance and some good questions about potential support of the following:</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> - Ansible and CFEgine config module support in cloud-initt</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> - better netplan config use-case handling</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> - better vmware integration as well as a request for proxmox (opensource alternative to vmware?) support</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> thanks smoser for a job well done on that talk.</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> beyond the conference highlight, cloud-init tip is being published to Xenial and Bionic on Ubuntu.</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> Expect to see updates published in today's images that will handle template-support for #cloud-config and user-data scripts and generalized instance-data.json on most recent Ubuntu releases.</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> tip of cloud-init has seen the following changes merged:</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> - instance-data: fallback to instance-data.json if sensitive is absent.</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> (<a href="[https://bugs.launchpad.net/bugs/1798189](https://bugs.launchpad.net/bugs/1798189)">LP: #1798189</a>)</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> - docs: remove colon from network v1 config example. [Tomer Cohen]</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> - Add cloud-id binary to packages for SUSE [Jason Zions]</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> - systemd: On SUSE ensure cloud-init.service runs before wicked</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> [Robert Schweikert] (<a href="[https://bugs.launchpad.net/bugs/1799709](https://bugs.launchpad.net/bugs/1799709)">LP: #1799709</a>)</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> - update detection of openSUSE variants [Robert Schweikert]</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> - azure: Add apply_network_config option to disable network from IMDS</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> (<a href="[https://bugs.launchpad.net/bugs/1798424](https://bugs.launchpad.net/bugs/1798424)">LP: #1798424</a>)</p> -<p>16:36 <code>&lt;ubot5&gt;</code> Ubuntu bug 1798189 in cloud-init "cloud-init query: /run/cloud/instance-data-sensitive.json not generated on upgrade" [Medium,Fix committed]</p> -<p>16:36 <code>&lt;ubot5&gt;</code> Ubuntu bug 1799709 in cloud-init "service order is incorrect for SUSE distros" [Undecided,Fix committed]</p> -<p>16:36 <code>&lt;ubot5&gt;</code> Ubuntu bug 1798424 in cloud-init (Ubuntu) "Xenial Azure: Make generation of network config from IMDS hotplug scripts configurable opt-in" [Undecided,New]</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> Thanks robjo for the commitment to keeping SuSE up to date and fully functional with cloud-init.</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> And thanks Jason and Tomer for the contributions to packaging and docs as well</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> Think that about wraps Recent Changes topic....</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> #topic In-Progress Development</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> Check out trello board for a prioritized order of what upstream is working</p> -<p>16:39 <code>&lt;blackboxsw&gt;</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:41 <code>&lt;blackboxsw&gt;</code> There are a couple of community branches in the wings that we'll get reviews on and shepherd into cloud-init proper. Azure has some work to increase efficiency of the detection and reporting during initial boot.</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> smoser is working on supplemental work with meena to handle platform-specializing our cloudinit.net module.</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> and I think we have a couple of branches pulled together for legacy centos6 build support and supporting Azure Gen2 vms.</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> We'll keep the trello board updated as big items come down the pipeline for us.</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> #topic Office hours (next ~30 mins)</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> so eyes will float on this channel a bit for any questions, concerns, bugs or features.</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> thanks again for your time and contributions folks.</p> -<p>17:09 <code>&lt;blackboxsw&gt;</code> alright. guess I'll call it wrap for this meeting. You can tune in to minutes on published github to browse any content that has been discussed at previous status meetings.</p> -<p>17:09 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>17:09 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-10-15T16:15:00+00:002018-10-15T16:15:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-10-15:/status-2018-10-15.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 15 Oct at 16:15 &mdash; 17:00 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-10-15-16.15.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-10-15-16.15.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:18.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </li> -</ul> -<h3>Recent Changes</h3> -<p>The …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 15 Oct at 16:15 &mdash; 17:00 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-10-15-16.15.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-10-15-16.15.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:18.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:19.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html#using-instance-data">https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html#using-instance-data</a> </li> -</ul> -<h3>In-Progress Development</h3> -<p>The discussion about "In-Progress Development" started at 16:28.</p> -<ul> -<li><strong>LINK</strong>: trello.com/b/hFtWKUn3/daily-cloud-init-curtin </li> -</ul> -<h3>Office hours (next ~30 mins)</h3> -<p>The discussion about "Office hours (next ~30 mins)" started at 16:35.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bug/1794399">https://bugs.launchpad.net/cloud-init/+bug/1794399</a> </li> -<li><strong>ACTION</strong>: Sort and review azure RHEL branch related to ephemeral dhcp handling of dhclient <a href="https://bugs.launchpad.net/cloud-init/+bug/1794399">https://bugs.launchpad.net/cloud-init/+bug/1794399</a></li> -<li><strong>ACTION</strong>: paulmey to dig up reference to proposed patch for <a href="https://bugs.launchpad.net/cloud-init/+bug/1794399">https://bugs.launchpad.net/cloud-init/+bug/1794399</a></li> -</ul> -<h2>Vote results</h2> -<h2>Action items, by person</h2> -<ul> -<li>paulmey</li> -<li>paulmey to dig up reference to proposed patch for <a href="https://bugs.launchpad.net/cloud-init/+bug/1794399">https://bugs.launchpad.net/cloud-init/+bug/1794399</a></li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (89)</li> -<li>paulmey (22)</li> -<li>ubot5 (13)</li> -<li>meetingology (5)</li> -<li>smoser (2)</li> -</ul> -<h2>Full Log</h2> -<p>16:15 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:15 <code>&lt;meetingology&gt;</code> Meeting started Mon Oct 15 16:15:41 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:15 <code>&lt;meetingology&gt;</code> </p> -<p>16:15 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> hi guys and gals. Today marks a belated cloud-init status meeting we use to provide a forum where folks from the cloud-init community can keep up to date on latest cloud-init developments and tap a shoulder if bugs or features need discussion/attention.</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> Next meeting will be two weeks from now on October 29th. at 16:00 UTC (as in the topic of this channel)</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> Today's meeting will go through the typical topics: Previous Actions, Recent Changes, In-progress development and Office hours</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> No unresolved actions from last meeting on Sept 25th.</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> For those interested our previous meeting minutes are at the following:</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> There has been a lot of work put into cloud-init over the last couple of weeks due to the timing of the Ubuntu Cosmic (18.10) series final freeze and release schedule</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> We managed to squeeze in a couple of features into 18.4 as well as improved some of Ubuntu's automated testing for StableReleaseUpdates (SRUs).</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> Beyond the 18.4 public upstream release (which is in Ubuntu Cosmic). We have the following commits that have landed since the last status meeting.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - tests: allow skipping an entire cloud_test without running.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - tests: disable lxd tests on cosmic</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - cii-tests: use unittest2.SkipTest in ntp_chrony due to new deps</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - lxd: adjust to snap installed lxd.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - docs: surface experimental doc in instance-data.json</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - tests: fix ec2 integration tests. process meta_data instead of meta-data</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - Add support for Infiniband network interfaces (IPoIB). [Mark Goddard]</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - cli: add cloud-init query subcommand to query instance metadata</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - tools/tox-venv: update for new features.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - pylint: ignore warning assignment-from-no-return for _write_network</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - stages: Fix bug causing datasource to have incorrect sys_cfg.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> (<a href="[https://bugs.launchpad.net/bugs/1787459](https://bugs.launchpad.net/bugs/1787459)">LP: #1787459</a>)</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - Remove dead-code _write_network distro implementations.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - net_util: ensure static configs have netmask in translate_network result</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> [Thomas Berger] (<a href="[https://bugs.launchpad.net/bugs/1792454](https://bugs.launchpad.net/bugs/1792454)">LP: #1792454</a>)</p> -<p>16:22 <code>&lt;ubot5&gt;</code> Ubuntu bug 1787459 in cloud-init (Ubuntu) "datasource.sys_cfg gets different values in local stage and after." [Medium,Fix released]</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - Fall back to root:root on syslog permissions if other options fail.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> [Robert Schweikert]</p> -<p>16:22 <code>&lt;ubot5&gt;</code> Ubuntu bug 1792454 in cloud-init "Network configuration broken for some distributions with OpenNebula, EC2, Azure" [High,Fix released]</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - tests: Add mock for util.get_hostname. [Robert Schweikert] (<a href="[https://bugs.launchpad.net/bugs/1792799](https://bugs.launchpad.net/bugs/1792799)">LP: #1792799</a>)</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - ds-identify: doc string cleanup.</p> -<p>16:22 <code>&lt;ubot5&gt;</code> Ubuntu bug 1792799 in cloud-init "Host environment bleeds into test for mirror access testing" [Undecided,Fix released]</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - OpenStack: Support setting mac address on bond.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - bash_completion/cloud-init: fix shell syntax error.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - EphemeralIPv4Network: Be more explicit when adding default route.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> (<a href="[https://bugs.launchpad.net/bugs/1792415](https://bugs.launchpad.net/bugs/1792415)">LP: #1792415</a>)</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - OpenStack: support reading of newer versions of metdata.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - OpenStack: fix bug causing 'latest' version to be used from network.</p> -<p>16:22 <code>&lt;ubot5&gt;</code> Ubuntu bug 1792415 in cloud-init (Ubuntu) "WARNINGs and failures in log on OVH public cloud" [Medium,Fix released]</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> (<a href="[https://bugs.launchpad.net/bugs/1792157](https://bugs.launchpad.net/bugs/1792157)">LP: #1792157</a>)</p> -<p>16:22 <code>&lt;ubot5&gt;</code> Ubuntu bug 1792157 in cloud-init (Ubuntu) "cloud-init uses openstack latest version due to decoding bug" [Medium,Fix released]</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> - Correct spelling in an error message (udevadm). [Katie McLaughlin]</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> - tests: meta_data key changed to meta-data in ec2 instance-data.json</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> (<a href="[https://bugs.launchpad.net/bugs/1797231](https://bugs.launchpad.net/bugs/1797231)">LP: #1797231</a>)</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> - tests: fix kvm integration test to assert flexible config-disk path</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> (<a href="[https://bugs.launchpad.net/bugs/1797199](https://bugs.launchpad.net/bugs/1797199)">LP: #1797199</a>)</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> - tools: Add cloud-id command line utility</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> - instance-data: Add standard keys platform and subplatform. Refactor ec2.</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> - net: ignore nics that have "zero" mac address. (<a href="[https://bugs.launchpad.net/bugs/1796917](https://bugs.launchpad.net/bugs/1796917)">LP: #1796917</a>)</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> - tests: fix apt_configure_primary to be more flexible</p> -<p>16:23 <code>&lt;ubot5&gt;</code> Ubuntu bug 1797231 in cloud-init "ec2 integration test failure on changed instance-data.json" [High,Fix committed]</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> - Ubuntu: update sources.list to comment out deb-src entries. (<a href="[https://bugs.launchpad.net/bugs/74747](https://bugs.launchpad.net/bugs/74747)">LP: #74747</a>)</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> - release 18.4 (<a href="[https://bugs.launchpad.net/bugs/1795741](https://bugs.launchpad.net/bugs/1795741)">LP: #1795741</a>)</p> -<p>16:23 <code>&lt;ubot5&gt;</code> Ubuntu bug 1797199 in cloud-init "kvm integration test failures due to invalid config-disk path" [High,Fix committed]</p> -<p>16:23 <code>&lt;ubot5&gt;</code> Ubuntu bug 1796917 in cloud-images "cloud-init fails to run on latest cosmic minimal image" [High,Fix released]</p> -<p>16:23 <code>&lt;ubot5&gt;</code> Ubuntu bug 74747 in cloud-init (Ubuntu Bionic) "Default sources.list file has source packages enabled by default" [Medium,Confirmed]</p> -<p>16:23 <code>&lt;ubot5&gt;</code> Ubuntu bug 1795741 in cloud-init (Ubuntu) "Release 18.4" [Medium,Fix released]</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> If you get a chance, it's worth noting that #cloud-config files can now be presented as a jinja template to the instance by adding a ## template: jinja as the first line above the #cloud-config in your user-data. Any metadata that cloud-init consumes (like cloud-given hostnames, ip addresses, region names etc) can be sourced and rendered in your cloud-config files now.</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html#using-instance-data">https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html#using-instance-data</a></p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> ^ for more information on instance data and templating</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> #topic In-Progress Development</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> #link trello.com/b/hFtWKUn3/daily-cloud-init-curtin</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> Our trello board tracks our current work. The most notable effort is cloud-init network hotplug handling for datasources which is currently being driven by rharper</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> What he is adding is the ability for for a datasource to be configured react to network hotplug events and apply cloud-init determined network configuration on device add/remove</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> This feature will be opt-in and configurable by the end-user to allow cloud-init to own network for any device added or removed after the initial boot. This feature will debut in OpenStack clouds and will shortly be adopted by other cloud/datasource types.</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> Also, smoser and I will be heading to OpenSource Summit Europe next week in Edinburgh, UK. <a href="https://events.linuxfoundation.org/events/open-source-summit-europe-2018/">https://events.linuxfoundation.org/events/open-source-summit-europe-2018/</a></p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> If you are in town come say hi :)</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> Without further ado, I think that about wraps our status for today</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> #topic Office hours (next ~30 mins)</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> Almost forgot; as part of the SRU process for for cloud-init to release into Xenial and Bionic, we'll be doing some additional manual and automated testing of cloud-init version 18.4 before publishing to those LTS series. I expect that'll take up a bit of our time this week and next as there is a lot to verify for that release.</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> For the next 30 mins, a few of us will have eyes on the channel for anyone with a desire to talk cloud-init bugs, features or reviews. Thanks again for the contributions and making cloud-init better!</p> -<p>16:40 <code>&lt;paulmey&gt;</code> Hi blackboxsw</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> Hi paulmey, how're things</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> ?</p> -<p>16:41 <code>&lt;paulmey&gt;</code> Good! How about yourself?</p> -<p>16:41 <code>&lt;paulmey&gt;</code> My buddy Jason has a bug open that could use some attention: <a href="https://bugs.launchpad.net/cloud-init/+bug/1794399">https://bugs.launchpad.net/cloud-init/+bug/1794399</a></p> -<p>16:41 <code>&lt;ubot5&gt;</code> Ubuntu bug 1794399 in cloud-init "cloud-init dhcp_discovery() crashes on preprovisioned RHEL 7.6 VM in Azure" [Undecided,New]</p> -<p>16:41 <code>&lt;paulmey&gt;</code> this is a stopgap fix until we have a pure-python dhcp client</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> it's been a push for the Cosmic release for us, racing to get things sorted, but I think we are on the other side of any fires now :)</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> ahh checking that bug</p> -<p>16:42 <code>&lt;paulmey&gt;</code> :-) good to hear that</p> -<p>16:42 <code>&lt;paulmey&gt;</code> it's basically just some more robustness around the handling of dhclient execution</p> -<p>16:44 <code>&lt;paulmey&gt;</code> it reproed very reliably on RHEL with reprovisioning (changing network etc., maybe slower/faster dhcp response?), but pretty unreproducible outside of that...</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> paulmey: jason made reference to a patch, but I don't see it linked to the bug.... I'm checking the review queue now</p> -<p>16:44 <code>&lt;paulmey&gt;</code> we saw cloud-init killing or trying to kill the initial process (which has already finished after the util exec)</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> was that bug just a request for us to make cloud-init more resilient in light of forking, or a request to accept a patch</p> -<p>16:45 <code>&lt;paulmey&gt;</code> let me link the patch... once I find it :-)</p> -<p>16:45 <code>&lt;paulmey&gt;</code> give me a minute</p> -<p>16:46 * blackboxsw documents the link for the meeting bot</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/+bug/1794399">https://bugs.launchpad.net/cloud-init/+bug/1794399</a></p> -<p>16:46 <code>&lt;ubot5&gt;</code> Ubuntu bug 1794399 in cloud-init "cloud-init dhcp_discovery() crashes on preprovisioned RHEL 7.6 VM in Azure" [Undecided,New]</p> -<p>16:46 * blackboxsw Sort and review azure RHEL branch related to ephemeral dhcp handling of dhclient <a href="https://bugs.launchpad.net/cloud-init/+bug/1794399">https://bugs.launchpad.net/cloud-init/+bug/1794399</a></p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> #action Sort and review azure RHEL branch related to ephemeral dhcp handling of dhclient <a href="https://bugs.launchpad.net/cloud-init/+bug/1794399">https://bugs.launchpad.net/cloud-init/+bug/1794399</a></p> -<p>16:47 * meetingology Sort and review azure RHEL branch related to ephemeral dhcp handling of dhclient <a href="https://bugs.launchpad.net/cloud-init/+bug/1794399">https://bugs.launchpad.net/cloud-init/+bug/1794399</a></p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> yeah, I wonder if now that 18.4 is cut and released if we want to start banging the drum to get our scapy-based dhclient solution landed in cloud-init proper so we don't have to patchup the ephemeral dhcp work in cloud-init.</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> while you look paulmey, I'll make sure we talk at our standups about what we can do with cloud-init's own dhcp-discovery so we don't have to handle different distro implementations of dhclient. The sandboxed dhclient solution we have felt dirty in the first place.</p> -<p>16:51 <code>&lt;paulmey&gt;</code> yar... I can't find a reference to it in my mails... I'll need to circle back with Jason. I prototyped the patch and he write some unit tests. I know it's somewhere, just not exactly where...</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> our only concern I thought with using scapy was adding the additional package dependency, (which we wouldn't be able to get released back into Ubuntu Xenial Bionic or Cosmic). But, we can resolve to come of with an approach for the nearterm</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> paulmey: sounds good. :) care if I add a virtual action item for you too to the meeting minutes</p> -<p>16:52 <code>&lt;paulmey&gt;</code> Sure, no problem</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> at least it'll guarantee we make progress before next meeting</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> #action paulmey to dig up reference to proposed patch for <a href="https://bugs.launchpad.net/cloud-init/+bug/1794399">https://bugs.launchpad.net/cloud-init/+bug/1794399</a></p> -<p>16:52 * meetingology paulmey to dig up reference to proposed patch for <a href="https://bugs.launchpad.net/cloud-init/+bug/1794399">https://bugs.launchpad.net/cloud-init/+bug/1794399</a></p> -<p>16:52 <code>&lt;ubot5&gt;</code> Ubuntu bug 1794399 in cloud-init "cloud-init dhcp_discovery() crashes on preprovisioned RHEL 7.6 VM in Azure" [Undecided,New]</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> thanks</p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> paulmey: are there other azure related discussions/features that are collecting dust with us that you know of?</p> -<p>16:54 <code>&lt;paulmey&gt;</code> not yet collecting dust, but I know that Sushant Sharma is going to be coming with some networking-related updates for pre-provisioning like we discussed at the summit</p> -<p>16:54 <code>&lt;paulmey&gt;</code> he's testing those on real systems right now</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> I know hyperv reporting feature is functional in cloud-init now. and that folks are instrumenting changes in images to support that.</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> ahh right. good to hear</p> -<p>16:55 <code>&lt;paulmey&gt;</code> we're also talking to SUSE this week to see what the next steps are to get cloud-init functional on Azure</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> ohh neat!</p> -<p>16:56 <code>&lt;paulmey&gt;</code> I know we still have some work items, but we're prototyping some stuff to get ahead of some testing work</p> -<p>16:56 <code>&lt;paulmey&gt;</code> funny thing is that I'm hardly doing any of this work. :-)</p> -<p>16:56 <code>&lt;paulmey&gt;</code> good to see more and more people at MS doing work on cloud-init</p> -<p>16:57 <code>&lt;blackboxsw&gt;</code> heh, juggling a lot I'm sure. yeah it is nice to see more devs involved</p> -<p>16:58 <code>&lt;smoser&gt;</code> paulmey: thats great to hear wrt suse</p> -<p>16:58 <code>&lt;paulmey&gt;</code> ok, cool. I'll follow up with Jason and circle back. If anything else comes to fruition before the 29th, I'll send people here to evangalize</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> perfect. Thanks again paulmey</p> -<p>16:59 <code>&lt;smoser&gt;</code> and /me agrees it'd be good to have a dhclient in cloud-init for what we need it for. scapy or other.</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> think I'll wrap up this meeting for today</p> -<p>16:59 <code>&lt;paulmey&gt;</code> (although it's always nice to talk to you guys... feels good being able to say was on IRC this week... :-P)</p> -<p>16:59 <code>&lt;paulmey&gt;</code> sgtm</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> heh, take care</p> -<p>16:59 <code>&lt;paulmey&gt;</code> ttyl</p> -<p>17:00 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-09-25T16:05:00+00:002018-09-25T16:05:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-09-25:/status-2018-09-25.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 25 Sep at 16:05 &mdash; 17:10 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-09-25-16.05.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-09-25-16.05.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:09.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 25 Sep at 16:05 &mdash; 17:10 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-09-25-16.05.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-09-25-16.05.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:09.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:10.</p> -<h3>In-Progress development</h3> -<p>The discussion about "In-Progress development" started at 16:15.</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>18.4 Release Schedule</h3> -<p>The discussion about "18.4 Release Schedule" started at 16:26.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~cloud-init-dev/cloud-init/+git/cloud-init/+ref/master/+activereviews">https://code.launchpad.net/~cloud-init-dev/cloud-init/+git/cloud-init/+ref/master/+activereviews</a> </li> -<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 16:31.</p> -<ul> -<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 (54)</li> -<li>ubot5 (6)</li> -<li>meetingology (3)</li> -<li>rharper (2)</li> -</ul> -<h2>Full Log</h2> -<p>16:05 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status meeting</p> -<p>16:05 <code>&lt;meetingology&gt;</code> Meeting started Tue Sep 25 16:05:46 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:05 <code>&lt;meetingology&gt;</code> </p> -<p>16:05 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> Hi cloud-init folks, time to kickoff our bi-weekly(ish) status meeting. As mentioned on the mailing list we pushed this meeting out until today so we could have a discussion about the 18.4 upstream release which is scheduled for this Thursday.</p> -<p>16:07 <code>&lt;blackboxsw&gt;</code> I just updated the topic to reflect the 18.4 release date, Sept 27th EOD.</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> for today's meeting we have the following agenda: Previous Actions, Recent Changes, In-progress development and 18.4 release discussion/office hours/ (~30 minutes)</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:09 * blackboxsw reviews our notes from Sept11 @ <a href="https://cloud-init.github.io">https://cloud-init.github.io</a></p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> No actions listed in previous meeting so we'll move to the next topic</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> Last week, we had some travel and planning discussions for cloud-init which took a few cycles out of our upstream landed content, but we were able to review and land a few items over the last couple weeks. Below is the list of changes that have landed in upstream cloud-init master. I expect we'll publish 18.4 release this week to Ubuntu Cosmic, so any changes below will be present in our next public release.</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - pylint: ignore warning assignment-from-no-return for _write_network</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - stages: Fix bug causing datasource to have incorrect sys_cfg.</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> (<a href="[https://bugs.launchpad.net/bugs/1787459](https://bugs.launchpad.net/bugs/1787459)">LP: #1787459</a>)</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - Remove dead-code _write_network distro implementations.</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - net_util: ensure static configs have netmask in translate_network result</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> [Thomas Berger] (<a href="[https://bugs.launchpad.net/bugs/1792454](https://bugs.launchpad.net/bugs/1792454)">LP: #1792454</a>)</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - Fall back to root:root on syslog permissions if other options fail.</p> -<p>16:12 <code>&lt;ubot5&gt;</code> Ubuntu bug 1787459 in cloud-init (Ubuntu) "datasource.sys_cfg gets different values in local stage and after." [Medium,Confirmed]</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> [Robert Schweikert]</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - tests: Add mock for util.get_hostname. [Robert Schweikert] (<a href="[https://bugs.launchpad.net/bugs/1792799](https://bugs.launchpad.net/bugs/1792799)">LP: #1792799</a>)</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - ds-identify: doc string cleanup.</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - OpenStack: Support setting mac address on bond.</p> -<p>16:12 <code>&lt;ubot5&gt;</code> Ubuntu bug 1792454 in cloud-init "Network configuration broken for some distributions with OpenNebula, EC2, Azure" [High,Fix committed]</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> [Fabian Wiesel] (<a href="[https://bugs.launchpad.net/bugs/1682064](https://bugs.launchpad.net/bugs/1682064)">LP: #1682064</a>)</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - bash_completion/cloud-init: fix shell syntax error.</p> -<p>16:12 <code>&lt;ubot5&gt;</code> Ubuntu bug 1792799 in cloud-init "Host environment bleeds into test for mirror access testing" [Undecided,Fix committed]</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - EphemeralIPv4Network: Be more explicit when adding default route.</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> (<a href="[https://bugs.launchpad.net/bugs/1792415](https://bugs.launchpad.net/bugs/1792415)">LP: #1792415</a>)</p> -<p>16:12 <code>&lt;ubot5&gt;</code> Ubuntu bug 1682064 in cloud-init "cloud-init should support config bond mac address " [Medium,Fix committed]</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - OpenStack: support reading of newer versions of metdata.</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - OpenStack: fix bug causing 'latest' version to be used from network.</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> (<a href="[https://bugs.launchpad.net/bugs/1792157](https://bugs.launchpad.net/bugs/1792157)">LP: #1792157</a>)</p> -<p>16:12 <code>&lt;ubot5&gt;</code> Ubuntu bug 1792415 in cloud-init (Ubuntu) "WARNINGs and failures in log on OVH public cloud" [Medium,Confirmed]</p> -<p>16:12 <code>&lt;ubot5&gt;</code> Ubuntu bug 1792157 in cloud-init (Ubuntu) "cloud-init uses openstack latest version due to decoding bug" [Medium,In progress]</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> Thank you again Robert, Thomas and Fabian for continued contributions to cloud-init upstream. Things are looking really good for the upcoming release</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> #topic In-Progress development</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> We are beating the drum toward the 18.4 release, as such, we are going to focus more on low-risk changes and bug fixes as we close in on the 18.4 upstream cutoff.</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> All of the work we have planned lives over on our trello board.</p> -<p>16:18 <code>&lt;blackboxsw&gt;</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:19 <code>&lt;blackboxsw&gt;</code> In our doing and review lane I expect we'll have a couple branches landing for standardizing and generalizing /run/cloud/instance-data.json on all clouds, and a couple of new cloud-init CLI commands 'cloud-init query' and 'cloud-id' to surface standardized instance-data on any cloud platform</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> post-18.4 release rharper has been doing some excellent work adding hotplug network support to OpenStack. I expect we'll be landing his branches shortly after we cut 18.4</p> -<p>16:21 <code>&lt;rharper&gt;</code> blackboxsw: thanks; it's been super interesting</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> this should give us an excellent example of reacting to changing metadata on a given platform, which hopefully other datasources will be able to adopt.</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> As far as additional content for the release, I'll also be circling an email around to the mailing list (cloud-init@lists.launchpad.net ) to describe existing instance data that cloud-init publishes. We are looking for input on common instance meta data that folks would like to see generalized across clouds.</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> I think about wraps up our current dev tasks.</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> #topic 18.4 Release Schedule</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> As mentioned earlier, we would like to cut 18.4 upstream release and tag it at end of day on Thursday, Sept 27th.</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> We will be looking at the active review queue for any branches with the 'Needs review' status.</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~cloud-init-dev/cloud-init/+git/cloud-init/+ref/master/+activereviews">https://code.launchpad.net/~cloud-init-dev/cloud-init/+git/cloud-init/+ref/master/+activereviews</a></p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> If there are branches or bugs that you think need attention, please don't hesitate to mail the mailing list, or ping in this channel to get attention</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> After thursday, we'll be performing some additional manual and automated integration tests and we will plan on publishing 18.4 to Ubuntu Cosmic.</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> As a service, we also will publish that 18.4 release to the following copr repo for those centos-inclined individuals :)</p> -<p>16:30 <code>&lt;blackboxsw&gt;</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:30 <code>&lt;blackboxsw&gt;</code> For each upstream release we sync that release to the 'el-testing' repo.</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> Daily upstream snapshots are also available at <a href="https://copr.fedorainfracloud.org/coprs/g/cloud-init/cloud-init-dev/">https://copr.fedorainfracloud.org/coprs/g/cloud-init/cloud-init-dev/</a></p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> #topic Office hours (next ~30 mins)</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> I think that about wraps the fire hose of content for our meeting. For the next 30 mins we should have eyes on this channel to discuss the finer points of life as well as anything cloud-init related. Bring your bugs, gripes, requests, reviews and/or discussions and we'll get a good answer for you.</p> -<p>16:33 * blackboxsw is going to hitup the review queue at the moment so see if there are some cloud-init branches we can clear out.</p> -<p>16:45 <code>&lt;rharper&gt;</code> +1</p> -<p>17:09 <code>&lt;blackboxsw&gt;</code> ok that about wraps it for today.</p> -<p>17:10 <code>&lt;blackboxsw&gt;</code> minutes will be published to the following link. Thanks again folks! See you next time</p> -<p>17:10 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io">https://cloud-init.github.io</a></p> -<p>17:10 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-09-04T16:08:00+00:002018-09-04T16:08:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-09-04:/status-2018-09-04.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 04 Sep at 16:08 &mdash; 17:01 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-09-04-16.08.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-09-04-16.08.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> - <strong>LINK</strong>: <a href="https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin">https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin</a> - <strong>LINK</strong>: <a href="https://powersj.github.io/post/cloud-init-summit18/">https://powersj.github.io/post …</a></p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 04 Sep at 16:08 &mdash; 17:01 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-09-04-16.08.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-09-04-16.08.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> - <strong>LINK</strong>: <a href="https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin">https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin</a> - <strong>LINK</strong>: <a href="https://powersj.github.io/post/cloud-init-summit18/">https://powersj.github.io/post/cloud-init-summit18/</a> </p> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:22.</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>?menu=filter&amp;filter=cloud-init </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/353740">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/353740</a> </li> -</ul> -<h3>Office Hource (next ~30 mins)</h3> -<p>The discussion about "Office Hource (next ~30 mins)" started at 16:30.</p> -<h3>Active review queue scrub (and open discussion/office hours)</h3> -<p>The discussion about "Active review queue scrub (and open discussion/office hours)" started at 16:41.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~praween/cloud-init/+git/cloud-init/+merge/353733">https://code.launchpad.net/~praween/cloud-init/+git/cloud-init/+merge/353733</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904</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 (60)</li> -<li>smoser (8)</li> -<li>meetingology (3)</li> -<li>marcoceppi (2)</li> -<li>ubot5 (1)</li> -</ul> -<h2>Full Log</h2> -<p>16:08 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status meeting</p> -<p>16:08 <code>&lt;meetingology&gt;</code> Meeting started Tue Sep 4 16:08:21 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:08 <code>&lt;meetingology&gt;</code> </p> -<p>16:08 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:08 <code>&lt;marcoceppi&gt;</code> rharper: oddly enough, that didn't work. root wasn't set</p> -<p>16:08 <code>&lt;marcoceppi&gt;</code> I'll bother you all after the meeting</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> or during marcoceppi :) sorry for the delay folks, I lost internet for a bit and just got it back up.</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> let's kickoff the bi-weekly status meeting and see what discussion we have for today</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> Our agenda is the following: Previous Actions, Recent Changes, In-progress development and office hours (~30 minutes)</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> the only logged action per last meeting was the following:</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> rharper/blackboxsw close out on this review before cloud-init summit <a href="https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742">https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742</a></p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> we were able to land that branch at the cloud-init summit 2 weeks ago and also landed a followup fix for a lock race condition related to that changeset</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> so we can cross that one off the list</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> .... and for those following from home. our meeting minutes from the last status meeting are here</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> Also generically we had a number of action items that came out of our Seattle cloud-init summit with various cloud and distribution partners. Our team will be having a review meeting to discuss some of those actions/decisions and ultimately convert them into trello work items on our board</p> -<p>16:13 <code>&lt;blackboxsw&gt;</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:16 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> Over the last couple weeks Microsoft hosted a very producting Cloud-init Summit conference in Seattle. A number of clouds and distribution vendors participated to set goals for the cloud-init upstream project. powersj wrote up a nice post to capture some of that work. Thank you all for partipating and helping to improve cloud-init</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> #link <a href="https://powersj.github.io/post/cloud-init-summit18/">https://powersj.github.io/post/cloud-init-summit18/</a></p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> also the following changes landed upstream:</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> - Add unit tests for config/cc_ssh.py [Francis Ginther]</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> - Fix the built-in cloudinit/tests/helpers:skipIf</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> - read-version: enhance error message [Joshua Powers]</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> - hyperv_reporting_handler: simplify threaded publisher</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> - VMWare: Fix a network config bug in vm with static IPv4 and no gateway.</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> [Pengpeng Sun] (LP: #1766538)</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> - logging: Add logging config type hyperv for reporting via Azure KVP</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> [Andy Liu]</p> -<p>16:21 <code>&lt;ubot5&gt;</code> Launchpad bug 1766538 in cloud-init (Ubuntu) "network customization with cloud-init does not work on Ubuntu18.04 Beta2 Server" [Medium,Confirmed] <a href="https://launchpad.net/bugs/1766538">https://launchpad.net/bugs/1766538</a></p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> as always, check our board if there are questions about what we are working on the cloud-init side of the house. any cloud-init cards will have a cloud-init label</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #link <a href="https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin">https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin</a>?menu=filter&amp;filter=cloud-init</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> we are working a couple of fixes for Oracle as well as the following features that could be interesting to folks:</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> - the ability to use jinja templating in cloud-config or user-scripts to reference any standardized instance meta data cloud-init consumes</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> - allowing new ssh user config in #cloud-config to specify a ssh-redirect-user, which would allow someone to disable an existing ssh user and provide a redirect message mentioning which username is the preferred default user</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - ryan is working on refactoring the sysconfig renderer align multiple distros, so that we don't have slightly different implementations in cloud-init for each distribution</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/353740">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/353740</a></p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> beyond that, there a number of new contibutions that have been generated by some of the amazon folks that we plan on reviewing and landing for better amazon linux support</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> thanks again for all the good work. I think we'll transition to the open forum for any discussion/feature/bug work.</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> #topic Office Hource (next ~30 mins)</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> we'll have eyes on this channel for the next 30 mins. any topic is acceptable; big or small. Bugs, discussions, features, complaints etc.</p> -<p>16:31 <code>&lt;smoser&gt;</code> o/</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> sorry for the interrupt earlier :)</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> Since we have a clear discussion docket for office hours... At the summit we decided maybe it would be a good idea to try reviewing our active review queue to keep the momentum going there and avoid stale branches sitting unresolved for a while.</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> smoser: rharper you gents up for taking a swing at our review queue in this forum to see if we can prioritize what needs landing/response etc?</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> #topic Active review queue scrub (and open discussion/office hours)</p> -<p>16:42 <code>&lt;smoser&gt;</code> sure.</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> I wanted to see if we could land Praveen's branch for Amazon linux support.</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~praween/cloud-init/+git/cloud-init/+merge/353733">https://code.launchpad.net/~praween/cloud-init/+git/cloud-init/+merge/353733</a></p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> their CI needs a new makefile target "sources"</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> I suggested that maybe they add that functionality into ./packages/brpm instead of just the commands on the cli</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> since we use brpm in our ci too. ....</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> Praveen had agreed at the summit to make some changes to extend brpm with a new cmdline option to do this work. But I don't see anything pushed. I'd like to mark this work in progress and comment to that affect. sound good?</p> -<p>16:46 <code>&lt;smoser&gt;</code> blackboxsw: that sounds good</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> smoser: ok <a href="https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/354001">https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/354001</a> I'll grab today after this meeting so we can land all the leaky unit tests. geez man</p> -<p>16:49 * blackboxsw grabs the review slot</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> I believe robert's branch is tabled until ryan's sysconfig branch is landed</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904</a></p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> ^ should we mark this 'work in progress' as it's blocked? or maybe just leave it in the active queue</p> -<p>16:51 <code>&lt;smoser&gt;</code> blackboxsw: your needs information still stands right?</p> -<p>16:51 <code>&lt;smoser&gt;</code> lets move it to work-in-progress and ask for response and also ask if it is sitll necessary (unless you know that it is or is not)</p> -<p>16:52 <code>&lt;smoser&gt;</code> and suggest that it will need to be re-worked.</p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> smoser: that sounds good. my 'needs information' on that is resolved/read/discussed already. so I should abstain for the moment until the rework</p> -<p>16:57 <code>&lt;blackboxsw&gt;</code> ok couple more minutes... any additional reviews we should look at in earnest now?</p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> I kinda want to hold on <a href="https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392">https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392</a> until we have our summit retro meeting today</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> here's a short one. <a href="https://code.launchpad.net/~otubo/cloud-init/+git/cloud-init/+merge/353436.">https://code.launchpad.net/~otubo/cloud-init/+git/cloud-init/+merge/353436.</a> should we mark this 'work in progress' until smoser's review comments are addressed and unit tests added?</p> -<p>16:59 <code>&lt;smoser&gt;</code> blackboxsw: yeah. i'll do that.</p> -<p>17:00 <code>&lt;blackboxsw&gt;</code> ok thanks. and I think that'll about wrap it for today. If we don't resolve the other community reviews by next status meeting, we can continue chipping away at this queue then.</p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> I'll post the minutes to cloudinit.github.io just after this.</p> -<p>17:01 <code>&lt;smoser&gt;</code> blackboxsw: i'm loking at rharper's mp now for the system config</p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> ok I'll get your review on <a href="https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/354001">https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/354001</a> now</p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-08-20T16:09:00+00:002018-08-20T16:09:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-08-20:/status-2018-08-20.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 20 Aug at 16:09 &mdash; 17:04 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-08-20-16.09.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-08-20-16.09.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:13.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 20 Aug at 16:09 &mdash; 17:04 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-08-20-16.09.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-08-20-16.09.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:13.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:13.</p> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:21.</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>Office Hource (next ~30 mins)</h3> -<p>The discussion about "Office Hource (next ~30 mins)" started at 16:27.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742">https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742</a> </li> -<li><strong>ACTION</strong>: rharper/blackboxsw close out on this review before cloud-init summit <a href="https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742">https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742</a></li> -</ul> -<h2>Vote results</h2> -<h2>Action items, by person</h2> -<ul> -<li>blackboxsw</li> -<li>rharper/blackboxsw close out on this review before cloud-init summit <a href="https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742">https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742</a></li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (39)</li> -<li>ubot5 (5)</li> -<li>paulmey (5)</li> -<li>meetingology (4)</li> -</ul> -<h2>Full Log</h2> -<p>16:09 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status meeting</p> -<p>16:09 <code>&lt;meetingology&gt;</code> Meeting started Mon Aug 20 16:09:08 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:09 <code>&lt;meetingology&gt;</code> </p> -<p>16:09 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> For those around, let's kickoff another cloud-init status meeting. Feel free to interrupt as we go through the agenda for today.</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> agenda: Previous Actions, Recent Changes, In-progress development and office hours (~30 minutes)</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> nothing to speak of here as far as I recall.</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> We have recently landed the following content in tip of cloud-init over the last 2 weeks</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> - Add datasource Oracle Compute Infrastructure (OCI).</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> - azure: allow azure to generate network configuration from IMDS per boot.</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> - Scaleway: Add network configuration to the DataSource [Louis Bouchard]</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> - docs: Fix example cloud-init analyze command to match output.</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> [Wesley Gao]</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> - netplan: Correctly render macaddress on a bonds and bridges when</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> provided. (LP: #1784699)</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> - tools: Add 'net-convert' subcommand command to 'cloud-init devel'.</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> - redhat: remove ssh keys on new instance. (LP: #1781094)</p> -<p>16:14 <code>&lt;ubot5&gt;</code> Launchpad bug 1784699 in cloud-init "cloud-init not setting mac address for bond or bridge in bionic" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1784699">https://launchpad.net/bugs/1784699</a></p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> - Use typeset or local in profile.d scripts. (LP: #1784713)</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> - OpenNebula: Fix null gateway6 [Akihiko Ota] (LP: #1768547)</p> -<p>16:15 <code>&lt;ubot5&gt;</code> Launchpad bug 1781094 in cloud-init "cloud.cfg.tmpl should not include "ssh_deletekeys: 0"" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1781094">https://launchpad.net/bugs/1781094</a></p> -<p>16:15 <code>&lt;ubot5&gt;</code> Launchpad bug 1784713 in cloud-init (Ubuntu) "cloud-init profile.d files use bash-specific builtin "local"" [Low,Confirmed] <a href="https://launchpad.net/bugs/1784713">https://launchpad.net/bugs/1784713</a></p> -<p>16:15 <code>&lt;ubot5&gt;</code> Launchpad bug 1768547 in cloud-init (Ubuntu) "OpenNebula DataSource adds null gateway6 to netplan config" [Medium,Confirmed] <a href="https://launchpad.net/bugs/1768547">https://launchpad.net/bugs/1768547</a></p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> most notable is the new datasource for Oracle and Azure datasource now emitting network configuration per boot.</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> new Ubuntu cosmic images should contain 18.3-24-gf6249277-0ubuntu1 with the lastest patches</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> The team in general is perparing for the cloud-init summit conference which will be the second half of this week with cloud and distro vendors so we'll probably be landing a couple more branches in preparation for talks/demos there.</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> <em>preparing</em> rather</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> Our trello board is a good representation of any existing work we are "Doing"</p> -<p>16:24 <code>&lt;blackboxsw&gt;</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:26 <code>&lt;blackboxsw&gt;</code> recently powersj has also moved our jenkins server around to a new network so there has been a good bit of work getting all things jenkins back up and running behind the new proxies/firewalls etc.</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> thanks for the heavy lift powersj</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> I think that wraps up all things cloud-init....</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> #topic Office Hource (next ~30 mins)</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> We'll have eyes on this channel for any quips, complaints, bug, feature or branch discussions for the next half hour</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> Otherwise, we'll be excited to see a few of you again in this year's cloud-init summit.\</p> -<p>16:28 <code>&lt;paulmey&gt;</code> Hi all, I'd like to request a review for this MP: <a href="https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742">https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742</a> (attached to LP: #1722959)</p> -<p>16:28 <code>&lt;ubot5&gt;</code> Launchpad bug 1722959 in cloud-init "Implement Key-Value Pair Telemetry for Azure" [Undecided,In progress] <a href="https://launchpad.net/bugs/1722959">https://launchpad.net/bugs/1722959</a></p> -<p>16:29 <code>&lt;paulmey&gt;</code> Hoping we can get this merged sometime soon. :-)</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> Hi paulmey thanks for the ping on this.</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742">https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742</a></p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> #action rharper/blackboxsw close out on this review before cloud-init summit <a href="https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742">https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742</a></p> -<p>16:30 * meetingology rharper/blackboxsw close out on this review before cloud-init summit <a href="https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742">https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742</a></p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> that has gotten dusty, thank you</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> I'll start a review in earnest now</p> -<p>16:31 <code>&lt;paulmey&gt;</code> Thanks. The dust is mostly mine... Andy has been working on this, but he's in a different time zone, so I'm still pushing it...</p> -<p>16:31 <code>&lt;paulmey&gt;</code> 😉</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> paulmey: I'll try spinning up an azure vm to test this out</p> -<p>16:34 <code>&lt;paulmey&gt;</code> let me know if you need anything</p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> ok thanks folks for tuning in. See you next time</p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-08-06T16:04:00+00:002018-08-06T16:04:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-08-06:/status-2018-08-06.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 06 Aug at 16:04 &mdash; 17:04 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-08-06-16.04.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-08-06-16.04.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:09.</p> -<ul> -<li><strong>ACTION</strong>: rharper …</li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 06 Aug at 16:04 &mdash; 17:04 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-08-06-16.04.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-08-06-16.04.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:09.</p> -<ul> -<li><strong>ACTION</strong>: rharper: and I need to review <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904</a></li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:11.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://jenkins.ubuntu.com/server/job/admin-lp-git-autoland/">https://jenkins.ubuntu.com/server/job/admin-lp-git-autoland/</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:19.</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="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348704">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348704</a> </li> -</ul> -<h3>Office Hource (next ~30 mins)</h3> -<p>The discussion about "Office Hource (next ~30 mins)" started at 16:25.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742.">https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742.</a> </li> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io">https://cloud-init.github.io</a> for meeting minutes</li> -</ul> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (59)</li> -<li>powersj (6)</li> -<li>meetingology (4)</li> -<li>ubot5 (1)</li> -<li>dpb1 (1)</li> -</ul> -<h2>Full Log</h2> -<p>16:04 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status meeting</p> -<p>16:04 <code>&lt;meetingology&gt;</code> Meeting started Mon Aug 6 16:04:05 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:04 <code>&lt;meetingology&gt;</code> </p> -<p>16:04 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:04 <code>&lt;dpb1&gt;</code> o/</p> -<p>16:04 <code>&lt;blackboxsw&gt;</code> hi folks, let's kickoff another cloud-init status meeting. Welcome back. Lot's of summer vacations disrupting our typical meeting schedule.</p> -<p>16:05 <code>&lt;blackboxsw&gt;</code> Our last meeting's minutes should be up on our github site</p> -<p>16:05 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>16:07 <code>&lt;blackboxsw&gt;</code> for this meeting we'll go through the following topics: previous actions, recent work, in-progress development and office hours</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> from our last meeting we had a couple of actions to carry over</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> we landed the folowing branch which added support for a datasource to re-write network config across each boot. <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348000">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348000</a></p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> #action rharper: and I need to review <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904</a></p> -<p>16:10 * meetingology rharper: and I need to review <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904</a></p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> the above is still a carryover</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> that's all for actions from last meeting</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> the following has landed in cloud-init tip:</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> * oracle: fix detect_openstack to report True on OracleCloud.com DMI data (LP: #1784685)</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> * tests: improve LXDInstance trying to workaround or catch bug.*</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> * update_metadata re-config on every boot comments and tests not quite right [Mike Gerdts]</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> * docs: note in rtd about avoiding /tmp when writing files</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> * ubuntu,centos,debian: get_linux_distro to align with platform.dist</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> * Fix boothook docs on environment variable name (INSTANCE_I -&gt;` INSTANCE_ID) (Marc Tamsky)</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> * update_metadata: a datasource can support network re-config every boot</p> -<p>16:13 <code>&lt;ubot5&gt;</code> Launchpad bug 1784685 in cloud-init "Oracle: cloud-init openstack local detection too strict for oracle cloud" [High,Fix committed] <a href="https://launchpad.net/bugs/1784685">https://launchpad.net/bugs/1784685</a></p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> * tests: drop salt-minion integration test</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> * Retry on failed import of gpg receive keys.</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> * tools: Fix run-container when neither source or binary package requested.</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> * docs: Fix a small spelling error (Oz N Tiram)</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> * tox: use simplestreams from git repository rather than bzr.</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> generally 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.</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> notably, we discovered a potential regression in Oracle datasource detection of their OpenStack implementation so that fix is queued for publish into xenial and bionic</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 18.3-9 is what folks are looking for. in xenial/bionic/cosmic for latest cloud-init containing all the above fixes</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> Also 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 acceptm</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> Also 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.</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> #link <a href="https://jenkins.ubuntu.com/server/job/admin-lp-git-autoland/">https://jenkins.ubuntu.com/server/job/admin-lp-git-autoland/</a></p> -<p>16:16 <code>&lt;powersj&gt;</code> yep that is live and with a recent fix to remove the extra "Author" line now</p> -<p>16:16 <code>&lt;powersj&gt;</code> hopefully it is saving blackboxsw, smoser, and rharper time ;)</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> powersj: can you explain what it does (so I don't have to type)</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> :)</p> -<p>16:17 <code>&lt;powersj&gt;</code> If a merge request is put in the "Approved" state, it will get test merged with the master branch</p> -<p>16:17 <code>&lt;powersj&gt;</code> the tests will run the same as during a review and verify that it can merge cleanly</p> -<p>16:18 <code>&lt;powersj&gt;</code> the commit message will get linted to verify it fits our format</p> -<p>16:18 <code>&lt;powersj&gt;</code> and if everything looks good, get merged in and pushed to master</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> thanks for that work powersj. it looks/works great so far.</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> All our current work is visible at the following trello board</p> -<p>16:19 <code>&lt;blackboxsw&gt;</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:20 <code>&lt;blackboxsw&gt;</code> I expect we'll have a couple of branches landed shortly in the following areas:</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> - smoser is working: A datasource specific to Oracle, because of their specific implementation of Openstack. Oracle will no longer use just stock DataSourceOpenStack.</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> - I</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> - I'm trying to wrap up a branch for Azure to write network data from their IMDS per-boot</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348704">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348704</a></p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - Joyent (SmartOS) per-boot network config review</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> - a couple netplan config option bugs for bionic ++</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> - and standardize instance-data sourcing in #cloud-config files (like referencing the hostname as detected from instance metadata)</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> I think that probably wraps it up for stuff in progress</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> anything I'm missing?</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> ... without further ado</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> #topic Office Hource (next ~30 mins)</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> eyes will float on this channel for any bug/feature discussions, review requests etc. any cloud-init topic is acceptable.</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> a 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.</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> while I'm at it, I think I'll set the topic to next status meeting time so folks know it's coming.</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> also 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.</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742.">https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742.</a></p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> it looks a bit noisy on the debug front with adding out/err messages for all subp calls, but other than that fairly straight forward.</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> looks like that's a wrap for today.</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io">https://cloud-init.github.io</a> for meeting minutes</p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> see you next time: 2 weeks from today</p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-07-02T16:05:00+00:002018-07-02T16:05:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-07-02:/status-2018-07-02.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 02 Jul at 16:05 &mdash; 17:02 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-07-02-16.05.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-07-02-16.05.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:09.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348000">https …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 02 Jul at 16:05 &mdash; 17:02 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-07-02-16.05.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-07-02-16.05.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:09.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348000">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348000</a> </li> -<li><strong>ACTION</strong>: haper/blackboxsw review <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904</a> [CARRYOVER]</li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:15.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://lists.launchpad.net/cloud-init/msg00164.html">https://lists.launchpad.net/cloud-init/msg00164.html</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:21.</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="https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/">https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348704">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348704</a> </li> -</ul> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 16:31.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </li> -</ul> -<h2>Vote results</h2> -<h2>Action items, by person</h2> -<ul> -<li>blackboxsw</li> -<li>haper/blackboxsw review <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904</a> [CARRYOVER]</li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (60)</li> -<li>meetingology (4)</li> -<li>ubot5 (3)</li> -<li>danMS_ (1)</li> -<li>mgerdts (1)</li> -</ul> -<h2>Full Log</h2> -<p>16:05 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status meeting</p> -<p>16:05 <code>&lt;meetingology&gt;</code> Meeting started Mon Jul 2 16:05:44 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:05 <code>&lt;meetingology&gt;</code> </p> -<p>16:05 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> hi folks, just kicking off another cloud-init status meeting to communicate the recent events in cloud-init land.</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> welcome to all, feel free to interrupt as we go through the agenda. As always cloud-init status minutes will live at the following url</p> -<p>16:07 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>16:07 <code>&lt;blackboxsw&gt;</code> The meeting agenda is as follows:</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> agenda: Previous Actions, Recent Changes, In-progress develepment and office hours (~30 minutes)</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> Last meeting we have a couple of actions to look over:</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> #ACTION blackboxsw carryover network hotplug vs network maintenance on reboot-only</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> #ACTION blackboxsw carryover network hotplug vs network maintenance on reboot-only [DONE]</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> we held multiple meetings, including discussion with mgerdts on a SmartOS solution for handling regenerating network configuration per-boot when a user selects this behavior</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> We have just landed a supporting branch in cloud-init tip to enable datasources to define what events (BOOT vs BOOT_NEW_INSTANCE) they will react to when generating network config.</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348000">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348000</a></p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> that should give a foundation for other datasources to write/change network config across boots, instead of allowing network config to remain static based on cloud-init's initial network configuration</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> the 2nd action ..</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> #ACTION haper/blackboxsw review <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904</a> [CARRYOVER]</p> -<p>16:14 * meetingology haper/blackboxsw review <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904</a> [CARRYOVER]</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> I'd like to carry this one over. We got a bit bogged down in SRU, CentOs stuff last week and we shold be able to get some eyes on this branch</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> I think that's it for actions.</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> Below is a list of changes landed in cloud-init tip or package publishing that has occured for the project:</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> * our 18.3 release was cut from tip if you caught the email on that mailing list</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> Congrats all for a great effort at improving quality and adding more datasource/cloud support</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> #link <a href="https://lists.launchpad.net/cloud-init/msg00164.html">https://lists.launchpad.net/cloud-init/msg00164.html</a></p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> ^ in case you didn't get the message</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> * we also publish 18.3 release into Ubuntu Cosmic and started a stable release update (SRU) to publish 18.3 in to xenial, artful, bionic</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> published*</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> expectations are that xenial, artful and bionic will have 18.3 after this week of testing</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> the remaining changes landed in tip are:</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - update_metadata: a datasource can support network re-config every boot</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> [Chad Smith]</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - tests: drop salt-minion integration test (LP: #1778737)</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - Retry on failed import of gpg receive keys.</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - tools: Fix run-container when neither source or binary package requested.</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - docs: Fix a small spelling error. [Oz N Tiram]</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - tox: use simplestreams from git repository rather than bzr.</p> -<p>16:20 <code>&lt;ubot5&gt;</code> Launchpad bug 1778737 in cloud-init "salt-minion test needs fixing" [Undecided,Fix committed] <a href="https://launchpad.net/bugs/1778737">https://launchpad.net/bugs/1778737</a></p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - release 18.3 [Chad Smith] (LP: #1777743)</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - docs: represent sudo:false in docs for user_groups config module</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> [Chad Smith]</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - Explicitly prevent <code>sudo</code> access for user module</p> -<p>16:20 <code>&lt;ubot5&gt;</code> Launchpad bug 1777743 in cloud-init "Release 18.3" [Undecided,Fix released] <a href="https://launchpad.net/bugs/1777743">https://launchpad.net/bugs/1777743</a></p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> [Jacob Bednarz] (LP: #1771468)</p> -<p>16:20 <code>&lt;ubot5&gt;</code> Launchpad bug 1771468 in cloud-init "Allow a way to explicitly disable sudo for a user" [Undecided,Fix released] <a href="https://launchpad.net/bugs/1771468">https://launchpad.net/bugs/1771468</a></p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> next topic</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> Our ongoing development is always listed publicly at the following trello board</p> -<p>16:22 <code>&lt;blackboxsw&gt;</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:23 <code>&lt;blackboxsw&gt;</code> We are going to be focused on SRU validation for Ubuntu this week which should take up the majority of the week.</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> At the end of this SRU process we will also rebuild centos binaries in our copr repo</p> -<p>16:23 <code>&lt;blackboxsw&gt;</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:24 <code>&lt;blackboxsw&gt;</code> so that folks in other envs will have access to latest bits if their distro/cloud doesn't have that update</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> Also, specfic to mgerdts and danMS_ there is a branch in progress for Azure support to regenerate network-config for all interfaces on each boot.</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348704">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348704</a></p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> mgerdts: might like it only as another example of a datasource managing network config across boots</p> -<p>16:26 <code>&lt;mgerdts&gt;</code> Thanks. Will look at that soon.</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> no prob, sorry for all the pings :)</p> -<p>16:26 <code>&lt;danMS_&gt;</code> will take a look too and spk to paulmey</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> also smoser is working on implementing an OCIC datasource (Oracle Cloud Infrastructure Classic)</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> think that wraps it up for this week.</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> there should be a couple of eyes on this channel for discusssions, questions, bug requests etc that might need a bit more attention.</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> again, thanks for tuning in and helping make cloud-init better!</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> meeting minutes will ultimately show at</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-06-18T16:08:00+00:002018-06-18T16:08:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-06-18:/status-2018-06-18.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 18 Jun at 16:08 &mdash; 17:23 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-06-18-16.08.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-06-18-16.08.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:11.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2018-05-29.html#status-2018-05-29">https://cloud-init.github.io/status-2018-05-29.html …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 18 Jun at 16:08 &mdash; 17:23 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-06-18-16.08.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-06-18-16.08.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:11.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2018-05-29.html#status-2018-05-29">https://cloud-init.github.io/status-2018-05-29.html#status-2018-05-29</a> </li> -<li><strong>ACTION</strong>: blackboxsw review distro dection and empty modules list [ DONE ] both robjo's branches are landed as of friday of last week.</li> -<li><strong>ACTION</strong>: blackboxsw carryover network hotplug vs network maintenance on reboot-only</li> -<li><strong>LINK</strong>: <a href="https://hackmd.io/NUUO4nndS4CXTItl8Rs6Nw">https://hackmd.io/NUUO4nndS4CXTItl8Rs6Nw</a> </li> -<li><strong>LINK</strong>: expectation is to get the foundation landed this week</li> -<li><strong>LINK</strong>: <a href="https://trello.com/c/Yp6VG2lP/837-eventpolicy-foundation-for-joyent-and-azure-coldplug">https://trello.com/c/Yp6VG2lP/837-eventpolicy-foundation-for-joyent-and-azure-coldplug</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+ref/feature/maintain-network-on-boot">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+ref/feature/maintain-network-on-boot</a> </li> -<li><strong>LINK</strong>: <a href="https://hackmd.io/aODzXfa_TOikNtYBLt8erA">https://hackmd.io/aODzXfa_TOikNtYBLt8erA</a> </li> -<li><strong>LINK</strong>: <a href="https://hackmd.io/aODzXfa_TOikNtYBLt8erA">https://hackmd.io/aODzXfa_TOikNtYBLt8erA</a> </li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:27.</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>Cloud-init 18.3 release</h3> -<p>The discussion about "Cloud-init 18.3 release" started at 16:36.</p> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 16:46.</p> -<ul> -<li><strong>ACTION</strong>: rhaper/blackboxsw review <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904</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>Action items, by person</h2> -<ul> -<li>blackboxsw</li> -<li>blackboxsw review distro dection and empty modules list [ DONE ] both robjo's branches are landed as of friday of last week.</li> -<li>blackboxsw carryover network hotplug vs network maintenance on reboot-only</li> -<li>rhaper/blackboxsw review <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904</a></li> -<li>robjo</li> -<li>blackboxsw review distro dection and empty modules list [ DONE ] both robjo's branches are landed as of friday of last week.</li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (83)</li> -<li>robjo (14)</li> -<li>rharper (10)</li> -<li>ubot5 (7)</li> -<li>smoser (7)</li> -<li>meetingology (6)</li> -</ul> -<h2>Full Log</h2> -<p>16:08 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status meeting</p> -<p>16:08 <code>&lt;meetingology&gt;</code> Meeting started Mon Jun 18 16:08:07 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:08 <code>&lt;meetingology&gt;</code> </p> -<p>16:08 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> Hi folks and welcome. We've got a big week this week as we are planning on a cloud-init release. So we will have an additional topic in today's agenda</p> -<p>16:09 <code>&lt;smoser&gt;</code> o/</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> it's been a few weeks, due to holiday schedules/travel, our agenda will be as following: Previous Actions, Recent Changes, In-progress develepment, cloud-init release 18.3 and office hours</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> last action items are listed in our meeting minutes at the following url:</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2018-05-29.html#status-2018-05-29">https://cloud-init.github.io/status-2018-05-29.html#status-2018-05-29</a></p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> #ACTION blackboxsw review distro dection and empty modules list [ DONE ] both robjo's branches are landed as of friday of last week.</p> -<p>16:12 * meetingology blackboxsw review distro dection and empty modules list [ DONE ] both robjo's branches are landed as of friday of last week.</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> that was a carryover from the meeting before I believe.</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> #ACTION blackboxsw carryover network hotplug vs network maintenance on reboot-only</p> -<p>16:13 * meetingology blackboxsw carryover network hotplug vs network maintenance on reboot-only</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> I think this was the only other unresolved action. Our team has had mutliple followup discussions internally and with mgerts from Joyent/SmartOs as well</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> smoser: and rharper drew up a hackmd doc related to this work here:</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> #link <a href="https://hackmd.io/NUUO4nndS4CXTItl8Rs6Nw">https://hackmd.io/NUUO4nndS4CXTItl8Rs6Nw</a></p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> We've come to a conclusion on a common near-term approach that will support cold-plug scenarios by allowing datasources to claim whether or not they will re-render networking on a boot event. This would allow cloud-init to react to network metadata changes across boot and enable/disable those devices accordingly</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> a WIP branch is available here</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> #link expectation is to get the foundation landed this week</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> and tracked in trello here</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> #link <a href="https://trello.com/c/Yp6VG2lP/837-eventpolicy-foundation-for-joyent-and-azure-coldplug">https://trello.com/c/Yp6VG2lP/837-eventpolicy-foundation-for-joyent-and-azure-coldplug</a></p> -<p>16:17 <code>&lt;robjo&gt;</code> Note that the metdata ins EC2 is "stale", AFIK, or at least some parts of the data are stale, i.e. they only get refreshed on instance restart</p> -<p>16:17 <code>&lt;rharper&gt;</code> is it instance restart or "re DHCP" ?</p> -<p>16:17 <code>&lt;rharper&gt;</code> ie, bounce the interface ?</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+ref/feature/maintain-network-on-boot">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+ref/feature/maintain-network-on-boot</a></p> -<p>16:18 <code>&lt;smoser&gt;</code> robjo: that is correct.</p> -<p>16:18 <code>&lt;robjo&gt;</code> so a re-read of the metadata on EC2 delivers no/maybe limited new information</p> -<p>16:18 <code>&lt;smoser&gt;</code> robjo: well, network information is updated.</p> -<p>16:18 <code>&lt;smoser&gt;</code> user-data is only updatable on stop -&gt;` start in ec2</p> -<p>16:18 <code>&lt;robjo&gt;</code> rharper: AFAIK new metadat gets pick up on instance restart</p> -<p>16:19 <code>&lt;rharper&gt;</code> ok</p> -<p>16:19 <code>&lt;robjo&gt;</code> I know the IID also only gets updated on stop-start</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> certainly in Azure that's the case. you have to stop the instance before changing attached network interfaces and then bring instance online again</p> -<p>16:20 <code>&lt;robjo&gt;</code> Yes, in Azure adding network interfaces is not dynamic</p> -<p>16:20 <code>&lt;robjo&gt;</code> meaning cannot happen while an instance is running</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> adding IPs in azure is an online thing, but even azure's network metadata is limited in that it doesn't tell you whether a network interface is static or dynamic. examples here:</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> <a href="https://hackmd.io/aODzXfa_TOikNtYBLt8erA">https://hackmd.io/aODzXfa_TOikNtYBLt8erA</a></p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> #link <a href="https://hackmd.io/aODzXfa_TOikNtYBLt8erA">https://hackmd.io/aODzXfa_TOikNtYBLt8erA</a></p> -<p>16:22 <code>&lt;robjo&gt;</code> Also for Azure there exists the "problem" of accelerated networking, i.e. SR-IOV</p> -<p>16:23 <code>&lt;robjo&gt;</code> when accelerated networking is on the SR-IOV interface gets the same MAC address as the "Synthetic nic"</p> -<p>16:23 <code>&lt;rharper&gt;</code> well, they "solved" it by having the kernel auto bond =/</p> -<p>16:23 <code>&lt;robjo&gt;</code> the SR-IOV interface gets bound to the synthetic nic in the kernel, that was a patch that went into the kernel 6-9 months ago</p> -<p>16:23 <code>&lt;rharper&gt;</code> AFAICT, the sriov device just magically comes and goes as it will</p> -<p>16:24 <code>&lt;rharper&gt;</code> so, one shouldn't worry about the silent bonding ... (I'm being a bit sarcastic here)</p> -<p>16:24 <code>&lt;robjo&gt;</code> yes, but the interface still shows up, so if output from "ip" command is read one has two devices with the same MAC address, only one of which should be configured</p> -<p>16:25 <code>&lt;rharper&gt;</code> we ignore any of the mlx4 driver devices</p> -<p>16:25 <code>&lt;rharper&gt;</code> yes they show up</p> -<p>16:25 <code>&lt;robjo&gt;</code> OK</p> -<p>16:25 <code>&lt;rharper&gt;</code> but the directive we got was to ignore them; and DHCP on the netvsc ones</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> ...so think that's all I had on action items from previous meeting.</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> shall we go to next topic?</p> -<p>16:26 <code>&lt;robjo&gt;</code> And that of course works until Msft gets a better HW deal from Intel or someone else for their network cards ;)</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> heh</p> -<p>16:26 <code>&lt;rharper&gt;</code> robjo: indeed</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> due to a couple vacations and some work travel it's been a slightly slower couple weeks below are the cloud-init changes that have gone in:</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - lxd: Delete default network and detach device if lxd-init created them.</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> (LP: #1776958)</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - openstack: avoid unneeded metadata probe on non-openstack platforms</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> [Chad Smith] (LP: #1776701)</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - stages: fix tracebacks if a module stage is undefined or empty</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> [Robert Schweikert] (LP: #1770462)</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - Be more safe on string/bytes when writing multipart user-data to disk.</p> -<p>16:28 <code>&lt;ubot5&gt;</code> Launchpad bug 1776958 in cloud-init "error creating lxdbr0." [Medium,Fix committed] <a href="https://launchpad.net/bugs/1776958">https://launchpad.net/bugs/1776958</a></p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> (LP: #1768600)</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - Fix get_proc_env for pids that have non-utf8 content in environment.</p> -<p>16:28 <code>&lt;ubot5&gt;</code> Launchpad bug 1776701 in cloud-init "ec2: xenial unnecessary openstack datasource probes during discovery" [High,Fix committed] <a href="https://launchpad.net/bugs/1776701">https://launchpad.net/bugs/1776701</a></p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> (LP: #1775371)</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - tests: fix salt_minion integration test on bionic and later [Chad Smith]</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - tests: provide human-readable integration test summary when --verbose</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> [Chad Smith]</p> -<p>16:28 <code>&lt;ubot5&gt;</code> Launchpad bug 1770462 in cloud-init "Allow empty stages" [Low,Fix committed] <a href="https://launchpad.net/bugs/1770462">https://launchpad.net/bugs/1770462</a></p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - tests: skip chrony integration tests on lxd running artful or older</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> [Chad Smith]</p> -<p>16:28 <code>&lt;ubot5&gt;</code> Launchpad bug 1768600 in cloud-init "UTF-8 support in User Data (text/x-shellscript) is broken" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1768600">https://launchpad.net/bugs/1768600</a></p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - test: add optional --preserve-instance arg to integraiton tests</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> [Chad Smith]</p> -<p>16:28 <code>&lt;ubot5&gt;</code> Launchpad bug 1775371 in cloud-init "cloud-init (18.2) fails on decoding proc1 env" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1775371">https://launchpad.net/bugs/1775371</a></p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - netplan: fix mtu if provided by network config for all rendered types</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> [Chad Smith] (LP: #1774666)</p> -<p>16:28 <code>&lt;ubot5&gt;</code> Launchpad bug 1774666 in netplan.io (Ubuntu Cosmic) "Bond interfaces stuck at 1500 MTU on Bionic" [Undecided,Confirmed] <a href="https://launchpad.net/bugs/1774666">https://launchpad.net/bugs/1774666</a></p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - tests: remove pip install workarounds for pylxd, take upstream fix.</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - subp: support combine_capture argument.</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - tests: ordered tox dependencies for pylxd install [Chad Smith]</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - util: add get_linux_distro function to replace platform.dist</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> [Robert Schweikert] (LP: #1745235)</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - pyflakes: fix unused variable references identified by pyflakes 2.0.0.</p> -<p>16:28 <code>&lt;ubot5&gt;</code> Launchpad bug 1745235 in cloud-init "distribution detection" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1745235">https://launchpad.net/bugs/1745235</a></p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> thanks again Robert for the contributions here getting cloud-init in order :)</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> we've also just pushed a release of cloud-init tip into Ubuntu Cosmic.</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> so all latest changes are in the development series</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> I think that about wraps it</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> #topc In-progress Development</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> As always, we track ongoing work publicly at</p> -<p>16:32 <code>&lt;blackboxsw&gt;</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:33 <code>&lt;blackboxsw&gt;</code> we've got some cold-plug network rendering handling that will be queued for this week, mgerts is working on enabling cold-plug network rendering support on boot for SmartOS, and there is a followup for Azure to do the same</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> cloud-init squad is going to be setting up an SRU into Xenial, Artful and Bionic this week as well</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> to sync latest qualified cloud-init into those Ubuntu series</p> -<p>16:35 <code>&lt;smoser&gt;</code> blackboxsw: thinking out loud..</p> -<p>16:35 <code>&lt;smoser&gt;</code> if we're going to release 18.3 on thursday</p> -<p>16:35 <code>&lt;smoser&gt;</code> might as well just hold off on sru until then</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> (wait on 18.3 release?)</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> yeha</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> yeah even</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> which brings us to our next topic</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> #topic Cloud-init 18.3 release</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> I hadn't seen any responsed to your email scott to cloud-init@lists.launchpad.net. Does anyone have any feature pressing that we'd like to get into this release</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> estimated release would be Thusday of this week</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> I'd whimsically like to include the azure cold-plug stuff, but that means getting those two branches in shape today for a thorough review/test cycle</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> s/whimsically/opportunitically/</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> heh I give up</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> did we want to pull this in? <a href="https://code.launchpad.net/~paul-meyer/cloud-init/+git/cloud-init/+merge/334989">https://code.launchpad.net/~paul-meyer/cloud-init/+git/cloud-init/+merge/334989</a></p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> If there are any pressing bugs or features that need to be in 18.3 we'd like to see them up for review by Wednesday of this week so that we can cut our upstream release. Feel free to send an email to the list cloud-init@lists.launchpad.net or this channel if your branch needs to get some eyes.</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> we'll SRU 18.3 then into Xenial, Artful and Bionic after a complete round of testing.</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:46 <code>&lt;robjo&gt;</code> :D After 18.3 but before the workshop: <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904</a></p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> Folks are around for further discussion on any cloud-init topics of interest</p> -<p>16:47 <code>&lt;robjo&gt;</code> then maybe at the workshop we can come up with a way to move SLES &amp; openSUSE to sysconfig renderer</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> good topic idea</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> #ACTION rhaper/blackboxsw review <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904</a></p> -<p>16:48 * meetingology rhaper/blackboxsw review <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904</a></p> -<p>17:22 <code>&lt;blackboxsw&gt;</code> thanks again folks. catch you next time.</p> -<p>17:23 <code>&lt;blackboxsw&gt;</code> minutes will be published to the link below</p> -<p>17:23 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>17:23 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-05-29T16:05:00+00:002018-05-29T16:05:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-05-29:/status-2018-05-29.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 29 May at 16:05 &mdash; 17:05 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-05-29-16.05.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-05-29-16.05.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:09.</p> -<h3>Recent Changes …</h3><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 29 May at 16:05 &mdash; 17:05 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-05-29-16.05.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-05-29-16.05.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:09.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:13.</p> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:19.</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="https://cloudinit.readthedocs.io/en/latest/topics/datasources.html">https://cloudinit.readthedocs.io/en/latest/topics/datasources.html</a>?highlight=instance-data#instance-data </li> -</ul> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 16:34.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://trello.com/c/5n5B8x23/802-cloud-init-query-standardized-json-information">https://trello.com/c/5n5B8x23/802-cloud-init-query-standardized-json-information</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/335290">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/335290</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 (118)</li> -<li>dmbaturin (20)</li> -<li>powersj (6)</li> -<li>dpb1 (5)</li> -<li>robjo (5)</li> -<li>ubot5 (4)</li> -<li>smoser (4)</li> -<li>meetingology (3)</li> -<li>rharper (2)</li> -</ul> -<h2>Full Log</h2> -<p>16:05 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status meeting</p> -<p>16:05 <code>&lt;meetingology&gt;</code> Meeting started Tue May 29 16:05:51 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:05 <code>&lt;meetingology&gt;</code> </p> -<p>16:05 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:06 <code>&lt;dpb1&gt;</code> dmbaturin: there will be a time for open questions in this meeting in just a few minutes. :)</p> -<p>16:06 <code>&lt;dpb1&gt;</code> so you will have the right people around</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> welcome folks to another cloud-init community status meeting, today's meeting delayed by one day due to US holiday. Next meeting will be June 11th. same time</p> -<p>16:07 <code>&lt;blackboxsw&gt;</code> I've added an actions topic to this meeting so we can wrap up or carry over any actions discussed last time</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> the topics will be Previous Actions, Recent Changes, In-progress Development, and Office Hours</p> -<p>16:08 <code>&lt;dmbaturin&gt;</code> Oh, cool.</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> As always notes will be posted to the following site</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> welcome dmbaturin good timing. :)</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:09 <code>&lt;dmbaturin&gt;</code> Yeah, I'm just in time it seems. ;)</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> 2 weeks ago we had a couple of followup items that needed some extra review:</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> * ACTION: blackboxsw review distro dection and empty modules list</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> * ACTION: robjo review existing chrony support in master per rharper's work</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> * ACTION: blackboxsw carryover network hotplug vs network maintenance on reboot-only</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> we did get through robjo's branches on distro <em>detection</em> and landed them\</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> and I know our team also discussed a potential approach to network hotplug vs network maintenance to better enable SmartOs folks who want to handle network config across reboots only</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> I think we decided we needed to draw up a quick shared document on a proposal which would allow for maintenance on reboots only vs true hotplug.</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> I'll carry over that action to write up a doc on this and send it to list by the next meeting</p> -<p>16:13 * blackboxsw blackboxsw write up short doc/branch on hotplug versus network maintenance on reboot for comment</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> and I believe robjo from SuSE was able to get through rharper's chrony support branch with a couple comments too</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> so no other actions from last meeting</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> this following content landed in cloud init tip over the last two weeks</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> - Do not use the systemd_prefix macro, not available in this environment</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> [Robert Schweikert]</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> - doc: Add config info to ec2, openstack and cloudstack datasource docs</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> [Chad Smith]</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> - Enable SmartOS network metadata to work with netplan via per-subnet</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> routes [Dan McDonald] (LP: #1763512)</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> - openstack: Allow discovery in init-local using dhclient in a sandbox.</p> -<p>16:14 <code>&lt;ubot5&gt;</code> Launchpad bug 1763512 in cloud-init "DataSourceSmartOS ignores sdc:routes" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1763512">https://launchpad.net/bugs/1763512</a></p> -<p>16:14 <code>&lt;powersj&gt;</code> lol!</p> -<p>16:14 <code>&lt;powersj&gt;</code> welcome back</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> heh looks like I got kicked for the paste :)</p> -<p>16:14 <code>&lt;powersj&gt;</code> blackboxsw: your last message was - openstack: Allow discovery in init-local using dhclient in a sandbox.</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> - tests: Avoid using https in httpretty, improve HttPretty test case.</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 (LP: #1771659)</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 - yaml_load/schema: Add invalid line and column nums to error message</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 [Chad Smith]</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 - Azure: Ignore NTFS mount errors when checking ephemeral drive</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 [Paul Meyer]</p> -<p>16:15 <code>&lt;ubot5&gt;</code> Launchpad bug 1771659 in cloud-init "unittests fail in OpenSuSE 42.3 with httpretty issues" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1771659">https://launchpad.net/bugs/1771659</a></p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> - packages/brpm: Get proper dependencies for cmdline distro.</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 - packages: Make rpm spec files patch in package version like in debs.</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 - tools/run-container: replace tools/run-centos with more generic.</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 - Update version.version_string to contain packaged version. (LP: #1770712)</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 - cc_mounts: Do not add devices to fstab that are already present.</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 [Lars Kellogg-Stedman]</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 - ds-identify: ensure that we have certain tokens in PATH. (LP: #1771382)</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 - tests: enable Ubuntu Cosmic in integration tests [Joshua Powers]</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 - read_file_or_url: move to url_helper, fix bug in its FileResponse.</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 - cloud_tests: help pylint [Ryan Harper]</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 - flake8: fix flake8 errors in previous commit.</p> -<p>16:15 <code>&lt;ubot5&gt;</code> Launchpad bug 1770712 in cloud-init "It would be nice if cloud-init provides full version in logs" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1770712">https://launchpad.net/bugs/1770712</a></p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 - typos: Fix spelling mistakes in cc_mounts.py log messages [Stephen Ford]</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 - tests: restructure SSH and initial connections [Joshua Powers]</p> -<p>16:15 <code>&lt;ubot5&gt;</code> Launchpad bug 1771382 in cloud-init "ds-identify: fails to recognize NoCloud datasource on boot cause it does not have /sbin in $PATH and thus does not find blkid" [Low,Fix committed] <a href="https://launchpad.net/bugs/1771382">https://launchpad.net/bugs/1771382</a></p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 - ds-identify: recognize container-other as a container, test SmartOS.</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> ok hopefully we ended on ds-identify</p> -<p>16:16 <code>&lt;dmbaturin&gt;</code> Yes, we did.</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> excellent. sorry for the paste, I'll send this out to cloud-init@lists.canonical.com a day before the next meeting so we don't have to IRC flood here</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> make that cloud-init@lists.launchpad.net</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> also we finished our SRU (stable release update) of cloud-init 18.2.27 to Bionic.</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> Ubuntu Cosmic currently reflects near tip of master 18.2.59</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> ok that's all for Recent Changes</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> anything I'm missing powersj ?</p> -<p>16:19 <code>&lt;powersj&gt;</code> I think you are good</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> We track upstreams progress publicly in trello</p> -<p>16:19 <code>&lt;blackboxsw&gt;</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:20 <code>&lt;blackboxsw&gt;</code> any blue labeled cards are cloud-init core work</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> we have been fixing a couple of bugs raised by our CI infrastructure on newer series of Ubuntu . currently a minor issue with salt minion on Bionic or later, and a couple of unit and integration test race conditions</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> big ticket items for cloud-init in the nearterm are metadata standardization across clouds, so cloud-init scripts/cloud-config template can source these cloud-provided values</p> -<p>16:24 <code>&lt;dmbaturin&gt;</code> Metadata standardization is something I really would like to see, if you need more hands for that, let me know.</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> the standardization of this instance-data will allow folks to script against any standard values provided to cloud-init in the same way on any cloud. Think hostname, fqdn, ip addrs, region name etc.</p> -<p>16:24 <code>&lt;dmbaturin&gt;</code> SSH keys too!</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> definitely dmbaturin I'll point you at a couple branches and what we're thinking</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> this conent will show up in /run/cloud-init/instance-data.json</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloudinit.readthedocs.io/en/latest/topics/datasources.html">https://cloudinit.readthedocs.io/en/latest/topics/datasources.html</a>?highlight=instance-data#instance-data</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> and will also be referenced via jinja template variables</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> and a cloud-init query CLI</p> -<p>16:28 <code>&lt;dmbaturin&gt;</code> The data will be updated whenever a change in the environment is made?</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> Also powersj will be working toward a common library for cloud-testing in the weeks to come which cloud-init integration tests will leverage to drive lxd, ec2, openstack azure etc for a cloud testing</p> -<p>16:29 <code>&lt;dmbaturin&gt;</code> Also, will it be possible to stop cloud-init from doing anything but writing that data and starting an external script to process it?</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> dmbaturin: some of that functionality will be handled in the hotplug work we are starting on. There will be operations that can be triggered by either a hotplug monitor on metadata or by cloud-init's CLI to say query from cache (the instance-data.json file) versus query fresh/update</p> -<p>16:30 <code>&lt;dmbaturin&gt;</code> I see.</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> dmbaturin: cloud-inits init-local or init-network stage is what calls "get_data" on the give datasources to collect and write that data to file. Spawning a script is generally done through runcmd which happens in cloud-init's 'final' stage. Trying to decouple them (and skipping the modules:config stage) is possible by altering /etc/cloud/cloud.cfg in a custom image to specify no modules in a given stage. Though it's not</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> really recommeded as most of the modules only do a quick sanity check to see if they are specifically enabled before trying to do any realy work</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> we try to keep boot time as fast as possible and cut out the fat where we can</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> if that's the concern you had</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> ok I think that's it for In-progress development we can move to office hours for all addtional discussion</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:35 <code>&lt;dmbaturin&gt;</code> No, boot time is not the primary concern here, my concern is how to ensure no module is trying to treat our system as if it was a normal Debian (which either doesn't work or can potentially get the system into an inconsistent state).</p> -<p>16:36 <code>&lt;dmbaturin&gt;</code> I guess if we are having a real meeting, it may be a good idea to formally introduce myself and the project. :)</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> All topics of interest to cloud-init development can be brought up and discussed here. If there are merge proposal that need attention, bugs that need work just bring them up here we should have a few sets of eyes on this channel to discuss and comment</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> sounds good dmbaturin introduce away :)</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> Chad smith, Canonical, one of the maintainers of cloud-init. We have a few others here (some on vacation). powersj rharper smoser dpb1 all canonical as well.</p> -<p>16:38 <code>&lt;dpb1&gt;</code> idk who blackboxsw is</p> -<p>16:38 <code>&lt;dpb1&gt;</code> he might be crazy</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> frequently we have other distribution developers and cloud devs here too (SuSE, RedHat, Microsoft Azure, SmartOS, VMWare )</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> heh, I'm just a bot</p> -<p>16:38 <code>&lt;dmbaturin&gt;</code> So, I'm one of the maintainers of the VyOS project (<a href="http://vyos.io">http://vyos.io</a>). It's a distro for routers and firewalls whose primary goal is to be just like hardware routers, but not tied to any hardware, which includes a single config file and unified CLI with a commit/rollback model, versioning, and cross-checks (e.g. if you try to reference a non-existent NIC in DHCP configuration, commit fails).</p> -<p>16:39 <code>&lt;dpb1&gt;</code> nice to meet you dmbaturin</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> ahh makes sense. So debian-based os kindof, which is why you'd want to lock down what modules run.</p> -<p>16:40 <code>&lt;dmbaturin&gt;</code> We support all major virtualization platforms now in the sense of including all required drivers and utilities, but autoconfiguration on cloud platforms is only supported for EC2 via a custom script, so we are looking to ways to support more clouds, ideally without doing the work that is already done, or at least contributing those general things into something where more people can benegit from it, not just us.</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> alos dmbaturin each config module claims what distro is supported in a distro property, so you could vet what modules you want to run, and only add VyOS to the list of compatible distros. Config modules all live in source at cloudinit/config/cc_*py.</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> but we can discuss that confuig module support (or not) once you dig in to look at supporting VyOS</p> -<p>16:42 <code>&lt;dmbaturin&gt;</code> Yes, I'm thinking how exactly it should be done.</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> dmbaturin: cloud-init's a pretty good choice for getting that cloud-support breadth for free</p> -<p>16:43 * robjo sorry I'm late</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> robjo: sorry for the late change from yesterday's normal meet time</p> -<p>16:43 <code>&lt;dmbaturin&gt;</code> The least intrusive option would be to indeed improve the instance data format, so that we can simply pass it to our own script, which is why I'm all for contributing to it.</p> -<p>16:43 <code>&lt;robjo&gt;</code> blackboxsw: noLnxDistro branch has not yet been merged</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> bah robjo ahh you're right</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> ok looks like you handled all review comments. I'll get it landed today</p> -<p>16:44 <code>&lt;smoser&gt;</code> powersj: <a href="https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/347060">https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/347060</a></p> -<p>16:44 * blackboxsw blackboxsw land <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/336794">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/336794</a> today</p> -<p>16:45 <code>&lt;smoser&gt;</code> you moved that to 'approved' i guess ?</p> -<p>16:45 <code>&lt;smoser&gt;</code> which meant the bot didnt comment (sorry blackboxsw ... interupted)</p> -<p>16:45 <code>&lt;dmbaturin&gt;</code> blackboxsw: Could you point me to the branches were the work on instance data is going on?</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> dmbaturin: here's one stale one I need to get back to this week. for enabling the template reference of instance-data.json content</p> -<p>16:46 <code>&lt;powersj&gt;</code> smoser: ah sorry you are right</p> -<p>16:47 <code>&lt;smoser&gt;</code> powersj: i'm going to land it anyway</p> -<p>16:47 <code>&lt;robjo&gt;</code> also I think emptyStageOK branch should be ready to go</p> -<p>16:47 <code>&lt;powersj&gt;</code> ok</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> hrm digging on the metadata branch.</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> dmbaturin: the trello card I'll be tying branches to is this one</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> #link <a href="https://trello.com/c/5n5B8x23/802-cloud-init-query-standardized-json-information">https://trello.com/c/5n5B8x23/802-cloud-init-query-standardized-json-information</a></p> -<p>16:48 <code>&lt;robjo&gt;</code> and <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904</a> should be on smoser plate</p> -<p>16:49 <code>&lt;robjo&gt;</code> or anyone else who wants to pick it up and get it merged, please</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/335290">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/335290</a></p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> ^ dmbaturin initial template handling thoughts.... I have to create at least 2 branches to standardize datasource class apis to make the metadata content easier to generalize and I can add your launchpad username to the review as I put them up</p> -<p>16:50 <code>&lt;rharper&gt;</code> smoser: re: hostname, yes, that's right; we probably could update the set_hostname docs to mention that detail w.r.t early hostname setting</p> -<p>16:51 <code>&lt;rharper&gt;</code> blackboxsw: sorry to interrupt</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> dmbaturin: what's your launchpad user name? (mine's chad.smith)</p> -<p>16:51 <code>&lt;dmbaturin&gt;</code> blackboxsw: dmbaturin</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> heh.</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> thx</p> -<p>16:51 <code>&lt;dmbaturin&gt;</code> I'm too predictable. ;)</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> yeah, I lost a bet on blackboxsw :)</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> robjo: okay adding that branch too for review/landing</p> -<p>16:51 * blackboxsw land <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904</a></p> -<p>16:52 * blackboxsw land <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/336794">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/336794</a></p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> alright, any other topics or discussions?</p> -<p>16:53 <code>&lt;dmbaturin&gt;</code> Trello is integrated with launchpad?</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> dmbaturin: nope, just easy to use for our agile workflow. And simple to cut-paste links, assign people, drag to different lanes as the work progresses</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> has a lot of github integraiton if you get the right plugins</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> we have some minimal tooling that can talk to lauchpad and inject cards, but that's hand-written, not part of trello product.</p> -<p>16:59 <code>&lt;dmbaturin&gt;</code> I mean, if you add my username there, will I get any notifications about card changes.</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> dmbaturin: I get emails from all trello card moves,changes. let's see</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> I can subscribe you to the card (you want the standardized json stuff?)</p> -<p>17:00 <code>&lt;dmbaturin&gt;</code> Yes.</p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> hrm can't find your user</p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> ahh</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> I think I invited you</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> and added your user to the card so you can watch it progress</p> -<p>17:05 <code>&lt;blackboxsw&gt;</code> ok I think that about wraps up our meeting for today</p> -<p>17:05 <code>&lt;blackboxsw&gt;</code> any parting shots?</p> -<p>17:05 <code>&lt;blackboxsw&gt;</code> I'll post these notes to our github project page</p> -<p>17:05 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>17:05 <code>&lt;blackboxsw&gt;</code> thanks again all</p> -<p>17:05 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-05-14T16:05:00+00:002018-05-14T16:05:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-05-14:/status-2018-05-14.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 14 May at 16:05 &mdash; 17:03 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-05-14-16.05.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-05-14-16.05.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:09.</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><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 14 May at 16:05 &mdash; 17:03 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-05-14-16.05.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-05-14-16.05.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:09.</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>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:19.</p> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 16:29.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://pastebin.ubuntu.com/p/266CyDt9gD/">https://pastebin.ubuntu.com/p/266CyDt9gD/</a> </li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/emptyStageOK">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/emptyStageOK</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/noLnxDistro">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/noLnxDistro</a> </li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bug/1745235">https://bugs.launchpad.net/cloud-init/+bug/1745235</a> </li> -<li><strong>ACTION</strong>: blackboxsw review distro dection and empty modules list</li> -<li><strong>ACTION</strong>: robjo review existing chrony support in master per rharper's work</li> -<li><strong>ACTION</strong>: blackboxsw carryover network hotplug vs network maintenance on reboot-only</li> -</ul> -<h2>Vote results</h2> -<h2>Action items, by person</h2> -<ul> -<li>blackboxsw</li> -<li>blackboxsw review distro dection and empty modules list</li> -<li>blackboxsw carryover network hotplug vs network maintenance on reboot-only</li> -<li>rharper</li> -<li>robjo review existing chrony support in master per rharper's work</li> -<li>robjo</li> -<li>robjo review existing chrony support in master per rharper's work</li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (73)</li> -<li>robjo (14)</li> -<li>ubot5 (9)</li> -<li>meetingology (6)</li> -<li>stanguturi (2)</li> -<li>rharper (1)</li> -</ul> -<h2>Full Log</h2> -<p>16:05 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status meeting</p> -<p>16:05 <code>&lt;meetingology&gt;</code> Meeting started Mon May 14 16:05:28 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:05 <code>&lt;meetingology&gt;</code> </p> -<p>16:05 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> welcome folks to another cloud-init status meeting. This forum is used to communicate the recent changes, current development efforts and host open office hours to help get quick discussion on bugs, branches or features of interest to anyone developing (or consuming) cloud-init.</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> We'll go through a couple of topics as usual (Recent changes, In-progress Development, Office Hours), if there are any additional topics needed just let me know.</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> We track our upstream work publicly on trello. Feel free to participate or ask questions about any feature work that is seen up there if there are concerns.</p> -<p>16:11 <code>&lt;blackboxsw&gt;</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:11 <code>&lt;blackboxsw&gt;</code> We have landed the following work items: beware the paste :)</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> * Completed release of 18.2 to Ubuntu Bionic, Artful, and Xenial</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> * Implement bash completion script for cloud-init command line</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> * Improved Softlayer datasource documentation</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> * net: Depend on iproute2's ip instead of net-tools ifconfig or route</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> * Accept-ra unset by default (LP: #1732002)</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> * Command collect-logs will only include most recent boot's journal (LP: #1766335)</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> * FreeBSD: Invoke growfs on ufs filesystems such that it does not prompt. (LP: #1404745)</p> -<p>16:11 <code>&lt;ubot5&gt;</code> Launchpad bug 1732002 in systemd (Ubuntu) "cloud images in lxc get ipv6 address" [Undecided,New] <a href="https://launchpad.net/bugs/1732002">https://launchpad.net/bugs/1732002</a></p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> * Azure: poll_imds fixes to only report 'ready' state once during pre-provisioning from Joshua Chan (LP: #1765214)</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> * DataSourceSmartOS: fix hang when metadata service is down from Mike Gerdts (LP: #1667735)</p> -<p>16:12 <code>&lt;ubot5&gt;</code> Launchpad bug 1766335 in cloud-init "Running cloud-init collect-logs inside a chroot is not possible" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1766335">https://launchpad.net/bugs/1766335</a></p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> * DataSourceSmartOS: change default fs on ephemeral disk from ext3 to ext4 from Mike Gerdts (LP: #1763511)</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> * pycodestyle: Fix invalid escape sequences in string literals</p> -<p>16:12 <code>&lt;ubot5&gt;</code> Launchpad bug 1404745 in cloud-init "cloud-init's growfs/resize fails with gpart dependency on FreeBSD" [Undecided,Fix committed] <a href="https://launchpad.net/bugs/1404745">https://launchpad.net/bugs/1404745</a></p> -<p>16:12 <code>&lt;ubot5&gt;</code> Launchpad bug 1765214 in cloud-init "Multiple success messages sent to Azure Fabric if reboot occurs during pre-provisioning" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1765214">https://launchpad.net/bugs/1765214</a></p> -<p>16:12 <code>&lt;ubot5&gt;</code> Launchpad bug 1667735 in cloud-init (Ubuntu Trusty) "cloud-init doesn't retry metadata lookups and hangs forever if metadata is down" [Medium,Confirmed] <a href="https://launchpad.net/bugs/1667735">https://launchpad.net/bugs/1667735</a></p> -<p>16:12 <code>&lt;ubot5&gt;</code> Launchpad bug 1763511 in cloud-init (Ubuntu) "DataSourceSmartOS should default to ext4" [Medium,Fix released] <a href="https://launchpad.net/bugs/1763511">https://launchpad.net/bugs/1763511</a></p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> A big thank you to community involvement again. Thanks jocha(Microsoft) and mgerdts(Joyent) for the recent branch work supporting Azure and SmartOS clouds respectively</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> We also went through another round of StableReleaseUpdates for Ubuntu on Xenial and Artful to pull in IBMCloud platform fixes. putting Xenial and artful at 18.2-4-g05926e48-0ubuntu~16.04.2 | ~17.10.2</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> I think that's about it for completed development...</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> There are a couple of items being worked actively at the moment:</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> * SRU of cloud-init tip into bionic (should land today or tomorrow) 18.2-27-g6ef92c98-0ubuntu1~18.04.1</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> * SmartOs datasource detection improvements</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> * Moving OpenStack datasource to get detected earlier at 'local' stange instead of 'network' stage using ephemeral dhcp client</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> * read_file_or_url fixes returing text content in all cases</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> * various upstream bug fixes</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> * powersj: is also investigating a move to a centralized library for our cloud testing.</p> -<p>16:29 <code>&lt;robjo&gt;</code> blackboxsw: w.r.t. Depend on iproute2's ip instead of net-tools ifconfig or route was this a merge of iproute2tools branch? I don't recall seeing a merge notification but am way behind in e-mail</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> think that about captures what upstream is working on. I think we can transition to office hours for ~30 mins for anyone to bring up ideas of interest</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> hi robjo, checking status there</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> I know we landed one branch on that topic</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> robjo: so we had a couple branches to packaging dependencies in ubuntu to call out iproute2 specifically as a hard package dependency.</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> robjo: and the code changes (which took in some of your branch content and review comments) landed in rev 6d48d265a0548a2dc23e587f2a335d4e38e8db90</p> -<p>16:32 <code>&lt;robjo&gt;</code> OK, so I can delete my branch</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> <a href="https://pastebin.ubuntu.com/p/266CyDt9gD/">https://pastebin.ubuntu.com/p/266CyDt9gD/</a></p> -<p>16:34 <code>&lt;robjo&gt;</code> thanks, so we'll get that in 18.3?</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> robjo: yes I think i marked you co-author on that branch and pulled in all your changes to cloudinit/config/cc_disable_ec2_metadata.py</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> 2</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> thanks again for that, sorry for the back and forth as I hadn't seen your original branch.</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> robjo: definitely in 18.3</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> it landed a week or two after the 18.2 cut.</p> -<p>16:35 <code>&lt;stanguturi&gt;</code> @blackboxsw, Can someone please provide inputs for the bug <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538</a> One of our team members has uploaded the necessary log files to the bug.</p> -<p>16:35 <code>&lt;ubot5&gt;</code> Ubuntu bug 1766538 in cloud-init (Ubuntu) "network customization with cloud-init does not work on Ubuntu18.04 Beta2 Server" [Undecided,New]</p> -<p>16:38 <code>&lt;robjo&gt;</code> OK, so lets also revisit some of the other stuff I have floating about as I just did the 18.2 package for openSUSE and SLES and noticed that I am once again scarring a lot of patches :(</p> -<p>16:39 <code>&lt;robjo&gt;</code> blackboxsw: <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/emptyStageOK">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/emptyStageOK</a> should be back in your court, did you get notification?</p> -<p>16:40 <code>&lt;robjo&gt;</code> blackboxsw: <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/noLnxDistro">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/noLnxDistro</a> pending since January this may have some merge conflicts now as I had to fiddle quite a bit with the patch in my package</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> stanguturi: looking</p> -<p>16:41 <code>&lt;robjo&gt;</code> I think rharper is working on a different approach to <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/chrony">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/chrony</a> when can we expect that?</p> -<p>16:42 <code>&lt;robjo&gt;</code> and does rharper account for the fact that ntp has a different service name on different distributions?</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538</a></p> -<p>16:43 <code>&lt;ubot5&gt;</code> Ubuntu bug 1766538 in cloud-init (Ubuntu) "network customization with cloud-init does not work on Ubuntu18.04 Beta2 Server" [Undecided,New]</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/emptyStageOK">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/emptyStageOK</a></p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> ahh robjo hadn't, was on vacation Friday, will grab that/close out today</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/noLnxDistro">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/noLnxDistro</a></p> -<p>16:44 <code>&lt;rharper&gt;</code> robjo: re: ntp/chrony, that's landed, including service names for different distros; I pulled unittests and scenarios from your branch; please look over master and see if we're missing anything from your branch w.r.t use-case/scenario</p> -<p>16:45 <code>&lt;robjo&gt;</code> rharper: OK, if it's landed I can at least throw my branch away, and yes, will take a look at master, I take it this will be another in 18.3 item?</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> stanguturi: ok thanks for the logs on that bug, looks like network config parsing is falling over and OVF datasource isn't being detected <a href="https://pastebin.ubuntu.com/p/qVJxDJWZRV/">https://pastebin.ubuntu.com/p/qVJxDJWZRV/</a></p> -<p>16:47 <code>&lt;stanguturi&gt;</code> @blackboxsw, Oh . Thanks. Will check with him about the test setup and update the bug. Thanks.</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> updated the bug with a comment there</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> thanks stanguturi</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> robjo: correct as well for ntp/chrony, we held off landing it in 18.2 because of risk</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> it was one of the first branches landed after the cut</p> -<p>16:51 <code>&lt;robjo&gt;</code> ok, leaves the <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/noLnxDistro">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/noLnxDistro</a> implementation of distro detection as things I'd like to get resolved, others to be addressed maybe in 2 weeks ;)</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> ok noLnxDistro.... I'm updating the commit comment robjo to the trailing LP: #<code>&lt;bug_id&gt;</code></p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> claiming a review slot on that now</p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> good unit test coverage, thanks for that</p> -<p>16:54 <code>&lt;robjo&gt;</code> np</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> ok this can be reviewed today, not sure if why we don't already have a get_linux_distro utility somewhere, but I'll poke around today for context</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> ahh ahh, thanks for the bug robjo ok</p> -<p>16:56 <code>&lt;robjo&gt;</code> the context is that the Python implementation is going away and has been deprecated</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/+bug/1745235">https://bugs.launchpad.net/cloud-init/+bug/1745235</a></p> -<p>16:56 <code>&lt;ubot5&gt;</code> Ubuntu bug 1745235 in cloud-init "distribution detection" [Undecided,New]</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> thanks again</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> changing that status and will help you get that landed</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> good one</p> -<p>16:58 <code>&lt;robjo&gt;</code> OK, blackboxsw is on the hook for two things this week ;) distro detection and the empty modules list</p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> #action blackboxsw review distro dection and empty modules list</p> -<p>16:58 * meetingology blackboxsw review distro dection and empty modules list</p> -<p>16:58 * robjo on the hook to look at chrony support in master and report back to rharper</p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> #action robjo review existing chrony support in master per rharper's work</p> -<p>16:58 * meetingology robjo review existing chrony support in master per rharper's work</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> official now :)</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> now if I only reviewed previous meeting's action items.... checking now</p> -<p>17:00 <code>&lt;blackboxsw&gt;</code> 16:51 <code>&lt;blackboxsw&gt;</code> #action blackboxsw to have discussions w/ team on datasource maintaining network on each reboot per <a href="https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712">https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712</a></p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> ok per last meeting, we have held a couple of discussions on hotplug vs. maintaining network only on reboot. on first blush it looks like we'd need to have these mutually exclusive, but we are just started to iron our what we want to do for our initial hotplug support in cloud-init and have to have a followup discussion about how to support both approaches</p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> #action blackboxsw carryover network hotplug vs network maintenance on reboot-only</p> -<p>17:02 * meetingology blackboxsw carryover network hotplug vs network maintenance on reboot-only</p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> well that was the only action item from last meeting looks like</p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> ok I think that wraps up today's meeting.</p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> any other parting shots folks?</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> Thanks again for your time. It's always a pleasure.</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> Next meeting two weeks, same bat time...</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-04-30T16:04:00+00:002018-04-30T16:04:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-04-30:/status-2018-04-30.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 30 Apr at 16:04 &mdash; 17:14 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-04-30-16.04.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-04-30-16.04.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:07.</p> -<h3>#cloud-init Reviews: <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a> | Meeting …</h3><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 30 Apr at 16:04 &mdash; 17:14 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-04-30-16.04.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-04-30-16.04.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:07.</p> -<h3>#cloud-init Reviews: <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting: Monday 5/14 16:00 UTC | cloud-init 18.2 released (03/28/2018)</h3> -<p>The discussion about "#cloud-init Reviews: <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting: Monday 5/14 16:00 UTC | cloud-init 18.2 released (03/28/2018)" started at 16:08.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://jenkins.ubuntu.com/server/job/cloud-init-integration-proposed-b/">https://jenkins.ubuntu.com/server/job/cloud-init-integration-proposed-b/</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~cloud-init-dev/cloud-init/+git/cloud-init/+ref/master/+activereviews">https://code.launchpad.net/~cloud-init-dev/cloud-init/+git/cloud-init/+ref/master/+activereviews</a> </li> -</ul> -<h3>In-progresss Development</h3> -<p>The discussion about "In-progresss Development" started at 16:21.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1767412">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1767412</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~jocha/cloud-init/+git/cloud-init/+merge/344192">https://code.launchpad.net/~jocha/cloud-init/+git/cloud-init/+merge/344192</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/344181">https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/344181</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/344198">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/344198</a> </li> -</ul> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 16:31.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712">https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712</a> </li> -<li><strong>LINK</strong>: <a href="https://github.com/SUSE/Enceladus/tree/master/cloud-netconfig">https://github.com/SUSE/Enceladus/tree/master/cloud-netconfig</a> </li> -<li><strong>ACTION</strong>: blackboxsw to have discussions w/ team on datasource maintaining network on each reboot per <a href="https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712">https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712</a></li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538</a> </li> -<li><strong>LINK</strong>: <a href="https://hackmd.io/M1Tae41PQBC7a9qMsurTJw">https://hackmd.io/M1Tae41PQBC7a9qMsurTJw</a>?both </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>Action items, by person</h2> -<ul> -<li>blackboxsw</li> -<li>blackboxsw to have discussions w/ team on datasource maintaining network on each reboot per <a href="https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712">https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712</a></li> -<li>mgerdts</li> -<li>blackboxsw to have discussions w/ team on datasource maintaining network on each reboot per <a href="https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712">https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712</a></li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (113)</li> -<li>mgerdts (21)</li> -<li>ubot5 (12)</li> -<li>akik (5)</li> -<li>stanguturi (4)</li> -<li>meetingology (4)</li> -<li>robjo (3)</li> -</ul> -<h2>Full Log</h2> -<p>16:04 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status meeting</p> -<p>16:04 <code>&lt;meetingology&gt;</code> Meeting started Mon Apr 30 16:04:15 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:04 <code>&lt;meetingology&gt;</code> </p> -<p>16:04 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:04 <code>&lt;blackboxsw&gt;</code> hi folks, sorry for the mis-representation of when our cloud-init status meeting date. It's time for another episode/update of the happenings in cloud-init.</p> -<p>16:05 <code>&lt;blackboxsw&gt;</code> Next meeting will be in two weeks: May 7th</p> -<p>16:05 <code>&lt;blackboxsw&gt;</code> at 16:00 UTC</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> The last couple weeks on the upstream side of the house has been a big push to get testing and stability into master for the Ubuntu Bionic release freeze</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> ... I'd better start with the topic</p> -<p>16:07 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:07 <code>&lt;blackboxsw&gt;</code> The last couple weeks on the upstream side of the house has been a big push to get testing and stability into master for the Ubuntu Bionic release freeze.</p> -<p>16:07 <code>&lt;robjo&gt;</code> May 7th would be 1 week from today that should be May 14th</p> -<p>16:07 <code>&lt;blackboxsw&gt;</code> robjo: gah, I did it again. Thank you... glad someone's listening. Next cloud-init status meeting Monday May 14th 16:00 UTC</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> #topic #cloud-init Reviews: <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting: Monday 5/14 16:00 UTC | cloud-init 18.2 released (03/28/2018)</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> ok topic agrees in channel now, so I don't botch it at the end of meeting</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> Along with a blitz for stability in Bionic the following changes have been shepherded into tip of master</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> - Add reporting events and log_time around early source of blocking time</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> [Ryan Harper]</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> - IBMCloud: recognize provisioning environment during debug boots.</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> (LP: #1767166)</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> - net: detect unstable network names and trigger a settle if needed</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> [Ryan Harper] (LP: #1766287)</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> - IBMCloud: improve documentation in datasource.</p> -<p>16:09 <code>&lt;ubot5&gt;</code> Launchpad bug 1767166 in cloud-init (Ubuntu) "IBMCloud datasource does not recognize provisioning in debug mode." [Medium,Confirmed] <a href="https://launchpad.net/bugs/1767166">https://launchpad.net/bugs/1767166</a></p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> - sysconfig: dhcp6 subnet type should not imply dhcpv4 [Vitaly Kuznetsov]</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> - packages/debian/control.in: add missing dependency on iproute2.</p> -<p>16:09 <code>&lt;ubot5&gt;</code> Launchpad bug 1766287 in cloud-init (Ubuntu) "18.04 minimal images on GCE intermittently fail to set up networking " [Undecided,In progress] <a href="https://launchpad.net/bugs/1766287">https://launchpad.net/bugs/1766287</a></p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> (LP: #1766711)</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> - DataSourceSmartOS: add locking of serial device.</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> [Mike Gerdts] (LP: #1746605)</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> - DataSourceSmartOS: sdc:hostname is ignored [Mike Gerdts] (LP: #1765085)</p> -<p>16:09 <code>&lt;ubot5&gt;</code> Launchpad bug 1766711 in cloud-init (Ubuntu Bionic) "cloud-init missing dependency on iproute2" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1766711">https://launchpad.net/bugs/1766711</a></p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> - DataSourceSmartOS: list() should always return a list</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> [Mike Gerdts] (LP: #1763480)</p> -<p>16:09 <code>&lt;ubot5&gt;</code> Launchpad bug 1746605 in cloud-init "DataSourceSmartOS needs locking" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1746605">https://launchpad.net/bugs/1746605</a></p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> - schema: in validation, raise ImportError if strict but no jsonschema.</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> - set_passwords: Add newline to end of sshd config, only restart if</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> updated. (LP: #1677205)</p> -<p>16:09 <code>&lt;ubot5&gt;</code> Launchpad bug 1765085 in cloud-init "DataSourceSmartOS ignores sdc:hostname" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1765085">https://launchpad.net/bugs/1765085</a></p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> - pylint: pay attention to unused variable warnings.</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> - doc: Add documentation for AliYun datasource. [Junjie Wang]</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> - Schema: do not warn on duplicate items in commands. (LP: #1764264)</p> -<p>16:09 <code>&lt;ubot5&gt;</code> Launchpad bug 1763480 in cloud-init "DataSourceSmartOS list() should always return a list" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1763480">https://launchpad.net/bugs/1763480</a></p> -<p>16:09 <code>&lt;ubot5&gt;</code> Launchpad bug 1677205 in cloud-init "cloud-init eats final EOL of sshd_config" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1677205">https://launchpad.net/bugs/1677205</a></p> -<p>16:09 <code>&lt;ubot5&gt;</code> Launchpad bug 1764264 in juju 2.3 "bionic cloud-init 18.2 WARNING Juju's 'runcmd' stanza" [High,Triaged] <a href="https://launchpad.net/bugs/1764264">https://launchpad.net/bugs/1764264</a></p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> the general theme has been: new IBMCloud datasource support for cloud-init, SmartOS datasource work by mgerdts, and some json schema improvements</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> so background on IBM, is that their support used to be ConfigDrive based datasource only, but there is now some additional support for different IBM boot/provisioning stages, hence a new datasource that can support different boot modew</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> *boot modes</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> over the last two weeks we've landed an SRU into xenial and artful: 18.2-4-g05926e48-0ubuntu1~16.04.1 and bionic sits at 18.2-14-g6d48d265-0ubuntu1</p> -<p>16:15 <code>&lt;mgerdts&gt;</code> On the SmartOS side, my changes are driven by our adoption of bhyve (moving away from kvm/qemu). qemu provides a dhcp server VMs could fall back to if could-init was missing or misbehaving. bhyve doesn't have that, so I've been working on getting cloud-init to be more stable with the bhyve serial metadata service.</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> Also, to our continuous integration on jenkins we now have an additional test for proposed packages in ubuntu for the bionic release to make sure ubuntu doesn't break across pending upgrades</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> #link <a href="https://jenkins.ubuntu.com/server/job/cloud-init-integration-proposed-b/">https://jenkins.ubuntu.com/server/job/cloud-init-integration-proposed-b/</a></p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> that integration tests hits the suite of platforms lxd, kvm and ec2</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> excellent mgerdts, and thanks for the blitz on these branches</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> looks like there are a few still in our review queue that we'll be able to get through once the dust settles on the bionic release (which should be this week)</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~cloud-init-dev/cloud-init/+git/cloud-init/+ref/master/+activereviews">https://code.launchpad.net/~cloud-init-dev/cloud-init/+git/cloud-init/+ref/master/+activereviews</a></p> -<p>16:19 <code>&lt;mgerdts&gt;</code> Is now the right time to discuss bug 1765801, or is that later?</p> -<p>16:19 <code>&lt;ubot5&gt;</code> bug 1765801 in cloud-init "network should be optionally reconfigured on every boot" [Undecided,Confirmed] <a href="https://launchpad.net/bugs/1765801">https://launchpad.net/bugs/1765801</a></p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> I think over the last 2 weeks there have been a couple of requests in channel for how someone goes about getting newer cloud init into RHEL7, if anyone on the line today knows the contact point or process for that it'd be helpful. larsks doesn't seem to be around</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> mgerdts: probably in about 10 mins. thanks for brining it up</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> hopefully less.</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> ok I think that's it for recent changes, next topic (in-progress dev, then office hours (and bug discussion))</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> #topic In-progresss Development</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> We'll make this one short:</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> for ubuntu : bionic just went feature freeze last week, our team has a couple of IBM-related cheanges that we are pulling together for a quick SRU into xenial/artful to handle upgrade path from configdrive -&gt;` IBMCloud that we are working on the beginning of this week</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> we are also trying to wrap up validation of a Bionic SRU per the following bug</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1767412">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1767412</a></p> -<p>16:22 <code>&lt;ubot5&gt;</code> Launchpad bug 1767412 in cloud-init (Ubuntu Bionic) "SRU cloud-init 18.2-27-g6ef92c98-0ubuntu1" [Medium,Fix committed]</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> which grabs a number of the updates I listed in the last topic</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> since Ubuntu tends to sync all changes from tip into each release stream</p> -<p>16:23 <code>&lt;mgerdts&gt;</code> Is there any chance the SmartOS changes can piggy back on that IBM SRU</p> -<p>16:24 <code>&lt;mgerdts&gt;</code> asked too soon - I see they are mentioned in that bug.</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> mgerdts: no worries. good ask. probably not for this IBM SRU into xenial/artful which is going to be an exception to our update rule and only be a single cherry pick, but planning a folllowup SRU in about 2 weeks which will pull all changes from tip into artful/xenial/bionic/chunky releases</p> -<p>16:25 <code>&lt;mgerdts&gt;</code> ok</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> the cherry pick is to fasttrack it for IBM into xenial with minimal risk.</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> and we want to pull in all your changes if we can (and perform additional validation)</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> so the next SRU is our target</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> Also inprogress is some more Azure work on pre-provisioning that should land shortly:</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~jocha/cloud-init/+git/cloud-init/+merge/344192">https://code.launchpad.net/~jocha/cloud-init/+git/cloud-init/+merge/344192</a></p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> as well as some builddeb fixes and network configuration printout fixes from smoser</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> smoser and rharper also worked out some issues on specific google regions where cloud-init was getting hit by a race condition. Cloud-init started up before the kernel/udev was able to rename network devices to stable names like ens4 etc, so cloud-init's network configuration written ended up breaking because it represented devices like eth0 etc.</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> there are a couple of branches in flight to fix this issue:</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/344181">https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/344181</a></p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/344198">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/344198</a></p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> ok I think that's it for in-progress work. So we'll head to office hours so we can chat bugs, branches reviews etc</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> We'll be hanging out here for anyone who wants more eyes on a review, feature discussions or bug triage....</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> well, some of us will be :) a couple of us are at a feature planning conference for the week.</p> -<p>16:33 <code>&lt;mgerdts&gt;</code> In <a href="https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712">https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712</a> smoser said that he was concerned about how this would interact with eventual network hotplug</p> -<p>16:34 <code>&lt;mgerdts&gt;</code> There doesn't seem to be a timeline for network hotplug and the lack of network autoreconfig on reboot is has popped up a couple times in the past week. This is just with a couple early adopters and internal users.</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712">https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712</a></p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> just to track it in the meeting</p> -<p>16:35 <code>&lt;mgerdts&gt;</code> So coming up with some mechanism to make this work soon is pretty important to us.</p> -<p>16:35 <code>&lt;mgerdts&gt;</code> gotcha, will be sure to do that in the future.</p> -<p>16:35 * blackboxsw reads up on that link</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> no worries, I'm pedantic :)</p> -<p>16:36 <code>&lt;mgerdts&gt;</code> That's how you got chosen to run the meeting, I suppose. :)</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> yeah network hotplug will have a long tail as far as feature develpment (agreed). I believe it's on our charter for this next quarter. but that's what is being discussed this week</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> heh on meeting comment ;) too true</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> so mgerdts your branch allows metadata to set maintain_network to allow cloud-init to control network configuration each reboot with a True value</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> ?</p> -<p>16:39 <code>&lt;mgerdts&gt;</code> yes</p> -<p>16:39 <code>&lt;mgerdts&gt;</code> if it's not set to true in our metadata, the traditional behavior stays.</p> -<p>16:40 <code>&lt;mgerdts&gt;</code> That is, in the default path, any customization that someone does in the guest will not get whacked.</p> -<p>16:41 <code>&lt;robjo&gt;</code> cloud-netconfig handles hotplug <a href="https://github.com/SUSE/Enceladus/tree/master/cloud-netconfig">https://github.com/SUSE/Enceladus/tree/master/cloud-netconfig</a> contributions for other distros welcome</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> nice reference robjo</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> #link <a href="https://github.com/SUSE/Enceladus/tree/master/cloud-netconfig">https://github.com/SUSE/Enceladus/tree/master/cloud-netconfig</a></p> -<p>16:43 <code>&lt;robjo&gt;</code> We currently have no GCE specific information but that is easy enough to add. The GCE guest environment handles this and we use the GCE guest environment code in our images in GCE</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> mgerdts: so can a user turn off that feature on an instance once they've already deployed, or is it create-time only</p> -<p>16:43 <code>&lt;mgerdts&gt;</code> It can be flipped at any time, in the current implementation.</p> -<p>16:44 <code>&lt;mgerdts&gt;</code> current implementation is only in a development branch</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> mgerdts: the only things I can see being an issue with the maintain network in cloud-init is that we are adding the cost of another function call &amp;&amp; metdata dict parse to look for a signal about maintaining the network. I agree that cloud-init having granularity between is_new_instance vs just re-do network, is something that cloud-init should have.</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> we probably need to discuss this too with rharper about what short-term vision we can get to while we await our network hotplug support in cloud-init proper</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> I'd tend to agree that waiting on fully baked hotplug solution is probably too long in this case</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> as that runway will be at least 2 months I'd think</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> ok, I'll take an action item to resolve this if we can by next meeting</p> -<p>16:50 <code>&lt;mgerdts&gt;</code> Not only that, but support for it will likely require changes in the host as well. We tend not to do host updates very often, so it could be a year or more after the feature is available in images before it will be useful.</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> #action blackboxsw to have discussions w/ team on datasource maintaining network on each reboot per <a href="https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712">https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712</a></p> -<p>16:51 * meetingology blackboxsw to have discussions w/ team on datasource maintaining network on each reboot per <a href="https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712">https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712</a></p> -<p>16:51 <code>&lt;mgerdts&gt;</code> thanks</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> good topic.</p> -<p>16:52 <code>&lt;mgerdts&gt;</code> Is there another place that is good to catch up with larsks or other people that can offer guidance on for redhat/centos?</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> let's see, anything else folks want to chat about? stagnant reviews, bugs of interest etc?</p> -<p>16:53 * blackboxsw looks at the last cloud-init community summit attendees list to see if rhel folks have another contacts that was supposed to replace larsks</p> -<p>16:53 <code>&lt;stanguturi&gt;</code> Chad, Is it possible that someone from cloud-init team can take a look at <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538</a></p> -<p>16:53 <code>&lt;ubot5&gt;</code> Launchpad bug 1766538 in cloud-init (Ubuntu) "network customization with cloud-init does not work on Ubuntu18.04 Beta2 Server" [Undecided,Confirmed]</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> mgerts, ryan mccabe is a potential contact too, looks like he's not here either today.</p> -<p>16:56 <code>&lt;mgerdts&gt;</code> ok, thanks</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> hrm, yeah not certain what mechanism is used to get cloud-init updated into RedHat mgerdts. Maybe filing a redhat bug about the request</p> -<p>16:57 <code>&lt;blackboxsw&gt;</code> mgerdts: <a href="https://bugzilla.redhat.com/">https://bugzilla.redhat.com/</a> maybe</p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> stanguturi: yes we can, we are trying to sort and understand any bugs against Bionic that we can</p> -<p>16:58 <code>&lt;mgerdts&gt;</code> ok, I can try that.</p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538</a></p> -<p>16:58 <code>&lt;ubot5&gt;</code> Launchpad bug 1766538 in cloud-init (Ubuntu) "network customization with cloud-init does not work on Ubuntu18.04 Beta2 Server" [Undecided,Confirmed]</p> -<p>16:58 <code>&lt;stanguturi&gt;</code> blackboxsw: Thanks</p> -<p>17:00 <code>&lt;blackboxsw&gt;</code> stanguturi: ok, so this is netplan + cloud-init related right?</p> -<p>17:00 <code>&lt;stanguturi&gt;</code> blackboxsw: Yes.</p> -<p>17:01 <code>&lt;akik&gt;</code> what does network hotplug mean in cloud-init context?</p> -<p>17:02 * blackboxsw tries to remember what vmware datasource does, (like writing files direct to network /etc/network/interfaces.d)</p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> akik: <a href="https://hackmd.io/M1Tae41PQBC7a9qMsurTJw">https://hackmd.io/M1Tae41PQBC7a9qMsurTJw</a>?both is a shared document for comment on hotplug in cloud-init</p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> #link <a href="https://hackmd.io/M1Tae41PQBC7a9qMsurTJw">https://hackmd.io/M1Tae41PQBC7a9qMsurTJw</a>?both</p> -<p>17:03 * blackboxsw looks to see if there was a better doc hrm</p> -<p>17:03 <code>&lt;stanguturi&gt;</code> blackboxsw: Oh. But in the case of netplan, why does cloud-init remembers?</p> -<p>17:04 <code>&lt;akik&gt;</code> blackboxsw: does it mean that cloud-init stays running, waiting for new network interfaces to appear?</p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> akik: right, it would mean that you wouldn't have to reboot cloud-init if devices get added at a later time (post-boot)</p> -<p>17:05 <code>&lt;blackboxsw&gt;</code> cloud-init would listen to some sort of event channel and react, re-write, and apply network config to add new devices</p> -<p>17:06 <code>&lt;akik&gt;</code> would it do the same thing as you could do with ansible or puppet? sorry i'm trying to understand why you would do it with cloud-init</p> -<p>17:08 <code>&lt;blackboxsw&gt;</code> akik: you would try to do it with cloud-init if you didn't want to rely on additional configuration management solutions if the only thing you needed was network config to reflect reality (not full system configuration and system automation)</p> -<p>17:09 * blackboxsw has more puppet/chef background than ansible.</p> -<p>17:09 <code>&lt;blackboxsw&gt;</code> cloud-init does currently detect and write network configuration based on what the user/cloud-metadata tell us is the proper config for the instance</p> -<p>17:10 <code>&lt;akik&gt;</code> i only thought of cloud-init to do the initial configuration</p> -<p>17:10 <code>&lt;blackboxsw&gt;</code> so it would follow that if the metadata could dynamically tell the instance that network config has changed, cloud-init should probably try to react to that to fix the config to match the updated network configuration</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> akik: correct. cloud-init current only handle initial boot config and leaves the rest up whatever mechanism someone uses to update detailed config after that boot</p> -<p>17:11 <code>&lt;akik&gt;</code> ok thanks</p> -<p>17:12 <code>&lt;blackboxsw&gt;</code> akik: and we'd make that feature configurable (handle hotplug:True/False) so if users have other services handling hotplug cloud-init wouldn't collide</p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> ok I think we're hitting the end of office hours. please feel free to continue discussion, we all poke around here throughout the day as our primary means of communication</p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> thanks robjo akik stanguturi and mgerdts for the lively discussion</p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> stanguturi: I'll dig up more info on that bug today</p> -<p>17:13 <code>&lt;mgerdts&gt;</code> thank you</p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> as always notes will be here</p> -<p>17:14 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>17:14 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-04-16T16:01:00+00:002018-04-16T16:01:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-04-16:/status-2018-04-16.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 16 Apr at 16:01 &mdash; 18:11 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-04-16-16.01.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-04-16-16.01.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent-changes</h3> -<p>The discussion about "Recent-changes" started at 16:04.</p> -<h3>In-progresss Development</h3> -<p>The discussion about "In-progresss Development" started at …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 16 Apr at 16:01 &mdash; 18:11 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-04-16-16.01.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-04-16-16.01.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent-changes</h3> -<p>The discussion about "Recent-changes" started at 16:04.</p> -<h3>In-progresss Development</h3> -<p>The discussion about "In-progresss Development" started at 16:11.</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="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1759406">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1759406</a> </li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/bugs/1570997">https://bugs.launchpad.net/bugs/1570997</a> </li> -<li><strong>LINK</strong>: <a href="https://trello.com/c/JVaXSfpo/749-eol-fix-for-ssh-file">https://trello.com/c/JVaXSfpo/749-eol-fix-for-ssh-file</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/343123">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/343123</a> </li> -</ul> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 16:23.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bug/1667735">https://bugs.launchpad.net/cloud-init/+bug/1667735</a> implements proper protocol negotiation over the serial port. The lack of this has caused problems with KVM at times too.</li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bug/1746605">https://bugs.launchpad.net/cloud-init/+bug/1746605</a> adressess times when cloud-init and other software may be trying to use the metadata serial port at the same time. This is purely a bug fix.</li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bug/1763480">https://bugs.launchpad.net/cloud-init/+bug/1763480</a> makes it so that cloud-init doesn't stack trace and exit when there is no customer_metadata. This is an unlikely case, but something that is hit when you are testing things that don't need ssh keys, etc.</li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bug/1763512">https://bugs.launchpad.net/cloud-init/+bug/1763512</a> finishes off the partial implementation of sdc:routes support. Previously, we didn't publish the required information to VMs, so it is fair to consider this a new feature.</li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1763511">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1763511</a> is probably the most incompatible change. New ephemeral disks will get ext4 instead of ext3, which is needed for larger disks that seem to be getting more common.</li> -</ul> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (54)</li> -<li>smoser (17)</li> -<li>rharper (13)</li> -<li>mgerdts (10)</li> -<li>ubot5` (10)</li> -<li>cyphermox (3)</li> -<li>meetingology (3)</li> -<li>dpb1 (1)</li> -</ul> -<h2>Full Log</h2> -<p>16:01 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status meeting</p> -<p>16:01 <code>&lt;meetingology&gt;</code> Meeting started Mon Apr 16 16:01:49 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:01 <code>&lt;meetingology&gt;</code> </p> -<p>16:01 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:02 <code>&lt;rharper&gt;</code> o/</p> -<p>16:03 <code>&lt;blackboxsw&gt;</code> Hi folks, welcome to cloud-init's bi-weekly status meeting. Feel free to interject at any time or bring up branches/bugs/questions over the next 30-60 mins. We'll have a number of folks around to get eyes and/or keyboards onto any problems.</p> -<p>16:03 <code>&lt;dpb1&gt;</code> o/</p> -<p>16:04 <code>&lt;blackboxsw&gt;</code> As always we'll go through the following topics (feel free to suggest others): Recent-changes, In-progress Development, and ~30 mins Office Hours)</p> -<p>16:04 <code>&lt;blackboxsw&gt;</code> #topic Recent-changes</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> a quick rundown of the hi level changes landed:</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> Prune integration test artifacts</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> Add support for LXD 3.0, fix pylxd integration test dependency</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> Fix Ubuntu proposed integration test CI job</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> Fix ec2 validation of instance-data.json network info</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> Do not retry optional userdata on 404 (LP: #1702160)</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> Add explicit cloud-init package dependency on isc-dhcp-client (LP: #1759307)</p> -<p>16:06 <code>&lt;ubot5</code>&gt;` Launchpad bug 1702160 in cloud-init "OpenStack datasource should not retry user-data on 404" [Medium,Fix released] <a href="https://launchpad.net/bugs/1702160">https://launchpad.net/bugs/1702160</a></p> -<p>16:06 <code>&lt;ubot5</code>&gt;` Launchpad bug 1759307 in cloud-init (Ubuntu) "missing dependency on isc-dhcp-client (dhclient)" [Medium,Fix released] <a href="https://launchpad.net/bugs/1759307">https://launchpad.net/bugs/1759307</a></p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> additionally from most recent commits we have:</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> tools: Fix make-tarball cli tool usage for development</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> renderer: support unicode in render_from_file.</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> Implement ntp client spec with auto support for distro selection</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> Apport: add Brightbox, IBM, LXD, and OpenTelekomCloud to list of clouds.</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> tests: fix ec2 integration network metadata validation</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> tests: fix integration tests to support lxd 3.0 release</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> correct documentation to match correct attribute name usage.</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> cc_resizefs, util: handle no /dev/zfs</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> Last week rharper found and fixed a regression in zfs resize behavior that was blocking our ubuntu SRU</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> We have uploaded those fixes, as well as rharper's ntp spec changes (which should incorporate a number of robjo's opensuse/sles needs too)</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> anything else notable that I'm missing gentlemen?</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> If not, I'll jump to in-progress development</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> #topic In-progresss Development</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> So, on the ubuntu side of the house we are about to approve the cloud-init 18.2 SRU (Stable release update) into xenial and artful. Just one more validation run and we should be good to see 18.2.4 on xenial, artful. Ubuntu Bionic is already a few commits beyond that.</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> On Ubuntu as well we are beating the drop to the Bionic LTS (Long term release) feature/bug freeze.</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> This week marks the last week for use to get fixes into Bioinic images before that release is cut.</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> so we'll be heads down on any Bionic-specific changes that need to get in.</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> Feel free to checkout our trello board @</p> -<p>16:14 <code>&lt;blackboxsw&gt;</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:15 <code>&lt;blackboxsw&gt;</code> we track all tasks we are working on in public view there so if there are any questions you can ping one of us here about our development efforts</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> additional tasks that are in flight: bash-autocompletion for cloud-init CLI (rhaper). dropping ifconfig and route in favor of 'ip' (bbsw), and moving openstack datasource to cloud-init's local stage</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> (smoser)</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> also a couple of bugs to fix such as #1570997</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1759406">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1759406</a></p> -<p>16:17 <code>&lt;ubot5</code>&gt;` Ubuntu bug 1759406 in cloud-init (Ubuntu) "sru cloud-init (17.2-35-gf576b2a2-0ubuntu1~16.04.1 update to 18.2-4-g05926e48-0ubuntu1)" [Medium,Confirmed]</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> oops paste fail:</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/bugs/1570997">https://bugs.launchpad.net/bugs/1570997</a></p> -<p>16:17 <code>&lt;ubot5</code>&gt;` Ubuntu bug 1570997 in ssh-import-id (Ubuntu Xenial) "fail if HOME environment variable is not set" [Low,Fix committed]</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> I think that about wraps in-progress development, anything else that should be noted smoser rharper ?</p> -<p>16:18 <code>&lt;rharper&gt;</code> I think you covered it</p> -<p>16:18 <code>&lt;smoser&gt;</code> ssh-import-id is not relally at all related to cloud-init</p> -<p>16:19 <code>&lt;smoser&gt;</code> thanks blackboxsw</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> oops grabbed the wrong one, was thinking about this card</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #link <a href="https://trello.com/c/JVaXSfpo/749-eol-fix-for-ssh-file">https://trello.com/c/JVaXSfpo/749-eol-fix-for-ssh-file</a></p> -<p>16:19 <code>&lt;smoser&gt;</code> right.</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> also of note, in some of our SRU testing we found time-tracking gaps in cloud-init analyze tracking on Azure. rharper put of a logging tracker fix to avoid those tracking gaps</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/343123">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/343123</a></p> -<p>16:21 <code>&lt;smoser&gt;</code> i'll point out one thing i just finished up with...</p> -<p>16:22 <code>&lt;smoser&gt;</code> for testing ubuntu, the <a href="https://github.com/cloud-init/ubuntu-sru/">https://github.com/cloud-init/ubuntu-sru/</a> has 'get-proposed-cloudimg' and 'lxc-proposed-snapshot'</p> -<p>16:22 <code>&lt;smoser&gt;</code> which now work more like each other.l and can do more than just upgrade cloud-init.</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> thanks smoser. Great tools to quicken dev-test cycles and make cloud-init development easier. That wraps up what we've been up to. We can probably move to the open forum for any discussions folks want to have</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> We'll be hanging out here for anyone who wants more eyes on a review, feature discussions or bug triage....</p> -<p>16:28 <code>&lt;smoser&gt;</code> mgerdts: i'm poking at the branch i think i shoudl be able to get something.</p> -<p>16:29 <code>&lt;mgerdts&gt;</code> I'm working on a bunch of fixes for things that have turned up on bhyve with SmartOS. Since we are looking to transition from KVM to bhyve, we will need to provide updates at least as far back as xenial and probably trusty. Is the process for this any more complicated than get the fixes in master, then cherry-pick the fixes into branches?</p> -<p>16:29 <code>&lt;mgerdts&gt;</code> thanks @smoser</p> -<p>17:09 <code>&lt;rharper&gt;</code> mgerdts: we preferrer not to cherry; rather we release master back to xenial via our SRU (Stable Release Update) process; however, we spend a lot of effort to not modify existing behavior on prevlous SRU releases; so if the changes to support bhyve can be done in a compatible way (working with either) that'd be best; worst-case, we patch in release specific bahvior into the release branch.</p> -<p>17:13 <code>&lt;mgerdts&gt;</code> Pretty much everything that I've got queued up is fully compatible.</p> -<p>17:14 <code>&lt;mgerdts&gt;</code> <a href="https://bugs.launchpad.net/cloud-init/+bug/1667735">https://bugs.launchpad.net/cloud-init/+bug/1667735</a> implements proper protocol negotiation over the serial port. The lack of this has caused problems with KVM at times too.</p> -<p>17:14 <code>&lt;ubot5</code>&gt;` Ubuntu bug 1667735 in cloud-init (Ubuntu Trusty) "cloud-init doesn't retry metadata lookups and hangs forever if metadata is down" [Medium,Confirmed]</p> -<p>17:15 <code>&lt;mgerdts&gt;</code> <a href="https://bugs.launchpad.net/cloud-init/+bug/1746605">https://bugs.launchpad.net/cloud-init/+bug/1746605</a> adressess times when cloud-init and other software may be trying to use the metadata serial port at the same time. This is purely a bug fix.</p> -<p>17:15 <code>&lt;ubot5</code>&gt;` Ubuntu bug 1746605 in cloud-init "DataSourceSmartOS needs locking" [Medium,Confirmed]</p> -<p>17:15 <code>&lt;mgerdts&gt;</code> I hit it when rc.local and cloud-init were both trying to get metadata.</p> -<p>17:17 <code>&lt;mgerdts&gt;</code> <a href="https://bugs.launchpad.net/cloud-init/+bug/1763480">https://bugs.launchpad.net/cloud-init/+bug/1763480</a> makes it so that cloud-init doesn't stack trace and exit when there is no customer_metadata. This is an unlikely case, but something that is hit when you are testing things that don't need ssh keys, etc.</p> -<p>17:17 <code>&lt;ubot5</code>&gt;` Ubuntu bug 1763480 in cloud-init "DataSourceSmartOS list() should always return a list" [Medium,Confirmed]</p> -<p>17:18 <code>&lt;mgerdts&gt;</code> <a href="https://bugs.launchpad.net/cloud-init/+bug/1763512">https://bugs.launchpad.net/cloud-init/+bug/1763512</a> finishes off the partial implementation of sdc:routes support. Previously, we didn't publish the required information to VMs, so it is fair to consider this a new feature.</p> -<p>17:18 <code>&lt;ubot5</code>&gt;` Ubuntu bug 1763512 in cloud-init "DataSourceSmartOS ignores sdc:routes" [Medium,Confirmed]</p> -<p>17:19 <code>&lt;mgerdts&gt;</code> <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1763511">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1763511</a> is probably the most incompatible change. New ephemeral disks will get ext4 instead of ext3, which is needed for larger disks that seem to be getting more common.</p> -<p>17:19 <code>&lt;ubot5</code>&gt;` Ubuntu bug 1763511 in cloud-init (Ubuntu) "DataSourceSmartOS should default to ext4" [Undecided,New]</p> -<p>17:21 <code>&lt;mgerdts&gt;</code> I think that's all that I have in the works right now. Do any of these sound like they would be problematic as far back as Xenial?</p> -<p>17:29 <code>&lt;rharper&gt;</code> new features are OK ,bug fixes are fine as well; I think that different filesystem is somewhat tricky</p> -<p>17:30 <code>&lt;smoser&gt;</code> i think i'm generally ok with the different filesystem.</p> -<p>17:31 <code>&lt;smoser&gt;</code> if the reason is that simply ext3 can't handle super-big</p> -<p>17:31 <code>&lt;rharper&gt;</code> yeah, that doesn't seem so user-visible w.r.t configuration;</p> -<p>17:32 <code>&lt;smoser&gt;</code> we could ensure being more backward compat if we checked the size of the disk and made an ext4 if &gt;` that-size</p> -<p>17:32 <code>&lt;smoser&gt;</code> then there'd less issue</p> -<p>17:32 <code>&lt;smoser&gt;</code> but more complication and future we'd be stuck with that</p> -<p>17:32 <code>&lt;rharper&gt;</code> yeah, it wouldn't have worked on ext3 then it would be fine to use ext4</p> -<p>17:32 <code>&lt;smoser&gt;</code> so i'd rather really just bite the bulleet</p> -<p>17:32 <code>&lt;rharper&gt;</code> it could be a metadata flag that the Datasource looks for</p> -<p>17:32 <code>&lt;smoser&gt;</code> rather than describing to pepole forever "well, if your disk is `&lt; X you'll get ext3 otherwise ext4"</p> -<p>17:49 <code>&lt;blackboxsw&gt;</code> rharper: got time for a netplan global dns hangout?</p> -<p>17:49 <code>&lt;rharper&gt;</code> y</p> -<p>17:49 <code>&lt;blackboxsw&gt;</code> I want to make sure I'm reading the tea leaves right</p> -<p>17:52 <code>&lt;smoser&gt;</code> mgerdts: <a href="http://paste.ubuntu.com/p/5qdtFzY8w7/">http://paste.ubuntu.com/p/5qdtFzY8w7/</a></p> -<p>17:52 <code>&lt;blackboxsw&gt;</code> ok rharper I'm in cloud-init hangout</p> -<p>17:52 <code>&lt;smoser&gt;</code> that makes tests pass. and i think the changes to the code path are right</p> -<p>17:52 <code>&lt;rharper&gt;</code> ok</p> -<p>17:52 <code>&lt;rharper&gt;</code> brt</p> -<p>17:54 <code>&lt;smoser&gt;</code> it is still hacked in a sense that the response only deals with fp.read(1) rather than possibly anything that read more than 1.</p> -<p>17:56 <code>&lt;cyphermox&gt;</code> blackboxsw: rharper: what's this about netplan global dns?</p> -<p>17:57 <code>&lt;rharper&gt;</code> cyphermox: converting network v1 syntax from maas into something that works with netplan which doesn't have "dns" unbound to any interfaces</p> -<p>17:57 <code>&lt;cyphermox&gt;</code> ok</p> -<p>17:57 <code>&lt;rharper&gt;</code> maas I believe has fixed this for 2.4.x</p> -<p>17:58 <code>&lt;rharper&gt;</code> they no longer will emit the type: nameserver but legacy maas would have that, so we've a branch that stuffs them in reasonable places under defined interfaces which don't already have DNS values</p> -<p>17:58 <code>&lt;blackboxsw&gt;</code> cyphermox: just SRU validation w.r.t. <a href="https://bugs.launchpad.net/cloud-init/+bug/1750884">https://bugs.launchpad.net/cloud-init/+bug/1750884</a></p> -<p>17:59 <code>&lt;ubot5</code>&gt;` Ubuntu bug 1750884 in cloud-init "[2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution" [Medium,Fix released]</p> -<p>17:59 <code>&lt;cyphermox&gt;</code> all good</p> -<p>18:11 <code>&lt;blackboxsw&gt;</code> ooops, and /me forgot the end the epic meeting</p> -<p>18:11 <code>&lt;blackboxsw&gt;</code> thx rharper for the chat</p> -<p>18:11 <code>&lt;blackboxsw&gt;</code> #endmeetiung</p> -<p>18:11 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-04-02T16:05:00+00:002018-04-02T16:05:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-04-02:/status-2018-04-02.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: bi-weekly status meeting, 02 Apr at 16:05 &mdash; 17:03 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-04-02-16.05.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-04-02-16.05.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:08.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://lists.launchpad.net/cloud-init/msg00145.html">https://lists.launchpad.net/cloud-init/msg00145.html …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: bi-weekly status meeting, 02 Apr at 16:05 &mdash; 17:03 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-04-02-16.05.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-04-02-16.05.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:08.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://lists.launchpad.net/cloud-init/msg00145.html">https://lists.launchpad.net/cloud-init/msg00145.html</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/fix/cc_resizefs_on_zfs_root">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/fix/cc_resizefs_on_zfs_root</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:19.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/fix/cc_resizefs_on_zfs_root">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/fix/cc_resizefs_on_zfs_root</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/342007">https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/342007</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/342428">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/342428</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/342010">https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/342010</a> </li> -<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>Office Hours (next ~30 minutes)</h3> -<p>The discussion about "Office Hours (next ~30 minutes)" started at 16:27.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/339438">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/339438</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/339438">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/339438</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 (64)</li> -<li>rharper (14)</li> -<li>ubot5 (3)</li> -<li>meetingology (3)</li> -<li>powersj (2)</li> -</ul> -<h2>Full Log</h2> -<p>16:05 <code>&lt;blackboxsw&gt;</code> #startmeeting bi-weekly status meeting</p> -<p>16:05 <code>&lt;meetingology&gt;</code> Meeting started Mon Apr 2 16:05:50 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:05 <code>&lt;meetingology&gt;</code> </p> -<p>16:05 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> Welcome to the post-Easter episode of cloud-init's status meeting 🐰</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> Today's meeting will probably be light as we are fairly light on attendees given various holiday schedules</p> -<p>16:07 <code>&lt;rharper&gt;</code> o/</p> -<p>16:07 <code>&lt;rharper&gt;</code> nice rabbit ears</p> -<p>16:07 <code>&lt;blackboxsw&gt;</code> heya! As always, we'll go through recent changes, in progress work and ~30 minutes of office hours</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> feel free to interject and ask quesitons at any time.</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> Here's a brief run down of what we have committed to master in the last couple weeks</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> - Support for setting hostname from metadata prior to network bringup.</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> This fixes vsphere multi-vm deployments all coming up with the same</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> 'ubuntu' hostname. <a href="[http://pad.lv/1746455](http://pad.lv/1746455)">LP: #1746455</a></p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> - Support initramfs iscsi root so network devices aren't disconnected</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> before shutdown</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> - Added cloud-config module <code>cc_snap</code> which enables loading snap</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> assertions, configuring snapd and installing snap packages on Ubuntu.</p> -<p>16:10 <code>&lt;ubot5&gt;</code> Launchpad bug 1746455 in cloud-init "cloud-init vSphere cloud provider DHCP unique hostname issue" [High,Fix released]</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> Deprecated <code>cc_snappy</code> and <code>cc_snap_config</code> modules.</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> - Make salt minion work on FreeBSD (Dominic Schlegel)</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> <a href="[http://pad.lv/1721503](http://pad.lv/1721503)">LP:#1721503</a></p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> - Simplify compound conditionals (Rémy Léone)</p> -<p>16:10 <code>&lt;ubot5&gt;</code> Launchpad bug 1721503 in cloud-init "salt module not able to be used on FreeBSD" [Medium,Fix released]</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> - Change some list creation and population to literals (Rémy Léone)</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> - Add puppet 4 support configurable in <code>cc_puppet</code> module (Romanos</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> Skiadas)</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> - Fix datasouce Azure <code>get_hostname</code> function for hostname bounce</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> (Douglas Jordan) <a href="[http://pad.lv/1754495](http://pad.lv/1754495)">LP:#1754495</a></p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> - OpenNebula datasource now uses network config v2 to support IPv6</p> -<p>16:10 <code>&lt;ubot5&gt;</code> Launchpad bug 1755965 in cloud-init (Ubuntu) "duplicate for #1754495 util.subp regression: no longer accept commands as string" [Critical,Fix released]</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> config (Akihiko Ota)</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> - Add Hetzner Cloud datasource support (Markus Schade)</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> The highlights of this work that will affect various clouds: hostname setting before network bringup, in cloud-init's init-local stage.</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> so if your cloud's metadata provides hostname information (per your instance creation) that hostname gets set before any potential dhcp discovery on the instance. This is a big win for Azure and may allow us to avoid/deprecate some of the hostname_bounce functionality</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> which was baked in to re-dhcp in order to publish updated hostname information to DDNS</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> We also have landed support for two new clouds: Hetzner Cloud and IBMCloud. A big thanks to Markus Schade for the Hetzner work there and smoser for the IBMCloud datasource</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> do3meli (Dominic Schlegel) has also been on a blitz fixing and updating a lot of FreeBSD support in cloud-init tip so thank you sir for that work as well.</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> We've just also landed some zfs resize support by rharper as well that should be making it's way into your friendly neighborhood Ubuntu Bionic series in a cloud near you</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> anything else I'm missing on rharper or powersj ?</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> ahh hold the phone</p> -<p>16:16 <code>&lt;rharper&gt;</code> blackboxsw: well, not my zfs-resize</p> -<p>16:17 <code>&lt;rharper&gt;</code> but I do have some fixes for it</p> -<p>16:17 <code>&lt;rharper&gt;</code> <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/fix/cc_resizefs_on_zfs_root">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/fix/cc_resizefs_on_zfs_root</a></p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> We officially released cloud-init 18.2 in master. There is an 18.2 tag in the repo for folks wanting to take an early cut of it.</p> -<p>16:17 <code>&lt;rharper&gt;</code> our ci-test backend normally runs with zfs, it's not right now so it missed a couple edge cases that we need to handle</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> Per cloud-init 18.2 here is an email sent to the cloud-init mailing list describing the details: <a href="https://lists.launchpad.net/cloud-init/msg00145.html">https://lists.launchpad.net/cloud-init/msg00145.html</a></p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> #link <a href="https://lists.launchpad.net/cloud-init/msg00145.html">https://lists.launchpad.net/cloud-init/msg00145.html</a></p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/fix/cc_resizefs_on_zfs_root">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/fix/cc_resizefs_on_zfs_root</a></p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> The upstream team has released 18,2 to Bionic as of last week, and we started an Ubuntu SRU process into Xenial and Artful.</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> We expect the 18.2 to be present in Xenial and Artful within 2 weeks in your cloud, so if you are waiting on a feature, it won't be very long.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> Also in-progress are some of rharper's zfs fixes, and some exception callback cleanup that will affect Azure, EC2, OpenStack and Scaleway clouds.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/fix/cc_resizefs_on_zfs_root">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/fix/cc_resizefs_on_zfs_root</a></p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/342007">https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/342007</a></p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> And we are doing our part to finally purge net-tools dependencies from cloud-init (in favor of iproute2)</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/342428">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/342428</a></p> -<p>16:24 <code>&lt;rharper&gt;</code> blackboxsw: I responded to your ip -6 route q from last week, did you see that ?</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> rharper: haven't yet, but I'll grab those comments today for sure (I think I missed some of your earlier review comments)</p> -<p>16:24 <code>&lt;rharper&gt;</code> ok</p> -<p>16:25 <code>&lt;rharper&gt;</code> the tl;dr for that one is that you want this: ip -6 route list table all</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> ahh excellent, I was wondering why we were missing content for local routes etc</p> -<p>16:25 <code>&lt;rharper&gt;</code> right</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> thanks</p> -<p>16:25 <code>&lt;rharper&gt;</code> np</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> also, on our continuous integration front , powersj has put up a branch that I'd like to see us land with some ssh improvements</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/342010">https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/342010</a></p> -<p>16:26 <code>&lt;powersj&gt;</code> :) yep</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> any other in-progress work worth noting?</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> Intereseted parties can always track our public trello board for a glimpse of what we are working on</p> -<p>16:27 <code>&lt;blackboxsw&gt;</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:27 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 minutes)</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> We'll all have eyes glued to the screen for the next 30 minutes for rants, feature discussion and bug work.</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> With that, the floor is open for any topics. Thanks for tuning in.</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> My day today will be Ubuntu SRU(stable release update)-related, so I'm getting on rharper's zfs branch now and they running a couple manual tests on ec2/azure/openstack</p> -<p>16:30 <code>&lt;rharper&gt;</code> +1</p> -<p>16:30 <code>&lt;rharper&gt;</code> oh, the ntp-spec update is ready for review and testing</p> -<p>16:31 <code>&lt;rharper&gt;</code> <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/339438">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/339438</a></p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> ahh +1 we want that in too</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/339438">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/339438</a></p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> Alrighty, happy spring break all.</p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> Next meeting will be two weeks from today.</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> powersj: rharper 4/16 look good for folks?</p> -<p>17:03 <code>&lt;powersj&gt;</code> +1 from me</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-03-19T16:02:00+00:002018-03-19T16:02:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-03-19:/status-2018-03-19.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 19 Mar at 16:02 &mdash; 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><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 19 Mar at 16:02 &mdash; 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>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status meeting</p> -<p>16:02 <code>&lt;meetingology&gt;</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>&lt;meetingology&gt;</code> </p> -<p>16:02 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:03 <code>&lt;blackboxsw&gt;</code> ok, let's kick off this cloud-init bi-weekly meeting. welcome all!</p> -<p>16:04 <code>&lt;dpb1&gt;</code> o/</p> -<p>16:04 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:05 <code>&lt;dpb1&gt;</code> smoser vacation specifically</p> -<p>16:05 <code>&lt;blackboxsw&gt;</code> hehe. Generally we're tracking high-points of what lands in our trello board</p> -<p>16:05 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> but from changelogs folks have made progress on azure, vmware and FreeBSD deployment targets</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> - netplan: render bridge port-priority values (LP: #1735821)</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> - net: recognize iscsi root cases without ip= on kernel command line.</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> (LP: #1752391)</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> - util: Fix subp regression. Allow specifying subp command as a string.</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> (LP: #1755965)</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> - This commit fixes get_hostname on the AzureDataSource.</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> [Douglas Jordan] (LP: #1754495)</p> -<p>16:06 <code>&lt;ubot5</code>&gt;` 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>&lt;blackboxsw&gt;</code> - shellify: raise TypeError on bad input.</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> - FreeBSD: Set hostname to FQDN. [Dominic Schlegel] (LP: #1753499)</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> - Make salt minion module work on FreeBSD.</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> [Dominic Schlegel] (LP: #1721503)</p> -<p>16:06 <code>&lt;ubot5</code>&gt;` 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>&lt;blackboxsw&gt;</code> - set_hostname: When present in metadata, set it before network bringup.</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> (LP: #1746455) VMWare</p> -<p>16:06 <code>&lt;ubot5</code>&gt;` 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>&lt;blackboxsw&gt;</code> - cc_snap: Add new module to install and configure snapd and snap</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> packages.</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> - doc: fix all warnings issued by 'tox -e doc'</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> - tests: Make pylint happy and fix python2.6 uses of assertRaisesRegex.</p> -<p>16:06 <code>&lt;ubot5</code>&gt;` 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>&lt;blackboxsw&gt;</code> - tests: fix run_tree and bddeb</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> - tests: Fix some warnings in tests that popped up with newer python.</p> -<p>16:06 <code>&lt;ubot5</code>&gt;` 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>&lt;blackboxsw&gt;</code> - tests: fix flakes warning for unused variable</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> - tests: patch leaked stderr messages from snap unit tests</p> -<p>16:06 <code>&lt;ubot5</code>&gt;` 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>&lt;blackboxsw&gt;</code> - tests: Centralize and re-use skipTest based on json schema presense.</p> -<p>16:06 <code>&lt;ubot5</code>&gt;` 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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> On the ubuntu side of the house we got tip of tree published into Bionic thusday &amp; 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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> Ubuntu is getting a number of new cloud-config modules:</p> -<p>16:13 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> - new cc_ubuntu_drivers: support to install 3rd party drivers on install</p> -<p>16:15 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> these should be landing in the week(s) to come</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> and cc_snap landed already</p> -<p>16:17 <code>&lt;blackboxsw&gt;</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>&lt;rharper&gt;</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>&lt;smoser&gt;</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>&lt;rharper&gt;</code> heh</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> maybe we can toggle between the two modulus 2 :)</p> -<p>16:18 <code>&lt;rharper&gt;</code> sorry, didn't meant to disturb the flow</p> -<p>16:19 <code>&lt;rharper&gt;</code> continue</p> -<p>16:19 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> anything to free up developer time will give us more time for reviews/code</p> -<p>16:19 <code>&lt;ajorg&gt;</code> should vendor-specific modules be shipped in a separate package?</p> -<p>16:20 <code>&lt;smoser&gt;</code> vendor specific modules ?</p> -<p>16:20 <code>&lt;ajorg&gt;</code> ubuntu_advantage</p> -<p>16:22 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> each module has a distro attribute defined as to whether or not it will even run</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> so we have spacewalk, zypper_repos etc</p> -<p>16:24 <code>&lt;smoser&gt;</code> and cloud.cfg is rendered based on knowledge of the distro</p> -<p>16:24 <code>&lt;smoser&gt;</code> so ubuntu_advantage wont even be in the list of config modules</p> -<p>16:24 <code>&lt;smoser&gt;</code> having a static config module list is WIN in this case (but pain elsewhere)</p> -<p>16:25 <code>&lt;smoser&gt;</code> at some point whe may have a more dynamic config module list.</p> -<p>16:25 <code>&lt;smoser&gt;</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>&lt;blackboxsw&gt;</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>&lt;ajorg&gt;</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>&lt;blackboxsw&gt;</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>&lt;smoser&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> so cloud-init is getting it's grubby hands into a couple of more clouds shortly.</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> s/it's/its/</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> it's nice to see the adoption continue to grow</p> -<p>16:31 <code>&lt;smoser&gt;</code> looks like someone followed up on hetzner</p> -<p>16:31 <code>&lt;smoser&gt;</code> so that hopefully is ready to land</p> -<p>16:31 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> I <em>think</em> that's all for in-progress development at the moment.</p> -<p>16:33 <code>&lt;smoser&gt;</code> man we need to fix that pylint thing.</p> -<p>16:33 <code>&lt;smoser&gt;</code> did you mention ?</p> -<p>16:33 <code>&lt;rharper&gt;</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>&lt;blackboxsw&gt;</code> Anything else that should be noted by anyone?</p> -<p>16:33 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> oops</p> -<p>16:34 <code>&lt;smoser&gt;</code> cloudinit/config/cc_puppet.py:143: [W1505(deprecated-method), handle] Using deprecated method readfp()</p> -<p>16:34 <code>&lt;blackboxsw&gt;</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>&lt;smoser&gt;</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>&lt;blackboxsw&gt;</code> yeah how much should we freeze our deps?</p> -<p>16:35 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> but I don't really know whether it's worth us 'pinning' everything</p> -<p>16:36 <code>&lt;smoser&gt;</code> i think pinning everything is generally the best practice for this sort of thing now.</p> -<p>16:37 <code>&lt;smoser&gt;</code> oh my.</p> -<p>16:37 <code>&lt;blackboxsw&gt;</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>&lt;smoser&gt;</code> blackboxsw: did you know you accidently fixed that in trunk ?</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> smoser: I know I intentionally added a pylint ignore on that to come back and address it today.</p> -<p>16:38 <code>&lt;ajorg&gt;</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>&lt;smoser&gt;</code> oh ko. i see.</p> -<p>16:39 <code>&lt;smoser&gt;</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>&lt;smoser&gt;</code> there is the "good" break, where new upload to pypi identifies some lingering bug</p> -<p>16:40 <code>&lt;blackboxsw&gt;</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>&lt;smoser&gt;</code> but also the "bad" break where some upload breaks your c-i for invalid reason.</p> -<p>16:42 <code>&lt;smoser&gt;</code> one huge advantage to pinning is the ability to re-create things.</p> -<p>16:42 <code>&lt;blackboxsw&gt;</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>&lt;smoser&gt;</code> ie, if you were looking to it bisect something...</p> -<p>16:42 <code>&lt;smoser&gt;</code> git bisect</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> I should transition to the office hours topic so we can continue discussion</p> -<p>16:43 <code>&lt;smoser&gt;</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>&lt;smoser&gt;</code> sure we can transition to office hours.</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> #topic Office hours (next ~30 mins)</p> -<p>16:43 <code>&lt;smoser&gt;</code> but yeah... i want c-i on tip to not just start failing.</p> -<p>16:44 <code>&lt;stanguturi&gt;</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>&lt;ubot5</code>&gt;` 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>&lt;blackboxsw&gt;</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>&lt;smoser&gt;</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>&lt;blackboxsw&gt;</code> +1 smoser I'll put a card up for that</p> -<p>16:46 <code>&lt;smoser&gt;</code> stanguturi: your suggestion there is not a bad idea at all.</p> -<p>16:46 <code>&lt;blackboxsw&gt;</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>&lt;smoser&gt;</code> the desire to have cloud-init tell the platform/datasource that it failed or succeeded is valid.</p> -<p>16:47 <code>&lt;smoser&gt;</code> with MAAS, that his done via reporting</p> -<p>16:47 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;smoser&gt;</code> cloud-init reports status and results via a Reporter.</p> -<p>16:47 <code>&lt;smoser&gt;</code> dojordan (i think) had also put up a request for a reproter module on azure.</p> -<p>16:47 <code>&lt;smoser&gt;</code> so we <em>do</em> kind of have the function you're after in place.</p> -<p>16:48 <code>&lt;stanguturi&gt;</code> smoser: ok. Any inputs / examples of using it will be really great.</p> -<p>16:50 <code>&lt;smoser&gt;</code> stanguturi: well, the reporter interface is pretty simple. you can cloudinit/reporting/handlers.py</p> -<p>16:51 <code>&lt;smoser&gt;</code> blackboxsw: <a href="http://paste.ubuntu.com/p/6KjDX8WHQH/">http://paste.ubuntu.com/p/6KjDX8WHQH/</a></p> -<p>16:51 <code>&lt;smoser&gt;</code> did you intend boht of those changes ?</p> -<p>16:51 <code>&lt;stanguturi&gt;</code> smoser: ok. Then do I need to write a new handler for our DataSource?</p> -<p>16:52 <code>&lt;smoser&gt;</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>&lt;blackboxsw&gt;</code> wow smoser, no</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> wow, ok, I'll put up a branch to fix that</p> -<p>16:52 <code>&lt;stanguturi&gt;</code> smoser: ok. Will work on that.</p> -<p>16:52 <code>&lt;smoser&gt;</code> ok.</p> -<p>16:53 <code>&lt;stanguturi&gt;</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>&lt;smoser&gt;</code> stanguturi: do you find this is actually needed ?</p> -<p>16:53 <code>&lt;smoser&gt;</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>&lt;smoser&gt;</code> which i can't seem to believe is all that a common situation in VMs</p> -<p>16:54 <code>&lt;stanguturi&gt;</code> smoser: Yeah. We need this for 'VMware guest customization workflow'.</p> -<p>16:54 <code>&lt;dpb1&gt;</code> smoser: oh man, I hope not</p> -<p>16:54 <code>&lt;stanguturi&gt;</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>&lt;smoser&gt;</code> stanguturi: does it actually solve a <em>current</em> problem for you ?</p> -<p>16:55 <code>&lt;stanguturi&gt;</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>&lt;smoser&gt;</code> or one that originally came in from a decade ago</p> -<p>16:55 <code>&lt;stanguturi&gt;</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>&lt;smoser&gt;</code> hm... so my sugestion is really to stop allowing that :)</p> -<p>16:56 <code>&lt;stanguturi&gt;</code> smoser: Oh ok. Can you please add a comment to that merge request just for the record.</p> -<p>16:56 <code>&lt;smoser&gt;</code> i very well could be wrong</p> -<p>16:56 <code>&lt;smoser&gt;</code> but the only time that i ever had to deal with this was when dual booting</p> -<p>16:56 <code>&lt;smoser&gt;</code> with windows specifically</p> -<p>16:57 <code>&lt;stanguturi&gt;</code> smoser: ok.</p> -<p>16:57 <code>&lt;smoser&gt;</code> am i wrong there ?</p> -<p>16:57 <code>&lt;smoser&gt;</code> i really <em>could</em> be.</p> -<p>16:58 <code>&lt;stanguturi&gt;</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>&lt;smoser&gt;</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>&lt;smoser&gt;</code> stanguturi: yeah. i understand that.</p> -<p>16:58 <code>&lt;stanguturi&gt;</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>&lt;stanguturi&gt;</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>&lt;stanguturi&gt;</code> smoser: And when is the cloud-init 18.2 scheduled for release? 3/22?</p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> probably a good time for us to bring that up</p> -<p>17:01 <code>&lt;smoser&gt;</code> yeah. whoops.</p> -<p>17:01 <code>&lt;smoser&gt;</code> :)</p> -<p>17:01 <code>&lt;smoser&gt;</code> 18.2 is scheduled for 3/22 (thursday)</p> -<p>17:02 <code>&lt;blackboxsw&gt;</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>&lt;smoser&gt;</code> but amoung our internall team we decided to push that to 3/27</p> -<p>17:02 <code>&lt;stanguturi&gt;</code> smoser: ok. Thanks for the update.</p> -<p>17:02 <code>&lt;blackboxsw&gt;</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>&lt;smoser&gt;</code> we will send an email today or tomrrow witih "pending release" like subject like we've done before.</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> dpb1: others any objections to cutting the 18.2 release on Tuesday 3/27?</p> -<p>17:03 <code>&lt;dpb1&gt;</code> none</p> -<p>17:04 * blackboxsw adds the upcoming date to the topic</p> -<p>17:05 <code>&lt;blackboxsw&gt;</code> ... ok, folks interested in discussing today?</p> -<p>17:08 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io">https://cloud-init.github.io</a></p> -<p>17:09 <code>&lt;blackboxsw&gt;</code> The above link will have our captured logs for this meeting.</p> -<p>17:09 <code>&lt;blackboxsw&gt;</code> thanks again for tuning in</p> -<p>17:09 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-03-05T17:00:00+00:002018-03-05T17:00:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-03-05:/status-2018-03-05.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 05 Mar at 17:00 &mdash; 17:53 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-03-05-17.00.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-03-05-17.00.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 17:02.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://lists.launchpad.net/cloud-init/msg00144.html">https://lists.launchpad.net/cloud-init/msg00144 …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 05 Mar at 17:00 &mdash; 17:53 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-03-05-17.00.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-03-05-17.00.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 17:02.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://lists.launchpad.net/cloud-init/msg00144.html">https://lists.launchpad.net/cloud-init/msg00144.html</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 17:12.</p> -<ul> -<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://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="https://bugs.launchpad.net/cloud-init/+bug/1724128">https://bugs.launchpad.net/cloud-init/+bug/1724128</a> </li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1750780">https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1750780</a> </li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1667831">https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1667831</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 (58)</li> -<li>stanguturi (13)</li> -<li>smoser (7)</li> -<li>ubot5` (7)</li> -<li>meetingology (3)</li> -<li>powersj (1)</li> -<li>rharper (1)</li> -</ul> -<h2>Full Log</h2> -<p>17:00 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status meeting</p> -<p>17:00 <code>&lt;meetingology&gt;</code> Meeting started Mon Mar 5 17:00:58 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>17:00 <code>&lt;meetingology&gt;</code> </p> -<p>17:00 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>17:01 <code>&lt;powersj&gt;</code> o/</p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> hey folks welcome to another episode of Cloud-init status updates. Thanks for coming.</p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> Since we had a status meeting just prior to the cloud-init upstream release last week there won't be a ton of updates this week.</p> -<p>17:02 <code>&lt;rharper&gt;</code> o--</p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> without further ado</p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> highlight of the last week was the upstream 18.1 release getting cut! Great work folks on getting branches landed in tip proir to release</p> -<p>17:03 * blackboxsw grabs powersj highlights</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> cloud-init 18.1 released!</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> ds-identify: Fix searching for iso9660 OVF cdroms for vmware (LP: #1749980)</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> Documented chef example incorrectly represented apt source configuration for chef install</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> SUSE: Fix groups used for ownership of cloud-init.log (Robert Schweikert)</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> OVF: Fix VMware support for 64-bit platforms (Sankar Tanguturi)</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> Salt: configure grains in grains file rather than in minion config (Daniel Wallace)</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> Implement puppet 4 support (Romanos Skiadas)</p> -<p>17:03 <code>&lt;ubot5</code>&gt;` Launchpad bug 1749980 in cloud-init "ds-identify doesn't properly detect ISO" [High,Fix released] <a href="https://launchpad.net/bugs/1749980">https://launchpad.net/bugs/1749980</a></p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> For those that didn't see the email:</p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> #link <a href="https://lists.launchpad.net/cloud-init/msg00144.html">https://lists.launchpad.net/cloud-init/msg00144.html</a></p> -<p>17:04 <code>&lt;smoser&gt;</code> o/</p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> thanks again stanguturi Akihiko and Max Illfelder</p> -<p>17:06 <code>&lt;blackboxsw&gt;</code> in the ubuntu side of the house we published 18.1 to the Bionic series so clouds now have this by default in bionic images</p> -<p>17:06 <code>&lt;blackboxsw&gt;</code> Also on the ubuntu-side of the house we finalized an SRU (stable release update) of 17.2.35.2 into both Xenial and Artful, so xenial-updates and artful-updates should have 17.2.35 available (which is only a few commits earlier than the 18.1 release)</p> -<p>17:10 <code>&lt;blackboxsw&gt;</code> Also in tip post 18.1 we had significant contribution from partners</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> Simplify some comparisions. [Rémy Léone]</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> Change some list creation and population to literal. [Rémy Léone]</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> GCE: fix reading of user-data that is not base64 encoded.</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> doc: fix chef install from apt packages example in RTD.</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> Implement puppet 4 support [Romanos Skiadas]</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> subp: Fix subp usage with non-ascii characters when no system locale.</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> salt: configure grains in grains file rather than in minion config. [Daniel Wallace]</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> (sorry took me a while to dig up the git formatting options)</p> -<p>17:12 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>17:12 <code>&lt;blackboxsw&gt;</code> We have some existing branches we are trying to get review feedback to folks on:</p> -<p>17:12 <code>&lt;blackboxsw&gt;</code> #link <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a></p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> Are there reviews that folks feel need some attention this week?</p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> Internally, we work on items in the TODO/Doing lane of our trello board here:</p> -<p>17:13 <code>&lt;blackboxsw&gt;</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>17:14 <code>&lt;stanguturi&gt;</code> @blackboxsw: I have one request about the bug <a href="https://bugs.launchpad.net/cloud-init/+bug/1724128">https://bugs.launchpad.net/cloud-init/+bug/1724128</a> Any inputs from cloud-init team will be great.</p> -<p>17:14 <code>&lt;ubot5</code>&gt;` Ubuntu bug 1724128 in open-vm-tools (Ubuntu) "Need a Success / Failure notification mechanism when cloud-init finishes." [Undecided,New]</p> -<p>17:15 <code>&lt;blackboxsw&gt;</code> so we have some Snap module development incoming on chrony support, snappy support, vsphere early hostname support</p> -<p>17:16 <code>&lt;blackboxsw&gt;</code> stanguturi: checking</p> -<p>17:17 <code>&lt;stanguturi&gt;</code> blackboxsw: Thanks. I discussed this last year in August in cloud-init meeting. Logged this bug long time back. But for some reason, it was not tagged with the proper project. My bad.</p> -<p>17:18 <code>&lt;blackboxsw&gt;</code> stanguturi: we have an external notification mechanism for scripts to information about when cloud-init has finally completed via "cloud-init status --wait" .... hrm trying to discuss here about alternative mechanisms internal to cloud-init</p> -<p>17:21 <code>&lt;blackboxsw&gt;</code> stanguturi: ok we can probably add a publish/subscription mechanism in cloud-init proper for internal eventing that'd get this done.</p> -<p>17:21 <code>&lt;stanguturi&gt;</code> @blackboxsw: Thanks a lot.</p> -<p>17:21 <code>&lt;blackboxsw&gt;</code> I've added a topic to our meetings this week to discuss the approach that could make this happen.</p> -<p>17:21 <code>&lt;blackboxsw&gt;</code> We'll comment on the bug/mailing list with an approach proposal</p> -<p>17:22 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/+bug/1724128">https://bugs.launchpad.net/cloud-init/+bug/1724128</a></p> -<p>17:22 <code>&lt;ubot5</code>&gt;` Ubuntu bug 1724128 in open-vm-tools (Ubuntu) "Need a Success / Failure notification mechanism when cloud-init finishes." [Undecided,New]</p> -<p>17:22 <code>&lt;blackboxsw&gt;</code> just so I capture the link</p> -<p>17:23 <code>&lt;stanguturi&gt;</code> @blackboxsw: Thanks I have got another request. I am working on <a href="https://code.launchpad.net/~sankaraditya/cloud-init/+git/cloud-init/+ref/vmware-customize-utc-time">https://code.launchpad.net/~sankaraditya/cloud-init/+git/cloud-init/+ref/vmware-customize-utc-time</a> to add some 'UTC customizations'. Got some review comments from Scott Moser. Can you please provide some pointers to any existing / tests / procedure to add new functionality to distro class</p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> stanguturi: re-reading ... and checking out the existing cloudinit.distro base module for utc /tz specifics</p> -<p>17:29 <code>&lt;stanguturi&gt;</code> @blackboxsw: We just want to customize /etc/default/rcS file with some settings on debian platforms.</p> -<p>17:36 <code>&lt;blackboxsw&gt;</code> hrm, so I'm conflicted with your branch by seeing that Distro.tz_zone_dir sets that path for for that distro for where TZ information is being configured. I think I'm missing why UTC=yes|no is needed versus Debian.set_timezone</p> -<p>17:38 <code>&lt;stanguturi&gt;</code> @blackboxsw: This is actually related to 'hwclock'. The key value that needs to be set in /etc/default/rcS is 'UTC' but it's related to 'hwclock' setting.</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> for my suggestion on that initial review, I thought that we might need to allow for a Debian-specific method which would handle this additional/separate configuration file processing you were doing w/ /etc/default/rcS</p> -<p>17:40 <code>&lt;smoser&gt;</code> looking quicklyi it looks like at least recently the correct place to store that is /etc/default/hwclock</p> -<p>17:40 <code>&lt;smoser&gt;</code> /etc/default/rcS is read, but per /etc/init.d/hwclock.sh, it looks like /etc/default/hwclock is preferred</p> -<p>17:41 <code>&lt;smoser&gt;</code> but either way, wahat i think we really want is for the distro class to have a 'store_hwclock_timezone' or something</p> -<p>17:41 <code>&lt;smoser&gt;</code> and then you'd call into that.</p> -<p>17:42 <code>&lt;stanguturi&gt;</code> ok. Thanks Scott. Are there any extra test cases / test suites that I need to run if I am modifying the distro class?</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> as far as developing additional unit tests for a new distro method: I'd expect new feature methods to be covered in tests/unittests/test_distros/test_debian.py</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> also cloud-init summit action we haven't done yet is to move all unittests out of tests/unittests and under cloudinit proper</p> -<p>17:42 <code>&lt;smoser&gt;</code> +1 blackboxsw</p> -<p>17:44 <code>&lt;stanguturi&gt;</code> ok Will work on that.</p> -<p>17:44 <code>&lt;blackboxsw&gt;</code> I'll take that test migration action for any existing modules that are already tested under tests/unittests. The policy we were hoping is that for new modules added under "cloudinit" we'd add a cloudinit/somepath/tests/test_newmodule.py for each cloudinit/somepath/newmodule.py</p> -<p>17:45 <code>&lt;blackboxsw&gt;</code> so if you want to build on tests/unittests/test_distros/test_debian.py we'll pull that under cloudinit proper when we finally remove tests/unittests altogether</p> -<p>17:45 <code>&lt;blackboxsw&gt;</code> stanguturi: any other items?</p> -<p>17:46 <code>&lt;blackboxsw&gt;</code> otherwise I think we'll probably wrap up this meeting in a few minutes</p> -<p>17:46 <code>&lt;stanguturi&gt;</code> Yeah. I have one more item. Sorry. <a href="https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1750780">https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1750780</a></p> -<p>17:46 <code>&lt;ubot5</code>&gt;` Ubuntu bug 1750780 in open-vm-tools (Ubuntu Xenial) "Race with local file systems can make open-vm-tools fail to start" [Undecided,Triaged]</p> -<p>17:47 <code>&lt;blackboxsw&gt;</code> no worries at all stanguturi we like the interest</p> -<p>17:47 <code>&lt;stanguturi&gt;</code> We just noticed that on Ubuntu 18.04 VMs, open-vm-tools service doesn't work with cloud-init.</p> -<p>17:47 <code>&lt;stanguturi&gt;</code> We didn't have any issues on 17.10. But only found in 18.04</p> -<p>17:47 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1750780">https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1750780</a></p> -<p>17:48 <code>&lt;ubot5</code>&gt;` Ubuntu bug 1750780 in open-vm-tools (Ubuntu Xenial) "Race with local file systems can make open-vm-tools fail to start" [Undecided,Triaged]</p> -<p>17:48 <code>&lt;stanguturi&gt;</code> I first logged the bug <a href="https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1667831">https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1667831</a> and it was fixed and it was mentioned that now the bug 1750780 came up.</p> -<p>17:48 <code>&lt;ubot5</code>&gt;` Ubuntu bug 1667831 in open-vm-tools (Ubuntu) "cloud-init dependency for open-vm-tools service" [Undecided,Fix released]</p> -<p>17:51 <code>&lt;smoser&gt;</code> stanguturi: i'll talk with christian tomorrow about the bug there.</p> -<p>17:52 <code>&lt;stanguturi&gt;</code> ok Thanks Scott.</p> -<p>17:52 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1667831">https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1667831</a></p> -<p>17:52 <code>&lt;ubot5</code>&gt;` Ubuntu bug 1667831 in open-vm-tools (Ubuntu) "cloud-init dependency for open-vm-tools service" [Undecided,Fix released]</p> -<p>17:52 <code>&lt;blackboxsw&gt;</code> ok I think we'll have to call this meeting a close for this week. Thanks again stanguturi for the help/chat here.</p> -<p>17:53 <code>&lt;blackboxsw&gt;</code> as always I'll post this log to the site:</p> -<p>17:53 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io">https://cloud-init.github.io</a></p> -<p>17:53 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-02-16T16:08:00+00:002018-02-16T16:08:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-02-16:/status-2018-02-16.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 16 Feb at 16:08 &mdash; 17:18 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-02-16-16.08.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-02-16-16.08.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent changes</h3> -<p>The discussion about "Recent changes" started at 16:08.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://jenkins.ubuntu.com/server/view/cloud-init/">https://jenkins.ubuntu.com/server/view …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 16 Feb at 16:08 &mdash; 17:18 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-02-16-16.08.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-02-16-16.08.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent changes</h3> -<p>The discussion about "Recent changes" started at 16:08.</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> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:18.</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="https://bugs.launchpad.net/cloud-init/+bug/1749722">https://bugs.launchpad.net/cloud-init/+bug/1749722</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~rski/cloud-init/+git/cloud-init/+merge/312284">https://code.launchpad.net/~rski/cloud-init/+git/cloud-init/+merge/312284</a> </li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bug/1749722">https://bugs.launchpad.net/cloud-init/+bug/1749722</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~rski/cloud-init/+git/cloud-init/+merge/312284">https://code.launchpad.net/~rski/cloud-init/+git/cloud-init/+merge/312284</a> </li> -</ul> -<h3>cloud-init version 18.1 release (2/23/2018)</h3> -<p>The discussion about "cloud-init version 18.1 release (2/23/2018)" started at 16:27.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~sankaraditya/cloud-init/+git/cloud-init/+merge/337736">https://code.launchpad.net/~sankaraditya/cloud-init/+git/cloud-init/+merge/337736</a> </li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bug/1749980">https://bugs.launchpad.net/cloud-init/+bug/1749980</a> </li> -</ul> -<h3>Office hours (next ~30 mins)</h3> -<p>The discussion about "Office hours (next ~30 mins)" started at 16:42.</p> -<ul> -<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 (64)</li> -<li>stanguturi (19)</li> -<li>smoser (17)</li> -<li>ubot5 (6)</li> -<li>meetingology (4)</li> -<li>powersj (3)</li> -<li>rharper (2)</li> -<li>nacc (1)</li> -</ul> -<h2>Full Log</h2> -<p>16:04 <code>&lt;blackboxsw&gt;</code> hey folks thanks for joining in to another cloud-init biweekly status meeting</p> -<p>16:05 <code>&lt;blackboxsw&gt;</code> the early meeting day this week is to avoid hitting the upcoming US holiday on Monday</p> -<p>16:05 <code>&lt;blackboxsw&gt;</code> This meeting is probably going to be short, but we wanted to generate any discussion around the release we have scheduled for next week. I'll go through the following topics</p> -<p>16:05 <code>&lt;blackboxsw&gt;</code> recent changes, In-progress development, Release 18.1 Discussion, Office hours (30 mins)</p> -<p>16:05 <code>&lt;blackboxsw&gt;</code> Without further ado...</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status meeting</p> -<p>16:08 <code>&lt;meetingology&gt;</code> Meeting started Fri Feb 16 16:08:08 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:08 <code>&lt;meetingology&gt;</code> </p> -<p>16:08 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> much better thanks nacc</p> -<p>16:08 <code>&lt;nacc&gt;</code> blackboxsw: yw</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> #topic Recent changes</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> Cloud-init upstream team has been working on an SRU for Artful and Xenial.</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> We discovered a couple of SRU-blocking bugs on EC2 as well as cloud-init subcommands so we've landed a couple of fixes there which are queued for SRU now</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> * cloud-init status --wait blocks until all stages complete (LP: #1747965)</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> * SRU EC2 upgrade path fix for 'systemctl restart cloud-init.service' (LP:1748354)</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> * Fix ds-identify nocloud detection with bind mounted writable/system-data directory (LP: #1747070)</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> * Tests: include missing unitests in python2.6 environments. Fix py2.6 incompatilibilies</p> -<p>16:09 <code>&lt;ubot5&gt;</code> Launchpad bug 1747965 in cloud-init (Ubuntu) "cloud-init status reports done before boot is finished" [High,Fix released] <a href="https://launchpad.net/bugs/1747965">https://launchpad.net/bugs/1747965</a></p> -<p>16:09 <code>&lt;ubot5&gt;</code> Launchpad bug 1747070 in cloud-init "ds-identify does not see nocloud seed in core snap" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1747070">https://launchpad.net/bugs/1747070</a></p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> * Fixed centos cloud-init build and test tooliing</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> * SUSE: Fix groups used for ownership of cloud-init.log [RobertS]</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> thanks folks for continuing to push on quality of cloud-init releases.</p> -<p>16:12 <code>&lt;smoser&gt;</code> o/ thanks for starting blackboxsw</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> not sure if I'm missing any other content that has landed in the last week and a half</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> I also think powersj rharper may have sorted a couple of issues with storage on our common CI on Jenkins</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> #link <a href="https://jenkins.ubuntu.com/server/view/cloud-init/">https://jenkins.ubuntu.com/server/view/cloud-init/</a></p> -<p>16:14 <code>&lt;powersj&gt;</code> Yes CI is up and running again, I have more defensive statements in to prevent us from running out of storage</p> -<p>16:15 * blackboxsw is not sure, are there rumors we might have more hardware dedicated to jenkins in the future powersj ?</p> -<p>16:15 <code>&lt;powersj&gt;</code> We do, however it is our jenkins master that runs out of storage :\</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> ahh gotcha, SPOF</p> -<p>16:16 <code>&lt;powersj&gt;</code> yeah</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> ok, if no other work is 'complete'; let's jump topics</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> ahh forgot ryan landed</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> net: accept network-config in netplan format for renaming interfaces</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> per LP: #1709715</p> -<p>16:17 <code>&lt;ubot5&gt;</code> Launchpad bug 1709715 in cloud-init "cloud-init apply_net_config_names doesn't grok v2 configs" [Medium,Confirmed] <a href="https://launchpad.net/bugs/1709715">https://launchpad.net/bugs/1709715</a></p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> So we are working toward quality on the 18.1 release for next week.</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> Ubuntu specifically is finalizing verification on cloud-init 17.2.35 update for Xenial and Artful series (expectation is that this SRU will be public in 1 week). 17.2.35 is a snapshot of tip from a couple days ago</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> we've also published tip of cloud-init master to bionic to keep the development release up to date with latest cloud-init</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> current ongoing work as always is on our trello board. we tried tidying up the cards a bit</p> -<p>16:20 <code>&lt;blackboxsw&gt;</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:21 <code>&lt;blackboxsw&gt;</code> we have upcoming branches for a new snap cloud-config module for configuring and maintaining snap packages</p> -<p>16:21 <code>&lt;rharper&gt;</code> <a href="https://bugs.launchpad.net/cloud-init/+bug/1749722">https://bugs.launchpad.net/cloud-init/+bug/1749722</a></p> -<p>16:21 <code>&lt;ubot5&gt;</code> Ubuntu bug 1749722 in cloud-init "NTP: take into account systemd-timesyncd where present" [Medium,In progress]</p> -<p>16:21 <code>&lt;rharper&gt;</code> I'm actively working on that</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> this snap work will obsolete snappy and snap_config modules, so expect that they'll be deprecated. in 18.1 and dropped completely in 18.2</p> -<p>16:22 <code>&lt;smoser&gt;</code> <a href="https://code.launchpad.net/~rski/cloud-init/+git/cloud-init/+merge/312284">https://code.launchpad.net/~rski/cloud-init/+git/cloud-init/+merge/312284</a></p> -<p>16:22 <code>&lt;smoser&gt;</code> i just moved that back into review</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/+bug/1749722">https://bugs.launchpad.net/cloud-init/+bug/1749722</a></p> -<p>16:22 <code>&lt;smoser&gt;</code> hope to take a lookc at it today.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~rski/cloud-init/+git/cloud-init/+merge/312284">https://code.launchpad.net/~rski/cloud-init/+git/cloud-init/+merge/312284</a></p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> so per rharper's; chrony will be first class citizen in cloud-init</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> per cards in our trello board TODO lane, any card above the 18.1 release card (and anything in Doing/Review lane) is something we want to land in the 18.1 release</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> ... next topic so we can talk about release</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> #topic cloud-init version 18.1 release (2/23/2018)</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> next thursday we want to cut tip of cloud-init with any features we want to fold into the 18.1 release</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> this point in the meeting is a good opportunity for us to discuss features and bugs that any folks think are a priority for this release</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> smoser we saw some talk about archlinux support/updates, do we know whether we've gotten any updates about gaps/needs/bugs there?</p> -<p>16:29 <code>&lt;stanguturi&gt;</code> @blackboxsw: I have two requests. One for the merge request and one about the bug.</p> -<p>16:29 <code>&lt;smoser&gt;</code> blackboxsw: i've not seen any more than that developer asked about here in the channel.</p> -<p>16:30 <code>&lt;stanguturi&gt;</code> @blackboxsw: Let me know if I can post my questions here or discuss them offline.</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> stanguturi: please do discuss here. open forum :)</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> if it gets too long a discussion, we can take it to your branch or email</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~sankaraditya/cloud-init/+git/cloud-init/+merge/337736">https://code.launchpad.net/~sankaraditya/cloud-init/+git/cloud-init/+merge/337736</a></p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> for reference right ?</p> -<p>16:31 <code>&lt;stanguturi&gt;</code> @blackboxsw: Thanks. I have a merge request posted at <a href="https://code.launchpad.net/~sankaraditya/cloud-init/+git/cloud-init/+merge/337736">https://code.launchpad.net/~sankaraditya/cloud-init/+git/cloud-init/+merge/337736</a></p> -<p>16:31 <code>&lt;stanguturi&gt;</code> Want this to get into 18.1 It's a low-risk fix. Should not break anything.</p> -<p>16:32 <code>&lt;stanguturi&gt;</code> Also, found a bug in ds-identify . <a href="https://bugs.launchpad.net/cloud-init/+bug/1749980">https://bugs.launchpad.net/cloud-init/+bug/1749980</a></p> -<p>16:32 <code>&lt;ubot5&gt;</code> Ubuntu bug 1749980 in cloud-init "ds-identify doesn't properly detect ISO" [Undecided,New]</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> ok just glancing at your branch now stanguturi looks fairly straight forward, and as always I'd like to see some unit tests covering that changeset</p> -<p>16:33 <code>&lt;stanguturi&gt;</code> @blackboxsw: We already have unit tests for DataSourceOVF. This actually doesn't add any new functionality. The existing test cases should be sufficient enough.</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> we have existing unit tests in tests/unittests/test_ds_identify.py which should be easy to extend for the additional detection</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> in ds-identify</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> yeah I was thinking more about ds-identify specifically</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> all said though, that branch looks low-risk and we can probably get that landed before release.</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> I'll add a card to trello for us to shepherd that in.</p> -<p>16:35 <code>&lt;stanguturi&gt;</code> @blackboxsw: Great. Thanks.</p> -<p>16:36 <code>&lt;stanguturi&gt;</code> @blackboxsw: Also I have a question about <a href="https://bugs.launchpad.net/cloud-init/+bug/1749980">https://bugs.launchpad.net/cloud-init/+bug/1749980</a> Any inputs will be great.</p> -<p>16:36 <code>&lt;ubot5&gt;</code> Ubuntu bug 1749980 in cloud-init "ds-identify doesn't properly detect ISO" [Undecided,New]</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/+bug/1749980">https://bugs.launchpad.net/cloud-init/+bug/1749980</a></p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> looking</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> ohh good stanguturi we'll sort that bug and either provide more information on this</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> for that bug discussion, let's move it to the "office hours" topic which comes up next</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> I'd like smoser rharper to peek at that too</p> -<p>16:38 <code>&lt;stanguturi&gt;</code> @blackboxsw: Ok. Sure. Thanks</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> any other topics, branches or bugs that folks are itching to get in for 18.1 release?</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> kpcyrd: any opdates or concerns on archlinux that you are aware of currently?</p> -<p>16:42 <code>&lt;smoser&gt;</code> stanguturi: you can run a command there now ?</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> let's transition to office hours now</p> -<p>16:42 <code>&lt;smoser&gt;</code> 2 things</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> #topic Office hours (next ~30 mins)</p> -<p>16:43 <code>&lt;stanguturi&gt;</code> @smoser: Sorry. Didn't quite get the question.</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> And thanks all for joining. Any burning questions, bugs, branches that need discussion can be brought up now.</p> -<p>16:44 <code>&lt;stanguturi&gt;</code> @smoser: Oh. Are you asking if I can run any commands in my virtual machine right now.? Yeah. Sure.</p> -<p>16:44 <code>&lt;smoser&gt;</code> stanguturi: can you run stuff int hat system ?</p> -<p>16:44 <code>&lt;smoser&gt;</code> a.) cat /run/cloud-init/ds-identify.log</p> -<p>16:44 <code>&lt;smoser&gt;</code> b.) idstr="<a href="http://schemas.dmtf.org/ovf/environment/1">http://schemas.dmtf.org/ovf/environment/1</a>"</p> -<p>16:45 <code>&lt;smoser&gt;</code> grep --quiet --ignore-case "$idstr" /dev/sr0</p> -<p>16:45 <code>&lt;smoser&gt;</code> grep --quiet --ignore-case "$idstr" /dev/sr0 &amp;&amp; echo y || echo n</p> -<p>16:46 <code>&lt;smoser&gt;</code> stanguturi: basically the 'is_cdrom_ovf' should have gone down the path into that grep of the cdrom block device</p> -<p>16:48 <code>&lt;stanguturi&gt;</code> @smoser: grep --quiet --ignore-case "$idstr" /dev/sr0 returned "grep: /dev/sr0: Input/output error"</p> -<p>16:48 <code>&lt;stanguturi&gt;</code> @smoser: grep --quiet --ignore-case "$idstr" /dev/sr0 &amp;&amp; echo y || echo n returned "grep: /dev/sr0: Input/output error and then new line and then n'</p> -<p>16:48 <code>&lt;meetingology&gt;</code> stanguturi: Error: No closing quotation</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> heh thanks meetingology</p> -<p>16:50 <code>&lt;stanguturi&gt;</code> @smoser: Actually, read_fs_info doesn't DI_ISO9660_DEVS in my system. and because of this, dscheck_OVF returns DS_NOT_FOUND.</p> -<p>16:51 <code>&lt;smoser&gt;</code> stanguturi: what release are you on ?</p> -<p>16:51 <code>&lt;stanguturi&gt;</code> Trying it on 17.04 zesty desktop</p> -<p>16:52 <code>&lt;stanguturi&gt;</code> and tried with top of the tree code in cloud-init.</p> -<p>16:56 <code>&lt;smoser&gt;</code> stanguturi: could you potentially let me in via ssh ?</p> -<p>16:57 <code>&lt;stanguturi&gt;</code> @smoser: Sorry. It's on my private network. Will not be able to provide ssh.</p> -<p>16:58 <code>&lt;stanguturi&gt;</code> @smoser: We can do a webex conference if you want.</p> -<p>17:03 <code>&lt;smoser&gt;</code> stanguturi: can you ssh out of the node ?</p> -<p>17:03 <code>&lt;stanguturi&gt;</code> @smoser: Yes.</p> -<p>17:07 <code>&lt;smoser&gt;</code> ok. /query window</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> ok this triage will continue. if there are no other pressing bugs/concerns, we'll close out this meeting and keep pushing toward 18.1 upstream release next thursday</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> thanks again for your time folks. I'll post these minutes to the cloud-init github page</p> -<p>17:12 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io">https://cloud-init.github.io</a></p> -<p>17:17 <code>&lt;blackboxsw&gt;</code> next meeting march 5th same "bat time" same "bat channel"</p> -<p>17:18 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-01-22T16:08:00+00:002018-01-22T16:08:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-01-22:/status-2018-01-22.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 22 Jan at 16:08 &mdash; 17:16 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-01-22-16.08.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-01-22-16.08.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent changes</h3> -<p>The discussion about "Recent changes" started at 16:10.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://github.com/boto/botocore/issues/1351">https://github.com/boto/botocore/issues …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 22 Jan at 16:08 &mdash; 17:16 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-01-22-16.08.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-01-22-16.08.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent changes</h3> -<p>The discussion about "Recent changes" started at 16:10.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://github.com/boto/botocore/issues/1351">https://github.com/boto/botocore/issues/1351</a> </li> -<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>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:24.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~dojordan/cloud-init/+git/cloud-init/+merge/334341">https://code.launchpad.net/~dojordan/cloud-init/+git/cloud-init/+merge/334341</a> </li> -<li><strong>LINK</strong>: <a href="https://jenkins.ubuntu.com/server/view/cloud-init/job/cloud-init-ci-nightly/">https://jenkins.ubuntu.com/server/view/cloud-init/job/cloud-init-ci-nightly/</a> </li> -</ul> -<h3>Office Hours (next 30 minutes)</h3> -<p>The discussion about "Office Hours (next 30 minutes)" started at 16:45.</p> -<ul> -<li><strong>LINK</strong>: <a href="http://paste.ubuntu.com/26438334/">http://paste.ubuntu.com/26438334/</a> </li> -<li><strong>LINK</strong>: <a href="http://paste.ubuntu.com/26438334/">http://paste.ubuntu.com/26438334/</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 (83)</li> -<li>smoser (23)</li> -<li>ajorg (16)</li> -<li>powersj (10)</li> -<li>ubot5 (6)</li> -<li>meetingology (3)</li> -<li>rharper (1)</li> -</ul> -<h2>Full Log</h2> -<p>16:08 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status meeting</p> -<p>16:08 <code>&lt;meetingology&gt;</code> Meeting started Mon Jan 22 16:08:22 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:08 <code>&lt;meetingology&gt;</code> </p> -<p>16:08 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> certianly ajorg :) (on office hours)</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> Welcome to another episode of cloud-init bi-weekly status. We'll chat about about cloud-init updates and in progress work, and we'l drop into office hours for ongoing discussions/bug work etc.</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> #topic Recent changes</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> Just walking through git-log for what we have committed in the last couple of weeks, here's the brief summary</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> thx smoser</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - shorten the message in the exception per powersj feedback</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - Use the same botocore session so the patched changes stick.</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - fix bad use of %</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - Fix console_log, improve comments and raise PlatformError on.</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - tests: Fix EC2 Platform to return console output as bytes.</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - tests: remove zesty as supported OS to test [Joshua Powers]</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - Do not log warning on config files that represent None. (LP: #1742479)</p> -<p>16:12 <code>&lt;ubot5&gt;</code> Launchpad bug 1742479 in cloud-init (Ubuntu) "setting manual_cache_clean causes warning" [Medium,Fix released] <a href="https://launchpad.net/bugs/1742479">https://launchpad.net/bugs/1742479</a></p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - tests: Use git hash pip dependency format for pylxd.</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - tests: add integration requirements text file [Joshua Powers]</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - MAAS: add check_instance_id based off oauth tokens. (LP: #1712680)</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - tests: update apt sources list test [Joshua Powers]</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - tests: clean up image properties [Joshua Powers]</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - tests: rename test ssh keys to avoid appearance of leaking private keys.</p> -<p>16:12 <code>&lt;ubot5&gt;</code> Launchpad bug 1712680 in maas-images "cloud-init re-generates network config every reboot overwriting manual admin changes on CentOS." [Undecided,New] <a href="https://launchpad.net/bugs/1712680">https://launchpad.net/bugs/1712680</a></p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> [Joshua Powers]</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - tests: Enable AWS EC2 Integration Testing [Joshua Powers]</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - cli: cloud-init clean handles symlinks (LP: #1741093)</p> -<p>16:12 <code>&lt;ubot5&gt;</code> Launchpad bug 1741093 in cloud-init "cloud-init clean traceback on instance dir symlink" [Low,Fix committed] <a href="https://launchpad.net/bugs/1741093">https://launchpad.net/bugs/1741093</a></p> -<p>16:13 <code>&lt;ajorg&gt;</code> What's being patched in botocore?</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> So a number of changes went into integration test related work, separating out requirements files.</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> MAASDatasource now also has smarted cache handling based on oauth token renewal from the maas server</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> so botocore is used by integration tests only as a mechanism to talk to the instance under test... looking back at the specifics here</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> it might have just been shuffling out how and where we define the dependency</p> -<p>16:14 <code>&lt;smoser&gt;</code> blackboxsw: (my 'paste' to you was bad... <a href="http://paste.ubuntu.com/26438113/">http://paste.ubuntu.com/26438113/</a> is better, showing only those on master, not my local branch that was currently checked out )</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> heh, oopsie daisy let's paste again inline then</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> - tests: remove zesty as supported OS to test [Joshua Powers]</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> - Do not log warning on config files that represent None. (LP: #1742479)</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> - tests: Use git hash pip dependency format for pylxd.</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> - tests: add integration requirements text file [Joshua Powers]</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> - MAAS: add check_instance_id based off oauth tokens. (LP: #1712680)</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> - tests: update apt sources list test [Joshua Powers]</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> - tests: clean up image properties [Joshua Powers]</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> - tests: rename test ssh keys to avoid appearance of leaking private keys.</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> [Joshua Powers]</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> - tests: Enable AWS EC2 Integration Testing [Joshua Powers]</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> - cli: cloud-init clean handles symlinks (LP: #1741093)</p> -<p>16:15 <code>&lt;ubot5&gt;</code> Launchpad bug 1742479 in cloud-init (Ubuntu) "setting manual_cache_clean causes warning" [Medium,Fix released] <a href="https://launchpad.net/bugs/1742479">https://launchpad.net/bugs/1742479</a></p> -<p>16:15 <code>&lt;ubot5&gt;</code> Launchpad bug 1712680 in maas-images "cloud-init re-generates network config every reboot overwriting manual admin changes on CentOS." [Undecided,New] <a href="https://launchpad.net/bugs/1712680">https://launchpad.net/bugs/1712680</a></p> -<p>16:15 <code>&lt;ubot5&gt;</code> Launchpad bug 1741093 in cloud-init "cloud-init clean traceback on instance dir symlink" [Low,Fix committed] <a href="https://launchpad.net/bugs/1741093">https://launchpad.net/bugs/1741093</a></p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> ok the real deal, that looks better</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> ahh ajorg that interim commit message on botocore was about integration tests caching the session information during testing so we don't recreate that session with every ssh connection to the instance</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> just a little time savings per review comments on powersj branch I believe</p> -<p>16:17 <code>&lt;ajorg&gt;</code> okay, so nothing that needs to get upstreamed to botocore?</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> I don't think so, powersj smoser I have vague recollection of someone filing an upstream botocore issue. did we have to do that for something else though?</p> -<p>16:18 <code>&lt;powersj&gt;</code> <a href="https://github.com/boto/botocore/issues/1351">https://github.com/boto/botocore/issues/1351</a></p> -<p>16:18 <code>&lt;powersj&gt;</code> that was the issue smoser put in ^</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> nice recall powersj thanks.</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> #link <a href="https://github.com/boto/botocore/issues/1351">https://github.com/boto/botocore/issues/1351</a></p> -<p>16:20 <code>&lt;smoser&gt;</code> ajorg: you can read that bug. imo they have a data loss error, but not one that they can easily fix without causing failures in places that previously ran fine.</p> -<p>16:20 <code>&lt;ajorg&gt;</code> I'll ask them to re-open it.</p> -<p>16:21 <code>&lt;ajorg&gt;</code> At the very least they should answer your last.</p> -<p>16:21 <code>&lt;smoser&gt;</code> thanks.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> Generally anything significant that we have landed (and any inprogress work) should be available at the following link.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</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:23 <code>&lt;blackboxsw&gt;</code> anything else we should note over the last couple weeks?</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> otherwise I'll switch to ongoing work topic</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> As you may have seen last week, we've gotten through a few passes and discussions around dojordan's branch to define pre-provisioning</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~dojordan/cloud-init/+git/cloud-init/+merge/334341">https://code.launchpad.net/~dojordan/cloud-init/+git/cloud-init/+merge/334341</a></p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> some of that discussion resulted in a new context manager: EphemeralDHCPv4 to support a sandboxed dhclient request on an instance.</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> this context manager affects Ec2 datasource a bit as it encapsulates all of the dhcp request -&gt;` EphemeralIPV4Network calls that Ec2 was doing</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> there may be a couple other datasources that follow suit with this type of sandboxed dhcp request in weeks to come</p> -<p>16:28 <code>&lt;ajorg&gt;</code> glad it turned out to be generally useful rather than only specifically to ec2</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> absolutely</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> Some other in-progress bits look like we might try focusing a bit more on chrony support and gettting robjo's branches some more eyes.</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> and some work on Ubuntu snappy support per the snappy and snap config modules.</p> -<p>16:31 <code>&lt;smoser&gt;</code> dojordan: i just put one comment on your mp. /me thanks dojordan again for his patience.</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> rharper: smoser powersj anything more in the immediate pipeline that I'm missing/</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> ?</p> -<p>16:32 <code>&lt;smoser&gt;</code> blackboxsw: we should get the EphemeralDHCP thingy into the digital ocean datasource also.</p> -<p>16:32 <code>&lt;rharper&gt;</code> blackboxsw: a reply to the network discussion on the list from the azure folks and robjo</p> -<p>16:32 <code>&lt;ajorg&gt;</code> I took another look at <a href="https://code.launchpad.net/~yeazelm/cloud-init/+git/cloud-init/+merge/331897">https://code.launchpad.net/~yeazelm/cloud-init/+git/cloud-init/+merge/331897</a> and saw that origin/master seems to be failing some of the integration tests too.</p> -<p>16:32 <code>&lt;ajorg&gt;</code> (at least for me, locally, on a 16.04 instance)</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> ahhh right forgot about all your work there rharper, thanks!</p> -<p>16:33 <code>&lt;smoser&gt;</code> ajorg: <a href="https://jenkins.ubuntu.com/server/view/cloud-init/job/cloud-init-ci-nightly/">https://jenkins.ubuntu.com/server/view/cloud-init/job/cloud-init-ci-nightly/</a></p> -<p>16:33 <code>&lt;smoser&gt;</code> that is nigytly run of trunk</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> #link <a href="https://jenkins.ubuntu.com/server/view/cloud-init/job/cloud-init-ci-nightly/">https://jenkins.ubuntu.com/server/view/cloud-init/job/cloud-init-ci-nightly/</a></p> -<p>16:34 <code>&lt;ajorg&gt;</code> I'll try blackholing IMDS on my instance. Could be that's interfering with something.</p> -<p>16:35 <code>&lt;smoser&gt;</code> it is red, but 218 (green) and 219 (red) used the same git has on trunk (5cc0b19b8).</p> -<p>16:35 <code>&lt;ajorg&gt;</code> I'll follow up during office hours</p> -<p>16:36 <code>&lt;smoser&gt;</code> can you give me example of your failures ? we had "disk full" errors recently on our jenkins, so that might be the cause of the issue for 291.</p> -<p>16:36 <code>&lt;smoser&gt;</code> s/291/219/</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> I don't remember seeing that traceback recently. w/ warning messages present in cloud-init</p> -<p>16:36 <code>&lt;smoser&gt;</code> powersj: ? can you explain lxc timeout failure at</p> -<p>16:36 <code>&lt;smoser&gt;</code> <a href="https://jenkins.ubuntu.com/server/view/cloud-init/job/cloud-init-ci-nightly/219/consoleFull">https://jenkins.ubuntu.com/server/view/cloud-init/job/cloud-init-ci-nightly/219/consoleFull</a></p> -<p>16:37 <code>&lt;powersj&gt;</code> smoser: we discovered that our qemu-migration test was installing lxd from the archive and causing conflicts with the snap installed lxd</p> -<p>16:37 <code>&lt;powersj&gt;</code> I have a message to christian to prevent it, and I have already cleaned it up</p> -<p>16:37 <code>&lt;powersj&gt;</code> so new runs should pass</p> -<p>16:37 <code>&lt;ajorg&gt;</code> 2018-01-22 16:19:03,550 - tests.cloud_tests - WARNING - test case: modules/ssh_import_id failed TestSshImportId.test_no_stages_errors with: AssertionError: 1 != 0 : errors ['(\'ssh-import-id\', ProcessExecutionError("Unexpected error while running command.\nCommand: [\'sudo\', \'-Hu\', \'ubuntu\', \'ssh-import-id\', \'gh:powersj\', \'lp:smoser\']\nExit code: 1\nReason: -\nStdout: -\nStderr: -",))'] were encountered in stage m</p> -<p>16:38 <code>&lt;smoser&gt;</code> hm.. well, that will hit launchpad.net over https</p> -<p>16:38 <code>&lt;smoser&gt;</code> cloud-init-output.log probaly has more info (should be collected)</p> -<p>16:38 <code>&lt;powersj&gt;</code> the actual error is: File "/var/lib/jenkins/slaves/torkoal/workspace/cloud-init-ci-nightly/tests/cloud_tests/platforms/instances.py", line 142, in _wait_for_system</p> -<p>16:38 <code>&lt;powersj&gt;</code> raise OSError('timeout: after {}s system not started'.format(time))</p> -<p>16:38 <code>&lt;powersj&gt;</code> it is because when the qemu tests installed lxd it didn't initialize lxd networking</p> -<p>16:38 <code>&lt;powersj&gt;</code> so no IP is received</p> -<p>16:39 <code>&lt;smoser&gt;</code> ajorg: would you have had outbound access to launchpad https ? if not, then that'd be expected failure.</p> -<p>16:40 <code>&lt;smoser&gt;</code> oh, and i guess 'gh:powersj' (github)</p> -<p>16:40 <code>&lt;ajorg&gt;</code> smoser: I'll check some things, but in short yes. Maybe lxc is being weird?</p> -<p>16:40 <code>&lt;smoser&gt;</code> i dont like our user names in that test though...</p> -<p>16:40 <code>&lt;powersj&gt;</code> smoser: we could use the bot instead</p> -<p>16:42 <code>&lt;ajorg&gt;</code> smoser: it's a public ec2 instance with no special outbound rules, and I can connect to public https sites from a normal session.</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> hrm, ok let's chat about what we can do to anonymize or drop that type of test data if we can</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> probably time to kick over to office hours</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next 30 minutes)</p> -<p>16:45 <code>&lt;smoser&gt;</code> powersj: well, i think i'd prefer some public key that we state "no one has the private key for this."</p> -<p>16:46 <code>&lt;smoser&gt;</code> obviously we could lie about that, but one would <em>expect</em> that you and I would gain access to the system using our public keys.</p> -<p>16:46 <code>&lt;smoser&gt;</code> it doens't make me feel a lot better that a bot could/can.</p> -<p>16:47 <code>&lt;ajorg&gt;</code> Is there a way to limit integration testing to a specific test?</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> Feel free to bring up any topic/bugs/branches/features you'd like discussion on. We can also continue our discussion on the ssh key imports in teting</p> -<p>16:47 <code>&lt;ajorg&gt;</code> (takes a long time to run the full suite)</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> ajorg: yes</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> (reverse-i-search)`cloud_t': python3 -m tests.cloud_tests run --os-name=artful --platform=nocloud-kvm --preserve-data --data-dir=../results --verbose -t modules/locale -t modules/set_password</p> -<p>16:48 <code>&lt;ajorg&gt;</code> thanks, that should help</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> ajorg: you can specify the test names (like modules/set_password) and modules/locale in this test</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> yeah those are short ones I frequently test with</p> -<p>16:49 <code>&lt;smoser&gt;</code> <a href="http://paste.ubuntu.com/26438334/">http://paste.ubuntu.com/26438334/</a></p> -<p>16:49 <code>&lt;smoser&gt;</code> that is what i use. and yeah... we've discussed that integration test could be easier to run :)</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> #link <a href="http://paste.ubuntu.com/26438334/">http://paste.ubuntu.com/26438334/</a></p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> nice 1</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> smoser: to have a public key we know nobody has a private key for would that mean we'd need a separate github account (or maybe just an additional key associated w/ our bot account in gh</p> -<p>16:51 * blackboxsw checks github for authorizing multiple keys.</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> hrm, that wouldn't work as we need gh:ubuntu-server-bot (one key) n/m</p> -<p>16:52 <code>&lt;ajorg&gt;</code> I've got meetings most of today, so I'll have to follow up later. thanks everyone!</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> thanks ajorg</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> so, bot account for the time being is better than powersj owning the testing world ;)</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> but I'm not too concerned about it as this are supposed to be throw away instances</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> but I'm not too concerned about it as there instances under test are supposed to be throw away instances</p> -<p>17:00 <code>&lt;blackboxsw&gt;</code> <em>these instances</em>.... anyway</p> -<p>17:04 <code>&lt;smoser&gt;</code> blackboxsw: right. it would require users on both those services .</p> -<p>17:14 <code>&lt;blackboxsw&gt;</code> alrighty. think we're at the close of office hours. Last call?</p> -<p>17:16 <code>&lt;blackboxsw&gt;</code> Thanks for your time and contributions to cloud-init folks!</p> -<p>17:16 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-01-08T16:03:00+00:002018-01-08T16:03:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-01-08:/status-2018-01-08.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-inin bi-weekly status meeting, 08 Jan at 16:03 &mdash; 17:15 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-01-08-16.03.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-01-08-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="https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin">https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-inin bi-weekly status meeting, 08 Jan at 16:03 &mdash; 17:15 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-01-08-16.03.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-01-08-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="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="https://cloudinit.readthedocs.io/en/latest/topics/tests.html#ec2">https://cloudinit.readthedocs.io/en/latest/topics/tests.html#ec2</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:22.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://trello.com/c/AYaCdQyT">https://trello.com/c/AYaCdQyT</a> </li> -<li><strong>LINK</strong>: <a href="https://trello.com/c/xyqxyOxg">https://trello.com/c/xyqxyOxg</a> </li> -<li><strong>LINK</strong>: <a href="https://trello.com/c/AYaCdQyT/21-cloud-init-query-standardized-json-information">https://trello.com/c/AYaCdQyT/21-cloud-init-query-standardized-json-information</a> </li> -</ul> -<h3>Office Hours (next 30 minutes)</h3> -<p>The discussion about "Office Hours (next 30 minutes)" started at 16:46.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/334992">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/334992</a> </li> -<li><strong>LINK</strong>: <a href="http://jinja.pocoo.org/docs/2.10/api/#policies">http://jinja.pocoo.org/docs/2.10/api/#policies</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 (99)</li> -<li>ajorg (45)</li> -<li>smoser (19)</li> -<li>rharper (9)</li> -<li>robjo (5)</li> -<li>powersj (4)</li> -<li>meetingology (3)</li> -<li>smoser1 (2)</li> -<li>ubot5 (1)</li> -</ul> -<h2>Full Log</h2> -<p>16:03 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-inin bi-weekly status meeting</p> -<p>16:03 <code>&lt;meetingology&gt;</code> Meeting started Mon Jan 8 16:03:53 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:03 <code>&lt;meetingology&gt;</code> </p> -<p>16:03 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:04 <code>&lt;blackboxsw&gt;</code> Happy 2018 cloud-initers! Thanks ajorg for helping kick us off.</p> -<p>16:04 <code>&lt;blackboxsw&gt;</code> Welcome back from break hope the holidays were good for folks.</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> #topic Recent changes</p> -<p>16:04 <code>&lt;blackboxsw&gt;</code> It</p> -<p>16:05 <code>&lt;blackboxsw&gt;</code> It's been a while since we've held the meeting due to holidays and vacation time. So, not a ton of content to report for the last bit. Digging up those details now</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> Testing of 17.2 on EC2, Azure, and GCE and release to Ubuntu Bionic</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> Complete 17.1.46 SRU to Ubuntu Xenial, Zesty, and Artful</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> Fix documentation around 'init' mode for modules subcommand (LP: #1736600)</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> Tooling to merge community authored branches into master</p> -<p>16:06 <code>&lt;ubot5&gt;</code> Launchpad bug 1736600 in cloud-init "CLI: cloud-init modules -h documents unsupported --mode init" [Low,Fix committed] <a href="https://launchpad.net/bugs/1736600">https://launchpad.net/bugs/1736600</a></p> -<p>16:07 <code>&lt;blackboxsw&gt;</code> So the canonical side of the team worked a bit on getting the latest SRU updates 17.1.46 into Xenial, Zesty and artful. The testing and verification of that release took a bit of time, but we are getting better(faster)</p> -<p>16:07 <code>&lt;blackboxsw&gt;</code> I think this last SRU only took us 2 weeks instead of 4 weeks. so that frees up more time on upstream reviews and increasing cloud-init's velocity</p> -<p>16:07 <code>&lt;ajorg&gt;</code> great</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> we also added team tools for streamlining community authored branches. so that we stop slowing folks down :/</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> then the only problem is the reviewer :)</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> Also 17.2 release was 'cut' prior to Christmas break, this opened master up for more changes to land. so we've pulled in good fixes for VMWare NoCloud and SLES</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> digging up the changests now.</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> Also, keep in touch with our active development and the "done" lane on trello. It's out bookkeeper for anything we are working and Done represents anything landed</p> -<p>16:11 <code>&lt;blackboxsw&gt;</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:13 <code>&lt;blackboxsw&gt;</code> so high-level content that landed between 17.1.46 and 17.2:</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> * CLI added the clean and status subcommands</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> * Support for identifying OVF datasource provided by VMware</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> * NoCloudKVM tests now run in continuous integration</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> * Formalize DataSource get_data and related properties</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> * Remove prettytable dependency and introduce simpletable</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> * VMWare pre and post-customization script support</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> Thanks ajorg I think you were the author of note on simpletable stuff, it's nice to drop dependencies where we can to increase speed of cloud-init</p> -<p>16:15 <code>&lt;ajorg&gt;</code> it was done selfishly</p> -<p>16:15 <code>&lt;ajorg&gt;</code> we dislike taking on new dependencies :-)</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> and thanks to robjo(suse) maitree(vmware) too and dojordan and Ryan McCabe(redhat) for recent branches too</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> :)</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> Post our 17.2 release we've started work on improved integration..... I think we just got powersj's ec2 integration tests landed right johs?</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> josh even</p> -<p>16:18 <code>&lt;powersj&gt;</code> \o/ yep!</p> -<p>16:18 <code>&lt;ajorg&gt;</code> nice</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> sweet, so an extra security blanked for us when we have significant changesets landed in master to ensure ec2 is happy.</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> powersj: what are out plans for continuous integration frequency</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> with ec2 specifically</p> -<p>16:19 <code>&lt;ajorg&gt;</code> Can those integration tests be run by others with EC2 accounts?</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> ajorg: yes they can</p> -<p>16:19 <code>&lt;powersj&gt;</code> I am working on the jenkins jobs this week and hope to have a weekly run as well as a manual run for backport testing</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> I'll get the cmdline</p> -<p>16:19 <code>&lt;ajorg&gt;</code> thanks!</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> tox -e citests -m tests.cloud_tests run --os-name=artful --platform=ec2 --preserve-data --data-dir=../results --verbose</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> or something like that</p> -<p>16:20 <code>&lt;ajorg&gt;</code> got it</p> -<p>16:20 <code>&lt;ajorg&gt;</code> thanks!</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> powersj: documented it too I think</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> getting link</p> -<p>16:20 <code>&lt;powersj&gt;</code> <a href="https://cloudinit.readthedocs.io/en/latest/topics/tests.html#ec2">https://cloudinit.readthedocs.io/en/latest/topics/tests.html#ec2</a></p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloudinit.readthedocs.io/en/latest/topics/tests.html#ec2">https://cloudinit.readthedocs.io/en/latest/topics/tests.html#ec2</a></p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> :)</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> excellent work Josh</p> -<p>16:21 <code>&lt;powersj&gt;</code> thanks for all the reviews :)</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> anything else I'm missing about landed work? rharper powersj smoser1 ?</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> otherwise next topic</p> -<p>16:22 <code>&lt;rharper&gt;</code> blackboxsw: nothing from me</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> So we've got a fairly healthy review queue that we need to get through as we get the year started....</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> we also have a few things we are in flight currently:</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> - continuous integration improvements per powersj</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> - dropping dependence on ifup ifdown utils where possible as that's not supported (or installed in some cases) in systemd world</p> -<p>16:24 <code>&lt;smoser1&gt;</code> blackboxsw: wow. sorry, missing.</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> who is that smoser1 guy anyway</p> -<p>16:25 <code>&lt;smoser1&gt;</code> yeah, i didnt see anything missing sorry.</p> -<p>16:25 <code>&lt;smoser&gt;</code> wonder how that happened.</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> welcome ;)</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> - netplan improvements per rharper and jinja template support for all cloud-config modules</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> - and softlayer support per smoser</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> know the Azure guys are also posting a couple branches on getting a pre-provisioning setup going for thier datasource which looks pretty exciting</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> I can't think of anything else off the top of my head.</p> -<p>16:28 <code>&lt;robjo&gt;</code> chrony support</p> -<p>16:28 <code>&lt;ajorg&gt;</code> we're only talking feature work in this topic?</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> any in progress development to highlight is fair game. bug work. refactoring, feature etc</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> +10 robjo and again thanks for working with us getting all those branches up and (hopefully soon) landed</p> -<p>16:29 <code>&lt;ajorg&gt;</code> what does "jinja template support for all cloud-config modules" mean?</p> -<p>16:31 <code>&lt;ajorg&gt;</code> I'd guess most modules don't need templating?</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> ajorg: two things. 1. since we have now landed /run/cloud-instance/instance-data.json to store metadata/userdata it'd be that #cloud-config can new be specified with ## template:jinja header and could leverage anything jinjia has to offer plus sourcing any of the instance-data.json metadata fields</p> -<p>16:33 <code>&lt;ajorg&gt;</code> Ah, right. Is that not being done above the module level?</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> so if people have repetitive or template-driven content in the runcmd or write_files portion or their #cloud-config they'd be able to leverage jinja templates etc</p> -<p>16:33 <code>&lt;smoser&gt;</code> ajorg: yes, above the module level.</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> ajorg: not anywhere in cloud-config currently</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> one sec I misunderstood the question</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> smoser: can you clarify what you mean?</p> -<p>16:33 <code>&lt;ajorg&gt;</code> I mean, shouldn't #cloud-config template expansion happen before the module sees the config?</p> -<p>16:34 <code>&lt;smoser&gt;</code> blackboxsw: we could/should also allow other part types to be rendered</p> -<p>16:34 <code>&lt;smoser&gt;</code> ttps://trello.com/c/xyqxyOxg</p> -<p>16:35 <code>&lt;smoser&gt;</code> er... bad url. in 2 ways</p> -<p>16:35 <code>&lt;ajorg&gt;</code> The the part handler would be the one to do that expansion.</p> -<p>16:35 <code>&lt;smoser&gt;</code> <a href="https://trello.com/c/AYaCdQyT">https://trello.com/c/AYaCdQyT</a></p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> ahh ok, right that makes sense. I think the cut I made was limited in focus to cloud-config modules and custom scripts supporting the ## template:jinja header.. but nothing would preclude handling other parts</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> so the link to my WIP branch was</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> #link <a href="https://trello.com/c/xyqxyOxg">https://trello.com/c/xyqxyOxg</a></p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> and the general feature per smoser</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> #link <a href="https://trello.com/c/AYaCdQyT/21-cloud-init-query-standardized-json-information">https://trello.com/c/AYaCdQyT/21-cloud-init-query-standardized-json-information</a></p> -<p>16:36 <code>&lt;ajorg&gt;</code> Is there a design doc of some kind of this?</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> not yet.. but we probably should have a spec as it'd be a good template for the docs we'll need to write</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> scott captured most of the use cases we'd be going for in that last trello link above</p> -<p>16:38 <code>&lt;ajorg&gt;</code> Small example of where some clarity is needed: if Jinja is interpreting {foo} in a user-script, what will it do when it sees a shell variable ${foo}</p> -<p>16:38 <code>&lt;ajorg&gt;</code> ?</p> -<p>16:39 <code>&lt;smoser&gt;</code> you declare that the content is a jinja template</p> -<p>16:39 <code>&lt;smoser&gt;</code> if you provide it something that is not renderable as a jinja template</p> -<p>16:39 <code>&lt;smoser&gt;</code> then it will fail</p> -<p>16:39 <code>&lt;smoser&gt;</code> it requires input to explicitly say "this is jinja". it does not just attempt to render anything.</p> -<p>16:39 <code>&lt;smoser&gt;</code> (unless explicitly told to)</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> some brief working examples are in the description of the branch @ <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/334030">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/334030</a></p> -<p>16:40 <code>&lt;ajorg&gt;</code> Sure. But as a content author, I need to know if Jinja is going to try to render ${foo} or not.</p> -<p>16:40 <code>&lt;smoser&gt;</code> then as a content author you can read jinja docs :)</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> jinja would try to render {{ foo }}</p> -<p>16:40 <code>&lt;ajorg&gt;</code> :-</p> -<p>16:41 <code>&lt;smoser&gt;</code> ajorg: we'll document a simple case, and we can even document "for shell, you'll have to be aware that ...."</p> -<p>16:41 <code>&lt;smoser&gt;</code> but we're not going to document all of jinja</p> -<p>16:41 <code>&lt;ajorg&gt;</code> I see.</p> -<p>16:42 <code>&lt;ajorg&gt;</code> My understanding was that Jinja was highly customizable in what it interpreted and how, so that it's important to document how you've configured it to work.</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> and since to burden is on the #cloud-config or script writer to provide the header ## template: jinja\n#cloud-config\n they <em>should</em> understand what they are doing</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> we won't implicitly run the #cloud-config through jinja</p> -<p>16:43 <code>&lt;ajorg&gt;</code> I get that, no problem, what I'm saying is that Jinja is an engine that you configure to do something, not a markup that always does the same thing for everyone.</p> -<p>16:43 <code>&lt;ajorg&gt;</code> Am I making any sense?</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> understood (though I thought it was fairly constrained it it's application and functionality). We'll make sure that the mechanism by which jinja operates is well documented and confined as best we can... for our own sanity we don't want that template engine to be too flexible... too many tough support use cases</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> ok anything else for "In progress development" otherwise we can move to Office hours for 30 mins</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next 30 minutes)</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> robjo: you've got quite a few branches of goodness up for us to review. Any prioritization on those branches or just take them as we can?</p> -<p>16:47 <code>&lt;rharper&gt;</code> I don't think there are issues w.r.t jinja and shell; they use different variable escape methods, jinja uses {{ variable/expression }}; and it doesn't consume $ AFAIK, ajorg do you know differently ?</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/334992">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/334992</a></p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> I'm guessing is top of the list</p> -<p>16:48 <code>&lt;ajorg&gt;</code> I saw {instance_id} at <a href="https://trello.com/c/AYaCdQyT/21-cloud-init-query-standardized-json-information">https://trello.com/c/AYaCdQyT/21-cloud-init-query-standardized-json-information</a> so I assumed it was being customized to look for { instead of {{</p> -<p>16:48 <code>&lt;robjo&gt;</code> blackboxsw: The chrony support should probably be the last as it will take longer over all and more back and forth</p> -<p>16:48 <code>&lt;ajorg&gt;</code> (for one thing)</p> -<p>16:49 <code>&lt;ajorg&gt;</code> rharper: also, there's the whole question of the "extends" feature</p> -<p>16:50 <code>&lt;ajorg&gt;</code> We integrated Jinja into an internal tool a few years back and we spent a very long time making sure the loaders did the right thing.</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> ajorg: I thought I read somewhere that you couldn't exend jinja for custom functions. maybe I was mistaken</p> -<p>16:50 <code>&lt;robjo&gt;</code> I am also not certain that the "re-write everything" on the first go around for chrony is really what we want to do initially</p> -<p>16:50 <code>&lt;ajorg&gt;</code> blackboxsw: I don't think I'm referring to custom functions</p> -<p>16:51 <code>&lt;robjo&gt;</code> That's probably where we ant to end up, but I am not certain that a "step function" approach is in order</p> -<p>16:51 <code>&lt;rharper&gt;</code> ajorg: hrm, I've always seen {{ variable }} or {% expression %}; so maybe blackboxsw can just update the templates;</p> -<p>16:51 <code>&lt;rharper&gt;</code> the examples in the cards</p> -<p>16:52 <code>&lt;ajorg&gt;</code> rharper: sure, that would have helped in this case.</p> -<p>16:52 <code>&lt;robjo&gt;</code> If we do go down the route of the step function I'll need more gudance then in rharper's comments</p> -<p>16:52 <code>&lt;ajorg&gt;</code> blackboxsw: I was referring to the ability of one template to extend another.</p> -<p>16:53 <code>&lt;ajorg&gt;</code> blackboxsw: and the question of where does the engine look when it's asked to extend another template. It can be tricky.</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> yeah I honestly hadn't gotten past step one of handling the template markup within an existing single template. so this may need a bit of thought/work</p> -<p>16:55 <code>&lt;ajorg&gt;</code> Personally, I'd be a lot happier with limiting things to Python format() templates, even though it means you can't have loops, but I won't get in the way as long as we're cognizant of the problems we can run into by accepting the full power of an advanced engine like Jinja.</p> -<p>16:56 <code>&lt;smoser&gt;</code> i'm not opposed to allowing ## template: python-format</p> -<p>16:56 <code>&lt;ajorg&gt;</code> heh</p> -<p>16:56 <code>&lt;smoser&gt;</code> honestly.</p> -<p>16:56 <code>&lt;smoser&gt;</code> you can pick a differnt name if you dont like that one.</p> -<p>16:57 <code>&lt;smoser&gt;</code> but we already use jinja, so it makes sense to support jinja</p> -<p>16:57 * smoser has to run. sorry.</p> -<p>16:57 <code>&lt;rharper&gt;</code> I do feel that supplying the template means the user is opting in; and specifically if we've got a good way to provide dry-run based on a instance.json and a script; that certainly can help folks work out the kinks in the template of their choosing</p> -<p>16:57 <code>&lt;ajorg&gt;</code> I'm really not opposed so much as wary of the extensive power of the thing</p> -<p>16:58 <code>&lt;rharper&gt;</code> ajorg: that's a fair warning; given you've experience here; help drawing the line is most welcome</p> -<p>16:58 <code>&lt;ajorg&gt;</code> I'm trying to think of a way to read in /etc/shadow using Jinja, you know?</p> -<p>16:58 <code>&lt;rharper&gt;</code> well, cloud-init is root anyhow; so, what's the deal with that ?</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> ajorg: heh, right though you can read that with your runcmd section in #cloud-config :)</p> -<p>16:59 <code>&lt;ajorg&gt;</code> If I can come up with a way to do it that doesn't make it look obvious that I'm doing it, and then post that as something others can copy, or use with #include <code>&lt;url&gt;</code> then I win.</p> -<p>16:59 <code>&lt;rharper&gt;</code> I don't think jinja makes that any more troublesome</p> -<p>17:00 <code>&lt;rharper&gt;</code> folks already wget | bash with shell they don't understand either</p> -<p>17:00 <code>&lt;ajorg&gt;</code> I suspect Jijna makes it more opaque.</p> -<p>17:01 <code>&lt;ajorg&gt;</code> The answer to "what file does Jinja read when I use {% extends foo %}" is a very lengthy "it depends"</p> -<p>17:02 <code>&lt;ajorg&gt;</code> anyway, I've said my piece</p> -<p>17:03 * ajorg is a bit of a template naysayer.</p> -<p>17:05 <code>&lt;blackboxsw&gt;</code> +1, there's one in every group. We'll try to keep that in mind as this feature evolves</p> -<p>17:05 <code>&lt;blackboxsw&gt;</code> :)</p> -<p>17:06 <code>&lt;ajorg&gt;</code> nice</p> -<p>17:06 <code>&lt;ajorg&gt;</code> :-)</p> -<p>17:06 <code>&lt;blackboxsw&gt;</code> any pet bugs, new features or burning reviews that need mention?</p> -<p>17:07 <code>&lt;blackboxsw&gt;</code> ajorg: we could do something simple like disable the extends option via policies</p> -<p>17:07 <code>&lt;blackboxsw&gt;</code> it looks like</p> -<p>17:08 <code>&lt;blackboxsw&gt;</code> #link <a href="http://jinja.pocoo.org/docs/2.10/api/#policies">http://jinja.pocoo.org/docs/2.10/api/#policies</a></p> -<p>17:08 <code>&lt;blackboxsw&gt;</code> or maybe I'm misunderstanding the issue I'll read up more on it</p> -<p>17:08 <code>&lt;ajorg&gt;</code> thanks</p> -<p>17:09 <code>&lt;ajorg&gt;</code> It looked like <a href="https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/334074">https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/334074</a> was blocking <a href="https://code.launchpad.net/~yeazelm/cloud-init/+git/cloud-init/+merge/331897">https://code.launchpad.net/~yeazelm/cloud-init/+git/cloud-init/+merge/331897</a> but shouldn't be anymore.</p> -<p>17:09 <code>&lt;ajorg&gt;</code> I'll remind Matt to try it again now.</p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> thanks good dela</p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> dela</p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> deal</p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> geez</p> -<p>17:14 <code>&lt;blackboxsw&gt;</code> on that note. I think it's time for coffee</p> -<p>17:14 <code>&lt;blackboxsw&gt;</code> and time to end the meeting</p> -<p>17:14 <code>&lt;blackboxsw&gt;</code> Happy New Year again folks. Good to be back in the office.</p> -<p>17:15 <code>&lt;blackboxsw&gt;</code> thanks again for the chat, until next time..</p> -<p>17:15 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2017-12-11T16:05:00+00:002017-12-11T16:05:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2017-12-11:/status-2017-12-11.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init 'bi-weekly' status meeting, 11 Dec at 16:05 &mdash; 17:22 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-12-11-16.05.log.html">http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-12-11-16.05.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:07.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://lists.launchpad.net/cloud-init/msg00114.html">https://lists.launchpad.net/cloud-init/msg00114 …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init 'bi-weekly' status meeting, 11 Dec at 16:05 &mdash; 17:22 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-12-11-16.05.log.html">http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-12-11-16.05.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:07.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://lists.launchpad.net/cloud-init/msg00114.html">https://lists.launchpad.net/cloud-init/msg00114.html</a> </li> -<li><strong>LINK</strong>: <a href="http://cloud-init.github.io">http://cloud-init.github.io</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:15.</p> -<ul> -<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/~paul-meyer/cloud-init/+git/cloud-init/+merge/334989">https://code.launchpad.net/~paul-meyer/cloud-init/+git/cloud-init/+merge/334989</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/335034">https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/335034</a> </li> -</ul> -<h3>Office Hours (for next 30 mins)</h3> -<p>The discussion about "Office Hours (for next 30 mins)" started at 16:38.</p> -<ul> -<li><strong>LINK</strong>: <a href="http://pastebin.ubuntu.com/26075842/">http://pastebin.ubuntu.com/26075842/</a> </li> -<li><strong>LINK</strong>: <a href="http://paste.ubuntu.com/26164503/">http://paste.ubuntu.com/26164503/</a> </li> -<li><strong>ACTION</strong>: blackboxsw bring up any updates in instance-data.json fields for discussion about common use-cases/patterns</li> -</ul> -<h2>Vote results</h2> -<h2>Action items, by person</h2> -<ul> -<li>blackboxsw</li> -<li>blackboxsw bring up any updates in instance-data.json fields for discussion about common use-cases/patterns</li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (83)</li> -<li>smoser (54)</li> -<li>ajorg (38)</li> -<li>robjo (32)</li> -<li>ubot5 (7)</li> -<li>meetingology (4)</li> -<li>powersj (2)</li> -<li>dpb1 (2)</li> -<li>rharper (2)</li> -</ul> -<h2>Full Log</h2> -<p>16:05 <code>&lt;blackboxsw</code>&gt; #startmeeting Cloud-init 'bi-weekly' status meeting</p> -<p>16:05 <code>&lt;meetingology</code>&gt; Meeting started Mon Dec 11 16:05:16 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:05 <code>&lt;meetingology</code>&gt; </p> -<p>16:05 <code>&lt;meetingology</code>&gt; Available commands: action commands idea info link nick</p> -<p>16:05 <code>&lt;smoser</code>&gt; thanks for hosting blackboxsw</p> -<p>16:05 <code>&lt;blackboxsw</code>&gt; no problemo.</p> -<p>16:05 <code>&lt;blackboxsw</code>&gt; happy holidays folks and thanks for joining.</p> -<p>16:07 <code>&lt;blackboxsw</code>&gt; #topic Recent Changes</p> -<p>16:07 <code>&lt;blackboxsw</code>&gt; As mentioned @ our 17.1 release, we're promising more frequent cloud-init releases.</p> -<p>16:08 <code>&lt;blackboxsw</code>&gt; smoser has mailed the list informing cloud-init interested parties that we are targeting a 17.2 release for Thursday this week</p> -<p>16:08 <code>&lt;blackboxsw</code>&gt; It's been a few weeks since we've hosted the meeting (I think we missed last meeting), so I'll post some of the development that has landed in trunk</p> -<p>16:08 <code>&lt;smoser</code>&gt; #link <a href="https://lists.launchpad.net/cloud-init/msg00114.html">https://lists.launchpad.net/cloud-init/msg00114.html</a></p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; * All integration tests now function with the nocloud-kvm backend</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; * Fix apport for cloud-name options (LP: #1722564)</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; * Improve warning message when templates aren't found (Robert Schweikert) (LP: #1730135)</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; * Perform null checks for enabled/disabled Red Hat repos (Dave Mulford)</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; * Fix openSUSE and SLES setup of /etc/hosts (Robert Schweikert) (LP: #1731022)</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; * Catch UrlError when #include'ing URLs (Andrew Jorgensen)</p> -<p>16:09 <code>&lt;ubot5</code>&gt; Launchpad bug 1722564 in Apport "apport question will not accept multi-character responses" [Undecided,Confirmed] <a href="https://launchpad.net/bugs/1722564">https://launchpad.net/bugs/1722564</a></p> -<p>16:09 <code>&lt;ubot5</code>&gt; Launchpad bug 1730135 in openstack-dev-sandbox ""Too much rain in Sydney"" [Undecided,New] <a href="https://launchpad.net/bugs/1730135">https://launchpad.net/bugs/1730135</a></p> -<p>16:09 <code>&lt;ubot5</code>&gt; Launchpad bug 1731022 in cloud-init "host template expansion does not work on SUSE distros" [High,Fix committed] <a href="https://launchpad.net/bugs/1731022">https://launchpad.net/bugs/1731022</a></p> -<p>16:09 <code>&lt;smoser</code>&gt; ajorg replied with a request for <a href="https://code.launchpad.net/~ajorgens/cloud-init/+git/cloud-init/+merge/329657">https://code.launchpad.net/~ajorgens/cloud-init/+git/cloud-init/+merge/329657</a></p> -<p>16:09 <code>&lt;smoser</code>&gt; that fell on deaf ears</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; * Released stable release update (SRU) of 17.1-27-geb292c18 (LP: #1721847)</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; * Cleanup dhclient background process after EC2 network discovery.</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; * ntp: fix configuration template rendering for openSUSE and SLES (Robert Schweikert) LP: #1726572</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; * fix manually running cloud-init after upgrade (LP: #1732917)</p> -<p>16:09 <code>&lt;ubot5</code>&gt; Launchpad bug 1721847 in cloud-init (Ubuntu Artful) "sru cloud-init 2017-10-06 (17.1-18-gd4f70470-0ubuntu1) updated to (17.1-27-geb292c18)" [Medium,Fix released] <a href="https://launchpad.net/bugs/1721847">https://launchpad.net/bugs/1721847</a></p> -<p>16:09 <code>&lt;ubot5</code>&gt; Launchpad bug 1726572 in cloud-init "ntp config handling inconsistent for SLES and openSUSE" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1726572">https://launchpad.net/bugs/1726572</a></p> -<p>16:09 <code>&lt;ubot5</code>&gt; Launchpad bug 1732917 in cloud-init "17.1 update breaks EC2 nodes" [High,Fix committed] <a href="https://launchpad.net/bugs/1732917">https://launchpad.net/bugs/1732917</a></p> -<p>16:09 <code>&lt;ajorg</code>&gt; truth</p> -<p>16:09 <code>&lt;smoser</code>&gt; ajorg: i will review shortly</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; * Queued upstream for merge into Bionic</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; * Queued 17.1.46 SRU for Xenial, Zesty, and Artful</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; * Fix EC2 race on sandboxed dhclient's pidfile during tempdir teardown (LP: #1735331)</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; * Enable Bionic in Integration Tests</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; * Create LXD and KVM Integration Tests in Jenkins</p> -<p>16:09 <code>&lt;ubot5</code>&gt; Launchpad bug 1735331 in cloud-init "ec2: zesty tempfile sandbox dhclient.pid file can't be created" [High,Fix committed] <a href="https://launchpad.net/bugs/1735331">https://launchpad.net/bugs/1735331</a></p> -<p>16:10 <code>&lt;blackboxsw</code>&gt; As of end of last week, we are trying to blitz the review queue and dust off anything that has been sitting too long</p> -<p>16:12 <code>&lt;blackboxsw</code>&gt; So a couple fixes went into Amazon's initial network setup, IPv6 support is live for Ubuntu series Xenial, Zesty, Artful and Bionic</p> -<p>16:13 <code>&lt;ajorg</code>&gt; cool</p> -<p>16:14 <code>&lt;blackboxsw</code>&gt; heh I blew that last topic. it should have been #topic Recent Changes.</p> -<p>16:14 <code>&lt;blackboxsw</code>&gt; anyway I'll fix it in the logs when I publish</p> -<p>16:15 <code>&lt;blackboxsw</code>&gt; As always , for historical docs from this meeting check this link</p> -<p>16:15 <code>&lt;blackboxsw</code>&gt; #link <a href="http://cloud-init.github.io">http://cloud-init.github.io</a></p> -<p>16:15 <code>&lt;blackboxsw</code>&gt; #topic In-progress Development</p> -<p>16:15 <code>&lt;blackboxsw</code>&gt; So we have an active queue that is pretty healthy still</p> -<p>16:15 <code>&lt;blackboxsw</code>&gt; #link <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a></p> -<p>16:16 <code>&lt;blackboxsw</code>&gt; smoser: rharper are we still trying to get through that queue as best we can for 17.2 or when do we think the window closes there?</p> -<p>16:16 <code>&lt;smoser</code>&gt; i think we can spend some more time on queue today.</p> -<p>16:16 <code>&lt;smoser</code>&gt; but that is about it really.</p> -<p>16:16 <code>&lt;blackboxsw</code>&gt; yeah, want some settle 'bake' time before the 17.2 cut on Thursday</p> -<p>16:17 <code>&lt;blackboxsw</code>&gt; We saw a couple Azure branches come in late last week.... Are there any branches folks are really excited about landing this week (today tomorrow?)</p> -<p>16:18 <code>&lt;blackboxsw</code>&gt; I had hoped to get through a couple of Robert's as they don't seem very contentious.</p> -<p>16:19 <code>&lt;smoser</code>&gt; the reporter bit seems pretty reasonable</p> -<p>16:19 <code>&lt;smoser</code>&gt; other than its not actually used anywhere in the mp</p> -<p>16:19 <code>&lt;smoser</code>&gt; ie, its non-contentious to add a reporter, but adding code that is not used is of not a lot of use :)</p> -<p>16:19 <code>&lt;blackboxsw</code>&gt; true</p> -<p>16:20 <code>&lt;ajorg</code>&gt; which mp is being discussed?</p> -<p>16:20 <code>&lt;smoser</code>&gt; (<a href="https://code.launchpad.net/~paul-meyer/cloud-init/+git/cloud-init/+merge/334989">https://code.launchpad.net/~paul-meyer/cloud-init/+git/cloud-init/+merge/334989</a>)</p> -<p>16:20 <code>&lt;blackboxsw</code>&gt; #link <a href="https://code.launchpad.net/~paul-meyer/cloud-init/+git/cloud-init/+merge/334989">https://code.launchpad.net/~paul-meyer/cloud-init/+git/cloud-init/+merge/334989</a></p> -<p>16:21 <code>&lt;ajorg</code>&gt; thanks</p> -<p>16:23 <code>&lt;blackboxsw</code>&gt; With the upcoming holidays I expect things will be pretty slow after mid-next week, so we won't likely be landing a lot before the first of the new year.</p> -<p>16:25 <code>&lt;robjo</code>&gt; If it's slow for you more time to review open merge proposals ;)</p> -<p>16:25 <code>&lt;blackboxsw</code>&gt; This week we are also trying to get an SRU into ubuntu xenial, zesty and artful for some VMware/OVF datasource fixes for ds-identify and for pre-cusomization marker files courtesty (smoser &amp; maitriyee)</p> -<p>16:26 <code>&lt;blackboxsw</code>&gt; <em>courtesy</em> rather</p> -<p>16:26 <code>&lt;smoser</code>&gt; ajorg: you could ping matthew on <a href="https://code.launchpad.net/~yeazelm/cloud-init/+git/cloud-init/+merge/331897">https://code.launchpad.net/~yeazelm/cloud-init/+git/cloud-init/+merge/331897</a></p> -<p>16:27 <code>&lt;ajorg</code>&gt; yup</p> -<p>16:27 <code>&lt;blackboxsw</code>&gt; and I know powersj is working on EC2 integration test support for cloud-init</p> -<p>16:27 <code>&lt;powersj</code>&gt; yep!</p> -<p>16:27 <code>&lt;powersj</code>&gt; Hoping to have an initial MP up this week</p> -<p>16:27 <code>&lt;blackboxsw</code>&gt; it's gonna be excellent to automatically test these releases</p> -<p>16:28 <code>&lt;blackboxsw</code>&gt; powersj: rharper smoser anything else in progress?</p> -<p>16:28 <code>&lt;rharper</code>&gt; nothing here</p> -<p>16:28 <code>&lt;ajorg</code>&gt; oh very nice.</p> -<p>16:28 <code>&lt;dpb1</code>&gt; powersj: \o/</p> -<p>16:28 <code>&lt;smoser</code>&gt; just the things that are in teh review queue. i put up one this morning for tmp file leakage</p> -<p>16:28 <code>&lt;smoser</code>&gt; <a href="https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/335034">https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/335034</a></p> -<p>16:29 <code>&lt;smoser</code>&gt; i think the yeazelm mp probably is just missing somethign simple bug haven't spent any time on it.</p> -<p>16:29 <code>&lt;blackboxsw</code>&gt; ahh also we landed the initial /run/cloud-init/instance-data.json which we had talked about with larsks. It captures all metadata and userdata and some standardized properties which could help people script instance data.</p> -<p>16:29 <code>&lt;smoser</code>&gt; yeah, that is neat.</p> -<p>16:30 <code>&lt;blackboxsw</code>&gt; Yeah, we have yet to write up docs on using it (and we have an inprogress branch to allow using jinja templates in #cloud-config modules). But I don't expect this to land by 17.2</p> -<p>16:31 <code>&lt;ajorg</code>&gt; did we? that's great!</p> -<p>16:32 <code>&lt;blackboxsw</code>&gt; yeah only basic standardized properties currently. + 'local-hostname': self.get_hostname(),</p> -<p>16:32 <code>&lt;blackboxsw</code>&gt; 592 + 'instance-id': self.get_instance_id(),</p> -<p>16:32 <code>&lt;blackboxsw</code>&gt; 593 + 'cloud-name': self.cloud_name,</p> -<p>16:32 <code>&lt;blackboxsw</code>&gt; 594 + 'region': self.region,</p> -<p>16:32 <code>&lt;blackboxsw</code>&gt; 595 + 'availability-zone': self.availability_zone}}</p> -<p>16:32 <code>&lt;robjo</code>&gt; is that basically a re-implementation of python-ec2metadata? <a href="https://github.com/SUSE/Enceladus/tree/master/ec2utils/ec2metadata">https://github.com/SUSE/Enceladus/tree/master/ec2utils/ec2metadata</a></p> -<p>16:32 <code>&lt;blackboxsw</code>&gt; but it's a first pass. We expect to add more</p> -<p>16:33 <code>&lt;blackboxsw</code>&gt; robjo: kindof, though generalized for all datasources</p> -<p>16:34 <code>&lt;rharper</code>&gt; robjo: long term, it's expected to be more than just ec2; rather a common baseline of instance metadata independent the actual cloud, but , IIRC, having a cloud-specific area (or at least access to the raw data)</p> -<p>16:34 <code>&lt;blackboxsw</code>&gt; it leaves a json-foramatted file containing any vendor data and user-data plus generalized/standardized fields extracted from that content which can be expected on all clouds</p> -<p>16:35 <code>&lt;robjo</code>&gt; problem with "all" clouds is that Azure is very different</p> -<p>16:35 <code>&lt;blackboxsw</code>&gt; since each datasource has that data already, it's essentially just formating it in a consumable file that others could levereage</p> -<p>16:35 <code>&lt;robjo</code>&gt; although one can argue that a "name" is an id it still looks weird when 'instance-id' and is a name</p> -<p>16:36 <code>&lt;blackboxsw</code>&gt; agreed robjo, some datasources may not provide different/less content.</p> -<p>16:36 <code>&lt;smoser</code>&gt; ajorg: <a href="http://paste.ubuntu.com/26164503/">http://paste.ubuntu.com/26164503/</a></p> -<p>16:36 <code>&lt;ajorg</code>&gt; Is that one of the Azure differences? name vs. instance-id?</p> -<p>16:36 <code>&lt;smoser</code>&gt; thats a demo of instance-data.json</p> -<p>16:36 <code>&lt;robjo</code>&gt; yes, azure has names no numbers</p> -<p>16:37 <code>&lt;robjo</code>&gt; it's more about "user expectations" as a "name" is an "identifier"</p> -<p>16:37 <code>&lt;blackboxsw</code>&gt; I'll check that azure run now. I think I linked it to the branch originally</p> -<p>16:37 <code>&lt;blackboxsw</code>&gt; ok I think it's probably a good to transition to open office hours now for the next 30 mins</p> -<p>16:38 <code>&lt;smoser</code>&gt; what is 'name' versus 'instance-id' comment ?</p> -<p>16:38 <code>&lt;smoser</code>&gt; ajorg: ?</p> -<p>16:38 <code>&lt;blackboxsw</code>&gt; #topic Office Hours (for next 30 mins)</p> -<p>16:38 <code>&lt;blackboxsw</code>&gt; feel free to continue the discussion now</p> -<p>16:38 <code>&lt;robjo</code>&gt; I'd just caution of making the assumption that we can stick the information from that data sources straight into another format and then call it "generic instance information"</p> -<p>16:38 <code>&lt;ajorg</code>&gt; smoser: re robjo's comment about "Azure is very different"</p> -<p>16:39 <code>&lt;smoser</code>&gt; oh. yes. ok.</p> -<p>16:39 <code>&lt;blackboxsw</code>&gt; azure instance-data</p> -<p>16:39 <code>&lt;blackboxsw</code>&gt; #link <a href="http://pastebin.ubuntu.com/26075842/">http://pastebin.ubuntu.com/26075842/</a></p> -<p>16:39 <code>&lt;dpb1</code>&gt; smoser: standup</p> -<p>16:39 <code>&lt;smoser</code>&gt; yeah, they do have a 'id'</p> -<p>16:40 <code>&lt;blackboxsw</code>&gt; #link <a href="http://paste.ubuntu.com/26164503/">http://paste.ubuntu.com/26164503/</a></p> -<p>16:40 <code>&lt;ajorg</code>&gt; from DMI?</p> -<p>16:40 <code>&lt;robjo</code>&gt; Which is useless in any any command</p> -<p>16:40 <code>&lt;smoser</code>&gt; from the cd i think.</p> -<p>16:41 <code>&lt;ajorg</code>&gt; robjo: ah, so the ID is unique (is it?) but can't be used to call any Azure APIs?</p> -<p>16:41 <code>&lt;robjo</code>&gt; in EC2 the instance-id is useful to me if I want to run "aws" commands, but the instance ID shown in the pastebin is useless for any "az" command</p> -<p>16:41 <code>&lt;robjo</code>&gt; ajorg: correct</p> -<p>16:41 <code>&lt;robjo</code>&gt; in the "az" tools everything is a name</p> -<p>16:42 <code>&lt;robjo</code>&gt; and thus to make the data cloud-init produces useful the -id should be the name of the VM</p> -<p>16:42 <code>&lt;robjo</code>&gt; then I can parse that information and use it if I need to deal with the API</p> -<p>16:43 <code>&lt;smoser</code>&gt; hm.</p> -<p>16:43 <code>&lt;robjo</code>&gt; but providing that ID as its is basically just sticking information into the json to "fill a field" which is somewhat counter to the point I'd say</p> -<p>16:43 <code>&lt;ajorg</code>&gt; robjo: there's a uniqueness constraint on the name too? but per-account or at-a-time or what?</p> -<p>16:43 <code>&lt;smoser</code>&gt; i odnt knwo. although it is insteresting thought.</p> -<p>16:43 <code>&lt;smoser</code>&gt; the issue is 'instance-id' is supposed to be an instance id</p> -<p>16:43 <code>&lt;smoser</code>&gt; not a user provided name that can be provided mutliple times in a row.</p> -<p>16:44 <code>&lt;smoser</code>&gt; i realize name is per-group unique, but if i</p> -<p>16:44 <code>&lt;smoser</code>&gt; a.) launch</p> -<p>16:44 <code>&lt;smoser</code>&gt; a.) launch 'foobar'</p> -<p>16:44 <code>&lt;robjo</code>&gt; There is a uniqueness constraint in that one cannot run a VM with the same "name" in the same resource group</p> -<p>16:44 <code>&lt;ajorg</code>&gt; so the question is if that ID provides global uniqueness, or if it provides a reference to the instance to be used via APIs</p> -<p>16:44 <code>&lt;smoser</code>&gt; b.) create capture</p> -<p>16:44 <code>&lt;smoser</code>&gt; c.) delete foobar</p> -<p>16:44 <code>&lt;smoser</code>&gt; d.) launch foobar</p> -<p>16:44 <code>&lt;smoser</code>&gt; then 'd' wont look new</p> -<p>16:45 <code>&lt;robjo</code>&gt; yes, it will it just takes a long time in Azure until the backend reaches "eventual" consistency and knows "foorbar" has been deleted previously</p> -<p>16:45 <code>&lt;ajorg</code>&gt; It seems clear enough that cloud-init is looking for a unique ID</p> -<p>16:45 <code>&lt;ajorg</code>&gt; But a user might want either, and probably an ID for API use.</p> -<p>16:47 <code>&lt;robjo</code>&gt; Well if we provide a format of the data that is exposed to the user via documentation and expected to be used by the user than at that point, IMHO, user needs have higher priority than what cloud-init is looking for</p> -<p>16:47 <code>&lt;ajorg</code>&gt; To decide which APIs to use, a script has to first look at which cloud it's on, so it has a chance to decide which value to use.</p> -<p>16:47 <code>&lt;robjo</code>&gt; that cloud-init uses the id to make decisions about "pre-once", "per-always" is a different topic</p> -<p>16:49 <code>&lt;robjo</code>&gt; Well that then kind of defeats the "generic instance information" claim, IMHO</p> -<p>16:49 <code>&lt;robjo</code>&gt; you are basically saying 1.) look for the framework and then decide if on that framework the "generic instance information" is useful or not</p> -<p>16:50 <code>&lt;robjo</code>&gt; 2.) If you happen to be on a platform where the "generic instance information" is not useful, go and collect your own</p> -<p>16:50 <code>&lt;robjo</code>&gt; From a user perspective that is not very nice, IMHO</p> -<p>16:51 <code>&lt;ajorg</code>&gt; oh, I was presuming we'd also include the Azure name, not that we'd include only a useless instance-id in that case.</p> -<p>16:51 <code>&lt;ajorg</code>&gt; clouds that don't have a name, wouldn't include a value for it.</p> -<p>16:52 <code>&lt;robjo</code>&gt; the pastebin only has the ID</p> -<p>16:52 <code>&lt;ajorg</code>&gt; right, I'm saying we should add the name</p> -<p>16:53 <code>&lt;robjo</code>&gt; This is why I am pointing out that "generic instance information" is not necessarily so easy to come by</p> -<p>16:54 <code>&lt;blackboxsw</code>&gt; robjo: ultimately, I'd like the generalized content surfaced in instance-data.json to be something that external user's could get value from and script against. This first pass was a stripped down approach to some of that content.</p> -<p>16:54 <code>&lt;smoser</code>&gt; we could add 'name' and have it be none yes.</p> -<p>16:55 <code>&lt;smoser</code>&gt; the not-yet-written doc will state that consumers should not be confused by new field names.</p> -<p>16:55 <code>&lt;blackboxsw</code>&gt; There are some fixes that need to be proposed to all datasources to better standardize on things like public vs private addresses, external hostnames etc. Those I expect will come in subsequent passes.</p> -<p>16:55 <code>&lt;robjo</code>&gt; it might be worth considering the concept of "equivalent instance information" where the entries in the json files get names/keys that are generic across all cloud frameworks and provide the euivalent information/usefulness to the user</p> -<p>16:55 <code>&lt;smoser</code>&gt; but inside the 'v1', then content of a key will not change.</p> -<p>16:55 <code>&lt;ajorg</code>&gt; robjo: that's a fair point, imho</p> -<p>16:55 <code>&lt;smoser</code>&gt; but 'instance-id' is in fact 'instance-id'. not 'name'.</p> -<p>16:55 <code>&lt;blackboxsw</code>&gt; robjo: I think that is the intent of those 'v1' standardized fields.</p> -<p>16:56 <code>&lt;smoser</code>&gt; note that lxd shares the same generic problem in this regard as azure. it uses user-provided name for instance-id. but does not provide an actual instance id of any sort.</p> -<p>16:56 <code>&lt;blackboxsw</code>&gt; right per name/instance-id discussion, they feel separate, and I think there is value in adding a separate 'name' as smoser mentioned</p> -<p>16:58 <code>&lt;robjo</code>&gt; Lets look at it from an API perspective, if I were to use the .json file wouldn't it be nice if I could just say json.load().get{'instance_api_id')</p> -<p>16:58 <code>&lt;robjo</code>&gt; for EC2 that returns the instance-id, for Azure it gives me the name</p> -<p>16:59 <code>&lt;robjo</code>&gt; part of the idea of cloud-init is to keep the ugly details of the cloud framework away from the user</p> -<p>16:59 <code>&lt;ajorg</code>&gt; if we were talking about the value of "region" we'd certainly want to yield the value that's useful for API calls.</p> -<p>17:00 <code>&lt;robjo</code>&gt; so why would the .json data then retrieve from that idea and make the user know if I am in EC2 I need to use instance-id and if I am in Azure I need to use instance-name?</p> -<p>17:01 <code>&lt;robjo</code>&gt; ajorg: agreed</p> -<p>17:01 <code>&lt;smoser</code>&gt; it seems somewhat non-sense that azure gives an instance a unique id, but cannot take that in as an identifier to the instance.</p> -<p>17:02 <code>&lt;robjo</code>&gt; AWS, GCE, and Azure all have the concept of "region" , not certain how IBM is handling that part in their setup but that may not be of interest to us at this point</p> -<p>17:02 <code>&lt;smoser</code>&gt; your point is good though. but instance-id i really think needs to be a unique identifier (as much as possible) for this <em>instance</em></p> -<p>17:02 <code>&lt;ajorg</code>&gt; It sounded like smoser's 'v1' comment was meant to imply we could have a 'v2' that yields data differently than 'v1'.</p> -<p>17:02 <code>&lt;smoser</code>&gt; softlayer has "datacenters"</p> -<p>17:03 <code>&lt;robjo</code>&gt; smoser: I agree, but that's the way it is</p> -<p>17:03 <code>&lt;smoser</code>&gt; at some point, ajorg we will of course realize that we're all idiots</p> -<p>17:03 <code>&lt;smoser</code>&gt; and wonder What were we thinking!</p> -<p>17:03 <code>&lt;smoser</code>&gt; and have a 'v2'</p> -<p>17:04 <code>&lt;blackboxsw</code>&gt; `&lt;-- it takes some of us longer than others to realize that</p> -<p>17:05 <code>&lt;ajorg</code>&gt; smoser: you're not convinced that today is that day?</p> -<p>17:05 <code>&lt;smoser</code>&gt; i try to keep acknowledgement of that fact to be more than a few days later</p> -<p>17:06 <code>&lt;ajorg</code>&gt; good to let it sink in first :-)</p> -<p>17:06 <code>&lt;smoser</code>&gt; (compared to when i notice it, to allow for additional occurences)</p> -<p>17:06 <code>&lt;ajorg</code>&gt; I'm not going to say it has to be changed, but I do think at the very least the azure name should be available.</p> -<p>17:07 <code>&lt;blackboxsw</code>&gt; I think this discussion definitely sheds light on the fact that we should continue to bring these standardized instance-data discussions to this meeting for a quick feedback loop from you guys as it evolves :)</p> -<p>17:07 <code>&lt;ajorg</code>&gt; :)</p> -<p>17:08 <code>&lt;blackboxsw</code>&gt; #action blackboxsw bring up any updates in instance-data.json fields for discussion about common use-cases/patterns</p> -<p>17:08 * meetingology blackboxsw bring up any updates in instance-data.json fields for discussion about common use-cases/patterns</p> -<p>17:08 <code>&lt;ajorg</code>&gt; and it doesn't seem harmful to have the name only if the cloud provides one, just as if the cloud doesn't have a concept of an availability zone we'll skip that too.</p> -<p>17:09 <code>&lt;blackboxsw</code>&gt; +1</p> -<p>17:10 <code>&lt;blackboxsw</code>&gt; well i think this about wraps up our meeting for today</p> -<p>17:10 <code>&lt;blackboxsw</code>&gt; any other topics for today?</p> -<p>17:11 <code>&lt;ajorg</code>&gt; I pinged Matt Yeazel, but he didn't respond yet.</p> -<p>17:11 <code>&lt;smoser</code>&gt; i think 'api-id' would lmake sense as a name.</p> -<p>17:11 <code>&lt;ajorg</code>&gt; so nothing more from my end</p> -<p>17:11 <code>&lt;ajorg</code>&gt; smoser: or 'api-instance-id'</p> -<p>17:12 <code>&lt;smoser</code>&gt; that just seems confusing.</p> -<p>17:12 <code>&lt;smoser</code>&gt; hm..</p> -<p>17:12 <code>&lt;smoser</code>&gt; i see why you want the 'instance' portion there, but the thing i dont like is that implies that this is 'per instance'</p> -<p>17:12 <code>&lt;ajorg</code>&gt; well, it's an API instance identifier.</p> -<p>17:13 <code>&lt;smoser</code>&gt; which in fact it is not.</p> -<p>17:13 <code>&lt;smoser</code>&gt; hm.</p> -<p>17:13 <code>&lt;ajorg</code>&gt; Ah, okay, that's true, but if the cloud doesn't have a unique way to identify the instance to the API...</p> -<p>17:13 <code>&lt;smoser</code>&gt; yeah</p> -<p>17:14 <code>&lt;ajorg</code>&gt; someone should check that assumption... how do you refer to terminated instances? or how are they identified in logs?</p> -<p>17:16 <code>&lt;ajorg</code>&gt; smoser: I just worry that someone's going to say "but in my API an API ID is this other thing"</p> -<p>17:17 <code>&lt;blackboxsw</code>&gt; yeah before surfacing something like that we'd need to vet it</p> -<p>17:17 <code>&lt;ajorg</code>&gt; In general I think there are enough differences between clouds that it's probably a losing battle to try to come up with something that's one-size-fits-all.</p> -<p>17:17 <code>&lt;ajorg</code>&gt; The goal was to make the information available more readily than by calling out to metadata services, right?</p> -<p>17:18 <code>&lt;ajorg</code>&gt; It's much harder to implement meta-data pulling for every cloud than to implement some logic that pulls the right value out of a JSON object, so it's still a big improvement even if it can't provide a unified view.</p> -<p>17:21 <code>&lt;ajorg</code>&gt; anywho, I should go do other things.</p> -<p>17:21 <code>&lt;blackboxsw</code>&gt; ajorg: yes that is the primary goal: more easily access cloud-provided metadata</p> -<p>17:21 <code>&lt;blackboxsw</code>&gt; if there is low-hanging fruit we can standardize I'm +1 on the concept</p> -<p>17:22 <code>&lt;blackboxsw</code>&gt; that's where the standard 'v1' key came from</p> -<p>17:22 <code>&lt;blackboxsw</code>&gt; but yeah I also don't think cloud-init needs to boil the ocean and standardize all fields</p> -<p>17:22 <code>&lt;blackboxsw</code>&gt; we'll capture what low-hanging fruit we can</p> -<p>17:22 <code>&lt;blackboxsw</code>&gt; and it'll take time</p> -<p>17:22 <code>&lt;blackboxsw</code>&gt; ok. Thanks for the great discusssions/suggestions ajorg and robjo. keep 'em coming</p> -<p>17:22 <code>&lt;blackboxsw</code>&gt; think I'll end meeting now</p> -<p>17:22 <code>&lt;blackboxsw</code>&gt; until next time...</p> -<p>17:22 <code>&lt;blackboxsw</code>&gt; #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2017-11-13T16:03:00+00:002017-11-13T16:03:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2017-11-13:/status-2017-11-13.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Office Hours (next 30 minutes), 13 Nov at 16:03 &mdash; 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></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Office Hours (next 30 minutes), 13 Nov at 16:03 &mdash; 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>&lt;blackboxsw</code>&gt; #startmeeting Cloud-init bi-weekly status</p> -<p>16:03 <code>&lt;meetingology</code>&gt; 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>&lt;meetingology</code>&gt; </p> -<p>16:03 <code>&lt;meetingology</code>&gt; Available commands: action commands idea info link nick</p> -<p>16:03 <code>&lt;powersj</code>&gt; o/</p> -<p>16:03 <code>&lt;blackboxsw</code>&gt; time change got to us</p> -<p>16:04 <code>&lt;blackboxsw</code>&gt; #topic Recent Changes</p> -<p>16:05 <code>&lt;blackboxsw</code>&gt; 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>&lt;smoser</code>&gt; <a href="http://paste.ubuntu.com/25954862/">http://paste.ubuntu.com/25954862/</a></p> -<p>16:06 <code>&lt;smoser</code>&gt; $ git log a90a8b1cb3104ee3250ac79d6e25a9ff4f527baa.. | log2dch | sed 's,^ ,,' | pastebinit</p> -<p>16:06 <code>&lt;blackboxsw</code>&gt; 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>&lt;blackboxsw</code>&gt; Published cloud-init packages to Bionic Beaver release</p> -<p>16:06 <code>&lt;blackboxsw</code>&gt; Update Gentoo Linux support to "rc-service" scripts as "service" is deprecated, thanks to ckonstanski!</p> -<p>16:06 <code>&lt;blackboxsw</code>&gt; 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>&lt;ubot5</code>&gt; 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>&lt;blackboxsw</code>&gt; #link <a href="http://paste.ubuntu.com/25954862/">http://paste.ubuntu.com/25954862/</a></p> -<p>16:07 <code>&lt;blackboxsw</code>&gt; #info SRU queued for release today</p> -<p>16:07 <code>&lt;blackboxsw</code>&gt; Here's the cloud-init content we published for the last two weeks:</p> -<p>16:07 <code>&lt;blackboxsw</code>&gt; #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>&lt;blackboxsw</code>&gt; #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>&lt;blackboxsw</code>&gt; 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>&lt;blackboxsw</code>&gt; 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>&lt;blackboxsw</code>&gt; 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>&lt;blackboxsw</code>&gt; #topic In Progress Development</p> -<p>16:10 <code>&lt;blackboxsw</code>&gt; smoser: rharper anything here?</p> -<p>16:10 <code>&lt;smoser</code>&gt; #link <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a></p> -<p>16:11 <code>&lt;smoser</code>&gt; robjo has done a couple fixes for SuSE and i've pulled a few of them.</p> -<p>16:11 <code>&lt;smoser</code>&gt; he has one up i saw yestderday for ntpSuSE</p> -<p>16:11 <code>&lt;smoser</code>&gt; others ther.e we've been delinquent due to some distractions recently.</p> -<p>16:11 <code>&lt;rharper</code>&gt; blackboxsw: nothing new for me at the moment</p> -<p>16:12 <code>&lt;smoser</code>&gt; and chad had one up for clean and status</p> -<p>16:12 <code>&lt;blackboxsw</code>&gt; 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>&lt;smoser</code>&gt; which is nice.</p> -<p>16:13 <code>&lt;robjo</code>&gt; 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>&lt;blackboxsw</code>&gt; #topic Office Hours (next 30 minutes)</p> -<p>16:14 <code>&lt;robjo</code>&gt; 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>&lt;blackboxsw</code>&gt; so we'll hang out with eyes on this channel for any burning questions/bugs/questions</p> -<p>16:14 <code>&lt;smoser</code>&gt; robjo: well, the meeting is listed in UTC time</p> -<p>16:14 <code>&lt;smoser</code>&gt; that pays no attention to US legislation to change clocks at random points in the year :)</p> -<p>16:15 <code>&lt;robjo</code>&gt; oK, my fault when I added it to my calendar, eay enough to fix ;)</p> -<p>16:15 <code>&lt;smoser</code>&gt; but the humans here were also affected :)</p> -<p>16:15 <code>&lt;blackboxsw</code>&gt; heh, anyone opposed to shifting this meeting time +30 from now during the next few months?</p> -<p>16:15 <code>&lt;blackboxsw</code>&gt; as the meeting now collides w/ another meeting for us</p> -<p>16:15 <code>&lt;blackboxsw</code>&gt; :/</p> -<p>16:16 <code>&lt;blackboxsw</code>&gt; officially 16:30 UTC?</p> -<p>16:17 <code>&lt;robjo</code>&gt; Well, I'd prefer to either follow the "randomness" clock manipulation or not follow it</p> -<p>16:19 <code>&lt;robjo</code>&gt; 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>&lt;blackboxsw</code>&gt; fair point. ok let's keep the new time as is.</p> -<p>16:20 <code>&lt;blackboxsw</code>&gt; we've discussed side-channel, we can shift our meetings out of the way of this</p> -<p>16:20 <code>&lt;blackboxsw</code>&gt; so robjo +1</p> -<p>16:20 <code>&lt;blackboxsw</code>&gt; 16:00 UTC</p> -<p>16:24 <code>&lt;blackboxsw</code>&gt; also related to CI side, powersj and rharper spent quite a bit of time w/ our continuous integration infrastructure fixing/addressing memory &amp; storage pressure issues to make sure we avoid intermittent false test failures due to timeouts or system resource contention</p> -<p>16:24 <code>&lt;blackboxsw</code>&gt; #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>&lt;via</code>&gt; 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>&lt;robjo</code>&gt; 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>&lt;via</code>&gt; like configuring the chef node name to have my instance id in it</p> -<p>16:32 <code>&lt;blackboxsw</code>&gt; #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>&lt;ubot5</code>&gt; Launchpad bug 1731619 in cloud-init "Support chrony as a client for ntp" [Undecided,New]</p> -<p>16:33 <code>&lt;blackboxsw</code>&gt; 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>&lt;blackboxsw</code>&gt; 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>&lt;smoser</code>&gt; 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>&lt;via</code>&gt; well, i'm trying to do it in a yaml cloud-config file</p> -<p>16:35 <code>&lt;smoser</code>&gt; right. as it is right now, via you cann't reference anything from the metadata.</p> -<p>16:35 <code>&lt;via</code>&gt; does that mean i need to use #jinja and if so how does that play with #cloud-config ?</p> -<p>16:35 <code>&lt;via</code>&gt; oh</p> -<p>16:36 <code>&lt;via</code>&gt; bummer</p> -<p>16:36 <code>&lt;via</code>&gt; should i just switch to a shell script?</p> -<p>16:36 <code>&lt;smoser</code>&gt; but we'd hope to implement that.</p> -<p>16:36 <code>&lt;smoser</code>&gt; 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>&lt;via</code>&gt; okay, damn</p> -<p>16:36 <code>&lt;via</code>&gt; thanks</p> -<p>16:36 <code>&lt;blackboxsw</code>&gt; 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>&lt;smoser</code>&gt; 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>&lt;smoser</code>&gt; but we do plan on implementing it.</p> -<p>16:37 <code>&lt;via</code>&gt; no worries, i'm stuck on an ancient version anyway</p> -<p>16:38 <code>&lt;robjo</code>&gt; 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>&lt;robjo</code>&gt; since with a third option the black/white decision being made today will no longer work</p> -<p>16:39 <code>&lt;blackboxsw</code>&gt; +1 robjo yeah. rharper was chatting about this potential approach as well</p> -<p>16:39 <code>&lt;robjo</code>&gt; look there is also grey ;)</p> -<p>16:39 <code>&lt;blackboxsw</code>&gt; heh yeah</p> -<p>16:40 <code>&lt;robjo</code>&gt; Next question.... network config.</p> -<p>16:40 <code>&lt;blackboxsw</code>&gt; yeah might have to 'grow' an override option in cc_ntp module eventually</p> -<p>16:41 <code>&lt;blackboxsw</code>&gt; as those grey use-cases come up (per bugs/requests ;) )</p> -<p>16:41 <code>&lt;robjo</code>&gt; 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>&lt;robjo</code>&gt; 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>&lt;robjo</code>&gt; 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>&lt;robjo</code>&gt; blackboxsw: "apply_network_config is not currently implemented "</p> -<p>16:44 <code>&lt;robjo</code>&gt; "for distribution '%s'. Attempting to use apply_network"</p> -<p>16:45 <code>&lt;blackboxsw</code>&gt; ahh. right-o</p> -<p>16:45 <code>&lt;robjo</code>&gt; 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>&lt;robjo</code>&gt; 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>&lt;blackboxsw</code>&gt; 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>&lt;robjo</code>&gt; OK :)</p> -<p>16:50 <code>&lt;blackboxsw</code>&gt; 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>&lt;blackboxsw</code>&gt; 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>&lt;blackboxsw</code>&gt; we'll keep our eyes open for discussions/suggestions from folks</p> -<p>16:54 <code>&lt;robjo</code>&gt; 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>&lt;blackboxsw</code>&gt; robjo: I'm curious how different that datasource would be from nocloud datasource</p> -<p>16:56 <code>&lt;blackboxsw</code>&gt; <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>&lt;blackboxsw</code>&gt; #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>&lt;blackboxsw</code>&gt; which allows for providing local data instead of dealing with metadata</p> -<p>16:56 <code>&lt;blackboxsw</code>&gt; well network metadata</p> -<p>16:57 <code>&lt;robjo</code>&gt; 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>&lt;blackboxsw</code>&gt; good deal.... think we are at the top of the hour... so I'll probably end meeting now</p> -<p>17:01 <code>&lt;blackboxsw</code>&gt; thanks via robjo rharper powersj &amp; smoser. next meeting 2 weeks same early time</p> -<p>17:01 <code>&lt;blackboxsw</code>&gt; #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2017-10-30T16:03:00+00:002017-10-30T16:03:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2017-10-30:/status-2017-10-30.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Open Discussion / Office Hours (30 mins), 30 Oct at 16:03 &mdash; 17:00 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-10-30-16.03.log.html">http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-10-30-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="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1721847">https://bugs.launchpad.net …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Open Discussion / Office Hours (30 mins), 30 Oct at 16:03 &mdash; 17:00 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-10-30-16.03.log.html">http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-10-30-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="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1721847">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1721847</a> </li> -</ul> -<h3>In Progess Development</h3> -<p>The discussion about “In Progress Development” started at 16:17.</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="https://launchpad.net/bugs/1728152">https://launchpad.net/bugs/1728152</a> </li> -</ul> -<h3>Open Discussion / Office Hours (30 mins)</h3> -<p>The discussion about “Recent Changes” started at 16:30.</p> -<ul> -<li><em>LINK:</em> <a href="https://launchpad.net/bugs/1728152">https://launchpad.net/bugs/1728152</a></li> -</ul> -<h2>Vote results</h2> -<h2>Done items</h2> -<h2>Meeting summary</h2> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (61)</li> -<li>smoser (10)</li> -<li>ubot5 (8)</li> -<li>powersj (6)</li> -<li>robjo (6)</li> -<li>meetingology (3)</li> -<li>rharper (2)</li> -<li>ckonstanski (1)</li> -</ul> -<h2>Full Log</h2> -<p>16:03 <code>&lt;blackboxsw</code>&gt; #startmeeting cloud-init bi-weekly status</p> -<p>16:03 <code>&lt;meetingology</code>&gt; Meeting started Mon Oct 30 16:03:09 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>&lt;meetingology</code>&gt; </p> -<p>16:03 <code>&lt;meetingology</code>&gt; Available commands: action commands idea info link nick</p> -<p>16:04 <code>&lt;blackboxsw</code>&gt; #topic In Progress Development</p> -<p>16:04 <code>&lt;blackboxsw</code>&gt; So, the last couple weeks have been fairly busy with Ubuntu an SRU processs for Xenial, Zesty and the new Artful release</p> -<p>16:05 <code>&lt;blackboxsw</code>&gt; our SRU process bug captures most of that work</p> -<p>16:05 <code>&lt;blackboxsw</code>&gt; #LINK <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1721847">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1721847</a></p> -<p>16:05 <code>&lt;ubot5</code>&gt; Ubuntu bug 1721847 in cloud-init (Ubuntu Zesty) "sru cloud-init 2017-10-06 (17.1-18-gd4f70470-0ubuntu1)" [Medium,Fix committed]</p> -<p>16:07 <code>&lt;blackboxsw</code>&gt; our teams uncovered at least one bug during verification testing</p> -<p>16:07 <code>&lt;blackboxsw</code>&gt; LINK <a href="https://bugs.launchpad.net/cloud-init/+bug/1725067">https://bugs.launchpad.net/cloud-init/+bug/1725067</a></p> -<p>16:07 <code>&lt;ubot5</code>&gt; Ubuntu bug 1725067 in cloud-init (Ubuntu Artful) "cloud-init resizefs fails when booting with root=PARTUUID=" [Medium,Fix committed]</p> -<p>16:08 <code>&lt;blackboxsw</code>&gt; The former bug we have now resolved. This SRU will not be published until we resolve one other bug for EC2-specfic environments to ensure we retain behavior to always bring up dhcp4 on the primary nic</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; I don't think we have created a bug for the ec2 issue yet (it affects artful only) instances with only private ipv4 addresses allocated will not have dhcp4 config'd for that instance</p> -<p>16:10 <code>&lt;blackboxsw</code>&gt; We'll link a bug for the above today</p> -<p>16:10 <code>&lt;blackboxsw</code>&gt; other work on cloud-init... paste coming</p> -<p>16:11 <code>&lt;blackboxsw</code>&gt; * Fix systemd mount target due to busy device or already mounted (LP: #1718287)</p> -<p>16:11 <code>&lt;blackboxsw</code>&gt; * Fix simpleteable object as output string (LP: #1722566)</p> -<p>16:11 <code>&lt;blackboxsw</code>&gt; * Fix netplan bridge stp boolean (LP: #1721157)</p> -<p>16:11 <code>&lt;blackboxsw</code>&gt; * Fix cc_ntp to allow empty configuration "ntp:". Fix ntp integration test to provide valid empty ntp config (LP: 1724951)</p> -<p>16:11 <code>&lt;blackboxsw</code>&gt; * Fixed cc_lxd to allow for missing bridge definitions in lxd cloud-config</p> -<p>16:11 <code>&lt;blackboxsw</code>&gt; * Dropped fastestmirror plugin for CentOS tests</p> -<p>16:11 <code>&lt;blackboxsw</code>&gt; * Numerous test and CI stability improvements</p> -<p>16:11 <code>&lt;ubot5</code>&gt; Launchpad bug 1718287 in cloud-init "systemd mount targets fail due to device busy or already mounted" [High,Fix committed] <a href="https://launchpad.net/bugs/1718287">https://launchpad.net/bugs/1718287</a></p> -<p>16:11 <code>&lt;ubot5</code>&gt; Launchpad bug 1722566 in cloud-init "ci-info: <code>&lt;cloudinit.simpletable.SimpleTable object at 0x7fa98d222748</code>&gt;" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1722566">https://launchpad.net/bugs/1722566</a></p> -<p>16:11 <code>&lt;ubot5</code>&gt; Launchpad bug 1721157 in cloud-init "netplan render drops bridge_stp setting" [High,Fix committed] <a href="https://launchpad.net/bugs/1721157">https://launchpad.net/bugs/1721157</a></p> -<p>16:11 <code>&lt;ubot5</code>&gt; Launchpad bug 1724951 in cloud-init "Ntp schema definition permits empty ntp cloud-config, but code disallows" [Medium,In progress] <a href="https://launchpad.net/bugs/1724951">https://launchpad.net/bugs/1724951</a></p> -<p>16:13 <code>&lt;blackboxsw</code>&gt; Also we got a couple of gentoo commits from ckonstanski to Use "rc-service" rather than "service". Thanks again</p> -<p>16:13 <code>&lt;rharper</code>&gt; \o/</p> -<p>16:14 <code>&lt;ckonstanski</code>&gt; You're welcome, though those were just tiny toy commits to get me indocrinated into the launchpad process. Getting NTP tests to work in gentoo will be more significant.</p> -<p>16:15 <code>&lt;blackboxsw</code>&gt; ckonstanski: testing always is time-consuming, but totally worth it. We are still trying build our unit test coverage up so we don't get suprises on different platforms/clouds when sparsely tested modules run. Thanks again</p> -<p>16:16 <code>&lt;blackboxsw</code>&gt; oops sorry about the topic for the above ... that should have been the following</p> -<p>16:16 <code>&lt;blackboxsw</code>&gt; #topic Recent Changes</p> -<p>16:16 <code>&lt;blackboxsw</code>&gt; anything else for recent changes that have landed rharper powersj or others?</p> -<p>16:17 <code>&lt;powersj</code>&gt; nope</p> -<p>16:17 <code>&lt;rharper</code>&gt; blackboxsw: not yet</p> -<p>16:17 <code>&lt;blackboxsw</code>&gt; ok then let's move to next topic</p> -<p>16:17 <code>&lt;blackboxsw</code>&gt; #meetingstatus In Progress Development</p> -<p>16:17 <code>&lt;blackboxsw</code>&gt; for real.</p> -<p>16:18 <code>&lt;blackboxsw</code>&gt; ok so we are wrapping up that one Ec2 bug that was raised by Sargun on friday (which affects Artful)</p> -<p>16:18 <code>&lt;blackboxsw</code>&gt; When we have that branch in place, we can kick our final validation of the cloud-init 17.1 updates to Xenial Zesty and Artful.</p> -<p>16:19 <code>&lt;blackboxsw</code>&gt; I know smoser just uploaded cloud-init to the newly opened Bionic release as well</p> -<p>16:19 <code>&lt;blackboxsw</code>&gt; We will be hitting the review queue a bit this week to wrap up content that we want landed once master is open for more dyna</p> -<p>16:20 <code>&lt;blackboxsw</code>&gt; We will be hitting the review queue a bit this week to wrap up content that we want landed once master is open for more significant changesets</p> -<p>16:21 <code>&lt;blackboxsw</code>&gt; we've been a little risk averse during the SRU release process</p> -<p>16:21 <code>&lt;blackboxsw</code>&gt; As always please watch our trello board for progress on anything we are working</p> -<p>16:21 <code>&lt;blackboxsw</code>&gt; 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:22 <code>&lt;powersj</code>&gt; need that #</p> -<p>16:22 <code>&lt;blackboxsw</code>&gt; #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:22 <code>&lt;blackboxsw</code>&gt; ahh thanks oops</p> -<p>16:23 <code>&lt;robjo</code>&gt; speaking of reviews thanks for the help so far blackboxsw , now that my schedule should be a bit less crazy I'd like to get back to <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/addZyppRepos">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/addZyppRepos</a></p> -<p>16:23 <code>&lt;blackboxsw</code>&gt; Our focus as well for the upcoming work in cloud-init is to increase continuous integration coverage and tooling around cloud-init to make sure we can keep delivering stability across releases</p> -<p>16:24 <code>&lt;robjo</code>&gt; since I cannotreproduce the issue the bot has locally and I don't really understand the problem some more help is needed</p> -<p>16:24 <code>&lt;blackboxsw</code>&gt; ahh hiya robjo</p> -<p>16:24 <code>&lt;powersj</code>&gt; that looks merged</p> -<p>16:24 <code>&lt;blackboxsw</code>&gt; robjo: good to hear, we'll watch for updates.</p> -<p>16:25 <code>&lt;powersj</code>&gt; smoser went and fixed the flake8 issues</p> -<p>16:25 <code>&lt;blackboxsw</code>&gt; robjo: do you mean another branch?</p> -<p>16:25 <code>&lt;robjo</code>&gt; blackboxsw: no, that branch, but bot thinks " Needs Fixing ", I just don't get why</p> -<p>16:26 <code>&lt;blackboxsw</code>&gt; yeah per robjo's work cloud-init folks can also configure zypper repos . We landed it Sept 21st. (So it's in cloud-init 17.1)</p> -<p>16:26 <code>&lt;blackboxsw</code>&gt; commit cc1475d07b9d0727012634ee9c7a914d67b051f5</p> -<p>16:26 <code>&lt;blackboxsw</code>&gt; Author: Robert Schweikert <code>&lt;rjschwei@suse.com</code>&gt;</p> -<p>16:26 <code>&lt;blackboxsw</code>&gt; Date: Thu Sep 21 11:58:28 2017 -0400</p> -<p>16:27 <code>&lt;robjo</code>&gt; Oh, so it did get merged, missed that, never mind</p> -<p>16:27 <code>&lt;blackboxsw</code>&gt; as powersj mentioned, I think it was a flake8 CI test issue, so we just fixed the minor issue and landed it as it wasn't a significant content change</p> -<p>16:28 <code>&lt;powersj</code>&gt; cloudinit/config/cc_zypper_add_repo.py:15:1: H306: imports not in alphabetical order (cloudinit.util, cloudinit.config.schema.get_schema_doc)</p> -<p>16:28 <code>&lt;robjo</code>&gt; much appreciated, still a bit concerning that the flake8 issue did not show up locally :(</p> -<p>16:28 <code>&lt;blackboxsw</code>&gt; thx powersj</p> -<p>16:29 <code>&lt;powersj</code>&gt; is correct way <a href="https://paste.ubuntu.com/25852643/">https://paste.ubuntu.com/25852643/</a></p> -<p>16:29 <code>&lt;robjo</code>&gt; SO flake8 has serious issue with the definition of alpha order :(</p> -<p>16:30 <code>&lt;blackboxsw</code>&gt; ;)</p> -<p>16:30 <code>&lt;blackboxsw</code>&gt; ok anything else for "In Progress Development" if not we'll transition to the next topic</p> -<p>16:30 <code>&lt;blackboxsw</code>&gt; #topic Open Discussion / Office Hours (30 mins)</p> -<p>16:31 <code>&lt;blackboxsw</code>&gt; ok we'll hang out in channel if anyone has topics, bugs or features they want to discuss or need some feedback on</p> -<p>16:35 <code>&lt;blackboxsw</code>&gt; and as always thanks for contributions folks. It's really great to work on a project where there is so much interest and investment</p> -<p>16:42 <code>&lt;smoser</code>&gt; blackboxsw: hey. i'm back now. did you open a bug?</p> -<p>16:42 <code>&lt;smoser</code>&gt; i can do so now if you have not.</p> -<p>16:43 <code>&lt;blackboxsw</code>&gt; smoser: I haven't done that yet, was just working out the fix</p> -<p>16:43 <code>&lt;blackboxsw</code>&gt; please do, then we can link it here</p> -<p>16:43 <code>&lt;smoser</code>&gt; ok. i'll do so. and i realized a comment you were making about artful.</p> -<p>16:43 <code>&lt;smoser</code>&gt; that we could go leave artful configuring all nics it saw.</p> -<p>16:43 <code>&lt;blackboxsw</code>&gt; right, because we allow change of behavior in artful right?</p> -<p>16:44 <code>&lt;smoser</code>&gt; as that isn't necessarily "broken" behavior.</p> -<p>16:44 <code>&lt;smoser</code>&gt; yeah. i didnt understand that when you said it.</p> -<p>16:44 <code>&lt;blackboxsw</code>&gt; ahh, I get you. Right, just that the new behavior of configuring all nics is acceptable as new behavior, but not for Xenial. It's just that artful is slightly busted for local-only ipv4</p> -<p>16:45 <code>&lt;smoser</code>&gt; i think it might be easiest both in terms of fixing and in terms of keeping things in our head if we just keep the same behavior everywhere for now.</p> -<p>16:46 <code>&lt;smoser</code>&gt; that is... make artful act like xenial in only configuring one nic</p> -<p>16:48 <code>&lt;smoser</code>&gt; blackboxsw: actually i dont think there is any reason why we shoudlnt just use bug 1728152</p> -<p>16:48 <code>&lt;ubot5</code>&gt; bug 1728152 in cloud-init "IPv4 and IPv6 Dual Stack Does Not work when instance is not assigned public IPv4 address" [High,In progress] <a href="https://launchpad.net/bugs/1728152">https://launchpad.net/bugs/1728152</a></p> -<p>16:48 <code>&lt;smoser</code>&gt; unless you disagree</p> -<p>16:51 <code>&lt;blackboxsw</code>&gt; +1 smoser</p> -<p>16:52 <code>&lt;blackboxsw</code>&gt; lets use that bug</p> -<p>16:59 <code>&lt;blackboxsw</code>&gt; #LINK <a href="https://launchpad.net/bugs/1728152">https://launchpad.net/bugs/1728152</a></p> -<p>16:59 <code>&lt;ubot5</code>&gt; Ubuntu bug 1728152 in cloud-init "EC2 IPv4 and IPv6 Dual Stack Does Not work when instance is not assigned public IPv4 address" [High,In progress]</p> -<p>16:59 <code>&lt;blackboxsw</code>&gt; ok looks like we are good for the status meeting</p> -<p>17:00 <code>&lt;blackboxsw</code>&gt; thanks for joining all. see you in two weeks</p> -<p>17:00 <code>&lt;blackboxsw</code>&gt; #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2017-10-16T16:06:00+00:002017-10-16T16:06:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2017-10-16:/status-2017-10-16.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Office Hours, 16 Oct at 16:06 &mdash; 17:03 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-10-16-16.06.log.html">http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-10-16-16.06.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:08</p> -<h3>In Progress Development</h3> -<p>The discussion about "In Progress Development …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Office Hours, 16 Oct at 16:06 &mdash; 17:03 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-10-16-16.06.log.html">http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-10-16-16.06.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:08</p> -<h3>In Progress Development</h3> -<p>The discussion about "In Progress Development" started at 16:13</p> -<ul> -<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://trello.com/c/wROS4mKT/458-sru-171">https://trello.com/c/wROS4mKT/458-sru-171</a> </li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1722668">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1722668</a> </li> -<li><strong>LINK</strong>: <a href="https://gist.github.com/smoser/49444542158f2e5f88f1/#file-lxc-pstart-md">https://gist.github.com/smoser/49444542158f2e5f88f1/#file-lxc-pstart-md</a></li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bug/1722992">https://bugs.launchpad.net/cloud-init/+bug/1722992</a> </li> -</ul> -<h3>Office Hours</h3> -<p>The discussion about "Office Houres" started at 16:25</p> -<ul> -<li>open season for discussions, bug requests, review requests for the next 30 mins</li> -</ul> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (49)</li> -<li>smoser (8)</li> -<li>ubot5 (3)</li> -<li>meetingology (3)</li> -<li>rharper (3)</li> -</ul> -<h2>Full Log</h2> -<p>16:06 <code>&lt;blackboxsw</code>&gt; #startmeeting Cloud-init bi-weekly status</p> -<p>16:06 <code>&lt;meetingology</code>&gt; Meeting started Mon Oct 16 16:06:51 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:06 <code>&lt;meetingology</code>&gt; </p> -<p>16:06 <code>&lt;meetingology</code>&gt; Available commands: action commands idea info link nick</p> -<p>16:08 <code>&lt;blackboxsw</code>&gt; #topic Recent Changes</p> -<p>16:08 <code>&lt;blackboxsw</code>&gt; Ok last couple of weeks for our team were</p> -<p>16:08 <code>&lt;blackboxsw</code>&gt; Ok last couple of weeks for our team were</p> -<p>16:08 <code>&lt;blackboxsw</code>&gt; Ok last couple of weeks for our team were 'impacted' by a couple of work conferences for planning next release of cloud-init/curtin etc.</p> -<p>16:08 <code>&lt;rharper</code>&gt; o/</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; so things felt a bit slow. but folks have still made some good progress.</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; Some changes that have landed in master:</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; Robert Schweikert: suse cloud-config module to add zypper repos and zypp config</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; Robert Schweikert: Allow cloud-init.final stage to spawn infinite processes</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; Andrew Jorgensen: Remove prettytable dependency</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; Fix dhcp parsing in Artful of networkd leases for CloudStack and Azure</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; Updated packaging copyright file (LP: #1718681)</p> -<p>16:09 <code>&lt;ubot5</code>&gt; Launchpad bug 1718681 in cloud-init "Package copyright file omits Apache 2 license" [High,Fix committed] <a href="https://launchpad.net/bugs/1718681">https://launchpad.net/bugs/1718681</a></p> -<p>16:10 <code>&lt;smoser</code>&gt; o/</p> -<p>16:10 <code>&lt;blackboxsw</code>&gt; thanks a lot for the contributions on that front folks. There have been a couple of work items that fell out of our conferences related to Ubuntu artful and systemd/networkd support so we've been workin those</p> -<p>16:11 <code>&lt;blackboxsw</code>&gt; on the testing front we've re-enable tox support for integration tests</p> -<p>16:11 <code>&lt;blackboxsw</code>&gt; and Ubuntu-only has queued a 17.1 SRU release/update into xenial and zesty</p> -<p>16:12 <code>&lt;blackboxsw</code>&gt; smoser: rharper powersj anyone else anything else I'm missing on recent changes?</p> -<p>16:12 <code>&lt;rharper</code>&gt; blackboxsw: that sounds right</p> -<p>16:13 <code>&lt;blackboxsw</code>&gt; ok. next topic</p> -<p>16:13 <code>&lt;blackboxsw</code>&gt; #topic In progress development</p> -<p>16:14 <code>&lt;blackboxsw</code>&gt; As mentioned, we are walking through the Ubuntu xenial/zesty SRU validation process, so I excpect we will have a release update published this week</p> -<p>16:14 * blackboxsw grabs the trello card link</p> -<p>16:14 <code>&lt;blackboxsw</code>&gt; #link <a href="https://trello.com/c/wROS4mKT/458-sru-171">https://trello.com/c/wROS4mKT/458-sru-171</a></p> -<p>16:15 <code>&lt;blackboxsw</code>&gt; This card will move to the Done lane once we've finished publishing</p> -<p>16:16 <code>&lt;blackboxsw</code>&gt; I know powersj has been working the integration test front for KVM as time permits. There will be some upcoming changes there to get us more complex storage/network testing on kvm</p> -<p>16:16 <code>&lt;blackboxsw</code>&gt; I know smoser is also working on a couple of Azure-related fixes for artful as well.</p> -<p>16:16 <code>&lt;blackboxsw</code>&gt; anything else to add there?</p> -<p>16:17 <code>&lt;smoser</code>&gt; <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1722668">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1722668</a></p> -<p>16:17 <code>&lt;rharper</code>&gt; nothing from me</p> -<p>16:17 <code>&lt;ubot5</code>&gt; Ubuntu bug 1722668 in cloud-init (Ubuntu) "Azure: bouncing of network device/publishing of hostname fails on artful" [Critical,Confirmed]</p> -<p>16:17 <code>&lt;blackboxsw</code>&gt; #link <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1722668">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1722668</a></p> -<p>16:18 <code>&lt;blackboxsw</code>&gt; thx</p> -<p>16:18 <code>&lt;smoser</code>&gt; that one i'm working on, and then also been trying to get lxc/mount-image-callback</p> -<p>16:19 <code>&lt;smoser</code>&gt; the use we ahve for 'lxc-proposed-snapshot' and also for 'mount-image-callback'</p> -<p>16:19 <code>&lt;blackboxsw</code>&gt; Also in the same vein of improving dev testing of Ubuntu or really any lxc image is that work smoser referenced above.</p> -<p>16:20 <code>&lt;blackboxsw</code>&gt; smoser: is that worth a link at the moment or does it still need polish?</p> -<p>16:20 <code>&lt;smoser</code>&gt; <a href="https://gist.github.com/smoser/49444542158f2e5f88f1/">https://gist.github.com/smoser/49444542158f2e5f88f1/</a>#file-lxc-pstart-md</p> -<p>16:20 <code>&lt;blackboxsw</code>&gt; sweet</p> -<p>16:20 <code>&lt;blackboxsw</code>&gt; #link <a href="https://gist.github.com/smoser/49444542158f2e5f88f1/">https://gist.github.com/smoser/49444542158f2e5f88f1/</a>#file-lxc-pstart-md</p> -<p>16:20 <code>&lt;smoser</code>&gt; right now that is only known to work on lxc 2.18</p> -<p>16:21 <code>&lt;smoser</code>&gt; i think we can make it work with earlier versions, and would like to make it work with xenial (2.02.. maybe)</p> -<p>16:22 <code>&lt;blackboxsw</code>&gt; yeah I just got my artful box up and was going to use that for the SRU verification</p> -<p>16:22 <code>&lt;blackboxsw</code>&gt; also, I think we were going to peek at a solution for the following bug:</p> -<p>16:22 <code>&lt;blackboxsw</code>&gt; #link <a href="https://bugs.launchpad.net/cloud-init/+bug/1722992">https://bugs.launchpad.net/cloud-init/+bug/1722992</a></p> -<p>16:22 <code>&lt;ubot5</code>&gt; Ubuntu bug 1722992 in cloud-init "On the latest centos 7 release, we are unable to resize our instances filesystems" [Medium,Confirmed]</p> -<p>16:23 <code>&lt;blackboxsw</code>&gt; so there might be some minor changes for the OpenStack/MAAS and ConfigDrive datasources</p> -<p>16:24 <code>&lt;blackboxsw</code>&gt; ok anything else in "In progress development"?</p> -<p>16:24 <code>&lt;blackboxsw</code>&gt; I know we have a queue of active reviews we need to get through. I was expecting we'll have bandwidth for that after this SRU push.</p> -<p>16:24 <code>&lt;blackboxsw</code>&gt; #link <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a></p> -<p>16:25 <code>&lt;blackboxsw</code>&gt; #topic Office Hours</p> -<p>16:26 <code>&lt;blackboxsw</code>&gt; #info open season for discussions, bug requests, review requests for the next 30 mins</p> -<p>16:29 <code>&lt;smoser</code>&gt; thanks blackboxsw</p> -<p>16:34 <code>&lt;blackboxsw</code>&gt; no prob. I was peeking around at puppet this weekend.... might have a branch puppet local(masterless deployment) to put up this week</p> -<p>16:34 <code>&lt;blackboxsw</code>&gt; I sort of got distracted by shiny objects while trying to write an SRU test for our existing puppet</p> -<p>16:34 <code>&lt;blackboxsw</code>&gt; config module</p> -<p>17:01 <code>&lt;blackboxsw</code>&gt; ok two more SRU tests left to write for Azure and datasourceOVF. then we can start validation for the upload</p> -<p>17:02 <code>&lt;blackboxsw</code>&gt; office hours coming to a close. but we'll still float in here as always. Happy Monday folks</p> -<p>17:02 <code>&lt;blackboxsw</code>&gt; just ping us directly by IRC nick if you aren't getting a response otherwise.</p> -<p>17:03 <code>&lt;blackboxsw</code>&gt; tanks again.</p> -<p>17:03 <code>&lt;blackboxsw</code>&gt; thanks even</p> -<p>17:03 <code>&lt;blackboxsw</code>&gt; #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2017-10-02T16:05:00+00:002017-10-02T16:05:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2017-10-02:/status-2017-10-02.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init, 02 Oct at 16:05 &mdash; 17:29 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-10-02-16.05.log.html">http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-10-02-16.05.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent Changes / Highlights</h3> -<p>The discussion about "Recent Changes / Highlights" started at 16:06.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://lists.launchpad.net/cloud-init/msg00106.html">https://lists.launchpad.net/cloud-init/msg00106.html …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init, 02 Oct at 16:05 &mdash; 17:29 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-10-02-16.05.log.html">http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-10-02-16.05.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent Changes / Highlights</h3> -<p>The discussion about "Recent Changes / Highlights" started at 16:06.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://lists.launchpad.net/cloud-init/msg00106.html">https://lists.launchpad.net/cloud-init/msg00106.html</a> </li> -<li><strong>LINK</strong>: <a href="https://launchpad.net/cloud-init/+milestone/17.2">https://launchpad.net/cloud-init/+milestone/17.2</a> </li> -<li>please target bugs to the next release</li> -</ul> -<h3>In Progress Development / Highlights</h3> -<p>The discussion about "In Progress Development / Highlights" started at 16:09.</p> -<ul> -<li><strong>LINK</strong>: <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a> </li> -<li><strong>LINK</strong>: ? </li> -<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="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/taskLimit">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/taskLimit</a> that's the branch for the task limit</li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init">https://bugs.launchpad.net/cloud-init</a> </li> -<li><strong>LINK</strong>: <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a> </li> -</ul> -<h3>Open Discussion / Office Hours</h3> -<p>The discussion about "Open Discussion / Office Hours" started at 16:17.</p> -<ul> -<li><strong>LINK</strong>: <a href="http://paste.ubuntu.com/25661692/">http://paste.ubuntu.com/25661692/</a> </li> -<li><strong>LINK</strong>: <a href="http://paste.ubuntu.com/25661714/">http://paste.ubuntu.com/25661714/</a> </li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bug/1720841">https://bugs.launchpad.net/cloud-init/+bug/1720841</a> </li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bug/1720841">https://bugs.launchpad.net/cloud-init/+bug/1720841</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~ajorgens/cloud-init/+git/cloud-init/+merge/330525">https://code.launchpad.net/~ajorgens/cloud-init/+git/cloud-init/+merge/330525</a> ;-)</li> -</ul> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>smoser (88)</li> -<li>ajorg (51)</li> -<li>rharper (28)</li> -<li>blackboxsw (25)</li> -<li>robjo (4)</li> -<li>ubot5 (3)</li> -<li>meetingology (3)</li> -</ul> -<h2>Full Log</h2> -<p>16:05 <code>&lt;smoser</code>&gt; #startmeeting cloud-init</p> -<p>16:05 <code>&lt;meetingology</code>&gt; Meeting started Mon Oct 2 16:05:47 2017 UTC. The chair is smoser. Information about MeetBot at <a href="http://wiki.ubuntu.com/meetingology.">http://wiki.ubuntu.com/meetingology.</a></p> -<p>16:05 <code>&lt;meetingology</code>&gt; </p> -<p>16:05 <code>&lt;meetingology</code>&gt; Available commands: action commands idea info link nick</p> -<p>16:06 <code>&lt;smoser</code>&gt; #topic Recent Changes / Highlights</p> -<p>16:06 <code>&lt;smoser</code>&gt; hm..</p> -<p>16:06 <code>&lt;smoser</code>&gt; 17.1 released <a href="https://lists.launchpad.net/cloud-init/msg00106.html">https://lists.launchpad.net/cloud-init/msg00106.html</a></p> -<p>16:06 <code>&lt;smoser</code>&gt; thats the biggest thing and only thing i have for this topic</p> -<p>16:06 <code>&lt;blackboxsw</code>&gt; #link <a href="https://lists.launchpad.net/cloud-init/msg00106.html">https://lists.launchpad.net/cloud-init/msg00106.html</a></p> -<p>16:06 <code>&lt;smoser</code>&gt; horay for a release, thanks to those who contributed.</p> -<p>16:07 <code>&lt;rharper</code>&gt; \o/</p> -<p>16:07 <code>&lt;smoser</code>&gt; 17.2 is set for 2017-12-14</p> -<p>16:08 <code>&lt;smoser</code>&gt; <a href="https://launchpad.net/cloud-init/+milestone/17.2">https://launchpad.net/cloud-init/+milestone/17.2</a></p> -<p>16:08 <code>&lt;ajorg</code>&gt; yay!</p> -<p>16:08 <code>&lt;smoser</code>&gt; feel free to target bugs to that release.</p> -<p>16:08 <code>&lt;rharper</code>&gt; #link <a href="https://launchpad.net/cloud-init/+milestone/17.2">https://launchpad.net/cloud-init/+milestone/17.2</a></p> -<p>16:08 <code>&lt;rharper</code>&gt; #info please target bugs to the next release</p> -<p>16:09 <code>&lt;smoser</code>&gt; does that do anyting ?</p> -<p>16:09 <code>&lt;rharper</code>&gt; in the meeting summary, it does</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; smoser: the links showed up in meeting minutes last time</p> -<p>16:09 <code>&lt;smoser</code>&gt; k. i always expected the bot to tell me that in a pm</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; meetingology didn't echo though</p> -<p>16:09 <code>&lt;rharper</code>&gt; well, smoser may have to do those</p> -<p>16:09 <code>&lt;smoser</code>&gt; #topic In Progress Development / Highlights</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; same. but something is up that needs attention.</p> -<p>16:10 <code>&lt;blackboxsw</code>&gt; I'll properly handle it when publishing</p> -<p>16:10 <code>&lt;rharper</code>&gt; cool</p> -<p>16:11 <code>&lt;smoser</code>&gt; Merge Proposals</p> -<p>16:11 <code>&lt;smoser</code>&gt; #link <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a></p> -<p>16:11 <code>&lt;smoser</code>&gt; there are some there for sure. i know that robjo has some he's interested in, and i think ajorg's instance-identity deserves a look</p> -<p>16:12 <code>&lt;smoser</code>&gt; as well as simpletable for 17.2</p> -<p>16:12 <code>&lt;ajorg</code>&gt; I'd be grateful for both, yes.</p> -<p>16:12 <code>&lt;smoser</code>&gt; i am looking at the 'networkd' one which is a blocker as currently Ubuntu does not work properly on azure</p> -<p>16:12 <code>&lt;blackboxsw</code>&gt; we should have more bandwidth this week</p> -<p>16:12 <code>&lt;smoser</code>&gt; and all sysstemd-networkd systems will not work properly on CloudStack.</p> -<p>16:12 <code>&lt;smoser</code>&gt; anything else there?</p> -<p>16:13 <code>&lt;robjo</code>&gt; The task limit increase has been tested and solves our problem, thus merging would be great</p> -<p>16:13 <code>&lt;smoser</code>&gt; robjo, yeah. athat does seem unlikely to cause issue</p> -<p>16:13 <code>&lt;smoser</code>&gt; Trello Board</p> -<p>16:13 <code>&lt;smoser</code>&gt; # <a href="https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin">https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin</a></p> -<p>16:13 <code>&lt;rharper</code>&gt; #link ?</p> -<p>16:13 <code>&lt;smoser</code>&gt; #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:14 <code>&lt;robjo</code>&gt; <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/taskLimit">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/taskLimit</a> that's the branch for the task limit</p> -<p>16:15 <code>&lt;robjo</code>&gt; Sorry, I can never find the link for the open merge proposals :( problem exists between the keyboard and the chair</p> -<p>16:16 <code>&lt;blackboxsw</code>&gt; will get eyes on that today robjo as your addZypper is about wrapped</p> -<p>16:16 <code>&lt;smoser</code>&gt; Bugs</p> -<p>16:16 <code>&lt;smoser</code>&gt; #link <a href="https://bugs.launchpad.net/cloud-init">https://bugs.launchpad.net/cloud-init</a></p> -<p>16:16 <code>&lt;smoser</code>&gt; just mostly pointers... above.</p> -<p>16:16 <code>&lt;smoser</code>&gt; for Ubuntu in 16.04, there is one SRU in progress that blackboxsw and i need to verify today</p> -<p>16:16 <code>&lt;smoser</code>&gt; and then we will be soon looking at doing an SRU of 17.1-ish</p> -<p>16:17 <code>&lt;robjo</code>&gt; Thanks, still in europe, my day is about done, will pick it up tomorrow</p> -<p>16:17 <code>&lt;smoser</code>&gt; robjo, link is in topic</p> -<p>16:17 <code>&lt;smoser</code>&gt; <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a></p> -<p>16:17 <code>&lt;smoser</code>&gt; ok. so open discussion i guess. no w?</p> -<p>16:17 <code>&lt;smoser</code>&gt; #topic Open Discussion / Office Hours</p> -<p>16:17 <code>&lt;smoser</code>&gt; we'll hang around and pay attention to pings and discussion fro the next 30 minutes or so.</p> -<p>16:18 <code>&lt;smoser</code>&gt; and after that, feel free to ping.</p> -<p>16:19 <code>&lt;ajorg</code>&gt; I'm writing a unit test for a bugfix I'm preparing to submit. It works, but it's slow because readurl retries and waits a second each time</p> -<p>16:20 <code>&lt;ajorg</code>&gt; I'm a bit of a mock / patch newb. Anyone can help me see how to patch that argument?</p> -<p>16:20 <code>&lt;smoser</code>&gt; you can feel free to mock readurl</p> -<p>16:20 <code>&lt;smoser</code>&gt; and set its return_value and look at calls</p> -<p>16:21 <code>&lt;smoser</code>&gt; then you dont have to httppretty.</p> -<p>16:21 <code>&lt;ajorg</code>&gt; The only thing I want to change about it is the sleep though. Is there a straightforward way to just change one arg?</p> -<p>16:21 <code>&lt;blackboxsw</code>&gt; tests/unittests/test_handler/test_handler_chef.py is an example and tests/unittests/test_datasource/test_maas.py</p> -<p>16:21 <code>&lt;blackboxsw</code>&gt; I think</p> -<p>16:21 <code>&lt;ajorg</code>&gt; Hmm, I could do that, yeah. Would be sufficient for this.</p> -<p>16:22 <code>&lt;ajorg</code>&gt; I'd still like to know if there's an easy way to just change one argument to something that gets called somewhere else.</p> -<p>16:22 <code>&lt;smoser</code>&gt; you could also mock the time.sleep from url_helper</p> -<p>16:22 <code>&lt;ajorg</code>&gt; hahaha, yes. that's what I need to do.</p> -<p>16:22 <code>&lt;rharper</code>&gt; ajorg: if you want to mock the sleep you can decorate the test_ method with @mock.patch(time.sleep)</p> -<p>16:22 <code>&lt;smoser</code>&gt; we're suggesting other ways generally because there isn't :) at least that i know of.</p> -<p>16:23 <code>&lt;ajorg</code>&gt; that's cool, patching time.sleep will do nicely</p> -<p>16:24 <code>&lt;ajorg</code>&gt; is there an integration test that looks at what lands on the console?</p> -<p>16:24 <code>&lt;ajorg</code>&gt; (going back to my question from before the meeting)</p> -<p>16:25 <code>&lt;smoser</code>&gt; no. there coudl be on the nocloud-kvm backend</p> -<p>16:25 <code>&lt;smoser</code>&gt; but i think there is no console access currently on lxd</p> -<p>16:25 <code>&lt;smoser</code>&gt; and i think that we do not collect console access on nocloud-kvm</p> -<p>16:25 <code>&lt;smoser</code>&gt; but as you suggest we should for sure</p> -<p>16:25 <code>&lt;ajorg</code>&gt; k</p> -<p>16:26 <code>&lt;ajorg</code>&gt; I wondered if systemd might be swallowing my output, or maybe python (boothook in this case is a python script) is making a strange choice when it sets up logging.</p> -<p>16:27 <code>&lt;rharper</code>&gt; certainly possible; I know there were issues with cloud-init starting before say rsyslog on non-systemd boots</p> -<p>16:28 <code>&lt;rharper</code>&gt; and the python logging has changed w.r.t the default configuration; cloud-init main sort of expects this transition as it starts up in init-local and it has not yet read the cloud-config for logging configuration yet, so it reads that and then does some replay</p> -<p>16:28 <code>&lt;ajorg</code>&gt; interesting</p> -<p>16:29 <code>&lt;smoser</code>&gt; ajorg, you're writing to stdout/err with logging from a boothook ?</p> -<p>16:29 <code>&lt;ajorg</code>&gt; at least I would have thought cloud-init-output.log would contain my logs though, since it's more a redirect of stderr and stdout, right?</p> -<p>16:29 <code>&lt;ajorg</code>&gt; yeah</p> -<p>16:29 <code>&lt;rharper</code>&gt; correct</p> -<p>16:29 <code>&lt;rharper</code>&gt; this is from a bootcmd ?</p> -<p>16:29 <code>&lt;ajorg</code>&gt; no, #cloud-boothook</p> -<p>16:29 * rharper hasn't used boothook</p> -<p>16:29 <code>&lt;smoser</code>&gt; hm..</p> -<p>16:30 <code>&lt;ajorg</code>&gt; boothooks are super useful</p> -<p>16:32 <code>&lt;rharper</code>&gt; smoser: when do boot_hooks run ? local ? net ?</p> -<p>16:33 <code>&lt;rharper</code>&gt; I'm not sure yet where stdout/err for boot hooks occur, but you can dump each from the units via: journalctl -u cloud-init-local.service (or cloud-init.service)</p> -<p>16:33 <code>&lt;blackboxsw</code>&gt; "This is the earliest hook available. Note, that there is no mechanism provided for running only once"</p> -<p>16:34 <code>&lt;blackboxsw</code>&gt; I'm checking the code now (local/pre-local maybe)?</p> -<p>16:34 <code>&lt;rharper</code>&gt; yeah, saw that; it runs in-image scripts programs</p> -<p>16:34 <code>&lt;ajorg</code>&gt; I did that too, and don't see anything.</p> -<p>16:34 <code>&lt;ajorg</code>&gt; (journalctl)</p> -<p>16:34 <code>&lt;rharper</code>&gt; you should see some output</p> -<p>16:34 <code>&lt;rharper</code>&gt; but not seeing your hook in there ?</p> -<p>16:34 <code>&lt;ajorg</code>&gt; I can tell by other means that the hook ran</p> -<p>16:34 <code>&lt;ajorg</code>&gt; just don't see that it printed anything</p> -<p>16:35 <code>&lt;ajorg</code>&gt; my prime suspect if systemd can't do something bad here is that python makes some decision about not actually logging.</p> -<p>16:35 <code>&lt;ajorg</code>&gt; and I need to be more explicit that it should log</p> -<p>16:36 <code>&lt;rharper</code>&gt; so, the boot_hook will sub out each part, I see no capture on the stderr/stdout ; so I would expect those to go to whatever is currently capturing those;</p> -<p>16:37 <code>&lt;rharper</code>&gt; s/sub/subprocess</p> -<p>16:38 <code>&lt;ajorg</code>&gt; yup, that's what I expect too, and what I recall seeing on Amazon Linux</p> -<p>16:38 <code>&lt;rharper</code>&gt; since it's using cloud-init's util.subp, there <em>should</em> be a debug level message saying 'Running command %s with allowed return codes %s' which maches a path to the boothook</p> -<p>16:38 <code>&lt;rharper</code>&gt; I would expect to see that in the cloud-init.log</p> -<p>16:39 <code>&lt;smoser</code>&gt; <a href="http://paste.ubuntu.com/25661692/">http://paste.ubuntu.com/25661692/</a></p> -<p>16:39 <code>&lt;ajorg</code>&gt; yup, I do see that</p> -<p>16:39 <code>&lt;rharper</code>&gt; the output of script, I <em>think</em> should go to cloud-init-output.log</p> -<p>16:39 <code>&lt;smoser</code>&gt; i'm testing ^ on serverstack now.</p> -<p>16:39 <code>&lt;smoser</code>&gt; i verified the commands run on lxd but not look at console there.</p> -<p>16:39 <code>&lt;ajorg</code>&gt; thanks</p> -<p>16:40 <code>&lt;smoser</code>&gt; actually.. yeah, BOOTHOOK does run, but doesnt seem to have stdout tied to same place as bootcmd</p> -<p>16:41 <code>&lt;ajorg</code>&gt; oh?</p> -<p>16:41 <code>&lt;ajorg</code>&gt; I'm slightly surprised it's not just me</p> -<p>16:42 <code>&lt;smoser</code>&gt; <a href="http://paste.ubuntu.com/25661714/">http://paste.ubuntu.com/25661714/</a></p> -<p>16:42 <code>&lt;rharper</code>&gt; it really should be in the journal/console if stdout is not redirected to a file, cloud-init-local service</p> -<p>16:43 <code>&lt;smoser</code>&gt; that reproduces in lxc</p> -<p>16:44 <code>&lt;rharper</code>&gt; smoser: in your instance on serverstack, do you see your BOOTHOOK in journalctl -b -u cloud-init-local.service ?</p> -<p>16:44 <code>&lt;smoser</code>&gt; ajorg, please go ahead and open a bug.</p> -<p>16:44 <code>&lt;ajorg</code>&gt; cool (not cool :-P)</p> -<p>16:44 <code>&lt;ajorg</code>&gt; will do</p> -<p>16:44 <code>&lt;smoser</code>&gt; # journalctl -b -u cloud-init.service | grep BOOT</p> -<p>16:44 <code>&lt;smoser</code>&gt; Oct 02 16:37:41 a5 cloud-init[121]: BOOTCMD: Mon, 02 Oct 2017 16:37:41 +0000: a5</p> -<p>16:44 <code>&lt;smoser</code>&gt; ^ that is from lxd</p> -<p>16:45 <code>&lt;rharper</code>&gt; and what about the welcome message from cloud-init ?</p> -<p>16:45 <code>&lt;smoser</code>&gt; i think not.</p> -<p>16:45 <code>&lt;rharper</code>&gt; bootcmd does: util.subp(cmd, env=env, capture=False) ; where boot_hook does: util.subp([filepath], env=env)</p> -<p>16:46 <code>&lt;smoser</code>&gt; yeah, so boot_hook definitely swallowed. and should not be.</p> -<p>16:47 <code>&lt;rharper</code>&gt; yeah</p> -<p>16:49 <code>&lt;ajorg</code>&gt; <a href="https://bugs.launchpad.net/cloud-init/+bug/1720841">https://bugs.launchpad.net/cloud-init/+bug/1720841</a></p> -<p>16:49 <code>&lt;ubot5</code>&gt; Ubuntu bug 1720841 in cloud-init "Output from boothook is not logged" [Undecided,New]</p> -<p>16:50 <code>&lt;ajorg</code>&gt; Meanwhile I need to setup more explicit logging from that boothook anyway, so I'm okay.</p> -<p>16:51 <code>&lt;blackboxsw</code>&gt; #link <a href="https://bugs.launchpad.net/cloud-init/+bug/1720841">https://bugs.launchpad.net/cloud-init/+bug/1720841</a></p> -<p>16:51 <code>&lt;ubot5</code>&gt; Ubuntu bug 1720841 in cloud-init "Output from boothook is not logged" [Medium,Confirmed]</p> -<p>16:55 <code>&lt;ajorg</code>&gt; Here's another one, which I've confirmed with a unit test and proposed a patch: <a href="https://bugs.launchpad.net/cloud-init/+bug/1720844">https://bugs.launchpad.net/cloud-init/+bug/1720844</a></p> -<p>16:55 <code>&lt;ubot5</code>&gt; Ubuntu bug 1720844 in cloud-init "UrlError from #include aborts stage" [Undecided,New]</p> -<p>16:55 <code>&lt;ajorg</code>&gt; (what is this #link thing you're doing there?)</p> -<p>16:55 <code>&lt;smoser</code>&gt; well, the bot is supposed to care and do somethign with it.</p> -<p>16:56 <code>&lt;smoser</code>&gt; but /me thinks it doesnt work right :)</p> -<p>16:56 <code>&lt;blackboxsw</code>&gt; ajorg: since meetingology is still active, the theory is it is keeping track of links during this meeting</p> -<p>16:56 <code>&lt;smoser</code>&gt; (during the meeting)</p> -<p>16:56 <code>&lt;ajorg</code>&gt; ah, okay</p> -<p>16:57 <code>&lt;ajorg</code>&gt; I think simpletable is completely ready to merge, btw. Any objections? <a href="https://code.launchpad.net/~ajorgens/cloud-init/+git/cloud-init/+merge/330525">https://code.launchpad.net/~ajorgens/cloud-init/+git/cloud-init/+merge/330525</a></p> -<p>16:57 <code>&lt;blackboxsw</code>&gt; The theory is it writes the meeting notes out for us so we can publish to <a href="https://cloud-init.github.io">https://cloud-init.github.io</a></p> -<p>16:57 <code>&lt;ajorg</code>&gt; #link <a href="https://code.launchpad.net/~ajorgens/cloud-init/+git/cloud-init/+merge/330525">https://code.launchpad.net/~ajorgens/cloud-init/+git/cloud-init/+merge/330525</a> ;-)</p> -<p>16:57 <code>&lt;blackboxsw</code>&gt; geg</p> -<p>16:57 <code>&lt;blackboxsw</code>&gt; heh</p> -<p>16:58 <code>&lt;blackboxsw</code>&gt; ajorg: I think we were good on that changeset, and we only wanted to wait post 17.1 cut to avoid potential regression</p> -<p>16:59 <code>&lt;ajorg</code>&gt; great</p> -<p>16:59 <code>&lt;blackboxsw</code>&gt; I'm +1 on that will give it a spin today and then I think we can land it</p> -<p>17:01 <code>&lt;smoser</code>&gt; blackboxsw, ajorg my thoughts on the simpletable...</p> -<p>17:01 <code>&lt;ajorg</code>&gt; here it comes...</p> -<p>17:01 <code>&lt;ajorg</code>&gt; :-P</p> -<p>17:01 <code>&lt;blackboxsw</code>&gt; :)</p> -<p>17:02 <code>&lt;smoser</code>&gt; i would like to have a machine friendly output available</p> -<p>17:02 <code>&lt;smoser</code>&gt; human friendly is good, but machine friendly solves the actual goal of writing the stuff.</p> -<p>17:02 <code>&lt;ajorg</code>&gt; So I modified it to display <em>exactly</em> as prettytable did</p> -<p>17:02 <code>&lt;smoser</code>&gt; oh really.</p> -<p>17:02 <code>&lt;smoser</code>&gt; wow</p> -<p>17:02 <code>&lt;ajorg</code>&gt; which is admittedly not machine friendly</p> -<p>17:02 <code>&lt;ajorg</code>&gt; not especially</p> -<p>17:02 <code>&lt;smoser</code>&gt; then i guess i can't object at all.</p> -<p>17:02 <code>&lt;ajorg</code>&gt; but it's at least as good as prettytable</p> -<p>17:03 <code>&lt;smoser</code>&gt; in that its backwards compat</p> -<p>17:03 <code>&lt;smoser</code>&gt; right.</p> -<p>17:03 <code>&lt;ajorg</code>&gt; ^ this was my goal, to get you to not object</p> -<p>17:03 <code>&lt;smoser</code>&gt; i still think we should probaly additionally write some machine friendly json</p> -<p>17:03 <code>&lt;ajorg</code>&gt; agreed, that would be better</p> -<p>17:03 <code>&lt;smoser</code>&gt; i tihnk having something human friendly is good though</p> -<p>17:03 <code>&lt;smoser</code>&gt; as i know <em>I</em> look at that output</p> -<p>17:04 <code>&lt;ajorg</code>&gt; it meets my goal of not depending on prettytable</p> -<p>17:04 <code>&lt;smoser</code>&gt; and parsing json would be less nice</p> -<p>17:04 <code>&lt;smoser</code>&gt; yeah</p> -<p>17:05 <code>&lt;smoser</code>&gt; so based on your assertion that it outputs the same as pretty table, i have no objections. only future hopes.</p> -<p>17:05 <code>&lt;smoser</code>&gt; and i do agree dropping pretty table is nice</p> -<p>17:05 <code>&lt;ajorg</code>&gt; winning</p> -<p>17:06 <code>&lt;blackboxsw</code>&gt; smoser: yeah I was wondering how we generally expect people/machines to parse cloud-init-output.log. Right now it's kindof hard to do machine parsing of cloud-init-output.log.</p> -<p>17:07 <code>&lt;smoser</code>&gt; blackboxsw, yeah. cloud-init-output.log is not intended to be machine friendly.</p> -<p>17:07 <code>&lt;blackboxsw</code>&gt; do we know already of non-human consumers of the formatting in cloud-init.output.log?</p> -<p>17:07 <code>&lt;smoser</code>&gt; but the console actually has value in having machien friendly things on it.</p> -<p>17:08 <code>&lt;smoser</code>&gt; my feeling is if you have access to /var/log/cloud-init.log, then you could very easily have written whatever you wanted to another file that was purely machine friendly.</p> -<p>17:08 <code>&lt;blackboxsw</code>&gt; was wondering where we would intend to dump machine-friendly json</p> -<p>17:08 <code>&lt;blackboxsw</code>&gt; yeah</p> -<p>17:08 <code>&lt;smoser</code>&gt; but the console (/dev/ttyS0) boot log is different</p> -<p>17:08 <code>&lt;smoser</code>&gt; in that it can give you a couple things you'd not find easy access to</p> -<p>17:09 <code>&lt;smoser</code>&gt; a.) ssh public keys for the system (providing out of band communication of this data)</p> -<p>17:09 <code>&lt;smoser</code>&gt; b.) network configuration info: providn useful bits of data on how you might get to this system</p> -<p>17:10 <code>&lt;smoser</code>&gt; systemd makes it "fun" to get that data to the console in a safe way</p> -<p>17:12 <code>&lt;ajorg</code>&gt; ugh yes. systemd like to stomp all over your consoles.</p> -<p>17:19 <code>&lt;blackboxsw</code>&gt; ok so did we want to iterate on simpletable to dump json, or just look for cloud-init to write supplementary json files under /run/cloud-init</p> -<p>17:20 <code>&lt;blackboxsw</code>&gt; .. after we land ajorg's branch</p> -<p>17:21 <code>&lt;ajorg</code>&gt; I think it's a good idea to dump json fragments to console for some things, but I suspect smoser will still not want to break anyone who might be using the tables, so probably best to land my branch as-is</p> -<p>17:23 <code>&lt;smoser</code>&gt; yeah, i agree with ajorg. for now, we can just take a replacement that drops prettytable</p> -<p>17:23 <code>&lt;smoser</code>&gt; there are improvments to be done there, but this is a simple win</p> -<p>17:29 <code>&lt;smoser</code>&gt; we'll go ahead and end meeting here.</p> -<p>17:29 <code>&lt;smoser</code>&gt; i'll still be around. thanks all!</p> -<p>17:29 <code>&lt;smoser</code>&gt; #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2017-09-18T16:04:00+00:002017-09-18T16:04:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2017-09-18:/status-2017-09-18.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 18 Sep at 16:04 &mdash; 16:27 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-09-18-16.04.log.html">http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-09-18-16.04.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<ul> -<li><strong>LINK</strong>: <a href="https://public.etherpad-mozilla.org/p/cloud-init-meeting">https://public.etherpad-mozilla.org/p/cloud-init-meeting</a> </li> -<li><strong>LINK</strong>: <a href="https://lists.launchpad.net/cloud-init/msg00100.html">https://lists.launchpad.net/cloud-init/msg00100.html</a> </li> -</ul> -<h3>Release Preparation</h3> -<p>The discussion …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 18 Sep at 16:04 &mdash; 16:27 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-09-18-16.04.log.html">http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-09-18-16.04.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<ul> -<li><strong>LINK</strong>: <a href="https://public.etherpad-mozilla.org/p/cloud-init-meeting">https://public.etherpad-mozilla.org/p/cloud-init-meeting</a> </li> -<li><strong>LINK</strong>: <a href="https://lists.launchpad.net/cloud-init/msg00100.html">https://lists.launchpad.net/cloud-init/msg00100.html</a> </li> -</ul> -<h3>Release Preparation</h3> -<p>The discussion about "Release Preparation" started at 16:08.</p> -<ul> -<li>'''Release Preparation''' (16:08)</li> -<li> -<ul> -<li><strong>LINK</strong>: <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a> </li> -</ul> -</li> -</ul> -<h3>Open Discussion</h3> -<p>The discussion about "Open Discussion" started at 16:14.</p> -<ul> -<li> -<ul> -<li><strong>LINK</strong>: <a href="https://launchpad.net/bugs/1717598">https://launchpad.net/bugs/1717598</a> </li> -</ul> -</li> -</ul> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>smoser (41)</li> -<li>blackboxsw (8)</li> -<li>ubot5 (4)</li> -<li>ajorg (4)</li> -<li>robjo (4)</li> -<li>meetingology (3)</li> -<li>dpb1 (3)</li> -<li>rharper (1)</li> -</ul> -<h2>Full Log</h2> -<p>16:04 <code>&lt;smoser</code>&gt; #startmeeting cloud-init status meeting</p> -<p>16:04 <code>&lt;meetingology</code>&gt; Meeting started Mon Sep 18 16:04:28 2017 UTC. The chair is smoser. Information about MeetBot at <a href="http://wiki.ubuntu.com/meetingology.">http://wiki.ubuntu.com/meetingology.</a></p> -<p>16:04 <code>&lt;meetingology</code>&gt; </p> -<p>16:04 <code>&lt;meetingology</code>&gt; Available commands: action commands idea info link nick</p> -<p>16:05 <code>&lt;blackboxsw</code>&gt; hiya o/</p> -<p>16:05 <code>&lt;rharper</code>&gt; o/</p> -<p>16:05 <code>&lt;smoser</code>&gt; #link <a href="https://public.etherpad-mozilla.org/p/cloud-init-meeting">https://public.etherpad-mozilla.org/p/cloud-init-meeting</a></p> -<p>16:05 <code>&lt;dpb1</code>&gt; hello</p> -<p>16:05 <code>&lt;smoser</code>&gt; so that contains a agenda that we'd been following</p> -<p>16:06 <code>&lt;smoser</code>&gt; #link <a href="https://lists.launchpad.net/cloud-init/msg00100.html">https://lists.launchpad.net/cloud-init/msg00100.html</a></p> -<p>16:07 <code>&lt;smoser</code>&gt; sorry for slow going here.</p> -<p>16:08 <code>&lt;smoser</code>&gt; shoot</p> -<p>16:08 <code>&lt;smoser</code>&gt; #topic Release Preparation</p> -<p>16:08 <code>&lt;smoser</code>&gt; #subtopic Release Preparation</p> -<p>16:08 <code>&lt;smoser</code>&gt; hm..</p> -<p>16:09 <code>&lt;smoser</code>&gt; anyway</p> -<p>16:09 <code>&lt;smoser</code>&gt; <a href="https://lists.launchpad.net/cloud-init/msg00100.html">https://lists.launchpad.net/cloud-init/msg00100.html</a></p> -<p>16:09 <code>&lt;smoser</code>&gt; that is the primariy point of this meeting for today.</p> -<p>16:09 <code>&lt;smoser</code>&gt; The goal is to make a release named 17.1 on Thursday of this week.</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; strange</p> -<p>16:09 <code>&lt;smoser</code>&gt; We have landed several branches in the last few days, and have 2 more to land at least.</p> -<p>16:10 <code>&lt;smoser</code>&gt; from <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a></p> -<p>16:10 <code>&lt;dpb1</code>&gt; meetingology │ Available commands: action commands idea info link nick</p> -<p>16:10 <code>&lt;dpb1</code>&gt; something to look into. :)</p> -<p>16:10 <code>&lt;blackboxsw</code>&gt; #link <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a></p> -<p>16:10 <code>&lt;smoser</code>&gt; the two we consider needs to be integrated are</p> -<p>16:10 <code>&lt;smoser</code>&gt; <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/330875">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/330875</a></p> -<p>16:10 <code>&lt;smoser</code>&gt; <a href="https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/330880">https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/330880</a></p> -<p>16:11 <code>&lt;smoser</code>&gt; and Chad's (the first) is the one we're looking at now.</p> -<p>16:11 <code>&lt;smoser</code>&gt; or that is the one that is non-trivial</p> -<p>16:11 <code>&lt;smoser</code>&gt; does anyone here wnat to raise other bugs or MP that they believe should be pulled ?</p> -<p>16:12 <code>&lt;smoser</code>&gt; ...</p> -<p>16:12 <code>&lt;smoser</code>&gt; ajorg, i think its best to hold off on some of yours until after release.</p> -<p>16:13 <code>&lt;smoser</code>&gt; anyone have anything else ?</p> -<p>16:13 <code>&lt;blackboxsw</code>&gt; msaika (vmware) pinged on a branch a couple days ago. but I think there is a little of discussion/re-work that's needed there before we land</p> -<p>16:13 <code>&lt;ajorg</code>&gt; smoser: I assume you mean the instance identity one, in which case I agree.</p> -<p>16:13 <code>&lt;ajorg</code>&gt; (in either case I'd agree)</p> -<p>16:13 <code>&lt;smoser</code>&gt; and simpletable</p> -<p>16:13 <code>&lt;smoser</code>&gt; yeah</p> -<p>16:14 <code>&lt;smoser</code>&gt; ok. so that is where we are. we are still targettin a release on Thursday.</p> -<p>16:14 <code>&lt;smoser</code>&gt; other than that, i thinkw e move on to open discussion or office hours</p> -<p>16:14 <code>&lt;smoser</code>&gt; #topic Open Discussion</p> -<p>16:14 <code>&lt;smoser</code>&gt; anyone have anything for this ?</p> -<p>16:14 <code>&lt;robjo</code>&gt; Customer has run into an issue where we run out of threads during the user script phase, should generally set TasksMax in the service file, i.e. is that of interest upstream?</p> -<p>16:15 <code>&lt;robjo</code>&gt; we are still testing, but that appears to be the solution for this particular problem</p> -<p>16:15 <code>&lt;smoser</code>&gt; robjo, i dont have an immediate objection to that idea.</p> -<p>16:16 <code>&lt;smoser</code>&gt; could you open a bug ?</p> -<p>16:16 <code>&lt;robjo</code>&gt; sure</p> -<p>16:17 <code>&lt;smoser</code>&gt; i dont think that we'd want to pull that change in right now, but it otherwise seems reasonable at frist b lush.</p> -<p>16:18 <code>&lt;smoser</code>&gt; anything else ?</p> -<p>16:18 <code>&lt;robjo</code>&gt; Agreed, do't think this is sufficiently urgent for Thursday's release, it can wait until the next one</p> -<p>16:19 <code>&lt;ajorg</code>&gt; were there other bugs that we should consider high enough prio to deserve landing a fix in the release?</p> -<p>16:20 <code>&lt;smoser</code>&gt; ajorg, the only 2 that i'm aware of are linked in those mp. i can dig the numbers</p> -<p>16:21 <code>&lt;smoser</code>&gt; * bug 1717598</p> -<p>16:21 <code>&lt;ubot5</code>&gt; bug 1717598 in cloud-init (Ubuntu) "Traceback when passing user-data on GCE" [High,In progress] <a href="https://launchpad.net/bugs/1717598">https://launchpad.net/bugs/1717598</a></p> -<p>16:21 <code>&lt;smoser</code>&gt; * bug 1717627</p> -<p>16:21 <code>&lt;ubot5</code>&gt; bug 1717627 in cloud-init "permission denied when executing dhclient in Ec2 datasource" [High,In progress] <a href="https://launchpad.net/bugs/1717627">https://launchpad.net/bugs/1717627</a></p> -<p>16:21 <code>&lt;ajorg</code>&gt; ok</p> -<p>16:22 <code>&lt;smoser</code>&gt; Anything else? other wise i'll call this meeting done and hang around for office hours for the next 30 m inutes at least.</p> -<p>16:22 <code>&lt;smoser</code>&gt; thanks for attending / feedback, robjo and ajorg</p> -<p>16:23 <code>&lt;blackboxsw</code>&gt; #link <a href="https://launchpad.net/bugs/1717598">https://launchpad.net/bugs/1717598</a></p> -<p>16:23 <code>&lt;ubot5</code>&gt; Ubuntu bug 1717598 in cloud-init (Ubuntu) "Traceback when passing user-data on GCE" [High,In progress]</p> -<p>16:24 <code>&lt;blackboxsw</code>&gt; #link<a href="https://launchpad.net/bugs/1717627">https://launchpad.net/bugs/1717627</a></p> -<p>16:24 <code>&lt;ubot5</code>&gt; Ubuntu bug 1717627 in cloud-init "permission denied when executing dhclient in Ec2 datasource" [High,In progress]</p> -<p>16:24 <code>&lt;blackboxsw</code>&gt; just in case</p> -<p>16:24 <code>&lt;blackboxsw</code>&gt; duno whats up with the bot.... again</p> -<p>16:27 <code>&lt;smoser</code>&gt; ok. well, lets move on</p> -<p>16:27 <code>&lt;smoser</code>&gt; #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init github.io details2017-09-05T16:30:00-04:002017-09-05T16:30:00-04:00chad.smith@canonical.comtag:cloud-init.github.io,2017-09-05:/cloud-init-githubio-details.html<h2>Cloud-init project info page</h2> -<p>Cloud-init dev team created a github.io project page based on pelican and Flex theme to host cloud-init status meeting notes.</p><h2>Cloud-init project info page</h2> -<p>Cloud-init dev team created a github.io project page based on pelican and Flex theme to host cloud-init status meeting notes.</p>Cloud-init bi-weekly status2017-09-05T16:30:00-04:002017-09-05T16:30:00-04:00chad.smith@canonical.comtag:cloud-init.github.io,2017-09-05:/status-2017-09-05.html<h2>Meeting information</h2> -<p><code>* #cloud-init: cloud-init status meeting, 05 Sep at 16:30 — 16:30 UTC</code></p> -<h2>Meeting summary</h2> -<p><em>LINK:</em> <a href="https://public.etherpad-mozilla.org/p/cloud-init-meeting">https://public.etherpad-mozilla.org/p/cloud-init-meeting</a></p> -<p><code>*</code><strong><code>Recent Changes</code></strong><code>(16:35)</code></p> -<ul> -<li>integration of robjo's opensuse items</li> -<li>summit results posted to mailing list https://lists.launchpad.net/cloud-init/msg00094.html</li> -</ul> -<p><em>LINK:</em> <a href="https://lists.launchpad.net/cloud-init/msg00094.html">https://lists.launchpad.net …</a></p><h2>Meeting information</h2> -<p><code>* #cloud-init: cloud-init status meeting, 05 Sep at 16:30 — 16:30 UTC</code></p> -<h2>Meeting summary</h2> -<p><em>LINK:</em> <a href="https://public.etherpad-mozilla.org/p/cloud-init-meeting">https://public.etherpad-mozilla.org/p/cloud-init-meeting</a></p> -<p><code>*</code><strong><code>Recent Changes</code></strong><code>(16:35)</code></p> -<ul> -<li>integration of robjo's opensuse items</li> -<li>summit results posted to mailing list https://lists.launchpad.net/cloud-init/msg00094.html</li> -</ul> -<p><em>LINK:</em> <a href="https://lists.launchpad.net/cloud-init/msg00094.html">https://lists.launchpad.net/cloud-init/msg00094.html</a></p> -<p><code>*</code><strong><code>In Progress Development</code></strong><code>(16:38)</code></p> -<ul> -<li><em>LINK:</em> <a href="https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin">https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin</a></li> -<li><em>LINK:</em> <a href="https://bugs.launchpad.net/cloud-init">https://bugs.launchpad.net/cloud-init</a></li> -<li>Opensuse builds: <em>LINK:</em> <a href="https://build.opensuse.org/package/show/Cloud:Tools:Next/cloud-init">https://build.opensuse.org/package/show/Cloud:Tools:Next/cloud-init</a></li> -<li>Ongoing SRU for ubuntu: <em>LINK:</em> <a href="https://people.canonical.com/~ubuntu-archive/pending-sru.html">https://people.canonical.com/~ubuntu-archive/pending-sru.html</a></li> -<li>Meetingology to join for next meeting</li> -</ul> -<p><code>*</code><strong><code>Open Discussion- cloud-init versioning</code></strong><code>(16:41)</code></p> -<ul> -<li>Will target a new versioned release Sept 21st</li> -<li>cloud-init will have major.minor versioning represented by &lt;2-digit-year&gt;.<minor>. The <minor> version will be 1-based and increment with each quarterly release.</li> -<li><em>ACTION</em> smoser to write to mailing list with that as the plan and suggesting the target release date of 17.1 on the Sept 21.</li> -<li>cloud-init releases will target quarterly cycles</li> -</ul> -<p><code>*</code><strong><code>Office Hours</code></strong><code>(15:15)</code></p> -<h2>Vote results</h2> -<h2>Done items</h2> -<p><code>* (none)</code></p> -<h2>People present (lines said)</h2> -<p><code>* blackboxsw</code> -<code>* smoser</code> -<code>* powersj</code> -<code>* rharper</code> -<code>* dpb1</code></p> -<h2>Full Log</h2> -<p><em>LINK:</em> <a href="https://irclogs.ubuntu.com/2017/09/05/%23cloud-init.html#t16:32">https://irclogs.ubuntu.com/2017/09/05/%23cloud-init.html#t16:32</a></p> \ No newline at end of file diff --git a/feeds/background.atom.xml b/feeds/background.atom.xml deleted file mode 100644 index f675b49..0000000 --- a/feeds/background.atom.xml +++ /dev/null @@ -1,4 +0,0 @@ - -Cloud-init Info - Backgroundhttps://cloud-init.github.io/2017-09-05T16:30:00-04:00Cloud-init github.io details2017-09-05T16:30:00-04:002017-09-05T16:30:00-04:00chad.smith@canonical.comtag:cloud-init.github.io,2017-09-05:/cloud-init-githubio-details.html<h2>Cloud-init project info page</h2> -<p>Cloud-init dev team created a github.io project page based on pelican and Flex theme to host cloud-init status meeting notes.</p><h2>Cloud-init project info page</h2> -<p>Cloud-init dev team created a github.io project page based on pelican and Flex theme to host cloud-init status meeting notes.</p> \ No newline at end of file diff --git a/feeds/status-meeting-minutes.atom.xml b/feeds/status-meeting-minutes.atom.xml deleted file mode 100644 index 907ab66..0000000 --- a/feeds/status-meeting-minutes.atom.xml +++ /dev/null @@ -1,9613 +0,0 @@ - -Cloud-init Info - status-meeting-minuteshttps://cloud-init.github.io/2021-06-29T16:23:00+00:00Cloud-init bi-weekly status2021-06-29T16:23:00+00:002021-06-29T16:23:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2021-06-29:/status-2021-06-29.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init bi-weekly office-hours meeting, started by blackboxsw, 29 Jun at 16:23 &mdash; 17:35 UTC.</li> -<li>Full logs at <a href="https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-06-29-16.23.log.html">https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-06-29-16.23.log.html</a></li> -</ul> -<h2>Meeting summary</h2> -<ul> -<li><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/t/cloud-init-status-06-29-2021/22981">https://discourse.ubuntu.com/t/cloud-init-status-06-29-2021/22981</a> (blackboxsw, 16:27)</li> -</ul> -<h2>People present (lines …</h2><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init bi-weekly office-hours meeting, started by blackboxsw, 29 Jun at 16:23 &mdash; 17:35 UTC.</li> -<li>Full logs at <a href="https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-06-29-16.23.log.html">https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-06-29-16.23.log.html</a></li> -</ul> -<h2>Meeting summary</h2> -<ul> -<li><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/t/cloud-init-status-06-29-2021/22981">https://discourse.ubuntu.com/t/cloud-init-status-06-29-2021/22981</a> (blackboxsw, 16:27)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (9)</li> -<li>meetingology (2)</li> -<li>ubottu (1)</li> -</ul> -<h2>Full log</h2> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #startmeeting cloud-init bi-weekly office-hours</p> -<p>16:23 <code>&lt;meetingology&gt;</code> Meeting started at 16:23:41 UTC. The chair is blackboxsw. Information about MeetBot at <a href="https://wiki.ubuntu.com/meetingology">https://wiki.ubuntu.com/meetingology</a></p> -<p>16:23 <code>&lt;meetingology&gt;</code> Available commands: action, commands, idea, info, link, nick</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> Hi cloud-init devs, Our biweekly office hours meeting has begun. We keep this channel open during the designated time on the channel #topic for drop in questions, feature or bug discussions and prodding committers folks for reviews.</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> All questions welcome and we'll have a couple of upstream committers with eyes on the channel to field any discussions brought up as best we can.</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> Just prior to this meeting, someone will post recent happenings in cloud-init upstream which may be of value to the community.</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> #link <a href="https://discourse.ubuntu.com/t/cloud-init-status-06-29-2021/22981">https://discourse.ubuntu.com/t/cloud-init-status-06-29-2021/22981</a></p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> As far as upstream is concerned, the only schedule detail of note is we are looking to create an official 21.3 upstream release August 28th. Before that time we hope to have some hot plug network device handling functional in cloud-init.</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> my plan today is to get falcojr a review on his foundational hotplug support work at <a href="https://github.com/canonical/cloud-init/pull/919">https://github.com/canonical/cloud-init/pull/919</a> which should allow cloud-init to support actively interacting with network config utilities to actively enable individual interfaces on device discovery after the network renderers have finished initial network bringup.</p> -<p>16:34 <code>&lt;ubottu&gt;</code> Pull 919 in canonical/cloud-init "Add new network configurers to bring up interfaces (SC-85)" [Open]</p> -<p>17:35 <code>&lt;blackboxsw&gt;</code> ok, that wraps things up for "office hours" for today. Thanks for checking in.</p> -<p>17:35 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.4.0 (<a href="https://wiki.ubuntu.com/meetingology">https://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2021-06-15T17:17:00+00:002021-06-15T17:17:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2021-06-15:/status-2021-06-15.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init bi-weekly office-hours meeting, started by blackboxsw, 15 Jun at 17:17 &mdash; 19:47 UTC.</li> -<li>Full logs at <a href="https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-06-15-17.17.log.html">https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-06-15-17.17.log.html</a></li> -</ul> -<h2>Meeting summary</h2> -<ul> -<li><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/t/cloud-init-status-06-15-2021/22730">https://discourse.ubuntu.com/t/cloud-init-status-06-15-2021/22730</a> (blackboxsw, 17:25)</li> -<li><strong>LINK</strong>: <a href="https://docs.github.com/en/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch#updating-a-local-clone-after-a-branch-name-changes">https://docs …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init bi-weekly office-hours meeting, started by blackboxsw, 15 Jun at 17:17 &mdash; 19:47 UTC.</li> -<li>Full logs at <a href="https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-06-15-17.17.log.html">https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-06-15-17.17.log.html</a></li> -</ul> -<h2>Meeting summary</h2> -<ul> -<li><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/t/cloud-init-status-06-15-2021/22730">https://discourse.ubuntu.com/t/cloud-init-status-06-15-2021/22730</a> (blackboxsw, 17:25)</li> -<li><strong>LINK</strong>: <a href="https://docs.github.com/en/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch#updating-a-local-clone-after-a-branch-name-changes">https://docs.github.com/en/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch#updating-a-local-clone-after-a-branch-name-changes</a> (blackboxsw, 17:37)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (16)</li> -<li>meetingology (3)</li> -<li>falcojr (2)</li> -</ul> -<h2>Full log</h2> -<p>17:17 <code>&lt;blackboxsw&gt;</code> #startmeeting cloud-init bi-weekly office-hours</p> -<p>17:17 <code>&lt;meetingology&gt;</code> Meeting started at 17:17:44 UTC. The chair is blackboxsw. Information about MeetBot at <a href="https://wiki.ubuntu.com/meetingology">https://wiki.ubuntu.com/meetingology</a></p> -<p>17:17 <code>&lt;meetingology&gt;</code> Available commands: action, commands, idea, info, link, nick</p> -<p>17:20 <code>&lt;blackboxsw&gt;</code> community-notice: Hi cloud-initers, welcome to another office hours meeting. cloud-init committers will be around for the next hour to field any discussions. answer questions or put some eyes on PR reviews or bugs that spark your interest.</p> -<p>17:21 <code>&lt;blackboxsw&gt;</code> We host this meeting to unblock, or unstick anybody toying around with cloud-init, as well as to update thecloud-init devs on recent changes in cloud-init upstream</p> -<p>17:21 <code>&lt;blackboxsw&gt;</code> #chair falcojr</p> -<p>17:21 <code>&lt;meetingology&gt;</code> Current chairs: blackboxsw, falcojr</p> -<p>17:25 <code>&lt;blackboxsw&gt;</code> We just published a little discourse post describing that cloud-init upstream version 21.2 has now cleared SRU validation for Ubuntu Bionic(16.04) Focal (20.04) Groovy (20.10) and Hirsute (21.04) <a href="https://discourse.ubuntu.com/t/cloud-init-status-06-15-2021/22730">https://discourse.ubuntu.com/t/cloud-init-status-06-15-2021/22730</a></p> -<p>17:25 <code>&lt;blackboxsw&gt;</code> #link <a href="https://discourse.ubuntu.com/t/cloud-init-status-06-15-2021/22730">https://discourse.ubuntu.com/t/cloud-init-status-06-15-2021/22730</a></p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> in that SRU, were some ssh_key handling improvement, Azure SSH key processing, Azure userdata updated ingested from IMDS and new support for Vultr cloud platform.</p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> Thanks all for those contributions!</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> one other interesting thing to note: 4 days ago I was banned from FreeNode. falcojr did this happen to you too? "Connection closed unexpectedly: You are banned from this server- [#1480] Contact support@freenode.net (2021/6/11 05.18):"</p> -<p>17:31 <code>&lt;falcojr&gt;</code> blackboxsw: no, that's weird. I know they completely reset everything over there though.</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> hrm maybe they tracked irc nicks that were advertizing moving to Libera.chat is the only thing I can think. will check it out</p> -<p>17:33 <code>&lt;falcojr&gt;</code> at this point probably just best to cut ties completely</p> -<p>17:35 <code>&lt;blackboxsw&gt;</code> yes agreed</p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> community-notice: reminder rename upstream/master -&gt;` upstream/main in 2 days. All active PRs will automatically be retargetted. For your local clones for cloud-init it should mean only the following:</p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> #link <a href="https://docs.github.com/en/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch#updating-a-local-clone-after-a-branch-name-changes">https://docs.github.com/en/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch#updating-a-local-clone-after-a-branch-name-changes</a></p> -<p>17:40 <code>&lt;blackboxsw&gt;</code> an email will be sent out to cloud-init@lists.launchpad.net</p> -<p>17:40 <code>&lt;blackboxsw&gt;</code> with detailed instructions.</p> -<p>19:47 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.4.0 (<a href="https://wiki.ubuntu.com/meetingology">https://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2021-06-01T17:25:00+00:002021-06-01T17:25:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2021-06-01:/status-2021-06-01.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init bi-weekly office hours (~30 mins) meeting, started by blackboxsw, 01 Jun at 17:25 &mdash; 19:29 UTC.</li> -<li>Full logs at <a href="https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-06-01-17.25.log.html">https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-06-01-17.25.log.html</a></li> -</ul> -<h2>Meeting summary</h2> -<ul> -<li><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/t/cloud-init-status-06-01-2021/22553">https://discourse.ubuntu.com/t/cloud-init-status-06-01-2021/22553</a> (blackboxsw, 17:29 …</li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init bi-weekly office hours (~30 mins) meeting, started by blackboxsw, 01 Jun at 17:25 &mdash; 19:29 UTC.</li> -<li>Full logs at <a href="https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-06-01-17.25.log.html">https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-06-01-17.25.log.html</a></li> -</ul> -<h2>Meeting summary</h2> -<ul> -<li><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/t/cloud-init-status-06-01-2021/22553">https://discourse.ubuntu.com/t/cloud-init-status-06-01-2021/22553</a> (blackboxsw, 17:29)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (9)</li> -<li>meetingology (2)</li> -</ul> -<h2>Full log</h2> -<p>17:25 <code>&lt;blackboxsw&gt;</code> #startmeeting cloud-init bi-weekly office hours (~30 mins)</p> -<p>17:25 <code>&lt;meetingology&gt;</code> Meeting started at 17:25:49 UTC. The chair is blackboxsw. Information about MeetBot at <a href="https://wiki.ubuntu.com/meetingology">https://wiki.ubuntu.com/meetingology</a></p> -<p>17:25 <code>&lt;meetingology&gt;</code> Available commands: action, commands, idea, info, link, nick</p> -<p>17:28 <code>&lt;blackboxsw&gt;</code> community-notice: office hours meeting starts now. We host this meeting time every two weeks for any drop in discussions for anything cloud-init related. Bring your bugs, feature discussions, gripes and questions and we'll have a couple sets of upstream cloud-init eyes on this channel to field those discussions.</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> highlights of recent upstream commits and project changes are at the url below:</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> #link <a href="https://discourse.ubuntu.com/t/cloud-init-status-06-01-2021/22553">https://discourse.ubuntu.com/t/cloud-init-status-06-01-2021/22553</a></p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> Of course, if you managed to join us over here you are already aware of the Freenode IRC politcal climate pushing us to migrate to a more open/friendly IRC network w/ libera.chat. paride is in the process of registering this channel for the cloud-init project so that we can add channel OPS to the upstream cloud-init committers smoser, rharper, Odd_Bloke, falcojr.</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> Once we have channel op status, we plan on adding upcoming dates, milestones and info to the IRC channel title.</p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> Also, as upstream, we want to rename the default development branch from 'master' to 'main' to provide more inclusive naming and drop antiquated and exclusive naming conventions. An email will be sent to the cloud-init mailing list explaining the perceived impact of such a default branch rename (which should be minimal).</p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> If there are any concerns about this rename impacting business, please raise concerns here, on the discourse post above or on the mailinglist</p> -<p>19:29 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.4.0 (<a href="https://wiki.ubuntu.com/meetingology">https://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2021-05-18T16:32:00+00:002021-05-18T16:32:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2021-05-18:/status-2021-05-18.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init bi-weekly office-hours meeting, started by blackboxsw, 18 May at 16:32 &mdash; 17:26 UTC.</li> -<li>Full logs at <a href="https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-05-18-16.32.log.html">https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-05-18-16.32.log.html</a></li> -</ul> -<h2>Meeting summary</h2> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (12)</li> -<li>paride (4)</li> -<li>smoser (4)</li> -<li>meetingology (2)</li> -<li>ubot5 (1 …</li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init bi-weekly office-hours meeting, started by blackboxsw, 18 May at 16:32 &mdash; 17:26 UTC.</li> -<li>Full logs at <a href="https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-05-18-16.32.log.html">https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-05-18-16.32.log.html</a></li> -</ul> -<h2>Meeting summary</h2> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (12)</li> -<li>paride (4)</li> -<li>smoser (4)</li> -<li>meetingology (2)</li> -<li>ubot5 (1)</li> -<li>falcojr (1)</li> -</ul> -<h2>Full log</h2> -<p>16:32 <code>&lt;blackboxsw&gt;</code> #startmeeting cloud-init bi-weekly office-hours</p> -<p>16:32 <code>&lt;meetingology&gt;</code> Meeting started at 16:32:21 UTC. The chair is blackboxsw. Information about MeetBot at <a href="https://wiki.ubuntu.com/meetingology">https://wiki.ubuntu.com/meetingology</a></p> -<p>16:32 <code>&lt;meetingology&gt;</code> Available commands: action, commands, idea, info, link, nick</p> -<p>16:32 <code>&lt;paride&gt;</code> smoser, thanks, merged!</p> -<p>16:33 <code>&lt;paride&gt;</code> but as it's not in the server packageset I'll need sponsorship for the upload...</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> community-notice: Let's get back to a more regularly scheduled cloud-init office hours. Every two weeks, feel free to watch the channel topic for the next scheduled time. We'll ensure to have a couple of sets of eyes on this IRC channel.</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> Next office-hours meeting is set for June 1, 17:15 UTC. It is worth us having this recurring meeting to give anyone a chance to drive-by #cloud-init if they have questions, discussions, bugs or PRs that need attention.</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> Prior to the office hours, we will continue to generate a post with the latest commits to land in cloud-init:master as well as any notable features in progress <a href="https://discourse.ubuntu.com/t/cloud-init-status-05-18-2021/22349">https://discourse.ubuntu.com/t/cloud-init-status-05-18-2021/22349</a></p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> From upstream standpoint, we were able to cut the time-based release 21.2 on May 6th. And for Ubuntu, we have queued the StableReleaseUpdate (SRU) for 21.2 into Bionic, Focal and Hirsute for which falcojr and Odd_Bloke have been going through verification.</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> Think we need to update the topic for the 21.2 upstream release too.</p> -<p>16:42 <code>&lt;smoser&gt;</code> paride: <a href="https://paste.ubuntu.com/p/y3N7wjCG3n/">https://paste.ubuntu.com/p/y3N7wjCG3n/</a></p> -<p>16:44 <code>&lt;smoser&gt;</code> fudge.</p> -<p>16:44 <code>&lt;smoser&gt;</code> but i just noticed your changelog didn't have LP: #1908452</p> -<p>16:44 <code>&lt;ubot5&gt;</code> Launchpad bug 1908452 in MAAS "MAAS stops working and deployment fails after <code>Loading ephemeral</code> step" [High,In progress] <a href="https://launchpad.net/bugs/1908452">https://launchpad.net/bugs/1908452</a></p> -<p>16:45 <code>&lt;smoser&gt;</code> because the commit message said 'Fixes LP:1908452' rather than just 'LP: #1908452'</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> 'Fixes LP:1908452' almost github; almost LP :/</p> -<p>16:48 <code>&lt;paride&gt;</code> smoser, argh :/ will update the bug status manually</p> -<p>16:48 <code>&lt;paride&gt;</code> thanks for the upload</p> -<p>16:50 * blackboxsw falcojr: do we have a trello board for the SRU 21.2 created?</p> -<p>16:50 <code>&lt;falcojr&gt;</code> yep, <a href="https://trello.com/b/tBP3Jrwp/sru-cloud-init-212">https://trello.com/b/tBP3Jrwp/sru-cloud-init-212</a> (just made it public)</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> Thanks a lot</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> Great, I was originally looking at the older trello board for the 21.1. Ok, so I'll grab Softlayer testing as you mentioned at standup today. If you want me to run through other clouds just let me know or hit me up for reviews.</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> Alright, I think that about wraps today's office hours. Next round in two weeks. Thanks for tuning in.</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.4.0 (<a href="https://wiki.ubuntu.com/meetingology">https://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2021-04-06T16:20:00+00:002021-04-06T16:20:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2021-04-06:/status-2021-04-06.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init bi-weekly office-hours meeting, started by blackboxsw, 06 Apr at 16:20 &mdash; 17:37 UTC.</li> -<li>Full logs at <a href="https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-04-06-16.20.log.html">https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-04-06-16.20.log.html</a></li> -</ul> -<h2>Meeting summary</h2> -<h2>People present (lines said)</h2> -<ul> -<li>hamalq (7)</li> -<li>blackboxsw (6)</li> -<li>falcojr (3)</li> -<li>meetingology (2)</li> -<li>Odd_Bloke (1 …</li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init bi-weekly office-hours meeting, started by blackboxsw, 06 Apr at 16:20 &mdash; 17:37 UTC.</li> -<li>Full logs at <a href="https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-04-06-16.20.log.html">https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-04-06-16.20.log.html</a></li> -</ul> -<h2>Meeting summary</h2> -<h2>People present (lines said)</h2> -<ul> -<li>hamalq (7)</li> -<li>blackboxsw (6)</li> -<li>falcojr (3)</li> -<li>meetingology (2)</li> -<li>Odd_Bloke (1)</li> -</ul> -<h2>Full log</h2> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #startmeeting cloud-init bi-weekly office-hours</p> -<p>16:20 <code>&lt;meetingology&gt;</code> Meeting started at 16:20:26 UTC. The chair is blackboxsw. Information about MeetBot at <a href="https://wiki.ubuntu.com/meetingology">https://wiki.ubuntu.com/meetingology</a></p> -<p>16:20 <code>&lt;meetingology&gt;</code> Available commands: action, commands, idea, info, link, nick</p> -<p>16:21 <code>&lt;falcojr&gt;</code> I think by default it should use the current defaults of what's chosen...e.g., true for rhel and false for others</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> Hi cloud-init! This marks another episode of cloud-init community office hours. This time is an opportunity to discuss any cloud-init questions, bugs or topics with cloud-init upstream developers. We try to ensure a couple of devs have eyes on this channel to field any questions/concerns folks may have.</p> -<p>16:24 <code>&lt;Odd_Bloke&gt;</code> o/</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> Recent happenings in cloud-init space are generally spent on the current SRU validation with Odd_Bloke and falcojr. It looks like we've cleared the last manual validation with that SRU and we will be waiting on a significant automated set of tests to pass before making this release public. <a href="https://discourse.ubuntu.com/t/cloud-init-status-04-06-2021/21691">https://discourse.ubuntu.com/t/cloud-init-status-04-06-2021/21691</a></p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> thanks falcojr and Odd_Bloke for reviews on <a href="https://github.com/canonical/cloud-init/pull/859">https://github.com/canonical/cloud-init/pull/859</a></p> -<p>16:36 <code>&lt;hamalq&gt;</code> i already did the change as the comment</p> -<p>16:37 <code>&lt;hamalq&gt;</code> i dont think i can change cloudinit/distros/<strong>init</strong>.py select_hostname though</p> -<p>16:38 <code>&lt;falcojr&gt;</code> we can change it...we just need to make sure the functionality stays the same if the option isn't specified</p> -<p>16:39 <code>&lt;hamalq&gt;</code> thats the point since the default for that option is true</p> -<p>16:40 <code>&lt;hamalq&gt;</code> unless we make the default for it false for other distros</p> -<p>16:41 <code>&lt;falcojr&gt;</code> yes, we would need to take it into account for all distros, and it would default to false for most</p> -<p>16:42 <code>&lt;hamalq&gt;</code> +1</p> -<p>16:47 <code>&lt;hamalq&gt;</code> i changed that now for distros and rhel</p> -<p>17:15 <code>&lt;hamalq&gt;</code> i think i got the changes required <a href="https://github.com/canonical/cloud-init/pull/859">https://github.com/canonical/cloud-init/pull/859</a></p> -<p>17:36 <code>&lt;blackboxsw&gt;</code> thanks folks for attending the office hours. See you all in two weeks. Same time</p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.4.0 (<a href="https://wiki.ubuntu.com/meetingology">https://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2021-03-23T17:22:00+00:002021-03-23T17:22:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2021-03-23:/status-2021-03-23.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init bi-weekly office-hours meeting, started by Odd_Bloke, 23 Mar at 17:22 &mdash; 18:24 UTC.</li> -<li>Full logs at <a href="https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-03-23-17.22.log.html">https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-03-23-17.22.log.html</a></li> -</ul> -<h2>Meeting summary</h2> -<ul> -<li><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/t/cloud-init-status-03-23-2021/21490">https://discourse.ubuntu.com/t/cloud-init-status-03-23-2021/21490</a> (Odd_Bloke, 17:23)</li> -<li><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/t/cloud-init-status-03-23-2021/21490">https://discourse …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init bi-weekly office-hours meeting, started by Odd_Bloke, 23 Mar at 17:22 &mdash; 18:24 UTC.</li> -<li>Full logs at <a href="https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-03-23-17.22.log.html">https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-03-23-17.22.log.html</a></li> -</ul> -<h2>Meeting summary</h2> -<ul> -<li><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/t/cloud-init-status-03-23-2021/21490">https://discourse.ubuntu.com/t/cloud-init-status-03-23-2021/21490</a> (Odd_Bloke, 17:23)</li> -<li><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/t/cloud-init-status-03-23-2021/21490">https://discourse.ubuntu.com/t/cloud-init-status-03-23-2021/21490</a> (blackboxsw, 17:23)</li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bug/1724414">https://bugs.launchpad.net/cloud-init/+bug/1724414</a> (blackboxsw, 17:25)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (11)</li> -<li>Odd_Bloke (10)</li> -<li>meetingology (3)</li> -<li>ubot5 (1)</li> -<li>falcojr (0)</li> -</ul> -<h2>Full log</h2> -<p>17:22 <code>&lt;Odd_Bloke&gt;</code> #startmeeting cloud-init bi-weekly office-hours</p> -<p>17:22 <code>&lt;meetingology&gt;</code> Meeting started at 17:22:08 UTC. The chair is Odd_Bloke. Information about MeetBot at <a href="https://wiki.ubuntu.com/meetingology">https://wiki.ubuntu.com/meetingology</a></p> -<p>17:22 <code>&lt;meetingology&gt;</code> Available commands: action, commands, idea, info, link, nick</p> -<p>17:22 <code>&lt;Odd_Bloke&gt;</code> #chair blackboxsw falcojr</p> -<p>17:22 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke, blackboxsw, falcojr</p> -<p>17:22 <code>&lt;blackboxsw&gt;</code> \0 woot thanks Odd_Bloke</p> -<p>17:23 <code>&lt;Odd_Bloke&gt;</code> Hey folks, the cloud-init committers will be around for the next while, to answer any questions or have any discussions you're interested in having.</p> -<p>17:23 <code>&lt;Odd_Bloke&gt;</code> blackboxsw posted a status update to Discourse earlier today.</p> -<p>17:23 <code>&lt;blackboxsw&gt;</code> Here's the discourse post for reference on recent cloud-init events</p> -<p>17:23 <code>&lt;Odd_Bloke&gt;</code> #link <a href="https://discourse.ubuntu.com/t/cloud-init-status-03-23-2021/21490">https://discourse.ubuntu.com/t/cloud-init-status-03-23-2021/21490</a></p> -<p>17:23 <code>&lt;blackboxsw&gt;</code> #link <a href="https://discourse.ubuntu.com/t/cloud-init-status-03-23-2021/21490">https://discourse.ubuntu.com/t/cloud-init-status-03-23-2021/21490</a></p> -<p>17:23 <code>&lt;blackboxsw&gt;</code> thanks Odd_Bloke</p> -<p>17:23 <code>&lt;Odd_Bloke&gt;</code> Haha</p> -<p>17:23 <code>&lt;Odd_Bloke&gt;</code> Please read it twice.</p> -<p>17:24 <code>&lt;blackboxsw&gt;</code> and correct any clerical errors</p> -<p>17:25 <code>&lt;blackboxsw&gt;</code> one topic of interested that hamalq brought up yesterday was the "feature" of RedHat and CentOS that automatically prefers fqdn over hostname in #cloud-config per this bug</p> -<p>17:25 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/+bug/1724414">https://bugs.launchpad.net/cloud-init/+bug/1724414</a></p> -<p>17:25 <code>&lt;ubot5&gt;</code> Ubuntu bug 1724414 in cloud-init "rhel distro selects FQDN as hostname" [Low,Won't fix]</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> I mentioned we'd bring it up to reflect our opinion on this behavior today after a discussion</p> -<p>17:28 <code>&lt;blackboxsw&gt;</code> I think the upstream stance on RedHat and CentOS is that this default behavior on RedHat/CentOS has been in play for a long time and changing that default behavior would be asking to cause problems for the majority of users who may rely on this behavior during system launch.</p> -<p>17:28 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: falcojr did we say in this case we'd prefer a new bug which better describes the desired use-case and how current cloud-init doesn't allow for that use-case?</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> that's all the content/discussion I had. I know I needed to get otubo a review today on his resize lvm partition branch <a href="https://github.com/canonical/cloud-init/pull/721">https://github.com/canonical/cloud-init/pull/721</a> as my stale review was blocking that.</p> -<p>17:31 <code>&lt;Odd_Bloke&gt;</code> We've closed out that bug as Won't Fix; we'd like folks who consider themselves affected by that bug to file a new one which describes their specific problem with the current situation: we can then work to support those requirements.</p> -<p>18:24 <code>&lt;Odd_Bloke&gt;</code> OK, sounds like there's not much to chat about; thanks to any lurkers. :)</p> -<p>18:24 <code>&lt;Odd_Bloke&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.4.0 (<a href="https://wiki.ubuntu.com/meetingology">https://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2021-03-09T17:19:00+00:002021-03-09T17:19:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2021-03-09:/status-2021-03-09.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init bi-weekly office-hours meeting, started by blackboxsw, 09 Mar at 17:19 &mdash; 18:38 UTC.</li> -<li>Full logs at <a href="https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-03-09-17.19.log.html">https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-03-09-17.19.log.html</a></li> -</ul> -<h2>Meeting summary</h2> -<ul> -<li><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/t/cloud-init-status-03-09-2021/21309">https://discourse.ubuntu.com/t/cloud-init-status-03-09-2021/21309</a> (blackboxsw, 17:23)</li> -</ul> -<h2>People present (lines …</h2><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init bi-weekly office-hours meeting, started by blackboxsw, 09 Mar at 17:19 &mdash; 18:38 UTC.</li> -<li>Full logs at <a href="https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-03-09-17.19.log.html">https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-03-09-17.19.log.html</a></li> -</ul> -<h2>Meeting summary</h2> -<ul> -<li><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/t/cloud-init-status-03-09-2021/21309">https://discourse.ubuntu.com/t/cloud-init-status-03-09-2021/21309</a> (blackboxsw, 17:23)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (14)</li> -<li>falcojr (8)</li> -<li>beantaxi (7)</li> -<li>meetingology (3)</li> -<li>Odd_Bloke (3)</li> -</ul> -<h2>Full log</h2> -<p>17:19 <code>&lt;blackboxsw&gt;</code> #startmeeting cloud-init bi-weekly office-hours</p> -<p>17:19 <code>&lt;meetingology&gt;</code> Meeting started at 17:19:08 UTC. The chair is blackboxsw. Information about MeetBot at <a href="https://wiki.ubuntu.com/meetingology">https://wiki.ubuntu.com/meetingology</a></p> -<p>17:19 <code>&lt;meetingology&gt;</code> Available commands: action, commands, idea, info, link, nick</p> -<p>17:19 <code>&lt;blackboxsw&gt;</code> #char Odd_Bloke falcojr</p> -<p>17:19 <code>&lt;blackboxsw&gt;</code> #chair Odd_Bloke falcojr</p> -<p>17:19 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke, blackboxsw, falcojr</p> -<p>17:20 <code>&lt;blackboxsw&gt;</code> hi cloud-init, sorry for the confusion on the UTC time that I posted in the topic. I had incorrectly set 15:15 UTC instead of 17:15.</p> -<p>17:20 <code>&lt;blackboxsw&gt;</code> welcome to the bi-weekly cloud-init office hours</p> -<p>17:21 <code>&lt;blackboxsw&gt;</code> This cloud-init status meeting has moved to a more asynchronous posting of high-level happenings in cloud-init to discourse to support timezone differences for all cloud-init developers.</p> -<p>17:23 <code>&lt;blackboxsw&gt;</code> We plan on continuing to host these office hours to provide a means for quick communication, questions and discussions with a couple of upstream developers present to help facilite any questions or discussions of interest to folks.</p> -<p>17:23 <code>&lt;blackboxsw&gt;</code> For reference, here are the high-level "happenings" in cloud-init upstream over the last two weeks.</p> -<p>17:23 <code>&lt;Odd_Bloke&gt;</code> o/</p> -<p>17:23 <code>&lt;blackboxsw&gt;</code> #link <a href="https://discourse.ubuntu.com/t/cloud-init-status-03-09-2021/21309">https://discourse.ubuntu.com/t/cloud-init-status-03-09-2021/21309</a></p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> As of last office-hours I belive upstream had just cut the first 21.1 release in the tip of cloud-init. Canonical will be starting the SRU process this week I believe to publish the 21.1 release (plus a couple of extra fixes which just landed in tip) into Ubuntu Xenial, Bionic, Focal, Groovy and Hirsute.</p> -<p>17:41 <code>&lt;beantaxi&gt;</code> Odd_Bloke: I tried your command and it was helpful. It complained about a missing ssh key, so I shrugged, tried ssh-keygen -t rsa and reran the test, and it passed. I've kicked off a run of all the tests, which I assume will take a bit.</p> -<p>17:55 <code>&lt;Odd_Bloke&gt;</code> beantaxi: Great, thanks for the update! A full run in LXD containers takes ~12mins locally (though I'm probably running on beefier hardware than you're paying EC2 for so YMMV :p).</p> -<p>17:55 <code>&lt;Odd_Bloke&gt;</code> beantaxi: Once you had the output, was it clear that the missing SSH key was the issue?</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> setting the appropriate time for next office hours</p> -<p>17:56 <code>&lt;blackboxsw&gt;</code> setting the appropriate time for next office hours Mar 23 17:15 UTC</p> -<p>17:57 <code>&lt;beantaxi&gt;</code> ERROR tests/integration_tests/modules/test_runcmd.py::TestRuncmd::test_runcmd - FileNotFoundError: [Errno 2] No such file or directory: '/home/ubuntu/.ssh/id_rsa.pub'</p> -<p>17:57 <code>&lt;beantaxi&gt;</code> That was the error message</p> -<p>17:59 <code>&lt;falcojr&gt;</code> tests require an ssh keypair. It'll use your user one by default or you can specify one manually in the integration settings config</p> -<p>17:59 <code>&lt;falcojr&gt;</code> do an <code>ssh-keygen</code></p> -<p>17:59 <code>&lt;beantaxi&gt;</code> The full test failed with 7 failures: <a href="https://paste.ubuntu.com/p/hcYN7ZDvbs/">https://paste.ubuntu.com/p/hcYN7ZDvbs/</a></p> -<p>18:00 <code>&lt;beantaxi&gt;</code> falcojr: Thanks ... I was just showing Odd_Bloke the error message I got before running ssh-keygen, which did indeed solve most of my issues</p> -<p>18:01 <code>&lt;beantaxi&gt;</code> falcojr: Also, this is just me running the existing integration tests on an EC2 instance. Without any of my changes</p> -<p>18:01 <code>&lt;falcojr&gt;</code> not sure the cause of that first one, but the rest are for code not in ubuntu images yet</p> -<p>18:03 <code>&lt;falcojr&gt;</code> the version of cloud_init to use is specified by the CLOUD_INIT_SOURCE variable (integration_settings.py...copy this to user_settings.py to easily override defaults)</p> -<p>18:03 <code>&lt;falcojr&gt;</code> it defaults to NONE which means use whatever image has been released on this platform</p> -<p>18:04 <code>&lt;falcojr&gt;</code> to test non-released code, changing it to IN_PLACE (only works on LXD) should work</p> -<p>18:08 <code>&lt;falcojr&gt;</code> you can also set it to ppa:cloud-init-dev/daily , but that won't contain any changes that you're trying to test</p> -<p>18:18 <code>&lt;beantaxi&gt;</code> falcojr: Copying integration_settings.py to user_settings.py and setting CLOUD_INIT_SOURCE=IN_PLACE made all the test_keys_to_console errors clean. There's still that simple_streams error. Do I just need to add a PPA for simplestreams? It looks like requires a file in /etc/apt/sources.list.d, but mine is empty</p> -<p>18:23 <code>&lt;falcojr&gt;</code> Not sure off the top of my head. Did you pip install the integration_requirements.txt?</p> -<p>18:38 * blackboxsw thinks I should about wrap up office hours. Thanks falcojr Odd_Bloke and beantaxi for the discussion there</p> -<p>18:38 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.4.0 (<a href="https://wiki.ubuntu.com/meetingology">https://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2021-02-23T17:18:00+00:002021-02-23T17:18:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2021-02-23:/status-2021-02-23.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init office hours meeting, started by blackboxsw, 23 Feb at 17:18 &mdash; 18:00 UTC.</li> -<li>Full logs at <a href="https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-02-23-17.18.log.html">https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-02-23-17.18.log.html</a></li> -</ul> -<h2>Meeting summary</h2> -<ul> -<li><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/c/server/cloud-init">https://discourse.ubuntu.com/c/server/cloud-init</a> (blackboxsw, 17:30)</li> -</ul> -<h2>People present (lines …</h2><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init office hours meeting, started by blackboxsw, 23 Feb at 17:18 &mdash; 18:00 UTC.</li> -<li>Full logs at <a href="https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-02-23-17.18.log.html">https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-02-23-17.18.log.html</a></li> -</ul> -<h2>Meeting summary</h2> -<ul> -<li><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/c/server/cloud-init">https://discourse.ubuntu.com/c/server/cloud-init</a> (blackboxsw, 17:30)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (17)</li> -<li>meetingology (2)</li> -<li>Odd_Bloke (2)</li> -</ul> -<h2>Full log</h2> -<p>17:18 <code>&lt;blackboxsw&gt;</code> #startmeeting cloud-init office hours</p> -<p>17:18 <code>&lt;meetingology&gt;</code> Meeting started at 17:18:36 UTC. The chair is blackboxsw. Information about MeetBot at <a href="https://wiki.ubuntu.com/meetingology">https://wiki.ubuntu.com/meetingology</a></p> -<p>17:18 <code>&lt;meetingology&gt;</code> Available commands: action, commands, idea, info, link, nick</p> -<p>17:18 <code>&lt;Odd_Bloke&gt;</code> o/</p> -<p>17:19 <code>&lt;blackboxsw&gt;</code> community notice: hi folks. We are resuming our much anticipated office hours. Every two weeks at this time. The IRC topic will host our upcoming expected office-hours meeting time.</p> -<p>17:19 <code>&lt;blackboxsw&gt;</code> \o Odd_Bloke thx</p> -<p>17:19 <code>&lt;blackboxsw&gt;</code> t</p> -<p>17:20 <code>&lt;blackboxsw&gt;</code> This meeting will provide an opportunity with multiple upstream cloud-init devs available to discuss bugs, features, ongoing development or answer your existential questions :)</p> -<p>17:20 <code>&lt;blackboxsw&gt;</code> We hope to continue this meeting with regular cadence (and calendar reminders) to make sure we hold this time and frequency.</p> -<p>17:22 <code>&lt;blackboxsw&gt;</code> I'll send an email to the mailing list (again) announcing this cadence. Again this time if for any discussions, questions or dev/feature topics that folks would like to gab about.</p> -<p>17:23 <code>&lt;blackboxsw&gt;</code> We just published a high-level update of what's been happening in the cloud-init space, <a href="https://discourse.ubuntu.com/t/cloud-init-status-02-23-2021/21069.">https://discourse.ubuntu.com/t/cloud-init-status-02-23-2021/21069.</a></p> -<p>17:25 <code>&lt;blackboxsw&gt;</code> As seen on the mailinglist, Odd_Bloke and falcojr have been trying to tidy up things for the upstream 21.1 timed release. Thanks both of you for driving this work. I believe 21.1 landed, was uploaded to Ubuntu 21.04 (Hirsute).</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> We are also planning on SRUing(StableReleaseUpdate - Ubuntu-speak for uploading) 21.1 plus a feature fix for OVS support into Xenial, Bionic, Focal and Groovy within the next week or two.</p> -<p>17:26 <code>&lt;Odd_Bloke&gt;</code> Yep, I'm currently working through the release announcement process.</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> great Dan. So, TLDR is watch the mailinglist cloud-init@lists.launchpad.net and discourse <a href="https://discourse.ubuntu.com/c/server/cloud-init">https://discourse.ubuntu.com/c/server/cloud-init</a> for announcements and updates</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> #link <a href="https://discourse.ubuntu.com/c/server/cloud-init">https://discourse.ubuntu.com/c/server/cloud-init</a></p> -<p>17:58 <code>&lt;blackboxsw&gt;</code> I think we've about rounded out the office-hours. (I spent that time walking through a sopel-irc bot setup to test out some of the features to see if we can't add some structure to this office-hours engagement (and frankly release announcements too )</p> -<p>17:59 <code>&lt;blackboxsw&gt;</code> Let's set that next office hours for +2 weeks-45 mins from now</p> -<p>18:00 <code>&lt;blackboxsw&gt;</code> hopefully by then we have an automated announcer kicking off the notification.</p> -<p>18:00 <code>&lt;blackboxsw&gt;</code> Thanks all!</p> -<p>18:00 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.4.0 (<a href="https://wiki.ubuntu.com/meetingology">https://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2020-11-17T17:25:00+00:002020-11-17T17:25:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2020-11-17:/status-2020-11-17.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting &amp;&amp; office hours, 17 Nov at 17:25 &mdash; 18:35 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-11-17-17.25.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-11-17-17.25.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/t/cloud-init-statue-11-17-20/19391">https://discourse.ubuntu.com/t/cloud-init-statue-11-17-20/19391</a> - <strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pull/655">https://github.com/canonical/cloud-init/pull/655</a> i'd …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting &amp;&amp; office hours, 17 Nov at 17:25 &mdash; 18:35 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-11-17-17.25.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-11-17-17.25.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/t/cloud-init-statue-11-17-20/19391">https://discourse.ubuntu.com/t/cloud-init-statue-11-17-20/19391</a> - <strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pull/655">https://github.com/canonical/cloud-init/pull/655</a> i'd love this too get merged, so we don't have to carry the patch on ports - <strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pull/655">https://github.com/canonical/cloud-init/pull/655</a> - <strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pull/647">https://github.com/canonical/cloud-init/pull/647</a> - <strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pull/588#pullrequestreview-529957360">https://github.com/canonical/cloud-init/pull/588#pullrequestreview-529957360</a> - <strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/sources/DataSourceAzure.py#L1325">https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/sources/DataSourceAzure.py#L1325</a> - <strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/config/cc_set_passwords.py#L163">https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/config/cc_set_passwords.py#L163</a> - <strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pull/663">https://github.com/canonical/cloud-init/pull/663</a> - <strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pull/659">https://github.com/canonical/cloud-init/pull/659</a> - <strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pulls">https://github.com/canonical/cloud-init/pulls</a>?q=is%3Apr+is%3Aopen+label%3A%22release+20.4%22 </p> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (48)</li> -<li>AnhVoMSFT (15)</li> -<li>rharper (7)</li> -<li>meena (6)</li> -<li>smoser (3)</li> -<li>meetingology (3)</li> -<li>Odd_Bloke (1)</li> -</ul> -<h2>Full Log</h2> -<p>17:25 <code>&lt;blackboxsw&gt;</code> #startmeeting cloud-init status meeting &amp;&amp; office hours</p> -<p>17:25 <code>&lt;meetingology&gt;</code> Meeting started Tue Nov 17 17:25:00 2020 UTC. The chair is blackboxsw. Information about MeetBot at <a href="http://wiki.ubuntu.com/meetingology.">http://wiki.ubuntu.com/meetingology.</a></p> -<p>17:25 <code>&lt;meetingology&gt;</code> </p> -<p>17:25 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>17:25 <code>&lt;blackboxsw&gt;</code> community-notice: hi folks just starting up an our cloud-init satus update and office hours community meeting.</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> As of the cloud-init summit, we decided to try to host these primarily async in discourse to allow folks in other timezones to participate as available.</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> I've just finished posting a status update for cloud-init upstream to <a href="https://discourse.ubuntu.com/t/cloud-init-statue-11-17-20/19391">https://discourse.ubuntu.com/t/cloud-init-statue-11-17-20/19391</a></p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> #link <a href="https://discourse.ubuntu.com/t/cloud-init-statue-11-17-20/19391">https://discourse.ubuntu.com/t/cloud-init-statue-11-17-20/19391</a></p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> #chairs rharper smoser Odd_Bloke</p> -<p>17:28 <code>&lt;rharper&gt;</code> o/</p> -<p>17:28 <code>&lt;blackboxsw&gt;</code> Generally I think this status meeting can be used as a platform for communication and discussion with the community.</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> for this week, as brought up by a few folks in the community, is that we are trying to define a "go" date for the next upstream cloud-init release 20.4.</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> The hope is to target this Friday Nov 20th. as a deadline for requesting specific PRs and reviews that are needed to get features or fixes included in this 20.4 release.</p> -<p>17:31 <code>&lt;meena&gt;</code> so, i just responded to falcojr's email</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> The goal of this date, from an Ubuntu standpoint, is also to be able to SRU (stable release update) and publish this functionality back to Xenial, Bionic and Focal before the end of the calendar year</p> -<p>17:32 <code>&lt;meena&gt;</code> <a href="https://github.com/canonical/cloud-init/pull/655">https://github.com/canonical/cloud-init/pull/655</a> i'd love this too get merged, so we don't have to carry the patch on ports</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> thanks meena there <a href="https://github.com/canonical/cloud-init/pull/655">https://github.com/canonical/cloud-init/pull/655</a> ahh I'm too late</p> -<p>17:34 <code>&lt;blackboxsw&gt;</code> So, for those who happen to be on this channel now, let's add links to the meeting log and I'll make sure they are also reflected on the discourse post and PRs that need review assessment and hopefully landing before upstream release cut.</p> -<p>17:34 <code>&lt;blackboxsw&gt;</code> #link <a href="https://github.com/canonical/cloud-init/pull/655">https://github.com/canonical/cloud-init/pull/655</a></p> -<p>17:34 <code>&lt;blackboxsw&gt;</code> rharper or smoser are there any concerns with existing PRs that you are aware of that should be destined for this 20.4 release?</p> -<p>17:35 <code>&lt;meena&gt;</code> rharper, i'd also love your historic knowledge on <a href="https://github.com/canonical/cloud-init/pull/588">https://github.com/canonical/cloud-init/pull/588</a> but that can wait until after the release</p> -<p>17:36 <code>&lt;blackboxsw&gt;</code> rharper: I wanted to put a solid review on the cached ds handling today/tomorrow</p> -<p>17:36 <code>&lt;blackboxsw&gt;</code> #link <a href="https://github.com/canonical/cloud-init/pull/647">https://github.com/canonical/cloud-init/pull/647</a></p> -<p>17:36 <code>&lt;blackboxsw&gt;</code> I've looked it over a couple times, but wanted to but some investment in the review myself today.</p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: welcome and thanks for peeking in to checkup. If your team also have any hopes for PRs you can pitch us here, discourse or email.</p> -<p>17:38 <code>&lt;AnhVoMSFT&gt;</code> I have a quick question on the cc_set_passwords. I'm still looking through the code but if anyone knows this one well and can point me to the right place to look it would be appreciated</p> -<p>17:39 <code>&lt;AnhVoMSFT&gt;</code> it seems like if we create an image that previously was deployed with password ABC, but during image preparation we don't delete that user, then when we deploy a VM with that image and specifying a new password DEF, it isn't applied. I.e., the user will still have password ABC</p> -<p>17:39 <code>&lt;rharper&gt;</code> blackboxsw: I'm not aware of anything critical PR wise; maybe the networking_cls bits; but not sure if that's ready;</p> -<p>17:40 <code>&lt;meena&gt;</code> from my understanding, that needs to get in</p> -<p>17:40 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: poking around now on that</p> -<p>17:41 <code>&lt;rharper&gt;</code> meena: yes; that makes sense; just hadn't looked at the current state of the PR since I last commented;</p> -<p>17:42 <code>&lt;rharper&gt;</code> meena: re: 588 (genreate_fallback_config); did you have a specific question you wanted some background on?</p> -<p>17:43 <code>&lt;meena&gt;</code> rharper, search for your name</p> -<p>17:44 <code>&lt;rharper&gt;</code> hidden under a "Load more Items"</p> -<p>17:44 <code>&lt;rharper&gt;</code> I'll respond</p> -<p>17:44 <code>&lt;blackboxsw&gt;</code> so instance-id should have changed on the newly deployed vm, so cc_set_passwords should get retriggered due to <a href="https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_set_passwords.py#L49">https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_set_passwords.py#L49</a> (the default frequency for cc modules). AnhVoMSFT: what the userdata password field you are using? top-level password or chpasswd?</p> -<p>17:45 <code>&lt;AnhVoMSFT&gt;</code> this is the user password passed in from ovf</p> -<p>17:45 <code>&lt;blackboxsw&gt;</code> as that'd be different code paths I think</p> -<p>17:45 <code>&lt;meena&gt;</code> <a href="https://github.com/canonical/cloud-init/pull/588#pullrequestreview-529957360">https://github.com/canonical/cloud-init/pull/588#pullrequestreview-529957360</a></p> -<p>17:46 <code>&lt;AnhVoMSFT&gt;</code> in a newly created instance without the existing user, I could see the password getting created during the initial useradd call when the user is created</p> -<p>17:47 <code>&lt;AnhVoMSFT&gt;</code> however, if the user existed, that code path isn't invoked. There's some code in cc_set_passwords to change the password for existing user, but I'm unsure when it's invoked (or why it's not invoked in the case of azure)</p> -<p>17:48 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: could you provide a paste of redacted userdata from that instance via <code>sudo cloud-init query userdata</code>... redacting the specific passwords ?</p> -<p>17:49 <code>&lt;blackboxsw&gt;</code> yeah I would have expected a log.debug("Changing password for %s:", users) log</p> -<p>17:53 <code>&lt;AnhVoMSFT&gt;</code> let me run the query</p> -<p>17:53 <code>&lt;AnhVoMSFT&gt;</code> there's nothing returned (since there's no userdata)</p> -<p>17:54 <code>&lt;AnhVoMSFT&gt;</code> looks like the ds Azure is adding the user/password information retrieved from OVF to cfg['defuser']</p> -<p>18:00 <code>&lt;AnhVoMSFT&gt;</code> <a href="https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/sources/DataSourceAzure.py#L1325">https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/sources/DataSourceAzure.py#L1325</a></p> -<p>18:00 <code>&lt;AnhVoMSFT&gt;</code> if I'm reading the code of cc_set_password correctly we will need to add cfg['password'] as well if we want the defuser's password to be changed?</p> -<p>18:01 <code>&lt;Odd_Bloke&gt;</code> rharper: We are treating the networking_cls PR as critical, and AFA(I/we)K it's pretty much ready to land.</p> -<p>18:02 <code>&lt;rharper&gt;</code> Odd_Bloke: ok, makes sense</p> -<p>18:06 <code>&lt;smoser&gt;</code> blackboxsw: i dont have anything critical.</p> -<p>18:06 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: so normalize_users_groups is what pulls the default_user configuration out of /etc/cloud/cloud.cfg(.d/*)</p> -<p>18:06 <code>&lt;blackboxsw&gt;</code> <a href="https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/config/cc_set_passwords.py#L163">https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/config/cc_set_passwords.py#L163</a></p> -<p>18:07 <code>&lt;blackboxsw&gt;</code> that ug_util.extract_default is what should be seeing the passwords set/changed</p> -<p>18:07 <code>&lt;smoser&gt;</code> </p> -<p>18:08 <code>&lt;smoser&gt;</code> #669 looks reasonable.</p> -<p>18:08 <code>&lt;blackboxsw&gt;</code> yet interestingly. password referenced there is only set from the top-level "password" value <a href="https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/config/cc_set_passwords.py#L143">https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/config/cc_set_passwords.py#L143</a></p> -<p>18:08 <code>&lt;blackboxsw&gt;</code> thanks smoser for that</p> -<p>18:08 <code>&lt;blackboxsw&gt;</code> #link <a href="https://github.com/canonical/cloud-init/pull/663">https://github.com/canonical/cloud-init/pull/663</a></p> -<p>18:12 <code>&lt;AnhVoMSFT&gt;</code> let me test it out real quick by setting the cfg['password'] key in the ds azure</p> -<p>18:12 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: so, I may be mistaken but if a password key is set on the default_user in system_info (which is what it looks like azure does), then that default password is only used if there is no top-level "password" key provided in merged cloud-config, then and the default_user specific password key is ignored</p> -<p>18:12 <code>&lt;blackboxsw&gt;</code> +1 AnhVoMSFT</p> -<p>18:13 <code>&lt;AnhVoMSFT&gt;</code> yep that worked</p> -<p>18:13 <code>&lt;AnhVoMSFT&gt;</code> it's a one liner change, I'll submit a PR asap</p> -<p>18:14 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: good. ok, I wonder if this ever worked (having the password key hung under default_user scope?)</p> -<p>18:14 <code>&lt;blackboxsw&gt;</code> as in, I wonder if there was a regression introduced with some of the is_FreeBSD restructuring</p> -<p>18:15 <code>&lt;AnhVoMSFT&gt;</code> I don't think so. customer reported this issue in cloud-init 18.5 and I repro-ed it in master</p> -<p>18:15 <code>&lt;blackboxsw&gt;</code> ok, ok. good thanks for that context</p> -<p>18:15 <code>&lt;blackboxsw&gt;</code> and checking the recent BSD change it looking completely unrelated</p> -<p>18:17 <code>&lt;blackboxsw&gt;</code> ok AnhVoMSFT when the PR is submitted. let's get that queued for this upstream 20.4 if we can</p> -<p>18:18 <code>&lt;blackboxsw&gt;</code> do folks have an opinion on whether it helps to add a custom label to active PRs that we intend to land before upstream release like 'upstream-blocker' or 'upstream-release'?</p> -<p>18:19 <code>&lt;blackboxsw&gt;</code> just for more public tracking/transparency. not sure if that's helpful or just needless process?</p> -<p>18:19 <code>&lt;blackboxsw&gt;</code> do folks have an opinion on whether it helps to add a custom label to active PRs that we intend to land before upstream release like 'upstream-blocker' or 'upstream-release'?</p> -<p>18:23 <code>&lt;AnhVoMSFT&gt;</code> I think that would be helpful, yes</p> -<p>18:25 <code>&lt;blackboxsw&gt;</code> ok, let's try it out. let's try specific 'release 20.4' and see how that feels to folks. easy enough to drop if it doesn't improve communication</p> -<p>18:30 <code>&lt;blackboxsw&gt;</code> also added pickling upgrade test validation PR</p> -<p>18:30 <code>&lt;blackboxsw&gt;</code> #link <a href="https://github.com/canonical/cloud-init/pull/659">https://github.com/canonical/cloud-init/pull/659</a></p> -<p>18:31 <code>&lt;blackboxsw&gt;</code> ok, last call for cloud-init status / office hours. Any other takers for discussion at the moment? If not I'll close out the meeting in a few mins and publish minutes.</p> -<p>18:33 <code>&lt;blackboxsw&gt;</code> my plan is still to publish to cloud-init.github.io status meetings and link it from the primary post at <a href="https://discourse.ubuntu.com/t/cloud-init-status-11-17-20/19391">https://discourse.ubuntu.com/t/cloud-init-status-11-17-20/19391</a></p> -<p>18:34 <code>&lt;blackboxsw&gt;</code> the following will list prs we hope to work toward landing this week</p> -<p>18:34 <code>&lt;blackboxsw&gt;</code> #link <a href="https://github.com/canonical/cloud-init/pulls">https://github.com/canonical/cloud-init/pulls</a>?q=is%3Apr+is%3Aopen+label%3A%22release+20.4%22</p> -<p>18:35 <code>&lt;blackboxsw&gt;</code> thanks again for the discussion and suggestions folks. Have a good one!</p> -<p>18:35 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2020-09-08T16:18:00+00:002020-09-08T16:18:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2020-09-08:/status-2020-09-08.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 08 Sep at 16:18 &mdash; 17:13 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-09-08-16.18.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-09-08-16.18.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-08-25.html#status-2020-08-25">https://cloud-init.github.io/status-2020-08-25.html#status-2020-08-25</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:21 …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 08 Sep at 16:18 &mdash; 17:13 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-09-08-16.18.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-09-08-16.18.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-08-25.html#status-2020-08-25">https://cloud-init.github.io/status-2020-08-25.html#status-2020-08-25</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:21.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:25.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://paste.ubuntu.com/p/NgqncRMG9c/">https://paste.ubuntu.com/p/NgqncRMG9c/</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:46.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1893064">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1893064</a> </li> -</ul> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 16:54.</p> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (51)</li> -<li>meetingology (3)</li> -<li>amansi26 (3)</li> -<li>ubot5 (2)</li> -</ul> -<h2>Full Log</h2> -<p>16:18 <code>&lt;blackboxsw&gt;</code> #startmeeting cloud-init status meeting</p> -<p>16:18 <code>&lt;meetingology&gt;</code> Meeting started Tue Sep 8 16:18:47 2020 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:18 <code>&lt;meetingology&gt;</code> </p> -<p>16:18 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #chairs smoser Odd_Bloke rharper falcojr lucasmoura</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> hey folks. welcome to another public cloud-init status meeting</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> disclaimer: interruptions and side conversations are welcome</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> We use this platform/channel to discuss latest and greatest cloud-init, as well as ensuring that there are a couple of upstream developers present to field questions or discussion as needed.</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> We gather here in this IRC channel every 2 weeks to discuss current development tasks and progress on cloud-init.</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> Previous meeting minutes are here;</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2020-08-25.html#status-2020-08-25">https://cloud-init.github.io/status-2020-08-25.html#status-2020-08-25</a></p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> The topics we'll cover today: Previous Actions, Recent Changes, In-progress Development, Community Charter, Office Hours (~30 mins).</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> I expect today will be short as the entire Canonical team is involved in cloud-init SRU verification for Ubuntu at the moment</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> last meeting had an action item we needed to resolve</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> bbsw add workitem to SRU release process to announce to mailinglist estimated next SRU timeframe.</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> this item can be resolved as I've added the content requested to our email template which will be sent out once this SRU completes.</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> I see no other actions from last meeting</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> The following are upstream commits landed in cloud-init's master branch:</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> #link <a href="https://paste.ubuntu.com/p/NgqncRMG9c/">https://paste.ubuntu.com/p/NgqncRMG9c/</a></p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> In the last couple of weeks we cut the upstream 20.3 release (thanks everyone for all the help there). Queued SRU uploads for ubuntu/xenial, bionic and focal release testing.</p> -<p>16:28 <code>&lt;amansi26&gt;</code> blackboxsw: metadata here will be the configdrive, if my understanding is right?</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> And added some goodness to systemd units and ordering (sort systemd cloud-init-local.service hv_kvp_daemon and systemd: add Before=shutdown.target when Conflicts=shutdown.target is</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> used )</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> thanks paride and robjo for those commits</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> amansi26: +1 you can see the metadata configured hostname from cloud-init query local-hostname I think</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> amansi26: +1 you can see the metadata configured hostname from <code>cloud-init query local-hostname</code> I think</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> amansi26: I was just starting to respond to your bug you linked too</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> I think preserve_hostname: false (which is cloud-init's default behavior ) means cloud-init will read that hostname from metadata and apply it to the system</p> -<p>16:31 <code>&lt;amansi26&gt;</code> Sure. there is another bug which I observed on a RHEL8 environment: <a href="https://bugs.launchpad.net/cloud-init/+bug/1894837">https://bugs.launchpad.net/cloud-init/+bug/1894837</a></p> -<p>16:31 <code>&lt;ubot5&gt;</code> Ubuntu bug 1894837 in cloud-init "RHEL8 ipv4 IPs not getting set" [Undecided,New]</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> amansi26: sorry cloud-init query local_hostname (# not with a hyphen)</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> checking 2nd bug</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> so amansi26 you'd like the ability to override the iface_defaults on rhel systems for NM_CONTROLLED to set True instead of false for cloud-init interfaces?</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> generally if cloud-init is rendering network configuration on an instance, it tries to avoid using network manager by default. I think it's worth requesting logs on your bug</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> those cloud-init logs can be obtained using cloud-init collect-logs (which generates a tar.gz file in the current working directory). then attach that to the bug</p> -<p>16:41 <code>&lt;amansi26&gt;</code> yes, since I was reading the documentation for RHEL8 network configuration, I found that NM_CONTROLLED = yes should be there. but we are passing the value as No. Sure I will attach the logs to the defect</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> thanks amansi26 I responded on that bug too</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> Ok, per the meeting, that wraps #recent-changes topic I believe</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> Currently the Canonical team is working hard on SRU verification so we can release cloud-init v. 20.3 to Xenial, Bionic and Focal. It looks like we are done with most major cloud verification and walking through individual verification items.</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> I believe falcojr mentioned this morning we are about 5 of 30ish verification items complete.</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> we are continuing to work this verification as our top priority</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> folks interested should subscribe to updates on our SRU bug</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1893064">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1893064</a></p> -<p>16:51 <code>&lt;ubot5&gt;</code> Ubuntu bug 1893064 in cloud-init (Ubuntu) "sru cloud-init (20.2-45 to 20.3-2) Xenial, Bionic, and Focal" [Undecided,In progress]</p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> that bug will transition to verification-complete once all verification is done</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> #topic Community Charter</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> The following topics are still topics for ongoing community development anyone new to cloud-init, or with a bit of time could easily grab one of these bitesized tasks:</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> JSON schema extensions to validate user-data before instance launch: <a href="https://bugs.launchpad.net/cloud-init/">https://bugs.launchpad.net/cloud-init/</a>?field.tag=bitesize</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> - cloudinit.net refactor into distro-specific networking subclasses cloudinit.distros.networking: <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=net-refactor</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> If anyone would like to be involved more than they currently are, please feel free to contact us here in IRC #cloud-init on Freenode or on the mailing list cloud-init@lists.launchpad.net and we can see how best we can get you "set up"</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> this time of the meeting is really just an open door for any discussions, concerns, bugs, questions or general prodding of upstream devs to make sure existing development work is unblocked where possible.</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> in absence of discussions. We actually will be focused on SRU verification tasks today.</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> each of these verification logs and scripts are pushed as pull requests to <a href="https://github.com/cloud-init/ubuntu-sru/pulls">https://github.com/cloud-init/ubuntu-sru/pulls</a></p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> ok I think that about wraps today's session. Next meeting will be in two weeks, but we'll likely see you in channel earlier.</p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2020-08-25T16:24:00+00:002020-08-25T16:24:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2020-08-25:/status-2020-08-25.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 25 Aug at 16:24 &mdash; 17:13 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-08-25-16.24.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-08-25-16.24.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io">https://cloud-init.github.io</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:27.</p> -<h3>Recent Changes</h3> -<p>The …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 25 Aug at 16:24 &mdash; 17:13 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-08-25-16.24.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-08-25-16.24.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io">https://cloud-init.github.io</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:27.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:27.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://paste.ubuntu.com/p/h2qxwKwvFw/">https://paste.ubuntu.com/p/h2qxwKwvFw/</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:35.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://wiki.ubuntu.com/CloudinitUpdates">https://wiki.ubuntu.com/CloudinitUpdates</a> </li> -</ul> -<h3>Community Charter</h3> -<p>The discussion about "Community Charter" started at 16:40.</p> -<h3>#cloud-init pull-requests <a href="https://git.io/JeVed">https://git.io/JeVed</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting Sep 8 16:15 UTC | 20.2 (Apr 26) | 20.3 (estimated Aug 19th) <a href="https://bugs.launchpad.net/cloud-init/+filebug">https://bugs.launchpad.net/cloud-init/+filebug</a></h3> -<p>The discussion about "#cloud-init pull-requests <a href="https://git.io/JeVed">https://git.io/JeVed</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting Sep 8 16:15 UTC | 20.2 (Apr 26) | 20.3 (estimated Aug 19th) <a href="https://bugs.launchpad.net/cloud-init/+filebug">https://bugs.launchpad.net/cloud-init/+filebug</a>" started at 16:48.</p> -<ul> -<li><strong>ACTION</strong>: bbsw add workitem to SRU release process to announce to mailinglist estimated next SRU timeframe</li> -</ul> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw_ (58)</li> -<li>meetingology (5)</li> -<li>AnhVoMSFT (4)</li> -<li>falcojr (1)</li> -<li>smoser (0)</li> -<li>lucasmoura (0)</li> -<li>rharper (0)</li> -</ul> -<h2>Full Log</h2> -<p>16:24 <code>&lt;blackboxsw_&gt;</code> #startmeeting cloud-init status meeting</p> -<p>16:24 <code>&lt;meetingology&gt;</code> Meeting started Tue Aug 25 16:24:27 2020 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:24 <code>&lt;meetingology&gt;</code> </p> -<p>16:24 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:24 <code>&lt;blackboxsw_&gt;</code> #chair smoser rharper falcojr lucasmoura</p> -<p>16:24 <code>&lt;meetingology&gt;</code> Current chairs: blackboxsw_ falcojr lucasmoura rharper smoser</p> -<p>16:25 <code>&lt;blackboxsw_&gt;</code> hey folks, welcome to another cloud-init bi-weekly (or bi-monthly) community status meeting</p> -<p>16:25 <code>&lt;blackboxsw_&gt;</code> or semi-monthly</p> -<p>16:26 <code>&lt;blackboxsw_&gt;</code> ... anyhow. We use this platform/channel to discuss latest and greatest cloud-init, as well as ensuring that there are a couple of upstream developers present to field questions or discussion as needed.</p> -<p>16:26 <code>&lt;blackboxsw_&gt;</code> We gather here in this IRC channel every 2 weeks to discuss current development tasks and progress on cloud-init. All questions and side-conversations welcome</p> -<p>16:26 <code>&lt;blackboxsw_&gt;</code> we keep our meeting minutes from previous meetings here:</p> -<p>16:27 <code>&lt;blackboxsw_&gt;</code> #link <a href="https://cloud-init.github.io">https://cloud-init.github.io</a></p> -<p>16:27 <code>&lt;blackboxsw_&gt;</code> The topics we'll cover today: Previous Actions, Recent Changes, In-progress Development, Community Charter, Office Hours (~30 mins).</p> -<p>16:27 <code>&lt;blackboxsw_&gt;</code> #topic Previous Actions</p> -<p>16:27 <code>&lt;blackboxsw_&gt;</code> Looks like no carryover actions from last meeting</p> -<p>16:27 <code>&lt;blackboxsw_&gt;</code> #topic Recent Changes</p> -<p>16:30 <code>&lt;blackboxsw_&gt;</code> The following changes have landed in tip of master since last meeting (08/14/20).</p> -<p>16:30 <code>&lt;blackboxsw_&gt;</code> found via git log --since 2020-08-014</p> -<p>16:30 <code>&lt;blackboxsw_&gt;</code> #link <a href="https://paste.ubuntu.com/p/h2qxwKwvFw/">https://paste.ubuntu.com/p/h2qxwKwvFw/</a></p> -<p>16:31 <code>&lt;blackboxsw_&gt;</code> things to note. we <em>JUST</em> cut 20.3 upstream release as of 20 seconds ago. Thanks a bunch James(falcojr) for getting the Azure timeout pr up to close out this upstream release.</p> -<p>16:31 <code>&lt;blackboxsw_&gt;</code> and thanks smoser, rharper and meena for all the reviews and work here.</p> -<p>16:34 <code>&lt;blackboxsw_&gt;</code> in the last couple weeks we got fixes to reduce boot timeouts for certain azure accelerated network instances, fix oracle datasource retries, handle compressed user-data on juju deployed machines in 'cloud-init query', and early boot dhclient will not attempt to run outside of the /var/tmp sandbox directory if that directory is marked no-exec</p> -<p>16:34 <code>&lt;blackboxsw_&gt;</code> thanks otubo for that noexec branch</p> -<p>16:35 <code>&lt;blackboxsw_&gt;</code> #topic In-progress Development</p> -<p>16:36 <code>&lt;blackboxsw_&gt;</code> So thanks all for the 20.3 upstream release. We will be tagging that release and pushing that tag to master just after this meeting</p> -<p>16:36 <code>&lt;blackboxsw_&gt;</code> falcojr: is our release lead for this upstream release and SRU so he'll be working through the release process work items. Thanks falcojr.</p> -<p>16:37 <code>&lt;blackboxsw_&gt;</code> -next step on the release process is to publish to Ubuntu Groovy (20.10) and then queue up a -proposed cloud-init SRU upload into xenial, bionic and focal.</p> -<p>16:37 <code>&lt;blackboxsw_&gt;</code> we will then begin the SRU testing (which we hope to keep at around ~7days)</p> -<p>16:38 <code>&lt;blackboxsw_&gt;</code> as smoser mentioned earlier. cloud-init has to follow this process to update cloud-init in stable Ubuntu releases</p> -<p>16:38 <code>&lt;blackboxsw_&gt;</code> #link <a href="https://wiki.ubuntu.com/CloudinitUpdates">https://wiki.ubuntu.com/CloudinitUpdates</a></p> -<p>16:39 <code>&lt;blackboxsw_&gt;</code> An email will be sent to the cloud-init mailinglist notifying the community about the SRU under test in the event that folks have spare cycles to pitch in on some of the verification effort</p> -<p>16:40 <code>&lt;blackboxsw_&gt;</code> also "in-progress" paride is cleaning up a bunch of automated CI-related failures and lint issues in cloud-init, so expect some branches against cloud-init on that front as well</p> -<p>16:40 <code>&lt;blackboxsw_&gt;</code> #topic Community Charter</p> -<p>16:41 <code>&lt;blackboxsw_&gt;</code> The following topics are still topics for ongoing community development anyone new to cloud-init, or with a bit of time could easily grab one of these bitesized tasks:</p> -<p>16:41 <code>&lt;blackboxsw_&gt;</code> JSON schema extensions to validate user-data before instance launch: <a href="https://bugs.launchpad.net/cloud-init/">https://bugs.launchpad.net/cloud-init/</a>?field.tag=bitesize</p> -<p>16:41 <code>&lt;blackboxsw_&gt;</code> - Datasource documentation and updates</p> -<p>16:41 <code>&lt;blackboxsw_&gt;</code> - cloudinit.net refactor into distro-specific networking subclasses cloudinit.distros.networking: <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=net-refactor</p> -<p>16:41 <code>&lt;blackboxsw_&gt;</code> As always: thank you all for bug contributions, PR submissions, triage and discussion participation.</p> -<p>16:41 <code>&lt;blackboxsw_&gt;</code> If anyone would like to be involved more than they currently are, please feel free to contact us here in IRC #cloud-init on Freenode or on the mailing list cloud-init@lists.launchpad.net and we can see how best we can get you "set up"</p> -<p>16:42 <code>&lt;blackboxsw_&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:42 <code>&lt;blackboxsw_&gt;</code> his time of the meeting is really just an open door for any discussions, concerns, bugs, questions or general prodding of upstream devs to make sure existing development work is unblocked where possible.</p> -<p>16:42 <code>&lt;blackboxsw_&gt;</code> *This time</p> -<p>16:42 <code>&lt;blackboxsw_&gt;</code> while we're at it with meeting time.... I'll set the next cloud-init status meeting date in the topic of this IRC channel</p> -<p>16:42 <code>&lt;AnhVoMSFT&gt;</code> When do you anticipate the next SRU would be?</p> -<p>16:43 <code>&lt;AnhVoMSFT&gt;</code> (after 20.3)</p> -<p>16:44 <code>&lt;blackboxsw_&gt;</code> AnhVoMSFT: thanks for the question. I hope today for 20.3, I think 20.4 will likely align with the next Ubuntu release cycle (20.10) so, October, 2020</p> -<p>16:46 <code>&lt;blackboxsw_&gt;</code> as mentioned in passing earlier, we are looking at trying to create an upstream release of cloud-init when any significant feature set has landed in tip to make release verification easier (and hopefull include less sprawling sets of broad commit streams).</p> -<p>16:46 <code>&lt;blackboxsw_&gt;</code> this ultimately may translated to 4-5 releases per year</p> -<p>16:46 <code>&lt;blackboxsw_&gt;</code> I expect a frequency of `&lt; 3 months</p> -<p>16:48 <code>&lt;blackboxsw_&gt;</code> #topic #cloud-init pull-requests <a href="https://git.io/JeVed">https://git.io/JeVed</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting Sep 8 16:15 UTC | 20.2 (Apr 26) | 20.3 (estimated Aug 19th) <a href="https://bugs.launchpad.net/cloud-init/+filebug">https://bugs.launchpad.net/cloud-init/+filebug</a></p> -<p>16:49 <code>&lt;blackboxsw_&gt;</code> next status meeting sept 8th, same time ^</p> -<p>16:49 <code>&lt;AnhVoMSFT&gt;</code> Thanks. There's some planned work for Azure's pre-provisioning v2 and will need some change in cloud-init. We're trying to get a sense of when cloud-init SRUs land so that we can communicate the timeline</p> -<p>16:52 <code>&lt;blackboxsw_&gt;</code> @AnhVoMSFT generally cadence has been ~3 months between SRUs, I think we'd like to see a slightly higher frequency than that because our last SRU was so costly. but I think expectation for this pass is likely 10/15/2020</p> -<p>16:53 <code>&lt;blackboxsw_&gt;</code> also, if we are looking to test features in Ubuntu Groovy 20.10 images, they don't require an SRU, so upload to that development release are possible any time (we could do that as frequently as weekly if need be)</p> -<p>16:56 <code>&lt;AnhVoMSFT&gt;</code> thanks for the clarification @blackboxsw_</p> -<p>16:57 <code>&lt;blackboxsw_&gt;</code> so as of today, I expect we'll have an SRU in October and likely something beginning of Jan</p> -<p>16:57 <code>&lt;blackboxsw_&gt;</code> I'll take an action for us to communicate via mailinglist the next estimated SRU once this SRU for 20.3 closes out</p> -<p>16:59 <code>&lt;blackboxsw_&gt;</code> #action bbsw add workitem to SRU release process to announce to mailinglist estimated next SRU timeframe</p> -<p>16:59 * meetingology bbsw add workitem to SRU release process to announce to mailinglist estimated next SRU timeframe</p> -<p>16:59 <code>&lt;blackboxsw_&gt;</code> and again we hope to have 20.3 SRU complete by next week</p> -<p>16:59 <code>&lt;blackboxsw_&gt;</code> complete, as in publish the 20.3 SRU for next week into Ubuntu xenial and later</p> -<p>17:00 <code>&lt;blackboxsw_&gt;</code> I expect today we publish tip of master (20.3) into Ubuntu Groovy (20.10) so expect to see it in your friendly neighborhood ubuntu cloud-images in the next day or two</p> -<p>17:04 <code>&lt;blackboxsw_&gt;</code> falcojr: I just annotated tag 20.3 and pushed to upstream</p> -<p>17:04 <code>&lt;blackboxsw_&gt;</code> so we have a signed tag</p> -<p>17:04 <code>&lt;blackboxsw_&gt;</code> falcojr: so next task is <a href="https://trello.com/c/KxShylli/14-upload-source-tarball-to-launchpad">https://trello.com/c/KxShylli/14-upload-source-tarball-to-launchpad</a></p> -<p>17:05 <code>&lt;falcojr&gt;</code> Cool, I can jump on that</p> -<p>17:12 <code>&lt;blackboxsw_&gt;</code> ok I think we'll wrap up the status meeting. Thanks all for tuning in!</p> -<p>17:13 <code>&lt;blackboxsw_&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2020-07-28T16:55:00+00:002020-07-28T16:55:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2020-07-28:/status-2020-07-28.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 28 Jul at 16:55 &mdash; 17:56 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-07-28-16.55.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-07-28-16.55.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-07-14.html#status-2020-07-14">https://cloud-init.github.io/status-2020-07-14.html#status-2020-07-14</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:58 …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 28 Jul at 16:55 &mdash; 17:56 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-07-28-16.55.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-07-28-16.55.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-07-14.html#status-2020-07-14">https://cloud-init.github.io/status-2020-07-14.html#status-2020-07-14</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:58.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 17:00.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://paste.ubuntu.com/p/RjZcwtk6Hd/">https://paste.ubuntu.com/p/RjZcwtk6Hd/</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 17:05.</p> -<h3>Community Charter</h3> -<p>The discussion about "Community Charter" started at 17:11.</p> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 17:15.</p> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw_ (38)</li> -<li>meetingology (4)</li> -<li>rharper (0)</li> -<li>Odd_Bloke (0)</li> -<li>smoser (0)</li> -</ul> -<h2>Full Log</h2> -<p>16:55 <code>&lt;blackboxsw_&gt;</code> #startmeeting cloud-init status meeting</p> -<p>16:55 <code>&lt;meetingology&gt;</code> Meeting started Tue Jul 28 16:55:17 2020 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:55 <code>&lt;meetingology&gt;</code> </p> -<p>16:55 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:56 <code>&lt;blackboxsw_&gt;</code> community notice: time for another bi-weekly (or semi-monthly if you prefer) cloud-init community status meeting</p> -<p>16:56 <code>&lt;blackboxsw_&gt;</code> #chair Odd_Bloke smoser rharper</p> -<p>16:56 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw_ rharper smoser</p> -<p>16:57 <code>&lt;blackboxsw_&gt;</code> Hello folks, cloud-init community status roundup. We gather here in this IRC channel every 2 weeks to discuss current development tasks and progress on cloud-init.</p> -<p>16:57 <code>&lt;blackboxsw_&gt;</code> All questions. side-conversations and interruptions are welcome</p> -<p>16:58 <code>&lt;blackboxsw_&gt;</code> Last meeting minutes live here</p> -<p>16:58 <code>&lt;blackboxsw_&gt;</code> #link <a href="https://cloud-init.github.io/status-2020-07-14.html#status-2020-07-14">https://cloud-init.github.io/status-2020-07-14.html#status-2020-07-14</a></p> -<p>16:58 <code>&lt;blackboxsw_&gt;</code> he topics we'll cover today: Previous Actions, Recent Changes, In-progress Development, Community Charter, Office Hours (~30 mins).</p> -<p>16:58 <code>&lt;blackboxsw_&gt;</code> #topic Previous Actions</p> -<p>16:58 <code>&lt;blackboxsw_&gt;</code> None found in meeting minutes from last session.</p> -<p>16:59 * blackboxsw_ sets the topic for next meeting.</p> -<p>16:59 <code>&lt;blackboxsw_&gt;</code> +2 weeks from now</p> -<p>16:59 <code>&lt;blackboxsw_&gt;</code> August 11th 16:15 UTC</p> -<p>17:00 <code>&lt;blackboxsw_&gt;</code> #topic Recent Changes</p> -<p>17:00 <code>&lt;blackboxsw_&gt;</code> The following commits have been landed on master of upstream branch since last meeting: found via git log --since 2020-07-14</p> -<p>17:01 <code>&lt;blackboxsw_&gt;</code> #link <a href="https://paste.ubuntu.com/p/RjZcwtk6Hd/">https://paste.ubuntu.com/p/RjZcwtk6Hd/</a></p> -<p>17:02 <code>&lt;blackboxsw_&gt;</code> features of note:</p> -<p>17:02 <code>&lt;blackboxsw_&gt;</code> - azure: avoid bouncing hostname if set hostname fails</p> -<p>17:03 <code>&lt;blackboxsw_&gt;</code> - vmware: new defaults for post customization script overrides on vCloud</p> -<p>17:04 <code>&lt;blackboxsw_&gt;</code> - azure ValueError raised if JsonDecodeErrors is not available when parsing metadata</p> -<p>17:05 <code>&lt;blackboxsw_&gt;</code> Thanks Goneri otubo anhVo and dermotbradley for community contributions this round</p> -<p>17:05 <code>&lt;blackboxsw_&gt;</code> #topic In-progress Development</p> -<p>17:09 <code>&lt;blackboxsw_&gt;</code> Current projects for cloud-init are leading us to additional features:</p> -<p>17:10 <code>&lt;blackboxsw_&gt;</code> - network device hot plug support for cloud-init post-boot</p> -<p>17:10 <code>&lt;blackboxsw_&gt;</code> - better integration testing on other clouds, Oracle support</p> -<p>17:11 <code>&lt;blackboxsw_&gt;</code> - extended json schema validation and publishing full static schema versions for external tools</p> -<p>17:11 <code>&lt;blackboxsw_&gt;</code> #topic Community Charter</p> -<p>17:12 <code>&lt;blackboxsw_&gt;</code> The following topics are still topics for ongoing community development:</p> -<p>17:13 <code>&lt;blackboxsw_&gt;</code> - JSON schema extensions to validate user-data before instance launch: <a href="https://bugs.launchpad.net/cloud-init/">https://bugs.launchpad.net/cloud-init/</a>?field.tag=bitesize</p> -<p>17:13 <code>&lt;blackboxsw_&gt;</code> - Datasource documentation and updates</p> -<p>17:14 <code>&lt;blackboxsw_&gt;</code> - cloudinit.net refactor into distro-specific networking subclasses cloudinit.distros.networking: <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=net-refactor</p> -<p>17:15 <code>&lt;blackboxsw_&gt;</code> As always: thank you all for bug contributions, PR submissions, triage and discussion participation.</p> -<p>17:15 <code>&lt;blackboxsw_&gt;</code> If anyone would like to be involved more than they currently are, please feel free to contact us here in IRC #cloud-init on Freenode or on the mailing list cloud-init@lists.launchpad.net and we can see how best we can get you "set up"</p> -<p>17:15 <code>&lt;blackboxsw_&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>17:17 <code>&lt;blackboxsw_&gt;</code> This time of the meeting is really just an open door for any discussions, concerns, bugs, questions or general prodding of upstream devs to make sure existing development work is unblocked where possible.</p> -<p>17:17 <code>&lt;blackboxsw_&gt;</code> In the absence of discussions, review of existing PRs is addressed.</p> -<p>17:56 <code>&lt;blackboxsw_&gt;</code> Thanks for tuning in folks. have a good one!</p> -<p>17:56 <code>&lt;blackboxsw_&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2020-07-14T16:52:00+00:002020-07-14T16:52:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2020-07-14:/status-2020-07-14.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 14 Jul at 16:52 &mdash; 17:50 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-07-14-16.52.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-07-14-16.52.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-06-30.html#status-2020-06-30">https://cloud-init.github.io/status-2020-06-30.html#status-2020-06-30</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:55 …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 14 Jul at 16:52 &mdash; 17:50 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-07-14-16.52.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-07-14-16.52.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-06-30.html#status-2020-06-30">https://cloud-init.github.io/status-2020-06-30.html#status-2020-06-30</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:55.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:56.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://paste.ubuntu.com/p/6Fn5jy8t46/">https://paste.ubuntu.com/p/6Fn5jy8t46/</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 17:01.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018</a> </li> -</ul> -<h3>Community Charter</h3> -<p>The discussion about "Community Charter" started at 17:08.</p> -<ul> -<li><strong>LINK</strong>: k <a href="https://bugs.launchpad.net/cloud-init/">https://bugs.launchpad.net/cloud-init/</a>?field.tag=bitesize</li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=net-refactor </li> -<li><strong>LINK</strong>: <a href="https://cloudinit.readthedocs.io/en/latest/topics/hacking.html#ongoing-refactors">https://cloudinit.readthedocs.io/en/latest/topics/hacking.html#ongoing-refactors</a> </li> -</ul> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 17:13.</p> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (52)</li> -<li>ubot5 (5)</li> -<li>meetingology (4)</li> -<li>AnhVoMSFT (2)</li> -<li>Odd_Bloke (2)</li> -<li>smoser (0)</li> -<li>rharper (0)</li> -</ul> -<h2>Full Log</h2> -<p>16:52 <code>&lt;blackboxsw&gt;</code> #startmeeting cloud-init status meeting</p> -<p>16:52 <code>&lt;meetingology&gt;</code> Meeting started Tue Jul 14 16:52:35 2020 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:52 <code>&lt;meetingology&gt;</code> </p> -<p>16:52 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:52 <code>&lt;AnhVoMSFT&gt;</code> nvm</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> heh.</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> let's do it since we have an active attendee.</p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> i'll make it snappy today</p> -<p>16:53 <code>&lt;AnhVoMSFT&gt;</code> sounds good</p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> community notice: time for another bi-weekly (or semi-monthly if you prefer) cloud-init community status meeting</p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> #chair rharper Odd_Bloke smoser</p> -<p>16:53 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw rharper smoser</p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> welcome to another round of cloud-init upstream updates and discussion. We use this meeting as a time to gather to discuss current development of cloud-init, ask and answer questions, and generally expedite development be unblocking devs. All questions. side-conversations and interruptions are welcome</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> first order of bizzzznesss. setting the meeting for next time</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> +2 weeks from today</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> July 28th same time (minus 30 mins)</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> previous meeting minutes are here:</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2020-06-30.html#status-2020-06-30">https://cloud-init.github.io/status-2020-06-30.html#status-2020-06-30</a></p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> The topics we'll cover today: Previous Actions, Recent Changes, In-progress Development, Community Charter, Office Hours (~30 mins).</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> none seen last session. so we can jump to the next topic</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> The following commits have been landed on master of upstream branch since last meeting: found via git log --since 2020-06-30</p> -<p>16:57 <code>&lt;blackboxsw&gt;</code> #link <a href="https://paste.ubuntu.com/p/6Fn5jy8t46/">https://paste.ubuntu.com/p/6Fn5jy8t46/</a></p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> a bit of cleanup and test coverage work and CI fixups for lxd integratin testing in those commits.</p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> Of note:</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> a fix for (LP: #1456277) thx lucas</p> -<p>16:59 <code>&lt;ubot5&gt;</code> Launchpad bug 1456277 in cloud-init "cloud-init searches for ec2 mirrors regardless of what cloud its on" [High,Fix committed] <a href="https://launchpad.net/bugs/1456277">https://launchpad.net/bugs/1456277</a></p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> a fix for (LP: #1884619) part of the cloudinit.net refactor for thx Odd_Bloke</p> -<p>16:59 <code>&lt;ubot5&gt;</code> Launchpad bug 1884619 in cloud-init "cloudinit.net refactor: is_physical" [Low,Fix committed] <a href="https://launchpad.net/bugs/1884619">https://launchpad.net/bugs/1884619</a></p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> and (LP: #1886531) fix for missing /etc/fstab file path thx rharper</p> -<p>16:59 <code>&lt;ubot5&gt;</code> Launchpad bug 1886531 in cloud-init "cloud-init status broken in groovy lxd containers" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1886531">https://launchpad.net/bugs/1886531</a></p> -<p>17:00 <code>&lt;blackboxsw&gt;</code> and thanks paride for fixing our CI tests for lxd-based targets</p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> I think that about wraps recent-changes.</p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> I was hoping today we'd be able to finally say cloud-init 20.2 has published and released to Ubuntu Xenial. Bionic, Eoan and Focal. All testing is complete, we have unblocked any of this process on our side and we are awaiting an SRU team representative to review and release the bits into Ubuntu proper.</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> We pinged yesterday and a few hour ago again to get this SRU reviewed and released. Expectation is that it will be released to all Ubuntu series today/tonight, so I'd expect that cloud images see that update in the next day or two.</p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> for those watching at home, the folowing bug will be closed as fix-released once cloud-init SRU is published.</p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018</a></p> -<p>17:04 <code>&lt;ubot5&gt;</code> Ubuntu bug 1881018 in cloud-init (Ubuntu) "sru cloud-init (19.4.33 to 20.2-45) Xenial, Bionic, Eoan and Focal" [Undecided,In progress]</p> -<p>17:06 <code>&lt;blackboxsw&gt;</code> for context, this was a beast of an SRU (as upstream waited too long (~6 months) between to get the SRUs, which involved more verification and complexity. We will make sure to avoid some of this complexity in the future by more frequent SRUs and more requests for community validation I expect.</p> -<p>17:07 <code>&lt;blackboxsw&gt;</code> Also, expect that when this SRU is published, and email will be sent to cloud-init@lists.launchpad.net and a discourse post as well as a "community-notice:" banned comment</p> -<p>17:08 <code>&lt;blackboxsw&gt;</code> #topic Community Charter</p> -<p>17:08 <code>&lt;blackboxsw&gt;</code> Community driven development is what helps keep cloud-init active, so that you all for your contributions ( PR reviews, bugs, PR development, discussion etc).</p> -<p>17:09 <code>&lt;blackboxsw&gt;</code> we have a number of general goals we continue to work toward:</p> -<p>17:10 <code>&lt;blackboxsw&gt;</code> - json schema coverage of cloudinit.config.cc_* modules for better error reporting on malformed user-data</p> -<p>17:10 <code>&lt;blackboxsw&gt;</code> - datasource documentation updates and content creation needs</p> -<p>17:10 <code>&lt;blackboxsw&gt;</code> - cloudinit.net refactor into distro-specific networking subclasses cloudinit.distros.networking</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> Bugs associated with that work are available for anyone to own</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> #link k <a href="https://bugs.launchpad.net/cloud-init/">https://bugs.launchpad.net/cloud-init/</a>?field.tag=bitesize</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=net-refactor</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> And details docs on existing refactor are available here</p> -<p>17:12 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloudinit.readthedocs.io/en/latest/topics/hacking.html#ongoing-refactors">https://cloudinit.readthedocs.io/en/latest/topics/hacking.html#ongoing-refactors</a></p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> If anyone would like to be involved more than they currently are, please feel free to contact us here in IRC #cloud-init on Freenode or on the mailing list cloud-init@lists.launchpad.net and we can see how best we can get you "set up"</p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> This 'section' of the meeting is a time where a couple of upstream devs will be available in channel for any discussions, questions, bug work or PR reviews.</p> -<p>17:14 <code>&lt;blackboxsw&gt;</code> any topics, bugs, PRs or concerns or rotten fruit to throw are all welcome :). In the absence of dicussion, cloud-init PR reviews are prioritized</p> -<p>17:18 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: can I merge the following as your squashmerge commit message for PR <a href="https://github.com/canonical/cloud-init/pull/466">https://github.com/canonical/cloud-init/pull/466</a> <a href="https://paste.ubuntu.com/p/ZRdq4bYWG7/">https://paste.ubuntu.com/p/ZRdq4bYWG7/</a> I think it fixed LP: #1884626</p> -<p>17:18 <code>&lt;ubot5&gt;</code> Launchpad bug 1884626 in cloud-init "cloudinit.net refactor: wait_for_physdevs" [Low,In progress] <a href="https://launchpad.net/bugs/1884626">https://launchpad.net/bugs/1884626</a></p> -<p>17:31 <code>&lt;Odd_Bloke&gt;</code> blackboxsw: You cannot (because I just did ;).</p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> :sad trombone:</p> -<p>17:43 <code>&lt;Odd_Bloke&gt;</code> I just reran the RTD doc build and it passed this time (for anyone else who just got that failure email).</p> -<p>17:50 <code>&lt;blackboxsw&gt;</code> Ok I think that about wraps the status meeting</p> -<p>17:50 <code>&lt;blackboxsw&gt;</code> thanks for tuning in folks</p> -<p>17:50 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2020-06-30T16:22:00+00:002020-06-30T16:22:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2020-06-30:/status-2020-06-30.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 30 Jun at 16:22 &mdash; 17:51 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-06-30-16.22.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-06-30-16.22.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-06-16.html#status-2020-06-16">https://cloud-init.github.io/status-2020-06-16.html#status-2020-06-16</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:28 …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 30 Jun at 16:22 &mdash; 17:51 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-06-30-16.22.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-06-30-16.22.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-06-16.html#status-2020-06-16">https://cloud-init.github.io/status-2020-06-16.html#status-2020-06-16</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:28.</p> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:31.</p> -<ul> -<li><strong>LINK</strong>: ACTION: mailing list email requesting comment/concerns about a refactor of startup services</li> -<li><strong>LINK</strong>: <a href="https://paste.ubuntu.com/p/fSvwRks86z/">https://paste.ubuntu.com/p/fSvwRks86z/</a> </li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:34.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloudinit.readthedocs.io/en/latest/topics/hacking.html#ongoing-refactors">https://cloudinit.readthedocs.io/en/latest/topics/hacking.html#ongoing-refactors</a> </li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=net-refactor </li> -<li><strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pull/457">https://github.com/canonical/cloud-init/pull/457</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:49.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018</a> </li> -</ul> -<h3>community charter</h3> -<p>The discussion about "community charter" started at 17:02.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/">https://bugs.launchpad.net/cloud-init/</a>?field.tag=bitesize </li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=net-refactor </li> -</ul> -<h3>Office Hours (~20 mins)</h3> -<p>The discussion about "Office Hours (~20 mins)" started at 17:08.</p> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (73)</li> -<li>meetingology (4)</li> -<li>ubot5 (1)</li> -<li>rharper (1)</li> -<li>smoser (0)</li> -<li>Odd_Bloke (0)</li> -</ul> -<h2>Full Log</h2> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #startmeeting cloud-init status meeting</p> -<p>16:22 <code>&lt;meetingology&gt;</code> Meeting started Tue Jun 30 16:22:42 2020 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:22 <code>&lt;meetingology&gt;</code> </p> -<p>16:22 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> community notice: time for another bi-weekly (or semi-monthly if you prefer) cloud-init community status meeting</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> #chair smoser rharper Odd_Bloke</p> -<p>16:24 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw rharper smoser</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> welcome to another round of cloud-init upstream updates and discussion. We use this meeting as a time to gather to discuss current development of cloud-init, ask and answer questions, and generally expedite development be unblocking devs. All questions. side-conversations and interruptions are welcome</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> last meeting minutes are at the link below</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2020-06-16.html#status-2020-06-16">https://cloud-init.github.io/status-2020-06-16.html#status-2020-06-16</a></p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> turns out I didn't update the topic for the next meeting time last session. Let's do that now</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> +2 weeks from now, same time</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> July 14th, same UTC time</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> now that that's out of the way, we typically cover the following topics.</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> Previous Actions, Recent Changes, In-progress Development, Community Charter, Office Hours (~30 mins).</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> additionally today, I'll discuss the current cloud-init SRU</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> topic #1. our previous meeting minutes logged two actions:</p> -<p>16:28 * blackboxsw file feature bug about refactoring startup services</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> I think in further discussion during last meeting, we talked with Odd_Bloke and meena and determined that we can't actually refactor startup services to live in the distro specifically, because these startup service templates actually get determined at cloud-init generator time (before distribution is determined in cloud-init's python code) so trying to specialize startup script content generation in the distro</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> python classes in cloud-init is too late</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> so this action is tabled as /wont-fix</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> that follows as well with the other ACTION: mailing list email requesting comment/concerns about a refactor of startup services</p> -<p>16:31 * blackboxsw isn't sure how to close out actions in meetingology syntax/cmds</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> The following is the set of commits landed in 'master' of cloud-init upstream repo: found with git log --since 06-20-2020</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> #link ACTION: mailing list email requesting comment/concerns about a refactor of startup services</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> #link <a href="https://paste.ubuntu.com/p/fSvwRks86z/">https://paste.ubuntu.com/p/fSvwRks86z/</a></p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> heh paste error</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:34 * blackboxsw sets appropriate topic for this section</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> so recently Odd_Bloke and a number of BSD folks (meena igalic etc) have gone through a number of discussions and design regarding a refactor of cloudinit.net functions to a cloudinit.distro.networking module as most network-related functionality is highly distro-dependent</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: created an overview of this current refactor work and published it to readthedocs</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloudinit.readthedocs.io/en/latest/topics/hacking.html#ongoing-refactors">https://cloudinit.readthedocs.io/en/latest/topics/hacking.html#ongoing-refactors</a></p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> This has been a big effort to get organized and started so many thanks for all those paricipating in this discussion, development and reviews.</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> there are many, functions that need to be refactored from cloudinit.net into the distribution-specialized cloudinit.distro.networking classes.</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> It is work that can be easily done in parallel and there is a tag used to classify each refactor as a "net-refactor" bug in launchpad</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=net-refactor</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> community notice: we encourage anyone interested in refactoring cloud-init networking functionality to grab and work any of those net-refactor bugs</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> there are a couple of example PRs up that give a good idea of how to get started</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> #link <a href="https://github.com/canonical/cloud-init/pull/457">https://github.com/canonical/cloud-init/pull/457</a></p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> and I can't seem to find the other at the moment.</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> besides net-refactor content landing, there have been fixes to Hetzner and RbxCloud datasources, redhat's systemd generator templates, Centos copr build fixes to help RPM build runs and Azure datasource logging. Thanks smoser, paride Moustafa and otubo Adam Dobrawy for contributions this round</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> Generally the last two weeks have been sunk into upstream testing and validation of cloud-init for SRU (Stable release Update) into Ubuntu Xenial Bionic, Eoan and Focal.</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> 3 to 5 of us have been on verification tasks on various clouds for all Ubuntu releases targeted and all features which affect ubuntu.</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> A thousand thanks rharper Odd_Bloke factor lucasmoura and xiaofeng for working through and validating some of these SRU tasks.</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> Our job is done, and we are awaiting feedback from an automation CI from Canonical solutions QA at the moment which runs through a ton of Openstack networking customer-configurations. It has been in the test queue for a week, and I just saw a successful run from that test harness this morning. That team has told us it looks for 3 successful runs to "pass" so I expect that pass to come shortly as the test runs</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> are currently inprogress.</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> as soon as this test passes we will mark the SRU bug verified and the SRU team will publish bits of cloud-init.</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018</a></p> -<p>16:55 <code>&lt;ubot5&gt;</code> Ubuntu bug 1881018 in cloud-init (Ubuntu) "sru cloud-init (19.4.33 to 20.2-45) Xenial, Bionic, Eoan and Focal" [Undecided,In progress]</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> This SRU has taken about 1+ week longer than normal verification because we hadn't SRU'd cloud-init in around 6 months, so there was a lot more content to verify.</p> -<p>16:57 <code>&lt;blackboxsw&gt;</code> Hopefully additional SRUs will be more frequent and less heavy-weight. We are looking into reducing the overhead on this process and will pitch ideas to the cloud-init mailinglist for input</p> -<p>16:57 <code>&lt;blackboxsw&gt;</code> Beyond SRU work, the following other work is in progress:</p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> * net-refactor formerly mentioned</p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> * falcojr into Oracle integration test harness</p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> * extending json schema validation for remaining cloud-config modules for better error reporting around invalid user-data</p> -<p>17:00 <code>&lt;blackboxsw&gt;</code> Long term work: cloud-init standalone daemon to improve startup time by avoiding reloading python across each cloud-int boot stage, initial networking hot-plug support to which datasources could "opt-in"</p> -<p>17:01 <code>&lt;rharper&gt;</code> blackboxsw: =)</p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> I think that about wraps this topic.</p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> yeah rharper, we've got it on our roadmap. We'd love to see that get in this round.</p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> #topic community charter</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> We have a couple of general themes of features we are working toward as a community this year:</p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> * json schema additions for cloudinit.config.cc_* modules to improve user-facing errors on invalid user-data</p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> * datasource documentation improvements, updates and corrections</p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> * cloudinit.net-refactor work</p> -<p>17:05 <code>&lt;blackboxsw&gt;</code> We encourage any interested developers to grab any of these work items related to these features.</p> -<p>17:06 <code>&lt;blackboxsw&gt;</code> We have two bug tags which enumerate each component of these work streams:</p> -<p>17:07 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/">https://bugs.launchpad.net/cloud-init/</a>?field.tag=bitesize</p> -<p>17:07 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=net-refactor</p> -<p>17:08 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (~20 mins)</p> -<p>17:08 <code>&lt;blackboxsw&gt;</code> This 'section' of the meeting is a time where a couple of upstream devs will be available in channel for any discussions, questions, bug work or PR reviews.</p> -<p>17:08 <code>&lt;blackboxsw&gt;</code> I think I spent most of the time typing, but will hit the review queue in the absence of any other discussion</p> -<p>17:17 <code>&lt;blackboxsw&gt;</code> merged <a href="https://github.com/canonical/cloud-init/pull/461">https://github.com/canonical/cloud-init/pull/461</a></p> -<p>17:51 <code>&lt;blackboxsw&gt;</code> lucasmoura: one minor change request and description update on the PR requested <a href="https://github.com/canonical/cloud-init/pull/390#pullrequestreview-440241947">https://github.com/canonical/cloud-init/pull/390#pullrequestreview-440241947</a></p> -<p>17:51 <code>&lt;blackboxsw&gt;</code> then we can land this one</p> -<p>17:51 <code>&lt;blackboxsw&gt;</code> ok folks, thanks for checking into the cloud-init status meeting. See you in 2 weeks.</p> -<p>17:51 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2020-06-16T16:21:00+00:002020-06-16T16:21:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2020-06-16:/status-2020-06-16.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 16 Jun at 16:21 &mdash; 17:58 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-06-16-16.21.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-06-16-16.21.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:24.</p> -<h3>In-progress Development</h3> -<p>The …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 16 Jun at 16:21 &mdash; 17:58 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-06-16-16.21.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-06-16-16.21.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:24.</p> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:32.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018</a> </li> -<li><strong>LINK</strong>: </li> -<li><strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pull/391">https://github.com/canonical/cloud-init/pull/391</a> </li> -<li><strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pull/416#issuecomment-640032968">https://github.com/canonical/cloud-init/pull/416#issuecomment-640032968</a> </li> -<li><strong>ACTION</strong>: file feature bug about refactoring startup services</li> -<li><strong>ACTION</strong>: mailing list email requesting comment/concerns about a refactor of startup services</li> -</ul> -<h3>community charter</h3> -<p>The discussion about "community charter" started at 16:54.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/">https://bugs.launchpad.net/cloud-init/</a>?field.tag=bitezise </li> -</ul> -<h3>Office Hours (~next 30 minutes)</h3> -<p>The discussion about "Office Hours (~next 30 minutes)" started at 16:59.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_puppet.py#L106">https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_puppet.py#L106</a> could this be entirely puppet specific, and no other module does this dance?</li> -<li><strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/blob/master/cloudinit/reporting/events.py#L84">https://github.com/canonical/cloud-init/blob/master/cloudinit/reporting/events.py#L84</a> </li> -<li><strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_rsyslog.py#L210">https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_rsyslog.py#L210</a> one more</li> -</ul> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (61)</li> -<li>meena (6)</li> -<li>meetingology (6)</li> -<li>AnhVoMSFT (2)</li> -<li>ubot5 (1)</li> -<li>cyberpear (1)</li> -<li>Odd_Bloke (1)</li> -<li>smoser (0)</li> -<li>rharper (0)</li> -</ul> -<h2>Full Log</h2> -<p>16:21 <code>&lt;blackboxsw&gt;</code> #startmeeting cloud-init status meeting</p> -<p>16:21 <code>&lt;meetingology&gt;</code> Meeting started Tue Jun 16 16:21:42 2020 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:21 <code>&lt;meetingology&gt;</code> </p> -<p>16:21 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #chair smoser Odd_Bloke rharper</p> -<p>16:22 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw rharper smoser</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> Welcome to the bi-weekly cloud-init status meeting. A place to chat about upstream cloud-init activity/</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> his meeting is a welcome place for interruptions, questions, requests and unrelated discussions at any point.</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> <em>this</em></p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> previous meeting minutes are stored on github</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> The topics we generally cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Office Hours (~30 mins).</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> From the previous meeting we captured no actions, so I'll jump into the next topic</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> the following are commits merged into cloud-init's upstream master branch: <a href="https://paste.ubuntu.com/p/WdsZXbwwWd/">https://paste.ubuntu.com/p/WdsZXbwwWd/</a></p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> found via git log --since 06-02-2020</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> notable changes: util.runparts and subp out of util into subp.py, there are a couple of branches related to improved vmware support, and resolving keyerror issues for users providing network configuration with bridges.</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> also upstream travis CI is now using the commercial travis-ci.com instead of travis-ci-org which should give us better throughput on test runs.</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> community notice: if any PRs created &gt;` 1 week ago have problems with unresolved travis ci runs marked 'in progress' those PRs will likely need to be closed and re-submitted due to the shift in travis-ci endpoints.</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> Upstream devs are currently working our way through Ubuntu StableReleaseUpdate (SRU) validation to release cloud-init version 20.2.45 to Ubuntu Xenial, Bionic, Eoan and Focal. Thanks falcojr lucasmoura and Odd_Bloke for all the help generating test cases and reviewing SRU-related content.</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> We are about halfway through out testing of this release of cloud-init and expect to be able to wrap this up before next week.</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> To track this release, anyone can subscribe to the SRU process bug</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018</a></p> -<p>16:35 <code>&lt;ubot5&gt;</code> Ubuntu bug 1881018 in cloud-init (Ubuntu) "sru cloud-init (19.4.33 to 20.2-45) Xenial, Bionic, Eoan and Focal" [Undecided,In progress]</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> that bug will go to Fix Released when our upload to <code>&lt;ubuntu-release&gt;</code>-updates apt pocket is published</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> Beyond SRU, there is a significant refactor of cloudinit.net* module to define a clear API and push distro-specific content into the distro modules.</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> #link</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> #link <a href="https://github.com/canonical/cloud-init/pull/391">https://github.com/canonical/cloud-init/pull/391</a></p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> Thanks Odd_Bloke for driving that refactor. Those interested should check out the above PR</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> I think that about wraps it.</p> -<p>16:40 <code>&lt;meena&gt;</code> during the util.subp refactor i suggested also looking into centralising service enabling and (re) starting</p> -<p>16:41 <code>&lt;meena&gt;</code> but we kinda glossed over that because of the net refactor</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> meena: good chance to bring that up: let's get that comment link</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> #link <a href="https://github.com/canonical/cloud-init/pull/416#issuecomment-640032968">https://github.com/canonical/cloud-init/pull/416#issuecomment-640032968</a></p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> meena: your comment was really about re-organizing the ./systemd ./upstart top-level directories and refactoring down into the distros somehow?</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> as that startup service construct is highly distro dependent?</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> If that's the suggestion you are raising for comment, I think it sounds like a reasonable thing to consider. Each distro has it's own way of handling system service management.</p> -<p>16:47 <code>&lt;meena&gt;</code> *nod</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> given the fact that all the systemd/ startup script files are all templates, it indicates that we have a lot of distro-specific uniqueness even across various flavors of linux</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> I think that refactor would be significantly simpler to describe in a distro-level API</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> meena: maybe we file a feature bug against cloud-init so we can prioritize that work.</p> -<p>16:51 <code>&lt;meena&gt;</code> you're right. let's do that</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> we could surface that bug to the mailinglist</p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> meena: do you want to do either of those (bug or mailinglist email: subj: Refactor startup service to distro-specific Api) ?</p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> #action file feature bug about refactoring startup services</p> -<p>16:53 * meetingology file feature bug about refactoring startup services</p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> #action mailing list email requesting comment/concerns about a refactor of startup services</p> -<p>16:53 * meetingology mailing list email requesting comment/concerns about a refactor of startup services</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> I've added actions that we can track by next meeting to see if we can make progress on that discussion</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> ok next topic I think</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> #topic community charter</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> As always, any aspects of the cloud-init project is open for participation from community members.</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> We thank everyone for contributing bugs @ <a href="https://bugs.launchpad.net/cloud-init/+filebug">https://bugs.launchpad.net/cloud-init/+filebug</a>, reviewing open 'New' bugs that are filed, and reviewing pulls requests @ <a href="https://github.com/canonical/cloud-init/pulls">https://github.com/canonical/cloud-init/pulls</a></p> -<p>16:57 <code>&lt;blackboxsw&gt;</code> all reviews are welcome on any PRs that are up. and driving feature discussions are also encouraged. Thanks meena for participating on all of those fronts</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> for those just wanting to join in and contribute small pull requests there is a queue of bugs or features that should be a fairly contained set of tasks in our bitesize queue:</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/">https://bugs.launchpad.net/cloud-init/</a>?field.tag=bitezise</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (~next 30 minutes)</p> -<p>17:00 <code>&lt;blackboxsw&gt;</code> This 'section' of the meeting is a time where a couple of upstream devs will be available in channel for any discussions, questions, bug work or PR reviews.</p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> In the absence of discussion topics, reviewing the active PRs generally occurs to scrub our queue and unblock conversations.</p> -<p>17:02 * blackboxsw addresses some review comments on a CI Ubuntu daily test branch</p> -<p>17:22 <code>&lt;AnhVoMSFT&gt;</code> question: is there anyway to only target a particular reporting handler?</p> -<p>17:23 <code>&lt;AnhVoMSFT&gt;</code> Right now the Azure DS emits events to the HyperV KVP handler and they also pass through the log handler. For the most part this is fine (and useful). For some larger event message (like compressed log), it does not make sense to emit a large blob of compressed gzip + b64 to the log, is it possible to skip the log handler ?</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> hrm, good question AnhVoMSFT . looking</p> -<p>17:33 <code>&lt;Odd_Bloke&gt;</code> blackboxsw: meena: Note that the service files are selected at package generation time, not at runtime, so it's not entirely clear to me how you would integrate them into the Distro hierarchy.</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> nice suggestion Odd_Bloke</p> -<p>17:43 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: I'm not seeing any filtering config options in reporting: config for handlers. Are you saying you are looking to add compressed object writes to your kvp message message plane?</p> -<p>17:44 * cyberpear wondering if there's any collaboration with the ignition folks</p> -<p>17:46 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: I think it's be reasonable to provide a named report handler to ReportEventStack</p> -<p>17:46 <code>&lt;blackboxsw&gt;</code> and let ReportEventStack limit what handlers it can emit publish_event to</p> -<p>17:48 <code>&lt;meena&gt;</code> <a href="https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_puppet.py#L106">https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_puppet.py#L106</a> could this be entirely puppet specific, and no other module does this dance?</p> -<p>17:50 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: that'd mean I suppose that report_event would need to accept a new param to limit which handler it calls handler.publish_event for</p> -<p>17:50 <code>&lt;blackboxsw&gt;</code> <a href="https://github.com/canonical/cloud-init/blob/master/cloudinit/reporting/events.py#L84">https://github.com/canonical/cloud-init/blob/master/cloudinit/reporting/events.py#L84</a></p> -<p>17:52 <code>&lt;meena&gt;</code> <a href="https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_rsyslog.py#L210">https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_rsyslog.py#L210</a> one more</p> -<p>17:52 <code>&lt;blackboxsw&gt;</code> or maybe you are suggesting that we add the ability for an existing handler to define a set of data types that it accepts (and will silently ignore others)?</p> -<p>17:54 <code>&lt;blackboxsw&gt;</code> and here meena <a href="https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_fan.py#L55-L83">https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_fan.py#L55-L83</a></p> -<p>17:58 <code>&lt;blackboxsw&gt;</code> ok I've got to run. time to close the meeting for today. Thanks all for joining in!</p> -<p>17:58 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2020-06-02T16:21:00+00:002020-06-02T16:21:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2020-06-02:/status-2020-06-02.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 02 Jun at 16:21 &mdash; 18:08 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-06-02-16.21.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-06-02-16.21.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:24.</p> -<h3>Recent Changes</h3> -<p>The …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 02 Jun at 16:21 &mdash; 18:08 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-06-02-16.21.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-06-02-16.21.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:24.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:27.</p> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:34.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018</a> </li> -</ul> -<h3>Community Charter</h3> -<p>The discussion about "Community Charter" started at 16:47.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/">https://bugs.launchpad.net/cloud-init/</a>?field.tag=bitezise </li> -</ul> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 16:50.</p> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (76)</li> -<li>Odd_Bloke (6)</li> -<li>knaccc (5)</li> -<li>meena (5)</li> -<li>meetingology (4)</li> -<li>rharper (3)</li> -<li>ddstreet (1)</li> -<li>ubot5 (1)</li> -<li>smoser (0)</li> -</ul> -<h2>Full Log</h2> -<p>16:21 <code>&lt;blackboxsw&gt;</code> #startmeeting cloud-init status meeting</p> -<p>16:21 <code>&lt;meetingology&gt;</code> Meeting started Tue Jun 2 16:21:15 2020 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:21 <code>&lt;meetingology&gt;</code> </p> -<p>16:21 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> hi folks, time for another cloud-init upstream status meeting.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> we use this meeting to provide a venue for any cloud-init interested parties to keep up to date on current development, release-related info and expedite distributed development where possible.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> this meeting is a welcome place for interruptions, questions, requests and unrelated discussions at any point. so don't be shy :)</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #chair Odd_Bloke smoser rharper</p> -<p>16:23 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw rharper smoser</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> The topics we generally cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Office Hours (~30 mins).</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> previous meeting minutes live here (and I just saw I forgot to publish last minutes so I pushed them now)</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> nothing actionable brought up in last meeting on 05/19</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: ahh we should fix devel with those pkg drops on next upload</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> we did drop that for Xenial, Bionic Eoan and maybe focal too?</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> so an oversight for groovy</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> next topic</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> the following are commits landed in tip of master found via git log --since 05/19/2020 : <a href="https://paste.ubuntu.com/p/QFvgWhjXY9/">https://paste.ubuntu.com/p/QFvgWhjXY9/</a></p> -<p>16:28 <code>&lt;Odd_Bloke&gt;</code> blackboxsw: When you say "next upload" are you referring to the upload you're about to do, or the one after that?</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: if you'd like we can adjust the current upload so that devel, focal, bionic xenial eoan all drop those stale deps</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> I think X, B E have all dropped them</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> so maybe I re-do ubuntu/devel PR Odd_Bloke ?</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> probably good/better/correct to keep all releases on the same footing.</p> -<p>16:29 <code>&lt;Odd_Bloke&gt;</code> blackboxsw: I think it's worth doing, we've uploaded without fixing it a few times before, and we've remembered this time around.</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> yeah sounds good Odd_Bloke I'll re-do that devel PR (and make sure focal drops it too)</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> if needed</p> -<p>16:30 <code>&lt;Odd_Bloke&gt;</code> And it should just be a case of pushing a new commit to your existing branch.</p> -<p>16:30 <code>&lt;Odd_Bloke&gt;</code> Thanks!</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> +1</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> things of note in the recent commits landed. <a href="https://github.com/canonical/cloud-init/pull/358">https://github.com/canonical/cloud-init/pull/358</a> Mattew Ruffell improved cc_grub_dpkg to be more dynamic in matching disks instead of a hardcoded device list</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> thanks Matthew</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> and chef_license support <a href="https://github.com/canonical/cloud-init/commit/0919bd46bbd1b12158c369569ec1298bb000dd8a">https://github.com/canonical/cloud-init/commit/0919bd46bbd1b12158c369569ec1298bb000dd8a</a></p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> thanks bipinbachhao for the config extension there</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> a couple of new notables in flight at the moment:</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - falcojr: introduction of feature-flags for cloud-init upstream to give us a toggle to retain original behavior of #include failures on stable downstream releases. <a href="https://github.com/canonical/cloud-init/pull/367">https://github.com/canonical/cloud-init/pull/367</a> . Upstream cloud-init will fail loudly and raise an Exception if someone tries to #include a url which fails. this differs from original cloud-init behavior which was to try our best to get a system up</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> and running, even amid not-critical failures</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> per the above, if downstreams (distributiions) would like to retain a more permissive warn on #include user-data issues, a cloudinit/feature_overrides.py file would need to be introduced in the downstream</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> - Also meena and Odd_Bloke and others have been working toward a refactor of cloudinit.net modules. Dan added a doc PR to capture this approach <a href="https://github.com/canonical/cloud-init/pull/391">https://github.com/canonical/cloud-init/pull/391</a></p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> beyond that, there are a number of PRs up from lucas on json schema additions for cloudinit/config/cc_* modules to get better validation of #cloud-config user-data</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> For ubuntu proper, we have started the StableReleaseUpdate process for cloud-init to publish master into ubuntu/xenial, bionic, eoan and focal releases</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> some of these changes will add the opportunity to enable 'new' features on platforms like Azure</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> and AWS</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> Azure (xenial) will be dropping walinuxagent support</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> AWS will now surface a datasource config option apply_full_imds_network_config boolean</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> if set true in an Ec2(aws) image network configuration from cloud-init can come completely from IMDS for every connected NIC. That config will include all secondary IPv4/IPv6 addressses configured for the machine</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> Upstream has started the Ubuntu SRU process (which generally takes around 10-14 days). We plan to include every commit that has landed in tip of master as of commitish 5f7825e22241423322dbe628de1b00289cf34114</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> the bug related to this SRU work is here</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018</a></p> -<p>16:46 <code>&lt;ubot5&gt;</code> Ubuntu bug 1881018 in cloud-init (Ubuntu Focal) "sru cloud-init (19.4.33 to 20.2-30) Xenial, Bionic, Eoan and Focal" [Undecided,New]</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> #topic Community Charter</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> upstream has signed up to get as much of the json schema coverage as we can for cloudinit/config/cc*py modules since invalid #cloud-config user-data formats tends to have one of the highest incidence of errors (because writing YAML is something humans shouldn't have to do :) )</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> so we are chopping away at defining JSON schema for as many cloud config modules as possible . there are still plenty to choose from. Anyone can feel free to grab a JSON schema bug and help us with bettering cloud-init</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> bugs are filed for each config module which needs schema definition:</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/">https://bugs.launchpad.net/cloud-init/</a>?field.tag=bitezise</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> a big thanks to lucasmoura for starting to grab a number of these</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> This 'section' of the meeting is a time where a couple of upstream devs will be available in channel for any discussions, questions, bug work or PR reviews.</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> In the absence of discussions/topics here we scrub the review queue.</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> since we are mid-stream on Ubuntu SRU at the moment, I'll be addressing review comments on some of the functional 'upload' branches we've put together</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> and, let's update the topic for next IRC meeting too while we are at it</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: just pushed ubuntu/devel dropping python3-six|unittest2|nose</p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> and just re-pushed ubuntu/focal to drop python3-six</p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> oops and missed you others. reworking</p> -<p>17:12 <code>&lt;blackboxsw&gt;</code> ok re-pushed. focal and devel PRs in shape</p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> dropped the following build-deps: python3-six, python3-unittest2, python3-pep8, python3-nose, python3-pyflakes</p> -<p>17:20 <code>&lt;Odd_Bloke&gt;</code> blackboxsw: +1 on the ubuntu/devel upload.</p> -<p>17:21 <code>&lt;blackboxsw&gt;</code> whew, think we got all of the dropped deps between the two of us... thanks!</p> -<p>17:21 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: thanks focal looks good and sbuilds</p> -<p>17:21 <code>&lt;blackboxsw&gt;</code> just finished eoan and building now to test</p> -<p>17:23 <code>&lt;meena&gt;</code> what? me??</p> -<p>17:24 <code>&lt;blackboxsw&gt;</code> well yes indeedy meena, just trying to keep you highlighted as participating in the cloud-init status meeting :) you've thankfully reviewed, pushed and prodded us to talk about cloudinit.net refactor and how best to address it I think :) credit due ;)</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> community notice: upload to Ubuntu groovy of cloud-init master accepted [ubuntu/groovy-proposed] cloud-init 20.2-45-g5f7825e2-0ubuntu1 (Accepted)</p> -<p>17:30 <code>&lt;Odd_Bloke&gt;</code> blackboxsw: One issue with <a href="https://github.com/canonical/cloud-init/pull/412">https://github.com/canonical/cloud-init/pull/412</a></p> -<p>17:31 <code>&lt;meena&gt;</code> blackboxsw: i'm just waiting for Odd_Bloke to provide the basic infrastructure so i can start moving code… without that, i have to bug other projects in my … 2 hours of free time per day.</p> -<p>17:31 <code>&lt;meena&gt;</code> blackboxsw: yesterday, i tried to build an android app on my laptop and gave up after an hour.</p> -<p>17:35 <code>&lt;blackboxsw&gt;</code> nice review again Odd_Bloke, will reflect that patch to each series. as every other ubuntu/* is missing enabling various cloud datasources beyond just Rbx</p> -<p>17:54 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: rharper so Xenial is interesting for datasource config via dpkg</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> We are missing: Hetzner, IBMCloud, Oracle, and RbxCloud</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> one was an oversight on previous SRUs</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> but Oracle and IBMCloud, I'm trying to recall if there is a reason we didn't want to surface either of those datasources as configurable on Xenial</p> -<p>17:56 <code>&lt;blackboxsw&gt;</code> a little warning bell is going off in my head</p> -<p>17:56 <code>&lt;blackboxsw&gt;</code> Hetzner I thought was 'ok'</p> -<p>17:56 <code>&lt;blackboxsw&gt;</code> Oracle currently gets detected as OpenStack on Xenial.</p> -<p>17:57 <code>&lt;rharper&gt;</code> IBMCloud and Oracle are sensitive</p> -<p>17:57 <code>&lt;rharper&gt;</code> not sure about Hetzner or RbxCloud though</p> -<p>17:57 <code>&lt;blackboxsw&gt;</code> upstream Oracle datasource is 'good', but I wasn't sure if there was extra baggage associated with <em>not</em> backporting that functionality</p> -<p>17:57 <code>&lt;rharper&gt;</code> blackboxsw: I think you might want to check with CPC on those</p> -<p>17:58 <code>&lt;meena&gt;</code> Hetzner is also detected as OpenStack on FreeBSD… but… only thru cloud-init itself, not thru ds-identify</p> -<p>18:03 <code>&lt;meena&gt;</code> (i'm not sure how much of that is my fault having helped a lot with Hetzner and FreeBSD and ds-identify myself)</p> -<p>18:03 <code>&lt;knaccc&gt;</code> Odd_Bloke thanks for your reply. I managed to fix things in the end, but kinda by cheating. Now my /etc/netplan/50-cloud-init.yaml only contains the IP addresses configuration, and I make the nameservers and search domain apply in the "Global" scope (as reported by systemd-resolve --status) by simply modifying the /etc/resolv.conf file. All configuration survives reboot just fine, and I am no longer</p> -<p>18:03 <code>&lt;knaccc&gt;</code> scared that resolv.conf will be overwritten because I found a web page that said that "Note: The mode of operation of systemd-resolved is detected automatically, depending on whether /etc/resolv.conf is a symlink to the local stub DNS resolver file or contains server names." Although you said in your message that "cloud-init will regenerate /etc/netplan/50-cloud-init.yaml on each boot, so yes, you don't</p> -<p>18:03 <code>&lt;knaccc&gt;</code> want to modify that", the OVH instructions directly contradict that and tell me to edit it to add all IP addresses to my interface (see Ubuntu 18.04 section here: <a href="https://docs.ovh.com/gb/en/vps/network-ipaliasing-vps/">https://docs.ovh.com/gb/en/vps/network-ipaliasing-vps/</a>). I'm therefore very confused about why OVH seem to contradict the instructions that are in that config file, and confused as to what other location I should be editing/creating instead</p> -<p>18:06 <code>&lt;ddstreet&gt;</code> knaccc why do you want to change resolved 'Global' section?</p> -<p>18:08 <code>&lt;blackboxsw&gt;</code> heh meena not at fault :) . Just need to make sure we move cloud-platforms to a better way of detecting the right datasource when we can.</p> -<p>18:08 <code>&lt;knaccc&gt;</code> ddstreet if I put the nameservers and search domain into the /etc/netplan/50-cloud-init.yaml file, it gets ignored completely (i.e. although those configurations show up in systemd-resolve --status against that specific "link", the "Global" nameservers and lack of any search domain in that Global section are taking precedence). Therefore I had to configure nameservers and search domain at the resolv.conf</p> -<p>18:08 <code>&lt;knaccc&gt;</code> level so that it appeared in the Global section, and then suddenly everything worked for the first time</p> -<p>18:08 <code>&lt;blackboxsw&gt;</code> I should tie off our cloud-init status meeting. Thanks folks for all who've attended</p> -<p>18:08 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2020-05-19T16:18:00+00:002020-05-19T16:18:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2020-05-19:/status-2020-05-19.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 19 May at 16:18 &mdash; 18:24 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-05-19-16.18.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-05-19-16.18.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-05-05.html#status-2020-05-05">https://cloud-init.github.io/status-2020-05-05.html#status-2020-05-05</a> </p> -<h3>#cloud-init pull-requests <a href="https://git.io/JeVed">https://git.io/JeVed</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl …</a></h3><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 19 May at 16:18 &mdash; 18:24 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-05-19-16.18.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-05-19-16.18.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-05-05.html#status-2020-05-05">https://cloud-init.github.io/status-2020-05-05.html#status-2020-05-05</a> </p> -<h3>#cloud-init pull-requests <a href="https://git.io/JeVed">https://git.io/JeVed</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting June 16:15 UTC | 20.1 (Feb 18) | 20.2 (Apr 28) | <a href="https://bugs.launchpad.net/cloud-init/+filebug">https://bugs.launchpad.net/cloud-init/+filebug</a></h3> -<p>The discussion about "#cloud-init pull-requests <a href="https://git.io/JeVed">https://git.io/JeVed</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting June 16:15 UTC | 20.1 (Feb 18) | 20.2 (Apr 28) | <a href="https://bugs.launchpad.net/cloud-init/+filebug">https://bugs.launchpad.net/cloud-init/+filebug</a>" started at 16:20.</p> -<h3>#cloud-init pull-requests <a href="https://git.io/JeVed">https://git.io/JeVed</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting June 2 16:15 UTC | 20.1 (Feb 18) | 20.2 (Apr 28) | <a href="https://bugs.launchpad.net/cloud-init/+filebug">https://bugs.launchpad.net/cloud-init/+filebug</a></h3> -<p>The discussion about "#cloud-init pull-requests <a href="https://git.io/JeVed">https://git.io/JeVed</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting June 2 16:15 UTC | 20.1 (Feb 18) | 20.2 (Apr 28) | <a href="https://bugs.launchpad.net/cloud-init/+filebug">https://bugs.launchpad.net/cloud-init/+filebug</a>" started at 16:20.</p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:21.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:22.</p> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:27.</p> -<h3>Community Charter</h3> -<p>The discussion about "Community Charter" started at 16:39.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/">https://bugs.launchpad.net/cloud-init/</a>?field.tag=bitezise </li> -</ul> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 16:44.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://pastebin.com/TG4E8Dft">https://pastebin.com/TG4E8Dft</a> 19.4-33 (latest 18.04 image on Azure)</li> -</ul> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (52)</li> -<li>AnhVoMSFT (8)</li> -<li>meetingology (4)</li> -<li>meena (3)</li> -<li>Odd_Bloke (2)</li> -<li>smoser (0)</li> -<li>rharper (0)</li> -</ul> -<h2>Full Log</h2> -<p>16:18 <code>&lt;blackboxsw&gt;</code> #startmeeting cloud-init status meeting</p> -<p>16:18 <code>&lt;meetingology&gt;</code> Meeting started Tue May 19 16:18:05 2020 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:18 <code>&lt;meetingology&gt;</code> </p> -<p>16:18 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> #chair Odd_Bloke smoser rharper</p> -<p>16:18 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw rharper smoser</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> hello cloud-init, welcome to another round cloud-init status updates</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> our IRC channel topic carries the next planned status meeting for those that wish to participate. All are welcome to interject or drive converstation topics here</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> Previous meeting notes are here</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2020-05-05.html#status-2020-05-05">https://cloud-init.github.io/status-2020-05-05.html#status-2020-05-05</a></p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> and next status meeting should be in 2 weeks time.</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> looks like June 2. I'll set the topic of this irc channel to so that dropins can see a reminder for when that meeting is held</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #topic #cloud-init pull-requests <a href="https://git.io/JeVed">https://git.io/JeVed</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting June 16:15 UTC | 20.1 (Feb 18) | 20.2 (Apr 28) | <a href="https://bugs.launchpad.net/cloud-init/+filebug">https://bugs.launchpad.net/cloud-init/+filebug</a></p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #topic #cloud-init pull-requests <a href="https://git.io/JeVed">https://git.io/JeVed</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting June 2 16:15 UTC | 20.1 (Feb 18) | 20.2 (Apr 28) | <a href="https://bugs.launchpad.net/cloud-init/+filebug">https://bugs.launchpad.net/cloud-init/+filebug</a></p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> let's try that instead</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> The topics we generally cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter and Office Hours (~30 mins).</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> I'll jump through each topic, as always interjections, questions or other topics welcome</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> Nothing brought up as an action in the last meeting so we'll jump to the next topic</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> The following changes have landed in master; found via git log --since 05-05-2020 <a href="https://paste.ubuntu.com/p/d2qR8pTZNY/">https://paste.ubuntu.com/p/d2qR8pTZNY/</a></p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> there are a number of commits landed related to dropping additional py2 support from various paths as well as improving pytest fixtures (thx OddBloke) and some json schema definitions added to cc_snap and cc_apt_configure thanks lucasmoura</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> and an additional bit of work from meena to make libc discovery platform independent</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> Current themes of work for upstream include: continuing to refine a spec on cloud-init daemon mode and hot-plug support, purging python2-isms, improving pytest automation.</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> falcojr: also has a new approach for feature flag definitions/behavior in cloud-init in <a href="https://github.com/canonical/cloud-init/pull/367">https://github.com/canonical/cloud-init/pull/367</a> This should give us the ability to better codify upstream unconfiguraable cloud-init behavior which may differ on previous releases.</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> falcojr: Odd_Bloke &amp; smoser thanks for good design discussion there. anyone interested feel free to weigh in.</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> Also in-progress work is a cloud-init StableReleaseUpdate planned to publish cloud-init version 20.2 to xenial, bionic, eoan and focal.</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> This will publish latest cloud-init (after verification) to old stable releases</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> the first step before SRU is to upload latest cloud-init to Ubuntu Groovy(20.10). Once this upload is complete, we'll start the SRU process to publish to Xenial, Bionic, Eoan and Focal</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> #topic Community Charter</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> As discussed at the last cloud-init summit we targeted a couple of streams of work that are easy to work in parallel, making them prime candidates for community involvement.</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> Those streams/themes are: updating and correcting datasource documentation at <a href="https://cloudinit.readthedocs.io/en/latest/topics/datasources.html">https://cloudinit.readthedocs.io/en/latest/topics/datasources.html</a></p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> and adding jsonschema definitions to any cloudinit.config.cc_* modules</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> any of these bugs are categorized as 'bitesize' and can be searched at the following link</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/">https://bugs.launchpad.net/cloud-init/</a>?field.tag=bitezise</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> a few of us have grabbed schema definitions for a few of the cloud config modules. I think we are up to 11 modules covered (of 50). Thanks all for the progress there. We have it on our roadmap to flesh out as much as we can</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> During this part of the meeting upstream devs should have eyes on the channel for any discussion related to feature, bug or review requests.</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> In the absence of active discussions, the active review queue will be be groomed.</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> for me, I've got to read through <a href="https://github.com/canonical/cloud-init/pull/367">https://github.com/canonical/cloud-init/pull/367</a> in depth to see if I have any use-cases to add there for feature management</p> -<p>17:21 <code>&lt;blackboxsw&gt;</code> so, yeah sorry for the noise Odd_Bloke and falcojr in standup about whether this 'feature' is runtime configurable on/off. It doesn't even make sense for this #include case. Also I think the merits of falcojr's suggestion to rely on some unique environment variable to determine whether a feature is on or off can and should be encoded in cloud-init proper, instead of relying on patching when releasing to</p> -<p>17:21 <code>&lt;blackboxsw&gt;</code> ubuntu/xenial.</p> -<p>17:22 <code>&lt;blackboxsw&gt;</code> when we add a new 'feature' to cloud-init upstream. I believe we know what our expectations are for older stable releases at that time. We generally could encode those expectations (at least for ubuntu series which we maintain) that a feature should behave a certain way when we end up releasing to ubuntu/xenial. Avoiding the RELEASE_BLOCKER comment as a reminder for us to manually patch a release wouldn't be</p> -<p>17:22 <code>&lt;blackboxsw&gt;</code> necessary in these cases.</p> -<p>17:26 <code>&lt;AnhVoMSFT&gt;</code> q question: when I specify a custom data to format/partition the datadisk, it seems like the ephemeral resource disk isn't getting formatted to ext4 anymore. Is this by-design that when the customer specifies disk_setup and fs_setup for additional datadisk they need to also include the fs_setup for ephemeral0 (it seems odd because disk_setup got "merged" properly. I could see the ephemeral0</p> -<p>17:26 <code>&lt;AnhVoMSFT&gt;</code> got partitioned. Yet fs_setup isn't).</p> -<p>17:27 <code>&lt;AnhVoMSFT&gt;</code> I am not sure if this is an appropriate topic for Office Hours. I can wait :-)</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: thx for the question. so, what version of cloud-init and what's the user-data for partitioning that is isn't working as expected?</p> -<p>17:31 <code>&lt;AnhVoMSFT&gt;</code> <a href="https://pastebin.com/TG4E8Dft">https://pastebin.com/TG4E8Dft</a> 19.4-33 (latest 18.04 image on Azure)</p> -<p>17:33 <code>&lt;AnhVoMSFT&gt;</code> (paste.ubuntu has been giving me problems today - not sure if it's only me)</p> -<p>17:49 <code>&lt;meena&gt;</code> blackboxsw: no mention of my work on the net refactoring or did i miss that</p> -<p>17:53 <code>&lt;blackboxsw&gt;</code> meena: sorry, right that is a large undertaking that you've raised via your PR <a href="https://github.com/canonical/cloud-init/pull/363">https://github.com/canonical/cloud-init/pull/363</a></p> -<p>17:55 <code>&lt;meena&gt;</code> yeah, it's my: please teach my software engineering while all i do is code monkeying PR.</p> -<p>17:55 <code>&lt;meena&gt;</code> don't tell no one tho, or else they… might not.</p> -<p>17:58 <code>&lt;Odd_Bloke&gt;</code> blackboxsw: Could you comment on the PR where we're having that feature flag conversation, please?</p> -<p>17:58 <code>&lt;blackboxsw&gt;</code> Heh, generally the direction meena is going is toward distro-specific networking subclass to handle network rendering details (as most of our network rendering utility functions are highly distro-dependent</p> -<p>17:59 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: yes, I shall.</p> -<p>17:59 <code>&lt;Odd_Bloke&gt;</code> Thanks!</p> -<p>18:06 <code>&lt;blackboxsw&gt;</code> Ok, I forgot to close out the meeting.</p> -<p>18:07 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: so I see your instance is properly "waiting" for the presence of ephemeral0 resource disk. trying to get to the bottom of why formatting isn't being addressed there.</p> -<p>18:10 <code>&lt;blackboxsw&gt;</code> I see 2020-05-19 17:20:24,072 - cc_mounts.py[DEBUG]: Mapped metadata name ephemeral0 to /dev/disk/cloud/azure_resource</p> -<p>18:10 <code>&lt;blackboxsw&gt;</code> 2020-05-19 17:20:24,073 - cc_mounts.py[DEBUG]: changed default device ephemeral0 =&gt;` /dev/disk/cloud/azure_resource-part1</p> -<p>18:16 <code>&lt;AnhVoMSFT&gt;</code> @blackboxsw this is reproducing 100% of the time</p> -<p>18:17 <code>&lt;blackboxsw&gt;</code> I'm wondering AnhVoMSFT if the ephemeral0 alias needs to be used instead. something like <a href="https://paste.ubuntu.com/p/7wmMc8drZ3/">https://paste.ubuntu.com/p/7wmMc8drZ3/</a></p> -<p>18:19 <code>&lt;blackboxsw&gt;</code> I see we've done SRU testing referencing that alias instead of full resource disk path <a href="https://github.com/cloud-init/ubuntu-sru/blob/master/bugs/b59870ca.txt">https://github.com/cloud-init/ubuntu-sru/blob/master/bugs/b59870ca.txt</a></p> -<p>18:23 <code>&lt;AnhVoMSFT&gt;</code> @blackboxsw, my config is actually having an EXTRA datadisk</p> -<p>18:23 <code>&lt;AnhVoMSFT&gt;</code> so in this case the VM is deployed with an additional data disk attached to the VM</p> -<p>18:24 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2020-05-05T16:16:00+00:002020-05-05T16:16:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2020-05-05:/status-2020-05-05.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 05 May at 16:16 &mdash; 17:34 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-05-05-16.16.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-05-05-16.16.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:20.</p> -<h3>Recent Changes</h3> -<p>The …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 05 May at 16:16 &mdash; 17:34 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-05-05-16.16.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-05-05-16.16.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:20.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:20.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://paste.ubuntu.com/p/YMb2Tw3tRD/">https://paste.ubuntu.com/p/YMb2Tw3tRD/</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:26.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pulls">https://github.com/canonical/cloud-init/pulls</a> </li> -</ul> -<h3>Community Charter</h3> -<p>The discussion about "Community Charter" started at 16:30.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=bitesize </li> -</ul> -<h3>Office hours (next ~30 mins)</h3> -<p>The discussion about "Office hours (next ~30 mins)" started at 16:33.</p> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (38)</li> -<li>meetingology (4)</li> -<li>rharper (0)</li> -<li>Odd_Bloke (0)</li> -<li>smoser (0)</li> -</ul> -<h2>Full Log</h2> -<p>16:16 <code>&lt;blackboxsw&gt;</code> #startmeeting cloud-init status meeting</p> -<p>16:16 <code>&lt;meetingology&gt;</code> Meeting started Tue May 5 16:16:41 2020 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:16 <code>&lt;meetingology&gt;</code> </p> -<p>16:16 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> good morning, afternoon and evening folks. Welcome to another cloud-init status meeting.</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> #chair Odd_Bloke smoser rharper</p> -<p>16:17 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw rharper smoser</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> our IRC channel topic carries the next planned status meeting for those that wish to participate. All are welcome to interject or drive converstation topics here</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> I'll set the next status meeting topic while we are thinking about it.</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> 2 weeks from today, same time 16:15 UTC.</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> May 19th it is.</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> Previous meeting minutes live over on github</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> The topics we generally cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Upcoming Meetings, Office Hours (~30 mins).</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> Looks like no unresolved actions from last meeting</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> Below is a list of commits that have landed in tip of master: found via git log --since 2020-03-10</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #link <a href="https://paste.ubuntu.com/p/YMb2Tw3tRD/">https://paste.ubuntu.com/p/YMb2Tw3tRD/</a></p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> We've had a number of milestones since the last status meeting, Ubuntu Focal Fossa 20.04 was released on Apr 23, cloud-init upstream cut a release 20.2 as well</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> Additionally we have two new hires to the canonical ubuntu-server team that will be participating in cloud-init, curtin and ubuntu-advantage-tools projects</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> We are really excited to have some extra hands on cloud-init from lucasmoura and falcojr. So welcome gentlemen, glad to have the help.</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> They just started yesterday and are going through a bit of onboarding this week, but expect to see them around in cloud-init shortly. I believe they have both landed their first PRs to get added as a contributor to cloud-init.</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> #link <a href="https://github.com/canonical/cloud-init/pulls">https://github.com/canonical/cloud-init/pulls</a></p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> ok active review queue is really getting well maintained now that we've adopted PR assignment. Thanks for helping is land branches quickly folks.</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> Generally upstream has set a couple of long-term goals for cloud-init in the next development cycle</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - wrap up cloud-init daemon mode (to reduce boot time by loading python only once)</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - OpenStack network hotplug handling from cloud-init</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> - Potentially a new LXD datasource for handling container deployments</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> - better json schema coverage for the remaining oncovered cloud config modules.</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> #topic Community Charter</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> We continue to categorize more bitesize bugs in cloud-init.</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=bitesize</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> These bugs are themed at doc updates and json schema improvements across all of cloud-init, but we continue to seed that bug tag with items which should be easy to drop in and make a lasting impact on cloud-init</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> All cloud-init contributors are encouraged to participate in any part of the cloud-init lifecycle, from bug filing, to fixing, to release testing and PR reviews. Thanks to everyone who continues to build the cloud-init community!</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> #topic Office hours (next ~30 mins)</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> During this stage we have a some focus time on cloud-init development and community support. Any questions, concerns, reviews or request for help/triage are most welcome. We should have a couple of upstream developers with eyes on this channel.</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> In the absence of discussion, we'll groom the active PR review queue and/or work additional cloud-init dev items.</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> community-notice: Ubuntu plans to release cloud-init version 20.2 to Ubuntu's new development release 20.10 (Groovy Gorilla). We expect to start an Ubuntu StableReleaseUpdate into xenial, bionic, eoan and focal within the next 2 weeks.</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> alrighty, think that about wraps today's status meeting. Happy Cinco De Mayo folks</p> -<p>17:34 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2020-04-14T16:17:00+00:002020-04-14T16:17:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2020-04-14:/status-2020-04-14.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 14 Apr at 16:17 &mdash; 17:12 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-04-14-16.17.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-04-14-16.17.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-03-31.html#status-2020-03-31">https://cloud-init.github.io/status-2020-03-31.html#status-2020-03-31</a> </p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:23 …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 14 Apr at 16:17 &mdash; 17:12 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-04-14-16.17.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-04-14-16.17.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-03-31.html#status-2020-03-31">https://cloud-init.github.io/status-2020-03-31.html#status-2020-03-31</a> </p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:23.</p> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:27.</p> -<h3>Office hours (next ~30 mins)</h3> -<p>The discussion about "Office hours (next ~30 mins)" started at 16:34.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://github.com/CanonicalLtd/uss-tableflip/pull/45">https://github.com/CanonicalLtd/uss-tableflip/pull/45</a> I think comments are resolved</li> -</ul> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (38)</li> -<li>meetingology (6)</li> -<li>powersj (2)</li> -<li>Goneri (2)</li> -<li>otubo (1)</li> -<li>punkgeek (1)</li> -<li>rharper (1)</li> -<li>smoser (0)</li> -<li>powers (0)</li> -<li>Odd_Bloke (0)</li> -</ul> -<h2>Full Log</h2> -<p>16:17 <code>&lt;blackboxsw&gt;</code> #startmeeting cloud-init status meeting</p> -<p>16:17 <code>&lt;meetingology&gt;</code> Meeting started Tue Apr 14 16:17:46 2020 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:17 <code>&lt;meetingology&gt;</code> </p> -<p>16:17 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> hey folks, time for cloud-init community status meeting</p> -<p>16:19 <code>&lt;powersj&gt;</code> \o/</p> -<p>16:19 <code>&lt;otubo&gt;</code> Right on time :-)</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> welcome again to our bi-weekly status meeting feel free to interject comments, questions, suggestions during this status meeting. Generally it is an opportunity for upstream to provide a frequent platform communication and drop-in discussion when a couple of upstream devs are available.</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #chair Odd_Bloke smoser rharper powers</p> -<p>16:20 <code>&lt;meetingology&gt;</code> Warning: Nick not in channel: powers</p> -<p>16:20 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw powers rharper smoser</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #chair powersj</p> -<p>16:20 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw powers powersj rharper smoser</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> our IRC channel topic carries the next planned status meeting for those that wish to participate. All are welcome to interject or drive converstation topics here</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> any objections to same time on Apr 28th?</p> -<p>16:21 <code>&lt;powersj&gt;</code> nah that's a good day given we want to cut 20.2 then</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> ok topic set for next meetin</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> our last meeting minutes can be found on github at</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2020-03-31.html#status-2020-03-31">https://cloud-init.github.io/status-2020-03-31.html#status-2020-03-31</a></p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> The topics we generally cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Upcoming Meetings, Office Hours (~30 mins).</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> none listed from last meeting</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> git commits landed in tip since Mar 31: <a href="https://paste.ubuntu.com/p/VptqRBfVfJ/">https://paste.ubuntu.com/p/VptqRBfVfJ/</a> found by git log --since 03-31-2020</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> changes sport doc updates, otubo's cc_mount fix , better url handling for regions which contain underscores in their name and openbsd fixes from Goneri for passwd locks.</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> thanks for the contributions this round folks!</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> upstream is currently focused on getting in bug fixes, dropping remnants of py2 in tooling reviewing active PRs to get cloud-init in shape for the upcoming 20.2 release</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> community notice: as mentioned in the channel topic, Apr 28th is our upstream release date for 20.2</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> community notice: we ask that pull requests or bugs that need resolution for 20.2 be up for review by Friday April 24th so there is time to review and merge those fixes.</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> active pulls indended for the release should be up in github at <a href="https://github.com/canonical/cloud-init/pulls">https://github.com/canonical/cloud-init/pulls</a></p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> <em>intended</em> rather</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> #topic Community Charter</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> his section is generally reserved to discuss any general community goals for cloud-init, at last cloud-init summit we defined those goals as:</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> - datasource doc fixes</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> - json schema validation for each cloudinit/config/cc_*py modules</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> there are feature bugs created for these tasks at <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=bitesize</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> #topic Office hours (next ~30 mins)</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> During office hours a couple of upstream devs will have eyes on this channel. Any questions, comments, branch reviews are fair game for discussion.</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> In leiu of active discussions, developers will be grooming the active pull request review queue to unblock branch authors.</p> -<p>16:37 <code>&lt;punkgeek&gt;</code> Odd_Bloke: No it doesn't work. why there is no way to config cloud-init in kvm virtualization rather than iso, like vm xml file?</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> I'm getting through a belated review on <a href="https://github.com/canonical/cloud-init/pull/298">https://github.com/canonical/cloud-init/pull/298</a></p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> punkgeek: like seeding ovf-env.xml? <a href="https://github.com/canonical/cloud-init/blob/master/doc/sources/ovf/README">https://github.com/canonical/cloud-init/blob/master/doc/sources/ovf/README</a></p> -<p>16:46 <code>&lt;rharper&gt;</code> punkgeek: you might want to look at virt-install , they recently have added support for providing cloud-config to VMs; virt-install is a wrapper around creating VMs utilizing libvirt as a backend, <a href="https://athinapl.home.blog/2019/08/25/gsoc-2019-cloud-init-configuration-for-virt-manager-virt-install/">https://athinapl.home.blog/2019/08/25/gsoc-2019-cloud-init-configuration-for-virt-manager-virt-install/</a></p> -<p>16:54 <code>&lt;Goneri&gt;</code> punkgeek, or you can take a look at virt-lightning</p> -<p>16:54 <code>&lt;Goneri&gt;</code> punkgeek, it's basically a CLI to use libvirt+cloud-init</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> Goneri: review done. sorry for the delay on such a minor set of change requests <a href="https://github.com/canonical/cloud-init/pull/298/files#">https://github.com/canonical/cloud-init/pull/298/files#</a></p> -<p>17:09 <code>&lt;blackboxsw&gt;</code> <a href="https://github.com/CanonicalLtd/uss-tableflip/pull/45">https://github.com/CanonicalLtd/uss-tableflip/pull/45</a> I think comments are resolved</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> I think we are at about the turn of the hour for cloud-init status. I'm going to review <a href="https://github.com/canonical/cloud-init/pull/305">https://github.com/canonical/cloud-init/pull/305</a> next</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> thanks all for tuning in. see you next time</p> -<p>17:12 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2020-03-31T16:19:00+00:002020-03-31T16:19:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2020-03-31:/status-2020-03-31.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 31 Mar at 16:19 &mdash; 17:17 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-03-31-16.19.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-03-31-16.19.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-03-10.html#status-2020-03-10">https://cloud-init.github.io/status-2020-03-10.html#status-2020-03-10</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:22 …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 31 Mar at 16:19 &mdash; 17:17 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-03-31-16.19.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-03-31-16.19.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-03-10.html#status-2020-03-10">https://cloud-init.github.io/status-2020-03-10.html#status-2020-03-10</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:22.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:23.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://paste.ubuntu.com/p/55hqVCfnpV/">https://paste.ubuntu.com/p/55hqVCfnpV/</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:32.</p> -<h3>Community Charter</h3> -<p>The discussion about "Community Charter" started at 16:42.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=bitesize </li> -</ul> -<h3>Office hours (next ~30 mins)</h3> -<p>The discussion about "Office hours (next ~30 mins)" started at 16:45.</p> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (38)</li> -<li>meetingology (4)</li> -<li>rharper (2)</li> -<li>Goneri (1)</li> -<li>shibumi (1)</li> -<li>smoser (0)</li> -<li>Odd_Bloke (0)</li> -</ul> -<h2>Full Log</h2> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #startmeeting cloud-init status meeting</p> -<p>16:19 <code>&lt;meetingology&gt;</code> Meeting started Tue Mar 31 16:19:14 2020 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:19 <code>&lt;meetingology&gt;</code> </p> -<p>16:19 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> Hello and welcome to another cloud-init community status meeting folks. please feel free to continue any current conversations</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> I'll interleave status meeting notes with existing conversations.</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #chair Odd_Bloke smoser rharper</p> -<p>16:20 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw rharper smoser</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> our IRC channel topic carries the next planned status meeting for those that wish to participate. All are welcome to interject or drive converstation topics here</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> let's set that now. to +2 weeks from now</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> April 14th, same time</p> -<p>16:21 <code>&lt;shibumi&gt;</code> rharper: thanks!</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> Previous meeting notes are here</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2020-03-10.html#status-2020-03-10">https://cloud-init.github.io/status-2020-03-10.html#status-2020-03-10</a></p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> The topics we generally cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Upcoming Meetings, Office Hours (~30 mins).</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> and from last meeting, no previous actions were unaccounted for.</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> recent changes landed in tip of master via git log --since 2020-03-10</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> #link <a href="https://paste.ubuntu.com/p/55hqVCfnpV/">https://paste.ubuntu.com/p/55hqVCfnpV/</a></p> -<p>16:24 <code>&lt;rharper&gt;</code> shibumi: also, the issue with openstack metadata service not being found is likely related to classless statci route support in the EphemeralDHCP class in cloud-init, we fixed an issue there last fall, <a href="https://github.com/canonical/cloud-init/commit/07b17236be5665bb552c7460102bcd07bf8f2be8">https://github.com/canonical/cloud-init/commit/07b17236be5665bb552c7460102bcd07bf8f2be8</a></p> -<p>16:24 <code>&lt;rharper&gt;</code> shibumi: long term, we would like to replace dhclient with a python-based one; we've just not had a change to implement a minimal dhclient in python only</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> in that paste or recent changes, some big items have landed since last we 'met': both NetBSD and OpenBSD distro support is now added to cloud-init. vmware support of guest info gc status, SAP Converged cloud gets identified as OpenStack and Ubuntu Focal prioritizing netplan over ifupdown if both are present</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> Also Odd_Bloke has been landing and improving cloud-init automated process with near daily branches. github actions/workflows and docs about review and coding style expectations are landing to make it a lot easier for upstream to help speed contributions and reviews</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> Also, you'll note a lot of dropping python six and other py2-related artifacts from our codebase. Since upstream support is py3.4 or later we can simplify and prune a lot of the vestigial py2 functionality.</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> Ahh I also forgot, Ec2 now by default (Ubuntu Focal or tip of cloud-init) renders full networking, including secondary IPv4/IPv6 addresses, for all interfaces attached to a VM based on network config supplied by IMDS. Old releases of cloud-init used to only render basic networking on the primary (eth0) nic.</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> thanks Goneri and meena for all your the BSD ongoing development and support work there BTW</p> -<p>16:33 * Goneri waves</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> :) upstream is focused a bit on continuing to clean up py2 remnants from tip, adding support for reading netplan configuration from initramfs and continuing to add automation to the github development and release process/tooling to speed reviews.</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> we are also hammering the review queue a bit better than in the past with daily PR assignments to ensure the system remains more efficient</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> thanks again for all the code submits folks!</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> waiting In the wings we will eventually get around to handling the network hotplug solution for cloud-init (if configured)</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> #topic Community Charter</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> This section is generally reserved to discuss any general community goals for cloud-init. Per last cloud-init summit we discussed prioritizing the following:</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> * json schema validation for each cloudinit/config/cc_*py module</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> * correcting, extending stale datasource documentation under doc/rtd/topics/datasources</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> those tasks are easy to split up and so we set a goal to try to chunk through it this year</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> they are also categorized as bugs for easy pickup/assignment for anyone interested.</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=bitesize</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> #topic Office hours (next ~30 mins)</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> thanks for listening to the above...... In this section a couple upstream devs should be available with eyes on the channel for the next 30 minutes for and bug, feature, PR review questions or concerns.</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> again thanks for joining. We'll have this meeting again in 2 weeks</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> I'm going to spend this time working on our cherry-pick script for publishing the Netplan -&gt;` ENI work into Ubuntu Focal today.</p> -<p>17:17 <code>&lt;blackboxsw&gt;</code> Thanks for tuning in.</p> -<p>17:17 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2020-03-10T16:22:00+00:002020-03-10T16:22:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2020-03-10:/status-2020-03-10.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 10 Mar at 16:22 &mdash; 17:45 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-03-10-16.22.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-03-10-16.22.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-02-18.html#status-2020-02-18">https://cloud-init.github.io/status-2020-02-18.html#status-2020-02-18</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:24 …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 10 Mar at 16:22 &mdash; 17:45 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-03-10-16.22.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-03-10-16.22.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-02-18.html#status-2020-02-18">https://cloud-init.github.io/status-2020-02-18.html#status-2020-02-18</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:24.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:25.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://wiki.ubuntu.com/FocalFossa/ReleaseSchedule">https://wiki.ubuntu.com/FocalFossa/ReleaseSchedule</a> </li> -<li><strong>LINK</strong>: <a href="https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html#format-of-instance-data-json">https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html#format-of-instance-data-json</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:37.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pulls">https://github.com/canonical/cloud-init/pulls</a> </li> -</ul> -<h3>Community Charter and upcoming meeting</h3> -<p>The discussion about "Community Charter and upcoming meeting" started at 16:51.</p> -<h3>cloud-init pull-requests <a href="https://git.io/JeVed">https://git.io/JeVed</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting March 1 16:15 UTC | 19.4 (Dec 17) drops Py2.7 : origin/stable-19.4 | 20.1 (Feb 18) | <a href="https://bugs.launchpad.net/cloud-init/+filebug">https://bugs.launchpad.net/cloud-init/+filebug</a></h3> -<p>The discussion about "cloud-init pull-requests <a href="https://git.io/JeVed">https://git.io/JeVed</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting March 1 16:15 UTC | 19.4 (Dec 17) drops Py2.7 : origin/stable-19.4 | 20.1 (Feb 18) | <a href="https://bugs.launchpad.net/cloud-init/+filebug">https://bugs.launchpad.net/cloud-init/+filebug</a>" started at 16:53.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=bitesize </li> -</ul> -<h3>Office Hours (next 30 mins)</h3> -<p>The discussion about "Office Hours (next 30 mins)" started at 16:58.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pull/241">https://github.com/canonical/cloud-init/pull/241</a> </li> -<li><strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pull/241/files">https://github.com/canonical/cloud-init/pull/241/files</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 (109)</li> -<li>Odd_Bloke (13)</li> -<li>tribaal (5)</li> -<li>meetingology (4)</li> -<li>AnhVoMSFT (2)</li> -<li>Goneri (2)</li> -<li>powersj (1)</li> -<li>smoser (0)</li> -<li>rharper (0)</li> -</ul> -<h2>Full Log</h2> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:22 <code>&lt;meetingology&gt;</code> Meeting started Tue Mar 10 16:22:58 2020 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:22 <code>&lt;meetingology&gt;</code> </p> -<p>16:22 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> Hello and welcome to another cloud-init community status meeting.</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> our IRC channel topic carries the next planned status meeting for those that wish to participate.</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> All are welcome and interruptions encouraged</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #chair rharper Odd_Bloke smoser</p> -<p>16:23 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw rharper smoser</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> Previous meeting notes are here</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2020-02-18.html#status-2020-02-18">https://cloud-init.github.io/status-2020-02-18.html#status-2020-02-18</a></p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> he topics we cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Upcoming Meetings, Office Hours (~30 mins).</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> *the even</p> -<p>16:24 <code>&lt;Odd_Bloke&gt;</code> o/</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> \O</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> sorry, have my big head on</p> -<p>16:24 <code>&lt;tribaal&gt;</code> o/</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> :). Last meeting had no actions carried over. So I think this topic is a noop this week</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> recent changes landed in tip of master via git log --since 2020-02-18 <a href="https://paste.ubuntu.com/p/sJVpvjFbPj/">https://paste.ubuntu.com/p/sJVpvjFbPj/</a></p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> we've added some tooling/actions for github, ec2 IMDSv2 token redacting from logs, alloowing kernel cmdline to tell cloud-init network-config=disabled and not falling back to IMDSv1 on Ec2-proper platform</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> thanks fred-lefebvre for the ec2 IMDS fallback branch and others for some additional driveby doc updates</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> Also, we performed an upload to Ubuntu Focal (20.04) series with latest tip of cloud-init to make sure the development release is up to date with recent features</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> Ubuntu Focal release is currently in feature freeze, so that will affect what patches we pull into Ubuntu Focal at this time as 'new features' would need a Feature Freeze Exception during the stage of Ubuntu development.</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> #link <a href="https://wiki.ubuntu.com/FocalFossa/ReleaseSchedule">https://wiki.ubuntu.com/FocalFossa/ReleaseSchedule</a></p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> As Odd_Bloke alluded to just before this meeting, we are trying to keep tip of master</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> open for commits.</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> On the ubuntu-side of the house we will sort cherry picking bug fixes into ubuntu focal during this short feature freeze period of time</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> If there are significant features that your cloud platform really would like to see on the first public release of Ubuntu Focal, then please get ahold of us in channel of on the mailing list to suggest that we shepherd those features in during this freeze.</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> But, generally cloud-init team will continue to follow the SRU process to get updates into Focal after feature freeze is lifted.</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> and again, our SRU test/verification process for Ubuntu will continue to target Xenial, Bionic, Eoan and Focal series for the updates we plan to make in the near future</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> one thing to note in recent changes as well is that we've now added the ability to query distro, kernel, cpu arch, python runtime version and and merged cloud-config to cloud-config jinja templates. So #cloud-config userdata can be opinionated based on your target distribution or runtime environment.</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html#format-of-instance-data-json">https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html#format-of-instance-data-json</a></p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> I think that about wraps recent changes</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> #link <a href="https://github.com/canonical/cloud-init/pulls">https://github.com/canonical/cloud-init/pulls</a></p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> our active pulls above is probably the best source of info on features/bugfixes in flight.</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> Though behind the scenes we have held a couple of meetings to determine how much more automation/tooling we need to clean up to improve our github developer process</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> I think Odd_Bloke and I have around 4 PRs that we are hoping to clean up to get a couple of things in place:</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> foremost I believe Odd_Bloke is scrubbing the github review process PR so that we have a good starting point for expectations for every developer, author or committer.</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> I think ultimately the goal there is to make sure committers can provide a set of expectations on active PR reviews to PR authors, so that active developers get better prioritized reviews.</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> we are going to add and enable a number of github actions and workflows that should do the following:</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> - age PRs and add labelling to indicate to reviewers and authors that a review needs attention or it will be automatically closed (after around 4 weeks of languishing)</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> - label/notify steps to signed the contributor license agreement if unsigned</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> - run addtional integration tests on active PRs in CI</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> not sure if I am I missing anything else there.</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> but ideally we'd like to find a process that helps upstream unblock PRs and get review comments faster</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> so, it'll be an iterative process</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> and thanks for the reviews and suggestions so far on <a href="https://github.com/canonical/cloud-init/pull/160">https://github.com/canonical/cloud-init/pull/160</a> as it is the first cut at trying to document the process</p> -<p>16:47 <code>&lt;tribaal&gt;</code> Nice!</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> woot. the hope I believe is to land that this week as well as branches like <a href="https://github.com/canonical/cloud-init/pull/164">https://github.com/canonical/cloud-init/pull/164</a> <a href="https://github.com/canonical/cloud-init/pull/236">https://github.com/canonical/cloud-init/pull/236</a> and <a href="https://github.com/canonical/cloud-init/pull/125">https://github.com/canonical/cloud-init/pull/125</a></p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> additionally a gap that we still have vs when we hosted in Launchpad, is our auto-merge Launchpad bug commenting/maintenance:</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> We still have a need for the following:</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> - comment on LP bugs linking to an open github PR</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> - comment on merged commitish in github and Fix Commited state when a PR lands in upstream</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> so we'll be tackling that too in order to make upstream maintainers happier and better advertise fixes to bug filers</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> right now that's all a manual process since we haven't retooled our bug-related tooling</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> #topic Community Charter and upcoming meeting</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> let's set the status meeting for next session</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> oops and I realize only now that I blew it this week due to daylight savings... meeting wasn't 'supposed' to start until 25 mins from now : /</p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> #topic cloud-init pull-requests <a href="https://git.io/JeVed">https://git.io/JeVed</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting March 1 16:15 UTC | 19.4 (Dec 17) drops Py2.7 : origin/stable-19.4 | 20.1 (Feb 18) | <a href="https://bugs.launchpad.net/cloud-init/+filebug">https://bugs.launchpad.net/cloud-init/+filebug</a></p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> that's better.</p> -<p>16:53 <code>&lt;AnhVoMSFT&gt;</code> it says March 1, is that correct?</p> -<p>16:54 <code>&lt;tribaal&gt;</code> there :)</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> hah, good I got another participant</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> :)</p> -<p>16:54 <code>&lt;AnhVoMSFT&gt;</code> UK will also have their own daylight savings March 29th I believe</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> sorry AnhVoMSFT tribaal :)</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> yeah this time of year always messes with timing. We try to set things in terms of UTC to avoid thrashing</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> but even that fails due to human error (my bad)</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> Other community charter tasks are generally categorized in bugs labelled bitesize</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=bitesize</p> -<p>16:57 <code>&lt;blackboxsw&gt;</code> general topics for this year were tasks that are easily done in parallel, such as json schema addtions and datasource readthe docs updates/corrections and fleshing out.</p> -<p>16:57 <code>&lt;blackboxsw&gt;</code> jsonschema example is here for review if anyone wants to take a stab at testing it out. or extending schema for other config modules.<a href="https://github.com/canonical/cloud-init/pull/152">https://github.com/canonical/cloud-init/pull/152</a></p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> and again all cloud-init contributors are encouraged to review/comment any active cloud-init PRs @ <a href="https://github.com/canonical/cloud-init/pulls">https://github.com/canonical/cloud-init/pulls</a> the more voices, the better the quality</p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next 30 mins)</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> During this topic, please bring up any questions, discussions, bugs or features or paper cuts that need attention. there should be a couple of cloud-init developers with eyes on the channel to actively respond.</p> -<p>17:00 <code>&lt;blackboxsw&gt;</code> just before the start of this meeting Odd_Bloke was asking about getting the pytest branch landed for cloud-init. (moving off of nosetests as the project is EOL/unmaintained)</p> -<p>17:00 <code>&lt;tribaal&gt;</code> that's nice. pytest is becoming the de-facto standard these days anyway</p> -<p>17:05 <code>&lt;blackboxsw&gt;</code> yeah, didn't want to get stuck using something that becomes unsupported or unsupportable. we don't have the bandwidth in this project to maintain stacks that aren't being looked at by the collective internet ;)</p> -<p>17:05 <code>&lt;Odd_Bloke&gt;</code> blackboxsw: I believe that branch is now only blocked on you removing your "Request changes" review now that we've established that we don't need to hold off on landing things for Feature Freeze.</p> -<p>17:05 <code>&lt;tribaal&gt;</code> makes total sense :)</p> -<p>17:05 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: do you know if rharper did the new-upstream-snapshot into focal already</p> -<p>17:05 <code>&lt;blackboxsw&gt;</code> to have a 'clean slate' for the pytest branch landing</p> -<p>17:06 <code>&lt;Odd_Bloke&gt;</code> blackboxsw: We can new-upstream-snapshot from an older commit, I don't believe that's a blocker.</p> -<p>17:06 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: not a blocker, but I could do that now as it's 5 mins</p> -<p>17:07 <code>&lt;blackboxsw&gt;</code> then we can land right aftr</p> -<p>17:07 <code>&lt;blackboxsw&gt;</code> sound good? I see nothing queued <a href="https://launchpad.net/ubuntu/focal/+queue">https://launchpad.net/ubuntu/focal/+queue</a>?queue_state=3&amp;queue_text=cloud-init</p> -<p>17:08 <code>&lt;Odd_Bloke&gt;</code> Sure, if you're happier doing that. :)</p> -<p>17:09 <code>&lt;blackboxsw&gt;</code> I aam :)</p> -<p>17:09 <code>&lt;blackboxsw&gt;</code> ok doing that right now</p> -<p>17:09 <code>&lt;blackboxsw&gt;</code> then we can start the cherry picking just after</p> -<p>17:10 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: I'm adding this as the debian/changelog section title</p> -<p>17:10 <code>&lt;blackboxsw&gt;</code> * New upstream snapshot: bug-fix-only feature-freeze-exception</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> instead of * New upstream snapshot:</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> sound reasonable?</p> -<p>17:11 <code>&lt;Odd_Bloke&gt;</code> It isn't bug-fix-only because we have the FFe for a non-bugfix.</p> -<p>17:12 <code>&lt;Odd_Bloke&gt;</code> I was just reading the wiki page that suggested wording, I think, let me take a look.</p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> <a href="https://github.com/canonical/cloud-init/pull/241">https://github.com/canonical/cloud-init/pull/241</a></p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> ahh right, reviewing that now</p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> yeah not quite sure how to handle our FFe uploads</p> -<p>17:14 <code>&lt;Odd_Bloke&gt;</code> Oh, if it's only that change, then I don't think we need anything specific in the changelog. We have an FFE bug that we're closing with that upload.</p> -<p>17:14 * blackboxsw re-reads <a href="https://wiki.ubuntu.com/FreezeExceptionProcess">https://wiki.ubuntu.com/FreezeExceptionProcess</a></p> -<p>17:14 <code>&lt;Odd_Bloke&gt;</code> And that means it's <em>definitely</em> not bug-fix-only, there isn't a single bugfix in there. ;)</p> -<p>17:14 <code>&lt;blackboxsw&gt;</code> ok that sounds good, will just keep the New upstream snapshot</p> -<p>17:14 <code>&lt;blackboxsw&gt;</code> ok thanks for the review. redoing.</p> -<p>17:14 <code>&lt;Odd_Bloke&gt;</code> Hopefully I'm right and you don't get yelled at. :p</p> -<p>17:15 <code>&lt;powersj&gt;</code> better to upload and ask for forgiveness...</p> -<p>17:15 <code>&lt;blackboxsw&gt;</code> ehh, unlikely :) it seems like steve and others have been pretty lax about changelog text (or manipulating it after the fact) :)</p> -<p>17:15 <code>&lt;Odd_Bloke&gt;</code> Cool, I'll do the same thing locally to review.</p> -<p>17:16 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: force pushed</p> -<p>17:16 <code>&lt;blackboxsw&gt;</code> <a href="https://github.com/canonical/cloud-init/pull/241/files">https://github.com/canonical/cloud-init/pull/241/files</a></p> -<p>17:16 <code>&lt;Odd_Bloke&gt;</code> blackboxsw: Approved.</p> -<p>17:17 <code>&lt;blackboxsw&gt;</code> thanks Odd_Bloke</p> -<p>17:17 <code>&lt;blackboxsw&gt;</code> build-and-pushing it up</p> -<p>17:18 <code>&lt;blackboxsw&gt;</code> ok onto your pytest branch now</p> -<p>17:18 <code>&lt;blackboxsw&gt;</code> while I await the ubuntu "accepted" response email</p> -<p>17:20 <code>&lt;blackboxsw&gt;</code> Uploading cloud-init_20.1-10-g71af48df-0ubuntu1.dsc: done.</p> -<p>17:21 <code>&lt;blackboxsw&gt;</code> just waiting on review/acceptance</p> -<p>17:22 <code>&lt;blackboxsw&gt;</code> community-notice: tip of cloud-init published into Ubuntu Focal (20.04) [ubuntu/focal-proposed] cloud-init 20.1-10-g71af48df-0ubuntu1 (Accepted)</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> ok Odd_Bloke merged at long last <a href="https://github.com/canonical/cloud-init/pull/211">https://github.com/canonical/cloud-init/pull/211</a></p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> nosetest is dead, long live pytest</p> -<p>17:26 <code>&lt;Odd_Bloke&gt;</code> \o/</p> -<p>17:27 <code>&lt;Odd_Bloke&gt;</code> blackboxsw: <a href="https://github.com/canonical/cloud-init/pull/239">https://github.com/canonical/cloud-init/pull/239</a> `&lt;-- another small one for you</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> approve Odd_Bloke and thanks. it is waiting on you for merge (and CI completion)</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> works on my focal box</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> which was broken before</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: <a href="https://github.com/canonical/cloud-init/pull/164">https://github.com/canonical/cloud-init/pull/164</a> is ready for you I think (labeling in cron)</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> for CLA ! CLA.</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> or do we want that PR to actually ignore certain paths (like doc changes) as not-requiring CLA</p> -<p>17:43 <code>&lt;Goneri&gt;</code> blackboxsw, could you take a look at <a href="https://github.com/canonical/cloud-init/pull/62">https://github.com/canonical/cloud-init/pull/62</a> Pleaaaase :-)</p> -<p>17:44 <code>&lt;blackboxsw&gt;</code> Goneri: yes, and so sorry about that.</p> -<p>17:44 <code>&lt;Goneri&gt;</code> np, and Yeah! for pytest :-D</p> -<p>17:44 <code>&lt;blackboxsw&gt;</code> ... and that about wraps up on our cloud-init status meeting. :) I'll close it out and post the minutes for next time</p> -<p>17:45 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2020-02-18T17:35:00+00:002020-02-18T17:35:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2020-02-18:/status-2020-02-18.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 18 Feb at 17:35 &mdash; 18:36 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-02-18-17.35.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-02-18-17.35.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-02-04.html#status-2020-02-04">https://cloud-init.github.io/status-2020-02-04.html#status-2020-02-04</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 17:37 …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 18 Feb at 17:35 &mdash; 18:36 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-02-18-17.35.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-02-18-17.35.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2020-02-04.html#status-2020-02-04">https://cloud-init.github.io/status-2020-02-04.html#status-2020-02-04</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 17:37.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 17:38.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://paste.ubuntu.com/p/28Y8jGTGwr/">https://paste.ubuntu.com/p/28Y8jGTGwr/</a> </li> -</ul> -<h3>In-prgoress Development</h3> -<p>The discussion about "In-prgoress Development" started at 17:45.</p> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 17:45.</p> -<h3>cloud-init upstream 20.1</h3> -<p>The discussion about "cloud-init upstream 20.1" started at 17:49.</p> -<h3>Community Charter</h3> -<p>The discussion about "Community Charter" started at 17:59.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=bitesize </li> -</ul> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (52)</li> -<li>meetingology (5)</li> -<li>Odd_Bloke (3)</li> -<li>smoser (0)</li> -<li>rharper (0)</li> -</ul> -<h2>Full Log</h2> -<p>17:35 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>17:35 <code>&lt;meetingology&gt;</code> Meeting started Tue Feb 18 17:35:26 2020 UTC. The chair is blackboxsw. Information about MeetBot at <a href="http://wiki.ubuntu.com/meetingology.">http://wiki.ubuntu.com/meetingology.</a></p> -<p>17:35 <code>&lt;meetingology&gt;</code> </p> -<p>17:35 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>17:35 <code>&lt;blackboxsw&gt;</code> o/ hi cloud-init folks. sorry I botched being able to read calendars last time.</p> -<p>17:36 <code>&lt;blackboxsw&gt;</code> let's kick off our cloud-init status meeting.</p> -<p>17:36 <code>&lt;blackboxsw&gt;</code> notes from previous meeting are here:</p> -<p>17:36 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2020-02-04.html#status-2020-02-04">https://cloud-init.github.io/status-2020-02-04.html#status-2020-02-04</a></p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> the topics we cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Upcoming Meetings, Office Hours (~30 mins).</p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> today I'll add a topic for cloud-init's upstream release 20.1</p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> Last meeting minutes show no carryover action items. So we can drop into recent changes</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>17:40 <code>&lt;blackboxsw&gt;</code> We have about 8 commits landed in master since last meeting: found with git log --since 02-04-2020</p> -<p>17:40 <code>&lt;blackboxsw&gt;</code> <a href="https://paste.ubuntu.com/p/28Y8jGTGwr/">https://paste.ubuntu.com/p/28Y8jGTGwr/</a></p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> some doc fixes, CI fixes for Azure integration testing , swap disk support for cc_disk_setup and freebsd improvements.</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> thanks for contributions there all. I think we still have a long tail of improvements to review for FreeBSD and NetBSD so we'll try to keep the conversation going there.. Thanks meena and do3meli there</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> I mean Goneri</p> -<p>17:44 <code>&lt;blackboxsw&gt;</code> #chair rharper Odd_Bloke smoser</p> -<p>17:44 <code>&lt;meetingology&gt;</code> Warning: Nick not in channel: rharper</p> -<p>17:44 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw rharper smoser</p> -<p>17:44 <code>&lt;blackboxsw&gt;</code> forgot to set meeting chairs. sry</p> -<p>17:45 <code>&lt;blackboxsw&gt;</code> #topic In-prgoress Development</p> -<p>17:45 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>17:47 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: is currently wrapping up any remaining py2/p3-isms in master branch. Dropping use of 'six' throughout the code. Paride is working on copr-build failures due to the shift to python3 packages. otubo, thanks for the ping back on finding various python3 CentOS packages. We'll also try sorting this this week so cloud-init py3 builds can work on CentOS 7 and 8</p> -<p>17:47 <code>&lt;blackboxsw&gt;</code> If folks didn't see the mailing list Odd_Bloke has a branch up to shift from nosetests -&gt;` pytest <a href="https://lists.launchpad.net/cloud-init/msg00245.html">https://lists.launchpad.net/cloud-init/msg00245.html</a></p> -<p>17:48 <code>&lt;blackboxsw&gt;</code> we expect to land that after 20.1 releases. Thanks for the reviews there <a href="https://github.com/canonical/cloud-init/pull/211">https://github.com/canonical/cloud-init/pull/211</a></p> -<p>17:49 <code>&lt;blackboxsw&gt;</code> #topic cloud-init upstream 20.1</p> -<p>17:50 <code>&lt;blackboxsw&gt;</code> So, today at EOD is upstream release day for cloud-init 20.1. Just another timed release of cloud-init which we strive to make quarterly thoughout the year</p> -<p>17:50 <code>&lt;blackboxsw&gt;</code> As mentioned on the mailing list, if there are any branches/PRs that folks really would like to get into 20.1, please raise them here. We will scrub the review queue today and see what makes sense to land for this release.</p> -<p>17:52 <code>&lt;Odd_Bloke&gt;</code> I'll be driving the 20.1 release.</p> -<p>17:53 <code>&lt;Odd_Bloke&gt;</code> We just landed <a href="https://github.com/canonical/cloud-init/pull/204">https://github.com/canonical/cloud-init/pull/204</a> into master, which is a fix for a (low priority) CVE that we wanted in before cutting the release.</p> -<p>17:54 <code>&lt;Odd_Bloke&gt;</code> I'm going to perform some testing of that change before cutting the release, to determine if any doc changes are required for it and to check if it impacts boot on Azure instances that have a password provided by the Azure fabric.</p> -<p>17:54 <code>&lt;blackboxsw&gt;</code> I was just looking over the PR from fred in ec2 land about handling a disabled path for IMDSv2 that looks interesting, but it still needs unit tests <a href="https://github.com/canonical/cloud-init/pull/216/files">https://github.com/canonical/cloud-init/pull/216/files</a></p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> this would certainly help non-ec2 lookalikes</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> and is a fairly specific fix.</p> -<p>17:56 <code>&lt;blackboxsw&gt;</code> we can peek over it during the office hours and see if it makes sense.</p> -<p>17:56 <code>&lt;blackboxsw&gt;</code> Thanks Odd_Bloke for driving the 20.1 release.</p> -<p>17:56 <code>&lt;blackboxsw&gt;</code> So, again, plan is to cut 20.1 at end of day today.</p> -<p>17:58 <code>&lt;blackboxsw&gt;</code> What follows will be a tag and release to Ubuntu Focal to sync tip of master to Ubuntu development release</p> -<p>17:59 <code>&lt;blackboxsw&gt;</code> #topic Community Charter</p> -<p>17:59 <code>&lt;blackboxsw&gt;</code> This topic is a placeholder to remind folks of any project-wide development tasks that we are engaging the community in.</p> -<p>18:00 <code>&lt;blackboxsw&gt;</code> the general theme at the moment is cloud-config schema definitions for the config modules in cloudinit/config/cc_*py and improving/correct datasource configuration documentation</p> -<p>18:00 <code>&lt;blackboxsw&gt;</code> We've queued this work as separate bugs in cloud-init at the following link</p> -<p>18:01 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=bitesize</p> -<p>18:01 <code>&lt;blackboxsw&gt;</code> we'll revisit this set of bugs/features and resent community charter goals near the end of 2020 at the next cloud-init summit. If there are suggestions/desires for community themed tasks please feel free to set the direction there.</p> -<p>18:02 <code>&lt;blackboxsw&gt;</code> these community tasks are grabbed by any contributor to cloud-init.</p> -<p>18:03 <code>&lt;blackboxsw&gt;</code> An example of the schema definitions we are looking to add is the PR in review here. <a href="https://github.com/canonical/cloud-init/pull/152">https://github.com/canonical/cloud-init/pull/152</a></p> -<p>18:04 <code>&lt;blackboxsw&gt;</code> As always, everyone's review counts. As a project we are trying to also look to 'promote' more core-contributors, with commit rights to the cloud-init project. Reviews count just much as proposing pull requests to the project.</p> -<p>18:04 <code>&lt;blackboxsw&gt;</code> thanks again for all the contributions, reviews and bugs that are being contributed to date. It really helps improve this project's use</p> -<p>18:05 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>18:07 <code>&lt;blackboxsw&gt;</code> During this topic, please bring up any questions, discussions, bugs or features or paper cuts that need attention. there should be a couple of cloud-init developers with eyes on the channel to actively respond.</p> -<p>18:08 <code>&lt;blackboxsw&gt;</code> In leiu of active discussions, we'll hit up the review queue for cloud-init at <a href="https://git.io/JeVed">https://git.io/JeVed</a> and get ready for the 20.1 release</p> -<p>18:09 <code>&lt;blackboxsw&gt;</code> I'm going to see if I can</p> -<p>18:09 <code>&lt;blackboxsw&gt;</code> review <a href="https://github.com/canonical/cloud-init/pull/216/files">https://github.com/canonical/cloud-init/pull/216/files</a> and propose the unit test changes there</p> -<p>18:09 <code>&lt;blackboxsw&gt;</code> I think that could be a valid addition for ec2-lookalikes to avoid an unnecessary 2 minute timeout</p> -<p>18:09 <code>&lt;blackboxsw&gt;</code> on boot</p> -<p>18:19 <code>&lt;blackboxsw&gt;</code> hrm on 2nd thought w/ 216, I think that patch set should be more specific, such as actually testing HTTP status 403 instead of just checking if metadata was None and assuming it was disabled. I'll put a couple of review comments on that as I dig in, but probably not in a state that it could be landed today</p> -<p>18:36 <code>&lt;blackboxsw&gt;</code> thanks for tuning in folks. See you next time</p> -<p>18:36 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2020-02-04T17:23:00+00:002020-02-04T17:23:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2020-02-04:/status-2020-02-04.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 04 Feb at 17:23 &mdash; 19:08 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-02-04-17.23.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-02-04-17.23.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 17:27.</p> -<h3>Recent Changes</h3> -<p>The …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 04 Feb at 17:23 &mdash; 19:08 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-02-04-17.23.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-02-04-17.23.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 17:27.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 17:27.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://paste.ubuntu.com/p/3jQdKZVPcM/">https://paste.ubuntu.com/p/3jQdKZVPcM/</a> </li> -</ul> -<h3>In-progress Development,</h3> -<p>The discussion about "In-progress Development," started at 17:32.</p> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 17:32.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pulls">https://github.com/canonical/cloud-init/pulls</a> </li> -</ul> -<h3>Community Charter</h3> -<p>The discussion about "Community Charter" started at 17:43.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=bitesize </li> -</ul> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 17:47.</p> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (68)</li> -<li>ahosmanMSFT (10)</li> -<li>meetingology (5)</li> -<li>powersj (4)</li> -<li>ubot5 (3)</li> -<li>Odd_Bloke (0)</li> -<li>rharper (0)</li> -</ul> -<h2>Full Log</h2> -<p>17:23 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>17:23 <code>&lt;meetingology&gt;</code> Meeting started Tue Feb 4 17:23:28 2020 UTC. The chair is blackboxsw. Information about MeetBot at <a href="http://wiki.ubuntu.com/meetingology.">http://wiki.ubuntu.com/meetingology.</a></p> -<p>17:23 <code>&lt;meetingology&gt;</code> </p> -<p>17:23 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>17:23 <code>&lt;blackboxsw&gt;</code> morning, afternoon and evening folks. Time for another cloud-init community status meeting</p> -<p>17:24 <code>&lt;blackboxsw&gt;</code> #chair rharper</p> -<p>17:24 <code>&lt;meetingology&gt;</code> Current chairs: blackboxsw rharper</p> -<p>17:24 <code>&lt;blackboxsw&gt;</code> #chair Odd_Bloke</p> -<p>17:24 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw rharper</p> -<p>17:24 <code>&lt;blackboxsw&gt;</code> Coud-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>17:24 <code>&lt;blackboxsw&gt;</code> The next scheduled status meeting is always listed in the topic of this channel, so feel free to drop in on next session if you miss this one</p> -<p>17:25 <code>&lt;blackboxsw&gt;</code> while we're at it I'll update for next status meeting.</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> 2 weeks from today, same bat time, same bat channel</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> Our previous meeting minutes line here:</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> <em>live here</em> rather</p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> the topics we cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Upcoming Meetings, Office Hours (~30 mins).</p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> new topics or intejections are always welcome</p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> From last meeting we had no unresolved actions so we can jump to the next section</p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> found from tip of master with <code>git log --since 01/21/2020</code></p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - sysconfig: distro-specific config rendering for BOOTPROTO option (#162)</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> [Robert Schweikert] (LP: #1800854)</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - cloudinit: replace "from six import X" imports (except in util.py) (#183)</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - run-container: use 'test -n' instead of 'test ! -z' (#202)</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> [Paride Legovini]</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - net/cmdline: correctly handle static ip= config (#201)</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> [Dimitri John Ledkov] (LP: #1861412)</p> -<p>17:29 <code>&lt;ubot5&gt;</code> Launchpad bug 1800854 in cloud-init "BOTOPROTO handling between RHEL/Centos/Fedora and SUSE distros is different" [Medium,Triaged] <a href="https://launchpad.net/bugs/1800854">https://launchpad.net/bugs/1800854</a></p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - Replace mock library with unittest.mock (#186)</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - HACKING.rst: update CLA link (#199)</p> -<p>17:29 <code>&lt;ubot5&gt;</code> Launchpad bug 1861412 in cloud-init (Ubuntu) "cloud-init crashes with static network configuration" [Undecided,Fix committed] <a href="https://launchpad.net/bugs/1861412">https://launchpad.net/bugs/1861412</a></p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - Scaleway: Fix DatasourceScaleway to avoid backtrace (#128)</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> [Louis Bouchard]</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - cloudinit/cmd/devel/net_convert.py: add missing space (#191)</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - tools/run-container: drop support for python2 (#192) [Paride Legovini]</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - Print ssh key fingerprints using sha256 hash (#188) (LP: #1860789)</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - Make the RPM build use Python 3 (#190) [Paride Legovini]</p> -<p>17:29 <code>&lt;ubot5&gt;</code> Launchpad bug 1860789 in cloud-init (Ubuntu) "ssh_authkey_fingerprints must use sha256 not md5" [Undecided,Fix committed] <a href="https://launchpad.net/bugs/1860789">https://launchpad.net/bugs/1860789</a></p> -<p>17:29 <code>&lt;powersj&gt;</code> thought we were going to use pastebin :P</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> heh, that is a good point (I wondered if anyone would call me on that)</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> #link <a href="https://paste.ubuntu.com/p/3jQdKZVPcM/">https://paste.ubuntu.com/p/3jQdKZVPcM/</a></p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> generally speaking, dropping use of six since our code based is not python3-only, tooling dropping py2, sysconfig rendering flavors for opensuse, doc fixes and read the docs fixups</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> thanks all for the contributions over the last couple weeks</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development,</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> Any existing PRs are up for review at the following url:</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> #link <a href="https://github.com/canonical/cloud-init/pulls">https://github.com/canonical/cloud-init/pulls</a></p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> generally speaking we are in the 'long tail' part of a couple of feature-sets:</p> -<p>17:34 <code>&lt;blackboxsw&gt;</code> * we are trying to wrap up tooling for our automated CI, publishing processes and documentation for the shift to github from launchpad</p> -<p>17:34 <code>&lt;blackboxsw&gt;</code> * we are in progress on cloud-init handling network hotplug for a couple of datasources</p> -<p>17:35 <code>&lt;blackboxsw&gt;</code> * in progress on boot speed improvements for various platforms</p> -<p>17:36 <code>&lt;blackboxsw&gt;</code> We also recently validated and released cloud-init v 19.4.33 to Xenial, Bionic and Eoan (1/9/2020)</p> -<p>17:38 <code>&lt;ahosmanMSFT&gt;</code> Hi @blackboxsw I'm no longer in the provisioning team, but there's an urgency for the cloud test to be resilient. Have you looked at those issues, I can dedicate as much time as needed to this. If you have time, can we tackle this today?</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> there are also a number of PRs in flight for FreeBSD,NetBSD, OpenSUSE and CentOS that need attention so we can better enable those distros</p> -<p>17:38 <code>&lt;ahosmanMSFT&gt;</code> azurecloudtest that is</p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> hi ahosmanMSFT I can spend some time on office hours here to peek more at it. my individual runs didn't hit the timeouts again, so we might need a reproducer cmdline from you in a new bug maybe?</p> -<p>17:39 <code>&lt;ahosmanMSFT&gt;</code> So your able to run all tests successfully without timeout and image not building&gt;`</p> -<p>17:40 <code>&lt;blackboxsw&gt;</code> ahosmanMSFT: but yes I can spend a little time on this today. and I think ultimately we'll have to find the tox command line that exhibits this error. I'll go checkout my test run again and see. I don't think I saw the failure. but I might be invoking tests differently than you</p> -<p>17:41 <code>&lt;ahosmanMSFT&gt;</code> blackboxsw: hmm that's interesting, thanks let me know</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> same here ahosmanMSFT, can you file a bug with the traceback you see and the tox cmdline you are running?</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> then I know exactly what to look for</p> -<p>17:42 <code>&lt;ahosmanMSFT&gt;</code> Sure, will do now</p> -<p>17:43 <code>&lt;blackboxsw&gt;</code> cool.</p> -<p>17:43 <code>&lt;blackboxsw&gt;</code> ok next topic</p> -<p>17:43 <code>&lt;blackboxsw&gt;</code> #topic Community Charter</p> -<p>17:43 <code>&lt;blackboxsw&gt;</code> ok this section is reserved to raise general community work/goals.</p> -<p>17:44 <code>&lt;blackboxsw&gt;</code> At last cloud-init summit we raised a couple of general themes of improvements cloud-init would like to achieve</p> -<p>17:45 <code>&lt;blackboxsw&gt;</code> These themes fell into two categories for this year: datasource documentation updates and cloud-init json schema validation for the 50+ config modules in cloudinit/config/cc_*py so that we can better raise user-config errors and remove some of cloud-init's "sharp edges"</p> -<p>17:45 <code>&lt;blackboxsw&gt;</code> we converted a number of these feature requests in into bugs which can be searched here:</p> -<p>17:46 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/+bugs">https://bugs.launchpad.net/cloud-init/+bugs</a>?field.tag=bitesize</p> -<p>17:46 <code>&lt;blackboxsw&gt;</code> tasks in this list should be fairly easy one-time bugs for folks with a little time available to help improve cloud-init.</p> -<p>17:47 <code>&lt;blackboxsw&gt;</code> we'll revisit this set of bugs/features and the community charter goals near the end of 2020 at the next cloud-init summit</p> -<p>17:47 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>17:48 <code>&lt;blackboxsw&gt;</code> this time is spent with cloud-init upstream dev eyes on this channel for any cloud-init feature, bug or implementation discussions. In the absence of such discussions, we'll review the active PRs to try to tidy up the review queue and unblock developers</p> -<p>17:49 <code>&lt;blackboxsw&gt;</code> for the moment, I'll look over some Azure test timeouts ahosmanMSFT is seeing</p> -<p>17:49 <code>&lt;blackboxsw&gt;</code> any other topics, concerns, bugs, questions are welcome and someone should be around to field them</p> -<p>17:50 <code>&lt;blackboxsw&gt;</code> ahosmanMSFT: so timeouts running integration tests, you said you are getting them about half the time?</p> -<p>18:48 <code>&lt;ahosmanMSFT&gt;</code> blackboxsw: Yes, I tracked it down to platforms/instance._wait_for_system</p> -<p>18:49 <code>&lt;ahosmanMSFT&gt;</code> I invoke it after initializing vm in platform/azurecloudtest/instance.start</p> -<p>18:49 <code>&lt;ahosmanMSFT&gt;</code> when removed, everything works as expected</p> -<p>18:50 <code>&lt;ahosmanMSFT&gt;</code> looks like it's needed for cloud tests so thought I'd leave it to you, since I don't know how ec2/lxd/... rely on</p> -<p>18:50 <code>&lt;powersj&gt;</code> ahosmanMSFT, can you file a bug please with the cli example?</p> -<p>18:50 <code>&lt;powersj&gt;</code> that would help us triage and make a proper decision on what change to make</p> -<p>18:51 <code>&lt;ahosmanMSFT&gt;</code> powersj, yes, was in the middle of that side tracked by meeting. On it now</p> -<p>18:51 <code>&lt;powersj&gt;</code> thanks!</p> -<p>19:07 <code>&lt;blackboxsw&gt;</code> aaaand, I should probably wrap the meeting for the day.</p> -<p>19:08 <code>&lt;blackboxsw&gt;</code> Thanks all for the time and energy you put into improving cloud-init! See you next time, or anytime in between</p> -<p>19:08 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2020-01-21T17:42:00+00:002020-01-21T17:42:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2020-01-21:/status-2020-01-21.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 21 Jan at 17:42 &mdash; 18:55 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-01-21-17.42.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-01-21-17.42.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 17:50.</p> -<ul> -<li><strong>LINK</strong>: bugs.launchpad …</li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 21 Jan at 17:42 &mdash; 18:55 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-01-21-17.42.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-01-21-17.42.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 17:50.</p> -<ul> -<li><strong>LINK</strong>: bugs.launchpad.net/cloud-init/+bugs?field.tag=bitesize </li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 17:53.</p> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 17:57.</p> -<h3>Community Charter</h3> -<p>The discussion about "Community Charter" started at 18:02.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloudinit.readthedocs.io/en/latest/topics/debugging.html#manual-sru-verification-procedure">https://cloudinit.readthedocs.io/en/latest/topics/debugging.html#manual-sru-verification-procedure</a> </li> -</ul> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 18:08.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1859725">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1859725</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 (58)</li> -<li>tribaal (3)</li> -<li>ubot5 (3)</li> -<li>meetingology (3)</li> -</ul> -<h2>Full Log</h2> -<p>17:42 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>17:42 <code>&lt;meetingology&gt;</code> Meeting started Tue Jan 21 17:42:43 2020 UTC. The chair is blackboxsw. Information about MeetBot at <a href="http://wiki.ubuntu.com/meetingology.">http://wiki.ubuntu.com/meetingology.</a></p> -<p>17:42 <code>&lt;meetingology&gt;</code> </p> -<p>17:42 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>17:43 <code>&lt;blackboxsw&gt;</code> At long last, and a bit late. Time for a brief cloud-init status meeting</p> -<p>17:43 <code>&lt;blackboxsw&gt;</code> Coud-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>17:44 <code>&lt;blackboxsw&gt;</code> You can always find the next date and time of the cloud-init status meeting in the topic of this channel.</p> -<p>17:45 <code>&lt;blackboxsw&gt;</code> it also serves as a reminder to me that we need to start it as I find it's easy to forget the appointment if it isn't staring us in the face.</p> -<p>17:46 <code>&lt;blackboxsw&gt;</code> Let's set next meeting now</p> -<p>17:48 <code>&lt;blackboxsw&gt;</code> our previous meeting minutes are recorded on our github site</p> -<p>17:49 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>17:49 <code>&lt;blackboxsw&gt;</code> the topics we cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Upcoming Meetings, Office Hours (~30 mins).</p> -<p>17:50 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>17:50 <code>&lt;blackboxsw&gt;</code> Previous #ACTION bbsw seed initial community charter bitesize bugs ... DONE.</p> -<p>17:51 <code>&lt;blackboxsw&gt;</code> 'bitesize' bugs for cloud-init can be found at the following link</p> -<p>17:51 <code>&lt;blackboxsw&gt;</code> #link bugs.launchpad.net/cloud-init/+bugs?field.tag=bitesize</p> -<p>17:52 <code>&lt;blackboxsw&gt;</code> These bugs should be easy to work in parallel as well as self-contained bits of work that any member of the community could approach as a small chunk of work</p> -<p>17:53 <code>&lt;blackboxsw&gt;</code> we moved from using trello board for tracking these tasks to using launchpad bugs as it eases the ability to search and grab ownership of the specific features/bugs</p> -<p>17:53 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> The following commits landed in tip of master: (found by git log --since 01/07/2020)</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> - Add Rootbox &amp; HyperOne to list of cloud in README (#176) [Adam Dobrawy]</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> - docs: add proposed SRU testing procedure (#167)</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> - util: rename get_architecture to get_dpkg_architecture (#173)</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> - Ensure util.get_architecture() runs only once (#172)</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> - Only use gpart if it is the BSD gpart (#131) [Conrad Hoffmann]</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> - freebsd: remove superflu exception mapping (#166) [Gonéri Le Bouder]</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> - ssh_auth_key_fingerprints_disable test: fix capitalization (#165)</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> [Paride Legovini]</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> - util: move uptime's else branch into its own boottime function (#53)</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> [Igor Galić] (LP: #1853160)</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> - workflows: add contributor license agreement checker (#155)</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> - net: fix rendering of 'static6' in network config (#77) (LP: #1850988)</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> - Make tests work with Python 3.8 (#139) [Conrad Hoffmann]</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> - fixed minor bug with mkswap in cc_disk_setup.py (#143) [andreaf74]</p> -<p>17:55 <code>&lt;ubot5&gt;</code> Launchpad bug 1853160 in cloud-init "uptime code does not work on FreeBSD with python 3" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1853160">https://launchpad.net/bugs/1853160</a></p> -<p>17:55 <code>&lt;ubot5&gt;</code> Launchpad bug 1850988 in cloud-init "[Cloud-init 18.5][CentOS 7 on vSphere] Crash when configuring static dual-stack (IPv4 + IPv6) networking" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1850988">https://launchpad.net/bugs/1850988</a></p> -<p>17:56 <code>&lt;blackboxsw&gt;</code> Thanks Adam, Conrad, andreaf74, Gonéri and meena for improving cloud-init.</p> -<p>17:57 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>17:58 <code>&lt;blackboxsw&gt;</code> FreeBSD, NetBSD improvements are under heavy development, thanks meena and Goneri for all the PRs put of in that regard.</p> -<p>17:58 <code>&lt;blackboxsw&gt;</code> Also robjo has started work on cleanup of sysconfig net rendering per <a href="https://github.com/canonical/cloud-init/pull/162">https://github.com/canonical/cloud-init/pull/162</a> and a mailing list discussion</p> -<p>17:59 <code>&lt;blackboxsw&gt;</code> rharper is also midstream on "cloud-init run as a daemon" mode <a href="https://github.com/canonical/cloud-init/pull/48">https://github.com/canonical/cloud-init/pull/48</a> which should improve cloud-init startup times by avoiding having to reload python 4 times for each cloud-init stage</p> -<p>18:00 <code>&lt;blackboxsw&gt;</code> Also in progress, upstream has started to SRU testing for cloud-init 19.4.33 into Ubuntu Xenial, Bionic and Eoan.</p> -<p>18:01 <code>&lt;blackboxsw&gt;</code> We expect to wrap up that testing this week for a publish of cloud-init 19.4.33 to those series</p> -<p>18:02 <code>&lt;blackboxsw&gt;</code> #topic Community Charter</p> -<p>18:02 <code>&lt;blackboxsw&gt;</code> As a note, any community member is welcome to participate in SRU testing of cloud-init if those changesets in the SRU affect your cloud platform or features.</p> -<p>18:02 <code>&lt;blackboxsw&gt;</code> We have added a guide for SRU testing on Ubuntu here</p> -<p>18:03 <code>&lt;tribaal&gt;</code> duly noted :)</p> -<p>18:03 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloudinit.readthedocs.io/en/latest/topics/debugging.html#manual-sru-verification-procedure">https://cloudinit.readthedocs.io/en/latest/topics/debugging.html#manual-sru-verification-procedure</a></p> -<p>18:03 <code>&lt;blackboxsw&gt;</code> :)</p> -<p>18:04 <code>&lt;blackboxsw&gt;</code> ahh tribaal we should pull in your PR for manual testing of Exoscale too if you think it's ready <a href="https://github.com/cloud-init/ubuntu-sru/pull/64">https://github.com/cloud-init/ubuntu-sru/pull/64</a></p> -<p>18:04 <code>&lt;tribaal&gt;</code> it's not unfortunately :/</p> -<p>18:05 <code>&lt;blackboxsw&gt;</code> ahh, ok <em>good</em>, thought it was waiting on review</p> -<p>18:05 <code>&lt;blackboxsw&gt;</code> ok can table that for another SRU (which will be around Feb 14th likely)</p> -<p>18:06 <code>&lt;tribaal&gt;</code> no worries, happy to help test the current one anyway</p> -<p>18:06 <code>&lt;blackboxsw&gt;</code> community notice: we are targeting Feb 18th as our cutoff for upstream cloud-init version 20.1 (which will be SRU'd to Ubuntu Xenial, bionic and Eoan). If there are features of bug fixes that you'd like to get into cloud-init 20.1 please raise them as PRs or discussion on the mailinglist or in channel</p> -<p>18:08 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>18:08 <code>&lt;blackboxsw&gt;</code> This time is spent on any cloud-init feature/bug/branch discussions. quetions or concerns and topics are welcome. In the absence of topics we'll groom the review queue.</p> -<p>18:09 <code>&lt;blackboxsw&gt;</code> I'm wrapping up some significant change suggestions the networking stuff for sysconfig on <a href="https://github.com/canonical/cloud-init/pull/162">https://github.com/canonical/cloud-init/pull/162</a></p> -<p>18:10 <code>&lt;blackboxsw&gt;</code> I should have that review done in about an hour</p> -<p>18:10 <code>&lt;blackboxsw&gt;</code> I've added myself as the "assignee" to that PR to indicate it as priority for me</p> -<p>18:11 <code>&lt;blackboxsw&gt;</code> also, note in SRU testing I've run into a repeated issue with cloud-init's ssh-import-id taking 1 minute to import a single ssh pubkey on Azure bionic advanced networking vms. (2 nics + ipv6 + multiple IPs). I'll be debugging this a bit today to make sure it is not a regression for this cloud-init SRU 19.4.33</p> -<p>18:12 <code>&lt;blackboxsw&gt;</code> if anyone has any feedback or issues associated with this cloud-init v 19.4.33 SRU, they can comment on the SRU bug or raise a new bug or comment in IRC</p> -<p>18:12 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1859725">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1859725</a></p> -<p>18:12 <code>&lt;ubot5&gt;</code> Ubuntu bug 1859725 in cloud-init (Ubuntu) "sru cloud-init (19.3.41 to 19.4.33) Xenial, Bionic and Eoan" [Undecided,New]</p> -<p>18:55 <code>&lt;blackboxsw&gt;</code> ok, that about wraps today's status meeting. We'll have the next one February 4th to chat again about getting features ready for 20.1</p> -<p>18:55 <code>&lt;blackboxsw&gt;</code> Thanks for tuning in.</p> -<p>18:55 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2020-01-07T17:30:00+00:002020-01-07T17:30:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2020-01-07:/status-2020-01-07.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 07 Jan at 17:30 &mdash; 18:39 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-01-07-17.30.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-01-07-17.30.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-12-10.html#status-2019-12-10">https://cloud-init.github.io/status-2019-12-10.html#status-2019-12-10</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 17:36 …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 07 Jan at 17:30 &mdash; 18:39 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-01-07-17.30.log.html">http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-01-07-17.30.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-12-10.html#status-2019-12-10">https://cloud-init.github.io/status-2019-12-10.html#status-2019-12-10</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 17:36.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://github.com/cloud-init/cloud-init/pulls">https://github.com/cloud-init/cloud-init/pulls</a> </li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 17:39.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://paste.ubuntu.com/p/Cwnn3SbmWQ/">https://paste.ubuntu.com/p/Cwnn3SbmWQ/</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 17:44.</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>Community Charter</h3> -<p>The discussion about "Community Charter" started at 17:51.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/">https://bugs.launchpad.net/cloud-init/</a>?field.tag=bitesize </li> -<li><strong>ACTION</strong>: bbsw seed initial community charter bitesize bugs</li> -</ul> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 18:02.</p> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (118)</li> -<li>robjo (16)</li> -<li>ubot5 (13)</li> -<li>Odd_Bloke (11)</li> -<li>meetingology (6)</li> -<li>smoser (5)</li> -<li>rharper (0)</li> -</ul> -<h2>Full Log</h2> -<p>17:30 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>17:30 <code>&lt;meetingology&gt;</code> Meeting started Tue Jan 7 17:30:28 2020 UTC. The chair is blackboxsw. Information about MeetBot at <a href="http://wiki.ubuntu.com/meetingology.">http://wiki.ubuntu.com/meetingology.</a></p> -<p>17:30 <code>&lt;meetingology&gt;</code> </p> -<p>17:30 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> #chair Odd_Bloke</p> -<p>17:30 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> #chair rharper</p> -<p>17:30 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw rharper</p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> Welcome to the first cloud-init community status meeting of 2020. 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>17:31 <code>&lt;Odd_Bloke&gt;</code> usrdev: I'm not 100% sure from that description, could you file a bug using the link in the topic and attach the output of <code>cloud-init collect-logs</code> on an affected instance?</p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> We generally have this meeting ever 2 weeks (outside of intermittent holidays)... You can always find the next scheduled meeting in the topic of this channel</p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> Let</p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> Let</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> Let's schedule the next meeting now as well</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> Any objections to Jan 21 ?</p> -<p>17:33 <code>&lt;robjo&gt;</code> Look I'm not late ;)</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> ok topic set for next meeting</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> nope, just me robjo :) welcome to the party</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> as always previous meeting minutes are here.</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2019-12-10.html#status-2019-12-10">https://cloud-init.github.io/status-2019-12-10.html#status-2019-12-10</a></p> -<p>17:34 <code>&lt;blackboxsw&gt;</code> topics for this round: Feel free to interject/suggest other topics 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>17:34 <code>&lt;robjo&gt;</code> The move to Tuesday creates a conflict for me for the last 15 minutes of the meeting. Generally I don't think that's an issue as we are often done in less than 1 hour, just pointing out that usually I have to leave 15 minutes early</p> -<p>17:34 <code>&lt;robjo&gt;</code> not today ;)</p> -<p>17:36 <code>&lt;blackboxsw&gt;</code> +1 robjo. We'll try to keep it snappy :) and if others have conflicts we can certainly touch on shifting the schedule a bit. We generally have a conflict at 1 hr before this meeting, which is the only reason it isn't 1 hr earlier</p> -<p>17:36 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> last round: rharper to confirm <a href="https://github.com/canonical/cloud-init/pull/42">https://github.com/canonical/cloud-init/pull/42</a> can land. COMPLETED</p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> action2: upstream core-devs to decide about whether a PR can land if any upstream dev still has 'requested changes'</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: started writing up a spec/procedure for PR review and he is currently working on adding a documentation addition PR to <a href="http://cloudinit.readthedocs.io">http://cloudinit.readthedocs.io</a> that will describe the workflow for a PR to get from proposed -&gt;` merged.</p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> that PR should likely be up this week for review if folks are watching our review queue</p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> #link <a href="https://github.com/cloud-init/cloud-init/pulls">https://github.com/cloud-init/cloud-init/pulls</a></p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> No other actions from the previous meeting in December.</p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>17:40 <code>&lt;blackboxsw&gt;</code> recent commits that made it into tip: found via git log --since 12-10-2019</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> let's see if I get throttled for spam</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> - freebsd: fix create_group() cmd (#146) [Gonéri Le Bouder]</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> - doc: make apt_update example consistent (#154)</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> - doc: add modules page toc with links (#153) (LP: #1852456)</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> - Add support for the amazon variant in cloud.cfg.tmpl (#119)</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> [Frederick Lefebvre]</p> -<p>17:41 <code>&lt;ubot5&gt;</code> Launchpad bug 1852456 in cloud-init "doc: list of modules is no longer present" [Medium,Triaged] <a href="https://launchpad.net/bugs/1852456">https://launchpad.net/bugs/1852456</a></p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> heh</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> - freebsd: fix create_group() cmd (#146) [Gonéri Le Bouder]</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 - doc: make apt_update example consistent (#154)</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 - doc: add modules page toc with links (#153) (LP: #1852456)</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 - Add support for the amazon variant in cloud.cfg.tmpl (#119)</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 [Frederick Lefebvre]</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 - ci: remove Python 2.7 from CI runs (#137)</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 - modules: drop cc_snap_config config module (#134)</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 - migrate-lp-user-to-github: ensure Launchpad repo exists (#136)</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 - docs: add initial troubleshooting to FAQ (#104) [Joshua Powers]</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 - doc: update cc_set_hostname frequency and descrip (#109)</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 [Joshua Powers] (LP: #1827021)</p> -<p>17:41 <code>&lt;ubot5&gt;</code> Launchpad bug 1827021 in cloud-init "SSH Documentation should mention "Host Key"" [Medium,Triaged] <a href="https://launchpad.net/bugs/1827021">https://launchpad.net/bugs/1827021</a></p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> - ci: emit names of tests run in Travis (#120)</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 - Release 19.4 (LP: #1856761)</p> -<p>17:41 <code>&lt;ubot5&gt;</code> Launchpad bug 1856761 in cloud-init "Release 19.4" [Undecided,Fix released] <a href="https://launchpad.net/bugs/1856761">https://launchpad.net/bugs/1856761</a></p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 - rbxcloud: fix dsname in RbxCloud [Adam Dobrawy] (LP: #1855196)</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 - tests: Add tests for value of dsname in datasources [Adam Dobrawy]</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 - apport: Add RbxCloud ds [Adam Dobrawy]</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 - docs: Updating index of datasources [Adam Dobrawy]</p> -<p>17:41 <code>&lt;ubot5&gt;</code> Launchpad bug 1855196 in cloud-init "RBXCloud has no dsname defined, so datasource cannot be properly detected." [Low,Triaged] <a href="https://launchpad.net/bugs/1855196">https://launchpad.net/bugs/1855196</a></p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 - docs: Fix anchor of datasource_rbx [Adam Dobrawy]</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 - settings: Add RbxCloud [Adam Dobrawy]</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 - doc: specify _ over - in cloud config modules</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> 10:41 [Joshua Powers] (LP: #1293254)</p> -<p>17:41 <code>&lt;ubot5&gt;</code> Launchpad bug 1293254 in cloud-init "style guide on dashes vs underscores in cloud-init" [Low,Fix released] <a href="https://launchpad.net/bugs/1293254">https://launchpad.net/bugs/1293254</a></p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - tools: Detect python to use via env in migrate-lp-user-to-github</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> [Adam Dobrawy]</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - Partially revert "fix unlocking method on FreeBSD" (#116)</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - tests: mock uid when running as root (#113)</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> [Joshua Powers] (LP: #1856096)</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - cloudinit/netinfo: remove unused getgateway (#111)</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - docs: clear up apt config sections (#107) [Joshua Powers] (LP: #1832823)</p> -<p>17:42 <code>&lt;ubot5&gt;</code> Launchpad bug 1856096 in cloud-init "unittest failure when running tests as root: no such file or dir: 'ud'" [High,Fix released] <a href="https://launchpad.net/bugs/1856096">https://launchpad.net/bugs/1856096</a></p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - doc: add kernel command line option to user data (#105)</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> [Joshua Powers] (LP: #1846524)</p> -<p>17:42 <code>&lt;ubot5&gt;</code> Launchpad bug 1832823 in cloud-init "docs: confusing heading "Add apt repositories"" [Low,Fix released] <a href="https://launchpad.net/bugs/1832823">https://launchpad.net/bugs/1832823</a></p> -<p>17:42 <code>&lt;ubot5&gt;</code> Launchpad bug 1846524 in cloud-init "docs: cloud-init user-data docs should mention kernel cmdline options" [Wishlist,Fix released] <a href="https://launchpad.net/bugs/1846524">https://launchpad.net/bugs/1846524</a></p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - config/cloud.cfg.d: update README [Joshua Powers] (LP: #1855006)</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - azure: avoid re-running cloud-init when instance-id is byte-swapped</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> (#84) [AOhassan]</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - fix unlocking method on FreeBSD [Igor Galić] (LP: #1854594)</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - debian: add reference to the manpages [Joshua Powers]</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - ds_identify: if /sys is not available use dmidecode (#42)</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> [Igor Galić] (LP: #1852442)</p> -<p>17:42 <code>&lt;ubot5&gt;</code> Launchpad bug 1855006 in cloud-init "config/cloud.cfg.d/README says "All files" rather than "*.cfg"" [Low,Fix released] <a href="https://launchpad.net/bugs/1855006">https://launchpad.net/bugs/1855006</a></p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - docs: add cloud-id manpage [Joshua Powers]</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - docs: add cloud-init-per manpage [Joshua Powers]</p> -<p>17:42 <code>&lt;ubot5&gt;</code> Launchpad bug 1854594 in cloud-init "lock passwd implemented wrong on FreeBSD" [Medium,Fix released] <a href="https://launchpad.net/bugs/1854594">https://launchpad.net/bugs/1854594</a></p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - docs: add cloud-init manpage [Joshua Powers]</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - docs: add additional details to per-instance/once [Joshua Powers]</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - Merge pull request #96 from fred-lefebvre/master [Joshua Powers]</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - Update doc-requirements.txt [Joshua Powers]</p> -<p>17:42 <code>&lt;ubot5&gt;</code> Launchpad bug 1852442 in cloud-init "ds-identify uses the /sys filesystem which is linux specific and non-portable" [Undecided,Fix released] <a href="https://launchpad.net/bugs/1852442">https://launchpad.net/bugs/1852442</a></p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> - doc-requirements: add missing dep [Joshua Powers]</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> Ok that should do it.</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> maybe best to just pastebin next time</p> -<p>17:43 <code>&lt;robjo&gt;</code> yup</p> -<p>17:43 <code>&lt;blackboxsw&gt;</code> lots of doc changes as you can see. dropping python 2.7 automatic testing</p> -<p>17:44 <code>&lt;blackboxsw&gt;</code> some additional FreeBSD enablement work landed too (thanks Goneri &amp;&amp; meena )</p> -<p>17:44 <code>&lt;blackboxsw&gt;</code> total changelog since last meeting:</p> -<p>17:44 <code>&lt;blackboxsw&gt;</code> #link <a href="https://paste.ubuntu.com/p/Cwnn3SbmWQ/">https://paste.ubuntu.com/p/Cwnn3SbmWQ/</a></p> -<p>17:44 <code>&lt;blackboxsw&gt;</code> much better</p> -<p>17:44 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>17:45 <code>&lt;blackboxsw&gt;</code> We've dusted off our shoes and will get back into using our Trello board more frequently for the immediate updates for what we are currently working.</p> -<p>17:45 <code>&lt;blackboxsw&gt;</code> New Year's resolution and all</p> -<p>17:45 <code>&lt;blackboxsw&gt;</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>17:46 <code>&lt;blackboxsw&gt;</code> expect to see more cloud-init cards migrating through the lanes of the board. Expectation as well is that we'll drop the backlog and ideas lanes and keep the board a simple kanban of what is in progress, review and done</p> -<p>17:47 <code>&lt;blackboxsw&gt;</code> Also note I'm going to drop the community charter lane and create bugs for each item, tagging them 'bitesize' so that quick drivebys of developers that want to contribute can search bugs for those straightforward tasks</p> -<p>17:47 <code>&lt;blackboxsw&gt;</code> that said, some high level goals upstream is working:</p> -<p>17:48 <code>&lt;blackboxsw&gt;</code> - cloud-init one-shot daemon work</p> -<p>17:48 <code>&lt;blackboxsw&gt;</code> - cloud-init network hotplug handling</p> -<p>17:48 <code>&lt;blackboxsw&gt;</code> - boot performance improvements</p> -<p>17:49 <code>&lt;blackboxsw&gt;</code> - github automation and tooling improvements for expedited reviews and process</p> -<p>17:50 <code>&lt;blackboxsw&gt;</code> I think that plus reviewing the PR active review queues will keep folks busy for the next 2 weeks :)</p> -<p>17:51 <code>&lt;blackboxsw&gt;</code> we will likely be adding a cloud-init SRU into xenial, bionic, disco, eoan into the mix as well</p> -<p>17:51 <code>&lt;blackboxsw&gt;</code> #topic Community Charter</p> -<p>17:52 <code>&lt;blackboxsw&gt;</code> So generally I'd be pointing to the trello lane "Community low hanging fruit" but I hope to convert those cards to bugs today. So let's say community ongoing efforts fall into two camps"</p> -<p>17:53 <code>&lt;blackboxsw&gt;</code> 1. add json schema validation to missing cloudinit/config/cc_*py modules. ( I think there are about 45 remaining modules that need json schema for syntax validation)</p> -<p>17:53 <code>&lt;blackboxsw&gt;</code> 2. doc scrub and update for datasources in read the docs</p> -<p>17:54 <code>&lt;blackboxsw&gt;</code> All of these items can easily be worked in parallel, which is why they are a good set of tasks for the greater community</p> -<p>17:55 <code>&lt;blackboxsw&gt;</code> Expect to find them by searching cloud-init bugs for bitesize tag</p> -<p>17:55 <code>&lt;robjo&gt;</code> With bugs remaining in launchpad, would it be a good idea to have things like the schema validation not as bugs but issues in GitHub?</p> -<p>17:55 <code>&lt;robjo&gt;</code> that would make them more visible IMHO</p> -<p>17:55 <code>&lt;robjo&gt;</code> and those are not really bugs nor is it pressing</p> -<p>17:56 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/">https://bugs.launchpad.net/cloud-init/</a>?field.tag=bitesize</p> -<p>17:57 <code>&lt;blackboxsw&gt;</code> robjo: good suggestion. I think we were trying to avoid the confusion of having two places for bugs (launchpad bugs and github issues) That is a good point though, and maybe it's worth a mailing list discussion to get others to weight in.</p> -<p>17:58 <code>&lt;Odd_Bloke&gt;</code> I would be -1 on enabling issues, we would spend our entire lives telling people to report in Launchpad instead.</p> -<p>17:59 <code>&lt;Odd_Bloke&gt;</code> I totally understand wanting to separate "bugs" and "development tasks", though.</p> -<p>18:00 <code>&lt;Odd_Bloke&gt;</code> But I don't think we have a <em>great</em> way of doing that which doesn't end up with a confusing experience for bug reporters.</p> -<p>18:00 <code>&lt;robjo&gt;</code> True that people will equate issues in GitHub with bugs and thus file problems there rather than launchpad, it's a two edged sword</p> -<p>18:00 <code>&lt;blackboxsw&gt;</code> right, I think designation is there. We could also add a link to community charter bugs to the top-level README.md for the github project. Just so there is a close breadcrumb in github to get to those items</p> -<p>18:01 <code>&lt;Odd_Bloke&gt;</code> Our plan is to assess how this is working in a month or two, so if it's not working well then we can figure something else out.</p> -<p>18:01 <code>&lt;blackboxsw&gt;</code> I think the designation of "community development tasks" is there by using bitesize tag or some equivalent</p> -<p>18:02 <code>&lt;blackboxsw&gt;</code> #ACTION bbsw seed initial community charter bitesize bugs</p> -<p>18:02 * meetingology bbsw seed initial community charter bitesize bugs</p> -<p>18:02 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>18:02 <code>&lt;robjo&gt;</code> Well, "community development tasks" is a bit mis-leading, after all the core team should be part of the "community" right?</p> -<p>18:03 <code>&lt;robjo&gt;</code> So everything is really a "community development tasks", just that some things are easier than others ;)</p> -<p>18:03 <code>&lt;blackboxsw&gt;</code> robjo: yes absolutely. right... I've seen some projects use 'goodfirstbug' or something like that too</p> -<p>18:04 <code>&lt;blackboxsw&gt;</code> just something to reduce the barrier to involvement for anyone wanting to contribute</p> -<p>18:05 <code>&lt;blackboxsw&gt;</code> and yes, core team should be accountable to work on some of those community charter tasks when time permits</p> -<p>18:05 <code>&lt;robjo&gt;</code> Yes, I think it is important to label the "easy" stuff to help people find a place to get started</p> -<p>18:05 <code>&lt;blackboxsw&gt;</code> so that hopefully next cloud-init summit we can set a charter for something else</p> -<p>18:06 <code>&lt;robjo&gt;</code> just based on experience there are a lot of people that are sensitive to wording and we don't really want to get into the bikeshedding that comes along with such situations</p> -<p>18:07 <code>&lt;blackboxsw&gt;</code> for those reading, office hours is a time of open and unstructured discussion. core cloud-init devs will have eyes on the channel to field questions, concerns, feature or bug discussions. Participate at will. In the absence of any ongoing discussions, upstream will groom/review the active review queue @ <a href="https://git.io/JeVed">https://git.io/JeVed</a> |</p> -<p>18:09 <code>&lt;Odd_Bloke&gt;</code> Honestly losing my mind over this bug: <a href="https://bugs.launchpad.net/cloud-init/+bug/1858615">https://bugs.launchpad.net/cloud-init/+bug/1858615</a></p> -<p>18:09 <code>&lt;ubot5&gt;</code> Ubuntu bug 1858615 in cloud-init "Fail to boot when NoCloud datasource is included" [Undecided,New]</p> -<p>18:09 <code>&lt;Odd_Bloke&gt;</code> The board reboots if you use dmidecode!</p> -<p>18:10 <code>&lt;Odd_Bloke&gt;</code> smoser: As you said, that's a regression. Do you think it follows that the fix should be in cloud-init?</p> -<p>18:10 <code>&lt;Odd_Bloke&gt;</code> Because I don't know how you deal with something that broken from where we are in the stack. :/</p> -<p>18:10 <code>&lt;Odd_Bloke&gt;</code> (Unless we think this is enough evidence that we can't reliably use dmidecode on aarch64, then I guess it is on us to stop doing that. :( )</p> -<p>18:10 <code>&lt;robjo&gt;</code> This was probably in the e-mail by rharper I have not yet read, but I'll ask anyway ;)</p> -<p>18:11 <code>&lt;robjo&gt;</code> I think I had some pending merge proposals in launchpad and patches, did these "magically" make their way into GitHub? DO I need to sort out where hings were?</p> -<p>18:11 <code>&lt;smoser&gt;</code> i've heard "board reboots if you use dmidecode" before.</p> -<p>18:12 <code>&lt;smoser&gt;</code> and maybe even cloud-init skipped calling dmidecode on aarch64 to avoid that.</p> -<p>18:12 <code>&lt;smoser&gt;</code> but that is sheer non-sense</p> -<p>18:12 <code>&lt;Odd_Bloke&gt;</code> Very glad that boards like this are going to be in the walls of every building in 5 years. ;)</p> -<p>18:12 <code>&lt;smoser&gt;</code> umm..... fix your hardware ?</p> -<p>18:13 <code>&lt;blackboxsw&gt;</code> other dmidecode issues on other hardware here too <a href="https://bugs.launchpad.net/qemu/+bug/1243287">https://bugs.launchpad.net/qemu/+bug/1243287</a></p> -<p>18:13 <code>&lt;ubot5&gt;</code> Ubuntu bug 1243287 in QEMU "[KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail" [Undecided,Fix released]</p> -<p>18:13 <code>&lt;smoser&gt;</code> its more forgivable because dmidecode is priviledged but i swear that all it does is <em>read</em> /dev/mem</p> -<p>18:16 <code>&lt;blackboxsw&gt;</code> robjo: for your pending merge proposals we'd like to see you propose against github if possible. Looking for a run of ./tools/migrate-lp-user-to-github robjo <code>&lt;your_GITHUB_USERNAME&gt;</code> to get your github user included as a CLA signer</p> -<p>18:17 <code>&lt;blackboxsw&gt;</code> then we have Conributor License Agreement accountability and can start merging those branches on the github side</p> -<p>18:17 <code>&lt;robjo&gt;</code> Yesh I haven't migrated to the GitHub repo.... even in 2020 the 24 hour/day limitation remains, darn it ;)</p> -<p>18:17 <code>&lt;robjo&gt;</code> I'll get at least my migration to GitHub done this week, possibly even this afternoon</p> -<p>18:18 <code>&lt;blackboxsw&gt;</code> heh, absolutely, and actually I mistyped your migrate cmd: ./tools/migrate-lp-user-to-github rjschwei <code>&lt;YOUR_GITHUB_USERNAME&gt;</code></p> -<p>18:39 <code>&lt;blackboxsw&gt;</code> ok think that about wraps the meeting for today. Happy new year folks! Thanks for dropping in!</p> -<p>18:39 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2019-12-10T17:17:00+00:002019-12-10T17:17:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2019-12-10:/status-2019-12-10.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 10 Dec at 17:17 &mdash; 18:16 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-12-10-17.17.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-12-10-17.17.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 17:22.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-11-26.html#status-2019-11-26">https://cloud-init.github.io/status-2019-11-26.html#status-2019-11-26 …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 10 Dec at 17:17 &mdash; 18:16 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-12-10-17.17.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-12-10-17.17.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 17:22.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-11-26.html#status-2019-11-26">https://cloud-init.github.io/status-2019-11-26.html#status-2019-11-26</a> </li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 17:28.</p> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 17:31.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://lists.launchpad.net/cloud-init/msg00236.html">https://lists.launchpad.net/cloud-init/msg00236.html</a> </li> -<li><strong>LINK</strong>: <a href="https://cloudinit.readthedocs.io/en/latest/topics/hacking.html">https://cloudinit.readthedocs.io/en/latest/topics/hacking.html</a> </li> -</ul> -<h3>Community Charter</h3> -<p>The discussion about "Community Charter" started at 17:40.</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>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 17:45.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://git.io/JeVed">https://git.io/JeVed</a> </li> -<li><strong>ACTION</strong>: rharper confirm no concerns on <a href="https://github.com/canonical/cloud-init/pull/42">https://github.com/canonical/cloud-init/pull/42</a> and that PR can land.</li> -<li><strong>ACTION</strong>: upstream core-devs to decide about whether a PR can land if any upstream dev still has 'requested changes'</li> -</ul> -<h2>Vote results</h2> -<h2>Action items, by person</h2> -<ul> -<li>rharper</li> -<li>rharper confirm no concerns on <a href="https://github.com/canonical/cloud-init/pull/42">https://github.com/canonical/cloud-init/pull/42</a> and that PR can land.</li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (79)</li> -<li>meetingology (7)</li> -<li>meena (5)</li> -<li>ubot5 (3)</li> -<li>Odd_Bloke (2)</li> -<li>rharper (1)</li> -</ul> -<h2>Full Log</h2> -<p>17:17 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>17:17 <code>&lt;meetingology&gt;</code> Meeting started Tue Dec 10 17:17:14 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>17:17 <code>&lt;meetingology&gt;</code> </p> -<p>17:17 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>17:18 <code>&lt;blackboxsw&gt;</code> Welcome folks to another cloud-init status meeting. Probably the last one of the year I presume due to upcoming Holidays in two weeks</p> -<p>17:18 <code>&lt;blackboxsw&gt;</code> #chair rharper</p> -<p>17:18 <code>&lt;meetingology&gt;</code> Current chairs: blackboxsw rharper</p> -<p>17:18 <code>&lt;blackboxsw&gt;</code> #chair Odd_Bloke</p> -<p>17:18 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw rharper</p> -<p>17:18 <code>&lt;rharper&gt;</code> o/</p> -<p>17:18 <code>&lt;blackboxsw&gt;</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>17:19 <code>&lt;blackboxsw&gt;</code> Let's start the meeting with setting the next meeting time</p> -<p>17:19 <code>&lt;blackboxsw&gt;</code> day/time</p> -<p>17:20 <code>&lt;blackboxsw&gt;</code> I think most of upstream is out the last two weeks of December. Shall we try January 7th?</p> -<p>17:20 <code>&lt;blackboxsw&gt;</code> Anyone opposed can voice their discontent as I remember the keystrokes to set the topic of the channel ;)_</p> -<p>17:21 <code>&lt;blackboxsw&gt;</code> I also dropped 19.3 upstream release date from the channel topic as "that's soooo November"</p> -<p>17:22 <code>&lt;blackboxsw&gt;</code> topics for this round: Feel free to interject/suggest other topics 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>17:22 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>17:22 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>17:23 <code>&lt;blackboxsw&gt;</code> and oops, forgot to publish meeting minutes from last session.</p> -<p>17:23 <code>&lt;blackboxsw&gt;</code> doing that now.</p> -<p>17:24 <code>&lt;meena&gt;</code> is it meeting time or did I miss it?</p> -<p>17:25 <code>&lt;Odd_Bloke&gt;</code> meena: It's happening as we speak.</p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> ok sorry for the delay. just pushed published meeting minutes</p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2019-11-26.html#status-2019-11-26">https://cloud-init.github.io/status-2019-11-26.html#status-2019-11-26</a></p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> ok so previous actions from last meeting:</p> -<p>17:28 <code>&lt;blackboxsw&gt;</code> no unresolved actions listed</p> -<p>17:28 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> found via git log --since 11.26.2019</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - dhcp: Support RedHat dhcp rfc3442 lease format for option 121 (#76)</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> [Eric Lafontaine] (LP: #1850642)</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - network_state: handle empty v1 config (#45) (LP: #1852496)</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - Merge pull request #94 from gaughen/patch-1 [Joshua Powers]</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - removed a couple of "the"s [gaughen]</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - docs: fix line length and remove highlighting [Joshua Powers]</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - docs: Add security.md to readthedocs [Joshua Powers]</p> -<p>17:29 <code>&lt;ubot5&gt;</code> Launchpad bug 1850642 in cloud-init "No support for classless-static-routes on centos 7" [Medium,Triaged] <a href="https://launchpad.net/bugs/1850642">https://launchpad.net/bugs/1850642</a></p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - Multiple file fix for AuthorizedKeysFile config (#60) [Eduardo Otubo]</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - Merge pull request #88 from OddBloke/travis [Joshua Powers]</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - Revert "travis: only run CI on pull requests"</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - doc: update links on README.md [Joshua Powers]</p> -<p>17:29 <code>&lt;ubot5&gt;</code> Launchpad bug 1852496 in cloud-init (Ubuntu) "nocloud network-config mishandles empty config" [Low,In progress] <a href="https://launchpad.net/bugs/1852496">https://launchpad.net/bugs/1852496</a></p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - doc: Updates to wording of README.md [Joshua Powers]</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - Add security.md [Joshua Powers]</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - setup.py: Amazon Linux sets libexec to /usr/libexec (#52)</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> [Frederick Lefebvre]</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - Fix linting failure in test_url_helper (#83) [Eric Lafontaine]</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - url_helper: read_file_or_url should pass headers param into readurl</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> (#66) (LP: #1854084)</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - dmidecode: log result <em>after</em> stripping n [Igor Galić]</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> - cloud_tests: add azure platform support to integration tests</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> [ahosmanmsft]</p> -<p>17:29 <code>&lt;ubot5&gt;</code> Launchpad bug 1854084 in cloud-init "Headers no longer passed through read_file_or_url" [Undecided,Fix committed] <a href="https://launchpad.net/bugs/1854084">https://launchpad.net/bugs/1854084</a></p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> thanks for all the FreeBSD work landing, utility improvements, caching and doc changes. + the dhcp lease format updates</p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> Generally upstream is doing a fair job of getting reviews to the community for PRs, though lately we've been spending a few cycles on SRU validation for cloud-init 19.4.31 into Ubuntu Xenial, Bionic, Disco and Eoan.</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> expectation is that we should be able to clear this SRU validation today/tomorrow and get back onto the review queue in github for cloud-init</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> most major cloud-platforms have passed validation with no regressions, so risk is low with this release</p> -<p>17:34 <code>&lt;blackboxsw&gt;</code> oops cloud-init 19.3.41 not 19.4.31</p> -<p>17:35 <code>&lt;blackboxsw&gt;</code> there is plenty of work in flight by meena (FreeBSD improvements) and ahosmanMSFT (Azure instance-id work). that we hope to get reviewed and landed.</p> -<p>17:36 <code>&lt;blackboxsw&gt;</code> community notice: Reminder we are working toward a 19.4 upstream release by end of year. So if there are bits/features that you hope to make the cut. please get those branches in shape by next tuesday Decemeber 17th</p> -<p>17:36 <code>&lt;blackboxsw&gt;</code> #link <a href="https://lists.launchpad.net/cloud-init/msg00236.html">https://lists.launchpad.net/cloud-init/msg00236.html</a></p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> community notice: Also a reminder that cloud-inig 19.4 will be the last release that claims official support for py2.7</p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> in January, tip of cloud-init will be allowed to drift from python2.7 support and tox -e py27 will no longer be exercised by upstream CI</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: or rharper anyything else in-progress at the moment?</p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> also, anyone interested in cloud-init development, please run tools/migrate-lp-user-to-github as mentioned in the hacking guide to make sure we can account for the CLA (contributor license agreement) for cloud-init</p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloudinit.readthedocs.io/en/latest/topics/hacking.html">https://cloudinit.readthedocs.io/en/latest/topics/hacking.html</a></p> -<p>17:40 <code>&lt;blackboxsw&gt;</code> #topic Community Charter</p> -<p>17:40 <code>&lt;blackboxsw&gt;</code> reminder on 19.4 release covered above, and getting your github account authorized for cloud-init conributions....</p> -<p>17:41 <code>&lt;Odd_Bloke&gt;</code> Nothing from me!</p> -<p>17:41 <code>&lt;meena&gt;</code> goneri and i have been working on / testing his freebsd render</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> for folks with time to burn and bite-sized branches/fixes. we've got a lane on our trello board that gives a variety of fixes that the community can grab if they are looking for quick suggestions. "Community low-hanging fruit"</p> -<p>17:42 <code>&lt;blackboxsw&gt;</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>17:42 <code>&lt;blackboxsw&gt;</code> meena: Goneri yes and thanks for the continued efforts there. A lot of good is coming out for cloud-init upstream as a result.</p> -<p>17:42 <code>&lt;meena&gt;</code> Goneri removed a lot of code, but from what i gather, that code is still used elsewhere</p> -<p>17:43 <code>&lt;meena&gt;</code> could someone explain why our where our how</p> -<p>17:43 <code>&lt;blackboxsw&gt;</code> as always, any community member is encouraged to review other PRs from devs. All reviews and input welcome.</p> -<p>17:44 <code>&lt;blackboxsw&gt;</code> meena: I'm not sure I follow, are you referring to a specific branch?</p> -<p>17:44 <code>&lt;blackboxsw&gt;</code> or just where stale snapshots or cloud-init code lives on certain distros?</p> -<p>17:45 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>17:45 <code>&lt;blackboxsw&gt;</code> might as well kick the topic and open office hours for general cloud-init discussions, questions, bug/feature work etc.</p> -<p>17:46 <code>&lt;blackboxsw&gt;</code> some upstream devs will have eyes/time available for discussion around anything cloud-init. This time will also be spent grooming the active review queue @ <a href="https://git.io/JeVed">https://git.io/JeVed</a></p> -<p>17:46 <code>&lt;blackboxsw&gt;</code> #link <a href="https://git.io/JeVed">https://git.io/JeVed</a></p> -<p>17:48 <code>&lt;meena&gt;</code> blackboxsw: <a href="https://github.com/canonical/cloud-init/pull/61#pullrequestreview-329139891">https://github.com/canonical/cloud-init/pull/61#pullrequestreview-329139891</a></p> -<p>17:48 <code>&lt;blackboxsw&gt;</code> checking</p> -<p>17:52 <code>&lt;blackboxsw&gt;</code> meena: so Distro._bring_up_interface() is called by Distro._bring_up_interfaces() base class via Distro.apply_network</p> -<p>17:59 <code>&lt;blackboxsw&gt;</code> which is called from Init.apply_network_config which gets run during "cloud-init init" when network is brought up</p> -<p>18:06 <code>&lt;blackboxsw&gt;</code> I think <a href="https://github.com/canonical/cloud-init/pull/42">https://github.com/canonical/cloud-init/pull/42</a> looks ready to merge. rharper has an outstanding "changes requested" but I believe those have been fixed. rharper I'll defer to you on this one</p> -<p>18:08 <code>&lt;blackboxsw&gt;</code> and policy question on reviews: if we get one upstream core-dev +1 can we proceed to land the branch as long as the "changes requested" from other upstream core seem to be resolved?</p> -<p>18:09 <code>&lt;blackboxsw&gt;</code> I'd vote that most recent core-dev on the PR that +1's can squash merge if they see that any prior core-dev's concerns seem to be addressed</p> -<p>18:12 <code>&lt;blackboxsw&gt;</code> I think I'll add an action for next meeting to make sure we iron out review/merge policy so PRs don't sit stale</p> -<p>18:13 <code>&lt;blackboxsw&gt;</code> #action rharper confirm no concerns on <a href="https://github.com/canonical/cloud-init/pull/42">https://github.com/canonical/cloud-init/pull/42</a> and that PR can land.</p> -<p>18:13 * meetingology rharper confirm no concerns on <a href="https://github.com/canonical/cloud-init/pull/42">https://github.com/canonical/cloud-init/pull/42</a> and that PR can land.</p> -<p>18:14 <code>&lt;blackboxsw&gt;</code> #action upstream core-devs to decide about whether a PR can land if any upstream dev still has 'requested changes'</p> -<p>18:14 * meetingology upstream core-devs to decide about whether a PR can land if any upstream dev still has 'requested changes'</p> -<p>18:16 <code>&lt;blackboxsw&gt;</code> ok I <em>think</em> that about wraps the meeting. Merry Christmas, Happy Hanukkah, Happy New Year and all that good stuff. See you all online.</p> -<p>18:16 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2019-11-26T17:23:00+00:002019-11-26T17:23:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2019-11-26:/status-2019-11-26.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 26 Nov at 17:23 &mdash; 19:00 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-11-26-17.23.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-11-26-17.23.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 17:28.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-10-29.html#status-2019-10-29">https://cloud-init.github.io/status-2019-10-29.html#status-2019-10-29 …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 26 Nov at 17:23 &mdash; 19:00 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-11-26-17.23.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-11-26-17.23.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 17:28.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-10-29.html#status-2019-10-29">https://cloud-init.github.io/status-2019-10-29.html#status-2019-10-29</a> </li> -<li><strong>LINK</strong>: <a href="https://lists.launchpad.net/cloud-init/msg00231.html">https://lists.launchpad.net/cloud-init/msg00231.html</a> </li> -<li><strong>LINK</strong>: <a href="https://cloudinit.readthedocs.io/en/latest/topics/hacking.html">https://cloudinit.readthedocs.io/en/latest/topics/hacking.html</a> </li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 17:36.</p> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 17:39.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bug/1854084">https://bugs.launchpad.net/cloud-init/+bug/1854084</a> </li> -<li><strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pull/48">https://github.com/canonical/cloud-init/pull/48</a> </li> -<li><strong>LINK</strong>: <a href="https://github.com/canonical/cloud-init/pull/47">https://github.com/canonical/cloud-init/pull/47</a> </li> -</ul> -<h3>Community Charter</h3> -<p>The discussion about "Community Charter" started at 17:46.</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 17:52.</p> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 17:52.</p> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (124)</li> -<li>ubot5 (16)</li> -<li>ahosmanMSFT (5)</li> -<li>meena (5)</li> -<li>chillysurfer (5)</li> -<li>meetingology (4)</li> -<li>Goneri (1)</li> -<li>Odd_Bloke (0)</li> -</ul> -<h2>Full Log</h2> -<p>17:23 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>17:23 <code>&lt;meetingology&gt;</code> Meeting started Tue Nov 26 17:23:40 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>17:23 <code>&lt;meetingology&gt;</code> </p> -<p>17:23 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>17:24 <code>&lt;blackboxsw&gt;</code> #chair Odd_Bloke</p> -<p>17:24 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw</p> -<p>17:24 <code>&lt;blackboxsw&gt;</code> Hi folks welcome to another cloud-init status meeting.</p> -<p>17:24 <code>&lt;blackboxsw&gt;</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>17:25 <code>&lt;blackboxsw&gt;</code> And as you've likely heard, we are shifting this meeting by +1 hr for the season to avoid meeting collisions with some of the upstream devs</p> -<p>17:25 <code>&lt;blackboxsw&gt;</code> I'll set the topic for next meeting so we don't forget</p> -<p>17:28 <code>&lt;blackboxsw&gt;</code> so Dec 10th, two weeks from today, same time as today</p> -<p>17:28 <code>&lt;blackboxsw&gt;</code> without further ado, let's jump into things</p> -<p>17:28 <code>&lt;blackboxsw&gt;</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>17:28 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>17:28 <code>&lt;blackboxsw&gt;</code> I'm going from our last meeting minutes at the following url</p> -<p>17:28 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2019-10-29.html#status-2019-10-29">https://cloud-init.github.io/status-2019-10-29.html#status-2019-10-29</a></p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> blackboxsw to 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>17:29 <code>&lt;blackboxsw&gt;</code> I did forward the proper Microsoft channel contact to other Microsoft dev teams working on cloud-init</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> so I think thats COMPLETE</p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> Also to note is that cloud image builds though are still stale for Azure &amp; Ec2 on focal. There are a couple of bugs in the image build process that Canonical's cloud image team is sorting to get those image builders unblocked</p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> Xenial, Bionic, Eoan images all look up to date</p> -<p>17:32 <code>&lt;chillysurfer&gt;</code> bug reports and issues are still going to be reported through launchpad right?</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> previous-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. Resolved. Upstream decided that it was going to be a bit of a maintenance cost to have a full table of all distributions and all versions of cloud-init as well as the planned support plan.</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> chillysurfer: +1 yes please do. file away and we'll tackle that</p> -<p>17:32 <code>&lt;chillysurfer&gt;</code> blackboxsw: great thanks!</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> previous-action: mailing list update to cloud-init community about procedure/timeline for migration to github. rharper took care of that per</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> #link <a href="https://lists.launchpad.net/cloud-init/msg00231.html">https://lists.launchpad.net/cloud-init/msg00231.html</a></p> -<p>17:34 <code>&lt;blackboxsw&gt;</code> Again for folks, we have moved cloud-init upstream to github for code and CI. Launchpad still being used for package build recipes and bugs/ issues</p> -<p>17:35 <code>&lt;blackboxsw&gt;</code> If you have signed the CLA (thanks ahosmanMSFT) then we need to link your github account to the Lauchpad username you signed the CLA with. See the hacking doc for more information</p> -<p>17:35 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloudinit.readthedocs.io/en/latest/topics/hacking.html">https://cloudinit.readthedocs.io/en/latest/topics/hacking.html</a></p> -<p>17:35 <code>&lt;blackboxsw&gt;</code> Think that wraps actions.</p> -<p>17:36 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>17:36 <code>&lt;meena&gt;</code> I've been very slowly working towards better freebsd support</p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> The following branches have landed in tip since last meeting: via git log --since 10.29.2019</p> -<p>17:37 <code>&lt;meena&gt;</code> Goneri has moved his network patch over to github, and a NetBSD patch, tok</p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> - tools: migrate-lp-user-to-github removes repo_dir if created (#35)</p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> - Correct jumbled documentation for cc_set_hostname module (#64)</p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> [do3meli] (LP: #1853543)</p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> - FreeBSD: fix for get_linux_distro() and lru_cache (#59)</p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> [Igor Galić] (LP: #1815030)</p> -<p>17:37 <code>&lt;ubot5&gt;</code> Launchpad bug 1853543 in cloud-init "jumbled documentation for cc_set_hostname module" [Undecided,Fix committed] <a href="https://launchpad.net/bugs/1853543">https://launchpad.net/bugs/1853543</a></p> -<p>17:37 <code>&lt;ubot5&gt;</code> Launchpad bug 1815030 in cloud-init "FreeBSD: Unable to determine distribution" [Undecided,Fix committed] <a href="https://launchpad.net/bugs/1815030">https://launchpad.net/bugs/1815030</a></p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> bah got kicked. let's try that again</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - tools: migrate-lp-user-to-github removes repo_dir if created (#35)</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> 10:37 - Correct jumbled documentation for cc_set_hostname module (#64)</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> 10:37 [do3meli] (LP: #1853543)</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> 10:37 - FreeBSD: fix for get_linux_distro() and lru_cache (#59)</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> 10:37 [Igor Galić] (LP: #1815030)</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> 10:37 - lp-to-git-users: adding do3meli [Dominic Schlegel]</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> 10:37 - ec2: Add support for AWS IMDS v2 (session-oriented) (#55)</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> 10:37 - tests: Fix cloudsigma tests when no dmidecode data is present. (#57)</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> 10:37 - net: IPv6, accept_ra, slaac, stateless (#51)</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> 10:37 [Harald] (LP: #1806014, #1808647)</p> -<p>17:38 <code>&lt;ubot5&gt;</code> Launchpad bug 1808647 in cloud-init "cloud-init hard codes IPV6_AUTOCONF=no, which prevents EC2 instances from getting a v6 default gateway if NetworkManager is disabled" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1808647">https://launchpad.net/bugs/1808647</a></p> -<p>17:38 <code>&lt;ubot5&gt;</code> Launchpad bug 1806014 in cloud-init "[Centos] IPV6_AUTOCONF=no when using dhcp6" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1806014">https://launchpad.net/bugs/1806014</a></p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - docs: Update the configdrive datasource links (#44)</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> [Joshua Powers] (LP: #1852461)</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - lp-to-git-users: adding PengpengSun [Pengpeng Sun]</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - lp-to-git-users: adding trstringer [Thomas Stringer]</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - lp-to-git-users: adding hjensas [Harald Jensås]</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - distro: correctly set usr_lib_exec path for FreeBSD distro (#40)</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> [Igor Galić] (LP: #1852491)</p> -<p>17:38 <code>&lt;ubot5&gt;</code> Launchpad bug 1852461 in cloud-init "Broken links in config-drive docs on RTD" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1852461">https://launchpad.net/bugs/1852461</a></p> -<p>17:38 <code>&lt;ubot5&gt;</code> Launchpad bug 1852491 in cloud-init "usr_lib_exec path is wrong on FreeBSD" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1852491">https://launchpad.net/bugs/1852491</a></p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - azure: support secondary ipv6 addresses (#33)</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - Fix metadata check when local-hostname is null (#32)</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> [Mark Goddard] (LP: #1852100)</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - Merge pull request #38 from blackboxsw/cleanup/run-ci-on-pull-request</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - switch default FreeBSD salt minion pkg from py27 to py36</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> [Dominic Schlegel]</p> -<p>17:38 <code>&lt;ubot5&gt;</code> Launchpad bug 1852100 in cloud-init "Cloud-init fails if metadata local-hostname is null" [Undecided,In progress] <a href="https://launchpad.net/bugs/1852100">https://launchpad.net/bugs/1852100</a></p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - lp-to-git-users: adding igalic [Igor Galić]</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - travis: only run CI on pull requests</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - add data-server dns entry as new metadata server detection [Joshua Hügli]</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - lp-to-git-users: adding chrisglass [Chris Glass]</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - lp-to-git-users: adding larsks [Lars Kellogg-Stedman]</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - Merge pull request #31 from raharper/fix/pycodestyle-tip</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - pycodestyle: remove unused local variable</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - reporting: Using a uuid to enforce uniqueness on the KVP keys. [momousta]</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - docs: touchups in rtd intro and README.md</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - doc: update launchpad git refs to github</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - tools: migrate script needs to write tools/.lp-to-git-user</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - github: drop pull-request template to prepare for migration</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - tools: add migrate-lp-user-to-github script to link LP to github</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - github: new basic project readme</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - Release 19.3 (LP: #1851428)</p> -<p>17:38 <code>&lt;ubot5&gt;</code> Launchpad bug 1851428 in cloud-init "Release 19.3" [Medium,In progress] <a href="https://launchpad.net/bugs/1851428">https://launchpad.net/bugs/1851428</a></p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - azure: support matching dhcp route-metrics for dual-stack ipv4 ipv6</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> (LP: #1850308)</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> - configdrive: fix subplatform config-drive for /config-drive source</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> [David Kindred] (LP: #1849731)</p> -<p>17:38 <code>&lt;ubot5&gt;</code> Launchpad bug 1850308 in cloud-init "cloud-init on azure with dual stack needs to add route-metric for dhcp6 also" [High,Fix committed] <a href="https://launchpad.net/bugs/1850308">https://launchpad.net/bugs/1850308</a></p> -<p>17:38 <code>&lt;ubot5&gt;</code> Launchpad bug 1849731 in cloud-init "Introduction of subplatform around 18.5 broke ConfigDrive" [Undecided,Fix committed] <a href="https://launchpad.net/bugs/1849731">https://launchpad.net/bugs/1849731</a></p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> - DataSourceSmartOS: reconfigure network on each boot</p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> [Mike Gerdts] (LP: #1765801)</p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> - Add config for ssh-key import and consuming user-data [Pavel Zakharov]</p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> - net: fix subnet_is_ipv6() for stateless|stateful</p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> [Harald Jensås] (LP: #1848690)</p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> - OVF: disable custom script execution by default [Xiaofeng Wang]</p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> - cc_puppet: Implement csr_attributes.yaml support [Matthias Baur]</p> -<p>17:39 <code>&lt;ubot5&gt;</code> Launchpad bug 1765801 in cloud-init "network should be optionally reconfigured on every boot" [Undecided,Fix committed] <a href="https://launchpad.net/bugs/1765801">https://launchpad.net/bugs/1765801</a></p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> - cloud-init.service: on centos/fedora/redhat wait on</p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> NetworkManager.service (LP: #1843334)</p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> - azure: Do not lock user on instance id change</p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> [Sam Eiderman] (LP: #1849677)</p> -<p>17:39 <code>&lt;ubot5&gt;</code> Launchpad bug 1848690 in cloud-init "subnet_is_ipv6() function does not work for types ipv6_dhcpv6-stateless|stateful" [Undecided,Fix committed] <a href="https://launchpad.net/bugs/1848690">https://launchpad.net/bugs/1848690</a></p> -<p>17:39 <code>&lt;ubot5&gt;</code> Launchpad bug 1843334 in cloud-init "Change location of DHCP leases in CloudStack provider as it doesn't work for RHEL8" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1843334">https://launchpad.net/bugs/1843334</a></p> -<p>17:39 <code>&lt;ubot5&gt;</code> Launchpad bug 1849677 in cloud-init "azure locks existing user if instance id changes" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1849677">https://launchpad.net/bugs/1849677</a></p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>17:40 <code>&lt;ahosmanMSFT&gt;</code> Looking into this</p> -<p>17:40 <code>&lt;ahosmanMSFT&gt;</code> Launchpad bug 1849677 in cloud-init "azure locks existing user if instance id changes" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1849677">https://launchpad.net/bugs/1849677</a></p> -<p>17:40 <code>&lt;ubot5&gt;</code> Ubuntu bug 1849677 in cloud-init "azure locks existing user if instance id changes" [Medium,Fix committed]</p> -<p>17:40 <code>&lt;blackboxsw&gt;</code> As meena mentioned there is a lot of work going on to improve FreeBSD support.</p> -<p>17:40 <code>&lt;blackboxsw&gt;</code> Thanks do3meli and meena for that herculean effort</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> ahosmanMSFT: also has be working on getting Azure CI up and running. That branch will land just as soon as this meeting is over</p> -<p>17:41 <code>&lt;blackboxsw&gt;</code> we also have landed a significant AWS feature for IMDSv2.</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> It looks like we'll have a bug to sort on that front</p> -<p>17:42 <code>&lt;chillysurfer&gt;</code> bug report just opened up</p> -<p>17:42 <code>&lt;chillysurfer&gt;</code> <a href="https://bugs.launchpad.net/cloud-init/+bug/1854084">https://bugs.launchpad.net/cloud-init/+bug/1854084</a></p> -<p>17:42 <code>&lt;ubot5&gt;</code> Ubuntu bug 1854084 in cloud-init "Headers no longer passed through read_file_or_url" [Undecided,New]</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> thanks chillysurfer !</p> -<p>17:43 <code>&lt;blackboxsw&gt;</code> will get on that today and confirm</p> -<p>17:43 <code>&lt;chillysurfer&gt;</code> blackboxsw: great thanks! let me know what you think when you know some things</p> -<p>17:43 <code>&lt;blackboxsw&gt;</code> will do</p> -<p>17:44 <code>&lt;blackboxsw&gt;</code> also in the "In progress" topic are the WIP branches that rharper has up to lay ground work for opting in to cloud-init hotplug support</p> -<p>17:45 <code>&lt;blackboxsw&gt;</code> #link <a href="https://github.com/canonical/cloud-init/pull/48">https://github.com/canonical/cloud-init/pull/48</a></p> -<p>17:45 <code>&lt;blackboxsw&gt;</code> #link <a href="https://github.com/canonical/cloud-init/pull/47">https://github.com/canonical/cloud-init/pull/47</a></p> -<p>17:45 <code>&lt;blackboxsw&gt;</code> we'll be trying to pull in hotplug functionality into this cycle, so expect work land on that front before 19.4 I'm guessing</p> -<p>17:45 <code>&lt;blackboxsw&gt;</code> sorry I mean version 20.1</p> -<p>17:46 <code>&lt;blackboxsw&gt;</code> ok next topic</p> -<p>17:46 <code>&lt;blackboxsw&gt;</code> #topic Community Charter</p> -<p>17:46 <code>&lt;meena&gt;</code> i want to test Goneri's network <a href="https://github.com/canonical/cloud-init/pull/61">https://github.com/canonical/cloud-init/pull/61</a> , but a prerequisite to make that easier is <a href="https://github.com/canonical/cloud-init/pull/42">https://github.com/canonical/cloud-init/pull/42</a> and it appears only rharper knows how to write tests for that part of the code</p> -<p>17:47 <code>&lt;meena&gt;</code> what's hotplug support mean in this context?</p> -<p>17:48 <code>&lt;blackboxsw&gt;</code> This Community Charter topic is a placeholder to remind anyone with some spare cycles that as a community anyone can drop in for low-hanging fruit or discrete tasks that will contribute to a better cloud-init</p> -<p>17:48 <code>&lt;blackboxsw&gt;</code> the community charter is currently:</p> -<p>17:48 <code>&lt;blackboxsw&gt;</code> 1. updated datasource docs</p> -<p>17:48 <code>&lt;blackboxsw&gt;</code> 2. get json schema implementation writting for each cloudinit.config.cc_*py module</p> -<p>17:49 <code>&lt;Goneri&gt;</code> meena, I can generate some prebuilt images with my last patch</p> -<p>17:49 <code>&lt;blackboxsw&gt;</code> those items are cards on our trello board in the community low-hanging-fruit lane that anyone grab and work</p> -<p>17:49 <code>&lt;blackboxsw&gt;</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>17:50 <code>&lt;blackboxsw&gt;</code> ... sorry meena, needed to finish my thought. so we'd like review and closure on 42?</p> -<p>17:50 <code>&lt;blackboxsw&gt;</code> &gt;<code>&gt;</code> what's hotplug support mean in this context? hotplug network device events currently would be the baseline.</p> -<p>17:51 <code>&lt;blackboxsw&gt;</code> so network config would be rewritten as devices show up or disappear</p> -<p>17:51 <code>&lt;blackboxsw&gt;</code> if someone opts into cloud-init controlling the running network config post-boot</p> -<p>17:52 <code>&lt;blackboxsw&gt;</code> #topic Upcoming Meetings</p> -<p>17:52 <code>&lt;blackboxsw&gt;</code> as set earlier. Dec 10th for another status meeting at this hour</p> -<p>17:52 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>17:53 <code>&lt;blackboxsw&gt;</code> This time is a chance for open discussions really on any cloud-init topic. bugs, issues, branches that need review etc. In the absence of other discussion, devs will be hitting the review queue to chip away at existing PRs to keep them from getting stale</p> -<p>17:56 <code>&lt;meena&gt;</code> blackboxsw: yes, please, 42 fix would be good</p> -<p>17:59 <code>&lt;blackboxsw&gt;</code> ok looking now</p> -<p>17:59 <code>&lt;blackboxsw&gt;</code> ahosmanMSFT: I'm landing your Azure CI first</p> -<p>18:04 <code>&lt;blackboxsw&gt;</code> ahosmanMSFT: would you like to provide me with a bit more information in the commit message <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> for enabling Azure integration testing? the 'commit message' in the UI will be the final message shown in cloud-init logs and it might be nice to have a bit more context</p> -<p>18:04 <code>&lt;ahosmanMSFT&gt;</code> blackboxsw Adding now</p> -<p>18:04 <code>&lt;blackboxsw&gt;</code> thank you sir</p> -<p>18:14 <code>&lt;ahosmanMSFT&gt;</code> blackboxsw take a look and let me know if I should add anything</p> -<p>18:15 <code>&lt;ahosmanMSFT&gt;</code> Added Azure to cloud tests supporting upstream integration testing. This Implements the inherited platform classes, Azure configurationsto release/platform, and docs on how to run Azure CI.</p> -<p>18:44 <code>&lt;blackboxsw&gt;</code> meena: I may come up with an alternative suggestion to address smoser's suggestion to run dmidecode once. it's a bit of a lift though as dmidecode output isn't structured very easy to parse</p> -<p>19:00 <code>&lt;blackboxsw&gt;</code> ahh I should close out the meeting</p> -<p>19:00 <code>&lt;blackboxsw&gt;</code> Thanks folks for attending. Until next time use the IRC channel or mailing list</p> -<p>19:00 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2019-10-29T16:20:00+00:002019-10-29T16:20:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2019-10-29:/status-2019-10-29.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 29 Oct at 16:20 &mdash; 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></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 29 Oct at 16:20 &mdash; 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>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:20 <code>&lt;meetingology&gt;</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>&lt;meetingology&gt;</code> </p> -<p>16:20 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> Boo! Welcome to the Halloween edition of cloud-init bi-weekly status meeting</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #chair rharper</p> -<p>16:20 <code>&lt;meetingology&gt;</code> Current chairs: blackboxsw rharper</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #chair Odd_Bloke</p> -<p>16:20 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw rharper</p> -<p>16:21 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> So that we don't forget, let's set the topic for next status meeting.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: rharper does 11/12 look good?</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> as in, no holidays etc?</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> ok topic updated. Any concerns we can change it and send out an email to the mailing list</p> -<p>16:26 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> I have three actions from last meeting</p> -<p>16:26 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;chillysurfer&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> thx chillysurfer :)</p> -<p>16:31 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;YEAR&gt;</code>.<code>&lt;minor_release_number&gt;</code> where minor_release_number will be [1-4]</p> -<p>16:34 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> ok long-winded. But I think that was our actions from last cloud-init status meeting.</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> next topic</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> The following branches have landed in tip since last meeting: via git log --since 2019-10-08</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - net/netplan: use ipv6-mtu key for specifying ipv6 mtu values</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - Fix usages of yaml, and move yaml_dump to safeyaml.dumps. (LP: #1849640)</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - exoscale: Increase url_max_wait to 120s. [Chris Glass]</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - net/sysconfig: fix available check on SUSE distros</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> [Robert Schweikert] (LP: #1849378)</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - docs: Fix incorrect Azure IMDS IP address [Joshua Powers] (LP: #1849508)</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - introduce .travis.yml</p> -<p>16:37 <code>&lt;ubot5&gt;</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>&lt;blackboxsw&gt;</code> - net: enable infiniband support in eni and sysconfig renderers</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> [Darren Birkett] (LP: #1847114)</p> -<p>16:37 <code>&lt;ubot5&gt;</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>&lt;blackboxsw&gt;</code> - guestcust_util: handle special characters in config file [Xiaofeng Wang]</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - fix some more typos in comments [Dominic Schlegel]</p> -<p>16:37 <code>&lt;ubot5&gt;</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>&lt;blackboxsw&gt;</code> - replace any deprecated log.warn with log.warning</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> [Dominic Schlegel] (LP: #1508442)</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - net: handle openstack dhcpv6-stateless configuration</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> [Harald Jensås] (LP: #1847517)</p> -<p>16:37 <code>&lt;ubot5&gt;</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>&lt;blackboxsw&gt;</code> - Add .venv/ to .gitignore [Dominic Schlegel]</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - Small typo fixes in code comments. [Dominic Schlegel]</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - cloud_test/lxd: Retry container delete a few times</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - Add Support for e24cloud to Ec2 datasource. (LP: #1696476)</p> -<p>16:37 <code>&lt;ubot5&gt;</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>&lt;ubot5&gt;</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>&lt;ubot5&gt;</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>&lt;blackboxsw&gt;</code> some good incremental improvements on SuSE, FreeBSD,Ubuntu Azure, Ec2, OpenStack and Exoscale</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> Thanks Dominic, Robert, XiaoFeng, Harald and Darren and Scott for the contibutions this round!</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:41 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> And the active review queue for cloud-init is a good representation of what should land shortly.</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> #link <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a></p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> The following work-streams are currently in progress:</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> - CI for Azure (thanks ahosmanMSFT)</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> - Openstack networking v2 support (which allows openstack to talk v2 network config 'netplan' )</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> - Azure async disk mounts</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> - cloud-init boot performance improvements</p> -<p>16:46 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> We'll be able to review some of the outstanding branches during Office hours today</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> #topic Community Charter</p> -<p>16:50 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;tribaal&gt;</code> That's nice!</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> all help is appreciated especially from the datasource owners</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> \o tribaal.</p> -<p>16:52 <code>&lt;tribaal&gt;</code> o/</p> -<p>16:53 <code>&lt;tribaal&gt;</code> sorry, I'm following along, didn't mean to interrupt</p> -<p>16:53 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> no worries, interruptions welcome</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> think that about wraps up community charter.</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> two to topics to go</p> -<p>16:57 <code>&lt;blackboxsw&gt;</code> #topic Upcoming meetings</p> -<p>16:57 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> #topic Upcoming Releases</p> -<p>16:59 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> Immediately after release, we'll publish to Ubuntu's devel release Focal Fossa and our copr repo</p> -<p>16:59 <code>&lt;tribaal&gt;</code> nice! this answers one of the questions I had coming in today :)</p> -<p>16:59 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> good deal tribaal</p> -<p>17:00 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> <em>schedule</em> even</p> -<p>17:00 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>17:01 <code>&lt;blackboxsw&gt;</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>&lt;tribaal&gt;</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>&lt;tribaal&gt;</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>&lt;blackboxsw&gt;</code> tribaal: yep sorry, I mentioned earlier, but should have mentioned in the last topic</p> -<p>17:03 <code>&lt;tribaal&gt;</code> no worries</p> -<p>17:03 <code>&lt;tribaal&gt;</code> it's the logical follow-up to a release - so it was surely implied</p> -<p>17:04 <code>&lt;blackboxsw&gt;</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>&lt;tribaal&gt;</code> blackboxsw: do you know how/when cloud-init lands in other distros, as a matter of curiosity?</p> -<p>17:04 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> tribaal: robjo knows for SLES. otubo (hrm not here today) is managing RHEL/CentOS release schedules</p> -<p>17:06 <code>&lt;blackboxsw&gt;</code> and debian is trying to shore up to 19.X I believe.</p> -<p>17:06 <code>&lt;tribaal&gt;</code> ack</p> -<p>17:06 <code>&lt;blackboxsw&gt;</code> but I think other distros are delayed (for good reasons: testing/validation/stability/etc).</p> -<p>17:07 <code>&lt;tribaal&gt;</code> sure, that would make sense</p> -<p>17:07 <code>&lt;tribaal&gt;</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>&lt;blackboxsw&gt;</code> or somewhere</p> -<p>17:07 <code>&lt;tribaal&gt;</code> that would be incredibly useful to us :)</p> -<p>17:08 <code>&lt;blackboxsw&gt;</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>&lt;tribaal&gt;</code> tracking where and when our new datasource is available is a bit of a mystery right now :)</p> -<p>17:08 <code>&lt;tribaal&gt;</code> (except for Ubuntus)</p> -<p>17:09 <code>&lt;blackboxsw&gt;</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>&lt;tribaal&gt;</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>&lt;blackboxsw&gt;</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>&lt;tribaal&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> tribaal: yeah let me restate the action then</p> -<p>17:12 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> per scheduling we at least could start filling in some gaps there on cloud-init planned distro releases</p> -<p>17:13 <code>&lt;tribaal&gt;</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>&lt;tribaal&gt;</code> is that something we can do ourselves?</p> -<p>17:13 <code>&lt;tribaal&gt;</code> (code wise at least)</p> -<p>17:14 <code>&lt;blackboxsw&gt;</code> tribaal: codewise, if you are talking about manual tests, we generally run something like the following:</p> -<p>17:14 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> oops wrong paste</p> -<p>17:15 <code>&lt;blackboxsw&gt;</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>&lt;tribaal&gt;</code> oh, I see</p> -<p>17:16 <code>&lt;tribaal&gt;</code> so thankfully it's only manual in the "manually run a script" sense :)</p> -<p>17:16 <code>&lt;blackboxsw&gt;</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>&lt;tribaal&gt;</code> yes, that would work (myself, and a handful of colleagues would be happy to I guess)</p> -<p>17:17 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;tribaal&gt;</code> ah nice, that makes sense</p> -<p>17:19 <code>&lt;blackboxsw&gt;</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>&lt;tribaal&gt;</code> yeah that sounds like a good first step, and we can expand later on if/when needed</p> -<p>17:24 <code>&lt;blackboxsw&gt;</code> +1 tribaal</p> -<p>17:24 <code>&lt;blackboxsw&gt;</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>&lt;tribaal&gt;</code> yeah that was a crazy coincidence</p> -<p>17:25 <code>&lt;tribaal&gt;</code> my brother got married in Odd_Bloke 's backyard :)</p> -<p>17:25 <code>&lt;tribaal&gt;</code> I wish we could do cross-company colocated sprints :P</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> heh, I think we can call those #cloud-init-summits :)</p> -<p>17:26 <code>&lt;tribaal&gt;</code> ohhh yeah :)</p> -<p>17:26 <code>&lt;tribaal&gt;</code> when's the next one?</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> we'll have to get invites together for the next one (Fall 2020)</p> -<p>17:27 <code>&lt;tribaal&gt;</code> noted :)</p> -<p>17:29 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;tribaal&gt;</code> ohhh big news indeed!</p> -<p>17:30 <code>&lt;Odd_Bloke&gt;</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>&lt;Odd_Bloke&gt;</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>&lt;blackboxsw&gt;</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>&lt;tribaal&gt;</code> very nice!</p> -<p>17:33 <code>&lt;blackboxsw&gt;</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>&lt;tribaal&gt;</code> ah that would make sese yeah</p> -<p>17:34 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> thanks Odd_Bloke and rharper for all the work there so far</p> -<p>17:38 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> thanks for participating chillysurfer &amp; tribaal</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2019-10-08T16:18:00+00:002019-10-08T16:18:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2019-10-08:/status-2019-10-08.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 08 Oct at 16:18 &mdash; 17:54 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-10-08-16.18.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-10-08-16.18.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:23.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-09-09.html#status-2019-09-09">https://cloud-init.github.io/status-2019-09-09.html#status-2019-09-09 …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 08 Oct at 16:18 &mdash; 17:54 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-10-08-16.18.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-10-08-16.18.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:23.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-09-09.html#status-2019-09-09">https://cloud-init.github.io/status-2019-09-09.html#status-2019-09-09</a> </li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:25.</p> -<ul> -<li><strong>ACTION</strong>: blackboxsw verify cpc image builds are unpaused/unblocked for Azure</li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:36.</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="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> </li> -<li><strong>ACTION</strong>: 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></li> -<li><strong>LINK</strong>: <a href="https://trello.com/c/pqA1adVM/1195-investigate-adding-github-travis-ci-to-cloud-init">https://trello.com/c/pqA1adVM/1195-investigate-adding-github-travis-ci-to-cloud-init</a> </li> -</ul> -<h3>Community Charter</h3> -<p>The discussion about "Community Charter" started at 16:44.</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 and releases</h3> -<p>The discussion about "Upcoming meetings and releases" started at 16:47.</p> -<ul> -<li><strong>ACTION</strong>: upstream cloud-init email about 19.3 release date</li> -</ul> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 16:52.</p> -<ul> -<li><strong>ACTION</strong>: revisit python deprecation and report to mailinglist</li> -</ul> -<h2>Vote results</h2> -<h2>Action items, by person</h2> -<ul> -<li>ahosmanmsft</li> -<li>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></li> -<li>blackboxsw</li> -<li>blackboxsw verify cpc image builds are unpaused/unblocked for Azure - <strong>UNASSIGNED</strong></li> -<li>upstream cloud-init email about 19.3 release date</li> -<li>revisit python deprecation and report to mailinglist</li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (110)</li> -<li>ubot5 (8)</li> -<li>AnhVoMSFT (8)</li> -<li>meetingology (8)</li> -<li>Odd_Bloke (7)</li> -<li>rharper (3)</li> -<li>ahosmanmsft (1)</li> -</ul> -<h2>Full Log</h2> -<p>16:18 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:18 <code>&lt;meetingology&gt;</code> Meeting started Tue Oct 8 16:18:28 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:18 <code>&lt;meetingology&gt;</code> </p> -<p>16:18 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> Welcome back folks o/ And thanks AnhVoMSFT for the ping to get us started</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> #chair rharper Odd_Bloke</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #chair rharper Odd_Bloke</p> -<p>16:19 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw rharper</p> -<p>16:19 <code>&lt;blackboxsw&gt;</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:19 <code>&lt;Odd_Bloke&gt;</code> o/</p> -<p>16:19 <code>&lt;Odd_Bloke&gt;</code> Thanks for the reminder, Anh.</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> Feel free to interject at any time. Our typical format is the following: Previous Actions, Recent Changes, In-progress Development, Office Hours (~30 mins).</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> For this, and subsequent, status meetings I proposed we add a new topic: Ongoing Community Charter which would give context on the new trello lane we added at the cloud-init summit.</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: rharper AnhVoMSFT does that sound good? We can then better advertise and remind about long-term community involvement projects that are available for anyone</p> -<p>16:22 <code>&lt;AnhVoMSFT&gt;</code> I would propose that the last agenda item of any status meeting would be to update the banner to reflect the next status meeting - and perhaps the next ETA for next release / SRU</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> +1 AnhVoMSFT that sounds good too.</p> -<p>16:22 <code>&lt;AnhVoMSFT&gt;</code> yep, sounds good on the Community Charter</p> -<p>16:22 <code>&lt;rharper&gt;</code> AnhVoMSFT: +1</p> -<p>16:22 <code>&lt;rharper&gt;</code> I think one topic each</p> -<p>16:22 <code>&lt;rharper&gt;</code> and end with the next status meeting</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> ok starting to turn the meeting crank</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> last meeting was 09/09/2019</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2019-09-09.html#status-2019-09-09">https://cloud-init.github.io/status-2019-09-09.html#status-2019-09-09</a></p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> meeting minutes at the link above ^</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> only action was #action blackboxsw send email to the list notifying of status meeting day change.</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> which was done <a href="https://lists.launchpad.net/cloud-init/msg00224.html">https://lists.launchpad.net/cloud-init/msg00224.html</a></p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> no further outstanding actions from last meeting</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> The following branches have landed in tip since last meeting: via git log --since 2019-09-09</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> - Add RbxCloud datasource [Adam Dobrawy]</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> - get_interfaces: don't exclude bridge and bond members (LP: #1846535)</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> - Add support for Arch Linux in render-cloudcfg [Conrad Hoffmann]</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> - util: json.dumps on python 2.7 will handle UnicodeDecodeError on binary</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> (LP: #1801364)</p> -<p>16:27 <code>&lt;ubot5&gt;</code> Launchpad bug 1846535 in cloud-init "cloud-init 19.2.36 fails with python exception "Not all expected physical devices present ..." during bionic image deployment from MAAS" [Critical,Fix committed] <a href="https://launchpad.net/bugs/1846535">https://launchpad.net/bugs/1846535</a></p> -<p>16:27 <code>&lt;ubot5&gt;</code> Launchpad bug 1801364 in cloud-init "persisting OpenStack metadata fails" [Undecided,Fix committed] <a href="https://launchpad.net/bugs/1801364">https://launchpad.net/bugs/1801364</a></p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> oopsie daisy</p> -<p>16:27 <code>&lt;AnhVoMSFT&gt;</code> :)</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> got kicked on flood. chunking that now</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> - Add RbxCloud datasource [Adam Dobrawy]</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> - get_interfaces: don't exclude bridge and bond members (LP: #1846535)</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> - Add support for Arch Linux in render-cloudcfg [Conrad Hoffmann]</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> - util: json.dumps on python 2.7 will handle UnicodeDecodeError on binary</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> (LP: #1801364)</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> - debian/ubuntu: add missing word to netplan/ENI header (LP: #1845669)</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> - ovf: do not generate random instance-id for IMC customization path</p> -<p>16:27 <code>&lt;ubot5&gt;</code> Launchpad bug 1845669 in cloud-init "The meaning of "Changes to it will not persist across an instance." in 50-cloud-init.yaml is unclear" [Undecided,Fix committed] <a href="https://launchpad.net/bugs/1845669">https://launchpad.net/bugs/1845669</a></p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> - sysconfig: only write resolv.conf if network_state has DNS values</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> (LP: #1843634)</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> - sysconfig: use distro variant to check if available (LP: #1843584)</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> - systemd/cloud-init.service.tmpl: start after wicked.service</p> -<p>16:27 <code>&lt;ubot5&gt;</code> Launchpad bug 1843634 in cloud-init (Suse) "cloud-init misconfigure the network on SLES" [Undecided,Incomplete] <a href="https://launchpad.net/bugs/1843634">https://launchpad.net/bugs/1843634</a></p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> [Robert Schweikert]</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> - docs: fix zstack documentation lints</p> -<p>16:28 <code>&lt;ubot5&gt;</code> Launchpad bug 1843584 in cloud-init "cloudinit/net/sysconfig.py lacks support for openSUSE 15.x and Tumbleweed" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1843584">https://launchpad.net/bugs/1843584</a></p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - analyze/show: remove trailing space in output</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - Add missing space in warning: "not avalid seed" [Brian Candler]</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - pylintrc: add 'enter_context' to generated-members list</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - Add datasource for ZStack platform. [Shixin Ruan] (LP: #1841181)</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - docs: organize TOC and update summary of project [Joshua Powers]</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - tools: make clean now cleans the dev directory, not the system</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - docs: create cli specific page [Joshua Powers]</p> -<p>16:28 <code>&lt;ubot5&gt;</code> Launchpad bug 1841181 in cloud-init "add datasource for ZStack" [Low,Fix committed] <a href="https://launchpad.net/bugs/1841181">https://launchpad.net/bugs/1841181</a></p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - docs: added output examples to analyze.rst [Joshua Powers]</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - docs: doc8 fixes for instancedata page [Joshua Powers]</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - docs: clean up formatting, organize boot page [Joshua Powers]</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - net: add is_master check for filtering device list (LP: #1844191)</p> -<p>16:28 <code>&lt;ubot5&gt;</code> Launchpad bug 1844191 in cloud-init "azure advanced networking sometimes triggers duplicate mac detection" [Critical,Fix committed] <a href="https://launchpad.net/bugs/1844191">https://launchpad.net/bugs/1844191</a></p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - docs: more complete list of availability [Joshua Powers]</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - docs: start FAQ page [Joshua Powers]</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - docs: cleanup output &amp; order of datasource page [Joshua Powers]</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - Brightbox: restrict detection to require full domain match .brightbox.com</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - VMWware: add option into VMTools config to enable/disable custom script.</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> [Xiaofeng Wang]</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - net,Oracle: Add support for netfailover detection</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - atomic_helper: add DEBUG logging to write_file (LP: #1843276)</p> -<p>16:28 <code>&lt;ubot5&gt;</code> Launchpad bug 1843276 in cloud-init "cloudinit.atomic_helper.write_file should have the same logging as util.write_file" [Low,Fix committed] <a href="https://launchpad.net/bugs/1843276">https://launchpad.net/bugs/1843276</a></p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> Thanks Brian, Shixin Ruan, Conrad Hoffmann, Adam Dobrawy and robjo for the contributions over the last month!</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> beyond tip commits to cloud-init the upstream team went through two SRUs of cloud-init</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> it's also excellent to see new datasources like the RbxCloud datasource added</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> cloud-init just passed validation for Ubuntu Xenial, Bionic and Disco on the 2nd SRU 19.2-36-g059d049c-0ubuntu2</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> cloud-images today should have that updated revision in them I blieve</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> there are fixes for both Azure accelerated networking support and handling issues seen on MAAS network bridge configuration</p> -<p>16:32 <code>&lt;AnhVoMSFT&gt;</code> on that note the last Azure image we had published was early September, which still didn't have the first SRU</p> -<p>16:32 <code>&lt;AnhVoMSFT&gt;</code> is there something going on with the image publishing pipeline again?</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: the publishing pipeline paused while we sorted the 2nd SRU pass for maas network bridge issues introduced by 19.2-36-g059d049c-0ubuntu1</p> -<p>16:33 <code>&lt;AnhVoMSFT&gt;</code> i see - that makes sense</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> 19.2-36-g059d049c-0ubuntu2 was verified as fixing all support there for both Azure and MAAS datasources and the expectation is that image builds are continuing today but I'll verify that the box is ✔ there on images rebuilding</p> -<p>16:34 <code>&lt;Odd_Bloke&gt;</code> There may also be Azure-specific publication pipeline issues, which we wouldn't necessarily know about off-hand.</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> #action blackboxsw verify cpc image builds are unpaused/unblocked for Azure</p> -<p>16:34 * meetingology blackboxsw verify cpc image builds are unpaused/unblocked for Azure</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> thx Odd_Bloke right</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> looks like Odd_Bloke is already on that verification internally</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> ok so SRU is through verification on our side. cloudimages should be getting latest version of cloud-init for Xenial, Bionic and Disco imminently</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> I think that is <em>it</em> for Recent Changes</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> the SRU verification work took a bit of steam out of our current work in progress as it involved a lot of manual and upgrade scenario tests.</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> But, as always we try to track ongoing work in trello</p> -<p>16:37 <code>&lt;blackboxsw&gt;</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:38 <code>&lt;blackboxsw&gt;</code> there are a number of branches in progress that are of interest:</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> Azure CI for one would be a great add for cloud-init's CI infrastructure</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> <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>16:39 <code>&lt;blackboxsw&gt;</code> we need to get eyes on that this week if we can</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> #action 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></p> -<p>16:39 * meetingology 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></p> -<p>16:39 <code>&lt;ahosmanmsft&gt;</code> That would be great</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> there are also a number of freebsd branches that need to close out.</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> and I know Odd_Bloke has started peeking at some initial github integration for CI.</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: any details you want to add about github CI at the moment?</p> -<p>16:41 <code>&lt;Odd_Bloke&gt;</code> I've started iterating on a Travis configuration to run what we currently run in our CI pipeline.</p> -<p>16:41 <code>&lt;Odd_Bloke&gt;</code> Unsurprisingly, setting up linting/unit testing was easy.</p> -<p>16:42 <code>&lt;Odd_Bloke&gt;</code> The other thing we do is run some integration testing from a built deb file. I got as far as being able to successfully sbuild the package in Travis, and ran into some initial stumbling blocks with running lxd.</p> -<p>16:42 <code>&lt;Odd_Bloke&gt;</code> That's as far as I've got, I expect to pick that work back up this week.</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> thanks Odd_Bloke , I've added the following card to trello for those interested.</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> #link <a href="https://trello.com/c/pqA1adVM/1195-investigate-adding-github-travis-ci-to-cloud-init">https://trello.com/c/pqA1adVM/1195-investigate-adding-github-travis-ci-to-cloud-init</a></p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> I think that about wraps in progress work. We'll tackle reviews a bit at the end of the meeting</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> ok next topic</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> #topic Community Charter</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> at the cloud-init summit we decided to highlight community work in trello so that any community member with some dev cycles and interest can join in and contribute to ongoing tasks</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> that lane is now in trello representing low-hanging-fruit content that upstream cloud-init is interested in completing, and that anyone can commit to.</p> -<p>16:45 <code>&lt;blackboxsw&gt;</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:46 <code>&lt;blackboxsw&gt;</code> the lane is labelled "Community low-hanging-fruit" and currently contains a number of doc update work items as well as json schema validation extensions for each cloud-init config module</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> we invite everyone to participate and feel free to grab those items as they have interest</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> we'll revisit this topic in each meeting so folks have context</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> #topic Upcoming meetings and releases</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> cloud-init upstream has just passed validation of cloud-init 19.2.36-*-ubuntu2 which should approved for upload into Xenial, Disco and Bionic (and queued for Eoan)</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> the cloud build team will be generating images for various clouds imminently and we will confirm that build pipelines are active so platforms get new bits asap</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> 19.3 upstream should by coming shortly, we will update the topic with the expected upstream release date and send an email to the mailing list with the estimated upstream cut</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> #action upstream cloud-init email about 19.3 release date</p> -<p>16:51 * meetingology upstream cloud-init email about 19.3 release date</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> next meeting is Oct 22</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> same bat time same bat channel</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> we spend this time for reviews, bug triage and cloud-init discussions.</p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> upstream devs should have eyes on this channel. Thanks everyone for tuning in</p> -<p>16:54 <code>&lt;AnhVoMSFT&gt;</code> have you had a chance to discuss about the python deprecation issue, or did the SRU verification take most of the time since the summit</p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: last week was vacation plus the remainder of us on sru verification .</p> -<p>17:00 <code>&lt;blackboxsw&gt;</code> But now we have cleared that hurdle we should we able to discuss it this week.</p> -<p>17:00 <code>&lt;AnhVoMSFT&gt;</code> yep, sounds good.</p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> #action revisit python deprecation and report to mailinglist</p> -<p>17:01 * meetingology revisit python deprecation and report to mailinglist</p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> Good meeting for actions</p> -<p>17:54 <code>&lt;blackboxsw&gt;</code> Thanks for the participation folks I'll publish minutes to github</p> -<p>17:54 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2019-09-09T16:26:00+00:002019-09-09T16:26:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2019-09-09:/status-2019-09-09.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 09 Sep at 16:26 &mdash; 17:33 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-09-09-16.26.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-09-09-16.26.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-08-19.html#status-2019-08-19">https://cloud-init.github.io/status-2019-08-19.html#status-2019-08-19</a> </p> -<h3>Previous actions</h3> -<p>The discussion about "Previous actions" started at 16:30 …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 09 Sep at 16:26 &mdash; 17:33 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-09-09-16.26.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-09-09-16.26.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-08-19.html#status-2019-08-19">https://cloud-init.github.io/status-2019-08-19.html#status-2019-08-19</a> </p> -<h3>Previous actions</h3> -<p>The discussion about "Previous actions" started at 16:30.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:31.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://lists.launchpad.net/cloud-init/msg00170.html">https://lists.launchpad.net/cloud-init/msg00170.html</a> </li> -<li><strong>LINK</strong>: <a href="https://lists.launchpad.net/cloud-init/">https://lists.launchpad.net/cloud-init/</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:38.</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="https://discourse.ubuntu.com/c/server">https://discourse.ubuntu.com/c/server</a> </li> -</ul> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 16:48.</p> -<ul> -<li><strong>ACTION</strong>: blackboxsw send email to the list notifying of status meeting day change.</li> -<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> -<h2>Vote results</h2> -<h2>Action items, by person</h2> -<ul> -<li>blackboxsw</li> -<li>blackboxsw send email to the list notifying of status meeting day change.</li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (64)</li> -<li>meetingology (5)</li> -<li>Odd_Bloke (4)</li> -<li>ubot5 (2)</li> -<li>rharper (1)</li> -</ul> -<h2>Full Log</h2> -<p>16:26 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:26 <code>&lt;meetingology&gt;</code> Meeting started Mon Sep 9 16:26:10 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:26 <code>&lt;meetingology&gt;</code> </p> -<p>16:26 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> Hey folks, welcome to the ~biweekly cloud-init status meeting.</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> #chair rharper Odd_Bloke</p> -<p>16:28 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw rharper</p> -<p>16:28 <code>&lt;Odd_Bloke&gt;</code> o/</p> -<p>16:28 <code>&lt;blackboxsw&gt;</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:30 <code>&lt;blackboxsw&gt;</code> Feel free to interject at any time. Our typical format is the following: Previous Actions, Recent Changes, In-progress Development, Office Hours (~30 mins)</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> Last meeting's minutes live here:</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2019-08-19.html#status-2019-08-19">https://cloud-init.github.io/status-2019-08-19.html#status-2019-08-19</a></p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> #topic Previous actions</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> no actions from last meeting so we'll plow right through to Recent Changes</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> The following branches have landed in tip since last meeting: via git log --since 2019-08-19</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> - doc: document doc, create makefile and tox target [Joshua Powers]</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> - .gitignore: ignore files produced by package builds [Daniel Watkins]</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> - docs: fix whitespace, spelling, and line length [Joshua Powers]</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> - docs: remove unnecessary file in doc directory [Joshua Powers]</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> - Oracle: Render secondary vnic IP and MTU values only [Ryan Harper]</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> - exoscale: fix sysconfig cloud_config_modules overrides</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> [Chad Smith] (LP: #1841454)</p> -<p>16:32 <code>&lt;ubot5&gt;</code> Launchpad bug 1841454 in cloud-init "Exoscale datasource overwrites <em>all</em> cloud_config_modules" [Undecided,Fix committed] <a href="https://launchpad.net/bugs/1841454">https://launchpad.net/bugs/1841454</a></p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> - net/cmdline: refactor to allow multiple initramfs network config sources</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> [Daniel Watkins]</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> - ubuntu-drivers: call db_x_loadtemplatefile to accept NVIDIA EULA</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> [Chad Smith] (LP: #1840080)</p> -<p>16:32 <code>&lt;ubot5&gt;</code> Launchpad bug 1840080 in cloud-init (Ubuntu) "cloud-init cc_ubuntu_drivers does not set up /etc/default/linux-modules-nvidia" [High,Fix released] <a href="https://launchpad.net/bugs/1840080">https://launchpad.net/bugs/1840080</a></p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> - Add missing #cloud-config comment on first example in documentation.</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> [Florian Müller]</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> - ubuntu-drivers: emit latelink=true debconf to accept nvidia eula</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> [Chad Smith] (LP: #1840080)</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> - DataSourceOracle: prefer DS network config over initramfs</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> [Daniel Watkins]</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> - format.rst: add text/jinja2 to list of content types (+ cleanups)</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> [Daniel Watkins]</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> - Add GitHub pull request template to point people at hacking doc</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> [Daniel Watkins]</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> Additionally: we have also cut a stable-18.4 branch from the 18.4 tag as our last supported python2.6 branch. There will be an email sent out to the mailing list about the intent of this branch. It requires a couple of minor fixes to make sure py2.6 support is functional, but this will be reference branch for any distribution that does not have access to py.27 or later. No additional feature development is</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> planned on stable-18.4</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> a reminder again that python2.6 support was 'dropped' in cloud-init upstream as of the 18.4 release, so expectations for py2.6 support stopped in 18.4 and there is a deprecation plan for py 2.7 as well</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> #link <a href="https://lists.launchpad.net/cloud-init/msg00170.html">https://lists.launchpad.net/cloud-init/msg00170.html</a></p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> Again, see the mailinglist for details and updates</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> #link <a href="https://lists.launchpad.net/cloud-init/">https://lists.launchpad.net/cloud-init/</a></p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> Last week or so the team has been working on SRU validation for cloud-init 19.2.24 into Xenial, Bionic and Disco.</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> We have passed all SRU validation tests and our expected pubish date for 19.2.24 is tomorrow for those Ubuntu series</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> good work on validation folks</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> and thanks for extra cloud-init community verification from exoscale, azure and VMware for validation efforts</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> There is additional Oracle, FreeBSD and Azure work in flight at the moment as well as some boot speed improvements and analysis from rharper</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> The following link represents any carded work upstream is tracking. The Doing lane is content or features we expect to land shortly</p> -<p>16:43 <code>&lt;blackboxsw&gt;</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:47 <code>&lt;blackboxsw&gt;</code> Now is probably a good time to also mention that our entire ubuntu server team also reflects our weekly accomplishements over in the ubuntu-server discourse. If there are deeper discussions or questions on various topics or features please join us there as well</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> #link <a href="https://discourse.ubuntu.com/c/server">https://discourse.ubuntu.com/c/server</a></p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> I think that about wraps it for in-progress development</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> upstream cloud-init devs will have eyes on this channel for any discussions, questions, bugs or feature work the greater community would like to discuss.</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> During this time, we'll also groom our activereview queue to make sure we try to get review comments out to devs who have active branches.</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> Again, thanks for tuning in</p> -<p>16:57 <code>&lt;blackboxsw&gt;</code> Ok just addressed review comments on <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/372432">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/372432</a> . I'm reviewing <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:59 * blackboxsw also sets the next meeting topic so we don't forget.</p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: rharper powersj, I <em>think</em> we decided to shift from Mondays to Tuesdays for status meetings to avoid collisions with holidays, vacation work travel etc. Are we doing that for next status meeting, or maybe waiting to discuss that more broadly?</p> -<p>17:02 <code>&lt;Odd_Bloke&gt;</code> Tuesday in two weeks is likely to be a travel day for anyone heading to the cloud-init summit.</p> -<p>17:02 <code>&lt;Odd_Bloke&gt;</code> But Monday is likely to be a swap day for Canonical folks because we're all travelling next week too.</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> hrm right, maybe we wait then and discuss at the summit</p> -<p>17:03 <code>&lt;Odd_Bloke&gt;</code> So I would perhaps suggest skipping the next meeting, and then we can resume on Tuesdays two weeks after the summit?</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> discuss scheduling changes that is</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> sure, let's push/postpone until summit +2 weeks</p> -<p>17:05 <code>&lt;blackboxsw&gt;</code> #action blackboxsw send email to the list notifying of status meeting day change.</p> -<p>17:05 * meetingology blackboxsw send email to the list notifying of status meeting day change.</p> -<p>17:10 <code>&lt;rharper&gt;</code> +1 Odd_Bloke</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> Also note that the version of cloud-init that has undergone SRU verification is also published to our copr el-testing repo. We only update that repo during upstream cloud-init releases XX.YY and any Ubuntu SRUs so it is much more stable than our daily copr repo.</p> -<p>17:11 <code>&lt;blackboxsw&gt;</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>17:33 <code>&lt;blackboxsw&gt;</code> I think that about wraps our cloud-init status meeting for today. I'm wrapping up my review here and will post it to the set_passwords branch.</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2019-08-19T16:18:00+00:002019-08-19T16:18:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2019-08-19:/status-2019-08-19.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 19 Aug at 16:18 &mdash; 17:25 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-08-19-16.18.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-08-19-16.18.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-08-05.html#status-2019-08-05">https://cloud-init.github.io/status-2019-08-05.html#status-2019-08-05</a> </p> -<h3>cloud-init Reviews: <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl …</a></h3><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 19 Aug at 16:18 &mdash; 17:25 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-08-19-16.18.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-08-19-16.18.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-08-05.html#status-2019-08-05">https://cloud-init.github.io/status-2019-08-05.html#status-2019-08-05</a> </p> -<h3>cloud-init Reviews: <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting Sept 2 16:15 UTC | cloud-init v 19.2 (07/17) | <a href="https://bugs.launchpad.net/cloud-init/+filebug">https://bugs.launchpad.net/cloud-init/+filebug</a></h3> -<p>The discussion about "cloud-init Reviews: <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting Sept 2 16:15 UTC | cloud-init v 19.2 (07/17) | <a href="https://bugs.launchpad.net/cloud-init/+filebug">https://bugs.launchpad.net/cloud-init/+filebug</a>" started at 16:20.</p> -<h3>Previous actions</h3> -<p>The discussion about "Previous actions" started at 16:21.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:22.</p> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:25.</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="https://code.launchpad.net/cloud-init/+activereviews">https://code.launchpad.net/cloud-init/+activereviews</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 (71)</li> -<li>rharper (9)</li> -<li>meetingology (5)</li> -<li>tribaal (4)</li> -<li>robjo (2)</li> -<li>ubot5 (1)</li> -<li>Odd_Bloke (0)</li> -</ul> -<h2>Full Log</h2> -<p>16:18 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:18 <code>&lt;meetingology&gt;</code> Meeting started Mon Aug 19 16:18:48 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:18 <code>&lt;meetingology&gt;</code> </p> -<p>16:18 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> Hi guys and girls, welcome to cloud-init biweekly status meeting</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #chair rharper</p> -<p>16:19 <code>&lt;meetingology&gt;</code> Current chairs: blackboxsw rharper</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #chair Odd_Bloke</p> -<p>16:19 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke blackboxsw rharper</p> -<p>16:19 <code>&lt;blackboxsw&gt;</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:19 <code>&lt;blackboxsw&gt;</code> All discussions and interjections are welcome</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> our format is the following topics: Previous Actions, Recent Changes, In-progress Development, Office Hours</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> last meeting's minutes are herer</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2019-08-05.html#status-2019-08-05">https://cloud-init.github.io/status-2019-08-05.html#status-2019-08-05</a></p> -<p>16:20 <code>&lt;rharper&gt;</code> o/</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> we host the meeting every two weeks at the date and time indicated in the IRC channel topic ^</p> -<p>16:20 * blackboxsw changes that topic now, since we(I) forgot last time</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #topic cloud-init Reviews: <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting Sept 2 16:15 UTC | cloud-init v 19.2 (07/17) | <a href="https://bugs.launchpad.net/cloud-init/+filebug">https://bugs.launchpad.net/cloud-init/+filebug</a></p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> next meeting in two weeks</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> #topic Previous actions</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> I see no previous actions raised during last meeting. Woo hoo!</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> the following are commits that</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> have landed in tip of master for cloud-init since the last meeting: git log --since 2019-08-04</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - cloudinit/distros/parsers/sys_conf: add docstring to SysConf</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> [Daniel Watkins]</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - pyflakes: remove unused variable [Joshua Powers]</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - Azure: Record boot timestamps, system information, and diagnostic events</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> [Anh Vo]</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - DataSourceOracle: configure secondary NICs on Virtual Machines</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> [Daniel Watkins]</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - distros: fix confusing variable names [Daniel Watkins]</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - azure/net: generate_fallback_nic emits network v2 config instead of v1</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> [Chad Smith]</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - Add support for publishing host keys to GCE guest attributes</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> [Rick Wright]</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - New data source for the Exoscale.com cloud platform [Chris Glass]</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - doc: remove intersphinx extension [Daniel Watkins]</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - cc_set_passwords: rewrite documentation [Daniel Watkins] (LP: #1838794)</p> -<p>16:22 <code>&lt;ubot5&gt;</code> Launchpad bug 1838794 in cloud-init "Set Passwords documentation describes incorrect behaviour for <code>password</code> config key" [Low,Fix committed] <a href="https://launchpad.net/bugs/1838794">https://launchpad.net/bugs/1838794</a></p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> We have also published commits though " - Azure: Record boot timestamps, system information, and diagnostic events" to Ubuntu Eoan (19.10) (cloud-init v.19.2-13) if folks want a glimpse of those features</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> Many thanks to Azure and GCE folks for their commits and a hi five to tribaal for adding Exoscale</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> As always, we try to keep most of our work up to date in trello</p> -<p>16:25 <code>&lt;blackboxsw&gt;</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:26 <code>&lt;blackboxsw&gt;</code> cards in the "Reviewing" column should represent the work we expect to have up for review in the short term.</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> rharper is mid-stream on some investigations that will likely lead to significant speed improvements for cloud-init</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: is working on some significant improvements for Oracle's datasource rendering network config</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> and I'm working on getting OpenStack and Ec2 datasources to talk network config v2.</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> beyond that work we have a pretty healther active review queue</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/cloud-init/+activereviews">https://code.launchpad.net/cloud-init/+activereviews</a></p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> of note, some freebsd work is in flight, gce dns improvements, udev triggers and OVF handling user-defined scripts.</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> We</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> will spend the latter part of this meeting looking over the review queue to see that open branches are in the proper state</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> Also, our plan for this week is to cut a Cloud-init SRU (Stable release update) for upload into xenial, bionic and disco.</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> expectation is that those Ubuntu series will see an update for cloud-init after our ~7 days of testing and verification</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> rharper: Odd_Bloke anything else in flight that we should note here?</p> -<p>16:34 <code>&lt;rharper&gt;</code> that looks like everything</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> without further ado, we can transition to office hours</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> We're here for any questions, bugs, discussions people would like to have around cloud-init. This block of time is available for any discussions or requests people may have.</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> We will also spend this time grooming the active review queue to make sure developers get any needed feedback on their active branches.</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> If there are any branches that need more eyes, please bring them up here or make sure they are in the 'Needs review' state in Launchpad</p> -<p>16:38 <code>&lt;tribaal&gt;</code> blackboxsw: thanks!</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> tribaal: good work. I think Odd_Bloke landed the followup work to enable exoscale datasource config to cloud-init.templates to 'enable' it. And looks like that has landed</p> -<p>16:40 <code>&lt;tribaal&gt;</code> blackboxsw: I'm happy to help verify SRU bugs when the process is kicked - just let me know</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> so it's 'on' in Eoan, once SRU is kicked off, it'll be in there</p> -<p>16:41 <code>&lt;tribaal&gt;</code> yep, I need to push an Eoan template to our preprod environment tomorrow to kick the tires, but I don't expect anything funny</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> tribaal: will do. I think the only thing we are waiting on before SRU is landing this ubuntu-drivers branch <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/371369">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/371369</a></p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> any feedback on behavior your in Eoan from you tribaal would be helpful.</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> let's try that in English this time: any feedback on the behavior in your Eoan environment would be helpful tribaal.</p> -<p>16:43 <code>&lt;tribaal&gt;</code> blackboxsw: haha that's what I inferred :)</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> :) /me hits the review queue</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> rharper: if you get a chance: you've landed <a href="https://git.launchpad.net/cloud-init/commit/">https://git.launchpad.net/cloud-init/commit/</a>?id=b3a87fc0. Do we also still need the following branch? <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/363571">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/363571</a></p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> If so, I'll spend this time trying to write up unit tests for this if possible</p> -<p>16:48 <code>&lt;rharper&gt;</code> blackboxsw: I don't think so; my branch should include all the needs of that branch</p> -<p>16:49 <code>&lt;rharper&gt;</code> and the branch tests the wait_for_physdev as well as updates the opensuse net render paths to account for the udev rule number change</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> that's kindof what I was thinking/hoping. I'll mark it rejected in favor of your commit, and we'll see what robjo thinks on that. We can reopen and try to address the unit test aspect of his branch if still needed.</p> -<p>16:50 <code>&lt;rharper&gt;</code> I think we can mark that branch closed</p> -<p>16:50 <code>&lt;rharper&gt;</code> robjo: had already looked at the branch before landing</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> ok done</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> thanks Florian for your first commit! <a href="https://code.launchpad.net/~florian-mueller-v/cloud-init/+git/cloud-init/+merge/371298">https://code.launchpad.net/~florian-mueller-v/cloud-init/+git/cloud-init/+merge/371298</a> ... doc update approved</p> -<p>16:58 <code>&lt;robjo&gt;</code> I don't recall having looked at <a href="https://git.launchpad.net/cloud-init/commit/">https://git.launchpad.net/cloud-init/commit/</a>?id=b3a87fc0 and there was no entry in the bug to remind me that I did. Anyway, I've done so now and yes, this obsoletes <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/363571">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/363571</a></p> -<p>17:00 <code>&lt;blackboxsw&gt;</code> thank you robjo for that</p> -<p>17:04 <code>&lt;rharper&gt;</code> robjo: <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/366667">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/366667</a> ; yes, I should have linked to the bug in my MP</p> -<p>17:04 <code>&lt;rharper&gt;</code> you did take a look a while back though</p> -<p>17:06 <code>&lt;robjo&gt;</code> rharper: I believe you, just cannot remember....</p> -<p>17:06 <code>&lt;rharper&gt;</code> heh, it was a while back</p> -<p>17:24 <code>&lt;blackboxsw&gt;</code> I think we should probably wrap up the meeting for this week. I've got one more review to clear.</p> -<p>17:24 <code>&lt;blackboxsw&gt;</code> Thanks again all for joining. minutes will be posted to github</p> -<p>17:25 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>17:25 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2019-08-05T16:16:00+00:002019-08-05T16:16:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2019-08-05:/status-2019-08-05.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 05 Aug at 16:16 &mdash; 17:06 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-08-05-16.16.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-08-05-16.16.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>#cloud-init Reviews: <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting Aug 19 16:15 …</h3><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 05 Aug at 16:16 &mdash; 17:06 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-08-05-16.16.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-08-05-16.16.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>#cloud-init Reviews: <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting Aug 19 16:15 UTC | cloud-init v 19.2 (07/17) | <a href="https://bugs.launchpad.net/cloud-init/+filebu">https://bugs.launchpad.net/cloud-init/+filebu</a></h3> -<p>The discussion about "#cloud-init Reviews: <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting Aug 19 16:15 UTC | cloud-init v 19.2 (07/17) | <a href="https://bugs.launchpad.net/cloud-init/+filebu">https://bugs.launchpad.net/cloud-init/+filebu</a>" started at 16:19.</p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:20.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-07-22.html#status-2019-07-22">https://cloud-init.github.io/status-2019-07-22.html#status-2019-07-22</a> </li> -</ul> -<h3>In-Progress Development</h3> -<p>The discussion about "In-Progress Development" started at 16:23.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516">https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/370927">https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/370927</a> (doc updates)</li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785">https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785</a> (Azure telemetry)</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> -<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>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:31.</p> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 16:33.</p> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (56)</li> -<li>tribaal (7)</li> -<li>cyphermox (4)</li> -<li>meetingology (4)</li> -<li>ubot5 (1)</li> -<li>rharper (0)</li> -</ul> -<h2>Full Log</h2> -<p>16:16 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:16 <code>&lt;meetingology&gt;</code> Meeting started Mon Aug 5 16:16:04 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:16 <code>&lt;meetingology&gt;</code> </p> -<p>16:16 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:16 <code>&lt;tribaal&gt;</code> o/</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> Heya Chris!</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> Welcome to another cloud-init community status meeting folks.</p> -<p>16:17 * blackboxsw finally back from a much needed vacation and have dug myself out of backlog</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> #chair rharper</p> -<p>16:17 <code>&lt;meetingology&gt;</code> Current chairs: blackboxsw rharper</p> -<p>16:18 <code>&lt;blackboxsw&gt;</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:18 <code>&lt;blackboxsw&gt;</code> All interjections updates and questions welcome</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> we may be a bit light this meeting as well as some folks have holidays and travel that coincide with this meeting</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> our format is the following topics: Previous Actions, Recent Changes, In-progress Development, Office Hours</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> we host the meeting every two weeks at the date and time indicated in the IRC channel topic ^</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> I'll update that topic now as I think we forgot to last meeting</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #topic #cloud-init Reviews: <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting Aug 19 16:15 UTC | cloud-init v 19.2 (07/17) | <a href="https://bugs.launchpad.net/cloud-init/+filebu">https://bugs.launchpad.net/cloud-init/+filebu</a></p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> next meeting will be two weeks from today, same time</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2019-07-22.html#status-2019-07-22">https://cloud-init.github.io/status-2019-07-22.html#status-2019-07-22</a></p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> groking the meeting last episode, looks like rharper needed to update status on <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a></p> -<p>16:20 <code>&lt;ubot5&gt;</code> Ubuntu bug 1832381 in cloud-init (Ubuntu) "vm fails to boot due to conflicting network configuration when user switches from netplan to eni" [Undecided,Incomplete]</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> I think we were awaiting feedback there from AnvoMSFT for a specific reproduce</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> I think we were awaiting feedback there from AnvoMSFT for a specific reproducer</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> so that'll carryover til next meeting if if it a priority</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> the other action from last session was for rharper to ping me on status publishing to github.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> I've pushed meeting minutes from last two cloud-init status meetings up to cloud-init.github.io so we are closed there</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> no other actions seen</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #topic In-Progress Development</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> Upstream 19.2 was cut on 7/17 and there are plans to SRU cloud-init within the next week or two into Xenial, bionic, disco and Eaon. I know that we are waiting on closure of a few branches in tip before we SRU cloud-init tip to Xenial ++</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> tribaal: your exoscale branch I believe is one of the ones we want landed before we start our SRU process</p> -<p>16:24 <code>&lt;tribaal&gt;</code> I was hoping to address Odd_Bloke 's comments today, but that didn't happen. Tomorrow, or "this week" at the very least is my new target.</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516">https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516</a></p> -<p>16:25 <code>&lt;tribaal&gt;</code> Most of the non-blocking comments should be easy - I want to double check the on-reboot behavior on an actual instance though</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> tribaal: excellent, Odd_Bloke was able to get the review in Friday as he knew he'd be on holiday today and wanted to get you feedback</p> -<p>16:25 <code>&lt;tribaal&gt;</code> ack</p> -<p>16:26 <code>&lt;tribaal&gt;</code> (the blocking comment about the copyright header should be trivial as well thankfully :) )</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> yeah agreed</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> we also have the following branches we'd like to get "in" and merged to tip before SRU</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/370927">https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/370927</a> (doc updates)</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785">https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785</a> (Azure telemetry)</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> and some of goneri's FreeBSD support look like they are straight forward for review/landing</p> -<p>16:28 <code>&lt;blackboxsw&gt;</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:28 <code>&lt;blackboxsw&gt;</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:29 <code>&lt;blackboxsw&gt;</code> If anyone else out there today is interested in getting reviews/merges before we SRU to Xenial, please feel free to raise a request in channel here or on the mailing list.</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> Also in progress, I just drew up a minispec for DataSourceOVF so that VMware can support merging configuration sources from IMC and OVF if both are present. This allows OVF datasource to configure both static IP config as well as do ssh user imports (which was previously not possible)</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> As always, our in progress development generally will also be represented on trello</p> -<p>16:31 <code>&lt;blackboxsw&gt;</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:31 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> the following has landed in tip of master since last cloud-init status meeting</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> % git log --oneline --since 2019-07-22</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> - net/cmdline: split interfaces_by_mac and init network config</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> determination [Daniel Watkins]</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> - stages: allow data sources to override network config source order</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> [Daniel Watkins]</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> feel free to ask for help, reviews, discussions on any cloud-init items you're looking at. Otherwise I'll spend some time today getting through the review queue for cloud-init branches.</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> and doing some bug triage</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> thanks tribaal for jumping in BTW.</p> -<p>16:35 <code>&lt;tribaal&gt;</code> blackboxsw: my pleasure :)</p> -<p>16:36 <code>&lt;tribaal&gt;</code> I'm working on the review points in parallel during office hours as well, that should move things forward hopefully.</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> excellent just ping when ready this week and we'll give a quick pass.</p> -<p>16:46 <code>&lt;cyphermox&gt;</code> blackboxsw: yeah, I'm not sure about that eni/netplan conflict; you do need to remove old config from one to the other, otherwise they might fight, but not something I'd expect to break boot.</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> hiya cyphermox. agreed, I <em>think</em> we decided that cloud-init needed to be smart in the transition from netplan -&gt;` eni if someone does that on a system and cloud-init can warn about the behavior change, cleanup old netplan config and render eni in that case.</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> since cloud-init should be smart enough to know what it '</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> used to render</p> -<p>16:49 <code>&lt;cyphermox&gt;</code> ack</p> -<p>16:49 <code>&lt;cyphermox&gt;</code> yeah, now that I think of it we said the exact same thing last meeting, I think</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> +1, I'm just dusting the vacation cobwebs off. so didn't know if something else happened on that front last week</p> -<p>16:52 <code>&lt;cyphermox&gt;</code> well, I recall the convo, that's what I meant</p> -<p>17:06 <code>&lt;blackboxsw&gt;</code> I think that about wraps cloud-init status meeting for today folks. Thanks again. And drop us a line on the mailing list (cloud-init@lists.launchpad.net) or here in IRC anytime with questions/discussions.</p> -<p>17:06 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2019-07-22T16:15:00+00:002019-07-22T16:15:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2019-07-22:/status-2019-07-22.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 22 Jul at 16:15 &mdash; 17:15 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-07-22-16.15.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-07-22-16.15.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:17.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 22 Jul at 16:15 &mdash; 17:15 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-07-22-16.15.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-07-22-16.15.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:17.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a> </li> -<li><strong>ACTION</strong>: rharper to update <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a> status</li> -<li><strong>LINK</strong>: <a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-07-08-16.16.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-07-08-16.16.html</a> </li> -<li><strong>ACTION</strong>: rharper to followup with blackboxsw on pushing status minutes up to cloud-init.github.io page</li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:23.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/t/cloud-init-19-2-release/11873">https://discourse.ubuntu.com/t/cloud-init-19-2-release/11873</a> </li> -</ul> -<h3>In Progress Development</h3> -<p>The discussion about "In Progress Development" started at 16:27.</p> -<ul> -<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> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368508">https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368508</a> </li> -</ul> -<h3>In Progress Development</h3> -<p>The discussion about "In Progress Development" started at 16:36.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516">https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~xiaofengw/cloud-init/+git/cloud-init/+merge/367889">https://code.launchpad.net/~xiaofengw/cloud-init/+git/cloud-init/+merge/367889</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/369783">https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/369783</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/feature/stage_threadpool">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/feature/stage_threadpool</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://copr.fedorainfracloud.org/coprs/g/cloud-init/cloud-init-dev/">https://copr.fedorainfracloud.org/coprs/g/cloud-init/cloud-init-dev/</a> </li> -<li><strong>LINK</strong>: <a href="https://download.opensuse.org/repositories/Cloud:/Tools/">https://download.opensuse.org/repositories/Cloud:/Tools/</a> </li> -</ul> -<h2>Vote results</h2> -<h2>Action items, by person</h2> -<ul> -<li>rharper</li> -<li>rharper to update <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a> status</li> -<li>rharper to followup with blackboxsw on pushing status minutes up to cloud-init.github.io page</li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>rharper (69)</li> -<li>Goneri (20)</li> -<li>meetingology (6)</li> -<li>Odd_Bloke (5)</li> -<li>metsuke (4)</li> -<li>ubot5 (2)</li> -</ul> -<h2>Full Log</h2> -<p>16:15 <code>&lt;rharper&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:15 <code>&lt;meetingology&gt;</code> Meeting started Mon Jul 22 16:15:03 2019 UTC. The chair is rharper. Information about MeetBot at <a href="http://wiki.ubuntu.com/meetingology.">http://wiki.ubuntu.com/meetingology.</a></p> -<p>16:15 <code>&lt;meetingology&gt;</code> </p> -<p>16:15 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:15 <code>&lt;rharper&gt;</code> \o/</p> -<p>16:15 <code>&lt;rharper&gt;</code> #chair Odd_Bloke</p> -<p>16:15 <code>&lt;meetingology&gt;</code> Current chairs: Odd_Bloke rharper</p> -<p>16:15 <code>&lt;rharper&gt;</code> hi folks, welcome to another cloud-init community status meeting. All discussions and interjections welcome.</p> -<p>16:16 <code>&lt;rharper&gt;</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:16 <code>&lt;rharper&gt;</code> our format is the following topics: Previous Actions, Recent Changes, In-progress Development, Office Hours</p> -<p>16:16 <code>&lt;rharper&gt;</code> anyone is welcome to participate, interject, make suggestions or ask questions</p> -<p>16:16 <code>&lt;rharper&gt;</code> we host the meeting every two weeks at the date and time indicated in the IRC channel topic ^</p> -<p>16:17 <code>&lt;rharper&gt;</code> #topic Previous Actions</p> -<p>16:17 <code>&lt;Odd_Bloke&gt;</code> o/</p> -<p>16:17 <code>&lt;rharper&gt;</code> We had a few previous action items to look at</p> -<p>16:18 <code>&lt;rharper&gt;</code> <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a></p> -<p>16:18 <code>&lt;ubot5&gt;</code> Ubuntu bug 1832381 in cloud-init (Ubuntu) "vm fails to boot due to conflicting network configuration when user switches from netplan to eni" [Undecided,Incomplete]</p> -<p>16:18 <code>&lt;rharper&gt;</code> AnhVoMSFT was looking to collect logs from this scenario;</p> -<p>16:19 <code>&lt;Goneri&gt;</code> hey!</p> -<p>16:19 <code>&lt;rharper&gt;</code> it appears that getting an instance where the MAC address changes is harder so fewer folks trip over this; however, we agreed that cloud-init can track which renderer it used and if it switches it can clean up the config it wrote;</p> -<p>16:19 <code>&lt;rharper&gt;</code> #action rharper to update <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a> status</p> -<p>16:19 * meetingology rharper to update <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a> status</p> -<p>16:19 <code>&lt;ubot5&gt;</code> Ubuntu bug 1832381 in cloud-init (Ubuntu) "vm fails to boot due to conflicting network configuration when user switches from netplan to eni" [Undecided,Incomplete]</p> -<p>16:20 <code>&lt;rharper&gt;</code> The other action was to review <a href="https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785">https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785</a></p> -<p>16:20 <code>&lt;rharper&gt;</code> This was completed the other week while we worked toward the 19.2 release; that branch is currently work-in-progress, awaiting feedback/changes from submitter</p> -<p>16:21 <code>&lt;rharper&gt;</code> that's all of the action items from previous meeting</p> -<p>16:22 <code>&lt;rharper&gt;</code> previous meeting status found here:</p> -<p>16:22 <code>&lt;rharper&gt;</code> #link <a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-07-08-16.16.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-07-08-16.16.html</a></p> -<p>16:23 <code>&lt;rharper&gt;</code> normally at the cloud-init.github.io status page; looks like we didn't push the logs there.</p> -<p>16:23 <code>&lt;rharper&gt;</code> #action rharper to followup with blackboxsw on pushing status minutes up to cloud-init.github.io page</p> -<p>16:23 * meetingology rharper to followup with blackboxsw on pushing status minutes up to cloud-init.github.io page</p> -<p>16:23 <code>&lt;rharper&gt;</code> #topic Recent Changes</p> -<p>16:25 <code>&lt;rharper&gt;</code> % git log --oneline --since 2019-07-08</p> -<p>16:25 <code>&lt;rharper&gt;</code> a02c0c9 (HEAD -&gt;` master, origin/master, origin/HEAD) cloud_tests: updates and fixes</p> -<p>16:25 <code>&lt;rharper&gt;</code> 5498107 Fix bug rendering MTU on bond or vlan when input was netplan.</p> -<p>16:25 <code>&lt;rharper&gt;</code> b3a87fc net: update net sequence, include wait on netdevs, opensuse netrules path</p> -<p>16:25 <code>&lt;rharper&gt;</code> 060b1a1 (tag: 19.2, raharper/release/19.2, release/19.2, fix/fs_setup_custom_command_lp1801790) Release 19.2</p> -<p>16:25 <code>&lt;rharper&gt;</code> 07b1723 net: add rfc3442 (classless static routes) to EphemeralDHCP</p> -<p>16:25 <code>&lt;rharper&gt;</code> 1404817 templates/ntp.conf.debian.tmpl: fix missing newline for pools</p> -<p>16:25 <code>&lt;rharper&gt;</code> a785462 Support netplan renderer in Arch Linux</p> -<p>16:25 <code>&lt;rharper&gt;</code> a066ccd Fix typo in publicly viewable documentation.</p> -<p>16:26 <code>&lt;rharper&gt;</code> d9769c4 Add a cdrom size checker for OVF ds to ds-identify</p> -<p>16:26 <code>&lt;rharper&gt;</code> 9c47c68 VMWare: Trigger the post customization script via cc_scripts module.</p> -<p>16:26 <code>&lt;rharper&gt;</code> a24550a Cloud-init analyze module: Added ability to analyze boot events.</p> -<p>16:26 <code>&lt;rharper&gt;</code> a6faf3a Update debian eni network configuration location, retain Ubuntu setting</p> -<p>16:26 <code>&lt;rharper&gt;</code> e5f5421 net: skip bond interfaces in get_interfaces</p> -<p>16:26 <code>&lt;rharper&gt;</code> 217c893 Fix a couple of issues raised by a coverity scan</p> -<p>16:26 <code>&lt;rharper&gt;</code> biggest item in there is the 19.2 release</p> -<p>16:26 <code>&lt;rharper&gt;</code> #link <a href="https://discourse.ubuntu.com/t/cloud-init-19-2-release/11873">https://discourse.ubuntu.com/t/cloud-init-19-2-release/11873</a></p> -<p>16:26 <code>&lt;rharper&gt;</code> a big thank you from the cloud-init team to everyone who helped contribute to the release</p> -<p>16:27 <code>&lt;Goneri&gt;</code> do you have time for a little BSD update?</p> -<p>16:27 <code>&lt;rharper&gt;</code> Yes, let's talk about In progress developement</p> -<p>16:27 <code>&lt;rharper&gt;</code> #topic In Progress Development</p> -<p>16:27 <code>&lt;rharper&gt;</code> Goneri: go ahead</p> -<p>16:28 <code>&lt;Goneri&gt;</code> #topic FreeBSD/NetBSD status</p> -<p>16:28 <code>&lt;Goneri&gt;</code> so there is two active branches, the first one is: <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:28 <code>&lt;rharper&gt;</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:29 <code>&lt;Goneri&gt;</code> it has started with a tiny fix to address a configuration difference with FreeBSD (there is no chpasswd there)</p> -<p>16:29 <code>&lt;Goneri&gt;</code> and it's now a slightly bigger refactoring now, I believe it clarify the code base and I would like to land it like that.</p> -<p>16:30 <code>&lt;Goneri&gt;</code> a discussion is ongoing with rharper on the PR</p> -<p>16:30 <code>&lt;Goneri&gt;</code> second PR is <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:30 <code>&lt;Goneri&gt;</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:30 <code>&lt;Goneri&gt;</code> this one is much bigger, and I've just addressed the last comment from rharper, I test it often and it works fine for me</p> -<p>16:31 <code>&lt;Goneri&gt;</code> if you want to give it a try, I pushed some pre-built images here: <a href="http://bsd-cloud-image.org/">http://bsd-cloud-image.org/</a></p> -<p>16:31 <code>&lt;rharper&gt;</code> nice!</p> -<p>16:31 <code>&lt;Goneri&gt;</code> I test it with OpenStack and NoCloud, a friend who maintains CBSD also test it on Bhyve (FreeBSD)</p> -<p>16:32 <code>&lt;Goneri&gt;</code> finally, the last one is <a href="https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368508">https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368508</a></p> -<p>16:32 <code>&lt;Goneri&gt;</code> #link <a href="https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368508">https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368508</a></p> -<p>16:32 <code>&lt;Goneri&gt;</code> No active merge request yet because it depends on the two actives PR that I just mentioned</p> -<p>16:32 <code>&lt;Goneri&gt;</code> this patch brings NetBSD support (7 and 8)</p> -<p>16:33 <code>&lt;Goneri&gt;</code> I would like to work on OpenBSD later, but it's still a low priority</p> -<p>16:34 <code>&lt;rharper&gt;</code> Goneri: thanks for the update</p> -<p>16:34 <code>&lt;Goneri&gt;</code> finally, I've a bunch of scripts that I use to build my images</p> -<p>16:35 <code>&lt;Goneri&gt;</code> it's still rather raw, but I would like to integrate that at some point with your CI</p> -<p>16:35 <code>&lt;Goneri&gt;</code> that's all</p> -<p>16:35 <code>&lt;rharper&gt;</code> thanks</p> -<p>16:36 <code>&lt;rharper&gt;</code> #topic In Progress Development</p> -<p>16:36 <code>&lt;rharper&gt;</code> #link <a href="https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516">https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516</a></p> -<p>16:36 <code>&lt;rharper&gt;</code> Adding a new datasource for Exoscale</p> -<p>16:36 <code>&lt;rharper&gt;</code> #link <a href="https://code.launchpad.net/~xiaofengw/cloud-init/+git/cloud-init/+merge/367889">https://code.launchpad.net/~xiaofengw/cloud-init/+git/cloud-init/+merge/367889</a></p> -<p>16:36 <code>&lt;rharper&gt;</code> vmware user-defined-scripts</p> -<p>16:37 <code>&lt;rharper&gt;</code> #link <a href="https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/369783">https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/369783</a></p> -<p>16:37 <code>&lt;rharper&gt;</code> Allow datasources to configure the order of network-config sources</p> -<p>16:37 <code>&lt;rharper&gt;</code> #link <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/feature/stage_threadpool">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/feature/stage_threadpool</a></p> -<p>16:38 <code>&lt;Odd_Bloke&gt;</code> I'm expecting to have a response to Ryan's review comments on that today, and whatever conclusion we reach shouldn't be too much work to implement.</p> -<p>16:38 <code>&lt;rharper&gt;</code> definitely</p> -<p>16:38 <code>&lt;Odd_Bloke&gt;</code> And then I'll have a follow-up to split apart the "cmdline" network data source in to "cmdline" and "initramfs", which are currently conflated.</p> -<p>16:39 <code>&lt;Odd_Bloke&gt;</code> (Neither of these should cause behavioural changes, they're just setting us up for some data source work down the line.)</p> -<p>16:40 <code>&lt;rharper&gt;</code> The threadpool branch is a more general approach to handle running modules async from the mainthread; there were some limitations depending on systemd; and there is a desire for more than just disk_setup to run async; this branch I'm working on would allow modules to be tagged async and they run in a separate thread allowing the next module to proceed; we then join at the end of stage to ensure completion of threads;</p> -<p>16:41 <code>&lt;rharper&gt;</code> any other upstream development I'm missing?</p> -<p>16:43 <code>&lt;rharper&gt;</code> ok, I think that's it then;</p> -<p>16:43 <code>&lt;rharper&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:43 <code>&lt;rharper&gt;</code> feel free to ask for help, reviews, discussions on any cloud-init items you're looking at.</p> -<p>16:44 <code>&lt;metsuke&gt;</code> Is Ubuntu the recommended, or most maintained, distribution of cloud-init?</p> -<p>16:46 <code>&lt;rharper&gt;</code> metsuke: hi; cloud-init in Ubuntu is the most-up-to-date as we're both the upstream maintainers (working for Canonical) and handle getting the latest upstream into Ubuntu images</p> -<p>16:47 <code>&lt;rharper&gt;</code> metsuke: we also help produce daily rpm builds for RedHat/Centos/Fedora in our copr repo</p> -<p>16:47 <code>&lt;rharper&gt;</code> #link <a href="https://copr.fedorainfracloud.org/coprs/g/cloud-init/cloud-init-dev/">https://copr.fedorainfracloud.org/coprs/g/cloud-init/cloud-init-dev/</a></p> -<p>16:48 <code>&lt;rharper&gt;</code> #link <a href="https://download.opensuse.org/repositories/Cloud:/Tools/">https://download.opensuse.org/repositories/Cloud:/Tools/</a></p> -<p>16:48 <code>&lt;rharper&gt;</code> suse's cloud:Tools keeps a really recent cloud-init as well</p> -<p>16:48 <code>&lt;metsuke&gt;</code> great, thanks for the info!</p> -<p>16:48 <code>&lt;rharper&gt;</code> sure</p> -<p>16:49 <code>&lt;metsuke&gt;</code> I'm looking to distribute standardized VMs to 100+ sites running ESXi so I'm trying to find the best way to do that =)</p> -<p>16:52 <code>&lt;Odd_Bloke&gt;</code> metsuke: If you have any questions, please don't hesitate to ask in here; we're generally around US working hours, for reference.</p> -<p>16:53 <code>&lt;rharper&gt;</code> yes, cloud-init can help keep your base image generic, allowing customization to happen at boot time;</p> -<p>16:53 <code>&lt;metsuke&gt;</code> thanks, I'm trying to do some preliminary investigation so I have an intelligent question to ask =P</p> -<p>17:15 <code>&lt;rharper&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2019-07-08T16:16:00+00:002019-07-08T16:16:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2019-07-08:/status-2019-07-08.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 08 Jul at 16:16 &mdash; 17:32 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-07-08-16.16.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-07-08-16.16.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:18.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-06-24.html#status-2019-06-24">https://cloud-init.github.io/status-2019-06-24.html#status-2019-06-24 …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 08 Jul at 16:16 &mdash; 17:32 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-07-08-16.16.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-07-08-16.16.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:18.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-06-24.html#status-2019-06-24">https://cloud-init.github.io/status-2019-06-24.html#status-2019-06-24</a> </li> -<li><strong>ACTION</strong>: query on incomplete <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a> with AnhVoMSFT to see if this needs priority</li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:22.</p> -<h3>In Progress Development</h3> -<p>The discussion about "In Progress Development" started at 16:27.</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="https://trello.com/c/RhevWnHx/1064-azure-imds-handle-multiple-default-routes-static-ips-in-primary-subnet">https://trello.com/c/RhevWnHx/1064-azure-imds-handle-multiple-default-routes-static-ips-in-primary-subnet</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/369792">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/369792</a> </li> -<li><strong>LINK</strong>: <a href="https://trello.com/c/TMK5ZDMf/1108-azure-async-disk-mounts">https://trello.com/c/TMK5ZDMf/1108-azure-async-disk-mounts</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516">https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516</a> </li> -<li><strong>LINK</strong>: <a href="https://wiki.ubuntu.com/CloudinitUpdates">https://wiki.ubuntu.com/CloudinitUpdates</a> </li> -<li><strong>ACTION</strong>: review Azure telemetry branch <a href="https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785">https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785</a></li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~bitfehler/cloud-init/+git/cloud-init/+merge/369814">https://code.launchpad.net/~bitfehler/cloud-init/+git/cloud-init/+merge/369814</a> </li> -</ul> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 16:48.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://netplan.io">https://netplan.io</a> for more info</li> -</ul> -<h2>Vote results</h2> -<h2>Action items, by person</h2> -<ul> -<li>AnhVoMSFT</li> -<li>query on incomplete <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a> with AnhVoMSFT to see if this needs priority</li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (89)</li> -<li>Odd_Bloke (13)</li> -<li>bitfehler (10)</li> -<li>tribaal (8)</li> -<li>AnhVoMSFT (7)</li> -<li>chad-aws (6)</li> -<li>meetingology (5)</li> -<li>ubot5 (3)</li> -<li>robjo (2)</li> -<li>rharper (2)</li> -</ul> -<h2>Full Log</h2> -<p>16:16 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:16 <code>&lt;meetingology&gt;</code> Meeting started Mon Jul 8 16:16:57 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:16 <code>&lt;meetingology&gt;</code> </p> -<p>16:16 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:17 <code>&lt;Odd_Bloke&gt;</code> bitfehler: It works for me on an Ubuntu eoan system, locally.</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> hi folks, welcome to another cloud-init community status meeting. All discussions and interjections welcome.</p> -<p>16:17 <code>&lt;Odd_Bloke&gt;</code> bitfehler: What version of Python 3 are you using?</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> loud-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:17 <code>&lt;blackboxsw&gt;</code> our format is the following topics: Previous Actions, Recent Changes, In-progress Development, Office Hours</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> anyone is welcome to participate, interject, make suggestions or ask questions</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> we host the meeting every two weeks at the date and time indicated in the IRC channel topic ^</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> I'm looking through our meeting minutes now from the previous meeting</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2019-06-24.html#status-2019-06-24">https://cloud-init.github.io/status-2019-06-24.html#status-2019-06-24</a></p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> Touch base with AnhVoMSFT by next status on priority of <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a></p> -<p>16:19 <code>&lt;ubot5&gt;</code> Ubuntu bug 1832381 in cloud-init (Ubuntu) "vm fails to boot due to conflicting network configuration when user switches from netplan to eni" [Undecided,Incomplete]</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> I think AnhVoMSFT may have been looking to get cloud-init logs on a system reproducing this problem</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> so let's carry this over for next meeting and this bug is marked incomplete until we have some cloud-init logs to debug</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> #action query on incomplete <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a> with AnhVoMSFT to see if this needs priority</p> -<p>16:21 * meetingology query on incomplete <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a> with AnhVoMSFT to see if this needs priority</p> -<p>16:21 <code>&lt;ubot5&gt;</code> Ubuntu bug 1832381 in cloud-init (Ubuntu) "vm fails to boot due to conflicting network configuration when user switches from netplan to eni" [Undecided,Incomplete]</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> no further actions listed from last meeting</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:22 <code>&lt;AnhVoMSFT&gt;</code> blackboxsw I did hear back from networking on how to trigger mac address change, so I'll work on that this week and get the logs attached</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> excellent AnhVoMSFT thanks!</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> and thanks for joining the meeting</p> -<p>16:22 <code>&lt;AnhVoMSFT&gt;</code> the harder it is to reproduce, the better, since it's unlikely to affect that many customers</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> +1</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> the following are commits that landed in tip of master for cloud-init upstream</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> - Add missing dsname for Hetzner Cloud datasource [Markus Schade]</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> - doc: indicate that netplan is default in Ubuntu now [Daniel Watkins]</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> - azure: add region and AZ properties from imds compute location metadata</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> [Chad Smith]</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> - sysconfig: support more bonding options [Penghui Liao]</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> - cloud-init-generator: use libexec path to ds-identify on redhat systems</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> [Ryan Harper] (<a href="[https://bugs.launchpad.net/bugs/1833264](https://bugs.launchpad.net/bugs/1833264)">LP: #1833264</a>)</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> - tools/build-on-freebsd: update to python3 [Gonéri Le Bouder]</p> -<p>16:24 <code>&lt;ubot5&gt;</code> Ubuntu bug 1833264 in cloud-init "cloud-init-generator hardcodes path to ds-identify" [Undecided,Fix committed]</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> though I think the bottom two of those commits I may have reported last meeting</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> beyond that I know that paride has resolved a couple of issues with our CI infrastructure not cleaning up stale containers which would have triggered a number of CI failures over the last few weeks.</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> I think that about wraps 'completed' work in tip.</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> #topic In Progress Development</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> We mentioned this last meeting, there are a couple of longer features we are working on that will hit cloud-init tip soon.</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> we track our work on trello at the following url</p> -<p>16:28 <code>&lt;blackboxsw&gt;</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:29 <code>&lt;blackboxsw&gt;</code> In trying to enable secondary IP configuration on Azure platforms, we discovered a systemd-networkd bug related to classless routes not getting the appropriate source IP configuration</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> per this card</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> #link <a href="https://trello.com/c/RhevWnHx/1064-azure-imds-handle-multiple-default-routes-static-ips-in-primary-subnet">https://trello.com/c/RhevWnHx/1064-azure-imds-handle-multiple-default-routes-static-ips-in-primary-subnet</a></p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> Dan Streetman filed a bug and upstream systemd fix for this <a href="https://github.com/systemd/systemd/issues/12969">https://github.com/systemd/systemd/issues/12969</a></p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> and he's working on getting that released into Ubuntu Eoan. cloud-init may need a minor fix to only render static IPs if systemd-networkd version contains the latest fix.</p> -<p>16:31 <code>&lt;chad-aws&gt;</code> secondary addresses on azure too, or aws?</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> chad-aws: I also have just pushed a branch for review that will add secondary IPs from AWS's Datasource as well</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> since we had context on the netplan we need to generate that</p> -<p>16:31 <code>&lt;chad-aws&gt;</code> ok</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/369792">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/369792</a></p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> chad-aws: the one question I think we might have to discuss related to the above branch is whether or not cloud-init on older LTSes (Xenial, Bionic) should change behavior to attempt rendering secondary IP information or not (because that would be a change in behavior)</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> generally we try to retain existing behavior on old Ubuntu LTS releases so we don't surprise folks who may have worked around previous limitations of cloud-init (like manually/scripted adding their own secondary IP information)</p> -<p>16:35 <code>&lt;chad-aws&gt;</code> (Note I am not the chad.smith above, but I am interested too.)</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> hehe, yes, I am not talking to myself (blackboxsw == chad.smith)</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> also in progress is rharper's good work on teasing out async mount functionality per the following</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> #link <a href="https://trello.com/c/TMK5ZDMf/1108-azure-async-disk-mounts">https://trello.com/c/TMK5ZDMf/1108-azure-async-disk-mounts</a></p> -<p>16:36 <code>&lt;chad-aws&gt;</code> I think different config files should make different behavior and that's okay.</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> +1 chad-aws</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> the async mount feature is the ability to allow cloud-init defer some disk mounts until later in the cloud-init stages to allow folks to ssh to the vms earlier in the boot process</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> as some systems with lots of mounts may block for a while trying to mount and format disks</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> while this approach is tagged as azure, rharper is approaching it in a generic way that should make this functionality accessible to many platforms</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> paride: rharper Odd_Bloke anything else I'm forgetting in progress?</p> -<p>16:40 <code>&lt;rharper&gt;</code> blackboxsw: right; it's changes to cc_disk_setup/cc_mount handling</p> -<p>16:40 <code>&lt;rharper&gt;</code> blackboxsw: nothing I can think of</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> we probably should cut an Ubutuu Eoan upload of cloud-init tip soon, but I don't know when that should be scheduled?</p> -<p>16:41 <code>&lt;Odd_Bloke&gt;</code> I'm doing some work to modify the way we determine network config sources, but that shouldn't affect any data sources that don't opt in to it.</p> -<p>16:41 <code>&lt;AnhVoMSFT&gt;</code> i looked at it briefly, this involves calling a systemd unit to format/mount - do we report error back to cloud-init ?</p> -<p>16:41 * tribaal raises hand</p> -<p>16:41 <code>&lt;tribaal&gt;</code> is there any rough estimation on where that tip cut would be?</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> tribaal: ahh yes awesome, forgot. tribaal has a new datasource</p> -<p>16:41 <code>&lt;tribaal&gt;</code> yes, thanks a lot for your reviews everyone</p> -<p>16:42 <code>&lt;tribaal&gt;</code> nice working with you guys again :)</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516">https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516</a></p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> for Exoscale ^</p> -<p>16:42 <code>&lt;tribaal&gt;</code> Ideally we'd target the next release for our datasource as well, but of course it's not landed yet so if the cut is e.g. tomorrow it might be a bit tight :)</p> -<p>16:42 <code>&lt;Odd_Bloke&gt;</code> Specifically, if a platform does any networking setup during the initramfs (such as for iSCSI), cloud-init will <em>only</em> consider the initramfs-provided configuration at the moment.</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> tribaal: for eoan, we can just grab tip of master at anypoint for an upload since it</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> is still a development release</p> -<p>16:43 <code>&lt;tribaal&gt;</code> ack</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> so it's super low weight for our release (and we should do it often)</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> also we have planned/upcoming an SRU into Xenial/Bionic/Disco on July 15th (so next week)</p> -<p>16:44 <code>&lt;tribaal&gt;</code> as far as SRUs are concerned, would that typically be something that would be backported, or not?</p> -<p>16:44 <code>&lt;Odd_Bloke&gt;</code> I'm making it possible for data sources to specify a different order for the network config sources, so that platforms where iSCSI is the default can have their data source's network config preferred.</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> tribaal: and others: cloud-init SRUs our tip into every release due to an SRU exception that we have with Ubuntu</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> so we upload latest code into each SRU target series for ubuntu</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> though we may patch/disable some functionality that is deemed a change in behavior from previous release</p> -<p>16:45 <code>&lt;tribaal&gt;</code> blackboxsw: understood, thanks. I'll schedule some time for myself to work on it "full time" as much as possible, so we can make the cut.</p> -<p>16:45 <code>&lt;Odd_Bloke&gt;</code> I'm also splitting apart explicitly-from-the-user cmdline configuration (i.e. network-data=...) from the initramfs-provided values (ip=... or iBFT), so that data sources can be configured to still allow explicit user network configuration to override data source network configuration.</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> here's our SRU process for those interested</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> #link <a href="https://wiki.ubuntu.com/CloudinitUpdates">https://wiki.ubuntu.com/CloudinitUpdates</a></p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> so this meeting (and an email to cloud-init mailinglist) will serve as a call for branches/features for SRU.</p> -<p>16:46 <code>&lt;Odd_Bloke&gt;</code> But as I said previously, this is all just refactoring except for the specific places we need this functionality.</p> -<p>16:46 <code>&lt;AnhVoMSFT&gt;</code> I sent a merge proposal for adding some more telemetry for Azure: <a href="https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785">https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785</a> - would appreciate a review. Trying to make it in before next SRU</p> -<p>16:46 <code>&lt;AnhVoMSFT&gt;</code> also will send a merge proposal today or tomorrow on the case sensitivity issue when checking is_new_instance</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> if folks are interested in getting a specific feature/bug or branch reviewed/fixed and published, please raise your hand, ping in channel or send email to the mailing list to make sure the need is not forgotten</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> #action review Azure telemetry branch <a href="https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785">https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785</a></p> -<p>16:47 * meetingology review Azure telemetry branch <a href="https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785">https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785</a></p> -<p>16:47 <code>&lt;bitfehler&gt;</code> i feel a bit awkward stepping in here, but i kind of do</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: we also have reviewed samgilson's branch on a new cloud-init analyze subcommand for boot performance</p> -<p>16:48 <code>&lt;bitfehler&gt;</code> sorry, i am pretty new to cloud-init, but i did open a merge proposal today</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> bitfehler: no worries, conversations gotta happen :)</p> -<p>16:48 <code>&lt;Odd_Bloke&gt;</code> #link <a href="https://code.launchpad.net/~bitfehler/cloud-init/+git/cloud-init/+merge/369814">https://code.launchpad.net/~bitfehler/cloud-init/+git/cloud-init/+merge/369814</a></p> -<p>16:48 <code>&lt;Odd_Bloke&gt;</code> (Can I do that, or only blackboxsw?)</p> -<p>16:48 <code>&lt;AnhVoMSFT&gt;</code> thanks blackboxsw, last I synced with him, Sam is actively working on addressing your comments</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> I'll tick the topic to office hours which is really just open season for discussion or reviews</p> -<p>16:48 <code>&lt;robjo&gt;</code> Does anyone know if VMware has any plans to move their source from <a href="https://github.com/vmware/cloud-init-vmware-guestinfo">https://github.com/vmware/cloud-init-vmware-guestinfo</a> to be included in upstream cloud-init?</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:51 <code>&lt;bitfehler&gt;</code> i think my main question would have been how to best get in touch with you, but i think i found the answer already :)</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> hrm, first I've seen of that robjo . maybe we can ping Sankar on that to see what the motivation is there</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> bitfehler: either here or mail cloud-init@lists.launchpad.net</p> -<p>16:52 <code>&lt;robjo&gt;</code> I was just made aware of this last week via "please create a packge' to which my initial answer is No, the VMware code should be in cloud-init proper</p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> per vmware,yeah that makes sense for them to try to get that cloud-init datasource upstream. forcing every distro to do their packaging for them is not really the right solution</p> -<p>16:54 <code>&lt;bitfehler&gt;</code> one other thing i was wondering: do you feel a plain systemd-networkd network renderer would make sense? i wrote a very basic one trying to get better cloud-init support for Arch Linux</p> -<p>16:54 <code>&lt;bitfehler&gt;</code> it sort of works, but I am not sure whether this goal worth pursuing?</p> -<p>16:57 <code>&lt;blackboxsw&gt;</code> bitfehler: interesting, right so we have netplan render which ultimately renders networkd on our behalf on ubuntu,</p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> if direct networkd render is the only way to support network config on Arch linux I don't see why we wouldn't want that.... rharper or Odd_Bloke? (maybe I'm missing the concern)</p> -<p>16:59 <code>&lt;bitfehler&gt;</code> i saw the comments about networkd above, but i am not familiar with netplan. it is another layer in between, right?</p> -<p>17:00 <code>&lt;Odd_Bloke&gt;</code> bitfehler: netplan takes v2 network configuration and renders it for a target backend. The two supported backends ATM are networkd and NetworkManager.</p> -<p>17:00 <code>&lt;blackboxsw&gt;</code> <a href="https://netplan.io">https://netplan.io</a> for more info</p> -<p>17:00 <code>&lt;bitfehler&gt;</code> oh, wow, i overlooked that. so it doesn't need any additional software?</p> -<p>17:01 <code>&lt;AnhVoMSFT&gt;</code> it does need netplan</p> -<p>17:01 <code>&lt;bitfehler&gt;</code> oh wait, netplan is a renderer itself, and that supports the two backends</p> -<p>17:02 <code>&lt;Odd_Bloke&gt;</code> Right, netplan is the intended way for cloud-init to render network config for networkd.</p> -<p>17:03 <code>&lt;bitfehler&gt;</code> ok, got it. i guess i could also look into porting netplan to arch then? not sure what an effort that would be</p> -<p>17:05 <code>&lt;Odd_Bloke&gt;</code> IMO, that would be the best way to go, if it's tractable.</p> -<p>17:05 <code>&lt;Odd_Bloke&gt;</code> We ideally wouldn't reimplement netplan's networkd renderer in cloud-init. :)</p> -<p>17:05 <code>&lt;bitfehler&gt;</code> i'll let you know soon ;)</p> -<p>17:08 <code>&lt;chad-aws&gt;</code> I guess this should go both ways. Is there anything AWS EC2 can do better or different?</p> -<p>17:25 <code>&lt;blackboxsw&gt;</code> nice chad-aws, sorry I got pulled into a second meeting. chad-aws I did have a question about metadata versioning in aws.</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> how are new features communicated for a new metadata version</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> I reference <a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html">https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html</a></p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> but it didn't have a specific note on the changes added for 2018-09-24 which I used in my branch</p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> only the first version that a field was introduced, not that local_ipv4s changed value from string to list in 2018-09-24.</p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> so I guess my question is, is there a better source of truth for ec2 metadata values that we should be looking at</p> -<p>17:28 <code>&lt;blackboxsw&gt;</code> chad-aws: sorry (I realize that's a question out of left field)</p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> I think I'll wrap the meeting here. Thank you all again for the attending this week.</p> -<p>17:31 <code>&lt;chad-aws&gt;</code> thx</p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> Again plan for cloud-init 19.2 SRU is scheduled for next week so any features/branches that need landing or review should be raised here or on the mailing list</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> minutes will be posted at <a href="https://cloud-init.github.io">https://cloud-init.github.io</a></p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2019-06-24T16:18:00+00:002019-06-24T16:18:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2019-06-24:/status-2019-06-24.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 24 Jun at 16:18 &mdash; 17:33 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-06-24-16.18.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-06-24-16.18.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:23.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-06-10.html#status-2019-06-10">https://cloud-init.github.io/status-2019-06-10.html#status-2019-06-10 …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 24 Jun at 16:18 &mdash; 17:33 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-06-24-16.18.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-06-24-16.18.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:23.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-06-10.html#status-2019-06-10">https://cloud-init.github.io/status-2019-06-10.html#status-2019-06-10</a> </li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a> </li> -<li><strong>ACTION</strong>: Touch base with AnhVoMSFT by next status on priority of <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a></li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:28.</p> -<h3>In Progress Development</h3> -<p>The discussion about "In Progress Development" started at 16:31.</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="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/feature/disk_setup_async">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/feature/disk_setup_async</a> is the WIP branch</li> -<li><strong>LINK</strong>: <a href="https://trello.com/c/TMK5ZDMf/1108-azure-async-disk-mounts">https://trello.com/c/TMK5ZDMf/1108-azure-async-disk-mounts</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>Action items, by person</h2> -<ul> -<li>AnhVoMSFT</li> -<li>Touch base with AnhVoMSFT by next status on priority of <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a></li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (73)</li> -<li>rharper (23)</li> -<li>AnhVoMSFT (18)</li> -<li>nik736 (12)</li> -<li>ubot5 (4)</li> -<li>meetingology (4)</li> -</ul> -<h2>Full Log</h2> -<p>16:18 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:18 <code>&lt;meetingology&gt;</code> Meeting started Mon Jun 24 16:18:34 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:18 <code>&lt;meetingology&gt;</code> </p> -<p>16:18 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> welcome to another episode of cloud-init status updates.</p> -<p>16:20 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> our format is the following topics: Previous Actions, Recent Changes, In-progress Development, Office Hours</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> anyone is welcome to participate, interject, make suggestions or ask questions</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> generally we try to host this meeting every two weeks on the day listed in the channel topic</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> last meeting</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2019-06-10.html#status-2019-06-10">https://cloud-init.github.io/status-2019-06-10.html#status-2019-06-10</a></p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> we had an action to follow up on any bugs related to installing ifupdown on a system that had netplan installed by default.</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> I believe we did see a bug come in from Azure about that.... checking for that bug id now</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> #1832381</p> -<p>16:25 <code>&lt;rharper&gt;</code> bug #1832381</p> -<p>16:25 <code>&lt;ubot5&gt;</code> bug 1832381 in cloud-init (Ubuntu) "vm fails to boot due to conflicting network configuration when user switches from netplan to eni" [Undecided,Incomplete] <a href="https://launchpad.net/bugs/1832381">https://launchpad.net/bugs/1832381</a></p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a></p> -<p>16:25 <code>&lt;AnhVoMSFT&gt;</code> There is an action item on me to attach a log to that bug. Since the incident created by the customer was closed and we did not have permission to share his log, I will need to get a repro and retrieve the log. It's not very easy to trigger a mac address change in Azure these days</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> thanks AnhVoMSFT for this bug</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> ok if we carry over that action item then for next status meeting AnhVoMSFT (just to close the loop if it's important)</p> -<p>16:27 <code>&lt;AnhVoMSFT&gt;</code> yep - once I get some help from our networking folks to trigger a mac address change I'll update the bug with more logs</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> #action Touch base with AnhVoMSFT by next status on priority of <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a></p> -<p>16:27 * meetingology Touch base with AnhVoMSFT by next status on priority of <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381</a></p> -<p>16:27 <code>&lt;ubot5&gt;</code> Ubuntu bug 1832381 in cloud-init (Ubuntu) "vm fails to boot due to conflicting network configuration when user switches from netplan to eni" [Undecided,Incomplete]</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> good deal. that's all we had for actions from last meeting</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> the following items have landed on tip of cloud-init's master branch</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> - sysconfig: support more bonding options [Penghui Liao]</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> - cloud-init-generator: use libexec path to ds-identify on redhat systems</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> [Ryan Harper] (<a href="[https://bugs.launchpad.net/bugs/1833264](https://bugs.launchpad.net/bugs/1833264)">LP: #1833264</a>)</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> - tools/build-on-freebsd: update to python3 [Gonéri Le Bouder]</p> -<p>16:30 <code>&lt;ubot5&gt;</code> Ubuntu bug 1833264 in cloud-init "cloud-init-generator hardcodes path to ds-identify" [Undecided,Fix committed]</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> thanks to Penghui and Gonéri for driving additional changes for cloud-init in this last sessions</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> session*</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> #topic In Progress Development</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> there a number of longer items for feature work in progress that should see some light soon</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> We track these features in trello as always</p> -<p>16:33 <code>&lt;blackboxsw&gt;</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:33 <code>&lt;blackboxsw&gt;</code> minor fixup for Azure instance-data.json (cloud-init query) for region and availability zone should land today</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> rharper: and blackboxsw are working on Azure-related route tables and async disk mount features</p> -<p>16:36 <code>&lt;AnhVoMSFT&gt;</code> is there any bug/discussion item for the async disk mount?</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: rharper has been testing out systemd unit magic for setting up disk mounts async and initial numbers look good. How to bake that work into cloud-init is the next small hurdle I think. (I thought he mentioned today in our standup a 50% speed increase due to async mounts instead of sync waits)</p> -<p>16:38 <code>&lt;rharper&gt;</code> <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/feature/disk_setup_async">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/feature/disk_setup_async</a> is the WIP branch</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: I expect we'll have something in the next couple of days.</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> orrr right now. thanx rharper</p> -<p>16:39 <code>&lt;AnhVoMSFT&gt;</code> that sounds really cool. I'll check it out</p> -<p>16:39 * blackboxsw creates a trello card that can be watched for this feature</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> #link <a href="https://trello.com/c/TMK5ZDMf/1108-azure-async-disk-mounts">https://trello.com/c/TMK5ZDMf/1108-azure-async-disk-mounts</a></p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> feel free to subscribe to any trello cards folks see that are of interest. you will get an email if the card changes state, like from Doing to Done or if new links are added</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: rharper process question</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> what do you guys think about us turning on voting on trello cards</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> people with interest on a feature/card in our backlog could upvote it and that <em>could</em> help drive what features we grab over time</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> dunno, thought it might be something we could toss around to see if that would make sense. the board it public after all</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> <em>is public</em> rather</p> -<p>16:43 <code>&lt;rharper&gt;</code> maybe; I worry about random +1 without any more context. Platform developers already work with us; and community folks file bugs/merge proposals</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> good point.</p> -<p>16:44 <code>&lt;rharper&gt;</code> I'm open to the idea</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> for sure, if it gets interest, we can think about adding that feature. can't hurt to have some additional input, unfounded though it may be.</p> -<p>16:45 <code>&lt;AnhVoMSFT&gt;</code> agreed on the usefulness might be limited. You guys are already talking to each other. Platform developers either engage directly on this board or through out of band channel (sync meeting with Canonical product groups, etc...)</p> -<p>16:46 <code>&lt;AnhVoMSFT&gt;</code> Perhaps you can try it out for a couple release periods and see how it works out</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> yeah, /me just likes all the shiny objects pretty icons ;) ... need to control myself</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> thx AnhVoMSFT +1.</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> so I think that about wraps in-progress development. I know paride has been tirelessly working on our CI infrastructure to improve quality of CI and false positives for failures due to resource constraints. So big thanks for paride working on our jenkins workers</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> This is an open topic to bring any cloud-init discussions, bugs, concerns or feature requests folks have.</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> In the absence of such topics we spend part of this time grooming the review queue to get back to dev</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> contributors so that they don't have stale branches waiting for input</p> -<p>16:50 <code>&lt;AnhVoMSFT&gt;</code> We had a review sent out to add some boot time telemetry collection as part of cloud-init analyze: <a href="https://code.launchpad.net/~samgilson/cloud-init/+git/cloud-init/+merge/368943">https://code.launchpad.net/~samgilson/cloud-init/+git/cloud-init/+merge/368943</a></p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> thanks AnhVoMSFT I'll grab a review slot on that one now</p> -<p>16:51 <code>&lt;AnhVoMSFT&gt;</code> would appreciate some reviews there and also on ideas on how to retrieve similar timestamps for FreeBSD</p> -<p>16:51 <code>&lt;rharper&gt;</code> AnhVoMSFT: yes, will review</p> -<p>16:51 <code>&lt;rharper&gt;</code> AnhVoMSFT: also, I filed a bug related to the azure telemetry, lemme get it</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> I'll kick off a CI run on that now</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> rharper: ^</p> -<p>16:52 <code>&lt;rharper&gt;</code> Bug 1833731</p> -<p>16:52 <code>&lt;ubot5&gt;</code> bug 1833731 in cloud-init "cloud-init analyze output not formatted cleanly on Azure" [Undecided,New] <a href="https://launchpad.net/bugs/1833731">https://launchpad.net/bugs/1833731</a></p> -<p>16:52 <code>&lt;rharper&gt;</code> AnhVoMSFT: not sure if the branch for review addresses the formatting of the output, but we should take a look to clean it up</p> -<p>16:52 <code>&lt;AnhVoMSFT&gt;</code> is there a good way to subscribe to new bugs with a certain keyword/tags? I.e., I would like to auto-subscribe to all bugs that has "Azure" in the bug title</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> rharper: if you get a chance to double check <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/369199">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/369199</a> we might be able to land that too</p> -<p>16:53 <code>&lt;rharper&gt;</code> blackboxsw: I asked you some questions, if you've replied, I'll look again</p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> rharper: nevermind, I see you already looked at it</p> -<p>16:53 <code>&lt;rharper&gt;</code> ah</p> -<p>16:53 <code>&lt;rharper&gt;</code> perfect</p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> thanks</p> -<p>16:53 <code>&lt;rharper&gt;</code> I think we're mostly fine; just a question on return values</p> -<p>16:53 * blackboxsw needed to refresh</p> -<p>16:54 <code>&lt;AnhVoMSFT&gt;</code> rharper I will take a look at the analyze output and see how we can improve it. If it is a minor change we can add it to the existing review</p> -<p>16:54 <code>&lt;rharper&gt;</code> AnhVoMSFT: no need to pull it into the existing stuff</p> -<p>16:55 <code>&lt;rharper&gt;</code> I'd prefer a separate targetted fix; which may land independently from the boot stage (which is super interesting on its own)</p> -<p>16:55 <code>&lt;AnhVoMSFT&gt;</code> cool - we will do a separate fix then</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> rharper: yeah that concern is clear, we are safe on the processing of region/az in absence of 'imds' key</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> it'll return none</p> -<p>16:57 <code>&lt;blackboxsw&gt;</code> by virtue of that last get('location|platformFaultDomain')</p> -<p>16:57 <code>&lt;blackboxsw&gt;</code> if either is absent due to any key above being absent, you'll get None as default value</p> -<p>16:58 <code>&lt;rharper&gt;</code> blackboxsw: ack</p> -<p>17:00 <code>&lt;nik736&gt;</code> Hi there, not sure if this is the right place to ask, but I have problems when creating a new VM, it only happens with the debian cloud image, ubuntu is fine. Booting is stuck at the drm line, the exact line is dependent on the video model type in my libvirt xml but it is basically stuck for 20-30sec and won't continue. It will boot eventually after that time. Thanks so much for any hints. Happy to provide</p> -<p>17:00 <code>&lt;nik736&gt;</code> further details.</p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> hrm, video model timeouts are a bit out of my wheelhouse :/</p> -<p>17:02 * blackboxsw pokes around a bit in google</p> -<p>17:02 <code>&lt;nik736&gt;</code> it seems to be that the lines after it would be about resizing the file system. I am not really sure if this is cloud-init related at all and I am not sure if it actually is caused by the video model or is just taking a bit to get to the next steps</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> nik736: you can run cloud-init analyze show or cloud-init analyze blame to see what cloud-init says it is spending a lot of time on</p> -<p>17:03 <code>&lt;nik736&gt;</code> I tried different host systems, Debian 18.04, 19.04, Debian 9, different libvirt versions, different qemu versions, nothing seems to be helping lol</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> (If you have cloud-init v 18 or later in your image I think)</p> -<p>17:04 <code>&lt;nik736&gt;</code> ah, ok, thanks, I will look into that</p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> nik736: also systemd-analyze blame is a good helper for what is killing boot time</p> -<p>17:04 <code>&lt;AnhVoMSFT&gt;</code> do you see any timestamp gap that reflects the 20-30s in cloud-init.log ?</p> -<p>17:08 <code>&lt;rharper&gt;</code> nik736: feel free to file a bug and attach logs from the 'cloud-init collect-logs' output (or serial console if available) and /var/log/cloud-init.log if you can get into the instance afterwards</p> -<p>17:08 <code>&lt;nik736&gt;</code> thanks for the help, currently looking into it</p> -<p>17:11 <code>&lt;AnhVoMSFT&gt;</code> rharper blackboxsw we have some instance deployment where cloud-init is hanging at the command ip route add - any idea how to look further?</p> -<p>17:12 <code>&lt;AnhVoMSFT&gt;</code> this does look like a platform problem, so it is more of a question related to networking, rather than cloud-init itself</p> -<p>17:14 <code>&lt;AnhVoMSFT&gt;</code> it's super hard to reproduce so the only thing we have so far to work with is logs. I thought the call to ip route add basically adds an entry to the kernel routing table. Is there an interaction with networking involved which might cause it to hang?</p> -<p>17:14 <code>&lt;rharper&gt;</code> AnhVoMSFT: I wonder if it's creating a route that breaks connection to IMDS or something else that cloud-init would then do an HTTP get on ?</p> -<p>17:17 <code>&lt;nik736&gt;</code> I saw in the log that 2 entries are around 1 minute apart "SUCCESS: searching for local datasources" and "Cloud-init v. 0.7.9 running 'init' at Mon, 24 Jun 2019 17:13:41 +0000. Up 73.67 seconds." I am not sure if this could be it or if this looks fine</p> -<p>17:18 <code>&lt;rharper&gt;</code> 0.7.9 is quite old, seeing the full cloud-init.log will be most useful for us to understand what's happening</p> -<p>17:19 <code>&lt;nik736&gt;</code> okay, sec</p> -<p>17:19 <code>&lt;AnhVoMSFT&gt;</code> rharper that is a good theory. I do see in a good case there's a call to IMDS immediately after that, although that call has a timeout. If it fails we should see more logs coming out of cloud-init. I'll look further into that todya</p> -<p>17:20 <code>&lt;nik736&gt;</code> @rharper <a href="https://pastebin.com/fzCSH5kC">https://pastebin.com/fzCSH5kC</a></p> -<p>17:20 <code>&lt;rharper&gt;</code> AnhVoMSFT: the retry logic in DataSourceAzure is quite long IIRC, so it's quite possible this is the very issue that blackboxsw is working w.r.t ensuring the instances always have a source-ip route to the IMDS</p> -<p>17:21 <code>&lt;AnhVoMSFT&gt;</code> rharper indeed it is long, and the log was overly suppressed to avoid log from growing too large while VM was waiting in pre-provisioning state. We are adding back some of the logs (in a smarter way to get enough details while avoiding huge log size)</p> -<p>17:22 <code>&lt;rharper&gt;</code> nik736: so, between line 260 and 261 there's a large timedelta; that's <em>outside</em> of cloud-init; cloud-init is executed separately 4 times (cloud-init init --local, cloud-init init, cloud-init config --modules, cloud-init config --final)</p> -<p>17:23 <code>&lt;rharper&gt;</code> nik736: so if you have a systemd journal, we could see what happens between the end of cloud-init-local.service and cloud-init.service (stage1 and 2);</p> -<p>17:23 <code>&lt;nik736&gt;</code> ah, okay, interesting</p> -<p>17:23 <code>&lt;nik736&gt;</code> will check</p> -<p>17:23 <code>&lt;rharper&gt;</code> or syslog might see stuff between those two time points</p> -<p>17:23 * rharper steps away for a bit, please keep sending info here; I'll respond when I;m back</p> -<p>17:24 <code>&lt;AnhVoMSFT&gt;</code> nik736 systemd-analyze critical-chain cloud-init.service might help here - I think some systemd service is running right after init-local and just before init and that service is taking time</p> -<p>17:25 <code>&lt;nik736&gt;</code> will check, thanks for your help, really appreciate it.</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> I think I'll wrap the meeting here, but we can continue the conversation. Thanks again folks for the discussions</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> next meeting will be July 8th</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> as updated in the topic</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> meeting minutes will be posted to</p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io">https://cloud-init.github.io</a></p> -<p>17:33 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2019-06-10T16:19:00+00:002019-06-10T16:19:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2019-06-10:/status-2019-06-10.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 10 Jun at 16:19 &mdash; 17:31 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-06-10-16.19.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-06-10-16.19.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io">https://cloud-init.github.io</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:23.</p> -<h3>Recent Changes</h3> -<p>The …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 10 Jun at 16:19 &mdash; 17:31 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-06-10-16.19.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-06-10-16.19.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io">https://cloud-init.github.io</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:23.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:24.</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>In Progress Development</h3> -<p>The discussion about "In Progress Development" started at 16:30.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/cloud-init/+activereviews">https://code.launchpad.net/cloud-init/+activereviews</a> </li> -</ul> -<h3>Office Hours</h3> -<p>The discussion about "Office Hours" started at 16:45.</p> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 16:48.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://netplan.io/faq#how-to-go-back-to-ifupdown">https://netplan.io/faq#how-to-go-back-to-ifupdown</a> </li> -<li><strong>ACTION</strong>: follow up any bugs related to Azure/netplan uninstall in favor ifupdown to see if cloud-init has actionable feature work to ensure proper network renderer is used</li> -</ul> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (39)</li> -<li>rharper (39)</li> -<li>AnhVoMSFT (29)</li> -<li>cyphermox (12)</li> -<li>robjo (6)</li> -<li>meetingology (4)</li> -<li>ubot5 (3)</li> -<li>paride (1)</li> -<li>Odd_Bloke (1)</li> -</ul> -<h2>Full Log</h2> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:19 <code>&lt;meetingology&gt;</code> Meeting started Mon Jun 10 16:19:45 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:19 <code>&lt;meetingology&gt;</code> </p> -<p>16:19 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:19 <code>&lt;rharper&gt;</code> o/</p> -<p>16:20 <code>&lt;Odd_Bloke&gt;</code> o/</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> hi cloud-init folks. let's kick off the bi-weekly meeting again</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> our last meeting minutes are hosted on github</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io">https://cloud-init.github.io</a></p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> welcome all. Generally cloud-init upstream uses this meeting to provide a platform for status updates, raising questions or concerns and feature discussion. All are encouraged to participate as you see fit.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> our format is the following topics: Previous Actions, Recent Changes, In-progress Development, Office Hours</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> interjections and additional topics are welcome</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> Checking last meeting's minutes we were clear of old actions.</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> so we'll jump to the next topic this week.</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> the following commits landedd in cloud-init tip since the last status meeting</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> - Allow identification of OpenStack by Asset Tag</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> [Mark T. Voelker] (<a href="[https://bugs.launchpad.net/bugs/1669875](https://bugs.launchpad.net/bugs/1669875)">LP: #1669875</a>)</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> - Fix spelling error making 'an Ubuntu' consistent. [Brian Murray]</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> - run-container: centos: comment out the repo mirrorlist [Paride Legovini]</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> - netplan: update netplan key mappings for gratuitous-arp</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> [Ryan Harper] (<a href="[https://bugs.launchpad.net/bugs/1827238](https://bugs.launchpad.net/bugs/1827238)">LP: #1827238</a>)</p> -<p>16:26 <code>&lt;ubot5&gt;</code> Launchpad bug 1669875 in OpenStack Compute (nova) "identify openstack vmware platform" [Wishlist,Confirmed]</p> -<p>16:26 <code>&lt;ubot5&gt;</code> Launchpad bug 1827238 in cloud-init "Machines fail to deploy because cloud-init needs to accept both netplan spellings for grat arp" [Medium,Fix committed]</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> I was poking around out trello board to see if we've moved other cloud-init related content into the done lane, but I think those commits about capture the recent work</p> -<p>16:30 <code>&lt;blackboxsw&gt;</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:30 <code>&lt;blackboxsw&gt;</code> #topic In Progress Development</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> our active reviews are located here (as mentioned in the topic)</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/cloud-init/+activereviews">https://code.launchpad.net/cloud-init/+activereviews</a></p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> Goneri: thanks for all the work on freebsd branches, there has been some good momentum there</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> there is ongoing work from Azure datasource that will likely land in the next week or two</p> -<p>16:33 <code>&lt;paride&gt;</code> ^^ "run-container: centos: comment out the repo mirrorlist", only actually relevent when using an http/https proxy, in all the other cases the mirrorlist works as usual</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> and some network-related changes landing shortly</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> paride: thank you paride for the extra note</p> -<p>16:33 <code>&lt;AnhVoMSFT&gt;</code> blackboxsw can you share more details on the work from Azure datasource ? Any bug that we can reference?</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> I was thinking <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/364012">https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/364012</a> AnhVoMSFT</p> -<p>16:35 <code>&lt;rharper&gt;</code> related to sorting out covering the all the network related scenarios so that we configure network in a way that ensures access to IMDS and internet in the face of additional static ips on the same subnet as the primary interface, multiple dhcp interfaces with default routes,</p> -<p>16:35 <code>&lt;AnhVoMSFT&gt;</code> I see - I think there potentially needs some bigger change there, as there was some issue around identifying the primary/secondary NIC. We got confirmation from our netwoking team that the first NIC returned is the primary</p> -<p>16:35 <code>&lt;rharper&gt;</code> AnhVoMSFT: good to know; that was our observation</p> -<p>16:36 <code>&lt;rharper&gt;</code> AnhVoMSFT: <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1815254">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1815254</a> , related as well; the plan being to put in place some source-based routing;</p> -<p>16:36 <code>&lt;ubot5&gt;</code> Launchpad bug 1815254 in cloud-init (Ubuntu) "Azure multiple ips prevent access to metadata service" [Undecided,Confirmed]</p> -<p>16:38 <code>&lt;AnhVoMSFT&gt;</code> thanks rharper - is that something that should be changed/fixed from cloudinit, or is this more platform related?</p> -<p>16:38 <code>&lt;rharper&gt;</code> that's a good question; generally it would be <em>great</em> if a platform were to include source-routes and metrics in the config they send</p> -<p>16:38 <code>&lt;AnhVoMSFT&gt;</code> if the latter I will file a workitem on our side to go do some research and get the right team to take a look at it</p> -<p>16:39 <code>&lt;rharper&gt;</code> currently no cloud does this, rather <em>some</em> indicate a <em>primary</em> via metadata, and then the OS scripts apply a metric to all non-primary routes to ensure that default routes go to the primary</p> -<p>16:39 <code>&lt;AnhVoMSFT&gt;</code> I see - so I guess we can do similarly on Azure since we know what the primary is (first nic returned in IMDS)</p> -<p>16:40 <code>&lt;rharper&gt;</code> AnhVoMSFT: so in the short term, I think cloud-init should (where possible with the OS network config) provide additional tuning (likely post-scripts in some cases) to tune the routing for what cloud-init knows is the primary route</p> -<p>16:40 <code>&lt;rharper&gt;</code> AnhVoMSFT: yes, I prefer a primary=True or whatever, but it's good enough to have the current behavior documented (in the code)</p> -<p>16:40 <code>&lt;AnhVoMSFT&gt;</code> thanks rharper</p> -<p>16:40 <code>&lt;rharper&gt;</code> so if it change/breaks, then we know</p> -<p>16:44 <code>&lt;rharper&gt;</code> I think that covers our in-progress items for the moment</p> -<p>16:45 <code>&lt;rharper&gt;</code> not sure if the bot will listen to me, but just in case</p> -<p>16:45 <code>&lt;robjo&gt;</code> Be mindful that in Azure the metadata service may lag behind by minutes w.r.t. secondary IPs on an interface</p> -<p>16:45 <code>&lt;rharper&gt;</code> #topic Office Hours</p> -<p>16:45 <code>&lt;rharper&gt;</code> robjo: in general, my awareness is that the instance has to be off line to change vnets and such; and booting back up has been enough time to see IMDS updated, do you see differently ?</p> -<p>16:46 <code>&lt;AnhVoMSFT&gt;</code> robjo that is good to know, I will check on that</p> -<p>16:46 <code>&lt;robjo&gt;</code> We've had various issues with cloud-netconfig due to the metadata server in Azure being slow and reverted to polling, which of course got us in trouble with API rate limits</p> -<p>16:46 <code>&lt;rharper&gt;</code> robjo: interesting</p> -<p>16:47 <code>&lt;rharper&gt;</code> We'll here in channel so if youve;; got merges or bugs that need an eye or just questions, fire away</p> -<p>16:47 <code>&lt;AnhVoMSFT&gt;</code> robjo feel free to file a bug on that and we will investigate - IMDS is our partner team so we'll get some answer quickly there</p> -<p>16:48 <code>&lt;AnhVoMSFT&gt;</code> rharper, a couple things I want to ask for Office Hours</p> -<p>16:48 <code>&lt;robjo&gt;</code> AnhVoMSFT: We have been working with Stephen Zarkos on the issues</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:48 <code>&lt;AnhVoMSFT&gt;</code> robjo I will ping Stephen and get more detail and see if we have any follow up items</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> sorry folks got pulled away for a bit thx rharper</p> -<p>16:48 <code>&lt;robjo&gt;</code> And double checked that the polling direction was OK form the Microsoft perspective before we implemented that</p> -<p>16:49 <code>&lt;AnhVoMSFT&gt;</code> I see, glad you're not blocked on it</p> -<p>16:50 <code>&lt;robjo&gt;</code> rharper: We always had bug reports that upon reboot not everything was always configured when secondary IP addresses were in play. But theoretically yes upon reboot everything should be there</p> -<p>16:50 <code>&lt;AnhVoMSFT&gt;</code> rharper we have a customer who booted up a VM based on 18.04, which uses netplan. Cloudinit wrote a netplan file to the image. He then installed ifupdown, then had some networking change which triggered a mac address change. Upon rebooting, cloudinit tries to use eni, but netplan file was still there, which caused his VM to mess up the network config</p> -<p>16:50 <code>&lt;robjo&gt;</code> putting cloud-netconfig into polling mode pretty mush addresses the issues we had reports about</p> -<p>16:51 <code>&lt;rharper&gt;</code> AnhVoMSFT: yes; that sounds very likely</p> -<p>16:51 <code>&lt;rharper&gt;</code> AnhVoMSFT: did they file a bug?</p> -<p>16:51 <code>&lt;rharper&gt;</code> cloud-init net "detects" which service is present</p> -<p>16:51 <code>&lt;AnhVoMSFT&gt;</code> I'm checking to see if this should be a bug, or that is expected behavior</p> -<p>16:51 <code>&lt;rharper&gt;</code> so if they did not uninstall netplan.io then cloud-init will likely prefer that over eni</p> -<p>16:52 <code>&lt;AnhVoMSFT&gt;</code> cloudinit actually prefers eni if ifupdown is installed, I think</p> -<p>16:52 <code>&lt;rharper&gt;</code> AnhVoMSFT: so the etc/netplan/*.yaml would only trigger things if netplan is still present; the systemd-generator will read yaml and write out networkd files</p> -<p>16:53 <code>&lt;AnhVoMSFT&gt;</code> right, I think the customer's mistake was to not uninstall netplan (or remove any netplan configuration file) after installing ifupdown</p> -<p>16:53 <code>&lt;rharper&gt;</code> AnhVoMSFT: right; I think we'll need to see the log and system state, but it sounds like an incomplete uninstall of netplan</p> -<p>16:53 <code>&lt;rharper&gt;</code> uninstall of netplan should be enough to make the cloud-init.yaml inert</p> -<p>16:54 <code>&lt;rharper&gt;</code> <a href="https://netplan.io/faq#how-to-go-back-to-ifupdown">https://netplan.io/faq#how-to-go-back-to-ifupdown</a></p> -<p>16:54 <code>&lt;rharper&gt;</code> AnhVoMSFT: it <em>should</em> have automatically uninstall netplan.io</p> -<p>16:54 <code>&lt;AnhVoMSFT&gt;</code> I'm not sure if there is much we can do from the cloudinit side - perhaps if choosing eni, disable the cloud-init netplan yaml</p> -<p>16:54 <code>&lt;rharper&gt;</code> AnhVoMSFT: well, we could check writable paths of the renderers</p> -<p>16:54 <code>&lt;AnhVoMSFT&gt;</code> rharper I don't think that is the behavior on 18.04 - installing ifupdown will not uninstall netplan</p> -<p>16:55 <code>&lt;rharper&gt;</code> AnhVoMSFT: you're right; =(</p> -<p>16:55 <code>&lt;rharper&gt;</code> that sort of feels like a bug in the packaging</p> -<p>16:55 <code>&lt;AnhVoMSFT&gt;</code> yes, I share the same sentiment</p> -<p>16:56 <code>&lt;AnhVoMSFT&gt;</code> I will go ahead and file a bug so even if we don't have a short term action we can still capture the discussion</p> -<p>16:57 <code>&lt;rharper&gt;</code> AnhVoMSFT: thanks, I'm pinging in #netplan and the bug will be great so we can figure out the right plan</p> -<p>16:59 <code>&lt;AnhVoMSFT&gt;</code> second question: We have an intern working in our team and as part of warming up in cloudinit he wrote some additional capabilities into cloud-init analyze, adding a "boot" module (in addition to show/blame/dump), which collects timestamps of phases happening during vm booting up, but before cloudinit started, such as kernel initialization, systemd initialization..</p> -<p>17:00 <code>&lt;AnhVoMSFT&gt;</code> this should work for all cloud (he tested in AWE/GCP). Currently only works for distros that uses systemd. He'll try to figure out how to get those counters for freebsd and others</p> -<p>17:00 <code>&lt;AnhVoMSFT&gt;</code> rharper since you were the original author of analyze, I'm trying to gauge the interest on this and we're open to suggestions/questions</p> -<p>17:01 <code>&lt;cyphermox&gt;</code> rharper: they can coexist and configure each their own interface, so it's not a conflict. It's no different than coexisting ifupdown and NetworkManager, or also NetworkManager and systemd-networkd</p> -<p>17:01 <code>&lt;rharper&gt;</code> AnhVoMSFT: that sounds excellent</p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> nice AnhVoMSFT on the commandline extensions!</p> -<p>17:01 <code>&lt;rharper&gt;</code> AnhVoMSFT: happy to review branch or Work-in-Progress when it's available</p> -<p>17:02 <code>&lt;AnhVoMSFT&gt;</code> thanks rharper blackboxsw we will have that in a branch very soon.</p> -<p>17:03 <code>&lt;AnhVoMSFT&gt;</code> cyphermox if that is the case then either the customer or cloudinit needs to make sure the system does not have conflicting configuration for netplan/eni.</p> -<p>17:03 <code>&lt;rharper&gt;</code> cyphermox: ok; would you be open to some sort of warning about having config in both or something? I dunno; it's just not a great experience to add the new package, configure it, reboot and not have networking since the same interface was configured (differenlty) in both packages</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> yeah, I'm quite intterested in any additional cli functionality that cloud-init more versatile as a system debug tool</p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> <em>makes cloud-init more versatile</em></p> -<p>17:04 <code>&lt;cyphermox&gt;</code> rharper: I'm not opposed to a warning, but that's not necessarily better UX.</p> -<p>17:05 <code>&lt;cyphermox&gt;</code> debconf prompts are quite annoying to have at upgrade, and just writing it out people are likely to miss it altogether</p> -<p>17:05 <code>&lt;cyphermox&gt;</code> (so you wouldn't really gain much)</p> -<p>17:05 <code>&lt;AnhVoMSFT&gt;</code> blackboxsw yep that was the goal - we want to be able to deploy 1000 VMs, then use cloud-init analyze output to analyze the 50th/99th percentile of where the timing was spent during system boot, and we need some more insights into phases before cloud-init started as well</p> -<p>17:05 <code>&lt;rharper&gt;</code> cyphermox: agreed; having a pointer to suggest cleaning/checking/confirming configs if /etc/netplan/ is non-empty and netplan.io is installed</p> -<p>17:06 <code>&lt;cyphermox&gt;</code> rharper: one option is to parse enough of /etc/network/ to catch mentions of the interface, but that's not necessarily super solid (though it's the best option), because people can rename interfaces in netplan and match by mac</p> -<p>17:06 <code>&lt;rharper&gt;</code> might be helpful; though I agree that they may still ignore that; and cloud-init could do some more work to see if an image has multiple renderers available and ensure it didn't leave config for a previous boot around</p> -<p>17:07 <code>&lt;rharper&gt;</code> cyphermox: yeah; cloud-init knows more about the config and both formats; we're likely in a better spot to see "you've configured this interface twice"</p> -<p>17:08 <code>&lt;cyphermox&gt;</code> rharper: so in short, I'm not opposed to improving the UX, but I'm not wowed by any solution right now (even mine)</p> -<p>17:09 <code>&lt;rharper&gt;</code> cyphermox: that's fair; thanks</p> -<p>17:09 <code>&lt;AnhVoMSFT&gt;</code> i think a fix in cloudinit might make most stakeholders happy here. It knows which configuration file it wrote, so it can definitely look for conflicting configurations</p> -<p>17:09 <code>&lt;rharper&gt;</code> cyphermox: AnhVoMSFT is going to file the customer bug with details and we can discuss what (if any) improvements are to be made; I suspect cloud-init can help most here</p> -<p>17:09 <code>&lt;cyphermox&gt;</code> yes, I think so too</p> -<p>17:09 <code>&lt;rharper&gt;</code> cyphermox: thanks for the input</p> -<p>17:09 <code>&lt;AnhVoMSFT&gt;</code> it can't be responsible for everything the customer does though. If customer writes some my-own-netplan.yml, we can't help much</p> -<p>17:10 <code>&lt;cyphermox&gt;</code> rharper: but hey, if someone was to write a check when running netplan apply that there exists config in /etc/network, I wouldn't have much issues merging it</p> -<p>17:10 <code>&lt;rharper&gt;</code> AnhVoMSFT: right, we have several "maybe_delete_if" where we verify expected output before we remove things</p> -<p>17:10 <code>&lt;cyphermox&gt;</code> I just know I won't have time to look into this myself in the near future</p> -<p>17:10 <code>&lt;rharper&gt;</code> cyphermox: ack</p> -<p>17:11 <code>&lt;cyphermox&gt;</code> I think what will help most is aggressively deprecating and removing ifupdown</p> -<p>17:13 <code>&lt;cyphermox&gt;</code> that said, the best we can realistically do for the time being is to demote it to universe</p> -<p>17:13 <code>&lt;cyphermox&gt;</code> (and that's not going to change anything for UX)</p> -<p>17:15 <code>&lt;AnhVoMSFT&gt;</code> we had another instance of someone installing ifupdown2, which had the effect of removing cloud-init on debian/ubuntu 16.04</p> -<p>17:16 <code>&lt;AnhVoMSFT&gt;</code> and totally hosed his system, but that's a different issue altogether</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> s</p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> thanks for the good discussion folks, I guess we'll just add an action item to followup on a netplan bug for next time to see where we are at</p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> #action follow up any bugs related to Azure/netplan uninstall in favor ifupdown to see if cloud-init has actionable feature work to ensure proper network renderer is used</p> -<p>17:31 * meetingology follow up any bugs related to Azure/netplan uninstall in favor ifupdown to see if cloud-init has actionable feature work to ensure proper network renderer is used</p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> ok, I'll post minutes on this. thank you again rharper for driving</p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> and for the participation robjo cyphermox and AnhVoMSFT</p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2019-05-28T15:23:00+00:002019-05-28T15:23:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2019-05-28:/status-2019-05-28.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 28 May at 15:23 &mdash; 16:19 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-05-28-15.23.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-05-28-15.23.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 15:27.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-05-13.html#status-2019-05-13">https://cloud-init.github.io/status-2019-05-13.html#status-2019-05-13 …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 28 May at 15:23 &mdash; 16:19 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-05-28-15.23.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-05-28-15.23.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 15:27.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-05-13.html#status-2019-05-13">https://cloud-init.github.io/status-2019-05-13.html#status-2019-05-13</a> </li> -</ul> -<h3>Recent changes</h3> -<p>The discussion about "Recent changes" started at 15:30.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://discourse.ubuntu.com/t/sru-of-cloud-init-19-1-released/11028/2">https://discourse.ubuntu.com/t/sru-of-cloud-init-19-1-released/11028/2</a> </li> -<li><strong>LINK</strong>: <a href="https://lists.launchpad.net/cloud-init/msg00211.html">https://lists.launchpad.net/cloud-init/msg00211.html</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 15: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> -</ul> -<h3>Office hours (next ~30 mins)</h3> -<p>The discussion about "Office hours (next ~30 mins)" started at 15:44.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/cloud-init/+activereviews">https://code.launchpad.net/cloud-init/+activereviews</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082">https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082</a> </li> -<li><strong>ACTION</strong>: blackboxsw discuss with the team about landing the branch <a href="https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082">https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082</a></li> -</ul> -<h2>Vote results</h2> -<h2>Action items, by person</h2> -<ul> -<li>blackboxsw</li> -<li>blackboxsw discuss with the team about landing the branch <a href="https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082">https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082</a></li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (44)</li> -<li>meetingology (4)</li> -<li>akik (2)</li> -<li>ubot5 (2)</li> -</ul> -<h2>Full Log</h2> -<p>15:23 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>15:23 <code>&lt;meetingology&gt;</code> Meeting started Tue May 28 15:23:50 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>15:23 <code>&lt;meetingology&gt;</code> </p> -<p>15:23 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>15:23 <code>&lt;blackboxsw&gt;</code> there we go</p> -<p>15:24 <code>&lt;blackboxsw&gt;</code> Hey folks, time for another bi-weekly cloud-init status. Welcome all!</p> -<p>15:25 <code>&lt;blackboxsw&gt;</code> Generally cloud-init upstream uses this meeting to provide a platform for status updates, raising questions or concerns and feature discussion. All are encouraged to participate as you see fit.</p> -<p>15:25 <code>&lt;blackboxsw&gt;</code> Generally the topics we would like to cover are the following: Previous Actions, Recent Changes, In-progress Development, Office Hours</p> -<p>15:26 <code>&lt;blackboxsw&gt;</code> without further ado let's jump into it.</p> -<p>15:27 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>15:27 <code>&lt;blackboxsw&gt;</code> From our previous meeting minutes we had a couple of action items that I think are resolved</p> -<p>15:27 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2019-05-13.html#status-2019-05-13">https://cloud-init.github.io/status-2019-05-13.html#status-2019-05-13</a></p> -<p>15:28 * blackboxsw Odd_Bloke confirm correct status of <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</a></p> -<p>15:28 <code>&lt;ubot5&gt;</code> Launchpad bug 1801364 in cloud-init "persisting OpenStack metadata fails" [Undecided,Confirmed]</p> -<p>15:28 <code>&lt;blackboxsw&gt;</code> Dan confirmed that this is the proper bug status and still needs a fix</p> -<p>15:28 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: we had an action related to you "followup on recommended approach for getting kernel/userspace timestamp with or without python-dbus package dependency"</p> -<p>15:29 <code>&lt;blackboxsw&gt;</code> I know rharper had a comment or two in channel about this approach. Hopefully AnhVoMSFT you have everything you need there</p> -<p>15:29 <code>&lt;blackboxsw&gt;</code> if not, you can feel free to ping us for more discussion on that feature</p> -<p>15:30 <code>&lt;blackboxsw&gt;</code> #topic Recent changes</p> -<p>15:31 <code>&lt;blackboxsw&gt;</code> Big news since last bi-weekly status meeting is that we have completed and published 19.1.1 in an SRU into Ubuntu Xenial, Bionic, Cosmic and Disco as of yesterday.</p> -<p>15:31 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: wrote up some content and email around this for more context. Thanks Odd_Bloke</p> -<p>15:32 <code>&lt;blackboxsw&gt;</code> #link <a href="https://discourse.ubuntu.com/t/sru-of-cloud-init-19-1-released/11028/2">https://discourse.ubuntu.com/t/sru-of-cloud-init-19-1-released/11028/2</a></p> -<p>15:33 <code>&lt;blackboxsw&gt;</code> #link <a href="https://lists.launchpad.net/cloud-init/msg00211.html">https://lists.launchpad.net/cloud-init/msg00211.html</a></p> -<p>15:38 <code>&lt;blackboxsw&gt;</code> beyond that we have the following upstream commits landed</p> -<p>15:39 <code>&lt;blackboxsw&gt;</code> d9b1e5de91..HEAD | log2dch</p> -<p>15:39 <code>&lt;blackboxsw&gt;</code> - freebsd: NoCloud data source support [Gonéri Le Bouder] (LP: #1645824)</p> -<p>15:39 <code>&lt;blackboxsw&gt;</code> - Azure: Return static fallback address as if failed to find endpoint</p> -<p>15:39 <code>&lt;blackboxsw&gt;</code> [Jason Zions (MSFT)]</p> -<p>15:39 <code>&lt;ubot5&gt;</code> Launchpad bug 1645824 in cloud-init "NoCloud source doesn't work on FreeBSD" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1645824">https://launchpad.net/bugs/1645824</a></p> -<p>15:40 <code>&lt;blackboxsw&gt;</code> Thanks again Jason and Gonéri for the commits there. We have a few branches in the wings under review for freebsd and azure that I expect will be landing this week</p> -<p>15:41 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>15:42 <code>&lt;blackboxsw&gt;</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>15:43 <code>&lt;blackboxsw&gt;</code> Our upcoming work is set and scheduled on this trello board above. As we grab new significant tasks and dev work for cloud-init we will pull those cards into the doing lane</p> -<p>15:44 <code>&lt;blackboxsw&gt;</code> #topic Office hours (next ~30 mins)</p> -<p>15:45 <code>&lt;blackboxsw&gt;</code> This topic is an opportunity for anyone to bring their bugs, features, questions or branches to get some extra eyes or discussion around current development.</p> -<p>15:47 <code>&lt;blackboxsw&gt;</code> It is also a slot of time where upstream developers will be spending some time reviewing active branches to unblock community members and help increase velocity of our review queue.</p> -<p>15:47 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/cloud-init/+activereviews">https://code.launchpad.net/cloud-init/+activereviews</a></p> -<p>15:48 * blackboxsw does as review pass on <a href="https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/367315.">https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/367315.</a> I'm grabbing an active review slot for this now</p> -<p>15:52 <code>&lt;akik&gt;</code> ls</p> -<p>15:52 <code>&lt;akik&gt;</code> sorry</p> -<p>16:03 <code>&lt;blackboxsw&gt;</code> yeah this looks good Goneri <a href="https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/367315...">https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/367315...</a> approved</p> -<p>16:03 <code>&lt;blackboxsw&gt;</code> will merge in ~15</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> smoser: so sorry on the review delay here for the doc change you took over. <a href="https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/343546">https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/343546</a></p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> just approved with a nit if you are around to push that. if not, I'll get that doc branch merged in tomorrow</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> I think that about wraps this status meeting this week. I think we should take an action to talk about we want to do with this old branch.</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082">https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082</a></p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> #action blackboxsw discuss with the team about landing the branch <a href="https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082">https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082</a></p> -<p>16:16 * meetingology blackboxsw discuss with the team about landing the branch <a href="https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082">https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082</a></p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> We'll hold the next cloud-init status meeting on Monday 3/10</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> and I'll post the status minutes up to <a href="https://cloud-init.github.io">https://cloud-init.github.io</a> momentarily</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> Thanks again. have a good one guys and gals.</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2019-05-13T16:25:00+00:002019-05-13T16:25:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2019-05-13:/status-2019-05-13.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 13 May at 16:25 &mdash; 17:32 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-05-13-16.25.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-05-13-16.25.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:31.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-01-28.html#status-2019-01-28">https://cloud-init.github.io/status-2019-01-28.html#status-2019-01-28 …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 13 May at 16:25 &mdash; 17:32 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-05-13-16.25.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-05-13-16.25.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:31.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2019-01-28.html#status-2019-01-28">https://cloud-init.github.io/status-2019-01-28.html#status-2019-01-28</a> </li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</a> </li> -<li><strong>ACTION</strong>: Odd_Bloke confirm correct status of <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</a></li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:35.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://launchpad.net/cloud-init/+milestone/19.1">https://launchpad.net/cloud-init/+milestone/19.1</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:46.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://wiki.ubuntu.com/CloudinitUpdates">https://wiki.ubuntu.com/CloudinitUpdates</a> </li> -<li><strong>LINK</strong>: <a href="https://trello.com/c/oxv61bPl/1099-sru-191-xenial-bionic-cosmic-and-disco">https://trello.com/c/oxv61bPl/1099-sru-191-xenial-bionic-cosmic-and-disco</a> </li> -<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> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367301">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367301</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367302">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367302</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367297">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367297</a> </li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1828637">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1828637</a> </li> -<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>Office hours (next ~30 mins)</h3> -<p>The discussion about "Office hours (next ~30 mins)" started at 17:02.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloudinit.readthedocs.io/en/latest/topics/tests.html#">https://cloudinit.readthedocs.io/en/latest/topics/tests.html#</a> </li> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io">https://cloud-init.github.io</a> </li> -<li><strong>ACTION</strong>: Odd_Bloke/rharper/AnhVoMSFT followup on recommended approach for getting kernel/userspace timestamp with or without python-dbus package dependency</li> -</ul> -<h2>Vote results</h2> -<h2>Action items, by person</h2> -<ul> -<li>AnhVoMSFT</li> -<li>Odd_Bloke/rharper/AnhVoMSFT followup on recommended approach for getting kernel/userspace timestamp with or without python-dbus package dependency</li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (163)</li> -<li>AnhVoMSFT (20)</li> -<li>ubot5` (19)</li> -<li>meetingology (5)</li> -<li>powersj (3)</li> -</ul> -<h2>Full Log</h2> -<p>16:25 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:25 <code>&lt;meetingology&gt;</code> Meeting started Mon May 13 16:25:37 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:25 <code>&lt;meetingology&gt;</code> </p> -<p>16:25 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> hi folks, we are restarting the cloud-init community status meeting so we can have a community forum to discuss current cloud-init development and try to improve momentum in the cloud-init project efforts.</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> over the last couple of months we had taken a break from this meeting. But, I think it's shown us that there is demand and usefulness in continuing hosting these meetings. So, from here on, we expect to post the upcoming date of status meetings in this channel's room topic.</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> Again the goal of this meeting is to give people a chance to see what work is currently being performed on upstream cloud-init as well as a forum to discuss or raise concerns or get eyes on potential bugs or features.</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> Generally the topics we would like to cover are the following: (and interjections/suggestions are always welcome</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> topics: Previous Actions, Recent Changes, In-progress Development, Office Hours.</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> so, looking at our last status minutes from the last meeting, (on Jan 28.... :( ) we had one action carried over</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2019-01-28.html#status-2019-01-28">https://cloud-init.github.io/status-2019-01-28.html#status-2019-01-28</a></p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> review and land <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098</a></p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> that's done. as well as an openstack bug...</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</a></p> -<p>16:33 <code>&lt;ubot5</code>&gt;` Ubuntu bug 1801364 in cloud-init "persisting OpenStack metadata fails" [Undecided,Confirmed]</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: has landed this bug, I think it needs to be marked fix committed though</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> Odd_Bloke: is out today at a meeting, but I'll mark that action so we can make sure that bug status is properly reported (if there are no other branches to land for it)</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> #action Odd_Bloke confirm correct status of <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</a></p> -<p>16:34 * meetingology Odd_Bloke confirm correct status of <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</a></p> -<p>16:34 <code>&lt;ubot5</code>&gt;` Ubuntu bug 1801364 in cloud-init "persisting OpenStack metadata fails" [Undecided,Confirmed]</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> That;s about it for actions from previous meeting.</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> Here we list current content that has landed in cloud-init since last meeting..... because it has been a really long time since last meeting, I'm going to redact this to the last month or so of content to avoid getting banned in this channel for spam</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - Azure: Return static fallback address as if failed to find endpoint</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> [Jason Zions (MSFT)]</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - release 19.1 (LP: #1828479)</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - freebsd: add chpasswd pkg in the image [Gonéri Le Bouder]</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - tests: add Eoan release [Paride Legovini]</p> -<p>16:37 <code>&lt;ubot5</code>&gt;` Launchpad bug 1828479 in cloud-init "Release 19.1" [Undecided,Fix released] <a href="https://launchpad.net/bugs/1828479">https://launchpad.net/bugs/1828479</a></p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> hah, I don't think that worked</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> ok breaking that content up</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - Azure: Return static fallback address as if failed to find endpoint</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> [Jason Zions (MSFT)]</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - release 19.1 (LP: #1828479)</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - freebsd: add chpasswd pkg in the image [Gonéri Le Bouder]</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - tests: add Eoan release [Paride Legovini]</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - cc_mounts: check if mount -a on no-change fstab path</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> [Jason Zions (MSFT)] (LP: #1825596)</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - replace remaining occurrences of LOG.warn [Daniel Watkins]</p> -<p>16:37 <code>&lt;ubot5</code>&gt;` Launchpad bug 1825596 in cloud-init "Azure reboot with unformatted ephemeral drive won't mount reformatted volume" [High,Fix released] <a href="https://launchpad.net/bugs/1825596">https://launchpad.net/bugs/1825596</a></p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - DataSourceAzure: Adjust timeout for polling IMDS [Anh Vo]</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - Azure: Changes to the Hyper-V KVP Reporter [Anh Vo]</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - git tests: no longer show warning about safe yaml.</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - tools/read-version: handle errors [Chad Miller]</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - net/sysconfig: only indicate available on known sysconfig distros</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> (LP: #1819994)</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - packages: update rpm specs for new bash completion path</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> [Daniel Watkins] (LP: #1825444)</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - test_azure: mock util.SeLinuxGuard where needed</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> [Jason Zions (MSFT)] (LP: #1825253)</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - setup.py: install bash completion script in new location [Daniel Watkins]</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - mount_cb: do not pass sync and rw options to mount</p> -<p>16:37 <code>&lt;ubot5</code>&gt;` Launchpad bug 1819994 in Provider for Plainbox - Canonical Certification Server "cloud-init selects sysconfig netconfig renderer if network-manager is installed on Ubuntu" [Critical,Confirmed] <a href="https://launchpad.net/bugs/1819994">https://launchpad.net/bugs/1819994</a></p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> [Gonéri Le Bouder] (LP: #1645824)</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - cc_apt_configure: fix typo in apt documentation [Dominic Schlegel]</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - Revert "DataSource: move update_events from a class to an instance..."</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> [Daniel Watkins]</p> -<p>16:37 <code>&lt;ubot5</code>&gt;` Launchpad bug 1825444 in cloud-init (Ubuntu) ""make rpm" fails on CentOS after commit 947d3c208" [Undecided,Fix released] <a href="https://launchpad.net/bugs/1825444">https://launchpad.net/bugs/1825444</a></p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - Change DataSourceNoCloud to ignore file system label's case.</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> [Risto Oikarinen]</p> -<p>16:38 <code>&lt;ubot5</code>&gt;` Launchpad bug 1825253 in cloud-init "Unit tests with filesystem-related mocks fail in SeLinuxGuard when run on RHEL or CentOS" [Undecided,Fix released] <a href="https://launchpad.net/bugs/1825253">https://launchpad.net/bugs/1825253</a></p> -<p>16:38 <code>&lt;ubot5</code>&gt;` Launchpad bug 1645824 in cloud-init "NoCloud source doesn't work on FreeBSD" [Medium,Fix released] <a href="https://launchpad.net/bugs/1645824">https://launchpad.net/bugs/1645824</a></p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - cmd:main.py: Fix missing 'modules-init' key in modes dict</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> [Antonio Romito] (LP: #1815109)</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - ubuntu_advantage: rewrite cloud-config module</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - Azure: Treat _unset network configuration as if it were absent</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> [Jason Zions (MSFT)] (LP: #1823084)</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - DatasourceAzure: add additional logging for azure datasource [Anh Vo]</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - cloud_tests: fix apt_pipelining test-cases</p> -<p>16:38 <code>&lt;ubot5</code>&gt;` Launchpad bug 1815109 in cloud-init "cloud-final.service: "cloud-init modules --mode final" exit with "KeyError: 'modules-init'" after upgrade to version 18.2" [Medium,Fix released] <a href="https://launchpad.net/bugs/1815109">https://launchpad.net/bugs/1815109</a></p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - Azure: Ensure platform random_seed is always serializable as JSON.</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> [Jason Zions (MSFT)]</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - net/sysconfig: write out SUSE-compatible IPv6 config [Robert Schweikert]</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - tox: Update testenv for openSUSE Leap to 15.0 [Thomas Bechtold]</p> -<p>16:38 <code>&lt;ubot5</code>&gt;` Launchpad bug 1823084 in cloud-init "DataSourceAzure doesn't rebuild network-config after reboot" [High,Fix released] <a href="https://launchpad.net/bugs/1823084">https://launchpad.net/bugs/1823084</a></p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - net: Fix ipv6 static routes when using eni renderer</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> [Raphael Glon] (LP: #1818669)</p> -<p>16:38 <code>&lt;ubot5</code>&gt;` Launchpad bug 1818669 in cloud-init "ipv6 static routes configured for eni are incorrect" [Undecided,Fix released] <a href="https://launchpad.net/bugs/1818669">https://launchpad.net/bugs/1818669</a></p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - Add ubuntu_drivers config module [Daniel Watkins]</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - doc: Refresh Azure walinuxagent docs [Daniel Watkins]</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - tox: bump pylint version to latest (2.3.1) [Daniel Watkins]</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - DataSource: move update_events from a class to an instance attribute</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> [Daniel Watkins] (LP: #1819913)</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - net/sysconfig: Handle default route setup for dhcp configured NICs</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> [Robert Schweikert] (LP: #1812117)</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - DataSourceEc2: update RELEASE_BLOCKER to be more accurate</p> -<p>16:38 <code>&lt;ubot5</code>&gt;` Launchpad bug 1819913 in cloud-init "cloud-init on xenial may generate network config on every boot" [Undecided,Fix released] <a href="https://launchpad.net/bugs/1819913">https://launchpad.net/bugs/1819913</a></p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> [Daniel Watkins]</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - cloud-init-per: POSIX sh does not support string subst, use sed</p> -<p>16:38 <code>&lt;ubot5</code>&gt;` Launchpad bug 1812117 in cloud-init "route files are not written on SUSE distros" [Undecided,Fix released] <a href="https://launchpad.net/bugs/1812117">https://launchpad.net/bugs/1812117</a></p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> (LP: #1819222)</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - Support locking user with usermod if passwd is not available.</p> -<p>16:38 <code>&lt;ubot5</code>&gt;` Launchpad bug 1819222 in cloud-init "cloud-init-per no longer works due to bashisms" [Undecided,Fix released] <a href="https://launchpad.net/bugs/1819222">https://launchpad.net/bugs/1819222</a></p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - Example for Microsoft Azure data disk added. [Anton Olifir]</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - clean: correctly determine the path for excluding seed directory</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> [Daniel Watkins] (LP: #1818571)</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - helpers/openstack: Treat unknown link types as physical</p> -<p>16:38 <code>&lt;ubot5</code>&gt;` Launchpad bug 1818571 in cloud-init "cloud-init clean removes seed directory even when --seed is not specified" [High,Fix released] <a href="https://launchpad.net/bugs/1818571">https://launchpad.net/bugs/1818571</a></p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> [Daniel Watkins] (LP: #1639263)</p> -<p>16:38 <code>&lt;ubot5</code>&gt;` Launchpad bug 1639263 in cloud-init " cloud-init Unknown network_data link type: macvtap" [Undecided,Fix released] <a href="https://launchpad.net/bugs/1639263">https://launchpad.net/bugs/1639263</a></p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - drop Python 2.6 support and our NIH version detection [Daniel Watkins]</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - tip-pylint: Fix assignment-from-return-none errors</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - net: append type:dhcp[46] only if dhcp[46] is True in v2 netconfig</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> [Kurt Stieger] (LP: #1818032)</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - cc_apt_pipelining: stop disabling pipelining by default</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> [Daniel Watkins] (LP: #1794982)</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - tests: fix some slow tests and some leaking state [Daniel Watkins]</p> -<p>16:38 <code>&lt;ubot5</code>&gt;` Launchpad bug 1818032 in cloud-init "sysconfig renders BOOTPROTO=dhcp even if dhcp=false in v2 network-config" [High,Fix released] <a href="https://launchpad.net/bugs/1818032">https://launchpad.net/bugs/1818032</a></p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> - util: don't determine string_types ourselves [Daniel Watkins]</p> -<p>16:38 <code>&lt;ubot5</code>&gt;` Launchpad bug 1794982 in cloud-init "drop /etc/apt/apt.conf.d/90cloud-init-pipelining in 16.04+" [Medium,Fix released] <a href="https://launchpad.net/bugs/1794982">https://launchpad.net/bugs/1794982</a></p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> Azure and SuSE and FreeBSD foks have been quite a bit of work and we have a number of other community contributors to thank this round</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: jasonzio (MSFT) and robjo (SuSE) thanks again for your efforts</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> Also, as you can see, Canonical added someone to our ranks for cloud-init development. Odd_Bloke is a permanent addition to our team and landing a lot of solid content for cloud-init.</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> welcome Dan!</p> -<p>16:43 <code>&lt;AnhVoMSFT&gt;</code> thanks rharper Odd_Bloke powersj blackboxsw for all the reviewing and advice</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> From upstream side of the house, we have cut our first official upstream release of cloud-init. Version 19.1 sports 5 months of development, 24 contributors from 20 top-level domains. Details of that release are sent to our mailinglist and posted to the luanchpad milestone</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> #link <a href="https://launchpad.net/cloud-init/+milestone/19.1">https://launchpad.net/cloud-init/+milestone/19.1</a></p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> :) ! it's nice how involved your teams have been thanks again.</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> So, for the upstream release of 19.1: Canonical has just started our SRU (Stable Release Update) process where we validate the upstream release before pushing it back into earlier Ubuntu series</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> We follow this upstream release process for Ubuntu</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> #link <a href="https://wiki.ubuntu.com/CloudinitUpdates">https://wiki.ubuntu.com/CloudinitUpdates</a></p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> I've queue to release branches for review as of Friday 05/10. I have queued Ubuntu Disco and published to disco-proposed pocket already.</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> So if someone deploys disco on your favorite cloud or hardware, you can add a disco-proposed apt source to /etc/apt/sources.list and you sound be able to install and or test 19.1</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> I made the 19.1.1 SRU cut which included the commitish baa478546d8cac98a706010699d64f8c2f70b5bf which was the tip containing " Azure: Return static fallback address as if failed to find endpoint" as the last commit</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> so jasonzio's latest azure branch made it</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> expectation is that I'll get most of verification done over this week and we can hopefully (pending no SRU regressions discovered) publish to Xenial, Bionic, Cosmic and Disco the beginning of next week (05/20/2019)</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> I just added the following card to track this work, it'll move to DONE when published</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> #link <a href="https://trello.com/c/oxv61bPl/1099-sru-191-xenial-bionic-cosmic-and-disco">https://trello.com/c/oxv61bPl/1099-sru-191-xenial-bionic-cosmic-and-disco</a></p> -<p>16:51 <code>&lt;powersj&gt;</code> AnhVoMSFT, thank you for all your contributions</p> -<p>16:52 <code>&lt;AnhVoMSFT&gt;</code> is there a package available publicly for 19.1 that we can download and apply it to existing images and run through our perf. regression test?</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> also today, we'll post 19.1 to our copr el-testing repo at</p> -<p>16:52 <code>&lt;blackboxsw&gt;</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:52 <code>&lt;blackboxsw&gt;</code> for centos.</p> -<p>16:53 <code>&lt;powersj&gt;</code> AnhVoMSFT, daily PPA: <a href="https://launchpad.net/~cloud-init-dev/+archive/ubuntu/daily">https://launchpad.net/~cloud-init-dev/+archive/ubuntu/daily</a></p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: we have daily repos that</p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> thx powersj</p> -<p>16:53 * powersj disappears</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT, so that is built from tip of master (which currently contains exactly the same commit set as will be published to each series)</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: once the following branches are "merged" for each series, xenial-proposed, bionic-proposed, cosmic-proposed will also contain the final bits for each series</p> -<p>16:54 <code>&lt;AnhVoMSFT&gt;</code> thanks powersj blackboxsw</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367301">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367301</a></p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367302">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367302</a></p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367297">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367297</a></p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> so when we land those, it should be a matter of an hour or so until <code>&lt;series&gt;</code>-proposed is accessible to test those final packages</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: in the SRU process, we still will have to verify and test those bits before release. There is a tracking bug for the overall process here</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1828637">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1828637</a></p> -<p>16:56 <code>&lt;ubot5</code>&gt;` Ubuntu bug 1828637 in cloud-init (Ubuntu) "sru cloud-init (18.5-45 to 19.1.1) Xenial, Bionic, Cosmic, Disco" [Undecided,In progress]</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> ^ this but will go to fix released when we pass verification and publish the SRU</p> -<p>16:57 <code>&lt;blackboxsw&gt;</code> which will be promotion from xenial-proposed to xenial-updates for public availability on all images</p> -<p>16:57 <code>&lt;blackboxsw&gt;</code> again the estimate on this is probably next week for getting through testing</p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> the rest of the cloud-init team is meeting this week for feature planning for the next cycle. But generally we will be tracking our ongoing work @ our public trello board</p> -<p>16:59 <code>&lt;blackboxsw&gt;</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>17:00 <code>&lt;blackboxsw&gt;</code> If there are there any features or significant gaps that people have interest in that we could try to put on our radar feel free to drop us a line here in channel or on the mailinglist @ cloud-init@lists.launchpad.net</p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> I think that about wraps up current in-flight work</p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> #topic Office hours (next ~30 mins)</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> This section is allocated generally for folks to chat about any burning questions that we have. Bring your topics, bugs, feature requests, merge proposals or questions and we'll try getting some eyes or discussion on the</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> *them.</p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> Generally we should have a couple cloud-init devs hanging out in channel during this time to help build momentum or unblock folks. Today may be a bit light in attendance due to a remote work trip a number of people are attending.</p> -<p>17:04 <code>&lt;AnhVoMSFT&gt;</code> if our next work requires importing another module (python-dbus), are there any guidelines wrt to using additional python modules not currently part of cloudinit package?</p> -<p>17:06 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: generally adding new dependencies is something we try to avoid if possible due to impacting the minimal cloud images with additional dependencies. From ubuntu's perspective we tend to try to look at an ubuntu minimal image to see if the dependency is already there (and that makes things simple for the addition).</p> -<p>17:06 <code>&lt;blackboxsw&gt;</code> If new dependency is also something that can be optional instead of strict it makes adding that dependency easier.</p> -<p>17:06 <code>&lt;blackboxsw&gt;</code> For example: python-jsonschema is an optional package dependency</p> -<p>17:07 <code>&lt;blackboxsw&gt;</code> we bookend the imports in cloud-init with a try/except ImportError: pass and make sure that cloud-init still behaves if it is not there.</p> -<p>17:07 <code>&lt;AnhVoMSFT&gt;</code> i will have to look into how to make it optional - certainly we can go that way if that makes thing easier</p> -<p>17:07 <code>&lt;AnhVoMSFT&gt;</code> what we are looking at is how to get the kernel init timestamp and systemd init timestamp - both of these are available as KernelTimestamp and UserSpaceTimestamp that are available as part of the systemd's system dbus</p> -<p>17:07 <code>&lt;blackboxsw&gt;</code> This type of approach has been helpful in supporting Centos 6 where jsonschema wasn't available in stock images</p> -<p>17:08 <code>&lt;AnhVoMSFT&gt;</code> normally you can get those info from "systemctl show", but the issue is systemctl internally use systemd's format_timestamp, which trims the precision down to "seconds" level. (format_timestamp_us would give us what we need)</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: interesting. since it seems like the dependency is one one or two values and not the full content of python-dbus library/modules I wonder if it might be better to see if those values are available in /proc or /sys somewhere as it might be fairly simple to instrument our own. (and avoid the time cost of importing larger python modules)</p> -<p>17:11 <code>&lt;AnhVoMSFT&gt;</code> I guess if we really want to avoid another module, we can use os.stat to key off ctime of /proc and /proc/1 - however, the ctimes of /proc and /proc/1 are a bit earlier than the actual KernelTimestamp and UserSpaceTimestamp. They do have the advantage of being more widely available. Systemd and dbus might not exist on all distros</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> ... at least something to peek at to see if it is low hanging fruit that is easy to handle</p> -<p>17:12 <code>&lt;AnhVoMSFT&gt;</code> Right, I would appreciate if someone with more knowledge on Linux systems can provide some advices here</p> -<p>17:12 <code>&lt;AnhVoMSFT&gt;</code> the dependency is really on those values, and the dbus library seems a bit overkill for it</p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> rharper: Odd_Bloke may have some thoughts on that too. but that conversation may have to wait a bit due to time difference.</p> -<p>17:14 <code>&lt;blackboxsw&gt;</code> AnhVoMSFT: again, what call/values would you like to make/get from python-dbus just for clarity</p> -<p>17:15 <code>&lt;AnhVoMSFT&gt;</code> bus=dbus.SystemBus() systemd1=bus.get_object('org.freedesktop.systemd1','/org/freedesktop/systemd1') manager=dbus.Interface(systemd1, 'org.freedesktop.systemd1.Manager') props_iface=dbus.Interface(manager,'org.freedesktop.DBus.Properties') props_iface.Get('org.freedesktop.systemd1.Manager','KernelTimestamp')</p> -<p>17:15 <code>&lt;AnhVoMSFT&gt;</code> oops - multiline didn't seem to go so well</p> -<p>17:15 <code>&lt;blackboxsw&gt;</code> it's all good thx</p> -<p>17:16 <code>&lt;blackboxsw&gt;</code> alternately, I support we could shell out via util.subp to make a cli call to handle that to avoid a python package dependency, but again it'd probably be better/faster to avoid that</p> -<p>17:17 <code>&lt;AnhVoMSFT&gt;</code> right, we're trying to avoid adding more util.subp call (in fact we have a workitem to reduce the numbers of the existing util.subp call the Azure DS makes)</p> -<p>17:18 <code>&lt;AnhVoMSFT&gt;</code> Like mentioned previously, we're looking at the /proc and /proc/1 ctime, they're cheap using the os.stat module and exist in all distros.</p> -<p>17:19 <code>&lt;blackboxsw&gt;</code> oops typo "alternatively , I support" /// I suppose</p> -<p>17:19 <code>&lt;blackboxsw&gt;</code> yeah that seems like the most non-contentious approach (processing /proc/1 ctime)</p> -<p>17:20 <code>&lt;blackboxsw&gt;</code> uncontentious rather</p> -<p>17:22 <code>&lt;AnhVoMSFT&gt;</code> another thing we're looking at is cloud-init cloudtests so that we can have some azure cloud test running as part of cloud-init check-in gate</p> -<p>17:22 <code>&lt;blackboxsw&gt;</code> excellent!</p> -<p>17:23 <code>&lt;AnhVoMSFT&gt;</code> if you guys have any pointers/tips on what it takes to enable cloud-tests please let us know</p> -<p>17:23 <code>&lt;AnhVoMSFT&gt;</code> one of our team members will be looking at it</p> -<p>17:24 <code>&lt;blackboxsw&gt;</code> any blockers that you are aware of to date? Generally the biggest lift is getting the platform support added to the cloud-tests</p> -<p>17:25 <code>&lt;blackboxsw&gt;</code> I know powersj added more CI docs related to this a few months ago at</p> -<p>17:25 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloudinit.readthedocs.io/en/latest/topics/tests.html#">https://cloudinit.readthedocs.io/en/latest/topics/tests.html#</a></p> -<p>17:25 <code>&lt;blackboxsw&gt;</code> I'll try to see if there was additional documentation tossed around</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> the benefit if Azure platform is added to cloud-init tip is that'd we would likely add some of that testing to our SRU verification process each release we are doing. I'm excited about that</p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> right now, it's manual for Azure testing... per something like this <a href="https://github.com/cloud-init/ubuntu-sru/blob/master/manual/azure-sru-18.5.21.txt">https://github.com/cloud-init/ubuntu-sru/blob/master/manual/azure-sru-18.5.21.txt</a></p> -<p>17:27 <code>&lt;AnhVoMSFT&gt;</code> I'm not aware of any blockers, we just barely started looking at it</p> -<p>17:27 <code>&lt;AnhVoMSFT&gt;</code> these links are very helpful, I'll pass them along</p> -<p>17:28 <code>&lt;blackboxsw&gt;</code> the above script is tedious to write up, and only is really testing upgrade path and any <em>new</em> azure-specific bugs/features that are fixed in the current SRU, since most of the other integration testing covers general case</p> -<p>17:28 <code>&lt;blackboxsw&gt;</code> thanks AnhVoMSFT that's good to hear</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> are there any other topics folks have for today's meeting? Otherwise we can adjourn until next meeting</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> next meeting will be May 27th, same time</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> and I'll post status notes for the meeting to our github pages</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io">https://cloud-init.github.io</a></p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> before I forget. let's get an action to followup on kernel/userspace timestamp discussion</p> -<p>17:31 <code>&lt;AnhVoMSFT&gt;</code> thanks blackboxsw</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> #action Odd_Bloke/rharper/AnhVoMSFT followup on recommended approach for getting kernel/userspace timestamp with or without python-dbus package dependency</p> -<p>17:32 * meetingology Odd_Bloke/rharper/AnhVoMSFT followup on recommended approach for getting kernel/userspace timestamp with or without python-dbus package dependency</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> thank you AnhVoMSFT</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> see folks next time, or anytime in channel</p> -<p>17:32 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2019-01-28T16:26:00+00:002019-01-28T16:26:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2019-01-28:/status-2019-01-28.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 28 Jan at 16:26 &mdash; 17:31 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-01-28-16.26.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-01-28-16.26.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:27.</p> -<ul> -<li><strong>ACTION</strong>: carry over blackboxsw close and land Openstack …</li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 28 Jan at 16:26 &mdash; 17:31 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-01-28-16.26.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-01-28-16.26.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:27.</p> -<ul> -<li><strong>ACTION</strong>: carry over blackboxsw close and land Openstack metadata handling bug <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</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:47.</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>Office Hours (next ~30 minutes)</h3> -<p>The discussion about "Office Hours (next ~30 minutes)" started at 16:51.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/357710">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/357710</a> merged</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>Action items, by person</h2> -<ul> -<li>blackboxsw</li> -<li>carry over blackboxsw close and land Openstack metadata handling bug <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</a></li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (60)</li> -<li>robjo (6)</li> -<li>ubot5 (6)</li> -<li>meetingology (4)</li> -</ul> -<h2>Full Log</h2> -<p>16:26 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:26 <code>&lt;meetingology&gt;</code> Meeting started Mon Jan 28 16:26:28 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:26 <code>&lt;meetingology&gt;</code> </p> -<p>16:26 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> hi cloud-init folks, it's that happy time again to chat about cloud-init upstream.</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> Generally the topics we cover in this status meeting are: Previous Actions, Recent Changes, In-progress Development, and Office hours</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> previously we had an action to review <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098.">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098.</a> I think rharper and robjo have a couple of back and forths on this branch. looks like we'll be able to land this</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> and oh noes, we need to followup and resolve the following MD bug on OpenStack <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</a></p> -<p>16:32 <code>&lt;ubot5&gt;</code> Ubuntu bug 1801364 in cloud-init "persisting OpenStack metadata fails" [Undecided,Confirmed]</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> #action carry over blackboxsw close and land Openstack metadata handling bug <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</a></p> -<p>16:32 * meetingology carry over blackboxsw close and land Openstack metadata handling bug <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</a></p> -<p>16:32 <code>&lt;robjo&gt;</code> Well that one was just about an additional empty line which I removed in October</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> ok I'll spend the 2nd half of this meeting going through this again and landing it if no other concerns. #toostale seeing <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098</a></p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> it doesn't look on review that there is anything concerning there.</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> ok I think that we it for actions last time.</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:36 <code>&lt;robjo&gt;</code> blackboxsw: There's also <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/357710">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/357710</a></p> -<p>16:36 <code>&lt;robjo&gt;</code> which appears to be complaining about he commit message</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> robjo: oops autolander rejection, will fix the LP commit message now and make approved (for merging)</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> Server Team CI bot (server-team-bot) wrote on 2019-01-07: #</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> Commit message lints:</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> - Expected empty line on line 2 of the commit message</p> -<p>16:37 <code>&lt;robjo&gt;</code> Can there not be a template in LP for the commit message?</p> -<p>16:38 <code>&lt;robjo&gt;</code> I can never remember the formatting intricacies and thus depend on one of you guys to set this</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> robjo: does the 'commit message' on the merge proposal look good to you now <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/357710">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/357710</a></p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> at the top</p> -<p>16:39 <code>&lt;robjo&gt;</code> LGTM, thanks</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> I've clicked approve and it should autoland within ~15 mins</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> great</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> so recent commits to upstream cloud-init</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> - flake8: use ==/!= to compare str, bytes, and int literals</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> [Paride Legovini]</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> - opennebula: exclude EPOCHREALTIME as known bash env variable with a</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> delta [Chad Smith] (<a href="[https://bugs.launchpad.net/bugs/1813383](https://bugs.launchpad.net/bugs/1813383)">LP: #1813383</a>)</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> - tox: fix disco httpretty dependencies for py37</p> -<p>16:41 <code>&lt;ubot5&gt;</code> Ubuntu bug 1813383 in cloud-init "opennebula: fail to sbuild, bash environment var failure EPOCHREALTIME" [Undecided,Fix committed]</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> ha, ircflood boot</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> not sure how far I got in that list of commits</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> - lxd: install zfs-linux instead of zfs meta package</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> 09:41 [Johnson Shi] (<a href="[https://bugs.launchpad.net/bugs/1799779](https://bugs.launchpad.net/bugs/1799779)">LP: #1799779</a>)</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> 09:41 - net/sysconfig: do not write a resolv.conf file with only the header.</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> 09:41 [Robert Schweikert]</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> 09:41 - net: Make sysconfig renderer compatible with Network Manager.</p> -<p>16:42 <code>&lt;ubot5&gt;</code> Ubuntu bug 1799779 in cloud-init (Ubuntu Disco) "LXD module installs the wrong ZFS package if it's missing" [Medium,Confirmed]</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> 09:41 [Eduardo Otubo]</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> - cc_set_passwords: Fix regex when parsing hashed passwords</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> 09:41 [Marlin Cremers] (<a href="[https://bugs.launchpad.net/bugs/1811446](https://bugs.launchpad.net/bugs/1811446)">LP: #1811446</a>)</p> -<p>16:42 <code>&lt;ubot5&gt;</code> Ubuntu bug 1811446 in cloud-init (Ubuntu) "chpasswd: is mangling certain password hashes" [Undecided,In progress]</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> 09:41 - net: Wait for dhclient to daemonize before reading lease file</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> 09:41 [Jason Zions] (<a href="[https://bugs.launchpad.net/bugs/1794399](https://bugs.launchpad.net/bugs/1794399)">LP: #1794399</a>)</p> -<p>16:42 <code>&lt;ubot5&gt;</code> Ubuntu bug 1794399 in cloud-init "cloud-init dhcp_discovery() crashes on preprovisioned RHEL 7.6 VM in Azure" [Undecided,Fix committed]</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> 09:41 - [Azure] Increase retries when talking to Wireserver during metadata walk</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> 09:41 [Jason Zions]</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> 09:41 - Add documentation on adding a datasource.</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> Thanks folks for all the contributions to cloud-init over the last couple of weeks.</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> Additionally, we just published tip of cloud-init to Ubuntu disco (19.04) development release</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> and we have queued that release as well (cloud-init 18.5.17) for SRU (stable release update) into Xenial, Bionic and Cosmic as of Saturday.</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> the SRU process bug can be watched to see when 18.5.17 publishes to 16.04 18.04 and 18.10. (xenial, bionic, cosmic) <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1813346">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1813346</a></p> -<p>16:44 <code>&lt;ubot5&gt;</code> Ubuntu bug 1813346 in cloud-init (Ubuntu) "sru cloud-init (18.4.0 update to 18.5-17-gd1a2fe73) Xenial, Bionic, Cosmic" [Undecided,New]</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> Also we welcome our new QA team member paride to Canonical, he's been working on re-enabling our copr build repos and generally improving the quality of our continuous integration for cloud-init (and other Canonical projects)</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> #topic In-Progress Development</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> we tracking our ongoing cloud-init upstream work (and backlog) on our Trello board</p> -<p>16:47 <code>&lt;blackboxsw&gt;</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:49 <code>&lt;blackboxsw&gt;</code> the next couple of weeks will likely result in Ubuntu SRU verificantion for that release into xenial, bionic and cosmic. robjo's been working on a few OpenSUSE/sysconfig network handling branches that will likely land. and we'll have a couple of EC2 branches that need to address EC2-Classic network re-configuration across reboots</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> and, as mentioned our upstream copr repo builds will likely be fixed for centos/fedora consumers</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 minutes)</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> So, upsteram devs will have eyes on this channel for any further discussion, bugs or questions about cloud-init. Please use this venue as you see fit to raise awareness of stale branches, bugs etc so we can queue them up for review.</p> -<p>16:53 * blackboxsw is going to look over <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098</a> to see if we can close out on that today</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/357710">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/357710</a> merged</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> and just approved <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098</a></p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> thanks robjo</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> I think that about wraps it up for today. thanks again for checking in folks.</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> As always minutes will be posted to cloud-init's github page @</p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io">https://cloud-init.github.io</a></p> -<p>17:31 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2019-01-07T16:36:00+00:002019-01-07T16:36:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2019-01-07:/status-2019-01-07.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 07 Jan at 16:36 &mdash; 18:02 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-01-07-16.36.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-01-07-16.36.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:38.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/360905">https://code …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 07 Jan at 16:36 &mdash; 18:02 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-01-07-16.36.log.html">http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-01-07-16.36.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:38.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/360905">https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/360905</a> </li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:42.</p> -<h3>In-Progress Development</h3> -<p>The discussion about "In-Progress Development" started at 16:46.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098</a> is pending since October :( :(</li> -<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>ACTION</strong>: Review robjo's branch today/tomorrow</li> -<li><strong>ACTION</strong>: Review robjo's branch today/tomorrow <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098</a></li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098</a> </li> -<li><strong>ACTION</strong>: review robjo's New bugs and get feedback <a href="https://bit.ly/2C4gEHJ">https://bit.ly/2C4gEHJ</a></li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</a> </li> -<li><strong>LINK</strong>: <a href="https://trello.com/c/bEGsPvTm/1028-updated-cloud-init-ci-review-bot-to-place-a-branch-back-into-needs-review-after-it-receives-a-commit">https://trello.com/c/bEGsPvTm/1028-updated-cloud-init-ci-review-bot-to-place-a-branch-back-into-needs-review-after-it-receives-a-commit</a> </li> -<li><strong>ACTION</strong>: blackboxsw resolve and land fix for <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</a> this week</li> -</ul> -<h3>Office Hours (next ~30 minutes)</h3> -<p>The discussion about "Office Hours (next ~30 minutes)" started at 17:29.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://build.opensuse.org/package/show/Cloud:Tools:Next/cloud-init">https://build.opensuse.org/package/show/Cloud:Tools:Next/cloud-init</a> </li> -</ul> -<h2>Vote results</h2> -<h2>Action items, by person</h2> -<ul> -<li>blackboxsw</li> -<li>blackboxsw resolve and land fix for <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</a> this week</li> -<li>robjo</li> -<li>Review robjo's branch today/tomorrow</li> -<li>Review robjo's branch today/tomorrow <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098</a></li> -<li>review robjo's New bugs and get feedback <a href="https://bit.ly/2C4gEHJ">https://bit.ly/2C4gEHJ</a></li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (62)</li> -<li>robjo (16)</li> -<li>meetingology (7)</li> -<li>ubot5 (6)</li> -<li>rharper (1)</li> -</ul> -<h2>Full Log</h2> -<p>16:36 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:36 <code>&lt;meetingology&gt;</code> Meeting started Mon Jan 7 16:36:15 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:36 <code>&lt;meetingology&gt;</code> </p> -<p>16:36 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> Happy New Year! We shifted the cloud-init status meeting time ... and then I subsequent forgot about it.</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> Hope the break went well for folks. We'll be hosting this meeting bi-weekly to keep folks updated on cloud-init developments</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> Generally the topics we cover in this status meeting are: Previous Actions, Recent Changes, In-progress Development, and Office hours</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> looking over last meeting minutes I see only one action</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> ^ meeting minutes</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/360905">https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/360905</a></p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> ^ this merge proposal from Jason Zions looks like it got updated and resubmitted a few days ago addressing our review comments. Let's get another review on this this week and see where it stands</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> - Upstream release of cloud-init 18.5 and publishing 18.5 to Ubuntu 19.04 (Disco)</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> - ds-identify: fix wrong variable name in ovf_vmware_transport_guestinfo.</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> - Scaleway: Support ssh keys provided inside an instance tag. [PORTE Loïc]</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> - OVF: simplify expected return values of transport functions.</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> - Vmware: Add support for the com.vmware.guestInfo OVF transport.</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> (<a href="[https://bugs.launchpad.net/bugs/1807466](https://bugs.launchpad.net/bugs/1807466)">LP: #1807466</a>)</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> - HACKING.rst: change contact info to Josh Powers</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> - Update to pylint 2.2.2.</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> - Release 18.5 [Ryan Harper] (<a href="[https://bugs.launchpad.net/bugs/1808380](https://bugs.launchpad.net/bugs/1808380)">LP: #1808380</a>)</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> - tests: add Disco release [Joshua Powers]</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> - net: render 'metric' values in per-subnet routes</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> [Ryan Harper] (<a href="[https://bugs.launchpad.net/bugs/1805871](https://bugs.launchpad.net/bugs/1805871)">LP: #1805871</a>)</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> - write_files: add support for appending to files. [James Baxter]</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> - config: On ubuntu select cloud archive mirrors for armel, armhf, arm64.</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> (<a href="[https://bugs.launchpad.net/bugs/1805854](https://bugs.launchpad.net/bugs/1805854)">LP: #1805854</a>)</p> -<p>16:45 <code>&lt;ubot5&gt;</code> Ubuntu bug 1807466 in cloud-init "add support for ovf transport com.vmware.guestInfo" [Medium,Fix committed]</p> -<p>16:45 <code>&lt;ubot5&gt;</code> Ubuntu bug 1808380 in cloud-init "Release 18.5" [Undecided,Fix released]</p> -<p>16:45 <code>&lt;ubot5&gt;</code> Ubuntu bug 1805871 in cloud-init (Ubuntu) "net renderers miss metric value in per-subnet routes" [Undecided,Fix released]</p> -<p>16:45 <code>&lt;ubot5&gt;</code> Ubuntu bug 1805854 in cloud-init "[feature-request] Add non-x86 Ubuntu EC2 mirrors in to default cloud-init configuration" [Medium,Fix released]</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> The above are commits landed in cloud-init since the last status meeting.</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> #topic In-Progress Development</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> As always we try tracking our ongoing cloud-init upstream work (and backlog) on our Trello board</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> #lin <a href="https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin">https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin</a></p> -<p>16:47 <code>&lt;robjo&gt;</code> <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098</a> is pending since October :( :(</p> -<p>16:47 <code>&lt;blackboxsw&gt;</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:47 <code>&lt;blackboxsw&gt;</code> #action Review robjo's branch today/tomorrow</p> -<p>16:47 * meetingology Review robjo's branch today/tomorrow</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> #action Review robjo's branch today/tomorrow <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098</a></p> -<p>16:47 * meetingology Review robjo's branch today/tomorrow <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098</a></p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098</a></p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> ok robjo, we'll have eyes on that today and get you something</p> -<p>16:48 <code>&lt;robjo&gt;</code> Also I filed a number of bugs w.r.t the network rendering some with proposals, for other's I simply have no idea about the best approach, none of these have seen any action</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> thanks for that</p> -<p>16:49 <code>&lt;robjo&gt;</code> then there is the Python 2 utf-8 issue w.r.t. metadata persistence on OpenStack</p> -<p>16:49 <code>&lt;robjo&gt;</code> smoser had supplied a test case, also not action on that issue since whenever .... :(</p> -<p>16:50 <code>&lt;robjo&gt;</code> on that topic the question is still open why that particular data is persisted in teh first place since every access to the APi on OpenStack yields a different result</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> #action review robjo's New bugs and get feedback <a href="https://bit.ly/2C4gEHJ">https://bit.ly/2C4gEHJ</a></p> -<p>16:51 * meetingology review robjo's New bugs and get feedback <a href="https://bit.ly/2C4gEHJ">https://bit.ly/2C4gEHJ</a></p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> robjo: I think we have to sort persistence story for metadata sub-components still. The only reason anything is persisted is for speed of course. OpenStack DS is notably very slow on every call the the md service.</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> robjo: some of that persistence/refresh should/will be addressed in rharper's openstack hotplug branch which would force cloud-init to refresh metadata when hotplug events are seen</p> -<p>16:57 <code>&lt;robjo&gt;</code> Well I have to admit that I do not know how OpenStack and or guest would use the value returned for "random_seed". What I was able to test is that the value is different when the API is aclled</p> -<p>16:59 <code>&lt;robjo&gt;</code> so that could mean that OpenStack keeps the "previously" returned value of "random_seed" until the API is called again and then uses the previous value for whatever hashing is being done to come up with authentication of the guest</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> robjo: is this the bug? <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</a></p> -<p>16:59 <code>&lt;ubot5&gt;</code> Ubuntu bug 1801364 in cloud-init "persisting OpenStack metadata fails" [Undecided,Confirmed]</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</a></p> -<p>17:00 <code>&lt;robjo&gt;</code> but that would imply that any calls to the OpenStack API from the quest must know that random_seed and I doubt that they are using the cache we build with cloud-init</p> -<p>17:00 <code>&lt;robjo&gt;</code> yes, that's the bug</p> -<p>17:03 <code>&lt;rharper&gt;</code> robjo: your <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098</a> was left in Needs Fixing and got tagged WIP; after you updated, it needed to move to Needs Review</p> -<p>17:04 <code>&lt;robjo&gt;</code> Well I am pretty sure I tried to set it back to get another review and from the interface it looked to me that happened.... :(</p> -<p>17:05 <code>&lt;robjo&gt;</code> If I look at the UI it tells me the review was requested from "Scott Moser [2]" on 2018-10-09 and the status is "Pending"</p> -<p>17:15 <code>&lt;blackboxsw&gt;</code> robjo: we're talking side-channel as we were in a meeting anyway. Just added a work item to help us avoid this situation</p> -<p>17:15 <code>&lt;blackboxsw&gt;</code> <a href="https://trello.com/c/bEGsPvTm/1028-updated-cloud-init-ci-review-bot-to-place-a-branch-back-into-needs-review-after-it-receives-a-commit">https://trello.com/c/bEGsPvTm/1028-updated-cloud-init-ci-review-bot-to-place-a-branch-back-into-needs-review-after-it-receives-a-commit</a></p> -<p>17:15 <code>&lt;blackboxsw&gt;</code> this will make reviews which you add commits to pop up on our radar anytime a new commit was added</p> -<p>17:16 <code>&lt;robjo&gt;</code> thanks</p> -<p>17:16 <code>&lt;blackboxsw&gt;</code> then we know what needs attention (as others have hit this issue too0</p> -<p>17:18 <code>&lt;blackboxsw&gt;</code> robjo: we also are talking about we can maybe blacklisting certain metadata elements as not-cacheable. We'll have to add 'cloud-init query' tooling to understand this at some point though.</p> -<p>17:18 <code>&lt;blackboxsw&gt;</code> #action blackboxsw resolve and land fix for <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</a> this week</p> -<p>17:18 * meetingology blackboxsw resolve and land fix for <a href="https://bugs.launchpad.net/cloud-init/+bug/1801364">https://bugs.launchpad.net/cloud-init/+bug/1801364</a> this week</p> -<p>17:18 <code>&lt;ubot5&gt;</code> Ubuntu bug 1801364 in cloud-init "persisting OpenStack metadata fails" [Undecided,Confirmed]</p> -<p>17:19 <code>&lt;blackboxsw&gt;</code> though the fix for serialization won't include this blacklisting/cache solution I don't think</p> -<p>17:20 <code>&lt;blackboxsw&gt;</code> Ok I grabbed <a href="https://trello.com/c/7ouGpa0A/1029-openstack-serialization-errors-py27">https://trello.com/c/7ouGpa0A/1029-openstack-serialization-errors-py27</a></p> -<p>17:23 <code>&lt;robjo&gt;</code> There is a patch for a very simplistic approach attached to the bug, that's what I am currently carrying in the SUSE package</p> -<p>17:28 <code>&lt;blackboxsw&gt;</code> +1</p> -<p>17:28 <code>&lt;blackboxsw&gt;</code> ok, so I think that wraps current topic.</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 minutes)</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> upstream devs will have eyes on this channel for any concerns, questions or discussions folks want to have about cloud-init.</p> -<p>17:29 <code>&lt;blackboxsw&gt;</code> We've also started going through some of the open reviews</p> -<p>17:30 <code>&lt;blackboxsw&gt;</code> raharper is on <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/360905">https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/360905</a> currently. I'll start looking at this <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/360905">https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/360905</a></p> -<p>17:34 <code>&lt;blackboxsw&gt;</code> robjo: can you re-share that opensuse download link for latest cloud-init images generated (I think you had shared once in the past your server team's public/latest/testing downloads of cloud-init)</p> -<p>17:34 <code>&lt;blackboxsw&gt;</code> just for reference while you are here :)</p> -<p>17:34 <code>&lt;blackboxsw&gt;</code> s/images/packages/</p> -<p>17:37 <code>&lt;robjo&gt;</code> <a href="https://build.opensuse.org/package/show/Cloud:Tools:Next/cloud-init">https://build.opensuse.org/package/show/Cloud:Tools:Next/cloud-init</a></p> -<p>17:37 <code>&lt;blackboxsw&gt;</code> thank you sir</p> -<p>17:38 <code>&lt;robjo&gt;</code> currently the same as the released <a href="https://build.opensuse.org/package/show/Cloud:Tools:Next/cloud-init">https://build.opensuse.org/package/show/Cloud:Tools:Next/cloud-init</a></p> -<p>17:38 <code>&lt;robjo&gt;</code> but planningt to move :Next to 18.5 this week</p> -<p>17:39 <code>&lt;blackboxsw&gt;</code> excellent thanks robjo</p> -<p>18:02 <code>&lt;blackboxsw&gt;</code> ok think that wraps up the meeting for today</p> -<p>18:02 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-12-10T16:11:00+00:002018-12-10T16:11:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-12-10:/status-2018-12-10.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 10 Dec at 16:11 &mdash; 16:58 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-12-10-16.11.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-12-10-16.11.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:13.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427">https://code.launchpad.net/~jasonzio/cloud-init/+git …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 10 Dec at 16:11 &mdash; 16:58 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-12-10-16.11.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-12-10-16.11.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:13.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427">https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427</a> </li> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2018-11-26.html#status-2018-11-26">https://cloud-init.github.io/status-2018-11-26.html#status-2018-11-26</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392">https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392</a> </li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:19.</p> -<h3>In-Progress Development</h3> -<p>The discussion about "In-Progress Development" started at 16:24.</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="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/359876">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/359876</a> </li> -</ul> -<h3>Cloud-init upstream Release 18.5</h3> -<p>The discussion about "Cloud-init upstream Release 18.5" started at 16:27.</p> -<h3>Office Hours (next ~30 minutes)</h3> -<p>The discussion about "Office Hours (next ~30 minutes)" started at 16:31.</p> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (57)</li> -<li>meetingology (3)</li> -<li>ubot5 (2)</li> -<li>powersj (1)</li> -</ul> -<h2>Full Log</h2> -<p>16:11 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:11 <code>&lt;meetingology&gt;</code> Meeting started Mon Dec 10 16:11:11 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:11 <code>&lt;meetingology&gt;</code> </p> -<p>16:11 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> Welcome to our biweekly status meeting. The intent is to provide a venue where we can advertise current cloud-init development efforts and a place and time where interested community members can ask questions or raise issues to the upstream development team.</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> Generally we go through the following topics: Previous Actions, Recent Changes, In-progress Development, and Office hours</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> Today we'll add a "Release" topic</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> Let's kick it off</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> One action we need to carry over from last meeting</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427">https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427</a></p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> our followup review is required on this branch to avoid a race condition for DHCP discovery on RHEL</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> I don't think there were any other actions raised last meeting</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> BTW our meeting minutes from last status meeting are here</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2018-11-26.html#status-2018-11-26">https://cloud-init.github.io/status-2018-11-26.html#status-2018-11-26</a></p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> we did land and publish cloud-init to Disco containing the Azure netlink listener support branch which was raised as an action last meeting. per the following</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392">https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392</a></p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> The following branches landed in cloud-init tip- dhclient-hook: cleanups, tests and fix a bug on 'down' event.</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - NoCloud: Allow top level 'network' key in network-config. (<a href="[https://bugs.launchpad.net/bugs/1798117](https://bugs.launchpad.net/bugs/1798117)">LP: #1798117</a>)</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - ovf: Fix ovf network config generation gateway/routes</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> [Ryan Harper] (<a href="[https://bugs.launchpad.net/bugs/1806103](https://bugs.launchpad.net/bugs/1806103)">LP: #1806103</a>)</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - Published Cloud-init v.18.3-41 to Ubuntu Disco</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - azure: detect vnet migration via netlink media change event</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> [Tamilmani Manoharan]</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - Azure: fix copy/paste error in error handling when reading azure ovf.</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> [Adam DePue]</p> -<p>16:20 <code>&lt;ubot5&gt;</code> Ubuntu bug 1798117 in cloud-init (Ubuntu) "juju sends "network" top level key to user.network-config in lxd containers" [Medium,Confirmed]</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - tests: fix incorrect order of mocks in test_handle_zfs_root.</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - doc: Change dns_nameserver property to dns_nameservers. [Tomer Cohen]</p> -<p>16:20 <code>&lt;ubot5&gt;</code> Ubuntu bug 1806103 in cloud-init (Ubuntu) "ovf: network config store routes under nic subnets 'routes' key" [Undecided,New]</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - OVF: identify label iso9660 filesystems with label 'OVF ENV'.</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - net: Ephemeral*Network: add connectivity check via URL</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> [Igor Galić]</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> we also published all latest changes to Ubuntu Disco as 18.4-31-gbf791715-0ubuntu1</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> I missed a couple of other commits to cloud-init</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> - config: On ubuntu select cloud archive mirrors for armel, armhf, arm64.</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> - write_files: add support for appending to files. [James Baxter]</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> Thanks James, Tamilmani, Adam and Tomer for the contributions here and making cloud-init bette</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> r</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> #topic In-Progress Development</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> We track our current work in the TODO, Doing and Done lanes on trello</p> -<p>16:24 <code>&lt;blackboxsw&gt;</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:25 <code>&lt;blackboxsw&gt;</code> mostly we are trying to wrap up low-hanging-fruit and bug fixes as we have an upstream release scheduled this week for cloud-init 18.5</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> There is also some significant work ongoing my smoser for vmware and ovf deployment support</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> <em>by smoser</em></p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> and rharper has a branch up to fix network metric config handling for subnet routes</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/359876">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/359876</a></p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> think that about wraps in-progress work.</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> #topic Cloud-init upstream Release 18.5</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> So, we have our 18.5 upstream release scheduled for this Wednesday 12/13/2018</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> If there are any feature requests or critical bug fixes that folks are interested, please bring them up either in channel here, or on the mailing list, cloud-init@lists.launchpad.net</p> -<p>16:29 <code>&lt;powersj&gt;</code> blackboxsw, ^ is that worth sending to mailing list?</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> powersj: yes. I'll send that email out in the next half hour</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> agreed</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> think that about wraps this status update for this meeting</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 minutes)</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> upstream devs will have eyes on this channel for any concerns, questions or discussions folks want to have about cloud-init.</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> Given the upcoming holidays, I think we will take a break from this meeting as next scheduled time would be the day before Christmas.</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> Next status meeting will be Monday January 7th 16:15 UTC</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> email sent to cloud-init about upcoming release</p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> Happy Holiday folks. Looks like we're already starting to use up vacation time. Thanks for tuning in. See you next year!</p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-11-26T16:18:00+00:002018-11-26T16:18:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-11-26:/status-2018-11-26.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 26 Nov at 16:18 &mdash; 17:17 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-11-26-16.18.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-11-26-16.18.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io">https://cloud-init.github.io</a> - <strong>LINK</strong>: <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427">https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427</a> - <strong>LINK</strong>: <a href="https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/358881">https://code …</a></p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 26 Nov at 16:18 &mdash; 17:17 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-11-26-16.18.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-11-26-16.18.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io">https://cloud-init.github.io</a> - <strong>LINK</strong>: <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427">https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427</a> - <strong>LINK</strong>: <a href="https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/358881">https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/358881</a> - <strong>LINK</strong>: c<a href="https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392">https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392</a> - <strong>LINK</strong>: <a href="https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392">https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392</a> </p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:29.</p> -<h3>In-Progress Development</h3> -<p>The discussion about "In-Progress Development" started at 16:33.</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>Office Hours (next ~30 minutes)</h3> -<p>The discussion about "Office Hours (next ~30 minutes)" started at 16:45.</p> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (64)</li> -<li>meena (10)</li> -<li>rharper (4)</li> -<li>meetingology (3)</li> -<li>ubot5 (2)</li> -</ul> -<h2>Full Log</h2> -<p>16:18 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:18 <code>&lt;meetingology&gt;</code> Meeting started Mon Nov 26 16:18:39 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:18 <code>&lt;meetingology&gt;</code> </p> -<p>16:18 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> Morning/Afternoon folks. welcome to another cloud-init status meeting</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> ... our open forum to advertise current cloud-init developments, giving an opportunity to discuss bugs or features in cloud-init and provide a touch point for the community</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> Generally we go through the following topics: Previous Actions, Recent Changes, In-progress Development, and Office hours</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> our last meeting's minutes are located here</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io">https://cloud-init.github.io</a></p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> only thing we carried into that meeting is a an review</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427">https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427</a></p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> rharper: had closed out feedback on the review. with a needs fixing. I did see some followup commits there from the author Jason Zion.</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> I think we need to take a look at this again and see if our comments were addressed, I'm marking it "Needs review"</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> I see no other actions carried over... but there was talk last week about a couple of branches so let's add these</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/358881">https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/358881</a></p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> ^ disco support</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> #link c<a href="https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392">https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392</a></p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392">https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392</a></p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> ^ Azure netlink listener</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> ok next topic</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> - azure: _poll_imds only retry on 404. Fail on Timeout</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> (<a href="[https://bugs.launchpad.net/bugs/1803598](https://bugs.launchpad.net/bugs/1803598)">LP: #1803598</a>)</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> - resizefs: Prefix discovered devpath with '/dev/' when path does not</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> exist [Igor Galić]</p> -<p>16:30 <code>&lt;ubot5&gt;</code> Ubuntu bug 1803598 in cloud-init "Do not retry polling IMDS for reprovisiondata during timeout" [Undecided,Fix committed]</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> t'was a slow week with all that Thanksgiving holiday stuff for US-based employees</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> welcome back from the Holidays boys and girls</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> also we were able to publish tip of cloud-init to Ubuntu Disco series</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> cloud-init 18.4-24-g8f812a15-0ubuntu1 has latest and greatest as seen on tip of master</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> #topic In-Progress Development</p> -<p>16:33 <code>&lt;blackboxsw&gt;</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:34 <code>&lt;blackboxsw&gt;</code> Our trello board tracks our queued and current work for cloud-init, feel free to watch that board for updates on significant cloud-init features/bug-fixes</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> what generally isn't tracked there is reviews on community authored branches</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> per community driven content, we have a number of branches from meena for better FreeBSD support in flight. Great work! and some Azure platform development to react to netlink events during the preprovisioning state.</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> thanks tamilmani_ on the azure work.</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> As a heads up to folks, we are trying to cut an upstream release of cloud-init 18.5 on 12/15/2018. So if there are branches you want to see landed or bugs you need fixed please holler here in this channel or on the mailing list to:cloud-init.lists.launchpad.net</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> We'll send an email to the mailing list requesting for input on the release as well</p> -<p>16:39 <code>&lt;meena&gt;</code> &gt;<code>blackboxsw what generally isn't tracked there is reviews on community authored branches</code>&lt;== i did check there first time around, but found nothing that was topical for me</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> Correct meena . I used to capture outstanding community reviews that needed review follow up, but that ended up being out of date all the time. It was easier for us to just use launchpad active review queue instead</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> Now we've tried to adopt the setting of a branch status to 'work in progress' if we are expecting feedback/fixes from the author. And have the author set it back to 'needs review' when it is ready for another round of upstream reviews</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> having trello cards was basically just duplicating what launchpad reviews were designed for, we just need to be more vigilant about grooming the review queue and getting folks the feedback they need</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> might as well switch over to office hours for open discussion etc.</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 minutes)</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> Cloud-init upstream folks will have eyes on this channel for any discussions. requests, bugs or features folks want to discuss.</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> we'll also spend some time actively grooming the branch review queue to see if we can clear out some review debyt</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> we'll also spend some time actively grooming the branch review queue to see if we can clear out some review debt</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> I think smoser mentioned at our team standup this morning he was taking one more review on <a href="https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392">https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392</a></p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> rharper: if you are done with your review on that tamilmani_ branch can you add a comment that doesn't leave it in "Needs fixing" review state from yoiu?</p> -<p>16:48 <code>&lt;rharper&gt;</code> blackboxsw: yes, I'm adding a commit message now, and I'll leave a comment marking approve;</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> excellent.</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> I'm going to give a review to <a href="https://code.launchpad.net/~i.galic/cloud-init/+git/cloud-init/+merge/358876">https://code.launchpad.net/~i.galic/cloud-init/+git/cloud-init/+merge/358876</a> now</p> -<p>16:48 * blackboxsw claims a review slot</p> -<p>16:49 <code>&lt;rharper&gt;</code> blackboxsw: did we have a LP for thisone ?</p> -<p>16:49 <code>&lt;rharper&gt;</code> the netlink ?</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> ohh, no we did not I don't think.</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> I'll check</p> -<p>16:56 <code>&lt;meena&gt;</code> blackboxsw: i think my (our) patch is ready to be merged</p> -<p>16:57 <code>&lt;blackboxsw&gt;</code> rharper: yeah didn't find any bug filed related to Azure and dhcp leak or netlink response etc.</p> -<p>16:57 <code>&lt;meena&gt;</code> (the feature / fix of adding connectivity check to ephemeral network stuff)</p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> meena: I think so too. Was just dusting off my memory on that one. I'm going to do a quick test run of setup/teardown and I think that's good. +1</p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> thanks again</p> -<p>16:58 <code>&lt;meena&gt;</code> once that's merged, I'll have a much easier time with splitting out the freebsd network</p> -<p>16:59 <code>&lt;meena&gt;</code> blackboxsw: thank you for showing me how to do the tests properly</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> most welcome.</p> -<p>17:00 <code>&lt;rharper&gt;</code> blackboxsw: thanks, me neither; I just didn't want to miss a LP: in the commit message if we had one</p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> after this branch lands and tamilmani_'s I probably will go through the motions of us publishing to Ubuntu Disco again, because I want to get a round or two of integration tests on both Azure and AWS with both the ephemeral* changes and the netlink stuff on pristine cloud-images before next week's release</p> -<p>17:06 <code>&lt;blackboxsw&gt;</code> meena: you didn't file a bug related to the ephermeraldhcp network connectivity did you? (I'm just double checking as I don't see one)</p> -<p>17:07 <code>&lt;blackboxsw&gt;</code> meena: not needed, just didn't want to miss it if it was there (as we'd want to link it in the commit message)</p> -<p>17:08 <code>&lt;meena&gt;</code> blackboxsw: nah, we just "filed" a mailing list thread</p> -<p>17:08 <code>&lt;blackboxsw&gt;</code> all good thanks</p> -<p>17:09 <code>&lt;blackboxsw&gt;</code> ok I had filed <a href="https://bugs.launchpad.net/cloud-init/+bug/1802598">https://bugs.launchpad.net/cloud-init/+bug/1802598</a> but we won't tie that to this branch</p> -<p>17:09 <code>&lt;ubot5&gt;</code> Ubuntu bug 1802598 in cloud-init "EphemeralIPv4Network: when device has requested existing network config, but link is down, network setup does not bring link up" [Undecided,Triaged]</p> -<p>17:09 <code>&lt;blackboxsw&gt;</code> it's a bit more about idempotent behavior</p> -<p>17:13 <code>&lt;meena&gt;</code> <em>nod </em>nod</p> -<p>17:13 <code>&lt;meena&gt;</code> i didn't think i had fixed it, so i didn't connect them.</p> -<p>17:16 <code>&lt;blackboxsw&gt;</code> +1 on your branch meena, it should land within the hour. Just tested it out one more time</p> -<p>17:16 <code>&lt;meena&gt;</code> cool</p> -<p>17:16 <code>&lt;blackboxsw&gt;</code> ok I think that about wraps today's meeting timewise. Thanks again for the chat meena.</p> -<p>17:16 <code>&lt;meena&gt;</code> \o/</p> -<p>17:17 <code>&lt;blackboxsw&gt;</code> next meeting is Dec 10, 2018 sameish time</p> -<p>17:17 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-11-12T16:17:00+00:002018-11-12T16:17:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-11-12:/status-2018-11-12.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 12 Nov at 16:17 &mdash; 17:27 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-11-12-16.17.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-11-12-16.17.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:20.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427">https://code …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 12 Nov at 16:17 &mdash; 17:27 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-11-12-16.17.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-11-12-16.17.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:20.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427">https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427</a> </li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:24.</p> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:30.</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="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/358112">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/358112</a> </li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bug/1802598">https://bugs.launchpad.net/cloud-init/+bug/1802598</a> </li> -</ul> -<h3>Office Hours (next ~30 minutes)</h3> -<p>The discussion about "Office Hours (next ~30 minutes)" started at 16:40.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~i.galic/cloud-init/+git/cloud-init/+merge/357723">https://code.launchpad.net/~i.galic/cloud-init/+git/cloud-init/+merge/357723</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 (53)</li> -<li>ubot5 (3)</li> -<li>meetingology (3)</li> -</ul> -<h2>Full Log</h2> -<p>16:17 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:17 <code>&lt;meetingology&gt;</code> Meeting started Mon Nov 12 16:17:50 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:17 <code>&lt;meetingology&gt;</code> </p> -<p>16:17 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> Morning/afternoon folks. Time for another brief episode of cloud-init upstream updates</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> Last meeting was 10/29 and meeting minutes live over on github</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> This meeting is an open forum for cloud-init discussions and status updates, feel free to interject at any time. It really is just a venue by which we can make sure we all have eyes and ears available for discussion on features, bugs or branches if needed.</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> Generally we go through the following topics: Previous Actions, Recent Changes, In-progress Development, and Office hours</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #toic Previous Actions</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> So last meeting we carried in one action, to review the following Azure branch related to DHCP and RHEL race conditions</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427">https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427</a></p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> Looks like rharper got a review in and I don't see any updates from Jason Zion (author) in response to that branch</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> thanks rharper</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> I'm marking that branch as 'Work in progress' and commenting that the author should set it back to 'Needs review' when comments have been addressed</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> ok done. No further actions seen</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:24 * blackboxsw digs up changes since 10/28</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> sorry interrupted.</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> Here are the changes committed:</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> - azure: add udev rules to create cloud-init Gen2 disk name symlinks</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> (<a href="[https://bugs.launchpad.net/bugs/1797480](https://bugs.launchpad.net/bugs/1797480)">LP: #1797480</a>)</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> - tests: ec2 mock missing httpretty user-data and instance-identity routes</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> - azure: remove /etc/netplan/90-hotplug-azure.yaml when net from IMDS</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> - azure: report ready to fabric after reprovision and reduce logging</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> [asakkurr] (<a href="[https://bugs.launchpad.net/bugs/1799594](https://bugs.launchpad.net/bugs/1799594)">LP: #1799594</a>)</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> - query: better error when missing read permission on instance-data</p> -<p>16:29 <code>&lt;ubot5&gt;</code> Ubuntu bug 1797480 in cloud-init "Azure: Support ephemeral disk handling on Gen2 VMs" [High,Fix committed]</p> -<p>16:29 <code>&lt;ubot5&gt;</code> Ubuntu bug 1799594 in cloud-init "Azure - Report ready during preprovisioning as soon as we get the ReprovisionData" [Undecided,Fix committed]</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> As you can see we are seeing a bit of momentum on azure datasource and some continuous integration cleanup on our side.</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> Thanks asakkurr for pulling that Azure branch together</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> We track our current cloud-init development publicly on trello</p> -<p>16:31 <code>&lt;blackboxsw&gt;</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:31 <code>&lt;blackboxsw&gt;</code> if there are any questions about certain branches or work feel free to comment in channel or on the linked branches we document there.</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> It looks like the Ubuntu archive for Disco Dingo series is open, so we'll likely be pushing an upload of tip of cloud-init by EOD today to get a new release queued</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> Also to note, I'd like to see us land <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/358112">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/358112</a> to fix an Azure retry on IMDS timeout to avoid cloud-init giving up if the instance boots while IMDS service is down or temporarily unavailable (I've only seen this once on any azure instance)</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/358112">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/358112</a></p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> we also have a fairly deep review queue, so we'll be attacking that in the 2nd half of today's meeting to clear out and respond to some of those merge proposals</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> I also think we have some mailing list threads to start responding to per usage of EphemeralDHCPv4 and EphemeralIPv4Network context managers.</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> I <em>think</em> the intent there should be that those context managers ensure that they setup whatever requested network configuration is misssing from a network interface.... so if an interface is 'down' yet has correct address configured, ephemeral* will make sure it is in operable 'up' state .</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> See the following bug for more information:</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/+bug/1802598">https://bugs.launchpad.net/cloud-init/+bug/1802598</a></p> -<p>16:38 <code>&lt;ubot5&gt;</code> Ubuntu bug 1802598 in cloud-init "EphemeralIPv4Network: when device has requested existing network config, but link is down, network setup does not bring link up" [Undecided,New]</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> I believe that about wraps it for current in-flight work. I'll drop us into office hours at the point</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 minutes)</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> Cloud-init upstream folks will have eyes on this channel for any discussions. requests, bugs or features folks want to discuss.</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> I'll spend most of this time on reviews to start to clear our review queue (or at least get some responses out to folks for more information)(</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> ok looks like <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357669">https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357669</a> is ready for landing. Just kicking off a CI test run on it</p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> also the approved version of this branch didn't actually match what Jenkins autolander expected, I've kick the jenkins landing job that should truly land that branch now. <a href="https://code.launchpad.net/~asakkurr/cloud-init/+git/cloud-init/+merge/358422">https://code.launchpad.net/~asakkurr/cloud-init/+git/cloud-init/+merge/358422</a>'</p> -<p>17:25 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~i.galic/cloud-init/+git/cloud-init/+merge/357723">https://code.launchpad.net/~i.galic/cloud-init/+git/cloud-init/+merge/357723</a></p> -<p>17:25 <code>&lt;blackboxsw&gt;</code> ok just got through an initial review there too.</p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> ok looks like our lander merged <a href="https://code.launchpad.net/~asakkurr/cloud-init/+git/cloud-init/+merge/358422">https://code.launchpad.net/~asakkurr/cloud-init/+git/cloud-init/+merge/358422</a></p> -<p>17:26 <code>&lt;blackboxsw&gt;</code> and :( <a href="https://jenkins.ubuntu.com/server/job/cloud-init-ci/431/console">https://jenkins.ubuntu.com/server/job/cloud-init-ci/431/console</a> the CI on jason zion</p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> and :( <a href="https://jenkins.ubuntu.com/server/job/cloud-init-ci/431/console">https://jenkins.ubuntu.com/server/job/cloud-init-ci/431/console</a> the CI on jason zion's branch will take 9 hrs and 51 minutes (because it doesn't have our CI fix for leaked test_ec2 link local unittests which take forever to timeout</p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> ok will that about wraps today's status meeting</p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> thanks all</p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-10-29T16:21:00+00:002018-10-29T16:21:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-10-29:/status-2018-10-29.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 29 Oct at 16:21 &mdash; 17:09 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-10-29-16.21.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-10-29-16.21.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:22.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2018-10-15.html#status-2018-10-15">https://cloud-init.github.io/status-2018-10-15.html#status-2018-10-15 …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 29 Oct at 16:21 &mdash; 17:09 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-10-29-16.21.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-10-29-16.21.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:22.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2018-10-15.html#status-2018-10-15">https://cloud-init.github.io/status-2018-10-15.html#status-2018-10-15</a> </li> -<li><strong>ACTION</strong>: Sort and review azure RHEL branch related to ephemeral dhcp handling of dhclient <a href="https://bugs.launchpad.net/cloud-init/+bug/1794399">https://bugs.launchpad.net/cloud-init/+bug/1794399</a></li> -<li><strong>ACTION</strong>: blackboxsw, rharper smoser a review on <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427">https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427</a> before next status meeting for Azure dhcp.</li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:28.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://events.linuxfoundation.org/events/open-source-summit-europe-2018/">https://events.linuxfoundation.org/events/open-source-summit-europe-2018/</a> </li> -</ul> -<h3>In-Progress Development</h3> -<p>The discussion about "In-Progress Development" started at 16:38.</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>Office hours (next ~30 mins)</h3> -<p>The discussion about "Office hours (next ~30 mins)" started at 16:44.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </li> -</ul> -<h2>Vote results</h2> -<h2>Action items, by person</h2> -<ul> -<li>blackboxsw</li> -<li>blackboxsw, rharper smoser a review on <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427">https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427</a> before next status meeting for Azure dhcp.</li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (46)</li> -<li>meetingology (5)</li> -<li>ubot5 (4)</li> -</ul> -<h2>Full Log</h2> -<p>16:21 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:21 <code>&lt;meetingology&gt;</code> Meeting started Mon Oct 29 16:21:16 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:21 <code>&lt;meetingology&gt;</code> </p> -<p>16:21 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> hi folks, now marks a 20 minute belated cloud-init status meeting, an opportunity to chat about current and future cloud-init happenings.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> Today's meeting will go through the typical topics: Previous Actions, Recent Changes, In-progress development and Office hours</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> Looking over our last meeting minutes, we had a single action</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2018-10-15.html#status-2018-10-15">https://cloud-init.github.io/status-2018-10-15.html#status-2018-10-15</a></p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> #action Sort and review azure RHEL branch related to ephemeral dhcp handling of dhclient <a href="https://bugs.launchpad.net/cloud-init/+bug/1794399">https://bugs.launchpad.net/cloud-init/+bug/1794399</a></p> -<p>16:24 * meetingology Sort and review azure RHEL branch related to ephemeral dhcp handling of dhclient <a href="https://bugs.launchpad.net/cloud-init/+bug/1794399">https://bugs.launchpad.net/cloud-init/+bug/1794399</a></p> -<p>16:24 <code>&lt;ubot5&gt;</code> Ubuntu bug 1794399 in cloud-init "cloud-init dhcp_discovery() crashes on preprovisioned RHEL 7.6 VM in Azure" [Undecided,New]</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> the meeting later showed us we didn't really have a branch referencing that bug, looks like paulmey was able to follow up there to tie the related branch to the bug. So we have something to review now</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> So looks like this is a <em>carryover</em> from last meeting, thanks Paul for tying the branch to this bug so we have something to review related to it. The branch is currently waiting on review feedback from cloud-init upstream. So, I'll pull it in for us to review this week</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> #action blackboxsw, rharper smoser a review on <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427">https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427</a> before next status meeting for Azure dhcp.</p> -<p>16:27 * meetingology blackboxsw, rharper smoser a review on <a href="https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427">https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427</a> before next status meeting for Azure dhcp.</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> over the last week, a number of us have been travelling at either planning meetings for cloud-init or the OpenSource Summit in Europe.</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> #link <a href="https://events.linuxfoundation.org/events/open-source-summit-europe-2018/">https://events.linuxfoundation.org/events/open-source-summit-europe-2018/</a></p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> The cloud-init talk had a pretty good turn out at OSS EU. I think we had ~ 100 people in attendance and some good questions about potential support of the following:</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> - Ansible and CFEgine config module support in cloud-initt</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> - better netplan config use-case handling</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> - better vmware integration as well as a request for proxmox (opensource alternative to vmware?) support</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> thanks smoser for a job well done on that talk.</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> beyond the conference highlight, cloud-init tip is being published to Xenial and Bionic on Ubuntu.</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> Expect to see updates published in today's images that will handle template-support for #cloud-config and user-data scripts and generalized instance-data.json on most recent Ubuntu releases.</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> tip of cloud-init has seen the following changes merged:</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> - instance-data: fallback to instance-data.json if sensitive is absent.</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> (<a href="[https://bugs.launchpad.net/bugs/1798189](https://bugs.launchpad.net/bugs/1798189)">LP: #1798189</a>)</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> - docs: remove colon from network v1 config example. [Tomer Cohen]</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> - Add cloud-id binary to packages for SUSE [Jason Zions]</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> - systemd: On SUSE ensure cloud-init.service runs before wicked</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> [Robert Schweikert] (<a href="[https://bugs.launchpad.net/bugs/1799709](https://bugs.launchpad.net/bugs/1799709)">LP: #1799709</a>)</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> - update detection of openSUSE variants [Robert Schweikert]</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> - azure: Add apply_network_config option to disable network from IMDS</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> (<a href="[https://bugs.launchpad.net/bugs/1798424](https://bugs.launchpad.net/bugs/1798424)">LP: #1798424</a>)</p> -<p>16:36 <code>&lt;ubot5&gt;</code> Ubuntu bug 1798189 in cloud-init "cloud-init query: /run/cloud/instance-data-sensitive.json not generated on upgrade" [Medium,Fix committed]</p> -<p>16:36 <code>&lt;ubot5&gt;</code> Ubuntu bug 1799709 in cloud-init "service order is incorrect for SUSE distros" [Undecided,Fix committed]</p> -<p>16:36 <code>&lt;ubot5&gt;</code> Ubuntu bug 1798424 in cloud-init (Ubuntu) "Xenial Azure: Make generation of network config from IMDS hotplug scripts configurable opt-in" [Undecided,New]</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> Thanks robjo for the commitment to keeping SuSE up to date and fully functional with cloud-init.</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> And thanks Jason and Tomer for the contributions to packaging and docs as well</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> Think that about wraps Recent Changes topic....</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> #topic In-Progress Development</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> Check out trello board for a prioritized order of what upstream is working</p> -<p>16:39 <code>&lt;blackboxsw&gt;</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:41 <code>&lt;blackboxsw&gt;</code> There are a couple of community branches in the wings that we'll get reviews on and shepherd into cloud-init proper. Azure has some work to increase efficiency of the detection and reporting during initial boot.</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> smoser is working on supplemental work with meena to handle platform-specializing our cloudinit.net module.</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> and I think we have a couple of branches pulled together for legacy centos6 build support and supporting Azure Gen2 vms.</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> We'll keep the trello board updated as big items come down the pipeline for us.</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> #topic Office hours (next ~30 mins)</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> so eyes will float on this channel a bit for any questions, concerns, bugs or features.</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> thanks again for your time and contributions folks.</p> -<p>17:09 <code>&lt;blackboxsw&gt;</code> alright. guess I'll call it wrap for this meeting. You can tune in to minutes on published github to browse any content that has been discussed at previous status meetings.</p> -<p>17:09 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>17:09 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-10-15T16:15:00+00:002018-10-15T16:15:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-10-15:/status-2018-10-15.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 15 Oct at 16:15 &mdash; 17:00 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-10-15-16.15.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-10-15-16.15.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:18.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </li> -</ul> -<h3>Recent Changes</h3> -<p>The …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status, 15 Oct at 16:15 &mdash; 17:00 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-10-15-16.15.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-10-15-16.15.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:18.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:19.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html#using-instance-data">https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html#using-instance-data</a> </li> -</ul> -<h3>In-Progress Development</h3> -<p>The discussion about "In-Progress Development" started at 16:28.</p> -<ul> -<li><strong>LINK</strong>: trello.com/b/hFtWKUn3/daily-cloud-init-curtin </li> -</ul> -<h3>Office hours (next ~30 mins)</h3> -<p>The discussion about "Office hours (next ~30 mins)" started at 16:35.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bug/1794399">https://bugs.launchpad.net/cloud-init/+bug/1794399</a> </li> -<li><strong>ACTION</strong>: Sort and review azure RHEL branch related to ephemeral dhcp handling of dhclient <a href="https://bugs.launchpad.net/cloud-init/+bug/1794399">https://bugs.launchpad.net/cloud-init/+bug/1794399</a></li> -<li><strong>ACTION</strong>: paulmey to dig up reference to proposed patch for <a href="https://bugs.launchpad.net/cloud-init/+bug/1794399">https://bugs.launchpad.net/cloud-init/+bug/1794399</a></li> -</ul> -<h2>Vote results</h2> -<h2>Action items, by person</h2> -<ul> -<li>paulmey</li> -<li>paulmey to dig up reference to proposed patch for <a href="https://bugs.launchpad.net/cloud-init/+bug/1794399">https://bugs.launchpad.net/cloud-init/+bug/1794399</a></li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (89)</li> -<li>paulmey (22)</li> -<li>ubot5 (13)</li> -<li>meetingology (5)</li> -<li>smoser (2)</li> -</ul> -<h2>Full Log</h2> -<p>16:15 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status</p> -<p>16:15 <code>&lt;meetingology&gt;</code> Meeting started Mon Oct 15 16:15:41 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:15 <code>&lt;meetingology&gt;</code> </p> -<p>16:15 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> hi guys and gals. Today marks a belated cloud-init status meeting we use to provide a forum where folks from the cloud-init community can keep up to date on latest cloud-init developments and tap a shoulder if bugs or features need discussion/attention.</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> Next meeting will be two weeks from now on October 29th. at 16:00 UTC (as in the topic of this channel)</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> Today's meeting will go through the typical topics: Previous Actions, Recent Changes, In-progress development and Office hours</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> No unresolved actions from last meeting on Sept 25th.</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> For those interested our previous meeting minutes are at the following:</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> There has been a lot of work put into cloud-init over the last couple of weeks due to the timing of the Ubuntu Cosmic (18.10) series final freeze and release schedule</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> We managed to squeeze in a couple of features into 18.4 as well as improved some of Ubuntu's automated testing for StableReleaseUpdates (SRUs).</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> Beyond the 18.4 public upstream release (which is in Ubuntu Cosmic). We have the following commits that have landed since the last status meeting.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - tests: allow skipping an entire cloud_test without running.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - tests: disable lxd tests on cosmic</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - cii-tests: use unittest2.SkipTest in ntp_chrony due to new deps</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - lxd: adjust to snap installed lxd.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - docs: surface experimental doc in instance-data.json</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - tests: fix ec2 integration tests. process meta_data instead of meta-data</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - Add support for Infiniband network interfaces (IPoIB). [Mark Goddard]</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - cli: add cloud-init query subcommand to query instance metadata</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - tools/tox-venv: update for new features.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - pylint: ignore warning assignment-from-no-return for _write_network</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - stages: Fix bug causing datasource to have incorrect sys_cfg.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> (<a href="[https://bugs.launchpad.net/bugs/1787459](https://bugs.launchpad.net/bugs/1787459)">LP: #1787459</a>)</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - Remove dead-code _write_network distro implementations.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - net_util: ensure static configs have netmask in translate_network result</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> [Thomas Berger] (<a href="[https://bugs.launchpad.net/bugs/1792454](https://bugs.launchpad.net/bugs/1792454)">LP: #1792454</a>)</p> -<p>16:22 <code>&lt;ubot5&gt;</code> Ubuntu bug 1787459 in cloud-init (Ubuntu) "datasource.sys_cfg gets different values in local stage and after." [Medium,Fix released]</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - Fall back to root:root on syslog permissions if other options fail.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> [Robert Schweikert]</p> -<p>16:22 <code>&lt;ubot5&gt;</code> Ubuntu bug 1792454 in cloud-init "Network configuration broken for some distributions with OpenNebula, EC2, Azure" [High,Fix released]</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - tests: Add mock for util.get_hostname. [Robert Schweikert] (<a href="[https://bugs.launchpad.net/bugs/1792799](https://bugs.launchpad.net/bugs/1792799)">LP: #1792799</a>)</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - ds-identify: doc string cleanup.</p> -<p>16:22 <code>&lt;ubot5&gt;</code> Ubuntu bug 1792799 in cloud-init "Host environment bleeds into test for mirror access testing" [Undecided,Fix released]</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - OpenStack: Support setting mac address on bond.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - bash_completion/cloud-init: fix shell syntax error.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - EphemeralIPv4Network: Be more explicit when adding default route.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> (<a href="[https://bugs.launchpad.net/bugs/1792415](https://bugs.launchpad.net/bugs/1792415)">LP: #1792415</a>)</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - OpenStack: support reading of newer versions of metdata.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - OpenStack: fix bug causing 'latest' version to be used from network.</p> -<p>16:22 <code>&lt;ubot5&gt;</code> Ubuntu bug 1792415 in cloud-init (Ubuntu) "WARNINGs and failures in log on OVH public cloud" [Medium,Fix released]</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> (<a href="[https://bugs.launchpad.net/bugs/1792157](https://bugs.launchpad.net/bugs/1792157)">LP: #1792157</a>)</p> -<p>16:22 <code>&lt;ubot5&gt;</code> Ubuntu bug 1792157 in cloud-init (Ubuntu) "cloud-init uses openstack latest version due to decoding bug" [Medium,Fix released]</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> - Correct spelling in an error message (udevadm). [Katie McLaughlin]</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> - tests: meta_data key changed to meta-data in ec2 instance-data.json</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> (<a href="[https://bugs.launchpad.net/bugs/1797231](https://bugs.launchpad.net/bugs/1797231)">LP: #1797231</a>)</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> - tests: fix kvm integration test to assert flexible config-disk path</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> (<a href="[https://bugs.launchpad.net/bugs/1797199](https://bugs.launchpad.net/bugs/1797199)">LP: #1797199</a>)</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> - tools: Add cloud-id command line utility</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> - instance-data: Add standard keys platform and subplatform. Refactor ec2.</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> - net: ignore nics that have "zero" mac address. (<a href="[https://bugs.launchpad.net/bugs/1796917](https://bugs.launchpad.net/bugs/1796917)">LP: #1796917</a>)</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> - tests: fix apt_configure_primary to be more flexible</p> -<p>16:23 <code>&lt;ubot5&gt;</code> Ubuntu bug 1797231 in cloud-init "ec2 integration test failure on changed instance-data.json" [High,Fix committed]</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> - Ubuntu: update sources.list to comment out deb-src entries. (<a href="[https://bugs.launchpad.net/bugs/74747](https://bugs.launchpad.net/bugs/74747)">LP: #74747</a>)</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> - release 18.4 (<a href="[https://bugs.launchpad.net/bugs/1795741](https://bugs.launchpad.net/bugs/1795741)">LP: #1795741</a>)</p> -<p>16:23 <code>&lt;ubot5&gt;</code> Ubuntu bug 1797199 in cloud-init "kvm integration test failures due to invalid config-disk path" [High,Fix committed]</p> -<p>16:23 <code>&lt;ubot5&gt;</code> Ubuntu bug 1796917 in cloud-images "cloud-init fails to run on latest cosmic minimal image" [High,Fix released]</p> -<p>16:23 <code>&lt;ubot5&gt;</code> Ubuntu bug 74747 in cloud-init (Ubuntu Bionic) "Default sources.list file has source packages enabled by default" [Medium,Confirmed]</p> -<p>16:23 <code>&lt;ubot5&gt;</code> Ubuntu bug 1795741 in cloud-init (Ubuntu) "Release 18.4" [Medium,Fix released]</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> If you get a chance, it's worth noting that #cloud-config files can now be presented as a jinja template to the instance by adding a ## template: jinja as the first line above the #cloud-config in your user-data. Any metadata that cloud-init consumes (like cloud-given hostnames, ip addresses, region names etc) can be sourced and rendered in your cloud-config files now.</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html#using-instance-data">https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html#using-instance-data</a></p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> ^ for more information on instance data and templating</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> #topic In-Progress Development</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> #link trello.com/b/hFtWKUn3/daily-cloud-init-curtin</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> Our trello board tracks our current work. The most notable effort is cloud-init network hotplug handling for datasources which is currently being driven by rharper</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> What he is adding is the ability for for a datasource to be configured react to network hotplug events and apply cloud-init determined network configuration on device add/remove</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> This feature will be opt-in and configurable by the end-user to allow cloud-init to own network for any device added or removed after the initial boot. This feature will debut in OpenStack clouds and will shortly be adopted by other cloud/datasource types.</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> Also, smoser and I will be heading to OpenSource Summit Europe next week in Edinburgh, UK. <a href="https://events.linuxfoundation.org/events/open-source-summit-europe-2018/">https://events.linuxfoundation.org/events/open-source-summit-europe-2018/</a></p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> If you are in town come say hi :)</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> Without further ado, I think that about wraps our status for today</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> #topic Office hours (next ~30 mins)</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> Almost forgot; as part of the SRU process for for cloud-init to release into Xenial and Bionic, we'll be doing some additional manual and automated testing of cloud-init version 18.4 before publishing to those LTS series. I expect that'll take up a bit of our time this week and next as there is a lot to verify for that release.</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> For the next 30 mins, a few of us will have eyes on the channel for anyone with a desire to talk cloud-init bugs, features or reviews. Thanks again for the contributions and making cloud-init better!</p> -<p>16:40 <code>&lt;paulmey&gt;</code> Hi blackboxsw</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> Hi paulmey, how're things</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> ?</p> -<p>16:41 <code>&lt;paulmey&gt;</code> Good! How about yourself?</p> -<p>16:41 <code>&lt;paulmey&gt;</code> My buddy Jason has a bug open that could use some attention: <a href="https://bugs.launchpad.net/cloud-init/+bug/1794399">https://bugs.launchpad.net/cloud-init/+bug/1794399</a></p> -<p>16:41 <code>&lt;ubot5&gt;</code> Ubuntu bug 1794399 in cloud-init "cloud-init dhcp_discovery() crashes on preprovisioned RHEL 7.6 VM in Azure" [Undecided,New]</p> -<p>16:41 <code>&lt;paulmey&gt;</code> this is a stopgap fix until we have a pure-python dhcp client</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> it's been a push for the Cosmic release for us, racing to get things sorted, but I think we are on the other side of any fires now :)</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> ahh checking that bug</p> -<p>16:42 <code>&lt;paulmey&gt;</code> :-) good to hear that</p> -<p>16:42 <code>&lt;paulmey&gt;</code> it's basically just some more robustness around the handling of dhclient execution</p> -<p>16:44 <code>&lt;paulmey&gt;</code> it reproed very reliably on RHEL with reprovisioning (changing network etc., maybe slower/faster dhcp response?), but pretty unreproducible outside of that...</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> paulmey: jason made reference to a patch, but I don't see it linked to the bug.... I'm checking the review queue now</p> -<p>16:44 <code>&lt;paulmey&gt;</code> we saw cloud-init killing or trying to kill the initial process (which has already finished after the util exec)</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> was that bug just a request for us to make cloud-init more resilient in light of forking, or a request to accept a patch</p> -<p>16:45 <code>&lt;paulmey&gt;</code> let me link the patch... once I find it :-)</p> -<p>16:45 <code>&lt;paulmey&gt;</code> give me a minute</p> -<p>16:46 * blackboxsw documents the link for the meeting bot</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/+bug/1794399">https://bugs.launchpad.net/cloud-init/+bug/1794399</a></p> -<p>16:46 <code>&lt;ubot5&gt;</code> Ubuntu bug 1794399 in cloud-init "cloud-init dhcp_discovery() crashes on preprovisioned RHEL 7.6 VM in Azure" [Undecided,New]</p> -<p>16:46 * blackboxsw Sort and review azure RHEL branch related to ephemeral dhcp handling of dhclient <a href="https://bugs.launchpad.net/cloud-init/+bug/1794399">https://bugs.launchpad.net/cloud-init/+bug/1794399</a></p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> #action Sort and review azure RHEL branch related to ephemeral dhcp handling of dhclient <a href="https://bugs.launchpad.net/cloud-init/+bug/1794399">https://bugs.launchpad.net/cloud-init/+bug/1794399</a></p> -<p>16:47 * meetingology Sort and review azure RHEL branch related to ephemeral dhcp handling of dhclient <a href="https://bugs.launchpad.net/cloud-init/+bug/1794399">https://bugs.launchpad.net/cloud-init/+bug/1794399</a></p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> yeah, I wonder if now that 18.4 is cut and released if we want to start banging the drum to get our scapy-based dhclient solution landed in cloud-init proper so we don't have to patchup the ephemeral dhcp work in cloud-init.</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> while you look paulmey, I'll make sure we talk at our standups about what we can do with cloud-init's own dhcp-discovery so we don't have to handle different distro implementations of dhclient. The sandboxed dhclient solution we have felt dirty in the first place.</p> -<p>16:51 <code>&lt;paulmey&gt;</code> yar... I can't find a reference to it in my mails... I'll need to circle back with Jason. I prototyped the patch and he write some unit tests. I know it's somewhere, just not exactly where...</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> our only concern I thought with using scapy was adding the additional package dependency, (which we wouldn't be able to get released back into Ubuntu Xenial Bionic or Cosmic). But, we can resolve to come of with an approach for the nearterm</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> paulmey: sounds good. :) care if I add a virtual action item for you too to the meeting minutes</p> -<p>16:52 <code>&lt;paulmey&gt;</code> Sure, no problem</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> at least it'll guarantee we make progress before next meeting</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> #action paulmey to dig up reference to proposed patch for <a href="https://bugs.launchpad.net/cloud-init/+bug/1794399">https://bugs.launchpad.net/cloud-init/+bug/1794399</a></p> -<p>16:52 * meetingology paulmey to dig up reference to proposed patch for <a href="https://bugs.launchpad.net/cloud-init/+bug/1794399">https://bugs.launchpad.net/cloud-init/+bug/1794399</a></p> -<p>16:52 <code>&lt;ubot5&gt;</code> Ubuntu bug 1794399 in cloud-init "cloud-init dhcp_discovery() crashes on preprovisioned RHEL 7.6 VM in Azure" [Undecided,New]</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> thanks</p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> paulmey: are there other azure related discussions/features that are collecting dust with us that you know of?</p> -<p>16:54 <code>&lt;paulmey&gt;</code> not yet collecting dust, but I know that Sushant Sharma is going to be coming with some networking-related updates for pre-provisioning like we discussed at the summit</p> -<p>16:54 <code>&lt;paulmey&gt;</code> he's testing those on real systems right now</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> I know hyperv reporting feature is functional in cloud-init now. and that folks are instrumenting changes in images to support that.</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> ahh right. good to hear</p> -<p>16:55 <code>&lt;paulmey&gt;</code> we're also talking to SUSE this week to see what the next steps are to get cloud-init functional on Azure</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> ohh neat!</p> -<p>16:56 <code>&lt;paulmey&gt;</code> I know we still have some work items, but we're prototyping some stuff to get ahead of some testing work</p> -<p>16:56 <code>&lt;paulmey&gt;</code> funny thing is that I'm hardly doing any of this work. :-)</p> -<p>16:56 <code>&lt;paulmey&gt;</code> good to see more and more people at MS doing work on cloud-init</p> -<p>16:57 <code>&lt;blackboxsw&gt;</code> heh, juggling a lot I'm sure. yeah it is nice to see more devs involved</p> -<p>16:58 <code>&lt;smoser&gt;</code> paulmey: thats great to hear wrt suse</p> -<p>16:58 <code>&lt;paulmey&gt;</code> ok, cool. I'll follow up with Jason and circle back. If anything else comes to fruition before the 29th, I'll send people here to evangalize</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> perfect. Thanks again paulmey</p> -<p>16:59 <code>&lt;smoser&gt;</code> and /me agrees it'd be good to have a dhclient in cloud-init for what we need it for. scapy or other.</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> think I'll wrap up this meeting for today</p> -<p>16:59 <code>&lt;paulmey&gt;</code> (although it's always nice to talk to you guys... feels good being able to say was on IRC this week... :-P)</p> -<p>16:59 <code>&lt;paulmey&gt;</code> sgtm</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> heh, take care</p> -<p>16:59 <code>&lt;paulmey&gt;</code> ttyl</p> -<p>17:00 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-09-25T16:05:00+00:002018-09-25T16:05:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-09-25:/status-2018-09-25.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 25 Sep at 16:05 &mdash; 17:10 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-09-25-16.05.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-09-25-16.05.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:09.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 25 Sep at 16:05 &mdash; 17:10 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-09-25-16.05.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-09-25-16.05.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:09.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:10.</p> -<h3>In-Progress development</h3> -<p>The discussion about "In-Progress development" started at 16:15.</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>18.4 Release Schedule</h3> -<p>The discussion about "18.4 Release Schedule" started at 16:26.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~cloud-init-dev/cloud-init/+git/cloud-init/+ref/master/+activereviews">https://code.launchpad.net/~cloud-init-dev/cloud-init/+git/cloud-init/+ref/master/+activereviews</a> </li> -<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 16:31.</p> -<ul> -<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 (54)</li> -<li>ubot5 (6)</li> -<li>meetingology (3)</li> -<li>rharper (2)</li> -</ul> -<h2>Full Log</h2> -<p>16:05 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status meeting</p> -<p>16:05 <code>&lt;meetingology&gt;</code> Meeting started Tue Sep 25 16:05:46 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:05 <code>&lt;meetingology&gt;</code> </p> -<p>16:05 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> Hi cloud-init folks, time to kickoff our bi-weekly(ish) status meeting. As mentioned on the mailing list we pushed this meeting out until today so we could have a discussion about the 18.4 upstream release which is scheduled for this Thursday.</p> -<p>16:07 <code>&lt;blackboxsw&gt;</code> I just updated the topic to reflect the 18.4 release date, Sept 27th EOD.</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> for today's meeting we have the following agenda: Previous Actions, Recent Changes, In-progress development and 18.4 release discussion/office hours/ (~30 minutes)</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:09 * blackboxsw reviews our notes from Sept11 @ <a href="https://cloud-init.github.io">https://cloud-init.github.io</a></p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> No actions listed in previous meeting so we'll move to the next topic</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> Last week, we had some travel and planning discussions for cloud-init which took a few cycles out of our upstream landed content, but we were able to review and land a few items over the last couple weeks. Below is the list of changes that have landed in upstream cloud-init master. I expect we'll publish 18.4 release this week to Ubuntu Cosmic, so any changes below will be present in our next public release.</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - pylint: ignore warning assignment-from-no-return for _write_network</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - stages: Fix bug causing datasource to have incorrect sys_cfg.</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> (<a href="[https://bugs.launchpad.net/bugs/1787459](https://bugs.launchpad.net/bugs/1787459)">LP: #1787459</a>)</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - Remove dead-code _write_network distro implementations.</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - net_util: ensure static configs have netmask in translate_network result</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> [Thomas Berger] (<a href="[https://bugs.launchpad.net/bugs/1792454](https://bugs.launchpad.net/bugs/1792454)">LP: #1792454</a>)</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - Fall back to root:root on syslog permissions if other options fail.</p> -<p>16:12 <code>&lt;ubot5&gt;</code> Ubuntu bug 1787459 in cloud-init (Ubuntu) "datasource.sys_cfg gets different values in local stage and after." [Medium,Confirmed]</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> [Robert Schweikert]</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - tests: Add mock for util.get_hostname. [Robert Schweikert] (<a href="[https://bugs.launchpad.net/bugs/1792799](https://bugs.launchpad.net/bugs/1792799)">LP: #1792799</a>)</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - ds-identify: doc string cleanup.</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - OpenStack: Support setting mac address on bond.</p> -<p>16:12 <code>&lt;ubot5&gt;</code> Ubuntu bug 1792454 in cloud-init "Network configuration broken for some distributions with OpenNebula, EC2, Azure" [High,Fix committed]</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> [Fabian Wiesel] (<a href="[https://bugs.launchpad.net/bugs/1682064](https://bugs.launchpad.net/bugs/1682064)">LP: #1682064</a>)</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - bash_completion/cloud-init: fix shell syntax error.</p> -<p>16:12 <code>&lt;ubot5&gt;</code> Ubuntu bug 1792799 in cloud-init "Host environment bleeds into test for mirror access testing" [Undecided,Fix committed]</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - EphemeralIPv4Network: Be more explicit when adding default route.</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> (<a href="[https://bugs.launchpad.net/bugs/1792415](https://bugs.launchpad.net/bugs/1792415)">LP: #1792415</a>)</p> -<p>16:12 <code>&lt;ubot5&gt;</code> Ubuntu bug 1682064 in cloud-init "cloud-init should support config bond mac address " [Medium,Fix committed]</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - OpenStack: support reading of newer versions of metdata.</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - OpenStack: fix bug causing 'latest' version to be used from network.</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> (<a href="[https://bugs.launchpad.net/bugs/1792157](https://bugs.launchpad.net/bugs/1792157)">LP: #1792157</a>)</p> -<p>16:12 <code>&lt;ubot5&gt;</code> Ubuntu bug 1792415 in cloud-init (Ubuntu) "WARNINGs and failures in log on OVH public cloud" [Medium,Confirmed]</p> -<p>16:12 <code>&lt;ubot5&gt;</code> Ubuntu bug 1792157 in cloud-init (Ubuntu) "cloud-init uses openstack latest version due to decoding bug" [Medium,In progress]</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> Thank you again Robert, Thomas and Fabian for continued contributions to cloud-init upstream. Things are looking really good for the upcoming release</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> #topic In-Progress development</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> We are beating the drum toward the 18.4 release, as such, we are going to focus more on low-risk changes and bug fixes as we close in on the 18.4 upstream cutoff.</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> All of the work we have planned lives over on our trello board.</p> -<p>16:18 <code>&lt;blackboxsw&gt;</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:19 <code>&lt;blackboxsw&gt;</code> In our doing and review lane I expect we'll have a couple branches landing for standardizing and generalizing /run/cloud/instance-data.json on all clouds, and a couple of new cloud-init CLI commands 'cloud-init query' and 'cloud-id' to surface standardized instance-data on any cloud platform</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> post-18.4 release rharper has been doing some excellent work adding hotplug network support to OpenStack. I expect we'll be landing his branches shortly after we cut 18.4</p> -<p>16:21 <code>&lt;rharper&gt;</code> blackboxsw: thanks; it's been super interesting</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> this should give us an excellent example of reacting to changing metadata on a given platform, which hopefully other datasources will be able to adopt.</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> As far as additional content for the release, I'll also be circling an email around to the mailing list (cloud-init@lists.launchpad.net ) to describe existing instance data that cloud-init publishes. We are looking for input on common instance meta data that folks would like to see generalized across clouds.</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> I think about wraps up our current dev tasks.</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> #topic 18.4 Release Schedule</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> As mentioned earlier, we would like to cut 18.4 upstream release and tag it at end of day on Thursday, Sept 27th.</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> We will be looking at the active review queue for any branches with the 'Needs review' status.</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~cloud-init-dev/cloud-init/+git/cloud-init/+ref/master/+activereviews">https://code.launchpad.net/~cloud-init-dev/cloud-init/+git/cloud-init/+ref/master/+activereviews</a></p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> If there are branches or bugs that you think need attention, please don't hesitate to mail the mailing list, or ping in this channel to get attention</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> After thursday, we'll be performing some additional manual and automated integration tests and we will plan on publishing 18.4 to Ubuntu Cosmic.</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> As a service, we also will publish that 18.4 release to the following copr repo for those centos-inclined individuals :)</p> -<p>16:30 <code>&lt;blackboxsw&gt;</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:30 <code>&lt;blackboxsw&gt;</code> For each upstream release we sync that release to the 'el-testing' repo.</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> Daily upstream snapshots are also available at <a href="https://copr.fedorainfracloud.org/coprs/g/cloud-init/cloud-init-dev/">https://copr.fedorainfracloud.org/coprs/g/cloud-init/cloud-init-dev/</a></p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> #topic Office hours (next ~30 mins)</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> I think that about wraps the fire hose of content for our meeting. For the next 30 mins we should have eyes on this channel to discuss the finer points of life as well as anything cloud-init related. Bring your bugs, gripes, requests, reviews and/or discussions and we'll get a good answer for you.</p> -<p>16:33 * blackboxsw is going to hitup the review queue at the moment so see if there are some cloud-init branches we can clear out.</p> -<p>16:45 <code>&lt;rharper&gt;</code> +1</p> -<p>17:09 <code>&lt;blackboxsw&gt;</code> ok that about wraps it for today.</p> -<p>17:10 <code>&lt;blackboxsw&gt;</code> minutes will be published to the following link. Thanks again folks! See you next time</p> -<p>17:10 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io">https://cloud-init.github.io</a></p> -<p>17:10 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-09-04T16:08:00+00:002018-09-04T16:08:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-09-04:/status-2018-09-04.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 04 Sep at 16:08 &mdash; 17:01 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-09-04-16.08.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-09-04-16.08.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> - <strong>LINK</strong>: <a href="https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin">https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin</a> - <strong>LINK</strong>: <a href="https://powersj.github.io/post/cloud-init-summit18/">https://powersj.github.io/post …</a></p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 04 Sep at 16:08 &mdash; 17:01 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-09-04-16.08.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-09-04-16.08.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> - <strong>LINK</strong>: <a href="https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin">https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin</a> - <strong>LINK</strong>: <a href="https://powersj.github.io/post/cloud-init-summit18/">https://powersj.github.io/post/cloud-init-summit18/</a> </p> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:22.</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>?menu=filter&amp;filter=cloud-init </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/353740">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/353740</a> </li> -</ul> -<h3>Office Hource (next ~30 mins)</h3> -<p>The discussion about "Office Hource (next ~30 mins)" started at 16:30.</p> -<h3>Active review queue scrub (and open discussion/office hours)</h3> -<p>The discussion about "Active review queue scrub (and open discussion/office hours)" started at 16:41.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~praween/cloud-init/+git/cloud-init/+merge/353733">https://code.launchpad.net/~praween/cloud-init/+git/cloud-init/+merge/353733</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904</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 (60)</li> -<li>smoser (8)</li> -<li>meetingology (3)</li> -<li>marcoceppi (2)</li> -<li>ubot5 (1)</li> -</ul> -<h2>Full Log</h2> -<p>16:08 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status meeting</p> -<p>16:08 <code>&lt;meetingology&gt;</code> Meeting started Tue Sep 4 16:08:21 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:08 <code>&lt;meetingology&gt;</code> </p> -<p>16:08 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:08 <code>&lt;marcoceppi&gt;</code> rharper: oddly enough, that didn't work. root wasn't set</p> -<p>16:08 <code>&lt;marcoceppi&gt;</code> I'll bother you all after the meeting</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> or during marcoceppi :) sorry for the delay folks, I lost internet for a bit and just got it back up.</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> let's kickoff the bi-weekly status meeting and see what discussion we have for today</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> Our agenda is the following: Previous Actions, Recent Changes, In-progress development and office hours (~30 minutes)</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> the only logged action per last meeting was the following:</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> rharper/blackboxsw close out on this review before cloud-init summit <a href="https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742">https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742</a></p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> we were able to land that branch at the cloud-init summit 2 weeks ago and also landed a followup fix for a lock race condition related to that changeset</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> so we can cross that one off the list</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> .... and for those following from home. our meeting minutes from the last status meeting are here</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> Also generically we had a number of action items that came out of our Seattle cloud-init summit with various cloud and distribution partners. Our team will be having a review meeting to discuss some of those actions/decisions and ultimately convert them into trello work items on our board</p> -<p>16:13 <code>&lt;blackboxsw&gt;</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:16 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> Over the last couple weeks Microsoft hosted a very producting Cloud-init Summit conference in Seattle. A number of clouds and distribution vendors participated to set goals for the cloud-init upstream project. powersj wrote up a nice post to capture some of that work. Thank you all for partipating and helping to improve cloud-init</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> #link <a href="https://powersj.github.io/post/cloud-init-summit18/">https://powersj.github.io/post/cloud-init-summit18/</a></p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> also the following changes landed upstream:</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> - Add unit tests for config/cc_ssh.py [Francis Ginther]</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> - Fix the built-in cloudinit/tests/helpers:skipIf</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> - read-version: enhance error message [Joshua Powers]</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> - hyperv_reporting_handler: simplify threaded publisher</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> - VMWare: Fix a network config bug in vm with static IPv4 and no gateway.</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> [Pengpeng Sun] (LP: #1766538)</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> - logging: Add logging config type hyperv for reporting via Azure KVP</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> [Andy Liu]</p> -<p>16:21 <code>&lt;ubot5&gt;</code> Launchpad bug 1766538 in cloud-init (Ubuntu) "network customization with cloud-init does not work on Ubuntu18.04 Beta2 Server" [Medium,Confirmed] <a href="https://launchpad.net/bugs/1766538">https://launchpad.net/bugs/1766538</a></p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> as always, check our board if there are questions about what we are working on the cloud-init side of the house. any cloud-init cards will have a cloud-init label</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #link <a href="https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin">https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin</a>?menu=filter&amp;filter=cloud-init</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> we are working a couple of fixes for Oracle as well as the following features that could be interesting to folks:</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> - the ability to use jinja templating in cloud-config or user-scripts to reference any standardized instance meta data cloud-init consumes</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> - allowing new ssh user config in #cloud-config to specify a ssh-redirect-user, which would allow someone to disable an existing ssh user and provide a redirect message mentioning which username is the preferred default user</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - ryan is working on refactoring the sysconfig renderer align multiple distros, so that we don't have slightly different implementations in cloud-init for each distribution</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/353740">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/353740</a></p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> beyond that, there a number of new contibutions that have been generated by some of the amazon folks that we plan on reviewing and landing for better amazon linux support</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> thanks again for all the good work. I think we'll transition to the open forum for any discussion/feature/bug work.</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> #topic Office Hource (next ~30 mins)</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> we'll have eyes on this channel for the next 30 mins. any topic is acceptable; big or small. Bugs, discussions, features, complaints etc.</p> -<p>16:31 <code>&lt;smoser&gt;</code> o/</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> sorry for the interrupt earlier :)</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> Since we have a clear discussion docket for office hours... At the summit we decided maybe it would be a good idea to try reviewing our active review queue to keep the momentum going there and avoid stale branches sitting unresolved for a while.</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> smoser: rharper you gents up for taking a swing at our review queue in this forum to see if we can prioritize what needs landing/response etc?</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> #topic Active review queue scrub (and open discussion/office hours)</p> -<p>16:42 <code>&lt;smoser&gt;</code> sure.</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> I wanted to see if we could land Praveen's branch for Amazon linux support.</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~praween/cloud-init/+git/cloud-init/+merge/353733">https://code.launchpad.net/~praween/cloud-init/+git/cloud-init/+merge/353733</a></p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> their CI needs a new makefile target "sources"</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> I suggested that maybe they add that functionality into ./packages/brpm instead of just the commands on the cli</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> since we use brpm in our ci too. ....</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> Praveen had agreed at the summit to make some changes to extend brpm with a new cmdline option to do this work. But I don't see anything pushed. I'd like to mark this work in progress and comment to that affect. sound good?</p> -<p>16:46 <code>&lt;smoser&gt;</code> blackboxsw: that sounds good</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> smoser: ok <a href="https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/354001">https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/354001</a> I'll grab today after this meeting so we can land all the leaky unit tests. geez man</p> -<p>16:49 * blackboxsw grabs the review slot</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> I believe robert's branch is tabled until ryan's sysconfig branch is landed</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904</a></p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> ^ should we mark this 'work in progress' as it's blocked? or maybe just leave it in the active queue</p> -<p>16:51 <code>&lt;smoser&gt;</code> blackboxsw: your needs information still stands right?</p> -<p>16:51 <code>&lt;smoser&gt;</code> lets move it to work-in-progress and ask for response and also ask if it is sitll necessary (unless you know that it is or is not)</p> -<p>16:52 <code>&lt;smoser&gt;</code> and suggest that it will need to be re-worked.</p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> smoser: that sounds good. my 'needs information' on that is resolved/read/discussed already. so I should abstain for the moment until the rework</p> -<p>16:57 <code>&lt;blackboxsw&gt;</code> ok couple more minutes... any additional reviews we should look at in earnest now?</p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> I kinda want to hold on <a href="https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392">https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392</a> until we have our summit retro meeting today</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> here's a short one. <a href="https://code.launchpad.net/~otubo/cloud-init/+git/cloud-init/+merge/353436.">https://code.launchpad.net/~otubo/cloud-init/+git/cloud-init/+merge/353436.</a> should we mark this 'work in progress' until smoser's review comments are addressed and unit tests added?</p> -<p>16:59 <code>&lt;smoser&gt;</code> blackboxsw: yeah. i'll do that.</p> -<p>17:00 <code>&lt;blackboxsw&gt;</code> ok thanks. and I think that'll about wrap it for today. If we don't resolve the other community reviews by next status meeting, we can continue chipping away at this queue then.</p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> I'll post the minutes to cloudinit.github.io just after this.</p> -<p>17:01 <code>&lt;smoser&gt;</code> blackboxsw: i'm loking at rharper's mp now for the system config</p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> ok I'll get your review on <a href="https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/354001">https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/354001</a> now</p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-08-20T16:09:00+00:002018-08-20T16:09:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-08-20:/status-2018-08-20.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 20 Aug at 16:09 &mdash; 17:04 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-08-20-16.09.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-08-20-16.09.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:13.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 20 Aug at 16:09 &mdash; 17:04 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-08-20-16.09.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-08-20-16.09.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:13.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:13.</p> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:21.</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>Office Hource (next ~30 mins)</h3> -<p>The discussion about "Office Hource (next ~30 mins)" started at 16:27.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742">https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742</a> </li> -<li><strong>ACTION</strong>: rharper/blackboxsw close out on this review before cloud-init summit <a href="https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742">https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742</a></li> -</ul> -<h2>Vote results</h2> -<h2>Action items, by person</h2> -<ul> -<li>blackboxsw</li> -<li>rharper/blackboxsw close out on this review before cloud-init summit <a href="https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742">https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742</a></li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (39)</li> -<li>ubot5 (5)</li> -<li>paulmey (5)</li> -<li>meetingology (4)</li> -</ul> -<h2>Full Log</h2> -<p>16:09 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status meeting</p> -<p>16:09 <code>&lt;meetingology&gt;</code> Meeting started Mon Aug 20 16:09:08 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:09 <code>&lt;meetingology&gt;</code> </p> -<p>16:09 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> For those around, let's kickoff another cloud-init status meeting. Feel free to interrupt as we go through the agenda for today.</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> agenda: Previous Actions, Recent Changes, In-progress development and office hours (~30 minutes)</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> nothing to speak of here as far as I recall.</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> We have recently landed the following content in tip of cloud-init over the last 2 weeks</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> - Add datasource Oracle Compute Infrastructure (OCI).</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> - azure: allow azure to generate network configuration from IMDS per boot.</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> - Scaleway: Add network configuration to the DataSource [Louis Bouchard]</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> - docs: Fix example cloud-init analyze command to match output.</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> [Wesley Gao]</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> - netplan: Correctly render macaddress on a bonds and bridges when</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> provided. (LP: #1784699)</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> - tools: Add 'net-convert' subcommand command to 'cloud-init devel'.</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> - redhat: remove ssh keys on new instance. (LP: #1781094)</p> -<p>16:14 <code>&lt;ubot5&gt;</code> Launchpad bug 1784699 in cloud-init "cloud-init not setting mac address for bond or bridge in bionic" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1784699">https://launchpad.net/bugs/1784699</a></p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> - Use typeset or local in profile.d scripts. (LP: #1784713)</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> - OpenNebula: Fix null gateway6 [Akihiko Ota] (LP: #1768547)</p> -<p>16:15 <code>&lt;ubot5&gt;</code> Launchpad bug 1781094 in cloud-init "cloud.cfg.tmpl should not include "ssh_deletekeys: 0"" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1781094">https://launchpad.net/bugs/1781094</a></p> -<p>16:15 <code>&lt;ubot5&gt;</code> Launchpad bug 1784713 in cloud-init (Ubuntu) "cloud-init profile.d files use bash-specific builtin "local"" [Low,Confirmed] <a href="https://launchpad.net/bugs/1784713">https://launchpad.net/bugs/1784713</a></p> -<p>16:15 <code>&lt;ubot5&gt;</code> Launchpad bug 1768547 in cloud-init (Ubuntu) "OpenNebula DataSource adds null gateway6 to netplan config" [Medium,Confirmed] <a href="https://launchpad.net/bugs/1768547">https://launchpad.net/bugs/1768547</a></p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> most notable is the new datasource for Oracle and Azure datasource now emitting network configuration per boot.</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> new Ubuntu cosmic images should contain 18.3-24-gf6249277-0ubuntu1 with the lastest patches</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> The team in general is perparing for the cloud-init summit conference which will be the second half of this week with cloud and distro vendors so we'll probably be landing a couple more branches in preparation for talks/demos there.</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> <em>preparing</em> rather</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> Our trello board is a good representation of any existing work we are "Doing"</p> -<p>16:24 <code>&lt;blackboxsw&gt;</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:26 <code>&lt;blackboxsw&gt;</code> recently powersj has also moved our jenkins server around to a new network so there has been a good bit of work getting all things jenkins back up and running behind the new proxies/firewalls etc.</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> thanks for the heavy lift powersj</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> I think that wraps up all things cloud-init....</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> #topic Office Hource (next ~30 mins)</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> We'll have eyes on this channel for any quips, complaints, bug, feature or branch discussions for the next half hour</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> Otherwise, we'll be excited to see a few of you again in this year's cloud-init summit.\</p> -<p>16:28 <code>&lt;paulmey&gt;</code> Hi all, I'd like to request a review for this MP: <a href="https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742">https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742</a> (attached to LP: #1722959)</p> -<p>16:28 <code>&lt;ubot5&gt;</code> Launchpad bug 1722959 in cloud-init "Implement Key-Value Pair Telemetry for Azure" [Undecided,In progress] <a href="https://launchpad.net/bugs/1722959">https://launchpad.net/bugs/1722959</a></p> -<p>16:29 <code>&lt;paulmey&gt;</code> Hoping we can get this merged sometime soon. :-)</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> Hi paulmey thanks for the ping on this.</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742">https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742</a></p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> #action rharper/blackboxsw close out on this review before cloud-init summit <a href="https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742">https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742</a></p> -<p>16:30 * meetingology rharper/blackboxsw close out on this review before cloud-init summit <a href="https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742">https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742</a></p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> that has gotten dusty, thank you</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> I'll start a review in earnest now</p> -<p>16:31 <code>&lt;paulmey&gt;</code> Thanks. The dust is mostly mine... Andy has been working on this, but he's in a different time zone, so I'm still pushing it...</p> -<p>16:31 <code>&lt;paulmey&gt;</code> 😉</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> paulmey: I'll try spinning up an azure vm to test this out</p> -<p>16:34 <code>&lt;paulmey&gt;</code> let me know if you need anything</p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> ok thanks folks for tuning in. See you next time</p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-08-06T16:04:00+00:002018-08-06T16:04:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-08-06:/status-2018-08-06.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 06 Aug at 16:04 &mdash; 17:04 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-08-06-16.04.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-08-06-16.04.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:09.</p> -<ul> -<li><strong>ACTION</strong>: rharper …</li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 06 Aug at 16:04 &mdash; 17:04 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-08-06-16.04.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-08-06-16.04.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:09.</p> -<ul> -<li><strong>ACTION</strong>: rharper: and I need to review <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904</a></li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:11.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://jenkins.ubuntu.com/server/job/admin-lp-git-autoland/">https://jenkins.ubuntu.com/server/job/admin-lp-git-autoland/</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:19.</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="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348704">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348704</a> </li> -</ul> -<h3>Office Hource (next ~30 mins)</h3> -<p>The discussion about "Office Hource (next ~30 mins)" started at 16:25.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742.">https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742.</a> </li> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io">https://cloud-init.github.io</a> for meeting minutes</li> -</ul> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (59)</li> -<li>powersj (6)</li> -<li>meetingology (4)</li> -<li>ubot5 (1)</li> -<li>dpb1 (1)</li> -</ul> -<h2>Full Log</h2> -<p>16:04 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status meeting</p> -<p>16:04 <code>&lt;meetingology&gt;</code> Meeting started Mon Aug 6 16:04:05 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:04 <code>&lt;meetingology&gt;</code> </p> -<p>16:04 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:04 <code>&lt;dpb1&gt;</code> o/</p> -<p>16:04 <code>&lt;blackboxsw&gt;</code> hi folks, let's kickoff another cloud-init status meeting. Welcome back. Lot's of summer vacations disrupting our typical meeting schedule.</p> -<p>16:05 <code>&lt;blackboxsw&gt;</code> Our last meeting's minutes should be up on our github site</p> -<p>16:05 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>16:07 <code>&lt;blackboxsw&gt;</code> for this meeting we'll go through the following topics: previous actions, recent work, in-progress development and office hours</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> from our last meeting we had a couple of actions to carry over</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> we landed the folowing branch which added support for a datasource to re-write network config across each boot. <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348000">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348000</a></p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> #action rharper: and I need to review <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904</a></p> -<p>16:10 * meetingology rharper: and I need to review <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904</a></p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> the above is still a carryover</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> that's all for actions from last meeting</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> the following has landed in cloud-init tip:</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> * oracle: fix detect_openstack to report True on OracleCloud.com DMI data (LP: #1784685)</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> * tests: improve LXDInstance trying to workaround or catch bug.*</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> * update_metadata re-config on every boot comments and tests not quite right [Mike Gerdts]</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> * docs: note in rtd about avoiding /tmp when writing files</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> * ubuntu,centos,debian: get_linux_distro to align with platform.dist</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> * Fix boothook docs on environment variable name (INSTANCE_I -&gt;` INSTANCE_ID) (Marc Tamsky)</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> * update_metadata: a datasource can support network re-config every boot</p> -<p>16:13 <code>&lt;ubot5&gt;</code> Launchpad bug 1784685 in cloud-init "Oracle: cloud-init openstack local detection too strict for oracle cloud" [High,Fix committed] <a href="https://launchpad.net/bugs/1784685">https://launchpad.net/bugs/1784685</a></p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> * tests: drop salt-minion integration test</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> * Retry on failed import of gpg receive keys.</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> * tools: Fix run-container when neither source or binary package requested.</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> * docs: Fix a small spelling error (Oz N Tiram)</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> * tox: use simplestreams from git repository rather than bzr.</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> generally 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.</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> notably, we discovered a potential regression in Oracle datasource detection of their OpenStack implementation so that fix is queued for publish into xenial and bionic</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 18.3-9 is what folks are looking for. in xenial/bionic/cosmic for latest cloud-init containing all the above fixes</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> Also 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 acceptm</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> Also 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.</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> #link <a href="https://jenkins.ubuntu.com/server/job/admin-lp-git-autoland/">https://jenkins.ubuntu.com/server/job/admin-lp-git-autoland/</a></p> -<p>16:16 <code>&lt;powersj&gt;</code> yep that is live and with a recent fix to remove the extra "Author" line now</p> -<p>16:16 <code>&lt;powersj&gt;</code> hopefully it is saving blackboxsw, smoser, and rharper time ;)</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> powersj: can you explain what it does (so I don't have to type)</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> :)</p> -<p>16:17 <code>&lt;powersj&gt;</code> If a merge request is put in the "Approved" state, it will get test merged with the master branch</p> -<p>16:17 <code>&lt;powersj&gt;</code> the tests will run the same as during a review and verify that it can merge cleanly</p> -<p>16:18 <code>&lt;powersj&gt;</code> the commit message will get linted to verify it fits our format</p> -<p>16:18 <code>&lt;powersj&gt;</code> and if everything looks good, get merged in and pushed to master</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> thanks for that work powersj. it looks/works great so far.</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> All our current work is visible at the following trello board</p> -<p>16:19 <code>&lt;blackboxsw&gt;</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:20 <code>&lt;blackboxsw&gt;</code> I expect we'll have a couple of branches landed shortly in the following areas:</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> - smoser is working: A datasource specific to Oracle, because of their specific implementation of Openstack. Oracle will no longer use just stock DataSourceOpenStack.</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> - I</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> - I'm trying to wrap up a branch for Azure to write network data from their IMDS per-boot</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348704">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348704</a></p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> - Joyent (SmartOS) per-boot network config review</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> - a couple netplan config option bugs for bionic ++</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> - and standardize instance-data sourcing in #cloud-config files (like referencing the hostname as detected from instance metadata)</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> I think that probably wraps it up for stuff in progress</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> anything I'm missing?</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> ... without further ado</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> #topic Office Hource (next ~30 mins)</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> eyes will float on this channel for any bug/feature discussions, review requests etc. any cloud-init topic is acceptable.</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> a 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.</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> while I'm at it, I think I'll set the topic to next status meeting time so folks know it's coming.</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> also 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.</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742.">https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742.</a></p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> it looks a bit noisy on the debug front with adding out/err messages for all subp calls, but other than that fairly straight forward.</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> looks like that's a wrap for today.</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io">https://cloud-init.github.io</a> for meeting minutes</p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> see you next time: 2 weeks from today</p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-07-02T16:05:00+00:002018-07-02T16:05:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-07-02:/status-2018-07-02.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 02 Jul at 16:05 &mdash; 17:02 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-07-02-16.05.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-07-02-16.05.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:09.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348000">https …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 02 Jul at 16:05 &mdash; 17:02 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-07-02-16.05.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-07-02-16.05.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:09.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348000">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348000</a> </li> -<li><strong>ACTION</strong>: haper/blackboxsw review <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904</a> [CARRYOVER]</li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:15.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://lists.launchpad.net/cloud-init/msg00164.html">https://lists.launchpad.net/cloud-init/msg00164.html</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:21.</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="https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/">https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348704">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348704</a> </li> -</ul> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 16:31.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </li> -</ul> -<h2>Vote results</h2> -<h2>Action items, by person</h2> -<ul> -<li>blackboxsw</li> -<li>haper/blackboxsw review <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904</a> [CARRYOVER]</li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (60)</li> -<li>meetingology (4)</li> -<li>ubot5 (3)</li> -<li>danMS_ (1)</li> -<li>mgerdts (1)</li> -</ul> -<h2>Full Log</h2> -<p>16:05 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status meeting</p> -<p>16:05 <code>&lt;meetingology&gt;</code> Meeting started Mon Jul 2 16:05:44 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:05 <code>&lt;meetingology&gt;</code> </p> -<p>16:05 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> hi folks, just kicking off another cloud-init status meeting to communicate the recent events in cloud-init land.</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> welcome to all, feel free to interrupt as we go through the agenda. As always cloud-init status minutes will live at the following url</p> -<p>16:07 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>16:07 <code>&lt;blackboxsw&gt;</code> The meeting agenda is as follows:</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> agenda: Previous Actions, Recent Changes, In-progress develepment and office hours (~30 minutes)</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> Last meeting we have a couple of actions to look over:</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> #ACTION blackboxsw carryover network hotplug vs network maintenance on reboot-only</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> #ACTION blackboxsw carryover network hotplug vs network maintenance on reboot-only [DONE]</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> we held multiple meetings, including discussion with mgerdts on a SmartOS solution for handling regenerating network configuration per-boot when a user selects this behavior</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> We have just landed a supporting branch in cloud-init tip to enable datasources to define what events (BOOT vs BOOT_NEW_INSTANCE) they will react to when generating network config.</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348000">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348000</a></p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> that should give a foundation for other datasources to write/change network config across boots, instead of allowing network config to remain static based on cloud-init's initial network configuration</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> the 2nd action ..</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> #ACTION haper/blackboxsw review <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904</a> [CARRYOVER]</p> -<p>16:14 * meetingology haper/blackboxsw review <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904</a> [CARRYOVER]</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> I'd like to carry this one over. We got a bit bogged down in SRU, CentOs stuff last week and we shold be able to get some eyes on this branch</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> I think that's it for actions.</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> Below is a list of changes landed in cloud-init tip or package publishing that has occured for the project:</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> * our 18.3 release was cut from tip if you caught the email on that mailing list</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> Congrats all for a great effort at improving quality and adding more datasource/cloud support</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> #link <a href="https://lists.launchpad.net/cloud-init/msg00164.html">https://lists.launchpad.net/cloud-init/msg00164.html</a></p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> ^ in case you didn't get the message</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> * we also publish 18.3 release into Ubuntu Cosmic and started a stable release update (SRU) to publish 18.3 in to xenial, artful, bionic</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> published*</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> expectations are that xenial, artful and bionic will have 18.3 after this week of testing</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> the remaining changes landed in tip are:</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - update_metadata: a datasource can support network re-config every boot</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> [Chad Smith]</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - tests: drop salt-minion integration test (LP: #1778737)</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - Retry on failed import of gpg receive keys.</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - tools: Fix run-container when neither source or binary package requested.</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - docs: Fix a small spelling error. [Oz N Tiram]</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - tox: use simplestreams from git repository rather than bzr.</p> -<p>16:20 <code>&lt;ubot5&gt;</code> Launchpad bug 1778737 in cloud-init "salt-minion test needs fixing" [Undecided,Fix committed] <a href="https://launchpad.net/bugs/1778737">https://launchpad.net/bugs/1778737</a></p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - release 18.3 [Chad Smith] (LP: #1777743)</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - docs: represent sudo:false in docs for user_groups config module</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> [Chad Smith]</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> - Explicitly prevent <code>sudo</code> access for user module</p> -<p>16:20 <code>&lt;ubot5&gt;</code> Launchpad bug 1777743 in cloud-init "Release 18.3" [Undecided,Fix released] <a href="https://launchpad.net/bugs/1777743">https://launchpad.net/bugs/1777743</a></p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> [Jacob Bednarz] (LP: #1771468)</p> -<p>16:20 <code>&lt;ubot5&gt;</code> Launchpad bug 1771468 in cloud-init "Allow a way to explicitly disable sudo for a user" [Undecided,Fix released] <a href="https://launchpad.net/bugs/1771468">https://launchpad.net/bugs/1771468</a></p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> next topic</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> Our ongoing development is always listed publicly at the following trello board</p> -<p>16:22 <code>&lt;blackboxsw&gt;</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:23 <code>&lt;blackboxsw&gt;</code> We are going to be focused on SRU validation for Ubuntu this week which should take up the majority of the week.</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> At the end of this SRU process we will also rebuild centos binaries in our copr repo</p> -<p>16:23 <code>&lt;blackboxsw&gt;</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:24 <code>&lt;blackboxsw&gt;</code> so that folks in other envs will have access to latest bits if their distro/cloud doesn't have that update</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> Also, specfic to mgerdts and danMS_ there is a branch in progress for Azure support to regenerate network-config for all interfaces on each boot.</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348704">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348704</a></p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> mgerdts: might like it only as another example of a datasource managing network config across boots</p> -<p>16:26 <code>&lt;mgerdts&gt;</code> Thanks. Will look at that soon.</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> no prob, sorry for all the pings :)</p> -<p>16:26 <code>&lt;danMS_&gt;</code> will take a look too and spk to paulmey</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> also smoser is working on implementing an OCIC datasource (Oracle Cloud Infrastructure Classic)</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> think that wraps it up for this week.</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> there should be a couple of eyes on this channel for discusssions, questions, bug requests etc that might need a bit more attention.</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> again, thanks for tuning in and helping make cloud-init better!</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> meeting minutes will ultimately show at</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-06-18T16:08:00+00:002018-06-18T16:08:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-06-18:/status-2018-06-18.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 18 Jun at 16:08 &mdash; 17:23 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-06-18-16.08.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-06-18-16.08.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:11.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2018-05-29.html#status-2018-05-29">https://cloud-init.github.io/status-2018-05-29.html …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 18 Jun at 16:08 &mdash; 17:23 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-06-18-16.08.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-06-18-16.08.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:11.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://cloud-init.github.io/status-2018-05-29.html#status-2018-05-29">https://cloud-init.github.io/status-2018-05-29.html#status-2018-05-29</a> </li> -<li><strong>ACTION</strong>: blackboxsw review distro dection and empty modules list [ DONE ] both robjo's branches are landed as of friday of last week.</li> -<li><strong>ACTION</strong>: blackboxsw carryover network hotplug vs network maintenance on reboot-only</li> -<li><strong>LINK</strong>: <a href="https://hackmd.io/NUUO4nndS4CXTItl8Rs6Nw">https://hackmd.io/NUUO4nndS4CXTItl8Rs6Nw</a> </li> -<li><strong>LINK</strong>: expectation is to get the foundation landed this week</li> -<li><strong>LINK</strong>: <a href="https://trello.com/c/Yp6VG2lP/837-eventpolicy-foundation-for-joyent-and-azure-coldplug">https://trello.com/c/Yp6VG2lP/837-eventpolicy-foundation-for-joyent-and-azure-coldplug</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+ref/feature/maintain-network-on-boot">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+ref/feature/maintain-network-on-boot</a> </li> -<li><strong>LINK</strong>: <a href="https://hackmd.io/aODzXfa_TOikNtYBLt8erA">https://hackmd.io/aODzXfa_TOikNtYBLt8erA</a> </li> -<li><strong>LINK</strong>: <a href="https://hackmd.io/aODzXfa_TOikNtYBLt8erA">https://hackmd.io/aODzXfa_TOikNtYBLt8erA</a> </li> -</ul> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:27.</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>Cloud-init 18.3 release</h3> -<p>The discussion about "Cloud-init 18.3 release" started at 16:36.</p> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 16:46.</p> -<ul> -<li><strong>ACTION</strong>: rhaper/blackboxsw review <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904</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>Action items, by person</h2> -<ul> -<li>blackboxsw</li> -<li>blackboxsw review distro dection and empty modules list [ DONE ] both robjo's branches are landed as of friday of last week.</li> -<li>blackboxsw carryover network hotplug vs network maintenance on reboot-only</li> -<li>rhaper/blackboxsw review <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904</a></li> -<li>robjo</li> -<li>blackboxsw review distro dection and empty modules list [ DONE ] both robjo's branches are landed as of friday of last week.</li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (83)</li> -<li>robjo (14)</li> -<li>rharper (10)</li> -<li>ubot5 (7)</li> -<li>smoser (7)</li> -<li>meetingology (6)</li> -</ul> -<h2>Full Log</h2> -<p>16:08 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status meeting</p> -<p>16:08 <code>&lt;meetingology&gt;</code> Meeting started Mon Jun 18 16:08:07 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:08 <code>&lt;meetingology&gt;</code> </p> -<p>16:08 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> Hi folks and welcome. We've got a big week this week as we are planning on a cloud-init release. So we will have an additional topic in today's agenda</p> -<p>16:09 <code>&lt;smoser&gt;</code> o/</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> it's been a few weeks, due to holiday schedules/travel, our agenda will be as following: Previous Actions, Recent Changes, In-progress develepment, cloud-init release 18.3 and office hours</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> last action items are listed in our meeting minutes at the following url:</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/status-2018-05-29.html#status-2018-05-29">https://cloud-init.github.io/status-2018-05-29.html#status-2018-05-29</a></p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> #ACTION blackboxsw review distro dection and empty modules list [ DONE ] both robjo's branches are landed as of friday of last week.</p> -<p>16:12 * meetingology blackboxsw review distro dection and empty modules list [ DONE ] both robjo's branches are landed as of friday of last week.</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> that was a carryover from the meeting before I believe.</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> #ACTION blackboxsw carryover network hotplug vs network maintenance on reboot-only</p> -<p>16:13 * meetingology blackboxsw carryover network hotplug vs network maintenance on reboot-only</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> I think this was the only other unresolved action. Our team has had mutliple followup discussions internally and with mgerts from Joyent/SmartOs as well</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> smoser: and rharper drew up a hackmd doc related to this work here:</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> #link <a href="https://hackmd.io/NUUO4nndS4CXTItl8Rs6Nw">https://hackmd.io/NUUO4nndS4CXTItl8Rs6Nw</a></p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> We've come to a conclusion on a common near-term approach that will support cold-plug scenarios by allowing datasources to claim whether or not they will re-render networking on a boot event. This would allow cloud-init to react to network metadata changes across boot and enable/disable those devices accordingly</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> a WIP branch is available here</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> #link expectation is to get the foundation landed this week</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> and tracked in trello here</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> #link <a href="https://trello.com/c/Yp6VG2lP/837-eventpolicy-foundation-for-joyent-and-azure-coldplug">https://trello.com/c/Yp6VG2lP/837-eventpolicy-foundation-for-joyent-and-azure-coldplug</a></p> -<p>16:17 <code>&lt;robjo&gt;</code> Note that the metdata ins EC2 is "stale", AFIK, or at least some parts of the data are stale, i.e. they only get refreshed on instance restart</p> -<p>16:17 <code>&lt;rharper&gt;</code> is it instance restart or "re DHCP" ?</p> -<p>16:17 <code>&lt;rharper&gt;</code> ie, bounce the interface ?</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+ref/feature/maintain-network-on-boot">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+ref/feature/maintain-network-on-boot</a></p> -<p>16:18 <code>&lt;smoser&gt;</code> robjo: that is correct.</p> -<p>16:18 <code>&lt;robjo&gt;</code> so a re-read of the metadata on EC2 delivers no/maybe limited new information</p> -<p>16:18 <code>&lt;smoser&gt;</code> robjo: well, network information is updated.</p> -<p>16:18 <code>&lt;smoser&gt;</code> user-data is only updatable on stop -&gt;` start in ec2</p> -<p>16:18 <code>&lt;robjo&gt;</code> rharper: AFAIK new metadat gets pick up on instance restart</p> -<p>16:19 <code>&lt;rharper&gt;</code> ok</p> -<p>16:19 <code>&lt;robjo&gt;</code> I know the IID also only gets updated on stop-start</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> certainly in Azure that's the case. you have to stop the instance before changing attached network interfaces and then bring instance online again</p> -<p>16:20 <code>&lt;robjo&gt;</code> Yes, in Azure adding network interfaces is not dynamic</p> -<p>16:20 <code>&lt;robjo&gt;</code> meaning cannot happen while an instance is running</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> adding IPs in azure is an online thing, but even azure's network metadata is limited in that it doesn't tell you whether a network interface is static or dynamic. examples here:</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> <a href="https://hackmd.io/aODzXfa_TOikNtYBLt8erA">https://hackmd.io/aODzXfa_TOikNtYBLt8erA</a></p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> #link <a href="https://hackmd.io/aODzXfa_TOikNtYBLt8erA">https://hackmd.io/aODzXfa_TOikNtYBLt8erA</a></p> -<p>16:22 <code>&lt;robjo&gt;</code> Also for Azure there exists the "problem" of accelerated networking, i.e. SR-IOV</p> -<p>16:23 <code>&lt;robjo&gt;</code> when accelerated networking is on the SR-IOV interface gets the same MAC address as the "Synthetic nic"</p> -<p>16:23 <code>&lt;rharper&gt;</code> well, they "solved" it by having the kernel auto bond =/</p> -<p>16:23 <code>&lt;robjo&gt;</code> the SR-IOV interface gets bound to the synthetic nic in the kernel, that was a patch that went into the kernel 6-9 months ago</p> -<p>16:23 <code>&lt;rharper&gt;</code> AFAICT, the sriov device just magically comes and goes as it will</p> -<p>16:24 <code>&lt;rharper&gt;</code> so, one shouldn't worry about the silent bonding ... (I'm being a bit sarcastic here)</p> -<p>16:24 <code>&lt;robjo&gt;</code> yes, but the interface still shows up, so if output from "ip" command is read one has two devices with the same MAC address, only one of which should be configured</p> -<p>16:25 <code>&lt;rharper&gt;</code> we ignore any of the mlx4 driver devices</p> -<p>16:25 <code>&lt;rharper&gt;</code> yes they show up</p> -<p>16:25 <code>&lt;robjo&gt;</code> OK</p> -<p>16:25 <code>&lt;rharper&gt;</code> but the directive we got was to ignore them; and DHCP on the netvsc ones</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> ...so think that's all I had on action items from previous meeting.</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> shall we go to next topic?</p> -<p>16:26 <code>&lt;robjo&gt;</code> And that of course works until Msft gets a better HW deal from Intel or someone else for their network cards ;)</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> heh</p> -<p>16:26 <code>&lt;rharper&gt;</code> robjo: indeed</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> due to a couple vacations and some work travel it's been a slightly slower couple weeks below are the cloud-init changes that have gone in:</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - lxd: Delete default network and detach device if lxd-init created them.</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> (LP: #1776958)</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - openstack: avoid unneeded metadata probe on non-openstack platforms</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> [Chad Smith] (LP: #1776701)</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - stages: fix tracebacks if a module stage is undefined or empty</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> [Robert Schweikert] (LP: #1770462)</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - Be more safe on string/bytes when writing multipart user-data to disk.</p> -<p>16:28 <code>&lt;ubot5&gt;</code> Launchpad bug 1776958 in cloud-init "error creating lxdbr0." [Medium,Fix committed] <a href="https://launchpad.net/bugs/1776958">https://launchpad.net/bugs/1776958</a></p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> (LP: #1768600)</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - Fix get_proc_env for pids that have non-utf8 content in environment.</p> -<p>16:28 <code>&lt;ubot5&gt;</code> Launchpad bug 1776701 in cloud-init "ec2: xenial unnecessary openstack datasource probes during discovery" [High,Fix committed] <a href="https://launchpad.net/bugs/1776701">https://launchpad.net/bugs/1776701</a></p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> (LP: #1775371)</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - tests: fix salt_minion integration test on bionic and later [Chad Smith]</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - tests: provide human-readable integration test summary when --verbose</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> [Chad Smith]</p> -<p>16:28 <code>&lt;ubot5&gt;</code> Launchpad bug 1770462 in cloud-init "Allow empty stages" [Low,Fix committed] <a href="https://launchpad.net/bugs/1770462">https://launchpad.net/bugs/1770462</a></p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - tests: skip chrony integration tests on lxd running artful or older</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> [Chad Smith]</p> -<p>16:28 <code>&lt;ubot5&gt;</code> Launchpad bug 1768600 in cloud-init "UTF-8 support in User Data (text/x-shellscript) is broken" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1768600">https://launchpad.net/bugs/1768600</a></p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - test: add optional --preserve-instance arg to integraiton tests</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> [Chad Smith]</p> -<p>16:28 <code>&lt;ubot5&gt;</code> Launchpad bug 1775371 in cloud-init "cloud-init (18.2) fails on decoding proc1 env" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1775371">https://launchpad.net/bugs/1775371</a></p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - netplan: fix mtu if provided by network config for all rendered types</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> [Chad Smith] (LP: #1774666)</p> -<p>16:28 <code>&lt;ubot5&gt;</code> Launchpad bug 1774666 in netplan.io (Ubuntu Cosmic) "Bond interfaces stuck at 1500 MTU on Bionic" [Undecided,Confirmed] <a href="https://launchpad.net/bugs/1774666">https://launchpad.net/bugs/1774666</a></p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - tests: remove pip install workarounds for pylxd, take upstream fix.</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - subp: support combine_capture argument.</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - tests: ordered tox dependencies for pylxd install [Chad Smith]</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - util: add get_linux_distro function to replace platform.dist</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> [Robert Schweikert] (LP: #1745235)</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> - pyflakes: fix unused variable references identified by pyflakes 2.0.0.</p> -<p>16:28 <code>&lt;ubot5&gt;</code> Launchpad bug 1745235 in cloud-init "distribution detection" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1745235">https://launchpad.net/bugs/1745235</a></p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> thanks again Robert for the contributions here getting cloud-init in order :)</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> we've also just pushed a release of cloud-init tip into Ubuntu Cosmic.</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> so all latest changes are in the development series</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> I think that about wraps it</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> #topc In-progress Development</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> As always, we track ongoing work publicly at</p> -<p>16:32 <code>&lt;blackboxsw&gt;</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:33 <code>&lt;blackboxsw&gt;</code> we've got some cold-plug network rendering handling that will be queued for this week, mgerts is working on enabling cold-plug network rendering support on boot for SmartOS, and there is a followup for Azure to do the same</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> cloud-init squad is going to be setting up an SRU into Xenial, Artful and Bionic this week as well</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> to sync latest qualified cloud-init into those Ubuntu series</p> -<p>16:35 <code>&lt;smoser&gt;</code> blackboxsw: thinking out loud..</p> -<p>16:35 <code>&lt;smoser&gt;</code> if we're going to release 18.3 on thursday</p> -<p>16:35 <code>&lt;smoser&gt;</code> might as well just hold off on sru until then</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> (wait on 18.3 release?)</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> yeha</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> yeah even</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> which brings us to our next topic</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> #topic Cloud-init 18.3 release</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> I hadn't seen any responsed to your email scott to cloud-init@lists.launchpad.net. Does anyone have any feature pressing that we'd like to get into this release</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> estimated release would be Thusday of this week</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> I'd whimsically like to include the azure cold-plug stuff, but that means getting those two branches in shape today for a thorough review/test cycle</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> s/whimsically/opportunitically/</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> heh I give up</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> did we want to pull this in? <a href="https://code.launchpad.net/~paul-meyer/cloud-init/+git/cloud-init/+merge/334989">https://code.launchpad.net/~paul-meyer/cloud-init/+git/cloud-init/+merge/334989</a></p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> If there are any pressing bugs or features that need to be in 18.3 we'd like to see them up for review by Wednesday of this week so that we can cut our upstream release. Feel free to send an email to the list cloud-init@lists.launchpad.net or this channel if your branch needs to get some eyes.</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> we'll SRU 18.3 then into Xenial, Artful and Bionic after a complete round of testing.</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:46 <code>&lt;robjo&gt;</code> :D After 18.3 but before the workshop: <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904</a></p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> Folks are around for further discussion on any cloud-init topics of interest</p> -<p>16:47 <code>&lt;robjo&gt;</code> then maybe at the workshop we can come up with a way to move SLES &amp; openSUSE to sysconfig renderer</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> good topic idea</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> #ACTION rhaper/blackboxsw review <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904</a></p> -<p>16:48 * meetingology rhaper/blackboxsw review <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904</a></p> -<p>17:22 <code>&lt;blackboxsw&gt;</code> thanks again folks. catch you next time.</p> -<p>17:23 <code>&lt;blackboxsw&gt;</code> minutes will be published to the link below</p> -<p>17:23 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>17:23 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-05-29T16:05:00+00:002018-05-29T16:05:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-05-29:/status-2018-05-29.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 29 May at 16:05 &mdash; 17:05 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-05-29-16.05.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-05-29-16.05.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:09.</p> -<h3>Recent Changes …</h3><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 29 May at 16:05 &mdash; 17:05 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-05-29-16.05.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-05-29-16.05.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<p><strong>LINK</strong>: <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a> </p> -<h3>Previous Actions</h3> -<p>The discussion about "Previous Actions" started at 16:09.</p> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:13.</p> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:19.</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="https://cloudinit.readthedocs.io/en/latest/topics/datasources.html">https://cloudinit.readthedocs.io/en/latest/topics/datasources.html</a>?highlight=instance-data#instance-data </li> -</ul> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 16:34.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://trello.com/c/5n5B8x23/802-cloud-init-query-standardized-json-information">https://trello.com/c/5n5B8x23/802-cloud-init-query-standardized-json-information</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/335290">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/335290</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 (118)</li> -<li>dmbaturin (20)</li> -<li>powersj (6)</li> -<li>dpb1 (5)</li> -<li>robjo (5)</li> -<li>ubot5 (4)</li> -<li>smoser (4)</li> -<li>meetingology (3)</li> -<li>rharper (2)</li> -</ul> -<h2>Full Log</h2> -<p>16:05 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status meeting</p> -<p>16:05 <code>&lt;meetingology&gt;</code> Meeting started Tue May 29 16:05:51 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:05 <code>&lt;meetingology&gt;</code> </p> -<p>16:05 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:06 <code>&lt;dpb1&gt;</code> dmbaturin: there will be a time for open questions in this meeting in just a few minutes. :)</p> -<p>16:06 <code>&lt;dpb1&gt;</code> so you will have the right people around</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> welcome folks to another cloud-init community status meeting, today's meeting delayed by one day due to US holiday. Next meeting will be June 11th. same time</p> -<p>16:07 <code>&lt;blackboxsw&gt;</code> I've added an actions topic to this meeting so we can wrap up or carry over any actions discussed last time</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> the topics will be Previous Actions, Recent Changes, In-progress Development, and Office Hours</p> -<p>16:08 <code>&lt;dmbaturin&gt;</code> Oh, cool.</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> As always notes will be posted to the following site</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> welcome dmbaturin good timing. :)</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> #topic Previous Actions</p> -<p>16:09 <code>&lt;dmbaturin&gt;</code> Yeah, I'm just in time it seems. ;)</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> 2 weeks ago we had a couple of followup items that needed some extra review:</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> * ACTION: blackboxsw review distro dection and empty modules list</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> * ACTION: robjo review existing chrony support in master per rharper's work</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> * ACTION: blackboxsw carryover network hotplug vs network maintenance on reboot-only</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> we did get through robjo's branches on distro <em>detection</em> and landed them\</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> and I know our team also discussed a potential approach to network hotplug vs network maintenance to better enable SmartOs folks who want to handle network config across reboots only</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> I think we decided we needed to draw up a quick shared document on a proposal which would allow for maintenance on reboots only vs true hotplug.</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> I'll carry over that action to write up a doc on this and send it to list by the next meeting</p> -<p>16:13 * blackboxsw blackboxsw write up short doc/branch on hotplug versus network maintenance on reboot for comment</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> and I believe robjo from SuSE was able to get through rharper's chrony support branch with a couple comments too</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> so no other actions from last meeting</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> this following content landed in cloud init tip over the last two weeks</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> - Do not use the systemd_prefix macro, not available in this environment</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> [Robert Schweikert]</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> - doc: Add config info to ec2, openstack and cloudstack datasource docs</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> [Chad Smith]</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> - Enable SmartOS network metadata to work with netplan via per-subnet</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> routes [Dan McDonald] (LP: #1763512)</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> - openstack: Allow discovery in init-local using dhclient in a sandbox.</p> -<p>16:14 <code>&lt;ubot5&gt;</code> Launchpad bug 1763512 in cloud-init "DataSourceSmartOS ignores sdc:routes" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1763512">https://launchpad.net/bugs/1763512</a></p> -<p>16:14 <code>&lt;powersj&gt;</code> lol!</p> -<p>16:14 <code>&lt;powersj&gt;</code> welcome back</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> heh looks like I got kicked for the paste :)</p> -<p>16:14 <code>&lt;powersj&gt;</code> blackboxsw: your last message was - openstack: Allow discovery in init-local using dhclient in a sandbox.</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> - tests: Avoid using https in httpretty, improve HttPretty test case.</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 (LP: #1771659)</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 - yaml_load/schema: Add invalid line and column nums to error message</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 [Chad Smith]</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 - Azure: Ignore NTFS mount errors when checking ephemeral drive</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 [Paul Meyer]</p> -<p>16:15 <code>&lt;ubot5&gt;</code> Launchpad bug 1771659 in cloud-init "unittests fail in OpenSuSE 42.3 with httpretty issues" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1771659">https://launchpad.net/bugs/1771659</a></p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> - packages/brpm: Get proper dependencies for cmdline distro.</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 - packages: Make rpm spec files patch in package version like in debs.</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 - tools/run-container: replace tools/run-centos with more generic.</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 - Update version.version_string to contain packaged version. (LP: #1770712)</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 - cc_mounts: Do not add devices to fstab that are already present.</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 [Lars Kellogg-Stedman]</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 - ds-identify: ensure that we have certain tokens in PATH. (LP: #1771382)</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 - tests: enable Ubuntu Cosmic in integration tests [Joshua Powers]</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 - read_file_or_url: move to url_helper, fix bug in its FileResponse.</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 - cloud_tests: help pylint [Ryan Harper]</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 - flake8: fix flake8 errors in previous commit.</p> -<p>16:15 <code>&lt;ubot5&gt;</code> Launchpad bug 1770712 in cloud-init "It would be nice if cloud-init provides full version in logs" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1770712">https://launchpad.net/bugs/1770712</a></p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 - typos: Fix spelling mistakes in cc_mounts.py log messages [Stephen Ford]</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 - tests: restructure SSH and initial connections [Joshua Powers]</p> -<p>16:15 <code>&lt;ubot5&gt;</code> Launchpad bug 1771382 in cloud-init "ds-identify: fails to recognize NoCloud datasource on boot cause it does not have /sbin in $PATH and thus does not find blkid" [Low,Fix committed] <a href="https://launchpad.net/bugs/1771382">https://launchpad.net/bugs/1771382</a></p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> 10:14 - ds-identify: recognize container-other as a container, test SmartOS.</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> ok hopefully we ended on ds-identify</p> -<p>16:16 <code>&lt;dmbaturin&gt;</code> Yes, we did.</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> excellent. sorry for the paste, I'll send this out to cloud-init@lists.canonical.com a day before the next meeting so we don't have to IRC flood here</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> make that cloud-init@lists.launchpad.net</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> also we finished our SRU (stable release update) of cloud-init 18.2.27 to Bionic.</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> Ubuntu Cosmic currently reflects near tip of master 18.2.59</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> ok that's all for Recent Changes</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> anything I'm missing powersj ?</p> -<p>16:19 <code>&lt;powersj&gt;</code> I think you are good</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> We track upstreams progress publicly in trello</p> -<p>16:19 <code>&lt;blackboxsw&gt;</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:20 <code>&lt;blackboxsw&gt;</code> any blue labeled cards are cloud-init core work</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> we have been fixing a couple of bugs raised by our CI infrastructure on newer series of Ubuntu . currently a minor issue with salt minion on Bionic or later, and a couple of unit and integration test race conditions</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> big ticket items for cloud-init in the nearterm are metadata standardization across clouds, so cloud-init scripts/cloud-config template can source these cloud-provided values</p> -<p>16:24 <code>&lt;dmbaturin&gt;</code> Metadata standardization is something I really would like to see, if you need more hands for that, let me know.</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> the standardization of this instance-data will allow folks to script against any standard values provided to cloud-init in the same way on any cloud. Think hostname, fqdn, ip addrs, region name etc.</p> -<p>16:24 <code>&lt;dmbaturin&gt;</code> SSH keys too!</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> definitely dmbaturin I'll point you at a couple branches and what we're thinking</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> this conent will show up in /run/cloud-init/instance-data.json</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloudinit.readthedocs.io/en/latest/topics/datasources.html">https://cloudinit.readthedocs.io/en/latest/topics/datasources.html</a>?highlight=instance-data#instance-data</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> and will also be referenced via jinja template variables</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> and a cloud-init query CLI</p> -<p>16:28 <code>&lt;dmbaturin&gt;</code> The data will be updated whenever a change in the environment is made?</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> Also powersj will be working toward a common library for cloud-testing in the weeks to come which cloud-init integration tests will leverage to drive lxd, ec2, openstack azure etc for a cloud testing</p> -<p>16:29 <code>&lt;dmbaturin&gt;</code> Also, will it be possible to stop cloud-init from doing anything but writing that data and starting an external script to process it?</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> dmbaturin: some of that functionality will be handled in the hotplug work we are starting on. There will be operations that can be triggered by either a hotplug monitor on metadata or by cloud-init's CLI to say query from cache (the instance-data.json file) versus query fresh/update</p> -<p>16:30 <code>&lt;dmbaturin&gt;</code> I see.</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> dmbaturin: cloud-inits init-local or init-network stage is what calls "get_data" on the give datasources to collect and write that data to file. Spawning a script is generally done through runcmd which happens in cloud-init's 'final' stage. Trying to decouple them (and skipping the modules:config stage) is possible by altering /etc/cloud/cloud.cfg in a custom image to specify no modules in a given stage. Though it's not</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> really recommeded as most of the modules only do a quick sanity check to see if they are specifically enabled before trying to do any realy work</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> we try to keep boot time as fast as possible and cut out the fat where we can</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> if that's the concern you had</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> ok I think that's it for In-progress development we can move to office hours for all addtional discussion</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:35 <code>&lt;dmbaturin&gt;</code> No, boot time is not the primary concern here, my concern is how to ensure no module is trying to treat our system as if it was a normal Debian (which either doesn't work or can potentially get the system into an inconsistent state).</p> -<p>16:36 <code>&lt;dmbaturin&gt;</code> I guess if we are having a real meeting, it may be a good idea to formally introduce myself and the project. :)</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> All topics of interest to cloud-init development can be brought up and discussed here. If there are merge proposal that need attention, bugs that need work just bring them up here we should have a few sets of eyes on this channel to discuss and comment</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> sounds good dmbaturin introduce away :)</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> Chad smith, Canonical, one of the maintainers of cloud-init. We have a few others here (some on vacation). powersj rharper smoser dpb1 all canonical as well.</p> -<p>16:38 <code>&lt;dpb1&gt;</code> idk who blackboxsw is</p> -<p>16:38 <code>&lt;dpb1&gt;</code> he might be crazy</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> frequently we have other distribution developers and cloud devs here too (SuSE, RedHat, Microsoft Azure, SmartOS, VMWare )</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> heh, I'm just a bot</p> -<p>16:38 <code>&lt;dmbaturin&gt;</code> So, I'm one of the maintainers of the VyOS project (<a href="http://vyos.io">http://vyos.io</a>). It's a distro for routers and firewalls whose primary goal is to be just like hardware routers, but not tied to any hardware, which includes a single config file and unified CLI with a commit/rollback model, versioning, and cross-checks (e.g. if you try to reference a non-existent NIC in DHCP configuration, commit fails).</p> -<p>16:39 <code>&lt;dpb1&gt;</code> nice to meet you dmbaturin</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> ahh makes sense. So debian-based os kindof, which is why you'd want to lock down what modules run.</p> -<p>16:40 <code>&lt;dmbaturin&gt;</code> We support all major virtualization platforms now in the sense of including all required drivers and utilities, but autoconfiguration on cloud platforms is only supported for EC2 via a custom script, so we are looking to ways to support more clouds, ideally without doing the work that is already done, or at least contributing those general things into something where more people can benegit from it, not just us.</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> alos dmbaturin each config module claims what distro is supported in a distro property, so you could vet what modules you want to run, and only add VyOS to the list of compatible distros. Config modules all live in source at cloudinit/config/cc_*py.</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> but we can discuss that confuig module support (or not) once you dig in to look at supporting VyOS</p> -<p>16:42 <code>&lt;dmbaturin&gt;</code> Yes, I'm thinking how exactly it should be done.</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> dmbaturin: cloud-init's a pretty good choice for getting that cloud-support breadth for free</p> -<p>16:43 * robjo sorry I'm late</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> robjo: sorry for the late change from yesterday's normal meet time</p> -<p>16:43 <code>&lt;dmbaturin&gt;</code> The least intrusive option would be to indeed improve the instance data format, so that we can simply pass it to our own script, which is why I'm all for contributing to it.</p> -<p>16:43 <code>&lt;robjo&gt;</code> blackboxsw: noLnxDistro branch has not yet been merged</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> bah robjo ahh you're right</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> ok looks like you handled all review comments. I'll get it landed today</p> -<p>16:44 <code>&lt;smoser&gt;</code> powersj: <a href="https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/347060">https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/347060</a></p> -<p>16:44 * blackboxsw blackboxsw land <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/336794">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/336794</a> today</p> -<p>16:45 <code>&lt;smoser&gt;</code> you moved that to 'approved' i guess ?</p> -<p>16:45 <code>&lt;smoser&gt;</code> which meant the bot didnt comment (sorry blackboxsw ... interupted)</p> -<p>16:45 <code>&lt;dmbaturin&gt;</code> blackboxsw: Could you point me to the branches were the work on instance data is going on?</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> dmbaturin: here's one stale one I need to get back to this week. for enabling the template reference of instance-data.json content</p> -<p>16:46 <code>&lt;powersj&gt;</code> smoser: ah sorry you are right</p> -<p>16:47 <code>&lt;smoser&gt;</code> powersj: i'm going to land it anyway</p> -<p>16:47 <code>&lt;robjo&gt;</code> also I think emptyStageOK branch should be ready to go</p> -<p>16:47 <code>&lt;powersj&gt;</code> ok</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> hrm digging on the metadata branch.</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> dmbaturin: the trello card I'll be tying branches to is this one</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> #link <a href="https://trello.com/c/5n5B8x23/802-cloud-init-query-standardized-json-information">https://trello.com/c/5n5B8x23/802-cloud-init-query-standardized-json-information</a></p> -<p>16:48 <code>&lt;robjo&gt;</code> and <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904</a> should be on smoser plate</p> -<p>16:49 <code>&lt;robjo&gt;</code> or anyone else who wants to pick it up and get it merged, please</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/335290">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/335290</a></p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> ^ dmbaturin initial template handling thoughts.... I have to create at least 2 branches to standardize datasource class apis to make the metadata content easier to generalize and I can add your launchpad username to the review as I put them up</p> -<p>16:50 <code>&lt;rharper&gt;</code> smoser: re: hostname, yes, that's right; we probably could update the set_hostname docs to mention that detail w.r.t early hostname setting</p> -<p>16:51 <code>&lt;rharper&gt;</code> blackboxsw: sorry to interrupt</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> dmbaturin: what's your launchpad user name? (mine's chad.smith)</p> -<p>16:51 <code>&lt;dmbaturin&gt;</code> blackboxsw: dmbaturin</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> heh.</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> thx</p> -<p>16:51 <code>&lt;dmbaturin&gt;</code> I'm too predictable. ;)</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> yeah, I lost a bet on blackboxsw :)</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> robjo: okay adding that branch too for review/landing</p> -<p>16:51 * blackboxsw land <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904</a></p> -<p>16:52 * blackboxsw land <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/336794">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/336794</a></p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> alright, any other topics or discussions?</p> -<p>16:53 <code>&lt;dmbaturin&gt;</code> Trello is integrated with launchpad?</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> dmbaturin: nope, just easy to use for our agile workflow. And simple to cut-paste links, assign people, drag to different lanes as the work progresses</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> has a lot of github integraiton if you get the right plugins</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> we have some minimal tooling that can talk to lauchpad and inject cards, but that's hand-written, not part of trello product.</p> -<p>16:59 <code>&lt;dmbaturin&gt;</code> I mean, if you add my username there, will I get any notifications about card changes.</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> dmbaturin: I get emails from all trello card moves,changes. let's see</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> I can subscribe you to the card (you want the standardized json stuff?)</p> -<p>17:00 <code>&lt;dmbaturin&gt;</code> Yes.</p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> hrm can't find your user</p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> ahh</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> I think I invited you</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> and added your user to the card so you can watch it progress</p> -<p>17:05 <code>&lt;blackboxsw&gt;</code> ok I think that about wraps up our meeting for today</p> -<p>17:05 <code>&lt;blackboxsw&gt;</code> any parting shots?</p> -<p>17:05 <code>&lt;blackboxsw&gt;</code> I'll post these notes to our github project page</p> -<p>17:05 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>17:05 <code>&lt;blackboxsw&gt;</code> thanks again all</p> -<p>17:05 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-05-14T16:05:00+00:002018-05-14T16:05:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-05-14:/status-2018-05-14.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 14 May at 16:05 &mdash; 17:03 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-05-14-16.05.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-05-14-16.05.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:09.</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><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 14 May at 16:05 &mdash; 17:03 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-05-14-16.05.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-05-14-16.05.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:09.</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>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:19.</p> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 16:29.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://pastebin.ubuntu.com/p/266CyDt9gD/">https://pastebin.ubuntu.com/p/266CyDt9gD/</a> </li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/emptyStageOK">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/emptyStageOK</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/noLnxDistro">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/noLnxDistro</a> </li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bug/1745235">https://bugs.launchpad.net/cloud-init/+bug/1745235</a> </li> -<li><strong>ACTION</strong>: blackboxsw review distro dection and empty modules list</li> -<li><strong>ACTION</strong>: robjo review existing chrony support in master per rharper's work</li> -<li><strong>ACTION</strong>: blackboxsw carryover network hotplug vs network maintenance on reboot-only</li> -</ul> -<h2>Vote results</h2> -<h2>Action items, by person</h2> -<ul> -<li>blackboxsw</li> -<li>blackboxsw review distro dection and empty modules list</li> -<li>blackboxsw carryover network hotplug vs network maintenance on reboot-only</li> -<li>rharper</li> -<li>robjo review existing chrony support in master per rharper's work</li> -<li>robjo</li> -<li>robjo review existing chrony support in master per rharper's work</li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (73)</li> -<li>robjo (14)</li> -<li>ubot5 (9)</li> -<li>meetingology (6)</li> -<li>stanguturi (2)</li> -<li>rharper (1)</li> -</ul> -<h2>Full Log</h2> -<p>16:05 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status meeting</p> -<p>16:05 <code>&lt;meetingology&gt;</code> Meeting started Mon May 14 16:05:28 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:05 <code>&lt;meetingology&gt;</code> </p> -<p>16:05 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> welcome folks to another cloud-init status meeting. This forum is used to communicate the recent changes, current development efforts and host open office hours to help get quick discussion on bugs, branches or features of interest to anyone developing (or consuming) cloud-init.</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> We'll go through a couple of topics as usual (Recent changes, In-progress Development, Office Hours), if there are any additional topics needed just let me know.</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> We track our upstream work publicly on trello. Feel free to participate or ask questions about any feature work that is seen up there if there are concerns.</p> -<p>16:11 <code>&lt;blackboxsw&gt;</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:11 <code>&lt;blackboxsw&gt;</code> We have landed the following work items: beware the paste :)</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> * Completed release of 18.2 to Ubuntu Bionic, Artful, and Xenial</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> * Implement bash completion script for cloud-init command line</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> * Improved Softlayer datasource documentation</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> * net: Depend on iproute2's ip instead of net-tools ifconfig or route</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> * Accept-ra unset by default (LP: #1732002)</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> * Command collect-logs will only include most recent boot's journal (LP: #1766335)</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> * FreeBSD: Invoke growfs on ufs filesystems such that it does not prompt. (LP: #1404745)</p> -<p>16:11 <code>&lt;ubot5&gt;</code> Launchpad bug 1732002 in systemd (Ubuntu) "cloud images in lxc get ipv6 address" [Undecided,New] <a href="https://launchpad.net/bugs/1732002">https://launchpad.net/bugs/1732002</a></p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> * Azure: poll_imds fixes to only report 'ready' state once during pre-provisioning from Joshua Chan (LP: #1765214)</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> * DataSourceSmartOS: fix hang when metadata service is down from Mike Gerdts (LP: #1667735)</p> -<p>16:12 <code>&lt;ubot5&gt;</code> Launchpad bug 1766335 in cloud-init "Running cloud-init collect-logs inside a chroot is not possible" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1766335">https://launchpad.net/bugs/1766335</a></p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> * DataSourceSmartOS: change default fs on ephemeral disk from ext3 to ext4 from Mike Gerdts (LP: #1763511)</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> * pycodestyle: Fix invalid escape sequences in string literals</p> -<p>16:12 <code>&lt;ubot5&gt;</code> Launchpad bug 1404745 in cloud-init "cloud-init's growfs/resize fails with gpart dependency on FreeBSD" [Undecided,Fix committed] <a href="https://launchpad.net/bugs/1404745">https://launchpad.net/bugs/1404745</a></p> -<p>16:12 <code>&lt;ubot5&gt;</code> Launchpad bug 1765214 in cloud-init "Multiple success messages sent to Azure Fabric if reboot occurs during pre-provisioning" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1765214">https://launchpad.net/bugs/1765214</a></p> -<p>16:12 <code>&lt;ubot5&gt;</code> Launchpad bug 1667735 in cloud-init (Ubuntu Trusty) "cloud-init doesn't retry metadata lookups and hangs forever if metadata is down" [Medium,Confirmed] <a href="https://launchpad.net/bugs/1667735">https://launchpad.net/bugs/1667735</a></p> -<p>16:12 <code>&lt;ubot5&gt;</code> Launchpad bug 1763511 in cloud-init (Ubuntu) "DataSourceSmartOS should default to ext4" [Medium,Fix released] <a href="https://launchpad.net/bugs/1763511">https://launchpad.net/bugs/1763511</a></p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> A big thank you to community involvement again. Thanks jocha(Microsoft) and mgerdts(Joyent) for the recent branch work supporting Azure and SmartOS clouds respectively</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> We also went through another round of StableReleaseUpdates for Ubuntu on Xenial and Artful to pull in IBMCloud platform fixes. putting Xenial and artful at 18.2-4-g05926e48-0ubuntu~16.04.2 | ~17.10.2</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> I think that's about it for completed development...</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> There are a couple of items being worked actively at the moment:</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> * SRU of cloud-init tip into bionic (should land today or tomorrow) 18.2-27-g6ef92c98-0ubuntu1~18.04.1</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> * SmartOs datasource detection improvements</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> * Moving OpenStack datasource to get detected earlier at 'local' stange instead of 'network' stage using ephemeral dhcp client</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> * read_file_or_url fixes returing text content in all cases</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> * various upstream bug fixes</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> * powersj: is also investigating a move to a centralized library for our cloud testing.</p> -<p>16:29 <code>&lt;robjo&gt;</code> blackboxsw: w.r.t. Depend on iproute2's ip instead of net-tools ifconfig or route was this a merge of iproute2tools branch? I don't recall seeing a merge notification but am way behind in e-mail</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> think that about captures what upstream is working on. I think we can transition to office hours for ~30 mins for anyone to bring up ideas of interest</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> hi robjo, checking status there</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> I know we landed one branch on that topic</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> robjo: so we had a couple branches to packaging dependencies in ubuntu to call out iproute2 specifically as a hard package dependency.</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> robjo: and the code changes (which took in some of your branch content and review comments) landed in rev 6d48d265a0548a2dc23e587f2a335d4e38e8db90</p> -<p>16:32 <code>&lt;robjo&gt;</code> OK, so I can delete my branch</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> <a href="https://pastebin.ubuntu.com/p/266CyDt9gD/">https://pastebin.ubuntu.com/p/266CyDt9gD/</a></p> -<p>16:34 <code>&lt;robjo&gt;</code> thanks, so we'll get that in 18.3?</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> robjo: yes I think i marked you co-author on that branch and pulled in all your changes to cloudinit/config/cc_disable_ec2_metadata.py</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> 2</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> thanks again for that, sorry for the back and forth as I hadn't seen your original branch.</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> robjo: definitely in 18.3</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> it landed a week or two after the 18.2 cut.</p> -<p>16:35 <code>&lt;stanguturi&gt;</code> @blackboxsw, Can someone please provide inputs for the bug <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538</a> One of our team members has uploaded the necessary log files to the bug.</p> -<p>16:35 <code>&lt;ubot5&gt;</code> Ubuntu bug 1766538 in cloud-init (Ubuntu) "network customization with cloud-init does not work on Ubuntu18.04 Beta2 Server" [Undecided,New]</p> -<p>16:38 <code>&lt;robjo&gt;</code> OK, so lets also revisit some of the other stuff I have floating about as I just did the 18.2 package for openSUSE and SLES and noticed that I am once again scarring a lot of patches :(</p> -<p>16:39 <code>&lt;robjo&gt;</code> blackboxsw: <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/emptyStageOK">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/emptyStageOK</a> should be back in your court, did you get notification?</p> -<p>16:40 <code>&lt;robjo&gt;</code> blackboxsw: <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/noLnxDistro">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/noLnxDistro</a> pending since January this may have some merge conflicts now as I had to fiddle quite a bit with the patch in my package</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> stanguturi: looking</p> -<p>16:41 <code>&lt;robjo&gt;</code> I think rharper is working on a different approach to <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/chrony">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/chrony</a> when can we expect that?</p> -<p>16:42 <code>&lt;robjo&gt;</code> and does rharper account for the fact that ntp has a different service name on different distributions?</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538</a></p> -<p>16:43 <code>&lt;ubot5&gt;</code> Ubuntu bug 1766538 in cloud-init (Ubuntu) "network customization with cloud-init does not work on Ubuntu18.04 Beta2 Server" [Undecided,New]</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/emptyStageOK">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/emptyStageOK</a></p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> ahh robjo hadn't, was on vacation Friday, will grab that/close out today</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/noLnxDistro">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/noLnxDistro</a></p> -<p>16:44 <code>&lt;rharper&gt;</code> robjo: re: ntp/chrony, that's landed, including service names for different distros; I pulled unittests and scenarios from your branch; please look over master and see if we're missing anything from your branch w.r.t use-case/scenario</p> -<p>16:45 <code>&lt;robjo&gt;</code> rharper: OK, if it's landed I can at least throw my branch away, and yes, will take a look at master, I take it this will be another in 18.3 item?</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> stanguturi: ok thanks for the logs on that bug, looks like network config parsing is falling over and OVF datasource isn't being detected <a href="https://pastebin.ubuntu.com/p/qVJxDJWZRV/">https://pastebin.ubuntu.com/p/qVJxDJWZRV/</a></p> -<p>16:47 <code>&lt;stanguturi&gt;</code> @blackboxsw, Oh . Thanks. Will check with him about the test setup and update the bug. Thanks.</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> updated the bug with a comment there</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> thanks stanguturi</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> robjo: correct as well for ntp/chrony, we held off landing it in 18.2 because of risk</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> it was one of the first branches landed after the cut</p> -<p>16:51 <code>&lt;robjo&gt;</code> ok, leaves the <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/noLnxDistro">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/noLnxDistro</a> implementation of distro detection as things I'd like to get resolved, others to be addressed maybe in 2 weeks ;)</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> ok noLnxDistro.... I'm updating the commit comment robjo to the trailing LP: #<code>&lt;bug_id&gt;</code></p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> claiming a review slot on that now</p> -<p>16:53 <code>&lt;blackboxsw&gt;</code> good unit test coverage, thanks for that</p> -<p>16:54 <code>&lt;robjo&gt;</code> np</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> ok this can be reviewed today, not sure if why we don't already have a get_linux_distro utility somewhere, but I'll poke around today for context</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> ahh ahh, thanks for the bug robjo ok</p> -<p>16:56 <code>&lt;robjo&gt;</code> the context is that the Python implementation is going away and has been deprecated</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/+bug/1745235">https://bugs.launchpad.net/cloud-init/+bug/1745235</a></p> -<p>16:56 <code>&lt;ubot5&gt;</code> Ubuntu bug 1745235 in cloud-init "distribution detection" [Undecided,New]</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> thanks again</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> changing that status and will help you get that landed</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> good one</p> -<p>16:58 <code>&lt;robjo&gt;</code> OK, blackboxsw is on the hook for two things this week ;) distro detection and the empty modules list</p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> #action blackboxsw review distro dection and empty modules list</p> -<p>16:58 * meetingology blackboxsw review distro dection and empty modules list</p> -<p>16:58 * robjo on the hook to look at chrony support in master and report back to rharper</p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> #action robjo review existing chrony support in master per rharper's work</p> -<p>16:58 * meetingology robjo review existing chrony support in master per rharper's work</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> official now :)</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> now if I only reviewed previous meeting's action items.... checking now</p> -<p>17:00 <code>&lt;blackboxsw&gt;</code> 16:51 <code>&lt;blackboxsw&gt;</code> #action blackboxsw to have discussions w/ team on datasource maintaining network on each reboot per <a href="https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712">https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712</a></p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> ok per last meeting, we have held a couple of discussions on hotplug vs. maintaining network only on reboot. on first blush it looks like we'd need to have these mutually exclusive, but we are just started to iron our what we want to do for our initial hotplug support in cloud-init and have to have a followup discussion about how to support both approaches</p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> #action blackboxsw carryover network hotplug vs network maintenance on reboot-only</p> -<p>17:02 * meetingology blackboxsw carryover network hotplug vs network maintenance on reboot-only</p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> well that was the only action item from last meeting looks like</p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> ok I think that wraps up today's meeting.</p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> any other parting shots folks?</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> Thanks again for your time. It's always a pleasure.</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> Next meeting two weeks, same bat time...</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-04-30T16:04:00+00:002018-04-30T16:04:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-04-30:/status-2018-04-30.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 30 Apr at 16:04 &mdash; 17:14 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-04-30-16.04.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-04-30-16.04.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:07.</p> -<h3>#cloud-init Reviews: <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a> | Meeting …</h3><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 30 Apr at 16:04 &mdash; 17:14 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-04-30-16.04.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-04-30-16.04.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:07.</p> -<h3>#cloud-init Reviews: <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting: Monday 5/14 16:00 UTC | cloud-init 18.2 released (03/28/2018)</h3> -<p>The discussion about "#cloud-init Reviews: <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting: Monday 5/14 16:00 UTC | cloud-init 18.2 released (03/28/2018)" started at 16:08.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://jenkins.ubuntu.com/server/job/cloud-init-integration-proposed-b/">https://jenkins.ubuntu.com/server/job/cloud-init-integration-proposed-b/</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~cloud-init-dev/cloud-init/+git/cloud-init/+ref/master/+activereviews">https://code.launchpad.net/~cloud-init-dev/cloud-init/+git/cloud-init/+ref/master/+activereviews</a> </li> -</ul> -<h3>In-progresss Development</h3> -<p>The discussion about "In-progresss Development" started at 16:21.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1767412">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1767412</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~jocha/cloud-init/+git/cloud-init/+merge/344192">https://code.launchpad.net/~jocha/cloud-init/+git/cloud-init/+merge/344192</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/344181">https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/344181</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/344198">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/344198</a> </li> -</ul> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 16:31.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712">https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712</a> </li> -<li><strong>LINK</strong>: <a href="https://github.com/SUSE/Enceladus/tree/master/cloud-netconfig">https://github.com/SUSE/Enceladus/tree/master/cloud-netconfig</a> </li> -<li><strong>ACTION</strong>: blackboxsw to have discussions w/ team on datasource maintaining network on each reboot per <a href="https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712">https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712</a></li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538</a> </li> -<li><strong>LINK</strong>: <a href="https://hackmd.io/M1Tae41PQBC7a9qMsurTJw">https://hackmd.io/M1Tae41PQBC7a9qMsurTJw</a>?both </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>Action items, by person</h2> -<ul> -<li>blackboxsw</li> -<li>blackboxsw to have discussions w/ team on datasource maintaining network on each reboot per <a href="https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712">https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712</a></li> -<li>mgerdts</li> -<li>blackboxsw to have discussions w/ team on datasource maintaining network on each reboot per <a href="https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712">https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712</a></li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (113)</li> -<li>mgerdts (21)</li> -<li>ubot5 (12)</li> -<li>akik (5)</li> -<li>stanguturi (4)</li> -<li>meetingology (4)</li> -<li>robjo (3)</li> -</ul> -<h2>Full Log</h2> -<p>16:04 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status meeting</p> -<p>16:04 <code>&lt;meetingology&gt;</code> Meeting started Mon Apr 30 16:04:15 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:04 <code>&lt;meetingology&gt;</code> </p> -<p>16:04 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:04 <code>&lt;blackboxsw&gt;</code> hi folks, sorry for the mis-representation of when our cloud-init status meeting date. It's time for another episode/update of the happenings in cloud-init.</p> -<p>16:05 <code>&lt;blackboxsw&gt;</code> Next meeting will be in two weeks: May 7th</p> -<p>16:05 <code>&lt;blackboxsw&gt;</code> at 16:00 UTC</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> The last couple weeks on the upstream side of the house has been a big push to get testing and stability into master for the Ubuntu Bionic release freeze</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> ... I'd better start with the topic</p> -<p>16:07 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:07 <code>&lt;blackboxsw&gt;</code> The last couple weeks on the upstream side of the house has been a big push to get testing and stability into master for the Ubuntu Bionic release freeze.</p> -<p>16:07 <code>&lt;robjo&gt;</code> May 7th would be 1 week from today that should be May 14th</p> -<p>16:07 <code>&lt;blackboxsw&gt;</code> robjo: gah, I did it again. Thank you... glad someone's listening. Next cloud-init status meeting Monday May 14th 16:00 UTC</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> #topic #cloud-init Reviews: <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a> | Meeting minutes: <a href="https://goo.gl/mrHdaj">https://goo.gl/mrHdaj</a> | Next status meeting: Monday 5/14 16:00 UTC | cloud-init 18.2 released (03/28/2018)</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> ok topic agrees in channel now, so I don't botch it at the end of meeting</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> Along with a blitz for stability in Bionic the following changes have been shepherded into tip of master</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> - Add reporting events and log_time around early source of blocking time</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> [Ryan Harper]</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> - IBMCloud: recognize provisioning environment during debug boots.</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> (LP: #1767166)</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> - net: detect unstable network names and trigger a settle if needed</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> [Ryan Harper] (LP: #1766287)</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> - IBMCloud: improve documentation in datasource.</p> -<p>16:09 <code>&lt;ubot5&gt;</code> Launchpad bug 1767166 in cloud-init (Ubuntu) "IBMCloud datasource does not recognize provisioning in debug mode." [Medium,Confirmed] <a href="https://launchpad.net/bugs/1767166">https://launchpad.net/bugs/1767166</a></p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> - sysconfig: dhcp6 subnet type should not imply dhcpv4 [Vitaly Kuznetsov]</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> - packages/debian/control.in: add missing dependency on iproute2.</p> -<p>16:09 <code>&lt;ubot5&gt;</code> Launchpad bug 1766287 in cloud-init (Ubuntu) "18.04 minimal images on GCE intermittently fail to set up networking " [Undecided,In progress] <a href="https://launchpad.net/bugs/1766287">https://launchpad.net/bugs/1766287</a></p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> (LP: #1766711)</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> - DataSourceSmartOS: add locking of serial device.</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> [Mike Gerdts] (LP: #1746605)</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> - DataSourceSmartOS: sdc:hostname is ignored [Mike Gerdts] (LP: #1765085)</p> -<p>16:09 <code>&lt;ubot5&gt;</code> Launchpad bug 1766711 in cloud-init (Ubuntu Bionic) "cloud-init missing dependency on iproute2" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1766711">https://launchpad.net/bugs/1766711</a></p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> - DataSourceSmartOS: list() should always return a list</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> [Mike Gerdts] (LP: #1763480)</p> -<p>16:09 <code>&lt;ubot5&gt;</code> Launchpad bug 1746605 in cloud-init "DataSourceSmartOS needs locking" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1746605">https://launchpad.net/bugs/1746605</a></p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> - schema: in validation, raise ImportError if strict but no jsonschema.</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> - set_passwords: Add newline to end of sshd config, only restart if</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> updated. (LP: #1677205)</p> -<p>16:09 <code>&lt;ubot5&gt;</code> Launchpad bug 1765085 in cloud-init "DataSourceSmartOS ignores sdc:hostname" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1765085">https://launchpad.net/bugs/1765085</a></p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> - pylint: pay attention to unused variable warnings.</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> - doc: Add documentation for AliYun datasource. [Junjie Wang]</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> - Schema: do not warn on duplicate items in commands. (LP: #1764264)</p> -<p>16:09 <code>&lt;ubot5&gt;</code> Launchpad bug 1763480 in cloud-init "DataSourceSmartOS list() should always return a list" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1763480">https://launchpad.net/bugs/1763480</a></p> -<p>16:09 <code>&lt;ubot5&gt;</code> Launchpad bug 1677205 in cloud-init "cloud-init eats final EOL of sshd_config" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1677205">https://launchpad.net/bugs/1677205</a></p> -<p>16:09 <code>&lt;ubot5&gt;</code> Launchpad bug 1764264 in juju 2.3 "bionic cloud-init 18.2 WARNING Juju's 'runcmd' stanza" [High,Triaged] <a href="https://launchpad.net/bugs/1764264">https://launchpad.net/bugs/1764264</a></p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> the general theme has been: new IBMCloud datasource support for cloud-init, SmartOS datasource work by mgerdts, and some json schema improvements</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> so background on IBM, is that their support used to be ConfigDrive based datasource only, but there is now some additional support for different IBM boot/provisioning stages, hence a new datasource that can support different boot modew</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> *boot modes</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> over the last two weeks we've landed an SRU into xenial and artful: 18.2-4-g05926e48-0ubuntu1~16.04.1 and bionic sits at 18.2-14-g6d48d265-0ubuntu1</p> -<p>16:15 <code>&lt;mgerdts&gt;</code> On the SmartOS side, my changes are driven by our adoption of bhyve (moving away from kvm/qemu). qemu provides a dhcp server VMs could fall back to if could-init was missing or misbehaving. bhyve doesn't have that, so I've been working on getting cloud-init to be more stable with the bhyve serial metadata service.</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> Also, to our continuous integration on jenkins we now have an additional test for proposed packages in ubuntu for the bionic release to make sure ubuntu doesn't break across pending upgrades</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> #link <a href="https://jenkins.ubuntu.com/server/job/cloud-init-integration-proposed-b/">https://jenkins.ubuntu.com/server/job/cloud-init-integration-proposed-b/</a></p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> that integration tests hits the suite of platforms lxd, kvm and ec2</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> excellent mgerdts, and thanks for the blitz on these branches</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> looks like there are a few still in our review queue that we'll be able to get through once the dust settles on the bionic release (which should be this week)</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~cloud-init-dev/cloud-init/+git/cloud-init/+ref/master/+activereviews">https://code.launchpad.net/~cloud-init-dev/cloud-init/+git/cloud-init/+ref/master/+activereviews</a></p> -<p>16:19 <code>&lt;mgerdts&gt;</code> Is now the right time to discuss bug 1765801, or is that later?</p> -<p>16:19 <code>&lt;ubot5&gt;</code> bug 1765801 in cloud-init "network should be optionally reconfigured on every boot" [Undecided,Confirmed] <a href="https://launchpad.net/bugs/1765801">https://launchpad.net/bugs/1765801</a></p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> I think over the last 2 weeks there have been a couple of requests in channel for how someone goes about getting newer cloud init into RHEL7, if anyone on the line today knows the contact point or process for that it'd be helpful. larsks doesn't seem to be around</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> mgerdts: probably in about 10 mins. thanks for brining it up</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> hopefully less.</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> ok I think that's it for recent changes, next topic (in-progress dev, then office hours (and bug discussion))</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> #topic In-progresss Development</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> We'll make this one short:</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> for ubuntu : bionic just went feature freeze last week, our team has a couple of IBM-related cheanges that we are pulling together for a quick SRU into xenial/artful to handle upgrade path from configdrive -&gt;` IBMCloud that we are working on the beginning of this week</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> we are also trying to wrap up validation of a Bionic SRU per the following bug</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1767412">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1767412</a></p> -<p>16:22 <code>&lt;ubot5&gt;</code> Launchpad bug 1767412 in cloud-init (Ubuntu Bionic) "SRU cloud-init 18.2-27-g6ef92c98-0ubuntu1" [Medium,Fix committed]</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> which grabs a number of the updates I listed in the last topic</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> since Ubuntu tends to sync all changes from tip into each release stream</p> -<p>16:23 <code>&lt;mgerdts&gt;</code> Is there any chance the SmartOS changes can piggy back on that IBM SRU</p> -<p>16:24 <code>&lt;mgerdts&gt;</code> asked too soon - I see they are mentioned in that bug.</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> mgerdts: no worries. good ask. probably not for this IBM SRU into xenial/artful which is going to be an exception to our update rule and only be a single cherry pick, but planning a folllowup SRU in about 2 weeks which will pull all changes from tip into artful/xenial/bionic/chunky releases</p> -<p>16:25 <code>&lt;mgerdts&gt;</code> ok</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> the cherry pick is to fasttrack it for IBM into xenial with minimal risk.</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> and we want to pull in all your changes if we can (and perform additional validation)</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> so the next SRU is our target</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> Also inprogress is some more Azure work on pre-provisioning that should land shortly:</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~jocha/cloud-init/+git/cloud-init/+merge/344192">https://code.launchpad.net/~jocha/cloud-init/+git/cloud-init/+merge/344192</a></p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> as well as some builddeb fixes and network configuration printout fixes from smoser</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> smoser and rharper also worked out some issues on specific google regions where cloud-init was getting hit by a race condition. Cloud-init started up before the kernel/udev was able to rename network devices to stable names like ens4 etc, so cloud-init's network configuration written ended up breaking because it represented devices like eth0 etc.</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> there are a couple of branches in flight to fix this issue:</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/344181">https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/344181</a></p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/344198">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/344198</a></p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> ok I think that's it for in-progress work. So we'll head to office hours so we can chat bugs, branches reviews etc</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> We'll be hanging out here for anyone who wants more eyes on a review, feature discussions or bug triage....</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> well, some of us will be :) a couple of us are at a feature planning conference for the week.</p> -<p>16:33 <code>&lt;mgerdts&gt;</code> In <a href="https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712">https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712</a> smoser said that he was concerned about how this would interact with eventual network hotplug</p> -<p>16:34 <code>&lt;mgerdts&gt;</code> There doesn't seem to be a timeline for network hotplug and the lack of network autoreconfig on reboot is has popped up a couple times in the past week. This is just with a couple early adopters and internal users.</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712">https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712</a></p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> just to track it in the meeting</p> -<p>16:35 <code>&lt;mgerdts&gt;</code> So coming up with some mechanism to make this work soon is pretty important to us.</p> -<p>16:35 <code>&lt;mgerdts&gt;</code> gotcha, will be sure to do that in the future.</p> -<p>16:35 * blackboxsw reads up on that link</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> no worries, I'm pedantic :)</p> -<p>16:36 <code>&lt;mgerdts&gt;</code> That's how you got chosen to run the meeting, I suppose. :)</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> yeah network hotplug will have a long tail as far as feature develpment (agreed). I believe it's on our charter for this next quarter. but that's what is being discussed this week</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> heh on meeting comment ;) too true</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> so mgerdts your branch allows metadata to set maintain_network to allow cloud-init to control network configuration each reboot with a True value</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> ?</p> -<p>16:39 <code>&lt;mgerdts&gt;</code> yes</p> -<p>16:39 <code>&lt;mgerdts&gt;</code> if it's not set to true in our metadata, the traditional behavior stays.</p> -<p>16:40 <code>&lt;mgerdts&gt;</code> That is, in the default path, any customization that someone does in the guest will not get whacked.</p> -<p>16:41 <code>&lt;robjo&gt;</code> cloud-netconfig handles hotplug <a href="https://github.com/SUSE/Enceladus/tree/master/cloud-netconfig">https://github.com/SUSE/Enceladus/tree/master/cloud-netconfig</a> contributions for other distros welcome</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> nice reference robjo</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> #link <a href="https://github.com/SUSE/Enceladus/tree/master/cloud-netconfig">https://github.com/SUSE/Enceladus/tree/master/cloud-netconfig</a></p> -<p>16:43 <code>&lt;robjo&gt;</code> We currently have no GCE specific information but that is easy enough to add. The GCE guest environment handles this and we use the GCE guest environment code in our images in GCE</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> mgerdts: so can a user turn off that feature on an instance once they've already deployed, or is it create-time only</p> -<p>16:43 <code>&lt;mgerdts&gt;</code> It can be flipped at any time, in the current implementation.</p> -<p>16:44 <code>&lt;mgerdts&gt;</code> current implementation is only in a development branch</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> mgerdts: the only things I can see being an issue with the maintain network in cloud-init is that we are adding the cost of another function call &amp;&amp; metdata dict parse to look for a signal about maintaining the network. I agree that cloud-init having granularity between is_new_instance vs just re-do network, is something that cloud-init should have.</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> we probably need to discuss this too with rharper about what short-term vision we can get to while we await our network hotplug support in cloud-init proper</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> I'd tend to agree that waiting on fully baked hotplug solution is probably too long in this case</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> as that runway will be at least 2 months I'd think</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> ok, I'll take an action item to resolve this if we can by next meeting</p> -<p>16:50 <code>&lt;mgerdts&gt;</code> Not only that, but support for it will likely require changes in the host as well. We tend not to do host updates very often, so it could be a year or more after the feature is available in images before it will be useful.</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> #action blackboxsw to have discussions w/ team on datasource maintaining network on each reboot per <a href="https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712">https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712</a></p> -<p>16:51 * meetingology blackboxsw to have discussions w/ team on datasource maintaining network on each reboot per <a href="https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712">https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712</a></p> -<p>16:51 <code>&lt;mgerdts&gt;</code> thanks</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> good topic.</p> -<p>16:52 <code>&lt;mgerdts&gt;</code> Is there another place that is good to catch up with larsks or other people that can offer guidance on for redhat/centos?</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> let's see, anything else folks want to chat about? stagnant reviews, bugs of interest etc?</p> -<p>16:53 * blackboxsw looks at the last cloud-init community summit attendees list to see if rhel folks have another contacts that was supposed to replace larsks</p> -<p>16:53 <code>&lt;stanguturi&gt;</code> Chad, Is it possible that someone from cloud-init team can take a look at <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538</a></p> -<p>16:53 <code>&lt;ubot5&gt;</code> Launchpad bug 1766538 in cloud-init (Ubuntu) "network customization with cloud-init does not work on Ubuntu18.04 Beta2 Server" [Undecided,Confirmed]</p> -<p>16:55 <code>&lt;blackboxsw&gt;</code> mgerts, ryan mccabe is a potential contact too, looks like he's not here either today.</p> -<p>16:56 <code>&lt;mgerdts&gt;</code> ok, thanks</p> -<p>16:56 <code>&lt;blackboxsw&gt;</code> hrm, yeah not certain what mechanism is used to get cloud-init updated into RedHat mgerdts. Maybe filing a redhat bug about the request</p> -<p>16:57 <code>&lt;blackboxsw&gt;</code> mgerdts: <a href="https://bugzilla.redhat.com/">https://bugzilla.redhat.com/</a> maybe</p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> stanguturi: yes we can, we are trying to sort and understand any bugs against Bionic that we can</p> -<p>16:58 <code>&lt;mgerdts&gt;</code> ok, I can try that.</p> -<p>16:58 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538</a></p> -<p>16:58 <code>&lt;ubot5&gt;</code> Launchpad bug 1766538 in cloud-init (Ubuntu) "network customization with cloud-init does not work on Ubuntu18.04 Beta2 Server" [Undecided,Confirmed]</p> -<p>16:58 <code>&lt;stanguturi&gt;</code> blackboxsw: Thanks</p> -<p>17:00 <code>&lt;blackboxsw&gt;</code> stanguturi: ok, so this is netplan + cloud-init related right?</p> -<p>17:00 <code>&lt;stanguturi&gt;</code> blackboxsw: Yes.</p> -<p>17:01 <code>&lt;akik&gt;</code> what does network hotplug mean in cloud-init context?</p> -<p>17:02 * blackboxsw tries to remember what vmware datasource does, (like writing files direct to network /etc/network/interfaces.d)</p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> akik: <a href="https://hackmd.io/M1Tae41PQBC7a9qMsurTJw">https://hackmd.io/M1Tae41PQBC7a9qMsurTJw</a>?both is a shared document for comment on hotplug in cloud-init</p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> #link <a href="https://hackmd.io/M1Tae41PQBC7a9qMsurTJw">https://hackmd.io/M1Tae41PQBC7a9qMsurTJw</a>?both</p> -<p>17:03 * blackboxsw looks to see if there was a better doc hrm</p> -<p>17:03 <code>&lt;stanguturi&gt;</code> blackboxsw: Oh. But in the case of netplan, why does cloud-init remembers?</p> -<p>17:04 <code>&lt;akik&gt;</code> blackboxsw: does it mean that cloud-init stays running, waiting for new network interfaces to appear?</p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> akik: right, it would mean that you wouldn't have to reboot cloud-init if devices get added at a later time (post-boot)</p> -<p>17:05 <code>&lt;blackboxsw&gt;</code> cloud-init would listen to some sort of event channel and react, re-write, and apply network config to add new devices</p> -<p>17:06 <code>&lt;akik&gt;</code> would it do the same thing as you could do with ansible or puppet? sorry i'm trying to understand why you would do it with cloud-init</p> -<p>17:08 <code>&lt;blackboxsw&gt;</code> akik: you would try to do it with cloud-init if you didn't want to rely on additional configuration management solutions if the only thing you needed was network config to reflect reality (not full system configuration and system automation)</p> -<p>17:09 * blackboxsw has more puppet/chef background than ansible.</p> -<p>17:09 <code>&lt;blackboxsw&gt;</code> cloud-init does currently detect and write network configuration based on what the user/cloud-metadata tell us is the proper config for the instance</p> -<p>17:10 <code>&lt;akik&gt;</code> i only thought of cloud-init to do the initial configuration</p> -<p>17:10 <code>&lt;blackboxsw&gt;</code> so it would follow that if the metadata could dynamically tell the instance that network config has changed, cloud-init should probably try to react to that to fix the config to match the updated network configuration</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> akik: correct. cloud-init current only handle initial boot config and leaves the rest up whatever mechanism someone uses to update detailed config after that boot</p> -<p>17:11 <code>&lt;akik&gt;</code> ok thanks</p> -<p>17:12 <code>&lt;blackboxsw&gt;</code> akik: and we'd make that feature configurable (handle hotplug:True/False) so if users have other services handling hotplug cloud-init wouldn't collide</p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> ok I think we're hitting the end of office hours. please feel free to continue discussion, we all poke around here throughout the day as our primary means of communication</p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> thanks robjo akik stanguturi and mgerdts for the lively discussion</p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> stanguturi: I'll dig up more info on that bug today</p> -<p>17:13 <code>&lt;mgerdts&gt;</code> thank you</p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> as always notes will be here</p> -<p>17:14 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io/">https://cloud-init.github.io/</a></p> -<p>17:14 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-04-16T16:01:00+00:002018-04-16T16:01:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-04-16:/status-2018-04-16.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 16 Apr at 16:01 &mdash; 18:11 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-04-16-16.01.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-04-16-16.01.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent-changes</h3> -<p>The discussion about "Recent-changes" started at 16:04.</p> -<h3>In-progresss Development</h3> -<p>The discussion about "In-progresss Development" started at …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 16 Apr at 16:01 &mdash; 18:11 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-04-16-16.01.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-04-16-16.01.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent-changes</h3> -<p>The discussion about "Recent-changes" started at 16:04.</p> -<h3>In-progresss Development</h3> -<p>The discussion about "In-progresss Development" started at 16:11.</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="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1759406">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1759406</a> </li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/bugs/1570997">https://bugs.launchpad.net/bugs/1570997</a> </li> -<li><strong>LINK</strong>: <a href="https://trello.com/c/JVaXSfpo/749-eol-fix-for-ssh-file">https://trello.com/c/JVaXSfpo/749-eol-fix-for-ssh-file</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/343123">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/343123</a> </li> -</ul> -<h3>Office Hours (next ~30 mins)</h3> -<p>The discussion about "Office Hours (next ~30 mins)" started at 16:23.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bug/1667735">https://bugs.launchpad.net/cloud-init/+bug/1667735</a> implements proper protocol negotiation over the serial port. The lack of this has caused problems with KVM at times too.</li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bug/1746605">https://bugs.launchpad.net/cloud-init/+bug/1746605</a> adressess times when cloud-init and other software may be trying to use the metadata serial port at the same time. This is purely a bug fix.</li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bug/1763480">https://bugs.launchpad.net/cloud-init/+bug/1763480</a> makes it so that cloud-init doesn't stack trace and exit when there is no customer_metadata. This is an unlikely case, but something that is hit when you are testing things that don't need ssh keys, etc.</li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bug/1763512">https://bugs.launchpad.net/cloud-init/+bug/1763512</a> finishes off the partial implementation of sdc:routes support. Previously, we didn't publish the required information to VMs, so it is fair to consider this a new feature.</li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1763511">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1763511</a> is probably the most incompatible change. New ephemeral disks will get ext4 instead of ext3, which is needed for larger disks that seem to be getting more common.</li> -</ul> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (54)</li> -<li>smoser (17)</li> -<li>rharper (13)</li> -<li>mgerdts (10)</li> -<li>ubot5` (10)</li> -<li>cyphermox (3)</li> -<li>meetingology (3)</li> -<li>dpb1 (1)</li> -</ul> -<h2>Full Log</h2> -<p>16:01 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status meeting</p> -<p>16:01 <code>&lt;meetingology&gt;</code> Meeting started Mon Apr 16 16:01:49 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:01 <code>&lt;meetingology&gt;</code> </p> -<p>16:01 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:02 <code>&lt;rharper&gt;</code> o/</p> -<p>16:03 <code>&lt;blackboxsw&gt;</code> Hi folks, welcome to cloud-init's bi-weekly status meeting. Feel free to interject at any time or bring up branches/bugs/questions over the next 30-60 mins. We'll have a number of folks around to get eyes and/or keyboards onto any problems.</p> -<p>16:03 <code>&lt;dpb1&gt;</code> o/</p> -<p>16:04 <code>&lt;blackboxsw&gt;</code> As always we'll go through the following topics (feel free to suggest others): Recent-changes, In-progress Development, and ~30 mins Office Hours)</p> -<p>16:04 <code>&lt;blackboxsw&gt;</code> #topic Recent-changes</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> a quick rundown of the hi level changes landed:</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> Prune integration test artifacts</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> Add support for LXD 3.0, fix pylxd integration test dependency</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> Fix Ubuntu proposed integration test CI job</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> Fix ec2 validation of instance-data.json network info</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> Do not retry optional userdata on 404 (LP: #1702160)</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> Add explicit cloud-init package dependency on isc-dhcp-client (LP: #1759307)</p> -<p>16:06 <code>&lt;ubot5</code>&gt;` Launchpad bug 1702160 in cloud-init "OpenStack datasource should not retry user-data on 404" [Medium,Fix released] <a href="https://launchpad.net/bugs/1702160">https://launchpad.net/bugs/1702160</a></p> -<p>16:06 <code>&lt;ubot5</code>&gt;` Launchpad bug 1759307 in cloud-init (Ubuntu) "missing dependency on isc-dhcp-client (dhclient)" [Medium,Fix released] <a href="https://launchpad.net/bugs/1759307">https://launchpad.net/bugs/1759307</a></p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> additionally from most recent commits we have:</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> tools: Fix make-tarball cli tool usage for development</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> renderer: support unicode in render_from_file.</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> Implement ntp client spec with auto support for distro selection</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> Apport: add Brightbox, IBM, LXD, and OpenTelekomCloud to list of clouds.</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> tests: fix ec2 integration network metadata validation</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> tests: fix integration tests to support lxd 3.0 release</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> correct documentation to match correct attribute name usage.</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> cc_resizefs, util: handle no /dev/zfs</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> Last week rharper found and fixed a regression in zfs resize behavior that was blocking our ubuntu SRU</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> We have uploaded those fixes, as well as rharper's ntp spec changes (which should incorporate a number of robjo's opensuse/sles needs too)</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> anything else notable that I'm missing gentlemen?</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> If not, I'll jump to in-progress development</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> #topic In-progresss Development</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> So, on the ubuntu side of the house we are about to approve the cloud-init 18.2 SRU (Stable release update) into xenial and artful. Just one more validation run and we should be good to see 18.2.4 on xenial, artful. Ubuntu Bionic is already a few commits beyond that.</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> On Ubuntu as well we are beating the drop to the Bionic LTS (Long term release) feature/bug freeze.</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> This week marks the last week for use to get fixes into Bioinic images before that release is cut.</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> so we'll be heads down on any Bionic-specific changes that need to get in.</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> Feel free to checkout our trello board @</p> -<p>16:14 <code>&lt;blackboxsw&gt;</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:15 <code>&lt;blackboxsw&gt;</code> we track all tasks we are working on in public view there so if there are any questions you can ping one of us here about our development efforts</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> additional tasks that are in flight: bash-autocompletion for cloud-init CLI (rhaper). dropping ifconfig and route in favor of 'ip' (bbsw), and moving openstack datasource to cloud-init's local stage</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> (smoser)</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> also a couple of bugs to fix such as #1570997</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1759406">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1759406</a></p> -<p>16:17 <code>&lt;ubot5</code>&gt;` Ubuntu bug 1759406 in cloud-init (Ubuntu) "sru cloud-init (17.2-35-gf576b2a2-0ubuntu1~16.04.1 update to 18.2-4-g05926e48-0ubuntu1)" [Medium,Confirmed]</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> oops paste fail:</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/bugs/1570997">https://bugs.launchpad.net/bugs/1570997</a></p> -<p>16:17 <code>&lt;ubot5</code>&gt;` Ubuntu bug 1570997 in ssh-import-id (Ubuntu Xenial) "fail if HOME environment variable is not set" [Low,Fix committed]</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> I think that about wraps in-progress development, anything else that should be noted smoser rharper ?</p> -<p>16:18 <code>&lt;rharper&gt;</code> I think you covered it</p> -<p>16:18 <code>&lt;smoser&gt;</code> ssh-import-id is not relally at all related to cloud-init</p> -<p>16:19 <code>&lt;smoser&gt;</code> thanks blackboxsw</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> oops grabbed the wrong one, was thinking about this card</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #link <a href="https://trello.com/c/JVaXSfpo/749-eol-fix-for-ssh-file">https://trello.com/c/JVaXSfpo/749-eol-fix-for-ssh-file</a></p> -<p>16:19 <code>&lt;smoser&gt;</code> right.</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> also of note, in some of our SRU testing we found time-tracking gaps in cloud-init analyze tracking on Azure. rharper put of a logging tracker fix to avoid those tracking gaps</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/343123">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/343123</a></p> -<p>16:21 <code>&lt;smoser&gt;</code> i'll point out one thing i just finished up with...</p> -<p>16:22 <code>&lt;smoser&gt;</code> for testing ubuntu, the <a href="https://github.com/cloud-init/ubuntu-sru/">https://github.com/cloud-init/ubuntu-sru/</a> has 'get-proposed-cloudimg' and 'lxc-proposed-snapshot'</p> -<p>16:22 <code>&lt;smoser&gt;</code> which now work more like each other.l and can do more than just upgrade cloud-init.</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> thanks smoser. Great tools to quicken dev-test cycles and make cloud-init development easier. That wraps up what we've been up to. We can probably move to the open forum for any discussions folks want to have</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 mins)</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> We'll be hanging out here for anyone who wants more eyes on a review, feature discussions or bug triage....</p> -<p>16:28 <code>&lt;smoser&gt;</code> mgerdts: i'm poking at the branch i think i shoudl be able to get something.</p> -<p>16:29 <code>&lt;mgerdts&gt;</code> I'm working on a bunch of fixes for things that have turned up on bhyve with SmartOS. Since we are looking to transition from KVM to bhyve, we will need to provide updates at least as far back as xenial and probably trusty. Is the process for this any more complicated than get the fixes in master, then cherry-pick the fixes into branches?</p> -<p>16:29 <code>&lt;mgerdts&gt;</code> thanks @smoser</p> -<p>17:09 <code>&lt;rharper&gt;</code> mgerdts: we preferrer not to cherry; rather we release master back to xenial via our SRU (Stable Release Update) process; however, we spend a lot of effort to not modify existing behavior on prevlous SRU releases; so if the changes to support bhyve can be done in a compatible way (working with either) that'd be best; worst-case, we patch in release specific bahvior into the release branch.</p> -<p>17:13 <code>&lt;mgerdts&gt;</code> Pretty much everything that I've got queued up is fully compatible.</p> -<p>17:14 <code>&lt;mgerdts&gt;</code> <a href="https://bugs.launchpad.net/cloud-init/+bug/1667735">https://bugs.launchpad.net/cloud-init/+bug/1667735</a> implements proper protocol negotiation over the serial port. The lack of this has caused problems with KVM at times too.</p> -<p>17:14 <code>&lt;ubot5</code>&gt;` Ubuntu bug 1667735 in cloud-init (Ubuntu Trusty) "cloud-init doesn't retry metadata lookups and hangs forever if metadata is down" [Medium,Confirmed]</p> -<p>17:15 <code>&lt;mgerdts&gt;</code> <a href="https://bugs.launchpad.net/cloud-init/+bug/1746605">https://bugs.launchpad.net/cloud-init/+bug/1746605</a> adressess times when cloud-init and other software may be trying to use the metadata serial port at the same time. This is purely a bug fix.</p> -<p>17:15 <code>&lt;ubot5</code>&gt;` Ubuntu bug 1746605 in cloud-init "DataSourceSmartOS needs locking" [Medium,Confirmed]</p> -<p>17:15 <code>&lt;mgerdts&gt;</code> I hit it when rc.local and cloud-init were both trying to get metadata.</p> -<p>17:17 <code>&lt;mgerdts&gt;</code> <a href="https://bugs.launchpad.net/cloud-init/+bug/1763480">https://bugs.launchpad.net/cloud-init/+bug/1763480</a> makes it so that cloud-init doesn't stack trace and exit when there is no customer_metadata. This is an unlikely case, but something that is hit when you are testing things that don't need ssh keys, etc.</p> -<p>17:17 <code>&lt;ubot5</code>&gt;` Ubuntu bug 1763480 in cloud-init "DataSourceSmartOS list() should always return a list" [Medium,Confirmed]</p> -<p>17:18 <code>&lt;mgerdts&gt;</code> <a href="https://bugs.launchpad.net/cloud-init/+bug/1763512">https://bugs.launchpad.net/cloud-init/+bug/1763512</a> finishes off the partial implementation of sdc:routes support. Previously, we didn't publish the required information to VMs, so it is fair to consider this a new feature.</p> -<p>17:18 <code>&lt;ubot5</code>&gt;` Ubuntu bug 1763512 in cloud-init "DataSourceSmartOS ignores sdc:routes" [Medium,Confirmed]</p> -<p>17:19 <code>&lt;mgerdts&gt;</code> <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1763511">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1763511</a> is probably the most incompatible change. New ephemeral disks will get ext4 instead of ext3, which is needed for larger disks that seem to be getting more common.</p> -<p>17:19 <code>&lt;ubot5</code>&gt;` Ubuntu bug 1763511 in cloud-init (Ubuntu) "DataSourceSmartOS should default to ext4" [Undecided,New]</p> -<p>17:21 <code>&lt;mgerdts&gt;</code> I think that's all that I have in the works right now. Do any of these sound like they would be problematic as far back as Xenial?</p> -<p>17:29 <code>&lt;rharper&gt;</code> new features are OK ,bug fixes are fine as well; I think that different filesystem is somewhat tricky</p> -<p>17:30 <code>&lt;smoser&gt;</code> i think i'm generally ok with the different filesystem.</p> -<p>17:31 <code>&lt;smoser&gt;</code> if the reason is that simply ext3 can't handle super-big</p> -<p>17:31 <code>&lt;rharper&gt;</code> yeah, that doesn't seem so user-visible w.r.t configuration;</p> -<p>17:32 <code>&lt;smoser&gt;</code> we could ensure being more backward compat if we checked the size of the disk and made an ext4 if &gt;` that-size</p> -<p>17:32 <code>&lt;smoser&gt;</code> then there'd less issue</p> -<p>17:32 <code>&lt;smoser&gt;</code> but more complication and future we'd be stuck with that</p> -<p>17:32 <code>&lt;rharper&gt;</code> yeah, it wouldn't have worked on ext3 then it would be fine to use ext4</p> -<p>17:32 <code>&lt;smoser&gt;</code> so i'd rather really just bite the bulleet</p> -<p>17:32 <code>&lt;rharper&gt;</code> it could be a metadata flag that the Datasource looks for</p> -<p>17:32 <code>&lt;smoser&gt;</code> rather than describing to pepole forever "well, if your disk is `&lt; X you'll get ext3 otherwise ext4"</p> -<p>17:49 <code>&lt;blackboxsw&gt;</code> rharper: got time for a netplan global dns hangout?</p> -<p>17:49 <code>&lt;rharper&gt;</code> y</p> -<p>17:49 <code>&lt;blackboxsw&gt;</code> I want to make sure I'm reading the tea leaves right</p> -<p>17:52 <code>&lt;smoser&gt;</code> mgerdts: <a href="http://paste.ubuntu.com/p/5qdtFzY8w7/">http://paste.ubuntu.com/p/5qdtFzY8w7/</a></p> -<p>17:52 <code>&lt;blackboxsw&gt;</code> ok rharper I'm in cloud-init hangout</p> -<p>17:52 <code>&lt;smoser&gt;</code> that makes tests pass. and i think the changes to the code path are right</p> -<p>17:52 <code>&lt;rharper&gt;</code> ok</p> -<p>17:52 <code>&lt;rharper&gt;</code> brt</p> -<p>17:54 <code>&lt;smoser&gt;</code> it is still hacked in a sense that the response only deals with fp.read(1) rather than possibly anything that read more than 1.</p> -<p>17:56 <code>&lt;cyphermox&gt;</code> blackboxsw: rharper: what's this about netplan global dns?</p> -<p>17:57 <code>&lt;rharper&gt;</code> cyphermox: converting network v1 syntax from maas into something that works with netplan which doesn't have "dns" unbound to any interfaces</p> -<p>17:57 <code>&lt;cyphermox&gt;</code> ok</p> -<p>17:57 <code>&lt;rharper&gt;</code> maas I believe has fixed this for 2.4.x</p> -<p>17:58 <code>&lt;rharper&gt;</code> they no longer will emit the type: nameserver but legacy maas would have that, so we've a branch that stuffs them in reasonable places under defined interfaces which don't already have DNS values</p> -<p>17:58 <code>&lt;blackboxsw&gt;</code> cyphermox: just SRU validation w.r.t. <a href="https://bugs.launchpad.net/cloud-init/+bug/1750884">https://bugs.launchpad.net/cloud-init/+bug/1750884</a></p> -<p>17:59 <code>&lt;ubot5</code>&gt;` Ubuntu bug 1750884 in cloud-init "[2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution" [Medium,Fix released]</p> -<p>17:59 <code>&lt;cyphermox&gt;</code> all good</p> -<p>18:11 <code>&lt;blackboxsw&gt;</code> ooops, and /me forgot the end the epic meeting</p> -<p>18:11 <code>&lt;blackboxsw&gt;</code> thx rharper for the chat</p> -<p>18:11 <code>&lt;blackboxsw&gt;</code> #endmeetiung</p> -<p>18:11 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-04-02T16:05:00+00:002018-04-02T16:05:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-04-02:/status-2018-04-02.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: bi-weekly status meeting, 02 Apr at 16:05 &mdash; 17:03 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-04-02-16.05.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-04-02-16.05.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:08.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://lists.launchpad.net/cloud-init/msg00145.html">https://lists.launchpad.net/cloud-init/msg00145.html …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: bi-weekly status meeting, 02 Apr at 16:05 &mdash; 17:03 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-04-02-16.05.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-04-02-16.05.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:08.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://lists.launchpad.net/cloud-init/msg00145.html">https://lists.launchpad.net/cloud-init/msg00145.html</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/fix/cc_resizefs_on_zfs_root">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/fix/cc_resizefs_on_zfs_root</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:19.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/fix/cc_resizefs_on_zfs_root">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/fix/cc_resizefs_on_zfs_root</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/342007">https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/342007</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/342428">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/342428</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/342010">https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/342010</a> </li> -<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>Office Hours (next ~30 minutes)</h3> -<p>The discussion about "Office Hours (next ~30 minutes)" started at 16:27.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/339438">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/339438</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/339438">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/339438</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 (64)</li> -<li>rharper (14)</li> -<li>ubot5 (3)</li> -<li>meetingology (3)</li> -<li>powersj (2)</li> -</ul> -<h2>Full Log</h2> -<p>16:05 <code>&lt;blackboxsw&gt;</code> #startmeeting bi-weekly status meeting</p> -<p>16:05 <code>&lt;meetingology&gt;</code> Meeting started Mon Apr 2 16:05:50 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:05 <code>&lt;meetingology&gt;</code> </p> -<p>16:05 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> Welcome to the post-Easter episode of cloud-init's status meeting 🐰</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> Today's meeting will probably be light as we are fairly light on attendees given various holiday schedules</p> -<p>16:07 <code>&lt;rharper&gt;</code> o/</p> -<p>16:07 <code>&lt;rharper&gt;</code> nice rabbit ears</p> -<p>16:07 <code>&lt;blackboxsw&gt;</code> heya! As always, we'll go through recent changes, in progress work and ~30 minutes of office hours</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> feel free to interject and ask quesitons at any time.</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> Here's a brief run down of what we have committed to master in the last couple weeks</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> - Support for setting hostname from metadata prior to network bringup.</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> This fixes vsphere multi-vm deployments all coming up with the same</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> 'ubuntu' hostname. <a href="[http://pad.lv/1746455](http://pad.lv/1746455)">LP: #1746455</a></p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> - Support initramfs iscsi root so network devices aren't disconnected</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> before shutdown</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> - Added cloud-config module <code>cc_snap</code> which enables loading snap</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> assertions, configuring snapd and installing snap packages on Ubuntu.</p> -<p>16:10 <code>&lt;ubot5&gt;</code> Launchpad bug 1746455 in cloud-init "cloud-init vSphere cloud provider DHCP unique hostname issue" [High,Fix released]</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> Deprecated <code>cc_snappy</code> and <code>cc_snap_config</code> modules.</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> - Make salt minion work on FreeBSD (Dominic Schlegel)</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> <a href="[http://pad.lv/1721503](http://pad.lv/1721503)">LP:#1721503</a></p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> - Simplify compound conditionals (Rémy Léone)</p> -<p>16:10 <code>&lt;ubot5&gt;</code> Launchpad bug 1721503 in cloud-init "salt module not able to be used on FreeBSD" [Medium,Fix released]</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> - Change some list creation and population to literals (Rémy Léone)</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> - Add puppet 4 support configurable in <code>cc_puppet</code> module (Romanos</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> Skiadas)</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> - Fix datasouce Azure <code>get_hostname</code> function for hostname bounce</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> (Douglas Jordan) <a href="[http://pad.lv/1754495](http://pad.lv/1754495)">LP:#1754495</a></p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> - OpenNebula datasource now uses network config v2 to support IPv6</p> -<p>16:10 <code>&lt;ubot5&gt;</code> Launchpad bug 1755965 in cloud-init (Ubuntu) "duplicate for #1754495 util.subp regression: no longer accept commands as string" [Critical,Fix released]</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> config (Akihiko Ota)</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> - Add Hetzner Cloud datasource support (Markus Schade)</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> The highlights of this work that will affect various clouds: hostname setting before network bringup, in cloud-init's init-local stage.</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> so if your cloud's metadata provides hostname information (per your instance creation) that hostname gets set before any potential dhcp discovery on the instance. This is a big win for Azure and may allow us to avoid/deprecate some of the hostname_bounce functionality</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> which was baked in to re-dhcp in order to publish updated hostname information to DDNS</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> We also have landed support for two new clouds: Hetzner Cloud and IBMCloud. A big thanks to Markus Schade for the Hetzner work there and smoser for the IBMCloud datasource</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> do3meli (Dominic Schlegel) has also been on a blitz fixing and updating a lot of FreeBSD support in cloud-init tip so thank you sir for that work as well.</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> We've just also landed some zfs resize support by rharper as well that should be making it's way into your friendly neighborhood Ubuntu Bionic series in a cloud near you</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> anything else I'm missing on rharper or powersj ?</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> ahh hold the phone</p> -<p>16:16 <code>&lt;rharper&gt;</code> blackboxsw: well, not my zfs-resize</p> -<p>16:17 <code>&lt;rharper&gt;</code> but I do have some fixes for it</p> -<p>16:17 <code>&lt;rharper&gt;</code> <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/fix/cc_resizefs_on_zfs_root">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/fix/cc_resizefs_on_zfs_root</a></p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> We officially released cloud-init 18.2 in master. There is an 18.2 tag in the repo for folks wanting to take an early cut of it.</p> -<p>16:17 <code>&lt;rharper&gt;</code> our ci-test backend normally runs with zfs, it's not right now so it missed a couple edge cases that we need to handle</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> Per cloud-init 18.2 here is an email sent to the cloud-init mailing list describing the details: <a href="https://lists.launchpad.net/cloud-init/msg00145.html">https://lists.launchpad.net/cloud-init/msg00145.html</a></p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> #link <a href="https://lists.launchpad.net/cloud-init/msg00145.html">https://lists.launchpad.net/cloud-init/msg00145.html</a></p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/fix/cc_resizefs_on_zfs_root">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/fix/cc_resizefs_on_zfs_root</a></p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> The upstream team has released 18,2 to Bionic as of last week, and we started an Ubuntu SRU process into Xenial and Artful.</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> We expect the 18.2 to be present in Xenial and Artful within 2 weeks in your cloud, so if you are waiting on a feature, it won't be very long.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> Also in-progress are some of rharper's zfs fixes, and some exception callback cleanup that will affect Azure, EC2, OpenStack and Scaleway clouds.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/fix/cc_resizefs_on_zfs_root">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/fix/cc_resizefs_on_zfs_root</a></p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/342007">https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/342007</a></p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> And we are doing our part to finally purge net-tools dependencies from cloud-init (in favor of iproute2)</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/342428">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/342428</a></p> -<p>16:24 <code>&lt;rharper&gt;</code> blackboxsw: I responded to your ip -6 route q from last week, did you see that ?</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> rharper: haven't yet, but I'll grab those comments today for sure (I think I missed some of your earlier review comments)</p> -<p>16:24 <code>&lt;rharper&gt;</code> ok</p> -<p>16:25 <code>&lt;rharper&gt;</code> the tl;dr for that one is that you want this: ip -6 route list table all</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> ahh excellent, I was wondering why we were missing content for local routes etc</p> -<p>16:25 <code>&lt;rharper&gt;</code> right</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> thanks</p> -<p>16:25 <code>&lt;rharper&gt;</code> np</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> also, on our continuous integration front , powersj has put up a branch that I'd like to see us land with some ssh improvements</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/342010">https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/342010</a></p> -<p>16:26 <code>&lt;powersj&gt;</code> :) yep</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> any other in-progress work worth noting?</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> Intereseted parties can always track our public trello board for a glimpse of what we are working on</p> -<p>16:27 <code>&lt;blackboxsw&gt;</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:27 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next ~30 minutes)</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> We'll all have eyes glued to the screen for the next 30 minutes for rants, feature discussion and bug work.</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> With that, the floor is open for any topics. Thanks for tuning in.</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> My day today will be Ubuntu SRU(stable release update)-related, so I'm getting on rharper's zfs branch now and they running a couple manual tests on ec2/azure/openstack</p> -<p>16:30 <code>&lt;rharper&gt;</code> +1</p> -<p>16:30 <code>&lt;rharper&gt;</code> oh, the ntp-spec update is ready for review and testing</p> -<p>16:31 <code>&lt;rharper&gt;</code> <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/339438">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/339438</a></p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> ahh +1 we want that in too</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/339438">https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/339438</a></p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> Alrighty, happy spring break all.</p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> Next meeting will be two weeks from today.</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> powersj: rharper 4/16 look good for folks?</p> -<p>17:03 <code>&lt;powersj&gt;</code> +1 from me</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-03-19T16:02:00+00:002018-03-19T16:02:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-03-19:/status-2018-03-19.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 19 Mar at 16:02 &mdash; 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><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 19 Mar at 16:02 &mdash; 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>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status meeting</p> -<p>16:02 <code>&lt;meetingology&gt;</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>&lt;meetingology&gt;</code> </p> -<p>16:02 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:03 <code>&lt;blackboxsw&gt;</code> ok, let's kick off this cloud-init bi-weekly meeting. welcome all!</p> -<p>16:04 <code>&lt;dpb1&gt;</code> o/</p> -<p>16:04 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>16:05 <code>&lt;dpb1&gt;</code> smoser vacation specifically</p> -<p>16:05 <code>&lt;blackboxsw&gt;</code> hehe. Generally we're tracking high-points of what lands in our trello board</p> -<p>16:05 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> but from changelogs folks have made progress on azure, vmware and FreeBSD deployment targets</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> - netplan: render bridge port-priority values (LP: #1735821)</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> - net: recognize iscsi root cases without ip= on kernel command line.</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> (LP: #1752391)</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> - util: Fix subp regression. Allow specifying subp command as a string.</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> (LP: #1755965)</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> - This commit fixes get_hostname on the AzureDataSource.</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> [Douglas Jordan] (LP: #1754495)</p> -<p>16:06 <code>&lt;ubot5</code>&gt;` 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>&lt;blackboxsw&gt;</code> - shellify: raise TypeError on bad input.</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> - FreeBSD: Set hostname to FQDN. [Dominic Schlegel] (LP: #1753499)</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> - Make salt minion module work on FreeBSD.</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> [Dominic Schlegel] (LP: #1721503)</p> -<p>16:06 <code>&lt;ubot5</code>&gt;` 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>&lt;blackboxsw&gt;</code> - set_hostname: When present in metadata, set it before network bringup.</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> (LP: #1746455) VMWare</p> -<p>16:06 <code>&lt;ubot5</code>&gt;` 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>&lt;blackboxsw&gt;</code> - cc_snap: Add new module to install and configure snapd and snap</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> packages.</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> - doc: fix all warnings issued by 'tox -e doc'</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> - tests: Make pylint happy and fix python2.6 uses of assertRaisesRegex.</p> -<p>16:06 <code>&lt;ubot5</code>&gt;` 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>&lt;blackboxsw&gt;</code> - tests: fix run_tree and bddeb</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> - tests: Fix some warnings in tests that popped up with newer python.</p> -<p>16:06 <code>&lt;ubot5</code>&gt;` 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>&lt;blackboxsw&gt;</code> - tests: fix flakes warning for unused variable</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> - tests: patch leaked stderr messages from snap unit tests</p> -<p>16:06 <code>&lt;ubot5</code>&gt;` 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>&lt;blackboxsw&gt;</code> - tests: Centralize and re-use skipTest based on json schema presense.</p> -<p>16:06 <code>&lt;ubot5</code>&gt;` 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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> On the ubuntu side of the house we got tip of tree published into Bionic thusday &amp; 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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> Ubuntu is getting a number of new cloud-config modules:</p> -<p>16:13 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> - new cc_ubuntu_drivers: support to install 3rd party drivers on install</p> -<p>16:15 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> these should be landing in the week(s) to come</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> and cc_snap landed already</p> -<p>16:17 <code>&lt;blackboxsw&gt;</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>&lt;rharper&gt;</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>&lt;smoser&gt;</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>&lt;rharper&gt;</code> heh</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> maybe we can toggle between the two modulus 2 :)</p> -<p>16:18 <code>&lt;rharper&gt;</code> sorry, didn't meant to disturb the flow</p> -<p>16:19 <code>&lt;rharper&gt;</code> continue</p> -<p>16:19 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> anything to free up developer time will give us more time for reviews/code</p> -<p>16:19 <code>&lt;ajorg&gt;</code> should vendor-specific modules be shipped in a separate package?</p> -<p>16:20 <code>&lt;smoser&gt;</code> vendor specific modules ?</p> -<p>16:20 <code>&lt;ajorg&gt;</code> ubuntu_advantage</p> -<p>16:22 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> each module has a distro attribute defined as to whether or not it will even run</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> so we have spacewalk, zypper_repos etc</p> -<p>16:24 <code>&lt;smoser&gt;</code> and cloud.cfg is rendered based on knowledge of the distro</p> -<p>16:24 <code>&lt;smoser&gt;</code> so ubuntu_advantage wont even be in the list of config modules</p> -<p>16:24 <code>&lt;smoser&gt;</code> having a static config module list is WIN in this case (but pain elsewhere)</p> -<p>16:25 <code>&lt;smoser&gt;</code> at some point whe may have a more dynamic config module list.</p> -<p>16:25 <code>&lt;smoser&gt;</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>&lt;blackboxsw&gt;</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>&lt;ajorg&gt;</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>&lt;blackboxsw&gt;</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>&lt;smoser&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> so cloud-init is getting it's grubby hands into a couple of more clouds shortly.</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> s/it's/its/</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> it's nice to see the adoption continue to grow</p> -<p>16:31 <code>&lt;smoser&gt;</code> looks like someone followed up on hetzner</p> -<p>16:31 <code>&lt;smoser&gt;</code> so that hopefully is ready to land</p> -<p>16:31 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> I <em>think</em> that's all for in-progress development at the moment.</p> -<p>16:33 <code>&lt;smoser&gt;</code> man we need to fix that pylint thing.</p> -<p>16:33 <code>&lt;smoser&gt;</code> did you mention ?</p> -<p>16:33 <code>&lt;rharper&gt;</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>&lt;blackboxsw&gt;</code> Anything else that should be noted by anyone?</p> -<p>16:33 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> oops</p> -<p>16:34 <code>&lt;smoser&gt;</code> cloudinit/config/cc_puppet.py:143: [W1505(deprecated-method), handle] Using deprecated method readfp()</p> -<p>16:34 <code>&lt;blackboxsw&gt;</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>&lt;smoser&gt;</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>&lt;blackboxsw&gt;</code> yeah how much should we freeze our deps?</p> -<p>16:35 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</code> but I don't really know whether it's worth us 'pinning' everything</p> -<p>16:36 <code>&lt;smoser&gt;</code> i think pinning everything is generally the best practice for this sort of thing now.</p> -<p>16:37 <code>&lt;smoser&gt;</code> oh my.</p> -<p>16:37 <code>&lt;blackboxsw&gt;</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>&lt;smoser&gt;</code> blackboxsw: did you know you accidently fixed that in trunk ?</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> smoser: I know I intentionally added a pylint ignore on that to come back and address it today.</p> -<p>16:38 <code>&lt;ajorg&gt;</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>&lt;smoser&gt;</code> oh ko. i see.</p> -<p>16:39 <code>&lt;smoser&gt;</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>&lt;smoser&gt;</code> there is the "good" break, where new upload to pypi identifies some lingering bug</p> -<p>16:40 <code>&lt;blackboxsw&gt;</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>&lt;smoser&gt;</code> but also the "bad" break where some upload breaks your c-i for invalid reason.</p> -<p>16:42 <code>&lt;smoser&gt;</code> one huge advantage to pinning is the ability to re-create things.</p> -<p>16:42 <code>&lt;blackboxsw&gt;</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>&lt;smoser&gt;</code> ie, if you were looking to it bisect something...</p> -<p>16:42 <code>&lt;smoser&gt;</code> git bisect</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> I should transition to the office hours topic so we can continue discussion</p> -<p>16:43 <code>&lt;smoser&gt;</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>&lt;smoser&gt;</code> sure we can transition to office hours.</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> #topic Office hours (next ~30 mins)</p> -<p>16:43 <code>&lt;smoser&gt;</code> but yeah... i want c-i on tip to not just start failing.</p> -<p>16:44 <code>&lt;stanguturi&gt;</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>&lt;ubot5</code>&gt;` 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>&lt;blackboxsw&gt;</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>&lt;smoser&gt;</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>&lt;blackboxsw&gt;</code> +1 smoser I'll put a card up for that</p> -<p>16:46 <code>&lt;smoser&gt;</code> stanguturi: your suggestion there is not a bad idea at all.</p> -<p>16:46 <code>&lt;blackboxsw&gt;</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>&lt;smoser&gt;</code> the desire to have cloud-init tell the platform/datasource that it failed or succeeded is valid.</p> -<p>16:47 <code>&lt;smoser&gt;</code> with MAAS, that his done via reporting</p> -<p>16:47 <code>&lt;blackboxsw&gt;</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>&lt;blackboxsw&gt;</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>&lt;smoser&gt;</code> cloud-init reports status and results via a Reporter.</p> -<p>16:47 <code>&lt;smoser&gt;</code> dojordan (i think) had also put up a request for a reproter module on azure.</p> -<p>16:47 <code>&lt;smoser&gt;</code> so we <em>do</em> kind of have the function you're after in place.</p> -<p>16:48 <code>&lt;stanguturi&gt;</code> smoser: ok. Any inputs / examples of using it will be really great.</p> -<p>16:50 <code>&lt;smoser&gt;</code> stanguturi: well, the reporter interface is pretty simple. you can cloudinit/reporting/handlers.py</p> -<p>16:51 <code>&lt;smoser&gt;</code> blackboxsw: <a href="http://paste.ubuntu.com/p/6KjDX8WHQH/">http://paste.ubuntu.com/p/6KjDX8WHQH/</a></p> -<p>16:51 <code>&lt;smoser&gt;</code> did you intend boht of those changes ?</p> -<p>16:51 <code>&lt;stanguturi&gt;</code> smoser: ok. Then do I need to write a new handler for our DataSource?</p> -<p>16:52 <code>&lt;smoser&gt;</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>&lt;blackboxsw&gt;</code> wow smoser, no</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> wow, ok, I'll put up a branch to fix that</p> -<p>16:52 <code>&lt;stanguturi&gt;</code> smoser: ok. Will work on that.</p> -<p>16:52 <code>&lt;smoser&gt;</code> ok.</p> -<p>16:53 <code>&lt;stanguturi&gt;</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>&lt;smoser&gt;</code> stanguturi: do you find this is actually needed ?</p> -<p>16:53 <code>&lt;smoser&gt;</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>&lt;smoser&gt;</code> which i can't seem to believe is all that a common situation in VMs</p> -<p>16:54 <code>&lt;stanguturi&gt;</code> smoser: Yeah. We need this for 'VMware guest customization workflow'.</p> -<p>16:54 <code>&lt;dpb1&gt;</code> smoser: oh man, I hope not</p> -<p>16:54 <code>&lt;stanguturi&gt;</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>&lt;smoser&gt;</code> stanguturi: does it actually solve a <em>current</em> problem for you ?</p> -<p>16:55 <code>&lt;stanguturi&gt;</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>&lt;smoser&gt;</code> or one that originally came in from a decade ago</p> -<p>16:55 <code>&lt;stanguturi&gt;</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>&lt;smoser&gt;</code> hm... so my sugestion is really to stop allowing that :)</p> -<p>16:56 <code>&lt;stanguturi&gt;</code> smoser: Oh ok. Can you please add a comment to that merge request just for the record.</p> -<p>16:56 <code>&lt;smoser&gt;</code> i very well could be wrong</p> -<p>16:56 <code>&lt;smoser&gt;</code> but the only time that i ever had to deal with this was when dual booting</p> -<p>16:56 <code>&lt;smoser&gt;</code> with windows specifically</p> -<p>16:57 <code>&lt;stanguturi&gt;</code> smoser: ok.</p> -<p>16:57 <code>&lt;smoser&gt;</code> am i wrong there ?</p> -<p>16:57 <code>&lt;smoser&gt;</code> i really <em>could</em> be.</p> -<p>16:58 <code>&lt;stanguturi&gt;</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>&lt;smoser&gt;</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>&lt;smoser&gt;</code> stanguturi: yeah. i understand that.</p> -<p>16:58 <code>&lt;stanguturi&gt;</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>&lt;stanguturi&gt;</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>&lt;stanguturi&gt;</code> smoser: And when is the cloud-init 18.2 scheduled for release? 3/22?</p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> probably a good time for us to bring that up</p> -<p>17:01 <code>&lt;smoser&gt;</code> yeah. whoops.</p> -<p>17:01 <code>&lt;smoser&gt;</code> :)</p> -<p>17:01 <code>&lt;smoser&gt;</code> 18.2 is scheduled for 3/22 (thursday)</p> -<p>17:02 <code>&lt;blackboxsw&gt;</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>&lt;smoser&gt;</code> but amoung our internall team we decided to push that to 3/27</p> -<p>17:02 <code>&lt;stanguturi&gt;</code> smoser: ok. Thanks for the update.</p> -<p>17:02 <code>&lt;blackboxsw&gt;</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>&lt;smoser&gt;</code> we will send an email today or tomrrow witih "pending release" like subject like we've done before.</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> dpb1: others any objections to cutting the 18.2 release on Tuesday 3/27?</p> -<p>17:03 <code>&lt;dpb1&gt;</code> none</p> -<p>17:04 * blackboxsw adds the upcoming date to the topic</p> -<p>17:05 <code>&lt;blackboxsw&gt;</code> ... ok, folks interested in discussing today?</p> -<p>17:08 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io">https://cloud-init.github.io</a></p> -<p>17:09 <code>&lt;blackboxsw&gt;</code> The above link will have our captured logs for this meeting.</p> -<p>17:09 <code>&lt;blackboxsw&gt;</code> thanks again for tuning in</p> -<p>17:09 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-03-05T17:00:00+00:002018-03-05T17:00:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-03-05:/status-2018-03-05.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 05 Mar at 17:00 &mdash; 17:53 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-03-05-17.00.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-03-05-17.00.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 17:02.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://lists.launchpad.net/cloud-init/msg00144.html">https://lists.launchpad.net/cloud-init/msg00144 …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 05 Mar at 17:00 &mdash; 17:53 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-03-05-17.00.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-03-05-17.00.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 17:02.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://lists.launchpad.net/cloud-init/msg00144.html">https://lists.launchpad.net/cloud-init/msg00144.html</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 17:12.</p> -<ul> -<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://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="https://bugs.launchpad.net/cloud-init/+bug/1724128">https://bugs.launchpad.net/cloud-init/+bug/1724128</a> </li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1750780">https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1750780</a> </li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1667831">https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1667831</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 (58)</li> -<li>stanguturi (13)</li> -<li>smoser (7)</li> -<li>ubot5` (7)</li> -<li>meetingology (3)</li> -<li>powersj (1)</li> -<li>rharper (1)</li> -</ul> -<h2>Full Log</h2> -<p>17:00 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status meeting</p> -<p>17:00 <code>&lt;meetingology&gt;</code> Meeting started Mon Mar 5 17:00:58 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>17:00 <code>&lt;meetingology&gt;</code> </p> -<p>17:00 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>17:01 <code>&lt;powersj&gt;</code> o/</p> -<p>17:01 <code>&lt;blackboxsw&gt;</code> hey folks welcome to another episode of Cloud-init status updates. Thanks for coming.</p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> Since we had a status meeting just prior to the cloud-init upstream release last week there won't be a ton of updates this week.</p> -<p>17:02 <code>&lt;rharper&gt;</code> o--</p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> without further ado</p> -<p>17:02 <code>&lt;blackboxsw&gt;</code> #topic Recent Changes</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> highlight of the last week was the upstream 18.1 release getting cut! Great work folks on getting branches landed in tip proir to release</p> -<p>17:03 * blackboxsw grabs powersj highlights</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> cloud-init 18.1 released!</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> ds-identify: Fix searching for iso9660 OVF cdroms for vmware (LP: #1749980)</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> Documented chef example incorrectly represented apt source configuration for chef install</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> SUSE: Fix groups used for ownership of cloud-init.log (Robert Schweikert)</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> OVF: Fix VMware support for 64-bit platforms (Sankar Tanguturi)</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> Salt: configure grains in grains file rather than in minion config (Daniel Wallace)</p> -<p>17:03 <code>&lt;blackboxsw&gt;</code> Implement puppet 4 support (Romanos Skiadas)</p> -<p>17:03 <code>&lt;ubot5</code>&gt;` Launchpad bug 1749980 in cloud-init "ds-identify doesn't properly detect ISO" [High,Fix released] <a href="https://launchpad.net/bugs/1749980">https://launchpad.net/bugs/1749980</a></p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> For those that didn't see the email:</p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> #link <a href="https://lists.launchpad.net/cloud-init/msg00144.html">https://lists.launchpad.net/cloud-init/msg00144.html</a></p> -<p>17:04 <code>&lt;smoser&gt;</code> o/</p> -<p>17:04 <code>&lt;blackboxsw&gt;</code> thanks again stanguturi Akihiko and Max Illfelder</p> -<p>17:06 <code>&lt;blackboxsw&gt;</code> in the ubuntu side of the house we published 18.1 to the Bionic series so clouds now have this by default in bionic images</p> -<p>17:06 <code>&lt;blackboxsw&gt;</code> Also on the ubuntu-side of the house we finalized an SRU (stable release update) of 17.2.35.2 into both Xenial and Artful, so xenial-updates and artful-updates should have 17.2.35 available (which is only a few commits earlier than the 18.1 release)</p> -<p>17:10 <code>&lt;blackboxsw&gt;</code> Also in tip post 18.1 we had significant contribution from partners</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> Simplify some comparisions. [Rémy Léone]</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> Change some list creation and population to literal. [Rémy Léone]</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> GCE: fix reading of user-data that is not base64 encoded.</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> doc: fix chef install from apt packages example in RTD.</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> Implement puppet 4 support [Romanos Skiadas]</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> subp: Fix subp usage with non-ascii characters when no system locale.</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> salt: configure grains in grains file rather than in minion config. [Daniel Wallace]</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> (sorry took me a while to dig up the git formatting options)</p> -<p>17:12 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>17:12 <code>&lt;blackboxsw&gt;</code> We have some existing branches we are trying to get review feedback to folks on:</p> -<p>17:12 <code>&lt;blackboxsw&gt;</code> #link <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a></p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> Are there reviews that folks feel need some attention this week?</p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> Internally, we work on items in the TODO/Doing lane of our trello board here:</p> -<p>17:13 <code>&lt;blackboxsw&gt;</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>17:14 <code>&lt;stanguturi&gt;</code> @blackboxsw: I have one request about the bug <a href="https://bugs.launchpad.net/cloud-init/+bug/1724128">https://bugs.launchpad.net/cloud-init/+bug/1724128</a> Any inputs from cloud-init team will be great.</p> -<p>17:14 <code>&lt;ubot5</code>&gt;` Ubuntu bug 1724128 in open-vm-tools (Ubuntu) "Need a Success / Failure notification mechanism when cloud-init finishes." [Undecided,New]</p> -<p>17:15 <code>&lt;blackboxsw&gt;</code> so we have some Snap module development incoming on chrony support, snappy support, vsphere early hostname support</p> -<p>17:16 <code>&lt;blackboxsw&gt;</code> stanguturi: checking</p> -<p>17:17 <code>&lt;stanguturi&gt;</code> blackboxsw: Thanks. I discussed this last year in August in cloud-init meeting. Logged this bug long time back. But for some reason, it was not tagged with the proper project. My bad.</p> -<p>17:18 <code>&lt;blackboxsw&gt;</code> stanguturi: we have an external notification mechanism for scripts to information about when cloud-init has finally completed via "cloud-init status --wait" .... hrm trying to discuss here about alternative mechanisms internal to cloud-init</p> -<p>17:21 <code>&lt;blackboxsw&gt;</code> stanguturi: ok we can probably add a publish/subscription mechanism in cloud-init proper for internal eventing that'd get this done.</p> -<p>17:21 <code>&lt;stanguturi&gt;</code> @blackboxsw: Thanks a lot.</p> -<p>17:21 <code>&lt;blackboxsw&gt;</code> I've added a topic to our meetings this week to discuss the approach that could make this happen.</p> -<p>17:21 <code>&lt;blackboxsw&gt;</code> We'll comment on the bug/mailing list with an approach proposal</p> -<p>17:22 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/+bug/1724128">https://bugs.launchpad.net/cloud-init/+bug/1724128</a></p> -<p>17:22 <code>&lt;ubot5</code>&gt;` Ubuntu bug 1724128 in open-vm-tools (Ubuntu) "Need a Success / Failure notification mechanism when cloud-init finishes." [Undecided,New]</p> -<p>17:22 <code>&lt;blackboxsw&gt;</code> just so I capture the link</p> -<p>17:23 <code>&lt;stanguturi&gt;</code> @blackboxsw: Thanks I have got another request. I am working on <a href="https://code.launchpad.net/~sankaraditya/cloud-init/+git/cloud-init/+ref/vmware-customize-utc-time">https://code.launchpad.net/~sankaraditya/cloud-init/+git/cloud-init/+ref/vmware-customize-utc-time</a> to add some 'UTC customizations'. Got some review comments from Scott Moser. Can you please provide some pointers to any existing / tests / procedure to add new functionality to distro class</p> -<p>17:27 <code>&lt;blackboxsw&gt;</code> stanguturi: re-reading ... and checking out the existing cloudinit.distro base module for utc /tz specifics</p> -<p>17:29 <code>&lt;stanguturi&gt;</code> @blackboxsw: We just want to customize /etc/default/rcS file with some settings on debian platforms.</p> -<p>17:36 <code>&lt;blackboxsw&gt;</code> hrm, so I'm conflicted with your branch by seeing that Distro.tz_zone_dir sets that path for for that distro for where TZ information is being configured. I think I'm missing why UTC=yes|no is needed versus Debian.set_timezone</p> -<p>17:38 <code>&lt;stanguturi&gt;</code> @blackboxsw: This is actually related to 'hwclock'. The key value that needs to be set in /etc/default/rcS is 'UTC' but it's related to 'hwclock' setting.</p> -<p>17:38 <code>&lt;blackboxsw&gt;</code> for my suggestion on that initial review, I thought that we might need to allow for a Debian-specific method which would handle this additional/separate configuration file processing you were doing w/ /etc/default/rcS</p> -<p>17:40 <code>&lt;smoser&gt;</code> looking quicklyi it looks like at least recently the correct place to store that is /etc/default/hwclock</p> -<p>17:40 <code>&lt;smoser&gt;</code> /etc/default/rcS is read, but per /etc/init.d/hwclock.sh, it looks like /etc/default/hwclock is preferred</p> -<p>17:41 <code>&lt;smoser&gt;</code> but either way, wahat i think we really want is for the distro class to have a 'store_hwclock_timezone' or something</p> -<p>17:41 <code>&lt;smoser&gt;</code> and then you'd call into that.</p> -<p>17:42 <code>&lt;stanguturi&gt;</code> ok. Thanks Scott. Are there any extra test cases / test suites that I need to run if I am modifying the distro class?</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> as far as developing additional unit tests for a new distro method: I'd expect new feature methods to be covered in tests/unittests/test_distros/test_debian.py</p> -<p>17:42 <code>&lt;blackboxsw&gt;</code> also cloud-init summit action we haven't done yet is to move all unittests out of tests/unittests and under cloudinit proper</p> -<p>17:42 <code>&lt;smoser&gt;</code> +1 blackboxsw</p> -<p>17:44 <code>&lt;stanguturi&gt;</code> ok Will work on that.</p> -<p>17:44 <code>&lt;blackboxsw&gt;</code> I'll take that test migration action for any existing modules that are already tested under tests/unittests. The policy we were hoping is that for new modules added under "cloudinit" we'd add a cloudinit/somepath/tests/test_newmodule.py for each cloudinit/somepath/newmodule.py</p> -<p>17:45 <code>&lt;blackboxsw&gt;</code> so if you want to build on tests/unittests/test_distros/test_debian.py we'll pull that under cloudinit proper when we finally remove tests/unittests altogether</p> -<p>17:45 <code>&lt;blackboxsw&gt;</code> stanguturi: any other items?</p> -<p>17:46 <code>&lt;blackboxsw&gt;</code> otherwise I think we'll probably wrap up this meeting in a few minutes</p> -<p>17:46 <code>&lt;stanguturi&gt;</code> Yeah. I have one more item. Sorry. <a href="https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1750780">https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1750780</a></p> -<p>17:46 <code>&lt;ubot5</code>&gt;` Ubuntu bug 1750780 in open-vm-tools (Ubuntu Xenial) "Race with local file systems can make open-vm-tools fail to start" [Undecided,Triaged]</p> -<p>17:47 <code>&lt;blackboxsw&gt;</code> no worries at all stanguturi we like the interest</p> -<p>17:47 <code>&lt;stanguturi&gt;</code> We just noticed that on Ubuntu 18.04 VMs, open-vm-tools service doesn't work with cloud-init.</p> -<p>17:47 <code>&lt;stanguturi&gt;</code> We didn't have any issues on 17.10. But only found in 18.04</p> -<p>17:47 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1750780">https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1750780</a></p> -<p>17:48 <code>&lt;ubot5</code>&gt;` Ubuntu bug 1750780 in open-vm-tools (Ubuntu Xenial) "Race with local file systems can make open-vm-tools fail to start" [Undecided,Triaged]</p> -<p>17:48 <code>&lt;stanguturi&gt;</code> I first logged the bug <a href="https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1667831">https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1667831</a> and it was fixed and it was mentioned that now the bug 1750780 came up.</p> -<p>17:48 <code>&lt;ubot5</code>&gt;` Ubuntu bug 1667831 in open-vm-tools (Ubuntu) "cloud-init dependency for open-vm-tools service" [Undecided,Fix released]</p> -<p>17:51 <code>&lt;smoser&gt;</code> stanguturi: i'll talk with christian tomorrow about the bug there.</p> -<p>17:52 <code>&lt;stanguturi&gt;</code> ok Thanks Scott.</p> -<p>17:52 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1667831">https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1667831</a></p> -<p>17:52 <code>&lt;ubot5</code>&gt;` Ubuntu bug 1667831 in open-vm-tools (Ubuntu) "cloud-init dependency for open-vm-tools service" [Undecided,Fix released]</p> -<p>17:52 <code>&lt;blackboxsw&gt;</code> ok I think we'll have to call this meeting a close for this week. Thanks again stanguturi for the help/chat here.</p> -<p>17:53 <code>&lt;blackboxsw&gt;</code> as always I'll post this log to the site:</p> -<p>17:53 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io">https://cloud-init.github.io</a></p> -<p>17:53 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-02-16T16:08:00+00:002018-02-16T16:08:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-02-16:/status-2018-02-16.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 16 Feb at 16:08 &mdash; 17:18 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-02-16-16.08.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-02-16-16.08.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent changes</h3> -<p>The discussion about "Recent changes" started at 16:08.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://jenkins.ubuntu.com/server/view/cloud-init/">https://jenkins.ubuntu.com/server/view …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 16 Feb at 16:08 &mdash; 17:18 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-02-16-16.08.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-02-16-16.08.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent changes</h3> -<p>The discussion about "Recent changes" started at 16:08.</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> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:18.</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="https://bugs.launchpad.net/cloud-init/+bug/1749722">https://bugs.launchpad.net/cloud-init/+bug/1749722</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~rski/cloud-init/+git/cloud-init/+merge/312284">https://code.launchpad.net/~rski/cloud-init/+git/cloud-init/+merge/312284</a> </li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bug/1749722">https://bugs.launchpad.net/cloud-init/+bug/1749722</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~rski/cloud-init/+git/cloud-init/+merge/312284">https://code.launchpad.net/~rski/cloud-init/+git/cloud-init/+merge/312284</a> </li> -</ul> -<h3>cloud-init version 18.1 release (2/23/2018)</h3> -<p>The discussion about "cloud-init version 18.1 release (2/23/2018)" started at 16:27.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~sankaraditya/cloud-init/+git/cloud-init/+merge/337736">https://code.launchpad.net/~sankaraditya/cloud-init/+git/cloud-init/+merge/337736</a> </li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bug/1749980">https://bugs.launchpad.net/cloud-init/+bug/1749980</a> </li> -</ul> -<h3>Office hours (next ~30 mins)</h3> -<p>The discussion about "Office hours (next ~30 mins)" started at 16:42.</p> -<ul> -<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 (64)</li> -<li>stanguturi (19)</li> -<li>smoser (17)</li> -<li>ubot5 (6)</li> -<li>meetingology (4)</li> -<li>powersj (3)</li> -<li>rharper (2)</li> -<li>nacc (1)</li> -</ul> -<h2>Full Log</h2> -<p>16:04 <code>&lt;blackboxsw&gt;</code> hey folks thanks for joining in to another cloud-init biweekly status meeting</p> -<p>16:05 <code>&lt;blackboxsw&gt;</code> the early meeting day this week is to avoid hitting the upcoming US holiday on Monday</p> -<p>16:05 <code>&lt;blackboxsw&gt;</code> This meeting is probably going to be short, but we wanted to generate any discussion around the release we have scheduled for next week. I'll go through the following topics</p> -<p>16:05 <code>&lt;blackboxsw&gt;</code> recent changes, In-progress development, Release 18.1 Discussion, Office hours (30 mins)</p> -<p>16:05 <code>&lt;blackboxsw&gt;</code> Without further ado...</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status meeting</p> -<p>16:08 <code>&lt;meetingology&gt;</code> Meeting started Fri Feb 16 16:08:08 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:08 <code>&lt;meetingology&gt;</code> </p> -<p>16:08 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> much better thanks nacc</p> -<p>16:08 <code>&lt;nacc&gt;</code> blackboxsw: yw</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> #topic Recent changes</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> Cloud-init upstream team has been working on an SRU for Artful and Xenial.</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> We discovered a couple of SRU-blocking bugs on EC2 as well as cloud-init subcommands so we've landed a couple of fixes there which are queued for SRU now</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> * cloud-init status --wait blocks until all stages complete (LP: #1747965)</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> * SRU EC2 upgrade path fix for 'systemctl restart cloud-init.service' (LP:1748354)</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> * Fix ds-identify nocloud detection with bind mounted writable/system-data directory (LP: #1747070)</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> * Tests: include missing unitests in python2.6 environments. Fix py2.6 incompatilibilies</p> -<p>16:09 <code>&lt;ubot5&gt;</code> Launchpad bug 1747965 in cloud-init (Ubuntu) "cloud-init status reports done before boot is finished" [High,Fix released] <a href="https://launchpad.net/bugs/1747965">https://launchpad.net/bugs/1747965</a></p> -<p>16:09 <code>&lt;ubot5&gt;</code> Launchpad bug 1747070 in cloud-init "ds-identify does not see nocloud seed in core snap" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1747070">https://launchpad.net/bugs/1747070</a></p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> * Fixed centos cloud-init build and test tooliing</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> * SUSE: Fix groups used for ownership of cloud-init.log [RobertS]</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> thanks folks for continuing to push on quality of cloud-init releases.</p> -<p>16:12 <code>&lt;smoser&gt;</code> o/ thanks for starting blackboxsw</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> not sure if I'm missing any other content that has landed in the last week and a half</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> I also think powersj rharper may have sorted a couple of issues with storage on our common CI on Jenkins</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> #link <a href="https://jenkins.ubuntu.com/server/view/cloud-init/">https://jenkins.ubuntu.com/server/view/cloud-init/</a></p> -<p>16:14 <code>&lt;powersj&gt;</code> Yes CI is up and running again, I have more defensive statements in to prevent us from running out of storage</p> -<p>16:15 * blackboxsw is not sure, are there rumors we might have more hardware dedicated to jenkins in the future powersj ?</p> -<p>16:15 <code>&lt;powersj&gt;</code> We do, however it is our jenkins master that runs out of storage :\</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> ahh gotcha, SPOF</p> -<p>16:16 <code>&lt;powersj&gt;</code> yeah</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> ok, if no other work is 'complete'; let's jump topics</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> ahh forgot ryan landed</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> net: accept network-config in netplan format for renaming interfaces</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> per LP: #1709715</p> -<p>16:17 <code>&lt;ubot5&gt;</code> Launchpad bug 1709715 in cloud-init "cloud-init apply_net_config_names doesn't grok v2 configs" [Medium,Confirmed] <a href="https://launchpad.net/bugs/1709715">https://launchpad.net/bugs/1709715</a></p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> So we are working toward quality on the 18.1 release for next week.</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> Ubuntu specifically is finalizing verification on cloud-init 17.2.35 update for Xenial and Artful series (expectation is that this SRU will be public in 1 week). 17.2.35 is a snapshot of tip from a couple days ago</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> we've also published tip of cloud-init master to bionic to keep the development release up to date with latest cloud-init</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> current ongoing work as always is on our trello board. we tried tidying up the cards a bit</p> -<p>16:20 <code>&lt;blackboxsw&gt;</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:21 <code>&lt;blackboxsw&gt;</code> we have upcoming branches for a new snap cloud-config module for configuring and maintaining snap packages</p> -<p>16:21 <code>&lt;rharper&gt;</code> <a href="https://bugs.launchpad.net/cloud-init/+bug/1749722">https://bugs.launchpad.net/cloud-init/+bug/1749722</a></p> -<p>16:21 <code>&lt;ubot5&gt;</code> Ubuntu bug 1749722 in cloud-init "NTP: take into account systemd-timesyncd where present" [Medium,In progress]</p> -<p>16:21 <code>&lt;rharper&gt;</code> I'm actively working on that</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> this snap work will obsolete snappy and snap_config modules, so expect that they'll be deprecated. in 18.1 and dropped completely in 18.2</p> -<p>16:22 <code>&lt;smoser&gt;</code> <a href="https://code.launchpad.net/~rski/cloud-init/+git/cloud-init/+merge/312284">https://code.launchpad.net/~rski/cloud-init/+git/cloud-init/+merge/312284</a></p> -<p>16:22 <code>&lt;smoser&gt;</code> i just moved that back into review</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/+bug/1749722">https://bugs.launchpad.net/cloud-init/+bug/1749722</a></p> -<p>16:22 <code>&lt;smoser&gt;</code> hope to take a lookc at it today.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~rski/cloud-init/+git/cloud-init/+merge/312284">https://code.launchpad.net/~rski/cloud-init/+git/cloud-init/+merge/312284</a></p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> so per rharper's; chrony will be first class citizen in cloud-init</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> per cards in our trello board TODO lane, any card above the 18.1 release card (and anything in Doing/Review lane) is something we want to land in the 18.1 release</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> ... next topic so we can talk about release</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> #topic cloud-init version 18.1 release (2/23/2018)</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> next thursday we want to cut tip of cloud-init with any features we want to fold into the 18.1 release</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> this point in the meeting is a good opportunity for us to discuss features and bugs that any folks think are a priority for this release</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> smoser we saw some talk about archlinux support/updates, do we know whether we've gotten any updates about gaps/needs/bugs there?</p> -<p>16:29 <code>&lt;stanguturi&gt;</code> @blackboxsw: I have two requests. One for the merge request and one about the bug.</p> -<p>16:29 <code>&lt;smoser&gt;</code> blackboxsw: i've not seen any more than that developer asked about here in the channel.</p> -<p>16:30 <code>&lt;stanguturi&gt;</code> @blackboxsw: Let me know if I can post my questions here or discuss them offline.</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> stanguturi: please do discuss here. open forum :)</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> if it gets too long a discussion, we can take it to your branch or email</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~sankaraditya/cloud-init/+git/cloud-init/+merge/337736">https://code.launchpad.net/~sankaraditya/cloud-init/+git/cloud-init/+merge/337736</a></p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> for reference right ?</p> -<p>16:31 <code>&lt;stanguturi&gt;</code> @blackboxsw: Thanks. I have a merge request posted at <a href="https://code.launchpad.net/~sankaraditya/cloud-init/+git/cloud-init/+merge/337736">https://code.launchpad.net/~sankaraditya/cloud-init/+git/cloud-init/+merge/337736</a></p> -<p>16:31 <code>&lt;stanguturi&gt;</code> Want this to get into 18.1 It's a low-risk fix. Should not break anything.</p> -<p>16:32 <code>&lt;stanguturi&gt;</code> Also, found a bug in ds-identify . <a href="https://bugs.launchpad.net/cloud-init/+bug/1749980">https://bugs.launchpad.net/cloud-init/+bug/1749980</a></p> -<p>16:32 <code>&lt;ubot5&gt;</code> Ubuntu bug 1749980 in cloud-init "ds-identify doesn't properly detect ISO" [Undecided,New]</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> ok just glancing at your branch now stanguturi looks fairly straight forward, and as always I'd like to see some unit tests covering that changeset</p> -<p>16:33 <code>&lt;stanguturi&gt;</code> @blackboxsw: We already have unit tests for DataSourceOVF. This actually doesn't add any new functionality. The existing test cases should be sufficient enough.</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> we have existing unit tests in tests/unittests/test_ds_identify.py which should be easy to extend for the additional detection</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> in ds-identify</p> -<p>16:34 <code>&lt;blackboxsw&gt;</code> yeah I was thinking more about ds-identify specifically</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> all said though, that branch looks low-risk and we can probably get that landed before release.</p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> I'll add a card to trello for us to shepherd that in.</p> -<p>16:35 <code>&lt;stanguturi&gt;</code> @blackboxsw: Great. Thanks.</p> -<p>16:36 <code>&lt;stanguturi&gt;</code> @blackboxsw: Also I have a question about <a href="https://bugs.launchpad.net/cloud-init/+bug/1749980">https://bugs.launchpad.net/cloud-init/+bug/1749980</a> Any inputs will be great.</p> -<p>16:36 <code>&lt;ubot5&gt;</code> Ubuntu bug 1749980 in cloud-init "ds-identify doesn't properly detect ISO" [Undecided,New]</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> #link <a href="https://bugs.launchpad.net/cloud-init/+bug/1749980">https://bugs.launchpad.net/cloud-init/+bug/1749980</a></p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> looking</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> ohh good stanguturi we'll sort that bug and either provide more information on this</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> for that bug discussion, let's move it to the "office hours" topic which comes up next</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> I'd like smoser rharper to peek at that too</p> -<p>16:38 <code>&lt;stanguturi&gt;</code> @blackboxsw: Ok. Sure. Thanks</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> any other topics, branches or bugs that folks are itching to get in for 18.1 release?</p> -<p>16:41 <code>&lt;blackboxsw&gt;</code> kpcyrd: any opdates or concerns on archlinux that you are aware of currently?</p> -<p>16:42 <code>&lt;smoser&gt;</code> stanguturi: you can run a command there now ?</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> let's transition to office hours now</p> -<p>16:42 <code>&lt;smoser&gt;</code> 2 things</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> #topic Office hours (next ~30 mins)</p> -<p>16:43 <code>&lt;stanguturi&gt;</code> @smoser: Sorry. Didn't quite get the question.</p> -<p>16:43 <code>&lt;blackboxsw&gt;</code> And thanks all for joining. Any burning questions, bugs, branches that need discussion can be brought up now.</p> -<p>16:44 <code>&lt;stanguturi&gt;</code> @smoser: Oh. Are you asking if I can run any commands in my virtual machine right now.? Yeah. Sure.</p> -<p>16:44 <code>&lt;smoser&gt;</code> stanguturi: can you run stuff int hat system ?</p> -<p>16:44 <code>&lt;smoser&gt;</code> a.) cat /run/cloud-init/ds-identify.log</p> -<p>16:44 <code>&lt;smoser&gt;</code> b.) idstr="<a href="http://schemas.dmtf.org/ovf/environment/1">http://schemas.dmtf.org/ovf/environment/1</a>"</p> -<p>16:45 <code>&lt;smoser&gt;</code> grep --quiet --ignore-case "$idstr" /dev/sr0</p> -<p>16:45 <code>&lt;smoser&gt;</code> grep --quiet --ignore-case "$idstr" /dev/sr0 &amp;&amp; echo y || echo n</p> -<p>16:46 <code>&lt;smoser&gt;</code> stanguturi: basically the 'is_cdrom_ovf' should have gone down the path into that grep of the cdrom block device</p> -<p>16:48 <code>&lt;stanguturi&gt;</code> @smoser: grep --quiet --ignore-case "$idstr" /dev/sr0 returned "grep: /dev/sr0: Input/output error"</p> -<p>16:48 <code>&lt;stanguturi&gt;</code> @smoser: grep --quiet --ignore-case "$idstr" /dev/sr0 &amp;&amp; echo y || echo n returned "grep: /dev/sr0: Input/output error and then new line and then n'</p> -<p>16:48 <code>&lt;meetingology&gt;</code> stanguturi: Error: No closing quotation</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> heh thanks meetingology</p> -<p>16:50 <code>&lt;stanguturi&gt;</code> @smoser: Actually, read_fs_info doesn't DI_ISO9660_DEVS in my system. and because of this, dscheck_OVF returns DS_NOT_FOUND.</p> -<p>16:51 <code>&lt;smoser&gt;</code> stanguturi: what release are you on ?</p> -<p>16:51 <code>&lt;stanguturi&gt;</code> Trying it on 17.04 zesty desktop</p> -<p>16:52 <code>&lt;stanguturi&gt;</code> and tried with top of the tree code in cloud-init.</p> -<p>16:56 <code>&lt;smoser&gt;</code> stanguturi: could you potentially let me in via ssh ?</p> -<p>16:57 <code>&lt;stanguturi&gt;</code> @smoser: Sorry. It's on my private network. Will not be able to provide ssh.</p> -<p>16:58 <code>&lt;stanguturi&gt;</code> @smoser: We can do a webex conference if you want.</p> -<p>17:03 <code>&lt;smoser&gt;</code> stanguturi: can you ssh out of the node ?</p> -<p>17:03 <code>&lt;stanguturi&gt;</code> @smoser: Yes.</p> -<p>17:07 <code>&lt;smoser&gt;</code> ok. /query window</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> ok this triage will continue. if there are no other pressing bugs/concerns, we'll close out this meeting and keep pushing toward 18.1 upstream release next thursday</p> -<p>17:11 <code>&lt;blackboxsw&gt;</code> thanks again for your time folks. I'll post these minutes to the cloud-init github page</p> -<p>17:12 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloud-init.github.io">https://cloud-init.github.io</a></p> -<p>17:17 <code>&lt;blackboxsw&gt;</code> next meeting march 5th same "bat time" same "bat channel"</p> -<p>17:18 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-01-22T16:08:00+00:002018-01-22T16:08:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-01-22:/status-2018-01-22.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 22 Jan at 16:08 &mdash; 17:16 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-01-22-16.08.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-01-22-16.08.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent changes</h3> -<p>The discussion about "Recent changes" started at 16:10.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://github.com/boto/botocore/issues/1351">https://github.com/boto/botocore/issues …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init bi-weekly status meeting, 22 Jan at 16:08 &mdash; 17:16 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-01-22-16.08.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-01-22-16.08.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent changes</h3> -<p>The discussion about "Recent changes" started at 16:10.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://github.com/boto/botocore/issues/1351">https://github.com/boto/botocore/issues/1351</a> </li> -<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>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:24.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~dojordan/cloud-init/+git/cloud-init/+merge/334341">https://code.launchpad.net/~dojordan/cloud-init/+git/cloud-init/+merge/334341</a> </li> -<li><strong>LINK</strong>: <a href="https://jenkins.ubuntu.com/server/view/cloud-init/job/cloud-init-ci-nightly/">https://jenkins.ubuntu.com/server/view/cloud-init/job/cloud-init-ci-nightly/</a> </li> -</ul> -<h3>Office Hours (next 30 minutes)</h3> -<p>The discussion about "Office Hours (next 30 minutes)" started at 16:45.</p> -<ul> -<li><strong>LINK</strong>: <a href="http://paste.ubuntu.com/26438334/">http://paste.ubuntu.com/26438334/</a> </li> -<li><strong>LINK</strong>: <a href="http://paste.ubuntu.com/26438334/">http://paste.ubuntu.com/26438334/</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 (83)</li> -<li>smoser (23)</li> -<li>ajorg (16)</li> -<li>powersj (10)</li> -<li>ubot5 (6)</li> -<li>meetingology (3)</li> -<li>rharper (1)</li> -</ul> -<h2>Full Log</h2> -<p>16:08 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-init bi-weekly status meeting</p> -<p>16:08 <code>&lt;meetingology&gt;</code> Meeting started Mon Jan 22 16:08:22 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:08 <code>&lt;meetingology&gt;</code> </p> -<p>16:08 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> certianly ajorg :) (on office hours)</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> Welcome to another episode of cloud-init bi-weekly status. We'll chat about about cloud-init updates and in progress work, and we'l drop into office hours for ongoing discussions/bug work etc.</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> #topic Recent changes</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> Just walking through git-log for what we have committed in the last couple of weeks, here's the brief summary</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> thx smoser</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - shorten the message in the exception per powersj feedback</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - Use the same botocore session so the patched changes stick.</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - fix bad use of %</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - Fix console_log, improve comments and raise PlatformError on.</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - tests: Fix EC2 Platform to return console output as bytes.</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - tests: remove zesty as supported OS to test [Joshua Powers]</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - Do not log warning on config files that represent None. (LP: #1742479)</p> -<p>16:12 <code>&lt;ubot5&gt;</code> Launchpad bug 1742479 in cloud-init (Ubuntu) "setting manual_cache_clean causes warning" [Medium,Fix released] <a href="https://launchpad.net/bugs/1742479">https://launchpad.net/bugs/1742479</a></p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - tests: Use git hash pip dependency format for pylxd.</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - tests: add integration requirements text file [Joshua Powers]</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - MAAS: add check_instance_id based off oauth tokens. (LP: #1712680)</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - tests: update apt sources list test [Joshua Powers]</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - tests: clean up image properties [Joshua Powers]</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - tests: rename test ssh keys to avoid appearance of leaking private keys.</p> -<p>16:12 <code>&lt;ubot5&gt;</code> Launchpad bug 1712680 in maas-images "cloud-init re-generates network config every reboot overwriting manual admin changes on CentOS." [Undecided,New] <a href="https://launchpad.net/bugs/1712680">https://launchpad.net/bugs/1712680</a></p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> [Joshua Powers]</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - tests: Enable AWS EC2 Integration Testing [Joshua Powers]</p> -<p>16:12 <code>&lt;blackboxsw&gt;</code> - cli: cloud-init clean handles symlinks (LP: #1741093)</p> -<p>16:12 <code>&lt;ubot5&gt;</code> Launchpad bug 1741093 in cloud-init "cloud-init clean traceback on instance dir symlink" [Low,Fix committed] <a href="https://launchpad.net/bugs/1741093">https://launchpad.net/bugs/1741093</a></p> -<p>16:13 <code>&lt;ajorg&gt;</code> What's being patched in botocore?</p> -<p>16:13 <code>&lt;blackboxsw&gt;</code> So a number of changes went into integration test related work, separating out requirements files.</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> MAASDatasource now also has smarted cache handling based on oauth token renewal from the maas server</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> so botocore is used by integration tests only as a mechanism to talk to the instance under test... looking back at the specifics here</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> it might have just been shuffling out how and where we define the dependency</p> -<p>16:14 <code>&lt;smoser&gt;</code> blackboxsw: (my 'paste' to you was bad... <a href="http://paste.ubuntu.com/26438113/">http://paste.ubuntu.com/26438113/</a> is better, showing only those on master, not my local branch that was currently checked out )</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> heh, oopsie daisy let's paste again inline then</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> - tests: remove zesty as supported OS to test [Joshua Powers]</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> - Do not log warning on config files that represent None. (LP: #1742479)</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> - tests: Use git hash pip dependency format for pylxd.</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> - tests: add integration requirements text file [Joshua Powers]</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> - MAAS: add check_instance_id based off oauth tokens. (LP: #1712680)</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> - tests: update apt sources list test [Joshua Powers]</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> - tests: clean up image properties [Joshua Powers]</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> - tests: rename test ssh keys to avoid appearance of leaking private keys.</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> [Joshua Powers]</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> - tests: Enable AWS EC2 Integration Testing [Joshua Powers]</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> - cli: cloud-init clean handles symlinks (LP: #1741093)</p> -<p>16:15 <code>&lt;ubot5&gt;</code> Launchpad bug 1742479 in cloud-init (Ubuntu) "setting manual_cache_clean causes warning" [Medium,Fix released] <a href="https://launchpad.net/bugs/1742479">https://launchpad.net/bugs/1742479</a></p> -<p>16:15 <code>&lt;ubot5&gt;</code> Launchpad bug 1712680 in maas-images "cloud-init re-generates network config every reboot overwriting manual admin changes on CentOS." [Undecided,New] <a href="https://launchpad.net/bugs/1712680">https://launchpad.net/bugs/1712680</a></p> -<p>16:15 <code>&lt;ubot5&gt;</code> Launchpad bug 1741093 in cloud-init "cloud-init clean traceback on instance dir symlink" [Low,Fix committed] <a href="https://launchpad.net/bugs/1741093">https://launchpad.net/bugs/1741093</a></p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> ok the real deal, that looks better</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> ahh ajorg that interim commit message on botocore was about integration tests caching the session information during testing so we don't recreate that session with every ssh connection to the instance</p> -<p>16:16 <code>&lt;blackboxsw&gt;</code> just a little time savings per review comments on powersj branch I believe</p> -<p>16:17 <code>&lt;ajorg&gt;</code> okay, so nothing that needs to get upstreamed to botocore?</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> I don't think so, powersj smoser I have vague recollection of someone filing an upstream botocore issue. did we have to do that for something else though?</p> -<p>16:18 <code>&lt;powersj&gt;</code> <a href="https://github.com/boto/botocore/issues/1351">https://github.com/boto/botocore/issues/1351</a></p> -<p>16:18 <code>&lt;powersj&gt;</code> that was the issue smoser put in ^</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> nice recall powersj thanks.</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> #link <a href="https://github.com/boto/botocore/issues/1351">https://github.com/boto/botocore/issues/1351</a></p> -<p>16:20 <code>&lt;smoser&gt;</code> ajorg: you can read that bug. imo they have a data loss error, but not one that they can easily fix without causing failures in places that previously ran fine.</p> -<p>16:20 <code>&lt;ajorg&gt;</code> I'll ask them to re-open it.</p> -<p>16:21 <code>&lt;ajorg&gt;</code> At the very least they should answer your last.</p> -<p>16:21 <code>&lt;smoser&gt;</code> thanks.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> Generally anything significant that we have landed (and any inprogress work) should be available at the following link.</p> -<p>16:22 <code>&lt;blackboxsw&gt;</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:23 <code>&lt;blackboxsw&gt;</code> anything else we should note over the last couple weeks?</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> otherwise I'll switch to ongoing work topic</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> As you may have seen last week, we've gotten through a few passes and discussions around dojordan's branch to define pre-provisioning</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~dojordan/cloud-init/+git/cloud-init/+merge/334341">https://code.launchpad.net/~dojordan/cloud-init/+git/cloud-init/+merge/334341</a></p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> some of that discussion resulted in a new context manager: EphemeralDHCPv4 to support a sandboxed dhclient request on an instance.</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> this context manager affects Ec2 datasource a bit as it encapsulates all of the dhcp request -&gt;` EphemeralIPV4Network calls that Ec2 was doing</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> there may be a couple other datasources that follow suit with this type of sandboxed dhcp request in weeks to come</p> -<p>16:28 <code>&lt;ajorg&gt;</code> glad it turned out to be generally useful rather than only specifically to ec2</p> -<p>16:28 <code>&lt;blackboxsw&gt;</code> absolutely</p> -<p>16:30 <code>&lt;blackboxsw&gt;</code> Some other in-progress bits look like we might try focusing a bit more on chrony support and gettting robjo's branches some more eyes.</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> and some work on Ubuntu snappy support per the snappy and snap config modules.</p> -<p>16:31 <code>&lt;smoser&gt;</code> dojordan: i just put one comment on your mp. /me thanks dojordan again for his patience.</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> rharper: smoser powersj anything more in the immediate pipeline that I'm missing/</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> ?</p> -<p>16:32 <code>&lt;smoser&gt;</code> blackboxsw: we should get the EphemeralDHCP thingy into the digital ocean datasource also.</p> -<p>16:32 <code>&lt;rharper&gt;</code> blackboxsw: a reply to the network discussion on the list from the azure folks and robjo</p> -<p>16:32 <code>&lt;ajorg&gt;</code> I took another look at <a href="https://code.launchpad.net/~yeazelm/cloud-init/+git/cloud-init/+merge/331897">https://code.launchpad.net/~yeazelm/cloud-init/+git/cloud-init/+merge/331897</a> and saw that origin/master seems to be failing some of the integration tests too.</p> -<p>16:32 <code>&lt;ajorg&gt;</code> (at least for me, locally, on a 16.04 instance)</p> -<p>16:32 <code>&lt;blackboxsw&gt;</code> ahhh right forgot about all your work there rharper, thanks!</p> -<p>16:33 <code>&lt;smoser&gt;</code> ajorg: <a href="https://jenkins.ubuntu.com/server/view/cloud-init/job/cloud-init-ci-nightly/">https://jenkins.ubuntu.com/server/view/cloud-init/job/cloud-init-ci-nightly/</a></p> -<p>16:33 <code>&lt;smoser&gt;</code> that is nigytly run of trunk</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> #link <a href="https://jenkins.ubuntu.com/server/view/cloud-init/job/cloud-init-ci-nightly/">https://jenkins.ubuntu.com/server/view/cloud-init/job/cloud-init-ci-nightly/</a></p> -<p>16:34 <code>&lt;ajorg&gt;</code> I'll try blackholing IMDS on my instance. Could be that's interfering with something.</p> -<p>16:35 <code>&lt;smoser&gt;</code> it is red, but 218 (green) and 219 (red) used the same git has on trunk (5cc0b19b8).</p> -<p>16:35 <code>&lt;ajorg&gt;</code> I'll follow up during office hours</p> -<p>16:36 <code>&lt;smoser&gt;</code> can you give me example of your failures ? we had "disk full" errors recently on our jenkins, so that might be the cause of the issue for 291.</p> -<p>16:36 <code>&lt;smoser&gt;</code> s/291/219/</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> I don't remember seeing that traceback recently. w/ warning messages present in cloud-init</p> -<p>16:36 <code>&lt;smoser&gt;</code> powersj: ? can you explain lxc timeout failure at</p> -<p>16:36 <code>&lt;smoser&gt;</code> <a href="https://jenkins.ubuntu.com/server/view/cloud-init/job/cloud-init-ci-nightly/219/consoleFull">https://jenkins.ubuntu.com/server/view/cloud-init/job/cloud-init-ci-nightly/219/consoleFull</a></p> -<p>16:37 <code>&lt;powersj&gt;</code> smoser: we discovered that our qemu-migration test was installing lxd from the archive and causing conflicts with the snap installed lxd</p> -<p>16:37 <code>&lt;powersj&gt;</code> I have a message to christian to prevent it, and I have already cleaned it up</p> -<p>16:37 <code>&lt;powersj&gt;</code> so new runs should pass</p> -<p>16:37 <code>&lt;ajorg&gt;</code> 2018-01-22 16:19:03,550 - tests.cloud_tests - WARNING - test case: modules/ssh_import_id failed TestSshImportId.test_no_stages_errors with: AssertionError: 1 != 0 : errors ['(\'ssh-import-id\', ProcessExecutionError("Unexpected error while running command.\nCommand: [\'sudo\', \'-Hu\', \'ubuntu\', \'ssh-import-id\', \'gh:powersj\', \'lp:smoser\']\nExit code: 1\nReason: -\nStdout: -\nStderr: -",))'] were encountered in stage m</p> -<p>16:38 <code>&lt;smoser&gt;</code> hm.. well, that will hit launchpad.net over https</p> -<p>16:38 <code>&lt;smoser&gt;</code> cloud-init-output.log probaly has more info (should be collected)</p> -<p>16:38 <code>&lt;powersj&gt;</code> the actual error is: File "/var/lib/jenkins/slaves/torkoal/workspace/cloud-init-ci-nightly/tests/cloud_tests/platforms/instances.py", line 142, in _wait_for_system</p> -<p>16:38 <code>&lt;powersj&gt;</code> raise OSError('timeout: after {}s system not started'.format(time))</p> -<p>16:38 <code>&lt;powersj&gt;</code> it is because when the qemu tests installed lxd it didn't initialize lxd networking</p> -<p>16:38 <code>&lt;powersj&gt;</code> so no IP is received</p> -<p>16:39 <code>&lt;smoser&gt;</code> ajorg: would you have had outbound access to launchpad https ? if not, then that'd be expected failure.</p> -<p>16:40 <code>&lt;smoser&gt;</code> oh, and i guess 'gh:powersj' (github)</p> -<p>16:40 <code>&lt;ajorg&gt;</code> smoser: I'll check some things, but in short yes. Maybe lxc is being weird?</p> -<p>16:40 <code>&lt;smoser&gt;</code> i dont like our user names in that test though...</p> -<p>16:40 <code>&lt;powersj&gt;</code> smoser: we could use the bot instead</p> -<p>16:42 <code>&lt;ajorg&gt;</code> smoser: it's a public ec2 instance with no special outbound rules, and I can connect to public https sites from a normal session.</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> hrm, ok let's chat about what we can do to anonymize or drop that type of test data if we can</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> probably time to kick over to office hours</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next 30 minutes)</p> -<p>16:45 <code>&lt;smoser&gt;</code> powersj: well, i think i'd prefer some public key that we state "no one has the private key for this."</p> -<p>16:46 <code>&lt;smoser&gt;</code> obviously we could lie about that, but one would <em>expect</em> that you and I would gain access to the system using our public keys.</p> -<p>16:46 <code>&lt;smoser&gt;</code> it doens't make me feel a lot better that a bot could/can.</p> -<p>16:47 <code>&lt;ajorg&gt;</code> Is there a way to limit integration testing to a specific test?</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> Feel free to bring up any topic/bugs/branches/features you'd like discussion on. We can also continue our discussion on the ssh key imports in teting</p> -<p>16:47 <code>&lt;ajorg&gt;</code> (takes a long time to run the full suite)</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> ajorg: yes</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> (reverse-i-search)`cloud_t': python3 -m tests.cloud_tests run --os-name=artful --platform=nocloud-kvm --preserve-data --data-dir=../results --verbose -t modules/locale -t modules/set_password</p> -<p>16:48 <code>&lt;ajorg&gt;</code> thanks, that should help</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> ajorg: you can specify the test names (like modules/set_password) and modules/locale in this test</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> yeah those are short ones I frequently test with</p> -<p>16:49 <code>&lt;smoser&gt;</code> <a href="http://paste.ubuntu.com/26438334/">http://paste.ubuntu.com/26438334/</a></p> -<p>16:49 <code>&lt;smoser&gt;</code> that is what i use. and yeah... we've discussed that integration test could be easier to run :)</p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> #link <a href="http://paste.ubuntu.com/26438334/">http://paste.ubuntu.com/26438334/</a></p> -<p>16:49 <code>&lt;blackboxsw&gt;</code> nice 1</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> smoser: to have a public key we know nobody has a private key for would that mean we'd need a separate github account (or maybe just an additional key associated w/ our bot account in gh</p> -<p>16:51 * blackboxsw checks github for authorizing multiple keys.</p> -<p>16:51 <code>&lt;blackboxsw&gt;</code> hrm, that wouldn't work as we need gh:ubuntu-server-bot (one key) n/m</p> -<p>16:52 <code>&lt;ajorg&gt;</code> I've got meetings most of today, so I'll have to follow up later. thanks everyone!</p> -<p>16:52 <code>&lt;blackboxsw&gt;</code> thanks ajorg</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> so, bot account for the time being is better than powersj owning the testing world ;)</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> but I'm not too concerned about it as this are supposed to be throw away instances</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> but I'm not too concerned about it as there instances under test are supposed to be throw away instances</p> -<p>17:00 <code>&lt;blackboxsw&gt;</code> <em>these instances</em>.... anyway</p> -<p>17:04 <code>&lt;smoser&gt;</code> blackboxsw: right. it would require users on both those services .</p> -<p>17:14 <code>&lt;blackboxsw&gt;</code> alrighty. think we're at the close of office hours. Last call?</p> -<p>17:16 <code>&lt;blackboxsw&gt;</code> Thanks for your time and contributions to cloud-init folks!</p> -<p>17:16 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2018-01-08T16:03:00+00:002018-01-08T16:03:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2018-01-08:/status-2018-01-08.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-inin bi-weekly status meeting, 08 Jan at 16:03 &mdash; 17:15 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-01-08-16.03.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-01-08-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="https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin">https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-inin bi-weekly status meeting, 08 Jan at 16:03 &mdash; 17:15 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-01-08-16.03.log.html">http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-01-08-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="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="https://cloudinit.readthedocs.io/en/latest/topics/tests.html#ec2">https://cloudinit.readthedocs.io/en/latest/topics/tests.html#ec2</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:22.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://trello.com/c/AYaCdQyT">https://trello.com/c/AYaCdQyT</a> </li> -<li><strong>LINK</strong>: <a href="https://trello.com/c/xyqxyOxg">https://trello.com/c/xyqxyOxg</a> </li> -<li><strong>LINK</strong>: <a href="https://trello.com/c/AYaCdQyT/21-cloud-init-query-standardized-json-information">https://trello.com/c/AYaCdQyT/21-cloud-init-query-standardized-json-information</a> </li> -</ul> -<h3>Office Hours (next 30 minutes)</h3> -<p>The discussion about "Office Hours (next 30 minutes)" started at 16:46.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/334992">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/334992</a> </li> -<li><strong>LINK</strong>: <a href="http://jinja.pocoo.org/docs/2.10/api/#policies">http://jinja.pocoo.org/docs/2.10/api/#policies</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 (99)</li> -<li>ajorg (45)</li> -<li>smoser (19)</li> -<li>rharper (9)</li> -<li>robjo (5)</li> -<li>powersj (4)</li> -<li>meetingology (3)</li> -<li>smoser1 (2)</li> -<li>ubot5 (1)</li> -</ul> -<h2>Full Log</h2> -<p>16:03 <code>&lt;blackboxsw&gt;</code> #startmeeting Cloud-inin bi-weekly status meeting</p> -<p>16:03 <code>&lt;meetingology&gt;</code> Meeting started Mon Jan 8 16:03:53 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:03 <code>&lt;meetingology&gt;</code> </p> -<p>16:03 <code>&lt;meetingology&gt;</code> Available commands: action commands idea info link nick</p> -<p>16:04 <code>&lt;blackboxsw&gt;</code> Happy 2018 cloud-initers! Thanks ajorg for helping kick us off.</p> -<p>16:04 <code>&lt;blackboxsw&gt;</code> Welcome back from break hope the holidays were good for folks.</p> -<p>16:09 <code>&lt;blackboxsw&gt;</code> #topic Recent changes</p> -<p>16:04 <code>&lt;blackboxsw&gt;</code> It</p> -<p>16:05 <code>&lt;blackboxsw&gt;</code> It's been a while since we've held the meeting due to holidays and vacation time. So, not a ton of content to report for the last bit. Digging up those details now</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> Testing of 17.2 on EC2, Azure, and GCE and release to Ubuntu Bionic</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> Complete 17.1.46 SRU to Ubuntu Xenial, Zesty, and Artful</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> Fix documentation around 'init' mode for modules subcommand (LP: #1736600)</p> -<p>16:06 <code>&lt;blackboxsw&gt;</code> Tooling to merge community authored branches into master</p> -<p>16:06 <code>&lt;ubot5&gt;</code> Launchpad bug 1736600 in cloud-init "CLI: cloud-init modules -h documents unsupported --mode init" [Low,Fix committed] <a href="https://launchpad.net/bugs/1736600">https://launchpad.net/bugs/1736600</a></p> -<p>16:07 <code>&lt;blackboxsw&gt;</code> So the canonical side of the team worked a bit on getting the latest SRU updates 17.1.46 into Xenial, Zesty and artful. The testing and verification of that release took a bit of time, but we are getting better(faster)</p> -<p>16:07 <code>&lt;blackboxsw&gt;</code> I think this last SRU only took us 2 weeks instead of 4 weeks. so that frees up more time on upstream reviews and increasing cloud-init's velocity</p> -<p>16:07 <code>&lt;ajorg&gt;</code> great</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> we also added team tools for streamlining community authored branches. so that we stop slowing folks down :/</p> -<p>16:08 <code>&lt;blackboxsw&gt;</code> then the only problem is the reviewer :)</p> -<p>16:10 <code>&lt;blackboxsw&gt;</code> Also 17.2 release was 'cut' prior to Christmas break, this opened master up for more changes to land. so we've pulled in good fixes for VMWare NoCloud and SLES</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> digging up the changests now.</p> -<p>16:11 <code>&lt;blackboxsw&gt;</code> Also, keep in touch with our active development and the "done" lane on trello. It's out bookkeeper for anything we are working and Done represents anything landed</p> -<p>16:11 <code>&lt;blackboxsw&gt;</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:13 <code>&lt;blackboxsw&gt;</code> so high-level content that landed between 17.1.46 and 17.2:</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> * CLI added the clean and status subcommands</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> * Support for identifying OVF datasource provided by VMware</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> * NoCloudKVM tests now run in continuous integration</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> * Formalize DataSource get_data and related properties</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> * Remove prettytable dependency and introduce simpletable</p> -<p>16:14 <code>&lt;blackboxsw&gt;</code> * VMWare pre and post-customization script support</p> -<p>16:15 <code>&lt;blackboxsw&gt;</code> Thanks ajorg I think you were the author of note on simpletable stuff, it's nice to drop dependencies where we can to increase speed of cloud-init</p> -<p>16:15 <code>&lt;ajorg&gt;</code> it was done selfishly</p> -<p>16:15 <code>&lt;ajorg&gt;</code> we dislike taking on new dependencies :-)</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> and thanks to robjo(suse) maitree(vmware) too and dojordan and Ryan McCabe(redhat) for recent branches too</p> -<p>16:17 <code>&lt;blackboxsw&gt;</code> :)</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> Post our 17.2 release we've started work on improved integration..... I think we just got powersj's ec2 integration tests landed right johs?</p> -<p>16:18 <code>&lt;blackboxsw&gt;</code> josh even</p> -<p>16:18 <code>&lt;powersj&gt;</code> \o/ yep!</p> -<p>16:18 <code>&lt;ajorg&gt;</code> nice</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> sweet, so an extra security blanked for us when we have significant changesets landed in master to ensure ec2 is happy.</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> powersj: what are out plans for continuous integration frequency</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> with ec2 specifically</p> -<p>16:19 <code>&lt;ajorg&gt;</code> Can those integration tests be run by others with EC2 accounts?</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> ajorg: yes they can</p> -<p>16:19 <code>&lt;powersj&gt;</code> I am working on the jenkins jobs this week and hope to have a weekly run as well as a manual run for backport testing</p> -<p>16:19 <code>&lt;blackboxsw&gt;</code> I'll get the cmdline</p> -<p>16:19 <code>&lt;ajorg&gt;</code> thanks!</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> tox -e citests -m tests.cloud_tests run --os-name=artful --platform=ec2 --preserve-data --data-dir=../results --verbose</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> or something like that</p> -<p>16:20 <code>&lt;ajorg&gt;</code> got it</p> -<p>16:20 <code>&lt;ajorg&gt;</code> thanks!</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> powersj: documented it too I think</p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> getting link</p> -<p>16:20 <code>&lt;powersj&gt;</code> <a href="https://cloudinit.readthedocs.io/en/latest/topics/tests.html#ec2">https://cloudinit.readthedocs.io/en/latest/topics/tests.html#ec2</a></p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> #link <a href="https://cloudinit.readthedocs.io/en/latest/topics/tests.html#ec2">https://cloudinit.readthedocs.io/en/latest/topics/tests.html#ec2</a></p> -<p>16:20 <code>&lt;blackboxsw&gt;</code> :)</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> excellent work Josh</p> -<p>16:21 <code>&lt;powersj&gt;</code> thanks for all the reviews :)</p> -<p>16:21 <code>&lt;blackboxsw&gt;</code> anything else I'm missing about landed work? rharper powersj smoser1 ?</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> otherwise next topic</p> -<p>16:22 <code>&lt;rharper&gt;</code> blackboxsw: nothing from me</p> -<p>16:22 <code>&lt;blackboxsw&gt;</code> #topic In-progress Development</p> -<p>16:23 <code>&lt;blackboxsw&gt;</code> So we've got a fairly healthy review queue that we need to get through as we get the year started....</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> we also have a few things we are in flight currently:</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> - continuous integration improvements per powersj</p> -<p>16:24 <code>&lt;blackboxsw&gt;</code> - dropping dependence on ifup ifdown utils where possible as that's not supported (or installed in some cases) in systemd world</p> -<p>16:24 <code>&lt;smoser1&gt;</code> blackboxsw: wow. sorry, missing.</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> who is that smoser1 guy anyway</p> -<p>16:25 <code>&lt;smoser1&gt;</code> yeah, i didnt see anything missing sorry.</p> -<p>16:25 <code>&lt;smoser&gt;</code> wonder how that happened.</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> welcome ;)</p> -<p>16:25 <code>&lt;blackboxsw&gt;</code> - netplan improvements per rharper and jinja template support for all cloud-config modules</p> -<p>16:26 <code>&lt;blackboxsw&gt;</code> - and softlayer support per smoser</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> know the Azure guys are also posting a couple branches on getting a pre-provisioning setup going for thier datasource which looks pretty exciting</p> -<p>16:27 <code>&lt;blackboxsw&gt;</code> I can't think of anything else off the top of my head.</p> -<p>16:28 <code>&lt;robjo&gt;</code> chrony support</p> -<p>16:28 <code>&lt;ajorg&gt;</code> we're only talking feature work in this topic?</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> any in progress development to highlight is fair game. bug work. refactoring, feature etc</p> -<p>16:29 <code>&lt;blackboxsw&gt;</code> +10 robjo and again thanks for working with us getting all those branches up and (hopefully soon) landed</p> -<p>16:29 <code>&lt;ajorg&gt;</code> what does "jinja template support for all cloud-config modules" mean?</p> -<p>16:31 <code>&lt;ajorg&gt;</code> I'd guess most modules don't need templating?</p> -<p>16:31 <code>&lt;blackboxsw&gt;</code> ajorg: two things. 1. since we have now landed /run/cloud-instance/instance-data.json to store metadata/userdata it'd be that #cloud-config can new be specified with ## template:jinja header and could leverage anything jinjia has to offer plus sourcing any of the instance-data.json metadata fields</p> -<p>16:33 <code>&lt;ajorg&gt;</code> Ah, right. Is that not being done above the module level?</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> so if people have repetitive or template-driven content in the runcmd or write_files portion or their #cloud-config they'd be able to leverage jinja templates etc</p> -<p>16:33 <code>&lt;smoser&gt;</code> ajorg: yes, above the module level.</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> ajorg: not anywhere in cloud-config currently</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> one sec I misunderstood the question</p> -<p>16:33 <code>&lt;blackboxsw&gt;</code> smoser: can you clarify what you mean?</p> -<p>16:33 <code>&lt;ajorg&gt;</code> I mean, shouldn't #cloud-config template expansion happen before the module sees the config?</p> -<p>16:34 <code>&lt;smoser&gt;</code> blackboxsw: we could/should also allow other part types to be rendered</p> -<p>16:34 <code>&lt;smoser&gt;</code> ttps://trello.com/c/xyqxyOxg</p> -<p>16:35 <code>&lt;smoser&gt;</code> er... bad url. in 2 ways</p> -<p>16:35 <code>&lt;ajorg&gt;</code> The the part handler would be the one to do that expansion.</p> -<p>16:35 <code>&lt;smoser&gt;</code> <a href="https://trello.com/c/AYaCdQyT">https://trello.com/c/AYaCdQyT</a></p> -<p>16:35 <code>&lt;blackboxsw&gt;</code> ahh ok, right that makes sense. I think the cut I made was limited in focus to cloud-config modules and custom scripts supporting the ## template:jinja header.. but nothing would preclude handling other parts</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> so the link to my WIP branch was</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> #link <a href="https://trello.com/c/xyqxyOxg">https://trello.com/c/xyqxyOxg</a></p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> and the general feature per smoser</p> -<p>16:36 <code>&lt;blackboxsw&gt;</code> #link <a href="https://trello.com/c/AYaCdQyT/21-cloud-init-query-standardized-json-information">https://trello.com/c/AYaCdQyT/21-cloud-init-query-standardized-json-information</a></p> -<p>16:36 <code>&lt;ajorg&gt;</code> Is there a design doc of some kind of this?</p> -<p>16:37 <code>&lt;blackboxsw&gt;</code> not yet.. but we probably should have a spec as it'd be a good template for the docs we'll need to write</p> -<p>16:38 <code>&lt;blackboxsw&gt;</code> scott captured most of the use cases we'd be going for in that last trello link above</p> -<p>16:38 <code>&lt;ajorg&gt;</code> Small example of where some clarity is needed: if Jinja is interpreting {foo} in a user-script, what will it do when it sees a shell variable ${foo}</p> -<p>16:38 <code>&lt;ajorg&gt;</code> ?</p> -<p>16:39 <code>&lt;smoser&gt;</code> you declare that the content is a jinja template</p> -<p>16:39 <code>&lt;smoser&gt;</code> if you provide it something that is not renderable as a jinja template</p> -<p>16:39 <code>&lt;smoser&gt;</code> then it will fail</p> -<p>16:39 <code>&lt;smoser&gt;</code> it requires input to explicitly say "this is jinja". it does not just attempt to render anything.</p> -<p>16:39 <code>&lt;smoser&gt;</code> (unless explicitly told to)</p> -<p>16:39 <code>&lt;blackboxsw&gt;</code> some brief working examples are in the description of the branch @ <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/334030">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/334030</a></p> -<p>16:40 <code>&lt;ajorg&gt;</code> Sure. But as a content author, I need to know if Jinja is going to try to render ${foo} or not.</p> -<p>16:40 <code>&lt;smoser&gt;</code> then as a content author you can read jinja docs :)</p> -<p>16:40 <code>&lt;blackboxsw&gt;</code> jinja would try to render {{ foo }}</p> -<p>16:40 <code>&lt;ajorg&gt;</code> :-</p> -<p>16:41 <code>&lt;smoser&gt;</code> ajorg: we'll document a simple case, and we can even document "for shell, you'll have to be aware that ...."</p> -<p>16:41 <code>&lt;smoser&gt;</code> but we're not going to document all of jinja</p> -<p>16:41 <code>&lt;ajorg&gt;</code> I see.</p> -<p>16:42 <code>&lt;ajorg&gt;</code> My understanding was that Jinja was highly customizable in what it interpreted and how, so that it's important to document how you've configured it to work.</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> and since to burden is on the #cloud-config or script writer to provide the header ## template: jinja\n#cloud-config\n they <em>should</em> understand what they are doing</p> -<p>16:42 <code>&lt;blackboxsw&gt;</code> we won't implicitly run the #cloud-config through jinja</p> -<p>16:43 <code>&lt;ajorg&gt;</code> I get that, no problem, what I'm saying is that Jinja is an engine that you configure to do something, not a markup that always does the same thing for everyone.</p> -<p>16:43 <code>&lt;ajorg&gt;</code> Am I making any sense?</p> -<p>16:44 <code>&lt;blackboxsw&gt;</code> understood (though I thought it was fairly constrained it it's application and functionality). We'll make sure that the mechanism by which jinja operates is well documented and confined as best we can... for our own sanity we don't want that template engine to be too flexible... too many tough support use cases</p> -<p>16:45 <code>&lt;blackboxsw&gt;</code> ok anything else for "In progress development" otherwise we can move to Office hours for 30 mins</p> -<p>16:46 <code>&lt;blackboxsw&gt;</code> #topic Office Hours (next 30 minutes)</p> -<p>16:47 <code>&lt;blackboxsw&gt;</code> robjo: you've got quite a few branches of goodness up for us to review. Any prioritization on those branches or just take them as we can?</p> -<p>16:47 <code>&lt;rharper&gt;</code> I don't think there are issues w.r.t jinja and shell; they use different variable escape methods, jinja uses {{ variable/expression }}; and it doesn't consume $ AFAIK, ajorg do you know differently ?</p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> #link <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/334992">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/334992</a></p> -<p>16:48 <code>&lt;blackboxsw&gt;</code> I'm guessing is top of the list</p> -<p>16:48 <code>&lt;ajorg&gt;</code> I saw {instance_id} at <a href="https://trello.com/c/AYaCdQyT/21-cloud-init-query-standardized-json-information">https://trello.com/c/AYaCdQyT/21-cloud-init-query-standardized-json-information</a> so I assumed it was being customized to look for { instead of {{</p> -<p>16:48 <code>&lt;robjo&gt;</code> blackboxsw: The chrony support should probably be the last as it will take longer over all and more back and forth</p> -<p>16:48 <code>&lt;ajorg&gt;</code> (for one thing)</p> -<p>16:49 <code>&lt;ajorg&gt;</code> rharper: also, there's the whole question of the "extends" feature</p> -<p>16:50 <code>&lt;ajorg&gt;</code> We integrated Jinja into an internal tool a few years back and we spent a very long time making sure the loaders did the right thing.</p> -<p>16:50 <code>&lt;blackboxsw&gt;</code> ajorg: I thought I read somewhere that you couldn't exend jinja for custom functions. maybe I was mistaken</p> -<p>16:50 <code>&lt;robjo&gt;</code> I am also not certain that the "re-write everything" on the first go around for chrony is really what we want to do initially</p> -<p>16:50 <code>&lt;ajorg&gt;</code> blackboxsw: I don't think I'm referring to custom functions</p> -<p>16:51 <code>&lt;robjo&gt;</code> That's probably where we ant to end up, but I am not certain that a "step function" approach is in order</p> -<p>16:51 <code>&lt;rharper&gt;</code> ajorg: hrm, I've always seen {{ variable }} or {% expression %}; so maybe blackboxsw can just update the templates;</p> -<p>16:51 <code>&lt;rharper&gt;</code> the examples in the cards</p> -<p>16:52 <code>&lt;ajorg&gt;</code> rharper: sure, that would have helped in this case.</p> -<p>16:52 <code>&lt;robjo&gt;</code> If we do go down the route of the step function I'll need more gudance then in rharper's comments</p> -<p>16:52 <code>&lt;ajorg&gt;</code> blackboxsw: I was referring to the ability of one template to extend another.</p> -<p>16:53 <code>&lt;ajorg&gt;</code> blackboxsw: and the question of where does the engine look when it's asked to extend another template. It can be tricky.</p> -<p>16:54 <code>&lt;blackboxsw&gt;</code> yeah I honestly hadn't gotten past step one of handling the template markup within an existing single template. so this may need a bit of thought/work</p> -<p>16:55 <code>&lt;ajorg&gt;</code> Personally, I'd be a lot happier with limiting things to Python format() templates, even though it means you can't have loops, but I won't get in the way as long as we're cognizant of the problems we can run into by accepting the full power of an advanced engine like Jinja.</p> -<p>16:56 <code>&lt;smoser&gt;</code> i'm not opposed to allowing ## template: python-format</p> -<p>16:56 <code>&lt;ajorg&gt;</code> heh</p> -<p>16:56 <code>&lt;smoser&gt;</code> honestly.</p> -<p>16:56 <code>&lt;smoser&gt;</code> you can pick a differnt name if you dont like that one.</p> -<p>16:57 <code>&lt;smoser&gt;</code> but we already use jinja, so it makes sense to support jinja</p> -<p>16:57 * smoser has to run. sorry.</p> -<p>16:57 <code>&lt;rharper&gt;</code> I do feel that supplying the template means the user is opting in; and specifically if we've got a good way to provide dry-run based on a instance.json and a script; that certainly can help folks work out the kinks in the template of their choosing</p> -<p>16:57 <code>&lt;ajorg&gt;</code> I'm really not opposed so much as wary of the extensive power of the thing</p> -<p>16:58 <code>&lt;rharper&gt;</code> ajorg: that's a fair warning; given you've experience here; help drawing the line is most welcome</p> -<p>16:58 <code>&lt;ajorg&gt;</code> I'm trying to think of a way to read in /etc/shadow using Jinja, you know?</p> -<p>16:58 <code>&lt;rharper&gt;</code> well, cloud-init is root anyhow; so, what's the deal with that ?</p> -<p>16:59 <code>&lt;blackboxsw&gt;</code> ajorg: heh, right though you can read that with your runcmd section in #cloud-config :)</p> -<p>16:59 <code>&lt;ajorg&gt;</code> If I can come up with a way to do it that doesn't make it look obvious that I'm doing it, and then post that as something others can copy, or use with #include <code>&lt;url&gt;</code> then I win.</p> -<p>16:59 <code>&lt;rharper&gt;</code> I don't think jinja makes that any more troublesome</p> -<p>17:00 <code>&lt;rharper&gt;</code> folks already wget | bash with shell they don't understand either</p> -<p>17:00 <code>&lt;ajorg&gt;</code> I suspect Jijna makes it more opaque.</p> -<p>17:01 <code>&lt;ajorg&gt;</code> The answer to "what file does Jinja read when I use {% extends foo %}" is a very lengthy "it depends"</p> -<p>17:02 <code>&lt;ajorg&gt;</code> anyway, I've said my piece</p> -<p>17:03 * ajorg is a bit of a template naysayer.</p> -<p>17:05 <code>&lt;blackboxsw&gt;</code> +1, there's one in every group. We'll try to keep that in mind as this feature evolves</p> -<p>17:05 <code>&lt;blackboxsw&gt;</code> :)</p> -<p>17:06 <code>&lt;ajorg&gt;</code> nice</p> -<p>17:06 <code>&lt;ajorg&gt;</code> :-)</p> -<p>17:06 <code>&lt;blackboxsw&gt;</code> any pet bugs, new features or burning reviews that need mention?</p> -<p>17:07 <code>&lt;blackboxsw&gt;</code> ajorg: we could do something simple like disable the extends option via policies</p> -<p>17:07 <code>&lt;blackboxsw&gt;</code> it looks like</p> -<p>17:08 <code>&lt;blackboxsw&gt;</code> #link <a href="http://jinja.pocoo.org/docs/2.10/api/#policies">http://jinja.pocoo.org/docs/2.10/api/#policies</a></p> -<p>17:08 <code>&lt;blackboxsw&gt;</code> or maybe I'm misunderstanding the issue I'll read up more on it</p> -<p>17:08 <code>&lt;ajorg&gt;</code> thanks</p> -<p>17:09 <code>&lt;ajorg&gt;</code> It looked like <a href="https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/334074">https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/334074</a> was blocking <a href="https://code.launchpad.net/~yeazelm/cloud-init/+git/cloud-init/+merge/331897">https://code.launchpad.net/~yeazelm/cloud-init/+git/cloud-init/+merge/331897</a> but shouldn't be anymore.</p> -<p>17:09 <code>&lt;ajorg&gt;</code> I'll remind Matt to try it again now.</p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> thanks good dela</p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> dela</p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> deal</p> -<p>17:13 <code>&lt;blackboxsw&gt;</code> geez</p> -<p>17:14 <code>&lt;blackboxsw&gt;</code> on that note. I think it's time for coffee</p> -<p>17:14 <code>&lt;blackboxsw&gt;</code> and time to end the meeting</p> -<p>17:14 <code>&lt;blackboxsw&gt;</code> Happy New Year again folks. Good to be back in the office.</p> -<p>17:15 <code>&lt;blackboxsw&gt;</code> thanks again for the chat, until next time..</p> -<p>17:15 <code>&lt;blackboxsw&gt;</code> #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2017-12-11T16:05:00+00:002017-12-11T16:05:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2017-12-11:/status-2017-12-11.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init 'bi-weekly' status meeting, 11 Dec at 16:05 &mdash; 17:22 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-12-11-16.05.log.html">http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-12-11-16.05.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:07.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://lists.launchpad.net/cloud-init/msg00114.html">https://lists.launchpad.net/cloud-init/msg00114 …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Cloud-init 'bi-weekly' status meeting, 11 Dec at 16:05 &mdash; 17:22 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-12-11-16.05.log.html">http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-12-11-16.05.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:07.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://lists.launchpad.net/cloud-init/msg00114.html">https://lists.launchpad.net/cloud-init/msg00114.html</a> </li> -<li><strong>LINK</strong>: <a href="http://cloud-init.github.io">http://cloud-init.github.io</a> </li> -</ul> -<h3>In-progress Development</h3> -<p>The discussion about "In-progress Development" started at 16:15.</p> -<ul> -<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/~paul-meyer/cloud-init/+git/cloud-init/+merge/334989">https://code.launchpad.net/~paul-meyer/cloud-init/+git/cloud-init/+merge/334989</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/335034">https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/335034</a> </li> -</ul> -<h3>Office Hours (for next 30 mins)</h3> -<p>The discussion about "Office Hours (for next 30 mins)" started at 16:38.</p> -<ul> -<li><strong>LINK</strong>: <a href="http://pastebin.ubuntu.com/26075842/">http://pastebin.ubuntu.com/26075842/</a> </li> -<li><strong>LINK</strong>: <a href="http://paste.ubuntu.com/26164503/">http://paste.ubuntu.com/26164503/</a> </li> -<li><strong>ACTION</strong>: blackboxsw bring up any updates in instance-data.json fields for discussion about common use-cases/patterns</li> -</ul> -<h2>Vote results</h2> -<h2>Action items, by person</h2> -<ul> -<li>blackboxsw</li> -<li>blackboxsw bring up any updates in instance-data.json fields for discussion about common use-cases/patterns</li> -</ul> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (83)</li> -<li>smoser (54)</li> -<li>ajorg (38)</li> -<li>robjo (32)</li> -<li>ubot5 (7)</li> -<li>meetingology (4)</li> -<li>powersj (2)</li> -<li>dpb1 (2)</li> -<li>rharper (2)</li> -</ul> -<h2>Full Log</h2> -<p>16:05 <code>&lt;blackboxsw</code>&gt; #startmeeting Cloud-init 'bi-weekly' status meeting</p> -<p>16:05 <code>&lt;meetingology</code>&gt; Meeting started Mon Dec 11 16:05:16 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:05 <code>&lt;meetingology</code>&gt; </p> -<p>16:05 <code>&lt;meetingology</code>&gt; Available commands: action commands idea info link nick</p> -<p>16:05 <code>&lt;smoser</code>&gt; thanks for hosting blackboxsw</p> -<p>16:05 <code>&lt;blackboxsw</code>&gt; no problemo.</p> -<p>16:05 <code>&lt;blackboxsw</code>&gt; happy holidays folks and thanks for joining.</p> -<p>16:07 <code>&lt;blackboxsw</code>&gt; #topic Recent Changes</p> -<p>16:07 <code>&lt;blackboxsw</code>&gt; As mentioned @ our 17.1 release, we're promising more frequent cloud-init releases.</p> -<p>16:08 <code>&lt;blackboxsw</code>&gt; smoser has mailed the list informing cloud-init interested parties that we are targeting a 17.2 release for Thursday this week</p> -<p>16:08 <code>&lt;blackboxsw</code>&gt; It's been a few weeks since we've hosted the meeting (I think we missed last meeting), so I'll post some of the development that has landed in trunk</p> -<p>16:08 <code>&lt;smoser</code>&gt; #link <a href="https://lists.launchpad.net/cloud-init/msg00114.html">https://lists.launchpad.net/cloud-init/msg00114.html</a></p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; * All integration tests now function with the nocloud-kvm backend</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; * Fix apport for cloud-name options (LP: #1722564)</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; * Improve warning message when templates aren't found (Robert Schweikert) (LP: #1730135)</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; * Perform null checks for enabled/disabled Red Hat repos (Dave Mulford)</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; * Fix openSUSE and SLES setup of /etc/hosts (Robert Schweikert) (LP: #1731022)</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; * Catch UrlError when #include'ing URLs (Andrew Jorgensen)</p> -<p>16:09 <code>&lt;ubot5</code>&gt; Launchpad bug 1722564 in Apport "apport question will not accept multi-character responses" [Undecided,Confirmed] <a href="https://launchpad.net/bugs/1722564">https://launchpad.net/bugs/1722564</a></p> -<p>16:09 <code>&lt;ubot5</code>&gt; Launchpad bug 1730135 in openstack-dev-sandbox ""Too much rain in Sydney"" [Undecided,New] <a href="https://launchpad.net/bugs/1730135">https://launchpad.net/bugs/1730135</a></p> -<p>16:09 <code>&lt;ubot5</code>&gt; Launchpad bug 1731022 in cloud-init "host template expansion does not work on SUSE distros" [High,Fix committed] <a href="https://launchpad.net/bugs/1731022">https://launchpad.net/bugs/1731022</a></p> -<p>16:09 <code>&lt;smoser</code>&gt; ajorg replied with a request for <a href="https://code.launchpad.net/~ajorgens/cloud-init/+git/cloud-init/+merge/329657">https://code.launchpad.net/~ajorgens/cloud-init/+git/cloud-init/+merge/329657</a></p> -<p>16:09 <code>&lt;smoser</code>&gt; that fell on deaf ears</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; * Released stable release update (SRU) of 17.1-27-geb292c18 (LP: #1721847)</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; * Cleanup dhclient background process after EC2 network discovery.</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; * ntp: fix configuration template rendering for openSUSE and SLES (Robert Schweikert) LP: #1726572</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; * fix manually running cloud-init after upgrade (LP: #1732917)</p> -<p>16:09 <code>&lt;ubot5</code>&gt; Launchpad bug 1721847 in cloud-init (Ubuntu Artful) "sru cloud-init 2017-10-06 (17.1-18-gd4f70470-0ubuntu1) updated to (17.1-27-geb292c18)" [Medium,Fix released] <a href="https://launchpad.net/bugs/1721847">https://launchpad.net/bugs/1721847</a></p> -<p>16:09 <code>&lt;ubot5</code>&gt; Launchpad bug 1726572 in cloud-init "ntp config handling inconsistent for SLES and openSUSE" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1726572">https://launchpad.net/bugs/1726572</a></p> -<p>16:09 <code>&lt;ubot5</code>&gt; Launchpad bug 1732917 in cloud-init "17.1 update breaks EC2 nodes" [High,Fix committed] <a href="https://launchpad.net/bugs/1732917">https://launchpad.net/bugs/1732917</a></p> -<p>16:09 <code>&lt;ajorg</code>&gt; truth</p> -<p>16:09 <code>&lt;smoser</code>&gt; ajorg: i will review shortly</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; * Queued upstream for merge into Bionic</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; * Queued 17.1.46 SRU for Xenial, Zesty, and Artful</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; * Fix EC2 race on sandboxed dhclient's pidfile during tempdir teardown (LP: #1735331)</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; * Enable Bionic in Integration Tests</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; * Create LXD and KVM Integration Tests in Jenkins</p> -<p>16:09 <code>&lt;ubot5</code>&gt; Launchpad bug 1735331 in cloud-init "ec2: zesty tempfile sandbox dhclient.pid file can't be created" [High,Fix committed] <a href="https://launchpad.net/bugs/1735331">https://launchpad.net/bugs/1735331</a></p> -<p>16:10 <code>&lt;blackboxsw</code>&gt; As of end of last week, we are trying to blitz the review queue and dust off anything that has been sitting too long</p> -<p>16:12 <code>&lt;blackboxsw</code>&gt; So a couple fixes went into Amazon's initial network setup, IPv6 support is live for Ubuntu series Xenial, Zesty, Artful and Bionic</p> -<p>16:13 <code>&lt;ajorg</code>&gt; cool</p> -<p>16:14 <code>&lt;blackboxsw</code>&gt; heh I blew that last topic. it should have been #topic Recent Changes.</p> -<p>16:14 <code>&lt;blackboxsw</code>&gt; anyway I'll fix it in the logs when I publish</p> -<p>16:15 <code>&lt;blackboxsw</code>&gt; As always , for historical docs from this meeting check this link</p> -<p>16:15 <code>&lt;blackboxsw</code>&gt; #link <a href="http://cloud-init.github.io">http://cloud-init.github.io</a></p> -<p>16:15 <code>&lt;blackboxsw</code>&gt; #topic In-progress Development</p> -<p>16:15 <code>&lt;blackboxsw</code>&gt; So we have an active queue that is pretty healthy still</p> -<p>16:15 <code>&lt;blackboxsw</code>&gt; #link <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a></p> -<p>16:16 <code>&lt;blackboxsw</code>&gt; smoser: rharper are we still trying to get through that queue as best we can for 17.2 or when do we think the window closes there?</p> -<p>16:16 <code>&lt;smoser</code>&gt; i think we can spend some more time on queue today.</p> -<p>16:16 <code>&lt;smoser</code>&gt; but that is about it really.</p> -<p>16:16 <code>&lt;blackboxsw</code>&gt; yeah, want some settle 'bake' time before the 17.2 cut on Thursday</p> -<p>16:17 <code>&lt;blackboxsw</code>&gt; We saw a couple Azure branches come in late last week.... Are there any branches folks are really excited about landing this week (today tomorrow?)</p> -<p>16:18 <code>&lt;blackboxsw</code>&gt; I had hoped to get through a couple of Robert's as they don't seem very contentious.</p> -<p>16:19 <code>&lt;smoser</code>&gt; the reporter bit seems pretty reasonable</p> -<p>16:19 <code>&lt;smoser</code>&gt; other than its not actually used anywhere in the mp</p> -<p>16:19 <code>&lt;smoser</code>&gt; ie, its non-contentious to add a reporter, but adding code that is not used is of not a lot of use :)</p> -<p>16:19 <code>&lt;blackboxsw</code>&gt; true</p> -<p>16:20 <code>&lt;ajorg</code>&gt; which mp is being discussed?</p> -<p>16:20 <code>&lt;smoser</code>&gt; (<a href="https://code.launchpad.net/~paul-meyer/cloud-init/+git/cloud-init/+merge/334989">https://code.launchpad.net/~paul-meyer/cloud-init/+git/cloud-init/+merge/334989</a>)</p> -<p>16:20 <code>&lt;blackboxsw</code>&gt; #link <a href="https://code.launchpad.net/~paul-meyer/cloud-init/+git/cloud-init/+merge/334989">https://code.launchpad.net/~paul-meyer/cloud-init/+git/cloud-init/+merge/334989</a></p> -<p>16:21 <code>&lt;ajorg</code>&gt; thanks</p> -<p>16:23 <code>&lt;blackboxsw</code>&gt; With the upcoming holidays I expect things will be pretty slow after mid-next week, so we won't likely be landing a lot before the first of the new year.</p> -<p>16:25 <code>&lt;robjo</code>&gt; If it's slow for you more time to review open merge proposals ;)</p> -<p>16:25 <code>&lt;blackboxsw</code>&gt; This week we are also trying to get an SRU into ubuntu xenial, zesty and artful for some VMware/OVF datasource fixes for ds-identify and for pre-cusomization marker files courtesty (smoser &amp; maitriyee)</p> -<p>16:26 <code>&lt;blackboxsw</code>&gt; <em>courtesy</em> rather</p> -<p>16:26 <code>&lt;smoser</code>&gt; ajorg: you could ping matthew on <a href="https://code.launchpad.net/~yeazelm/cloud-init/+git/cloud-init/+merge/331897">https://code.launchpad.net/~yeazelm/cloud-init/+git/cloud-init/+merge/331897</a></p> -<p>16:27 <code>&lt;ajorg</code>&gt; yup</p> -<p>16:27 <code>&lt;blackboxsw</code>&gt; and I know powersj is working on EC2 integration test support for cloud-init</p> -<p>16:27 <code>&lt;powersj</code>&gt; yep!</p> -<p>16:27 <code>&lt;powersj</code>&gt; Hoping to have an initial MP up this week</p> -<p>16:27 <code>&lt;blackboxsw</code>&gt; it's gonna be excellent to automatically test these releases</p> -<p>16:28 <code>&lt;blackboxsw</code>&gt; powersj: rharper smoser anything else in progress?</p> -<p>16:28 <code>&lt;rharper</code>&gt; nothing here</p> -<p>16:28 <code>&lt;ajorg</code>&gt; oh very nice.</p> -<p>16:28 <code>&lt;dpb1</code>&gt; powersj: \o/</p> -<p>16:28 <code>&lt;smoser</code>&gt; just the things that are in teh review queue. i put up one this morning for tmp file leakage</p> -<p>16:28 <code>&lt;smoser</code>&gt; <a href="https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/335034">https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/335034</a></p> -<p>16:29 <code>&lt;smoser</code>&gt; i think the yeazelm mp probably is just missing somethign simple bug haven't spent any time on it.</p> -<p>16:29 <code>&lt;blackboxsw</code>&gt; ahh also we landed the initial /run/cloud-init/instance-data.json which we had talked about with larsks. It captures all metadata and userdata and some standardized properties which could help people script instance data.</p> -<p>16:29 <code>&lt;smoser</code>&gt; yeah, that is neat.</p> -<p>16:30 <code>&lt;blackboxsw</code>&gt; Yeah, we have yet to write up docs on using it (and we have an inprogress branch to allow using jinja templates in #cloud-config modules). But I don't expect this to land by 17.2</p> -<p>16:31 <code>&lt;ajorg</code>&gt; did we? that's great!</p> -<p>16:32 <code>&lt;blackboxsw</code>&gt; yeah only basic standardized properties currently. + 'local-hostname': self.get_hostname(),</p> -<p>16:32 <code>&lt;blackboxsw</code>&gt; 592 + 'instance-id': self.get_instance_id(),</p> -<p>16:32 <code>&lt;blackboxsw</code>&gt; 593 + 'cloud-name': self.cloud_name,</p> -<p>16:32 <code>&lt;blackboxsw</code>&gt; 594 + 'region': self.region,</p> -<p>16:32 <code>&lt;blackboxsw</code>&gt; 595 + 'availability-zone': self.availability_zone}}</p> -<p>16:32 <code>&lt;robjo</code>&gt; is that basically a re-implementation of python-ec2metadata? <a href="https://github.com/SUSE/Enceladus/tree/master/ec2utils/ec2metadata">https://github.com/SUSE/Enceladus/tree/master/ec2utils/ec2metadata</a></p> -<p>16:32 <code>&lt;blackboxsw</code>&gt; but it's a first pass. We expect to add more</p> -<p>16:33 <code>&lt;blackboxsw</code>&gt; robjo: kindof, though generalized for all datasources</p> -<p>16:34 <code>&lt;rharper</code>&gt; robjo: long term, it's expected to be more than just ec2; rather a common baseline of instance metadata independent the actual cloud, but , IIRC, having a cloud-specific area (or at least access to the raw data)</p> -<p>16:34 <code>&lt;blackboxsw</code>&gt; it leaves a json-foramatted file containing any vendor data and user-data plus generalized/standardized fields extracted from that content which can be expected on all clouds</p> -<p>16:35 <code>&lt;robjo</code>&gt; problem with "all" clouds is that Azure is very different</p> -<p>16:35 <code>&lt;blackboxsw</code>&gt; since each datasource has that data already, it's essentially just formating it in a consumable file that others could levereage</p> -<p>16:35 <code>&lt;robjo</code>&gt; although one can argue that a "name" is an id it still looks weird when 'instance-id' and is a name</p> -<p>16:36 <code>&lt;blackboxsw</code>&gt; agreed robjo, some datasources may not provide different/less content.</p> -<p>16:36 <code>&lt;smoser</code>&gt; ajorg: <a href="http://paste.ubuntu.com/26164503/">http://paste.ubuntu.com/26164503/</a></p> -<p>16:36 <code>&lt;ajorg</code>&gt; Is that one of the Azure differences? name vs. instance-id?</p> -<p>16:36 <code>&lt;smoser</code>&gt; thats a demo of instance-data.json</p> -<p>16:36 <code>&lt;robjo</code>&gt; yes, azure has names no numbers</p> -<p>16:37 <code>&lt;robjo</code>&gt; it's more about "user expectations" as a "name" is an "identifier"</p> -<p>16:37 <code>&lt;blackboxsw</code>&gt; I'll check that azure run now. I think I linked it to the branch originally</p> -<p>16:37 <code>&lt;blackboxsw</code>&gt; ok I think it's probably a good to transition to open office hours now for the next 30 mins</p> -<p>16:38 <code>&lt;smoser</code>&gt; what is 'name' versus 'instance-id' comment ?</p> -<p>16:38 <code>&lt;smoser</code>&gt; ajorg: ?</p> -<p>16:38 <code>&lt;blackboxsw</code>&gt; #topic Office Hours (for next 30 mins)</p> -<p>16:38 <code>&lt;blackboxsw</code>&gt; feel free to continue the discussion now</p> -<p>16:38 <code>&lt;robjo</code>&gt; I'd just caution of making the assumption that we can stick the information from that data sources straight into another format and then call it "generic instance information"</p> -<p>16:38 <code>&lt;ajorg</code>&gt; smoser: re robjo's comment about "Azure is very different"</p> -<p>16:39 <code>&lt;smoser</code>&gt; oh. yes. ok.</p> -<p>16:39 <code>&lt;blackboxsw</code>&gt; azure instance-data</p> -<p>16:39 <code>&lt;blackboxsw</code>&gt; #link <a href="http://pastebin.ubuntu.com/26075842/">http://pastebin.ubuntu.com/26075842/</a></p> -<p>16:39 <code>&lt;dpb1</code>&gt; smoser: standup</p> -<p>16:39 <code>&lt;smoser</code>&gt; yeah, they do have a 'id'</p> -<p>16:40 <code>&lt;blackboxsw</code>&gt; #link <a href="http://paste.ubuntu.com/26164503/">http://paste.ubuntu.com/26164503/</a></p> -<p>16:40 <code>&lt;ajorg</code>&gt; from DMI?</p> -<p>16:40 <code>&lt;robjo</code>&gt; Which is useless in any any command</p> -<p>16:40 <code>&lt;smoser</code>&gt; from the cd i think.</p> -<p>16:41 <code>&lt;ajorg</code>&gt; robjo: ah, so the ID is unique (is it?) but can't be used to call any Azure APIs?</p> -<p>16:41 <code>&lt;robjo</code>&gt; in EC2 the instance-id is useful to me if I want to run "aws" commands, but the instance ID shown in the pastebin is useless for any "az" command</p> -<p>16:41 <code>&lt;robjo</code>&gt; ajorg: correct</p> -<p>16:41 <code>&lt;robjo</code>&gt; in the "az" tools everything is a name</p> -<p>16:42 <code>&lt;robjo</code>&gt; and thus to make the data cloud-init produces useful the -id should be the name of the VM</p> -<p>16:42 <code>&lt;robjo</code>&gt; then I can parse that information and use it if I need to deal with the API</p> -<p>16:43 <code>&lt;smoser</code>&gt; hm.</p> -<p>16:43 <code>&lt;robjo</code>&gt; but providing that ID as its is basically just sticking information into the json to "fill a field" which is somewhat counter to the point I'd say</p> -<p>16:43 <code>&lt;ajorg</code>&gt; robjo: there's a uniqueness constraint on the name too? but per-account or at-a-time or what?</p> -<p>16:43 <code>&lt;smoser</code>&gt; i odnt knwo. although it is insteresting thought.</p> -<p>16:43 <code>&lt;smoser</code>&gt; the issue is 'instance-id' is supposed to be an instance id</p> -<p>16:43 <code>&lt;smoser</code>&gt; not a user provided name that can be provided mutliple times in a row.</p> -<p>16:44 <code>&lt;smoser</code>&gt; i realize name is per-group unique, but if i</p> -<p>16:44 <code>&lt;smoser</code>&gt; a.) launch</p> -<p>16:44 <code>&lt;smoser</code>&gt; a.) launch 'foobar'</p> -<p>16:44 <code>&lt;robjo</code>&gt; There is a uniqueness constraint in that one cannot run a VM with the same "name" in the same resource group</p> -<p>16:44 <code>&lt;ajorg</code>&gt; so the question is if that ID provides global uniqueness, or if it provides a reference to the instance to be used via APIs</p> -<p>16:44 <code>&lt;smoser</code>&gt; b.) create capture</p> -<p>16:44 <code>&lt;smoser</code>&gt; c.) delete foobar</p> -<p>16:44 <code>&lt;smoser</code>&gt; d.) launch foobar</p> -<p>16:44 <code>&lt;smoser</code>&gt; then 'd' wont look new</p> -<p>16:45 <code>&lt;robjo</code>&gt; yes, it will it just takes a long time in Azure until the backend reaches "eventual" consistency and knows "foorbar" has been deleted previously</p> -<p>16:45 <code>&lt;ajorg</code>&gt; It seems clear enough that cloud-init is looking for a unique ID</p> -<p>16:45 <code>&lt;ajorg</code>&gt; But a user might want either, and probably an ID for API use.</p> -<p>16:47 <code>&lt;robjo</code>&gt; Well if we provide a format of the data that is exposed to the user via documentation and expected to be used by the user than at that point, IMHO, user needs have higher priority than what cloud-init is looking for</p> -<p>16:47 <code>&lt;ajorg</code>&gt; To decide which APIs to use, a script has to first look at which cloud it's on, so it has a chance to decide which value to use.</p> -<p>16:47 <code>&lt;robjo</code>&gt; that cloud-init uses the id to make decisions about "pre-once", "per-always" is a different topic</p> -<p>16:49 <code>&lt;robjo</code>&gt; Well that then kind of defeats the "generic instance information" claim, IMHO</p> -<p>16:49 <code>&lt;robjo</code>&gt; you are basically saying 1.) look for the framework and then decide if on that framework the "generic instance information" is useful or not</p> -<p>16:50 <code>&lt;robjo</code>&gt; 2.) If you happen to be on a platform where the "generic instance information" is not useful, go and collect your own</p> -<p>16:50 <code>&lt;robjo</code>&gt; From a user perspective that is not very nice, IMHO</p> -<p>16:51 <code>&lt;ajorg</code>&gt; oh, I was presuming we'd also include the Azure name, not that we'd include only a useless instance-id in that case.</p> -<p>16:51 <code>&lt;ajorg</code>&gt; clouds that don't have a name, wouldn't include a value for it.</p> -<p>16:52 <code>&lt;robjo</code>&gt; the pastebin only has the ID</p> -<p>16:52 <code>&lt;ajorg</code>&gt; right, I'm saying we should add the name</p> -<p>16:53 <code>&lt;robjo</code>&gt; This is why I am pointing out that "generic instance information" is not necessarily so easy to come by</p> -<p>16:54 <code>&lt;blackboxsw</code>&gt; robjo: ultimately, I'd like the generalized content surfaced in instance-data.json to be something that external user's could get value from and script against. This first pass was a stripped down approach to some of that content.</p> -<p>16:54 <code>&lt;smoser</code>&gt; we could add 'name' and have it be none yes.</p> -<p>16:55 <code>&lt;smoser</code>&gt; the not-yet-written doc will state that consumers should not be confused by new field names.</p> -<p>16:55 <code>&lt;blackboxsw</code>&gt; There are some fixes that need to be proposed to all datasources to better standardize on things like public vs private addresses, external hostnames etc. Those I expect will come in subsequent passes.</p> -<p>16:55 <code>&lt;robjo</code>&gt; it might be worth considering the concept of "equivalent instance information" where the entries in the json files get names/keys that are generic across all cloud frameworks and provide the euivalent information/usefulness to the user</p> -<p>16:55 <code>&lt;smoser</code>&gt; but inside the 'v1', then content of a key will not change.</p> -<p>16:55 <code>&lt;ajorg</code>&gt; robjo: that's a fair point, imho</p> -<p>16:55 <code>&lt;smoser</code>&gt; but 'instance-id' is in fact 'instance-id'. not 'name'.</p> -<p>16:55 <code>&lt;blackboxsw</code>&gt; robjo: I think that is the intent of those 'v1' standardized fields.</p> -<p>16:56 <code>&lt;smoser</code>&gt; note that lxd shares the same generic problem in this regard as azure. it uses user-provided name for instance-id. but does not provide an actual instance id of any sort.</p> -<p>16:56 <code>&lt;blackboxsw</code>&gt; right per name/instance-id discussion, they feel separate, and I think there is value in adding a separate 'name' as smoser mentioned</p> -<p>16:58 <code>&lt;robjo</code>&gt; Lets look at it from an API perspective, if I were to use the .json file wouldn't it be nice if I could just say json.load().get{'instance_api_id')</p> -<p>16:58 <code>&lt;robjo</code>&gt; for EC2 that returns the instance-id, for Azure it gives me the name</p> -<p>16:59 <code>&lt;robjo</code>&gt; part of the idea of cloud-init is to keep the ugly details of the cloud framework away from the user</p> -<p>16:59 <code>&lt;ajorg</code>&gt; if we were talking about the value of "region" we'd certainly want to yield the value that's useful for API calls.</p> -<p>17:00 <code>&lt;robjo</code>&gt; so why would the .json data then retrieve from that idea and make the user know if I am in EC2 I need to use instance-id and if I am in Azure I need to use instance-name?</p> -<p>17:01 <code>&lt;robjo</code>&gt; ajorg: agreed</p> -<p>17:01 <code>&lt;smoser</code>&gt; it seems somewhat non-sense that azure gives an instance a unique id, but cannot take that in as an identifier to the instance.</p> -<p>17:02 <code>&lt;robjo</code>&gt; AWS, GCE, and Azure all have the concept of "region" , not certain how IBM is handling that part in their setup but that may not be of interest to us at this point</p> -<p>17:02 <code>&lt;smoser</code>&gt; your point is good though. but instance-id i really think needs to be a unique identifier (as much as possible) for this <em>instance</em></p> -<p>17:02 <code>&lt;ajorg</code>&gt; It sounded like smoser's 'v1' comment was meant to imply we could have a 'v2' that yields data differently than 'v1'.</p> -<p>17:02 <code>&lt;smoser</code>&gt; softlayer has "datacenters"</p> -<p>17:03 <code>&lt;robjo</code>&gt; smoser: I agree, but that's the way it is</p> -<p>17:03 <code>&lt;smoser</code>&gt; at some point, ajorg we will of course realize that we're all idiots</p> -<p>17:03 <code>&lt;smoser</code>&gt; and wonder What were we thinking!</p> -<p>17:03 <code>&lt;smoser</code>&gt; and have a 'v2'</p> -<p>17:04 <code>&lt;blackboxsw</code>&gt; `&lt;-- it takes some of us longer than others to realize that</p> -<p>17:05 <code>&lt;ajorg</code>&gt; smoser: you're not convinced that today is that day?</p> -<p>17:05 <code>&lt;smoser</code>&gt; i try to keep acknowledgement of that fact to be more than a few days later</p> -<p>17:06 <code>&lt;ajorg</code>&gt; good to let it sink in first :-)</p> -<p>17:06 <code>&lt;smoser</code>&gt; (compared to when i notice it, to allow for additional occurences)</p> -<p>17:06 <code>&lt;ajorg</code>&gt; I'm not going to say it has to be changed, but I do think at the very least the azure name should be available.</p> -<p>17:07 <code>&lt;blackboxsw</code>&gt; I think this discussion definitely sheds light on the fact that we should continue to bring these standardized instance-data discussions to this meeting for a quick feedback loop from you guys as it evolves :)</p> -<p>17:07 <code>&lt;ajorg</code>&gt; :)</p> -<p>17:08 <code>&lt;blackboxsw</code>&gt; #action blackboxsw bring up any updates in instance-data.json fields for discussion about common use-cases/patterns</p> -<p>17:08 * meetingology blackboxsw bring up any updates in instance-data.json fields for discussion about common use-cases/patterns</p> -<p>17:08 <code>&lt;ajorg</code>&gt; and it doesn't seem harmful to have the name only if the cloud provides one, just as if the cloud doesn't have a concept of an availability zone we'll skip that too.</p> -<p>17:09 <code>&lt;blackboxsw</code>&gt; +1</p> -<p>17:10 <code>&lt;blackboxsw</code>&gt; well i think this about wraps up our meeting for today</p> -<p>17:10 <code>&lt;blackboxsw</code>&gt; any other topics for today?</p> -<p>17:11 <code>&lt;ajorg</code>&gt; I pinged Matt Yeazel, but he didn't respond yet.</p> -<p>17:11 <code>&lt;smoser</code>&gt; i think 'api-id' would lmake sense as a name.</p> -<p>17:11 <code>&lt;ajorg</code>&gt; so nothing more from my end</p> -<p>17:11 <code>&lt;ajorg</code>&gt; smoser: or 'api-instance-id'</p> -<p>17:12 <code>&lt;smoser</code>&gt; that just seems confusing.</p> -<p>17:12 <code>&lt;smoser</code>&gt; hm..</p> -<p>17:12 <code>&lt;smoser</code>&gt; i see why you want the 'instance' portion there, but the thing i dont like is that implies that this is 'per instance'</p> -<p>17:12 <code>&lt;ajorg</code>&gt; well, it's an API instance identifier.</p> -<p>17:13 <code>&lt;smoser</code>&gt; which in fact it is not.</p> -<p>17:13 <code>&lt;smoser</code>&gt; hm.</p> -<p>17:13 <code>&lt;ajorg</code>&gt; Ah, okay, that's true, but if the cloud doesn't have a unique way to identify the instance to the API...</p> -<p>17:13 <code>&lt;smoser</code>&gt; yeah</p> -<p>17:14 <code>&lt;ajorg</code>&gt; someone should check that assumption... how do you refer to terminated instances? or how are they identified in logs?</p> -<p>17:16 <code>&lt;ajorg</code>&gt; smoser: I just worry that someone's going to say "but in my API an API ID is this other thing"</p> -<p>17:17 <code>&lt;blackboxsw</code>&gt; yeah before surfacing something like that we'd need to vet it</p> -<p>17:17 <code>&lt;ajorg</code>&gt; In general I think there are enough differences between clouds that it's probably a losing battle to try to come up with something that's one-size-fits-all.</p> -<p>17:17 <code>&lt;ajorg</code>&gt; The goal was to make the information available more readily than by calling out to metadata services, right?</p> -<p>17:18 <code>&lt;ajorg</code>&gt; It's much harder to implement meta-data pulling for every cloud than to implement some logic that pulls the right value out of a JSON object, so it's still a big improvement even if it can't provide a unified view.</p> -<p>17:21 <code>&lt;ajorg</code>&gt; anywho, I should go do other things.</p> -<p>17:21 <code>&lt;blackboxsw</code>&gt; ajorg: yes that is the primary goal: more easily access cloud-provided metadata</p> -<p>17:21 <code>&lt;blackboxsw</code>&gt; if there is low-hanging fruit we can standardize I'm +1 on the concept</p> -<p>17:22 <code>&lt;blackboxsw</code>&gt; that's where the standard 'v1' key came from</p> -<p>17:22 <code>&lt;blackboxsw</code>&gt; but yeah I also don't think cloud-init needs to boil the ocean and standardize all fields</p> -<p>17:22 <code>&lt;blackboxsw</code>&gt; we'll capture what low-hanging fruit we can</p> -<p>17:22 <code>&lt;blackboxsw</code>&gt; and it'll take time</p> -<p>17:22 <code>&lt;blackboxsw</code>&gt; ok. Thanks for the great discusssions/suggestions ajorg and robjo. keep 'em coming</p> -<p>17:22 <code>&lt;blackboxsw</code>&gt; think I'll end meeting now</p> -<p>17:22 <code>&lt;blackboxsw</code>&gt; until next time...</p> -<p>17:22 <code>&lt;blackboxsw</code>&gt; #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2017-11-13T16:03:00+00:002017-11-13T16:03:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2017-11-13:/status-2017-11-13.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Office Hours (next 30 minutes), 13 Nov at 16:03 &mdash; 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></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Office Hours (next 30 minutes), 13 Nov at 16:03 &mdash; 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>&lt;blackboxsw</code>&gt; #startmeeting Cloud-init bi-weekly status</p> -<p>16:03 <code>&lt;meetingology</code>&gt; 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>&lt;meetingology</code>&gt; </p> -<p>16:03 <code>&lt;meetingology</code>&gt; Available commands: action commands idea info link nick</p> -<p>16:03 <code>&lt;powersj</code>&gt; o/</p> -<p>16:03 <code>&lt;blackboxsw</code>&gt; time change got to us</p> -<p>16:04 <code>&lt;blackboxsw</code>&gt; #topic Recent Changes</p> -<p>16:05 <code>&lt;blackboxsw</code>&gt; 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>&lt;smoser</code>&gt; <a href="http://paste.ubuntu.com/25954862/">http://paste.ubuntu.com/25954862/</a></p> -<p>16:06 <code>&lt;smoser</code>&gt; $ git log a90a8b1cb3104ee3250ac79d6e25a9ff4f527baa.. | log2dch | sed 's,^ ,,' | pastebinit</p> -<p>16:06 <code>&lt;blackboxsw</code>&gt; 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>&lt;blackboxsw</code>&gt; Published cloud-init packages to Bionic Beaver release</p> -<p>16:06 <code>&lt;blackboxsw</code>&gt; Update Gentoo Linux support to "rc-service" scripts as "service" is deprecated, thanks to ckonstanski!</p> -<p>16:06 <code>&lt;blackboxsw</code>&gt; 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>&lt;ubot5</code>&gt; 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>&lt;blackboxsw</code>&gt; #link <a href="http://paste.ubuntu.com/25954862/">http://paste.ubuntu.com/25954862/</a></p> -<p>16:07 <code>&lt;blackboxsw</code>&gt; #info SRU queued for release today</p> -<p>16:07 <code>&lt;blackboxsw</code>&gt; Here's the cloud-init content we published for the last two weeks:</p> -<p>16:07 <code>&lt;blackboxsw</code>&gt; #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>&lt;blackboxsw</code>&gt; #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>&lt;blackboxsw</code>&gt; 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>&lt;blackboxsw</code>&gt; 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>&lt;blackboxsw</code>&gt; 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>&lt;blackboxsw</code>&gt; #topic In Progress Development</p> -<p>16:10 <code>&lt;blackboxsw</code>&gt; smoser: rharper anything here?</p> -<p>16:10 <code>&lt;smoser</code>&gt; #link <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a></p> -<p>16:11 <code>&lt;smoser</code>&gt; robjo has done a couple fixes for SuSE and i've pulled a few of them.</p> -<p>16:11 <code>&lt;smoser</code>&gt; he has one up i saw yestderday for ntpSuSE</p> -<p>16:11 <code>&lt;smoser</code>&gt; others ther.e we've been delinquent due to some distractions recently.</p> -<p>16:11 <code>&lt;rharper</code>&gt; blackboxsw: nothing new for me at the moment</p> -<p>16:12 <code>&lt;smoser</code>&gt; and chad had one up for clean and status</p> -<p>16:12 <code>&lt;blackboxsw</code>&gt; 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>&lt;smoser</code>&gt; which is nice.</p> -<p>16:13 <code>&lt;robjo</code>&gt; 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>&lt;blackboxsw</code>&gt; #topic Office Hours (next 30 minutes)</p> -<p>16:14 <code>&lt;robjo</code>&gt; 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>&lt;blackboxsw</code>&gt; so we'll hang out with eyes on this channel for any burning questions/bugs/questions</p> -<p>16:14 <code>&lt;smoser</code>&gt; robjo: well, the meeting is listed in UTC time</p> -<p>16:14 <code>&lt;smoser</code>&gt; that pays no attention to US legislation to change clocks at random points in the year :)</p> -<p>16:15 <code>&lt;robjo</code>&gt; oK, my fault when I added it to my calendar, eay enough to fix ;)</p> -<p>16:15 <code>&lt;smoser</code>&gt; but the humans here were also affected :)</p> -<p>16:15 <code>&lt;blackboxsw</code>&gt; heh, anyone opposed to shifting this meeting time +30 from now during the next few months?</p> -<p>16:15 <code>&lt;blackboxsw</code>&gt; as the meeting now collides w/ another meeting for us</p> -<p>16:15 <code>&lt;blackboxsw</code>&gt; :/</p> -<p>16:16 <code>&lt;blackboxsw</code>&gt; officially 16:30 UTC?</p> -<p>16:17 <code>&lt;robjo</code>&gt; Well, I'd prefer to either follow the "randomness" clock manipulation or not follow it</p> -<p>16:19 <code>&lt;robjo</code>&gt; 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>&lt;blackboxsw</code>&gt; fair point. ok let's keep the new time as is.</p> -<p>16:20 <code>&lt;blackboxsw</code>&gt; we've discussed side-channel, we can shift our meetings out of the way of this</p> -<p>16:20 <code>&lt;blackboxsw</code>&gt; so robjo +1</p> -<p>16:20 <code>&lt;blackboxsw</code>&gt; 16:00 UTC</p> -<p>16:24 <code>&lt;blackboxsw</code>&gt; also related to CI side, powersj and rharper spent quite a bit of time w/ our continuous integration infrastructure fixing/addressing memory &amp; storage pressure issues to make sure we avoid intermittent false test failures due to timeouts or system resource contention</p> -<p>16:24 <code>&lt;blackboxsw</code>&gt; #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>&lt;via</code>&gt; 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>&lt;robjo</code>&gt; 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>&lt;via</code>&gt; like configuring the chef node name to have my instance id in it</p> -<p>16:32 <code>&lt;blackboxsw</code>&gt; #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>&lt;ubot5</code>&gt; Launchpad bug 1731619 in cloud-init "Support chrony as a client for ntp" [Undecided,New]</p> -<p>16:33 <code>&lt;blackboxsw</code>&gt; 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>&lt;blackboxsw</code>&gt; 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>&lt;smoser</code>&gt; 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>&lt;via</code>&gt; well, i'm trying to do it in a yaml cloud-config file</p> -<p>16:35 <code>&lt;smoser</code>&gt; right. as it is right now, via you cann't reference anything from the metadata.</p> -<p>16:35 <code>&lt;via</code>&gt; does that mean i need to use #jinja and if so how does that play with #cloud-config ?</p> -<p>16:35 <code>&lt;via</code>&gt; oh</p> -<p>16:36 <code>&lt;via</code>&gt; bummer</p> -<p>16:36 <code>&lt;via</code>&gt; should i just switch to a shell script?</p> -<p>16:36 <code>&lt;smoser</code>&gt; but we'd hope to implement that.</p> -<p>16:36 <code>&lt;smoser</code>&gt; 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>&lt;via</code>&gt; okay, damn</p> -<p>16:36 <code>&lt;via</code>&gt; thanks</p> -<p>16:36 <code>&lt;blackboxsw</code>&gt; 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>&lt;smoser</code>&gt; 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>&lt;smoser</code>&gt; but we do plan on implementing it.</p> -<p>16:37 <code>&lt;via</code>&gt; no worries, i'm stuck on an ancient version anyway</p> -<p>16:38 <code>&lt;robjo</code>&gt; 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>&lt;robjo</code>&gt; since with a third option the black/white decision being made today will no longer work</p> -<p>16:39 <code>&lt;blackboxsw</code>&gt; +1 robjo yeah. rharper was chatting about this potential approach as well</p> -<p>16:39 <code>&lt;robjo</code>&gt; look there is also grey ;)</p> -<p>16:39 <code>&lt;blackboxsw</code>&gt; heh yeah</p> -<p>16:40 <code>&lt;robjo</code>&gt; Next question.... network config.</p> -<p>16:40 <code>&lt;blackboxsw</code>&gt; yeah might have to 'grow' an override option in cc_ntp module eventually</p> -<p>16:41 <code>&lt;blackboxsw</code>&gt; as those grey use-cases come up (per bugs/requests ;) )</p> -<p>16:41 <code>&lt;robjo</code>&gt; 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>&lt;robjo</code>&gt; 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>&lt;robjo</code>&gt; 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>&lt;robjo</code>&gt; blackboxsw: "apply_network_config is not currently implemented "</p> -<p>16:44 <code>&lt;robjo</code>&gt; "for distribution '%s'. Attempting to use apply_network"</p> -<p>16:45 <code>&lt;blackboxsw</code>&gt; ahh. right-o</p> -<p>16:45 <code>&lt;robjo</code>&gt; 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>&lt;robjo</code>&gt; 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>&lt;blackboxsw</code>&gt; 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>&lt;robjo</code>&gt; OK :)</p> -<p>16:50 <code>&lt;blackboxsw</code>&gt; 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>&lt;blackboxsw</code>&gt; 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>&lt;blackboxsw</code>&gt; we'll keep our eyes open for discussions/suggestions from folks</p> -<p>16:54 <code>&lt;robjo</code>&gt; 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>&lt;blackboxsw</code>&gt; robjo: I'm curious how different that datasource would be from nocloud datasource</p> -<p>16:56 <code>&lt;blackboxsw</code>&gt; <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>&lt;blackboxsw</code>&gt; #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>&lt;blackboxsw</code>&gt; which allows for providing local data instead of dealing with metadata</p> -<p>16:56 <code>&lt;blackboxsw</code>&gt; well network metadata</p> -<p>16:57 <code>&lt;robjo</code>&gt; 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>&lt;blackboxsw</code>&gt; good deal.... think we are at the top of the hour... so I'll probably end meeting now</p> -<p>17:01 <code>&lt;blackboxsw</code>&gt; thanks via robjo rharper powersj &amp; smoser. next meeting 2 weeks same early time</p> -<p>17:01 <code>&lt;blackboxsw</code>&gt; #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2017-10-30T16:03:00+00:002017-10-30T16:03:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2017-10-30:/status-2017-10-30.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Open Discussion / Office Hours (30 mins), 30 Oct at 16:03 &mdash; 17:00 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-10-30-16.03.log.html">http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-10-30-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="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1721847">https://bugs.launchpad.net …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Open Discussion / Office Hours (30 mins), 30 Oct at 16:03 &mdash; 17:00 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-10-30-16.03.log.html">http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-10-30-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="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1721847">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1721847</a> </li> -</ul> -<h3>In Progess Development</h3> -<p>The discussion about “In Progress Development” started at 16:17.</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="https://launchpad.net/bugs/1728152">https://launchpad.net/bugs/1728152</a> </li> -</ul> -<h3>Open Discussion / Office Hours (30 mins)</h3> -<p>The discussion about “Recent Changes” started at 16:30.</p> -<ul> -<li><em>LINK:</em> <a href="https://launchpad.net/bugs/1728152">https://launchpad.net/bugs/1728152</a></li> -</ul> -<h2>Vote results</h2> -<h2>Done items</h2> -<h2>Meeting summary</h2> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (61)</li> -<li>smoser (10)</li> -<li>ubot5 (8)</li> -<li>powersj (6)</li> -<li>robjo (6)</li> -<li>meetingology (3)</li> -<li>rharper (2)</li> -<li>ckonstanski (1)</li> -</ul> -<h2>Full Log</h2> -<p>16:03 <code>&lt;blackboxsw</code>&gt; #startmeeting cloud-init bi-weekly status</p> -<p>16:03 <code>&lt;meetingology</code>&gt; Meeting started Mon Oct 30 16:03:09 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>&lt;meetingology</code>&gt; </p> -<p>16:03 <code>&lt;meetingology</code>&gt; Available commands: action commands idea info link nick</p> -<p>16:04 <code>&lt;blackboxsw</code>&gt; #topic In Progress Development</p> -<p>16:04 <code>&lt;blackboxsw</code>&gt; So, the last couple weeks have been fairly busy with Ubuntu an SRU processs for Xenial, Zesty and the new Artful release</p> -<p>16:05 <code>&lt;blackboxsw</code>&gt; our SRU process bug captures most of that work</p> -<p>16:05 <code>&lt;blackboxsw</code>&gt; #LINK <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1721847">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1721847</a></p> -<p>16:05 <code>&lt;ubot5</code>&gt; Ubuntu bug 1721847 in cloud-init (Ubuntu Zesty) "sru cloud-init 2017-10-06 (17.1-18-gd4f70470-0ubuntu1)" [Medium,Fix committed]</p> -<p>16:07 <code>&lt;blackboxsw</code>&gt; our teams uncovered at least one bug during verification testing</p> -<p>16:07 <code>&lt;blackboxsw</code>&gt; LINK <a href="https://bugs.launchpad.net/cloud-init/+bug/1725067">https://bugs.launchpad.net/cloud-init/+bug/1725067</a></p> -<p>16:07 <code>&lt;ubot5</code>&gt; Ubuntu bug 1725067 in cloud-init (Ubuntu Artful) "cloud-init resizefs fails when booting with root=PARTUUID=" [Medium,Fix committed]</p> -<p>16:08 <code>&lt;blackboxsw</code>&gt; The former bug we have now resolved. This SRU will not be published until we resolve one other bug for EC2-specfic environments to ensure we retain behavior to always bring up dhcp4 on the primary nic</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; I don't think we have created a bug for the ec2 issue yet (it affects artful only) instances with only private ipv4 addresses allocated will not have dhcp4 config'd for that instance</p> -<p>16:10 <code>&lt;blackboxsw</code>&gt; We'll link a bug for the above today</p> -<p>16:10 <code>&lt;blackboxsw</code>&gt; other work on cloud-init... paste coming</p> -<p>16:11 <code>&lt;blackboxsw</code>&gt; * Fix systemd mount target due to busy device or already mounted (LP: #1718287)</p> -<p>16:11 <code>&lt;blackboxsw</code>&gt; * Fix simpleteable object as output string (LP: #1722566)</p> -<p>16:11 <code>&lt;blackboxsw</code>&gt; * Fix netplan bridge stp boolean (LP: #1721157)</p> -<p>16:11 <code>&lt;blackboxsw</code>&gt; * Fix cc_ntp to allow empty configuration "ntp:". Fix ntp integration test to provide valid empty ntp config (LP: 1724951)</p> -<p>16:11 <code>&lt;blackboxsw</code>&gt; * Fixed cc_lxd to allow for missing bridge definitions in lxd cloud-config</p> -<p>16:11 <code>&lt;blackboxsw</code>&gt; * Dropped fastestmirror plugin for CentOS tests</p> -<p>16:11 <code>&lt;blackboxsw</code>&gt; * Numerous test and CI stability improvements</p> -<p>16:11 <code>&lt;ubot5</code>&gt; Launchpad bug 1718287 in cloud-init "systemd mount targets fail due to device busy or already mounted" [High,Fix committed] <a href="https://launchpad.net/bugs/1718287">https://launchpad.net/bugs/1718287</a></p> -<p>16:11 <code>&lt;ubot5</code>&gt; Launchpad bug 1722566 in cloud-init "ci-info: <code>&lt;cloudinit.simpletable.SimpleTable object at 0x7fa98d222748</code>&gt;" [Medium,Fix committed] <a href="https://launchpad.net/bugs/1722566">https://launchpad.net/bugs/1722566</a></p> -<p>16:11 <code>&lt;ubot5</code>&gt; Launchpad bug 1721157 in cloud-init "netplan render drops bridge_stp setting" [High,Fix committed] <a href="https://launchpad.net/bugs/1721157">https://launchpad.net/bugs/1721157</a></p> -<p>16:11 <code>&lt;ubot5</code>&gt; Launchpad bug 1724951 in cloud-init "Ntp schema definition permits empty ntp cloud-config, but code disallows" [Medium,In progress] <a href="https://launchpad.net/bugs/1724951">https://launchpad.net/bugs/1724951</a></p> -<p>16:13 <code>&lt;blackboxsw</code>&gt; Also we got a couple of gentoo commits from ckonstanski to Use "rc-service" rather than "service". Thanks again</p> -<p>16:13 <code>&lt;rharper</code>&gt; \o/</p> -<p>16:14 <code>&lt;ckonstanski</code>&gt; You're welcome, though those were just tiny toy commits to get me indocrinated into the launchpad process. Getting NTP tests to work in gentoo will be more significant.</p> -<p>16:15 <code>&lt;blackboxsw</code>&gt; ckonstanski: testing always is time-consuming, but totally worth it. We are still trying build our unit test coverage up so we don't get suprises on different platforms/clouds when sparsely tested modules run. Thanks again</p> -<p>16:16 <code>&lt;blackboxsw</code>&gt; oops sorry about the topic for the above ... that should have been the following</p> -<p>16:16 <code>&lt;blackboxsw</code>&gt; #topic Recent Changes</p> -<p>16:16 <code>&lt;blackboxsw</code>&gt; anything else for recent changes that have landed rharper powersj or others?</p> -<p>16:17 <code>&lt;powersj</code>&gt; nope</p> -<p>16:17 <code>&lt;rharper</code>&gt; blackboxsw: not yet</p> -<p>16:17 <code>&lt;blackboxsw</code>&gt; ok then let's move to next topic</p> -<p>16:17 <code>&lt;blackboxsw</code>&gt; #meetingstatus In Progress Development</p> -<p>16:17 <code>&lt;blackboxsw</code>&gt; for real.</p> -<p>16:18 <code>&lt;blackboxsw</code>&gt; ok so we are wrapping up that one Ec2 bug that was raised by Sargun on friday (which affects Artful)</p> -<p>16:18 <code>&lt;blackboxsw</code>&gt; When we have that branch in place, we can kick our final validation of the cloud-init 17.1 updates to Xenial Zesty and Artful.</p> -<p>16:19 <code>&lt;blackboxsw</code>&gt; I know smoser just uploaded cloud-init to the newly opened Bionic release as well</p> -<p>16:19 <code>&lt;blackboxsw</code>&gt; We will be hitting the review queue a bit this week to wrap up content that we want landed once master is open for more dyna</p> -<p>16:20 <code>&lt;blackboxsw</code>&gt; We will be hitting the review queue a bit this week to wrap up content that we want landed once master is open for more significant changesets</p> -<p>16:21 <code>&lt;blackboxsw</code>&gt; we've been a little risk averse during the SRU release process</p> -<p>16:21 <code>&lt;blackboxsw</code>&gt; As always please watch our trello board for progress on anything we are working</p> -<p>16:21 <code>&lt;blackboxsw</code>&gt; 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:22 <code>&lt;powersj</code>&gt; need that #</p> -<p>16:22 <code>&lt;blackboxsw</code>&gt; #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:22 <code>&lt;blackboxsw</code>&gt; ahh thanks oops</p> -<p>16:23 <code>&lt;robjo</code>&gt; speaking of reviews thanks for the help so far blackboxsw , now that my schedule should be a bit less crazy I'd like to get back to <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/addZyppRepos">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/addZyppRepos</a></p> -<p>16:23 <code>&lt;blackboxsw</code>&gt; Our focus as well for the upcoming work in cloud-init is to increase continuous integration coverage and tooling around cloud-init to make sure we can keep delivering stability across releases</p> -<p>16:24 <code>&lt;robjo</code>&gt; since I cannotreproduce the issue the bot has locally and I don't really understand the problem some more help is needed</p> -<p>16:24 <code>&lt;blackboxsw</code>&gt; ahh hiya robjo</p> -<p>16:24 <code>&lt;powersj</code>&gt; that looks merged</p> -<p>16:24 <code>&lt;blackboxsw</code>&gt; robjo: good to hear, we'll watch for updates.</p> -<p>16:25 <code>&lt;powersj</code>&gt; smoser went and fixed the flake8 issues</p> -<p>16:25 <code>&lt;blackboxsw</code>&gt; robjo: do you mean another branch?</p> -<p>16:25 <code>&lt;robjo</code>&gt; blackboxsw: no, that branch, but bot thinks " Needs Fixing ", I just don't get why</p> -<p>16:26 <code>&lt;blackboxsw</code>&gt; yeah per robjo's work cloud-init folks can also configure zypper repos . We landed it Sept 21st. (So it's in cloud-init 17.1)</p> -<p>16:26 <code>&lt;blackboxsw</code>&gt; commit cc1475d07b9d0727012634ee9c7a914d67b051f5</p> -<p>16:26 <code>&lt;blackboxsw</code>&gt; Author: Robert Schweikert <code>&lt;rjschwei@suse.com</code>&gt;</p> -<p>16:26 <code>&lt;blackboxsw</code>&gt; Date: Thu Sep 21 11:58:28 2017 -0400</p> -<p>16:27 <code>&lt;robjo</code>&gt; Oh, so it did get merged, missed that, never mind</p> -<p>16:27 <code>&lt;blackboxsw</code>&gt; as powersj mentioned, I think it was a flake8 CI test issue, so we just fixed the minor issue and landed it as it wasn't a significant content change</p> -<p>16:28 <code>&lt;powersj</code>&gt; cloudinit/config/cc_zypper_add_repo.py:15:1: H306: imports not in alphabetical order (cloudinit.util, cloudinit.config.schema.get_schema_doc)</p> -<p>16:28 <code>&lt;robjo</code>&gt; much appreciated, still a bit concerning that the flake8 issue did not show up locally :(</p> -<p>16:28 <code>&lt;blackboxsw</code>&gt; thx powersj</p> -<p>16:29 <code>&lt;powersj</code>&gt; is correct way <a href="https://paste.ubuntu.com/25852643/">https://paste.ubuntu.com/25852643/</a></p> -<p>16:29 <code>&lt;robjo</code>&gt; SO flake8 has serious issue with the definition of alpha order :(</p> -<p>16:30 <code>&lt;blackboxsw</code>&gt; ;)</p> -<p>16:30 <code>&lt;blackboxsw</code>&gt; ok anything else for "In Progress Development" if not we'll transition to the next topic</p> -<p>16:30 <code>&lt;blackboxsw</code>&gt; #topic Open Discussion / Office Hours (30 mins)</p> -<p>16:31 <code>&lt;blackboxsw</code>&gt; ok we'll hang out in channel if anyone has topics, bugs or features they want to discuss or need some feedback on</p> -<p>16:35 <code>&lt;blackboxsw</code>&gt; and as always thanks for contributions folks. It's really great to work on a project where there is so much interest and investment</p> -<p>16:42 <code>&lt;smoser</code>&gt; blackboxsw: hey. i'm back now. did you open a bug?</p> -<p>16:42 <code>&lt;smoser</code>&gt; i can do so now if you have not.</p> -<p>16:43 <code>&lt;blackboxsw</code>&gt; smoser: I haven't done that yet, was just working out the fix</p> -<p>16:43 <code>&lt;blackboxsw</code>&gt; please do, then we can link it here</p> -<p>16:43 <code>&lt;smoser</code>&gt; ok. i'll do so. and i realized a comment you were making about artful.</p> -<p>16:43 <code>&lt;smoser</code>&gt; that we could go leave artful configuring all nics it saw.</p> -<p>16:43 <code>&lt;blackboxsw</code>&gt; right, because we allow change of behavior in artful right?</p> -<p>16:44 <code>&lt;smoser</code>&gt; as that isn't necessarily "broken" behavior.</p> -<p>16:44 <code>&lt;smoser</code>&gt; yeah. i didnt understand that when you said it.</p> -<p>16:44 <code>&lt;blackboxsw</code>&gt; ahh, I get you. Right, just that the new behavior of configuring all nics is acceptable as new behavior, but not for Xenial. It's just that artful is slightly busted for local-only ipv4</p> -<p>16:45 <code>&lt;smoser</code>&gt; i think it might be easiest both in terms of fixing and in terms of keeping things in our head if we just keep the same behavior everywhere for now.</p> -<p>16:46 <code>&lt;smoser</code>&gt; that is... make artful act like xenial in only configuring one nic</p> -<p>16:48 <code>&lt;smoser</code>&gt; blackboxsw: actually i dont think there is any reason why we shoudlnt just use bug 1728152</p> -<p>16:48 <code>&lt;ubot5</code>&gt; bug 1728152 in cloud-init "IPv4 and IPv6 Dual Stack Does Not work when instance is not assigned public IPv4 address" [High,In progress] <a href="https://launchpad.net/bugs/1728152">https://launchpad.net/bugs/1728152</a></p> -<p>16:48 <code>&lt;smoser</code>&gt; unless you disagree</p> -<p>16:51 <code>&lt;blackboxsw</code>&gt; +1 smoser</p> -<p>16:52 <code>&lt;blackboxsw</code>&gt; lets use that bug</p> -<p>16:59 <code>&lt;blackboxsw</code>&gt; #LINK <a href="https://launchpad.net/bugs/1728152">https://launchpad.net/bugs/1728152</a></p> -<p>16:59 <code>&lt;ubot5</code>&gt; Ubuntu bug 1728152 in cloud-init "EC2 IPv4 and IPv6 Dual Stack Does Not work when instance is not assigned public IPv4 address" [High,In progress]</p> -<p>16:59 <code>&lt;blackboxsw</code>&gt; ok looks like we are good for the status meeting</p> -<p>17:00 <code>&lt;blackboxsw</code>&gt; thanks for joining all. see you in two weeks</p> -<p>17:00 <code>&lt;blackboxsw</code>&gt; #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2017-10-16T16:06:00+00:002017-10-16T16:06:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2017-10-16:/status-2017-10-16.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: Office Hours, 16 Oct at 16:06 &mdash; 17:03 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-10-16-16.06.log.html">http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-10-16-16.06.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:08</p> -<h3>In Progress Development</h3> -<p>The discussion about "In Progress Development …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: Office Hours, 16 Oct at 16:06 &mdash; 17:03 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-10-16-16.06.log.html">http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-10-16-16.06.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent Changes</h3> -<p>The discussion about "Recent Changes" started at 16:08</p> -<h3>In Progress Development</h3> -<p>The discussion about "In Progress Development" started at 16:13</p> -<ul> -<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://trello.com/c/wROS4mKT/458-sru-171">https://trello.com/c/wROS4mKT/458-sru-171</a> </li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1722668">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1722668</a> </li> -<li><strong>LINK</strong>: <a href="https://gist.github.com/smoser/49444542158f2e5f88f1/#file-lxc-pstart-md">https://gist.github.com/smoser/49444542158f2e5f88f1/#file-lxc-pstart-md</a></li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bug/1722992">https://bugs.launchpad.net/cloud-init/+bug/1722992</a> </li> -</ul> -<h3>Office Hours</h3> -<p>The discussion about "Office Houres" started at 16:25</p> -<ul> -<li>open season for discussions, bug requests, review requests for the next 30 mins</li> -</ul> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>blackboxsw (49)</li> -<li>smoser (8)</li> -<li>ubot5 (3)</li> -<li>meetingology (3)</li> -<li>rharper (3)</li> -</ul> -<h2>Full Log</h2> -<p>16:06 <code>&lt;blackboxsw</code>&gt; #startmeeting Cloud-init bi-weekly status</p> -<p>16:06 <code>&lt;meetingology</code>&gt; Meeting started Mon Oct 16 16:06:51 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:06 <code>&lt;meetingology</code>&gt; </p> -<p>16:06 <code>&lt;meetingology</code>&gt; Available commands: action commands idea info link nick</p> -<p>16:08 <code>&lt;blackboxsw</code>&gt; #topic Recent Changes</p> -<p>16:08 <code>&lt;blackboxsw</code>&gt; Ok last couple of weeks for our team were</p> -<p>16:08 <code>&lt;blackboxsw</code>&gt; Ok last couple of weeks for our team were</p> -<p>16:08 <code>&lt;blackboxsw</code>&gt; Ok last couple of weeks for our team were 'impacted' by a couple of work conferences for planning next release of cloud-init/curtin etc.</p> -<p>16:08 <code>&lt;rharper</code>&gt; o/</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; so things felt a bit slow. but folks have still made some good progress.</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; Some changes that have landed in master:</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; Robert Schweikert: suse cloud-config module to add zypper repos and zypp config</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; Robert Schweikert: Allow cloud-init.final stage to spawn infinite processes</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; Andrew Jorgensen: Remove prettytable dependency</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; Fix dhcp parsing in Artful of networkd leases for CloudStack and Azure</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; Updated packaging copyright file (LP: #1718681)</p> -<p>16:09 <code>&lt;ubot5</code>&gt; Launchpad bug 1718681 in cloud-init "Package copyright file omits Apache 2 license" [High,Fix committed] <a href="https://launchpad.net/bugs/1718681">https://launchpad.net/bugs/1718681</a></p> -<p>16:10 <code>&lt;smoser</code>&gt; o/</p> -<p>16:10 <code>&lt;blackboxsw</code>&gt; thanks a lot for the contributions on that front folks. There have been a couple of work items that fell out of our conferences related to Ubuntu artful and systemd/networkd support so we've been workin those</p> -<p>16:11 <code>&lt;blackboxsw</code>&gt; on the testing front we've re-enable tox support for integration tests</p> -<p>16:11 <code>&lt;blackboxsw</code>&gt; and Ubuntu-only has queued a 17.1 SRU release/update into xenial and zesty</p> -<p>16:12 <code>&lt;blackboxsw</code>&gt; smoser: rharper powersj anyone else anything else I'm missing on recent changes?</p> -<p>16:12 <code>&lt;rharper</code>&gt; blackboxsw: that sounds right</p> -<p>16:13 <code>&lt;blackboxsw</code>&gt; ok. next topic</p> -<p>16:13 <code>&lt;blackboxsw</code>&gt; #topic In progress development</p> -<p>16:14 <code>&lt;blackboxsw</code>&gt; As mentioned, we are walking through the Ubuntu xenial/zesty SRU validation process, so I excpect we will have a release update published this week</p> -<p>16:14 * blackboxsw grabs the trello card link</p> -<p>16:14 <code>&lt;blackboxsw</code>&gt; #link <a href="https://trello.com/c/wROS4mKT/458-sru-171">https://trello.com/c/wROS4mKT/458-sru-171</a></p> -<p>16:15 <code>&lt;blackboxsw</code>&gt; This card will move to the Done lane once we've finished publishing</p> -<p>16:16 <code>&lt;blackboxsw</code>&gt; I know powersj has been working the integration test front for KVM as time permits. There will be some upcoming changes there to get us more complex storage/network testing on kvm</p> -<p>16:16 <code>&lt;blackboxsw</code>&gt; I know smoser is also working on a couple of Azure-related fixes for artful as well.</p> -<p>16:16 <code>&lt;blackboxsw</code>&gt; anything else to add there?</p> -<p>16:17 <code>&lt;smoser</code>&gt; <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1722668">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1722668</a></p> -<p>16:17 <code>&lt;rharper</code>&gt; nothing from me</p> -<p>16:17 <code>&lt;ubot5</code>&gt; Ubuntu bug 1722668 in cloud-init (Ubuntu) "Azure: bouncing of network device/publishing of hostname fails on artful" [Critical,Confirmed]</p> -<p>16:17 <code>&lt;blackboxsw</code>&gt; #link <a href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1722668">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1722668</a></p> -<p>16:18 <code>&lt;blackboxsw</code>&gt; thx</p> -<p>16:18 <code>&lt;smoser</code>&gt; that one i'm working on, and then also been trying to get lxc/mount-image-callback</p> -<p>16:19 <code>&lt;smoser</code>&gt; the use we ahve for 'lxc-proposed-snapshot' and also for 'mount-image-callback'</p> -<p>16:19 <code>&lt;blackboxsw</code>&gt; Also in the same vein of improving dev testing of Ubuntu or really any lxc image is that work smoser referenced above.</p> -<p>16:20 <code>&lt;blackboxsw</code>&gt; smoser: is that worth a link at the moment or does it still need polish?</p> -<p>16:20 <code>&lt;smoser</code>&gt; <a href="https://gist.github.com/smoser/49444542158f2e5f88f1/">https://gist.github.com/smoser/49444542158f2e5f88f1/</a>#file-lxc-pstart-md</p> -<p>16:20 <code>&lt;blackboxsw</code>&gt; sweet</p> -<p>16:20 <code>&lt;blackboxsw</code>&gt; #link <a href="https://gist.github.com/smoser/49444542158f2e5f88f1/">https://gist.github.com/smoser/49444542158f2e5f88f1/</a>#file-lxc-pstart-md</p> -<p>16:20 <code>&lt;smoser</code>&gt; right now that is only known to work on lxc 2.18</p> -<p>16:21 <code>&lt;smoser</code>&gt; i think we can make it work with earlier versions, and would like to make it work with xenial (2.02.. maybe)</p> -<p>16:22 <code>&lt;blackboxsw</code>&gt; yeah I just got my artful box up and was going to use that for the SRU verification</p> -<p>16:22 <code>&lt;blackboxsw</code>&gt; also, I think we were going to peek at a solution for the following bug:</p> -<p>16:22 <code>&lt;blackboxsw</code>&gt; #link <a href="https://bugs.launchpad.net/cloud-init/+bug/1722992">https://bugs.launchpad.net/cloud-init/+bug/1722992</a></p> -<p>16:22 <code>&lt;ubot5</code>&gt; Ubuntu bug 1722992 in cloud-init "On the latest centos 7 release, we are unable to resize our instances filesystems" [Medium,Confirmed]</p> -<p>16:23 <code>&lt;blackboxsw</code>&gt; so there might be some minor changes for the OpenStack/MAAS and ConfigDrive datasources</p> -<p>16:24 <code>&lt;blackboxsw</code>&gt; ok anything else in "In progress development"?</p> -<p>16:24 <code>&lt;blackboxsw</code>&gt; I know we have a queue of active reviews we need to get through. I was expecting we'll have bandwidth for that after this SRU push.</p> -<p>16:24 <code>&lt;blackboxsw</code>&gt; #link <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a></p> -<p>16:25 <code>&lt;blackboxsw</code>&gt; #topic Office Hours</p> -<p>16:26 <code>&lt;blackboxsw</code>&gt; #info open season for discussions, bug requests, review requests for the next 30 mins</p> -<p>16:29 <code>&lt;smoser</code>&gt; thanks blackboxsw</p> -<p>16:34 <code>&lt;blackboxsw</code>&gt; no prob. I was peeking around at puppet this weekend.... might have a branch puppet local(masterless deployment) to put up this week</p> -<p>16:34 <code>&lt;blackboxsw</code>&gt; I sort of got distracted by shiny objects while trying to write an SRU test for our existing puppet</p> -<p>16:34 <code>&lt;blackboxsw</code>&gt; config module</p> -<p>17:01 <code>&lt;blackboxsw</code>&gt; ok two more SRU tests left to write for Azure and datasourceOVF. then we can start validation for the upload</p> -<p>17:02 <code>&lt;blackboxsw</code>&gt; office hours coming to a close. but we'll still float in here as always. Happy Monday folks</p> -<p>17:02 <code>&lt;blackboxsw</code>&gt; just ping us directly by IRC nick if you aren't getting a response otherwise.</p> -<p>17:03 <code>&lt;blackboxsw</code>&gt; tanks again.</p> -<p>17:03 <code>&lt;blackboxsw</code>&gt; thanks even</p> -<p>17:03 <code>&lt;blackboxsw</code>&gt; #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2017-10-02T16:05:00+00:002017-10-02T16:05:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2017-10-02:/status-2017-10-02.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init, 02 Oct at 16:05 &mdash; 17:29 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-10-02-16.05.log.html">http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-10-02-16.05.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent Changes / Highlights</h3> -<p>The discussion about "Recent Changes / Highlights" started at 16:06.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://lists.launchpad.net/cloud-init/msg00106.html">https://lists.launchpad.net/cloud-init/msg00106.html …</a></li></ul><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init, 02 Oct at 16:05 &mdash; 17:29 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-10-02-16.05.log.html">http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-10-02-16.05.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<h3>Recent Changes / Highlights</h3> -<p>The discussion about "Recent Changes / Highlights" started at 16:06.</p> -<ul> -<li><strong>LINK</strong>: <a href="https://lists.launchpad.net/cloud-init/msg00106.html">https://lists.launchpad.net/cloud-init/msg00106.html</a> </li> -<li><strong>LINK</strong>: <a href="https://launchpad.net/cloud-init/+milestone/17.2">https://launchpad.net/cloud-init/+milestone/17.2</a> </li> -<li>please target bugs to the next release</li> -</ul> -<h3>In Progress Development / Highlights</h3> -<p>The discussion about "In Progress Development / Highlights" started at 16:09.</p> -<ul> -<li><strong>LINK</strong>: <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a> </li> -<li><strong>LINK</strong>: ? </li> -<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="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/taskLimit">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/taskLimit</a> that's the branch for the task limit</li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init">https://bugs.launchpad.net/cloud-init</a> </li> -<li><strong>LINK</strong>: <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a> </li> -</ul> -<h3>Open Discussion / Office Hours</h3> -<p>The discussion about "Open Discussion / Office Hours" started at 16:17.</p> -<ul> -<li><strong>LINK</strong>: <a href="http://paste.ubuntu.com/25661692/">http://paste.ubuntu.com/25661692/</a> </li> -<li><strong>LINK</strong>: <a href="http://paste.ubuntu.com/25661714/">http://paste.ubuntu.com/25661714/</a> </li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bug/1720841">https://bugs.launchpad.net/cloud-init/+bug/1720841</a> </li> -<li><strong>LINK</strong>: <a href="https://bugs.launchpad.net/cloud-init/+bug/1720841">https://bugs.launchpad.net/cloud-init/+bug/1720841</a> </li> -<li><strong>LINK</strong>: <a href="https://code.launchpad.net/~ajorgens/cloud-init/+git/cloud-init/+merge/330525">https://code.launchpad.net/~ajorgens/cloud-init/+git/cloud-init/+merge/330525</a> ;-)</li> -</ul> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>smoser (88)</li> -<li>ajorg (51)</li> -<li>rharper (28)</li> -<li>blackboxsw (25)</li> -<li>robjo (4)</li> -<li>ubot5 (3)</li> -<li>meetingology (3)</li> -</ul> -<h2>Full Log</h2> -<p>16:05 <code>&lt;smoser</code>&gt; #startmeeting cloud-init</p> -<p>16:05 <code>&lt;meetingology</code>&gt; Meeting started Mon Oct 2 16:05:47 2017 UTC. The chair is smoser. Information about MeetBot at <a href="http://wiki.ubuntu.com/meetingology.">http://wiki.ubuntu.com/meetingology.</a></p> -<p>16:05 <code>&lt;meetingology</code>&gt; </p> -<p>16:05 <code>&lt;meetingology</code>&gt; Available commands: action commands idea info link nick</p> -<p>16:06 <code>&lt;smoser</code>&gt; #topic Recent Changes / Highlights</p> -<p>16:06 <code>&lt;smoser</code>&gt; hm..</p> -<p>16:06 <code>&lt;smoser</code>&gt; 17.1 released <a href="https://lists.launchpad.net/cloud-init/msg00106.html">https://lists.launchpad.net/cloud-init/msg00106.html</a></p> -<p>16:06 <code>&lt;smoser</code>&gt; thats the biggest thing and only thing i have for this topic</p> -<p>16:06 <code>&lt;blackboxsw</code>&gt; #link <a href="https://lists.launchpad.net/cloud-init/msg00106.html">https://lists.launchpad.net/cloud-init/msg00106.html</a></p> -<p>16:06 <code>&lt;smoser</code>&gt; horay for a release, thanks to those who contributed.</p> -<p>16:07 <code>&lt;rharper</code>&gt; \o/</p> -<p>16:07 <code>&lt;smoser</code>&gt; 17.2 is set for 2017-12-14</p> -<p>16:08 <code>&lt;smoser</code>&gt; <a href="https://launchpad.net/cloud-init/+milestone/17.2">https://launchpad.net/cloud-init/+milestone/17.2</a></p> -<p>16:08 <code>&lt;ajorg</code>&gt; yay!</p> -<p>16:08 <code>&lt;smoser</code>&gt; feel free to target bugs to that release.</p> -<p>16:08 <code>&lt;rharper</code>&gt; #link <a href="https://launchpad.net/cloud-init/+milestone/17.2">https://launchpad.net/cloud-init/+milestone/17.2</a></p> -<p>16:08 <code>&lt;rharper</code>&gt; #info please target bugs to the next release</p> -<p>16:09 <code>&lt;smoser</code>&gt; does that do anyting ?</p> -<p>16:09 <code>&lt;rharper</code>&gt; in the meeting summary, it does</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; smoser: the links showed up in meeting minutes last time</p> -<p>16:09 <code>&lt;smoser</code>&gt; k. i always expected the bot to tell me that in a pm</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; meetingology didn't echo though</p> -<p>16:09 <code>&lt;rharper</code>&gt; well, smoser may have to do those</p> -<p>16:09 <code>&lt;smoser</code>&gt; #topic In Progress Development / Highlights</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; same. but something is up that needs attention.</p> -<p>16:10 <code>&lt;blackboxsw</code>&gt; I'll properly handle it when publishing</p> -<p>16:10 <code>&lt;rharper</code>&gt; cool</p> -<p>16:11 <code>&lt;smoser</code>&gt; Merge Proposals</p> -<p>16:11 <code>&lt;smoser</code>&gt; #link <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a></p> -<p>16:11 <code>&lt;smoser</code>&gt; there are some there for sure. i know that robjo has some he's interested in, and i think ajorg's instance-identity deserves a look</p> -<p>16:12 <code>&lt;smoser</code>&gt; as well as simpletable for 17.2</p> -<p>16:12 <code>&lt;ajorg</code>&gt; I'd be grateful for both, yes.</p> -<p>16:12 <code>&lt;smoser</code>&gt; i am looking at the 'networkd' one which is a blocker as currently Ubuntu does not work properly on azure</p> -<p>16:12 <code>&lt;blackboxsw</code>&gt; we should have more bandwidth this week</p> -<p>16:12 <code>&lt;smoser</code>&gt; and all sysstemd-networkd systems will not work properly on CloudStack.</p> -<p>16:12 <code>&lt;smoser</code>&gt; anything else there?</p> -<p>16:13 <code>&lt;robjo</code>&gt; The task limit increase has been tested and solves our problem, thus merging would be great</p> -<p>16:13 <code>&lt;smoser</code>&gt; robjo, yeah. athat does seem unlikely to cause issue</p> -<p>16:13 <code>&lt;smoser</code>&gt; Trello Board</p> -<p>16:13 <code>&lt;smoser</code>&gt; # <a href="https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin">https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin</a></p> -<p>16:13 <code>&lt;rharper</code>&gt; #link ?</p> -<p>16:13 <code>&lt;smoser</code>&gt; #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:14 <code>&lt;robjo</code>&gt; <a href="https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/taskLimit">https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/taskLimit</a> that's the branch for the task limit</p> -<p>16:15 <code>&lt;robjo</code>&gt; Sorry, I can never find the link for the open merge proposals :( problem exists between the keyboard and the chair</p> -<p>16:16 <code>&lt;blackboxsw</code>&gt; will get eyes on that today robjo as your addZypper is about wrapped</p> -<p>16:16 <code>&lt;smoser</code>&gt; Bugs</p> -<p>16:16 <code>&lt;smoser</code>&gt; #link <a href="https://bugs.launchpad.net/cloud-init">https://bugs.launchpad.net/cloud-init</a></p> -<p>16:16 <code>&lt;smoser</code>&gt; just mostly pointers... above.</p> -<p>16:16 <code>&lt;smoser</code>&gt; for Ubuntu in 16.04, there is one SRU in progress that blackboxsw and i need to verify today</p> -<p>16:16 <code>&lt;smoser</code>&gt; and then we will be soon looking at doing an SRU of 17.1-ish</p> -<p>16:17 <code>&lt;robjo</code>&gt; Thanks, still in europe, my day is about done, will pick it up tomorrow</p> -<p>16:17 <code>&lt;smoser</code>&gt; robjo, link is in topic</p> -<p>16:17 <code>&lt;smoser</code>&gt; <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a></p> -<p>16:17 <code>&lt;smoser</code>&gt; ok. so open discussion i guess. no w?</p> -<p>16:17 <code>&lt;smoser</code>&gt; #topic Open Discussion / Office Hours</p> -<p>16:17 <code>&lt;smoser</code>&gt; we'll hang around and pay attention to pings and discussion fro the next 30 minutes or so.</p> -<p>16:18 <code>&lt;smoser</code>&gt; and after that, feel free to ping.</p> -<p>16:19 <code>&lt;ajorg</code>&gt; I'm writing a unit test for a bugfix I'm preparing to submit. It works, but it's slow because readurl retries and waits a second each time</p> -<p>16:20 <code>&lt;ajorg</code>&gt; I'm a bit of a mock / patch newb. Anyone can help me see how to patch that argument?</p> -<p>16:20 <code>&lt;smoser</code>&gt; you can feel free to mock readurl</p> -<p>16:20 <code>&lt;smoser</code>&gt; and set its return_value and look at calls</p> -<p>16:21 <code>&lt;smoser</code>&gt; then you dont have to httppretty.</p> -<p>16:21 <code>&lt;ajorg</code>&gt; The only thing I want to change about it is the sleep though. Is there a straightforward way to just change one arg?</p> -<p>16:21 <code>&lt;blackboxsw</code>&gt; tests/unittests/test_handler/test_handler_chef.py is an example and tests/unittests/test_datasource/test_maas.py</p> -<p>16:21 <code>&lt;blackboxsw</code>&gt; I think</p> -<p>16:21 <code>&lt;ajorg</code>&gt; Hmm, I could do that, yeah. Would be sufficient for this.</p> -<p>16:22 <code>&lt;ajorg</code>&gt; I'd still like to know if there's an easy way to just change one argument to something that gets called somewhere else.</p> -<p>16:22 <code>&lt;smoser</code>&gt; you could also mock the time.sleep from url_helper</p> -<p>16:22 <code>&lt;ajorg</code>&gt; hahaha, yes. that's what I need to do.</p> -<p>16:22 <code>&lt;rharper</code>&gt; ajorg: if you want to mock the sleep you can decorate the test_ method with @mock.patch(time.sleep)</p> -<p>16:22 <code>&lt;smoser</code>&gt; we're suggesting other ways generally because there isn't :) at least that i know of.</p> -<p>16:23 <code>&lt;ajorg</code>&gt; that's cool, patching time.sleep will do nicely</p> -<p>16:24 <code>&lt;ajorg</code>&gt; is there an integration test that looks at what lands on the console?</p> -<p>16:24 <code>&lt;ajorg</code>&gt; (going back to my question from before the meeting)</p> -<p>16:25 <code>&lt;smoser</code>&gt; no. there coudl be on the nocloud-kvm backend</p> -<p>16:25 <code>&lt;smoser</code>&gt; but i think there is no console access currently on lxd</p> -<p>16:25 <code>&lt;smoser</code>&gt; and i think that we do not collect console access on nocloud-kvm</p> -<p>16:25 <code>&lt;smoser</code>&gt; but as you suggest we should for sure</p> -<p>16:25 <code>&lt;ajorg</code>&gt; k</p> -<p>16:26 <code>&lt;ajorg</code>&gt; I wondered if systemd might be swallowing my output, or maybe python (boothook in this case is a python script) is making a strange choice when it sets up logging.</p> -<p>16:27 <code>&lt;rharper</code>&gt; certainly possible; I know there were issues with cloud-init starting before say rsyslog on non-systemd boots</p> -<p>16:28 <code>&lt;rharper</code>&gt; and the python logging has changed w.r.t the default configuration; cloud-init main sort of expects this transition as it starts up in init-local and it has not yet read the cloud-config for logging configuration yet, so it reads that and then does some replay</p> -<p>16:28 <code>&lt;ajorg</code>&gt; interesting</p> -<p>16:29 <code>&lt;smoser</code>&gt; ajorg, you're writing to stdout/err with logging from a boothook ?</p> -<p>16:29 <code>&lt;ajorg</code>&gt; at least I would have thought cloud-init-output.log would contain my logs though, since it's more a redirect of stderr and stdout, right?</p> -<p>16:29 <code>&lt;ajorg</code>&gt; yeah</p> -<p>16:29 <code>&lt;rharper</code>&gt; correct</p> -<p>16:29 <code>&lt;rharper</code>&gt; this is from a bootcmd ?</p> -<p>16:29 <code>&lt;ajorg</code>&gt; no, #cloud-boothook</p> -<p>16:29 * rharper hasn't used boothook</p> -<p>16:29 <code>&lt;smoser</code>&gt; hm..</p> -<p>16:30 <code>&lt;ajorg</code>&gt; boothooks are super useful</p> -<p>16:32 <code>&lt;rharper</code>&gt; smoser: when do boot_hooks run ? local ? net ?</p> -<p>16:33 <code>&lt;rharper</code>&gt; I'm not sure yet where stdout/err for boot hooks occur, but you can dump each from the units via: journalctl -u cloud-init-local.service (or cloud-init.service)</p> -<p>16:33 <code>&lt;blackboxsw</code>&gt; "This is the earliest hook available. Note, that there is no mechanism provided for running only once"</p> -<p>16:34 <code>&lt;blackboxsw</code>&gt; I'm checking the code now (local/pre-local maybe)?</p> -<p>16:34 <code>&lt;rharper</code>&gt; yeah, saw that; it runs in-image scripts programs</p> -<p>16:34 <code>&lt;ajorg</code>&gt; I did that too, and don't see anything.</p> -<p>16:34 <code>&lt;ajorg</code>&gt; (journalctl)</p> -<p>16:34 <code>&lt;rharper</code>&gt; you should see some output</p> -<p>16:34 <code>&lt;rharper</code>&gt; but not seeing your hook in there ?</p> -<p>16:34 <code>&lt;ajorg</code>&gt; I can tell by other means that the hook ran</p> -<p>16:34 <code>&lt;ajorg</code>&gt; just don't see that it printed anything</p> -<p>16:35 <code>&lt;ajorg</code>&gt; my prime suspect if systemd can't do something bad here is that python makes some decision about not actually logging.</p> -<p>16:35 <code>&lt;ajorg</code>&gt; and I need to be more explicit that it should log</p> -<p>16:36 <code>&lt;rharper</code>&gt; so, the boot_hook will sub out each part, I see no capture on the stderr/stdout ; so I would expect those to go to whatever is currently capturing those;</p> -<p>16:37 <code>&lt;rharper</code>&gt; s/sub/subprocess</p> -<p>16:38 <code>&lt;ajorg</code>&gt; yup, that's what I expect too, and what I recall seeing on Amazon Linux</p> -<p>16:38 <code>&lt;rharper</code>&gt; since it's using cloud-init's util.subp, there <em>should</em> be a debug level message saying 'Running command %s with allowed return codes %s' which maches a path to the boothook</p> -<p>16:38 <code>&lt;rharper</code>&gt; I would expect to see that in the cloud-init.log</p> -<p>16:39 <code>&lt;smoser</code>&gt; <a href="http://paste.ubuntu.com/25661692/">http://paste.ubuntu.com/25661692/</a></p> -<p>16:39 <code>&lt;ajorg</code>&gt; yup, I do see that</p> -<p>16:39 <code>&lt;rharper</code>&gt; the output of script, I <em>think</em> should go to cloud-init-output.log</p> -<p>16:39 <code>&lt;smoser</code>&gt; i'm testing ^ on serverstack now.</p> -<p>16:39 <code>&lt;smoser</code>&gt; i verified the commands run on lxd but not look at console there.</p> -<p>16:39 <code>&lt;ajorg</code>&gt; thanks</p> -<p>16:40 <code>&lt;smoser</code>&gt; actually.. yeah, BOOTHOOK does run, but doesnt seem to have stdout tied to same place as bootcmd</p> -<p>16:41 <code>&lt;ajorg</code>&gt; oh?</p> -<p>16:41 <code>&lt;ajorg</code>&gt; I'm slightly surprised it's not just me</p> -<p>16:42 <code>&lt;smoser</code>&gt; <a href="http://paste.ubuntu.com/25661714/">http://paste.ubuntu.com/25661714/</a></p> -<p>16:42 <code>&lt;rharper</code>&gt; it really should be in the journal/console if stdout is not redirected to a file, cloud-init-local service</p> -<p>16:43 <code>&lt;smoser</code>&gt; that reproduces in lxc</p> -<p>16:44 <code>&lt;rharper</code>&gt; smoser: in your instance on serverstack, do you see your BOOTHOOK in journalctl -b -u cloud-init-local.service ?</p> -<p>16:44 <code>&lt;smoser</code>&gt; ajorg, please go ahead and open a bug.</p> -<p>16:44 <code>&lt;ajorg</code>&gt; cool (not cool :-P)</p> -<p>16:44 <code>&lt;ajorg</code>&gt; will do</p> -<p>16:44 <code>&lt;smoser</code>&gt; # journalctl -b -u cloud-init.service | grep BOOT</p> -<p>16:44 <code>&lt;smoser</code>&gt; Oct 02 16:37:41 a5 cloud-init[121]: BOOTCMD: Mon, 02 Oct 2017 16:37:41 +0000: a5</p> -<p>16:44 <code>&lt;smoser</code>&gt; ^ that is from lxd</p> -<p>16:45 <code>&lt;rharper</code>&gt; and what about the welcome message from cloud-init ?</p> -<p>16:45 <code>&lt;smoser</code>&gt; i think not.</p> -<p>16:45 <code>&lt;rharper</code>&gt; bootcmd does: util.subp(cmd, env=env, capture=False) ; where boot_hook does: util.subp([filepath], env=env)</p> -<p>16:46 <code>&lt;smoser</code>&gt; yeah, so boot_hook definitely swallowed. and should not be.</p> -<p>16:47 <code>&lt;rharper</code>&gt; yeah</p> -<p>16:49 <code>&lt;ajorg</code>&gt; <a href="https://bugs.launchpad.net/cloud-init/+bug/1720841">https://bugs.launchpad.net/cloud-init/+bug/1720841</a></p> -<p>16:49 <code>&lt;ubot5</code>&gt; Ubuntu bug 1720841 in cloud-init "Output from boothook is not logged" [Undecided,New]</p> -<p>16:50 <code>&lt;ajorg</code>&gt; Meanwhile I need to setup more explicit logging from that boothook anyway, so I'm okay.</p> -<p>16:51 <code>&lt;blackboxsw</code>&gt; #link <a href="https://bugs.launchpad.net/cloud-init/+bug/1720841">https://bugs.launchpad.net/cloud-init/+bug/1720841</a></p> -<p>16:51 <code>&lt;ubot5</code>&gt; Ubuntu bug 1720841 in cloud-init "Output from boothook is not logged" [Medium,Confirmed]</p> -<p>16:55 <code>&lt;ajorg</code>&gt; Here's another one, which I've confirmed with a unit test and proposed a patch: <a href="https://bugs.launchpad.net/cloud-init/+bug/1720844">https://bugs.launchpad.net/cloud-init/+bug/1720844</a></p> -<p>16:55 <code>&lt;ubot5</code>&gt; Ubuntu bug 1720844 in cloud-init "UrlError from #include aborts stage" [Undecided,New]</p> -<p>16:55 <code>&lt;ajorg</code>&gt; (what is this #link thing you're doing there?)</p> -<p>16:55 <code>&lt;smoser</code>&gt; well, the bot is supposed to care and do somethign with it.</p> -<p>16:56 <code>&lt;smoser</code>&gt; but /me thinks it doesnt work right :)</p> -<p>16:56 <code>&lt;blackboxsw</code>&gt; ajorg: since meetingology is still active, the theory is it is keeping track of links during this meeting</p> -<p>16:56 <code>&lt;smoser</code>&gt; (during the meeting)</p> -<p>16:56 <code>&lt;ajorg</code>&gt; ah, okay</p> -<p>16:57 <code>&lt;ajorg</code>&gt; I think simpletable is completely ready to merge, btw. Any objections? <a href="https://code.launchpad.net/~ajorgens/cloud-init/+git/cloud-init/+merge/330525">https://code.launchpad.net/~ajorgens/cloud-init/+git/cloud-init/+merge/330525</a></p> -<p>16:57 <code>&lt;blackboxsw</code>&gt; The theory is it writes the meeting notes out for us so we can publish to <a href="https://cloud-init.github.io">https://cloud-init.github.io</a></p> -<p>16:57 <code>&lt;ajorg</code>&gt; #link <a href="https://code.launchpad.net/~ajorgens/cloud-init/+git/cloud-init/+merge/330525">https://code.launchpad.net/~ajorgens/cloud-init/+git/cloud-init/+merge/330525</a> ;-)</p> -<p>16:57 <code>&lt;blackboxsw</code>&gt; geg</p> -<p>16:57 <code>&lt;blackboxsw</code>&gt; heh</p> -<p>16:58 <code>&lt;blackboxsw</code>&gt; ajorg: I think we were good on that changeset, and we only wanted to wait post 17.1 cut to avoid potential regression</p> -<p>16:59 <code>&lt;ajorg</code>&gt; great</p> -<p>16:59 <code>&lt;blackboxsw</code>&gt; I'm +1 on that will give it a spin today and then I think we can land it</p> -<p>17:01 <code>&lt;smoser</code>&gt; blackboxsw, ajorg my thoughts on the simpletable...</p> -<p>17:01 <code>&lt;ajorg</code>&gt; here it comes...</p> -<p>17:01 <code>&lt;ajorg</code>&gt; :-P</p> -<p>17:01 <code>&lt;blackboxsw</code>&gt; :)</p> -<p>17:02 <code>&lt;smoser</code>&gt; i would like to have a machine friendly output available</p> -<p>17:02 <code>&lt;smoser</code>&gt; human friendly is good, but machine friendly solves the actual goal of writing the stuff.</p> -<p>17:02 <code>&lt;ajorg</code>&gt; So I modified it to display <em>exactly</em> as prettytable did</p> -<p>17:02 <code>&lt;smoser</code>&gt; oh really.</p> -<p>17:02 <code>&lt;smoser</code>&gt; wow</p> -<p>17:02 <code>&lt;ajorg</code>&gt; which is admittedly not machine friendly</p> -<p>17:02 <code>&lt;ajorg</code>&gt; not especially</p> -<p>17:02 <code>&lt;smoser</code>&gt; then i guess i can't object at all.</p> -<p>17:02 <code>&lt;ajorg</code>&gt; but it's at least as good as prettytable</p> -<p>17:03 <code>&lt;smoser</code>&gt; in that its backwards compat</p> -<p>17:03 <code>&lt;smoser</code>&gt; right.</p> -<p>17:03 <code>&lt;ajorg</code>&gt; ^ this was my goal, to get you to not object</p> -<p>17:03 <code>&lt;smoser</code>&gt; i still think we should probaly additionally write some machine friendly json</p> -<p>17:03 <code>&lt;ajorg</code>&gt; agreed, that would be better</p> -<p>17:03 <code>&lt;smoser</code>&gt; i tihnk having something human friendly is good though</p> -<p>17:03 <code>&lt;smoser</code>&gt; as i know <em>I</em> look at that output</p> -<p>17:04 <code>&lt;ajorg</code>&gt; it meets my goal of not depending on prettytable</p> -<p>17:04 <code>&lt;smoser</code>&gt; and parsing json would be less nice</p> -<p>17:04 <code>&lt;smoser</code>&gt; yeah</p> -<p>17:05 <code>&lt;smoser</code>&gt; so based on your assertion that it outputs the same as pretty table, i have no objections. only future hopes.</p> -<p>17:05 <code>&lt;smoser</code>&gt; and i do agree dropping pretty table is nice</p> -<p>17:05 <code>&lt;ajorg</code>&gt; winning</p> -<p>17:06 <code>&lt;blackboxsw</code>&gt; smoser: yeah I was wondering how we generally expect people/machines to parse cloud-init-output.log. Right now it's kindof hard to do machine parsing of cloud-init-output.log.</p> -<p>17:07 <code>&lt;smoser</code>&gt; blackboxsw, yeah. cloud-init-output.log is not intended to be machine friendly.</p> -<p>17:07 <code>&lt;blackboxsw</code>&gt; do we know already of non-human consumers of the formatting in cloud-init.output.log?</p> -<p>17:07 <code>&lt;smoser</code>&gt; but the console actually has value in having machien friendly things on it.</p> -<p>17:08 <code>&lt;smoser</code>&gt; my feeling is if you have access to /var/log/cloud-init.log, then you could very easily have written whatever you wanted to another file that was purely machine friendly.</p> -<p>17:08 <code>&lt;blackboxsw</code>&gt; was wondering where we would intend to dump machine-friendly json</p> -<p>17:08 <code>&lt;blackboxsw</code>&gt; yeah</p> -<p>17:08 <code>&lt;smoser</code>&gt; but the console (/dev/ttyS0) boot log is different</p> -<p>17:08 <code>&lt;smoser</code>&gt; in that it can give you a couple things you'd not find easy access to</p> -<p>17:09 <code>&lt;smoser</code>&gt; a.) ssh public keys for the system (providing out of band communication of this data)</p> -<p>17:09 <code>&lt;smoser</code>&gt; b.) network configuration info: providn useful bits of data on how you might get to this system</p> -<p>17:10 <code>&lt;smoser</code>&gt; systemd makes it "fun" to get that data to the console in a safe way</p> -<p>17:12 <code>&lt;ajorg</code>&gt; ugh yes. systemd like to stomp all over your consoles.</p> -<p>17:19 <code>&lt;blackboxsw</code>&gt; ok so did we want to iterate on simpletable to dump json, or just look for cloud-init to write supplementary json files under /run/cloud-init</p> -<p>17:20 <code>&lt;blackboxsw</code>&gt; .. after we land ajorg's branch</p> -<p>17:21 <code>&lt;ajorg</code>&gt; I think it's a good idea to dump json fragments to console for some things, but I suspect smoser will still not want to break anyone who might be using the tables, so probably best to land my branch as-is</p> -<p>17:23 <code>&lt;smoser</code>&gt; yeah, i agree with ajorg. for now, we can just take a replacement that drops prettytable</p> -<p>17:23 <code>&lt;smoser</code>&gt; there are improvments to be done there, but this is a simple win</p> -<p>17:29 <code>&lt;smoser</code>&gt; we'll go ahead and end meeting here.</p> -<p>17:29 <code>&lt;smoser</code>&gt; i'll still be around. thanks all!</p> -<p>17:29 <code>&lt;smoser</code>&gt; #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2017-09-18T16:04:00+00:002017-09-18T16:04:00+00:00chad.smith@canonical.comtag:cloud-init.github.io,2017-09-18:/status-2017-09-18.html<h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 18 Sep at 16:04 &mdash; 16:27 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-09-18-16.04.log.html">http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-09-18-16.04.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<ul> -<li><strong>LINK</strong>: <a href="https://public.etherpad-mozilla.org/p/cloud-init-meeting">https://public.etherpad-mozilla.org/p/cloud-init-meeting</a> </li> -<li><strong>LINK</strong>: <a href="https://lists.launchpad.net/cloud-init/msg00100.html">https://lists.launchpad.net/cloud-init/msg00100.html</a> </li> -</ul> -<h3>Release Preparation</h3> -<p>The discussion …</p><h2>Meeting information</h2> -<ul> -<li>#cloud-init: cloud-init status meeting, 18 Sep at 16:04 &mdash; 16:27 UTC</li> -<li>Full logs at [[<a href="http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-09-18-16.04.log.html">http://ubottu.com/meetingology/logs/cloud-init/2017/cloud-init.2017-09-18-16.04.log.html</a>]]</li> -</ul> -<h2>Meeting summary</h2> -<ul> -<li><strong>LINK</strong>: <a href="https://public.etherpad-mozilla.org/p/cloud-init-meeting">https://public.etherpad-mozilla.org/p/cloud-init-meeting</a> </li> -<li><strong>LINK</strong>: <a href="https://lists.launchpad.net/cloud-init/msg00100.html">https://lists.launchpad.net/cloud-init/msg00100.html</a> </li> -</ul> -<h3>Release Preparation</h3> -<p>The discussion about "Release Preparation" started at 16:08.</p> -<ul> -<li>'''Release Preparation''' (16:08)</li> -<li> -<ul> -<li><strong>LINK</strong>: <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a> </li> -</ul> -</li> -</ul> -<h3>Open Discussion</h3> -<p>The discussion about "Open Discussion" started at 16:14.</p> -<ul> -<li> -<ul> -<li><strong>LINK</strong>: <a href="https://launchpad.net/bugs/1717598">https://launchpad.net/bugs/1717598</a> </li> -</ul> -</li> -</ul> -<h2>Vote results</h2> -<h2>Done items</h2> -<ul> -<li>(none)</li> -</ul> -<h2>People present (lines said)</h2> -<ul> -<li>smoser (41)</li> -<li>blackboxsw (8)</li> -<li>ubot5 (4)</li> -<li>ajorg (4)</li> -<li>robjo (4)</li> -<li>meetingology (3)</li> -<li>dpb1 (3)</li> -<li>rharper (1)</li> -</ul> -<h2>Full Log</h2> -<p>16:04 <code>&lt;smoser</code>&gt; #startmeeting cloud-init status meeting</p> -<p>16:04 <code>&lt;meetingology</code>&gt; Meeting started Mon Sep 18 16:04:28 2017 UTC. The chair is smoser. Information about MeetBot at <a href="http://wiki.ubuntu.com/meetingology.">http://wiki.ubuntu.com/meetingology.</a></p> -<p>16:04 <code>&lt;meetingology</code>&gt; </p> -<p>16:04 <code>&lt;meetingology</code>&gt; Available commands: action commands idea info link nick</p> -<p>16:05 <code>&lt;blackboxsw</code>&gt; hiya o/</p> -<p>16:05 <code>&lt;rharper</code>&gt; o/</p> -<p>16:05 <code>&lt;smoser</code>&gt; #link <a href="https://public.etherpad-mozilla.org/p/cloud-init-meeting">https://public.etherpad-mozilla.org/p/cloud-init-meeting</a></p> -<p>16:05 <code>&lt;dpb1</code>&gt; hello</p> -<p>16:05 <code>&lt;smoser</code>&gt; so that contains a agenda that we'd been following</p> -<p>16:06 <code>&lt;smoser</code>&gt; #link <a href="https://lists.launchpad.net/cloud-init/msg00100.html">https://lists.launchpad.net/cloud-init/msg00100.html</a></p> -<p>16:07 <code>&lt;smoser</code>&gt; sorry for slow going here.</p> -<p>16:08 <code>&lt;smoser</code>&gt; shoot</p> -<p>16:08 <code>&lt;smoser</code>&gt; #topic Release Preparation</p> -<p>16:08 <code>&lt;smoser</code>&gt; #subtopic Release Preparation</p> -<p>16:08 <code>&lt;smoser</code>&gt; hm..</p> -<p>16:09 <code>&lt;smoser</code>&gt; anyway</p> -<p>16:09 <code>&lt;smoser</code>&gt; <a href="https://lists.launchpad.net/cloud-init/msg00100.html">https://lists.launchpad.net/cloud-init/msg00100.html</a></p> -<p>16:09 <code>&lt;smoser</code>&gt; that is the primariy point of this meeting for today.</p> -<p>16:09 <code>&lt;smoser</code>&gt; The goal is to make a release named 17.1 on Thursday of this week.</p> -<p>16:09 <code>&lt;blackboxsw</code>&gt; strange</p> -<p>16:09 <code>&lt;smoser</code>&gt; We have landed several branches in the last few days, and have 2 more to land at least.</p> -<p>16:10 <code>&lt;smoser</code>&gt; from <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a></p> -<p>16:10 <code>&lt;dpb1</code>&gt; meetingology │ Available commands: action commands idea info link nick</p> -<p>16:10 <code>&lt;dpb1</code>&gt; something to look into. :)</p> -<p>16:10 <code>&lt;blackboxsw</code>&gt; #link <a href="http://bit.ly/ci-reviews">http://bit.ly/ci-reviews</a></p> -<p>16:10 <code>&lt;smoser</code>&gt; the two we consider needs to be integrated are</p> -<p>16:10 <code>&lt;smoser</code>&gt; <a href="https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/330875">https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/330875</a></p> -<p>16:10 <code>&lt;smoser</code>&gt; <a href="https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/330880">https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/330880</a></p> -<p>16:11 <code>&lt;smoser</code>&gt; and Chad's (the first) is the one we're looking at now.</p> -<p>16:11 <code>&lt;smoser</code>&gt; or that is the one that is non-trivial</p> -<p>16:11 <code>&lt;smoser</code>&gt; does anyone here wnat to raise other bugs or MP that they believe should be pulled ?</p> -<p>16:12 <code>&lt;smoser</code>&gt; ...</p> -<p>16:12 <code>&lt;smoser</code>&gt; ajorg, i think its best to hold off on some of yours until after release.</p> -<p>16:13 <code>&lt;smoser</code>&gt; anyone have anything else ?</p> -<p>16:13 <code>&lt;blackboxsw</code>&gt; msaika (vmware) pinged on a branch a couple days ago. but I think there is a little of discussion/re-work that's needed there before we land</p> -<p>16:13 <code>&lt;ajorg</code>&gt; smoser: I assume you mean the instance identity one, in which case I agree.</p> -<p>16:13 <code>&lt;ajorg</code>&gt; (in either case I'd agree)</p> -<p>16:13 <code>&lt;smoser</code>&gt; and simpletable</p> -<p>16:13 <code>&lt;smoser</code>&gt; yeah</p> -<p>16:14 <code>&lt;smoser</code>&gt; ok. so that is where we are. we are still targettin a release on Thursday.</p> -<p>16:14 <code>&lt;smoser</code>&gt; other than that, i thinkw e move on to open discussion or office hours</p> -<p>16:14 <code>&lt;smoser</code>&gt; #topic Open Discussion</p> -<p>16:14 <code>&lt;smoser</code>&gt; anyone have anything for this ?</p> -<p>16:14 <code>&lt;robjo</code>&gt; Customer has run into an issue where we run out of threads during the user script phase, should generally set TasksMax in the service file, i.e. is that of interest upstream?</p> -<p>16:15 <code>&lt;robjo</code>&gt; we are still testing, but that appears to be the solution for this particular problem</p> -<p>16:15 <code>&lt;smoser</code>&gt; robjo, i dont have an immediate objection to that idea.</p> -<p>16:16 <code>&lt;smoser</code>&gt; could you open a bug ?</p> -<p>16:16 <code>&lt;robjo</code>&gt; sure</p> -<p>16:17 <code>&lt;smoser</code>&gt; i dont think that we'd want to pull that change in right now, but it otherwise seems reasonable at frist b lush.</p> -<p>16:18 <code>&lt;smoser</code>&gt; anything else ?</p> -<p>16:18 <code>&lt;robjo</code>&gt; Agreed, do't think this is sufficiently urgent for Thursday's release, it can wait until the next one</p> -<p>16:19 <code>&lt;ajorg</code>&gt; were there other bugs that we should consider high enough prio to deserve landing a fix in the release?</p> -<p>16:20 <code>&lt;smoser</code>&gt; ajorg, the only 2 that i'm aware of are linked in those mp. i can dig the numbers</p> -<p>16:21 <code>&lt;smoser</code>&gt; * bug 1717598</p> -<p>16:21 <code>&lt;ubot5</code>&gt; bug 1717598 in cloud-init (Ubuntu) "Traceback when passing user-data on GCE" [High,In progress] <a href="https://launchpad.net/bugs/1717598">https://launchpad.net/bugs/1717598</a></p> -<p>16:21 <code>&lt;smoser</code>&gt; * bug 1717627</p> -<p>16:21 <code>&lt;ubot5</code>&gt; bug 1717627 in cloud-init "permission denied when executing dhclient in Ec2 datasource" [High,In progress] <a href="https://launchpad.net/bugs/1717627">https://launchpad.net/bugs/1717627</a></p> -<p>16:21 <code>&lt;ajorg</code>&gt; ok</p> -<p>16:22 <code>&lt;smoser</code>&gt; Anything else? other wise i'll call this meeting done and hang around for office hours for the next 30 m inutes at least.</p> -<p>16:22 <code>&lt;smoser</code>&gt; thanks for attending / feedback, robjo and ajorg</p> -<p>16:23 <code>&lt;blackboxsw</code>&gt; #link <a href="https://launchpad.net/bugs/1717598">https://launchpad.net/bugs/1717598</a></p> -<p>16:23 <code>&lt;ubot5</code>&gt; Ubuntu bug 1717598 in cloud-init (Ubuntu) "Traceback when passing user-data on GCE" [High,In progress]</p> -<p>16:24 <code>&lt;blackboxsw</code>&gt; #link<a href="https://launchpad.net/bugs/1717627">https://launchpad.net/bugs/1717627</a></p> -<p>16:24 <code>&lt;ubot5</code>&gt; Ubuntu bug 1717627 in cloud-init "permission denied when executing dhclient in Ec2 datasource" [High,In progress]</p> -<p>16:24 <code>&lt;blackboxsw</code>&gt; just in case</p> -<p>16:24 <code>&lt;blackboxsw</code>&gt; duno whats up with the bot.... again</p> -<p>16:27 <code>&lt;smoser</code>&gt; ok. well, lets move on</p> -<p>16:27 <code>&lt;smoser</code>&gt; #endmeeting</p> -<p>Generated by MeetBot 0.1.5 (<a href="http://wiki.ubuntu.com/meetingology">http://wiki.ubuntu.com/meetingology</a>)</p>Cloud-init bi-weekly status2017-09-05T16:30:00-04:002017-09-05T16:30:00-04:00chad.smith@canonical.comtag:cloud-init.github.io,2017-09-05:/status-2017-09-05.html<h2>Meeting information</h2> -<p><code>* #cloud-init: cloud-init status meeting, 05 Sep at 16:30 — 16:30 UTC</code></p> -<h2>Meeting summary</h2> -<p><em>LINK:</em> <a href="https://public.etherpad-mozilla.org/p/cloud-init-meeting">https://public.etherpad-mozilla.org/p/cloud-init-meeting</a></p> -<p><code>*</code><strong><code>Recent Changes</code></strong><code>(16:35)</code></p> -<ul> -<li>integration of robjo's opensuse items</li> -<li>summit results posted to mailing list https://lists.launchpad.net/cloud-init/msg00094.html</li> -</ul> -<p><em>LINK:</em> <a href="https://lists.launchpad.net/cloud-init/msg00094.html">https://lists.launchpad.net …</a></p><h2>Meeting information</h2> -<p><code>* #cloud-init: cloud-init status meeting, 05 Sep at 16:30 — 16:30 UTC</code></p> -<h2>Meeting summary</h2> -<p><em>LINK:</em> <a href="https://public.etherpad-mozilla.org/p/cloud-init-meeting">https://public.etherpad-mozilla.org/p/cloud-init-meeting</a></p> -<p><code>*</code><strong><code>Recent Changes</code></strong><code>(16:35)</code></p> -<ul> -<li>integration of robjo's opensuse items</li> -<li>summit results posted to mailing list https://lists.launchpad.net/cloud-init/msg00094.html</li> -</ul> -<p><em>LINK:</em> <a href="https://lists.launchpad.net/cloud-init/msg00094.html">https://lists.launchpad.net/cloud-init/msg00094.html</a></p> -<p><code>*</code><strong><code>In Progress Development</code></strong><code>(16:38)</code></p> -<ul> -<li><em>LINK:</em> <a href="https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin">https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin</a></li> -<li><em>LINK:</em> <a href="https://bugs.launchpad.net/cloud-init">https://bugs.launchpad.net/cloud-init</a></li> -<li>Opensuse builds: <em>LINK:</em> <a href="https://build.opensuse.org/package/show/Cloud:Tools:Next/cloud-init">https://build.opensuse.org/package/show/Cloud:Tools:Next/cloud-init</a></li> -<li>Ongoing SRU for ubuntu: <em>LINK:</em> <a href="https://people.canonical.com/~ubuntu-archive/pending-sru.html">https://people.canonical.com/~ubuntu-archive/pending-sru.html</a></li> -<li>Meetingology to join for next meeting</li> -</ul> -<p><code>*</code><strong><code>Open Discussion- cloud-init versioning</code></strong><code>(16:41)</code></p> -<ul> -<li>Will target a new versioned release Sept 21st</li> -<li>cloud-init will have major.minor versioning represented by &lt;2-digit-year&gt;.<minor>. The <minor> version will be 1-based and increment with each quarterly release.</li> -<li><em>ACTION</em> smoser to write to mailing list with that as the plan and suggesting the target release date of 17.1 on the Sept 21.</li> -<li>cloud-init releases will target quarterly cycles</li> -</ul> -<p><code>*</code><strong><code>Office Hours</code></strong><code>(15:15)</code></p> -<h2>Vote results</h2> -<h2>Done items</h2> -<p><code>* (none)</code></p> -<h2>People present (lines said)</h2> -<p><code>* blackboxsw</code> -<code>* smoser</code> -<code>* powersj</code> -<code>* rharper</code> -<code>* dpb1</code></p> -<h2>Full Log</h2> -<p><em>LINK:</em> <a href="https://irclogs.ubuntu.com/2017/09/05/%23cloud-init.html#t16:32">https://irclogs.ubuntu.com/2017/09/05/%23cloud-init.html#t16:32</a></p> \ No newline at end of file diff --git a/index.html b/index.html deleted file mode 100644 index dafcafb..0000000 --- a/index.html +++ /dev/null @@ -1,390 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info - - - - -
- - - - - -
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 29 June 2021 in status-meeting-minutes - - - • 2 min read -

-
-
-

Meeting information

- -

Meeting summary

- -

People present (lines …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 15 June 2021 in status-meeting-minutes - - - • 2 min read -

-
-
-

Meeting information

- -

Meeting summary

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 01 June 2021 in status-meeting-minutes - - - • 2 min read -

-
-
-

Meeting information

- -

Meeting summary

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 18 May 2021 in status-meeting-minutes - - - • 2 min read -

-
-
-

Meeting information

- -

Meeting summary

-

People present (lines said)

-
    -
  • blackboxsw (12)
  • -
  • paride (4)
  • -
  • smoser (4)
  • -
  • meetingology (2)
  • -
  • ubot5 (1 …
-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 06 April 2021 in status-meeting-minutes - - - • 2 min read -

-
-
-

Meeting information

- -

Meeting summary

-

People present (lines said)

-
    -
  • hamalq (7)
  • -
  • blackboxsw (6)
  • -
  • falcojr (3)
  • -
  • meetingology (2)
  • -
  • Odd_Bloke (1 …
-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 23 March 2021 in status-meeting-minutes - - - • 2 min read -

-
-
-

Meeting information

- -

Meeting summary

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 09 March 2021 in status-meeting-minutes - - - • 3 min read -

-
-
-

Meeting information

- -

Meeting summary

- -

People present (lines …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 23 February 2021 in status-meeting-minutes - - - • 2 min read -

-
-
-

Meeting information

- -

Meeting summary

- -

People present (lines …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 17 November 2020 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://discourse.ubuntu.com/t/cloud-init-statue-11-17-20/19391 - LINK: https://github.com/canonical/cloud-init/pull/655 i'd …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 08 September 2020 in status-meeting-minutes - - - • 5 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-08-25.html#status-2020-08-25

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:21 …

-
- Continue reading -
-
- - - - - - - -
- - - - - - - - \ No newline at end of file diff --git a/index2.html b/index2.html deleted file mode 100644 index 19cda6d..0000000 --- a/index2.html +++ /dev/null @@ -1,391 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info - - - - -
- - - - - -
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 25 August 2020 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:27.

-

Recent Changes

-

The …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 28 July 2020 in status-meeting-minutes - - - • 3 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-07-14.html#status-2020-07-14

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:58 …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 14 July 2020 in status-meeting-minutes - - - • 5 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-06-30.html#status-2020-06-30

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:55 …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 30 June 2020 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-06-16.html#status-2020-06-16

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:28 …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 16 June 2020 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:24.

-

In-progress Development

-

The …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 02 June 2020 in status-meeting-minutes - - - • 8 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:24.

-

Recent Changes

-

The …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 19 May 2020 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-05-05.html#status-2020-05-05

-

#cloud-init pull-requests https://git.io/JeVed | Meeting minutes: https://goo.gl …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 05 May 2020 in status-meeting-minutes - - - • 4 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:20.

-

Recent Changes

-

The …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 14 April 2020 in status-meeting-minutes - - - • 4 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-03-31.html#status-2020-03-31

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:23 …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 31 March 2020 in status-meeting-minutes - - - • 4 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-03-10.html#status-2020-03-10

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:22 …

-
- Continue reading -
-
- - - - - - - -
- - - - - - - - \ No newline at end of file diff --git a/index3.html b/index3.html deleted file mode 100644 index 47e9dba..0000000 --- a/index3.html +++ /dev/null @@ -1,392 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info - - - - -
- - - - - -
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 10 March 2020 in status-meeting-minutes - - - • 9 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-02-18.html#status-2020-02-18

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:24 …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 18 February 2020 in status-meeting-minutes - - - • 5 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-02-04.html#status-2020-02-04

-

Previous Actions

-

The discussion about "Previous Actions" started at 17:37 …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 04 February 2020 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Previous Actions

-

The discussion about "Previous Actions" started at 17:27.

-

Recent Changes

-

The …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 21 January 2020 in status-meeting-minutes - - - • 5 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Previous Actions

-

The discussion about "Previous Actions" started at 17:50.

-
    -
  • LINK: bugs.launchpad …
-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 07 January 2020 in status-meeting-minutes - - - • 11 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2019-12-10.html#status-2019-12-10

-

Previous Actions

-

The discussion about "Previous Actions" started at 17:36 …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 10 December 2019 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 17:22.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 26 November 2019 in status-meeting-minutes - - - • 9 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 17:28.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 29 October 2019 in status-meeting-minutes - - - • 12 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:26.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 08 October 2019 in status-meeting-minutes - - - • 9 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:23.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 09 September 2019 in status-meeting-minutes - - - • 5 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2019-08-19.html#status-2019-08-19

-

Previous actions

-

The discussion about "Previous actions" started at 16:30 …

-
- Continue reading -
-
- - - - - - - -
- - - - - - - - \ No newline at end of file diff --git a/index4.html b/index4.html deleted file mode 100644 index 38b8627..0000000 --- a/index4.html +++ /dev/null @@ -1,391 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info - - - - -
- - - - - -
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 19 August 2019 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2019-08-05.html#status-2019-08-05

-

cloud-init Reviews: http://bit.ly/ci-reviews | Meeting minutes: https://goo.gl …

-
- Continue reading -
-
-
- -
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 22 July 2019 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:17.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 08 July 2019 in status-meeting-minutes - - - • 10 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:18.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 24 June 2019 in status-meeting-minutes - - - • 10 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:23.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 10 June 2019 in status-meeting-minutes - - - • 11 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:23.

-

Recent Changes

-

The …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 28 May 2019 in status-meeting-minutes - - - • 4 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 15:27.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 13 May 2019 in status-meeting-minutes - - - • 14 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:31.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 28 January 2019 in status-meeting-minutes - - - • 5 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:27.

-
    -
  • ACTION: carry over blackboxsw close and land Openstack …
-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 07 January 2019 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:38.

- -
- Continue reading -
-
- - - - - - - -
- - - - - - - - \ No newline at end of file diff --git a/index5.html b/index5.html deleted file mode 100644 index bbbda1f..0000000 --- a/index5.html +++ /dev/null @@ -1,398 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info - - - - -
- - - - - -
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 10 December 2018 in status-meeting-minutes - - - • 4 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:13.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 26 November 2018 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io - LINK: https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427 - LINK: https://code …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 12 November 2018 in status-meeting-minutes - - - • 4 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:20.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 29 October 2018 in status-meeting-minutes - - - • 4 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:22.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 15 October 2018 in status-meeting-minutes - - - • 9 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:18.

- -

Recent Changes

-

The …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 25 September 2018 in status-meeting-minutes - - - • 5 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:09.

-

Recent Changes

-

The discussion about "Recent Changes …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 04 September 2018 in status-meeting-minutes - - - • 5 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/ - LINK: https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin - LINK: https://powersj.github.io/post …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 20 August 2018 in status-meeting-minutes - - - • 4 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:13.

-

Recent Changes

-

The discussion about "Recent Changes …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 06 August 2018 in status-meeting-minutes - - - • 5 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:09.

-
    -
  • ACTION: rharper …
-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 02 July 2018 in status-meeting-minutes - - - • 4 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:09.

- -
- Continue reading -
-
- - - - - - - -
- - - - - - - - \ No newline at end of file diff --git a/index6.html b/index6.html deleted file mode 100644 index 54946d9..0000000 --- a/index6.html +++ /dev/null @@ -1,393 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info - - - - -
- - - - - -
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 18 June 2018 in status-meeting-minutes - - - • 8 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:11.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 29 May 2018 in status-meeting-minutes - - - • 10 min read -

-
-
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:09.

-

Recent Changes …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 14 May 2018 in status-meeting-minutes - - - • 7 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:09.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 30 April 2018 in status-meeting-minutes - - - • 12 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:07.

-

#cloud-init Reviews: http://bit.ly/ci-reviews | Meeting …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 16 April 2018 in status-meeting-minutes - - - • 8 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent-changes

-

The discussion about "Recent-changes" started at 16:04.

-

In-progresss Development

-

The discussion about "In-progresss Development" started at …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 02 April 2018 in status-meeting-minutes - - - • 5 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:08.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 19 March 2018 in status-meeting-minutes - - - • 11 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:05.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 05 March 2018 in status-meeting-minutes - - - • 6 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent Changes

-

The discussion about "Recent Changes" started at 17:02.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Fri 16 February 2018 in status-meeting-minutes - - - • 7 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent changes

-

The discussion about "Recent changes" started at 16:08.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 22 January 2018 in status-meeting-minutes - - - • 8 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent changes

-

The discussion about "Recent changes" started at 16:10.

- -
- Continue reading -
-
- - - - - - - -
- - - - - - - - \ No newline at end of file diff --git a/index7.html b/index7.html deleted file mode 100644 index 2aee796..0000000 --- a/index7.html +++ /dev/null @@ -1,359 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info - - - - -
- - - - - -
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 08 January 2018 in status-meeting-minutes - - - • 11 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent changes

-

The discussion about "Recent changes" started at 16:04.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 11 December 2017 in status-meeting-minutes - - - • 13 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:07.

- -
- Continue reading -
-
-
- - -
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 16 October 2017 in status-meeting-minutes - - - • 4 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:08

-

In Progress Development

-

The discussion about "In Progress Development …

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 02 October 2017 in status-meeting-minutes - - - • 10 min read -

-
-
-

Meeting information

- -

Meeting summary

-

Recent Changes / Highlights

-

The discussion about "Recent Changes / Highlights" started at 16:06.

- -
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Mon 18 September 2017 in status-meeting-minutes - - - • 3 min read -

-
-
-

Meeting information

- -

Meeting summary

- -

Release Preparation

-

The discussion …

-
- Continue reading -
-
-
-
-
-

Cloud-init github.io details

-

- Posted on Tue 05 September 2017 in Background - - - • 1 min read -

-
-
-

Cloud-init project info page

-

Cloud-init dev team created a github.io project page based on pelican and Flex theme to host cloud-init status meeting notes.

-
- Continue reading -
-
-
-
-
-

Cloud-init bi-weekly status

-

- Posted on Tue 05 September 2017 in status-meeting-minutes - - - • 1 min read -

-
-
-

Meeting information

-

* #cloud-init: cloud-init status meeting, 05 Sep at 16:30 — 16:30 UTC

-

Meeting summary

-

LINK: https://public.etherpad-mozilla.org/p/cloud-init-meeting

-

*Recent Changes(16:35)

-
    -
  • integration of robjo's opensuse items
  • -
  • summit results posted to mailing list https://lists.launchpad.net/cloud-init/msg00094.html
  • -
-

LINK: https://lists.launchpad.net …

-
- Continue reading -
-
- - - - - - - -
- - - - - - - - \ No newline at end of file diff --git a/pelican-plugins b/pelican-plugins new file mode 160000 index 0000000..4437398 --- /dev/null +++ b/pelican-plugins @@ -0,0 +1 @@ +Subproject commit 443739890a96125f4cfa796972a7b53119df89ff diff --git a/pelicanconf.py b/pelicanconf.py new file mode 100644 index 0000000..c2bae14 --- /dev/null +++ b/pelicanconf.py @@ -0,0 +1,63 @@ +#!/usr/bin/env python +# -*- coding: utf-8 -*- # +from __future__ import unicode_literals + +SITENAME = u'Cloud-init Project Info' +SITEURL = '' +AUTHOR = u'chad.smith@canonical.com' +SITEURL = '' +SITENAME = 'Cloud-init Info' +SITETITLE = 'Cloud-init' +SITESUBTITLE = 'Make your cloud images be all they can be' +SITEDESCRIPTION = 'Cloud-init project updates and general information' +SITELOGO = SITEURL + '/images/cloud-init-orange.svg' +FAVICON = SITEURL + '/theme/img/favicon.ico' + +USE_FOLDER_AS_CATEGORY = False +MAIN_MENU = True +HOME_HIDE_TAGS = True + +BROWSER_COLOR = '#2c001e' +ROBOTS = 'index, follow' + +PATH = 'content' + +TIMEZONE = 'America/New_York' + +DEFAULT_LANG = u'English' + +# Feed generation is usually not desired when developing +FEED_ALL_ATOM = None +CATEGORY_FEED_ATOM = None +TRANSLATION_FEED_ATOM = None +AUTHOR_FEED_ATOM = None +AUTHOR_FEED_RSS = None + +# Blogroll +LINKS = (('Docs', 'https://cloudinit.readthedocs.org/'), + ('Overview', 'https://cloud-init.io'), + ('Hacking', 'https://cloudinit.readthedocs.io/en/latest/topics/hacking.html'), + ('CI builds', 'https://jenkins.ubuntu.com/server/view/cloud-init/'), + ('Code', 'https://launchpad.net/cloud-init'),) + +# Social widget +SOCIAL = (('github', 'https://github.com/cloud-init'), + ('wechat', 'https://webchat.freenode.net/?channels=cloud-init'),) + +MENUITEMS = (('Archives', '/archives.html'), + ('Categories', '/categories.html'), + ('Tags', '/tags.html'),) + +DEFAULT_PAGINATION = 10 + +# Uncomment following line if you want document-relative URLs when developing +#RELATIVE_URLS = True +THEME = 'Flex' +# Plugins config +JINJA_ENVIRONMENT = { + 'extensions': ['jinja2.ext.i18n'] +} +PLUGIN_PATHS = ['pelican-plugins'] +PLUGINS = ['sitemap', 'i18n_subsites', 'post_stats'] + +STATIC_PATHS = ['images', 'extra'] diff --git a/publishconf.py b/publishconf.py new file mode 100644 index 0000000..208e909 --- /dev/null +++ b/publishconf.py @@ -0,0 +1,24 @@ +#!/usr/bin/env python +# -*- coding: utf-8 -*- # +from __future__ import unicode_literals + +# This file is only used if you use `make publish` or +# explicitly specify it as your config file. + +import os +import sys +sys.path.append(os.curdir) +from pelicanconf import * + +SITEURL = 'https://cloud-init.github.io' +RELATIVE_URLS = False + +FEED_ALL_ATOM = 'feeds/all.atom.xml' +CATEGORY_FEED_ATOM = 'feeds/%s.atom.xml' + +DELETE_OUTPUT_DIRECTORY = True + +# Following items are often useful when publishing + +#DISQUS_SITENAME = "" +GOOGLE_ANALYTICS = "UA-50554247-3" diff --git a/sitemap.xml b/sitemap.xml deleted file mode 100644 index a03383c..0000000 --- a/sitemap.xml +++ /dev/null @@ -1,538 +0,0 @@ - - - - -https://cloud-init.github.io/ -2021-06-29T17:39:08-00:00 -daily -0.5 - - - -https://cloud-init.github.io/archives.html -2021-06-29T17:39:08-00:00 -daily -0.5 - - - -https://cloud-init.github.io/tags.html -2021-06-29T17:39:08-00:00 -daily -0.5 - - - -https://cloud-init.github.io/categories.html -2021-06-29T17:39:08-00:00 -daily -0.5 - - - -https://cloud-init.github.io/status-2021-06-29.html -2021-06-29T16:23:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2021-06-15.html -2021-06-15T17:17:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2021-06-01.html -2021-06-01T17:25:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2021-05-18.html -2021-05-18T16:32:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2021-04-06.html -2021-04-06T16:20:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2021-03-23.html -2021-03-23T17:22:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2021-03-09.html -2021-03-09T17:19:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2021-02-23.html -2021-02-23T17:18:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2020-11-17.html -2020-11-17T17:25:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2020-09-08.html -2020-09-08T16:18:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2020-08-25.html -2020-08-25T16:24:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2020-07-28.html -2020-07-28T16:55:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2020-07-14.html -2020-07-14T16:52:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2020-06-30.html -2020-06-30T16:22:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2020-06-16.html -2020-06-16T16:21:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2020-06-02.html -2020-06-02T16:21:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2020-05-19.html -2020-05-19T16:18:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2020-05-05.html -2020-05-05T16:16:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2020-04-14.html -2020-04-14T16:17:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2020-03-31.html -2020-03-31T16:19:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2020-03-10.html -2020-03-10T16:22:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2020-02-18.html -2020-02-18T17:35:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2020-02-04.html -2020-02-04T17:23:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2020-01-21.html -2020-01-21T17:42:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2020-01-07.html -2020-01-07T17:30:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2019-12-10.html -2019-12-10T17:17:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2019-11-26.html -2019-11-26T17:23:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2019-10-29.html -2019-10-29T16:20:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2019-10-08.html -2019-10-08T16:18:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2019-09-09.html -2019-09-09T16:26:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2019-08-19.html -2019-08-19T16:18:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2019-08-05.html -2019-08-05T16:16:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2019-07-22.html -2019-07-22T16:15:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2019-07-08.html -2019-07-08T16:16:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2019-06-24.html -2019-06-24T16:18:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2019-06-10.html -2019-06-10T16:19:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2019-05-28.html -2019-05-28T15:23:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2019-05-13.html -2019-05-13T16:25:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2019-01-28.html -2019-01-28T16:26:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2019-01-07.html -2019-01-07T16:36:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2018-12-10.html -2018-12-10T16:11:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2018-11-26.html -2018-11-26T16:18:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2018-11-12.html -2018-11-12T16:17:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2018-10-29.html -2018-10-29T16:21:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2018-10-15.html -2018-10-15T16:15:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2018-09-25.html -2018-09-25T16:05:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2018-09-04.html -2018-09-04T16:08:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2018-08-20.html -2018-08-20T16:09:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2018-08-06.html -2018-08-06T16:04:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2018-07-02.html -2018-07-02T16:05:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2018-06-18.html -2018-06-18T16:08:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2018-05-29.html -2018-05-29T16:05:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2018-05-14.html -2018-05-14T16:05:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2018-04-30.html -2018-04-30T16:04:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2018-04-16.html -2018-04-16T16:01:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2018-04-02.html -2018-04-02T16:05:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2018-03-19.html -2018-03-19T16:02:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2018-03-05.html -2018-03-05T17:00:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2018-02-16.html -2018-02-16T16:08:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2018-01-22.html -2018-01-22T16:08:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2018-01-08.html -2018-01-08T16:03:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2017-12-11.html -2017-12-11T16:05:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2017-11-13.html -2017-11-13T16:03:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2017-10-30.html -2017-10-30T16:03:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2017-10-16.html -2017-10-16T16:06:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2017-10-02.html -2017-10-02T16:05:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2017-09-18.html -2017-09-18T16:04:00+00:00 -monthly -0.5 - - - -https://cloud-init.github.io/cloud-init-githubio-details.html -2017-09-05T16:30:00-04:00 -monthly -0.5 - - - -https://cloud-init.github.io/status-2017-09-05.html -2017-09-05T16:30:00-04:00 -monthly -0.5 - - - -https://cloud-init.github.io/category/background.html -2017-09-05T16:30:00-04:56 -daily -0.5 - - - -https://cloud-init.github.io/category/status-meeting-minutes.html -2021-06-29T16:23:00-04:56 -daily -0.5 - - - -https://cloud-init.github.io/author/chadsmithcanonicalcom.html -2021-06-29T16:23:00-04:56 -daily -0.5 - - - diff --git a/status-2017-09-05.html b/status-2017-09-05.html deleted file mode 100644 index 70c511e..0000000 --- a/status-2017-09-05.html +++ /dev/null @@ -1,189 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Tue 05 September 2017 in status-meeting-minutes - - • 1 min read -

-
- - -
-

Meeting information

-

* #cloud-init: cloud-init status meeting, 05 Sep at 16:30 — 16:30 UTC

-

Meeting summary

-

LINK: https://public.etherpad-mozilla.org/p/cloud-init-meeting

-

*Recent Changes(16:35)

-
    -
  • integration of robjo's opensuse items
  • -
  • summit results posted to mailing list https://lists.launchpad.net/cloud-init/msg00094.html
  • -
-

LINK: https://lists.launchpad.net/cloud-init/msg00094.html

-

*In Progress Development(16:38)

- -

*Open Discussion- cloud-init versioning(16:41)

-
    -
  • Will target a new versioned release Sept 21st
  • -
  • cloud-init will have major.minor versioning represented by <2-digit-year>.. The version will be 1-based and increment with each quarterly release.
  • -
  • ACTION smoser to write to mailing list with that as the plan and suggesting the target release date of 17.1 on the Sept 21.
  • -
  • cloud-init releases will target quarterly cycles
  • -
-

*Office Hours(15:15)

-

Vote results

-

Done items

-

* (none)

-

People present (lines said)

-

* blackboxsw -* smoser -* powersj -* rharper -* dpb1

-

Full Log

-

LINK: https://irclogs.ubuntu.com/2017/09/05/%23cloud-init.html#t16:32

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2017-09-18.html b/status-2017-09-18.html deleted file mode 100644 index 658cd44..0000000 --- a/status-2017-09-18.html +++ /dev/null @@ -1,267 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Mon 18 September 2017 in status-meeting-minutes - - • 3 min read -

-
- - -
-

Meeting information

- -

Meeting summary

- -

Release Preparation

-

The discussion about "Release Preparation" started at 16:08.

- -

Open Discussion

-

The discussion about "Open Discussion" started at 16:14.

- -

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • smoser (41)
  • -
  • blackboxsw (8)
  • -
  • ubot5 (4)
  • -
  • ajorg (4)
  • -
  • robjo (4)
  • -
  • meetingology (3)
  • -
  • dpb1 (3)
  • -
  • rharper (1)
  • -
-

Full Log

-

16:04 <smoser> #startmeeting cloud-init status meeting

-

16:04 <meetingology> Meeting started Mon Sep 18 16:04:28 2017 UTC. The chair is smoser. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:04 <meetingology>

-

16:04 <meetingology> Available commands: action commands idea info link nick

-

16:05 <blackboxsw> hiya o/

-

16:05 <rharper> o/

-

16:05 <smoser> #link https://public.etherpad-mozilla.org/p/cloud-init-meeting

-

16:05 <dpb1> hello

-

16:05 <smoser> so that contains a agenda that we'd been following

-

16:06 <smoser> #link https://lists.launchpad.net/cloud-init/msg00100.html

-

16:07 <smoser> sorry for slow going here.

-

16:08 <smoser> shoot

-

16:08 <smoser> #topic Release Preparation

-

16:08 <smoser> #subtopic Release Preparation

-

16:08 <smoser> hm..

-

16:09 <smoser> anyway

-

16:09 <smoser> https://lists.launchpad.net/cloud-init/msg00100.html

-

16:09 <smoser> that is the primariy point of this meeting for today.

-

16:09 <smoser> The goal is to make a release named 17.1 on Thursday of this week.

-

16:09 <blackboxsw> strange

-

16:09 <smoser> We have landed several branches in the last few days, and have 2 more to land at least.

-

16:10 <smoser> from http://bit.ly/ci-reviews

-

16:10 <dpb1> meetingology │ Available commands: action commands idea info link nick

-

16:10 <dpb1> something to look into. :)

-

16:10 <blackboxsw> #link http://bit.ly/ci-reviews

-

16:10 <smoser> the two we consider needs to be integrated are

-

16:10 <smoser> https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/330875

-

16:10 <smoser> https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/330880

-

16:11 <smoser> and Chad's (the first) is the one we're looking at now.

-

16:11 <smoser> or that is the one that is non-trivial

-

16:11 <smoser> does anyone here wnat to raise other bugs or MP that they believe should be pulled ?

-

16:12 <smoser> ...

-

16:12 <smoser> ajorg, i think its best to hold off on some of yours until after release.

-

16:13 <smoser> anyone have anything else ?

-

16:13 <blackboxsw> msaika (vmware) pinged on a branch a couple days ago. but I think there is a little of discussion/re-work that's needed there before we land

-

16:13 <ajorg> smoser: I assume you mean the instance identity one, in which case I agree.

-

16:13 <ajorg> (in either case I'd agree)

-

16:13 <smoser> and simpletable

-

16:13 <smoser> yeah

-

16:14 <smoser> ok. so that is where we are. we are still targettin a release on Thursday.

-

16:14 <smoser> other than that, i thinkw e move on to open discussion or office hours

-

16:14 <smoser> #topic Open Discussion

-

16:14 <smoser> anyone have anything for this ?

-

16:14 <robjo> Customer has run into an issue where we run out of threads during the user script phase, should generally set TasksMax in the service file, i.e. is that of interest upstream?

-

16:15 <robjo> we are still testing, but that appears to be the solution for this particular problem

-

16:15 <smoser> robjo, i dont have an immediate objection to that idea.

-

16:16 <smoser> could you open a bug ?

-

16:16 <robjo> sure

-

16:17 <smoser> i dont think that we'd want to pull that change in right now, but it otherwise seems reasonable at frist b lush.

-

16:18 <smoser> anything else ?

-

16:18 <robjo> Agreed, do't think this is sufficiently urgent for Thursday's release, it can wait until the next one

-

16:19 <ajorg> were there other bugs that we should consider high enough prio to deserve landing a fix in the release?

-

16:20 <smoser> ajorg, the only 2 that i'm aware of are linked in those mp. i can dig the numbers

-

16:21 <smoser> * bug 1717598

-

16:21 <ubot5> bug 1717598 in cloud-init (Ubuntu) "Traceback when passing user-data on GCE" [High,In progress] https://launchpad.net/bugs/1717598

-

16:21 <smoser> * bug 1717627

-

16:21 <ubot5> bug 1717627 in cloud-init "permission denied when executing dhclient in Ec2 datasource" [High,In progress] https://launchpad.net/bugs/1717627

-

16:21 <ajorg> ok

-

16:22 <smoser> Anything else? other wise i'll call this meeting done and hang around for office hours for the next 30 m inutes at least.

-

16:22 <smoser> thanks for attending / feedback, robjo and ajorg

-

16:23 <blackboxsw> #link https://launchpad.net/bugs/1717598

-

16:23 <ubot5> Ubuntu bug 1717598 in cloud-init (Ubuntu) "Traceback when passing user-data on GCE" [High,In progress]

-

16:24 <blackboxsw> #linkhttps://launchpad.net/bugs/1717627

-

16:24 <ubot5> Ubuntu bug 1717627 in cloud-init "permission denied when executing dhclient in Ec2 datasource" [High,In progress]

-

16:24 <blackboxsw> just in case

-

16:24 <blackboxsw> duno whats up with the bot.... again

-

16:27 <smoser> ok. well, lets move on

-

16:27 <smoser> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2017-10-02.html b/status-2017-10-02.html deleted file mode 100644 index 1aa6ca6..0000000 --- a/status-2017-10-02.html +++ /dev/null @@ -1,403 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Mon 02 October 2017 in status-meeting-minutes - - • 10 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

Recent Changes / Highlights

-

The discussion about "Recent Changes / Highlights" started at 16:06.

- -

In Progress Development / Highlights

-

The discussion about "In Progress Development / Highlights" started at 16:09.

- -

Open Discussion / Office Hours

-

The discussion about "Open Discussion / Office Hours" started at 16:17.

- -

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • smoser (88)
  • -
  • ajorg (51)
  • -
  • rharper (28)
  • -
  • blackboxsw (25)
  • -
  • robjo (4)
  • -
  • ubot5 (3)
  • -
  • meetingology (3)
  • -
-

Full Log

-

16:05 <smoser> #startmeeting cloud-init

-

16:05 <meetingology> Meeting started Mon Oct 2 16:05:47 2017 UTC. The chair is smoser. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:05 <meetingology>

-

16:05 <meetingology> Available commands: action commands idea info link nick

-

16:06 <smoser> #topic Recent Changes / Highlights

-

16:06 <smoser> hm..

-

16:06 <smoser> 17.1 released https://lists.launchpad.net/cloud-init/msg00106.html

-

16:06 <smoser> thats the biggest thing and only thing i have for this topic

-

16:06 <blackboxsw> #link https://lists.launchpad.net/cloud-init/msg00106.html

-

16:06 <smoser> horay for a release, thanks to those who contributed.

-

16:07 <rharper> \o/

-

16:07 <smoser> 17.2 is set for 2017-12-14

-

16:08 <smoser> https://launchpad.net/cloud-init/+milestone/17.2

-

16:08 <ajorg> yay!

-

16:08 <smoser> feel free to target bugs to that release.

-

16:08 <rharper> #link https://launchpad.net/cloud-init/+milestone/17.2

-

16:08 <rharper> #info please target bugs to the next release

-

16:09 <smoser> does that do anyting ?

-

16:09 <rharper> in the meeting summary, it does

-

16:09 <blackboxsw> smoser: the links showed up in meeting minutes last time

-

16:09 <smoser> k. i always expected the bot to tell me that in a pm

-

16:09 <blackboxsw> meetingology didn't echo though

-

16:09 <rharper> well, smoser may have to do those

-

16:09 <smoser> #topic In Progress Development / Highlights

-

16:09 <blackboxsw> same. but something is up that needs attention.

-

16:10 <blackboxsw> I'll properly handle it when publishing

-

16:10 <rharper> cool

-

16:11 <smoser> Merge Proposals

-

16:11 <smoser> #link http://bit.ly/ci-reviews

-

16:11 <smoser> there are some there for sure. i know that robjo has some he's interested in, and i think ajorg's instance-identity deserves a look

-

16:12 <smoser> as well as simpletable for 17.2

-

16:12 <ajorg> I'd be grateful for both, yes.

-

16:12 <smoser> i am looking at the 'networkd' one which is a blocker as currently Ubuntu does not work properly on azure

-

16:12 <blackboxsw> we should have more bandwidth this week

-

16:12 <smoser> and all sysstemd-networkd systems will not work properly on CloudStack.

-

16:12 <smoser> anything else there?

-

16:13 <robjo> The task limit increase has been tested and solves our problem, thus merging would be great

-

16:13 <smoser> robjo, yeah. athat does seem unlikely to cause issue

-

16:13 <smoser> Trello Board

-

16:13 <smoser> # https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:13 <rharper> #link ?

-

16:13 <smoser> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:14 <robjo> https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/taskLimit that's the branch for the task limit

-

16:15 <robjo> Sorry, I can never find the link for the open merge proposals :( problem exists between the keyboard and the chair

-

16:16 <blackboxsw> will get eyes on that today robjo as your addZypper is about wrapped

-

16:16 <smoser> Bugs

-

16:16 <smoser> #link https://bugs.launchpad.net/cloud-init

-

16:16 <smoser> just mostly pointers... above.

-

16:16 <smoser> for Ubuntu in 16.04, there is one SRU in progress that blackboxsw and i need to verify today

-

16:16 <smoser> and then we will be soon looking at doing an SRU of 17.1-ish

-

16:17 <robjo> Thanks, still in europe, my day is about done, will pick it up tomorrow

-

16:17 <smoser> robjo, link is in topic

-

16:17 <smoser> http://bit.ly/ci-reviews

-

16:17 <smoser> ok. so open discussion i guess. no w?

-

16:17 <smoser> #topic Open Discussion / Office Hours

-

16:17 <smoser> we'll hang around and pay attention to pings and discussion fro the next 30 minutes or so.

-

16:18 <smoser> and after that, feel free to ping.

-

16:19 <ajorg> I'm writing a unit test for a bugfix I'm preparing to submit. It works, but it's slow because readurl retries and waits a second each time

-

16:20 <ajorg> I'm a bit of a mock / patch newb. Anyone can help me see how to patch that argument?

-

16:20 <smoser> you can feel free to mock readurl

-

16:20 <smoser> and set its return_value and look at calls

-

16:21 <smoser> then you dont have to httppretty.

-

16:21 <ajorg> The only thing I want to change about it is the sleep though. Is there a straightforward way to just change one arg?

-

16:21 <blackboxsw> tests/unittests/test_handler/test_handler_chef.py is an example and tests/unittests/test_datasource/test_maas.py

-

16:21 <blackboxsw> I think

-

16:21 <ajorg> Hmm, I could do that, yeah. Would be sufficient for this.

-

16:22 <ajorg> I'd still like to know if there's an easy way to just change one argument to something that gets called somewhere else.

-

16:22 <smoser> you could also mock the time.sleep from url_helper

-

16:22 <ajorg> hahaha, yes. that's what I need to do.

-

16:22 <rharper> ajorg: if you want to mock the sleep you can decorate the test_ method with @mock.patch(time.sleep)

-

16:22 <smoser> we're suggesting other ways generally because there isn't :) at least that i know of.

-

16:23 <ajorg> that's cool, patching time.sleep will do nicely

-

16:24 <ajorg> is there an integration test that looks at what lands on the console?

-

16:24 <ajorg> (going back to my question from before the meeting)

-

16:25 <smoser> no. there coudl be on the nocloud-kvm backend

-

16:25 <smoser> but i think there is no console access currently on lxd

-

16:25 <smoser> and i think that we do not collect console access on nocloud-kvm

-

16:25 <smoser> but as you suggest we should for sure

-

16:25 <ajorg> k

-

16:26 <ajorg> I wondered if systemd might be swallowing my output, or maybe python (boothook in this case is a python script) is making a strange choice when it sets up logging.

-

16:27 <rharper> certainly possible; I know there were issues with cloud-init starting before say rsyslog on non-systemd boots

-

16:28 <rharper> and the python logging has changed w.r.t the default configuration; cloud-init main sort of expects this transition as it starts up in init-local and it has not yet read the cloud-config for logging configuration yet, so it reads that and then does some replay

-

16:28 <ajorg> interesting

-

16:29 <smoser> ajorg, you're writing to stdout/err with logging from a boothook ?

-

16:29 <ajorg> at least I would have thought cloud-init-output.log would contain my logs though, since it's more a redirect of stderr and stdout, right?

-

16:29 <ajorg> yeah

-

16:29 <rharper> correct

-

16:29 <rharper> this is from a bootcmd ?

-

16:29 <ajorg> no, #cloud-boothook

-

16:29 * rharper hasn't used boothook

-

16:29 <smoser> hm..

-

16:30 <ajorg> boothooks are super useful

-

16:32 <rharper> smoser: when do boot_hooks run ? local ? net ?

-

16:33 <rharper> I'm not sure yet where stdout/err for boot hooks occur, but you can dump each from the units via: journalctl -u cloud-init-local.service (or cloud-init.service)

-

16:33 <blackboxsw> "This is the earliest hook available. Note, that there is no mechanism provided for running only once"

-

16:34 <blackboxsw> I'm checking the code now (local/pre-local maybe)?

-

16:34 <rharper> yeah, saw that; it runs in-image scripts programs

-

16:34 <ajorg> I did that too, and don't see anything.

-

16:34 <ajorg> (journalctl)

-

16:34 <rharper> you should see some output

-

16:34 <rharper> but not seeing your hook in there ?

-

16:34 <ajorg> I can tell by other means that the hook ran

-

16:34 <ajorg> just don't see that it printed anything

-

16:35 <ajorg> my prime suspect if systemd can't do something bad here is that python makes some decision about not actually logging.

-

16:35 <ajorg> and I need to be more explicit that it should log

-

16:36 <rharper> so, the boot_hook will sub out each part, I see no capture on the stderr/stdout ; so I would expect those to go to whatever is currently capturing those;

-

16:37 <rharper> s/sub/subprocess

-

16:38 <ajorg> yup, that's what I expect too, and what I recall seeing on Amazon Linux

-

16:38 <rharper> since it's using cloud-init's util.subp, there should be a debug level message saying 'Running command %s with allowed return codes %s' which maches a path to the boothook

-

16:38 <rharper> I would expect to see that in the cloud-init.log

-

16:39 <smoser> http://paste.ubuntu.com/25661692/

-

16:39 <ajorg> yup, I do see that

-

16:39 <rharper> the output of script, I think should go to cloud-init-output.log

-

16:39 <smoser> i'm testing ^ on serverstack now.

-

16:39 <smoser> i verified the commands run on lxd but not look at console there.

-

16:39 <ajorg> thanks

-

16:40 <smoser> actually.. yeah, BOOTHOOK does run, but doesnt seem to have stdout tied to same place as bootcmd

-

16:41 <ajorg> oh?

-

16:41 <ajorg> I'm slightly surprised it's not just me

-

16:42 <smoser> http://paste.ubuntu.com/25661714/

-

16:42 <rharper> it really should be in the journal/console if stdout is not redirected to a file, cloud-init-local service

-

16:43 <smoser> that reproduces in lxc

-

16:44 <rharper> smoser: in your instance on serverstack, do you see your BOOTHOOK in journalctl -b -u cloud-init-local.service ?

-

16:44 <smoser> ajorg, please go ahead and open a bug.

-

16:44 <ajorg> cool (not cool :-P)

-

16:44 <ajorg> will do

-

16:44 <smoser> # journalctl -b -u cloud-init.service | grep BOOT

-

16:44 <smoser> Oct 02 16:37:41 a5 cloud-init[121]: BOOTCMD: Mon, 02 Oct 2017 16:37:41 +0000: a5

-

16:44 <smoser> ^ that is from lxd

-

16:45 <rharper> and what about the welcome message from cloud-init ?

-

16:45 <smoser> i think not.

-

16:45 <rharper> bootcmd does: util.subp(cmd, env=env, capture=False) ; where boot_hook does: util.subp([filepath], env=env)

-

16:46 <smoser> yeah, so boot_hook definitely swallowed. and should not be.

-

16:47 <rharper> yeah

-

16:49 <ajorg> https://bugs.launchpad.net/cloud-init/+bug/1720841

-

16:49 <ubot5> Ubuntu bug 1720841 in cloud-init "Output from boothook is not logged" [Undecided,New]

-

16:50 <ajorg> Meanwhile I need to setup more explicit logging from that boothook anyway, so I'm okay.

-

16:51 <blackboxsw> #link https://bugs.launchpad.net/cloud-init/+bug/1720841

-

16:51 <ubot5> Ubuntu bug 1720841 in cloud-init "Output from boothook is not logged" [Medium,Confirmed]

-

16:55 <ajorg> Here's another one, which I've confirmed with a unit test and proposed a patch: https://bugs.launchpad.net/cloud-init/+bug/1720844

-

16:55 <ubot5> Ubuntu bug 1720844 in cloud-init "UrlError from #include aborts stage" [Undecided,New]

-

16:55 <ajorg> (what is this #link thing you're doing there?)

-

16:55 <smoser> well, the bot is supposed to care and do somethign with it.

-

16:56 <smoser> but /me thinks it doesnt work right :)

-

16:56 <blackboxsw> ajorg: since meetingology is still active, the theory is it is keeping track of links during this meeting

-

16:56 <smoser> (during the meeting)

-

16:56 <ajorg> ah, okay

-

16:57 <ajorg> I think simpletable is completely ready to merge, btw. Any objections? https://code.launchpad.net/~ajorgens/cloud-init/+git/cloud-init/+merge/330525

-

16:57 <blackboxsw> The theory is it writes the meeting notes out for us so we can publish to https://cloud-init.github.io

-

16:57 <ajorg> #link https://code.launchpad.net/~ajorgens/cloud-init/+git/cloud-init/+merge/330525 ;-)

-

16:57 <blackboxsw> geg

-

16:57 <blackboxsw> heh

-

16:58 <blackboxsw> ajorg: I think we were good on that changeset, and we only wanted to wait post 17.1 cut to avoid potential regression

-

16:59 <ajorg> great

-

16:59 <blackboxsw> I'm +1 on that will give it a spin today and then I think we can land it

-

17:01 <smoser> blackboxsw, ajorg my thoughts on the simpletable...

-

17:01 <ajorg> here it comes...

-

17:01 <ajorg> :-P

-

17:01 <blackboxsw> :)

-

17:02 <smoser> i would like to have a machine friendly output available

-

17:02 <smoser> human friendly is good, but machine friendly solves the actual goal of writing the stuff.

-

17:02 <ajorg> So I modified it to display exactly as prettytable did

-

17:02 <smoser> oh really.

-

17:02 <smoser> wow

-

17:02 <ajorg> which is admittedly not machine friendly

-

17:02 <ajorg> not especially

-

17:02 <smoser> then i guess i can't object at all.

-

17:02 <ajorg> but it's at least as good as prettytable

-

17:03 <smoser> in that its backwards compat

-

17:03 <smoser> right.

-

17:03 <ajorg> ^ this was my goal, to get you to not object

-

17:03 <smoser> i still think we should probaly additionally write some machine friendly json

-

17:03 <ajorg> agreed, that would be better

-

17:03 <smoser> i tihnk having something human friendly is good though

-

17:03 <smoser> as i know I look at that output

-

17:04 <ajorg> it meets my goal of not depending on prettytable

-

17:04 <smoser> and parsing json would be less nice

-

17:04 <smoser> yeah

-

17:05 <smoser> so based on your assertion that it outputs the same as pretty table, i have no objections. only future hopes.

-

17:05 <smoser> and i do agree dropping pretty table is nice

-

17:05 <ajorg> winning

-

17:06 <blackboxsw> smoser: yeah I was wondering how we generally expect people/machines to parse cloud-init-output.log. Right now it's kindof hard to do machine parsing of cloud-init-output.log.

-

17:07 <smoser> blackboxsw, yeah. cloud-init-output.log is not intended to be machine friendly.

-

17:07 <blackboxsw> do we know already of non-human consumers of the formatting in cloud-init.output.log?

-

17:07 <smoser> but the console actually has value in having machien friendly things on it.

-

17:08 <smoser> my feeling is if you have access to /var/log/cloud-init.log, then you could very easily have written whatever you wanted to another file that was purely machine friendly.

-

17:08 <blackboxsw> was wondering where we would intend to dump machine-friendly json

-

17:08 <blackboxsw> yeah

-

17:08 <smoser> but the console (/dev/ttyS0) boot log is different

-

17:08 <smoser> in that it can give you a couple things you'd not find easy access to

-

17:09 <smoser> a.) ssh public keys for the system (providing out of band communication of this data)

-

17:09 <smoser> b.) network configuration info: providn useful bits of data on how you might get to this system

-

17:10 <smoser> systemd makes it "fun" to get that data to the console in a safe way

-

17:12 <ajorg> ugh yes. systemd like to stomp all over your consoles.

-

17:19 <blackboxsw> ok so did we want to iterate on simpletable to dump json, or just look for cloud-init to write supplementary json files under /run/cloud-init

-

17:20 <blackboxsw> .. after we land ajorg's branch

-

17:21 <ajorg> I think it's a good idea to dump json fragments to console for some things, but I suspect smoser will still not want to break anyone who might be using the tables, so probably best to land my branch as-is

-

17:23 <smoser> yeah, i agree with ajorg. for now, we can just take a replacement that drops prettytable

-

17:23 <smoser> there are improvments to be done there, but this is a simple win

-

17:29 <smoser> we'll go ahead and end meeting here.

-

17:29 <smoser> i'll still be around. thanks all!

-

17:29 <smoser> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2017-10-16.html b/status-2017-10-16.html deleted file mode 100644 index a0014fe..0000000 --- a/status-2017-10-16.html +++ /dev/null @@ -1,255 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Mon 16 October 2017 in status-meeting-minutes - - • 4 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:08

-

In Progress Development

-

The discussion about "In Progress Development" started at 16:13

- -

Office Hours

-

The discussion about "Office Houres" started at 16:25

-
    -
  • open season for discussions, bug requests, review requests for the next 30 mins
  • -
-

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (49)
  • -
  • smoser (8)
  • -
  • ubot5 (3)
  • -
  • meetingology (3)
  • -
  • rharper (3)
  • -
-

Full Log

-

16:06 <blackboxsw> #startmeeting Cloud-init bi-weekly status

-

16:06 <meetingology> Meeting started Mon Oct 16 16:06:51 2017 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:06 <meetingology>

-

16:06 <meetingology> Available commands: action commands idea info link nick

-

16:08 <blackboxsw> #topic Recent Changes

-

16:08 <blackboxsw> Ok last couple of weeks for our team were

-

16:08 <blackboxsw> Ok last couple of weeks for our team were

-

16:08 <blackboxsw> Ok last couple of weeks for our team were 'impacted' by a couple of work conferences for planning next release of cloud-init/curtin etc.

-

16:08 <rharper> o/

-

16:09 <blackboxsw> so things felt a bit slow. but folks have still made some good progress.

-

16:09 <blackboxsw> Some changes that have landed in master:

-

16:09 <blackboxsw> Robert Schweikert: suse cloud-config module to add zypper repos and zypp config

-

16:09 <blackboxsw> Robert Schweikert: Allow cloud-init.final stage to spawn infinite processes

-

16:09 <blackboxsw> Andrew Jorgensen: Remove prettytable dependency

-

16:09 <blackboxsw> Fix dhcp parsing in Artful of networkd leases for CloudStack and Azure

-

16:09 <blackboxsw> Updated packaging copyright file (LP: #1718681)

-

16:09 <ubot5> Launchpad bug 1718681 in cloud-init "Package copyright file omits Apache 2 license" [High,Fix committed] https://launchpad.net/bugs/1718681

-

16:10 <smoser> o/

-

16:10 <blackboxsw> thanks a lot for the contributions on that front folks. There have been a couple of work items that fell out of our conferences related to Ubuntu artful and systemd/networkd support so we've been workin those

-

16:11 <blackboxsw> on the testing front we've re-enable tox support for integration tests

-

16:11 <blackboxsw> and Ubuntu-only has queued a 17.1 SRU release/update into xenial and zesty

-

16:12 <blackboxsw> smoser: rharper powersj anyone else anything else I'm missing on recent changes?

-

16:12 <rharper> blackboxsw: that sounds right

-

16:13 <blackboxsw> ok. next topic

-

16:13 <blackboxsw> #topic In progress development

-

16:14 <blackboxsw> As mentioned, we are walking through the Ubuntu xenial/zesty SRU validation process, so I excpect we will have a release update published this week

-

16:14 * blackboxsw grabs the trello card link

-

16:14 <blackboxsw> #link https://trello.com/c/wROS4mKT/458-sru-171

-

16:15 <blackboxsw> This card will move to the Done lane once we've finished publishing

-

16:16 <blackboxsw> I know powersj has been working the integration test front for KVM as time permits. There will be some upcoming changes there to get us more complex storage/network testing on kvm

-

16:16 <blackboxsw> I know smoser is also working on a couple of Azure-related fixes for artful as well.

-

16:16 <blackboxsw> anything else to add there?

-

16:17 <smoser> https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1722668

-

16:17 <rharper> nothing from me

-

16:17 <ubot5> Ubuntu bug 1722668 in cloud-init (Ubuntu) "Azure: bouncing of network device/publishing of hostname fails on artful" [Critical,Confirmed]

-

16:17 <blackboxsw> #link https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1722668

-

16:18 <blackboxsw> thx

-

16:18 <smoser> that one i'm working on, and then also been trying to get lxc/mount-image-callback

-

16:19 <smoser> the use we ahve for 'lxc-proposed-snapshot' and also for 'mount-image-callback'

-

16:19 <blackboxsw> Also in the same vein of improving dev testing of Ubuntu or really any lxc image is that work smoser referenced above.

-

16:20 <blackboxsw> smoser: is that worth a link at the moment or does it still need polish?

-

16:20 <smoser> https://gist.github.com/smoser/49444542158f2e5f88f1/#file-lxc-pstart-md

-

16:20 <blackboxsw> sweet

-

16:20 <blackboxsw> #link https://gist.github.com/smoser/49444542158f2e5f88f1/#file-lxc-pstart-md

-

16:20 <smoser> right now that is only known to work on lxc 2.18

-

16:21 <smoser> i think we can make it work with earlier versions, and would like to make it work with xenial (2.02.. maybe)

-

16:22 <blackboxsw> yeah I just got my artful box up and was going to use that for the SRU verification

-

16:22 <blackboxsw> also, I think we were going to peek at a solution for the following bug:

-

16:22 <blackboxsw> #link https://bugs.launchpad.net/cloud-init/+bug/1722992

-

16:22 <ubot5> Ubuntu bug 1722992 in cloud-init "On the latest centos 7 release, we are unable to resize our instances filesystems" [Medium,Confirmed]

-

16:23 <blackboxsw> so there might be some minor changes for the OpenStack/MAAS and ConfigDrive datasources

-

16:24 <blackboxsw> ok anything else in "In progress development"?

-

16:24 <blackboxsw> I know we have a queue of active reviews we need to get through. I was expecting we'll have bandwidth for that after this SRU push.

-

16:24 <blackboxsw> #link http://bit.ly/ci-reviews

-

16:25 <blackboxsw> #topic Office Hours

-

16:26 <blackboxsw> #info open season for discussions, bug requests, review requests for the next 30 mins

-

16:29 <smoser> thanks blackboxsw

-

16:34 <blackboxsw> no prob. I was peeking around at puppet this weekend.... might have a branch puppet local(masterless deployment) to put up this week

-

16:34 <blackboxsw> I sort of got distracted by shiny objects while trying to write an SRU test for our existing puppet

-

16:34 <blackboxsw> config module

-

17:01 <blackboxsw> ok two more SRU tests left to write for Azure and datasourceOVF. then we can start validation for the upload

-

17:02 <blackboxsw> office hours coming to a close. but we'll still float in here as always. Happy Monday folks

-

17:02 <blackboxsw> just ping us directly by IRC nick if you aren't getting a response otherwise.

-

17:03 <blackboxsw> tanks again.

-

17:03 <blackboxsw> thanks even

-

17:03 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2017-10-30.html b/status-2017-10-30.html deleted file mode 100644 index daf8b51..0000000 --- a/status-2017-10-30.html +++ /dev/null @@ -1,292 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Mon 30 October 2017 in status-meeting-minutes - - • 6 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

Recent Changes

-

The discussion about “Recent Changes” started at 16:04.

- -

In Progess Development

-

The discussion about “In Progress Development” started at 16:17.

- -

Open Discussion / Office Hours (30 mins)

-

The discussion about “Recent Changes” started at 16:30.

- -

Vote results

-

Done items

-

Meeting summary

-

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (61)
  • -
  • smoser (10)
  • -
  • ubot5 (8)
  • -
  • powersj (6)
  • -
  • robjo (6)
  • -
  • meetingology (3)
  • -
  • rharper (2)
  • -
  • ckonstanski (1)
  • -
-

Full Log

-

16:03 <blackboxsw> #startmeeting cloud-init bi-weekly status

-

16:03 <meetingology> Meeting started Mon Oct 30 16:03:09 2017 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:03 <meetingology>

-

16:03 <meetingology> Available commands: action commands idea info link nick

-

16:04 <blackboxsw> #topic In Progress Development

-

16:04 <blackboxsw> So, the last couple weeks have been fairly busy with Ubuntu an SRU processs for Xenial, Zesty and the new Artful release

-

16:05 <blackboxsw> our SRU process bug captures most of that work

-

16:05 <blackboxsw> #LINK https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1721847

-

16:05 <ubot5> Ubuntu bug 1721847 in cloud-init (Ubuntu Zesty) "sru cloud-init 2017-10-06 (17.1-18-gd4f70470-0ubuntu1)" [Medium,Fix committed]

-

16:07 <blackboxsw> our teams uncovered at least one bug during verification testing

-

16:07 <blackboxsw> LINK https://bugs.launchpad.net/cloud-init/+bug/1725067

-

16:07 <ubot5> Ubuntu bug 1725067 in cloud-init (Ubuntu Artful) "cloud-init resizefs fails when booting with root=PARTUUID=" [Medium,Fix committed]

-

16:08 <blackboxsw> The former bug we have now resolved. This SRU will not be published until we resolve one other bug for EC2-specfic environments to ensure we retain behavior to always bring up dhcp4 on the primary nic

-

16:09 <blackboxsw> I don't think we have created a bug for the ec2 issue yet (it affects artful only) instances with only private ipv4 addresses allocated will not have dhcp4 config'd for that instance

-

16:10 <blackboxsw> We'll link a bug for the above today

-

16:10 <blackboxsw> other work on cloud-init... paste coming

-

16:11 <blackboxsw> * Fix systemd mount target due to busy device or already mounted (LP: #1718287)

-

16:11 <blackboxsw> * Fix simpleteable object as output string (LP: #1722566)

-

16:11 <blackboxsw> * Fix netplan bridge stp boolean (LP: #1721157)

-

16:11 <blackboxsw> * Fix cc_ntp to allow empty configuration "ntp:". Fix ntp integration test to provide valid empty ntp config (LP: 1724951)

-

16:11 <blackboxsw> * Fixed cc_lxd to allow for missing bridge definitions in lxd cloud-config

-

16:11 <blackboxsw> * Dropped fastestmirror plugin for CentOS tests

-

16:11 <blackboxsw> * Numerous test and CI stability improvements

-

16:11 <ubot5> Launchpad bug 1718287 in cloud-init "systemd mount targets fail due to device busy or already mounted" [High,Fix committed] https://launchpad.net/bugs/1718287

-

16:11 <ubot5> Launchpad bug 1722566 in cloud-init "ci-info: <cloudinit.simpletable.SimpleTable object at 0x7fa98d222748>" [Medium,Fix committed] https://launchpad.net/bugs/1722566

-

16:11 <ubot5> Launchpad bug 1721157 in cloud-init "netplan render drops bridge_stp setting" [High,Fix committed] https://launchpad.net/bugs/1721157

-

16:11 <ubot5> Launchpad bug 1724951 in cloud-init "Ntp schema definition permits empty ntp cloud-config, but code disallows" [Medium,In progress] https://launchpad.net/bugs/1724951

-

16:13 <blackboxsw> Also we got a couple of gentoo commits from ckonstanski to Use "rc-service" rather than "service". Thanks again

-

16:13 <rharper> \o/

-

16:14 <ckonstanski> You're welcome, though those were just tiny toy commits to get me indocrinated into the launchpad process. Getting NTP tests to work in gentoo will be more significant.

-

16:15 <blackboxsw> ckonstanski: testing always is time-consuming, but totally worth it. We are still trying build our unit test coverage up so we don't get suprises on different platforms/clouds when sparsely tested modules run. Thanks again

-

16:16 <blackboxsw> oops sorry about the topic for the above ... that should have been the following

-

16:16 <blackboxsw> #topic Recent Changes

-

16:16 <blackboxsw> anything else for recent changes that have landed rharper powersj or others?

-

16:17 <powersj> nope

-

16:17 <rharper> blackboxsw: not yet

-

16:17 <blackboxsw> ok then let's move to next topic

-

16:17 <blackboxsw> #meetingstatus In Progress Development

-

16:17 <blackboxsw> for real.

-

16:18 <blackboxsw> ok so we are wrapping up that one Ec2 bug that was raised by Sargun on friday (which affects Artful)

-

16:18 <blackboxsw> When we have that branch in place, we can kick our final validation of the cloud-init 17.1 updates to Xenial Zesty and Artful.

-

16:19 <blackboxsw> I know smoser just uploaded cloud-init to the newly opened Bionic release as well

-

16:19 <blackboxsw> We will be hitting the review queue a bit this week to wrap up content that we want landed once master is open for more dyna

-

16:20 <blackboxsw> We will be hitting the review queue a bit this week to wrap up content that we want landed once master is open for more significant changesets

-

16:21 <blackboxsw> we've been a little risk averse during the SRU release process

-

16:21 <blackboxsw> As always please watch our trello board for progress on anything we are working

-

16:21 <blackboxsw> LINK https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:22 <powersj> need that #

-

16:22 <blackboxsw> #LINK https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:22 <blackboxsw> ahh thanks oops

-

16:23 <robjo> speaking of reviews thanks for the help so far blackboxsw , now that my schedule should be a bit less crazy I'd like to get back to https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/addZyppRepos

-

16:23 <blackboxsw> Our focus as well for the upcoming work in cloud-init is to increase continuous integration coverage and tooling around cloud-init to make sure we can keep delivering stability across releases

-

16:24 <robjo> since I cannotreproduce the issue the bot has locally and I don't really understand the problem some more help is needed

-

16:24 <blackboxsw> ahh hiya robjo

-

16:24 <powersj> that looks merged

-

16:24 <blackboxsw> robjo: good to hear, we'll watch for updates.

-

16:25 <powersj> smoser went and fixed the flake8 issues

-

16:25 <blackboxsw> robjo: do you mean another branch?

-

16:25 <robjo> blackboxsw: no, that branch, but bot thinks " Needs Fixing ", I just don't get why

-

16:26 <blackboxsw> yeah per robjo's work cloud-init folks can also configure zypper repos . We landed it Sept 21st. (So it's in cloud-init 17.1)

-

16:26 <blackboxsw> commit cc1475d07b9d0727012634ee9c7a914d67b051f5

-

16:26 <blackboxsw> Author: Robert Schweikert <rjschwei@suse.com>

-

16:26 <blackboxsw> Date: Thu Sep 21 11:58:28 2017 -0400

-

16:27 <robjo> Oh, so it did get merged, missed that, never mind

-

16:27 <blackboxsw> as powersj mentioned, I think it was a flake8 CI test issue, so we just fixed the minor issue and landed it as it wasn't a significant content change

-

16:28 <powersj> cloudinit/config/cc_zypper_add_repo.py:15:1: H306: imports not in alphabetical order (cloudinit.util, cloudinit.config.schema.get_schema_doc)

-

16:28 <robjo> much appreciated, still a bit concerning that the flake8 issue did not show up locally :(

-

16:28 <blackboxsw> thx powersj

-

16:29 <powersj> is correct way https://paste.ubuntu.com/25852643/

-

16:29 <robjo> SO flake8 has serious issue with the definition of alpha order :(

-

16:30 <blackboxsw> ;)

-

16:30 <blackboxsw> ok anything else for "In Progress Development" if not we'll transition to the next topic

-

16:30 <blackboxsw> #topic Open Discussion / Office Hours (30 mins)

-

16:31 <blackboxsw> ok we'll hang out in channel if anyone has topics, bugs or features they want to discuss or need some feedback on

-

16:35 <blackboxsw> and as always thanks for contributions folks. It's really great to work on a project where there is so much interest and investment

-

16:42 <smoser> blackboxsw: hey. i'm back now. did you open a bug?

-

16:42 <smoser> i can do so now if you have not.

-

16:43 <blackboxsw> smoser: I haven't done that yet, was just working out the fix

-

16:43 <blackboxsw> please do, then we can link it here

-

16:43 <smoser> ok. i'll do so. and i realized a comment you were making about artful.

-

16:43 <smoser> that we could go leave artful configuring all nics it saw.

-

16:43 <blackboxsw> right, because we allow change of behavior in artful right?

-

16:44 <smoser> as that isn't necessarily "broken" behavior.

-

16:44 <smoser> yeah. i didnt understand that when you said it.

-

16:44 <blackboxsw> ahh, I get you. Right, just that the new behavior of configuring all nics is acceptable as new behavior, but not for Xenial. It's just that artful is slightly busted for local-only ipv4

-

16:45 <smoser> i think it might be easiest both in terms of fixing and in terms of keeping things in our head if we just keep the same behavior everywhere for now.

-

16:46 <smoser> that is... make artful act like xenial in only configuring one nic

-

16:48 <smoser> blackboxsw: actually i dont think there is any reason why we shoudlnt just use bug 1728152

-

16:48 <ubot5> bug 1728152 in cloud-init "IPv4 and IPv6 Dual Stack Does Not work when instance is not assigned public IPv4 address" [High,In progress] https://launchpad.net/bugs/1728152

-

16:48 <smoser> unless you disagree

-

16:51 <blackboxsw> +1 smoser

-

16:52 <blackboxsw> lets use that bug

-

16:59 <blackboxsw> #LINK https://launchpad.net/bugs/1728152

-

16:59 <ubot5> Ubuntu bug 1728152 in cloud-init "EC2 IPv4 and IPv6 Dual Stack Does Not work when instance is not assigned public IPv4 address" [High,In progress]

-

16:59 <blackboxsw> ok looks like we are good for the status meeting

-

17:00 <blackboxsw> thanks for joining all. see you in two weeks

-

17:00 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2017-11-13.html b/status-2017-11-13.html deleted file mode 100644 index 6ad3065..0000000 --- a/status-2017-11-13.html +++ /dev/null @@ -1,303 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Mon 13 November 2017 in status-meeting-minutes - - • 7 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:04

- -

In Progress Development

-

The discussion about "In Progress Development" started at 16:10

- -

Office Hours next 30 minutes

-

The discussion about "Office Hours next 30 minutes" started at 16:13

- -

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (53)
  • -
  • robjo (20)
  • -
  • smoser (17)
  • -
  • via (10)
  • -
  • meetingology (3)
  • -
  • ubot5 (2)
  • -
  • powersj (1)
  • -
  • rharper (1)
  • -
-

Full Log

-

16:03 <blackboxsw> #startmeeting Cloud-init bi-weekly status

-

16:03 <meetingology> Meeting started Mon Nov 13 16:03:13 2017 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:03 <meetingology>

-

16:03 <meetingology> Available commands: action commands idea info link nick

-

16:03 <powersj> o/

-

16:03 <blackboxsw> time change got to us

-

16:04 <blackboxsw> #topic Recent Changes

-

16:05 <blackboxsw> hey folks. thanks for joining just pulling together the content for the last couple weeks of work for the cloud-init project

-

16:06 <smoser> http://paste.ubuntu.com/25954862/

-

16:06 <smoser> $ git log a90a8b1cb3104ee3250ac79d6e25a9ff4f527baa.. | log2dch | sed 's,^ ,,' | pastebinit

-

16:06 <blackboxsw> most of the ubuntu-side of the house was involved in handling the SRU of 17.1 into ubuntu and handling any discovered regressions

-

16:06 <blackboxsw> Published cloud-init packages to Bionic Beaver release

-

16:06 <blackboxsw> Update Gentoo Linux support to "rc-service" scripts as "service" is deprecated, thanks to ckonstanski!

-

16:06 <blackboxsw> Detected and fixed a pre-release regression of resizefs when root path is specified by UUID on the kernel cmdline (LP: #1725067)

-

16:06 <ubot5> Launchpad bug 1725067 in cloud-init (Ubuntu Zesty) "cloud-init resizefs fails when booting with root=PARTUUID=" [Medium,Fix committed] https://launchpad.net/bugs/1725067

-

16:06 <blackboxsw> #link http://paste.ubuntu.com/25954862/

-

16:07 <blackboxsw> #info SRU queued for release today

-

16:07 <blackboxsw> Here's the cloud-init content we published for the last two weeks:

-

16:07 <blackboxsw> #link https://github.com/canonical-server/dev-summary/blob/master/doc/2017-10-31.md

-

16:07 <blackboxsw> #link https://github.com/canonical-server/dev-summary/blob/master/doc/2017-11-07.md

-

16:09 <blackboxsw> 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

-

16:09 <blackboxsw> 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

-

16:09 <blackboxsw> with those SRU regresssions fixed and published to master, we expect cloud-init 17.1 updated in Xenial,Zesty and Artful today

-

16:10 <blackboxsw> #topic In Progress Development

-

16:10 <blackboxsw> smoser: rharper anything here?

-

16:10 <smoser> #link http://bit.ly/ci-reviews

-

16:11 <smoser> robjo has done a couple fixes for SuSE and i've pulled a few of them.

-

16:11 <smoser> he has one up i saw yestderday for ntpSuSE

-

16:11 <smoser> others ther.e we've been delinquent due to some distractions recently.

-

16:11 <rharper> blackboxsw: nothing new for me at the moment

-

16:12 <smoser> and chad had one up for clean and status

-

16:12 <blackboxsw> 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

-

16:12 <smoser> which is nice.

-

16:13 <robjo> moving the meeting an hour foward while we are on Standard time or is this a one time occurance, did I miss an announcement?

-

16:13 <blackboxsw> #topic Office Hours (next 30 minutes)

-

16:14 <robjo> lp#1731619, chrony support, should that also be driven through ntp config or should there be a new config option?

-

16:14 <blackboxsw> so we'll hang out with eyes on this channel for any burning questions/bugs/questions

-

16:14 <smoser> robjo: well, the meeting is listed in UTC time

-

16:14 <smoser> that pays no attention to US legislation to change clocks at random points in the year :)

-

16:15 <robjo> oK, my fault when I added it to my calendar, eay enough to fix ;)

-

16:15 <smoser> but the humans here were also affected :)

-

16:15 <blackboxsw> heh, anyone opposed to shifting this meeting time +30 from now during the next few months?

-

16:15 <blackboxsw> as the meeting now collides w/ another meeting for us

-

16:15 <blackboxsw> :/

-

16:16 <blackboxsw> officially 16:30 UTC?

-

16:17 <robjo> Well, I'd prefer to either follow the "randomness" clock manipulation or not follow it

-

16:19 <robjo> 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

-

16:19 <blackboxsw> fair point. ok let's keep the new time as is.

-

16:20 <blackboxsw> we've discussed side-channel, we can shift our meetings out of the way of this

-

16:20 <blackboxsw> so robjo +1

-

16:20 <blackboxsw> 16:00 UTC

-

16:24 <blackboxsw> 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

-

16:24 <blackboxsw> #link https://jenkins.ubuntu.com/server/view/cloud-init/

-

16:28 <via> 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

-

16:28 <robjo> 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?

-

16:28 <via> like configuring the chef node name to have my instance id in it

-

16:32 <blackboxsw> #link https://bugs.launchpad.net/cloud-init/+bug/1731619

-

16:32 <ubot5> Launchpad bug 1731619 in cloud-init "Support chrony as a client for ntp" [Undecided,New]

-

16:33 <blackboxsw> it's a good bug, we've had a couple of discussions about ntpd versus timesyncd for different system environments

-

16:34 <blackboxsw> 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

-

16:34 <smoser> via: i think what your asking is (i htink) covered in https://trello.com/c/AYaCdQyT

-

16:35 <via> well, i'm trying to do it in a yaml cloud-config file

-

16:35 <smoser> right. as it is right now, via you cann't reference anything from the metadata.

-

16:35 <via> does that mean i need to use #jinja and if so how does that play with #cloud-config ?

-

16:35 <via> oh

-

16:36 <via> bummer

-

16:36 <via> should i just switch to a shell script?

-

16:36 <smoser> but we'd hope to implement that.

-

16:36 <smoser> via: thats really the only way right now. and then in the shell scripty you'd have to query the metadata service yourself.

-

16:36 <via> okay, damn

-

16:36 <via> thanks

-

16:36 <blackboxsw> 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

-

16:36 <smoser> basically... we realize what you're asking is quite helpful and reasonable but dont have a way to do it right now

-

16:36 <smoser> but we do plan on implementing it.

-

16:37 <via> no worries, i'm stuck on an ancient version anyway

-

16:38 <robjo> 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

-

16:39 <robjo> since with a third option the black/white decision being made today will no longer work

-

16:39 <blackboxsw> +1 robjo yeah. rharper was chatting about this potential approach as well

-

16:39 <robjo> look there is also grey ;)

-

16:39 <blackboxsw> heh yeah

-

16:40 <robjo> Next question.... network config.

-

16:40 <blackboxsw> yeah might have to 'grow' an override option in cc_ntp module eventually

-

16:41 <blackboxsw> as those grey use-cases come up (per bugs/requests ;) )

-

16:41 <robjo> 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

-

16:42 <robjo> 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

-

16:43 * blackboxsw is looking for the warning generated

-

16:43 <robjo> 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

-

16:44 <robjo> blackboxsw: "apply_network_config is not currently implemented "

-

16:44 <robjo> "for distribution '%s'. Attempting to use apply_network"

-

16:45 <blackboxsw> ahh. right-o

-

16:45 <robjo> 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 ;)

-

16:47 <robjo> And yes, I realize a bug will need to be filed, but I haven't figured out how to formulate this nicely

-

16:47 <blackboxsw> 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.

-

16:47 <robjo> OK :)

-

16:50 <blackboxsw> 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.

-

16:51 <blackboxsw> 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.

-

16:52 <blackboxsw> we'll keep our eyes open for discussions/suggestions from folks

-

16:54 <robjo> 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 ;)

-

16:56 <blackboxsw> robjo: I'm curious how different that datasource would be from nocloud datasource

-

16:56 <blackboxsw> http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html?highlight=nocloud

-

16:56 <blackboxsw> #link http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html?highlight=nocloud

-

16:56 <blackboxsw> which allows for providing local data instead of dealing with metadata

-

16:56 <blackboxsw> well network metadata

-

16:57 <robjo> 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

-

17:00 <blackboxsw> good deal.... think we are at the top of the hour... so I'll probably end meeting now

-

17:01 <blackboxsw> thanks via robjo rharper powersj & smoser. next meeting 2 weeks same early time

-

17:01 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2017-12-11.html b/status-2017-12-11.html deleted file mode 100644 index 4bda152..0000000 --- a/status-2017-12-11.html +++ /dev/null @@ -1,426 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Mon 11 December 2017 in status-meeting-minutes - - • 13 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:07.

- -

In-progress Development

-

The discussion about "In-progress Development" started at 16:15.

- -

Office Hours (for next 30 mins)

-

The discussion about "Office Hours (for next 30 mins)" started at 16:38.

- -

Vote results

-

Action items, by person

-
    -
  • blackboxsw
  • -
  • blackboxsw bring up any updates in instance-data.json fields for discussion about common use-cases/patterns
  • -
-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (83)
  • -
  • smoser (54)
  • -
  • ajorg (38)
  • -
  • robjo (32)
  • -
  • ubot5 (7)
  • -
  • meetingology (4)
  • -
  • powersj (2)
  • -
  • dpb1 (2)
  • -
  • rharper (2)
  • -
-

Full Log

-

16:05 <blackboxsw> #startmeeting Cloud-init 'bi-weekly' status meeting

-

16:05 <meetingology> Meeting started Mon Dec 11 16:05:16 2017 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:05 <meetingology>

-

16:05 <meetingology> Available commands: action commands idea info link nick

-

16:05 <smoser> thanks for hosting blackboxsw

-

16:05 <blackboxsw> no problemo.

-

16:05 <blackboxsw> happy holidays folks and thanks for joining.

-

16:07 <blackboxsw> #topic Recent Changes

-

16:07 <blackboxsw> As mentioned @ our 17.1 release, we're promising more frequent cloud-init releases.

-

16:08 <blackboxsw> smoser has mailed the list informing cloud-init interested parties that we are targeting a 17.2 release for Thursday this week

-

16:08 <blackboxsw> It's been a few weeks since we've hosted the meeting (I think we missed last meeting), so I'll post some of the development that has landed in trunk

-

16:08 <smoser> #link https://lists.launchpad.net/cloud-init/msg00114.html

-

16:09 <blackboxsw> * All integration tests now function with the nocloud-kvm backend

-

16:09 <blackboxsw> * Fix apport for cloud-name options (LP: #1722564)

-

16:09 <blackboxsw> * Improve warning message when templates aren't found (Robert Schweikert) (LP: #1730135)

-

16:09 <blackboxsw> * Perform null checks for enabled/disabled Red Hat repos (Dave Mulford)

-

16:09 <blackboxsw> * Fix openSUSE and SLES setup of /etc/hosts (Robert Schweikert) (LP: #1731022)

-

16:09 <blackboxsw> * Catch UrlError when #include'ing URLs (Andrew Jorgensen)

-

16:09 <ubot5> Launchpad bug 1722564 in Apport "apport question will not accept multi-character responses" [Undecided,Confirmed] https://launchpad.net/bugs/1722564

-

16:09 <ubot5> Launchpad bug 1730135 in openstack-dev-sandbox ""Too much rain in Sydney"" [Undecided,New] https://launchpad.net/bugs/1730135

-

16:09 <ubot5> Launchpad bug 1731022 in cloud-init "host template expansion does not work on SUSE distros" [High,Fix committed] https://launchpad.net/bugs/1731022

-

16:09 <smoser> ajorg replied with a request for https://code.launchpad.net/~ajorgens/cloud-init/+git/cloud-init/+merge/329657

-

16:09 <smoser> that fell on deaf ears

-

16:09 <blackboxsw> * Released stable release update (SRU) of 17.1-27-geb292c18 (LP: #1721847)

-

16:09 <blackboxsw> * Cleanup dhclient background process after EC2 network discovery.

-

16:09 <blackboxsw> * ntp: fix configuration template rendering for openSUSE and SLES (Robert Schweikert) LP: #1726572

-

16:09 <blackboxsw> * fix manually running cloud-init after upgrade (LP: #1732917)

-

16:09 <ubot5> Launchpad bug 1721847 in cloud-init (Ubuntu Artful) "sru cloud-init 2017-10-06 (17.1-18-gd4f70470-0ubuntu1) updated to (17.1-27-geb292c18)" [Medium,Fix released] https://launchpad.net/bugs/1721847

-

16:09 <ubot5> Launchpad bug 1726572 in cloud-init "ntp config handling inconsistent for SLES and openSUSE" [Medium,Fix committed] https://launchpad.net/bugs/1726572

-

16:09 <ubot5> Launchpad bug 1732917 in cloud-init "17.1 update breaks EC2 nodes" [High,Fix committed] https://launchpad.net/bugs/1732917

-

16:09 <ajorg> truth

-

16:09 <smoser> ajorg: i will review shortly

-

16:09 <blackboxsw> * Queued upstream for merge into Bionic

-

16:09 <blackboxsw> * Queued 17.1.46 SRU for Xenial, Zesty, and Artful

-

16:09 <blackboxsw> * Fix EC2 race on sandboxed dhclient's pidfile during tempdir teardown (LP: #1735331)

-

16:09 <blackboxsw> * Enable Bionic in Integration Tests

-

16:09 <blackboxsw> * Create LXD and KVM Integration Tests in Jenkins

-

16:09 <ubot5> Launchpad bug 1735331 in cloud-init "ec2: zesty tempfile sandbox dhclient.pid file can't be created" [High,Fix committed] https://launchpad.net/bugs/1735331

-

16:10 <blackboxsw> As of end of last week, we are trying to blitz the review queue and dust off anything that has been sitting too long

-

16:12 <blackboxsw> So a couple fixes went into Amazon's initial network setup, IPv6 support is live for Ubuntu series Xenial, Zesty, Artful and Bionic

-

16:13 <ajorg> cool

-

16:14 <blackboxsw> heh I blew that last topic. it should have been #topic Recent Changes.

-

16:14 <blackboxsw> anyway I'll fix it in the logs when I publish

-

16:15 <blackboxsw> As always , for historical docs from this meeting check this link

-

16:15 <blackboxsw> #link http://cloud-init.github.io

-

16:15 <blackboxsw> #topic In-progress Development

-

16:15 <blackboxsw> So we have an active queue that is pretty healthy still

-

16:15 <blackboxsw> #link http://bit.ly/ci-reviews

-

16:16 <blackboxsw> smoser: rharper are we still trying to get through that queue as best we can for 17.2 or when do we think the window closes there?

-

16:16 <smoser> i think we can spend some more time on queue today.

-

16:16 <smoser> but that is about it really.

-

16:16 <blackboxsw> yeah, want some settle 'bake' time before the 17.2 cut on Thursday

-

16:17 <blackboxsw> We saw a couple Azure branches come in late last week.... Are there any branches folks are really excited about landing this week (today tomorrow?)

-

16:18 <blackboxsw> I had hoped to get through a couple of Robert's as they don't seem very contentious.

-

16:19 <smoser> the reporter bit seems pretty reasonable

-

16:19 <smoser> other than its not actually used anywhere in the mp

-

16:19 <smoser> ie, its non-contentious to add a reporter, but adding code that is not used is of not a lot of use :)

-

16:19 <blackboxsw> true

-

16:20 <ajorg> which mp is being discussed?

-

16:20 <smoser> (https://code.launchpad.net/~paul-meyer/cloud-init/+git/cloud-init/+merge/334989)

-

16:20 <blackboxsw> #link https://code.launchpad.net/~paul-meyer/cloud-init/+git/cloud-init/+merge/334989

-

16:21 <ajorg> thanks

-

16:23 <blackboxsw> With the upcoming holidays I expect things will be pretty slow after mid-next week, so we won't likely be landing a lot before the first of the new year.

-

16:25 <robjo> If it's slow for you more time to review open merge proposals ;)

-

16:25 <blackboxsw> This week we are also trying to get an SRU into ubuntu xenial, zesty and artful for some VMware/OVF datasource fixes for ds-identify and for pre-cusomization marker files courtesty (smoser & maitriyee)

-

16:26 <blackboxsw> courtesy rather

-

16:26 <smoser> ajorg: you could ping matthew on https://code.launchpad.net/~yeazelm/cloud-init/+git/cloud-init/+merge/331897

-

16:27 <ajorg> yup

-

16:27 <blackboxsw> and I know powersj is working on EC2 integration test support for cloud-init

-

16:27 <powersj> yep!

-

16:27 <powersj> Hoping to have an initial MP up this week

-

16:27 <blackboxsw> it's gonna be excellent to automatically test these releases

-

16:28 <blackboxsw> powersj: rharper smoser anything else in progress?

-

16:28 <rharper> nothing here

-

16:28 <ajorg> oh very nice.

-

16:28 <dpb1> powersj: \o/

-

16:28 <smoser> just the things that are in teh review queue. i put up one this morning for tmp file leakage

-

16:28 <smoser> https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/335034

-

16:29 <smoser> i think the yeazelm mp probably is just missing somethign simple bug haven't spent any time on it.

-

16:29 <blackboxsw> ahh also we landed the initial /run/cloud-init/instance-data.json which we had talked about with larsks. It captures all metadata and userdata and some standardized properties which could help people script instance data.

-

16:29 <smoser> yeah, that is neat.

-

16:30 <blackboxsw> Yeah, we have yet to write up docs on using it (and we have an inprogress branch to allow using jinja templates in #cloud-config modules). But I don't expect this to land by 17.2

-

16:31 <ajorg> did we? that's great!

-

16:32 <blackboxsw> yeah only basic standardized properties currently. + 'local-hostname': self.get_hostname(),

-

16:32 <blackboxsw> 592 + 'instance-id': self.get_instance_id(),

-

16:32 <blackboxsw> 593 + 'cloud-name': self.cloud_name,

-

16:32 <blackboxsw> 594 + 'region': self.region,

-

16:32 <blackboxsw> 595 + 'availability-zone': self.availability_zone}}

-

16:32 <robjo> is that basically a re-implementation of python-ec2metadata? https://github.com/SUSE/Enceladus/tree/master/ec2utils/ec2metadata

-

16:32 <blackboxsw> but it's a first pass. We expect to add more

-

16:33 <blackboxsw> robjo: kindof, though generalized for all datasources

-

16:34 <rharper> robjo: long term, it's expected to be more than just ec2; rather a common baseline of instance metadata independent the actual cloud, but , IIRC, having a cloud-specific area (or at least access to the raw data)

-

16:34 <blackboxsw> it leaves a json-foramatted file containing any vendor data and user-data plus generalized/standardized fields extracted from that content which can be expected on all clouds

-

16:35 <robjo> problem with "all" clouds is that Azure is very different

-

16:35 <blackboxsw> since each datasource has that data already, it's essentially just formating it in a consumable file that others could levereage

-

16:35 <robjo> although one can argue that a "name" is an id it still looks weird when 'instance-id' and is a name

-

16:36 <blackboxsw> agreed robjo, some datasources may not provide different/less content.

-

16:36 <smoser> ajorg: http://paste.ubuntu.com/26164503/

-

16:36 <ajorg> Is that one of the Azure differences? name vs. instance-id?

-

16:36 <smoser> thats a demo of instance-data.json

-

16:36 <robjo> yes, azure has names no numbers

-

16:37 <robjo> it's more about "user expectations" as a "name" is an "identifier"

-

16:37 <blackboxsw> I'll check that azure run now. I think I linked it to the branch originally

-

16:37 <blackboxsw> ok I think it's probably a good to transition to open office hours now for the next 30 mins

-

16:38 <smoser> what is 'name' versus 'instance-id' comment ?

-

16:38 <smoser> ajorg: ?

-

16:38 <blackboxsw> #topic Office Hours (for next 30 mins)

-

16:38 <blackboxsw> feel free to continue the discussion now

-

16:38 <robjo> I'd just caution of making the assumption that we can stick the information from that data sources straight into another format and then call it "generic instance information"

-

16:38 <ajorg> smoser: re robjo's comment about "Azure is very different"

-

16:39 <smoser> oh. yes. ok.

-

16:39 <blackboxsw> azure instance-data

-

16:39 <blackboxsw> #link http://pastebin.ubuntu.com/26075842/

-

16:39 <dpb1> smoser: standup

-

16:39 <smoser> yeah, they do have a 'id'

-

16:40 <blackboxsw> #link http://paste.ubuntu.com/26164503/

-

16:40 <ajorg> from DMI?

-

16:40 <robjo> Which is useless in any any command

-

16:40 <smoser> from the cd i think.

-

16:41 <ajorg> robjo: ah, so the ID is unique (is it?) but can't be used to call any Azure APIs?

-

16:41 <robjo> in EC2 the instance-id is useful to me if I want to run "aws" commands, but the instance ID shown in the pastebin is useless for any "az" command

-

16:41 <robjo> ajorg: correct

-

16:41 <robjo> in the "az" tools everything is a name

-

16:42 <robjo> and thus to make the data cloud-init produces useful the -id should be the name of the VM

-

16:42 <robjo> then I can parse that information and use it if I need to deal with the API

-

16:43 <smoser> hm.

-

16:43 <robjo> but providing that ID as its is basically just sticking information into the json to "fill a field" which is somewhat counter to the point I'd say

-

16:43 <ajorg> robjo: there's a uniqueness constraint on the name too? but per-account or at-a-time or what?

-

16:43 <smoser> i odnt knwo. although it is insteresting thought.

-

16:43 <smoser> the issue is 'instance-id' is supposed to be an instance id

-

16:43 <smoser> not a user provided name that can be provided mutliple times in a row.

-

16:44 <smoser> i realize name is per-group unique, but if i

-

16:44 <smoser> a.) launch

-

16:44 <smoser> a.) launch 'foobar'

-

16:44 <robjo> There is a uniqueness constraint in that one cannot run a VM with the same "name" in the same resource group

-

16:44 <ajorg> so the question is if that ID provides global uniqueness, or if it provides a reference to the instance to be used via APIs

-

16:44 <smoser> b.) create capture

-

16:44 <smoser> c.) delete foobar

-

16:44 <smoser> d.) launch foobar

-

16:44 <smoser> then 'd' wont look new

-

16:45 <robjo> yes, it will it just takes a long time in Azure until the backend reaches "eventual" consistency and knows "foorbar" has been deleted previously

-

16:45 <ajorg> It seems clear enough that cloud-init is looking for a unique ID

-

16:45 <ajorg> But a user might want either, and probably an ID for API use.

-

16:47 <robjo> Well if we provide a format of the data that is exposed to the user via documentation and expected to be used by the user than at that point, IMHO, user needs have higher priority than what cloud-init is looking for

-

16:47 <ajorg> To decide which APIs to use, a script has to first look at which cloud it's on, so it has a chance to decide which value to use.

-

16:47 <robjo> that cloud-init uses the id to make decisions about "pre-once", "per-always" is a different topic

-

16:49 <robjo> Well that then kind of defeats the "generic instance information" claim, IMHO

-

16:49 <robjo> you are basically saying 1.) look for the framework and then decide if on that framework the "generic instance information" is useful or not

-

16:50 <robjo> 2.) If you happen to be on a platform where the "generic instance information" is not useful, go and collect your own

-

16:50 <robjo> From a user perspective that is not very nice, IMHO

-

16:51 <ajorg> oh, I was presuming we'd also include the Azure name, not that we'd include only a useless instance-id in that case.

-

16:51 <ajorg> clouds that don't have a name, wouldn't include a value for it.

-

16:52 <robjo> the pastebin only has the ID

-

16:52 <ajorg> right, I'm saying we should add the name

-

16:53 <robjo> This is why I am pointing out that "generic instance information" is not necessarily so easy to come by

-

16:54 <blackboxsw> robjo: ultimately, I'd like the generalized content surfaced in instance-data.json to be something that external user's could get value from and script against. This first pass was a stripped down approach to some of that content.

-

16:54 <smoser> we could add 'name' and have it be none yes.

-

16:55 <smoser> the not-yet-written doc will state that consumers should not be confused by new field names.

-

16:55 <blackboxsw> There are some fixes that need to be proposed to all datasources to better standardize on things like public vs private addresses, external hostnames etc. Those I expect will come in subsequent passes.

-

16:55 <robjo> it might be worth considering the concept of "equivalent instance information" where the entries in the json files get names/keys that are generic across all cloud frameworks and provide the euivalent information/usefulness to the user

-

16:55 <smoser> but inside the 'v1', then content of a key will not change.

-

16:55 <ajorg> robjo: that's a fair point, imho

-

16:55 <smoser> but 'instance-id' is in fact 'instance-id'. not 'name'.

-

16:55 <blackboxsw> robjo: I think that is the intent of those 'v1' standardized fields.

-

16:56 <smoser> note that lxd shares the same generic problem in this regard as azure. it uses user-provided name for instance-id. but does not provide an actual instance id of any sort.

-

16:56 <blackboxsw> right per name/instance-id discussion, they feel separate, and I think there is value in adding a separate 'name' as smoser mentioned

-

16:58 <robjo> Lets look at it from an API perspective, if I were to use the .json file wouldn't it be nice if I could just say json.load().get{'instance_api_id')

-

16:58 <robjo> for EC2 that returns the instance-id, for Azure it gives me the name

-

16:59 <robjo> part of the idea of cloud-init is to keep the ugly details of the cloud framework away from the user

-

16:59 <ajorg> if we were talking about the value of "region" we'd certainly want to yield the value that's useful for API calls.

-

17:00 <robjo> so why would the .json data then retrieve from that idea and make the user know if I am in EC2 I need to use instance-id and if I am in Azure I need to use instance-name?

-

17:01 <robjo> ajorg: agreed

-

17:01 <smoser> it seems somewhat non-sense that azure gives an instance a unique id, but cannot take that in as an identifier to the instance.

-

17:02 <robjo> AWS, GCE, and Azure all have the concept of "region" , not certain how IBM is handling that part in their setup but that may not be of interest to us at this point

-

17:02 <smoser> your point is good though. but instance-id i really think needs to be a unique identifier (as much as possible) for this instance

-

17:02 <ajorg> It sounded like smoser's 'v1' comment was meant to imply we could have a 'v2' that yields data differently than 'v1'.

-

17:02 <smoser> softlayer has "datacenters"

-

17:03 <robjo> smoser: I agree, but that's the way it is

-

17:03 <smoser> at some point, ajorg we will of course realize that we're all idiots

-

17:03 <smoser> and wonder What were we thinking!

-

17:03 <smoser> and have a 'v2'

-

17:04 <blackboxsw> `<-- it takes some of us longer than others to realize that

-

17:05 <ajorg> smoser: you're not convinced that today is that day?

-

17:05 <smoser> i try to keep acknowledgement of that fact to be more than a few days later

-

17:06 <ajorg> good to let it sink in first :-)

-

17:06 <smoser> (compared to when i notice it, to allow for additional occurences)

-

17:06 <ajorg> I'm not going to say it has to be changed, but I do think at the very least the azure name should be available.

-

17:07 <blackboxsw> I think this discussion definitely sheds light on the fact that we should continue to bring these standardized instance-data discussions to this meeting for a quick feedback loop from you guys as it evolves :)

-

17:07 <ajorg> :)

-

17:08 <blackboxsw> #action blackboxsw bring up any updates in instance-data.json fields for discussion about common use-cases/patterns

-

17:08 * meetingology blackboxsw bring up any updates in instance-data.json fields for discussion about common use-cases/patterns

-

17:08 <ajorg> and it doesn't seem harmful to have the name only if the cloud provides one, just as if the cloud doesn't have a concept of an availability zone we'll skip that too.

-

17:09 <blackboxsw> +1

-

17:10 <blackboxsw> well i think this about wraps up our meeting for today

-

17:10 <blackboxsw> any other topics for today?

-

17:11 <ajorg> I pinged Matt Yeazel, but he didn't respond yet.

-

17:11 <smoser> i think 'api-id' would lmake sense as a name.

-

17:11 <ajorg> so nothing more from my end

-

17:11 <ajorg> smoser: or 'api-instance-id'

-

17:12 <smoser> that just seems confusing.

-

17:12 <smoser> hm..

-

17:12 <smoser> i see why you want the 'instance' portion there, but the thing i dont like is that implies that this is 'per instance'

-

17:12 <ajorg> well, it's an API instance identifier.

-

17:13 <smoser> which in fact it is not.

-

17:13 <smoser> hm.

-

17:13 <ajorg> Ah, okay, that's true, but if the cloud doesn't have a unique way to identify the instance to the API...

-

17:13 <smoser> yeah

-

17:14 <ajorg> someone should check that assumption... how do you refer to terminated instances? or how are they identified in logs?

-

17:16 <ajorg> smoser: I just worry that someone's going to say "but in my API an API ID is this other thing"

-

17:17 <blackboxsw> yeah before surfacing something like that we'd need to vet it

-

17:17 <ajorg> In general I think there are enough differences between clouds that it's probably a losing battle to try to come up with something that's one-size-fits-all.

-

17:17 <ajorg> The goal was to make the information available more readily than by calling out to metadata services, right?

-

17:18 <ajorg> It's much harder to implement meta-data pulling for every cloud than to implement some logic that pulls the right value out of a JSON object, so it's still a big improvement even if it can't provide a unified view.

-

17:21 <ajorg> anywho, I should go do other things.

-

17:21 <blackboxsw> ajorg: yes that is the primary goal: more easily access cloud-provided metadata

-

17:21 <blackboxsw> if there is low-hanging fruit we can standardize I'm +1 on the concept

-

17:22 <blackboxsw> that's where the standard 'v1' key came from

-

17:22 <blackboxsw> but yeah I also don't think cloud-init needs to boil the ocean and standardize all fields

-

17:22 <blackboxsw> we'll capture what low-hanging fruit we can

-

17:22 <blackboxsw> and it'll take time

-

17:22 <blackboxsw> ok. Thanks for the great discusssions/suggestions ajorg and robjo. keep 'em coming

-

17:22 <blackboxsw> think I'll end meeting now

-

17:22 <blackboxsw> until next time...

-

17:22 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2018-01-08.html b/status-2018-01-08.html deleted file mode 100644 index 2192bf6..0000000 --- a/status-2018-01-08.html +++ /dev/null @@ -1,382 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Mon 08 January 2018 in status-meeting-minutes - - • 11 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

Recent changes

-

The discussion about "Recent changes" started at 16:04.

- -

In-progress Development

-

The discussion about "In-progress Development" started at 16:22.

- -

Office Hours (next 30 minutes)

-

The discussion about "Office Hours (next 30 minutes)" started at 16:46.

- -

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (99)
  • -
  • ajorg (45)
  • -
  • smoser (19)
  • -
  • rharper (9)
  • -
  • robjo (5)
  • -
  • powersj (4)
  • -
  • meetingology (3)
  • -
  • smoser1 (2)
  • -
  • ubot5 (1)
  • -
-

Full Log

-

16:03 <blackboxsw> #startmeeting Cloud-inin bi-weekly status meeting

-

16:03 <meetingology> Meeting started Mon Jan 8 16:03:53 2018 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:03 <meetingology>

-

16:03 <meetingology> Available commands: action commands idea info link nick

-

16:04 <blackboxsw> Happy 2018 cloud-initers! Thanks ajorg for helping kick us off.

-

16:04 <blackboxsw> Welcome back from break hope the holidays were good for folks.

-

16:09 <blackboxsw> #topic Recent changes

-

16:04 <blackboxsw> It

-

16:05 <blackboxsw> It's been a while since we've held the meeting due to holidays and vacation time. So, not a ton of content to report for the last bit. Digging up those details now

-

16:06 <blackboxsw> Testing of 17.2 on EC2, Azure, and GCE and release to Ubuntu Bionic

-

16:06 <blackboxsw> Complete 17.1.46 SRU to Ubuntu Xenial, Zesty, and Artful

-

16:06 <blackboxsw> Fix documentation around 'init' mode for modules subcommand (LP: #1736600)

-

16:06 <blackboxsw> Tooling to merge community authored branches into master

-

16:06 <ubot5> Launchpad bug 1736600 in cloud-init "CLI: cloud-init modules -h documents unsupported --mode init" [Low,Fix committed] https://launchpad.net/bugs/1736600

-

16:07 <blackboxsw> So the canonical side of the team worked a bit on getting the latest SRU updates 17.1.46 into Xenial, Zesty and artful. The testing and verification of that release took a bit of time, but we are getting better(faster)

-

16:07 <blackboxsw> I think this last SRU only took us 2 weeks instead of 4 weeks. so that frees up more time on upstream reviews and increasing cloud-init's velocity

-

16:07 <ajorg> great

-

16:08 <blackboxsw> we also added team tools for streamlining community authored branches. so that we stop slowing folks down :/

-

16:08 <blackboxsw> then the only problem is the reviewer :)

-

16:10 <blackboxsw> Also 17.2 release was 'cut' prior to Christmas break, this opened master up for more changes to land. so we've pulled in good fixes for VMWare NoCloud and SLES

-

16:11 <blackboxsw> digging up the changests now.

-

16:11 <blackboxsw> Also, keep in touch with our active development and the "done" lane on trello. It's out bookkeeper for anything we are working and Done represents anything landed

-

16:11 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:13 <blackboxsw> so high-level content that landed between 17.1.46 and 17.2:

-

16:14 <blackboxsw> * CLI added the clean and status subcommands

-

16:14 <blackboxsw> * Support for identifying OVF datasource provided by VMware

-

16:14 <blackboxsw> * NoCloudKVM tests now run in continuous integration

-

16:14 <blackboxsw> * Formalize DataSource get_data and related properties

-

16:14 <blackboxsw> * Remove prettytable dependency and introduce simpletable

-

16:14 <blackboxsw> * VMWare pre and post-customization script support

-

16:15 <blackboxsw> Thanks ajorg I think you were the author of note on simpletable stuff, it's nice to drop dependencies where we can to increase speed of cloud-init

-

16:15 <ajorg> it was done selfishly

-

16:15 <ajorg> we dislike taking on new dependencies :-)

-

16:17 <blackboxsw> and thanks to robjo(suse) maitree(vmware) too and dojordan and Ryan McCabe(redhat) for recent branches too

-

16:17 <blackboxsw> :)

-

16:18 <blackboxsw> Post our 17.2 release we've started work on improved integration..... I think we just got powersj's ec2 integration tests landed right johs?

-

16:18 <blackboxsw> josh even

-

16:18 <powersj> \o/ yep!

-

16:18 <ajorg> nice

-

16:19 <blackboxsw> sweet, so an extra security blanked for us when we have significant changesets landed in master to ensure ec2 is happy.

-

16:19 <blackboxsw> powersj: what are out plans for continuous integration frequency

-

16:19 <blackboxsw> with ec2 specifically

-

16:19 <ajorg> Can those integration tests be run by others with EC2 accounts?

-

16:19 <blackboxsw> ajorg: yes they can

-

16:19 <powersj> I am working on the jenkins jobs this week and hope to have a weekly run as well as a manual run for backport testing

-

16:19 <blackboxsw> I'll get the cmdline

-

16:19 <ajorg> thanks!

-

16:20 <blackboxsw> tox -e citests -m tests.cloud_tests run --os-name=artful --platform=ec2 --preserve-data --data-dir=../results --verbose

-

16:20 <blackboxsw> or something like that

-

16:20 <ajorg> got it

-

16:20 <ajorg> thanks!

-

16:20 <blackboxsw> powersj: documented it too I think

-

16:20 <blackboxsw> getting link

-

16:20 <powersj> https://cloudinit.readthedocs.io/en/latest/topics/tests.html#ec2

-

16:20 <blackboxsw> #link https://cloudinit.readthedocs.io/en/latest/topics/tests.html#ec2

-

16:20 <blackboxsw> :)

-

16:21 <blackboxsw> excellent work Josh

-

16:21 <powersj> thanks for all the reviews :)

-

16:21 <blackboxsw> anything else I'm missing about landed work? rharper powersj smoser1 ?

-

16:22 <blackboxsw> otherwise next topic

-

16:22 <rharper> blackboxsw: nothing from me

-

16:22 <blackboxsw> #topic In-progress Development

-

16:23 <blackboxsw> So we've got a fairly healthy review queue that we need to get through as we get the year started....

-

16:24 <blackboxsw> we also have a few things we are in flight currently:

-

16:24 <blackboxsw> - continuous integration improvements per powersj

-

16:24 <blackboxsw> - dropping dependence on ifup ifdown utils where possible as that's not supported (or installed in some cases) in systemd world

-

16:24 <smoser1> blackboxsw: wow. sorry, missing.

-

16:25 <blackboxsw> who is that smoser1 guy anyway

-

16:25 <smoser1> yeah, i didnt see anything missing sorry.

-

16:25 <smoser> wonder how that happened.

-

16:25 <blackboxsw> welcome ;)

-

16:25 <blackboxsw> - netplan improvements per rharper and jinja template support for all cloud-config modules

-

16:26 <blackboxsw> - and softlayer support per smoser

-

16:27 <blackboxsw> know the Azure guys are also posting a couple branches on getting a pre-provisioning setup going for thier datasource which looks pretty exciting

-

16:27 <blackboxsw> I can't think of anything else off the top of my head.

-

16:28 <robjo> chrony support

-

16:28 <ajorg> we're only talking feature work in this topic?

-

16:29 <blackboxsw> any in progress development to highlight is fair game. bug work. refactoring, feature etc

-

16:29 <blackboxsw> +10 robjo and again thanks for working with us getting all those branches up and (hopefully soon) landed

-

16:29 <ajorg> what does "jinja template support for all cloud-config modules" mean?

-

16:31 <ajorg> I'd guess most modules don't need templating?

-

16:31 <blackboxsw> ajorg: two things. 1. since we have now landed /run/cloud-instance/instance-data.json to store metadata/userdata it'd be that #cloud-config can new be specified with ## template:jinja header and could leverage anything jinjia has to offer plus sourcing any of the instance-data.json metadata fields

-

16:33 <ajorg> Ah, right. Is that not being done above the module level?

-

16:33 <blackboxsw> so if people have repetitive or template-driven content in the runcmd or write_files portion or their #cloud-config they'd be able to leverage jinja templates etc

-

16:33 <smoser> ajorg: yes, above the module level.

-

16:33 <blackboxsw> ajorg: not anywhere in cloud-config currently

-

16:33 <blackboxsw> one sec I misunderstood the question

-

16:33 <blackboxsw> smoser: can you clarify what you mean?

-

16:33 <ajorg> I mean, shouldn't #cloud-config template expansion happen before the module sees the config?

-

16:34 <smoser> blackboxsw: we could/should also allow other part types to be rendered

-

16:34 <smoser> ttps://trello.com/c/xyqxyOxg

-

16:35 <smoser> er... bad url. in 2 ways

-

16:35 <ajorg> The the part handler would be the one to do that expansion.

-

16:35 <smoser> https://trello.com/c/AYaCdQyT

-

16:35 <blackboxsw> ahh ok, right that makes sense. I think the cut I made was limited in focus to cloud-config modules and custom scripts supporting the ## template:jinja header.. but nothing would preclude handling other parts

-

16:36 <blackboxsw> so the link to my WIP branch was

-

16:36 <blackboxsw> #link https://trello.com/c/xyqxyOxg

-

16:36 <blackboxsw> and the general feature per smoser

-

16:36 <blackboxsw> #link https://trello.com/c/AYaCdQyT/21-cloud-init-query-standardized-json-information

-

16:36 <ajorg> Is there a design doc of some kind of this?

-

16:37 <blackboxsw> not yet.. but we probably should have a spec as it'd be a good template for the docs we'll need to write

-

16:38 <blackboxsw> scott captured most of the use cases we'd be going for in that last trello link above

-

16:38 <ajorg> Small example of where some clarity is needed: if Jinja is interpreting {foo} in a user-script, what will it do when it sees a shell variable ${foo}

-

16:38 <ajorg> ?

-

16:39 <smoser> you declare that the content is a jinja template

-

16:39 <smoser> if you provide it something that is not renderable as a jinja template

-

16:39 <smoser> then it will fail

-

16:39 <smoser> it requires input to explicitly say "this is jinja". it does not just attempt to render anything.

-

16:39 <smoser> (unless explicitly told to)

-

16:39 <blackboxsw> some brief working examples are in the description of the branch @ https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/334030

-

16:40 <ajorg> Sure. But as a content author, I need to know if Jinja is going to try to render ${foo} or not.

-

16:40 <smoser> then as a content author you can read jinja docs :)

-

16:40 <blackboxsw> jinja would try to render {{ foo }}

-

16:40 <ajorg> :-

-

16:41 <smoser> ajorg: we'll document a simple case, and we can even document "for shell, you'll have to be aware that ...."

-

16:41 <smoser> but we're not going to document all of jinja

-

16:41 <ajorg> I see.

-

16:42 <ajorg> My understanding was that Jinja was highly customizable in what it interpreted and how, so that it's important to document how you've configured it to work.

-

16:42 <blackboxsw> and since to burden is on the #cloud-config or script writer to provide the header ## template: jinja\n#cloud-config\n they should understand what they are doing

-

16:42 <blackboxsw> we won't implicitly run the #cloud-config through jinja

-

16:43 <ajorg> I get that, no problem, what I'm saying is that Jinja is an engine that you configure to do something, not a markup that always does the same thing for everyone.

-

16:43 <ajorg> Am I making any sense?

-

16:44 <blackboxsw> understood (though I thought it was fairly constrained it it's application and functionality). We'll make sure that the mechanism by which jinja operates is well documented and confined as best we can... for our own sanity we don't want that template engine to be too flexible... too many tough support use cases

-

16:45 <blackboxsw> ok anything else for "In progress development" otherwise we can move to Office hours for 30 mins

-

16:46 <blackboxsw> #topic Office Hours (next 30 minutes)

-

16:47 <blackboxsw> robjo: you've got quite a few branches of goodness up for us to review. Any prioritization on those branches or just take them as we can?

-

16:47 <rharper> I don't think there are issues w.r.t jinja and shell; they use different variable escape methods, jinja uses {{ variable/expression }}; and it doesn't consume $ AFAIK, ajorg do you know differently ?

-

16:48 <blackboxsw> #link https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/334992

-

16:48 <blackboxsw> I'm guessing is top of the list

-

16:48 <ajorg> I saw {instance_id} at https://trello.com/c/AYaCdQyT/21-cloud-init-query-standardized-json-information so I assumed it was being customized to look for { instead of {{

-

16:48 <robjo> blackboxsw: The chrony support should probably be the last as it will take longer over all and more back and forth

-

16:48 <ajorg> (for one thing)

-

16:49 <ajorg> rharper: also, there's the whole question of the "extends" feature

-

16:50 <ajorg> We integrated Jinja into an internal tool a few years back and we spent a very long time making sure the loaders did the right thing.

-

16:50 <blackboxsw> ajorg: I thought I read somewhere that you couldn't exend jinja for custom functions. maybe I was mistaken

-

16:50 <robjo> I am also not certain that the "re-write everything" on the first go around for chrony is really what we want to do initially

-

16:50 <ajorg> blackboxsw: I don't think I'm referring to custom functions

-

16:51 <robjo> That's probably where we ant to end up, but I am not certain that a "step function" approach is in order

-

16:51 <rharper> ajorg: hrm, I've always seen {{ variable }} or {% expression %}; so maybe blackboxsw can just update the templates;

-

16:51 <rharper> the examples in the cards

-

16:52 <ajorg> rharper: sure, that would have helped in this case.

-

16:52 <robjo> If we do go down the route of the step function I'll need more gudance then in rharper's comments

-

16:52 <ajorg> blackboxsw: I was referring to the ability of one template to extend another.

-

16:53 <ajorg> blackboxsw: and the question of where does the engine look when it's asked to extend another template. It can be tricky.

-

16:54 <blackboxsw> yeah I honestly hadn't gotten past step one of handling the template markup within an existing single template. so this may need a bit of thought/work

-

16:55 <ajorg> Personally, I'd be a lot happier with limiting things to Python format() templates, even though it means you can't have loops, but I won't get in the way as long as we're cognizant of the problems we can run into by accepting the full power of an advanced engine like Jinja.

-

16:56 <smoser> i'm not opposed to allowing ## template: python-format

-

16:56 <ajorg> heh

-

16:56 <smoser> honestly.

-

16:56 <smoser> you can pick a differnt name if you dont like that one.

-

16:57 <smoser> but we already use jinja, so it makes sense to support jinja

-

16:57 * smoser has to run. sorry.

-

16:57 <rharper> I do feel that supplying the template means the user is opting in; and specifically if we've got a good way to provide dry-run based on a instance.json and a script; that certainly can help folks work out the kinks in the template of their choosing

-

16:57 <ajorg> I'm really not opposed so much as wary of the extensive power of the thing

-

16:58 <rharper> ajorg: that's a fair warning; given you've experience here; help drawing the line is most welcome

-

16:58 <ajorg> I'm trying to think of a way to read in /etc/shadow using Jinja, you know?

-

16:58 <rharper> well, cloud-init is root anyhow; so, what's the deal with that ?

-

16:59 <blackboxsw> ajorg: heh, right though you can read that with your runcmd section in #cloud-config :)

-

16:59 <ajorg> If I can come up with a way to do it that doesn't make it look obvious that I'm doing it, and then post that as something others can copy, or use with #include <url> then I win.

-

16:59 <rharper> I don't think jinja makes that any more troublesome

-

17:00 <rharper> folks already wget | bash with shell they don't understand either

-

17:00 <ajorg> I suspect Jijna makes it more opaque.

-

17:01 <ajorg> The answer to "what file does Jinja read when I use {% extends foo %}" is a very lengthy "it depends"

-

17:02 <ajorg> anyway, I've said my piece

-

17:03 * ajorg is a bit of a template naysayer.

-

17:05 <blackboxsw> +1, there's one in every group. We'll try to keep that in mind as this feature evolves

-

17:05 <blackboxsw> :)

-

17:06 <ajorg> nice

-

17:06 <ajorg> :-)

-

17:06 <blackboxsw> any pet bugs, new features or burning reviews that need mention?

-

17:07 <blackboxsw> ajorg: we could do something simple like disable the extends option via policies

-

17:07 <blackboxsw> it looks like

-

17:08 <blackboxsw> #link http://jinja.pocoo.org/docs/2.10/api/#policies

-

17:08 <blackboxsw> or maybe I'm misunderstanding the issue I'll read up more on it

-

17:08 <ajorg> thanks

-

17:09 <ajorg> It looked like https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/334074 was blocking https://code.launchpad.net/~yeazelm/cloud-init/+git/cloud-init/+merge/331897 but shouldn't be anymore.

-

17:09 <ajorg> I'll remind Matt to try it again now.

-

17:13 <blackboxsw> thanks good dela

-

17:13 <blackboxsw> dela

-

17:13 <blackboxsw> deal

-

17:13 <blackboxsw> geez

-

17:14 <blackboxsw> on that note. I think it's time for coffee

-

17:14 <blackboxsw> and time to end the meeting

-

17:14 <blackboxsw> Happy New Year again folks. Good to be back in the office.

-

17:15 <blackboxsw> thanks again for the chat, until next time..

-

17:15 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2018-01-22.html b/status-2018-01-22.html deleted file mode 100644 index fd09a0b..0000000 --- a/status-2018-01-22.html +++ /dev/null @@ -1,335 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Mon 22 January 2018 in status-meeting-minutes - - • 8 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

Recent changes

-

The discussion about "Recent changes" started at 16:10.

- -

In-progress Development

-

The discussion about "In-progress Development" started at 16:24.

- -

Office Hours (next 30 minutes)

-

The discussion about "Office Hours (next 30 minutes)" started at 16:45.

- -

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (83)
  • -
  • smoser (23)
  • -
  • ajorg (16)
  • -
  • powersj (10)
  • -
  • ubot5 (6)
  • -
  • meetingology (3)
  • -
  • rharper (1)
  • -
-

Full Log

-

16:08 <blackboxsw> #startmeeting Cloud-init bi-weekly status meeting

-

16:08 <meetingology> Meeting started Mon Jan 22 16:08:22 2018 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:08 <meetingology>

-

16:08 <meetingology> Available commands: action commands idea info link nick

-

16:08 <blackboxsw> certianly ajorg :) (on office hours)

-

16:09 <blackboxsw> Welcome to another episode of cloud-init bi-weekly status. We'll chat about about cloud-init updates and in progress work, and we'l drop into office hours for ongoing discussions/bug work etc.

-

16:10 <blackboxsw> #topic Recent changes

-

16:11 <blackboxsw> Just walking through git-log for what we have committed in the last couple of weeks, here's the brief summary

-

16:12 <blackboxsw> thx smoser

-

16:12 <blackboxsw> - shorten the message in the exception per powersj feedback

-

16:12 <blackboxsw> - Use the same botocore session so the patched changes stick.

-

16:12 <blackboxsw> - fix bad use of %

-

16:12 <blackboxsw> - Fix console_log, improve comments and raise PlatformError on.

-

16:12 <blackboxsw> - tests: Fix EC2 Platform to return console output as bytes.

-

16:12 <blackboxsw> - tests: remove zesty as supported OS to test [Joshua Powers]

-

16:12 <blackboxsw> - Do not log warning on config files that represent None. (LP: #1742479)

-

16:12 <ubot5> Launchpad bug 1742479 in cloud-init (Ubuntu) "setting manual_cache_clean causes warning" [Medium,Fix released] https://launchpad.net/bugs/1742479

-

16:12 <blackboxsw> - tests: Use git hash pip dependency format for pylxd.

-

16:12 <blackboxsw> - tests: add integration requirements text file [Joshua Powers]

-

16:12 <blackboxsw> - MAAS: add check_instance_id based off oauth tokens. (LP: #1712680)

-

16:12 <blackboxsw> - tests: update apt sources list test [Joshua Powers]

-

16:12 <blackboxsw> - tests: clean up image properties [Joshua Powers]

-

16:12 <blackboxsw> - tests: rename test ssh keys to avoid appearance of leaking private keys.

-

16:12 <ubot5> Launchpad bug 1712680 in maas-images "cloud-init re-generates network config every reboot overwriting manual admin changes on CentOS." [Undecided,New] https://launchpad.net/bugs/1712680

-

16:12 <blackboxsw> [Joshua Powers]

-

16:12 <blackboxsw> - tests: Enable AWS EC2 Integration Testing [Joshua Powers]

-

16:12 <blackboxsw> - cli: cloud-init clean handles symlinks (LP: #1741093)

-

16:12 <ubot5> Launchpad bug 1741093 in cloud-init "cloud-init clean traceback on instance dir symlink" [Low,Fix committed] https://launchpad.net/bugs/1741093

-

16:13 <ajorg> What's being patched in botocore?

-

16:13 <blackboxsw> So a number of changes went into integration test related work, separating out requirements files.

-

16:14 <blackboxsw> MAASDatasource now also has smarted cache handling based on oauth token renewal from the maas server

-

16:14 <blackboxsw> so botocore is used by integration tests only as a mechanism to talk to the instance under test... looking back at the specifics here

-

16:14 <blackboxsw> it might have just been shuffling out how and where we define the dependency

-

16:14 <smoser> blackboxsw: (my 'paste' to you was bad... http://paste.ubuntu.com/26438113/ is better, showing only those on master, not my local branch that was currently checked out )

-

16:15 <blackboxsw> heh, oopsie daisy let's paste again inline then

-

16:15 <blackboxsw> - tests: remove zesty as supported OS to test [Joshua Powers]

-

16:15 <blackboxsw> - Do not log warning on config files that represent None. (LP: #1742479)

-

16:15 <blackboxsw> - tests: Use git hash pip dependency format for pylxd.

-

16:15 <blackboxsw> - tests: add integration requirements text file [Joshua Powers]

-

16:15 <blackboxsw> - MAAS: add check_instance_id based off oauth tokens. (LP: #1712680)

-

16:15 <blackboxsw> - tests: update apt sources list test [Joshua Powers]

-

16:15 <blackboxsw> - tests: clean up image properties [Joshua Powers]

-

16:15 <blackboxsw> - tests: rename test ssh keys to avoid appearance of leaking private keys.

-

16:15 <blackboxsw> [Joshua Powers]

-

16:15 <blackboxsw> - tests: Enable AWS EC2 Integration Testing [Joshua Powers]

-

16:15 <blackboxsw> - cli: cloud-init clean handles symlinks (LP: #1741093)

-

16:15 <ubot5> Launchpad bug 1742479 in cloud-init (Ubuntu) "setting manual_cache_clean causes warning" [Medium,Fix released] https://launchpad.net/bugs/1742479

-

16:15 <ubot5> Launchpad bug 1712680 in maas-images "cloud-init re-generates network config every reboot overwriting manual admin changes on CentOS." [Undecided,New] https://launchpad.net/bugs/1712680

-

16:15 <ubot5> Launchpad bug 1741093 in cloud-init "cloud-init clean traceback on instance dir symlink" [Low,Fix committed] https://launchpad.net/bugs/1741093

-

16:15 <blackboxsw> ok the real deal, that looks better

-

16:16 <blackboxsw> ahh ajorg that interim commit message on botocore was about integration tests caching the session information during testing so we don't recreate that session with every ssh connection to the instance

-

16:16 <blackboxsw> just a little time savings per review comments on powersj branch I believe

-

16:17 <ajorg> okay, so nothing that needs to get upstreamed to botocore?

-

16:17 <blackboxsw> I don't think so, powersj smoser I have vague recollection of someone filing an upstream botocore issue. did we have to do that for something else though?

-

16:18 <powersj> https://github.com/boto/botocore/issues/1351

-

16:18 <powersj> that was the issue smoser put in ^

-

16:18 <blackboxsw> nice recall powersj thanks.

-

16:18 <blackboxsw> #link https://github.com/boto/botocore/issues/1351

-

16:20 <smoser> ajorg: you can read that bug. imo they have a data loss error, but not one that they can easily fix without causing failures in places that previously ran fine.

-

16:20 <ajorg> I'll ask them to re-open it.

-

16:21 <ajorg> At the very least they should answer your last.

-

16:21 <smoser> thanks.

-

16:22 <blackboxsw> Generally anything significant that we have landed (and any inprogress work) should be available at the following link.

-

16:22 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:23 <blackboxsw> anything else we should note over the last couple weeks?

-

16:23 <blackboxsw> otherwise I'll switch to ongoing work topic

-

16:24 <blackboxsw> #topic In-progress Development

-

16:25 <blackboxsw> As you may have seen last week, we've gotten through a few passes and discussions around dojordan's branch to define pre-provisioning

-

16:25 <blackboxsw> #link https://code.launchpad.net/~dojordan/cloud-init/+git/cloud-init/+merge/334341

-

16:26 <blackboxsw> some of that discussion resulted in a new context manager: EphemeralDHCPv4 to support a sandboxed dhclient request on an instance.

-

16:27 <blackboxsw> this context manager affects Ec2 datasource a bit as it encapsulates all of the dhcp request ->` EphemeralIPV4Network calls that Ec2 was doing

-

16:28 <blackboxsw> there may be a couple other datasources that follow suit with this type of sandboxed dhcp request in weeks to come

-

16:28 <ajorg> glad it turned out to be generally useful rather than only specifically to ec2

-

16:28 <blackboxsw> absolutely

-

16:30 <blackboxsw> Some other in-progress bits look like we might try focusing a bit more on chrony support and gettting robjo's branches some more eyes.

-

16:31 <blackboxsw> and some work on Ubuntu snappy support per the snappy and snap config modules.

-

16:31 <smoser> dojordan: i just put one comment on your mp. /me thanks dojordan again for his patience.

-

16:32 <blackboxsw> rharper: smoser powersj anything more in the immediate pipeline that I'm missing/

-

16:32 <blackboxsw> ?

-

16:32 <smoser> blackboxsw: we should get the EphemeralDHCP thingy into the digital ocean datasource also.

-

16:32 <rharper> blackboxsw: a reply to the network discussion on the list from the azure folks and robjo

-

16:32 <ajorg> I took another look at https://code.launchpad.net/~yeazelm/cloud-init/+git/cloud-init/+merge/331897 and saw that origin/master seems to be failing some of the integration tests too.

-

16:32 <ajorg> (at least for me, locally, on a 16.04 instance)

-

16:32 <blackboxsw> ahhh right forgot about all your work there rharper, thanks!

-

16:33 <smoser> ajorg: https://jenkins.ubuntu.com/server/view/cloud-init/job/cloud-init-ci-nightly/

-

16:33 <smoser> that is nigytly run of trunk

-

16:33 <blackboxsw> #link https://jenkins.ubuntu.com/server/view/cloud-init/job/cloud-init-ci-nightly/

-

16:34 <ajorg> I'll try blackholing IMDS on my instance. Could be that's interfering with something.

-

16:35 <smoser> it is red, but 218 (green) and 219 (red) used the same git has on trunk (5cc0b19b8).

-

16:35 <ajorg> I'll follow up during office hours

-

16:36 <smoser> can you give me example of your failures ? we had "disk full" errors recently on our jenkins, so that might be the cause of the issue for 291.

-

16:36 <smoser> s/291/219/

-

16:36 <blackboxsw> I don't remember seeing that traceback recently. w/ warning messages present in cloud-init

-

16:36 <smoser> powersj: ? can you explain lxc timeout failure at

-

16:36 <smoser> https://jenkins.ubuntu.com/server/view/cloud-init/job/cloud-init-ci-nightly/219/consoleFull

-

16:37 <powersj> smoser: we discovered that our qemu-migration test was installing lxd from the archive and causing conflicts with the snap installed lxd

-

16:37 <powersj> I have a message to christian to prevent it, and I have already cleaned it up

-

16:37 <powersj> so new runs should pass

-

16:37 <ajorg> 2018-01-22 16:19:03,550 - tests.cloud_tests - WARNING - test case: modules/ssh_import_id failed TestSshImportId.test_no_stages_errors with: AssertionError: 1 != 0 : errors ['(\'ssh-import-id\', ProcessExecutionError("Unexpected error while running command.\nCommand: [\'sudo\', \'-Hu\', \'ubuntu\', \'ssh-import-id\', \'gh:powersj\', \'lp:smoser\']\nExit code: 1\nReason: -\nStdout: -\nStderr: -",))'] were encountered in stage m

-

16:38 <smoser> hm.. well, that will hit launchpad.net over https

-

16:38 <smoser> cloud-init-output.log probaly has more info (should be collected)

-

16:38 <powersj> the actual error is: File "/var/lib/jenkins/slaves/torkoal/workspace/cloud-init-ci-nightly/tests/cloud_tests/platforms/instances.py", line 142, in _wait_for_system

-

16:38 <powersj> raise OSError('timeout: after {}s system not started'.format(time))

-

16:38 <powersj> it is because when the qemu tests installed lxd it didn't initialize lxd networking

-

16:38 <powersj> so no IP is received

-

16:39 <smoser> ajorg: would you have had outbound access to launchpad https ? if not, then that'd be expected failure.

-

16:40 <smoser> oh, and i guess 'gh:powersj' (github)

-

16:40 <ajorg> smoser: I'll check some things, but in short yes. Maybe lxc is being weird?

-

16:40 <smoser> i dont like our user names in that test though...

-

16:40 <powersj> smoser: we could use the bot instead

-

16:42 <ajorg> smoser: it's a public ec2 instance with no special outbound rules, and I can connect to public https sites from a normal session.

-

16:44 <blackboxsw> hrm, ok let's chat about what we can do to anonymize or drop that type of test data if we can

-

16:44 <blackboxsw> probably time to kick over to office hours

-

16:45 <blackboxsw> #topic Office Hours (next 30 minutes)

-

16:45 <smoser> powersj: well, i think i'd prefer some public key that we state "no one has the private key for this."

-

16:46 <smoser> obviously we could lie about that, but one would expect that you and I would gain access to the system using our public keys.

-

16:46 <smoser> it doens't make me feel a lot better that a bot could/can.

-

16:47 <ajorg> Is there a way to limit integration testing to a specific test?

-

16:47 <blackboxsw> Feel free to bring up any topic/bugs/branches/features you'd like discussion on. We can also continue our discussion on the ssh key imports in teting

-

16:47 <ajorg> (takes a long time to run the full suite)

-

16:48 <blackboxsw> ajorg: yes

-

16:48 <blackboxsw> (reverse-i-search)`cloud_t': python3 -m tests.cloud_tests run --os-name=artful --platform=nocloud-kvm --preserve-data --data-dir=../results --verbose -t modules/locale -t modules/set_password

-

16:48 <ajorg> thanks, that should help

-

16:48 <blackboxsw> ajorg: you can specify the test names (like modules/set_password) and modules/locale in this test

-

16:48 <blackboxsw> yeah those are short ones I frequently test with

-

16:49 <smoser> http://paste.ubuntu.com/26438334/

-

16:49 <smoser> that is what i use. and yeah... we've discussed that integration test could be easier to run :)

-

16:49 <blackboxsw> #link http://paste.ubuntu.com/26438334/

-

16:49 <blackboxsw> nice 1

-

16:51 <blackboxsw> smoser: to have a public key we know nobody has a private key for would that mean we'd need a separate github account (or maybe just an additional key associated w/ our bot account in gh

-

16:51 * blackboxsw checks github for authorizing multiple keys.

-

16:51 <blackboxsw> hrm, that wouldn't work as we need gh:ubuntu-server-bot (one key) n/m

-

16:52 <ajorg> I've got meetings most of today, so I'll have to follow up later. thanks everyone!

-

16:52 <blackboxsw> thanks ajorg

-

16:59 <blackboxsw> so, bot account for the time being is better than powersj owning the testing world ;)

-

16:59 <blackboxsw> but I'm not too concerned about it as this are supposed to be throw away instances

-

16:59 <blackboxsw> but I'm not too concerned about it as there instances under test are supposed to be throw away instances

-

17:00 <blackboxsw> these instances.... anyway

-

17:04 <smoser> blackboxsw: right. it would require users on both those services .

-

17:14 <blackboxsw> alrighty. think we're at the close of office hours. Last call?

-

17:16 <blackboxsw> Thanks for your time and contributions to cloud-init folks!

-

17:16 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2018-02-16.html b/status-2018-02-16.html deleted file mode 100644 index 3e9ea33..0000000 --- a/status-2018-02-16.html +++ /dev/null @@ -1,322 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Fri 16 February 2018 in status-meeting-minutes - - • 7 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

Recent changes

-

The discussion about "Recent changes" started at 16:08.

- -

In-progress Development

-

The discussion about "In-progress Development" started at 16:18.

- -

cloud-init version 18.1 release (2/23/2018)

-

The discussion about "cloud-init version 18.1 release (2/23/2018)" started at 16:27.

- -

Office hours (next ~30 mins)

-

The discussion about "Office hours (next ~30 mins)" started at 16:42.

- -

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (64)
  • -
  • stanguturi (19)
  • -
  • smoser (17)
  • -
  • ubot5 (6)
  • -
  • meetingology (4)
  • -
  • powersj (3)
  • -
  • rharper (2)
  • -
  • nacc (1)
  • -
-

Full Log

-

16:04 <blackboxsw> hey folks thanks for joining in to another cloud-init biweekly status meeting

-

16:05 <blackboxsw> the early meeting day this week is to avoid hitting the upcoming US holiday on Monday

-

16:05 <blackboxsw> This meeting is probably going to be short, but we wanted to generate any discussion around the release we have scheduled for next week. I'll go through the following topics

-

16:05 <blackboxsw> recent changes, In-progress development, Release 18.1 Discussion, Office hours (30 mins)

-

16:05 <blackboxsw> Without further ado...

-

16:08 <blackboxsw> #startmeeting Cloud-init bi-weekly status meeting

-

16:08 <meetingology> Meeting started Fri Feb 16 16:08:08 2018 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:08 <meetingology>

-

16:08 <meetingology> Available commands: action commands idea info link nick

-

16:08 <blackboxsw> much better thanks nacc

-

16:08 <nacc> blackboxsw: yw

-

16:08 <blackboxsw> #topic Recent changes

-

16:08 <blackboxsw> Cloud-init upstream team has been working on an SRU for Artful and Xenial.

-

16:09 <blackboxsw> We discovered a couple of SRU-blocking bugs on EC2 as well as cloud-init subcommands so we've landed a couple of fixes there which are queued for SRU now

-

16:09 <blackboxsw> * cloud-init status --wait blocks until all stages complete (LP: #1747965)

-

16:09 <blackboxsw> * SRU EC2 upgrade path fix for 'systemctl restart cloud-init.service' (LP:1748354)

-

16:09 <blackboxsw> * Fix ds-identify nocloud detection with bind mounted writable/system-data directory (LP: #1747070)

-

16:09 <blackboxsw> * Tests: include missing unitests in python2.6 environments. Fix py2.6 incompatilibilies

-

16:09 <ubot5> Launchpad bug 1747965 in cloud-init (Ubuntu) "cloud-init status reports done before boot is finished" [High,Fix released] https://launchpad.net/bugs/1747965

-

16:09 <ubot5> Launchpad bug 1747070 in cloud-init "ds-identify does not see nocloud seed in core snap" [Medium,Fix committed] https://launchpad.net/bugs/1747070

-

16:11 <blackboxsw> * Fixed centos cloud-init build and test tooliing

-

16:12 <blackboxsw> * SUSE: Fix groups used for ownership of cloud-init.log [RobertS]

-

16:12 <blackboxsw> thanks folks for continuing to push on quality of cloud-init releases.

-

16:12 <smoser> o/ thanks for starting blackboxsw

-

16:13 <blackboxsw> not sure if I'm missing any other content that has landed in the last week and a half

-

16:14 <blackboxsw> I also think powersj rharper may have sorted a couple of issues with storage on our common CI on Jenkins

-

16:14 <blackboxsw> #link https://jenkins.ubuntu.com/server/view/cloud-init/

-

16:14 <powersj> Yes CI is up and running again, I have more defensive statements in to prevent us from running out of storage

-

16:15 * blackboxsw is not sure, are there rumors we might have more hardware dedicated to jenkins in the future powersj ?

-

16:15 <powersj> We do, however it is our jenkins master that runs out of storage :\

-

16:15 <blackboxsw> ahh gotcha, SPOF

-

16:16 <powersj> yeah

-

16:16 <blackboxsw> ok, if no other work is 'complete'; let's jump topics

-

16:16 <blackboxsw> ahh forgot ryan landed

-

16:16 <blackboxsw> net: accept network-config in netplan format for renaming interfaces

-

16:17 <blackboxsw> per LP: #1709715

-

16:17 <ubot5> Launchpad bug 1709715 in cloud-init "cloud-init apply_net_config_names doesn't grok v2 configs" [Medium,Confirmed] https://launchpad.net/bugs/1709715

-

16:18 <blackboxsw> #topic In-progress Development

-

16:18 <blackboxsw> So we are working toward quality on the 18.1 release for next week.

-

16:19 <blackboxsw> Ubuntu specifically is finalizing verification on cloud-init 17.2.35 update for Xenial and Artful series (expectation is that this SRU will be public in 1 week). 17.2.35 is a snapshot of tip from a couple days ago

-

16:20 <blackboxsw> we've also published tip of cloud-init master to bionic to keep the development release up to date with latest cloud-init

-

16:20 <blackboxsw> current ongoing work as always is on our trello board. we tried tidying up the cards a bit

-

16:20 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:21 <blackboxsw> we have upcoming branches for a new snap cloud-config module for configuring and maintaining snap packages

-

16:21 <rharper> https://bugs.launchpad.net/cloud-init/+bug/1749722

-

16:21 <ubot5> Ubuntu bug 1749722 in cloud-init "NTP: take into account systemd-timesyncd where present" [Medium,In progress]

-

16:21 <rharper> I'm actively working on that

-

16:22 <blackboxsw> this snap work will obsolete snappy and snap_config modules, so expect that they'll be deprecated. in 18.1 and dropped completely in 18.2

-

16:22 <smoser> https://code.launchpad.net/~rski/cloud-init/+git/cloud-init/+merge/312284

-

16:22 <smoser> i just moved that back into review

-

16:22 <blackboxsw> #link https://bugs.launchpad.net/cloud-init/+bug/1749722

-

16:22 <smoser> hope to take a lookc at it today.

-

16:22 <blackboxsw> #link https://code.launchpad.net/~rski/cloud-init/+git/cloud-init/+merge/312284

-

16:23 <blackboxsw> so per rharper's; chrony will be first class citizen in cloud-init

-

16:26 <blackboxsw> per cards in our trello board TODO lane, any card above the 18.1 release card (and anything in Doing/Review lane) is something we want to land in the 18.1 release

-

16:26 <blackboxsw> ... next topic so we can talk about release

-

16:27 <blackboxsw> #topic cloud-init version 18.1 release (2/23/2018)

-

16:27 <blackboxsw> next thursday we want to cut tip of cloud-init with any features we want to fold into the 18.1 release

-

16:28 <blackboxsw> this point in the meeting is a good opportunity for us to discuss features and bugs that any folks think are a priority for this release

-

16:29 <blackboxsw> smoser we saw some talk about archlinux support/updates, do we know whether we've gotten any updates about gaps/needs/bugs there?

-

16:29 <stanguturi> @blackboxsw: I have two requests. One for the merge request and one about the bug.

-

16:29 <smoser> blackboxsw: i've not seen any more than that developer asked about here in the channel.

-

16:30 <stanguturi> @blackboxsw: Let me know if I can post my questions here or discuss them offline.

-

16:30 <blackboxsw> stanguturi: please do discuss here. open forum :)

-

16:30 <blackboxsw> if it gets too long a discussion, we can take it to your branch or email

-

16:31 <blackboxsw> #link https://code.launchpad.net/~sankaraditya/cloud-init/+git/cloud-init/+merge/337736

-

16:31 <blackboxsw> for reference right ?

-

16:31 <stanguturi> @blackboxsw: Thanks. I have a merge request posted at https://code.launchpad.net/~sankaraditya/cloud-init/+git/cloud-init/+merge/337736

-

16:31 <stanguturi> Want this to get into 18.1 It's a low-risk fix. Should not break anything.

-

16:32 <stanguturi> Also, found a bug in ds-identify . https://bugs.launchpad.net/cloud-init/+bug/1749980

-

16:32 <ubot5> Ubuntu bug 1749980 in cloud-init "ds-identify doesn't properly detect ISO" [Undecided,New]

-

16:32 <blackboxsw> ok just glancing at your branch now stanguturi looks fairly straight forward, and as always I'd like to see some unit tests covering that changeset

-

16:33 <stanguturi> @blackboxsw: We already have unit tests for DataSourceOVF. This actually doesn't add any new functionality. The existing test cases should be sufficient enough.

-

16:33 <blackboxsw> we have existing unit tests in tests/unittests/test_ds_identify.py which should be easy to extend for the additional detection

-

16:33 <blackboxsw> in ds-identify

-

16:34 <blackboxsw> yeah I was thinking more about ds-identify specifically

-

16:35 <blackboxsw> all said though, that branch looks low-risk and we can probably get that landed before release.

-

16:35 <blackboxsw> I'll add a card to trello for us to shepherd that in.

-

16:35 <stanguturi> @blackboxsw: Great. Thanks.

-

16:36 <stanguturi> @blackboxsw: Also I have a question about https://bugs.launchpad.net/cloud-init/+bug/1749980 Any inputs will be great.

-

16:36 <ubot5> Ubuntu bug 1749980 in cloud-init "ds-identify doesn't properly detect ISO" [Undecided,New]

-

16:37 <blackboxsw> #link https://bugs.launchpad.net/cloud-init/+bug/1749980

-

16:37 <blackboxsw> looking

-

16:38 <blackboxsw> ohh good stanguturi we'll sort that bug and either provide more information on this

-

16:38 <blackboxsw> for that bug discussion, let's move it to the "office hours" topic which comes up next

-

16:38 <blackboxsw> I'd like smoser rharper to peek at that too

-

16:38 <stanguturi> @blackboxsw: Ok. Sure. Thanks

-

16:39 <blackboxsw> any other topics, branches or bugs that folks are itching to get in for 18.1 release?

-

16:41 <blackboxsw> kpcyrd: any opdates or concerns on archlinux that you are aware of currently?

-

16:42 <smoser> stanguturi: you can run a command there now ?

-

16:42 <blackboxsw> let's transition to office hours now

-

16:42 <smoser> 2 things

-

16:42 <blackboxsw> #topic Office hours (next ~30 mins)

-

16:43 <stanguturi> @smoser: Sorry. Didn't quite get the question.

-

16:43 <blackboxsw> And thanks all for joining. Any burning questions, bugs, branches that need discussion can be brought up now.

-

16:44 <stanguturi> @smoser: Oh. Are you asking if I can run any commands in my virtual machine right now.? Yeah. Sure.

-

16:44 <smoser> stanguturi: can you run stuff int hat system ?

-

16:44 <smoser> a.) cat /run/cloud-init/ds-identify.log

-

16:44 <smoser> b.) idstr="http://schemas.dmtf.org/ovf/environment/1"

-

16:45 <smoser> grep --quiet --ignore-case "$idstr" /dev/sr0

-

16:45 <smoser> grep --quiet --ignore-case "$idstr" /dev/sr0 && echo y || echo n

-

16:46 <smoser> stanguturi: basically the 'is_cdrom_ovf' should have gone down the path into that grep of the cdrom block device

-

16:48 <stanguturi> @smoser: grep --quiet --ignore-case "$idstr" /dev/sr0 returned "grep: /dev/sr0: Input/output error"

-

16:48 <stanguturi> @smoser: grep --quiet --ignore-case "$idstr" /dev/sr0 && echo y || echo n returned "grep: /dev/sr0: Input/output error and then new line and then n'

-

16:48 <meetingology> stanguturi: Error: No closing quotation

-

16:48 <blackboxsw> heh thanks meetingology

-

16:50 <stanguturi> @smoser: Actually, read_fs_info doesn't DI_ISO9660_DEVS in my system. and because of this, dscheck_OVF returns DS_NOT_FOUND.

-

16:51 <smoser> stanguturi: what release are you on ?

-

16:51 <stanguturi> Trying it on 17.04 zesty desktop

-

16:52 <stanguturi> and tried with top of the tree code in cloud-init.

-

16:56 <smoser> stanguturi: could you potentially let me in via ssh ?

-

16:57 <stanguturi> @smoser: Sorry. It's on my private network. Will not be able to provide ssh.

-

16:58 <stanguturi> @smoser: We can do a webex conference if you want.

-

17:03 <smoser> stanguturi: can you ssh out of the node ?

-

17:03 <stanguturi> @smoser: Yes.

-

17:07 <smoser> ok. /query window

-

17:11 <blackboxsw> ok this triage will continue. if there are no other pressing bugs/concerns, we'll close out this meeting and keep pushing toward 18.1 upstream release next thursday

-

17:11 <blackboxsw> thanks again for your time folks. I'll post these minutes to the cloud-init github page

-

17:12 <blackboxsw> #link https://cloud-init.github.io

-

17:17 <blackboxsw> next meeting march 5th same "bat time" same "bat channel"

-

17:18 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2018-03-05.html b/status-2018-03-05.html deleted file mode 100644 index 4f3533f..0000000 --- a/status-2018-03-05.html +++ /dev/null @@ -1,280 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Mon 05 March 2018 in status-meeting-minutes - - • 6 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

Recent Changes

-

The discussion about "Recent Changes" started at 17:02.

- -

In-progress Development

-

The discussion about "In-progress Development" started at 17:12.

- -

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (58)
  • -
  • stanguturi (13)
  • -
  • smoser (7)
  • -
  • ubot5` (7)
  • -
  • meetingology (3)
  • -
  • powersj (1)
  • -
  • rharper (1)
  • -
-

Full Log

-

17:00 <blackboxsw> #startmeeting Cloud-init bi-weekly status meeting

-

17:00 <meetingology> Meeting started Mon Mar 5 17:00:58 2018 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

17:00 <meetingology>

-

17:00 <meetingology> Available commands: action commands idea info link nick

-

17:01 <powersj> o/

-

17:01 <blackboxsw> hey folks welcome to another episode of Cloud-init status updates. Thanks for coming.

-

17:02 <blackboxsw> Since we had a status meeting just prior to the cloud-init upstream release last week there won't be a ton of updates this week.

-

17:02 <rharper> o--

-

17:02 <blackboxsw> without further ado

-

17:02 <blackboxsw> #topic Recent Changes

-

17:03 <blackboxsw> highlight of the last week was the upstream 18.1 release getting cut! Great work folks on getting branches landed in tip proir to release

-

17:03 * blackboxsw grabs powersj highlights

-

17:03 <blackboxsw> cloud-init 18.1 released!

-

17:03 <blackboxsw> ds-identify: Fix searching for iso9660 OVF cdroms for vmware (LP: #1749980)

-

17:03 <blackboxsw> Documented chef example incorrectly represented apt source configuration for chef install

-

17:03 <blackboxsw> SUSE: Fix groups used for ownership of cloud-init.log (Robert Schweikert)

-

17:03 <blackboxsw> OVF: Fix VMware support for 64-bit platforms (Sankar Tanguturi)

-

17:03 <blackboxsw> Salt: configure grains in grains file rather than in minion config (Daniel Wallace)

-

17:03 <blackboxsw> Implement puppet 4 support (Romanos Skiadas)

-

17:03 <ubot5>` Launchpad bug 1749980 in cloud-init "ds-identify doesn't properly detect ISO" [High,Fix released] https://launchpad.net/bugs/1749980

-

17:04 <blackboxsw> For those that didn't see the email:

-

17:04 <blackboxsw> #link https://lists.launchpad.net/cloud-init/msg00144.html

-

17:04 <smoser> o/

-

17:04 <blackboxsw> thanks again stanguturi Akihiko and Max Illfelder

-

17:06 <blackboxsw> in the ubuntu side of the house we published 18.1 to the Bionic series so clouds now have this by default in bionic images

-

17:06 <blackboxsw> Also on the ubuntu-side of the house we finalized an SRU (stable release update) of 17.2.35.2 into both Xenial and Artful, so xenial-updates and artful-updates should have 17.2.35 available (which is only a few commits earlier than the 18.1 release)

-

17:10 <blackboxsw> Also in tip post 18.1 we had significant contribution from partners

-

17:11 <blackboxsw> Simplify some comparisions. [Rémy Léone]

-

17:11 <blackboxsw> Change some list creation and population to literal. [Rémy Léone]

-

17:11 <blackboxsw> GCE: fix reading of user-data that is not base64 encoded.

-

17:11 <blackboxsw> doc: fix chef install from apt packages example in RTD.

-

17:11 <blackboxsw> Implement puppet 4 support [Romanos Skiadas]

-

17:11 <blackboxsw> subp: Fix subp usage with non-ascii characters when no system locale.

-

17:11 <blackboxsw> salt: configure grains in grains file rather than in minion config. [Daniel Wallace]

-

17:11 <blackboxsw> (sorry took me a while to dig up the git formatting options)

-

17:12 <blackboxsw> #topic In-progress Development

-

17:12 <blackboxsw> We have some existing branches we are trying to get review feedback to folks on:

-

17:12 <blackboxsw> #link http://bit.ly/ci-reviews

-

17:13 <blackboxsw> Are there reviews that folks feel need some attention this week?

-

17:13 <blackboxsw> Internally, we work on items in the TODO/Doing lane of our trello board here:

-

17:13 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

17:14 <stanguturi> @blackboxsw: I have one request about the bug https://bugs.launchpad.net/cloud-init/+bug/1724128 Any inputs from cloud-init team will be great.

-

17:14 <ubot5>` Ubuntu bug 1724128 in open-vm-tools (Ubuntu) "Need a Success / Failure notification mechanism when cloud-init finishes." [Undecided,New]

-

17:15 <blackboxsw> so we have some Snap module development incoming on chrony support, snappy support, vsphere early hostname support

-

17:16 <blackboxsw> stanguturi: checking

-

17:17 <stanguturi> blackboxsw: Thanks. I discussed this last year in August in cloud-init meeting. Logged this bug long time back. But for some reason, it was not tagged with the proper project. My bad.

-

17:18 <blackboxsw> stanguturi: we have an external notification mechanism for scripts to information about when cloud-init has finally completed via "cloud-init status --wait" .... hrm trying to discuss here about alternative mechanisms internal to cloud-init

-

17:21 <blackboxsw> stanguturi: ok we can probably add a publish/subscription mechanism in cloud-init proper for internal eventing that'd get this done.

-

17:21 <stanguturi> @blackboxsw: Thanks a lot.

-

17:21 <blackboxsw> I've added a topic to our meetings this week to discuss the approach that could make this happen.

-

17:21 <blackboxsw> We'll comment on the bug/mailing list with an approach proposal

-

17:22 <blackboxsw> #link https://bugs.launchpad.net/cloud-init/+bug/1724128

-

17:22 <ubot5>` Ubuntu bug 1724128 in open-vm-tools (Ubuntu) "Need a Success / Failure notification mechanism when cloud-init finishes." [Undecided,New]

-

17:22 <blackboxsw> just so I capture the link

-

17:23 <stanguturi> @blackboxsw: Thanks I have got another request. I am working on https://code.launchpad.net/~sankaraditya/cloud-init/+git/cloud-init/+ref/vmware-customize-utc-time to add some 'UTC customizations'. Got some review comments from Scott Moser. Can you please provide some pointers to any existing / tests / procedure to add new functionality to distro class

-

17:27 <blackboxsw> stanguturi: re-reading ... and checking out the existing cloudinit.distro base module for utc /tz specifics

-

17:29 <stanguturi> @blackboxsw: We just want to customize /etc/default/rcS file with some settings on debian platforms.

-

17:36 <blackboxsw> hrm, so I'm conflicted with your branch by seeing that Distro.tz_zone_dir sets that path for for that distro for where TZ information is being configured. I think I'm missing why UTC=yes|no is needed versus Debian.set_timezone

-

17:38 <stanguturi> @blackboxsw: This is actually related to 'hwclock'. The key value that needs to be set in /etc/default/rcS is 'UTC' but it's related to 'hwclock' setting.

-

17:38 <blackboxsw> for my suggestion on that initial review, I thought that we might need to allow for a Debian-specific method which would handle this additional/separate configuration file processing you were doing w/ /etc/default/rcS

-

17:40 <smoser> looking quicklyi it looks like at least recently the correct place to store that is /etc/default/hwclock

-

17:40 <smoser> /etc/default/rcS is read, but per /etc/init.d/hwclock.sh, it looks like /etc/default/hwclock is preferred

-

17:41 <smoser> but either way, wahat i think we really want is for the distro class to have a 'store_hwclock_timezone' or something

-

17:41 <smoser> and then you'd call into that.

-

17:42 <stanguturi> ok. Thanks Scott. Are there any extra test cases / test suites that I need to run if I am modifying the distro class?

-

17:42 <blackboxsw> as far as developing additional unit tests for a new distro method: I'd expect new feature methods to be covered in tests/unittests/test_distros/test_debian.py

-

17:42 <blackboxsw> also cloud-init summit action we haven't done yet is to move all unittests out of tests/unittests and under cloudinit proper

-

17:42 <smoser> +1 blackboxsw

-

17:44 <stanguturi> ok Will work on that.

-

17:44 <blackboxsw> I'll take that test migration action for any existing modules that are already tested under tests/unittests. The policy we were hoping is that for new modules added under "cloudinit" we'd add a cloudinit/somepath/tests/test_newmodule.py for each cloudinit/somepath/newmodule.py

-

17:45 <blackboxsw> so if you want to build on tests/unittests/test_distros/test_debian.py we'll pull that under cloudinit proper when we finally remove tests/unittests altogether

-

17:45 <blackboxsw> stanguturi: any other items?

-

17:46 <blackboxsw> otherwise I think we'll probably wrap up this meeting in a few minutes

-

17:46 <stanguturi> Yeah. I have one more item. Sorry. https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1750780

-

17:46 <ubot5>` Ubuntu bug 1750780 in open-vm-tools (Ubuntu Xenial) "Race with local file systems can make open-vm-tools fail to start" [Undecided,Triaged]

-

17:47 <blackboxsw> no worries at all stanguturi we like the interest

-

17:47 <stanguturi> We just noticed that on Ubuntu 18.04 VMs, open-vm-tools service doesn't work with cloud-init.

-

17:47 <stanguturi> We didn't have any issues on 17.10. But only found in 18.04

-

17:47 <blackboxsw> #link https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1750780

-

17:48 <ubot5>` Ubuntu bug 1750780 in open-vm-tools (Ubuntu Xenial) "Race with local file systems can make open-vm-tools fail to start" [Undecided,Triaged]

-

17:48 <stanguturi> I first logged the bug https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1667831 and it was fixed and it was mentioned that now the bug 1750780 came up.

-

17:48 <ubot5>` Ubuntu bug 1667831 in open-vm-tools (Ubuntu) "cloud-init dependency for open-vm-tools service" [Undecided,Fix released]

-

17:51 <smoser> stanguturi: i'll talk with christian tomorrow about the bug there.

-

17:52 <stanguturi> ok Thanks Scott.

-

17:52 <blackboxsw> #link https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1667831

-

17:52 <ubot5>` Ubuntu bug 1667831 in open-vm-tools (Ubuntu) "cloud-init dependency for open-vm-tools service" [Undecided,Fix released]

-

17:52 <blackboxsw> ok I think we'll have to call this meeting a close for this week. Thanks again stanguturi for the help/chat here.

-

17:53 <blackboxsw> as always I'll post this log to the site:

-

17:53 <blackboxsw> #link https://cloud-init.github.io

-

17:53 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2018-03-19.html b/status-2018-03-19.html deleted file mode 100644 index 62b26cc..0000000 --- a/status-2018-03-19.html +++ /dev/null @@ -1,377 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Mon 19 March 2018 in status-meeting-minutes - - • 11 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:05.

- -

In-progress Development

-

The discussion about "In-progress Development" started at 16:12.

- -

Office hours (next ~30 mins)

-

The discussion about "Office hours (next ~30 mins)" started at 16:43.

- -

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (85)
  • -
  • smoser (57)
  • -
  • stanguturi (16)
  • -
  • ubot5` (8)
  • -
  • ajorg (5)
  • -
  • rharper (5)
  • -
  • dpb1 (4)
  • -
  • meetingology (3)
  • -
-

Full Log

-

16:02 <blackboxsw> #startmeeting Cloud-init bi-weekly status meeting

-

16:02 <meetingology> Meeting started Mon Mar 19 16:02:30 2018 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:02 <meetingology>

-

16:02 <meetingology> Available commands: action commands idea info link nick

-

16:03 <blackboxsw> ok, let's kick off this cloud-init bi-weekly meeting. welcome all!

-

16:04 <dpb1> o/

-

16:04 <blackboxsw> 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.

-

16:05 <blackboxsw> #topic Recent Changes

-

16:05 <dpb1> smoser vacation specifically

-

16:05 <blackboxsw> hehe. Generally we're tracking high-points of what lands in our trello board

-

16:05 <blackboxsw> #link http://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:06 <blackboxsw> but from changelogs folks have made progress on azure, vmware and FreeBSD deployment targets

-

16:06 <blackboxsw> - netplan: render bridge port-priority values (LP: #1735821)

-

16:06 <blackboxsw> - net: recognize iscsi root cases without ip= on kernel command line.

-

16:06 <blackboxsw> (LP: #1752391)

-

16:06 <blackboxsw> - util: Fix subp regression. Allow specifying subp command as a string.

-

16:06 <blackboxsw> (LP: #1755965)

-

16:06 <blackboxsw> - This commit fixes get_hostname on the AzureDataSource.

-

16:06 <blackboxsw> [Douglas Jordan] (LP: #1754495)

-

16:06 <ubot5>` Launchpad bug 1735821 in nplan (Ubuntu Artful) "netplan needs bridge port-priority support" [Medium,Fix committed] https://launchpad.net/bugs/1735821

-

16:06 <blackboxsw> - shellify: raise TypeError on bad input.

-

16:06 <blackboxsw> - FreeBSD: Set hostname to FQDN. [Dominic Schlegel] (LP: #1753499)

-

16:06 <blackboxsw> - Make salt minion module work on FreeBSD.

-

16:06 <blackboxsw> [Dominic Schlegel] (LP: #1721503)

-

16:06 <ubot5>` Launchpad bug 1752391 in cloud-init "cloud-init does not recognize initramfs provided network config in all cases" [Medium,Fix committed] https://launchpad.net/bugs/1752391

-

16:06 <blackboxsw> - set_hostname: When present in metadata, set it before network bringup.

-

16:06 <blackboxsw> (LP: #1746455) VMWare

-

16:06 <ubot5>` Launchpad bug 1755965 in cloud-init "util.subp regression: no longer accept commands as string" [High,Fix committed] https://launchpad.net/bugs/1755965

-

16:06 <blackboxsw> - cc_snap: Add new module to install and configure snapd and snap

-

16:06 <blackboxsw> packages.

-

16:06 <blackboxsw> - doc: fix all warnings issued by 'tox -e doc'

-

16:06 <blackboxsw> - tests: Make pylint happy and fix python2.6 uses of assertRaisesRegex.

-

16:06 <ubot5>` Launchpad bug 1755965 in cloud-init "duplicate for #1754495 util.subp regression: no longer accept commands as string" [High,Fix committed] https://launchpad.net/bugs/1755965

-

16:06 <blackboxsw> - tests: fix run_tree and bddeb

-

16:06 <blackboxsw> - tests: Fix some warnings in tests that popped up with newer python.

-

16:06 <ubot5>` Launchpad bug 1753499 in cloud-init "hostname in FreeBSD should prefere FQDN" [Undecided,Fix committed] https://launchpad.net/bugs/1753499

-

16:06 <blackboxsw> - tests: fix flakes warning for unused variable

-

16:06 <blackboxsw> - tests: patch leaked stderr messages from snap unit tests

-

16:06 <ubot5>` Launchpad bug 1721503 in cloud-init "salt module not able to be used on FreeBSD" [Medium,Fix committed] https://launchpad.net/bugs/1721503

-

16:06 <blackboxsw> - tests: Centralize and re-use skipTest based on json schema presense.

-

16:06 <ubot5>` Launchpad bug 1746455 in cloud-init "cloud-init vSphere cloud provider DHCP unique hostname issue" [High,Fix committed] https://launchpad.net/bugs/1746455

-

16:08 <blackboxsw> a big thanks to dojordan (Azure) and Dominic Schlegel (FreeBSD) for patching some gaps in support as cloud-init master progresses

-

16:10 <blackboxsw> 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

-

16:11 <blackboxsw> I think that's probably it for 'done' work. We have a few things in flight at the moment

-

16:12 <blackboxsw> #topic In-progress Development

-

16:13 <blackboxsw> Ubuntu is getting a number of new cloud-config modules:

-

16:13 <blackboxsw> - new cc_snap module (deprecated cc_snappy and cc_snap_config modules) the ability to install and manage snap package

-

16:14 <blackboxsw> - new cc_ubuntu_drivers: support to install 3rd party drivers on install

-

16:15 <blackboxsw> - new cc_ubuntu_advantage: manage Ubuntu Advantage subscriptions for services such as Extended Security Mainenance (trusty), canonical livepatch and FIPS PPAs

-

16:15 <blackboxsw> these should be landing in the week(s) to come

-

16:15 <blackboxsw> and cc_snap landed already

-

16:17 <blackboxsw> 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)

-

16:17 <rharper> blackboxsw: smoser: on the lander emails, the subject could include the git hash (or branch name); it's currently only in the body;

-

16:17 <smoser> rharper: i had suggested to blackboxsw that it should acutally change to not send a subject. so it threads in your email reader with the other MP mails.

-

16:18 <rharper> heh

-

16:18 <blackboxsw> maybe we can toggle between the two modulus 2 :)

-

16:18 <rharper> sorry, didn't meant to disturb the flow

-

16:19 <rharper> continue

-

16:19 <blackboxsw> 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

-

16:19 <blackboxsw> anything to free up developer time will give us more time for reviews/code

-

16:19 <ajorg> should vendor-specific modules be shipped in a separate package?

-

16:20 <smoser> vendor specific modules ?

-

16:20 <ajorg> ubuntu_advantage

-

16:22 <blackboxsw> good question/point. I hand't thought about that separation as a lot of the modules cloud-init delivers support a subset of distros

-

16:23 <blackboxsw> each module has a distro attribute defined as to whether or not it will even run

-

16:23 <blackboxsw> so we have spacewalk, zypper_repos etc

-

16:24 <smoser> and cloud.cfg is rendered based on knowledge of the distro

-

16:24 <smoser> so ubuntu_advantage wont even be in the list of config modules

-

16:24 <smoser> having a static config module list is WIN in this case (but pain elsewhere)

-

16:25 <smoser> at some point whe may have a more dynamic config module list.

-

16:25 <smoser> but anyway... at the moment the only cost to non-ubuntu of that module being shipped is bytes on disk.

-

16:26 <blackboxsw> 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.

-

16:26 <ajorg> agree that having a more dynamic config module list is prerequisite to being able to parcel out modules to other packages

-

16:26 <blackboxsw> so that we don't expect folks to add plugins directly into /usr/lib/python3/dist-packages/cloudinit/config/ for instance

-

16:26 <smoser> 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.

-

16:29 * ajorg is satisfied

-

16:30 <blackboxsw> :). the only other thing I can think of in progress two more datasources softlayer cloud support by smoser and hetzner cloud

-

16:30 <blackboxsw> so cloud-init is getting it's grubby hands into a couple of more clouds shortly.

-

16:31 <blackboxsw> s/it's/its/

-

16:31 <blackboxsw> it's nice to see the adoption continue to grow

-

16:31 <smoser> looks like someone followed up on hetzner

-

16:31 <smoser> so that hopefully is ready to land

-

16:31 <blackboxsw> #link https://code.launchpad.net/~lp-markusschade/cloud-init/+git/cloud-init

-

16:32 <blackboxsw> rharper: also has a couple of branches to allow cloud-init to work a bit better when rendering netplan configuration

-

16:33 <blackboxsw> I think that's all for in-progress development at the moment.

-

16:33 <smoser> man we need to fix that pylint thing.

-

16:33 <smoser> did you mention ?

-

16:33 <rharper> blackboxsw: yeah, I just pushed a fix for v1 global dns entries to get rendered under interfaces without any dns configuration

-

16:33 <blackboxsw> Anything else that should be noted by anyone?

-

16:33 <blackboxsw> #link https://code.launchpad.net/~lp-markusschade/cloud-init/+git/cloud-init/+merge/338439

-

16:33 <blackboxsw> oops

-

16:34 <smoser> cloudinit/config/cc_puppet.py:143: [W1505(deprecated-method), handle] Using deprecated method readfp()

-

16:34 <blackboxsw> #link https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/341662

-

16:34 <smoser> 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.

-

16:35 <blackboxsw> yeah how much should we freeze our deps?

-

16:35 <blackboxsw> it's kindof annoying to have your branch locally pass ci, and a fresh build of CI deps fail when you try to land

-

16:36 <blackboxsw> but I don't really know whether it's worth us 'pinning' everything

-

16:36 <smoser> i think pinning everything is generally the best practice for this sort of thing now.

-

16:37 <smoser> oh my.

-

16:37 <blackboxsw> so if we pin the world, should we also just make it a habit to occasionally tox -e tip-pylint?

-

16:37 <smoser> blackboxsw: did you know you accidently fixed that in trunk ?

-

16:38 <blackboxsw> smoser: I know I intentionally added a pylint ignore on that to come back and address it today.

-

16:38 <ajorg> 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.

-

16:38 <smoser> oh ko. i see.

-

16:39 <smoser> 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

-

16:40 <smoser> there is the "good" break, where new upload to pypi identifies some lingering bug

-

16:40 <blackboxsw> +1 ajorg, but I'm good (on avoiding a avalanche) if we agree to run tip-pylint target fairy regularly to avoid the landslide

-

16:40 <smoser> but also the "bad" break where some upload breaks your c-i for invalid reason.

-

16:42 <smoser> one huge advantage to pinning is the ability to re-create things.

-

16:42 <blackboxsw> it definitely felt like last week was a lot of c-i breaks for changes unrelated to the code up for review

-

16:42 <smoser> ie, if you were looking to it bisect something...

-

16:42 <smoser> git bisect

-

16:43 <blackboxsw> I should transition to the office hours topic so we can continue discussion

-

16:43 <smoser> you can't really do that if trunk from a point in the past does not pass C-I because an external dependency changed.

-

16:43 <smoser> sure we can transition to office hours.

-

16:43 <blackboxsw> #topic Office hours (next ~30 mins)

-

16:43 <smoser> but yeah... i want c-i on tip to not just start failing.

-

16:44 <stanguturi> @blackboxsw, I have couple of requests. First, https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1724128 discussed this in last meeting as well. Any help is greatly appreciated

-

16:44 <ubot5>` Ubuntu bug 1724128 in open-vm-tools (Ubuntu) "Need a Success / Failure notification mechanism when cloud-init finishes." [Undecided,New]

-

16:44 <blackboxsw> 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?

-

16:45 <smoser> blackboxsw: i'mi fine with that... thats why we added the tip-* targets. so it was easy enough to keep current.

-

16:45 <blackboxsw> +1 smoser I'll put a card up for that

-

16:46 <smoser> stanguturi: your suggestion there is not a bad idea at all.

-

16:46 <blackboxsw> #link https://trello.com/c/vD1em9WP/698-jenkins-job-to-run-tox-tip-pylint-weekly-pin-all-lint-versions-otherwise

-

16:46 <smoser> the desire to have cloud-init tell the platform/datasource that it failed or succeeded is valid.

-

16:47 <smoser> with MAAS, that his done via reporting

-

16:47 <blackboxsw> stanguturi: hiya. I think we talked after that meeting about trying to allow the datasource to subscribe to a callback when cloud-init exists

-

16:47 <blackboxsw> stanguturi: hiya. I think we talked after that meeting about trying to allow the datasource to subscribe to a callback when cloud-init exits

-

16:47 <smoser> cloud-init reports status and results via a Reporter.

-

16:47 <smoser> dojordan (i think) had also put up a request for a reproter module on azure.

-

16:47 <smoser> so we do kind of have the function you're after in place.

-

16:48 <stanguturi> smoser: ok. Any inputs / examples of using it will be really great.

-

16:50 <smoser> stanguturi: well, the reporter interface is pretty simple. you can cloudinit/reporting/handlers.py

-

16:51 <smoser> blackboxsw: http://paste.ubuntu.com/p/6KjDX8WHQH/

-

16:51 <smoser> did you intend boht of those changes ?

-

16:51 <stanguturi> smoser: ok. Then do I need to write a new handler for our DataSource?

-

16:52 <smoser> stanguturi: well you write a reporting Handler, ankd then either system confi or optionally datasource config would turn that reporter on.

-

16:52 <blackboxsw> wow smoser, no

-

16:52 <blackboxsw> wow, ok, I'll put up a branch to fix that

-

16:52 <stanguturi> smoser: ok. Will work on that.

-

16:52 <smoser> ok.

-

16:53 <stanguturi> I have another quick request about https://code.launchpad.net/~sankaraditya/cloud-init/+git/cloud-init/+ref/set_hwclock_module

-

16:53 <smoser> stanguturi: do you find this is actually needed ?

-

16:53 <smoser> to my knowledge the only time anyone would ever set their hardware clock to something other than UTC would be dual booting with windows.

-

16:54 <smoser> which i can't seem to believe is all that a common situation in VMs

-

16:54 <stanguturi> smoser: Yeah. We need this for 'VMware guest customization workflow'.

-

16:54 <dpb1> smoser: oh man, I hope not

-

16:54 <stanguturi> 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.

-

16:54 <smoser> stanguturi: does it actually solve a current problem for you ?

-

16:55 <stanguturi> smoser: For 'VMware managed VMs', customers can specify in the specification file if they want UTC or localtime for the hardware clock.

-

16:55 <smoser> or one that originally came in from a decade ago

-

16:55 <stanguturi> 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.

-

16:55 <smoser> hm... so my sugestion is really to stop allowing that :)

-

16:56 <stanguturi> smoser: Oh ok. Can you please add a comment to that merge request just for the record.

-

16:56 <smoser> i very well could be wrong

-

16:56 <smoser> but the only time that i ever had to deal with this was when dual booting

-

16:56 <smoser> with windows specifically

-

16:57 <stanguturi> smoser: ok.

-

16:57 <smoser> am i wrong there ?

-

16:57 <smoser> i really could be.

-

16:58 <stanguturi> smoser: I can discuss this within our team. But to be on par with our existing engine, want to port the changes.

-

16:58 <smoser> and even if you get it wrong, generally speaking you havhe some sort of ntpdate or ntp that will fix your system clock anyway.

-

16:58 <smoser> stanguturi: yeah. i understand that.

-

16:58 <stanguturi> 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.

-

16:59 <stanguturi> Want to know your opinion, shall we set it in cloud-init installation phase or request Ubuntu maintainers to set it in 18.04

-

17:00 <stanguturi> smoser: And when is the cloud-init 18.2 scheduled for release? 3/22?

-

17:01 <blackboxsw> probably a good time for us to bring that up

-

17:01 <smoser> yeah. whoops.

-

17:01 <smoser> :)

-

17:01 <smoser> 18.2 is scheduled for 3/22 (thursday)

-

17:02 <blackboxsw> 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

-

17:02 <smoser> but amoung our internall team we decided to push that to 3/27

-

17:02 <stanguturi> smoser: ok. Thanks for the update.

-

17:02 <blackboxsw> there a a few in flight branches, azure, softlayer etc that we'd like to get in and get tested before 18.2

-

17:02 <smoser> we will send an email today or tomrrow witih "pending release" like subject like we've done before.

-

17:03 <blackboxsw> dpb1: others any objections to cutting the 18.2 release on Tuesday 3/27?

-

17:03 <dpb1> none

-

17:04 * blackboxsw adds the upcoming date to the topic

-

17:05 <blackboxsw> ... ok, folks interested in discussing today?

-

17:08 <blackboxsw> #link https://cloud-init.github.io

-

17:09 <blackboxsw> The above link will have our captured logs for this meeting.

-

17:09 <blackboxsw> thanks again for tuning in

-

17:09 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2018-04-02.html b/status-2018-04-02.html deleted file mode 100644 index 03e637c..0000000 --- a/status-2018-04-02.html +++ /dev/null @@ -1,280 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Mon 02 April 2018 in status-meeting-minutes - - • 5 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:08.

- -

In-progress Development

-

The discussion about "In-progress Development" started at 16:19.

- -

Office Hours (next ~30 minutes)

-

The discussion about "Office Hours (next ~30 minutes)" started at 16:27.

- -

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (64)
  • -
  • rharper (14)
  • -
  • ubot5 (3)
  • -
  • meetingology (3)
  • -
  • powersj (2)
  • -
-

Full Log

-

16:05 <blackboxsw> #startmeeting bi-weekly status meeting

-

16:05 <meetingology> Meeting started Mon Apr 2 16:05:50 2018 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:05 <meetingology>

-

16:05 <meetingology> Available commands: action commands idea info link nick

-

16:06 <blackboxsw> Welcome to the post-Easter episode of cloud-init's status meeting 🐰

-

16:06 <blackboxsw> Today's meeting will probably be light as we are fairly light on attendees given various holiday schedules

-

16:07 <rharper> o/

-

16:07 <rharper> nice rabbit ears

-

16:07 <blackboxsw> heya! As always, we'll go through recent changes, in progress work and ~30 minutes of office hours

-

16:08 <blackboxsw> feel free to interject and ask quesitons at any time.

-

16:08 <blackboxsw> #topic Recent Changes

-

16:09 <blackboxsw> Here's a brief run down of what we have committed to master in the last couple weeks

-

16:10 <blackboxsw> - Support for setting hostname from metadata prior to network bringup.

-

16:10 <blackboxsw> This fixes vsphere multi-vm deployments all coming up with the same

-

16:10 <blackboxsw> 'ubuntu' hostname. LP: #1746455

-

16:10 <blackboxsw> - Support initramfs iscsi root so network devices aren't disconnected

-

16:10 <blackboxsw> before shutdown

-

16:10 <blackboxsw> - Added cloud-config module cc_snap which enables loading snap

-

16:10 <blackboxsw> assertions, configuring snapd and installing snap packages on Ubuntu.

-

16:10 <ubot5> Launchpad bug 1746455 in cloud-init "cloud-init vSphere cloud provider DHCP unique hostname issue" [High,Fix released]

-

16:10 <blackboxsw> Deprecated cc_snappy and cc_snap_config modules.

-

16:10 <blackboxsw> - Make salt minion work on FreeBSD (Dominic Schlegel)

-

16:10 <blackboxsw> LP:#1721503

-

16:10 <blackboxsw> - Simplify compound conditionals (Rémy Léone)

-

16:10 <ubot5> Launchpad bug 1721503 in cloud-init "salt module not able to be used on FreeBSD" [Medium,Fix released]

-

16:10 <blackboxsw> - Change some list creation and population to literals (Rémy Léone)

-

16:10 <blackboxsw> - Add puppet 4 support configurable in cc_puppet module (Romanos

-

16:10 <blackboxsw> Skiadas)

-

16:10 <blackboxsw> - Fix datasouce Azure get_hostname function for hostname bounce

-

16:10 <blackboxsw> (Douglas Jordan) LP:#1754495

-

16:10 <blackboxsw> - OpenNebula datasource now uses network config v2 to support IPv6

-

16:10 <ubot5> Launchpad bug 1755965 in cloud-init (Ubuntu) "duplicate for #1754495 util.subp regression: no longer accept commands as string" [Critical,Fix released]

-

16:10 <blackboxsw> config (Akihiko Ota)

-

16:10 <blackboxsw> - Add Hetzner Cloud datasource support (Markus Schade)

-

16:11 <blackboxsw> The highlights of this work that will affect various clouds: hostname setting before network bringup, in cloud-init's init-local stage.

-

16:12 <blackboxsw> so if your cloud's metadata provides hostname information (per your instance creation) that hostname gets set before any potential dhcp discovery on the instance. This is a big win for Azure and may allow us to avoid/deprecate some of the hostname_bounce functionality

-

16:13 <blackboxsw> which was baked in to re-dhcp in order to publish updated hostname information to DDNS

-

16:14 <blackboxsw> We also have landed support for two new clouds: Hetzner Cloud and IBMCloud. A big thanks to Markus Schade for the Hetzner work there and smoser for the IBMCloud datasource

-

16:15 <blackboxsw> do3meli (Dominic Schlegel) has also been on a blitz fixing and updating a lot of FreeBSD support in cloud-init tip so thank you sir for that work as well.

-

16:16 <blackboxsw> We've just also landed some zfs resize support by rharper as well that should be making it's way into your friendly neighborhood Ubuntu Bionic series in a cloud near you

-

16:16 <blackboxsw> anything else I'm missing on rharper or powersj ?

-

16:16 <blackboxsw> ahh hold the phone

-

16:16 <rharper> blackboxsw: well, not my zfs-resize

-

16:17 <rharper> but I do have some fixes for it

-

16:17 <rharper> https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/fix/cc_resizefs_on_zfs_root

-

16:17 <blackboxsw> We officially released cloud-init 18.2 in master. There is an 18.2 tag in the repo for folks wanting to take an early cut of it.

-

16:17 <rharper> our ci-test backend normally runs with zfs, it's not right now so it missed a couple edge cases that we need to handle

-

16:18 <blackboxsw> Per cloud-init 18.2 here is an email sent to the cloud-init mailing list describing the details: https://lists.launchpad.net/cloud-init/msg00145.html

-

16:18 <blackboxsw> #link https://lists.launchpad.net/cloud-init/msg00145.html

-

16:18 <blackboxsw> #link https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/fix/cc_resizefs_on_zfs_root

-

16:19 <blackboxsw> #topic In-progress Development

-

16:20 <blackboxsw> The upstream team has released 18,2 to Bionic as of last week, and we started an Ubuntu SRU process into Xenial and Artful.

-

16:21 <blackboxsw> We expect the 18.2 to be present in Xenial and Artful within 2 weeks in your cloud, so if you are waiting on a feature, it won't be very long.

-

16:22 <blackboxsw> Also in-progress are some of rharper's zfs fixes, and some exception callback cleanup that will affect Azure, EC2, OpenStack and Scaleway clouds.

-

16:22 <blackboxsw> #link https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/fix/cc_resizefs_on_zfs_root

-

16:22 <blackboxsw> #link https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/342007

-

16:23 <blackboxsw> And we are doing our part to finally purge net-tools dependencies from cloud-init (in favor of iproute2)

-

16:23 <blackboxsw> #link https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/342428

-

16:24 <rharper> blackboxsw: I responded to your ip -6 route q from last week, did you see that ?

-

16:24 <blackboxsw> rharper: haven't yet, but I'll grab those comments today for sure (I think I missed some of your earlier review comments)

-

16:24 <rharper> ok

-

16:25 <rharper> the tl;dr for that one is that you want this: ip -6 route list table all

-

16:25 <blackboxsw> ahh excellent, I was wondering why we were missing content for local routes etc

-

16:25 <rharper> right

-

16:25 <blackboxsw> thanks

-

16:25 <rharper> np

-

16:26 <blackboxsw> also, on our continuous integration front , powersj has put up a branch that I'd like to see us land with some ssh improvements

-

16:26 <blackboxsw> #link https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/342010

-

16:26 <powersj> :) yep

-

16:26 <blackboxsw> any other in-progress work worth noting?

-

16:27 <blackboxsw> Intereseted parties can always track our public trello board for a glimpse of what we are working on

-

16:27 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:27 <blackboxsw> #topic Office Hours (next ~30 minutes)

-

16:28 <blackboxsw> We'll all have eyes glued to the screen for the next 30 minutes for rants, feature discussion and bug work.

-

16:29 <blackboxsw> With that, the floor is open for any topics. Thanks for tuning in.

-

16:30 <blackboxsw> My day today will be Ubuntu SRU(stable release update)-related, so I'm getting on rharper's zfs branch now and they running a couple manual tests on ec2/azure/openstack

-

16:30 <rharper> +1

-

16:30 <rharper> oh, the ntp-spec update is ready for review and testing

-

16:31 <rharper> https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/339438

-

16:32 <blackboxsw> ahh +1 we want that in too

-

16:32 <blackboxsw> #link https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/339438

-

17:02 <blackboxsw> Alrighty, happy spring break all.

-

17:02 <blackboxsw> Next meeting will be two weeks from today.

-

17:03 <blackboxsw> powersj: rharper 4/16 look good for folks?

-

17:03 <powersj> +1 from me

-

17:03 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2018-04-16.html b/status-2018-04-16.html deleted file mode 100644 index 7393bcc..0000000 --- a/status-2018-04-16.html +++ /dev/null @@ -1,307 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Mon 16 April 2018 in status-meeting-minutes - - • 8 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

Recent-changes

-

The discussion about "Recent-changes" started at 16:04.

-

In-progresss Development

-

The discussion about "In-progresss Development" started at 16:11.

- -

Office Hours (next ~30 mins)

-

The discussion about "Office Hours (next ~30 mins)" started at 16:23.

- -

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (54)
  • -
  • smoser (17)
  • -
  • rharper (13)
  • -
  • mgerdts (10)
  • -
  • ubot5` (10)
  • -
  • cyphermox (3)
  • -
  • meetingology (3)
  • -
  • dpb1 (1)
  • -
-

Full Log

-

16:01 <blackboxsw> #startmeeting Cloud-init bi-weekly status meeting

-

16:01 <meetingology> Meeting started Mon Apr 16 16:01:49 2018 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:01 <meetingology>

-

16:01 <meetingology> Available commands: action commands idea info link nick

-

16:02 <rharper> o/

-

16:03 <blackboxsw> Hi folks, welcome to cloud-init's bi-weekly status meeting. Feel free to interject at any time or bring up branches/bugs/questions over the next 30-60 mins. We'll have a number of folks around to get eyes and/or keyboards onto any problems.

-

16:03 <dpb1> o/

-

16:04 <blackboxsw> As always we'll go through the following topics (feel free to suggest others): Recent-changes, In-progress Development, and ~30 mins Office Hours)

-

16:04 <blackboxsw> #topic Recent-changes

-

16:06 <blackboxsw> a quick rundown of the hi level changes landed:

-

16:06 <blackboxsw> Prune integration test artifacts

-

16:06 <blackboxsw> Add support for LXD 3.0, fix pylxd integration test dependency

-

16:06 <blackboxsw> Fix Ubuntu proposed integration test CI job

-

16:06 <blackboxsw> Fix ec2 validation of instance-data.json network info

-

16:06 <blackboxsw> Do not retry optional userdata on 404 (LP: #1702160)

-

16:06 <blackboxsw> Add explicit cloud-init package dependency on isc-dhcp-client (LP: #1759307)

-

16:06 <ubot5>` Launchpad bug 1702160 in cloud-init "OpenStack datasource should not retry user-data on 404" [Medium,Fix released] https://launchpad.net/bugs/1702160

-

16:06 <ubot5>` Launchpad bug 1759307 in cloud-init (Ubuntu) "missing dependency on isc-dhcp-client (dhclient)" [Medium,Fix released] https://launchpad.net/bugs/1759307

-

16:08 <blackboxsw> additionally from most recent commits we have:

-

16:08 <blackboxsw> tools: Fix make-tarball cli tool usage for development

-

16:08 <blackboxsw> renderer: support unicode in render_from_file.

-

16:08 <blackboxsw> Implement ntp client spec with auto support for distro selection

-

16:08 <blackboxsw> Apport: add Brightbox, IBM, LXD, and OpenTelekomCloud to list of clouds.

-

16:08 <blackboxsw> tests: fix ec2 integration network metadata validation

-

16:08 <blackboxsw> tests: fix integration tests to support lxd 3.0 release

-

16:08 <blackboxsw> correct documentation to match correct attribute name usage.

-

16:08 <blackboxsw> cc_resizefs, util: handle no /dev/zfs

-

16:09 <blackboxsw> Last week rharper found and fixed a regression in zfs resize behavior that was blocking our ubuntu SRU

-

16:09 <blackboxsw> We have uploaded those fixes, as well as rharper's ntp spec changes (which should incorporate a number of robjo's opensuse/sles needs too)

-

16:10 <blackboxsw> anything else notable that I'm missing gentlemen?

-

16:10 <blackboxsw> If not, I'll jump to in-progress development

-

16:11 <blackboxsw> #topic In-progresss Development

-

16:13 <blackboxsw> So, on the ubuntu side of the house we are about to approve the cloud-init 18.2 SRU (Stable release update) into xenial and artful. Just one more validation run and we should be good to see 18.2.4 on xenial, artful. Ubuntu Bionic is already a few commits beyond that.

-

16:13 <blackboxsw> On Ubuntu as well we are beating the drop to the Bionic LTS (Long term release) feature/bug freeze.

-

16:14 <blackboxsw> This week marks the last week for use to get fixes into Bioinic images before that release is cut.

-

16:14 <blackboxsw> so we'll be heads down on any Bionic-specific changes that need to get in.

-

16:14 <blackboxsw> Feel free to checkout our trello board @

-

16:14 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:15 <blackboxsw> we track all tasks we are working on in public view there so if there are any questions you can ping one of us here about our development efforts

-

16:17 <blackboxsw> additional tasks that are in flight: bash-autocompletion for cloud-init CLI (rhaper). dropping ifconfig and route in favor of 'ip' (bbsw), and moving openstack datasource to cloud-init's local stage

-

16:17 <blackboxsw> (smoser)

-

16:17 <blackboxsw> also a couple of bugs to fix such as #1570997

-

16:17 <blackboxsw> #link https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1759406

-

16:17 <ubot5>` Ubuntu bug 1759406 in cloud-init (Ubuntu) "sru cloud-init (17.2-35-gf576b2a2-0ubuntu1~16.04.1 update to 18.2-4-g05926e48-0ubuntu1)" [Medium,Confirmed]

-

16:17 <blackboxsw> oops paste fail:

-

16:17 <blackboxsw> #link https://bugs.launchpad.net/bugs/1570997

-

16:17 <ubot5>` Ubuntu bug 1570997 in ssh-import-id (Ubuntu Xenial) "fail if HOME environment variable is not set" [Low,Fix committed]

-

16:18 <blackboxsw> I think that about wraps in-progress development, anything else that should be noted smoser rharper ?

-

16:18 <rharper> I think you covered it

-

16:18 <smoser> ssh-import-id is not relally at all related to cloud-init

-

16:19 <smoser> thanks blackboxsw

-

16:19 <blackboxsw> oops grabbed the wrong one, was thinking about this card

-

16:19 <blackboxsw> #link https://trello.com/c/JVaXSfpo/749-eol-fix-for-ssh-file

-

16:19 <smoser> right.

-

16:21 <blackboxsw> also of note, in some of our SRU testing we found time-tracking gaps in cloud-init analyze tracking on Azure. rharper put of a logging tracker fix to avoid those tracking gaps

-

16:21 <blackboxsw> #link https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/343123

-

16:21 <smoser> i'll point out one thing i just finished up with...

-

16:22 <smoser> for testing ubuntu, the https://github.com/cloud-init/ubuntu-sru/ has 'get-proposed-cloudimg' and 'lxc-proposed-snapshot'

-

16:22 <smoser> which now work more like each other.l and can do more than just upgrade cloud-init.

-

16:23 <blackboxsw> thanks smoser. Great tools to quicken dev-test cycles and make cloud-init development easier. That wraps up what we've been up to. We can probably move to the open forum for any discussions folks want to have

-

16:23 <blackboxsw> #topic Office Hours (next ~30 mins)

-

16:24 <blackboxsw> We'll be hanging out here for anyone who wants more eyes on a review, feature discussions or bug triage....

-

16:28 <smoser> mgerdts: i'm poking at the branch i think i shoudl be able to get something.

-

16:29 <mgerdts> I'm working on a bunch of fixes for things that have turned up on bhyve with SmartOS. Since we are looking to transition from KVM to bhyve, we will need to provide updates at least as far back as xenial and probably trusty. Is the process for this any more complicated than get the fixes in master, then cherry-pick the fixes into branches?

-

16:29 <mgerdts> thanks @smoser

-

17:09 <rharper> mgerdts: we preferrer not to cherry; rather we release master back to xenial via our SRU (Stable Release Update) process; however, we spend a lot of effort to not modify existing behavior on prevlous SRU releases; so if the changes to support bhyve can be done in a compatible way (working with either) that'd be best; worst-case, we patch in release specific bahvior into the release branch.

-

17:13 <mgerdts> Pretty much everything that I've got queued up is fully compatible.

-

17:14 <mgerdts> https://bugs.launchpad.net/cloud-init/+bug/1667735 implements proper protocol negotiation over the serial port. The lack of this has caused problems with KVM at times too.

-

17:14 <ubot5>` Ubuntu bug 1667735 in cloud-init (Ubuntu Trusty) "cloud-init doesn't retry metadata lookups and hangs forever if metadata is down" [Medium,Confirmed]

-

17:15 <mgerdts> https://bugs.launchpad.net/cloud-init/+bug/1746605 adressess times when cloud-init and other software may be trying to use the metadata serial port at the same time. This is purely a bug fix.

-

17:15 <ubot5>` Ubuntu bug 1746605 in cloud-init "DataSourceSmartOS needs locking" [Medium,Confirmed]

-

17:15 <mgerdts> I hit it when rc.local and cloud-init were both trying to get metadata.

-

17:17 <mgerdts> https://bugs.launchpad.net/cloud-init/+bug/1763480 makes it so that cloud-init doesn't stack trace and exit when there is no customer_metadata. This is an unlikely case, but something that is hit when you are testing things that don't need ssh keys, etc.

-

17:17 <ubot5>` Ubuntu bug 1763480 in cloud-init "DataSourceSmartOS list() should always return a list" [Medium,Confirmed]

-

17:18 <mgerdts> https://bugs.launchpad.net/cloud-init/+bug/1763512 finishes off the partial implementation of sdc:routes support. Previously, we didn't publish the required information to VMs, so it is fair to consider this a new feature.

-

17:18 <ubot5>` Ubuntu bug 1763512 in cloud-init "DataSourceSmartOS ignores sdc:routes" [Medium,Confirmed]

-

17:19 <mgerdts> https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1763511 is probably the most incompatible change. New ephemeral disks will get ext4 instead of ext3, which is needed for larger disks that seem to be getting more common.

-

17:19 <ubot5>` Ubuntu bug 1763511 in cloud-init (Ubuntu) "DataSourceSmartOS should default to ext4" [Undecided,New]

-

17:21 <mgerdts> I think that's all that I have in the works right now. Do any of these sound like they would be problematic as far back as Xenial?

-

17:29 <rharper> new features are OK ,bug fixes are fine as well; I think that different filesystem is somewhat tricky

-

17:30 <smoser> i think i'm generally ok with the different filesystem.

-

17:31 <smoser> if the reason is that simply ext3 can't handle super-big

-

17:31 <rharper> yeah, that doesn't seem so user-visible w.r.t configuration;

-

17:32 <smoser> we could ensure being more backward compat if we checked the size of the disk and made an ext4 if >` that-size

-

17:32 <smoser> then there'd less issue

-

17:32 <smoser> but more complication and future we'd be stuck with that

-

17:32 <rharper> yeah, it wouldn't have worked on ext3 then it would be fine to use ext4

-

17:32 <smoser> so i'd rather really just bite the bulleet

-

17:32 <rharper> it could be a metadata flag that the Datasource looks for

-

17:32 <smoser> rather than describing to pepole forever "well, if your disk is `< X you'll get ext3 otherwise ext4"

-

17:49 <blackboxsw> rharper: got time for a netplan global dns hangout?

-

17:49 <rharper> y

-

17:49 <blackboxsw> I want to make sure I'm reading the tea leaves right

-

17:52 <smoser> mgerdts: http://paste.ubuntu.com/p/5qdtFzY8w7/

-

17:52 <blackboxsw> ok rharper I'm in cloud-init hangout

-

17:52 <smoser> that makes tests pass. and i think the changes to the code path are right

-

17:52 <rharper> ok

-

17:52 <rharper> brt

-

17:54 <smoser> it is still hacked in a sense that the response only deals with fp.read(1) rather than possibly anything that read more than 1.

-

17:56 <cyphermox> blackboxsw: rharper: what's this about netplan global dns?

-

17:57 <rharper> cyphermox: converting network v1 syntax from maas into something that works with netplan which doesn't have "dns" unbound to any interfaces

-

17:57 <cyphermox> ok

-

17:57 <rharper> maas I believe has fixed this for 2.4.x

-

17:58 <rharper> they no longer will emit the type: nameserver but legacy maas would have that, so we've a branch that stuffs them in reasonable places under defined interfaces which don't already have DNS values

-

17:58 <blackboxsw> cyphermox: just SRU validation w.r.t. https://bugs.launchpad.net/cloud-init/+bug/1750884

-

17:59 <ubot5>` Ubuntu bug 1750884 in cloud-init "[2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution" [Medium,Fix released]

-

17:59 <cyphermox> all good

-

18:11 <blackboxsw> ooops, and /me forgot the end the epic meeting

-

18:11 <blackboxsw> thx rharper for the chat

-

18:11 <blackboxsw> #endmeetiung

-

18:11 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2018-04-30.html b/status-2018-04-30.html deleted file mode 100644 index 3b01975..0000000 --- a/status-2018-04-30.html +++ /dev/null @@ -1,370 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Mon 30 April 2018 in status-meeting-minutes - - • 12 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:07.

-

#cloud-init Reviews: http://bit.ly/ci-reviews | Meeting minutes: https://goo.gl/mrHdaj | Next status meeting: Monday 5/14 16:00 UTC | cloud-init 18.2 released (03/28/2018)

-

The discussion about "#cloud-init Reviews: http://bit.ly/ci-reviews | Meeting minutes: https://goo.gl/mrHdaj | Next status meeting: Monday 5/14 16:00 UTC | cloud-init 18.2 released (03/28/2018)" started at 16:08.

- -

In-progresss Development

-

The discussion about "In-progresss Development" started at 16:21.

- -

Office Hours (next ~30 mins)

-

The discussion about "Office Hours (next ~30 mins)" started at 16:31.

- -

Vote results

-

Action items, by person

- -

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (113)
  • -
  • mgerdts (21)
  • -
  • ubot5 (12)
  • -
  • akik (5)
  • -
  • stanguturi (4)
  • -
  • meetingology (4)
  • -
  • robjo (3)
  • -
-

Full Log

-

16:04 <blackboxsw> #startmeeting Cloud-init bi-weekly status meeting

-

16:04 <meetingology> Meeting started Mon Apr 30 16:04:15 2018 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:04 <meetingology>

-

16:04 <meetingology> Available commands: action commands idea info link nick

-

16:04 <blackboxsw> hi folks, sorry for the mis-representation of when our cloud-init status meeting date. It's time for another episode/update of the happenings in cloud-init.

-

16:05 <blackboxsw> Next meeting will be in two weeks: May 7th

-

16:05 <blackboxsw> at 16:00 UTC

-

16:06 <blackboxsw> The last couple weeks on the upstream side of the house has been a big push to get testing and stability into master for the Ubuntu Bionic release freeze

-

16:06 <blackboxsw> ... I'd better start with the topic

-

16:07 <blackboxsw> #topic Recent Changes

-

16:07 <blackboxsw> The last couple weeks on the upstream side of the house has been a big push to get testing and stability into master for the Ubuntu Bionic release freeze.

-

16:07 <robjo> May 7th would be 1 week from today that should be May 14th

-

16:07 <blackboxsw> robjo: gah, I did it again. Thank you... glad someone's listening. Next cloud-init status meeting Monday May 14th 16:00 UTC

-

16:08 <blackboxsw> #topic #cloud-init Reviews: http://bit.ly/ci-reviews | Meeting minutes: https://goo.gl/mrHdaj | Next status meeting: Monday 5/14 16:00 UTC | cloud-init 18.2 released (03/28/2018)

-

16:08 <blackboxsw> ok topic agrees in channel now, so I don't botch it at the end of meeting

-

16:09 <blackboxsw> Along with a blitz for stability in Bionic the following changes have been shepherded into tip of master

-

16:09 <blackboxsw> - Add reporting events and log_time around early source of blocking time

-

16:09 <blackboxsw> [Ryan Harper]

-

16:09 <blackboxsw> - IBMCloud: recognize provisioning environment during debug boots.

-

16:09 <blackboxsw> (LP: #1767166)

-

16:09 <blackboxsw> - net: detect unstable network names and trigger a settle if needed

-

16:09 <blackboxsw> [Ryan Harper] (LP: #1766287)

-

16:09 <blackboxsw> - IBMCloud: improve documentation in datasource.

-

16:09 <ubot5> Launchpad bug 1767166 in cloud-init (Ubuntu) "IBMCloud datasource does not recognize provisioning in debug mode." [Medium,Confirmed] https://launchpad.net/bugs/1767166

-

16:09 <blackboxsw> - sysconfig: dhcp6 subnet type should not imply dhcpv4 [Vitaly Kuznetsov]

-

16:09 <blackboxsw> - packages/debian/control.in: add missing dependency on iproute2.

-

16:09 <ubot5> Launchpad bug 1766287 in cloud-init (Ubuntu) "18.04 minimal images on GCE intermittently fail to set up networking " [Undecided,In progress] https://launchpad.net/bugs/1766287

-

16:09 <blackboxsw> (LP: #1766711)

-

16:09 <blackboxsw> - DataSourceSmartOS: add locking of serial device.

-

16:09 <blackboxsw> [Mike Gerdts] (LP: #1746605)

-

16:09 <blackboxsw> - DataSourceSmartOS: sdc:hostname is ignored [Mike Gerdts] (LP: #1765085)

-

16:09 <ubot5> Launchpad bug 1766711 in cloud-init (Ubuntu Bionic) "cloud-init missing dependency on iproute2" [Medium,Fix committed] https://launchpad.net/bugs/1766711

-

16:09 <blackboxsw> - DataSourceSmartOS: list() should always return a list

-

16:09 <blackboxsw> [Mike Gerdts] (LP: #1763480)

-

16:09 <ubot5> Launchpad bug 1746605 in cloud-init "DataSourceSmartOS needs locking" [Medium,Fix committed] https://launchpad.net/bugs/1746605

-

16:09 <blackboxsw> - schema: in validation, raise ImportError if strict but no jsonschema.

-

16:09 <blackboxsw> - set_passwords: Add newline to end of sshd config, only restart if

-

16:09 <blackboxsw> updated. (LP: #1677205)

-

16:09 <ubot5> Launchpad bug 1765085 in cloud-init "DataSourceSmartOS ignores sdc:hostname" [Medium,Fix committed] https://launchpad.net/bugs/1765085

-

16:09 <blackboxsw> - pylint: pay attention to unused variable warnings.

-

16:09 <blackboxsw> - doc: Add documentation for AliYun datasource. [Junjie Wang]

-

16:09 <blackboxsw> - Schema: do not warn on duplicate items in commands. (LP: #1764264)

-

16:09 <ubot5> Launchpad bug 1763480 in cloud-init "DataSourceSmartOS list() should always return a list" [Medium,Fix committed] https://launchpad.net/bugs/1763480

-

16:09 <ubot5> Launchpad bug 1677205 in cloud-init "cloud-init eats final EOL of sshd_config" [Medium,Fix committed] https://launchpad.net/bugs/1677205

-

16:09 <ubot5> Launchpad bug 1764264 in juju 2.3 "bionic cloud-init 18.2 WARNING Juju's 'runcmd' stanza" [High,Triaged] https://launchpad.net/bugs/1764264

-

16:10 <blackboxsw> the general theme has been: new IBMCloud datasource support for cloud-init, SmartOS datasource work by mgerdts, and some json schema improvements

-

16:12 <blackboxsw> so background on IBM, is that their support used to be ConfigDrive based datasource only, but there is now some additional support for different IBM boot/provisioning stages, hence a new datasource that can support different boot modew

-

16:12 <blackboxsw> *boot modes

-

16:14 <blackboxsw> over the last two weeks we've landed an SRU into xenial and artful: 18.2-4-g05926e48-0ubuntu1~16.04.1 and bionic sits at 18.2-14-g6d48d265-0ubuntu1

-

16:15 <mgerdts> On the SmartOS side, my changes are driven by our adoption of bhyve (moving away from kvm/qemu). qemu provides a dhcp server VMs could fall back to if could-init was missing or misbehaving. bhyve doesn't have that, so I've been working on getting cloud-init to be more stable with the bhyve serial metadata service.

-

16:15 <blackboxsw> Also, to our continuous integration on jenkins we now have an additional test for proposed packages in ubuntu for the bionic release to make sure ubuntu doesn't break across pending upgrades

-

16:15 <blackboxsw> #link https://jenkins.ubuntu.com/server/job/cloud-init-integration-proposed-b/

-

16:16 <blackboxsw> that integration tests hits the suite of platforms lxd, kvm and ec2

-

16:16 <blackboxsw> excellent mgerdts, and thanks for the blitz on these branches

-

16:17 <blackboxsw> looks like there are a few still in our review queue that we'll be able to get through once the dust settles on the bionic release (which should be this week)

-

16:17 <blackboxsw> #link https://code.launchpad.net/~cloud-init-dev/cloud-init/+git/cloud-init/+ref/master/+activereviews

-

16:19 <mgerdts> Is now the right time to discuss bug 1765801, or is that later?

-

16:19 <ubot5> bug 1765801 in cloud-init "network should be optionally reconfigured on every boot" [Undecided,Confirmed] https://launchpad.net/bugs/1765801

-

16:20 <blackboxsw> I think over the last 2 weeks there have been a couple of requests in channel for how someone goes about getting newer cloud init into RHEL7, if anyone on the line today knows the contact point or process for that it'd be helpful. larsks doesn't seem to be around

-

16:20 <blackboxsw> mgerdts: probably in about 10 mins. thanks for brining it up

-

16:20 <blackboxsw> hopefully less.

-

16:20 <blackboxsw> ok I think that's it for recent changes, next topic (in-progress dev, then office hours (and bug discussion))

-

16:21 <blackboxsw> #topic In-progresss Development

-

16:21 <blackboxsw> We'll make this one short:

-

16:22 <blackboxsw> for ubuntu : bionic just went feature freeze last week, our team has a couple of IBM-related cheanges that we are pulling together for a quick SRU into xenial/artful to handle upgrade path from configdrive ->` IBMCloud that we are working on the beginning of this week

-

16:22 <blackboxsw> we are also trying to wrap up validation of a Bionic SRU per the following bug

-

16:22 <blackboxsw> #link https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1767412

-

16:22 <ubot5> Launchpad bug 1767412 in cloud-init (Ubuntu Bionic) "SRU cloud-init 18.2-27-g6ef92c98-0ubuntu1" [Medium,Fix committed]

-

16:23 <blackboxsw> which grabs a number of the updates I listed in the last topic

-

16:23 <blackboxsw> since Ubuntu tends to sync all changes from tip into each release stream

-

16:23 <mgerdts> Is there any chance the SmartOS changes can piggy back on that IBM SRU

-

16:24 <mgerdts> asked too soon - I see they are mentioned in that bug.

-

16:25 <blackboxsw> mgerdts: no worries. good ask. probably not for this IBM SRU into xenial/artful which is going to be an exception to our update rule and only be a single cherry pick, but planning a folllowup SRU in about 2 weeks which will pull all changes from tip into artful/xenial/bionic/chunky releases

-

16:25 <mgerdts> ok

-

16:25 <blackboxsw> the cherry pick is to fasttrack it for IBM into xenial with minimal risk.

-

16:25 <blackboxsw> and we want to pull in all your changes if we can (and perform additional validation)

-

16:25 <blackboxsw> so the next SRU is our target

-

16:26 <blackboxsw> Also inprogress is some more Azure work on pre-provisioning that should land shortly:

-

16:26 <blackboxsw> #link https://code.launchpad.net/~jocha/cloud-init/+git/cloud-init/+merge/344192

-

16:27 <blackboxsw> as well as some builddeb fixes and network configuration printout fixes from smoser

-

16:29 <blackboxsw> smoser and rharper also worked out some issues on specific google regions where cloud-init was getting hit by a race condition. Cloud-init started up before the kernel/udev was able to rename network devices to stable names like ens4 etc, so cloud-init's network configuration written ended up breaking because it represented devices like eth0 etc.

-

16:29 <blackboxsw> there are a couple of branches in flight to fix this issue:

-

16:29 <blackboxsw> #link https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/344181

-

16:30 <blackboxsw> #link https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/344198

-

16:30 <blackboxsw> ok I think that's it for in-progress work. So we'll head to office hours so we can chat bugs, branches reviews etc

-

16:31 <blackboxsw> #topic Office Hours (next ~30 mins)

-

16:31 <blackboxsw> We'll be hanging out here for anyone who wants more eyes on a review, feature discussions or bug triage....

-

16:32 <blackboxsw> well, some of us will be :) a couple of us are at a feature planning conference for the week.

-

16:33 <mgerdts> In https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712 smoser said that he was concerned about how this would interact with eventual network hotplug

-

16:34 <mgerdts> There doesn't seem to be a timeline for network hotplug and the lack of network autoreconfig on reboot is has popped up a couple times in the past week. This is just with a couple early adopters and internal users.

-

16:34 <blackboxsw> #link https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712

-

16:35 <blackboxsw> just to track it in the meeting

-

16:35 <mgerdts> So coming up with some mechanism to make this work soon is pretty important to us.

-

16:35 <mgerdts> gotcha, will be sure to do that in the future.

-

16:35 * blackboxsw reads up on that link

-

16:35 <blackboxsw> no worries, I'm pedantic :)

-

16:36 <mgerdts> That's how you got chosen to run the meeting, I suppose. :)

-

16:36 <blackboxsw> yeah network hotplug will have a long tail as far as feature develpment (agreed). I believe it's on our charter for this next quarter. but that's what is being discussed this week

-

16:37 <blackboxsw> heh on meeting comment ;) too true

-

16:39 <blackboxsw> so mgerdts your branch allows metadata to set maintain_network to allow cloud-init to control network configuration each reboot with a True value

-

16:39 <blackboxsw> ?

-

16:39 <mgerdts> yes

-

16:39 <mgerdts> if it's not set to true in our metadata, the traditional behavior stays.

-

16:40 <mgerdts> That is, in the default path, any customization that someone does in the guest will not get whacked.

-

16:41 <robjo> cloud-netconfig handles hotplug https://github.com/SUSE/Enceladus/tree/master/cloud-netconfig contributions for other distros welcome

-

16:42 <blackboxsw> nice reference robjo

-

16:42 <blackboxsw> #link https://github.com/SUSE/Enceladus/tree/master/cloud-netconfig

-

16:43 <robjo> We currently have no GCE specific information but that is easy enough to add. The GCE guest environment handles this and we use the GCE guest environment code in our images in GCE

-

16:43 <blackboxsw> mgerdts: so can a user turn off that feature on an instance once they've already deployed, or is it create-time only

-

16:43 <mgerdts> It can be flipped at any time, in the current implementation.

-

16:44 <mgerdts> current implementation is only in a development branch

-

16:47 <blackboxsw> mgerdts: the only things I can see being an issue with the maintain network in cloud-init is that we are adding the cost of another function call && metdata dict parse to look for a signal about maintaining the network. I agree that cloud-init having granularity between is_new_instance vs just re-do network, is something that cloud-init should have.

-

16:48 <blackboxsw> we probably need to discuss this too with rharper about what short-term vision we can get to while we await our network hotplug support in cloud-init proper

-

16:49 <blackboxsw> I'd tend to agree that waiting on fully baked hotplug solution is probably too long in this case

-

16:49 <blackboxsw> as that runway will be at least 2 months I'd think

-

16:50 <blackboxsw> ok, I'll take an action item to resolve this if we can by next meeting

-

16:50 <mgerdts> Not only that, but support for it will likely require changes in the host as well. We tend not to do host updates very often, so it could be a year or more after the feature is available in images before it will be useful.

-

16:51 <blackboxsw> #action blackboxsw to have discussions w/ team on datasource maintaining network on each reboot per https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712

-

16:51 * meetingology blackboxsw to have discussions w/ team on datasource maintaining network on each reboot per https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712

-

16:51 <mgerdts> thanks

-

16:51 <blackboxsw> good topic.

-

16:52 <mgerdts> Is there another place that is good to catch up with larsks or other people that can offer guidance on for redhat/centos?

-

16:52 <blackboxsw> let's see, anything else folks want to chat about? stagnant reviews, bugs of interest etc?

-

16:53 * blackboxsw looks at the last cloud-init community summit attendees list to see if rhel folks have another contacts that was supposed to replace larsks

-

16:53 <stanguturi> Chad, Is it possible that someone from cloud-init team can take a look at https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538

-

16:53 <ubot5> Launchpad bug 1766538 in cloud-init (Ubuntu) "network customization with cloud-init does not work on Ubuntu18.04 Beta2 Server" [Undecided,Confirmed]

-

16:55 <blackboxsw> mgerts, ryan mccabe is a potential contact too, looks like he's not here either today.

-

16:56 <mgerdts> ok, thanks

-

16:56 <blackboxsw> hrm, yeah not certain what mechanism is used to get cloud-init updated into RedHat mgerdts. Maybe filing a redhat bug about the request

-

16:57 <blackboxsw> mgerdts: https://bugzilla.redhat.com/ maybe

-

16:58 <blackboxsw> stanguturi: yes we can, we are trying to sort and understand any bugs against Bionic that we can

-

16:58 <mgerdts> ok, I can try that.

-

16:58 <blackboxsw> #link https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538

-

16:58 <ubot5> Launchpad bug 1766538 in cloud-init (Ubuntu) "network customization with cloud-init does not work on Ubuntu18.04 Beta2 Server" [Undecided,Confirmed]

-

16:58 <stanguturi> blackboxsw: Thanks

-

17:00 <blackboxsw> stanguturi: ok, so this is netplan + cloud-init related right?

-

17:00 <stanguturi> blackboxsw: Yes.

-

17:01 <akik> what does network hotplug mean in cloud-init context?

-

17:02 * blackboxsw tries to remember what vmware datasource does, (like writing files direct to network /etc/network/interfaces.d)

-

17:02 <blackboxsw> akik: https://hackmd.io/M1Tae41PQBC7a9qMsurTJw?both is a shared document for comment on hotplug in cloud-init

-

17:02 <blackboxsw> #link https://hackmd.io/M1Tae41PQBC7a9qMsurTJw?both

-

17:03 * blackboxsw looks to see if there was a better doc hrm

-

17:03 <stanguturi> blackboxsw: Oh. But in the case of netplan, why does cloud-init remembers?

-

17:04 <akik> blackboxsw: does it mean that cloud-init stays running, waiting for new network interfaces to appear?

-

17:04 <blackboxsw> akik: right, it would mean that you wouldn't have to reboot cloud-init if devices get added at a later time (post-boot)

-

17:05 <blackboxsw> cloud-init would listen to some sort of event channel and react, re-write, and apply network config to add new devices

-

17:06 <akik> would it do the same thing as you could do with ansible or puppet? sorry i'm trying to understand why you would do it with cloud-init

-

17:08 <blackboxsw> akik: you would try to do it with cloud-init if you didn't want to rely on additional configuration management solutions if the only thing you needed was network config to reflect reality (not full system configuration and system automation)

-

17:09 * blackboxsw has more puppet/chef background than ansible.

-

17:09 <blackboxsw> cloud-init does currently detect and write network configuration based on what the user/cloud-metadata tell us is the proper config for the instance

-

17:10 <akik> i only thought of cloud-init to do the initial configuration

-

17:10 <blackboxsw> so it would follow that if the metadata could dynamically tell the instance that network config has changed, cloud-init should probably try to react to that to fix the config to match the updated network configuration

-

17:11 <blackboxsw> akik: correct. cloud-init current only handle initial boot config and leaves the rest up whatever mechanism someone uses to update detailed config after that boot

-

17:11 <akik> ok thanks

-

17:12 <blackboxsw> akik: and we'd make that feature configurable (handle hotplug:True/False) so if users have other services handling hotplug cloud-init wouldn't collide

-

17:13 <blackboxsw> ok I think we're hitting the end of office hours. please feel free to continue discussion, we all poke around here throughout the day as our primary means of communication

-

17:13 <blackboxsw> thanks robjo akik stanguturi and mgerdts for the lively discussion

-

17:13 <blackboxsw> stanguturi: I'll dig up more info on that bug today

-

17:13 <mgerdts> thank you

-

17:13 <blackboxsw> as always notes will be here

-

17:14 <blackboxsw> #link https://cloud-init.github.io/

-

17:14 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2018-05-14.html b/status-2018-05-14.html deleted file mode 100644 index e231738..0000000 --- a/status-2018-05-14.html +++ /dev/null @@ -1,308 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Mon 14 May 2018 in status-meeting-minutes - - • 7 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:09.

- -

In-progress Development

-

The discussion about "In-progress Development" started at 16:19.

-

Office Hours (next ~30 mins)

-

The discussion about "Office Hours (next ~30 mins)" started at 16:29.

- -

Vote results

-

Action items, by person

-
    -
  • blackboxsw
  • -
  • blackboxsw review distro dection and empty modules list
  • -
  • blackboxsw carryover network hotplug vs network maintenance on reboot-only
  • -
  • rharper
  • -
  • robjo review existing chrony support in master per rharper's work
  • -
  • robjo
  • -
  • robjo review existing chrony support in master per rharper's work
  • -
-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (73)
  • -
  • robjo (14)
  • -
  • ubot5 (9)
  • -
  • meetingology (6)
  • -
  • stanguturi (2)
  • -
  • rharper (1)
  • -
-

Full Log

-

16:05 <blackboxsw> #startmeeting Cloud-init bi-weekly status meeting

-

16:05 <meetingology> Meeting started Mon May 14 16:05:28 2018 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:05 <meetingology>

-

16:05 <meetingology> Available commands: action commands idea info link nick

-

16:08 <blackboxsw> welcome folks to another cloud-init status meeting. This forum is used to communicate the recent changes, current development efforts and host open office hours to help get quick discussion on bugs, branches or features of interest to anyone developing (or consuming) cloud-init.

-

16:09 <blackboxsw> We'll go through a couple of topics as usual (Recent changes, In-progress Development, Office Hours), if there are any additional topics needed just let me know.

-

16:09 <blackboxsw> #topic Recent Changes

-

16:10 <blackboxsw> We track our upstream work publicly on trello. Feel free to participate or ask questions about any feature work that is seen up there if there are concerns.

-

16:11 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:11 <blackboxsw> We have landed the following work items: beware the paste :)

-

16:11 <blackboxsw> * Completed release of 18.2 to Ubuntu Bionic, Artful, and Xenial

-

16:11 <blackboxsw> * Implement bash completion script for cloud-init command line

-

16:11 <blackboxsw> * Improved Softlayer datasource documentation

-

16:11 <blackboxsw> * net: Depend on iproute2's ip instead of net-tools ifconfig or route

-

16:11 <blackboxsw> * Accept-ra unset by default (LP: #1732002)

-

16:11 <blackboxsw> * Command collect-logs will only include most recent boot's journal (LP: #1766335)

-

16:11 <blackboxsw> * FreeBSD: Invoke growfs on ufs filesystems such that it does not prompt. (LP: #1404745)

-

16:11 <ubot5> Launchpad bug 1732002 in systemd (Ubuntu) "cloud images in lxc get ipv6 address" [Undecided,New] https://launchpad.net/bugs/1732002

-

16:11 <blackboxsw> * Azure: poll_imds fixes to only report 'ready' state once during pre-provisioning from Joshua Chan (LP: #1765214)

-

16:11 <blackboxsw> * DataSourceSmartOS: fix hang when metadata service is down from Mike Gerdts (LP: #1667735)

-

16:12 <ubot5> Launchpad bug 1766335 in cloud-init "Running cloud-init collect-logs inside a chroot is not possible" [Medium,Fix committed] https://launchpad.net/bugs/1766335

-

16:12 <blackboxsw> * DataSourceSmartOS: change default fs on ephemeral disk from ext3 to ext4 from Mike Gerdts (LP: #1763511)

-

16:12 <blackboxsw> * pycodestyle: Fix invalid escape sequences in string literals

-

16:12 <ubot5> Launchpad bug 1404745 in cloud-init "cloud-init's growfs/resize fails with gpart dependency on FreeBSD" [Undecided,Fix committed] https://launchpad.net/bugs/1404745

-

16:12 <ubot5> Launchpad bug 1765214 in cloud-init "Multiple success messages sent to Azure Fabric if reboot occurs during pre-provisioning" [Medium,Fix committed] https://launchpad.net/bugs/1765214

-

16:12 <ubot5> Launchpad bug 1667735 in cloud-init (Ubuntu Trusty) "cloud-init doesn't retry metadata lookups and hangs forever if metadata is down" [Medium,Confirmed] https://launchpad.net/bugs/1667735

-

16:12 <ubot5> Launchpad bug 1763511 in cloud-init (Ubuntu) "DataSourceSmartOS should default to ext4" [Medium,Fix released] https://launchpad.net/bugs/1763511

-

16:14 <blackboxsw> A big thank you to community involvement again. Thanks jocha(Microsoft) and mgerdts(Joyent) for the recent branch work supporting Azure and SmartOS clouds respectively

-

16:16 <blackboxsw> We also went through another round of StableReleaseUpdates for Ubuntu on Xenial and Artful to pull in IBMCloud platform fixes. putting Xenial and artful at 18.2-4-g05926e48-0ubuntu~16.04.2 | ~17.10.2

-

16:18 <blackboxsw> I think that's about it for completed development...

-

16:19 <blackboxsw> #topic In-progress Development

-

16:21 <blackboxsw> There are a couple of items being worked actively at the moment:

-

16:22 <blackboxsw> * SRU of cloud-init tip into bionic (should land today or tomorrow) 18.2-27-g6ef92c98-0ubuntu1~18.04.1

-

16:23 <blackboxsw> * SmartOs datasource detection improvements

-

16:23 <blackboxsw> * Moving OpenStack datasource to get detected earlier at 'local' stange instead of 'network' stage using ephemeral dhcp client

-

16:26 <blackboxsw> * read_file_or_url fixes returing text content in all cases

-

16:26 <blackboxsw> * various upstream bug fixes

-

16:27 <blackboxsw> * powersj: is also investigating a move to a centralized library for our cloud testing.

-

16:29 <robjo> blackboxsw: w.r.t. Depend on iproute2's ip instead of net-tools ifconfig or route was this a merge of iproute2tools branch? I don't recall seeing a merge notification but am way behind in e-mail

-

16:29 <blackboxsw> think that about captures what upstream is working on. I think we can transition to office hours for ~30 mins for anyone to bring up ideas of interest

-

16:29 <blackboxsw> #topic Office Hours (next ~30 mins)

-

16:29 <blackboxsw> hi robjo, checking status there

-

16:30 <blackboxsw> I know we landed one branch on that topic

-

16:31 <blackboxsw> robjo: so we had a couple branches to packaging dependencies in ubuntu to call out iproute2 specifically as a hard package dependency.

-

16:32 <blackboxsw> robjo: and the code changes (which took in some of your branch content and review comments) landed in rev 6d48d265a0548a2dc23e587f2a335d4e38e8db90

-

16:32 <robjo> OK, so I can delete my branch

-

16:32 <blackboxsw> https://pastebin.ubuntu.com/p/266CyDt9gD/

-

16:34 <robjo> thanks, so we'll get that in 18.3?

-

16:34 <blackboxsw> robjo: yes I think i marked you co-author on that branch and pulled in all your changes to cloudinit/config/cc_disable_ec2_metadata.py

-

16:34 <blackboxsw> 2

-

16:34 <blackboxsw> thanks again for that, sorry for the back and forth as I hadn't seen your original branch.

-

16:35 <blackboxsw> robjo: definitely in 18.3

-

16:35 <blackboxsw> it landed a week or two after the 18.2 cut.

-

16:35 <stanguturi> @blackboxsw, Can someone please provide inputs for the bug https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538 One of our team members has uploaded the necessary log files to the bug.

-

16:35 <ubot5> Ubuntu bug 1766538 in cloud-init (Ubuntu) "network customization with cloud-init does not work on Ubuntu18.04 Beta2 Server" [Undecided,New]

-

16:38 <robjo> OK, so lets also revisit some of the other stuff I have floating about as I just did the 18.2 package for openSUSE and SLES and noticed that I am once again scarring a lot of patches :(

-

16:39 <robjo> blackboxsw: https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/emptyStageOK should be back in your court, did you get notification?

-

16:40 <robjo> blackboxsw: https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/noLnxDistro pending since January this may have some merge conflicts now as I had to fiddle quite a bit with the patch in my package

-

16:41 <blackboxsw> stanguturi: looking

-

16:41 <robjo> I think rharper is working on a different approach to https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/chrony when can we expect that?

-

16:42 <robjo> and does rharper account for the fact that ntp has a different service name on different distributions?

-

16:43 <blackboxsw> #link https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538

-

16:43 <ubot5> Ubuntu bug 1766538 in cloud-init (Ubuntu) "network customization with cloud-init does not work on Ubuntu18.04 Beta2 Server" [Undecided,New]

-

16:43 <blackboxsw> #link https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/emptyStageOK

-

16:43 <blackboxsw> ahh robjo hadn't, was on vacation Friday, will grab that/close out today

-

16:43 <blackboxsw> #link https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/noLnxDistro

-

16:44 <rharper> robjo: re: ntp/chrony, that's landed, including service names for different distros; I pulled unittests and scenarios from your branch; please look over master and see if we're missing anything from your branch w.r.t use-case/scenario

-

16:45 <robjo> rharper: OK, if it's landed I can at least throw my branch away, and yes, will take a look at master, I take it this will be another in 18.3 item?

-

16:46 <blackboxsw> stanguturi: ok thanks for the logs on that bug, looks like network config parsing is falling over and OVF datasource isn't being detected https://pastebin.ubuntu.com/p/qVJxDJWZRV/

-

16:47 <stanguturi> @blackboxsw, Oh . Thanks. Will check with him about the test setup and update the bug. Thanks.

-

16:48 <blackboxsw> updated the bug with a comment there

-

16:48 <blackboxsw> thanks stanguturi

-

16:50 <blackboxsw> robjo: correct as well for ntp/chrony, we held off landing it in 18.2 because of risk

-

16:50 <blackboxsw> it was one of the first branches landed after the cut

-

16:51 <robjo> ok, leaves the https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+ref/noLnxDistro implementation of distro detection as things I'd like to get resolved, others to be addressed maybe in 2 weeks ;)

-

16:51 <blackboxsw> ok noLnxDistro.... I'm updating the commit comment robjo to the trailing LP: #<bug_id>

-

16:51 <blackboxsw> claiming a review slot on that now

-

16:53 <blackboxsw> good unit test coverage, thanks for that

-

16:54 <robjo> np

-

16:55 <blackboxsw> ok this can be reviewed today, not sure if why we don't already have a get_linux_distro utility somewhere, but I'll poke around today for context

-

16:55 <blackboxsw> ahh ahh, thanks for the bug robjo ok

-

16:56 <robjo> the context is that the Python implementation is going away and has been deprecated

-

16:56 <blackboxsw> #link https://bugs.launchpad.net/cloud-init/+bug/1745235

-

16:56 <ubot5> Ubuntu bug 1745235 in cloud-init "distribution detection" [Undecided,New]

-

16:56 <blackboxsw> thanks again

-

16:56 <blackboxsw> changing that status and will help you get that landed

-

16:56 <blackboxsw> good one

-

16:58 <robjo> OK, blackboxsw is on the hook for two things this week ;) distro detection and the empty modules list

-

16:58 <blackboxsw> #action blackboxsw review distro dection and empty modules list

-

16:58 * meetingology blackboxsw review distro dection and empty modules list

-

16:58 * robjo on the hook to look at chrony support in master and report back to rharper

-

16:58 <blackboxsw> #action robjo review existing chrony support in master per rharper's work

-

16:58 * meetingology robjo review existing chrony support in master per rharper's work

-

16:59 <blackboxsw> official now :)

-

16:59 <blackboxsw> now if I only reviewed previous meeting's action items.... checking now

-

17:00 <blackboxsw> 16:51 <blackboxsw> #action blackboxsw to have discussions w/ team on datasource maintaining network on each reboot per https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712

-

17:01 <blackboxsw> ok per last meeting, we have held a couple of discussions on hotplug vs. maintaining network only on reboot. on first blush it looks like we'd need to have these mutually exclusive, but we are just started to iron our what we want to do for our initial hotplug support in cloud-init and have to have a followup discussion about how to support both approaches

-

17:02 <blackboxsw> #action blackboxsw carryover network hotplug vs network maintenance on reboot-only

-

17:02 * meetingology blackboxsw carryover network hotplug vs network maintenance on reboot-only

-

17:02 <blackboxsw> well that was the only action item from last meeting looks like

-

17:02 <blackboxsw> ok I think that wraps up today's meeting.

-

17:02 <blackboxsw> any other parting shots folks?

-

17:03 <blackboxsw> Thanks again for your time. It's always a pleasure.

-

17:03 <blackboxsw> Next meeting two weeks, same bat time...

-

17:03 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2018-05-29.html b/status-2018-05-29.html deleted file mode 100644 index 9344650..0000000 --- a/status-2018-05-29.html +++ /dev/null @@ -1,362 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Tue 29 May 2018 in status-meeting-minutes - - • 10 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:09.

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:13.

-

In-progress Development

-

The discussion about "In-progress Development" started at 16:19.

- -

Office Hours (next ~30 mins)

-

The discussion about "Office Hours (next ~30 mins)" started at 16:34.

- -

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (118)
  • -
  • dmbaturin (20)
  • -
  • powersj (6)
  • -
  • dpb1 (5)
  • -
  • robjo (5)
  • -
  • ubot5 (4)
  • -
  • smoser (4)
  • -
  • meetingology (3)
  • -
  • rharper (2)
  • -
-

Full Log

-

16:05 <blackboxsw> #startmeeting Cloud-init bi-weekly status meeting

-

16:05 <meetingology> Meeting started Tue May 29 16:05:51 2018 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:05 <meetingology>

-

16:05 <meetingology> Available commands: action commands idea info link nick

-

16:06 <dpb1> dmbaturin: there will be a time for open questions in this meeting in just a few minutes. :)

-

16:06 <dpb1> so you will have the right people around

-

16:06 <blackboxsw> welcome folks to another cloud-init community status meeting, today's meeting delayed by one day due to US holiday. Next meeting will be June 11th. same time

-

16:07 <blackboxsw> I've added an actions topic to this meeting so we can wrap up or carry over any actions discussed last time

-

16:08 <blackboxsw> the topics will be Previous Actions, Recent Changes, In-progress Development, and Office Hours

-

16:08 <dmbaturin> Oh, cool.

-

16:09 <blackboxsw> As always notes will be posted to the following site

-

16:09 <blackboxsw> #link https://cloud-init.github.io/

-

16:09 <blackboxsw> welcome dmbaturin good timing. :)

-

16:09 <blackboxsw> #topic Previous Actions

-

16:09 <dmbaturin> Yeah, I'm just in time it seems. ;)

-

16:09 <blackboxsw> 2 weeks ago we had a couple of followup items that needed some extra review:

-

16:10 <blackboxsw> * ACTION: blackboxsw review distro dection and empty modules list

-

16:10 <blackboxsw> * ACTION: robjo review existing chrony support in master per rharper's work

-

16:10 <blackboxsw> * ACTION: blackboxsw carryover network hotplug vs network maintenance on reboot-only

-

16:10 <blackboxsw> we did get through robjo's branches on distro detection and landed them\

-

16:11 <blackboxsw> and I know our team also discussed a potential approach to network hotplug vs network maintenance to better enable SmartOs folks who want to handle network config across reboots only

-

16:12 <blackboxsw> I think we decided we needed to draw up a quick shared document on a proposal which would allow for maintenance on reboots only vs true hotplug.

-

16:12 <blackboxsw> I'll carry over that action to write up a doc on this and send it to list by the next meeting

-

16:13 * blackboxsw blackboxsw write up short doc/branch on hotplug versus network maintenance on reboot for comment

-

16:13 <blackboxsw> and I believe robjo from SuSE was able to get through rharper's chrony support branch with a couple comments too

-

16:13 <blackboxsw> so no other actions from last meeting

-

16:13 <blackboxsw> #topic Recent Changes

-

16:14 <blackboxsw> this following content landed in cloud init tip over the last two weeks

-

16:14 <blackboxsw> - Do not use the systemd_prefix macro, not available in this environment

-

16:14 <blackboxsw> [Robert Schweikert]

-

16:14 <blackboxsw> - doc: Add config info to ec2, openstack and cloudstack datasource docs

-

16:14 <blackboxsw> [Chad Smith]

-

16:14 <blackboxsw> - Enable SmartOS network metadata to work with netplan via per-subnet

-

16:14 <blackboxsw> routes [Dan McDonald] (LP: #1763512)

-

16:14 <blackboxsw> - openstack: Allow discovery in init-local using dhclient in a sandbox.

-

16:14 <ubot5> Launchpad bug 1763512 in cloud-init "DataSourceSmartOS ignores sdc:routes" [Medium,Fix committed] https://launchpad.net/bugs/1763512

-

16:14 <powersj> lol!

-

16:14 <powersj> welcome back

-

16:14 <blackboxsw> heh looks like I got kicked for the paste :)

-

16:14 <powersj> blackboxsw: your last message was - openstack: Allow discovery in init-local using dhclient in a sandbox.

-

16:15 <blackboxsw> - tests: Avoid using https in httpretty, improve HttPretty test case.

-

16:15 <blackboxsw> 10:14 (LP: #1771659)

-

16:15 <blackboxsw> 10:14 - yaml_load/schema: Add invalid line and column nums to error message

-

16:15 <blackboxsw> 10:14 [Chad Smith]

-

16:15 <blackboxsw> 10:14 - Azure: Ignore NTFS mount errors when checking ephemeral drive

-

16:15 <blackboxsw> 10:14 [Paul Meyer]

-

16:15 <ubot5> Launchpad bug 1771659 in cloud-init "unittests fail in OpenSuSE 42.3 with httpretty issues" [Medium,Fix committed] https://launchpad.net/bugs/1771659

-

16:15 <blackboxsw> - packages/brpm: Get proper dependencies for cmdline distro.

-

16:15 <blackboxsw> 10:14 - packages: Make rpm spec files patch in package version like in debs.

-

16:15 <blackboxsw> 10:14 - tools/run-container: replace tools/run-centos with more generic.

-

16:15 <blackboxsw> 10:14 - Update version.version_string to contain packaged version. (LP: #1770712)

-

16:15 <blackboxsw> 10:14 - cc_mounts: Do not add devices to fstab that are already present.

-

16:15 <blackboxsw> 10:14 [Lars Kellogg-Stedman]

-

16:15 <blackboxsw> 10:14 - ds-identify: ensure that we have certain tokens in PATH. (LP: #1771382)

-

16:15 <blackboxsw> 10:14 - tests: enable Ubuntu Cosmic in integration tests [Joshua Powers]

-

16:15 <blackboxsw> 10:14 - read_file_or_url: move to url_helper, fix bug in its FileResponse.

-

16:15 <blackboxsw> 10:14 - cloud_tests: help pylint [Ryan Harper]

-

16:15 <blackboxsw> 10:14 - flake8: fix flake8 errors in previous commit.

-

16:15 <ubot5> Launchpad bug 1770712 in cloud-init "It would be nice if cloud-init provides full version in logs" [Medium,Fix committed] https://launchpad.net/bugs/1770712

-

16:15 <blackboxsw> 10:14 - typos: Fix spelling mistakes in cc_mounts.py log messages [Stephen Ford]

-

16:15 <blackboxsw> 10:14 - tests: restructure SSH and initial connections [Joshua Powers]

-

16:15 <ubot5> Launchpad bug 1771382 in cloud-init "ds-identify: fails to recognize NoCloud datasource on boot cause it does not have /sbin in $PATH and thus does not find blkid" [Low,Fix committed] https://launchpad.net/bugs/1771382

-

16:15 <blackboxsw> 10:14 - ds-identify: recognize container-other as a container, test SmartOS.

-

16:15 <blackboxsw> ok hopefully we ended on ds-identify

-

16:16 <dmbaturin> Yes, we did.

-

16:16 <blackboxsw> excellent. sorry for the paste, I'll send this out to cloud-init@lists.canonical.com a day before the next meeting so we don't have to IRC flood here

-

16:17 <blackboxsw> make that cloud-init@lists.launchpad.net

-

16:17 <blackboxsw> also we finished our SRU (stable release update) of cloud-init 18.2.27 to Bionic.

-

16:18 <blackboxsw> Ubuntu Cosmic currently reflects near tip of master 18.2.59

-

16:18 <blackboxsw> ok that's all for Recent Changes

-

16:18 <blackboxsw> anything I'm missing powersj ?

-

16:19 <powersj> I think you are good

-

16:19 <blackboxsw> #topic In-progress Development

-

16:19 <blackboxsw> We track upstreams progress publicly in trello

-

16:19 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:20 <blackboxsw> any blue labeled cards are cloud-init core work

-

16:21 <blackboxsw> we have been fixing a couple of bugs raised by our CI infrastructure on newer series of Ubuntu . currently a minor issue with salt minion on Bionic or later, and a couple of unit and integration test race conditions

-

16:23 <blackboxsw> big ticket items for cloud-init in the nearterm are metadata standardization across clouds, so cloud-init scripts/cloud-config template can source these cloud-provided values

-

16:24 <dmbaturin> Metadata standardization is something I really would like to see, if you need more hands for that, let me know.

-

16:24 <blackboxsw> the standardization of this instance-data will allow folks to script against any standard values provided to cloud-init in the same way on any cloud. Think hostname, fqdn, ip addrs, region name etc.

-

16:24 <dmbaturin> SSH keys too!

-

16:24 <blackboxsw> definitely dmbaturin I'll point you at a couple branches and what we're thinking

-

16:25 <blackboxsw> this conent will show up in /run/cloud-init/instance-data.json

-

16:25 <blackboxsw> #link https://cloudinit.readthedocs.io/en/latest/topics/datasources.html?highlight=instance-data#instance-data

-

16:26 <blackboxsw> and will also be referenced via jinja template variables

-

16:26 <blackboxsw> and a cloud-init query CLI

-

16:28 <dmbaturin> The data will be updated whenever a change in the environment is made?

-

16:28 <blackboxsw> Also powersj will be working toward a common library for cloud-testing in the weeks to come which cloud-init integration tests will leverage to drive lxd, ec2, openstack azure etc for a cloud testing

-

16:29 <dmbaturin> Also, will it be possible to stop cloud-init from doing anything but writing that data and starting an external script to process it?

-

16:30 <blackboxsw> dmbaturin: some of that functionality will be handled in the hotplug work we are starting on. There will be operations that can be triggered by either a hotplug monitor on metadata or by cloud-init's CLI to say query from cache (the instance-data.json file) versus query fresh/update

-

16:30 <dmbaturin> I see.

-

16:33 <blackboxsw> dmbaturin: cloud-inits init-local or init-network stage is what calls "get_data" on the give datasources to collect and write that data to file. Spawning a script is generally done through runcmd which happens in cloud-init's 'final' stage. Trying to decouple them (and skipping the modules:config stage) is possible by altering /etc/cloud/cloud.cfg in a custom image to specify no modules in a given stage. Though it's not

-

16:33 <blackboxsw> really recommeded as most of the modules only do a quick sanity check to see if they are specifically enabled before trying to do any realy work

-

16:33 <blackboxsw> we try to keep boot time as fast as possible and cut out the fat where we can

-

16:33 <blackboxsw> if that's the concern you had

-

16:34 <blackboxsw> ok I think that's it for In-progress development we can move to office hours for all addtional discussion

-

16:34 <blackboxsw> #topic Office Hours (next ~30 mins)

-

16:35 <dmbaturin> No, boot time is not the primary concern here, my concern is how to ensure no module is trying to treat our system as if it was a normal Debian (which either doesn't work or can potentially get the system into an inconsistent state).

-

16:36 <dmbaturin> I guess if we are having a real meeting, it may be a good idea to formally introduce myself and the project. :)

-

16:36 <blackboxsw> All topics of interest to cloud-init development can be brought up and discussed here. If there are merge proposal that need attention, bugs that need work just bring them up here we should have a few sets of eyes on this channel to discuss and comment

-

16:36 <blackboxsw> sounds good dmbaturin introduce away :)

-

16:37 <blackboxsw> Chad smith, Canonical, one of the maintainers of cloud-init. We have a few others here (some on vacation). powersj rharper smoser dpb1 all canonical as well.

-

16:38 <dpb1> idk who blackboxsw is

-

16:38 <dpb1> he might be crazy

-

16:38 <blackboxsw> frequently we have other distribution developers and cloud devs here too (SuSE, RedHat, Microsoft Azure, SmartOS, VMWare )

-

16:38 <blackboxsw> heh, I'm just a bot

-

16:38 <dmbaturin> So, I'm one of the maintainers of the VyOS project (http://vyos.io). It's a distro for routers and firewalls whose primary goal is to be just like hardware routers, but not tied to any hardware, which includes a single config file and unified CLI with a commit/rollback model, versioning, and cross-checks (e.g. if you try to reference a non-existent NIC in DHCP configuration, commit fails).

-

16:39 <dpb1> nice to meet you dmbaturin

-

16:40 <blackboxsw> ahh makes sense. So debian-based os kindof, which is why you'd want to lock down what modules run.

-

16:40 <dmbaturin> We support all major virtualization platforms now in the sense of including all required drivers and utilities, but autoconfiguration on cloud platforms is only supported for EC2 via a custom script, so we are looking to ways to support more clouds, ideally without doing the work that is already done, or at least contributing those general things into something where more people can benegit from it, not just us.

-

16:41 <blackboxsw> alos dmbaturin each config module claims what distro is supported in a distro property, so you could vet what modules you want to run, and only add VyOS to the list of compatible distros. Config modules all live in source at cloudinit/config/cc_*py.

-

16:41 <blackboxsw> but we can discuss that confuig module support (or not) once you dig in to look at supporting VyOS

-

16:42 <dmbaturin> Yes, I'm thinking how exactly it should be done.

-

16:42 <blackboxsw> dmbaturin: cloud-init's a pretty good choice for getting that cloud-support breadth for free

-

16:43 * robjo sorry I'm late

-

16:43 <blackboxsw> robjo: sorry for the late change from yesterday's normal meet time

-

16:43 <dmbaturin> The least intrusive option would be to indeed improve the instance data format, so that we can simply pass it to our own script, which is why I'm all for contributing to it.

-

16:43 <robjo> blackboxsw: noLnxDistro branch has not yet been merged

-

16:44 <blackboxsw> bah robjo ahh you're right

-

16:44 <blackboxsw> ok looks like you handled all review comments. I'll get it landed today

-

16:44 <smoser> powersj: https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/347060

-

16:44 * blackboxsw blackboxsw land https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/336794 today

-

16:45 <smoser> you moved that to 'approved' i guess ?

-

16:45 <smoser> which meant the bot didnt comment (sorry blackboxsw ... interupted)

-

16:45 <dmbaturin> blackboxsw: Could you point me to the branches were the work on instance data is going on?

-

16:45 <blackboxsw> dmbaturin: here's one stale one I need to get back to this week. for enabling the template reference of instance-data.json content

-

16:46 <powersj> smoser: ah sorry you are right

-

16:47 <smoser> powersj: i'm going to land it anyway

-

16:47 <robjo> also I think emptyStageOK branch should be ready to go

-

16:47 <powersj> ok

-

16:47 <blackboxsw> hrm digging on the metadata branch.

-

16:48 <blackboxsw> dmbaturin: the trello card I'll be tying branches to is this one

-

16:48 <blackboxsw> #link https://trello.com/c/5n5B8x23/802-cloud-init-query-standardized-json-information

-

16:48 <robjo> and https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904 should be on smoser plate

-

16:49 <robjo> or anyone else who wants to pick it up and get it merged, please

-

16:49 <blackboxsw> #link https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/335290

-

16:50 <blackboxsw> ^ dmbaturin initial template handling thoughts.... I have to create at least 2 branches to standardize datasource class apis to make the metadata content easier to generalize and I can add your launchpad username to the review as I put them up

-

16:50 <rharper> smoser: re: hostname, yes, that's right; we probably could update the set_hostname docs to mention that detail w.r.t early hostname setting

-

16:51 <rharper> blackboxsw: sorry to interrupt

-

16:51 <blackboxsw> dmbaturin: what's your launchpad user name? (mine's chad.smith)

-

16:51 <dmbaturin> blackboxsw: dmbaturin

-

16:51 <blackboxsw> heh.

-

16:51 <blackboxsw> thx

-

16:51 <dmbaturin> I'm too predictable. ;)

-

16:51 <blackboxsw> yeah, I lost a bet on blackboxsw :)

-

16:51 <blackboxsw> robjo: okay adding that branch too for review/landing

-

16:51 * blackboxsw land https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904

-

16:52 * blackboxsw land https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/336794

-

16:53 <blackboxsw> alright, any other topics or discussions?

-

16:53 <dmbaturin> Trello is integrated with launchpad?

-

16:55 <blackboxsw> dmbaturin: nope, just easy to use for our agile workflow. And simple to cut-paste links, assign people, drag to different lanes as the work progresses

-

16:55 <blackboxsw> has a lot of github integraiton if you get the right plugins

-

16:56 <blackboxsw> we have some minimal tooling that can talk to lauchpad and inject cards, but that's hand-written, not part of trello product.

-

16:59 <dmbaturin> I mean, if you add my username there, will I get any notifications about card changes.

-

16:59 <blackboxsw> dmbaturin: I get emails from all trello card moves,changes. let's see

-

16:59 <blackboxsw> I can subscribe you to the card (you want the standardized json stuff?)

-

17:00 <dmbaturin> Yes.

-

17:02 <blackboxsw> hrm can't find your user

-

17:02 <blackboxsw> ahh

-

17:03 <blackboxsw> I think I invited you

-

17:03 <blackboxsw> and added your user to the card so you can watch it progress

-

17:05 <blackboxsw> ok I think that about wraps up our meeting for today

-

17:05 <blackboxsw> any parting shots?

-

17:05 <blackboxsw> I'll post these notes to our github project page

-

17:05 <blackboxsw> #link https://cloud-init.github.io/

-

17:05 <blackboxsw> thanks again all

-

17:05 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2018-06-18.html b/status-2018-06-18.html deleted file mode 100644 index 20b9dd4..0000000 --- a/status-2018-06-18.html +++ /dev/null @@ -1,336 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Mon 18 June 2018 in status-meeting-minutes - - • 8 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:11.

- -

Recent Changes

-

The discussion about "Recent Changes" started at 16:27.

- -

Cloud-init 18.3 release

-

The discussion about "Cloud-init 18.3 release" started at 16:36.

-

Office Hours (next ~30 mins)

-

The discussion about "Office Hours (next ~30 mins)" started at 16:46.

- -

Vote results

-

Action items, by person

-
    -
  • blackboxsw
  • -
  • blackboxsw review distro dection and empty modules list [ DONE ] both robjo's branches are landed as of friday of last week.
  • -
  • blackboxsw carryover network hotplug vs network maintenance on reboot-only
  • -
  • rhaper/blackboxsw review https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904
  • -
  • robjo
  • -
  • blackboxsw review distro dection and empty modules list [ DONE ] both robjo's branches are landed as of friday of last week.
  • -
-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (83)
  • -
  • robjo (14)
  • -
  • rharper (10)
  • -
  • ubot5 (7)
  • -
  • smoser (7)
  • -
  • meetingology (6)
  • -
-

Full Log

-

16:08 <blackboxsw> #startmeeting Cloud-init bi-weekly status meeting

-

16:08 <meetingology> Meeting started Mon Jun 18 16:08:07 2018 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:08 <meetingology>

-

16:08 <meetingology> Available commands: action commands idea info link nick

-

16:09 <blackboxsw> Hi folks and welcome. We've got a big week this week as we are planning on a cloud-init release. So we will have an additional topic in today's agenda

-

16:09 <smoser> o/

-

16:10 <blackboxsw> it's been a few weeks, due to holiday schedules/travel, our agenda will be as following: Previous Actions, Recent Changes, In-progress develepment, cloud-init release 18.3 and office hours

-

16:11 <blackboxsw> #topic Previous Actions

-

16:11 <blackboxsw> last action items are listed in our meeting minutes at the following url:

-

16:11 <blackboxsw> #link https://cloud-init.github.io/status-2018-05-29.html#status-2018-05-29

-

16:12 <blackboxsw> #ACTION blackboxsw review distro dection and empty modules list [ DONE ] both robjo's branches are landed as of friday of last week.

-

16:12 * meetingology blackboxsw review distro dection and empty modules list [ DONE ] both robjo's branches are landed as of friday of last week.

-

16:13 <blackboxsw> that was a carryover from the meeting before I believe.

-

16:13 <blackboxsw> #ACTION blackboxsw carryover network hotplug vs network maintenance on reboot-only

-

16:13 * meetingology blackboxsw carryover network hotplug vs network maintenance on reboot-only

-

16:14 <blackboxsw> I think this was the only other unresolved action. Our team has had mutliple followup discussions internally and with mgerts from Joyent/SmartOs as well

-

16:14 <blackboxsw> smoser: and rharper drew up a hackmd doc related to this work here:

-

16:14 <blackboxsw> #link https://hackmd.io/NUUO4nndS4CXTItl8Rs6Nw

-

16:15 <blackboxsw> We've come to a conclusion on a common near-term approach that will support cold-plug scenarios by allowing datasources to claim whether or not they will re-render networking on a boot event. This would allow cloud-init to react to network metadata changes across boot and enable/disable those devices accordingly

-

16:16 <blackboxsw> a WIP branch is available here

-

16:16 <blackboxsw> #link expectation is to get the foundation landed this week

-

16:16 <blackboxsw> and tracked in trello here

-

16:16 <blackboxsw> #link https://trello.com/c/Yp6VG2lP/837-eventpolicy-foundation-for-joyent-and-azure-coldplug

-

16:17 <robjo> Note that the metdata ins EC2 is "stale", AFIK, or at least some parts of the data are stale, i.e. they only get refreshed on instance restart

-

16:17 <rharper> is it instance restart or "re DHCP" ?

-

16:17 <rharper> ie, bounce the interface ?

-

16:17 <blackboxsw> #link https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+ref/feature/maintain-network-on-boot

-

16:18 <smoser> robjo: that is correct.

-

16:18 <robjo> so a re-read of the metadata on EC2 delivers no/maybe limited new information

-

16:18 <smoser> robjo: well, network information is updated.

-

16:18 <smoser> user-data is only updatable on stop ->` start in ec2

-

16:18 <robjo> rharper: AFAIK new metadat gets pick up on instance restart

-

16:19 <rharper> ok

-

16:19 <robjo> I know the IID also only gets updated on stop-start

-

16:19 <blackboxsw> certainly in Azure that's the case. you have to stop the instance before changing attached network interfaces and then bring instance online again

-

16:20 <robjo> Yes, in Azure adding network interfaces is not dynamic

-

16:20 <robjo> meaning cannot happen while an instance is running

-

16:21 <blackboxsw> adding IPs in azure is an online thing, but even azure's network metadata is limited in that it doesn't tell you whether a network interface is static or dynamic. examples here:

-

16:21 <blackboxsw> https://hackmd.io/aODzXfa_TOikNtYBLt8erA

-

16:21 <blackboxsw> #link https://hackmd.io/aODzXfa_TOikNtYBLt8erA

-

16:22 <robjo> Also for Azure there exists the "problem" of accelerated networking, i.e. SR-IOV

-

16:23 <robjo> when accelerated networking is on the SR-IOV interface gets the same MAC address as the "Synthetic nic"

-

16:23 <rharper> well, they "solved" it by having the kernel auto bond =/

-

16:23 <robjo> the SR-IOV interface gets bound to the synthetic nic in the kernel, that was a patch that went into the kernel 6-9 months ago

-

16:23 <rharper> AFAICT, the sriov device just magically comes and goes as it will

-

16:24 <rharper> so, one shouldn't worry about the silent bonding ... (I'm being a bit sarcastic here)

-

16:24 <robjo> yes, but the interface still shows up, so if output from "ip" command is read one has two devices with the same MAC address, only one of which should be configured

-

16:25 <rharper> we ignore any of the mlx4 driver devices

-

16:25 <rharper> yes they show up

-

16:25 <robjo> OK

-

16:25 <rharper> but the directive we got was to ignore them; and DHCP on the netvsc ones

-

16:25 <blackboxsw> ...so think that's all I had on action items from previous meeting.

-

16:26 <blackboxsw> shall we go to next topic?

-

16:26 <robjo> And that of course works until Msft gets a better HW deal from Intel or someone else for their network cards ;)

-

16:26 <blackboxsw> heh

-

16:26 <rharper> robjo: indeed

-

16:27 <blackboxsw> #topic Recent Changes

-

16:27 <blackboxsw> due to a couple vacations and some work travel it's been a slightly slower couple weeks below are the cloud-init changes that have gone in:

-

16:28 <blackboxsw> - lxd: Delete default network and detach device if lxd-init created them.

-

16:28 <blackboxsw> (LP: #1776958)

-

16:28 <blackboxsw> - openstack: avoid unneeded metadata probe on non-openstack platforms

-

16:28 <blackboxsw> [Chad Smith] (LP: #1776701)

-

16:28 <blackboxsw> - stages: fix tracebacks if a module stage is undefined or empty

-

16:28 <blackboxsw> [Robert Schweikert] (LP: #1770462)

-

16:28 <blackboxsw> - Be more safe on string/bytes when writing multipart user-data to disk.

-

16:28 <ubot5> Launchpad bug 1776958 in cloud-init "error creating lxdbr0." [Medium,Fix committed] https://launchpad.net/bugs/1776958

-

16:28 <blackboxsw> (LP: #1768600)

-

16:28 <blackboxsw> - Fix get_proc_env for pids that have non-utf8 content in environment.

-

16:28 <ubot5> Launchpad bug 1776701 in cloud-init "ec2: xenial unnecessary openstack datasource probes during discovery" [High,Fix committed] https://launchpad.net/bugs/1776701

-

16:28 <blackboxsw> (LP: #1775371)

-

16:28 <blackboxsw> - tests: fix salt_minion integration test on bionic and later [Chad Smith]

-

16:28 <blackboxsw> - tests: provide human-readable integration test summary when --verbose

-

16:28 <blackboxsw> [Chad Smith]

-

16:28 <ubot5> Launchpad bug 1770462 in cloud-init "Allow empty stages" [Low,Fix committed] https://launchpad.net/bugs/1770462

-

16:28 <blackboxsw> - tests: skip chrony integration tests on lxd running artful or older

-

16:28 <blackboxsw> [Chad Smith]

-

16:28 <ubot5> Launchpad bug 1768600 in cloud-init "UTF-8 support in User Data (text/x-shellscript) is broken" [Medium,Fix committed] https://launchpad.net/bugs/1768600

-

16:28 <blackboxsw> - test: add optional --preserve-instance arg to integraiton tests

-

16:28 <blackboxsw> [Chad Smith]

-

16:28 <ubot5> Launchpad bug 1775371 in cloud-init "cloud-init (18.2) fails on decoding proc1 env" [Medium,Fix committed] https://launchpad.net/bugs/1775371

-

16:28 <blackboxsw> - netplan: fix mtu if provided by network config for all rendered types

-

16:28 <blackboxsw> [Chad Smith] (LP: #1774666)

-

16:28 <ubot5> Launchpad bug 1774666 in netplan.io (Ubuntu Cosmic) "Bond interfaces stuck at 1500 MTU on Bionic" [Undecided,Confirmed] https://launchpad.net/bugs/1774666

-

16:28 <blackboxsw> - tests: remove pip install workarounds for pylxd, take upstream fix.

-

16:28 <blackboxsw> - subp: support combine_capture argument.

-

16:28 <blackboxsw> - tests: ordered tox dependencies for pylxd install [Chad Smith]

-

16:28 <blackboxsw> - util: add get_linux_distro function to replace platform.dist

-

16:28 <blackboxsw> [Robert Schweikert] (LP: #1745235)

-

16:28 <blackboxsw> - pyflakes: fix unused variable references identified by pyflakes 2.0.0.

-

16:28 <ubot5> Launchpad bug 1745235 in cloud-init "distribution detection" [Medium,Fix committed] https://launchpad.net/bugs/1745235

-

16:28 <blackboxsw> thanks again Robert for the contributions here getting cloud-init in order :)

-

16:30 <blackboxsw> we've also just pushed a release of cloud-init tip into Ubuntu Cosmic.

-

16:30 <blackboxsw> so all latest changes are in the development series

-

16:32 <blackboxsw> I think that about wraps it

-

16:32 <blackboxsw> #topc In-progress Development

-

16:32 <blackboxsw> As always, we track ongoing work publicly at

-

16:32 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:33 <blackboxsw> we've got some cold-plug network rendering handling that will be queued for this week, mgerts is working on enabling cold-plug network rendering support on boot for SmartOS, and there is a followup for Azure to do the same

-

16:34 <blackboxsw> cloud-init squad is going to be setting up an SRU into Xenial, Artful and Bionic this week as well

-

16:34 <blackboxsw> to sync latest qualified cloud-init into those Ubuntu series

-

16:35 <smoser> blackboxsw: thinking out loud..

-

16:35 <smoser> if we're going to release 18.3 on thursday

-

16:35 <smoser> might as well just hold off on sru until then

-

16:35 <blackboxsw> (wait on 18.3 release?)

-

16:36 <blackboxsw> yeha

-

16:36 <blackboxsw> yeah even

-

16:36 <blackboxsw> which brings us to our next topic

-

16:36 <blackboxsw> #topic Cloud-init 18.3 release

-

16:37 <blackboxsw> I hadn't seen any responsed to your email scott to cloud-init@lists.launchpad.net. Does anyone have any feature pressing that we'd like to get into this release

-

16:38 <blackboxsw> estimated release would be Thusday of this week

-

16:39 <blackboxsw> I'd whimsically like to include the azure cold-plug stuff, but that means getting those two branches in shape today for a thorough review/test cycle

-

16:39 <blackboxsw> s/whimsically/opportunitically/

-

16:39 <blackboxsw> heh I give up

-

16:42 <blackboxsw> did we want to pull this in? https://code.launchpad.net/~paul-meyer/cloud-init/+git/cloud-init/+merge/334989

-

16:45 <blackboxsw> If there are any pressing bugs or features that need to be in 18.3 we'd like to see them up for review by Wednesday of this week so that we can cut our upstream release. Feel free to send an email to the list cloud-init@lists.launchpad.net or this channel if your branch needs to get some eyes.

-

16:46 <blackboxsw> we'll SRU 18.3 then into Xenial, Artful and Bionic after a complete round of testing.

-

16:46 <blackboxsw> #topic Office Hours (next ~30 mins)

-

16:46 <robjo> :D After 18.3 but before the workshop: https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904

-

16:47 <blackboxsw> Folks are around for further discussion on any cloud-init topics of interest

-

16:47 <robjo> then maybe at the workshop we can come up with a way to move SLES & openSUSE to sysconfig renderer

-

16:48 <blackboxsw> good topic idea

-

16:48 <blackboxsw> #ACTION rhaper/blackboxsw review https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904

-

16:48 * meetingology rhaper/blackboxsw review https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904

-

17:22 <blackboxsw> thanks again folks. catch you next time.

-

17:23 <blackboxsw> minutes will be published to the link below

-

17:23 <blackboxsw> #link https://cloud-init.github.io/

-

17:23 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2018-07-02.html b/status-2018-07-02.html deleted file mode 100644 index ed868e3..0000000 --- a/status-2018-07-02.html +++ /dev/null @@ -1,271 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Mon 02 July 2018 in status-meeting-minutes - - • 4 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:09.

- -

Recent Changes

-

The discussion about "Recent Changes" started at 16:15.

- -

In-progress Development

-

The discussion about "In-progress Development" started at 16:21.

- -

Office Hours (next ~30 mins)

-

The discussion about "Office Hours (next ~30 mins)" started at 16:31.

- -

Vote results

-

Action items, by person

- -

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (60)
  • -
  • meetingology (4)
  • -
  • ubot5 (3)
  • -
  • danMS_ (1)
  • -
  • mgerdts (1)
  • -
-

Full Log

-

16:05 <blackboxsw> #startmeeting Cloud-init bi-weekly status meeting

-

16:05 <meetingology> Meeting started Mon Jul 2 16:05:44 2018 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:05 <meetingology>

-

16:05 <meetingology> Available commands: action commands idea info link nick

-

16:06 <blackboxsw> hi folks, just kicking off another cloud-init status meeting to communicate the recent events in cloud-init land.

-

16:06 <blackboxsw> welcome to all, feel free to interrupt as we go through the agenda. As always cloud-init status minutes will live at the following url

-

16:07 <blackboxsw> #link https://cloud-init.github.io/

-

16:07 <blackboxsw> The meeting agenda is as follows:

-

16:08 <blackboxsw> agenda: Previous Actions, Recent Changes, In-progress develepment and office hours (~30 minutes)

-

16:09 <blackboxsw> #topic Previous Actions

-

16:09 <blackboxsw> Last meeting we have a couple of actions to look over:

-

16:10 <blackboxsw> #ACTION blackboxsw carryover network hotplug vs network maintenance on reboot-only

-

16:10 <blackboxsw> #ACTION blackboxsw carryover network hotplug vs network maintenance on reboot-only [DONE]

-

16:11 <blackboxsw> we held multiple meetings, including discussion with mgerdts on a SmartOS solution for handling regenerating network configuration per-boot when a user selects this behavior

-

16:12 <blackboxsw> We have just landed a supporting branch in cloud-init tip to enable datasources to define what events (BOOT vs BOOT_NEW_INSTANCE) they will react to when generating network config.

-

16:12 <blackboxsw> #link https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348000

-

16:13 <blackboxsw> that should give a foundation for other datasources to write/change network config across boots, instead of allowing network config to remain static based on cloud-init's initial network configuration

-

16:13 <blackboxsw> the 2nd action ..

-

16:14 <blackboxsw> #ACTION haper/blackboxsw review https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904 [CARRYOVER]

-

16:14 * meetingology haper/blackboxsw review https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904 [CARRYOVER]

-

16:14 <blackboxsw> I'd like to carry this one over. We got a bit bogged down in SRU, CentOs stuff last week and we shold be able to get some eyes on this branch

-

16:14 <blackboxsw> I think that's it for actions.

-

16:15 <blackboxsw> #topic Recent Changes

-

16:16 <blackboxsw> Below is a list of changes landed in cloud-init tip or package publishing that has occured for the project:

-

16:16 <blackboxsw> * our 18.3 release was cut from tip if you caught the email on that mailing list

-

16:16 <blackboxsw> Congrats all for a great effort at improving quality and adding more datasource/cloud support

-

16:17 <blackboxsw> #link https://lists.launchpad.net/cloud-init/msg00164.html

-

16:17 <blackboxsw> ^ in case you didn't get the message

-

16:18 <blackboxsw> * we also publish 18.3 release into Ubuntu Cosmic and started a stable release update (SRU) to publish 18.3 in to xenial, artful, bionic

-

16:18 <blackboxsw> published*

-

16:19 <blackboxsw> expectations are that xenial, artful and bionic will have 18.3 after this week of testing

-

16:20 <blackboxsw> the remaining changes landed in tip are:

-

16:20 <blackboxsw> - update_metadata: a datasource can support network re-config every boot

-

16:20 <blackboxsw> [Chad Smith]

-

16:20 <blackboxsw> - tests: drop salt-minion integration test (LP: #1778737)

-

16:20 <blackboxsw> - Retry on failed import of gpg receive keys.

-

16:20 <blackboxsw> - tools: Fix run-container when neither source or binary package requested.

-

16:20 <blackboxsw> - docs: Fix a small spelling error. [Oz N Tiram]

-

16:20 <blackboxsw> - tox: use simplestreams from git repository rather than bzr.

-

16:20 <ubot5> Launchpad bug 1778737 in cloud-init "salt-minion test needs fixing" [Undecided,Fix committed] https://launchpad.net/bugs/1778737

-

16:20 <blackboxsw> - release 18.3 [Chad Smith] (LP: #1777743)

-

16:20 <blackboxsw> - docs: represent sudo:false in docs for user_groups config module

-

16:20 <blackboxsw> [Chad Smith]

-

16:20 <blackboxsw> - Explicitly prevent sudo access for user module

-

16:20 <ubot5> Launchpad bug 1777743 in cloud-init "Release 18.3" [Undecided,Fix released] https://launchpad.net/bugs/1777743

-

16:20 <blackboxsw> [Jacob Bednarz] (LP: #1771468)

-

16:20 <ubot5> Launchpad bug 1771468 in cloud-init "Allow a way to explicitly disable sudo for a user" [Undecided,Fix released] https://launchpad.net/bugs/1771468

-

16:21 <blackboxsw> next topic

-

16:21 <blackboxsw> #topic In-progress Development

-

16:22 <blackboxsw> Our ongoing development is always listed publicly at the following trello board

-

16:22 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:23 <blackboxsw> We are going to be focused on SRU validation for Ubuntu this week which should take up the majority of the week.

-

16:23 <blackboxsw> At the end of this SRU process we will also rebuild centos binaries in our copr repo

-

16:23 <blackboxsw> #link https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/

-

16:24 <blackboxsw> so that folks in other envs will have access to latest bits if their distro/cloud doesn't have that update

-

16:24 <blackboxsw> Also, specfic to mgerdts and danMS_ there is a branch in progress for Azure support to regenerate network-config for all interfaces on each boot.

-

16:25 <blackboxsw> #link https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348704

-

16:25 <blackboxsw> mgerdts: might like it only as another example of a datasource managing network config across boots

-

16:26 <mgerdts> Thanks. Will look at that soon.

-

16:26 <blackboxsw> no prob, sorry for all the pings :)

-

16:26 <danMS_> will take a look too and spk to paulmey

-

16:27 <blackboxsw> also smoser is working on implementing an OCIC datasource (Oracle Cloud Infrastructure Classic)

-

16:31 <blackboxsw> think that wraps it up for this week.

-

16:31 <blackboxsw> #topic Office Hours (next ~30 mins)

-

16:31 <blackboxsw> there should be a couple of eyes on this channel for discusssions, questions, bug requests etc that might need a bit more attention.

-

16:33 <blackboxsw> again, thanks for tuning in and helping make cloud-init better!

-

16:33 <blackboxsw> meeting minutes will ultimately show at

-

16:33 <blackboxsw> #link https://cloud-init.github.io/

-

17:02 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2018-08-06.html b/status-2018-08-06.html deleted file mode 100644 index b3c0e48..0000000 --- a/status-2018-08-06.html +++ /dev/null @@ -1,267 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Mon 06 August 2018 in status-meeting-minutes - - • 5 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:09.

- -

Recent Changes

-

The discussion about "Recent Changes" started at 16:11.

- -

In-progress Development

-

The discussion about "In-progress Development" started at 16:19.

- -

Office Hource (next ~30 mins)

-

The discussion about "Office Hource (next ~30 mins)" started at 16:25.

- -

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (59)
  • -
  • powersj (6)
  • -
  • meetingology (4)
  • -
  • ubot5 (1)
  • -
  • dpb1 (1)
  • -
-

Full Log

-

16:04 <blackboxsw> #startmeeting Cloud-init bi-weekly status meeting

-

16:04 <meetingology> Meeting started Mon Aug 6 16:04:05 2018 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:04 <meetingology>

-

16:04 <meetingology> Available commands: action commands idea info link nick

-

16:04 <dpb1> o/

-

16:04 <blackboxsw> hi folks, let's kickoff another cloud-init status meeting. Welcome back. Lot's of summer vacations disrupting our typical meeting schedule.

-

16:05 <blackboxsw> Our last meeting's minutes should be up on our github site

-

16:05 <blackboxsw> #link https://cloud-init.github.io/

-

16:07 <blackboxsw> for this meeting we'll go through the following topics: previous actions, recent work, in-progress development and office hours

-

16:09 <blackboxsw> #topic Previous Actions

-

16:09 <blackboxsw> from our last meeting we had a couple of actions to carry over

-

16:10 <blackboxsw> we 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/348000

-

16:10 <blackboxsw> #action rharper: and I need to review https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904

-

16:10 * meetingology rharper: and I need to review https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904

-

16:10 <blackboxsw> the above is still a carryover

-

16:11 <blackboxsw> that's all for actions from last meeting

-

16:11 <blackboxsw> #topic Recent Changes

-

16:12 <blackboxsw> the following has landed in cloud-init tip:

-

16:13 <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 files

-

16:13 <blackboxsw> * ubuntu,centos,debian: get_linux_distro to align with platform.dist

-

16: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 boot

-

16:13 <ubot5> Launchpad bug 1784685 in cloud-init "Oracle: cloud-init openstack local detection too strict for oracle cloud" [High,Fix committed] https://launchpad.net/bugs/1784685

-

16:13 <blackboxsw> * tests: drop salt-minion integration test

-

16: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:14 <blackboxsw> generally 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:15 <blackboxsw> notably, we discovered a potential regression in Oracle datasource detection of their OpenStack implementation so that fix is queued for publish into xenial and bionic

-

16:15 <blackboxsw> 18.3-9 is what folks are looking for. in xenial/bionic/cosmic for latest cloud-init containing all the above fixes

-

16:16 <blackboxsw> Also 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 acceptm

-

16:16 <blackboxsw> Also 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 <powersj> yep that is live and with a recent fix to remove the extra "Author" line now

-

16:16 <powersj> hopefully it is saving blackboxsw, smoser, and rharper time ;)

-

16:17 <blackboxsw> powersj: can you explain what it does (so I don't have to type)

-

16:17 <blackboxsw> :)

-

16:17 <powersj> If a merge request is put in the "Approved" state, it will get test merged with the master branch

-

16:17 <powersj> the tests will run the same as during a review and verify that it can merge cleanly

-

16:18 <powersj> the commit message will get linted to verify it fits our format

-

16:18 <powersj> and if everything looks good, get merged in and pushed to master

-

16:18 <blackboxsw> thanks for that work powersj. it looks/works great so far.

-

16:19 <blackboxsw> #topic In-progress Development

-

16:19 <blackboxsw> All our current work is visible at the following trello board

-

16:19 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:20 <blackboxsw> I expect we'll have a couple of branches landed shortly in the following areas:

-

16:21 <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> - I

-

16:21 <blackboxsw> - I'm trying to wrap up a branch for Azure to write network data from their IMDS per-boot

-

16:22 <blackboxsw> #link https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348704

-

16:22 <blackboxsw> - Joyent (SmartOS) per-boot network config review

-

16:23 <blackboxsw> - a couple netplan config option bugs for bionic ++

-

16:24 <blackboxsw> - and standardize instance-data sourcing in #cloud-config files (like referencing the hostname as detected from instance metadata)

-

16:24 <blackboxsw> I think that probably wraps it up for stuff in progress

-

16:24 <blackboxsw> anything I'm missing?

-

16:25 <blackboxsw> ... without further ado

-

16:25 <blackboxsw> #topic Office Hource (next ~30 mins)

-

16:26 <blackboxsw> eyes will float on this channel for any bug/feature discussions, review requests etc. any cloud-init topic is acceptable.

-

16:28 <blackboxsw> a 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:31 <blackboxsw> while I'm at it, I think I'll set the topic to next status meeting time so folks know it's coming.

-

16:39 <blackboxsw> also 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 <blackboxsw> it looks a bit noisy on the debug front with adding out/err messages for all subp calls, but other than that fairly straight forward.

-

17:03 <blackboxsw> looks like that's a wrap for today.

-

17:03 <blackboxsw> #link https://cloud-init.github.io for meeting minutes

-

17:04 <blackboxsw> see you next time: 2 weeks from today

-

17:04 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2018-08-20.html b/status-2018-08-20.html deleted file mode 100644 index 869072a..0000000 --- a/status-2018-08-20.html +++ /dev/null @@ -1,245 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Mon 20 August 2018 in status-meeting-minutes - - • 4 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:13.

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:13.

-

In-progress Development

-

The discussion about "In-progress Development" started at 16:21.

- -

Office Hource (next ~30 mins)

-

The discussion about "Office Hource (next ~30 mins)" started at 16:27.

- -

Vote results

-

Action items, by person

- -

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (39)
  • -
  • ubot5 (5)
  • -
  • paulmey (5)
  • -
  • meetingology (4)
  • -
-

Full Log

-

16:09 <blackboxsw> #startmeeting Cloud-init bi-weekly status meeting

-

16:09 <meetingology> Meeting started Mon Aug 20 16:09:08 2018 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:09 <meetingology>

-

16:09 <meetingology> Available commands: action commands idea info link nick

-

16:09 <blackboxsw> For those around, let's kickoff another cloud-init status meeting. Feel free to interrupt as we go through the agenda for today.

-

16:10 <blackboxsw> agenda: Previous Actions, Recent Changes, In-progress development and office hours (~30 minutes)

-

16:13 <blackboxsw> #topic Previous Actions

-

16:13 <blackboxsw> nothing to speak of here as far as I recall.

-

16:13 <blackboxsw> #topic Recent Changes

-

16:14 <blackboxsw> We have recently landed the following content in tip of cloud-init over the last 2 weeks

-

16:14 <blackboxsw> - Add datasource Oracle Compute Infrastructure (OCI).

-

16:14 <blackboxsw> - azure: allow azure to generate network configuration from IMDS per boot.

-

16:14 <blackboxsw> - Scaleway: Add network configuration to the DataSource [Louis Bouchard]

-

16:14 <blackboxsw> - docs: Fix example cloud-init analyze command to match output.

-

16:14 <blackboxsw> [Wesley Gao]

-

16:14 <blackboxsw> - netplan: Correctly render macaddress on a bonds and bridges when

-

16:14 <blackboxsw> provided. (LP: #1784699)

-

16:14 <blackboxsw> - tools: Add 'net-convert' subcommand command to 'cloud-init devel'.

-

16:14 <blackboxsw> - redhat: remove ssh keys on new instance. (LP: #1781094)

-

16:14 <ubot5> Launchpad bug 1784699 in cloud-init "cloud-init not setting mac address for bond or bridge in bionic" [Medium,Fix committed] https://launchpad.net/bugs/1784699

-

16:15 <blackboxsw> - Use typeset or local in profile.d scripts. (LP: #1784713)

-

16:15 <blackboxsw> - OpenNebula: Fix null gateway6 [Akihiko Ota] (LP: #1768547)

-

16:15 <ubot5> Launchpad bug 1781094 in cloud-init "cloud.cfg.tmpl should not include "ssh_deletekeys: 0"" [Medium,Fix committed] https://launchpad.net/bugs/1781094

-

16:15 <ubot5> Launchpad bug 1784713 in cloud-init (Ubuntu) "cloud-init profile.d files use bash-specific builtin "local"" [Low,Confirmed] https://launchpad.net/bugs/1784713

-

16:15 <ubot5> Launchpad bug 1768547 in cloud-init (Ubuntu) "OpenNebula DataSource adds null gateway6 to netplan config" [Medium,Confirmed] https://launchpad.net/bugs/1768547

-

16:15 <blackboxsw> most notable is the new datasource for Oracle and Azure datasource now emitting network configuration per boot.

-

16:21 <blackboxsw> new Ubuntu cosmic images should contain 18.3-24-gf6249277-0ubuntu1 with the lastest patches

-

16:21 <blackboxsw> #topic In-progress Development

-

16:23 <blackboxsw> The team in general is perparing for the cloud-init summit conference which will be the second half of this week with cloud and distro vendors so we'll probably be landing a couple more branches in preparation for talks/demos there.

-

16:23 <blackboxsw> preparing rather

-

16:24 <blackboxsw> Our trello board is a good representation of any existing work we are "Doing"

-

16:24 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:26 <blackboxsw> recently powersj has also moved our jenkins server around to a new network so there has been a good bit of work getting all things jenkins back up and running behind the new proxies/firewalls etc.

-

16:26 <blackboxsw> thanks for the heavy lift powersj

-

16:27 <blackboxsw> I think that wraps up all things cloud-init....

-

16:27 <blackboxsw> #topic Office Hource (next ~30 mins)

-

16:28 <blackboxsw> We'll have eyes on this channel for any quips, complaints, bug, feature or branch discussions for the next half hour

-

16:28 <blackboxsw> Otherwise, we'll be excited to see a few of you again in this year's cloud-init summit.\

-

16:28 <paulmey> Hi all, I'd like to request a review for this MP: https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742 (attached to LP: #1722959)

-

16:28 <ubot5> Launchpad bug 1722959 in cloud-init "Implement Key-Value Pair Telemetry for Azure" [Undecided,In progress] https://launchpad.net/bugs/1722959

-

16:29 <paulmey> Hoping we can get this merged sometime soon. :-)

-

16:29 <blackboxsw> Hi paulmey thanks for the ping on this.

-

16:29 <blackboxsw> #link https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742

-

16:30 <blackboxsw> #action rharper/blackboxsw close out on this review before cloud-init summit https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742

-

16:30 * meetingology rharper/blackboxsw close out on this review before cloud-init summit https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742

-

16:30 <blackboxsw> that has gotten dusty, thank you

-

16:31 <blackboxsw> I'll start a review in earnest now

-

16:31 <paulmey> Thanks. The dust is mostly mine... Andy has been working on this, but he's in a different time zone, so I'm still pushing it...

-

16:31 <paulmey> 😉

-

16:32 <blackboxsw> paulmey: I'll try spinning up an azure vm to test this out

-

16:34 <paulmey> let me know if you need anything

-

17:04 <blackboxsw> ok thanks folks for tuning in. See you next time

-

17:04 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2018-09-04.html b/status-2018-09-04.html deleted file mode 100644 index f13cf40..0000000 --- a/status-2018-09-04.html +++ /dev/null @@ -1,264 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Tue 04 September 2018 in status-meeting-minutes - - • 5 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/ - LINK: https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin - LINK: https://powersj.github.io/post/cloud-init-summit18/

-

In-progress Development

-

The discussion about "In-progress Development" started at 16:22.

- -

Office Hource (next ~30 mins)

-

The discussion about "Office Hource (next ~30 mins)" started at 16:30.

-

Active review queue scrub (and open discussion/office hours)

-

The discussion about "Active review queue scrub (and open discussion/office hours)" started at 16:41.

- -

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (60)
  • -
  • smoser (8)
  • -
  • meetingology (3)
  • -
  • marcoceppi (2)
  • -
  • ubot5 (1)
  • -
-

Full Log

-

16:08 <blackboxsw> #startmeeting Cloud-init bi-weekly status meeting

-

16:08 <meetingology> Meeting started Tue Sep 4 16:08:21 2018 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:08 <meetingology>

-

16:08 <meetingology> Available commands: action commands idea info link nick

-

16:08 <marcoceppi> rharper: oddly enough, that didn't work. root wasn't set

-

16:08 <marcoceppi> I'll bother you all after the meeting

-

16:08 <blackboxsw> or during marcoceppi :) sorry for the delay folks, I lost internet for a bit and just got it back up.

-

16:09 <blackboxsw> let's kickoff the bi-weekly status meeting and see what discussion we have for today

-

16:09 <blackboxsw> Our agenda is the following: Previous Actions, Recent Changes, In-progress development and office hours (~30 minutes)

-

16:09 <blackboxsw> #topic Previous Actions

-

16:10 <blackboxsw> the only logged action per last meeting was the following:

-

16:10 <blackboxsw> rharper/blackboxsw close out on this review before cloud-init summit https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742

-

16:11 <blackboxsw> we were able to land that branch at the cloud-init summit 2 weeks ago and also landed a followup fix for a lock race condition related to that changeset

-

16:11 <blackboxsw> so we can cross that one off the list

-

16:11 <blackboxsw> .... and for those following from home. our meeting minutes from the last status meeting are here

-

16:11 <blackboxsw> #link https://cloud-init.github.io/

-

16:13 <blackboxsw> Also generically we had a number of action items that came out of our Seattle cloud-init summit with various cloud and distribution partners. Our team will be having a review meeting to discuss some of those actions/decisions and ultimately convert them into trello work items on our board

-

16:13 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:16 <blackboxsw> #topic Recent Changes

-

16:17 <blackboxsw> Over the last couple weeks Microsoft hosted a very producting Cloud-init Summit conference in Seattle. A number of clouds and distribution vendors participated to set goals for the cloud-init upstream project. powersj wrote up a nice post to capture some of that work. Thank you all for partipating and helping to improve cloud-init

-

16:17 <blackboxsw> #link https://powersj.github.io/post/cloud-init-summit18/

-

16:19 <blackboxsw> also the following changes landed upstream:

-

16:21 <blackboxsw> - Add unit tests for config/cc_ssh.py [Francis Ginther]

-

16:21 <blackboxsw> - Fix the built-in cloudinit/tests/helpers:skipIf

-

16:21 <blackboxsw> - read-version: enhance error message [Joshua Powers]

-

16:21 <blackboxsw> - hyperv_reporting_handler: simplify threaded publisher

-

16:21 <blackboxsw> - VMWare: Fix a network config bug in vm with static IPv4 and no gateway.

-

16:21 <blackboxsw> [Pengpeng Sun] (LP: #1766538)

-

16:21 <blackboxsw> - logging: Add logging config type hyperv for reporting via Azure KVP

-

16:21 <blackboxsw> [Andy Liu]

-

16:21 <ubot5> Launchpad bug 1766538 in cloud-init (Ubuntu) "network customization with cloud-init does not work on Ubuntu18.04 Beta2 Server" [Medium,Confirmed] https://launchpad.net/bugs/1766538

-

16:22 <blackboxsw> #topic In-progress Development

-

16:23 <blackboxsw> as always, check our board if there are questions about what we are working on the cloud-init side of the house. any cloud-init cards will have a cloud-init label

-

16:23 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin?menu=filter&filter=cloud-init

-

16:24 <blackboxsw> we are working a couple of fixes for Oracle as well as the following features that could be interesting to folks:

-

16:24 <blackboxsw> - the ability to use jinja templating in cloud-config or user-scripts to reference any standardized instance meta data cloud-init consumes

-

16:26 <blackboxsw> - allowing new ssh user config in #cloud-config to specify a ssh-redirect-user, which would allow someone to disable an existing ssh user and provide a redirect message mentioning which username is the preferred default user

-

16:28 <blackboxsw> - ryan is working on refactoring the sysconfig renderer align multiple distros, so that we don't have slightly different implementations in cloud-init for each distribution

-

16:28 <blackboxsw> #link https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/353740

-

16:29 <blackboxsw> beyond that, there a number of new contibutions that have been generated by some of the amazon folks that we plan on reviewing and landing for better amazon linux support

-

16:30 <blackboxsw> thanks again for all the good work. I think we'll transition to the open forum for any discussion/feature/bug work.

-

16:30 <blackboxsw> #topic Office Hource (next ~30 mins)

-

16:31 <blackboxsw> we'll have eyes on this channel for the next 30 mins. any topic is acceptable; big or small. Bugs, discussions, features, complaints etc.

-

16:31 <smoser> o/

-

16:31 <blackboxsw> sorry for the interrupt earlier :)

-

16:40 <blackboxsw> Since we have a clear discussion docket for office hours... At the summit we decided maybe it would be a good idea to try reviewing our active review queue to keep the momentum going there and avoid stale branches sitting unresolved for a while.

-

16:41 <blackboxsw> smoser: rharper you gents up for taking a swing at our review queue in this forum to see if we can prioritize what needs landing/response etc?

-

16:41 <blackboxsw> #topic Active review queue scrub (and open discussion/office hours)

-

16:42 <smoser> sure.

-

16:42 <blackboxsw> I wanted to see if we could land Praveen's branch for Amazon linux support.

-

16:42 <blackboxsw> #link https://code.launchpad.net/~praween/cloud-init/+git/cloud-init/+merge/353733

-

16:42 <blackboxsw> their CI needs a new makefile target "sources"

-

16:43 <blackboxsw> I suggested that maybe they add that functionality into ./packages/brpm instead of just the commands on the cli

-

16:44 <blackboxsw> since we use brpm in our ci too. ....

-

16:44 <blackboxsw> Praveen had agreed at the summit to make some changes to extend brpm with a new cmdline option to do this work. But I don't see anything pushed. I'd like to mark this work in progress and comment to that affect. sound good?

-

16:46 <smoser> blackboxsw: that sounds good

-

16:49 <blackboxsw> smoser: ok https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/354001 I'll grab today after this meeting so we can land all the leaky unit tests. geez man

-

16:49 * blackboxsw grabs the review slot

-

16:50 <blackboxsw> I believe robert's branch is tabled until ryan's sysconfig branch is landed

-

16:50 <blackboxsw> #link https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904

-

16:50 <blackboxsw> ^ should we mark this 'work in progress' as it's blocked? or maybe just leave it in the active queue

-

16:51 <smoser> blackboxsw: your needs information still stands right?

-

16:51 <smoser> lets move it to work-in-progress and ask for response and also ask if it is sitll necessary (unless you know that it is or is not)

-

16:52 <smoser> and suggest that it will need to be re-worked.

-

16:53 <blackboxsw> smoser: that sounds good. my 'needs information' on that is resolved/read/discussed already. so I should abstain for the moment until the rework

-

16:57 <blackboxsw> ok couple more minutes... any additional reviews we should look at in earnest now?

-

16:58 <blackboxsw> I kinda want to hold on https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392 until we have our summit retro meeting today

-

16:59 <blackboxsw> here's a short one. https://code.launchpad.net/~otubo/cloud-init/+git/cloud-init/+merge/353436. should we mark this 'work in progress' until smoser's review comments are addressed and unit tests added?

-

16:59 <smoser> blackboxsw: yeah. i'll do that.

-

17:00 <blackboxsw> ok thanks. and I think that'll about wrap it for today. If we don't resolve the other community reviews by next status meeting, we can continue chipping away at this queue then.

-

17:01 <blackboxsw> I'll post the minutes to cloudinit.github.io just after this.

-

17:01 <smoser> blackboxsw: i'm loking at rharper's mp now for the system config

-

17:01 <blackboxsw> ok I'll get your review on https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/354001 now

-

17:01 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2018-09-25.html b/status-2018-09-25.html deleted file mode 100644 index e53ff4e..0000000 --- a/status-2018-09-25.html +++ /dev/null @@ -1,257 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Tue 25 September 2018 in status-meeting-minutes - - • 5 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:09.

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:10.

-

In-Progress development

-

The discussion about "In-Progress development" started at 16:15.

- -

18.4 Release Schedule

-

The discussion about "18.4 Release Schedule" started at 16:26.

- -

Office hours (next ~30 mins)

-

The discussion about "Office hours (next ~30 mins)" started at 16:31.

- -

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (54)
  • -
  • ubot5 (6)
  • -
  • meetingology (3)
  • -
  • rharper (2)
  • -
-

Full Log

-

16:05 <blackboxsw> #startmeeting Cloud-init bi-weekly status meeting

-

16:05 <meetingology> Meeting started Tue Sep 25 16:05:46 2018 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:05 <meetingology>

-

16:05 <meetingology> Available commands: action commands idea info link nick

-

16:06 <blackboxsw> Hi cloud-init folks, time to kickoff our bi-weekly(ish) status meeting. As mentioned on the mailing list we pushed this meeting out until today so we could have a discussion about the 18.4 upstream release which is scheduled for this Thursday.

-

16:07 <blackboxsw> I just updated the topic to reflect the 18.4 release date, Sept 27th EOD.

-

16:08 <blackboxsw> for today's meeting we have the following agenda: Previous Actions, Recent Changes, In-progress development and 18.4 release discussion/office hours/ (~30 minutes)

-

16:09 <blackboxsw> #topic Previous Actions

-

16:09 * blackboxsw reviews our notes from Sept11 @ https://cloud-init.github.io

-

16:10 <blackboxsw> No actions listed in previous meeting so we'll move to the next topic

-

16:10 <blackboxsw> #topic Recent Changes

-

16:12 <blackboxsw> Last week, we had some travel and planning discussions for cloud-init which took a few cycles out of our upstream landed content, but we were able to review and land a few items over the last couple weeks. Below is the list of changes that have landed in upstream cloud-init master. I expect we'll publish 18.4 release this week to Ubuntu Cosmic, so any changes below will be present in our next public release.

-

16:12 <blackboxsw> - pylint: ignore warning assignment-from-no-return for _write_network

-

16:12 <blackboxsw> - stages: Fix bug causing datasource to have incorrect sys_cfg.

-

16:12 <blackboxsw> (LP: #1787459)

-

16:12 <blackboxsw> - Remove dead-code _write_network distro implementations.

-

16:12 <blackboxsw> - net_util: ensure static configs have netmask in translate_network result

-

16:12 <blackboxsw> [Thomas Berger] (LP: #1792454)

-

16:12 <blackboxsw> - Fall back to root:root on syslog permissions if other options fail.

-

16:12 <ubot5> Ubuntu bug 1787459 in cloud-init (Ubuntu) "datasource.sys_cfg gets different values in local stage and after." [Medium,Confirmed]

-

16:12 <blackboxsw> [Robert Schweikert]

-

16:12 <blackboxsw> - tests: Add mock for util.get_hostname. [Robert Schweikert] (LP: #1792799)

-

16:12 <blackboxsw> - ds-identify: doc string cleanup.

-

16:12 <blackboxsw> - OpenStack: Support setting mac address on bond.

-

16:12 <ubot5> Ubuntu bug 1792454 in cloud-init "Network configuration broken for some distributions with OpenNebula, EC2, Azure" [High,Fix committed]

-

16:12 <blackboxsw> [Fabian Wiesel] (LP: #1682064)

-

16:12 <blackboxsw> - bash_completion/cloud-init: fix shell syntax error.

-

16:12 <ubot5> Ubuntu bug 1792799 in cloud-init "Host environment bleeds into test for mirror access testing" [Undecided,Fix committed]

-

16:12 <blackboxsw> - EphemeralIPv4Network: Be more explicit when adding default route.

-

16:12 <blackboxsw> (LP: #1792415)

-

16:12 <ubot5> Ubuntu bug 1682064 in cloud-init "cloud-init should support config bond mac address " [Medium,Fix committed]

-

16:12 <blackboxsw> - OpenStack: support reading of newer versions of metdata.

-

16:12 <blackboxsw> - OpenStack: fix bug causing 'latest' version to be used from network.

-

16:12 <blackboxsw> (LP: #1792157)

-

16:12 <ubot5> Ubuntu bug 1792415 in cloud-init (Ubuntu) "WARNINGs and failures in log on OVH public cloud" [Medium,Confirmed]

-

16:12 <ubot5> Ubuntu bug 1792157 in cloud-init (Ubuntu) "cloud-init uses openstack latest version due to decoding bug" [Medium,In progress]

-

16:13 <blackboxsw> Thank you again Robert, Thomas and Fabian for continued contributions to cloud-init upstream. Things are looking really good for the upcoming release

-

16:15 <blackboxsw> #topic In-Progress development

-

16:16 <blackboxsw> We are beating the drum toward the 18.4 release, as such, we are going to focus more on low-risk changes and bug fixes as we close in on the 18.4 upstream cutoff.

-

16:17 <blackboxsw> All of the work we have planned lives over on our trello board.

-

16:18 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:19 <blackboxsw> In our doing and review lane I expect we'll have a couple branches landing for standardizing and generalizing /run/cloud/instance-data.json on all clouds, and a couple of new cloud-init CLI commands 'cloud-init query' and 'cloud-id' to surface standardized instance-data on any cloud platform

-

16:20 <blackboxsw> post-18.4 release rharper has been doing some excellent work adding hotplug network support to OpenStack. I expect we'll be landing his branches shortly after we cut 18.4

-

16:21 <rharper> blackboxsw: thanks; it's been super interesting

-

16:21 <blackboxsw> this should give us an excellent example of reacting to changing metadata on a given platform, which hopefully other datasources will be able to adopt.

-

16:25 <blackboxsw> As far as additional content for the release, I'll also be circling an email around to the mailing list (cloud-init@lists.launchpad.net ) to describe existing instance data that cloud-init publishes. We are looking for input on common instance meta data that folks would like to see generalized across clouds.

-

16:26 <blackboxsw> I think about wraps up our current dev tasks.

-

16:26 <blackboxsw> #topic 18.4 Release Schedule

-

16:27 <blackboxsw> As mentioned earlier, we would like to cut 18.4 upstream release and tag it at end of day on Thursday, Sept 27th.

-

16:27 <blackboxsw> We will be looking at the active review queue for any branches with the 'Needs review' status.

-

16:28 <blackboxsw> #link https://code.launchpad.net/~cloud-init-dev/cloud-init/+git/cloud-init/+ref/master/+activereviews

-

16:28 <blackboxsw> If there are branches or bugs that you think need attention, please don't hesitate to mail the mailing list, or ping in this channel to get attention

-

16:29 <blackboxsw> After thursday, we'll be performing some additional manual and automated integration tests and we will plan on publishing 18.4 to Ubuntu Cosmic.

-

16:29 <blackboxsw> As a service, we also will publish that 18.4 release to the following copr repo for those centos-inclined individuals :)

-

16:30 <blackboxsw> #link https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/

-

16:30 <blackboxsw> For each upstream release we sync that release to the 'el-testing' repo.

-

16:31 <blackboxsw> Daily upstream snapshots are also available at https://copr.fedorainfracloud.org/coprs/g/cloud-init/cloud-init-dev/

-

16:31 <blackboxsw> #topic Office hours (next ~30 mins)

-

16:33 <blackboxsw> I think that about wraps the fire hose of content for our meeting. For the next 30 mins we should have eyes on this channel to discuss the finer points of life as well as anything cloud-init related. Bring your bugs, gripes, requests, reviews and/or discussions and we'll get a good answer for you.

-

16:33 * blackboxsw is going to hitup the review queue at the moment so see if there are some cloud-init branches we can clear out.

-

16:45 <rharper> +1

-

17:09 <blackboxsw> ok that about wraps it for today.

-

17:10 <blackboxsw> minutes will be published to the following link. Thanks again folks! See you next time

-

17:10 <blackboxsw> #link https://cloud-init.github.io

-

17:10 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2018-10-15.html b/status-2018-10-15.html deleted file mode 100644 index 771176f..0000000 --- a/status-2018-10-15.html +++ /dev/null @@ -1,331 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Mon 15 October 2018 in status-meeting-minutes - - • 9 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:18.

- -

Recent Changes

-

The discussion about "Recent Changes" started at 16:19.

- -

In-Progress Development

-

The discussion about "In-Progress Development" started at 16:28.

-
    -
  • LINK: trello.com/b/hFtWKUn3/daily-cloud-init-curtin
  • -
-

Office hours (next ~30 mins)

-

The discussion about "Office hours (next ~30 mins)" started at 16:35.

- -

Vote results

-

Action items, by person

- -

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (89)
  • -
  • paulmey (22)
  • -
  • ubot5 (13)
  • -
  • meetingology (5)
  • -
  • smoser (2)
  • -
-

Full Log

-

16:15 <blackboxsw> #startmeeting Cloud-init bi-weekly status

-

16:15 <meetingology> Meeting started Mon Oct 15 16:15:41 2018 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:15 <meetingology>

-

16:15 <meetingology> Available commands: action commands idea info link nick

-

16:17 <blackboxsw> hi guys and gals. Today marks a belated cloud-init status meeting we use to provide a forum where folks from the cloud-init community can keep up to date on latest cloud-init developments and tap a shoulder if bugs or features need discussion/attention.

-

16:17 <blackboxsw> Next meeting will be two weeks from now on October 29th. at 16:00 UTC (as in the topic of this channel)

-

16:18 <blackboxsw> Today's meeting will go through the typical topics: Previous Actions, Recent Changes, In-progress development and Office hours

-

16:18 <blackboxsw> #topic Previous Actions

-

16:19 <blackboxsw> No unresolved actions from last meeting on Sept 25th.

-

16:19 <blackboxsw> For those interested our previous meeting minutes are at the following:

-

16:19 <blackboxsw> #link https://cloud-init.github.io/

-

16:19 <blackboxsw> #topic Recent Changes

-

16:20 <blackboxsw> There has been a lot of work put into cloud-init over the last couple of weeks due to the timing of the Ubuntu Cosmic (18.10) series final freeze and release schedule

-

16:21 <blackboxsw> We managed to squeeze in a couple of features into 18.4 as well as improved some of Ubuntu's automated testing for StableReleaseUpdates (SRUs).

-

16:22 <blackboxsw> Beyond the 18.4 public upstream release (which is in Ubuntu Cosmic). We have the following commits that have landed since the last status meeting.

-

16:22 <blackboxsw> - tests: allow skipping an entire cloud_test without running.

-

16:22 <blackboxsw> - tests: disable lxd tests on cosmic

-

16:22 <blackboxsw> - cii-tests: use unittest2.SkipTest in ntp_chrony due to new deps

-

16:22 <blackboxsw> - lxd: adjust to snap installed lxd.

-

16:22 <blackboxsw> - docs: surface experimental doc in instance-data.json

-

16:22 <blackboxsw> - tests: fix ec2 integration tests. process meta_data instead of meta-data

-

16:22 <blackboxsw> - Add support for Infiniband network interfaces (IPoIB). [Mark Goddard]

-

16:22 <blackboxsw> - cli: add cloud-init query subcommand to query instance metadata

-

16:22 <blackboxsw> - tools/tox-venv: update for new features.

-

16:22 <blackboxsw> - pylint: ignore warning assignment-from-no-return for _write_network

-

16:22 <blackboxsw> - stages: Fix bug causing datasource to have incorrect sys_cfg.

-

16:22 <blackboxsw> (LP: #1787459)

-

16:22 <blackboxsw> - Remove dead-code _write_network distro implementations.

-

16:22 <blackboxsw> - net_util: ensure static configs have netmask in translate_network result

-

16:22 <blackboxsw> [Thomas Berger] (LP: #1792454)

-

16:22 <ubot5> Ubuntu bug 1787459 in cloud-init (Ubuntu) "datasource.sys_cfg gets different values in local stage and after." [Medium,Fix released]

-

16:22 <blackboxsw> - Fall back to root:root on syslog permissions if other options fail.

-

16:22 <blackboxsw> [Robert Schweikert]

-

16:22 <ubot5> Ubuntu bug 1792454 in cloud-init "Network configuration broken for some distributions with OpenNebula, EC2, Azure" [High,Fix released]

-

16:22 <blackboxsw> - tests: Add mock for util.get_hostname. [Robert Schweikert] (LP: #1792799)

-

16:22 <blackboxsw> - ds-identify: doc string cleanup.

-

16:22 <ubot5> Ubuntu bug 1792799 in cloud-init "Host environment bleeds into test for mirror access testing" [Undecided,Fix released]

-

16:22 <blackboxsw> - OpenStack: Support setting mac address on bond.

-

16:22 <blackboxsw> - bash_completion/cloud-init: fix shell syntax error.

-

16:22 <blackboxsw> - EphemeralIPv4Network: Be more explicit when adding default route.

-

16:22 <blackboxsw> (LP: #1792415)

-

16:22 <blackboxsw> - OpenStack: support reading of newer versions of metdata.

-

16:22 <blackboxsw> - OpenStack: fix bug causing 'latest' version to be used from network.

-

16:22 <ubot5> Ubuntu bug 1792415 in cloud-init (Ubuntu) "WARNINGs and failures in log on OVH public cloud" [Medium,Fix released]

-

16:22 <blackboxsw> (LP: #1792157)

-

16:22 <ubot5> Ubuntu bug 1792157 in cloud-init (Ubuntu) "cloud-init uses openstack latest version due to decoding bug" [Medium,Fix released]

-

16:23 <blackboxsw> - Correct spelling in an error message (udevadm). [Katie McLaughlin]

-

16:23 <blackboxsw> - tests: meta_data key changed to meta-data in ec2 instance-data.json

-

16:23 <blackboxsw> (LP: #1797231)

-

16:23 <blackboxsw> - tests: fix kvm integration test to assert flexible config-disk path

-

16:23 <blackboxsw> (LP: #1797199)

-

16:23 <blackboxsw> - tools: Add cloud-id command line utility

-

16:23 <blackboxsw> - instance-data: Add standard keys platform and subplatform. Refactor ec2.

-

16:23 <blackboxsw> - net: ignore nics that have "zero" mac address. (LP: #1796917)

-

16:23 <blackboxsw> - tests: fix apt_configure_primary to be more flexible

-

16:23 <ubot5> Ubuntu bug 1797231 in cloud-init "ec2 integration test failure on changed instance-data.json" [High,Fix committed]

-

16:23 <blackboxsw> - Ubuntu: update sources.list to comment out deb-src entries. (LP: #74747)

-

16:23 <blackboxsw> - release 18.4 (LP: #1795741)

-

16:23 <ubot5> Ubuntu bug 1797199 in cloud-init "kvm integration test failures due to invalid config-disk path" [High,Fix committed]

-

16:23 <ubot5> Ubuntu bug 1796917 in cloud-images "cloud-init fails to run on latest cosmic minimal image" [High,Fix released]

-

16:23 <ubot5> Ubuntu bug 74747 in cloud-init (Ubuntu Bionic) "Default sources.list file has source packages enabled by default" [Medium,Confirmed]

-

16:23 <ubot5> Ubuntu bug 1795741 in cloud-init (Ubuntu) "Release 18.4" [Medium,Fix released]

-

16:26 <blackboxsw> If you get a chance, it's worth noting that #cloud-config files can now be presented as a jinja template to the instance by adding a ## template: jinja as the first line above the #cloud-config in your user-data. Any metadata that cloud-init consumes (like cloud-given hostnames, ip addresses, region names etc) can be sourced and rendered in your cloud-config files now.

-

16:27 <blackboxsw> #link https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html#using-instance-data

-

16:27 <blackboxsw> ^ for more information on instance data and templating

-

16:28 <blackboxsw> #topic In-Progress Development

-

16:28 <blackboxsw> #link trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:29 <blackboxsw> Our trello board tracks our current work. The most notable effort is cloud-init network hotplug handling for datasources which is currently being driven by rharper

-

16:30 <blackboxsw> What he is adding is the ability for for a datasource to be configured react to network hotplug events and apply cloud-init determined network configuration on device add/remove

-

16:31 <blackboxsw> This feature will be opt-in and configurable by the end-user to allow cloud-init to own network for any device added or removed after the initial boot. This feature will debut in OpenStack clouds and will shortly be adopted by other cloud/datasource types.

-

16:33 <blackboxsw> Also, smoser and I will be heading to OpenSource Summit Europe next week in Edinburgh, UK. https://events.linuxfoundation.org/events/open-source-summit-europe-2018/

-

16:34 <blackboxsw> If you are in town come say hi :)

-

16:35 <blackboxsw> Without further ado, I think that about wraps our status for today

-

16:35 <blackboxsw> #topic Office hours (next ~30 mins)

-

16:37 <blackboxsw> Almost forgot; as part of the SRU process for for cloud-init to release into Xenial and Bionic, we'll be doing some additional manual and automated testing of cloud-init version 18.4 before publishing to those LTS series. I expect that'll take up a bit of our time this week and next as there is a lot to verify for that release.

-

16:38 <blackboxsw> For the next 30 mins, a few of us will have eyes on the channel for anyone with a desire to talk cloud-init bugs, features or reviews. Thanks again for the contributions and making cloud-init better!

-

16:40 <paulmey> Hi blackboxsw

-

16:41 <blackboxsw> Hi paulmey, how're things

-

16:41 <blackboxsw> ?

-

16:41 <paulmey> Good! How about yourself?

-

16:41 <paulmey> My buddy Jason has a bug open that could use some attention: https://bugs.launchpad.net/cloud-init/+bug/1794399

-

16:41 <ubot5> Ubuntu bug 1794399 in cloud-init "cloud-init dhcp_discovery() crashes on preprovisioned RHEL 7.6 VM in Azure" [Undecided,New]

-

16:41 <paulmey> this is a stopgap fix until we have a pure-python dhcp client

-

16:42 <blackboxsw> it's been a push for the Cosmic release for us, racing to get things sorted, but I think we are on the other side of any fires now :)

-

16:42 <blackboxsw> ahh checking that bug

-

16:42 <paulmey> :-) good to hear that

-

16:42 <paulmey> it's basically just some more robustness around the handling of dhclient execution

-

16:44 <paulmey> it reproed very reliably on RHEL with reprovisioning (changing network etc., maybe slower/faster dhcp response?), but pretty unreproducible outside of that...

-

16:44 <blackboxsw> paulmey: jason made reference to a patch, but I don't see it linked to the bug.... I'm checking the review queue now

-

16:44 <paulmey> we saw cloud-init killing or trying to kill the initial process (which has already finished after the util exec)

-

16:45 <blackboxsw> was that bug just a request for us to make cloud-init more resilient in light of forking, or a request to accept a patch

-

16:45 <paulmey> let me link the patch... once I find it :-)

-

16:45 <paulmey> give me a minute

-

16:46 * blackboxsw documents the link for the meeting bot

-

16:46 <blackboxsw> #link https://bugs.launchpad.net/cloud-init/+bug/1794399

-

16:46 <ubot5> Ubuntu bug 1794399 in cloud-init "cloud-init dhcp_discovery() crashes on preprovisioned RHEL 7.6 VM in Azure" [Undecided,New]

-

16:46 * blackboxsw Sort and review azure RHEL branch related to ephemeral dhcp handling of dhclient https://bugs.launchpad.net/cloud-init/+bug/1794399

-

16:47 <blackboxsw> #action Sort and review azure RHEL branch related to ephemeral dhcp handling of dhclient https://bugs.launchpad.net/cloud-init/+bug/1794399

-

16:47 * meetingology Sort and review azure RHEL branch related to ephemeral dhcp handling of dhclient https://bugs.launchpad.net/cloud-init/+bug/1794399

-

16:48 <blackboxsw> yeah, I wonder if now that 18.4 is cut and released if we want to start banging the drum to get our scapy-based dhclient solution landed in cloud-init proper so we don't have to patchup the ephemeral dhcp work in cloud-init.

-

16:50 <blackboxsw> while you look paulmey, I'll make sure we talk at our standups about what we can do with cloud-init's own dhcp-discovery so we don't have to handle different distro implementations of dhclient. The sandboxed dhclient solution we have felt dirty in the first place.

-

16:51 <paulmey> yar... I can't find a reference to it in my mails... I'll need to circle back with Jason. I prototyped the patch and he write some unit tests. I know it's somewhere, just not exactly where...

-

16:51 <blackboxsw> our only concern I thought with using scapy was adding the additional package dependency, (which we wouldn't be able to get released back into Ubuntu Xenial Bionic or Cosmic). But, we can resolve to come of with an approach for the nearterm

-

16:52 <blackboxsw> paulmey: sounds good. :) care if I add a virtual action item for you too to the meeting minutes

-

16:52 <paulmey> Sure, no problem

-

16:52 <blackboxsw> at least it'll guarantee we make progress before next meeting

-

16:52 <blackboxsw> #action paulmey to dig up reference to proposed patch for https://bugs.launchpad.net/cloud-init/+bug/1794399

-

16:52 * meetingology paulmey to dig up reference to proposed patch for https://bugs.launchpad.net/cloud-init/+bug/1794399

-

16:52 <ubot5> Ubuntu bug 1794399 in cloud-init "cloud-init dhcp_discovery() crashes on preprovisioned RHEL 7.6 VM in Azure" [Undecided,New]

-

16:52 <blackboxsw> thanks

-

16:53 <blackboxsw> paulmey: are there other azure related discussions/features that are collecting dust with us that you know of?

-

16:54 <paulmey> not yet collecting dust, but I know that Sushant Sharma is going to be coming with some networking-related updates for pre-provisioning like we discussed at the summit

-

16:54 <paulmey> he's testing those on real systems right now

-

16:54 <blackboxsw> I know hyperv reporting feature is functional in cloud-init now. and that folks are instrumenting changes in images to support that.

-

16:55 <blackboxsw> ahh right. good to hear

-

16:55 <paulmey> we're also talking to SUSE this week to see what the next steps are to get cloud-init functional on Azure

-

16:55 <blackboxsw> ohh neat!

-

16:56 <paulmey> I know we still have some work items, but we're prototyping some stuff to get ahead of some testing work

-

16:56 <paulmey> funny thing is that I'm hardly doing any of this work. :-)

-

16:56 <paulmey> good to see more and more people at MS doing work on cloud-init

-

16:57 <blackboxsw> heh, juggling a lot I'm sure. yeah it is nice to see more devs involved

-

16:58 <smoser> paulmey: thats great to hear wrt suse

-

16:58 <paulmey> ok, cool. I'll follow up with Jason and circle back. If anything else comes to fruition before the 29th, I'll send people here to evangalize

-

16:59 <blackboxsw> perfect. Thanks again paulmey

-

16:59 <smoser> and /me agrees it'd be good to have a dhclient in cloud-init for what we need it for. scapy or other.

-

16:59 <blackboxsw> think I'll wrap up this meeting for today

-

16:59 <paulmey> (although it's always nice to talk to you guys... feels good being able to say was on IRC this week... :-P)

-

16:59 <paulmey> sgtm

-

16:59 <blackboxsw> heh, take care

-

16:59 <paulmey> ttyl

-

17:00 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2018-10-29.html b/status-2018-10-29.html deleted file mode 100644 index b81225f..0000000 --- a/status-2018-10-29.html +++ /dev/null @@ -1,253 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Mon 29 October 2018 in status-meeting-minutes - - • 4 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:22.

- -

Recent Changes

-

The discussion about "Recent Changes" started at 16:28.

- -

In-Progress Development

-

The discussion about "In-Progress Development" started at 16:38.

- -

Office hours (next ~30 mins)

-

The discussion about "Office hours (next ~30 mins)" started at 16:44.

- -

Vote results

-

Action items, by person

- -

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (46)
  • -
  • meetingology (5)
  • -
  • ubot5 (4)
  • -
-

Full Log

-

16:21 <blackboxsw> #startmeeting Cloud-init bi-weekly status

-

16:21 <meetingology> Meeting started Mon Oct 29 16:21:16 2018 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:21 <meetingology>

-

16:21 <meetingology> Available commands: action commands idea info link nick

-

16:22 <blackboxsw> hi folks, now marks a 20 minute belated cloud-init status meeting, an opportunity to chat about current and future cloud-init happenings.

-

16:22 <blackboxsw> Today's meeting will go through the typical topics: Previous Actions, Recent Changes, In-progress development and Office hours

-

16:22 <blackboxsw> #topic Previous Actions

-

16:23 <blackboxsw> Looking over our last meeting minutes, we had a single action

-

16:23 <blackboxsw> #link https://cloud-init.github.io/status-2018-10-15.html#status-2018-10-15

-

16:24 <blackboxsw> #action Sort and review azure RHEL branch related to ephemeral dhcp handling of dhclient https://bugs.launchpad.net/cloud-init/+bug/1794399

-

16:24 * meetingology Sort and review azure RHEL branch related to ephemeral dhcp handling of dhclient https://bugs.launchpad.net/cloud-init/+bug/1794399

-

16:24 <ubot5> Ubuntu bug 1794399 in cloud-init "cloud-init dhcp_discovery() crashes on preprovisioned RHEL 7.6 VM in Azure" [Undecided,New]

-

16:25 <blackboxsw> the meeting later showed us we didn't really have a branch referencing that bug, looks like paulmey was able to follow up there to tie the related branch to the bug. So we have something to review now

-

16:27 <blackboxsw> So looks like this is a carryover from last meeting, thanks Paul for tying the branch to this bug so we have something to review related to it. The branch is currently waiting on review feedback from cloud-init upstream. So, I'll pull it in for us to review this week

-

16:27 <blackboxsw> #action blackboxsw, rharper smoser a review on https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427 before next status meeting for Azure dhcp.

-

16:27 * meetingology blackboxsw, rharper smoser a review on https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427 before next status meeting for Azure dhcp.

-

16:28 <blackboxsw> #topic Recent Changes

-

16:29 <blackboxsw> over the last week, a number of us have been travelling at either planning meetings for cloud-init or the OpenSource Summit in Europe.

-

16:29 <blackboxsw> #link https://events.linuxfoundation.org/events/open-source-summit-europe-2018/

-

16:30 <blackboxsw> The cloud-init talk had a pretty good turn out at OSS EU. I think we had ~ 100 people in attendance and some good questions about potential support of the following:

-

16:31 <blackboxsw> - Ansible and CFEgine config module support in cloud-initt

-

16:32 <blackboxsw> - better netplan config use-case handling

-

16:33 <blackboxsw> - better vmware integration as well as a request for proxmox (opensource alternative to vmware?) support

-

16:34 <blackboxsw> thanks smoser for a job well done on that talk.

-

16:35 <blackboxsw> beyond the conference highlight, cloud-init tip is being published to Xenial and Bionic on Ubuntu.

-

16:36 <blackboxsw> Expect to see updates published in today's images that will handle template-support for #cloud-config and user-data scripts and generalized instance-data.json on most recent Ubuntu releases.

-

16:36 <blackboxsw> tip of cloud-init has seen the following changes merged:

-

16:36 <blackboxsw> - instance-data: fallback to instance-data.json if sensitive is absent.

-

16:36 <blackboxsw> (LP: #1798189)

-

16:36 <blackboxsw> - docs: remove colon from network v1 config example. [Tomer Cohen]

-

16:36 <blackboxsw> - Add cloud-id binary to packages for SUSE [Jason Zions]

-

16:36 <blackboxsw> - systemd: On SUSE ensure cloud-init.service runs before wicked

-

16:36 <blackboxsw> [Robert Schweikert] (LP: #1799709)

-

16:36 <blackboxsw> - update detection of openSUSE variants [Robert Schweikert]

-

16:36 <blackboxsw> - azure: Add apply_network_config option to disable network from IMDS

-

16:36 <blackboxsw> (LP: #1798424)

-

16:36 <ubot5> Ubuntu bug 1798189 in cloud-init "cloud-init query: /run/cloud/instance-data-sensitive.json not generated on upgrade" [Medium,Fix committed]

-

16:36 <ubot5> Ubuntu bug 1799709 in cloud-init "service order is incorrect for SUSE distros" [Undecided,Fix committed]

-

16:36 <ubot5> Ubuntu bug 1798424 in cloud-init (Ubuntu) "Xenial Azure: Make generation of network config from IMDS hotplug scripts configurable opt-in" [Undecided,New]

-

16:37 <blackboxsw> Thanks robjo for the commitment to keeping SuSE up to date and fully functional with cloud-init.

-

16:38 <blackboxsw> And thanks Jason and Tomer for the contributions to packaging and docs as well

-

16:38 <blackboxsw> Think that about wraps Recent Changes topic....

-

16:38 <blackboxsw> #topic In-Progress Development

-

16:39 <blackboxsw> Check out trello board for a prioritized order of what upstream is working

-

16:39 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:41 <blackboxsw> There are a couple of community branches in the wings that we'll get reviews on and shepherd into cloud-init proper. Azure has some work to increase efficiency of the detection and reporting during initial boot.

-

16:42 <blackboxsw> smoser is working on supplemental work with meena to handle platform-specializing our cloudinit.net module.

-

16:43 <blackboxsw> and I think we have a couple of branches pulled together for legacy centos6 build support and supporting Azure Gen2 vms.

-

16:43 <blackboxsw> We'll keep the trello board updated as big items come down the pipeline for us.

-

16:44 <blackboxsw> #topic Office hours (next ~30 mins)

-

16:44 <blackboxsw> so eyes will float on this channel a bit for any questions, concerns, bugs or features.

-

16:45 <blackboxsw> thanks again for your time and contributions folks.

-

17:09 <blackboxsw> alright. guess I'll call it wrap for this meeting. You can tune in to minutes on published github to browse any content that has been discussed at previous status meetings.

-

17:09 <blackboxsw> #link https://cloud-init.github.io/

-

17:09 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2018-11-12.html b/status-2018-11-12.html deleted file mode 100644 index a49ef3c..0000000 --- a/status-2018-11-12.html +++ /dev/null @@ -1,250 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Mon 12 November 2018 in status-meeting-minutes - - • 4 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:20.

- -

Recent Changes

-

The discussion about "Recent Changes" started at 16:24.

-

In-progress Development

-

The discussion about "In-progress Development" started at 16:30.

- -

Office Hours (next ~30 minutes)

-

The discussion about "Office Hours (next ~30 minutes)" started at 16:40.

- -

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (53)
  • -
  • ubot5 (3)
  • -
  • meetingology (3)
  • -
-

Full Log

-

16:17 <blackboxsw> #startmeeting Cloud-init bi-weekly status

-

16:17 <meetingology> Meeting started Mon Nov 12 16:17:50 2018 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:17 <meetingology>

-

16:17 <meetingology> Available commands: action commands idea info link nick

-

16:18 <blackboxsw> Morning/afternoon folks. Time for another brief episode of cloud-init upstream updates

-

16:18 <blackboxsw> Last meeting was 10/29 and meeting minutes live over on github

-

16:18 <blackboxsw> #link https://cloud-init.github.io/

-

16:20 <blackboxsw> This meeting is an open forum for cloud-init discussions and status updates, feel free to interject at any time. It really is just a venue by which we can make sure we all have eyes and ears available for discussion on features, bugs or branches if needed.

-

16:20 <blackboxsw> Generally we go through the following topics: Previous Actions, Recent Changes, In-progress Development, and Office hours

-

16:20 <blackboxsw> #toic Previous Actions

-

16:20 <blackboxsw> #topic Previous Actions

-

16:21 <blackboxsw> So last meeting we carried in one action, to review the following Azure branch related to DHCP and RHEL race conditions

-

16:21 <blackboxsw> https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427

-

16:22 <blackboxsw> Looks like rharper got a review in and I don't see any updates from Jason Zion (author) in response to that branch

-

16:22 <blackboxsw> thanks rharper

-

16:22 <blackboxsw> I'm marking that branch as 'Work in progress' and commenting that the author should set it back to 'Needs review' when comments have been addressed

-

16:24 <blackboxsw> ok done. No further actions seen

-

16:24 <blackboxsw> #topic Recent Changes

-

16:24 * blackboxsw digs up changes since 10/28

-

16:29 <blackboxsw> sorry interrupted.

-

16:29 <blackboxsw> Here are the changes committed:

-

16:29 <blackboxsw> - azure: add udev rules to create cloud-init Gen2 disk name symlinks

-

16:29 <blackboxsw> (LP: #1797480)

-

16:29 <blackboxsw> - tests: ec2 mock missing httpretty user-data and instance-identity routes

-

16:29 <blackboxsw> - azure: remove /etc/netplan/90-hotplug-azure.yaml when net from IMDS

-

16:29 <blackboxsw> - azure: report ready to fabric after reprovision and reduce logging

-

16:29 <blackboxsw> [asakkurr] (LP: #1799594)

-

16:29 <blackboxsw> - query: better error when missing read permission on instance-data

-

16:29 <ubot5> Ubuntu bug 1797480 in cloud-init "Azure: Support ephemeral disk handling on Gen2 VMs" [High,Fix committed]

-

16:29 <ubot5> Ubuntu bug 1799594 in cloud-init "Azure - Report ready during preprovisioning as soon as we get the ReprovisionData" [Undecided,Fix committed]

-

16:29 <blackboxsw> As you can see we are seeing a bit of momentum on azure datasource and some continuous integration cleanup on our side.

-

16:30 <blackboxsw> Thanks asakkurr for pulling that Azure branch together

-

16:30 <blackboxsw> #topic In-progress Development

-

16:31 <blackboxsw> We track our current cloud-init development publicly on trello

-

16:31 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:31 <blackboxsw> if there are any questions about certain branches or work feel free to comment in channel or on the linked branches we document there.

-

16:32 <blackboxsw> It looks like the Ubuntu archive for Disco Dingo series is open, so we'll likely be pushing an upload of tip of cloud-init by EOD today to get a new release queued

-

16:33 <blackboxsw> Also to note, I'd like to see us land https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/358112 to fix an Azure retry on IMDS timeout to avoid cloud-init giving up if the instance boots while IMDS service is down or temporarily unavailable (I've only seen this once on any azure instance)

-

16:33 <blackboxsw> #link https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/358112

-

16:35 <blackboxsw> we also have a fairly deep review queue, so we'll be attacking that in the 2nd half of today's meeting to clear out and respond to some of those merge proposals

-

16:36 <blackboxsw> I also think we have some mailing list threads to start responding to per usage of EphemeralDHCPv4 and EphemeralIPv4Network context managers.

-

16:37 <blackboxsw> I think the intent there should be that those context managers ensure that they setup whatever requested network configuration is misssing from a network interface.... so if an interface is 'down' yet has correct address configured, ephemeral* will make sure it is in operable 'up' state .

-

16:37 <blackboxsw> See the following bug for more information:

-

16:38 <blackboxsw> #link https://bugs.launchpad.net/cloud-init/+bug/1802598

-

16:38 <ubot5> Ubuntu bug 1802598 in cloud-init "EphemeralIPv4Network: when device has requested existing network config, but link is down, network setup does not bring link up" [Undecided,New]

-

16:39 <blackboxsw> I believe that about wraps it for current in-flight work. I'll drop us into office hours at the point

-

16:40 <blackboxsw> #topic Office Hours (next ~30 minutes)

-

16:40 <blackboxsw> Cloud-init upstream folks will have eyes on this channel for any discussions. requests, bugs or features folks want to discuss.

-

16:40 <blackboxsw> I'll spend most of this time on reviews to start to clear our review queue (or at least get some responses out to folks for more information)(

-

17:03 <blackboxsw> ok looks like https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357669 is ready for landing. Just kicking off a CI test run on it

-

17:04 <blackboxsw> also the approved version of this branch didn't actually match what Jenkins autolander expected, I've kick the jenkins landing job that should truly land that branch now. https://code.launchpad.net/~asakkurr/cloud-init/+git/cloud-init/+merge/358422'

-

17:25 <blackboxsw> #link https://code.launchpad.net/~i.galic/cloud-init/+git/cloud-init/+merge/357723

-

17:25 <blackboxsw> ok just got through an initial review there too.

-

17:26 <blackboxsw> ok looks like our lander merged https://code.launchpad.net/~asakkurr/cloud-init/+git/cloud-init/+merge/358422

-

17:26 <blackboxsw> and :( https://jenkins.ubuntu.com/server/job/cloud-init-ci/431/console the CI on jason zion

-

17:27 <blackboxsw> and :( https://jenkins.ubuntu.com/server/job/cloud-init-ci/431/console the CI on jason zion's branch will take 9 hrs and 51 minutes (because it doesn't have our CI fix for leaked test_ec2 link local unittests which take forever to timeout

-

17:27 <blackboxsw> ok will that about wraps today's status meeting

-

17:27 <blackboxsw> thanks all

-

17:27 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2018-11-26.html b/status-2018-11-26.html deleted file mode 100644 index 40e6b39..0000000 --- a/status-2018-11-26.html +++ /dev/null @@ -1,270 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Mon 26 November 2018 in status-meeting-minutes - - • 6 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io - LINK: https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427 - LINK: https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/358881 - LINK: chttps://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392 - LINK: https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:29.

-

In-Progress Development

-

The discussion about "In-Progress Development" started at 16:33.

- -

Office Hours (next ~30 minutes)

-

The discussion about "Office Hours (next ~30 minutes)" started at 16:45.

-

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (64)
  • -
  • meena (10)
  • -
  • rharper (4)
  • -
  • meetingology (3)
  • -
  • ubot5 (2)
  • -
-

Full Log

-

16:18 <blackboxsw> #startmeeting Cloud-init bi-weekly status

-

16:18 <meetingology> Meeting started Mon Nov 26 16:18:39 2018 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:18 <meetingology>

-

16:18 <meetingology> Available commands: action commands idea info link nick

-

16:18 <blackboxsw> Morning/Afternoon folks. welcome to another cloud-init status meeting

-

16:20 <blackboxsw> ... our open forum to advertise current cloud-init developments, giving an opportunity to discuss bugs or features in cloud-init and provide a touch point for the community

-

16:20 <blackboxsw> Generally we go through the following topics: Previous Actions, Recent Changes, In-progress Development, and Office hours

-

16:20 <blackboxsw> #topic Previous Actions

-

16:20 <blackboxsw> our last meeting's minutes are located here

-

16:21 <blackboxsw> #link https://cloud-init.github.io

-

16:21 <blackboxsw> only thing we carried into that meeting is a an review

-

16:21 <blackboxsw> #link https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427

-

16:22 <blackboxsw> rharper: had closed out feedback on the review. with a needs fixing. I did see some followup commits there from the author Jason Zion.

-

16:23 <blackboxsw> I think we need to take a look at this again and see if our comments were addressed, I'm marking it "Needs review"

-

16:24 <blackboxsw> I see no other actions carried over... but there was talk last week about a couple of branches so let's add these

-

16:25 <blackboxsw> #link https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/358881

-

16:25 <blackboxsw> ^ disco support

-

16:25 <blackboxsw> #link chttps://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392

-

16:25 <blackboxsw> #link https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392

-

16:25 <blackboxsw> ^ Azure netlink listener

-

16:26 <blackboxsw> ok next topic

-

16:29 <blackboxsw> #topic Recent Changes

-

16:30 <blackboxsw> - azure: _poll_imds only retry on 404. Fail on Timeout

-

16:30 <blackboxsw> (LP: #1803598)

-

16:30 <blackboxsw> - resizefs: Prefix discovered devpath with '/dev/' when path does not

-

16:30 <blackboxsw> exist [Igor Galić]

-

16:30 <ubot5> Ubuntu bug 1803598 in cloud-init "Do not retry polling IMDS for reprovisiondata during timeout" [Undecided,Fix committed]

-

16:30 <blackboxsw> t'was a slow week with all that Thanksgiving holiday stuff for US-based employees

-

16:30 <blackboxsw> welcome back from the Holidays boys and girls

-

16:31 <blackboxsw> also we were able to publish tip of cloud-init to Ubuntu Disco series

-

16:32 <blackboxsw> cloud-init 18.4-24-g8f812a15-0ubuntu1 has latest and greatest as seen on tip of master

-

16:33 <blackboxsw> #topic In-Progress Development

-

16:33 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:34 <blackboxsw> Our trello board tracks our queued and current work for cloud-init, feel free to watch that board for updates on significant cloud-init features/bug-fixes

-

16:34 <blackboxsw> what generally isn't tracked there is reviews on community authored branches

-

16:36 <blackboxsw> per community driven content, we have a number of branches from meena for better FreeBSD support in flight. Great work! and some Azure platform development to react to netlink events during the preprovisioning state.

-

16:36 <blackboxsw> thanks tamilmani_ on the azure work.

-

16:39 <blackboxsw> As a heads up to folks, we are trying to cut an upstream release of cloud-init 18.5 on 12/15/2018. So if there are branches you want to see landed or bugs you need fixed please holler here in this channel or on the mailing list to:cloud-init.lists.launchpad.net

-

16:39 <blackboxsw> We'll send an email to the mailing list requesting for input on the release as well

-

16:39 <meena> >blackboxsw what generally isn't tracked there is reviews on community authored branches<== i did check there first time around, but found nothing that was topical for me

-

16:41 <blackboxsw> Correct meena . I used to capture outstanding community reviews that needed review follow up, but that ended up being out of date all the time. It was easier for us to just use launchpad active review queue instead

-

16:43 <blackboxsw> Now we've tried to adopt the setting of a branch status to 'work in progress' if we are expecting feedback/fixes from the author. And have the author set it back to 'needs review' when it is ready for another round of upstream reviews

-

16:44 <blackboxsw> having trello cards was basically just duplicating what launchpad reviews were designed for, we just need to be more vigilant about grooming the review queue and getting folks the feedback they need

-

16:45 <blackboxsw> might as well switch over to office hours for open discussion etc.

-

16:45 <blackboxsw> #topic Office Hours (next ~30 minutes)

-

16:45 <blackboxsw> Cloud-init upstream folks will have eyes on this channel for any discussions. requests, bugs or features folks want to discuss.

-

16:45 <blackboxsw> we'll also spend some time actively grooming the branch review queue to see if we can clear out some review debyt

-

16:45 <blackboxsw> we'll also spend some time actively grooming the branch review queue to see if we can clear out some review debt

-

16:46 <blackboxsw> I think smoser mentioned at our team standup this morning he was taking one more review on https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392

-

16:47 <blackboxsw> rharper: if you are done with your review on that tamilmani_ branch can you add a comment that doesn't leave it in "Needs fixing" review state from yoiu?

-

16:48 <rharper> blackboxsw: yes, I'm adding a commit message now, and I'll leave a comment marking approve;

-

16:48 <blackboxsw> excellent.

-

16:48 <blackboxsw> I'm going to give a review to https://code.launchpad.net/~i.galic/cloud-init/+git/cloud-init/+merge/358876 now

-

16:48 * blackboxsw claims a review slot

-

16:49 <rharper> blackboxsw: did we have a LP for thisone ?

-

16:49 <rharper> the netlink ?

-

16:52 <blackboxsw> ohh, no we did not I don't think.

-

16:52 <blackboxsw> I'll check

-

16:56 <meena> blackboxsw: i think my (our) patch is ready to be merged

-

16:57 <blackboxsw> rharper: yeah didn't find any bug filed related to Azure and dhcp leak or netlink response etc.

-

16:57 <meena> (the feature / fix of adding connectivity check to ephemeral network stuff)

-

16:58 <blackboxsw> meena: I think so too. Was just dusting off my memory on that one. I'm going to do a quick test run of setup/teardown and I think that's good. +1

-

16:58 <blackboxsw> thanks again

-

16:58 <meena> once that's merged, I'll have a much easier time with splitting out the freebsd network

-

16:59 <meena> blackboxsw: thank you for showing me how to do the tests properly

-

16:59 <blackboxsw> most welcome.

-

17:00 <rharper> blackboxsw: thanks, me neither; I just didn't want to miss a LP: in the commit message if we had one

-

17:01 <blackboxsw> after this branch lands and tamilmani_'s I probably will go through the motions of us publishing to Ubuntu Disco again, because I want to get a round or two of integration tests on both Azure and AWS with both the ephemeral* changes and the netlink stuff on pristine cloud-images before next week's release

-

17:06 <blackboxsw> meena: you didn't file a bug related to the ephermeraldhcp network connectivity did you? (I'm just double checking as I don't see one)

-

17:07 <blackboxsw> meena: not needed, just didn't want to miss it if it was there (as we'd want to link it in the commit message)

-

17:08 <meena> blackboxsw: nah, we just "filed" a mailing list thread

-

17:08 <blackboxsw> all good thanks

-

17:09 <blackboxsw> ok I had filed https://bugs.launchpad.net/cloud-init/+bug/1802598 but we won't tie that to this branch

-

17:09 <ubot5> Ubuntu bug 1802598 in cloud-init "EphemeralIPv4Network: when device has requested existing network config, but link is down, network setup does not bring link up" [Undecided,Triaged]

-

17:09 <blackboxsw> it's a bit more about idempotent behavior

-

17:13 <meena> nod nod

-

17:13 <meena> i didn't think i had fixed it, so i didn't connect them.

-

17:16 <blackboxsw> +1 on your branch meena, it should land within the hour. Just tested it out one more time

-

17:16 <meena> cool

-

17:16 <blackboxsw> ok I think that about wraps today's meeting timewise. Thanks again for the chat meena.

-

17:16 <meena> \o/

-

17:17 <blackboxsw> next meeting is Dec 10, 2018 sameish time

-

17:17 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2018-12-10.html b/status-2018-12-10.html deleted file mode 100644 index 13ddbee..0000000 --- a/status-2018-12-10.html +++ /dev/null @@ -1,254 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Mon 10 December 2018 in status-meeting-minutes - - • 4 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:13.

- -

Recent Changes

-

The discussion about "Recent Changes" started at 16:19.

-

In-Progress Development

-

The discussion about "In-Progress Development" started at 16:24.

- -

Cloud-init upstream Release 18.5

-

The discussion about "Cloud-init upstream Release 18.5" started at 16:27.

-

Office Hours (next ~30 minutes)

-

The discussion about "Office Hours (next ~30 minutes)" started at 16:31.

-

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (57)
  • -
  • meetingology (3)
  • -
  • ubot5 (2)
  • -
  • powersj (1)
  • -
-

Full Log

-

16:11 <blackboxsw> #startmeeting Cloud-init bi-weekly status

-

16:11 <meetingology> Meeting started Mon Dec 10 16:11:11 2018 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:11 <meetingology>

-

16:11 <meetingology> Available commands: action commands idea info link nick

-

16:12 <blackboxsw> Welcome to our biweekly status meeting. The intent is to provide a venue where we can advertise current cloud-init development efforts and a place and time where interested community members can ask questions or raise issues to the upstream development team.

-

16:12 <blackboxsw> Generally we go through the following topics: Previous Actions, Recent Changes, In-progress Development, and Office hours

-

16:13 <blackboxsw> Today we'll add a "Release" topic

-

16:13 <blackboxsw> Let's kick it off

-

16:13 <blackboxsw> #topic Previous Actions

-

16:14 <blackboxsw> One action we need to carry over from last meeting

-

16:14 <blackboxsw> #link https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/357427

-

16:14 <blackboxsw> our followup review is required on this branch to avoid a race condition for DHCP discovery on RHEL

-

16:15 <blackboxsw> I don't think there were any other actions raised last meeting

-

16:15 <blackboxsw> BTW our meeting minutes from last status meeting are here

-

16:15 <blackboxsw> #link https://cloud-init.github.io/status-2018-11-26.html#status-2018-11-26

-

16:17 <blackboxsw> we did land and publish cloud-init to Disco containing the Azure netlink listener support branch which was raised as an action last meeting. per the following

-

16:17 <blackboxsw> #link https://code.launchpad.net/~tamilmani1989/cloud-init/+git/cloud-init/+merge/336392

-

16:19 <blackboxsw> #topic Recent Changes

-

16:20 <blackboxsw> The following branches landed in cloud-init tip- dhclient-hook: cleanups, tests and fix a bug on 'down' event.

-

16:20 <blackboxsw> - NoCloud: Allow top level 'network' key in network-config. (LP: #1798117)

-

16:20 <blackboxsw> - ovf: Fix ovf network config generation gateway/routes

-

16:20 <blackboxsw> [Ryan Harper] (LP: #1806103)

-

16:20 <blackboxsw> - Published Cloud-init v.18.3-41 to Ubuntu Disco

-

16:20 <blackboxsw> - azure: detect vnet migration via netlink media change event

-

16:20 <blackboxsw> [Tamilmani Manoharan]

-

16:20 <blackboxsw> - Azure: fix copy/paste error in error handling when reading azure ovf.

-

16:20 <blackboxsw> [Adam DePue]

-

16:20 <ubot5> Ubuntu bug 1798117 in cloud-init (Ubuntu) "juju sends "network" top level key to user.network-config in lxd containers" [Medium,Confirmed]

-

16:20 <blackboxsw> - tests: fix incorrect order of mocks in test_handle_zfs_root.

-

16:20 <blackboxsw> - doc: Change dns_nameserver property to dns_nameservers. [Tomer Cohen]

-

16:20 <ubot5> Ubuntu bug 1806103 in cloud-init (Ubuntu) "ovf: network config store routes under nic subnets 'routes' key" [Undecided,New]

-

16:20 <blackboxsw> - OVF: identify label iso9660 filesystems with label 'OVF ENV'.

-

16:20 <blackboxsw> - net: Ephemeral*Network: add connectivity check via URL

-

16:20 <blackboxsw> [Igor Galić]

-

16:21 <blackboxsw> we also published all latest changes to Ubuntu Disco as 18.4-31-gbf791715-0ubuntu1

-

16:22 <blackboxsw> I missed a couple of other commits to cloud-init

-

16:23 <blackboxsw> - config: On ubuntu select cloud archive mirrors for armel, armhf, arm64.

-

16:23 <blackboxsw> - write_files: add support for appending to files. [James Baxter]

-

16:23 <blackboxsw> Thanks James, Tamilmani, Adam and Tomer for the contributions here and making cloud-init bette

-

16:23 <blackboxsw> r

-

16:24 <blackboxsw> #topic In-Progress Development

-

16:24 <blackboxsw> We track our current work in the TODO, Doing and Done lanes on trello

-

16:24 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:25 <blackboxsw> mostly we are trying to wrap up low-hanging-fruit and bug fixes as we have an upstream release scheduled this week for cloud-init 18.5

-

16:25 <blackboxsw> There is also some significant work ongoing my smoser for vmware and ovf deployment support

-

16:25 <blackboxsw> by smoser

-

16:26 <blackboxsw> and rharper has a branch up to fix network metric config handling for subnet routes

-

16:26 <blackboxsw> #link https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/359876

-

16:27 <blackboxsw> think that about wraps in-progress work.

-

16:27 <blackboxsw> #topic Cloud-init upstream Release 18.5

-

16:27 <blackboxsw> So, we have our 18.5 upstream release scheduled for this Wednesday 12/13/2018

-

16:28 <blackboxsw> If there are any feature requests or critical bug fixes that folks are interested, please bring them up either in channel here, or on the mailing list, cloud-init@lists.launchpad.net

-

16:29 <powersj> blackboxsw, ^ is that worth sending to mailing list?

-

16:30 <blackboxsw> powersj: yes. I'll send that email out in the next half hour

-

16:30 <blackboxsw> agreed

-

16:31 <blackboxsw> think that about wraps this status update for this meeting

-

16:31 <blackboxsw> #topic Office Hours (next ~30 minutes)

-

16:32 <blackboxsw> upstream devs will have eyes on this channel for any concerns, questions or discussions folks want to have about cloud-init.

-

16:32 <blackboxsw> Given the upcoming holidays, I think we will take a break from this meeting as next scheduled time would be the day before Christmas.

-

16:33 <blackboxsw> Next status meeting will be Monday January 7th 16:15 UTC

-

16:41 <blackboxsw> email sent to cloud-init about upcoming release

-

16:58 <blackboxsw> Happy Holiday folks. Looks like we're already starting to use up vacation time. Thanks for tuning in. See you next year!

-

16:58 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2019-01-07.html b/status-2019-01-07.html deleted file mode 100644 index 3a7e5f8..0000000 --- a/status-2019-01-07.html +++ /dev/null @@ -1,300 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Mon 07 January 2019 in status-meeting-minutes - - • 6 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:38.

- -

Recent Changes

-

The discussion about "Recent Changes" started at 16:42.

-

In-Progress Development

-

The discussion about "In-Progress Development" started at 16:46.

- -

Office Hours (next ~30 minutes)

-

The discussion about "Office Hours (next ~30 minutes)" started at 17:29.

- -

Vote results

-

Action items, by person

- -

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (62)
  • -
  • robjo (16)
  • -
  • meetingology (7)
  • -
  • ubot5 (6)
  • -
  • rharper (1)
  • -
-

Full Log

-

16:36 <blackboxsw> #startmeeting Cloud-init bi-weekly status

-

16:36 <meetingology> Meeting started Mon Jan 7 16:36:15 2019 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:36 <meetingology>

-

16:36 <meetingology> Available commands: action commands idea info link nick

-

16:37 <blackboxsw> Happy New Year! We shifted the cloud-init status meeting time ... and then I subsequent forgot about it.

-

16:37 <blackboxsw> Hope the break went well for folks. We'll be hosting this meeting bi-weekly to keep folks updated on cloud-init developments

-

16:38 <blackboxsw> Generally the topics we cover in this status meeting are: Previous Actions, Recent Changes, In-progress Development, and Office hours

-

16:38 <blackboxsw> #topic Previous Actions

-

16:39 <blackboxsw> looking over last meeting minutes I see only one action

-

16:39 <blackboxsw> #link https://cloud-init.github.io/

-

16:39 <blackboxsw> ^ meeting minutes

-

16:40 <blackboxsw> #link https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/360905

-

16:40 <blackboxsw> ^ this merge proposal from Jason Zions looks like it got updated and resubmitted a few days ago addressing our review comments. Let's get another review on this this week and see where it stands

-

16:42 <blackboxsw> #topic Recent Changes

-

16:44 <blackboxsw> - Upstream release of cloud-init 18.5 and publishing 18.5 to Ubuntu 19.04 (Disco)

-

16:45 <blackboxsw> - ds-identify: fix wrong variable name in ovf_vmware_transport_guestinfo.

-

16:45 <blackboxsw> - Scaleway: Support ssh keys provided inside an instance tag. [PORTE Loïc]

-

16:45 <blackboxsw> - OVF: simplify expected return values of transport functions.

-

16:45 <blackboxsw> - Vmware: Add support for the com.vmware.guestInfo OVF transport.

-

16:45 <blackboxsw> (LP: #1807466)

-

16:45 <blackboxsw> - HACKING.rst: change contact info to Josh Powers

-

16:45 <blackboxsw> - Update to pylint 2.2.2.

-

16:45 <blackboxsw> - Release 18.5 [Ryan Harper] (LP: #1808380)

-

16:45 <blackboxsw> - tests: add Disco release [Joshua Powers]

-

16:45 <blackboxsw> - net: render 'metric' values in per-subnet routes

-

16:45 <blackboxsw> [Ryan Harper] (LP: #1805871)

-

16:45 <blackboxsw> - write_files: add support for appending to files. [James Baxter]

-

16:45 <blackboxsw> - config: On ubuntu select cloud archive mirrors for armel, armhf, arm64.

-

16:45 <blackboxsw> (LP: #1805854)

-

16:45 <ubot5> Ubuntu bug 1807466 in cloud-init "add support for ovf transport com.vmware.guestInfo" [Medium,Fix committed]

-

16:45 <ubot5> Ubuntu bug 1808380 in cloud-init "Release 18.5" [Undecided,Fix released]

-

16:45 <ubot5> Ubuntu bug 1805871 in cloud-init (Ubuntu) "net renderers miss metric value in per-subnet routes" [Undecided,Fix released]

-

16:45 <ubot5> Ubuntu bug 1805854 in cloud-init "[feature-request] Add non-x86 Ubuntu EC2 mirrors in to default cloud-init configuration" [Medium,Fix released]

-

16:46 <blackboxsw> The above are commits landed in cloud-init since the last status meeting.

-

16:46 <blackboxsw> #topic In-Progress Development

-

16:47 <blackboxsw> As always we try tracking our ongoing cloud-init upstream work (and backlog) on our Trello board

-

16:47 <blackboxsw> #lin https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:47 <robjo> https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098 is pending since October :( :(

-

16:47 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:47 <blackboxsw> #action Review robjo's branch today/tomorrow

-

16:47 * meetingology Review robjo's branch today/tomorrow

-

16:47 <blackboxsw> #action Review robjo's branch today/tomorrow https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098

-

16:47 * meetingology Review robjo's branch today/tomorrow https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098

-

16:48 <blackboxsw> #link https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098

-

16:48 <blackboxsw> ok robjo, we'll have eyes on that today and get you something

-

16:48 <robjo> Also I filed a number of bugs w.r.t the network rendering some with proposals, for other's I simply have no idea about the best approach, none of these have seen any action

-

16:48 <blackboxsw> thanks for that

-

16:49 <robjo> then there is the Python 2 utf-8 issue w.r.t. metadata persistence on OpenStack

-

16:49 <robjo> smoser had supplied a test case, also not action on that issue since whenever .... :(

-

16:50 <robjo> on that topic the question is still open why that particular data is persisted in teh first place since every access to the APi on OpenStack yields a different result

-

16:51 <blackboxsw> #action review robjo's New bugs and get feedback https://bit.ly/2C4gEHJ

-

16:51 * meetingology review robjo's New bugs and get feedback https://bit.ly/2C4gEHJ

-

16:55 <blackboxsw> robjo: I think we have to sort persistence story for metadata sub-components still. The only reason anything is persisted is for speed of course. OpenStack DS is notably very slow on every call the the md service.

-

16:56 <blackboxsw> robjo: some of that persistence/refresh should/will be addressed in rharper's openstack hotplug branch which would force cloud-init to refresh metadata when hotplug events are seen

-

16:57 <robjo> Well I have to admit that I do not know how OpenStack and or guest would use the value returned for "random_seed". What I was able to test is that the value is different when the API is aclled

-

16:59 <robjo> so that could mean that OpenStack keeps the "previously" returned value of "random_seed" until the API is called again and then uses the previous value for whatever hashing is being done to come up with authentication of the guest

-

16:59 <blackboxsw> robjo: is this the bug? https://bugs.launchpad.net/cloud-init/+bug/1801364

-

16:59 <ubot5> Ubuntu bug 1801364 in cloud-init "persisting OpenStack metadata fails" [Undecided,Confirmed]

-

16:59 <blackboxsw> #link https://bugs.launchpad.net/cloud-init/+bug/1801364

-

17:00 <robjo> but that would imply that any calls to the OpenStack API from the quest must know that random_seed and I doubt that they are using the cache we build with cloud-init

-

17:00 <robjo> yes, that's the bug

-

17:03 <rharper> robjo: your https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098 was left in Needs Fixing and got tagged WIP; after you updated, it needed to move to Needs Review

-

17:04 <robjo> Well I am pretty sure I tried to set it back to get another review and from the interface it looked to me that happened.... :(

-

17:05 <robjo> If I look at the UI it tells me the review was requested from "Scott Moser [2]" on 2018-10-09 and the status is "Pending"

-

17:15 <blackboxsw> robjo: we're talking side-channel as we were in a meeting anyway. Just added a work item to help us avoid this situation

-

17:15 <blackboxsw> https://trello.com/c/bEGsPvTm/1028-updated-cloud-init-ci-review-bot-to-place-a-branch-back-into-needs-review-after-it-receives-a-commit

-

17:15 <blackboxsw> this will make reviews which you add commits to pop up on our radar anytime a new commit was added

-

17:16 <robjo> thanks

-

17:16 <blackboxsw> then we know what needs attention (as others have hit this issue too0

-

17:18 <blackboxsw> robjo: we also are talking about we can maybe blacklisting certain metadata elements as not-cacheable. We'll have to add 'cloud-init query' tooling to understand this at some point though.

-

17:18 <blackboxsw> #action blackboxsw resolve and land fix for https://bugs.launchpad.net/cloud-init/+bug/1801364 this week

-

17:18 * meetingology blackboxsw resolve and land fix for https://bugs.launchpad.net/cloud-init/+bug/1801364 this week

-

17:18 <ubot5> Ubuntu bug 1801364 in cloud-init "persisting OpenStack metadata fails" [Undecided,Confirmed]

-

17:19 <blackboxsw> though the fix for serialization won't include this blacklisting/cache solution I don't think

-

17:20 <blackboxsw> Ok I grabbed https://trello.com/c/7ouGpa0A/1029-openstack-serialization-errors-py27

-

17:23 <robjo> There is a patch for a very simplistic approach attached to the bug, that's what I am currently carrying in the SUSE package

-

17:28 <blackboxsw> +1

-

17:28 <blackboxsw> ok, so I think that wraps current topic.

-

17:29 <blackboxsw> #topic Office Hours (next ~30 minutes)

-

17:29 <blackboxsw> upstream devs will have eyes on this channel for any concerns, questions or discussions folks want to have about cloud-init.

-

17:29 <blackboxsw> We've also started going through some of the open reviews

-

17:30 <blackboxsw> raharper is on https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/360905 currently. I'll start looking at this https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/360905

-

17:34 <blackboxsw> robjo: can you re-share that opensuse download link for latest cloud-init images generated (I think you had shared once in the past your server team's public/latest/testing downloads of cloud-init)

-

17:34 <blackboxsw> just for reference while you are here :)

-

17:34 <blackboxsw> s/images/packages/

-

17:37 <robjo> https://build.opensuse.org/package/show/Cloud:Tools:Next/cloud-init

-

17:37 <blackboxsw> thank you sir

-

17:38 <robjo> currently the same as the released https://build.opensuse.org/package/show/Cloud:Tools:Next/cloud-init

-

17:38 <robjo> but planningt to move :Next to 18.5 this week

-

17:39 <blackboxsw> excellent thanks robjo

-

18:02 <blackboxsw> ok think that wraps up the meeting for today

-

18:02 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2019-01-28.html b/status-2019-01-28.html deleted file mode 100644 index 6b0dfda..0000000 --- a/status-2019-01-28.html +++ /dev/null @@ -1,271 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Mon 28 January 2019 in status-meeting-minutes - - • 5 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:27.

- -

Recent Changes

-

The discussion about "Recent Changes" started at 16:36.

-

In-Progress Development

-

The discussion about "In-Progress Development" started at 16:47.

- -

Office Hours (next ~30 minutes)

-

The discussion about "Office Hours (next ~30 minutes)" started at 16:51.

- -

Vote results

-

Action items, by person

- -

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (60)
  • -
  • robjo (6)
  • -
  • ubot5 (6)
  • -
  • meetingology (4)
  • -
-

Full Log

-

16:26 <blackboxsw> #startmeeting Cloud-init bi-weekly status

-

16:26 <meetingology> Meeting started Mon Jan 28 16:26:28 2019 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:26 <meetingology>

-

16:26 <meetingology> Available commands: action commands idea info link nick

-

16:27 <blackboxsw> hi cloud-init folks, it's that happy time again to chat about cloud-init upstream.

-

16:27 <blackboxsw> Generally the topics we cover in this status meeting are: Previous Actions, Recent Changes, In-progress Development, and Office hours

-

16:27 <blackboxsw> #topic Previous Actions

-

16:30 <blackboxsw> previously we had an action to review https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098. I think rharper and robjo have a couple of back and forths on this branch. looks like we'll be able to land this

-

16:32 <blackboxsw> and oh noes, we need to followup and resolve the following MD bug on OpenStack https://bugs.launchpad.net/cloud-init/+bug/1801364

-

16:32 <ubot5> Ubuntu bug 1801364 in cloud-init "persisting OpenStack metadata fails" [Undecided,Confirmed]

-

16:32 <blackboxsw> #action carry over blackboxsw close and land Openstack metadata handling bug https://bugs.launchpad.net/cloud-init/+bug/1801364

-

16:32 * meetingology carry over blackboxsw close and land Openstack metadata handling bug https://bugs.launchpad.net/cloud-init/+bug/1801364

-

16:32 <robjo> Well that one was just about an additional empty line which I removed in October

-

16:34 <blackboxsw> ok I'll spend the 2nd half of this meeting going through this again and landing it if no other concerns. #toostale seeing https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098

-

16:35 <blackboxsw> it doesn't look on review that there is anything concerning there.

-

16:36 <blackboxsw> ok I think that we it for actions last time.

-

16:36 <blackboxsw> #topic Recent Changes

-

16:36 <robjo> blackboxsw: There's also https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/357710

-

16:36 <robjo> which appears to be complaining about he commit message

-

16:37 <blackboxsw> robjo: oops autolander rejection, will fix the LP commit message now and make approved (for merging)

-

16:37 <blackboxsw> Server Team CI bot (server-team-bot) wrote on 2019-01-07: #

-

16:37 <blackboxsw> Commit message lints:

-

16:37 <blackboxsw> - Expected empty line on line 2 of the commit message

-

16:37 <robjo> Can there not be a template in LP for the commit message?

-

16:38 <robjo> I can never remember the formatting intricacies and thus depend on one of you guys to set this

-

16:38 <blackboxsw> robjo: does the 'commit message' on the merge proposal look good to you now https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/357710

-

16:39 <blackboxsw> at the top

-

16:39 <robjo> LGTM, thanks

-

16:39 <blackboxsw> I've clicked approve and it should autoland within ~15 mins

-

16:39 <blackboxsw> great

-

16:40 <blackboxsw> so recent commits to upstream cloud-init

-

16:41 <blackboxsw> - flake8: use ==/!= to compare str, bytes, and int literals

-

16:41 <blackboxsw> [Paride Legovini]

-

16:41 <blackboxsw> - opennebula: exclude EPOCHREALTIME as known bash env variable with a

-

16:41 <blackboxsw> delta [Chad Smith] (LP: #1813383)

-

16:41 <blackboxsw> - tox: fix disco httpretty dependencies for py37

-

16:41 <ubot5> Ubuntu bug 1813383 in cloud-init "opennebula: fail to sbuild, bash environment var failure EPOCHREALTIME" [Undecided,Fix committed]

-

16:41 <blackboxsw> ha, ircflood boot

-

16:41 <blackboxsw> not sure how far I got in that list of commits

-

16:42 <blackboxsw> - lxd: install zfs-linux instead of zfs meta package

-

16:42 <blackboxsw> 09:41 [Johnson Shi] (LP: #1799779)

-

16:42 <blackboxsw> 09:41 - net/sysconfig: do not write a resolv.conf file with only the header.

-

16:42 <blackboxsw> 09:41 [Robert Schweikert]

-

16:42 <blackboxsw> 09:41 - net: Make sysconfig renderer compatible with Network Manager.

-

16:42 <ubot5> Ubuntu bug 1799779 in cloud-init (Ubuntu Disco) "LXD module installs the wrong ZFS package if it's missing" [Medium,Confirmed]

-

16:42 <blackboxsw> 09:41 [Eduardo Otubo]

-

16:42 <blackboxsw> - cc_set_passwords: Fix regex when parsing hashed passwords

-

16:42 <blackboxsw> 09:41 [Marlin Cremers] (LP: #1811446)

-

16:42 <ubot5> Ubuntu bug 1811446 in cloud-init (Ubuntu) "chpasswd: is mangling certain password hashes" [Undecided,In progress]

-

16:42 <blackboxsw> 09:41 - net: Wait for dhclient to daemonize before reading lease file

-

16:42 <blackboxsw> 09:41 [Jason Zions] (LP: #1794399)

-

16:42 <ubot5> Ubuntu bug 1794399 in cloud-init "cloud-init dhcp_discovery() crashes on preprovisioned RHEL 7.6 VM in Azure" [Undecided,Fix committed]

-

16:42 <blackboxsw> 09:41 - [Azure] Increase retries when talking to Wireserver during metadata walk

-

16:42 <blackboxsw> 09:41 [Jason Zions]

-

16:42 <blackboxsw> 09:41 - Add documentation on adding a datasource.

-

16:42 <blackboxsw> Thanks folks for all the contributions to cloud-init over the last couple of weeks.

-

16:43 <blackboxsw> Additionally, we just published tip of cloud-init to Ubuntu disco (19.04) development release

-

16:44 <blackboxsw> and we have queued that release as well (cloud-init 18.5.17) for SRU (stable release update) into Xenial, Bionic and Cosmic as of Saturday.

-

16:44 <blackboxsw> the SRU process bug can be watched to see when 18.5.17 publishes to 16.04 18.04 and 18.10. (xenial, bionic, cosmic) https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1813346

-

16:44 <ubot5> Ubuntu bug 1813346 in cloud-init (Ubuntu) "sru cloud-init (18.4.0 update to 18.5-17-gd1a2fe73) Xenial, Bionic, Cosmic" [Undecided,New]

-

16:46 <blackboxsw> Also we welcome our new QA team member paride to Canonical, he's been working on re-enabling our copr build repos and generally improving the quality of our continuous integration for cloud-init (and other Canonical projects)

-

16:47 <blackboxsw> #topic In-Progress Development

-

16:47 <blackboxsw> we tracking our ongoing cloud-init upstream work (and backlog) on our Trello board

-

16:47 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:49 <blackboxsw> the next couple of weeks will likely result in Ubuntu SRU verificantion for that release into xenial, bionic and cosmic. robjo's been working on a few OpenSUSE/sysconfig network handling branches that will likely land. and we'll have a couple of EC2 branches that need to address EC2-Classic network re-configuration across reboots

-

16:50 <blackboxsw> and, as mentioned our upstream copr repo builds will likely be fixed for centos/fedora consumers

-

16:51 <blackboxsw> #topic Office Hours (next ~30 minutes)

-

16:52 <blackboxsw> So, upsteram devs will have eyes on this channel for any further discussion, bugs or questions about cloud-init. Please use this venue as you see fit to raise awareness of stale branches, bugs etc so we can queue them up for review.

-

16:53 * blackboxsw is going to look over https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098 to see if we can close out on that today

-

17:30 <blackboxsw> https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/357710 merged

-

17:30 <blackboxsw> and just approved https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098

-

17:30 <blackboxsw> thanks robjo

-

17:30 <blackboxsw> I think that about wraps it up for today. thanks again for checking in folks.

-

17:30 <blackboxsw> As always minutes will be posted to cloud-init's github page @

-

17:31 <blackboxsw> #link https://cloud-init.github.io

-

17:31 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2019-05-13.html b/status-2019-05-13.html deleted file mode 100644 index 0dbfaee..0000000 --- a/status-2019-05-13.html +++ /dev/null @@ -1,419 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Mon 13 May 2019 in status-meeting-minutes - - • 14 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:31.

- -

Recent Changes

-

The discussion about "Recent Changes" started at 16:35.

- -

In-progress Development

-

The discussion about "In-progress Development" started at 16:46.

- -

Office hours (next ~30 mins)

-

The discussion about "Office hours (next ~30 mins)" started at 17:02.

- -

Vote results

-

Action items, by person

-
    -
  • AnhVoMSFT
  • -
  • Odd_Bloke/rharper/AnhVoMSFT followup on recommended approach for getting kernel/userspace timestamp with or without python-dbus package dependency
  • -
-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (163)
  • -
  • AnhVoMSFT (20)
  • -
  • ubot5` (19)
  • -
  • meetingology (5)
  • -
  • powersj (3)
  • -
-

Full Log

-

16:25 <blackboxsw> #startmeeting Cloud-init bi-weekly status

-

16:25 <meetingology> Meeting started Mon May 13 16:25:37 2019 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:25 <meetingology>

-

16:25 <meetingology> Available commands: action commands idea info link nick

-

16:26 <blackboxsw> hi folks, we are restarting the cloud-init community status meeting so we can have a community forum to discuss current cloud-init development and try to improve momentum in the cloud-init project efforts.

-

16:28 <blackboxsw> over the last couple of months we had taken a break from this meeting. But, I think it's shown us that there is demand and usefulness in continuing hosting these meetings. So, from here on, we expect to post the upcoming date of status meetings in this channel's room topic.

-

16:29 <blackboxsw> Again the goal of this meeting is to give people a chance to see what work is currently being performed on upstream cloud-init as well as a forum to discuss or raise concerns or get eyes on potential bugs or features.

-

16:30 <blackboxsw> Generally the topics we would like to cover are the following: (and interjections/suggestions are always welcome

-

16:30 <blackboxsw> topics: Previous Actions, Recent Changes, In-progress Development, Office Hours.

-

16:31 <blackboxsw> #topic Previous Actions

-

16:32 <blackboxsw> so, looking at our last status minutes from the last meeting, (on Jan 28.... :( ) we had one action carried over

-

16:32 <blackboxsw> #link https://cloud-init.github.io/status-2019-01-28.html#status-2019-01-28

-

16:33 <blackboxsw> review and land https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/356098

-

16:33 <blackboxsw> that's done. as well as an openstack bug...

-

16:33 <blackboxsw> #link https://bugs.launchpad.net/cloud-init/+bug/1801364

-

16:33 <ubot5>` Ubuntu bug 1801364 in cloud-init "persisting OpenStack metadata fails" [Undecided,Confirmed]

-

16:33 <blackboxsw> Odd_Bloke: has landed this bug, I think it needs to be marked fix committed though

-

16:34 <blackboxsw> Odd_Bloke: is out today at a meeting, but I'll mark that action so we can make sure that bug status is properly reported (if there are no other branches to land for it)

-

16:34 <blackboxsw> #action Odd_Bloke confirm correct status of https://bugs.launchpad.net/cloud-init/+bug/1801364

-

16:34 * meetingology Odd_Bloke confirm correct status of https://bugs.launchpad.net/cloud-init/+bug/1801364

-

16:34 <ubot5>` Ubuntu bug 1801364 in cloud-init "persisting OpenStack metadata fails" [Undecided,Confirmed]

-

16:34 <blackboxsw> That;s about it for actions from previous meeting.

-

16:35 <blackboxsw> #topic Recent Changes

-

16:36 <blackboxsw> Here we list current content that has landed in cloud-init since last meeting..... because it has been a really long time since last meeting, I'm going to redact this to the last month or so of content to avoid getting banned in this channel for spam

-

16:37 <blackboxsw> - Azure: Return static fallback address as if failed to find endpoint

-

16:37 <blackboxsw> [Jason Zions (MSFT)]

-

16:37 <blackboxsw> - release 19.1 (LP: #1828479)

-

16:37 <blackboxsw> - freebsd: add chpasswd pkg in the image [Gonéri Le Bouder]

-

16:37 <blackboxsw> - tests: add Eoan release [Paride Legovini]

-

16:37 <ubot5>` Launchpad bug 1828479 in cloud-init "Release 19.1" [Undecided,Fix released] https://launchpad.net/bugs/1828479

-

16:37 <blackboxsw> hah, I don't think that worked

-

16:37 <blackboxsw> ok breaking that content up

-

16:37 <blackboxsw> - Azure: Return static fallback address as if failed to find endpoint

-

16:37 <blackboxsw> [Jason Zions (MSFT)]

-

16:37 <blackboxsw> - release 19.1 (LP: #1828479)

-

16:37 <blackboxsw> - freebsd: add chpasswd pkg in the image [Gonéri Le Bouder]

-

16:37 <blackboxsw> - tests: add Eoan release [Paride Legovini]

-

16:37 <blackboxsw> - cc_mounts: check if mount -a on no-change fstab path

-

16:37 <blackboxsw> [Jason Zions (MSFT)] (LP: #1825596)

-

16:37 <blackboxsw> - replace remaining occurrences of LOG.warn [Daniel Watkins]

-

16:37 <ubot5>` Launchpad bug 1825596 in cloud-init "Azure reboot with unformatted ephemeral drive won't mount reformatted volume" [High,Fix released] https://launchpad.net/bugs/1825596

-

16:37 <blackboxsw> - DataSourceAzure: Adjust timeout for polling IMDS [Anh Vo]

-

16:37 <blackboxsw> - Azure: Changes to the Hyper-V KVP Reporter [Anh Vo]

-

16:37 <blackboxsw> - git tests: no longer show warning about safe yaml.

-

16:37 <blackboxsw> - tools/read-version: handle errors [Chad Miller]

-

16:37 <blackboxsw> - net/sysconfig: only indicate available on known sysconfig distros

-

16:37 <blackboxsw> (LP: #1819994)

-

16:37 <blackboxsw> - packages: update rpm specs for new bash completion path

-

16:37 <blackboxsw> [Daniel Watkins] (LP: #1825444)

-

16:37 <blackboxsw> - test_azure: mock util.SeLinuxGuard where needed

-

16:37 <blackboxsw> [Jason Zions (MSFT)] (LP: #1825253)

-

16:37 <blackboxsw> - setup.py: install bash completion script in new location [Daniel Watkins]

-

16:37 <blackboxsw> - mount_cb: do not pass sync and rw options to mount

-

16:37 <ubot5>` Launchpad bug 1819994 in Provider for Plainbox - Canonical Certification Server "cloud-init selects sysconfig netconfig renderer if network-manager is installed on Ubuntu" [Critical,Confirmed] https://launchpad.net/bugs/1819994

-

16:37 <blackboxsw> [Gonéri Le Bouder] (LP: #1645824)

-

16:37 <blackboxsw> - cc_apt_configure: fix typo in apt documentation [Dominic Schlegel]

-

16:37 <blackboxsw> - Revert "DataSource: move update_events from a class to an instance..."

-

16:37 <blackboxsw> [Daniel Watkins]

-

16:37 <ubot5>` Launchpad bug 1825444 in cloud-init (Ubuntu) ""make rpm" fails on CentOS after commit 947d3c208" [Undecided,Fix released] https://launchpad.net/bugs/1825444

-

16:37 <blackboxsw> - Change DataSourceNoCloud to ignore file system label's case.

-

16:37 <blackboxsw> [Risto Oikarinen]

-

16:38 <ubot5>` Launchpad bug 1825253 in cloud-init "Unit tests with filesystem-related mocks fail in SeLinuxGuard when run on RHEL or CentOS" [Undecided,Fix released] https://launchpad.net/bugs/1825253

-

16:38 <ubot5>` Launchpad bug 1645824 in cloud-init "NoCloud source doesn't work on FreeBSD" [Medium,Fix released] https://launchpad.net/bugs/1645824

-

16:38 <blackboxsw> - cmd:main.py: Fix missing 'modules-init' key in modes dict

-

16:38 <blackboxsw> [Antonio Romito] (LP: #1815109)

-

16:38 <blackboxsw> - ubuntu_advantage: rewrite cloud-config module

-

16:38 <blackboxsw> - Azure: Treat _unset network configuration as if it were absent

-

16:38 <blackboxsw> [Jason Zions (MSFT)] (LP: #1823084)

-

16:38 <blackboxsw> - DatasourceAzure: add additional logging for azure datasource [Anh Vo]

-

16:38 <blackboxsw> - cloud_tests: fix apt_pipelining test-cases

-

16:38 <ubot5>` Launchpad bug 1815109 in cloud-init "cloud-final.service: "cloud-init modules --mode final" exit with "KeyError: 'modules-init'" after upgrade to version 18.2" [Medium,Fix released] https://launchpad.net/bugs/1815109

-

16:38 <blackboxsw> - Azure: Ensure platform random_seed is always serializable as JSON.

-

16:38 <blackboxsw> [Jason Zions (MSFT)]

-

16:38 <blackboxsw> - net/sysconfig: write out SUSE-compatible IPv6 config [Robert Schweikert]

-

16:38 <blackboxsw> - tox: Update testenv for openSUSE Leap to 15.0 [Thomas Bechtold]

-

16:38 <ubot5>` Launchpad bug 1823084 in cloud-init "DataSourceAzure doesn't rebuild network-config after reboot" [High,Fix released] https://launchpad.net/bugs/1823084

-

16:38 <blackboxsw> - net: Fix ipv6 static routes when using eni renderer

-

16:38 <blackboxsw> [Raphael Glon] (LP: #1818669)

-

16:38 <ubot5>` Launchpad bug 1818669 in cloud-init "ipv6 static routes configured for eni are incorrect" [Undecided,Fix released] https://launchpad.net/bugs/1818669

-

16:38 <blackboxsw> - Add ubuntu_drivers config module [Daniel Watkins]

-

16:38 <blackboxsw> - doc: Refresh Azure walinuxagent docs [Daniel Watkins]

-

16:38 <blackboxsw> - tox: bump pylint version to latest (2.3.1) [Daniel Watkins]

-

16:38 <blackboxsw> - DataSource: move update_events from a class to an instance attribute

-

16:38 <blackboxsw> [Daniel Watkins] (LP: #1819913)

-

16:38 <blackboxsw> - net/sysconfig: Handle default route setup for dhcp configured NICs

-

16:38 <blackboxsw> [Robert Schweikert] (LP: #1812117)

-

16:38 <blackboxsw> - DataSourceEc2: update RELEASE_BLOCKER to be more accurate

-

16:38 <ubot5>` Launchpad bug 1819913 in cloud-init "cloud-init on xenial may generate network config on every boot" [Undecided,Fix released] https://launchpad.net/bugs/1819913

-

16:38 <blackboxsw> [Daniel Watkins]

-

16:38 <blackboxsw> - cloud-init-per: POSIX sh does not support string subst, use sed

-

16:38 <ubot5>` Launchpad bug 1812117 in cloud-init "route files are not written on SUSE distros" [Undecided,Fix released] https://launchpad.net/bugs/1812117

-

16:38 <blackboxsw> (LP: #1819222)

-

16:38 <blackboxsw> - Support locking user with usermod if passwd is not available.

-

16:38 <ubot5>` Launchpad bug 1819222 in cloud-init "cloud-init-per no longer works due to bashisms" [Undecided,Fix released] https://launchpad.net/bugs/1819222

-

16:38 <blackboxsw> - Example for Microsoft Azure data disk added. [Anton Olifir]

-

16:38 <blackboxsw> - clean: correctly determine the path for excluding seed directory

-

16:38 <blackboxsw> [Daniel Watkins] (LP: #1818571)

-

16:38 <blackboxsw> - helpers/openstack: Treat unknown link types as physical

-

16:38 <ubot5>` Launchpad bug 1818571 in cloud-init "cloud-init clean removes seed directory even when --seed is not specified" [High,Fix released] https://launchpad.net/bugs/1818571

-

16:38 <blackboxsw> [Daniel Watkins] (LP: #1639263)

-

16:38 <ubot5>` Launchpad bug 1639263 in cloud-init " cloud-init Unknown network_data link type: macvtap" [Undecided,Fix released] https://launchpad.net/bugs/1639263

-

16:38 <blackboxsw> - drop Python 2.6 support and our NIH version detection [Daniel Watkins]

-

16:38 <blackboxsw> - tip-pylint: Fix assignment-from-return-none errors

-

16:38 <blackboxsw> - net: append type:dhcp[46] only if dhcp[46] is True in v2 netconfig

-

16:38 <blackboxsw> [Kurt Stieger] (LP: #1818032)

-

16:38 <blackboxsw> - cc_apt_pipelining: stop disabling pipelining by default

-

16:38 <blackboxsw> [Daniel Watkins] (LP: #1794982)

-

16:38 <blackboxsw> - tests: fix some slow tests and some leaking state [Daniel Watkins]

-

16:38 <ubot5>` Launchpad bug 1818032 in cloud-init "sysconfig renders BOOTPROTO=dhcp even if dhcp=false in v2 network-config" [High,Fix released] https://launchpad.net/bugs/1818032

-

16:38 <blackboxsw> - util: don't determine string_types ourselves [Daniel Watkins]

-

16:38 <ubot5>` Launchpad bug 1794982 in cloud-init "drop /etc/apt/apt.conf.d/90cloud-init-pipelining in 16.04+" [Medium,Fix released] https://launchpad.net/bugs/1794982

-

16:39 <blackboxsw> Azure and SuSE and FreeBSD foks have been quite a bit of work and we have a number of other community contributors to thank this round

-

16:41 <blackboxsw> AnhVoMSFT: jasonzio (MSFT) and robjo (SuSE) thanks again for your efforts

-

16:43 <blackboxsw> Also, as you can see, Canonical added someone to our ranks for cloud-init development. Odd_Bloke is a permanent addition to our team and landing a lot of solid content for cloud-init.

-

16:43 <blackboxsw> welcome Dan!

-

16:43 <AnhVoMSFT> thanks rharper Odd_Bloke powersj blackboxsw for all the reviewing and advice

-

16:44 <blackboxsw> From upstream side of the house, we have cut our first official upstream release of cloud-init. Version 19.1 sports 5 months of development, 24 contributors from 20 top-level domains. Details of that release are sent to our mailinglist and posted to the luanchpad milestone

-

16:44 <blackboxsw> #link https://launchpad.net/cloud-init/+milestone/19.1

-

16:46 <blackboxsw> :) ! it's nice how involved your teams have been thanks again.

-

16:46 <blackboxsw> #topic In-progress Development

-

16:47 <blackboxsw> So, for the upstream release of 19.1: Canonical has just started our SRU (Stable Release Update) process where we validate the upstream release before pushing it back into earlier Ubuntu series

-

16:47 <blackboxsw> We follow this upstream release process for Ubuntu

-

16:47 <blackboxsw> #link https://wiki.ubuntu.com/CloudinitUpdates

-

16:48 <blackboxsw> I've queue to release branches for review as of Friday 05/10. I have queued Ubuntu Disco and published to disco-proposed pocket already.

-

16:48 <blackboxsw> So if someone deploys disco on your favorite cloud or hardware, you can add a disco-proposed apt source to /etc/apt/sources.list and you sound be able to install and or test 19.1

-

16:49 <blackboxsw> I made the 19.1.1 SRU cut which included the commitish baa478546d8cac98a706010699d64f8c2f70b5bf which was the tip containing " Azure: Return static fallback address as if failed to find endpoint" as the last commit

-

16:49 <blackboxsw> so jasonzio's latest azure branch made it

-

16:50 <blackboxsw> expectation is that I'll get most of verification done over this week and we can hopefully (pending no SRU regressions discovered) publish to Xenial, Bionic, Cosmic and Disco the beginning of next week (05/20/2019)

-

16:51 <blackboxsw> I just added the following card to track this work, it'll move to DONE when published

-

16:51 <blackboxsw> #link https://trello.com/c/oxv61bPl/1099-sru-191-xenial-bionic-cosmic-and-disco

-

16:51 <powersj> AnhVoMSFT, thank you for all your contributions

-

16:52 <AnhVoMSFT> is there a package available publicly for 19.1 that we can download and apply it to existing images and run through our perf. regression test?

-

16:52 <blackboxsw> also today, we'll post 19.1 to our copr el-testing repo at

-

16:52 <blackboxsw> #link https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/

-

16:52 <blackboxsw> for centos.

-

16:53 <powersj> AnhVoMSFT, daily PPA: https://launchpad.net/~cloud-init-dev/+archive/ubuntu/daily

-

16:53 <blackboxsw> AnhVoMSFT: we have daily repos that

-

16:53 <blackboxsw> thx powersj

-

16:53 * powersj disappears

-

16:54 <blackboxsw> AnhVoMSFT, so that is built from tip of master (which currently contains exactly the same commit set as will be published to each series)

-

16:54 <blackboxsw> AnhVoMSFT: once the following branches are "merged" for each series, xenial-proposed, bionic-proposed, cosmic-proposed will also contain the final bits for each series

-

16:54 <AnhVoMSFT> thanks powersj blackboxsw

-

16:55 <blackboxsw> #link https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367301

-

16:55 <blackboxsw> #link https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367302

-

16:55 <blackboxsw> #link https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367297

-

16:55 <blackboxsw> so when we land those, it should be a matter of an hour or so until <series>-proposed is accessible to test those final packages

-

16:56 <blackboxsw> AnhVoMSFT: in the SRU process, we still will have to verify and test those bits before release. There is a tracking bug for the overall process here

-

16:56 <blackboxsw> #link https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1828637

-

16:56 <ubot5>` Ubuntu bug 1828637 in cloud-init (Ubuntu) "sru cloud-init (18.5-45 to 19.1.1) Xenial, Bionic, Cosmic, Disco" [Undecided,In progress]

-

16:56 <blackboxsw> ^ this but will go to fix released when we pass verification and publish the SRU

-

16:57 <blackboxsw> which will be promotion from xenial-proposed to xenial-updates for public availability on all images

-

16:57 <blackboxsw> again the estimate on this is probably next week for getting through testing

-

16:58 <blackboxsw> the rest of the cloud-init team is meeting this week for feature planning for the next cycle. But generally we will be tracking our ongoing work @ our public trello board

-

16:59 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

17:00 <blackboxsw> If there are there any features or significant gaps that people have interest in that we could try to put on our radar feel free to drop us a line here in channel or on the mailinglist @ cloud-init@lists.launchpad.net

-

17:01 <blackboxsw> I think that about wraps up current in-flight work

-

17:02 <blackboxsw> #topic Office hours (next ~30 mins)

-

17:03 <blackboxsw> This section is allocated generally for folks to chat about any burning questions that we have. Bring your topics, bugs, feature requests, merge proposals or questions and we'll try getting some eyes or discussion on the

-

17:03 <blackboxsw> *them.

-

17:04 <blackboxsw> Generally we should have a couple cloud-init devs hanging out in channel during this time to help build momentum or unblock folks. Today may be a bit light in attendance due to a remote work trip a number of people are attending.

-

17:04 <AnhVoMSFT> if our next work requires importing another module (python-dbus), are there any guidelines wrt to using additional python modules not currently part of cloudinit package?

-

17:06 <blackboxsw> AnhVoMSFT: generally adding new dependencies is something we try to avoid if possible due to impacting the minimal cloud images with additional dependencies. From ubuntu's perspective we tend to try to look at an ubuntu minimal image to see if the dependency is already there (and that makes things simple for the addition).

-

17:06 <blackboxsw> If new dependency is also something that can be optional instead of strict it makes adding that dependency easier.

-

17:06 <blackboxsw> For example: python-jsonschema is an optional package dependency

-

17:07 <blackboxsw> we bookend the imports in cloud-init with a try/except ImportError: pass and make sure that cloud-init still behaves if it is not there.

-

17:07 <AnhVoMSFT> i will have to look into how to make it optional - certainly we can go that way if that makes thing easier

-

17:07 <AnhVoMSFT> what we are looking at is how to get the kernel init timestamp and systemd init timestamp - both of these are available as KernelTimestamp and UserSpaceTimestamp that are available as part of the systemd's system dbus

-

17:07 <blackboxsw> This type of approach has been helpful in supporting Centos 6 where jsonschema wasn't available in stock images

-

17:08 <AnhVoMSFT> normally you can get those info from "systemctl show", but the issue is systemctl internally use systemd's format_timestamp, which trims the precision down to "seconds" level. (format_timestamp_us would give us what we need)

-

17:11 <blackboxsw> AnhVoMSFT: interesting. since it seems like the dependency is one one or two values and not the full content of python-dbus library/modules I wonder if it might be better to see if those values are available in /proc or /sys somewhere as it might be fairly simple to instrument our own. (and avoid the time cost of importing larger python modules)

-

17:11 <AnhVoMSFT> I guess if we really want to avoid another module, we can use os.stat to key off ctime of /proc and /proc/1 - however, the ctimes of /proc and /proc/1 are a bit earlier than the actual KernelTimestamp and UserSpaceTimestamp. They do have the advantage of being more widely available. Systemd and dbus might not exist on all distros

-

17:11 <blackboxsw> ... at least something to peek at to see if it is low hanging fruit that is easy to handle

-

17:12 <AnhVoMSFT> Right, I would appreciate if someone with more knowledge on Linux systems can provide some advices here

-

17:12 <AnhVoMSFT> the dependency is really on those values, and the dbus library seems a bit overkill for it

-

17:13 <blackboxsw> rharper: Odd_Bloke may have some thoughts on that too. but that conversation may have to wait a bit due to time difference.

-

17:14 <blackboxsw> AnhVoMSFT: again, what call/values would you like to make/get from python-dbus just for clarity

-

17:15 <AnhVoMSFT> bus=dbus.SystemBus() systemd1=bus.get_object('org.freedesktop.systemd1','/org/freedesktop/systemd1') manager=dbus.Interface(systemd1, 'org.freedesktop.systemd1.Manager') props_iface=dbus.Interface(manager,'org.freedesktop.DBus.Properties') props_iface.Get('org.freedesktop.systemd1.Manager','KernelTimestamp')

-

17:15 <AnhVoMSFT> oops - multiline didn't seem to go so well

-

17:15 <blackboxsw> it's all good thx

-

17:16 <blackboxsw> alternately, I support we could shell out via util.subp to make a cli call to handle that to avoid a python package dependency, but again it'd probably be better/faster to avoid that

-

17:17 <AnhVoMSFT> right, we're trying to avoid adding more util.subp call (in fact we have a workitem to reduce the numbers of the existing util.subp call the Azure DS makes)

-

17:18 <AnhVoMSFT> Like mentioned previously, we're looking at the /proc and /proc/1 ctime, they're cheap using the os.stat module and exist in all distros.

-

17:19 <blackboxsw> oops typo "alternatively , I support" /// I suppose

-

17:19 <blackboxsw> yeah that seems like the most non-contentious approach (processing /proc/1 ctime)

-

17:20 <blackboxsw> uncontentious rather

-

17:22 <AnhVoMSFT> another thing we're looking at is cloud-init cloudtests so that we can have some azure cloud test running as part of cloud-init check-in gate

-

17:22 <blackboxsw> excellent!

-

17:23 <AnhVoMSFT> if you guys have any pointers/tips on what it takes to enable cloud-tests please let us know

-

17:23 <AnhVoMSFT> one of our team members will be looking at it

-

17:24 <blackboxsw> any blockers that you are aware of to date? Generally the biggest lift is getting the platform support added to the cloud-tests

-

17:25 <blackboxsw> I know powersj added more CI docs related to this a few months ago at

-

17:25 <blackboxsw> #link https://cloudinit.readthedocs.io/en/latest/topics/tests.html#

-

17:25 <blackboxsw> I'll try to see if there was additional documentation tossed around

-

17:26 <blackboxsw> the benefit if Azure platform is added to cloud-init tip is that'd we would likely add some of that testing to our SRU verification process each release we are doing. I'm excited about that

-

17:27 <blackboxsw> right now, it's manual for Azure testing... per something like this https://github.com/cloud-init/ubuntu-sru/blob/master/manual/azure-sru-18.5.21.txt

-

17:27 <AnhVoMSFT> I'm not aware of any blockers, we just barely started looking at it

-

17:27 <AnhVoMSFT> these links are very helpful, I'll pass them along

-

17:28 <blackboxsw> the above script is tedious to write up, and only is really testing upgrade path and any new azure-specific bugs/features that are fixed in the current SRU, since most of the other integration testing covers general case

-

17:28 <blackboxsw> thanks AnhVoMSFT that's good to hear

-

17:29 <blackboxsw> are there any other topics folks have for today's meeting? Otherwise we can adjourn until next meeting

-

17:29 <blackboxsw> next meeting will be May 27th, same time

-

17:30 <blackboxsw> and I'll post status notes for the meeting to our github pages

-

17:30 <blackboxsw> #link https://cloud-init.github.io

-

17:31 <blackboxsw> before I forget. let's get an action to followup on kernel/userspace timestamp discussion

-

17:31 <AnhVoMSFT> thanks blackboxsw

-

17:32 <blackboxsw> #action Odd_Bloke/rharper/AnhVoMSFT followup on recommended approach for getting kernel/userspace timestamp with or without python-dbus package dependency

-

17:32 * meetingology Odd_Bloke/rharper/AnhVoMSFT followup on recommended approach for getting kernel/userspace timestamp with or without python-dbus package dependency

-

17:32 <blackboxsw> thank you AnhVoMSFT

-

17:32 <blackboxsw> see folks next time, or anytime in channel

-

17:32 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2019-05-28.html b/status-2019-05-28.html deleted file mode 100644 index c0eb66f..0000000 --- a/status-2019-05-28.html +++ /dev/null @@ -1,252 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Tue 28 May 2019 in status-meeting-minutes - - • 4 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 15:27.

- -

Recent changes

-

The discussion about "Recent changes" started at 15:30.

- -

In-progress Development

-

The discussion about "In-progress Development" started at 15:41.

- -

Office hours (next ~30 mins)

-

The discussion about "Office hours (next ~30 mins)" started at 15:44.

- -

Vote results

-

Action items, by person

- -

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (44)
  • -
  • meetingology (4)
  • -
  • akik (2)
  • -
  • ubot5 (2)
  • -
-

Full Log

-

15:23 <blackboxsw> #startmeeting Cloud-init bi-weekly status

-

15:23 <meetingology> Meeting started Tue May 28 15:23:50 2019 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

15:23 <meetingology>

-

15:23 <meetingology> Available commands: action commands idea info link nick

-

15:23 <blackboxsw> there we go

-

15:24 <blackboxsw> Hey folks, time for another bi-weekly cloud-init status. Welcome all!

-

15:25 <blackboxsw> Generally cloud-init upstream uses this meeting to provide a platform for status updates, raising questions or concerns and feature discussion. All are encouraged to participate as you see fit.

-

15:25 <blackboxsw> Generally the topics we would like to cover are the following: Previous Actions, Recent Changes, In-progress Development, Office Hours

-

15:26 <blackboxsw> without further ado let's jump into it.

-

15:27 <blackboxsw> #topic Previous Actions

-

15:27 <blackboxsw> From our previous meeting minutes we had a couple of action items that I think are resolved

-

15:27 <blackboxsw> #link https://cloud-init.github.io/status-2019-05-13.html#status-2019-05-13

-

15:28 * blackboxsw Odd_Bloke confirm correct status of https://bugs.launchpad.net/cloud-init/+bug/1801364

-

15:28 <ubot5> Launchpad bug 1801364 in cloud-init "persisting OpenStack metadata fails" [Undecided,Confirmed]

-

15:28 <blackboxsw> Dan confirmed that this is the proper bug status and still needs a fix

-

15:28 <blackboxsw> AnhVoMSFT: we had an action related to you "followup on recommended approach for getting kernel/userspace timestamp with or without python-dbus package dependency"

-

15:29 <blackboxsw> I know rharper had a comment or two in channel about this approach. Hopefully AnhVoMSFT you have everything you need there

-

15:29 <blackboxsw> if not, you can feel free to ping us for more discussion on that feature

-

15:30 <blackboxsw> #topic Recent changes

-

15:31 <blackboxsw> Big news since last bi-weekly status meeting is that we have completed and published 19.1.1 in an SRU into Ubuntu Xenial, Bionic, Cosmic and Disco as of yesterday.

-

15:31 <blackboxsw> Odd_Bloke: wrote up some content and email around this for more context. Thanks Odd_Bloke

-

15:32 <blackboxsw> #link https://discourse.ubuntu.com/t/sru-of-cloud-init-19-1-released/11028/2

-

15:33 <blackboxsw> #link https://lists.launchpad.net/cloud-init/msg00211.html

-

15:38 <blackboxsw> beyond that we have the following upstream commits landed

-

15:39 <blackboxsw> d9b1e5de91..HEAD | log2dch

-

15:39 <blackboxsw> - freebsd: NoCloud data source support [Gonéri Le Bouder] (LP: #1645824)

-

15:39 <blackboxsw> - Azure: Return static fallback address as if failed to find endpoint

-

15:39 <blackboxsw> [Jason Zions (MSFT)]

-

15:39 <ubot5> Launchpad bug 1645824 in cloud-init "NoCloud source doesn't work on FreeBSD" [Medium,Fix committed] https://launchpad.net/bugs/1645824

-

15:40 <blackboxsw> Thanks again Jason and Gonéri for the commits there. We have a few branches in the wings under review for freebsd and azure that I expect will be landing this week

-

15:41 <blackboxsw> #topic In-progress Development

-

15:42 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

15:43 <blackboxsw> Our upcoming work is set and scheduled on this trello board above. As we grab new significant tasks and dev work for cloud-init we will pull those cards into the doing lane

-

15:44 <blackboxsw> #topic Office hours (next ~30 mins)

-

15:45 <blackboxsw> This topic is an opportunity for anyone to bring their bugs, features, questions or branches to get some extra eyes or discussion around current development.

-

15:47 <blackboxsw> It is also a slot of time where upstream developers will be spending some time reviewing active branches to unblock community members and help increase velocity of our review queue.

-

15:47 <blackboxsw> #link https://code.launchpad.net/cloud-init/+activereviews

-

15:48 * blackboxsw does as review pass on https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/367315. I'm grabbing an active review slot for this now

-

15:52 <akik> ls

-

15:52 <akik> sorry

-

16:03 <blackboxsw> yeah this looks good Goneri https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/367315... approved

-

16:03 <blackboxsw> will merge in ~15

-

16:13 <blackboxsw> smoser: so sorry on the review delay here for the doc change you took over. https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/343546

-

16:14 <blackboxsw> just approved with a nit if you are around to push that. if not, I'll get that doc branch merged in tomorrow

-

16:16 <blackboxsw> I think that about wraps this status meeting this week. I think we should take an action to talk about we want to do with this old branch.

-

16:16 <blackboxsw> #link https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082

-

16:16 <blackboxsw> #action blackboxsw discuss with the team about landing the branch https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082

-

16:16 * meetingology blackboxsw discuss with the team about landing the branch https://code.launchpad.net/~amzn-cmiller/cloud-init/+git/cloud-init/+merge/360082

-

16:18 <blackboxsw> We'll hold the next cloud-init status meeting on Monday 3/10

-

16:19 <blackboxsw> and I'll post the status minutes up to https://cloud-init.github.io momentarily

-

16:19 <blackboxsw> Thanks again. have a good one guys and gals.

-

16:19 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2019-06-10.html b/status-2019-06-10.html deleted file mode 100644 index aed5092..0000000 --- a/status-2019-06-10.html +++ /dev/null @@ -1,332 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Mon 10 June 2019 in status-meeting-minutes - - • 11 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:23.

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:24.

- -

In Progress Development

-

The discussion about "In Progress Development" started at 16:30.

- -

Office Hours

-

The discussion about "Office Hours" started at 16:45.

-

Office Hours (next ~30 mins)

-

The discussion about "Office Hours (next ~30 mins)" started at 16:48.

- -

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (39)
  • -
  • rharper (39)
  • -
  • AnhVoMSFT (29)
  • -
  • cyphermox (12)
  • -
  • robjo (6)
  • -
  • meetingology (4)
  • -
  • ubot5 (3)
  • -
  • paride (1)
  • -
  • Odd_Bloke (1)
  • -
-

Full Log

-

16:19 <blackboxsw> #startmeeting Cloud-init bi-weekly status

-

16:19 <meetingology> Meeting started Mon Jun 10 16:19:45 2019 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:19 <meetingology>

-

16:19 <meetingology> Available commands: action commands idea info link nick

-

16:19 <rharper> o/

-

16:20 <Odd_Bloke> o/

-

16:20 <blackboxsw> hi cloud-init folks. let's kick off the bi-weekly meeting again

-

16:21 <blackboxsw> our last meeting minutes are hosted on github

-

16:21 <blackboxsw> #link https://cloud-init.github.io

-

16:22 <blackboxsw> welcome all. Generally cloud-init upstream uses this meeting to provide a platform for status updates, raising questions or concerns and feature discussion. All are encouraged to participate as you see fit.

-

16:22 <blackboxsw> our format is the following topics: Previous Actions, Recent Changes, In-progress Development, Office Hours

-

16:23 <blackboxsw> interjections and additional topics are welcome

-

16:23 <blackboxsw> #topic Previous Actions

-

16:24 <blackboxsw> Checking last meeting's minutes we were clear of old actions.

-

16:24 <blackboxsw> so we'll jump to the next topic this week.

-

16:24 <blackboxsw> #topic Recent Changes

-

16:26 <blackboxsw> the following commits landedd in cloud-init tip since the last status meeting

-

16:26 <blackboxsw> - Allow identification of OpenStack by Asset Tag

-

16:26 <blackboxsw> [Mark T. Voelker] (LP: #1669875)

-

16:26 <blackboxsw> - Fix spelling error making 'an Ubuntu' consistent. [Brian Murray]

-

16:26 <blackboxsw> - run-container: centos: comment out the repo mirrorlist [Paride Legovini]

-

16:26 <blackboxsw> - netplan: update netplan key mappings for gratuitous-arp

-

16:26 <blackboxsw> [Ryan Harper] (LP: #1827238)

-

16:26 <ubot5> Launchpad bug 1669875 in OpenStack Compute (nova) "identify openstack vmware platform" [Wishlist,Confirmed]

-

16:26 <ubot5> Launchpad bug 1827238 in cloud-init "Machines fail to deploy because cloud-init needs to accept both netplan spellings for grat arp" [Medium,Fix committed]

-

16:30 <blackboxsw> I was poking around out trello board to see if we've moved other cloud-init related content into the done lane, but I think those commits about capture the recent work

-

16:30 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:30 <blackboxsw> #topic In Progress Development

-

16:31 <blackboxsw> our active reviews are located here (as mentioned in the topic)

-

16:31 <blackboxsw> #link https://code.launchpad.net/cloud-init/+activereviews

-

16:32 <blackboxsw> Goneri: thanks for all the work on freebsd branches, there has been some good momentum there

-

16:32 <blackboxsw> there is ongoing work from Azure datasource that will likely land in the next week or two

-

16:33 <paride> ^^ "run-container: centos: comment out the repo mirrorlist", only actually relevent when using an http/https proxy, in all the other cases the mirrorlist works as usual

-

16:33 <blackboxsw> and some network-related changes landing shortly

-

16:33 <blackboxsw> paride: thank you paride for the extra note

-

16:33 <AnhVoMSFT> blackboxsw can you share more details on the work from Azure datasource ? Any bug that we can reference?

-

16:33 <blackboxsw> I was thinking https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/364012 AnhVoMSFT

-

16:35 <rharper> related to sorting out covering the all the network related scenarios so that we configure network in a way that ensures access to IMDS and internet in the face of additional static ips on the same subnet as the primary interface, multiple dhcp interfaces with default routes,

-

16:35 <AnhVoMSFT> I see - I think there potentially needs some bigger change there, as there was some issue around identifying the primary/secondary NIC. We got confirmation from our netwoking team that the first NIC returned is the primary

-

16:35 <rharper> AnhVoMSFT: good to know; that was our observation

-

16:36 <rharper> AnhVoMSFT: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1815254 , related as well; the plan being to put in place some source-based routing;

-

16:36 <ubot5> Launchpad bug 1815254 in cloud-init (Ubuntu) "Azure multiple ips prevent access to metadata service" [Undecided,Confirmed]

-

16:38 <AnhVoMSFT> thanks rharper - is that something that should be changed/fixed from cloudinit, or is this more platform related?

-

16:38 <rharper> that's a good question; generally it would be great if a platform were to include source-routes and metrics in the config they send

-

16:38 <AnhVoMSFT> if the latter I will file a workitem on our side to go do some research and get the right team to take a look at it

-

16:39 <rharper> currently no cloud does this, rather some indicate a primary via metadata, and then the OS scripts apply a metric to all non-primary routes to ensure that default routes go to the primary

-

16:39 <AnhVoMSFT> I see - so I guess we can do similarly on Azure since we know what the primary is (first nic returned in IMDS)

-

16:40 <rharper> AnhVoMSFT: so in the short term, I think cloud-init should (where possible with the OS network config) provide additional tuning (likely post-scripts in some cases) to tune the routing for what cloud-init knows is the primary route

-

16:40 <rharper> AnhVoMSFT: yes, I prefer a primary=True or whatever, but it's good enough to have the current behavior documented (in the code)

-

16:40 <AnhVoMSFT> thanks rharper

-

16:40 <rharper> so if it change/breaks, then we know

-

16:44 <rharper> I think that covers our in-progress items for the moment

-

16:45 <rharper> not sure if the bot will listen to me, but just in case

-

16:45 <robjo> Be mindful that in Azure the metadata service may lag behind by minutes w.r.t. secondary IPs on an interface

-

16:45 <rharper> #topic Office Hours

-

16:45 <rharper> robjo: in general, my awareness is that the instance has to be off line to change vnets and such; and booting back up has been enough time to see IMDS updated, do you see differently ?

-

16:46 <AnhVoMSFT> robjo that is good to know, I will check on that

-

16:46 <robjo> We've had various issues with cloud-netconfig due to the metadata server in Azure being slow and reverted to polling, which of course got us in trouble with API rate limits

-

16:46 <rharper> robjo: interesting

-

16:47 <rharper> We'll here in channel so if youve;; got merges or bugs that need an eye or just questions, fire away

-

16:47 <AnhVoMSFT> robjo feel free to file a bug on that and we will investigate - IMDS is our partner team so we'll get some answer quickly there

-

16:48 <AnhVoMSFT> rharper, a couple things I want to ask for Office Hours

-

16:48 <robjo> AnhVoMSFT: We have been working with Stephen Zarkos on the issues

-

16:48 <blackboxsw> #topic Office Hours (next ~30 mins)

-

16:48 <AnhVoMSFT> robjo I will ping Stephen and get more detail and see if we have any follow up items

-

16:48 <blackboxsw> sorry folks got pulled away for a bit thx rharper

-

16:48 <robjo> And double checked that the polling direction was OK form the Microsoft perspective before we implemented that

-

16:49 <AnhVoMSFT> I see, glad you're not blocked on it

-

16:50 <robjo> rharper: We always had bug reports that upon reboot not everything was always configured when secondary IP addresses were in play. But theoretically yes upon reboot everything should be there

-

16:50 <AnhVoMSFT> rharper we have a customer who booted up a VM based on 18.04, which uses netplan. Cloudinit wrote a netplan file to the image. He then installed ifupdown, then had some networking change which triggered a mac address change. Upon rebooting, cloudinit tries to use eni, but netplan file was still there, which caused his VM to mess up the network config

-

16:50 <robjo> putting cloud-netconfig into polling mode pretty mush addresses the issues we had reports about

-

16:51 <rharper> AnhVoMSFT: yes; that sounds very likely

-

16:51 <rharper> AnhVoMSFT: did they file a bug?

-

16:51 <rharper> cloud-init net "detects" which service is present

-

16:51 <AnhVoMSFT> I'm checking to see if this should be a bug, or that is expected behavior

-

16:51 <rharper> so if they did not uninstall netplan.io then cloud-init will likely prefer that over eni

-

16:52 <AnhVoMSFT> cloudinit actually prefers eni if ifupdown is installed, I think

-

16:52 <rharper> AnhVoMSFT: so the etc/netplan/*.yaml would only trigger things if netplan is still present; the systemd-generator will read yaml and write out networkd files

-

16:53 <AnhVoMSFT> right, I think the customer's mistake was to not uninstall netplan (or remove any netplan configuration file) after installing ifupdown

-

16:53 <rharper> AnhVoMSFT: right; I think we'll need to see the log and system state, but it sounds like an incomplete uninstall of netplan

-

16:53 <rharper> uninstall of netplan should be enough to make the cloud-init.yaml inert

-

16:54 <rharper> https://netplan.io/faq#how-to-go-back-to-ifupdown

-

16:54 <rharper> AnhVoMSFT: it should have automatically uninstall netplan.io

-

16:54 <AnhVoMSFT> I'm not sure if there is much we can do from the cloudinit side - perhaps if choosing eni, disable the cloud-init netplan yaml

-

16:54 <rharper> AnhVoMSFT: well, we could check writable paths of the renderers

-

16:54 <AnhVoMSFT> rharper I don't think that is the behavior on 18.04 - installing ifupdown will not uninstall netplan

-

16:55 <rharper> AnhVoMSFT: you're right; =(

-

16:55 <rharper> that sort of feels like a bug in the packaging

-

16:55 <AnhVoMSFT> yes, I share the same sentiment

-

16:56 <AnhVoMSFT> I will go ahead and file a bug so even if we don't have a short term action we can still capture the discussion

-

16:57 <rharper> AnhVoMSFT: thanks, I'm pinging in #netplan and the bug will be great so we can figure out the right plan

-

16:59 <AnhVoMSFT> second question: We have an intern working in our team and as part of warming up in cloudinit he wrote some additional capabilities into cloud-init analyze, adding a "boot" module (in addition to show/blame/dump), which collects timestamps of phases happening during vm booting up, but before cloudinit started, such as kernel initialization, systemd initialization..

-

17:00 <AnhVoMSFT> this should work for all cloud (he tested in AWE/GCP). Currently only works for distros that uses systemd. He'll try to figure out how to get those counters for freebsd and others

-

17:00 <AnhVoMSFT> rharper since you were the original author of analyze, I'm trying to gauge the interest on this and we're open to suggestions/questions

-

17:01 <cyphermox> rharper: they can coexist and configure each their own interface, so it's not a conflict. It's no different than coexisting ifupdown and NetworkManager, or also NetworkManager and systemd-networkd

-

17:01 <rharper> AnhVoMSFT: that sounds excellent

-

17:01 <blackboxsw> nice AnhVoMSFT on the commandline extensions!

-

17:01 <rharper> AnhVoMSFT: happy to review branch or Work-in-Progress when it's available

-

17:02 <AnhVoMSFT> thanks rharper blackboxsw we will have that in a branch very soon.

-

17:03 <AnhVoMSFT> cyphermox if that is the case then either the customer or cloudinit needs to make sure the system does not have conflicting configuration for netplan/eni.

-

17:03 <rharper> cyphermox: ok; would you be open to some sort of warning about having config in both or something? I dunno; it's just not a great experience to add the new package, configure it, reboot and not have networking since the same interface was configured (differenlty) in both packages

-

17:03 <blackboxsw> yeah, I'm quite intterested in any additional cli functionality that cloud-init more versatile as a system debug tool

-

17:04 <blackboxsw> makes cloud-init more versatile

-

17:04 <cyphermox> rharper: I'm not opposed to a warning, but that's not necessarily better UX.

-

17:05 <cyphermox> debconf prompts are quite annoying to have at upgrade, and just writing it out people are likely to miss it altogether

-

17:05 <cyphermox> (so you wouldn't really gain much)

-

17:05 <AnhVoMSFT> blackboxsw yep that was the goal - we want to be able to deploy 1000 VMs, then use cloud-init analyze output to analyze the 50th/99th percentile of where the timing was spent during system boot, and we need some more insights into phases before cloud-init started as well

-

17:05 <rharper> cyphermox: agreed; having a pointer to suggest cleaning/checking/confirming configs if /etc/netplan/ is non-empty and netplan.io is installed

-

17:06 <cyphermox> rharper: one option is to parse enough of /etc/network/ to catch mentions of the interface, but that's not necessarily super solid (though it's the best option), because people can rename interfaces in netplan and match by mac

-

17:06 <rharper> might be helpful; though I agree that they may still ignore that; and cloud-init could do some more work to see if an image has multiple renderers available and ensure it didn't leave config for a previous boot around

-

17:07 <rharper> cyphermox: yeah; cloud-init knows more about the config and both formats; we're likely in a better spot to see "you've configured this interface twice"

-

17:08 <cyphermox> rharper: so in short, I'm not opposed to improving the UX, but I'm not wowed by any solution right now (even mine)

-

17:09 <rharper> cyphermox: that's fair; thanks

-

17:09 <AnhVoMSFT> i think a fix in cloudinit might make most stakeholders happy here. It knows which configuration file it wrote, so it can definitely look for conflicting configurations

-

17:09 <rharper> cyphermox: AnhVoMSFT is going to file the customer bug with details and we can discuss what (if any) improvements are to be made; I suspect cloud-init can help most here

-

17:09 <cyphermox> yes, I think so too

-

17:09 <rharper> cyphermox: thanks for the input

-

17:09 <AnhVoMSFT> it can't be responsible for everything the customer does though. If customer writes some my-own-netplan.yml, we can't help much

-

17:10 <cyphermox> rharper: but hey, if someone was to write a check when running netplan apply that there exists config in /etc/network, I wouldn't have much issues merging it

-

17:10 <rharper> AnhVoMSFT: right, we have several "maybe_delete_if" where we verify expected output before we remove things

-

17:10 <cyphermox> I just know I won't have time to look into this myself in the near future

-

17:10 <rharper> cyphermox: ack

-

17:11 <cyphermox> I think what will help most is aggressively deprecating and removing ifupdown

-

17:13 <cyphermox> that said, the best we can realistically do for the time being is to demote it to universe

-

17:13 <cyphermox> (and that's not going to change anything for UX)

-

17:15 <AnhVoMSFT> we had another instance of someone installing ifupdown2, which had the effect of removing cloud-init on debian/ubuntu 16.04

-

17:16 <AnhVoMSFT> and totally hosed his system, but that's a different issue altogether

-

17:26 <blackboxsw> s

-

17:27 <blackboxsw> thanks for the good discussion folks, I guess we'll just add an action item to followup on a netplan bug for next time to see where we are at

-

17:31 <blackboxsw> #action follow up any bugs related to Azure/netplan uninstall in favor ifupdown to see if cloud-init has actionable feature work to ensure proper network renderer is used

-

17:31 * meetingology follow up any bugs related to Azure/netplan uninstall in favor ifupdown to see if cloud-init has actionable feature work to ensure proper network renderer is used

-

17:31 <blackboxsw> ok, I'll post minutes on this. thank you again rharper for driving

-

17:31 <blackboxsw> and for the participation robjo cyphermox and AnhVoMSFT

-

17:31 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2019-06-24.html b/status-2019-06-24.html deleted file mode 100644 index ed822cf..0000000 --- a/status-2019-06-24.html +++ /dev/null @@ -1,330 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Mon 24 June 2019 in status-meeting-minutes - - • 10 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:23.

- -

Recent Changes

-

The discussion about "Recent Changes" started at 16:28.

-

In Progress Development

-

The discussion about "In Progress Development" started at 16:31.

- -

Vote results

-

Action items, by person

- -

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (73)
  • -
  • rharper (23)
  • -
  • AnhVoMSFT (18)
  • -
  • nik736 (12)
  • -
  • ubot5 (4)
  • -
  • meetingology (4)
  • -
-

Full Log

-

16:18 <blackboxsw> #startmeeting Cloud-init bi-weekly status

-

16:18 <meetingology> Meeting started Mon Jun 24 16:18:34 2019 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:18 <meetingology>

-

16:18 <meetingology> Available commands: action commands idea info link nick

-

16:19 <blackboxsw> welcome to another episode of cloud-init status updates.

-

16:20 <blackboxsw> 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.

-

16:21 <blackboxsw> our format is the following topics: Previous Actions, Recent Changes, In-progress Development, Office Hours

-

16:21 <blackboxsw> anyone is welcome to participate, interject, make suggestions or ask questions

-

16:22 <blackboxsw> generally we try to host this meeting every two weeks on the day listed in the channel topic

-

16:23 <blackboxsw> #topic Previous Actions

-

16:23 <blackboxsw> last meeting

-

16:23 <blackboxsw> #link https://cloud-init.github.io/status-2019-06-10.html#status-2019-06-10

-

16:24 <blackboxsw> we had an action to follow up on any bugs related to installing ifupdown on a system that had netplan installed by default.

-

16:24 <blackboxsw> I believe we did see a bug come in from Azure about that.... checking for that bug id now

-

16:25 <blackboxsw> #1832381

-

16:25 <rharper> bug #1832381

-

16:25 <ubot5> bug 1832381 in cloud-init (Ubuntu) "vm fails to boot due to conflicting network configuration when user switches from netplan to eni" [Undecided,Incomplete] https://launchpad.net/bugs/1832381

-

16:25 <blackboxsw> #link https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381

-

16:25 <AnhVoMSFT> There is an action item on me to attach a log to that bug. Since the incident created by the customer was closed and we did not have permission to share his log, I will need to get a repro and retrieve the log. It's not very easy to trigger a mac address change in Azure these days

-

16:25 <blackboxsw> thanks AnhVoMSFT for this bug

-

16:27 <blackboxsw> ok if we carry over that action item then for next status meeting AnhVoMSFT (just to close the loop if it's important)

-

16:27 <AnhVoMSFT> yep - once I get some help from our networking folks to trigger a mac address change I'll update the bug with more logs

-

16:27 <blackboxsw> #action Touch base with AnhVoMSFT by next status on priority of https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381

-

16:27 * meetingology Touch base with AnhVoMSFT by next status on priority of https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381

-

16:27 <ubot5> Ubuntu bug 1832381 in cloud-init (Ubuntu) "vm fails to boot due to conflicting network configuration when user switches from netplan to eni" [Undecided,Incomplete]

-

16:28 <blackboxsw> good deal. that's all we had for actions from last meeting

-

16:28 <blackboxsw> #topic Recent Changes

-

16:29 <blackboxsw> the following items have landed on tip of cloud-init's master branch

-

16:30 <blackboxsw> - sysconfig: support more bonding options [Penghui Liao]

-

16:30 <blackboxsw> - cloud-init-generator: use libexec path to ds-identify on redhat systems

-

16:30 <blackboxsw> [Ryan Harper] (LP: #1833264)

-

16:30 <blackboxsw> - tools/build-on-freebsd: update to python3 [Gonéri Le Bouder]

-

16:30 <ubot5> Ubuntu bug 1833264 in cloud-init "cloud-init-generator hardcodes path to ds-identify" [Undecided,Fix committed]

-

16:30 <blackboxsw> thanks to Penghui and Gonéri for driving additional changes for cloud-init in this last sessions

-

16:30 <blackboxsw> session*

-

16:31 <blackboxsw> #topic In Progress Development

-

16:32 <blackboxsw> there a number of longer items for feature work in progress that should see some light soon

-

16:33 <blackboxsw> We track these features in trello as always

-

16:33 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:33 <blackboxsw> minor fixup for Azure instance-data.json (cloud-init query) for region and availability zone should land today

-

16:34 <blackboxsw> rharper: and blackboxsw are working on Azure-related route tables and async disk mount features

-

16:36 <AnhVoMSFT> is there any bug/discussion item for the async disk mount?

-

16:37 <blackboxsw> AnhVoMSFT: rharper has been testing out systemd unit magic for setting up disk mounts async and initial numbers look good. How to bake that work into cloud-init is the next small hurdle I think. (I thought he mentioned today in our standup a 50% speed increase due to async mounts instead of sync waits)

-

16:38 <rharper> https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/feature/disk_setup_async is the WIP branch

-

16:39 <blackboxsw> AnhVoMSFT: I expect we'll have something in the next couple of days.

-

16:39 <blackboxsw> orrr right now. thanx rharper

-

16:39 <AnhVoMSFT> that sounds really cool. I'll check it out

-

16:39 * blackboxsw creates a trello card that can be watched for this feature

-

16:40 <blackboxsw> #link https://trello.com/c/TMK5ZDMf/1108-azure-async-disk-mounts

-

16:41 <blackboxsw> feel free to subscribe to any trello cards folks see that are of interest. you will get an email if the card changes state, like from Doing to Done or if new links are added

-

16:42 <blackboxsw> Odd_Bloke: rharper process question

-

16:42 <blackboxsw> what do you guys think about us turning on voting on trello cards

-

16:42 <blackboxsw> people with interest on a feature/card in our backlog could upvote it and that could help drive what features we grab over time

-

16:43 <blackboxsw> dunno, thought it might be something we could toss around to see if that would make sense. the board it public after all

-

16:43 <blackboxsw> is public rather

-

16:43 <rharper> maybe; I worry about random +1 without any more context. Platform developers already work with us; and community folks file bugs/merge proposals

-

16:44 <blackboxsw> good point.

-

16:44 <rharper> I'm open to the idea

-

16:45 <blackboxsw> for sure, if it gets interest, we can think about adding that feature. can't hurt to have some additional input, unfounded though it may be.

-

16:45 <AnhVoMSFT> agreed on the usefulness might be limited. You guys are already talking to each other. Platform developers either engage directly on this board or through out of band channel (sync meeting with Canonical product groups, etc...)

-

16:46 <AnhVoMSFT> Perhaps you can try it out for a couple release periods and see how it works out

-

16:46 <blackboxsw> yeah, /me just likes all the shiny objects pretty icons ;) ... need to control myself

-

16:47 <blackboxsw> thx AnhVoMSFT +1.

-

16:48 <blackboxsw> so I think that about wraps in-progress development. I know paride has been tirelessly working on our CI infrastructure to improve quality of CI and false positives for failures due to resource constraints. So big thanks for paride working on our jenkins workers

-

16:48 <blackboxsw> #topic Office Hours (next ~30 mins)

-

16:49 <blackboxsw> This is an open topic to bring any cloud-init discussions, bugs, concerns or feature requests folks have.

-

16:49 <blackboxsw> In the absence of such topics we spend part of this time grooming the review queue to get back to dev

-

16:50 <blackboxsw> contributors so that they don't have stale branches waiting for input

-

16:50 <AnhVoMSFT> We had a review sent out to add some boot time telemetry collection as part of cloud-init analyze: https://code.launchpad.net/~samgilson/cloud-init/+git/cloud-init/+merge/368943

-

16:50 <blackboxsw> thanks AnhVoMSFT I'll grab a review slot on that one now

-

16:51 <AnhVoMSFT> would appreciate some reviews there and also on ideas on how to retrieve similar timestamps for FreeBSD

-

16:51 <rharper> AnhVoMSFT: yes, will review

-

16:51 <rharper> AnhVoMSFT: also, I filed a bug related to the azure telemetry, lemme get it

-

16:51 <blackboxsw> I'll kick off a CI run on that now

-

16:51 <blackboxsw> rharper: ^

-

16:52 <rharper> Bug 1833731

-

16:52 <ubot5> bug 1833731 in cloud-init "cloud-init analyze output not formatted cleanly on Azure" [Undecided,New] https://launchpad.net/bugs/1833731

-

16:52 <rharper> AnhVoMSFT: not sure if the branch for review addresses the formatting of the output, but we should take a look to clean it up

-

16:52 <AnhVoMSFT> is there a good way to subscribe to new bugs with a certain keyword/tags? I.e., I would like to auto-subscribe to all bugs that has "Azure" in the bug title

-

16:52 <blackboxsw> rharper: if you get a chance to double check https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/369199 we might be able to land that too

-

16:53 <rharper> blackboxsw: I asked you some questions, if you've replied, I'll look again

-

16:53 <blackboxsw> rharper: nevermind, I see you already looked at it

-

16:53 <rharper> ah

-

16:53 <rharper> perfect

-

16:53 <blackboxsw> thanks

-

16:53 <rharper> I think we're mostly fine; just a question on return values

-

16:53 * blackboxsw needed to refresh

-

16:54 <AnhVoMSFT> rharper I will take a look at the analyze output and see how we can improve it. If it is a minor change we can add it to the existing review

-

16:54 <rharper> AnhVoMSFT: no need to pull it into the existing stuff

-

16:55 <rharper> I'd prefer a separate targetted fix; which may land independently from the boot stage (which is super interesting on its own)

-

16:55 <AnhVoMSFT> cool - we will do a separate fix then

-

16:55 <blackboxsw> rharper: yeah that concern is clear, we are safe on the processing of region/az in absence of 'imds' key

-

16:55 <blackboxsw> it'll return none

-

16:57 <blackboxsw> by virtue of that last get('location|platformFaultDomain')

-

16:57 <blackboxsw> if either is absent due to any key above being absent, you'll get None as default value

-

16:58 <rharper> blackboxsw: ack

-

17:00 <nik736> Hi there, not sure if this is the right place to ask, but I have problems when creating a new VM, it only happens with the debian cloud image, ubuntu is fine. Booting is stuck at the drm line, the exact line is dependent on the video model type in my libvirt xml but it is basically stuck for 20-30sec and won't continue. It will boot eventually after that time. Thanks so much for any hints. Happy to provide

-

17:00 <nik736> further details.

-

17:02 <blackboxsw> hrm, video model timeouts are a bit out of my wheelhouse :/

-

17:02 * blackboxsw pokes around a bit in google

-

17:02 <nik736> it seems to be that the lines after it would be about resizing the file system. I am not really sure if this is cloud-init related at all and I am not sure if it actually is caused by the video model or is just taking a bit to get to the next steps

-

17:03 <blackboxsw> nik736: you can run cloud-init analyze show or cloud-init analyze blame to see what cloud-init says it is spending a lot of time on

-

17:03 <nik736> I tried different host systems, Debian 18.04, 19.04, Debian 9, different libvirt versions, different qemu versions, nothing seems to be helping lol

-

17:03 <blackboxsw> (If you have cloud-init v 18 or later in your image I think)

-

17:04 <nik736> ah, ok, thanks, I will look into that

-

17:04 <blackboxsw> nik736: also systemd-analyze blame is a good helper for what is killing boot time

-

17:04 <AnhVoMSFT> do you see any timestamp gap that reflects the 20-30s in cloud-init.log ?

-

17:08 <rharper> nik736: feel free to file a bug and attach logs from the 'cloud-init collect-logs' output (or serial console if available) and /var/log/cloud-init.log if you can get into the instance afterwards

-

17:08 <nik736> thanks for the help, currently looking into it

-

17:11 <AnhVoMSFT> rharper blackboxsw we have some instance deployment where cloud-init is hanging at the command ip route add - any idea how to look further?

-

17:12 <AnhVoMSFT> this does look like a platform problem, so it is more of a question related to networking, rather than cloud-init itself

-

17:14 <AnhVoMSFT> it's super hard to reproduce so the only thing we have so far to work with is logs. I thought the call to ip route add basically adds an entry to the kernel routing table. Is there an interaction with networking involved which might cause it to hang?

-

17:14 <rharper> AnhVoMSFT: I wonder if it's creating a route that breaks connection to IMDS or something else that cloud-init would then do an HTTP get on ?

-

17:17 <nik736> I saw in the log that 2 entries are around 1 minute apart "SUCCESS: searching for local datasources" and "Cloud-init v. 0.7.9 running 'init' at Mon, 24 Jun 2019 17:13:41 +0000. Up 73.67 seconds." I am not sure if this could be it or if this looks fine

-

17:18 <rharper> 0.7.9 is quite old, seeing the full cloud-init.log will be most useful for us to understand what's happening

-

17:19 <nik736> okay, sec

-

17:19 <AnhVoMSFT> rharper that is a good theory. I do see in a good case there's a call to IMDS immediately after that, although that call has a timeout. If it fails we should see more logs coming out of cloud-init. I'll look further into that todya

-

17:20 <nik736> @rharper https://pastebin.com/fzCSH5kC

-

17:20 <rharper> AnhVoMSFT: the retry logic in DataSourceAzure is quite long IIRC, so it's quite possible this is the very issue that blackboxsw is working w.r.t ensuring the instances always have a source-ip route to the IMDS

-

17:21 <AnhVoMSFT> rharper indeed it is long, and the log was overly suppressed to avoid log from growing too large while VM was waiting in pre-provisioning state. We are adding back some of the logs (in a smarter way to get enough details while avoiding huge log size)

-

17:22 <rharper> nik736: so, between line 260 and 261 there's a large timedelta; that's outside of cloud-init; cloud-init is executed separately 4 times (cloud-init init --local, cloud-init init, cloud-init config --modules, cloud-init config --final)

-

17:23 <rharper> nik736: so if you have a systemd journal, we could see what happens between the end of cloud-init-local.service and cloud-init.service (stage1 and 2);

-

17:23 <nik736> ah, okay, interesting

-

17:23 <nik736> will check

-

17:23 <rharper> or syslog might see stuff between those two time points

-

17:23 * rharper steps away for a bit, please keep sending info here; I'll respond when I;m back

-

17:24 <AnhVoMSFT> nik736 systemd-analyze critical-chain cloud-init.service might help here - I think some systemd service is running right after init-local and just before init and that service is taking time

-

17:25 <nik736> will check, thanks for your help, really appreciate it.

-

17:32 <blackboxsw> I think I'll wrap the meeting here, but we can continue the conversation. Thanks again folks for the discussions

-

17:33 <blackboxsw> next meeting will be July 8th

-

17:33 <blackboxsw> as updated in the topic

-

17:33 <blackboxsw> meeting minutes will be posted to

-

17:33 <blackboxsw> #link https://cloud-init.github.io

-

17:33 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2019-07-08.html b/status-2019-07-08.html deleted file mode 100644 index 5dc8210..0000000 --- a/status-2019-07-08.html +++ /dev/null @@ -1,353 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Mon 08 July 2019 in status-meeting-minutes - - • 10 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:18.

- -

Recent Changes

-

The discussion about "Recent Changes" started at 16:22.

-

In Progress Development

-

The discussion about "In Progress Development" started at 16:27.

- -

Office Hours (next ~30 mins)

-

The discussion about "Office Hours (next ~30 mins)" started at 16:48.

- -

Vote results

-

Action items, by person

- -

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (89)
  • -
  • Odd_Bloke (13)
  • -
  • bitfehler (10)
  • -
  • tribaal (8)
  • -
  • AnhVoMSFT (7)
  • -
  • chad-aws (6)
  • -
  • meetingology (5)
  • -
  • ubot5 (3)
  • -
  • robjo (2)
  • -
  • rharper (2)
  • -
-

Full Log

-

16:16 <blackboxsw> #startmeeting Cloud-init bi-weekly status

-

16:16 <meetingology> Meeting started Mon Jul 8 16:16:57 2019 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:16 <meetingology>

-

16:16 <meetingology> Available commands: action commands idea info link nick

-

16:17 <Odd_Bloke> bitfehler: It works for me on an Ubuntu eoan system, locally.

-

16:17 <blackboxsw> hi folks, welcome to another cloud-init community status meeting. All discussions and interjections welcome.

-

16:17 <Odd_Bloke> bitfehler: What version of Python 3 are you using?

-

16:17 <blackboxsw> loud-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.

-

16:17 <blackboxsw> our format is the following topics: Previous Actions, Recent Changes, In-progress Development, Office Hours

-

16:17 <blackboxsw> anyone is welcome to participate, interject, make suggestions or ask questions

-

16:18 <blackboxsw> we host the meeting every two weeks at the date and time indicated in the IRC channel topic ^

-

16:18 <blackboxsw> #topic Previous Actions

-

16:19 <blackboxsw> I'm looking through our meeting minutes now from the previous meeting

-

16:19 <blackboxsw> #link https://cloud-init.github.io/status-2019-06-24.html#status-2019-06-24

-

16:19 <blackboxsw> Touch base with AnhVoMSFT by next status on priority of https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381

-

16:19 <ubot5> Ubuntu bug 1832381 in cloud-init (Ubuntu) "vm fails to boot due to conflicting network configuration when user switches from netplan to eni" [Undecided,Incomplete]

-

16:20 <blackboxsw> I think AnhVoMSFT may have been looking to get cloud-init logs on a system reproducing this problem

-

16:20 <blackboxsw> so let's carry this over for next meeting and this bug is marked incomplete until we have some cloud-init logs to debug

-

16:21 <blackboxsw> #action query on incomplete https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381 with AnhVoMSFT to see if this needs priority

-

16:21 * meetingology query on incomplete https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381 with AnhVoMSFT to see if this needs priority

-

16:21 <ubot5> Ubuntu bug 1832381 in cloud-init (Ubuntu) "vm fails to boot due to conflicting network configuration when user switches from netplan to eni" [Undecided,Incomplete]

-

16:21 <blackboxsw> no further actions listed from last meeting

-

16:22 <blackboxsw> #topic Recent Changes

-

16:22 <AnhVoMSFT> blackboxsw I did hear back from networking on how to trigger mac address change, so I'll work on that this week and get the logs attached

-

16:22 <blackboxsw> excellent AnhVoMSFT thanks!

-

16:22 <blackboxsw> and thanks for joining the meeting

-

16:22 <AnhVoMSFT> the harder it is to reproduce, the better, since it's unlikely to affect that many customers

-

16:22 <blackboxsw> +1

-

16:23 <blackboxsw> the following are commits that landed in tip of master for cloud-init upstream

-

16:23 <blackboxsw> - Add missing dsname for Hetzner Cloud datasource [Markus Schade]

-

16:24 <blackboxsw> - doc: indicate that netplan is default in Ubuntu now [Daniel Watkins]

-

16:24 <blackboxsw> - azure: add region and AZ properties from imds compute location metadata

-

16:24 <blackboxsw> [Chad Smith]

-

16:24 <blackboxsw> - sysconfig: support more bonding options [Penghui Liao]

-

16:24 <blackboxsw> - cloud-init-generator: use libexec path to ds-identify on redhat systems

-

16:24 <blackboxsw> [Ryan Harper] (LP: #1833264)

-

16:24 <blackboxsw> - tools/build-on-freebsd: update to python3 [Gonéri Le Bouder]

-

16:24 <ubot5> Ubuntu bug 1833264 in cloud-init "cloud-init-generator hardcodes path to ds-identify" [Undecided,Fix committed]

-

16:25 <blackboxsw> though I think the bottom two of those commits I may have reported last meeting

-

16:26 <blackboxsw> beyond that I know that paride has resolved a couple of issues with our CI infrastructure not cleaning up stale containers which would have triggered a number of CI failures over the last few weeks.

-

16:27 <blackboxsw> I think that about wraps 'completed' work in tip.

-

16:27 <blackboxsw> #topic In Progress Development

-

16:28 <blackboxsw> We mentioned this last meeting, there are a couple of longer features we are working on that will hit cloud-init tip soon.

-

16:28 <blackboxsw> we track our work on trello at the following url

-

16:28 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:29 <blackboxsw> In trying to enable secondary IP configuration on Azure platforms, we discovered a systemd-networkd bug related to classless routes not getting the appropriate source IP configuration

-

16:29 <blackboxsw> per this card

-

16:29 <blackboxsw> #link https://trello.com/c/RhevWnHx/1064-azure-imds-handle-multiple-default-routes-static-ips-in-primary-subnet

-

16:30 <blackboxsw> Dan Streetman filed a bug and upstream systemd fix for this https://github.com/systemd/systemd/issues/12969

-

16:31 <blackboxsw> and he's working on getting that released into Ubuntu Eoan. cloud-init may need a minor fix to only render static IPs if systemd-networkd version contains the latest fix.

-

16:31 <chad-aws> secondary addresses on azure too, or aws?

-

16:31 <blackboxsw> chad-aws: I also have just pushed a branch for review that will add secondary IPs from AWS's Datasource as well

-

16:31 <blackboxsw> since we had context on the netplan we need to generate that

-

16:31 <chad-aws> ok

-

16:32 <blackboxsw> #link https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/369792

-

16:33 <blackboxsw> chad-aws: the one question I think we might have to discuss related to the above branch is whether or not cloud-init on older LTSes (Xenial, Bionic) should change behavior to attempt rendering secondary IP information or not (because that would be a change in behavior)

-

16:34 <blackboxsw> generally we try to retain existing behavior on old Ubuntu LTS releases so we don't surprise folks who may have worked around previous limitations of cloud-init (like manually/scripted adding their own secondary IP information)

-

16:35 <chad-aws> (Note I am not the chad.smith above, but I am interested too.)

-

16:35 <blackboxsw> hehe, yes, I am not talking to myself (blackboxsw == chad.smith)

-

16:36 <blackboxsw> also in progress is rharper's good work on teasing out async mount functionality per the following

-

16:36 <blackboxsw> #link https://trello.com/c/TMK5ZDMf/1108-azure-async-disk-mounts

-

16:36 <chad-aws> I think different config files should make different behavior and that's okay.

-

16:36 <blackboxsw> +1 chad-aws

-

16:37 <blackboxsw> the async mount feature is the ability to allow cloud-init defer some disk mounts until later in the cloud-init stages to allow folks to ssh to the vms earlier in the boot process

-

16:38 <blackboxsw> as some systems with lots of mounts may block for a while trying to mount and format disks

-

16:39 <blackboxsw> while this approach is tagged as azure, rharper is approaching it in a generic way that should make this functionality accessible to many platforms

-

16:40 <blackboxsw> paride: rharper Odd_Bloke anything else I'm forgetting in progress?

-

16:40 <rharper> blackboxsw: right; it's changes to cc_disk_setup/cc_mount handling

-

16:40 <rharper> blackboxsw: nothing I can think of

-

16:41 <blackboxsw> we probably should cut an Ubutuu Eoan upload of cloud-init tip soon, but I don't know when that should be scheduled?

-

16:41 <Odd_Bloke> I'm doing some work to modify the way we determine network config sources, but that shouldn't affect any data sources that don't opt in to it.

-

16:41 <AnhVoMSFT> i looked at it briefly, this involves calling a systemd unit to format/mount - do we report error back to cloud-init ?

-

16:41 * tribaal raises hand

-

16:41 <tribaal> is there any rough estimation on where that tip cut would be?

-

16:41 <blackboxsw> tribaal: ahh yes awesome, forgot. tribaal has a new datasource

-

16:41 <tribaal> yes, thanks a lot for your reviews everyone

-

16:42 <tribaal> nice working with you guys again :)

-

16:42 <blackboxsw> #link https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516

-

16:42 <blackboxsw> for Exoscale ^

-

16:42 <tribaal> Ideally we'd target the next release for our datasource as well, but of course it's not landed yet so if the cut is e.g. tomorrow it might be a bit tight :)

-

16:42 <Odd_Bloke> Specifically, if a platform does any networking setup during the initramfs (such as for iSCSI), cloud-init will only consider the initramfs-provided configuration at the moment.

-

16:42 <blackboxsw> tribaal: for eoan, we can just grab tip of master at anypoint for an upload since it

-

16:43 <blackboxsw> is still a development release

-

16:43 <tribaal> ack

-

16:43 <blackboxsw> so it's super low weight for our release (and we should do it often)

-

16:43 <blackboxsw> also we have planned/upcoming an SRU into Xenial/Bionic/Disco on July 15th (so next week)

-

16:44 <tribaal> as far as SRUs are concerned, would that typically be something that would be backported, or not?

-

16:44 <Odd_Bloke> I'm making it possible for data sources to specify a different order for the network config sources, so that platforms where iSCSI is the default can have their data source's network config preferred.

-

16:44 <blackboxsw> tribaal: and others: cloud-init SRUs our tip into every release due to an SRU exception that we have with Ubuntu

-

16:44 <blackboxsw> so we upload latest code into each SRU target series for ubuntu

-

16:45 <blackboxsw> though we may patch/disable some functionality that is deemed a change in behavior from previous release

-

16:45 <tribaal> blackboxsw: understood, thanks. I'll schedule some time for myself to work on it "full time" as much as possible, so we can make the cut.

-

16:45 <Odd_Bloke> I'm also splitting apart explicitly-from-the-user cmdline configuration (i.e. network-data=...) from the initramfs-provided values (ip=... or iBFT), so that data sources can be configured to still allow explicit user network configuration to override data source network configuration.

-

16:45 <blackboxsw> here's our SRU process for those interested

-

16:45 <blackboxsw> #link https://wiki.ubuntu.com/CloudinitUpdates

-

16:46 <blackboxsw> so this meeting (and an email to cloud-init mailinglist) will serve as a call for branches/features for SRU.

-

16:46 <Odd_Bloke> But as I said previously, this is all just refactoring except for the specific places we need this functionality.

-

16:46 <AnhVoMSFT> I sent a merge proposal for adding some more telemetry for Azure: https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785 - would appreciate a review. Trying to make it in before next SRU

-

16:46 <AnhVoMSFT> also will send a merge proposal today or tomorrow on the case sensitivity issue when checking is_new_instance

-

16:46 <blackboxsw> if folks are interested in getting a specific feature/bug or branch reviewed/fixed and published, please raise your hand, ping in channel or send email to the mailing list to make sure the need is not forgotten

-

16:47 <blackboxsw> #action review Azure telemetry branch https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785

-

16:47 * meetingology review Azure telemetry branch https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785

-

16:47 <bitfehler> i feel a bit awkward stepping in here, but i kind of do

-

16:47 <blackboxsw> AnhVoMSFT: we also have reviewed samgilson's branch on a new cloud-init analyze subcommand for boot performance

-

16:48 <bitfehler> sorry, i am pretty new to cloud-init, but i did open a merge proposal today

-

16:48 <blackboxsw> bitfehler: no worries, conversations gotta happen :)

-

16:48 <Odd_Bloke> #link https://code.launchpad.net/~bitfehler/cloud-init/+git/cloud-init/+merge/369814

-

16:48 <Odd_Bloke> (Can I do that, or only blackboxsw?)

-

16:48 <AnhVoMSFT> thanks blackboxsw, last I synced with him, Sam is actively working on addressing your comments

-

16:48 <blackboxsw> I'll tick the topic to office hours which is really just open season for discussion or reviews

-

16:48 <robjo> Does anyone know if VMware has any plans to move their source from https://github.com/vmware/cloud-init-vmware-guestinfo to be included in upstream cloud-init?

-

16:48 <blackboxsw> #topic Office Hours (next ~30 mins)

-

16:51 <bitfehler> i think my main question would have been how to best get in touch with you, but i think i found the answer already :)

-

16:51 <blackboxsw> hrm, first I've seen of that robjo . maybe we can ping Sankar on that to see what the motivation is there

-

16:51 <blackboxsw> bitfehler: either here or mail cloud-init@lists.launchpad.net

-

16:52 <robjo> I was just made aware of this last week via "please create a packge' to which my initial answer is No, the VMware code should be in cloud-init proper

-

16:53 <blackboxsw> per vmware,yeah that makes sense for them to try to get that cloud-init datasource upstream. forcing every distro to do their packaging for them is not really the right solution

-

16:54 <bitfehler> one other thing i was wondering: do you feel a plain systemd-networkd network renderer would make sense? i wrote a very basic one trying to get better cloud-init support for Arch Linux

-

16:54 <bitfehler> it sort of works, but I am not sure whether this goal worth pursuing?

-

16:57 <blackboxsw> bitfehler: interesting, right so we have netplan render which ultimately renders networkd on our behalf on ubuntu,

-

16:58 <blackboxsw> if direct networkd render is the only way to support network config on Arch linux I don't see why we wouldn't want that.... rharper or Odd_Bloke? (maybe I'm missing the concern)

-

16:59 <bitfehler> i saw the comments about networkd above, but i am not familiar with netplan. it is another layer in between, right?

-

17:00 <Odd_Bloke> bitfehler: netplan takes v2 network configuration and renders it for a target backend. The two supported backends ATM are networkd and NetworkManager.

-

17:00 <blackboxsw> https://netplan.io for more info

-

17:00 <bitfehler> oh, wow, i overlooked that. so it doesn't need any additional software?

-

17:01 <AnhVoMSFT> it does need netplan

-

17:01 <bitfehler> oh wait, netplan is a renderer itself, and that supports the two backends

-

17:02 <Odd_Bloke> Right, netplan is the intended way for cloud-init to render network config for networkd.

-

17:03 <bitfehler> ok, got it. i guess i could also look into porting netplan to arch then? not sure what an effort that would be

-

17:05 <Odd_Bloke> IMO, that would be the best way to go, if it's tractable.

-

17:05 <Odd_Bloke> We ideally wouldn't reimplement netplan's networkd renderer in cloud-init. :)

-

17:05 <bitfehler> i'll let you know soon ;)

-

17:08 <chad-aws> I guess this should go both ways. Is there anything AWS EC2 can do better or different?

-

17:25 <blackboxsw> nice chad-aws, sorry I got pulled into a second meeting. chad-aws I did have a question about metadata versioning in aws.

-

17:26 <blackboxsw> how are new features communicated for a new metadata version

-

17:26 <blackboxsw> I reference https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html

-

17:26 <blackboxsw> but it didn't have a specific note on the changes added for 2018-09-24 which I used in my branch

-

17:27 <blackboxsw> only the first version that a field was introduced, not that local_ipv4s changed value from string to list in 2018-09-24.

-

17:27 <blackboxsw> so I guess my question is, is there a better source of truth for ec2 metadata values that we should be looking at

-

17:28 <blackboxsw> chad-aws: sorry (I realize that's a question out of left field)

-

17:31 <blackboxsw> I think I'll wrap the meeting here. Thank you all again for the attending this week.

-

17:31 <chad-aws> thx

-

17:31 <blackboxsw> Again plan for cloud-init 19.2 SRU is scheduled for next week so any features/branches that need landing or review should be raised here or on the mailing list

-

17:32 <blackboxsw> minutes will be posted at https://cloud-init.github.io

-

17:32 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2019-07-22.html b/status-2019-07-22.html deleted file mode 100644 index ba362d6..0000000 --- a/status-2019-07-22.html +++ /dev/null @@ -1,320 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Mon 22 July 2019 in status-meeting-minutes - - • 6 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:17.

- -

Recent Changes

-

The discussion about "Recent Changes" started at 16:23.

- -

In Progress Development

-

The discussion about "In Progress Development" started at 16:27.

- -

In Progress Development

-

The discussion about "In Progress Development" started at 16:36.

- -

Office Hours (next ~30 mins)

-

The discussion about "Office Hours (next ~30 mins)" started at 16:43.

- -

Vote results

-

Action items, by person

- -

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • rharper (69)
  • -
  • Goneri (20)
  • -
  • meetingology (6)
  • -
  • Odd_Bloke (5)
  • -
  • metsuke (4)
  • -
  • ubot5 (2)
  • -
-

Full Log

-

16:15 <rharper> #startmeeting Cloud-init bi-weekly status

-

16:15 <meetingology> Meeting started Mon Jul 22 16:15:03 2019 UTC. The chair is rharper. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:15 <meetingology>

-

16:15 <meetingology> Available commands: action commands idea info link nick

-

16:15 <rharper> \o/

-

16:15 <rharper> #chair Odd_Bloke

-

16:15 <meetingology> Current chairs: Odd_Bloke rharper

-

16:15 <rharper> hi folks, welcome to another cloud-init community status meeting. All discussions and interjections welcome.

-

16:16 <rharper> 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.

-

16:16 <rharper> our format is the following topics: Previous Actions, Recent Changes, In-progress Development, Office Hours

-

16:16 <rharper> anyone is welcome to participate, interject, make suggestions or ask questions

-

16:16 <rharper> we host the meeting every two weeks at the date and time indicated in the IRC channel topic ^

-

16:17 <rharper> #topic Previous Actions

-

16:17 <Odd_Bloke> o/

-

16:17 <rharper> We had a few previous action items to look at

-

16:18 <rharper> https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381

-

16:18 <ubot5> Ubuntu bug 1832381 in cloud-init (Ubuntu) "vm fails to boot due to conflicting network configuration when user switches from netplan to eni" [Undecided,Incomplete]

-

16:18 <rharper> AnhVoMSFT was looking to collect logs from this scenario;

-

16:19 <Goneri> hey!

-

16:19 <rharper> it appears that getting an instance where the MAC address changes is harder so fewer folks trip over this; however, we agreed that cloud-init can track which renderer it used and if it switches it can clean up the config it wrote;

-

16:19 <rharper> #action rharper to update https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381 status

-

16:19 * meetingology rharper to update https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381 status

-

16:19 <ubot5> Ubuntu bug 1832381 in cloud-init (Ubuntu) "vm fails to boot due to conflicting network configuration when user switches from netplan to eni" [Undecided,Incomplete]

-

16:20 <rharper> The other action was to review https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785

-

16:20 <rharper> This was completed the other week while we worked toward the 19.2 release; that branch is currently work-in-progress, awaiting feedback/changes from submitter

-

16:21 <rharper> that's all of the action items from previous meeting

-

16:22 <rharper> previous meeting status found here:

-

16:22 <rharper> #link http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-07-08-16.16.html

-

16:23 <rharper> normally at the cloud-init.github.io status page; looks like we didn't push the logs there.

-

16:23 <rharper> #action rharper to followup with blackboxsw on pushing status minutes up to cloud-init.github.io page

-

16:23 * meetingology rharper to followup with blackboxsw on pushing status minutes up to cloud-init.github.io page

-

16:23 <rharper> #topic Recent Changes

-

16:25 <rharper> % git log --oneline --since 2019-07-08

-

16:25 <rharper> a02c0c9 (HEAD ->` master, origin/master, origin/HEAD) cloud_tests: updates and fixes

-

16:25 <rharper> 5498107 Fix bug rendering MTU on bond or vlan when input was netplan.

-

16:25 <rharper> b3a87fc net: update net sequence, include wait on netdevs, opensuse netrules path

-

16:25 <rharper> 060b1a1 (tag: 19.2, raharper/release/19.2, release/19.2, fix/fs_setup_custom_command_lp1801790) Release 19.2

-

16:25 <rharper> 07b1723 net: add rfc3442 (classless static routes) to EphemeralDHCP

-

16:25 <rharper> 1404817 templates/ntp.conf.debian.tmpl: fix missing newline for pools

-

16:25 <rharper> a785462 Support netplan renderer in Arch Linux

-

16:25 <rharper> a066ccd Fix typo in publicly viewable documentation.

-

16:26 <rharper> d9769c4 Add a cdrom size checker for OVF ds to ds-identify

-

16:26 <rharper> 9c47c68 VMWare: Trigger the post customization script via cc_scripts module.

-

16:26 <rharper> a24550a Cloud-init analyze module: Added ability to analyze boot events.

-

16:26 <rharper> a6faf3a Update debian eni network configuration location, retain Ubuntu setting

-

16:26 <rharper> e5f5421 net: skip bond interfaces in get_interfaces

-

16:26 <rharper> 217c893 Fix a couple of issues raised by a coverity scan

-

16:26 <rharper> biggest item in there is the 19.2 release

-

16:26 <rharper> #link https://discourse.ubuntu.com/t/cloud-init-19-2-release/11873

-

16:26 <rharper> a big thank you from the cloud-init team to everyone who helped contribute to the release

-

16:27 <Goneri> do you have time for a little BSD update?

-

16:27 <rharper> Yes, let's talk about In progress developement

-

16:27 <rharper> #topic In Progress Development

-

16:27 <rharper> Goneri: go ahead

-

16:28 <Goneri> #topic FreeBSD/NetBSD status

-

16:28 <Goneri> so there is two active branches, the first one is: https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368507

-

16:28 <rharper> #link https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368507

-

16:29 <Goneri> it has started with a tiny fix to address a configuration difference with FreeBSD (there is no chpasswd there)

-

16:29 <Goneri> and it's now a slightly bigger refactoring now, I believe it clarify the code base and I would like to land it like that.

-

16:30 <Goneri> a discussion is ongoing with rharper on the PR

-

16:30 <Goneri> second PR is https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/365641

-

16:30 <Goneri> #link https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/365641

-

16:30 <Goneri> this one is much bigger, and I've just addressed the last comment from rharper, I test it often and it works fine for me

-

16:31 <Goneri> if you want to give it a try, I pushed some pre-built images here: http://bsd-cloud-image.org/

-

16:31 <rharper> nice!

-

16:31 <Goneri> I test it with OpenStack and NoCloud, a friend who maintains CBSD also test it on Bhyve (FreeBSD)

-

16:32 <Goneri> finally, the last one is https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368508

-

16:32 <Goneri> #link https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368508

-

16:32 <Goneri> No active merge request yet because it depends on the two actives PR that I just mentioned

-

16:32 <Goneri> this patch brings NetBSD support (7 and 8)

-

16:33 <Goneri> I would like to work on OpenBSD later, but it's still a low priority

-

16:34 <rharper> Goneri: thanks for the update

-

16:34 <Goneri> finally, I've a bunch of scripts that I use to build my images

-

16:35 <Goneri> it's still rather raw, but I would like to integrate that at some point with your CI

-

16:35 <Goneri> that's all

-

16:35 <rharper> thanks

-

16:36 <rharper> #topic In Progress Development

-

16:36 <rharper> #link https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516

-

16:36 <rharper> Adding a new datasource for Exoscale

-

16:36 <rharper> #link https://code.launchpad.net/~xiaofengw/cloud-init/+git/cloud-init/+merge/367889

-

16:36 <rharper> vmware user-defined-scripts

-

16:37 <rharper> #link https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/369783

-

16:37 <rharper> Allow datasources to configure the order of network-config sources

-

16:37 <rharper> #link https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/feature/stage_threadpool

-

16:38 <Odd_Bloke> I'm expecting to have a response to Ryan's review comments on that today, and whatever conclusion we reach shouldn't be too much work to implement.

-

16:38 <rharper> definitely

-

16:38 <Odd_Bloke> And then I'll have a follow-up to split apart the "cmdline" network data source in to "cmdline" and "initramfs", which are currently conflated.

-

16:39 <Odd_Bloke> (Neither of these should cause behavioural changes, they're just setting us up for some data source work down the line.)

-

16:40 <rharper> The threadpool branch is a more general approach to handle running modules async from the mainthread; there were some limitations depending on systemd; and there is a desire for more than just disk_setup to run async; this branch I'm working on would allow modules to be tagged async and they run in a separate thread allowing the next module to proceed; we then join at the end of stage to ensure completion of threads;

-

16:41 <rharper> any other upstream development I'm missing?

-

16:43 <rharper> ok, I think that's it then;

-

16:43 <rharper> #topic Office Hours (next ~30 mins)

-

16:43 <rharper> feel free to ask for help, reviews, discussions on any cloud-init items you're looking at.

-

16:44 <metsuke> Is Ubuntu the recommended, or most maintained, distribution of cloud-init?

-

16:46 <rharper> metsuke: hi; cloud-init in Ubuntu is the most-up-to-date as we're both the upstream maintainers (working for Canonical) and handle getting the latest upstream into Ubuntu images

-

16:47 <rharper> metsuke: we also help produce daily rpm builds for RedHat/Centos/Fedora in our copr repo

-

16:47 <rharper> #link https://copr.fedorainfracloud.org/coprs/g/cloud-init/cloud-init-dev/

-

16:48 <rharper> #link https://download.opensuse.org/repositories/Cloud:/Tools/

-

16:48 <rharper> suse's cloud:Tools keeps a really recent cloud-init as well

-

16:48 <metsuke> great, thanks for the info!

-

16:48 <rharper> sure

-

16:49 <metsuke> I'm looking to distribute standardized VMs to 100+ sites running ESXi so I'm trying to find the best way to do that =)

-

16:52 <Odd_Bloke> metsuke: If you have any questions, please don't hesitate to ask in here; we're generally around US working hours, for reference.

-

16:53 <rharper> yes, cloud-init can help keep your base image generic, allowing customization to happen at boot time;

-

16:53 <metsuke> thanks, I'm trying to do some preliminary investigation so I have an intelligent question to ask =P

-

17:15 <rharper> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2019-08-05.html b/status-2019-08-05.html deleted file mode 100644 index 5c3fdf6..0000000 --- a/status-2019-08-05.html +++ /dev/null @@ -1,267 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Mon 05 August 2019 in status-meeting-minutes - - • 5 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

#cloud-init Reviews: http://bit.ly/ci-reviews | Meeting minutes: https://goo.gl/mrHdaj | Next status meeting Aug 19 16:15 UTC | cloud-init v 19.2 (07/17) | https://bugs.launchpad.net/cloud-init/+filebu

-

The discussion about "#cloud-init Reviews: http://bit.ly/ci-reviews | Meeting minutes: https://goo.gl/mrHdaj | Next status meeting Aug 19 16:15 UTC | cloud-init v 19.2 (07/17) | https://bugs.launchpad.net/cloud-init/+filebu" started at 16:19.

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:20.

- -

In-Progress Development

-

The discussion about "In-Progress Development" started at 16:23.

- -

Recent Changes

-

The discussion about "Recent Changes" started at 16:31.

-

Office Hours (next ~30 mins)

-

The discussion about "Office Hours (next ~30 mins)" started at 16:33.

-

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (56)
  • -
  • tribaal (7)
  • -
  • cyphermox (4)
  • -
  • meetingology (4)
  • -
  • ubot5 (1)
  • -
  • rharper (0)
  • -
-

Full Log

-

16:16 <blackboxsw> #startmeeting Cloud-init bi-weekly status

-

16:16 <meetingology> Meeting started Mon Aug 5 16:16:04 2019 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:16 <meetingology>

-

16:16 <meetingology> Available commands: action commands idea info link nick

-

16:16 <tribaal> o/

-

16:16 <blackboxsw> Heya Chris!

-

16:16 <blackboxsw> Welcome to another cloud-init community status meeting folks.

-

16:17 * blackboxsw finally back from a much needed vacation and have dug myself out of backlog

-

16:17 <blackboxsw> #chair rharper

-

16:17 <meetingology> Current chairs: blackboxsw rharper

-

16:18 <blackboxsw> 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.

-

16:18 <blackboxsw> All interjections updates and questions welcome

-

16:18 <blackboxsw> we may be a bit light this meeting as well as some folks have holidays and travel that coincide with this meeting

-

16:19 <blackboxsw> our format is the following topics: Previous Actions, Recent Changes, In-progress Development, Office Hours

-

16:19 <blackboxsw> we host the meeting every two weeks at the date and time indicated in the IRC channel topic ^

-

16:19 <blackboxsw> I'll update that topic now as I think we forgot to last meeting

-

16:19 <blackboxsw> #topic #cloud-init Reviews: http://bit.ly/ci-reviews | Meeting minutes: https://goo.gl/mrHdaj | Next status meeting Aug 19 16:15 UTC | cloud-init v 19.2 (07/17) | https://bugs.launchpad.net/cloud-init/+filebu

-

16:20 <blackboxsw> next meeting will be two weeks from today, same time

-

16:20 <blackboxsw> #topic Previous Actions

-

16:20 <blackboxsw> #link https://cloud-init.github.io/status-2019-07-22.html#status-2019-07-22

-

16:20 <blackboxsw> groking the meeting last episode, looks like rharper needed to update status on https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381

-

16:20 <ubot5> Ubuntu bug 1832381 in cloud-init (Ubuntu) "vm fails to boot due to conflicting network configuration when user switches from netplan to eni" [Undecided,Incomplete]

-

16:21 <blackboxsw> I think we were awaiting feedback there from AnvoMSFT for a specific reproduce

-

16:21 <blackboxsw> I think we were awaiting feedback there from AnvoMSFT for a specific reproducer

-

16:21 <blackboxsw> so that'll carryover til next meeting if if it a priority

-

16:22 <blackboxsw> the other action from last session was for rharper to ping me on status publishing to github.

-

16:22 <blackboxsw> I've pushed meeting minutes from last two cloud-init status meetings up to cloud-init.github.io so we are closed there

-

16:22 <blackboxsw> no other actions seen

-

16:23 <blackboxsw> #topic In-Progress Development

-

16:24 <blackboxsw> Upstream 19.2 was cut on 7/17 and there are plans to SRU cloud-init within the next week or two into Xenial, bionic, disco and Eaon. I know that we are waiting on closure of a few branches in tip before we SRU cloud-init tip to Xenial ++

-

16:24 <blackboxsw> tribaal: your exoscale branch I believe is one of the ones we want landed before we start our SRU process

-

16:24 <tribaal> I was hoping to address Odd_Bloke 's comments today, but that didn't happen. Tomorrow, or "this week" at the very least is my new target.

-

16:24 <blackboxsw> #link https://code.launchpad.net/~tribaal/cloud-init/+git/cloud-init/+merge/369516

-

16:25 <tribaal> Most of the non-blocking comments should be easy - I want to double check the on-reboot behavior on an actual instance though

-

16:25 <blackboxsw> tribaal: excellent, Odd_Bloke was able to get the review in Friday as he knew he'd be on holiday today and wanted to get you feedback

-

16:25 <tribaal> ack

-

16:26 <tribaal> (the blocking comment about the copyright header should be trivial as well thankfully :) )

-

16:26 <blackboxsw> yeah agreed

-

16:26 <blackboxsw> we also have the following branches we'd like to get "in" and merged to tip before SRU

-

16:26 <blackboxsw> #link https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/370927 (doc updates)

-

16:27 <blackboxsw> #link https://code.launchpad.net/~vtqanh/cloud-init/+git/cloud-init/+merge/369785 (Azure telemetry)

-

16:28 <blackboxsw> and some of goneri's FreeBSD support look like they are straight forward for review/landing

-

16:28 <blackboxsw> #link https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368507

-

16:28 <blackboxsw> #link https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/365641

-

16:29 <blackboxsw> If anyone else out there today is interested in getting reviews/merges before we SRU to Xenial, please feel free to raise a request in channel here or on the mailing list.

-

16:31 <blackboxsw> Also in progress, I just drew up a minispec for DataSourceOVF so that VMware can support merging configuration sources from IMC and OVF if both are present. This allows OVF datasource to configure both static IP config as well as do ssh user imports (which was previously not possible)

-

16:31 <blackboxsw> As always, our in progress development generally will also be represented on trello

-

16:31 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:31 <blackboxsw> #topic Recent Changes

-

16:32 <blackboxsw> the following has landed in tip of master since last cloud-init status meeting

-

16:32 <blackboxsw> % git log --oneline --since 2019-07-22

-

16:33 <blackboxsw> - net/cmdline: split interfaces_by_mac and init network config

-

16:33 <blackboxsw> determination [Daniel Watkins]

-

16:33 <blackboxsw> - stages: allow data sources to override network config source order

-

16:33 <blackboxsw> [Daniel Watkins]

-

16:33 <blackboxsw> #topic Office Hours (next ~30 mins)

-

16:34 <blackboxsw> feel free to ask for help, reviews, discussions on any cloud-init items you're looking at. Otherwise I'll spend some time today getting through the review queue for cloud-init branches.

-

16:34 <blackboxsw> and doing some bug triage

-

16:34 <blackboxsw> thanks tribaal for jumping in BTW.

-

16:35 <tribaal> blackboxsw: my pleasure :)

-

16:36 <tribaal> I'm working on the review points in parallel during office hours as well, that should move things forward hopefully.

-

16:36 <blackboxsw> excellent just ping when ready this week and we'll give a quick pass.

-

16:46 <cyphermox> blackboxsw: yeah, I'm not sure about that eni/netplan conflict; you do need to remove old config from one to the other, otherwise they might fight, but not something I'd expect to break boot.

-

16:47 <blackboxsw> hiya cyphermox. agreed, I think we decided that cloud-init needed to be smart in the transition from netplan ->` eni if someone does that on a system and cloud-init can warn about the behavior change, cleanup old netplan config and render eni in that case.

-

16:48 <blackboxsw> since cloud-init should be smart enough to know what it '

-

16:48 <blackboxsw> used to render

-

16:49 <cyphermox> ack

-

16:49 <cyphermox> yeah, now that I think of it we said the exact same thing last meeting, I think

-

16:51 <blackboxsw> +1, I'm just dusting the vacation cobwebs off. so didn't know if something else happened on that front last week

-

16:52 <cyphermox> well, I recall the convo, that's what I meant

-

17:06 <blackboxsw> I think that about wraps cloud-init status meeting for today folks. Thanks again. And drop us a line on the mailing list (cloud-init@lists.launchpad.net) or here in IRC anytime with questions/discussions.

-

17:06 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2019-08-19.html b/status-2019-08-19.html deleted file mode 100644 index 52f0b4f..0000000 --- a/status-2019-08-19.html +++ /dev/null @@ -1,281 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Mon 19 August 2019 in status-meeting-minutes - - • 6 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2019-08-05.html#status-2019-08-05

-

cloud-init Reviews: http://bit.ly/ci-reviews | Meeting minutes: https://goo.gl/mrHdaj | Next status meeting Sept 2 16:15 UTC | cloud-init v 19.2 (07/17) | https://bugs.launchpad.net/cloud-init/+filebug

-

The discussion about "cloud-init Reviews: http://bit.ly/ci-reviews | Meeting minutes: https://goo.gl/mrHdaj | Next status meeting Sept 2 16:15 UTC | cloud-init v 19.2 (07/17) | https://bugs.launchpad.net/cloud-init/+filebug" started at 16:20.

-

Previous actions

-

The discussion about "Previous actions" started at 16:21.

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:22.

-

In-progress Development

-

The discussion about "In-progress Development" started at 16:25.

- -

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (71)
  • -
  • rharper (9)
  • -
  • meetingology (5)
  • -
  • tribaal (4)
  • -
  • robjo (2)
  • -
  • ubot5 (1)
  • -
  • Odd_Bloke (0)
  • -
-

Full Log

-

16:18 <blackboxsw> #startmeeting Cloud-init bi-weekly status

-

16:18 <meetingology> Meeting started Mon Aug 19 16:18:48 2019 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:18 <meetingology>

-

16:18 <meetingology> Available commands: action commands idea info link nick

-

16:19 <blackboxsw> Hi guys and girls, welcome to cloud-init biweekly status meeting

-

16:19 <blackboxsw> #chair rharper

-

16:19 <meetingology> Current chairs: blackboxsw rharper

-

16:19 <blackboxsw> #chair Odd_Bloke

-

16:19 <meetingology> Current chairs: Odd_Bloke blackboxsw rharper

-

16:19 <blackboxsw> 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.

-

16:19 <blackboxsw> All discussions and interjections are welcome

-

16:19 <blackboxsw> our format is the following topics: Previous Actions, Recent Changes, In-progress Development, Office Hours

-

16:20 <blackboxsw> last meeting's minutes are herer

-

16:20 <blackboxsw> #link https://cloud-init.github.io/status-2019-08-05.html#status-2019-08-05

-

16:20 <rharper> o/

-

16:20 <blackboxsw> we host the meeting every two weeks at the date and time indicated in the IRC channel topic ^

-

16:20 * blackboxsw changes that topic now, since we(I) forgot last time

-

16:20 <blackboxsw> #topic cloud-init Reviews: http://bit.ly/ci-reviews | Meeting minutes: https://goo.gl/mrHdaj | Next status meeting Sept 2 16:15 UTC | cloud-init v 19.2 (07/17) | https://bugs.launchpad.net/cloud-init/+filebug

-

16:21 <blackboxsw> next meeting in two weeks

-

16:21 <blackboxsw> #topic Previous actions

-

16:21 <blackboxsw> I see no previous actions raised during last meeting. Woo hoo!

-

16:22 <blackboxsw> #topic Recent Changes

-

16:22 <blackboxsw> the following are commits that

-

16:22 <blackboxsw> have landed in tip of master for cloud-init since the last meeting: git log --since 2019-08-04

-

16:22 <blackboxsw> - cloudinit/distros/parsers/sys_conf: add docstring to SysConf

-

16:22 <blackboxsw> [Daniel Watkins]

-

16:22 <blackboxsw> - pyflakes: remove unused variable [Joshua Powers]

-

16:22 <blackboxsw> - Azure: Record boot timestamps, system information, and diagnostic events

-

16:22 <blackboxsw> [Anh Vo]

-

16:22 <blackboxsw> - DataSourceOracle: configure secondary NICs on Virtual Machines

-

16:22 <blackboxsw> [Daniel Watkins]

-

16:22 <blackboxsw> - distros: fix confusing variable names [Daniel Watkins]

-

16:22 <blackboxsw> - azure/net: generate_fallback_nic emits network v2 config instead of v1

-

16:22 <blackboxsw> [Chad Smith]

-

16:22 <blackboxsw> - Add support for publishing host keys to GCE guest attributes

-

16:22 <blackboxsw> [Rick Wright]

-

16:22 <blackboxsw> - New data source for the Exoscale.com cloud platform [Chris Glass]

-

16:22 <blackboxsw> - doc: remove intersphinx extension [Daniel Watkins]

-

16:22 <blackboxsw> - cc_set_passwords: rewrite documentation [Daniel Watkins] (LP: #1838794)

-

16:22 <ubot5> Launchpad bug 1838794 in cloud-init "Set Passwords documentation describes incorrect behaviour for password config key" [Low,Fix committed] https://launchpad.net/bugs/1838794

-

16:24 <blackboxsw> We have also published commits though " - Azure: Record boot timestamps, system information, and diagnostic events" to Ubuntu Eoan (19.10) (cloud-init v.19.2-13) if folks want a glimpse of those features

-

16:24 <blackboxsw> Many thanks to Azure and GCE folks for their commits and a hi five to tribaal for adding Exoscale

-

16:25 <blackboxsw> #topic In-progress Development

-

16:25 <blackboxsw> As always, we try to keep most of our work up to date in trello

-

16:25 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:26 <blackboxsw> cards in the "Reviewing" column should represent the work we expect to have up for review in the short term.

-

16:27 <blackboxsw> rharper is mid-stream on some investigations that will likely lead to significant speed improvements for cloud-init

-

16:28 <blackboxsw> Odd_Bloke: is working on some significant improvements for Oracle's datasource rendering network config

-

16:29 <blackboxsw> and I'm working on getting OpenStack and Ec2 datasources to talk network config v2.

-

16:29 <blackboxsw> beyond that work we have a pretty healther active review queue

-

16:29 <blackboxsw> #link https://code.launchpad.net/cloud-init/+activereviews

-

16:31 <blackboxsw> of note, some freebsd work is in flight, gce dns improvements, udev triggers and OVF handling user-defined scripts.

-

16:31 <blackboxsw> We

-

16:32 <blackboxsw> will spend the latter part of this meeting looking over the review queue to see that open branches are in the proper state

-

16:33 <blackboxsw> Also, our plan for this week is to cut a Cloud-init SRU (Stable release update) for upload into xenial, bionic and disco.

-

16:34 <blackboxsw> expectation is that those Ubuntu series will see an update for cloud-init after our ~7 days of testing and verification

-

16:34 <blackboxsw> rharper: Odd_Bloke anything else in flight that we should note here?

-

16:34 <rharper> that looks like everything

-

16:35 <blackboxsw> without further ado, we can transition to office hours

-

16:35 <blackboxsw> #topic Office Hours (next ~30 mins)

-

16:36 <blackboxsw> We're here for any questions, bugs, discussions people would like to have around cloud-init. This block of time is available for any discussions or requests people may have.

-

16:37 <blackboxsw> We will also spend this time grooming the active review queue to make sure developers get any needed feedback on their active branches.

-

16:37 <blackboxsw> If there are any branches that need more eyes, please bring them up here or make sure they are in the 'Needs review' state in Launchpad

-

16:38 <tribaal> blackboxsw: thanks!

-

16:40 <blackboxsw> tribaal: good work. I think Odd_Bloke landed the followup work to enable exoscale datasource config to cloud-init.templates to 'enable' it. And looks like that has landed

-

16:40 <tribaal> blackboxsw: I'm happy to help verify SRU bugs when the process is kicked - just let me know

-

16:40 <blackboxsw> so it's 'on' in Eoan, once SRU is kicked off, it'll be in there

-

16:41 <tribaal> yep, I need to push an Eoan template to our preprod environment tomorrow to kick the tires, but I don't expect anything funny

-

16:41 <blackboxsw> tribaal: will do. I think the only thing we are waiting on before SRU is landing this ubuntu-drivers branch https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/371369

-

16:42 <blackboxsw> any feedback on behavior your in Eoan from you tribaal would be helpful.

-

16:43 <blackboxsw> let's try that in English this time: any feedback on the behavior in your Eoan environment would be helpful tribaal.

-

16:43 <tribaal> blackboxsw: haha that's what I inferred :)

-

16:43 <blackboxsw> :) /me hits the review queue

-

16:47 <blackboxsw> rharper: if you get a chance: you've landed https://git.launchpad.net/cloud-init/commit/?id=b3a87fc0. Do we also still need the following branch? https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/363571

-

16:48 <blackboxsw> If so, I'll spend this time trying to write up unit tests for this if possible

-

16:48 <rharper> blackboxsw: I don't think so; my branch should include all the needs of that branch

-

16:49 <rharper> and the branch tests the wait_for_physdev as well as updates the opensuse net render paths to account for the udev rule number change

-

16:50 <blackboxsw> that's kindof what I was thinking/hoping. I'll mark it rejected in favor of your commit, and we'll see what robjo thinks on that. We can reopen and try to address the unit test aspect of his branch if still needed.

-

16:50 <rharper> I think we can mark that branch closed

-

16:50 <rharper> robjo: had already looked at the branch before landing

-

16:52 <blackboxsw> ok done

-

16:54 <blackboxsw> thanks Florian for your first commit! https://code.launchpad.net/~florian-mueller-v/cloud-init/+git/cloud-init/+merge/371298 ... doc update approved

-

16:58 <robjo> I don't recall having looked at https://git.launchpad.net/cloud-init/commit/?id=b3a87fc0 and there was no entry in the bug to remind me that I did. Anyway, I've done so now and yes, this obsoletes https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/363571

-

17:00 <blackboxsw> thank you robjo for that

-

17:04 <rharper> robjo: https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/366667 ; yes, I should have linked to the bug in my MP

-

17:04 <rharper> you did take a look a while back though

-

17:06 <robjo> rharper: I believe you, just cannot remember....

-

17:06 <rharper> heh, it was a while back

-

17:24 <blackboxsw> I think we should probably wrap up the meeting for this week. I've got one more review to clear.

-

17:24 <blackboxsw> Thanks again all for joining. minutes will be posted to github

-

17:25 <blackboxsw> #link https://cloud-init.github.io/

-

17:25 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2019-09-09.html b/status-2019-09-09.html deleted file mode 100644 index de6064f..0000000 --- a/status-2019-09-09.html +++ /dev/null @@ -1,275 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Mon 09 September 2019 in status-meeting-minutes - - • 5 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2019-08-19.html#status-2019-08-19

-

Previous actions

-

The discussion about "Previous actions" started at 16:30.

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:31.

- -

In-progress Development

-

The discussion about "In-progress Development" started at 16:38.

- -

Office Hours (next ~30 mins)

-

The discussion about "Office Hours (next ~30 mins)" started at 16:48.

- -

Vote results

-

Action items, by person

-
    -
  • blackboxsw
  • -
  • blackboxsw send email to the list notifying of status meeting day change.
  • -
-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (64)
  • -
  • meetingology (5)
  • -
  • Odd_Bloke (4)
  • -
  • ubot5 (2)
  • -
  • rharper (1)
  • -
-

Full Log

-

16:26 <blackboxsw> #startmeeting Cloud-init bi-weekly status

-

16:26 <meetingology> Meeting started Mon Sep 9 16:26:10 2019 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:26 <meetingology>

-

16:26 <meetingology> Available commands: action commands idea info link nick

-

16:27 <blackboxsw> Hey folks, welcome to the ~biweekly cloud-init status meeting.

-

16:28 <blackboxsw> #chair rharper Odd_Bloke

-

16:28 <meetingology> Current chairs: Odd_Bloke blackboxsw rharper

-

16:28 <Odd_Bloke> o/

-

16:28 <blackboxsw> 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.

-

16:30 <blackboxsw> Feel free to interject at any time. Our typical format is the following: Previous Actions, Recent Changes, In-progress Development, Office Hours (~30 mins)

-

16:30 <blackboxsw> Last meeting's minutes live here:

-

16:30 <blackboxsw> #link https://cloud-init.github.io/status-2019-08-19.html#status-2019-08-19

-

16:30 <blackboxsw> #topic Previous actions

-

16:31 <blackboxsw> no actions from last meeting so we'll plow right through to Recent Changes

-

16:31 <blackboxsw> #topic Recent Changes

-

16:32 <blackboxsw> The following branches have landed in tip since last meeting: via git log --since 2019-08-19

-

16:32 <blackboxsw> - doc: document doc, create makefile and tox target [Joshua Powers]

-

16:32 <blackboxsw> - .gitignore: ignore files produced by package builds [Daniel Watkins]

-

16:32 <blackboxsw> - docs: fix whitespace, spelling, and line length [Joshua Powers]

-

16:32 <blackboxsw> - docs: remove unnecessary file in doc directory [Joshua Powers]

-

16:32 <blackboxsw> - Oracle: Render secondary vnic IP and MTU values only [Ryan Harper]

-

16:32 <blackboxsw> - exoscale: fix sysconfig cloud_config_modules overrides

-

16:32 <blackboxsw> [Chad Smith] (LP: #1841454)

-

16:32 <ubot5> Launchpad bug 1841454 in cloud-init "Exoscale datasource overwrites all cloud_config_modules" [Undecided,Fix committed] https://launchpad.net/bugs/1841454

-

16:32 <blackboxsw> - net/cmdline: refactor to allow multiple initramfs network config sources

-

16:32 <blackboxsw> [Daniel Watkins]

-

16:32 <blackboxsw> - ubuntu-drivers: call db_x_loadtemplatefile to accept NVIDIA EULA

-

16:32 <blackboxsw> [Chad Smith] (LP: #1840080)

-

16:32 <ubot5> Launchpad bug 1840080 in cloud-init (Ubuntu) "cloud-init cc_ubuntu_drivers does not set up /etc/default/linux-modules-nvidia" [High,Fix released] https://launchpad.net/bugs/1840080

-

16:32 <blackboxsw> - Add missing #cloud-config comment on first example in documentation.

-

16:32 <blackboxsw> [Florian Müller]

-

16:32 <blackboxsw> - ubuntu-drivers: emit latelink=true debconf to accept nvidia eula

-

16:32 <blackboxsw> [Chad Smith] (LP: #1840080)

-

16:32 <blackboxsw> - DataSourceOracle: prefer DS network config over initramfs

-

16:32 <blackboxsw> [Daniel Watkins]

-

16:32 <blackboxsw> - format.rst: add text/jinja2 to list of content types (+ cleanups)

-

16:32 <blackboxsw> [Daniel Watkins]

-

16:32 <blackboxsw> - Add GitHub pull request template to point people at hacking doc

-

16:32 <blackboxsw> [Daniel Watkins]

-

16:34 <blackboxsw> Additionally: we have also cut a stable-18.4 branch from the 18.4 tag as our last supported python2.6 branch. There will be an email sent out to the mailing list about the intent of this branch. It requires a couple of minor fixes to make sure py2.6 support is functional, but this will be reference branch for any distribution that does not have access to py.27 or later. No additional feature development is

-

16:34 <blackboxsw> planned on stable-18.4

-

16:37 <blackboxsw> a reminder again that python2.6 support was 'dropped' in cloud-init upstream as of the 18.4 release, so expectations for py2.6 support stopped in 18.4 and there is a deprecation plan for py 2.7 as well

-

16:37 <blackboxsw> #link https://lists.launchpad.net/cloud-init/msg00170.html

-

16:37 <blackboxsw> Again, see the mailinglist for details and updates

-

16:37 <blackboxsw> #link https://lists.launchpad.net/cloud-init/

-

16:38 <blackboxsw> #topic In-progress Development

-

16:38 <blackboxsw> Last week or so the team has been working on SRU validation for cloud-init 19.2.24 into Xenial, Bionic and Disco.

-

16:39 <blackboxsw> We have passed all SRU validation tests and our expected pubish date for 19.2.24 is tomorrow for those Ubuntu series

-

16:40 <blackboxsw> good work on validation folks

-

16:41 <blackboxsw> and thanks for extra cloud-init community verification from exoscale, azure and VMware for validation efforts

-

16:42 <blackboxsw> There is additional Oracle, FreeBSD and Azure work in flight at the moment as well as some boot speed improvements and analysis from rharper

-

16:43 <blackboxsw> The following link represents any carded work upstream is tracking. The Doing lane is content or features we expect to land shortly

-

16:43 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:47 <blackboxsw> Now is probably a good time to also mention that our entire ubuntu server team also reflects our weekly accomplishements over in the ubuntu-server discourse. If there are deeper discussions or questions on various topics or features please join us there as well

-

16:47 <blackboxsw> #link https://discourse.ubuntu.com/c/server

-

16:48 <blackboxsw> I think that about wraps it for in-progress development

-

16:48 <blackboxsw> #topic Office Hours (next ~30 mins)

-

16:48 <blackboxsw> upstream cloud-init devs will have eyes on this channel for any discussions, questions, bugs or feature work the greater community would like to discuss.

-

16:49 <blackboxsw> During this time, we'll also groom our activereview queue to make sure we try to get review comments out to devs who have active branches.

-

16:49 <blackboxsw> Again, thanks for tuning in

-

16:57 <blackboxsw> Ok just addressed review comments on https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/372432 . I'm reviewing https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368507

-

16:59 * blackboxsw also sets the next meeting topic so we don't forget.

-

17:01 <blackboxsw> Odd_Bloke: rharper powersj, I think we decided to shift from Mondays to Tuesdays for status meetings to avoid collisions with holidays, vacation work travel etc. Are we doing that for next status meeting, or maybe waiting to discuss that more broadly?

-

17:02 <Odd_Bloke> Tuesday in two weeks is likely to be a travel day for anyone heading to the cloud-init summit.

-

17:02 <Odd_Bloke> But Monday is likely to be a swap day for Canonical folks because we're all travelling next week too.

-

17:03 <blackboxsw> hrm right, maybe we wait then and discuss at the summit

-

17:03 <Odd_Bloke> So I would perhaps suggest skipping the next meeting, and then we can resume on Tuesdays two weeks after the summit?

-

17:03 <blackboxsw> discuss scheduling changes that is

-

17:03 <blackboxsw> sure, let's push/postpone until summit +2 weeks

-

17:05 <blackboxsw> #action blackboxsw send email to the list notifying of status meeting day change.

-

17:05 * meetingology blackboxsw send email to the list notifying of status meeting day change.

-

17:10 <rharper> +1 Odd_Bloke

-

17:11 <blackboxsw> Also note that the version of cloud-init that has undergone SRU verification is also published to our copr el-testing repo. We only update that repo during upstream cloud-init releases XX.YY and any Ubuntu SRUs so it is much more stable than our daily copr repo.

-

17:11 <blackboxsw> #link https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/

-

17:33 <blackboxsw> I think that about wraps our cloud-init status meeting for today. I'm wrapping up my review here and will post it to the set_passwords branch.

-

17:33 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2019-10-08.html b/status-2019-10-08.html deleted file mode 100644 index 5059cbf..0000000 --- a/status-2019-10-08.html +++ /dev/null @@ -1,363 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Tue 08 October 2019 in status-meeting-minutes - - • 9 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:23.

- -

Recent Changes

-

The discussion about "Recent Changes" started at 16:25.

-
    -
  • ACTION: blackboxsw verify cpc image builds are unpaused/unblocked for Azure
  • -
-

In-progress Development

-

The discussion about "In-progress Development" started at 16:36.

- -

Community Charter

-

The discussion about "Community Charter" started at 16:44.

- -

Upcoming meetings and releases

-

The discussion about "Upcoming meetings and releases" started at 16:47.

-
    -
  • ACTION: upstream cloud-init email about 19.3 release date
  • -
-

Office Hours (next ~30 mins)

-

The discussion about "Office Hours (next ~30 mins)" started at 16:52.

-
    -
  • ACTION: revisit python deprecation and report to mailinglist
  • -
-

Vote results

-

Action items, by person

- -

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (110)
  • -
  • ubot5 (8)
  • -
  • AnhVoMSFT (8)
  • -
  • meetingology (8)
  • -
  • Odd_Bloke (7)
  • -
  • rharper (3)
  • -
  • ahosmanmsft (1)
  • -
-

Full Log

-

16:18 <blackboxsw> #startmeeting Cloud-init bi-weekly status

-

16:18 <meetingology> Meeting started Tue Oct 8 16:18:28 2019 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:18 <meetingology>

-

16:18 <meetingology> Available commands: action commands idea info link nick

-

16:18 <blackboxsw> Welcome back folks o/ And thanks AnhVoMSFT for the ping to get us started

-

16:18 <blackboxsw> #chair rharper Odd_Bloke

-

16:19 <blackboxsw> #chair rharper Odd_Bloke

-

16:19 <meetingology> Current chairs: Odd_Bloke blackboxsw rharper

-

16:19 <blackboxsw> 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.

-

16:19 <Odd_Bloke> o/

-

16:19 <Odd_Bloke> Thanks for the reminder, Anh.

-

16:19 <blackboxsw> Feel free to interject at any time. Our typical format is the following: Previous Actions, Recent Changes, In-progress Development, Office Hours (~30 mins).

-

16:21 <blackboxsw> For this, and subsequent, status meetings I proposed we add a new topic: Ongoing Community Charter which would give context on the new trello lane we added at the cloud-init summit.

-

16:21 <blackboxsw> Odd_Bloke: rharper AnhVoMSFT does that sound good? We can then better advertise and remind about long-term community involvement projects that are available for anyone

-

16:22 <AnhVoMSFT> I would propose that the last agenda item of any status meeting would be to update the banner to reflect the next status meeting - and perhaps the next ETA for next release / SRU

-

16:22 <blackboxsw> +1 AnhVoMSFT that sounds good too.

-

16:22 <AnhVoMSFT> yep, sounds good on the Community Charter

-

16:22 <rharper> AnhVoMSFT: +1

-

16:22 <rharper> I think one topic each

-

16:22 <rharper> and end with the next status meeting

-

16:23 <blackboxsw> ok starting to turn the meeting crank

-

16:23 <blackboxsw> #topic Previous Actions

-

16:23 <blackboxsw> last meeting was 09/09/2019

-

16:23 <blackboxsw> #link https://cloud-init.github.io/status-2019-09-09.html#status-2019-09-09

-

16:23 <blackboxsw> meeting minutes at the link above ^

-

16:24 <blackboxsw> only action was #action blackboxsw send email to the list notifying of status meeting day change.

-

16:24 <blackboxsw> which was done https://lists.launchpad.net/cloud-init/msg00224.html

-

16:24 <blackboxsw> no further outstanding actions from last meeting

-

16:25 <blackboxsw> #topic Recent Changes

-

16:25 <blackboxsw> The following branches have landed in tip since last meeting: via git log --since 2019-09-09

-

16:27 <blackboxsw> - Add RbxCloud datasource [Adam Dobrawy]

-

16:27 <blackboxsw> - get_interfaces: don't exclude bridge and bond members (LP: #1846535)

-

16:27 <blackboxsw> - Add support for Arch Linux in render-cloudcfg [Conrad Hoffmann]

-

16:27 <blackboxsw> - util: json.dumps on python 2.7 will handle UnicodeDecodeError on binary

-

16:27 <blackboxsw> (LP: #1801364)

-

16:27 <ubot5> Launchpad bug 1846535 in cloud-init "cloud-init 19.2.36 fails with python exception "Not all expected physical devices present ..." during bionic image deployment from MAAS" [Critical,Fix committed] https://launchpad.net/bugs/1846535

-

16:27 <ubot5> Launchpad bug 1801364 in cloud-init "persisting OpenStack metadata fails" [Undecided,Fix committed] https://launchpad.net/bugs/1801364

-

16:27 <blackboxsw> oopsie daisy

-

16:27 <AnhVoMSFT> :)

-

16:27 <blackboxsw> got kicked on flood. chunking that now

-

16:27 <blackboxsw> - Add RbxCloud datasource [Adam Dobrawy]

-

16:27 <blackboxsw> - get_interfaces: don't exclude bridge and bond members (LP: #1846535)

-

16:27 <blackboxsw> - Add support for Arch Linux in render-cloudcfg [Conrad Hoffmann]

-

16:27 <blackboxsw> - util: json.dumps on python 2.7 will handle UnicodeDecodeError on binary

-

16:27 <blackboxsw> (LP: #1801364)

-

16:27 <blackboxsw> - debian/ubuntu: add missing word to netplan/ENI header (LP: #1845669)

-

16:27 <blackboxsw> - ovf: do not generate random instance-id for IMC customization path

-

16:27 <ubot5> Launchpad bug 1845669 in cloud-init "The meaning of "Changes to it will not persist across an instance." in 50-cloud-init.yaml is unclear" [Undecided,Fix committed] https://launchpad.net/bugs/1845669

-

16:27 <blackboxsw> - sysconfig: only write resolv.conf if network_state has DNS values

-

16:27 <blackboxsw> (LP: #1843634)

-

16:27 <blackboxsw> - sysconfig: use distro variant to check if available (LP: #1843584)

-

16:27 <blackboxsw> - systemd/cloud-init.service.tmpl: start after wicked.service

-

16:27 <ubot5> Launchpad bug 1843634 in cloud-init (Suse) "cloud-init misconfigure the network on SLES" [Undecided,Incomplete] https://launchpad.net/bugs/1843634

-

16:27 <blackboxsw> [Robert Schweikert]

-

16:27 <blackboxsw> - docs: fix zstack documentation lints

-

16:28 <ubot5> Launchpad bug 1843584 in cloud-init "cloudinit/net/sysconfig.py lacks support for openSUSE 15.x and Tumbleweed" [Medium,Fix committed] https://launchpad.net/bugs/1843584

-

16:28 <blackboxsw> - analyze/show: remove trailing space in output

-

16:28 <blackboxsw> - Add missing space in warning: "not avalid seed" [Brian Candler]

-

16:28 <blackboxsw> - pylintrc: add 'enter_context' to generated-members list

-

16:28 <blackboxsw> - Add datasource for ZStack platform. [Shixin Ruan] (LP: #1841181)

-

16:28 <blackboxsw> - docs: organize TOC and update summary of project [Joshua Powers]

-

16:28 <blackboxsw> - tools: make clean now cleans the dev directory, not the system

-

16:28 <blackboxsw> - docs: create cli specific page [Joshua Powers]

-

16:28 <ubot5> Launchpad bug 1841181 in cloud-init "add datasource for ZStack" [Low,Fix committed] https://launchpad.net/bugs/1841181

-

16:28 <blackboxsw> - docs: added output examples to analyze.rst [Joshua Powers]

-

16:28 <blackboxsw> - docs: doc8 fixes for instancedata page [Joshua Powers]

-

16:28 <blackboxsw> - docs: clean up formatting, organize boot page [Joshua Powers]

-

16:28 <blackboxsw> - net: add is_master check for filtering device list (LP: #1844191)

-

16:28 <ubot5> Launchpad bug 1844191 in cloud-init "azure advanced networking sometimes triggers duplicate mac detection" [Critical,Fix committed] https://launchpad.net/bugs/1844191

-

16:28 <blackboxsw> - docs: more complete list of availability [Joshua Powers]

-

16:28 <blackboxsw> - docs: start FAQ page [Joshua Powers]

-

16:28 <blackboxsw> - docs: cleanup output & order of datasource page [Joshua Powers]

-

16:28 <blackboxsw> - Brightbox: restrict detection to require full domain match .brightbox.com

-

16:28 <blackboxsw> - VMWware: add option into VMTools config to enable/disable custom script.

-

16:28 <blackboxsw> [Xiaofeng Wang]

-

16:28 <blackboxsw> - net,Oracle: Add support for netfailover detection

-

16:28 <blackboxsw> - atomic_helper: add DEBUG logging to write_file (LP: #1843276)

-

16:28 <ubot5> Launchpad bug 1843276 in cloud-init "cloudinit.atomic_helper.write_file should have the same logging as util.write_file" [Low,Fix committed] https://launchpad.net/bugs/1843276

-

16:29 <blackboxsw> Thanks Brian, Shixin Ruan, Conrad Hoffmann, Adam Dobrawy and robjo for the contributions over the last month!

-

16:29 <blackboxsw> beyond tip commits to cloud-init the upstream team went through two SRUs of cloud-init

-

16:30 <blackboxsw> it's also excellent to see new datasources like the RbxCloud datasource added

-

16:31 <blackboxsw> cloud-init just passed validation for Ubuntu Xenial, Bionic and Disco on the 2nd SRU 19.2-36-g059d049c-0ubuntu2

-

16:31 <blackboxsw> cloud-images today should have that updated revision in them I blieve

-

16:32 <blackboxsw> there are fixes for both Azure accelerated networking support and handling issues seen on MAAS network bridge configuration

-

16:32 <AnhVoMSFT> on that note the last Azure image we had published was early September, which still didn't have the first SRU

-

16:32 <AnhVoMSFT> is there something going on with the image publishing pipeline again?

-

16:33 <blackboxsw> AnhVoMSFT: the publishing pipeline paused while we sorted the 2nd SRU pass for maas network bridge issues introduced by 19.2-36-g059d049c-0ubuntu1

-

16:33 <AnhVoMSFT> i see - that makes sense

-

16:34 <blackboxsw> 19.2-36-g059d049c-0ubuntu2 was verified as fixing all support there for both Azure and MAAS datasources and the expectation is that image builds are continuing today but I'll verify that the box is ✔ there on images rebuilding

-

16:34 <Odd_Bloke> There may also be Azure-specific publication pipeline issues, which we wouldn't necessarily know about off-hand.

-

16:34 <blackboxsw> #action blackboxsw verify cpc image builds are unpaused/unblocked for Azure

-

16:34 * meetingology blackboxsw verify cpc image builds are unpaused/unblocked for Azure

-

16:34 <blackboxsw> thx Odd_Bloke right

-

16:35 <blackboxsw> looks like Odd_Bloke is already on that verification internally

-

16:35 <blackboxsw> ok so SRU is through verification on our side. cloudimages should be getting latest version of cloud-init for Xenial, Bionic and Disco imminently

-

16:36 <blackboxsw> I think that is it for Recent Changes

-

16:36 <blackboxsw> #topic In-progress Development

-

16:37 <blackboxsw> the SRU verification work took a bit of steam out of our current work in progress as it involved a lot of manual and upgrade scenario tests.

-

16:37 <blackboxsw> But, as always we try to track ongoing work in trello

-

16:37 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:38 <blackboxsw> there are a number of branches in progress that are of interest:

-

16:39 <blackboxsw> Azure CI for one would be a great add for cloud-init's CI infrastructure

-

16:39 <blackboxsw> https://code.launchpad.net/~ahosmanmsft/cloud-init/+git/cloud-init/+merge/372957

-

16:39 <blackboxsw> we need to get eyes on that this week if we can

-

16:39 <blackboxsw> #action cloud-init upstream review https://code.launchpad.net/~ahosmanmsft/cloud-init/+git/cloud-init/+merge/372957

-

16:39 * meetingology cloud-init upstream review https://code.launchpad.net/~ahosmanmsft/cloud-init/+git/cloud-init/+merge/372957

-

16:39 <ahosmanmsft> That would be great

-

16:40 <blackboxsw> there are also a number of freebsd branches that need to close out.

-

16:40 <blackboxsw> and I know Odd_Bloke has started peeking at some initial github integration for CI.

-

16:40 <blackboxsw> Odd_Bloke: any details you want to add about github CI at the moment?

-

16:41 <Odd_Bloke> I've started iterating on a Travis configuration to run what we currently run in our CI pipeline.

-

16:41 <Odd_Bloke> Unsurprisingly, setting up linting/unit testing was easy.

-

16:42 <Odd_Bloke> The other thing we do is run some integration testing from a built deb file. I got as far as being able to successfully sbuild the package in Travis, and ran into some initial stumbling blocks with running lxd.

-

16:42 <Odd_Bloke> That's as far as I've got, I expect to pick that work back up this week.

-

16:42 <blackboxsw> thanks Odd_Bloke , I've added the following card to trello for those interested.

-

16:43 <blackboxsw> #link https://trello.com/c/pqA1adVM/1195-investigate-adding-github-travis-ci-to-cloud-init

-

16:43 <blackboxsw> I think that about wraps in progress work. We'll tackle reviews a bit at the end of the meeting

-

16:43 <blackboxsw> ok next topic

-

16:44 <blackboxsw> #topic Community Charter

-

16:45 <blackboxsw> at the cloud-init summit we decided to highlight community work in trello so that any community member with some dev cycles and interest can join in and contribute to ongoing tasks

-

16:45 <blackboxsw> that lane is now in trello representing low-hanging-fruit content that upstream cloud-init is interested in completing, and that anyone can commit to.

-

16:45 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:46 <blackboxsw> the lane is labelled "Community low-hanging-fruit" and currently contains a number of doc update work items as well as json schema validation extensions for each cloud-init config module

-

16:47 <blackboxsw> we invite everyone to participate and feel free to grab those items as they have interest

-

16:47 <blackboxsw> we'll revisit this topic in each meeting so folks have context

-

16:47 <blackboxsw> #topic Upcoming meetings and releases

-

16:48 <blackboxsw> cloud-init upstream has just passed validation of cloud-init 19.2.36-*-ubuntu2 which should approved for upload into Xenial, Disco and Bionic (and queued for Eoan)

-

16:48 <blackboxsw> the cloud build team will be generating images for various clouds imminently and we will confirm that build pipelines are active so platforms get new bits asap

-

16:50 <blackboxsw> 19.3 upstream should by coming shortly, we will update the topic with the expected upstream release date and send an email to the mailing list with the estimated upstream cut

-

16:51 <blackboxsw> #action upstream cloud-init email about 19.3 release date

-

16:51 * meetingology upstream cloud-init email about 19.3 release date

-

16:52 <blackboxsw> next meeting is Oct 22

-

16:52 <blackboxsw> same bat time same bat channel

-

16:52 <blackboxsw> #topic Office Hours (next ~30 mins)

-

16:52 <blackboxsw> we spend this time for reviews, bug triage and cloud-init discussions.

-

16:53 <blackboxsw> upstream devs should have eyes on this channel. Thanks everyone for tuning in

-

16:54 <AnhVoMSFT> have you had a chance to discuss about the python deprecation issue, or did the SRU verification take most of the time since the summit

-

16:58 <blackboxsw> AnhVoMSFT: last week was vacation plus the remainder of us on sru verification .

-

17:00 <blackboxsw> But now we have cleared that hurdle we should we able to discuss it this week.

-

17:00 <AnhVoMSFT> yep, sounds good.

-

17:01 <blackboxsw> #action revisit python deprecation and report to mailinglist

-

17:01 * meetingology revisit python deprecation and report to mailinglist

-

17:01 <blackboxsw> Good meeting for actions

-

17:54 <blackboxsw> Thanks for the participation folks I'll publish minutes to github

-

17:54 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2019-10-29.html b/status-2019-10-29.html deleted file mode 100644 index 82bb233..0000000 --- a/status-2019-10-29.html +++ /dev/null @@ -1,393 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Tue 29 October 2019 in status-meeting-minutes - - • 12 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:26.

- -

Recent Changes

-

The discussion about "Recent Changes" started at 16:36.

-

In-progress Development

-

The discussion about "In-progress Development" started at 16:41.

- -

Community Charter

-

The discussion about "Community Charter" started at 16:49.

- -

Upcoming meetings

-

The discussion about "Upcoming meetings" started at 16:57.

-

Upcoming Releases

-

The discussion about "Upcoming Releases" started at 16:58.

- -

Office Hours (next ~30 mins)

-

The discussion about "Office Hours (next ~30 mins)" started at 17:00.

-
    -
  • ACTION: cloud-init upstream discuss where/how/if to host documentation supported cloud-init versions for debian/suse/redhat/ubuntu/freebsd etc.
  • -
  • 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.
  • -
  • LINK: https://github.com/cloud-init/ubuntu-sru/blob/master/manual/ec2-sru-19.2.36.ubuntu2.txt
  • -
  • ACTION: mailing list update to cloud-init community about procedure/timeline for migration to github
  • -
-

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (130)
  • -
  • tribaal (34)
  • -
  • meetingology (8)
  • -
  • ubot5 (7)
  • -
  • Odd_Bloke (2)
  • -
  • chillysurfer (1)
  • -
  • rharper (0)
  • -
-

Full Log

-

16:20 <blackboxsw> #startmeeting Cloud-init bi-weekly status

-

16:20 <meetingology> Meeting started Tue Oct 29 16:20:09 2019 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:20 <meetingology>

-

16:20 <meetingology> Available commands: action commands idea info link nick

-

16:20 <blackboxsw> Boo! Welcome to the Halloween edition of cloud-init bi-weekly status meeting

-

16:20 <blackboxsw> #chair rharper

-

16:20 <meetingology> Current chairs: blackboxsw rharper

-

16:20 <blackboxsw> #chair Odd_Bloke

-

16:20 <meetingology> Current chairs: Odd_Bloke blackboxsw rharper

-

16:21 <blackboxsw> 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.

-

16:21 <blackboxsw> 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

-

16:22 <blackboxsw> So that we don't forget, let's set the topic for next status meeting.

-

16:22 <blackboxsw> Odd_Bloke: rharper does 11/12 look good?

-

16:22 <blackboxsw> as in, no holidays etc?

-

16:25 <blackboxsw> ok topic updated. Any concerns we can change it and send out an email to the mailing list

-

16:26 <blackboxsw> 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).

-

16:26 <blackboxsw> #topic Previous Actions

-

16:26 <blackboxsw> I have three actions from last meeting

-

16:26 <blackboxsw> #link https://cloud-init.github.io/status-2019-10-08.html#status-2019-10-08

-

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.

-

16:28 <blackboxsw> We also established a point of contact via email for continued cloud image status updates

-

16:29 * blackboxsw cloud-init upstream review https://code.launchpad.net/~ahosmanmsft/cloud-init/+git/cloud-init/+merge/372957 . 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

-

16:30 <chillysurfer> nice, good work ahosmanMSFT

-

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. https://lists.launchpad.net/cloud-init/msg00229.html

-

16:30 <blackboxsw> #link https://lists.launchpad.net/cloud-init/msg00229.html

-

16:30 <blackboxsw> thx chillysurfer :)

-

16:31 <blackboxsw> 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

-

16:31 <blackboxsw> 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

-

16:33 <blackboxsw> 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 <YEAR>.<minor_release_number> where minor_release_number will be [1-4]

-

16:34 <blackboxsw> 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.

-

16:35 <blackboxsw> 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.

-

16:35 <blackboxsw> ok long-winded. But I think that was our actions from last cloud-init status meeting.

-

16:35 <blackboxsw> next topic

-

16:36 <blackboxsw> #topic Recent Changes

-

16:37 <blackboxsw> The following branches have landed in tip since last meeting: via git log --since 2019-10-08

-

16:37 <blackboxsw> - net/netplan: use ipv6-mtu key for specifying ipv6 mtu values

-

16:37 <blackboxsw> - Fix usages of yaml, and move yaml_dump to safeyaml.dumps. (LP: #1849640)

-

16:37 <blackboxsw> - exoscale: Increase url_max_wait to 120s. [Chris Glass]

-

16:37 <blackboxsw> - net/sysconfig: fix available check on SUSE distros

-

16:37 <blackboxsw> [Robert Schweikert] (LP: #1849378)

-

16:37 <blackboxsw> - docs: Fix incorrect Azure IMDS IP address [Joshua Powers] (LP: #1849508)

-

16:37 <blackboxsw> - introduce .travis.yml

-

16:37 <ubot5> Launchpad bug 1849640 in cloud-init "security scan reported insecure yaml load method usage in latest cloud-init code" [Undecided,Fix committed] https://launchpad.net/bugs/1849640

-

16:37 <blackboxsw> - net: enable infiniband support in eni and sysconfig renderers

-

16:37 <blackboxsw> [Darren Birkett] (LP: #1847114)

-

16:37 <ubot5> Launchpad bug 1849378 in cloud-init "sysconfig renderer not detected on SLE distros" [Medium,Fix committed] https://launchpad.net/bugs/1849378

-

16:37 <blackboxsw> - guestcust_util: handle special characters in config file [Xiaofeng Wang]

-

16:37 <blackboxsw> - fix some more typos in comments [Dominic Schlegel]

-

16:37 <ubot5> Launchpad bug 1849508 in cloud-init "Azure IMDS documentation wrong about IP address" [High,Fix committed] https://launchpad.net/bugs/1849508

-

16:37 <blackboxsw> - replace any deprecated log.warn with log.warning

-

16:37 <blackboxsw> [Dominic Schlegel] (LP: #1508442)

-

16:37 <blackboxsw> - net: handle openstack dhcpv6-stateless configuration

-

16:37 <blackboxsw> [Harald Jensås] (LP: #1847517)

-

16:37 <ubot5> Launchpad bug 1847114 in cloud-init "Infiniband network devices not configured correctly on Ubuntu" [Medium,Fix committed] https://launchpad.net/bugs/1847114

-

16:37 <blackboxsw> - Add .venv/ to .gitignore [Dominic Schlegel]

-

16:37 <blackboxsw> - Small typo fixes in code comments. [Dominic Schlegel]

-

16:37 <blackboxsw> - cloud_test/lxd: Retry container delete a few times

-

16:37 <blackboxsw> - Add Support for e24cloud to Ec2 datasource. (LP: #1696476)

-

16:37 <ubot5> Launchpad bug 1508442 in python-watcherclient "LOG.warn is deprecated" [Low,In progress] https://launchpad.net/bugs/1508442

-

16:37 <ubot5> Launchpad bug 1847517 in cloud-init "cloudinit/net/sysconfig.py write incorrect config for dhcp-stateless openstack subnets" [Medium,Fix committed] https://launchpad.net/bugs/1847517

-

16:37 <ubot5> Launchpad bug 1696476 in cloud-init "Identification of e24cloud platform as using Ec2 datasource" [Low,Fix committed] https://launchpad.net/bugs/1696476

-

16:39 <blackboxsw> some good incremental improvements on SuSE, FreeBSD,Ubuntu Azure, Ec2, OpenStack and Exoscale

-

16:40 <blackboxsw> Thanks Dominic, Robert, XiaoFeng, Harald and Darren and Scott for the contibutions this round!

-

16:41 <blackboxsw> #topic In-progress Development

-

16:41 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:42 <blackboxsw> We keep track of most of cloud-init's development efforts on the cloud-init and curtin trello board above.

-

16:43 <blackboxsw> And the active review queue for cloud-init is a good representation of what should land shortly.

-

16:43 <blackboxsw> #link http://bit.ly/ci-reviews

-

16:44 <blackboxsw> The following work-streams are currently in progress:

-

16:44 <blackboxsw> - CI for Azure (thanks ahosmanMSFT)

-

16:44 <blackboxsw> - Openstack networking v2 support (which allows openstack to talk v2 network config 'netplan' )

-

16:45 <blackboxsw> - Azure async disk mounts

-

16:45 <blackboxsw> - cloud-init boot performance improvements

-

16:46 <blackboxsw> As features related to those streams make progress we'll be updating the trello board and dragging cards to the done lane

-

16:47 <blackboxsw> There are also a number of branches for FreeBSD support up that we need to shepherd and merge I think

-

16:48 <blackboxsw> #link https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368507

-

16:48 <blackboxsw> #link https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/365641

-

16:48 <blackboxsw> We'll be able to review some of the outstanding branches during Office hours today

-

16:49 <blackboxsw> #topic Community Charter

-

16:50 <blackboxsw> 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.

-

16:51 <blackboxsw> 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

-

16:51 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

16:52 <blackboxsw> Our current community goal is to scrub, update and correct all datasource docs seen @ https://cloudinit.readthedocs.io/en/latest/topics/datasources.html

-

16:52 <tribaal> That's nice!

-

16:52 <blackboxsw> all help is appreciated especially from the datasource owners

-

16:52 <blackboxsw> \o tribaal.

-

16:52 <tribaal> o/

-

16:53 <tribaal> sorry, I'm following along, didn't mean to interrupt

-

16:53 <blackboxsw> 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.

-

16:55 <blackboxsw> There are around 50 modules that would need a jsonschema definition so that we can promote our cloud-init devel schema command to it can properly vet any #cloud-config a user provides to annotate user errors

-

16:55 <blackboxsw> 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

-

16:56 <blackboxsw> example https://trello.com/c/NENad4m3/1172-schema-add-initial-schema-definition-for-ccpowerstatechange

-

16:56 <blackboxsw> no worries, interruptions welcome

-

16:56 <blackboxsw> think that about wraps up community charter.

-

16:56 <blackboxsw> two to topics to go

-

16:57 <blackboxsw> #topic Upcoming meetings

-

16:57 <blackboxsw> 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

-

16:58 <blackboxsw> #topic Upcoming Releases

-

16:59 <blackboxsw> 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

-

16:59 <blackboxsw> Immediately after release, we'll publish to Ubuntu's devel release Focal Fossa and our copr repo

-

16:59 <tribaal> nice! this answers one of the questions I had coming in today :)

-

16:59 <blackboxsw> #link https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/

-

16:59 <blackboxsw> good deal tribaal

-

17:00 <blackboxsw> and again, upstream will schedulae 19.4 release probably ~6 weeks after 19.3 so not long to wait if folks miss 19.3

-

17:00 <blackboxsw> schedule even

-

17:00 <blackboxsw> #topic Office Hours (next ~30 mins)

-

17:01 <blackboxsw> 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

-

17:02 <tribaal> blackboxsw: I suspect the plan for y'all is to SRU 19.3 into the various Ubuntues after it lands in focal?

-

17:03 <tribaal> my latest bugfix, although small, impacts one of our customers so I'd like to give them a heads up in that direction

-

17:03 <blackboxsw> tribaal: yep sorry, I mentioned earlier, but should have mentioned in the last topic

-

17:03 <tribaal> no worries

-

17:03 <tribaal> it's the logical follow-up to a release - so it was surely implied

-

17:04 <blackboxsw> 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

-

17:04 <tribaal> blackboxsw: do you know how/when cloud-init lands in other distros, as a matter of curiosity?

-

17:04 <blackboxsw> I think now that Ubuntu Eoan is released and post-release dust is settling we'll have bandwidth to cover that

-

17:05 <blackboxsw> tribaal: robjo knows for SLES. otubo (hrm not here today) is managing RHEL/CentOS release schedules

-

17:06 <blackboxsw> and debian is trying to shore up to 19.X I believe.

-

17:06 <tribaal> ack

-

17:06 <blackboxsw> but I think other distros are delayed (for good reasons: testing/validation/stability/etc).

-

17:07 <tribaal> sure, that would make sense

-

17:07 <tribaal> more QA is good :)

-

17:07 * blackboxsw finds myself wanting a current support matrix on cloudinit.readthedocs.io

-

17:07 <blackboxsw> or somewhere

-

17:07 <tribaal> that would be incredibly useful to us :)

-

17:08 <blackboxsw> agreed. Maybe we can take an action to at least discuss what that would look like (and where to host it)

-

17:08 <tribaal> tracking where and when our new datasource is available is a bit of a mystery right now :)

-

17:08 <tribaal> (except for Ubuntus)

-

17:09 <blackboxsw> #action cloud-init upstream discuss where/how/if to host documentation supported cloud-init versions for debian/suse/redhat/ubuntu/freebsd etc.

-

17:09 * meetingology cloud-init upstream discuss where/how/if to host documentation supported cloud-init versions for debian/suse/redhat/ubuntu/freebsd etc.

-

17:09 <tribaal> blackboxsw: another question since I have the mic: would it be useful to you to add us to your CI pipeline?

-

17:09 <blackboxsw> 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

-

17:11 <tribaal> 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)

-

17:11 <blackboxsw> 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

-

17:12 <blackboxsw> tribaal: yeah let me restate the action then

-

17:12 <blackboxsw> #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.

-

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.

-

17:12 <blackboxsw> per scheduling we at least could start filling in some gaps there on cloud-init planned distro releases

-

17:13 <tribaal> 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).

-

17:13 <tribaal> is that something we can do ourselves?

-

17:13 <tribaal> (code wise at least)

-

17:14 <blackboxsw> tribaal: codewise, if you are talking about manual tests, we generally run something like the following:

-

17:14 <blackboxsw> #link https://github.com/cloud-init/ubuntu-sru/blob/master/manual/ec2-sru-19.2.36.ubuntu2.txt

-

17:15 <blackboxsw> if you wanted to write up an example manual sru test and propose it to https://github.com/cloud-init/ubuntu-sru/

-

17:15 <blackboxsw> you could follow the examples in https://github.com/cloud-init/ubuntu-sru/blob/master/manual/ec2-sru-19.2.36.ubuntu2.txt

-

17:15 <blackboxsw> oops wrong paste

-

17:15 <blackboxsw> you could follow the examples in : https://github.com/cloud-init/ubuntu-sru/tree/master/sru-templates/manual

-

17:16 <tribaal> oh, I see

-

17:16 <tribaal> so thankfully it's only manual in the "manually run a script" sense :)

-

17:16 <blackboxsw> 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

-

17:17 <tribaal> yes, that would work (myself, and a handful of colleagues would be happy to I guess)

-

17:17 <blackboxsw> 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 https://code.launchpad.net/~ahosmanmsft/cloud-init/+git/cloud-init/+merge/372957

-

17:18 <blackboxsw> having the cloud_tests platform definition would allow us our you to more easily extend a jenkins CI job to drive the cloud tests

-

17:19 <tribaal> ah nice, that makes sense

-

17:19 <blackboxsw> 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.

-

17:20 <tribaal> yeah that sounds like a good first step, and we can expand later on if/when needed

-

17:24 <blackboxsw> +1 tribaal

-

17:24 <blackboxsw> btw good deal that you were able to run into Odd_Bloke on your travels. Always good to see a familiar face

-

17:24 <tribaal> yeah that was a crazy coincidence

-

17:25 <tribaal> my brother got married in Odd_Bloke 's backyard :)

-

17:25 <tribaal> I wish we could do cross-company colocated sprints :P

-

17:26 <blackboxsw> heh, I think we can call those #cloud-init-summits :)

-

17:26 <tribaal> ohhh yeah :)

-

17:26 <tribaal> when's the next one?

-

17:26 <blackboxsw> we'll have to get invites together for the next one (Fall 2020)

-

17:27 <tribaal> noted :)

-

17:29 <blackboxsw> Ohh right and BIG NEWS that I forgot to highlight: cloud-init is moving from launchpad to github. We discussed this at the last cloud-init summit a couple of weeks ago.

-

17:29 <blackboxsw> Odd_Bloke: and rharper have been working on getting initial travis.yml together for allowing travis to run our CI tests.

-

17:30 <tribaal> ohhh big news indeed!

-

17:30 <Odd_Bloke> That has, indeed, landed. You can see it at https://github.com/cloud-init/cloud-init/blob/master/.travis.yml (it's also in the Launchpad git repo, we're still syncing from there to GH ATM :).

-

17:31 <Odd_Bloke> And you can see that we're green at https://travis-ci.org/cloud-init/cloud-init

-

17:31 <blackboxsw> 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 @ https://github.com/cloud-init/cloud-init instead of posting branch review requests at https://git.launchpad.net/cloud-init

-

17:31 <tribaal> very nice!

-

17:33 <blackboxsw> 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

-

17:33 <tribaal> ah that would make sese yeah

-

17:34 <blackboxsw> 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

-

17:35 <blackboxsw> #action mailing list update to cloud-init community about procedure/timeline for migration to github

-

17:35 * meetingology mailing list update to cloud-init community about procedure/timeline for migration to github

-

17:36 <blackboxsw> 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

-

17:36 <blackboxsw> thanks Odd_Bloke and rharper for all the work there so far

-

17:38 <blackboxsw> 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.

-

17:38 <blackboxsw> thanks for participating chillysurfer & tribaal

-

17:38 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2019-11-26.html b/status-2019-11-26.html deleted file mode 100644 index d86ca8f..0000000 --- a/status-2019-11-26.html +++ /dev/null @@ -1,361 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Tue 26 November 2019 in status-meeting-minutes - - • 9 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 17:28.

- -

Recent Changes

-

The discussion about "Recent Changes" started at 17:36.

-

In-progress Development

-

The discussion about "In-progress Development" started at 17:39.

- -

Community Charter

-

The discussion about "Community Charter" started at 17:46.

- -

Upcoming Meetings

-

The discussion about "Upcoming Meetings" started at 17:52.

-

Office Hours (next ~30 mins)

-

The discussion about "Office Hours (next ~30 mins)" started at 17:52.

-

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (124)
  • -
  • ubot5 (16)
  • -
  • ahosmanMSFT (5)
  • -
  • meena (5)
  • -
  • chillysurfer (5)
  • -
  • meetingology (4)
  • -
  • Goneri (1)
  • -
  • Odd_Bloke (0)
  • -
-

Full Log

-

17:23 <blackboxsw> #startmeeting Cloud-init bi-weekly status

-

17:23 <meetingology> Meeting started Tue Nov 26 17:23:40 2019 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

17:23 <meetingology>

-

17:23 <meetingology> Available commands: action commands idea info link nick

-

17:24 <blackboxsw> #chair Odd_Bloke

-

17:24 <meetingology> Current chairs: Odd_Bloke blackboxsw

-

17:24 <blackboxsw> Hi folks welcome to another cloud-init status meeting.

-

17:24 <blackboxsw> 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.

-

17:25 <blackboxsw> And as you've likely heard, we are shifting this meeting by +1 hr for the season to avoid meeting collisions with some of the upstream devs

-

17:25 <blackboxsw> I'll set the topic for next meeting so we don't forget

-

17:28 <blackboxsw> so Dec 10th, two weeks from today, same time as today

-

17:28 <blackboxsw> without further ado, let's jump into things

-

17:28 <blackboxsw> 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).

-

17:28 <blackboxsw> #topic Previous Actions

-

17:28 <blackboxsw> I'm going from our last meeting minutes at the following url

-

17:28 <blackboxsw> #link https://cloud-init.github.io/status-2019-10-29.html#status-2019-10-29

-

17:29 <blackboxsw> blackboxsw to 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.

-

17:29 <blackboxsw> I did forward the proper Microsoft channel contact to other Microsoft dev teams working on cloud-init

-

17:30 <blackboxsw> so I think thats COMPLETE

-

17:31 <blackboxsw> Also to note is that cloud image builds though are still stale for Azure & Ec2 on focal. There are a couple of bugs in the image build process that Canonical's cloud image team is sorting to get those image builders unblocked

-

17:31 <blackboxsw> Xenial, Bionic, Eoan images all look up to date

-

17:32 <chillysurfer> bug reports and issues are still going to be reported through launchpad right?

-

17:32 <blackboxsw> previous-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. Resolved. Upstream decided that it was going to be a bit of a maintenance cost to have a full table of all distributions and all versions of cloud-init as well as the planned support plan.

-

17:32 <blackboxsw> chillysurfer: +1 yes please do. file away and we'll tackle that

-

17:32 <chillysurfer> blackboxsw: great thanks!

-

17:33 <blackboxsw> previous-action: mailing list update to cloud-init community about procedure/timeline for migration to github. rharper took care of that per

-

17:33 <blackboxsw> #link https://lists.launchpad.net/cloud-init/msg00231.html

-

17:34 <blackboxsw> Again for folks, we have moved cloud-init upstream to github for code and CI. Launchpad still being used for package build recipes and bugs/ issues

-

17:35 <blackboxsw> If you have signed the CLA (thanks ahosmanMSFT) then we need to link your github account to the Lauchpad username you signed the CLA with. See the hacking doc for more information

-

17:35 <blackboxsw> #link https://cloudinit.readthedocs.io/en/latest/topics/hacking.html

-

17:35 <blackboxsw> Think that wraps actions.

-

17:36 <blackboxsw> #topic Recent Changes

-

17:36 <meena> I've been very slowly working towards better freebsd support

-

17:37 <blackboxsw> The following branches have landed in tip since last meeting: via git log --since 10.29.2019

-

17:37 <meena> Goneri has moved his network patch over to github, and a NetBSD patch, tok

-

17:37 <blackboxsw> - tools: migrate-lp-user-to-github removes repo_dir if created (#35)

-

17:37 <blackboxsw> - Correct jumbled documentation for cc_set_hostname module (#64)

-

17:37 <blackboxsw> [do3meli] (LP: #1853543)

-

17:37 <blackboxsw> - FreeBSD: fix for get_linux_distro() and lru_cache (#59)

-

17:37 <blackboxsw> [Igor Galić] (LP: #1815030)

-

17:37 <ubot5> Launchpad bug 1853543 in cloud-init "jumbled documentation for cc_set_hostname module" [Undecided,Fix committed] https://launchpad.net/bugs/1853543

-

17:37 <ubot5> Launchpad bug 1815030 in cloud-init "FreeBSD: Unable to determine distribution" [Undecided,Fix committed] https://launchpad.net/bugs/1815030

-

17:37 <blackboxsw> bah got kicked. let's try that again

-

17:38 <blackboxsw> - tools: migrate-lp-user-to-github removes repo_dir if created (#35)

-

17:38 <blackboxsw> 10:37 - Correct jumbled documentation for cc_set_hostname module (#64)

-

17:38 <blackboxsw> 10:37 [do3meli] (LP: #1853543)

-

17:38 <blackboxsw> 10:37 - FreeBSD: fix for get_linux_distro() and lru_cache (#59)

-

17:38 <blackboxsw> 10:37 [Igor Galić] (LP: #1815030)

-

17:38 <blackboxsw> 10:37 - lp-to-git-users: adding do3meli [Dominic Schlegel]

-

17:38 <blackboxsw> 10:37 - ec2: Add support for AWS IMDS v2 (session-oriented) (#55)

-

17:38 <blackboxsw> 10:37 - tests: Fix cloudsigma tests when no dmidecode data is present. (#57)

-

17:38 <blackboxsw> 10:37 - net: IPv6, accept_ra, slaac, stateless (#51)

-

17:38 <blackboxsw> 10:37 [Harald] (LP: #1806014, #1808647)

-

17:38 <ubot5> Launchpad bug 1808647 in cloud-init "cloud-init hard codes IPV6_AUTOCONF=no, which prevents EC2 instances from getting a v6 default gateway if NetworkManager is disabled" [Medium,Fix committed] https://launchpad.net/bugs/1808647

-

17:38 <ubot5> Launchpad bug 1806014 in cloud-init "[Centos] IPV6_AUTOCONF=no when using dhcp6" [Medium,Fix committed] https://launchpad.net/bugs/1806014

-

17:38 <blackboxsw> - docs: Update the configdrive datasource links (#44)

-

17:38 <blackboxsw> [Joshua Powers] (LP: #1852461)

-

17:38 <blackboxsw> - lp-to-git-users: adding PengpengSun [Pengpeng Sun]

-

17:38 <blackboxsw> - lp-to-git-users: adding trstringer [Thomas Stringer]

-

17:38 <blackboxsw> - lp-to-git-users: adding hjensas [Harald Jensås]

-

17:38 <blackboxsw> - distro: correctly set usr_lib_exec path for FreeBSD distro (#40)

-

17:38 <blackboxsw> [Igor Galić] (LP: #1852491)

-

17:38 <ubot5> Launchpad bug 1852461 in cloud-init "Broken links in config-drive docs on RTD" [Medium,Fix committed] https://launchpad.net/bugs/1852461

-

17:38 <ubot5> Launchpad bug 1852491 in cloud-init "usr_lib_exec path is wrong on FreeBSD" [Medium,Fix committed] https://launchpad.net/bugs/1852491

-

17:38 <blackboxsw> - azure: support secondary ipv6 addresses (#33)

-

17:38 <blackboxsw> - Fix metadata check when local-hostname is null (#32)

-

17:38 <blackboxsw> [Mark Goddard] (LP: #1852100)

-

17:38 <blackboxsw> - Merge pull request #38 from blackboxsw/cleanup/run-ci-on-pull-request

-

17:38 <blackboxsw> - switch default FreeBSD salt minion pkg from py27 to py36

-

17:38 <blackboxsw> [Dominic Schlegel]

-

17:38 <ubot5> Launchpad bug 1852100 in cloud-init "Cloud-init fails if metadata local-hostname is null" [Undecided,In progress] https://launchpad.net/bugs/1852100

-

17:38 <blackboxsw> - lp-to-git-users: adding igalic [Igor Galić]

-

17:38 <blackboxsw> - travis: only run CI on pull requests

-

17:38 <blackboxsw> - add data-server dns entry as new metadata server detection [Joshua Hügli]

-

17:38 <blackboxsw> - lp-to-git-users: adding chrisglass [Chris Glass]

-

17:38 <blackboxsw> - lp-to-git-users: adding larsks [Lars Kellogg-Stedman]

-

17:38 <blackboxsw> - Merge pull request #31 from raharper/fix/pycodestyle-tip

-

17:38 <blackboxsw> - pycodestyle: remove unused local variable

-

17:38 <blackboxsw> - reporting: Using a uuid to enforce uniqueness on the KVP keys. [momousta]

-

17:38 <blackboxsw> - docs: touchups in rtd intro and README.md

-

17:38 <blackboxsw> - doc: update launchpad git refs to github

-

17:38 <blackboxsw> - tools: migrate script needs to write tools/.lp-to-git-user

-

17:38 <blackboxsw> - github: drop pull-request template to prepare for migration

-

17:38 <blackboxsw> - tools: add migrate-lp-user-to-github script to link LP to github

-

17:38 <blackboxsw> - github: new basic project readme

-

17:38 <blackboxsw> - Release 19.3 (LP: #1851428)

-

17:38 <ubot5> Launchpad bug 1851428 in cloud-init "Release 19.3" [Medium,In progress] https://launchpad.net/bugs/1851428

-

17:38 <blackboxsw> - azure: support matching dhcp route-metrics for dual-stack ipv4 ipv6

-

17:38 <blackboxsw> (LP: #1850308)

-

17:38 <blackboxsw> - configdrive: fix subplatform config-drive for /config-drive source

-

17:38 <blackboxsw> [David Kindred] (LP: #1849731)

-

17:38 <ubot5> Launchpad bug 1850308 in cloud-init "cloud-init on azure with dual stack needs to add route-metric for dhcp6 also" [High,Fix committed] https://launchpad.net/bugs/1850308

-

17:38 <ubot5> Launchpad bug 1849731 in cloud-init "Introduction of subplatform around 18.5 broke ConfigDrive" [Undecided,Fix committed] https://launchpad.net/bugs/1849731

-

17:39 <blackboxsw> - DataSourceSmartOS: reconfigure network on each boot

-

17:39 <blackboxsw> [Mike Gerdts] (LP: #1765801)

-

17:39 <blackboxsw> - Add config for ssh-key import and consuming user-data [Pavel Zakharov]

-

17:39 <blackboxsw> - net: fix subnet_is_ipv6() for stateless|stateful

-

17:39 <blackboxsw> [Harald Jensås] (LP: #1848690)

-

17:39 <blackboxsw> - OVF: disable custom script execution by default [Xiaofeng Wang]

-

17:39 <blackboxsw> - cc_puppet: Implement csr_attributes.yaml support [Matthias Baur]

-

17:39 <ubot5> Launchpad bug 1765801 in cloud-init "network should be optionally reconfigured on every boot" [Undecided,Fix committed] https://launchpad.net/bugs/1765801

-

17:39 <blackboxsw> - cloud-init.service: on centos/fedora/redhat wait on

-

17:39 <blackboxsw> NetworkManager.service (LP: #1843334)

-

17:39 <blackboxsw> - azure: Do not lock user on instance id change

-

17:39 <blackboxsw> [Sam Eiderman] (LP: #1849677)

-

17:39 <ubot5> Launchpad bug 1848690 in cloud-init "subnet_is_ipv6() function does not work for types ipv6_dhcpv6-stateless|stateful" [Undecided,Fix committed] https://launchpad.net/bugs/1848690

-

17:39 <ubot5> Launchpad bug 1843334 in cloud-init "Change location of DHCP leases in CloudStack provider as it doesn't work for RHEL8" [Medium,Fix committed] https://launchpad.net/bugs/1843334

-

17:39 <ubot5> Launchpad bug 1849677 in cloud-init "azure locks existing user if instance id changes" [Medium,Fix committed] https://launchpad.net/bugs/1849677

-

17:39 <blackboxsw> #topic In-progress Development

-

17:40 <ahosmanMSFT> Looking into this

-

17:40 <ahosmanMSFT> Launchpad bug 1849677 in cloud-init "azure locks existing user if instance id changes" [Medium,Fix committed] https://launchpad.net/bugs/1849677

-

17:40 <ubot5> Ubuntu bug 1849677 in cloud-init "azure locks existing user if instance id changes" [Medium,Fix committed]

-

17:40 <blackboxsw> As meena mentioned there is a lot of work going on to improve FreeBSD support.

-

17:40 <blackboxsw> Thanks do3meli and meena for that herculean effort

-

17:41 <blackboxsw> ahosmanMSFT: also has be working on getting Azure CI up and running. That branch will land just as soon as this meeting is over

-

17:41 <blackboxsw> we also have landed a significant AWS feature for IMDSv2.

-

17:42 <blackboxsw> It looks like we'll have a bug to sort on that front

-

17:42 <chillysurfer> bug report just opened up

-

17:42 <chillysurfer> https://bugs.launchpad.net/cloud-init/+bug/1854084

-

17:42 <ubot5> Ubuntu bug 1854084 in cloud-init "Headers no longer passed through read_file_or_url" [Undecided,New]

-

17:42 <blackboxsw> thanks chillysurfer !

-

17:43 <blackboxsw> will get on that today and confirm

-

17:43 <chillysurfer> blackboxsw: great thanks! let me know what you think when you know some things

-

17:43 <blackboxsw> will do

-

17:44 <blackboxsw> also in the "In progress" topic are the WIP branches that rharper has up to lay ground work for opting in to cloud-init hotplug support

-

17:45 <blackboxsw> #link https://github.com/canonical/cloud-init/pull/48

-

17:45 <blackboxsw> #link https://github.com/canonical/cloud-init/pull/47

-

17:45 <blackboxsw> we'll be trying to pull in hotplug functionality into this cycle, so expect work land on that front before 19.4 I'm guessing

-

17:45 <blackboxsw> sorry I mean version 20.1

-

17:46 <blackboxsw> ok next topic

-

17:46 <blackboxsw> #topic Community Charter

-

17:46 <meena> i want to test Goneri's network https://github.com/canonical/cloud-init/pull/61 , but a prerequisite to make that easier is https://github.com/canonical/cloud-init/pull/42 and it appears only rharper knows how to write tests for that part of the code

-

17:47 <meena> what's hotplug support mean in this context?

-

17:48 <blackboxsw> This Community Charter topic is a placeholder to remind anyone with some spare cycles that as a community anyone can drop in for low-hanging fruit or discrete tasks that will contribute to a better cloud-init

-

17:48 <blackboxsw> the community charter is currently:

-

17:48 <blackboxsw> 1. updated datasource docs

-

17:48 <blackboxsw> 2. get json schema implementation writting for each cloudinit.config.cc_*py module

-

17:49 <Goneri> meena, I can generate some prebuilt images with my last patch

-

17:49 <blackboxsw> those items are cards on our trello board in the community low-hanging-fruit lane that anyone grab and work

-

17:49 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

17:50 <blackboxsw> ... sorry meena, needed to finish my thought. so we'd like review and closure on 42?

-

17:50 <blackboxsw> >> what's hotplug support mean in this context? hotplug network device events currently would be the baseline.

-

17:51 <blackboxsw> so network config would be rewritten as devices show up or disappear

-

17:51 <blackboxsw> if someone opts into cloud-init controlling the running network config post-boot

-

17:52 <blackboxsw> #topic Upcoming Meetings

-

17:52 <blackboxsw> as set earlier. Dec 10th for another status meeting at this hour

-

17:52 <blackboxsw> #topic Office Hours (next ~30 mins)

-

17:53 <blackboxsw> This time is a chance for open discussions really on any cloud-init topic. bugs, issues, branches that need review etc. In the absence of other discussion, devs will be hitting the review queue to chip away at existing PRs to keep them from getting stale

-

17:56 <meena> blackboxsw: yes, please, 42 fix would be good

-

17:59 <blackboxsw> ok looking now

-

17:59 <blackboxsw> ahosmanMSFT: I'm landing your Azure CI first

-

18:04 <blackboxsw> ahosmanMSFT: would you like to provide me with a bit more information in the commit message https://code.launchpad.net/~ahosmanmsft/cloud-init/+git/cloud-init/+merge/372957 for enabling Azure integration testing? the 'commit message' in the UI will be the final message shown in cloud-init logs and it might be nice to have a bit more context

-

18:04 <ahosmanMSFT> blackboxsw Adding now

-

18:04 <blackboxsw> thank you sir

-

18:14 <ahosmanMSFT> blackboxsw take a look and let me know if I should add anything

-

18:15 <ahosmanMSFT> Added Azure to cloud tests supporting upstream integration testing. This Implements the inherited platform classes, Azure configurationsto release/platform, and docs on how to run Azure CI.

-

18:44 <blackboxsw> meena: I may come up with an alternative suggestion to address smoser's suggestion to run dmidecode once. it's a bit of a lift though as dmidecode output isn't structured very easy to parse

-

19:00 <blackboxsw> ahh I should close out the meeting

-

19:00 <blackboxsw> Thanks folks for attending. Until next time use the IRC channel or mailing list

-

19:00 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2019-12-10.html b/status-2019-12-10.html deleted file mode 100644 index 39be3e9..0000000 --- a/status-2019-12-10.html +++ /dev/null @@ -1,301 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Tue 10 December 2019 in status-meeting-minutes - - • 6 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

Previous Actions

-

The discussion about "Previous Actions" started at 17:22.

- -

Recent Changes

-

The discussion about "Recent Changes" started at 17:28.

-

In-progress Development

-

The discussion about "In-progress Development" started at 17:31.

- -

Community Charter

-

The discussion about "Community Charter" started at 17:40.

- -

Office Hours (next ~30 mins)

-

The discussion about "Office Hours (next ~30 mins)" started at 17:45.

- -

Vote results

-

Action items, by person

- -

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (79)
  • -
  • meetingology (7)
  • -
  • meena (5)
  • -
  • ubot5 (3)
  • -
  • Odd_Bloke (2)
  • -
  • rharper (1)
  • -
-

Full Log

-

17:17 <blackboxsw> #startmeeting Cloud-init bi-weekly status

-

17:17 <meetingology> Meeting started Tue Dec 10 17:17:14 2019 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

17:17 <meetingology>

-

17:17 <meetingology> Available commands: action commands idea info link nick

-

17:18 <blackboxsw> Welcome folks to another cloud-init status meeting. Probably the last one of the year I presume due to upcoming Holidays in two weeks

-

17:18 <blackboxsw> #chair rharper

-

17:18 <meetingology> Current chairs: blackboxsw rharper

-

17:18 <blackboxsw> #chair Odd_Bloke

-

17:18 <meetingology> Current chairs: Odd_Bloke blackboxsw rharper

-

17:18 <rharper> o/

-

17:18 <blackboxsw> 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.

-

17:19 <blackboxsw> Let's start the meeting with setting the next meeting time

-

17:19 <blackboxsw> day/time

-

17:20 <blackboxsw> I think most of upstream is out the last two weeks of December. Shall we try January 7th?

-

17:20 <blackboxsw> Anyone opposed can voice their discontent as I remember the keystrokes to set the topic of the channel ;)_

-

17:21 <blackboxsw> I also dropped 19.3 upstream release date from the channel topic as "that's soooo November"

-

17:22 <blackboxsw> topics for this round: Feel free to interject/suggest other topics at any time. Our typical format is the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Upcoming Meetings, Office Hours (~30 mins).

-

17:22 <blackboxsw> #topic Previous Actions

-

17:22 <blackboxsw> #topic Previous Actions

-

17:23 <blackboxsw> and oops, forgot to publish meeting minutes from last session.

-

17:23 <blackboxsw> doing that now.

-

17:24 <meena> is it meeting time or did I miss it?

-

17:25 <Odd_Bloke> meena: It's happening as we speak.

-

17:27 <blackboxsw> ok sorry for the delay. just pushed published meeting minutes

-

17:27 <blackboxsw> #link https://cloud-init.github.io/status-2019-11-26.html#status-2019-11-26

-

17:27 <blackboxsw> ok so previous actions from last meeting:

-

17:28 <blackboxsw> no unresolved actions listed

-

17:28 <blackboxsw> #topic Recent Changes

-

17:29 <blackboxsw> found via git log --since 11.26.2019

-

17:29 <blackboxsw> - dhcp: Support RedHat dhcp rfc3442 lease format for option 121 (#76)

-

17:29 <blackboxsw> [Eric Lafontaine] (LP: #1850642)

-

17:29 <blackboxsw> - network_state: handle empty v1 config (#45) (LP: #1852496)

-

17:29 <blackboxsw> - Merge pull request #94 from gaughen/patch-1 [Joshua Powers]

-

17:29 <blackboxsw> - removed a couple of "the"s [gaughen]

-

17:29 <blackboxsw> - docs: fix line length and remove highlighting [Joshua Powers]

-

17:29 <blackboxsw> - docs: Add security.md to readthedocs [Joshua Powers]

-

17:29 <ubot5> Launchpad bug 1850642 in cloud-init "No support for classless-static-routes on centos 7" [Medium,Triaged] https://launchpad.net/bugs/1850642

-

17:29 <blackboxsw> - Multiple file fix for AuthorizedKeysFile config (#60) [Eduardo Otubo]

-

17:29 <blackboxsw> - Merge pull request #88 from OddBloke/travis [Joshua Powers]

-

17:29 <blackboxsw> - Revert "travis: only run CI on pull requests"

-

17:29 <blackboxsw> - doc: update links on README.md [Joshua Powers]

-

17:29 <ubot5> Launchpad bug 1852496 in cloud-init (Ubuntu) "nocloud network-config mishandles empty config" [Low,In progress] https://launchpad.net/bugs/1852496

-

17:29 <blackboxsw> - doc: Updates to wording of README.md [Joshua Powers]

-

17:29 <blackboxsw> - Add security.md [Joshua Powers]

-

17:29 <blackboxsw> - setup.py: Amazon Linux sets libexec to /usr/libexec (#52)

-

17:29 <blackboxsw> [Frederick Lefebvre]

-

17:29 <blackboxsw> - Fix linting failure in test_url_helper (#83) [Eric Lafontaine]

-

17:29 <blackboxsw> - url_helper: read_file_or_url should pass headers param into readurl

-

17:29 <blackboxsw> (#66) (LP: #1854084)

-

17:29 <blackboxsw> - dmidecode: log result after stripping n [Igor Galić]

-

17:29 <blackboxsw> - cloud_tests: add azure platform support to integration tests

-

17:29 <blackboxsw> [ahosmanmsft]

-

17:29 <ubot5> Launchpad bug 1854084 in cloud-init "Headers no longer passed through read_file_or_url" [Undecided,Fix committed] https://launchpad.net/bugs/1854084

-

17:31 <blackboxsw> thanks for all the FreeBSD work landing, utility improvements, caching and doc changes. + the dhcp lease format updates

-

17:31 <blackboxsw> #topic In-progress Development

-

17:32 <blackboxsw> Generally upstream is doing a fair job of getting reviews to the community for PRs, though lately we've been spending a few cycles on SRU validation for cloud-init 19.4.31 into Ubuntu Xenial, Bionic, Disco and Eoan.

-

17:32 <blackboxsw> expectation is that we should be able to clear this SRU validation today/tomorrow and get back onto the review queue in github for cloud-init

-

17:33 <blackboxsw> most major cloud-platforms have passed validation with no regressions, so risk is low with this release

-

17:34 <blackboxsw> oops cloud-init 19.3.41 not 19.4.31

-

17:35 <blackboxsw> there is plenty of work in flight by meena (FreeBSD improvements) and ahosmanMSFT (Azure instance-id work). that we hope to get reviewed and landed.

-

17:36 <blackboxsw> community notice: Reminder we are working toward a 19.4 upstream release by end of year. So if there are bits/features that you hope to make the cut. please get those branches in shape by next tuesday Decemeber 17th

-

17:36 <blackboxsw> #link https://lists.launchpad.net/cloud-init/msg00236.html

-

17:37 <blackboxsw> community notice: Also a reminder that cloud-inig 19.4 will be the last release that claims official support for py2.7

-

17:37 <blackboxsw> in January, tip of cloud-init will be allowed to drift from python2.7 support and tox -e py27 will no longer be exercised by upstream CI

-

17:38 <blackboxsw> Odd_Bloke: or rharper anyything else in-progress at the moment?

-

17:39 <blackboxsw> also, anyone interested in cloud-init development, please run tools/migrate-lp-user-to-github as mentioned in the hacking guide to make sure we can account for the CLA (contributor license agreement) for cloud-init

-

17:39 <blackboxsw> #link https://cloudinit.readthedocs.io/en/latest/topics/hacking.html

-

17:40 <blackboxsw> #topic Community Charter

-

17:40 <blackboxsw> reminder on 19.4 release covered above, and getting your github account authorized for cloud-init conributions....

-

17:41 <Odd_Bloke> Nothing from me!

-

17:41 <meena> goneri and i have been working on / testing his freebsd render

-

17:42 <blackboxsw> for folks with time to burn and bite-sized branches/fixes. we've got a lane on our trello board that gives a variety of fixes that the community can grab if they are looking for quick suggestions. "Community low-hanging fruit"

-

17:42 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

17:42 <blackboxsw> meena: Goneri yes and thanks for the continued efforts there. A lot of good is coming out for cloud-init upstream as a result.

-

17:42 <meena> Goneri removed a lot of code, but from what i gather, that code is still used elsewhere

-

17:43 <meena> could someone explain why our where our how

-

17:43 <blackboxsw> as always, any community member is encouraged to review other PRs from devs. All reviews and input welcome.

-

17:44 <blackboxsw> meena: I'm not sure I follow, are you referring to a specific branch?

-

17:44 <blackboxsw> or just where stale snapshots or cloud-init code lives on certain distros?

-

17:45 <blackboxsw> #topic Office Hours (next ~30 mins)

-

17:45 <blackboxsw> might as well kick the topic and open office hours for general cloud-init discussions, questions, bug/feature work etc.

-

17:46 <blackboxsw> some upstream devs will have eyes/time available for discussion around anything cloud-init. This time will also be spent grooming the active review queue @ https://git.io/JeVed

-

17:46 <blackboxsw> #link https://git.io/JeVed

-

17:48 <meena> blackboxsw: https://github.com/canonical/cloud-init/pull/61#pullrequestreview-329139891

-

17:48 <blackboxsw> checking

-

17:52 <blackboxsw> meena: so Distro._bring_up_interface() is called by Distro._bring_up_interfaces() base class via Distro.apply_network

-

17:59 <blackboxsw> which is called from Init.apply_network_config which gets run during "cloud-init init" when network is brought up

-

18:06 <blackboxsw> I think https://github.com/canonical/cloud-init/pull/42 looks ready to merge. rharper has an outstanding "changes requested" but I believe those have been fixed. rharper I'll defer to you on this one

-

18:08 <blackboxsw> and policy question on reviews: if we get one upstream core-dev +1 can we proceed to land the branch as long as the "changes requested" from other upstream core seem to be resolved?

-

18:09 <blackboxsw> I'd vote that most recent core-dev on the PR that +1's can squash merge if they see that any prior core-dev's concerns seem to be addressed

-

18:12 <blackboxsw> I think I'll add an action for next meeting to make sure we iron out review/merge policy so PRs don't sit stale

-

18:13 <blackboxsw> #action rharper confirm no concerns on https://github.com/canonical/cloud-init/pull/42 and that PR can land.

-

18:13 * meetingology rharper confirm no concerns on https://github.com/canonical/cloud-init/pull/42 and that PR can land.

-

18:14 <blackboxsw> #action upstream core-devs to decide about whether a PR can land if any upstream dev still has 'requested changes'

-

18:14 * meetingology upstream core-devs to decide about whether a PR can land if any upstream dev still has 'requested changes'

-

18:16 <blackboxsw> ok I think that about wraps the meeting. Merry Christmas, Happy Hanukkah, Happy New Year and all that good stuff. See you all online.

-

18:16 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2020-01-07.html b/status-2020-01-07.html deleted file mode 100644 index 249a267..0000000 --- a/status-2020-01-07.html +++ /dev/null @@ -1,368 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Tue 07 January 2020 in status-meeting-minutes - - • 11 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2019-12-10.html#status-2019-12-10

-

Previous Actions

-

The discussion about "Previous Actions" started at 17:36.

- -

Recent Changes

-

The discussion about "Recent Changes" started at 17:39.

- -

In-progress Development

-

The discussion about "In-progress Development" started at 17:44.

- -

Community Charter

-

The discussion about "Community Charter" started at 17:51.

- -

Office Hours (next ~30 mins)

-

The discussion about "Office Hours (next ~30 mins)" started at 18:02.

-

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (118)
  • -
  • robjo (16)
  • -
  • ubot5 (13)
  • -
  • Odd_Bloke (11)
  • -
  • meetingology (6)
  • -
  • smoser (5)
  • -
  • rharper (0)
  • -
-

Full Log

-

17:30 <blackboxsw> #startmeeting Cloud-init bi-weekly status

-

17:30 <meetingology> Meeting started Tue Jan 7 17:30:28 2020 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

17:30 <meetingology>

-

17:30 <meetingology> Available commands: action commands idea info link nick

-

17:30 <blackboxsw> #chair Odd_Bloke

-

17:30 <meetingology> Current chairs: Odd_Bloke blackboxsw

-

17:30 <blackboxsw> #chair rharper

-

17:30 <meetingology> Current chairs: Odd_Bloke blackboxsw rharper

-

17:31 <blackboxsw> Welcome to the first cloud-init community status meeting of 2020. 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.

-

17:31 <Odd_Bloke> usrdev: I'm not 100% sure from that description, could you file a bug using the link in the topic and attach the output of cloud-init collect-logs on an affected instance?

-

17:31 <blackboxsw> We generally have this meeting ever 2 weeks (outside of intermittent holidays)... You can always find the next scheduled meeting in the topic of this channel

-

17:31 <blackboxsw> Let

-

17:31 <blackboxsw> Let

-

17:32 <blackboxsw> Let's schedule the next meeting now as well

-

17:32 <blackboxsw> Any objections to Jan 21 ?

-

17:33 <robjo> Look I'm not late ;)

-

17:33 <blackboxsw> ok topic set for next meeting

-

17:33 <blackboxsw> nope, just me robjo :) welcome to the party

-

17:33 <blackboxsw> as always previous meeting minutes are here.

-

17:33 <blackboxsw> #link https://cloud-init.github.io/status-2019-12-10.html#status-2019-12-10

-

17:34 <blackboxsw> topics for this round: Feel free to interject/suggest other topics at any time. Our typical format is the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Upcoming Meetings, Office Hours (~30 mins).

-

17:34 <robjo> The move to Tuesday creates a conflict for me for the last 15 minutes of the meeting. Generally I don't think that's an issue as we are often done in less than 1 hour, just pointing out that usually I have to leave 15 minutes early

-

17:34 <robjo> not today ;)

-

17:36 <blackboxsw> +1 robjo. We'll try to keep it snappy :) and if others have conflicts we can certainly touch on shifting the schedule a bit. We generally have a conflict at 1 hr before this meeting, which is the only reason it isn't 1 hr earlier

-

17:36 <blackboxsw> #topic Previous Actions

-

17:37 <blackboxsw> last round: rharper to confirm https://github.com/canonical/cloud-init/pull/42 can land. COMPLETED

-

17:37 <blackboxsw> action2: upstream core-devs to decide about whether a PR can land if any upstream dev still has 'requested changes'

-

17:38 <blackboxsw> Odd_Bloke: started writing up a spec/procedure for PR review and he is currently working on adding a documentation addition PR to http://cloudinit.readthedocs.io that will describe the workflow for a PR to get from proposed ->` merged.

-

17:39 <blackboxsw> that PR should likely be up this week for review if folks are watching our review queue

-

17:39 <blackboxsw> #link https://github.com/cloud-init/cloud-init/pulls

-

17:39 <blackboxsw> No other actions from the previous meeting in December.

-

17:39 <blackboxsw> #topic Recent Changes

-

17:40 <blackboxsw> recent commits that made it into tip: found via git log --since 12-10-2019

-

17:41 <blackboxsw> let's see if I get throttled for spam

-

17:41 <blackboxsw> - freebsd: fix create_group() cmd (#146) [Gonéri Le Bouder]

-

17:41 <blackboxsw> - doc: make apt_update example consistent (#154)

-

17:41 <blackboxsw> - doc: add modules page toc with links (#153) (LP: #1852456)

-

17:41 <blackboxsw> - Add support for the amazon variant in cloud.cfg.tmpl (#119)

-

17:41 <blackboxsw> [Frederick Lefebvre]

-

17:41 <ubot5> Launchpad bug 1852456 in cloud-init "doc: list of modules is no longer present" [Medium,Triaged] https://launchpad.net/bugs/1852456

-

17:41 <blackboxsw> heh

-

17:41 <blackboxsw> - freebsd: fix create_group() cmd (#146) [Gonéri Le Bouder]

-

17:41 <blackboxsw> 10:41 - doc: make apt_update example consistent (#154)

-

17:41 <blackboxsw> 10:41 - doc: add modules page toc with links (#153) (LP: #1852456)

-

17:41 <blackboxsw> 10:41 - Add support for the amazon variant in cloud.cfg.tmpl (#119)

-

17:41 <blackboxsw> 10:41 [Frederick Lefebvre]

-

17:41 <blackboxsw> 10:41 - ci: remove Python 2.7 from CI runs (#137)

-

17:41 <blackboxsw> 10:41 - modules: drop cc_snap_config config module (#134)

-

17:41 <blackboxsw> 10:41 - migrate-lp-user-to-github: ensure Launchpad repo exists (#136)

-

17:41 <blackboxsw> 10:41 - docs: add initial troubleshooting to FAQ (#104) [Joshua Powers]

-

17:41 <blackboxsw> 10:41 - doc: update cc_set_hostname frequency and descrip (#109)

-

17:41 <blackboxsw> 10:41 [Joshua Powers] (LP: #1827021)

-

17:41 <ubot5> Launchpad bug 1827021 in cloud-init "SSH Documentation should mention "Host Key"" [Medium,Triaged] https://launchpad.net/bugs/1827021

-

17:41 <blackboxsw> - ci: emit names of tests run in Travis (#120)

-

17:41 <blackboxsw> 10:41 - Release 19.4 (LP: #1856761)

-

17:41 <ubot5> Launchpad bug 1856761 in cloud-init "Release 19.4" [Undecided,Fix released] https://launchpad.net/bugs/1856761

-

17:41 <blackboxsw> 10:41 - rbxcloud: fix dsname in RbxCloud [Adam Dobrawy] (LP: #1855196)

-

17:41 <blackboxsw> 10:41 - tests: Add tests for value of dsname in datasources [Adam Dobrawy]

-

17:41 <blackboxsw> 10:41 - apport: Add RbxCloud ds [Adam Dobrawy]

-

17:41 <blackboxsw> 10:41 - docs: Updating index of datasources [Adam Dobrawy]

-

17:41 <ubot5> Launchpad bug 1855196 in cloud-init "RBXCloud has no dsname defined, so datasource cannot be properly detected." [Low,Triaged] https://launchpad.net/bugs/1855196

-

17:41 <blackboxsw> 10:41 - docs: Fix anchor of datasource_rbx [Adam Dobrawy]

-

17:41 <blackboxsw> 10:41 - settings: Add RbxCloud [Adam Dobrawy]

-

17:41 <blackboxsw> 10:41 - doc: specify _ over - in cloud config modules

-

17:41 <blackboxsw> 10:41 [Joshua Powers] (LP: #1293254)

-

17:41 <ubot5> Launchpad bug 1293254 in cloud-init "style guide on dashes vs underscores in cloud-init" [Low,Fix released] https://launchpad.net/bugs/1293254

-

17:42 <blackboxsw> - tools: Detect python to use via env in migrate-lp-user-to-github

-

17:42 <blackboxsw> [Adam Dobrawy]

-

17:42 <blackboxsw> - Partially revert "fix unlocking method on FreeBSD" (#116)

-

17:42 <blackboxsw> - tests: mock uid when running as root (#113)

-

17:42 <blackboxsw> [Joshua Powers] (LP: #1856096)

-

17:42 <blackboxsw> - cloudinit/netinfo: remove unused getgateway (#111)

-

17:42 <blackboxsw> - docs: clear up apt config sections (#107) [Joshua Powers] (LP: #1832823)

-

17:42 <ubot5> Launchpad bug 1856096 in cloud-init "unittest failure when running tests as root: no such file or dir: 'ud'" [High,Fix released] https://launchpad.net/bugs/1856096

-

17:42 <blackboxsw> - doc: add kernel command line option to user data (#105)

-

17:42 <blackboxsw> [Joshua Powers] (LP: #1846524)

-

17:42 <ubot5> Launchpad bug 1832823 in cloud-init "docs: confusing heading "Add apt repositories"" [Low,Fix released] https://launchpad.net/bugs/1832823

-

17:42 <ubot5> Launchpad bug 1846524 in cloud-init "docs: cloud-init user-data docs should mention kernel cmdline options" [Wishlist,Fix released] https://launchpad.net/bugs/1846524

-

17:42 <blackboxsw> - config/cloud.cfg.d: update README [Joshua Powers] (LP: #1855006)

-

17:42 <blackboxsw> - azure: avoid re-running cloud-init when instance-id is byte-swapped

-

17:42 <blackboxsw> (#84) [AOhassan]

-

17:42 <blackboxsw> - fix unlocking method on FreeBSD [Igor Galić] (LP: #1854594)

-

17:42 <blackboxsw> - debian: add reference to the manpages [Joshua Powers]

-

17:42 <blackboxsw> - ds_identify: if /sys is not available use dmidecode (#42)

-

17:42 <blackboxsw> [Igor Galić] (LP: #1852442)

-

17:42 <ubot5> Launchpad bug 1855006 in cloud-init "config/cloud.cfg.d/README says "All files" rather than "*.cfg"" [Low,Fix released] https://launchpad.net/bugs/1855006

-

17:42 <blackboxsw> - docs: add cloud-id manpage [Joshua Powers]

-

17:42 <blackboxsw> - docs: add cloud-init-per manpage [Joshua Powers]

-

17:42 <ubot5> Launchpad bug 1854594 in cloud-init "lock passwd implemented wrong on FreeBSD" [Medium,Fix released] https://launchpad.net/bugs/1854594

-

17:42 <blackboxsw> - docs: add cloud-init manpage [Joshua Powers]

-

17:42 <blackboxsw> - docs: add additional details to per-instance/once [Joshua Powers]

-

17:42 <blackboxsw> - Merge pull request #96 from fred-lefebvre/master [Joshua Powers]

-

17:42 <blackboxsw> - Update doc-requirements.txt [Joshua Powers]

-

17:42 <ubot5> Launchpad bug 1852442 in cloud-init "ds-identify uses the /sys filesystem which is linux specific and non-portable" [Undecided,Fix released] https://launchpad.net/bugs/1852442

-

17:42 <blackboxsw> - doc-requirements: add missing dep [Joshua Powers]

-

17:42 <blackboxsw> Ok that should do it.

-

17:42 <blackboxsw> maybe best to just pastebin next time

-

17:43 <robjo> yup

-

17:43 <blackboxsw> lots of doc changes as you can see. dropping python 2.7 automatic testing

-

17:44 <blackboxsw> some additional FreeBSD enablement work landed too (thanks Goneri && meena )

-

17:44 <blackboxsw> total changelog since last meeting:

-

17:44 <blackboxsw> #link https://paste.ubuntu.com/p/Cwnn3SbmWQ/

-

17:44 <blackboxsw> much better

-

17:44 <blackboxsw> #topic In-progress Development

-

17:45 <blackboxsw> We've dusted off our shoes and will get back into using our Trello board more frequently for the immediate updates for what we are currently working.

-

17:45 <blackboxsw> New Year's resolution and all

-

17:45 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin

-

17:46 <blackboxsw> expect to see more cloud-init cards migrating through the lanes of the board. Expectation as well is that we'll drop the backlog and ideas lanes and keep the board a simple kanban of what is in progress, review and done

-

17:47 <blackboxsw> Also note I'm going to drop the community charter lane and create bugs for each item, tagging them 'bitesize' so that quick drivebys of developers that want to contribute can search bugs for those straightforward tasks

-

17:47 <blackboxsw> that said, some high level goals upstream is working:

-

17:48 <blackboxsw> - cloud-init one-shot daemon work

-

17:48 <blackboxsw> - cloud-init network hotplug handling

-

17:48 <blackboxsw> - boot performance improvements

-

17:49 <blackboxsw> - github automation and tooling improvements for expedited reviews and process

-

17:50 <blackboxsw> I think that plus reviewing the PR active review queues will keep folks busy for the next 2 weeks :)

-

17:51 <blackboxsw> we will likely be adding a cloud-init SRU into xenial, bionic, disco, eoan into the mix as well

-

17:51 <blackboxsw> #topic Community Charter

-

17:52 <blackboxsw> So generally I'd be pointing to the trello lane "Community low hanging fruit" but I hope to convert those cards to bugs today. So let's say community ongoing efforts fall into two camps"

-

17:53 <blackboxsw> 1. add json schema validation to missing cloudinit/config/cc_*py modules. ( I think there are about 45 remaining modules that need json schema for syntax validation)

-

17:53 <blackboxsw> 2. doc scrub and update for datasources in read the docs

-

17:54 <blackboxsw> All of these items can easily be worked in parallel, which is why they are a good set of tasks for the greater community

-

17:55 <blackboxsw> Expect to find them by searching cloud-init bugs for bitesize tag

-

17:55 <robjo> With bugs remaining in launchpad, would it be a good idea to have things like the schema validation not as bugs but issues in GitHub?

-

17:55 <robjo> that would make them more visible IMHO

-

17:55 <robjo> and those are not really bugs nor is it pressing

-

17:56 <blackboxsw> #link https://bugs.launchpad.net/cloud-init/?field.tag=bitesize

-

17:57 <blackboxsw> robjo: good suggestion. I think we were trying to avoid the confusion of having two places for bugs (launchpad bugs and github issues) That is a good point though, and maybe it's worth a mailing list discussion to get others to weight in.

-

17:58 <Odd_Bloke> I would be -1 on enabling issues, we would spend our entire lives telling people to report in Launchpad instead.

-

17:59 <Odd_Bloke> I totally understand wanting to separate "bugs" and "development tasks", though.

-

18:00 <Odd_Bloke> But I don't think we have a great way of doing that which doesn't end up with a confusing experience for bug reporters.

-

18:00 <robjo> True that people will equate issues in GitHub with bugs and thus file problems there rather than launchpad, it's a two edged sword

-

18:00 <blackboxsw> right, I think designation is there. We could also add a link to community charter bugs to the top-level README.md for the github project. Just so there is a close breadcrumb in github to get to those items

-

18:01 <Odd_Bloke> Our plan is to assess how this is working in a month or two, so if it's not working well then we can figure something else out.

-

18:01 <blackboxsw> I think the designation of "community development tasks" is there by using bitesize tag or some equivalent

-

18:02 <blackboxsw> #ACTION bbsw seed initial community charter bitesize bugs

-

18:02 * meetingology bbsw seed initial community charter bitesize bugs

-

18:02 <blackboxsw> #topic Office Hours (next ~30 mins)

-

18:02 <robjo> Well, "community development tasks" is a bit mis-leading, after all the core team should be part of the "community" right?

-

18:03 <robjo> So everything is really a "community development tasks", just that some things are easier than others ;)

-

18:03 <blackboxsw> robjo: yes absolutely. right... I've seen some projects use 'goodfirstbug' or something like that too

-

18:04 <blackboxsw> just something to reduce the barrier to involvement for anyone wanting to contribute

-

18:05 <blackboxsw> and yes, core team should be accountable to work on some of those community charter tasks when time permits

-

18:05 <robjo> Yes, I think it is important to label the "easy" stuff to help people find a place to get started

-

18:05 <blackboxsw> so that hopefully next cloud-init summit we can set a charter for something else

-

18:06 <robjo> just based on experience there are a lot of people that are sensitive to wording and we don't really want to get into the bikeshedding that comes along with such situations

-

18:07 <blackboxsw> for those reading, office hours is a time of open and unstructured discussion. core cloud-init devs will have eyes on the channel to field questions, concerns, feature or bug discussions. Participate at will. In the absence of any ongoing discussions, upstream will groom/review the active review queue @ https://git.io/JeVed |

-

18:09 <Odd_Bloke> Honestly losing my mind over this bug: https://bugs.launchpad.net/cloud-init/+bug/1858615

-

18:09 <ubot5> Ubuntu bug 1858615 in cloud-init "Fail to boot when NoCloud datasource is included" [Undecided,New]

-

18:09 <Odd_Bloke> The board reboots if you use dmidecode!

-

18:10 <Odd_Bloke> smoser: As you said, that's a regression. Do you think it follows that the fix should be in cloud-init?

-

18:10 <Odd_Bloke> Because I don't know how you deal with something that broken from where we are in the stack. :/

-

18:10 <Odd_Bloke> (Unless we think this is enough evidence that we can't reliably use dmidecode on aarch64, then I guess it is on us to stop doing that. :( )

-

18:10 <robjo> This was probably in the e-mail by rharper I have not yet read, but I'll ask anyway ;)

-

18:11 <robjo> I think I had some pending merge proposals in launchpad and patches, did these "magically" make their way into GitHub? DO I need to sort out where hings were?

-

18:11 <smoser> i've heard "board reboots if you use dmidecode" before.

-

18:12 <smoser> and maybe even cloud-init skipped calling dmidecode on aarch64 to avoid that.

-

18:12 <smoser> but that is sheer non-sense

-

18:12 <Odd_Bloke> Very glad that boards like this are going to be in the walls of every building in 5 years. ;)

-

18:12 <smoser> umm..... fix your hardware ?

-

18:13 <blackboxsw> other dmidecode issues on other hardware here too https://bugs.launchpad.net/qemu/+bug/1243287

-

18:13 <ubot5> Ubuntu bug 1243287 in QEMU "[KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail" [Undecided,Fix released]

-

18:13 <smoser> its more forgivable because dmidecode is priviledged but i swear that all it does is read /dev/mem

-

18:16 <blackboxsw> robjo: for your pending merge proposals we'd like to see you propose against github if possible. Looking for a run of ./tools/migrate-lp-user-to-github robjo <your_GITHUB_USERNAME> to get your github user included as a CLA signer

-

18:17 <blackboxsw> then we have Conributor License Agreement accountability and can start merging those branches on the github side

-

18:17 <robjo> Yesh I haven't migrated to the GitHub repo.... even in 2020 the 24 hour/day limitation remains, darn it ;)

-

18:17 <robjo> I'll get at least my migration to GitHub done this week, possibly even this afternoon

-

18:18 <blackboxsw> heh, absolutely, and actually I mistyped your migrate cmd: ./tools/migrate-lp-user-to-github rjschwei <YOUR_GITHUB_USERNAME>

-

18:39 <blackboxsw> ok think that about wraps the meeting for today. Happy new year folks! Thanks for dropping in!

-

18:39 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2020-01-21.html b/status-2020-01-21.html deleted file mode 100644 index 266c094..0000000 --- a/status-2020-01-21.html +++ /dev/null @@ -1,259 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Tue 21 January 2020 in status-meeting-minutes - - • 5 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Previous Actions

-

The discussion about "Previous Actions" started at 17:50.

-
    -
  • LINK: bugs.launchpad.net/cloud-init/+bugs?field.tag=bitesize
  • -
-

Recent Changes

-

The discussion about "Recent Changes" started at 17:53.

-

In-progress Development

-

The discussion about "In-progress Development" started at 17:57.

-

Community Charter

-

The discussion about "Community Charter" started at 18:02.

- -

Office Hours (next ~30 mins)

-

The discussion about "Office Hours (next ~30 mins)" started at 18:08.

- -

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (58)
  • -
  • tribaal (3)
  • -
  • ubot5 (3)
  • -
  • meetingology (3)
  • -
-

Full Log

-

17:42 <blackboxsw> #startmeeting Cloud-init bi-weekly status

-

17:42 <meetingology> Meeting started Tue Jan 21 17:42:43 2020 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

17:42 <meetingology>

-

17:42 <meetingology> Available commands: action commands idea info link nick

-

17:43 <blackboxsw> At long last, and a bit late. Time for a brief cloud-init status meeting

-

17:43 <blackboxsw> Coud-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.

-

17:44 <blackboxsw> You can always find the next date and time of the cloud-init status meeting in the topic of this channel.

-

17:45 <blackboxsw> it also serves as a reminder to me that we need to start it as I find it's easy to forget the appointment if it isn't staring us in the face.

-

17:46 <blackboxsw> Let's set next meeting now

-

17:48 <blackboxsw> our previous meeting minutes are recorded on our github site

-

17:49 <blackboxsw> #link https://cloud-init.github.io/

-

17:49 <blackboxsw> the topics we cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Upcoming Meetings, Office Hours (~30 mins).

-

17:50 <blackboxsw> #topic Previous Actions

-

17:50 <blackboxsw> Previous #ACTION bbsw seed initial community charter bitesize bugs ... DONE.

-

17:51 <blackboxsw> 'bitesize' bugs for cloud-init can be found at the following link

-

17:51 <blackboxsw> #link bugs.launchpad.net/cloud-init/+bugs?field.tag=bitesize

-

17:52 <blackboxsw> These bugs should be easy to work in parallel as well as self-contained bits of work that any member of the community could approach as a small chunk of work

-

17:53 <blackboxsw> we moved from using trello board for tracking these tasks to using launchpad bugs as it eases the ability to search and grab ownership of the specific features/bugs

-

17:53 <blackboxsw> #topic Recent Changes

-

17:55 <blackboxsw> The following commits landed in tip of master: (found by git log --since 01/07/2020)

-

17:55 <blackboxsw> - Add Rootbox & HyperOne to list of cloud in README (#176) [Adam Dobrawy]

-

17:55 <blackboxsw> - docs: add proposed SRU testing procedure (#167)

-

17:55 <blackboxsw> - util: rename get_architecture to get_dpkg_architecture (#173)

-

17:55 <blackboxsw> - Ensure util.get_architecture() runs only once (#172)

-

17:55 <blackboxsw> - Only use gpart if it is the BSD gpart (#131) [Conrad Hoffmann]

-

17:55 <blackboxsw> - freebsd: remove superflu exception mapping (#166) [Gonéri Le Bouder]

-

17:55 <blackboxsw> - ssh_auth_key_fingerprints_disable test: fix capitalization (#165)

-

17:55 <blackboxsw> [Paride Legovini]

-

17:55 <blackboxsw> - util: move uptime's else branch into its own boottime function (#53)

-

17:55 <blackboxsw> [Igor Galić] (LP: #1853160)

-

17:55 <blackboxsw> - workflows: add contributor license agreement checker (#155)

-

17:55 <blackboxsw> - net: fix rendering of 'static6' in network config (#77) (LP: #1850988)

-

17:55 <blackboxsw> - Make tests work with Python 3.8 (#139) [Conrad Hoffmann]

-

17:55 <blackboxsw> - fixed minor bug with mkswap in cc_disk_setup.py (#143) [andreaf74]

-

17:55 <ubot5> Launchpad bug 1853160 in cloud-init "uptime code does not work on FreeBSD with python 3" [Medium,Fix committed] https://launchpad.net/bugs/1853160

-

17:55 <ubot5> Launchpad bug 1850988 in cloud-init "[Cloud-init 18.5][CentOS 7 on vSphere] Crash when configuring static dual-stack (IPv4 + IPv6) networking" [Medium,Fix committed] https://launchpad.net/bugs/1850988

-

17:56 <blackboxsw> Thanks Adam, Conrad, andreaf74, Gonéri and meena for improving cloud-init.

-

17:57 <blackboxsw> #topic In-progress Development

-

17:58 <blackboxsw> FreeBSD, NetBSD improvements are under heavy development, thanks meena and Goneri for all the PRs put of in that regard.

-

17:58 <blackboxsw> Also robjo has started work on cleanup of sysconfig net rendering per https://github.com/canonical/cloud-init/pull/162 and a mailing list discussion

-

17:59 <blackboxsw> rharper is also midstream on "cloud-init run as a daemon" mode https://github.com/canonical/cloud-init/pull/48 which should improve cloud-init startup times by avoiding having to reload python 4 times for each cloud-init stage

-

18:00 <blackboxsw> Also in progress, upstream has started to SRU testing for cloud-init 19.4.33 into Ubuntu Xenial, Bionic and Eoan.

-

18:01 <blackboxsw> We expect to wrap up that testing this week for a publish of cloud-init 19.4.33 to those series

-

18:02 <blackboxsw> #topic Community Charter

-

18:02 <blackboxsw> As a note, any community member is welcome to participate in SRU testing of cloud-init if those changesets in the SRU affect your cloud platform or features.

-

18:02 <blackboxsw> We have added a guide for SRU testing on Ubuntu here

-

18:03 <tribaal> duly noted :)

-

18:03 <blackboxsw> #link https://cloudinit.readthedocs.io/en/latest/topics/debugging.html#manual-sru-verification-procedure

-

18:03 <blackboxsw> :)

-

18:04 <blackboxsw> ahh tribaal we should pull in your PR for manual testing of Exoscale too if you think it's ready https://github.com/cloud-init/ubuntu-sru/pull/64

-

18:04 <tribaal> it's not unfortunately :/

-

18:05 <blackboxsw> ahh, ok good, thought it was waiting on review

-

18:05 <blackboxsw> ok can table that for another SRU (which will be around Feb 14th likely)

-

18:06 <tribaal> no worries, happy to help test the current one anyway

-

18:06 <blackboxsw> community notice: we are targeting Feb 18th as our cutoff for upstream cloud-init version 20.1 (which will be SRU'd to Ubuntu Xenial, bionic and Eoan). If there are features of bug fixes that you'd like to get into cloud-init 20.1 please raise them as PRs or discussion on the mailinglist or in channel

-

18:08 <blackboxsw> #topic Office Hours (next ~30 mins)

-

18:08 <blackboxsw> This time is spent on any cloud-init feature/bug/branch discussions. quetions or concerns and topics are welcome. In the absence of topics we'll groom the review queue.

-

18:09 <blackboxsw> I'm wrapping up some significant change suggestions the networking stuff for sysconfig on https://github.com/canonical/cloud-init/pull/162

-

18:10 <blackboxsw> I should have that review done in about an hour

-

18:10 <blackboxsw> I've added myself as the "assignee" to that PR to indicate it as priority for me

-

18:11 <blackboxsw> also, note in SRU testing I've run into a repeated issue with cloud-init's ssh-import-id taking 1 minute to import a single ssh pubkey on Azure bionic advanced networking vms. (2 nics + ipv6 + multiple IPs). I'll be debugging this a bit today to make sure it is not a regression for this cloud-init SRU 19.4.33

-

18:12 <blackboxsw> if anyone has any feedback or issues associated with this cloud-init v 19.4.33 SRU, they can comment on the SRU bug or raise a new bug or comment in IRC

-

18:12 <blackboxsw> #link https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1859725

-

18:12 <ubot5> Ubuntu bug 1859725 in cloud-init (Ubuntu) "sru cloud-init (19.3.41 to 19.4.33) Xenial, Bionic and Eoan" [Undecided,New]

-

18:55 <blackboxsw> ok, that about wraps today's status meeting. We'll have the next one February 4th to chat again about getting features ready for 20.1

-

18:55 <blackboxsw> Thanks for tuning in.

-

18:55 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2020-02-04.html b/status-2020-02-04.html deleted file mode 100644 index 5c501da..0000000 --- a/status-2020-02-04.html +++ /dev/null @@ -1,287 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Tue 04 February 2020 in status-meeting-minutes - - • 6 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Previous Actions

-

The discussion about "Previous Actions" started at 17:27.

-

Recent Changes

-

The discussion about "Recent Changes" started at 17:27.

- -

In-progress Development,

-

The discussion about "In-progress Development," started at 17:32.

-

In-progress Development

-

The discussion about "In-progress Development" started at 17:32.

- -

Community Charter

-

The discussion about "Community Charter" started at 17:43.

- -

Office Hours (next ~30 mins)

-

The discussion about "Office Hours (next ~30 mins)" started at 17:47.

-

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (68)
  • -
  • ahosmanMSFT (10)
  • -
  • meetingology (5)
  • -
  • powersj (4)
  • -
  • ubot5 (3)
  • -
  • Odd_Bloke (0)
  • -
  • rharper (0)
  • -
-

Full Log

-

17:23 <blackboxsw> #startmeeting Cloud-init bi-weekly status

-

17:23 <meetingology> Meeting started Tue Feb 4 17:23:28 2020 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

17:23 <meetingology>

-

17:23 <meetingology> Available commands: action commands idea info link nick

-

17:23 <blackboxsw> morning, afternoon and evening folks. Time for another cloud-init community status meeting

-

17:24 <blackboxsw> #chair rharper

-

17:24 <meetingology> Current chairs: blackboxsw rharper

-

17:24 <blackboxsw> #chair Odd_Bloke

-

17:24 <meetingology> Current chairs: Odd_Bloke blackboxsw rharper

-

17:24 <blackboxsw> Coud-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.

-

17:24 <blackboxsw> The next scheduled status meeting is always listed in the topic of this channel, so feel free to drop in on next session if you miss this one

-

17:25 <blackboxsw> while we're at it I'll update for next status meeting.

-

17:26 <blackboxsw> 2 weeks from today, same bat time, same bat channel

-

17:26 <blackboxsw> Our previous meeting minutes line here:

-

17:26 <blackboxsw> #link https://cloud-init.github.io/

-

17:26 <blackboxsw> live here rather

-

17:27 <blackboxsw> the topics we cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Upcoming Meetings, Office Hours (~30 mins).

-

17:27 <blackboxsw> new topics or intejections are always welcome

-

17:27 <blackboxsw> #topic Previous Actions

-

17:27 <blackboxsw> From last meeting we had no unresolved actions so we can jump to the next section

-

17:27 <blackboxsw> #topic Recent Changes

-

17:29 <blackboxsw> found from tip of master with git log --since 01/21/2020

-

17:29 <blackboxsw> - sysconfig: distro-specific config rendering for BOOTPROTO option (#162)

-

17:29 <blackboxsw> [Robert Schweikert] (LP: #1800854)

-

17:29 <blackboxsw> - cloudinit: replace "from six import X" imports (except in util.py) (#183)

-

17:29 <blackboxsw> - run-container: use 'test -n' instead of 'test ! -z' (#202)

-

17:29 <blackboxsw> [Paride Legovini]

-

17:29 <blackboxsw> - net/cmdline: correctly handle static ip= config (#201)

-

17:29 <blackboxsw> [Dimitri John Ledkov] (LP: #1861412)

-

17:29 <ubot5> Launchpad bug 1800854 in cloud-init "BOTOPROTO handling between RHEL/Centos/Fedora and SUSE distros is different" [Medium,Triaged] https://launchpad.net/bugs/1800854

-

17:29 <blackboxsw> - Replace mock library with unittest.mock (#186)

-

17:29 <blackboxsw> - HACKING.rst: update CLA link (#199)

-

17:29 <ubot5> Launchpad bug 1861412 in cloud-init (Ubuntu) "cloud-init crashes with static network configuration" [Undecided,Fix committed] https://launchpad.net/bugs/1861412

-

17:29 <blackboxsw> - Scaleway: Fix DatasourceScaleway to avoid backtrace (#128)

-

17:29 <blackboxsw> [Louis Bouchard]

-

17:29 <blackboxsw> - cloudinit/cmd/devel/net_convert.py: add missing space (#191)

-

17:29 <blackboxsw> - tools/run-container: drop support for python2 (#192) [Paride Legovini]

-

17:29 <blackboxsw> - Print ssh key fingerprints using sha256 hash (#188) (LP: #1860789)

-

17:29 <blackboxsw> - Make the RPM build use Python 3 (#190) [Paride Legovini]

-

17:29 <ubot5> Launchpad bug 1860789 in cloud-init (Ubuntu) "ssh_authkey_fingerprints must use sha256 not md5" [Undecided,Fix committed] https://launchpad.net/bugs/1860789

-

17:29 <powersj> thought we were going to use pastebin :P

-

17:29 <blackboxsw> heh, that is a good point (I wondered if anyone would call me on that)

-

17:30 <blackboxsw> #link https://paste.ubuntu.com/p/3jQdKZVPcM/

-

17:31 <blackboxsw> generally speaking, dropping use of six since our code based is not python3-only, tooling dropping py2, sysconfig rendering flavors for opensuse, doc fixes and read the docs fixups

-

17:32 <blackboxsw> thanks all for the contributions over the last couple weeks

-

17:32 <blackboxsw> #topic In-progress Development,

-

17:32 <blackboxsw> #topic In-progress Development

-

17:32 <blackboxsw> Any existing PRs are up for review at the following url:

-

17:33 <blackboxsw> #link https://github.com/canonical/cloud-init/pulls

-

17:33 <blackboxsw> generally speaking we are in the 'long tail' part of a couple of feature-sets:

-

17:34 <blackboxsw> * we are trying to wrap up tooling for our automated CI, publishing processes and documentation for the shift to github from launchpad

-

17:34 <blackboxsw> * we are in progress on cloud-init handling network hotplug for a couple of datasources

-

17:35 <blackboxsw> * in progress on boot speed improvements for various platforms

-

17:36 <blackboxsw> We also recently validated and released cloud-init v 19.4.33 to Xenial, Bionic and Eoan (1/9/2020)

-

17:38 <ahosmanMSFT> Hi @blackboxsw I'm no longer in the provisioning team, but there's an urgency for the cloud test to be resilient. Have you looked at those issues, I can dedicate as much time as needed to this. If you have time, can we tackle this today?

-

17:38 <blackboxsw> there are also a number of PRs in flight for FreeBSD,NetBSD, OpenSUSE and CentOS that need attention so we can better enable those distros

-

17:38 <ahosmanMSFT> azurecloudtest that is

-

17:39 <blackboxsw> hi ahosmanMSFT I can spend some time on office hours here to peek more at it. my individual runs didn't hit the timeouts again, so we might need a reproducer cmdline from you in a new bug maybe?

-

17:39 <ahosmanMSFT> So your able to run all tests successfully without timeout and image not building>`

-

17:40 <blackboxsw> ahosmanMSFT: but yes I can spend a little time on this today. and I think ultimately we'll have to find the tox command line that exhibits this error. I'll go checkout my test run again and see. I don't think I saw the failure. but I might be invoking tests differently than you

-

17:41 <ahosmanMSFT> blackboxsw: hmm that's interesting, thanks let me know

-

17:41 <blackboxsw> same here ahosmanMSFT, can you file a bug with the traceback you see and the tox cmdline you are running?

-

17:41 <blackboxsw> then I know exactly what to look for

-

17:42 <ahosmanMSFT> Sure, will do now

-

17:43 <blackboxsw> cool.

-

17:43 <blackboxsw> ok next topic

-

17:43 <blackboxsw> #topic Community Charter

-

17:43 <blackboxsw> ok this section is reserved to raise general community work/goals.

-

17:44 <blackboxsw> At last cloud-init summit we raised a couple of general themes of improvements cloud-init would like to achieve

-

17:45 <blackboxsw> These themes fell into two categories for this year: datasource documentation updates and cloud-init json schema validation for the 50+ config modules in cloudinit/config/cc_*py so that we can better raise user-config errors and remove some of cloud-init's "sharp edges"

-

17:45 <blackboxsw> we converted a number of these feature requests in into bugs which can be searched here:

-

17:46 <blackboxsw> #link https://bugs.launchpad.net/cloud-init/+bugs?field.tag=bitesize

-

17:46 <blackboxsw> tasks in this list should be fairly easy one-time bugs for folks with a little time available to help improve cloud-init.

-

17:47 <blackboxsw> we'll revisit this set of bugs/features and the community charter goals near the end of 2020 at the next cloud-init summit

-

17:47 <blackboxsw> #topic Office Hours (next ~30 mins)

-

17:48 <blackboxsw> this time is spent with cloud-init upstream dev eyes on this channel for any cloud-init feature, bug or implementation discussions. In the absence of such discussions, we'll review the active PRs to try to tidy up the review queue and unblock developers

-

17:49 <blackboxsw> for the moment, I'll look over some Azure test timeouts ahosmanMSFT is seeing

-

17:49 <blackboxsw> any other topics, concerns, bugs, questions are welcome and someone should be around to field them

-

17:50 <blackboxsw> ahosmanMSFT: so timeouts running integration tests, you said you are getting them about half the time?

-

18:48 <ahosmanMSFT> blackboxsw: Yes, I tracked it down to platforms/instance._wait_for_system

-

18:49 <ahosmanMSFT> I invoke it after initializing vm in platform/azurecloudtest/instance.start

-

18:49 <ahosmanMSFT> when removed, everything works as expected

-

18:50 <ahosmanMSFT> looks like it's needed for cloud tests so thought I'd leave it to you, since I don't know how ec2/lxd/... rely on

-

18:50 <powersj> ahosmanMSFT, can you file a bug please with the cli example?

-

18:50 <powersj> that would help us triage and make a proper decision on what change to make

-

18:51 <ahosmanMSFT> powersj, yes, was in the middle of that side tracked by meeting. On it now

-

18:51 <powersj> thanks!

-

19:07 <blackboxsw> aaaand, I should probably wrap the meeting for the day.

-

19:08 <blackboxsw> Thanks all for the time and energy you put into improving cloud-init! See you next time, or anytime in between

-

19:08 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2020-02-18.html b/status-2020-02-18.html deleted file mode 100644 index 2917687..0000000 --- a/status-2020-02-18.html +++ /dev/null @@ -1,252 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Tue 18 February 2020 in status-meeting-minutes - - • 5 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-02-04.html#status-2020-02-04

-

Previous Actions

-

The discussion about "Previous Actions" started at 17:37.

-

Recent Changes

-

The discussion about "Recent Changes" started at 17:38.

- -

In-prgoress Development

-

The discussion about "In-prgoress Development" started at 17:45.

-

In-progress Development

-

The discussion about "In-progress Development" started at 17:45.

-

cloud-init upstream 20.1

-

The discussion about "cloud-init upstream 20.1" started at 17:49.

-

Community Charter

-

The discussion about "Community Charter" started at 17:59.

- -

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (52)
  • -
  • meetingology (5)
  • -
  • Odd_Bloke (3)
  • -
  • smoser (0)
  • -
  • rharper (0)
  • -
-

Full Log

-

17:35 <blackboxsw> #startmeeting Cloud-init bi-weekly status

-

17:35 <meetingology> Meeting started Tue Feb 18 17:35:26 2020 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

17:35 <meetingology>

-

17:35 <meetingology> Available commands: action commands idea info link nick

-

17:35 <blackboxsw> o/ hi cloud-init folks. sorry I botched being able to read calendars last time.

-

17:36 <blackboxsw> let's kick off our cloud-init status meeting.

-

17:36 <blackboxsw> notes from previous meeting are here:

-

17:36 <blackboxsw> #link https://cloud-init.github.io/status-2020-02-04.html#status-2020-02-04

-

17:37 <blackboxsw> the topics we cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Upcoming Meetings, Office Hours (~30 mins).

-

17:37 <blackboxsw> today I'll add a topic for cloud-init's upstream release 20.1

-

17:37 <blackboxsw> #topic Previous Actions

-

17:38 <blackboxsw> Last meeting minutes show no carryover action items. So we can drop into recent changes

-

17:38 <blackboxsw> #topic Recent Changes

-

17:40 <blackboxsw> We have about 8 commits landed in master since last meeting: found with git log --since 02-04-2020

-

17:40 <blackboxsw> https://paste.ubuntu.com/p/28Y8jGTGwr/

-

17:41 <blackboxsw> some doc fixes, CI fixes for Azure integration testing , swap disk support for cc_disk_setup and freebsd improvements.

-

17:42 <blackboxsw> thanks for contributions there all. I think we still have a long tail of improvements to review for FreeBSD and NetBSD so we'll try to keep the conversation going there.. Thanks meena and do3meli there

-

17:42 <blackboxsw> I mean Goneri

-

17:44 <blackboxsw> #chair rharper Odd_Bloke smoser

-

17:44 <meetingology> Warning: Nick not in channel: rharper

-

17:44 <meetingology> Current chairs: Odd_Bloke blackboxsw rharper smoser

-

17:44 <blackboxsw> forgot to set meeting chairs. sry

-

17:45 <blackboxsw> #topic In-prgoress Development

-

17:45 <blackboxsw> #topic In-progress Development

-

17:47 <blackboxsw> Odd_Bloke: is currently wrapping up any remaining py2/p3-isms in master branch. Dropping use of 'six' throughout the code. Paride is working on copr-build failures due to the shift to python3 packages. otubo, thanks for the ping back on finding various python3 CentOS packages. We'll also try sorting this this week so cloud-init py3 builds can work on CentOS 7 and 8

-

17:47 <blackboxsw> If folks didn't see the mailing list Odd_Bloke has a branch up to shift from nosetests ->` pytest https://lists.launchpad.net/cloud-init/msg00245.html

-

17:48 <blackboxsw> we expect to land that after 20.1 releases. Thanks for the reviews there https://github.com/canonical/cloud-init/pull/211

-

17:49 <blackboxsw> #topic cloud-init upstream 20.1

-

17:50 <blackboxsw> So, today at EOD is upstream release day for cloud-init 20.1. Just another timed release of cloud-init which we strive to make quarterly thoughout the year

-

17:50 <blackboxsw> As mentioned on the mailing list, if there are any branches/PRs that folks really would like to get into 20.1, please raise them here. We will scrub the review queue today and see what makes sense to land for this release.

-

17:52 <Odd_Bloke> I'll be driving the 20.1 release.

-

17:53 <Odd_Bloke> We just landed https://github.com/canonical/cloud-init/pull/204 into master, which is a fix for a (low priority) CVE that we wanted in before cutting the release.

-

17:54 <Odd_Bloke> I'm going to perform some testing of that change before cutting the release, to determine if any doc changes are required for it and to check if it impacts boot on Azure instances that have a password provided by the Azure fabric.

-

17:54 <blackboxsw> I was just looking over the PR from fred in ec2 land about handling a disabled path for IMDSv2 that looks interesting, but it still needs unit tests https://github.com/canonical/cloud-init/pull/216/files

-

17:55 <blackboxsw> this would certainly help non-ec2 lookalikes

-

17:55 <blackboxsw> and is a fairly specific fix.

-

17:56 <blackboxsw> we can peek over it during the office hours and see if it makes sense.

-

17:56 <blackboxsw> Thanks Odd_Bloke for driving the 20.1 release.

-

17:56 <blackboxsw> So, again, plan is to cut 20.1 at end of day today.

-

17:58 <blackboxsw> What follows will be a tag and release to Ubuntu Focal to sync tip of master to Ubuntu development release

-

17:59 <blackboxsw> #topic Community Charter

-

17:59 <blackboxsw> This topic is a placeholder to remind folks of any project-wide development tasks that we are engaging the community in.

-

18:00 <blackboxsw> the general theme at the moment is cloud-config schema definitions for the config modules in cloudinit/config/cc_*py and improving/correct datasource configuration documentation

-

18:00 <blackboxsw> We've queued this work as separate bugs in cloud-init at the following link

-

18:01 <blackboxsw> #link https://bugs.launchpad.net/cloud-init/+bugs?field.tag=bitesize

-

18:01 <blackboxsw> we'll revisit this set of bugs/features and resent community charter goals near the end of 2020 at the next cloud-init summit. If there are suggestions/desires for community themed tasks please feel free to set the direction there.

-

18:02 <blackboxsw> these community tasks are grabbed by any contributor to cloud-init.

-

18:03 <blackboxsw> An example of the schema definitions we are looking to add is the PR in review here. https://github.com/canonical/cloud-init/pull/152

-

18:04 <blackboxsw> As always, everyone's review counts. As a project we are trying to also look to 'promote' more core-contributors, with commit rights to the cloud-init project. Reviews count just much as proposing pull requests to the project.

-

18:04 <blackboxsw> thanks again for all the contributions, reviews and bugs that are being contributed to date. It really helps improve this project's use

-

18:05 <blackboxsw> #topic Office Hours (next ~30 mins)

-

18:07 <blackboxsw> During this topic, please bring up any questions, discussions, bugs or features or paper cuts that need attention. there should be a couple of cloud-init developers with eyes on the channel to actively respond.

-

18:08 <blackboxsw> In leiu of active discussions, we'll hit up the review queue for cloud-init at https://git.io/JeVed and get ready for the 20.1 release

-

18:09 <blackboxsw> I'm going to see if I can

-

18:09 <blackboxsw> review https://github.com/canonical/cloud-init/pull/216/files and propose the unit test changes there

-

18:09 <blackboxsw> I think that could be a valid addition for ec2-lookalikes to avoid an unnecessary 2 minute timeout

-

18:09 <blackboxsw> on boot

-

18:19 <blackboxsw> hrm on 2nd thought w/ 216, I think that patch set should be more specific, such as actually testing HTTP status 403 instead of just checking if metadata was None and assuming it was disabled. I'll put a couple of review comments on that as I dig in, but probably not in a state that it could be landed today

-

18:36 <blackboxsw> thanks for tuning in folks. See you next time

-

18:36 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2020-03-10.html b/status-2020-03-10.html deleted file mode 100644 index 92d44e2..0000000 --- a/status-2020-03-10.html +++ /dev/null @@ -1,340 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Tue 10 March 2020 in status-meeting-minutes - - • 9 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-02-18.html#status-2020-02-18

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:24.

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:25.

- -

In-progress Development

-

The discussion about "In-progress Development" started at 16:37.

- -

Community Charter and upcoming meeting

-

The discussion about "Community Charter and upcoming meeting" started at 16:51.

-

cloud-init pull-requests https://git.io/JeVed | Meeting minutes: https://goo.gl/mrHdaj | Next status meeting March 1 16:15 UTC | 19.4 (Dec 17) drops Py2.7 : origin/stable-19.4 | 20.1 (Feb 18) | https://bugs.launchpad.net/cloud-init/+filebug

-

The discussion about "cloud-init pull-requests https://git.io/JeVed | Meeting minutes: https://goo.gl/mrHdaj | Next status meeting March 1 16:15 UTC | 19.4 (Dec 17) drops Py2.7 : origin/stable-19.4 | 20.1 (Feb 18) | https://bugs.launchpad.net/cloud-init/+filebug" started at 16:53.

- -

Office Hours (next 30 mins)

-

The discussion about "Office Hours (next 30 mins)" started at 16:58.

- -

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (109)
  • -
  • Odd_Bloke (13)
  • -
  • tribaal (5)
  • -
  • meetingology (4)
  • -
  • AnhVoMSFT (2)
  • -
  • Goneri (2)
  • -
  • powersj (1)
  • -
  • smoser (0)
  • -
  • rharper (0)
  • -
-

Full Log

-

16:22 <blackboxsw> #startmeeting Cloud-init bi-weekly status

-

16:22 <meetingology> Meeting started Tue Mar 10 16:22:58 2020 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:22 <meetingology>

-

16:22 <meetingology> Available commands: action commands idea info link nick

-

16:23 <blackboxsw> Hello and welcome to another cloud-init community status meeting.

-

16:23 <blackboxsw> our IRC channel topic carries the next planned status meeting for those that wish to participate.

-

16:23 <blackboxsw> All are welcome and interruptions encouraged

-

16:23 <blackboxsw> #chair rharper Odd_Bloke smoser

-

16:23 <meetingology> Current chairs: Odd_Bloke blackboxsw rharper smoser

-

16:23 <blackboxsw> Previous meeting notes are here

-

16:23 <blackboxsw> #link https://cloud-init.github.io/status-2020-02-18.html#status-2020-02-18

-

16:24 <blackboxsw> he topics we cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Upcoming Meetings, Office Hours (~30 mins).

-

16:24 <blackboxsw> *the even

-

16:24 <Odd_Bloke> o/

-

16:24 <blackboxsw> #topic Previous Actions

-

16:24 <blackboxsw> \O

-

16:24 <blackboxsw> sorry, have my big head on

-

16:24 <tribaal> o/

-

16:25 <blackboxsw> :). Last meeting had no actions carried over. So I think this topic is a noop this week

-

16:25 <blackboxsw> #topic Recent Changes

-

16:26 <blackboxsw> recent changes landed in tip of master via git log --since 2020-02-18 https://paste.ubuntu.com/p/sJVpvjFbPj/

-

16:27 <blackboxsw> we've added some tooling/actions for github, ec2 IMDSv2 token redacting from logs, alloowing kernel cmdline to tell cloud-init network-config=disabled and not falling back to IMDSv1 on Ec2-proper platform

-

16:28 <blackboxsw> thanks fred-lefebvre for the ec2 IMDS fallback branch and others for some additional driveby doc updates

-

16:29 <blackboxsw> Also, we performed an upload to Ubuntu Focal (20.04) series with latest tip of cloud-init to make sure the development release is up to date with recent features

-

16:30 <blackboxsw> Ubuntu Focal release is currently in feature freeze, so that will affect what patches we pull into Ubuntu Focal at this time as 'new features' would need a Feature Freeze Exception during the stage of Ubuntu development.

-

16:30 <blackboxsw> #link https://wiki.ubuntu.com/FocalFossa/ReleaseSchedule

-

16:31 <blackboxsw> As Odd_Bloke alluded to just before this meeting, we are trying to keep tip of master

-

16:31 <blackboxsw> open for commits.

-

16:32 <blackboxsw> On the ubuntu-side of the house we will sort cherry picking bug fixes into ubuntu focal during this short feature freeze period of time

-

16:33 <blackboxsw> If there are significant features that your cloud platform really would like to see on the first public release of Ubuntu Focal, then please get ahold of us in channel of on the mailing list to suggest that we shepherd those features in during this freeze.

-

16:33 <blackboxsw> But, generally cloud-init team will continue to follow the SRU process to get updates into Focal after feature freeze is lifted.

-

16:35 <blackboxsw> and again, our SRU test/verification process for Ubuntu will continue to target Xenial, Bionic, Eoan and Focal series for the updates we plan to make in the near future

-

16:37 <blackboxsw> one thing to note in recent changes as well is that we've now added the ability to query distro, kernel, cpu arch, python runtime version and and merged cloud-config to cloud-config jinja templates. So #cloud-config userdata can be opinionated based on your target distribution or runtime environment.

-

16:37 <blackboxsw> #link https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html#format-of-instance-data-json

-

16:37 <blackboxsw> I think that about wraps recent changes

-

16:37 <blackboxsw> #topic In-progress Development

-

16:38 <blackboxsw> #link https://github.com/canonical/cloud-init/pulls

-

16:38 <blackboxsw> our active pulls above is probably the best source of info on features/bugfixes in flight.

-

16:39 <blackboxsw> Though behind the scenes we have held a couple of meetings to determine how much more automation/tooling we need to clean up to improve our github developer process

-

16:39 <blackboxsw> I think Odd_Bloke and I have around 4 PRs that we are hoping to clean up to get a couple of things in place:

-

16:40 <blackboxsw> foremost I believe Odd_Bloke is scrubbing the github review process PR so that we have a good starting point for expectations for every developer, author or committer.

-

16:42 <blackboxsw> I think ultimately the goal there is to make sure committers can provide a set of expectations on active PR reviews to PR authors, so that active developers get better prioritized reviews.

-

16:42 <blackboxsw> we are going to add and enable a number of github actions and workflows that should do the following:

-

16:43 <blackboxsw> - age PRs and add labelling to indicate to reviewers and authors that a review needs attention or it will be automatically closed (after around 4 weeks of languishing)

-

16:43 <blackboxsw> - label/notify steps to signed the contributor license agreement if unsigned

-

16:44 <blackboxsw> - run addtional integration tests on active PRs in CI

-

16:45 <blackboxsw> not sure if I am I missing anything else there.

-

16:45 <blackboxsw> but ideally we'd like to find a process that helps upstream unblock PRs and get review comments faster

-

16:45 <blackboxsw> so, it'll be an iterative process

-

16:46 <blackboxsw> and thanks for the reviews and suggestions so far on https://github.com/canonical/cloud-init/pull/160 as it is the first cut at trying to document the process

-

16:47 <tribaal> Nice!

-

16:48 <blackboxsw> woot. the hope I believe is to land that this week as well as branches like https://github.com/canonical/cloud-init/pull/164 https://github.com/canonical/cloud-init/pull/236 and https://github.com/canonical/cloud-init/pull/125

-

16:49 <blackboxsw> additionally a gap that we still have vs when we hosted in Launchpad, is our auto-merge Launchpad bug commenting/maintenance:

-

16:49 <blackboxsw> We still have a need for the following:

-

16:49 <blackboxsw> - comment on LP bugs linking to an open github PR

-

16:49 <blackboxsw> - comment on merged commitish in github and Fix Commited state when a PR lands in upstream

-

16:50 <blackboxsw> so we'll be tackling that too in order to make upstream maintainers happier and better advertise fixes to bug filers

-

16:50 <blackboxsw> right now that's all a manual process since we haven't retooled our bug-related tooling

-

16:51 <blackboxsw> #topic Community Charter and upcoming meeting

-

16:52 <blackboxsw> let's set the status meeting for next session

-

16:52 <blackboxsw> oops and I realize only now that I blew it this week due to daylight savings... meeting wasn't 'supposed' to start until 25 mins from now : /

-

16:53 <blackboxsw> #topic cloud-init pull-requests https://git.io/JeVed | Meeting minutes: https://goo.gl/mrHdaj | Next status meeting March 1 16:15 UTC | 19.4 (Dec 17) drops Py2.7 : origin/stable-19.4 | 20.1 (Feb 18) | https://bugs.launchpad.net/cloud-init/+filebug

-

16:53 <blackboxsw> that's better.

-

16:53 <AnhVoMSFT> it says March 1, is that correct?

-

16:54 <tribaal> there :)

-

16:54 <blackboxsw> hah, good I got another participant

-

16:54 <blackboxsw> :)

-

16:54 <AnhVoMSFT> UK will also have their own daylight savings March 29th I believe

-

16:54 <blackboxsw> sorry AnhVoMSFT tribaal :)

-

16:54 <blackboxsw> yeah this time of year always messes with timing. We try to set things in terms of UTC to avoid thrashing

-

16:55 <blackboxsw> but even that fails due to human error (my bad)

-

16:56 <blackboxsw> Other community charter tasks are generally categorized in bugs labelled bitesize

-

16:56 <blackboxsw> #link https://bugs.launchpad.net/cloud-init/+bugs?field.tag=bitesize

-

16:57 <blackboxsw> general topics for this year were tasks that are easily done in parallel, such as json schema addtions and datasource readthe docs updates/corrections and fleshing out.

-

16:57 <blackboxsw> jsonschema example is here for review if anyone wants to take a stab at testing it out. or extending schema for other config modules.https://github.com/canonical/cloud-init/pull/152

-

16:58 <blackboxsw> and again all cloud-init contributors are encouraged to review/comment any active cloud-init PRs @ https://github.com/canonical/cloud-init/pulls the more voices, the better the quality

-

16:58 <blackboxsw> #topic Office Hours (next 30 mins)

-

16:59 <blackboxsw> During this topic, please bring up any questions, discussions, bugs or features or paper cuts that need attention. there should be a couple of cloud-init developers with eyes on the channel to actively respond.

-

17:00 <blackboxsw> just before the start of this meeting Odd_Bloke was asking about getting the pytest branch landed for cloud-init. (moving off of nosetests as the project is EOL/unmaintained)

-

17:00 <tribaal> that's nice. pytest is becoming the de-facto standard these days anyway

-

17:05 <blackboxsw> yeah, didn't want to get stuck using something that becomes unsupported or unsupportable. we don't have the bandwidth in this project to maintain stacks that aren't being looked at by the collective internet ;)

-

17:05 <Odd_Bloke> blackboxsw: I believe that branch is now only blocked on you removing your "Request changes" review now that we've established that we don't need to hold off on landing things for Feature Freeze.

-

17:05 <tribaal> makes total sense :)

-

17:05 <blackboxsw> Odd_Bloke: do you know if rharper did the new-upstream-snapshot into focal already

-

17:05 <blackboxsw> to have a 'clean slate' for the pytest branch landing

-

17:06 <Odd_Bloke> blackboxsw: We can new-upstream-snapshot from an older commit, I don't believe that's a blocker.

-

17:06 <blackboxsw> Odd_Bloke: not a blocker, but I could do that now as it's 5 mins

-

17:07 <blackboxsw> then we can land right aftr

-

17:07 <blackboxsw> sound good? I see nothing queued https://launchpad.net/ubuntu/focal/+queue?queue_state=3&queue_text=cloud-init

-

17:08 <Odd_Bloke> Sure, if you're happier doing that. :)

-

17:09 <blackboxsw> I aam :)

-

17:09 <blackboxsw> ok doing that right now

-

17:09 <blackboxsw> then we can start the cherry picking just after

-

17:10 <blackboxsw> Odd_Bloke: I'm adding this as the debian/changelog section title

-

17:10 <blackboxsw> * New upstream snapshot: bug-fix-only feature-freeze-exception

-

17:11 <blackboxsw> instead of * New upstream snapshot:

-

17:11 <blackboxsw> sound reasonable?

-

17:11 <Odd_Bloke> It isn't bug-fix-only because we have the FFe for a non-bugfix.

-

17:12 <Odd_Bloke> I was just reading the wiki page that suggested wording, I think, let me take a look.

-

17:13 <blackboxsw> https://github.com/canonical/cloud-init/pull/241

-

17:13 <blackboxsw> ahh right, reviewing that now

-

17:13 <blackboxsw> yeah not quite sure how to handle our FFe uploads

-

17:14 <Odd_Bloke> Oh, if it's only that change, then I don't think we need anything specific in the changelog. We have an FFE bug that we're closing with that upload.

-

17:14 * blackboxsw re-reads https://wiki.ubuntu.com/FreezeExceptionProcess

-

17:14 <Odd_Bloke> And that means it's definitely not bug-fix-only, there isn't a single bugfix in there. ;)

-

17:14 <blackboxsw> ok that sounds good, will just keep the New upstream snapshot

-

17:14 <blackboxsw> ok thanks for the review. redoing.

-

17:14 <Odd_Bloke> Hopefully I'm right and you don't get yelled at. :p

-

17:15 <powersj> better to upload and ask for forgiveness...

-

17:15 <blackboxsw> ehh, unlikely :) it seems like steve and others have been pretty lax about changelog text (or manipulating it after the fact) :)

-

17:15 <Odd_Bloke> Cool, I'll do the same thing locally to review.

-

17:16 <blackboxsw> Odd_Bloke: force pushed

-

17:16 <blackboxsw> https://github.com/canonical/cloud-init/pull/241/files

-

17:16 <Odd_Bloke> blackboxsw: Approved.

-

17:17 <blackboxsw> thanks Odd_Bloke

-

17:17 <blackboxsw> build-and-pushing it up

-

17:18 <blackboxsw> ok onto your pytest branch now

-

17:18 <blackboxsw> while I await the ubuntu "accepted" response email

-

17:20 <blackboxsw> Uploading cloud-init_20.1-10-g71af48df-0ubuntu1.dsc: done.

-

17:21 <blackboxsw> just waiting on review/acceptance

-

17:22 <blackboxsw> community-notice: tip of cloud-init published into Ubuntu Focal (20.04) [ubuntu/focal-proposed] cloud-init 20.1-10-g71af48df-0ubuntu1 (Accepted)

-

17:26 <blackboxsw> ok Odd_Bloke merged at long last https://github.com/canonical/cloud-init/pull/211

-

17:26 <blackboxsw> nosetest is dead, long live pytest

-

17:26 <Odd_Bloke> \o/

-

17:27 <Odd_Bloke> blackboxsw: https://github.com/canonical/cloud-init/pull/239 `<-- another small one for you

-

17:29 <blackboxsw> approve Odd_Bloke and thanks. it is waiting on you for merge (and CI completion)

-

17:30 <blackboxsw> works on my focal box

-

17:30 <blackboxsw> which was broken before

-

17:33 <blackboxsw> Odd_Bloke: https://github.com/canonical/cloud-init/pull/164 is ready for you I think (labeling in cron)

-

17:33 <blackboxsw> for CLA ! CLA.

-

17:33 <blackboxsw> or do we want that PR to actually ignore certain paths (like doc changes) as not-requiring CLA

-

17:43 <Goneri> blackboxsw, could you take a look at https://github.com/canonical/cloud-init/pull/62 Pleaaaase :-)

-

17:44 <blackboxsw> Goneri: yes, and so sorry about that.

-

17:44 <Goneri> np, and Yeah! for pytest :-D

-

17:44 <blackboxsw> ... and that about wraps up on our cloud-init status meeting. :) I'll close it out and post the minutes for next time

-

17:45 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2020-03-31.html b/status-2020-03-31.html deleted file mode 100644 index c9a227a..0000000 --- a/status-2020-03-31.html +++ /dev/null @@ -1,238 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Tue 31 March 2020 in status-meeting-minutes - - • 4 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-03-10.html#status-2020-03-10

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:22.

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:23.

- -

In-progress Development

-

The discussion about "In-progress Development" started at 16:32.

-

Community Charter

-

The discussion about "Community Charter" started at 16:42.

- -

Office hours (next ~30 mins)

-

The discussion about "Office hours (next ~30 mins)" started at 16:45.

-

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (38)
  • -
  • meetingology (4)
  • -
  • rharper (2)
  • -
  • Goneri (1)
  • -
  • shibumi (1)
  • -
  • smoser (0)
  • -
  • Odd_Bloke (0)
  • -
-

Full Log

-

16:19 <blackboxsw> #startmeeting cloud-init status meeting

-

16:19 <meetingology> Meeting started Tue Mar 31 16:19:14 2020 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:19 <meetingology>

-

16:19 <meetingology> Available commands: action commands idea info link nick

-

16:19 <blackboxsw> Hello and welcome to another cloud-init community status meeting folks. please feel free to continue any current conversations

-

16:20 <blackboxsw> I'll interleave status meeting notes with existing conversations.

-

16:20 <blackboxsw> #chair Odd_Bloke smoser rharper

-

16:20 <meetingology> Current chairs: Odd_Bloke blackboxsw rharper smoser

-

16:20 <blackboxsw> our IRC channel topic carries the next planned status meeting for those that wish to participate. All are welcome to interject or drive converstation topics here

-

16:21 <blackboxsw> let's set that now. to +2 weeks from now

-

16:21 <blackboxsw> April 14th, same time

-

16:21 <shibumi> rharper: thanks!

-

16:22 <blackboxsw> Previous meeting notes are here

-

16:22 <blackboxsw> #link https://cloud-init.github.io/status-2020-03-10.html#status-2020-03-10

-

16:22 <blackboxsw> The topics we generally cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Upcoming Meetings, Office Hours (~30 mins).

-

16:22 <blackboxsw> #topic Previous Actions

-

16:23 <blackboxsw> and from last meeting, no previous actions were unaccounted for.

-

16:23 <blackboxsw> #topic Recent Changes

-

16:24 <blackboxsw> recent changes landed in tip of master via git log --since 2020-03-10

-

16:24 <blackboxsw> #link https://paste.ubuntu.com/p/55hqVCfnpV/

-

16:24 <rharper> shibumi: also, the issue with openstack metadata service not being found is likely related to classless statci route support in the EphemeralDHCP class in cloud-init, we fixed an issue there last fall, https://github.com/canonical/cloud-init/commit/07b17236be5665bb552c7460102bcd07bf8f2be8

-

16:24 <rharper> shibumi: long term, we would like to replace dhclient with a python-based one; we've just not had a change to implement a minimal dhclient in python only

-

16:27 <blackboxsw> in that paste or recent changes, some big items have landed since last we 'met': both NetBSD and OpenBSD distro support is now added to cloud-init. vmware support of guest info gc status, SAP Converged cloud gets identified as OpenStack and Ubuntu Focal prioritizing netplan over ifupdown if both are present

-

16:28 <blackboxsw> Also Odd_Bloke has been landing and improving cloud-init automated process with near daily branches. github actions/workflows and docs about review and coding style expectations are landing to make it a lot easier for upstream to help speed contributions and reviews

-

16:29 <blackboxsw> Also, you'll note a lot of dropping python six and other py2-related artifacts from our codebase. Since upstream support is py3.4 or later we can simplify and prune a lot of the vestigial py2 functionality.

-

16:31 <blackboxsw> Ahh I also forgot, Ec2 now by default (Ubuntu Focal or tip of cloud-init) renders full networking, including secondary IPv4/IPv6 addresses, for all interfaces attached to a VM based on network config supplied by IMDS. Old releases of cloud-init used to only render basic networking on the primary (eth0) nic.

-

16:32 <blackboxsw> #topic In-progress Development

-

16:33 <blackboxsw> thanks Goneri and meena for all your the BSD ongoing development and support work there BTW

-

16:33 * Goneri waves

-

16:38 <blackboxsw> :) upstream is focused a bit on continuing to clean up py2 remnants from tip, adding support for reading netplan configuration from initramfs and continuing to add automation to the github development and release process/tooling to speed reviews.

-

16:39 <blackboxsw> we are also hammering the review queue a bit better than in the past with daily PR assignments to ensure the system remains more efficient

-

16:40 <blackboxsw> thanks again for all the code submits folks!

-

16:41 <blackboxsw> waiting In the wings we will eventually get around to handling the network hotplug solution for cloud-init (if configured)

-

16:42 <blackboxsw> #topic Community Charter

-

16:43 <blackboxsw> This section is generally reserved to discuss any general community goals for cloud-init. Per last cloud-init summit we discussed prioritizing the following:

-

16:43 <blackboxsw> * json schema validation for each cloudinit/config/cc_*py module

-

16:43 <blackboxsw> * correcting, extending stale datasource documentation under doc/rtd/topics/datasources

-

16:44 <blackboxsw> those tasks are easy to split up and so we set a goal to try to chunk through it this year

-

16:44 <blackboxsw> they are also categorized as bugs for easy pickup/assignment for anyone interested.

-

16:45 <blackboxsw> #link https://bugs.launchpad.net/cloud-init/+bugs?field.tag=bitesize

-

16:45 <blackboxsw> #topic Office hours (next ~30 mins)

-

16:46 <blackboxsw> thanks for listening to the above...... In this section a couple upstream devs should be available with eyes on the channel for the next 30 minutes for and bug, feature, PR review questions or concerns.

-

16:46 <blackboxsw> again thanks for joining. We'll have this meeting again in 2 weeks

-

16:47 <blackboxsw> I'm going to spend this time working on our cherry-pick script for publishing the Netplan ->` ENI work into Ubuntu Focal today.

-

17:17 <blackboxsw> Thanks for tuning in.

-

17:17 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2020-04-14.html b/status-2020-04-14.html deleted file mode 100644 index d852b00..0000000 --- a/status-2020-04-14.html +++ /dev/null @@ -1,239 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Tue 14 April 2020 in status-meeting-minutes - - • 4 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-03-31.html#status-2020-03-31

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:23.

-

In-progress Development

-

The discussion about "In-progress Development" started at 16:27.

-

Office hours (next ~30 mins)

-

The discussion about "Office hours (next ~30 mins)" started at 16:34.

- -

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (38)
  • -
  • meetingology (6)
  • -
  • powersj (2)
  • -
  • Goneri (2)
  • -
  • otubo (1)
  • -
  • punkgeek (1)
  • -
  • rharper (1)
  • -
  • smoser (0)
  • -
  • powers (0)
  • -
  • Odd_Bloke (0)
  • -
-

Full Log

-

16:17 <blackboxsw> #startmeeting cloud-init status meeting

-

16:17 <meetingology> Meeting started Tue Apr 14 16:17:46 2020 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:17 <meetingology>

-

16:17 <meetingology> Available commands: action commands idea info link nick

-

16:18 <blackboxsw> hey folks, time for cloud-init community status meeting

-

16:19 <powersj> \o/

-

16:19 <otubo> Right on time :-)

-

16:20 <blackboxsw> welcome again to our bi-weekly status meeting feel free to interject comments, questions, suggestions during this status meeting. Generally it is an opportunity for upstream to provide a frequent platform communication and drop-in discussion when a couple of upstream devs are available.

-

16:20 <blackboxsw> #chair Odd_Bloke smoser rharper powers

-

16:20 <meetingology> Warning: Nick not in channel: powers

-

16:20 <meetingology> Current chairs: Odd_Bloke blackboxsw powers rharper smoser

-

16:20 <blackboxsw> #chair powersj

-

16:20 <meetingology> Current chairs: Odd_Bloke blackboxsw powers powersj rharper smoser

-

16:20 <blackboxsw> our IRC channel topic carries the next planned status meeting for those that wish to participate. All are welcome to interject or drive converstation topics here

-

16:21 <blackboxsw> any objections to same time on Apr 28th?

-

16:21 <powersj> nah that's a good day given we want to cut 20.2 then

-

16:21 <blackboxsw> ok topic set for next meetin

-

16:22 <blackboxsw> our last meeting minutes can be found on github at

-

16:22 <blackboxsw> #link https://cloud-init.github.io/status-2020-03-31.html#status-2020-03-31

-

16:23 <blackboxsw> The topics we generally cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Upcoming Meetings, Office Hours (~30 mins).

-

16:23 <blackboxsw> #topic Previous Actions

-

16:23 <blackboxsw> none listed from last meeting

-

16:23 <blackboxsw> #topic Recent Changes

-

16:24 <blackboxsw> git commits landed in tip since Mar 31: https://paste.ubuntu.com/p/VptqRBfVfJ/ found by git log --since 03-31-2020

-

16:26 <blackboxsw> changes sport doc updates, otubo's cc_mount fix , better url handling for regions which contain underscores in their name and openbsd fixes from Goneri for passwd locks.

-

16:27 <blackboxsw> thanks for the contributions this round folks!

-

16:27 <blackboxsw> #topic In-progress Development

-

16:30 <blackboxsw> upstream is currently focused on getting in bug fixes, dropping remnants of py2 in tooling reviewing active PRs to get cloud-init in shape for the upcoming 20.2 release

-

16:31 <blackboxsw> community notice: as mentioned in the channel topic, Apr 28th is our upstream release date for 20.2

-

16:31 <blackboxsw> community notice: we ask that pull requests or bugs that need resolution for 20.2 be up for review by Friday April 24th so there is time to review and merge those fixes.

-

16:32 <blackboxsw> active pulls indended for the release should be up in github at https://github.com/canonical/cloud-init/pulls

-

16:32 <blackboxsw> intended rather

-

16:32 <blackboxsw> #topic Community Charter

-

16:33 <blackboxsw> his section is generally reserved to discuss any general community goals for cloud-init, at last cloud-init summit we defined those goals as:

-

16:33 <blackboxsw> - datasource doc fixes

-

16:33 <blackboxsw> - json schema validation for each cloudinit/config/cc_*py modules

-

16:34 <blackboxsw> there are feature bugs created for these tasks at https://bugs.launchpad.net/cloud-init/+bugs?field.tag=bitesize

-

16:34 <blackboxsw> #topic Office hours (next ~30 mins)

-

16:35 <blackboxsw> During office hours a couple of upstream devs will have eyes on this channel. Any questions, comments, branch reviews are fair game for discussion.

-

16:36 <blackboxsw> In leiu of active discussions, developers will be grooming the active pull request review queue to unblock branch authors.

-

16:37 <punkgeek> Odd_Bloke: No it doesn't work. why there is no way to config cloud-init in kvm virtualization rather than iso, like vm xml file?

-

16:37 <blackboxsw> I'm getting through a belated review on https://github.com/canonical/cloud-init/pull/298

-

16:42 <blackboxsw> punkgeek: like seeding ovf-env.xml? https://github.com/canonical/cloud-init/blob/master/doc/sources/ovf/README

-

16:46 <rharper> punkgeek: you might want to look at virt-install , they recently have added support for providing cloud-config to VMs; virt-install is a wrapper around creating VMs utilizing libvirt as a backend, https://athinapl.home.blog/2019/08/25/gsoc-2019-cloud-init-configuration-for-virt-manager-virt-install/

-

16:54 <Goneri> punkgeek, or you can take a look at virt-lightning

-

16:54 <Goneri> punkgeek, it's basically a CLI to use libvirt+cloud-init

-

17:03 <blackboxsw> Goneri: review done. sorry for the delay on such a minor set of change requests https://github.com/canonical/cloud-init/pull/298/files#

-

17:09 <blackboxsw> https://github.com/CanonicalLtd/uss-tableflip/pull/45 I think comments are resolved

-

17:11 <blackboxsw> I think we are at about the turn of the hour for cloud-init status. I'm going to review https://github.com/canonical/cloud-init/pull/305 next

-

17:11 <blackboxsw> thanks all for tuning in. see you next time

-

17:12 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2020-05-05.html b/status-2020-05-05.html deleted file mode 100644 index 6069d66..0000000 --- a/status-2020-05-05.html +++ /dev/null @@ -1,235 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Tue 05 May 2020 in status-meeting-minutes - - • 4 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:20.

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:20.

- -

In-progress Development

-

The discussion about "In-progress Development" started at 16:26.

- -

Community Charter

-

The discussion about "Community Charter" started at 16:30.

- -

Office hours (next ~30 mins)

-

The discussion about "Office hours (next ~30 mins)" started at 16:33.

-

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (38)
  • -
  • meetingology (4)
  • -
  • rharper (0)
  • -
  • Odd_Bloke (0)
  • -
  • smoser (0)
  • -
-

Full Log

-

16:16 <blackboxsw> #startmeeting cloud-init status meeting

-

16:16 <meetingology> Meeting started Tue May 5 16:16:41 2020 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:16 <meetingology>

-

16:16 <meetingology> Available commands: action commands idea info link nick

-

16:17 <blackboxsw> good morning, afternoon and evening folks. Welcome to another cloud-init status meeting.

-

16:17 <blackboxsw> #chair Odd_Bloke smoser rharper

-

16:17 <meetingology> Current chairs: Odd_Bloke blackboxsw rharper smoser

-

16:17 <blackboxsw> our IRC channel topic carries the next planned status meeting for those that wish to participate. All are welcome to interject or drive converstation topics here

-

16:18 <blackboxsw> I'll set the next status meeting topic while we are thinking about it.

-

16:18 <blackboxsw> 2 weeks from today, same time 16:15 UTC.

-

16:18 <blackboxsw> May 19th it is.

-

16:19 <blackboxsw> Previous meeting minutes live over on github

-

16:19 <blackboxsw> #link https://cloud-init.github.io/

-

16:19 <blackboxsw> The topics we generally cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Upcoming Meetings, Office Hours (~30 mins).

-

16:20 <blackboxsw> #topic Previous Actions

-

16:20 <blackboxsw> Looks like no unresolved actions from last meeting

-

16:20 <blackboxsw> #topic Recent Changes

-

16:22 <blackboxsw> Below is a list of commits that have landed in tip of master: found via git log --since 2020-03-10

-

16:22 <blackboxsw> #link https://paste.ubuntu.com/p/YMb2Tw3tRD/

-

16:23 <blackboxsw> We've had a number of milestones since the last status meeting, Ubuntu Focal Fossa 20.04 was released on Apr 23, cloud-init upstream cut a release 20.2 as well

-

16:23 <blackboxsw> Additionally we have two new hires to the canonical ubuntu-server team that will be participating in cloud-init, curtin and ubuntu-advantage-tools projects

-

16:24 <blackboxsw> We are really excited to have some extra hands on cloud-init from lucasmoura and falcojr. So welcome gentlemen, glad to have the help.

-

16:25 <blackboxsw> They just started yesterday and are going through a bit of onboarding this week, but expect to see them around in cloud-init shortly. I believe they have both landed their first PRs to get added as a contributor to cloud-init.

-

16:26 <blackboxsw> #topic In-progress Development

-

16:26 <blackboxsw> #link https://github.com/canonical/cloud-init/pulls

-

16:27 <blackboxsw> ok active review queue is really getting well maintained now that we've adopted PR assignment. Thanks for helping is land branches quickly folks.

-

16:28 <blackboxsw> Generally upstream has set a couple of long-term goals for cloud-init in the next development cycle

-

16:28 <blackboxsw> - wrap up cloud-init daemon mode (to reduce boot time by loading python only once)

-

16:28 <blackboxsw> - OpenStack network hotplug handling from cloud-init

-

16:29 <blackboxsw> - Potentially a new LXD datasource for handling container deployments

-

16:29 <blackboxsw> - better json schema coverage for the remaining oncovered cloud config modules.

-

16:30 <blackboxsw> #topic Community Charter

-

16:31 <blackboxsw> We continue to categorize more bitesize bugs in cloud-init.

-

16:31 <blackboxsw> #link https://bugs.launchpad.net/cloud-init/+bugs?field.tag=bitesize

-

16:32 <blackboxsw> These bugs are themed at doc updates and json schema improvements across all of cloud-init, but we continue to seed that bug tag with items which should be easy to drop in and make a lasting impact on cloud-init

-

16:33 <blackboxsw> All cloud-init contributors are encouraged to participate in any part of the cloud-init lifecycle, from bug filing, to fixing, to release testing and PR reviews. Thanks to everyone who continues to build the cloud-init community!

-

16:33 <blackboxsw> #topic Office hours (next ~30 mins)

-

16:35 <blackboxsw> During this stage we have a some focus time on cloud-init development and community support. Any questions, concerns, reviews or request for help/triage are most welcome. We should have a couple of upstream developers with eyes on this channel.

-

16:36 <blackboxsw> In the absence of discussion, we'll groom the active PR review queue and/or work additional cloud-init dev items.

-

16:38 <blackboxsw> community-notice: Ubuntu plans to release cloud-init version 20.2 to Ubuntu's new development release 20.10 (Groovy Gorilla). We expect to start an Ubuntu StableReleaseUpdate into xenial, bionic, eoan and focal within the next 2 weeks.

-

17:33 <blackboxsw> alrighty, think that about wraps today's status meeting. Happy Cinco De Mayo folks

-

17:34 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2020-05-19.html b/status-2020-05-19.html deleted file mode 100644 index 0855c9f..0000000 --- a/status-2020-05-19.html +++ /dev/null @@ -1,265 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Tue 19 May 2020 in status-meeting-minutes - - • 6 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-05-05.html#status-2020-05-05

-

#cloud-init pull-requests https://git.io/JeVed | Meeting minutes: https://goo.gl/mrHdaj | Next status meeting June 16:15 UTC | 20.1 (Feb 18) | 20.2 (Apr 28) | https://bugs.launchpad.net/cloud-init/+filebug

-

The discussion about "#cloud-init pull-requests https://git.io/JeVed | Meeting minutes: https://goo.gl/mrHdaj | Next status meeting June 16:15 UTC | 20.1 (Feb 18) | 20.2 (Apr 28) | https://bugs.launchpad.net/cloud-init/+filebug" started at 16:20.

-

#cloud-init pull-requests https://git.io/JeVed | Meeting minutes: https://goo.gl/mrHdaj | Next status meeting June 2 16:15 UTC | 20.1 (Feb 18) | 20.2 (Apr 28) | https://bugs.launchpad.net/cloud-init/+filebug

-

The discussion about "#cloud-init pull-requests https://git.io/JeVed | Meeting minutes: https://goo.gl/mrHdaj | Next status meeting June 2 16:15 UTC | 20.1 (Feb 18) | 20.2 (Apr 28) | https://bugs.launchpad.net/cloud-init/+filebug" started at 16:20.

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:21.

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:22.

-

In-progress Development

-

The discussion about "In-progress Development" started at 16:27.

-

Community Charter

-

The discussion about "Community Charter" started at 16:39.

- -

Office Hours (next ~30 mins)

-

The discussion about "Office Hours (next ~30 mins)" started at 16:44.

- -

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (52)
  • -
  • AnhVoMSFT (8)
  • -
  • meetingology (4)
  • -
  • meena (3)
  • -
  • Odd_Bloke (2)
  • -
  • smoser (0)
  • -
  • rharper (0)
  • -
-

Full Log

-

16:18 <blackboxsw> #startmeeting cloud-init status meeting

-

16:18 <meetingology> Meeting started Tue May 19 16:18:05 2020 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:18 <meetingology>

-

16:18 <meetingology> Available commands: action commands idea info link nick

-

16:18 <blackboxsw> #chair Odd_Bloke smoser rharper

-

16:18 <meetingology> Current chairs: Odd_Bloke blackboxsw rharper smoser

-

16:18 <blackboxsw> hello cloud-init, welcome to another round cloud-init status updates

-

16:19 <blackboxsw> our IRC channel topic carries the next planned status meeting for those that wish to participate. All are welcome to interject or drive converstation topics here

-

16:19 <blackboxsw> Previous meeting notes are here

-

16:19 <blackboxsw> #link https://cloud-init.github.io/status-2020-05-05.html#status-2020-05-05

-

16:19 <blackboxsw> and next status meeting should be in 2 weeks time.

-

16:20 <blackboxsw> looks like June 2. I'll set the topic of this irc channel to so that dropins can see a reminder for when that meeting is held

-

16:20 <blackboxsw> #topic #cloud-init pull-requests https://git.io/JeVed | Meeting minutes: https://goo.gl/mrHdaj | Next status meeting June 16:15 UTC | 20.1 (Feb 18) | 20.2 (Apr 28) | https://bugs.launchpad.net/cloud-init/+filebug

-

16:20 <blackboxsw> #topic #cloud-init pull-requests https://git.io/JeVed | Meeting minutes: https://goo.gl/mrHdaj | Next status meeting June 2 16:15 UTC | 20.1 (Feb 18) | 20.2 (Apr 28) | https://bugs.launchpad.net/cloud-init/+filebug

-

16:20 <blackboxsw> let's try that instead

-

16:21 <blackboxsw> The topics we generally cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter and Office Hours (~30 mins).

-

16:21 <blackboxsw> I'll jump through each topic, as always interjections, questions or other topics welcome

-

16:21 <blackboxsw> #topic Previous Actions

-

16:22 <blackboxsw> Nothing brought up as an action in the last meeting so we'll jump to the next topic

-

16:22 <blackboxsw> #topic Recent Changes

-

16:24 <blackboxsw> The following changes have landed in master; found via git log --since 05-05-2020 https://paste.ubuntu.com/p/d2qR8pTZNY/

-

16:26 <blackboxsw> there are a number of commits landed related to dropping additional py2 support from various paths as well as improving pytest fixtures (thx OddBloke) and some json schema definitions added to cc_snap and cc_apt_configure thanks lucasmoura

-

16:27 <blackboxsw> and an additional bit of work from meena to make libc discovery platform independent

-

16:27 <blackboxsw> #topic In-progress Development

-

16:30 <blackboxsw> Current themes of work for upstream include: continuing to refine a spec on cloud-init daemon mode and hot-plug support, purging python2-isms, improving pytest automation.

-

16:33 <blackboxsw> falcojr: also has a new approach for feature flag definitions/behavior in cloud-init in https://github.com/canonical/cloud-init/pull/367 This should give us the ability to better codify upstream unconfiguraable cloud-init behavior which may differ on previous releases.

-

16:34 <blackboxsw> falcojr: Odd_Bloke & smoser thanks for good design discussion there. anyone interested feel free to weigh in.

-

16:36 <blackboxsw> Also in-progress work is a cloud-init StableReleaseUpdate planned to publish cloud-init version 20.2 to xenial, bionic, eoan and focal.

-

16:37 <blackboxsw> This will publish latest cloud-init (after verification) to old stable releases

-

16:38 <blackboxsw> the first step before SRU is to upload latest cloud-init to Ubuntu Groovy(20.10). Once this upload is complete, we'll start the SRU process to publish to Xenial, Bionic, Eoan and Focal

-

16:39 <blackboxsw> #topic Community Charter

-

16:40 <blackboxsw> As discussed at the last cloud-init summit we targeted a couple of streams of work that are easy to work in parallel, making them prime candidates for community involvement.

-

16:41 <blackboxsw> Those streams/themes are: updating and correcting datasource documentation at https://cloudinit.readthedocs.io/en/latest/topics/datasources.html

-

16:41 <blackboxsw> and adding jsonschema definitions to any cloudinit.config.cc_* modules

-

16:41 <blackboxsw> any of these bugs are categorized as 'bitesize' and can be searched at the following link

-

16:42 <blackboxsw> #link https://bugs.launchpad.net/cloud-init/?field.tag=bitezise

-

16:43 <blackboxsw> a few of us have grabbed schema definitions for a few of the cloud config modules. I think we are up to 11 modules covered (of 50). Thanks all for the progress there. We have it on our roadmap to flesh out as much as we can

-

16:44 <blackboxsw> #topic Office Hours (next ~30 mins)

-

16:45 <blackboxsw> During this part of the meeting upstream devs should have eyes on the channel for any discussion related to feature, bug or review requests.

-

16:45 <blackboxsw> In the absence of active discussions, the active review queue will be be groomed.

-

16:46 <blackboxsw> for me, I've got to read through https://github.com/canonical/cloud-init/pull/367 in depth to see if I have any use-cases to add there for feature management

-

17:21 <blackboxsw> so, yeah sorry for the noise Odd_Bloke and falcojr in standup about whether this 'feature' is runtime configurable on/off. It doesn't even make sense for this #include case. Also I think the merits of falcojr's suggestion to rely on some unique environment variable to determine whether a feature is on or off can and should be encoded in cloud-init proper, instead of relying on patching when releasing to

-

17:21 <blackboxsw> ubuntu/xenial.

-

17:22 <blackboxsw> when we add a new 'feature' to cloud-init upstream. I believe we know what our expectations are for older stable releases at that time. We generally could encode those expectations (at least for ubuntu series which we maintain) that a feature should behave a certain way when we end up releasing to ubuntu/xenial. Avoiding the RELEASE_BLOCKER comment as a reminder for us to manually patch a release wouldn't be

-

17:22 <blackboxsw> necessary in these cases.

-

17:26 <AnhVoMSFT> q question: when I specify a custom data to format/partition the datadisk, it seems like the ephemeral resource disk isn't getting formatted to ext4 anymore. Is this by-design that when the customer specifies disk_setup and fs_setup for additional datadisk they need to also include the fs_setup for ephemeral0 (it seems odd because disk_setup got "merged" properly. I could see the ephemeral0

-

17:26 <AnhVoMSFT> got partitioned. Yet fs_setup isn't).

-

17:27 <AnhVoMSFT> I am not sure if this is an appropriate topic for Office Hours. I can wait :-)

-

17:30 <blackboxsw> AnhVoMSFT: thx for the question. so, what version of cloud-init and what's the user-data for partitioning that is isn't working as expected?

-

17:31 <AnhVoMSFT> https://pastebin.com/TG4E8Dft 19.4-33 (latest 18.04 image on Azure)

-

17:33 <AnhVoMSFT> (paste.ubuntu has been giving me problems today - not sure if it's only me)

-

17:49 <meena> blackboxsw: no mention of my work on the net refactoring or did i miss that

-

17:53 <blackboxsw> meena: sorry, right that is a large undertaking that you've raised via your PR https://github.com/canonical/cloud-init/pull/363

-

17:55 <meena> yeah, it's my: please teach my software engineering while all i do is code monkeying PR.

-

17:55 <meena> don't tell no one tho, or else they… might not.

-

17:58 <Odd_Bloke> blackboxsw: Could you comment on the PR where we're having that feature flag conversation, please?

-

17:58 <blackboxsw> Heh, generally the direction meena is going is toward distro-specific networking subclass to handle network rendering details (as most of our network rendering utility functions are highly distro-dependent

-

17:59 <blackboxsw> Odd_Bloke: yes, I shall.

-

17:59 <Odd_Bloke> Thanks!

-

18:06 <blackboxsw> Ok, I forgot to close out the meeting.

-

18:07 <blackboxsw> AnhVoMSFT: so I see your instance is properly "waiting" for the presence of ephemeral0 resource disk. trying to get to the bottom of why formatting isn't being addressed there.

-

18:10 <blackboxsw> I see 2020-05-19 17:20:24,072 - cc_mounts.py[DEBUG]: Mapped metadata name ephemeral0 to /dev/disk/cloud/azure_resource

-

18:10 <blackboxsw> 2020-05-19 17:20:24,073 - cc_mounts.py[DEBUG]: changed default device ephemeral0 =>` /dev/disk/cloud/azure_resource-part1

-

18:16 <AnhVoMSFT> @blackboxsw this is reproducing 100% of the time

-

18:17 <blackboxsw> I'm wondering AnhVoMSFT if the ephemeral0 alias needs to be used instead. something like https://paste.ubuntu.com/p/7wmMc8drZ3/

-

18:19 <blackboxsw> I see we've done SRU testing referencing that alias instead of full resource disk path https://github.com/cloud-init/ubuntu-sru/blob/master/bugs/b59870ca.txt

-

18:23 <AnhVoMSFT> @blackboxsw, my config is actually having an EXTRA datadisk

-

18:23 <AnhVoMSFT> so in this case the VM is deployed with an additional data disk attached to the VM

-

18:24 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2020-06-02.html b/status-2020-06-02.html deleted file mode 100644 index 8252f81..0000000 --- a/status-2020-06-02.html +++ /dev/null @@ -1,295 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Tue 02 June 2020 in status-meeting-minutes - - • 8 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:24.

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:27.

-

In-progress Development

-

The discussion about "In-progress Development" started at 16:34.

- -

Community Charter

-

The discussion about "Community Charter" started at 16:47.

- -

Office Hours (next ~30 mins)

-

The discussion about "Office Hours (next ~30 mins)" started at 16:50.

-

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (76)
  • -
  • Odd_Bloke (6)
  • -
  • knaccc (5)
  • -
  • meena (5)
  • -
  • meetingology (4)
  • -
  • rharper (3)
  • -
  • ddstreet (1)
  • -
  • ubot5 (1)
  • -
  • smoser (0)
  • -
-

Full Log

-

16:21 <blackboxsw> #startmeeting cloud-init status meeting

-

16:21 <meetingology> Meeting started Tue Jun 2 16:21:15 2020 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:21 <meetingology>

-

16:21 <meetingology> Available commands: action commands idea info link nick

-

16:21 <blackboxsw> hi folks, time for another cloud-init upstream status meeting.

-

16:22 <blackboxsw> we use this meeting to provide a venue for any cloud-init interested parties to keep up to date on current development, release-related info and expedite distributed development where possible.

-

16:22 <blackboxsw> this meeting is a welcome place for interruptions, questions, requests and unrelated discussions at any point. so don't be shy :)

-

16:23 <blackboxsw> #chair Odd_Bloke smoser rharper

-

16:23 <meetingology> Current chairs: Odd_Bloke blackboxsw rharper smoser

-

16:23 <blackboxsw> The topics we generally cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Office Hours (~30 mins).

-

16:24 <blackboxsw> previous meeting minutes live here (and I just saw I forgot to publish last minutes so I pushed them now)

-

16:24 <blackboxsw> #link https://cloud-init.github.io/

-

16:24 <blackboxsw> #topic Previous Actions

-

16:25 <blackboxsw> nothing actionable brought up in last meeting on 05/19

-

16:26 <blackboxsw> Odd_Bloke: ahh we should fix devel with those pkg drops on next upload

-

16:26 <blackboxsw> we did drop that for Xenial, Bionic Eoan and maybe focal too?

-

16:26 <blackboxsw> so an oversight for groovy

-

16:27 <blackboxsw> next topic

-

16:27 <blackboxsw> #topic Recent Changes

-

16:28 <blackboxsw> the following are commits landed in tip of master found via git log --since 05/19/2020 : https://paste.ubuntu.com/p/QFvgWhjXY9/

-

16:28 <Odd_Bloke> blackboxsw: When you say "next upload" are you referring to the upload you're about to do, or the one after that?

-

16:28 <blackboxsw> Odd_Bloke: if you'd like we can adjust the current upload so that devel, focal, bionic xenial eoan all drop those stale deps

-

16:28 <blackboxsw> I think X, B E have all dropped them

-

16:29 <blackboxsw> so maybe I re-do ubuntu/devel PR Odd_Bloke ?

-

16:29 <blackboxsw> probably good/better/correct to keep all releases on the same footing.

-

16:29 <Odd_Bloke> blackboxsw: I think it's worth doing, we've uploaded without fixing it a few times before, and we've remembered this time around.

-

16:30 <blackboxsw> yeah sounds good Odd_Bloke I'll re-do that devel PR (and make sure focal drops it too)

-

16:30 <blackboxsw> if needed

-

16:30 <Odd_Bloke> And it should just be a case of pushing a new commit to your existing branch.

-

16:30 <Odd_Bloke> Thanks!

-

16:30 <blackboxsw> +1

-

16:32 <blackboxsw> things of note in the recent commits landed. https://github.com/canonical/cloud-init/pull/358 Mattew Ruffell improved cc_grub_dpkg to be more dynamic in matching disks instead of a hardcoded device list

-

16:33 <blackboxsw> thanks Matthew

-

16:33 <blackboxsw> and chef_license support https://github.com/canonical/cloud-init/commit/0919bd46bbd1b12158c369569ec1298bb000dd8a

-

16:34 <blackboxsw> thanks bipinbachhao for the config extension there

-

16:34 <blackboxsw> #topic In-progress Development

-

16:35 <blackboxsw> a couple of new notables in flight at the moment:

-

16:38 <blackboxsw> - falcojr: introduction of feature-flags for cloud-init upstream to give us a toggle to retain original behavior of #include failures on stable downstream releases. https://github.com/canonical/cloud-init/pull/367 . Upstream cloud-init will fail loudly and raise an Exception if someone tries to #include a url which fails. this differs from original cloud-init behavior which was to try our best to get a system up

-

16:38 <blackboxsw> and running, even amid not-critical failures

-

16:39 <blackboxsw> per the above, if downstreams (distributiions) would like to retain a more permissive warn on #include user-data issues, a cloudinit/feature_overrides.py file would need to be introduced in the downstream

-

16:40 <blackboxsw> - Also meena and Odd_Bloke and others have been working toward a refactor of cloudinit.net modules. Dan added a doc PR to capture this approach https://github.com/canonical/cloud-init/pull/391

-

16:41 <blackboxsw> beyond that, there are a number of PRs up from lucas on json schema additions for cloudinit/config/cc_* modules to get better validation of #cloud-config user-data

-

16:42 <blackboxsw> For ubuntu proper, we have started the StableReleaseUpdate process for cloud-init to publish master into ubuntu/xenial, bionic, eoan and focal releases

-

16:43 <blackboxsw> some of these changes will add the opportunity to enable 'new' features on platforms like Azure

-

16:43 <blackboxsw> and AWS

-

16:43 <blackboxsw> Azure (xenial) will be dropping walinuxagent support

-

16:44 <blackboxsw> AWS will now surface a datasource config option apply_full_imds_network_config boolean

-

16:45 <blackboxsw> if set true in an Ec2(aws) image network configuration from cloud-init can come completely from IMDS for every connected NIC. That config will include all secondary IPv4/IPv6 addressses configured for the machine

-

16:46 <blackboxsw> Upstream has started the Ubuntu SRU process (which generally takes around 10-14 days). We plan to include every commit that has landed in tip of master as of commitish 5f7825e22241423322dbe628de1b00289cf34114

-

16:46 <blackboxsw> the bug related to this SRU work is here

-

16:46 <blackboxsw> #link https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018

-

16:46 <ubot5> Ubuntu bug 1881018 in cloud-init (Ubuntu Focal) "sru cloud-init (19.4.33 to 20.2-30) Xenial, Bionic, Eoan and Focal" [Undecided,New]

-

16:47 <blackboxsw> #topic Community Charter

-

16:48 <blackboxsw> upstream has signed up to get as much of the json schema coverage as we can for cloudinit/config/cc*py modules since invalid #cloud-config user-data formats tends to have one of the highest incidence of errors (because writing YAML is something humans shouldn't have to do :) )

-

16:49 <blackboxsw> so we are chopping away at defining JSON schema for as many cloud config modules as possible . there are still plenty to choose from. Anyone can feel free to grab a JSON schema bug and help us with bettering cloud-init

-

16:49 <blackboxsw> bugs are filed for each config module which needs schema definition:

-

16:49 <blackboxsw> #link https://bugs.launchpad.net/cloud-init/?field.tag=bitezise

-

16:50 <blackboxsw> a big thanks to lucasmoura for starting to grab a number of these

-

16:50 <blackboxsw> #topic Office Hours (next ~30 mins)

-

16:50 <blackboxsw> This 'section' of the meeting is a time where a couple of upstream devs will be available in channel for any discussions, questions, bug work or PR reviews.

-

16:51 <blackboxsw> In the absence of discussions/topics here we scrub the review queue.

-

16:51 <blackboxsw> since we are mid-stream on Ubuntu SRU at the moment, I'll be addressing review comments on some of the functional 'upload' branches we've put together

-

16:52 <blackboxsw> and, let's update the topic for next IRC meeting too while we are at it

-

16:59 <blackboxsw> Odd_Bloke: just pushed ubuntu/devel dropping python3-six|unittest2|nose

-

17:01 <blackboxsw> and just re-pushed ubuntu/focal to drop python3-six

-

17:04 <blackboxsw> oops and missed you others. reworking

-

17:12 <blackboxsw> ok re-pushed. focal and devel PRs in shape

-

17:13 <blackboxsw> dropped the following build-deps: python3-six, python3-unittest2, python3-pep8, python3-nose, python3-pyflakes

-

17:20 <Odd_Bloke> blackboxsw: +1 on the ubuntu/devel upload.

-

17:21 <blackboxsw> whew, think we got all of the dropped deps between the two of us... thanks!

-

17:21 <blackboxsw> Odd_Bloke: thanks focal looks good and sbuilds

-

17:21 <blackboxsw> just finished eoan and building now to test

-

17:23 <meena> what? me??

-

17:24 <blackboxsw> well yes indeedy meena, just trying to keep you highlighted as participating in the cloud-init status meeting :) you've thankfully reviewed, pushed and prodded us to talk about cloudinit.net refactor and how best to address it I think :) credit due ;)

-

17:26 <blackboxsw> community notice: upload to Ubuntu groovy of cloud-init master accepted [ubuntu/groovy-proposed] cloud-init 20.2-45-g5f7825e2-0ubuntu1 (Accepted)

-

17:30 <Odd_Bloke> blackboxsw: One issue with https://github.com/canonical/cloud-init/pull/412

-

17:31 <meena> blackboxsw: i'm just waiting for Odd_Bloke to provide the basic infrastructure so i can start moving code… without that, i have to bug other projects in my … 2 hours of free time per day.

-

17:31 <meena> blackboxsw: yesterday, i tried to build an android app on my laptop and gave up after an hour.

-

17:35 <blackboxsw> nice review again Odd_Bloke, will reflect that patch to each series. as every other ubuntu/* is missing enabling various cloud datasources beyond just Rbx

-

17:54 <blackboxsw> Odd_Bloke: rharper so Xenial is interesting for datasource config via dpkg

-

17:55 <blackboxsw> We are missing: Hetzner, IBMCloud, Oracle, and RbxCloud

-

17:55 <blackboxsw> one was an oversight on previous SRUs

-

17:55 <blackboxsw> but Oracle and IBMCloud, I'm trying to recall if there is a reason we didn't want to surface either of those datasources as configurable on Xenial

-

17:56 <blackboxsw> a little warning bell is going off in my head

-

17:56 <blackboxsw> Hetzner I thought was 'ok'

-

17:56 <blackboxsw> Oracle currently gets detected as OpenStack on Xenial.

-

17:57 <rharper> IBMCloud and Oracle are sensitive

-

17:57 <rharper> not sure about Hetzner or RbxCloud though

-

17:57 <blackboxsw> upstream Oracle datasource is 'good', but I wasn't sure if there was extra baggage associated with not backporting that functionality

-

17:57 <rharper> blackboxsw: I think you might want to check with CPC on those

-

17:58 <meena> Hetzner is also detected as OpenStack on FreeBSD… but… only thru cloud-init itself, not thru ds-identify

-

18:03 <meena> (i'm not sure how much of that is my fault having helped a lot with Hetzner and FreeBSD and ds-identify myself)

-

18:03 <knaccc> Odd_Bloke thanks for your reply. I managed to fix things in the end, but kinda by cheating. Now my /etc/netplan/50-cloud-init.yaml only contains the IP addresses configuration, and I make the nameservers and search domain apply in the "Global" scope (as reported by systemd-resolve --status) by simply modifying the /etc/resolv.conf file. All configuration survives reboot just fine, and I am no longer

-

18:03 <knaccc> scared that resolv.conf will be overwritten because I found a web page that said that "Note: The mode of operation of systemd-resolved is detected automatically, depending on whether /etc/resolv.conf is a symlink to the local stub DNS resolver file or contains server names." Although you said in your message that "cloud-init will regenerate /etc/netplan/50-cloud-init.yaml on each boot, so yes, you don't

-

18:03 <knaccc> want to modify that", the OVH instructions directly contradict that and tell me to edit it to add all IP addresses to my interface (see Ubuntu 18.04 section here: https://docs.ovh.com/gb/en/vps/network-ipaliasing-vps/). I'm therefore very confused about why OVH seem to contradict the instructions that are in that config file, and confused as to what other location I should be editing/creating instead

-

18:06 <ddstreet> knaccc why do you want to change resolved 'Global' section?

-

18:08 <blackboxsw> heh meena not at fault :) . Just need to make sure we move cloud-platforms to a better way of detecting the right datasource when we can.

-

18:08 <knaccc> ddstreet if I put the nameservers and search domain into the /etc/netplan/50-cloud-init.yaml file, it gets ignored completely (i.e. although those configurations show up in systemd-resolve --status against that specific "link", the "Global" nameservers and lack of any search domain in that Global section are taking precedence). Therefore I had to configure nameservers and search domain at the resolv.conf

-

18:08 <knaccc> level so that it appeared in the Global section, and then suddenly everything worked for the first time

-

18:08 <blackboxsw> I should tie off our cloud-init status meeting. Thanks folks for all who've attended

-

18:08 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2020-06-16.html b/status-2020-06-16.html deleted file mode 100644 index 1a3064f..0000000 --- a/status-2020-06-16.html +++ /dev/null @@ -1,280 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Tue 16 June 2020 in status-meeting-minutes - - • 6 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:24.

-

In-progress Development

-

The discussion about "In-progress Development" started at 16:32.

- -

community charter

-

The discussion about "community charter" started at 16:54.

- -

Office Hours (~next 30 minutes)

-

The discussion about "Office Hours (~next 30 minutes)" started at 16:59.

- -

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (61)
  • -
  • meena (6)
  • -
  • meetingology (6)
  • -
  • AnhVoMSFT (2)
  • -
  • ubot5 (1)
  • -
  • cyberpear (1)
  • -
  • Odd_Bloke (1)
  • -
  • smoser (0)
  • -
  • rharper (0)
  • -
-

Full Log

-

16:21 <blackboxsw> #startmeeting cloud-init status meeting

-

16:21 <meetingology> Meeting started Tue Jun 16 16:21:42 2020 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:21 <meetingology>

-

16:21 <meetingology> Available commands: action commands idea info link nick

-

16:22 <blackboxsw> #chair smoser Odd_Bloke rharper

-

16:22 <meetingology> Current chairs: Odd_Bloke blackboxsw rharper smoser

-

16:22 <blackboxsw> Welcome to the bi-weekly cloud-init status meeting. A place to chat about upstream cloud-init activity/

-

16:23 <blackboxsw> his meeting is a welcome place for interruptions, questions, requests and unrelated discussions at any point.

-

16:23 <blackboxsw> this

-

16:23 <blackboxsw> previous meeting minutes are stored on github

-

16:23 <blackboxsw> #link https://cloud-init.github.io/

-

16:24 <blackboxsw> The topics we generally cover in this meeting are the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Office Hours (~30 mins).

-

16:24 <blackboxsw> From the previous meeting we captured no actions, so I'll jump into the next topic

-

16:24 <blackboxsw> #topic Recent Changes

-

16:25 <blackboxsw> the following are commits merged into cloud-init's upstream master branch: https://paste.ubuntu.com/p/WdsZXbwwWd/

-

16:26 <blackboxsw> found via git log --since 06-02-2020

-

16:29 <blackboxsw> notable changes: util.runparts and subp out of util into subp.py, there are a couple of branches related to improved vmware support, and resolving keyerror issues for users providing network configuration with bridges.

-

16:30 <blackboxsw> also upstream travis CI is now using the commercial travis-ci.com instead of travis-ci-org which should give us better throughput on test runs.

-

16:31 <blackboxsw> community notice: if any PRs created >` 1 week ago have problems with unresolved travis ci runs marked 'in progress' those PRs will likely need to be closed and re-submitted due to the shift in travis-ci endpoints.

-

16:32 <blackboxsw> #topic In-progress Development

-

16:33 <blackboxsw> Upstream devs are currently working our way through Ubuntu StableReleaseUpdate (SRU) validation to release cloud-init version 20.2.45 to Ubuntu Xenial, Bionic, Eoan and Focal. Thanks falcojr lucasmoura and Odd_Bloke for all the help generating test cases and reviewing SRU-related content.

-

16:34 <blackboxsw> We are about halfway through out testing of this release of cloud-init and expect to be able to wrap this up before next week.

-

16:34 <blackboxsw> To track this release, anyone can subscribe to the SRU process bug

-

16:35 <blackboxsw> #link https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018

-

16:35 <ubot5> Ubuntu bug 1881018 in cloud-init (Ubuntu) "sru cloud-init (19.4.33 to 20.2-45) Xenial, Bionic, Eoan and Focal" [Undecided,In progress]

-

16:35 <blackboxsw> that bug will go to Fix Released when our upload to <ubuntu-release>-updates apt pocket is published

-

16:36 <blackboxsw> Beyond SRU, there is a significant refactor of cloudinit.net* module to define a clear API and push distro-specific content into the distro modules.

-

16:37 <blackboxsw> #link

-

16:37 <blackboxsw> #link https://github.com/canonical/cloud-init/pull/391

-

16:38 <blackboxsw> Thanks Odd_Bloke for driving that refactor. Those interested should check out the above PR

-

16:39 <blackboxsw> I think that about wraps it.

-

16:40 <meena> during the util.subp refactor i suggested also looking into centralising service enabling and (re) starting

-

16:41 <meena> but we kinda glossed over that because of the net refactor

-

16:41 <blackboxsw> meena: good chance to bring that up: let's get that comment link

-

16:43 <blackboxsw> #link https://github.com/canonical/cloud-init/pull/416#issuecomment-640032968

-

16:44 <blackboxsw> meena: your comment was really about re-organizing the ./systemd ./upstart top-level directories and refactoring down into the distros somehow?

-

16:44 <blackboxsw> as that startup service construct is highly distro dependent?

-

16:46 <blackboxsw> If that's the suggestion you are raising for comment, I think it sounds like a reasonable thing to consider. Each distro has it's own way of handling system service management.

-

16:47 <meena> *nod

-

16:48 <blackboxsw> given the fact that all the systemd/ startup script files are all templates, it indicates that we have a lot of distro-specific uniqueness even across various flavors of linux

-

16:49 <blackboxsw> I think that refactor would be significantly simpler to describe in a distro-level API

-

16:51 <blackboxsw> meena: maybe we file a feature bug against cloud-init so we can prioritize that work.

-

16:51 <meena> you're right. let's do that

-

16:52 <blackboxsw> we could surface that bug to the mailinglist

-

16:53 <blackboxsw> meena: do you want to do either of those (bug or mailinglist email: subj: Refactor startup service to distro-specific Api) ?

-

16:53 <blackboxsw> #action file feature bug about refactoring startup services

-

16:53 * meetingology file feature bug about refactoring startup services

-

16:53 <blackboxsw> #action mailing list email requesting comment/concerns about a refactor of startup services

-

16:53 * meetingology mailing list email requesting comment/concerns about a refactor of startup services

-

16:54 <blackboxsw> I've added actions that we can track by next meeting to see if we can make progress on that discussion

-

16:54 <blackboxsw> ok next topic I think

-

16:54 <blackboxsw> #topic community charter

-

16:55 <blackboxsw> As always, any aspects of the cloud-init project is open for participation from community members.

-

16:56 <blackboxsw> We thank everyone for contributing bugs @ https://bugs.launchpad.net/cloud-init/+filebug, reviewing open 'New' bugs that are filed, and reviewing pulls requests @ https://github.com/canonical/cloud-init/pulls

-

16:57 <blackboxsw> all reviews are welcome on any PRs that are up. and driving feature discussions are also encouraged. Thanks meena for participating on all of those fronts

-

16:59 <blackboxsw> for those just wanting to join in and contribute small pull requests there is a queue of bugs or features that should be a fairly contained set of tasks in our bitesize queue:

-

16:59 <blackboxsw> #link https://bugs.launchpad.net/cloud-init/?field.tag=bitezise

-

16:59 <blackboxsw> #topic Office Hours (~next 30 minutes)

-

17:00 <blackboxsw> This 'section' of the meeting is a time where a couple of upstream devs will be available in channel for any discussions, questions, bug work or PR reviews.

-

17:01 <blackboxsw> In the absence of discussion topics, reviewing the active PRs generally occurs to scrub our queue and unblock conversations.

-

17:02 * blackboxsw addresses some review comments on a CI Ubuntu daily test branch

-

17:22 <AnhVoMSFT> question: is there anyway to only target a particular reporting handler?

-

17:23 <AnhVoMSFT> Right now the Azure DS emits events to the HyperV KVP handler and they also pass through the log handler. For the most part this is fine (and useful). For some larger event message (like compressed log), it does not make sense to emit a large blob of compressed gzip + b64 to the log, is it possible to skip the log handler ?

-

17:30 <blackboxsw> hrm, good question AnhVoMSFT . looking

-

17:33 <Odd_Bloke> blackboxsw: meena: Note that the service files are selected at package generation time, not at runtime, so it's not entirely clear to me how you would integrate them into the Distro hierarchy.

-

17:42 <blackboxsw> nice suggestion Odd_Bloke

-

17:43 <blackboxsw> AnhVoMSFT: I'm not seeing any filtering config options in reporting: config for handlers. Are you saying you are looking to add compressed object writes to your kvp message message plane?

-

17:44 * cyberpear wondering if there's any collaboration with the ignition folks

-

17:46 <blackboxsw> AnhVoMSFT: I think it's be reasonable to provide a named report handler to ReportEventStack

-

17:46 <blackboxsw> and let ReportEventStack limit what handlers it can emit publish_event to

-

17:48 <meena> https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_puppet.py#L106 could this be entirely puppet specific, and no other module does this dance?

-

17:50 <blackboxsw> AnhVoMSFT: that'd mean I suppose that report_event would need to accept a new param to limit which handler it calls handler.publish_event for

-

17:50 <blackboxsw> https://github.com/canonical/cloud-init/blob/master/cloudinit/reporting/events.py#L84

-

17:52 <meena> https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_rsyslog.py#L210 one more

-

17:52 <blackboxsw> or maybe you are suggesting that we add the ability for an existing handler to define a set of data types that it accepts (and will silently ignore others)?

-

17:54 <blackboxsw> and here meena https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_fan.py#L55-L83

-

17:58 <blackboxsw> ok I've got to run. time to close the meeting for today. Thanks all for joining in!

-

17:58 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2020-06-30.html b/status-2020-06-30.html deleted file mode 100644 index 3b712fb..0000000 --- a/status-2020-06-30.html +++ /dev/null @@ -1,282 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Tue 30 June 2020 in status-meeting-minutes - - • 6 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-06-16.html#status-2020-06-16

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:28.

-

In-progress Development

-

The discussion about "In-progress Development" started at 16:31.

- -

Recent Changes

-

The discussion about "Recent Changes" started at 16:34.

- -

In-progress Development

-

The discussion about "In-progress Development" started at 16:49.

- -

community charter

-

The discussion about "community charter" started at 17:02.

- -

Office Hours (~20 mins)

-

The discussion about "Office Hours (~20 mins)" started at 17:08.

-

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (73)
  • -
  • meetingology (4)
  • -
  • ubot5 (1)
  • -
  • rharper (1)
  • -
  • smoser (0)
  • -
  • Odd_Bloke (0)
  • -
-

Full Log

-

16:22 <blackboxsw> #startmeeting cloud-init status meeting

-

16:22 <meetingology> Meeting started Tue Jun 30 16:22:42 2020 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:22 <meetingology>

-

16:22 <meetingology> Available commands: action commands idea info link nick

-

16:23 <blackboxsw> community notice: time for another bi-weekly (or semi-monthly if you prefer) cloud-init community status meeting

-

16:24 <blackboxsw> #chair smoser rharper Odd_Bloke

-

16:24 <meetingology> Current chairs: Odd_Bloke blackboxsw rharper smoser

-

16:25 <blackboxsw> welcome to another round of cloud-init upstream updates and discussion. We use this meeting as a time to gather to discuss current development of cloud-init, ask and answer questions, and generally expedite development be unblocking devs. All questions. side-conversations and interruptions are welcome

-

16:25 <blackboxsw> last meeting minutes are at the link below

-

16:26 <blackboxsw> #link https://cloud-init.github.io/status-2020-06-16.html#status-2020-06-16

-

16:26 <blackboxsw> turns out I didn't update the topic for the next meeting time last session. Let's do that now

-

16:26 <blackboxsw> +2 weeks from now, same time

-

16:26 <blackboxsw> July 14th, same UTC time

-

16:27 <blackboxsw> now that that's out of the way, we typically cover the following topics.

-

16:27 <blackboxsw> Previous Actions, Recent Changes, In-progress Development, Community Charter, Office Hours (~30 mins).

-

16:27 <blackboxsw> additionally today, I'll discuss the current cloud-init SRU

-

16:28 <blackboxsw> #topic Previous Actions

-

16:28 <blackboxsw> topic #1. our previous meeting minutes logged two actions:

-

16:28 * blackboxsw file feature bug about refactoring startup services

-

16:30 <blackboxsw> I think in further discussion during last meeting, we talked with Odd_Bloke and meena and determined that we can't actually refactor startup services to live in the distro specifically, because these startup service templates actually get determined at cloud-init generator time (before distribution is determined in cloud-init's python code) so trying to specialize startup script content generation in the distro

-

16:30 <blackboxsw> python classes in cloud-init is too late

-

16:30 <blackboxsw> so this action is tabled as /wont-fix

-

16:31 <blackboxsw> that follows as well with the other ACTION: mailing list email requesting comment/concerns about a refactor of startup services

-

16:31 * blackboxsw isn't sure how to close out actions in meetingology syntax/cmds

-

16:31 <blackboxsw> #topic In-progress Development

-

16:33 <blackboxsw> The following is the set of commits landed in 'master' of cloud-init upstream repo: found with git log --since 06-20-2020

-

16:33 <blackboxsw> #link ACTION: mailing list email requesting comment/concerns about a refactor of startup services

-

16:33 <blackboxsw> #link https://paste.ubuntu.com/p/fSvwRks86z/

-

16:34 <blackboxsw> heh paste error

-

16:34 <blackboxsw> #topic Recent Changes

-

16:34 * blackboxsw sets appropriate topic for this section

-

16:37 <blackboxsw> so recently Odd_Bloke and a number of BSD folks (meena igalic etc) have gone through a number of discussions and design regarding a refactor of cloudinit.net functions to a cloudinit.distro.networking module as most network-related functionality is highly distro-dependent

-

16:37 <blackboxsw> Odd_Bloke: created an overview of this current refactor work and published it to readthedocs

-

16:37 <blackboxsw> #link https://cloudinit.readthedocs.io/en/latest/topics/hacking.html#ongoing-refactors

-

16:38 <blackboxsw> This has been a big effort to get organized and started so many thanks for all those paricipating in this discussion, development and reviews.

-

16:39 <blackboxsw> there are many, functions that need to be refactored from cloudinit.net into the distribution-specialized cloudinit.distro.networking classes.

-

16:40 <blackboxsw> It is work that can be easily done in parallel and there is a tag used to classify each refactor as a "net-refactor" bug in launchpad

-

16:40 <blackboxsw> #link https://bugs.launchpad.net/cloud-init/+bugs?field.tag=net-refactor

-

16:41 <blackboxsw> community notice: we encourage anyone interested in refactoring cloud-init networking functionality to grab and work any of those net-refactor bugs

-

16:41 <blackboxsw> there are a couple of example PRs up that give a good idea of how to get started

-

16:42 <blackboxsw> #link https://github.com/canonical/cloud-init/pull/457

-

16:42 <blackboxsw> and I can't seem to find the other at the moment.

-

16:48 <blackboxsw> besides net-refactor content landing, there have been fixes to Hetzner and RbxCloud datasources, redhat's systemd generator templates, Centos copr build fixes to help RPM build runs and Azure datasource logging. Thanks smoser, paride Moustafa and otubo Adam Dobrawy for contributions this round

-

16:49 <blackboxsw> #topic In-progress Development

-

16:51 <blackboxsw> Generally the last two weeks have been sunk into upstream testing and validation of cloud-init for SRU (Stable release Update) into Ubuntu Xenial Bionic, Eoan and Focal.

-

16:52 <blackboxsw> 3 to 5 of us have been on verification tasks on various clouds for all Ubuntu releases targeted and all features which affect ubuntu.

-

16:52 <blackboxsw> A thousand thanks rharper Odd_Bloke factor lucasmoura and xiaofeng for working through and validating some of these SRU tasks.

-

16:54 <blackboxsw> Our job is done, and we are awaiting feedback from an automation CI from Canonical solutions QA at the moment which runs through a ton of Openstack networking customer-configurations. It has been in the test queue for a week, and I just saw a successful run from that test harness this morning. That team has told us it looks for 3 successful runs to "pass" so I expect that pass to come shortly as the test runs

-

16:54 <blackboxsw> are currently inprogress.

-

16:55 <blackboxsw> as soon as this test passes we will mark the SRU bug verified and the SRU team will publish bits of cloud-init.

-

16:55 <blackboxsw> #link https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018

-

16:55 <ubot5> Ubuntu bug 1881018 in cloud-init (Ubuntu) "sru cloud-init (19.4.33 to 20.2-45) Xenial, Bionic, Eoan and Focal" [Undecided,In progress]

-

16:56 <blackboxsw> This SRU has taken about 1+ week longer than normal verification because we hadn't SRU'd cloud-init in around 6 months, so there was a lot more content to verify.

-

16:57 <blackboxsw> Hopefully additional SRUs will be more frequent and less heavy-weight. We are looking into reducing the overhead on this process and will pitch ideas to the cloud-init mailinglist for input

-

16:57 <blackboxsw> Beyond SRU work, the following other work is in progress:

-

16:58 <blackboxsw> * net-refactor formerly mentioned

-

16:58 <blackboxsw> * falcojr into Oracle integration test harness

-

16:58 <blackboxsw> * extending json schema validation for remaining cloud-config modules for better error reporting around invalid user-data

-

17:00 <blackboxsw> Long term work: cloud-init standalone daemon to improve startup time by avoiding reloading python across each cloud-int boot stage, initial networking hot-plug support to which datasources could "opt-in"

-

17:01 <rharper> blackboxsw: =)

-

17:01 <blackboxsw> I think that about wraps this topic.

-

17:01 <blackboxsw> yeah rharper, we've got it on our roadmap. We'd love to see that get in this round.

-

17:02 <blackboxsw> #topic community charter

-

17:03 <blackboxsw> We have a couple of general themes of features we are working toward as a community this year:

-

17:04 <blackboxsw> * json schema additions for cloudinit.config.cc_* modules to improve user-facing errors on invalid user-data

-

17:04 <blackboxsw> * datasource documentation improvements, updates and corrections

-

17:04 <blackboxsw> * cloudinit.net-refactor work

-

17:05 <blackboxsw> We encourage any interested developers to grab any of these work items related to these features.

-

17:06 <blackboxsw> We have two bug tags which enumerate each component of these work streams:

-

17:07 <blackboxsw> #link https://bugs.launchpad.net/cloud-init/?field.tag=bitesize

-

17:07 <blackboxsw> #link https://bugs.launchpad.net/cloud-init/+bugs?field.tag=net-refactor

-

17:08 <blackboxsw> #topic Office Hours (~20 mins)

-

17:08 <blackboxsw> This 'section' of the meeting is a time where a couple of upstream devs will be available in channel for any discussions, questions, bug work or PR reviews.

-

17:08 <blackboxsw> I think I spent most of the time typing, but will hit the review queue in the absence of any other discussion

-

17:17 <blackboxsw> merged https://github.com/canonical/cloud-init/pull/461

-

17:51 <blackboxsw> lucasmoura: one minor change request and description update on the PR requested https://github.com/canonical/cloud-init/pull/390#pullrequestreview-440241947

-

17:51 <blackboxsw> then we can land this one

-

17:51 <blackboxsw> ok folks, thanks for checking into the cloud-init status meeting. See you in 2 weeks.

-

17:51 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2020-07-14.html b/status-2020-07-14.html deleted file mode 100644 index f763316..0000000 --- a/status-2020-07-14.html +++ /dev/null @@ -1,262 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Tue 14 July 2020 in status-meeting-minutes - - • 5 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-06-30.html#status-2020-06-30

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:55.

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:56.

- -

In-progress Development

-

The discussion about "In-progress Development" started at 17:01.

- -

Community Charter

-

The discussion about "Community Charter" started at 17:08.

- -

Office Hours (next ~30 mins)

-

The discussion about "Office Hours (next ~30 mins)" started at 17:13.

-

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (52)
  • -
  • ubot5 (5)
  • -
  • meetingology (4)
  • -
  • AnhVoMSFT (2)
  • -
  • Odd_Bloke (2)
  • -
  • smoser (0)
  • -
  • rharper (0)
  • -
-

Full Log

-

16:52 <blackboxsw> #startmeeting cloud-init status meeting

-

16:52 <meetingology> Meeting started Tue Jul 14 16:52:35 2020 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:52 <meetingology>

-

16:52 <meetingology> Available commands: action commands idea info link nick

-

16:52 <AnhVoMSFT> nvm

-

16:52 <blackboxsw> heh.

-

16:52 <blackboxsw> let's do it since we have an active attendee.

-

16:53 <blackboxsw> i'll make it snappy today

-

16:53 <AnhVoMSFT> sounds good

-

16:53 <blackboxsw> community notice: time for another bi-weekly (or semi-monthly if you prefer) cloud-init community status meeting

-

16:53 <blackboxsw> #chair rharper Odd_Bloke smoser

-

16:53 <meetingology> Current chairs: Odd_Bloke blackboxsw rharper smoser

-

16:53 <blackboxsw> welcome to another round of cloud-init upstream updates and discussion. We use this meeting as a time to gather to discuss current development of cloud-init, ask and answer questions, and generally expedite development be unblocking devs. All questions. side-conversations and interruptions are welcome

-

16:54 <blackboxsw> first order of bizzzznesss. setting the meeting for next time

-

16:54 <blackboxsw> +2 weeks from today

-

16:54 <blackboxsw> July 28th same time (minus 30 mins)

-

16:55 <blackboxsw> previous meeting minutes are here:

-

16:55 <blackboxsw> #link https://cloud-init.github.io/status-2020-06-30.html#status-2020-06-30

-

16:55 <blackboxsw> The topics we'll cover today: Previous Actions, Recent Changes, In-progress Development, Community Charter, Office Hours (~30 mins).

-

16:55 <blackboxsw> #topic Previous Actions

-

16:56 <blackboxsw> none seen last session. so we can jump to the next topic

-

16:56 <blackboxsw> #topic Recent Changes

-

16:56 <blackboxsw> The following commits have been landed on master of upstream branch since last meeting: found via git log --since 2020-06-30

-

16:57 <blackboxsw> #link https://paste.ubuntu.com/p/6Fn5jy8t46/

-

16:58 <blackboxsw> a bit of cleanup and test coverage work and CI fixups for lxd integratin testing in those commits.

-

16:58 <blackboxsw> Of note:

-

16:59 <blackboxsw> a fix for (LP: #1456277) thx lucas

-

16:59 <ubot5> Launchpad bug 1456277 in cloud-init "cloud-init searches for ec2 mirrors regardless of what cloud its on" [High,Fix committed] https://launchpad.net/bugs/1456277

-

16:59 <blackboxsw> a fix for (LP: #1884619) part of the cloudinit.net refactor for thx Odd_Bloke

-

16:59 <ubot5> Launchpad bug 1884619 in cloud-init "cloudinit.net refactor: is_physical" [Low,Fix committed] https://launchpad.net/bugs/1884619

-

16:59 <blackboxsw> and (LP: #1886531) fix for missing /etc/fstab file path thx rharper

-

16:59 <ubot5> Launchpad bug 1886531 in cloud-init "cloud-init status broken in groovy lxd containers" [Medium,Fix committed] https://launchpad.net/bugs/1886531

-

17:00 <blackboxsw> and thanks paride for fixing our CI tests for lxd-based targets

-

17:01 <blackboxsw> I think that about wraps recent-changes.

-

17:01 <blackboxsw> #topic In-progress Development

-

17:02 <blackboxsw> I was hoping today we'd be able to finally say cloud-init 20.2 has published and released to Ubuntu Xenial. Bionic, Eoan and Focal. All testing is complete, we have unblocked any of this process on our side and we are awaiting an SRU team representative to review and release the bits into Ubuntu proper.

-

17:03 <blackboxsw> We pinged yesterday and a few hour ago again to get this SRU reviewed and released. Expectation is that it will be released to all Ubuntu series today/tonight, so I'd expect that cloud images see that update in the next day or two.

-

17:04 <blackboxsw> for those watching at home, the folowing bug will be closed as fix-released once cloud-init SRU is published.

-

17:04 <blackboxsw> #link https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018

-

17:04 <ubot5> Ubuntu bug 1881018 in cloud-init (Ubuntu) "sru cloud-init (19.4.33 to 20.2-45) Xenial, Bionic, Eoan and Focal" [Undecided,In progress]

-

17:06 <blackboxsw> for context, this was a beast of an SRU (as upstream waited too long (~6 months) between to get the SRUs, which involved more verification and complexity. We will make sure to avoid some of this complexity in the future by more frequent SRUs and more requests for community validation I expect.

-

17:07 <blackboxsw> Also, expect that when this SRU is published, and email will be sent to cloud-init@lists.launchpad.net and a discourse post as well as a "community-notice:" banned comment

-

17:08 <blackboxsw> #topic Community Charter

-

17:08 <blackboxsw> Community driven development is what helps keep cloud-init active, so that you all for your contributions ( PR reviews, bugs, PR development, discussion etc).

-

17:09 <blackboxsw> we have a number of general goals we continue to work toward:

-

17:10 <blackboxsw> - json schema coverage of cloudinit.config.cc_* modules for better error reporting on malformed user-data

-

17:10 <blackboxsw> - datasource documentation updates and content creation needs

-

17:10 <blackboxsw> - cloudinit.net refactor into distro-specific networking subclasses cloudinit.distros.networking

-

17:11 <blackboxsw> Bugs associated with that work are available for anyone to own

-

17:11 <blackboxsw> #link k https://bugs.launchpad.net/cloud-init/?field.tag=bitesize

-

17:11 <blackboxsw> #link https://bugs.launchpad.net/cloud-init/+bugs?field.tag=net-refactor

-

17:11 <blackboxsw> And details docs on existing refactor are available here

-

17:12 <blackboxsw> #link https://cloudinit.readthedocs.io/en/latest/topics/hacking.html#ongoing-refactors

-

17:13 <blackboxsw> If anyone would like to be involved more than they currently are, please feel free to contact us here in IRC #cloud-init on Freenode or on the mailing list cloud-init@lists.launchpad.net and we can see how best we can get you "set up"

-

17:13 <blackboxsw> #topic Office Hours (next ~30 mins)

-

17:13 <blackboxsw> This 'section' of the meeting is a time where a couple of upstream devs will be available in channel for any discussions, questions, bug work or PR reviews.

-

17:14 <blackboxsw> any topics, bugs, PRs or concerns or rotten fruit to throw are all welcome :). In the absence of dicussion, cloud-init PR reviews are prioritized

-

17:18 <blackboxsw> Odd_Bloke: can I merge the following as your squashmerge commit message for PR https://github.com/canonical/cloud-init/pull/466 https://paste.ubuntu.com/p/ZRdq4bYWG7/ I think it fixed LP: #1884626

-

17:18 <ubot5> Launchpad bug 1884626 in cloud-init "cloudinit.net refactor: wait_for_physdevs" [Low,In progress] https://launchpad.net/bugs/1884626

-

17:31 <Odd_Bloke> blackboxsw: You cannot (because I just did ;).

-

17:31 <blackboxsw> :sad trombone:

-

17:43 <Odd_Bloke> I just reran the RTD doc build and it passed this time (for anyone else who just got that failure email).

-

17:50 <blackboxsw> Ok I think that about wraps the status meeting

-

17:50 <blackboxsw> thanks for tuning in folks

-

17:50 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2020-07-28.html b/status-2020-07-28.html deleted file mode 100644 index f4be2e5..0000000 --- a/status-2020-07-28.html +++ /dev/null @@ -1,229 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Tue 28 July 2020 in status-meeting-minutes - - • 3 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-07-14.html#status-2020-07-14

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:58.

-

Recent Changes

-

The discussion about "Recent Changes" started at 17:00.

- -

In-progress Development

-

The discussion about "In-progress Development" started at 17:05.

-

Community Charter

-

The discussion about "Community Charter" started at 17:11.

-

Office Hours (next ~30 mins)

-

The discussion about "Office Hours (next ~30 mins)" started at 17:15.

-

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw_ (38)
  • -
  • meetingology (4)
  • -
  • rharper (0)
  • -
  • Odd_Bloke (0)
  • -
  • smoser (0)
  • -
-

Full Log

-

16:55 <blackboxsw_> #startmeeting cloud-init status meeting

-

16:55 <meetingology> Meeting started Tue Jul 28 16:55:17 2020 UTC. The chair is blackboxsw_. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:55 <meetingology>

-

16:55 <meetingology> Available commands: action commands idea info link nick

-

16:56 <blackboxsw_> community notice: time for another bi-weekly (or semi-monthly if you prefer) cloud-init community status meeting

-

16:56 <blackboxsw_> #chair Odd_Bloke smoser rharper

-

16:56 <meetingology> Current chairs: Odd_Bloke blackboxsw_ rharper smoser

-

16:57 <blackboxsw_> Hello folks, cloud-init community status roundup. We gather here in this IRC channel every 2 weeks to discuss current development tasks and progress on cloud-init.

-

16:57 <blackboxsw_> All questions. side-conversations and interruptions are welcome

-

16:58 <blackboxsw_> Last meeting minutes live here

-

16:58 <blackboxsw_> #link https://cloud-init.github.io/status-2020-07-14.html#status-2020-07-14

-

16:58 <blackboxsw_> he topics we'll cover today: Previous Actions, Recent Changes, In-progress Development, Community Charter, Office Hours (~30 mins).

-

16:58 <blackboxsw_> #topic Previous Actions

-

16:58 <blackboxsw_> None found in meeting minutes from last session.

-

16:59 * blackboxsw_ sets the topic for next meeting.

-

16:59 <blackboxsw_> +2 weeks from now

-

16:59 <blackboxsw_> August 11th 16:15 UTC

-

17:00 <blackboxsw_> #topic Recent Changes

-

17:00 <blackboxsw_> The following commits have been landed on master of upstream branch since last meeting: found via git log --since 2020-07-14

-

17:01 <blackboxsw_> #link https://paste.ubuntu.com/p/RjZcwtk6Hd/

-

17:02 <blackboxsw_> features of note:

-

17:02 <blackboxsw_> - azure: avoid bouncing hostname if set hostname fails

-

17:03 <blackboxsw_> - vmware: new defaults for post customization script overrides on vCloud

-

17:04 <blackboxsw_> - azure ValueError raised if JsonDecodeErrors is not available when parsing metadata

-

17:05 <blackboxsw_> Thanks Goneri otubo anhVo and dermotbradley for community contributions this round

-

17:05 <blackboxsw_> #topic In-progress Development

-

17:09 <blackboxsw_> Current projects for cloud-init are leading us to additional features:

-

17:10 <blackboxsw_> - network device hot plug support for cloud-init post-boot

-

17:10 <blackboxsw_> - better integration testing on other clouds, Oracle support

-

17:11 <blackboxsw_> - extended json schema validation and publishing full static schema versions for external tools

-

17:11 <blackboxsw_> #topic Community Charter

-

17:12 <blackboxsw_> The following topics are still topics for ongoing community development:

-

17:13 <blackboxsw_> - JSON schema extensions to validate user-data before instance launch: https://bugs.launchpad.net/cloud-init/?field.tag=bitesize

-

17:13 <blackboxsw_> - Datasource documentation and updates

-

17:14 <blackboxsw_> - cloudinit.net refactor into distro-specific networking subclasses cloudinit.distros.networking: https://bugs.launchpad.net/cloud-init/+bugs?field.tag=net-refactor

-

17:15 <blackboxsw_> As always: thank you all for bug contributions, PR submissions, triage and discussion participation.

-

17:15 <blackboxsw_> If anyone would like to be involved more than they currently are, please feel free to contact us here in IRC #cloud-init on Freenode or on the mailing list cloud-init@lists.launchpad.net and we can see how best we can get you "set up"

-

17:15 <blackboxsw_> #topic Office Hours (next ~30 mins)

-

17:17 <blackboxsw_> This time of the meeting is really just an open door for any discussions, concerns, bugs, questions or general prodding of upstream devs to make sure existing development work is unblocked where possible.

-

17:17 <blackboxsw_> In the absence of discussions, review of existing PRs is addressed.

-

17:56 <blackboxsw_> Thanks for tuning in folks. have a good one!

-

17:56 <blackboxsw_> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2020-08-25.html b/status-2020-08-25.html deleted file mode 100644 index 7353379..0000000 --- a/status-2020-08-25.html +++ /dev/null @@ -1,263 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Tue 25 August 2020 in status-meeting-minutes - - • 6 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:27.

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:27.

- -

In-progress Development

-

The discussion about "In-progress Development" started at 16:35.

- -

Community Charter

-

The discussion about "Community Charter" started at 16:40.

-

#cloud-init pull-requests https://git.io/JeVed | Meeting minutes: https://goo.gl/mrHdaj | Next status meeting Sep 8 16:15 UTC | 20.2 (Apr 26) | 20.3 (estimated Aug 19th) https://bugs.launchpad.net/cloud-init/+filebug

-

The discussion about "#cloud-init pull-requests https://git.io/JeVed | Meeting minutes: https://goo.gl/mrHdaj | Next status meeting Sep 8 16:15 UTC | 20.2 (Apr 26) | 20.3 (estimated Aug 19th) https://bugs.launchpad.net/cloud-init/+filebug" started at 16:48.

-
    -
  • ACTION: bbsw add workitem to SRU release process to announce to mailinglist estimated next SRU timeframe
  • -
-

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw_ (58)
  • -
  • meetingology (5)
  • -
  • AnhVoMSFT (4)
  • -
  • falcojr (1)
  • -
  • smoser (0)
  • -
  • lucasmoura (0)
  • -
  • rharper (0)
  • -
-

Full Log

-

16:24 <blackboxsw_> #startmeeting cloud-init status meeting

-

16:24 <meetingology> Meeting started Tue Aug 25 16:24:27 2020 UTC. The chair is blackboxsw_. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:24 <meetingology>

-

16:24 <meetingology> Available commands: action commands idea info link nick

-

16:24 <blackboxsw_> #chair smoser rharper falcojr lucasmoura

-

16:24 <meetingology> Current chairs: blackboxsw_ falcojr lucasmoura rharper smoser

-

16:25 <blackboxsw_> hey folks, welcome to another cloud-init bi-weekly (or bi-monthly) community status meeting

-

16:25 <blackboxsw_> or semi-monthly

-

16:26 <blackboxsw_> ... anyhow. We use this platform/channel to discuss latest and greatest cloud-init, as well as ensuring that there are a couple of upstream developers present to field questions or discussion as needed.

-

16:26 <blackboxsw_> We gather here in this IRC channel every 2 weeks to discuss current development tasks and progress on cloud-init. All questions and side-conversations welcome

-

16:26 <blackboxsw_> we keep our meeting minutes from previous meetings here:

-

16:27 <blackboxsw_> #link https://cloud-init.github.io

-

16:27 <blackboxsw_> The topics we'll cover today: Previous Actions, Recent Changes, In-progress Development, Community Charter, Office Hours (~30 mins).

-

16:27 <blackboxsw_> #topic Previous Actions

-

16:27 <blackboxsw_> Looks like no carryover actions from last meeting

-

16:27 <blackboxsw_> #topic Recent Changes

-

16:30 <blackboxsw_> The following changes have landed in tip of master since last meeting (08/14/20).

-

16:30 <blackboxsw_> found via git log --since 2020-08-014

-

16:30 <blackboxsw_> #link https://paste.ubuntu.com/p/h2qxwKwvFw/

-

16:31 <blackboxsw_> things to note. we JUST cut 20.3 upstream release as of 20 seconds ago. Thanks a bunch James(falcojr) for getting the Azure timeout pr up to close out this upstream release.

-

16:31 <blackboxsw_> and thanks smoser, rharper and meena for all the reviews and work here.

-

16:34 <blackboxsw_> in the last couple weeks we got fixes to reduce boot timeouts for certain azure accelerated network instances, fix oracle datasource retries, handle compressed user-data on juju deployed machines in 'cloud-init query', and early boot dhclient will not attempt to run outside of the /var/tmp sandbox directory if that directory is marked no-exec

-

16:34 <blackboxsw_> thanks otubo for that noexec branch

-

16:35 <blackboxsw_> #topic In-progress Development

-

16:36 <blackboxsw_> So thanks all for the 20.3 upstream release. We will be tagging that release and pushing that tag to master just after this meeting

-

16:36 <blackboxsw_> falcojr: is our release lead for this upstream release and SRU so he'll be working through the release process work items. Thanks falcojr.

-

16:37 <blackboxsw_> -next step on the release process is to publish to Ubuntu Groovy (20.10) and then queue up a -proposed cloud-init SRU upload into xenial, bionic and focal.

-

16:37 <blackboxsw_> we will then begin the SRU testing (which we hope to keep at around ~7days)

-

16:38 <blackboxsw_> as smoser mentioned earlier. cloud-init has to follow this process to update cloud-init in stable Ubuntu releases

-

16:38 <blackboxsw_> #link https://wiki.ubuntu.com/CloudinitUpdates

-

16:39 <blackboxsw_> An email will be sent to the cloud-init mailinglist notifying the community about the SRU under test in the event that folks have spare cycles to pitch in on some of the verification effort

-

16:40 <blackboxsw_> also "in-progress" paride is cleaning up a bunch of automated CI-related failures and lint issues in cloud-init, so expect some branches against cloud-init on that front as well

-

16:40 <blackboxsw_> #topic Community Charter

-

16:41 <blackboxsw_> The following topics are still topics for ongoing community development anyone new to cloud-init, or with a bit of time could easily grab one of these bitesized tasks:

-

16:41 <blackboxsw_> JSON schema extensions to validate user-data before instance launch: https://bugs.launchpad.net/cloud-init/?field.tag=bitesize

-

16:41 <blackboxsw_> - Datasource documentation and updates

-

16:41 <blackboxsw_> - cloudinit.net refactor into distro-specific networking subclasses cloudinit.distros.networking: https://bugs.launchpad.net/cloud-init/+bugs?field.tag=net-refactor

-

16:41 <blackboxsw_> As always: thank you all for bug contributions, PR submissions, triage and discussion participation.

-

16:41 <blackboxsw_> If anyone would like to be involved more than they currently are, please feel free to contact us here in IRC #cloud-init on Freenode or on the mailing list cloud-init@lists.launchpad.net and we can see how best we can get you "set up"

-

16:42 <blackboxsw_> #topic Office Hours (next ~30 mins)

-

16:42 <blackboxsw_> his time of the meeting is really just an open door for any discussions, concerns, bugs, questions or general prodding of upstream devs to make sure existing development work is unblocked where possible.

-

16:42 <blackboxsw_> *This time

-

16:42 <blackboxsw_> while we're at it with meeting time.... I'll set the next cloud-init status meeting date in the topic of this IRC channel

-

16:42 <AnhVoMSFT> When do you anticipate the next SRU would be?

-

16:43 <AnhVoMSFT> (after 20.3)

-

16:44 <blackboxsw_> AnhVoMSFT: thanks for the question. I hope today for 20.3, I think 20.4 will likely align with the next Ubuntu release cycle (20.10) so, October, 2020

-

16:46 <blackboxsw_> as mentioned in passing earlier, we are looking at trying to create an upstream release of cloud-init when any significant feature set has landed in tip to make release verification easier (and hopefull include less sprawling sets of broad commit streams).

-

16:46 <blackboxsw_> this ultimately may translated to 4-5 releases per year

-

16:46 <blackboxsw_> I expect a frequency of `< 3 months

-

16:48 <blackboxsw_> #topic #cloud-init pull-requests https://git.io/JeVed | Meeting minutes: https://goo.gl/mrHdaj | Next status meeting Sep 8 16:15 UTC | 20.2 (Apr 26) | 20.3 (estimated Aug 19th) https://bugs.launchpad.net/cloud-init/+filebug

-

16:49 <blackboxsw_> next status meeting sept 8th, same time ^

-

16:49 <AnhVoMSFT> Thanks. There's some planned work for Azure's pre-provisioning v2 and will need some change in cloud-init. We're trying to get a sense of when cloud-init SRUs land so that we can communicate the timeline

-

16:52 <blackboxsw_> @AnhVoMSFT generally cadence has been ~3 months between SRUs, I think we'd like to see a slightly higher frequency than that because our last SRU was so costly. but I think expectation for this pass is likely 10/15/2020

-

16:53 <blackboxsw_> also, if we are looking to test features in Ubuntu Groovy 20.10 images, they don't require an SRU, so upload to that development release are possible any time (we could do that as frequently as weekly if need be)

-

16:56 <AnhVoMSFT> thanks for the clarification @blackboxsw_

-

16:57 <blackboxsw_> so as of today, I expect we'll have an SRU in October and likely something beginning of Jan

-

16:57 <blackboxsw_> I'll take an action for us to communicate via mailinglist the next estimated SRU once this SRU for 20.3 closes out

-

16:59 <blackboxsw_> #action bbsw add workitem to SRU release process to announce to mailinglist estimated next SRU timeframe

-

16:59 * meetingology bbsw add workitem to SRU release process to announce to mailinglist estimated next SRU timeframe

-

16:59 <blackboxsw_> and again we hope to have 20.3 SRU complete by next week

-

16:59 <blackboxsw_> complete, as in publish the 20.3 SRU for next week into Ubuntu xenial and later

-

17:00 <blackboxsw_> I expect today we publish tip of master (20.3) into Ubuntu Groovy (20.10) so expect to see it in your friendly neighborhood ubuntu cloud-images in the next day or two

-

17:04 <blackboxsw_> falcojr: I just annotated tag 20.3 and pushed to upstream

-

17:04 <blackboxsw_> so we have a signed tag

-

17:04 <blackboxsw_> falcojr: so next task is https://trello.com/c/KxShylli/14-upload-source-tarball-to-launchpad

-

17:05 <falcojr> Cool, I can jump on that

-

17:12 <blackboxsw_> ok I think we'll wrap up the status meeting. Thanks all for tuning in!

-

17:13 <blackboxsw_> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2020-09-08.html b/status-2020-09-08.html deleted file mode 100644 index 3bf4a28..0000000 --- a/status-2020-09-08.html +++ /dev/null @@ -1,246 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Tue 08 September 2020 in status-meeting-minutes - - • 5 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

LINK: https://cloud-init.github.io/status-2020-08-25.html#status-2020-08-25

-

Previous Actions

-

The discussion about "Previous Actions" started at 16:21.

-

Recent Changes

-

The discussion about "Recent Changes" started at 16:25.

- -

In-progress Development

-

The discussion about "In-progress Development" started at 16:46.

- -

Office Hours (next ~30 mins)

-

The discussion about "Office Hours (next ~30 mins)" started at 16:54.

-

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (51)
  • -
  • meetingology (3)
  • -
  • amansi26 (3)
  • -
  • ubot5 (2)
  • -
-

Full Log

-

16:18 <blackboxsw> #startmeeting cloud-init status meeting

-

16:18 <meetingology> Meeting started Tue Sep 8 16:18:47 2020 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

16:18 <meetingology>

-

16:18 <meetingology> Available commands: action commands idea info link nick

-

16:19 <blackboxsw> #chairs smoser Odd_Bloke rharper falcojr lucasmoura

-

16:19 <blackboxsw> hey folks. welcome to another public cloud-init status meeting

-

16:19 <blackboxsw> disclaimer: interruptions and side conversations are welcome

-

16:19 <blackboxsw> We use this platform/channel to discuss latest and greatest cloud-init, as well as ensuring that there are a couple of upstream developers present to field questions or discussion as needed.

-

16:20 <blackboxsw> We gather here in this IRC channel every 2 weeks to discuss current development tasks and progress on cloud-init.

-

16:20 <blackboxsw> Previous meeting minutes are here;

-

16:20 <blackboxsw> #link https://cloud-init.github.io/status-2020-08-25.html#status-2020-08-25

-

16:20 <blackboxsw> The topics we'll cover today: Previous Actions, Recent Changes, In-progress Development, Community Charter, Office Hours (~30 mins).

-

16:21 <blackboxsw> I expect today will be short as the entire Canonical team is involved in cloud-init SRU verification for Ubuntu at the moment

-

16:21 <blackboxsw> #topic Previous Actions

-

16:22 <blackboxsw> last meeting had an action item we needed to resolve

-

16:22 <blackboxsw> bbsw add workitem to SRU release process to announce to mailinglist estimated next SRU timeframe.

-

16:24 <blackboxsw> this item can be resolved as I've added the content requested to our email template which will be sent out once this SRU completes.

-

16:24 <blackboxsw> I see no other actions from last meeting

-

16:25 <blackboxsw> #topic Recent Changes

-

16:26 <blackboxsw> The following are upstream commits landed in cloud-init's master branch:

-

16:26 <blackboxsw> #link https://paste.ubuntu.com/p/NgqncRMG9c/

-

16:28 <blackboxsw> In the last couple of weeks we cut the upstream 20.3 release (thanks everyone for all the help there). Queued SRU uploads for ubuntu/xenial, bionic and focal release testing.

-

16:28 <amansi26> blackboxsw: metadata here will be the configdrive, if my understanding is right?

-

16:30 <blackboxsw> And added some goodness to systemd units and ordering (sort systemd cloud-init-local.service hv_kvp_daemon and systemd: add Before=shutdown.target when Conflicts=shutdown.target is

-

16:30 <blackboxsw> used )

-

16:30 <blackboxsw> thanks paride and robjo for those commits

-

16:30 <blackboxsw> amansi26: +1 you can see the metadata configured hostname from cloud-init query local-hostname I think

-

16:30 <blackboxsw> amansi26: +1 you can see the metadata configured hostname from cloud-init query local-hostname I think

-

16:30 <blackboxsw> amansi26: I was just starting to respond to your bug you linked too

-

16:31 <blackboxsw> I think preserve_hostname: false (which is cloud-init's default behavior ) means cloud-init will read that hostname from metadata and apply it to the system

-

16:31 <amansi26> Sure. there is another bug which I observed on a RHEL8 environment: https://bugs.launchpad.net/cloud-init/+bug/1894837

-

16:31 <ubot5> Ubuntu bug 1894837 in cloud-init "RHEL8 ipv4 IPs not getting set" [Undecided,New]

-

16:35 <blackboxsw> amansi26: sorry cloud-init query local_hostname (# not with a hyphen)

-

16:35 <blackboxsw> checking 2nd bug

-

16:38 <blackboxsw> so amansi26 you'd like the ability to override the iface_defaults on rhel systems for NM_CONTROLLED to set True instead of false for cloud-init interfaces?

-

16:40 <blackboxsw> generally if cloud-init is rendering network configuration on an instance, it tries to avoid using network manager by default. I think it's worth requesting logs on your bug

-

16:40 <blackboxsw> those cloud-init logs can be obtained using cloud-init collect-logs (which generates a tar.gz file in the current working directory). then attach that to the bug

-

16:41 <amansi26> yes, since I was reading the documentation for RHEL8 network configuration, I found that NM_CONTROLLED = yes should be there. but we are passing the value as No. Sure I will attach the logs to the defect

-

16:43 <blackboxsw> thanks amansi26 I responded on that bug too

-

16:46 <blackboxsw> Ok, per the meeting, that wraps #recent-changes topic I believe

-

16:46 <blackboxsw> #topic In-progress Development

-

16:48 <blackboxsw> Currently the Canonical team is working hard on SRU verification so we can release cloud-init v. 20.3 to Xenial, Bionic and Focal. It looks like we are done with most major cloud verification and walking through individual verification items.

-

16:50 <blackboxsw> I believe falcojr mentioned this morning we are about 5 of 30ish verification items complete.

-

16:50 <blackboxsw> we are continuing to work this verification as our top priority

-

16:50 <blackboxsw> folks interested should subscribe to updates on our SRU bug

-

16:51 <blackboxsw> #link https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1893064

-

16:51 <ubot5> Ubuntu bug 1893064 in cloud-init (Ubuntu) "sru cloud-init (20.2-45 to 20.3-2) Xenial, Bionic, and Focal" [Undecided,In progress]

-

16:53 <blackboxsw> that bug will transition to verification-complete once all verification is done

-

16:54 <blackboxsw> #topic Community Charter

-

16:54 <blackboxsw> The following topics are still topics for ongoing community development anyone new to cloud-init, or with a bit of time could easily grab one of these bitesized tasks:

-

16:54 <blackboxsw> JSON schema extensions to validate user-data before instance launch: https://bugs.launchpad.net/cloud-init/?field.tag=bitesize

-

16:54 <blackboxsw> - cloudinit.net refactor into distro-specific networking subclasses cloudinit.distros.networking: https://bugs.launchpad.net/cloud-init/+bugs?field.tag=net-refactor

-

16:54 <blackboxsw> If anyone would like to be involved more than they currently are, please feel free to contact us here in IRC #cloud-init on Freenode or on the mailing list cloud-init@lists.launchpad.net and we can see how best we can get you "set up"

-

16:54 <blackboxsw> #topic Office Hours (next ~30 mins)

-

16:55 <blackboxsw> this time of the meeting is really just an open door for any discussions, concerns, bugs, questions or general prodding of upstream devs to make sure existing development work is unblocked where possible.

-

16:55 <blackboxsw> in absence of discussions. We actually will be focused on SRU verification tasks today.

-

16:56 <blackboxsw> each of these verification logs and scripts are pushed as pull requests to https://github.com/cloud-init/ubuntu-sru/pulls

-

17:13 <blackboxsw> ok I think that about wraps today's session. Next meeting will be in two weeks, but we'll likely see you in channel earlier.

-

17:13 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2020-11-17.html b/status-2020-11-17.html deleted file mode 100644 index 2c1038e..0000000 --- a/status-2020-11-17.html +++ /dev/null @@ -1,268 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Tue 17 November 2020 in status-meeting-minutes - - • 6 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

LINK: https://discourse.ubuntu.com/t/cloud-init-statue-11-17-20/19391 - LINK: https://github.com/canonical/cloud-init/pull/655 i'd love this too get merged, so we don't have to carry the patch on ports - LINK: https://github.com/canonical/cloud-init/pull/655 - LINK: https://github.com/canonical/cloud-init/pull/647 - LINK: https://github.com/canonical/cloud-init/pull/588#pullrequestreview-529957360 - LINK: https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/sources/DataSourceAzure.py#L1325 - LINK: https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/config/cc_set_passwords.py#L163 - LINK: https://github.com/canonical/cloud-init/pull/663 - LINK: https://github.com/canonical/cloud-init/pull/659 - LINK: https://github.com/canonical/cloud-init/pulls?q=is%3Apr+is%3Aopen+label%3A%22release+20.4%22

-

Vote results

-

Done items

-
    -
  • (none)
  • -
-

People present (lines said)

-
    -
  • blackboxsw (48)
  • -
  • AnhVoMSFT (15)
  • -
  • rharper (7)
  • -
  • meena (6)
  • -
  • smoser (3)
  • -
  • meetingology (3)
  • -
  • Odd_Bloke (1)
  • -
-

Full Log

-

17:25 <blackboxsw> #startmeeting cloud-init status meeting && office hours

-

17:25 <meetingology> Meeting started Tue Nov 17 17:25:00 2020 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

-

17:25 <meetingology>

-

17:25 <meetingology> Available commands: action commands idea info link nick

-

17:25 <blackboxsw> community-notice: hi folks just starting up an our cloud-init satus update and office hours community meeting.

-

17:26 <blackboxsw> As of the cloud-init summit, we decided to try to host these primarily async in discourse to allow folks in other timezones to participate as available.

-

17:26 <blackboxsw> I've just finished posting a status update for cloud-init upstream to https://discourse.ubuntu.com/t/cloud-init-statue-11-17-20/19391

-

17:26 <blackboxsw> #link https://discourse.ubuntu.com/t/cloud-init-statue-11-17-20/19391

-

17:27 <blackboxsw> #chairs rharper smoser Odd_Bloke

-

17:28 <rharper> o/

-

17:28 <blackboxsw> Generally I think this status meeting can be used as a platform for communication and discussion with the community.

-

17:29 <blackboxsw> for this week, as brought up by a few folks in the community, is that we are trying to define a "go" date for the next upstream cloud-init release 20.4.

-

17:30 <blackboxsw> The hope is to target this Friday Nov 20th. as a deadline for requesting specific PRs and reviews that are needed to get features or fixes included in this 20.4 release.

-

17:31 <meena> so, i just responded to falcojr's email

-

17:32 <blackboxsw> The goal of this date, from an Ubuntu standpoint, is also to be able to SRU (stable release update) and publish this functionality back to Xenial, Bionic and Focal before the end of the calendar year

-

17:32 <meena> https://github.com/canonical/cloud-init/pull/655 i'd love this too get merged, so we don't have to carry the patch on ports

-

17:33 <blackboxsw> thanks meena there https://github.com/canonical/cloud-init/pull/655 ahh I'm too late

-

17:34 <blackboxsw> So, for those who happen to be on this channel now, let's add links to the meeting log and I'll make sure they are also reflected on the discourse post and PRs that need review assessment and hopefully landing before upstream release cut.

-

17:34 <blackboxsw> #link https://github.com/canonical/cloud-init/pull/655

-

17:34 <blackboxsw> rharper or smoser are there any concerns with existing PRs that you are aware of that should be destined for this 20.4 release?

-

17:35 <meena> rharper, i'd also love your historic knowledge on https://github.com/canonical/cloud-init/pull/588 but that can wait until after the release

-

17:36 <blackboxsw> rharper: I wanted to put a solid review on the cached ds handling today/tomorrow

-

17:36 <blackboxsw> #link https://github.com/canonical/cloud-init/pull/647

-

17:36 <blackboxsw> I've looked it over a couple times, but wanted to but some investment in the review myself today.

-

17:37 <blackboxsw> AnhVoMSFT: welcome and thanks for peeking in to checkup. If your team also have any hopes for PRs you can pitch us here, discourse or email.

-

17:38 <AnhVoMSFT> I have a quick question on the cc_set_passwords. I'm still looking through the code but if anyone knows this one well and can point me to the right place to look it would be appreciated

-

17:39 <AnhVoMSFT> it seems like if we create an image that previously was deployed with password ABC, but during image preparation we don't delete that user, then when we deploy a VM with that image and specifying a new password DEF, it isn't applied. I.e., the user will still have password ABC

-

17:39 <rharper> blackboxsw: I'm not aware of anything critical PR wise; maybe the networking_cls bits; but not sure if that's ready;

-

17:40 <meena> from my understanding, that needs to get in

-

17:40 <blackboxsw> AnhVoMSFT: poking around now on that

-

17:41 <rharper> meena: yes; that makes sense; just hadn't looked at the current state of the PR since I last commented;

-

17:42 <rharper> meena: re: 588 (genreate_fallback_config); did you have a specific question you wanted some background on?

-

17:43 <meena> rharper, search for your name

-

17:44 <rharper> hidden under a "Load more Items"

-

17:44 <rharper> I'll respond

-

17:44 <blackboxsw> so instance-id should have changed on the newly deployed vm, so cc_set_passwords should get retriggered due to https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_set_passwords.py#L49 (the default frequency for cc modules). AnhVoMSFT: what the userdata password field you are using? top-level password or chpasswd?

-

17:45 <AnhVoMSFT> this is the user password passed in from ovf

-

17:45 <blackboxsw> as that'd be different code paths I think

-

17:45 <meena> https://github.com/canonical/cloud-init/pull/588#pullrequestreview-529957360

-

17:46 <AnhVoMSFT> in a newly created instance without the existing user, I could see the password getting created during the initial useradd call when the user is created

-

17:47 <AnhVoMSFT> however, if the user existed, that code path isn't invoked. There's some code in cc_set_passwords to change the password for existing user, but I'm unsure when it's invoked (or why it's not invoked in the case of azure)

-

17:48 <blackboxsw> AnhVoMSFT: could you provide a paste of redacted userdata from that instance via sudo cloud-init query userdata... redacting the specific passwords ?

-

17:49 <blackboxsw> yeah I would have expected a log.debug("Changing password for %s:", users) log

-

17:53 <AnhVoMSFT> let me run the query

-

17:53 <AnhVoMSFT> there's nothing returned (since there's no userdata)

-

17:54 <AnhVoMSFT> looks like the ds Azure is adding the user/password information retrieved from OVF to cfg['defuser']

-

18:00 <AnhVoMSFT> https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/sources/DataSourceAzure.py#L1325

-

18:00 <AnhVoMSFT> if I'm reading the code of cc_set_password correctly we will need to add cfg['password'] as well if we want the defuser's password to be changed?

-

18:01 <Odd_Bloke> rharper: We are treating the networking_cls PR as critical, and AFA(I/we)K it's pretty much ready to land.

-

18:02 <rharper> Odd_Bloke: ok, makes sense

-

18:06 <smoser> blackboxsw: i dont have anything critical.

-

18:06 <blackboxsw> AnhVoMSFT: so normalize_users_groups is what pulls the default_user configuration out of /etc/cloud/cloud.cfg(.d/*)

-

18:06 <blackboxsw> https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/config/cc_set_passwords.py#L163

-

18:07 <blackboxsw> that ug_util.extract_default is what should be seeing the passwords set/changed

-

18:07 <smoser>

-

18:08 <smoser> #669 looks reasonable.

-

18:08 <blackboxsw> yet interestingly. password referenced there is only set from the top-level "password" value https://github.com/canonical/cloud-init/blob/eeef783b0322d99840f39a58de052772afefe822/cloudinit/config/cc_set_passwords.py#L143

-

18:08 <blackboxsw> thanks smoser for that

-

18:08 <blackboxsw> #link https://github.com/canonical/cloud-init/pull/663

-

18:12 <AnhVoMSFT> let me test it out real quick by setting the cfg['password'] key in the ds azure

-

18:12 <blackboxsw> AnhVoMSFT: so, I may be mistaken but if a password key is set on the default_user in system_info (which is what it looks like azure does), then that default password is only used if there is no top-level "password" key provided in merged cloud-config, then and the default_user specific password key is ignored

-

18:12 <blackboxsw> +1 AnhVoMSFT

-

18:13 <AnhVoMSFT> yep that worked

-

18:13 <AnhVoMSFT> it's a one liner change, I'll submit a PR asap

-

18:14 <blackboxsw> AnhVoMSFT: good. ok, I wonder if this ever worked (having the password key hung under default_user scope?)

-

18:14 <blackboxsw> as in, I wonder if there was a regression introduced with some of the is_FreeBSD restructuring

-

18:15 <AnhVoMSFT> I don't think so. customer reported this issue in cloud-init 18.5 and I repro-ed it in master

-

18:15 <blackboxsw> ok, ok. good thanks for that context

-

18:15 <blackboxsw> and checking the recent BSD change it looking completely unrelated

-

18:17 <blackboxsw> ok AnhVoMSFT when the PR is submitted. let's get that queued for this upstream 20.4 if we can

-

18:18 <blackboxsw> do folks have an opinion on whether it helps to add a custom label to active PRs that we intend to land before upstream release like 'upstream-blocker' or 'upstream-release'?

-

18:19 <blackboxsw> just for more public tracking/transparency. not sure if that's helpful or just needless process?

-

18:19 <blackboxsw> do folks have an opinion on whether it helps to add a custom label to active PRs that we intend to land before upstream release like 'upstream-blocker' or 'upstream-release'?

-

18:23 <AnhVoMSFT> I think that would be helpful, yes

-

18:25 <blackboxsw> ok, let's try it out. let's try specific 'release 20.4' and see how that feels to folks. easy enough to drop if it doesn't improve communication

-

18:30 <blackboxsw> also added pickling upgrade test validation PR

-

18:30 <blackboxsw> #link https://github.com/canonical/cloud-init/pull/659

-

18:31 <blackboxsw> ok, last call for cloud-init status / office hours. Any other takers for discussion at the moment? If not I'll close out the meeting in a few mins and publish minutes.

-

18:33 <blackboxsw> my plan is still to publish to cloud-init.github.io status meetings and link it from the primary post at https://discourse.ubuntu.com/t/cloud-init-status-11-17-20/19391

-

18:34 <blackboxsw> the following will list prs we hope to work toward landing this week

-

18:34 <blackboxsw> #link https://github.com/canonical/cloud-init/pulls?q=is%3Apr+is%3Aopen+label%3A%22release+20.4%22

-

18:35 <blackboxsw> thanks again for the discussion and suggestions folks. Have a good one!

-

18:35 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2021-02-23.html b/status-2021-02-23.html deleted file mode 100644 index cc2ed8f..0000000 --- a/status-2021-02-23.html +++ /dev/null @@ -1,190 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Tue 23 February 2021 in status-meeting-minutes - - • 2 min read -

-
- - -
-

Meeting information

- -

Meeting summary

- -

People present (lines said)

-
    -
  • blackboxsw (17)
  • -
  • meetingology (2)
  • -
  • Odd_Bloke (2)
  • -
-

Full log

-

17:18 <blackboxsw> #startmeeting cloud-init office hours

-

17:18 <meetingology> Meeting started at 17:18:36 UTC. The chair is blackboxsw. Information about MeetBot at https://wiki.ubuntu.com/meetingology

-

17:18 <meetingology> Available commands: action, commands, idea, info, link, nick

-

17:18 <Odd_Bloke> o/

-

17:19 <blackboxsw> community notice: hi folks. We are resuming our much anticipated office hours. Every two weeks at this time. The IRC topic will host our upcoming expected office-hours meeting time.

-

17:19 <blackboxsw> \o Odd_Bloke thx

-

17:19 <blackboxsw> t

-

17:20 <blackboxsw> This meeting will provide an opportunity with multiple upstream cloud-init devs available to discuss bugs, features, ongoing development or answer your existential questions :)

-

17:20 <blackboxsw> We hope to continue this meeting with regular cadence (and calendar reminders) to make sure we hold this time and frequency.

-

17:22 <blackboxsw> I'll send an email to the mailing list (again) announcing this cadence. Again this time if for any discussions, questions or dev/feature topics that folks would like to gab about.

-

17:23 <blackboxsw> We just published a high-level update of what's been happening in the cloud-init space, https://discourse.ubuntu.com/t/cloud-init-status-02-23-2021/21069.

-

17:25 <blackboxsw> As seen on the mailinglist, Odd_Bloke and falcojr have been trying to tidy up things for the upstream 21.1 timed release. Thanks both of you for driving this work. I believe 21.1 landed, was uploaded to Ubuntu 21.04 (Hirsute).

-

17:26 <blackboxsw> We are also planning on SRUing(StableReleaseUpdate - Ubuntu-speak for uploading) 21.1 plus a feature fix for OVS support into Xenial, Bionic, Focal and Groovy within the next week or two.

-

17:26 <Odd_Bloke> Yep, I'm currently working through the release announcement process.

-

17:30 <blackboxsw> great Dan. So, TLDR is watch the mailinglist cloud-init@lists.launchpad.net and discourse https://discourse.ubuntu.com/c/server/cloud-init for announcements and updates

-

17:30 <blackboxsw> #link https://discourse.ubuntu.com/c/server/cloud-init

-

17:58 <blackboxsw> I think we've about rounded out the office-hours. (I spent that time walking through a sopel-irc bot setup to test out some of the features to see if we can't add some structure to this office-hours engagement (and frankly release announcements too )

-

17:59 <blackboxsw> Let's set that next office hours for +2 weeks-45 mins from now

-

18:00 <blackboxsw> hopefully by then we have an automated announcer kicking off the notification.

-

18:00 <blackboxsw> Thanks all!

-

18:00 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.4.0 (https://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2021-03-09.html b/status-2021-03-09.html deleted file mode 100644 index 00afe08..0000000 --- a/status-2021-03-09.html +++ /dev/null @@ -1,206 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Tue 09 March 2021 in status-meeting-minutes - - • 3 min read -

-
- - -
-

Meeting information

- -

Meeting summary

- -

People present (lines said)

-
    -
  • blackboxsw (14)
  • -
  • falcojr (8)
  • -
  • beantaxi (7)
  • -
  • meetingology (3)
  • -
  • Odd_Bloke (3)
  • -
-

Full log

-

17:19 <blackboxsw> #startmeeting cloud-init bi-weekly office-hours

-

17:19 <meetingology> Meeting started at 17:19:08 UTC. The chair is blackboxsw. Information about MeetBot at https://wiki.ubuntu.com/meetingology

-

17:19 <meetingology> Available commands: action, commands, idea, info, link, nick

-

17:19 <blackboxsw> #char Odd_Bloke falcojr

-

17:19 <blackboxsw> #chair Odd_Bloke falcojr

-

17:19 <meetingology> Current chairs: Odd_Bloke, blackboxsw, falcojr

-

17:20 <blackboxsw> hi cloud-init, sorry for the confusion on the UTC time that I posted in the topic. I had incorrectly set 15:15 UTC instead of 17:15.

-

17:20 <blackboxsw> welcome to the bi-weekly cloud-init office hours

-

17:21 <blackboxsw> This cloud-init status meeting has moved to a more asynchronous posting of high-level happenings in cloud-init to discourse to support timezone differences for all cloud-init developers.

-

17:23 <blackboxsw> We plan on continuing to host these office hours to provide a means for quick communication, questions and discussions with a couple of upstream developers present to help facilite any questions or discussions of interest to folks.

-

17:23 <blackboxsw> For reference, here are the high-level "happenings" in cloud-init upstream over the last two weeks.

-

17:23 <Odd_Bloke> o/

-

17:23 <blackboxsw> #link https://discourse.ubuntu.com/t/cloud-init-status-03-09-2021/21309

-

17:26 <blackboxsw> As of last office-hours I belive upstream had just cut the first 21.1 release in the tip of cloud-init. Canonical will be starting the SRU process this week I believe to publish the 21.1 release (plus a couple of extra fixes which just landed in tip) into Ubuntu Xenial, Bionic, Focal, Groovy and Hirsute.

-

17:41 <beantaxi> Odd_Bloke: I tried your command and it was helpful. It complained about a missing ssh key, so I shrugged, tried ssh-keygen -t rsa and reran the test, and it passed. I've kicked off a run of all the tests, which I assume will take a bit.

-

17:55 <Odd_Bloke> beantaxi: Great, thanks for the update! A full run in LXD containers takes ~12mins locally (though I'm probably running on beefier hardware than you're paying EC2 for so YMMV :p).

-

17:55 <Odd_Bloke> beantaxi: Once you had the output, was it clear that the missing SSH key was the issue?

-

17:55 <blackboxsw> setting the appropriate time for next office hours

-

17:56 <blackboxsw> setting the appropriate time for next office hours Mar 23 17:15 UTC

-

17:57 <beantaxi> ERROR tests/integration_tests/modules/test_runcmd.py::TestRuncmd::test_runcmd - FileNotFoundError: [Errno 2] No such file or directory: '/home/ubuntu/.ssh/id_rsa.pub'

-

17:57 <beantaxi> That was the error message

-

17:59 <falcojr> tests require an ssh keypair. It'll use your user one by default or you can specify one manually in the integration settings config

-

17:59 <falcojr> do an ssh-keygen

-

17:59 <beantaxi> The full test failed with 7 failures: https://paste.ubuntu.com/p/hcYN7ZDvbs/

-

18:00 <beantaxi> falcojr: Thanks ... I was just showing Odd_Bloke the error message I got before running ssh-keygen, which did indeed solve most of my issues

-

18:01 <beantaxi> falcojr: Also, this is just me running the existing integration tests on an EC2 instance. Without any of my changes

-

18:01 <falcojr> not sure the cause of that first one, but the rest are for code not in ubuntu images yet

-

18:03 <falcojr> the version of cloud_init to use is specified by the CLOUD_INIT_SOURCE variable (integration_settings.py...copy this to user_settings.py to easily override defaults)

-

18:03 <falcojr> it defaults to NONE which means use whatever image has been released on this platform

-

18:04 <falcojr> to test non-released code, changing it to IN_PLACE (only works on LXD) should work

-

18:08 <falcojr> you can also set it to ppa:cloud-init-dev/daily , but that won't contain any changes that you're trying to test

-

18:18 <beantaxi> falcojr: Copying integration_settings.py to user_settings.py and setting CLOUD_INIT_SOURCE=IN_PLACE made all the test_keys_to_console errors clean. There's still that simple_streams error. Do I just need to add a PPA for simplestreams? It looks like requires a file in /etc/apt/sources.list.d, but mine is empty

-

18:23 <falcojr> Not sure off the top of my head. Did you pip install the integration_requirements.txt?

-

18:38 * blackboxsw thinks I should about wrap up office hours. Thanks falcojr Odd_Bloke and beantaxi for the discussion there

-

18:38 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.4.0 (https://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2021-03-23.html b/status-2021-03-23.html deleted file mode 100644 index 2e17568..0000000 --- a/status-2021-03-23.html +++ /dev/null @@ -1,198 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Tue 23 March 2021 in status-meeting-minutes - - • 2 min read -

-
- - -
-

Meeting information

- -

Meeting summary

- -

People present (lines said)

-
    -
  • blackboxsw (11)
  • -
  • Odd_Bloke (10)
  • -
  • meetingology (3)
  • -
  • ubot5 (1)
  • -
  • falcojr (0)
  • -
-

Full log

-

17:22 <Odd_Bloke> #startmeeting cloud-init bi-weekly office-hours

-

17:22 <meetingology> Meeting started at 17:22:08 UTC. The chair is Odd_Bloke. Information about MeetBot at https://wiki.ubuntu.com/meetingology

-

17:22 <meetingology> Available commands: action, commands, idea, info, link, nick

-

17:22 <Odd_Bloke> #chair blackboxsw falcojr

-

17:22 <meetingology> Current chairs: Odd_Bloke, blackboxsw, falcojr

-

17:22 <blackboxsw> \0 woot thanks Odd_Bloke

-

17:23 <Odd_Bloke> Hey folks, the cloud-init committers will be around for the next while, to answer any questions or have any discussions you're interested in having.

-

17:23 <Odd_Bloke> blackboxsw posted a status update to Discourse earlier today.

-

17:23 <blackboxsw> Here's the discourse post for reference on recent cloud-init events

-

17:23 <Odd_Bloke> #link https://discourse.ubuntu.com/t/cloud-init-status-03-23-2021/21490

-

17:23 <blackboxsw> #link https://discourse.ubuntu.com/t/cloud-init-status-03-23-2021/21490

-

17:23 <blackboxsw> thanks Odd_Bloke

-

17:23 <Odd_Bloke> Haha

-

17:23 <Odd_Bloke> Please read it twice.

-

17:24 <blackboxsw> and correct any clerical errors

-

17:25 <blackboxsw> one topic of interested that hamalq brought up yesterday was the "feature" of RedHat and CentOS that automatically prefers fqdn over hostname in #cloud-config per this bug

-

17:25 <blackboxsw> #link https://bugs.launchpad.net/cloud-init/+bug/1724414

-

17:25 <ubot5> Ubuntu bug 1724414 in cloud-init "rhel distro selects FQDN as hostname" [Low,Won't fix]

-

17:26 <blackboxsw> I mentioned we'd bring it up to reflect our opinion on this behavior today after a discussion

-

17:28 <blackboxsw> I think the upstream stance on RedHat and CentOS is that this default behavior on RedHat/CentOS has been in play for a long time and changing that default behavior would be asking to cause problems for the majority of users who may rely on this behavior during system launch.

-

17:28 <blackboxsw> Odd_Bloke: falcojr did we say in this case we'd prefer a new bug which better describes the desired use-case and how current cloud-init doesn't allow for that use-case?

-

17:30 <blackboxsw> that's all the content/discussion I had. I know I needed to get otubo a review today on his resize lvm partition branch https://github.com/canonical/cloud-init/pull/721 as my stale review was blocking that.

-

17:31 <Odd_Bloke> We've closed out that bug as Won't Fix; we'd like folks who consider themselves affected by that bug to file a new one which describes their specific problem with the current situation: we can then work to support those requirements.

-

18:24 <Odd_Bloke> OK, sounds like there's not much to chat about; thanks to any lurkers. :)

-

18:24 <Odd_Bloke> #endmeeting

-

Generated by MeetBot 0.4.0 (https://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2021-04-06.html b/status-2021-04-06.html deleted file mode 100644 index e831296..0000000 --- a/status-2021-04-06.html +++ /dev/null @@ -1,187 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Tue 06 April 2021 in status-meeting-minutes - - • 2 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

People present (lines said)

-
    -
  • hamalq (7)
  • -
  • blackboxsw (6)
  • -
  • falcojr (3)
  • -
  • meetingology (2)
  • -
  • Odd_Bloke (1)
  • -
-

Full log

-

16:20 <blackboxsw> #startmeeting cloud-init bi-weekly office-hours

-

16:20 <meetingology> Meeting started at 16:20:26 UTC. The chair is blackboxsw. Information about MeetBot at https://wiki.ubuntu.com/meetingology

-

16:20 <meetingology> Available commands: action, commands, idea, info, link, nick

-

16:21 <falcojr> I think by default it should use the current defaults of what's chosen...e.g., true for rhel and false for others

-

16:22 <blackboxsw> Hi cloud-init! This marks another episode of cloud-init community office hours. This time is an opportunity to discuss any cloud-init questions, bugs or topics with cloud-init upstream developers. We try to ensure a couple of devs have eyes on this channel to field any questions/concerns folks may have.

-

16:24 <Odd_Bloke> o/

-

16:25 <blackboxsw> Recent happenings in cloud-init space are generally spent on the current SRU validation with Odd_Bloke and falcojr. It looks like we've cleared the last manual validation with that SRU and we will be waiting on a significant automated set of tests to pass before making this release public. https://discourse.ubuntu.com/t/cloud-init-status-04-06-2021/21691

-

16:32 <blackboxsw> thanks falcojr and Odd_Bloke for reviews on https://github.com/canonical/cloud-init/pull/859

-

16:36 <hamalq> i already did the change as the comment

-

16:37 <hamalq> i dont think i can change cloudinit/distros/init.py select_hostname though

-

16:38 <falcojr> we can change it...we just need to make sure the functionality stays the same if the option isn't specified

-

16:39 <hamalq> thats the point since the default for that option is true

-

16:40 <hamalq> unless we make the default for it false for other distros

-

16:41 <falcojr> yes, we would need to take it into account for all distros, and it would default to false for most

-

16:42 <hamalq> +1

-

16:47 <hamalq> i changed that now for distros and rhel

-

17:15 <hamalq> i think i got the changes required https://github.com/canonical/cloud-init/pull/859

-

17:36 <blackboxsw> thanks folks for attending the office hours. See you all in two weeks. Same time

-

17:37 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.4.0 (https://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2021-05-18.html b/status-2021-05-18.html deleted file mode 100644 index 2dfdff7..0000000 --- a/status-2021-05-18.html +++ /dev/null @@ -1,193 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Tue 18 May 2021 in status-meeting-minutes - - • 2 min read -

-
- - -
-

Meeting information

- -

Meeting summary

-

People present (lines said)

-
    -
  • blackboxsw (12)
  • -
  • paride (4)
  • -
  • smoser (4)
  • -
  • meetingology (2)
  • -
  • ubot5 (1)
  • -
  • falcojr (1)
  • -
-

Full log

-

16:32 <blackboxsw> #startmeeting cloud-init bi-weekly office-hours

-

16:32 <meetingology> Meeting started at 16:32:21 UTC. The chair is blackboxsw. Information about MeetBot at https://wiki.ubuntu.com/meetingology

-

16:32 <meetingology> Available commands: action, commands, idea, info, link, nick

-

16:32 <paride> smoser, thanks, merged!

-

16:33 <paride> but as it's not in the server packageset I'll need sponsorship for the upload...

-

16:33 <blackboxsw> community-notice: Let's get back to a more regularly scheduled cloud-init office hours. Every two weeks, feel free to watch the channel topic for the next scheduled time. We'll ensure to have a couple of sets of eyes on this IRC channel.

-

16:35 <blackboxsw> Next office-hours meeting is set for June 1, 17:15 UTC. It is worth us having this recurring meeting to give anyone a chance to drive-by #cloud-init if they have questions, discussions, bugs or PRs that need attention.

-

16:36 <blackboxsw> Prior to the office hours, we will continue to generate a post with the latest commits to land in cloud-init:master as well as any notable features in progress https://discourse.ubuntu.com/t/cloud-init-status-05-18-2021/22349

-

16:41 <blackboxsw> From upstream standpoint, we were able to cut the time-based release 21.2 on May 6th. And for Ubuntu, we have queued the StableReleaseUpdate (SRU) for 21.2 into Bionic, Focal and Hirsute for which falcojr and Odd_Bloke have been going through verification.

-

16:41 <blackboxsw> Think we need to update the topic for the 21.2 upstream release too.

-

16:42 <smoser> paride: https://paste.ubuntu.com/p/y3N7wjCG3n/

-

16:44 <smoser> fudge.

-

16:44 <smoser> but i just noticed your changelog didn't have LP: #1908452

-

16:44 <ubot5> Launchpad bug 1908452 in MAAS "MAAS stops working and deployment fails after Loading ephemeral step" [High,In progress] https://launchpad.net/bugs/1908452

-

16:45 <smoser> because the commit message said 'Fixes LP:1908452' rather than just 'LP: #1908452'

-

16:46 <blackboxsw> 'Fixes LP:1908452' almost github; almost LP :/

-

16:48 <paride> smoser, argh :/ will update the bug status manually

-

16:48 <paride> thanks for the upload

-

16:50 * blackboxsw falcojr: do we have a trello board for the SRU 21.2 created?

-

16:50 <falcojr> yep, https://trello.com/b/tBP3Jrwp/sru-cloud-init-212 (just made it public)

-

16:51 <blackboxsw> Thanks a lot

-

16:55 <blackboxsw> Great, I was originally looking at the older trello board for the 21.1. Ok, so I'll grab Softlayer testing as you mentioned at standup today. If you want me to run through other clouds just let me know or hit me up for reviews.

-

17:26 <blackboxsw> Alright, I think that about wraps today's office hours. Next round in two weeks. Thanks for tuning in.

-

17:26 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.4.0 (https://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2021-06-01.html b/status-2021-06-01.html deleted file mode 100644 index 69780bc..0000000 --- a/status-2021-06-01.html +++ /dev/null @@ -1,179 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Tue 01 June 2021 in status-meeting-minutes - - • 2 min read -

-
- - -
-

Meeting information

- -

Meeting summary

- -

People present (lines said)

-
    -
  • blackboxsw (9)
  • -
  • meetingology (2)
  • -
-

Full log

-

17:25 <blackboxsw> #startmeeting cloud-init bi-weekly office hours (~30 mins)

-

17:25 <meetingology> Meeting started at 17:25:49 UTC. The chair is blackboxsw. Information about MeetBot at https://wiki.ubuntu.com/meetingology

-

17:25 <meetingology> Available commands: action, commands, idea, info, link, nick

-

17:28 <blackboxsw> community-notice: office hours meeting starts now. We host this meeting time every two weeks for any drop in discussions for anything cloud-init related. Bring your bugs, feature discussions, gripes and questions and we'll have a couple sets of upstream cloud-init eyes on this channel to field those discussions.

-

17:29 <blackboxsw> highlights of recent upstream commits and project changes are at the url below:

-

17:29 <blackboxsw> #link https://discourse.ubuntu.com/t/cloud-init-status-06-01-2021/22553

-

17:32 <blackboxsw> Of course, if you managed to join us over here you are already aware of the Freenode IRC politcal climate pushing us to migrate to a more open/friendly IRC network w/ libera.chat. paride is in the process of registering this channel for the cloud-init project so that we can add channel OPS to the upstream cloud-init committers smoser, rharper, Odd_Bloke, falcojr.

-

17:32 <blackboxsw> Once we have channel op status, we plan on adding upcoming dates, milestones and info to the IRC channel title.

-

17:37 <blackboxsw> Also, as upstream, we want to rename the default development branch from 'master' to 'main' to provide more inclusive naming and drop antiquated and exclusive naming conventions. An email will be sent to the cloud-init mailing list explaining the perceived impact of such a default branch rename (which should be minimal).

-

17:37 <blackboxsw> If there are any concerns about this rename impacting business, please raise concerns here, on the discourse post above or on the mailinglist

-

19:29 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.4.0 (https://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2021-06-15.html b/status-2021-06-15.html deleted file mode 100644 index 7aef7f4..0000000 --- a/status-2021-06-15.html +++ /dev/null @@ -1,191 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Tue 15 June 2021 in status-meeting-minutes - - • 2 min read -

-
- - -
-

Meeting information

- -

Meeting summary

- -

People present (lines said)

-
    -
  • blackboxsw (16)
  • -
  • meetingology (3)
  • -
  • falcojr (2)
  • -
-

Full log

-

17:17 <blackboxsw> #startmeeting cloud-init bi-weekly office-hours

-

17:17 <meetingology> Meeting started at 17:17:44 UTC. The chair is blackboxsw. Information about MeetBot at https://wiki.ubuntu.com/meetingology

-

17:17 <meetingology> Available commands: action, commands, idea, info, link, nick

-

17:20 <blackboxsw> community-notice: Hi cloud-initers, welcome to another office hours meeting. cloud-init committers will be around for the next hour to field any discussions. answer questions or put some eyes on PR reviews or bugs that spark your interest.

-

17:21 <blackboxsw> We host this meeting to unblock, or unstick anybody toying around with cloud-init, as well as to update thecloud-init devs on recent changes in cloud-init upstream

-

17:21 <blackboxsw> #chair falcojr

-

17:21 <meetingology> Current chairs: blackboxsw, falcojr

-

17:25 <blackboxsw> We just published a little discourse post describing that cloud-init upstream version 21.2 has now cleared SRU validation for Ubuntu Bionic(16.04) Focal (20.04) Groovy (20.10) and Hirsute (21.04) https://discourse.ubuntu.com/t/cloud-init-status-06-15-2021/22730

-

17:25 <blackboxsw> #link https://discourse.ubuntu.com/t/cloud-init-status-06-15-2021/22730

-

17:26 <blackboxsw> in that SRU, were some ssh_key handling improvement, Azure SSH key processing, Azure userdata updated ingested from IMDS and new support for Vultr cloud platform.

-

17:27 <blackboxsw> Thanks all for those contributions!

-

17:30 <blackboxsw> one other interesting thing to note: 4 days ago I was banned from FreeNode. falcojr did this happen to you too? "Connection closed unexpectedly: You are banned from this server- [#1480] Contact support@freenode.net (2021/6/11 05.18):"

-

17:31 <falcojr> blackboxsw: no, that's weird. I know they completely reset everything over there though.

-

17:32 <blackboxsw> hrm maybe they tracked irc nicks that were advertizing moving to Libera.chat is the only thing I can think. will check it out

-

17:33 <falcojr> at this point probably just best to cut ties completely

-

17:35 <blackboxsw> yes agreed

-

17:37 <blackboxsw> community-notice: reminder rename upstream/master ->` upstream/main in 2 days. All active PRs will automatically be retargetted. For your local clones for cloud-init it should mean only the following:

-

17:37 <blackboxsw> #link https://docs.github.com/en/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch#updating-a-local-clone-after-a-branch-name-changes

-

17:40 <blackboxsw> an email will be sent out to cloud-init@lists.launchpad.net

-

17:40 <blackboxsw> with detailed instructions.

-

19:47 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.4.0 (https://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/status-2021-06-29.html b/status-2021-06-29.html deleted file mode 100644 index a8dbc57..0000000 --- a/status-2021-06-29.html +++ /dev/null @@ -1,181 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Cloud-init bi-weekly status - - - - -
- - - -
-
- -

Cloud-init bi-weekly status

-

- Posted on Tue 29 June 2021 in status-meeting-minutes - - • 2 min read -

-
- - -
-

Meeting information

- -

Meeting summary

- -

People present (lines said)

-
    -
  • blackboxsw (9)
  • -
  • meetingology (2)
  • -
  • ubottu (1)
  • -
-

Full log

-

16:23 <blackboxsw> #startmeeting cloud-init bi-weekly office-hours

-

16:23 <meetingology> Meeting started at 16:23:41 UTC. The chair is blackboxsw. Information about MeetBot at https://wiki.ubuntu.com/meetingology

-

16:23 <meetingology> Available commands: action, commands, idea, info, link, nick

-

16:25 <blackboxsw> Hi cloud-init devs, Our biweekly office hours meeting has begun. We keep this channel open during the designated time on the channel #topic for drop in questions, feature or bug discussions and prodding committers folks for reviews.

-

16:27 <blackboxsw> All questions welcome and we'll have a couple of upstream committers with eyes on the channel to field any discussions brought up as best we can.

-

16:27 <blackboxsw> Just prior to this meeting, someone will post recent happenings in cloud-init upstream which may be of value to the community.

-

16:27 <blackboxsw> #link https://discourse.ubuntu.com/t/cloud-init-status-06-29-2021/22981

-

16:29 <blackboxsw> As far as upstream is concerned, the only schedule detail of note is we are looking to create an official 21.3 upstream release August 28th. Before that time we hope to have some hot plug network device handling functional in cloud-init.

-

16:34 <blackboxsw> my plan today is to get falcojr a review on his foundational hotplug support work at https://github.com/canonical/cloud-init/pull/919 which should allow cloud-init to support actively interacting with network config utilities to actively enable individual interfaces on device discovery after the network renderers have finished initial network bringup.

-

16:34 <ubottu> Pull 919 in canonical/cloud-init "Add new network configurers to bring up interfaces (SC-85)" [Open]

-

17:35 <blackboxsw> ok, that wraps things up for "office hours" for today. Thanks for checking in.

-

17:35 <blackboxsw> #endmeeting

-

Generated by MeetBot 0.4.0 (https://wiki.ubuntu.com/meetingology)

-
-
-

-

-
- - - -
- - -
- - - - - - - - \ No newline at end of file diff --git a/tags.html b/tags.html deleted file mode 100644 index f0d5582..0000000 --- a/tags.html +++ /dev/null @@ -1,129 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cloud-init Info – Tags - - - - -
- - - -
-
-

Tags

-
-
-
-
-
- - -
- - - - - - - - \ No newline at end of file diff --git a/theme/font-awesome/css/font-awesome.min.css b/theme/font-awesome/css/font-awesome.min.css deleted file mode 100644 index 9b27f8e..0000000 --- a/theme/font-awesome/css/font-awesome.min.css +++ /dev/null @@ -1,4 +0,0 @@ -/*! - * Font Awesome 4.6.3 by @davegandy - http://fontawesome.io - @fontawesome - * License - http://fontawesome.io/license (Font: SIL OFL 1.1, CSS: MIT License) - */@font-face{font-family:'FontAwesome';src:url('../fonts/fontawesome-webfont.eot?v=4.6.3');src:url('../fonts/fontawesome-webfont.eot?#iefix&v=4.6.3') format('embedded-opentype'),url('../fonts/fontawesome-webfont.woff2?v=4.6.3') format('woff2'),url('../fonts/fontawesome-webfont.woff?v=4.6.3') format('woff'),url('../fonts/fontawesome-webfont.ttf?v=4.6.3') format('truetype'),url('../fonts/fontawesome-webfont.svg?v=4.6.3#fontawesomeregular') format('svg');font-weight:normal;font-style:normal}.fa{display:inline-block;font:normal normal normal 14px/1 FontAwesome;font-size:inherit;text-rendering:auto;-webkit-font-smoothing:antialiased;-moz-osx-font-smoothing:grayscale}.fa-lg{font-size:1.33333333em;line-height:.75em;vertical-align:-15%}.fa-2x{font-size:2em}.fa-3x{font-size:3em}.fa-4x{font-size:4em}.fa-5x{font-size:5em}.fa-fw{width:1.28571429em;text-align:center}.fa-ul{padding-left:0;margin-left:2.14285714em;list-style-type:none}.fa-ul>li{position:relative}.fa-li{position:absolute;left:-2.14285714em;width:2.14285714em;top:.14285714em;text-align:center}.fa-li.fa-lg{left:-1.85714286em}.fa-border{padding:.2em .25em .15em;border:solid .08em #eee;border-radius:.1em}.fa-pull-left{float:left}.fa-pull-right{float:right}.fa.fa-pull-left{margin-right:.3em}.fa.fa-pull-right{margin-left:.3em}.pull-right{float:right}.pull-left{float:left}.fa.pull-left{margin-right:.3em}.fa.pull-right{margin-left:.3em}.fa-spin{-webkit-animation:fa-spin 2s infinite linear;animation:fa-spin 2s infinite linear}.fa-pulse{-webkit-animation:fa-spin 1s infinite steps(8);animation:fa-spin 1s infinite steps(8)}@-webkit-keyframes fa-spin{0%{-webkit-transform:rotate(0deg);transform:rotate(0deg)}100%{-webkit-transform:rotate(359deg);transform:rotate(359deg)}}@keyframes fa-spin{0%{-webkit-transform:rotate(0deg);transform:rotate(0deg)}100%{-webkit-transform:rotate(359deg);transform:rotate(359deg)}}.fa-rotate-90{-ms-filter:"progid:DXImageTransform.Microsoft.BasicImage(rotation=1)";-webkit-transform:rotate(90deg);-ms-transform:rotate(90deg);transform:rotate(90deg)}.fa-rotate-180{-ms-filter:"progid:DXImageTransform.Microsoft.BasicImage(rotation=2)";-webkit-transform:rotate(180deg);-ms-transform:rotate(180deg);transform:rotate(180deg)}.fa-rotate-270{-ms-filter:"progid:DXImageTransform.Microsoft.BasicImage(rotation=3)";-webkit-transform:rotate(270deg);-ms-transform:rotate(270deg);transform:rotate(270deg)}.fa-flip-horizontal{-ms-filter:"progid:DXImageTransform.Microsoft.BasicImage(rotation=0, mirror=1)";-webkit-transform:scale(-1, 1);-ms-transform:scale(-1, 1);transform:scale(-1, 1)}.fa-flip-vertical{-ms-filter:"progid:DXImageTransform.Microsoft.BasicImage(rotation=2, mirror=1)";-webkit-transform:scale(1, -1);-ms-transform:scale(1, -1);transform:scale(1, -1)}:root .fa-rotate-90,:root .fa-rotate-180,:root .fa-rotate-270,:root .fa-flip-horizontal,:root .fa-flip-vertical{filter:none}.fa-stack{position:relative;display:inline-block;width:2em;height:2em;line-height:2em;vertical-align:middle}.fa-stack-1x,.fa-stack-2x{position:absolute;left:0;width:100%;text-align:center}.fa-stack-1x{line-height:inherit}.fa-stack-2x{font-size:2em}.fa-inverse{color:#fff}.fa-glass:before{content:"\f000"}.fa-music:before{content:"\f001"}.fa-search:before{content:"\f002"}.fa-envelope-o:before{content:"\f003"}.fa-heart:before{content:"\f004"}.fa-star:before{content:"\f005"}.fa-star-o:before{content:"\f006"}.fa-user:before{content:"\f007"}.fa-film:before{content:"\f008"}.fa-th-large:before{content:"\f009"}.fa-th:before{content:"\f00a"}.fa-th-list:before{content:"\f00b"}.fa-check:before{content:"\f00c"}.fa-remove:before,.fa-close:before,.fa-times:before{content:"\f00d"}.fa-search-plus:before{content:"\f00e"}.fa-search-minus:before{content:"\f010"}.fa-power-off:before{content:"\f011"}.fa-signal:before{content:"\f012"}.fa-gear:before,.fa-cog:before{content:"\f013"}.fa-trash-o:before{content:"\f014"}.fa-home:before{content:"\f015"}.fa-file-o:before{content:"\f016"}.fa-clock-o:before{content:"\f017"}.fa-road:before{content:"\f018"}.fa-download:before{content:"\f019"}.fa-arrow-circle-o-down:before{content:"\f01a"}.fa-arrow-circle-o-up:before{content:"\f01b"}.fa-inbox:before{content:"\f01c"}.fa-play-circle-o:before{content:"\f01d"}.fa-rotate-right:before,.fa-repeat:before{content:"\f01e"}.fa-refresh:before{content:"\f021"}.fa-list-alt:before{content:"\f022"}.fa-lock:before{content:"\f023"}.fa-flag:before{content:"\f024"}.fa-headphones:before{content:"\f025"}.fa-volume-off:before{content:"\f026"}.fa-volume-down:before{content:"\f027"}.fa-volume-up:before{content:"\f028"}.fa-qrcode:before{content:"\f029"}.fa-barcode:before{content:"\f02a"}.fa-tag:before{content:"\f02b"}.fa-tags:before{content:"\f02c"}.fa-book:before{content:"\f02d"}.fa-bookmark:before{content:"\f02e"}.fa-print:before{content:"\f02f"}.fa-camera:before{content:"\f030"}.fa-font:before{content:"\f031"}.fa-bold:before{content:"\f032"}.fa-italic:before{content:"\f033"}.fa-text-height:before{content:"\f034"}.fa-text-width:before{content:"\f035"}.fa-align-left:before{content:"\f036"}.fa-align-center:before{content:"\f037"}.fa-align-right:before{content:"\f038"}.fa-align-justify:before{content:"\f039"}.fa-list:before{content:"\f03a"}.fa-dedent:before,.fa-outdent:before{content:"\f03b"}.fa-indent:before{content:"\f03c"}.fa-video-camera:before{content:"\f03d"}.fa-photo:before,.fa-image:before,.fa-picture-o:before{content:"\f03e"}.fa-pencil:before{content:"\f040"}.fa-map-marker:before{content:"\f041"}.fa-adjust:before{content:"\f042"}.fa-tint:before{content:"\f043"}.fa-edit:before,.fa-pencil-square-o:before{content:"\f044"}.fa-share-square-o:before{content:"\f045"}.fa-check-square-o:before{content:"\f046"}.fa-arrows:before{content:"\f047"}.fa-step-backward:before{content:"\f048"}.fa-fast-backward:before{content:"\f049"}.fa-backward:before{content:"\f04a"}.fa-play:before{content:"\f04b"}.fa-pause:before{content:"\f04c"}.fa-stop:before{content:"\f04d"}.fa-forward:before{content:"\f04e"}.fa-fast-forward:before{content:"\f050"}.fa-step-forward:before{content:"\f051"}.fa-eject:before{content:"\f052"}.fa-chevron-left:before{content:"\f053"}.fa-chevron-right:before{content:"\f054"}.fa-plus-circle:before{content:"\f055"}.fa-minus-circle:before{content:"\f056"}.fa-times-circle:before{content:"\f057"}.fa-check-circle:before{content:"\f058"}.fa-question-circle:before{content:"\f059"}.fa-info-circle:before{content:"\f05a"}.fa-crosshairs:before{content:"\f05b"}.fa-times-circle-o:before{content:"\f05c"}.fa-check-circle-o:before{content:"\f05d"}.fa-ban:before{content:"\f05e"}.fa-arrow-left:before{content:"\f060"}.fa-arrow-right:before{content:"\f061"}.fa-arrow-up:before{content:"\f062"}.fa-arrow-down:before{content:"\f063"}.fa-mail-forward:before,.fa-share:before{content:"\f064"}.fa-expand:before{content:"\f065"}.fa-compress:before{content:"\f066"}.fa-plus:before{content:"\f067"}.fa-minus:before{content:"\f068"}.fa-asterisk:before{content:"\f069"}.fa-exclamation-circle:before{content:"\f06a"}.fa-gift:before{content:"\f06b"}.fa-leaf:before{content:"\f06c"}.fa-fire:before{content:"\f06d"}.fa-eye:before{content:"\f06e"}.fa-eye-slash:before{content:"\f070"}.fa-warning:before,.fa-exclamation-triangle:before{content:"\f071"}.fa-plane:before{content:"\f072"}.fa-calendar:before{content:"\f073"}.fa-random:before{content:"\f074"}.fa-comment:before{content:"\f075"}.fa-magnet:before{content:"\f076"}.fa-chevron-up:before{content:"\f077"}.fa-chevron-down:before{content:"\f078"}.fa-retweet:before{content:"\f079"}.fa-shopping-cart:before{content:"\f07a"}.fa-folder:before{content:"\f07b"}.fa-folder-open:before{content:"\f07c"}.fa-arrows-v:before{content:"\f07d"}.fa-arrows-h:before{content:"\f07e"}.fa-bar-chart-o:before,.fa-bar-chart:before{content:"\f080"}.fa-twitter-square:before{content:"\f081"}.fa-facebook-square:before{content:"\f082"}.fa-camera-retro:before{content:"\f083"}.fa-key:before{content:"\f084"}.fa-gears:before,.fa-cogs:before{content:"\f085"}.fa-comments:before{content:"\f086"}.fa-thumbs-o-up:before{content:"\f087"}.fa-thumbs-o-down:before{content:"\f088"}.fa-star-half:before{content:"\f089"}.fa-heart-o:before{content:"\f08a"}.fa-sign-out:before{content:"\f08b"}.fa-linkedin-square:before{content:"\f08c"}.fa-thumb-tack:before{content:"\f08d"}.fa-external-link:before{content:"\f08e"}.fa-sign-in:before{content:"\f090"}.fa-trophy:before{content:"\f091"}.fa-github-square:before{content:"\f092"}.fa-upload:before{content:"\f093"}.fa-lemon-o:before{content:"\f094"}.fa-phone:before{content:"\f095"}.fa-square-o:before{content:"\f096"}.fa-bookmark-o:before{content:"\f097"}.fa-phone-square:before{content:"\f098"}.fa-twitter:before{content:"\f099"}.fa-facebook-f:before,.fa-facebook:before{content:"\f09a"}.fa-github:before{content:"\f09b"}.fa-unlock:before{content:"\f09c"}.fa-credit-card:before{content:"\f09d"}.fa-feed:before,.fa-rss:before{content:"\f09e"}.fa-hdd-o:before{content:"\f0a0"}.fa-bullhorn:before{content:"\f0a1"}.fa-bell:before{content:"\f0f3"}.fa-certificate:before{content:"\f0a3"}.fa-hand-o-right:before{content:"\f0a4"}.fa-hand-o-left:before{content:"\f0a5"}.fa-hand-o-up:before{content:"\f0a6"}.fa-hand-o-down:before{content:"\f0a7"}.fa-arrow-circle-left:before{content:"\f0a8"}.fa-arrow-circle-right:before{content:"\f0a9"}.fa-arrow-circle-up:before{content:"\f0aa"}.fa-arrow-circle-down:before{content:"\f0ab"}.fa-globe:before{content:"\f0ac"}.fa-wrench:before{content:"\f0ad"}.fa-tasks:before{content:"\f0ae"}.fa-filter:before{content:"\f0b0"}.fa-briefcase:before{content:"\f0b1"}.fa-arrows-alt:before{content:"\f0b2"}.fa-group:before,.fa-users:before{content:"\f0c0"}.fa-chain:before,.fa-link:before{content:"\f0c1"}.fa-cloud:before{content:"\f0c2"}.fa-flask:before{content:"\f0c3"}.fa-cut:before,.fa-scissors:before{content:"\f0c4"}.fa-copy:before,.fa-files-o:before{content:"\f0c5"}.fa-paperclip:before{content:"\f0c6"}.fa-save:before,.fa-floppy-o:before{content:"\f0c7"}.fa-square:before{content:"\f0c8"}.fa-navicon:before,.fa-reorder:before,.fa-bars:before{content:"\f0c9"}.fa-list-ul:before{content:"\f0ca"}.fa-list-ol:before{content:"\f0cb"}.fa-strikethrough:before{content:"\f0cc"}.fa-underline:before{content:"\f0cd"}.fa-table:before{content:"\f0ce"}.fa-magic:before{content:"\f0d0"}.fa-truck:before{content:"\f0d1"}.fa-pinterest:before{content:"\f0d2"}.fa-pinterest-square:before{content:"\f0d3"}.fa-google-plus-square:before{content:"\f0d4"}.fa-google-plus:before{content:"\f0d5"}.fa-money:before{content:"\f0d6"}.fa-caret-down:before{content:"\f0d7"}.fa-caret-up:before{content:"\f0d8"}.fa-caret-left:before{content:"\f0d9"}.fa-caret-right:before{content:"\f0da"}.fa-columns:before{content:"\f0db"}.fa-unsorted:before,.fa-sort:before{content:"\f0dc"}.fa-sort-down:before,.fa-sort-desc:before{content:"\f0dd"}.fa-sort-up:before,.fa-sort-asc:before{content:"\f0de"}.fa-envelope:before{content:"\f0e0"}.fa-linkedin:before{content:"\f0e1"}.fa-rotate-left:before,.fa-undo:before{content:"\f0e2"}.fa-legal:before,.fa-gavel:before{content:"\f0e3"}.fa-dashboard:before,.fa-tachometer:before{content:"\f0e4"}.fa-comment-o:before{content:"\f0e5"}.fa-comments-o:before{content:"\f0e6"}.fa-flash:before,.fa-bolt:before{content:"\f0e7"}.fa-sitemap:before{content:"\f0e8"}.fa-umbrella:before{content:"\f0e9"}.fa-paste:before,.fa-clipboard:before{content:"\f0ea"}.fa-lightbulb-o:before{content:"\f0eb"}.fa-exchange:before{content:"\f0ec"}.fa-cloud-download:before{content:"\f0ed"}.fa-cloud-upload:before{content:"\f0ee"}.fa-user-md:before{content:"\f0f0"}.fa-stethoscope:before{content:"\f0f1"}.fa-suitcase:before{content:"\f0f2"}.fa-bell-o:before{content:"\f0a2"}.fa-coffee:before{content:"\f0f4"}.fa-cutlery:before{content:"\f0f5"}.fa-file-text-o:before{content:"\f0f6"}.fa-building-o:before{content:"\f0f7"}.fa-hospital-o:before{content:"\f0f8"}.fa-ambulance:before{content:"\f0f9"}.fa-medkit:before{content:"\f0fa"}.fa-fighter-jet:before{content:"\f0fb"}.fa-beer:before{content:"\f0fc"}.fa-h-square:before{content:"\f0fd"}.fa-plus-square:before{content:"\f0fe"}.fa-angle-double-left:before{content:"\f100"}.fa-angle-double-right:before{content:"\f101"}.fa-angle-double-up:before{content:"\f102"}.fa-angle-double-down:before{content:"\f103"}.fa-angle-left:before{content:"\f104"}.fa-angle-right:before{content:"\f105"}.fa-angle-up:before{content:"\f106"}.fa-angle-down:before{content:"\f107"}.fa-desktop:before{content:"\f108"}.fa-laptop:before{content:"\f109"}.fa-tablet:before{content:"\f10a"}.fa-mobile-phone:before,.fa-mobile:before{content:"\f10b"}.fa-circle-o:before{content:"\f10c"}.fa-quote-left:before{content:"\f10d"}.fa-quote-right:before{content:"\f10e"}.fa-spinner:before{content:"\f110"}.fa-circle:before{content:"\f111"}.fa-mail-reply:before,.fa-reply:before{content:"\f112"}.fa-github-alt:before{content:"\f113"}.fa-folder-o:before{content:"\f114"}.fa-folder-open-o:before{content:"\f115"}.fa-smile-o:before{content:"\f118"}.fa-frown-o:before{content:"\f119"}.fa-meh-o:before{content:"\f11a"}.fa-gamepad:before{content:"\f11b"}.fa-keyboard-o:before{content:"\f11c"}.fa-flag-o:before{content:"\f11d"}.fa-flag-checkered:before{content:"\f11e"}.fa-terminal:before{content:"\f120"}.fa-code:before{content:"\f121"}.fa-mail-reply-all:before,.fa-reply-all:before{content:"\f122"}.fa-star-half-empty:before,.fa-star-half-full:before,.fa-star-half-o:before{content:"\f123"}.fa-location-arrow:before{content:"\f124"}.fa-crop:before{content:"\f125"}.fa-code-fork:before{content:"\f126"}.fa-unlink:before,.fa-chain-broken:before{content:"\f127"}.fa-question:before{content:"\f128"}.fa-info:before{content:"\f129"}.fa-exclamation:before{content:"\f12a"}.fa-superscript:before{content:"\f12b"}.fa-subscript:before{content:"\f12c"}.fa-eraser:before{content:"\f12d"}.fa-puzzle-piece:before{content:"\f12e"}.fa-microphone:before{content:"\f130"}.fa-microphone-slash:before{content:"\f131"}.fa-shield:before{content:"\f132"}.fa-calendar-o:before{content:"\f133"}.fa-fire-extinguisher:before{content:"\f134"}.fa-rocket:before{content:"\f135"}.fa-maxcdn:before{content:"\f136"}.fa-chevron-circle-left:before{content:"\f137"}.fa-chevron-circle-right:before{content:"\f138"}.fa-chevron-circle-up:before{content:"\f139"}.fa-chevron-circle-down:before{content:"\f13a"}.fa-html5:before{content:"\f13b"}.fa-css3:before{content:"\f13c"}.fa-anchor:before{content:"\f13d"}.fa-unlock-alt:before{content:"\f13e"}.fa-bullseye:before{content:"\f140"}.fa-ellipsis-h:before{content:"\f141"}.fa-ellipsis-v:before{content:"\f142"}.fa-rss-square:before{content:"\f143"}.fa-play-circle:before{content:"\f144"}.fa-ticket:before{content:"\f145"}.fa-minus-square:before{content:"\f146"}.fa-minus-square-o:before{content:"\f147"}.fa-level-up:before{content:"\f148"}.fa-level-down:before{content:"\f149"}.fa-check-square:before{content:"\f14a"}.fa-pencil-square:before{content:"\f14b"}.fa-external-link-square:before{content:"\f14c"}.fa-share-square:before{content:"\f14d"}.fa-compass:before{content:"\f14e"}.fa-toggle-down:before,.fa-caret-square-o-down:before{content:"\f150"}.fa-toggle-up:before,.fa-caret-square-o-up:before{content:"\f151"}.fa-toggle-right:before,.fa-caret-square-o-right:before{content:"\f152"}.fa-euro:before,.fa-eur:before{content:"\f153"}.fa-gbp:before{content:"\f154"}.fa-dollar:before,.fa-usd:before{content:"\f155"}.fa-rupee:before,.fa-inr:before{content:"\f156"}.fa-cny:before,.fa-rmb:before,.fa-yen:before,.fa-jpy:before{content:"\f157"}.fa-ruble:before,.fa-rouble:before,.fa-rub:before{content:"\f158"}.fa-won:before,.fa-krw:before{content:"\f159"}.fa-bitcoin:before,.fa-btc:before{content:"\f15a"}.fa-file:before{content:"\f15b"}.fa-file-text:before{content:"\f15c"}.fa-sort-alpha-asc:before{content:"\f15d"}.fa-sort-alpha-desc:before{content:"\f15e"}.fa-sort-amount-asc:before{content:"\f160"}.fa-sort-amount-desc:before{content:"\f161"}.fa-sort-numeric-asc:before{content:"\f162"}.fa-sort-numeric-desc:before{content:"\f163"}.fa-thumbs-up:before{content:"\f164"}.fa-thumbs-down:before{content:"\f165"}.fa-youtube-square:before{content:"\f166"}.fa-youtube:before{content:"\f167"}.fa-xing:before{content:"\f168"}.fa-xing-square:before{content:"\f169"}.fa-youtube-play:before{content:"\f16a"}.fa-dropbox:before{content:"\f16b"}.fa-stack-overflow:before{content:"\f16c"}.fa-instagram:before{content:"\f16d"}.fa-flickr:before{content:"\f16e"}.fa-adn:before{content:"\f170"}.fa-bitbucket:before{content:"\f171"}.fa-bitbucket-square:before{content:"\f172"}.fa-tumblr:before{content:"\f173"}.fa-tumblr-square:before{content:"\f174"}.fa-long-arrow-down:before{content:"\f175"}.fa-long-arrow-up:before{content:"\f176"}.fa-long-arrow-left:before{content:"\f177"}.fa-long-arrow-right:before{content:"\f178"}.fa-apple:before{content:"\f179"}.fa-windows:before{content:"\f17a"}.fa-android:before{content:"\f17b"}.fa-linux:before{content:"\f17c"}.fa-dribbble:before{content:"\f17d"}.fa-skype:before{content:"\f17e"}.fa-foursquare:before{content:"\f180"}.fa-trello:before{content:"\f181"}.fa-female:before{content:"\f182"}.fa-male:before{content:"\f183"}.fa-gittip:before,.fa-gratipay:before{content:"\f184"}.fa-sun-o:before{content:"\f185"}.fa-moon-o:before{content:"\f186"}.fa-archive:before{content:"\f187"}.fa-bug:before{content:"\f188"}.fa-vk:before{content:"\f189"}.fa-weibo:before{content:"\f18a"}.fa-renren:before{content:"\f18b"}.fa-pagelines:before{content:"\f18c"}.fa-stack-exchange:before{content:"\f18d"}.fa-arrow-circle-o-right:before{content:"\f18e"}.fa-arrow-circle-o-left:before{content:"\f190"}.fa-toggle-left:before,.fa-caret-square-o-left:before{content:"\f191"}.fa-dot-circle-o:before{content:"\f192"}.fa-wheelchair:before{content:"\f193"}.fa-vimeo-square:before{content:"\f194"}.fa-turkish-lira:before,.fa-try:before{content:"\f195"}.fa-plus-square-o:before{content:"\f196"}.fa-space-shuttle:before{content:"\f197"}.fa-slack:before{content:"\f198"}.fa-envelope-square:before{content:"\f199"}.fa-wordpress:before{content:"\f19a"}.fa-openid:before{content:"\f19b"}.fa-institution:before,.fa-bank:before,.fa-university:before{content:"\f19c"}.fa-mortar-board:before,.fa-graduation-cap:before{content:"\f19d"}.fa-yahoo:before{content:"\f19e"}.fa-google:before{content:"\f1a0"}.fa-reddit:before{content:"\f1a1"}.fa-reddit-square:before{content:"\f1a2"}.fa-stumbleupon-circle:before{content:"\f1a3"}.fa-stumbleupon:before{content:"\f1a4"}.fa-delicious:before{content:"\f1a5"}.fa-digg:before{content:"\f1a6"}.fa-pied-piper-pp:before{content:"\f1a7"}.fa-pied-piper-alt:before{content:"\f1a8"}.fa-drupal:before{content:"\f1a9"}.fa-joomla:before{content:"\f1aa"}.fa-language:before{content:"\f1ab"}.fa-fax:before{content:"\f1ac"}.fa-building:before{content:"\f1ad"}.fa-child:before{content:"\f1ae"}.fa-paw:before{content:"\f1b0"}.fa-spoon:before{content:"\f1b1"}.fa-cube:before{content:"\f1b2"}.fa-cubes:before{content:"\f1b3"}.fa-behance:before{content:"\f1b4"}.fa-behance-square:before{content:"\f1b5"}.fa-steam:before{content:"\f1b6"}.fa-steam-square:before{content:"\f1b7"}.fa-recycle:before{content:"\f1b8"}.fa-automobile:before,.fa-car:before{content:"\f1b9"}.fa-cab:before,.fa-taxi:before{content:"\f1ba"}.fa-tree:before{content:"\f1bb"}.fa-spotify:before{content:"\f1bc"}.fa-deviantart:before{content:"\f1bd"}.fa-soundcloud:before{content:"\f1be"}.fa-database:before{content:"\f1c0"}.fa-file-pdf-o:before{content:"\f1c1"}.fa-file-word-o:before{content:"\f1c2"}.fa-file-excel-o:before{content:"\f1c3"}.fa-file-powerpoint-o:before{content:"\f1c4"}.fa-file-photo-o:before,.fa-file-picture-o:before,.fa-file-image-o:before{content:"\f1c5"}.fa-file-zip-o:before,.fa-file-archive-o:before{content:"\f1c6"}.fa-file-sound-o:before,.fa-file-audio-o:before{content:"\f1c7"}.fa-file-movie-o:before,.fa-file-video-o:before{content:"\f1c8"}.fa-file-code-o:before{content:"\f1c9"}.fa-vine:before{content:"\f1ca"}.fa-codepen:before{content:"\f1cb"}.fa-jsfiddle:before{content:"\f1cc"}.fa-life-bouy:before,.fa-life-buoy:before,.fa-life-saver:before,.fa-support:before,.fa-life-ring:before{content:"\f1cd"}.fa-circle-o-notch:before{content:"\f1ce"}.fa-ra:before,.fa-resistance:before,.fa-rebel:before{content:"\f1d0"}.fa-ge:before,.fa-empire:before{content:"\f1d1"}.fa-git-square:before{content:"\f1d2"}.fa-git:before{content:"\f1d3"}.fa-y-combinator-square:before,.fa-yc-square:before,.fa-hacker-news:before{content:"\f1d4"}.fa-tencent-weibo:before{content:"\f1d5"}.fa-qq:before{content:"\f1d6"}.fa-wechat:before,.fa-weixin:before{content:"\f1d7"}.fa-send:before,.fa-paper-plane:before{content:"\f1d8"}.fa-send-o:before,.fa-paper-plane-o:before{content:"\f1d9"}.fa-history:before{content:"\f1da"}.fa-circle-thin:before{content:"\f1db"}.fa-header:before{content:"\f1dc"}.fa-paragraph:before{content:"\f1dd"}.fa-sliders:before{content:"\f1de"}.fa-share-alt:before{content:"\f1e0"}.fa-share-alt-square:before{content:"\f1e1"}.fa-bomb:before{content:"\f1e2"}.fa-soccer-ball-o:before,.fa-futbol-o:before{content:"\f1e3"}.fa-tty:before{content:"\f1e4"}.fa-binoculars:before{content:"\f1e5"}.fa-plug:before{content:"\f1e6"}.fa-slideshare:before{content:"\f1e7"}.fa-twitch:before{content:"\f1e8"}.fa-yelp:before{content:"\f1e9"}.fa-newspaper-o:before{content:"\f1ea"}.fa-wifi:before{content:"\f1eb"}.fa-calculator:before{content:"\f1ec"}.fa-paypal:before{content:"\f1ed"}.fa-google-wallet:before{content:"\f1ee"}.fa-cc-visa:before{content:"\f1f0"}.fa-cc-mastercard:before{content:"\f1f1"}.fa-cc-discover:before{content:"\f1f2"}.fa-cc-amex:before{content:"\f1f3"}.fa-cc-paypal:before{content:"\f1f4"}.fa-cc-stripe:before{content:"\f1f5"}.fa-bell-slash:before{content:"\f1f6"}.fa-bell-slash-o:before{content:"\f1f7"}.fa-trash:before{content:"\f1f8"}.fa-copyright:before{content:"\f1f9"}.fa-at:before{content:"\f1fa"}.fa-eyedropper:before{content:"\f1fb"}.fa-paint-brush:before{content:"\f1fc"}.fa-birthday-cake:before{content:"\f1fd"}.fa-area-chart:before{content:"\f1fe"}.fa-pie-chart:before{content:"\f200"}.fa-line-chart:before{content:"\f201"}.fa-lastfm:before{content:"\f202"}.fa-lastfm-square:before{content:"\f203"}.fa-toggle-off:before{content:"\f204"}.fa-toggle-on:before{content:"\f205"}.fa-bicycle:before{content:"\f206"}.fa-bus:before{content:"\f207"}.fa-ioxhost:before{content:"\f208"}.fa-angellist:before{content:"\f209"}.fa-cc:before{content:"\f20a"}.fa-shekel:before,.fa-sheqel:before,.fa-ils:before{content:"\f20b"}.fa-meanpath:before{content:"\f20c"}.fa-buysellads:before{content:"\f20d"}.fa-connectdevelop:before{content:"\f20e"}.fa-dashcube:before{content:"\f210"}.fa-forumbee:before{content:"\f211"}.fa-leanpub:before{content:"\f212"}.fa-sellsy:before{content:"\f213"}.fa-shirtsinbulk:before{content:"\f214"}.fa-simplybuilt:before{content:"\f215"}.fa-skyatlas:before{content:"\f216"}.fa-cart-plus:before{content:"\f217"}.fa-cart-arrow-down:before{content:"\f218"}.fa-diamond:before{content:"\f219"}.fa-ship:before{content:"\f21a"}.fa-user-secret:before{content:"\f21b"}.fa-motorcycle:before{content:"\f21c"}.fa-street-view:before{content:"\f21d"}.fa-heartbeat:before{content:"\f21e"}.fa-venus:before{content:"\f221"}.fa-mars:before{content:"\f222"}.fa-mercury:before{content:"\f223"}.fa-intersex:before,.fa-transgender:before{content:"\f224"}.fa-transgender-alt:before{content:"\f225"}.fa-venus-double:before{content:"\f226"}.fa-mars-double:before{content:"\f227"}.fa-venus-mars:before{content:"\f228"}.fa-mars-stroke:before{content:"\f229"}.fa-mars-stroke-v:before{content:"\f22a"}.fa-mars-stroke-h:before{content:"\f22b"}.fa-neuter:before{content:"\f22c"}.fa-genderless:before{content:"\f22d"}.fa-facebook-official:before{content:"\f230"}.fa-pinterest-p:before{content:"\f231"}.fa-whatsapp:before{content:"\f232"}.fa-server:before{content:"\f233"}.fa-user-plus:before{content:"\f234"}.fa-user-times:before{content:"\f235"}.fa-hotel:before,.fa-bed:before{content:"\f236"}.fa-viacoin:before{content:"\f237"}.fa-train:before{content:"\f238"}.fa-subway:before{content:"\f239"}.fa-medium:before{content:"\f23a"}.fa-yc:before,.fa-y-combinator:before{content:"\f23b"}.fa-optin-monster:before{content:"\f23c"}.fa-opencart:before{content:"\f23d"}.fa-expeditedssl:before{content:"\f23e"}.fa-battery-4:before,.fa-battery-full:before{content:"\f240"}.fa-battery-3:before,.fa-battery-three-quarters:before{content:"\f241"}.fa-battery-2:before,.fa-battery-half:before{content:"\f242"}.fa-battery-1:before,.fa-battery-quarter:before{content:"\f243"}.fa-battery-0:before,.fa-battery-empty:before{content:"\f244"}.fa-mouse-pointer:before{content:"\f245"}.fa-i-cursor:before{content:"\f246"}.fa-object-group:before{content:"\f247"}.fa-object-ungroup:before{content:"\f248"}.fa-sticky-note:before{content:"\f249"}.fa-sticky-note-o:before{content:"\f24a"}.fa-cc-jcb:before{content:"\f24b"}.fa-cc-diners-club:before{content:"\f24c"}.fa-clone:before{content:"\f24d"}.fa-balance-scale:before{content:"\f24e"}.fa-hourglass-o:before{content:"\f250"}.fa-hourglass-1:before,.fa-hourglass-start:before{content:"\f251"}.fa-hourglass-2:before,.fa-hourglass-half:before{content:"\f252"}.fa-hourglass-3:before,.fa-hourglass-end:before{content:"\f253"}.fa-hourglass:before{content:"\f254"}.fa-hand-grab-o:before,.fa-hand-rock-o:before{content:"\f255"}.fa-hand-stop-o:before,.fa-hand-paper-o:before{content:"\f256"}.fa-hand-scissors-o:before{content:"\f257"}.fa-hand-lizard-o:before{content:"\f258"}.fa-hand-spock-o:before{content:"\f259"}.fa-hand-pointer-o:before{content:"\f25a"}.fa-hand-peace-o:before{content:"\f25b"}.fa-trademark:before{content:"\f25c"}.fa-registered:before{content:"\f25d"}.fa-creative-commons:before{content:"\f25e"}.fa-gg:before{content:"\f260"}.fa-gg-circle:before{content:"\f261"}.fa-tripadvisor:before{content:"\f262"}.fa-odnoklassniki:before{content:"\f263"}.fa-odnoklassniki-square:before{content:"\f264"}.fa-get-pocket:before{content:"\f265"}.fa-wikipedia-w:before{content:"\f266"}.fa-safari:before{content:"\f267"}.fa-chrome:before{content:"\f268"}.fa-firefox:before{content:"\f269"}.fa-opera:before{content:"\f26a"}.fa-internet-explorer:before{content:"\f26b"}.fa-tv:before,.fa-television:before{content:"\f26c"}.fa-contao:before{content:"\f26d"}.fa-500px:before{content:"\f26e"}.fa-amazon:before{content:"\f270"}.fa-calendar-plus-o:before{content:"\f271"}.fa-calendar-minus-o:before{content:"\f272"}.fa-calendar-times-o:before{content:"\f273"}.fa-calendar-check-o:before{content:"\f274"}.fa-industry:before{content:"\f275"}.fa-map-pin:before{content:"\f276"}.fa-map-signs:before{content:"\f277"}.fa-map-o:before{content:"\f278"}.fa-map:before{content:"\f279"}.fa-commenting:before{content:"\f27a"}.fa-commenting-o:before{content:"\f27b"}.fa-houzz:before{content:"\f27c"}.fa-vimeo:before{content:"\f27d"}.fa-black-tie:before{content:"\f27e"}.fa-fonticons:before{content:"\f280"}.fa-reddit-alien:before{content:"\f281"}.fa-edge:before{content:"\f282"}.fa-credit-card-alt:before{content:"\f283"}.fa-codiepie:before{content:"\f284"}.fa-modx:before{content:"\f285"}.fa-fort-awesome:before{content:"\f286"}.fa-usb:before{content:"\f287"}.fa-product-hunt:before{content:"\f288"}.fa-mixcloud:before{content:"\f289"}.fa-scribd:before{content:"\f28a"}.fa-pause-circle:before{content:"\f28b"}.fa-pause-circle-o:before{content:"\f28c"}.fa-stop-circle:before{content:"\f28d"}.fa-stop-circle-o:before{content:"\f28e"}.fa-shopping-bag:before{content:"\f290"}.fa-shopping-basket:before{content:"\f291"}.fa-hashtag:before{content:"\f292"}.fa-bluetooth:before{content:"\f293"}.fa-bluetooth-b:before{content:"\f294"}.fa-percent:before{content:"\f295"}.fa-gitlab:before{content:"\f296"}.fa-wpbeginner:before{content:"\f297"}.fa-wpforms:before{content:"\f298"}.fa-envira:before{content:"\f299"}.fa-universal-access:before{content:"\f29a"}.fa-wheelchair-alt:before{content:"\f29b"}.fa-question-circle-o:before{content:"\f29c"}.fa-blind:before{content:"\f29d"}.fa-audio-description:before{content:"\f29e"}.fa-volume-control-phone:before{content:"\f2a0"}.fa-braille:before{content:"\f2a1"}.fa-assistive-listening-systems:before{content:"\f2a2"}.fa-asl-interpreting:before,.fa-american-sign-language-interpreting:before{content:"\f2a3"}.fa-deafness:before,.fa-hard-of-hearing:before,.fa-deaf:before{content:"\f2a4"}.fa-glide:before{content:"\f2a5"}.fa-glide-g:before{content:"\f2a6"}.fa-signing:before,.fa-sign-language:before{content:"\f2a7"}.fa-low-vision:before{content:"\f2a8"}.fa-viadeo:before{content:"\f2a9"}.fa-viadeo-square:before{content:"\f2aa"}.fa-snapchat:before{content:"\f2ab"}.fa-snapchat-ghost:before{content:"\f2ac"}.fa-snapchat-square:before{content:"\f2ad"}.fa-pied-piper:before{content:"\f2ae"}.fa-first-order:before{content:"\f2b0"}.fa-yoast:before{content:"\f2b1"}.fa-themeisle:before{content:"\f2b2"}.fa-google-plus-circle:before,.fa-google-plus-official:before{content:"\f2b3"}.fa-fa:before,.fa-font-awesome:before{content:"\f2b4"}.sr-only{position:absolute;width:1px;height:1px;padding:0;margin:-1px;overflow:hidden;clip:rect(0, 0, 0, 0);border:0}.sr-only-focusable:active,.sr-only-focusable:focus{position:static;width:auto;height:auto;margin:0;overflow:visible;clip:auto} diff --git a/theme/font-awesome/fonts/FontAwesome.otf b/theme/font-awesome/fonts/FontAwesome.otf deleted file mode 100644 index d4de13e..0000000 Binary files a/theme/font-awesome/fonts/FontAwesome.otf and /dev/null differ diff --git a/theme/font-awesome/fonts/fontawesome-webfont.eot b/theme/font-awesome/fonts/fontawesome-webfont.eot deleted file mode 100644 index c7b00d2..0000000 Binary files a/theme/font-awesome/fonts/fontawesome-webfont.eot and /dev/null differ diff --git a/theme/font-awesome/fonts/fontawesome-webfont.svg b/theme/font-awesome/fonts/fontawesome-webfont.svg deleted file mode 100644 index 8b66187..0000000 --- a/theme/font-awesome/fonts/fontawesome-webfont.svg +++ /dev/null @@ -1,685 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \ No newline at end of file diff --git a/theme/font-awesome/fonts/fontawesome-webfont.ttf b/theme/font-awesome/fonts/fontawesome-webfont.ttf deleted file mode 100644 index f221e50..0000000 Binary files a/theme/font-awesome/fonts/fontawesome-webfont.ttf and /dev/null differ diff --git a/theme/font-awesome/fonts/fontawesome-webfont.woff b/theme/font-awesome/fonts/fontawesome-webfont.woff deleted file mode 100644 index 6e7483c..0000000 Binary files a/theme/font-awesome/fonts/fontawesome-webfont.woff and /dev/null differ diff --git a/theme/font-awesome/fonts/fontawesome-webfont.woff2 b/theme/font-awesome/fonts/fontawesome-webfont.woff2 deleted file mode 100644 index 7eb74fd..0000000 Binary files a/theme/font-awesome/fonts/fontawesome-webfont.woff2 and /dev/null differ diff --git a/theme/img/profile.png b/theme/img/profile.png deleted file mode 100644 index 8ccf2e8..0000000 Binary files a/theme/img/profile.png and /dev/null differ diff --git a/theme/img/profile_license.txt b/theme/img/profile_license.txt deleted file mode 100644 index a38ff91..0000000 --- a/theme/img/profile_license.txt +++ /dev/null @@ -1 +0,0 @@ -https://www.iconfinder.com/icons/196742/account_boy_male_man_people_profile_user_icon \ No newline at end of file diff --git a/theme/pygments/algol.css b/theme/pygments/algol.css deleted file mode 100644 index cd099f1..0000000 --- a/theme/pygments/algol.css +++ /dev/null @@ -1,39 +0,0 @@ -.highlight { background-color: #ffffcc } -.c { color: #888888; font-style: italic } /* Comment */ -.err { border: 1px solid #FF0000 } /* Error */ -.k { font-weight: bold; text-decoration: underline } /* Keyword */ -.ch { color: #888888; font-style: italic } /* Comment.Hashbang */ -.cm { color: #888888; font-style: italic } /* Comment.Multiline */ -.cp { color: #888888; font-weight: bold } /* Comment.Preproc */ -.cpf { color: #888888; font-style: italic } /* Comment.PreprocFile */ -.c1 { color: #888888; font-style: italic } /* Comment.Single */ -.cs { color: #888888; font-weight: bold } /* Comment.Special */ -.kc { font-weight: bold; text-decoration: underline } /* Keyword.Constant */ -.kd { font-weight: bold; font-style: italic; text-decoration: underline } /* Keyword.Declaration */ -.kn { font-weight: bold; text-decoration: underline } /* Keyword.Namespace */ -.kp { font-weight: bold; text-decoration: underline } /* Keyword.Pseudo */ -.kr { font-weight: bold; text-decoration: underline } /* Keyword.Reserved */ -.kt { font-weight: bold; text-decoration: underline } /* Keyword.Type */ -.s { color: #666666; font-style: italic } /* Literal.String */ -.nb { font-weight: bold; font-style: italic } /* Name.Builtin */ -.nc { color: #666666; font-weight: bold; font-style: italic } /* Name.Class */ -.no { color: #666666; font-weight: bold; font-style: italic } /* Name.Constant */ -.nf { color: #666666; font-weight: bold; font-style: italic } /* Name.Function */ -.nn { color: #666666; font-weight: bold; font-style: italic } /* Name.Namespace */ -.nv { color: #666666; font-weight: bold; font-style: italic } /* Name.Variable */ -.ow { font-weight: bold } /* Operator.Word */ -.sb { color: #666666; font-style: italic } /* Literal.String.Backtick */ -.sc { color: #666666; font-style: italic } /* Literal.String.Char */ -.sd { color: #666666; font-style: italic } /* Literal.String.Doc */ -.s2 { color: #666666; font-style: italic } /* Literal.String.Double */ -.se { color: #666666; font-style: italic } /* Literal.String.Escape */ -.sh { color: #666666; font-style: italic } /* Literal.String.Heredoc */ -.si { color: #666666; font-style: italic } /* Literal.String.Interpol */ -.sx { color: #666666; font-style: italic } /* Literal.String.Other */ -.sr { color: #666666; font-style: italic } /* Literal.String.Regex */ -.s1 { color: #666666; font-style: italic } /* Literal.String.Single */ -.ss { color: #666666; font-style: italic } /* Literal.String.Symbol */ -.bp { font-weight: bold; font-style: italic } /* Name.Builtin.Pseudo */ -.vc { color: #666666; font-weight: bold; font-style: italic } /* Name.Variable.Class */ -.vg { color: #666666; font-weight: bold; font-style: italic } /* Name.Variable.Global */ -.vi { color: #666666; font-weight: bold; font-style: italic } /* Name.Variable.Instance */ \ No newline at end of file diff --git a/theme/pygments/algol.min.css b/theme/pygments/algol.min.css deleted file mode 100644 index d9335e8..0000000 --- a/theme/pygments/algol.min.css +++ /dev/null @@ -1 +0,0 @@ -.highlight{background-color:#ffc}.c{color:#888;font-style:italic}.err{border:1px solid red}.k{font-weight:700;text-decoration:underline}.ch,.cm{color:#888;font-style:italic}.cp{color:#888;font-weight:700}.c1,.cpf{color:#888;font-style:italic}.cs{color:#888;font-weight:700}.kc,.kd{font-weight:700;text-decoration:underline}.kd{font-style:italic}.kn,.kp,.kr,.kt{font-weight:700;text-decoration:underline}.s{color:#666;font-style:italic}.nb,.nc{font-weight:700;font-style:italic}.nc{color:#666}.nf,.nn,.no,.nv{color:#666;font-weight:700;font-style:italic}.ow{font-weight:700}.s1,.s2,.sb,.sc,.sd,.se,.sh,.si,.sr,.ss,.sx{color:#666;font-style:italic}.bp,.vc{font-weight:700;font-style:italic}.vc{color:#666}.vg,.vi{color:#666;font-weight:700;font-style:italic} \ No newline at end of file diff --git a/theme/pygments/algol_nu.css b/theme/pygments/algol_nu.css deleted file mode 100644 index cbbb271..0000000 --- a/theme/pygments/algol_nu.css +++ /dev/null @@ -1,39 +0,0 @@ -.highlight { background-color: #ffffcc } -.c { color: #888888; font-style: italic } /* Comment */ -.err { border: 1px solid #FF0000 } /* Error */ -.k { font-weight: bold } /* Keyword */ -.ch { color: #888888; font-style: italic } /* Comment.Hashbang */ -.cm { color: #888888; font-style: italic } /* Comment.Multiline */ -.cp { color: #888888; font-weight: bold } /* Comment.Preproc */ -.cpf { color: #888888; font-style: italic } /* Comment.PreprocFile */ -.c1 { color: #888888; font-style: italic } /* Comment.Single */ -.cs { color: #888888; font-weight: bold } /* Comment.Special */ -.kc { font-weight: bold } /* Keyword.Constant */ -.kd { font-weight: bold; font-style: italic } /* Keyword.Declaration */ -.kn { font-weight: bold } /* Keyword.Namespace */ -.kp { font-weight: bold } /* Keyword.Pseudo */ -.kr { font-weight: bold } /* Keyword.Reserved */ -.kt { font-weight: bold } /* Keyword.Type */ -.s { color: #666666; font-style: italic } /* Literal.String */ -.nb { font-weight: bold; font-style: italic } /* Name.Builtin */ -.nc { color: #666666; font-weight: bold; font-style: italic } /* Name.Class */ -.no { color: #666666; font-weight: bold; font-style: italic } /* Name.Constant */ -.nf { color: #666666; font-weight: bold; font-style: italic } /* Name.Function */ -.nn { color: #666666; font-weight: bold; font-style: italic } /* Name.Namespace */ -.nv { color: #666666; font-weight: bold; font-style: italic } /* Name.Variable */ -.ow { font-weight: bold } /* Operator.Word */ -.sb { color: #666666; font-style: italic } /* Literal.String.Backtick */ -.sc { color: #666666; font-style: italic } /* Literal.String.Char */ -.sd { color: #666666; font-style: italic } /* Literal.String.Doc */ -.s2 { color: #666666; font-style: italic } /* Literal.String.Double */ -.se { color: #666666; font-style: italic } /* Literal.String.Escape */ -.sh { color: #666666; font-style: italic } /* Literal.String.Heredoc */ -.si { color: #666666; font-style: italic } /* Literal.String.Interpol */ -.sx { color: #666666; font-style: italic } /* Literal.String.Other */ -.sr { color: #666666; font-style: italic } /* Literal.String.Regex */ -.s1 { color: #666666; font-style: italic } /* Literal.String.Single */ -.ss { color: #666666; font-style: italic } /* Literal.String.Symbol */ -.bp { font-weight: bold; font-style: italic } /* Name.Builtin.Pseudo */ -.vc { color: #666666; font-weight: bold; font-style: italic } /* Name.Variable.Class */ -.vg { color: #666666; font-weight: bold; font-style: italic } /* Name.Variable.Global */ -.vi { color: #666666; font-weight: bold; font-style: italic } /* Name.Variable.Instance */ \ No newline at end of file diff --git a/theme/pygments/algol_nu.min.css b/theme/pygments/algol_nu.min.css deleted file mode 100644 index 1e79262..0000000 --- a/theme/pygments/algol_nu.min.css +++ /dev/null @@ -1 +0,0 @@ -.highlight{background-color:#ffc}.c{color:#888;font-style:italic}.err{border:1px solid red}.k{font-weight:700}.ch,.cm{color:#888;font-style:italic}.cp{color:#888;font-weight:700}.c1,.cpf{color:#888;font-style:italic}.cs{color:#888}.cs,.kc,.kd{font-weight:700}.kd{font-style:italic}.kn,.kp,.kr,.kt{font-weight:700}.s{color:#666;font-style:italic}.nb,.nc{font-weight:700;font-style:italic}.nc{color:#666}.nf,.nn,.no,.nv{color:#666;font-weight:700;font-style:italic}.ow{font-weight:700}.s1,.s2,.sb,.sc,.sd,.se,.sh,.si,.sr,.ss,.sx{color:#666;font-style:italic}.bp,.vc{font-weight:700;font-style:italic}.vc{color:#666}.vg,.vi{color:#666;font-weight:700;font-style:italic} \ No newline at end of file diff --git a/theme/pygments/autumn.css b/theme/pygments/autumn.css deleted file mode 100644 index 4b8fe52..0000000 --- a/theme/pygments/autumn.css +++ /dev/null @@ -1,61 +0,0 @@ -.highlight { background-color: #ffffcc } -.c { color: #aaaaaa; font-style: italic } /* Comment */ -.err { color: #FF0000; background-color: #FFAAAA } /* Error */ -.k { color: #0000aa } /* Keyword */ -.ch { color: #aaaaaa; font-style: italic } /* Comment.Hashbang */ -.cm { color: #aaaaaa; font-style: italic } /* Comment.Multiline */ -.cp { color: #4c8317 } /* Comment.Preproc */ -.cpf { color: #aaaaaa; font-style: italic } /* Comment.PreprocFile */ -.c1 { color: #aaaaaa; font-style: italic } /* Comment.Single */ -.cs { color: #0000aa; font-style: italic } /* Comment.Special */ -.gd { color: #aa0000 } /* Generic.Deleted */ -.ge { font-style: italic } /* Generic.Emph */ -.gr { color: #aa0000 } /* Generic.Error */ -.gh { color: #000080; font-weight: bold } /* Generic.Heading */ -.gi { color: #00aa00 } /* Generic.Inserted */ -.go { color: #888888 } /* Generic.Output */ -.gp { color: #555555 } /* Generic.Prompt */ -.gs { font-weight: bold } /* Generic.Strong */ -.gu { color: #800080; font-weight: bold } /* Generic.Subheading */ -.gt { color: #aa0000 } /* Generic.Traceback */ -.kc { color: #0000aa } /* Keyword.Constant */ -.kd { color: #0000aa } /* Keyword.Declaration */ -.kn { color: #0000aa } /* Keyword.Namespace */ -.kp { color: #0000aa } /* Keyword.Pseudo */ -.kr { color: #0000aa } /* Keyword.Reserved */ -.kt { color: #00aaaa } /* Keyword.Type */ -.m { color: #009999 } /* Literal.Number */ -.s { color: #aa5500 } /* Literal.String */ -.na { color: #1e90ff } /* Name.Attribute */ -.nb { color: #00aaaa } /* Name.Builtin */ -.nc { color: #00aa00; text-decoration: underline } /* Name.Class */ -.no { color: #aa0000 } /* Name.Constant */ -.nd { color: #888888 } /* Name.Decorator */ -.ni { color: #880000; font-weight: bold } /* Name.Entity */ -.nf { color: #00aa00 } /* Name.Function */ -.nn { color: #00aaaa; text-decoration: underline } /* Name.Namespace */ -.nt { color: #1e90ff; font-weight: bold } /* Name.Tag */ -.nv { color: #aa0000 } /* Name.Variable */ -.ow { color: #0000aa } /* Operator.Word */ -.w { color: #bbbbbb } /* Text.Whitespace */ -.mb { color: #009999 } /* Literal.Number.Bin */ -.mf { color: #009999 } /* Literal.Number.Float */ -.mh { color: #009999 } /* Literal.Number.Hex */ -.mi { color: #009999 } /* Literal.Number.Integer */ -.mo { color: #009999 } /* Literal.Number.Oct */ -.sb { color: #aa5500 } /* Literal.String.Backtick */ -.sc { color: #aa5500 } /* Literal.String.Char */ -.sd { color: #aa5500 } /* Literal.String.Doc */ -.s2 { color: #aa5500 } /* Literal.String.Double */ -.se { color: #aa5500 } /* Literal.String.Escape */ -.sh { color: #aa5500 } /* Literal.String.Heredoc */ -.si { color: #aa5500 } /* Literal.String.Interpol */ -.sx { color: #aa5500 } /* Literal.String.Other */ -.sr { color: #009999 } /* Literal.String.Regex */ -.s1 { color: #aa5500 } /* Literal.String.Single */ -.ss { color: #0000aa } /* Literal.String.Symbol */ -.bp { color: #00aaaa } /* Name.Builtin.Pseudo */ -.vc { color: #aa0000 } /* Name.Variable.Class */ -.vg { color: #aa0000 } /* Name.Variable.Global */ -.vi { color: #aa0000 } /* Name.Variable.Instance */ -.il { color: #009999 } /* Literal.Number.Integer.Long */ \ No newline at end of file diff --git a/theme/pygments/autumn.min.css b/theme/pygments/autumn.min.css deleted file mode 100644 index e014095..0000000 --- a/theme/pygments/autumn.min.css +++ /dev/null @@ -1 +0,0 @@ -.highlight{background-color:#ffc}.c{color:#aaa;font-style:italic}.err{color:red;background-color:#faa}.k{color:#00a}.ch,.cm{color:#aaa;font-style:italic}.cp{color:#4c8317}.c1,.cpf{color:#aaa}.c1,.cpf,.cs{font-style:italic}.cs{color:#00a}.gd{color:#a00}.ge{font-style:italic}.gr{color:#a00}.gh{color:navy;font-weight:700}.gi{color:#0a0}.go{color:#888}.gp{color:#555}.gs,.gu{font-weight:700}.gu{color:purple}.gt{color:#a00}.kc,.kd,.kn,.kp,.kr{color:#00a}.kt{color:#0aa}.m{color:#099}.s{color:#a50}.na{color:#1e90ff}.nb{color:#0aa}.nc{color:#0a0;text-decoration:underline}.no{color:#a00}.nd{color:#888}.ni{color:#800;font-weight:700}.nf{color:#0a0}.nn{color:#0aa;text-decoration:underline}.nt{color:#1e90ff;font-weight:700}.nv{color:#a00}.ow{color:#00a}.w{color:#bbb}.mb,.mf,.mh,.mi,.mo{color:#099}.s2,.sb,.sc,.sd,.se,.sh,.si,.sx{color:#a50}.sr{color:#099}.s1{color:#a50}.ss{color:#00a}.bp{color:#0aa}.vc,.vg,.vi{color:#a00}.il{color:#099} \ No newline at end of file diff --git a/theme/pygments/borland.css b/theme/pygments/borland.css deleted file mode 100644 index cdf0b28..0000000 --- a/theme/pygments/borland.css +++ /dev/null @@ -1,49 +0,0 @@ -.highlight { background-color: #ffffcc } -.c { color: #008800; font-style: italic } /* Comment */ -.err { color: #a61717; background-color: #e3d2d2 } /* Error */ -.k { color: #000080; font-weight: bold } /* Keyword */ -.ch { color: #008800; font-style: italic } /* Comment.Hashbang */ -.cm { color: #008800; font-style: italic } /* Comment.Multiline */ -.cp { color: #008080 } /* Comment.Preproc */ -.cpf { color: #008800; font-style: italic } /* Comment.PreprocFile */ -.c1 { color: #008800; font-style: italic } /* Comment.Single */ -.cs { color: #008800; font-weight: bold } /* Comment.Special */ -.gd { color: #000000; background-color: #ffdddd } /* Generic.Deleted */ -.ge { font-style: italic } /* Generic.Emph */ -.gr { color: #aa0000 } /* Generic.Error */ -.gh { color: #999999 } /* Generic.Heading */ -.gi { color: #000000; background-color: #ddffdd } /* Generic.Inserted */ -.go { color: #888888 } /* Generic.Output */ -.gp { color: #555555 } /* Generic.Prompt */ -.gs { font-weight: bold } /* Generic.Strong */ -.gu { color: #aaaaaa } /* Generic.Subheading */ -.gt { color: #aa0000 } /* Generic.Traceback */ -.kc { color: #000080; font-weight: bold } /* Keyword.Constant */ -.kd { color: #000080; font-weight: bold } /* Keyword.Declaration */ -.kn { color: #000080; font-weight: bold } /* Keyword.Namespace */ -.kp { color: #000080; font-weight: bold } /* Keyword.Pseudo */ -.kr { color: #000080; font-weight: bold } /* Keyword.Reserved */ -.kt { color: #000080; font-weight: bold } /* Keyword.Type */ -.m { color: #0000FF } /* Literal.Number */ -.s { color: #0000FF } /* Literal.String */ -.na { color: #FF0000 } /* Name.Attribute */ -.nt { color: #000080; font-weight: bold } /* Name.Tag */ -.ow { font-weight: bold } /* Operator.Word */ -.w { color: #bbbbbb } /* Text.Whitespace */ -.mb { color: #0000FF } /* Literal.Number.Bin */ -.mf { color: #0000FF } /* Literal.Number.Float */ -.mh { color: #0000FF } /* Literal.Number.Hex */ -.mi { color: #0000FF } /* Literal.Number.Integer */ -.mo { color: #0000FF } /* Literal.Number.Oct */ -.sb { color: #0000FF } /* Literal.String.Backtick */ -.sc { color: #800080 } /* Literal.String.Char */ -.sd { color: #0000FF } /* Literal.String.Doc */ -.s2 { color: #0000FF } /* Literal.String.Double */ -.se { color: #0000FF } /* Literal.String.Escape */ -.sh { color: #0000FF } /* Literal.String.Heredoc */ -.si { color: #0000FF } /* Literal.String.Interpol */ -.sx { color: #0000FF } /* Literal.String.Other */ -.sr { color: #0000FF } /* Literal.String.Regex */ -.s1 { color: #0000FF } /* Literal.String.Single */ -.ss { color: #0000FF } /* Literal.String.Symbol */ -.il { color: #0000FF } /* Literal.Number.Integer.Long */ \ No newline at end of file diff --git a/theme/pygments/borland.min.css b/theme/pygments/borland.min.css deleted file mode 100644 index 1be51cc..0000000 --- a/theme/pygments/borland.min.css +++ /dev/null @@ -1 +0,0 @@ -.highlight{background-color:#ffc}.c{color:#080;font-style:italic}.err{color:#a61717;background-color:#e3d2d2}.k{color:navy;font-weight:700}.ch,.cm{color:#080;font-style:italic}.cp{color:teal}.c1,.cpf{color:#080;font-style:italic}.cs{color:#080;font-weight:700}.gd{color:#000;background-color:#fdd}.ge{font-style:italic}.gr{color:#a00}.gh{color:#999}.gi{color:#000;background-color:#dfd}.go{color:#888}.gp{color:#555}.gs{font-weight:700}.gu{color:#aaa}.gt{color:#a00}.kc,.kd,.kn,.kp,.kr,.kt{color:navy;font-weight:700}.m,.s{color:#00f}.na{color:red}.nt{color:navy}.nt,.ow{font-weight:700}.w{color:#bbb}.mb,.mf,.mh,.mi,.mo,.sb{color:#00f}.sc{color:purple}.il,.s1,.s2,.sd,.se,.sh,.si,.sr,.ss,.sx{color:#00f} \ No newline at end of file diff --git a/theme/pygments/bw.css b/theme/pygments/bw.css deleted file mode 100644 index e9d2551..0000000 --- a/theme/pygments/bw.css +++ /dev/null @@ -1,36 +0,0 @@ -.highlight { background-color: #ffffcc } -.c { font-style: italic } /* Comment */ -.err { border: 1px solid #FF0000 } /* Error */ -.k { font-weight: bold } /* Keyword */ -.ch { font-style: italic } /* Comment.Hashbang */ -.cm { font-style: italic } /* Comment.Multiline */ -.cpf { font-style: italic } /* Comment.PreprocFile */ -.c1 { font-style: italic } /* Comment.Single */ -.cs { font-style: italic } /* Comment.Special */ -.ge { font-style: italic } /* Generic.Emph */ -.gh { font-weight: bold } /* Generic.Heading */ -.gp { font-weight: bold } /* Generic.Prompt */ -.gs { font-weight: bold } /* Generic.Strong */ -.gu { font-weight: bold } /* Generic.Subheading */ -.kc { font-weight: bold } /* Keyword.Constant */ -.kd { font-weight: bold } /* Keyword.Declaration */ -.kn { font-weight: bold } /* Keyword.Namespace */ -.kr { font-weight: bold } /* Keyword.Reserved */ -.s { font-style: italic } /* Literal.String */ -.nc { font-weight: bold } /* Name.Class */ -.ni { font-weight: bold } /* Name.Entity */ -.ne { font-weight: bold } /* Name.Exception */ -.nn { font-weight: bold } /* Name.Namespace */ -.nt { font-weight: bold } /* Name.Tag */ -.ow { font-weight: bold } /* Operator.Word */ -.sb { font-style: italic } /* Literal.String.Backtick */ -.sc { font-style: italic } /* Literal.String.Char */ -.sd { font-style: italic } /* Literal.String.Doc */ -.s2 { font-style: italic } /* Literal.String.Double */ -.se { font-weight: bold; font-style: italic } /* Literal.String.Escape */ -.sh { font-style: italic } /* Literal.String.Heredoc */ -.si { font-weight: bold; font-style: italic } /* Literal.String.Interpol */ -.sx { font-style: italic } /* Literal.String.Other */ -.sr { font-style: italic } /* Literal.String.Regex */ -.s1 { font-style: italic } /* Literal.String.Single */ -.ss { font-style: italic } /* Literal.String.Symbol */ \ No newline at end of file diff --git a/theme/pygments/bw.min.css b/theme/pygments/bw.min.css deleted file mode 100644 index a8965bf..0000000 --- a/theme/pygments/bw.min.css +++ /dev/null @@ -1 +0,0 @@ -.highlight{background-color:#ffc}.c{font-style:italic}.err{border:1px solid red}.k{font-weight:700}.c1,.ch,.cm,.cpf,.cs,.ge{font-style:italic}.gh,.gp,.gs,.gu,.kc,.kd,.kn,.kr{font-weight:700}.s{font-style:italic}.nc,.ne,.ni,.nn,.nt,.ow{font-weight:700}.s2,.sb,.sc,.sd,.se{font-style:italic}.se{font-weight:700}.sh,.si{font-style:italic}.si{font-weight:700}.s1,.sr,.ss,.sx{font-style:italic} \ No newline at end of file diff --git a/theme/pygments/colorful.css b/theme/pygments/colorful.css deleted file mode 100644 index 6d73d55..0000000 --- a/theme/pygments/colorful.css +++ /dev/null @@ -1,64 +0,0 @@ -.highlight { background-color: #ffffcc } -.c { color: #888888 } /* Comment */ -.err { color: #FF0000; background-color: #FFAAAA } /* Error */ -.k { color: #008800; font-weight: bold } /* Keyword */ -.o { color: #333333 } /* Operator */ -.ch { color: #888888 } /* Comment.Hashbang */ -.cm { color: #888888 } /* Comment.Multiline */ -.cp { color: #557799 } /* Comment.Preproc */ -.cpf { color: #888888 } /* Comment.PreprocFile */ -.c1 { color: #888888 } /* Comment.Single */ -.cs { color: #cc0000; font-weight: bold } /* Comment.Special */ -.gd { color: #A00000 } /* Generic.Deleted */ -.ge { font-style: italic } /* Generic.Emph */ -.gr { color: #FF0000 } /* Generic.Error */ -.gh { color: #000080; font-weight: bold } /* Generic.Heading */ -.gi { color: #00A000 } /* Generic.Inserted */ -.go { color: #888888 } /* Generic.Output */ -.gp { color: #c65d09; font-weight: bold } /* Generic.Prompt */ -.gs { font-weight: bold } /* Generic.Strong */ -.gu { color: #800080; font-weight: bold } /* Generic.Subheading */ -.gt { color: #0044DD } /* Generic.Traceback */ -.kc { color: #008800; font-weight: bold } /* Keyword.Constant */ -.kd { color: #008800; font-weight: bold } /* Keyword.Declaration */ -.kn { color: #008800; font-weight: bold } /* Keyword.Namespace */ -.kp { color: #003388; font-weight: bold } /* Keyword.Pseudo */ -.kr { color: #008800; font-weight: bold } /* Keyword.Reserved */ -.kt { color: #333399; font-weight: bold } /* Keyword.Type */ -.m { color: #6600EE; font-weight: bold } /* Literal.Number */ -.s { background-color: #fff0f0 } /* Literal.String */ -.na { color: #0000CC } /* Name.Attribute */ -.nb { color: #007020 } /* Name.Builtin */ -.nc { color: #BB0066; font-weight: bold } /* Name.Class */ -.no { color: #003366; font-weight: bold } /* Name.Constant */ -.nd { color: #555555; font-weight: bold } /* Name.Decorator */ -.ni { color: #880000; font-weight: bold } /* Name.Entity */ -.ne { color: #FF0000; font-weight: bold } /* Name.Exception */ -.nf { color: #0066BB; font-weight: bold } /* Name.Function */ -.nl { color: #997700; font-weight: bold } /* Name.Label */ -.nn { color: #0e84b5; font-weight: bold } /* Name.Namespace */ -.nt { color: #007700 } /* Name.Tag */ -.nv { color: #996633 } /* Name.Variable */ -.ow { color: #000000; font-weight: bold } /* Operator.Word */ -.w { color: #bbbbbb } /* Text.Whitespace */ -.mb { color: #6600EE; font-weight: bold } /* Literal.Number.Bin */ -.mf { color: #6600EE; font-weight: bold } /* Literal.Number.Float */ -.mh { color: #005588; font-weight: bold } /* Literal.Number.Hex */ -.mi { color: #0000DD; font-weight: bold } /* Literal.Number.Integer */ -.mo { color: #4400EE; font-weight: bold } /* Literal.Number.Oct */ -.sb { background-color: #fff0f0 } /* Literal.String.Backtick */ -.sc { color: #0044DD } /* Literal.String.Char */ -.sd { color: #DD4422 } /* Literal.String.Doc */ -.s2 { background-color: #fff0f0 } /* Literal.String.Double */ -.se { color: #666666; font-weight: bold; background-color: #fff0f0 } /* Literal.String.Escape */ -.sh { background-color: #fff0f0 } /* Literal.String.Heredoc */ -.si { background-color: #eeeeee } /* Literal.String.Interpol */ -.sx { color: #DD2200; background-color: #fff0f0 } /* Literal.String.Other */ -.sr { color: #000000; background-color: #fff0ff } /* Literal.String.Regex */ -.s1 { background-color: #fff0f0 } /* Literal.String.Single */ -.ss { color: #AA6600 } /* Literal.String.Symbol */ -.bp { color: #007020 } /* Name.Builtin.Pseudo */ -.vc { color: #336699 } /* Name.Variable.Class */ -.vg { color: #dd7700; font-weight: bold } /* Name.Variable.Global */ -.vi { color: #3333BB } /* Name.Variable.Instance */ -.il { color: #0000DD; font-weight: bold } /* Literal.Number.Integer.Long */ \ No newline at end of file diff --git a/theme/pygments/colorful.min.css b/theme/pygments/colorful.min.css deleted file mode 100644 index cec1bbd..0000000 --- a/theme/pygments/colorful.min.css +++ /dev/null @@ -1 +0,0 @@ -.highlight{background-color:#ffc}.c{color:#888}.err{color:red;background-color:#faa}.k{color:#080;font-weight:700}.o{color:#333}.ch,.cm{color:#888}.cp{color:#579}.c1,.cpf{color:#888}.cs{color:#c00;font-weight:700}.gd{color:#a00000}.ge{font-style:italic}.gr{color:red}.gh{color:navy;font-weight:700}.gi{color:#00a000}.go{color:#888}.gp{color:#c65d09}.gp,.gs,.gu{font-weight:700}.gu{color:purple}.gt{color:#04d}.kc,.kd,.kn{color:#080;font-weight:700}.kp{color:#038}.kp,.kr{font-weight:700}.kr{color:#080}.kt{color:#339}.kt,.m{font-weight:700}.m{color:#60e}.s{background-color:#fff0f0}.na{color:#00c}.nb{color:#007020}.nc{color:#b06}.nc,.no{font-weight:700}.no{color:#036}.nd{color:#555}.nd,.ni{font-weight:700}.ni{color:#800}.ne{color:red}.ne,.nf{font-weight:700}.nf{color:#06b}.nl{color:#970}.nl,.nn{font-weight:700}.nn{color:#0e84b5}.nt{color:#070}.nv{color:#963}.ow{color:#000;font-weight:700}.w{color:#bbb}.mb,.mf{color:#60e}.mb,.mf,.mh{font-weight:700}.mh{color:#058}.mi{color:#00d}.mi,.mo{font-weight:700}.mo{color:#40e}.sb{background-color:#fff0f0}.sc{color:#04d}.sd{color:#d42}.s2,.se{background-color:#fff0f0}.se{color:#666;font-weight:700}.sh{background-color:#fff0f0}.si{background-color:#eee}.sx{color:#d20;background-color:#fff0f0}.sr{color:#000;background-color:#fff0ff}.s1{background-color:#fff0f0}.ss{color:#a60}.bp{color:#007020}.vc{color:#369}.vg{color:#d70;font-weight:700}.vi{color:#33b}.il{color:#00d;font-weight:700} \ No newline at end of file diff --git a/theme/pygments/default.css b/theme/pygments/default.css deleted file mode 100644 index a342ba0..0000000 --- a/theme/pygments/default.css +++ /dev/null @@ -1,64 +0,0 @@ -.highlight { background-color: #ffffcc } -.c { color: #408080; font-style: italic } /* Comment */ -.err { border: 1px solid #FF0000 } /* Error */ -.k { color: #008000; font-weight: bold } /* Keyword */ -.o { color: #666666 } /* Operator */ -.ch { color: #408080; font-style: italic } /* Comment.Hashbang */ -.cm { color: #408080; font-style: italic } /* Comment.Multiline */ -.cp { color: #BC7A00 } /* Comment.Preproc */ -.cpf { color: #408080; font-style: italic } /* Comment.PreprocFile */ -.c1 { color: #408080; font-style: italic } /* Comment.Single */ -.cs { color: #408080; font-style: italic } /* Comment.Special */ -.gd { color: #A00000 } /* Generic.Deleted */ -.ge { font-style: italic } /* Generic.Emph */ -.gr { color: #FF0000 } /* Generic.Error */ -.gh { color: #000080; font-weight: bold } /* Generic.Heading */ -.gi { color: #00A000 } /* Generic.Inserted */ -.go { color: #888888 } /* Generic.Output */ -.gp { color: #000080; font-weight: bold } /* Generic.Prompt */ -.gs { font-weight: bold } /* Generic.Strong */ -.gu { color: #800080; font-weight: bold } /* Generic.Subheading */ -.gt { color: #0044DD } /* Generic.Traceback */ -.kc { color: #008000; font-weight: bold } /* Keyword.Constant */ -.kd { color: #008000; font-weight: bold } /* Keyword.Declaration */ -.kn { color: #008000; font-weight: bold } /* Keyword.Namespace */ -.kp { color: #008000 } /* Keyword.Pseudo */ -.kr { color: #008000; font-weight: bold } /* Keyword.Reserved */ -.kt { color: #B00040 } /* Keyword.Type */ -.m { color: #666666 } /* Literal.Number */ -.s { color: #BA2121 } /* Literal.String */ -.na { color: #7D9029 } /* Name.Attribute */ -.nb { color: #008000 } /* Name.Builtin */ -.nc { color: #0000FF; font-weight: bold } /* Name.Class */ -.no { color: #880000 } /* Name.Constant */ -.nd { color: #AA22FF } /* Name.Decorator */ -.ni { color: #999999; font-weight: bold } /* Name.Entity */ -.ne { color: #D2413A; font-weight: bold } /* Name.Exception */ -.nf { color: #0000FF } /* Name.Function */ -.nl { color: #A0A000 } /* Name.Label */ -.nn { color: #0000FF; font-weight: bold } /* Name.Namespace */ -.nt { color: #008000; font-weight: bold } /* Name.Tag */ -.nv { color: #19177C } /* Name.Variable */ -.ow { color: #AA22FF; font-weight: bold } /* Operator.Word */ -.w { color: #bbbbbb } /* Text.Whitespace */ -.mb { color: #666666 } /* Literal.Number.Bin */ -.mf { color: #666666 } /* Literal.Number.Float */ -.mh { color: #666666 } /* Literal.Number.Hex */ -.mi { color: #666666 } /* Literal.Number.Integer */ -.mo { color: #666666 } /* Literal.Number.Oct */ -.sb { color: #BA2121 } /* Literal.String.Backtick */ -.sc { color: #BA2121 } /* Literal.String.Char */ -.sd { color: #BA2121; font-style: italic } /* Literal.String.Doc */ -.s2 { color: #BA2121 } /* Literal.String.Double */ -.se { color: #BB6622; font-weight: bold } /* Literal.String.Escape */ -.sh { color: #BA2121 } /* Literal.String.Heredoc */ -.si { color: #BB6688; font-weight: bold } /* Literal.String.Interpol */ -.sx { color: #008000 } /* Literal.String.Other */ -.sr { color: #BB6688 } /* Literal.String.Regex */ -.s1 { color: #BA2121 } /* Literal.String.Single */ -.ss { color: #19177C } /* Literal.String.Symbol */ -.bp { color: #008000 } /* Name.Builtin.Pseudo */ -.vc { color: #19177C } /* Name.Variable.Class */ -.vg { color: #19177C } /* Name.Variable.Global */ -.vi { color: #19177C } /* Name.Variable.Instance */ -.il { color: #666666 } /* Literal.Number.Integer.Long */ \ No newline at end of file diff --git a/theme/pygments/default.min.css b/theme/pygments/default.min.css deleted file mode 100644 index 86f44e7..0000000 --- a/theme/pygments/default.min.css +++ /dev/null @@ -1 +0,0 @@ -.highlight{background-color:#ffc}.c{color:#408080;font-style:italic}.err{border:1px solid red}.k{color:green;font-weight:700}.o{color:#666}.ch,.cm{color:#408080;font-style:italic}.cp{color:#bc7a00}.c1,.cpf,.cs{color:#408080;font-style:italic}.gd{color:#a00000}.ge{font-style:italic}.gr{color:red}.gh{color:navy;font-weight:700}.gi{color:#00a000}.go{color:#888}.gp{color:navy}.gp,.gs,.gu{font-weight:700}.gu{color:purple}.gt{color:#04d}.kc,.kd,.kn{color:green;font-weight:700}.kp,.kr{color:green}.kr{font-weight:700}.kt{color:#b00040}.m{color:#666}.s{color:#ba2121}.na{color:#7d9029}.nb{color:green}.nc{color:#00f;font-weight:700}.no{color:#800}.nd{color:#a2f}.ni{color:#999}.ne,.ni{font-weight:700}.ne{color:#d2413a}.nf{color:#00f}.nl{color:#a0a000}.nn{color:#00f}.nn,.nt{font-weight:700}.nt{color:green}.nv{color:#19177c}.ow{color:#a2f;font-weight:700}.w{color:#bbb}.mb,.mf,.mh,.mi,.mo{color:#666}.sb,.sc,.sd{color:#ba2121}.sd{font-style:italic}.s2{color:#ba2121}.se{color:#b62;font-weight:700}.sh{color:#ba2121}.si{color:#b68;font-weight:700}.sx{color:green}.sr{color:#b68}.s1{color:#ba2121}.ss{color:#19177c}.bp{color:green}.vc,.vg,.vi{color:#19177c}.il{color:#666} \ No newline at end of file diff --git a/theme/pygments/emacs.css b/theme/pygments/emacs.css deleted file mode 100644 index b28c685..0000000 --- a/theme/pygments/emacs.css +++ /dev/null @@ -1,64 +0,0 @@ -.highlight { background-color: #ffffcc } -.c { color: #008800; font-style: italic } /* Comment */ -.err { border: 1px solid #FF0000 } /* Error */ -.k { color: #AA22FF; font-weight: bold } /* Keyword */ -.o { color: #666666 } /* Operator */ -.ch { color: #008800; font-style: italic } /* Comment.Hashbang */ -.cm { color: #008800; font-style: italic } /* Comment.Multiline */ -.cp { color: #008800 } /* Comment.Preproc */ -.cpf { color: #008800; font-style: italic } /* Comment.PreprocFile */ -.c1 { color: #008800; font-style: italic } /* Comment.Single */ -.cs { color: #008800; font-weight: bold } /* Comment.Special */ -.gd { color: #A00000 } /* Generic.Deleted */ -.ge { font-style: italic } /* Generic.Emph */ -.gr { color: #FF0000 } /* Generic.Error */ -.gh { color: #000080; font-weight: bold } /* Generic.Heading */ -.gi { color: #00A000 } /* Generic.Inserted */ -.go { color: #888888 } /* Generic.Output */ -.gp { color: #000080; font-weight: bold } /* Generic.Prompt */ -.gs { font-weight: bold } /* Generic.Strong */ -.gu { color: #800080; font-weight: bold } /* Generic.Subheading */ -.gt { color: #0044DD } /* Generic.Traceback */ -.kc { color: #AA22FF; font-weight: bold } /* Keyword.Constant */ -.kd { color: #AA22FF; font-weight: bold } /* Keyword.Declaration */ -.kn { color: #AA22FF; font-weight: bold } /* Keyword.Namespace */ -.kp { color: #AA22FF } /* Keyword.Pseudo */ -.kr { color: #AA22FF; font-weight: bold } /* Keyword.Reserved */ -.kt { color: #00BB00; font-weight: bold } /* Keyword.Type */ -.m { color: #666666 } /* Literal.Number */ -.s { color: #BB4444 } /* Literal.String */ -.na { color: #BB4444 } /* Name.Attribute */ -.nb { color: #AA22FF } /* Name.Builtin */ -.nc { color: #0000FF } /* Name.Class */ -.no { color: #880000 } /* Name.Constant */ -.nd { color: #AA22FF } /* Name.Decorator */ -.ni { color: #999999; font-weight: bold } /* Name.Entity */ -.ne { color: #D2413A; font-weight: bold } /* Name.Exception */ -.nf { color: #00A000 } /* Name.Function */ -.nl { color: #A0A000 } /* Name.Label */ -.nn { color: #0000FF; font-weight: bold } /* Name.Namespace */ -.nt { color: #008000; font-weight: bold } /* Name.Tag */ -.nv { color: #B8860B } /* Name.Variable */ -.ow { color: #AA22FF; font-weight: bold } /* Operator.Word */ -.w { color: #bbbbbb } /* Text.Whitespace */ -.mb { color: #666666 } /* Literal.Number.Bin */ -.mf { color: #666666 } /* Literal.Number.Float */ -.mh { color: #666666 } /* Literal.Number.Hex */ -.mi { color: #666666 } /* Literal.Number.Integer */ -.mo { color: #666666 } /* Literal.Number.Oct */ -.sb { color: #BB4444 } /* Literal.String.Backtick */ -.sc { color: #BB4444 } /* Literal.String.Char */ -.sd { color: #BB4444; font-style: italic } /* Literal.String.Doc */ -.s2 { color: #BB4444 } /* Literal.String.Double */ -.se { color: #BB6622; font-weight: bold } /* Literal.String.Escape */ -.sh { color: #BB4444 } /* Literal.String.Heredoc */ -.si { color: #BB6688; font-weight: bold } /* Literal.String.Interpol */ -.sx { color: #008000 } /* Literal.String.Other */ -.sr { color: #BB6688 } /* Literal.String.Regex */ -.s1 { color: #BB4444 } /* Literal.String.Single */ -.ss { color: #B8860B } /* Literal.String.Symbol */ -.bp { color: #AA22FF } /* Name.Builtin.Pseudo */ -.vc { color: #B8860B } /* Name.Variable.Class */ -.vg { color: #B8860B } /* Name.Variable.Global */ -.vi { color: #B8860B } /* Name.Variable.Instance */ -.il { color: #666666 } /* Literal.Number.Integer.Long */ \ No newline at end of file diff --git a/theme/pygments/emacs.min.css b/theme/pygments/emacs.min.css deleted file mode 100644 index 18d9979..0000000 --- a/theme/pygments/emacs.min.css +++ /dev/null @@ -1 +0,0 @@ -.highlight{background-color:#ffc}.c{color:#080;font-style:italic}.err{border:1px solid red}.k{color:#a2f;font-weight:700}.o{color:#666}.ch,.cm{font-style:italic}.ch,.cm,.cp{color:#080}.c1,.cpf{color:#080;font-style:italic}.cs{color:#080;font-weight:700}.gd{color:#a00000}.ge{font-style:italic}.gr{color:red}.gh{color:navy;font-weight:700}.gi{color:#00a000}.go{color:#888}.gp{color:navy}.gp,.gs,.gu{font-weight:700}.gu{color:purple}.gt{color:#04d}.kc,.kd,.kn{color:#a2f;font-weight:700}.kp,.kr{color:#a2f}.kr,.kt{font-weight:700}.kt{color:#0b0}.m{color:#666}.na,.s{color:#b44}.nb{color:#a2f}.nc{color:#00f}.no{color:#800}.nd{color:#a2f}.ni{color:#999}.ne,.ni{font-weight:700}.ne{color:#d2413a}.nf{color:#00a000}.nl{color:#a0a000}.nn{color:#00f}.nn,.nt{font-weight:700}.nt{color:green}.nv{color:#b8860b}.ow{color:#a2f;font-weight:700}.w{color:#bbb}.mb,.mf,.mh,.mi,.mo{color:#666}.sb,.sc,.sd{color:#b44}.sd{font-style:italic}.s2{color:#b44}.se{color:#b62;font-weight:700}.sh{color:#b44}.si{color:#b68;font-weight:700}.sx{color:green}.sr{color:#b68}.s1{color:#b44}.ss{color:#b8860b}.bp{color:#a2f}.vc,.vg,.vi{color:#b8860b}.il{color:#666} \ No newline at end of file diff --git a/theme/pygments/friendly.css b/theme/pygments/friendly.css deleted file mode 100644 index 9a155b4..0000000 --- a/theme/pygments/friendly.css +++ /dev/null @@ -1,64 +0,0 @@ -.highlight { background-color: #ffffcc } -.c { color: #60a0b0; font-style: italic } /* Comment */ -.err { border: 1px solid #FF0000 } /* Error */ -.k { color: #007020; font-weight: bold } /* Keyword */ -.o { color: #666666 } /* Operator */ -.ch { color: #60a0b0; font-style: italic } /* Comment.Hashbang */ -.cm { color: #60a0b0; font-style: italic } /* Comment.Multiline */ -.cp { color: #007020 } /* Comment.Preproc */ -.cpf { color: #60a0b0; font-style: italic } /* Comment.PreprocFile */ -.c1 { color: #60a0b0; font-style: italic } /* Comment.Single */ -.cs { color: #60a0b0; background-color: #fff0f0 } /* Comment.Special */ -.gd { color: #A00000 } /* Generic.Deleted */ -.ge { font-style: italic } /* Generic.Emph */ -.gr { color: #FF0000 } /* Generic.Error */ -.gh { color: #000080; font-weight: bold } /* Generic.Heading */ -.gi { color: #00A000 } /* Generic.Inserted */ -.go { color: #888888 } /* Generic.Output */ -.gp { color: #c65d09; font-weight: bold } /* Generic.Prompt */ -.gs { font-weight: bold } /* Generic.Strong */ -.gu { color: #800080; font-weight: bold } /* Generic.Subheading */ -.gt { color: #0044DD } /* Generic.Traceback */ -.kc { color: #007020; font-weight: bold } /* Keyword.Constant */ -.kd { color: #007020; font-weight: bold } /* Keyword.Declaration */ -.kn { color: #007020; font-weight: bold } /* Keyword.Namespace */ -.kp { color: #007020 } /* Keyword.Pseudo */ -.kr { color: #007020; font-weight: bold } /* Keyword.Reserved */ -.kt { color: #902000 } /* Keyword.Type */ -.m { color: #40a070 } /* Literal.Number */ -.s { color: #4070a0 } /* Literal.String */ -.na { color: #4070a0 } /* Name.Attribute */ -.nb { color: #007020 } /* Name.Builtin */ -.nc { color: #0e84b5; font-weight: bold } /* Name.Class */ -.no { color: #60add5 } /* Name.Constant */ -.nd { color: #555555; font-weight: bold } /* Name.Decorator */ -.ni { color: #d55537; font-weight: bold } /* Name.Entity */ -.ne { color: #007020 } /* Name.Exception */ -.nf { color: #06287e } /* Name.Function */ -.nl { color: #002070; font-weight: bold } /* Name.Label */ -.nn { color: #0e84b5; font-weight: bold } /* Name.Namespace */ -.nt { color: #062873; font-weight: bold } /* Name.Tag */ -.nv { color: #bb60d5 } /* Name.Variable */ -.ow { color: #007020; font-weight: bold } /* Operator.Word */ -.w { color: #bbbbbb } /* Text.Whitespace */ -.mb { color: #40a070 } /* Literal.Number.Bin */ -.mf { color: #40a070 } /* Literal.Number.Float */ -.mh { color: #40a070 } /* Literal.Number.Hex */ -.mi { color: #40a070 } /* Literal.Number.Integer */ -.mo { color: #40a070 } /* Literal.Number.Oct */ -.sb { color: #4070a0 } /* Literal.String.Backtick */ -.sc { color: #4070a0 } /* Literal.String.Char */ -.sd { color: #4070a0; font-style: italic } /* Literal.String.Doc */ -.s2 { color: #4070a0 } /* Literal.String.Double */ -.se { color: #4070a0; font-weight: bold } /* Literal.String.Escape */ -.sh { color: #4070a0 } /* Literal.String.Heredoc */ -.si { color: #70a0d0; font-style: italic } /* Literal.String.Interpol */ -.sx { color: #c65d09 } /* Literal.String.Other */ -.sr { color: #235388 } /* Literal.String.Regex */ -.s1 { color: #4070a0 } /* Literal.String.Single */ -.ss { color: #517918 } /* Literal.String.Symbol */ -.bp { color: #007020 } /* Name.Builtin.Pseudo */ -.vc { color: #bb60d5 } /* Name.Variable.Class */ -.vg { color: #bb60d5 } /* Name.Variable.Global */ -.vi { color: #bb60d5 } /* Name.Variable.Instance */ -.il { color: #40a070 } /* Literal.Number.Integer.Long */ \ No newline at end of file diff --git a/theme/pygments/friendly.min.css b/theme/pygments/friendly.min.css deleted file mode 100644 index b0ccee2..0000000 --- a/theme/pygments/friendly.min.css +++ /dev/null @@ -1 +0,0 @@ -.highlight{background-color:#ffc}.c{color:#60a0b0;font-style:italic}.err{border:1px solid red}.k{color:#007020;font-weight:700}.o{color:#666}.ch,.cm{color:#60a0b0;font-style:italic}.cp{color:#007020}.c1,.cpf{font-style:italic}.c1,.cpf,.cs{color:#60a0b0}.cs{background-color:#fff0f0}.gd{color:#a00000}.ge{font-style:italic}.gr{color:red}.gh{color:navy;font-weight:700}.gi{color:#00a000}.go{color:#888}.gp{color:#c65d09}.gp,.gs,.gu{font-weight:700}.gu{color:purple}.gt{color:#04d}.kc,.kd,.kn{font-weight:700}.kc,.kd,.kn,.kp,.kr{color:#007020}.kr{font-weight:700}.kt{color:#902000}.m{color:#40a070}.na,.s{color:#4070a0}.nb{color:#007020}.nc{color:#0e84b5;font-weight:700}.no{color:#60add5}.nd{color:#555}.nd,.ni{font-weight:700}.ni{color:#d55537}.ne{color:#007020}.nf{color:#06287e}.nl{color:#002070}.nl,.nn{font-weight:700}.nn{color:#0e84b5}.nt{color:#062873;font-weight:700}.nv{color:#bb60d5}.ow{color:#007020;font-weight:700}.w{color:#bbb}.mb,.mf,.mh,.mi,.mo{color:#40a070}.sb,.sc,.sd{color:#4070a0}.sd{font-style:italic}.s2,.se{color:#4070a0}.se{font-weight:700}.sh{color:#4070a0}.si{color:#70a0d0;font-style:italic}.sx{color:#c65d09}.sr{color:#235388}.s1{color:#4070a0}.ss{color:#517918}.bp{color:#007020}.vc,.vg,.vi{color:#bb60d5}.il{color:#40a070} \ No newline at end of file diff --git a/theme/pygments/fruity.css b/theme/pygments/fruity.css deleted file mode 100644 index 033e274..0000000 --- a/theme/pygments/fruity.css +++ /dev/null @@ -1,73 +0,0 @@ -.highlight { background-color: #333333 } -.c { color: #008800; font-style: italic; background-color: #0f140f } /* Comment */ -.err { color: #ffffff } /* Error */ -.esc { color: #ffffff } /* Escape */ -.g { color: #ffffff } /* Generic */ -.k { color: #fb660a; font-weight: bold } /* Keyword */ -.l { color: #ffffff } /* Literal */ -.n { color: #ffffff } /* Name */ -.o { color: #ffffff } /* Operator */ -.x { color: #ffffff } /* Other */ -.p { color: #ffffff } /* Punctuation */ -.ch { color: #008800; font-style: italic; background-color: #0f140f } /* Comment.Hashbang */ -.cm { color: #008800; font-style: italic; background-color: #0f140f } /* Comment.Multiline */ -.cp { color: #ff0007; font-weight: bold; font-style: italic; background-color: #0f140f } /* Comment.Preproc */ -.cpf { color: #008800; font-style: italic; background-color: #0f140f } /* Comment.PreprocFile */ -.c1 { color: #008800; font-style: italic; background-color: #0f140f } /* Comment.Single */ -.cs { color: #008800; font-style: italic; background-color: #0f140f } /* Comment.Special */ -.gd { color: #ffffff } /* Generic.Deleted */ -.ge { color: #ffffff } /* Generic.Emph */ -.gr { color: #ffffff } /* Generic.Error */ -.gh { color: #ffffff; font-weight: bold } /* Generic.Heading */ -.gi { color: #ffffff } /* Generic.Inserted */ -.go { color: #444444; background-color: #222222 } /* Generic.Output */ -.gp { color: #ffffff } /* Generic.Prompt */ -.gs { color: #ffffff } /* Generic.Strong */ -.gu { color: #ffffff; font-weight: bold } /* Generic.Subheading */ -.gt { color: #ffffff } /* Generic.Traceback */ -.kc { color: #fb660a; font-weight: bold } /* Keyword.Constant */ -.kd { color: #fb660a; font-weight: bold } /* Keyword.Declaration */ -.kn { color: #fb660a; font-weight: bold } /* Keyword.Namespace */ -.kp { color: #fb660a } /* Keyword.Pseudo */ -.kr { color: #fb660a; font-weight: bold } /* Keyword.Reserved */ -.kt { color: #cdcaa9; font-weight: bold } /* Keyword.Type */ -.ld { color: #ffffff } /* Literal.Date */ -.m { color: #0086f7; font-weight: bold } /* Literal.Number */ -.s { color: #0086d2 } /* Literal.String */ -.na { color: #ff0086; font-weight: bold } /* Name.Attribute */ -.nb { color: #ffffff } /* Name.Builtin */ -.nc { color: #ffffff } /* Name.Class */ -.no { color: #0086d2 } /* Name.Constant */ -.nd { color: #ffffff } /* Name.Decorator */ -.ni { color: #ffffff } /* Name.Entity */ -.ne { color: #ffffff } /* Name.Exception */ -.nf { color: #ff0086; font-weight: bold } /* Name.Function */ -.nl { color: #ffffff } /* Name.Label */ -.nn { color: #ffffff } /* Name.Namespace */ -.nx { color: #ffffff } /* Name.Other */ -.py { color: #ffffff } /* Name.Property */ -.nt { color: #fb660a; font-weight: bold } /* Name.Tag */ -.nv { color: #fb660a } /* Name.Variable */ -.ow { color: #ffffff } /* Operator.Word */ -.w { color: #888888 } /* Text.Whitespace */ -.mb { color: #0086f7; font-weight: bold } /* Literal.Number.Bin */ -.mf { color: #0086f7; font-weight: bold } /* Literal.Number.Float */ -.mh { color: #0086f7; font-weight: bold } /* Literal.Number.Hex */ -.mi { color: #0086f7; font-weight: bold } /* Literal.Number.Integer */ -.mo { color: #0086f7; font-weight: bold } /* Literal.Number.Oct */ -.sb { color: #0086d2 } /* Literal.String.Backtick */ -.sc { color: #0086d2 } /* Literal.String.Char */ -.sd { color: #0086d2 } /* Literal.String.Doc */ -.s2 { color: #0086d2 } /* Literal.String.Double */ -.se { color: #0086d2 } /* Literal.String.Escape */ -.sh { color: #0086d2 } /* Literal.String.Heredoc */ -.si { color: #0086d2 } /* Literal.String.Interpol */ -.sx { color: #0086d2 } /* Literal.String.Other */ -.sr { color: #0086d2 } /* Literal.String.Regex */ -.s1 { color: #0086d2 } /* Literal.String.Single */ -.ss { color: #0086d2 } /* Literal.String.Symbol */ -.bp { color: #ffffff } /* Name.Builtin.Pseudo */ -.vc { color: #fb660a } /* Name.Variable.Class */ -.vg { color: #fb660a } /* Name.Variable.Global */ -.vi { color: #fb660a } /* Name.Variable.Instance */ -.il { color: #0086f7; font-weight: bold } /* Literal.Number.Integer.Long */ \ No newline at end of file diff --git a/theme/pygments/fruity.min.css b/theme/pygments/fruity.min.css deleted file mode 100644 index 6220f05..0000000 --- a/theme/pygments/fruity.min.css +++ /dev/null @@ -1 +0,0 @@ -.highlight{background-color:#333}.c{color:#080;font-style:italic;background-color:#0f140f}.err,.esc,.g{color:#fff}.k{color:#fb660a;font-weight:700}.l,.n,.o,.p,.x{color:#fff}.ch,.cm{color:#080}.ch,.cm,.cp{font-style:italic;background-color:#0f140f}.cp{color:#ff0007;font-weight:700}.c1,.cpf,.cs{color:#080;font-style:italic;background-color:#0f140f}.gd,.ge,.gh,.gr{color:#fff}.gh{font-weight:700}.gi{color:#fff}.go{color:#444;background-color:#222}.gp,.gs,.gu{color:#fff}.gu{font-weight:700}.gt{color:#fff}.kc,.kd,.kn{font-weight:700}.kc,.kd,.kn,.kp,.kr{color:#fb660a}.kr,.kt{font-weight:700}.kt{color:#cdcaa9}.ld{color:#fff}.m{color:#0086f7;font-weight:700}.s{color:#0086d2}.na{color:#ff0086;font-weight:700}.nb,.nc{color:#fff}.no{color:#0086d2}.nd,.ne,.ni{color:#fff}.nf{color:#ff0086;font-weight:700}.nl,.nn,.nx,.py{color:#fff}.nt{font-weight:700}.nt,.nv{color:#fb660a}.ow{color:#fff}.w{color:#888}.mb,.mf,.mh,.mi,.mo{color:#0086f7;font-weight:700}.s1,.s2,.sb,.sc,.sd,.se,.sh,.si,.sr,.ss,.sx{color:#0086d2}.bp{color:#fff}.vc,.vg,.vi{color:#fb660a}.il{color:#0086f7;font-weight:700} \ No newline at end of file diff --git a/theme/pygments/github.css b/theme/pygments/github.css deleted file mode 100644 index 139ae86..0000000 --- a/theme/pygments/github.css +++ /dev/null @@ -1,64 +0,0 @@ -.highlight { background-color: #ffffcc } -.c { color: #999988; font-style: italic } /* Comment */ -.err { color: #a61717; background-color: #e3d2d2 } /* Error */ -.k { color: #000000; font-weight: bold } /* Keyword */ -.o { color: #000000; font-weight: bold } /* Operator */ -.ch { color: #999988; font-style: italic } /* Comment.Hashbang */ -.cm { color: #999988; font-style: italic } /* Comment.Multiline */ -.cp { color: #999999; font-weight: bold; font-style: italic } /* Comment.Preproc */ -.cpf { color: #999988; font-style: italic } /* Comment.PreprocFile */ -.c1 { color: #999988; font-style: italic } /* Comment.Single */ -.cs { color: #999999; font-weight: bold; font-style: italic } /* Comment.Special */ -.gd { color: #000000; background-color: #ffdddd } /* Generic.Deleted */ -.ge { color: #000000; font-style: italic } /* Generic.Emph */ -.gr { color: #aa0000 } /* Generic.Error */ -.gh { color: #999999 } /* Generic.Heading */ -.gi { color: #000000; background-color: #ddffdd } /* Generic.Inserted */ -.go { color: #888888 } /* Generic.Output */ -.gp { color: #555555 } /* Generic.Prompt */ -.gs { font-weight: bold } /* Generic.Strong */ -.gu { color: #aaaaaa } /* Generic.Subheading */ -.gt { color: #aa0000 } /* Generic.Traceback */ -.kc { color: #000000; font-weight: bold } /* Keyword.Constant */ -.kd { color: #000000; font-weight: bold } /* Keyword.Declaration */ -.kn { color: #000000; font-weight: bold } /* Keyword.Namespace */ -.kp { color: #000000; font-weight: bold } /* Keyword.Pseudo */ -.kr { color: #000000; font-weight: bold } /* Keyword.Reserved */ -.kt { color: #445588; font-weight: bold } /* Keyword.Type */ -.m { color: #009999 } /* Literal.Number */ -.s { color: #dd1144 } /* Literal.String */ -.na { color: #008080 } /* Name.Attribute */ -.nb { color: #0086B3 } /* Name.Builtin */ -.nc { color: #445588; font-weight: bold } /* Name.Class */ -.no { color: #008080 } /* Name.Constant */ -.nd { color: #3c5d5d; font-weight: bold } /* Name.Decorator */ -.ni { color: #800080 } /* Name.Entity */ -.ne { color: #990000; font-weight: bold } /* Name.Exception */ -.nf { color: #990000; font-weight: bold } /* Name.Function */ -.nl { color: #990000; font-weight: bold } /* Name.Label */ -.nn { color: #555555 } /* Name.Namespace */ -.nt { color: #000080 } /* Name.Tag */ -.nv { color: #008080 } /* Name.Variable */ -.ow { color: #000000; font-weight: bold } /* Operator.Word */ -.w { color: #bbbbbb } /* Text.Whitespace */ -.mb { color: #009999 } /* Literal.Number.Bin */ -.mf { color: #009999 } /* Literal.Number.Float */ -.mh { color: #009999 } /* Literal.Number.Hex */ -.mi { color: #009999 } /* Literal.Number.Integer */ -.mo { color: #009999 } /* Literal.Number.Oct */ -.sb { color: #dd1144 } /* Literal.String.Backtick */ -.sc { color: #dd1144 } /* Literal.String.Char */ -.sd { color: #dd1144 } /* Literal.String.Doc */ -.s2 { color: #dd1144 } /* Literal.String.Double */ -.se { color: #dd1144 } /* Literal.String.Escape */ -.sh { color: #dd1144 } /* Literal.String.Heredoc */ -.si { color: #dd1144 } /* Literal.String.Interpol */ -.sx { color: #dd1144 } /* Literal.String.Other */ -.sr { color: #009926 } /* Literal.String.Regex */ -.s1 { color: #dd1144 } /* Literal.String.Single */ -.ss { color: #990073 } /* Literal.String.Symbol */ -.bp { color: #999999 } /* Name.Builtin.Pseudo */ -.vc { color: #008080 } /* Name.Variable.Class */ -.vg { color: #008080 } /* Name.Variable.Global */ -.vi { color: #008080 } /* Name.Variable.Instance */ -.il { color: #009999 } /* Literal.Number.Integer.Long */ \ No newline at end of file diff --git a/theme/pygments/github.min.css b/theme/pygments/github.min.css deleted file mode 100644 index 0d35cf1..0000000 --- a/theme/pygments/github.min.css +++ /dev/null @@ -1 +0,0 @@ -.highlight{background-color:#ffc}.c{color:#998;font-style:italic}.err{color:#a61717;background-color:#e3d2d2}.k,.o{color:#000;font-weight:700}.ch,.cm{color:#998}.ch,.cm,.cp{font-style:italic}.cp{color:#999;font-weight:700}.c1,.cpf{color:#998}.c1,.cpf,.cs{font-style:italic}.cs{color:#999;font-weight:700}.gd{background-color:#fdd}.gd,.ge{color:#000}.ge{font-style:italic}.gr{color:#a00}.gh{color:#999}.gi{color:#000;background-color:#dfd}.go{color:#888}.gp{color:#555}.gs{font-weight:700}.gu{color:#aaa}.gt{color:#a00}.kc,.kd,.kn,.kp,.kr{color:#000;font-weight:700}.kt{color:#458;font-weight:700}.m{color:#099}.s{color:#d14}.na{color:teal}.nb{color:#0086b3}.nc{color:#458;font-weight:700}.no{color:teal}.nd{color:#3c5d5d;font-weight:700}.ni{color:purple}.ne,.nf,.nl{color:#900;font-weight:700}.nn{color:#555}.nt{color:navy}.nv{color:teal}.ow{color:#000;font-weight:700}.w{color:#bbb}.mb,.mf,.mh,.mi,.mo{color:#099}.s2,.sb,.sc,.sd,.se,.sh,.si,.sx{color:#d14}.sr{color:#009926}.s1{color:#d14}.ss{color:#990073}.bp{color:#999}.vc,.vg,.vi{color:teal}.il{color:#099} \ No newline at end of file diff --git a/theme/pygments/igor.css b/theme/pygments/igor.css deleted file mode 100644 index 87cf359..0000000 --- a/theme/pygments/igor.css +++ /dev/null @@ -1,30 +0,0 @@ -.highlight { background-color: #ffffcc } -.c { color: #FF0000; font-style: italic } /* Comment */ -.k { color: #0000FF } /* Keyword */ -.ch { color: #FF0000; font-style: italic } /* Comment.Hashbang */ -.cm { color: #FF0000; font-style: italic } /* Comment.Multiline */ -.cp { color: #FF0000; font-style: italic } /* Comment.Preproc */ -.cpf { color: #FF0000; font-style: italic } /* Comment.PreprocFile */ -.c1 { color: #FF0000; font-style: italic } /* Comment.Single */ -.cs { color: #FF0000; font-style: italic } /* Comment.Special */ -.kc { color: #0000FF } /* Keyword.Constant */ -.kd { color: #0000FF } /* Keyword.Declaration */ -.kn { color: #0000FF } /* Keyword.Namespace */ -.kp { color: #0000FF } /* Keyword.Pseudo */ -.kr { color: #0000FF } /* Keyword.Reserved */ -.kt { color: #0000FF } /* Keyword.Type */ -.s { color: #009C00 } /* Literal.String */ -.nc { color: #007575 } /* Name.Class */ -.nd { color: #CC00A3 } /* Name.Decorator */ -.nf { color: #C34E00 } /* Name.Function */ -.sb { color: #009C00 } /* Literal.String.Backtick */ -.sc { color: #009C00 } /* Literal.String.Char */ -.sd { color: #009C00 } /* Literal.String.Doc */ -.s2 { color: #009C00 } /* Literal.String.Double */ -.se { color: #009C00 } /* Literal.String.Escape */ -.sh { color: #009C00 } /* Literal.String.Heredoc */ -.si { color: #009C00 } /* Literal.String.Interpol */ -.sx { color: #009C00 } /* Literal.String.Other */ -.sr { color: #009C00 } /* Literal.String.Regex */ -.s1 { color: #009C00 } /* Literal.String.Single */ -.ss { color: #009C00 } /* Literal.String.Symbol */ \ No newline at end of file diff --git a/theme/pygments/igor.min.css b/theme/pygments/igor.min.css deleted file mode 100644 index c68c6b7..0000000 --- a/theme/pygments/igor.min.css +++ /dev/null @@ -1 +0,0 @@ -.highlight{background-color:#ffc}.c{color:red;font-style:italic}.k{color:#00f}.c1,.ch,.cm,.cp,.cpf,.cs{color:red;font-style:italic}.kc,.kd,.kn,.kp,.kr,.kt{color:#00f}.s{color:#009c00}.nc{color:#007575}.nd{color:#cc00a3}.nf{color:#c34e00}.s1,.s2,.sb,.sc,.sd,.se,.sh,.si,.sr,.ss,.sx{color:#009c00} \ No newline at end of file diff --git a/theme/pygments/lovelace.css b/theme/pygments/lovelace.css deleted file mode 100644 index d248228..0000000 --- a/theme/pygments/lovelace.css +++ /dev/null @@ -1,65 +0,0 @@ -.highlight { background-color: #ffffcc } -.c { color: #888888; font-style: italic } /* Comment */ -.err { background-color: #a848a8 } /* Error */ -.k { color: #2838b0 } /* Keyword */ -.o { color: #666666 } /* Operator */ -.p { color: #888888 } /* Punctuation */ -.ch { color: #287088; font-style: italic } /* Comment.Hashbang */ -.cm { color: #888888; font-style: italic } /* Comment.Multiline */ -.cp { color: #289870 } /* Comment.Preproc */ -.cpf { color: #888888; font-style: italic } /* Comment.PreprocFile */ -.c1 { color: #888888; font-style: italic } /* Comment.Single */ -.cs { color: #888888; font-style: italic } /* Comment.Special */ -.gd { color: #c02828 } /* Generic.Deleted */ -.ge { font-style: italic } /* Generic.Emph */ -.gr { color: #c02828 } /* Generic.Error */ -.gh { color: #666666 } /* Generic.Heading */ -.gi { color: #388038 } /* Generic.Inserted */ -.go { color: #666666 } /* Generic.Output */ -.gp { color: #444444 } /* Generic.Prompt */ -.gs { font-weight: bold } /* Generic.Strong */ -.gu { color: #444444 } /* Generic.Subheading */ -.gt { color: #2838b0 } /* Generic.Traceback */ -.kc { color: #444444; font-style: italic } /* Keyword.Constant */ -.kd { color: #2838b0; font-style: italic } /* Keyword.Declaration */ -.kn { color: #2838b0 } /* Keyword.Namespace */ -.kp { color: #2838b0 } /* Keyword.Pseudo */ -.kr { color: #2838b0 } /* Keyword.Reserved */ -.kt { color: #2838b0; font-style: italic } /* Keyword.Type */ -.m { color: #444444 } /* Literal.Number */ -.s { color: #b83838 } /* Literal.String */ -.na { color: #388038 } /* Name.Attribute */ -.nb { color: #388038 } /* Name.Builtin */ -.nc { color: #287088 } /* Name.Class */ -.no { color: #b85820 } /* Name.Constant */ -.nd { color: #287088 } /* Name.Decorator */ -.ni { color: #709030 } /* Name.Entity */ -.ne { color: #908828 } /* Name.Exception */ -.nf { color: #785840 } /* Name.Function */ -.nl { color: #289870 } /* Name.Label */ -.nn { color: #289870 } /* Name.Namespace */ -.nt { color: #2838b0 } /* Name.Tag */ -.nv { color: #b04040 } /* Name.Variable */ -.ow { color: #a848a8 } /* Operator.Word */ -.w { color: #a89028 } /* Text.Whitespace */ -.mb { color: #444444 } /* Literal.Number.Bin */ -.mf { color: #444444 } /* Literal.Number.Float */ -.mh { color: #444444 } /* Literal.Number.Hex */ -.mi { color: #444444 } /* Literal.Number.Integer */ -.mo { color: #444444 } /* Literal.Number.Oct */ -.sb { color: #b83838 } /* Literal.String.Backtick */ -.sc { color: #a848a8 } /* Literal.String.Char */ -.sd { color: #b85820; font-style: italic } /* Literal.String.Doc */ -.s2 { color: #b83838 } /* Literal.String.Double */ -.se { color: #709030 } /* Literal.String.Escape */ -.sh { color: #b83838 } /* Literal.String.Heredoc */ -.si { color: #b83838; text-decoration: underline } /* Literal.String.Interpol */ -.sx { color: #a848a8 } /* Literal.String.Other */ -.sr { color: #a848a8 } /* Literal.String.Regex */ -.s1 { color: #b83838 } /* Literal.String.Single */ -.ss { color: #b83838 } /* Literal.String.Symbol */ -.bp { color: #388038; font-style: italic } /* Name.Builtin.Pseudo */ -.vc { color: #b04040 } /* Name.Variable.Class */ -.vg { color: #908828 } /* Name.Variable.Global */ -.vi { color: #b04040 } /* Name.Variable.Instance */ -.il { color: #444444 } /* Literal.Number.Integer.Long */ \ No newline at end of file diff --git a/theme/pygments/lovelace.min.css b/theme/pygments/lovelace.min.css deleted file mode 100644 index 4d28a6d..0000000 --- a/theme/pygments/lovelace.min.css +++ /dev/null @@ -1 +0,0 @@ -.highlight{background-color:#ffc}.c{color:#888;font-style:italic}.err{background-color:#a848a8}.k{color:#2838b0}.o{color:#666}.p{color:#888}.ch{color:#287088}.ch,.cm{font-style:italic}.cm{color:#888}.cp{color:#289870}.c1,.cpf,.cs{color:#888;font-style:italic}.gd{color:#c02828}.ge{font-style:italic}.gr{color:#c02828}.gh{color:#666}.gi{color:#388038}.go{color:#666}.gp{color:#444}.gs{font-weight:700}.gu{color:#444}.gt{color:#2838b0}.kc{color:#444}.kc,.kd{font-style:italic}.kd,.kn,.kp,.kr,.kt{color:#2838b0}.kt{font-style:italic}.m{color:#444}.s{color:#b83838}.na,.nb{color:#388038}.nc{color:#287088}.no{color:#b85820}.nd{color:#287088}.ni{color:#709030}.ne{color:#908828}.nf{color:#785840}.nl,.nn{color:#289870}.nt{color:#2838b0}.nv{color:#b04040}.ow{color:#a848a8}.w{color:#a89028}.mb,.mf,.mh,.mi,.mo{color:#444}.sb{color:#b83838}.sc{color:#a848a8}.sd{color:#b85820;font-style:italic}.s2{color:#b83838}.se{color:#709030}.sh,.si{color:#b83838}.si{text-decoration:underline}.sr,.sx{color:#a848a8}.s1,.ss{color:#b83838}.bp{color:#388038;font-style:italic}.vc{color:#b04040}.vg{color:#908828}.vi{color:#b04040}.il{color:#444} \ No newline at end of file diff --git a/theme/pygments/manni.css b/theme/pygments/manni.css deleted file mode 100644 index a4f174e..0000000 --- a/theme/pygments/manni.css +++ /dev/null @@ -1,64 +0,0 @@ -.highlight { background-color: #ffffcc } -.c { color: #0099FF; font-style: italic } /* Comment */ -.err { color: #AA0000; background-color: #FFAAAA } /* Error */ -.k { color: #006699; font-weight: bold } /* Keyword */ -.o { color: #555555 } /* Operator */ -.ch { color: #0099FF; font-style: italic } /* Comment.Hashbang */ -.cm { color: #0099FF; font-style: italic } /* Comment.Multiline */ -.cp { color: #009999 } /* Comment.Preproc */ -.cpf { color: #0099FF; font-style: italic } /* Comment.PreprocFile */ -.c1 { color: #0099FF; font-style: italic } /* Comment.Single */ -.cs { color: #0099FF; font-weight: bold; font-style: italic } /* Comment.Special */ -.gd { background-color: #FFCCCC; border: 1px solid #CC0000 } /* Generic.Deleted */ -.ge { font-style: italic } /* Generic.Emph */ -.gr { color: #FF0000 } /* Generic.Error */ -.gh { color: #003300; font-weight: bold } /* Generic.Heading */ -.gi { background-color: #CCFFCC; border: 1px solid #00CC00 } /* Generic.Inserted */ -.go { color: #AAAAAA } /* Generic.Output */ -.gp { color: #000099; font-weight: bold } /* Generic.Prompt */ -.gs { font-weight: bold } /* Generic.Strong */ -.gu { color: #003300; font-weight: bold } /* Generic.Subheading */ -.gt { color: #99CC66 } /* Generic.Traceback */ -.kc { color: #006699; font-weight: bold } /* Keyword.Constant */ -.kd { color: #006699; font-weight: bold } /* Keyword.Declaration */ -.kn { color: #006699; font-weight: bold } /* Keyword.Namespace */ -.kp { color: #006699 } /* Keyword.Pseudo */ -.kr { color: #006699; font-weight: bold } /* Keyword.Reserved */ -.kt { color: #007788; font-weight: bold } /* Keyword.Type */ -.m { color: #FF6600 } /* Literal.Number */ -.s { color: #CC3300 } /* Literal.String */ -.na { color: #330099 } /* Name.Attribute */ -.nb { color: #336666 } /* Name.Builtin */ -.nc { color: #00AA88; font-weight: bold } /* Name.Class */ -.no { color: #336600 } /* Name.Constant */ -.nd { color: #9999FF } /* Name.Decorator */ -.ni { color: #999999; font-weight: bold } /* Name.Entity */ -.ne { color: #CC0000; font-weight: bold } /* Name.Exception */ -.nf { color: #CC00FF } /* Name.Function */ -.nl { color: #9999FF } /* Name.Label */ -.nn { color: #00CCFF; font-weight: bold } /* Name.Namespace */ -.nt { color: #330099; font-weight: bold } /* Name.Tag */ -.nv { color: #003333 } /* Name.Variable */ -.ow { color: #000000; font-weight: bold } /* Operator.Word */ -.w { color: #bbbbbb } /* Text.Whitespace */ -.mb { color: #FF6600 } /* Literal.Number.Bin */ -.mf { color: #FF6600 } /* Literal.Number.Float */ -.mh { color: #FF6600 } /* Literal.Number.Hex */ -.mi { color: #FF6600 } /* Literal.Number.Integer */ -.mo { color: #FF6600 } /* Literal.Number.Oct */ -.sb { color: #CC3300 } /* Literal.String.Backtick */ -.sc { color: #CC3300 } /* Literal.String.Char */ -.sd { color: #CC3300; font-style: italic } /* Literal.String.Doc */ -.s2 { color: #CC3300 } /* Literal.String.Double */ -.se { color: #CC3300; font-weight: bold } /* Literal.String.Escape */ -.sh { color: #CC3300 } /* Literal.String.Heredoc */ -.si { color: #AA0000 } /* Literal.String.Interpol */ -.sx { color: #CC3300 } /* Literal.String.Other */ -.sr { color: #33AAAA } /* Literal.String.Regex */ -.s1 { color: #CC3300 } /* Literal.String.Single */ -.ss { color: #FFCC33 } /* Literal.String.Symbol */ -.bp { color: #336666 } /* Name.Builtin.Pseudo */ -.vc { color: #003333 } /* Name.Variable.Class */ -.vg { color: #003333 } /* Name.Variable.Global */ -.vi { color: #003333 } /* Name.Variable.Instance */ -.il { color: #FF6600 } /* Literal.Number.Integer.Long */ \ No newline at end of file diff --git a/theme/pygments/manni.min.css b/theme/pygments/manni.min.css deleted file mode 100644 index 851fb30..0000000 --- a/theme/pygments/manni.min.css +++ /dev/null @@ -1 +0,0 @@ -.highlight{background-color:#ffc}.c{color:#09f;font-style:italic}.err{color:#a00;background-color:#faa}.k{color:#069;font-weight:700}.o{color:#555}.ch,.cm{color:#09f;font-style:italic}.cp{color:#099}.c1,.cpf,.cs{color:#09f;font-style:italic}.cs{font-weight:700}.gd{background-color:#fcc;border:1px solid #c00}.ge{font-style:italic}.gr{color:red}.gh{color:#030;font-weight:700}.gi{background-color:#cfc;border:1px solid #0c0}.go{color:#aaa}.gp{color:#009}.gp,.gs,.gu{font-weight:700}.gu{color:#030}.gt{color:#9c6}.kc,.kd,.kn{color:#069;font-weight:700}.kp,.kr{color:#069}.kr,.kt{font-weight:700}.kt{color:#078}.m{color:#f60}.s{color:#c30}.na{color:#309}.nb{color:#366}.nc{color:#0a8;font-weight:700}.no{color:#360}.nd{color:#99f}.ni{color:#999}.ne,.ni{font-weight:700}.ne{color:#c00}.nf{color:#c0f}.nl{color:#99f}.nn{color:#0cf}.nn,.nt{font-weight:700}.nt{color:#309}.nv{color:#033}.ow{color:#000;font-weight:700}.w{color:#bbb}.mb,.mf,.mh,.mi,.mo{color:#f60}.sb,.sc,.sd{color:#c30}.sd{font-style:italic}.s2,.se{color:#c30}.se{font-weight:700}.sh{color:#c30}.si{color:#a00}.sx{color:#c30}.sr{color:#3aa}.s1{color:#c30}.ss{color:#fc3}.bp{color:#366}.vc,.vg,.vi{color:#033}.il{color:#f60} \ No newline at end of file diff --git a/theme/pygments/monokai.css b/theme/pygments/monokai.css deleted file mode 100644 index 3c8bf06..0000000 --- a/theme/pygments/monokai.css +++ /dev/null @@ -1,65 +0,0 @@ -.highlight { background-color: #49483e } -.c { color: #75715e } /* Comment */ -.err { color: #960050; background-color: #1e0010 } /* Error */ -.k { color: #66d9ef } /* Keyword */ -.l { color: #ae81ff } /* Literal */ -.n { color: #f8f8f2 } /* Name */ -.o { color: #f92672 } /* Operator */ -.p { color: #f8f8f2 } /* Punctuation */ -.ch { color: #75715e } /* Comment.Hashbang */ -.cm { color: #75715e } /* Comment.Multiline */ -.cp { color: #75715e } /* Comment.Preproc */ -.cpf { color: #75715e } /* Comment.PreprocFile */ -.c1 { color: #75715e } /* Comment.Single */ -.cs { color: #75715e } /* Comment.Special */ -.gd { color: #f92672 } /* Generic.Deleted */ -.ge { font-style: italic } /* Generic.Emph */ -.gi { color: #a6e22e } /* Generic.Inserted */ -.gs { font-weight: bold } /* Generic.Strong */ -.gu { color: #75715e } /* Generic.Subheading */ -.kc { color: #66d9ef } /* Keyword.Constant */ -.kd { color: #66d9ef } /* Keyword.Declaration */ -.kn { color: #f92672 } /* Keyword.Namespace */ -.kp { color: #66d9ef } /* Keyword.Pseudo */ -.kr { color: #66d9ef } /* Keyword.Reserved */ -.kt { color: #66d9ef } /* Keyword.Type */ -.ld { color: #e6db74 } /* Literal.Date */ -.m { color: #ae81ff } /* Literal.Number */ -.s { color: #e6db74 } /* Literal.String */ -.na { color: #a6e22e } /* Name.Attribute */ -.nb { color: #f8f8f2 } /* Name.Builtin */ -.nc { color: #a6e22e } /* Name.Class */ -.no { color: #66d9ef } /* Name.Constant */ -.nd { color: #a6e22e } /* Name.Decorator */ -.ni { color: #f8f8f2 } /* Name.Entity */ -.ne { color: #a6e22e } /* Name.Exception */ -.nf { color: #a6e22e } /* Name.Function */ -.nl { color: #f8f8f2 } /* Name.Label */ -.nn { color: #f8f8f2 } /* Name.Namespace */ -.nx { color: #a6e22e } /* Name.Other */ -.py { color: #f8f8f2 } /* Name.Property */ -.nt { color: #f92672 } /* Name.Tag */ -.nv { color: #f8f8f2 } /* Name.Variable */ -.ow { color: #f92672 } /* Operator.Word */ -.w { color: #f8f8f2 } /* Text.Whitespace */ -.mb { color: #ae81ff } /* Literal.Number.Bin */ -.mf { color: #ae81ff } /* Literal.Number.Float */ -.mh { color: #ae81ff } /* Literal.Number.Hex */ -.mi { color: #ae81ff } /* Literal.Number.Integer */ -.mo { color: #ae81ff } /* Literal.Number.Oct */ -.sb { color: #e6db74 } /* Literal.String.Backtick */ -.sc { color: #e6db74 } /* Literal.String.Char */ -.sd { color: #e6db74 } /* Literal.String.Doc */ -.s2 { color: #e6db74 } /* Literal.String.Double */ -.se { color: #ae81ff } /* Literal.String.Escape */ -.sh { color: #e6db74 } /* Literal.String.Heredoc */ -.si { color: #e6db74 } /* Literal.String.Interpol */ -.sx { color: #e6db74 } /* Literal.String.Other */ -.sr { color: #e6db74 } /* Literal.String.Regex */ -.s1 { color: #e6db74 } /* Literal.String.Single */ -.ss { color: #e6db74 } /* Literal.String.Symbol */ -.bp { color: #f8f8f2 } /* Name.Builtin.Pseudo */ -.vc { color: #f8f8f2 } /* Name.Variable.Class */ -.vg { color: #f8f8f2 } /* Name.Variable.Global */ -.vi { color: #f8f8f2 } /* Name.Variable.Instance */ -.il { color: #ae81ff } /* Literal.Number.Integer.Long */ \ No newline at end of file diff --git a/theme/pygments/monokai.min.css b/theme/pygments/monokai.min.css deleted file mode 100644 index e9eb78b..0000000 --- a/theme/pygments/monokai.min.css +++ /dev/null @@ -1 +0,0 @@ -.highlight{background-color:#49483e}.c{color:#75715e}.err{color:#960050;background-color:#1e0010}.k{color:#66d9ef}.l{color:#ae81ff}.n{color:#f8f8f2}.o{color:#f92672}.p{color:#f8f8f2}.c1,.ch,.cm,.cp,.cpf,.cs{color:#75715e}.gd{color:#f92672}.ge{font-style:italic}.gi{color:#a6e22e}.gs{font-weight:700}.gu{color:#75715e}.kc,.kd{color:#66d9ef}.kn{color:#f92672}.kp,.kr,.kt{color:#66d9ef}.ld{color:#e6db74}.m{color:#ae81ff}.s{color:#e6db74}.na{color:#a6e22e}.nb{color:#f8f8f2}.nc{color:#a6e22e}.no{color:#66d9ef}.nd{color:#a6e22e}.ni{color:#f8f8f2}.ne,.nf{color:#a6e22e}.nl,.nn{color:#f8f8f2}.nx{color:#a6e22e}.py{color:#f8f8f2}.nt{color:#f92672}.nv{color:#f8f8f2}.ow{color:#f92672}.w{color:#f8f8f2}.mb,.mf,.mh,.mi,.mo{color:#ae81ff}.s2,.sb,.sc,.sd{color:#e6db74}.se{color:#ae81ff}.s1,.sh,.si,.sr,.ss,.sx{color:#e6db74}.bp,.vc,.vg,.vi{color:#f8f8f2}.il{color:#ae81ff} \ No newline at end of file diff --git a/theme/pygments/murphy.css b/theme/pygments/murphy.css deleted file mode 100644 index fd46e31..0000000 --- a/theme/pygments/murphy.css +++ /dev/null @@ -1,64 +0,0 @@ -.highlight { background-color: #ffffcc } -.c { color: #666666; font-style: italic } /* Comment */ -.err { color: #FF0000; background-color: #FFAAAA } /* Error */ -.k { color: #228899; font-weight: bold } /* Keyword */ -.o { color: #333333 } /* Operator */ -.ch { color: #666666; font-style: italic } /* Comment.Hashbang */ -.cm { color: #666666; font-style: italic } /* Comment.Multiline */ -.cp { color: #557799 } /* Comment.Preproc */ -.cpf { color: #666666; font-style: italic } /* Comment.PreprocFile */ -.c1 { color: #666666; font-style: italic } /* Comment.Single */ -.cs { color: #cc0000; font-weight: bold; font-style: italic } /* Comment.Special */ -.gd { color: #A00000 } /* Generic.Deleted */ -.ge { font-style: italic } /* Generic.Emph */ -.gr { color: #FF0000 } /* Generic.Error */ -.gh { color: #000080; font-weight: bold } /* Generic.Heading */ -.gi { color: #00A000 } /* Generic.Inserted */ -.go { color: #888888 } /* Generic.Output */ -.gp { color: #c65d09; font-weight: bold } /* Generic.Prompt */ -.gs { font-weight: bold } /* Generic.Strong */ -.gu { color: #800080; font-weight: bold } /* Generic.Subheading */ -.gt { color: #0044DD } /* Generic.Traceback */ -.kc { color: #228899; font-weight: bold } /* Keyword.Constant */ -.kd { color: #228899; font-weight: bold } /* Keyword.Declaration */ -.kn { color: #228899; font-weight: bold } /* Keyword.Namespace */ -.kp { color: #0088ff; font-weight: bold } /* Keyword.Pseudo */ -.kr { color: #228899; font-weight: bold } /* Keyword.Reserved */ -.kt { color: #6666ff; font-weight: bold } /* Keyword.Type */ -.m { color: #6600EE; font-weight: bold } /* Literal.Number */ -.s { background-color: #e0e0ff } /* Literal.String */ -.na { color: #000077 } /* Name.Attribute */ -.nb { color: #007722 } /* Name.Builtin */ -.nc { color: #ee99ee; font-weight: bold } /* Name.Class */ -.no { color: #55eedd; font-weight: bold } /* Name.Constant */ -.nd { color: #555555; font-weight: bold } /* Name.Decorator */ -.ni { color: #880000 } /* Name.Entity */ -.ne { color: #FF0000; font-weight: bold } /* Name.Exception */ -.nf { color: #55eedd; font-weight: bold } /* Name.Function */ -.nl { color: #997700; font-weight: bold } /* Name.Label */ -.nn { color: #0e84b5; font-weight: bold } /* Name.Namespace */ -.nt { color: #007700 } /* Name.Tag */ -.nv { color: #003366 } /* Name.Variable */ -.ow { color: #000000; font-weight: bold } /* Operator.Word */ -.w { color: #bbbbbb } /* Text.Whitespace */ -.mb { color: #6600EE; font-weight: bold } /* Literal.Number.Bin */ -.mf { color: #6600EE; font-weight: bold } /* Literal.Number.Float */ -.mh { color: #005588; font-weight: bold } /* Literal.Number.Hex */ -.mi { color: #6666ff; font-weight: bold } /* Literal.Number.Integer */ -.mo { color: #4400EE; font-weight: bold } /* Literal.Number.Oct */ -.sb { background-color: #e0e0ff } /* Literal.String.Backtick */ -.sc { color: #8888FF } /* Literal.String.Char */ -.sd { color: #DD4422 } /* Literal.String.Doc */ -.s2 { background-color: #e0e0ff } /* Literal.String.Double */ -.se { color: #666666; font-weight: bold; background-color: #e0e0ff } /* Literal.String.Escape */ -.sh { background-color: #e0e0ff } /* Literal.String.Heredoc */ -.si { background-color: #eeeeee } /* Literal.String.Interpol */ -.sx { color: #ff8888; background-color: #e0e0ff } /* Literal.String.Other */ -.sr { color: #000000; background-color: #e0e0ff } /* Literal.String.Regex */ -.s1 { background-color: #e0e0ff } /* Literal.String.Single */ -.ss { color: #ffcc88 } /* Literal.String.Symbol */ -.bp { color: #007722 } /* Name.Builtin.Pseudo */ -.vc { color: #ccccff } /* Name.Variable.Class */ -.vg { color: #ff8844 } /* Name.Variable.Global */ -.vi { color: #aaaaff } /* Name.Variable.Instance */ -.il { color: #6666ff; font-weight: bold } /* Literal.Number.Integer.Long */ \ No newline at end of file diff --git a/theme/pygments/murphy.min.css b/theme/pygments/murphy.min.css deleted file mode 100644 index 2b44ac9..0000000 --- a/theme/pygments/murphy.min.css +++ /dev/null @@ -1 +0,0 @@ -.highlight{background-color:#ffc}.c{color:#666;font-style:italic}.err{color:red;background-color:#faa}.k{color:#289;font-weight:700}.o{color:#333}.ch,.cm{color:#666;font-style:italic}.cp{color:#579}.c1,.cpf{color:#666}.c1,.cpf,.cs{font-style:italic}.cs{color:#c00;font-weight:700}.gd{color:#a00000}.ge{font-style:italic}.gr{color:red}.gh{color:navy;font-weight:700}.gi{color:#00a000}.go{color:#888}.gp{color:#c65d09}.gp,.gs,.gu{font-weight:700}.gu{color:purple}.gt{color:#04d}.kc,.kd,.kn{color:#289;font-weight:700}.kp{color:#08f}.kp,.kr{font-weight:700}.kr{color:#289}.kt{color:#66f}.kt,.m{font-weight:700}.m{color:#60e}.s{background-color:#e0e0ff}.na{color:#007}.nb{color:#072}.nc{color:#e9e}.nc,.no{font-weight:700}.no{color:#5ed}.nd{color:#555;font-weight:700}.ni{color:#800}.ne{color:red}.ne,.nf{font-weight:700}.nf{color:#5ed}.nl{color:#970}.nl,.nn{font-weight:700}.nn{color:#0e84b5}.nt{color:#070}.nv{color:#036}.ow{color:#000;font-weight:700}.w{color:#bbb}.mb,.mf{color:#60e}.mb,.mf,.mh{font-weight:700}.mh{color:#058}.mi{color:#66f}.mi,.mo{font-weight:700}.mo{color:#40e}.sb{background-color:#e0e0ff}.sc{color:#88f}.sd{color:#d42}.s2,.se{background-color:#e0e0ff}.se{color:#666;font-weight:700}.sh{background-color:#e0e0ff}.si{background-color:#eee}.sx{color:#f88}.sr,.sx{background-color:#e0e0ff}.sr{color:#000}.s1{background-color:#e0e0ff}.ss{color:#fc8}.bp{color:#072}.vc{color:#ccf}.vg{color:#f84}.vi{color:#aaf}.il{color:#66f;font-weight:700} \ No newline at end of file diff --git a/theme/pygments/native.css b/theme/pygments/native.css deleted file mode 100644 index 65f10c1..0000000 --- a/theme/pygments/native.css +++ /dev/null @@ -1,73 +0,0 @@ -.highlight { background-color: #404040 } -.c { color: #999999; font-style: italic } /* Comment */ -.err { color: #a61717; background-color: #e3d2d2 } /* Error */ -.esc { color: #d0d0d0 } /* Escape */ -.g { color: #d0d0d0 } /* Generic */ -.k { color: #6ab825; font-weight: bold } /* Keyword */ -.l { color: #d0d0d0 } /* Literal */ -.n { color: #d0d0d0 } /* Name */ -.o { color: #d0d0d0 } /* Operator */ -.x { color: #d0d0d0 } /* Other */ -.p { color: #d0d0d0 } /* Punctuation */ -.ch { color: #999999; font-style: italic } /* Comment.Hashbang */ -.cm { color: #999999; font-style: italic } /* Comment.Multiline */ -.cp { color: #cd2828; font-weight: bold } /* Comment.Preproc */ -.cpf { color: #999999; font-style: italic } /* Comment.PreprocFile */ -.c1 { color: #999999; font-style: italic } /* Comment.Single */ -.cs { color: #e50808; font-weight: bold; background-color: #520000 } /* Comment.Special */ -.gd { color: #d22323 } /* Generic.Deleted */ -.ge { color: #d0d0d0; font-style: italic } /* Generic.Emph */ -.gr { color: #d22323 } /* Generic.Error */ -.gh { color: #ffffff; font-weight: bold } /* Generic.Heading */ -.gi { color: #589819 } /* Generic.Inserted */ -.go { color: #cccccc } /* Generic.Output */ -.gp { color: #aaaaaa } /* Generic.Prompt */ -.gs { color: #d0d0d0; font-weight: bold } /* Generic.Strong */ -.gu { color: #ffffff; text-decoration: underline } /* Generic.Subheading */ -.gt { color: #d22323 } /* Generic.Traceback */ -.kc { color: #6ab825; font-weight: bold } /* Keyword.Constant */ -.kd { color: #6ab825; font-weight: bold } /* Keyword.Declaration */ -.kn { color: #6ab825; font-weight: bold } /* Keyword.Namespace */ -.kp { color: #6ab825 } /* Keyword.Pseudo */ -.kr { color: #6ab825; font-weight: bold } /* Keyword.Reserved */ -.kt { color: #6ab825; font-weight: bold } /* Keyword.Type */ -.ld { color: #d0d0d0 } /* Literal.Date */ -.m { color: #3677a9 } /* Literal.Number */ -.s { color: #ed9d13 } /* Literal.String */ -.na { color: #bbbbbb } /* Name.Attribute */ -.nb { color: #24909d } /* Name.Builtin */ -.nc { color: #447fcf; text-decoration: underline } /* Name.Class */ -.no { color: #40ffff } /* Name.Constant */ -.nd { color: #ffa500 } /* Name.Decorator */ -.ni { color: #d0d0d0 } /* Name.Entity */ -.ne { color: #bbbbbb } /* Name.Exception */ -.nf { color: #447fcf } /* Name.Function */ -.nl { color: #d0d0d0 } /* Name.Label */ -.nn { color: #447fcf; text-decoration: underline } /* Name.Namespace */ -.nx { color: #d0d0d0 } /* Name.Other */ -.py { color: #d0d0d0 } /* Name.Property */ -.nt { color: #6ab825; font-weight: bold } /* Name.Tag */ -.nv { color: #40ffff } /* Name.Variable */ -.ow { color: #6ab825; font-weight: bold } /* Operator.Word */ -.w { color: #666666 } /* Text.Whitespace */ -.mb { color: #3677a9 } /* Literal.Number.Bin */ -.mf { color: #3677a9 } /* Literal.Number.Float */ -.mh { color: #3677a9 } /* Literal.Number.Hex */ -.mi { color: #3677a9 } /* Literal.Number.Integer */ -.mo { color: #3677a9 } /* Literal.Number.Oct */ -.sb { color: #ed9d13 } /* Literal.String.Backtick */ -.sc { color: #ed9d13 } /* Literal.String.Char */ -.sd { color: #ed9d13 } /* Literal.String.Doc */ -.s2 { color: #ed9d13 } /* Literal.String.Double */ -.se { color: #ed9d13 } /* Literal.String.Escape */ -.sh { color: #ed9d13 } /* Literal.String.Heredoc */ -.si { color: #ed9d13 } /* Literal.String.Interpol */ -.sx { color: #ffa500 } /* Literal.String.Other */ -.sr { color: #ed9d13 } /* Literal.String.Regex */ -.s1 { color: #ed9d13 } /* Literal.String.Single */ -.ss { color: #ed9d13 } /* Literal.String.Symbol */ -.bp { color: #24909d } /* Name.Builtin.Pseudo */ -.vc { color: #40ffff } /* Name.Variable.Class */ -.vg { color: #40ffff } /* Name.Variable.Global */ -.vi { color: #40ffff } /* Name.Variable.Instance */ -.il { color: #3677a9 } /* Literal.Number.Integer.Long */ \ No newline at end of file diff --git a/theme/pygments/native.min.css b/theme/pygments/native.min.css deleted file mode 100644 index 8dd3e3c..0000000 --- a/theme/pygments/native.min.css +++ /dev/null @@ -1 +0,0 @@ -.highlight{background-color:#404040}.c{color:#999;font-style:italic}.err{color:#a61717;background-color:#e3d2d2}.esc,.g{color:#d0d0d0}.k{color:#6ab825;font-weight:700}.l,.n,.o,.p,.x{color:#d0d0d0}.ch,.cm{color:#999;font-style:italic}.cp{color:#cd2828;font-weight:700}.c1,.cpf{color:#999;font-style:italic}.cs{color:#e50808;font-weight:700;background-color:#520000}.gd{color:#d22323}.ge{color:#d0d0d0;font-style:italic}.gr{color:#d22323}.gh{color:#fff;font-weight:700}.gi{color:#589819}.go{color:#ccc}.gp{color:#aaa}.gs{color:#d0d0d0;font-weight:700}.gu{color:#fff;text-decoration:underline}.gt{color:#d22323}.kc,.kd,.kn{font-weight:700}.kc,.kd,.kn,.kp{color:#6ab825}.kr,.kt{color:#6ab825;font-weight:700}.ld{color:#d0d0d0}.m{color:#3677a9}.s{color:#ed9d13}.na{color:#bbb}.nb{color:#24909d}.nc{color:#447fcf;text-decoration:underline}.no{color:#40ffff}.nd{color:orange}.ni{color:#d0d0d0}.ne{color:#bbb}.nf{color:#447fcf}.nl{color:#d0d0d0}.nn{color:#447fcf;text-decoration:underline}.nx,.py{color:#d0d0d0}.nt{color:#6ab825;font-weight:700}.nv{color:#40ffff}.ow{color:#6ab825;font-weight:700}.w{color:#666}.mb,.mf,.mh,.mi,.mo{color:#3677a9}.s2,.sb,.sc,.sd,.se,.sh,.si{color:#ed9d13}.sx{color:orange}.s1,.sr,.ss{color:#ed9d13}.bp{color:#24909d}.vc,.vg,.vi{color:#40ffff}.il{color:#3677a9} \ No newline at end of file diff --git a/theme/pygments/paraiso-dark.css b/theme/pygments/paraiso-dark.css deleted file mode 100644 index cfecfa9..0000000 --- a/theme/pygments/paraiso-dark.css +++ /dev/null @@ -1,67 +0,0 @@ -.highlight { background-color: #4f424c } -.c { color: #776e71 } /* Comment */ -.err { color: #ef6155 } /* Error */ -.k { color: #815ba4 } /* Keyword */ -.l { color: #f99b15 } /* Literal */ -.n { color: #e7e9db } /* Name */ -.o { color: #5bc4bf } /* Operator */ -.p { color: #e7e9db } /* Punctuation */ -.ch { color: #776e71 } /* Comment.Hashbang */ -.cm { color: #776e71 } /* Comment.Multiline */ -.cp { color: #776e71 } /* Comment.Preproc */ -.cpf { color: #776e71 } /* Comment.PreprocFile */ -.c1 { color: #776e71 } /* Comment.Single */ -.cs { color: #776e71 } /* Comment.Special */ -.gd { color: #ef6155 } /* Generic.Deleted */ -.ge { font-style: italic } /* Generic.Emph */ -.gh { color: #e7e9db; font-weight: bold } /* Generic.Heading */ -.gi { color: #48b685 } /* Generic.Inserted */ -.gp { color: #776e71; font-weight: bold } /* Generic.Prompt */ -.gs { font-weight: bold } /* Generic.Strong */ -.gu { color: #5bc4bf; font-weight: bold } /* Generic.Subheading */ -.kc { color: #815ba4 } /* Keyword.Constant */ -.kd { color: #815ba4 } /* Keyword.Declaration */ -.kn { color: #5bc4bf } /* Keyword.Namespace */ -.kp { color: #815ba4 } /* Keyword.Pseudo */ -.kr { color: #815ba4 } /* Keyword.Reserved */ -.kt { color: #fec418 } /* Keyword.Type */ -.ld { color: #48b685 } /* Literal.Date */ -.m { color: #f99b15 } /* Literal.Number */ -.s { color: #48b685 } /* Literal.String */ -.na { color: #06b6ef } /* Name.Attribute */ -.nb { color: #e7e9db } /* Name.Builtin */ -.nc { color: #fec418 } /* Name.Class */ -.no { color: #ef6155 } /* Name.Constant */ -.nd { color: #5bc4bf } /* Name.Decorator */ -.ni { color: #e7e9db } /* Name.Entity */ -.ne { color: #ef6155 } /* Name.Exception */ -.nf { color: #06b6ef } /* Name.Function */ -.nl { color: #e7e9db } /* Name.Label */ -.nn { color: #fec418 } /* Name.Namespace */ -.nx { color: #06b6ef } /* Name.Other */ -.py { color: #e7e9db } /* Name.Property */ -.nt { color: #5bc4bf } /* Name.Tag */ -.nv { color: #ef6155 } /* Name.Variable */ -.ow { color: #5bc4bf } /* Operator.Word */ -.w { color: #e7e9db } /* Text.Whitespace */ -.mb { color: #f99b15 } /* Literal.Number.Bin */ -.mf { color: #f99b15 } /* Literal.Number.Float */ -.mh { color: #f99b15 } /* Literal.Number.Hex */ -.mi { color: #f99b15 } /* Literal.Number.Integer */ -.mo { color: #f99b15 } /* Literal.Number.Oct */ -.sb { color: #48b685 } /* Literal.String.Backtick */ -.sc { color: #e7e9db } /* Literal.String.Char */ -.sd { color: #776e71 } /* Literal.String.Doc */ -.s2 { color: #48b685 } /* Literal.String.Double */ -.se { color: #f99b15 } /* Literal.String.Escape */ -.sh { color: #48b685 } /* Literal.String.Heredoc */ -.si { color: #f99b15 } /* Literal.String.Interpol */ -.sx { color: #48b685 } /* Literal.String.Other */ -.sr { color: #48b685 } /* Literal.String.Regex */ -.s1 { color: #48b685 } /* Literal.String.Single */ -.ss { color: #48b685 } /* Literal.String.Symbol */ -.bp { color: #e7e9db } /* Name.Builtin.Pseudo */ -.vc { color: #ef6155 } /* Name.Variable.Class */ -.vg { color: #ef6155 } /* Name.Variable.Global */ -.vi { color: #ef6155 } /* Name.Variable.Instance */ -.il { color: #f99b15 } /* Literal.Number.Integer.Long */ \ No newline at end of file diff --git a/theme/pygments/paraiso-dark.min.css b/theme/pygments/paraiso-dark.min.css deleted file mode 100644 index 0931d6e..0000000 --- a/theme/pygments/paraiso-dark.min.css +++ /dev/null @@ -1 +0,0 @@ -.highlight{background-color:#4f424c}.c{color:#776e71}.err{color:#ef6155}.k{color:#815ba4}.l{color:#f99b15}.n{color:#e7e9db}.o{color:#5bc4bf}.p{color:#e7e9db}.c1,.ch,.cm,.cp,.cpf,.cs{color:#776e71}.gd{color:#ef6155}.ge{font-style:italic}.gh{color:#e7e9db;font-weight:700}.gi{color:#48b685}.gp{color:#776e71}.gp,.gs,.gu{font-weight:700}.gu{color:#5bc4bf}.kc,.kd{color:#815ba4}.kn{color:#5bc4bf}.kp,.kr{color:#815ba4}.kt{color:#fec418}.ld{color:#48b685}.m{color:#f99b15}.s{color:#48b685}.na{color:#06b6ef}.nb{color:#e7e9db}.nc{color:#fec418}.no{color:#ef6155}.nd{color:#5bc4bf}.ni{color:#e7e9db}.ne{color:#ef6155}.nf{color:#06b6ef}.nl{color:#e7e9db}.nn{color:#fec418}.nx{color:#06b6ef}.py{color:#e7e9db}.nt{color:#5bc4bf}.nv{color:#ef6155}.ow{color:#5bc4bf}.w{color:#e7e9db}.mb,.mf,.mh,.mi,.mo{color:#f99b15}.sb{color:#48b685}.sc{color:#e7e9db}.sd{color:#776e71}.s2{color:#48b685}.se{color:#f99b15}.sh{color:#48b685}.si{color:#f99b15}.s1,.sr,.ss,.sx{color:#48b685}.bp{color:#e7e9db}.vc,.vg,.vi{color:#ef6155}.il{color:#f99b15} \ No newline at end of file diff --git a/theme/pygments/paraiso-light.css b/theme/pygments/paraiso-light.css deleted file mode 100644 index c7db930..0000000 --- a/theme/pygments/paraiso-light.css +++ /dev/null @@ -1,67 +0,0 @@ -.highlight { background-color: #a39e9b } -.c { color: #8d8687 } /* Comment */ -.err { color: #ef6155 } /* Error */ -.k { color: #815ba4 } /* Keyword */ -.l { color: #f99b15 } /* Literal */ -.n { color: #2f1e2e } /* Name */ -.o { color: #5bc4bf } /* Operator */ -.p { color: #2f1e2e } /* Punctuation */ -.ch { color: #8d8687 } /* Comment.Hashbang */ -.cm { color: #8d8687 } /* Comment.Multiline */ -.cp { color: #8d8687 } /* Comment.Preproc */ -.cpf { color: #8d8687 } /* Comment.PreprocFile */ -.c1 { color: #8d8687 } /* Comment.Single */ -.cs { color: #8d8687 } /* Comment.Special */ -.gd { color: #ef6155 } /* Generic.Deleted */ -.ge { font-style: italic } /* Generic.Emph */ -.gh { color: #2f1e2e; font-weight: bold } /* Generic.Heading */ -.gi { color: #48b685 } /* Generic.Inserted */ -.gp { color: #8d8687; font-weight: bold } /* Generic.Prompt */ -.gs { font-weight: bold } /* Generic.Strong */ -.gu { color: #5bc4bf; font-weight: bold } /* Generic.Subheading */ -.kc { color: #815ba4 } /* Keyword.Constant */ -.kd { color: #815ba4 } /* Keyword.Declaration */ -.kn { color: #5bc4bf } /* Keyword.Namespace */ -.kp { color: #815ba4 } /* Keyword.Pseudo */ -.kr { color: #815ba4 } /* Keyword.Reserved */ -.kt { color: #fec418 } /* Keyword.Type */ -.ld { color: #48b685 } /* Literal.Date */ -.m { color: #f99b15 } /* Literal.Number */ -.s { color: #48b685 } /* Literal.String */ -.na { color: #06b6ef } /* Name.Attribute */ -.nb { color: #2f1e2e } /* Name.Builtin */ -.nc { color: #fec418 } /* Name.Class */ -.no { color: #ef6155 } /* Name.Constant */ -.nd { color: #5bc4bf } /* Name.Decorator */ -.ni { color: #2f1e2e } /* Name.Entity */ -.ne { color: #ef6155 } /* Name.Exception */ -.nf { color: #06b6ef } /* Name.Function */ -.nl { color: #2f1e2e } /* Name.Label */ -.nn { color: #fec418 } /* Name.Namespace */ -.nx { color: #06b6ef } /* Name.Other */ -.py { color: #2f1e2e } /* Name.Property */ -.nt { color: #5bc4bf } /* Name.Tag */ -.nv { color: #ef6155 } /* Name.Variable */ -.ow { color: #5bc4bf } /* Operator.Word */ -.w { color: #2f1e2e } /* Text.Whitespace */ -.mb { color: #f99b15 } /* Literal.Number.Bin */ -.mf { color: #f99b15 } /* Literal.Number.Float */ -.mh { color: #f99b15 } /* Literal.Number.Hex */ -.mi { color: #f99b15 } /* Literal.Number.Integer */ -.mo { color: #f99b15 } /* Literal.Number.Oct */ -.sb { color: #48b685 } /* Literal.String.Backtick */ -.sc { color: #2f1e2e } /* Literal.String.Char */ -.sd { color: #8d8687 } /* Literal.String.Doc */ -.s2 { color: #48b685 } /* Literal.String.Double */ -.se { color: #f99b15 } /* Literal.String.Escape */ -.sh { color: #48b685 } /* Literal.String.Heredoc */ -.si { color: #f99b15 } /* Literal.String.Interpol */ -.sx { color: #48b685 } /* Literal.String.Other */ -.sr { color: #48b685 } /* Literal.String.Regex */ -.s1 { color: #48b685 } /* Literal.String.Single */ -.ss { color: #48b685 } /* Literal.String.Symbol */ -.bp { color: #2f1e2e } /* Name.Builtin.Pseudo */ -.vc { color: #ef6155 } /* Name.Variable.Class */ -.vg { color: #ef6155 } /* Name.Variable.Global */ -.vi { color: #ef6155 } /* Name.Variable.Instance */ -.il { color: #f99b15 } /* Literal.Number.Integer.Long */ \ No newline at end of file diff --git a/theme/pygments/paraiso-light.min.css b/theme/pygments/paraiso-light.min.css deleted file mode 100644 index f163e16..0000000 --- a/theme/pygments/paraiso-light.min.css +++ /dev/null @@ -1 +0,0 @@ -.highlight{background-color:#a39e9b}.c{color:#8d8687}.err{color:#ef6155}.k{color:#815ba4}.l{color:#f99b15}.n{color:#2f1e2e}.o{color:#5bc4bf}.p{color:#2f1e2e}.c1,.ch,.cm,.cp,.cpf,.cs{color:#8d8687}.gd{color:#ef6155}.ge{font-style:italic}.gh{color:#2f1e2e;font-weight:700}.gi{color:#48b685}.gp{color:#8d8687}.gp,.gs,.gu{font-weight:700}.gu{color:#5bc4bf}.kc,.kd{color:#815ba4}.kn{color:#5bc4bf}.kp,.kr{color:#815ba4}.kt{color:#fec418}.ld{color:#48b685}.m{color:#f99b15}.s{color:#48b685}.na{color:#06b6ef}.nb{color:#2f1e2e}.nc{color:#fec418}.no{color:#ef6155}.nd{color:#5bc4bf}.ni{color:#2f1e2e}.ne{color:#ef6155}.nf{color:#06b6ef}.nl{color:#2f1e2e}.nn{color:#fec418}.nx{color:#06b6ef}.py{color:#2f1e2e}.nt{color:#5bc4bf}.nv{color:#ef6155}.ow{color:#5bc4bf}.w{color:#2f1e2e}.mb,.mf,.mh,.mi,.mo{color:#f99b15}.sb{color:#48b685}.sc{color:#2f1e2e}.sd{color:#8d8687}.s2{color:#48b685}.se{color:#f99b15}.sh{color:#48b685}.si{color:#f99b15}.s1,.sr,.ss,.sx{color:#48b685}.bp{color:#2f1e2e}.vc,.vg,.vi{color:#ef6155}.il{color:#f99b15} \ No newline at end of file diff --git a/theme/pygments/pastie.css b/theme/pygments/pastie.css deleted file mode 100644 index 0484a40..0000000 --- a/theme/pygments/pastie.css +++ /dev/null @@ -1,63 +0,0 @@ -.highlight { background-color: #ffffcc } -.c { color: #888888 } /* Comment */ -.err { color: #a61717; background-color: #e3d2d2 } /* Error */ -.k { color: #008800; font-weight: bold } /* Keyword */ -.ch { color: #888888 } /* Comment.Hashbang */ -.cm { color: #888888 } /* Comment.Multiline */ -.cp { color: #cc0000; font-weight: bold } /* Comment.Preproc */ -.cpf { color: #888888 } /* Comment.PreprocFile */ -.c1 { color: #888888 } /* Comment.Single */ -.cs { color: #cc0000; font-weight: bold; background-color: #fff0f0 } /* Comment.Special */ -.gd { color: #000000; background-color: #ffdddd } /* Generic.Deleted */ -.ge { font-style: italic } /* Generic.Emph */ -.gr { color: #aa0000 } /* Generic.Error */ -.gh { color: #333333 } /* Generic.Heading */ -.gi { color: #000000; background-color: #ddffdd } /* Generic.Inserted */ -.go { color: #888888 } /* Generic.Output */ -.gp { color: #555555 } /* Generic.Prompt */ -.gs { font-weight: bold } /* Generic.Strong */ -.gu { color: #666666 } /* Generic.Subheading */ -.gt { color: #aa0000 } /* Generic.Traceback */ -.kc { color: #008800; font-weight: bold } /* Keyword.Constant */ -.kd { color: #008800; font-weight: bold } /* Keyword.Declaration */ -.kn { color: #008800; font-weight: bold } /* Keyword.Namespace */ -.kp { color: #008800 } /* Keyword.Pseudo */ -.kr { color: #008800; font-weight: bold } /* Keyword.Reserved */ -.kt { color: #888888; font-weight: bold } /* Keyword.Type */ -.m { color: #0000DD; font-weight: bold } /* Literal.Number */ -.s { color: #dd2200; background-color: #fff0f0 } /* Literal.String */ -.na { color: #336699 } /* Name.Attribute */ -.nb { color: #003388 } /* Name.Builtin */ -.nc { color: #bb0066; font-weight: bold } /* Name.Class */ -.no { color: #003366; font-weight: bold } /* Name.Constant */ -.nd { color: #555555 } /* Name.Decorator */ -.ne { color: #bb0066; font-weight: bold } /* Name.Exception */ -.nf { color: #0066bb; font-weight: bold } /* Name.Function */ -.nl { color: #336699; font-style: italic } /* Name.Label */ -.nn { color: #bb0066; font-weight: bold } /* Name.Namespace */ -.py { color: #336699; font-weight: bold } /* Name.Property */ -.nt { color: #bb0066; font-weight: bold } /* Name.Tag */ -.nv { color: #336699 } /* Name.Variable */ -.ow { color: #008800 } /* Operator.Word */ -.w { color: #bbbbbb } /* Text.Whitespace */ -.mb { color: #0000DD; font-weight: bold } /* Literal.Number.Bin */ -.mf { color: #0000DD; font-weight: bold } /* Literal.Number.Float */ -.mh { color: #0000DD; font-weight: bold } /* Literal.Number.Hex */ -.mi { color: #0000DD; font-weight: bold } /* Literal.Number.Integer */ -.mo { color: #0000DD; font-weight: bold } /* Literal.Number.Oct */ -.sb { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Backtick */ -.sc { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Char */ -.sd { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Doc */ -.s2 { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Double */ -.se { color: #0044dd; background-color: #fff0f0 } /* Literal.String.Escape */ -.sh { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Heredoc */ -.si { color: #3333bb; background-color: #fff0f0 } /* Literal.String.Interpol */ -.sx { color: #22bb22; background-color: #f0fff0 } /* Literal.String.Other */ -.sr { color: #008800; background-color: #fff0ff } /* Literal.String.Regex */ -.s1 { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Single */ -.ss { color: #aa6600; background-color: #fff0f0 } /* Literal.String.Symbol */ -.bp { color: #003388 } /* Name.Builtin.Pseudo */ -.vc { color: #336699 } /* Name.Variable.Class */ -.vg { color: #dd7700 } /* Name.Variable.Global */ -.vi { color: #3333bb } /* Name.Variable.Instance */ -.il { color: #0000DD; font-weight: bold } /* Literal.Number.Integer.Long */ \ No newline at end of file diff --git a/theme/pygments/pastie.min.css b/theme/pygments/pastie.min.css deleted file mode 100644 index 7a1b6fb..0000000 --- a/theme/pygments/pastie.min.css +++ /dev/null @@ -1 +0,0 @@ -.highlight{background-color:#ffc}.c{color:#888}.err{color:#a61717;background-color:#e3d2d2}.k{color:#080;font-weight:700}.ch,.cm{color:#888}.cp{color:#c00;font-weight:700}.c1,.cpf{color:#888}.cs{color:#c00;font-weight:700;background-color:#fff0f0}.gd{color:#000;background-color:#fdd}.ge{font-style:italic}.gr{color:#a00}.gh{color:#333}.gi{color:#000;background-color:#dfd}.go{color:#888}.gp{color:#555}.gs{font-weight:700}.gu{color:#666}.gt{color:#a00}.kc,.kd,.kn{color:#080;font-weight:700}.kp,.kr{color:#080}.kr,.kt{font-weight:700}.kt{color:#888}.m{color:#00d;font-weight:700}.s{color:#d20;background-color:#fff0f0}.na{color:#369}.nb{color:#038}.nc{color:#b06}.nc,.no{font-weight:700}.no{color:#036}.nd{color:#555}.ne{color:#b06}.ne,.nf{font-weight:700}.nf{color:#06b}.nl{color:#369;font-style:italic}.nn{color:#b06}.nn,.py{font-weight:700}.py{color:#369}.nt{color:#b06;font-weight:700}.nv{color:#369}.ow{color:#080}.w{color:#bbb}.mb,.mf,.mh,.mi,.mo{color:#00d;font-weight:700}.s2,.sb,.sc,.sd{color:#d20}.s2,.sb,.sc,.sd,.se{background-color:#fff0f0}.se{color:#04d}.sh{color:#d20}.sh,.si{background-color:#fff0f0}.si{color:#33b}.sx{color:#2b2;background-color:#f0fff0}.sr{color:#080;background-color:#fff0ff}.s1{color:#d20}.s1,.ss{background-color:#fff0f0}.ss{color:#a60}.bp{color:#038}.vc{color:#369}.vg{color:#d70}.vi{color:#33b}.il{color:#00d;font-weight:700} \ No newline at end of file diff --git a/theme/pygments/perldoc.css b/theme/pygments/perldoc.css deleted file mode 100644 index a488774..0000000 --- a/theme/pygments/perldoc.css +++ /dev/null @@ -1,61 +0,0 @@ -.highlight { background-color: #ffffcc } -.c { color: #228B22 } /* Comment */ -.err { color: #a61717; background-color: #e3d2d2 } /* Error */ -.k { color: #8B008B; font-weight: bold } /* Keyword */ -.ch { color: #228B22 } /* Comment.Hashbang */ -.cm { color: #228B22 } /* Comment.Multiline */ -.cp { color: #1e889b } /* Comment.Preproc */ -.cpf { color: #228B22 } /* Comment.PreprocFile */ -.c1 { color: #228B22 } /* Comment.Single */ -.cs { color: #8B008B; font-weight: bold } /* Comment.Special */ -.gd { color: #aa0000 } /* Generic.Deleted */ -.ge { font-style: italic } /* Generic.Emph */ -.gr { color: #aa0000 } /* Generic.Error */ -.gh { color: #000080; font-weight: bold } /* Generic.Heading */ -.gi { color: #00aa00 } /* Generic.Inserted */ -.go { color: #888888 } /* Generic.Output */ -.gp { color: #555555 } /* Generic.Prompt */ -.gs { font-weight: bold } /* Generic.Strong */ -.gu { color: #800080; font-weight: bold } /* Generic.Subheading */ -.gt { color: #aa0000 } /* Generic.Traceback */ -.kc { color: #8B008B; font-weight: bold } /* Keyword.Constant */ -.kd { color: #8B008B; font-weight: bold } /* Keyword.Declaration */ -.kn { color: #8B008B; font-weight: bold } /* Keyword.Namespace */ -.kp { color: #8B008B; font-weight: bold } /* Keyword.Pseudo */ -.kr { color: #8B008B; font-weight: bold } /* Keyword.Reserved */ -.kt { color: #a7a7a7; font-weight: bold } /* Keyword.Type */ -.m { color: #B452CD } /* Literal.Number */ -.s { color: #CD5555 } /* Literal.String */ -.na { color: #658b00 } /* Name.Attribute */ -.nb { color: #658b00 } /* Name.Builtin */ -.nc { color: #008b45; font-weight: bold } /* Name.Class */ -.no { color: #00688B } /* Name.Constant */ -.nd { color: #707a7c } /* Name.Decorator */ -.ne { color: #008b45; font-weight: bold } /* Name.Exception */ -.nf { color: #008b45 } /* Name.Function */ -.nn { color: #008b45; text-decoration: underline } /* Name.Namespace */ -.nt { color: #8B008B; font-weight: bold } /* Name.Tag */ -.nv { color: #00688B } /* Name.Variable */ -.ow { color: #8B008B } /* Operator.Word */ -.w { color: #bbbbbb } /* Text.Whitespace */ -.mb { color: #B452CD } /* Literal.Number.Bin */ -.mf { color: #B452CD } /* Literal.Number.Float */ -.mh { color: #B452CD } /* Literal.Number.Hex */ -.mi { color: #B452CD } /* Literal.Number.Integer */ -.mo { color: #B452CD } /* Literal.Number.Oct */ -.sb { color: #CD5555 } /* Literal.String.Backtick */ -.sc { color: #CD5555 } /* Literal.String.Char */ -.sd { color: #CD5555 } /* Literal.String.Doc */ -.s2 { color: #CD5555 } /* Literal.String.Double */ -.se { color: #CD5555 } /* Literal.String.Escape */ -.sh { color: #1c7e71; font-style: italic } /* Literal.String.Heredoc */ -.si { color: #CD5555 } /* Literal.String.Interpol */ -.sx { color: #cb6c20 } /* Literal.String.Other */ -.sr { color: #1c7e71 } /* Literal.String.Regex */ -.s1 { color: #CD5555 } /* Literal.String.Single */ -.ss { color: #CD5555 } /* Literal.String.Symbol */ -.bp { color: #658b00 } /* Name.Builtin.Pseudo */ -.vc { color: #00688B } /* Name.Variable.Class */ -.vg { color: #00688B } /* Name.Variable.Global */ -.vi { color: #00688B } /* Name.Variable.Instance */ -.il { color: #B452CD } /* Literal.Number.Integer.Long */ \ No newline at end of file diff --git a/theme/pygments/perldoc.min.css b/theme/pygments/perldoc.min.css deleted file mode 100644 index a22b37d..0000000 --- a/theme/pygments/perldoc.min.css +++ /dev/null @@ -1 +0,0 @@ -.highlight{background-color:#ffc}.c{color:#228b22}.err{color:#a61717;background-color:#e3d2d2}.k{color:#8b008b;font-weight:700}.ch,.cm{color:#228b22}.cp{color:#1e889b}.c1,.cpf{color:#228b22}.cs{color:#8b008b;font-weight:700}.gd{color:#a00}.ge{font-style:italic}.gr{color:#a00}.gh{color:navy;font-weight:700}.gi{color:#0a0}.go{color:#888}.gp{color:#555}.gs,.gu{font-weight:700}.gu{color:purple}.gt{color:#a00}.kc,.kd,.kn,.kp,.kr{color:#8b008b;font-weight:700}.kt{color:#a7a7a7;font-weight:700}.m{color:#b452cd}.s{color:#cd5555}.na,.nb{color:#658b00}.nc{color:#008b45;font-weight:700}.no{color:#00688b}.nd{color:#707a7c}.ne{font-weight:700}.ne,.nf,.nn{color:#008b45}.nn{text-decoration:underline}.nt{color:#8b008b;font-weight:700}.nv{color:#00688b}.ow{color:#8b008b}.w{color:#bbb}.mb,.mf,.mh,.mi,.mo{color:#b452cd}.s2,.sb,.sc,.sd,.se{color:#cd5555}.sh{color:#1c7e71;font-style:italic}.si{color:#cd5555}.sx{color:#cb6c20}.sr{color:#1c7e71}.s1,.ss{color:#cd5555}.bp{color:#658b00}.vc,.vg,.vi{color:#00688b}.il{color:#b452cd} \ No newline at end of file diff --git a/theme/pygments/rrt.css b/theme/pygments/rrt.css deleted file mode 100644 index 9e01466..0000000 --- a/theme/pygments/rrt.css +++ /dev/null @@ -1,33 +0,0 @@ -.highlight { background-color: #0000ff } -.c { color: #00ff00 } /* Comment */ -.k { color: #ff0000 } /* Keyword */ -.ch { color: #00ff00 } /* Comment.Hashbang */ -.cm { color: #00ff00 } /* Comment.Multiline */ -.cp { color: #e5e5e5 } /* Comment.Preproc */ -.cpf { color: #00ff00 } /* Comment.PreprocFile */ -.c1 { color: #00ff00 } /* Comment.Single */ -.cs { color: #00ff00 } /* Comment.Special */ -.kc { color: #ff0000 } /* Keyword.Constant */ -.kd { color: #ff0000 } /* Keyword.Declaration */ -.kn { color: #ff0000 } /* Keyword.Namespace */ -.kp { color: #ff0000 } /* Keyword.Pseudo */ -.kr { color: #ff0000 } /* Keyword.Reserved */ -.kt { color: #ee82ee } /* Keyword.Type */ -.s { color: #87ceeb } /* Literal.String */ -.no { color: #7fffd4 } /* Name.Constant */ -.nf { color: #ffff00 } /* Name.Function */ -.nv { color: #eedd82 } /* Name.Variable */ -.sb { color: #87ceeb } /* Literal.String.Backtick */ -.sc { color: #87ceeb } /* Literal.String.Char */ -.sd { color: #87ceeb } /* Literal.String.Doc */ -.s2 { color: #87ceeb } /* Literal.String.Double */ -.se { color: #87ceeb } /* Literal.String.Escape */ -.sh { color: #87ceeb } /* Literal.String.Heredoc */ -.si { color: #87ceeb } /* Literal.String.Interpol */ -.sx { color: #87ceeb } /* Literal.String.Other */ -.sr { color: #87ceeb } /* Literal.String.Regex */ -.s1 { color: #87ceeb } /* Literal.String.Single */ -.ss { color: #87ceeb } /* Literal.String.Symbol */ -.vc { color: #eedd82 } /* Name.Variable.Class */ -.vg { color: #eedd82 } /* Name.Variable.Global */ -.vi { color: #eedd82 } /* Name.Variable.Instance */ \ No newline at end of file diff --git a/theme/pygments/rrt.min.css b/theme/pygments/rrt.min.css deleted file mode 100644 index 5c9c744..0000000 --- a/theme/pygments/rrt.min.css +++ /dev/null @@ -1 +0,0 @@ -.highlight{background-color:#00f}.c{color:#0f0}.k{color:red}.ch,.cm{color:#0f0}.cp{color:#e5e5e5}.c1,.cpf,.cs{color:#0f0}.kc,.kd,.kn,.kp,.kr{color:red}.kt{color:violet}.s{color:#87ceeb}.no{color:#7fffd4}.nf{color:#ff0}.nv{color:#eedd82}.s1,.s2,.sb,.sc,.sd,.se,.sh,.si,.sr,.ss,.sx{color:#87ceeb}.vc,.vg,.vi{color:#eedd82} \ No newline at end of file diff --git a/theme/pygments/solarized-dark.css b/theme/pygments/solarized-dark.css deleted file mode 100644 index 41cc9f6..0000000 --- a/theme/pygments/solarized-dark.css +++ /dev/null @@ -1,87 +0,0 @@ -/* Solarized Dark - -For use with Jekyll and Pygments - -http://ethanschoonover.com/solarized - -SOLARIZED HEX ROLE ---------- -------- ------------------------------------------ -base03 #002b36 background -base01 #586e75 comments / secondary content -base1 #93a1a1 body text / default code / primary content -orange #cb4b16 constants -red #dc322f regex, special keywords -blue #268bd2 reserved keywords -cyan #2aa198 strings, numbers -green #859900 operators, other keywords -*/ - -.highlight {background-color: #002b36; color: #93a1a1;} -.highlight .c { color: #586e75 } /* Comment */ -.highlight .err { color: #93a1a1 } /* Error */ -.highlight .g { color: #93a1a1 } /* Generic */ -.highlight .k { color: #859900 } /* Keyword */ -.highlight .l { color: #93a1a1 } /* Literal */ -.highlight .n { color: #93a1a1 } /* Name */ -.highlight .o { color: #859900 } /* Operator */ -.highlight .x { color: #cb4b16 } /* Other */ -.highlight .p { color: #93a1a1 } /* Punctuation */ -.highlight .cm { color: #586e75 } /* Comment.Multiline */ -.highlight .cp { color: #859900 } /* Comment.Preproc */ -.highlight .c1 { color: #586e75 } /* Comment.Single */ -.highlight .cs { color: #859900 } /* Comment.Special */ -.highlight .gd { color: #2aa198 } /* Generic.Deleted */ -.highlight .ge { color: #93a1a1; font-style: italic } /* Generic.Emph */ -.highlight .gr { color: #dc322f } /* Generic.Error */ -.highlight .gh { color: #cb4b16 } /* Generic.Heading */ -.highlight .gi { color: #859900 } /* Generic.Inserted */ -.highlight .go { color: #93a1a1 } /* Generic.Output */ -.highlight .gp { color: #93a1a1 } /* Generic.Prompt */ -.highlight .gs { color: #93a1a1; font-weight: bold } /* Generic.Strong */ -.highlight .gu { color: #cb4b16 } /* Generic.Subheading */ -.highlight .gt { color: #93a1a1 } /* Generic.Traceback */ -.highlight .kc { color: #cb4b16 } /* Keyword.Constant */ -.highlight .kd { color: #268bd2 } /* Keyword.Declaration */ -.highlight .kn { color: #859900 } /* Keyword.Namespace */ -.highlight .kp { color: #859900 } /* Keyword.Pseudo */ -.highlight .kr { color: #268bd2 } /* Keyword.Reserved */ -.highlight .kt { color: #dc322f } /* Keyword.Type */ -.highlight .ld { color: #93a1a1 } /* Literal.Date */ -.highlight .m { color: #2aa198 } /* Literal.Number */ -.highlight .s { color: #2aa198 } /* Literal.String */ -.highlight .na { color: #93a1a1 } /* Name.Attribute */ -.highlight .nb { color: #B58900 } /* Name.Builtin */ -.highlight .nc { color: #268bd2 } /* Name.Class */ -.highlight .no { color: #cb4b16 } /* Name.Constant */ -.highlight .nd { color: #268bd2 } /* Name.Decorator */ -.highlight .ni { color: #cb4b16 } /* Name.Entity */ -.highlight .ne { color: #cb4b16 } /* Name.Exception */ -.highlight .nf { color: #268bd2 } /* Name.Function */ -.highlight .nl { color: #93a1a1 } /* Name.Label */ -.highlight .nn { color: #93a1a1 } /* Name.Namespace */ -.highlight .nx { color: #93a1a1 } /* Name.Other */ -.highlight .py { color: #93a1a1 } /* Name.Property */ -.highlight .nt { color: #268bd2 } /* Name.Tag */ -.highlight .nv { color: #268bd2 } /* Name.Variable */ -.highlight .ow { color: #859900 } /* Operator.Word */ -.highlight .w { color: #93a1a1 } /* Text.Whitespace */ -.highlight .mf { color: #2aa198 } /* Literal.Number.Float */ -.highlight .mh { color: #2aa198 } /* Literal.Number.Hex */ -.highlight .mi { color: #2aa198 } /* Literal.Number.Integer */ -.highlight .mo { color: #2aa198 } /* Literal.Number.Oct */ -.highlight .sb { color: #586e75 } /* Literal.String.Backtick */ -.highlight .sc { color: #2aa198 } /* Literal.String.Char */ -.highlight .sd { color: #93a1a1 } /* Literal.String.Doc */ -.highlight .s2 { color: #2aa198 } /* Literal.String.Double */ -.highlight .se { color: #cb4b16 } /* Literal.String.Escape */ -.highlight .sh { color: #93a1a1 } /* Literal.String.Heredoc */ -.highlight .si { color: #2aa198 } /* Literal.String.Interpol */ -.highlight .sx { color: #2aa198 } /* Literal.String.Other */ -.highlight .sr { color: #dc322f } /* Literal.String.Regex */ -.highlight .s1 { color: #2aa198 } /* Literal.String.Single */ -.highlight .ss { color: #2aa198 } /* Literal.String.Symbol */ -.highlight .bp { color: #268bd2 } /* Name.Builtin.Pseudo */ -.highlight .vc { color: #268bd2 } /* Name.Variable.Class */ -.highlight .vg { color: #268bd2 } /* Name.Variable.Global */ -.highlight .vi { color: #268bd2 } /* Name.Variable.Instance */ -.highlight .il { color: #2aa198 } /* Literal.Number.Integer.Long */ diff --git a/theme/pygments/solarized-dark.min.css b/theme/pygments/solarized-dark.min.css deleted file mode 100644 index 259d7cb..0000000 --- a/theme/pygments/solarized-dark.min.css +++ /dev/null @@ -1 +0,0 @@ -.highlight{background-color:#002b36;color:#93a1a1}.highlight .c{color:#586e75}.highlight .err,.highlight .g{color:#93a1a1}.highlight .k{color:#859900}.highlight .l,.highlight .n{color:#93a1a1}.highlight .o{color:#859900}.highlight .x{color:#cb4b16}.highlight .p{color:#93a1a1}.highlight .cm{color:#586e75}.highlight .cp{color:#859900}.highlight .c1{color:#586e75}.highlight .cs{color:#859900}.highlight .gd{color:#2aa198}.highlight .ge{color:#93a1a1;font-style:italic}.highlight .gr{color:#dc322f}.highlight .gh{color:#cb4b16}.highlight .gi{color:#859900}.highlight .go,.highlight .gp{color:#93a1a1}.highlight .gs{color:#93a1a1;font-weight:700}.highlight .gu{color:#cb4b16}.highlight .gt{color:#93a1a1}.highlight .kc{color:#cb4b16}.highlight .kd{color:#268bd2}.highlight .kn,.highlight .kp{color:#859900}.highlight .kr{color:#268bd2}.highlight .kt{color:#dc322f}.highlight .ld{color:#93a1a1}.highlight .m,.highlight .s{color:#2aa198}.highlight .na{color:#93a1a1}.highlight .nb{color:#b58900}.highlight .nc{color:#268bd2}.highlight .no{color:#cb4b16}.highlight .nd{color:#268bd2}.highlight .ne,.highlight .ni{color:#cb4b16}.highlight .nf{color:#268bd2}.highlight .nl,.highlight .nn,.highlight .nx,.highlight .py{color:#93a1a1}.highlight .nt,.highlight .nv{color:#268bd2}.highlight .ow{color:#859900}.highlight .w{color:#93a1a1}.highlight .mf,.highlight .mh,.highlight .mi,.highlight .mo{color:#2aa198}.highlight .sb{color:#586e75}.highlight .sc{color:#2aa198}.highlight .sd{color:#93a1a1}.highlight .s2{color:#2aa198}.highlight .se{color:#cb4b16}.highlight .sh{color:#93a1a1}.highlight .si,.highlight .sx{color:#2aa198}.highlight .sr{color:#dc322f}.highlight .s1,.highlight .ss{color:#2aa198}.highlight .bp,.highlight .vc,.highlight .vg,.highlight .vi{color:#268bd2}.highlight .il{color:#2aa198} \ No newline at end of file diff --git a/theme/pygments/tango.css b/theme/pygments/tango.css deleted file mode 100644 index de6d99a..0000000 --- a/theme/pygments/tango.css +++ /dev/null @@ -1,72 +0,0 @@ -.highlight { background-color: #ffffcc } -.c { color: #8f5902; font-style: italic } /* Comment */ -.err { color: #a40000; border: 1px solid #ef2929 } /* Error */ -.g { color: #000000 } /* Generic */ -.k { color: #204a87; font-weight: bold } /* Keyword */ -.l { color: #000000 } /* Literal */ -.n { color: #000000 } /* Name */ -.o { color: #ce5c00; font-weight: bold } /* Operator */ -.x { color: #000000 } /* Other */ -.p { color: #000000; font-weight: bold } /* Punctuation */ -.ch { color: #8f5902; font-style: italic } /* Comment.Hashbang */ -.cm { color: #8f5902; font-style: italic } /* Comment.Multiline */ -.cp { color: #8f5902; font-style: italic } /* Comment.Preproc */ -.cpf { color: #8f5902; font-style: italic } /* Comment.PreprocFile */ -.c1 { color: #8f5902; font-style: italic } /* Comment.Single */ -.cs { color: #8f5902; font-style: italic } /* Comment.Special */ -.gd { color: #a40000 } /* Generic.Deleted */ -.ge { color: #000000; font-style: italic } /* Generic.Emph */ -.gr { color: #ef2929 } /* Generic.Error */ -.gh { color: #000080; font-weight: bold } /* Generic.Heading */ -.gi { color: #00A000 } /* Generic.Inserted */ -.go { color: #000000; font-style: italic } /* Generic.Output */ -.gp { color: #8f5902 } /* Generic.Prompt */ -.gs { color: #000000; font-weight: bold } /* Generic.Strong */ -.gu { color: #800080; font-weight: bold } /* Generic.Subheading */ -.gt { color: #a40000; font-weight: bold } /* Generic.Traceback */ -.kc { color: #204a87; font-weight: bold } /* Keyword.Constant */ -.kd { color: #204a87; font-weight: bold } /* Keyword.Declaration */ -.kn { color: #204a87; font-weight: bold } /* Keyword.Namespace */ -.kp { color: #204a87; font-weight: bold } /* Keyword.Pseudo */ -.kr { color: #204a87; font-weight: bold } /* Keyword.Reserved */ -.kt { color: #204a87; font-weight: bold } /* Keyword.Type */ -.ld { color: #000000 } /* Literal.Date */ -.m { color: #0000cf; font-weight: bold } /* Literal.Number */ -.s { color: #4e9a06 } /* Literal.String */ -.na { color: #c4a000 } /* Name.Attribute */ -.nb { color: #204a87 } /* Name.Builtin */ -.nc { color: #000000 } /* Name.Class */ -.no { color: #000000 } /* Name.Constant */ -.nd { color: #5c35cc; font-weight: bold } /* Name.Decorator */ -.ni { color: #ce5c00 } /* Name.Entity */ -.ne { color: #cc0000; font-weight: bold } /* Name.Exception */ -.nf { color: #000000 } /* Name.Function */ -.nl { color: #f57900 } /* Name.Label */ -.nn { color: #000000 } /* Name.Namespace */ -.nx { color: #000000 } /* Name.Other */ -.py { color: #000000 } /* Name.Property */ -.nt { color: #204a87; font-weight: bold } /* Name.Tag */ -.nv { color: #000000 } /* Name.Variable */ -.ow { color: #204a87; font-weight: bold } /* Operator.Word */ -.w { color: #f8f8f8; text-decoration: underline } /* Text.Whitespace */ -.mb { color: #0000cf; font-weight: bold } /* Literal.Number.Bin */ -.mf { color: #0000cf; font-weight: bold } /* Literal.Number.Float */ -.mh { color: #0000cf; font-weight: bold } /* Literal.Number.Hex */ -.mi { color: #0000cf; font-weight: bold } /* Literal.Number.Integer */ -.mo { color: #0000cf; font-weight: bold } /* Literal.Number.Oct */ -.sb { color: #4e9a06 } /* Literal.String.Backtick */ -.sc { color: #4e9a06 } /* Literal.String.Char */ -.sd { color: #8f5902; font-style: italic } /* Literal.String.Doc */ -.s2 { color: #4e9a06 } /* Literal.String.Double */ -.se { color: #4e9a06 } /* Literal.String.Escape */ -.sh { color: #4e9a06 } /* Literal.String.Heredoc */ -.si { color: #4e9a06 } /* Literal.String.Interpol */ -.sx { color: #4e9a06 } /* Literal.String.Other */ -.sr { color: #4e9a06 } /* Literal.String.Regex */ -.s1 { color: #4e9a06 } /* Literal.String.Single */ -.ss { color: #4e9a06 } /* Literal.String.Symbol */ -.bp { color: #3465a4 } /* Name.Builtin.Pseudo */ -.vc { color: #000000 } /* Name.Variable.Class */ -.vg { color: #000000 } /* Name.Variable.Global */ -.vi { color: #000000 } /* Name.Variable.Instance */ -.il { color: #0000cf; font-weight: bold } /* Literal.Number.Integer.Long */ \ No newline at end of file diff --git a/theme/pygments/tango.min.css b/theme/pygments/tango.min.css deleted file mode 100644 index c5fdf76..0000000 --- a/theme/pygments/tango.min.css +++ /dev/null @@ -1 +0,0 @@ -.highlight{background-color:#ffc}.c{color:#8f5902;font-style:italic}.err{color:#a40000;border:1px solid #ef2929}.g{color:#000}.k{color:#204a87;font-weight:700}.l,.n{color:#000}.o{color:#ce5c00;font-weight:700}.p,.x{color:#000}.p{font-weight:700}.c1,.ch,.cm,.cp,.cpf,.cs{color:#8f5902;font-style:italic}.gd{color:#a40000}.ge{color:#000;font-style:italic}.gr{color:#ef2929}.gh{color:navy;font-weight:700}.gi{color:#00a000}.go{color:#000;font-style:italic}.gp{color:#8f5902}.gs{color:#000}.gs,.gu{font-weight:700}.gu{color:purple}.gt{color:#a40000;font-weight:700}.kc,.kd,.kn,.kp,.kr,.kt{color:#204a87;font-weight:700}.ld{color:#000}.m{color:#0000cf;font-weight:700}.s{color:#4e9a06}.na{color:#c4a000}.nb{color:#204a87}.nc,.no{color:#000}.nd{color:#5c35cc;font-weight:700}.ni{color:#ce5c00}.ne{color:#c00;font-weight:700}.nf{color:#000}.nl{color:#f57900}.nn,.nx,.py{color:#000}.nt{color:#204a87;font-weight:700}.nv{color:#000}.ow{color:#204a87;font-weight:700}.w{color:#f8f8f8;text-decoration:underline}.mb,.mf,.mh,.mi,.mo{color:#0000cf;font-weight:700}.sb,.sc{color:#4e9a06}.sd{color:#8f5902;font-style:italic}.s1,.s2,.se,.sh,.si,.sr,.ss,.sx{color:#4e9a06}.bp{color:#3465a4}.vc,.vg,.vi{color:#000}.il{color:#0000cf;font-weight:700} \ No newline at end of file diff --git a/theme/pygments/trac.css b/theme/pygments/trac.css deleted file mode 100644 index fe1440d..0000000 --- a/theme/pygments/trac.css +++ /dev/null @@ -1,62 +0,0 @@ -.highlight { background-color: #ffffcc } -.c { color: #999988; font-style: italic } /* Comment */ -.err { color: #a61717; background-color: #e3d2d2 } /* Error */ -.k { font-weight: bold } /* Keyword */ -.o { font-weight: bold } /* Operator */ -.ch { color: #999988; font-style: italic } /* Comment.Hashbang */ -.cm { color: #999988; font-style: italic } /* Comment.Multiline */ -.cp { color: #999999; font-weight: bold } /* Comment.Preproc */ -.cpf { color: #999988; font-style: italic } /* Comment.PreprocFile */ -.c1 { color: #999988; font-style: italic } /* Comment.Single */ -.cs { color: #999999; font-weight: bold; font-style: italic } /* Comment.Special */ -.gd { color: #000000; background-color: #ffdddd } /* Generic.Deleted */ -.ge { font-style: italic } /* Generic.Emph */ -.gr { color: #aa0000 } /* Generic.Error */ -.gh { color: #999999 } /* Generic.Heading */ -.gi { color: #000000; background-color: #ddffdd } /* Generic.Inserted */ -.go { color: #888888 } /* Generic.Output */ -.gp { color: #555555 } /* Generic.Prompt */ -.gs { font-weight: bold } /* Generic.Strong */ -.gu { color: #aaaaaa } /* Generic.Subheading */ -.gt { color: #aa0000 } /* Generic.Traceback */ -.kc { font-weight: bold } /* Keyword.Constant */ -.kd { font-weight: bold } /* Keyword.Declaration */ -.kn { font-weight: bold } /* Keyword.Namespace */ -.kp { font-weight: bold } /* Keyword.Pseudo */ -.kr { font-weight: bold } /* Keyword.Reserved */ -.kt { color: #445588; font-weight: bold } /* Keyword.Type */ -.m { color: #009999 } /* Literal.Number */ -.s { color: #bb8844 } /* Literal.String */ -.na { color: #008080 } /* Name.Attribute */ -.nb { color: #999999 } /* Name.Builtin */ -.nc { color: #445588; font-weight: bold } /* Name.Class */ -.no { color: #008080 } /* Name.Constant */ -.ni { color: #800080 } /* Name.Entity */ -.ne { color: #990000; font-weight: bold } /* Name.Exception */ -.nf { color: #990000; font-weight: bold } /* Name.Function */ -.nn { color: #555555 } /* Name.Namespace */ -.nt { color: #000080 } /* Name.Tag */ -.nv { color: #008080 } /* Name.Variable */ -.ow { font-weight: bold } /* Operator.Word */ -.w { color: #bbbbbb } /* Text.Whitespace */ -.mb { color: #009999 } /* Literal.Number.Bin */ -.mf { color: #009999 } /* Literal.Number.Float */ -.mh { color: #009999 } /* Literal.Number.Hex */ -.mi { color: #009999 } /* Literal.Number.Integer */ -.mo { color: #009999 } /* Literal.Number.Oct */ -.sb { color: #bb8844 } /* Literal.String.Backtick */ -.sc { color: #bb8844 } /* Literal.String.Char */ -.sd { color: #bb8844 } /* Literal.String.Doc */ -.s2 { color: #bb8844 } /* Literal.String.Double */ -.se { color: #bb8844 } /* Literal.String.Escape */ -.sh { color: #bb8844 } /* Literal.String.Heredoc */ -.si { color: #bb8844 } /* Literal.String.Interpol */ -.sx { color: #bb8844 } /* Literal.String.Other */ -.sr { color: #808000 } /* Literal.String.Regex */ -.s1 { color: #bb8844 } /* Literal.String.Single */ -.ss { color: #bb8844 } /* Literal.String.Symbol */ -.bp { color: #999999 } /* Name.Builtin.Pseudo */ -.vc { color: #008080 } /* Name.Variable.Class */ -.vg { color: #008080 } /* Name.Variable.Global */ -.vi { color: #008080 } /* Name.Variable.Instance */ -.il { color: #009999 } /* Literal.Number.Integer.Long */ \ No newline at end of file diff --git a/theme/pygments/trac.min.css b/theme/pygments/trac.min.css deleted file mode 100644 index c802a23..0000000 --- a/theme/pygments/trac.min.css +++ /dev/null @@ -1 +0,0 @@ -.highlight{background-color:#ffc}.c{color:#998;font-style:italic}.err{color:#a61717;background-color:#e3d2d2}.k,.o{font-weight:700}.ch,.cm{color:#998;font-style:italic}.cp{color:#999;font-weight:700}.c1,.cpf{color:#998}.c1,.cpf,.cs{font-style:italic}.cs{color:#999;font-weight:700}.gd{color:#000;background-color:#fdd}.ge{font-style:italic}.gr{color:#a00}.gh{color:#999}.gi{color:#000;background-color:#dfd}.go{color:#888}.gp{color:#555}.gs{font-weight:700}.gu{color:#aaa}.gt{color:#a00}.kc,.kd,.kn,.kp,.kr,.kt{font-weight:700}.kt{color:#458}.m{color:#099}.s{color:#b84}.na{color:teal}.nb{color:#999}.nc{color:#458;font-weight:700}.no{color:teal}.ni{color:purple}.ne,.nf{color:#900;font-weight:700}.nn{color:#555}.nt{color:navy}.nv{color:teal}.ow{font-weight:700}.w{color:#bbb}.mb,.mf,.mh,.mi,.mo{color:#099}.s2,.sb,.sc,.sd,.se,.sh,.si,.sx{color:#b84}.sr{color:olive}.s1,.ss{color:#b84}.bp{color:#999}.vc,.vg,.vi{color:teal}.il{color:#099} \ No newline at end of file diff --git a/theme/pygments/vim.css b/theme/pygments/vim.css deleted file mode 100644 index 3c4a177..0000000 --- a/theme/pygments/vim.css +++ /dev/null @@ -1,73 +0,0 @@ -.highlight { background-color: #222222 } -.c { color: #000080 } /* Comment */ -.err { color: #cccccc; border: 1px solid #FF0000 } /* Error */ -.esc { color: #cccccc } /* Escape */ -.g { color: #cccccc } /* Generic */ -.k { color: #cdcd00 } /* Keyword */ -.l { color: #cccccc } /* Literal */ -.n { color: #cccccc } /* Name */ -.o { color: #3399cc } /* Operator */ -.x { color: #cccccc } /* Other */ -.p { color: #cccccc } /* Punctuation */ -.ch { color: #000080 } /* Comment.Hashbang */ -.cm { color: #000080 } /* Comment.Multiline */ -.cp { color: #000080 } /* Comment.Preproc */ -.cpf { color: #000080 } /* Comment.PreprocFile */ -.c1 { color: #000080 } /* Comment.Single */ -.cs { color: #cd0000; font-weight: bold } /* Comment.Special */ -.gd { color: #cd0000 } /* Generic.Deleted */ -.ge { color: #cccccc; font-style: italic } /* Generic.Emph */ -.gr { color: #FF0000 } /* Generic.Error */ -.gh { color: #000080; font-weight: bold } /* Generic.Heading */ -.gi { color: #00cd00 } /* Generic.Inserted */ -.go { color: #888888 } /* Generic.Output */ -.gp { color: #000080; font-weight: bold } /* Generic.Prompt */ -.gs { color: #cccccc; font-weight: bold } /* Generic.Strong */ -.gu { color: #800080; font-weight: bold } /* Generic.Subheading */ -.gt { color: #0044DD } /* Generic.Traceback */ -.kc { color: #cdcd00 } /* Keyword.Constant */ -.kd { color: #00cd00 } /* Keyword.Declaration */ -.kn { color: #cd00cd } /* Keyword.Namespace */ -.kp { color: #cdcd00 } /* Keyword.Pseudo */ -.kr { color: #cdcd00 } /* Keyword.Reserved */ -.kt { color: #00cd00 } /* Keyword.Type */ -.ld { color: #cccccc } /* Literal.Date */ -.m { color: #cd00cd } /* Literal.Number */ -.s { color: #cd0000 } /* Literal.String */ -.na { color: #cccccc } /* Name.Attribute */ -.nb { color: #cd00cd } /* Name.Builtin */ -.nc { color: #00cdcd } /* Name.Class */ -.no { color: #cccccc } /* Name.Constant */ -.nd { color: #cccccc } /* Name.Decorator */ -.ni { color: #cccccc } /* Name.Entity */ -.ne { color: #666699; font-weight: bold } /* Name.Exception */ -.nf { color: #cccccc } /* Name.Function */ -.nl { color: #cccccc } /* Name.Label */ -.nn { color: #cccccc } /* Name.Namespace */ -.nx { color: #cccccc } /* Name.Other */ -.py { color: #cccccc } /* Name.Property */ -.nt { color: #cccccc } /* Name.Tag */ -.nv { color: #00cdcd } /* Name.Variable */ -.ow { color: #cdcd00 } /* Operator.Word */ -.w { color: #cccccc } /* Text.Whitespace */ -.mb { color: #cd00cd } /* Literal.Number.Bin */ -.mf { color: #cd00cd } /* Literal.Number.Float */ -.mh { color: #cd00cd } /* Literal.Number.Hex */ -.mi { color: #cd00cd } /* Literal.Number.Integer */ -.mo { color: #cd00cd } /* Literal.Number.Oct */ -.sb { color: #cd0000 } /* Literal.String.Backtick */ -.sc { color: #cd0000 } /* Literal.String.Char */ -.sd { color: #cd0000 } /* Literal.String.Doc */ -.s2 { color: #cd0000 } /* Literal.String.Double */ -.se { color: #cd0000 } /* Literal.String.Escape */ -.sh { color: #cd0000 } /* Literal.String.Heredoc */ -.si { color: #cd0000 } /* Literal.String.Interpol */ -.sx { color: #cd0000 } /* Literal.String.Other */ -.sr { color: #cd0000 } /* Literal.String.Regex */ -.s1 { color: #cd0000 } /* Literal.String.Single */ -.ss { color: #cd0000 } /* Literal.String.Symbol */ -.bp { color: #cd00cd } /* Name.Builtin.Pseudo */ -.vc { color: #00cdcd } /* Name.Variable.Class */ -.vg { color: #00cdcd } /* Name.Variable.Global */ -.vi { color: #00cdcd } /* Name.Variable.Instance */ -.il { color: #cd00cd } /* Literal.Number.Integer.Long */ \ No newline at end of file diff --git a/theme/pygments/vim.min.css b/theme/pygments/vim.min.css deleted file mode 100644 index 3b4bb4f..0000000 --- a/theme/pygments/vim.min.css +++ /dev/null @@ -1 +0,0 @@ -.highlight{background-color:#222}.c{color:navy}.err{border:1px solid red}.err,.esc,.g{color:#ccc}.k{color:#cdcd00}.l,.n{color:#ccc}.o{color:#39c}.p,.x{color:#ccc}.c1,.ch,.cm,.cp,.cpf{color:navy}.cs{font-weight:700}.cs,.gd{color:#cd0000}.ge{color:#ccc;font-style:italic}.gr{color:red}.gh{color:navy;font-weight:700}.gi{color:#00cd00}.go{color:#888}.gp{color:navy}.gp,.gs{font-weight:700}.gs{color:#ccc}.gu{color:purple;font-weight:700}.gt{color:#04d}.kc{color:#cdcd00}.kd{color:#00cd00}.kn{color:#cd00cd}.kp,.kr{color:#cdcd00}.kt{color:#00cd00}.ld{color:#ccc}.m{color:#cd00cd}.s{color:#cd0000}.na{color:#ccc}.nb{color:#cd00cd}.nc{color:#00cdcd}.nd,.ni,.no{color:#ccc}.ne{color:#669;font-weight:700}.nf,.nl,.nn,.nt,.nx,.py{color:#ccc}.nv{color:#00cdcd}.ow{color:#cdcd00}.w{color:#ccc}.mb,.mf,.mh,.mi,.mo{color:#cd00cd}.s1,.s2,.sb,.sc,.sd,.se,.sh,.si,.sr,.ss,.sx{color:#cd0000}.bp{color:#cd00cd}.vc,.vg,.vi{color:#00cdcd}.il{color:#cd00cd} \ No newline at end of file diff --git a/theme/pygments/vs.css b/theme/pygments/vs.css deleted file mode 100644 index 7fd5bed..0000000 --- a/theme/pygments/vs.css +++ /dev/null @@ -1,35 +0,0 @@ -.highlight { background-color: #ffffcc } -.c { color: #008000 } /* Comment */ -.err { border: 1px solid #FF0000 } /* Error */ -.k { color: #0000ff } /* Keyword */ -.ch { color: #008000 } /* Comment.Hashbang */ -.cm { color: #008000 } /* Comment.Multiline */ -.cp { color: #0000ff } /* Comment.Preproc */ -.cpf { color: #008000 } /* Comment.PreprocFile */ -.c1 { color: #008000 } /* Comment.Single */ -.cs { color: #008000 } /* Comment.Special */ -.ge { font-style: italic } /* Generic.Emph */ -.gh { font-weight: bold } /* Generic.Heading */ -.gp { font-weight: bold } /* Generic.Prompt */ -.gs { font-weight: bold } /* Generic.Strong */ -.gu { font-weight: bold } /* Generic.Subheading */ -.kc { color: #0000ff } /* Keyword.Constant */ -.kd { color: #0000ff } /* Keyword.Declaration */ -.kn { color: #0000ff } /* Keyword.Namespace */ -.kp { color: #0000ff } /* Keyword.Pseudo */ -.kr { color: #0000ff } /* Keyword.Reserved */ -.kt { color: #2b91af } /* Keyword.Type */ -.s { color: #a31515 } /* Literal.String */ -.nc { color: #2b91af } /* Name.Class */ -.ow { color: #0000ff } /* Operator.Word */ -.sb { color: #a31515 } /* Literal.String.Backtick */ -.sc { color: #a31515 } /* Literal.String.Char */ -.sd { color: #a31515 } /* Literal.String.Doc */ -.s2 { color: #a31515 } /* Literal.String.Double */ -.se { color: #a31515 } /* Literal.String.Escape */ -.sh { color: #a31515 } /* Literal.String.Heredoc */ -.si { color: #a31515 } /* Literal.String.Interpol */ -.sx { color: #a31515 } /* Literal.String.Other */ -.sr { color: #a31515 } /* Literal.String.Regex */ -.s1 { color: #a31515 } /* Literal.String.Single */ -.ss { color: #a31515 } /* Literal.String.Symbol */ \ No newline at end of file diff --git a/theme/pygments/vs.min.css b/theme/pygments/vs.min.css deleted file mode 100644 index 4a250ed..0000000 --- a/theme/pygments/vs.min.css +++ /dev/null @@ -1 +0,0 @@ -.highlight{background-color:#ffc}.c{color:green}.err{border:1px solid red}.k{color:#00f}.ch,.cm{color:green}.cp{color:#00f}.c1,.cpf,.cs{color:green}.ge{font-style:italic}.gh,.gp,.gs,.gu{font-weight:700}.kc,.kd,.kn,.kp,.kr{color:#00f}.kt{color:#2b91af}.s{color:#a31515}.nc{color:#2b91af}.ow{color:#00f}.s1,.s2,.sb,.sc,.sd,.se,.sh,.si,.sr,.ss,.sx{color:#a31515} \ No newline at end of file diff --git a/theme/pygments/xcode.css b/theme/pygments/xcode.css deleted file mode 100644 index e45bf95..0000000 --- a/theme/pygments/xcode.css +++ /dev/null @@ -1,58 +0,0 @@ -.highlight { background-color: #ffffcc } -.c { color: #177500 } /* Comment */ -.err { color: #000000 } /* Error */ -.k { color: #A90D91 } /* Keyword */ -.l { color: #1C01CE } /* Literal */ -.n { color: #000000 } /* Name */ -.o { color: #000000 } /* Operator */ -.ch { color: #177500 } /* Comment.Hashbang */ -.cm { color: #177500 } /* Comment.Multiline */ -.cp { color: #633820 } /* Comment.Preproc */ -.cpf { color: #177500 } /* Comment.PreprocFile */ -.c1 { color: #177500 } /* Comment.Single */ -.cs { color: #177500 } /* Comment.Special */ -.kc { color: #A90D91 } /* Keyword.Constant */ -.kd { color: #A90D91 } /* Keyword.Declaration */ -.kn { color: #A90D91 } /* Keyword.Namespace */ -.kp { color: #A90D91 } /* Keyword.Pseudo */ -.kr { color: #A90D91 } /* Keyword.Reserved */ -.kt { color: #A90D91 } /* Keyword.Type */ -.ld { color: #1C01CE } /* Literal.Date */ -.m { color: #1C01CE } /* Literal.Number */ -.s { color: #C41A16 } /* Literal.String */ -.na { color: #836C28 } /* Name.Attribute */ -.nb { color: #A90D91 } /* Name.Builtin */ -.nc { color: #3F6E75 } /* Name.Class */ -.no { color: #000000 } /* Name.Constant */ -.nd { color: #000000 } /* Name.Decorator */ -.ni { color: #000000 } /* Name.Entity */ -.ne { color: #000000 } /* Name.Exception */ -.nf { color: #000000 } /* Name.Function */ -.nl { color: #000000 } /* Name.Label */ -.nn { color: #000000 } /* Name.Namespace */ -.nx { color: #000000 } /* Name.Other */ -.py { color: #000000 } /* Name.Property */ -.nt { color: #000000 } /* Name.Tag */ -.nv { color: #000000 } /* Name.Variable */ -.ow { color: #000000 } /* Operator.Word */ -.mb { color: #1C01CE } /* Literal.Number.Bin */ -.mf { color: #1C01CE } /* Literal.Number.Float */ -.mh { color: #1C01CE } /* Literal.Number.Hex */ -.mi { color: #1C01CE } /* Literal.Number.Integer */ -.mo { color: #1C01CE } /* Literal.Number.Oct */ -.sb { color: #C41A16 } /* Literal.String.Backtick */ -.sc { color: #2300CE } /* Literal.String.Char */ -.sd { color: #C41A16 } /* Literal.String.Doc */ -.s2 { color: #C41A16 } /* Literal.String.Double */ -.se { color: #C41A16 } /* Literal.String.Escape */ -.sh { color: #C41A16 } /* Literal.String.Heredoc */ -.si { color: #C41A16 } /* Literal.String.Interpol */ -.sx { color: #C41A16 } /* Literal.String.Other */ -.sr { color: #C41A16 } /* Literal.String.Regex */ -.s1 { color: #C41A16 } /* Literal.String.Single */ -.ss { color: #C41A16 } /* Literal.String.Symbol */ -.bp { color: #5B269A } /* Name.Builtin.Pseudo */ -.vc { color: #000000 } /* Name.Variable.Class */ -.vg { color: #000000 } /* Name.Variable.Global */ -.vi { color: #000000 } /* Name.Variable.Instance */ -.il { color: #1C01CE } /* Literal.Number.Integer.Long */ \ No newline at end of file diff --git a/theme/pygments/xcode.min.css b/theme/pygments/xcode.min.css deleted file mode 100644 index a9cbbc3..0000000 --- a/theme/pygments/xcode.min.css +++ /dev/null @@ -1 +0,0 @@ -.highlight{background-color:#ffc}.c{color:#177500}.err{color:#000}.k{color:#a90d91}.l{color:#1c01ce}.n,.o{color:#000}.ch,.cm{color:#177500}.cp{color:#633820}.c1,.cpf,.cs{color:#177500}.kc,.kd,.kn,.kp,.kr,.kt{color:#a90d91}.ld,.m{color:#1c01ce}.s{color:#c41a16}.na{color:#836c28}.nb{color:#a90d91}.nc{color:#3f6e75}.nd,.ne,.nf,.ni,.nl,.nn,.no,.nt,.nv,.nx,.ow,.py{color:#000}.mb,.mf,.mh,.mi,.mo{color:#1c01ce}.sb{color:#c41a16}.sc{color:#2300ce}.s1,.s2,.sd,.se,.sh,.si,.sr,.ss,.sx{color:#c41a16}.bp{color:#5b269a}.vc,.vg,.vi{color:#000}.il{color:#1c01ce} \ No newline at end of file diff --git a/theme/stylesheet/style.less b/theme/stylesheet/style.less deleted file mode 100644 index 044599f..0000000 --- a/theme/stylesheet/style.less +++ /dev/null @@ -1,528 +0,0 @@ -@import "variables.less"; - -html, body { - width: 100%; - height: 100%; -} - -h1, -h2, -h3, -h4, -h5, -h6 { - font-weight: 300; - line-height: 1.1; -} - -h1{ - font-size: 2.4em -} - -h2 { - font-size: 2em -} - -h3 { - font-size: 1.6em -} - -h4 { - font-size: 1.36em -} - -h5 { - font-size: 1.2em -} - -h6 { - font-size: 1.1em -} - -body { - margin: 0; - padding: 0; - background-color: @body-bg; - color: @text-color; - font-family: @sans; - font-size: 1.02em; - line-height: 1.2em; -} - -a { - color: @link-color; - text-decoration: none; -} - -a:hover { - color: @link-hover-color; -} - -hr { - color: @light-grey; - background-color: @light-grey; - height: 1px; - border: none; - margin-top: 40px; - margin-bottom: 40px; -} - -img { - max-width: 100%; -} - -aside { - background-color: @sidebar-bg; - color: @sidebar-text-color; - text-align: center; - - a { - color: @sidebar-link-color; - } - - a:hover { - color: @sidebar-link-hover-color; - } - - div { - padding: 20px; - margin: 0; - - img { - border-radius: 50%; - max-width: 140px; - } - - h1 { - margin: 15px 0 5px 0; - } - - p { - margin: 0 0 15px 0; - font-size: .92em; - } - } - - nav { - ul { - li { - display: inline; - line-height: 1.6em; - font-size: 1.28em; - text-transform: lowercase; - } - } - } -} - -main { - nav { - text-align: center; - text-transform: uppercase; - font-size: .72em; - padding: 14px 0 14px 0; - border-bottom: @nav-border-color 1px solid; - } - - nav, .translations { - a { - padding: 0 4px 0 4px; - border-left: @nav-border-color 1px solid; - border-right: @nav-border-color 1px solid; - } - - :first-child { - border-left: none; - } - - :last-child { - border-right: none; - } - } - - .neighbors { - margin: 4% 0% 4% 0%; - height: 20px; - } - - .pagination { - margin: 4% 8% 4% 8%; - height: 20px; - } - - .social-share { - p { - font-size: .8em; - } - } - - article { - margin: 0 8% 2% 8%; - - header { - h1, h2 { - margin-bottom: 0; - } - - p { - color: @header-text-color; - font-size: 0.86em; - } - - .translations { - float: right; - - .active { - font-weight: 600; - } - } - } - - code, kbd, samp, pre { - font-family: @mono; - } - - blockquote, pre { - background-color: rgba(128,128,128,0.05); - border-top-right-radius: 5px; - border-bottom-right-radius: 5px; - border-left: 8px solid rgba(128,128,128,0.075); - border-left-width: 10px; - } - - blockquote { - padding: 10px 20px; - font-weight: 300; - font-size: 1.1em; - } - - pre { - padding: 4px; - font-size: .9em; - overflow-x: auto; - } - - samp { - white-space: pre; - display: block; - overflow-x: auto; - } - - kbd { - padding: .1em .6em; - border: 1px solid rgba(63,63,63,0.25); - box-shadow: 0 1px 0 rgba(63,63,63,0.25); - background-color: #fff; - color: #333; - border-radius: 3px; - display: inline-block; - margin: 0 .1em; - white-space: nowrap; - font-size: .78em; - } - - code { - font-size: .8em; - white-space: nowrap; - color: #c25; - padding: 1px 3px; - background-color: #f7f7f9; - border: 1px solid #e1e1e8; - border-radius: 3px; - } - - .comment-count { - font-size: .8em; - } - - table { - border-collapse: collapse; - border-spacing: 0; - - thead:first-child tr:first-child th { - border-top: 0; - } - - th, td { - padding: 8px; - line-height: 20px; - vertical-align: top; - border-top: 1px solid #ddd; - } - } - } - - footer { - padding-top: 4px; - border-top: @footer-border-color 1px solid; - - p { - margin: 2px; - text-align: center; - padding: 0 40px 0 40px; - color: @footer-text-color; - font-size: 11px; - } - } -} - -.tag-cloud { - a { - background-color: @tag-bg; - padding: .2em .6em .2em; - font-size: .74em; - line-height: 1; - color: @tag-text-color; - text-align: center; - white-space: nowrap; - vertical-align: baseline; - border-radius: .25em; - } - - a:hover { - background-color: @tag-hover-color; - } -} - -a.btn { - background-color: @btn-bg; - padding: .6em .6em; - font-size: .8em; - line-height: 1; - color: @btn-text-color; - text-align: center; - white-space: nowrap; - vertical-align: baseline; - border-radius: .25em; -} - -a.btn:hover { - background-color: @btn-hover-color; -} - -.center, .text-center { - text-align: center; -} - -.img-center { - margin-left: auto; - margin-right: auto; - display: block; -} - -.align-center { - margin-left: auto; - margin-right: auto; - display: block; -} - -.float-left { - float: left; -} - -.float-right { - float: right; -} - -div.related-posts { - margin: 15px 0 15px 0; - padding-bottom: 20px; - border-top: @rel-post-border-color 1px solid; - border-bottom: @rel-post-border-color 1px solid; - - h4 { - margin: 20px 0 25px 0; - } - - ul { - font-size: 1.1em; - padding-left: 12px; - - li { - padding: 4px 0 4px 0; - } - } -} - -ul.list, ul.social, ul.related-posts { - list-style-type: none; - margin: 0; - padding: 0; -} - -ul.list { - padding: 1em 0 1em 0; - - li { - padding: 4px; - } -} - -ul.social { - font-size: 1.6em; - padding-top: 20px; - - li { - display: inline; - } - - a:hover { - z-index: 2; - -webkit-transform: translateY(-5px); - transform: translateY(-5px); - } - - a { - display: inline-block; - width: 36px; - height: 36px; - border-radius: 100%; - text-align: center; - font-size: .8em; - line-height: 36px; - } - - a.sc-facebook { - background-color: @facebook-bg-color; - } - - a.sc-google { - background-color: @google-bg-color; - } - - a.sc-instagram { - background-color: @instagram-bg-color; - } - - a.sc-pinterest { - background-color: @pinterest-bg-color; - } - - a.sc-linkedin { - background-color: @linkedin-bg-color; - } - - a.sc-medium { - background-color: @medium-bg-color; - } - - a.sc-rss { - background-color: @rss-bg-color; - } - - a.sc-stack-overflow { - background-color: @stack-overflow-bg-color; - } - - a.sc-tumblr { - background-color: @tumblr-bg-color; - } - - a.sc-twitter { - background-color: @twitter-bg-color; - } - - a.sc-youtube { - background-color: @youtube-bg-color; - } - - a.sc-github, a.sc-github-alt { - background-color: @github-bg-color; - } - - a.sc-envelope-o { - background-color: @email-bg-color; - } - - a.sc-reddit { - background-color: @reddit-bg-color; - } - - a.sc-soundcloud { - background-color: @soundcloud-bg-color; - } - - a.sc-gitlab { - background-color: @gitlab-bg-color; - } - - a.sc-xing { - background-color: @xing-bg-color; - } - -} - -.ads-aside { - display: inline-block; - height: 90px; - width: 70%; -} - -.ads-responsive { - display: inline-block; - margin: 6px 0 6px 0; - width: 90%; - height: 70px; - margin-left: 5%; -} - -// -// Desktop -// - -@media screen and (min-width: 768px) { - aside { - width: 25%; - height: 100%; - position: fixed; - top: 0; - left: 0; - overflow-y: auto; - - div { - padding: 36px 18px; - - nav { - ul { - li { - padding: 0 !important; - display: block; - } - } - } - - ul.social { - padding-top: 32px; - } - } - } - - main { - width: 75%; - height: 100%; - position: absolute; - top: 0; - left: 25%; - - article { - - &.single { - min-height: 80%; - } - - ul.list { - li { - padding: 2px; - } - } - } - } - - .ads-aside { - height: 250px; - } - - .ads-responsive { - height: 90px; - } -} diff --git a/theme/stylesheet/style.min.css b/theme/stylesheet/style.min.css deleted file mode 100644 index 632fb98..0000000 --- a/theme/stylesheet/style.min.css +++ /dev/null @@ -1 +0,0 @@ -body,html{width:100%;height:100%}h1,h2,h3,h4,h5,h6{font-weight:300;line-height:1.1}h1{font-size:2.4em}h2{font-size:2em}h3{font-size:1.6em}h4{font-size:1.36em}h5{font-size:1.2em}h6{font-size:1.1em}body{margin:0;padding:0;background-color:#fff;color:#242121;font-family:Source Sans Pro,Verdana,sans-serif;font-size:1.02em;line-height:1.2em}a{color:#d9411e;text-decoration:none}a:hover{color:#ff5a09}hr{color:#eee;background-color:#eee;height:1px;border:none;margin-top:40px;margin-bottom:40px}img{max-width:100%}aside{background-color:#333;text-align:center}aside,aside a{color:#fff}aside a:hover{color:#eee}aside div{padding:20px;margin:0}aside div img{border-radius:50%;max-width:140px}aside div h1{margin:15px 0 5px}aside div p{margin:0 0 15px;font-size:.92em}aside nav ul li{display:inline;line-height:1.6em;font-size:1.28em;text-transform:lowercase}main nav{text-align:center;text-transform:uppercase;font-size:.72em;padding:14px 0;border-bottom:1px solid #eee}main .translations a,main nav a{padding:0 4px;border-left:1px solid #eee;border-right:1px solid #eee}main .translations :first-child,main nav :first-child{border-left:none}main .translations :last-child,main nav :last-child{border-right:none}main .neighbors{margin:4% 0;height:20px}main .pagination{margin:4% 8%;height:20px}main .social-share p{font-size:.8em}main article{margin:0 8% 2%}main article header h1,main article header h2{margin-bottom:0}main article header p{color:#999;font-size:.86em}main article header .translations{float:right}main article header .translations .active{font-weight:600}main article code,main article kbd,main article pre,main article samp{font-family:Source Code Pro,Consolas,monospace}main article blockquote,main article pre{background-color:hsla(0,0%,50%,.05);border-top-right-radius:5px;border-bottom-right-radius:5px;border-left:8px solid hsla(0,0%,50%,.075);border-left-width:10px}main article blockquote{padding:10px 20px;font-weight:300;font-size:1.1em}main article pre{padding:4px;font-size:.9em;overflow-x:auto}main article samp{white-space:pre;display:block;overflow-x:auto}main article kbd{padding:.1em .6em;border:1px solid rgba(63,63,63,.25);box-shadow:0 1px 0 rgba(63,63,63,.25);background-color:#fff;color:#333;border-radius:3px;display:inline-block;margin:0 .1em;white-space:nowrap;font-size:.78em}main article code{font-size:.8em;white-space:nowrap;color:#c25;padding:1px 3px;background-color:#f7f7f9;border:1px solid #e1e1e8;border-radius:3px}main article .comment-count{font-size:.8em}main article table{border-collapse:collapse;border-spacing:0}main article table thead:first-child tr:first-child th{border-top:0}main article table td,main article table th{padding:8px;line-height:20px;vertical-align:top;border-top:1px solid #ddd}main footer{padding-top:4px;border-top:1px solid #eee}main footer p{margin:2px;text-align:center;padding:0 40px;color:#999;font-size:11px}.tag-cloud a{background-color:#d9411e;padding:.2em .6em;font-size:.74em;line-height:1;color:#fff;text-align:center;white-space:nowrap;vertical-align:baseline;border-radius:.25em}.tag-cloud a:hover{background-color:#ff5a09}a.btn{background-color:#d9411e;padding:.6em;font-size:.8em;line-height:1;color:#fff;text-align:center;white-space:nowrap;vertical-align:baseline;border-radius:.25em}a.btn:hover{background-color:#ff5a09}.center,.text-center{text-align:center}.align-center,.img-center{margin-left:auto;margin-right:auto;display:block}.float-left{float:left}.float-right{float:right}div.related-posts{margin:15px 0;padding-bottom:20px;border-top:1px solid #eee;border-bottom:1px solid #eee}div.related-posts h4{margin:20px 0 25px}div.related-posts ul{font-size:1.1em;padding-left:12px}div.related-posts ul li{padding:4px 0}ul.list,ul.related-posts,ul.social{list-style-type:none;margin:0;padding:0}ul.list{padding:1em 0}ul.list li{padding:4px}ul.social{font-size:1.6em;padding-top:20px}ul.social li{display:inline}ul.social a:hover{z-index:1;-webkit-transform:translateY(-5px);transform:translateY(-5px)}ul.social a{display:inline-block;width:36px;height:36px;border-radius:100%;text-align:center;font-size:.8em;line-height:36px}ul.social a.sc-facebook{background-color:#3e5b98}ul.social a.sc-google{background-color:#d93e2d}ul.social a.sc-instagram{background-color:#125688}ul.social a.sc-pinterest{background-color:#c92619}ul.social a.sc-linkedin{background-color:#3371b7}ul.social a.sc-medium{background-color:#00ab6b}ul.social a.sc-rss{background-color:#f26109}ul.social a.sc-stack-overflow{background-color:#f90}ul.social a.sc-tumblr{background-color:#36465d}ul.social a.sc-twitter{background-color:#4da7de}ul.social a.sc-youtube{background-color:#e02a20}ul.social a.sc-github,ul.social a.sc-github-alt{background-color:#111010}ul.social a.sc-envelope-o{background-color:#578ad6}ul.social a.sc-reddit{background-color:#ff4500}ul.social a.sc-soundcloud{background-color:#f50}ul.social a.sc-gitlab{background-color:#fca326}ul.social a.sc-xing{background-color:#007575}.ads-aside{display:inline-block;height:90px;width:70%}.ads-responsive{display:inline-block;margin:6px 0;width:90%;height:70px;margin-left:5%}@media screen and (min-width:768px){aside{width:25%;height:100%;position:fixed;top:0;left:0;overflow-y:auto}aside div{padding:36px 18px}aside div nav ul li{padding:0!important;display:block}aside div ul.social{padding-top:32px}main{width:75%;height:100%;position:absolute;top:0;left:25%}main article.single{min-height:80%}main article ul.list li{padding:2px}.ads-aside{height:250px}.ads-responsive{height:90px}} \ No newline at end of file diff --git a/theme/stylesheet/variables.less b/theme/stylesheet/variables.less deleted file mode 100644 index fa00ffa..0000000 --- a/theme/stylesheet/variables.less +++ /dev/null @@ -1,69 +0,0 @@ -// Flex colors -@orange: #D9411E; -@light-orange: #FF5A09; -@white: #ffffff; -@grey: #333333; -@light-grey: #eeeeee; -@med-grey: #999999; -@dark-grey: #242121; - -// Font family -@sans: 'Source Sans Pro', 'Verdana', sans-serif; -@mono: 'Source Code Pro', 'Consolas', monospace; - -// Body -@body-bg: @white; -@text-color: @dark-grey; - -// Links -@link-color: @orange; -@link-hover-color: @light-orange; - -// Sidebar (aside) -@sidebar-bg: @grey; -@sidebar-text-color: @white; -@sidebar-link-color: @white; -@sidebar-link-hover-color: @light-grey; - -// Buttons -@btn-bg: @orange; -@btn-text-color: @white; -@btn-hover-color: @light-orange; - -// Tag cloud -@tag-bg: @orange; -@tag-text-color: @white; -@tag-hover-color: @light-orange; - -// Header -@header-text-color: @med-grey; - -// Footer -@footer-text-color: @med-grey; -@footer-border-color: @light-grey; - -// Relativer posts -@rel-post-border-color: @light-grey; - -// Nav -@nav-border-color: @light-grey; - -// Social buttons - -@email-bg-color: #578ad6; -@facebook-bg-color: #3e5b98; -@github-bg-color: #111010; -@google-bg-color: #d93e2d; -@instagram-bg-color: #125688; -@linkedin-bg-color: #3371b7; -@medium-bg-color: #00ab6b; -@pinterest-bg-color: #c92619; -@reddit-bg-color: #ff4500; -@rss-bg-color: #f26109; -@soundcloud-bg-color: #ff5500; -@stack-overflow-bg-color: #ff9900; -@tumblr-bg-color: #36465d; -@twitter-bg-color: #4da7de; -@youtube-bg-color: #e02a20; -@gitlab-bg-color: #fca326; -@xing-bg-color: #007575; diff --git a/tools/get-minutes b/tools/get-minutes new file mode 100755 index 0000000..a58d392 --- /dev/null +++ b/tools/get-minutes @@ -0,0 +1,93 @@ +#!/usr/bin/python3 +"""Convert meetingology meeting minutes for publishing.""" + +from argparse import ArgumentParser +import re +from subprocess import check_call, CalledProcessError +import sys + +HEADER = '''\ +Title: Cloud-init bi-weekly status +Date: {date} {time} +Category: status-meeting-minutes +Slug: status-{date} + +''' + + +def get_parser(): + parser = ArgumentParser(description=__doc__) + parser.add_argument( + 'url', type=str, + help='URL of meetingology moinmoin formatted text minutes to publish') + return parser + + + +def error(message): + print(message) + sys.exit(1) + + +MINUTES_REGEX = ( + r'cloud-init\.(?P[\d]+-[\d]+-[\d]+)-(?P