Wednesday, 2019-04-10

*** mattw4 has quit IRC00:03
*** armax has joined #openstack-meeting00:10
*** tetsuro has joined #openstack-meeting00:14
*** lseki has quit IRC00:34
*** lbragstad has quit IRC00:45
*** yamamoto has joined #openstack-meeting00:48
*** yamamoto has quit IRC00:51
*** yamamoto has joined #openstack-meeting00:58
*** tetsuro has quit IRC00:58
*** yamamoto has quit IRC01:03
*** gyee has quit IRC01:03
*** whoami-rajat has joined #openstack-meeting01:12
*** mriedem has quit IRC01:18
*** Liang__ has joined #openstack-meeting01:18
*** jamesmcarthur has joined #openstack-meeting01:20
*** jamesmcarthur has quit IRC01:23
*** Liang__ is now known as LiangFang01:25
*** yamahata has quit IRC01:27
*** iyamahat has quit IRC01:27
*** yamamoto has joined #openstack-meeting01:47
*** ijw has quit IRC02:06
*** hongbin has joined #openstack-meeting02:29
*** enriquetaso has joined #openstack-meeting02:33
*** yamamoto has quit IRC02:40
*** yamamoto has joined #openstack-meeting02:41
*** psachin has joined #openstack-meeting03:00
*** mmethot has quit IRC03:09
*** mmethot has joined #openstack-meeting03:09
*** enriquetaso has quit IRC03:14
*** armax has quit IRC03:17
*** ricolin has joined #openstack-meeting03:31
*** hongbin has quit IRC03:42
*** sridharg has joined #openstack-meeting04:04
*** imsurit has joined #openstack-meeting04:05
*** JangwonLee has joined #openstack-meeting04:21
*** diablo_rojo has quit IRC04:29
*** yamamoto has quit IRC04:57
*** tetsuro has joined #openstack-meeting04:59
*** pcaruana has joined #openstack-meeting05:06
*** yamamoto has joined #openstack-meeting05:07
*** yamamoto has quit IRC05:10
*** yamamoto has joined #openstack-meeting05:10
*** browny has quit IRC05:17
*** Luzi has joined #openstack-meeting05:17
*** ricolin has quit IRC05:30
*** sidx64 has joined #openstack-meeting05:43
*** yamamoto has quit IRC05:49
*** yamamoto has joined #openstack-meeting05:50
*** yamahata has joined #openstack-meeting06:00
*** vishalmanchanda has joined #openstack-meeting06:04
*** kopecmartin|off is now known as kopecmartin06:10
*** janki has joined #openstack-meeting06:19
*** yamamoto has quit IRC06:26
*** yamamoto has joined #openstack-meeting06:27
*** e0ne has joined #openstack-meeting06:28
*** ijw has joined #openstack-meeting06:29
*** apetrich has joined #openstack-meeting06:30
*** yamamoto has quit IRC06:32
*** ralonsoh has joined #openstack-meeting06:36
*** yamamoto has joined #openstack-meeting06:38
*** yamamoto has quit IRC06:47
*** yamamoto has joined #openstack-meeting06:48
*** e0ne has quit IRC06:48
*** liuyulong_ has joined #openstack-meeting06:50
*** rubasov has left #openstack-meeting06:55
*** e0ne has joined #openstack-meeting06:57
*** slaweq has joined #openstack-meeting07:00
*** tssurya has joined #openstack-meeting07:26
*** psachin has quit IRC07:32
*** e0ne has quit IRC07:33
*** pcaruana has quit IRC07:34
*** pcaruana has joined #openstack-meeting07:35
*** psachin has joined #openstack-meeting07:35
*** yamamoto has quit IRC07:37
*** yamamoto has joined #openstack-meeting07:38
*** e0ne has joined #openstack-meeting07:40
*** lpetrut has joined #openstack-meeting07:41
*** boxiang has quit IRC07:45
*** boxiang has joined #openstack-meeting07:46
*** e0ne has quit IRC07:48
*** e0ne has joined #openstack-meeting07:53
*** yamamoto has quit IRC07:56
*** priteau has joined #openstack-meeting08:05
*** yamamoto has joined #openstack-meeting08:11
*** Luzi has quit IRC08:21
*** yamamoto has quit IRC08:22
*** jrbalderrama has joined #openstack-meeting08:23
*** ttsiouts has joined #openstack-meeting08:27
*** ricolin has joined #openstack-meeting08:30
*** e0ne has quit IRC08:47
*** liuyulong_ has quit IRC08:50
*** yamamoto has joined #openstack-meeting08:54
*** e0ne has joined #openstack-meeting08:58
*** ijw has quit IRC09:05
*** LiangFang has quit IRC09:05
*** e0ne has quit IRC09:06
*** ttsiouts has quit IRC09:18
*** ttsiouts has joined #openstack-meeting09:19
*** ttsiouts has quit IRC09:23
*** tetsuro has quit IRC09:24
*** Lucas_Gray has joined #openstack-meeting09:25
*** electrofelix has joined #openstack-meeting09:28
*** yamamoto has quit IRC09:28
*** Lucas_Gray has quit IRC09:31
*** Lucas_Gray has joined #openstack-meeting09:34
*** ociuhandu has quit IRC09:35
*** imsurit has quit IRC09:43
*** imsurit has joined #openstack-meeting09:44
*** rcernin has quit IRC09:47
*** boxiang has quit IRC09:52
*** ygbo has joined #openstack-meeting09:52
*** boxiang has joined #openstack-meeting09:53
*** ttsiouts has joined #openstack-meeting09:57
*** yamamoto has joined #openstack-meeting09:58
*** yamamoto has quit IRC10:01
*** yamamoto has joined #openstack-meeting10:01
*** yamamoto has quit IRC10:05
*** yamahata has quit IRC10:05
*** ttsiouts has quit IRC10:07
*** verdurin has left #openstack-meeting10:07
*** verdurin has joined #openstack-meeting10:08
*** hyunsikyang has quit IRC10:14
*** tssurya has quit IRC10:31
*** yamamoto has joined #openstack-meeting10:44
*** erlon has joined #openstack-meeting10:48
*** yamamoto has quit IRC10:50
*** oneswig has joined #openstack-meeting10:58
oneswig#startmeeting scientific-sig10:59
openstackMeeting started Wed Apr 10 10:59:59 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
oneswig#link Agenda for today
oneswigHey arne_wiebalck, thanks for joining11:00
oneswigHi priteau11:00
*** dtantsur has joined #openstack-meeting11:01
*** mgoddard has joined #openstack-meeting11:01
oneswigHi dtantsur mgoddard - welcome11:02
*** janders has joined #openstack-meeting11:02
mgoddardhi, thanks11:02
oneswigOK lets kick off with the agenda11:02
oneswig#topic Ironic and external DCIM11:03
*** openstack changes topic to "Ironic and external DCIM (Meeting topic: scientific-sig)"11:03
oneswigThanks Arne for bringing the discussion this way.11:03
arne_wiebalckThat's a long standing issue here at CERN.11:04
oneswigCan you summarise what your needs are?11:04
arne_wiebalckWe have compiled a doc with all details:
arne_wiebalckIn short, we need to keep track of the servers in our DC.11:05
arne_wiebalckLife cycle, but also for campaigns.11:05
arne_wiebalckThink f/w upgrades.11:05
arne_wiebalckWe have a DB for this, but keeping it up to date is diffcult.11:06
arne_wiebalckironic provides some means to gather data about hosts, so we were wondering whether this could be leveraged.11:06
*** ttsiouts has joined #openstack-meeting11:06
dtantsuris it enough to have a link in ironic to some external system? or do you mean inspection integration?11:07
arne_wiebalckFor now, we were wondering how other sites deal with this issue and what tools they use.11:07
arne_wiebalckthe issue with inspection is that it happens only once11:07
oneswigIt's interesting because there's a clear precedent for this problem.11:07
arne_wiebalckironic would interface with some external system11:07
arne_wiebalckto store the data11:07
oneswigIn other sites I'm aware of, there's openDCIM (used by the DC guys) and XCAT for the infrastructure provisioning (non-OpenStack)11:08
arne_wiebalckmain idea here is that others have already thought about a schema, for instance11:08
*** tssurya has joined #openstack-meeting11:08
oneswigNow those sites also have Ironic to deal with as a third source of truth.11:08
arne_wiebalckyeah, different sources of truth is also an issue11:08
arne_wiebalckI have a list of 8 or so tools that we will have a look at.11:09
jandersis monitoring baremetal node health of interest in this context, or do you do this using a different tool?11:10
arne_wiebalckThe main idea being to use these as potential backends to which ironic (or some additional tool) could send data.11:10
arne_wiebalckmonitoring is different, I'd say11:10
oneswigIn this model, the nodes and ports would no longer be stored in a local database?  Do you think everything could be delegated?11:10
arne_wiebalckthis is more like #cpus, disks, ... f/w version, ...11:10
arne_wiebalckoneswig: "local" you mean ironic's DB?11:11
*** simon-AS559 has joined #openstack-meeting11:11
arne_wiebalckI think this would be more like the sensor data ironic is gathering and sending to ceilometer11:11
dtantsurit sounds like you need to post results of introspection to some external database for reconciliation?11:11
dtantsurand maybe do it periodically out-of-band?11:12
arne_wiebalckdtantsur: yes11:12
*** e0ne has joined #openstack-meeting11:12
dtantsuryes to both?11:12
arne_wiebalckdtantsur: that sums it up11:12
arne_wiebalckdtantsur: yes11:12
dtantsurfun fact: we've just discussed downstream a possibility of periodic out-of-band mini-inspection11:12
mgoddardthere is a fine line here between monitoring and inspection11:12
arne_wiebalckperiodically, out-of-band, external system11:12
*** hearnsj has joined #openstack-meeting11:12
dtantsurnow, with ironic-inspector it's easy: we have processing hooks that can post data anywhere11:13
arne_wiebalckdtantsur: yes11:13
mgoddardwe'll probably want the results of out of band 'inspection' to also be pushed to a monitoring system11:13
dtantsurwhat we don't have is 1. out-of-band inspection hooks to post data anywhere, 2. a way to run out-of-band inspection periodically11:13
mgoddardit's just a question of which parts of the data they're interested in, and how frequently11:13
dtantsurthis sounds like two pretty orthogonal RFEs to me, I'm fine with both personally11:14
oneswigmgoddard: what kind of monitoring?11:14
arne_wiebalckdtantsur: concerning 2. what about the sensor data collection, isn't that similar?11:14
dtantsurarne_wiebalck: it's similar, except that inventory is not quite sensor data11:14
mgoddardoneswig: the equivalent of IPMI sensor data collection, I assume something similar exists for redfish11:14
dtantsurthe question is whether we want to represent inventory as part of sensor data or separately11:14
oneswigpower and environmentals via BMC channels?11:14
arne_wiebalckdtantsur: agreed, I was more thinking about the machinery/framework11:15
arne_wiebalckdtantsur: the sensor data contains what?11:15
dtantsurI've heard downstream that people want to collect sensor data much more (and order of magnitude?) often than inventory11:15
*** e0ne has quit IRC11:15
dtantsurarne_wiebalck: thermal data, etc11:15
dtantsurI can try finding an example11:15
jandersI am also very interested in baremetal health monitoring via out-of-band but agreed that's not necessary something for a DCIM system11:15
mgoddardthe line between these two things might be more of a site policy question than anything?11:16
*** erlon has quit IRC11:16
oneswigIt does sound separable, if not completely separate.11:16
dtantsuryeah, it may be a similar mechanism, but logically separate11:16
oneswigHardware inventory is a piece that could be focused on first11:16
jandersDCIM doesn't need to send notifications, it needs to answer queries11:16
oneswigAlthough mgoddard we certainly know people who want the monitorng11:17
arne_wiebalckDCIM may be more than what I had in mind initially (it'd add switches, racks, cabls, ...)11:17
jandersmonitoring is sort of the opposite in that sense11:17
dtantsurarne_wiebalck: looking at our example from IPMI I see power, voltage, POST errors, temperature readings, etc11:18
arne_wiebalckI guess there is also a thin line11:18
dtantsurthis is for sensors ^^11:18
arne_wiebalckdtantsur: thanks11:18
arne_wiebalckdtantsur: that is handled by our monitoring (and hence separate for us :-D)11:18
dtantsurwell, yeah. we need it from ironic :) but for IPMI it's an existing feature for some time.11:19
*** e0ne has joined #openstack-meeting11:19
arne_wiebalckI'm putting some hope into redfish for OOB inspection11:19
dtantsurI can help with the ironic side of this feature (well, two related features), we have interest in it11:20
jandersdtantsur: excellent! :)11:20
*** e0ne has quit IRC11:20
oneswigdtantsur: with inspection data & extra data, is that posted to Swift by Ironic?  Could that be made modular?11:20
arne_wiebalckoneswig: swift or a db11:20
dtantsuroneswig: it's only for ironic-inspector (in-band inspection)11:20
dtantsurand it is pluggable since Stein11:20
dtantsurwe also have pluggable hooks that run on inspection11:21
dtantsurbut again, it's all in-band. you cannot run it periodically on a live instance.11:21
dtantsur(well, unless you write an in-instance agent)11:21
arne_wiebalckthe alternative would be to require a h/w daemon on each instance11:21
arne_wiebalckdtantsur: :-D11:21
dtantsurright, this is something that we (as in ironic) are not very fond of doing, to be honest11:22
jandersare you aware of anyone using this (an agent inside the baremetal) in the wild?11:22
dtantsurwe've been trying to avoid touching running instances. doing that will need us to talk to neutron to understand networking, etc.11:22
arne_wiebalckI think Rackspace had sth like this.11:22
janderssounds crazy but maybe it's not that crazy11:22
dtantsurit's not crazy at all, it just doesn't seem to fit in ironic very well11:22
*** t0rrant has joined #openstack-meeting11:22
arne_wiebalckwell, that would be an ironic-independent approach11:23
dtantsuryou don't need ironic's help to do that. you can make such daemon just post data wherever you need11:23
oneswigWhat inventory data can be extracted from out-of-band inspection, using generic Redfish objects?11:23
dtantsuroneswig: essentially everything in theory11:23
jandershaving an optional agent gathering utilisation metrics and health information would be pretty cool11:23
dtantsurthe practice depends on a specific vendor, unfortunately11:23
jandersfor now running in baremetal means bye bye metrics11:23
dtantsurredfish is a very loose standard11:24
jandersor - could this be done out of band as well? I guess that'd be vendor specific11:24
arne_wiebalckoneswig: dtantsur : but in reality probably very different things11:24
dtantsurof course :(11:24
oneswigdtantsur: I think of it like SNMP, in that there is a common protocol but with useful data in vendor extensions.11:24
*** e0ne has joined #openstack-meeting11:24
dtantsurarne_wiebalck, oneswig, talk to etingof on #openstack-ironic, he's our local Redfish guru :)11:24
dtantsuroneswig: it's not THAT bad usually11:25
dtantsurit's just that literally everything in Redfish is optional11:25
oneswigdtantsur: thanks :-)11:25
dtantsuryou can have a compliant implementation with zero features11:25
dtantsurbut vendors do catch up, so it's rarely that bad in practice11:25
oneswigarne_wiebalck: you have a shortlist already, what's on it?11:26
*** yamamoto has joined #openstack-meeting11:26
arne_wiebalcka short list for things to read out, you mean?11:26
oneswigexternal dcims11:26
* arne_wiebalck getting the list11:27
dtantsurcheck e.g. this DMTF mockup of a Redfish server:
oneswigSeems like a reference implementation is readily achievable, which is great11:27
dtantsur(go into the available System, check e.g. Processors)11:27
dtantsur#link a redfish mockup to play with11:28
arne_wiebalcki-doit, CMDBuild, SnipeIT, SysAid, Spiceworks, GLPI, NetBox, xcat11:28
arne_wiebalckcompletely unfiltered ^11:28
mgoddardoneswig: you mentioned openDCIM earlier. Is that worth adding?11:28
oneswigI think so but I don't know how it works and what it can do for supporting integration11:29
arne_wiebalckwe'll start by having a look at these and see which of these make it on a short list by criteria such as licensing, maintained, storage needs, ...11:29
arne_wiebalck... APIs ...11:29
arne_wiebalckwell, that's the plan for now11:30
hearnsjopenDCIM is OK. Simple to set up11:30
arne_wiebalckhearnsj: added to my list, thx11:30
hearnsjI'm not an expert with commercial DCIM suites though11:30
oneswigHello hearnsj, welcome!11:31
hearnsjI have worked with openDCIM   ping me offline hearnsj@gamil.com11:31
arne_wiebalckhearnsj: thx!11:31
oneswigAPIs is probably a big differentiator given the implementors may not assume a machine-to-machine interface11:32
dtantsurno API - no integration :)11:32
arne_wiebalckyeah, probably a good thing to check early on11:32
oneswigI don't know how much useful lifecycle data XCat stores - that's not really it's mission AFAIK.11:33
oneswigWay back there was a project to integrate it with Ironic as a power driver...11:33
dtantsurwaaaay back :)11:34
jandersI think that died a horrible death, didn't it?11:34
jandersI never quite got the concept - was it more of an image-deployment driver?11:35
janderspower wise, not sure what would xcat add to the picture?11:35
dtantsurI barely remember it11:35
*** aloga has quit IRC11:35
oneswigI'm not sure either...11:36
*** aloga has joined #openstack-meeting11:36
oneswigWere there other candidates to suggest for arne_wiebalck ?11:37
arne_wiebalckif you have suggestions or input, please get in touch :)11:37
oneswigQuick response from UCam - "HI Stig, we've experimented with both of those, but still use Xcat mostly for a pseudo DCIM. But we're playing with netbox from DO now as a replacement to make Xcat less central, and also I know Sanger use Infloblox as their DHCP/DNS/IPAM solution."11:38
jandersInfoblox.. that's widely used in shops around town here11:38
*** sidx64 has quit IRC11:39
arne_wiebalcksome these tools have quite an emphasis on the networking ...11:39
arne_wiebalck.. not necessarily what we look for for our use case.11:40
oneswigOK, we should conclude this topic11:40
jandersAdd Infoblox IPAM agent image. The agent will listen for neutron and nova events and automatically manage DNS entries within an Infoblox appliance. The agent will be started when ‘infoblox’ is selected as the neutron_ipam_driver.11:40
dtantsurany action items from ironic side?11:40
jandersthat's right11:40
oneswigarne_wiebalck: will you follow up with your research?11:41
arne_wiebalckdefinitely :)11:41
jandersdtantsur: I would be very much interested in the out-of-band monitoring angle11:41
oneswigdtantsur: sounds like your hard work is already done :-) Thanks for that!11:41
oneswigarne_wiebalck: is there anything planned for forum or PTG on this?11:41
dtantsurmaybe we should sync off-channel re next ironic action items? or indeed at the forum/PTG?11:42
arne_wiebalckthere was a session two PTGs ago11:42
janders+1 for PTG11:42
oneswigI'll put this on the agenda again next week in the US timezone and try to gather a few more data points.11:42
arne_wiebalckdtantsur: sounds good!11:42
arne_wiebalckoneswig: thanks!11:42
dtantsurarne_wiebalck: wanna drive this process?11:42
arne_wiebalckdtantsur: yes11:42
dtantsurgreat, thanks!11:43
arne_wiebalckdtantsur: won't be at the ptg, though11:43
dtantsurwhat about the forum?11:43
arne_wiebalckdtantsur: neither11:43
dtantsurokay, asynchronous ways work just as well11:43
arne_wiebalcklol, sorry11:44
dtantsurno need to worry. I actually think it's better.11:44
oneswigGreat, thanks arne_wiebalck dtantsur and all, lets move on11:44
arne_wiebalckthx oneswig !11:44
oneswig#topic HPC containers CFP11:44
*** openstack changes topic to "HPC containers CFP (Meeting topic: scientific-sig)"11:44
oneswigMartial sends his apologies today but is running an event at ISC in Frankfurt11:45
*** imsurit has quit IRC11:45
oneswig#link HPC containers workshop
oneswigHe has a few panelists involved and from them I think he'll be looking at a good range of technologies11:46
oneswigI think it was just the announcement for that one.11:46
oneswig#topic Help most needed - SIG functional gaps11:46
*** openstack changes topic to "Help most needed - SIG functional gaps (Meeting topic: scientific-sig)"11:47
oneswig#link Forum session on SIG-identified functional gaps
oneswigRico Lin got in touch to ask for participation last week11:47
dtantsurI see 2 bare metal items, but I think I may have a conflict at this time..11:48
oneswigWe started an etherpad11:48
oneswig#link SIG functional gaps etherpad
oneswigdtantsur: I think there'll be plenty of opportunities to respond.  A good one might be the SIG session at the PTG.11:48
dtantsuroh, it's not critical for me, but rather for mgoddard :D11:49
dtantsurI mean, the conflict11:49
*** sidx64 has joined #openstack-meeting11:49
oneswigmgoddard is packing a suitcase full of hats to wear for his many roles in Denver...11:49
mgoddardI didn't even check, tuesday is full :)11:49
dtantsurmgoddard: yeah, it's the slot of your talk11:50
oneswigThursday morning I hope will be a better chance (haven't seen the SIG slots for the PTG yet though)11:50
oneswigI'm hoping we can add some federation experiences to this etherpad in due course11:51
jandersI am inclined to add the baremetal metrics in there11:52
jandersis this of interest to you as well?11:52
oneswigjanders: good idea.11:53
oneswigFor example SKA has concerns on heat management.11:53
oneswigGiven their data centre sites in South Africa and Western Australia...11:53
oneswigjanders: Is SuperCloud in Canberra or WA?11:54
jandersCanberra.. for now ;)11:54
hearnsjRegarding heat/power - people also looking at power budget for compute runs, not just time11:55
jandersimmersive cooling could help there - and there's some really interesting work on that in WA11:55
oneswighearnsj: did you ever evaluate DK Panda's energy-efficient MPI?11:55
*** bobh has joined #openstack-meeting11:55
oneswiga small part of a solution for a big problem11:56
*** raildo has joined #openstack-meeting11:56
* dtantsur has to drop for lunch, sorry. was great to talk to you!11:57
oneswigjanders: think you've got some interest in seeing that raised11:57
oneswigthanks dtantsur!11:57
oneswig#topic Denver Summit11:57
*** openstack changes topic to "Denver Summit (Meeting topic: scientific-sig)"11:57
oneswig#link SIG main session
*** dtantsur has left #openstack-meeting11:57
oneswigIt's Monday afternoon this time11:57
* arne_wiebalck has to run to another meeting o/11:58
oneswigWe'll use the same format, which means half the session will be lightning talks on SIG topics11:58
oneswigthanks arne_wiebalck!11:58
hearnsjoneswig Never did I'm afraid11:58
oneswig#link lightning talks etherpad
hearnsjRegarding immersive cooling - my company has a boat load of it. Pun intended.11:59
oneswigI see janders is already there to defend his win last time :-)11:59
hearnsjIt public knowledge - our Houston datacentre has immersive cooling.11:59
oneswighearnsj: interesting11:59
hearnsjIs there any relevance to Openstack though - we dont run Openstack there.12:00
jandershearnsj: maybe you can give a lightning talk about it? :)12:00
oneswigWe are out of time12:00
jandersthanks guys!12:00
oneswigFinal mentions?12:00
oneswigOK, have to close it there.  Thank you all12:00
*** openstack changes topic to "OpenStack Meetings ||"12:00
openstackMeeting ended Wed Apr 10 12:00:57 2019 UTC.  Information about MeetBot at . (v 0.1.4)12:00
openstackMinutes (text):
*** mgoddard has left #openstack-meeting12:01
*** janders has quit IRC12:02
*** oneswig has quit IRC12:02
*** eharney has joined #openstack-meeting12:06
*** sidx64 has quit IRC12:06
*** ttsiouts has quit IRC12:08
*** ttsiouts has joined #openstack-meeting12:09
*** e0ne has quit IRC12:09
*** sidx64 has joined #openstack-meeting12:09
*** e0ne has joined #openstack-meeting12:12
*** priteau has quit IRC12:12
*** ttsiouts has quit IRC12:13
*** e0ne has quit IRC12:13
*** priteau has joined #openstack-meeting12:14
*** bobh has quit IRC12:18
*** hearnsj has quit IRC12:18
*** sidx64 has quit IRC12:19
*** e0ne has joined #openstack-meeting12:28
*** sidx64 has joined #openstack-meeting12:30
*** sidx64 has quit IRC12:38
*** awaugama has joined #openstack-meeting12:45
*** ricolin has quit IRC12:50
*** ttsiouts has joined #openstack-meeting12:51
*** ricolin has joined #openstack-meeting12:51
*** mjturek has joined #openstack-meeting12:53
*** lbragstad has joined #openstack-meeting12:58
*** lpetrut has quit IRC13:01
*** mriedem has joined #openstack-meeting13:02
*** irclogbot_3 has joined #openstack-meeting13:03
*** sidx64 has joined #openstack-meeting13:07
*** altlogbot_0 has joined #openstack-meeting13:07
*** sidx64 has quit IRC13:08
*** sidx64 has joined #openstack-meeting13:08
*** t0rrant has quit IRC13:09
*** sidx64 has quit IRC13:10
*** jrbalderrama has quit IRC13:16
*** dklyle has joined #openstack-meeting13:17
*** Liang__ has joined #openstack-meeting13:18
*** yamamoto has quit IRC13:19
*** yamamoto has joined #openstack-meeting13:19
*** e0ne has quit IRC13:20
*** t0rrant has joined #openstack-meeting13:21
*** e0ne has joined #openstack-meeting13:25
*** sidx64 has joined #openstack-meeting13:34
*** sidx64 has quit IRC13:39
*** lseki has joined #openstack-meeting13:39
*** e0ne has quit IRC13:54
*** e0ne has joined #openstack-meeting13:57
*** mlavalle has joined #openstack-meeting13:58
mlavalle#startmeeting neutron_l314:00
openstackMeeting started Wed Apr 10 14:00:12 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:00
*** openstack changes topic to " (Meeting topic: neutron_l3)"14:00
openstackThe meeting name has been set to 'neutron_l3'14:00
*** simon-AS559 has quit IRC14:00
*** simon-AS559 has joined #openstack-meeting14:00
mlavallehi liuyulong14:01
mlavalle#topic Announcements14:03
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"14:03
mlavalleThe community is releasing Stein this week14:03
mlavallehaleyb: I think we can tag stable/stein next week to include the latest fixes14:04
mlavalleok with you?14:04
haleybmlavalle: ack, i'll check and make sure things are merged14:04
haleyb shows a few14:06
mlavalleI remind folks that we are gathering topics for the PTG here:
*** davidsha has joined #openstack-meeting14:07
mlavalleand finally, pike stable branch is entering the extended maintenance stage14:07
mlavalleper discussion during yesterday's team meeting, it is up to us to decide how lomg it stays there14:07
mlavalleany other announcements?14:08
mlavalleok moving on14:09
mlavalle#topic Bugs14:10
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"14:10
mlavalleFirst one is
openstackLaunchpad bug 1821912 in neutron "intermittent ssh failures in various scenario tests" [High,Confirmed]14:10
mlavalleas I've mentioned before, we are working collectively in debugging this14:10
mlavalleit was discussed during yesterday's CI meeting14:11
mlavalleand we took specific homeworks:14:11
liuyulongYes, I talked with slaweq today. I will join this team.14:11
mlavalleslaweq is going to create a DNM patch in Tempest to add more logging14:12
mlavalleI am going to create a DNM patch to add some tcpdump tracing14:12
mlavalleliuyulong: great!14:12
*** janki has quit IRC14:13
mlavalleNext one is
openstackLaunchpad bug 1823038 in neutron (Ubuntu Cosmic) "Neutron-keepalived-state-change fails to check initial router state" [High,Confirmed]14:14
mlavalleit seems it has already benn fixed14:14
mlavalleand those are all the bugs I have for today14:15
mlavalleany other bugs we should discuss?14:15
*** slaweq has quit IRC14:16
mlavalleok, moving on14:17
mlavalle#topic On demand agenda14:17
*** openstack changes topic to "On demand agenda (Meeting topic: neutron_l3)"14:17
mlavalleanything else we should discuss today?14:17
haleybvery quiet meeting14:18
mlavallewell, in that case, this will be a short one14:18
mlavallehave a great rest of your day14:19
*** openstack changes topic to "OpenStack Meetings ||"14:19
openstackMeeting ended Wed Apr 10 14:19:11 2019 UTC.  Information about MeetBot at . (v 0.1.4)14:19
openstackMinutes (text):
*** xubozhang has joined #openstack-meeting14:19
*** enriquetaso has joined #openstack-meeting14:22
*** enriquetaso has quit IRC14:35
*** yamamoto has quit IRC14:36
*** yamamoto has joined #openstack-meeting14:40
*** enriquetaso has joined #openstack-meeting14:40
*** yamamoto has quit IRC14:41
*** yamamoto has joined #openstack-meeting14:42
*** sridharg has quit IRC14:42
*** ttsiouts has quit IRC14:44
*** ttsiouts has joined #openstack-meeting14:45
*** mjturek has quit IRC14:47
*** yamamoto has quit IRC14:47
*** ttsiouts has quit IRC14:47
*** ttsiouts has joined #openstack-meeting14:47
*** artom has quit IRC14:50
*** e0ne has quit IRC14:50
*** sidx64 has joined #openstack-meeting14:51
*** slaweq has joined #openstack-meeting14:54
*** e0ne has joined #openstack-meeting14:54
*** ianychoi has quit IRC14:56
*** sidx64_ has joined #openstack-meeting14:56
*** sidx64 has quit IRC14:57
*** walshh_ has joined #openstack-meeting14:57
smcginnis#startmeeting cinder15:00
openstackMeeting started Wed Apr 10 15:00:05 2019 UTC and is due to finish in 60 minutes.  The chair is smcginnis. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: cinder)"15:00
openstackThe meeting name has been set to 'cinder'15:00
smcginnisCourtesy ping: jungleboyj diablo_rojo, diablo_rojo_phon, rajinir tbarron xyang xyang1 e0ne gouthamr erlon tpsilva ganso patrickeast tommylikehu eharney geguileo smcginnis lhx_ lhx__ aspiers jgriffith moshele hwalsh felipemonteiro lpetrut lseki _alastor_ whoami-rajat yikun rosmaita enriquetaso hemna _hemna15:00
smcginnis#link Agenda15:00
*** Liang__ has quit IRC15:00
smcginnisHaha, wait a minute! I'm an hour early!! :D15:01
e0nesmcginnis: it's only 1500 utc :)15:01
whoami-rajatexactly ^^15:01
*** openstack changes topic to "OpenStack Meetings ||"15:01
openstackMeeting ended Wed Apr 10 15:01:12 2019 UTC.  Information about MeetBot at . (v 0.1.4)15:01
openstackMinutes (text):
smcginnisGood meeting all! LOL15:01
smcginnisBusy morning for me.15:01
whoami-rajatsmcginnis:  hah, :)15:02
*** diablo_rojo has joined #openstack-meeting15:02
*** dkehn has joined #openstack-meeting15:03
*** rosmaita has joined #openstack-meeting15:04
*** mjturek has joined #openstack-meeting15:04
davidshastarted an hour early15:04
smcginnisxyang: I jumped the gun an hour early. :]15:04
smcginnisDarn time changes.15:04
*** Erasmus has joined #openstack-meeting15:09
Erasmusso many topic changes15:09
*** Erasmus has quit IRC15:11
*** JangwonLee has quit IRC15:12
*** armax has joined #openstack-meeting15:12
*** mlavalle has left #openstack-meeting15:18
*** munimeha1 has joined #openstack-meeting15:25
*** gyee has joined #openstack-meeting15:26
*** mjturek has quit IRC15:26
*** efried has quit IRC15:28
*** artom has joined #openstack-meeting15:29
*** _alastor_ has joined #openstack-meeting15:29
*** _alastor_ has quit IRC15:30
*** _alastor_ has joined #openstack-meeting15:30
*** Erasmus has joined #openstack-meeting15:30
*** mjturek has joined #openstack-meeting15:32
*** jamesmcarthur has joined #openstack-meeting15:32
*** rsimai is now known as rsimai_away15:39
*** njohnston has joined #openstack-meeting15:40
*** efried has joined #openstack-meeting15:47
*** yamamoto has joined #openstack-meeting15:50
*** mattw4 has joined #openstack-meeting15:51
*** sidx64_ has quit IRC15:51
*** artom has quit IRC15:51
*** carloss has joined #openstack-meeting15:54
*** yamamoto has quit IRC15:59
*** artom has joined #openstack-meeting15:59
smcginnisOK, let's try this again. :)15:59
*** woojay has joined #openstack-meeting16:00
*** geguileo has joined #openstack-meeting16:00
rosmaitayou're still early!16:00
smcginnis#startmeeting cinder16:00
openstackMeeting started Wed Apr 10 16:00:14 2019 UTC and is due to finish in 60 minutes.  The chair is smcginnis. 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
geguileohi! o/16:00
smcginnisrosmaita: I waited. :)16:00
smcginnisPing jungleboyj diablo_rojo, diablo_rojo_phon, rajinir tbarron xyang xyang1 e0ne gouthamr erlon tpsilva ganso patrickeast tommylikehu eharney geguileo smcginnis lhx_ lhx__ aspiers jgriffith moshele hwalsh felipemonteiro lpetrut lseki _alastor_ whoami-rajat yikun rosmaita enriquetaso hemna _hemna16:00
smcginnisFor reals this time.16:00
*** enriquetaso has quit IRC16:00
carlosshi :)16:00
e0nesmcginnis: :)16:00
smcginnisI'm just the substitute. :)16:01
*** dviroel has joined #openstack-meeting16:01
whoami-rajat2 cinder meetings in 1 day :)16:01
e0newe need the 2nd cinder release now16:01
smcginnis#link Agenda16:01
*** thgcorrea has joined #openstack-meeting16:01
smcginnis#topic Announcements16:01
*** openstack changes topic to "Announcements (Meeting topic: cinder)"16:01
smcginnisThe Train PTG is coming up the Thurs-Sat after the Summit.16:02
smcginnisTrying to collect topics here:16:02
*** _erlon_ has joined #openstack-meeting16:02
smcginnisPlease add anything that needs to be discussed.16:02
smcginnisJay is also trying to coordinate a dinner/outing for the team16:03
smcginnisAnyone that will be in Denver - it would be great to get us all together.16:03
smcginnisI'm sure he will have more updates as far as location and other details.16:04
smcginnisWe aren't so far out from the city this time around, so there will probably be a lot of options.16:04
*** ygbo has quit IRC16:05
rosmaitareminder: anyone with dietary restrictions, please put them on that etherpad16:05
smcginnisI processed the final stein release this morning, so we are now officially on to train.16:05
smcginnisPlease take a look at the new driver patches so we can get those out of the way as soon as possible.16:05
*** simon-AS559 has quit IRC16:06
smcginnisI know one or two (RSD at least) were pretty close at the stein deadline, so it would be great if we can help those folks relax and not leave them sit out there too long.16:06
*** Lucas_Gray has quit IRC16:06
*** jamesmcarthur has quit IRC16:06
whoami-rajatit was due to CI not running all tests IIRC ?16:07
smcginnisAnd finally, we are overdue for stable/pike to enter "Extended Maintenance" phase.16:07
smcginniswhoami-rajat: That could be for some. Hopefully they've all sorted that out by now.16:07
whoami-rajatsmcginnis: ok16:07
rosmaitalooks like we're in good shape for final stable/pike releases except for os_brick16:07
smcginnisWith EM phase, we can still choose to backport fixes, but there will no longer be official releases of that stable branch.16:07
rosmaitasome outstanding patches there16:07
smcginnisSo we need to get a final pike release out while we can.16:08
smcginnisrosmaita: Thanks for pulling all of that together.16:08
*** jamesmcarthur has joined #openstack-meeting16:08
smcginnisStable cores, please look at open patches when you can. Other reviews welcome too of course.16:08
*** ociuhandu has joined #openstack-meeting16:08
smcginnis#topic Cinder/Nova Cross Project Discussion16:09
*** openstack changes topic to "Cinder/Nova Cross Project Discussion (Meeting topic: cinder)"16:09
rosmaitaquick question about pythong-brick-cinderclient-ext ... no functional changes, do we want to do a final release just to have no un-merged patches?16:09
*** tejdeep has joined #openstack-meeting16:09
smcginnisI was signed up for this one by Jay, so I don't have too much detail. :)16:09
smcginnisBut as usual, we will have some time with Nova at the PTG to go through cross-project things.16:09
smcginnis#link   Line 23016:10
*** ociuhandu has quit IRC16:10
e0nerosmaita, smcginnis: IMO, it's better to make a final release with current changes if some vendors uses only releases16:10
smcginnisIf anyone has topics that should be discussed that involve any kind of Cinder<>Nova interaction, please get those topics added.16:10
smcginnise0ne: ++ Yep, I agree.16:10
rosmaitaok, thanks16:10
smcginnisThe extended maintenance phase is really kind of like what we did with driverfixes/*16:11
smcginnisJust a place for fixes to be kept so everyone isn't forking their own repos to hold them.16:11
smcginnisBut actual releases are best.16:11
e0nesmcginnis: +116:11
whoami-rajatsmcginnis: L 249? it will change anyway.16:11
smcginnisOK, as far as the Cinder/Nova session, I haven't seen a specific time for that.16:12
smcginniswhoami-rajat: Yeah. Look "somewhere around that area" ;)16:12
smcginnisWatch for more details about when that will take place.16:12
smcginnisTypically in the past we've just joined Nova in their room since they end up with a larger room and it's just easier.16:12
smcginnisSo if anyone shows up to the PTG and the Cinder room is empty, check the nova room.16:13
smcginnisOr the bar. :P16:13
smcginnisAny questions about any of that?16:13
*** psachin has quit IRC16:14
smcginnisOK, moving on then.16:14
*** efried is now known as efried_rollin16:14
smcginnisOh, but first, please add your name/nick to the PTG etherpad so we can get an idea of who will actually be there:
smcginnisAlright, now moving on...16:15
smcginnis#topic Adding is-public arg to cinderclient16:16
*** openstack changes topic to "Adding is-public arg to cinderclient (Meeting topic: cinder)"16:16
smcginniswhoami-rajat: All yours16:16
whoami-rajatSo the patch is receiving multiple suggestions and Eric thought that we need to discuss what the exact parameter should be and where it should reside (inside the --filters or as a separate arg)16:16
whoami-rajateharney:  ^^16:17
eharneyit's not at all clear why we would add a new arg for this while we are actively deprecating other similar args from the list command16:17
eharneywhat is the intent or policy here?16:17
smcginnisGeneric filters were added to prevent the need to keep adding new args.16:17
eharneywhich is... questionable for usability, but good for the code, i think16:18
geguileoI like the idea of adding it as a filter16:18
whoami-rajatso i added the new arg as it is fairly an old option for the API, and keeping in it filters would require 3.52 MV or higher16:18
eharneyi asked in the review if there was some reason it could not be done via filters16:18
e0negeguileo: +116:18
geguileowhoami-rajat: the CLI can receive it as a filter, and internally decide how to pass it to the server, right?16:19
whoami-rajatgeguileo:  need to check, but yeah it can be added in filter.16:20
eharneywhat would a user pass in to use this w/ filters?16:20
eharneybecause as Brian pointed out, the --is-public boolean is not exactly straightforward16:21
geguileoeharney: yeah, rosmaita raise an important point there16:22
rosmaitait might not be so bad with --filter, though16:22
eharneycalling "cinder list --visibility private" is way more sensible than "cinder list --filters is_public=False"16:22
eharneywhich kind of makes me wonder where we were going with the idea of deprecating --bootable, --status, etc16:22
geguileoeharney: it is indeed more sentible, but it kind of diverges from what we usually do, right?16:23
eharneygeguileo: i'm trying to figure out if what we usually/currently do is actually reasonable or not16:23
eharneyand i'm not really sure yet16:23
eharneybecause replacing "--bootable true" with "--filters bootable=true" seems like something just designed to be annoying when there's no reason we couldn't just map "--bootable true" into whatever API we want16:24
geguileoeharney: I kind of prefer the filters thing  XD16:25
eharneyi... really don't16:25
eharneybut anyway, is it possible to do this with --filters currently w/o changing the client?16:25
whoami-rajatgeguileo: filters are just updated inside search_opts so yeah we can decide what to send to API.16:26
eharneyjust to know where we are starting from16:26
rosmaitai think that's the key question, because if we have to change the client, might as well make it a good usability change16:26
rosmaitathe only advantage i see to --filters is if we don't have to change the client to handle new filters16:26
smcginnisThat was the intent for how it should work.16:27
smcginnisThen you don't need a new client release every time we add yet another thing to filter on.16:27
rosmaitaright, makes sense16:27
whoami-rajatsmcginnis: and can be backported as well?16:27
eharneybackporting is a whole separate discussion from any of this for now16:27
eharneylet's just worry about cinderclient master16:28
smcginnisShouldn't be a need to backport, since the mechanism just allows whatever attribute you want to filter on to be passed through.16:28
smcginnisSo older clients can work with newer servers and vice versa.16:28
smcginnisBut yeah, let's just focus on master for now.16:28
whoami-rajati think this option started with the discussion of backporting to stein, but yeah first concluding the master is better.16:29
eharneyworrying about stein is a huge distraction from trying to design cinderclient's interface16:29
*** Erasmus has quit IRC16:29
whoami-rajateharney: ++16:30
smcginnisSo I'm not clear where things stand. Are we actually fine with the client as it is today with being able to use --filter?16:31
eharneyone argument against --filters is that it exposes cinder db internals to the shell interface16:31
rosmaitaalso, i think what you can actually filter on isn't available in the help, right?16:32
eharneyalso, --filters doesn't work correctly, which is really an implementation bug, but maybe worth keeping in mind here:
openstackLaunchpad bug 1696780 in python-cinderclient "supplying multiple list --filters does not work correctly" [Undecided,New] - Assigned to Rajat Dhasmana (whoami-rajat)16:32
smcginnisDidn't that include a way to query what the available filters were? I thought that was part of it.16:32
smcginnisBecause administrators could also control some of that.16:33
eharneyyou can specify what fields can be filtered in the server config16:33
eharneyi don't think you can query for them..?16:33
whoami-rajateharney: i remember that, when multiple filters are passed it only considers the first (or last) one.16:34
eharneyoh, "cinder list-filters"16:34
whoami-rajateharney: that just returns the resource_filters.json right?16:34
eharneyit lists the fields for each resource16:34
smcginnis"The list-filters component is derived from an Admin provided list of valid and enabled filters for end users to access."16:36
eharneywhich is kind of interesting because now it means that things like the message table's message_level field is exposed as a string via the API, which means we couldn't ever do something like change it to an integer in the database without going through a bunch of compat issues16:36
smcginnisIt's something that can be discovered by querying, so I think it's a little more flexible that an actual API change.16:37
*** factor has joined #openstack-meeting16:38
smcginnisSo... next steps for is_public?16:39
*** ttsiouts has quit IRC16:40
*** ttsiouts has joined #openstack-meeting16:41
eharneywell 1) is make sure it actually works currently w/ --filters like we think it does16:41
smcginniswhoami-rajat: Can you take that action? ^16:41
whoami-rajatwill update the code with --filters16:41
eharneythen we can categorize the addition of a new arg to the CLI as a usability improvement instead of something needed to enable the feature16:42
smcginnis#action whoami-rajat to test --filters works with public visibility16:42
eharneywhich, i dunno, gives us time to procrastinate until we figure out how this should actually be designed?16:42
smcginnisIf this is not a topic on the PTG etherpad, might be good to add it there to make sure we follow up.16:42
whoami-rajatsmcginnis: ++16:43
eharneythe generalized filters spec has an unfortunately link to a github gist which no longer exists.  maybe all the answers were in there16:43
eharneyunfortunate link*16:43
smcginniswhoami-rajat: I will leave that to you as well. :)16:43
whoami-rajatsmcginnis: sure, will do!16:43
smcginniswhoami-rajat: Thanks!16:43
smcginniseharney: I'm sure jgriffith has all the answers. :)16:43
smcginnisA couple more topics. Are we good to move on?16:44
smcginnis#topic User messages16:44
*** openstack changes topic to "User messages (Meeting topic: cinder)"16:44
rosmaitai will make this quick16:44
smcginnisrosmaita: You have the floor.16:44
*** altlogbot_0 has quit IRC16:44
rosmaitai was reviewing some patches that add some user messages for the messages API and wasn't quite clear on how it's supposed to work16:44
rosmaitai dug in the code a bit, thought i had found a bug, and then realized that it probably wasn't a bug16:44
rosmaitaanyway, i updated the contrib docs on user messages (the code had been refactored in pike to add the message_field stuff but the docs were not updated)16:45
rosmaitai also added some tests so that some dope like me doesn't come along and "fix" something that is not broken16:45
*** ttsiouts has quit IRC16:45
rosmaitathe reason i am bringing this up is that i've only been working on cinder a few months, so it would be good for some people with more institutional memory to double-check me on this16:45
rosmaitabtw, i added a "usage patterns" section to the contrib docs so it's easy to see how to add them16:45
rosmaitabecause adding user messages seems like a useful thing that new contributors can do that also has a high end-user impact16:45
smcginnisThanks for making that docs better with that!16:45
rosmaitaanyway, that's it from me16:45
smcginnisI think we could still spend some time improving our user messages. Glad to see some attention there.16:46
rosmaitayeah, they're used in surprisingly few places16:46
smcginnis#topic cinderlib update16:47
*** openstack changes topic to "cinderlib update (Meeting topic: cinder)"16:47
smcginnisgeguileo: Your turn16:47
eharneyalong similar lines, the client would love some more work adding --poll to other operations to get those messages16:47
geguileosmcginnis: thanks16:47
geguileoThis will be quick16:47
smcginniseharney: ++16:47
geguileoWe are just 1 patch away from being able to release cinderlib16:48
geguileo^ that's the last patch16:48
geguileoAfter that we'll be able to release version 0.9 as the Stein release16:48
geguileoas we agreed in last week's meeting16:48
smcginnisgeguileo: Thanks for all your work on that. There was a lot of churn over the course of that in stein.16:48
geguileoand thank you all that helped with the reviews and making suggestions on how to do things16:49
geguileolike using launchpad for the time being16:49
geguileoand doing independent releases16:49
geguileoit helped :-)16:49
geguileonow I'm working on a document explaining how to validate cinderlib using devstack16:50
geguileoand how to add it to the 3rd party CI jobs16:50
smcginnisOh nice. That will be good. That would be for those other backends that you have not been able to work with?16:50
geguileoaaaaaaand that was all O:-)16:50
geguileosmcginnis: and even for those that I have been able to work16:50
geguileobecause that way they can ensure that they keep working16:51
smcginnisThird party CI would be good. I think we have a few things to talk about with CI at the PTG that we need to make sure all of the maintainers are aware of.16:51
smcginnisPython 3 being the other major thing.16:51
smcginnisThanks geguileo!16:52
smcginnis#topic Open floor16:52
*** openstack changes topic to "Open floor (Meeting topic: cinder)"16:52
smcginnisAnyone else have anything to bring up?16:52
smcginnisWould be great to get a good start on Train. I have it on my list to take a look through specs.16:53
smcginnisOK, I guess we can wrap up for today. Thanks everyone!16:54
*** openstack changes topic to "OpenStack Meetings ||"16:54
openstackMeeting ended Wed Apr 10 16:54:54 2019 UTC.  Information about MeetBot at . (v 0.1.4)16:54
openstackMinutes (text):
*** e0ne has quit IRC16:55
whoami-rajatthanks smcginnis16:55
smcginnisTake 2 was better than the first one. :D16:55
*** enriquetaso has joined #openstack-meeting16:56
*** woojay has left #openstack-meeting16:58
*** davidsha has quit IRC17:01
*** kopecmartin is now known as kopecmartin|off17:03
*** dviroel has left #openstack-meeting17:05
*** thgcorrea has left #openstack-meeting17:07
*** t0rrant has quit IRC17:08
*** enriquetaso has quit IRC17:10
*** tejdeep has quit IRC17:12
*** enriquetaso has joined #openstack-meeting17:12
*** slaweq has quit IRC17:14
*** priteau has quit IRC17:31
*** iyamahat has joined #openstack-meeting17:41
*** jamesmcarthur has quit IRC17:42
*** boxiang has quit IRC17:43
*** boxiang has joined #openstack-meeting17:48
*** ricolin has quit IRC17:49
*** yamahata has joined #openstack-meeting17:59
*** yamamoto has joined #openstack-meeting18:12
*** jamesmcarthur has joined #openstack-meeting18:12
*** tejdeep has joined #openstack-meeting18:14
*** electrofelix has quit IRC18:24
*** ijw has joined #openstack-meeting18:25
*** rosmaita has left #openstack-meeting18:31
*** priteau has joined #openstack-meeting18:33
*** priteau has quit IRC18:37
*** vishalmanchanda has quit IRC18:39
*** slaweq has joined #openstack-meeting18:46
*** slaweq has quit IRC18:52
*** enriquetaso has quit IRC18:58
*** enriquetaso has joined #openstack-meeting18:58
*** simon-AS559 has joined #openstack-meeting19:03
*** simon-AS5591 has joined #openstack-meeting19:04
*** simon-AS559 has quit IRC19:07
*** tssurya has quit IRC19:07
*** enriquetaso has quit IRC19:08
*** artom has quit IRC19:11
*** ijw has quit IRC19:16
fungifor those wondering, chatter in #storyboard suggests no meeting this week. find us in there if you have something to bring up19:23
*** yamamoto has quit IRC19:23
*** yamamoto has joined #openstack-meeting19:24
*** eharney has quit IRC19:28
*** yamamoto has quit IRC19:29
*** efried_rollin is now known as efried19:37
*** mjturek has quit IRC19:44
*** ijw has joined #openstack-meeting19:47
*** ralonsoh has quit IRC19:48
*** simon-AS559 has joined #openstack-meeting19:56
*** simon-AS5591 has quit IRC19:56
*** simon-AS5591 has joined #openstack-meeting19:58
*** jamesmcarthur has quit IRC19:59
*** simon-AS559 has quit IRC20:00
*** igordc has joined #openstack-meeting20:08
*** slaweq has joined #openstack-meeting20:20
*** priteau has joined #openstack-meeting20:33
*** priteau has quit IRC20:48
*** Lucas_Gray has joined #openstack-meeting20:51
*** patchbot has joined #openstack-meeting20:58
timburke#startmeeting swift21:00
openstackMeeting started Wed Apr 10 21:00:06 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:00
*** openstack changes topic to " (Meeting topic: swift)"21:00
openstackThe meeting name has been set to 'swift'21:00
timburkewho's here for the swift meeting?21:00
*** alecuyer has joined #openstack-meeting21:01
*** zaitcev has joined #openstack-meeting21:01
timburkepretty short agenda (i guess that happens for a while after a release)21:02
clayglove it21:02
timburkefirst up, updates!21:02
timburke#topic py321:02
*** openstack changes topic to "py3 (Meeting topic: swift)"21:02
timburkewho has progress to share?21:02
* zaitcev hides21:02
* zaitcev remembers SLO and reappers21:03
timburkeyay slo!21:03
zaitcevOh, right. How many months did I promise SLO? It's there now. Still needs bulk first though, and there's a couple of tests that triggered re-think in bulk, although bulk's own tests did not catch it.21:03
mattoliverauzaitcev: nice21:04
mattoliverauI pushed a very slight update on the staticweb patch, just addressed comments21:04
timburkedefinitely seems promising21:05
timburkei'm currently working on s3api -- down to just 26 or so failing tests... but i think they're all to do with creating strings to sign, which might get messy21:05
timburkeanybody blocked on py3 work? need any help or want to highlight something worth reviewing?21:06
timburkeall right, moving on21:06
*** raildo has quit IRC21:06
timburke#topic losf21:07
*** openstack changes topic to "losf (Meeting topic: swift)"21:07
timburkei saw kota_ pushed up a series of patches21:07
kota_i still need to fix (and perhaps squash) some of these tho.21:08
alecuyeryes, the go modules, I think it's a good idea, I tried in on vagrant, posted a few comments and some changes to the Makefile21:08
kota_thx alecuyer! I'll check what's going on in such a vagrant box.21:09
kota_it worked in my box so i should check what's diff.21:09
timburkecool -- sounds like it's coming along. hopefully we'll be able to have tests running with go code in the gate soonish21:10
kota_i also *want* try to make ansible ploybook to repro the make in the gate env.21:10
kota_timburke: :)21:10
timburkeagain, anybody blocked? anything the rest of us should be doing to help this week?21:11
zaitcevI'm scared of leveldb.21:11
alecuyerotherwise, I still have unit tests to fix to go with the http/rpc change21:11
zaitcevI'm going to ask for some kind of technical overview at PTG.21:11
alecuyerzaitcev: tell me more :) here or outside the meeting, whichever is best21:11
timburkewell, how about after21:13
timburkeany other topics that should give updates?21:14
kota_it looks like zaitcev wants to do that in PTG21:14
timburkeer, on which we should give updates? i suppose the topic itself can't provide an update...21:14
timburke#topic PTG21:15
*** openstack changes topic to "PTG (Meeting topic: swift)"21:15
timburkemattoliverau was great and already set up an etherpad21:16
timburkei seeded a few topics; feel free to add more21:16
timburkeand of course, add yourself to topics you're interested in21:16
* kota_ will do21:16
timburkei ought to book a slot for the team photo -- does anyone have a preference for Thursday or Friday?21:17
zaitceveither one okay by me21:17
timburkelooking at the days that people put on the etherpad, it seems like either will probably be fine...21:18
timburkedoes anyone have a preference for morning or afternoon?21:18
mattoliverau I think I need to look at the strawman shedule again.. but I think either is fine21:19
claygI can get ragged after a long day of ptg’ing21:19
timburkeall right, i'll pick a slot21:19
notmynameclay's suggestion of morning is good. doesn't matter the day. but morning or right next to lunch doens't interrupt the flow21:20
timburkethat's it for the agenda21:20
timburke#topic open discussion21:20
*** openstack changes topic to "open discussion (Meeting topic: swift)"21:20
timburke(booked the photo for 11:20 on Thursday)21:21
*** slaweq has quit IRC21:21
timburkewho has other things to bring up?21:21
notmynamethe release happened!21:22
notmynameie the big ol' openstack stein release21:22
notmynameso there's marketing around that21:22
timburketotally did. there's a Stein! let's celebrate with beer21:22
notmynamedoesn't affect us *too* much (since we tagged a while back), but celebrate the wins :-)21:22
mattoliverauoh a swift stein would be an awesome peice of shwag21:23
timburkenotmyname, you've done shirts before... how about it? ;-)21:23
notmynamethat would be cool, but it's a bit late for that. take a few months to make shirts21:24
notmynamewell, at least the way i've done them in the past21:24
*** njohnston has left #openstack-meeting21:25
timburkeso, i started poking at the quadiron patches. i think one of them may break compat for phazr, though :-/21:25
timburkeand i realized that i really want to restructure the libec unit tests, so we could have a separate job per external backend21:26
kota_sounds good21:27
timburkeanyone have anything else?21:28
timburkethanks for coming, and thank you all for working on swift!21:30
alecuyerthanks tim21:30
*** patchbot has left #openstack-meeting21:30
timburkei'll see most (all?) of you soon in Denver!21:30
*** openstack changes topic to "OpenStack Meetings ||"21:30
openstackMeeting ended Wed Apr 10 21:30:42 2019 UTC.  Information about MeetBot at . (v 0.1.4)21:30
openstackMinutes (text):
*** zaitcev has left #openstack-meeting21:30
*** alecuyer has left #openstack-meeting21:31
mattoliverauthanks timburke21:31
*** ijw has quit IRC21:31
*** ijw has joined #openstack-meeting21:35
*** eharney has joined #openstack-meeting21:37
*** slaweq has joined #openstack-meeting21:38
*** bobh has joined #openstack-meeting21:39
*** mriedem has quit IRC21:40
*** slaweq has quit IRC21:42
*** bobh has quit IRC21:47
*** bobh has joined #openstack-meeting21:48
*** eharney has quit IRC22:06
*** rcernin has joined #openstack-meeting22:06
*** bobh has quit IRC22:14
*** JangwonLee has joined #openstack-meeting22:24
*** carloss has quit IRC22:24
*** Lucas_Gray has quit IRC22:35
*** simon-AS5591 has left #openstack-meeting22:41
*** munimeha1 has quit IRC22:41
*** slaweq has joined #openstack-meeting22:49
*** whoami-rajat has quit IRC22:51
*** slaweq has quit IRC22:53
*** Liang__ has joined #openstack-meeting22:56
*** _erlon_ has quit IRC23:21
*** david-lyle has joined #openstack-meeting23:36
*** dklyle has quit IRC23:36
*** Liang__ has quit IRC23:42
*** david-lyle has quit IRC23:46
*** ianychoi has joined #openstack-meeting23:46
*** artom has joined #openstack-meeting23:48
*** rcernin has quit IRC23:52

Generated by 2.15.3 by Marius Gedminas - find it at!