Thursday, 2019-06-27

*** openstack has joined #openstack-meeting-alt13:15
*** ChanServ sets mode: +o openstack13:15
*** rcernin has quit IRC13:31
*** munimeha1 has joined #openstack-meeting-alt13:43
*** dave-mccowan has quit IRC13:43
*** mtreinish has joined #openstack-meeting-alt13:56
*** lpetrut has quit IRC14:13
*** baojg has joined #openstack-meeting-alt14:14
*** bhavikdbavishi has joined #openstack-meeting-alt14:57
*** baojg has quit IRC14:59
*** ganso has joined #openstack-meeting-alt15:00
gouthamr...15:01
lseki...15:01
carloss...15:01
tbarron#startmeeting manila15:02
openstackMeeting started Thu Jun 27 15:02:00 2019 UTC and is due to finish in 60 minutes.  The chair is tbarron. Information about MeetBot at http://wiki.debian.org/MeetBot.15:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:02
*** openstack changes topic to " (Meeting topic: manila)"15:02
openstackThe meeting name has been set to 'manila'15:02
lseki\o/15:02
*** bhavikdbavishi has quit IRC15:02
*** sfernand has joined #openstack-meeting-alt15:02
gouthamro/15:02
carlosshey :)15:02
tbarroncourtesy ping: gouthamr xyang toabctl bswartz ganso erlon tpsilva vkmc amito jgrosso15:02
gansohello15:02
vkmco/15:02
dviroelo/15:02
lsekitbarron: this courtesy ping seems outdated...15:03
*** s0ru has joined #openstack-meeting-alt15:03
tbarronlseki: it is editable by anyone so peoole can add themselves15:04
tbarronbut it helps15:04
tbarronif it don't leave part of it out :)15:04
tbarroni see the folks I dropped here though15:04
tbarronhi all!15:04
tbarronwe have some of our folks in training today15:05
vkmco/15:05
tbarronand bswartz has a conflict for part of the meeting15:05
tbarronso let's get started15:05
*** vishakha has quit IRC15:05
tbarronwe have a pretty full agenda:15:05
tbarron#link https://wiki.openstack.org/wiki/Manila/Meetings15:06
tbarron#topic announcements15:06
*** openstack changes topic to "announcements (Meeting topic: manila)"15:06
tbarronI just want to remind folks that the call for presentations15:06
tbarrondeadline15:06
tbarronfor the Shanghai summit is this coming Tuesday15:07
tbarron#link http://lists.openstack.org/pipermail/openstack-discuss/2019-June/007376.html15:07
tbarronit will be good to have manila presentations!15:08
tbarronAny other announcements?15:08
tbarron#topic PTG planning15:08
*** openstack changes topic to "PTG planning (Meeting topic: manila)"15:08
tbarronAs noted here:15:08
tbarron#link http://lists.openstack.org/pipermail/openstack-discuss/2019-June/007079.html15:09
tbarronPTG will be a bit different this time15:10
*** bhavikdbavishi has joined #openstack-meeting-alt15:10
tbarronIt will overlap with Summit15:10
tbarronand run past Summit, so won't be a separate event15:11
tbarronso in that respect a bit like last time15:11
tbarronbut there will likely be fewer attendees from the Americas and15:12
tbarronmore from the Pacific Rim15:12
tbarronBecause we have lots of regular PTG participants from the Americas we can15:12
tbarronexpect to do more of the post-meeting followup this time.15:13
tbarronWe already had carryover items this last time.15:13
tbarronAnd we can expect to do more formal and informal onboarding during the Shanghai PTG itself.15:13
tbarronMake sense?15:14
tbarronAre there folks who normally attend PTG who know or think they won't be in Shanghai?15:14
*** bhavikdbavishi has quit IRC15:14
tbarronOr vice versa>15:14
tbarrons/>/?/15:14
gouthamryep, we'll still plan to do physical presence and bluejeans?15:15
*** bhavikdbavishi has joined #openstack-meeting-alt15:15
tbarronI'll need to respond to an upcoming query to PTLs on PTG soon.15:15
tbarrongouthamr: I think so.15:15
tbarronmaybe it would be best if people ping me privately with their best15:16
tbarronestimate as to whether they will be attending physically15:17
tbarronthat would be best.15:17
gouthamri still don't know if i will be there, but if i can't; i may be able to join the first-half sessions15:17
lsekipretty sure that 2 or 3 netappers will be there15:17
vkmcbluejeans might be tricky15:17
tbarronvkmc: that's a point15:17
vkmcus based folks won't be able to follow it live15:18
gouthamroh i totally forgot about that :P15:18
vkmcwell, us... americas in general15:18
tbarronlos americanos15:18
lsekiand 1 or 2 will try to attend via bluejeans, though timezone won't help ;-(15:18
vkmcemea is better but still might be late15:18
vkmctbarron, 'xactly15:18
tbarroni think vkmc is referring to firewalls as well as TZ15:18
vkmcso we need to make sure to take good notes15:19
tbarronmaybe zoom will work across firewalls15:19
vkmcwe need a doc person in the room15:19
vkmctbarron, wechat15:19
tbarronvkmc: wedo15:19
vkmcyou can do anything with wechat in china, as far as I heard15:19
tbarronok, lots of logistics to figure out, thanks for letting me know that we'll have15:20
tbarronnetapp physical presence15:20
tbarron#topic our work15:20
*** openstack changes topic to "our work (Meeting topic: manila)"15:20
gouthamrwe might be able to figure something out for bluejeans, if you have decent computers: https://support.bluejeans.com/s/article/Premium-Access-for-China15:20
tbarronnew drivers15:20
tbarron#link https://review.opendev.org/#/c/636819/15:21
tbarronINSPUR driver15:21
tbarronI've reviewed it informally and lseki and gouthamr have given it a lot of attention15:21
tbarronI'm inclined to merge it15:22
tbarronanyone have issues with this?  If you want to review, put your hand up please.15:22
tbarronINSPUR CI is working and they've responded to all outstanding review questions at this point.15:23
tbarronBut the deadline isn't for another month so if you want to review you have time.15:23
tbarroncrickets15:23
gouthamryeah, only weird thing is their CI is running on stable branches, where the code isn't (going to be) present..15:24
gouthamrhope they can turn off that bit..15:24
tbarrongouthamr: do you want to hold workflow until that's fixed?15:24
gouthamrtbarron: not really...15:25
tbarronit's a waste of their resources but otherwise pretty harmless, right?15:25
tbarronkk15:25
tbarron#link https://review.opendev.org/#/c/657775/15:25
tbarronthis is INFORTREND ^^^15:25
* gouthamr ALL CAPS15:26
tbarronsome of you may not have noticed that these are *two* things :)15:26
* tbarron is practicing for his tweets15:26
gouthamrlseki: great work on the reviews!15:26
lsekigouthamr: thanks :-)15:26
tbarronwell thanks to lseki and gouthamr again15:26
tbarronthey've been pretty responsive but there are outstanding -1s15:27
tbarronlseki: gouthamr: seems like this one is on track as long as they keep responding to review comments?15:27
gouthamryes..15:27
lsekiyep15:28
*** kopecmartin is now known as kopecmartin|off15:28
gouthamrthe CI's been running too, many of the changes suggested should be easy to incorporate, or respond to15:28
tbarronok, let's just keep track of it15:28
tbarron#link https://review.opendev.org/#/c/664269/15:28
tbarronNexentaStor5 NFS driver refactor ^^^15:29
* gouthamr started looking at it15:29
gouthamrETOOBIG15:29
tbarrongouthamr: in the finest ntap tradition :)15:29
tbarronfrom when we were there15:29
tbarronThey are adding significant new features though15:30
tbarronHA15:31
tbarronDHSS true it looks like15:31
tbarronand then internally using jsonrpc instead of http to communicate with the back end15:32
tbarronthe last is pretty much their business but we need to15:32
tbarronreview the other stuff15:32
tbarrongouthamr: thanks for starting to look at this one15:32
tbarronlet's get some more eyes on it please15:33
gouthamrack, should have an initial review this week15:33
tbarronOK, let's talk about Specs15:35
*** ayoung has quit IRC15:35
tbarron#link https://review.opendev.org/#/c/66120915:35
tbarronthis is Add update share-type API to Share Types15:35
gouthamrThere's one more big driver change15:35
tbarrongouthamr: oh, which?15:36
gouthamr#LINK https://review.opendev.org/#/c/663089/15:36
gouthamralthough i see it's been redone now, i initially saw a lot of LOC15:36
bswartz.o/15:36
tbarroni was thinking it's "just" a rebranding15:36
* bswartz is trying to escape from other meeting15:36
* gouthamr provides bswartz covering fire15:37
tbarronbswartz: welcome15:37
tbarronI think most of the LOC are a file rename15:38
tbarronbut yeah, let's review it please15:38
tbarronSpecs15:38
tbarronI'm inclined to merge the one we talked about last week15:38
tbarronupdate share-types15:39
tbarronlseki reviewed since then15:39
tbarronthanks lseki15:39
tbarronand dviroel15:39
tbarronI think all reviewers are OK with it.15:40
tbarronAnyone want to review it ?  Just raise your hand and I'll hold off workflow.15:40
tbarronOK, let's talk about the spec for openstackclient15:41
*** hongbin has joined #openstack-meeting-alt15:41
tbarron#link https://review.opendev.org/#/c/64421815:41
tbarronas you can see this one has a lot of review attention and15:41
tbarroncorresponding updates15:41
tbarronI think good progress is being made and new issues are being15:42
tbarrondiscovered and addressed along the way.15:42
tbarronIt's important stuff and I mainly just want to hightlight it for review visibility.15:43
tbarronNow.15:43
tbarronLet's talk about the create from snaps in another pool or back end spec15:43
dviroel\o/15:44
tbarron#link https://review.opendev.org/#/c/60953715:44
tbarrondviroel has done nice work here and the review is progressing but15:44
tbarronan issue of fairly general interest came up15:44
tbarrongouthamr: do you want to explain your remarks about slow copies?15:45
* gouthamr hasn't seen dviroel's last update15:45
gouthamrmy comments are at https://review.opendev.org/#/c/609537/7/specs/train/create-share-from-snapshot-in-another-pool.rst@30915:46
tbarrongouthamr pointed out that these creates may take long enough time15:46
gouthamrso, our create_share driver interface is synchronous, and we expect drivers to return quickly15:46
tbarronthat it would make sense to do them asynchronously15:46
* tbarron baks off now :)15:46
dviroelyes, for sure. In scenarios where we need move data between different pools/backends, this copy can take longer then expected...15:47
gouthamrif they take a long time to perform some thing, it might starve a thread on our end... so i think it's time to revisit that, especially for this use case15:47
gouthamrso i think we can allow drivers to tell us the new share isn't ready yet15:48
gouthamrand we can check back at our default periodic interval15:48
gouthamrkinda like what we do for migration and replication today15:48
tbarronso the driver would tell the manager that the share is still 'creating', right?15:48
dviroelYes, agree15:49
tbarronok, you guys agree15:49
tbarronit will require a bit of manager work15:49
gouthamryes, i think that's a good way to signal that15:49
gouthamrtoday, drivers return export locations, which can be a string, a list of strings or a list of dictionaries15:49
tbarronanyone have issues with this approach?15:49
tbarronI think it's consistent with what we do in general, loosely couple services and allow operations to go into ING states15:50
tbarronat the time of an rpc or boundary handoff15:51
tbarronmanager to driver is a library call, not a service rpc15:51
*** ttsiouts has quit IRC15:51
gouthamrwhat needs to be considered is how the manager will track these shares15:51
tbarronbut the back ends are separate services really15:52
gouthamrand how it will ask drivers for their status15:52
*** itssurya has quit IRC15:52
*** ttsiouts has joined #openstack-meeting-alt15:52
tbarrongouthamr: the priodic check will work, right?15:52
tbarronand we have to address all those periodic tasks with leader election or some such whe15:53
tbarronwhen we do active-active share service15:53
tbarronso this doesn't change that equation15:53
gouthamrthat's one concern15:54
dviroelI was thinking that should work in the way it works for replication.15:55
tbarroni would think the manager should pass a list of shares to the driver rather than one by one when querying status15:55
gouthamrthe other is how the manager can identify shares that need to be queried for15:55
*** ccamacho has quit IRC15:55
gouthamrcan we expect that, even with asynchronous creation, the driver can update export locations?15:56
gouthamrthen it'll be easier for us to query for creating shares and filter them by those that have export locations15:56
*** ttsiouts has quit IRC15:56
gouthamrelse, we'd pick up shares that are in-flight too, to perform a status check15:57
*** helenafm has left #openstack-meeting-alt15:57
tbarrongouthamr: what about keeping a list of shares in the manager that are driver-creating?  persist it to DB for manager restarts but keep it in memory15:57
gouthamrtbarron: in-memory?15:58
tbarronfor speed15:58
tbarronor look it up every time, maybe it doesn't matter15:58
tbarronbut avoid checking all shares for state15:58
tbarronmaybe I'm doing premature optimization15:59
tbarronand using up time15:59
gouthamryep, time check :)15:59
tbarronthis is a good topic, so join the discussion in the review15:59
tbarronThanks everyone!!15:59
dviroelThanks15:59
tbarroni have one more operational concern, for #openstack-maila in a minute16:00
tbarron#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:00
openstackMeeting ended Thu Jun 27 16:00:06 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/manila/2019/manila.2019-06-27-15.02.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/manila/2019/manila.2019-06-27-15.02.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/manila/2019/manila.2019-06-27-15.02.log.html16:00
*** ganso has left #openstack-meeting-alt16:00
gouthamr /join #openstack-maila16:00
carlosshaha16:00
lsekilol16:00
*** e0ne has quit IRC16:02
*** jcoufal has joined #openstack-meeting-alt16:05
tbarronjaja16:09
*** igordc has joined #openstack-meeting-alt16:11
*** rdopiera has quit IRC16:31
*** panda has quit IRC16:32
*** panda has joined #openstack-meeting-alt16:36
*** whoami-rajat has quit IRC16:44
*** jcoufal_ has joined #openstack-meeting-alt16:59
*** jcoufal has quit IRC17:02
*** whoami-rajat has joined #openstack-meeting-alt17:06
*** ayoung has joined #openstack-meeting-alt17:14
*** kaisers has quit IRC17:27
*** diablo_rojo has joined #openstack-meeting-alt17:30
*** kaisers has joined #openstack-meeting-alt17:31
*** _erlon_ has quit IRC17:42
*** bhavikdbavishi has quit IRC17:48
*** jcoufal_ has quit IRC18:08
*** s0ru has left #openstack-meeting-alt18:34
*** diablo_rojo has quit IRC18:50
*** diablo_rojo has joined #openstack-meeting-alt18:51
*** diablo_rojo_ has joined #openstack-meeting-alt18:51
*** diablo_rojo_ has quit IRC18:51
*** armstrong has joined #openstack-meeting-alt19:39
*** whoami-rajat has quit IRC19:54
*** jtomasek has quit IRC19:55
*** ayoung has quit IRC19:59
*** diablo_rojo has quit IRC19:59
*** sfernand has quit IRC20:17
*** jtomasek has joined #openstack-meeting-alt20:52
*** raildo has quit IRC21:06
*** diablo_rojo has joined #openstack-meeting-alt21:10
*** tesseract has quit IRC21:19
*** rcernin has joined #openstack-meeting-alt21:24
*** jtomasek has quit IRC21:30
*** hongbin has quit IRC22:01
*** ayoung has joined #openstack-meeting-alt22:01
*** armstrong has quit IRC22:19
*** munimeha1 has quit IRC22:23
*** slaweq has quit IRC22:23
*** igordc has quit IRC22:36
*** carloss has quit IRC23:21
*** tonyb has quit IRC23:32
*** tonyb has joined #openstack-meeting-alt23:32
*** slaweq has joined #openstack-meeting-alt23:42
*** slaweq has quit IRC23:46

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