Wednesday, 2017-03-22

*** ntpttr_ has quit IRC00:04
*** ntpttr_ has joined #openstack-meeting-400:05
*** eglute_s has quit IRC00:14
*** cloudnull has quit IRC00:14
*** _d34dh0r53_ has quit IRC00:14
*** cloudnull has joined #openstack-meeting-400:14
*** eglute has joined #openstack-meeting-400:15
*** uck has quit IRC00:15
*** bobh has joined #openstack-meeting-400:16
*** d34dh0r53 has joined #openstack-meeting-400:19
*** woodard_ has joined #openstack-meeting-400:24
*** woodard has quit IRC00:24
*** Sukhdev has quit IRC00:30
*** rwallner has joined #openstack-meeting-400:32
*** Julien-zte has joined #openstack-meeting-400:32
*** Syed__ has quit IRC00:35
*** rwallner has quit IRC00:36
*** reedip has quit IRC00:38
*** armax has quit IRC00:41
*** harlowja has joined #openstack-meeting-400:42
*** dave-mcc_ has joined #openstack-meeting-400:52
*** zhurong has joined #openstack-meeting-400:52
*** tovin07 has quit IRC00:52
*** dave-mccowan has quit IRC00:53
*** tovin07_ has joined #openstack-meeting-400:58
*** SerenaFeng has joined #openstack-meeting-401:00
*** baoli has joined #openstack-meeting-401:02
*** hongbin has quit IRC01:08
*** Sukhdev has joined #openstack-meeting-401:11
*** cathrich_ has joined #openstack-meeting-401:18
*** reedip has joined #openstack-meeting-401:24
*** gongysh has joined #openstack-meeting-401:33
*** cathrich_ has quit IRC01:41
*** s3wong has quit IRC01:43
*** markvoelker has quit IRC01:49
*** dave-mccowan has joined #openstack-meeting-401:58
*** dave-mcc_ has quit IRC02:00
*** vishnoianil has quit IRC02:13
*** bobh has quit IRC02:13
*** unicell has quit IRC02:16
*** baoli has quit IRC02:16
*** baoli has joined #openstack-meeting-402:19
*** bobh has joined #openstack-meeting-402:35
*** hongbin has joined #openstack-meeting-402:42
*** markvoelker has joined #openstack-meeting-402:50
*** reedip has quit IRC02:52
*** markvoelker has quit IRC02:54
*** bobh has quit IRC03:00
*** baoli has quit IRC03:03
*** links has joined #openstack-meeting-403:12
*** hongbin has quit IRC03:13
*** iyamahat has quit IRC03:14
*** hongbin has joined #openstack-meeting-403:14
*** tovin07 has joined #openstack-meeting-403:14
*** yamahata has quit IRC03:14
*** limao has joined #openstack-meeting-403:16
*** david-lyle has joined #openstack-meeting-403:30
*** harlowja has quit IRC03:35
*** galstrom_zzz is now known as galstrom03:36
*** david-lyle has quit IRC03:36
*** links has quit IRC03:38
*** Sukhdev has quit IRC03:46
*** hongbin has quit IRC03:50
*** markvoelker has joined #openstack-meeting-403:51
*** dave-mccowan has quit IRC03:51
*** links has joined #openstack-meeting-403:52
*** galstrom is now known as galstrom_zzz03:54
*** markvoelker has quit IRC03:55
*** adisky_ has joined #openstack-meeting-404:14
*** psachin_ has joined #openstack-meeting-404:29
*** links has quit IRC04:33
*** zhurong has quit IRC04:37
*** iyamahat has joined #openstack-meeting-404:38
*** anilvenkata has joined #openstack-meeting-404:39
*** vks1 has joined #openstack-meeting-404:41
*** armax has joined #openstack-meeting-404:44
*** unicell has joined #openstack-meeting-404:48
*** links has joined #openstack-meeting-404:50
*** markvoelker has joined #openstack-meeting-404:52
*** markvoelker has quit IRC04:56
*** hongbin has joined #openstack-meeting-404:58
*** trinaths has joined #openstack-meeting-405:04
*** l4yerffeJ has joined #openstack-meeting-405:05
*** hongbin has quit IRC05:08
*** yfauser has joined #openstack-meeting-405:15
*** l4yerffeJ has quit IRC05:15
*** l4yerffeJ has joined #openstack-meeting-405:16
*** l4yerffeJ has quit IRC05:17
*** l4yerffeJ has joined #openstack-meeting-405:18
*** l4yerffeJ has quit IRC05:18
*** l4yerffeJ has joined #openstack-meeting-405:19
*** sshnaidm|afk is now known as sshnaidm|off05:25
*** Jeffrey4l_ has quit IRC05:27
*** pbourke has joined #openstack-meeting-405:29
*** Jeffrey4l_ has joined #openstack-meeting-405:29
*** zhurong has joined #openstack-meeting-405:31
*** markvoelker has joined #openstack-meeting-405:52
*** reedip has joined #openstack-meeting-405:55
*** markvoelker has quit IRC05:57
*** reedip has quit IRC06:06
*** reedip has joined #openstack-meeting-406:10
*** reedip has quit IRC06:12
*** reedip has joined #openstack-meeting-406:13
*** ltomasbo|away is now known as ltomasbo06:17
*** revon has quit IRC06:23
*** anilvenkata has quit IRC06:33
*** iyamahat has quit IRC06:36
*** nkrinner_afk is now known as nkrinner06:43
*** iyamahat has joined #openstack-meeting-406:48
*** markvoelker has joined #openstack-meeting-406:53
*** markvoelker has quit IRC06:58
*** alexchadin has joined #openstack-meeting-406:59
*** unicell has quit IRC07:02
*** yamahata has joined #openstack-meeting-407:03
*** yfauser has quit IRC07:03
*** armax has quit IRC07:05
*** armax has joined #openstack-meeting-407:05
*** unicell has joined #openstack-meeting-407:07
*** bobmel has joined #openstack-meeting-407:15
*** reedip has quit IRC07:16
*** reedip has joined #openstack-meeting-407:16
*** bobmel has quit IRC07:20
*** kzaitsev_ws has joined #openstack-meeting-407:23
*** oshidoshi has joined #openstack-meeting-407:27
*** reedip__ has joined #openstack-meeting-407:30
*** reedip has quit IRC07:31
*** psachin_ has quit IRC07:34
*** reedip__ has quit IRC07:34
*** reedip__ has joined #openstack-meeting-407:34
*** reedip__ has quit IRC07:37
*** reedip__ has joined #openstack-meeting-407:37
*** pcaruana has joined #openstack-meeting-407:39
*** reedip__ has quit IRC07:43
*** reedip__ has joined #openstack-meeting-407:43
*** reedip__ has quit IRC07:44
*** reedip__ has joined #openstack-meeting-407:44
*** ifat_afek has joined #openstack-meeting-407:51
*** matrohon has joined #openstack-meeting-407:53
*** markvoelker has joined #openstack-meeting-407:54
*** reedip__ has quit IRC07:54
*** reedip__ has joined #openstack-meeting-407:56
*** usman has joined #openstack-meeting-407:56
*** psachin has joined #openstack-meeting-407:57
*** markvoelker has quit IRC07:58
*** eyalb has joined #openstack-meeting-407:59
*** danoffek has joined #openstack-meeting-407:59
*** zhurong has quit IRC08:00
danoffekHi Guys08:00
ifat_afek#startmeeting vitrage08:00
openstackMeeting started Wed Mar 22 08:00:29 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
danoffekHi again08:00
ifat_afekHi :-)08:00
eyalb\o08:00
*** elisha_r has joined #openstack-meeting-408:00
*** irenab_ has joined #openstack-meeting-408:00
elisha_rhi08:01
*** alexey_weyl has joined #openstack-meeting-408:01
usmanhi08:02
*** dwj has joined #openstack-meeting-408:02
*** yujunz has joined #openstack-meeting-408:04
ifat_afekLe’ts start08:04
ifat_afekToday’s agenda:08:04
alexey_weylhello everyone08:04
ifat_afek•Status and Updates08:04
ifat_afek•Boston Summit08:04
ifat_afek•Open Discussion08:04
ifat_afek#topic Status and Updates08:04
*** openstack changes topic to "Status and Updates (Meeting topic: vitrage)"08:04
ifat_afekI didn’t do much this week, was sick part of it.08:04
ifat_afekRegarding Doctor: I finished the implementation, but still need to verify the test on an OPNFV pod.08:05
ifat_afekOn the meeting yesterday, Ryota suggested that we have a dedicated POD for Vitrage tests, or to complete Apex installation until E-release08:05
ifat_afekHe said that the Apex task is very big and risky. I need to evaluate both options and better understand the requirements.08:05
*** idan_hefetz has joined #openstack-meeting-408:05
ifat_afekThat’s it for me08:05
ifat_afekWho’s next?08:05
danoffekI can update about the state of Vitrage ID08:05
danoffekNo change yet, still fixing tempest tests to support Vitrage ID change08:06
*** annarez has joined #openstack-meeting-408:06
danoffekI don't think I'll have it ready this week.08:06
danoffekThanks, Anna, for joining08:07
danoffekIn any case, hopefully next week I'll have a better update08:07
danoffekThat's it08:07
ifat_afekdanoffek: Ok, thanks08:07
annarezHi all08:08
yujunzOn my side, not much work done last week due to the OPNFV release milestones08:08
annarezI wrote the blueprint for snmp support in Vitrage08:08
danoffek:)08:09
ifat_afekOk, thanks08:09
ifat_afekyujunz: Any other updates?08:09
yujunzYes08:09
yujunzI will continue on @Weiya's bp about alarm deduction next week08:10
ifat_afekGreat, I was going to ask about that08:11
yujunzHope to deliver the design before MS108:11
yujunzI want to ask about the status of alarm aggregation08:11
ifat_afekWe will also try to check idan_hefetz’s proposal, to see if it matches08:11
*** zhurong has joined #openstack-meeting-408:11
ifat_afekNothing happened regarding alarm aggregation. AFAIK, nobody is working on that08:11
ifat_afekWhy?08:12
yujunzYes, I shall consider weiya, idan_hefretz proposals08:12
yujunzidan_hefetz sorry08:12
ifat_afekAnd your proposal08:12
yujunzOf course :-)08:12
yujunzBasically we are trying to handle the requirement of Nokia's use case and ZTE's use case and back compatibiity on existing interfaces08:13
ifat_afekRight08:13
yujunzThat's all08:13
ifat_afekOk, thanks. So we’ll be in touch regarding the design later on08:14
ifat_afekWho else wants to update?08:14
alexey_weylI have an update08:14
alexey_weylI really but really really want to finish the "not" operator support for the templates and teh evaluator08:14
alexey_weylThat is it for now08:15
ifat_afekThanks :-)08:15
ifat_afekAnyone else?08:15
dwjI'll update. I will continue to implement the `resource list` and `resource show` APIs. :)08:15
ifat_afekdwj: Great!08:16
alexey_weylThat's cool. But dong, don't forget the those APIs needs to support Multi tenancy as well as --all-tenants08:16
dwjI register a bp and proposed a patch #link https://review.openstack.org/#/c/447980/08:16
ifat_afekCool, we’ll review it08:17
dwjalexey_weyl, ok08:17
ifat_afekAny other updates?08:18
dwjThat's all.08:18
ifat_afekMoving on08:18
ifat_afek#topic Boston Summit08:18
*** openstack changes topic to "Boston Summit (Meeting topic: vitrage)"08:18
ifat_afekWe were supposed to finish the brainstorming on the Forum session until yesterday…08:18
ifat_afekwe have one more week to submit the session proposals08:19
ifat_afekPlease enter the etherpad and write a short description on the topics that interest you, and then we’ll vote (or submit all)08:19
ifat_afek#link https://wiki.openstack.org/wiki/Forum08:19
ifat_afek#link https://etherpad.openstack.org/p/BOS-Vitrage-brainstorming08:19
*** amotoki has joined #openstack-meeting-408:20
ifat_afekAnything else regarding the Boston Summit?08:20
ifat_afekBTW, it’s not clear that we’ll get the forum sessions that we want. I’m not so sure about the criteria for approving them08:21
*** irenab_ has quit IRC08:21
ifat_afek#topic Open Discussion08:22
*** openstack changes topic to "Open Discussion (Meeting topic: vitrage)"08:22
ifat_afekAny other issue you would like to raise?08:22
yujunzAbout alarm aggregation08:22
ifat_afekRight :-)08:23
yujunzI'm asking about it because it may relate to alarm deduction08:23
yujunzSo if somebody is starting to work on it, please add me as reviewer08:23
ifat_afekI agree that we need alarm aggregation once we implement the alarm deduction bp08:24
ifat_afekOK to your request, but of course you can become a reviewer even if we don’t add you08:24
ifat_afekA complex bp like that won’t be approved so quickly I guess…08:24
yujunzYes, I have created a filter in openstack gerrit08:25
yujunz#link https://review.openstack.org/#/q/(project:openstack/vitrage+OR+project:openstack/vitrage-specs+)+AND+status:open08:25
yujunzI suppose this will filter out all the open reviews about vitrage core, right?08:25
ifat_afekYou can also get notifications for every new change08:26
ifat_afekI think that filter is ok08:26
ifat_afekIf you set your settings/watched projects, you will get notifications and won’t need the filter08:27
yujunzNormally, I would ignore email notification since there are too many...08:27
ifat_afek:-)08:27
yujunzSo I'm working in PULL mode instead of PUSH08:28
yujunzAnother subject we are watching is persistent database, any progress?08:28
ifat_afekI think we better start thinking about the alarm aggregation, but AFAIK nobody is doing it at the moment. So maybe we’ll wait for the alarm deduction design08:28
ifat_afekNot yet… unfortunately08:28
ifat_afekEveryone seems busy in other tasks08:29
yujunzUnderstandable but the MS1 is quite close. It is April 14, right?08:29
ifat_afekI think so08:29
ifat_afekI agree that we better give it a higher priority08:30
*** matrohon has quit IRC08:30
ifat_afekAny other issue?08:30
yujunzNope08:30
ifat_afekOk, goodbye then08:31
elisha_rbye08:31
*** elisha_r has quit IRC08:32
eyalbbye08:32
usmanbye08:32
dwjbye08:32
*** reedip__ has quit IRC08:32
ifat_afek#endmeeting08:32
*** openstack changes topic to " (Meeting topic: ironic_neutron)"08:32
openstackMeeting ended Wed Mar 22 08:32:36 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vitrage/2017/vitrage.2017-03-22-08.00.html08:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2017/vitrage.2017-03-22-08.00.txt08:32
yujunzbye08:32
*** eyalb has left #openstack-meeting-408:32
openstackLog:            http://eavesdrop.openstack.org/meetings/vitrage/2017/vitrage.2017-03-22-08.00.log.html08:32
*** matrohon has joined #openstack-meeting-408:33
*** yujunz has left #openstack-meeting-408:35
*** alexey_weyl has quit IRC08:35
*** usman has quit IRC08:40
*** ralonsoh has joined #openstack-meeting-408:45
*** annarez has quit IRC08:47
*** l4yerffeJ has quit IRC08:50
*** l4yerffeJ has joined #openstack-meeting-408:50
*** l4yerffeJ has quit IRC08:55
*** l4yerffeJ has joined #openstack-meeting-408:55
*** danoffek has left #openstack-meeting-409:02
*** ifat_afek has left #openstack-meeting-409:08
*** mchiappe|timeoff is now known as mchiappero09:08
*** jamemcc has quit IRC09:12
*** yohoffman has quit IRC09:13
*** trinaths has left #openstack-meeting-409:15
*** yfauser has joined #openstack-meeting-409:16
*** reedip__ has joined #openstack-meeting-409:20
*** alexchadin has quit IRC09:20
*** yfauser has quit IRC09:20
*** alexchadin has joined #openstack-meeting-409:27
*** dwj has quit IRC09:32
*** reedip__ has quit IRC09:33
*** reedip__ has joined #openstack-meeting-409:33
*** gongysh has quit IRC09:36
*** reedip__ has quit IRC09:37
*** reedip__ has joined #openstack-meeting-409:37
*** l4yerffeJ has quit IRC09:38
*** l4yerffeJ has joined #openstack-meeting-409:38
*** iyamahat has quit IRC09:41
*** salmankhan has joined #openstack-meeting-409:44
*** Julien-zte has quit IRC09:47
*** reedip__ has quit IRC09:47
*** reedip__ has joined #openstack-meeting-409:47
*** jamemcc has joined #openstack-meeting-409:48
*** yamahata has quit IRC09:51
*** iyamahat has joined #openstack-meeting-409:51
*** zhurong has quit IRC09:52
*** iyamahat has quit IRC09:56
*** alexchadin has quit IRC10:07
*** pbourke has quit IRC10:08
*** idan_hefetz has quit IRC10:09
*** tovin07_ has quit IRC10:11
*** pbourke has joined #openstack-meeting-410:14
*** limao has quit IRC10:16
*** yohoffman has joined #openstack-meeting-410:17
*** reedip__ has quit IRC10:19
*** ntpttr_ has quit IRC10:22
*** ntpttr_ has joined #openstack-meeting-410:25
*** l4yerffeJ has quit IRC10:29
*** l4yerffeJ has joined #openstack-meeting-410:29
*** ntpttr_ has quit IRC10:33
*** sshnaidm|off is now known as sshnaidm10:42
*** reedip__ has joined #openstack-meeting-410:46
*** bogdando has joined #openstack-meeting-410:51
*** SerenaFeng has quit IRC11:04
*** ntpttr_ has joined #openstack-meeting-411:12
*** neiljerram has joined #openstack-meeting-411:29
*** salmankhan has quit IRC11:39
*** salmankhan has joined #openstack-meeting-411:39
*** rwallner has joined #openstack-meeting-411:39
*** rwallner has joined #openstack-meeting-411:40
*** gongysh has joined #openstack-meeting-411:49
*** alexchadin has joined #openstack-meeting-411:54
*** niedbalski has quit IRC11:56
*** NachoDuck has quit IRC12:01
*** SerenaFeng has joined #openstack-meeting-412:02
*** ntpttr_ has quit IRC12:03
*** ntpttr_ has joined #openstack-meeting-412:09
*** alexchadin has quit IRC12:10
*** alexchadin has joined #openstack-meeting-412:12
*** alexchadin has quit IRC12:17
*** alexchadin has joined #openstack-meeting-412:19
*** woodard_ has quit IRC12:19
*** woodard has joined #openstack-meeting-412:20
*** rwallner has quit IRC12:30
*** haleyb has joined #openstack-meeting-412:31
*** vks1 has quit IRC12:31
*** SerenaFeng has quit IRC12:31
*** oshidoshi has quit IRC12:31
*** limao has joined #openstack-meeting-412:34
*** SerenaFeng has joined #openstack-meeting-412:36
*** rwallner has joined #openstack-meeting-412:36
*** reedip__ has quit IRC12:36
*** reedip has joined #openstack-meeting-412:39
*** klamath has joined #openstack-meeting-412:49
*** markvoelker has joined #openstack-meeting-412:51
*** markvoelker_ has joined #openstack-meeting-412:54
*** markvoelker has quit IRC12:54
*** limao has quit IRC12:56
*** mriedem has joined #openstack-meeting-412:56
*** cleong has joined #openstack-meeting-412:57
*** cdent has joined #openstack-meeting-413:00
alex_xu#startmeeting nova api#startmeeting nova api13:00
openstackMeeting started Wed Mar 22 13:00:16 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#startmeeting nova api)"13:00
openstackThe meeting name has been set to 'nova_api_startmeeting_nova_api'13:00
mriedemo/13:00
johnthetubaguyo/13:00
alex_xuoops13:00
mriedemundo or endmeeting and restart?13:00
johnthetubaguyyeah13:00
alex_xuok13:00
alex_xu#endmeeting13:00
*** openstack changes topic to " (Meeting topic: ironic_neutron)"13:00
openstackMeeting ended Wed Mar 22 13:00:56 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_api_startmeeting_nova_api/2017/nova_api_startmeeting_nova_api.2017-03-22-13.00.html13:01
alex_xu#startmeeting nova api13:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_api_startmeeting_nova_api/2017/nova_api_startmeeting_nova_api.2017-03-22-13.00.txt13:01
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_api_startmeeting_nova_api/2017/nova_api_startmeeting_nova_api.2017-03-22-13.00.log.html13:01
openstackMeeting started Wed Mar 22 13:01:01 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:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
*** openstack changes topic to " (Meeting topic: nova api)"13:01
openstackThe meeting name has been set to 'nova_api'13:01
mriedemo/13:01
gmanno/13:01
cdentmriedem: are you everywhere now because of your working-from-home-ness?13:01
johnthetubaguyo/13:01
mriedemcdent: yes13:01
alex_xumriedem: you worked at office before, i thought no-one will work at office in the US13:02
mriedemalex_xu: the local ibm people do13:02
alex_xu#topic priorities13:02
*** openstack changes topic to "priorities (Meeting topic: nova api)"13:02
alex_xu#link https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/policy-docs13:02
alex_xuthe spec for policy docs merged, and already have a lot of patches ready for review \o/13:02
gmannwant to ask how to show policy for deprecated APIs - #link https://review.openstack.org/#/c/448267/13:03
gmannas test line ok?13:03
Kevin_Zhengo/13:03
*** cathrichardson has joined #openstack-meeting-413:03
gmanntext13:03
johnthetubaguyso deprecated APIs are still APIs13:03
johnthetubaguythats different to deprecated policy rules that are about to die13:04
gmannyea13:04
alex_xuyea13:04
alex_xuwe only to note deprecated API in the api-ref.13:04
*** pmesserli has joined #openstack-meeting-413:04
alex_xus/only/only need/13:04
johnthetubaguyI think we should get the basics in there, and see how we look once thats done13:05
johnthetubaguyits a shame to bloat loads saying that the API is deprecated, if we don't need to.13:05
alex_xuyea13:05
johnthetubaguy#link https://docs.openstack.org/developer/nova/sample_policy.html13:06
johnthetubaguyits starting to look much better already ^13:06
*** julim has joined #openstack-meeting-413:06
mriedemyeah it is13:06
gmannyea, so we do show note about deprecated API like volume API in that sample.13:07
johnthetubaguyI thought we said about we probably don't need to mention it13:07
*** limao has joined #openstack-meeting-413:07
johnthetubaguywe might deprecated a policy rule, but thats different13:08
gmannyea that is separate.13:08
alex_xujohnthetubaguy: do we need a space line between the doc and rule? a little hard to figure which one is rule.13:08
johnthetubaguyalex_xu: sure, thats an oslo.policy generator change though13:09
*** Julien-zte has joined #openstack-meeting-413:09
johnthetubaguysneti or aunnam might fancy fixing that up ^13:09
alex_xujohnthetubaguy: ah yes, that true. I thought we can add a '\n', but you are right, that should be done by oslo.policy13:10
johnthetubaguyoh I quick note on "os_compute_api:os-attach-interfaces:discoverable" and the like13:10
johnthetubaguyI asked them not to document those, because I think we can remove those13:10
gmann+1.13:11
alex_xuyea, hope we can remove those. really needn't waiting for one more release13:11
gmannpatrole project want to test discover policy which they should not right?13:11
johnthetubaguythat in the follow up spec, removing those13:11
johnthetubaguygmann: correct, its not worth it13:12
gmannonly thing we did document that those are going to remove and they thought its valid policy13:12
alex_xujohnthetubaguy: or just create a separated bp for it, then people can begin to kill those directly?13:12
johnthetubaguygmann: I still need to work out what that thing does at some point, probably before we approve the next spec13:12
johnthetubaguyalex_xu: can do13:12
gmann+1, ll convey that13:12
johnthetubaguygmann: I hadn't spotted they still existed till we started this, there are quite a few rules sneti and aunnam have found that actually are unused13:13
johnthetubaguyI am sure, just like with the config, there is a bunch of stuff that will need tidying up13:14
gmannyea13:14
gmanni feel its good to have patrole gate job on nova side ?13:14
johnthetubaguyanyways, not sure there is much else I wanted to discuss on that one (I am keen to talk about the other two specs I guess)13:14
*** dtardivel has joined #openstack-meeting-413:14
*** liangy has joined #openstack-meeting-413:15
alex_xujohnthetubaguy: would OSIC guys want to create a bp for removing discovery entry?13:15
johnthetubaguyalex_xu: its already on their TODO list, I can ask them to create a separate specless BP for that13:15
alex_xujohnthetubaguy: thanks13:16
johnthetubaguygmann: I think we need to work out where it fits, I was really wanting in tree functional tests for the policy stuff13:16
alex_xuthanks OSIC guys, thanks sneti and aunnam13:16
johnthetubaguy+1 great to see us making progress on this stuff13:16
alex_xu#link https://review.openstack.org/#/c/433037/13:17
gmannjohnthetubaguy: yea functional tests always nice. i was thinking we can use patrole effort also for more testing13:17
alex_xujohnthetubaguy: ^ you want to talk that more13:17
gmannbut not sure if sometime that can delay the changes etc13:17
johnthetubaguyso the spec13:18
johnthetubaguyreally I am wondering whats needed to get that approved / agreed13:18
*** limao has quit IRC13:18
johnthetubaguyhad some great comments from alex_xu sneti and aunnam to clean up the text in there13:18
*** limao has joined #openstack-meeting-413:18
johnthetubaguygmann: having both might be correct, I just don't know right now13:19
johnthetubaguyI should copy the summary I guess13:19
gmannsure13:19
johnthetubaguyHere we separate the concerns of what resources user has access to and13:19
johnthetubaguywhat actions the user is allowed to do.13:19
johnthetubaguythats basically it13:19
johnthetubaguyremove scope checks from policy.json13:19
alex_xuyea, mix the role check and scope checks into one rule, that makes people hard to understand13:20
johnthetubaguyalso makes it easy to break Nova's API in the policy file13:21
johnthetubaguynow we are not breaking the whole user_id thing just yet, while we get hierarchical quotas implemented13:21
alex_xuand scope check isn't something people need to change13:21
johnthetubaguyalex_xu: +1 thats the hope, well its something we don't want them to change13:22
johnthetubaguydoing that makes this one much easier13:22
johnthetubaguy#link https://review.openstack.org/#/c/42787213:22
johnthetubaguybasically having some proper default roles for various use cases, beyond user vs global admin13:22
johnthetubaguymriedem: do you think you will get chance to hit those two remaining policy specs?13:23
mriedemjohnthetubaguy: umm13:23
mriedemtoday?13:23
alex_xuI didn't read that spec again. the orignal one feel mix too much thing: more role, deprecated policy..etc13:23
johnthetubaguymriedem: sometime this week would be cool, not worried about it being today13:24
*** julim_ has joined #openstack-meeting-413:24
mriedemhonestly i didn't grok those very well the last time i looked13:24
johnthetubaguyalex_xu: yeah, the key bit is the new role, the deprecated policy is needed to implement that13:24
mriedemaround the time of the ptg13:24
johnthetubaguymriedem: that first one reads much better now I hope13:24
mriedemok i guess if i still don't understand the problem i'll yell about it13:25
johnthetubaguymriedem: totally13:25
mriedemi think it was missing some clear examples before13:25
alex_xujohnthetubaguy: ok, i will try to read that again13:25
alex_xu#link https://review.openstack.org/43548513:26
alex_xumriedem: johnthetubaguy also have a poc ^13:26
johnthetubaguyyeah, its just for that first one13:26
johnthetubaguygmann: thats the functional tests I was on about earlier ^13:27
*** julim has quit IRC13:27
*** mbruzek has joined #openstack-meeting-413:27
*** mbruzek has quit IRC13:27
*** mbruzek has joined #openstack-meeting-413:27
johnthetubaguynow there are some fun details here, between 404 errors and 403 errors13:27
gmannjohnthetubaguy: i see, ll look into those  tomorrow.13:27
johnthetubaguyDB checks triggering 404s and policy triggering (sometimes) 403 errors13:28
johnthetubaguybut the basic idea is to have zero API impact, its just there are some inconsistencies that need to be ironed out here and there13:29
*** limao has quit IRC13:29
alex_xufor the policy check we return 403, for scope check we return 400, i thought13:29
*** baoli has joined #openstack-meeting-413:30
*** limao has joined #openstack-meeting-413:30
johnthetubaguywell, its more complicated I think13:30
gmann404 on policy failure ?13:30
alex_xujohnthetubaguy: the 404 and 403 both are expected return code, so i think it's fine. we won't impact the API13:30
*** SerenaFeng has quit IRC13:30
johnthetubaguyalex_xu: agreed13:30
johnthetubaguymy worry is information disclosure13:31
johnthetubaguysomeone with no access to a server, gets a 404 on that URL today13:31
johnthetubaguyso you can't tell if you guessed the instance uuid correctly13:31
*** janki has joined #openstack-meeting-413:31
johnthetubaguy(for example)13:31
johnthetubaguyI vote we keep that behaviour the same, even when the check is no longer in the DB code13:31
cdentguessing uuids is a new olympic sport13:32
cdentbut yeah, it is a tricky issue13:32
alex_xujohnthetubaguy: you already separate the scope check out of policy rule. that means the policy rule is only about whether you have permission to access the API13:32
gmannjohnthetubaguy: you mean 404 on scope check right so people would not know anything about internal restriction etc13:32
alex_xuso we return 403 for polciy check is right at here. The API endpoint existed, you are just not allowed to access13:33
alex_xufor scope check, for a uuid, we will return 404. you can't see that instance. and we didn't leak something13:33
johnthetubaguyyeah, something like that13:34
*** SerenaFeng has joined #openstack-meeting-413:34
*** yfauser has joined #openstack-meeting-413:34
*** cathrichardson has left #openstack-meeting-413:34
johnthetubaguyif you got 403 for all valid and invalid uuids, that would be fine, for example13:34
*** jchhatbar has joined #openstack-meeting-413:34
johnthetubaguyits the difference in return value that means you can probe for information13:35
*** gongysh has quit IRC13:35
johnthetubaguyanyways, thats all implementation detail I think, because it exact circumstances are different for different APIs13:35
*** SerenaFeng has quit IRC13:35
johnthetubaguythe functional tests we create will help discover these things13:35
johnthetubaguy(at least, thats how I found out there was a problem, when I wrote the POC)13:36
*** SerenaFeng has joined #openstack-meeting-413:36
*** janki has quit IRC13:38
alex_xui need check the spec about the functional tests13:39
johnthetubaguyI think I said tests that pass before and after the change.13:39
gmannfrom first look those are really useful and ll find many issue as johnthetubaguy mentioned13:39
johnthetubaguyi.e. we move the check from the DB into the new logic, and the same tests should check its all good13:39
gmann+113:40
johnthetubaguygmann: it shocked me how interesting they will be :)13:40
alex_xuok, anything more about policy?13:40
*** salmankhan has quit IRC13:40
*** limao has quit IRC13:41
gmannjohnthetubaguy: but we need to complete all those tests before new policy way13:41
*** limao has joined #openstack-meeting-413:41
gmanni think those will be huge with all negative combination for all current policy13:41
johnthetubaguywell, need to add the test in each code path, before converting that code path13:42
johnthetubaguywe certainly shouldn't add them all first13:42
gmannyea that's much feasible13:42
johnthetubaguymost of that test I added is common boilerplate stuff, I think13:43
johnthetubaguythe per API stuff is quite minimal I hope13:43
johnthetubaguybut time will tell13:43
johnthetubaguyanyways, feedback very welcome on all that stuff13:43
johnthetubaguyI would love for us to make some progress on at least the first of those two specs this cycle13:44
alex_xu+113:44
gmann\o/13:44
johnthetubaguygranted, the third spec should not be started until the first two are completed13:44
alex_xuyea13:44
johnthetubaguycool, seems like we are roughly agreed on the approach, which is all good13:45
alex_xuyes13:45
alex_xuI didn't get progress for the poc of remove stevedore, hope I bring news in next week13:46
alex_xuwe have three items in the open, if nothing more for priorities, let us jump to open13:46
cdentalex_xu++ on that stuff.13:46
alex_xucdent: thanks13:46
cdent(the removal of stevedore)13:47
johnthetubaguyyeah, that tottally needs removing13:47
alex_xu#topic open13:47
*** openstack changes topic to "open (Meeting topic: nova api)"13:47
alex_xumriedem: your turn13:47
mriedemyay13:47
mriedemi just replied to comments in https://review.openstack.org/#/c/447149/13:47
*** jchhatbar has quit IRC13:47
johnthetubaguy(FWIW, we hit some strangeness around limits and used limits looking at that policy stuff, so the collapse of those would be nice at some point)13:47
mriedemalex_xu: some clarifying questions for you13:47
alex_xumriedem: thanks13:47
mriedemken'ichi also brought up the os-hosts API13:48
mriedemwhich i didn't even think of,13:48
*** janki has joined #openstack-meeting-413:48
mriedembut now that i look at it, is basically the same as the os-services API, except it has some additional actions, like stop/start/reboot13:48
mriedemso that's pretty ugly13:48
johnthetubaguyoh, most of those are broken too13:48
mriedemi don't know why we have 2 APIs for the same resource, but i've questioned this over my tenure in nova13:48
mriedemjohnthetubaguy: i haven't looked at what supports those APIs, but assume it's xen13:48
*** alexchadin has quit IRC13:49
johnthetubaguymriedem: quite the opposite I think13:49
mriedembecause xen is always the oddball in the API13:49
mriedemoh13:49
johnthetubaguyI think its more about clustered hypervisors where that distinction becomes important13:49
johnthetubaguyquite how you start a host that is shutdown and no nova-compute service running on it, for example13:49
johnthetubaguyit might be left over from the old pre-ironic stuff, I haven't dug to check that13:50
alex_xui feel we add new 'uuid' field explicitly better than change the id field's value to a uuid13:50
johnthetubaguymriedem: so I guess we need to stage this work somehow, we could go with the more obvious fixes first13:50
mriedemlooks like xen and hyperv support host_power_action13:51
mriedembut vcenter doesn't13:51
mriedemnor libvirt or ironic13:51
johnthetubaguymriedem: hmm, must have been baremetal than, I know its mostly broken for xen13:51
johnthetubaguyprobably worth deprecating that API I guess13:51
mriedemmaybe first step is opening a bug about actually documenting wtf os-hosts does and what supports it :)13:51
johnthetubaguyyeah13:52
johnthetubaguythen deprecating it13:52
mriedemok so i think i basicaly have two open questions for the spec,13:52
*** limao has quit IRC13:52
mriedem1. do we change the os-services action APIs to take a service_id rather than rely on looking up the service by hostname/binary in the body?13:52
*** limao has joined #openstack-meeting-413:52
mriedeme.g. PUT /os-services/{service_id}/disable13:52
mriedemPUT /os-services/disable-log-reason13:53
mriedem{13:53
mriedem    'disabled_reason': 'host os upgrade maintenance'13:53
mriedem}13:53
johnthetubaguyI am +1 that myself13:53
mriedemerr PUT /os-services/{service_id}/disable-log-reason13:53
johnthetubaguyyeah, that13:53
mriedemalex_xu: gmann: cdent: opinions on that?13:53
* cdent is thinking13:54
mriedemfeel free to just chime in on the spec when you have time13:54
alex_xuso we want to introduce that new action way?13:54
mriedemi want dansmith to review it before i make changes13:54
alex_xunot /os-services/{service_id}/action, anymore?13:54
dansmithack13:54
cdenti'll give the review a real review later today13:55
mriedemalex_xu: we already have PUT /os-services/disable today13:55
gmannand user will get service_id from list13:55
mriedemwith a body like:13:55
mriedem{     "host": "host1",     "binary": "nova-compute" }13:55
*** alexchadin has joined #openstack-meeting-413:55
*** chrisspencer_ has joined #openstack-meeting-413:55
alex_xumriedem: at least we consistent with other existed apis i think13:55
*** salmankhan has joined #openstack-meeting-413:55
mriedemso that becomes just PUT /os-services/{service_id}/disable13:55
mriedemwith no body13:55
* edleafe wakes up. Long night13:55
mriedembecause we don't need the host and binary to identify the service if we have the id13:55
cdentin general using identifiers in the URL is good13:56
* alex_xu reminds that we only left 4 mins13:56
gmannIMO /disable explicitly much cleaner than /action13:56
mriedemyeah honestly i had assumed this was how things already worked in here13:56
johnthetubaguycdent: is that the correct URL for an action, rather than our silly /action catch all thing?13:56
gmannyea +1 on those13:56
mriedemken'ichi didn't want /action13:56
mriedemwhich i'm fine with13:56
cdentjohnthetubaguy: unresolved huge debate that was so huge people gave up13:56
johnthetubaguyyeah, I think avoiding the catch all /action is probably good, I can't remember if there is already an API WG thingy for this13:56
johnthetubaguycdent: ah, OK13:57
cdentit was abandoned13:57
mriedemthe other thing,13:57
*** vincentfrancoise has joined #openstack-meeting-413:57
cdentbecause it looked like soap13:57
edleafejohnthetubaguy: cdent: usually POST is more forgiving, no?13:57
mriedem2. do we also want to do this for os-hosts if we're doing it for os-services (since they are basically the same api)?13:57
mriedemi'd think yes13:57
mriedem"yes" to also doing os-hosts13:57
johnthetubaguywell, the option is to just deprecate os-hosts13:57
gmannme also not comfirtable  for /action13:57
johnthetubaguyand roll any remaining things of interest into os-services13:58
mriedemjohnthetubaguy: if we deprecate os-hosts,13:58
mriedemthen we have to move the stop/start/reboot actions from os-hosts to os-services13:58
mriedemwhich we could do13:58
johnthetubaguyI think we could argue they shouldn't live in our API13:58
mriedemit just starts to become a hell of a big spec13:58
johnthetubaguyso there is no replacement13:58
mriedemwith 1 minute left, move discussion to the spec?13:59
cdentyes13:59
mriedemi also wanted sdague's thoughts on all of this too13:59
alex_xuyea13:59
gmannyes13:59
mriedemanyway, thanks13:59
alex_xuedleafe: sorry, we didn't have enough time for your item13:59
edleafenp13:59
edleafeI slept in anyway :)13:59
johnthetubaguy+1 on wanting sdague's view on this13:59
alex_xuok, it's time to close the meeting, thanks all, let us back to the nova channel14:00
alex_xu#endmeeting14:00
*** openstack changes topic to " (Meeting topic: ironic_neutron)"14:00
openstackMeeting ended Wed Mar 22 14:00:04 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-03-22-13.01.html14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_api/2017/nova_api.2017-03-22-13.01.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_api/2017/nova_api.2017-03-22-13.01.log.html14:00
alexchadin#startmeeting watcher14:00
openstackMeeting started Wed Mar 22 14:00:19 2017 UTC and is due to finish in 60 minutes.  The chair is alexchadin. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: watcher)"14:00
openstackThe meeting name has been set to 'watcher'14:00
*** cdent has left #openstack-meeting-414:00
alexchadinHi Watcher folks!14:00
chrisspencer_o/14:00
sballe_o/14:00
dtardivelhi14:00
vincentfrancoiseo/14:00
*** markvoelker_ is now known as markvoelker14:01
*** mriedem has left #openstack-meeting-414:01
alexchadin#info Today we have the following agenda https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#02.2F15.2F201614:01
alexchadin#link https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#03.2F22.2F201714:01
*** pshedimb has joined #openstack-meeting-414:01
alexchadin#topic Announcements14:01
*** openstack changes topic to "Announcements (Meeting topic: watcher)"14:01
alexchadinDue to time changes the next meeting will be one hour later than usually.14:01
pshedimbYayy :)14:02
alexchadinso be prepared next time ;)14:02
sballe_ok14:02
vincentfrancoisealexchadin: depends on the country though :p14:02
sballe_alexchadin: not for people in the US though14:02
alexchadinvincentfrancoise: yeah, it is applicable only for time-change countries :)14:02
*** galstrom_zzz is now known as galstrom14:03
sballe_:) just wanted to pshedimb to not be late14:03
vincentfrancoisealexchadin: even worse not all country change time on the same day...14:03
pshedimbsballe_, haha :)14:03
*** bobh has joined #openstack-meeting-414:03
*** limao has quit IRC14:03
alexchadinwe have a lot of discussions today so I'd like to start with them14:03
alexchadin#topic Open discussions14:03
*** openstack changes topic to "Open discussions (Meeting topic: watcher)"14:03
alexchadinPython 3.5 Support – it is one of the main goals for Pike cycle and we need to meet completion criteria.14:04
*** limao has joined #openstack-meeting-414:04
alexchadin#link https://governance.openstack.org/tc/goals/pike/python35.html14:04
*** bobh has quit IRC14:04
*** bobh has joined #openstack-meeting-414:04
alexchadinwe have unit test gates for both 2.7 and 3.5 - it is great!14:04
*** ostroverkhov has joined #openstack-meeting-414:04
vincentfrancoisealexchadin: so after a quick read it means we need to have both unit tests **and** tempest test to pass with py3514:04
alexchadinbut our functional tests works only with 2.714:05
alexchadinso yes, vincentfrancoise +1, we need functional gate for 3.514:05
vincentfrancoisealexchadin: I reckon they work with py34 (I checked once like 3-4 months ago)14:05
alexchadinvincentfrancoise: if so, I believe they will work great with 3.514:06
vincentfrancoisealexchadin: regarding tempest tests, they are really flaky these days so before getting them onto py35, we also need to spend time stabilizing them14:06
alexchadinvincentfrancoise: we need to define what we want from functional tests and set boundaries14:07
alexchadinvincentfrancoise: the situation with "one more blueprint" ;)14:07
acabothi sorry to be late14:08
alexchadinhi acabot14:08
vincentfrancoisealexchadin: all api tests + the dummy strategy end2end execution14:08
alexchadinvincentfrancoise: +114:08
alexchadinwho would like to take it?14:08
alexchadinI suppose we need some sort of spec here14:08
alexchadinwhich would define what tests we actually need14:10
*** sshnaidm has quit IRC14:10
*** corey_ has joined #openstack-meeting-414:10
*** cleong has quit IRC14:11
alexchadinwell, I will add it to my TODO's and assign it later14:11
alexchadinmove on14:11
alexchadinWSGI Support. Does our API work with WSGI? #link https://governance.openstack.org/tc/goals/pike/deploy-api-in-wsgi.html#watcher14:11
*** vks1 has joined #openstack-meeting-414:11
*** oshidoshi has joined #openstack-meeting-414:11
vincentfrancoisealexchadin: our API stack is the same as magnum and ironic so if it works for them then we should be OK14:12
sballe_alexchadin: I will go through as many of the spec as i can review. based ont hese minutes14:13
alexchadinvincentfrancoise: there are status of projects: https://governance.openstack.org/tc/goals/pike/deploy-api-in-wsgi.html#current-state-anticipated-impact14:13
alexchadinsballe_: thank you!14:13
vincentfrancoisealexchadin: yes but the remaining steps can be copied from ironic then14:14
vincentfrancoisealexchadin: https://github.com/openstack/ironic/blob/master/ironic/api/app.wsgi seems like one of the main difference we don't have14:14
*** sshnaidm has joined #openstack-meeting-414:14
*** limao has quit IRC14:15
alexchadinas it is one of the main goals for Pike cycle, it would be great to take it now14:15
*** limao has joined #openstack-meeting-414:15
adisky_alexchadin: I can take it14:16
alexchadinadisky_: thanks!14:16
adisky_:)14:17
alexchadin#action adisky_ update WSGI status of Watcher14:17
alexchadinWatcher is not presented in Debian-based systems due to issue. It would be great to build package by ourselves. #link http://lists.openstack.org/pipermail/openstack-dev/2017-February/112220.html14:17
alexchadinthe main problem here is that zigo lost his contract with Mirantis, so there is no one who can hold it14:18
alexchadinadisky_ said that we are not presented in Debian repos for Ocata release14:19
zigoThere's no Ocata release in Debian *at all*.14:19
zigoHopefully, this may change though ...14:20
alexchadinHere is page https://openstack.alioth.debian.org that explains packaging process14:20
alexchadinhi, zigo!14:20
zigoNo, this is old, and doesn't take into account the fact we're now packaging on OpenStack infra.14:20
*** siva_krishnan has left #openstack-meeting-414:20
*** links has quit IRC14:21
alexchadinzigo: could you please give us some information about building and releasing Watcher for Debian?14:21
zigoalexchadin: We need to first get a Stretch image into OpenStack infra, which I have been working on, then all of the rest of OpenStack needs to get packaged (oslo, etc.).14:22
zigoAll is done through Gerrit these days.14:22
alexchadinzigo: is there some docs with first steps?14:22
zigoSo just openstack/deb-watcher...14:22
zigoalexchadin: Basically, it's fix the issues with openstack-infra/project-config stuff. ie: ./tools/build-image.sh14:23
zigoCurrently, it fails.14:23
zigoI'm not sure why yet...14:23
zigoHelp would be appreciated.14:23
zigoIt's been 1 week I'm on that already, and can't find what's going on.14:24
zigoProbably something with Puppet 4 instead of 3.14:24
zigoRunning ./tools/build-image.sh with these variables:14:24
zigoexport DIB_RELEASE="stretch"14:24
zigoexport DIB_DEBOOTSTRAP_EXTRA_ARGS=--include=systemd-sysv14:24
zigoexport DISTRO=debian-minimal14:24
zigoexport DISTRO_NAME=debian14:24
zigoexport CONFIG_REF=refs/changes/13/445813/414:24
zigothen fix the problems.14:25
alexchadinzigo: thank you. can we discuss it in our main channel, openstack-watcher?14:25
*** sanfern has joined #openstack-meeting-414:25
zigoSure ! Feel free to discuss that Stretch issue on #openstack-infra or even #openstack-pkg if you like too.14:25
alexchadinzigo: great!14:25
zigoOnce that's done, I believe I can release Ocata quite fast.14:26
*** dave-mccowan has joined #openstack-meeting-414:26
alexchadin#action continue discussion with zigo about building Watcher for Ocata14:26
*** limao has quit IRC14:26
alexchadinmove on14:26
alexchadinadisky reported that python-watcherclient is not included in rdo repo of python-openstackclient.14:26
*** limao has joined #openstack-meeting-414:26
adisky_alexchadin:  correction there is no rpm package of python-watcherclient14:27
adisky_we have rpm packages available for watcher, but not for watcher-client14:27
zigonumber80 is the nick behind all RDO stuff.14:28
adisky_so i am unable to complete installation  guide for rdo14:28
zigoChat with him ...14:28
alexchadinadisky_: can you resolve this issue?14:29
adisky_zigo: thanks :)14:29
adisky_alexchadin: yes i will14:29
alexchadin#action adisky_ contact number80 to resolve rpm-issue14:30
alexchadin#topic Review Action Items14:31
*** openstack changes topic to "Review Action Items (Meeting topic: watcher)"14:31
alexchadinWatcher14:31
alexchadinVersioned Notifications for service object needs reviews #link https://review.openstack.org/#/c/437333/14:31
alexchadinwho would like to review it?14:32
chrisspencer_+114:32
*** yfauser has quit IRC14:32
vincentfrancoise+114:32
alexchadinit isn't big patch14:32
alexchadinthanks chrisspencer_ vincentfrancoise14:33
alexchadin#action chrisspencer_ vincentfrancoise review https://review.openstack.org/#/c/437333/14:33
alexchadinAdd Gnocchi datasource needs final core reviews #link https://review.openstack.org/#/c/438530/14:33
sanfernhello14:34
alexchadinhi sanfern14:34
sballe_hi14:34
alexchadinI can't just +2 on my patch :)14:34
alexchadinvincentfrancoise: will you take a look?14:35
pshedimb+114:35
alexchadinpshedimb: thanks14:35
vincentfrancoisealexchadin: on this one there were comments you didn't answer14:35
alexchadinvincentfrancoise: ah sure14:35
vincentfrancoisealexchadin: so I remember I was waiting for you to answer before putting a +214:36
*** srwilkers has joined #openstack-meeting-414:36
vincentfrancoisealexchadin: once you do, I'll review it once more14:36
alexchadin#action vincentfrancoise pshedimb review https://review.openstack.org/#/c/438530/ when alexchadin update it14:36
alexchadinAdded suspended audit state needs reviews #link https://review.openstack.org/#/c/438800/14:36
pshedimbalexchadin, also gnocchi is moving out of openstack. will it affect the patch?14:37
*** limao has quit IRC14:37
*** limao has joined #openstack-meeting-414:38
alexchadinpshedimb: I've seen this thread and they promise that there won't be any changes for projects which use it14:38
pshedimbalexchadin, okay :)14:38
vincentfrancoisepshedimb: alexchadin what about gnocchi moving out? can I have a link about this?14:38
alexchadinpshedimb: they will have changes with CI, but should remain OpenStack support14:39
alexchadinvincentfrancoise: let me find14:39
sanfernvincentfrancoise, https://review.openstack.org/#/c/447438/14:39
pshedimbvincentfrancoise, Gnocchi guys submitted request to OpenStack congress to move out of openstack14:39
alexchadinvincentfrancoise: http://lists.openstack.org/pipermail/openstack-dev/2017-March/114300.html14:39
sballe_Maybe we should do the same down the line if we want to support other eco-system than openstack... Not now but just food for thoughts14:40
alexchadinpshedimb: although there were some opinions that they are more OpenStack-related than they thought14:40
acabotthey just want to leave the big tent14:40
*** janki has quit IRC14:41
acabotit doesn't mean it will not work with openstack anymore14:41
vincentfrancoisealexchadin: pshedimb: so that means there is won't be any openstack-tagged telemetry project anymore14:41
sballe_acabot: I agree14:41
alexchadinvincentfrancoise: yeap14:41
sballe_how about Monasca they claim to do it all14:41
pshedimbvincentfrancoise, alexchadin Ceilometer is still there14:42
pshedimbThe main component of telemetry14:42
alexchadinpshedimb: ceilometer doesn't have API14:42
sballe_pshedimb: but witth no supported APIS14:42
sballe_alexchadin: lol14:42
alexchadinpshedimb: high five!:D14:42
pshedimbalexchadin sballe_ , yeah we gotta use backend like mongodb14:42
pshedimbhaha :D14:42
sballe_indfluxDb is better for the stuff we are lookign at doing anywau14:43
pshedimbGnocchi is just a backend. So any other backend like Mongo or HBase will work just fine.14:43
sballe_s/anyway14:43
vincentfrancoisewhich is why Watcher should definitely be datasource agnostic as much as possible14:43
alexchadinpshedimb: gnocchi works perfectly as API for Ceilometer14:43
pshedimbalexchadin, Yeah I agree.14:43
alexchadinlet's leave this discussion for main channel14:44
sballe_+114:44
vincentfrancoise+114:44
alexchadinwe have only 15 minutes left14:44
pshedimb+114:44
alexchadinmove on14:44
alexchadinPrevent the migration of VM with 'optimize' False in VM metadata needs new PS14:45
alexchadin#link https://review.openstack.org/#/c/443070/14:45
alexchadinpksingh is not here14:45
vincentfrancoisealexchadin: I discussed this with him14:45
*** blallau has joined #openstack-meeting-414:45
alexchadinvincentfrancoise: +114:45
alexchadinvincentfrancoise: I've seen it14:45
alexchadinvincentfrancoise: Have you got some conclusion?14:46
vincentfrancoisealexchadin: basically, the code made me realise there was another issue with the nova metadata representation14:46
vincentfrancoisealexchadin: we have an XML reprenstation to declare scenarios14:46
vincentfrancoisealexchadin: this is a declarative/human readable system to make it easy in tests14:47
alexchadinvincentfrancoise: is it applicable only for basic_consolidation strategy?14:47
vincentfrancoisealexchadin: but the metadata breaks it (or at least the test do not pass because dicts are unordered so we cannot dafely bootstrap)14:47
*** hongbin has joined #openstack-meeting-414:47
vincentfrancoisesafely*14:48
*** pksingh has joined #openstack-meeting-414:48
pksinghHello14:48
vincentfrancoisealexchadin: so we need to ensure that we can test the model which contains json14:48
*** limao has quit IRC14:48
*** marst has joined #openstack-meeting-414:48
vincentfrancoisepksingh: hi14:49
pksinghvincentfrancoise: Hi14:49
vincentfrancoisealexchadin: before we can carry on with what pksingh was actually trying to do in the first place14:49
*** limao has joined #openstack-meeting-414:49
*** armax has quit IRC14:49
alexchadin#action vincentfrancoise and pksingh work together on https://review.openstack.org/#/c/443070/14:49
vincentfrancoisealexchadin: does that make sense?14:49
alexchadinvincentfrancoise: yeah14:50
vincentfrancoisealexchadin: good :)14:50
alexchadinAdding tempest test that executes outlet_temp_control strategy. needs reviews #link https://review.openstack.org/#/c/439184/14:50
*** blallau has left #openstack-meeting-414:50
pshedimb+114:50
alexchadin#action pshedimb review https://review.openstack.org/#/c/439184/14:51
alexchadinReduced the code complexity needs new PS #link https://review.openstack.org/#/c/441873/14:51
*** vds has quit IRC14:51
*** vds has joined #openstack-meeting-414:52
*** vds has quit IRC14:52
alexchadinstale the action plan needs final core reviews #link https://review.openstack.org/#/c/440927/14:52
alexchadinI will review it, who else?14:52
*** ntpttr__ has joined #openstack-meeting-414:53
*** ntpttr__ is now known as ntpttr_laptop14:53
alexchadin#action alexchadin review https://review.openstack.org/#/c/440927/14:53
*** vds has joined #openstack-meeting-414:53
alexchadinAdd gnocchi support in basic_consolidation strategy needs reviews #link https://review.openstack.org/#/c/440293/14:53
chrisspencer_+114:54
alexchadinsanfern provided new PS yesterday, let's review it14:54
alexchadin#action chrisspencer_ alexchadin review https://review.openstack.org/#/c/440293/14:54
*** talonx has joined #openstack-meeting-414:54
alexchadinexception when running 'watcher service list' needs reviews #link https://review.openstack.org/#/c/447354/14:55
chrisspencer_+114:55
alexchadinI have a question here: is it good pattern to have one named hosts?14:55
*** bklei has joined #openstack-meeting-414:56
alexchadinsame named*14:56
*** armax has joined #openstack-meeting-414:56
*** Serlex has joined #openstack-meeting-414:56
vincentfrancoisealexchadin: I guess no, but sometimes legcy bites...14:57
*** rbak has joined #openstack-meeting-414:58
alexchadinvincentfrancoise: well, let's ask licanwei about it14:58
*** galstrom is now known as galstrom_zzz14:58
alexchadin#action alexchadin put some comments on https://review.openstack.org/#/c/447354/14:58
alexchadinwe have only 2 minutes left14:58
acabotno time left for specs :-D14:59
alexchadinDon't forget there are 5 specs which are waiting for your reviews14:59
alexchadinacabot: unfortunately...14:59
alexchadinwell, thank you for your attention14:59
vincentfrancoisebye everyone14:59
alexchadinbye15:00
sanfernbye15:00
*** limao has quit IRC15:00
adisky_bye15:00
*** liangy has quit IRC15:00
pshedimbbye15:00
ostroverkhovbye15:00
acabotbye15:00
chrisspencer_bye15:00
*** ostroverkhov has quit IRC15:00
alexchadin#endmeeting15:00
*** openstack changes topic to " (Meeting topic: ironic_neutron)"15:00
*** sanfern has left #openstack-meeting-415:00
openstackMeeting ended Wed Mar 22 15:00:28 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/watcher/2017/watcher.2017-03-22-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/watcher/2017/watcher.2017-03-22-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/watcher/2017/watcher.2017-03-22-14.00.log.html15:00
*** chrisspencer_ has left #openstack-meeting-415:00
*** limao has joined #openstack-meeting-415:00
serverascode #startmeeting operators_telco_nfv15:01
*** jascott1 has joined #openstack-meeting-415:01
*** armax has quit IRC15:01
*** sayantani01 has joined #openstack-meeting-415:01
serverascodehmm15:01
*** vincentfrancoise has left #openstack-meeting-415:02
*** shintaro has joined #openstack-meeting-415:02
*** GeraldK has joined #openstack-meeting-415:02
serverascode #startmeeting operators_telco_nfv15:02
shintarohi15:03
*** hongbin_ has joined #openstack-meeting-415:03
*** galstrom_zzz is now known as galstrom15:03
GeraldKhi15:04
shintarohi GeraldK15:04
*** wxy| has joined #openstack-meeting-415:04
serverascodecan't seem to get the meeting started15:05
serverascodenot too sure why15:05
*** hongbin has quit IRC15:05
serverascodebut I guess lets get going15:05
GeraldKhi shintaro and serverascode15:05
GeraldKserverascode, I believe you had an extra space before #startmeeting15:05
serverascodeoh15:06
serverascode#startmeeting operators_telco_nfv15:06
openstackMeeting started Wed Mar 22 15:06:10 2017 UTC and is due to finish in 60 minutes.  The chair is serverascode. Information about MeetBot at http://wiki.debian.org/MeetBot.15:06
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:06
*** openstack changes topic to " (Meeting topic: operators_telco_nfv)"15:06
openstackThe meeting name has been set to 'operators_telco_nfv'15:06
serverascodeyay!15:06
shintaroo/15:06
GeraldKo/15:06
GeraldKjust the three of us today?15:06
serverascodethanks GeraldK :)15:06
shintaroto start with15:07
serverascodeok, lets get going :)15:07
serverascode#topic boston forum15:07
*** openstack changes topic to "boston forum (Meeting topic: operators_telco_nfv)"15:07
serverascodeok so there is some kind of forum happening at the next summit15:08
shintaroyes15:08
serverascodeI don't think that we will be getting the meeting space we requested, and instead it's the forum15:08
shintaroand the agenda is here #link https://etherpad.openstack.org/p/BOS-UC-brainstorming-Telecom&NFV15:08
serverascodeyeah shintaro I think you have a bit better understanding of whats happening :)15:08
serverascodedo you want ot try to explain?15:09
shintaroso as I have heard, there wont be ops meetup at the summit, but only the Forum15:09
serverascodeok15:09
shintaroForum is for the ops to give feedback to devs for longer term stragetgy planning15:10
serverascodetoo bad jamie from the lcoo isn't here today, I think they were briefed on the forum15:10
serverascodeit also looks like we have to submit forum session requests?15:10
serverascodehttp://forumtopics.openstack.org/15:11
*** rbak has quit IRC15:11
*** yingjun has joined #openstack-meeting-415:11
serverascode#link http://forumtopics.openstack.org/15:11
shintaroRight now the brainstorming for the session planning is going on15:11
serverascodeso should we be submitting somethere there? or will groups like the LCOO submit?15:11
GeraldKright. proposed topicd in the Etherpad link shintaro had shared15:11
*** limao has quit IRC15:11
*** rbak has joined #openstack-meeting-415:11
GeraldKmy understanding is we have to submit if we want some Telco/NFV specific sessions15:11
*** limao has joined #openstack-meeting-415:11
shintaroyes. put the NFV related agenda to the etherpad and will be considered the proposal15:12
GeraldKthe user committee also has a similar Etherpad to collect session ideas15:12
*** david-lyle has joined #openstack-meeting-415:12
shintarooh which one GeladK15:12
jamemccHi - i am here now15:13
serverascodeso we should be adding session ideas to the etherpad, then at some point someone will submit?15:13
serverascodehey jamemcc15:13
GeraldKdeadline for the proposals was March 14th15:13
GeraldK#link https://etherpad.openstack.org/p/BOS-UC-brainstorming15:13
serverascodeah, ok so that is done now then15:13
serverascodejamemcc do you know anything about the status of the next summit forum?15:14
serverascodeand nfv related sessions?15:14
shintaroI don't know who but Telco-NFV is already proposed and the ehterpad was created15:14
GeraldK#link https://wiki.openstack.org/wiki/Forum/Boston2017 list of all Boston Summit planning Etherpads15:14
jamemccI only know about the contents of the pad https://etherpad.openstack.org/p/BOS-UC-brainstorming-Telecom&NFV and that we have been asked and to some extent have added our topics there15:15
*** talonx has quit IRC15:15
*** yingjun has quit IRC15:15
jamemccFor LCOO we really havent' added there yet15:15
shintaroI see Gluon topic prposal there15:15
jamemccRight15:15
GeraldKDid you discuss about the proposal on gaps in openstack related to NFV and related to the ETSI STF in Milan or a previous meeting?15:16
shintarowhat does STF stands for?15:16
GeraldKETSI specialist task force. see line 30 in the NFV/Telco Etherpad page15:17
serverascodeok, well I'm not sure what to do here, but at least we all know about the right etherpads and the submission page :)15:18
shintarono not at the ops meetup. but we disucussed that we need to discuss gaps in openstack15:18
serverascodeI had put a item on the agenda for shintaro to let us know what happened at the ops meeutp in milan15:18
jamemccFor the Gluon and for the new PWG User Proposals (previously known as User Stories) we wil be submitting matchign Forum Topic Proposals15:18
GeraldKshintaro: yes. I had seen the discussion on gaps in the minutes.15:18
jamemccBut not yet decided if those will be called LCOO Forum topics or not15:19
*** iyamahat has joined #openstack-meeting-415:19
jamemccTomorrow morning is our weekly LCOO meeting and that's on the agenda15:19
shintaroyes, there were only few telco at the ops meetup but we had more than 10 attendees in the room15:19
serverascodedoes anyone think there is something specific this group should be doing around the forum session?15:20
shintarowe discussed that we should discuss the gaps between OPNFV requirements and current Openstack15:20
serverascodeif not then perhaps we move onto the next topic15:20
*** yamahata has joined #openstack-meeting-415:20
serverascodedoesn't seem like it :)15:21
GeraldKfrom an email on the forum submission process: There are two stages to the brainstorming:     1. Starting today, set up an etherpad with your group/team, or use one on the list and start discussing ideas you'd like to talk about at the Forum. Then, through +1s on etherpads and mailing list discussion, work out which ones are the most needed - just like you did prior to the ops events.       2. Then, in a couple of week15:21
jamemccIt's good to not let that drop - there was also an outreach directly to OPNFV15:21
*** Julien-zte has quit IRC15:21
jamemccI know Kathy C attended their meeting a week ago15:21
shintaroAlso we agreed that the  docunentation work that have been undertaken by this group was important15:21
jamemccAnd the Gluon topic there was a result of that15:21
GeraldKso, a second submission stage is required.15:22
jamemccI guess that specifically OPNFV is handlign ehri own entries into the Forum.15:22
GeraldKdeadline for submission is April 2nd: http://forumtopics.openstack.org/15:22
*** Julien-zte has joined #openstack-meeting-415:22
serverascodeok, but is there anything *we* should be doing?15:23
*** limao has quit IRC15:23
serverascodeLCOO is working on it, OPNFV is working on it...15:23
*** limao has joined #openstack-meeting-415:23
GeraldKif we (NFV/Telco team) want to propose some of the ideas listed in the Etherpad we should submit it15:23
shintaroI think we should handle the telco-nfv session proposals15:24
GeraldKWe should pick our favorites from the Etherpad and submit them15:24
shintaroyes +115:24
serverascodeah ok15:25
GeraldKresults will be available from April 10th15:25
shintaroit should be working group session proposal15:25
*** rwellum has joined #openstack-meeting-415:25
*** armax has joined #openstack-meeting-415:26
serverascodeis there anything from the etherpad that you think are important?15:26
shintarothe proposal from Jay is really interesting15:26
GeraldKthere are 5 topics that had received >= 2 votes15:26
GeraldKhave you all already voted?15:27
serverascodeno I have not myself15:27
GeraldKshintaro: which of the proposals by Jay are you referring to?15:27
serverascode2 votes is not very many for the entirity of the NFV ecosystem :)15:27
shintaroI also want to discuss about the networking northbound API15:27
shintarothe placement API GeraldK15:27
GeraldKmaximum is 5 votes so this shows little outreach we have and how unfamiliar we all are still with the process15:27
serverascodeyeah15:28
GeraldKshintaro: +1 on this topic15:28
*** duonghq has joined #openstack-meeting-415:28
*** psachin has quit IRC15:29
serverascodeperhaps we will have to do a bit of organization via email?  our next meeting is not until april 5th i believe15:29
serverascodewhich would be after the deadline for forum submissions15:29
*** vks1 has quit IRC15:30
GeraldKotherwise, if we agree on 2 or 3 topics now, we could assign ourselved to do one submission each15:30
shintarovia ML, yes15:30
GeraldKML would also be okay for me.15:30
serverascodeok, are you both on the openstack operators list?15:31
shintaroyes15:31
GeraldKyes15:32
serverascodeok cool15:32
serverascodeperhaps lets try to do this by email out in the open15:32
GeraldKwe then also need to agree on a "champion" who will lead the session/discussion at the Forum in case it is accepted.15:32
serverascodethat's a good point, I had htought I heard that maybe there would be someone from the foundation tasked with that? and with taking notes?15:33
serverascodelike a professional facilitator?15:33
serverascodenot sure if that is actually happening though15:33
*** pksingh has quit IRC15:34
*** limao has quit IRC15:34
serverascodeif you two are ok with it, I will start a mailing list thread under telecom-nfv, and perhaps others will jump in and help out15:34
shintaro+115:34
*** limao has joined #openstack-meeting-415:35
serverascodeif we need to we can set an impromptu meeting next week in #openstack-nfv or something15:35
serverascodeGerladK does that sound ok?15:35
serverascodeGeraldK does that sound ok?15:35
GeraldK+115:35
serverascodecool15:35
serverascodejamemcc you still there?15:35
shintarothere are already names in the session proposal on the etherpad and they might want to lead the session15:36
serverascodeyeah15:36
GeraldKshintaro: +115:36
serverascodeok lets move onto the next topic15:36
serverascode#topic multi-site docs15:36
*** openstack changes topic to "multi-site docs (Meeting topic: operators_telco_nfv)"15:36
serverascodeI don't know if either of you are interested in this topic, but it's more of a point of information that the arch guide15:37
serverascodeis being rewritten, and the multi-site docs that were there are no longer there15:37
serverascodeso there are currently no official docs on multi-site/region15:37
serverascodeand perhaps they could use some help writing those15:37
GeraldKcan you share a link to the arch docs?15:37
*** bobmel_ has joined #openstack-meeting-415:37
serverascodeyup one sec15:37
serverascodeso this is whta is online now:15:38
serverascodel#link https://docs.openstack.org/arch-design/15:38
serverascodeone sec to track down the git repo15:38
serverascode#link https://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc15:39
serverascodeif you go to the above link you can see the "arch-design-to-archive" that has the old multi-stie docs15:39
shintaroHeidi from the Foundation said we can get their support in finalizing the document as in the #link https://etherpad.openstack.org/p/MIL-ops-telco-nfv line3715:39
serverascodeoh interesting15:40
*** bklei has quit IRC15:40
serverascodeI  will have to review the mil ops doc :)15:40
GeraldKwhy was the multi-site being proposed to be removed? is the text too outdated?15:40
serverascodeI don't know if it's being removed, I'm not completely sure what is going on with the arch-guide15:41
serverascodeI think it's just being rewritten piece by piece15:41
serverascodethere is also potentially a NFV section to it15:41
*** Julien-zte has quit IRC15:42
serverascodeso piece by piece, they just haven't gotten to it yet, and could probably use some help15:42
serverascodealso I know that OPNFV has a multi-site team15:42
serverascodeI just think it's interesting how important some form of multi-site is for NFV, and there are currently no official docs15:42
GeraldKyes. there is a multi.site team in OPNFV. should I drop them an email related to this?15:42
serverascodethat would be great if you would! :)15:42
serverascodedo you want to take that as an action item?15:43
GeraldKyes.15:44
serverascode#action GeraldK email OPNFV multi-site group regarding new arch-guide multi-site section15:44
serverascodecool thanks GeraldK15:44
serverascodeany other thoughts on that topic?15:44
serverascodeor move on?15:44
serverascode#topic Report on Milan Ops  Meetup15:45
*** openstack changes topic to "Report on Milan Ops Meetup (Meeting topic: operators_telco_nfv)"15:45
serverascodeshintaro are you still there?15:45
shintaroyes15:45
*** limao has quit IRC15:45
serverascodedo you want to say a couple things about the ops meetup and NFV?15:45
serverascodeor the ops meetup in general? was it pretty good?15:46
shintarothere were only few telco ops in the room, but we had 10+ ppl in the room15:46
*** limao has joined #openstack-meeting-415:46
serverascodewhat were the non-telco ops peoole interested in?15:46
serverascodemostly wondering what NFV is?15:47
shintarowe discussed whether the documentation work was useful for them and got feedback that the documentation is important for other ops as well15:47
serverascodeok so docs were important15:47
shintaroserverascode: other ops was large ops who where interested in NFV usecases15:47
shintarothat might be applied to their environment as well15:48
serverascodeorganizations like comcast?15:48
shintarodatacenterd and OSIC guys were there15:48
serverascodeah ok15:48
shintarowe also discussed that we should address networking issues15:49
shintarofor instance issues related to SR-IOV and DPDK15:49
serverascodeok15:49
serverascodesounds like a good session15:50
serverascodeanything else to mention or onto "open discussion"? :)15:50
shintaroyes, interface between MANO and Openstack15:50
shintarowhat is missing in OpenStack to mandate MANO requirement in terms of northbound APIs15:51
serverascodeok that is interesting, a good place to look for gaps15:52
*** rwallner has quit IRC15:52
shintaroeveryone agreed OpenStack is NFVI de-facto standard but no one was sure what was missing in OpenStack15:52
serverascodemaybe nothing then :)15:53
serverascodeok thanks shintaro, I will go over that etherpad15:53
*** Serlex has quit IRC15:53
shintarothat was about it15:53
serverascodewith a few min left I want to move onto open discussion15:54
serverascode#topic open discussion15:54
*** openstack changes topic to "open discussion (Meeting topic: operators_telco_nfv)"15:54
serverascodeif anyone has any items... :)15:54
GeraldKemail to OPNFV multisite team is sent out15:54
*** SerenaFeng has quit IRC15:54
serverascodeawesome thanks GeraldK15:54
serverascodeI will start a thread later today on the NFV forum sessions15:55
shintarogreat!15:55
GeraldK+115:55
serverascodeif no other items, then I guess we can close the meeting15:55
*** egonzalez has joined #openstack-meeting-415:55
serverascodethank you two for attending :)15:55
serverascodejamemcc thanks too :)15:55
shintarothank you15:56
serverascodetalk to you on the mailing list :)15:56
serverascode#endmeeting15:56
*** openstack changes topic to " (Meeting topic: ironic_neutron)"15:56
openstackMeeting ended Wed Mar 22 15:56:20 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2017/operators_telco_nfv.2017-03-22-15.06.html15:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2017/operators_telco_nfv.2017-03-22-15.06.txt15:56
openstackLog:            http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2017/operators_telco_nfv.2017-03-22-15.06.log.html15:56
GeraldKbye15:56
*** limao has quit IRC15:56
*** GeraldK has quit IRC15:57
*** shintaro has quit IRC15:57
*** limao has joined #openstack-meeting-415:57
*** Sukhdev has joined #openstack-meeting-415:57
*** blallau has joined #openstack-meeting-415:58
*** sbezverk has joined #openstack-meeting-415:58
inc0#startmeeting kolla15:59
openstackMeeting started Wed Mar 22 15:59:00 2017 UTC and is due to finish in 60 minutes.  The chair is inc0. Information about MeetBot at http://wiki.debian.org/MeetBot.15:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:59
*** openstack changes topic to " (Meeting topic: kolla)"15:59
openstackThe meeting name has been set to 'kolla'15:59
egonzalezwoot o/15:59
inc0#topic rollcall15:59
*** openstack changes topic to "rollcall (Meeting topic: kolla)"15:59
*** mnaser has joined #openstack-meeting-415:59
duonghqo/ woot15:59
jascott1woot15:59
sdakeo/15:59
kfox1111o/15:59
mnasero/15:59
egonzalezwelcome duonghq ;)15:59
rwellumo/15:59
asettleo/15:59
duonghqthank egonzalez15:59
blallauHi all15:59
spsurya_o/15:59
sbezverko?15:59
sbezverko/16:00
*** zhubingbing has joined #openstack-meeting-416:00
zhubingbingo/16:00
Jeffrey4l_\o/16:00
*** vhosakot has joined #openstack-meeting-416:00
*** mandre has joined #openstack-meeting-416:00
akwasnieo/16:00
*** Guest52040 has joined #openstack-meeting-416:00
pbourkew00t16:01
mandreo/16:01
pbourkeegonzalez: you gotta wait for the official announcement :p16:01
inc0yup, so I'll just do it:P16:01
inc0#topic announcements16:01
*** openstack changes topic to "announcements (Meeting topic: kolla)"16:01
lazyPowero/16:02
inc0Welcome duonghq in our core team!:)16:02
pbourkeduonghq: welcome nice job16:02
vhosakoto/16:02
kfox1111o/16:02
vhosakotw00t w00t16:02
spsurya_nice duonghq16:02
*** armax has quit IRC16:02
Jeffrey4l_congrats duonghq16:02
zhubingbing;)16:02
sdakegrats dude :)16:02
akwasnieduonghq: welcome:)16:02
bogdandoo/16:03
mnaserquick everyone take advantage and get your +2s in16:03
mnaser>:)16:03
inc0mnaser: >:(16:03
sdakeif only the gate wer eworkign :)16:03
mnaserbut congrats! :-P16:03
duonghqthank inc0, pbourke, egonzalez, Jeffrey4l_ akwasnie sdake  and all other core gave me support, I'll do my best for our deliverables16:03
vhosakotcongrats duonghq!16:03
inc0any community announcements?16:03
sdakeduonghq would like to see ya core on kolla-kubernetes at some point too :)16:03
inc0we have busy agenda today:)16:03
duonghqsdake, sure16:03
sdakeyup i have one16:03
inc0go on16:04
sdakesince the ptgs were pretty disruptive to our kolla-kubernetes schedule, I moved 0.6.0 to 4-15-201616:04
sdake(from 3-15-2017)16:04
sdakerather 4-15-201716:04
sdakeenjoy :)16:04
*** iyamahat has quit IRC16:04
inc0ok moving on to agenda items16:04
inc0#topic unwedging the gate (Jeffrey4l, mnaser)16:04
*** openstack changes topic to "unwedging the gate (Jeffrey4l, mnaser) (Meeting topic: kolla)"16:04
inc0gentleman, you have the floor16:05
*** nkrinner is now known as nkrinner_afk16:05
mnaserright so: gate was broken by bifrost (for the second time)16:05
inc0drop bifrost from voting gates?16:05
mnaserthe first time we werent pointing to the right python exec and they started installing system packages which broke things16:05
sdakeinc0 that was my suggestion16:05
Jeffrey4l_i have no idea for this issue right.16:05
mnaserthe second time (time), it seems to be related to ansible_env.SUDO_USER missing16:05
sdakethe only gating that happens is the image build16:06
Jeffrey4l_i tried change "ansible_env.SUDO_USER to root. but another issue happends16:06
mnaseri proposed and merged a patch which i thought would fix it (missing defaults): https://review.openstack.org/#/c/447713/16:06
sdakewe can *temporarily* unblock the gate by droping bifforst from it16:06
Jeffrey4l_'dict object' has no attribute 'bootstrap'"16:06
*** harlowja has joined #openstack-meeting-416:06
*** Sukhdev_ has joined #openstack-meeting-416:06
Jeffrey4l_sdake, yes. we can16:06
mnaserJeffrey4l_ interesting, i didnt try to fix that... i did some digging on monday, but tuesday and today have been busy in $job so yeah.16:07
inc0I think that's good discussion to have - having voting and non-voting build gates at same time16:07
Jeffrey4l_i will try to find more later.16:07
inc0voting with lower number of projects16:07
*** ntpttr_laptop has quit IRC16:07
Jeffrey4l_on master we depends on lots of other project,which may break our jobs easily ;(16:08
*** limao has quit IRC16:08
mnaserwell during this whole thing i was thinking it would be really cool if we added checks for each project we build images for (and the job builds images for that specific project only)16:08
mnaserif bifrost images were built on bifrost reviews, it could give them some indication of "hey you broke something". it could either be $project filing a bug saying "we changed this, please reflect your stuff accordingly"16:08
*** limao has joined #openstack-meeting-416:08
mnaseror they can realize that they did break something somewhere16:08
inc0mnaser: issue is, we're bound to what is in tarballs.o.o today16:09
mnaserbut again, going back to our issue16:09
duonghqhave we had internal docker registry, I cannot recall, sorry. But mnaser's idea need this16:09
Jeffrey4l_mnaser, like devstack does ? that will be nice16:09
inc0that's one16:09
mnaserbut going back to the main subject16:09
mnaseri think putting bifrost aside to stop the project from halting for now..16:10
mnaseri would be behind it16:10
Jeffrey4l_inc0, based on tarballs.o.o site. the project could build his new image ( bifrost ) + tarball.o.o images.16:10
mnaserthe reason is there is another issue apparently with python-mysqldb which i saw on launchpad16:10
*** oshidoshi has quit IRC16:10
mnaserand honestly, the bifrost images seem to have a lot of, uh, hacky things.16:10
inc0yeah, thats why I'd be ok to drop it from voting16:11
mnaserhttps://github.com/openstack/kolla/blob/master/docker/bifrost/bifrost-base/Dockerfile.j2#L29-L3116:11
Jeffrey4l_beyond this. base on inc0's idea, we can set a priority on building image in master branch. i.e. bifrost failed, that's OK and +1,   nova failed, critical -116:11
mnaseras an example16:11
inc0and add non-voting gates with more images16:11
mnaseri like that idea, 2 jobs16:11
duonghqJeffrey4l_, you mean we have mandatory and optional image inside our gate script?16:12
Jeffrey4l_inc0, we can re-use the current jobs.16:12
duonghq*will have16:12
inc0Jeffrey4l_: yeah, and just change profile confs16:12
mnaserone that builds core, one that builds $world16:12
mnaseri agree with this16:12
Jeffrey4l_inc0, if add extra-jobs, we have to add centos/ubuntu/oracle ** binary/source  = 6 jobs.16:12
inc0yeah16:12
inc0I don't think that's big issue16:12
mnaseroraclelinux jobs take forever and it would be nice if we had mirrors :-(16:13
inc0pbourke: ^ told ya:P16:13
Jeffrey4l_;/16:13
*** zhubingbing__ has joined #openstack-meeting-416:13
inc0let's do this16:13
mnaseralso an interesting aspect is this might not be as bad because16:13
pbourkethey take ~10 mins more than centos from what Ive seen16:13
inc01. drop bifrost as it blocked our dev16:13
inc0from voting16:13
Jeffrey4l_then how about push tarball registry?16:14
mnaserif we build $core in one job, and $non-core in another job, we only duplicate the base image building, so we dont have that much "wasted" resources16:14
inc02. create non-voting gates16:14
inc0Jeffrey4l_: good question16:14
mnaseryeah that's a tricky one16:14
Jeffrey4l_and this should be only happen in master.16:14
inc0is there any way to "soft-fail" job?16:14
Jeffrey4l_we should keep all voting in stable branch.16:15
Jeffrey4l_inc0, i guess no. mnaser do you have any idea on "soft fail"?16:15
mnaseri dont think there is such thing16:15
inc0like, we have some notion of fail, but won't block16:15
mnaserits a pass or fail, voting or non voting16:15
inc0yeah I guess16:15
Jeffrey4l_inc0, we can define soft fail ;)16:15
mnaseri think we handle this in our scripts16:15
inc0ok, my suggestion (modified)16:16
Jeffrey4l_just like what i said :)16:16
inc0let's drop bifrost from voting asap16:16
inc0and start ML thread16:16
duonghqis soft-fail hard to tracking issue?16:16
mnaserbuild images, if $core images fail, exit 1, if $core pass and $non-core fail, exit 0 but push what you got16:16
inc0it needs more discussion16:16
Jeffrey4l_great.16:16
mnaser+116:16
*** zhubingbing has quit IRC16:16
Jeffrey4l_mnaser, yes. i prefer to do this.16:16
inc0mnaser: can you publish patch with bifrost drop?16:16
mnasershooure16:16
inc0many thanks good sir16:17
*** caboucha has joined #openstack-meeting-416:17
inc0btw it's soft fail I was thinking of, what mnaser described16:17
Jeffrey4l_mnaser, drop it and please file a bug to track this ;)16:17
mnasercan i use the same one i had for the gate failures?16:17
inc0only thing is we somehow need to have info that if soft-failed visible somewhere16:17
inc0mnaser: yeah16:18
Jeffrey4l_ya. i think it is OK.16:18
mnaserhttps://bugs.launchpad.net/kolla/+bug/167448316:18
openstackLaunchpad bug 1674483 in kolla "Bifrost failing because of missing SUDO_USER" [Critical,Confirmed]16:18
inc0ok let's move on16:18
Jeffrey4l_inc0, ya. i'd like something soft-fail to support.16:18
inc0(sorry, busy agenda)16:18
inc0#topic Native helm config maps (sbezverk)16:18
*** openstack changes topic to "Native helm config maps (sbezverk) (Meeting topic: kolla)"16:18
inc0sbezverk: go ahead16:18
*** limao has quit IRC16:19
*** mgoddard has joined #openstack-meeting-416:19
*** l4yerffeJ has quit IRC16:20
*** wxy| has quit IRC16:20
*** l4yerffeJ has joined #openstack-meeting-416:21
*** wxy| has joined #openstack-meeting-416:21
sbezverkok, configmaps, there was a proposal to use ansible16:21
inc0#link https://review.openstack.org/#/c/448258/16:21
berendto/16:21
kfox1111to clarify, I thin kthe proposal was to temporarily use ansible as we are now, but move it closer to kolla-kubernetes.16:21
sbezverkto generate configmaps, but imho it is not ideal.  I would still like to explore16:21
sbezverkhelm charts to generate them16:21
*** alexchadin has quit IRC16:22
kfox1111sbezverk: +116:22
kfox1111I thikn helm based configmaps are a better place to go long term.16:22
inc0sbezverk: issue with this is....helm charts are not ideal today and porting it all to helm will be a lot of work16:22
*** Jeffrey4l_ has quit IRC16:22
*** hongbin_ has quit IRC16:22
sbezverkbased on what I see, helm has native way to support this specific functionality16:22
kfox1111short term, just moving the code from kolla-ansible -> kolla-kubernetes would reduce the breakage we see periodically.16:22
inc0without things like parent values16:22
*** Jeffrey4l_ has joined #openstack-meeting-416:22
sbezverkI do not see any reason notto use it, unless people know something that prevents16:22
mnaseri don't know a lot about the k8s stuff, but i would love to have a shared lib/repo rather than us maintaining the same thing in two places16:23
inc0just a lot of work16:23
inc0mnaser: that was idea behind using kolla-ansible to generate configs for k8s16:23
kfox1111what I want to prevent, is yet a 3rd required workflow.... ansibe for generating some config, kollakube for some other ressources, and helm for yet more.16:23
inc0but it turns out that configs in fact differs16:23
sbezverkwell, if I had right syntax, it would be a chart common to ALL services with only 6-8 lines of code16:23
inc0kfox1111: I'd really like to get rid of kollakube tbh16:23
kfox1111inc0: I fully agree.16:24
sbezverk+116:24
kfox1111inc0: but I'm saying, it should go, before we add yet another kollakube.16:24
kfox1111or at the same time.16:24
inc0my plan with ansible is to repeal and replace kollakube16:24
inc0and it's gonna be great16:25
sbezverkit makes sense to have genconfig moved, we should not even try to implement it at least short term16:25
kfox1111100% repeal. not 50%, I'm saying.16:25
inc0kfox1111: yeah16:25
sbezverkbut for configmap using helm seems logical to me..16:25
kfox1111sbezverk: I agree with you. but one of the stated goals is to allow microservices to be configed by any mechanism.16:25
kfox1111I think we should provide a helm based config option.16:25
srwilkerssbezverk, i agree 100%16:25
kfox1111but if others want to perminanly support an ansible based one, I wouldn't block it.16:26
inc0my question tho - we need to explore how helm would deal with self-prepared configs16:26
kfox1111inc0: not sure it needs to?16:26
inc0I see 2 approaches here16:26
sbezverkkfox1111: sure thing16:26
inc0kfox1111: I'd say yes, there are companies that handcrafted their confs16:26
kfox1111user uploads the configmaps, the microservices consume them.16:26
kfox1111inc0: sorry, that was ambiguous.16:27
kfox1111I meant, I'm not sure anything has to change today to support hte use case. we already do.16:27
sbezverkkfox1111 +216:27
inc0yeah, today we generate tons of configs and then just add them to k8s16:27
sbezverkwe just mount whatever matches the needed name16:27
inc0that or just add your own16:27
sbezverkdoes not matter what you used to generate them16:28
*** galstrom is now known as galstrom_zzz16:28
inc0but if we move configmaps to charts, won't that be issue?16:28
inc0I mean...is configmap a microservice?16:28
inc0(I'd say that's a step too far tbh)16:28
sbezverkinc0: we can bundle configmap charts16:29
sbezverkinto corresponding services16:29
sbezverkfor example providing complete deployable package16:29
inc0but then won't helm re-create resources?16:29
duonghqsbezverk, you mean configmap will be one of the chart template?16:29
sbezverkduonghq: yes16:29
sbezverkinc0: as dependency16:29
kfox1111inc0: no. the configmaps would be seperate charts. the user can launch them too, or not.16:30
inc0if it's inside chart, it won't be dependenct right?16:30
sbezverkinc0: I have not tried at least yet, but it should be doable16:30
*** Jeffrey4l_ has quit IRC16:30
kfox1111like, maybe we create helm/configmaps/xxxxx16:30
duonghqhow do we deal with node-specific config? or will we suffer that?16:30
inc0ehh16:30
sbezverkkfox1111: exactly what I think too16:30
*** Jeffrey4l_ has joined #openstack-meeting-416:30
inc0and then init container doing sed:/16:30
kfox1111duonghq: group specific config could be handled by instancing.16:30
inc0I must say I don't like this. Chart-configmap is...overkill16:31
sbezverkinc0: you cannot completely get rid of sed, ever!!16:31
kfox1111helm install nova-compute-configmap --set element_name=foo16:31
kfox1111helm install nova-compute --set element_name=foo16:31
inc0sbezverk: because we need to put interface in configmap16:31
sbezverkinc0: there ae tons of run time only known parameters16:31
inc0and that's not something k8s supports very well16:32
kfox1111inc0: thats again, the lowest level. you can wrap them up in grouping charts if you don't care about the details.16:32
sbezverkinc0: there is not interface in kube16:32
sbezverkinc0: only IP16:32
duonghqhow about static pod provide such that value?16:32
*** Jeffrey4l_ has quit IRC16:32
inc0sbezverk: yeah, but ovs doesn't care about what is or not in kube16:32
kfox1111inc0: we handle that usually with init containers. it already works.16:32
sbezverkwhich are dynamically allocated16:32
*** Jeffrey4l_ has joined #openstack-meeting-416:32
inc0ok, so back to the topic at hand16:33
sbezverkso run time config modification is ineviatable16:33
inc0how we do configmaps in helm? I dunno yet16:33
inc0sbezverk: but sed isn't great tool to do it imho16:33
kfox1111my vote is /helm/configmaps/xxx charts.16:33
sbezverkinc0: the idea is to use common config chart16:33
kfox1111we can provide templates for the most common things we need to configure.16:33
sbezverkwhich will pull inside of a configmap all config files16:34
sbezverkgenerated by kolla genconfog16:34
kfox1111users can override settings via the cloud.yaml settings, or16:34
kfox1111upload their own configmaps.16:34
inc0one chart to have just configs? I don't like that tbh16:34
duonghqI do not like put every thing in cloud.yaml, it'll be very huge file16:34
kfox1111sbezverk: your thinking one chart for all configmaps?16:34
sbezverkkfox1111: no16:34
kfox1111ok.16:35
sbezverkone chart per /etc/kolla/neutron-server16:35
inc0I think configmaps should be part of microservice chart16:35
kfox1111sbezverk: +116:35
sbezverkone chart per /etc/kolla/neutron-openvswitch0agent16:35
sbezverketc16:35
spsurya_duonghq:  +116:35
kfox1111inc0: what does that buy you?16:35
inc0better correlation between microservice and config it uses16:35
kfox1111inc0: that assumes you will be using that configmap.16:36
inc0we will effectively double number of microservices, which is significant today16:36
kfox1111inc0: so?16:36
inc0most people will16:36
inc0use base configmap16:36
kfox1111computekit-configmap16:36
sbezverkinc0: most people will use service or compute16:36
kfox1111can aggregate them all up so those that don't want to think about them, dont have to.16:36
sbezverkkit and we can bundle16:36
sbezverkconfigmaps there as dependencies16:37
kfox1111right.16:37
kfox1111yeah16:37
duonghqsbezverk, +116:37
kfox1111service/neutron can bundle the configmaps with helm conditionals.16:37
duonghqbut, will we have configmap @ microservice level or also service level?16:37
inc0I know we can do all that16:37
kfox1111embeded_configmaps=true16:37
sbezverkduonghq: the idea is to have configmap at the same level16:38
sbezverkas microsecices16:38
sbezverkand then bundle them on a needed basis16:38
sdakehey sorry was otp :)16:38
duonghqsbezverk, wfm16:38
inc0ehh...idk, I think chart per every resource is a bit of unneeded churn16:38
inc0maybe not a bit16:39
inc0microservice, fine, but configmap? seems ugly to me16:39
*** matrohon has quit IRC16:39
inc0but that is just my personal opinion I didn't though through fully16:39
kfox1111inc0: folks like tripleo are now talking with us, becuase we're staying neutral to things like config generation.16:39
inc0think through*16:39
sbezverkI would suggest to try both approaches16:39
inc0both - no16:40
sbezverkto gain better undersatnding of pros and cons16:40
inc0ahh try16:40
inc0sorry misread you16:40
kfox1111following the aproach lets us continue to be unbiased on config management technologies.16:40
sdakeinc0 why no, you said you wouldn't be married to any ansible implementation16:40
sbezverkjust try, cause what I just said was theory ;)16:40
inc0yeah, third approach is to assume existing configmaps and provide tool to create them16:40
*** Sukhdev_ has quit IRC16:40
inc0sdake: we're not talking about ansible16:40
sdakeok16:41
inc0which is what we do today16:41
inc0just tools are ugly16:41
sdakewhat are the 2 approaches16:41
kfox1111yeah.16:41
sdakesorry - i could scorllback but it takes awhile16:41
sdake2 one liners will do16:41
inc0configmap as microservice on its own or part of existing microservice16:41
mnaser(sorry guys but there are 4 more items and something id like to bring up in the open discussion and $time -- just a hint :x)16:41
duonghqI concern about something like config merge and override as in kolla-ansible, not sure if we need it and how do we done it efficient16:42
sdakei think we want configmap as separate helm chart right?16:42
kfox1111yeah. seperate.16:42
inc0we don't know what we want yet16:42
portdirectthat seems a bit overkill?16:42
sdakeinc0 i think we do ;)16:42
inc0I'm not too hot on separate chart16:42
sbezverkthat is what we suggest to try16:42
lazyPoweri say straw man it, and let the design shake itself out based on how many times you bump into the rough edges16:42
sdakelazyPower ++16:43
lazyPowerseems like conjecture otherwise16:43
*** iyamahat has joined #openstack-meeting-416:43
inc0yeah, and in the meantime I'll just move ansible generation as we already have code16:43
sdakeinc0 wfm - we need to eject kolla-ansible as adep soon - its annoying :)16:43
lazyPowerinc0: we aren't talking about ansible ;)16:43
kfox111199% of the work is getting hte configmaps into gotl.16:43
kfox11111% is where in the fs they land.16:43
inc0yeah16:44
inc0I'm afraid of gotl:(16:44
kfox1111inc0: hehe. its... interesting.16:44
sdakeone path forward is to focus on what goes in the gotpls16:44
lazyPowerits very very similar to liquid templates16:44
sdakeand then sort out where to put them through iteration16:44
Jeffrey4l_( time, guys )16:44
sbezverkkfox1111: atm we do not even need to do ANY templating16:44
*** matrohon has joined #openstack-meeting-416:44
lazyPowernot exactly like it, but very close. so if you have some chops in jinja/liquid you should be on the right path.16:44
kfox1111been a while since I used a polish notation language before gotl.16:44
sbezverkwe can take config files as is and dump them into corresponding configmap16:45
kfox1111sbezverk: we will need to do some I think. iscsi vs ceph, etc.16:45
sdakeok peeps - lots of pepeps complaining we should have timboxed this session can we move on :)16:45
kfox1111sbezverk: mostly minor things though.16:45
inc0#topic Deployment guide16:45
*** openstack changes topic to "Deployment guide (Meeting topic: kolla)"16:45
sbezverkkfox1111: but know we do not do it at all, so first step would be to match what we do now16:45
sdakedeployment guide has lots o -1s16:45
sdakethansk for the reviews folks16:45
sdakeI'm going to give it a spa treatment _today_16:46
kfox1111sbezverk: we dont' do it because genconfig does it. but if genconfig is getting repleaced by helm, then we need to do it.16:46
sdakewoudl appreciate people that are interested add themselves as a reviewer16:46
rwellumI'm not sure about copying the etherpad directly into a review like that?16:46
sdaketo fllow progress16:46
rwellumI found it a little confusing..16:46
rwellumBecause there are embedded comments.16:46
sdakerwellum it wont be after i update it16:46
*** bobmel has joined #openstack-meeting-416:46
rwellumsure16:46
sdakerwellum i agree its confusing now16:46
sdakeupdate is in progress on my disk now16:47
sdakethere are 40 comments in gerrit - so takes awhiel to get thorugh16:47
*** rwallner has joined #openstack-meeting-416:47
sdakehttps://review.openstack.org/#/c/447731/ please add yourself as a reviewer if you want to follow the work or have contributions to make16:48
sdakethanks inc016:48
inc0ok, so moving on?:)16:48
sdakeyup16:48
sbezverksdake: practice showed that the most efficient approach is to get together and go step by step, people can follow in their environment and share comments in the real time..16:48
inc0#topic KS rolling upgrade review16:48
*** openstack changes topic to "KS rolling upgrade review (Meeting topic: kolla)"16:48
spsurya_inc0:  sdake: patch need reviews of cores   https://review.openstack.org/#/c/425446/    depend on mentioned patch of kolla16:48
inc0spsurya_: floor is yours16:48
sdakesbezverk wfm - we can do that after i get the doc cleaned up16:48
sdakesbezverk so we have some sanitary starting point16:49
spsurya_inc0: need core review16:49
*** unicell has quit IRC16:49
*** links has joined #openstack-meeting-416:49
spsurya_  https://review.openstack.org/#/c/425446/16:49
*** unicell has joined #openstack-meeting-416:49
*** test_user has joined #openstack-meeting-416:49
spsurya_that is all from my for today16:49
spsurya_my side*16:49
inc0ok:)16:50
duonghqshould we rebase and try to get all gate green before move on for this ps?16:50
duonghqonly ubuntu-binary failed16:50
inc0ok, I'll bump post-ptg bps to next week16:50
*** bobmel_ has quit IRC16:50
sdakeduonghq yo ucan just recheck - no need to rebase16:50
spsurya_duonghq: seems like that16:50
inc0#topic open discussion16:50
*** openstack changes topic to "open discussion (Meeting topic: kolla)"16:50
sdakeduonghq recheck automatically does a rebase - tested and confirmed by many people16:50
mnaserhttps://review.openstack.org/#/c/447524/16:50
mnaserdockerhub publishers in infra16:51
mnaseri got some feedback from infra team, i wanted to ask some folks at kolla to give some comments/feedback16:51
sdakemnaser ++ thanks for kicking that off :)16:51
lazyPowerinc0: open discussion - is this where i can bring up a topic from last week that got postponed?16:51
duonghqsdake, I'll try, last time I do recheck, it didn't rebase, I'm not sure16:51
mnaserso i can make another revision to the review to throw towards infra folks16:51
Jeffrey4l_i will release next z stream for newton and mitaka branch. any advice and idea?16:51
sdakeduonghq i'll talk to after meeting on this topic ok?16:51
inc0lazyPower: yeah16:51
mnaser(thats all i had to say, just wanted to put peoples eyes on it)16:51
duonghqsdake, wfm, thanks16:51
*** uck has joined #openstack-meeting-416:52
Jeffrey4l_inc0, ^16:52
sdakecould folks in kolla interested in the dockerhub pushing add yourself to that review mnaser linked?16:52
sdakeTIA :)16:52
inc0Jeffrey4l_: hold on a sec16:52
inc0kfox1111: lazyPower have different way to deploy k8s on ubuntu right?:)16:52
lazyPowerI'd like to re-propose the topic of adding the Canonical Distribution of Kubernetes to the Kolla CI system. We'll be happy to run it, do the integration path, and submit results so you get warm fuzzies knowing kolla will always work on top of the CDK which is the officially supported method to deploying k8s on ubuntu.16:52
lazyPoweryeah, sorry was typing out that short novel ^16:53
sdakelazyPower are you the fella we met at the PTG from cononical?16:53
kfox1111inc0: ubuntu has a product now for k8s.16:53
lazyPowersdake: correct16:53
sdakelazyPower nice to see ya onnline and in the community :)16:53
lazyPowersdake: well one of about 3 engineers that were in/out of the room anyway :) but yeah i was the primary driver of the talks for CI integration16:53
kfox1111lazyPower: yeah, that would be cool.16:53
sdakelazyPower we have typically stayed away from third party gating, although this is because people misunderstand that at some point it becomes voting16:53
lazyPowerThanks sdake, glad to be here16:53
Jeffrey4l_mancdaz, will review the specs. thanks for the work.16:53
inc0Jeffrey4l_: we should release z streams for ocata at the same time16:53
sdakelazyPower so as long as you understand (infra) wont allow it to be voting, i think that is a great idea16:54
inc0lazyPower: what we need is k8s and ceph deployed, can you provide this part?16:54
*** iyamahat has quit IRC16:54
Jeffrey4l_yes. but i am thinking leave another week for ocata branch.16:54
lazyPowersdake: this is contrary information from what iw as told, which is not entirely a deal breaker but this means i have to take this new info back to management so they can weigh in. but i dont think this will be a hug eissue16:55
Jeffrey4l_will release 4.0.1 next week.16:55
lazyPowerinc0: we can, we already deploy k8s + have relations to ceph for RBD based PV enlistment16:55
sdakelazyPower openstack infrstruture just wont allow third party gates to vote16:55
sdakelazyPower its not something this team has any control over16:55
lazyPowersdake: thats understandable. I came back from the PTG with the understanding that once integrated we could be a voting gate16:55
sdakelazyPower by vote I mean block a review16:55
inc0lazyPower: alternatively to 3rd party non voting we can just write it in infra16:55
lazyPowerwhichi means i got bad info, and i'm going to have to ammend that16:55
inc0as regular infra gates16:56
*** yamahata has quit IRC16:56
sdakelazyPower join me in openstack-infra after, and we can confirm with the team16:56
lazyPowersure thing16:56
inc0I understand it's all opensource16:56
sdakelazyPower right - not sure who you got th ebad info from, this is why we hav eavoided third party gates in the past :)16:56
lazyPowerThats basically all I had, was to get the ball rolling here, and see what follow up steps we needed to take to even get started.16:56
sdakelazyPower followup step is communicating with openstack-infra about how to do third party gating16:57
sdakelazyPower asuming your fine with a nonvoting gate16:57
kfox1111lazyPower: thanks for working on it. more testing on things users really care about is always a good thing. :)16:57
*** caboucha has quit IRC16:57
sdakelazyPower happy to facilitate the conversation if anyone is around in openstack-infra in about 1 hr :)16:57
sdakelazyPower or any of the cores can do it now if they are available16:58
inc0I'll join you in a second there16:58
sdakeinc0 can handle it then, i've got a meeting in 2 minutes :)16:58
inc0anyway, we're reacing the end times16:58
inc0ok, in 1 hr then16:58
sdakeEND OF DAYS -- DADA16:58
sdakeinc0 infra knows you as well as me, you can handle it :)16:58
inc0thank you all for coming16:58
inc0kk16:59
sdakethanks everyone16:59
inc0#endmeeting kolla16:59
lazyPowersdake: can do16:59
*** openstack changes topic to " (Meeting topic: ironic_neutron)"16:59
openstackMeeting ended Wed Mar 22 16:59:08 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-03-22-15.59.html16:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-03-22-15.59.txt16:59
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-03-22-15.59.log.html16:59
*** jascott1 has left #openstack-meeting-416:59
mnaserlater folks16:59
lazyPowercheers o/16:59
*** mnaser has left #openstack-meeting-417:00
*** bobmel has quit IRC17:00
*** unicell has quit IRC17:00
*** wxy| has quit IRC17:00
*** egonzalez has quit IRC17:01
*** sayantani01 has quit IRC17:02
*** galstrom_zzz is now known as galstrom17:04
*** cjloader_ has joined #openstack-meeting-417:06
*** blallau has left #openstack-meeting-417:07
*** vhosakot has left #openstack-meeting-417:08
*** matrohon has quit IRC17:11
*** anilvenkata has joined #openstack-meeting-417:12
*** liangy has joined #openstack-meeting-417:13
*** iyamahat has joined #openstack-meeting-417:14
*** cathrichardson has joined #openstack-meeting-417:17
*** duonghq has quit IRC17:17
*** liangy has quit IRC17:17
*** pmesserli has quit IRC17:18
*** liangy has joined #openstack-meeting-417:18
*** pmesserli has joined #openstack-meeting-417:18
*** uck_ has joined #openstack-meeting-417:21
*** uck has quit IRC17:21
*** zhubingbing__ has quit IRC17:23
*** test_user has quit IRC17:23
*** bogdando has quit IRC17:29
*** mbruzek has quit IRC17:31
*** unicell has joined #openstack-meeting-417:33
*** yamahata has joined #openstack-meeting-417:35
*** links has quit IRC17:39
*** Sukhdev_ has joined #openstack-meeting-417:45
*** pmesserl_ has joined #openstack-meeting-417:50
*** pmesserli has quit IRC17:50
*** anonymike has left #openstack-meeting-417:52
*** armax has joined #openstack-meeting-417:53
*** armax has quit IRC17:54
*** anilvenkata has quit IRC17:56
*** mgoddard has quit IRC17:57
*** ltomasbo is now known as ltomasbo|away17:59
*** uck_ has quit IRC18:04
*** kzaitsev_ws has quit IRC18:04
*** uck has joined #openstack-meeting-418:04
*** ralonsoh has quit IRC18:04
*** liangy has quit IRC18:09
*** mbruzek has joined #openstack-meeting-418:10
*** mbruzek has joined #openstack-meeting-418:10
*** liangy has joined #openstack-meeting-418:23
*** ltomasbo|away is now known as ltomasbo18:26
*** bobmel has joined #openstack-meeting-418:34
*** bobmel has quit IRC18:34
*** bobmel has joined #openstack-meeting-418:34
*** armax has joined #openstack-meeting-418:41
*** uck_ has joined #openstack-meeting-418:49
*** uck has quit IRC18:49
*** vishnoianil has joined #openstack-meeting-418:49
*** ltomasbo is now known as ltomasbo|away18:55
*** rwallner has quit IRC18:55
*** rwallner has joined #openstack-meeting-418:59
*** harlowja has quit IRC18:59
*** harlowja has joined #openstack-meeting-419:00
*** harlowja has quit IRC19:01
*** MeganR has joined #openstack-meeting-419:01
*** cathrichardson has quit IRC19:04
*** armax has quit IRC19:04
*** rwellum has left #openstack-meeting-419:05
*** salmankhan has quit IRC19:08
*** Guest52040 has quit IRC19:08
*** cathrichardson has joined #openstack-meeting-419:15
*** joanna is now known as joana_lunch19:26
*** spotz is now known as spotz_zzz19:32
*** armax has joined #openstack-meeting-419:33
*** spotz_zzz is now known as spotz19:33
*** bobmel has quit IRC19:33
*** krtaylor has quit IRC19:36
*** harlowja has joined #openstack-meeting-419:45
*** marst_ has joined #openstack-meeting-419:50
*** julim_ has quit IRC19:50
*** julim has joined #openstack-meeting-419:50
*** rwallner has quit IRC19:53
*** julim has quit IRC19:53
*** marst has quit IRC19:53
*** hongbin has joined #openstack-meeting-419:54
*** uck_ has quit IRC19:56
*** julim has joined #openstack-meeting-419:56
*** julim has quit IRC20:13
*** armax has quit IRC20:16
*** vishwanathj has quit IRC20:18
*** harlowja has quit IRC20:18
*** vishwanathj has joined #openstack-meeting-420:18
*** uck has joined #openstack-meeting-420:19
*** cathrichardson has quit IRC20:21
*** cathrichardson has joined #openstack-meeting-420:22
*** cathrich_ has joined #openstack-meeting-420:23
*** cathrichardson has quit IRC20:23
*** cathrich_ is now known as cathrichardson20:23
*** srwilkers has quit IRC20:26
*** cathrichardson has quit IRC20:28
*** marst_ has quit IRC20:34
*** bobmel has joined #openstack-meeting-420:34
*** cathrichardson has joined #openstack-meeting-420:34
*** cathrich_ has joined #openstack-meeting-420:35
*** cathrichardson has quit IRC20:39
*** bobmel has quit IRC20:39
*** alex_xu has quit IRC20:43
*** MeganR has quit IRC20:44
*** alex_xu has joined #openstack-meeting-420:46
*** bzhao_ has joined #openstack-meeting-420:46
*** corey_ has quit IRC20:51
*** joana_lunch is now known as joanna20:51
*** salmankhan has joined #openstack-meeting-420:56
*** Sukhdev has quit IRC20:56
*** salmankhan has quit IRC21:00
*** cjloader_ has quit IRC21:01
*** matrohon has joined #openstack-meeting-421:02
*** krtaylor has joined #openstack-meeting-421:06
*** salmankhan has joined #openstack-meeting-421:15
*** dtardivel has quit IRC21:20
*** baoli has quit IRC21:22
*** baoli has joined #openstack-meeting-421:22
*** marst_ has joined #openstack-meeting-421:25
*** harlowja has joined #openstack-meeting-421:33
*** l4yerffeJ has quit IRC21:34
*** Jeffrey4l_ has quit IRC21:34
*** mbruzek has quit IRC21:35
*** bobmel has joined #openstack-meeting-421:35
*** galstrom is now known as galstrom_zzz21:36
*** baoli has quit IRC21:36
*** aunnam has quit IRC21:37
*** raj_singh has quit IRC21:37
*** inc0 has quit IRC21:38
*** joanna has quit IRC21:38
*** dharinic has quit IRC21:38
*** pshedimb has quit IRC21:38
*** sneti has quit IRC21:38
*** cathrich_ has quit IRC21:39
*** bobmel has quit IRC21:40
*** bobmel has joined #openstack-meeting-421:46
*** pcaruana has quit IRC21:47
*** baoli has joined #openstack-meeting-421:47
*** Jeffrey4l_ has joined #openstack-meeting-421:48
*** baoli has quit IRC21:48
*** Jeffrey4l_ has quit IRC21:50
*** Jeffrey4l_ has joined #openstack-meeting-421:50
*** haleyb has quit IRC21:50
*** bobmel has quit IRC21:51
*** sneti has joined #openstack-meeting-421:51
*** irenab has left #openstack-meeting-421:51
*** david-lyle has quit IRC21:52
*** sneti has quit IRC21:54
*** liangy has quit IRC21:55
*** sneti has joined #openstack-meeting-421:56
*** baoli has joined #openstack-meeting-421:58
*** mrunge has quit IRC22:04
*** mrunge has joined #openstack-meeting-422:07
*** turvey has quit IRC22:08
*** matrohon has quit IRC22:15
*** david-lyle has joined #openstack-meeting-422:15
*** krtaylor has quit IRC22:16
*** julim has joined #openstack-meeting-422:18
*** salmankhan has quit IRC22:21
*** salmankhan has joined #openstack-meeting-422:26
*** marst_ has quit IRC22:32
*** sneti has quit IRC22:38
*** uck has quit IRC22:40
*** uck has joined #openstack-meeting-422:40
*** tonytan4ever has joined #openstack-meeting-422:45
*** julim has quit IRC22:46
*** bobmel has joined #openstack-meeting-422:47
*** bobmel has quit IRC22:52
*** klamath has quit IRC22:57
*** baoli has quit IRC22:58
*** bzhao_ has quit IRC22:58
*** baoli has joined #openstack-meeting-422:59
*** baoli has quit IRC23:03
*** cholcombe has joined #openstack-meeting-423:11
*** hongbin has quit IRC23:19
*** pmesserl_ has quit IRC23:31
*** baoli has joined #openstack-meeting-423:33
*** bobh has quit IRC23:42
*** armax has joined #openstack-meeting-423:52

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