Wednesday, 2017-01-25

*** tinwood has quit IRC00:00
*** tinwood has joined #openstack-meeting-400:01
*** sdague has joined #openstack-meeting-400:02
*** pmesserli has quit IRC00:02
*** limao has quit IRC00:04
*** Swami_ has joined #openstack-meeting-400:08
*** Swami has quit IRC00:10
*** mattmceuen has quit IRC00:13
*** hongbin has quit IRC00:22
*** TxGirlGeek has quit IRC00:26
*** sdake has joined #openstack-meeting-400:26
*** yamahata has quit IRC00:27
*** iyamahat has quit IRC00:34
*** thorst_ has joined #openstack-meeting-400:42
*** zhurong has joined #openstack-meeting-400:44
*** neiljerram has quit IRC00:45
*** limao has joined #openstack-meeting-400:46
*** amotoki has joined #openstack-meeting-400:49
*** bobh has joined #openstack-meeting-400:51
*** bobh has quit IRC00:51
*** bobh has joined #openstack-meeting-400:51
*** bobh has quit IRC00:51
*** julim has joined #openstack-meeting-400:55
*** thorst_ has quit IRC00:58
*** SerenaFeng has joined #openstack-meeting-401:01
*** sdague has quit IRC01:01
*** cathrichardson has joined #openstack-meeting-401:06
*** cathrichardson has quit IRC01:11
*** Syed__ has quit IRC01:15
*** admcleod_ has quit IRC01:17
*** sdake has quit IRC01:22
*** sdake has joined #openstack-meeting-401:35
*** bobh has joined #openstack-meeting-401:37
*** tovin07_ has joined #openstack-meeting-401:43
*** Sukhdev has quit IRC01:45
*** KunalGandhi has joined #openstack-meeting-401:49
*** jose-phillips has quit IRC01:49
*** woodard_ has joined #openstack-meeting-401:55
*** woodard has quit IRC01:55
*** jose-phillips has joined #openstack-meeting-401:56
*** bobh has quit IRC01:57
*** Swami_ has quit IRC02:00
*** lei-zh has joined #openstack-meeting-402:05
*** sdake has quit IRC02:06
*** bobh has joined #openstack-meeting-402:14
*** sacharya has joined #openstack-meeting-402:15
*** armax has quit IRC02:31
*** admcleod has joined #openstack-meeting-402:38
*** admcleod has quit IRC02:38
*** admcleod has joined #openstack-meeting-402:38
*** yfauser has joined #openstack-meeting-402:44
*** KunalGandhi has quit IRC02:45
*** l4yerffeJ has quit IRC02:48
*** l4yerffeJ has joined #openstack-meeting-402:49
*** s3wong has quit IRC02:52
*** SerenaFeng has quit IRC02:54
*** SerenaFeng has joined #openstack-meeting-402:54
*** thorst_ has joined #openstack-meeting-402:57
*** thorst_ has quit IRC02:57
*** hongbin has joined #openstack-meeting-403:02
*** iyamahat has joined #openstack-meeting-403:05
*** chandanc_ has joined #openstack-meeting-403:05
*** iyamahat has quit IRC03:11
*** iyamahat has joined #openstack-meeting-403:11
*** revon has quit IRC03:13
*** iyamahat_ has joined #openstack-meeting-403:14
*** iyamahat_ has quit IRC03:15
*** iyamahat_ has joined #openstack-meeting-403:16
*** iyamahat has quit IRC03:17
*** hongbin has quit IRC03:20
*** sdake has joined #openstack-meeting-403:21
*** hongbin has joined #openstack-meeting-403:21
*** sp___ has joined #openstack-meeting-403:22
*** yfauser has quit IRC03:28
*** anilvenkata has joined #openstack-meeting-403:50
*** spotz_zzz is now known as spotz03:53
*** SerenaFeng has quit IRC03:57
*** l4yerffeJ has quit IRC04:01
*** marst has joined #openstack-meeting-404:01
*** l4yerffeJ has joined #openstack-meeting-404:01
*** tovin07 has quit IRC04:02
*** spotz is now known as spotz_zzz04:03
*** sdake has quit IRC04:08
*** armax has joined #openstack-meeting-404:10
*** hongbin has quit IRC04:23
*** bobh has quit IRC04:25
*** vishnoianil has quit IRC04:30
*** dave-mccowan has quit IRC04:30
*** armax has quit IRC04:30
*** Sukhdev has joined #openstack-meeting-404:37
*** jose-phillips has quit IRC04:40
*** sdake_ has joined #openstack-meeting-404:40
*** sdake_ has quit IRC04:40
*** sdake_ has joined #openstack-meeting-404:40
*** hongbin has joined #openstack-meeting-404:41
*** psachin has joined #openstack-meeting-404:42
*** hongbin has quit IRC04:53
*** armax has joined #openstack-meeting-404:55
*** yamahata has joined #openstack-meeting-404:56
*** armax has quit IRC04:56
*** thorst_ has joined #openstack-meeting-404:59
*** thorst_ has quit IRC05:03
*** adisky_ has joined #openstack-meeting-405:04
*** gongysh has joined #openstack-meeting-405:18
*** vikasc has quit IRC05:20
*** tlbr_ has quit IRC05:20
*** yfauser has joined #openstack-meeting-405:21
*** s3wong has joined #openstack-meeting-405:29
*** janki has joined #openstack-meeting-405:32
*** tlbr has joined #openstack-meeting-405:49
*** jchhatbar has joined #openstack-meeting-405:50
*** spotz_zzz is now known as spotz05:50
*** sacharya has quit IRC05:51
*** janki has quit IRC05:51
*** SerenaFeng has joined #openstack-meeting-405:52
*** KunalGandhi has joined #openstack-meeting-405:59
*** janki has joined #openstack-meeting-406:02
*** jchhatbar has quit IRC06:04
*** spotz is now known as spotz_zzz06:11
*** irenab_ has joined #openstack-meeting-406:11
*** irenab_ has quit IRC06:12
*** armax has joined #openstack-meeting-406:13
*** SerenaFeng has quit IRC06:15
*** armax has quit IRC06:16
*** yfauser has quit IRC06:17
*** KunalGandhi has quit IRC06:19
*** vikasc has joined #openstack-meeting-406:23
*** jchhatbar has joined #openstack-meeting-406:26
*** janki has quit IRC06:29
*** s3wong has quit IRC06:31
*** anilvenkata has quit IRC06:32
*** vishnoianil has joined #openstack-meeting-406:34
*** chandanc_ has quit IRC06:37
*** Sukhdev has quit IRC06:39
*** s3wong has joined #openstack-meeting-406:43
*** anilvenkata has joined #openstack-meeting-406:44
*** spotz_zzz is now known as spotz06:46
*** jchhatbar is now known as janki06:47
*** Jeffrey4l_ has quit IRC06:48
*** Jeffrey4l has joined #openstack-meeting-406:53
*** makowals_ has quit IRC06:53
*** trinaths has joined #openstack-meeting-406:53
*** tovin07 has joined #openstack-meeting-406:54
*** spotz is now known as spotz_zzz06:56
*** s3wong has quit IRC06:57
*** thorst_ has joined #openstack-meeting-406:59
*** sdake_ has quit IRC07:01
*** thorst_ has quit IRC07:04
*** makowals has joined #openstack-meeting-407:06
*** spotz_zzz is now known as spotz07:07
*** mrunge has quit IRC07:08
*** mrunge has joined #openstack-meeting-407:09
*** matrohon has joined #openstack-meeting-407:16
*** spotz is now known as spotz_zzz07:17
*** yamamoto has quit IRC07:17
*** anilvenkata has quit IRC07:17
*** matrohon has quit IRC07:23
*** pcaruana has joined #openstack-meeting-407:28
*** anilvenkata has joined #openstack-meeting-407:30
*** tovin07 has quit IRC07:32
*** britthouser7 has joined #openstack-meeting-407:34
*** yifei_ has joined #openstack-meeting-407:36
*** pshedimb has quit IRC07:37
*** yifei has left #openstack-meeting-407:37
*** britthouser has quit IRC07:38
*** pshedimb has joined #openstack-meeting-407:39
*** lcastell has quit IRC07:40
*** spotz_zzz is now known as spotz07:42
*** alexchadin has joined #openstack-meeting-407:45
*** tovin07 has joined #openstack-meeting-407:45
*** ricolin has joined #openstack-meeting-407:49
*** spotz is now known as spotz_zzz07:52
*** ifat_afek has joined #openstack-meeting-407:54
*** eyalb has joined #openstack-meeting-407:59
*** yamamoto has joined #openstack-meeting-408:00
ifat_afek#startmeeting vitrage08:00
openstackMeeting started Wed Jan 25 08:00:27 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
eyalbhi08:00
*** doffek has joined #openstack-meeting-408:01
doffekHi guys.08:01
*** yamamoto has quit IRC08:02
*** alexey_weyl has joined #openstack-meeting-408:02
alexey_weylhi08:02
*** yamamoto has joined #openstack-meeting-408:03
ifat_afekToday’s agenda:08:03
ifat_afek•Ocata Release08:03
ifat_afek•Status and Updates08:04
ifat_afek•Pike Design sessions08:04
ifat_afek•Boston CFP08:04
ifat_afek#topic Ocata Release08:04
*** openstack changes topic to "Ocata Release (Meeting topic: vitrage)"08:04
ifat_afekThis week we need to release python-vitrageclient, and then to add it to the global-requirements08:04
ifat_afekUnfortunately, our gate is broken for a few days (thanks Alexey_weyl and idan_hefetz for fixing it!), so it was delayed. I will request to release python-vitrageclient today08:04
ifat_afekOnce python-vitrageclient is released, I will request to add it to the global-requirements08:04
*** dwj has joined #openstack-meeting-408:04
ifat_afekNote that we can continue developing the vitrage and vitrage-dashboard projects for Ocata until February 16th (but we’ll probably stop a little earlier to make sure everything is stable)08:05
ifat_afekThis week is also the PTLs nomination week. I plan to announce my candidacy later today.08:05
ifat_afekThe full Ocata schedule can be found here:08:05
ifat_afek#link https://releases.openstack.org/ocata/schedule.html08:05
ifat_afekAny comments regarding the release dates?08:05
eyalbnope08:06
ifat_afek#topic Status and Updates08:06
*** openstack changes topic to "Status and Updates (Meeting topic: vitrage)"08:06
ifat_afekMy updates: I’m done with the blueprint of adding a new API for post event to Vitrage, to be used by Doctor datasource (but not only).08:06
ifat_afek#link https://blueprints.launchpad.net/vitrage/+spec/support-inspector-sb-api08:06
ifat_afekNext thing, I plan to modify Doctor’s test script so that it will test Vitrage in a similar way to the Congress test.08:07
ifat_afekWho’s next?08:07
doffekI'll update .08:07
doffekI prepared a Vitrage Lab via webinar for yesterday for anyone that wishes to contribute to Vitrage.08:08
doffekPrepared about 15 Devstacks with Vitrage08:08
doffekPeople joined the webinar and saw the preliminary presentation.08:08
doffekThere was a set of instructions as  part of the lab, that, when run, step by step allowed the lab participants to learn how Vitrage looks, how it works, how to run CLI commands, how to add additional datasources,08:10
doffekIt even had an easy instructions set for how to prepare templates for deduced alarms and RCA .08:10
doffekBut no one seemed to actually do the lab. That's a miss from my point of view. It was a lab webinar, not a presentation one.08:11
doffekI don't see any new contributors coming from this webinar08:11
ifat_afekdoffek: It was only yesterday, let’s wait ;-)08:12
doffekNone of them participated in the lab.08:12
ifat_afekAnd I think the presentation part is also very important. I understand why you were disappointed, but it still might help08:12
ifat_afekWas the session recorded?08:12
ifat_afekBecause if it was, we could publish it08:12
doffekDon't think so, but in any case, the purpose was to show potential contributors how easy it is to contribute.08:13
ifat_afekI think there is a lot of value to it for a contributor that likes to start working with Vitrage08:13
*** tovin07 has quit IRC08:13
ifat_afekI konw…08:13
doffekIn any case, that's my update.08:13
*** nofarsch has joined #openstack-meeting-408:13
ifat_afekdoffek: thanks! and BTW, I noticed you suggested a lab for Boston. I think it’s a great idea08:14
alexey_weylI will update08:14
alexey_weylwe has some problems in the gate, and finally resolved them yesterday because some novaclient api was changed08:15
alexey_weylIn addition I am working on the "not" operator for the templates08:15
ifat_afekalexey_weyl: Thanks for fixing it! I just don’t understand how come no other project was affected. Strange…08:15
alexey_weylthis will give a much bigger language to describe our language and our use cases08:16
ifat_afekThe ‘not’ is very important. It was blocking some of our use cases08:16
alexey_weylfor example if we have HA between two switches, thus if one will fall then we won't have to raise alarms on some vms due to that08:16
ifat_afekBTW, once you are done, don’t forget to update also the documentation08:17
nofarschmaybe other projects knew of this change?08:17
ifat_afekalexey_weyl: Right, that’s a good example08:17
ifat_afeknofarsch: I must admit that I don’t follow all of nova emails. But I don’t believe I’m the only one who missed it08:17
alexey_weylWe haven't seen that other projects encountered the same problem, most probably due to the fact that they didn't use the interface parameter for the novaclient08:17
ifat_afekWhat is the interface parameter?08:18
alexey_weylNow, another update is the vitrage-aodh integration08:18
*** idan_hefetz has joined #openstack-meeting-408:19
alexey_weylAfter the aodh team has agreed to our changes of adding a new alarm (in austin and barcelona) with another field called metadata/userdata that will contain some internal information about the alarm08:19
alexey_weylthey are now rethinking that decision, because they say that aodh isn't an alarm manager for all alarms but is more a system that is alarm engine evaluator08:20
alexey_weylat the moment we are trying to figure out exactly what can't be done in that area with the aodh team, but if some other vitrage users have something to say about that, please do so, because I think if there will more voices that say that this value is needed then it may make them rethink about that08:22
alexey_weylthat's it for now08:23
ifat_afekPersonally I was quite surprised that they started hesitating, because I felt that we already discussed it. We should continue the discussions in the ML until soneone is convinced :-)08:23
*** ralonsoh has joined #openstack-meeting-408:24
ifat_afekAnyone else wants to updated?08:24
ifat_afekupdate08:24
ifat_afek#topic Pike Design Sessions08:25
*** openstack changes topic to "Pike Design Sessions (Meeting topic: vitrage)"08:25
ifat_afekWe will hold Pike Design Sessions in Israel, on March 6th-7th. You are all invited to participate and to suggest topics for the discussions08:25
ifat_afekThe design session etherpad:08:25
ifat_afek#link https://etherpad.openstack.org/p/vitrage-pike-design-sessions08:26
ifat_afekAny comments about it?08:26
ifat_afek#topic Boston CFP08:28
*** openstack changes topic to "Boston CFP (Meeting topic: vitrage)"08:28
ifat_afekBoston CFP is now open, and we already listed some ideas in our etherpad08:28
ifat_afek#link https://www.openstack.org/summit/boston-2017/call-for-presentations/08:28
ifat_afek#link https://etherpad.openstack.org/p/vitrage-boston-session-proposals08:28
ifat_afekFeel free to add more ideas. The deadline for submitting is February 6.08:28
ifat_afekAny proposal you would like to discuss?08:29
*** tovin07 has joined #openstack-meeting-408:29
*** Jeffrey4l_ has joined #openstack-meeting-408:30
*** l4yerffeJ_ has joined #openstack-meeting-408:30
ifat_afekSo I guess we are done. See you next week :-)08:31
eyalbbye08:31
idan_hefetzbye08:31
ifat_afek#endmeeting08:31
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:31
openstackMeeting ended Wed Jan 25 08:31:37 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vitrage/2017/vitrage.2017-01-25-08.00.html08:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2017/vitrage.2017-01-25-08.00.txt08:31
openstackLog:            http://eavesdrop.openstack.org/meetings/vitrage/2017/vitrage.2017-01-25-08.00.log.html08:31
*** eyalb has left #openstack-meeting-408:32
*** alexey_weyl has quit IRC08:32
*** vikasc has quit IRC08:33
*** l4yerffeJ has quit IRC08:34
*** Jeffrey4l has quit IRC08:34
*** spotz_zzz is now known as spotz08:36
*** nofarsch has quit IRC08:36
*** lcastell has joined #openstack-meeting-408:37
*** doffek has left #openstack-meeting-408:42
*** ifat_afek has left #openstack-meeting-408:42
*** spotz is now known as spotz_zzz08:46
*** amotoki has quit IRC08:47
*** sshnaidm|afk is now known as sshnaidm08:48
*** chandanc_ has joined #openstack-meeting-408:49
*** vikasc has joined #openstack-meeting-408:51
*** tlbr has quit IRC08:58
*** thorst_ has joined #openstack-meeting-409:00
*** tovin07 has quit IRC09:00
*** thorst_ has quit IRC09:05
*** tlbr has joined #openstack-meeting-409:06
*** dwj has quit IRC09:09
*** zhurong has quit IRC09:14
*** tovin07 has joined #openstack-meeting-409:15
*** janki has left #openstack-meeting-409:16
*** janki has joined #openstack-meeting-409:17
*** spotz_zzz is now known as spotz09:30
*** limao has quit IRC09:31
*** dtardivel has joined #openstack-meeting-409:35
*** yamamoto has quit IRC09:38
*** spotz is now known as spotz_zzz09:40
*** tovin07 has quit IRC09:41
*** sp___ has quit IRC09:42
*** adisky_ has quit IRC09:49
*** ricolin has quit IRC09:50
*** tovin07_ has quit IRC09:55
*** tlbr has quit IRC10:02
*** spotz_zzz is now known as spotz10:06
*** iyamahat_ has quit IRC10:10
*** sambetts|afk is now known as sambetts10:13
*** spotz is now known as spotz_zzz10:16
*** neiljerram has joined #openstack-meeting-410:16
*** alexchad_ has joined #openstack-meeting-410:18
*** amotoki has joined #openstack-meeting-410:19
*** alexchadin has quit IRC10:21
*** yamamoto has joined #openstack-meeting-410:25
*** yamamoto has quit IRC10:26
*** pbourke has quit IRC10:29
*** pbourke has joined #openstack-meeting-410:30
*** aarefiev_afk is now known as aarefiev10:32
*** tlbr has joined #openstack-meeting-410:38
*** lei-zh has quit IRC10:41
*** vmahe_ has joined #openstack-meeting-410:45
*** tlbr has quit IRC10:46
*** vikasc has quit IRC10:48
*** iyamahat_ has joined #openstack-meeting-410:53
*** yamahata has quit IRC10:56
*** tlbr has joined #openstack-meeting-410:59
*** spotz_zzz is now known as spotz11:00
*** thorst_ has joined #openstack-meeting-411:01
*** chandanc_ has quit IRC11:02
*** thorst_ has quit IRC11:05
*** iyamahat_ has quit IRC11:07
*** spotz is now known as spotz_zzz11:10
*** yamamoto has joined #openstack-meeting-411:18
*** yamamoto has quit IRC11:18
*** vikasc has joined #openstack-meeting-411:20
*** cdelatte has quit IRC11:23
*** chem has quit IRC11:24
*** rfolco has joined #openstack-meeting-411:26
*** yamamoto has joined #openstack-meeting-411:33
*** yamamoto has quit IRC11:34
*** spotz_zzz is now known as spotz11:36
*** galstrom_zzz is now known as galstrom11:39
*** anilvenkata has quit IRC11:41
*** alexchad_ has quit IRC11:42
*** spotz is now known as spotz_zzz11:46
*** alexchadin has joined #openstack-meeting-411:47
*** anilvenkata has joined #openstack-meeting-412:01
*** anilvenkata has quit IRC12:09
*** cdelatte has joined #openstack-meeting-412:10
*** d0ugal has quit IRC12:10
*** reedip_ has joined #openstack-meeting-412:11
*** trinaths has left #openstack-meeting-412:14
*** d0ugal has joined #openstack-meeting-412:19
*** anilvenkata has joined #openstack-meeting-412:21
*** spotz_zzz is now known as spotz12:30
*** neiljerram has quit IRC12:36
*** iurygregory has quit IRC12:38
*** neiljerram has joined #openstack-meeting-412:39
*** vikasc has quit IRC12:42
*** neiljerram has quit IRC12:43
*** thorst_ has joined #openstack-meeting-412:44
*** lei-zh has joined #openstack-meeting-412:45
*** sdake has joined #openstack-meeting-412:45
*** neiljerram has joined #openstack-meeting-412:45
*** sp___ has joined #openstack-meeting-412:53
*** chandanc_ has joined #openstack-meeting-412:57
*** sshnaidm is now known as sshnaidm|afk12:57
alex_xu#startmeeting nova api13:00
openstackMeeting started Wed Jan 25 13:00:21 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
Kevin_Zhengo/13:00
gmanno/13:00
*** bobh has joined #openstack-meeting-413:01
*** bobh has quit IRC13:01
*** vikasc has joined #openstack-meeting-413:01
*** bobh has joined #openstack-meeting-413:01
alex_xulooks like just three of us13:01
gmannyea13:01
Kevin_Zhenghttps://review.openstack.org/#/c/421760/13:02
Kevin_Zhengplease also review he doc patch if have time?13:02
*** chandanc_ has quit IRC13:02
gmannor let's wait for few min for johnthetubaguy  sdague13:02
alex_xuKevin_Zheng: yea13:02
Kevin_ZhengI may update again tommorow13:02
gmannKevin_Zheng: sure, ll check in morning tomorrow13:02
johnthetubaguyoops, hello13:03
alex_xu#link https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/add-whitelist-for-server-list-filter-sort-parameters13:03
alex_xu^ the last three patches13:03
*** iurygregory has joined #openstack-meeting-413:04
alex_xujohnthetubaguy: the policy one is ready, hope you can take a look at it13:04
*** cdent has joined #openstack-meeting-413:05
johnthetubaguyso the logging, we probably don't want to do all that logging on every API request13:05
johnthetubaguymaybe we can check that in the API controller constructor? would that work?13:06
alex_xuemm...yea, that is a little annoying13:06
gmannjohnthetubaguy:  you mean for old rule?13:07
johnthetubaguyyeah13:07
alex_xuin the controller constructor sounds doable13:07
gmannbut that will be only when all_tenants13:08
johnthetubaguyits really logging to the operators about their config13:08
johnthetubaguyits not really anything to do with a particular API request as such13:08
alex_xuwe have another warning at https://github.com/openstack/nova/blob/master/nova/policy.py#L8313:08
gmannah i see your point13:09
alex_xuthat warn on every policy config change13:09
johnthetubaguyalex_xu: ah, well remembered, we should probably copy that pattern13:09
johnthetubaguyI had forgotten about that one13:09
gmann+113:10
alex_xuwe can put that warning in the policy.init() also13:11
johnthetubaguyI was kinda expecting to have the defaults deal with falling back to the old rules13:11
johnthetubaguydid that not work?13:11
gmannwith is_rule_override check it can be more aligned when old rules are overridden13:11
johnthetubaguyall_tenants_visible = rule:detail:get_all_tenants and rule:index:get_all_tenants (or something like that)13:12
johnthetubaguyI guess thats been done in code, just wondering what pattern we should choose for these things13:13
gmannjohnthetubaguy: but if operator use to have policy.json from the sample and override the interesting one then it might be issue13:13
gmannbut not sure if they do this way13:13
johnthetubaguythats fine, they overrode it, so it does the right thing13:14
alex_xujohnthetubaguy: that doesn't work for new deployer. due to the old one always return 403 when fail13:14
johnthetubaguywhy? all the rules have the same default?13:15
johnthetubaguyoh, wait, I see your point now13:15
alex_xuthe new behaviour expect no 403 when fail.13:15
johnthetubaguyyou are trying to keep the 403 behaviour13:15
johnthetubaguyhmm... I wasn't expecting us doing that13:15
gmanni think no 403 and give at least their own servers13:16
johnthetubaguydoesn't that change need a microversion, with the new rule we 403 before it, and after it everyone leaves it soft13:16
johnthetubaguyI guess its dropping an error, so maybe thats OK13:17
alex_xuemm...whether it return 403 still depend on policy config13:17
alex_xuthat isn't something resolved by microversion. it should be resovled by policy discovery13:18
johnthetubaguylets step back13:20
johnthetubaguyright now, all_tenants sends 403 if an admins (or whatever policy says)13:21
*** sshnaidm|afk is now known as sshnaidm13:21
alex_xuyup13:21
johnthetubaguyafter this, we don't send 403... unless the admin has overridden the old policy rule, which we want to delete next cycle13:21
gmannyea13:22
johnthetubaguyI think my comment about working with the old policy has confused things here13:22
johnthetubaguywhat I mean is, you can only view other tenants servers when you pass a certainly policy rule13:22
johnthetubaguywe are basically renaming that rule13:23
johnthetubaguyso across upgrade, we need to respect settings on the old rules for now13:23
johnthetubaguyI think we are all agreed with that aim13:23
alex_xuyes13:24
gmannyes13:24
johnthetubaguycool13:24
Kevin_Zhengyeah13:24
johnthetubaguyso you could consider that one patch13:24
*** jchhatbar has joined #openstack-meeting-413:24
johnthetubaguynow there is a second patch in there13:24
johnthetubaguywhen you pass all_tenants=True, the API should return as many instance as you are allowed to see given your token, rather than doing 403 if you fail a policy check to list instances from all tenants in the system13:25
johnthetubaguypart of me wonders if that needs a microversion13:25
johnthetubaguyit feels strange to me for the API to flip between the old behaviour and new behaviour based on the policy file, given we want to kill the old behaviour next cycle13:26
gmannbut that is with new policy rule.13:26
*** janki has quit IRC13:26
johnthetubaguyno, we want the new behaviour13:26
*** spotz is now known as spotz_zzz13:26
johnthetubaguywe could keep the old policy rules13:27
*** v1k0d3n has quit IRC13:27
johnthetubaguybut with the new behaviour, the old policy rule names don't really make any sense13:27
johnthetubaguyI am not every good at describing my concern here I guess13:28
alex_xuso you want to rename it first13:28
alex_xuthen microversion with behaviour change13:28
*** v1k0d3n has joined #openstack-meeting-413:29
johnthetubaguyactually my preferece is the other way around13:30
cdentah microversions... :)13:30
johnthetubaguywhether we want a microversion or not is a different debate, it feels like we are changing the API to me, but I could be looking at this wrongly13:31
gmanneven that is something depends on policy setting and each cloud can have different behavior based on their policy setting13:31
gmannbut yea if cloud with same policy setting then, API can behave differently13:32
*** spotz_zzz is now known as spotz13:32
johnthetubaguyI don't think we want different behaviours based on config13:33
*** zeih has joined #openstack-meeting-413:33
johnthetubaguywe do want admins to be able to upgrade without accidentally changing who is able to list all the instances on the system, because they have modified their policy rules, and we didn't warn them about the change13:34
johnthetubaguywe can have different behaviours based on different microversions though, that seems just fine13:35
*** bobh has quit IRC13:36
alex_xuso microversion with new behaviour. but new rule just copy the rule of old one13:37
gmannbut when policy rules are modified, anyways behavior can be changed when admin upgrade (currently also)13:38
johnthetubaguygmann: thats fairly terrible, we should stop that13:38
johnthetubaguynow we need oslo.policy to help us more, eventually, but we just are not there yet13:39
johnthetubaguymy concern is based on this13:39
johnthetubaguyhttps://governance.openstack.org/tc/reference/tags/assert_supports-upgrade.html#requirements13:39
johnthetubaguyand because I believe policy = configuration13:39
*** spotz is now known as spotz_zzz13:41
alex_xujohnthetubaguy: yes, we just implement that. so you concern on microversion?13:42
alex_xusorry, i'm a little lost...13:42
gmannhumm13:42
Kevin_Zhengold rule can work on the current patch, I think13:42
*** vikasc has quit IRC13:43
johnthetubaguyalex_xu: that was just a comment about how we have failed to do this properly in the past13:44
gmannjohnthetubaguy: can new rule be considered as new config option kinnda ?13:44
*** kylek3h_ has joined #openstack-meeting-413:44
johnthetubaguyso it is a new config, effectively13:44
johnthetubaguyI really don't like us changing the API behaviour based on a config13:44
johnthetubaguythe odd bit, is we plan on removing the old behaviour and old config next cycle13:45
gmannyea that's true13:45
alex_xuyea13:45
johnthetubaguythat just seems odd to me, struggling to describe why13:45
gmannnow i got your point13:45
johnthetubaguyfor me, we use microversions to create API behaviour changes13:45
johnthetubaguyand advertise them correctly, etc13:45
gmannagree on this now.13:46
*** kylek3h has quit IRC13:46
Kevin_Zhengok13:46
gmannotherwise it can be interop issue13:46
johnthetubaguynow I think its easier to think about this in two steps13:47
johnthetubaguyone change adds a microversion to make all_tenants no longer trigger 403, the old policy rules just decide if you show servers from all tenants, when you request all_tenants=True13:47
*** spotz_zzz is now known as spotz13:48
johnthetubaguythe second change can rename the policy rules, with some backwards compatibility, because the old rule names don't really make sense with the new behaviour13:48
alex_xuso whether we return 403 in old microversion?13:49
johnthetubaguyin the old microversion, yes, the new policy rule decides if its 403 or allowed13:49
johnthetubaguyjust like the old ones did before it13:50
gmannbut with old rule support right13:50
johnthetubaguythe rename of the rule has to be backwards compatible, yes13:50
johnthetubaguywhatever those rules say, it gets used in the old microversion to return 403, and in the new microversion its a silent ignore or list instances across all tenants on the system13:51
*** Yumeng has joined #openstack-meeting-413:51
gmannyea13:51
johnthetubaguynow, there is a debate of whether its worth a microversion or not, but I don't think the policy settings should decide the behaviour13:52
johnthetubaguyif there is no microversion, I think everyone should have the new behaviour13:52
Kevin_Zhengmaybe a microversion bump when remove the old rule and change the behaviour for new rule?13:53
gmannbut still that change behavior if doing for everyne13:53
johnthetubaguyyeah, as long as its the same behaviour for everyone, that could work for me13:54
*** woodard_ has quit IRC13:54
gmanni mean app moving from upgareded cloud to old cloud can break13:54
*** chrisspencer has joined #openstack-meeting-413:54
gmannno 403 -> 40313:55
*** woodard has joined #openstack-meeting-413:55
alex_xu5 mins left13:55
*** vikasc has joined #openstack-meeting-413:55
johnthetubaguyreally its only people depending on getting 403 that would break13:55
*** sp___ has quit IRC13:55
johnthetubaguybut yeah, a break is possible, unless its microversioned13:55
gmannyea it can break interoperability13:56
alex_xuyea, althought the 403 is generic error people processed13:56
johnthetubaguyyou could use that 403 to check if you had an admin token, duno why you would, but you could13:57
gmann also app, on upgraded cloud where no 403 if decide to move to old non-upgraded cloud where 40313:57
alex_xuemm...yes13:57
gmanni mean we changing error to success which is issue. error-> good error only ok13:58
alex_xuone news, I will start the vacation from tomorrow. Kevin_Zheng will be there for tomorrow?13:58
*** baoli has joined #openstack-meeting-413:58
Kevin_Zhengyeah13:58
*** bobmel has quit IRC13:58
*** marst has quit IRC13:58
johnthetubaguyalex_xu: have a good break13:59
alex_xuprobably I will help on the patch tonight. but i'm not sure I have network tomorrow evening13:59
gmannalex_xu:  i can take up those updates, i am in for next week13:59
alex_xujohnthetubaguy: gmann thanks13:59
Kevin_Zhengcould you also update the doc one? already did some work13:59
gmannso we should go with microversion on behavior change ? as johnthetubaguy mentioned on 2 changes13:59
alex_xuok, we should back to nova channel, it is time to close the meeting13:59
*** vincentfrancoise has joined #openstack-meeting-413:59
gmannKevin_Zheng: sure ll do13:59
*** baoli_ has joined #openstack-meeting-414:00
alex_xu#endmeeting14:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:00
openstackMeeting ended Wed Jan 25 14:00:09 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_api/2017/nova_api.2017-01-25-13.00.html14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_api/2017/nova_api.2017-01-25-13.00.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_api/2017/nova_api.2017-01-25-13.00.log.html14:00
*** cdent has left #openstack-meeting-414:01
acabot#startmeeting watcher14:01
openstackMeeting started Wed Jan 25 14:01:15 2017 UTC and is due to finish in 60 minutes.  The chair is acabot. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: watcher)"14:01
openstackThe meeting name has been set to 'watcher'14:01
sballe_hi14:01
chrisspencero/14:01
acaboto/14:01
alexchadino/14:01
vincentfrancoiseo/14:01
hvprashhi14:01
acabotagenda for today #link https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#01.2F25.2F201614:01
dtardivelhi14:02
acabot#topic Announcements14:02
*** openstack changes topic to "Announcements (Meeting topic: watcher)"14:02
acabot#info Pike PTLs self nomination has started and Watcher has no candidate yet14:02
acabot#link https://governance.openstack.org/election/14:02
acabotPTL nomination ends in 4d9h42m1s14:03
alexchadinacabot: I've placed my self-nomination couple of hours ago14:03
sballe_alexchadin: +114:03
acabotalexchadin : yop sorry I missed it14:03
vincentfrancoisealexchadin: Nice!14:03
acabotalexchadin : review # ?14:03
alexchadinacabot: seconds14:03
alexchadinhttps://review.openstack.org/#/c/425163/14:03
*** baoli has quit IRC14:03
acabotalexchadin : thx Alex, looks great14:04
sballe_alexchadin: I like your plans!14:04
*** pmesserli has joined #openstack-meeting-414:04
alexchadinacabot, sballe_, vincentfrancoise thank you!14:04
hvprashgreat alexchadin !14:05
alexchadinhvprash: thank you!14:05
acabot#info alexchadin has submited his candidacy as Watcher PTL https://review.openstack.org/#/c/425163/14:05
acabot#info Meeting time for odd weeks will be moved from 9:00 UTC to 13:00 UTC on #openstack-meeting-alt14:06
acabotas requested by US contributors14:06
sballe_all thx a million for agreeing to move the time :-)14:06
hvprash+114:06
acabotI hope it will be easier for you guys and still compatible with asian agenda14:06
acabot#link https://review.openstack.org/#/c/425107/14:06
sballe_acabot: It will be for me since I have been travling a lot to CA and it was at 1am i nthat timezone14:07
acabotas soon as the review will be merged we will met at 13 UTC on #openstack-meeting-alt14:07
Yumenghi guys14:07
sballe_hi14:07
alexchadinhi Yumeng14:07
vincentfrancoisehi Yumeng14:07
acabothi Yumeng14:07
Yumengthank you  such warm welcome!14:08
acabotYumeng : our weekly meeting on odd weeks will be moved to 13 UTC14:08
acabotYumeng : I hope its still good for you14:08
acabot#info PTG is in one month, a dedicated etherpad is now open, please submit topics that you want to discuss14:08
acabot#link https://etherpad.openstack.org/p/pike-watcher-ptg14:09
acabotplease add at least your name in the attendees list14:09
acabotI hope to have around 10 people here but I still dont know who bought a ticket14:09
acabotthx chrisspencer14:10
chrisspencer:)14:10
sballe_acabot: we got travel approval for pshedimb and chrisspencer14:10
sballe_chrisspencer: +214:10
*** galstrom is now known as galstrom_zzz14:10
acabotok Yumeng any update on your visa approval ?14:10
Yumengnot yet14:11
acabotok14:11
*** bobh has joined #openstack-meeting-414:11
acabotfeel free to add topics in the list even if you dont plan to be in Atlanta14:11
acabot#info Call for presentations for Boston summit is now open (deadline is February 6th), a dedicated etherpad is ready to be completed14:11
acabot#link https://etherpad.openstack.org/p/Watcher_abstracts_boston201714:11
acabotYumeng : thx for your contribution14:12
acabotif we could submit at least 3 talks next week it would be great14:12
Yumengacabot: :)14:12
sballe_I will submit one today14:12
acabotsballe_ : thx14:12
acabot#info Watcher CLI has been released as 1.0.014:13
acabot#link https://releases.openstack.org/ocata/#ocata-python-watcherclient14:13
acabotthx dtardivel & vincentfrancoise14:13
sballe_alexchadin: since you are our new PTL you should be on the Watcher, the Infrastructure Optimization service for OpenStack: Plans for the P&Q-releases14:13
acabotsballe_ : I think we can wait for the end of the week to see if we have any other candidate ;-)14:14
sballe_For some reasons I am thinking that only two speakers can be on talks. If that is true I would suggest you and acabot on the talk14:14
sballe_acabot: make sense14:14
acabot#topic Review Action Items14:14
*** openstack changes topic to "Review Action Items (Meeting topic: watcher)"14:14
acabotSpecs14:14
acabotAdd improvements to the planner and workflow mechanisms needs a final core review before release14:14
alexchadinsballe_: 95% I'll be in Boston14:14
acabot#link https://review.openstack.org/#/c/385871/14:15
*** cleong has joined #openstack-meeting-414:15
acabotsballe_ : could you do a W+1 on this ?14:15
*** sdague has joined #openstack-meeting-414:15
sballe_yes14:15
acabotsballe_ : all code has been merged already14:15
alexchadinsballe_: code already has been merged14:15
*** matrohon has joined #openstack-meeting-414:15
acabot#sballe_ : W+1 on https://review.openstack.org/#/c/385871/14:15
acabot#action sballe_ : W+1 on https://review.openstack.org/#/c/385871/14:15
acabotDefine grammar for workload characterization needs a new PS answering previous comments14:16
acabot#link https://review.openstack.org/#/c/377100/1914:16
acabothvprash : what's the status for this spec ?14:16
hvprashacabot, there are still certain things unclear for the workload characterization. would have to discuss during the design summit14:16
hvprashi am working on the PS though14:16
*** dave-mccowan has joined #openstack-meeting-414:17
hvprashmay have to move this to Pike14:17
acabothvprash : ok please add it in the topics list then, I think its a major topic we have to discuss14:17
dtardivelsballe_: give me more time to review it please #link https://review.openstack.org/#/c/385871/14:17
sballe_ok14:17
hvprashyes, will do14:17
acabot#action hvprash add a new PS for https://review.openstack.org/#/c/377100/ and add it to the topics list in https://etherpad.openstack.org/p/pike-watcher-ptg14:18
acabotSupport Description For Dynamic Action needs a new PS14:18
acabot#link https://review.openstack.org/#/c/401111/14:18
acabotis hanrong here ?14:18
acabotYumeng : any update on this spec ?14:19
acabotNoisy Neighbor Strategy has still work in progress14:19
acabot#link https://review.openstack.org/#/c/398162/14:19
*** cathrich_ has joined #openstack-meeting-414:20
acabotsballe_ : could you please complete it ?14:20
Yumengacabot: I will pass the message :)14:20
acabotYumeng : ok thx14:20
sballe_acabot: yes. we got our systems working this week so we are now good to go. I will finish the spec14:21
acabotthx14:21
acabot#action sballe_ complete https://review.openstack.org/#/c/398162/14:21
acabotsballe_ : this strategy could be a good candidate for Watcher talk in Boston14:21
sballe_yes thta is the talk I am submitting14:22
acabotsballe_ : ok14:22
acabotAudit tag in VM Metadata needs reviews14:22
acabot#link https://review.openstack.org/#/c/391374/14:22
acabotthx hvprash for adding a PS14:22
*** psachin has quit IRC14:22
hvprashsballe_ vincentfrancois - need your help on this. pls review. pksingh and sanfern have started looking into the code.14:22
acabotwho wants to review it ?14:22
alexchadinacabot: tag me14:23
acabot#action sballe_ vincentfrancoise acabot alexchadin review https://review.openstack.org/#/c/391374/14:23
hvprashi would need vincent to take a look and have some clarifications on the cluster data model14:23
hvprashthabnks alexchadin14:23
*** cathrichardson has joined #openstack-meeting-414:23
acabotmoving to Watcher14:23
vincentfrancoisehvprash: well, this week I'm still busy to finalize the release but we can discuss about it next week14:23
hvprashjust need 10 mins of your time. after this meeting ?14:24
acabotwe should release Watcher O3 tomorrow so a lot of code has been merged recently14:24
vincentfrancoisehvprash: oh ok then14:24
hvprashthx a lot14:24
*** cathrich_ has quit IRC14:24
acabot#info New default planner has been merged #link https://review.openstack.org/#/c/406991/14:25
*** sanfern has joined #openstack-meeting-414:25
acabotthx alexchadin vincentfrancoise for this great addition14:25
alexchadin2(!) new default planners:D14:25
alexchadinthanks vincentfrancoise14:25
vincentfrancoisealexchadin: sure :p14:25
acabotalexchadin : yes now we have 2 planners :-)14:25
acabotgood to see that the plugin system works well14:26
vincentfrancoiseacabot: just need to be able to be able to select one in PIke :)14:26
acabotvincentfrancoise : yes indeed14:26
acabot#info Graph cluster model instead of mapping one & Remove obsolete Resource element have been merged14:26
acabotthx tmetsh & vincentfrancoise for this14:26
acabotall this work really improve watcher14:27
acabotFix multinode tempest test failure multinode gate is still being fixed14:27
vincentfrancoisethx to intel folks for also giving us  a good starting point to integrate cinder and neutron data in the future14:27
acabot#link https://review.openstack.org/#/c/419544/14:27
*** cathrichardson has left #openstack-meeting-414:28
sballe_vincentfrancoise: +114:28
acabotsballe_  : as the graph model is now used by watcher, you should probably check that all Intel's strategies are still working14:28
vincentfrancoiseacabot: +114:29
sballe_acabot: make sense. chrisspencer can you do that?14:29
acabotbecause we check only workload consolidation & dummy strategies with the gate14:29
vincentfrancoiseall strategies aren't covered by integration tests so can you all test the strategies14:29
sballe_acabot: can you add an action for chrisspencer14:29
acabotsure14:29
acabot#action chrisspencer check that existing Intel strategies are still working with graph model implementation14:30
acabotso our multinode tempest gate still has problems14:30
acabotvincentfrancoise is investigating it14:31
vincentfrancoiseacabot: we are getting there though14:31
acabotwe hope to have it fixed before the release to test Watcher in multinode14:31
*** bobh has quit IRC14:31
vincentfrancoiseacabot: but right now people are merging code big time so things are moving slow14:31
acabot#action vincentfrancoise Fix multinode tempest test failure https://review.openstack.org/#/c/419544/14:32
acabotcheck the state of action plan needs final core reviews14:32
acabot#link https://review.openstack.org/#/c/391383/14:32
acabotwho wants to review this last BP for O3 ?14:32
acabotdoes anyone wants to fix the merge conflict ?14:33
dtardivel=&14:33
dtardivel+114:33
acabotok thx14:33
acabot#action dtardivel fix merge conflict for https://review.openstack.org/#/c/391383/14:33
acabotwho wants to review it before merge tomorrow ?14:34
vincentfrancoiseacabot: I'll work with dtardivel on it I guess14:34
acabot#action vincentfrancoise review https://review.openstack.org/#/c/391383/14:34
acabotDocumentation update needs reviews14:34
acabot#link https://review.openstack.org/#/c/424187/14:35
*** tlbr has quit IRC14:35
acabotdtardivel reviewed our current doc before the release14:35
acabotand provides a new architecture diagram14:35
acabotI think its good for all to take a look at it14:35
acabothttp://docs-draft.openstack.org/87/424187/8/check/gate-watcher-docs-ubuntu-xenial/1dfdacb//doc/build/html/architecture.html14:36
alexchadin+114:36
*** Swami has joined #openstack-meeting-414:36
acabot#action alexchadin sballe_ hvprash acabot review https://review.openstack.org/#/c/424187/14:36
acabotadd Ocata release notes needs reviews14:37
hvprashwill do14:37
acabot#link https://review.openstack.org/#/c/421281/14:37
acabotI have created Reno release notes for Ocata14:37
acabotI would really like to have a quick feedback about it before merging it14:38
sballe_dtardivel: I guess joe W+1 https://review.openstack.org/#/c/385871/ right now and didn't wait for you to review :-(14:38
acabotwho wants to review release notes ? (its really quick)14:39
sballe_+114:39
chrisspenceracabot: will do14:39
hvprash+114:39
acabot#action sballe_ chrisspencer hvprash review https://review.openstack.org/#/c/421281/14:39
acabotthx14:39
acabotAdd period input parameter to basic strategy is in merge conflict14:39
acabot#link https://review.openstack.org/#/c/416432/14:40
acabotI dont think hidekazu is here14:40
acabotvincentfrancoise : should we merge it for o3 ?14:40
acabotor it can wait14:40
dtardivelI can resolv this issue as well14:40
alexchadin+114:40
alexchadincan resolve14:40
vincentfrancoiseacabot: we could14:40
vincentfrancoiseacabot: it's a nice to have only though14:41
acabot#action alexchadin fix merge conflict on https://review.openstack.org/#/c/416432/14:41
acabot#action dtardivel merge https://review.openstack.org/#/c/416432/ in o314:41
acabot#topic Blueprint/Bug Review and Discussion14:41
*** openstack changes topic to "Blueprint/Bug Review and Discussion (Meeting topic: watcher)"14:41
acabot#info Ocata 3 Milestone, with Feature and Requirements Freezes: 26 Jan14:42
acabot#link https://launchpad.net/watcher/+milestone/ocata-314:42
acabotwe still have bugs and 1 BP in progress14:42
acabotI plan to submit the release in 24h14:42
acabotatuly_ : are you still working on https://bugs.launchpad.net/watcher/+bug/1640099 ?14:43
openstackLaunchpad bug 1640099 in watcher "Add tempest test for workload_stabilization" [Low,Triaged] - Assigned to Atul Pandey (atul-4you)14:43
acabot#info Ocata RC1 target: 2 Feb14:44
acabot#link https://launchpad.net/watcher/+milestone/ocata-rc114:44
*** spotz is now known as spotz_zzz14:44
acabothvprash : I will move your 2 BPs to Pike14:44
hvprashthanks acabot14:45
acabot#action acabot move hvprash BPs to Pike cycle14:45
acabot#info Ocata Final Release candidate deadline: 16 Feb14:46
acabot#link https://launchpad.net/watcher/+milestone/ocata-rc-final14:46
acabotso we will have at least 3 weeks to run tests between tomorrow and the final release14:46
*** Yumeng has quit IRC14:47
*** TxGirlGeek has joined #openstack-meeting-414:47
acabotI hope everyone will run tests on master branch during this period14:47
acabotas we are targeting 1.0.0 version14:47
acabot#topic Open discussions14:48
*** openstack changes topic to "Open discussions (Meeting topic: watcher)"14:48
*** bobmel has joined #openstack-meeting-414:48
hvprashi have an open discussion topic14:48
*** rbak has joined #openstack-meeting-414:48
acabothvprash : please go ahead14:48
hvprashwith the monasca helper, does that mean the existing strategies needed to be modified too ?14:49
alexchadinI've done all BPs related to Applier except limiting14:49
hvprashexisting action plans14:49
alexchadinI think it is time for that old BP14:49
vincentfrancoisehvprash: yes we still need to make each one Monasca-compatible14:49
alexchadinvincentfrancoise: have you installed it yet?14:50
*** matrohon_ has joined #openstack-meeting-414:50
vincentfrancoisealexchadin: you mean Monasca? Yes dtardivel did in our lab14:51
acabothvprash : yes you have to modify the strategy like this https://review.openstack.org/#/c/414617/14:51
hvprashvincentfrancois - so we will be maintaining multiple versions or something configurable ?14:51
hvprashthanks vincent. that helps.. will go thru it14:52
alexchadinvincentfrancoise: yeah, Monasca. Do you have proper installation guide? There are a lot of technologies to be configured well14:52
*** bobmel_ has joined #openstack-meeting-414:52
vincentfrancoisehvprash: well each strategy has to provide a datasource switch like I did for basic_consolidation14:52
dtardivelalexchadin: please have a look on https://github.com/b-com/ansible-monasca14:53
hvprashgot it !14:53
*** matrohon has quit IRC14:53
vincentfrancoisehvprash: but some like IPMI based do not have the corresponding metrics in Monasca I believe so this can be a bit complicated14:53
*** bobmel has quit IRC14:53
hvprashok14:53
alexchadindtardivel: thanks!14:54
*** yfauser has joined #openstack-meeting-414:54
*** yfauser has quit IRC14:54
acabotalexchadin : alex, could you please send an email on the ML with your PTL candidacy ?14:54
vincentfrancoisealexchadin: I also have a quick memo to configure the libvirt metrics somewhere if you want14:54
alexchadinvincentfrancoise: If I need them I will let you know:)14:55
*** hongbin has joined #openstack-meeting-414:55
*** matrohon__ has joined #openstack-meeting-414:55
alexchadinacabot: yeah, just the message with the same content?14:55
acabotalexchadin : yes please14:55
alexchadinacabot: will do14:55
acabot#action alexchadin share PTL candidacy on the ML14:56
acabotthank you all14:57
*** marst has joined #openstack-meeting-414:57
acabothave a good day/night14:57
alexchadinbye14:57
hvprashthanks !14:57
hvprashbye14:57
acabotbye14:57
acabot#endmeeting14:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:57
openstackMeeting ended Wed Jan 25 14:57:24 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/watcher/2017/watcher.2017-01-25-14.01.html14:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/watcher/2017/watcher.2017-01-25-14.01.txt14:57
openstackLog:            http://eavesdrop.openstack.org/meetings/watcher/2017/watcher.2017-01-25-14.01.log.html14:57
*** matrohon_ has quit IRC14:57
sballe_bye14:57
*** shintaro has joined #openstack-meeting-414:58
*** TxGirlGeek has quit IRC14:58
*** chrisspencer has left #openstack-meeting-414:58
*** TxGirlGeek has joined #openstack-meeting-414:58
*** bklei has joined #openstack-meeting-415:00
*** woodard has quit IRC15:00
serverascode#startmeeting operators_telco_nfv15:00
openstackMeeting started Wed Jan 25 15:00:34 2017 UTC and is due to finish in 60 minutes.  The chair is serverascode. 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: operators_telco_nfv)"15:00
openstackThe meeting name has been set to 'operators_telco_nfv'15:00
*** vincentfrancoise has left #openstack-meeting-415:00
serverascodehello :)15:00
uli-khello15:00
shintarohi15:01
*** ad_rien_ has joined #openstack-meeting-415:01
ad_rien_o/15:01
serverascodeI'll give it another minute or so15:01
serverascodeif you hav eanything to add to the agenda, please go ahead :)15:02
serverascode#link https://etherpad.openstack.org/p/ops-telco-nfv-meeting-agenda15:02
jamemccHi15:02
serverascode#topic Weekly Meetings15:03
*** openstack changes topic to "Weekly Meetings (Meeting topic: operators_telco_nfv)"15:03
serverascodeNot sure if anyone has an opinion on this, or I could push it to the next meeting15:03
serverascodeit was mentioned last meeting that perhaps we should move to weekly meetings15:03
ad_rien_cannot on my side15:03
ad_rien_to be honest15:03
ad_rien_One week I have to chair the massively distributed WG15:04
*** GeraldK has joined #openstack-meeting-415:04
ad_rien_and the other one, I attend this meeting15:04
ad_rien_it becomes to costly for me to attend all Openstack meeting15:04
ad_rien_s15:04
ad_rien_sorry15:04
serverascodeyeah I would like to start attending the massively distributed group more often myself15:04
GeraldKhi15:04
serverascodehi GeraldK :)15:04
ad_rien_but if you believe it is mandatory, I will read the minutes15:04
ad_rien_go ahead15:04
serverascodeI'm happy with bi-weekly meetings myelf15:04
ad_rien_just to let you know that I will be not able to do more right now15:05
serverascodeanyone else have any strong feelings about it? otherwise I will suggest we revisit in a couple months15:05
jamemccevery 2 weeks is good for me15:05
serverascodeok, I put up a reminder to revist in a while15:06
serverascode#topic Boston Summit15:06
*** openstack changes topic to "Boston Summit (Meeting topic: operators_telco_nfv)"15:06
GeraldKevery 2 weeks would be okay for me. Anyway, I have a meeting clash at this time.15:07
serverascodeOver the last couple days there has been some discussion on doing a presentation and session on multi-site/multi-cloud15:07
serverascodeso if anyone is interested in that, let me know, as we will start to put together and abstract to submit by Feb 6th15:08
ad_rien_So what is your idea right now ?15:08
ad_rien_are there notes somewhere?15:08
*** TxGirlGeek has quit IRC15:08
serverascodeno notes yet, just joehuang and I were discussing it, and we wanted to chat with you ad_rien_ regarding the Massively Dist. team15:09
*** spotz_zzz is now known as spotz15:09
serverascodeI think overall it was just that there is a lot of confusion regarding multi-site/cloud and we should help to clear that up :)15:09
ad_rien_ok so the idea on our side is to present some performance evaluations of the scenario 115:09
shintarois it from OPNFV? sounds interesting although i do not have any experience on the topic.15:09
shintaroI mean muti-site15:09
* ad_rien_ is looking for links15:10
serverascodeI think OPNFV has a project related to multi-site15:10
serverascodebut I'm more talking about an overview of all the different methods15:10
ad_rien_#link https://docs.google.com/presentation/d/1jJFZejZqgYDxu5FX4K8g3I5zQ87afnjYI4VSRSuCQ6U/edit#slide=id.p15:10
ad_rien_so basically we identified the different scenarios that can be done right now with the vanilla openstack code.15:11
serverascodemulti-region, multi-site, related projects like kingbird, tricircle, connecting tenant networks in different clouds, massively distributed, fog, edge...etc etc :)15:11
GeraldKcool, thanks, thats a nice summary...15:11
ad_rien_We implemented a tool dedicated to perform experiments. We plan to submit a presentation regarding the scenario 115:11
shintarolooks interesting topic15:11
ad_rien_This should be tagged by the performance team15:11
ad_rien_as discussed with DinaBelova yesterday15:12
*** sdague has quit IRC15:12
ad_rien_We can probably do another presentation that aims to clarify what is behind NFV infrastructures/massively distributed/Fog/Edge infrastructures15:12
serverascodeyeah I agree ad_rien_15:13
ad_rien_and what is the link w-r-t the openstack community15:13
ad_rien_I think it might be valuable (in addition to see whether we should not merge all the different WGs at the end ;) )15:13
serverascode:)15:13
serverascodeok, if you are interested in participating in putting forward that presenation and session, let me know and I will make sure to let you know what we are up to15:14
serverascodeI will also report back next meeting15:14
ad_rien_We can also try to identify what are the production platform that are already deployed15:14
ad_rien_We know the NECTAR one and the CERN one15:14
ad_rien_I'm sure there are others15:14
ad_rien_ATT has a massively distributed clouds but they are using their own glue to orchestrate the different openstack deployment15:15
serverascoderight, existing deployments would be a good to include15:15
*** leo_wang has quit IRC15:15
serverascodeany other ideas on presentation topics this group could perhaps put forward?15:16
uli-kMaybe Joe knows more. I heard something he will engage in the massive distributed cloud activity.15:16
* uli-k (sorry I had nipped out a few minutes....)15:16
serverascodeI will still put forward a NFV session for Boston15:17
ad_rien_sounds good15:17
serverascodeto be more clear, a working group meeting for this group15:18
serverascodeat the boston summit15:18
ad_rien_sounds good15:18
serverascodeis there anything specific we want to achieve in that meeting? or leave it more general?15:18
ad_rien_will do the same for the massively distributed15:18
ad_rien_I will ask to do not schedule the two sessions at the same time15:18
serverascodegood idea :)15:18
ad_rien_Can you do the same serverascode please?15:18
serverascoderight will do15:18
ad_rien_thanks15:18
serverascodefor previous sessions they are often quite full, but end up being more like an general informational session on the what the working group is15:19
*** yfauser has joined #openstack-meeting-415:20
serverascodeand it doesn't necessarily move us forward all that much, though may help to find additional participants15:20
serverascodeactually it looks like our next meeting is after the deadline for submissions15:21
serverascodeso I will have to submit it before next meeting15:21
jamemccRegarding what to acheive in Boston.  Seems there is interest from those attending the Summit/Meetup.  Maybe we can hold the session to explore/document the varieties of the attendees NFV use cases.  Maybe we start with some fo the conversation we've had here.15:21
serverascodeok, that is interesting. Would make use of the varied people attending the session.15:22
jamemccKind of 2 fold - if we voted by end of the session we'd get some #'s as to the types and all in all might encourage those with the use cases that interest them to participate.15:23
jamemccWhat was the approcah in Barcelona Curtis - I was there but forgetting.  How did you kick it off?15:24
serverascodeBarcelona was pretty random15:24
serverascodeit was a small room, lots of people, and mostly it ended up being a discussion about what the working group actually is15:24
*** vmahe_ has quit IRC15:24
serverascodeperhaps people came out understanding what we are doing, but that was about it :)15:24
shintaro40min was a little too short I guess15:25
serverascodeyeah it is very very short15:25
ad_rien_you can ask two consecutive slots?15:25
ad_rien_we ask that for the massively distributed15:26
ad_rien_it was enough I think15:26
serverascodeyeah that's an interesting idea, usually they are pretty limited on slots though, but yeah 40 min is so little15:26
serverascodeI will give it a shot :)15:26
GeraldKin Barcelona we had collected many topics during that session but failed to attract people to IRC meetings to further discuss on them15:27
*** Syed__ has joined #openstack-meeting-415:27
GeraldKtwo slots could help to categorize/priorituze topics and also discuss next steps15:28
*** TxGirlGeek has joined #openstack-meeting-415:28
serverascoderight I am probably oversimplifying what we actually discussed, I should find the etherpad...15:28
serverascode#link https://etherpad.openstack.org/p/BCN-ops-telcom-nfv-team15:28
ad_rien_the other good point of having two consecutive slots is that you get people that are really interested to take part to the effort15:28
*** yfauser has quit IRC15:28
ad_rien_i.e. folks that are not interested usually leave the room after 40 mins15:29
*** baoli_ has quit IRC15:29
serverascodeis there anything in that etherpad that we could or should focus on for the session?15:29
serverascodewell, we can certainly alter the focus of the session later, now that I think about it the abstract doesn't have to be super specific15:30
GeraldKserverascode: +115:31
*** markvoelker has quit IRC15:31
*** markvoelker has joined #openstack-meeting-415:32
*** bobh has joined #openstack-meeting-415:32
serverascodeok next topic15:32
serverascode# Generic NFV Platform Defintion Document15:32
*** SridharP has joined #openstack-meeting-415:32
serverascodeI started a bit of work on this in terms of starting a table of contents15:32
serverascode#link https://etherpad.openstack.org/p/generic-nfv-platform15:32
serverascodewith the idea being of starting the document in that etherpad, filling it out as a first draft, then getting it into the git repo15:33
ad_rien_+115:33
ad_rien_good work15:33
serverascodethanks, it's really just an initial skeleton that needs a lot more work :)15:34
serverascodebut the etherpad is there, and if you have suggesions now or in the future, please feel free to make them :)15:34
ad_rien_yes but at least it gives one direction15:34
jamemccIt does look like a good outline - this is how we would would document the Reference Architecture?15:34
serverascodeI think so, my idea was to cover some NFV related background, then define an example architecture in one of the later sections15:35
serverascodeand that reference arch would be fairly prescriptive, but would juts be one example15:35
ad_rien_I don't know whether it will be reachable but I think you have a good outline for the presentation ;)15:36
*** markvoelker has quit IRC15:36
*** bobh has quit IRC15:37
*** woodard has joined #openstack-meeting-415:37
serverascodeyeah it will be tough to keep the scope limited enough to actually finish it and provide something useful15:37
serverascodeI see some additions already :) thanks!15:38
GeraldKso, in setion 4 you'd like to collect basic features that should be there for a generic NFV platform?15:39
GeraldKcan we add a kind of Note on each section to explain what it should be about?15:39
serverascodeyup, or at least list the ones that are available in production15:39
GeraldKdo we need "advanced NFV features" for a generic NFV platform?15:40
serverascodegood point, I was thinking that we might have to at least mention them as I find that is where a lot of confusion comes int15:40
serverascodeor perhaps some way of determining what is "production" worthy15:40
*** TxGirlGeek has quit IRC15:41
GeraldKso this is to differentiate what is "generic/basic NFV features" and "additional advanced featues"?15:41
*** jschwarz is now known as jschwarz|brb15:41
ad_rien_just one question (please take into account that I'm not involved in the OPENNFV community)15:42
serverascoderight, perhaps 'advanced' is the wrong word15:42
ad_rien_Is there any overlappings with OPNFV actions15:42
ad_rien_It looks to be general (i.e; interesting but general)15:42
ad_rien_The focus should not be done on the OpenStack ?15:42
*** rhallisey has joined #openstack-meeting-415:42
*** rhallisey has left #openstack-meeting-415:42
GeraldKad_rien_: I'd say so. however, for OPNFV I have not seen such a structured approach like serverascode has started here15:43
ad_rien_ok15:43
GeraldKand OPNFV is more than OpenStack; however, including SDN in the list, this might also go beyond here15:43
shintarobut we can pick stuff from OPNFV requirements15:44
ad_rien_one more question15:44
ad_rien_What about having a use-case that can guide the discussion15:44
GeraldKshintaro: certainly yes. I'd even love to see both work together on such a document.15:44
ad_rien_(i.e. don't know; cloudRan for instance if it makes sense)15:44
*** jose-phillips has joined #openstack-meeting-415:44
serverascodea use case might be a good idea15:44
*** zeih has quit IRC15:45
serverascodefor the SDN section, I think it's valuable to discuss b/c at some point basic neutron might have all the features one would require from an SDN :)15:45
serverascodeI mean if if gets service function chaining... :)15:45
GeraldKthis is something I also had in mind with the previous topic and the long list of interesting topics from last Summit: let's try to see which topics could be well described by a user story and let's propose such user story in the PWG if it does not yet exist15:45
GeraldKserverascode: you're right15:46
*** Swami_ has joined #openstack-meeting-415:46
*** krtaylor has joined #openstack-meeting-415:47
shintaroserverascode VNF can come in containers as well or may need to connect with PNF(physicalNF) so it might go beyond Neutron15:48
GeraldKabout "3. commen theme use case": do you have a use case in mind why we need a generic NFV platform or a use case how it could be used or something different?15:48
*** jschwarz|brb is now known as jschwarz15:48
serverascodeshintaro good point, I haven't even begun to consider containers in NFV yet but they are important15:49
ad_rien_The idea is to introduce a use-case that will act as a common theme for all following aspects15:49
ad_rien_This should make the read and the understanding easier (I'm not sure we can be exhaustive i.e. covering all use-cases)15:49
ad_rien_I can be wrong ;)15:49
*** Swami has quit IRC15:49
*** SridharP1 has joined #openstack-meeting-415:50
serverascodesome kind of VNF that has clustering built into the application would probably be the baseline15:50
serverascodenot sure what that would be15:50
*** Sukhdev has joined #openstack-meeting-415:51
serverascodeI find lots of telecoms struggle with the lack of "instance HA" in openstack15:51
serverascodethey want to run single isolated workloads and have them magically be restarted if the hypervisor fails15:51
*** mandre has joined #openstack-meeting-415:51
*** duonghq has joined #openstack-meeting-415:51
serverascodeI know there are some projects in the big tent to do that, but generally speaking that is not a usecase openstack supports15:52
*** SridharP has quit IRC15:52
*** trinaths has joined #openstack-meeting-415:52
shintaroyeah we are working on that project. but that is for "legacy"apps15:53
serverascodeok, so we have about 7 minutes left, should we go into open discussion?15:53
*** inc0 has joined #openstack-meeting-415:53
*** sdake_ has joined #openstack-meeting-415:53
shintaroI want to make sure whether we will have a session/meetup in OpsMeetup in Milano15:54
serverascode#topic open discussion15:54
*** openstack changes topic to "open discussion (Meeting topic: operators_telco_nfv)"15:54
serverascodeshintaro: good call15:54
shintaroSession discussion is open and now is time to fix it15:54
*** jchhatbar has quit IRC15:55
serverascodewhere is the discussion happening now? still in the etherpad?15:55
shintaro#link https://etherpad.openstack.org/p/MIL-ops-meetup15:55
*** caboucha has joined #openstack-meeting-415:55
*** mliima has joined #openstack-meeting-415:55
ad_rien_I'm lost sorry15:55
ad_rien_ok15:55
ad_rien_I'm back15:56
ad_rien_sorry15:56
*** vikasc has quit IRC15:56
serverascodethere is an operators meeting in Milan in March, and we might have a session there :)15:56
ad_rien_taking about the Milano meetup15:56
*** sdake has quit IRC15:56
shintaroRegistration is now open, too15:56
serverascodeI think some people from the LCOO will be there?15:56
shintaro#link https://opsmidcycle_march2017.eventbrite.com15:56
serverascodethe NFV session discussion got a little confused when I think Chris was suggesting maybe it's not a session15:57
serverascodebut it depends on how many NFV related pepole will be there15:57
serverascodeusually there are only one or two15:57
*** lei-zh has quit IRC15:57
serverascodeeveryone else is not doing anything that they would consider NFV15:57
serverascodeoh but now I see some +1s :)15:57
*** egonzalez has joined #openstack-meeting-415:57
shintaroLCOO decided not to have an official WG meeting there but some members will be there, I guess.15:58
*** bobmel_ has quit IRC15:58
serverascodeso you and I will be there, but I'm wondering who else?15:58
*** gema has joined #openstack-meeting-415:59
*** KunalGandhi has joined #openstack-meeting-415:59
serverascodeoh one min left :)15:59
ad_rien_Not me15:59
serverascodeI will have to end the meeting soon15:59
*** bobmel has joined #openstack-meeting-415:59
ad_rien_but if we can attend by a webconf tool it would be great15:59
ad_rien_;)15:59
serverascodeshintaro: if you have time we can continue the discussion by email or irc15:59
*** zhubingbing has joined #openstack-meeting-415:59
shintarook, but email would be better since its 1am for me15:59
serverascodeif you want you can email me at curtis@serverascode.com16:00
*** Serlex has joined #openstack-meeting-416:00
*** srwilkers has joined #openstack-meeting-416:00
serverascodeand we can discuss that way or setup a time16:00
serverascodegotta end meeting!16:00
serverascode#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Wed Jan 25 16:00:21 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2017/operators_telco_nfv.2017-01-25-15.00.html16:00
serverascodethanks everyone!16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2017/operators_telco_nfv.2017-01-25-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2017/operators_telco_nfv.2017-01-25-15.00.log.html16:00
*** mgiles has joined #openstack-meeting-416:00
shintarothanks16:00
GeraldKbye16:00
*** bklei_ has joined #openstack-meeting-416:00
zhubingbingthanks16:00
*** GeraldK has quit IRC16:00
zhubingbingbye16:00
zhubingbing;)16:00
inc0allright16:00
inc0#startmeeting kolla16:01
zhubingbinghey16:01
openstackMeeting started Wed Jan 25 16:01:02 2017 UTC and is due to finish in 60 minutes.  The chair is inc0. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: kolla)"16:01
openstackThe meeting name has been set to 'kolla'16:01
*** portdirect has joined #openstack-meeting-416:01
*** bklei_ has quit IRC16:01
*** shintaro has quit IRC16:01
inc0#topic w00t for kolla16:01
*** openstack changes topic to "w00t for kolla (Meeting topic: kolla)"16:01
trinathsHi16:01
inc0w00t people16:01
inc0;)16:01
duonghqo/16:01
zhubingbingo/16:01
gemao/16:01
zhubingbingo/16:01
SridharP1Hai16:01
duonghqoops16:01
Jeffrey4l_o/16:01
trinathshi16:01
pbourkew00t16:01
srwilkerso/16:01
portdirectgood afternoon16:01
mandreo/16:01
* portdirect w00t16:01
zhubingbinggood afternoon16:01
srwilkers:is all out of woots to give16:02
inc0and it's only 8am? your day is looking bright srwilkers16:02
*** cathrichardson has joined #openstack-meeting-416:02
egonzalezwoot o/16:02
krtayloro/16:02
trinathso/16:03
SridharP1o/16:03
*** sdague has joined #openstack-meeting-416:03
*** bklei has quit IRC16:03
inc0#topic agenda16:03
*** ad_rien_ has left #openstack-meeting-416:03
*** openstack changes topic to "agenda (Meeting topic: kolla)"16:03
inc0* Roll-call16:04
inc0* Announcements16:04
inc0* Documentation (pbourke)16:04
inc0* Ocata kolla deliverable (inc0}16:04
inc0* Ocata kolla-ansible deliverable (inc0)16:04
inc0* kolla-kubernetes 0.5.0 (sdake) timebox [10 minutes]16:04
inc0* deprecation of Debian images (berendt)16:04
inc0* Debian images for ARM architecture (gema, berendt)16:04
inc0* Finalize Brainstorming of PTG topics (we have 2 days of PTG space) timebox [10 minutes]16:04
inc0* Open Discussion16:04
inc0#topic announcements16:04
*** openstack changes topic to "announcements (Meeting topic: kolla)"16:04
inc0We came into agreement how to add new deliverables16:04
*** SergeM has joined #openstack-meeting-416:04
inc0it will be change to this file https://review.openstack.org/#/c/424784/16:05
*** srwilkers has quit IRC16:05
inc0and merge as usual with caveat of PTL +2 present16:05
*** srwilkers has joined #openstack-meeting-416:05
inc0any community announcements?16:05
inc0guess not:) let's get to business16:06
inc0#topic Documentation16:06
*** openstack changes topic to "Documentation (Meeting topic: kolla)"16:06
inc0pbourke, you're up16:06
pbourkeok, simple enough really16:06
qwango/16:06
berendto/16:06
*** bmace_ has joined #openstack-meeting-416:06
*** gongysh has quit IRC16:07
pbourkeI had a short note on the ML but the gist is, I think some people are working in the background on revamping the kolla docs16:07
pbourkeI think a lot of people have grand visions of what needs to happen16:07
pbourketill then though, Id like to suggest we take some immeidate steps to remove duplication16:07
*** anilvenkata has quit IRC16:07
berendtdo we have a doc liason for the docs team?16:08
*** jascott1 has joined #openstack-meeting-416:08
pbourkeby that I mean strip down the kolla section to just building info and info related to the image themselves, along with hyperlinks to kolla deliverables that can deploy the images16:08
mliima\o16:08
pbourkeif people like this idea I can submit a change before end of the week16:08
*** SergeM has quit IRC16:08
berendtpbourke: i like it :)16:08
mandrepbourke: +116:08
inc0berendt, officialy no, but we have people talking to them16:09
zhubingbingi have  a problem, the document we have to refer to what to do16:09
berendti think we should think about a central starting page16:09
inc0and some guide which tool to choose16:09
*** sp___ has joined #openstack-meeting-416:09
zhubingbingyes16:09
duonghqpbourke, +1 but Kolla need including some common info too16:09
pbourkesounds like no major concerns with the above so that's it from me :)16:09
zhubingbingwo should need some guide and tools16:09
duonghqpbourke, how about QSG?16:10
berendtgeneric information in kolla docs?16:10
duonghqberendt, sure16:10
berendtduonghq: quick start guide is related to ansible/salt/k8s16:10
berendtevery deliverable needs a qsq16:10
trinaths+1 to qsg16:11
Jeffrey4l_im agree with pbourke.16:11
duonghqso we need one landing page in Kolla and point to deliverables qsg?16:11
Jeffrey4l_kolla QSQ just solve image build. kolla-ansible QSQ just explain how to deploy images.16:11
berendtduonghq: i think this is the best way16:11
duonghqagreed with berendt16:12
pbourkeagain, Id rather not go into all the various improvements needed. My main goal is just to remove the current duplication16:12
berendtJeffrey4l_: +116:12
duonghqfor QSG, we should use images from docker hub (IMO)16:12
berendtpbourke: then i think the best is to start with the split of the qsg and to remove common content from kolla-ansible16:12
zhubingbing+1 pbourke16:12
berendtduonghq: +1 but we also need a qsg how to build images16:13
portdirecti agree with pbourke the first step is seeing what we have, kolla-k8s in particular has a lot of very out of date docs, that need removed or reworked before we promote them16:13
inc0well we do have good doc on it16:13
inc0just not called qsg16:13
duonghqberendt,  not really qsg16:13
SridharP1duonghq: +1 about building images16:13
inc0we can link to it from kolla-ansible qsg16:13
berendtyes, maybe qsg is the wrong wording for it16:13
inc0also, qsg itself can ask people to use dockerhub images16:14
inc0to make stuff even easier16:14
duonghqberendt, something like Basic building instruction (w/ some advanced instructions...)16:14
*** KunalGandhi has quit IRC16:14
Jeffrey4l_we need qsg, event though current "qsg" is too complicate.16:14
berendtdoes it makes sense the pbourke prepares a list for the next meeting?16:14
trinathsberendt: this doc will be the starting point. right ?16:14
duonghqyeah, iirc, sdake is working on that16:14
krtaylordeploy vs building qsg - have a switch at the starting page16:14
*** alexchadin has quit IRC16:14
berendttrinaths: yes16:14
trinathsberendt: then let it be qsg. it gives a good meaning too16:15
*** rainya has joined #openstack-meeting-416:15
Jeffrey4l_i think we need a outline which explain how the doc will looks like in the future in overview. pbourke16:16
*** sean-k-mooney has joined #openstack-meeting-416:16
pbourkehonestly Id rather not commit to that16:16
pbourkeat least right now16:16
zhubingbing+1 Jeffrey4l16:16
inc0yeah we have release16:16
pbourketo reiterate, all I want to achieve is that when you go to http://docs.openstack.org/developer/kolla-ansible/ vs http://docs.openstack.org/developer/kolla/ they actually look different16:16
berendtinclude it in the ptg?16:16
pbourkeright now we have patches going into both, it makes no sense16:17
trinathsJeffrey4l_: oultine mean future plans?16:17
pbourkeit should have happened long ago16:17
berendtlet's freeze kolla-ansible/docs until we start working on it16:17
*** markvoelker has joined #openstack-meeting-416:17
Jeffrey4l_trinaths, yep. bird's eye.16:17
duonghqsorry guys but the improved docs stuff should go in Ocata or Pike?16:17
*** armax has joined #openstack-meeting-416:18
*** zioproto has joined #openstack-meeting-416:18
zioprotohello16:18
berendti think in pike16:18
*** markvoelker_ has joined #openstack-meeting-416:18
zioprotomeeting started ?16:18
berendtzioproto: yes16:18
inc0ok, lets move on16:18
trinathsJeffrey4l_: i believe it to have a roadmap line. and doc t more concentrate on bringing up the environment16:18
zhubingbingzioproto: yes16:18
duonghqso PTG would be better place for further discussion?16:18
inc0(I'm going to cannibalize kolla-k8s from this meeting, sorry, we're in release week(16:19
inc0#topic ocata-316:19
*** openstack changes topic to "ocata-3 (Meeting topic: kolla)"16:19
berendtduonghq: i think so16:19
inc0https://launchpad.net/kolla-ansible/+milestone/ocata-316:19
inc0https://launchpad.net/kolla/+milestone/ocata-316:19
inc0the list is long and full of not implemented16:20
Jeffrey4l_inc0, which day we have to release m3?16:20
inc0Jeffrey4l_, we'll tag ocata-3 at 27th right?16:20
inc0this week16:20
inc027th is last day16:20
Jeffrey4l_yep. 27th is the last day.16:21
inc0which means I'll be bumping blueprints to Pike16:21
inc0which aren't finished by then16:21
trinathsand there is not assignee and the there is good progress.16:21
*** sayantani01 has joined #openstack-meeting-416:21
*** rainya has quit IRC16:22
*** markvoelker has quit IRC16:22
inc0zhubingbing, whats the status of fluentd?16:23
inc0is it finished?16:23
Jeffrey4l_ inc0 yep.16:23
zhubingbingyes16:23
inc0anyone knows anything about keystone upgrade?16:24
berendtdoes it include an upgrade from heka to fluentd?16:24
*** sacharya has joined #openstack-meeting-416:24
*** sacharya has quit IRC16:24
*** simon-AS559 has joined #openstack-meeting-416:24
zhubingbingkeka replaced fluentd's work has been completed16:24
Jeffrey4l_berendt, yep. heka will be removed during upgrade from newton to ocata16:24
inc0changed to implemented16:24
inc0good job!16:24
berendtJeffrey4l_: good :)16:24
inc0https://blueprints.launchpad.net/kolla/+spec/ks-rolling-upgrade-role <- this needs to happen16:25
*** TxGirlGeek has joined #openstack-meeting-416:25
duonghqsp___, are you there?16:25
Jeffrey4l_this should be moved to P cycle ;(16:25
*** rainya has joined #openstack-meeting-416:25
inc0without this KS might break upgrade, and have right to do so16:26
sean-k-mooneyinc0: will that also handel change such as enableing fernet tokens correctly on upgrade?16:26
Jeffrey4l_seems it is not started. i am afraid this can not be done before release.16:26
Jeffrey4l_sean-k-mooney, i do not think so16:27
duonghqJeffrey4l_, it need some rework due to recent ansible refactoring16:27
inc0sean-k-mooney, negative, this will just make sure we'll handle db changes correctly16:27
egonzalezyup, is under a bug_id instead of the bp https://review.openstack.org/#/c/388544/16:27
inc0https://review.openstack.org/#/c/405215/2 there is some code for it16:27
inc0duonghq, thoughts? you wrote most of the code16:28
inc0think you can get it done?16:28
zhubingbingi can  do  this work ;)if duonghq have free time;)16:29
duonghqduonghq, if tomorrow I can get it done than it can be done, or not, :(16:29
inc0ok, try it16:29
duonghqroger16:29
inc0let me know if you need help, I can take on it too16:29
inc0ok next one https://blueprints.launchpad.net/kolla/+spec/api-interface-bind-address-override16:30
egonzalezme too16:30
inc0I think it's no longer relevant16:30
Jeffrey4l_k8s do not reply on this?16:30
Jeffrey4l_depends on*16:31
Jeffrey4l_inc0, ^16:31
inc0well no movement in this change and k8s seems to handle itself16:31
inc0kfox1111, comments?16:31
*** cathrichardson has left #openstack-meeting-416:32
Jeffrey4l_whether k8s depends on orchestration_engine variable?  kfox1111 inc016:32
portdirectinc0 that was well before my time - but looks like it was working on the assumpption of running in the hosts network namespace?16:33
*** bobh has joined #openstack-meeting-416:33
inc0yeah, and we're not really using host networking everywhere right?16:33
inc0not for apis anyhow16:33
*** SridharP has joined #openstack-meeting-416:33
portdirectwe are using it as little as possible16:34
inc0Jeffrey4l_, yeah this was really mitaka16:34
inc0I'm going to close it for now16:34
portdirectso though nice to have I dont think its causing any issues at present16:34
inc0portdirect, would you be kind enough and double check? we can always reopen16:34
portdirectyeah i'll ask kfox and co, np16:35
*** SridharP2 has joined #openstack-meeting-416:35
*** SridharP1 has quit IRC16:35
inc0https://blueprints.launchpad.net/kolla/+spec/apply-service-upgrade-procedure16:35
inc0this is related to keystone16:35
sean-k-mooneyinc0: is k8s using the docker proxy for apis if so that could be a scaleing problem though i understand why you might want to avoid net=host16:35
inc0sean-k-mooney, k8s doesn't really uses docker proxy afaik16:36
inc0it has it's own network overlay16:36
*** morgabra has quit IRC16:36
duonghqit have some network option, the recommend is flannel16:37
sean-k-mooneyinc0: ack, it should be ok then.16:37
kfox1111o/16:37
inc0but back to topic, duonghq I assume someone will have to take on neutron too right?16:37
*** SridharP has quit IRC16:38
inc0or I see you're working on this change16:38
*** bobh has quit IRC16:38
kfox1111we support both external and host ports currently in kolla-kubernetes.16:38
inc0so let's do this, you focus on neutron16:38
duonghqabout the apply-service-upgrade-procedure, the neutron's ansible potion run into same problem as ks: need to be migrated to new ansible structure16:38
inc0and me and egonzalez will take keystone ok?16:38
kfox1111since ingress is starting to stabalize, we may support that at some point too.16:38
duonghqinc0, nice,16:38
inc0thanks16:38
inc0just get neutron done:) egonzalez I'll start today and by your morning you should have something to work on:)16:39
inc0feel free to coauthor patch16:39
duonghqthank inc0 and egonzalez16:39
egonzalezinc0: roger, i'll check what you got at the morning16:39
inc0https://blueprints.launchpad.net/kolla/+spec/support-python-35 this is doen?16:40
*** cathrichardson has joined #openstack-meeting-416:40
duonghqinc0, it should be depend on code coverage improvement bp16:41
*** idan_hefetz has quit IRC16:41
sean-k-mooneyinc0: Python 3.5 support in some openstack projects is still experimental. i assume this is for the kolla module rather then the containers?16:41
duonghqsean-k-mooney, yup16:42
*** cathrichardson has left #openstack-meeting-416:42
sean-k-mooneyduonghq: cool16:42
berendtsean-k-mooney: yes, should be for kolla itself16:42
inc0yeah, I'll bump it to pike16:42
inc0and all the rest in fact16:42
duonghqfor all Python code, indeed16:42
inc0since these are highs/essentials16:42
inc0#link https://launchpad.net/kolla-ansible/+milestone/ocata-316:42
*** trinaths has left #openstack-meeting-416:43
sean-k-mooneyinc0: would you like me to pre-emptively bump dpdk,odl and hugepage configuration to pike? i doubt they will be merged by the 27th and they are also not currently targeted to ocata-316:43
duonghqinc0, https://blueprints.launchpad.net/kolla/+spec/coverage-increment-for-kolla -> here, last bp should depend on this16:43
inc0sean-k-mooney, yes, please16:43
berendtsean-k-mooney: hugepage yes16:43
berendtsean-k-mooney: i do not have time to work on it at the moment and prio is low16:43
inc0duonghq, then i'll keep this one16:44
inc0since it might be merged16:44
inc0but please, focus on upgrades16:44
duonghqsure16:44
sean-k-mooneyberendt: i have some patches for it up for bootstrap servers playbook.16:44
inc0I'll bump all meds/lows16:44
inc0kolla-ansible doesn't look bad16:45
*** zioproto has quit IRC16:45
inc0ok, let's move on16:45
inc0#topic Debian deprecation16:46
*** openstack changes topic to "Debian deprecation (Meeting topic: kolla)"16:46
duonghqforgot, the apply service upgrade should be done for all service that have rolling upgrade procedure, not just ks and neutron, but ks and neutron have most mature procedure, so in general, part of the bp should be done on Ocata, other in Pike or next...16:46
berendtgema: around?16:46
inc0berendt, gema we wanted to discuss16:46
gemayep16:46
berendtyour turn16:46
*** woodard has quit IRC16:46
inc0gema, question, do you *need* debian containers for ARM?16:46
inc0or ubuntu would work?16:46
gemainc0: our current release is based on Debian and CentOS16:46
gemaso we were planning to produce containers first for debian then for centos16:47
inc0ok, so CentOS would work?16:47
*** woodard has joined #openstack-meeting-416:47
gemainc0: yes, but we prefer debian16:47
inc0issue is, nobody else prefers debian;)16:47
gemasince it is a purely community driven project16:47
gemainc0: all our members are keen on it16:47
gemamost :D16:47
berendtgema: are you willing to working on the debian images?16:47
inc0if you volunteer to be maintainers of it in kolla, we can discuss keeping it16:48
gemaberendt: yes16:48
Jeffrey4l_and please add job gate for debian ;)16:48
inc0yeah, gate job for debian is first step16:48
inc0we'll be happy to help you do it16:48
berendtfirst step is making the debian images working again16:48
gemawe will be working on debian ARM64, I am not sure how much work is involved in also making them work on x86_6416:48
berendtnext step gates for debian16:48
gemabut we don't have hardware to test that16:48
*** klindgren_ has joined #openstack-meeting-416:48
berendtarm64 is the next topic, i think we should discuss the addition of a new platform independent of the debian deprecation16:48
inc0gema, it will have to work on both arm and x86 as gates are all x8616:48
*** mdorman has joined #openstack-meeting-416:49
sean-k-mooneygema i would not expect there to be much if any difference between x86_64 and armv8 in this context16:49
Jeffrey4l_i prefer to add a non-voting debian gate, then fix all issue to make it green.16:49
gemainc0: we will be adding a 3rd party CI for ARM6416:49
berendtJeffrey4l_: +116:49
gemaJeffrey4l_: agreed16:49
inc0gema, fine, but we also want proper openstack CI16:49
Jeffrey4l_gema, re 3rd ci , cool.16:49
gemaberendt, inc0: plus I can only commit resources to do this for pike16:49
inc0and yeah, I don't expect debian to be voting anytime soon16:49
inc0ocata is done anyway16:50
gemawe'll be ramping up in the meantime16:50
gemaok, good16:50
*** bobmel_ has joined #openstack-meeting-416:50
berendtwhen adding debian for arm64, can the current images be used or do you have to add it as a new distro?16:50
inc0so order of business would be:16:50
kfox1111oh. that reminds me. are we in feature freeze yet?16:50
gemaberendt: I don't know16:50
berendtat the moment the debian images are nearly the same like ubuntu16:50
inc01. make sure debian works at all16:50
sean-k-mooneyberendt: it would have to be a new distro16:50
inc0kfox1111, k8s is not16:50
inc0ansible and kolla yeah16:51
kfox1111no, kollla. I'd still like to see https://review.openstack.org/#/c/422950/ go in.16:51
sean-k-mooneyberendt: the binaries in the current image would not work on arm16:51
berendtwhen it would to be a new distro we can deprecate current debian images and add debian arm64 as new images16:51
gemasean-k-mooney: corrent16:51
*** bobmel has quit IRC16:51
kfox1111its an additional set of containers, so shoudl be very low risk.16:51
gemacorrect16:51
inc0kfox1111, I'll review it in a moment16:51
kfox1111inc0: thx.16:51
inc0yeah, I'm not concerned16:51
inc0yeah berendt that's good point16:52
inc0we can have distro debian-arm16:52
inc0and deprecate x8616:52
berendti think the best way is to deprecate current debian images in kolla, to not deprecate debian support in kolla-ansible16:52
sean-k-mooneyi would actully thik it would be best to add an arch flag not a distro16:52
berendtthis way gema can re-add working debian arm64 images16:52
berendtwith a spec16:52
kfox1111not sure level of effort is that much different for arm vs arm+x86.16:52
kfox1111the packages should all be the same.16:52
portdirectinc0: do you have contact with stackenetes at all? they use kolla debian16:52
kfox1111Id expect most of the work to be arm-kvm related really.16:52
inc0I know, but they don't work of it at all any more16:53
berendtgema: does this work for you? deprecation of debian images this cycle?16:53
berendtthis way we are able to remove them next cycle16:53
duonghqI like idea treating debian-arm is pseudo distro16:53
gemaberendt: yes, as long as we are allowed to work on the ARM64 ones going forward, that works16:53
berendtgema: yes of course16:54
gemawe will likely also work on centos-arm16:54
gemabut I see that as a future thing16:54
inc0let's make it distros16:54
berendtbut it makes no sense to keep the x86 images when nobody works on them and you are only willing to work on arm16:54
gemasince there will be 3 of us only working on this part time16:54
inc0we don't need to change build for these two16:54
egonzalezthere is a PS to add powerservers support, already are changing to support different archs in kolla build IIRC16:54
berendtdo we need an other vote when we change the scope of the deprecation?16:55
inc0gema, will we see you in Atlanta?16:55
sean-k-mooneyi think long run having an arch flag would be better then distos per arch16:55
kfox1111just to throw the question out there,16:55
gemainc0: yes, I will try to make time from the interop meetings to come visit you guys16:55
berendtwe will keep debian in kolla-ansible, we will deprecate current debian images16:55
*** zhubingbing has quit IRC16:55
kfox1111do we beleive in container space, arches are as much work as seperate distros?16:55
inc0berendt, let's discuss it on PTG16:55
kfox1111I really don't think they are.16:55
berendtptg is too late for a deprecation?16:55
Jeffrey4l_egonzalez, power support https://review.openstack.org/42323916:55
gemakfox1111: I am not sure of the implications of either16:55
inc0kfox1111, if you look at our debian16:55
inc0it's 90% of ubuntu with few exceptions16:56
egonzalezJeffrey4l_: thanks16:56
sean-k-mooneykfox1111: they should be minimal change unless except when building cross arch images e.g. arm images on windows16:56
kfox1111inc0: ah. so the debian's not debian.16:56
*** tonytan4ever has joined #openstack-meeting-416:56
kfox1111inc0: thats still a seperate issue of, do we support a debian with x86/arm, or just arm.16:56
inc0well names of packages are mostly the same anyway16:56
inc0we narrowed it down from "nobody cares for debian" to "nobody cares for debian on x86"16:57
kfox1111I am pretty sure the instructions for building a debian based arm container once multiarch is in kolla's build scripts, will be essentially the same as for x86.16:57
sean-k-mooneyinc0: yes currently we dont use the full name16:57
kfox1111I think that basically comes for free.16:57
sean-k-mooneyinc0: we excluded the arch and that is determined by apt/yum16:57
gemakfox1111: if that is the case, we will add it16:57
kfox1111I guess we can cross that bridge when we get to it though.16:57
kfox1111yeah.16:57
berendt3 minutes left.. how to proceed?16:57
gemaas long as someone can help validating16:57
inc0berendt, let's hold on with deprecation since gema is volunteering16:57
Jeffrey4l_inc0, +116:58
kfox1111inc0: +116:58
egonzalezyep +116:58
berendtinc0: ok i will close the vote and send the decision to the list16:58
inc0and extend debian to pike, then gema can take on fixing it:)16:58
Jeffrey4l_if we support arm, it will be easy to support x86/power16:58
gema+1!16:58
inc0we will need gates tho, I'm adamant about it16:58
inc0but we'll help16:59
inc0ok, we ran out of time16:59
inc0thank you all for coming!16:59
gemathank you!16:59
inc0#endmeeting kolla16:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:59
*** markvoelker_ has quit IRC16:59
openstackMeeting ended Wed Jan 25 16:59:26 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-01-25-16.01.html16:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-01-25-16.01.txt16:59
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-01-25-16.01.log.html16:59
*** bmace_ has left #openstack-meeting-416:59
*** mgiles has left #openstack-meeting-416:59
*** bobmel_ has quit IRC16:59
sean-k-mooneyincO we might be able to get arm gates via qemu emulation16:59
*** markvoelker has joined #openstack-meeting-416:59
*** TxGirlGeek has quit IRC17:00
*** TxGirlGeek has joined #openstack-meeting-417:01
*** duonghq has quit IRC17:02
*** Serlex has quit IRC17:02
*** sean-k-mooney has left #openstack-meeting-417:02
*** markvoelker has quit IRC17:03
*** inc0 has quit IRC17:03
*** gema has left #openstack-meeting-417:03
*** mdorman has left #openstack-meeting-417:03
*** bobmel has joined #openstack-meeting-417:03
*** mliima has left #openstack-meeting-417:06
*** Jeffrey4l_ has quit IRC17:06
*** mandre has left #openstack-meeting-417:07
*** egonzalez has left #openstack-meeting-417:12
*** SridharP2 has left #openstack-meeting-417:12
*** rainya has quit IRC17:14
*** sp__ has joined #openstack-meeting-417:17
*** sp___ has quit IRC17:19
*** srwilkers has quit IRC17:20
*** l4yerffeJ_ has quit IRC17:21
*** l4yerffeJ_ has joined #openstack-meeting-417:21
*** reedip_ has quit IRC17:23
*** Jeffrey4l has joined #openstack-meeting-417:25
*** TxGirlGeek has quit IRC17:25
*** Swami_ has quit IRC17:27
*** TxGirlGeek has joined #openstack-meeting-417:27
*** rainya has joined #openstack-meeting-417:28
*** iyamahat has joined #openstack-meeting-417:29
*** Jeffrey4l has quit IRC17:30
*** sp__ has quit IRC17:30
*** rainya has quit IRC17:33
*** anilvenkata has joined #openstack-meeting-417:33
*** bobh has joined #openstack-meeting-417:34
*** karts has quit IRC17:34
*** baoli has joined #openstack-meeting-417:35
*** rainya has joined #openstack-meeting-417:36
*** aarefiev is now known as aarefiev_afk17:37
*** bobh has quit IRC17:38
*** tonytan4ever has quit IRC17:39
*** tonytan4ever has joined #openstack-meeting-417:40
*** bobmel has quit IRC17:42
*** Swami has joined #openstack-meeting-417:46
*** zaneb has quit IRC17:46
*** iyamahat has quit IRC17:48
*** KunalGandhi has joined #openstack-meeting-417:54
*** caboucha has quit IRC17:54
*** simon-AS559 has quit IRC17:57
*** klindgren__ has joined #openstack-meeting-417:58
*** ralonsoh has quit IRC17:58
*** beagles is now known as beagles-biab17:59
*** klindgren_ has quit IRC18:01
*** TxGirlGeek has quit IRC18:03
*** sdague has quit IRC18:03
*** TxGirlGeek has joined #openstack-meeting-418:04
*** bobmel has joined #openstack-meeting-418:06
*** tonytan_brb has joined #openstack-meeting-418:06
*** tonytan4ever has quit IRC18:07
*** TxGirlGeek has quit IRC18:10
*** matrohon__ has quit IRC18:10
*** TxGirlGeek has joined #openstack-meeting-418:12
*** unicell has joined #openstack-meeting-418:20
*** dharinic is now known as dharinic|lunch18:24
*** sayantani01 has quit IRC18:30
*** sambetts is now known as sambetts|afk18:34
*** bobh has joined #openstack-meeting-418:34
*** vishnoianil has quit IRC18:35
*** Sukhdev has quit IRC18:35
*** Sukhdev has joined #openstack-meeting-418:36
*** sdake_ has quit IRC18:39
*** bobh has quit IRC18:39
*** sdake has joined #openstack-meeting-418:39
*** KunalGandhi has quit IRC18:40
*** KunalGandhi has joined #openstack-meeting-418:40
*** krtaylor has quit IRC18:40
*** Jeffrey4l has joined #openstack-meeting-418:41
*** yamahata has joined #openstack-meeting-418:43
*** iyamahat has joined #openstack-meeting-418:43
*** KunalGandhi has quit IRC18:45
*** Jeffrey4l has quit IRC18:46
*** rlpple has joined #openstack-meeting-418:48
*** rainya has quit IRC18:52
*** pcaruana has quit IRC18:53
*** tonytan4ever has joined #openstack-meeting-418:56
*** tonytan_brb has quit IRC18:58
*** britthouser has joined #openstack-meeting-418:59
*** sdague has joined #openstack-meeting-419:00
*** benj_ has quit IRC19:00
*** pshedimb has quit IRC19:01
*** KunalGandhi has joined #openstack-meeting-419:03
*** benj_ has joined #openstack-meeting-419:04
*** draynium has quit IRC19:05
*** pshedimb has joined #openstack-meeting-419:05
*** dharinic|lunch is now known as dharinic19:06
*** Jeffrey4l has joined #openstack-meeting-419:10
*** britthouser7 has quit IRC19:10
*** jwagner is now known as jwagner_lunch19:11
*** Sukhdev has quit IRC19:13
*** draynium has joined #openstack-meeting-419:13
*** Jeffrey4l has quit IRC19:15
*** anilvenkata has quit IRC19:15
*** britthouser has quit IRC19:16
*** britthouser has joined #openstack-meeting-419:16
*** krtaylor has joined #openstack-meeting-419:19
*** sdague has quit IRC19:26
*** sdague has joined #openstack-meeting-419:27
*** vishnoianil has joined #openstack-meeting-419:28
*** woodard has quit IRC19:29
*** woodard has joined #openstack-meeting-419:35
*** mitchjameson has joined #openstack-meeting-419:42
*** mitchjameson has left #openstack-meeting-419:43
*** britthouser has quit IRC19:45
*** britthouser has joined #openstack-meeting-419:45
*** Sukhdev has joined #openstack-meeting-419:52
*** Jeffrey4l has joined #openstack-meeting-419:58
*** draynium has quit IRC19:59
*** bobmel has quit IRC19:59
*** bobmel has joined #openstack-meeting-419:59
*** MeganR has joined #openstack-meeting-420:04
*** Jeffrey4l has quit IRC20:04
*** Sukhdev has quit IRC20:05
*** sdague has quit IRC20:06
*** draynium has joined #openstack-meeting-420:06
*** KunalGandhi has quit IRC20:08
*** morgabra has joined #openstack-meeting-420:08
*** morgabra has quit IRC20:08
*** morgabra has joined #openstack-meeting-420:08
*** KunalGandhi has joined #openstack-meeting-420:08
*** KunalGandhi has quit IRC20:12
*** woodard has quit IRC20:12
*** woodard has joined #openstack-meeting-420:13
*** dtardivel has quit IRC20:14
*** beagles-biab is now known as beagles20:16
*** sdague has joined #openstack-meeting-420:18
*** bobmel has quit IRC20:31
*** MeganR has quit IRC20:31
*** bobmel has joined #openstack-meeting-420:34
*** jwagner_lunch is now known as jwagner20:37
*** revon has joined #openstack-meeting-420:38
*** woodard has quit IRC20:42
*** Jeffrey4l has joined #openstack-meeting-420:45
*** KunalGandhi has joined #openstack-meeting-420:51
*** mrunge has quit IRC20:51
*** sdague has quit IRC20:53
*** sdague has joined #openstack-meeting-420:54
*** mrunge has joined #openstack-meeting-420:55
*** TxGirlGeek has quit IRC21:02
*** TxGirlGeek has joined #openstack-meeting-421:06
*** woodard has joined #openstack-meeting-421:21
*** yamamoto has joined #openstack-meeting-421:27
*** tonytan4ever has quit IRC21:29
*** tonytan4ever has joined #openstack-meeting-421:29
*** tonytan4ever has quit IRC21:30
*** tonytan4ever has joined #openstack-meeting-421:31
*** tonytan4ever has quit IRC21:33
*** tonytan4ever has joined #openstack-meeting-421:34
*** l4yerffeJ has joined #openstack-meeting-421:34
*** Jeffrey4l_ has joined #openstack-meeting-421:34
*** l4yerffeJ_ has quit IRC21:35
*** Jeffrey4l has quit IRC21:35
*** yamamoto has quit IRC21:36
*** tonytan4ever has quit IRC21:46
*** tonytan4ever has joined #openstack-meeting-421:46
*** tonytan4ever has quit IRC21:56
*** tonytan4ever has joined #openstack-meeting-421:56
*** cleong has quit IRC21:57
*** zaneb has joined #openstack-meeting-421:58
*** v1k0d3n has quit IRC21:59
*** v1k0d3n has joined #openstack-meeting-422:01
*** sdague has quit IRC22:02
*** tonytan4ever has quit IRC22:11
*** yamamoto has joined #openstack-meeting-422:22
*** thorst_ has quit IRC22:28
*** baoli has quit IRC22:31
*** Sukhdev has joined #openstack-meeting-422:41
*** dave-mcc_ has joined #openstack-meeting-422:52
*** spotz is now known as spotz_zzz22:53
*** dave-mccowan has quit IRC22:54
*** l4yerffeJ_ has joined #openstack-meeting-423:03
*** l4yerffeJ has quit IRC23:03
*** Swami has quit IRC23:04
*** dave-mcc_ has quit IRC23:05
*** dave-mccowan has joined #openstack-meeting-423:05
*** draynium has quit IRC23:10
*** marst has quit IRC23:13
*** TxGirlGeek has quit IRC23:17
*** draynium has joined #openstack-meeting-423:17
*** spotz_zzz is now known as spotz23:18
*** krtaylor has quit IRC23:18
*** KunalGandhi has quit IRC23:20
*** rlpple has quit IRC23:27
*** rbak_ has joined #openstack-meeting-423:37
*** rbak has quit IRC23:38
*** Swami has joined #openstack-meeting-423:46
*** baoli has joined #openstack-meeting-423:47
*** bobmel has quit IRC23:48
*** Swami_ has joined #openstack-meeting-423:48
*** Swami has quit IRC23:51
*** Swami has joined #openstack-meeting-423:52
*** Swami_ has quit IRC23:55
*** rbak_ has quit IRC23:56
*** Swami has quit IRC23:59

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