Wednesday, 2017-12-20

*** salv-orlando has quit IRC00:05
*** salv-orlando has joined #openstack-meeting-400:05
*** pmesserli has quit IRC00:06
*** salv-orlando has quit IRC00:11
*** yifei has joined #openstack-meeting-400:16
*** yifei has left #openstack-meeting-400:17
*** bobh has joined #openstack-meeting-400:32
*** dave-mccowan has quit IRC00:35
*** armstrong has quit IRC00:48
*** tuanla____ has joined #openstack-meeting-400:54
*** bobh has quit IRC00:56
*** kiennt26 has joined #openstack-meeting-400:56
*** VW has joined #openstack-meeting-400:59
*** salv-orlando has joined #openstack-meeting-401:06
*** salv-orlando has quit IRC01:11
*** dave-mccowan has joined #openstack-meeting-401:12
*** yamamoto has joined #openstack-meeting-401:21
*** yamamoto has quit IRC01:21
*** psachin has joined #openstack-meeting-401:24
*** psachin has quit IRC01:28
*** psachin has joined #openstack-meeting-401:32
*** yamahata has quit IRC01:38
*** yamahata has joined #openstack-meeting-401:39
*** makowals has quit IRC01:43
*** makowals has joined #openstack-meeting-401:44
*** edleafe- has joined #openstack-meeting-401:57
*** edleafe has quit IRC01:57
*** yamamoto has joined #openstack-meeting-401:57
*** seajay has joined #openstack-meeting-402:03
*** iyamahat has quit IRC02:03
*** iyamahat has joined #openstack-meeting-402:03
*** salv-orlando has joined #openstack-meeting-402:07
*** salv-orlando has quit IRC02:11
*** karthiks has joined #openstack-meeting-402:16
*** VW has quit IRC02:32
*** bobh has joined #openstack-meeting-402:34
*** seajay has quit IRC02:43
*** unicell has quit IRC02:45
*** bobh has quit IRC02:51
*** bobh has joined #openstack-meeting-402:52
*** gmann has quit IRC02:55
*** bobh has quit IRC03:06
*** salv-orlando has joined #openstack-meeting-403:07
*** yamahata has quit IRC03:11
*** iyamahat has quit IRC03:12
*** salv-orlando has quit IRC03:12
*** bobh has joined #openstack-meeting-403:13
*** dave-mccowan has quit IRC03:13
*** karthiks has quit IRC03:23
*** janonymous has joined #openstack-meeting-403:25
*** tinwood has quit IRC03:30
*** tinwood has joined #openstack-meeting-403:31
*** slaweq has joined #openstack-meeting-403:49
*** slaweq has quit IRC03:54
*** zhurong has joined #openstack-meeting-403:58
*** yamamoto_ has joined #openstack-meeting-404:08
*** salv-orlando has joined #openstack-meeting-404:08
*** yamamoto has quit IRC04:11
*** salv-orlando has quit IRC04:13
*** iyamahat has joined #openstack-meeting-404:25
*** iyamahat has quit IRC04:35
*** iyamahat has joined #openstack-meeting-404:39
*** VW has joined #openstack-meeting-404:42
*** bobh has quit IRC04:48
*** links has joined #openstack-meeting-404:57
*** VW has quit IRC05:05
*** slaweq has joined #openstack-meeting-405:05
*** salv-orlando has joined #openstack-meeting-405:09
*** slaweq has quit IRC05:09
*** yamamoto_ has quit IRC05:10
*** salv-orlando has quit IRC05:15
*** coolsvap has joined #openstack-meeting-405:20
*** yboaron has joined #openstack-meeting-405:21
*** VW has joined #openstack-meeting-405:25
*** yamamoto has joined #openstack-meeting-405:32
*** VW has quit IRC06:06
*** salv-orlando has joined #openstack-meeting-406:10
*** MinWookKim has joined #openstack-meeting-406:10
*** salv-orlando has quit IRC06:15
*** d0ugal has quit IRC06:17
*** gcheresh_ has joined #openstack-meeting-406:18
*** yifei has joined #openstack-meeting-406:19
*** d0ugal has joined #openstack-meeting-406:23
*** salv-orlando has joined #openstack-meeting-406:28
*** VW has joined #openstack-meeting-406:30
*** VW has quit IRC06:34
*** trungnv has joined #openstack-meeting-406:39
*** unicell has joined #openstack-meeting-406:40
*** yamamoto has quit IRC06:49
*** karthiks has joined #openstack-meeting-406:49
*** janki has joined #openstack-meeting-406:49
*** karthiks has quit IRC06:54
*** yamamoto has joined #openstack-meeting-407:04
*** gcheresh_ has quit IRC07:06
*** karthiks has joined #openstack-meeting-407:06
*** yamamoto has quit IRC07:09
*** yifei has quit IRC07:11
*** yamamoto has joined #openstack-meeting-407:20
*** gcheresh_ has joined #openstack-meeting-407:20
*** yamamoto has quit IRC07:24
*** gcheresh_ has quit IRC07:25
*** yifei has joined #openstack-meeting-407:30
*** kiennt26 has quit IRC07:35
*** iyamahat has quit IRC07:42
*** slaweq has joined #openstack-meeting-407:45
*** gcheresh_ has joined #openstack-meeting-407:48
*** iyamahat has joined #openstack-meeting-407:49
*** iyamahat has quit IRC07:50
*** Liat has joined #openstack-meeting-407:55
LiatGood Morning07:56
Liat07:56
LiatHi07:56
*** iyamahat has joined #openstack-meeting-407:57
*** ifat_afek has joined #openstack-meeting-407:59
ifat_afek#startmeeting vitrage08:00
openstackMeeting started Wed Dec 20 08:00:20 2017 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:-)08:00
*** dwj has joined #openstack-meeting-408:00
ifat_afekdwj: Hi, it seems like it’s just us today… we are only two people from Nokia (there is a holiday in Israel so many people are on vacation)08:04
*** yamamoto has joined #openstack-meeting-408:04
ifat_afekDo you have anythink you want to discuss? I prepared a meeting agenda, but I’m not sure if we should hold the meeting at all08:05
*** yujunz has joined #openstack-meeting-408:05
dwjYujunz also here. :)08:05
yujunzhi08:05
ifat_afekyujunz: Hi! so now we are four people :-)08:05
*** peipei has joined #openstack-meeting-408:05
ifat_afekSo I’ll start08:06
ifat_afek#topic Status and Updates08:06
*** openstack changes topic to "Status and Updates (Meeting topic: vitrage)"08:06
ifat_afekMy updated: I am still working on the execute-mistral refactoring… I was on vacation in the beginning of this week, but I really hope to push my change today08:07
ifat_afekMy change will include: support for per-version validation and loading of the templates + refactoring of the execute-mistral syntax08:07
ifat_afekMost of the change is around the version support08:07
ifat_afekThat’s it for me08:08
*** iyamahat has quit IRC08:08
yujunzMy updates.08:08
yujunzDraft a blueprint about suspect alarm08:08
yujunz#link https://review.openstack.org/#/c/519250/08:08
yujunzAnd fixed some document building issues.08:08
ifat_afekI’ve seen the suspect alarm blueprint. I still want to think over about the suspect state and how to represent it. And I’d like eyalb and idan_hefetz to review it as well, but they are on vacation08:09
*** yamamoto has quit IRC08:09
ifat_afekAnd thanks for the document fixes. Are they all related to the latest doc-build change?08:10
yujunzThe latest two are addressing the new build job08:10
yujunzTo keep the local build job consistent with openstack infra08:11
ifat_afekGreat, thanks. I actually didn’t understand that there was a need for us to do anything08:11
yujunzNo, we don't need to do it to make the build job work. It just help when the build job fails and you want to troubleshoot it locally.08:12
ifat_afekThat’s also a good idea :-)08:12
yujunzThe other two are encountered by myself while drafting the suspect alarm blueprint.08:13
yujunzSo I spent a few minutes to fix them.08:13
ifat_afekThanks08:13
yujunzNext I will validate the proactive fault model against some common use cases.08:14
ifat_afekSounds good. Will it belong to one of the blueprints?08:14
yujunzHard to decide where to put them. Maybe the outcome would be a design document in vitrage/docs, not a blueprint in vitrage-specs08:15
ifat_afekThat could also work. We have a few of those already08:15
yujunzThat's all from me08:16
dwjMy update: I start to do the task: support Vitrage in Apex(TripleO),  and I send email to apex team to ask the progress/plan as they have an assignee to take over the integration task in April, but no response yet.08:16
dwjIn parallel, I start to learn how to integrate with TripleO. So complex,maybe we need to add some modification in several repos.such as: puppet-triplo, tripleo-heat-template, tripleo-puppet-elements and so on08:17
*** zhurong has quit IRC08:17
dwjI haven't clear up the whole workflow......08:18
ifat_afekThanks for taking these tasks. Are they related to one another? I somehow understood that we could do the TripleO first and then Apex should be easy. But I’m not sure that I understood correctly08:18
ifat_afekAnd I don’t think that there is someone else in our team that knows more about these installations08:18
*** tuanla____ has quit IRC08:18
*** hieulq has quit IRC08:18
dwjYes, Apex use the repos from TripleO, so we need to do the TripleO first08:19
*** tuanla____ has joined #openstack-meeting-408:19
*** hieulq has joined #openstack-meeting-408:19
ifat_afekNote that we already have Vitrage rpms in RDO. I’m not sure if it’s related, but maybe…08:20
dwjYes, it's related.08:20
ifat_afekOk, seems like by now you know a lot more than me about this issue :-)08:21
dwjAs we have Vitrage rpms in RDO, we can start to do the deploy.08:21
dwjNot so much. :)08:21
ifat_afekAnd that’s a lot of work?08:21
*** salv-orlando has quit IRC08:22
dwjSeems like that because I don't familiar with TripleO. - _ -08:23
*** iyamahat has joined #openstack-meeting-408:23
ifat_afekOk. Let us know if you need any help. Unfortunately none of us is familiar with TripleO08:24
dwjOK, thanks~08:24
ifat_afekAny other updates by anyone?08:25
*** alexchadin has joined #openstack-meeting-408:26
ifat_afek#topic Queens releaes08:27
*** openstack changes topic to "Queens releaes (Meeting topic: vitrage)"08:27
ifat_afek#topic Queens Release08:27
*** openstack changes topic to "Queens Release (Meeting topic: vitrage)"08:27
ifat_afekA reminder about the Queens release timeframe:08:27
ifat_afekThe release deadline for python-vitrageclient: January 2508:28
*** yifei has quit IRC08:28
ifat_afekThis week is also declared as the “feature freeze”, although we are not committed to it (as we are following the cycle-with-intermediary release model).08:28
ifat_afekThe release candidate deadline is February 5-908:28
ifat_afekHere is the etherpad with our roadmap:08:28
ifat_afek#link https://etherpad.openstack.org/p/vitrage-ptg-queens08:28
*** yifei has joined #openstack-meeting-408:29
ifat_afekA few updates in the etherpad:08:29
ifat_afek(Must) Move tempests tests to a separate repository - in progress by chandankumar08:29
ifat_afek(Must) Support Networkx 2.0 - I need to email openstack-dev and check if it really is a must. Depends whether they plan to chagne networkx version in the global requirements08:30
ifat_afek(Very Important) Make sure all existing tests run in the gate - I believe this is done, but need to check with idan_hefetz08:31
ifat_afek(Very important) Configurable notifications API  - the task has moved to nivo, and it’s in progress08:31
ifat_afek(Very Important) HA - Muhamad Najjar already implemented the event persistor, and he is now working on persisting the graph snapshots08:32
ifat_afekSo it’s also in progress08:32
ifat_afek(Medium) Template CRUD08:33
ifat_afeknice progress by idan_kinory08:33
ifat_afekAnd latest news - the Congress PTL, Eric Kao, emailed me regarding the Vitrage-Congress integration. He seems to be interested in pushing this forward08:34
ifat_afekThat’s it on my side, I’ll now update the etherpad itself08:34
*** yamamoto has joined #openstack-meeting-408:34
yujunzI have updated the etherpad. Put a brief record in IRC as well08:34
yujunz[pending] Template simplification08:35
yujunz[in progress] Suspect status08:35
yujunz[not started] Diagnostic action08:35
yujunz[pending] Equivalence and aggregation08:35
yujunzSo we get started with suspect status08:36
yujunzThe two pending items has already a draft blueprint08:36
yujunzWill update after we validate the common use cases08:36
yujunzThat's it on my side.08:36
ifat_afekOk. So I think that for Nokia’s task we are in good state. The only thing that I’m not 100% sure about is the HA. But I believe it can be done for Queens.08:38
ifat_afekAnother issue related to the release: the TC introduced the concept of “release highlights”.08:39
ifat_afekIn every version that we release we should write, in addition to the release notes, some short highlights about the version.08:39
ifat_afekI plan to check what other teams are writing and then we should decide about our own highlights.08:39
ifat_afek#link http://lists.openstack.org/pipermail/openstack-dev/2017-December/125613.html08:39
*** yamamoto has quit IRC08:39
yujunz#info Cycle highlights: Journalists, product manager, and others08:40
yujunzIs it about this?08:40
ifat_afekCould be… where did you copy it from?08:40
yujunzFrom your link :-)08:41
ifat_afekThe idea is that “PTLs will not be asked over and over again about the cycle highlights”08:41
ifat_afek:-)08:41
ifat_afekI don’t fully understand what’s the difference betewwn the highlights and the release notes08:41
ifat_afekSo I’m waiting to see what others are doing08:41
yujunz#info Release notes:    End user and deployer documentatio08:42
yujunzThe audience is a bit different08:42
yujunzHighlights is more for marketing08:42
ifat_afekSo we need to consult a marketing person about the content ;-)08:42
ifat_afekLast issue: I believe that most IRC meetings will be canceled next week due to the holidays. In Israel we are working as usual, so we can either hold the meeting or cancel it like anyone else. What do you say?08:44
yujunzWe have a team building next Wednesday08:45
ifat_afekWhat does it mean?08:45
yujunzdwj and me won't be available for the meeting08:45
ifat_afekOk, so let’s cancel it. I’ll send an email about it08:45
ifat_afek#topic Open Discussion08:47
*** openstack changes topic to "Open Discussion (Meeting topic: vitrage)"08:47
ifat_afekAnything else?08:47
yujunzIs the PTG schedule settled?08:47
ifat_afekI didn’t even prepare an etherpad yet, because it’s only in February… I can create one so people can start writing their ideas08:48
yujunzAnd people? How many from vitrage team plan to attend?08:49
ifat_afekOk, so here is the link:08:49
ifat_afek#link https://etherpad.openstack.org/p/vitrage-ptg-rocky08:49
ifat_afekIt’s still empty, I’ll write a few lines08:49
*** slaweq_ has joined #openstack-meeting-408:49
*** yamamoto has joined #openstack-meeting-408:50
ifat_afekFrom Nokia it seems like only Yuval Adar will travel to Dublin, and the rest of us will join remotely08:50
yujunzOK, I see. Thanks.08:50
ifat_afekWe’ll adjust the schedule so it will match Shaghai time as much as possible. Israel time is similar so that’s not an issue08:50
ifat_afekI asked for a room for 3 days, so we’ll have 3 mornings for meetings with Shanghai. I’m not sure if we need 3 full days08:51
ifat_afekAny other issue?08:53
yujunzNope08:53
dwjNo08:53
ifat_afekOk, bye then :-)08:53
dwjbye~08:53
yujunzbye08:53
ifat_afek#endmeeting08:54
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:54
openstackMeeting ended Wed Dec 20 08:54:02 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vitrage/2017/vitrage.2017-12-20-08.00.html08:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2017/vitrage.2017-12-20-08.00.txt08:54
openstackLog:            http://eavesdrop.openstack.org/meetings/vitrage/2017/vitrage.2017-12-20-08.00.log.html08:54
Liatbye08:54
*** Liat has quit IRC08:54
*** yamamoto has quit IRC08:54
*** slaweq_ has quit IRC08:54
*** yamamoto has joined #openstack-meeting-408:56
*** yamamoto has quit IRC08:56
*** salv-orlando has joined #openstack-meeting-408:57
*** anilvenkata has joined #openstack-meeting-408:58
*** dwj has quit IRC08:58
*** sbezverk has quit IRC09:02
*** alexchadin has quit IRC09:04
*** gcheresh_ has quit IRC09:04
*** alexchadin has joined #openstack-meeting-409:04
*** yamamoto has joined #openstack-meeting-409:05
*** yujunz has quit IRC09:09
*** yujunz has joined #openstack-meeting-409:14
*** slaweq_ has joined #openstack-meeting-409:20
*** yboaron has quit IRC09:24
*** yboaron has joined #openstack-meeting-409:24
*** slaweq_ has quit IRC09:25
*** anilvenkata has quit IRC09:28
*** anilvenkata has joined #openstack-meeting-409:29
*** yujunz has quit IRC09:32
*** arcolife has joined #openstack-meeting-409:36
*** iyamahat has quit IRC09:40
*** psachin has quit IRC10:01
*** psachin has joined #openstack-meeting-410:10
*** bcafarel has quit IRC10:15
*** armstrong has joined #openstack-meeting-410:15
*** psachin has quit IRC10:20
*** salmankhan has joined #openstack-meeting-410:26
*** sambetts|afk is now known as sambetts10:27
*** aarefiev has joined #openstack-meeting-410:30
*** ifat_afek has quit IRC10:34
*** gcheresh_ has joined #openstack-meeting-410:39
*** gcheresh_ has quit IRC10:40
*** alexchadin has quit IRC10:41
*** alexchadin has joined #openstack-meeting-410:42
*** bcafarel has joined #openstack-meeting-410:42
*** krtaylor has quit IRC10:53
*** yboaron_ has joined #openstack-meeting-410:59
*** yboaron has quit IRC11:02
*** krtaylor has joined #openstack-meeting-411:06
*** yamamoto_ has joined #openstack-meeting-411:08
*** gcheresh_ has joined #openstack-meeting-411:08
*** yifei has left #openstack-meeting-411:09
*** yamamoto has quit IRC11:11
*** tuanla____ has quit IRC11:14
*** reedip has quit IRC11:21
*** ifat_afek has joined #openstack-meeting-411:27
*** ifat_afek has left #openstack-meeting-411:27
*** caboucha has joined #openstack-meeting-411:30
*** neiljerram has joined #openstack-meeting-411:31
*** alexchadin has quit IRC11:33
*** reedip has joined #openstack-meeting-411:34
*** alexchadin has joined #openstack-meeting-411:39
*** psachin has joined #openstack-meeting-411:39
*** gcheresh_ has quit IRC11:43
*** pbourke has quit IRC11:48
*** alexchadin has quit IRC11:49
*** pbourke has joined #openstack-meeting-411:49
*** gcheresh_ has joined #openstack-meeting-411:50
*** yboaron_ has quit IRC11:50
*** salv-orl_ has joined #openstack-meeting-411:59
*** unicell has quit IRC12:00
*** salv-orlando has quit IRC12:03
*** seajay has joined #openstack-meeting-412:03
*** salmankhan has quit IRC12:04
*** yboaron_ has joined #openstack-meeting-412:04
*** salmankhan has joined #openstack-meeting-412:06
*** dave-mccowan has joined #openstack-meeting-412:14
*** alexchadin has joined #openstack-meeting-412:15
*** aarefiev has quit IRC12:33
*** MinWookKim has quit IRC12:36
*** liuyulong has joined #openstack-meeting-412:43
*** bobh has joined #openstack-meeting-412:45
*** kiennt26 has joined #openstack-meeting-412:53
*** Yumeng__ has joined #openstack-meeting-412:59
alex_xu#startmeeting nova api13:00
openstackMeeting started Wed Dec 20 13:00:19 2017 UTC and is due to finish in 60 minutes.  The chair is alex_xu. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: nova api)"13:00
openstackThe meeting name has been set to 'nova_api'13:00
alex_xuwho is here today?13:00
alex_xuok, looks like no one, let me wait two mins13:01
alex_xuok, let me end the meeting13:03
*** gcheresh_ has quit IRC13:03
alex_xu#endmeetings13:03
alex_xu#endmeeting13:03
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:03
openstackMeeting ended Wed Dec 20 13:03:24 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_api/2017/nova_api.2017-12-20-13.00.html13:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_api/2017/nova_api.2017-12-20-13.00.txt13:03
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_api/2017/nova_api.2017-12-20-13.00.log.html13:03
*** dmellado has quit IRC13:05
*** coolsvap has quit IRC13:05
*** dmellado has joined #openstack-meeting-413:15
*** dmellado has quit IRC13:19
*** dmellado has joined #openstack-meeting-413:21
*** alexchadin has quit IRC13:27
*** bobh has quit IRC13:31
*** yamamoto_ has quit IRC13:34
*** edleafe- is now known as edleafe13:45
*** SerenaFeng has joined #openstack-meeting-413:45
*** kiennt26 has quit IRC13:46
*** psachin has quit IRC13:49
*** pmesserli has joined #openstack-meeting-414:07
*** logan- has quit IRC14:08
*** cleong has joined #openstack-meeting-414:10
*** logan- has joined #openstack-meeting-414:10
*** yamamoto has joined #openstack-meeting-414:10
*** dardelean_ has joined #openstack-meeting-414:13
*** armstrong has quit IRC14:14
*** yamamoto has quit IRC14:23
*** gcheresh_ has joined #openstack-meeting-414:29
*** gcheresh_ has quit IRC14:54
*** bobh has joined #openstack-meeting-415:01
*** SerenaFeng has quit IRC15:05
*** marst has joined #openstack-meeting-415:06
*** SerenaFeng has joined #openstack-meeting-415:07
*** makowals has quit IRC15:08
*** liuyulong has quit IRC15:14
*** Yumeng__ has left #openstack-meeting-415:17
*** yamamoto has joined #openstack-meeting-415:23
*** karthiks has quit IRC15:32
*** yamamoto has quit IRC15:35
*** duonghq has joined #openstack-meeting-415:37
*** trozet has quit IRC15:40
*** slaweq has quit IRC15:43
*** trozet has joined #openstack-meeting-415:43
*** hrw has joined #openstack-meeting-415:44
*** iyamahat has joined #openstack-meeting-415:44
*** iyamahat has quit IRC15:45
*** iyamahat has joined #openstack-meeting-415:45
*** peipei has quit IRC15:47
*** lyan has joined #openstack-meeting-415:47
*** yboaron_ has quit IRC15:49
*** pcaruana has joined #openstack-meeting-415:51
*** coolsvap has joined #openstack-meeting-415:53
*** janki has quit IRC15:53
*** egonzalez90 has joined #openstack-meeting-415:53
*** duonghq has quit IRC15:56
*** duonghq has joined #openstack-meeting-415:56
*** gcheresh_ has joined #openstack-meeting-415:58
*** inc0 has joined #openstack-meeting-415:58
hrwo/15:59
inc0#startmeeting kolla15:59
hrwor today rather /o\15:59
openstackMeeting started Wed Dec 20 15:59:52 2017 UTC and is due to finish in 60 minutes.  The chair is inc0. Information about MeetBot at http://wiki.debian.org/MeetBot.15:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:59
*** openstack changes topic to " (Meeting topic: kolla)"15:59
openstackThe meeting name has been set to 'kolla'15:59
inc0#topic w00t!16:00
*** openstack changes topic to "w00t! (Meeting topic: kolla)"16:00
inc0you know what to do16:00
duonghqwo0t16:00
hrw /o\16:00
egonzalez90Woot16:00
chasonWoot16:00
coolsvapo/16:00
niedbalskio/16:00
Jeffrey4lo/16:00
*** gema has joined #openstack-meeting-416:00
rwellumo/16:00
gemao/16:00
*** premsankar has joined #openstack-meeting-416:01
dardelean_o/16:01
krtaylorw00t16:01
*** peipei has joined #openstack-meeting-416:02
*** barjavel.freenode.net changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:02
dardelean_w00t16:02
inc0#topic announcements16:02
*** openstack changes topic to "announcements (Meeting topic: kolla)"16:02
inc0so, next meeting will be canceled16:02
inc0so merry chrismas, happy hannukah, have a good holiday16:02
inc0any community announcements?16:03
Jeffrey4locata 4.0.3 is finally released at the end of last week16:04
inc0ah so was pike16:04
Jeffrey4land pike 5.0.1 is on the way16:04
inc0right16:04
Jeffrey4lwaiting for review :D16:04
Jeffrey4lthat is all from me.16:05
inc0ok, let's get to agenda, it's fairly busy today16:05
inc0or anyone else have announcement?16:05
inc0guess not:)16:05
inc0#topic Image containers lifecycle: how to differentiate on docker registry between tested/untested images? Staging/stable? (gema)16:05
*** openstack changes topic to "Image containers lifecycle: how to differentiate on docker registry between tested/untested images? Staging/stable? (gema) (Meeting topic: kolla)"16:05
inc0gema shoot16:05
gemainc0: we were discussing today how to handle images lifecycle16:06
gemaif having one copy of them is good, or if we should have them tagged by date16:06
inc0#link https://review.openstack.org/#/c/526469/16:06
inc0check that out16:06
gemaor if we could make them staging until we test them and then promote them to released16:06
hrwnow we have 'queens-YYYYMMDD' tag in use16:06
inc0that's what I came up for now - build => :pike-staging => pull/test => retag to :pike => push16:07
inc0one thing, one image can have multiple tags16:07
gemainc0: ok, we'll look into it16:07
gemainc0: for queens we are going to have to do something similar but with manual testing16:07
gemainc0: thanks16:08
inc0well...once you have nodepool for arm, it'd be super easy to use this mechanism;)16:08
gemainc0: yep16:08
gemainc0: on the topic, I'd like to introduce niedbalski , our new devops lead16:08
gemainc0: he is going to be fixing one of our clouds to be able to add that nodepool :)16:08
inc0o/16:09
gemainc0: and he'll be in dublin with us also16:09
krtaylorhi niedbalski, welcome!16:09
niedbalskikrtaylor, inc0 o/16:09
egonzalez90o/16:09
*** SerenaFeng has quit IRC16:09
niedbalskiegonzalez90, o/16:09
inc0so, gema we also discussed having tag like16:10
inc0pike-12316:10
inc0where 123 is autoincrement16:10
gemainc0: but then how do you know which images are tested and good, vs just built and bad?16:10
inc0so images won't be repulled automatically16:10
inc0well staging can be the same16:10
inc0as I said, one image can have multiple tags16:11
gemaok16:11
gemayou can tag them after testing16:11
rwellumWhy push images that are bad?16:11
gemarwellum: to be able to test them?16:11
inc0so you can have both pike and pike-123 pointing to same image16:11
hrwalso the issue can be when image is not built because of some reason16:11
rwellumWhy test a bad image?16:11
gemarwellum: you don't know is bad until you test it16:11
inc0rwellum: you son't know if it's bad until it's tested16:11
gemarwellum: I don't want my team building all different images they built themselves16:11
rwellumWe should test before pushing16:11
gemathen testing becomes non reproducible16:11
inc0I mean if it fails building, you don't push it obviously16:11
gemarwellum: hrw cannot test everything16:12
gemarwellum: and he is our builder :D16:12
rwellumNah - we add tempest and run basic tests?16:12
inc0rwellum: pushing -staging is just requirement of zuul really - we don't have good way to pass built images between gates16:12
hrwand our CI job is simple: ./tools/build.py --push --some-other-options16:12
*** gcheresh_ has quit IRC16:12
inc0right, change I linked also deploys kolla-ansible16:12
hrwinc0: deploy is another on a list ;D16:13
inc0and have place for different scenarios, so at the end we can have testing of both k-ans and k-k8s in multiple scenarios16:13
gemarwellum: we need to get to a point where we can run tempest on a deployed cloud automatically, we are just not there yet16:13
inc0before pushing16:13
inc0rwellum: what we could use is tempest in our regular gates16:14
inc0after we have job like that we can add it to push pipeline16:14
rwellumRight because to hrw point, CI without testing is not really CI imo.16:14
*** pmesserli has quit IRC16:14
inc0build alone is smoketest16:14
inc0after that you jsut add more testing:)16:15
gemayep16:15
hrwrwellum: now our CI job is my replacement for days when I am under bus ;d16:15
gemarwellum: but I am 100% in agreement16:15
rwellumWow inc0 :)16:15
gemarwellum: it just takes some time to get to a point where tests can be automated without some workaround or another16:15
rwellumI feel it's my mission to prove you wrong there :)16:16
Jeffrey4lhow about just extend our ci, and test the image before pushing them?16:16
gemayou guys are preaching to the converted here :D16:16
inc0Jeffrey4l: review this https://review.openstack.org/#/c/526469/16:16
hrwwe are stage where all possible images can be built (aka those without 3rdparty and x86-only stuff). took far too long to get there but at least something16:16
inc0this is exactly what you asked for:)16:16
gemainc0: I will review that patch also16:17
gemaseems to answer our question exactly16:18
inc0thanks16:18
hrwand we do two new things at once: 1. !x86  2. Debian16:18
Jeffrey4lah, right.16:18
inc0hrw: as I said, when we get arm nodepool16:18
hrwinc0: soon (tm)16:18
inc0we'll just create slew of jobs for arm there and all that work will be applicable16:18
inc0we'll need new tag for you, like pike-arm-staging => pike-arm16:19
inc0but that's fine16:19
inc0easy enough16:19
*** dardelean_ has quit IRC16:19
hrws/arm/aarch64 ;D16:19
rwellumtm = tomorrow hrw ?16:19
gemahrw: missing the point x)16:19
hrwrwellum: haha. I wish16:20
inc0yeah, well, I wouldn't know, not that I work for processor maker...16:20
gemainc0: lol16:20
hrwinc0: then arm64. not arm16:20
inc0anyway, can we move on to AArch64 topic?;)16:20
gemayep16:20
hrwyes16:20
inc0#topic State of deploying on AArch64 (hrw)16:20
*** openstack changes topic to "State of deploying on AArch64 (hrw) (Meeting topic: kolla)"16:20
hrwok16:20
inc0hrw: so what's the state:)16:20
hrwso 1. docker16:20
inc0?16:20
hrwdoes not look good without hacks16:21
hrwhttps://review.openstack.org/#/c/522712/ takes care of 'docker daemon or dockerd' stuff16:21
hrwI really wonder how many people use docker 1.12 (or whichever used 'docker daemon')16:21
inc0but gates are bloody red so we can't merge it...before...wait for it...nodepool!;)16:22
hrwwithout that patch 'bootstrap-servers' crash perfectly working docker-ce installation16:22
hrwinc0: none of your gates run debian. we change debian only16:22
hrwwithout it merged in this form or other we do not have deploy at all16:23
hrwquestions to this part?16:23
*** iyamahat has quit IRC16:24
rwellumWe use docker-ce?16:24
hrwwe do16:24
hrw17.0616:24
Jeffrey4lcould you fix the gate at the same time?16:24
Jeffrey4lhrw, something is broken.16:24
inc0well...1.12/1.13 is what distros carry usually16:24
Jeffrey4lhttp://logs.openstack.org/12/522712/8/check/kolla-ansible-centos-source/8f4125e/primary/ansible/bootstrap-servers16:24
inc0http://logs.openstack.org/12/522712/8/check/kolla-ansible-centos-source/8f4125e/primary/ansible/bootstrap-servers16:24
inc0;)16:24
hrwJeffrey4l: will look16:24
Jeffrey4lwhy can't we have a widely support for docker version?16:25
Jeffrey4lkolla works if docker > 1.1016:25
Jeffrey4lhrw thanks.16:25
hrwJeffrey4l: ask docker guys to handle upgrades etc. they do not care much16:25
hrw;'d16:25
hrwI would love to see docker package in debian/stable but docker way of development == no package for stable at all16:26
Jeffrey4lhrw, fyi, we use docker 1.12.6 for a long time. and migrate to docker-ce 17.9 recently.16:26
inc0that's pretty much why we pin to 1.12 / 1.1316:26
rwellumI thought the move was to using CNFI docker - but maybe that's more specific to kubernetes community16:26
inc0upgrades/breaking things is not docker inc first priority16:27
Jeffrey4ldocker changed too much after 1.13. including its name and deployment progress.16:27
hrw#action hrw to check http://logs.openstack.org/12/522712/8/check/kolla-ansible-centos-source/8f4125e/primary/ansible/bootstrap-servers failures16:27
hrw2. cpu_mode for nova - just ignore now. have to debug and improve16:27
hrw3. mariadb boostrap. or rather galera16:28
hrwlooks like centos/ubuntu on x86 has galera enabled always (wsrep_on = ON)16:28
hrwin Debian it has to be set in config or via cli16:29
hrwwith http://paste.debian.net/1001704/ I have mariadb container which says " wsrep_ready   | ON "16:29
hrwbut I assume that it will break other distros etc as this is a hack16:30
*** pmesserli has joined #openstack-meeting-416:30
inc0well gates pass so it's not horrendous16:30
Jeffrey4lhrw, with that patch, debian will not support cluster.16:30
inc0it might break on multinode16:30
hrwso far I am unable to do all-in-one16:31
Jeffrey4lstill do not get the point what should be done in debian side.16:31
Jeffrey4lhrw, it will break multi node in debian.16:31
egonzalez90Try with mariadb 10.0 rather 10.116:31
hrwJeffrey4l: neither do I. times when I used mysql as admin were gone 10y ago16:31
hrwegonzalez90: 10.1 is in repo16:31
hrwegonzalez90: we do not use 3rdparty repos with Debian16:31
Jeffrey4lhrw what error did you get?16:32
egonzalez90Is what we use in other distros16:32
*** lyan has quit IRC16:32
Jeffrey4lwhy not try to enable wsrep by configuration?16:32
hrwJeffrey4l: thats where fun starts - fatal: [10.101.3.104]: FAILED! => {"changed": false, "failed": true, "msg": "unable to connect to database, check login_user and login_password are correct or /var/lib/ansible/.my.cnf16:33
hrwhas the credentials. Exception message: (1045, \"Access denied for user 'root'@'c8n1' (using password: YES)\")"}16:33
hrwegonzalez90: I got used to be that crazy guy who does some stuff first in kolla16:33
gemahrw: he has a point though, if 10.0 works then we can be sure it is the new version16:34
hrwI will probably start again with deploys in x86-64 vm to find out how the hell it works at each step16:34
gemaelse it could be configuration16:34
gemacan we use ubuntu's package to try?16:34
gemaor that, sounds good also16:35
hrwgema: I would rather dig out 10.0 from Debian. that would also require digging out old galera package16:35
gemahrw: ok, sound good16:35
hrwgema: using Ubuntu package would be like using CentOS rpms basically - no idea what was changed and why16:35
gemahrw: understood16:35
hrwI hope that Xinliang will get further than I did. He has more experience now with k-a16:36
gemahrw: he will16:36
gemagive him some time16:36
hrwgema: I do not touch kolla stuff this year probably.16:37
gemaanyway, I think we can move to your next topic16:37
gemaif you had more16:37
hrwnope, finished16:37
inc0that's it with agenda16:37
inc0#topic open discussion16:38
*** openstack changes topic to "open discussion (Meeting topic: kolla)"16:38
inc0anyone?16:38
hrwI wish kolla*start etc would be in k-a instead of images ;d16:38
hrweasier to hack and deploy ;D16:38
rwellumI have a fairly large PS for kolla-k8s - adding V3 api's if anyone wants to look...16:39
Jeffrey4lyep i thought of this too.16:39
inc0https://review.openstack.org/#/c/526200/ speaking of which:)16:39
inc0I'll address stuff from review today but I'll need more feedback16:39
inc0and agree, after hub images kolla becomes much less useful for users16:39
inc0kolla-ansible is standalone now16:40
inc0building images moved from requirement to advanced usage16:40
hrws/eth0/eno1 s/eth1/eno1d1 ;d16:41
rwelluminc0: most companies probably have their own source tho right? Not sure that statement is correct unless you are deploying pure upstream.16:41
gemarwellum: for some images16:41
hrwspeaking of hub. is there a way to list someone's hub.docker images?16:41
rwellumgema: ack16:41
inc0rwellum: I don't think so tbh, I think most companies (at least smaller ones) uses just openstack16:41
hrwkind of 'docker hubimages kolla' for example16:41
inc0hrw: https://review.openstack.org/#/c/526469/11/tests/playbooks/publish_release.yml line 3516:42
hrwinc0: thanks16:42
hrwanything else?16:43
inc0so projects are now separate, kolla and kolla-ansible16:44
inc0there is no "default" doc now16:44
*** links has quit IRC16:44
chasoninc0 Maybe we can link both kolla and kolla-ansible's docs together. :)16:45
inc0yeah16:46
inc0we do it now kinda16:46
inc0but maybe it's not fully clear16:46
inc0anything else on topic? anyone want to discuss anything?16:47
* hrw nope16:47
inc0allright16:48
inc0let's get 10min back in our lives:)16:48
inc0merry chrismas everyone!16:48
inc0#endmeeting kolla16:49
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:49
hrwhappy xmas16:49
openstackMeeting ended Wed Dec 20 16:49:04 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-12-20-15.59.html16:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-12-20-15.59.txt16:49
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-12-20-15.59.log.html16:49
*** hrw has left #openstack-meeting-416:49
*** gibi is now known as gibi_away16:50
*** egonzalez90 has quit IRC16:50
*** egonzalez has joined #openstack-meeting-416:50
*** chyka has joined #openstack-meeting-416:50
*** gema has left #openstack-meeting-416:56
*** egonzalez has quit IRC16:58
*** anilvenkata has quit IRC16:58
*** iyamahat has joined #openstack-meeting-417:14
*** duonghq has quit IRC17:16
*** d0ugal has quit IRC17:23
*** sbezverk has joined #openstack-meeting-417:25
*** salmankhan has quit IRC17:29
*** d0ugal has joined #openstack-meeting-417:35
*** salmankhan has joined #openstack-meeting-417:37
*** neiljerram has quit IRC17:42
*** neiljerram has joined #openstack-meeting-417:44
*** iyamahat has quit IRC17:45
*** sambetts is now known as sambetts|afk17:53
*** arcolife has quit IRC17:57
*** iyamahat has joined #openstack-meeting-418:00
*** neiljerram has quit IRC18:09
*** makowals has joined #openstack-meeting-418:11
*** yamahata has joined #openstack-meeting-418:17
*** lyan has joined #openstack-meeting-418:35
*** janonymous has quit IRC18:35
*** salmankhan has quit IRC18:41
*** coolsvap has quit IRC19:00
*** gcheresh_ has joined #openstack-meeting-419:03
*** salv-orl_ has quit IRC19:14
*** salv-orlando has joined #openstack-meeting-419:14
*** makowals has quit IRC19:15
*** premsankar has quit IRC19:19
*** salv-orlando has quit IRC19:19
*** bobh has quit IRC19:20
*** bobh has joined #openstack-meeting-419:28
*** pcaruana has quit IRC19:29
*** bobh has quit IRC19:33
*** bobh has joined #openstack-meeting-419:33
*** bobh has quit IRC19:38
*** gcheresh_ has quit IRC19:39
*** gcheresh_ has joined #openstack-meeting-419:40
*** gcheresh_ has quit IRC19:44
*** bobh has joined #openstack-meeting-419:44
*** pcaruana has joined #openstack-meeting-419:48
*** bobh has quit IRC19:49
*** pcaruana has quit IRC19:54
*** bobh has joined #openstack-meeting-419:55
*** bobh has quit IRC19:59
*** bobh has joined #openstack-meeting-420:05
*** pcaruana has joined #openstack-meeting-420:06
*** slaweq_ has joined #openstack-meeting-420:06
*** bobh has quit IRC20:10
*** pcaruana has quit IRC20:13
*** bobh has joined #openstack-meeting-420:14
*** bobh has quit IRC20:19
*** bobh has joined #openstack-meeting-420:24
*** bobh has quit IRC20:28
*** lyan has quit IRC20:36
*** links has joined #openstack-meeting-420:41
*** seajay has quit IRC20:46
*** links has quit IRC20:47
*** chyka has quit IRC20:48
*** bobh has joined #openstack-meeting-421:15
*** salv-orlando has joined #openstack-meeting-421:16
*** bobh has quit IRC21:20
*** salv-orlando has quit IRC21:20
*** slaweq_ has quit IRC21:23
*** bobh has joined #openstack-meeting-421:34
*** bnemec has quit IRC21:36
*** cleong has quit IRC21:38
*** bobh has quit IRC21:38
*** bobh has joined #openstack-meeting-421:42
*** bobh has quit IRC21:47
*** bobh has joined #openstack-meeting-421:53
*** seajay has joined #openstack-meeting-421:56
*** bobh has quit IRC21:58
*** seajay has quit IRC22:07
*** salv-orlando has joined #openstack-meeting-422:17
*** chyka has joined #openstack-meeting-422:17
*** salv-orlando has quit IRC22:22
*** chyka has quit IRC22:22
*** bobh has joined #openstack-meeting-422:24
*** david-lyle has quit IRC22:24
*** bobh has quit IRC22:28
*** trozet has quit IRC22:32
*** bobh has joined #openstack-meeting-422:54
*** david-lyle has joined #openstack-meeting-422:56
*** bobh has quit IRC22:59
*** bobh has joined #openstack-meeting-423:14
*** dave-mccowan has quit IRC23:17
*** salv-orlando has joined #openstack-meeting-423:17
*** bobh has quit IRC23:18
*** salv-orlando has quit IRC23:21
*** bobh has joined #openstack-meeting-423:25
*** bobh has quit IRC23:29
*** bobh has joined #openstack-meeting-423:33
*** bobh has quit IRC23:37

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