From 96c9fa3e420c3f15a51c92202d88665e1d2fc721 Mon Sep 17 00:00:00 2001 From: Chad Smith Date: Fri, 8 Sep 2017 03:05:45 +0000 Subject: [PATCH 01/77] initial pelican site creation for cloud-init info --- .gitignore | 3 + Flex | 1 + Makefile | 124 +++++++++++++++++++++++++++++++++++ content/details.md | 8 +++ content/status-2017-09-05.md | 60 +++++++++++++++++ develop_server.sh | 103 +++++++++++++++++++++++++++++ fabfile.py | 92 ++++++++++++++++++++++++++ pelican-plugins | 1 + pelicanconf.py | 63 ++++++++++++++++++ publishconf.py | 24 +++++++ 10 files changed, 479 insertions(+) create mode 100644 .gitignore create mode 160000 Flex create mode 100644 Makefile create mode 100644 content/details.md create mode 100644 content/status-2017-09-05.md create mode 100755 develop_server.sh create mode 100644 fabfile.py create mode 160000 pelican-plugins create mode 100644 pelicanconf.py create mode 100644 publishconf.py 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..0091474 --- /dev/null +++ b/Flex @@ -0,0 +1 @@ +Subproject commit 0091474a91e7a691ec489bc05cf4884a2a8fb77e diff --git a/Makefile b/Makefile new file mode 100644 index 0000000..0513c2e --- /dev/null +++ b/Makefile @@ -0,0 +1,124 @@ +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) + +.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/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/content/status-2017-09-05.md b/content/status-2017-09-05.md new file mode 100644 index 0000000..697fcb9 --- /dev/null +++ b/content/status-2017-09-05.md @@ -0,0 +1,60 @@ +Title: Cloud-init status meeting +Date: 2017-09-05 16:30:00 +Category: status-update +Slug: status-1 + +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 +-------- + 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/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..074d94d --- /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 + '/theme/images/logo2.png' +FAVICON = SITEURL + '/theme/images/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..cd0bb8b --- /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 = "" From 0d11f6473228f7e7496ed9d2e3b139df4a7fcd37 Mon Sep 17 00:00:00 2001 From: Chad Smith Date: Fri, 8 Sep 2017 03:44:34 +0000 Subject: [PATCH 02/77] update Flex profile.png logo --- Flex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Flex b/Flex index 0091474..25ff099 160000 --- a/Flex +++ b/Flex @@ -1 +1 @@ -Subproject commit 0091474a91e7a691ec489bc05cf4884a2a8fb77e +Subproject commit 25ff099b73d7d242149a63d26de4e726420a2188 From d02cda7a798284af06642bb5a9f96e4ede6cee75 Mon Sep 17 00:00:00 2001 From: Chad Smith Date: Fri, 8 Sep 2017 03:46:32 +0000 Subject: [PATCH 03/77] update gh-pages publish for cloud-init --- Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Makefile b/Makefile index 0513c2e..9825e72 100644 --- a/Makefile +++ b/Makefile @@ -119,6 +119,6 @@ cf_upload: publish github: publish ghp-import -m "Generate Pelican site" -b $(GITHUB_PAGES_BRANCH) $(OUTPUTDIR) - git push origin $(GITHUB_PAGES_BRANCH) + git push origin $(GITHUB_PAGES_BRANCH):master .PHONY: html help clean regenerate serve serve-global devserver stopserver publish ssh_upload rsync_upload dropbox_upload ftp_upload s3_upload cf_upload github From 71aaa061340de11cec94e54d957b8b7cf9ee6986 Mon Sep 17 00:00:00 2001 From: Chad Smith Date: Fri, 8 Sep 2017 03:48:38 +0000 Subject: [PATCH 04/77] update profile.png reference in pelicanconf.py --- pelicanconf.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pelicanconf.py b/pelicanconf.py index 074d94d..ef5d96b 100644 --- a/pelicanconf.py +++ b/pelicanconf.py @@ -10,7 +10,7 @@ SITETITLE = 'Cloud-init' SITESUBTITLE = 'Make your cloud images be all they can be' SITEDESCRIPTION = 'Cloud-init project updates and general information' -SITELOGO = SITEURL + '/theme/images/logo2.png' +SITELOGO = SITEURL + '/theme/images/profile.png' FAVICON = SITEURL + '/theme/images/favicon.ico' USE_FOLDER_AS_CATEGORY = False From c1597743a1781a9a026c3c30a8cf92b550239f6f Mon Sep 17 00:00:00 2001 From: Chad Smith Date: Fri, 8 Sep 2017 03:52:02 +0000 Subject: [PATCH 05/77] update profile.png reference in pelicanconf.py --- Flex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Flex b/Flex index 25ff099..3b1abc6 160000 --- a/Flex +++ b/Flex @@ -1 +1 @@ -Subproject commit 25ff099b73d7d242149a63d26de4e726420a2188 +Subproject commit 3b1abc6adb2161e65eda90b4d97f3d81b4d006cc From 2c26ba527fa9d5e7a465a4d414edcc7a0ccee0a5 Mon Sep 17 00:00:00 2001 From: Chad Smith Date: Fri, 8 Sep 2017 03:53:15 +0000 Subject: [PATCH 06/77] github publish --force --- Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Makefile b/Makefile index 9825e72..02bc43c 100644 --- a/Makefile +++ b/Makefile @@ -119,6 +119,6 @@ cf_upload: publish github: publish ghp-import -m "Generate Pelican site" -b $(GITHUB_PAGES_BRANCH) $(OUTPUTDIR) - git push origin $(GITHUB_PAGES_BRANCH):master + git push origin $(GITHUB_PAGES_BRANCH):master --force .PHONY: html help clean regenerate serve serve-global devserver stopserver publish ssh_upload rsync_upload dropbox_upload ftp_upload s3_upload cf_upload github From 6dc0c8d8b2ebd814c72d54afd18a59d279ce401f Mon Sep 17 00:00:00 2001 From: Chad Smith Date: Fri, 8 Sep 2017 03:55:35 +0000 Subject: [PATCH 07/77] update profile.png reference in pelicanconf.py --- pelicanconf.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pelicanconf.py b/pelicanconf.py index ef5d96b..b4e7459 100644 --- a/pelicanconf.py +++ b/pelicanconf.py @@ -10,8 +10,8 @@ SITETITLE = 'Cloud-init' SITESUBTITLE = 'Make your cloud images be all they can be' SITEDESCRIPTION = 'Cloud-init project updates and general information' -SITELOGO = SITEURL + '/theme/images/profile.png' -FAVICON = SITEURL + '/theme/images/favicon.ico' +SITELOGO = SITEURL + '/theme/img/profile.png' +FAVICON = SITEURL + '/theme/img/favicon.ico' USE_FOLDER_AS_CATEGORY = False MAIN_MENU = True From eec7fd007072499711485cde9953774012718ff5 Mon Sep 17 00:00:00 2001 From: Chad Smith Date: Fri, 8 Sep 2017 04:01:15 +0000 Subject: [PATCH 08/77] update category and titles for status meeting pages --- content/status-2017-09-05.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/status-2017-09-05.md b/content/status-2017-09-05.md index 697fcb9..6e011e0 100644 --- a/content/status-2017-09-05.md +++ b/content/status-2017-09-05.md @@ -1,6 +1,6 @@ -Title: Cloud-init status meeting +Title: Cloud-init bi-weekly status Date: 2017-09-05 16:30:00 -Category: status-update +Category: status-meeting-minutes Slug: status-1 Meeting information From cf127e5449618b03dbd84ef3306ed1d9efda9890 Mon Sep 17 00:00:00 2001 From: Chad Smith Date: Fri, 8 Sep 2017 04:02:31 +0000 Subject: [PATCH 09/77] update github make target to push source too --- Makefile | 1 + 1 file changed, 1 insertion(+) diff --git a/Makefile b/Makefile index 02bc43c..ac6f866 100644 --- a/Makefile +++ b/Makefile @@ -120,5 +120,6 @@ cf_upload: publish github: publish ghp-import -m "Generate Pelican site" -b $(GITHUB_PAGES_BRANCH) $(OUTPUTDIR) git push origin $(GITHUB_PAGES_BRANCH):master --force + git push origin master: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 From a71160a3db9b74a898cdb0e9d23a17c9b8e7179a Mon Sep 17 00:00:00 2001 From: Chad Smith Date: Fri, 8 Sep 2017 22:04:27 +0000 Subject: [PATCH 10/77] add link to IRC logs for the last meeting since meetingology wasn't yet there --- content/status-2017-09-05.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/status-2017-09-05.md b/content/status-2017-09-05.md index 6e011e0..ac67278 100644 --- a/content/status-2017-09-05.md +++ b/content/status-2017-09-05.md @@ -58,3 +58,5 @@ People present (lines said) Full Log -------- +*LINK:* + From 175d82abe187120167c72199024745d19498dd01 Mon Sep 17 00:00:00 2001 From: Chad Smith Date: Tue, 19 Sep 2017 19:01:28 +0000 Subject: [PATCH 11/77] added content from weekly status meeting --- content/status-2017-09-05.md | 2 +- content/status-2017-09-18.md | 192 +++++++++++++++++++++++++++++++++++ 2 files changed, 193 insertions(+), 1 deletion(-) create mode 100644 content/status-2017-09-18.md diff --git a/content/status-2017-09-05.md b/content/status-2017-09-05.md index ac67278..9bc87e8 100644 --- a/content/status-2017-09-05.md +++ b/content/status-2017-09-05.md @@ -1,5 +1,5 @@ Title: Cloud-init bi-weekly status -Date: 2017-09-05 16:30:00 +Date: 2017-09-05 16:30:00 Category: status-meeting-minutes Slug: status-1 diff --git a/content/status-2017-09-18.md b/content/status-2017-09-18.md new file mode 100644 index 0000000..178c62a --- /dev/null +++ b/content/status-2017-09-18.md @@ -0,0 +1,192 @@ +Title: Cloud-init bi-weekly status +Date: 2017-09-18 16:30:00 UTC +Category: status-meeting-minutes +Slug: status-3 + +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 "wikilink") + +Meeting summary +--------------- + +* *LINK:* +* *LINK:* + +### 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 +-------- +*LINK:* + +`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  #linkhttps://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) From 08aa0bd2fd4b8dd7da13269d93881b0556dfd87c Mon Sep 17 00:00:00 2001 From: Chad Smith Date: Tue, 19 Sep 2017 19:03:38 +0000 Subject: [PATCH 12/77] update slugs on status reports --- content/status-2017-09-05.md | 2 +- content/status-2017-09-18.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/status-2017-09-05.md b/content/status-2017-09-05.md index 9bc87e8..858b471 100644 --- a/content/status-2017-09-05.md +++ b/content/status-2017-09-05.md @@ -1,7 +1,7 @@ Title: Cloud-init bi-weekly status Date: 2017-09-05 16:30:00 Category: status-meeting-minutes -Slug: status-1 +Slug: status-2017-09-05 Meeting information ------------------- diff --git a/content/status-2017-09-18.md b/content/status-2017-09-18.md index 178c62a..12e3f6d 100644 --- a/content/status-2017-09-18.md +++ b/content/status-2017-09-18.md @@ -1,7 +1,7 @@ Title: Cloud-init bi-weekly status Date: 2017-09-18 16:30:00 UTC Category: status-meeting-minutes -Slug: status-3 +Slug: status-2017-09-18 Meeting information ------------------- From 5b2f04c18d8c10f4ee8f497154a760d8010be1df Mon Sep 17 00:00:00 2001 From: Chad Smith Date: Wed, 20 Sep 2017 01:46:35 +0000 Subject: [PATCH 13/77] add analytics --- publishconf.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/publishconf.py b/publishconf.py index cd0bb8b..208e909 100644 --- a/publishconf.py +++ b/publishconf.py @@ -21,4 +21,4 @@ # Following items are often useful when publishing #DISQUS_SITENAME = "" -#GOOGLE_ANALYTICS = "" +GOOGLE_ANALYTICS = "UA-50554247-3" From fe4420f7d579a704ead0b3b6a46a9999894c4e38 Mon Sep 17 00:00:00 2001 From: Chad Smith Date: Wed, 18 Oct 2017 03:06:22 +0000 Subject: [PATCH 14/77] add bi-weekly status logs for cloud-init --- Flex | 2 +- content/status-2017-10-02.md | 471 +++++++++++++++++++++++++++++++++++ content/status-2017-10-16.md | 179 +++++++++++++ 3 files changed, 651 insertions(+), 1 deletion(-) create mode 100644 content/status-2017-10-02.md create mode 100644 content/status-2017-10-16.md diff --git a/Flex b/Flex index 3b1abc6..229ad20 160000 --- a/Flex +++ b/Flex @@ -1 +1 @@ -Subproject commit 3b1abc6adb2161e65eda90b4d97f3d81b4d006cc +Subproject commit 229ad20d36f093d8a6d4526aa67d22d34812ee02 diff --git a/content/status-2017-10-02.md b/content/status-2017-10-02.md new file mode 100644 index 0000000..1f8b7bb --- /dev/null +++ b/content/status-2017-10-02.md @@ -0,0 +1,471 @@ +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 "wikilink") + +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) diff --git a/content/status-2017-10-16.md b/content/status-2017-10-16.md new file mode 100644 index 0000000..0f0c8ce --- /dev/null +++ b/content/status-2017-10-16.md @@ -0,0 +1,179 @@ +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 "wikilink") + +Meeting summary +--------------- + +*LINK:* *LINK:* + +*LINK:* + +*LINK:* + +*LINK:* + +*LINK:* *LINK:* + 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 `` #meetingtopic 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 `` #meetingtopic 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/#file-lxc-pstart-md`](https://gist.github.com/smoser/49444542158f2e5f88f1/#file-lxc-pstart-md) + +`16:20 `` sweet` + +`16:20 `` #link `[`https://gist.github.com/smoser/49444542158f2e5f88f1/#file-lxc-pstart-md`](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 `` #meetingtopic 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) From 20b69abcdf8586a3a67c2cafaec4bdf6c3ce8366 Mon Sep 17 00:00:00 2001 From: root Date: Tue, 31 Oct 2017 16:56:16 +0000 Subject: [PATCH 15/77] Sync meeting minutes --- content/status-2017-10-02.md | 471 +++++++++++++++++++++++++++++++++++ content/status-2017-10-16.md | 179 +++++++++++++ 2 files changed, 650 insertions(+) create mode 100644 content/status-2017-10-02.md create mode 100644 content/status-2017-10-16.md diff --git a/content/status-2017-10-02.md b/content/status-2017-10-02.md new file mode 100644 index 0000000..1f8b7bb --- /dev/null +++ b/content/status-2017-10-02.md @@ -0,0 +1,471 @@ +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 "wikilink") + +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) diff --git a/content/status-2017-10-16.md b/content/status-2017-10-16.md new file mode 100644 index 0000000..0f0c8ce --- /dev/null +++ b/content/status-2017-10-16.md @@ -0,0 +1,179 @@ +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 "wikilink") + +Meeting summary +--------------- + +*LINK:* *LINK:* + +*LINK:* + +*LINK:* + +*LINK:* + +*LINK:* *LINK:* + 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 `` #meetingtopic 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 `` #meetingtopic 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/#file-lxc-pstart-md`](https://gist.github.com/smoser/49444542158f2e5f88f1/#file-lxc-pstart-md) + +`16:20 `` sweet` + +`16:20 `` #link `[`https://gist.github.com/smoser/49444542158f2e5f88f1/#file-lxc-pstart-md`](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 `` #meetingtopic 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) From f0b226b03140109f90ddad865f05c0a12edd4637 Mon Sep 17 00:00:00 2001 From: Chad Smith Date: Wed, 1 Nov 2017 04:34:49 +0000 Subject: [PATCH 16/77] add meeting minutes 10-30. Add tools/get-minutes to do this conversion for us using pandoc --- content/status-2017-10-30.md | 237 +++++++++++++++++++++++++++++++++++ tools/get-minutes | 71 +++++++++++ 2 files changed, 308 insertions(+) create mode 100644 content/status-2017-10-30.md create mode 100755 tools/get-minutes diff --git a/content/status-2017-10-30.md b/content/status-2017-10-30.md new file mode 100644 index 0000000..db90662 --- /dev/null +++ b/content/status-2017-10-30.md @@ -0,0 +1,237 @@ +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 "wikilink") + +Meeting summary +--------------- + +*LINK:* + +*LINK:* *LINK:* + + +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 `` #meetingtopic 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 meetingtopic for the above ... that should have been the following` + +`16:16 `` #meetingtopic 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 `` #meetingtopic 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) diff --git a/tools/get-minutes b/tools/get-minutes new file mode 100755 index 0000000..5ee1f59 --- /dev/null +++ b/tools/get-minutes @@ -0,0 +1,71 @@ +#!/usr/bin/python3 +"""Convert meetingology meeting minutes for publishing.""" + +from argparse import ArgumentParser +import re +from subprocess import check_call, check_output, 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