Wednesday, 2018-08-22

*** harlowja has quit IRC00:23
*** hongbin has joined #openstack-meeting-302:22
*** yamahata has quit IRC02:23
*** apetrich has quit IRC02:26
*** edleafe has quit IRC02:46
*** edleafe has joined #openstack-meeting-302:47
*** psachin has joined #openstack-meeting-302:51
*** yamahata has joined #openstack-meeting-303:04
*** jamesmcarthur has joined #openstack-meeting-303:08
*** jamesmcarthur has quit IRC03:13
*** hongbin has quit IRC03:33
*** diablo_rojo has quit IRC03:34
*** sdake has quit IRC05:13
*** sdake has joined #openstack-meeting-305:13
*** sdake has quit IRC05:50
*** Luzi has joined #openstack-meeting-305:51
*** sdake has joined #openstack-meeting-305:51
*** sdake has quit IRC06:02
*** sdake has joined #openstack-meeting-306:04
*** diablo_rojo has joined #openstack-meeting-306:33
*** pcaruana has joined #openstack-meeting-306:41
*** tssurya has joined #openstack-meeting-306:47
*** moguimar has joined #openstack-meeting-307:27
*** moguimar has left #openstack-meeting-307:28
*** alexchadin has joined #openstack-meeting-307:31
*** moguimar has joined #openstack-meeting-307:47
*** moguimar has quit IRC07:48
*** moguimar has joined #openstack-meeting-307:53
*** macza has joined #openstack-meeting-308:01
*** e0ne has joined #openstack-meeting-308:01
*** macza has quit IRC08:05
*** pcaruana has quit IRC08:28
*** pcaruana has joined #openstack-meeting-308:30
*** davidsha has joined #openstack-meeting-308:45
*** diablo_rojo has quit IRC08:48
*** sambetts_ is now known as sambetts09:00
*** jamesmcarthur has joined #openstack-meeting-309:09
*** jamesmcarthur has quit IRC09:13
*** ttx has joined #openstack-meeting-309:17
*** alexchadin has quit IRC09:17
*** alexchadin has joined #openstack-meeting-309:21
*** tobberydberg has joined #openstack-meeting-309:29
*** dougsz_ has joined #openstack-meeting-309:45
*** alexchadin has quit IRC10:13
*** alexchadin has joined #openstack-meeting-310:14
*** alexchadin has quit IRC10:14
*** alexchadin has joined #openstack-meeting-310:15
*** alexchadin has quit IRC10:15
*** alexchadin has joined #openstack-meeting-310:48
*** alexchadin has quit IRC10:53
*** apetrich has joined #openstack-meeting-310:58
*** electrichead has quit IRC10:59
*** alexchadin has joined #openstack-meeting-311:04
*** alexchadin has quit IRC11:19
*** alexchadin has joined #openstack-meeting-311:22
*** moguimar has quit IRC11:32
*** moguimar has joined #openstack-meeting-311:35
*** macza has joined #openstack-meeting-311:38
*** macza has quit IRC11:43
*** raildo has joined #openstack-meeting-311:56
*** rmart04 has joined #openstack-meeting-312:31
*** psachin has quit IRC12:32
*** jamesmcarthur has joined #openstack-meeting-312:50
*** cgayan has joined #openstack-meeting-312:58
*** cgayan has quit IRC13:00
*** cgayan has joined #openstack-meeting-313:00
*** cgayan has quit IRC13:04
*** cgayan has joined #openstack-meeting-313:05
*** mjturek has joined #openstack-meeting-313:14
*** cgayan has quit IRC13:17
*** alexchadin has quit IRC13:59
*** mpiwowarczy has joined #openstack-meeting-314:00
*** Luzi has quit IRC14:07
*** haleyb has joined #openstack-meeting-314:10
*** alexchadin has joined #openstack-meeting-314:10
*** hongbin has joined #openstack-meeting-314:17
*** munimeha1 has joined #openstack-meeting-314:26
*** alexchadin has quit IRC14:33
*** raildo has quit IRC14:40
*** raildo has joined #openstack-meeting-314:42
*** pandy has joined #openstack-meeting-314:47
*** raildo_ has joined #openstack-meeting-314:51
*** jamesmcarthur has quit IRC14:51
*** raildo has quit IRC14:54
*** mmedvede is now known as mmedvede_14:55
*** mmedvede_ is now known as mmedvede14:55
*** jamesmcarthur has joined #openstack-meeting-314:56
*** koji_n has joined #openstack-meeting-314:57
*** moguimar has quit IRC14:58
*** apetrich has quit IRC14:58
*** mpiwowarczy has quit IRC15:00
dougsz_hi all15:00
dougsz_#startmeeting monasca15:00
koji_nhello15:01
openstackMeeting started Wed Aug 22 15:00:59 2018 UTC and is due to finish in 60 minutes.  The chair is dougsz_. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: monasca)"15:01
openstackThe meeting name has been set to 'monasca'15:01
dougsz_hi koji_n15:01
dougsz_#topic volunteer15:01
*** openstack changes topic to "volunteer (Meeting topic: monasca)"15:01
dougsz_So the first topic: I am away next week on holiday, and witek will be back the following week.15:02
dougsz_Any volunteers to run the IRC meeting? :)15:02
koji_n29th?15:03
dougsz_Yes, 29th.15:03
koji_nsorry, but maybe it's difficult for me on that date15:04
dougsz_Not to worry koji_n15:04
koji_nif there is no candidate, i'll touch my colleague15:04
*** tonyb has quit IRC15:04
dougsz_thanks, if we can't find someone we will skip the meeting on the 29th15:04
koji_nok15:05
dougsz_#topic reviews15:05
*** openstack changes topic to "reviews (Meeting topic: monasca)"15:05
pandyHi Dougz15:05
dougsz_pandy: over to you15:05
dougsz_Hi Pandy15:05
pandyyes, i have two patches to review15:05
dougsz_Looks like a couple of doc fixes15:05
dougsz_thanks for submitting those15:05
pandywhere changes were made and need review & merge15:05
*** jamesmcarthur has quit IRC15:06
pandyhttps://review.openstack.org/#/c/591292/15:06
pandyhttps://review.openstack.org/#/c/590667/15:06
dougsz_I have added myself as a reviewer and I will have a look later today.15:07
dougsz_anything more to add on this one pandy?15:07
dougsz_ok, next topic15:09
pandyhey15:09
dougsz_#topic grafana15:09
*** openstack changes topic to "grafana (Meeting topic: monasca)"15:09
pandysorry for late15:09
dougsz_This is yours again pandy?15:09
pandyokay, please review and merge15:09
pandyyes regarding grafana15:09
*** pcaruana has quit IRC15:10
pandyhttps://storyboard.openstack.org/#!/story/200347515:10
pandyhere step to reproduce15:10
*** jamesmcarthur has joined #openstack-meeting-315:10
pandyi am seeing old/different metrics where monasca-agent not running15:10
pandyplease take a look at storyboard https://storyboard.openstack.org/#!/story/200347515:11
pandyits applicable for both monasca & influxdb datasource15:11
pandydougsz_, are you looking into15:11
dougsz_Yeah, it could be a bug.15:12
dougsz_What I would suggest is tailing the output from monasca-grafana when the drop down box is generated15:12
dougsz_You might need to set it to debug mode.15:12
pandymay i know how to do ? in Grafana how to ?15:13
dougsz_I'm not sure how logging is set up in the monasca docker project you are using15:13
dougsz_But i assume it just goes to stdout15:13
dougsz_in which case something like docker logs --follow monasca_grafana --since 1m should work15:14
dougsz_You should be able to see the API calls the datasource plugins make15:14
dougsz_Secondly: What are you using the InfluxDB datasource for?15:15
*** jamesmcarthur has quit IRC15:15
dougsz_You need to query InfluxDB via the Monasca API to get tenant isolation.15:15
dougsz_pandy: does that make sense?15:17
pandyyes15:17
koji_npandy: can i ask you whether you've configured the monitoring-delegate role for the agent user?15:17
pandywhether i should use "monitoring-delegate" or i can any name in place of that15:18
koji_nplease wait little bit...15:18
koji_nhttps://github.com/openstack/monasca-agent/blob/ec31373621c3f10c6d31d71a86bc9336df31bb41/docs/MonascaMetrics.md#cross-tenant-metric-submission15:19
koji_nthis one15:19
pandyyes got it. so i should use only "monitoring-delegate" not any other name like "pandy-delegate" and follow rest steps... ?15:20
pandyalso what are user persmission i should give for "end-user" right now "monasca-user" & "member" is that fine ?15:21
dougsz_pandy: you don't *need* to use it. It depends how you deploy the monasca-agent.15:21
dougsz_but it could be one reason why you have metrics from many projects in your project15:21
pandydidn't get you, can you please explain little more15:21
koji_nyes, the name is configurable15:21
pandykoji_n, okay15:22
pandykoji_n, you mean i can give any name15:22
dougsz_You need to define it in the monasca-api config file15:22
pandydougsz_, you mean delegate_role= pandy-delegate" ?15:23
koji_nhttps://github.com/monasca/monasca-docker/blob/master/monasca-api-python/api-config.conf.j2#L35-L3715:24
koji_nprobably here15:24
koji_nneed to specify your delegate role to DELEGATE_AUTHORIZED_ROLES15:25
dougsz_thanks  koji_n - that's the place15:25
pandyi have created "monasca & monasca-agent" users & "monasca-agent, monasca-user" roles & "monasca" project in this case what should be values for "DELEGATE_AUTHORIZED_ROLES"  "AUTHORIZED_ROLES"15:25
pandy& AGENT_AUTHORIZED_ROLES15:25
pandybased on my user and role creation, what should i give ? do i need admin role anywhere ?15:26
dougsz_pandy: Do you want your monasca agent to post metrics from one project into another? If not you don't need delegate roles.15:26
pandyi dont want to post other projects.. so shall i remove "pandy-delegate" in that case ?15:27
dougsz_You don't need delegate roles then, so yes, you can.15:27
pandy"i have created "monasca & monasca-agent" users & "monasca-agent, monasca-user" roles & "monasca" project in this case what should be values for "DELEGATE_AUTHORIZED_ROLES"  "AUTHORIZED_ROLES"15:27
pandy & AGENT_AUTHORIZED_ROLES15:27
pandy based on my user and role creation, what should i give ? do i need admin role anywhere ?"15:27
pandyjust let me know what values i should based on my user & roles creation, so i can pass in monasca-docker15:28
dougsz_You need to figure them out yourself.15:28
dougsz_It's specific to your configuration.15:28
koji_npandy: so you just want to see the metrics of the instances on the host where agent is running by the project of the agent user?15:29
koji_ni thought you want to use the cross-tenant monitoring15:29
pandykoji_n, yes, i want to see metrics of VM where my agent is running15:29
*** macza has joined #openstack-meeting-315:29
pandyin simple.. client  user name "A" should see Vm metrics of his project "B" only..15:31
dougsz_You don't need delegate roles in that case.15:31
dougsz_Why do you have the InfluxDB datasource plugin installed?15:32
koji_nso, you mean, "HOST-A" has "instance-A" of project A and "instance-B" of project B, and the monasca agent user is running as project A user, in this case, you just want to see only "instance-A" not "instance-B", right?15:32
pandydougsz_, we dont want influxdb as now.  please ignore that in storyboard15:32
dougsz_pandy: The reason I ask is because it doesn't have tenant isolation, so it might be why you are seeing metrics from all projects.15:33
pandykoji_n, yes, but what you mean by "monasca agent" user ? you mean "monasca-agent' role added to A user ?15:33
*** jamesmcarthur has joined #openstack-meeting-315:33
pandyonly influxdb dont have tenant isolation15:34
pandy?15:34
pandyi think based on my created user and role, if i know what i should pass values for " "DELEGATE_AUTHORIZED_ROLES"  "AUTHORIZED_ROLES"15:35
pandy  & AGENT_AUTHORIZED_ROLES " in docker moansc-api file will give solution think so15:35
koji_ni mean the user who you specified when executing monasca-setup command15:35
koji_nhttps://github.com/openstack/monasca-agent/blob/master/docs/Agent.md#explanation-of-primary-monasca-setup-command-line-parameters15:35
pandyi have given "monasca-agent" and "admin" tenant15:36
koji_nok, i got it15:36
koji_nso you want to see only the instances of admin project15:36
pandyactually i am doing mistake with user & roles at "docker-api" & "monasca-setup" ..15:36
koji_nin my idea, libvirt monitoring plugin is not intended to use for that use case15:37
pandykoji_n, no, i have given admin project in monasca-setup, becaus i cant give all projects names ( say if i have 500) ..whether "project" & "user" at monasca-setup will forward only those project logs ?15:38
dougsz_Sorry, I need to go now. Please can we continue this discussion in the monasca channel.15:39
pandyokay15:39
dougsz_thanks everyone15:39
koji_ni cannot close meeting15:39
dougsz_#endmeeting15:39
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:39
openstackMeeting ended Wed Aug 22 15:39:24 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:39
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2018/monasca.2018-08-22-15.00.html15:39
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2018/monasca.2018-08-22-15.00.txt15:39
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2018/monasca.2018-08-22-15.00.log.html15:39
koji_nsorry, i got it15:39
*** dougsz_ has left #openstack-meeting-315:39
*** cgayan has joined #openstack-meeting-315:42
*** koji_n has quit IRC15:43
*** pandy has quit IRC15:46
*** pcaruana has joined #openstack-meeting-315:49
*** tssurya has quit IRC15:53
markvoelker#startmeeting interopwg16:00
openstackMeeting started Wed Aug 22 16:00:34 2018 UTC and is due to finish in 60 minutes.  The chair is markvoelker. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: interopwg)"16:00
openstackThe meeting name has been set to 'interopwg'16:00
markvoelker#chair hogepodge eglute16:00
openstackCurrent chairs: eglute hogepodge markvoelker16:00
markvoelkero/16:00
hogepodgehi!16:00
egluteo/ for as long as my internet permits16:00
markvoelker#link https://etherpad.openstack.org/p/InteropWhistler.17 Today's Agenda16:01
* markvoelker gives folks a moment to look it over and make changes/additions16:01
*** diablo_rojo has joined #openstack-meeting-316:02
markvoelker#topic Build Gate Jobs against Tempest16:02
*** openstack changes topic to "Build Gate Jobs against Tempest (Meeting topic: interopwg)"16:02
markvoelkerOops, skipped the PTG...16:02
markvoelker#topic PTG16:02
*** openstack changes topic to "PTG (Meeting topic: interopwg)"16:02
markvoelkerThere is schedule link and some proposed topics in the etherpad16:03
markvoelkerPRoposed topics looks thin-ish right now...I'll try to flesh that out some this week between aeroplane rides16:03
markvoelker#link https://etherpad.openstack.org/p/InteropRefstackPTGDenver_2018 PTG proposed topics16:03
eglutethank you Mark16:03
markvoelkerAny particular points we need to talk about on PTG stuff right now?16:04
egluteI don't think so... any pressing refstack issues hogepodge?16:04
markvoelkerPossibly worth noting here that https://review.openstack.org/#/c/590179/ has landed so Refstack governance has moved over16:05
markvoelker(Somewhat of a formality, but....)16:05
hogepodgerefstack client now has auto-config capabilities16:05
* markvoelker fumbles for his shades because of the shinyness16:06
hogepodgethanks to the python-tempestconf team for their hard work and patience on that patch16:06
markvoelker++16:06
hogepodgeOne more nova flag needs to be enabled for the configuration to be complete, just have to find the 10 minutes to send the patch up16:06
markvoelkerNeat.  Anything else?16:07
hogepodgesubunit upload work is on hold while I continue my search for a new intern. If any of you know some bright CS students looking for open source work please send the my way.16:08
markvoelkerWill do.  Any particular requirements?  Might be chatting with some folks at NCSU soonish, would be happy to put out some feelers.16:09
hogepodgejust a willingness to do python, javascript, and ruby programming.16:09
hogepodgejob is posted on the jobs board (I have PNW as preferred area, but will accept from wider)16:10
markvoelker10-4.  Was just in the PNW yesterday btw....I hope Portland is less smokey than Seattle was. =)  But I digress...16:10
hogepodgeIt's not 😢16:11
markvoelker#topic Build Gate Job Against Tempest16:11
*** openstack changes topic to "Build Gate Job Against Tempest (Meeting topic: interopwg)"16:11
markvoelkerhogpeodge: the floor is yours again16:11
hogepodgeI wish I could say I've moved this forward.16:11
hogepodgesome of the python-tempestconf folks have talked about working on it16:12
markvoelkerIs this another possible intern project, or is it more of a "someone with a little more background and more than a semester needs to look at it"?16:13
hogepodgeIt's mostly a scripting issue16:13
hogepodgeWe need to parse the json file and pull all the function names out of it, then use code reflection to match them with functions in tempest16:14
hogepodgeand uuids16:14
hogepodgeso on the interop side, the algorithm is at least one alias of all tests needs to be in tempest16:14
hogepodgeall uuids in interop must exist in tempest16:15
hogepodgerun as gate jobs against both projects to guarantee that changes that break interop don't merge without dependent changes to both projects identifying the changes16:16
hogepodgeI'd say that it's more than a day but less than a week of work16:16
*** raildo has joined #openstack-meeting-316:16
markvoelkerGot it.  Ok, thanks.16:16
markvoelker#topic Should we consider an existing tool such as OPNFV yardstick16:17
*** openstack changes topic to "Should we consider an existing tool such as OPNFV yardstick (Meeting topic: interopwg)"16:17
markvoelkerNot sure we quite have the right folks here for this, so it may be something to park until PTG.16:17
markvoelkerIIRC the basic concern is that the Foundation would like tests used to produce a branded certification (something like "OpenStack Powered NFV Solution" or whatever) to be under OpenStack governance, yes?16:18
*** raildo_ has quit IRC16:19
* markvoelker parks it for now16:20
markvoelker#topic Next guideline timing16:20
*** openstack changes topic to "Next guideline timing (Meeting topic: interopwg)"16:20
hogepodgeI'm not sure where the opnfv teams and foundation execs are, but I can bring it up again with them16:20
markvoelkerthanks16:20
markvoelkerWe can do useful things either way I think, but knowing the intended outcome might help us figure out the best avenues for everyone.16:21
markvoelkerAs noted in the pad, no BoD meeting in August and the September one is by phone.  We could shift to November to do an in-person update and approval, as we often do....16:22
markvoelkerThoughts?  I'm pretty agnostic.  The updates don't look like they're going to be particularly complex, so I think we could do either way.16:22
hogepodgeI think November would work just fine for me, but I'm always more optimistic about my availability further out in the future. I'm sure there's a name for that psychological condition16:23
* markvoelker is fine with that too16:23
hogepodgeis eglute still here?16:24
egluteyes, my internet in and out16:24
markvoelkerShe had an electrician coming over today and warned me she might lose power/internet16:24
hogepodgewhat do you think about the timing?16:24
eglutei think november is a good time :)16:24
markvoelkerOk, works for me...shall I submit a patch to next.json to reflect timing?16:25
hogepodge+116:25
markvoelkerNow that this whole process is more mature, it feels like there's less need to adhere to a strict cadence than in the past...might be worth updating the governance docs to clarify target dates at some stage.16:25
markvoelker#action markvoelker submit updated date for next.json16:26
markvoelkerAnyone not here today can voice their opinion on that patch, if they have one. =)16:26
markvoelker#topic Scoring 2018.08^H^H1116:27
*** openstack changes topic to "Scoring 2018.08^H^H11 (Meeting topic: interopwg)"16:27
markvoelker#link https://review.openstack.org/#/c/585772/ Clean up advisory list16:27
markvoelkereglute, I think I missed your comment on this while I was out on the road...I'll have a look at that this afternoon16:28
hogepodgemarkvoelker: yes, is the removal list permanent?16:29
hogepodgeI'm +2/+1 on it with that question answered16:29
markvoelkerHm, I don't think we've kept it permanent in the past, but I'll double check and update the review16:29
markvoelker#action markvoelker check comments on https://review.openstack.org/#/c/585772/ and respond/revise16:30
markvoelkerOther scoring stuff: no major updates from me on Nova/Neutron.  Updates from anyone else?16:31
hogepodgenot here16:31
markvoelkereglute I saw https://review.openstack.org/#/c/585606/ and will sort through it today16:31
*** davidsha has quit IRC16:31
*** tosky has joined #openstack-meeting-316:32
markvoelkerBut it basically looks like no changes16:32
markvoelkerOk, if no major updates on scoring stuff then looks like we need to review https://review.openstack.org/#/c/585606/ and https://review.openstack.org/#/c/565878/16:33
markvoelker#action all please review https://review.openstack.org/#/c/565878/16:33
markvoelker#action all please review https://review.openstack.org/#/c/585606/16:33
markvoelker#topic Open Floor16:33
*** openstack changes topic to "Open Floor (Meeting topic: interopwg)"16:33
markvoelkerAnything else we want to discuss today?16:33
markvoelkerHearing nothing, I think we're done!16:35
markvoelker#endmeeting16:35
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:35
openstackMeeting ended Wed Aug 22 16:35:33 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:35
openstackMinutes:        http://eavesdrop.openstack.org/meetings/interopwg/2018/interopwg.2018-08-22-16.00.html16:35
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/interopwg/2018/interopwg.2018-08-22-16.00.txt16:35
openstackLog:            http://eavesdrop.openstack.org/meetings/interopwg/2018/interopwg.2018-08-22-16.00.log.html16:35
*** macza_ has joined #openstack-meeting-316:42
*** macza has quit IRC16:46
*** jamesmcarthur has quit IRC16:52
*** iyamahat has joined #openstack-meeting-316:57
*** rmart04 has quit IRC17:01
*** e0ne has quit IRC17:07
*** yamahata has quit IRC17:18
*** iyamahat has quit IRC17:18
*** sambetts is now known as sambetts|afk17:23
*** sambetts|afk has quit IRC17:25
*** DinaBelova has quit IRC17:25
*** mmedvede has quit IRC17:25
*** redrobot has quit IRC17:25
*** jlvillal has quit IRC17:25
*** kjansson_ has quit IRC17:25
*** dims has quit IRC17:25
*** Anticimex has quit IRC17:25
*** DinaBelova has joined #openstack-meeting-317:26
*** jlvillal has joined #openstack-meeting-317:27
*** Guest92900 has joined #openstack-meeting-317:34
*** dims_ has joined #openstack-meeting-317:36
*** markvoelker has quit IRC17:39
*** aagate has quit IRC17:50
*** mtreinish has joined #openstack-meeting-317:54
*** mmedvede has joined #openstack-meeting-317:58
*** jamesmcarthur has joined #openstack-meeting-318:07
*** tosky has quit IRC18:47
*** jamesmcarthur has quit IRC18:50
*** mjturek has quit IRC19:11
*** pcaruana has quit IRC19:47
*** e0ne has joined #openstack-meeting-319:57
*** iyamahat has joined #openstack-meeting-320:00
*** iyamahat has quit IRC20:00
*** tonyb has joined #openstack-meeting-320:26
*** jamesmcarthur has joined #openstack-meeting-320:27
*** e0ne has quit IRC20:27
*** mriedem has joined #openstack-meeting-320:30
*** tssurya has joined #openstack-meeting-320:30
*** jamesmcarthur has quit IRC20:33
*** jamesmcarthur has joined #openstack-meeting-320:34
*** tssurya has quit IRC20:35
*** tssurya has joined #openstack-meeting-320:35
*** harlowja has joined #openstack-meeting-320:42
*** raildo has quit IRC20:45
*** jamesmcarthur has quit IRC20:57
dansmith#startmeeting nova_cells21:00
openstackMeeting started Wed Aug 22 21:00:24 2018 UTC and is due to finish in 60 minutes.  The chair is dansmith. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: nova_cells)"21:00
openstackThe meeting name has been set to 'nova_cells'21:00
dansmith#link https://wiki.openstack.org/wiki/Meetings/NovaCellsv221:00
melwitto/21:00
tssuryao/21:00
dansmith#topic bugs21:01
*** openstack changes topic to "bugs (Meeting topic: nova_cells)"21:01
mriedemo.21:01
dansmiththere's a big list of bugs in the agenda, and because I'm a terrible person I haven't looked at them much21:01
dansmithI plan to do that tomorrow morning first thing21:01
dansmithanyone want to highlight any of them specifically? they're fairly well documented so that it's easy to see which are the most important.21:02
mriedemanything i have in there is stale,21:02
mriedemlike the stuff mnaser reported on instance mappings without a build request and no cell set on the mapping21:02
mriedemwe had talked about a transactional write for those21:03
mriedemnothing critical atm21:03
*** jamesmcarthur has joined #openstack-meeting-321:03
dansmithalright.21:04
dansmithanyone else?21:04
dansmiththere's a bug for this cells batching perf thing but I will comment on that in open reviews21:04
dansmithskipping testing21:04
dansmith#topic open reviews21:04
*** openstack changes topic to "open reviews (Meeting topic: nova_cells)"21:04
dansmithmriedem: has one open which I just clicked on21:05
dansmithwhich appears merged, so. okay21:05
mriedem?21:05
mriedemoh21:05
mriedemyeah that21:05
mriedemi have an item for the ptg for that21:05
melwittI still have the multiple cells affinity thing https://review.openstack.org/58507321:06
mriedemi at least got the test :)21:06
mriedemwhich reminds me,21:06
melwittyes, thank you21:06
mriedemthat i think we do some redundant instance group query shit now in setup_instance_group or whatever it's called21:07
mriedemunrelated to that patch, but perftastic21:07
melwittthe second query in there? that keeps confusing me21:07
mriedemever since we stopped storing hosts/members in the group record21:07
*** jamesmcarthur has quit IRC21:08
mriedemno https://review.openstack.org/#/c/540258/13/nova/scheduler/utils.py@79221:08
mriedemi think21:08
mriedemwell, i mean if we already have the group21:08
melwittyeah, that's what I was thinking of21:08
melwittand the subsequent get the hosts again21:08
mriedemyeah i assume that was in there b/c we needed the freshest latest members and hosts in the group21:09
mriedembut dansmith fixed that by not storing the group hosts/members in the db21:09
mriedemthis ^ code predated dan's fix21:09
mriedemand is likely redundant now21:09
mriedemjust one of the many todo threads to pull21:09
dansmithso, open a bug?21:09
mriedem"this might be total bullshit, but i think x is not required now b/c of y"21:10
mriedemsure21:10
dansmithmelwitt: I will try to hit those tomorrow morning as well, remind me if not21:10
melwittok, thanks21:10
dansmithso tssurya has had down-cells patches up for a while and because I'm a terrible person I just circled back to them this morning21:11
dansmithor was that yesterday? I forget21:11
mriedemyesterday21:11
tssuryayesterday21:11
dansmithregardless, I think we worked out a better way to do part of the accounting bit which is cool,21:11
mriedemi've been slowly burning through gmann's dep stuff below it21:11
tssuryayea thanks and thanks21:11
dansmithand I have that on the end of my batching set for her to use,21:11
dansmithsince she's blocked on that other thing anyway21:11
tssuryameanwhile I will write tests for them21:12
dansmithI found an issue in the batching code while writing that for her, so I'm glad I did that at the end anyway21:12
dansmithwhich leads me to my batching stuff to address perf issues the huawei guys have noted21:13
dansmiththey've been reviewing and testing that stuff for me, which is cool21:13
mriedemhave kevin and yikun been talking to you about testing the latest?21:13
mriedemwith like error instances and such?21:13
dansmithI assume we're all aware of that process but if anyone isn't clear on what that is or why/if it's important speak up21:13
dansmithmriedem: not since last night or whatever21:13
dansmithI decided not to do the fault thing (again)21:13
mriedemok but they tested the distributed strategy right?21:14
mriedemah nevermind21:15
dansmithI'm not sure about that, but it will equate to the same thing for them unless they perturb their distribution a little21:15
mriedemchenfujun will be pleased!21:15
dansmithanything else on batching or other open reviews?21:15
dansmith#topic open reviews21:16
*** openstack changes topic to "open reviews (Meeting topic: nova_cells)"21:16
dansmithmriedem has things21:16
mriedemopen discussion?21:16
dansmithsorry21:16
dansmith#undo21:16
openstackRemoving item from minutes: #topic open reviews21:16
dansmith#topic open discussion21:16
*** openstack changes topic to "open discussion (Meeting topic: nova_cells)"21:16
mriedemi'll do the 2nd one first, since its a segue from handling a down cell21:16
mriedemwhen we were talking to the public cloud guy in charge of moving from their cascading / cells v1 type thing last week,21:17
mriedemand talked about handling a down cell,21:17
mriedemhe wanted an option to not return any results when listing if the tenant has any instances in a down cell; this would be before tssurya's new microversion which returns the instnaces in down cells with the UNKNOWN status21:17
mriedemhe was concerned that users would be confused if they knew they had like 3 VMs and then all of a sudden they see 221:18
dansmiththis seems a bit close to config-defined-api-behavior to me21:18
mriedemso he'd rather not show them any, because if they delete the 2 and the 1 comes back, it would be an issue21:18
dansmithseems like going back to 500 would be better than an empty list21:18
mriedemit is, yes, which i pointed out,21:18
mriedembut it's also not really an interop kind of situation21:19
mriedem500 is an option21:19
mriedembut we already fixed that 500 bug...21:19
mriedemso clearly CERN wants it one way and huawei wants it another21:19
dansmithI meant turn on the 500 with a config flag21:19
mriedemoh21:19
dansmithlike explode_if_some_are_down=True21:20
mriedemyeah that's an option21:20
mriedemi can go back and ask which is preferrable21:20
mriedemhide or explode21:20
mriedemin the end,21:20
mriedemit's basically the same from the user viewpoint21:20
tssuryaI had this  https://review.openstack.org/592428/ which was for the empty list config21:20
mriedemalthough of course huawei public cloud has a strict no errors policy... :)21:20
melwittso this would be a change, pre-microversion?21:20
dansmithnot IMHO.. 500 means "the server is broken, I'll try later", empty means "firedrill, my instances and data are gone"21:20
dansmithto me21:20
mriedemmelwitt: yes pre-microversion21:21
melwittok21:21
mriedemif you request the microversion you get the down cell instances with UNKNOWN status21:21
dansmithcan't imagine how returning an empty list doesn't just generate a billion urgent calls to support21:21
mriedemyeah i know21:21
mriedemi'll ask21:21
dansmith500 might mean "hmm, I'll go check the status page" and see that some issues are occurring21:22
melwittyeah, the empty list might give people a heart attack21:22
dansmithif my instances are gone suddenly I freak the eff out21:22
tssuryaI vote for 500 too, makes more sense21:22
tssuryaspecially since the problem is users being confused to see 2 instead of 3.. now they would see 021:22
mriedemyup21:22
mriedemnoted21:22
mriedemmoving onto the other item21:23
mriedemcross-cell cold migration21:23
mriedemi've vomited some random thoughts into https://etherpad.openstack.org/p/nova-ptg-stein-cells21:23
mriedemour requirements are basically, network isolation between cells,21:23
mriedemso no ssh between hosts in different cells so can't cold migrate the traditional way21:23
mriedemimage service is global, which made me think of an orchestrated shelve/unshelve type thing21:23
mriedemi feel like that might be a bit cludgy, so open to other ideas21:24
mriedemi'm not sure how else to get the guest disk image out of the one cell and into the other w/o snapshots21:24
dansmithI think snapshot for migrate will not be what some people want, but I think it will be ideal for a lot of others21:24
dansmithI think that's a good first step for us to do though21:24
mriedemof course, ports and volumes...21:24
mriedemwith ports and volumes we just attach on the new host, migrate, detach from old host on confirm21:25
mriedemso how ports and volumes get migrated is going to be another thing21:25
mriedemwhat else do we have attached to an instance that's external? barbican secrets? castellan certs?21:26
dansmithyep, we'll have to do some thinking probably21:27
mriedemi dislike thinking21:27
mriedemhowever,21:27
mriedemmlavalle and smcginnis work for the same overlords so i can talk to them21:28
mriedemrouted networks comes to mind for ports, but cinder has no concept like this21:28
mriedemas far as i know21:28
melwittsynergy21:28
dansmithare we done with that for the moment?21:29
mriedemyes21:29
mriedemdump ideas/comments in the etherpad21:29
dansmith#todo everyone be thinking about cross-cell-migration gotchas21:30
mriedemalso,21:30
mriedemhuawei cloud is all volume-backed...21:30
mriedemso i have to care about that bigly21:30
dansmithwell, maybe that helps21:30
mriedemmaybe, if the volume storage is shared between cells21:30
dansmithor if it's migratable on the cinder side and we can just wait21:31
mriedemmy guess is that would trigger a swap callback21:31
mriedemthat's what happens if you do volume live migration21:31
mriedemkevin seemed pretty confident this wasn't a hard problem, so maybe i'll just let him own it :)21:32
dansmithanything else before we close?21:32
mriedemnope21:33
dansmith#endmeeting21:34
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"21:34
openstackMeeting ended Wed Aug 22 21:34:00 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:34
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2018/nova_cells.2018-08-22-21.00.html21:34
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2018/nova_cells.2018-08-22-21.00.txt21:34
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2018/nova_cells.2018-08-22-21.00.log.html21:34
*** dansmith is now known as htimsnad21:34
*** mriedem has left #openstack-meeting-321:34
*** tssurya has quit IRC21:38
*** munimeha1 has quit IRC21:41
*** macza_ has quit IRC22:56
*** hongbin has quit IRC23:12
*** jamesmcarthur has joined #openstack-meeting-323:13
*** jamesmcarthur has quit IRC23:35

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