Wednesday, 2019-03-27

*** maxhub_ has joined #openstack-meeting00:00
*** mjturek has quit IRC00:06
*** erlon has joined #openstack-meeting00:07
*** lseki has quit IRC00:14
*** dolphm has quit IRC00:16
*** tetsuro has joined #openstack-meeting00:18
*** slaweq has joined #openstack-meeting00:21
*** slaweq has quit IRC00:27
*** fatema_ has quit IRC00:38
*** igordc has quit IRC00:48
*** jamesmcarthur has joined #openstack-meeting00:49
*** markvoelker has joined #openstack-meeting00:51
*** zhubx has quit IRC00:53
*** zhubx has joined #openstack-meeting00:53
*** markvoelker has quit IRC01:03
*** jbadiapa has quit IRC01:23
*** jbadiapa has joined #openstack-meeting01:23
*** senrique_ has joined #openstack-meeting01:38
*** rcernin has quit IRC01:49
*** rcernin has joined #openstack-meeting01:53
*** erlon has quit IRC01:53
*** hongbin has joined #openstack-meeting01:54
*** cheng1 has joined #openstack-meeting01:54
*** iyamahat has quit IRC02:01
*** yamahata has quit IRC02:01
*** ianychoi has quit IRC02:03
*** ianychoi has joined #openstack-meeting02:03
*** whoami-rajat has joined #openstack-meeting02:08
*** SotK has quit IRC02:15
*** mgagne has quit IRC02:15
*** mgagne has joined #openstack-meeting02:15
*** SotK has joined #openstack-meeting02:15
*** psachin has joined #openstack-meeting02:50
*** jamesmcarthur has quit IRC02:52
*** hongbin has quit IRC03:06
*** senrique_ has quit IRC03:10
*** apetrich has quit IRC03:15
*** cheng1 has quit IRC03:20
*** alexandre_b has joined #openstack-meeting03:21
*** jamesmcarthur has joined #openstack-meeting03:36
*** jamesmcarthur has quit IRC03:44
*** jamesmcarthur has joined #openstack-meeting03:45
*** jamesmcarthur has quit IRC03:47
*** jamesmcarthur has joined #openstack-meeting03:47
*** jamesmcarthur has quit IRC03:52
*** cheng1 has joined #openstack-meeting03:55
*** tetsuro has quit IRC03:58
*** jamesmcarthur has joined #openstack-meeting04:00
*** jamesmcarthur has quit IRC04:01
*** maxhub_ has quit IRC04:04
*** imsurit_ofc has joined #openstack-meeting04:05
*** janki has joined #openstack-meeting04:50
*** psachin has quit IRC04:58
*** tetsuro has joined #openstack-meeting05:18
*** psachin has joined #openstack-meeting05:19
*** lbragstad has joined #openstack-meeting05:25
*** lbragstad has quit IRC05:41
*** iyamahat has joined #openstack-meeting05:43
*** alexandre_b has quit IRC05:45
*** ivy has joined #openstack-meeting05:46
*** vishalmanchanda has joined #openstack-meeting05:57
*** ivy has quit IRC06:04
*** cheng1_ has joined #openstack-meeting06:22
*** e0ne has joined #openstack-meeting06:23
*** cheng1 has quit IRC06:25
*** markvoelker has joined #openstack-meeting06:31
*** liuyulong has joined #openstack-meeting06:32
*** e0ne has quit IRC06:43
*** e0ne has joined #openstack-meeting06:47
*** apetrich has joined #openstack-meeting06:52
*** e0ne has quit IRC06:59
mattoliverauok fc_sig meeting time07:00
mattoliverau#startmeeting fc_sig07:00
openstackMeeting started Wed Mar 27 07:00:26 2019 UTC and is due to finish in 60 minutes.  The chair is mattoliverau. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.07:00
*** openstack changes topic to " (Meeting topic: fc_sig)"07:00
openstackThe meeting name has been set to 'fc_sig'07:00
mattoliveraupinglist: gmann, mattoliverau, tonyb07:00
mattoliverau(minus cmurphy who turned up before I could ping) :P07:00
mattoliverauoh a salute, I'll take it07:01
mattoliverauThis weeks agenda:07:01
mattoliverauShall we wait for gmann or just begin?07:02
diablo_rojoI dont think he will be attending since its like... 2:00AM his time?07:03
mattoliverauoh, pfft, who needs sleep :P07:03
mattoliveraufair enough07:03
diablo_rojoI do. I ran an 8k today :P07:03
mattoliverau#topic New Contributor Patches07:03
*** openstack changes topic to "New Contributor Patches (Meeting topic: fc_sig)"07:03
*** lennyb has joined #openstack-meeting07:03
mattoliveraudiablo_rojo: wow07:04
* tonyb didn't do homework but did notice the 2 tripleo new-contributor patches merged this week :)07:04
diablo_rojoI accidentally did the homework!07:04
mattoliverautonyb: oh cool nice07:04
mattoliveraudiablo_rojo: WHAT!07:04
tonybIt's homework or run the meeting pick one ;P07:05
mattoliveraugood, cause I didn't do the homework either. It's been a little crazy at home this week.07:05
mattoliverau* fortnight07:05
mattoliverauoh good07:05
diablo_rojoYeah we had a bunch of new contributors to storyboard07:05
diablo_rojopotential outreachy interns07:05
*** e0ne has joined #openstack-meeting07:05
tonybdiablo_rojo: cool.07:06
mattoliverauoh cool, with all the flurry of net contrib patches, anything stand out for New contrib of the month?07:06
diablo_rojoEhhh its a little early to tell07:06
mattoliveraunot that we've had one yet.. and it's definitely not monthly :P07:06
diablo_rojowe will see if they respond to comments07:06
mattoliverauoh yes.. the dreaded, pushing a patch is the easy part. pushing a follow up is hard.07:07
tonybmattoliverau: as it's the first it can be New COntributor of the eon!07:07
mattoliverauanything else on this topic?07:08
mattoliveraudiablo_rojo: will any of the interns or potential interns be at summit/ptg?07:08
diablo_rojomattoliverau, not that I know of sadly07:09
diablo_rojoMaybe shanghai07:09
mattoliverau:( otherwise we could have met and hung out with them getting them used to the craziness of a summit07:09
mattoliverauI guess we should offer that for anyone new at the OUI as well.07:10
mattoliverauanyway, I'm just rambling now. let's move on.07:10
mattoliverau#topic Contribution Questions07:10
*** openstack changes topic to " Contribution Questions (Meeting topic: fc_sig)"07:10
mattoliverauAnyone notice anything new? or did anyone seed some more questions?07:11
diablo_rojoI didnt go answer any but I looked up the two I had posted a while ago and they still could use some love.07:12
* tonyb sheepishly looks at his boots07:12
diablo_rojoI got responses..but not correct for one of them.07:12
mattoliverautonyb: are they ugg boots cause then sheepish would have a double meaning :)07:12
tonybmattoliverau: LOL07:12
mattoliverauremember, I'm a dad now.. I can say those kind of things :P07:13
tonybmattoliverau: very true07:13
mattoliverauFrom a quick look now, I can't see anything new contributor-ish that is new (well based on dates).07:13
mattoliverauwe do need to give diablo_rojo's anon questions some love07:14
tonybwhen I find them07:14
* tonyb might be missing some thing07:14
mattoliverauaha, that sounds like a volunteer ;)07:14
tonybUm no07:15
mattoliverauif you follow each link you should find them. She used some of the tags we are monitoring.07:15
tonybmattoliverau: Okay07:16
diablo_rojoDefinitely sounds like a volunteer ;)07:16
diablo_rojoYes I did07:16
tonybmattoliverau: I'll double check that my tabs have all the links07:16
mattoliverauwell if someone hasn't gotten to them by next meeting I'll pull out the big action item guns.07:17
mattoliverauanything else for this topic?07:17
diablo_rojomattoliverau, that sounds like you just volunteered to run the next meeting ;)07:18
mattoliveraudiablo_rojo: well anything can probably use the #action tag.. but... bugger.07:19
mattoliveraudepends on when the meeting is ;)07:19
diablo_rojoTwo weeks from now ;)07:19
mattoliveraulol, I meant time07:19
mattoliverau#topic Sandbox Bot07:19
*** openstack changes topic to "Sandbox Bot (Meeting topic: fc_sig)"07:19
*** slaweq has joined #openstack-meeting07:19
mattoliverautonyb: over to you07:19
* diablo_rojo looks at tonyb 07:19
tonybYou know 2 weeks ago I made a promise07:20
tonybto email the list07:20
tonybabout a week ago I worked out that I've lost the last version of the code :/07:21
mattoliverauoh noes07:21
tonybI normally live in a world wheer gerrit is my backup but this time I chose not to07:21
diablo_rojoThis kids is a lesson in commiting and pushing code often even if its still a WIP07:22
tonybthen someone ran git clean -fdx && git reset --hard origin/master in all the repos I have cloned07:22
mattoliverauoh opps07:22
mattoliveraumaybe your new script can "git stash && git clean -fdx && git reset --hard origin/master" :P07:23
tonybmattoliverau: Yeah I decided I wanted from free disk so ran my updater script with --clean :(07:23
tonybcan I have a raincheck?07:24
mattoliverauso the stuff in sandbox is much older?07:24
tonybit's close but I had bug fixes locally :(07:24
tonybI'm keen to fix it so I can run a 'test run' during OUI07:24
tonybdon't tell anytone07:24
tonybanyone even :(07:24
mattoliverauoh well at least there is an enforced deadline.07:25
mattoliverauwell debug it, and then maybe send an email when you get back to parity07:25
tonybYeah kinda07:25
* diablo_rojo imagines mattoliverau banging some gavel in resolution 07:26
mattoliverauoh I should get one of the those.. can we have one for OUI?07:26
mattoliverauok. well let's bug tonyb again in 2 weeks and see if anythings moved. tonyb please ping me (or us) if you need any help getting it done before OUI07:28
mattoliverau#topic Summit + Forum Planning07:28
*** openstack changes topic to "Summit + Forum Planning (Meeting topic: fc_sig)"07:28
mattoliverauseems diablo_rojo has organised some awesome fc-sig events for Monday and Tuesday.07:29
mattoliveraudiablo_rojo: do we need to talk about plans for these?07:31
mattoliveraumaybe bring any left over snacks (like the tim-tams) to the meet and greet, or do we need an American or Denver equiv :P07:32
diablo_rojotim tams sounds good07:32
* tonyb will have tim tams07:32
diablo_rojoMaybe we can get other junk food07:33
tonybspotz: hasn't asked for any yet but meh I'll pre-empt07:33
diablo_rojoas for the second one..just be there with brains a plenty to chat07:33
mattoliverauluckly I arrive on Friday so by Tuesday my brain should be working :)07:34
mattoliveraulet's move on then07:34
mattoliverau#topic Project Liaisons07:34
*** openstack changes topic to "Project Liaisons (Meeting topic: fc_sig)"07:34
mattoliverauNow that there are a bunch of new ptls we should email the list and make sure the liason list is updated07:35
mattoliverauat least with the projects that have defaulted to the ptl07:35
mattoliveraunot that the last call out got the PTLs to go update the wiki.07:36
mattoliverauany volunteers?07:36
mattoliverauI see no one wants to speak up :P07:37
mattoliverauI'll give it a whirl then.07:38
* diablo_rojo looks at mattoliverau :)07:38
diablo_rojoThank you mattoliverau :)07:38
mattoliverau#action mattoliverau to send out an email to the list asking for PTLs to update FC SIG liason list.07:38
mattoliveraulet's move on..07:39
diablo_rojoa true hero ;)07:39
mattoliverau#topic People to Reach Out To07:39
*** openstack changes topic to "People to Reach Out To (Meeting topic: fc_sig)"07:39
mattoliverauIs there anything to talk about here. Anyone reached out. I'll admit I haven't really looked at this at all.07:39
diablo_rojoI dont think anything has happened with them07:40
diablo_rojoI think we can table this topic unless you want to set actions for people07:41
* tonyb didn't do anything with the people on his list07:41
mattoliverauyeah let's leave it for now.. cause we might want to talk about something more important.. the new meeting time.07:42
diablo_rojo\o/ last topic?07:42
mattoliverau#topic new meeting time07:42
*** openstack changes topic to "new meeting time (Meeting topic: fc_sig)"07:42
mattoliveraudiablo_rojo: you can sleep soon :)07:43
diablo_rojoI saw one more response come in today07:43
mattoliveraucool, diablo_rojo any updates?07:43
*** kopecmartin|off is now known as kopecmartin07:43
mattoliverauyou sent an email today, so will the next meeting be the first at the new time?07:44
diablo_rojoI was gonna give it till the end of the week and announce the new time07:44
diablo_rojoEhhh I think I said in the email that the next one would be the new time?07:44
diablo_rojoOr was t the one after?07:44
mattoliverauthe 9/10 april. which should be the next right?07:45
* mattoliverau always fails at dates and timezones :P07:45
*** e0ne has quit IRC07:45
tonyb[tony@thor ~]$ date --date "+2 weeks"07:46
tonybWed Apr 10 17:45:59 AEST 201907:46
mattoliverautonyb: ahh great work07:46
diablo_rojoSo that one would be the new time?07:46
diablo_rojoOr no?07:46
mattoliverauso yes next meeting.07:46
diablo_rojoWe wanted to wait till after all the dst changes I think?07:46
mattoliverauthats when you say it takes effect in your  email :)07:46
tonybI think that is after the chaange here07:46
diablo_rojoSo yeah, end of the week I will announce the new time/update the config07:46
tonyband AU is last IIUC07:47
mattoliveraudiablo_rojo: cool.07:47
tonybSo yeah 2 weeks from now at whatevere the new time is07:47
mattoliverauoh yeah.. I didn't think about our time changing again. damn you day light saving time!07:47
diablo_rojoBehind the times and in the future simultaneously. Impressive.07:47
tonybdiablo_rojo: we are a paradox!07:47
*** e0ne has joined #openstack-meeting07:48
diablo_rojoI still enjoy knowing that the flat earth people think Australia is a government subsidized ploy to make people think the world is round.07:48
mattoliveraucool, then I don't think there is anything else to say on this topic then.. we'll await diablo_rojo's annoucement07:49
diablo_rojoAnd that its not actually a thing07:49
diablo_rojoNothing else from me07:49
* tonyb can't wait to find out ;P07:49
mattoliveraufinally, I can stop using the damn funny sounding accent :P07:49
mattoliveraucool then..07:49
diablo_rojomattoliverau, and not be so jetlagged07:50
mattoliverau#topic open floor07:50
*** openstack changes topic to "open floor (Meeting topic: fc_sig)"07:50
tonybmattoliverau: LOL07:50
diablo_rojoCan you keep the funny accent at least until the Summit starts? My sister will want to hear it in person on Friday night.07:50
mattoliveraulol, fine, another month or so wont hurt :P07:51
tonybmattoliverau: doesn't have an accent07:51
diablo_rojoI think its a month exactly07:51
tonybdiablo_rojo: you do ...07:51
*** liuyulong_ has joined #openstack-meeting07:51
tonybOh wow you're right07:51
mattoliveraulol, tonyb thanks, I agree.07:51
*** e0ne has quit IRC07:51
diablo_rojoI'm outnumbered here so I guess I am the minority..but in denver...07:52
*** e0ne has joined #openstack-meeting07:52
* diablo_rojo shakes fist07:52
mattoliverauAnything else anyone want to raise before we let diablo_rojo get some sleep?07:52
diablo_rojoyou will be the funny accent people ;)07:52
diablo_rojoYes sleep please07:52
*** e0ne has quit IRC07:52
*** liuyulong has quit IRC07:54
mattoliverauwell thanks everyone for coming and I look forward to chatting again at the next meeting. Same day... different time.07:54
*** e0ne has joined #openstack-meeting07:54
tonybmattoliverau: I think you can do a thing ;P07:54
mattoliverauoh yeah07:54
mattoliveraujust dragging it out :P07:54
*** openstack changes topic to "OpenStack Meetings ||"07:54
openstackMeeting ended Wed Mar 27 07:54:58 2019 UTC.  Information about MeetBot at . (v 0.1.4)07:55
openstackMinutes (text):
diablo_rojoThank you again mattoliverau07:55
diablo_rojoI owe you something. I would say a beer but idk if the gout will be flaring up in Denver amd it will be on the forbidden list.07:56
mattoliveraunps, night diablo_rojo o/07:56
mattoliveraulet's see how the meds hold out ;)07:56
* diablo_rojo croses fingers for mattoliverau 07:56
*** diablo_rojo has quit IRC08:03
*** liuyulong_ has quit IRC08:04
*** lajoskatona has left #openstack-meeting08:11
*** e0ne has quit IRC08:17
*** yamahata has joined #openstack-meeting08:24
*** yamamoto has joined #openstack-meeting08:33
*** Lucas_Gray has joined #openstack-meeting08:46
*** sridharg has quit IRC08:54
*** sridharg has joined #openstack-meeting08:56
*** pcaruana has joined #openstack-meeting08:57
*** ttsiouts has joined #openstack-meeting09:00
*** ttsiouts has quit IRC09:10
*** tetsuro has quit IRC09:12
*** ttsiouts has joined #openstack-meeting09:13
*** priteau has joined #openstack-meeting09:16
*** tssurya has joined #openstack-meeting09:18
*** a-pugachev has joined #openstack-meeting09:19
*** Lucas_Gray has quit IRC09:37
*** Lucas_Gray has joined #openstack-meeting09:37
*** ralonsoh has joined #openstack-meeting09:42
*** cheng1_ has quit IRC09:55
*** cheng1_ has joined #openstack-meeting10:07
*** e0ne has joined #openstack-meeting10:12
*** yamamoto has quit IRC10:21
*** imsurit_ofc has quit IRC10:28
*** alexandre_b has joined #openstack-meeting10:31
*** e0ne has quit IRC10:34
*** electrofelix has joined #openstack-meeting10:41
*** e0ne has joined #openstack-meeting10:42
*** a-pugachev has quit IRC10:45
*** maxhub_ has joined #openstack-meeting10:45
*** a-pugachev has joined #openstack-meeting10:46
*** kaisers has quit IRC10:47
*** martial_ has joined #openstack-meeting10:48
*** kaisers has joined #openstack-meeting10:49
*** rcernin has quit IRC10:51
*** oneswig has joined #openstack-meeting10:57
martial_Stig, Blair, Alex, Maxime?10:57
martial_Bonjour indeed :)10:58
martial_sounds like we have quorum :)10:58
oneswigTake it away, Mr Music :-)10:59
oneswigmartial_: will you drive today?11:00
martial_#start-meeting scientific-sig11:00
martial_#startmeeting scientific-sig11:01
openstackMeeting started Wed Mar 27 11:01:00 2019 UTC and is due to finish in 60 minutes.  The chair is martial_. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.11:01
*** openstack changes topic to " (Meeting topic: scientific-sig)"11:01
openstackThe meeting name has been set to 'scientific_sig'11:01
martial_#chair oneswig11:01
openstackCurrent chairs: martial_ oneswig11:01
oneswigup, up and away11:01
martial_Good morning team11:01
*** yamamoto has joined #openstack-meeting11:01
*** verdurin has joined #openstack-meeting11:01
oneswig#link Agenda for today
oneswigMorning verdurin11:02
martial_Today we have an exciting agenda (as always :) )11:02
martial_#topic Evaluation of hardware-specific machine learning systems orchestrated in an OS cluster at NIST11:02
*** openstack changes topic to "Evaluation of hardware-specific machine learning systems orchestrated in an OS cluster at NIST (Meeting topic: scientific-sig)"11:02
martial_We welcome Maxime and Alexandre to talk to us about the work they did on their project for NIST11:03
oneswigThank you for coming!11:03
martial_For people that want to follow up at home the link to the outline for their presentation is at11:03
martial_and it has been accepted as a lighting talk for the Denver Summit11:03
oneswigWhat is Multimodal information?11:04
martial_Alex, Maxime: the floor is yours11:04
maxhub_Thanks for welcoming us, that's a great opportunity to dry-run our presentation!11:04
alexandre_bThank you for this opportunity, Multimodal Information is a group of researchers that performs evaluation on machine learning systems11:05
maxhub_So first of all: hi everyone, we (Alexandre Boyer and Maxime Hubert), we are working at NIST and we are going to present to you how we automated our machine learning evaluation process using Openstack.11:05
alexandre_bThe Multimodal Information Group, which is part of the National Institute of Standards and Technology, often performs advanced evaluations and benchmarking of the performance of computer programs.11:06
alexandre_bThe main actors are:11:06
alexandre_b- The performers whose systems will be evaluated11:06
alexandre_b- The data providers who collect and send the data to evaluate the performers’ systems11:06
alexandre_b- The evaluators who design the evaluation steps and report the results11:06
*** zbr|ssbarnea has quit IRC11:06
*** zbr has joined #openstack-meeting11:07
maxhub_This is how we usually proceed11:07
maxhub_ - Collect and send the data sets to the performers: Data collection/delivery11:07
maxhub_ - Collect the system outputs from the performers11:07
maxhub_ - Score/Analysis of the Results11:07
maxhub_However, this approach has some caveats:11:07
maxhub_ - The data collection task may be (very) costly, and has to be performed for every new evaluation11:07
maxhub_ - Some agencies may not want their data to be released.11:07
maxhub_ - Systems are being evaluated on “known” data (some ML systems are good at learning)11:07
alexandre_bAll these constraints led us to rethink the evaluation process:11:08
alexandre_bNew evaluation tasks involving in-house system runs:11:08
alexandre_b- Collect the data sets: Data collection, deliver a Validation data set11:08
alexandre_b- Collect and validate the computer programs (aka Systems delivery)11:08
alexandre_b- Run the systems over the collected data, in our sequestered environment.11:08
alexandre_b- Score/Analysis of the results11:08
alexandre_bThis process is raising this new question: How to deliver a system to guarantee that it will run in-house?11:08
alexandre_b- OS Virtualization (containers) or Full Virtualization (VMs) to leverage all the configuration hassle11:08
alexandre_b- The system can be run against the Validation data set in advance11:08
alexandre_bOnce the systems are delivered and validated, the evaluator still has to run them on the evaluation data sets. This could be done manually but would require a lot of time if a lot of systems have to be evaluated against a lot of data sets.11:08
*** yamamoto has quit IRC11:08
*** yamamoto has joined #openstack-meeting11:08
oneswigWhat kind of machine learning frameworks were you using and what were the use cases?11:09
martial_To support what project?11:09
martial_Also, explain the constraints that control the use of resources and the solutions to alleviate those, please11:11
maxhub_this process was applied during a NIST evaluation consisting of six systems performing activity detection on cctv footage: some dozens of hours of video were processed by six systems in different chunks11:11
verdurinAny special considerations with the GPUs?11:12
maxhub_The teams designing the systems had the freedom to pick whatever framework they wanted too.11:12
maxhub_The configuration consisted in the following:11:13
maxhub_    16 cores (32 hyperthreaded)11:13
maxhub_    128GB of memory11:13
maxhub_    4 x Nvidia GTX1080Ti11:13
maxhub_    40GB root disk space11:13
maxhub_    256GB of ephemeral SSD disk space mounted to /mnt/11:13
martial_per VM or system?11:14
maxhub_One system consisted of one VM only so far, but we expect to receive multi-VMs systems in the next few months11:16
martial_so 4x GPU per VMs ... nice :)11:16
verdurinAnd this was with GPU passthrough, not Ironic?11:17
maxhub_Yes it was11:18
oneswigDid you deploy OpenStack specifically for managing this evaluation work?11:19
martial_you are listing "4 x Nvidia GTX1080Ti" in a server system or a desktop system (ie which chassis was used to support the non server version)?11:20
alexandre_bYes we deploy OpenStack specifically for this evaluation work11:20
martial_what prevents exfiltration of information?11:21
martial_In case people have questions, would you be okay adding your contact information in the outline document?11:23
verdurinDid you use specific node-cleaning in between runs?11:23
maxhub_We would give one node to each team so they can integrate their system on it first through an Openstack project, and collect the images and volumes one they were ready.11:24
maxhub_The last step for us was to automate the runs of the systems: We abstracted the system runs so all pairs of systems/datasets can be executed the same way. A job scheduler would instantiate the systems and trigger them. This only required a change to our Systems delivery: we Collected and validated the computer programs wrapped into a standard CLI/API.11:24
alexandre_bmartial what do you mean by server system system or desktop system?11:25
maxhub_Data exfiltration was prevented by cutting the internet access to the VMs before pluggin in our datasets11:26
martial_1080s have a connector for power that make them hard to use in a server form factor usually11:27
verdurinDetail on that last step you described would be interesting11:27
*** cheng1_ has quit IRC11:27
verdurinmartial_: we have a number of server systems like that11:27
martial_alexandre_b + verdurin: investigating server box to use :)11:28
maxhub_Instantiating the VMs over and ever again would make our nodes run out of memory sometimes, we had this problem when we had to deal with several image versions at the beginning. So the node cleaning would consist in deleting the past images on the nodes11:28
verdurinmaxhub_: Sure, I was wondering whether you had other cleaning processes in addition, given that you imply the need for strong isolation between groups11:29
martial_what are your lessons learned?11:32
maxhub_No we didn't, each system instanciation was offering a clean environment so we didn't feel the needs for any other cleanup11:32
alexandre_bHow Openstack made this possible for us:11:33
alexandre_bSystems delivery:11:33
alexandre_b- Opening an Openstack project per team for a limited amount of time allowed performers to remotely integrate their system on our hardware that can be specific (specific set of GPUs, SSDs). Performers have one VM per system.11:33
alexandre_b- The ability to “snapshot” the state of a system made it easy to deliver, as well as easy to re-deploy. One system can consist of one or several images and volumes.11:33
alexandre_bOpenstack already provided all the mechanisms to help us improving our systems delivery: it’s easier for the evaluator to collect the systems, and easier for the performers who can integrate their systems directly.11:33
alexandre_bRun the systems11:33
alexandre_b- An NFS server instance using OS Cinder allowed us to distribute large amounts of data to different systems at the same time11:33
alexandre_b- The use of VMs + OS security group mechanisms helped to leverage the requirements in terms of security and protection against data exfiltration11:33
alexandre_b- VMs snapshots guaranteed the replicability needed when performing experiments11:33
alexandre_b- A job scheduler using the OS API helped us to automate the instantiation and execution of our systems.11:33
maxhub_Lessons learned: Openstack is a good tool to work with, but is not designed to support the instantiation of a lot of VMs at the same time11:34
oneswig"A job scheduler using the OS API" - what was that?11:34
martial_so basically using the openstack CLI to run the VM?11:34
maxhub_Yes, after abstracting the systems into Heat templates11:35
martial_any "wrapper" type technology to start/control the process within the VM?11:35
maxhub_The system delivery would require teams to implement specific entrypoints11:36
alexandre_bWe use a job scheduler developed in-house similar to Slurm, and it allows us to instanciate/delete Openstack instances, sequestered the network thanks to the OpenStack API11:36
martial_so firewall rules?11:37
martial_anything else that you want to share on your work that you have not shared yet?11:38
martial_or is the rest secrets for the lighting talk? :)11:39
maxhub_Right now we are working on generalizing this evalutation process,11:39
maxhub_This would imply using more resource management technologies (Terraform for example)11:39
martial_Speaking of ligthing talks, oneswig do we have space available you think for them to talk to our audience?11:40
maxhub_And using a more advanced Job scheduling technology (Airflow)11:40
maxhub_Thanks for listening to listening to us!11:40
oneswigmartial_: I expect so.11:41
oneswigmaxhub_: alexandre_b: Thanks to both of you.11:41
oneswigAre you done with the project now or will you continue to work on it?11:42
martial_was looking for the link to the Etherpad to share with them, do you have it handy oneswig ?11:42
*** e0ne has quit IRC11:42
oneswigI am not sure if there is one yet.  I think Blair might have set one up.11:42
verdurinYes, thanks for presenting.11:43
alexandre_bWe will be working on it for at least another year11:43
alexandre_bThanks for listening to us11:44
oneswigI hope the next steps go well11:44
oneswigOK, let's move on11:46
oneswig#topic Open Infra Days London11:46
*** openstack changes topic to "Open Infra Days London (Meeting topic: scientific-sig)"11:46
oneswigThis is 1st April (ie Monday), and there's a scientific track11:46
martial_(was looking for Etherpad link, no luck)11:47
oneswigincluding a nice chap from Oxford, I believe...11:47
martial_(maxhub_ alexandre_b will share with you when I have it)11:47
oneswigverdurin: there's always plenty of interest in the AAI system on your infrastructure11:47
martial_cool :)11:47
oneswig#topic Denver Forum Sessions11:49
*** openstack changes topic to "Denver Forum Sessions (Meeting topic: scientific-sig)"11:49
martial_No dates yet?11:50
oneswigWe had a mail from Rico Lin to highlight this session11:51
oneswig#link Help most needed for SIGs and WGs
oneswigmartial_: for the PTG session?  I don't think I've seen anything confirmed11:51
oneswigFor the forum session, we'd need to re-think what the gaps may be for OpenStack support for research computing.11:53
oneswigAnd that's probably a session in itself.11:54
*** e0ne has joined #openstack-meeting11:54
martial_I would agree11:55
martial_any update on ISC?11:56
*** e0ne has quit IRC11:56
oneswig#topic AOB11:56
*** openstack changes topic to "AOB (Meeting topic: scientific-sig)"11:57
oneswigNot heard anything yet I don't think11:57
oneswigJust checking when we should hear11:58
oneswigApril 10th11:58
martial_for ISC, I am on the program chair for HPCW11:58
martial_"5th High Performance Containers Workshop - In conjunction with ISC HIGH PERFORMANCE 2019"11:59
martial_(program committee)11:59
oneswigInteresting, not seen that before11:59
martial_Christian Kniep was organizing it12:00
martial_We started this conversation at SC1912:00
oneswigI was wondering where Christian was, assumed he'd be involved somewhere...12:00
martial_so inviting submissions obviously :)12:00
*** number80 is now known as hguemar|lunch12:00
oneswigLet's put it on the agenda for next time12:00
oneswigTime to close!12:00
*** hguemar|lunch is now known as number8012:00
martial_Waiting to hear back from him, but not at Docker anymore it seems12:00
oneswigFinal comments?12:00
martial_Thanks for a great session everybody :)12:01
oneswigIndeed, thanks12:01
*** openstack changes topic to "OpenStack Meetings ||"12:01
openstackMeeting ended Wed Mar 27 12:01:19 2019 UTC.  Information about MeetBot at . (v 0.1.4)12:01
openstackMinutes (text):
*** e0ne has joined #openstack-meeting12:03
martial_good meeting team12:04
martial_oneswig: coming to PEARC19?12:04
oneswigSadly no.12:05
oneswigWhen is it?12:05
martial_July in Chicago12:06
martial_I proposed a "HPC using clouds" panels12:07
*** e0ne has quit IRC12:07
martial_we will see what happens (the usual US OpenStack team for Denver / SC19)12:08
oneswigHave fun with that :-)12:08
*** oneswig has quit IRC12:09
martial_was going to ask you if you wanted in ;012:09
*** e0ne has joined #openstack-meeting12:12
*** markvoelker has quit IRC12:21
*** jamesmcarthur has joined #openstack-meeting12:23
*** liuyulong_zzzZ is now known as liuyulong12:31
*** jamesmcarthur has quit IRC12:32
*** e0ne has quit IRC12:37
*** pcaruana has quit IRC12:39
*** cheng1_ has joined #openstack-meeting12:39
*** pcaruana has joined #openstack-meeting12:42
*** pcaruana has quit IRC12:42
*** pcaruana has joined #openstack-meeting12:43
*** mdbooth_ is now known as mdbooth12:44
*** lbragstad has joined #openstack-meeting12:46
*** jamesmcarthur has joined #openstack-meeting12:51
*** jamesmcarthur has quit IRC12:52
*** jamesmcarthur has joined #openstack-meeting12:52
*** fatema_ has joined #openstack-meeting13:07
*** jhesketh has quit IRC13:10
*** cheng1_ has quit IRC13:19
*** lseki has joined #openstack-meeting13:23
*** eharney has joined #openstack-meeting13:23
*** jamesmcarthur has quit IRC13:28
*** mjturek has joined #openstack-meeting13:33
*** e0ne has joined #openstack-meeting13:36
*** enriquetaso has joined #openstack-meeting13:37
*** rbudden has joined #openstack-meeting13:43
*** jamesmcarthur has joined #openstack-meeting13:44
*** priteau has quit IRC13:44
*** vishalmanchanda has quit IRC13:56
*** hongbin has joined #openstack-meeting13:56
*** mlavalle has joined #openstack-meeting14:01
mlavalle#startmeeting neutron_l314:01
openstackMeeting started Wed Mar 27 14:01:34 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
*** jamesmcarthur_ has joined #openstack-meeting14:02
mlavallehow are you all?14:02
*** igordc has joined #openstack-meeting14:03
ralonsohVery well!14:03
mlavalleigordc: hi, welcome14:03
igordcI'm alright, thanks14:04
mlavalle#topic Announcements14:04
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"14:04
mlavalleTwo announcements:14:05
*** jamesmcarthur has quit IRC14:05
mlavalle1) We cut RC-1 over the weekend and yesterday during the Neutron weekly meeting we decided that there won't be another RC this cycle14:06
mlavalleso we are merging code to master as normal again14:06
mlavalle2) We have an etherpad to propose topics for the PTG in Denver:
mlavalleI can see that 13 people have already registered and 11 confirmed attendance to social event Friday night14:08
mlavalledavidsha is attending!14:08
mlavalleigordc: are you planning to be in Denver?14:08
njohnstonLooking forward to seeing davidsha again!14:09
igordcmlavalle, no, manjeets will be covering for me14:09
ralonsohigordc, what a pity...14:09
igordcralonsoh, so close but so far... :)14:10
mlavalleigordc: ok, please look at line 47 of the etherpad. We want to review DVR openflow. the idea is that I would like to merge the code as eary as possible in the cycle, ideally before T-1, so we can debug it for the rest of the cycle14:11
mlavallemanjeets should be ready to discuss the status in Denver14:11
igordcmlavalle, yep14:11
mlavalleigordc: cool14:11
mlavalleany other announcements?14:12
igordcmlavalle, I'm also going to stay on etherpad and IRC during the PTG.. any plans for attempting live streaming like those few times before?14:12
mlavalleigordc: we have done that before. I will try it again this time aorund. Worst case, we can have a hangout with you on the dvr topic14:13
igordcmlavalle, awesome14:14
mlavallenjohnston: nice topic: IPAM... I agree14:14
mlavalleok next topic...14:15
mlavalle#topic Bugs14:15
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"14:15
njohnstonI'm interested in the DVR openflow discussion as well.  I'm especially interested in how we can manage the complexity of having so many kinds of DVR and supporting them all adequately.  I think the instability of the DVR+L3HA job shows us that there is real operational and cognitive overhead there.14:15
mlavallenjohnston: also agree14:16
mlavalleand that includes lack of documentation14:16
igordcnjohnston, I can see how dvr openflow can potentially also make things a bit more stable since there are less moving parts overall14:17
liuyulongIt may needs more dev cycle to make it stable. Please follow the team and trace the bug to make it steady.14:17
igordcnjohnston, but to get to feature parity with classic backend would still take a long while14:17
igordcliuyulong, yep14:17
mlavalleok, first bug today:14:18
openstackLaunchpad bug 1789434 in neutron "neutron_tempest_plugin.scenario.test_migration.NetworkMigrationFromHA failing 100% times" [High,In progress] - Assigned to Miguel Lavalle (minsel)14:18
mlavalleI think we can close this one with the merge of
mlavalleand done14:19
mlavalleNext one is
openstackLaunchpad bug 1821912 in neutron "intermittent ssh failures in various scenario tests" [High,Confirmed]14:19
mlavalleThis is a bug report that we talke about yesterday during the CI meeting14:20
mlavalleit is intended to be a collective effort14:20
*** cheng1 has joined #openstack-meeting14:20
mlavallesince at this point we haven't found a unifying pattern14:20
mlavalleso slaweq and I will be using the logstash query to find cases and then dig deeper in them14:21
mlavalleothers are welcome to do the same14:21
slaweqthere is a lot of such examples in logstash, so it's easy to find :)14:21
*** maxhub_ has quit IRC14:21
mlavalleslaweq: thanks for filing it14:22
*** xubozhang has joined #openstack-meeting14:22
slaweqyw mlavalle :)14:22
mlavallewe also have
openstackLaunchpad bug 1774459 in neutron "Update permanent ARP entries for allowed_address_pair IPs in DVR Routers" [High,Confirmed] - Assigned to Swaminathan Vasudevan (swaminathan-vasudevan)14:22
mlavalleprogress on this has stalled since early January14:23
mlavalleI'll send a message to swami today and ask about it14:24
mlavalleif anyone wants to tackle this, please feel free14:24
mlavallethose are all the bugs I have today14:25
mlavalleany other bugs we should discuss?14:25
liuyulongI have14:26
openstackLaunchpad bug 1819160 in neutron "Functional tests for dvr ha routers are broken" [High,In progress] - Assigned to LIU Yulong (dragon889)14:26
liuyulongFor now, I think we have found the root cause of this failure.14:26
igordcoh I've been a victim of that one14:26
liuyulongThat HA failover bridges veth pair devices were not set UP during the test.14:27
liuyulongThis causes the VRRP advertisement packet can not pass to each HA port. So they set themselves all 'master'.14:27
slaweqliuyulong: but it is needed together with IIUC14:27
liuyulongslaweq, Yes14:28
*** alexandre_b has quit IRC14:28
liuyulongFor this patch, we are going to give each HA case a specific VRRP id.14:28
liuyulongAnd each HA port a independent IP address.14:28
liuyulong There are some more cases need to add such IP, not only the failover cases.14:29
liuyulongralonsoh's patch may also be needed.14:30
ralonsohso we need 1) the veth links up, 2) make the IP different and 3) check both routers status14:31
liuyulongralonsoh, yes14:31
liuyulongralonsoh's patch handled the situation is router2 can also be 'master' during the test.14:32
mlavalleis this latter patch rebased on one of the former two?14:32
ralonsohI'll rebase my patch to yours, liuyulong14:32
mlavalleralonsoh: +++14:33
liuyulongralonsoh's patch can be independent.14:33
igordcis it worth doing some manual testing of this? any recommendations to try and make it fail?14:33
liuyulongigordc, I just run tox locally14:34
mlavalleanything else on this bug?14:35
mlavalleany other bugs?14:36
liuyulongNot from me14:36
igordcmlavalle, if I suspect a bug, is this a good place to mention it or just I first report it in launchpad always?14:37
mlavalleok, let's move on14:37
igordcor should I first*14:37
mlavalleigordc: just report it in launchpad at tag it l3-dvr-backlog14:37
igordcmlavalle, what's the tag for non dvr?14:38
igordcmlavalle, thanks14:39
mlavalleok, moving on14:39
mlavalle#topic openflow dvr14:39
*** openstack changes topic to "openflow dvr (Meeting topic: neutron_l3)"14:39
mlavalleigordc: you are up14:39
igordcxubozhang also in the house14:39
igordcanyway, we've been polishing what we have14:40
*** vishalmanchanda has joined #openstack-meeting14:40
igordcI've personally started the implemention of legacy for dvr, but am facing some issues and doubts regarding existing DNAT and SNAT in the openflow dvr patch14:40
igordcI don't see any risk for the scope we discussed on the mailing list except the scenario job, for <train-114:41
*** janki has quit IRC14:41
igordcso I'd like to ask whether merging every needed patch without a scenario job is something acceptable before train-1.... and later work on the scenario job?14:41
mlavalleI think that's ok14:42
mlavallelet's just try to keep things close to T-114:42
igordcI'm also moving to other work at the moment, but will continue to hold the l3 agent refactor.. xubozhang will mostly hold the openflow dvr patch14:43
igordcmlavalle, yep14:43
igordcplease review once I rebase it again14:43
igordcI expect it will be controversial due to the existing agent changes, so time will be needed to address things14:44
mlavalleyes, that is why I want to do this early14:44
mlavalleare thse all the patches:
igordcmlavalle, that's right, that is the new topic per liuyulong's recommendation14:45
*** munimeha1 has joined #openstack-meeting14:45
igordcmlavalle, we will tag the commit with it too so it doesn't reset the topic14:45
mlavalleok I will add it to the blueprint in launchpad14:45
liuyulongYes, it is based on the BP name.14:45
mlavallethat way it is easy to find the patches14:46
*** priteau has joined #openstack-meeting14:46
igordcalso something that might not be clear:14:47
*** awaugama has joined #openstack-meeting14:47
igordcthe refactor patch actually depends on yang's router factory patch:
mlavalleahh good point14:48
mlavallemaybe we should put this patch under the samae topic14:50
mlavallegerrit topic^^^^14:50
*** e0ne has quit IRC14:50
mlavalleanything else?14:51
igordchaleyb, what's the state of neutron + ovn + dvr today?14:51
mlavalleI don't think he is in the meeting today14:53
igordcthat's all from my side14:53
mlavallethanks for the update igordc14:53
mlavalle#topic On demand agenda14:53
*** openstack changes topic to "On demand agenda (Meeting topic: neutron_l3)"14:53
mlavalleanything else we should discuss today?14:54
mlavalleok, thanks for attending14:55
mlavalleespecially you liuyulong and igordc. These are odd hours for you14:55
igordcthank you!14:55
*** openstack changes topic to "OpenStack Meetings ||"14:55
openstackMeeting ended Wed Mar 27 14:55:37 2019 UTC.  Information about MeetBot at . (v 0.1.4)14:55
openstackMinutes (text):
*** e0ne has joined #openstack-meeting15:02
e0ne#startmeeting horizon15:03
openstackMeeting started Wed Mar 27 15:03:24 2019 UTC and is due to finish in 60 minutes.  The chair is e0ne. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:03
*** openstack changes topic to " (Meeting topic: horizon)"15:03
openstackThe meeting name has been set to 'horizon'15:03
*** openstack changes topic to "OpenStack Meetings ||"15:03
openstackMeeting ended Wed Mar 27 15:03:30 2019 UTC.  Information about MeetBot at . (v 0.1.4)15:03
openstackMinutes (text):
*** artom has quit IRC15:11
*** a-pugachev has quit IRC15:13
*** a-pugachev has joined #openstack-meeting15:15
*** eharney has quit IRC15:28
*** eharney has joined #openstack-meeting15:29
*** cheng1 has quit IRC15:34
*** carlos_silva has joined #openstack-meeting15:48
*** a-pugachev has left #openstack-meeting15:48
*** woojay has joined #openstack-meeting15:49
*** e0ne has quit IRC15:49
*** diablo_rojo has joined #openstack-meeting15:49
*** e0ne has joined #openstack-meeting15:53
*** abishop has joined #openstack-meeting15:57
*** rosmaita has joined #openstack-meeting15:57
jungleboyj#startmeeting Cinder16:00
openstackMeeting started Wed Mar 27 16:00:47 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 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:01
*** thgcorrea has joined #openstack-meeting16:01
_pewp_jungleboyj ( *՞ਊ՞*)ノ16:01
geguileohi! o/16:01
jungleboyjHey everyone.16:02
jungleboyjLooks like a good showing.16:02
jungleboyjThanks team.16:02
*** efried is now known as efried_rollin16:02
jungleboyjHappy Wednesday.16:03
jungleboyjSo, lets get started.16:04
jungleboyjFirst ...16:04
*** walshh_ has joined #openstack-meeting16:04
jungleboyjAs you guys noted last week, I will be PTL for another cycle.16:04
jungleboyjThank you for your vote of confidence?  :-)16:04
whoami-rajatjungleboyj: could you provide the etherpad link please.16:05
jungleboyje0ne:  Thanks.16:05
rosmaitajungleboyj: thank you for your service16:05
e0nejungleboyj, whoami-rajat: np16:05
jungleboyjThings have been a little crazy the last month or two and I am appreciative to all who have helped keep things moving forward.16:05
*** davidsha has joined #openstack-meeting16:06
jungleboyjWorking to schedule things better for this release so that things will go a bit smoother.16:06
jungleboyjSo, looking forward to riding the Train with you all.16:06
*** artom has joined #openstack-meeting16:06
jungleboyjThanks to smcginnis  for covering me last week while I was dealing with a family issue.16:06
jungleboyjOk, moving on ...16:06
jungleboyj#topic announcements16:06
*** openstack changes topic to "announcements (Meeting topic: Cinder)"16:06
*** artom has quit IRC16:06
jungleboyjWe are in RC2 week for Stein.16:07
*** artom has joined #openstack-meeting16:07
jungleboyjI think we have had a couple of things backported to stable/stein.16:07
jungleboyjNeed to look and see if it is worth cutting an RC2 for.16:08
jungleboyjrosmaita: Have any thoughts there?16:08
rosmaitai think we should, unless there's more coming in16:08
rosmaitathere are a bunch of patches to master that haven't been backported16:08
rosmaita(some may be train stuff, though)16:09
smcginnisWe may want to wait a little to see if any translations come in.16:09
*** Lucas_Gray has quit IRC16:09
rosmaitagood point, they came into master pretty recently16:09
jungleboyjSo, lets plan to cut an RC2 tomorrow.16:09
jungleboyjIf you have anything that you need to get to stable/stein, please propose the backports ASAP.16:10
jungleboyjMake sense to everyone?16:10
rosmaitasmcginnis: the stein translations will be proposed there directly, right? we don't backport the ones that came into master?16:11
jungleboyjI will take that as a yes.  Cores, please watch for any stable/stein patches.16:12
whoami-rajatjungleboyj: should i propose the filtering patch to stein?16:12
e0nerosmaita: yes, we don't need to backport translations manually16:12
jungleboyjwhoami-rajat:  Can you remind me which one that is?16:12
jungleboyjwhoami-rajat:  I am ok with that.  Any objections eharney hemna_ ?16:13
eharneysounds like a good idea to me16:13
jungleboyjOk.  whoami-rajat  Please do that.16:14
whoami-rajatjungleboyj: eharney done
jungleboyjwhoami-rajat:  Cool.  Will give it a +2 once it passes the check.16:14
rosmaitathat cherry-pick button was a good invention16:14
whoami-rajatjungleboyj: thanks16:15
* jungleboyj keeps forgetting about that.16:15
whoami-rajatrosmaita: agreed!16:15
jungleboyjAnything else there?16:15
jungleboyjOk.  Moving on.16:16
jungleboyjI now have the mid-cycle summary up.  I am sorry that this took so long to get in place.16:16
jungleboyjI have summarized all the todos.  Please take a look and see if you have a todo and take it.16:17
jungleboyjI have started working on my todos already.16:17
*** gyee has joined #openstack-meeting16:17
jungleboyjIf there are unassigned Actions, please consider taking one.16:17
jungleboyjThank you to all who have helped there and attended.16:18
jungleboyjFinal announcement.16:18
jungleboyjPlease help with the Denver PTG planning.16:18
jungleboyjI have populated some topics on there based on what I found in the Actions from the mid-cycle.16:19
jungleboyjThe more topics we can get proposed, the more productive a time we will have.16:19
jungleboyjHopefully people saw that the strawman schedule for the PTG has been announced.16:20
rosmaitai managed to miss that, i need to adjust my email filters16:20
whoami-rajatjungleboyj: i think eharney assigned the untyped volumes spec to me?16:21
jungleboyjI was just looking for the schedule16:21
jungleboyjSo, we have Thursday afternoon through Saturday.16:23
jungleboyjWho all is planning to attend at this point in time?16:24
jungleboyjI will be there.16:24
jungleboyjOk, that is a good start.16:25
jungleboyjI think geguileo as well?16:25
eharneyno, unfortunately16:25
*** yamamoto has quit IRC16:25
jungleboyjOk, so hopefully he can attach remotely at least.16:25
geguileojungleboyj: nop, I'll just attend the summit16:25
jungleboyjOh, Summit only?  Ok.16:25
geguileojungleboyj: it was my best friend's wedding during the PTG  :-(16:26
jungleboyjOh.  Well that is fun.16:26
eharneybut Cinder is also your best friend16:26
* jungleboyj laughs16:26
rosmaitayou can give him a tarball as a wedding present16:26
geguileoeharney: but it's not getting married  ;-P16:26
*** luizbag has joined #openstack-meeting16:26
jungleboyjgeguileo:  Cinder loves you.16:26
jungleboyjrosmaita:  ++16:26
jungleboyjrosmaita:  That is wonderfully nerdy.16:27
rosmaitaand probably more useful than a toaster?16:27
jungleboyjOk, so we will either chat during the Summit or something like that.16:27
jungleboyjWe will need to get together for dinner before you leave.16:27
jungleboyjAs a team.16:27
geguileoI would love that  :-)16:27
jungleboyjSounds good.16:28
jungleboyjAny other discussion around the PTG?16:28
xyangI’ll be at the summit too16:29
jungleboyjxyang:  Oh cool.  Will be good to see you.16:29
jungleboyjwhoami-rajat:  Will you be able to look at the untyped volumes discussion?16:30
whoami-rajatjungleboyj: yes.16:31
jungleboyjOk.  Good.  Thank you.16:31
jungleboyjOk.  Moving on for real now.16:31
jungleboyj#topic Stein cinderclient update16:31
*** openstack changes topic to "Stein cinderclient update (Meeting topic: Cinder)"16:31
rosmaitawe had a small snafu with where the cinderclient stable/stein branch was cut16:32
rosmaitaanyway, thanks to everyone who has reviewed the patches16:32
rosmaitaonly 2 left16:32
rosmaitathat one i think should go in, has 1 +216:33
rosmaitathe other one i thought might cause backport problems if we left it out, but now i think it's probably ok to skip:16:33
jungleboyjOk, I will approve the first one unless someone has a major concern.16:33
jungleboyjI think the objectives are overly picky.16:34
rosmaitaso we've basically caught stable/stein up with master at this point16:34
*** ttsiouts has quit IRC16:34
*** ttsiouts has joined #openstack-meeting16:35
jungleboyjOoops, both Sean and I +Wd.16:35
jungleboyjWell, we made our statement.16:35
jungleboyjrosmaita:  Great.  Thank you!16:35
smcginnisSuper approval!16:35
rosmaitamy ask is that if people agree that is not necessary, please -2 it and i can abandon it16:35
jungleboyjdah dah daaaah!16:35
smcginnisrosmaita: Yeah, I think that one can be abandoned. It's useful, but less so on a stable branch.16:36
rosmaitathat's all from me16:36
jungleboyjsmcginnis: ++16:36
smcginnisrosmaita: Besides, I don't really trust the guy that wrote it. :)16:36
jungleboyjHe he.16:37
jungleboyjrosmaita:  So once the last couple of things are merged you will do a new release?16:38
rosmaitai think i have to wait until after the coordinate Stein release?16:38
jungleboyjrosmaita:  Yeah, that sounds right.16:38
rosmaitaor did we want to propose an exception and update global requirements?16:38
*** tssurya has quit IRC16:39
smcginnisI don't think there's anything release critical for stein. So we can just do a stable release once things open up again.16:39
eharneyit seems ok to wait to me16:39
jungleboyjsmcginnis:  ++16:39
*** ttsiouts has quit IRC16:40
jungleboyjOk.  So, last topic.16:40
jungleboyj#topic Consistency Groups removal16:40
*** openstack changes topic to "Consistency Groups removal (Meeting topic: Cinder)"16:40
e0nethanks, jungleboyj!16:40
e0neI just want to sync with the team on this topic16:41
jungleboyjWelcome.  :-)16:41
e0neare we going to remove CGs support in Train release?16:41
eharneyCGs that aren't through the generic groups API, i assume16:42
e0neeharney: exactly16:42
jungleboyjSo, the way we left it at the mid-cycle was that smcginnis was going to investigate and see if it was a possibility with the goal of dropping it in Train.16:42
*** jamesmcarthur_ has quit IRC16:42
jungleboyjI think smcginnis took that todo.16:42
e0neso it looks like it's safe to remove it from horizon16:43
e0nehorizon supports generic groups now16:43
whoami-rajate0ne: isn't it better to remove it from cinder first?16:44
e0newhoami-rajat: sure16:44
jungleboyje0ne:  Yeah, I think it is probably best to make sure we remove it from Cinder and then remove it from Horizon.16:44
e0nehorizon now follows the same deprecation policy and projects16:44
e0nejungleboyj: +116:45
smcginnisI thought we had already disabled the CG APIs16:45
smcginnisI did not get a chance to dig through that more.16:46
smcginnisOh, we did mark it deprecated in the api-ref at least:
smcginnisSo I think it makes sense for Horizon to stop using them.16:46
jungleboyjOk, so that means we can remove them in Train then?16:47
e0neafair, it's deprecated, but still enabled16:47
smcginnisThe problem is microversions. We can bump a microversion that drops them, but would still need to have it there for older MVs.16:48
*** enriquetaso has quit IRC16:48
e0nesmcginnis: :(16:48
jungleboyjThat sounds kind of yucky.16:49
whoami-rajatsmcginnis: isn't there a way to remove a feature if no more used in MVs?16:49
e0nebut CGs are in API extensions. we don't nave microversions for them16:49
smcginnisThe only thing that gains us is - if we do what was discussed at the Forum in Vancouver - someday we could decide that microversion 3.87 (example) has been stable for awhile and make a v4 API starting from that point.16:49
smcginniswhoami-rajat: I suppose for older versions we can keep the API endpoints there and just have them return some 400 error.16:50
eharneyif we have to keep the CG APIs around, can they not be mapped into the generic group code?  (i feel like we considered this at one point)16:50
smcginnisOr maybe something like a 301 with reference to the new API?16:50
jungleboyjeharney:  I do feel like we considered that.16:51
smcginnisMaybe we did.16:51
*** enriquetaso has joined #openstack-meeting16:51
smcginnisJust noticing, other than a small change for the update call, this was a contrib API. So maybe we can drop it.16:51
jungleboyjSo, given that the API is deprecated it seems like Horizon could remove it.  Anyone disagree there?16:52
smcginnisSince those contrib APIs were not "official".16:52
rosmaitayes, no sense in horizon supporting a deprecated API16:52
e0nesmcginnis: :)16:52
eharneyis it really a contrib API..?16:53
whoami-rajate0ne: i think horizon completely supports volume groups in project and admin panel now?16:53
smcginnisLike quotas and a few other core things.16:53
jungleboyjSo, lets land on that agreement and work on solving this problem in Denver?16:53
smcginnisI did verify, the cg API does call through to the group code.16:53
e0newhoami-rajat: yes, since Stein16:54
smcginnisBut either way, I agree Horizon should stop using the deprecated APIs.16:54
smcginnis5 minutes16:55
eharney  doesn't look very contrib-y, but i'm not sure16:55
e0nesmcginnis: great!16:56
smcginniseharney: Yeah, that kind of uncontrib'd it I guess.16:56
jungleboyjSo, lets get it out of Horizon.16:56
e0neanyway, it's deprecated and uses generic groups api inside. we can drop it from horizon now :)16:56
jungleboyjAnd decide what to do in the future.16:57
smcginnise0ne: ++16:57
xyange0ne: good call.  +1 to remove call to cg api16:57
jungleboyjOk, anything else we need to cover in the last couple of minutes.16:58
jungleboyjI guess not.16:59
jungleboyjThanks to everyone joining.16:59
e0nesee you next week17:00
jungleboyjHave a good rest of your week and thanks for helping get Stein out!17:00
rosmaitaquick reminder to stable cores:
*** openstack changes topic to "OpenStack Meetings ||"17:00
rosmaitaafter that merges i will propose RC-217:00
openstackMeeting ended Wed Mar 27 17:00:19 2019 UTC.  Information about MeetBot at . (v 0.1.4)17:00
openstackMinutes (text):
*** woojay has left #openstack-meeting17:00
jungleboyjrosmaita:  Thanks!17:00
*** e0ne has quit IRC17:01
*** a-pugachev has joined #openstack-meeting17:01
*** a-pugachev has left #openstack-meeting17:05
*** kopecmartin is now known as kopecmartin|off17:10
*** diablo_rojo has quit IRC17:20
*** diablo_rojo_ has joined #openstack-meeting17:20
*** priteau has quit IRC17:27
*** abishop has quit IRC17:27
*** diablo_rojo_ is now known as diablo_rojo17:28
*** davidsha has quit IRC17:28
*** mdbooth has quit IRC17:35
*** psachin has quit IRC17:36
*** cheng1 has joined #openstack-meeting17:43
*** priteau has joined #openstack-meeting17:43
*** iyamahat_ has joined #openstack-meeting17:44
*** iyamahat has quit IRC17:46
*** eharney has quit IRC17:47
*** luizbag has left #openstack-meeting17:52
*** ekcs has joined #openstack-meeting17:55
*** e0ne has joined #openstack-meeting18:04
*** jamesmcarthur has joined #openstack-meeting18:05
*** e0ne has quit IRC18:11
*** ralonsoh has quit IRC18:16
*** enriquetaso has quit IRC18:17
*** enriquetaso has joined #openstack-meeting18:20
*** electrofelix has quit IRC18:27
*** rossella_s has quit IRC18:39
*** priteau has quit IRC18:43
*** eharney has joined #openstack-meeting18:47
*** jamesmcarthur has quit IRC18:53
diablo_rojoStoryboard is skipping meeting this week! If you want to chat with us, join us in #storyboard :)18:54
*** rosmaita has left #openstack-meeting19:05
*** yamamoto has joined #openstack-meeting19:05
*** artom has quit IRC19:06
*** yamamoto has quit IRC19:10
*** hongbin has quit IRC19:15
*** jamesmcarthur has joined #openstack-meeting19:16
*** hongbin has joined #openstack-meeting19:28
*** sridharg has quit IRC19:30
*** cheng1 has quit IRC19:32
*** thgcorrea has left #openstack-meeting19:33
*** efried_rollin is now known as efried19:45
*** iyamahat_ has quit IRC19:49
*** yamahata has quit IRC19:49
*** erlon has joined #openstack-meeting19:53
*** pcaruana has quit IRC19:53
*** mdbooth has joined #openstack-meeting19:57
*** iyamahat has joined #openstack-meeting19:58
*** lbragstad has quit IRC20:05
*** hongbin has quit IRC20:07
*** erlon has quit IRC20:09
*** yamahata has joined #openstack-meeting20:17
*** mjturek has quit IRC20:31
*** mdbooth has quit IRC20:37
*** lbragstad has joined #openstack-meeting20:43
*** vishalmanchanda has quit IRC20:46
*** m_kazuhiro has joined #openstack-meeting20:56
timburke#startmeeting swift21:00
openstackMeeting started Wed Mar 27 21:00:50 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:01
timburkeagenda's pretty short21:01
timburke#topic Swift 2.21.021:02
*** openstack changes topic to "Swift 2.21.0 (Meeting topic: swift)"21:02
timburkeso we had a release! that'll be our stein release; stable branch has already been cut21:02
timburkea lot of great stuff went out in it; thanks to everyone for writing and reviewing patches, and just generally making swift better :-)21:03
timburke#topic pyeclib release21:04
*** openstack changes topic to "pyeclib release (Meeting topic: swift)"21:04
timburkeit's been a bit since we did one of these21:05
timburkeand i was thinking it might be good (by which i mean, it would make my life easier ;-)21:05
timburkeauthors/change log patch is up at
claygthings happen in swift for two reasons 1) make timburke's life easeir 2) for the lulz21:06
timburkeif anyone has anything else they'd like to see for that, you should probably speak up in the next couple days21:06
tdasilvafwiw, it would also make my life easier21:06
kota_only pyeclib? liberasurecode too?21:07
timburkekota_, i hadn't thought that hard about it :-)21:07
tdasilvai just need pyeclib for now, but we still have libec patch to review...21:07
mattoliveraumaking life easier is a great reason for a new release :)21:07
tdasilvaone sec, let me dig it up21:07
timburkeoh, yeah... zaitcev's patch might be good to release...21:08
clayg@timburke can we get them all on priority reviews between now and next meeting and plan to do the release the week after that (2 weeks from now-ish)?21:09
timburkeclayg, i think the stuff i'm really interested in releasing is landed... tdasilva's right that we should really review the quadiron patches (since we invited them to submit them and all), but idk that it should keep us from doing a release sooner rather than later21:10
claygwas the aim to get a new tagged released packaged by downstream as stein?21:11
timburkenope; too late for that. this'd be part of train regardless at this point21:11
timburkei just want something pip-installable that fixes
openstackLaunchpad bug 1780320 in PyECLib "If find_library('erasurecode') in does not return a library version, try to append it " [Undecided,Fix released]21:12
claygtdasilva: ok well at a minimum they have some pre-req "fix" patches that are probably good candidates for "priority" review along with zaitcev's crc32 fix thing?21:12
kota_yeah, if we need some patches for stein, anyway backporting to stable/stein branch is needed.21:12
tdasilvajust realized that libec is already 1.6.021:13
timburkeneither pyeclib nor liberasure code have stable branches, as i understand it21:13
claygso land good code and cut a release then do backports - is anyone against the timeline of "on priority review this week; merge what we can next week; then cut a release"?21:13
claygbam - stable branches are for scardy cats21:13
claygoh, the crc32 is already landed21:14
timburkefwiw, the lists of open patches are remarkably short:
claygso do we have important patches outstanding that we could realistically land before a release?  maybe timburke was just saying "new tag incoming"21:15
timburkei think the quadiron changes (and my prep-for-release patch) are the only "live" changes21:15
mattoliverauthen it's priority reviews until patches are landed or until we just want to cut a relase. be it next week or earlier (if things have landed)21:15
tdasilvaclayg: i don't think we have anything that is so important that needs to land before a release, agree quadiron could wait for next release as it will take a bit of time to land21:15
claygok, good talk 👍21:16
timburkeso, on to updates!21:16
claygalso WTG everyone who's been doing work/review on py/libec!  that's an amazingly short backlog21:16
*** _alastor_ has quit IRC21:16
timburkeclayg, it's almost like we don't really think much about it ;-)21:17
timburke#topic losf update21:17
*** openstack changes topic to "losf update (Meeting topic: swift)"21:17
timburkekota_, rledisez: how's the feature branch going?21:17
rlediseznot much move for the last days. alecuyer was working on a patch to automatically clean empty volumes. he will start working again on replacing grpc with http next week21:18
kota_sorry, not so much from my side because of business trip in the last week. I had asked to Norio to push their docs, he has bee preparing the patch I think.21:18
kota_I'll work in this week and the next to setup packaging and testing for that, in my plan.21:19
timburkecool! eventlet-friendly losf seems good, as do more docs :-)21:19
timburke#topic py3 updates21:20
*** openstack changes topic to "py3 updates (Meeting topic: swift)"21:20
timburkelooks like zaitcev isn't here today, but i know he's been pushing up patches for DLO recently21:20
timburkei've been spiking hard on getting some in-process functional tests running in the gate21:21
mattoliverautimburke: nice work on that21:21
timburkefor example,
timburkethey'll have similar ratchets as the unit tests. currently targeting py37 (largely because that's what i've got as my default py3)21:22
timburkeand mattoliverau's been working on getting staticweb running on py3!21:23
mattoliveraujust picked a middleware that hasn't been touched yet :)21:23
timburkei think that's about it for updates -- am i missing anything?21:24
timburke#topic open discussion21:25
*** openstack changes topic to "open discussion (Meeting topic: swift)"21:25
timburkesince we've got both rledisez and m_kazuhiro here, how about we bring up again?21:25
claygdoes it need another rev - or it's good to go?21:26
rledisezsure, give me a second to re-read the last answer of m_kazuhiro :)21:26
clayglooks like mostly docs21:27
m_kazuhiroYes. Another rev and rledisez's answer will be helpful for me.21:27
*** whoami-rajat has quit IRC21:28
*** rbudden has quit IRC21:28
mattoliveraufeel free to sqash the docs update into that patch if you want:
mattoliverauor we can land them one after the other, whatevs21:28
claygi thought object-server needed an internal-client so it couldn't use the object-server's config because that config already has a pipeline section that points to the object-server:app instead of the proxy:app?21:28
rledisezI guess we can ask here opinions: does it seem reasonable to decide of the behavior of a daemon based on the name of the config file?21:29
timburkeclayg, surely we could point to an internal-client.conf or something though, yeah?21:29
kota_mattoliverau: it looks like that patch already was squashed.21:29
m_kazuhiromattoliverau: I have already squashed the patch.21:29
mattoliverauoh, great21:29
mattoliveraunever mind me then :P21:30
claygi see some code that says "read_conf_for_queue_access" - but that's no on master is it?21:30
kota_mattoliverau: appreciated for working that :P21:30
claygoh it is21:30
timburkerledisez, that does seem a little odd...21:32
claygyeah i'm confused, having the object expirer use the internal-client.conf for the pipeline config seems absolutely brilliant tho...21:32
timburkewhy can't we just drive off the dequeue_from_legacy setting?21:33
claygso it looks like this patch is not done - or at least all the core reviewers that look at it get confused really quickly which isn't a great sign for "ready" - but maybe we need to do a better job of enumerating the complete set of issues which much be resolved if we want it to land21:34
timburkeseems about right21:35
claygAFAIK this is a pre-req for the generalized task queue which everyone thinks is a brilliant idea, so ... maybe I'll put it on my list for Friday?21:35
timburkeanyone have anything else to bring up?21:35
*** erlon has joined #openstack-meeting21:35
m_kazuhiroclayg: Thank you for your question review, I'll add answer review to the patch.21:37
claygtimburke: I hear this one person using s3api wants bulk delete to be more faster/async?  is that right?21:37
timburkeyup. so... i'm gonna be thinking about how to do that in a sane way21:37
timburkeit's looking... messy. like, i'm debating about making some REPLICATE requests from the proxy to clear out listings earlier. not sure yet about how good any of my ideas are21:38
rlediseztimburke: that's interesting, even for non-s3. i used to pass a regex with DELETE that was matching all entries of a container and create an object-expirer entry before removing the line from the container.21:39
timburkerledisez, that sounds rather similar to what i'm thinking about trying to do -- bulk-insert some expirer entries, then bulk-insert some tombstones...21:40
*** awaugama has quit IRC21:40
timburkehow did you get around the expirer wanting to send x-if-delete-at?21:40
rlediseztimburke:  it was 5 years ago (what, already?!) and we removed it from prod since, so I would have to check21:41
timburkeeh, don't worry too much -- just curious. my current plan is to use a distinct content-type on the expirer queue entry21:42
timburke seems like a good thing, but maybe a little scary21:43
timburke(Include some pipeline validation during proxy-server start-up)21:43
timburkewe've had a few bugs get reported that ultimately came down to badly-configured pipelines (or badly-behaved auto-insertion of required middlewares)21:44
timburkethat patch tries to prevent such situations from arising, but may keep your proxy from starting on upgrade (with old configs)21:45
mattoliverauyeah, I think we need to do something to ease pipeline issues. at least the major gotchas.21:45
timburke addresses some issues with our lower-constraints job, which apparently wasn't testing what we thought it was testing21:47
timburkeit involves a couple dependency up-revs (for cryptography and netifaces, in particular), but i think they're old enough that it shouldn't really impact anyone?21:48
timburkeif someone could take another look at that, i'd appreciate it -- i did enough to fix it up that i'm not sure i should be the one to +A21:49
claygtimburke: why can't you just +A that one - the infra guys all signed off - do you need someone else to load it into their head for any specific reason?21:49
timburkefine -- done :P21:50
timburkeanyone have anything else?21:50
claygI mean getting it on master is a great way to find out if it breaks "something else we don't know about" - and even then the remediation is the same "figure out how to have both things works and merge the fix"21:51
clayggetting it on master *right after a release I might say21:51
timburkeall right, i think i'm calling it then21:52
timburkethanks for coming everyone, and thank you for working on swift!21:53
*** openstack changes topic to "OpenStack Meetings ||"21:53
openstackMeeting ended Wed Mar 27 21:53:19 2019 UTC.  Information about MeetBot at . (v 0.1.4)21:53
openstackMinutes (text):
*** iyamahat_ has joined #openstack-meeting21:57
*** iyamahat_ has quit IRC21:59
*** m_kazuhiro has quit IRC21:59
*** iyamahat_ has joined #openstack-meeting22:00
*** iyamahat has quit IRC22:01
*** mlavalle has quit IRC22:11
*** raildo has quit IRC22:18
*** rcernin has joined #openstack-meeting22:31
*** jamesmcarthur has quit IRC22:33
*** jamesmcarthur has joined #openstack-meeting22:33
*** zhubx has quit IRC22:37
*** zhubx007 has joined #openstack-meeting22:37
*** diablo_rojo has quit IRC22:40
*** jamesmcarthur has quit IRC22:44
*** _alastor_ has joined #openstack-meeting22:46
*** erlon has quit IRC22:47
*** jamesmcarthur has joined #openstack-meeting22:48
*** jamesmcarthur has quit IRC22:51
*** munimeha1 has quit IRC22:51
*** _alastor_ has quit IRC22:51
*** jamesmcarthur has joined #openstack-meeting22:52
*** jamesmcarthur has quit IRC22:55
*** enriquetaso has quit IRC23:00
*** gibi has quit IRC23:03
*** carlos_silva has quit IRC23:04
*** mdbooth has joined #openstack-meeting23:04
*** mdbooth has quit IRC23:08
*** enriquetaso has joined #openstack-meeting23:16
*** gibi has joined #openstack-meeting23:22
*** iyamahat_ has quit IRC23:24
*** enriquetaso has quit IRC23:26
*** artom has joined #openstack-meeting23:32
*** jgriffith has quit IRC23:45
*** jgriffith has joined #openstack-meeting23:46
*** lbragstad has quit IRC23:48
*** tetsuro has joined #openstack-meeting23:58

Generated by 2.15.3 by Marius Gedminas - find it at!