Wednesday, 2019-07-17

*** slaweq has joined #openstack-meeting00:11
*** slaweq has quit IRC00:15
*** TxGirlGeek has quit IRC00:21
*** mattw4 has quit IRC00:31
*** hemna has joined #openstack-meeting00:35
*** hemna has quit IRC00:42
*** ijw has quit IRC00:42
*** gyee has quit IRC00:48
*** rfolco_l8r is now known as rfolco00:49
*** Liang__ has joined #openstack-meeting00:50
*** dviroel has quit IRC00:54
*** zhangchi has joined #openstack-meeting00:56
*** slaweq has joined #openstack-meeting00:59
zhangchi#startmeeting tricircle01:00
openstackMeeting started Wed Jul 17 01:00:48 2019 UTC and is due to finish in 60 minutes.  The chair is zhangchi. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.01:00
*** openstack changes topic to " (Meeting topic: tricircle)"01:00
openstackThe meeting name has been set to 'tricircle'01:00
zhangchiMorning all.01:01
zhangchiWelcome back to tricircle meeting01:01
*** XSM_HUST has joined #openstack-meeting01:03
*** slaweq has quit IRC01:04
zhangchiHello XSM_HUST. Glad to see you on line01:04
zhangchiHow about your container test  going one01:05
XSM_HUSTSorry, I am busy with the opening report of master's degree recently.01:06
XSM_HUSTSo, the container testing has not progressed.01:07
zhangchiIt doesn't matter01:09
*** TxGirlGeek has joined #openstack-meeting01:09
*** slaweq has joined #openstack-meeting01:11
zhangchiGet ready for your matter at hand01:11
*** TxGirlGeek has quit IRC01:11
zhangchiLast week zhangxiaohan has submmit a bp aims at tricircle tempest rate over 80%01:12
*** Liang__ has quit IRC01:15
*** slaweq has quit IRC01:16
*** Liang__ has joined #openstack-meeting01:16
*** TxGirlGeek has joined #openstack-meeting01:16
*** bobh has joined #openstack-meeting01:18
zhangchiThe options of Series goals and Milestone target in tricircle bp page stays still and need to update01:21
*** diablo_rojo has quit IRC01:34
zhangchiany other topics01:41
zhangchiWelcome XSM_Hust01:42
*** iyamahat_ has quit IRC01:42
*** yamahata has quit IRC01:42
zhangchiNext session is July 31th01:42
zhangchiWecome all01:42
zhangchiif no other topics we will end meeting noew01:43
*** openstack changes topic to "OpenStack Meetings ||"01:43
openstackMeeting ended Wed Jul 17 01:43:28 2019 UTC.  Information about MeetBot at . (v 0.1.4)01:43
openstackMinutes (text):
*** ykatabam has quit IRC01:47
*** ykatabam has joined #openstack-meeting01:47
*** tetsuro has joined #openstack-meeting01:53
*** kunlunwan has joined #openstack-meeting01:54
*** XSM_HUST has quit IRC01:57
*** apetrich has quit IRC01:58
*** kunlunwan has quit IRC02:02
*** yaawang has quit IRC02:10
*** tetsuro has quit IRC02:13
*** bobh has quit IRC02:24
*** ricolin has joined #openstack-meeting02:33
*** enriquetaso has quit IRC02:42
*** jamesmcarthur has joined #openstack-meeting02:48
*** jamesmcarthur has quit IRC02:48
*** jamesmcarthur has joined #openstack-meeting02:48
*** yaawang has joined #openstack-meeting02:58
*** tetsuro has joined #openstack-meeting03:01
*** tetsuro has quit IRC03:05
*** igordc has quit IRC03:08
*** slaweq has joined #openstack-meeting03:11
*** slaweq has quit IRC03:16
*** jbadiapa has quit IRC03:21
*** jbadiapa has joined #openstack-meeting03:21
*** rbudden has joined #openstack-meeting03:23
*** jamesmcarthur has quit IRC03:26
*** yamamoto has quit IRC03:26
*** jamesmcarthur has joined #openstack-meeting03:28
*** yamamoto has joined #openstack-meeting03:28
*** jamesmcarthur has quit IRC03:31
*** Liang__ has quit IRC03:32
*** jamesmcarthur has joined #openstack-meeting03:32
*** psachin has joined #openstack-meeting03:32
*** yamamoto has quit IRC03:33
*** Liang__ has joined #openstack-meeting03:33
*** mmethot has quit IRC03:35
*** rbudden has quit IRC03:36
*** imsurit has joined #openstack-meeting03:36
*** tetsuro has joined #openstack-meeting03:49
*** mmethot has joined #openstack-meeting04:04
*** slaweq has joined #openstack-meeting04:11
*** yamamoto has joined #openstack-meeting04:12
*** slaweq has quit IRC04:16
*** yamamoto has quit IRC04:21
*** tetsuro has quit IRC04:22
*** igordc has joined #openstack-meeting04:22
*** jamesmcarthur has quit IRC04:33
*** yamamoto has joined #openstack-meeting04:41
*** kopecmartin|off is now known as kopecmartin04:54
*** tetsuro has joined #openstack-meeting04:58
*** brinzhang_ has joined #openstack-meeting04:59
*** Luzi has joined #openstack-meeting05:02
*** brinzhang has quit IRC05:02
*** rbudden has joined #openstack-meeting05:02
*** links has joined #openstack-meeting05:03
*** ykatabam has quit IRC05:07
*** slaweq has joined #openstack-meeting05:11
*** slaweq has quit IRC05:17
*** yamamoto has quit IRC05:17
*** TxGirlGeek has quit IRC05:22
*** yamamoto has joined #openstack-meeting05:28
*** vishalmanchanda has joined #openstack-meeting05:29
*** links has quit IRC05:35
*** shilpasd has quit IRC05:37
*** rbudden has quit IRC05:38
*** links has joined #openstack-meeting05:38
*** yamahata has joined #openstack-meeting05:50
*** whoami-rajat has joined #openstack-meeting06:06
*** slaweq has joined #openstack-meeting06:11
*** igordc has quit IRC06:11
*** yamamoto has quit IRC06:14
*** igordc has joined #openstack-meeting06:15
*** slaweq has quit IRC06:16
*** liuyulong has quit IRC06:19
*** pcaruana has joined #openstack-meeting06:20
*** slaweq has joined #openstack-meeting06:28
*** ykatabam has joined #openstack-meeting06:29
*** slaweq has quit IRC06:33
*** igordc has quit IRC06:33
*** tetsuro has quit IRC06:35
*** apetrich has joined #openstack-meeting06:40
*** yamamoto has joined #openstack-meeting06:51
*** slaweq has joined #openstack-meeting07:01
*** yamamoto has quit IRC07:02
*** yamamoto has joined #openstack-meeting07:13
*** ralonsoh has joined #openstack-meeting07:15
*** ttsiouts has joined #openstack-meeting07:15
*** tssurya has joined #openstack-meeting07:29
*** imsurit_ofc has joined #openstack-meeting07:30
*** imsurit has quit IRC07:32
*** imsurit_ofc is now known as imsurit07:32
*** ttsiouts has quit IRC07:46
*** ttsiouts has joined #openstack-meeting07:46
*** yamamoto has quit IRC07:48
*** ttsiouts has quit IRC07:51
*** jraju__ has joined #openstack-meeting07:52
*** links has quit IRC07:53
*** rcernin has quit IRC07:56
*** ttsiouts has joined #openstack-meeting08:04
*** yamamoto has joined #openstack-meeting08:09
*** rcernin has joined #openstack-meeting08:13
*** imsurit_ofc has joined #openstack-meeting08:20
*** imsurit has quit IRC08:22
*** imsurit_ofc is now known as imsurit08:22
*** jawad_axd has joined #openstack-meeting08:36
*** jraju__ has quit IRC08:39
*** jraju__ has joined #openstack-meeting08:41
*** tssurya_ has joined #openstack-meeting08:41
*** tssurya has quit IRC08:41
*** electrofelix has joined #openstack-meeting08:44
*** e0ne has joined #openstack-meeting08:47
*** ociuhandu has joined #openstack-meeting08:57
*** ociuhandu has quit IRC08:58
*** ociuhandu has joined #openstack-meeting09:04
*** ociuhandu has quit IRC09:10
*** ttsiouts has quit IRC09:29
*** ttsiouts has joined #openstack-meeting09:29
*** Liang__ has quit IRC09:32
*** ayoung has quit IRC09:32
*** ttsiouts_ has joined #openstack-meeting09:33
*** ttsiouts has quit IRC09:34
*** ayoung has joined #openstack-meeting09:44
*** ttsiouts_ has quit IRC09:53
*** ttsiouts has joined #openstack-meeting09:53
*** ttsiouts_ has joined #openstack-meeting09:57
*** ttsiouts has quit IRC09:58
*** e0ne has quit IRC10:00
*** imsurit_ofc has joined #openstack-meeting10:01
*** imsurit has quit IRC10:05
*** imsurit_ofc is now known as imsurit10:05
*** ociuhandu has joined #openstack-meeting10:05
*** tssurya_ is now known as tssurya10:10
*** ociuhandu has quit IRC10:13
*** ttsiouts_ has quit IRC10:17
*** ttsiouts has joined #openstack-meeting10:18
*** ttsiouts has quit IRC10:23
*** zhangchi has quit IRC10:37
*** rsimai has quit IRC10:38
*** rsimai has joined #openstack-meeting10:40
*** slaweq has quit IRC10:43
*** slaweq has joined #openstack-meeting10:43
*** belmoreira has joined #openstack-meeting10:45
*** imsurit_ofc has joined #openstack-meeting10:45
*** priteau has joined #openstack-meeting10:45
*** shilpasd has joined #openstack-meeting10:46
*** ociuhandu has joined #openstack-meeting10:46
*** imsurit has quit IRC10:47
*** imsurit_ofc is now known as imsurit10:47
*** carloss has joined #openstack-meeting10:47
*** dh3 has joined #openstack-meeting10:51
*** janders has joined #openstack-meeting10:54
*** ociuhandu has quit IRC10:57
*** martial_ has joined #openstack-meeting11:01
martial_#startmeeting scientific-sig11:01
openstackMeeting started Wed Jul 17 11:01:52 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
dh3hi o/11:02
martial_so this week, we have a couple items to go through followed by AOB11:02
martial_#topic Complete the OpenStack user survey and register scientific OpenStack deployments11:03
*** openstack changes topic to "Complete the OpenStack user survey and register scientific OpenStack deployments (Meeting topic: scientific-sig)"11:03
jandershi Martial11:03
martial_if you have a running OpenStack at your site, we request that you fill the survey11:03
dh3we inadvertently did the survey twice (left hand meet right hand) and wondered if/how the results are deduped11:03
*** b1airo has joined #openstack-meeting11:03
martial_janders: hi :)11:04
martial_#chair b1airo11:04
openstackCurrent chairs: b1airo martial_11:04
martial_dh3: I do not remember if the survey is related to our OpenStack ID11:04
martial_b1airo: hi11:04
b1airoi think it is OpenStack ID related, or at least was...11:05
martial_just checked and it shows my name at the top, so yes it is11:05
martial_OpenStack User Survey 2019 "Step 1 of 5 for Martial Michel"11:05
martial_Therefore it updates your content11:06
martial_(ot at least there is a way to do de-duplication)11:06
martial_but survey away please :)11:07
*** ttsiouts has joined #openstack-meeting11:07
martial_#topic CFP for OpenInfra days Rome11:07
*** openstack changes topic to "CFP for OpenInfra days Rome (Meeting topic: scientific-sig)"11:07
martial_Perfect time zone for this one :)11:07
martial_"OpenInfra Day Italy 2019 will provide a 360-degrees view of Open Infrastructure – from computing, networking, and storage, through hands-on workshops and sessions focussing on real-world stories, more and more focusing on container orchestration and microservices architecture."11:08
martial_two times, two locations: Milan october, 2nd 2019 – Rome october, 3rd 201911:09
martial_#topic Shangai Summit and PTG11:10
*** openstack changes topic to "Shangai Summit and PTG (Meeting topic: scientific-sig)"11:10
martial_Adding this one to the list11:10
martial_The Shanghai summit CFP is over, it was extended11:10
martial_I hope everybody had a chance to submit their proposals11:11
dh3good luck, sadly I spent my "foreign conference" budget already this year11:12
martial_the Scientific SIG will be present with our usual two back to back sessions11:12
martial_b1airo: coming to the summit?11:12
martial_belmoreira: hopefully other opportunities will arise11:13
martial_The Scientific SIG has also requested a presence at the PTG11:13
*** Lucas_Gray has joined #openstack-meeting11:14
martial_From 1/2 day to 1 day (filled the survey last night)11:14
jandersit was a great session in Denver. I'm not sure if I'll be in Shanghai at this stage, but would be very happy to do that again11:14
martial_janders: if you are able to join us, please do so; because our role is much more outreach we tend to go to follow up sessions to understand how to best use novel technologies for our scientific workloads11:15
b1airodon't think i'll make it i'm afraid, already two trips to the States on the horizon before December11:15
martial_#topic SC1911:16
*** openstack changes topic to "SC19 (Meeting topic: scientific-sig)"11:16
martial_following up on our conferences, we need to submit the BoF shortly11:16
martial_Kubecon is at the same time as SC1911:17
b1airowhich will you choose martial_ ?11:17
martial_I will be at SC1911:17
martial_My colleague Rion (who has been on a few of our panels) will be at Kubecon11:17
b1airoKubecon not Docker-y enough for you ;-)11:17
martial_We are going to propose a BoF on cloud federation11:18
martial_as such my colleague Chris is the person that will be with us (if welcome)11:19
martial_we started this conversation on the Scientific SIG Slack11:19
martial_#topic Cloud Federation11:19
*** openstack changes topic to "Cloud Federation (Meeting topic: scientific-sig)"11:19
b1airook, interesting, do you have a list of people interested in the federation bof yet?11:19
martial_am going to make this a regular topic for the next couple months :)11:20
martial_The work I have been participating on “Cloud Federation” is officially in public comment phase for publication as a NIST SP50011:21
martial_it is open until September11:22
martial_(open for review that is)11:22
b1airodoes that provide a window for Summit feedback session on it?11:22
*** raildo has joined #openstack-meeting11:22
martial_unfortunately no, which is why I want to talk about it at our meetings11:23
martial_we will be talking about it at PEARC1911:23
martial_(in a couple weeks)11:23
*** baojg has quit IRC11:24
b1airoah yeah, i would have liked to head to PEARC, maybe next year11:24
martial_so for people interested, this is the change to get your comments in on the efforts of federation11:24
*** baojg has joined #openstack-meeting11:24
*** baojg has quit IRC11:25
martial_note that this is a foundation document (reference architecture)11:25
*** jawad_axd has quit IRC11:25
b1airoperhaps you can give us an overview of NIST SP500 in a future session here martial_ ?11:25
martial_and that there is still a lot of work to be done :)11:25
*** baojg has joined #openstack-meeting11:25
*** baojg has quit IRC11:26
martial_I can, but I will invite my co-authors to join11:26
b1airosounds good11:26
martial_so likely the session that works better in the pm :)11:26
*** baojg has joined #openstack-meeting11:26
martial_(pm for me that is :) )11:26
*** baojg has quit IRC11:26
b1airobetter for me - almost midnight here now11:26
*** baojg has joined #openstack-meeting11:27
martial_#topic AOB11:27
*** openstack changes topic to "AOB (Meeting topic: scientific-sig)"11:27
*** baojg has quit IRC11:27
martial_ad lib time :)11:27
*** baojg has joined #openstack-meeting11:28
b1airoi'm working on a little containerisation problem at the moment and wondering if people can help...11:28
*** tesseract has joined #openstack-meeting11:28
*** baojg has quit IRC11:28
*** baojg has joined #openstack-meeting11:28
dh3if anyone has experience of instances spontaneously/persistently ending up kvm-paused I'd love to hear from you (pm/email) - not made much progress with Google or RH support11:28
*** baojg has quit IRC11:29
jandersis temporary disk space depletion a possibility?11:29
*** baojg has joined #openstack-meeting11:29
dh3I wondered that but the hypervisor has >200GB free so I don't *think* so11:29
b1airohave a use-case for a client-server workflow that builds map cache layers hanging around a Postgres DB plus frontend webserver API, want to be able to fire the whole stack up on-demand within the HPC environment...11:30
*** baojg has quit IRC11:30
*** baojg has joined #openstack-meeting11:30
*** ykatabam has quit IRC11:30
*** baojg has quit IRC11:30
*** rcernin has quit IRC11:30
*** baojg has joined #openstack-meeting11:31
*** baojg has quit IRC11:31
*** baojg has joined #openstack-meeting11:32
b1airowe've got a Docker container that has all the dependencies, and were thinking we could go from there to Singularity image11:32
*** baojg has quit IRC11:32
martial_have you looked at Sarus?11:32
*** baojg has joined #openstack-meeting11:32
*** baojg has quit IRC11:33
*** baojg has joined #openstack-meeting11:33
*** baojg has quit IRC11:34
martial_looked like a very promising OCI compliant runtime11:34
*** baojg has joined #openstack-meeting11:34
b1airocreating the image is easy enough, but naturally things like postgres and apache that have been installed into the image via apt would (IIUC) normally be started in Docker via `service start apache`, but those init.d service scripts try to do that via sudo...11:34
*** baojg has quit IRC11:34
*** baojg has joined #openstack-meeting11:35
b1airoyeah heard about Sarus at CUG, don't think it really adds much that would help in this use-case though11:35
*** baojg has quit IRC11:35
*** baojg has joined #openstack-meeting11:36
dh3running more than one process inside a container always seems to end up being fragile, would multiple-containers be acceptable?11:36
*** baojg has quit IRC11:36
*** baojg has joined #openstack-meeting11:36
*** baojg has quit IRC11:37
b1airodh3: yep, i suspect the "proper" way to do this might be multiple Singularity service "instances" of the same container11:37
*** baojg has joined #openstack-meeting11:37
*** baojg has quit IRC11:38
b1aironot sure how they work from inside a Slurm job yet though...11:38
*** baojg has joined #openstack-meeting11:38
dh3my knee-jerk reaction is "wrapper script" but it's not terribly elegant11:38
*** baojg has quit IRC11:38
*** baojg has joined #openstack-meeting11:39
*** baojg has quit IRC11:39
b1airomy main question is whether there are some standard practices for building containers that allow launching services without root escalation requirements11:39
*** baojg has joined #openstack-meeting11:40
*** baojg has quit IRC11:40
*** baojg has joined #openstack-meeting11:40
*** baojg has quit IRC11:41
b1airodh3: i think i've seen that pause issue at some point in the past, wondering if sw3 is around and has better memory than me11:41
dh3do you mean, not-have-root when building the container? We haven't found a way round that (and suggest users do it in OpenStack where they do have root)11:41
martial_you can create a local account on the container that matches the local user; only problem is that this needs to be done per user11:41
martial_so a `docker build` per user11:41
martial_so create the user last to be able to rely on the previous union layers11:42
*** imsurit_ofc has joined #openstack-meeting11:43
b1airobuilding isn't a problem, can do that on a local dev machine or via remote build service (and  with Singularity 3.3 there's new fakeroot functionality that enables rootless builds, albeit with a couple of caveats)11:43
dh3fakeroot> good to know, ta11:44
*** panda is now known as panda|lunch11:44
*** imsurit has quit IRC11:44
*** imsurit_ofc is now known as imsurit11:44
b1airohow does such a matching container-internal user help martial_ ?11:46
*** baojg has joined #openstack-meeting11:46
*** jawad_axd has joined #openstack-meeting11:49
*** imsurit_ofc has joined #openstack-meeting11:50
martial_you were talking about root-less containers, I have a couple ubuntu based where you can sudo without a password but the container is run with a local user that matches the directory it is in11:50
martial_not sure if it is the use case that you are envisioning11:51
*** imsurit has quit IRC11:52
*** jawad_axd has quit IRC11:52
*** imsurit_ofc is now known as imsurit11:52
b1airosounds like a potential avenue worth looking at11:52
b1airoany Dockerfiles you can point me to?11:52
martial_not public but the core component  you are looking for is11:53
jandersI gotta run, I'll see you guys later. Till next time!11:54
martial_that users get access to the webcam too11:54
b1airodo i smell a deep learning inference application? :-)11:55
martial_you can specifiy the uid and gid as needed by adapting it11:55
*** dviroel has joined #openstack-meeting11:56
martial_and using `ARG`11:56
martial_OpenCV / Tensorflow application11:56
b1airogreat, thanks martial_ , will see how we go11:57
martial_built `FROM` that11:57
b1airook, time to wrap up and sleep11:58
b1airotill next time!11:58
dh3thanks, bye!11:59
*** openstack changes topic to "OpenStack Meetings ||"11:59
openstackMeeting ended Wed Jul 17 11:59:22 2019 UTC.  Information about MeetBot at . (v 0.1.4)11:59
openstackMinutes (text):
*** ociuhandu has joined #openstack-meeting12:04
*** _erlon_ has joined #openstack-meeting12:13
*** ociuhandu has quit IRC12:14
*** apetrich has quit IRC12:21
*** apetrich has joined #openstack-meeting12:31
*** imsurit_ofc has joined #openstack-meeting12:32
*** imsurit has quit IRC12:33
*** imsurit_ofc is now known as imsurit12:33
*** yamamoto has quit IRC12:37
*** panda|lunch is now known as panda12:37
*** yamamoto has joined #openstack-meeting12:41
*** enriquetaso has joined #openstack-meeting12:42
*** shilpasd has quit IRC12:42
*** ijw has joined #openstack-meeting12:44
*** yamamoto has quit IRC12:46
*** ijw has quit IRC12:49
*** belmoreira has quit IRC12:52
*** imsurit_ofc has joined #openstack-meeting12:52
*** imsurit has quit IRC12:53
*** imsurit_ofc is now known as imsurit12:53
*** ttsiouts has quit IRC12:54
*** ttsiouts has joined #openstack-meeting12:55
*** ttsiouts has quit IRC12:59
*** Lucas_Gray has quit IRC12:59
*** yamamoto has joined #openstack-meeting13:01
*** dh3 has quit IRC13:03
*** Lucas_Gray has joined #openstack-meeting13:04
*** imsurit_ofc has joined #openstack-meeting13:07
*** imsurit has quit IRC13:08
*** imsurit_ofc is now known as imsurit13:08
*** yamamoto has quit IRC13:08
*** hemna has joined #openstack-meeting13:14
*** ttsiouts has joined #openstack-meeting13:15
*** artom has quit IRC13:19
*** jawad_axd has joined #openstack-meeting13:23
*** liuyulong has joined #openstack-meeting13:24
*** liuyulong has quit IRC13:26
*** liuyulong73 has joined #openstack-meeting13:28
*** liuyulong73 is now known as liuyulong13:29
*** belmoreira has joined #openstack-meeting13:31
*** jamesmcarthur has joined #openstack-meeting13:32
*** rajinir has joined #openstack-meeting13:34
*** belmoreira has quit IRC13:36
*** psachin has quit IRC13:37
*** Lucas_Gray has quit IRC13:40
*** yamamoto has joined #openstack-meeting13:42
*** yamamoto has quit IRC13:42
*** Lucas_Gray has joined #openstack-meeting13:43
*** jamesmcarthur has quit IRC13:54
*** jraju__ has quit IRC13:55
*** jamesmcarthur has joined #openstack-meeting13:56
*** artom has joined #openstack-meeting13:57
*** jamesmcarthur has quit IRC13:57
*** jamesmcarthur has joined #openstack-meeting13:58
liuyulong#startmeeting neutron_l314:00
openstackMeeting started Wed Jul 17 14:00:14 2019 UTC and is due to finish in 60 minutes.  The chair is liuyulong. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: neutron_l3)"14:00
openstackThe meeting name has been set to 'neutron_l3'14:00
liuyulong#chair haleyb14:00
openstackCurrent chairs: haleyb liuyulong14:00
*** martial_ has quit IRC14:00
*** wwriverrat has joined #openstack-meeting14:01
liuyulong#topic Announcements14:01
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"14:01
liuyulongI have a question14:01
liuyulongWhere we can apply the early-bird discount for Shanghai summit and PTG?14:01
liuyulongI have not received any discount CODE recently. If you have any information, please let us know.14:01
liuyulongAnd we have this PTG plan etherpad now:14:02
*** b1airo has quit IRC14:03
liuyulongAnd one more important thing is, seems we all still do not know the final official 'U' release name.14:03
liuyulongIt is interesting now.14:03
haleybthere will be a vote eventually...14:04
liuyulongChinese Pinyin does not have 'U' starts pronunciation. But I have sent a suggestion to the mail list, like a stone dropped into the ocean, without any response.14:04
*** e0ne has joined #openstack-meeting14:05
*** Luzi has quit IRC14:05
liuyulongAllow me to quote the contents from that mail:14:06
liuyulongAnd my name is Yulong, then 'Uylong' can be a good example to explain my suggestion, : )14:06
slaweqso maybe we should propose 'Uylong' as a name of the most famous chineese neutron core ;)14:07
haleyb+2 :)14:08
liuyulonghaleyb, What vote time is it usually?14:08
*** altlogbot_0 has quit IRC14:09
liuyulongFor OpenStack tradition, it should be a place name. Haha14:09
haleybliuyulong: i don't remember when exactly, but yes, a place or street or ???14:09
liuyulongYes, mountains and rivers14:10
*** njohnsto_ has joined #openstack-meeting14:10
*** belmoreira has joined #openstack-meeting14:10
haleybthe TC will eventually send an email with a place to add suggestions14:11
slaweqyes, usually it was some wiki page or something like that where people were adding proposals for voting IIRC14:11
liuyulongUssuri is more like a Russia word. For Chinese Pinyin, it is "Wusuli".14:12
haleybwe had the same problem in Hong Kong and chose Icehouse (street)14:12
haleybnot sure we will solve this in the L3 meeting though :)14:13
liuyulongOK, Any other announcements?14:13
liuyulongSure, let's move on.14:13
liuyulong#topic Bugs14:13
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"14:13
liuyulongSlawek Kaplonski (slaweq) was our bug deputy last week, thank you for the collection.14:14
liuyulongI will skip all the bugs which were fixed or the related patches are getting merged now.14:14
liuyulongFirst one14:14
openstackLaunchpad bug 1836642 in neutron "Metadata responses are very slow sometimes" [High,Confirmed] - Assigned to Slawek Kaplonski (slaweq)14:14
liuyulongLooks like nova metadata API was do nothing during that 16s+.14:15
liuyulongHere is an example:14:15
*** imsurit_ofc has joined #openstack-meeting14:15
openstackLaunchpad bug 1821912 in neutron "intermittent ssh failures in various scenario tests" [High,In progress] - Assigned to LIU Yulong (dragon889)14:15
liuyulongslaweq sent some similar logs here before.14:15
slaweqsean-k-mooney was looking into it yesterday with me, and he found that in case which we were analysing there was most of the time wasted on
slaweqbecause when nova is preparing metadata for instance it is asking neutron server for security groups for instance :O14:16
slaweqand it looks that in this case that call to neutron took most of the time and caused problem14:16
*** imsurit has quit IRC14:17
*** imsurit_ofc is now known as imsurit14:17
*** irclogbot_1 has quit IRC14:17
slaweqbecuase of that I sent today DNM patch to check time-cost of those resync quota methods14:17
*** ricolin_ has joined #openstack-meeting14:17
slaweqnjohnston_: ^^ that's explanation for Your question in review there :)14:17
slaweqbut I'm also looking at other examples14:17
haleybwhy does nova need that?  is it something given in metadata?14:17
liuyulongWe can not blame nova now, haha14:17
slaweqhaleyb: I have no idea14:17
*** altlogbot_0 has joined #openstack-meeting14:18
njohnsto_yes security groups are part of metadata14:18
liuyulonghaleyb, I know some clue14:18
slaweqso, I was looking also at other examples and I found that it's not always this quota resync which takes long time14:18
liuyulonghaleyb, when nova try to sync network info it will try to get the port and its secruity group informations.14:18
slaweqBUT, in every case in almost the same time as timeouted request to metadata is send, there is some API call in neutron which takes more than 10 seconds14:19
*** ricolin has quit IRC14:19
slaweqso currently it looks for me like some slow down in neutron or maybe in db? I don't know14:19
haleybjust a thought, but we should look at the code making the call, and make sure it's not asking for everything, but supplying a good filter14:20
liuyulongDB slow query, maybe something like the bug we talked about last week.14:20
slaweqhaleyb: sure, but it is working fine in most cases14:20
njohnsto_in the long term it would be good to14:20
*** TxGirlGeek has joined #openstack-meeting14:21
slaweqin tempest job there is plenty of vms spawned, each of them is asking for public-keys to metadata14:21
*** belmoreira has quit IRC14:21
slaweqand sometimes, one of such queries is long (more than 10 seconds)14:21
slaweqand it's not last/middle/first test AFAICT - there is no any other pattern IMO14:21
liuyulongSome related neutron API call is here:
*** altlogbot_0 has quit IRC14:22
*** yamamoto has joined #openstack-meeting14:22
slaweqthe only common thing is that VM is doing request GET /2009-04-04/public-keys/ and it takes more than 10 seconds14:22
slaweq10 seconds is set as timeout in cirros script14:22
slaweqso this fails14:22
slaweqeven if later nova send proper 200 response14:22
*** belmoreira has joined #openstack-meeting14:23
slaweqI will try to read one more time all analysis from sean and go through all those calls there14:23
slaweqmaybe I will find something more14:23
liuyulongslaweq, OK, thank you for working on this. Where is your DNM patch?14:25
haleybslaweq: i wonder how many SGs nova is asking for after noticing this...14:25
haleybit is at least passing the tenant_id though14:26
liuyulongslaweq, this should be the metadata API call neutron security group list:
njohnston_a related bug filed under the tripleo project for similar failures in queens:
openstackLaunchpad bug 1836046 in tripleo "tempest.scenario.test_network_basic_ops.TestNetworkBasicOps Failing on queens" [Critical,Triaged]14:26
slaweqhaleyb: but as I said, in other cases it wasn't exactly the same, and there was other call which took long time14:26
*** jamesmcarthur has quit IRC14:26
slaweqnjohnston_: yep14:26
slaweqand we have also d/s bug in bugzilla for the same14:27
*** altlogbot_1 has joined #openstack-meeting14:27
liuyulongOne more thing is, we have added some time-consuming tracking log. It will help us to find some potential causes of CI failure.14:27
liuyulongL3 RPC time-costs:14:27
liuyulongL3 router processing time:14:27
njohnston_this is great stuff14:28
openstackLaunchpad bug 1836253 in neutron "Sometimes InstanceMetada API returns 404 due to invalid InstaceID returned by _get_instance_and_tenant_id()" [Medium,Confirmed] - Assigned to Bence Romsics (bence-romsics)14:28
liuyulongAnd this one looks like also related to the former bugs.14:29
slaweqI though that it may be related14:29
slaweqbut it seems that we don't have this cache configured in neutron-metadata agent in any job14:29
slaweqso it's not the case in gate14:29
liuyulongMore like a race condition.14:30
liuyulongNext one14:31
openstackLaunchpad bug 1806032 in neutron "neutron doesn't prevent the network update from external to internal when floatingIPs present" [Low,New]14:31
liuyulongThis will be proceed again from my understanding.14:32
*** altlogbot_1 has quit IRC14:32
liuyulongI don't know why a cloud wants to change the external network type, but it is indeed a neutron bug.14:32
*** yamamoto has quit IRC14:33
openstackLaunchpad bug 1835914 in neutron "Test test_show_network_segment_range failing" [Medium,Confirmed]14:33
liuyulongLet's try to contact Kailun Qin, he is the original author.14:33
*** altlogbot_2 has joined #openstack-meeting14:34
liuyulongAnd for this new feature, our test team have report many bugs. I will file them to the launchpad recently.14:35
liuyulongNext two has been talked last week:14:36
openstackLaunchpad bug 1834308 in neutron "[DVR][DB] too many slow query during agent restart" [Medium,Confirmed] - Assigned to LIU Yulong (dragon889)14:36
openstackLaunchpad bug 1835663 in neutron "Some L3 RPCs are time-consuming especially get_routers" [Medium,Confirmed]14:37
*** imsurit_ofc has joined #openstack-meeting14:37
liuyulongYes, I will upload some fix for the DB slow query.14:37
*** altlogbot_2 has quit IRC14:38
*** imsurit has quit IRC14:38
*** imsurit_ofc is now known as imsurit14:38
liuyulongNo more bug from me today.14:39
slaweq\o/ no more bugs \o/ :D14:39
haleybthere was one i had14:39
openstackLaunchpad bug 1835731 in neutron "Neutron server error: failed to update port DOWN" [High,In progress] - Assigned to Oleg Bondarev (obondarev)14:39
slaweqhaleyb: :(14:39
*** altlogbot_2 has joined #openstack-meeting14:40
haleybliuyulong had a -1 on the change, didn't know if we needed to discuss14:40
liuyulongWe have remove that config for master branch14:40
liuyulongAnd that removal fixes the bug, IMO14:40
liuyulongBut for the stable branches, it may need another approach.14:41
ralonsohIMO, we can use this patch with a note and then cherry-pick to stable branches14:41
ralonsohthe logic seems to be correct in master and stable14:42
*** artom has quit IRC14:42
slaweqand later merge liuyulong's patch which removes this option in master14:43
haleybok, seems we have a way forward, just didn't want it to fall through the cracks14:43
*** altlogbot_2 has quit IRC14:44
*** altlogbot_3 has joined #openstack-meeting14:46
haleybthat's all from me14:46
ralonsohjust a last note:
ralonsohreviews are welcome14:46
liuyulongOK, Let's move on.14:47
liuyulong#topic Routed Networks14:47
*** openstack changes topic to "Routed Networks (Meeting topic: neutron_l3)"14:47
liuyulongI have get no reponse for the concern of "externel network with multiple segments".14:48
liuyulongno reponse and not too much activities from these patches.14:48
ralonsohmaybe mlavalle can ping David14:49
wwriverratyes. sorry. I fear I'm a little over my head on how far reaching allowing multiple segments per host touches14:49
*** jamesmcarthur has joined #openstack-meeting14:49
*** altlogbot_3 has quit IRC14:50
wwriverratWould love to have a 1-1 review with someone who has pulled ^ code and knows the intent of where it was going14:51
*** mattw4 has joined #openstack-meeting14:51
*** duochao has joined #openstack-meeting14:51
liuyulongWe are now facing such issue, external network has a large sets IPs,  broadcast domain is too large.14:52
*** altlogbot_0 has joined #openstack-meeting14:52
wwriverratOur original thought: why not allow multiple segments per network *everywhere* (thinking that for most implementations only one would be returned in a list)14:53
wwriverratbut this crosses api, rpc and agent boundries14:53
wwriverratso... I know mlavalle and I were trying to find time to have a review session. Will keep trying14:54
liuyulongboth mlavalle and tidwellr may help14:55
*** altlogbot_0 has quit IRC14:56
liuyulong#topic On demand agenda14:56
*** openstack changes topic to "On demand agenda (Meeting topic: neutron_l3)"14:56
liuyulongI've added a small NOTE here: we have abandoned it.14:56
liuyulongAnd these patches should be abandoned. I have no right to do that.14:56
liuyulongWe are running out of time.14:58
*** altlogbot_1 has joined #openstack-meeting14:58
liuyulongus stop here14:58
*** openstack changes topic to "OpenStack Meetings ||"14:58
openstackMeeting ended Wed Jul 17 14:58:21 2019 UTC.  Information about MeetBot at . (v 0.1.4)14:58
openstackMinutes (text):
*** liuyulong has quit IRC14:59
*** gyee has joined #openstack-meeting14:59
*** altlogbot_1 has quit IRC15:02
*** njohnsto_ has quit IRC15:02
*** igordc has joined #openstack-meeting15:02
*** altlogbot_0 has joined #openstack-meeting15:04
duochaoIs anyone here?15:05
*** artom has joined #openstack-meeting15:05
*** ociuhandu has joined #openstack-meeting15:06
*** duochao has quit IRC15:07
*** altlogbot_0 has quit IRC15:08
*** belmoreira has quit IRC15:08
*** priteau has quit IRC15:11
*** jraju__ has joined #openstack-meeting15:12
*** ttsiouts has quit IRC15:13
*** ttsiouts has joined #openstack-meeting15:14
*** altlogbot_3 has joined #openstack-meeting15:14
*** altlogbot_3 has quit IRC15:18
*** ttsiouts has quit IRC15:18
*** tssurya has quit IRC15:19
*** ociuhandu has quit IRC15:19
*** altlogbot_1 has joined #openstack-meeting15:20
*** zhengMa has joined #openstack-meeting15:21
*** jawad_axd has quit IRC15:23
*** altlogbot_1 has quit IRC15:24
*** jamesmcarthur has quit IRC15:24
*** wwriverrat has quit IRC15:29
*** Luzi has joined #openstack-meeting15:30
*** altlogbot_0 has joined #openstack-meeting15:34
*** altlogbot_0 has quit IRC15:38
*** altlogbot_1 has joined #openstack-meeting15:40
*** belmoreira has joined #openstack-meeting15:41
*** belmoreira has quit IRC15:42
*** davidsha has joined #openstack-meeting15:43
*** altlogbot_1 has quit IRC15:44
*** altlogbot_2 has joined #openstack-meeting15:46
*** rosmaita has joined #openstack-meeting15:46
*** altlogbot_2 has quit IRC15:50
*** altlogbot_0 has joined #openstack-meeting15:52
*** artom has quit IRC15:52
*** altlogbot_0 has quit IRC15:58
*** artom has joined #openstack-meeting15:59
*** e0ne has quit IRC16:00
jungleboyj#startmeeting Cinder16:00
openstackMeeting started Wed Jul 17 16:00:35 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
jungleboyjToday's agenda:16:01
geguileohi! o/16:01
jungleboyjCourtesy ping:  jungleboyj whoami-rajat rajinir lseki carloss pots woojay erlon geguileo eharney rosmaita enriquetaso e0ne smcginnis davidsha walshh_ xyang hemna _hemna16:01
_pewp_jungleboyj ( ´ ▽ ` )ノ16:01
jungleboyjHey everyone.  Wait one more minute to see if we get anyone else.16:03
*** abishop has joined #openstack-meeting16:03
*** altlogbot_3 has joined #openstack-meeting16:04
jungleboyjOk.  Guessing this is it for today.16:04
jungleboyjI know Sean is at a conference and didn't think he could make it.16:04
jungleboyj#topic Announcements16:04
*** openstack changes topic to "Announcements (Meeting topic: Cinder)"16:04
jungleboyjThe usual reminder that we are almost to Milestone 2.16:04
jungleboyjSo, we have Spec freeze next week and driver merge deadline.16:05
jungleboyjI have more discussion on specifics there later.16:05
jungleboyjAlso a reminder that we have the deadline to show drivers trying to run with Py3.7y16:06
jungleboyjI know people have been working on this as I have heard frustration in the channel.16:06
jungleboyjIs there anyone that has their CI working with Py3.7 that is here?16:06
potsI've got it working but not posting comments just yet.16:07
jungleboyjpots:  Awesome.16:07
jungleboyjWould encourage those of you that have it working to keep an eye on the Cinder channel/mailing lists so you guys might be able to help each other.16:07
*** altlogbot_3 has quit IRC16:08
potsA word of caution to others, I tried moving up to bionic to get Python 3.7 support but found that the kernel crashed when starting nested VMs, so I reverted to Xenial and just used the deadsnakes ppa for Python 3.7.16:08
jungleboyjI will be going through the CI results in the next couple of weeks to see who all is running with Py3.7.  I have seen at least one py3.5.  I am not going to mark a driver unsupported for that, but by the end of Train it will need to be py3.7 or it will get marked.16:09
*** altlogbot_2 has joined #openstack-meeting16:10
jungleboyjThanks for the info pots16:10
jungleboyjLets me to the main agenda16:10
jungleboyj#topic stable releases update (and controversy)16:11
*** openstack changes topic to "stable releases update (and controversy) (Meeting topic: Cinder)"16:11
rosmaitathe update is we've cut a bunch of releases from the stable branches, see the etherpad for details16:11
rosmaitanow the controversy16:11
rosmaitacinder stable/rocky and stable/queens are being held up over a question about a backport to stable/rocky16:11
rosmaitabackport in question is "Declare multiattach support for HPE MSA"16:12
rosmaitabackport was allowed by cinder team because there wasn't a code change, just a change to a flag to indicate multiattach support16:12
rosmaitathe objection is: has the already existing code been tested with stable/rocky?16:12
rosmaitathe change in is to the dothill driver, which isn't a currently supported driver16:12
rosmaitabut it *is* the base class for supported drivers that run 3rd party CI: Lenovo FC/ISCSI and HPMSA FC/ISCSI16:12
rosmaitabut, unless i'm reading the logs incorrectly, those CIs are not currently testing multiattach on master (so I doubt they are testing it in the stable branches)16:12
rosmaitarecent test logs so you can check my work:16:13
jungleboyjpots ^^^16:13
*** Liang__ has joined #openstack-meeting16:13
rosmaitai thik we have two options here:16:13
rosmaita(option-1) revert the change from stable/rocky16:13
rosmaitamriedem has already put up a patch for that16:14
*** altlogbot_2 has quit IRC16:14
rosmaita(option-2) the proposed release is 13.0.6; change it to 13.1.0 to indicate a new feature16:14
*** irclogbot_3 has joined #openstack-meeting16:14
rosmaitathat's a lot to digest, so i'll wait a few minutes to hear what people think16:14
*** Liang__ is now known as LiangFang16:14
*** altlogbot_3 has joined #openstack-meeting16:15
jungleboyjrosmaita:  Thanks.  So I would like to hear from pots what level of testing they did since he is the one who worked on that.16:15
eharneythe version bump option is kind of appealing to dodge the issue of landing a change in stable and then undoing it -- but as part of this... how much do we know about how well this works?  has it been thoroughly tested?16:16
rosmaitai'm worried about the test coverage, tbh16:16
jungleboyjeharney:  I am ok with the version bump.  I am curious if this was backported based on customer request.16:17
rosmaitawe may need to update the driver doc that sean just added to include you must run the multiattach tests in gate to be allowed to turn the flag on in a driver16:17
*** Lucas_Gray has quit IRC16:17
*** sfernand has joined #openstack-meeting16:17
*** irclogbot_3 has quit IRC16:17
*** ijw has joined #openstack-meeting16:17
potsThe CI isn't testing it explicitly no.  And yes, it was a customer request to backport it.16:18
jungleboyjrosmaita:  That is a good thought.16:18
eharneywe've found that just passing multiattach tempest tests is not sufficient to know that the feature even works at a basic level16:18
jungleboyjpots:  Did you test it manually?16:18
eharneyso it would be good to hear about hands-on testing with it16:18
jungleboyjrosmaita:  The 3rd Party CI requirement sounds like a good midcycle topic.16:19
rosmaitaok, i will add it to the etherpad16:20
*** ricolin_ is now known as ricolin16:20
potsi did some manual testing but frankly I don't remember enough that i think it should count.  i would welcome some guidance into what would be considered adequate testing.16:20
*** woojay has joined #openstack-meeting16:20
eharneythe scenario that broke on a handful of drivers was, attach to two instances, detach from one, and then make sure I/O continues to work as expected on the other instance16:20
jungleboyjeharney:  ++16:21
jungleboyjrosmaita:  Added.16:21
eharneyat least three drivers failed to do that without falling apart, which is a pretty minimal requirement for this to be a working feature16:21
*** efried is now known as efried_rollin16:21
*** thgcorrea has joined #openstack-meeting16:22
potsi'll check that out today.16:22
jungleboyjpots:  Ok.  Thank you.16:23
rosmaitawe can hold up the release another week16:23
jungleboyjrosmaita: eharney  If pots manually verifies the environment then are we ok with going for the 13.1.0 bump?16:23
rosmaitai think that would be a good compromise16:24
jungleboyjWe probably shouldn't have backported it, but it was kind of a bug that they didn't have the flag for what was supported.16:24
* jungleboyj sighs16:24
eharneyis the idea there that's also a promise of "we won't backport this kind of change in the future"?16:24
rosmaitai think we should discuss that16:24
jungleboyjeharney:  Yeah, I think we should probably say that.16:24
rosmaitai think with the drivers we have a different situation that with the "regular" code16:25
jungleboyjYeah. That is a longer future discussion.16:25
rosmaitawhat i mean is that it may be ok to backport some feature-esque changes, nothing major16:25
eharneyit was quite nice when we were a little more liberal with backports to driverfixes branches... not having that as an option leaves kind of a gap for what to do now16:25
jungleboyjeharney:  Yeah,  I was just thinking that.16:26
jungleboyjThe longer lived branches are a blessing and a curese.16:26
rosmaitaso the key point is that we're not promising anything by what we do with stable/rocky for this next release16:26
jungleboyjrosmaita:  Yes.16:26
rosmaitaok, cool, just want to make sure that's in the minutes16:27
jungleboyj#action pots to test the requested multi-attach scenario16:27
jungleboyj#action we will go with 13.1.0 once the results have been reported.16:27
rosmaitaThe People don't seem to be demanding new stable/rocky and stable/queens releases ATM, so i think it is ok to wait16:27
jungleboyjEveryone ok with that response?16:27
jungleboyjrosmaita:  ++16:28
rosmaitai am good with that response16:28
jungleboyjOk.  Cool.  Yay for resolving controversy.16:28
rosmaitathat's all from me, then16:28
jungleboyjrosmaita:  Thank you for keeping up with those releases.16:29
rosmaitanp, glad to stir things up16:29
jungleboyj#topic Spec:  Leverage compression hardware accelerator16:29
*** openstack changes topic to "Spec: Leverage compression hardware accelerator (Meeting topic: Cinder)"16:29
LiangFangI have reworked with the spec16:29
LiangFangit seems the spec will be refused to check-in on 7-22?16:30
LiangFangJuly 22 is the latest day for train release, right/16:30
jungleboyjLiangFang:  I wouldn't say that.  It depends on if eharney and rosmaita are ok with the updates you have made.16:31
rosmaitai will read through this afternoon16:31
LiangFangeharney: I and Mazheng did test for NFS and ceph as backend16:31
jungleboyjI will do the same.  I know we talked about this at the PTG and I thought had worked through the majority of the issues.  Hope we can get it merged.16:32
LiangFangit should work16:32
eharneyit works because those drivers just don't end up using the hardware compressor path at all?16:32
LiangFangthe volume will be mapped to a path16:33
rosmaitaLiangFang: i do have a question about nova -- i guess we need to be sure that nova can handle a compressed container_format gracefully -- i'm not sure what it does now if you have a container_format it doesn't understand16:33
LiangFangand this path is a normal file path16:33
eharneyi don't think that's accurate for nfs with snapshots, but i might be missing something16:34
*** altlogbot_3 has quit IRC16:34
LiangFangrosmaita: nova with new container_format, we will do test today, thanks16:35
LiangFangand let you know16:35
rosmaitaLiangFang: thanks!16:36
*** altlogbot_1 has joined #openstack-meeting16:36
LiangFangeharney: to just use nfs as backend storage, no snapshots yet16:36
LiangFangwe only tested nfs without snapshots16:37
LiangFangeharney: do you mean a volume is created from NFS, and then we create snapshot on this volume, and then upload this volume as image?16:38
jungleboyjOk.  So, I think there some updates needed to the spec and we will review.16:38
jungleboyjAnd some testing done.16:38
eharneyLiangFang: yes16:39
eharneyi'll check out the spec again16:39
LiangFangeharney: ok, we will do this test today16:39
*** sfernand has quit IRC16:39
LiangFangeharney: thanks16:39
jungleboyjChanges need to be merged by 7/2516:39
LiangFangjungleboyj: OK16:40
jungleboyjSo, we will do one last check-in on these things next Wednesday.16:40
LiangFangwe will do our best to catch train release16:40
*** links has joined #openstack-meeting16:40
* jungleboyj giggles. Catch the Train16:40
*** sfernand has joined #openstack-meeting16:40
jungleboyjOk.  So lets move on.16:41
*** jraju__ has quit IRC16:41
LiangFangcurrently we have 2 engineer working on this16:41
jungleboyj#topic Review prep for Milestone 2.16:42
*** openstack changes topic to "Review prep for Milestone 2. (Meeting topic: Cinder)"16:42
*** artom has quit IRC16:42
jungleboyjSo, we have a couple of drivers that I have been pinged about:16:42
jungleboyjFirst, re-adding the Infortrend driver.16:42
jungleboyjTheir CI is running and passing again.16:42
jungleboyjThe vendor indicates that they plan to continue support.16:43
jungleboyjThey have updated the driver to support the new exception handling.16:43
jungleboyjIn driver instead of in cinder/exception.16:43
jungleboyjI am ok with adding it back in unless others have objections.16:43
jungleboyjKnow it is a little late but given that it is a re-add I don't feel a need to nit-pick.16:44
jungleboyjI voted in the driver.  Please add your votes.16:44
jungleboyjNow this one is more fun.  :-)16:44
jungleboyjpots: You want to explain?16:45
potsSure.  So I need to add a driver for Seagate storage arrays.16:45
potsSeagate acquired dothill a few years ago and took over maintenance of the dothill driver and the drivers that subclass it.  The dothill driver became unsupported at that point, which causes a little confusion because other drivers subclass the dothill driver.16:45
potsRather than adding a new Seagate driver and subclassing the dothill driver, I submitted a patch (WIP) to re-enable the dothill driver and rename it to "Seagate".16:45
potsThe patch is cosmetic changes only, and includes documentation, release note and support matrix updates, and patches to the the HPMSA and Lenovo drivers to use the new class names.16:46
potsSo the end result is that the dothill driver is gone, replaced by a "supported" Seagate driver.16:46
*** irclogbot_3 has joined #openstack-meeting16:47
potsThis seemed like a better long term solution than just subclassing the dothill driver again.16:47
jungleboyjSo, I think that this is actually a good change as it is getting rid of the weird driver that isn't a driver.16:47
jungleboyjThe driver has been tested all along as part of the HPE MSA and Lenovo CIs.16:48
jungleboyjpots:  Will add a CI job for it.16:48
jungleboyjThey have been active and kept their CI running.16:48
jungleboyjSo, it is a little late in the game to 'add' the driver but I think it is low risk and there is a good argument for it.16:48
eharneythis is ok, but i suspect that in the long run it will be easier to keep all this clean by moving most of the code to a common class that all three can inherit from instead of inheriting drivers from other drivers16:49
* jungleboyj shakes my finger at people for coming in at the last minute. ;-)16:49
eharneyi wouldn't hold it up for that now though16:49
rosmaitai agree with eharney16:49
eharneythis is bound to cause some confusion and messes later16:49
jungleboyjeharney:  Well, that is how it currently is and it has caused confusion because we have one driver that can't actually be run by itself.16:49
rosmaitawe can worry about it when seagate decides to stop supporting it :P16:49
eharneyit's not16:50
jungleboyjsmcginnis: Didn't like what we are currently doing.16:50
eharneybecause the thing it was inheriting from currently was still a "driver"16:50
*** irclogbot_3 has quit IRC16:50
jungleboyjeharney: Ok, I don't understand.16:50
jungleboyjeharney:  No, it was just a dothill library.16:50
jungleboyjLenovo and HPE MSA used it.16:50
eharneynamed DotHillISCSIDriver16:50
potsthe dothill driver is an actual driver, it just contains extra code now to prevent it from being invoked without subclassing.16:51
jungleboyjpots:  Right.16:51
jungleboyjeharney:  So what are you proposing for the future?16:51
rosmaitait is definitely a plus that it will be a "real" driver and have CI16:52
*** imsurit_ofc has joined #openstack-meeting16:52
eharneythe proposal is to make a library of the common shared code that isn't a driver16:53
jungleboyjrosmaita: Ok.  So we are short on time.  It sounds like we are in agreement that this is good for now and making a library for the shared code in the future could be good.16:53
jungleboyjeharney:  Ok.16:53
rosmaitajungleboyj: that is my position in a nutshell16:53
jungleboyjSomething else to discuss for the mid-cycle.  How we would like that to happen.16:54
*** imsurit has quit IRC16:54
*** imsurit_ofc is now known as imsurit16:54
jungleboyjOk, specs that are waiting to merge.16:54
*** jbadiapa has quit IRC16:55
jungleboyj#link  The Untyped vol to default vol type is close.16:55
jungleboyjWould be nice if we could agree and merge that.16:55
jungleboyjI think the volume rekey is good to go:16:56
jungleboyjThere are two small comments that need to be addressed and then we can merge it.16:56
eharneyyeah i'll tweak the "work items" list16:56
jungleboyjeharney:  Ok.  Great and then I will merge it.16:56
jungleboyjLast.  The Image Encryption sepc:16:57
jungleboyjSo, I think it is down to whether eharney 's comments are addressed.16:57
Luzieharney, did you read mhen16:58
Luzis comment16:58
eharneymy only outstanding concern was more about the general question of having multiple ways that images are encrypted, but we've collectively decided that that is ok, so i'm ok with this one16:58
eharneyremoved my -2, will give it another read-over soon16:59
Luzieharney, thank you16:59
*** irclogbot_2 has joined #openstack-meeting16:59
*** iyamahat has joined #openstack-meeting16:59
*** artom has joined #openstack-meeting17:00
jungleboyjeharney:  Ok.  Cool.  So, I will read through it after the meeting.  We will try to get this merged for you Luzi17:00
eharneyLuzi: thanks for tolerating all of my complaining on this one :)17:00
jungleboyjIf you can provide updated patch once we have made comments.17:01
jungleboyjOk.  Where did the time go.  It is 12:01 already.17:01
jungleboyjSo, thank you everyone for a productive meeting.17:01
Luzijungleboyj, i will do so17:01
jungleboyjLets get specs and drivers merged.17:01
jungleboyjLook forward to talking to you next week.17:01
jungleboyjReminder to check the etherpad on the mid-cycle for next month.  I am booked.17:02
*** irclogbot_2 has quit IRC17:02
jungleboyjDon't forget to vote for Shanghai  presentations!17:02
jungleboyjTalk to you all next week.17:02
*** openstack changes topic to "OpenStack Meetings ||"17:02
openstackMeeting ended Wed Jul 17 17:02:51 2019 UTC.  Information about MeetBot at . (v 0.1.4)17:02
openstackMinutes (text):
*** Luzi has quit IRC17:03
*** rosmaita has left #openstack-meeting17:03
*** ekcs has joined #openstack-meeting17:04
*** zhengMa has quit IRC17:07
*** davidsha has quit IRC17:07
*** electrofelix has quit IRC17:15
*** ociuhandu has joined #openstack-meeting17:17
*** jamesmcarthur has joined #openstack-meeting17:19
*** woojay has left #openstack-meeting17:20
*** ociuhandu has quit IRC17:22
*** iyamahat has quit IRC17:26
*** yamahata has quit IRC17:26
*** baojg has quit IRC17:40
*** baojg has joined #openstack-meeting17:40
*** baojg has quit IRC17:41
*** baojg has joined #openstack-meeting17:41
*** iyamahat has joined #openstack-meeting17:41
*** baojg has quit IRC17:41
*** baojg has joined #openstack-meeting17:42
*** baojg has quit IRC17:42
*** baojg has joined #openstack-meeting17:43
*** baojg has quit IRC17:43
*** baojg has joined #openstack-meeting17:43
*** baojg has quit IRC17:44
*** baojg has joined #openstack-meeting17:44
*** baojg has quit IRC17:45
*** baojg has joined #openstack-meeting17:45
*** baojg has quit IRC17:45
*** baojg has joined #openstack-meeting17:46
*** baojg has quit IRC17:46
*** baojg has joined #openstack-meeting17:47
*** baojg has quit IRC17:47
*** irclogbot_1 has joined #openstack-meeting17:47
*** baojg has joined #openstack-meeting17:47
*** baojg has quit IRC17:48
*** baojg has joined #openstack-meeting17:48
*** baojg has quit IRC17:49
*** baojg has joined #openstack-meeting17:49
*** baojg has quit IRC17:49
*** baojg has joined #openstack-meeting17:50
*** irclogbot_1 has quit IRC17:50
*** baojg has quit IRC17:50
*** baojg has joined #openstack-meeting17:51
*** baojg has quit IRC17:51
*** baojg has joined #openstack-meeting17:51
*** baojg has quit IRC17:52
*** baojg has joined #openstack-meeting17:52
*** baojg has quit IRC17:53
*** ociuhandu has joined #openstack-meeting17:53
*** yamahata has joined #openstack-meeting18:00
*** ociuhandu has quit IRC18:01
*** ociuhandu_ has joined #openstack-meeting18:01
*** ociuhandu_ has quit IRC18:18
*** e0ne has joined #openstack-meeting18:36
*** mattw4 has quit IRC18:47
*** e0ne has quit IRC18:52
*** ianychoi has quit IRC18:56
*** ianychoi has joined #openstack-meeting18:56
*** ralonsoh has quit IRC19:04
*** links has quit IRC19:05
*** ociuhandu has joined #openstack-meeting19:15
*** igordc has quit IRC19:18
*** wwriverrat has joined #openstack-meeting19:19
*** thgcorrea has quit IRC19:19
*** ociuhandu has quit IRC19:21
*** irclogbot_0 has joined #openstack-meeting19:23
*** irclogbot_0 has quit IRC19:26
*** irclogbot_0 has joined #openstack-meeting19:27
*** irclogbot_0 has quit IRC19:30
*** links has joined #openstack-meeting19:31
*** irclogbot_2 has joined #openstack-meeting19:31
*** irclogbot_2 has quit IRC19:34
*** kopecmartin is now known as kopecmartin|off19:36
*** irclogbot_3 has joined #openstack-meeting19:39
*** irclogbot_3 has quit IRC19:42
*** irclogbot_1 has joined #openstack-meeting19:47
*** gyee has quit IRC19:49
*** gyee has joined #openstack-meeting19:50
*** irclogbot_1 has quit IRC19:50
*** irclogbot_0 has joined #openstack-meeting19:59
*** irclogbot_0 has quit IRC20:02
*** mattw4 has joined #openstack-meeting20:04
*** mattw4 has joined #openstack-meeting20:04
*** wwriverrat has quit IRC20:10
*** bnemec has quit IRC20:11
*** irclogbot_0 has joined #openstack-meeting20:12
*** irclogbot_0 has quit IRC20:14
*** bnemec has joined #openstack-meeting20:15
*** igordc has joined #openstack-meeting20:15
*** beekneemech has joined #openstack-meeting20:16
*** bnemec has quit IRC20:16
*** beekneemech has quit IRC20:16
*** bnemec has joined #openstack-meeting20:16
*** efried_rollin is now known as efried20:18
*** artom has quit IRC20:18
*** beekneemech has joined #openstack-meeting20:18
*** enriquetaso has quit IRC20:23
*** ociuhandu has joined #openstack-meeting20:24
*** ociuhandu has quit IRC20:33
*** e0ne has joined #openstack-meeting20:38
*** pcaruana has quit IRC20:48
*** bnemec has quit IRC20:48
*** jamesmcarthur has quit IRC20:51
*** bnemec has joined #openstack-meeting20:51
*** beekneemech has quit IRC20:54
*** tdasilva has joined #openstack-meeting20:57
*** alecuyer has joined #openstack-meeting20:57
*** patchbot has joined #openstack-meeting20:59
timburke#startmeeting swift21:00
openstackMeeting started Wed Jul 17 21:00:01 2019 UTC and is due to finish in 60 minutes.  The chair is timburke. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: swift)"21:00
openstackThe meeting name has been set to 'swift'21:00
timburkewho's here for the swift meeting?21:00
*** Liang__ has joined #openstack-meeting21:00
*** LiangFang has quit IRC21:01
claygoh yeah21:02
timburke#topic shanghai21:02
*** openstack changes topic to "shanghai (Meeting topic: swift)"21:02
*** _erlon_ has quit IRC21:02
timburkei made an etherpad!21:03
claygoh snap is it etherpad time already!  😓21:03
timburkeif you're coming (or even just hopeful that you'll be coming), please add yourself!21:03
timburkeclayg, mainly because of logistics -- foundation wants a rough headcount21:04
timburkei also started seeding some potential onboarding topics; please add anything else that might be good "intro" material21:04
mattoliverauI really need to poke Suse to make a decision, ecp because visa's will be involved.21:05
timburkei feel like this is an awesome opportunity to reach out and meet potential new contributors21:05
alecuyerSame with OVH I think (romain?)21:05
*** mattw4 has quit IRC21:05
rledisezalecuyer: you can copy/paste my line ;)21:05
alecuyerright :-)21:05
tdasilvaanyone has the link for the visa form? can you add to etherpad? can't seem to find it21:06
*** raildo has quit IRC21:06
rledisezthis one? ^21:06
timburkei'll be sure to bring up shanghai again when i see the discount codes go out21:06
rledisezoups, no :)21:06
tdasilvarledisez: yep, thanks!21:07
*** mattw4 has joined #openstack-meeting21:07
tdasilvajust noticed the dealine too, hadn't seen that yet21:07
timburkeetherpad was the main thing i wanted to bring up regarding the summit; does anyone have other questions about it?21:09
claygis this one of those places you can't bring a laptop/phone?21:09
alecuyerI was wondering about that21:09
timburke...maybe. i'll probably have a freshly-formatted computer, fwiw21:09
tdasilvaor keep it with you at all times?21:10
*** Liang__ has quit IRC21:10
rledisezalecuyer: i'll ask our SOC team what they think about that21:10
tdasilvathat's my hope/plan21:10
timburkemoving on21:11
kota_not sure it must be fresh, but fwiw we cannot reach out any cloud service including google thre.21:11
timburke#topic releases21:11
*** openstack changes topic to "releases (Meeting topic: swift)"21:11
kota_w/o roaming21:11
timburkekota_, good to know21:11
timburkethere's a new swiftclient release!21:12
timburkeit'd been a while, and there was an interesting/nasty bug related to SLO that bit a customer of ours21:12
timburkehopefully *just* us ;-)21:12
clayglooks like it!
timburkethat's the one!21:13
timburkeand i merged the authors/changelog patch for swift 2.22.021:13
claygrelease machine!!!21:14
timburkeand requested a release:
patchbotpatch 671350 - releases - swift 2.22.0 release - 1 patch set21:14
mattoliveraunice even21:14
*** e0ne has quit IRC21:15
timburkea lot of great stuff is going into these releases and i want to thank you all for your hard work21:15
timburkewhich leads nicely into updates...21:15
timburke#topic py321:16
*** openstack changes topic to "py3 (Meeting topic: swift)"21:16
timburkewe've got py2 func tests against py3 services in the gate!21:16
timburkei've proposed to get swift on py3 in devstack21:17
patchbotpatch 670353 - devstack - Remove Swift from default DISABLED_PYTHON3_PACKAGES - 1 patch set21:17
mattoliverauawesome work21:17
timburkeand already fixed up vagrant-swift-all-in-one to let you run services on py321:17
claygso py321:18
timburkeonce i had that, i figured we'd get the most bang-for-the-buck with probe tests21:18
timburkeso now we've got
patchbotpatch 671333 - swift - py3: (mostly) port probe tests - 2 patch sets21:19
timburkewhich already found bugs! that kicked out...21:19
patchbotpatch 671167 - swift - py3: fix up listings on sharded containers - 1 patch set21:19
patchbotpatch 670932 - swift - py3: fix up swift-orphans - 1 patch set21:19
patchbotpatch 670933 - swift - py3: fix object-replicator rsync output parsing - 2 patch sets21:19
patchbotpatch 671168 - swift - Fix up errno checking - 1 patch set21:19
timburkeso... release with initial support is great! but there's also more work ahead ;-)21:20
mattoliveraugood to find these now.21:20
alecuyernice finds:)21:20
timburkefunc tests still need to get ported, of course. and we've got a lot of progress there, too21:21
timburkenext up21:21
timburke#topic lots of small files21:21
*** openstack changes topic to "lots of small files (Meeting topic: swift)"21:21
*** links has quit IRC21:22
timburkewe've got a working gate again! and merges from master are happening again (thanks kota_!)21:22
timburkealecuyer, rledisez, kota_ how's it going?21:23
alecuyerthanks kota_ for the merge.21:23
*** irclogbot_2 has joined #openstack-meeting21:23
alecuyerhaven't been able to work on LOSF this week, but I have read the comments you made on the test patch tim, thanks. I will work on that ,21:24
timburkei *almost* got tests passing :P21:24
alecuyerand I will get back to the HTTP patch21:24
alecuyertimburke on SAIO you mean? :)21:25
timburkeon py3. there's just this one tricky guy where OSError and IOError get confused...21:25
alecuyerouch oh yes , we can discuss that after the meeting or on the review, I have to check on that21:26
timburkeis there anything else the rest of us could/should be doing?21:26
alecuyerI saw your comments about the headers (volume header, object header)21:27
alecuyerkota_ also had comments about it a while back (I think kota you wished for a fixed size)21:27
alecuyerso if anyone wants to comment on that and make the headers better, please comment (swift/obj/
patchbotpatch 666378 - swift (feature/losf) - Add tests for - 7 patch sets21:28
kota_hopefully. but it's general comments so if we should make it flexible, it's not strong opinion. I'll check the comment.21:28
alecuyeryes, thanks21:28
timburkeall right21:29
timburke#topic auto-sharding21:29
*** openstack changes topic to "auto-sharding (Meeting topic: swift)"21:29
timburkemattoliverau, how's it going?21:30
mattoliverauI haven't had much of a chance to progress this much, been a busy week. But I did see your patches timburke21:30
mattoliveraulooked at your ring change which some extra data. Looking good. Haven't tested it much though21:31
mattoliverauthe ring service is interesting.21:31
*** tdasilva_ has joined #openstack-meeting21:31
mattoliverauI really need to write a probe test re:shrinking with the new autosharding to make sure it behaves.21:32
mattoliverauWith timburke's rewored ring change, I might remove the patch chain around it21:32
mattoliverauwow, I can't type pre breakfast :P21:33
timburkeoh, right! i'd already started paging this stuff out. the ring-as-a-service thing was just an idea i had since we always seem hesitant to add rings to a daemon that didn't have them before...21:33
*** tdasilva has quit IRC21:34
mattoliveraulet's try that again.. with timburke's reworked ring change I might rebase and rework the patch chain around it. To keep patches more generic21:34
timburkesounds good21:34
mattoliverauthat's all I got as an update.21:35
timburke#topic symlink-backed versioning21:35
*** openstack changes topic to "symlink-backed versioning (Meeting topic: swift)"21:35
*** ociuhandu has joined #openstack-meeting21:35
timburkei mainly added this because clayg said he might have an update for the meeting earlier :-)21:35
claygoh good!21:36
claygplease feel free to look at hardlinks -> p 63309421:36
patchbot - swift - Allow "harder" symlinks - 14 patch sets21:36
*** whoami-rajat has quit IRC21:36
clayghardlinks are really cool - they're symlinks that put a lot of useful info into your container listing for you21:36
claygversioned writes is very close to moving to using these hardlinks to make things operate a lot smoother on the backend -> p 63385721:37
patchbot - swift - WIP: symlink-backed versioned_writes - 3 patch sets21:37
clayginstead of COPYs to move things in and out of the stack - we just need to update some links in the version container21:38
timburkeclayg, you really ought to add yourself as co-author on those ;-)21:38
timburkei definitely like the reduced data movement aspect; i'm super-excited21:39
claygyeah it's super great21:40
timburkeanything else we can do for you other than go review it?21:40
claygright, yeah play with hardlinks - I was toying around with adding something to python-swiftclient `swift link ...`21:41
claygbut i think i set that aside realizing that it was a pretty significant set of work21:41
timburkeyeah -- i remember you trying to bend it to creating a symlink before and not having much luck... we surely *should* add a `link` subcommand...21:42
timburkemaybe that's a thing i could take on... i realized as part of the probe tests getting ported that i need to do some updates to swiftclient to get around
claygbut aside from that yeah just a review on the hardlinks - it's a foundational piece of the versioned_writes update - which is pretty significant21:43
timburkeas long as i'm looking at the client anyway...21:43
claygbut at this point (EoD) it's going to be significantly well tested - so I'm happy with how that's been going21:44
claygok, cool!21:44
claygthanks timburke21:44
timburke#topic open discussion21:44
*** openstack changes topic to "open discussion (Meeting topic: swift)"21:44
timburkeanything else we'd like to bring up today?21:44
*** ociuhandu has quit IRC21:45
*** panda has quit IRC21:46
timburkeall right21:47
timburkethank you all for coming, and thank you for working on swift!21:47
*** openstack changes topic to "OpenStack Meetings ||"21:47
openstackMeeting ended Wed Jul 17 21:47:57 2019 UTC.  Information about MeetBot at . (v 0.1.4)21:47
mattoliverauthanks timburke21:48
openstackMinutes (text):
*** patchbot has left #openstack-meeting21:48
*** ijw has quit IRC21:48
*** panda has joined #openstack-meeting21:48
*** Liang__ has joined #openstack-meeting21:50
*** ociuhandu has joined #openstack-meeting22:00
*** ociuhandu has quit IRC22:06
*** slaweq has quit IRC22:23
*** tesseract has quit IRC22:40
*** TxGirlGeek has quit IRC23:01
*** ociuhandu has joined #openstack-meeting23:02
*** ricolin_ has joined #openstack-meeting23:03
*** ricolin has quit IRC23:06
*** ociuhandu has quit IRC23:06
*** ykatabam has joined #openstack-meeting23:11
*** rcernin has joined #openstack-meeting23:11
*** rcernin has quit IRC23:16
*** rcernin has joined #openstack-meeting23:17
*** diablo_rojo has joined #openstack-meeting23:21
*** jamesmcarthur has joined #openstack-meeting23:23
*** ykatabam has quit IRC23:23
*** tdasilva_ has quit IRC23:25
*** tdasilva_ has joined #openstack-meeting23:25
*** ykatabam has joined #openstack-meeting23:26
*** _hemna has joined #openstack-meeting23:39
*** janders has quit IRC23:41
*** brinzhang_ has quit IRC23:49
*** diablo_rojo has quit IRC23:54
*** carloss has quit IRC23:54
*** artom has joined #openstack-meeting23:56

Generated by 2.15.3 by Marius Gedminas - find it at!