Wednesday, 2017-01-04

*** spzala has quit IRC00:02
*** spzala has joined #openstack-meeting-400:02
*** sdake has quit IRC00:04
*** Xeregin has quit IRC00:04
*** baoli has quit IRC00:05
*** revon has quit IRC00:13
*** salv-orlando has quit IRC00:14
*** bobh has joined #openstack-meeting-400:16
*** yamamoto has joined #openstack-meeting-400:17
*** bobh has quit IRC00:19
*** jose-phillips has quit IRC00:25
*** Swami has quit IRC00:32
*** Julien-zte has joined #openstack-meeting-400:32
*** hongbin has quit IRC00:32
*** limao has joined #openstack-meeting-400:47
*** yfauser has joined #openstack-meeting-400:48
*** tovin07 has joined #openstack-meeting-400:51
*** itisha has quit IRC00:52
*** yfauser has quit IRC00:54
*** thorst has joined #openstack-meeting-400:55
*** SerenaFeng has joined #openstack-meeting-400:57
*** thorst has quit IRC00:58
*** yamamoto has quit IRC01:04
*** mattmceuen has quit IRC01:05
*** salv-orlando has joined #openstack-meeting-401:15
*** salv-orlando has quit IRC01:20
*** unicell has joined #openstack-meeting-401:24
*** woodard has quit IRC01:24
*** Syed__ has quit IRC01:25
*** sdake has joined #openstack-meeting-401:33
*** woodard has joined #openstack-meeting-401:39
*** sdake_ has joined #openstack-meeting-401:50
*** yfauser has joined #openstack-meeting-401:50
*** dave-mccowan has joined #openstack-meeting-401:52
*** sdake has quit IRC01:52
*** woodard has quit IRC01:53
*** thorst has joined #openstack-meeting-401:54
*** yfauser has quit IRC01:55
*** bobh_ has joined #openstack-meeting-401:59
*** yamamoto has joined #openstack-meeting-402:02
*** gongysh has joined #openstack-meeting-402:03
*** dave-mcc_ has joined #openstack-meeting-402:06
*** dave-mccowan has quit IRC02:08
*** yfauser has joined #openstack-meeting-402:10
*** yfauser has quit IRC02:15
*** salv-orlando has joined #openstack-meeting-402:16
*** unicell has quit IRC02:19
*** thorst has quit IRC02:21
*** salv-orlando has quit IRC02:21
*** thorst has joined #openstack-meeting-402:21
*** thorst has quit IRC02:25
*** sdake_ has quit IRC02:29
*** rainya has joined #openstack-meeting-402:31
*** rainya has quit IRC02:31
*** dave-mcc_ has quit IRC02:33
*** dave-mccowan has joined #openstack-meeting-402:39
*** s3wong has quit IRC02:45
*** mattmceuen has joined #openstack-meeting-402:46
*** thorst has joined #openstack-meeting-402:47
*** sdake has joined #openstack-meeting-402:49
*** thorst has quit IRC02:49
*** dave-mccowan has quit IRC03:01
*** yfauser has joined #openstack-meeting-403:11
*** yfauser has quit IRC03:16
*** hongbin has joined #openstack-meeting-403:17
*** mriedem has quit IRC03:22
*** thorst has joined #openstack-meeting-403:35
*** prateek has quit IRC03:36
*** prateek has joined #openstack-meeting-403:36
*** thorst has quit IRC03:36
*** prateek has quit IRC03:45
*** links has joined #openstack-meeting-403:56
*** SerenaFeng has quit IRC03:59
*** bobh_ has quit IRC04:02
*** bobh has joined #openstack-meeting-404:06
*** janonymous has joined #openstack-meeting-404:09
*** baoli has joined #openstack-meeting-404:10
*** bobh has quit IRC04:11
*** yfauser has joined #openstack-meeting-404:12
*** baoli has quit IRC04:15
*** spzala has quit IRC04:16
*** psachin has joined #openstack-meeting-404:16
*** limao has quit IRC04:16
*** yfauser has quit IRC04:17
*** salv-orlando has joined #openstack-meeting-404:17
*** salv-orlando has quit IRC04:21
*** hongbin has quit IRC04:22
*** thorst has joined #openstack-meeting-404:37
*** thorst has quit IRC04:41
*** cartik has joined #openstack-meeting-404:50
*** janki has joined #openstack-meeting-404:52
*** unicell has joined #openstack-meeting-405:01
*** limao has joined #openstack-meeting-405:02
*** reedip has joined #openstack-meeting-405:05
*** yfauser has joined #openstack-meeting-405:34
*** yfauser has quit IRC05:38
*** prateek has joined #openstack-meeting-405:44
*** SerenaFeng has joined #openstack-meeting-405:44
*** s3wong has joined #openstack-meeting-405:46
*** ricolin has joined #openstack-meeting-405:47
*** SerenaFeng has quit IRC05:53
*** jovon has joined #openstack-meeting-406:14
*** amotoki has joined #openstack-meeting-406:22
*** Kevin_Zheng has joined #openstack-meeting-406:35
*** thorst has joined #openstack-meeting-406:38
*** nbloom has joined #openstack-meeting-406:41
*** thorst has quit IRC06:42
*** salv-orlando has joined #openstack-meeting-406:43
*** usman has joined #openstack-meeting-406:46
*** pcaruana has joined #openstack-meeting-406:51
*** yfauser has joined #openstack-meeting-406:55
*** nkrinner_afk has quit IRC06:59
*** yfauser has quit IRC06:59
*** nkrinner has joined #openstack-meeting-406:59
*** elisha_r has joined #openstack-meeting-407:19
*** yfauser has joined #openstack-meeting-407:24
*** yujunz has joined #openstack-meeting-407:26
*** salv-orlando has quit IRC07:39
*** SerenaFeng has joined #openstack-meeting-407:49
*** s3wong has quit IRC07:52
*** eyalb has joined #openstack-meeting-407:54
*** ifat_afek has joined #openstack-meeting-407:56
*** danoffek has joined #openstack-meeting-407:57
danoffekHI guys07:57
*** gongysh_ has joined #openstack-meeting-407:59
*** cartik has quit IRC07:59
*** matrohon has joined #openstack-meeting-407:59
ifat_afek#startmeeting vitrage08:00
openstackMeeting started Wed Jan  4 08:00:21 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
*** gongysh has quit IRC08:00
openstackThe meeting name has been set to 'vitrage'08:00
ifat_afekHi :-)08:00
danoffekHi guys08:00
nbloomHello!!!08:00
eyalbhi08:00
yujunzhi08:01
*** dwj has joined #openstack-meeting-408:01
ifat_afek#topic Status and Updates08:02
*** openstack changes topic to "Status and Updates (Meeting topic: vitrage)"08:02
ifat_afekOcata development is about to end this month. The feature freeze is on January 27.08:03
ifat_afek#link https://releases.openstack.org/ocata/schedule.html08:03
ifat_afekBoston CFP is now open. Let’s start thinking about ideas for sessions. We can submit proposals until February 6th.08:03
ifat_afek#link https://www.openstack.org/summit/boston-2017/call-for-presentations/08:03
yujunzWhat features are ready for ocata at the moment?08:04
elisha_rhello08:04
ifat_afekI will finish the Doctor impelmentation (will update about it soon), and hopefully eyalb will finish the collectd integration08:04
ifat_afekI’m doing a fast-fowrard update here ;-) maybe we should ask everyone to update about their own status08:05
*** nadav has joined #openstack-meeting-408:05
*** alexey_weyl has joined #openstack-meeting-408:05
alexey_weylHi Guys :)08:05
danoffekHi. Working on Vitrage ID.08:05
yujunzI will continue working on static data source and I think it will catch up with ocata08:05
ifat_afekSo I’ll update about Doctor: I’m done writing a Doctor datasource for Vitrage, that will implement Doctor SB API. Waiting for your code reviews.08:05
nadavhi08:06
ifat_afek#link https://review.openstack.org/#/c/414742/08:06
ifat_afek#link https://review.openstack.org/41497508:06
ifat_afekI suggest we go one by one, and then have a topic about Ocata. Makes sense?08:06
yujunzAgree08:06
ifat_afekSo who has other updates?08:07
yujunzI will08:07
yujunzstatic datasource is pending for a few weeks and now resumed08:08
yujunzI'll finish the transformer part as soon as possible08:08
yujunzBut I have a question on the recent refactoring on transformer08:08
yujunzWill it affect static datasource?08:08
yujunz#link https://review.openstack.org/#/c/415684/08:09
yujunzping alexey_weyl08:09
yujunzOK, I saw a reply on gerrit08:10
alexey_weylyes, it will affect you a bit, but don't use it yet, because the Doctor datasource should be pushed first, and then we will approve the refactoring08:10
yujunzIs there any background for this refactoring?08:10
yujunzWhat is changed in summary?08:10
alexey_weylafter that you can pull it from the master and use it, but don't worry it's not such a big change08:10
yujunzOK08:11
alexey_weylthe reason fro the refactoring is that there are 2 new datasources that are being added to Vitrage at the moment, and they saw that those methods of the create_placeholder and the create_neighbor are basically the same and should sit at the base where everyone can use it08:12
yujunzI see. Maybe adding these notes into the commit message will help reviewers to understand :-)08:13
ifat_afekalexey_weyl: you just moved a function to the base class, right?08:13
alexey_weylyujunz: no problem :)08:13
yujunzOK thanks. That's all from my side08:14
alexey_weylifat_afek: kind of, I moved them, and adjusted them so they will be much more robust for usage08:14
ifat_afekalexey_weyl: ok, thanks. I’ll review it soon08:14
alexey_weylThanks08:14
ifat_afekI forgot another update on my side: I plan to start writing another blueprint, for implementing Doctor SB API in Vitrage. We should have an API for “send event” or something similar, that will send the event to the message bus. Then, Doctor datasource will read it from there08:15
ifat_afekAnyone else wants to update?08:16
eyalbI am still working on the collectd datasource08:16
*** jchhatbar has joined #openstack-meeting-408:17
usmanHello everyone08:17
alexey_weylI am waiting for feedback from aodh on the commits that I have pushed08:18
ifat_afekHi usman08:18
alexey_weylyou can see the changes here:08:18
alexey_weylhttps://review.openstack.org/#/c/413008/08:18
ifat_afekalexey_weyl: did you push all of your code, or is it just the first phase?08:18
alexey_weylhttps://review.openstack.org/#/c/413594/08:18
alexey_weylnot all the code yet, but anyfeedback would be great08:19
*** janki has quit IRC08:19
ifat_afekalexey_weyl: Great. I’ll try to review, although I’m not familiar with Aodh code08:19
ifat_afekAny other update anyone?08:20
ifat_afek#topic Ocata Release08:21
*** openstack changes topic to "Ocata Release (Meeting topic: vitrage)"08:21
ifat_afekSo let’s see what we expect to have ready for Ocata08:21
ifat_afekDoctor Datasource + SB API should be ready08:21
yujunzlow risk on static datasource evolution08:22
danoffekVitrage Id08:22
ifat_afekdwj: Are you here? you finished the Aodh notifications for Vitrage, right? I see that the blueprint is still open08:22
dwjyes08:23
ifat_afekhttps://blueprints.launchpad.net/vitrage/+spec/aodh-message-bus-notifications08:23
ifat_afekBTW, you can see all Ocata blueprints here:08:23
dwjIt's already finished08:23
ifat_afek#link https://blueprints.launchpad.net/vitrage/+spec/aodh-message-bus-notifications08:23
ifat_afek#link https://blueprints.launchpad.net/vitrage/ocata08:23
dwjI'll change the status later08:23
ifat_afekdwj: great, thanks08:23
ifat_afekeyalb: what about collectd and red hat?08:23
eyalbI hope so  :-)08:24
ifat_afekgreat08:24
ifat_afekalexey_weyl: I guess Aodh is in risk because you got no reviews yet?08:24
yujunzWhat is red hat?08:25
yujunzapex installer?08:25
alexey_weylyes, it is a risk, because there are a lot of stuff yet to do there, and I need to get feedbacks and responses from the Aodh team08:25
ifat_afekyujunz: We would like to support Apex installer, and base it on TripleO installation. Currently we are waiting for RDO08:25
eyalbI pushed the initial spec file of vitrage to rdo and I am waiting for there response08:26
ifat_afekSo the apex installer is also in risk08:26
yujunzSo red hat = https://blueprints.launchpad.net/vitrage/+spec/support-tripleo-instllation08:26
yujunzright?08:26
yujunzAnd apex is another story08:26
ifat_afek(But the apex installer not a pure Vitrage task, it’s an OPNFV one)08:27
ifat_afekyujunz: right08:27
ifat_afekBoth are in risk08:27
yujunzI see. Thanks08:28
ifat_afekeyalb: I’ll mark collectd blueprint for Ocata as well08:28
ifat_afek#link https://blueprints.launchpad.net/vitrage/+spec/collectd-datasource08:28
eyalbok08:28
ifat_afekAnything that I forgot?…08:29
yujunzHow is neo4j going?08:30
yujunzAny chance to get it ready?08:30
ifat_afekBTW, yujunz: eyalb is working on collectd datasource, and collectd DPDK plugin raises alarms on the bridges. This is the reason he wants to use the new static datasource08:30
yujunzThanks for reminding ifat_afek. I'll try to speed up08:31
ifat_afekyujunz: no problme08:32
yujunzHow about neo4j?08:33
*** SerenaFeng has quit IRC08:33
alexey_weylyujunz: at the moment we are thinking about our steps regarding the neo4j because in the community edition it doesn't support HA, and thus it is a problem.08:33
*** SerenaFeng has joined #openstack-meeting-408:33
ifat_afekyujunz: and in any case, I doubt if have enough time left to finish it for Ocata08:33
yujunzIs there a big gap to migrate community edition to commercial neo4j?08:34
ifat_afekyujunz: there are two issues with the commerical Neo4J08:34
yujunzI mean integrate community version in openstack/vitrage and leave it to commercial user the migration tasks08:34
alexey_weylThe persistent graph DB is very important, but we need to make sure that we are using the correct one that gives us the most tools as a DB.08:35
ifat_afekYou can either pay for the license, or use GPL3 license which is “contaminating” (meaning your entire code must become open source as well)08:35
yujunzOK, so the community version is licensed under GPL308:35
yujunzThat's really something08:36
ifat_afekYour suggestion is to have non-HA version in openstack, and a possibility to use the commercial version in another product (Nokia/ZTE)?08:36
ifat_afekthe community version is apache license, no problem with that. The commerical version is GPL308:36
yujunzYes, things like that08:36
*** gongysh_ has quit IRC08:37
yujunzAlright, I kind of understand the issue now08:37
ifat_afekI already checked the license issue. Neo4j does not exist in openstack at the moment, but there is no problem to add it to the global requirements (I believe the package name is py2neo)08:38
*** thorst has joined #openstack-meeting-408:39
ifat_afekBut we did not check the issue of using the community version vs. the commerical version in different distributions08:39
*** jovon has quit IRC08:40
yujunzI guess we need a lawyer for this issue :-)08:40
ifat_afekRight :-)08:40
yujunzIs there any alternative solution?08:40
yujunzI remember we mentioned another in summit08:40
ifat_afekWe did not investigate it yet08:40
yujunzBut forgot the name08:41
ifat_afekI know there are a few graph databases, but I don’t know of anyone from Vitrage who did a thorough evaluation08:41
ifat_afekI don’t remember either08:41
*** thorst has quit IRC08:43
ifat_afekAnything else, for Ocata or on a different topic?08:44
*** anilvenkata has joined #openstack-meeting-408:45
ifat_afekSee you next week!08:46
*** danoffek has left #openstack-meeting-408:47
nbloombye :)08:47
eyalbbye08:47
yujunzSee08:47
alexey_weylbye bye08:47
dwjbye08:47
*** alexey_weyl has quit IRC08:47
*** nbloom has quit IRC08:47
usmanbye08:47
ifat_afek#endmeeting08:47
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:47
openstackMeeting ended Wed Jan  4 08:47:54 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vitrage/2017/vitrage.2017-01-04-08.00.html08:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2017/vitrage.2017-01-04-08.00.txt08:47
openstackLog:            http://eavesdrop.openstack.org/meetings/vitrage/2017/vitrage.2017-01-04-08.00.log.html08:47
*** yujunz has left #openstack-meeting-408:48
*** Yumeng has joined #openstack-meeting-408:48
*** ifat_afek has left #openstack-meeting-408:48
*** salv-orlando has joined #openstack-meeting-408:49
*** gongysh has joined #openstack-meeting-408:51
*** cartik has joined #openstack-meeting-408:53
*** vincentfrancoise has joined #openstack-meeting-408:59
*** dtardivel has joined #openstack-meeting-408:59
*** licanwei has joined #openstack-meeting-408:59
acabot#startmeeting watcher09:00
openstackMeeting started Wed Jan  4 09:00:05 2017 UTC and is due to finish in 60 minutes.  The chair is acabot. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
*** openstack changes topic to " (Meeting topic: watcher)"09:00
openstackThe meeting name has been set to 'watcher'09:00
*** hidekazu has joined #openstack-meeting-409:00
vincentfrancoiseo/09:00
sballe_Hi09:00
acaboto/09:00
hidekazuhi09:00
acabothappy new year everyone !09:00
licanweihi09:00
sballe_Thx09:00
dtardivelhi09:00
acabot#info our agenda for today #link https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#01.2F04.2F201609:01
vincentfrancoiseHappy New Year !09:01
acabot#topic Announcements09:01
*** openstack changes topic to "Announcements (Meeting topic: watcher)"09:01
dtardivelBonne Année 2017 - Happy New Year to you all09:01
*** iyamahat has joined #openstack-meeting-409:01
acabot#info Watcher ocata-2 has been released on December 15th09:02
*** atuly has joined #openstack-meeting-409:02
acabotwe missed 2 BPs for this release because of late reviews09:02
sballe_+109:02
acabotsorry alexchadin for postponing your 2 BPs to ocata-309:02
acabotso now we have 12 BPs for ocata-3 !09:02
Yumenghi09:03
acabot#info Pike PTLs self nomination will start January 23rd and Watcher needs to find a new PTL09:03
*** ricolin has quit IRC09:03
acabotas said in the ML #link http://lists.openstack.org/pipermail/openstack-dev/2016-December/109019.html I wont be candidate for a 4th cycle09:03
acabotso please think about becoming Watcher PTL before January 23rd09:04
acabot;-)09:04
*** iyamahat has quit IRC09:04
acabotyou should also know that nobody from bcom will be candidate (vincentfrancoise, dtardivel, jed56)09:05
acabotand I'd like to avoid having no candidate for the election :-)09:06
acabotlets move on09:06
acabot#topic Review Action Items09:06
*** openstack changes topic to "Review Action Items (Meeting topic: watcher)"09:06
acabotwe really need to finalize a couple of specs here09:06
acabotAudit tag in VM Metadata There are +1s but TODOs are still left in spec09:06
acabot#link https://review.openstack.org/#/c/391374/09:07
acabothvprash told me that he will work on this one this week09:07
acabot#actio hvprash complete and finalize spec https://review.openstack.org/#/c/391374/09:07
acabot#action hvprash complete and finalize spec https://review.openstack.org/#/c/391374/09:08
acabotDefine grammar for workload characterization needs a new PS an answering previous comments09:08
acabot#link https://review.openstack.org/#/c/377100/09:08
acabotsballe : could you please try to add a new PS ?09:08
acabotsballe_ : could you please try to add a new PS ?09:09
sballe_Yes hvprash and I will do that this week09:09
acabot#action hvprash sballe_ : answer comments on https://review.openstack.org/#/c/377100/09:09
acabotSupport Description For Dynamic Action needs a new PS09:09
acabot#link https://review.openstack.org/#/c/401111/09:10
acabotis hanrong here ?09:10
acabot#action hanrong add a new PS on https://review.openstack.org/#/c/401111/09:11
Yumengnope. she will join very soon09:11
acabotYumeng : thx09:11
acabotSpec for Noisy Neighbor Startegy needs reviews09:11
acabot#link https://review.openstack.org/#/c/398162/09:11
acabotwho wants to review this strategy ?09:11
*** eyalb has left #openstack-meeting-409:11
acabotAdd improvements to the planner and workflow mechanisms needs final reviews09:12
acabot#link https://review.openstack.org/#/c/385871/09:12
sballe_ I can review09:12
acabot#action sballe_ acabot : final review on https://review.openstack.org/#/c/385871/09:13
*** ricolin has joined #openstack-meeting-409:13
acabotAdd improvements to Applier to make it parallel needs reviews09:13
acabot#link https://review.openstack.org/#/c/413079/09:13
acabot#action sballe_ acabot hvprash review https://review.openstack.org/#/c/413079/09:14
acabotcluster energy saving needs to be resubmitted as launchpad does not allow to change the superseded state09:14
hidekazui want to review09:14
acabot#action hidekazu review https://review.openstack.org/#/c/413079/09:14
acabot#link https://blueprints.launchpad.net/watcher/+spec/cluster-energy-saving09:14
acabotYumeng hanrong : I cant remove the superseded state in launchpad so could you resubmit your BP with the same description ?09:15
acabotI'd like to keep the ZTE origin of drafted bps09:15
acabotYumeng : could you do it ?09:16
Yumengyes, will do.09:17
acabot#action Yumeng resubmit BP https://blueprints.launchpad.net/watcher/+spec/cluster-energy-saving as a new PB09:17
Yumengactually i think hanrong has updated that .. i didn't find the link09:17
acabotshe updated the description09:17
acabotbut I cant remove the superseded state09:18
acabotmoving to Watcher09:18
acabotAdd auto_trigger support to watcher needs final reviews & merge09:18
acabot#link https://review.openstack.org/#/c/403718/09:18
acabotdo we need to create a new BP for BDB migration before moving on ?09:19
vincentfrancoiseacabot: I can review this one09:19
*** SerenaFeng has quit IRC09:19
sballe_ Me too09:19
acabot#action vincentfrancoise sballe_ review https://review.openstack.org/#/c/403718/09:19
sballe_What's BDB?09:19
acabotsorry DB09:19
*** SerenaFeng has joined #openstack-meeting-409:20
sballe_😀09:20
acabotGraph model needs reviews09:20
acabot#link https://review.openstack.org/#/c/362730/09:20
vincentfrancoiseacabot: if we want to have a Watcher 1.0, yes09:20
acabotI'd like to have it merge by octata-309:20
acabot#action acabot submit a BP to handle DB migration09:21
acabotwho wants to review the graph model ?09:21
vincentfrancoiseacabot: I started already so count me on09:21
acabotok thx09:21
acabot#action vincentfrancoise review https://review.openstack.org/#/c/362730/09:22
acabotAdded Monasca Helper needs reviews09:22
acabot#link https://review.openstack.org/#/c/348891/09:22
sballe_I can review09:23
acabotwho wants to review ?09:23
hidekazuI will09:23
acabotthx09:23
dtardivel+109:24
acabot#action sballe_ hidekazu dtardivel review https://review.openstack.org/#/c/348891/09:24
acabotMulti datasource support for Basic Consolidation needs discussions09:24
acabot#link https://review.openstack.org/#/c/414617/09:24
*** dwj has quit IRC09:24
acabotthe point from licanwei is should we add an abstraction layer09:25
acabotto deal with multiple datasource (Monasca, Gnocchi)09:25
acabotit has been a very long discussion on our side09:25
acabotvincentfrancoise proposed a BP for that #link https://blueprints.launchpad.net/watcher/+spec/watcher-multi-datasource09:26
acabotfor now we decided to implement a basic version with backend choice in the strategy09:27
*** tinwood has quit IRC09:27
acabotit means that every strategy will be specific to a metrics backend09:27
*** tmetsch has joined #openstack-meeting-409:27
acabotwho wants to review https://review.openstack.org/#/c/414617/ ?09:28
dtardivel+109:28
acabot#action dtardivel review https://review.openstack.org/#/c/414617/09:28
acabotNew default planner & check the state of action plan needs final reviews09:28
acabot#link https://review.openstack.org/#/c/406991/09:29
acabot#link https://review.openstack.org/#/c/391383/09:29
acabotNew default planner needs to be discussed with alexchadin09:30
vincentfrancoise+109:30
vincentfrancoiseI proposed an alternative that I would like to discuss with him09:30
acabot#action vincentfrancoise dtardivel : sync with alexchadin about https://review.openstack.org/#/c/406991/09:30
vincentfrancoise#link https://review.openstack.org/#/c/415505/09:30
acabot#action vincentfrancoise dtardivel final reviews on https://review.openstack.org/#/c/391383/09:32
acabotWatcher CLI09:32
acabotAdd auto_trigger support needs final reviews & merge09:32
acabot#link https://review.openstack.org/#/c/403716/09:32
dtardivelacabot: there is a Depends-On rule09:33
acabot#action dtardivel review & merge https://review.openstack.org/#/c/403716/09:34
acabot#topic Blueprint/Bug Review and Discussion09:34
*** openstack changes topic to "Blueprint/Bug Review and Discussion (Meeting topic: watcher)"09:34
*** Yumeng__ has joined #openstack-meeting-409:34
acabotWatcher ocata-3 has started and finishes on January 23rd with 12 BPs to finish09:34
acabot#info Watcher ocata-3 has started and finishes on January 23rd with 12 BPs to finish09:34
acabot#link https://launchpad.net/watcher/+milestone/ocata-309:34
acabotwe wont be able to deliver 12 BPs in 2 weeks !09:35
acabotwe should focus on "needs code review" BP !09:35
dtardivel+109:35
acabotI will move the others to the next release09:36
acabotdoes any one can update the status of his/her BPs ? set as started if it is09:36
acabotI will move all not started or unknown state BPs to ocata-rc today09:37
Yumengi have just started https://blueprints.launchpad.net/watcher/+spec/watcher-api-validation09:37
Yumengbut also pls  move it to ocata-rc09:38
acabotYumeng : do you plan to write a spec for it ?09:38
acabotYumeng : you can use the one from keystone https://review.openstack.org/#/c/95957/14/specs/juno/keystone-api-validation.rst09:39
Yumengi am doing with the code about initial implementation of the validator framework09:39
Yumengcan i just submit a rough implementaion first ?09:40
acabotYumeng : sure you can09:40
Yumengand see what's your suggestions09:40
Yumengok, thx09:40
vincentfrancoiseYumeng: Can you explain to me/us how you want to do it?09:40
Yumengi was following this https://review.openstack.org/#/c/86483/09:41
Yumengbut keep update with the new code in keystone09:41
vincentfrancoiseYumeng: the idea was to use jsonschema if I remember correctly09:42
Yumengyes, i will use jsonschema09:42
vincentfrancoiseYumeng: ok09:43
vincentfrancoiseYumeng: if you need help or you are not sure, please do ping me ;)09:43
acabot#action acabot move all unstarted BPs to ocata-rc109:44
Yumengvincentfrancoise: thx09:44
acabot#topic Open discussions09:44
*** openstack changes topic to "Open discussions (Meeting topic: watcher)"09:44
acabot15 mins left for open discussions09:44
hidekazuacabot: https://bugs.launchpad.net/watcher/+bug/1640105 was fixed actually.09:45
openstackLaunchpad bug 1640105 in watcher "Change hardware.cpu_util to compute.node.cpu.percent in workload_stabilization" [Medium,In progress] - Assigned to Hidekazu Nakamura (nakamura-h)09:45
acabotYumeng : do you know the priority on your side for cluster-energy-saving ?09:45
Yumengi don't know09:45
acabothidekazu : ok this is because you didn't mention Closes-Bug in your commit msg09:46
acabotI will update09:46
vincentfrancoiseacabot: I did it ;)09:46
hidekazuacabot: yes, sorry.09:46
acabotanyone has submitted a new BP during holidays ?09:47
acabotI could have missed it09:47
*** tinwood has joined #openstack-meeting-409:47
acabotI will create Pike cycle in launchpad soon and start adding next BPs09:48
Yumengacabot: can we have the priority of  cluster-energy-saving as "high" ?09:48
acabotYumeng : I can set it as high but it will be in the Pike cycle09:49
Yumengaha~ that's ok09:49
acabot#link https://blueprints.launchpad.net/watcher/ocata09:49
Yumengthx09:50
acabotwe still have 3 BPs with high priority that needs to be implemented09:50
*** jchhatbar_ has joined #openstack-meeting-409:50
acabotany other topic to discuss ?09:51
acabotso thank you all09:52
acabotsee you next week09:52
*** limao has quit IRC09:52
acabot#endmeeting09:52
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:52
openstackMeeting ended Wed Jan  4 09:52:36 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/watcher/2017/watcher.2017-01-04-09.00.html09:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/watcher/2017/watcher.2017-01-04-09.00.txt09:52
openstackLog:            http://eavesdrop.openstack.org/meetings/watcher/2017/watcher.2017-01-04-09.00.log.html09:52
vincentfrancoisebye09:52
*** pbourke has quit IRC09:52
*** vincentfrancoise has left #openstack-meeting-409:52
*** hidekazu has left #openstack-meeting-409:53
*** pbourke has joined #openstack-meeting-409:53
*** Julien-zte has quit IRC09:53
*** tmetsch has left #openstack-meeting-409:53
*** jchhatbar has quit IRC09:53
*** salv-orl_ has joined #openstack-meeting-409:53
Yumeng__Bye09:54
*** apuimed|away is now known as apuimedo09:56
*** salv-orlando has quit IRC09:56
*** l4yerffeJ has quit IRC10:03
*** l4yerffeJ_ is now known as l4yerffeJ10:03
*** tovin07 has quit IRC10:05
*** nadav has quit IRC10:13
*** anilvenkata has quit IRC10:17
*** zhurong has joined #openstack-meeting-410:26
*** diga has joined #openstack-meeting-410:29
*** anilvenkata has joined #openstack-meeting-410:29
*** armax has joined #openstack-meeting-410:36
*** thorst has joined #openstack-meeting-410:39
*** pbourke has quit IRC10:41
*** pbourke has joined #openstack-meeting-410:41
*** yamahata has quit IRC10:42
*** thorst has quit IRC10:44
*** yamamoto has quit IRC10:47
*** SerenaFeng has quit IRC10:49
*** links has quit IRC10:57
*** sambetts|afk is now known as sambetts11:04
*** salv-orl_ has quit IRC11:05
*** matrohon has quit IRC11:09
*** zhurong has quit IRC11:19
*** tovin07 has joined #openstack-meeting-411:19
*** links has joined #openstack-meeting-411:21
*** gongysh has quit IRC11:21
*** dtardivel has quit IRC11:23
*** salv-orlando has joined #openstack-meeting-411:28
*** anilvenkata has quit IRC11:32
*** yamamoto has joined #openstack-meeting-411:40
*** yamamoto has quit IRC11:46
*** anilvenkata has joined #openstack-meeting-411:46
*** yamamoto has joined #openstack-meeting-411:47
*** sdake has quit IRC11:49
*** sshnaidm|afk is now known as sshnaidm11:51
*** yamamoto has quit IRC11:51
*** diga has quit IRC11:55
*** Yumeng has quit IRC12:03
*** neiljerram has joined #openstack-meeting-412:07
*** Yumeng__ has quit IRC12:11
*** karthiks has quit IRC12:11
*** yamamoto has joined #openstack-meeting-412:17
*** rtheis has joined #openstack-meeting-412:26
*** ricolin has quit IRC12:29
*** cartik has quit IRC12:30
*** cdelatte has joined #openstack-meeting-412:30
*** rtheis_ has joined #openstack-meeting-412:30
*** rtheis has quit IRC12:33
*** rtheis has joined #openstack-meeting-412:40
*** thorst has joined #openstack-meeting-412:41
*** rtheis_ has quit IRC12:42
*** yamamoto has quit IRC12:42
*** tovin07 has quit IRC12:55
*** salv-orlando has quit IRC12:56
*** zhurong has joined #openstack-meeting-412:57
*** licanwei has quit IRC12:58
*** matrohon has joined #openstack-meeting-412:59
*** cdent has joined #openstack-meeting-413:00
*** dtardivel has joined #openstack-meeting-413:00
*** psachin has quit IRC13:00
alex_xu#startmeeting nova api13:00
openstackMeeting started Wed Jan  4 13:00:07 2017 UTC and is due to finish in 60 minutes.  The chair is alex_xu. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: nova api)"13:00
openstackThe meeting name has been set to 'nova_api'13:00
*** psachin has joined #openstack-meeting-413:00
alex_xuwho is here today?13:00
Kevin_Zhengo/13:00
cdento/13:00
alex_xulet us wait one more minute13:00
alex_xui'm not sure all the people back from holiday yet13:02
alex_xuso....13:02
johnthetubaguyo/13:02
alex_xu#topic open13:02
*** openstack changes topic to "open (Meeting topic: nova api)"13:02
alex_xu#link https://review.openstack.org/#/c/393205/13:03
alex_xuthe servers filter spec merged \o/13:03
alex_xu#link https://review.openstack.org/#/q/status:open++branch:master+topic:bp/consistent-query-parameters-validation13:03
alex_xuthe base part is close i guess13:03
*** licanwei has joined #openstack-meeting-413:03
alex_xu#link https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/add-whitelist-for-server-list-filter-sort-parameters13:03
Kevin_ZhengI found some typo in the spec when I coding though13:03
alex_xuKevin_Zheng is working on the servers list query parameters13:04
alex_xuKevin_Zheng: which one?13:04
alex_xuKevin_Zheng: oops, you mean the spec, we can fix it quickly13:04
Kevin_Zhenghttps://review.openstack.org/#/c/415115/13:04
Kevin_Zhengyeah13:04
*** sdague has joined #openstack-meeting-413:04
johnthetubaguyyeah, that looks like good fixes to me13:05
*** rfolco has joined #openstack-meeting-413:05
johnthetubaguyall_tenants missing its s was the nasty one I guess13:06
Kevin_Zhenghaha yes13:06
alex_xuFor filters, return 400 when joined-table and internal attributes specified, I didn't find a good implementation13:06
*** bobmel has joined #openstack-meeting-413:06
*** salv-orlando has joined #openstack-meeting-413:07
*** bobh has joined #openstack-meeting-413:07
alex_xuIs it ok we only return 400 for sort with joined-table and internal attributes? For filters, we just ignore all the extra filters, that also matches the current filters behaviour13:07
alex_xuProbably I just want to remove the 'filters' from this line https://review.openstack.org/#/c/393205/21/specs/ocata/approved/add-whitelist-for-server-list-filter-sort-parameters.rst@4513:08
*** dave-mccowan has joined #openstack-meeting-413:08
johnthetubaguyhmm, maybe13:09
johnthetubaguyits a shame to go from 500 error to silent failure13:09
*** bobmel has quit IRC13:11
alex_xuactually we ignore extra filters also13:11
alex_xuonly not ignore few of them13:11
alex_xuBut we can have a try the implement it, I have a idea, then we take a look at whether we want to put that in the code13:12
alex_xuit will pretty similar to sort implementation https://review.openstack.org/#/c/415142/11/nova/api/validation/parameter_types.py13:13
*** janonymous has quit IRC13:14
*** elisha_r has quit IRC13:14
johnthetubaguyyeah, seems worth a try13:14
johnthetubaguyI mean we might decide its better not to bother, but I would like to try13:14
alex_xuok, cool13:15
johnthetubaguylonger term, we add a microversion and they are all 400 I guess13:15
alex_xuKevin_Zheng: later I will talk to you the idea with chinese :)13:15
alex_xujohnthetubaguy: yea13:15
Kevin_Zhengyeah13:15
johnthetubaguyI guess if we can get closer to that, cool, if not, then we know how to fix it later13:16
*** yamamoto has joined #openstack-meeting-413:16
alex_xuok13:16
*** sdake has joined #openstack-meeting-413:16
alex_xuso...we only this one priority task. and we are cool now13:17
alex_xuanything more people want to talk about?13:17
alex_xu#link https://etherpad.openstack.org/p/ocata-nova-priorities-tracking13:18
sdagueo/13:18
alex_xu^ we have few non-priority api changes, I also put them in the etherpad, people can track it13:18
johnthetubaguyawesome, thats my usual question answered already13:18
alex_xusdague: anything more in your mind, we are close to the end of meeting :)13:19
sdaguenope, I'm fine, just saying I was around, I can start reviewing code before too long13:19
alex_xu#link  https://review.openstack.org/38655513:20
alex_xujohnthetubaguy: sdague in the priority task, we also mention ^ that13:20
alex_xubut except review, i guess there isn't any more we can do for it, right?13:20
johnthetubaguyyeah, if we could all be +1 on that before the PTG, so we can talk about an implementation plan at the PTG, that would be awesome13:21
johnthetubaguyor ideally have a nova spec to agree before the PTG I guess13:21
*** itisha has joined #openstack-meeting-413:21
alex_xuok, try to review it more13:22
johnthetubaguycdent has some interesting questions on that one about instance capabilities, not sure I understand his concern yet13:23
*** bobh has quit IRC13:23
* cdent refreshes his memory13:23
cdentah, that13:23
cdentmy main concern is that capabilities should be on types, not instances13:23
johnthetubaguyI guess its  GET /volume/{volume_id}/capabilities vs adding caps into  GET /volume/{volume_id} ?13:23
johnthetubaguycdent: its on both right now13:24
cdentright, and I think that's wrong13:24
johnthetubaguybasically because the type is not a type, its more a template13:24
cdentif an instance of thing has special capabilities, those things should be represented _within_ the resource's representation13:24
johnthetubaguyflavor + image gives you something thats a combination of the two13:24
cdentas they are specific to it13:24
cdenta capability ought to be a generic thing13:24
johnthetubaguyso GET /volume/{volume_id}/capabilities vs adding caps into  GET /volume/{volume_id} ?13:25
cdentI also worry that we are thinking about capabilities with too much of an eye to existing situations in nova and cinder, rather than a more general thing. Obviously those things need to meet somewhere in the middle (not be just general) but I think we can consider the general case a bit more.13:26
johnthetubaguyits not data we return today, basically something missing in the representation13:26
cdentyeah13:26
cdent /capabilities/volume is a fairly static thing (but deployment specific)13:26
cdentwhereas /volume/{volument_id} _has_ capabilities13:27
cdentthat are dependent on "stuff"13:27
johnthetubaguyso to be specific, the example is "can I do a volume backup?"13:28
sdagueit feels like from a user perspective though the question the user is going to ask is "can I do X to this thing in front of me"13:28
johnthetubaguysome clouds don't do that, some volume types don't do that, and some volumes land somewhere thats not possible13:28
cdentfor any volumen, we answer that question under /capabilities13:28
*** yamamoto has quit IRC13:28
cdentfor an existing volume, we ask the volume13:29
cdent(goodness my typing is poor)13:29
johnthetubaguywell, I think can any volume in this cloud do action X? can any volume of this type do action X? can my volume uuid-5 do action X?13:29
johnthetubaguyall seems the same question to me13:30
johnthetubaguyas sdague said, really just thinking about the question the API user is trying to answer (it includes policy and ability of the system)13:30
* cdent nods13:30
johnthetubaguymost of the discussion seemed to be around how to represent the actions13:31
cdentIf the question is "can X do this thing" why should I ask something else, other than X, that question?13:31
sdagueand, at least on the nova side, potentially the hypervisor type & version the instance landed on, so cant' just be flavor13:31
johnthetubaguybecause you want to know what type to pick if you want to do X?13:31
johnthetubaguyI want to do a snapshot, I can't use the ironic only cloud, and I can't use that ironic flavor over there13:32
cdentI think you mean "Y" because "X" is a thing I already have13:32
cdentthat's the two different questions:13:32
cdentwhen I use this cloud can I do activity A13:32
cdentwhen I use this entity can I do activity A13:32
cdenton the latter question, why shouldn't we ask the entity?13:32
johnthetubaguyfor me thats a scope, there are three scopes13:33
johnthetubaguywe are proposing you do ask the entity, I believe13:33
johnthetubaguywell, ish13:33
cdentthe spec proposes a new url13:33
cdentand my concern is adding yet more urls13:33
johnthetubaguyso there is an implementation detail13:33
cdentinstead of having more useful representations13:33
*** lamt has joined #openstack-meeting-413:34
johnthetubaguyto find the capabilitiy, we need to make an RPC call to the compute node, so including it by default is really expense13:34
johnthetubaguyI suspect we missed that bit13:34
cdent_that_ is an implementation detail of Nova, thus my point above about meeting in the middle between general correctness, and needing to deal with nova/cinder implementation concerns13:34
cdentobviously we have to be concerned about the cost of these things to nova etc, but we can also be aware of how they can inform different/better implementations in the future13:35
johnthetubaguyGET /volume/{volume_id}?include_capabilties=True13:36
johnthetubaguywould that be better?13:36
cdentIf the reason for have /foo/{id}/capabilities is a performance optimization, we should say so.13:36
*** klamath has joined #openstack-meeting-413:36
johnthetubaguycdent: totally agree, thats missing in the spec right now, just adding that comment13:37
*** klamath has quit IRC13:37
cdentgiven a choice between a query param and a sub resource I'd tend to go for subresource simply because it looks prettier :)13:37
johnthetubaguyfrankly I forgot about that (again) till 10 mins ago13:37
*** klamath has joined #openstack-meeting-413:37
*** mattmceuen has quit IRC13:37
johnthetubaguycdent: yeah, I am with you13:37
johnthetubaguyanyways, thanks cdent, that makes good sense to me now13:38
cdentWhen I come back around to that review, I'll try to a) make my concerns more clear b) make it clear my concerns are not blocking, more for highlighting issues etc13:38
johnthetubaguyI guess we keep pushing on that spec13:38
cdent+113:39
alex_xuso...it turn to me say... anything more?13:40
johnthetubaguyI am all good, thanks for pushing on all that over the holidays13:40
johnthetubaguygetting there now13:40
alex_xu\o/13:40
alex_xuthanks Kevin_Zheng will take care those patches13:40
Kevin_ZhengNP13:41
*** prateek has quit IRC13:41
Kevin_Zhengthanks for the review13:41
alex_xuso... we can close the meeting now13:41
alex_xuthanks all13:41
alex_xu#endmeeting13:41
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:41
* cdent wavs13:41
openstackMeeting ended Wed Jan  4 13:41:28 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:41
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_api/2017/nova_api.2017-01-04-13.00.html13:41
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_api/2017/nova_api.2017-01-04-13.00.txt13:41
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_api/2017/nova_api.2017-01-04-13.00.log.html13:41
*** cdent has left #openstack-meeting-413:41
*** wxy| has joined #openstack-meeting-413:43
*** reedip_ has joined #openstack-meeting-413:47
*** reedip_outofmemo has joined #openstack-meeting-414:06
*** woodard has joined #openstack-meeting-414:08
*** woodard has quit IRC14:09
*** woodard has joined #openstack-meeting-414:09
*** baoli has joined #openstack-meeting-414:09
*** woodard has quit IRC14:09
*** baoli has quit IRC14:09
*** woodard has joined #openstack-meeting-414:10
*** baoli has joined #openstack-meeting-414:10
*** gibi has quit IRC14:11
*** julim has joined #openstack-meeting-414:12
*** pmesserli has joined #openstack-meeting-414:15
*** pmesserl_ has joined #openstack-meeting-414:16
*** pmesserli has quit IRC14:16
*** salv-orlando has quit IRC14:17
*** cathrichardson has joined #openstack-meeting-414:17
*** salv-orlando has joined #openstack-meeting-414:17
*** hwoarang has quit IRC14:19
*** hwoarang has joined #openstack-meeting-414:20
*** karthiks has joined #openstack-meeting-414:22
*** cathrichardson has quit IRC14:22
*** BjoernT has joined #openstack-meeting-414:22
*** cathrichardson has joined #openstack-meeting-414:24
*** psachin has quit IRC14:25
*** bklei has joined #openstack-meeting-414:26
*** salv-orlando has quit IRC14:27
*** mattmceuen has joined #openstack-meeting-414:28
*** woodard has quit IRC14:34
*** cleong has joined #openstack-meeting-414:46
*** bogdando has quit IRC14:50
*** ramishra has joined #openstack-meeting-414:52
*** baoli has quit IRC14:52
*** therve has joined #openstack-meeting-414:52
*** mattmceuen has quit IRC14:55
*** rbak has joined #openstack-meeting-414:56
*** baoli has joined #openstack-meeting-414:58
*** bogdando has joined #openstack-meeting-414:58
*** ricolin has joined #openstack-meeting-414:59
*** bobh_ has joined #openstack-meeting-414:59
*** cwolferh has joined #openstack-meeting-414:59
*** links has quit IRC14:59
ramishra#startmeeting heat15:00
openstackMeeting started Wed Jan  4 15:00:12 2017 UTC and is due to finish in 60 minutes.  The chair is ramishra. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: heat)"15:00
openstackThe meeting name has been set to 'heat'15:00
*** ntpttr__ has joined #openstack-meeting-415:00
ramishra#topic roll call15:00
*** openstack changes topic to "roll call (Meeting topic: heat)"15:00
therveHeya15:00
ricolinO/15:00
ramishrahappy new year all15:00
zanebhappy new year!15:01
ricolinhappy new year!15:01
*** ntpttr__ has quit IRC15:01
*** ntpttr__ has joined #openstack-meeting-415:01
cwolferhhappy new year!15:01
*** ntpttr__ has quit IRC15:02
ramishra#topic adding items to agenda15:02
*** openstack changes topic to "adding items to agenda (Meeting topic: heat)"15:02
*** ntpttr__ has joined #openstack-meeting-415:02
ramishra#link https://wiki.openstack.org/wiki/Meetings/HeatAgenda#Agenda_.282017-01-04_1500_UTC.2915:02
ramishraI've added a few topics, anything else we would like to discuss?15:03
*** hongbin has joined #openstack-meeting-415:03
therveramishra, Adding one about heat-agents15:03
ramishratherve: yep15:04
ramishra#topic gate failures15:05
*** openstack changes topic to "gate failures (Meeting topic: heat)"15:05
ramishraSo the new year has not been good;)15:05
*** cathrichardson has left #openstack-meeting-415:05
ramishrafailure rate is very high.15:05
*** baoli has quit IRC15:05
therveWe had a barbican issue?15:05
therveThen that cfn weird stuff15:06
ramishratherve: yeah I fixed that15:06
therveAnything else identified?15:06
ramishraI noticed that we get slow nodes for the jobs.15:06
*** zhurong has quit IRC15:06
ramishra and devstack build takes 30-40 mins15:06
ramishrafrom the total 80 mins for the job.15:06
ramishraI propose this https://review.openstack.org/#/c/414365/15:07
ramishracomment in that patch has the logstash query too.15:07
*** baoli has joined #openstack-meeting-415:08
ramishraTo me it's mostly infra issue, tests with waitconditions fail mostly.15:08
*** corey_ has joined #openstack-meeting-415:09
therveThat sounds like a good workaround15:09
*** corey_ is now known as Guest4114715:09
ramishraOne more issue I noticed today, raised a bug 165399015:10
openstackbug 1653990 in heat "test_asg_scale_up_max_size fails with KeyError" [Undecided,New] https://launchpad.net/bugs/165399015:10
*** GordonTX has joined #openstack-meeting-415:10
*** klamath_ has joined #openstack-meeting-415:10
*** cleong has quit IRC15:11
*** wxy|_ has joined #openstack-meeting-415:11
ramishraweird kind of failure.15:11
therveSome kind of race with metadata maybe?15:12
*** armax_ has joined #openstack-meeting-415:12
*** tiantian has joined #openstack-meeting-415:12
*** wxy| has quit IRC15:13
*** BjoernT has quit IRC15:13
*** armax has quit IRC15:13
*** klamath has quit IRC15:13
*** armax_ is now known as armax15:13
* zaneb groans15:13
*** duonghq has joined #openstack-meeting-415:13
tiantian;)15:13
ramishratherve: it seems to me like the resource is in db but not in template.15:13
ramishranot looked in detail though.15:13
ramishraAny help to fix these is appreciated:)15:15
therveramishra, Ah probably just some transaction boundaries not handled properly15:16
*** spzala has joined #openstack-meeting-415:16
ramishratherve: yeah, possibly had never seen this before.15:17
ramishraok, lets move on15:17
ramishraelse we would only be discussing gate issues;)15:17
ramishra#topic Status of Blueprints15:17
*** openstack changes topic to "Status of Blueprints (Meeting topic: heat)"15:17
ramishra#link https://launchpad.net/heat/+milestone/ocata-315:18
ramishracan we identify the bps we plan to land in ocata? We don't have much time.15:19
ramishraNone of them seem super important to me.15:19
tiantianhttps://blueprints.launchpad.net/heat/+spec/custom-update-replace-for-failed-resources hope this can be landed in ocata15:20
tiantianacturally it's simple15:20
ramishratiantian: ok15:21
tiantianone or two patches have been merged already15:21
tiantianthank you :)15:21
ricolinI think we should define the Priority of undefined one and I feel free to land till next release if no high Priority there15:22
ramishrait seems we would not be able to do much translation stuff.15:22
ramishraNot seen any patches.15:22
ramishraok, I'll talk to the respective owners and change the target release accoridingly.15:23
ramishramoving on...15:24
ramishra#topic User survey question15:24
*** openstack changes topic to "User survey question (Meeting topic: heat)"15:24
ramishra#link http://lists.openstack.org/pipermail/openstack-dev/2017-January/109511.html15:25
therveYeah that's kind of tough15:25
ramishracan we've some good adoption questions? I've not seen many replies to my mail;)15:25
zanebwould be interesting to know if people are enabling convergence (phase 1)15:25
zanebalthough that'd *more* interesting in 6 months or a year from now15:26
zanebso I'm inclined to leave it out for now, because I can't think of anything we'd do differently at _this_ point based on the results15:27
*** ativelkov_ has quit IRC15:27
ricolinramishra: how about put throughs here https://etherpad.openstack.org/p/ocata-heat-user-survey15:27
ramishraricolin: sure15:27
ramishraactually we need one good/relevant question:)15:27
ricolin#link https://etherpad.openstack.org/p/ocata-heat-user-survey15:28
cwolferhhow often do you purge your stacks, with what parameters? :)15:28
*** Guest66666 has quit IRC15:29
ramishraHow do we decide the *one* question?15:29
*** Guest66666 has joined #openstack-meeting-415:29
ramishrasome projects are using voting/scoring system etc. We should not make it complicated;)15:30
*** mliima has joined #openstack-meeting-415:31
zanebcwolferh: how many operators would even *know* the answer to that? ;)15:31
*** baoli has quit IRC15:31
therveramishra, Some kind of rough estimate of stack size would be interesting15:32
*** ativelkov has joined #openstack-meeting-415:32
thervestack lifetime, too15:32
ramishratherve: yeah15:33
ramishraSomeone would like to help finalize the question? we've few more days to decide.15:34
*** spotz_zzz is now known as spotz_15:35
ricolinramishra: I can help:)15:35
ramishraricolin: great:)15:35
cwolferhzaneb, i'll just go with "not enough" :)15:36
ramishramoving on..15:37
ricolinLet's put some random questions list in etherpad, I will help to finalize it (probility by voting)15:38
ramishra#topic heat-agents repository15:38
*** openstack changes topic to "heat-agents repository (Meeting topic: heat)"15:38
zanebcwolferh: in an ideal world installers just do the Right Thing my default and 90% of operators never have to think about it. (I don't think we live in that world yet.)15:38
zanebs/my/by/15:38
ramishratherve: your topic:)15:38
therveYes!15:38
therveSo I started https://review.openstack.org/41624415:38
*** Sukhdev has joined #openstack-meeting-415:39
therveTo create the new repository out of heat-templates15:39
thervehttps://github.com/therve/heat-agents is the source, I used some git filter-branch invocation to get the content15:39
thervePlus one commit to fix the folder moves15:39
therveDepending on when it's created I may have to catch up some commits manually later on15:40
therveReviewing that repo can be helpful15:40
therveI hope we'll get infra feedback quickly afterwards15:40
ramishra#link http://lists.openstack.org/pipermail/openstack-dev/2016-November/107306.html15:40
ramishrathat's the ML thread on it.15:40
therveIt'd be nice if someone contacted the rdo package maintainer15:40
tiantiangood start:)15:41
therveThat's pretty much it, unless someone has questions :)15:42
*** rbak_ has joined #openstack-meeting-415:43
*** salv-orlando has joined #openstack-meeting-415:43
ramishratherve: are we going to able to keep the history after the move?15:43
*** woodard has joined #openstack-meeting-415:43
therveramishra, Yeah that's the point of that github repo15:43
ramishraok great:)15:43
zanebtherve: did I just hear you volunteer to be the rdo package maintainer?15:44
therveramishra, Actually, if you know how to improve the history that'd be great actually15:44
ramishra:)15:44
therveIt contains empty files changes currently15:44
thervezaneb, Seems like twisting my word quite heavily :)15:44
*** reedip_ has quit IRC15:45
*** woodard has quit IRC15:45
zanebtherve: is it working? ;)15:45
therveI don't think so15:46
*** woodard has joined #openstack-meeting-415:46
zanebdang15:46
ricolintherve: will `upstream: ` change after?15:46
*** rbak has quit IRC15:46
zanebtherve: I think stevebaker is the current maintainer for that15:47
thervericolin, It doesn't need to, from what I understand15:47
ramishraI think someone is already maintaining the rdo packages(python-heat-agent*) as per stevebaker in that ML thread15:47
thervericolin, It's only used for initial import if we don't set that other keyword15:47
ricolintherve: Okey, thx15:47
thervehguemar and apevec seem to make the uploads15:47
*** salv-orlando has quit IRC15:48
*** inc0 has joined #openstack-meeting-415:48
ramishratherve: anything else you want to add?15:49
therveNope15:49
ramishra#topic open discussion15:50
*** openstack changes topic to "open discussion (Meeting topic: heat)"15:50
therveShould we try to write down some PTG schedule?15:51
ramishratherve: yeah, I forgot that completely. Thanks for reminding.15:51
*** marst has joined #openstack-meeting-415:52
ramishraWould be it design session like the earlier summits or some concrete use cases that we can work on there?15:52
*** Syed__ has joined #openstack-meeting-415:53
ricolinWill be great to strong cross project discussion15:54
ramishraI think some teams are doing both.15:54
ramishraWill create an etherpad and let's capture ideas first.15:55
zanebtherve: if you run "git rebase 40e6c0874dc3877666a92c706079e7b74cc67601" on the heat-agents repo it'll delete all the merge commits15:55
* zaneb discovered that just now15:55
*** bklei has quit IRC15:55
*** caboucha has joined #openstack-meeting-415:55
therveramishra, I was thinking a bit of both? I'd like to do some real implementation if we can15:55
thervezaneb, Does that remove commits with no files?15:55
* zaneb looks15:56
thervezaneb, Looks like a winner, thanks :)15:57
zanebtherve: gonna say yes. I don't see any commits left with no files, except the first one, 40e6c0874dc3877666a92c706079e7b74cc67601, "Added .gitreview"15:57
*** egonzalez90 has joined #openstack-meeting-415:57
zanebtherve: speaking of which, we need to add a .gitreview :)15:57
thervezaneb, It's there?15:58
*** Xeregin has joined #openstack-meeting-415:58
zanebtherve: oh, you added it in the last commit. great :)15:58
zanebthere's probably a way to delete that first empty commit, but not sure what it is15:59
therveramishra, end meeting!15:59
*** lrensing has joined #openstack-meeting-415:59
ramishrayep15:59
zanebbtw +1 on "a bit of both" for the PTG15:59
thervezaneb, Thanks that look much nicer15:59
ramishrathanks all for joining16:00
*** srwilkers has joined #openstack-meeting-416:00
ramishra#endmeeting heat16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
*** TxGirlGeek has joined #openstack-meeting-416:00
openstackMeeting ended Wed Jan  4 16:00:15 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/heat/2017/heat.2017-01-04-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/heat/2017/heat.2017-01-04-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/heat/2017/heat.2017-01-04-15.00.log.html16:00
*** vhosakot has joined #openstack-meeting-416:00
*** therve has left #openstack-meeting-416:00
*** yamahata has joined #openstack-meeting-416:00
*** Marcellin__ has joined #openstack-meeting-416:01
*** jascott1 has joined #openstack-meeting-416:01
inc0#startmeeting kolla16:01
openstackMeeting started Wed Jan  4 16:01:49 2017 UTC and is due to finish in 60 minutes.  The chair is inc0. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: kolla)"16:01
openstackThe meeting name has been set to 'kolla'16:01
*** ramishra has left #openstack-meeting-416:02
inc0#topic rollcall - w00t for kolla16:02
*** openstack changes topic to "rollcall - w00t for kolla (Meeting topic: kolla)"16:02
duonghqo/16:02
srwilkerso/16:02
egonzalez90woot o/16:02
jascott1woot16:02
*** cleong has joined #openstack-meeting-416:02
qwango/16:02
mliima16:02
Jeffrey4l\0/16:02
*** portdirect has joined #openstack-meeting-416:03
*** sbezverk has joined #openstack-meeting-416:03
lrensingo/16:03
vhosakoto/16:03
pbourkew00t16:03
sbezverko/16:03
lrensingwoot16:03
portdirectw00t16:03
*** Guest41147 has quit IRC16:03
vhosakotw00t16:03
britthouser0/16:04
inc0#topic agenda16:04
*** openstack changes topic to "agenda (Meeting topic: kolla)"16:04
inc0* Roll-call16:04
inc0* Announcements16:04
inc0* Documentation16:04
inc0* Brainstorming PTG topics (we have 2 days of PTG space) timebox [30 minutes]16:04
inc0* Open Discussion16:04
sdakeo/16:04
inc0it's going to be lightweight meeting16:05
inc0:)16:05
inc0#topic Announcements16:05
Jeffrey4linc0, i added kolla-ansible dependecy ;)16:05
*** openstack changes topic to "Announcements (Meeting topic: kolla)"16:05
sdakenote I have to leave in about 20 mins :)16:05
inc0happy new year everyone!16:05
inc0any other announcements?:)16:05
inc0guess not16:06
portdirectinc0 returned from the wilderness?16:06
inc0no, arrived to one16:06
portdirectlol16:07
inc0#topic Documentation16:07
vhosakotlol16:07
*** openstack changes topic to "Documentation (Meeting topic: kolla)"16:07
inc0Sayantani is not here, she's out sick16:07
inc0so we might need to move this one once more16:07
srwilkersshe's been doing solid work trying to tidy up the docs16:07
srwilkersyeah, we should move this one more week. next week should be the last time we move it though. its something we should get to a solid place on because we have quite a few doc fixes sitting in the review queue iirc16:08
pbourkeinc0: can we be more specific on which aspect of docs we're discussing?16:08
*** wirehead_ has joined #openstack-meeting-416:08
*** corey_ has joined #openstack-meeting-416:08
inc0pbourke, person who set this up is sick:( so we need to move the topic16:08
sdakeportdirect oregon is sort of wild - much like arizona :)16:08
pbourkeinc0: roger16:09
*** corey_ is now known as Guest4830916:09
*** cleong has quit IRC16:09
*** sayantan_ has joined #openstack-meeting-416:09
srwilkershey sayantan_16:09
sayantan_Hey16:10
inc0do you feel well enough to have docs discussion?16:10
inc0sayantan_,16:10
sayantan_Yes sure16:10
*** mgiles has joined #openstack-meeting-416:10
inc0go ahead then, you're up:)16:10
sayantan_So, I wanted to discuss if we should have separate documents for the operator and developer workflow16:11
*** nkrinner is now known as nkrinner_afk16:11
portdirectwhich sub-project?16:11
portdirector kolla-*?16:11
srwilkersportdirect, for example: https://review.openstack.org/#/c/404993/16:11
sayantan_Kolla-*16:11
sayantan_yes16:12
sayantan_this would mean a lot of duplication which will get difficult to maintain.16:12
sayantan_To address the duplication, we can have different rst files for the common sections of the documents and include them in the other docs.16:12
sdakeportdirect the correct terminology is deliverable :)16:12
Jeffrey4lsayantan_, i think we need separate doc for different kolla-* project.16:12
sayantan_Do we need to separate it by OS as well16:13
sdakesayantan_ so there are three things here - kolla kolla-ansible, and kolla-kubernetes16:13
Jeffrey4l put the doc into its owner project. rather put all doc into kolla project.16:13
sayantan_as in ubuntu centos etc?16:13
sdakesayantan_ i think its best to focus on kolla-ansible documentation since its in teh worst shape16:13
sayantan_Jeffrey will do that16:13
srwilkersJeffrey4l, i think the point of discussion is operator vs dev workflow in docs, not so much where the docs are housed16:13
*** vhosakot_ has joined #openstack-meeting-416:13
Jeffrey4lsdake, inc0 srwilkers will we have operator doc?16:14
sdakeJeffrey4l i think that is what sayantan_ is working on iiuc - a document for operators16:14
Jeffrey4lsayantan_, it is better to have different OS part.16:14
sdakesayantan_ maybe I am confused on who is doing what :)16:14
*** vhosakot has quit IRC16:14
pbourkesayantan_: my vote would be to keep operator and developer docs separate16:14
Jeffrey4loops. i thought we are talking about dev doc :(16:14
srwilkersafter looking at the docs, i think it's best to streamline as much as we can. a decent amount of the workflow is similar at this point. instead of maintaining two distinct doc sets, i think we should maintain one set and make detailed notes in that workflow where the two scenarios diverge16:15
sayantan_So, my point was, in order to do the separation, there will be certain parts common in both the docs. To minimize effort of maintenance, we will need to have different rst files for the common portions of these documents16:15
srwilkersthis doesnt seem to happen all that often currently16:15
pbourkesayantan_: with an emphasis on operator16:15
sdakesrwilkers what you described is what we have today16:15
pbourkedo we even need developer docs16:15
srwilkerssdake, correct. but see the review i linked. thats the point im discussing16:15
srwilkershttps://review.openstack.org/#/c/404993/ just incase16:15
sayantan_sdake how you had suggested16:15
inc0so how about going back16:15
portdirectpbourke: yes - these ar hyper important16:15
inc0and try to remove this "operator" and "dev" workstreams?16:16
sayantan_trove has it that way Trove has it that way Please check https://github.com/openstack/trove/tree/master/install-guide/source for reference16:16
inc0I mean, it's really strange to have it16:16
pbourkethey are essentially the same thing16:16
inc0yeah, issue is versioning with pbr afair16:16
sdakesayantan_ will you be at the ptg?16:16
inc0git clone - not working, pip - working16:16
sdakesayantan_ we have made about 10 outlines of documentation in the past16:16
sdakemaybe 5-8 :)16:16
sdakebut a bunch16:16
sayantan_No, I will not be able to attend it unfortunately16:16
sdakeand they never get done16:16
pbourkeif pbr is making things difficult we should vote to drop it16:17
srwilkersproblem is, they need to get done16:17
sdakeeach time we do an outline they get better ,however, the repo split has made it difficult16:17
sdakepbourke reno and pbr are tightly integrated IIUC16:17
sdakedhellmann would be able to validate my assumption16:17
pbourkepbr is a pos16:17
sdakepbourke so dropping pbr makes release notes an impossibility - I htink but not certain16:18
portdirectlets let sayantan_ outline their vision.16:18
sdakepbourke agree pbr is a pile :)16:18
sdakeportdirect wfm :)16:18
sdakesayantan_ the reason for the pbr discussio nabove is because that is why we have the developer docs at all in kolla and kolla-ansible16:19
sayantan_So are we going for both workflows in the same doc?16:19
sdakekolla-kubernetes has dev docs for a different reason16:19
sayantan_oh16:19
sdakei think if your making new docs or improving the ones we have, for kolla and kolla-kubernetes we could drop the workflow and just handhold people through that process if they want to do devvelopment16:20
sdakerather kolla-ansible, not kolla-kubernetes16:20
portdirectyeah - the developer doc for k8s decribe setting up a non production ready reference cluster, a real cluster is out of scope for kolla-k8s16:20
sayantan_okay16:20
pbourkeeven with pbr the differences for dev are minor, they could be described in a separate doc16:20
sdakesayantan_ my suggesetion would be to not try to tackle kolla-kubernetes for the moment16:20
sayantan_sdake I plan the same16:21
sayantan_Will work on the kolla-ansible docs first16:21
sayantan_And are we deciding to divide it by OS?16:21
sayantan_ubuntu centOS etc?16:21
Jeffrey4lpbourke, pbr is not a big issue. and the root cause is how to sync the tag name between kolla and kolla-ansible, not pbr.16:21
*** ntpttr__ has quit IRC16:22
berendto/16:22
inc0sayantan_, with our playbook it's not any different really16:22
portdirectI think divion by os makes sense - as it can get really confising trying to follow a dock that covers both16:22
Jeffrey4ls/tag name/tag number16:22
inc0ubuntu vs centos16:22
pbourkesayantan_: there is a feature used in guides on docs.openstack.org where they have docs generated for centos/ubuntu from the same sources16:22
sdakeportdirect agree16:22
pbourkesayantan_: it would be great if we could use this functionality16:22
sayantan_pbrouke16:22
sdakesayantan_ ya we dont know how to do that :)16:22
sayantan_It can only be used in openstack.org docs16:22
pbourkeah16:23
pbourke:( !16:23
sayantan_I had a discussion with the docs team16:23
*** pmesserl_ has quit IRC16:23
portdirect(at least for host setup - if by the time the playbooks are run its the same then there is not point having a sperate one for that)16:23
sayantan_It can be done on a project level16:23
sayantan_check this one check https://github.com/openstack/trove/tree/master/install-guide/source16:23
sayantan_The trove guys have done it on a project level by separating the common parts in separate rst files16:24
sayantan_But this would mean a little more maintenance16:24
*** neiljerram has quit IRC16:24
srwilkersi dont see a problem with that maintenance. we should expect some associated with docs as the deliverables iterate anyway16:25
inc0so my idea would be16:25
sdakeok - gotta jet - would like to attend more, but have to go16:25
*** neiljerram has joined #openstack-meeting-416:25
sdakebye folks :)16:25
sdakei'll read the logs later16:25
sdake(tonight)16:25
inc0to get back and figure out *why* do we have 2 different installation processes16:25
inc0if it's pbr, just try to fix pbr16:25
sayantan_okay16:25
inc0and try to squeeze this to one workstream16:25
sayantan_that sounds good16:25
sdakeinc0 there is a log on the ml in [kolla] explaining why that can't be done16:25
sayantan_:)16:26
inc0that would make docs much clearer16:26
sdakeinc0 agree16:26
sdakegotta jet :)16:26
inc0k thanks sdake16:26
sayantan_Also, the openstack.org team wants to integrate kolla with the openstack.org docs16:26
*** jose-phillips has joined #openstack-meeting-416:27
inc0http://docs.openstack.org/developer/kolla/ <- any more than that?16:27
sayantan_So, if we can get this up, we can have the kolla docs in the openstack.org docs, giving us more visibility16:27
pbourkeI think that sounds great16:27
portdirectthats awesome! (as an outside i used to judge that as a lvel of a projects maturity)16:28
portdirect*outsider16:28
inc0yeah, so guys, let's quickly think about this 2 workstreams16:28
*** SamYaple has joined #openstack-meeting-416:28
pbourkeI find the guides on docs.openstack.org to be of good quality16:28
SamYapleo/16:28
sayantan_They want the doc team involved so that they can maintain it moving forward16:28
berendti think docs team want to include kolla at http://docs.openstack.org/project-deploy-guide/newton/16:28
inc0SamYaple, good that you're here, might actually help16:28
SamYaple /leave16:28
inc0why do we have two workstreams again?16:28
SamYaplei need to read scrollback16:29
inc0is this only because of pbr incorrectly tagging images if installed from git16:29
inc0?16:29
inc0SamYaple, in short, dev installation guide and ops installation guide...why?16:29
sayantan_berendt that's how they want it. You are right16:29
SamYapleinc0: i said no to that16:29
SamYaplei disagreed iwth it16:29
*** unicell has quit IRC16:29
inc0I disagree with it too, just trying to figure out why do we even consider it16:30
sayantan_Yes, this discussion stems from SamYaple 's concern16:30
inc0and only thing that comes to mind is pbr16:30
*** pmesserli has joined #openstack-meeting-416:30
SamYaplethe reasoning i got was "well merge them later" but i thought that was bad reasoning16:30
SamYaplewe never do things later!16:30
*** tonytan4ever has joined #openstack-meeting-416:30
sayantan_If it only pbr, let us fix it and have one doc16:30
sayantan_It will be better if we do not complicate it by having more docs to maintain16:31
portdirect+1, lets fix a problem rather than create new ones to work round therm16:31
sayantan_Will take up the pbr issue and fix it16:31
Jeffrey4lif it is caused by pbr, a note is enough. no need add a extra doc file.16:31
SamYapleduplicate docs*16:31
SamYaplemore docs are fine16:32
sayantan_yes16:32
inc0I think this is ML thread sdake mentioned http://lists.openstack.org/pipermail/openstack-dev/2016-September/103619.html16:32
inc0and yeah, seems to be pbr issue16:33
inc0let's fix our versioning and be done with it16:33
inc0also another thing about docs16:33
inc0I'd really encourage people to use bootstrap-servers more16:33
SamYapleidk about that16:34
sayantan_I agree. It is much easier. Have added that in the new patch set I have been working on16:34
inc0well it boils down installation of kolla to16:34
*** mattmceuen has joined #openstack-meeting-416:34
egonzalez90+116:34
inc0pip install kolla-ansible kolla ansible16:34
inc0configure globals.yml and build.conf16:35
inc0kolla build -> kolla-ansible bootstrap-servers -> kolla-ansible deploy16:35
pbourkethats the dream16:35
SamYaplesure. should be ok for the docs. i just dont want the option bootstrap-servers role to become a requirement. otherwise kolla-ansible goes in a really different "touch host" direction16:36
inc0SamYaple, requirement no16:36
inc0it stays the same as now16:36
berendtSamYaple:16:36
SamYaplefair enough16:36
berendt+116:36
inc0just to put more focus on it in docs16:36
sayantan_+116:36
inc0as it's really convenient16:36
pbourkeif we can maintain stable images on dockerhub the build step goes away too16:36
inc0thats the dream16:37
pbourkeha16:37
inc0ok I think we can move on16:37
portdirectinc0: can we talk about that (docker hub images in a bit)16:37
inc0sayantan_, I'll talk to you later today about what exactly pbr issue was16:37
*** jchhatbar_ has quit IRC16:37
inc0portdirect, we should ahve some time in open discussion16:38
inc0or next meeting16:38
inc0this is important16:38
sayantan_sounds good :16:38
inc0ok next topic is about PTG but sdake added it and went out and I really wanted to discuss ptg closer to actual ptg;)16:38
inc0so16:38
inc0#topic kolla-ansible dependency. ansible version? and third party packages.16:38
*** openstack changes topic to "kolla-ansible dependency. ansible version? and third party packages. (Meeting topic: kolla)"16:38
inc0Jeffrey4l, floor is yours16:38
berendtgood news, i got accepted for the travel support program for the ptg16:38
Jeffrey4lthanks.16:39
inc0yay Christian!16:39
Jeffrey4ltwo issue:16:39
Jeffrey4lshould be bump ansible y stream now?16:39
Jeffrey4lbecause ansible 2.2 has a big change then ansible 2.016:39
inc0hmm, how big for us? can we reasonably tackle it in Ocata?16:40
Jeffrey4lfor example ansible 2.2 will raise some warning and ansible 2.0 not.16:40
pbourkewhere do you propose bumping this16:40
inc0well if it's non-breaking warning, I'd say we can bump and post bug16:41
Jeffrey4lthe reason is ansible 2.2 and ansible 2.0 is  not compatible in some way.16:41
Jeffrey4lwe got lots of warning when using ansible 2.216:42
duonghqwe have some bug report about this issue16:42
duonghqthe warning will become error around 2.416:42
Jeffrey4land can not use some new feature ( like block ) in ansible 2.216:42
Jeffrey4lthat's the issue. it is not big, but we need handle.16:42
Jeffrey4lduonghq, yep.16:42
*** amirv has joined #openstack-meeting-416:42
inc0so that's what I'd do: bump today, post bugs for any error16:43
inc0(warning that is)16:43
egonzalez90if we move to ansible 2.2 we cannot use prior versions16:43
inc0ofc make sure everything works even with warnings16:43
Jeffrey4legonzalez90, yep.16:43
egonzalez90some module options in ansible2.2 does not work16:43
Jeffrey4lnow kolla-ansible require ansible > 2.16:43
kfox1111o/16:43
Jeffrey4legonzalez90, details?16:43
*** sdake has quit IRC16:44
*** dtardivel has quit IRC16:44
Jeffrey4lanother question is: whether and how to determine the requirments.txt in kolla-ansible.  this is raised by https://review.openstack.org/41210116:45
Jeffrey4lthis patch ^^16:45
egonzalez90#link https://review.openstack.org/#/c/402691/16:45
Jeffrey4li added oslo.config into kolla-ansible requirements.txt.16:45
egonzalez90this module does not work with ansible 2.1, they just removed it withour warning16:45
Jeffrey4l( even though oslo.config is already in req.txt file, not it is historical issue )16:45
Jeffrey4lshould we or can we add more requirements ( especially python packages ) in kolla-ansible projects?16:46
Jeffrey4lSamYaple, need your opinion ;)16:46
inc0Jeffrey4l, can - sure16:46
inc0should - well, if we need them, then yes;)16:47
Jeffrey4legonzalez90, yep that options will be removed in ansible 2.4 ( iirc )16:47
SamYaplei just want to make people aware that modules are different than action_plugins16:47
*** revon has joined #openstack-meeting-416:47
SamYapleaction_plugin runs on deploy host (we can probably reasonably require requirements.txt)16:48
SamYaplemodules run on the target host16:48
SamYapleoslo.config can't be a import on a target host16:48
SamYaplethats not the case here, but i dont want confusion down the road16:48
Jeffrey4lSamYaple, merge_config run in deployment node. not target node.16:48
SamYapleJeffrey4l: i know. but everyone else should be aware of that too16:48
inc0Jeffrey4l, right16:48
SamYaplethis isnt open the flood gates and allow external libs in modules16:49
inc0so if somethign is required on deploy node - goes to req.txt16:49
SamYaplethis is 'require thigns on deploy host'16:49
Jeffrey4lSamYaple, yep. if we add some requirement which run on target host, we should re-consider that and better not to that.16:49
inc0if something is required on target node - goes to docs and bootstap servers16:49
SamYapleinc0: nope16:49
SamYapledisagree16:49
SamYaplethat makes bootstrap servers required16:49
Jeffrey4linc0, kolla do not touch host.16:49
SamYapleand it adds packages to the host, something we dont do16:49
inc0docs and bootstrap servers16:49
SamYaplenope16:49
inc0that's what we do now16:50
SamYaplethats a fundemental shift in philosphy16:50
Jeffrey4lso if you add some requirement in target host, better use kolla_toolbox ;)16:50
inc0you can always do it manually16:50
SamYaplei dont think you understand16:50
inc0SamYaple, it was shifted when you were away16:50
SamYapleit was not...16:50
inc0deploy play does not touch host16:50
SamYaplenot this16:50
inc0bootstap-servers mangles it as it will16:50
SamYaplebootstrap servers is optional16:51
SamYaplewe just discussed this inc016:51
inc0sure16:51
inc0we add it to DOCS too16:51
SamYaplethe only requirements on the host were docker and docker-py16:51
inc0so people can install package manually on target node16:51
inc0yeah16:51
inc0what I'm saying is16:51
inc0if we EVER have more reqs on target hosts16:51
SamYapleanythign past docker and docker-py certianly hasnt been discussed inc016:51
inc0that's how we handle it16:51
SamYaplethere was no shift16:51
inc0point being, it's much more heavyweight than having deploy node req16:51
inc0so let's stick to deploy node req as much as possible16:52
SamYapleperiod16:52
SamYapleunless the discussion is opened up16:52
SamYaplenot as much as possible16:52
inc0no, it's not16:52
inc0anyway, nothing changes now16:52
SamYapleyoure making decsions here that no one has agreed to inc016:52
inc0I'm not making any decisions!16:53
inc0anyway16:53
inc0let's go back to topic16:53
Jeffrey4lyep.16:53
inc0Jeffrey4l, anything left to say?16:53
SamYaplepoint being, this code runs on deploy host where we can reasonable require oslo_config16:53
Jeffrey4lif we need add some other patch in deploy host, re-consider use kolla_toolbox.16:53
pbourkeJeffrey4l: +116:53
SamYapleagreed Jeffrey4l16:53
inc0yup16:54
SamYaplethats what its there for16:54
Jeffrey4lif it really can not work, it is acceptable and worth to talk to add requirements in target node.16:54
Jeffrey4lthat what i want to say. ;)16:54
inc0no argument here16:54
SamYaplea discussion would be needed to change direction, agreed16:54
Jeffrey4lok. please move on16:54
inc0#topic open discussion16:55
*** openstack changes topic to "open discussion (Meeting topic: kolla)"16:55
SamYapleneed to talk about the statid uid/gid for a moment16:55
inc0portdirect, registry?16:55
portdirectcan we push images to the hub a little bit more often?16:55
inc0SamYaple, portdirect was first:)16:55
inc0well, we don't have master build images at all16:55
inc0today we push every stable release16:55
portdirectas we (kolla-k8s) are needing to work round bugs in release images: https://review.openstack.org/#/c/416366/16:55
Jeffrey4lwe should not push master tag. it is easily to break.16:56
portdirectthis is not master - but 3.0.2 i think16:56
inc0we technically can create new tag, like develop16:56
inc0and push as needed16:56
kfox11113.0.2 or at least a freshened 3.0.116:56
Jeffrey4lwe have this now http://tarballs.openstack.org/kolla/images/16:56
Jeffrey4lmaster registry images.16:56
kfox1111really its only one set of packages, kolla-toolbox that has a stale package.16:57
Jeffrey4lit is still WIP. but almost done. and it just works.16:57
berendtJeffrey4l: cool16:57
sbezverkinc0: would be great to have a separate tag for master16:57
inc0that for gates16:57
Jeffrey4l3.0.2 will be release soon. ;)16:57
inc0yeah, once 3.0.2 tags, we'll build and push it16:57
sbezverkin this case we can experiment with close to master state images16:57
inc0we were discussing nightly builds and pushes too16:58
kfox1111Jeffrey4l: whats "soon"? :)16:58
Jeffrey4linc0, i am thinking to push tag registry tarball during release.16:58
inc0if someone would like to donate server we can crack up cronjob for it;)16:58
kfox1111like, before next wednesday?16:58
Jeffrey4lkfox1111, 3.0.2 will be release soon.16:58
Jeffrey4l( time ... )16:58
portdirectinc0: I can do that for this dev cycle16:58
kfox1111like, can we get rid of the workaround before we cut the kolla-kubernetes release?16:58
inc0kfox1111, Jeffrey4l I think we can say this week right?16:59
Jeffrey4lbtw, when kolla-k8s will be release next tag ( 0.4 )16:59
inc0for 3.0.216:59
Jeffrey4linc0, yep16:59
kfox1111ok. cool. then we'll just wait for the end of the week, then pull the workaround out.16:59
Jeffrey4lthe scheduler date we talked last is Jan 4 kfox111116:59
kfox1111Jeffrey4l: slipped one week.16:59
Jeffrey4lroger.16:59
*** sayantan_ has quit IRC17:00
berendttimeout...17:00
*** sayantan_ has joined #openstack-meeting-417:00
inc0yes, thank you all17:00
inc0#endmeeting kolla17:00
*** sayantan_ has left #openstack-meeting-417:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Wed Jan  4 17:00:43 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-01-04-16.01.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-01-04-16.01.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-01-04-16.01.log.html17:00
*** mgiles has left #openstack-meeting-417:01
*** jascott1 has left #openstack-meeting-417:01
*** inc0 has quit IRC17:01
*** duonghq has quit IRC17:02
*** egonzalez90 has left #openstack-meeting-417:02
*** salv-orlando has joined #openstack-meeting-417:04
*** chyka has joined #openstack-meeting-417:04
*** ricolin has quit IRC17:08
*** sdake has joined #openstack-meeting-417:08
*** mliima has left #openstack-meeting-417:09
*** vhosakot_ has quit IRC17:09
*** sdake has quit IRC17:13
*** amirv has quit IRC17:14
*** wxy|_ has quit IRC17:14
*** matrohon has quit IRC17:31
*** reedip_outofmemo has quit IRC17:33
*** Swami has joined #openstack-meeting-417:39
*** sdague has quit IRC17:39
*** Guest48309 has quit IRC17:40
*** cleong has joined #openstack-meeting-417:40
*** ntpttr__ has joined #openstack-meeting-417:42
*** baoli has joined #openstack-meeting-417:45
*** yamahata has quit IRC17:54
*** portdirect has left #openstack-meeting-417:59
*** aleph1 is now known as agarner17:59
*** Sukhdev has quit IRC18:01
*** Sukhdev has joined #openstack-meeting-418:02
*** bobmel has joined #openstack-meeting-418:04
*** tonytan4ever has quit IRC18:07
*** tonytan4ever has joined #openstack-meeting-418:07
*** iyamahat has joined #openstack-meeting-418:11
*** tonytan4ever has quit IRC18:14
*** wirehead_ has left #openstack-meeting-418:14
*** tonytan4ever has joined #openstack-meeting-418:15
*** dharinic is now known as dharinic|lunch18:16
*** chyka has quit IRC18:18
*** ntpttr__ has quit IRC18:18
*** iyamahat has quit IRC18:21
*** GordonTX has quit IRC18:23
*** iyamahat has joined #openstack-meeting-418:26
*** yamahata has joined #openstack-meeting-418:32
*** sdake has joined #openstack-meeting-418:36
*** yfauser has quit IRC18:38
*** yfauser has joined #openstack-meeting-418:38
*** unicell has joined #openstack-meeting-418:38
*** spzala has quit IRC18:40
*** spzala has joined #openstack-meeting-418:41
*** spzala has quit IRC18:44
*** spzala has joined #openstack-meeting-418:44
*** yamahata has quit IRC18:46
*** yamahata has joined #openstack-meeting-418:47
*** galstrom_zzz is now known as galstrom18:48
*** pcaruana has quit IRC18:52
*** s3wong has joined #openstack-meeting-418:52
*** sdague has joined #openstack-meeting-418:52
*** sdake has quit IRC18:54
*** vishnoianil has quit IRC18:55
*** anilvenkata has quit IRC18:59
*** spzala has quit IRC19:01
*** sambetts is now known as sambetts|afk19:05
*** admcleod has joined #openstack-meeting-419:06
*** admcleod has quit IRC19:06
*** admcleod has joined #openstack-meeting-419:06
*** admcleod_ has quit IRC19:07
*** sdake has joined #openstack-meeting-419:15
*** sdake has quit IRC19:16
*** Xeregin has left #openstack-meeting-419:17
*** dharinic|lunch is now known as dharinic19:18
*** matrohon has joined #openstack-meeting-419:24
*** spotz_ is now known as spotz_zzz19:25
*** fitoduarte has joined #openstack-meeting-419:27
*** sdake has joined #openstack-meeting-419:29
*** fitoduarte has quit IRC19:30
*** galstrom is now known as galstrom_zzz19:32
*** spzala has joined #openstack-meeting-419:32
*** galstrom_zzz is now known as galstrom19:32
*** galstrom is now known as galstrom_zzz19:33
*** spzala_ has joined #openstack-meeting-419:35
*** bnemec has quit IRC19:35
*** ttx has quit IRC19:36
*** sshnaidm has quit IRC19:36
*** kevinbenton has quit IRC19:36
*** raginbajin has quit IRC19:36
*** jschwarz has quit IRC19:36
*** mfranc213 has quit IRC19:36
*** ngraf has quit IRC19:36
*** hughsaunders has quit IRC19:36
*** pshedimb has quit IRC19:36
*** raj_singh has quit IRC19:36
*** d34dh0r53 has quit IRC19:36
*** dharinic has quit IRC19:36
*** sneti has quit IRC19:36
*** pshige_________ has quit IRC19:36
*** eglute has quit IRC19:36
*** bnemec has joined #openstack-meeting-419:36
*** eglute has joined #openstack-meeting-419:36
*** jschwarz has joined #openstack-meeting-419:36
*** mfranc213 has joined #openstack-meeting-419:36
*** d34dh0r53 has joined #openstack-meeting-419:36
*** spzala has quit IRC19:36
*** pshige_________ has joined #openstack-meeting-419:36
*** hughsaunders has joined #openstack-meeting-419:36
*** yfauser has quit IRC19:36
*** ttx has joined #openstack-meeting-419:36
*** nategraf has joined #openstack-meeting-419:37
*** kevinbenton has joined #openstack-meeting-419:37
*** yfauser has joined #openstack-meeting-419:37
*** sshnaidm has joined #openstack-meeting-419:37
*** fitoduarte has joined #openstack-meeting-419:38
*** raginbajin has joined #openstack-meeting-419:38
*** galstrom_zzz is now known as galstrom19:39
*** pshedimb has joined #openstack-meeting-419:41
*** yfauser has quit IRC19:41
*** dharinic has joined #openstack-meeting-419:41
*** raj_singh has joined #openstack-meeting-419:44
*** vishnoianil has joined #openstack-meeting-419:49
*** corey_ has joined #openstack-meeting-419:50
*** corey_ is now known as Guest374519:51
*** SerenaFeng has joined #openstack-meeting-419:52
*** cleong has quit IRC19:53
*** rfolco has quit IRC19:53
*** spotz_zzz is now known as spotz_19:56
*** mattmceuen has quit IRC20:02
*** yfauser has joined #openstack-meeting-420:07
*** beagles is now known as beagles_biab20:08
*** salv-orlando has quit IRC20:08
*** Sukhdev has quit IRC20:11
*** yfauser has quit IRC20:12
*** liangy has joined #openstack-meeting-420:12
*** yfauser has joined #openstack-meeting-420:12
*** yfauser has quit IRC20:16
*** SerenaFeng has quit IRC20:16
*** revon has quit IRC20:23
*** rtheis has quit IRC20:28
*** icey has quit IRC20:28
*** icey has joined #openstack-meeting-420:31
*** icey has quit IRC20:31
*** icey has joined #openstack-meeting-420:31
*** spotz_ is now known as spotz_zzz20:32
*** Guest3745 is now known as cleong20:33
*** spotz_zzz is now known as spotz_20:33
*** caboucha has quit IRC20:34
*** tonytan4ever has quit IRC20:35
*** tonytan4ever has joined #openstack-meeting-420:36
*** d0ugal has quit IRC20:39
*** lamt has quit IRC20:39
*** sdake has quit IRC20:40
*** spzala_ has quit IRC20:42
*** d0ugal has joined #openstack-meeting-420:55
*** rtheis has joined #openstack-meeting-421:04
*** rtheis has quit IRC21:04
*** spzala has joined #openstack-meeting-421:06
*** yfauser has joined #openstack-meeting-421:10
*** cleong has quit IRC21:12
*** srwilkers has quit IRC21:14
*** yfauser has quit IRC21:14
*** galstrom is now known as galstrom_zzz21:18
*** spzala has quit IRC21:19
*** julim has quit IRC21:20
*** salv-orlando has joined #openstack-meeting-421:23
*** sdake has joined #openstack-meeting-421:28
*** l4yerffeJ_ has joined #openstack-meeting-421:32
*** Jeffrey4l has quit IRC21:35
*** l4yerffeJ has quit IRC21:35
*** lrensing has quit IRC21:36
*** Jeffrey4l has joined #openstack-meeting-421:49
*** lamt has joined #openstack-meeting-421:50
*** salv-orl_ has joined #openstack-meeting-421:54
*** TxGirlGeek has quit IRC21:55
*** TxGirlGeek has joined #openstack-meeting-421:55
*** spotz_ is now known as spotz__21:56
*** spotz__ is now known as spotz_21:56
*** salv-orlando has quit IRC21:56
*** thorst has quit IRC21:58
*** matrohon has quit IRC21:58
*** thorst has joined #openstack-meeting-422:00
*** TxGirlGeek has quit IRC22:01
*** TxGirlGeek has joined #openstack-meeting-422:01
*** iyamahat has quit IRC22:03
*** iyamahat has joined #openstack-meeting-422:03
*** TxGirlGeek has quit IRC22:03
*** TxGirlGeek has joined #openstack-meeting-422:04
*** thorst has quit IRC22:05
*** TxGirlGeek has quit IRC22:06
*** TxGirlGeek has joined #openstack-meeting-422:06
*** woodard_ has joined #openstack-meeting-422:08
*** TxGirlGeek has quit IRC22:09
*** TxGirlGeek has joined #openstack-meeting-422:09
*** yfauser has joined #openstack-meeting-422:11
*** TxGirlGeek has quit IRC22:11
*** TxGirlGeek has joined #openstack-meeting-422:11
*** woodard has quit IRC22:11
*** woodard_ has quit IRC22:12
*** yfauser has quit IRC22:15
*** TxGirlGeek has quit IRC22:16
*** TxGirlGeek has joined #openstack-meeting-422:16
*** thorst has joined #openstack-meeting-422:18
*** thorst has quit IRC22:21
*** thorst has joined #openstack-meeting-422:22
*** TxGirlGeek has quit IRC22:23
*** dave-mccowan has quit IRC22:28
*** baoli has quit IRC22:29
*** TxGirlGeek has joined #openstack-meeting-422:30
*** baoli has joined #openstack-meeting-422:30
*** baoli has quit IRC22:33
*** baoli has joined #openstack-meeting-422:36
*** rbak_ has quit IRC22:38
*** thorst has quit IRC22:39
*** dave-mccowan has joined #openstack-meeting-422:40
*** baoli has quit IRC22:40
*** usman has quit IRC22:41
*** bobh_ has quit IRC22:45
*** tonytan4ever has quit IRC22:50
*** clarkb has joined #openstack-meeting-422:52
*** openstack has joined #openstack-meeting-422:55
*** ChanServ sets mode: +o openstack22:55
*** TxGirlGeek has quit IRC22:59
*** amotoki has quit IRC23:00
*** dave-mccowan has quit IRC23:00
*** amotoki has joined #openstack-meeting-423:02
*** armax has quit IRC23:04
*** armax has joined #openstack-meeting-423:05
*** armax has quit IRC23:06
*** sdake has quit IRC23:09
*** yfauser has joined #openstack-meeting-423:12
*** yfauser has quit IRC23:16
*** spzala has joined #openstack-meeting-423:17
*** lihi has quit IRC23:18
*** yamahata has quit IRC23:19
*** lihi has joined #openstack-meeting-423:20
*** salv-orl_ has quit IRC23:20
*** cdelatte has quit IRC23:23
*** sdake has joined #openstack-meeting-423:24
*** sdake has quit IRC23:26
*** yamahata has joined #openstack-meeting-423:26
*** amotoki has quit IRC23:26
*** gongysh has joined #openstack-meeting-423:28
*** sdake has joined #openstack-meeting-423:29
*** spotz_ is now known as spotz_zzz23:30
*** portdirect_ has joined #openstack-meeting-423:31
*** amotoki has joined #openstack-meeting-423:31
*** yfauser has joined #openstack-meeting-423:32
*** iyamahat_ has joined #openstack-meeting-423:34
*** iyamahat has quit IRC23:34
*** klamath_ has quit IRC23:34
*** thorst_ has joined #openstack-meeting-423:35
*** yfauser has quit IRC23:37
*** spzala has quit IRC23:42
*** yfauser has joined #openstack-meeting-423:42
*** spzala has joined #openstack-meeting-423:45
*** yfauser has quit IRC23:47
*** portdirect_ has quit IRC23:47
*** lamt has quit IRC23:48
*** iyamahat has joined #openstack-meeting-423:57
*** iyamahat_ has quit IRC23:57

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