Wednesday, 2018-01-24

*** zhurong has joined #openstack-meeting-300:02
*** zhurong has quit IRC00:20
*** wanghao has quit IRC00:28
*** wanghao has joined #openstack-meeting-300:29
*** kaz has joined #openstack-meeting-300:37
*** MarkBaker has joined #openstack-meeting-300:42
*** chyka has quit IRC00:43
*** wanghao_ has joined #openstack-meeting-300:55
*** wanghao has quit IRC00:55
*** zhurong has joined #openstack-meeting-300:58
*** wanghao has joined #openstack-meeting-301:07
*** wanghao_ has quit IRC01:11
*** shuyingya has joined #openstack-meeting-301:14
*** shuyingy_ has joined #openstack-meeting-301:15
*** salv-orlando has joined #openstack-meeting-301:15
*** shuyingya has quit IRC01:18
*** salv-orlando has quit IRC01:20
*** VW has joined #openstack-meeting-301:21
*** david-lyle has quit IRC01:22
*** dobson has quit IRC01:27
*** dobson has joined #openstack-meeting-301:31
*** MarkBaker has quit IRC01:31
*** rstarmer has quit IRC01:43
*** VW has quit IRC01:56
*** chyka has joined #openstack-meeting-302:07
*** chyka has quit IRC02:08
*** gcb has joined #openstack-meeting-302:09
*** yamamoto has joined #openstack-meeting-302:13
*** hongbin has joined #openstack-meeting-302:16
*** salv-orlando has joined #openstack-meeting-302:17
*** harlowja has quit IRC02:20
*** salv-orlando has quit IRC02:21
*** VW has joined #openstack-meeting-302:32
*** wxy has joined #openstack-meeting-302:33
*** lyan has quit IRC02:47
*** haint93 has joined #openstack-meeting-302:55
*** zhurong has quit IRC02:57
*** haint_ has quit IRC02:58
*** VW has quit IRC03:09
*** VW has joined #openstack-meeting-303:09
*** VW has quit IRC03:13
*** tuanla____ has joined #openstack-meeting-303:14
*** salv-orlando has joined #openstack-meeting-303:17
*** MarkBaker has joined #openstack-meeting-303:20
*** salv-orlando has quit IRC03:22
*** lyan has joined #openstack-meeting-303:31
*** lyan has quit IRC03:31
*** david-lyle has joined #openstack-meeting-303:31
*** david-lyle has quit IRC03:32
*** david-lyle has joined #openstack-meeting-303:33
*** david-lyle has quit IRC03:39
*** MarkBaker has quit IRC03:41
*** lyan has joined #openstack-meeting-303:47
*** psachin` has joined #openstack-meeting-303:52
*** psachin has joined #openstack-meeting-303:52
*** tuanla____ has quit IRC04:00
*** MarkBaker has joined #openstack-meeting-304:01
*** tuanla____ has joined #openstack-meeting-304:01
*** lyan has quit IRC04:12
*** salv-orlando has joined #openstack-meeting-304:18
*** salv-orlando has quit IRC04:22
*** tuanla____ has quit IRC04:33
*** tuanla____ has joined #openstack-meeting-304:34
*** armstrong has quit IRC04:47
*** hongbin has quit IRC04:54
*** MarkBaker has quit IRC05:10
*** salv-orlando has joined #openstack-meeting-305:19
*** harlowja has joined #openstack-meeting-305:19
*** salv-orlando has quit IRC05:23
kazhi05:31
reedip0/05:35
kazreedip: hi05:35
reediphi kaz05:35
kaz#startmeeting taas05:35
openstackMeeting started Wed Jan 24 05:35:31 2018 UTC and is due to finish in 60 minutes.  The chair is kaz. Information about MeetBot at http://wiki.debian.org/MeetBot.05:35
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:35
*** openstack changes topic to " (Meeting topic: taas)"05:35
openstackThe meeting name has been set to 'taas'05:35
reedipI think we can drop an email for the future of TaaS05:35
yamamotohi05:35
reedipas discussed last week05:35
kazdorp?05:36
kazdrop?05:36
kazwhat does 'drop' mean?05:37
*** wanghao_ has joined #openstack-meeting-305:37
reedipsend an email05:37
kazdo you mean we can send an email to OpenStack ML?05:38
*** wanghao has quit IRC05:39
*** salv-orlando has joined #openstack-meeting-305:45
*** chyka has joined #openstack-meeting-305:50
*** pgadiya has joined #openstack-meeting-305:51
yamamotohave any of you heard anything from anil or vinay since then?05:53
kazyamamoto: hi05:53
kazno05:53
*** chyka has quit IRC05:55
*** coolsvap has joined #openstack-meeting-306:04
*** anilvenkata has joined #openstack-meeting-306:09
kazHow can we clarify the procedure for joining Neutron Stadium?06:11
kazdoes anyone have any idea?06:14
yamamotoclarify to who?06:14
kazto us06:15
kazi think we need concrete action items.06:16
*** gcb has quit IRC06:22
yamamotokaz: something like this? https://github.com/openstack/neutron-specs/blob/master/specs/stadium/queens/neutron-vpnaas.rst06:23
yamamotoi guess we should make the project itself working first though.  either wait for anil and vinay coming back, or take it over.06:25
kazyamamoto: yes, we should create and manage like that.06:25
yamamotoi think i know another email of anil. let me try to ping him via it.06:26
kazyamamoto: ok06:26
*** slaweq has joined #openstack-meeting-306:26
*** slaweq has quit IRC06:28
kazIt' time to close IRC meeting.06:29
kaz #endmeeting06:30
yamamotothank you06:30
kaz#endmeeting06:30
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"06:30
openstackMeeting ended Wed Jan 24 06:30:26 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)06:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/taas/2018/taas.2018-01-24-05.35.html06:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/taas/2018/taas.2018-01-24-05.35.txt06:30
openstackLog:            http://eavesdrop.openstack.org/meetings/taas/2018/taas.2018-01-24-05.35.log.html06:30
kazthank you, bye.06:30
*** kaz has quit IRC06:30
*** marios has joined #openstack-meeting-306:37
*** witek has quit IRC06:37
*** witek has joined #openstack-meeting-306:42
*** slaweq has joined #openstack-meeting-306:44
*** slaweq has quit IRC06:49
*** makowals has joined #openstack-meeting-306:53
*** slaweq has joined #openstack-meeting-307:03
*** sgrasley1 has quit IRC07:06
*** pcaruana has joined #openstack-meeting-307:10
*** slaweq has quit IRC07:14
*** pcaruana has quit IRC07:21
*** pcaruana has joined #openstack-meeting-307:22
*** markvoelker has quit IRC07:25
*** markvoelker has joined #openstack-meeting-307:27
*** e0ne has joined #openstack-meeting-307:30
*** markvoelker has quit IRC07:32
*** stendulker has joined #openstack-meeting-307:36
*** chyka has joined #openstack-meeting-307:39
*** slaweq has joined #openstack-meeting-307:40
*** chyka has quit IRC07:44
*** slaweq has quit IRC07:45
*** gauravsitlani has joined #openstack-meeting-307:46
*** anilvenkata has quit IRC07:49
*** apetrich has quit IRC07:52
*** e0ne has quit IRC08:01
*** pcaruana has quit IRC08:01
*** e0ne has joined #openstack-meeting-308:01
*** apetrich has joined #openstack-meeting-308:05
*** alexchadin has joined #openstack-meeting-308:10
*** lpetrut has joined #openstack-meeting-308:25
*** alexchadin has quit IRC08:28
*** alexchadin has joined #openstack-meeting-308:29
*** cshastri has joined #openstack-meeting-308:30
*** lpetrut has quit IRC08:32
*** alexchadin has quit IRC08:36
*** alexchadin has joined #openstack-meeting-308:36
*** lpetrut has joined #openstack-meeting-308:38
*** pcaruana has joined #openstack-meeting-308:39
*** alexchad_ has joined #openstack-meeting-308:40
*** alexchadin has quit IRC08:42
*** rossella_s has quit IRC08:44
*** gauravsitlani has quit IRC08:46
*** gauravsitlani has joined #openstack-meeting-308:46
*** yamamoto has quit IRC08:53
*** rossella_s has joined #openstack-meeting-308:55
*** egallen has joined #openstack-meeting-308:57
*** rossella_s has quit IRC09:05
*** gauravsitlani has quit IRC09:07
*** harlowja has quit IRC09:07
*** rossella_s has joined #openstack-meeting-309:07
*** freerunner has quit IRC09:08
*** lpetrut_ has joined #openstack-meeting-309:08
*** yamahata has quit IRC09:10
*** yamamoto has joined #openstack-meeting-309:10
*** lpetrut has quit IRC09:10
*** freerunner has joined #openstack-meeting-309:14
*** alexchad_ is now known as alexchadin09:15
*** rossella_s has quit IRC09:19
*** rossella_s has joined #openstack-meeting-309:20
*** anilvenkata has joined #openstack-meeting-309:21
*** psachin` has quit IRC09:24
*** lpetrut_ has quit IRC09:25
*** psachin has quit IRC09:25
*** markvoelker has joined #openstack-meeting-309:28
*** wanghao_ has quit IRC09:30
*** wanghao has joined #openstack-meeting-309:30
*** wanghao has quit IRC09:31
*** wanghao has joined #openstack-meeting-309:31
*** wanghao has quit IRC09:31
*** wanghao has joined #openstack-meeting-309:32
*** wanghao has quit IRC09:32
*** wanghao has joined #openstack-meeting-309:33
*** psachin has joined #openstack-meeting-309:33
*** wanghao has quit IRC09:33
*** wanghao has joined #openstack-meeting-309:33
*** wanghao has quit IRC09:34
*** wanghao has joined #openstack-meeting-309:34
*** wanghao has quit IRC09:35
*** wanghao has joined #openstack-meeting-309:35
*** wanghao has quit IRC09:35
*** wanghao has joined #openstack-meeting-309:36
*** wanghao has quit IRC09:36
*** wanghao has joined #openstack-meeting-309:36
*** wanghao has quit IRC09:37
*** wanghao has joined #openstack-meeting-309:37
*** wanghao has quit IRC09:38
*** wanghao has joined #openstack-meeting-309:38
*** absubram has joined #openstack-meeting-309:50
*** gauravsitlani has joined #openstack-meeting-309:50
*** absubram has quit IRC09:54
*** absubram has joined #openstack-meeting-309:56
*** tuanla____ has quit IRC09:58
*** yamamoto has quit IRC09:59
*** markvoelker has quit IRC10:02
*** numans has quit IRC10:09
*** rossella_s has quit IRC10:09
*** numans has joined #openstack-meeting-310:10
*** rossella_s has joined #openstack-meeting-310:14
*** yamamoto has joined #openstack-meeting-310:16
*** sambetts|afk is now known as sambetts10:20
*** pgadiya has quit IRC10:22
*** pgadiya has joined #openstack-meeting-310:23
*** pbourke has quit IRC10:35
*** pbourke has joined #openstack-meeting-310:37
*** rossella_s has quit IRC10:39
*** rossella_s has joined #openstack-meeting-310:42
*** rossella_s has quit IRC10:51
*** rossella_s has joined #openstack-meeting-310:54
*** alexchadin has quit IRC10:56
*** markvoelker has joined #openstack-meeting-310:58
*** rossella_s has quit IRC10:59
*** rossella_s has joined #openstack-meeting-310:59
*** alexchadin has joined #openstack-meeting-310:59
*** donghao has joined #openstack-meeting-311:01
*** anilvenkata has quit IRC11:10
*** absubram has quit IRC11:11
*** chyka has joined #openstack-meeting-311:15
*** rossella_s has quit IRC11:18
*** psachin has quit IRC11:19
*** rossella_s has joined #openstack-meeting-311:20
*** chyka has quit IRC11:20
*** markvoelker has quit IRC11:32
*** gauravsitlani_ has joined #openstack-meeting-311:45
*** stendulker has quit IRC11:45
*** gauravsitlani has quit IRC11:47
*** gauravsitlani_ has quit IRC12:02
*** pgadiya has quit IRC12:02
*** zhurong has joined #openstack-meeting-312:10
*** julim has joined #openstack-meeting-312:13
*** pgadiya has joined #openstack-meeting-312:14
*** pgadiya_ has joined #openstack-meeting-312:19
*** pgadiya has quit IRC12:23
*** slaweq has joined #openstack-meeting-312:24
*** raildo has joined #openstack-meeting-312:27
*** slaweq has quit IRC12:29
*** lpetrut_ has joined #openstack-meeting-312:29
*** markvoelker has joined #openstack-meeting-312:29
*** fouadben has joined #openstack-meeting-312:59
*** bloatyfloat has quit IRC13:01
*** markvoelker has quit IRC13:03
*** lpetrut_ has quit IRC13:05
*** lpetrut_ has joined #openstack-meeting-313:06
*** lpetrut_ has quit IRC13:07
*** lpetrut_ has joined #openstack-meeting-313:08
*** chyka has joined #openstack-meeting-313:08
*** lpetrut_ has quit IRC13:09
*** lpetrut_ has joined #openstack-meeting-313:10
*** lpetrut_ has quit IRC13:11
*** lpetrut_ has joined #openstack-meeting-313:11
*** chyka has quit IRC13:13
*** pgadiya_ has quit IRC13:25
*** lpetrut_ has quit IRC13:30
*** alexchadin has quit IRC13:31
*** lhx_ has joined #openstack-meeting-313:33
*** makowals has quit IRC13:34
*** makowals has joined #openstack-meeting-313:35
*** egallen_ has joined #openstack-meeting-313:36
*** egallen has quit IRC13:37
*** egallen_ is now known as egallen13:37
*** alexchadin has joined #openstack-meeting-313:40
*** alexchadin has quit IRC13:41
*** makowals has quit IRC13:43
*** makowals has joined #openstack-meeting-313:44
*** shuyingy_ has quit IRC13:46
*** donghao has quit IRC13:48
*** yamamoto has quit IRC13:53
*** bloatyfloat has joined #openstack-meeting-313:53
*** VW has joined #openstack-meeting-313:55
*** VW has quit IRC13:55
*** tenobreg has joined #openstack-meeting-313:56
*** VW has joined #openstack-meeting-313:56
*** alexchadin has joined #openstack-meeting-313:57
*** lpetrut_ has joined #openstack-meeting-313:59
*** markvoelker has joined #openstack-meeting-314:00
*** hidekazu has joined #openstack-meeting-314:00
alexchadin#startmeeting watcher14:00
openstackMeeting started Wed Jan 24 14:00:49 2018 UTC and is due to finish in 60 minutes.  The chair is alexchadin. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: watcher)"14:00
openstackThe meeting name has been set to 'watcher'14:00
alexchadinhi14:01
hidekazuhi14:01
alexchadinAgenda for today: https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#01.2F24.2F201814:01
alexchadinhidekazu: let's wait 5 minutes for other people?14:01
hidekazualexchadin: yes14:02
*** coolsvap has quit IRC14:02
alexchadinhidekazu: I hope we close most of Queens blueprints :)14:03
hidekazualexchadin: we may need to have meeting at more asian european friendly time.14:03
alexchadinhidekazu: I agree14:03
hidekazualexchadin: lets add it to ptg agenda.14:04
alexchadinhidekazu: done14:04
hidekazualexchadin: thanks.14:04
alexchadinhidekazu: I've added it to "What should be improved" section14:05
hidekazualexchadin: i confirmed.14:06
alexchadinwell, 5 minutes passed, let's move on14:06
alexchadin#topic Announcements14:06
*** openstack changes topic to "Announcements (Meeting topic: watcher)"14:06
alexchadinWe're going to release queens-3 today.14:06
*** krtaylor has quit IRC14:07
alexchadinonce zone migration, storage spec and strategy requirements are merged, I will create release14:08
alexchadinCall for Presentations is opened, deadline is February 8th14:08
*** krtaylor has joined #openstack-meeting-314:08
alexchadinhidekazu: do you have any ideas about presentations?14:10
*** yamamoto has joined #openstack-meeting-314:10
hidekazualexchadin: unfortunately no.14:10
*** armstrong has joined #openstack-meeting-314:11
*** adisky__ has joined #openstack-meeting-314:11
hidekazualexchadin: do you have project update session?14:11
adisky__hi14:11
alexchadinadisky__: hi14:11
adisky__sorry for joining late14:11
hidekazuadisky__: hi14:11
hidekazuadisky__: i heard it snowed even in india.14:12
alexchadinhidekazu: I haven't applied for PU yet14:12
adisky__hidekazu: yes it snows in india as well but at highert altitudes :)14:12
hidekazualexchadin: i see14:12
alexchadinhidekazu: I'm not sure if I go to Vancouver14:13
hidekazualexchadin: i can not go summit without having session.14:13
adisky__alexchadin: hidekazu : we should have a project update session as two new strategies will be there in queens14:14
alexchadinhidekazu: I will apply for PU :)14:14
*** lyan has joined #openstack-meeting-314:14
*** yamahata has joined #openstack-meeting-314:15
hidekazualexchadin: nice14:15
alexchadinadisky__: will you go to PTG?14:15
adisky__alexchadin: i will try my best, but our company does not make things clear so early :)14:16
alexchadinadisky__: ah, then let me know if you get confirmation14:17
adisky__alexchadin: sure14:17
*** egallen has quit IRC14:17
*** zhurong has quit IRC14:18
alexchadinPTL nominations starts on 29th January.14:18
alexchadin#link https://governance.openstack.org/election/14:18
alexchadinI'll apply my candidacy14:19
alexchadinsince this project takes 80% of my work time14:19
adisky__alexchadin: +114:20
hidekazualexchadin: 80% nice14:20
*** amofakhar_ has joined #openstack-meeting-314:20
*** egallen has joined #openstack-meeting-314:20
alexchadinWe need to work on adding PTG topics here. #link https://etherpad.openstack.org/p/rocky-watcher-ptg14:21
*** egallen has quit IRC14:21
*** shuyingya has joined #openstack-meeting-314:22
alexchadinhidekazu: thank you for your contribution to the topics14:22
hidekazualexchadin: we need discussion.14:22
alexchadinI continue to filling them up14:22
alexchadinhidekazu: I agree14:22
*** egallen has joined #openstack-meeting-314:23
alexchadinadisky__: I would be happy if you add something you want to share with us :)14:24
*** yamahata has quit IRC14:24
adisky__alexchadin: i will add the scaling up things, that we were discussing14:24
alexchadinadisky__: any feedback is welcome14:24
alexchadinadisky__: +114:25
adisky__alexchadin: and i was thinking should we increase watcher optimizations to containers also??14:25
alexchadinI will complete list of blueprints to discuss each of them on PTG14:25
alexchadinadisky__: ah, that's old question :)14:25
adisky__alexchadin: yea, but i dont know the answer14:26
hidekazuhaha14:26
alexchadinadisky__: hidekazu: can we migrate containers in live or cold mode at least14:26
hidekazuadisky__: you can add it to ptg agenda.14:26
alexchadin?14:26
*** markvoelker has quit IRC14:27
*** markvoelker has joined #openstack-meeting-314:27
adisky__alexchadin: i dont think a direct approach is available14:27
hidekazualexchadin: adisky__: kubernetes is container orchestration standard.14:27
hidekazukubernetes has self-healing.14:27
*** egallen has quit IRC14:28
adisky__hidekazu: yes, but i think kubernetes do not migrate containers, its spawns up new one with the image14:28
hidekazuadisky__: i do not know container can migrate.14:29
adisky__and there are projects like zun, which do not use kubernetes can levarage watcher to do optimization14:29
adisky__hidekazu: same here14:29
*** zhipeng has joined #openstack-meeting-314:29
*** aagate has joined #openstack-meeting-314:30
alexchadinI propose for us to get more knowledge about self-healing in containers and discuss it on PTG14:30
hidekazuadisky__: kill and spawn new container is only way. personally i do not believe zun becomes used widely.14:30
adisky__alexchadin: +114:30
hidekazualexchadin: ok14:30
alexchadinwe should be prepared to get valuable results of PTG14:31
*** sgrasley1 has joined #openstack-meeting-314:31
adisky__alexchadin: hidekazu: i think we should also think about some particular strategies that focus on NFV and Edge computing, so that watcher used by more companies in production14:31
alexchadinadisky__: you want to use neutron somehow in Watcher?14:32
hidekazuadisky__: you read last discussion topic??14:32
adisky__hidekazu: no.14:32
alexchadinadisky__: hidekazu has already written about NFV in Agenda :)14:33
adisky__alexchadin: At this point i don't know, need to research!14:33
adisky__alexchadin: yea, i see14:33
*** makowals has quit IRC14:33
alexchadinadisky__: I've got requests from my colleagues and manager, I'll add them too14:34
alexchadinReview Action Items14:35
alexchadinWatcher14:35
alexchadinStrategy requirements needs final core review14:35
alexchadin#link https://review.openstack.org/#/c/522538/14:35
adisky__alexchadin: if you are not travelling to summit and have any ideas related to watcher, please suggest them as watcher will gain more popularity if no. of sessions is high.14:35
alexchadinadisky__: sure14:36
*** egallen has joined #openstack-meeting-314:36
*** makowals has joined #openstack-meeting-314:36
alexchadinadisky__: after PTG we will announce main tasks for Rocky cycle14:36
adisky__alexchadin:+114:37
alexchadinhidekazu: I've missed you w+114:37
alexchadinhidekazu: thanks!14:37
alexchadinAdd baremetal strategy validation needs reviews #link https://review.openstack.org/#/c/537356/14:37
alexchadinadisky__: could you please review it?14:38
adisky__alexchadin: +114:39
*** amofakhar_ has quit IRC14:39
*** qwebirc11274 has joined #openstack-meeting-314:39
*** qwebirc11274 has quit IRC14:40
*** __pele__ has joined #openstack-meeting-314:40
alexchadinadisky__: we need to merge it ASAP14:40
adisky__alexchadin: today itself??14:40
alexchadinAdd zone migration strategy is going to be merged14:41
*** egallen has quit IRC14:41
*** cleong has joined #openstack-meeting-314:42
alexchadinadisky__: I would like to make release today14:42
hidekazualexchadin: zone migration will have merge conflict with strategy requirement.14:43
adisky__alexchadin: i did +214:43
alexchadinhidekazu: why?14:43
hidekazualexchadin: both updates strategy base14:44
hidekazualexchadin: ah, but not same line.14:45
alexchadinhidekazu: there is no intersections14:45
hidekazualexchadin: yeah, i misunderstood.14:45
alexchadinWatcher CLI14:46
alexchadinAdd strategy state command needs reviews #link https://review.openstack.org/#/c/523422/14:46
alexchadinit should be merged as well14:46
hidekazu8 weeks ago!14:46
alexchadinhidekazu: perfect things shouldn't be updated :P14:47
alexchadinI will update blueprints and releasenotes by end of this week14:47
*** egallen has joined #openstack-meeting-314:49
alexchadinI think that's enough for today14:49
adisky__alexchadin: i reviewed, at one go it looks fine :)14:49
hidekazualexchadin: one nit14:50
alexchadinhidekazu: check out]14:51
hidekazubye14:51
adisky__bye14:52
alexchadinbye14:53
alexchadin#endmeeting14:53
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:53
openstackMeeting ended Wed Jan 24 14:53:51 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/watcher/2018/watcher.2018-01-24-14.00.html14:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/watcher/2018/watcher.2018-01-24-14.00.txt14:53
openstackLog:            http://eavesdrop.openstack.org/meetings/watcher/2018/watcher.2018-01-24-14.00.log.html14:53
*** markvoelker has quit IRC14:55
*** bobh has joined #openstack-meeting-314:55
*** amofakhar has joined #openstack-meeting-314:58
*** hidekazu has left #openstack-meeting-314:58
*** amofakhar has quit IRC14:58
*** haruki has joined #openstack-meeting-314:58
*** markvoelker has joined #openstack-meeting-314:59
*** sc has joined #openstack-meeting-314:59
*** tenobreg has quit IRC14:59
*** amofakhar has joined #openstack-meeting-314:59
witek#startmeeting monasca15:00
openstackMeeting started Wed Jan 24 15:00:23 2018 UTC and is due to finish in 60 minutes.  The chair is witek. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: monasca)"15:00
openstackThe meeting name has been set to 'monasca'15:00
witekHello everyone15:00
fouadbenHi all,15:00
amofakharHello15:00
schi there15:00
harukihello15:01
witekAgenda as usual here https://etherpad.openstack.org/p/monasca-team-meeting-agenda15:01
*** joadavis_m has joined #openstack-meeting-315:01
*** mjturek has joined #openstack-meeting-315:01
witek#topic deadlines15:01
*** openstack changes topic to "deadlines (Meeting topic: monasca)"15:02
witektomorrow is the queens-milestone-315:02
witekI have already released python-monascaclient15:02
witekand cut the stable/queens branch15:02
witekfor this repo15:02
witeki will also tag the other repositories in the next days15:03
witekalthough we're not bound by the official feature freeze15:04
witekit's a good idea not to include bigger changes at that point15:04
witekand wait until stable branches for all repos are cut15:04
*** jgu_ has joined #openstack-meeting-315:04
scOK15:04
joadavis_mSounds good15:05
amofakhargood15:05
*** cbellucci has joined #openstack-meeting-315:05
witekif some change should come in anyway, please communicate at irc or mailing list15:06
scthe mailing list it's almost dead15:07
witekbut it works :)15:07
*** slaweq has joined #openstack-meeting-315:07
witekopenstack-dev list15:08
scok, I was thinking monasca mailing list15:08
scsorry15:08
witeklaunchpad list will be deactivated next week, as agreed last time15:08
witekfrom other dates, Call for Presentations for Vancouver is open15:09
witekuntil Feb 815:09
scwitek: do you like to propose the workshop again?15:10
witeknot sure15:11
witekI thought about heat auto-scaling with Monasca, but haven't played that through15:11
witekas workshop session15:12
cbellucciauto-scaling would be a great use case for the workshop15:12
scI used it in the past with not that much success with helion, may be with other distros or no distro i.e. devstack15:13
scit's hard to find the track where to place monasca, take a look at: https://www.openstack.org/summit/vancouver-2018/summit-categories15:14
witekyou're right, workshops are not listed here, I guess15:16
scyes, generally speaking it looks more a user oriented summit15:17
cbellucciworkshop should be available in the form to submit a presentation15:17
*** e0ne has quit IRC15:18
*** e0ne has joined #openstack-meeting-315:19
*** alexchadin has quit IRC15:19
witekok, sleep over it, and if you have some ideas how we can promote Monasca and would like to share it, let's come back to that next week15:19
witek#topic bug triage15:19
*** openstack changes topic to "bug triage (Meeting topic: monasca)"15:19
scgrand15:19
witekwe have one new bug without assignee15:20
witekhttps://storyboard.openstack.org/#!/story/200148515:20
witekit's about InfluxDB version detection in API15:20
*** e0ne has quit IRC15:20
witekas Kevan noticed, we don't need `SHOW DIAGNOSTICS` for that, so we can improve the code15:21
witekalso, the version is checked now at the start of API15:22
witekand InfluxDB could be not available at that point15:22
witekany volunteers?15:23
witekif not, anyone can pick it up in spare time15:24
witekjust assign the task to yourself15:24
witek#topic tempest-tests-plugin15:25
*** openstack changes topic to "tempest-tests-plugin (Meeting topic: monasca)"15:25
witekchandankumar is ready with his changes15:25
witekon splitting the tempest tests15:25
witekhttps://review.openstack.org/#/q/projects:openstack/monasca++topic:goal-split-tempest-plugins+status:open15:26
witekgreat thanks for that15:26
witekdocumentation for running the tests locally is also added15:26
witekhttps://review.openstack.org/#/c/530454/12/devstack/README.rst15:26
*** slaweq has quit IRC15:26
witekit will also affect monasca-docker repo, as the tests are being removed from monasca-api and monasca-log-api15:27
scI'll test in devstack ASAP15:28
witeknice15:28
witek#topic ptg15:29
*** openstack changes topic to "ptg (Meeting topic: monasca)"15:29
witeksomeone has asked about the schedule last week15:29
witekthe proposed track layout is here:15:29
witekhttp://lists.openstack.org/pipermail/openstack-dev/2018-January/126335.html15:29
witekhttps://docs.google.com/spreadsheets/d/e/2PACX-1vRmqAAQZA1rIzlNJpVp-X60-z6jMn_95BKWtf0csGT9LkDharY-mppI25KjiuRasmK413MxXcoSU7ki/pubhtml?gid=1374855307&single=true15:29
scI  got my ticket today15:30
witekas planned, Monasca sessions will be on Wednesday-Thursday15:30
joadavis_mAwesome. I'd missed seeing that come through15:30
joadavis_mI've booked travel so I'll be there Mon through Thurs (same as jgu)15:30
witekgreat15:31
witekwe'll have full room :)15:31
scI have to find out if getting up and down from Galway is an option or it's better to book a hotel15:32
witekalso, I want to set up remote call for people not being able to travel15:32
witekthere is special rate in the conference hotel15:32
*** Guest28399 is now known as mgagne15:33
*** mgagne has joined #openstack-meeting-315:33
amofakharI and one of my colleagues will join you there too15:33
witekgreat15:34
witekplease add your names to the etherpad15:34
witekhttps://etherpad.openstack.org/p/monasca-ptg-rocky15:34
amofakharok15:34
*** hongbin has joined #openstack-meeting-315:34
witekalso, we'll have to start working on preparing the agenda15:35
witeksome items are already there15:35
witekI don't have any more topics for today15:36
witekif you have some, please go ahead15:36
witekif not, I'll be winding up15:38
witekthank you everyone15:38
witekbye, bye15:38
amofakharThank you15:38
amofakharbye every one15:38
harukithank you, bye15:39
joadavis_mBye15:39
witek#endmeeting15:39
cbelluccibye15:39
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:39
openstackMeeting ended Wed Jan 24 15:39:16 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-01-24-15.00.html15:39
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2018/monasca.2018-01-24-15.00.txt15:39
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2018/monasca.2018-01-24-15.00.log.html15:39
*** cbellucci has quit IRC15:39
*** rbrndt has joined #openstack-meeting-315:43
*** rbrndt has quit IRC15:43
*** haruki has quit IRC15:43
*** sgrasley1 has quit IRC15:43
*** __pele__ has quit IRC15:45
*** AndChat445556 has joined #openstack-meeting-315:46
*** amofakhar has quit IRC15:46
*** jgu_ has quit IRC15:47
*** aagate has quit IRC15:48
*** bobh has quit IRC15:50
*** egallen has quit IRC15:50
*** AndChat|445556 has joined #openstack-meeting-315:50
*** david-lyle has joined #openstack-meeting-315:50
*** egallen has joined #openstack-meeting-315:50
*** bobh has joined #openstack-meeting-315:50
*** e0ne has joined #openstack-meeting-315:52
*** AndChat445556 has quit IRC15:53
*** sgrasley1 has joined #openstack-meeting-315:54
*** shuyingya has quit IRC15:58
*** joadavis_m has quit IRC16:05
*** marios has quit IRC16:05
*** marios has joined #openstack-meeting-316:05
*** mjturek has quit IRC16:07
*** VW_ has joined #openstack-meeting-316:08
*** rossella_s has quit IRC16:09
*** rossella_s has joined #openstack-meeting-316:11
*** sc has left #openstack-meeting-316:11
*** VW__ has joined #openstack-meeting-316:12
*** VW has quit IRC16:12
*** VW_ has quit IRC16:13
*** lpetrut_ has quit IRC16:17
*** mjturek has joined #openstack-meeting-316:17
*** gauravsitlani_ has joined #openstack-meeting-316:17
*** tellesnobrega has joined #openstack-meeting-316:26
*** bobh has quit IRC16:33
*** pcaruana has quit IRC16:35
*** zhipeng has quit IRC16:39
*** e0ne has quit IRC16:40
*** slaweq has joined #openstack-meeting-316:40
*** e0ne has joined #openstack-meeting-316:40
*** AndChat445556 has joined #openstack-meeting-316:41
*** AndChat|445556 has quit IRC16:44
*** slaweq has quit IRC16:48
*** yamamoto has quit IRC16:49
*** rossella_s has quit IRC16:59
*** rossella_s has joined #openstack-meeting-317:01
*** bobh has joined #openstack-meeting-317:01
*** yamamoto has joined #openstack-meeting-317:05
*** yamamoto has quit IRC17:07
*** yamamoto has joined #openstack-meeting-317:07
*** yamamoto has quit IRC17:07
*** chyka has joined #openstack-meeting-317:09
*** AndChat|445556 has joined #openstack-meeting-317:10
*** VW__ has quit IRC17:12
*** VW has joined #openstack-meeting-317:12
*** AndChat445556 has quit IRC17:13
*** VW has quit IRC17:14
*** VW has joined #openstack-meeting-317:14
*** VW has quit IRC17:16
*** VW has joined #openstack-meeting-317:16
*** VW has quit IRC17:16
*** VW has joined #openstack-meeting-317:17
*** slaweq has joined #openstack-meeting-317:24
*** lhx_ has quit IRC17:30
*** slaweq has quit IRC17:33
*** cshastri has quit IRC17:41
*** slaweq has joined #openstack-meeting-317:43
*** AndChat|445556 has quit IRC17:46
*** slaweq has quit IRC17:49
*** lkoranda has quit IRC17:51
*** mjturek has quit IRC17:52
*** mjturek has joined #openstack-meeting-317:52
*** slaweq has joined #openstack-meeting-317:54
*** sgrasley1 has quit IRC17:56
*** lkoranda has joined #openstack-meeting-317:57
*** slaweq has quit IRC17:58
*** sgrasley1 has joined #openstack-meeting-317:58
*** david-lyle has quit IRC18:04
*** yamamoto has joined #openstack-meeting-318:07
*** sambetts is now known as sambetts|afk18:08
*** armstrong has quit IRC18:10
*** sgrasley1 has quit IRC18:15
*** sgrasley1 has joined #openstack-meeting-318:15
*** rstarmer has joined #openstack-meeting-318:17
*** yamamoto has quit IRC18:18
*** gauravsitlani__ has joined #openstack-meeting-318:25
*** sgrasley1 has quit IRC18:27
*** sgrasley1 has joined #openstack-meeting-318:27
*** gauravsitlani_ has quit IRC18:27
*** e0ne has quit IRC18:28
*** tellesnobrega has quit IRC18:28
*** gauravsitlani__ has quit IRC18:33
*** tssurya_ has joined #openstack-meeting-318:40
*** tssurya_ has quit IRC18:41
*** tssurya_ has joined #openstack-meeting-318:49
*** rstarmer has quit IRC18:49
*** mjturek has quit IRC18:52
*** sgrasley1 has quit IRC18:52
*** marios has quit IRC18:52
*** sgrasley1 has joined #openstack-meeting-318:52
*** MarkBaker has joined #openstack-meeting-318:52
*** mjturek has joined #openstack-meeting-318:53
*** sgrasley1 has quit IRC18:55
*** sgrasley1 has joined #openstack-meeting-318:55
*** tssurya_ has quit IRC19:02
*** vladiskuz has joined #openstack-meeting-319:06
*** tssurya_ has joined #openstack-meeting-319:06
*** adisky__ has quit IRC19:07
*** VW_ has joined #openstack-meeting-319:11
*** VW_ has quit IRC19:12
*** VW_ has joined #openstack-meeting-319:12
*** vladiskuz has quit IRC19:13
*** VW has quit IRC19:15
*** david-lyle has joined #openstack-meeting-319:17
*** sgrasley1 has quit IRC19:23
*** sgrasley1 has joined #openstack-meeting-319:24
*** pcaruana has joined #openstack-meeting-319:27
*** pcaruana has quit IRC19:27
*** e0ne has joined #openstack-meeting-319:28
*** sgrasley1 has quit IRC19:29
*** muttley has joined #openstack-meeting-319:32
*** e0ne_ has joined #openstack-meeting-319:35
*** e0ne has quit IRC19:38
*** harlowja has joined #openstack-meeting-319:38
*** yamahata has joined #openstack-meeting-319:38
*** MarkBaker has quit IRC19:42
*** slaweq has joined #openstack-meeting-319:45
*** muttley has quit IRC19:48
*** tssurya_ has quit IRC19:49
*** tssurya_ has joined #openstack-meeting-319:51
*** slaweq has quit IRC19:52
*** VW_ has quit IRC19:57
*** VW has joined #openstack-meeting-319:58
ying_zuo#startmeeting horizon20:00
openstackMeeting started Wed Jan 24 20:00:09 2018 UTC and is due to finish in 60 minutes.  The chair is ying_zuo. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: horizon)"20:00
openstackThe meeting name has been set to 'horizon'20:00
ying_zuoHi everyone o/20:00
e0ne_hi20:00
betherlyo/20:00
ying_zuo#topic Queens-3 milestone release20:00
*** openstack changes topic to "Queens-3 milestone release (Meeting topic: horizon)"20:00
ying_zuoI am going to cut the release tonight20:01
ying_zuoare there any last minute urgent patches need to get in before I do so?20:01
e0ne_does it mean that we'll face feature freeze right after it?20:01
ying_zuoyes20:01
ying_zuono feature related patches will be merged after that20:02
e0ne_ok, just wanted to confirm because there is nothing about it at https://releases.openstack.org/queens/schedule.html20:02
ying_zuountil RC-2 is cut20:02
e0ne_why rc1, not rc1?20:02
ying_zuoFeature freeze is listed in the same time slot as Q320:03
*** VW has quit IRC20:03
ying_zuoI think RC2 is safer20:03
*** VW has joined #openstack-meeting-320:03
ying_zuojust in case20:03
ying_zuobut usually the changes upto RC1 will be included in Queens20:04
e0ne_technically, after rc1 master branch will be opened for Rocky20:04
ying_zuoyes20:04
ying_zuo#topic Open Discussion20:06
*** openstack changes topic to "Open Discussion (Meeting topic: horizon)"20:06
e0ne_ying_zuo: are you going to create etherpad for PTG topics proposals?20:07
ying_zuoright. I will do that20:08
ying_zuodo you have in mind at the moment?20:08
ying_zuodo you have anything in mind20:08
ying_zuoanything you hope to see different from the last time?20:09
e0ne_last PTG was good for me20:09
e0ne_we discussed a lot of topics20:10
ying_zuoyes20:10
ying_zuothe discussion and going through the blueprints20:11
ying_zuothis is the perfect time to propose blueprints for Rocky20:11
ying_zuoif you are thinking of adding any features, please feel free to write up a blueprint20:12
e0ne_ok, will do if any20:12
ying_zuousing this template https://blueprints.launchpad.net/horizon/+spec/template20:12
e0ne_#link https://blueprints.launchpad.net/horizon/+spec/template20:13
ying_zuoalright. thanks everyone for joining!20:15
ying_zuosee you next week20:15
david-lylethanks20:15
e0ne_see you next week!20:15
ying_zuo#endmeeting20:15
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"20:15
openstackMeeting ended Wed Jan 24 20:15:40 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:15
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2018/horizon.2018-01-24-20.00.html20:15
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2018/horizon.2018-01-24-20.00.txt20:15
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2018/horizon.2018-01-24-20.00.log.html20:15
*** slaweq has joined #openstack-meeting-320:16
*** e0ne_ has quit IRC20:19
*** slaweq has quit IRC20:29
*** mriedem has joined #openstack-meeting-320:30
*** cleong has quit IRC20:37
*** slaweq_ has joined #openstack-meeting-320:45
*** slaweq_ has quit IRC20:50
*** belmoreira has joined #openstack-meeting-320:51
dansmith#startmeeting nova_cells21:00
openstackMeeting started Wed Jan 24 21:00:01 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
*** e0ne has joined #openstack-meeting-321:00
tssurya_o/21:00
*** VW has quit IRC21:00
* dansmith pokes belmoreira melwitt mriedem 21:00
*** VW has joined #openstack-meeting-321:00
melwitto/21:01
belmoreirao/21:01
mriedemo/21:01
melwittsorry I thought maybe we were talking in #openstack-nova instead of meeting21:01
dansmith#topic bugs21:01
*** openstack changes topic to "bugs (Meeting topic: nova_cells)"21:01
dansmithI think we already said there are no new major bugs to discuss, right?21:01
mriedemright21:02
dansmith#topic open reviews21:02
belmoreiraWe just run out into something... not sure if its a bug21:02
*** openstack changes topic to "open reviews (Meeting topic: nova_cells)"21:02
dansmithanything here?21:02
mriedemnope,21:03
dansmithbelmoreira: okay let's just pile all your stuff into open discussion, which I'm assuming we can just roll to21:03
mriedemjust rechecking the alternate host patch21:03
dansmithunless anyone has anything here21:03
*** VW_ has joined #openstack-meeting-321:03
dansmithcool21:03
dansmith#topic open discussion21:03
*** openstack changes topic to "open discussion (Meeting topic: nova_cells)"21:03
*** VW has quit IRC21:03
dansmithbelmoreira: okay, first off, what's the issue you just hit?21:03
belmoreiracurrently our instance_mappings in nova_api DB doens't have any cell mapping (it's null)... when migrating to cellsV2 will need to do the correct mapping. However, the table is already populated and it fails to update the correct cell (change null to the right one)21:04
belmoreirawe are in Newton and nova_api DB is required21:04
belmoreiraare we missing something?21:05
dansmithyou're using newton nova-manage to do the instance mappings and it's not filling that field, is that right?21:05
dansmithwith --cell_uuid ?21:06
belmoreiraWe were testing this week with master and it didn't update the cell_uuid21:06
belmoreiratssurya_?21:06
tssurya_yes, we tested this with master21:06
tssurya_and we had provided the --cell_uuid21:07
dansmiththat seems really odd, I don't know why that would be21:07
mriedemprobably because of the marker?21:07
mriedemsaying you've already mapped everything21:07
tssurya_yea that or the duplicate entry check ?21:08
dansmithdoes map_instances use a marker like that?21:08
* dansmith looks21:08
mriedemit does21:08
dansmithah, then just nuke that and try again I guess21:08
mriedemcell-uuid is required for map_instances, so i'm not sure how the instance mappings would have a null cell mapping entry21:08
mriedemunless it was a bug in the CLI in newton?21:08
belmoreirain Newton we don't have any cellV2 defined21:09
dansmithidk21:09
mriedemdo you see an instance mapping with INSTANCE_MIGRATION_MARKER as the project_id?21:09
belmoreirahowever nova_api DB is required and new instances have an entry in instances_mapping21:09
mriedemi don't see how you could run map_instances without a cell_uuid21:09
mriedemto a valid cell mapping21:09
tssurya_okay so to test the scenario, we ran it on master with a --cell_uuid option21:10
dansmithcertainly not based on the master code, but maybe it was different in newton21:10
*** chason has quit IRC21:10
tssurya_we manually set the value in the DB as NULL21:10
tssurya_to recreate the scenario21:10
belmoreiramriedem we will run "map_instances" only when upgrading to Pike21:11
dansmithyou need it in ocata too21:11
dansmitheven though it's all one cell21:11
mriedemok i guess you'll have to find a valid recreate for this,21:11
belmoreiradansmith, true21:11
mriedemthat doesn't involve manually messing with the db21:11
mriedemb/c i do'nt know how this would happen21:11
mriedemare you using simple_cell_setup at all?21:12
dansmithI hope not :)21:12
dansmiththat's toootally not for situations like this :P21:12
melwittto be clear, map_instances isn't going to fill in a NULL field for you. it will only create new instance_mappings records. right?21:12
belmoreirabut is the same thing. Then we need to map again the instances to the real cells when upgrading to Pike and cellsV221:13
tssurya_melwitt : yes21:13
belmoreirain ocata everything will be mapped to only one21:13
melwittso the question is, how did you get any instance_mappings records with a NULL field in the first place21:13
mriedemi think i understand what belmoreira is saying now,21:13
dansmithah yeah I guess that's right21:13
mriedemin ocata, they have like 50 child cells,21:13
belmoreiramelwitt newton with any cellV2 defined21:13
mriedembut they really only have 1 global cellsv2 cell right?21:13
mriedemso if you map instances in ocata, they go to the global single cellsv2 cell,21:14
mriedembut in pike,21:14
mriedemyou want to map the instances in the separate child cells,21:14
mriedembut they are already mapped to the global thing21:14
belmoreiramriedem yes21:14
mriedemcorrect?21:14
mriedemok21:14
mriedemwell,21:14
melwittoh, I understand now too21:14
dansmithyeah, but at that point you can just nuke all the mappings and recreate them right?21:14
melwittit wasn't NULL but it was all to one global cell21:14
*** chason has joined #openstack-meeting-321:15
mriedemdansmith: yeah, that or provide some --overwrite option to the CLI21:15
mriedemto create or update21:15
belmoreiradansmith we were thinking on that as well. Just asking if there was a different way, ir the nova-manage instance mapping just could update the cell if already sees the instance21:15
tssurya_dansmith : we already thought of nuking and recreating21:15
dansmithyeah I actually thought the code would create or get-and-then-save, but it doesn't21:15
dansmithupdating the cell of an instance is kindof a dangerous thing if it's wrong, which might be why this doesn't do that now, but I can't think of any real reason to not do that21:16
mriedemthe fake marker in the instance_mappings table will also cause problems21:16
dansmithif you ended up with two cells pointing at the same db, for example, you could re-map and mess struff up21:16
dansmithoh right21:17
*** raildo has quit IRC21:17
belmoreiramelwitt all instance_mappings created in Ocata have the cell_uuid of the global but the old entries from newton is null21:17
dansmithso we could allow delete_cell --force to remove instance mappings too,21:18
dansmithand then when they go to delete their global cell, it will nuke the instance mappings too21:18
mriedemi think that's probably safer21:18
melwittbelmoreira: oh, odd. there must be a bug in newton then. we need to investigate that21:18
dansmithwe have --force right now for hosts but not instance mappings21:18
mriedemnote that the marker mapping has a null cell mapping field21:19
tssurya_dansmith : yes mappings go only after archive21:19
mriedemso delete_cell --force wouldn't remove the marker either...21:19
dansmithyeah the marker is going to be a problem regardless21:19
dansmithwe probably need a map_instances --reset21:20
dansmithwhich will avoid the marker21:20
belmoreiradon't know what the marker is. Will check tomorrow21:20
mriedemmap_instances can run in chunks21:20
mriedemuntil complete,21:20
mriedemso there is a marker for knowing where to start next21:20
*** e0ne has quit IRC21:20
belmoreiramriedem thanks21:20
dansmithso, belmoreira tssurya_, can one of you file bugs for these two new flags to the cli?21:21
tssurya_dansmith : sure21:21
dansmithokay so is that all we need to discuss on this map_instances thing?21:21
*** yamahata has quit IRC21:21
belmoreiraFrom us I think so21:22
dansmithokay, so what else did you have? the cell-is-down thing?21:22
tssurya_just to be sure the new flags you mean are reset and force right ?21:22
mriedem1. reset marker on map_instances21:22
dansmithtssurya_: for map_instances and delete_cell respectively, yeah21:22
mriedem2. remove instance mappings for a deleted cell21:22
tssurya_dansmith : got it21:22
tssurya_mriedem thanks21:22
dansmithtssurya_: we already have --force on delete_cell but it's only active for hosts, so it needs to do instance_mappings too21:23
belmoreirawhen moving to Pike with cellsV2 we need to have a solution for a cell going down.21:23
dansmithI'm quite sure we previously said something about never wanting to let you nuke a cell with instances in it, but alas, whatever :)21:23
tssurya_dansmith : yea I remember that patch from takashi21:23
mriedembelmoreira: well the solution probably depends on what you need for functionality out of the API21:24
dansmithand it depends on what the API people want in the way of communicating a partial result21:24
belmoreiraunderstand21:25
mriedemyeah because i think all we have in the api db is the instance uuid, cell and host21:25
dansmithpretty much yeah21:25
belmoreirafor us the uuid will be enough21:25
dansmithso I expect we'll just need to return {uuid: $uuid, state: UNKNOWN} or something for each instance21:25
belmoreirabut I can't hide instances from the users21:26
dansmithbut then the api layer will need to return 234: only part of your stuff was found, yo.21:26
belmoreirais looking into the request_specs a crazy idea?21:26
dansmithyes21:26
mriedemthere is a bunch of stuff we'll need to return UNKNOWN for21:26
dansmith:)21:26
belmoreira:)21:26
belmoreiracrazy yes, but it could work... just when a cell is down21:27
mriedemi guess i forgot about request specs21:28
dansmithI don't know how much we could get out of reqspec that would be accurate, so I'd have to see,21:28
dansmithbut reqspec requires de-json'ing every instance21:28
dansmithwhich would be a lot of CPU overhead to incur when a cell is down21:28
dansmithand we couldn't get all the info out of it that we need I think21:28
mriedemnot so bad for GET on a specific instance,21:28
mriedembut for listing instances, yes definitely21:28
dansmithand I'm also not sure it'll always be accurate.. I can't remember if we update reqspec after a resize, for example21:29
mriedemthe accuracy of reqspecs is definitely dubious21:29
dansmithsince resize happens in the cell late, I think we don't21:29
* mriedem refers to all of the TODOs in the conductor code21:29
dansmithyeah, reqspecs are a big mess21:29
mriedemlooks like we do update the reqspec for the new flavor during resize,21:30
mriedemin conductor21:30
mriedemand for rebuild if you're changing the image, in the api21:30
dansmithand if the resize fails? I guess we have a chance to fix it when you revert or confirm?21:31
mriedemyeah i don't see anything about fixing the reqspec if the resize fails, or you revert21:31
dansmithanyway, this is about listing and I think listing and de-jsoning all that stuff for a whole cell is a bit of a problem21:31
dansmithso one option I guess,21:32
dansmithis to just fake out anything we don't have and go forward with that21:32
dansmithknowing it's a bit of a lie, but we could do that fairly quickly21:32
mriedemyeah i think we're going to have to start with the quick and dirty options so we have *something* if a cell is down21:33
dansmithI dunno what to say about things like the flavor21:33
dansmithright, well, I thought that's what tssurya_ was going to do21:33
dansmithso we had something to argue over :)21:33
belmoreiraI'm happy with "not available"21:33
belmoreirasame for VM state, and all the others21:33
mriedemand then if we did try to use the requestspec for a single GET /servers/id, we then have to assess how much of the response could be wrong, and if we're going to spend a bunch of time updating code to make sure the reqspec is correct because it's now used in the API21:33
dansmithso we currently have a state of "unknown" for if the host is down I think21:33
dansmithbut we still have things like flavor at that point21:34
dansmithmriedem: well, if we lie in the list, then returning different stuff on GET is kinda messy21:34
tssurya_dansmith : yes that what we have started with, we have faked stuff, but yes stuck at fields lke flavor21:34
dansmithif we return a shell only in the list somehow, then the GET having details seems a little more legit to me21:34
mriedemdansmith: i don't mean lie in the list,21:34
dansmithtssurya_: ack, makes sense21:35
mriedemlist would just return uuid and UNKNOWN for everything else,21:35
dansmithwell, that's not going to work with our schema I'm sure21:35
mriedemwith the uuid, you could at least to get some information for a specific instance using the reqspec, but that could be all wrong too21:35
dansmithwe can't return UNKNOWN for a flavor that should be a dict21:35
mriedemright, we'd have to use something else that means unknown for non-strings21:35
mriedemNone or {} or [] or -1 or whatever21:36
dansmithor we fill out a flavor object with all UNKNOWN properties,21:36
dansmithbut we have no sentinel for integers21:36
mriedem-1 typically means unlimited :)21:36
dansmithwhich is terrible,21:36
dansmithand which will conflict for flavor things that actually use -1 and 0 and stuff21:36
mriedem-MAX_INT :)21:37
dansmithbut that's fine, we can start with that and see how it goes21:37
dansmiththey can at least use that locally while we argue21:37
melwittcross reference with the flavors table?21:37
dansmithmelwitt: can't21:37
dansmithwe don't know which flavor look up in there, unless we decode the reqspec, which as pointed out, may be stale21:37
dansmith(and it's a lie since the flavor might have been redefined)21:38
dansmithwe could pull the first flavor and just say everything in the cell is flavors[0] :P21:38
mriedemthe reqspec has a serialized versoin of the flavor from when the instance was created,21:38
melwitthehe21:38
mriedemlike the instance itself21:38
dansmithah yeah so if we're going to decode that we could just use that lie instead of making up a new one :)21:38
dansmithtssurya_: so I think you just need to post something, anything, document the things you know are controversial, and then let's go from there21:39
dansmiththat was the point of the straw man21:39
tssurya_sure I have been playing around with the above stuff21:39
dansmithwe can point api people to it and they can say "I hate this so much" and then we can ask for alternatives :)21:39
tssurya_on how to go about with the various fields21:39
belmoreiragreat, we will continue with this approach21:40
melwittdansmith: are you saying post up a rough POC patch?21:40
mriedemyeah21:40
dansmithmelwitt: yes,21:40
dansmiththat's the thing I'm saying we need to discuss (a strawman)21:40
mriedem"post up" isn't that gang slang?21:40
melwittokay. so yeah, tssurya_ if you can post up a very rough draft POC patch to show a way we can do it, we can discuss it there more concretely21:40
tssurya_cool then, will open a WIP21:40
melwittgang slang? lol.21:41
mriedemhttps://www.urbandictionary.com/define.php?term=post%20up21:41
melwitt"propose"21:41
mriedemtime to watch the wire again21:41
tssurya_another thing we got stuck at was this - https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/extended_volumes.py#L5021:41
tssurya_even if we manage to fill fake stuff and come out,21:42
tssurya_again the connection failure stuff comes up21:42
dansmiththat needs to be converted to use scatter/gather and then it can take a similar approach21:42
tssurya_dansmith : ok21:42
melwittmriedem: lol, nice. I had never heard of it before21:42
mriedemtssurya_: what's the issue? that we don't know which volumes are attached to which servers b/c we can't get BDMs?21:42
tssurya_yea21:43
mriedemwe could use cinder...21:43
mriedembut i don't know if there is a way to list volumes by instance_uuid in cinder as a filter, there might be21:43
tssurya_basically that code again tries to query the DB which is down of course21:43
dansmiththat's N calls to cinder for N instances right?21:43
mriedemif it's a list, i'm just saying for a show21:44
mriedemif we do anything21:44
dansmiththat is only for list21:44
mriedemagain, start small and just ignore the down cell and return []21:44
dansmithagreed21:44
mriedemdansmith: i do'nt think so...21:44
belmoreira+121:44
mriedemhttps://github.com/openstack/nova/blob/master/nova/api/openstack/compute/extended_volumes.py#L4021:44
tssurya_mriedem : ok :d21:45
dansmithmriedem: doesn't use that helper21:45
mriedemah21:45
dansmithonly detail does, and it takes a list of servers and iterates over them21:45
dansmiththe show needs to be graceful about not failing the whole show there though because it tries and fails to do the list21:46
dansmiththe context is targeted there, so it needs to catch that and not explode21:46
dansmithelse the returning of fake things isn't going to work21:46
dansmithtssurya_, belmoreira: okay what else?21:48
belmoreiraabout quotas...21:48
belmoreiraWhat we are thinking is if we can't use the request_specs to calculate the quota of a project (challenging!!!) we will block the creation of new instances if the project has instances in cells that are down.21:48
belmoreiramakes sense?21:48
dansmiththat seems like a totally legit workaround to me21:48
dansmithit needs to be configurable, in [workarounds]21:49
dansmithas not everyone will want that of course21:49
mriedemthat seems fine as a start to me also21:50
melwittyeah, seems like that could be a good way to best-effort quota while cells are down21:50
mriedemalthough,21:50
mriedemwhen you go to create a server, how do you know any cells are down?21:50
dansmithwe have to know if cells are down when..21:50
dansmithyeah that21:50
mriedemsince we don't have any status for cell mappings?/21:50
dansmithbut21:50
melwittthe scatter-gather will return sentinels for no response etc at least21:51
dansmiththe scheduler has to get the host lists from all the cells to start, right?21:51
dansmithalthough not with placement anymore I guess.. not reliably overlapping the down cell21:51
melwitt(during the quota check)21:51
mriedemunless you're forcing a specific host, yeah21:51
dansmithmelwitt: ah right because we do the quota check21:51
dansmithsweet21:51
belmoreirabut the quota will be checked21:51
dansmithyep, totes21:52
mriedemso if the quota check scatter gather returns sentinels, fail?21:52
mriedemor, check to see if that project has instances in a downed cell?21:52
dansmith...and this flag is asserted21:52
dansmithmriedem: yeah, if sentinels, then go on to check on instances in the down cell21:52
mriedemit's almost like we need a service group API heartbeat for cells...21:53
dansmithwhich we can do by checking mappings21:53
dansmithbecause our other servicegroup heartbeat thing works so well?21:53
mriedemtotally21:53
melwittwouldn't it be if sentinels then fall back to request_specs if workaround?21:53
mriedemif it were using zk21:53
dansmitheither way, we'd have to have one thing in the cell dedicated to pumping that back up, which is a problem21:53
dansmithmelwitt: no, not using reqspecs at all21:53
dansmithmelwitt: if we do the quota check and find downed sentinels, then we quickly count the number of instances owned by the project in those downed cells21:54
melwittoh. what do you mean by "check on instances in down cell"21:54
dansmithif that number is nonzero, then we refuse the build21:54
mriedemdansmith: i think i'm just proposing some kind of periodic at the top (scheduler?) that tries to target the cells every minute or something21:54
melwittoh, I see21:54
melwittfor cores and ram you'd need request_spec21:54
dansmithmriedem: we have no single thing that can do that, we can have multiple schedulers now, and network partitions may make that not so straightforward21:55
mriedemthis reminds me that we said in syndey we'd add a type to the allocations / consumers table in placement...and didn't21:55
melwitter, nevermind. I think I'm not following the "nonzero, refuse the build". need to think more21:55
dansmithmelwitt: we wouldn't care about cores and ram, because they have instances in the downed cell so we just punt21:55
melwittgot it21:55
dansmithmriedem: we said we would and then got into a big argument21:55
dansmithmriedem: and apparently there was a lot of disagreement on it21:55
dansmithand jay wasn't there21:56
* mriedem adds it back to the ptg etherpad21:56
melwittyeah, we need the type to be able to use placement for the quota stuff21:56
dansmithanyway21:56
dansmithtssurya_: belmoreira: I say propose something for that, yeah21:56
tssurya_dansmith : yep21:56
belmoreirayes, will do21:56
dansmithsweet21:56
dansmithis there anything else? we're about out of time21:57
tssurya_I guess that's all for now ...21:57
dansmithokay, anything else can go back to the main channel21:57
dansmithlast call....21:57
belmoreirathanks a lot21:57
dansmith...for alcohol21:57
tssurya_thanks!21:58
* dansmith said that for mriedem's benefit21:58
dansmith#endmeeting21:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"21:58
openstackMeeting ended Wed Jan 24 21:58:10 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2018/nova_cells.2018-01-24-21.00.html21:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2018/nova_cells.2018-01-24-21.00.txt21:58
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2018/nova_cells.2018-01-24-21.00.log.html21:58
mriedemooo george thoroughgood refferences21:59
mriedemwow spelling21:59
*** belmoreira has quit IRC22:00
*** mriedem has left #openstack-meeting-322:00
*** mriedem has joined #openstack-meeting-322:01
*** mriedem has left #openstack-meeting-322:02
*** tssurya_ has quit IRC22:05
*** rmcall has quit IRC22:09
*** lyan has quit IRC22:11
*** VW_ has quit IRC22:18
*** VW has joined #openstack-meeting-322:19
*** sgrasley1 has joined #openstack-meeting-322:20
*** sgrasley1 has quit IRC22:24
*** sgrasley1 has joined #openstack-meeting-322:24
*** bobh has quit IRC22:28
*** jrist has quit IRC22:29
*** jrist has joined #openstack-meeting-322:30
*** VW_ has joined #openstack-meeting-322:34
*** VW has quit IRC22:37
*** VW_ has quit IRC22:39
*** sgrasley1 has quit IRC22:52
*** kei-ichi has joined #openstack-meeting-323:08
*** yamahata has joined #openstack-meeting-323:17
*** apetrich has quit IRC23:35
*** hongbin has quit IRC23:56

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