Wednesday, 2018-03-21

*** caoyuan has joined #openstack-meeting-400:36
*** zhubingbing has joined #openstack-meeting-400:41
*** yamamoto has joined #openstack-meeting-400:43
*** caoyuan has quit IRC00:44
*** zhubingbing has quit IRC00:45
*** TxGirlGeek has quit IRC00:48
*** yamamoto has quit IRC00:48
*** hongbin has joined #openstack-meeting-400:51
*** caoyuan has joined #openstack-meeting-400:51
*** caoyuan has quit IRC01:00
*** julim has joined #openstack-meeting-401:02
*** chyka has joined #openstack-meeting-401:07
*** harlowja has quit IRC01:07
*** chyka has quit IRC01:12
*** yamamoto has joined #openstack-meeting-401:45
*** yamamoto has quit IRC01:51
*** caoyuan has joined #openstack-meeting-401:58
*** caoyuan has quit IRC01:59
*** caoyuan has joined #openstack-meeting-402:00
*** seajay has joined #openstack-meeting-402:02
*** caoyuan_ has joined #openstack-meeting-402:06
*** caoyuan has quit IRC02:06
*** seajay has quit IRC02:16
*** yamamoto has joined #openstack-meeting-402:37
*** psachin has joined #openstack-meeting-402:38
*** zhurong has joined #openstack-meeting-402:40
*** salv-orl_ has joined #openstack-meeting-402:48
*** salv-orlando has quit IRC02:51
*** yamamoto has quit IRC02:55
*** dave-mccowan has quit IRC03:16
*** hongbin has quit IRC03:19
*** iyamahat_ has quit IRC03:33
*** zhurong has quit IRC03:44
*** yamamoto has joined #openstack-meeting-403:45
*** links has joined #openstack-meeting-404:00
*** links has quit IRC04:00
*** yamamoto has quit IRC04:07
*** yamamoto has joined #openstack-meeting-404:08
*** radeks has joined #openstack-meeting-404:29
*** radeks has quit IRC04:30
*** radeks has joined #openstack-meeting-404:30
*** yamamoto has quit IRC04:33
*** chyka has joined #openstack-meeting-404:34
*** harlowja has joined #openstack-meeting-404:39
*** chyka has quit IRC04:39
*** zhubingbing has joined #openstack-meeting-404:44
*** zhubingbing has quit IRC04:49
*** harlowja has quit IRC04:56
*** lpetrut has joined #openstack-meeting-405:06
*** yboaron has joined #openstack-meeting-405:11
*** Mmike has quit IRC05:41
*** Mmike has joined #openstack-meeting-406:05
*** zhurong has joined #openstack-meeting-406:05
*** lpetrut has quit IRC06:19
*** yamamoto has joined #openstack-meeting-406:28
*** radeks has quit IRC06:30
*** radeks has joined #openstack-meeting-406:32
*** lpetrut has joined #openstack-meeting-406:35
*** sdake has quit IRC06:35
*** sdake has joined #openstack-meeting-406:37
*** sdake has quit IRC06:37
*** sdake has joined #openstack-meeting-406:37
*** gkadam has joined #openstack-meeting-406:50
*** lpetrut has quit IRC06:55
*** logan- has quit IRC06:58
*** logan- has joined #openstack-meeting-406:58
*** kiennt26 has joined #openstack-meeting-407:04
*** salv-orl_ has quit IRC07:12
*** alexchadin has joined #openstack-meeting-407:14
*** salv-orlando has joined #openstack-meeting-407:16
*** yamamoto has quit IRC07:32
*** zhubingbing has joined #openstack-meeting-407:47
*** zhubingbing has quit IRC07:51
*** yamahata has joined #openstack-meeting-407:55
*** Idan_Kinory has joined #openstack-meeting-407:57
*** ifat_afek has joined #openstack-meeting-407:59
ifat_afek#startmeeting vitrage08:00
openstackMeeting started Wed Mar 21 08:00:13 2018 UTC and is due to finish in 60 minutes.  The chair is ifat_afek. Information about MeetBot at http://wiki.debian.org/MeetBot.08:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:00
*** openstack changes topic to " (Meeting topic: vitrage)"08:00
openstackThe meeting name has been set to 'vitrage'08:00
ifat_afekHi :-)08:00
*** Liat has joined #openstack-meeting-408:00
*** yamamoto has joined #openstack-meeting-408:00
*** annarez has joined #openstack-meeting-408:00
*** cjloader has joined #openstack-meeting-408:01
annarezHi :)08:01
Idan_KinoryHi08:01
LiatHi08:01
*** dwj has joined #openstack-meeting-408:01
*** nivo has joined #openstack-meeting-408:01
yujunzhi08:01
nivohey08:01
*** eyalb has joined #openstack-meeting-408:01
eyalb\o/08:02
*** peipei has joined #openstack-meeting-408:03
*** yamamoto has quit IRC08:03
ifat_afekFirst update: I would like to nominate dwj to a Vitrage core contributor :-) I will send an email to OpenStack mailing list later today08:03
eyalb+208:03
yujunz+208:04
annarezcongratulations!!08:04
dwjThanks~08:04
ifat_afekWelcome :-)08:04
Idan_Kinorycongratulations :)08:05
ifat_afekNext - we have continued the equivalence/merge alarm and resource design.08:05
ifat_afek#link https://review.openstack.org/55053408:05
ifat_afek#link https://review.openstack.org/54793108:05
ifat_afekyujunz, dwj: any update on your side?08:05
dwjNo08:05
ifat_afekand peipei of course :-)08:05
ifat_afekSo how do we continue?08:05
yujunzI discussed about the topic with peipei and want to clarify a few things.08:06
ifat_afekOK08:06
yujunzFirstly the use case for us is mainly the merge of reported and monitored alarm.08:07
yujunzSorry reported and deduced08:07
*** cjloader has quit IRC08:08
yujunzSince we are actually deducing an alarm which should be reported. So the there is less conflict in properties than two distinct data sources.08:08
ifat_afekMakes sense08:09
*** gcheresh has joined #openstack-meeting-408:10
yujunzSo I wonder if you have the use case for two different alarm data sources like nagios and zabbix at the same time or currently what you are facing is mainly the resource equivalent08:11
ifat_afekNot now, but we might have this use case in the future08:11
ifat_afekWe are not working on Prometheus datasource, and we might add Grafana, that will also include Prometheus alarms08:11
yujunznot or now? :-)08:12
ifat_afeknow :-)08:12
peipeiso the use case that two monitored alarms are equivalent should be supported any how,right?08:13
*** yamamoto has joined #openstack-meeting-408:13
ifat_afekWe won’t need it in Rocky, but we will probably need it some time in the future (within a year maybe), and then we don’t want to have two different mechanisms08:14
yujunzYou mean two mechanism for resource and alarm?08:14
ifat_afekFor resource merge, we can handle k8s datasource without it, since it knows exactly the Nova datasource properties08:14
ifat_afekI mean two mechanisms for deduced and complete merge08:15
ifat_afekBecause if I understand you correctly, you are saying that maybe we could have a smaller refactoring now that will only solve your use case08:15
ifat_afekI agree that it might be easier, the question is what we will do in the future08:15
*** yamamoto has quit IRC08:16
ifat_afekWill you ever need the full merge functionality?08:16
ifat_afekIn ZTE?08:16
*** yamamoto has joined #openstack-meeting-408:16
peipeiWe have discussed that maybe we can use equivalence for resource, and merge for alarm.08:18
ifat_afekAnother future use case is merge of Vitrage discovery agent and Nova, but this won’t happen in Rocky either08:19
ifat_afekAnd  we don’t know the details yet08:19
ifat_afekpeipei: why?08:19
peipeiBecause equivalence for alarm will be complex。08:20
ifat_afekAlso for resources, right?…08:20
peipeiIf we support bidirectional deduce, maybe number of scenarios  will rise by exponential...08:21
ifat_afekSo you don’t want to duplicate the scenarios, that’s the main motivation?08:22
ifat_afekI would say it’s not complex, but it has a performance issue08:22
ifat_afekBut in order to not-duplicate scenarios, I believe we need the merge option that I suggested, where we keep all properties all all datasources08:23
ifat_afekOr do you want to make a special handling without it, just because it is Vitrage and not two external monitors?08:24
*** chyka has joined #openstack-meeting-408:24
yujunzAre you talking about merge option #2 ?08:25
ifat_afekI think so08:26
ifat_afekUnless we find a way for option #1 without scenario duplication08:26
peipeiYou mean overwrite in merge option #1?08:27
peipeior equivalence option?08:28
ifat_afekI mean overwrite merge option #108:28
ifat_afekI understood that you don’t want equivalence08:28
*** chyka has quit IRC08:29
ifat_afekBTW, we didn’t discuss it in the last meeting, but - are you sure that you won’t reach an endless loop in the bi-directional templates?08:29
annarezpeipei why is scenario duplication in the case of bidirectional deduce will be exponential?08:30
peipeiIn the template A OR B -> C, and zabbix A ~ nagios A, and zabbix B~ nagios B, 4 scenarios will be matched.08:33
ifat_afekSo this is not related to bidirectional deduction, right?08:33
peipeiYes.08:34
peipeiI mean if in bi-diretional, number of nodes and edged both rise fastly08:34
ifat_afekSo this is the performance problem we discussed. The question is how many such equivalences you expect to have08:35
ifat_afekRegarding bidirectional: you will have C -> suspect V08:36
ifat_afekSo this will not be duplicatied08:36
ifat_afekV for Vitrage :-)08:36
ifat_afekBTW, it is important to note that in your example we WON’T execute four scenarios. There will be a single trigger, say zabbix A. So we will only execute scenarios related to Zabbix A, and there will be two of them. The Nagios A scenarios will be ignored at this stage08:37
ifat_afekAnd again, what matters is how many duplicated scenarios you expect to have08:38
yujunzI think performance is just one side of concerns. There is a complexity issue in the deducing model.08:40
ifat_afekWhat do you mean?08:41
yujunzWith equivalent entities in the graph, it is no longer a tree, but probably a a mesh.08:41
ifat_afekIt hasn’t been a tree for a long time :-) with RCA and ‘causes’ edges08:42
ifat_afekAnd Heat stacks08:42
ifat_afekBut I understand what you mean08:42
ifat_afekBut why does it matter so much? the sub-graph matching algorithm should work as before08:43
peipeiI wonder whether duplicated scenarios will lower performance of sub-graph matching algorithm?08:45
*** lpetrut has joined #openstack-meeting-408:45
ifat_afekCan I ask something? why is it actually so important to create a suspect alarm? why not write a template like ‘ if C and not A then run diagnose action’? without having an intermediate suspect vertex?08:46
*** idan_hefetz has joined #openstack-meeting-408:46
ifat_afekWhy do you think that duplicated scenarios will have lower performance? it only means that we will execute more scenarios08:47
ifat_afekWe should chose one of two solutions: 1. IMO is more robust, but with a performance penalty 2. Better performance, but very complex implementation08:48
ifat_afekThat’s how I see it08:48
*** lpetrut has quit IRC08:48
*** lpetrut_ has joined #openstack-meeting-408:48
peipeiOk, and merge option #2 may be more complex to implement.08:50
peipeiAnd I can send a more detailed design about merge option lator by mail.08:50
ifat_afekWhat option are you talking about?08:51
ifat_afekI meant 1. equivalence and 2. merge option #208:51
peipeimerge option #208:51
ifat_afekRegarding merge option #1 - I think it still requires scenario duplication08:51
ifat_afekOk08:51
*** aniketh has joined #openstack-meeting-408:51
ifat_afekTwo unrelated quick updates, before we end the meeting08:53
ifat_afek#topic Vancouver summit08:53
*** openstack changes topic to "Vancouver summit (Meeting topic: vitrage)"08:53
ifat_afekWe are going to have many Vitrage sessions in Vancouver :-)08:53
yujunzHow many? I got 1/3 :-)08:54
ifat_afek#link https://www.openstack.org/summit/vancouver-2018/summit-schedule/global-search?t=vitrage08:54
ifat_afek7 total, one of them by WindRiver08:54
ifat_afekAbout the alarm banner that they implemented08:54
ifat_afekNot all of them are *about* Vitrage, but they will mention Vitrage08:55
ifat_afekNext, we can ask for a forum discussion. We need to think if there is an issue we would like to discuss08:56
ifat_afek#link http://lists.openstack.org/pipermail/openstack-dev/2018-March/127944.htmlx08:56
ifat_afek#link https://wiki.openstack.org/wiki/Forum/Vancouver201808:56
ifat_afek#link https://wiki.openstack.org/wiki/Forum08:56
ifat_afekI created an etherpad, at the moment it is empty08:56
ifat_afek#link https://etherpad.openstack.org/p/YVR-vitrage-brainstorming08:56
ifat_afekAnd last issue: StoryBoard migration. annarez and I checked it and we have a few unclear issues. We emailed OpenStack representative and got no response yet. So for now it is on hold08:57
ifat_afekAnything else? we have 3 minutes left08:57
ifat_afekBye, see you next week :-)08:59
yujunzBye08:59
eyalbbye08:59
annarezbye08:59
dwjBye08:59
Liatby08:59
Liatbye08:59
*** annarez has quit IRC09:00
ifat_afek#endmeeting09:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"09:00
openstackMeeting ended Wed Mar 21 09:00:01 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vitrage/2018/vitrage.2018-03-21-08.00.html09:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2018/vitrage.2018-03-21-08.00.txt09:00
openstackLog:            http://eavesdrop.openstack.org/meetings/vitrage/2018/vitrage.2018-03-21-08.00.log.html09:00
*** Idan_Kinory has quit IRC09:00
*** zhurong has quit IRC09:04
*** dwj has quit IRC09:06
*** zhurong has joined #openstack-meeting-409:14
*** Liat has quit IRC09:14
*** paken has joined #openstack-meeting-409:36
*** ifat_afek has left #openstack-meeting-409:38
*** yamamoto has quit IRC09:42
*** yamamoto has joined #openstack-meeting-409:43
*** yamamoto has quit IRC09:48
*** yamamoto has joined #openstack-meeting-409:48
*** yamamoto has quit IRC09:48
*** idan_hefetz has quit IRC09:49
*** pbourke has joined #openstack-meeting-409:53
*** salmankhan has joined #openstack-meeting-409:59
*** eyalb has left #openstack-meeting-410:05
*** salmankhan1 has joined #openstack-meeting-410:11
*** salmankhan has quit IRC10:11
*** salmankhan1 is now known as salmankhan10:11
*** caoyuan_ has quit IRC10:13
*** ktibi has joined #openstack-meeting-410:15
*** alexchadin has quit IRC10:27
*** alexchadin has joined #openstack-meeting-410:28
*** salmankhan has quit IRC10:30
*** alexchadin has quit IRC10:30
*** salmankhan has joined #openstack-meeting-410:34
*** alexchadin has joined #openstack-meeting-410:35
*** alexchadin has quit IRC10:46
*** yamamoto has joined #openstack-meeting-410:48
*** yamahata has quit IRC10:52
*** yamamoto has quit IRC10:54
*** zhurong has quit IRC10:55
*** yamamoto has joined #openstack-meeting-410:56
*** yamamoto has quit IRC11:01
*** chyka has joined #openstack-meeting-411:02
*** yamamoto has joined #openstack-meeting-411:02
*** yboaron has quit IRC11:03
*** numans is now known as numans_afk11:05
*** yamamoto has quit IRC11:06
*** chyka has quit IRC11:07
*** seajay has joined #openstack-meeting-411:11
*** TxGirlGeek has joined #openstack-meeting-411:14
*** yamamoto has joined #openstack-meeting-411:16
*** yamamoto has quit IRC11:16
*** alexchadin has joined #openstack-meeting-411:16
*** TxGirlGeek has quit IRC11:19
*** diman has joined #openstack-meeting-411:25
*** snapiri has quit IRC11:28
*** snapiri has joined #openstack-meeting-411:28
*** numans_afk is now known as numans11:29
*** diman has quit IRC11:37
*** diman has joined #openstack-meeting-411:43
*** diman has quit IRC11:47
*** yamamoto has joined #openstack-meeting-411:48
*** zhubingbing has joined #openstack-meeting-411:49
*** yamamoto has quit IRC11:52
*** zhubingbing has quit IRC11:53
*** zhubingbing has joined #openstack-meeting-412:03
*** yamamoto has joined #openstack-meeting-412:03
*** yamamoto has quit IRC12:08
*** nivo has quit IRC12:16
*** yamamoto has joined #openstack-meeting-412:18
*** yamamoto has quit IRC12:22
*** sambetts|afk is now known as sambetts12:24
*** yamamoto has joined #openstack-meeting-412:33
*** yamamoto has quit IRC12:38
*** VW has joined #openstack-meeting-412:41
*** yamamoto has joined #openstack-meeting-412:48
*** lyan has joined #openstack-meeting-412:52
*** lyan is now known as Guest1710112:52
*** yamamoto has quit IRC12:53
*** zhubingbing has quit IRC12:53
*** diman has joined #openstack-meeting-412:57
*** diman has quit IRC12:57
*** SerenaFeng has joined #openstack-meeting-413:00
*** pmesserli has joined #openstack-meeting-413:00
*** SerenaFeng has quit IRC13:02
*** SerenaFeng has joined #openstack-meeting-413:03
*** yamamoto has joined #openstack-meeting-413:03
*** mjturek has joined #openstack-meeting-413:03
*** SerenaFeng has quit IRC13:05
*** SerenaFeng has joined #openstack-meeting-413:06
*** diman has joined #openstack-meeting-413:07
*** yamamoto has quit IRC13:08
*** SerenaFeng has quit IRC13:12
*** diman has quit IRC13:14
*** zhubingbing has joined #openstack-meeting-413:14
*** diman has joined #openstack-meeting-413:16
*** yamamoto has joined #openstack-meeting-413:18
*** snapiri has quit IRC13:19
*** diman has quit IRC13:20
*** yamamoto has quit IRC13:22
*** alexchad_ has joined #openstack-meeting-413:24
*** alexchadin has quit IRC13:25
*** zhubingbing has quit IRC13:26
*** edleafe- has joined #openstack-meeting-413:28
*** edleafe has quit IRC13:29
*** edleafe- is now known as edleafe13:29
*** diman_ has joined #openstack-meeting-413:31
*** yamamoto has joined #openstack-meeting-413:33
*** diman_ has quit IRC13:35
*** zhubingbing has joined #openstack-meeting-413:36
*** yamamoto has quit IRC13:38
*** Yumeng__ has joined #openstack-meeting-413:39
*** dklyle has joined #openstack-meeting-413:44
*** david-lyle has quit IRC13:44
*** yamamoto has joined #openstack-meeting-413:48
*** psachin has quit IRC13:48
*** yamamoto has quit IRC13:53
*** alexchad_ is now known as alexchadin13:54
*** suzhengwei has joined #openstack-meeting-413:58
*** ktibi has quit IRC13:59
*** bobh has joined #openstack-meeting-414:03
*** yamamoto has joined #openstack-meeting-414:03
*** SerenaFeng has joined #openstack-meeting-414:05
*** yamamoto has quit IRC14:07
*** hongbin has joined #openstack-meeting-414:08
*** salmankhan has quit IRC14:10
*** premsankar has joined #openstack-meeting-414:14
*** salmankhan has joined #openstack-meeting-414:15
*** gkadam_ has joined #openstack-meeting-414:18
*** yamamoto has joined #openstack-meeting-414:18
*** caoyuan has joined #openstack-meeting-414:19
*** salmankhan has quit IRC14:20
*** salmankhan has joined #openstack-meeting-414:20
*** gkadam has quit IRC14:20
*** yamamoto has quit IRC14:23
*** ktibi has joined #openstack-meeting-414:23
*** cjloader has joined #openstack-meeting-414:24
*** diman has joined #openstack-meeting-414:32
*** yamamoto has joined #openstack-meeting-414:33
*** mjturek has quit IRC14:35
*** mjturek has joined #openstack-meeting-414:35
*** hamzy has joined #openstack-meeting-414:35
*** gcheresh_ has joined #openstack-meeting-414:35
*** diman has quit IRC14:37
*** yamamoto has quit IRC14:38
*** gcheresh has quit IRC14:38
*** gcheresh_ has quit IRC14:41
*** yamamoto has joined #openstack-meeting-414:46
*** yamamoto has quit IRC14:46
*** dave-mccowan has joined #openstack-meeting-414:47
*** Mmike has quit IRC14:48
*** Mmike has joined #openstack-meeting-414:48
*** suzhengwei has quit IRC14:50
*** alexchadin has quit IRC14:50
*** zhubingbing has quit IRC14:53
*** gcheresh_ has joined #openstack-meeting-414:57
*** zhubingbing has joined #openstack-meeting-414:58
*** yamahata has joined #openstack-meeting-414:59
*** iyamahat has joined #openstack-meeting-415:00
*** SerenaFeng has quit IRC15:06
*** Yumeng__ has left #openstack-meeting-415:06
*** gcheresh_ has quit IRC15:08
*** gkadam_ has quit IRC15:15
*** VW_ has joined #openstack-meeting-415:28
*** kbyrne has quit IRC15:30
*** VW has quit IRC15:30
*** VW_ has quit IRC15:32
*** VW has joined #openstack-meeting-415:32
*** yamamoto has joined #openstack-meeting-415:33
*** diman has joined #openstack-meeting-415:34
*** kbyrne has joined #openstack-meeting-415:35
*** diman has quit IRC15:39
*** caoyuan has quit IRC15:49
*** VW has quit IRC15:50
*** chyka has joined #openstack-meeting-415:50
*** VW has joined #openstack-meeting-415:50
*** zhubingbing has quit IRC15:55
*** duonghq has joined #openstack-meeting-415:55
*** mjturek has quit IRC15:56
*** bmace has joined #openstack-meeting-415:56
*** mjturek has joined #openstack-meeting-415:56
*** mgiles has joined #openstack-meeting-415:56
*** sadasu has joined #openstack-meeting-415:57
*** mgoddard has joined #openstack-meeting-415:57
*** JamesBenson has joined #openstack-meeting-415:57
*** mjturek has quit IRC15:57
*** iyamahat has quit IRC15:58
*** caoyuan has joined #openstack-meeting-415:58
Jeffrey4l#startmeeting kolla16:00
openstackMeeting started Wed Mar 21 16:00:03 2018 UTC and is due to finish in 60 minutes.  The chair is Jeffrey4l. 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: kolla)"16:00
openstackThe meeting name has been set to 'kolla'16:00
Jeffrey4l#topic  Roll-call16:00
*** openstack changes topic to "Roll-call (Meeting topic: kolla)"16:00
mgoddardo/16:00
duonghqo/16:00
caoyuano、16:00
spsurya__0/16:00
*** yamahata has quit IRC16:00
ktibio/16:01
bmaceo/16:01
caoyuano/16:01
pbourkeo/16:01
chasono/16:01
Jeffrey4l#topic announcements16:01
*** openstack changes topic to "announcements (Meeting topic: kolla)"16:01
Jeffrey4lfirst of all, welcome caoyuan to join the core team16:02
sadasuo/16:02
caoyuan:)16:02
caoyuanthanks16:02
duonghqcongratulation caoyuan16:02
spsurya__grats caoyuan16:02
ktibicongrats ;)16:02
caoyuanthanks :) guys16:02
portdirecto/16:03
Jeffrey4lsecond, kolla rc2 is tagged. and kolla 6.0.0 tag will be released soon.16:03
Jeffrey4lany announcements from community?16:03
Jeffrey4l#topic ptg summary bp16:04
*** openstack changes topic to "ptg summary bp (Meeting topic: kolla)"16:04
Jeffrey4l#link https://etherpad.openstack.org/p/kolla-rocky-ptg-recap16:04
Jeffrey4lthanks pbourke for preparing the summary.16:04
Jeffrey4lwe need convert them to bp.16:04
Jeffrey4lplease open the link.16:04
Jeffrey4land add proper bp for them, if the pb already exists, please just add the link.16:05
pbourkea handful have already started bps16:05
pbourkewill add links now16:05
Jeffrey4lwe will be after 10 min16:06
*** yankcrime has joined #openstack-meeting-416:06
Jeffrey4lif anyone is interested in any bp, please assign it to yourself.16:06
sadasuI am working on 3rd party vendor plugins for Neutron16:07
*** mjturek has joined #openstack-meeting-416:07
Jeffrey4lcool.16:07
sadasuthat approach could be used for plugins that are currently in tree and are planning to be split out16:07
sadasuand I understand the issue that Sam Betts brought up during the PTG16:08
sadasudoes a BP already exist for this?16:09
Jeffrey4lsadasu, could you write a spec or POC to explain what the issue and how to solve it?16:09
sadasuJeffrey41: yes, if non already exists, I would be happy to start a new spec16:09
Jeffrey4liirc, there is no such a bp16:10
*** mjturek has quit IRC16:10
sadasuI also have some initial changes out in https://review.openstack.org/#/c/552119/16:10
sadasulet me first create a spec and then link this review to that16:11
sadasuthanks to caoyuan for providing comments on the review16:12
caoyuansadasu you are welcome:)16:12
*** dougsz has joined #openstack-meeting-416:13
yankcrimeregarding backups, i've added the link in to the existing bp for mariadb backup and recovery16:15
Jeffrey4lyankcrime, thanks.16:16
Jeffrey4ltime is up. thanks all guys.16:16
Jeffrey4lplease feel free to take the pbs.16:16
*** Guest17101 has quit IRC16:16
Jeffrey4land if you have any concern, please throw it out in meeting or ML.16:17
Jeffrey4lanythink wanna be talked for the pb now?16:17
Jeffrey4lguess no16:18
Jeffrey4llet us move on16:18
pbourkepb?16:18
Jeffrey4lyes.16:18
pbourkewhat is that?16:18
Jeffrey4lany bluesprint in the etherpad you wannt to talk here, now?16:19
*** caoyuan_ has joined #openstack-meeting-416:19
mgoddardJeffrey4l: you mean bp (not pb)?16:19
Jeffrey4lhrm, sorry, my bad16:20
pbourkeah right16:20
pbourkeone thing16:20
pbourkesometimes there's confusion on who can set those to approved16:20
pbourkecould you clarify Jeffrey4l ?16:20
*** caoyuan has quit IRC16:20
spsurya__Jeffrey4l: I would be working on rolling upgrade for few of core Services and I would assign the same16:21
pbourkeI think its anyone in the kolla launchpad group, but Im not sure what makes a bp eligble for approval16:21
Jeffrey4lnormally, another core member, who is not the drafer,  could.16:21
pbourkeok16:21
Jeffrey4lwe are not that strict on this.16:21
pbourkegood enough for me :)16:21
Jeffrey4lin other team, a spec and a roll-voting is required.16:22
Jeffrey4land we only do this for big change.16:22
Jeffrey4lspsurya__, cool, thanks.16:22
ktibiI can see a lot of bp have old series version. Maybe try to clean bp ?16:22
Jeffrey4lktibi, yep. we need update them.16:23
duonghqspsurya__, thanks, I'll update the current status, I also working on Heat locally16:23
caoyuan_spsurya__ cool and the other's rolling upgrade I glad to complete16:23
spsurya__duonghq: caoyuan_ roger16:24
*** mjturek has joined #openstack-meeting-416:24
Jeffrey4lfeel free to re-target the bp status and series.16:25
Jeffrey4lok. let us move on16:25
Jeffrey4l#topic kolla-kubernetes project split16:25
*** openstack changes topic to "kolla-kubernetes project split (Meeting topic: kolla)"16:25
duonghqcaoyuan_, spsurya__ Glance ps is finished, can you test with me?16:25
Jeffrey4lthis is still WIP16:25
Jeffrey4l#link https://review.openstack.org/55253116:25
Jeffrey4li think we guys are agree on that split the kk8s project.16:26
caoyuan_duonghq my pleasure16:26
portdirectare any kolla-k8s cores here?16:26
spsurya__duonghq: sure, we can discuss in opendiscussion16:26
Jeffrey4lportdirect, anything you wanna to update now?16:26
Jeffrey4lportdirect, tbh, the former active contributor are not here.16:26
pbourkei just read portdirect's comment and I think it makes sense16:26
portdirect:(16:27
Jeffrey4li checked the code of kolla-k8s and osh ( shamed on me that i never tried them), i am agree with the former kk8s active contributor,16:27
pbourkeportdirect: usually agreement is a good thing ;)16:28
Jeffrey4lthe microservice is a good arch than only one charts.16:28
portdirectAs someone who used to be active in the project I'm just worried that it would be confusing, and potentially damaging, to 'launch' a project that from the outset does not have a path towards sustainability.16:28
Jeffrey4lportdirect, it is hard to upgrade the openstack through only one charts for nova.16:29
portdirectI contest that :)16:29
Jeffrey4lportdirect, spsurya__ and i will start contribute this project16:29
Jeffrey4land we will also try to find other volunteers16:29
spsurya__Jeffrey4l: IIRC rwellum is also in16:30
portdirectalso osh supports the same architecture as kolla-k8s if desired: https://github.com/openstack/openstack-helm/blob/master/nova/values.yaml#L1594-L163916:30
Jeffrey4lyeap16:30
pbourkewhy not just contribute to osh16:30
spsurya__Jeffrey4l: duonghq has also shown interest at a time don't know at the moment16:31
portdirectI dont want to cause to much issues - but its worth noting that osh has three large orgs in or close to prod16:31
Jeffrey4lhrm, i see, interesting,16:31
portdirectand for them, upgrade was the primary attraction16:31
Jeffrey4lpbourke, it is mainly concern with arch or deploy philosophy16:31
pbourkeI imagine those issues could be worked out with osh16:32
pbourkeassuming they even are issues from an end user perspective16:32
portdirectJeffrey4l: would it help if i produced a demo of OSH run as micro-charts?16:32
Jeffrey4li think i get your idea.16:32
Jeffrey4luse variables to control which chart is loaded in heml16:33
Jeffrey4lhelm*16:33
portdirectyup16:33
Jeffrey4li missed that when i review the code.16:33
portdirectthis provides the exact same flexibility as the kolla-k8s deployment method16:33
portdirectwhere each object can be addressed individually16:34
Jeffrey4lthere is another thing i concern.16:34
*** diman has joined #openstack-meeting-416:34
Jeffrey4lhow helm load the *.yml? any possible order?16:35
portdirectas in the templates?16:35
Jeffrey4lyes.16:35
portdirectit uses a semi-deterministic order16:36
*** egonzalez has joined #openstack-meeting-416:36
portdirectwhich is controlled through one of two methods16:36
Jeffrey4lokay, i will check that16:37
portdirectwe use dependency/environment checking extensivly: https://github.com/openstack/openstack-helm/blob/master/nova/values.yaml#L205-L21916:37
Jeffrey4lroger thanks16:38
portdirector you can take control of the manifest deployment via toggling them in the over-rides in a playbook16:38
Jeffrey4lunderstand.16:38
portdirect*via a playbook16:38
Jeffrey4lat least for microservice, osh and kk8s are almost the them.16:38
*** diman has quit IRC16:39
Jeffrey4lmybe i need dig these two projects more later.16:39
portdirectwe choose a different `default path` but you can drive them in veritually the same way if desired16:39
portdirectits also worth noting that with osh - we fully support both Kolla and LOCI images16:40
portdirecttaking the same path that Kolla-Ansible is now exploring for bind mounting in the config and scripts16:41
Jeffrey4lgot.16:41
portdirectthanks16:43
portdirect:)16:43
Jeffrey4li am agree now that we should and may be co-operation. but we still need some time before make the decision. ;D16:43
portdirect++16:43
Jeffrey4lthanks portdirect16:44
Jeffrey4lanything else about kk8s and osh?16:44
*** paken has quit IRC16:44
Jeffrey4llet us move on16:44
Jeffrey4l#topic  Documentation RST convention upgrade16:44
*** openstack changes topic to "Documentation RST convention upgrade (Meeting topic: kolla)"16:44
Jeffrey4lchason, your floor16:45
Jeffrey4lseem he is not here.16:46
Jeffrey4l#link https://review.openstack.org/#/q/status:open+project:openstack/kolla-ansible+branch:master+topic:bp/optimize-the-documentation-format16:46
Jeffrey4lthis is a legecy patch in fact.16:46
*** mjturek has quit IRC16:46
Jeffrey4lthere some syntax or convention issue in doc16:46
spsurya__https://review.openstack.org/#/c/538220/16:46
Jeffrey4lfeel free to review them16:46
Jeffrey4lthanks16:46
*** mjturek has joined #openstack-meeting-416:46
*** lyan has joined #openstack-meeting-416:47
Jeffrey4l#topic Open Discussion16:47
*** openstack changes topic to "Open Discussion (Meeting topic: kolla)"16:47
*** lyan is now known as Guest9089316:47
Jeffrey4lany volunteers?16:47
*** VW has quit IRC16:47
bmaceif we have time i wouldn't mind getting any feedback on my email to the mailing list regarding upstreaming the kollacli16:48
bmaceand putting it under kolla management16:48
*** VW has joined #openstack-meeting-416:48
*** paken has joined #openstack-meeting-416:48
*** paken has quit IRC16:48
pbourkeim good with it but a little biased obviously ;)16:49
Jeffrey4lwe can create a new repo for it.16:49
pbourkedo we need a spec?16:49
spsurya__duonghq: i can help in test and also would like add script for nova rolling upgrade16:49
pbourkewould like people to be in agreement with the overall way it works before importing it16:50
bmacewell, since it is already sort of fully implemented and i linked the docs in the email to the mailing list, i'm not sure what extra a spec would provide.16:50
mgoddardwould be nice to see a spec for the cli, but clearly an implementation exists so how much will you be willing to change?16:50
duonghqspsurya__, nice, thank you very much16:50
bmacei am fine with it changing in whatever ways the community wants, that is the whole point of doing the upstream :)16:50
bmacemgoddard ^^16:51
mgoddardanother approach could be - import existing as a pre 1.0 release, with the proviso that anything may change before 1.016:51
duonghqhope that we can finished 1st version for rolling upgrade of all core services, it will need extensive test16:51
pbourkemgoddard: seems a good idea16:51
Jeffrey4lhow about move the project into openstack project namespace, then if there is anything not properly, we can improve it through a spec16:51
bmacemgoddard: that is fine with me as well... consider the cli pre-release until a point that the community is happy with it.16:52
*** mjturek has quit IRC16:52
spsurya__duonghq:  will learn in advance way to test for glance probably tomorrow16:52
duonghqspsurya__,  nice16:52
mgoddardon the question of a new repo vs. in kolla-ansible - how closely tied is it to the inventory, config, playbooks etc.?16:52
*** mjturek has joined #openstack-meeting-416:53
pbourkebmace: people may be more likely to read a spec rather than trawl the oracle docs16:53
spsurya__we also need to optimize the solution of zedro downtime of ks16:53
pbourkeprob not a big deal though16:53
pbourkemost seem in favor so16:53
bmacemgoddard: internally we have a totally separate repository for the cli, so having it broken out is fine, but for the cli to be actually usable, it does rely on bits from kolla-ansible, like the passwords, playbooks, inventory, etc.16:53
*** mjturek has quit IRC16:53
Jeffrey4lpbourke, the issue is we can not wait until the spec is merged.16:53
mgoddardif the cli is in a separate repo, then does the playbook 'interface' need to become stable?16:53
*** mjturek has joined #openstack-meeting-416:54
Jeffrey4lfor ansible playbooks, the interface is more like "inventory" file or "globals.yml"16:55
bmacemgoddard: a problem with the separate repo is that conceptually a change in kolla-ansible could break the cli, though in our experience it would need to be a pretty big change and that issue happens very rarely16:55
pbourkewell I guess we'll have tests and gates to prevent that too16:55
Jeffrey4lbmace, we can add cross-project jobs to ensure this.16:55
bmacemgoddard: i think in the long run that could be covered by the introduction of some sort of co-dependent tests.16:56
bmaceJeffrey4l: exactly my thought, right16:56
Jeffrey4lafter the kolla-cli, we can use it in kolla-ansible jobs to genreate the inventory or global.syml file.s16:56
mgoddardit probably shouldn't come up often, but it just means we can't do something like rename site.yml to somethingelse.yml16:56
pbourkeall that can be configurable16:57
Jeffrey4lmgoddard, once that done, jobs failed and we could fix kolla-cli at the same time.16:57
bmacemgoddard: right, some sort of thought of the effect on the cli needs to be kept in mind, which i think is  good all around, because some people use it already without a cli and might do scripts of their own and similar changes could break those people also.16:57
mgoddardthat's true16:58
Jeffrey4llet us start by separate repo. once it is not  proper in the future, we can still merge two repo into one16:58
Jeffrey4lthis is not a big deal.16:58
bmaceJeffrey4l: that sounds great.  starting with it broken out, as it is internally for us, should also make the transition easier.16:58
Jeffrey4lyeah.16:59
Jeffrey4lok time is up. let us move to kolla channel16:59
bmaceis there any way that i can be a core for just the cli?  i'm not sure how it was for the kolla-k8s stuff, i think something was done similar?  if not that is fine.. i just know i have a bit of outstanding work to do on it and will just need to get other folks to review it :)16:59
caoyuan_ok16:59
Jeffrey4lthanks guys for coming.16:59
bmacekk16:59
duonghqthanks17:00
Jeffrey4l#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"17:00
openstackMeeting ended Wed Mar 21 17:00:08 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kolla/2018/kolla.2018-03-21-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2018/kolla.2018-03-21-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2018/kolla.2018-03-21-16.00.log.html17:00
*** mgoddard has left #openstack-meeting-417:00
*** bmace has left #openstack-meeting-417:00
*** yankcrime has left #openstack-meeting-417:00
*** egonzalez has quit IRC17:01
*** sadasu has left #openstack-meeting-417:01
*** bradjones has quit IRC17:03
*** paken has joined #openstack-meeting-417:05
*** salmankhan has quit IRC17:08
*** caoyuan_ has quit IRC17:09
*** duonghq has quit IRC17:10
*** salmankhan has joined #openstack-meeting-417:12
*** paken has quit IRC17:17
*** pbourke has quit IRC17:27
*** diman has joined #openstack-meeting-417:30
*** lpetrut_ has quit IRC17:32
*** diman has quit IRC17:34
*** aniketh has quit IRC17:37
*** aniketh has joined #openstack-meeting-417:37
*** toan has quit IRC17:37
*** icey has quit IRC17:37
*** v1k0d3n has quit IRC17:38
*** gmann_ has quit IRC17:38
*** gmann_ has joined #openstack-meeting-417:40
*** icey has joined #openstack-meeting-417:40
*** v1k0d3n has joined #openstack-meeting-417:40
*** toan has joined #openstack-meeting-417:41
*** haleyb has quit IRC17:56
*** dougsz has quit IRC17:58
*** sambetts is now known as sambetts|afk18:00
*** VW_ has joined #openstack-meeting-418:05
*** VW_ has quit IRC18:05
*** VW_ has joined #openstack-meeting-418:06
*** VW has quit IRC18:08
*** VW_ has quit IRC18:13
*** VW has joined #openstack-meeting-418:13
*** lpetrut has joined #openstack-meeting-418:20
*** EmilienM is now known as mimi18:21
*** mimi is now known as EmilienM18:21
*** gcheresh_ has joined #openstack-meeting-418:21
*** harlowja has joined #openstack-meeting-418:24
*** paken has joined #openstack-meeting-418:26
*** diman has joined #openstack-meeting-418:26
*** haleyb has joined #openstack-meeting-418:30
*** diman has quit IRC18:31
*** yamamoto has quit IRC18:43
*** paken has quit IRC18:47
*** lpetrut has quit IRC18:51
*** lpetrut has joined #openstack-meeting-419:00
*** salmankhan has quit IRC19:06
*** diman has joined #openstack-meeting-419:09
*** paken has joined #openstack-meeting-419:11
*** paken has quit IRC19:12
*** seajay has quit IRC19:16
*** seajay has joined #openstack-meeting-419:17
*** seajay has quit IRC19:20
*** salv-orlando has quit IRC19:34
*** salv-orlando has joined #openstack-meeting-419:35
*** radeks_ has joined #openstack-meeting-419:36
*** diman has quit IRC19:38
*** radeks has quit IRC19:38
*** salv-orlando has quit IRC19:38
*** radeks_ has quit IRC19:42
*** paken has joined #openstack-meeting-419:42
*** radeks_ has joined #openstack-meeting-419:43
*** yamamoto has joined #openstack-meeting-419:44
*** salv-orlando has joined #openstack-meeting-419:44
*** yamamoto has quit IRC19:49
*** VW has quit IRC19:54
*** VW has joined #openstack-meeting-419:54
*** radeks_ has quit IRC20:07
*** radeks_ has joined #openstack-meeting-420:11
*** yboaron has joined #openstack-meeting-420:21
*** salv-orlando has quit IRC20:32
*** seajay has joined #openstack-meeting-420:37
*** paken has quit IRC20:39
*** yamamoto has joined #openstack-meeting-420:45
*** paken has joined #openstack-meeting-420:46
*** zhubingbing has joined #openstack-meeting-420:47
*** seajay has quit IRC20:48
*** paken has joined #openstack-meeting-420:48
*** radeks_ has quit IRC20:48
*** yamamoto has quit IRC20:51
*** zhubingbing has quit IRC20:51
*** bnemec is now known as sin-master21:12
*** sin-master is now known as bnemec21:12
*** VW has quit IRC21:13
*** paken has quit IRC21:19
*** paken has joined #openstack-meeting-421:25
*** ktibi has quit IRC21:27
*** salv-orlando has joined #openstack-meeting-421:32
*** paken has quit IRC21:37
*** salv-orlando has quit IRC21:38
*** gcheresh_ has quit IRC21:40
*** yamamoto has joined #openstack-meeting-421:47
*** yamamoto has quit IRC21:53
*** pcaruana has quit IRC21:55
*** salv-orlando has joined #openstack-meeting-421:59
*** JamesBenson has quit IRC22:05
*** lpetrut has quit IRC22:22
*** yamahata has joined #openstack-meeting-422:24
*** yboaron has quit IRC22:28
*** bobh has quit IRC22:30
*** d0ugal has quit IRC22:34
*** d0ugal has joined #openstack-meeting-422:37
*** iyamahat has joined #openstack-meeting-422:49
*** yamamoto has joined #openstack-meeting-422:49
*** hongbin has quit IRC22:50
*** pmesserli has quit IRC22:54
*** yamamoto has quit IRC22:54
*** aniketh has quit IRC23:11
*** salv-orlando has quit IRC23:26
*** salv-orlando has joined #openstack-meeting-423:26
*** salv-orlando has quit IRC23:30
*** chyka has quit IRC23:39
*** Adri2000 has quit IRC23:40
*** Adri2000 has joined #openstack-meeting-423:41
*** yamamoto has joined #openstack-meeting-423:51
*** yamamoto has quit IRC23:55

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