/srv/irclogs.ubuntu.com/2017/03/14/#ubuntu-meeting-2.txt

* slangasek waves17:00
* infinity grunts17:00
mdeslaurhi17:00
slangasekhello17:01
mdeslaursorry for not updating the agenda17:01
slangasek#startmeeting17:01
meetingologyMeeting started Tue Mar 14 17:01:17 2017 UTC.  The chair is slangasek. Information about MeetBot at http://wiki.ubuntu.com/meetingology.17:01
meetingologyAvailable commands: action commands idea info link nick17:01
slangasek:-)17:01
slangasek[TOPIC] Apologies17:01
slangaseknone received on the mailing list17:01
slangasekkees: are you here?17:02
slangasekwe have mdeslaur infinity slangasek; no sign of stgraber on channel17:02
slangasek[TOPIC] Action review17:03
slangasekACTION: infinity to follow up with maas SRU exception17:03
slangasekinfinity: any news there?17:03
infinityNo news is good news?17:03
infinityThat's a thing, right?17:03
slangasekwell, that hardly stops the maas SRUs from coming in :)17:03
mdeslaurheh17:03
slangasekif you haven't made progress I'd like to suggest a path forward?17:03
infinityI need to make some time to go back to what is and isn't documented and JFDI.  Said time has not been made.17:04
slangasekI've recently started forcing people who are asking for SRU exceptions to do the work of preparing a wiki page like https://wiki.ubuntu.com/CurtinUpdates17:04
slangasekand then once it's approved by a member of the SRU team, we update the main wiki page with a link to it17:05
slangasekthis puts the burden on the team that is asking for the SRU, which might work better than having you responsible for it17:05
infinityThat sounds not unreasonable.17:05
slangasekinfinity: would you follow up with the maas team and tell them to do this?17:05
infinity*nod*17:05
slangasek[ACTION] infinity to ask maas team to prepare SRU exception policy à la https://wiki.ubuntu.com/CurtinUpdates17:06
meetingologyACTION: infinity to ask maas team to prepare SRU exception policy à la https://wiki.ubuntu.com/CurtinUpdates17:06
slangasekcool, next17:06
slangasekACTION: infinity to play with seed/maint-check changes on dogfood to build a new xenial release pocket for support length auditing (ETA: 16.04.2 release)17:06
slangasekI guess this didn't happen before 16.04.2 :)17:06
infinityThat ETA is clearly a lie now.  But another short deferral.17:06
infinityThis also dovetails into your email about custom kernel support that I need to reply angrily to.17:06
slangasekhmm :)17:07
slangasekok17:07
slangasek[ACTION] infinity to play with seed/maint-check changes on dogfood to build a new xenial release pocket for support length auditing17:07
meetingologyACTION: infinity to play with seed/maint-check changes on dogfood to build a new xenial release pocket for support length auditing17:07
slangasekACTION: slangasek to investigate getting tagged ubuntu-community bugs automatically forwarded to technical-board, and if not feasible, fall back to DMB sending signed emails to list for ACL requests17:07
slangasekin practice I guess we're already relying on the fallback17:08
slangasekbut I would still like to sort this out, it just hasn't been a high priority17:08
slangasekanybody mind if I keep this todo on my list? :)17:08
mdeslaurheh17:08
slangasekhearing no objections...17:09
slangasek[ACTION] slangasek to investigate getting tagged ubuntu-community bugs automatically forwarded to technical-board, and if not feasible, fall back to DMB sending signed emails to list for ACL requests17:09
meetingologyACTION: slangasek to investigate getting tagged ubuntu-community bugs automatically forwarded to technical-board, and if not feasible, fall back to DMB sending signed emails to list for ACL requests17:09
slangasekACTION: slangasek to follow up to snapd-glib SRU exception request17:09
slangasekI don't remember where this one got to17:09
slangasekguess I just need to dig that out of the mail and reply to it, telling them to do the same thing as MAAS17:10
slangasekwill follow up today17:10
slangasek[ACTION] slangasek to follow up to snapd-glib SRU exception request17:10
meetingologyACTION: slangasek to follow up to snapd-glib SRU exception request17:10
slangaseknow, there's an item on the wiki page which I think was discussed last time and I failed to take it off?17:11
slangasekalso, sorry, I'm making a late add of an agenda topic... right now17:11
mdeslauryeah, we discussed that last week17:11
slangasekon the email I just sent to the list re: walinuxagent17:12
slangasek[TOPIC] walinuxagent17:12
slangasek[LINK] https://lists.ubuntu.com/archives/technical-board/2017-March/002287.html17:12
slangasekany chance either of you had time to read this mail, which was sent at 17:01 UTC? ;)17:12
mdeslaurI read it17:12
slangasekmdeslaur: questions/concerns/feedback?17:13
mdeslaurI think the reasoning is sound, and I don't have any objections17:13
mdeslaurmy only concern is how the code which is pulled down is validated17:13
mdeslaurI haven't looked at it at all, is it sane?17:14
slangasekmdeslaur: the endpoint is secured with SSL; there's no code signing that I'm aware of17:14
infinityHow it's validated and/or how the source is validated.17:14
infinitySSL works if it's a static host we're pulling from, and we're not ignoring SSL host mismatches in the code.17:15
slangasekI have an email thread with MS about how control of publishing code to that endpoint is managed, I would need to check with them before sharing details; I'll just say it seems reasonable, and again I don't think we should be setting a higher security bar for that endpoint than we do for the cloud substrate itself17:15
slangasekinfinity: that mostly relies on the underlying python libraries to enforce, AIUI; but the endpoint itself is supposed to be not spoofable17:17
slangasek(as in, no arp/dns spoofing allowed)17:17
infinityWell, the libraries, and how you call the connect methods.17:17
mdeslaurhrm, python 2 code...not sure how well ssl certs and hostnames are being checked17:17
infinityBut yes.17:17
slangasekshould be python317:17
mdeslaurah, yes, it is17:18
mdeslaurok17:18
slangasekcould we take a vote on this, so there's a record of this agreement?17:18
mdeslaursure17:18
slangasek[VOTE] Affirm the walinuxagent exception for out-of-band code updates on Azure guests https://lists.ubuntu.com/archives/technical-board/2017-March/002287.html17:18
meetingologyPlease vote on: Affirm the walinuxagent exception for out-of-band code updates on Azure guests https://lists.ubuntu.com/archives/technical-board/2017-March/002287.html17:18
meetingologyPublic votes can be registered by saying +1, +0 or -1 in channel, (for private voting, private message me with 'vote +1/-1/+0 #channelname)17:18
infinityAnyhow, I'm not super fond of the idea, but if we can't get them to push all their stuff to the archive, we don't really have a choice either.17:18
slangasekyeah, it's not very archive-able17:19
slangasek+117:19
meetingology+1 received from slangasek17:19
mdeslaur+117:19
meetingology+1 received from mdeslaur17:19
infinity+117:19
meetingology+1 received from infinity17:19
slangasekuh how do I end a vote again?17:19
slangasek[ENDVOTE]17:19
meetingologyVoting ended on: Affirm the walinuxagent exception for out-of-band code updates on Azure guests https://lists.ubuntu.com/archives/technical-board/2017-March/002287.html17:19
meetingologyVotes for:3 Votes against:0 Abstentions:017:19
meetingologyMotion carried17:19
slangasekgot it :)17:19
infinityI could see this having more interesting use-cases in heterogenous clouds where the running software might want to change behaviour (or version) based on the compute node you're on.17:19
slangasek[TOPIC] Mailing list archive17:19
infinitySo, as a general policy, it's not awful.17:20
* slangasek nods17:20
slangasekmailing list, there's a request from bdmurray to extend cyphermox's DMB membership to allow coverage for a vote17:20
slangasekthis seems noncontroversial to me, any objection to me JFDI?17:20
infinityGo nuts.17:21
mdeslaurno objection from me17:21
slangasek[ACTION] slangasek to extend cyphermox DMB membership to cover next election17:21
meetingologyACTION: slangasek to extend cyphermox DMB membership to cover next election17:21
cyphermoxyes, please ;)17:21
slangasekI see nothing else new on the mailing list17:21
slangasek[TOPIC] community bugs17:22
slangasek[LINK] https://bugs.launchpad.net/ubuntu-community/+bugs?field.assignee=techboard17:22
slangasekzarro boogs17:22
slangasek[TOPIC] Select a chair for the next meeting17:23
slangaseklooks like stgraber, with infinity as backup?17:23
infinityYep.17:23
slangasek[AGREED] next TB meeting Tuesday, March 28 @ 17:00 London Time; stgraber chair; infinity backup17:24
slangasek[TOPIC] AOB17:24
slangasekanything else?17:24
mdeslaurnope17:25
slangasek#endmeeting17:25
meetingologyMeeting ended Tue Mar 14 17:25:29 2017 UTC.17:25
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting-2/2017/ubuntu-meeting-2.2017-03-14-17.01.moin.txt17:25
mdeslaurthanks slangasek17:25
slangasekmdeslaur, infinity, cyphermox: thanks!17:25
mdeslaurthanks infinity17:25
cyphermoxthanks to you, I had just had a request for DMB stuff.17:25
slangasekcyphermox: renewal done ;)17:26
cyphermoxthere was an important comma there.17:26
cyphermoxta17:26

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!