Wednesday, 2016-09-28

*** padkrish has quit IRC00:02
*** thorst has joined #openstack-meeting-400:03
*** spzala_ has quit IRC00:04
*** padkrish has joined #openstack-meeting-400:04
*** thorst has quit IRC00:05
*** zhurong has quit IRC00:06
*** padkrish has quit IRC00:09
*** davidlenwell has quit IRC00:11
*** ddieterly has quit IRC00:13
*** trozet has quit IRC00:19
*** markvoelker has joined #openstack-meeting-400:20
*** markvoelker has quit IRC00:25
*** davidlenwell has joined #openstack-meeting-400:25
*** banix has quit IRC00:26
*** banix has joined #openstack-meeting-400:27
*** markvoelker has joined #openstack-meeting-400:34
*** caowei has joined #openstack-meeting-400:40
*** limao has joined #openstack-meeting-400:42
*** sgordon has quit IRC00:42
*** sgordon has joined #openstack-meeting-400:43
*** haleyb has quit IRC00:43
*** haleyb has joined #openstack-meeting-400:43
*** ddieterly has joined #openstack-meeting-400:46
*** salv-orlando has joined #openstack-meeting-400:48
*** salv-orlando has quit IRC00:52
*** vishnoianil has quit IRC00:56
*** padkrish has joined #openstack-meeting-401:00
*** ddieterly has quit IRC01:01
*** padkrish has quit IRC01:04
*** padkrish has joined #openstack-meeting-401:04
*** padkrish_ has joined #openstack-meeting-401:06
*** padkrish has quit IRC01:09
*** gongysh has joined #openstack-meeting-401:14
*** zhurong has joined #openstack-meeting-401:18
*** pkoniszewski has quit IRC01:25
*** pkoniszewski has joined #openstack-meeting-401:31
*** thorst has joined #openstack-meeting-401:32
*** thorst has quit IRC01:32
*** yulong|away has joined #openstack-meeting-401:38
*** yulong|away is now known as liuyulong01:38
*** yifei has joined #openstack-meeting-401:44
*** tonytan4ever has joined #openstack-meeting-401:46
*** yifei1 has joined #openstack-meeting-401:47
*** hieulq has joined #openstack-meeting-401:47
*** yifei has quit IRC01:48
*** yifei1 is now known as yifei01:48
*** ddieterly has joined #openstack-meeting-401:49
*** haleyb_ has joined #openstack-meeting-401:49
*** tonytan4ever has quit IRC01:50
*** ddieterly has quit IRC01:52
*** s3wong has quit IRC01:54
*** haleyb_ has quit IRC01:55
*** padkrish_ has quit IRC01:55
*** padkrish has joined #openstack-meeting-401:56
*** Jeffrey4l has joined #openstack-meeting-401:58
*** padkrish has quit IRC02:01
*** baoli has quit IRC02:05
*** haleyb_ has joined #openstack-meeting-402:06
*** banix has quit IRC02:07
*** unicell has quit IRC02:08
*** baoli has joined #openstack-meeting-402:11
*** padkrish has joined #openstack-meeting-402:20
*** ddieterly has joined #openstack-meeting-402:21
*** ddieterly has quit IRC02:25
*** bobh_ has joined #openstack-meeting-402:35
*** salv-orlando has joined #openstack-meeting-402:36
*** salv-orlando has quit IRC02:40
*** bobh_ has quit IRC02:52
*** baoli has quit IRC02:52
*** xuao has joined #openstack-meeting-402:52
*** padkrish has quit IRC02:56
*** padkrish has joined #openstack-meeting-402:56
*** Sukhdev has joined #openstack-meeting-402:59
*** Sukhdev has quit IRC03:01
*** david-lyle has quit IRC03:04
*** spzala has joined #openstack-meeting-403:05
*** spzala has quit IRC03:05
*** dcwangmit01_ has joined #openstack-meeting-403:16
*** sdake_ has quit IRC03:17
*** armax has quit IRC03:18
*** dcwangmit01 has quit IRC03:19
*** unicell has joined #openstack-meeting-403:21
*** sdake has joined #openstack-meeting-403:39
*** padkrish has quit IRC03:46
*** haleyb_ has quit IRC03:48
*** bobh_ has joined #openstack-meeting-403:48
*** hemanthm|afk is now known as hemanthm03:50
*** sdake_ has joined #openstack-meeting-403:50
*** Sukhdev has joined #openstack-meeting-403:50
*** sdake has quit IRC03:51
*** padkrish has joined #openstack-meeting-403:53
*** gongysh has quit IRC03:58
*** bobh_ has quit IRC03:59
*** njohnston__ is now known as njohnston04:01
*** janonymous has joined #openstack-meeting-404:05
*** yamamoto_ has quit IRC04:17
*** amotoki has joined #openstack-meeting-404:28
*** JRobinson__ is now known as JRobinson__afk04:31
*** Rocky_g has quit IRC04:36
*** prateek_ has joined #openstack-meeting-404:38
*** psachin has joined #openstack-meeting-404:41
*** unicell has quit IRC04:41
*** unicell has joined #openstack-meeting-404:42
*** unicell1 has joined #openstack-meeting-404:48
*** gongysh has joined #openstack-meeting-404:49
*** unicell has quit IRC04:51
*** JRobinson__afk is now known as JRobinson__04:55
*** unicell1 has quit IRC04:55
*** unicell has joined #openstack-meeting-404:56
*** yamamoto has joined #openstack-meeting-404:59
*** syed_ has joined #openstack-meeting-405:05
*** Sukhdev has quit IRC05:08
*** links has joined #openstack-meeting-405:08
*** janki has joined #openstack-meeting-405:14
*** links has quit IRC05:15
*** links has joined #openstack-meeting-405:17
*** salv-orlando has joined #openstack-meeting-405:18
*** sshnaidm|afk is now known as sshnaidm05:21
*** anilvenkata has joined #openstack-meeting-405:21
*** salv-orlando has quit IRC05:22
*** woodster_ has quit IRC05:30
*** sdake_ has quit IRC05:30
*** unicell has quit IRC05:32
*** unicell1 has joined #openstack-meeting-405:32
*** dshakhray_ has joined #openstack-meeting-405:41
*** anilvenkata is now known as anilvenkata_afk05:47
*** iyamahat has joined #openstack-meeting-405:52
*** iyamahat has quit IRC05:55
*** unicell has joined #openstack-meeting-405:58
*** unicell1 has quit IRC05:59
*** iyamahat has joined #openstack-meeting-406:01
*** trozet has joined #openstack-meeting-406:07
*** nkrinner_afk is now known as nkrinner06:20
*** trozet has quit IRC06:24
*** crinkle_ is now known as crinkle06:33
*** mrunge has quit IRC06:36
*** pcaruana has joined #openstack-meeting-406:37
*** mrunge has joined #openstack-meeting-406:42
*** padkrish has quit IRC06:50
*** salv-orlando has joined #openstack-meeting-406:50
*** padkrish has joined #openstack-meeting-406:52
*** ralonsoh has joined #openstack-meeting-407:04
*** ralonsoh_ has joined #openstack-meeting-407:04
*** ralonsoh has quit IRC07:04
*** ralonsoh_ has quit IRC07:04
*** ralonsoh has joined #openstack-meeting-407:04
*** ralonsoh_ has joined #openstack-meeting-407:04
*** ralonsoh has quit IRC07:04
*** ralonsoh_ has quit IRC07:04
*** ralonsoh has joined #openstack-meeting-407:05
*** JRobinson__ has quit IRC07:09
*** matrohon has joined #openstack-meeting-407:10
*** reedip has quit IRC07:11
*** syed_ has quit IRC07:14
*** links has quit IRC07:16
*** cartik has joined #openstack-meeting-407:17
*** iyamahat has quit IRC07:18
*** LotharKAtt has joined #openstack-meeting-407:24
*** reedip has joined #openstack-meeting-407:25
*** spotz is now known as spotz_zzz07:25
*** iyamahat has joined #openstack-meeting-407:29
*** ifat_afek has joined #openstack-meeting-407:30
*** barmaley has joined #openstack-meeting-407:36
*** iyamahat has quit IRC07:40
*** ifat_afek has quit IRC07:41
*** salv-orl_ has joined #openstack-meeting-407:43
*** links has joined #openstack-meeting-407:45
*** janki has quit IRC07:45
*** salv-orlando has quit IRC07:46
*** janonymous has quit IRC07:48
*** sshnaidm has quit IRC07:51
*** janki has joined #openstack-meeting-407:52
*** zenoway has joined #openstack-meeting-407:52
*** padkrish has quit IRC07:52
*** padkrish has joined #openstack-meeting-407:52
*** padkrish has quit IRC07:59
*** ifat_afek has joined #openstack-meeting-408:01
*** bogdando has joined #openstack-meeting-408:01
ifat_afek#startmeeting vitrage08:01
openstackMeeting started Wed Sep 28 08:01:11 2016 UTC and is due to finish in 60 minutes.  The chair is ifat_afek. Information about MeetBot at http://wiki.debian.org/MeetBot.08:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:01
*** openstack changes topic to " (Meeting topic: vitrage)"08:01
ifat_afekhi everyone!08:01
openstackThe meeting name has been set to 'vitrage'08:01
*** idan_hefetz has joined #openstack-meeting-408:02
idan_hefetzHi all!08:02
*** eyalb has joined #openstack-meeting-408:02
*** sc68cal_ has joined #openstack-meeting-408:02
eyalbhi08:02
*** sc68cal has quit IRC08:03
ifat_afekHi everyone :-)08:05
ifat_afek#topic Status and Updates08:06
*** openstack changes topic to "Status and Updates (Meeting topic: vitrage)"08:06
ifat_afekNewton release - vitrage Newton versions are marked:08:06
ifat_afekvitrage 1.3.008:06
ifat_afekpython-vitrageclient 1.0.108:06
ifat_afekvitrage-dashboard 1.0.208:06
ifat_afekWe now have stable/newton branch for all vitrage repositories, and master can be used for Ocata development.08:06
*** elisha_r has joined #openstack-meeting-408:07
ifat_afekThe final release is scheduled for October 6.08:07
elisha_rhi08:07
ifat_afekI’m working on the documentation. I want to make sure that the developer guide, blueprints, api reference – are all up to date and copied to openstack official sites.08:07
*** danoffek has joined #openstack-meeting-408:07
ifat_afekWho wants to update?08:07
danoffekhi guys08:07
eyalbI will08:07
eyalbI am working on installing a devstack with vitrage that will get its data from a remote openstack cluster08:08
eyalbwe will use the devstack keystone for vitrage and for the datasources we will communicate with the remote keystone08:09
eyalbthats all08:09
ifat_afekeyalb: cool. sounds like an interesting use case08:09
danoffekI'll update on the templates list on Horizon08:09
danoffekI started working on the UI .08:10
*** alexey_weyl has joined #openstack-meeting-408:10
danoffekI'll also add a blueprint for it08:10
danoffekIt's a simple template list on phase one, without the option to update templates via UI .08:11
danoffekThat's it08:11
ifat_afekdanoffek: that’s great. will you also show the template file?08:11
danoffekI'll display anything available via the standard vitrage teplates list API.08:12
ifat_afekcool08:12
alexey_weylI have an update08:13
alexey_weylI have worked on the multi tenancy blueprint08:13
alexey_weylit is working, and I have only some final touches to make, and then I will push into github08:14
alexey_weylthats it08:14
ifat_afekalexey_weyl: thanks08:14
ifat_afekany other updates?08:14
ifat_afekmoving on08:16
ifat_afek#topic Preparations for Barcelona08:16
*** alexey_weyl has quit IRC08:16
*** openstack changes topic to "Preparations for Barcelona (Meeting topic: vitrage)"08:16
ifat_afekGood news: vitrage hands-on lab was accepted!08:17
ifat_afekIt was an “alternate session”, so I guess some other session was canceled. We should start planning it.08:17
danoffekOnly a few weeks to prepare. Still, we'll be ready.08:18
ifat_afekdanoffek: of course :-)08:18
ifat_afekThis is the up to date schedule for the design sessions:08:18
ifat_afek#link https://docs.google.com/spreadsheets/d/1TQ-RSlbiBBEclkonIbfUP7R1ExZSJylF1uiEKV2G_Cw/pubhtml?gid=1107826458&single=true08:18
ifat_afekWe will have three design sessions on Wednesday:08:18
ifat_afek15:05-15:45: workroom08:19
ifat_afek15:55-16:35: fishbowl08:19
ifat_afek17:55-18:35: workroom08:19
ifat_afekI saw that some of you wrote your ideas in the etherpad. Feel free to add some more:08:19
ifat_afek#link https://etherpad.openstack.org/p/vitrage-barcelona-design-sessions08:19
ifat_afekother than that, elisha_r and myself submitted two “brown bag” talk proposals. These are 10-minutes talks in smaller rooms than the regular sessions. We are in the waiting list...08:20
ifat_afek#topic Open Discussion08:20
*** openstack changes topic to "Open Discussion (Meeting topic: vitrage)"08:20
ifat_afekany other issues?08:20
*** links has quit IRC08:21
ifat_afekgoodbye then08:21
danoffekby08:21
*** danoffek has left #openstack-meeting-408:21
ifat_afek#endmeeting08:21
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:21
eyalbbye08:21
openstackMeeting ended Wed Sep 28 08:21:48 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:21
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-09-28-08.01.html08:21
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-09-28-08.01.txt08:21
openstackLog:            http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-09-28-08.01.log.html08:21
*** eyalb has quit IRC08:22
*** rstarmer has joined #openstack-meeting-408:30
*** janonymous has joined #openstack-meeting-408:35
*** links has joined #openstack-meeting-408:37
*** elisha_r has quit IRC08:38
*** sdake has joined #openstack-meeting-408:41
*** sdake has quit IRC08:42
*** sshnaidm has joined #openstack-meeting-408:42
*** jed56 has joined #openstack-meeting-408:45
*** dshakhray_ has quit IRC08:46
*** danpawlik has joined #openstack-meeting-408:49
*** _oanson is now known as oanson08:55
*** ifat_afek has quit IRC08:55
*** Julien-z_ has joined #openstack-meeting-408:58
*** dtardivel has joined #openstack-meeting-408:58
*** vincentfrancoise has joined #openstack-meeting-409:00
*** ifat_afek has joined #openstack-meeting-409:00
acabot#startmeeting watcher09:00
openstackMeeting started Wed Sep 28 09:00:38 2016 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
acaboto/09:00
vincentfrancoiseo/09:00
*** licanwei has joined #openstack-meeting-409:00
*** befreax has joined #openstack-meeting-409:00
dtardivelhi09:01
*** befreax is now known as tmetsch09:01
licanweihi09:01
tmetschhi09:01
acabotagenda for today https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#09.2F28.2F201609:02
*** cartik has quit IRC09:02
acabot#topic Announcements09:02
*** openstack changes topic to "Announcements (Meeting topic: watcher)"09:02
acabot#info please complete topics list in barcelona summit etherpad09:02
acabot#link https://etherpad.openstack.org/p/watcher-ocata-design-session09:02
acabottmetsch : do you plan to join us in Barcelona ?09:03
tmetschacabot: not 100% sure yet.09:03
acabotok09:03
acabotlicanwei : please complete the topics list in the etherpad09:04
acabot#info Watcher Newton final release will be submitted today09:04
acabotwe will have a final release for watcher-pythonclient and watcher-dashboard as well09:05
acabotplease test it asap, it still time to submit bugs09:05
acabotany other announcement ?09:05
acabot#topic Review Action Items09:06
*** openstack changes topic to "Review Action Items (Meeting topic: watcher)"09:06
acabotWatcher specs09:06
acabotResize instance base on workload needs reviews from core09:06
acabot#link https://review.openstack.org/#/c/359690/09:06
acabotlicanwei : is this ready to be reviewed ?09:06
*** alexchadin has joined #openstack-meeting-409:06
*** diga_ has joined #openstack-meeting-409:07
diga_o/09:07
diga_got late09:07
alexchadino/09:07
licanweiacabot:ok09:07
acabotdiga_ : no pb09:07
acabot#action sballe jwcroppe hvprash acabot review https://review.openstack.org/#/c/359690/09:07
acabotLimit concurrent actions invoked by Watcher needs a new PS09:07
acabot#link https://review.openstack.org/#/c/348049/09:08
acabot#action jwcroppe add a new PS for https://review.openstack.org/#/c/348049/09:08
acabotautomatic triggering of action plans for AUDIT needs a new PS09:08
acabot#link https://review.openstack.org/#/c/342473/09:08
diga_acabot: yes09:08
acabotdiga_ : I'm concerned about the speed of this spec...09:08
diga_acabot: I will make sure, it will get merged till next meeting09:09
acabotdiga_ : do you want me to take it over and then you will be able to start implementing ?09:09
acabotdiga_ : I dont think its ready for core reviews09:09
diga_acabot: yes, I need to update it09:10
acabotdiga_ : could you please update it before EOW ?09:10
diga_acabot: okay09:10
*** janki has quit IRC09:10
acabot#action diga_ add a new PS for https://review.openstack.org/#/c/342473/09:10
acabotAdd team priorities for Ocata needs a new PS with BP split09:10
acabot#link https://review.openstack.org/#/c/372528/09:10
acabot#action acabot add a new PS for https://review.openstack.org/#/c/372528/09:11
acabotWatcher09:11
acabotAdd Audit Scope Handler needs reviews09:11
acabot#link https://review.openstack.org/#/q/status:open++topic:bp/define-the-audit-scope09:11
acabotdtardivel is already working on it09:11
*** sambetts_ is now known as sambetts09:12
acabotlicanwei : do you want to review it ?09:12
licanweiok09:12
acabot#action licanwei review https://review.openstack.org/#/q/status:open++topic:bp/define-the-audit-scope09:13
acabotGraph cluster model implementation needs reviews09:13
acabot#link https://review.openstack.org/#/c/362730/09:13
dtardivelacabot: I'm revewing09:14
acabottmetsch : do you follow Kevin work on this ?09:14
tmetschyes09:14
acabot#action dtardivel review https://review.openstack.org/#/q/status:open++topic:bp/define-the-audit-scope09:14
acabottmetsch : vincentfrancoise started reviewing it09:14
tmetschthanks for that - I'll work with Kevin and address the issue.09:15
vincentfrancoisetmetsch: yeah I started reviewing it yesterday and there were a few points that were bugging me09:15
vincentfrancoiseI will address them in the review and I will post probably post them by EOD09:16
acabot#action vincentfrancoise add questions on https://review.openstack.org/#/c/362730/09:16
tmetschvincentfrancoise: cool thanks!09:16
acabot#action tmetsch add a new PS for https://review.openstack.org/#/c/362730/ answering comments and questions09:17
acabotAdd service supervisor needs reviews09:17
acabot#link https://review.openstack.org/#/q/status:open+project:openstack/watcher+branch:master+topic:bp/watcher-service-list09:17
acabotlicanwei : do you want to review this as well ?09:17
licanweiacabot: np09:17
dtardivelI can review it as well09:17
acabot#action licanwei dtardivel review https://review.openstack.org/#/q/status:open+project:openstack/watcher+branch:master+topic:bp/watcher-service-list09:18
acabotAdded Tempest API tests for /scoring_engines needs reviews09:18
acabot#link https://review.openstack.org/#/c/371558/09:18
acabotanyone likes to review tempest tests ?09:19
acabotits a small PS ;-)09:19
licanweime09:20
acabotthx09:20
acabot#action licanwei review https://review.openstack.org/#/c/371558/09:20
acabotlets move to Watcher CLI09:20
acabotAdded support for Client creation from KS session needs reviews09:21
acabot#link https://review.openstack.org/#/c/374286/09:21
acabotit would be great to have this merge for Newton09:21
acabotbut its a large PS...09:21
acabotanyone familiar with keystone here ?09:22
dtardivel+109:22
acabot#action dtardivel review https://review.openstack.org/#/c/374286/09:23
acabotthx09:23
acabotWatcher dashboard09:23
acabotAdded action details needs reviews09:23
acabot#link https://review.openstack.org/#/c/377699/09:23
vincentfrancoisethis is essentially a big refactoring that allows us to simplify the use of python-watcherclient as an SDK instead of a shell command09:23
acabotwe really need to have the action details merged before the final release09:23
acabotwho can review it today ?09:24
dtardivel+109:24
vincentfrancoiseThe idea is to make it behave like other projects to reduce the difficulty for people already used to other OS clients09:24
acabot#action dtardivel review https://review.openstack.org/#/c/377699/09:24
acabotthanks vincentfrancoise for the explanations09:25
acabot#topic Blueprint/Bug Review and Discussion09:25
*** openstack changes topic to "Blueprint/Bug Review and Discussion (Meeting topic: watcher)"09:25
acabot#info Improve the storage of the ActionPlan has many dependencies and should be started asap09:25
acabot#link https://blueprints.launchpad.net/watcher/+spec/planner-storage-action-plan09:25
*** numans has joined #openstack-meeting-409:25
acabotlicanwei : this BP has been taken by jinquan09:25
acabotlicanwei : I'd like to start working on spec now09:26
licanweiacabot: ok09:26
acabotlicanwei : do you know if he can leave the BP ?09:26
*** ifat_afek has quit IRC09:26
acabotlicanwei : or if he already started working a on spec ?09:26
licanweiI don't know09:27
acabotok I will ask him on launchpad09:27
acabot#action acabot ask jinquan to leave the BP https://blueprints.launchpad.net/watcher/+spec/planner-storage-action-plan09:27
licanweiI can ask him09:28
acabotok09:28
acabot#link https://launchpad.net/watcher/+milestone/newton-rc-final09:28
acabotwe still have 1 bug open09:28
acabot#link https://bugs.launchpad.net/bugs/162022509:28
openstackLaunchpad bug 1620225 in watcher "missing doc section to add notifications when building a new cluster data model collector" [Medium,Triaged]09:28
*** limao has quit IRC09:28
acabotvincentfrancoise dtardivel : can we fix it before the release ?09:29
dtardivelacabot: We already added a section in the configuration section ...;09:29
vincentfrancoiseacabot: doesn't it correspond to http://docs.openstack.org/developer/watcher/dev/plugin/cdmc-plugin.html#add-new-notification-endpoints ?09:30
vincentfrancoiseacabot: in which case we can close this bug straight away :)09:30
acabotvincentfrancoise : :-) I think you can09:31
acabot#topic Open discussions09:31
*** openstack changes topic to "Open discussions (Meeting topic: watcher)"09:31
acabotI forgot to mention that slides for Watcher talk in Barcelona are open to reviews09:31
acabot#link https://drive.google.com/file/d/0B_YlsOGofvCCZFc3UnZ1MkxBNG8/view?ts=57eaab7309:32
acabot#undo09:32
openstackRemoving item from minutes: <ircmeeting.items.Link object at 0x7f66f52ef750>09:32
acabot#link https://drive.google.com/file/d/0B_YlsOGofvCCZFc3UnZ1MkxBNG8/view?usp=sharing09:32
*** LotharKAtt has quit IRC09:32
acabot#info We need more reviewers on patches09:34
acabottoday most of the reviews are done by core contributors09:34
acabotand I think we need more +1 before each +209:34
acabotso please review some code09:35
vincentfrancoise+1 on that09:35
acabotlicanwei : thank you for taking all these reviews today09:35
*** Julien-z_ has quit IRC09:35
licanwei:)09:35
acabot#action sballe jwcroppe hvprash try to convince people to do more reviews on the project09:36
acabotany other discussion to open ?09:36
diga_acabot: is it ok if I start reviewing the code ?09:36
vincentfrancoisediga_: anytime you want :)09:37
acabotdiga_ : of course you are more than welcome to review09:37
diga_vincentfrancoise: acabot : thank you!09:37
acabotdiga_ : if you start reviewing, please reply with a comment09:37
diga_acabot: sure09:38
acabotevery +1/-1 or even 0 is counted09:38
diga_okay09:38
acabotif you look at this #link http://stackalytics.com/?module=watcher-group09:38
diga_acabot: this is good way to understand watcher completely09:38
diga_sure09:39
acabot72% of reviews are done by b@#com09:39
*** berendt has joined #openstack-meeting-409:39
acabotwe should be around 50%09:39
acabotevery new contributor reviewing code is good for the project09:40
diga_Yes09:40
acabotif you dont have any other topic to discuss, we can close the meeting09:40
acabotthank you09:40
*** gongysh has quit IRC09:40
diga_I appreciate b-com teams efforts on this project, I see it everydy09:41
acabotdiga_ : thx09:41
acabotbye09:41
vincentfrancoisebye09:41
diga_acabot: wc! bye09:41
licanweibye09:41
acabot#endmeeting09:41
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:41
openstackMeeting ended Wed Sep 28 09:41:38 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:41
openstackMinutes:        http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-09-28-09.00.html09:41
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-09-28-09.00.txt09:41
openstackLog:            http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-09-28-09.00.log.html09:41
*** tmetsch has left #openstack-meeting-409:41
*** licanwei has quit IRC09:42
*** vincentfrancoise has left #openstack-meeting-409:43
*** dshakhray_ has joined #openstack-meeting-409:43
*** barmaley has quit IRC09:44
*** alexchadin has quit IRC09:48
*** alexchadin has joined #openstack-meeting-409:49
*** alexchadin has quit IRC09:53
*** matrohon has quit IRC09:56
*** ralonsoh_ has joined #openstack-meeting-409:58
*** ralonsoh_ has quit IRC09:58
*** ralonsoh has quit IRC09:59
*** ralonsoh has joined #openstack-meeting-409:59
*** bogdando has quit IRC10:00
*** zhurong has quit IRC10:02
*** xuao has quit IRC10:12
*** yamamoto has quit IRC10:13
*** bogdando has joined #openstack-meeting-410:16
*** sshnaidm is now known as sshnaidm|lnch10:21
*** anilvenkata_afk has quit IRC10:31
*** numan_ has joined #openstack-meeting-410:31
*** anilvenkata_afk has joined #openstack-meeting-410:31
*** numans has quit IRC10:35
*** spotz_zzz is now known as spotz10:36
*** rstarmer has quit IRC10:39
*** salv-orlando has joined #openstack-meeting-410:40
*** salv-orl_ has quit IRC10:40
*** _degorenko is now known as degorenko10:46
*** dingboopt_ has quit IRC10:50
*** alexchadin has joined #openstack-meeting-410:52
*** links has quit IRC10:53
*** links has joined #openstack-meeting-411:02
*** sshnaidm|lnch is now known as sshnaidm11:08
*** ifat_afek has joined #openstack-meeting-411:08
*** sdague has joined #openstack-meeting-411:09
*** idan_hefetz has left #openstack-meeting-411:15
*** dcwangmit01_ has quit IRC11:15
*** rtheis has joined #openstack-meeting-411:16
*** spotz is now known as spotz_zzz11:16
*** karthiks has joined #openstack-meeting-411:16
*** dcwangmit01 has joined #openstack-meeting-411:20
*** cdelatte has quit IRC11:40
*** zhurong has joined #openstack-meeting-411:41
*** anilvenkata_afk is now known as anilvenkata11:43
*** haleyb_ has joined #openstack-meeting-411:43
*** salv-orlando has quit IRC11:44
*** thorst has joined #openstack-meeting-411:48
*** ifat_afek has quit IRC11:52
*** markvoelker has quit IRC11:53
*** berendt has quit IRC11:54
*** baoli has joined #openstack-meeting-411:58
*** ifat_afek has joined #openstack-meeting-412:01
*** sdake has joined #openstack-meeting-412:02
*** cdelatte has joined #openstack-meeting-412:09
*** cdelatte has quit IRC12:11
*** diga_ has quit IRC12:11
*** alexchadin has quit IRC12:11
*** alexchadin has joined #openstack-meeting-412:12
*** haleyb_ has quit IRC12:14
*** baoli has quit IRC12:16
*** yamamoto has joined #openstack-meeting-412:16
*** woodard has joined #openstack-meeting-412:22
*** yamamoto has quit IRC12:25
*** haleyb_ has joined #openstack-meeting-412:28
*** alexchadin has quit IRC12:30
*** salv-orlando has joined #openstack-meeting-412:33
*** oanson has quit IRC12:34
*** Julien-zte has joined #openstack-meeting-412:37
*** myatsenko1 has quit IRC12:41
*** myatsenko has joined #openstack-meeting-412:42
*** duvarenkov has quit IRC12:42
*** aarefiev has quit IRC12:42
*** duvarenkov has joined #openstack-meeting-412:43
*** ifat_afek has quit IRC12:43
*** aarefiev has joined #openstack-meeting-412:44
*** yamamoto has joined #openstack-meeting-412:45
*** yamamoto has quit IRC12:45
*** yamamoto has joined #openstack-meeting-412:49
*** oshidoshi has joined #openstack-meeting-412:52
*** markvoelker has joined #openstack-meeting-412:55
*** LotharKAtt has joined #openstack-meeting-412:55
*** mriedem has joined #openstack-meeting-412:56
*** david-lyle has joined #openstack-meeting-412:57
*** vishwanathj has joined #openstack-meeting-412:58
*** baoli has joined #openstack-meeting-412:59
alex_xu#startmeeting nova api13:00
openstackMeeting started Wed Sep 28 13:00:03 2016 UTC and is due to finish in 60 minutes.  The chair is alex_xu. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: nova api)"13:00
openstackThe meeting name has been set to 'nova_api'13:00
alex_xuwho is here today?13:00
*** rstarmer has joined #openstack-meeting-413:00
mriedemo/13:00
alex_xusdague: johnthetubaguy gmann are you around for api meeting13:01
johnthetubaguyo/13:01
*** caboucha has joined #openstack-meeting-413:01
alex_xulet us wait one mins?13:01
*** baoli_ has joined #openstack-meeting-413:02
alex_xuok, just three of us13:02
alex_xulet us start the meting13:02
alex_xu#topic action from previous meeting13:02
*** openstack changes topic to "action from previous meeting (Meeting topic: nova api)"13:02
alex_xuaction: alex_xu to work on generic diagnostics spec13:03
alex_xu#link https://review.openstack.org/35788413:03
alex_xuSergey already help on this spec13:03
* edleafe wanders in late13:03
mriedemi haven't seen the latest on that one yet13:04
alex_xuthere is one hot point in the spec13:04
alex_xuuse which value to identify the disk13:04
*** rstarmer has quit IRC13:04
*** Julien-zte has quit IRC13:04
mriedemfor libvirt i thought we can't rely on the device name13:05
alex_xuthere are three options at here, bdm_id, device_name, and disk local path13:05
mriedemso that's why people wanted tags13:05
alex_xumriedem: yea, +113:05
alex_xumriedem: the tags is really for normal user, which defined by normal user, and used by normal user13:05
mriedemi don't like the idea of leaking the bdm id13:05
sdagueo/13:05
*** baoli has quit IRC13:06
alex_xuexpose the tags in an API for debug, that sounds duplicated13:06
mriedembdm id is per cell and if we're talking about the id field in the db table it could collide with bdms in other cells13:06
*** portdirect has joined #openstack-meeting-413:06
alex_xuso the disk local path is the last choice13:06
sdaguemriedem: it's not a uuid?13:07
*** yamamoto has quit IRC13:07
johnthetubaguyor we create a uuid for this API13:07
alex_xuit is not13:07
alex_xujohnthetubaguy: but we doesn't have api expose the bdm also13:07
mriedemsdague: yeah we don't have a uuid on the bdm table13:08
mriedemwe've talked about having one forever13:08
mriedembut never had use cases13:08
mriedemdansmith has the patches to make that happen though13:08
mriedemdisk local path is the path on the host?13:08
*** yamamoto has joined #openstack-meeting-413:08
*** klamath has joined #openstack-meeting-413:09
alex_xumriedem: for network device, it can be a URI, very virt driver specific13:09
*** Julien-zte has joined #openstack-meeting-413:09
* johnthetubaguy scratches head13:09
*** ldeptula has joined #openstack-meeting-413:09
mriedemhmm, if the only point is having a unique identifier per disk/bdm, then i think i'd just go with a uuid13:09
mriedemand we revive dansmith's patches to add a uuid field to the bdm13:10
sdagueyeh, uuid seems better than a uri13:10
*** sshnaidm is now known as sshnaidm|afk13:10
alex_xuthe point for disk path is this is debug API, so it should be ok for debug user13:10
mriedemhttps://review.openstack.org/#/q/status:abandoned+project:openstack/nova+branch:master+topic:bug/1489581+owner:dms@danplanet.com13:11
johnthetubaguyit feels like we should do it properly and add a uuid anyways13:11
sdaguejohnthetubaguy: ++13:11
alex_xuso do way need API expose that uuid?13:12
*** psachin has quit IRC13:12
*** alexchadin has joined #openstack-meeting-413:12
alex_xus/way/we13:12
mriedemi'd think so13:13
alex_xusomething like /servers/{uuid}/bdm?13:13
*** woodster_ has joined #openstack-meeting-413:13
johnthetubaguyso we spoke about the VIF APIs I think, pointing to neutron, feels like a unified list of disks that has all bdms, not just volumes, might be what we want?13:14
sdaguejohnthetubaguy: yeh, a GET call for that as a sub resource probably makes some sense13:14
sdaguelike alex_xu just said13:14
johnthetubaguyyeah, I just wonder if we already have something close...13:14
johnthetubaguyoh, we call it os-volume_attachments, thats clearly not a bdm13:15
alex_xuwe have vol-attachment API, but it won't include swap and ephermal disk13:15
mriedemnor a bdm uuid since that doesn't exist yet13:16
mriedembrb13:16
sdagueyeh, so /servers/{uuid}/bdm seems like a good approach there13:16
*** sshnaidm|afk has quit IRC13:16
alex_xuis it a little duplicated with vol-attachment API?13:16
sdagueI guess, is the disk device info the only hold out here? Could we split that out?13:16
*** berendt has joined #openstack-meeting-413:17
sdagueso diagnostics - disk on first go, get that in. Sort out bdm consistent exposure in parallel, then diag + bdm as second pass.13:17
sdaguejust so that the rest of the cleanup work can be sorted13:17
*** vhoward has joined #openstack-meeting-413:17
johnthetubaguysdague: that sounds like a good idea13:18
alex_xuwe have microversion, so that is cool for making progress :)13:18
alex_xuanother idea is if we don't have clear use-case for /servers/uuid/bdm, we can put some bdm attribute with uuid in the diag API13:19
*** psachin has joined #openstack-meeting-413:19
sdagueso, honestly, it feels like more consistently dealing with bdm and not just in the attachment api seems sensible13:19
johnthetubaguyhonestly, it feels like BDMs need some thought, generally. Where do we want to take disks and flavors.13:19
johnthetubaguyit feels a bit wrong we don't expose bdms in a GET api13:20
sdaguejohnthetubaguy: yeh13:20
sdagueok, so plan forward. Split diagnostics spec so there is a non disk version13:20
alex_xuah, i see the point13:20
sdagueget that sorted and landed13:20
*** ifat_afek has joined #openstack-meeting-413:21
sdaguethen there is probably a bdm api spec (which includes uuid exposure) and diag + bdm13:21
sdagueright?13:21
*** salv-orlando has quit IRC13:21
johnthetubaguy+113:22
alex_xuyea13:22
*** Julien-zte has quit IRC13:23
mriedemthat would be a regression from the existing diagnostics api,13:23
mriedemso if you wanted disk stuff you'd have to use v2.1 or something lower13:23
mriedemthe existing diagnostics api doesn't expose a disk id though, but it does expose some disk stuff13:24
alex_xuor just no id, but with disk info13:24
alex_xumriedem: yea13:24
sdagueok, well, maybe that then13:24
sdaguethe thing is, I'd hate to have the standardization get held up on disk id thing that is going to take a while to sort out13:24
*** Julien-zte has joined #openstack-meeting-413:25
mriedemif long-term you want both disk path and id in the diag api,13:26
mriedemthen you could do disk path now13:26
mriedemand add id later13:26
johnthetubaguydo we want disk path?13:26
mriedemidk13:26
mriedemit's really hard to tell what should be in this thing w/o input from someone that uses it13:26
mriedemwe could query the ops list to see if anyone uses the api and if so, what they think about options we're talking about13:27
*** cdent has joined #openstack-meeting-413:28
johnthetubaguyyes, although releasing a smaller reduced, but standardized API feels like an improvement13:28
johnthetubaguythey may just tell us to delete it, I guess13:29
*** claudiub has joined #openstack-meeting-413:30
sdagueso, with the microversion it would let us replace this with something standard, even if missing info13:30
mriedemi've got to get my kid on the bus so back in a while13:30
alex_xuso, what we should do?13:31
sdagueok, maybe another topic, because we seem to not be agreed here13:31
johnthetubaguyyeah, lets come back to this later13:31
sdagueI don't think we're going to get reasonable feedback off of the ops list for a thing like this13:31
sdagueand I think standarization is more important than missing info13:32
johnthetubaguy+1 for just getting this standardized13:32
alex_xu+113:32
johnthetubaguyeven with missing info13:32
*** alexchadin has quit IRC13:33
alex_xuso let me feedback to the spec, then we revisit the id problem later?13:33
*** alexchadin has joined #openstack-meeting-413:34
sdaguealex_xu: sounds good13:35
alex_xu#action alex_xu feedback to the diag API spec about just standardized the API first13:35
alex_xuso let's go next one13:36
alex_xuaction: johnthetubaguy to sketch out what an ideal security group workflow looks like in the nova api now with neutron as the presumed backend13:36
alex_xu#link https://etherpad.openstack.org/p/ocata-nova-security-groups13:36
johnthetubaguyso that etherpad I had, includes some ideas13:36
johnthetubaguynova boot --nic net-id=uuid_net1 security-group=db --nic ned-id=uuid_net2 security-group=api --flavor 1 --image test-image test-server13:37
johnthetubaguyis where I was thinking we could go13:37
johnthetubaguyto add a security group13:37
johnthetubaguythen you just need to look at the port in neutron to find out or modify any details around that13:38
alex_xujohnthetubaguy: so we just need fail when use it with nova-network?13:38
sdaguejohnthetubaguy: yeh, that makes a lot of sense.13:38
*** links has quit IRC13:38
johnthetubaguyalex_xu: I am thinking nova-network dies in a few weeks, lets just worry about neutron13:38
sdaguealex_xu: well nova-net calls after 2.35 are pretty suspect anyway13:38
johnthetubaguyright, use the older version of the API if you must use nova-network still13:38
alex_xuok, cool13:38
sdaguejohnthetubaguy: can you turn that into a spec? That seems like it would solve a bunch of things13:39
alex_xuI'm thinking should we stop some point which works for nova-network after 2.3513:39
johnthetubaguyyeah, I can make that into a spec13:39
*** woodard_ has joined #openstack-meeting-413:40
*** tonytan4ever has joined #openstack-meeting-413:40
*** woodard_ has quit IRC13:40
mriedemalex_xu: well, deleting nova-network is going to make it stop after 2.3513:40
mriedemand before 2.35 for that matter13:40
*** woodard_ has joined #openstack-meeting-413:40
johnthetubaguyright, this becomes simpler once we nuke nova-net13:40
alex_xuah, I see now13:41
johnthetubaguy#action johnthetubaguy to create a spec out of ideas in https://etherpad.openstack.org/p/ocata-nova-security-groups13:41
alex_xuok, so let us go to next one13:41
johnthetubaguythe bit I like about --nic is that already means nothing for nova-net13:41
*** woodard_ has quit IRC13:41
alex_xujohnthetubaguy: yea13:42
alex_xuaction: mriedem to write up spec for os-virtual-interface deprecation13:42
mriedemnot really13:42
mriedem--nic can pass the network id or fixed ip for nova-net13:42
mriedemyou just can't pass a port for nova-net13:42
mriedemalex_xu: i didn't get that done13:42
johnthetubaguymriedem: oh, I didn't know that was a thing13:42
alex_xumriedem: it's fine, so let us talk about that when it is ready13:43
alex_xuso next one13:43
alex_xuaction: alex_xu to write a spec for deprecating the proxy api to set/delete image metadata13:43
alex_xu#link https://review.openstack.org/37752813:43
alex_xumriedem already give some review, I need update the spec13:44
*** woodard has quit IRC13:44
*** alexchadin has quit IRC13:44
alex_xuthe only highlight in the spec is there is quota check in server create_image API, which I thought we should remove13:44
mriedemi think the quota check should be gone, it's actually kind of silly that nova has that at all given glance could blow up even if you pass the nova quota check for image metadata properties13:45
mriedemif the glance quota is lower13:45
alex_xumriedem: yea13:45
mriedemthe thing i'm nervous about is moving the image create before the volume snapshot13:46
mriedemnot for any known reason right now except dragons13:46
alex_xuyea, I double check that, probaly test it in my local env, ensure it is safe13:46
mriedemnote also,13:46
mriedemcinder probably has a quota on volume snapshots13:46
mriedemso you are fixing one thing by moving image create before vol snapshot, but could be breaking the quota check on vol snapshot13:47
mriedemwell, not breaking but you could still fail13:47
mriedemfwiw this is probably why nova-api checks port quota with neutron before casting to the compute to create new ports13:47
mriedemracey as that is13:47
johnthetubaguymriedem: I have a spec in the works to possibly change that, but yeah13:48
mriedem# Number of volume snapshots allowed per project (integer value) #quota_snapshots = 1013:48
mriedem^ from cinder.conf13:48
mriedemalex_xu: so i think i'd rather not even move the image create before the vol snapshot13:49
mriedemsince either could fail a quota check13:49
johnthetubaguyhonestly, leaving the order the same is probably a good idea, just to keep the API semantics the same13:49
johnthetubaguyyeah, because either could fail13:49
mriedemyes i don't want to introduce some new weirdness we don't know about if we don't have to13:49
alex_xubut if we do vol snapshot first, then create image on glance failed on quota, that sounds waste. in the glance side, it just a db call.13:49
mriedemwell, vol snapshot quota check in cinder should also be a db call,13:49
mriedemor do you mean, create image is a db call, then you still have to upload the data to glance13:50
alex_xumriedem: even if we don't move that, but sounds like we should have some rollback code for removing vol snaphsot when quota fail on glance?13:50
mriedemwhich you won't have to do if you fail the image create13:50
*** bobh_ has joined #openstack-meeting-413:50
johnthetubaguythey could both fail for other reasons though, feels like we should fix that anyways13:50
mriedemwe'd probably want that yeah13:51
mriedemright it sounds like a bug exposure today13:51
johnthetubaguyI mean treat it separately outside this spec, I guess13:51
mriedemwe could test it by creating a volume-backed instance, set cinder snapshot quota to 0 and try to snapshot13:51
mriedemand make sure everything is cleaned up13:51
mriedemjohnthetubaguy: +1 - i think it's just a bug13:51
johnthetubaguyyeah13:51
alex_xuok, I can move that to a bug13:52
*** ddieterly has joined #openstack-meeting-413:52
johnthetubaguywell, we have the rest of the spec, and a separate bug, to be clear13:52
*** haleyb_ has quit IRC13:52
*** bobh_ has quit IRC13:53
mriedemyes the rest of the spec is pretty clear13:53
alex_xu#action alex_xu is going to double check the moving create image, then separate the spec to a spec and a bug13:53
*** bobh_ has joined #openstack-meeting-413:53
alex_xuok, so let us go next one?13:54
mriedemyeah 6 min13:54
*** uck has joined #openstack-meeting-413:54
alex_xuaction: mriedem to follow up with gmann about testing swap-volume in tempest13:54
*** ramishra has joined #openstack-meeting-413:54
*** uck has quit IRC13:54
alex_xulooks like we can't finish all the items today13:54
*** uck has joined #openstack-meeting-413:55
mriedemgmann is out for awhile so i'll handle that tempest test,13:55
mriedemit just needs to move from scenario to api13:55
mriedem#action mriedem to move swap volume test from scenario to api https://review.openstack.org/#/c/299830/13:55
alex_xumriedem: cool, thanks13:55
alex_xuaction: sdague to start in on a capabilities spec13:56
sdague#link https://review.openstack.org/#/c/377756/13:56
sdagueit's pretty early, but hopefully a reasonable starting point13:56
alex_xuyea, sounds like it is related to qualitative part of placement13:56
sdaguethe key thing I wanted to capture is that we're going to need a way to query *all* possible capabilities, as well as what's allowed on any particular resource13:57
sdagueotherwise we'll be in versioning hell13:57
alex_xu+113:57
sdagueI'm going to be out until the next meeting, so feedback there probably worth while13:58
alex_xuoops, I'm in holiday next week also13:58
*** uxdanielle has joined #openstack-meeting-413:58
sdaguethere are a couple of good feedback points13:58
alex_xudo we still want to cancel this meeting next week?13:58
alex_xuoops, you mean out before the next meeting13:59
sdagueone which is what degree of machine consumption vs. doc consumption we should end up with13:59
johnthetubaguysdague: I like the idea of ensuring we can see the full list of possible capabilities, to help with versioning, as you say13:59
sdaguethe other is about granularity, though I honestly think that's mostly a comes later13:59
alex_xu1 mins left13:59
sdaguegranularity gets decided independently of the mechanism to expose I think13:59
johnthetubaguyI am quite keen on very course grained, to a human could understand things13:59
johnthetubaguyso a14:00
alex_xuso let us back to nova channel14:00
alex_xuthanks all14:00
sdaguesure14:00
alex_xu#endmeeting14:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:00
openstackMeeting ended Wed Sep 28 14:00:20 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-09-28-13.00.html14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-09-28-13.00.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-09-28-13.00.log.html14:00
*** mriedem has left #openstack-meeting-414:00
*** Rockyg has joined #openstack-meeting-414:00
*** andymaier has joined #openstack-meeting-414:01
*** galstrom_zzz is now known as galstrom14:02
*** sshnaidm|afk has joined #openstack-meeting-414:08
*** rbak has joined #openstack-meeting-414:08
*** haleyb_ has joined #openstack-meeting-414:10
*** vishnoianil has joined #openstack-meeting-414:12
*** oshidoshi has quit IRC14:14
*** salv-orlando has joined #openstack-meeting-414:20
*** prateek_ has quit IRC14:22
*** uck has quit IRC14:22
*** padkrish has joined #openstack-meeting-414:23
*** Julien-zte has quit IRC14:24
*** Julien-zte has joined #openstack-meeting-414:24
*** hongbin has joined #openstack-meeting-414:24
*** padkrish_ has joined #openstack-meeting-414:27
*** yamahata has joined #openstack-meeting-414:27
*** spotz_zzz is now known as spotz14:28
*** iyamahat has joined #openstack-meeting-414:29
*** padkrish has quit IRC14:29
*** baoli_ has quit IRC14:31
*** baoli has joined #openstack-meeting-414:31
*** ricolin has joined #openstack-meeting-414:32
*** numan_ has quit IRC14:32
*** limao has joined #openstack-meeting-414:32
*** LotharKAtt has quit IRC14:33
*** limao_ has joined #openstack-meeting-414:33
*** limao has quit IRC14:37
*** spzala has joined #openstack-meeting-414:38
*** baoli has quit IRC14:38
*** caowei has quit IRC14:39
*** haleyb_ has quit IRC14:44
*** padkrish_ has quit IRC14:45
*** yamamoto has quit IRC14:52
*** yamamoto has joined #openstack-meeting-414:52
*** Swami has joined #openstack-meeting-414:53
*** bobh_ has quit IRC14:54
*** ddieterly has quit IRC14:56
*** ddieterly has joined #openstack-meeting-414:56
*** mhoppal has joined #openstack-meeting-414:59
*** mhoppal has left #openstack-meeting-414:59
*** cwolferh has joined #openstack-meeting-414:59
*** rpothier has joined #openstack-meeting-415:00
ramishra#startmeeting heat15:00
openstackMeeting started Wed Sep 28 15:00:27 2016 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
ramishra#topic roll call15:00
*** openstack changes topic to "roll call (Meeting topic: heat)"15:00
*** syed_ has joined #openstack-meeting-415:00
*** armax has joined #openstack-meeting-415:01
zanebo/15:01
skraynevo/15:01
spzalao/15:01
*** zhurong has quit IRC15:01
cwolferh\o15:01
*** marst has joined #openstack-meeting-415:02
*** therve has joined #openstack-meeting-415:02
therveHey15:02
ricolin0/15:03
*** Drago has joined #openstack-meeting-415:03
Dragoo/15:03
*** padkrish has joined #openstack-meeting-415:03
ramishra#topic adding items to agenda15:03
*** openstack changes topic to "adding items to agenda (Meeting topic: heat)"15:03
*** ochuprykov has joined #openstack-meeting-415:04
ramishra#link https://wiki.openstack.org/wiki/Meetings/HeatAgenda#Agenda_.282016-09-28_1500_UTC.2915:04
*** caboucha has quit IRC15:04
*** caboucha has joined #openstack-meeting-415:04
ramishra#topic stable:follows-policy tag15:05
*** openstack changes topic to "stable:follows-policy tag (Meeting topic: heat)"15:05
ramishra#link http://governance.openstack.org/reference/tags/stable_follows-policy.html15:05
ramishranot sure who has added this.15:05
zanebme15:05
ramishraI assume a patch to governance repo should do it, no?15:05
zanebyes15:06
ramishraok, I'll do that15:06
*** Swami_ has joined #openstack-meeting-415:06
*** tonytan_brb has joined #openstack-meeting-415:06
zanebit will help if we have a link to a meeting decision that this is definitely what we want15:06
zanebI don't think it's controversial though, right?15:06
*** caowei has joined #openstack-meeting-415:07
therveJust confirming what we do already, you mean? :)15:07
zanebtherve: yeah15:07
therve+115:07
zanebI guess there's a theoretical difference between "following it" and "agreeing to be bound by it"15:08
ramishrayeah, we are agreeing to do it from now on:)15:08
zanebI'd also like to know why we have not been rated on "Existence and quality of packages for this project in popular distributions."15:08
ramishrazaneb: who can answer that question, tc?15:09
*** Swami has quit IRC15:09
zanebno, it's the ops group15:09
*** tonytan4ever has quit IRC15:09
zanebI'd also love to know exactly how many SDKs have to have support before you get a maturity tick there15:09
zanebbecause honestly 7 feels like a lot15:09
ramishraok, so we can drop a mail to them with the question?15:10
zanebmight be worth a try15:10
*** jovon has joined #openstack-meeting-415:11
ramishraok15:11
zanebmake sure they give us a fair shake for newton15:11
*** duonghq has joined #openstack-meeting-415:11
zaneb(we can move on :)15:11
ramishrayep15:11
ramishra#topic heat summit sessions15:11
*** openstack changes topic to "heat summit sessions (Meeting topic: heat)"15:11
thervezaneb, https://www.openstack.org/software/releases/mitaka/components/glance 8 is enough apparently :)15:12
ramishraI've arranged the topics now on the etherpad15:12
ramishrawe need more topics15:12
zanebtherve: so close!15:12
ramishra#link https://etherpad.openstack.org/p/ocata-heat-sessions15:12
ramishratherve: I saw your forwarded mail and I also got a mail from magnum PTL yesterday.15:13
ramishraThey want a joint session to discuss about some of the heat issues they are facing wrt heat scalability15:13
ramishrawe have one session on performance and scalability, probably add another one?15:14
therveYeah, we should do the usual "large stacks" session15:14
*** ldeptula has quit IRC15:14
ramishraanyway, we don't have enough sessions yet, so I'll add this one too.15:15
ramishrabtw, we probably have add a little more to the descriptions of the topics:)15:16
*** amotoki has quit IRC15:16
ramishraanyone has more topics, please propose them. We still have 3 more slots available.15:17
ramishraok, moving on..15:19
ramishra#topic gate failures15:19
*** openstack changes topic to "gate failures (Meeting topic: heat)"15:19
ramishraWe are seeing large number of gate failures these few days.15:19
ramishrait seems mostly due to some external network connectivity issues.15:19
*** caowei has quit IRC15:20
ramishraso we were thinking of disabling some of the tests that use fedora image? any thoughts?15:20
zanebno thoughts, but just a reminder to please tag gate failure bugs with 'gate-failure' so they end up in https://bugs.launchpad.net/heat/+bugs?field.tag=gate-failure15:21
ramishrazaneb: sure15:22
*** iyamahat has quit IRC15:22
*** cdent has left #openstack-meeting-415:22
therveramishra, There are many tests using image_ref15:22
therveMore than I thought15:22
*** yamahata has quit IRC15:22
therveWe should switch some of them to minimal first15:22
*** reedip has quit IRC15:23
ramishratherve: yeah, that why I was worried to disable all of them.15:23
therveramishra, I don't think most of them need it15:23
*** ifat_afek has quit IRC15:24
*** galstrom is now known as galstrom_zzz15:24
ramishrazaneb: I've added gate-failure tags to few of them just now.15:25
ramishratherve: yeah, probably we can change the tests where it's not needed first.15:26
ramishraand then look at disabling the ones left.15:26
*** nkrinner is now known as nkrinner_afk15:27
*** apuimedo is now known as apuimedo|away15:27
ramishraI was thinking of waiting for a response from the infra team before doing any test disable.15:27
therveWe got one, not really encouraging :)15:27
thervehttp://lists.openstack.org/pipermail/openstack-infra/2016-September/004750.html15:28
therveAlso <fungi> therve: sheer speculation, but if it's ipv4 then maybe we're overloading their pat (since that environment only has ipv6 for direct global connectivity)15:28
fungiyeah, we recently increased instance count significantly in that environment15:29
*** padkrish has quit IRC15:29
fungiso it's possible we've put strain on their networks, and the nat they're using to provide ipv4 egress is a likely weak spot15:29
thervefungi, Should we try ipv6 mirror?15:30
fungitherve: do they have one for the fedora images?15:30
therveNo idea15:30
zanebfungi: it seems like sdague's suggestion of mirroring that image locally is a good one, though maybe not a short-term fix. wdyt?15:30
*** baoli has joined #openstack-meeting-415:31
fungizaneb: we agreed during yesterday's infra meeting (in therve's absence) that it makes sense we just need whoever's going to implement the mirroring for arbitrary blobs to write up a very brief infra spec so we can work out the modekl15:31
fungimodel15:31
zanebfungi++15:32
fungi#link http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-09-27-19.02.log.html#l-11915:32
*** caowei has joined #openstack-meeting-415:32
*** vhoward has quit IRC15:32
fungibut in the near term, we're working with the operators for osic to see if we can figure out what's happening and then we'll either reduce our utilization there or they'll beef up whatever's overloaded15:33
fungithere's been ongoing discussion today in #openstack-infra about it15:33
*** limao_ has quit IRC15:33
*** limao has joined #openstack-meeting-415:33
*** galstrom_zzz is now known as galstrom15:33
*** limao has quit IRC15:34
*** padkrish has joined #openstack-meeting-415:34
thervehttp://mirror.speedpartner.de/ seems to be ipv6, it's worth trying15:34
*** limao has joined #openstack-meeting-415:34
*** ifat_afek has joined #openstack-meeting-415:35
cloudnullo/ if there's something i can help out with regarding OSIC issues please let me know.15:35
fungicloudnull: you already have been15:35
cloudnullI was just lurking and figured i'd say hi.15:35
*** reedip has joined #openstack-meeting-415:36
ramishrafungi, cloudnull, thanks for joining the discussion15:37
*** andymaier has quit IRC15:37
ramishratherve: will you propose a patch to use the specific mirror?15:38
therveramishra, Yep let me do that15:38
ramishratherve: thanks!15:38
ramishra#topic open discussion15:39
*** openstack changes topic to "open discussion (Meeting topic: heat)"15:39
ramishraanything else we want to discuss?15:40
*** haleyb_ has joined #openstack-meeting-415:41
therveIf anybody wants to look at memory consumption that'd be rad15:41
*** hrito has joined #openstack-meeting-415:41
zanebyeah, I'm looking but not making much progress15:42
*** AlanClark has joined #openstack-meeting-415:43
ramishrado you have an understanding now, when memory consumption started moving up again for tripleo?15:44
ramishrafrom some of the discussions it looked to coincide with the days when conditions patches landed, though we can infer anything from that.15:45
zanebI'm seeing a definite increase between http://logs.openstack.org/58/351358/1/check-tripleo/gate-tripleo-ci-centos-7-ovb-nonha/54cf4ea/logs/ and http://logs.openstack.org/40/359940/2/check-tripleo/gate-tripleo-ci-centos-7-ovb-nonha/f3c1ef5/logs/ which were both on 2016-08-25 and appear to use the same Heat build15:45
zanebso my suspicion is that some change to the templates may have triggered it15:46
*** haleyb_ has quit IRC15:46
ramishrayeah, we would need help from the tripleo team to resolve it. shardy does not seem to be online.15:49
ramishraif there is nothing else, we can move back to #heat15:50
*** reedip has quit IRC15:51
*** padkrish has quit IRC15:51
ramishraThanks all for joining15:51
ramishra #endmeeting heat15:51
*** neil__ has quit IRC15:52
ramishra#endmeeting heat15:52
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:52
openstackMeeting ended Wed Sep 28 15:52:09 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/heat/2016/heat.2016-09-28-15.00.html15:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/heat/2016/heat.2016-09-28-15.00.txt15:52
openstackLog:            http://eavesdrop.openstack.org/meetings/heat/2016/heat.2016-09-28-15.00.log.html15:52
*** zhubingbing has joined #openstack-meeting-415:52
*** therve has left #openstack-meeting-415:53
*** iyamahat has joined #openstack-meeting-415:54
*** ochuprykov has quit IRC15:54
*** bobh_ has joined #openstack-meeting-415:54
*** pbourke has joined #openstack-meeting-415:55
*** Drago has left #openstack-meeting-415:55
*** rhallisey has joined #openstack-meeting-415:56
*** woodard has joined #openstack-meeting-415:56
*** inc0 has joined #openstack-meeting-415:57
*** sbezverk has joined #openstack-meeting-415:58
*** unicell1 has joined #openstack-meeting-415:58
*** egonzalez90 has joined #openstack-meeting-415:58
*** bobh_ has quit IRC15:59
*** tonytan_brb is now known as tonytan4ever15:59
*** unicell has quit IRC16:00
sdake#startmeeting kolla16:00
openstackMeeting started Wed Sep 28 16:00:25 2016 UTC and is due to finish in 60 minutes.  The chair is sdake. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: kolla)"16:00
openstackThe meeting name has been set to 'kolla'16:00
sdake#topic rollcall16:00
*** openstack changes topic to "rollcall (Meeting topic: kolla)"16:00
duonghqo/16:00
*** galstrom is now known as galstrom_zzz16:00
zhubingbingo/16:00
rhalliseyhello16:00
zhubingbing\o/16:00
egonzalez90o/16:00
hritoo/16:01
*** krtaylor has quit IRC16:01
akwasnie\o16:01
caoweihi16:01
Jeffrey4lo/16:01
*** cartik has joined #openstack-meeting-416:01
*** lrensing has joined #openstack-meeting-416:01
sdakehey there folks ;)16:02
lrensingo/16:02
kfox1111o/16:02
sbezverko/16:02
sdakewhere be inc016:02
inc0here16:02
sdakecool16:02
*** berendt has joined #openstack-meeting-416:02
sdake#topic announcements16:02
*** openstack changes topic to "announcements (Meeting topic: kolla)"16:02
berendto/16:02
*** srwilkers has joined #openstack-meeting-416:03
sdakeas you are probably aware, inc0 is my successor as ptl - say grats ;)16:03
*** lamt has joined #openstack-meeting-416:03
srwilkerscongrats inc016:03
egonzalez90congrats inc0 !!16:03
kfox1111contrats inc0!16:03
inc0\o/16:03
duonghqcongratulation inc016:03
lrensingcongrats!16:03
inc0thank you all:)16:03
kfox1111sdake: and thanks for all your hard work! :)16:03
akwasniecongratulations, Michał!16:03
sdakethanks kfox111116:04
sdakehow the rest of this cycle will opertate is as follows16:04
akwasniethank you Steven for your hard work!16:04
rhalliseywoo16:04
sdakeuring ptl transitions, typically at election time  the successor ptl takes on rsponsibilities or summitand master16:04
rhalliseyyay inc016:04
sbezverkcongrats inc0! good sailing!16:04
sdakeand my responsibility for newton stays in place16:04
rhalliseyand ofcourse nice work sdake16:04
sdakethanks rhallisey16:05
duonghqthank steak for bootstrap kolla in 1st and 2nd cycle16:05
*** reedip has joined #openstack-meeting-416:05
sdakeduonghq its been 3 years dude ;)16:05
rhalliseysince Juno16:05
sdakeso back on track16:05
sdakelook to inc0 for leadership for master/summit/ocata/etc16:05
sdakelook to both of us for 3.0.0 - as far as I'm concerned its a bit of a joint responsibiity16:06
sdakefinally, I want to thank everyone in the community for supporting kolla16:06
sdakewithout you, kolla wouldn't exist16:06
sdakeor would exist in vastly different ways16:06
sdakekolla has created a turning point for openstack16:06
sdakethats a good thing ;)16:07
sdake#chair inc016:07
openstackCurrent chairs: inc0 sdake16:07
sdakeok inc0 - take it away16:07
inc0ok:) thanks sdake!16:07
sdakealso, i have a conflict right at this time, so I have to jet ;)16:07
sdakebut i'll be back in 45-50 mins16:07
inc0for all the hard work, I'll make sure to continue making kolla great, so we won't ever have to make it great again16:07
rhalliseyha16:07
sdakesbezverk also one point of clarificaiton, I am remaining on the core teeam going forward16:07
inc0#topic rc216:08
*** openstack changes topic to "rc2 (Meeting topic: kolla)"16:08
*** Julien-zte has quit IRC16:08
*** padkrish has joined #openstack-meeting-416:08
inc0ok, rc2 means we branch stable/netwon and open master to Ocata16:08
inc0this happends 10-13 Oct16:08
sbezverksdake: not sure the reason of your comments to me, I had no doubt you would stays as core ;-)16:09
inc0I'd like to target 10, but that depends on how many bugs and stuff we'll be able to fix16:09
inc0or more importantly, how many will stay16:09
inc0#link https://launchpad.net/kolla/+milestone/newton-rc216:10
*** wirehead_ has joined #openstack-meeting-416:10
pbourkeo/16:10
wirehead_o/16:10
duonghqo/16:10
kfox1111o/16:10
DavieySorry, what is this for?16:10
inc0take a look at this list, let's try to fix as much as we can in following 2 weeks16:10
inc0Daviey, these are bugs outstanding in Kolla targeted for RC-216:11
DavieyAh16:11
inc0reviewers, please prioritize reviews as bug priority goes16:11
*** thorst_ has joined #openstack-meeting-416:11
inc0besies that, we need lots of testing16:12
inc0if there is any bug you feel is important to be fixed in N, shout out to any of cores and let's triage/target it to RC216:12
inc0after that we release 3.0.016:12
inc0we still will backport bugfixes to stable branch, but let's make sure release is solid16:13
DavieyNot just kolla, but i kinda feel a few bugs have been introduced in the last couple of weeks across OpenStack.. We really need to bash out testing hard16:13
*** thorst has quit IRC16:13
pbourkeone point on this also, please do not merge any patches that are not high/critical for newton-216:13
inc0especially take a look at our release notes and 1. test what's there, new features and 2. if you see any feature missing from release notes, put a patch up please16:14
kfox1111inc0: I asked sdake, and I'll ask you. right before cutting the final rc2, can you please let me know and I'll run some regression tests against kolla-kubernetes just to make sure we don't introduce any bugs last minute.16:14
kfox1111we really need a gate test for that, and its in progress, but its kind of manual right now. :/16:14
*** ramishra has left #openstack-meeting-416:14
inc0kfox1111, sure, be extra careful when you put any patch to kolla itself16:14
rhalliseykfox1111, we don't have a release though16:15
inc0also please test it out as much as you can yourself:) deployment and such of kolla-ansible with your patch16:15
*** njohnston has quit IRC16:15
kfox1111inc0: sure.16:15
rhalliseyeven though we depend on kolla, we can just go off master16:15
rhalliseywell we have an N release16:15
rhalliseyeh not really16:15
kfox1111rhallisey: yeah, but I think we want to make sure trunk kolla-kubernetes works with released kolla 3.0.0,16:15
rhalliseylet's skip a release for N16:15
rhalliseymake the first release O16:15
*** njohnston has joined #openstack-meeting-416:16
inc0rhallisey, but if some regression gets introduced due to kolla-k8s required changes before we branch out, it's gonna be critical16:16
kfox1111as ocata is going to have a bunch of refactoring goin on to do the ansible split.16:16
*** mdnadeem_home has joined #openstack-meeting-416:16
kfox1111so we will want a stable target for a little while, which 3.0.0 can be.16:16
rhalliseythat's find16:16
rhalliseyfine16:16
rhalliseyI think it would be a problem16:16
inc0split will happen after we branch out stable16:16
rhalliseyand issue we hit will likely be hit on the kolla side16:16
rhalliseyamy*16:16
rhalliseyany*16:16
kfox1111yeah. so if we can target 3.0 and let the ansible split happen and settle out for a month or two,16:17
kfox1111then we can retarget to trunk again and both parts can make progress.16:17
rhalliseysure that works16:17
inc0bottom line everyone - extra careful testing16:17
kfox1111+1. :)16:17
inc0anyone wants to add anything?16:17
rhalliseykfox1111, it's going to be a bump road :)16:17
berendti think it makes sense to make the split in or a few days after barcelona16:17
wirehead_Even knowing "Hey, this worked in rc2 but broke" is going to eliminate wasted effort.16:17
inc0berendt, I'll talk with infra folks to make it seamless16:18
kfox1111berendt: hard to say... some advantage to getting it done before the summit so folks wont keep talking about it then.16:18
*** ddieterly is now known as ddieterly[away]16:18
rhalliseykfox1111, interesting opinion.  Either way works for me16:18
berendtkfox1111 makes sense16:18
inc0kfox1111, decision has been made, when we branch it out is just a workload issue16:18
kfox1111yeah.16:19
inc0it might require some git magic to retain history16:19
inc0anyway, moving on16:19
rhalliseyinc0, could be worth disccusing over beers or something our process for that16:19
inc0#topic summit session schedule16:19
*** openstack changes topic to "summit session schedule (Meeting topic: kolla)"16:19
inc0So thank you for answers in poll16:19
inc0https://etherpad.openstack.org/p/kolla-o-summit-schedule I took liberty of copying all the sessions from poll in order of votes16:20
inc0we have total of 9 design session (WR in etherpad) and 3 fishbowl16:20
Davieyinc0: I quite wanted a session about version numbering... I think there is potentially enough content to cover most of a session at least16:20
* britthouser is late16:20
britthouser0/16:20
*** zhubingbing has quit IRC16:21
*** aclark has joined #openstack-meeting-416:21
*** Guest46101 is now known as mgagne16:21
*** mgagne has quit IRC16:21
*** mgagne has joined #openstack-meeting-416:21
inc0as you can see, I didn't follow poll results 100%, also took liberty of adding 2 more sessions to the list, one about deprecation and stuff and second session for kolla-k8s16:21
inc0Daviey, we always have contributor meetup and beer track, we can discuss then too16:22
*** caowei has quit IRC16:22
rhalliseyDaviey, a doc for that would be awesome.  Agreed though16:22
*** njohnston has quit IRC16:22
*** ddieterly[away] is now known as ddieterly16:22
inc0so this is what I'm going to propose unless somebody is opposed to these ideas, so shoot away16:22
*** galstrom_zzz is now known as galstrom16:23
*** njohnston has joined #openstack-meeting-416:23
*** yamamoto has quit IRC16:23
inc0or if somebody have question regarding this schedule, please ask16:23
britthouserI was really hoping for baremetal to make the list16:23
britthouserit was nearly in the top9, and its a pretty new feature we just added.16:23
inc0britthouser, yes, although I'm not sure what we should talk about there16:24
berendtthat we do not work on monitoring is not good16:24
inc0ok, fact that we're not doing session doesn't mean we don't work on it16:24
*** njohnston has quit IRC16:25
*** AlanClark has quit IRC16:25
berendtyes of course, but i think it needs a wr..16:25
inc0sessions are for things we need to discuss, are contentious, aren't clear16:25
rhalliseywe can cover some of these topics in the roadmapping16:25
rhalliseyI think the roadmapping session will be a bit open16:25
rhalliseywe can also have backup topics of one of those topics don't use the whole time16:25
rhalliseybut I bet they will :)16:25
*** trozet has joined #openstack-meeting-416:25
berendtwhat is the focus of Security VMT threat?16:26
inc0berendt, so VMT is a team in OpenStack16:26
berendtyes.. but what will we do in the wr?16:26
inc0they started to analyze our projecxt in Austin16:26
inc0they will come to us and work with us to finish up this analyze16:26
berendtok16:26
*** padkrish has quit IRC16:27
inc0I wanted to keep it on schedule even tho it was pretty low in poll, because it's good to have them locally to finish up this work and get us vulnerability-managed tag16:27
rhalliseyya it's good to get that tag16:28
berendtyes that makes sense16:28
inc0Monitoring and Bare metal were ones that I thought are extremally important, but not much to discuss really (if you don't agree, do tell)16:28
inc0we have both features in Kolla in N, we need to fix it up, gather feedback and such16:28
*** anilvenkata has quit IRC16:29
inc0but what are questions we need to answer on sessions?16:29
berendti think the schedule is fine. we have to cover a lot of topics...16:29
berendtfor monitoring e.g. which monitoring tool we want to use, if we want to keep telegraf, ...16:29
inc0we always have couple unassigned hours in Friday16:29
britthouserI guess my thought as far as baremetal goes, is since its a new feature - go over what was done, get some feedback, discuss next steps, etc.  maybe that can be rolled into roadmap though?16:30
*** reedip has quit IRC16:30
*** limao has quit IRC16:30
*** thorst_ is now known as thorst16:30
britthouserYeah I think pencil it in for friday is fine with me.16:30
rhalliseybritthouser, ya agreed16:30
inc0britthouser, so what I'm sayin is that I doubt there will be much feedback to get16:30
*** njohnston has joined #openstack-meeting-416:30
rhalliseythere may not be, but we could talk about what to do next or somethign16:31
* rhallisey hasn't used it yet16:31
britthouserccccccfnnvlltgvvfcrllgbgthlhnubclilhbjeeciig16:31
inc0sure, so let's discuss what to drop for bare metal then16:31
rhalliseyanyway there will be plenty of *open time*16:31
britthouserccccccfnnvllfnvhltlffkhbnddgijcdhvntfgbvnfjv16:31
berendtwe voted and i think we should go with this schedule16:31
inc0lol16:31
rhalliseyinc0, nah keep the schedule16:31
berendtwe can discuss other topics on friday16:31
rhalliseyinc0, let's have baremetal and monitoring be the #1 and #2 backup topics16:32
rhalliseywe16:32
*** njohnston has quit IRC16:32
britthouser+116:32
inc0ok, so let's keep it for now, we don't need to submit it just now, so it still is open to slight changes (slight please)16:32
*** njohnston has joined #openstack-meeting-416:32
rhalliseyit will be apart of the *beer summit*16:32
*** dshakhray_ has quit IRC16:32
*** LotharKAtt has joined #openstack-meeting-416:32
inc0ok, moving on16:33
inc0#topic deprecation16:33
*** openstack changes topic to "deprecation (Meeting topic: kolla)"16:33
*** padkrish has joined #openstack-meeting-416:33
inc0so I wanted to move this topic in summit, hence my addition to schedule16:33
*** njohnston has quit IRC16:33
*** Swami_ has quit IRC16:34
*** njohnston has joined #openstack-meeting-416:34
inc0we decided to deprecate fedora in N and keep debian in16:34
sbezverkinc0: how about deprication of heka?16:34
inc0(can someone please take action item to add warning during build if fedora then deprecated?)16:34
inc0heka is another thing16:34
berendtinc0 already did it16:34
*** bobh_ has joined #openstack-meeting-416:34
inc0oh thank you16:34
*** baoli has quit IRC16:34
*** sshnaidm|afk is now known as sshnaidm16:34
berendt#link https://review.openstack.org/#/c/369184/16:35
inc0so here is thing, I'd like to put some sort of process behind decisions like that16:35
*** baoli has joined #openstack-meeting-416:35
*** njohnston has quit IRC16:35
inc0it might be as simple as documentation matrix of "what has CI and is super supported and what is not"16:35
inc0as distros and services goes16:35
inc0heka is different matter, let's talk about it after that16:36
*** armax has quit IRC16:36
britthouserI would use the word “maintained” instead of supported, but that sounds like a good idea16:36
sbezverkok, but we will talk right ;-)16:36
inc0yes, agree britthouser16:36
*** njohnston has joined #openstack-meeting-416:36
*** rpothier has left #openstack-meeting-416:36
inc0yes sbezverk thanks for bringing it up16:36
portdirecthi, sorry I've been away and just noticed this was going on :/16:37
*** njohnston has quit IRC16:37
britthouserand then have some rule, if bugs against that distro aren’t worked on in X months, then vote to deprecate.  something along those lines?16:37
inc0it will be more complicated than this16:37
inc0for example for distros we might require CI, but RHEL, although maintained and healthy won't have CI for license reasons16:38
Jeffrey4lhow about some distro is out of maintain for 1-2 cycle.16:38
inc0Jeffrey4l, what I mean is how do we define "maintain"16:38
*** njohnston has joined #openstack-meeting-416:38
*** njohnston has quit IRC16:38
inc0anyway, I don't expect us to answer it today16:38
britthouserYeah…I think we can work out that definition at summit.16:38
inc0just wanted to throw an idea for you to think about16:39
inc0and make a call at summit16:39
Jeffrey4lok16:39
britthouser+116:39
*** njohnston has joined #openstack-meeting-416:39
berendtwe also need this defintion also for services, not only for distros16:39
inc0I get lots of questions like "do you support ironic", answer is yes, but we'd lie if we'd say that we have same level of quality across every service we have16:39
inc0berendt, totally agree16:39
berendtat the moment we do not have a CI for most of our services, this has to be changed16:40
*** njohnston has quit IRC16:40
inc0I don't think we'll ever reach a spot when we'll have CI for everything we can deploy, Big tent is growing all the time16:40
Jeffrey4lci is one of the most thing we need set up in O cycle.16:40
*** njohnston has joined #openstack-meeting-416:40
britthouser+10016:40
inc0but we can just say openly what has CI and what doesn't16:40
berendt+infinity ;)16:40
egonzalez90+116:40
*** LotharKAtt has quit IRC16:41
inc0CI is in summit, agree totally;)16:41
inc0ok, moving on16:41
inc0#topic heka16:41
*** openstack changes topic to "heka (Meeting topic: kolla)"16:41
inc0sbezverk, can you please describe issue to everyone?16:41
*** njohnston has quit IRC16:42
*** njohnston has joined #openstack-meeting-416:42
*** haleyb_ has joined #openstack-meeting-416:42
inc0ok, I'll do it:) https://github.com/mozilla-services/heka16:43
inc0if you click the link there is big DEPRECATED work in the title16:43
inc0that's bad.16:43
inc0we need to look for alternatives16:43
berendtlogstash16:43
*** reedip has joined #openstack-meeting-416:43
britthousernuts!16:43
*** njohnston has quit IRC16:43
wirehead_Well, the promise for Hekka was that you'd get one fancy foofy daemon to do logs and metrics and alerts.16:43
kfox1111I think logstash is deprectated too in preference to filebeat?16:44
wirehead_As opposed to logstash + monitoring + metrics.16:44
kfox1111fluentd's an option too.16:44
berendts/logstash/filebeat/...16:44
*** njohnston has joined #openstack-meeting-416:45
berendtlet's open a blueprint "replace-heka"..?16:45
duonghq+1 berendt16:45
rhalliseyhow about "kill-heka"?16:45
inc0I'll write the bp16:45
wirehead_This is that intersection between the modern notion of a "12 factor app" and the way that OpenStack presently is.  From the Kolla-kube world, I'm kinda a bigger fan of not using a logging daemon inside of the contaienr at all.16:45
rhallisey:)16:45
*** njohnston has quit IRC16:45
berendtbecause we use elasticsearch for our logs i think it makes sense to go with them...16:45
inc0#action inc0 to write kill-heka bp16:45
rhalliseyinc0, hehe16:45
Jeffrey4lwirehead_, 12 factor app is ideal and reality is not.16:46
berendtwhat about https://review.openstack.org/#/c/375615/7 ?16:46
sbezverkfluentd16:46
britthouserSo are there things that we need for Heka to change, and we wont’ get those changes?16:46
berendti think it makes no sense to replace heka by something and to add fluentd as well16:46
britthouseror Heka works fine as is, but we don’t want to be on a dead code?16:46
sbezverkwe already used fluentd in kolla-kubernetes16:46
sbezverkwhy not to have more things in common than different ;-)16:46
rhalliseysbezverk, link to you fluentd patch??16:47
inc0also don't forget we'll need upgrade procedure for it16:47
*** njohnston has joined #openstack-meeting-416:47
*** njohnston has quit IRC16:47
rhalliseythere could be multiple ones here16:47
kfox1111with the way kolla lays out its log files,16:47
sbezverkhttps://review.openstack.org/37561516:47
britthouserI guess what I’m asking is, is heka broken today? or just a dead-end?16:47
kfox1111it really shouldn't matter if you use a heka container, or fluentd, or filebeat to do the uploading.16:47
pbourkebritthouser: dead end16:47
Jeffrey4ldead end16:47
inc0anyway, bp will be essential in Ocata, if somebody feel like taking it, we can discuss pros and cons of alternatives16:47
Jeffrey4lno one maintain the heka's code16:47
rhalliseyok if it's a dead end how about we leave it and provide an upgrade path16:48
britthouserOk good to know.  So its not hair of fire, but the sooner we make a u-turn the better.16:48
Davieysdake: Just reading scrollback... RH *could* do 3rd-party-ci, if they cared to test kolla.16:48
inc0but it does work so it's not *that* bad16:48
berendtheka has to be dropped, i think this has not to be discusses16:48
wirehead_Security patches, etc.16:48
rhalliseythey don't support it so let's not in the upcoming cycle16:48
*** ifat_afek has quit IRC16:48
inc0Daviey, well, 3rd party ci is more than just code16:48
inc0so let's not put them on the line16:49
kfox1111yeah. I think the discussion is not about keepign heka alive. just what to replace it with.16:49
Jeffrey4lberendt, +1 the really concern is which we choose.16:49
inc0we would need, however, call that one out16:49
Davieyinc0: I mean, if we wanted to have RH as a flavour we supported.. it could be 3rd party16:49
inc0but not having 3rd party ci shouldn't make them deprecated16:49
DavieyYes it should :)16:49
DavieyIf it isn't tested, we have to assume it doesn't wrk16:49
Davieywork*16:50
*** njohnston has joined #openstack-meeting-416:50
inc0so we might create something in between, like we have it, we think it works but not really tested by our CI16:50
inc0anyway, session on summit, we need to call these things out16:50
Davieythat way leads to madness16:50
berendtcan we finish the heka discussion first?16:50
inc0lots of moving parts16:50
kfox1111you could say its vendor supported, if thats the case?16:50
*** krtaylor has joined #openstack-meeting-416:50
britthouserwe’re on to a different topic Daviey, and we decided to define all that at summit16:50
inc0berendt, sure, sorry16:50
*** njohnston has quit IRC16:50
inc0ok, back to heka16:50
*** unicell1 has quit IRC16:50
DavieyWe are sticking with heka for Newton, right(!?)16:50
inc0I'm just going to propose bp, think of alternatives16:50
inc0we do16:51
inc0Neutron is done, only bugfixes16:51
berendtwhat about https://review.openstack.org/#/c/375615?16:51
*** njohnston has joined #openstack-meeting-416:51
inc0heka goes away in mitaka16:51
berendti would prefer to -2 this one until we have a decision16:51
inc0we might however mark it as deprecated16:51
inc0done berendt16:51
berendtinc0 we should mark it as deprecated right now, i think we do not need a mailing list vote for this deprecation16:51
inc0berendt, I think we don't need to vote16:52
*** njohnston has quit IRC16:52
inc0so yes, let's mark is as deprecated now16:52
berendtinc0 do you add a deprecation release note after opening the blueprint ?16:52
sbezverkinc0: I filed bp centralized-logging which could be used for logging discussion activities16:52
*** LotharKAtt has joined #openstack-meeting-416:52
berendtsbezverk centralized logging bp makes no sense because we already have centralized logging16:52
*** njohnston has joined #openstack-meeting-416:52
Jeffrey4lsbezverk, yes that name is confused.16:53
sbezverkJeffrey4l ok that can be changed16:53
Jeffrey4llet's move on? next topic?16:53
*** njohnston has quit IRC16:53
berendtsbezverk but this bp is not correct.. you wrote "bp to track activities around introducing fluentd as a replacement of heka in kolla"16:54
*** njohnston has joined #openstack-meeting-416:54
inc0I'll publish new bp16:54
berendtsbezverk we have not yet decided to use fluentd...16:54
inc0about heka16:54
*** banix has joined #openstack-meeting-416:54
Jeffrey4lkill-heka is nice ;)16:54
inc0and yes, I'd also would like to have some alternatives before we jump to fluentd16:54
sbezverkberendt: but we are :-) it is already running in kolla-kubernetes16:54
sbezverkand we need that image in kolla, if kolla continues provide us images16:54
berendtsbezverk but this does not mean that you need an ansible role for it, right?16:55
inc0sbezverk, berendt I'd love to have same logging architecture in both kollas:)16:55
inc0but let's make this educated decision16:55
*** njohnston has quit IRC16:55
inc0even if this means changing it in kolla-k8s16:55
*** njohnston has joined #openstack-meeting-416:55
sbezverkinc0: that is my point exactly why complicates things if we can have somehting common16:56
Jeffrey4lsbezverk, i think kolla can provide fluentd image. But Kolla may not use fluentd for collection logs.16:56
berendtyes but we have to discuss it first... we use E and K at the moment and they have there own tool16:56
sbezverkJeffrey4l: and that is perfectly fine at least for now16:56
berendtsbezverk yes.. but your review provides docker + ansible..16:56
sbezverkberendt: you do not have to use it16:56
inc0ok, hold on. We acknowledged problem, we discuss it now16:56
sbezverkit does not hart to have it right?16:57
inc0so let's first gather alternatives16:57
berendtsbezverk it does, we have to maintain it16:57
*** njohnston has quit IRC16:57
inc0I've heard at least 2 - fluentd and filebeat16:57
berendtwhy should we implement an ansible role for fluentd when we decide to use filebeat?16:57
*** njohnston has joined #openstack-meeting-416:57
Jeffrey4lsbezverk, please split the docker file and ansible playbook.16:57
sbezverkJeffrey4l: sure will do that16:57
inc0let's see if there is anything else, weigth pros and cons and push patches up when we make a decision16:57
inc0and ideally both kolla-ansible and kolla-k8s should have same logging stack16:58
*** bjolo has joined #openstack-meeting-416:58
Jeffrey4linc0, agreed16:58
inc0we have whole release to sort this out16:58
berendtdoes kolla-k8s uses elasticsearch and kibana?16:58
sbezverkyes16:58
rhalliseyyar16:58
inc0rhallisey, I think we ran out of time16:58
inc0sorry:(16:58
Davieyinc0: I wanted to squeeze in before the end of the meeting..... the performance monitoring stack seems to be in a sad state and not ready for release.  Is anyone else looking at it?16:58
rhalliseyno worries16:58
*** njohnston has quit IRC16:58
inc0we can overflow to our channel16:59
Jeffrey4limho, there is no alternative for elasticsearch and kibana16:59
rhalliseysure16:59
*** njohnston has joined #openstack-meeting-416:59
rhalliseywhat topics are left?16:59
sbezverkJeffrey4l +116:59
*** LotharKAtt has quit IRC16:59
inc0Daviey, what do you mean?16:59
berendttimeout...16:59
rhalliseyI'll quickly type kolla-kube update:16:59
inc0ok, we ran out of time:)16:59
inc0Daviey, let's talk on #openstac-kolla16:59
Daviey-> #openstack-kolla16:59
rhalliseyya let's jump over16:59
inc0thank you guys! I wanted to thank you again for your trust in me:)16:59
inc0and votes17:00
britthouser+1 inc0 :smiley:17:00
rhalliseywoot for kolla?17:00
inc0thanks Ryan. ofc woot for kolla please:)17:00
inc0woot:)17:00
rhalliseyyou promised!17:00
egonzalez90woot!!17:00
rhallisey:)17:00
rhalliseywoot :)17:00
duonghqwoot!!17:00
Jeffrey4lwoot!17:00
*** wirehead_ has left #openstack-meeting-417:00
sdakewh00000000t17:00
inc0#endmeeting kolla17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Wed Sep 28 17:00:35 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-09-28-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-09-28-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-09-28-16.00.log.html17:00
*** njohnston has quit IRC17:00
*** rhallisey has left #openstack-meeting-417:00
lrensing:) woot17:00
berendtsdake just in time ;)17:00
sdakeya my meeting just ended17:01
*** bjolo has left #openstack-meeting-417:01
*** lrensing has left #openstack-meeting-417:01
*** njohnston has joined #openstack-meeting-417:01
*** egonzalez90 has left #openstack-meeting-417:01
*** njohnston has quit IRC17:02
*** njohnston has joined #openstack-meeting-417:04
*** padkrish has quit IRC17:05
*** njohnston has quit IRC17:05
*** njohnston has joined #openstack-meeting-417:06
*** njohnston has quit IRC17:07
*** psachin has quit IRC17:08
*** njohnston has joined #openstack-meeting-417:08
*** njohnston has quit IRC17:08
*** duonghq has quit IRC17:08
*** hrito has quit IRC17:08
*** njohnston has joined #openstack-meeting-417:09
*** LotharKAtt has joined #openstack-meeting-417:11
*** ddieterly is now known as ddieterly[away]17:15
*** mdnadeem_home has quit IRC17:16
*** pbourke has quit IRC17:23
*** unicell has joined #openstack-meeting-417:23
*** yamamoto has joined #openstack-meeting-417:23
*** vhoward has joined #openstack-meeting-417:25
*** berendt has quit IRC17:27
*** pvaneck has joined #openstack-meeting-417:27
*** sc68cal_ is now known as sc68cal17:27
dougwigno lib meeting today17:28
*** sambetts is now known as sambetts|afk17:29
*** Swami has joined #openstack-meeting-417:31
*** yamamoto has quit IRC17:31
*** vhoward has quit IRC17:34
*** apuimedo|away is now known as apuimedo17:34
*** ralonsoh has quit IRC17:36
*** reedip has quit IRC17:38
*** iyamahat has quit IRC17:38
*** baoli has quit IRC17:39
*** baoli has joined #openstack-meeting-417:39
*** baoli has quit IRC17:40
*** trozet has quit IRC17:41
*** baoli has joined #openstack-meeting-417:41
*** LotharKAtt has quit IRC17:44
*** thorst has quit IRC17:45
*** thorst has joined #openstack-meeting-417:46
*** padkrish has joined #openstack-meeting-417:47
*** padkrish has quit IRC17:48
*** jimbaker` is now known as jimbaker17:48
*** padkrish has joined #openstack-meeting-417:49
*** padkrish has quit IRC17:50
*** padkrish has joined #openstack-meeting-417:51
*** reedip has joined #openstack-meeting-417:52
*** sshnaidm is now known as sshnaidm|afk17:53
*** iyamahat has joined #openstack-meeting-417:56
*** caboucha_ has joined #openstack-meeting-417:57
*** caboucha has quit IRC17:58
*** vishnoianil has quit IRC17:59
*** vhoward has joined #openstack-meeting-418:03
*** dshakhray_ has joined #openstack-meeting-418:05
*** ddieterly[away] is now known as ddieterly18:12
*** cartik has quit IRC18:12
*** berendt has joined #openstack-meeting-418:13
*** padkrish has quit IRC18:18
*** degorenko is now known as _degorenko18:20
*** portdirect has quit IRC18:20
*** zenoway has quit IRC18:22
*** zenoway has joined #openstack-meeting-418:23
*** iyamahat has quit IRC18:24
*** portdirect has joined #openstack-meeting-418:27
*** zenoway has quit IRC18:27
*** Jeffrey4l has quit IRC18:28
*** baoli has quit IRC18:28
*** krtaylor has quit IRC18:32
*** ddieterly is now known as ddieterly[away]18:33
*** salv-orlando has quit IRC18:34
*** woodster_ has quit IRC18:40
*** shasha_t_ is now known as shasha_tavil_18:40
*** yamahata has joined #openstack-meeting-418:43
*** shasha_tavil_ is now known as shasha_tavil18:44
*** sdake has quit IRC18:46
*** krtaylor has joined #openstack-meeting-418:48
*** cdelatte has joined #openstack-meeting-418:50
*** inc0 has quit IRC18:53
*** baoli has joined #openstack-meeting-418:56
*** banix has quit IRC18:59
*** DevonBoatwright has joined #openstack-meeting-419:00
*** DevonBoatwright has left #openstack-meeting-419:01
*** hogepodge has quit IRC19:01
*** spzala has quit IRC19:01
*** banix has joined #openstack-meeting-419:03
*** baoli has quit IRC19:05
*** baoli has joined #openstack-meeting-419:06
*** s3wong has joined #openstack-meeting-419:06
*** anilvenkata has joined #openstack-meeting-419:07
*** dtardivel has quit IRC19:07
*** berendt has quit IRC19:08
*** bobh_ has quit IRC19:10
*** bobh_ has joined #openstack-meeting-419:10
*** berendt has joined #openstack-meeting-419:12
*** yamahata has quit IRC19:13
*** ddieterly[away] is now known as ddieterly19:14
*** rstarmer has joined #openstack-meeting-419:20
*** rstarmer has quit IRC19:22
*** salv-orlando has joined #openstack-meeting-419:22
*** padkrish has joined #openstack-meeting-419:25
*** syjulian has quit IRC19:26
*** yohoffman has quit IRC19:26
*** jamemcc has quit IRC19:26
*** xenogear has quit IRC19:26
*** yohoffman has joined #openstack-meeting-419:27
*** spotz is now known as spotz_zzz19:27
*** jamemcc has joined #openstack-meeting-419:28
*** ifat_afek has joined #openstack-meeting-419:29
*** ifat_afek has quit IRC19:29
*** xenogear has joined #openstack-meeting-419:32
*** sdake has joined #openstack-meeting-419:34
*** haleyb_ has quit IRC19:35
*** ifat_afek has joined #openstack-meeting-419:39
*** banix has quit IRC19:39
*** syjulian has joined #openstack-meeting-419:40
*** salv-orl_ has joined #openstack-meeting-419:43
*** oanson has joined #openstack-meeting-419:45
*** ifat_afek has quit IRC19:46
*** salv-orlando has quit IRC19:46
*** iyamahat has joined #openstack-meeting-419:48
*** vhoward has quit IRC19:49
*** banix has joined #openstack-meeting-419:51
*** banix has quit IRC19:51
*** banix has joined #openstack-meeting-419:53
*** padkrish has quit IRC19:54
*** iyamahat has quit IRC19:55
*** padkrish has joined #openstack-meeting-419:55
*** banix has quit IRC19:55
*** padkrish has quit IRC19:55
*** padkrish has joined #openstack-meeting-419:56
*** padkrish has quit IRC19:56
*** padkrish has joined #openstack-meeting-419:58
*** spzala has joined #openstack-meeting-420:01
*** ducttape_ has joined #openstack-meeting-420:02
*** padkrish has quit IRC20:02
*** berendt has quit IRC20:04
*** padkrish has joined #openstack-meeting-420:04
*** spzala has quit IRC20:07
*** berendt has joined #openstack-meeting-420:07
*** salv-orl_ has quit IRC20:07
*** salv-orlando has joined #openstack-meeting-420:08
*** cdelatte has quit IRC20:08
*** ddieterly is now known as ddieterly[away]20:09
*** anilvenkata has quit IRC20:10
*** ddieterly[away] is now known as ddieterly20:17
*** oanson has quit IRC20:20
*** tonytan4ever has quit IRC20:23
*** padkrish has quit IRC20:28
*** LotharKAtt has joined #openstack-meeting-420:28
*** baoli has quit IRC20:29
*** haleyb_ has joined #openstack-meeting-420:32
*** ddieterly is now known as ddieterly[away]20:34
*** ddieterly[away] is now known as ddieterly20:34
*** haleyb_ has quit IRC20:36
*** rbak has quit IRC20:40
*** aclark has quit IRC20:41
*** berendt has quit IRC20:42
*** ddieterly is now known as ddieterly[away]20:43
*** padkrish has joined #openstack-meeting-420:43
*** padkrish has quit IRC20:44
*** padkrish has joined #openstack-meeting-420:46
*** caboucha_ has quit IRC20:48
*** spzala has joined #openstack-meeting-420:49
*** haleyb_ has joined #openstack-meeting-420:49
*** spzala has quit IRC20:53
*** dshakhray_ has quit IRC20:54
*** spotz_zzz is now known as spotz20:56
*** haleyb_ has quit IRC21:03
*** rtheis has quit IRC21:03
*** pvaneck has quit IRC21:04
*** spzala has joined #openstack-meeting-421:04
*** ddieterly[away] is now known as ddieterly21:06
*** yamahata has joined #openstack-meeting-421:06
*** baoli has joined #openstack-meeting-421:06
*** trozet has joined #openstack-meeting-421:09
*** woodard has quit IRC21:15
*** padkrish has quit IRC21:16
*** padkrish has joined #openstack-meeting-421:17
*** padkrish has quit IRC21:20
*** krtaylor has quit IRC21:21
*** tonytan4ever has joined #openstack-meeting-421:23
*** padkrish has joined #openstack-meeting-421:25
*** sdague has quit IRC21:27
*** cdelatte has joined #openstack-meeting-421:28
*** tonytan4ever has quit IRC21:28
*** hogepodge has joined #openstack-meeting-421:28
*** LotharKAtt has quit IRC21:29
*** yamahata has quit IRC21:35
*** iyamahat has joined #openstack-meeting-421:35
*** trozet has quit IRC21:36
*** spzala has quit IRC21:44
*** marst has quit IRC21:50
*** baoli has quit IRC21:53
*** cwolferh has left #openstack-meeting-421:54
*** baoli_ has joined #openstack-meeting-421:58
*** JRobinson__ has joined #openstack-meeting-422:03
*** padkrish has quit IRC22:03
*** baoli_ has quit IRC22:04
*** dtardivel has joined #openstack-meeting-422:05
*** padkrish has joined #openstack-meeting-422:07
*** marst has joined #openstack-meeting-422:07
*** padkrish has quit IRC22:07
*** padkrish has joined #openstack-meeting-422:08
*** lamt has quit IRC22:09
*** padkrish has quit IRC22:10
*** padkrish_ has joined #openstack-meeting-422:10
*** padkrish_ has quit IRC22:10
*** salv-orlando has quit IRC22:10
*** padkrish has joined #openstack-meeting-422:10
*** krtaylor has joined #openstack-meeting-422:10
*** klamath has quit IRC22:13
*** thorst has quit IRC22:13
*** baoli has joined #openstack-meeting-422:13
*** thorst has joined #openstack-meeting-422:14
*** baoli has quit IRC22:16
*** rbak has joined #openstack-meeting-422:16
*** thorst has quit IRC22:18
*** reedip has quit IRC22:21
*** ducttape_ has quit IRC22:22
*** tonytan4ever has joined #openstack-meeting-422:23
*** barmaley has joined #openstack-meeting-422:24
*** vishwanathj has quit IRC22:29
*** reedip has joined #openstack-meeting-422:32
*** thorst has joined #openstack-meeting-422:33
*** galstrom is now known as galstrom_zzz22:36
*** markvoelker has quit IRC22:36
*** thorst has quit IRC22:38
*** thorst has joined #openstack-meeting-422:38
*** limao has joined #openstack-meeting-422:42
*** thorst has quit IRC22:43
*** jovon has quit IRC22:46
*** thorst has joined #openstack-meeting-422:48
*** salv-orlando has joined #openstack-meeting-422:48
*** tonytan4ever has quit IRC22:51
*** salv-orlando has quit IRC22:52
*** thorst has quit IRC22:52
*** Swami has quit IRC22:53
*** sdake has quit IRC22:56
*** ddieterly has quit IRC22:59
*** bpokorny has joined #openstack-meeting-423:06
*** kbyrne has quit IRC23:06
*** bobh_ has quit IRC23:07
*** iyamahat has quit IRC23:07
*** woodard has joined #openstack-meeting-423:08
*** kbyrne has joined #openstack-meeting-423:08
*** hongbin has quit IRC23:10
*** spotz is now known as spotz_zzz23:12
*** padkrish has quit IRC23:18
*** ricolin has quit IRC23:31
*** sdake has joined #openstack-meeting-423:32
*** sdake_ has joined #openstack-meeting-423:35
*** iyamahat has joined #openstack-meeting-423:36
*** markvoelker has joined #openstack-meeting-423:37
*** sdake has quit IRC23:38
*** markvoelker has quit IRC23:41
*** padkrish has joined #openstack-meeting-423:45
*** zhurong has joined #openstack-meeting-423:46
*** woodard has quit IRC23:47
*** woodard has joined #openstack-meeting-423:47
*** woodard has quit IRC23:52
*** bobh_ has joined #openstack-meeting-423:59

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