Wednesday, 2018-11-21

*** LiangFang has quit IRC00:00
*** jamesmcarthur has quit IRC00:00
*** jamesmcarthur has joined #openstack-meeting00:07
*** tetsuro has quit IRC00:07
*** tetsuro has joined #openstack-meeting00:10
*** armax has joined #openstack-meeting00:13
*** mriedem has quit IRC00:17
*** a-pugachev has quit IRC00:25
*** yamamoto has quit IRC00:34
*** longkb has joined #openstack-meeting00:38
*** longkb has quit IRC00:38
*** jamesmcarthur has quit IRC01:05
*** jamesmcarthur has joined #openstack-meeting01:08
*** jamesmcarthur has quit IRC01:17
*** jamesmcarthur has joined #openstack-meeting01:18
*** jamesmcarthur has quit IRC01:22
*** iyamahat has quit IRC01:47
*** yamahata has quit IRC01:47
*** jamesmcarthur has joined #openstack-meeting01:56
*** rbudden has joined #openstack-meeting02:19
*** mhen has quit IRC02:50
*** anteaya has quit IRC02:51
*** mhen has joined #openstack-meeting02:52
*** zaneb has quit IRC03:23
*** zaneb has joined #openstack-meeting03:42
*** yamamoto has joined #openstack-meeting04:05
*** psachin has joined #openstack-meeting04:14
*** janki has joined #openstack-meeting04:42
*** iyamahat has joined #openstack-meeting04:52
*** iyamahat has quit IRC04:54
*** iyamahat has joined #openstack-meeting04:54
*** sridharg has joined #openstack-meeting04:54
*** zbitter has joined #openstack-meeting05:05
*** zaneb has quit IRC05:08
*** yamahata has joined #openstack-meeting05:11
*** yamamoto has quit IRC05:20
*** yamamoto has joined #openstack-meeting05:24
*** rbudden has quit IRC05:37
*** yamamoto has quit IRC05:47
*** yamamoto has joined #openstack-meeting05:51
*** rbudden has joined #openstack-meeting05:57
*** yamamoto has quit IRC06:07
*** apetrich has joined #openstack-meeting06:40
*** yamamoto has joined #openstack-meeting06:41
*** mahatic has quit IRC06:55
*** mahatic has joined #openstack-meeting06:56
*** rfolco has quit IRC07:06
*** rcernin has quit IRC07:26
*** yamahata has quit IRC08:03
*** iyamahat has quit IRC08:04
*** artom has quit IRC08:08
*** artom has joined #openstack-meeting08:12
*** artom has quit IRC08:13
*** artom has joined #openstack-meeting08:13
*** rubasov has left #openstack-meeting08:16
*** yamahata has joined #openstack-meeting08:23
*** yamamoto has quit IRC08:24
*** kailun has quit IRC08:27
*** iyamahat has joined #openstack-meeting08:41
*** bobh has joined #openstack-meeting08:43
*** yamamoto has joined #openstack-meeting08:47
*** ralonsoh has joined #openstack-meeting08:50
*** e0ne has joined #openstack-meeting09:03
*** rfolco has joined #openstack-meeting09:09
*** whoami-rajat has joined #openstack-meeting09:09
*** tetsuro has quit IRC09:12
*** Fdaisuke has joined #openstack-meeting09:14
*** Fdaisuke has left #openstack-meeting09:15
*** rossella_s has joined #openstack-meeting09:19
*** erlon has quit IRC09:24
*** tssurya has joined #openstack-meeting09:32
*** pcaruana has joined #openstack-meeting09:48
*** yamamoto has quit IRC09:55
*** kopecmartin|off is now known as kopecmartin10:00
*** gibi has quit IRC10:01
*** bobh has quit IRC10:01
*** arne_wiebalck_ has joined #openstack-meeting10:07
*** gibi has joined #openstack-meeting10:08
*** Elwell has joined #openstack-meeting10:11
*** a-pugachev has joined #openstack-meeting10:11
Elwellhave I missed the Scientific-SIG?10:13
*** yamamoto has joined #openstack-meeting10:22
fricklerElwell: iiuc it should be at 11 UTC, i.e. in a bit more than half an hour10:22
* Elwell failed at TZ calculation. 11+11 != 2110:25
*** yamamoto has quit IRC10:28
*** yamamoto has joined #openstack-meeting10:30
*** enolfc has joined #openstack-meeting10:33
*** shrasool has joined #openstack-meeting10:34
*** dh3 has joined #openstack-meeting10:37
*** priteau has joined #openstack-meeting10:37
*** erlon has joined #openstack-meeting10:40
*** oneswig has joined #openstack-meeting10:48
*** mgoddard has joined #openstack-meeting10:57
oneswig#startmeeting scientific-sig11:00
openstackMeeting started Wed Nov 21 11:00:03 2018 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
oneswigHello \o/11:00
priteauGood morning11:00
oneswig#link Agenda for today
oneswigGreetings all11:00
ElwellHi Folks, Mostly lurking for #3 on agenda11:01
oneswigIt's thanksgiving over the pond, we'll not be hearing from them I guess11:01
oneswigHi Elwell - good to see you11:01
oneswigdh3: I heard from Komathy, she's waiting for confirmation from Sanger on their visit11:02
dh3oneswig: OK, I will prod Pete to give a definite "yes" (I thought I had already)11:02
oneswigElwell: We could move #3 to #1 - no problem at all11:02
ElwellI can wait :-)11:03
oneswigLet's tee off with that?11:03
oneswigI'm curious myself!11:03
oneswig#topic Lustre and Manila11:03
*** openstack changes topic to "Lustre and Manila (Meeting topic: scientific-sig)"11:03
oneswigElwell: can you describe what you're looking for?11:04
*** miloa has joined #openstack-meeting11:04
ElwellI've been tasked with "investigate how possible it is to export our lustre filesystem(s) to on-prem openstack, securely"11:04
oneswigIB or IP?11:04
ElwellMy current plan is probably to reproduce the NCI (manual NFS export) way, but wondeered how automatic Manila would help11:04
*** janders has joined #openstack-meeting11:04
jandersg'day everyone11:05
oneswighey janders, you made it home11:05
dh3Sanger are interested in the Manila approach too but haven't got further than looking at the generic manila plugin and going "not enough time". We have Lustre connected to OpenStack in two ways though11:05
ElwellStorage is IB, cloud is IP, so I'm expecting to either throw router or (ib client, nfs export to IP) into mix11:05
jandersI indeed have, however I may still be on Singapore time11:05
dh31. "isolated" - Lustre FS connected to a separate VLAN which is exposed to a single project as a provider network11:06
dh32. "secure Lustre" - in the scientific sig book - proper multi-tenant using Lustre routers, full isolation but costs in terms of performance (and complexity to set up)11:06
dh3we are all IP/ethernet though11:06
oneswigWe did a project at Cambridge University for which pretty closely matched #1, but all-IB and bare metal OpenStack11:07
janderscould Lustre work with a purely hardware based IB router?11:07
jandersthis sort of a thing11:08
Elwellah by router I mean LNET routeer11:08
dh3different beast :)11:08
oneswigElwell: The book dh3 is referring to is here:
Elwellour storage is still on FDR, we have a mix of EDR and OPA lustre clients (and Aires)11:09
oneswigSanger contributed their method for multi-tenant Lustre11:09
Elwell is probably what I'll follow for now11:09
oneswigAries + OpenStack, I remember something faintly about that...11:10
*** arne_wiebalck_ has quit IRC11:10
oneswigThanks for the link - will study it!11:10
ElwellOK - so looks like noone's using Manila in that role yet, but a few sites interested (if lacking time/manpower) right?11:11
oneswigElwell: what's the ideal mode of usage?11:11
Elwellopenstack user / project mapped to their own / project part of lustre tree and can read / write there from cloud.11:12
oneswigAs I understand it, with Manila we can provision filesystems on the fly for cloud use.  I think we can also use Manila as a broker for providing access to existing "provider filesystems"11:13
Elwellso pre-post processing on cloud, HPC on $bigsystems,11:13
dh3Elwell: do you want the client to be a Lustre client or an NFS client? (we provide images with Lustre ready-baked for less technical users)11:13
Elwelltbh, probably just NFS11:14
Elwellas we can all_smash permissions down, rather than letting random cloud user hit us with a real lustre client11:15
Elwellall_squash even11:15
dh3the Lustre uid mapping is neat for that11:15
Elwellyep, but only 2/3 of our systems are on 2.10, the other is still 2.511:16
dh3fair point, the majority of ours are 2.5 too11:16
Elwell(appliance so unlikely to be upgraded11:16
oneswigI assume it's easier to develop this NFS interposer than it is to upgrade Lustre11:16
oneswigElwell: your OpenStack is virtualised or bare metal?11:17
ElwellI *think* virtualised - I'm not in the nimbus team11:18
*** belmoreira has joined #openstack-meeting11:19
oneswigThe NFS re-export is a well established pattern in Manila.  But I think currently the solution is not designed to scale out.11:19
oneswigThere are plans for that, I believe, but it's not there today.11:20
*** sambetts_ has joined #openstack-meeting11:20
ElwellOK - that's probably not too big a blocker for us at the moment as it's more a proof-of-concept for now11:21
*** sambetts_ is now known as sambetts|afk11:21
ElwellThanks all.11:21
oneswigElwell: do you think you / your group would be up for developing this poc?11:21
oneswigI'm pretty sure we could gather together a decent group of interested people.11:22
ElwellIt'll depend on staff availability I guess. We're about to kick off some heavy procurements and not sure how much time that'll suck up11:22
Elwell(OT- we're recuiting a project manager...)11:23
oneswigSounds familiar.11:23
Elwellbut yeah - happy to share progress with others11:23
oneswigOK, I'll make a note, we should come back to this again.  Are you in Perth?11:24
ElwellI'm actually in Tasmania - I work remotely11:24
oneswigThere are few places more remote, from here...11:25
Elwell(and I'm normally loitering on IRC anyway)11:25
oneswig#action oneswig to follow up on Lustre + Manila interest group11:25
oneswigOK - thanks Elwell, I hope we can gather some requirements in the next couple of weeks.11:26
oneswigMove on?11:26
oneswig#topic Berlin wash-up11:26
*** openstack changes topic to "Berlin wash-up (Meeting topic: scientific-sig)"11:26
oneswigFor those that joined in Berlin, thanks for taking part, it was on a large scale and good with it, I thought11:27
oneswigjanders: how was the wine? :-)11:27
oneswigA well-deserved win11:27
jandersit's waiting in the cellar for a good occasion :)11:28
oneswig#link Etherpad from the meeting
jandersI think it will go perfectly for a spicy Asian pork dish like bun cha11:28
oneswigSounds great :-)11:29
jandersthanks oneswig :)11:29
oneswigThere were several topics discussed in the meeting that seemed to get a positive response11:29
oneswigOngoing developments with federation being a major one.  It was great that Colleen joined us, from the Keystone project11:30
oneswigProbably the biggest area of discussion was on how to manage one infrastructure for virt, bare metal and containers (in particular, kubernetes)11:32
janderskeystone - ocp/k8s integration sounds promising however I believe it has some limitations (especially if we put Kuryr into the picture)11:33
oneswigwhat specifically?11:35
jandersI believe keystone projects can translate 1:1 to ocp/k8s projects11:35
janderskuryr creates all per-project networks in one designated "kuryr" tenant11:35
jandersthat's my understanding11:35
jandersthere might be some confusion here as the kuryr guys aren't 100% across the keystone integration part but that was their take on it11:36
miloaHi, i was at the scientific-sig meeting at Berlin. I would like to give if it is also part of this discution some feedbacks as it was my first scientific-sig meeting.11:37
oneswigHi miloa - welcome!11:37
miloathanks :)11:37
oneswigjanders: so on the openstack side there is 1 project, on the kubernetes side, many projects?11:38
oneswigmiloa: go ahead11:38
miloaIt was very interresting, thanks for the meeting. We were a lot of people from different scientific area11:38
*** aojea has joined #openstack-meeting11:39
miloaI was wondering if it would be possible to have a sort of Scientific SIG On boarding session to not be get lost :)11:39
oneswigmiloa: That's an interesting point.  The meeting session should cover that, but perhaps it does not cover it enough.11:40
miloaAnd if it would be possible to for example do little group organized in scientific aera (biology, physics...) to know each others and discuss then go back in big group and share ?11:41
oneswigAre you thinking of something like a presentation to introduce the SIG and what it does?11:41
miloayes :) something like that, and a presentation of the communication tools the SIG is using for example.11:42
oneswigmiloa: small spin-off groups, that can sometimes work.  We don't get much time to do it in 40 minutes.  I recall we did something like this with the session at the Austin summit a couple of years ago11:42
miloaok i didn't know :)11:42
oneswigI think it's a good idea.  Perhaps we should just get people sitting together anyway!11:43
*** enolfc has quit IRC11:43
oneswigmiloa: where are you from?11:43
oneswigbienvenue :-)11:43
miloamerci :)11:43
oneswigI was really encouraged to see how many new people were at the SIG for the first time.11:44
oneswigYou make a good point, we should focus more on introductions11:44
*** yamamoto has quit IRC11:45
miloaPerhaps scientifics SIG breakfirst and/or speed-mentoring will help too.11:45
mgoddardthere is
mgoddardfor information about communication etc.11:46
oneswigThanks mgoddard, good link :-)11:46
miloathanks mgoddard :)11:46
oneswigThe other major topic we discussed in the session was AI/ML and in particular GPUs.  There were ~10 people there representing institutions interested in this.11:47
oneswigI don't think there are major gaps at an infrastructure level here, only a gathering of all the current best practice to help share knowledge.11:47
jandersoneswig: (sorry for the delayed response, didn't want to interrupt the valuable onboarding thread) my understanding is that each ocp/k8s namespace/project can have its own private neutron network11:47
jandershowever all of these networks live in a designated openstack project assigned to kuryr11:48
oneswigjanders: that does seem strange.  It's like the transposition of what Magnum does.11:48
janderswhich is a little weird on its own but gets weirder if there is ocp/k8s keystone integration11:49
jandersI will try to work with RHAT to see if we can propose something more sane11:49
*** njohnston has quit IRC11:49
*** mugsie has joined #openstack-meeting11:49
oneswigI saw Kuryr on several RH slides, they do seem to be pushing it.11:49
*** njohnston_ has joined #openstack-meeting11:49
*** vishalmanchanda has joined #openstack-meeting11:50
oneswigok, thanks janders, would be great to understand more about how these fit together11:50
*** janki has quit IRC11:50
jandersI will do my best to progress on this in the coming weeks/months and I shall report back11:50
oneswigOn the GPU side, I was wondering if we might prevail on Blair - but now he's in NZ the meetings really are at antisocial hours for him.11:51
jandersperhaps next week?11:51
jandersit'll be the morning meeting, easier for NZ peeps11:51
oneswigI'll drop him a mail - I think it's at a time when he's often en route to the airport for an early morning flight!11:51
jandersgood call11:52
jandersI didnt mean to interrupt the lustre-manila chat but as we're approaching the end of the meeting:11:52
janderswhat's the appetite for manila-beegfs integration11:52
oneswig#action oneswig to contact Blair re state of knowledge on GPUs11:52
jandersas well as wider adoption of beegfs as an openstack storage backend?11:53
jandersI think beegfs is perfect material for ceph of HPC OpenStack11:53
dh3janders: we keep hearing anecdotal good things about beegfs but have no experience. Potentially interested11:53
oneswigjanders: plenty of appetite over here, that's for sure.  Can it do the necessary functions?11:53
Elwelljanders: "possible, depends if we go down beegfs"11:53
jandersI havent done much prep, however my thinking is - if GPFS can do it, why beegfs can't?11:54
verdurinI would consider it strictly for scratch-type storage at the moment11:54
janderssome R&D would need to happen but I think it's well worth it11:54
oneswigI'm hoping to meet Sven the BeeGFS creator at a conference in a few weeks (ciuk).  Perhaps if we can figure out what's needed of it, I can put it to him.11:54
jandersI had a chat to RHAT about it but I also feel we need to speak to BeeGFS guys first11:54
*** tssurya has quit IRC11:55
janderspersonally I think manila+BeeGFS-OND = nirvana of HPC Cloud stoarge11:55
oneswigjanders: would you mind looking into what's needed?11:55
jandersnot at all11:55
*** janki has joined #openstack-meeting11:56
oneswig#action janders to research BeeGFS functional requirements for Manila11:56
oneswigthanks janders, already looking forward to it :-11:56
oneswigjust time for ...11:56
oneswig#topic AOB11:56
*** openstack changes topic to "AOB (Meeting topic: scientific-sig)"11:56
jandersI also think that what you guys have going with ansible (no manila involved) is a pretty powerful demo of what OpenStack+BeeGFS are capable of11:56
oneswigthanks janders - it's proving quite popular!11:56
oneswigHad a really useful session yesterday in London - the UKRI Cloud Working Group.  Totally recommend it for next time for the UK contingent here.11:57
verdurinGlad it was useful, oneswig - couldn't attend, unfortunately11:58
jandersre AOB - just wanted to say it was great to see some of you in Berlin. Oneswig: thanks for organising a great dinner meetup, really enjoyed it (and heard more good feedback from others)11:58
jandersgood stuff11:59
oneswigYou're very welcome.  It was great to see so many11:59
dh3next time James and I will do the dinner not the bar crawl :)11:59
*** raildo has joined #openstack-meeting11:59
jandershow many were brave enough to try the cheese?11:59
janderswas pretty full on11:59
jandersgood though!11:59
oneswigAh, the cheese.  Despite the alpine theme, I didn't get round to it.12:00
oneswigone last thing - have you seen this box -
verdurinYou can't miss the cheese.12:00
oneswigMakes the DGX-1 look like a mere abacus :-)12:00
janderswas about to say - is this the DGX killer?12:00
oneswigwho knows...12:01
oneswigOK we are over time, alas12:01
jandersDGXes seem quite capable of killing themselves :P12:01
oneswigthanks all12:01
*** psachin has quit IRC12:01
*** openstack changes topic to "OpenStack Meetings ||"12:01
jandersthank you12:01
openstackMeeting ended Wed Nov 21 12:01:17 2018 UTC.  Information about MeetBot at . (v 0.1.4)12:01
openstackMinutes (text):
priteauBye everyone12:01
dh3thanks, bye!12:01
*** oneswig has quit IRC12:02
*** mgoddard has left #openstack-meeting12:07
*** yamamoto has joined #openstack-meeting12:07
*** dh3 has quit IRC12:07
*** janki has quit IRC12:12
*** Elwell has left #openstack-meeting12:17
*** kopecmartin has quit IRC12:23
*** kopecmartin has joined #openstack-meeting12:25
*** yamamoto has quit IRC12:36
*** a-pugachev has quit IRC12:38
*** e0ne has quit IRC12:45
*** aojea has quit IRC12:45
*** geguileo has quit IRC12:48
*** Guest93279 has joined #openstack-meeting12:50
*** Guest93279 is now known as geguileor12:51
*** tssurya has joined #openstack-meeting13:02
*** e0ne has joined #openstack-meeting13:02
*** e0ne has quit IRC13:03
*** e0ne has joined #openstack-meeting13:03
*** yamamoto has joined #openstack-meeting13:06
*** yamamoto has quit IRC13:18
*** Fdaisuke_ has joined #openstack-meeting13:38
*** tobiash has left #openstack-meeting13:49
*** mriedem has joined #openstack-meeting13:49
*** whoami-rajat has quit IRC13:54
*** janki has joined #openstack-meeting13:59
*** vishalmanchanda has quit IRC14:02
*** dustins has joined #openstack-meeting14:06
*** zbitter is now known as zaneb14:06
*** Fdaisuke_ has left #openstack-meeting14:10
*** Douhet has quit IRC14:13
*** bobh has joined #openstack-meeting14:21
*** Douhet has joined #openstack-meeting14:26
*** njohnston_ has quit IRC14:29
*** njohnston has joined #openstack-meeting14:29
*** vishalmanchanda has joined #openstack-meeting14:29
*** whoami-rajat has joined #openstack-meeting14:43
*** Douhet has quit IRC14:56
*** hongbin has joined #openstack-meeting15:03
*** Douhet has joined #openstack-meeting15:04
*** shrasool has quit IRC15:13
*** a-pugachev has joined #openstack-meeting15:30
*** walshh_ has joined #openstack-meeting15:50
*** tssurya has quit IRC15:50
*** rosmaita has joined #openstack-meeting15:52
jungleboyj#startmeeting Cinder16:00
openstackMeeting started Wed Nov 21 16:00:18 2018 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 thingee erlon tpsilva ganso patrickeast tommylikehu eharney geguileo smcginnis lhx_ lhx__ aspiers jgriffith moshele hwalsh felipemonteiro lpetrut lseki _alastor_ whoami-rajat yikun rosmaita16:00
_pewp_jungleboyj (◍˃̶ᗜ˂̶◍)ノ”16:01
*** geguileor is now known as geguileo16:01
jungleboyjgeguileo:  Make your flight last week?16:02
geguileojungleboyj: yup, I did :-)16:02
jungleboyj:-)  Good.16:02
jungleboyjOk.  smcginnis Is on a plane somewhere.  So, we have everyone else I expect today.16:03
jungleboyjSo, lets get started16:03
jungleboyj#topic Announcements16:03
*** openstack changes topic to "Announcements (Meeting topic: Cinder)"16:03
jungleboyjI have the Cinder on-boarding presentation posted:16:03
jungleboyjThank you to rosmaita who reviewed it and found some mistakes.16:04
jungleboyjI have fixed those so they will be right when I start with that for Denver.  :-)16:04
jungleboyjrosmaita:  That was after I fixed other issues found during the presentation.  Ooops.16:04
jungleboyjMight have phoned that one in.16:04
jungleboyjThere was good turnout for it and good questions so I think it was worth the time to do.16:04
jungleboyjSo, that is all I have there.16:05
jungleboyjI am working on getting the audio from the forum sessions posted.  I would like to say I will have that done today, but we will see.16:05
jungleboyjI will work to get it posted soon.16:06
rosmaitajust out of curiosity, have we gotten any contributors in the past from the onboarding sessions?16:06
jungleboyjrosmaita:  Yes, a couple.16:07
*** miloa has quit IRC16:07
jungleboyjI think that Brian Pawlik started with an on-boarding session.16:08
jungleboyjSame for the DRBD driver developers.16:08
rosmaitathat's about 200% better than glance16:08
jungleboyjSo, not a lot, but something.16:08
jungleboyjAlso the group working on the encryption changes sat in on the session in Berlin so I think that was helpful for them.16:09
jungleboyjWe had a good discussion around their needs and actually may have solved their issues.16:09
jungleboyj:-)  So ... it has been useful time.16:09
jungleboyjOk.  Moving on:16:10
geguileojungleboyj: yeah, they did16:10
geguileojungleboyj: because they talked with the Oslo team16:10
jungleboyjgeguileo:  Awesome.16:10
geguileowhich is what we recommended they should do16:11
jungleboyjAnd then they spent some time talking to eharney as well.16:11
geguileothey'll be proposing a new olso project16:11
jungleboyjgeguileo:  Good news.16:11
rosmaitathat's good news16:11
*** kukacz has joined #openstack-meeting16:11
*** woojay has joined #openstack-meeting16:11
jungleboyjThat makes more sense than the SDK idea.16:12
rosmaitajungleboyj: ++16:12
jungleboyjAnyway ...16:13
jungleboyj#topic Paying attention to Bugs16:13
*** openstack changes topic to "Paying attention to Bugs (Meeting topic: Cinder)"16:13
jungleboyjOk, so this was smcginnis but I think what he is trying to say is pretty obvious.16:13
jungleboyjIf you look at the link 3Par has a lot of bugs that haven't been addressed.16:14
jungleboyjThe contribution wiki clearly says that bugs need to be addressed.16:15
jungleboyjIs there anyone here that works with 3Par?16:15
jungleboyj_hemna: ^^16:15
enriquetasojungleboyj: to be addressed is to be confirmed?16:15
*** diablo_rojo has joined #openstack-meeting16:16
jungleboyjenriquetaso:  Confirmed, responded to and a plan to mitigate the issue.16:16
whoami-rajati see some of them assigned long ago but no progress since a year.16:16
jungleboyjwhoami-rajat:  Right.16:17
enriquetasojungleboyj: thanks16:17
*** jamesmcarthur has quit IRC16:17
*** jamesmcarthur_ has joined #openstack-meeting16:18
jungleboyjSome of them have had no response.16:18
whoami-rajat this can be closed i think16:18
openstackLaunchpad bug 1645136 in Cinder "create_cloned_volume of HPE 3PAR Cinder Driver has a performance bottleneck when source/target volume size are different" [Undecided,New]16:18
jungleboyjI am sure that 3Par is not the only example here.16:18
jungleboyjwhoami-rajat:  True.  I will close that one out.16:19
*** bobh has quit IRC16:19
jungleboyjAnyway, we don't need to go through all of these right now.16:20
whoami-rajatjungleboyj:  how can we proceed for these driver specific bugs?16:20
jungleboyjPoint is, if you are a driver maintainer, please take some time to review the list of bugs and respond to any bugs that may be filed against your driver.16:21
jgriffithjungleboyj: whoami-rajat the policy is that if there's not an active maintainer of the driver then it gets deprecated16:21
jgriffithactively maintaining means dealign with bugs in LP related to said driver16:22
jungleboyjI am going to follow up with a note to the mailing list and indicate that this is required.16:22
whoami-rajatjgriffith: ok. Thanks for the info.16:22
jungleboyjjgriffith:  I am thinking I should indicate that drivers that are not dealing with their bugs will be marked unsupported just like not having CI running.16:22
jgriffithIn other words how you deal with the driver related bugs is by maintaining your driver.  The Cinde repo isn't a dumping ground for stuff16:22
jungleboyjjgriffith:  ++16:23
jgriffithjungleboyj: yeah, we've done that before actually16:23
jungleboyjOk.  So...16:24
jungleboyj#action jungleboyj to e-mail ml about keeping up with bugs and that if you don't you will be marked unsupported.16:24
jungleboyj#action jungleboyj and smcginnis to review open bugs to figure out who the offenders are.16:24
*** kopecmartin is now known as kopecmartin|off16:25
jungleboyjEveryone ok with the plan above?16:25
jungleboyj#topic User Survey Feedback Blog Post16:26
*** openstack changes topic to "User Survey Feedback Blog Post (Meeting topic: Cinder)"16:26
jungleboyjI have created a blog post to respond to our user survey feedback based on discussion we had at the Forum.16:27
jungleboyjI would appreciate the rest of the team taking a look at it and making comments/updates.16:27
e0nejungleboyj: I read it really fast, could miss something. but it looks great! I'll read it more carefully after later today16:27
jungleboyjI would like to get it sent off to SuperUser soon so that it is still fresh.16:27
jungleboyje0ne: Awesome.  Thank yoU!16:28
jungleboyjjgriffith and geguileo I would appreciate your input as well.16:28
geguileojungleboyj: thanks for writting it !16:28
jungleboyjgeguileo:  No problem.  I have wanted to start doing that kind of thing.  So, it was a good time to do it.16:28
jungleboyjAny comments or questions to address on the document now?16:30
rosmaita++ on keeping backups scheduling out of cinder16:31
jungleboyjrosmaita:  :-)  Yeah, so many people asked for that and it is just not what we do.16:31
jungleboyjAnyway, please review and leave your comments.  I will get it updated and have one last call on it next week before submission.16:32
jungleboyjThat was all I had on the agenda for topics.  Anything else to discuss or should we talk quickly about bugs?16:32
enriquetasoI have something for "Ceph driver should respect the `--incremental` option for backups", but I'm not sure if this is the place to ask for more opinions about the bug.16:32
jungleboyjenriquetaso:  I think we could talk about that.16:33
jungleboyj#topic Ceph driver should respect the `--incremental` option for backups16:34
*** openstack changes topic to "Ceph driver should respect the `--incremental` option for backups (Meeting topic: Cinder)"16:34
whoami-rajatjungleboyj: Looks good. i will read it in detail.i found some minor spelling mistakes, can we correct them ourselves to not to bother you with it?16:34
jungleboyjwhoami-rajat:  Go ahead and fix them.16:34
whoami-rajatjungleboyj: i've requested edit access.16:34
enriquetasoI'll appreciate any opinions about changing the default behavior of the backups and reviews of course :)16:35
jungleboyjenriquetaso:  Go ahead.16:35
whoami-rajatjungleboyj: Thanks!16:35
*** janki has quit IRC16:36
geguileoenriquetaso: you have to explain on what you want us to give you feedback here16:37
jungleboyjgeguileo:  Thank you.  :-)16:38
jungleboyjenriquetaso:  Are you just looking for follow-up reviews?16:38
enriquetasooh, i'm looking for reviews u.u geguileo and jungleboyj16:39
jungleboyjOk.  Can take a look and review.16:40
geguileoenriquetaso: only for reviews? or do you want to hear about keeping backward compatibility?16:40
jungleboyjJust wanted to make sure you weren't looking for something more specific.16:40
geguileojungleboyj: there is an issue with keeping it backward compatible16:40
geguileoor making it behave like the other drivers that support incremental backup16:41
jungleboyjDoh.  Ok.  What is the issue?16:41
geguileoceph backups cannot create full backups (except the first one)16:41
geguileosince they are doing incremental by default16:41
geguileothe patch fixes this16:41
geguileobut if it behaves like other drivers16:41
jungleboyjRight.  Remember that discussion.16:41
geguileoonly doing incremental when requested, then it's not backward compatible16:42
geguileoand if it's backward compatible, then it's not consistent with other drivers16:42
jungleboyj:-(  Indeed.16:42
geguileoso it's a matter of preference/choosing our favourite evil16:43
e0neI'm wondered I we didn't catch anything of this on our gates16:43
enriquetasothanks geguileo, yup. So my patch make the driver consistent with other drivers16:43
jungleboyjWhat are other drivers doing?16:43
geguileothey create full by default16:44
geguileoif you specify incremental, then they do incremental using the latest full as the base16:44
jungleboyjgeguileo:  Ok.  Makes sense.16:44
geguileosorry, latest full, or latest incremental16:44
jungleboyjAnd I forget, why can't we make Ceph do the same?16:44
geguileobut ceph just tries to do incremental if it can, and does full if it can't16:44
e0neI'm +1 for consistency even if we have to change our default behaviour16:45
geguileojungleboyj: we can do it, but then we change the default behavior16:45
geguileomaybe it's enough to add an upgrade note16:45
jungleboyje0ne:  Yeah.16:45
geguileoto make sure that any automation is changed16:46
jungleboyjI think consistency is best.16:46
geguileoenriquetaso: looks like what you have is OK, maybe update the release note, and change the "features" section for an upgrade one16:46
jungleboyjgeguileo: ++16:47
jungleboyjHonestly, it seems like a bug that it didn't work the same as other drivers in the first place.16:47
enriquetasoIt's reported as a bug16:48
whoami-rajatlooks like many people want the incremental functionality with ceph.16:48
*** shrasool has joined #openstack-meeting16:48
whoami-rajatfull backup*16:48
geguileojungleboyj: it's not a real bug16:48
geguileojungleboyj: Ceph was the first backup driver that did incremental16:48
jungleboyjOh ... ok.  :-)16:49
geguileojungleboyj: then we introduced incremental, but the driver was not updated16:49
geguileojungleboyj: so it was inconsistent with the others16:49
jungleboyjgeguileo:  Gotcha.  Ok.  So, I think it is good to get it caught up.16:49
geguileoin any case, this will fix it, and our drivers will be more consistent  :-)16:49
jungleboyjMoving on16:50
jungleboyj#topic Bug Triage16:50
*** openstack changes topic to "Bug Triage (Meeting topic: Cinder)"16:50
jungleboyjSo, I wanted to bring up the following bug:16:50
*** pcaruana has quit IRC16:50
openstackLaunchpad bug 1802070 in openstack-ansible "Add resource_filter field in cinder.conf for non-admin user can retrieve volume & snapshot volume" [Undecided,In progress] - Assigned to KimMinsik (for-beatitudo)16:50
jungleboyjOpenStack Ansible needed to make a change to fix an issue they were seeing.16:50
jungleboyjIt seems to me, however, they are working around a Cinder bug.16:51
*** efried_back_mon has quit IRC16:51
jungleboyjI don't remember who was working on the resource_filter stuff.  I am thinking it might have been tommylike ?16:51
e0nejungleboyj: I agree that we need to fix it in cinder too16:52
jungleboyje0ne:  That was my thought as well.16:53
jungleboyjIt seems like there should be some default behavior if the file doesn't exit.16:53
e0nejungleboyj: +116:54
jungleboyjA 400 isn't right.16:54
jungleboyje0ne:  Are you familiar enough with that code path to fix it up?16:54
jungleboyjSince this was causing issues for Horizon it would be up your alley to fix/test.16:55
e0nejungleboyj: at lease I think so:)16:55
e0neI'll take it as my priority for tomorrow morning16:55
jungleboyje0ne:  Ok.  Cool.  I can open a bug based on the one in OpenStack ansible to track it against Cinder.16:56
jungleboyjMake sense?16:56
e0neI just add Cinder project to the existing bug16:56
jungleboyjOh ... yeah.  That probably makes more sense.16:56
jungleboyje0ne:  Cool.  Thanks for taking that one.16:57
e0nejungleboyj: np. I'm happy to be useful for the team :)16:57
jungleboyjgeguileo: Did you open a follow up bug to16:58
openstackLaunchpad bug 1782714 in Cinder "Properties of an attached volume are lost after live migration" [Medium,New]16:58
jungleboyje0ne:  You are always useful to the team.  :-)16:58
e0nejungleboyj: thanks, Jay!16:58
geguileojungleboyj: yes, and I proposed a fix16:59
jungleboyjOk.  Cool.16:59
* jungleboyj is behind on reviews. :-(16:59
geguileojungleboyj: it's in the last comment of the bug for reference16:59
geguileoit's a 4 lines patch16:59
jungleboyjNice!  Ok.  I will follow up on that.17:00
whoami-rajatjungleboyj: Sorry for interrupting, there is a frequent gate failure that yikun and I have been looking at, . can the cinder team take a look at the patches for it? Thanks.17:00
openstackLaunchpad bug 1803648 in Cinder "gate failure : testtools.matchers._impl.MismatchError: 'volume.retype' != 'backup.createprogress'" [Undecided,In progress] - Assigned to Rajat Dhasmana (whoami-rajat)17:00
jungleboyjAnd on that note.  We are out of time.17:00
jungleboyjwhoami-rajat:  Sure.  Can look at that as well.17:00
jungleboyjOk.  Lets wrap up.17:00
jungleboyjThanks team for a good meeting.17:00
jungleboyjHope those of you in the US have a Happy Thanksgiving!17:00
jungleboyjTalk to you all next week.17:01
whoami-rajatjungleboyj: Thanks! :)17:01
enriquetasoHappy thanksgiving!17:01
*** openstack changes topic to "OpenStack Meetings ||"17:01
openstackMeeting ended Wed Nov 21 17:01:27 2018 UTC.  Information about MeetBot at . (v 0.1.4)17:01
openstackMinutes (text):
*** e0ne has quit IRC17:02
*** woojay has left #openstack-meeting17:05
*** sambetts|afk has quit IRC17:14
*** sambetts_ has joined #openstack-meeting17:16
*** yamamoto has joined #openstack-meeting17:16
*** alex_xu has quit IRC17:17
*** sridharg has quit IRC17:20
*** yamamoto has quit IRC17:20
*** shrasool has quit IRC17:30
*** vishalmanchanda has quit IRC17:32
*** yamahata has quit IRC17:39
*** iyamahat has quit IRC17:39
*** jamesmcarthur_ has quit IRC17:41
*** rosmaita has left #openstack-meeting17:42
*** jamesmcarthur has joined #openstack-meeting17:42
*** iyamahat has joined #openstack-meeting17:52
*** jamesmcarthur has quit IRC17:54
*** jamesmcarthur has joined #openstack-meeting17:54
*** jamesmcarthur has quit IRC18:07
*** jamesmcarthur has joined #openstack-meeting18:09
*** jamesmcarthur has quit IRC18:14
*** jamesmcarthur has joined #openstack-meeting18:15
*** jamesmcarthur has quit IRC18:20
*** yamahata has joined #openstack-meeting18:21
*** jamesmcarthur has joined #openstack-meeting18:23
*** mriedem has quit IRC18:26
*** mriedem has joined #openstack-meeting18:37
*** ralonsoh has quit IRC18:40
*** shrasool has joined #openstack-meeting18:49
*** apetrich has quit IRC19:00
*** jamesmcarthur has quit IRC19:02
*** jamesmcarthur has joined #openstack-meeting19:12
*** jamesmcarthur has quit IRC19:13
*** jamesmcarthur has joined #openstack-meeting19:14
*** apetrich has joined #openstack-meeting19:15
*** e0ne has joined #openstack-meeting19:33
*** bobh has joined #openstack-meeting19:35
*** dklyle has quit IRC19:38
*** jamesmcarthur has quit IRC19:40
*** whoami-rajat has quit IRC19:41
*** raildo has quit IRC19:43
*** raildo has joined #openstack-meeting19:43
*** jamesmcarthur has joined #openstack-meeting19:44
*** dklyle has joined #openstack-meeting19:46
*** erlon has quit IRC19:49
*** apetrich has quit IRC20:01
*** shrasool has quit IRC20:06
*** jamesmcarthur has quit IRC20:25
*** bobh has quit IRC20:29
*** jamesmcarthur has joined #openstack-meeting20:29
*** raildo has quit IRC20:35
*** dustins has quit IRC20:35
*** bobh has joined #openstack-meeting20:39
*** jamesmcarthur has quit IRC20:46
*** jamesmcarthur has joined #openstack-meeting20:49
*** timburke has joined #openstack-meeting21:01
mattoliverau#startmeeting swift21:01
openstackMeeting started Wed Nov 21 21:01:10 2018 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.21:01
*** openstack changes topic to " (Meeting topic: swift)"21:01
openstackThe meeting name has been set to 'swift'21:01
mattoliverauhey everyone21:01
mattoliverauwho's here for the swift team meeting?21:01
rledisezhi o/21:01
mattoliveraustill waiting on tdasilva21:02
mattoliverauwho seems to be in channel21:02
*** tdasilva has joined #openstack-meeting21:02
mattoliverauNot expecting a lot of turn out this week, because of thanksgiving in the US21:02
mattoliverauSo this will just be a status meeting. So should go pretty quick21:03
mattoliveraubefore we get to the agenda, I'm curius to those who where there, kota_ and rledisez, how was the summit?21:04
*** shrasool has joined #openstack-meeting21:04
kota_that was good except notmyname absent project onboarding.21:05
mattoliverauyeah, opps. :(21:05
kota_absent from21:05
mattoliverauother then that how'd the onboarding go?21:05
rledisezit was ok. some interesting sessions on various topics21:05
rlediseznot a lot related to swift, sadly :)21:05
timburkeapparently somebody *cough*rledisez*cough* kept him out too late the night before ;-)21:05
mattoliverauahhh, so that's what happended ;)21:06
rlediseztimburke: there is no proof :p21:06
kota_one interesting session I found, wait a moment, i'm looking for the slide...21:06
mattoliveraure: not a lot related to swift, sadly: We may need to make swift less stable so people take more notice ;)21:07
timburkeor find other conferences to check out...21:07
mattoliverautrue, maybe something storage focused21:07
kota_that was present by Tristan@RedHat21:08
kota_introducing how we reduce noisy logs in the gerrit/zuul.21:08
timburkekota_: that *does* sound interesting!21:08
mattoliverauand Dirk it seems21:09
mattoliverauI work with him21:09
kota_basically, that reduces anoying setup logs.21:09
*** jamesmcarthur has quit IRC21:09
kota_then, it will show anomaly logs when the gate failed.21:09
kota_timburke: i thought you like it ;)21:10
mattoliveraucool. I shall go and actaully watch that one.. I asusme it would have been recorded21:10
mattoliverauany other highlights?21:10
mattoliverauwe can always ask again next week to get notmyname's summit highlights too :)21:11
kota_i think it was recorded but it seems like the video has been delayed in this summit.21:11
kota_mattoliverau: good idea21:11
mattoliverauwell no links here then, but will keep my eye out.21:12
mattoliveraulet's move on then.21:12
mattoliverau#topic Priority Reviews21:12
*** openstack changes topic to "Priority Reviews (Meeting topic: swift)"21:12
*** jamesmcarthur has joined #openstack-meeting21:13
mattoliverauwe seem to have a general task queue topic later.. so we can talk about that then.21:13
mattoliverauSeems to not have changed much. Which is fine.21:14
mattoliverautimburke, kota_ hows the s3api patches.. need any love from us?21:14
timburkei've got a couple new s3api patches, too :-) adds a concurrency factor for multi-delete requests, similar to what we already have for bulk, and adds a config option to allow some specific subset of AWS's server-side-encryption options21:14
timburkei know tdasilva was interested in kota_'s opinion on
kota_ah... I know them, sorry no updates for this time, I just finished another one than the last 2 things.21:15
mattoliverauahh no notmyname means no patchbot. shame21:15
kota_then, I won't have this week and the next week because of the technical *NTT* conference in my office location.21:16
mattoliverautimburke: did you want to add them to the s3api list there? or do you feel their not a priority21:16
mattoliveraukota_: no worries, these things happen21:16
timburkemattoliverau: yeah, i'll probably do that. they came up as customer issues, so i'm gonna carry some (more) patches on swift3, which puts me further off from being able to switch to s3api :-(21:17
timburkekota_: don't worry :-) enjoy the work conference!21:17
mattoliverautimburke: yeah, we don't want that. I'd rathere have you pushing patches upstream then loose you to maintain downstream patches!21:18
mattoliveraulet's add them21:18
timburkei can do both :-)21:19
mattoliveraumaybe I should finally stop being lazy and learn more of the s3 api so I can help review21:19
timburkeat least for a while21:19
mattoliverauThe undelete accounts is on me, but I haven't really gone and helped like I said yet. Been too busy with SUSE work :(21:19
kota_mattoliverau: no worries21:20
timburkefwiw configures s3cmd pretty well, and i've got a patch up to have it also configure awscli for you21:20
timburkei like that i can use aws's own tooling to test my changes :-)21:21
mattoliveraubut from what I can see, if we add the ability to undelete accounts (officially) then we need to support it. and there is a eventual consistency issue when a reaper may delete _everything_ if something has been undeleted. So I think some kind of qourum needs to be added, if we want to support it.21:21
mattoliverautimburke: ahh cool, I should take a look at that21:21
mattoliverauI offered to help write some quorum check, but haven't had a chance...21:22
mattoliverauI should go and at least let them know I'm not dead.21:22
*** radeks_ has quit IRC21:22
mattoliverauThe only other patch on the priority reviews is the keymaster nice to have. and the swift-object-info one.21:23
mattoliverauI did review it a while ago. timburke is it ready for another review?21:23
timburkeoh, i forget. i'll take a look today21:24
mattoliverauI know you have alot of patches in the air, so maybe this one isn't really a hight priority21:24
timburkespeaking of keymasters, i keep meaning to review your mattoliverau21:24
timburkei guess i'll break down and actually have my barbican config under /etc/ -- i managed to get keystone happy running from somewhere else, but i haven't been able to do the same for barbican...21:25
mattoliverauyeah, I'd love to see that in the next release, just so all our keymasters (upstream) have the same set of features. maybe I should add that to the priority reviews section?21:25
timburkei like it. i feel like it ought to be higher priority than the object-info guy, anyway21:26
mattoliverautimburke: I used the saio install script/env that tdasilva forked when we were first reviewing the kms keymaster orginially :)21:26
timburkeit all *looks* right -- i just wanna remember how to functionally test again :-)21:26
mattoliverauI'll add it to the page.21:27
timburkethen maybe i could add barbican to our dsvm job...21:27
mattoliveraunot a bad idea21:27
*** bobh has quit IRC21:28
mattoliveraualso makes us look better doing more cross project testing21:28
mattoliveraunot that we'd install barbican master tho21:28
mattoliverautdasilva: that's the one, I forked and use that when I want to test kms, because I'm lazy21:28
mattoliverauwhy reinvent the wheel, when tdasilva or timburke has already invented it ;)21:29
timburkebut what if i can *make a better wheel*!? :P21:29
mattoliveraulol, it's called a PR ;)21:30
*** janders has quit IRC21:30
tdasilvaif you are in the business of making wheels...21:30
mattoliverauthen that's a different story I guess.21:30
mattoliverauif there's nothing else on this topic, lets move on.21:30
mattoliverau#topic task queue21:31
*** openstack changes topic to "task queue (Meeting topic: swift)"21:31
mattoliverauAny updates on this?21:31
mattoliverautdasilva and myself worked on a documentation follow up patch.21:31
*** e0ne has quit IRC21:32
mattoliveraudid that get sqashed in?21:32
kota_no idea, m_kazuhiro doesn't seem to be here.21:33
mattoliverau^ documentation patch21:33
kota_can i ping him in the day time in my time zone?21:33
mattoliveraukazahiro left a comment saying he'd like to get rledisez review on it before sqashing it in.21:33
kota_i see21:34
rledisezmattoliverau: i'll try to have a look at it this week21:34
mattoliverauAnd I have no doubt rledisez english skills are better then mine (Australian english == bad english) :P21:34
mattoliveraubut the doc patch doesn't stop people looking at the task queue patch.21:35
mattoliverauanyway, this is just a reminder. If you have the time, I know we're all busy21:35
mattoliveraunext topic21:35
mattoliverau#topic LOSF21:35
*** openstack changes topic to "LOSF (Meeting topic: swift)"21:35
mattoliveraurledisez: anything to update?21:36
mattoliverauany reviews you want to point us at that we really should be reviewing for you?21:36
rlediseznot for this week. it's quiet on the losf side21:36
rledisezwe've been struggling with bugs that might be related to eventlet more than losf21:36
rlediseza proper bugreport + patch is on the way about one of them, still digging for the others21:37
kota_rledisez: it seems like Norio succeeded to run the Alex's branch in his env, he is now looking the diff to know how was implemented.21:37
rledisezkota_: awesome, it's not only OVH work now ;)21:37
kota_rledisez: that's my plan ;)21:38
mattoliverauthat's awesome news21:38
mattoliverauI look forward to reading the bugreport.21:39
mattoliveraumaybe that reads bad. is it bad to look forward to reading bug reports?21:39
mattoliveraui dunno, still pre coffee for me :p21:39
rledisezmattoliverau: you loof forward to reading the bugreport that will contain a link to the patch, right? :D21:40
mattoliverauoh yeah, well that certainly is true ;)21:40
mattoliveraubut if you get blocked and need more eyes and heads then get the bugreport in. Especially if it's due to eventlet, clayg would love more fodder against eventlet I'm sure :)21:41
mattoliverauCool, then lets move on the last topic.21:41
mattoliverau#topic open discussion21:41
*** openstack changes topic to "open discussion (Meeting topic: swift)"21:41
mattoliverauAnything else anyone wants to bring up?21:42
rledisezmattoliverau: back to the subject, the more we go, the more I want to drop eventlet. is there somewhere an idea of a plan to do that?21:42
timburkeencryption got ported to py3!21:42
rledisezmy first though was to get uwsgi in, to do the "prefork" stuff, then remove eventlet step by step. does it sounds crazy? what about having uwsgi as dependency… so man questions :)21:43
timburkerledisez: i know clayg feels the same way -- not sure about a concrete plan, though21:43
mattoliverauyeah, that's similar to the plan clayg has21:44
mattoliverauAnd I think makes sense.21:44
mattoliverauNot sure we documented it anywhere.21:44
mattoliverauI'll see if I can find any clay ramblings in etherpads about it. And let's add it to ideas to start fleshing out some more.21:44
timburkewere you thinking mainly for the backend servers, or proxy server as well? i could maybe see eventlet still kinda making sense on the proxy... idk. haven't thought about it enough.21:44
mattoliveraubased on that we'd hopefully know if it sinks or swims and can move on it, either way21:45
rlediseztimburke: yes, object server first. for proxy, it might be a good idea to keep it for now21:45
rledisezi think i'll try something simple first, running object server in uwsgi with eventlet_tpool_size to 0 and see how it goes (performance & co). after that, we'll see if there is something to fo from there21:46
mattoliverauwith all the worker stuff starting to happen in the back end, it makes sense. currently I think we need to fork before eventlet monkey patches breaks things, so it definitely gets in the way.21:47
timburkei think zaitcev's might still be a pre-req -- kinda depends on what the new server would do with the stray zero-byte chunk we stick into the mime doc PUT stream...21:47
rlediseztimburke: hum, i see, i will try to run func test on it to see what happen21:48
mattoliveraurledisez: nice, see how that goes. But eventley does a bunch of monkey patching to other areas of python, so would a eventlet_tpool_size of 0 stop that, you may still end up fighting evenlet to some extent.21:49
mattoliveraubut only testing will tell21:49
timburkeyeah -- EC is where it'd bite you. see
openstackLaunchpad bug 1496636 in OpenStack Object Storage (swift) "EC: Chunked transfer/commit protocol is *not* HTTP" [Medium,In progress] - Assigned to Pete Zaitcev (zaitcev)21:49
rledisezok, so back to square one i guess21:50
*** yamamoto has joined #openstack-meeting21:50
mattoliverauto go back a step, timburke yeah py3 encrption, nice!21:51
timburkeor, we keep moving forward on getting our "HTTP" protocol to actually be HTTP! and then we can (theoretically) use whatever WSGI server we want!21:51
mattoliverautimburke: hows the py3 stuff going, I've seen patches for the account server, so you and zaitcev are doing awesome there.21:52
mattoliverautimburke: +121:52
mattoliverauthat's the whole point of using a standard :)21:52
timburkewho knows21:52
timburkesomeday it'll all run under py3 -- hopefully it'll even upgrade all nice21:53
mattoliveraupy2 > py3 is much more of a rewrite then I expected, and it always comes down to unicode and byte strings.21:54
timburkethere's probably going o be a long tail of fixes before we declare full support. like, we thought we had common.utils ported already, but nope:
timburke(thanks for merging that btw, mattoliverau)21:54
timburkeoccasionally there are other issues -- like lists becoming iterators :-)21:55
mattoliverauwe may need to add to our developer documentation, for devs, on how to write code that behaves correctly (ie how and when to use str_to_wsgi etc)21:56
mattoliverautimburke: yeah21:56
mattoliverauand moving everything :P21:56
mattoliverauok only 4 minutes to go21:56
mattoliverauI didn't expect the meeting to go as long.. but then again, I'm not very short winded.21:57
mattoliverauAnything else to bring up before the end of the meeting?21:57
mattoliveraugoing 1...21:58
mattoliverauthe channel my inner notmyname: thanks for your work on swift!21:58
kota_thanks mattoliverau21:58
*** openstack changes topic to "OpenStack Meetings ||"21:58
openstackMeeting ended Wed Nov 21 21:58:40 2018 UTC.  Information about MeetBot at . (v 0.1.4)21:58
openstackMinutes (text):
timburkethanks mattoliverau!21:58
*** timburke has left #openstack-meeting21:59
*** mriedem has quit IRC21:59
*** shrasool has quit IRC22:02
*** shrasool has joined #openstack-meeting22:04
*** rcernin has joined #openstack-meeting22:09
*** priteau has quit IRC22:16
*** shrasool has quit IRC22:17
*** erlon has joined #openstack-meeting22:26
*** dtrainor_ has joined #openstack-meeting22:37
*** dtrainor has quit IRC22:40
*** imacdonn has quit IRC22:42
*** imacdonn has joined #openstack-meeting22:42
*** a-pugachev has quit IRC22:54
*** diablo_rojo has quit IRC23:02
*** dtrainor__ has joined #openstack-meeting23:12
*** dtrainor_ has quit IRC23:15
*** slaweq has quit IRC23:45
*** lbragstad is now known as lbragstad_turkey23:46
*** lbragstad_turkey has quit IRC23:56

Generated by 2.15.3 by Marius Gedminas - find it at!