Wednesday, 2019-06-05

*** slaweq has quit IRC00:03
*** artom has joined #openstack-meeting00:05
*** jgriffith has quit IRC00:22
*** slaweq has joined #openstack-meeting00:23
*** jgriffith has joined #openstack-meeting00:24
*** mriedem_away has quit IRC00:30
*** ykatabam has quit IRC00:30
*** ykatabam has joined #openstack-meeting00:32
*** slaweq has quit IRC00:33
*** yamamoto has quit IRC00:34
*** mattw4 has quit IRC00:44
*** brault has joined #openstack-meeting00:44
*** brault has quit IRC00:49
*** diablo_rojo has quit IRC00:49
*** slaweq has joined #openstack-meeting00:51
*** ziyu has joined #openstack-meeting00:55
*** XSM_HUST has joined #openstack-meeting00:57
*** zhangchi has joined #openstack-meeting00:58
*** Liang__ has joined #openstack-meeting01:00
*** Yipei has joined #openstack-meeting01:02
zhangchi#startmeeting tricircle01:03
openstackMeeting started Wed Jun  5 01:03:10 2019 UTC and is due to finish in 60 minutes.  The chair is zhangchi. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.01:03
*** openstack changes topic to " (Meeting topic: tricircle)"01:03
openstackThe meeting name has been set to 'tricircle'01:03
*** njohnston has quit IRC01:03
*** slaweq has quit IRC01:03
zhangchiMorning Yipei01:03
Yipeihi, zhangchi01:03
XSM_HUSThi all01:03
zhangchiHi Yipei XSM  Nice to meet you all01:04
zhangchiis every one here01:04
zhangchiwelcome back to our bi-weekly meeting01:04
zhangchihi ziyu01:05
zhangchilet check and begin our topics today01:05
zhangchiThe container eviroment need zun and kuyrr add configuration01:08
zhangchi#info XSM_hust I think you can submit a bug or patch on lanuchpad01:09
zhangchiziyu  what about you ipv6_mode function test01:11
ziyuthat already merged01:12
ziyuI with yaguang are studying zull v301:12
ziyumaybe you can help us to have a look, after the meeting.01:12
zhangchiok let's check the zull v3 later01:16
*** cyg has joined #openstack-meeting01:17
*** enriquetaso has quit IRC01:21
*** slaweq has joined #openstack-meeting01:21
zhangchisome format changed between zuul v3 and v201:23
ziyuthank you!01:24
zhangchixiaohan is now working on funtional test over 80%, now reached 78%01:25
YipeiSorry, guys, I have some personal business to address. I have to leave now.01:25
zhangchiok Yipei take your time01:26
YipeiThank you, bye01:26
*** baojg has joined #openstack-meeting01:26
*** boxiang has quit IRC01:26
zhangchiOk bye Yipei01:27
*** Yipei has quit IRC01:27
*** boxiang has joined #openstack-meeting01:27
zhangchiwhat about the else topics now01:28
zhangchi#info xsm please show me the bugs link later we'all check later01:29
*** zhangchi has quit IRC01:33
*** ziyu has quit IRC01:33
*** slaweq has quit IRC01:33
*** cyg has quit IRC01:35
*** cyg has joined #openstack-meeting01:35
*** zhangchi has joined #openstack-meeting01:36
zhangchiright now we are planning to make tricirle and trio2o working together, on plan stage now01:36
zhangchiany other topics now01:38
zhangchiif not we'all end right now01:39
*** openstack changes topic to "OpenStack Meetings ||"01:39
openstackMeeting ended Wed Jun  5 01:39:29 2019 UTC.  Information about MeetBot at . (v 0.1.4)01:39
openstackMinutes (text):
*** zhangchi has quit IRC01:39
*** rfolco has quit IRC01:46
*** hongbin has joined #openstack-meeting01:47
*** rfolco has joined #openstack-meeting01:47
*** cyg has quit IRC01:53
*** XSM_HUST has quit IRC01:54
*** slaweq has joined #openstack-meeting01:54
*** ykatabam has quit IRC01:55
*** apetrich has quit IRC01:57
*** XSM_HUST has joined #openstack-meeting01:58
*** lseki has quit IRC02:02
*** slaweq has quit IRC02:03
*** lbragstad has quit IRC02:14
*** slaweq has joined #openstack-meeting02:14
*** boxiang_ has joined #openstack-meeting02:16
*** boxiang has quit IRC02:18
*** yamamoto has joined #openstack-meeting02:23
*** slaweq has quit IRC02:25
*** slaweq has joined #openstack-meeting02:41
*** ykatabam has joined #openstack-meeting02:43
*** yamahata has quit IRC02:48
*** iyamahat_ has quit IRC02:49
*** slaweq has quit IRC02:54
*** markvoelker has joined #openstack-meeting02:59
*** XSM_HUST has quit IRC03:15
*** slaweq has joined #openstack-meeting03:15
*** slaweq has quit IRC03:26
*** markvoelker has quit IRC03:30
*** slaweq has joined #openstack-meeting03:42
*** Liang__ has quit IRC03:43
*** Liang__ has joined #openstack-meeting03:45
*** hongbin has quit IRC03:52
*** slaweq has quit IRC03:55
*** ricolin has joined #openstack-meeting03:58
*** gyee has quit IRC04:02
*** imsurit has joined #openstack-meeting04:04
*** slaweq has joined #openstack-meeting04:12
*** ykatabam has quit IRC04:13
*** bnemec has quit IRC04:23
*** gmann has quit IRC04:23
*** slaweq has quit IRC04:25
*** bnemec has joined #openstack-meeting04:25
*** markvoelker has joined #openstack-meeting04:27
*** gmann has joined #openstack-meeting04:27
*** pcaruana has joined #openstack-meeting04:30
*** ykatabam has joined #openstack-meeting04:46
*** markvoelker has quit IRC05:00
*** slaweq has joined #openstack-meeting05:02
*** rubasov has quit IRC05:31
*** kopecmartin|off is now known as kopecmartin05:34
*** radeks has joined #openstack-meeting05:39
*** markvoelker has joined #openstack-meeting05:56
*** radeks_ has joined #openstack-meeting06:00
*** radeks has quit IRC06:03
*** markvoelker has quit IRC06:28
*** e0ne has joined #openstack-meeting06:31
*** takamatsu has joined #openstack-meeting06:32
*** apetrich has joined #openstack-meeting06:33
*** radeks_ has quit IRC06:39
*** heikkine has joined #openstack-meeting06:55
*** ykatabam has quit IRC06:58
*** lpetrut has joined #openstack-meeting06:58
*** liuyulong_ has joined #openstack-meeting06:58
*** rcernin has quit IRC06:59
*** brault has joined #openstack-meeting07:02
*** tssurya has joined #openstack-meeting07:13
*** e0ne has quit IRC07:15
*** aloga has quit IRC07:23
*** aloga has joined #openstack-meeting07:23
*** tesseract has joined #openstack-meeting07:25
*** liuyulong_ has quit IRC07:26
*** ttsiouts has joined #openstack-meeting07:27
*** ttsiouts has quit IRC07:37
*** whoami-rajat has joined #openstack-meeting07:45
*** ralonsoh has joined #openstack-meeting07:51
*** heikkine has quit IRC07:58
*** heikkine has joined #openstack-meeting08:00
*** heikkine has left #openstack-meeting08:00
*** ttsiouts has joined #openstack-meeting08:02
*** heikkine has joined #openstack-meeting08:03
*** tetsuro has joined #openstack-meeting08:05
*** Lucas_Gray has joined #openstack-meeting08:13
*** panda|ruck has quit IRC08:14
*** markvoelker has joined #openstack-meeting08:26
*** panda has joined #openstack-meeting08:28
*** ykatabam has joined #openstack-meeting08:35
*** radeks has joined #openstack-meeting08:38
*** ykatabam has quit IRC08:39
*** ykatabam has joined #openstack-meeting08:42
*** tetsuro has quit IRC08:46
*** panda is now known as panda|ruck08:52
*** imsurit has quit IRC08:56
*** rcernin has joined #openstack-meeting08:58
*** markvoelker has quit IRC08:59
*** hberaud has joined #openstack-meeting09:15
*** priteau has joined #openstack-meeting09:22
*** e0ne has joined #openstack-meeting09:30
*** Liang__ has quit IRC09:36
*** yamamoto has quit IRC09:50
*** miloa has joined #openstack-meeting09:54
*** markvoelker has joined #openstack-meeting09:57
*** lpetrut has quit IRC10:09
*** boxiang_ has quit IRC10:10
*** boxiang has joined #openstack-meeting10:10
*** verdurin has joined #openstack-meeting10:11
*** ttsiouts has quit IRC10:15
*** ttsiouts has joined #openstack-meeting10:16
*** ttsiouts has quit IRC10:20
*** lpetrut has joined #openstack-meeting10:22
*** yamamoto has joined #openstack-meeting10:24
*** baojg has quit IRC10:28
*** markvoelker has quit IRC10:29
*** yamamoto has quit IRC10:33
*** yamamoto has joined #openstack-meeting10:34
*** yamamoto has quit IRC10:35
*** oneswig has joined #openstack-meeting10:38
*** ricolin has quit IRC10:47
*** yamamoto has joined #openstack-meeting10:48
*** janders has joined #openstack-meeting10:51
*** yamamoto has quit IRC10:53
*** boxiang_ has joined #openstack-meeting10:54
*** dh3 has joined #openstack-meeting10:55
*** boxiang has quit IRC10:57
*** martial_ has joined #openstack-meeting11:00
oneswig#startmeeting scientific-sig11:00
openstackMeeting started Wed Jun  5 11:00:25 2019 UTC and is due to finish in 60 minutes.  The chair is oneswig. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.11:00
*** openstack changes topic to " (Meeting topic: scientific-sig)"11:00
openstackThe meeting name has been set to 'scientific_sig'11:00
oneswigyarr \o/11:00
jandershi All11:00
*** mgoddard has joined #openstack-meeting11:00
martial_Good morning/day/evening :)11:00
jandersoneswig: would you mind if we start with the SDN discussion? I need to pop out for half an hour soon11:00
oneswighi janders, g'day11:00
oneswigcertainly, lets do that.11:01
oneswighi verdurin11:01
oneswig#link Agenda for today
*** b1airo has joined #openstack-meeting11:01
oneswigOK, let's start by ignoring the running order...11:01
dh3hi all11:01
oneswig#topic Coherent SDN fabrics11:01
*** openstack changes topic to "Coherent SDN fabrics (Meeting topic: scientific-sig)"11:01
oneswigjanders: you raised this at teh PTG11:01
jandersonly a brief update from my side: I've had a brief chat with the Mellanox guys. Overall they don't see an issue with this, but I'd like to get more detailed feedback off them11:01
oneswig#chair b1airo martial_11:01
openstackCurrent chairs: b1airo martial_ oneswig11:02
janderslast week's neutron-driver meeting got cancelled so haven't spoken to the Neutron guys in detail either11:02
jandersindeed - this is follow up to the SDN consistency issues that we raised in the SIG11:02
oneswigjanders: ah that's too bad on the cancelled meeting11:02
oneswighi mgoddard thanks for coming11:02
oneswigdid you see what this is about?11:02
*** ttsiouts has joined #openstack-meeting11:03
mgoddardhi oneswig yes I did, and thought I'd pop along11:03
jandershey Mark thanks for coming11:03
oneswig#link Spec in review
mgoddardI haven't got as far through the neutron spec as I'd like11:03
oneswigMe neither.  Still a little concerned it's tied to one implementation11:04
oneswigWe could come back to this in 15 minutes to allow some reading time?11:05
jandersmy understanding is they're trying to model on ODL but are trying to make the consistency check mechanism generic11:05
janderswhat we can also do is - I will give you guys some time to go through this more in detail - and if you could make comments in the bug, that would be great11:06
oneswigHi hberaud, welcome11:06
*** yamamoto has joined #openstack-meeting11:06
jandersdoesn't have to be during the meeting11:06
hberaudoneswig: thx11:06
oneswigjanders: +1 makes sense to get the feedback out there11:06
mgoddardone key difference between mlnx and OVS is the async update11:07
jandersbut I think if we could provide some feedback to the Neutron guys before Friday's driver meeting, that would be great11:07
mgoddardthe mellanox driver updates NEO in an async thread11:07
mgoddardso not only have we committed the update to the neutron DB, we've actually finished processing the original update request by the time NEO is updated11:07
jandersright! that matches my experience/observations11:08
oneswigmgoddard: in extreme cases could this cause a provisioned instance to be transiently connected to a different tenant network?  Is there any means of blocking on completion of an operation?11:09
*** ociuhandu has joined #openstack-meeting11:09
b1airoo_0 !11:10
mgoddardoneswig: potentially11:10
mgoddardoneswig: neutron does have a blocking mechanism, but I don't think mlnx uses it11:10
janderswhich part of this would need to go into neutron-core, and which part would be mlnx-specific changes?11:10
mgoddardthere is a thing called provisioning blocks which can be used for this11:11
mgoddardagents are inherently aysnc, so it's nothing new. You just have to know how to use it11:11
jandersconvincing mlnx to use that definitely sounds like a good idea11:11
oneswigAh OK.  Feature not bug11:11
jandersbut how about detecting state divergence and addressing it? what we're talking about doesn't address that right?11:12
jandersor would it?11:12
mgoddardProbably bug not feature :)11:12
b1airostate divergence is always a potential problem if the controller can be changed/updated independently of Neutron11:13
oneswigjanders: yes this doesn't relate to the missing port updates11:13
jandersmy idea behind the bug was implementing a mechanism that brings SDN-based approaches on par with ovs - so that state divergence can be detected/addressed11:14
janders looks like it might be able to address that11:14
jandershowever it would be great to have your feedback11:14
jandersin general I think it would be worthwhile to split the discussion into two parts - the generic one (which the neutron team need to address) and the specific ones (which I'm happy to bring up with Mellanox)11:15
jandersI totally see value of improvements around provisioning blocks as suggested by mgoddard11:16
oneswigMakes sense.  First part may be gated, for example, on the difficulty of associating a revision number on applied config in arbitrary SDN implementations.  That's reviewing the spec I guess11:17
mgoddardI think provisioning blocks could be an easy win11:17
mgoddardthen the spec might be able to prevent subsequent drift11:17
oneswigjanders: think you can entice your friendly mlnx engineer here for part 2?11:17
jandersI have to disappear for about half an hour now - can I please ask you to make comments on what you like/dislike/any suggestions around the generic part in the bug report? It would be great to see some activity there, it would help get attention from the devs11:17
jandersoneswig: yes, I'm happy to! :)11:18
jandersexcellent - thanks guys11:18
jandershopefully I'll be back before the end of the meeting11:18
oneswig#action janders Involve Mellanox tech team on the issue11:18
oneswig#action oneswig mgoddard add comments to the bug report and/or spec11:18
oneswigOK, thanks janders and all, next11:19
*** panda|ruck is now known as panda|ruck|eat11:19
oneswig#topic CERN OpenStack roundup11:19
*** openstack changes topic to "CERN OpenStack roundup (Meeting topic: scientific-sig)"11:19
oneswigthat was fun, the CERN team laid on a great day11:19
oneswigdh3: great talk11:19
dh3you are too kind *blush*11:19
oneswigHow's the eagle recovering from being swabbed? :-)11:19
dh3I hear there are some interesting stories from field expeditions ("Real Science")11:20
oneswigI once had a support call that ended "can we get this fixed because there's a plane flying over antartica right now that needs the service back onilne..."11:20
oneswigIn a previous job11:21
b1airolooked like a good time on Slack and Twitter11:21
oneswigI enjoyed it.  In the afternoon the talk on OpenStack control plane tracing was especially interesting.11:21
dh3Yes I think osprofiler could be educational as well as useful11:22
oneswig#link Ilya's presentation
*** ykatabam has quit IRC11:22
oneswigI think we'll be doing plenty of that in due course11:23
martial_nice, thanks11:24
*** Lucas_Gray has quit IRC11:24
oneswigErwan Gallens talk on face recognition was good too - nice to cover more on the algorithms.11:25
oneswigOK we should move on I think11:25
oneswig#topic Secure Computing Environments11:26
*** openstack changes topic to "Secure Computing Environments (Meeting topic: scientific-sig)"11:26
*** markvoelker has joined #openstack-meeting11:26
oneswigOne question from the audience at CERN last week related to how to find best practice for controlled-access data processing11:26
oneswigThis is something we've attempted to grapple with previously but not got very far towards common ground.11:27
oneswigOnce more unto the breach...11:27
oneswigJani from Basel University and I presented on a project underway there11:28
oneswig#link BioMedIT project in Basel
oneswigThis was a lightning talk though so no time to cover anything at all in depth11:28
martial_this had all the talks11:29
oneswigcool, thanks martial_11:29
dh3We don't have a best practice as such - we are still offering all the various compute/storage facilities to data owners/principal investigators and trying to help them choose the right one for their data access and analysis workload11:30
dh3buffet table vs a la carte I guess11:30
verdurinOn our side, the first meeting to discuss a paper about our work with restricted data is coming up. That will be science as well as infrastructure.11:31
*** ttsiouts has quit IRC11:31
oneswigI saw a useful paper recently on classification of security levels across various domains, but I'm struggling to find it alas11:32
*** ttsiouts has joined #openstack-meeting11:32
b1airointeresting set of slides11:32
b1airolooks like a decent architecture, though the thing often missing is mapping of various controls to any particular framework of reference11:34
oneswigSomething I'd like to see is authoritative research of the form "to achieve this level of security / standard, you must implement this...'11:34
dh3oneswig: do you have something like ISO 27001/2 in mind?11:35
oneswigYes, that kind of thing, but also there are different classification systems in different sectors - government, health data, etc.11:36
*** ttsiouts has quit IRC11:36
b1airoyes agreed oneswig... starting with a basic multi-tenant cloud implementation, what bits of OpenStack or other standard tooling can you sprinkle in to achieve sufficient confidence in the architecture and visibility of drift or abnormalities, you then need to layer in incident response requirements, so on and so forth11:38
oneswigb1airo: infrastructure configuration is certainly not the only requirement, true.11:39
verdurinYes, in my experience, lots of policies, and possibly even the setting up of new administrative bodies.11:40
oneswigI'm drawing a blank on this paper, may follow up to the Slack workspace if I find it.11:40
b1airoto achieve compliance with any standard there's necessarily a layer of abstraction down to specific controls, procedures (and sometimes the organisational units & heads that are responsible for them)11:40
dh3I've never had to work with that sort of published standard but experience says that it will reach from infra/admins through application devs too11:41
b1airoin OpenStack today I don't think we even have a reference list of controls, let alone reference architectures11:42
oneswigdh3: do you need specific standards to host eg UK BioBank data?  (Or was that just animals and plants?)11:42
*** raildo has joined #openstack-meeting11:42
verdurinoneswig: it's actually more complicated than that, there are many varieties of UKB data, with their own special requirements.11:43
dh3oneswig: it's not really my area but I know that for some data (human identifiable) we have had to implement separate networks, virt platforms, storage....11:43
*** yamamoto has quit IRC11:44
oneswigdh3: does Sanger have policy guidelines for this that are public?11:44
dh3our UKB vanguard data is in our production OpenStack environment, but in a separate host aggregate (for perf isolation but does bring security) and separate storage/networking (via provider network)11:44
dh3oneswig: not that I have seen! but I can ask11:45
heikkinedh3 Jani from Basel here, I agree with requirement for separate networks, etc.11:45
oneswigMight be really useful!11:45
oneswighi heikkine, thanks for coming11:45
heikkineI may drop off any moment but trying to follow what I can11:45
oneswigdh3: do you go as far as separate physical storage?11:46
dh3oneswig: yes in some cases, "identifiable human data" is the usual trigger but not always11:47
heikkinedh3: what is in your case separate physical storage? Separate from OpenStack?11:47
dh3heikkine: taking UKB as an example, we have it on a separate Lustre system, it's only accessible from that tenant's provider network.11:48
oneswigso separate from OpenStack and separate from other projects too11:49
janderswould software-defined-storage help in this sense?11:49
heikkineI see. So you do tenant isolation that way. We are starting with NFS but I have done tests with BeeGFS11:49
jandersas in - having a pool of JBOFs - and then spinning up a "private" storage cluster of a certain scale on demand11:49
verdurinWe are looking at Lustre to cover this kind of case in the future, given it's more amenable than GPFS.11:49
oneswigA substantial discussion in its own right11:49
b1airothere are some US standards that actually specify isolated physical storage11:50
dh3janders: it depends - again not entirely my area but I understand that some data access agreements are restrictive on where data can be kept (physically and geographically) - and SDS makes it harder to show an auditor "it's here"11:50
oneswigOver the summer it may be good to gather some of these pieces together into a joint study.  Does anyone object to being involved?11:51
b1airoe.g. think ITAR data cannot be mixed with non-ITAR data on same physical storage11:51
martial_I think this is correct, Blair11:51
b1airolol, love the phrasing of that question oneswig !11:51
jandersright! whether it works is one thing, whether it ticks compliance box might be another thing. Very useful feedback, thank you.11:51
verdurinjanders: yes, to echo dh3's comments, I'm dealing with a project at the moment in which the form would not cope well with such a setup.11:51
dh3SDS also makes proving secure deletion more difficult (can't even identify which HDDs to take out and shred...)11:52
oneswigb1airo: opt-out from being volunteered :-)11:52
janders(I suppose node cleaning doesn't cut it :)11:52
dh3node cleaning + DBAN maybe :)11:52
b1airojanders: actually if you are using self-encrypting disks then it might...11:53
verdurinDon't deprive the workshop people of their longer-for chances to deploy the angle grinder11:53
oneswigverdurin: --yes-i-really-mean-it ...11:53
b1airobecause we know hardware level security is so good... *cough*11:53
oneswigOne more topic to cover today, can we follow up on this perhaps via the slack channel?11:54
b1airosounds good11:54
oneswigdh3: are you on there?11:54
oneswigI can send an invite - unless you're too secure for Slack of course :-)11:54
oneswig#topic Justification whitepaper for on premise cloud for research and scientific computing11:55
*** openstack changes topic to "Justification whitepaper for on premise cloud for research and scientific computing (Meeting topic: scientific-sig)"11:55
dh3oneswig: no (not yet - do invite me please)11:55
oneswigdh3: will do11:55
oneswigjust a quick mention, some of the US folks are very interested in pooling together on a paper that lays out the private cloud case11:55
oneswigThis was raised at the SIG session in the Denver PTG11:56
b1airothere's a great NASA tech paper i came across today that looks at this from the HPC perspective:
oneswigAnyone in this session recently made this case themselves?11:56
oneswigthanks b1airo11:56
oneswigDuring the session somebody mentioned the talk by Andrew Jones of NAG at the UKRI Cloud Workshop in January11:57
oneswig#link Andrew Jones presentation
oneswigThe hope is that this material might make a useful resource to draw upon when writing procurement proposals.11:58
janderslots of follow up reading after today's meeting - thanks for some great links guys11:58
b1airoa key thing to establish early on here would be the kinds of applications that are being supported on the private cloud11:59
dh3hadn't seen that, thanks (but we are "strategically" going cloud-wards anyway)11:59
oneswigb1airo: very true11:59
b1airoand a valid answer might be "all of them"11:59
oneswigOK nearly out of time - final comments on this?11:59
b1airoraise it again for next week's timezone i guess11:59
*** markvoelker has quit IRC12:00
oneswigb1airo: +1, will do.12:00
oneswigOK all, time to stop - thanks everyone12:00
jandersthanks guys! again - any comments in the SDN bug will be very welcome by the Neutron team12:00
martial_Thanks ;)12:00
oneswigjanders: will do12:00
*** openstack changes topic to "OpenStack Meetings ||"12:00
openstackMeeting ended Wed Jun  5 12:00:46 2019 UTC.  Information about MeetBot at . (v 0.1.4)12:00
openstackMinutes (text):
dh3thanks all, talk soon12:01
verdurinThanks, bye.12:01
oneswigUntil next time12:01
*** mgoddard has left #openstack-meeting12:02
*** gmann has quit IRC12:03
*** ricolin has joined #openstack-meeting12:03
*** janders has quit IRC12:04
*** ociuhandu_ has joined #openstack-meeting12:06
*** dh3 has quit IRC12:06
*** ociuhandu has quit IRC12:06
*** yamamoto has joined #openstack-meeting12:09
*** ttsiouts has joined #openstack-meeting12:10
*** jaypipes has joined #openstack-meeting12:28
*** panda|ruck|eat is now known as panda|ruck12:30
*** oneswig has left #openstack-meeting12:35
*** rcernin has quit IRC12:37
*** priteau has quit IRC12:41
*** radeks has quit IRC12:48
*** radeks has joined #openstack-meeting12:50
*** priteau has joined #openstack-meeting12:54
*** njohnston has joined #openstack-meeting12:59
*** ttsiouts has quit IRC13:01
*** ttsiouts has joined #openstack-meeting13:01
*** ttsiouts has quit IRC13:05
*** eharney has joined #openstack-meeting13:06
*** mriedem has joined #openstack-meeting13:10
*** apetrich has quit IRC13:10
*** baojg has joined #openstack-meeting13:11
*** lbragstad has joined #openstack-meeting13:17
*** ayoung has joined #openstack-meeting13:17
*** ttsiouts has joined #openstack-meeting13:22
*** apetrich has joined #openstack-meeting13:23
*** _erlon_ has joined #openstack-meeting13:27
*** yamamoto has quit IRC13:28
*** cheng1__ has joined #openstack-meeting13:36
*** lseki has joined #openstack-meeting13:40
*** eharney has quit IRC13:41
*** rcernin has joined #openstack-meeting13:42
*** bobh has joined #openstack-meeting13:47
*** jamesmcarthur has joined #openstack-meeting13:48
*** bdperkin has quit IRC13:49
*** bobh has quit IRC13:50
*** dtrainor has quit IRC13:52
*** enriquetaso has joined #openstack-meeting13:53
*** eharney has joined #openstack-meeting13:57
*** baojg has quit IRC13:59
*** mlavalle has joined #openstack-meeting14:00
mlavalle#startmeeting neutron_l314:01
openstackMeeting started Wed Jun  5 14:01:00 2019 UTC and is due to finish in 60 minutes.  The chair is mlavalle. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: neutron_l3)"14:01
openstackThe meeting name has been set to 'neutron_l3'14:01
*** eharney has quit IRC14:02
mlavalle#topic Announcements14:03
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"14:03
mlavalleJust a quick reminder that this is the Train-1 milestone week14:04
mlavallewe reviewed the blueprints we were targeting for this milestone yesterday and we made solid progress14:05
mlavallethanks for all your hard waork14:05
*** miloa has quit IRC14:05
mlavallePlease also remember that July 2nd is the deadline for the Shanghai Summit CFP14:06
mlavalleany other announcements?14:06
mlavallemoving on14:07
mlavalle#topic Bugs14:07
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"14:07
mlavalleFirst one in the list is
openstackLaunchpad bug 1821912 in neutron "intermittent ssh failures in various scenario tests" [High,In progress] - Assigned to LIU Yulong (dragon889)14:08
mlavalleslaweq: any update with the authentication problem?14:08
*** martial_ has quit IRC14:09
slaweqmlavalle: nope14:09
*** jamesmcarthur has quit IRC14:09
slaweqI didn't make any progress on this one14:09
mlavallestill working on it?14:10
slaweqmlavalle: I will look if I will have some time14:11
slaweqbut I can't promise it will be this or next week14:11
mlavallerelated to this is
openstackLaunchpad bug 1830763 in neutron "Debug neutron-tempest-plugin-dvr-multinode-scenario failures" [High,Confirmed] - Assigned to Miguel Lavalle (minsel)14:11
*** radeks_ has joined #openstack-meeting14:12
mlavalleI spent time yesterday reproducing locally the failure of test_connectivity_thorugh_2_routers14:12
mlavalleI can reproduce it exactly as it happens in the zuul14:13
mlavalleand the test case attempts to ping one VM from the other14:13
mlavallein sshing to the VM that is going to send the ping, I get an ssh failure14:13
mlavalleso it will probably help with 182191214:14
mlavalleI'll report any further discovery in both bugs14:14
*** radeks has quit IRC14:14
mlavalleNext one is
openstackLaunchpad bug 1831534 in neutron "[l3][dvr] with openflow security group east-west traffic between different vlan networks is broken" [High,In progress] - Assigned to LIU Yulong (dragon889)14:15
*** artom has quit IRC14:15
mlavallethis one recently reported14:15
*** eharney has joined #openstack-meeting14:15
mlavalleand liuyulong is working on a fix14:16
mlavallethis is a related patch
mlavallethose are all the bugs I have today14:17
mlavalleany other bugs we should discuss today?14:17
haleybi have more :(14:17
mlavallefire away14:17
openstackLaunchpad bug 1831575 in neutron "br-tun gets a wrong arp drop rule when dvr is connected to a network but not used as gateway" [High,Fix released] - Assigned to Slawek Kaplonski (slaweq)14:17
*** thgcorrea has joined #openstack-meeting14:17
haleyboh, sorry, that one just merged...14:18
haleybthere are backports to do14:18
*** Lucas_Gray has joined #openstack-meeting14:18
*** jamesmcarthur has joined #openstack-meeting14:18
openstackLaunchpad bug 1831706 in neutron "[DVR] Modify `in_port` field of packets which from remote qr-* port" [Undecided,New]14:18
haleybthere was a comment from the submitter this could be related to
openstackLaunchpad bug 1732067 in neutron "openvswitch firewall flows cause flooding on integration bridge" [High,In progress] - Assigned to Zhengdong Wu (zhengdong.wu)14:19
haleybliuyulong: can you take a look at that as you were also active in the review for ^^^14:20
haleybi will follow-up with him since he's not here14:21
haleybthose where the only other bugs i had14:21
mlavallethanks haleyb14:22
*** jamesmcarthur has quit IRC14:22
mlavalle#topic On demand agenda14:22
*** openstack changes topic to "On demand agenda (Meeting topic: neutron_l3)"14:22
mlavalleanything lese we should discuss today?14:23
*** bnemec has quit IRC14:23
tidwellrif anyone has a minute, I resurrected
*** bnemec has joined #openstack-meeting14:25
mlavalleyes, I noticed that14:25
mlavalleI will take a look soon14:25
mlavalleit's in my pile14:25
mlavallethanks for following up14:25
*** jamesmcarthur has joined #openstack-meeting14:26
*** cheng1__ has quit IRC14:26
mlavallethis was a quick one14:26
mlavalleenjoy the rest of your day14:26
*** openstack changes topic to "OpenStack Meetings ||"14:27
openstackMeeting ended Wed Jun  5 14:27:06 2019 UTC.  Information about MeetBot at . (v 0.1.4)14:27
openstackMinutes (text):
*** dtrainor has joined #openstack-meeting14:27
*** yamamoto has joined #openstack-meeting14:27
*** lpetrut has quit IRC14:28
*** b1airo has quit IRC14:30
*** yamamoto has quit IRC14:32
*** dtrainor has quit IRC14:32
*** eharney has quit IRC14:35
*** bdperkin has joined #openstack-meeting14:39
*** mlavalle has left #openstack-meeting14:40
*** dtrainor has joined #openstack-meeting14:45
*** eharney has joined #openstack-meeting14:48
*** boxiang has joined #openstack-meeting14:49
*** akhil_jain has joined #openstack-meeting14:50
*** artom has joined #openstack-meeting14:51
*** lpetrut has joined #openstack-meeting14:52
*** eharney has quit IRC14:54
*** lpetrut has quit IRC14:54
*** lpetrut has joined #openstack-meeting14:55
*** cheng1__ has joined #openstack-meeting15:00
*** boxiang has quit IRC15:03
*** lennyb has quit IRC15:07
*** lennyb has joined #openstack-meeting15:07
*** eharney has joined #openstack-meeting15:07
*** diablo_rojo has joined #openstack-meeting15:16
*** panda|ruck is now known as panda15:19
*** woojay has joined #openstack-meeting15:19
*** cheng1__ has quit IRC15:20
*** cheng1__ has joined #openstack-meeting15:21
*** rcernin has quit IRC15:26
*** liuyulong has quit IRC15:26
*** gyee has joined #openstack-meeting15:27
*** aarents has joined #openstack-meeting15:29
*** cheng1__ has quit IRC15:31
*** cheng1__ has joined #openstack-meeting15:32
*** ttsiouts has quit IRC15:32
*** ttsiouts has joined #openstack-meeting15:33
*** enriquetaso has quit IRC15:35
*** enriquetaso has joined #openstack-meeting15:35
*** tssurya has quit IRC15:36
*** ttsiouts has quit IRC15:38
*** kopecmartin is now known as kopecmartin|off15:53
*** rosmaita has joined #openstack-meeting15:54
*** Qiming has quit IRC15:54
*** cheng1__ has quit IRC15:55
*** Lucas_Gray has quit IRC15:55
*** davidsha has joined #openstack-meeting15:57
*** _erlon_ has quit IRC15:57
*** Qiming has joined #openstack-meeting15:58
*** m5z_|mszwed| has joined #openstack-meeting15:58
jungleboyj#startmeeting Cinder16:00
openstackMeeting started Wed Jun  5 16:00:26 2019 UTC and is due to finish in 60 minutes.  The chair is jungleboyj. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: Cinder)"16:00
openstackThe meeting name has been set to 'cinder'16:00
jungleboyjcourtesy ping:  jungleboyj whoami-rajat rajinir lseki carloss pots woojay erlon geguileo eharney rosmaita enriquetaso e0ne smcginnis davidsha walshh_ xyang hemna _hemna eharney16:00
geguileohi! o/16:00
m5z_|mszwed|hi :)16:00
_pewp_jungleboyj (;-_-)ノ16:01
_pewp_hemna (✧∇✧)╯16:01
_pewp_jungleboyj (*゚͠ ∀ ͠)ノ16:02
* jungleboyj misses _pewp_ in the cinder channel16:02
*** panda is now known as panda|off16:02
jungleboyjOk.  Lets get started.16:03
jungleboyj#topic announcements16:03
*** openstack changes topic to "announcements (Meeting topic: Cinder)"16:03
*** markvoelker has joined #openstack-meeting16:04
jungleboyjJust a friendly reminder that we have the Train Mid-Cycle planning going on.16:04
jungleboyjIf you can make it please add your name.16:05
jungleboyjStart planning ahead so we can have a good turnout.16:05
_pewp_hemna (/ .□.) ︵╰(゜Д゜)╯︵ /(.□. )16:05
_pewp_hemna (/ .□.) ︵╰(゜Д゜)╯︵ /(.□. )16:05
_pewp_hemna (/ .□.) ︵╰(゜Д゜)╯︵ /(.□. )16:05
_pewp_hemna (/ .□.) ︵╰(゜Д゜)╯︵ /(.□. )16:05
_pewp_hemna (/ .□.) ︵╰(゜Д゜)╯︵ /(.□. )16:05
hemnawtf was that16:05
* jungleboyj is laughing16:05
jungleboyj_pewp_:  Is mad at you16:05
jungleboyjAnyone have other announcements?16:06
e0nejungleboyj: will you cut train-1 for cinder tomorrow?16:06
e0neAFAIK, it's not required anymore16:06
jungleboyje0ne:  Good question.  I thought that we didn't have to do that anymore.16:06
jungleboyjsmcginnis: ^^16:07
rosmaitapretty sure it is up to us16:07
e0nejungleboyj: it's up to the team16:07
smcginnisThe cycle-with-intermediary deliverables will be proposed, but no need to do beta releases of the services anymore.16:07
smcginnisOnly reason to do a x.x.x.0b1 release is if you actually know someone downstream wants to pick it up and do something with it.16:08
jungleboyjsmcginnis:  Ok, that is what I thought.16:08
jungleboyjeharney: geguileo Anything you guys need a beta for?16:08
geguileojungleboyj: I don't think so...16:09
* jungleboyj hears crickets16:09
geguileoeharney: ^16:09
jungleboyjOk.  Good.  So, I would say we just keep rolling forward.16:09
smcginnisBased on what we saw, those usually were not being used.16:09
jungleboyjWe also don't have any deadlines for T-1 .16:09
jungleboyjThough, now we need to make sure we are helping get people to T-2.16:10
jungleboyjDoing driver reviews, reviewing spes.16:10
smcginnisGotta get those drivers reviewed.16:10
jungleboyjsmcginnis:  ++16:11
jungleboyjSo, a todo for the whole team is to please work on reviewing drivers and specs.16:12
* jungleboyj is included16:13
eharneyi don't think we have any need for it16:13
*** mattw4 has joined #openstack-meeting16:13
jungleboyjOk.  I think we can move on.16:13
jungleboyj#topic Driver Unsupported Patches16:14
*** openstack changes topic to "Driver Unsupported Patches (Meeting topic: Cinder)"16:14
jungleboyjI have a list in the agenda of the drivers I have unsupported.16:14
hemnais there a review topic for those?16:15
jungleboyjAppreciate help getting those merged.16:15
jungleboyjThey all start with 'unsupport'16:15
jungleboyjGuess I should have made that more general.16:16
jungleboyjI could set them to a review topic.16:17
hemnamaybe change the topic on all of them, to the same?16:17
smcginnisjungleboyj: I think I had always used "ci-unsupported" to make it easy to find all of them.16:17
jungleboyjOk.  I will do that.16:17
rajinirIs there a link that can list them?16:19
jungleboyjI am also going to try to work on getting driver removal patches up yet this week so that is all taken care of.16:19
jungleboyjrajinir: They are in the agenda right now:
smcginnisrajinir: If they all have the same topic, then it's easy to list the gerrit query to list them all16:19
jungleboyjOr you can just click on the topic and get a list.16:19
smcginnisSimilar to what I set for the new drivers:
smcginnisjungleboyj: Had the ci_unsupported wrong (-/_):
jungleboyjAh, you do that for removal too.  Ok.  Good.16:21
* jungleboyj thinks that is something to add to our documentation. :-)16:22
rajinirsmcginnis: thanks16:22
jungleboyjSo, I will keep all the patches under that topic.16:23
jungleboyjSo, I think that is all I have there.16:24
jungleboyj#topic Update on Ceph iSCSI driver16:24
*** openstack changes topic to "Update on Ceph iSCSI driver (Meeting topic: Cinder)"16:24
hemnaok I guess I'm up16:24
hemnaso I've been doing some research on an iscsi ceph driver16:25
jungleboyjhemna:  If you don't mind.16:25
hemnaI have an etherpad here:
hemnaand a WIP of the driver here:
hemnathe driver assumes that it has access to the rbd-target-api from the project16:26
hemnathe rbd-target-api python REST flask server is meant to coordinate the iscsi gw configs between ceph iscsi gateways16:27
hemnaso it's not really meant to do what I'm using it for16:27
hemnabut it happens to work at this point16:27
hemnaI'm getting close to having the initialize_connection working16:27
hemnaI was able to get a single attach and detach work16:27
hemnabut then discovered issues, which is leading to more work for both initialize_connection and terminate_connection16:27
*** lpetrut has quit IRC16:28
hemnathere is zero documentation on how to properly use the rbd-target-api to do an export16:28
hemnabut I'm kinda figuring it out as a go from a standalone script using my REST client16:28
smcginnisAny conversations in the ceph community to just get some assurance that this is an acceptable use of it?16:28
hemnanah not yet16:29
hemnamy hope is to verify that this works16:29
hemnathen the thought was to create a separate client pypi project16:29
hemnathat is the REST client that can talk to the rbd-target-api16:29
hemnawhich is my ceph_iscsi_client.py16:30
* jungleboyj is thinking it is good that you are the one working on this.16:30
hemnathe driver is a derivation of the existing cinder driver16:30
hemnaso I got most of the functionality for free so far16:30
hemnaother than attach/detach16:30
jungleboyjhemna:  Awesome.  I was hoping that that would be the case.16:31
hemnabut I've done zero testing with it other than create a few volumes and work on attach/detach16:31
hemnathis is a research project still at this point16:31
hemnawith the hopes that it can get stabilized and then work on cleaning it up and making it a viable driver16:31
geguileogreat progress!!16:32
hemnathere is a lot of setup on the ceph cluster side to make sure the iscsi gateway works properly16:32
hemnaso I'm not sure how much effort it'd take to do the CI side of things16:32
hemnaif someone is familiar with the existing ceph CI, I could help them on the iscsi gw setup16:32
hemnafor CI16:32
jungleboyjWe have automation in Lenovo that I think does some of that.16:33
jungleboyjI wonder if we can help with that.16:33
hemnaI had to manually update my 7 ubuntu VMs to linux kernel 4.1816:33
smcginnisThat's going to be a big issue.16:33
hemna4.15 wasn't happy16:33
*** panda|off has quit IRC16:33
hemnaluckily it's an apt-get install16:34
hemnainstead of a compile16:34
hemnaso I'm hoping in the next day or so, to stabilize initialize_connection16:34
hemnait's still giving me fits16:34
*** panda has joined #openstack-meeting16:35
hemnathe rbd-target-api is a bit compilicated in what it needs done at certain times.16:35
hemnaanyone wants to help with the CI side of things I'd appreciate it16:35
hemnabut at least the driver is possible at this point still.  so I'm hopeful16:36
jungleboyjhemna:  Ok.  Let me see if there is anything we have from the iSCSI work we did previously in Lenovo.16:36
jungleboyjWill get back to you.16:36
jungleboyjhemna:  Hopeful is good!16:36
hemnaI'll keep updating the driver review with code as I go along16:37
jungleboyjhemna:  Anything else?16:37
hemnathat's it.16:37
jungleboyjCool.  Thank you for the update.16:37
eharneyi assume the CI work would involve adding a new mode to devstack-plugin-ceph?16:37
geguileohemna: thanks for the update and the work!16:37
jungleboyjgeguileo: ++16:38
hemnaeharney: yah I'm assuming so16:38
hemnainstalling all the required ceph-iscsi packages16:38
hemnaand setting up the rbd-target-gw16:38
hemnaand installing the rbd-target-api16:38
hemnaI documented as much as I could in the etherpad16:39
*** panda has quit IRC16:39
hemnageguileo: np.  I'd really love to get this working and in cinder.16:40
jungleboyjhemna: ++16:40
jungleboyjOk.  That was all we had for topics this week.16:40
jungleboyj#topic Open Discussion16:40
*** openstack changes topic to "Open Discussion (Meeting topic: Cinder)"16:40
whoami-rajatI've something that was brought up yesterday16:40
eharneyi'd love to get lvm multiattach fixed in stable:
hemnaeharney: ++16:42
whoami-rajattempest is capping its api-extensions in devstack [1] that is blocked by cinder as we "mistakely" removed an extension in a MV bump which wasn't backward compatible. i've a patch up for it, will appreciate some reviews on it.
jungleboyjeharney:  Ok, will watch those and get them through.16:43
smcginnisgeguileo: Do we still need to sort out this whole mess?
eharneyi looked at the os-sch-hnt change and was fairly unclear on the details involved there16:44
*** bnemec has quit IRC16:44
geguileosmcginnis: not sure...16:44
smcginniseharney: Which part?16:44
eharneysmcginnis: i think e0ne was going to follow up on syncing scheduler stats from the ptg, which i think is the same area that spec is about16:45
geguileosmcginnis: I mean, the issue is still there, that's for sure16:45
smcginnisOh right, forgot about that from the PTG.16:45
jungleboyjeharney: ++16:45
*** haleyb has quit IRC16:46
smcginnisWasn't sure if that spec should be abandoned or not. Sounds like it should be.16:46
whoami-rajateharney:  i replied to your comment there, hope it helps.16:46
geguileosmcginnis: probably a good idea to abandon it for now...16:46
e0neI need to  read Tommy's spec16:46
smcginnise0ne: I think he had three different ones out there at one point trying to get opinions on different approaches.16:47
*** panda has joined #openstack-meeting16:48
jungleboyj:-)  That is one way to do it.16:48
jungleboyjOther topics for today?16:50
jungleboyjDoesn't sound like it ...16:51
jungleboyjOk.  So lets wrap this up.16:52
jungleboyjThanks everyone for joining and for continuing to work on Cinder.16:52
*** openstack changes topic to "OpenStack Meetings ||"16:52
openstackMeeting ended Wed Jun  5 16:52:54 2019 UTC.  Information about MeetBot at . (v 0.1.4)16:52
*** woojay has left #openstack-meeting16:52
openstackMinutes (text):
*** dviroel has left #openstack-meeting16:53
m5z_|mszwed|bye :)16:53
*** e0ne has quit IRC16:53
*** ekcs has joined #openstack-meeting16:55
*** m5z_|mszwed| has left #openstack-meeting16:55
*** davidsha has quit IRC17:00
*** rosmaita has left #openstack-meeting17:03
*** hberaud is now known as hberaud|gone17:18
*** iyamahat has joined #openstack-meeting17:27
*** ralonsoh has quit IRC17:28
*** _hemna has joined #openstack-meeting17:31
*** ociuhandu has joined #openstack-meeting17:33
*** iyamahat has quit IRC17:34
*** ociuhandu_ has quit IRC17:36
*** haleyb has joined #openstack-meeting17:37
*** ociuhandu has quit IRC17:39
*** akhil_jain has quit IRC17:40
*** yamahata has joined #openstack-meeting17:45
*** yamamoto has joined #openstack-meeting17:48
*** iyamahat has joined #openstack-meeting17:51
*** yamamoto has quit IRC17:53
*** tesseract has quit IRC17:57
*** _hemna has quit IRC18:02
*** ankita-2798 has joined #openstack-meeting18:08
*** enriquetaso has quit IRC18:17
*** enriquetaso has joined #openstack-meeting18:17
*** thgcorrea has quit IRC18:19
*** e0ne has joined #openstack-meeting18:20
*** ricolin has quit IRC18:41
*** tidwellr has quit IRC18:54
*** ociuhandu has joined #openstack-meeting19:02
SotKanyone around for the storyboard meeting?19:02
SotK#startmeeting storyboard19:03
openstackMeeting started Wed Jun  5 19:03:05 2019 UTC and is due to finish in 60 minutes.  The chair is SotK. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:03
*** openstack changes topic to " (Meeting topic: storyboard)"19:03
openstackThe meeting name has been set to 'storyboard'19:03
SotK#link Agenda19:03
SotK#topic Migration Updates19:03
*** openstack changes topic to "Migration Updates (Meeting topic: storyboard)"19:03
SotKI don't think there's been anything new this week right?19:04
diablo_rojoNo negative feedback.. or any feedback for that matter from Swift19:04
diablo_rojoNothing new19:04
SotKI guess we just give them a bit more time for now?19:04
fungiyeah, wouldn't rush it19:04
notmynamethe swift team meeting is today. it should be raised there for people to offer comments19:05
notmyname(in about 3 hours)19:05
notmynamesorry, in 2 hours19:05
fungigetting feedback isn't time-sensitive, they should take all the time they need to try stuff out19:06
*** priteau has quit IRC19:06
diablo_rojoYeah I agree19:06
diablo_rojoDefinitely not rushing19:07
diablo_rojoMore just noting that there isnt any yet.19:07
*** priteau has joined #openstack-meeting19:08
SotK#topic Release Progress19:08
*** openstack changes topic to "Release Progress (Meeting topic: storyboard)"19:08
SotKso I think we decided on most of the things we needed to after the meeting last week19:09
diablo_rojoWhat are the next steps?19:09
fungiwell, a recap of that decision would help too19:09
diablo_rojoOh yeah19:09
*** ociuhandu has quit IRC19:09
diablo_rojofor logging purposes19:09
fungii mean, it's in the #storyboard channel logs, but for posterity having it mentioned in the meeting would be great19:10
diablo_rojoSO I think we decided on storyboard-api for pypi?19:10
fungithat matches my recollection19:10
SotK#info we'll rename the python package to storyboard-api19:10
fungiwhich i think just needs a minor update to the existing patch?19:10
SotK#info we'll number the first release 1.0.019:11
fungii can do that unless someone has already started19:11
diablo_rojoAnd someday...might rename the storyboard repo to storyboard-api19:11
diablo_rojofungi, go for it :)19:11
diablo_rojoI haven't touched it.19:11
SotKme neither19:11
fungii'll check with tonyb first to see if he wants to19:12
fungisince it is his patch19:12
fungii'll leave a review comment real quick at least19:12
SotKwe didn't firmly decide on when to do a release19:12
SotKbut I think we should just do it when we've finished planning what we need to do to do a release19:12
fungithere was something you wanted merged first... the attachments implementation? security teams?19:13
fungior we could make those 1.1.0 et cetera19:13
fungiand just release as soon as the dist name is updated19:13
SotKyeah I mentioned attachments, but I ended up preferring the idea of "here's 1.1.0, now with attachments!"19:13
diablo_rojoYeah I think we decided early and often?19:14
fungibasically the process (once we're using an available dist name) is to make a 1.0.0 signed tag and push it to gerrit19:14
fungioh, we needed to add jobs ;)19:14
fungii'll check into what jobs we're missing for release automation19:15
SotKnice, thanks19:15
fungiwith the correct jobs added we'll upload an sdist and a wheel to pypi automatically each time a new tag is pushed to gerrit19:15
SotKI think that adding jobs is the only other thing we need to do then19:16
fungiyep, i concur19:17
diablo_rojoSounds pretty easy19:17
SotKon a related note, what about webclient releases?19:17
fungii may also push a manual build to just to make sure the package metadata isn't going to be rejected by warehouse19:17
SotKthat sounds like a good idea19:18
fungistoryboard-webclient will need different sorts of jobs, presumably19:18
fungii know less about javascript, but i believe we do have some js-based projects doing automatic releases to npm, if that's where it makes sense19:19
SotKyep, we'll want jobs to upload to npm I expect19:19
*** panda has quit IRC19:19
SotKI'm not totally sure if that makes sense, but will look into being more sure19:19
fungii can probably work out what those are using to accomplish that, but less sure how to safely test that it'll work ahead of time and not sure what sorts of package registration we need to do19:19
fungimordred might have ideas there too19:20
SotKalso, do we want to keep version numbers in sync and release them simultaneously?19:20
diablo_rojoDo we want to to outline some actions for logging's sake?19:20
SotKmy initial feeling is "not really"19:20
*** panda has joined #openstack-meeting19:20
fungii would not try to sync releases19:20
diablo_rojoI would agree with the not really19:20
fungirelease them whenever makes sense for each project19:21
diablo_rojoI feel like there will be more stuff in the api we want to/need to release than in the webclient19:21
SotK#action SotK to decide if npm makes sense as a place to release the webclient, and what it entails19:21
fungiand if the demo docker image is something we think is useful, i believe we have jobs which could build that and publish to dockerhub too19:21
SotK#action fungi to investigate what jobs we are missing for api releases19:22
diablo_rojoThat would be cool.19:23
*** lpetrut has joined #openstack-meeting19:23
diablo_rojo(the docker image)19:23
diablo_rojoThough I dont think its a priority19:23
SotK+1, but I'm not sure it actually exists yet19:23
SotKit would definitely be useful, but we can probably wait for an updated version of
SotK#topic Forum + PTG Summary19:25
*** openstack changes topic to "Forum + PTG Summary (Meeting topic: storyboard)"19:25
SotK#link Summary email19:26
diablo_rojoSo did all the stories we have on the etherpad get added?19:27
diablo_rojoI know you were working on that Friday19:27
diablo_rojoI didnt have time to circle back19:27
SotK#link PTG Etherpad19:27
*** lpetrut has quit IRC19:27
diablo_rojoYeah that etherpad :)19:27
SotKI think there are still a couple of story-less things19:27
SotKwe should do as the agenda suggests and go through tagging things and creating the last couple of stories19:28
SotKat some point19:28
SotKthe missing ones are "Integration tests", "Search is slow", and "Archive tasks/stories"19:29
diablo_rojoSotK, I feel like we should schedule a meeting..19:30
SotKheh, that's probably a good idea19:31
diablo_rojoWhats the rest of your week look like?19:31
diablo_rojoMy Friday is very open.19:31
diablo_rojoAnywhere from like.. 15:00 UTC onward19:32
SotKanything after 16:00 UTC works for me tomorrow or Friday19:32
diablo_rojoLets do like.. 17 UTC on Friday19:33
diablo_rojowe can use my zoom19:33
diablo_rojofor those interested in participating19:34
diablo_rojoI'm sure it will be thrilling19:34
ankita-2798diablo_rojo, what is the agenda for the meeting?19:35
diablo_rojoOr for Friday?19:37
diablo_rojoWhich meeting? lol19:37
diablo_rojothe wiki link is for the meeting now19:38
diablo_rojoSotK, do I need to make an invite?19:38
ankita-2798the one you are planning for Friday19:38
diablo_rojoOr you just want to write it down19:38
SotKif you like, I've added it to my calendar already though :)19:38
diablo_rojoankita-2798, its just to finish a triage of the active stories in the storyboard project group that we started at the Project Team Gathering a few weeks ago19:39
diablo_rojoSotK, if you dont need one I wont ;)19:39
ankita-2798Oh, okay19:39
SotKanything else on this?19:40
ankita-2798No, thank you :)19:41
diablo_rojoNone from me19:42
SotK#topic In Progress Work19:42
*** openstack changes topic to "In Progress Work (Meeting topic: storyboard)"19:42
diablo_rojoDid we ever get mkarray's work merged?19:42
* SotK reviewed it and left some comments19:43
SotKmostly just some things that I'd like to neaten up before we merge them19:43
diablo_rojoSotK, not sure he is around much anymore.19:44
diablo_rojoI can take a look and update based on your comments and then you can merge it?19:44
SotKme neither, I noted in the reviews that I can make the fixes if he doesn't have time, and was planning to do so if I didn't hear anything19:44
SotKbut feel free to beat me to it :)19:44
fungior can always add a followup change with the suggested improvements and approve them both at the same time if that's more palatable19:44
SotKeither works for me, there was nothing too problematic in them19:45
*** slaweq has quit IRC19:47
SotKdiablo_rojo: do you have a preference?19:47
*** slaweq has joined #openstack-meeting19:47
*** artom has quit IRC19:48
diablo_rojoI'll just go make the changes and ping you when I have the patchset up19:48
SotKok, sounds good19:48
SotKalso, thanks for reviewing the security teams stuff :)19:48
fungii'm almost through the api side of that stack as well19:48
fungishould hopefully see it merged by the end of the day19:49
SotKexcellent, thanks19:49
SotKthe issues that diablo_rojo noted on the webclient side of that should go away once the api side is deployed on storyboard-dev too I think19:50
fungiawesome, and yeah that's why i started on the api stack19:50
SotKI'll try to continue getting through my review/rework backlog19:50
diablo_rojoSo excited :)19:51
SotKit would also be spectacular to merge
SotKI think that should help reduce the complexity of that 3 minute long query19:52
fungiyes indeed19:52
fungithanks for the reminder19:52
SotKsame goes for too, but that query is a bit less bad to start with19:53
SotKin fact, that isn't much better19:53
SotKbut its a bit better at least19:53
* diablo_rojo opens tabs19:54
diablo_rojo(5 min left)19:54
SotKI think that's everything I have to mention for in progress work19:55
SotKanyone else?19:55
fungiankita-2798 likely will want to track 643323 and 643303 since that may alter some of the queries in the slow query log data she asked about in #storyboard earlier19:56
diablo_rojoGood point19:56
fungiwe can also grab a fresh log after those are in place and see if they made a difference19:56
ankita-2798Regarding the Search Improvement, I have been currently going through the storyboard's backend's codebase, learning the frameworks etc. I am yet to study the logs provided by corvus.19:57
ankita-2798fungi, yeah I already took a note of these reviews :)19:57
*** brault has quit IRC19:58
*** _hemna has joined #openstack-meeting19:59
*** jamesmcarthur has quit IRC19:59
SotKand with that we're out of time, thanks for coming folks!20:00
*** openstack changes topic to "OpenStack Meetings ||"20:00
openstackMeeting ended Wed Jun  5 20:00:08 2019 UTC.  Information about MeetBot at . (v 0.1.4)20:00
openstackMinutes (text):
fungithanks SotK!20:00
diablo_rojoThanks SotK!20:01
ankita-2798Thank you!20:08
*** ankita-2798 has quit IRC20:13
*** radeks_ has quit IRC20:29
*** _hemna has quit IRC20:33
*** pcaruana has quit IRC20:59
*** tdasilva has joined #openstack-meeting21:00
timburke_#startmeeting swift21:01
openstackMeeting started Wed Jun  5 21:01:49 2019 UTC and is due to finish in 60 minutes.  The chair is timburke_. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** openstack changes topic to " (Meeting topic: swift)"21:01
openstackThe meeting name has been set to 'swift'21:01
timburke_who's here for the swift meeting?21:02
*** _hemna has joined #openstack-meeting21:03
*** brault has joined #openstack-meeting21:03
timburke_i forgot the update the agenda to reflect the actual state of what we need to discuss, but the broad topics are right21:03
timburke_#topic migration to story board21:04
*** openstack changes topic to "migration to story board (Meeting topic: swift)"21:04
timburke_who's had a chance to play around in the storyboard sandbox?21:04
mattoliverauOpps, I was meaning to play with the sandbox.. but didn't.21:04
* diablo_rojo lurks21:05
mattoliverauOpps did I just say that out loud :p21:05
timburke_diablo_rojo, well, i've got some feedback :-)21:06
timburke_responsiveness is a bit of a problem. 10-12s to load a story and 14-15s to load the first 10 active stories for a project? launchpad has its own issues, but i don't recall it being *this* bad21:06
timburke_being able to have **bold**, *italics*, and `code` is nice. i can especially see the ability to have code blocks being good for tracebacks and curl output, for instance21:07
diablo_rojotimburke_, we set up a slow log query and are starting to look over it to make improvements on loading times21:07
timburke_(iirc, launchpad would lose all the indents for tracebacks)21:07
diablo_rojoand by 'we' I mean corvus :) Thanks corvus :)21:07
timburke_applying styling to migrated stories is an interesting choice -- i maybe would've put everything in code blocks to preserve the monospaced formatting that launchpad does (again, thinking about tracebacks and sample output), but i could see arguments either way21:07
timburke_being able to get to a project's resolved stories quickly is good. finding a related (but closed) issue is definitely one of the more annoying things about launchpad IMO21:08
*** patchbot has joined #openstack-meeting21:08
*** brault has quit IRC21:08
timburke_search field could use some help text; what operators do i get? how do i combine them? as a result, finding all stories that i'm subscribed to (for example) is not obvious21:08
timburke_on the stories search, it's not clear what projects are in play for a given story; i have to click through to the story, which is worsened by the responsiveness problems21:08
timburke_would be nice if i could specify a default set of filters when i go to the story list; "all open stories, across all projects, sorted by most-recently updated" is unlikely to be right for anyone21:08
timburke_sorry, that was a bunch all at once :-)21:08
diablo_rojotimburke_, you can set up an automatic worklist with those default filter criteria21:09
diablo_rojotimburke_, happy to have feedback :)21:09
timburke_cool! i hadn't gotten around to messing with worklists -- i just knew that i wanted to go looking for some stories, so i clicked on "stories" :-)21:09
diablo_rojoIf its a common set of criteria you will go back to repeatedly I would make a worklist21:10
diablo_rojoan automatic one21:10
*** priteau has quit IRC21:10
timburke_for me, the two biggest things would be "open stories for these projects" and "stories i'm subscribed to"21:11
tdasilvais a worklist a global/public list or owned/visible by user?21:12
timburke_with the latter maybe getting split into "in this set of projects that i have a lot of interest in" and "outside of that set"21:12
diablo_rojothey are public but they are owned by the person that creates them. Other can subscribe to them but I think you need to add people to them if they are going to make changes to the worklist.21:12
diablo_rojoIf there are private things in the worklist, sb is smart and wont show the user if they dont have the correct permissions21:13
timburke_"stories/tasks assigned to me" might also be useful, but i feel like at that point i'm more likely to be thinking in terms of reviews and looking to gerrit instead21:13
diablo_rojotimburke_, you should be able to see that on your dashboard21:13
timburke_makes sense21:14
mattoliverauInterestingly we might be able to have worlists for things like py3 migration and maybe priority reviews.21:14
diablo_rojostories and tasks you created as well21:14
diablo_rojomattoliverau, yep :) and you could put that all in a board if you wanted or have them exist separately21:14
diablo_rojoDepends on how you want to view the info21:14
diablo_rojoand organize yourselves21:15
timburke_py3 seems like it'd be its own story, with a (likely large) number of tasks to do the porting and testing21:15
timburke_i think?21:15
diablo_rojoCould be done either way.21:15
diablo_rojoDepends on how granular you want to get I suppose.21:16
*** dmsimard has quit IRC21:16
*** dmsimard8 has joined #openstack-meeting21:16
*** dmsimard8 is now known as dmsimard21:16
diablo_rojoLooking at your wiki of priority reviews.. I might lean towards a worklist21:16
timburke_are there guidelines on what makes sense as a story vs as a task? or is the expectation that teams will figure out what works for them?21:16
diablo_rojoand then have a story for each of the py3fun tests, a story for middleware, and a story bor 'obj'21:17
diablo_rojoand then the tasks would be the patches under each of those larger topics21:17
diablo_rojoMake sense?21:17
timburke_i think so21:17
diablo_rojoA task is the actual change in the repo. A story is the more general thing to get done21:18
diablo_rojoSo like.. if I had a new feature I would make a story for it and the tasks would be like.. a task for the cli update and another for the api change21:18
diablo_rojoAnd if you did docs or tests as separate patches you could have a task for each of those too.21:18
diablo_rojoIf you wanted to do a release right after that you could also make a task associated with the releases repo in that story21:19
diablo_rojoso that its all together in one place21:19
diablo_rojoAny other questions atm? :)21:20
timburke_did anyone else have comments of questions for diablo_rojo?21:20
diablo_rojoIf you think of them later come bother us in #storyboard :)21:20
timburke_cool, thanks diablo_rojo!21:21
timburke_#topic libec21:21
*** openstack changes topic to "libec (Meeting topic: swift)"21:21
timburke_it's under openstack/ again!21:21
timburke_new release synced over to just fine21:22
timburke_i might poke at to pick it up21:22
timburke_in light of the impending
patchbotpatch 662615 - swift - Installing liberasurecode from Alpine Linux repos ... - 3 patch sets21:23
timburke_we still owe the quadiron guys some reviews :-/21:23
timburke_and i still need to follow up with the libphazr guys about whether they'd get broken by some of the proposed changes, and how we'd know without a gate job21:24
timburke_but... that'll probably be later, because we've got other priorities!21:25
timburke_#topic py321:25
*** openstack changes topic to "py3 (Meeting topic: swift)"21:25
timburke_i got some good comments on the ssync patch; pushed up a new patchset this morning21:26
patchbotpatch 660542 - swift - py3: port ssync - 5 patch sets21:26
timburke_got the memcache fixup at
patchbotpatch 662115 - swift - Fix up how we memcache on py3 - 2 patch sets21:26
timburke_that's going to be needed for tempurl
patchbotpatch 652928 - swift - py3: Port the tempurl middleware - 5 patch sets21:27
*** rcernin has joined #openstack-meeting21:27
timburke_on top of *that*, i've started working on getting func tests running under py2 passing against services running under py321:27
timburke_nothing in terms of a gate job just yet, but so far things are really promising!21:28
timburke_there were two spots of trouble i hit: first was non-ascii header names21:29
timburke_which led to
patchbotpatch 662546 - swift - py3: Stop truncating response headers - 1 patch set21:29
timburke_(see for one of the tests that exercises that -- and note that it already has a `if tf.web_front_end == 'integral':` guard)21:30
timburke_the other is something i happened to hit because i was using an EC policy by default -- apparently there's some bad interaction between SegmentedIterable and ECAppIter that trips a `ValueError: generator already executing` when closing iters at the end of the response21:32
timburke_still not sure what's going on there, but it doesn't happen on py2 :-/21:33
timburke_while trying to characterize that, i found
openstackLaunchpad bug 1831790 in OpenStack Object Storage (swift) "Multi-range GET of DLO returns bad data" [Undecided,New]21:34
timburke_and proposed to fix it21:34
patchbotpatch 663403 - swift - dlo: Respond 200 on multi-range GETs - 1 patch set21:34
timburke_apparently we never really intended to be able to do multi-ranged gets on DLOs21:35
timburke_i think that's about all the progress i've got -- mattoliverau, zaitcev, anything to add?21:36
*** _hemna has quit IRC21:36
mattoliverauNice summary, nothing to add for me. I'll go look at the memcache one to hopefully unblock tempurl21:37
*** enriquetaso has quit IRC21:38
timburke_mattoliverau, anything else you'd like before landing ?21:38
patchbotpatch 662294 - swift - py3: symlink follow-up - 2 patch sets21:38
mattoliveraunope, I'm happy with it.21:40
timburke_yay, more py3 func tests!21:40
timburke_#topic lots of small files21:41
*** openstack changes topic to "lots of small files (Meeting topic: swift)"21:41
timburke_rledisez, kota_, how's it going?21:41
rledisezno real moves from ovh side. last there were a holiday and alex is sick these days21:42
rledisez*last week21:42
mattoliverautimburke_: +A'ed21:42
timburke_thanks mattoliverau21:42
timburke_i saw kota_ proposed a merge from master, which is great. just approved21:43
kota_but not yet have time to look at alex's test improvement sorry21:45
*** gmann has joined #openstack-meeting21:45
timburke_is there any particular order we should look at things on ?21:45
kota_let me check21:46
timburke_i know there are some unit test patches that conflict; which should we try to land first? i might make sure they can run under py3 ;-)21:46
kota_i think, and are easy and able to be reviewed21:47
patchbotpatch 660381 - swift (feature/losf) - Add tests for vfile_utils - 1 patch set21:47
patchbotpatch 659515 - swift (feature/losf) - Add small unit tests for vfile and related modules - 2 patch sets21:47
timburke_cool! sounds good21:47
kota_Alex's improvement starts from ... not sure, but probably we need to know what exactly problem is21:48
patchbotpatch 659254 - swift (feature/losf) - In _get_vfile(), handle the case when a referenced... - 1 patch set21:48
kota_I'll try to catch up those.21:49
timburke_fwiw, notmyname got me excited about this over lunch yesterday -- reminded me that losf is giving us a model for how we can have more experimentation in the backend, and that getting really opens up the scope of what kinds of experiments would be possible21:50
patchbotpatch 427911 - swift - Replace MIME with PUT+POST for EC and Encryption - 37 patch sets21:50
timburke_after py3, i'm fairly certain these should be the priority21:52
*** slaweq has quit IRC21:52
kota_thanks a lot21:52
timburke_#topic swift 2.22.0 release21:52
*** openstack changes topic to "swift 2.22.0 release (Meeting topic: swift)"21:52
kota_i know py3 is the top priority.21:52
timburke_speaking of... i'd like to cut a release shortly after the py3 unit tests are ported21:53
timburke_i maybe would've liked to have func tests, too, but i think we can get ourselves confident enough for "experimental" py3 support by running func tests manually under py221:54
kota_sounds reasonable to me21:55
timburke_in light of that plan, what *else* should be getting in? anyone have patches they think would be good to land concurrent with the py3 work?21:55
mattoliverauexperimental py3 release would be exciting, and the distros would love to see that we've made that kind of porgress.21:55
timburke_(alternatively, does anyone feel that this is a terrible plan and premature; we need to get func tests *first*?)21:55
mattoliverauWell I'd like func tests, but if we can somehow do the py2 func to a py3 then I'm happy with that.21:57
timburke_well, keep thinking about both what other patches we'd want for a release, and what we can do to feel more confident in the eventual (experimental) py3 support :-)21:58
timburke_the sooner we can get the experimental release out, the more confidence we can have when we have for the *next* release when we say we *really* support it21:59
timburke_we're about at time21:59
timburke_thank you all for coming, and thank you for working on swift!21:59
*** openstack changes topic to "OpenStack Meetings ||"21:59
openstackMeeting ended Wed Jun  5 21:59:45 2019 UTC.  Information about MeetBot at . (v 0.1.4)21:59
openstackMinutes (text):
*** whoami-rajat has quit IRC22:00
*** patchbot has left #openstack-meeting22:00
mattoliverauthanks timburke_22:00
*** slaweq has joined #openstack-meeting22:02
*** manjeets has joined #openstack-meeting22:03
*** rcernin has quit IRC22:04
*** slaweq has quit IRC22:08
*** manjeets has quit IRC22:12
*** e0ne has quit IRC22:13
*** yamamoto has joined #openstack-meeting22:46
*** tdasilva has quit IRC22:53
*** raildo has quit IRC22:58
*** artom has joined #openstack-meeting23:09
*** carloss has quit IRC23:21
*** _hemna has joined #openstack-meeting23:33
*** ykatabam has joined #openstack-meeting23:42
*** ykatabam has quit IRC23:48
*** slaweq has joined #openstack-meeting23:48
*** yamamoto has quit IRC23:48
*** bobh has joined #openstack-meeting23:56
*** ykatabam has joined #openstack-meeting23:58

Generated by 2.15.3 by Marius Gedminas - find it at!