Wednesday, 2016-11-23

*** yfauser has quit IRC00:00
*** haleyb_ has quit IRC00:02
*** klamath has quit IRC00:07
*** emagana has quit IRC00:14
*** Sukhdev has quit IRC00:16
*** spotz is now known as spotz_zzz00:28
*** limao has joined #openstack-meeting-400:35
*** Julien-zte has joined #openstack-meeting-400:42
*** sdake has quit IRC00:43
*** sdake has joined #openstack-meeting-400:45
*** Julien-zte has quit IRC00:50
*** Julien-z_ has joined #openstack-meeting-400:50
*** yfauser has joined #openstack-meeting-400:55
*** haleyb_ has joined #openstack-meeting-400:58
*** tovin07 has joined #openstack-meeting-400:59
*** tovin07 has quit IRC00:59
*** tovin07 has joined #openstack-meeting-401:00
*** yfauser has quit IRC01:00
*** tovin07 has quit IRC01:01
*** Julien-zte has joined #openstack-meeting-401:01
*** tovin07 has joined #openstack-meeting-401:01
*** tovin07 has quit IRC01:02
*** tovin07 has joined #openstack-meeting-401:02
*** Julien-z_ has quit IRC01:02
*** haleyb_ has quit IRC01:04
*** sdake has quit IRC01:05
*** sdake has joined #openstack-meeting-401:06
*** JRobinson__ is now known as JRobinson__afk01:07
*** tovin07_ has joined #openstack-meeting-401:15
*** xingchao has joined #openstack-meeting-401:16
*** zhurong has joined #openstack-meeting-401:19
*** sdake has quit IRC01:27
*** sdake has joined #openstack-meeting-401:29
*** Alagar has joined #openstack-meeting-401:31
*** JRobinson__afk is now known as JRobinson__01:34
*** dave-mccowan has joined #openstack-meeting-401:35
*** bobh has quit IRC01:35
*** woodard has quit IRC01:36
*** woodard has joined #openstack-meeting-401:36
*** sdake has quit IRC01:50
*** sdake has joined #openstack-meeting-401:53
*** syed__ has quit IRC01:56
*** yfauser has joined #openstack-meeting-401:56
*** haleyb_ has joined #openstack-meeting-401:59
*** haleyb_ has quit IRC02:04
*** xingchao has quit IRC02:05
*** dave-mcc_ has joined #openstack-meeting-402:11
*** dave-mccowan has quit IRC02:12
*** dave-mccowan has joined #openstack-meeting-402:13
*** bobh has joined #openstack-meeting-402:13
*** sdake has quit IRC02:14
*** sdake has joined #openstack-meeting-402:15
*** haleyb_ has joined #openstack-meeting-402:15
*** dave-mcc_ has quit IRC02:16
*** bpokorny_ has joined #openstack-meeting-402:16
*** yfauser has quit IRC02:16
*** syed__ has joined #openstack-meeting-402:17
*** hieulq has joined #openstack-meeting-402:18
*** dave-mccowan has quit IRC02:18
*** haleyb_ has quit IRC02:18
*** haleyb_ has joined #openstack-meeting-402:19
*** xingchao has joined #openstack-meeting-402:19
*** bpokorny has quit IRC02:19
*** bpokorny_ has quit IRC02:20
*** hieulq has quit IRC02:21
*** hieulq has joined #openstack-meeting-402:23
*** gongysh has joined #openstack-meeting-402:24
*** thorst has joined #openstack-meeting-402:32
*** thorst has quit IRC02:32
*** thorst has joined #openstack-meeting-402:33
*** sdake has quit IRC02:36
*** sdake has joined #openstack-meeting-402:37
*** dave-mccowan has joined #openstack-meeting-402:39
*** thorst has quit IRC02:40
*** thorst has joined #openstack-meeting-402:41
*** thorst has quit IRC02:45
*** asettle has joined #openstack-meeting-402:45
*** dave-mccowan has quit IRC02:48
*** bobh has quit IRC02:49
*** asettle has quit IRC02:50
*** yamamoto has joined #openstack-meeting-402:51
*** Alagar has quit IRC02:52
*** yamamoto has quit IRC02:52
*** JRobinson__ has quit IRC02:53
*** Alagar has joined #openstack-meeting-402:53
*** s3wong has quit IRC02:53
*** JRobinson__ has joined #openstack-meeting-402:53
*** Alagar has quit IRC02:55
*** bobh has joined #openstack-meeting-402:57
*** sdake has quit IRC02:57
*** Alagar has joined #openstack-meeting-402:58
*** sdake has joined #openstack-meeting-402:59
*** zhurong has quit IRC03:04
*** bobh has quit IRC03:04
*** zhurong has joined #openstack-meeting-403:07
*** thorst has joined #openstack-meeting-403:09
*** thorst has quit IRC03:10
*** yfauser has joined #openstack-meeting-403:13
*** bobh has joined #openstack-meeting-403:16
*** yfauser has quit IRC03:17
*** sdake has quit IRC03:19
*** sdake has joined #openstack-meeting-403:21
*** kylek3h_ has quit IRC03:24
*** kylek3h has joined #openstack-meeting-403:25
*** iyamahat has quit IRC03:27
*** kylek3h has quit IRC03:29
*** yamahata has quit IRC03:29
*** unicell has quit IRC03:34
*** zhurong has quit IRC03:35
*** zhurong has joined #openstack-meeting-403:36
*** thorst has joined #openstack-meeting-403:36
*** thorst has quit IRC03:37
*** sdake has quit IRC03:41
*** links has joined #openstack-meeting-403:42
*** sdake has joined #openstack-meeting-403:43
*** armax has quit IRC03:46
*** psachin has joined #openstack-meeting-403:52
*** JRobinson__ is now known as JRobinson__afk04:00
*** ricolin has joined #openstack-meeting-404:00
*** markvoelker has quit IRC04:02
*** bobh has quit IRC04:02
*** sdake has quit IRC04:03
*** sdake has joined #openstack-meeting-404:04
*** julim has quit IRC04:04
*** julim has joined #openstack-meeting-404:05
*** julim has quit IRC04:05
*** Julien-zte has quit IRC04:11
*** Julien-zte has joined #openstack-meeting-404:12
*** yfauser has joined #openstack-meeting-404:15
*** GB21 has joined #openstack-meeting-404:17
*** yfauser has quit IRC04:20
*** yamamoto has joined #openstack-meeting-404:21
*** haleyb_ has quit IRC04:22
*** GB21 has quit IRC04:22
*** yamamoto has quit IRC04:23
*** Alagar has quit IRC04:24
*** sdake has quit IRC04:25
*** kylek3h has joined #openstack-meeting-404:25
*** sdake has joined #openstack-meeting-404:28
*** yamahata has joined #openstack-meeting-404:29
*** kylek3h has quit IRC04:30
*** yfauser has joined #openstack-meeting-404:34
*** GB21 has joined #openstack-meeting-404:34
*** yuli_s has quit IRC04:38
*** mhayden has quit IRC04:38
*** yfauser has quit IRC04:39
*** yamahata has quit IRC04:43
*** Alagar has joined #openstack-meeting-404:44
*** julim has joined #openstack-meeting-404:45
*** sdake has quit IRC04:49
*** julim has quit IRC04:50
*** mhayden has joined #openstack-meeting-404:50
*** yuli_s has joined #openstack-meeting-404:51
*** sdake has joined #openstack-meeting-404:52
*** yamamoto has joined #openstack-meeting-404:54
*** yamamoto has quit IRC04:54
*** JRobinson__afk is now known as JRobinson__05:03
*** yamahata has joined #openstack-meeting-405:05
*** Jeffrey4l has quit IRC05:06
*** unicell has joined #openstack-meeting-405:14
*** julim has joined #openstack-meeting-405:16
*** Alagar has quit IRC05:16
*** prateek has joined #openstack-meeting-405:18
*** Alagar has joined #openstack-meeting-405:20
*** julim has quit IRC05:21
*** unicell has quit IRC05:26
*** kylek3h has joined #openstack-meeting-405:26
*** unicell has joined #openstack-meeting-405:26
*** kylek3h has quit IRC05:31
*** sdake_ has joined #openstack-meeting-405:31
*** trinaths has joined #openstack-meeting-405:34
*** sdake has quit IRC05:35
*** anilvenkata has joined #openstack-meeting-405:49
*** gongysh has quit IRC05:49
*** cathrichardson has quit IRC05:49
*** cathrichardson has joined #openstack-meeting-405:50
*** Alagar has quit IRC05:52
*** yamamoto has joined #openstack-meeting-406:02
*** markvoelker has joined #openstack-meeting-406:02
*** markvoelker has quit IRC06:08
*** Alagar has joined #openstack-meeting-406:12
*** ricolin has quit IRC06:17
*** vishnoianil has quit IRC06:17
*** yfauser has joined #openstack-meeting-406:24
*** janki has joined #openstack-meeting-406:26
*** kylek3h has joined #openstack-meeting-406:27
*** vishnoianil has joined #openstack-meeting-406:30
*** kylek3h has quit IRC06:31
*** ricolin has joined #openstack-meeting-406:34
*** yamamoto has quit IRC06:34
*** karthiks has quit IRC06:42
*** yamamoto has joined #openstack-meeting-406:43
*** yamamoto has quit IRC06:43
*** ricolin has quit IRC06:46
*** yamamoto has joined #openstack-meeting-406:51
*** karthiks has joined #openstack-meeting-406:56
*** yamamoto has quit IRC06:57
*** Alagar has quit IRC07:12
*** Alagar has joined #openstack-meeting-407:12
*** numans has joined #openstack-meeting-407:17
*** nkrinner_afk is now known as nkrinner07:17
*** nkrinner has quit IRC07:19
*** GB21 has quit IRC07:21
*** nkrinner has joined #openstack-meeting-407:24
*** kylek3h has joined #openstack-meeting-407:28
*** nkrinner has quit IRC07:29
*** nkrinner has joined #openstack-meeting-407:30
*** kylek3h has quit IRC07:32
*** yamahata has quit IRC07:39
*** zenoway has joined #openstack-meeting-407:39
*** ifat_afek has joined #openstack-meeting-407:49
*** idan_hefetz has joined #openstack-meeting-407:49
*** eyalb has joined #openstack-meeting-407:49
*** GB21 has joined #openstack-meeting-407:53
*** nadav has joined #openstack-meeting-407:54
*** danoffek has joined #openstack-meeting-407:54
*** alexey_weyl has joined #openstack-meeting-407:55
*** matrohon has joined #openstack-meeting-407:56
ifat_afek#startmeeting vitrage08:00
openstackMeeting started Wed Nov 23 08:00:25 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:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:00
*** openstack changes topic to " (Meeting topic: vitrage)"08:00
openstackThe meeting name has been set to 'vitrage'08:00
ifat_afekHi everyone :-)08:00
eyalbhi08:00
idan_hefetzHi08:00
danoffekHi guys08:01
*** alexey_weyl has quit IRC08:01
danoffekI'd like to update first08:01
danoffekIt's been a few weeks since the summit.08:01
nadavhi08:02
danoffekWe've had a very good Vitrage lab going there08:02
*** nbloom has joined #openstack-meeting-408:02
nbloomhi :)08:02
danoffekstill, we can't see any recording of the lab, even though we've been informed that all the labs were recorded.08:02
danoffekWe can see all the recordings of the labs in the adjacent room.08:03
danoffekWe've sent mails to representatives of the summit, but we didn't get any response yet.08:03
danoffekDoes anyone knows of a responsive contact / what is going on with recordings on Barcelona OpenStack Summit Ballroom B ?08:04
danoffekThanks.08:04
*** yifei has quit IRC08:04
ifat_afekdanoffek: I’ll do my best to help. Not sure who else we can email, but I’ll try to search someone08:05
*** yifei has joined #openstack-meeting-408:05
danoffekThanks. Maybe another IRC ?08:05
ifat_afekI don’t know if there is any relevant IRC. But may try to find out08:05
*** syed__ has quit IRC08:06
danoffekSome other project who found answerd...08:06
ifat_afekor maybe we can email the lecturers of the other sessions that were in that room08:06
danoffekanswers08:06
danoffekThat's a good idea.08:06
danoffekThanks.08:06
danoffekI'll look in that direction.08:06
ifat_afekOk08:06
*** ad_rien_ has joined #openstack-meeting-408:06
ifat_afek#topic Status and Updates08:06
*** openstack changes topic to "Status and Updates (Meeting topic: vitrage)"08:06
ifat_afekVitrage official documentations was updated, both the developer guide and the specs. Have a look:08:07
ifat_afek#link http://docs.openstack.org/developer/vitrage/08:07
ifat_afek#link http://specs.openstack.org/openstack/vitrage-specs/08:07
ifat_afekThanks tovin07 for your help!08:07
ifat_afekI know there are still things to be improved in the documentation (e.g. in the specs there is Mitaka, Newton and Newton…). Will try to do it later this week.08:07
*** yamamoto has joined #openstack-meeting-408:08
ifat_afekWho else wants to update?08:08
idan_hefetzI will update08:08
idan_hefetzWe had a problem at the gate due to change of mysql version in the aodh08:09
idan_hefetzwe have changed the image on which we run the tempests to xenial so it will be with the new mysql version08:09
idan_hefetzthen we had another problem with the heat datasource tempest08:10
idan_hefetzwhen we try to connect to the heatclient it tells us that we have no endpoint.08:10
*** JRobinson__ has quit IRC08:11
idan_hefetzWe need to find out the correct / new way to connect to heatclient, and thats why so far we have put the tempests heat datasource to ignore.08:11
*** berendt has joined #openstack-meeting-408:12
idan_hefetzIf someone can, he is more then welcome to find a solution for this problem, otherwise we will update it soon.08:12
idan_hefetzAfter that I ahve rechecked all of the commits in gerrit.08:12
idan_hefetzThats it for now (alexey)08:12
ifat_afekidan_hefetz: are we the only project that experienced this problem with mysql? or is it a known issue?08:13
idan_hefetzwe aren't the only one. another project that had the same issue for example is congress.08:13
idan_hefetzthe have done the same changed that we did with the gate image08:14
ifat_afekmakes sense, they also have an aodh datasource08:14
ifat_afekok, great08:14
idan_hefetzyeppppp08:14
ifat_afekidan_hefetz: thanks!08:14
ifat_afekAny other update?08:14
ifat_afekok, that was a short meeting :-)08:15
ifat_afekGoodbye everyone08:16
eyalbbye08:16
nbloombye08:16
ifat_afek#endmeeting08:16
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:16
openstackMeeting ended Wed Nov 23 08:16:27 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:16
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-11-23-08.00.html08:16
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-11-23-08.00.txt08:16
openstackLog:            http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-11-23-08.00.log.html08:16
*** idan_hefetz has left #openstack-meeting-408:16
*** eyalb has left #openstack-meeting-408:16
*** nbloom has quit IRC08:16
*** diga has joined #openstack-meeting-408:18
*** yamamoto has quit IRC08:19
*** ralonsoh has joined #openstack-meeting-408:20
*** iyamahat has joined #openstack-meeting-408:20
*** derekjhyang has quit IRC08:21
*** yamamoto has joined #openstack-meeting-408:23
*** kylek3h has joined #openstack-meeting-408:28
*** yamamoto has quit IRC08:29
*** yamamoto has joined #openstack-meeting-408:30
*** kylek3h has quit IRC08:33
*** yamamoto has quit IRC08:35
*** yujunz has joined #openstack-meeting-408:40
*** dtardivel has joined #openstack-meeting-408:41
*** brunograz has joined #openstack-meeting-408:46
*** Alagar has quit IRC08:48
*** makowals has quit IRC08:49
*** makowals_ has joined #openstack-meeting-408:49
*** robputt has quit IRC08:50
*** alexchadin has joined #openstack-meeting-408:51
*** Yumeng has joined #openstack-meeting-408:58
*** seanmurphy has joined #openstack-meeting-408:59
acabot#startmeeting watcher09:00
openstackMeeting started Wed Nov 23 09:00:32 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
dtardivelhi09:00
brunograzo/09:00
seanmurphyhi guys09:00
Yumenghi09:00
acaboteurope is awake ;-)09:01
*** gongysh has joined #openstack-meeting-409:01
*** yujunz has left #openstack-meeting-409:01
acabotagenda for today #link https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#11.2F23.2F201609:01
seanmurphyi guess the us is preparing for thanksgiving ;-)09:01
acabotseanmurphy : for sure09:01
*** hanrong has joined #openstack-meeting-409:01
*** diga has quit IRC09:02
acabotso lets start09:02
acabot#topic Announcements09:02
*** openstack changes topic to "Announcements (Meeting topic: watcher)"09:02
acabot#info python-watcher v0.32 & python-watcherclient v0.26 & watcher-dashboard v0.6 have been released for ocata-1 on November 18th09:02
acabotthx everyone for meeting the deadline09:03
acabot#info recap for Barcelona has been sent09:03
acabot#link http://lists.openstack.org/pipermail/openstack-dev/2016-November/107623.html09:03
acabotdo not hesitate to answer the thread if something is missing09:03
acabot#info a discussion has been started regarding the way we should validate Watcher strategies09:03
acabot#link http://lists.openstack.org/pipermail/openstack-dev/2016-November/107402.html09:04
acabotthis is an important issue so feel free to send your thoughts about it09:04
acaboton the ML09:04
acabot#info acabot didn't has the time to prepare the trello board for the meeting09:04
acabotsorry for that, I will do it next week09:05
alexchadinhello everyone09:05
acabothello alex09:05
acabot#info acabot presented Watcher & our big tent journey on November 22nd @openstackdayfrance201609:05
*** asettle has joined #openstack-meeting-409:05
acabotI had 40 attendees09:05
alexchadingreat!09:06
acabot#info your OSIC cluster request for testing Watcher has been rejected09:06
dtardivelacabot: why ?09:06
acabotthey ask us to request a bare metal env instead of an openstack already deployed09:06
seanmurphywell done on the openstack france presentation09:06
acabotand I dont really want to have to configure OpenStack for our tests09:07
seanmurphycan we get some usage info from osic so we could estimate what gains could be made?09:07
acabotseanmurphy : I need to check that with sballe09:08
acabotseanmurphy : as I dont really know what metrics we can get09:08
acabotmy main concern is to take 2 weeks to have an openstack ready with monasca deployed...09:08
seanmurphyone idea that i thought might make sense - (I mentioned it in barca) - was if watcher could publish some usage data from some real systems as a driver for showing what gains are possible09:09
acabotand we can have a cluster for a month max09:09
acabotseanmurphy : yes this is something we planned to do before Barcelona, with the Intel cluster09:09
*** iyamahat has quit IRC09:09
acabotseanmurphy : unfortunately it took 7 weeks to have openstack & watcher ready !09:10
seanmurphyhaha - things always take longer than planned ;-)09:10
acabotseanmurphy : so we stopped the experimentation falling back on OSIC node with an openstack already deployed09:10
acabotseanmurphy : but as I said, they want us to deploy openstack as well...09:11
alexchadinacabot: how much servers?09:11
acabotalexchadin : we can have 132 nodes or 66 nodes cluster09:12
*** diga has joined #openstack-meeting-409:12
acabotI would suggest to work on improving watcher code until christmas and then ask for a testing env in january09:12
acabotI will check with Intel if they can handle the openstack deployment on the OSIC cluster09:13
dtardivelacabot: from  my point of view, we have no choice, we have to run watcher within a medium cluster size, to be able to demonstrate the real gains with watcher09:13
acabotdtardivel : I agree but on bcom side, we wont be able to work on an openstack deployment on OSIC before Xmas09:14
dtardivelacabot: could we find some guys in our teams ready to help us to deploy a OS for our aims ?09:14
acabot#action acabot check with Intel if they could set up a new test environment for Watcher09:15
acabotdtardivel : I will try to find some09:15
alexchadindtardivel: I have 2 years experience with deploying openstack09:15
alexchadinbut only on very small cluster09:15
alexchadin4-5 machines09:15
*** tmetsch has joined #openstack-meeting-409:15
dtardivelalexchadin: 8 machines for me :)09:15
alexchadinwithout automation tools like ansible, vagrant so on09:16
acabotI think configuring Newton on a 66 nodes env is not that easy ;-)09:16
alexchadinwe need some tools to automate it09:16
alexchadinlike fuel09:16
acabots/Newton/Neutron09:16
alexchadinbut it is in nearly dead state09:16
acabotlet me ask for help next week09:17
acabot#topic Review Action Items09:17
*** openstack changes topic to "Review Action Items (Meeting topic: watcher)"09:17
acabotWatcher specs09:17
acabotautomatic triggering of action plans for AUDIT should now be reviewed and merged09:17
acabot#link https://review.openstack.org/#/c/342473/09:17
acabotalexchadin diga : can we merge it ?09:18
alexchadinI think yes09:18
alexchadin+2 from me09:18
acabotdiga ?09:18
digahi09:18
acabotdiga : can we merge your spec ?09:19
acabotnothing to add ?09:19
digaacabot: yesm we can merge the spec09:19
acabotok thx09:19
acabot#action acabot sballe review and merge https://review.openstack.org/#/c/342473/09:19
acabotDefine grammar for workload characterization needs a new PS09:19
acabot#link https://review.openstack.org/#/c/377100/09:19
acabotthx seanmurphy for your comments09:20
acabot#action hvprash answer comments on https://review.openstack.org/#/c/377100/09:20
acabotDefine when an action plan is stale/invalid needs final reviews from cores09:20
acabot#link https://review.openstack.org/#/c/386293/09:20
acabotI think this spec looks good09:20
acabotanyone wants to review it before merging ?09:21
acabot#action acabot sballe review and merge https://review.openstack.org/#/c/386293/09:21
hanrong+109:21
acabot#action hanrong review and merge https://review.openstack.org/#/c/386293/09:21
acabothi hanrong ;-)09:21
hanronghi, :-D09:21
acabotAudit tag in VM Metadata needs reviews09:22
acabot#link https://review.openstack.org/#/c/391374/09:22
acabotvincentfrancoise did a great addition to this spec09:22
acabotanyone wants to review it ?09:22
acabotI think its now complete09:23
dtardivelacabot: i think vincentfrancoise forgot to update this spec with our latest comments. I will do it.09:23
acabotdtardivel : PS 5 ?09:23
alexchadinI'd like to review it09:23
dtardivelyes i think so. I will check.09:23
acabot#action alexchadin acabot review https://review.openstack.org/#/c/391374/09:23
acabotAdd improvements to the planner and workflow mechanisms needs reviews09:24
acabot#link https://review.openstack.org/#/c/385871/09:24
acabotwe talked about splitting this spec in 209:24
acabotdtardivel : did you talked with alexchadin about it ?09:24
*** _degorenko|afk is now known as degorenko09:25
alexchadinacabot: I talked with vincent about it09:25
seanmurphyi can review 38587109:25
alexchadinseanmurphy: I appreciate it!09:25
dtardivelacabot: no, this is the position of vincentfrancoise.09:25
alexchadinacabot: In this spec I've described only the first part of BP09:26
acabotalexchadin : ok so should we update the BP description  and add a new one ?09:26
dtardivelalexchadin: so only the data model impact ?09:26
alexchadinacabot: the second one, about modifying Applier, would be in the next spec.09:26
*** sshnaidm|away is now known as sshnaidm09:26
acabotseanmurphy : let me check is the scope is ok before reviewing09:26
alexchadindtardivel: yes, but we cannot merge it without the second part:)09:27
acabotalexchadin : lets discuss this on our channel09:27
alexchadinso, these two specs cannot exists without each other09:27
acabot#action dtardivel alexchadin acabot sync on openstack-watcher about https://review.openstack.org/#/c/385871/09:28
acabotMoving to Watcher code09:28
dtardivelalexchadin: from vincentfrancoise point of view, we should be able to update the data model and the way the planner will handle new model to make the action plan, without impacting the applier09:28
acabotwatcher-notifications-ovo & audit-versioned-notifications-api merged09:29
acabotDocumentation for Outlet Temperature Based Strategy looks good and will be merged soon09:29
acabot#link https://review.openstack.org/#/c/397411/09:29
acabotis it the last doc strategy ?09:29
*** kylek3h has joined #openstack-meeting-409:29
acabotdtardivel : do we still have strategies without doc ?09:30
dtardivelacabot: not sure09:30
dtardivelacabot: let me check09:30
acabot#action dtardivel check if we have all our strategies documented09:31
acabotcentralise config options need reviews09:31
acabot#link https://review.openstack.org/#/q/status:open+project:openstack/watcher+branch:master+topic:bp/centralise-config-opts09:31
acabotwho wants to review this ?09:31
dtardivel+109:31
hanrong+109:31
acabot#action dtardivel hanrong review https://review.openstack.org/#/q/status:open+project:openstack/watcher+branch:master+topic:bp/centralise-config-opts09:31
*** markvoelker has joined #openstack-meeting-409:32
*** revon has quit IRC09:32
acabotcheck the state of action plan needs a new PS09:32
acabot#link https://review.openstack.org/#/c/391383/09:32
acabot#action licanwei answer comments on https://review.openstack.org/#/c/391383/09:32
acabotWatcher CLI09:33
acabotAdd functional tests to watcherclient needs reviews09:33
acabot#link https://review.openstack.org/#/c/389181/09:33
dtardivel+109:33
acabot#action dtardivel review https://review.openstack.org/#/c/389181/09:33
acabot#topic Blueprint/Bug Review and Discussion09:33
*** openstack changes topic to "Blueprint/Bug Review and Discussion (Meeting topic: watcher)"09:33
*** yifei has quit IRC09:33
acabot#info Ocata-2 is our current target due December 12th09:33
acabot#link https://launchpad.net/watcher/+milestone/ocata-209:34
*** kylek3h has quit IRC09:34
*** Julien-zte has quit IRC09:34
dtardivelacabot: uniform airflow strategy is not documented09:34
acabotnishi's strategy09:35
acabotI will ask sballe09:35
acabot#action acabot ask sballe for documenting airflow strategy09:35
acabotfor ocata-2, we have 9 BPs targeted09:36
acabotplease update the delivery field if you already started implementing09:36
acabothanrong : did you start https://blueprints.launchpad.net/watcher/+spec/dynamic-action-description ?09:36
hanrongyes09:36
*** markvoelker has quit IRC09:37
hanronghttps://review.openstack.org/#/c/401111/09:37
acabothanrong : ops sorry I missed it09:37
hanrongI submitted today09:37
acabotok ;-)09:37
dtardivel36 min ago ;)09:38
hanrongneed more discussion09:38
acabotok09:39
acabot#topic Open discussions09:39
*** openstack changes topic to "Open discussions (Meeting topic: watcher)"09:39
dtardivelhanrong: I will read your proposition09:39
acabot#undo09:39
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x7fbb93d2fc10>09:39
acabot#action dtardivel review https://review.openstack.org/#/c/401111/09:39
acabot#topic Open discussions09:40
*** openstack changes topic to "Open discussions (Meeting topic: watcher)"09:40
acabotI dont have any topic to discuss today09:40
acabotanyone wants to open one ?09:40
YumengI can also do review for https://review.openstack.org/#/c/401111/09:40
acabot#action Yumeng review https://review.openstack.org/#/c/401111/09:40
*** ifat_afek has left #openstack-meeting-409:41
*** diga_ has joined #openstack-meeting-409:41
seanmurphywe have been setting up monasca to understand resource consumption09:41
seanmurphyas sballe suggested at barca meeting09:41
seanmurphyit’s a pita!09:42
acabotseanmurphy : :-)09:42
seanmurphybrunograz put up a blog post on it09:42
acabotplease share it09:42
seanmurphywe’re now thinking that prometheus is a better option09:42
*** diga has quit IRC09:42
brunograz#link https://blog.zhaw.ch/icclab/installing-monasca-a-happy-ending-after-much-sadness-and-woe/09:42
alexchadinseanmurphy: hi:)09:42
acabotI heard also yesterday that prometheus is probably the best option today for monitoring09:42
alexchadinI read your post yesterday and leaved some comments09:43
seanmurphyinterestingly, it seems to have little support so far for openstack09:43
seanmurphycanonical are working on it afaik09:43
seanmurphyanyway - it’s just a ‘by the way’ - not core to watcher, i guess but relevant09:43
seanmurphywe did bounce around the idea of embedded a grafana dashboard into watcher on horizon09:44
seanmurphybut we will see how doable it might be09:44
acabotok09:44
acabotso thx everyone09:45
acabothave a good day/evening09:45
dtardivelpromotheus is available on dockey hub: #link https://hub.docker.com/r/prom/prometheus09:45
dtardivels/dockey/docker09:45
seanmurphydockey hub - i like it ;-)09:45
seanmurphyyeah - it took 10 mins to set up prometheus to play with09:46
seanmurphyvs days for monasca09:46
acabot#09:46
* acabot not surprised ;-)09:46
acabotthx09:47
acabot#endmeeting09:47
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:47
openstackMeeting ended Wed Nov 23 09:47:22 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-11-23-09.00.html09:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-11-23-09.00.txt09:47
openstackLog:            http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-11-23-09.00.log.html09:47
*** brunograz has left #openstack-meeting-409:47
*** tmetsch has left #openstack-meeting-409:50
*** alexchadin has quit IRC09:57
*** alexchadin has joined #openstack-meeting-409:57
*** alexchad_ has joined #openstack-meeting-409:57
*** alexchadin has quit IRC09:58
*** zhurong has quit IRC10:01
*** tovin07_ has quit IRC10:06
*** Yumeng has quit IRC10:06
*** yfauser has quit IRC10:12
*** yfauser has joined #openstack-meeting-410:13
*** gongysh has quit IRC10:15
*** limao has quit IRC10:17
*** yfauser has quit IRC10:17
*** limao has joined #openstack-meeting-410:17
*** julim has joined #openstack-meeting-410:21
*** limao has quit IRC10:22
*** sambetts|afk is now known as sambetts10:24
*** julim has quit IRC10:25
*** numans has quit IRC10:30
*** yifei has joined #openstack-meeting-410:32
*** numans has joined #openstack-meeting-410:33
*** pkoniszewski has quit IRC10:35
*** isq has quit IRC10:35
*** yifei has quit IRC10:36
*** alexchad_ has quit IRC10:37
*** alexchadin has joined #openstack-meeting-410:37
*** alexchadin has quit IRC10:42
*** pkoniszewski has joined #openstack-meeting-410:44
*** ddellav has quit IRC10:46
*** xingchao has quit IRC10:47
*** mfedosin has quit IRC10:47
*** xingchao has joined #openstack-meeting-410:49
*** mfedosin has joined #openstack-meeting-410:50
*** ddellav has joined #openstack-meeting-410:52
*** xingchao has quit IRC10:55
*** ativelkov has quit IRC11:01
*** ativelkov has joined #openstack-meeting-411:03
*** numans has quit IRC11:13
*** yfauser has joined #openstack-meeting-411:13
*** GB21 has quit IRC11:14
*** Jeffrey4l has joined #openstack-meeting-411:14
*** igordcard has quit IRC11:14
*** igordcard has joined #openstack-meeting-411:15
*** yfauser has quit IRC11:17
*** ad_rien_ has quit IRC11:18
*** GB21 has joined #openstack-meeting-411:30
*** kylek3h has joined #openstack-meeting-411:34
*** prateek has quit IRC11:37
*** kylek3h has quit IRC11:39
*** numans has joined #openstack-meeting-411:42
*** yfauser has joined #openstack-meeting-411:43
*** robputt has joined #openstack-meeting-411:45
*** yfauser has quit IRC11:48
*** diga_ has quit IRC11:48
*** robputt has quit IRC11:50
*** trinaths has quit IRC11:55
*** yfauser has joined #openstack-meeting-412:03
*** GB21 has quit IRC12:05
*** prateek has joined #openstack-meeting-412:05
*** seanmurphy has quit IRC12:06
*** prateek has quit IRC12:07
*** prateek has joined #openstack-meeting-412:08
*** prateek has quit IRC12:10
*** GB21 has joined #openstack-meeting-412:12
*** gongysh has joined #openstack-meeting-412:15
*** prateek has joined #openstack-meeting-412:17
*** gongysh has quit IRC12:17
*** GB21 has quit IRC12:17
*** prateek has quit IRC12:17
*** prateek has joined #openstack-meeting-412:18
*** zenoway has quit IRC12:21
*** zenoway has joined #openstack-meeting-412:21
*** prateek has quit IRC12:24
*** prateek has joined #openstack-meeting-412:25
*** zenoway has quit IRC12:25
*** rtheis has joined #openstack-meeting-412:26
*** rtheis has quit IRC12:26
*** nadav has quit IRC12:30
*** kylek3h has joined #openstack-meeting-412:36
*** kylek3h has quit IRC12:40
*** alexchadin has joined #openstack-meeting-412:41
*** GB21 has joined #openstack-meeting-412:43
*** kylek3h has joined #openstack-meeting-412:52
*** links has quit IRC12:54
*** danoffek has left #openstack-meeting-412:54
*** claudiub has joined #openstack-meeting-412:57
alex_xu#startmeeting nova api13:00
openstackMeeting started Wed Nov 23 13:00:04 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
*** cdent has joined #openstack-meeting-413:00
cdento/13:01
alex_xucdent: good to see you get well13:01
cdentThanks. I'm not 100% yet but bored, so getting on irc is a thing to do :)13:02
alex_xuemmm....holiday weeks13:03
cdentindeed13:03
alex_xuactually only thing want to talk about is about spec https://review.openstack.org/393205, people get different opionion, probably i will reach johnthetubaguy later to ensure what we should now13:04
cdentI tend to agree with jay: remove the vectors for bad13:05
* johnthetubaguy wonders in late13:05
alex_xujohnthetubaguy: ah, just talk about https://review.openstack.org/#/c/393205/13:06
*** GB21 has quit IRC13:06
alex_xucdent also tend to jay13:06
johnthetubaguyI think my problem is that "bad" is relative, in small deployments those queries are quite quick, and folks might be counting on them13:06
alex_xuyea, i'm more afraid to break the api, so tend to johnthetubaguy13:06
johnthetubaguyI wonder if we just make it safe by default, i.e. policy stops them by default?13:07
johnthetubaguybut folks that rely on them can restore the API, if needed13:07
alex_xujohnthetubaguy: after we have capabilities discovery?13:07
johnthetubaguyalthough, that feels a bit like over-engineering13:07
cdenti was just gonna say that13:07
johnthetubaguyalex_xu: I am thinking before we have it, just afterwards it could be discoverable13:07
johnthetubaguywe got direct feedback on this at the summit, from operators saying don't break my searching13:08
*** zenoway has joined #openstack-meeting-413:08
johnthetubaguythats what really worry, feels like we are just ignoring them13:08
johnthetubaguy... at the same time, we should protect our users from cutting their legs off13:09
alex_xuis it worth an email to get board discussion?13:10
cdentI can't remember we were debating the user query or just the admin query13:10
cdentit seems that on the admin side, perhaps enough rope to hang yourself is okay?13:10
johnthetubaguythats where I my thinking about policy comes in really13:10
johnthetubaguyI am OK restricting the user query by default (and I think the operators where too)13:11
johnthetubaguyI am tempted to just restrict everyone by default, but let you relax it, if you want to take that risk13:11
johnthetubaguyat least for the admins13:11
johnthetubaguybut again, feels overcomplicated, so I don't feel happy with that direction as such13:12
johnthetubaguybut not breaking users can really suck sometimes, maybe this is just one of those time13:12
johnthetubaguys13:12
johnthetubaguyhmm, we got network delays again, or is everyone just very quiet today?13:14
*** yifei has joined #openstack-meeting-413:14
alex_xui'm jus thinking13:14
johnthetubaguythats allowed I guess :)13:14
alex_xuso....those query parameters already being here for very long time, people should cut their leg many times....13:15
johnthetubaguycdent: do you think if its clear we protect people by default, that spec seems more reasonable?13:15
* cdent has slow brain13:15
cdentYeah, if the default is protection, but it can be turned off, that seems likely to make folk happy without totally rejecting the input of operators13:16
alex_xuturned off by policy?13:16
johnthetubaguyyeah, off by default in the policy13:16
alex_xuand only off the admin part?13:17
johnthetubaguyit does mean if we missed some things, we can tweak the groups of queries linked to each policy13:17
alex_xufilters won't break the user, it only ignore those filters. it just didn't return expected sliently13:19
johnthetubaguyI duno, I was thinking off by default for everyone13:19
alex_xusort will break user, the 400 returned13:19
johnthetubaguyhmm, true, I guess this should be ignore using policy13:20
johnthetubaguybased on the overall plan13:20
johnthetubaguya new microversion could add in the errors to help folks later13:20
alex_xuhow about we ignore for invalid sort key?13:20
alex_xuat least it won't break the user.13:21
*** ad_rien_ has joined #openstack-meeting-413:21
*** ad_rien_ has quit IRC13:21
johnthetubaguyyeah, I think we should ignore the not allowed ones, to be consistent13:22
*** ad_rien_ has joined #openstack-meeting-413:22
johnthetubaguyfilters and sorts13:22
*** ad_rien_ has quit IRC13:22
alex_xuor return 403 is enough, most of client should process the case when the request return 40313:23
alex_xus/403/40113:24
*** ad_rien_ has joined #openstack-meeting-413:24
*** yamamoto has joined #openstack-meeting-413:25
johnthetubaguyunsure13:25
johnthetubaguythat feels inconsistent13:26
johnthetubaguyin the future, we can have a microversion that does what we want, and rejects all input thats not acepted/acceptable13:26
alex_xujohnthetubaguy: so break them vs. ignore silently13:26
*** prateek_ has joined #openstack-meeting-413:26
alex_xujohnthetubaguy: +1 microversion in the future to rejects all and return 40013:27
johnthetubaguyyeah, for now, I think we are choosing silently ignore invalid input, unless its an allowed key that has an invalid value13:28
johnthetubaguyto mirror the old behaviour, as close as we can, in a general way13:28
*** markvoelker has joined #openstack-meeting-413:28
*** prateek has quit IRC13:30
*** sp__ has joined #openstack-meeting-413:30
cdentthe twists and turns we take "to mirror the old behaviour, as close as we can, in a general way" throughout all this stuff are both admirable and depressing13:30
cdentit's a nice quotable phrase too13:30
alex_xuI'm a little tent to the 401 returned, the 401 should be processed by client in general. I'm just afraid we return the result the client didn't expected, then just return a fault result siliently13:32
johnthetubaguyyeah, its hard to describe how technical debt mounts up, thats sure a big cause of it13:32
*** Julien-zte has joined #openstack-meeting-413:35
johnthetubaguyyou mean 403?13:35
alex_xuemm....what we return when policy failed?13:35
johnthetubaguyI think 40313:35
johnthetubaguy401 suggests you need a new token I guess?13:35
johnthetubaguyauthenticated vs authorised I am assuming?13:36
johnthetubaguyso what do we want to do next?13:37
johnthetubaguydraft a new version of the spec, and see how that looks?13:37
alex_xuyea13:37
cdentyeah 401 is auth req, 403 is you got auth but it ain't no good13:37
alex_xuchoice in the main, and write others in the alternative section13:37
alex_xus/choice/choose one/13:38
johnthetubaguyyeah13:38
johnthetubaguythats fair, feels like a discussion in the alternatives section13:38
*** lamt has joined #openstack-meeting-413:39
alex_xu#action alex_xu draft a new version of https://review.openstack.org/#/c/39320513:39
johnthetubaguyoh, one clarification...13:39
johnthetubaguyI think we agreed that all joined fields and anything that isn't using he same format as returned in the API, can be rejected without policy?13:40
alex_xuI think yes13:40
alex_xujoined fields means 'system_metadata', 'info_cache'...etc13:40
alex_xuthe tags isn't in the list13:41
johnthetubaguyyeah, stuff not in the instance table directly13:41
johnthetubaguytags are indexed OK, so that should be fine13:41
johnthetubaguywell, tags are intentionally there, put it that way13:41
alex_xuwhat about metadata one, it works now, and metadata is the normal user faced data.13:41
johnthetubaguyyeah, that one feels like we could stop it via policy for now, as its not very efficient13:42
alex_xuok, got it13:42
*** baoli has joined #openstack-meeting-413:43
*** baoli has quit IRC13:43
johnthetubaguy(1) stuff we block that may have worked or caused 500 (silently) (2) stuff we block with policy (silently) (3) stuff we allow for admins only by default (4) stuff we allow for users by default13:43
johnthetubaguyI think thats the 4 camps they need splitting into13:43
*** baoli has joined #openstack-meeting-413:43
johnthetubaguyI guess there is (5) stuff not on any of those lists that is ignored silently13:43
johnthetubaguyman this we managed to make this really complicated by taking so long to clear up this mess13:44
alex_xuemm...we block with policy and sliently ignore the invalid parameters. actually the policy equal to a config option13:45
alex_xupolicy means it will return 40313:45
johnthetubaguyit doesn't have to be, in this case its not going to trigger 403, it can in the new microversion13:46
johnthetubaguynow in theory, all the stuff that causes 500s, could trigger 403, but that seems like an even worse mess13:46
*** prateek_ has quit IRC13:46
*** prateek has joined #openstack-meeting-413:47
alex_xuyea13:47
cdentwhat's an even worse mess?13:47
johnthetubaguyhaving lists of all the things we should reject differently because of what they return today13:47
johnthetubaguyoslo.db blocks a bunch of stuff that triggers 500s13:48
johnthetubaguyits a recent-ish change we didn't notice happen13:48
* cdent nods13:48
cdentIt sort of read like you were saying 403s were messier than 500s, so I was confused13:49
*** alexchadin has quit IRC13:50
*** haleyb_ has joined #openstack-meeting-413:51
alex_xuso...we have plan now13:51
alex_xuupdate the spec13:51
johnthetubaguycdent: ah, oops, true13:51
johnthetubaguyalex_xu: sounds good, thank you!13:52
alex_xujohnthetubaguy: np13:52
*** haleyb_ has quit IRC13:52
alex_xuanything more? otherwise let us close the meeting13:52
*** jichen has joined #openstack-meeting-413:53
* cdent nods13:53
alex_xuok, i think we back to work now13:54
alex_xuthanks all!13:54
alex_xucdent: have a good rest13:54
alex_xu#endmeeting13:54
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:54
openstackMeeting ended Wed Nov 23 13:54:20 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-11-23-13.00.html13:54
cdentthank you13:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-11-23-13.00.txt13:54
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-11-23-13.00.log.html13:54
*** prateek_ has joined #openstack-meeting-413:57
*** prateek has quit IRC13:59
*** woodard_ has joined #openstack-meeting-414:01
*** woodard has quit IRC14:05
*** thorst has joined #openstack-meeting-414:08
*** pcaruana has quit IRC14:14
*** parora has joined #openstack-meeting-414:18
*** thorst has quit IRC14:19
*** prateek has joined #openstack-meeting-414:21
*** prateek_ has quit IRC14:22
*** thorst has joined #openstack-meeting-414:22
*** parora has quit IRC14:24
*** prateek_ has joined #openstack-meeting-414:24
*** psachin has quit IRC14:26
*** prateek has quit IRC14:27
*** thorst has quit IRC14:31
*** yamamoto has quit IRC14:42
*** yamamoto has joined #openstack-meeting-414:44
*** yamamoto has quit IRC14:45
*** vishnoianil has quit IRC14:48
*** bobh has joined #openstack-meeting-414:49
*** bobh has quit IRC14:49
*** bobh has joined #openstack-meeting-414:50
*** andymaier has joined #openstack-meeting-414:52
*** ricolin has joined #openstack-meeting-414:53
*** haleyb_ has joined #openstack-meeting-414:53
*** yamamoto has joined #openstack-meeting-414:54
*** therve has joined #openstack-meeting-414:56
*** ramishra has joined #openstack-meeting-414:56
*** haleyb_ has quit IRC14:57
*** rbak has joined #openstack-meeting-415:00
ramishra#startmeeting heat15:00
openstackMeeting started Wed Nov 23 15:00:17 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
*** cdent has left #openstack-meeting-415:00
*** openstack changes topic to "roll call (Meeting topic: heat)"15:00
*** Julien-zte has quit IRC15:00
ricolin0/15:01
*** Julien-zte has joined #openstack-meeting-415:01
*** Julien-zte has quit IRC15:01
therveYop15:01
*** Julien-zte has joined #openstack-meeting-415:02
*** cwolferh has joined #openstack-meeting-415:02
*** Julien-zte has quit IRC15:02
cwolferho/15:02
ramishrahmm.. US guys probably are in holiday mode already:)15:02
syjuliano/15:02
*** Julien-zte has joined #openstack-meeting-415:02
*** Julien-zte has quit IRC15:03
cwolferhholiday is so close :-)15:03
*** Julien-zte has joined #openstack-meeting-415:03
ramishraok, let's start, it should be quick one15:03
*** Julien-zte has quit IRC15:03
ramishra#topic adding items to agenda15:03
*** openstack changes topic to "adding items to agenda (Meeting topic: heat)"15:03
ramishrahttps://wiki.openstack.org/wiki/Meetings/HeatAgenda#Agenda_.282016-11-23_1500_UTC.2915:04
ramishra#link https://wiki.openstack.org/wiki/Meetings/HeatAgenda#Agenda_.282016-11-23_1500_UTC.2915:04
*** Julien-zte has joined #openstack-meeting-415:04
*** Julien-zte has quit IRC15:04
ramishraAny more items, we only have one bp to discuss I think.15:05
*** thorst has joined #openstack-meeting-415:05
*** Julien-zte has joined #openstack-meeting-415:05
*** Julien-zte has quit IRC15:05
ramishra#topic resource type versions15:05
*** openstack changes topic to "resource type versions (Meeting topic: heat)"15:05
ramishra#link https://blueprints.launchpad.net/heat/+spec/heat-resource-type-versions15:05
ramishrasyjulian: you've added this, right?15:06
*** Julien-zte has joined #openstack-meeting-415:06
syjulianyes15:06
*** Julien-zte has quit IRC15:06
zanebo/15:06
ramishrahi zaneb15:06
ramishrawe discussed that during the summit.15:06
ramishrait looks ok to me.15:06
* zaneb blames daylight savings15:06
*** Julien-zte has joined #openstack-meeting-415:07
ricolinlol15:07
*** Julien-zte has quit IRC15:07
*** claudiub has quit IRC15:07
syjulianyup. we're kinda wondering how registering would work15:07
ramishrazaneb: you were not present during that discussion, wdyt?15:07
ramishra#link https://review.openstack.org/39860115:08
zanebreading now... seems reasonable15:08
ricolinI think it might be a good start to support micro version15:09
thervesyjulian, I feel that the problem description is really lacking15:09
*** reedip_ has joined #openstack-meeting-415:09
therveIt basically says "we don't support version, let's do it"15:09
therveI want to know why we need resouce versions15:09
cwolferhwhat's the advantage over the resource itself just having an arbitrary my_version property and the resource just knows what to do internally to itself?15:10
ricolincwolferh: I think current approch is more like allow V1 and V2 share same resource type15:12
ramishratherve: we do lot of hacks err.. translations to be backward compatible.15:12
thervecwolferh, That's one solution not mentioned too, yeah. But you need to keep the property schema compatible if you do that15:12
*** thorst has quit IRC15:12
ramishratherve: it sould probably mention that.15:12
therveramishra, Well yeah and that won't solve that?15:12
cwolferhtherve, ah, true15:12
therveramishra, Unless we somehow start to enforce versions, you can't break compatibility15:13
ramishratherve: yeah15:13
ramishraMay be should review and put these comments on the spec, however, it would be good to add this.15:14
therveYeah I'll do that15:14
syjulianyes that will help15:15
ramishrasyjulian: I think we would review and provide the comments.15:16
thervesyjulian, We're also here to discuss it though :)15:16
zanebjust added some thoughts on the spec15:16
therveAnyway15:16
syjuliangotcha15:16
*** limao has joined #openstack-meeting-415:16
syjulianwe decided on versions so when a resource has a new version we won't have to register it in a new name15:16
*** thorst has joined #openstack-meeting-415:16
ramishrait's way to get attention of the reviewers, by adding it to the meeting agenda:)15:17
syjulianit does help :) . thank you guys for looking at it15:17
ramishrashould we move on now?15:18
ramishra#topic gate issues15:18
*** openstack changes topic to "gate issues (Meeting topic: heat)"15:18
*** spotz_zzz is now known as spotz15:19
therveUrg it's bad15:19
ramishraI just thought to give an update on the issues we had in the last few days.15:19
ramishraNumber of things broken after the jobs changed to xenial15:19
ricolinheatclient 1.6 current been add to black list15:19
ramishraricolin: yeah, it had a backward incompatible change, my mistake15:20
*** thorst has quit IRC15:20
ramishrahttps://review.openstack.org/#/c/401096/15:20
ramishrawe have a new release now and it should merge anytime.15:21
ramishraI mean the global requirement change.15:21
ramishraThings seems to be in control now.15:21
ramishratherve: most of jobs are passing since a few hours;)15:22
*** klamath has joined #openstack-meeting-415:22
*** klamath has quit IRC15:22
*** hongbin has joined #openstack-meeting-415:22
therveramishra, There are 50% slower for some reasons though15:23
ramishraif someone can help land this https://review.openstack.org/#/c/400689/ stable/newton would be fixed.15:23
*** klamath has joined #openstack-meeting-415:23
zaneb+2'd15:24
ramishratherve: you can self approve;)15:24
*** limao_ has joined #openstack-meeting-415:25
*** unicell has quit IRC15:25
therveramishra, I don't have stable permissions for some reasons15:25
ramishraskraynev: ^^15:25
zanebreally?15:25
* zaneb will look in to that15:25
zanebramishra: do you not have stable +A permissions either?15:26
ricolinI think Zane can just +workflow and let it land15:26
ramishratherve: it seems issues with some clouds, some of the jobs are finishing in 30-35 mins.15:26
ramishratherve: like this one finished quick https://review.openstack.org/#/c/400961/15:27
therveramishra, Okay we'll see :)15:27
zanebI thought https://review.openstack.org/#/admin/groups/152,members was the only group needed.15:28
*** limao has quit IRC15:28
* zaneb goes looking for more15:28
zaneboh ho https://review.openstack.org/#/admin/groups/536,members15:28
zanebI cant edit though :/15:28
ramishraok, let's move on.15:29
ramishra#topic placeholder15:29
*** openstack changes topic to "placeholder (Meeting topic: heat)"15:29
ramishra#link https://blueprints.launchpad.net/heat/+spec/implement-placeholder15:29
ramishraricolin: stage is yours;)15:30
ricolinNeed some review on that BP15:30
zanebyeah, I need to find some time to have a look15:31
*** Qiming has joined #openstack-meeting-415:31
ramishraricolin: ok just reviews:)15:31
ricolinyep15:31
zanebricolin: there isn't a spec for this, right?15:32
ricolinMaybe we can get it done before Pika15:32
ramishrabtw, there are number of bps for review, we need to see what we can do in this cycle.15:32
ricolinwe have a spec15:32
ramishrawe don't have much time though and the holidays.15:32
*** unicell has joined #openstack-meeting-415:32
ricolinhttps://review.openstack.org/#/c/392499/15:32
zanebah!15:33
zanebok, linked it from the bp15:33
ricolinramishra: It's a holiday week for us!15:33
zanebI can review that first, it'll be quicker :)15:33
ricolinI mean U.S.15:33
ricolinzaneb: yah! don't want you guys go for those 15 patches first15:34
ramishraRequest to review the specs and then see if/what we can do this cycle.15:34
*** numans has quit IRC15:34
zanebok, will do15:35
ricolinramishra: +115:35
zanebramishra: btw I have another topic once we have finished the agenda15:36
*** nkrinner has quit IRC15:36
ramishrawe have translation, property, template migrate group and more;)15:36
ramishraproperty group15:36
ramishrazaneb: sure15:37
ramishraricolin: the next topic is also spec review request I think?15:37
ramishra#topic ironic resource15:37
*** openstack changes topic to "ironic resource (Meeting topic: heat)"15:37
ricolinramishra: kind of, but I would like to know what guys think about it15:38
*** janki has quit IRC15:38
ramishraricolin: I thought we had agreed to add the ironic resources, no?15:38
ramishrazaneb, therve ?15:38
zanebremind me why we're doing this again?15:38
zanebmost people will never see it, since it's admin-only, so no big deal...15:39
*** duonghq has joined #openstack-meeting-415:39
*** nkrinner has joined #openstack-meeting-415:39
ricolinzaneb: ironic resource should seperate to manage resource and deploy resource15:39
zanebjust not sure that it's actually a useful thing15:39
ramishrazaneb: I think there was an earlier discussion about it, not able to locate it.15:40
*** limao_ has quit IRC15:40
ricolinand manage resource will be a good item to add in to heat15:40
thervericolin, Are you going to use this?15:40
zanebok, so it's not actually about going around nova for allocating servers, just about managing the stuff that Ironic knows about15:40
zaneb?15:40
*** limao has joined #openstack-meeting-415:41
ricolinzaneb: Yep15:41
ramishrazaneb: yeah, that was also my impression without reading the spec15:41
zanebok, sounds harmless enough15:41
ricolinzaneb: I add all ironic resource in spec15:42
ramishraok, sounds good.15:42
ricolinzaneb: would like to let nova do it job and use ironic resource in heat to cover the rest15:42
zanebI'm not actually convinced that any of our admin-only resources are really useful but they're mostly harmless as long as they're hidden15:42
zaneb(from non-admins)15:43
ramishrayeah, I've seen keystone resources used a lot though.15:43
*** sayantani01 has joined #openstack-meeting-415:43
ramishraI see number of bugs reported.15:43
ricolintherve: It will be a greate thing if we can use heat to control baremetral15:43
thervericolin, That's not my question though :)15:44
*** berendt has quit IRC15:44
ricolinricolin: I'm more thinking about Ironic+magnum case can be done just in heat15:44
*** berendt has joined #openstack-meeting-415:45
zanebramishra: keystone resources would be _really_ useful if only you didn't have to be an admin to use them :/15:45
*** yifei has quit IRC15:45
*** prateek_ has quit IRC15:46
*** prateek_ has joined #openstack-meeting-415:46
therve(got to go, bbl)15:46
*** nkrinner has quit IRC15:46
ramishraok, should we move on, we've few more mins.15:47
ramishra#topic open discussion15:47
*** openstack changes topic to "open discussion (Meeting topic: heat)"15:47
ramishratherve: np, thanks:)15:47
ramishrazaneb: you wanted to discuss something?15:47
ricolinzaneb: aren't you have some topic?15:47
zanebramishra: ah, yes. backpressure.15:48
zanebspecifically, how, in convergence, do we limit the amount of work that we try to do at one time15:48
zanebso that we don't e.g. run out of DB connections15:48
ramishrazaneb: I don't have a clue, you know better:)15:49
zanebright now we do it by limiting the thread pool size...15:49
zanebbut as we've found this week that's apparently not an ideal solution15:50
zanebsmall limit -> everything is slow15:50
zaneblarge limit -> run out of db connections15:51
cwolferhit's not an ideal solution in the db connection case. but are there others?15:51
ramishrazaneb: Isn't it deployment specific15:51
ramishra?15:51
ramishraI mean someone can increase max_connections if they want?15:51
ramishraif the concurrency is high.15:51
zanebI guess15:52
ramishraThough I may be missing something.15:52
zanebwe either need to publish the correct tuning parameters for different sized deployments or make this Just Work imho15:52
ramishrazaneb: I saw this patch from therve https://review.openstack.org/#/c/400155/15:53
zanebthe ideal thing would be to enumerate our bottlenecks (like db connections) and apply backpressure, using the message queue as a buffer15:53
*** sukhdev has joined #openstack-meeting-415:54
zanebiow the exact opposite of therve's slow-start patch ;)15:54
*** syed__ has joined #openstack-meeting-415:54
*** haleyb_ has joined #openstack-meeting-415:54
zanebI don't have a solution here15:54
ramishrazaneb: yeah:)15:54
zanebjust wanted to socialise the idea a little bit15:55
ramishrazaneb: Would it be good to start a ML thread for it?15:55
zanebit probably would15:55
*** andymaier has quit IRC15:56
zanebtherve: can you give a quick update on exactly what we found with the gate and how we fixed it?15:56
*** klamath has quit IRC15:56
ramishrazaneb: I'm not sure if therve is still around.15:56
zaneboh, missed that he dropped out15:56
ramishrazaneb: we did not know the exact root cause.15:56
zanebramishra: can *you* give a quick update? ;)15:57
ramishrait started when we moved to xenial15:57
ramishrabut it seems it's fine now.15:57
ramishraWe changed the executor_thread_pool_size to 8 from default 6415:58
ramishrain master15:58
*** inc0 has joined #openstack-meeting-415:58
ramishrathat's actually used as the max_overflow of connections in oslo.db15:58
ramishramax_overflow is 40 by default15:58
*** mgiles has joined #openstack-meeting-415:58
*** srwilkers_ has joined #openstack-meeting-415:58
zanebwhat does overflow mean in this context?15:59
*** haleyb_ has quit IRC15:59
ramishrawe have a pool_size of 5 (default)15:59
*** v1k0d3n has joined #openstack-meeting-415:59
*** makowals has joined #openstack-meeting-415:59
ramishraso if more connections are needed from the pool, it can overflow to the overflow limit16:00
ramishraso the max connections from the pool that can be used is 5+40=4516:00
*** nkrinner has joined #openstack-meeting-416:00
* zaneb scratches head16:00
*** sean-k-mooney has joined #openstack-meeting-416:00
zanebit sounds like we're saying the pool_size is meaningless?16:00
*** Sukhdev_ has joined #openstack-meeting-416:01
ramishrazaneb: http://docs.openstack.org/developer/oslo.db/api/options.html16:01
inc0<< taps into meeting doors >>16:01
ricolintime's up16:01
ramishraI think we've to end.16:01
zanebok16:01
ramishrathanks all16:01
inc0thank you guys!:) sorry, but I sense our meeting will be packed too16:02
ramishra#endmeeting heat16:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:02
openstackMeeting ended Wed Nov 23 16:02:03 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/heat/2016/heat.2016-11-23-15.00.html16:02
*** zhubingbing has joined #openstack-meeting-416:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/heat/2016/heat.2016-11-23-15.00.txt16:02
openstackLog:            http://eavesdrop.openstack.org/meetings/heat/2016/heat.2016-11-23-15.00.log.html16:02
zhubingbinghello guys16:02
inc0#startmeeting kolla16:02
openstackMeeting started Wed Nov 23 16:02:18 2016 UTC and is due to finish in 60 minutes.  The chair is inc0. Information about MeetBot at http://wiki.debian.org/MeetBot.16:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:02
*** openstack changes topic to " (Meeting topic: kolla)"16:02
openstackThe meeting name has been set to 'kolla'16:02
*** jascott1 has joined #openstack-meeting-416:02
inc0#topic woot for kolla - rollcall16:02
*** openstack changes topic to "woot for kolla - rollcall (Meeting topic: kolla)"16:02
inc0w00t everyone!;)16:02
duonghqwoot16:02
berendtwoot16:02
*** makowals_ has quit IRC16:02
sean-k-mooneywoot16:03
jascott1woot16:03
Jeffrey4lwoot16:03
zhubingbingwoot16:03
srwilkers_woot and such16:03
duonghqnice to see you guys16:03
sdake_o/16:03
mgileswoot16:03
portdirecto/16:03
* berendt is only reading, walking to the hotel at the moment, reading on my mobile phone16:03
*** ad_rien_ has quit IRC16:03
sean-k-mooneysdake_: being a rebel with the o/16:03
sp__hi all16:03
sayantani01woot :)16:03
inc0#topic announcements16:04
*** openstack changes topic to "announcements (Meeting topic: kolla)"16:04
sdake_sean-k-mooney o/ is standard openstack greeting16:04
inc0I don't have anything:)16:04
inc0oh, we do have voting gates now16:04
sean-k-mooneycool16:04
inc0for source builds16:04
Jeffrey4land gate is green ;)16:04
sdake_Jeffrey4l ++16:05
*** anilvenkata has quit IRC16:05
inc0any announcements from community?16:05
sdake_ya i got something16:05
inc0go ahead16:05
sdake_ryan stepping away from kolla project for awhile16:05
sdake_who knows how long16:05
srwilkers_:(16:05
sdake_in the meantime i'll be handling kolla-kubernetes16:05
Jeffrey4l;(16:06
sdake_this project is too big to handle solo16:06
sdake_i failed at handling kolla-kubernetes in newton - so busy with ansible16:06
*** egonzalez90 has joined #openstack-meeting-416:06
sdake_lets make it a winner16:06
zhubingbing;)16:06
jascott1woot!16:06
duonghqroger16:06
berendtBad news... :-(16:06
inc0k, let's start with actual meeting:)16:07
inc0we'll talk about k8s later16:07
sdake_ya he may come back who knows16:07
inc0#topic gates - state of union16:07
*** openstack changes topic to "gates - state of union (Meeting topic: kolla)"16:07
inc0so, thanks to Jeffrey4l and others we have green gates after repo splut16:07
inc0we also have some voting gates, so now we can move forward to make improvements16:07
inc01 thing is effort to setup docker registry in infra16:08
Jeffrey4linc0, what's the progress on that?16:08
inc0https://review.openstack.org/#/c/401003/ https://review.openstack.org/#/c/399221/16:08
inc0these reviews + some discussions I keep having on infra16:09
Jeffrey4lcool16:09
inc0I know how to install registry outside docker, but I could use puppet help16:09
*** armax has joined #openstack-meeting-416:09
inc0so if anyone knows puppet and would like to assist me with this, I'd appreciate it16:09
inc0having registry will allow us to have voting deploy gates16:09
inc0also few other nice things like proper upgrade gates16:10
inc0next item that could be done would be multinode gating16:10
sean-k-mooneyinc0: is there a reason you are installing the registry with puppet and not using the docker container?16:10
inc0kfox1111 already prototyped multinode gate in kolla-k8s, we could do it in kolla too16:10
inc0kolla-ansible*16:10
inc0sean-k-mooney, they don't have running docker16:11
inc0so we'd need to install docker;) arguably harder16:11
sean-k-mooneyinc0: ah ok makes sense16:11
inc0so if someone would like to tackle multinode gating, this is open for volunteers too16:11
inc0next in line would be more scenerios, but that's going to grow16:12
sdake_inc0 i did you a favor and cleaned up launchpad for kolla itself16:12
inc0gates are one of biggest painpoints Kolla has today, and one of priorities for release16:12
inc0sdake_, thank you16:12
sdake_inc0 recommend blueprints to track that work16:12
sean-k-mooneyinc0: is tempest run in the gates currently?16:13
sdake_then people can sign themselves up16:13
inc0sean-k-mooney, nope16:13
Jeffrey4lsean-k-mooney, i am trying to set tempest up.16:13
sdake_np16:13
sean-k-mooneyJeffrey4l: cool useing the tempest contaienr in kolla?16:13
Jeffrey4lsean-k-mooney, yep.16:13
sdake_rather kolla-ansible16:13
sdake_which is where we want the gates16:13
inc0sdake_, we want gates everywhere;016:14
inc0but build gates are straightforward and not much more we can do there16:14
sdake_right16:14
inc0(well, we could use customizations for example)16:14
inc0but ansible needs more immediate gate help16:14
sean-k-mooneyJeffrey4l: its mising ping which make the scenairo tests fail so that will need to be fixed to make the gates pass when tempest is added16:14
*** mandre has joined #openstack-meeting-416:16
Jeffrey4lwe also need something like puppet scenario 1/2/3, to test more service.16:16
inc0anyway, I'd like to get registry up first, so if anyone would be willing to help me, please speak up now or after meeting16:16
inc0anything else about gates?16:17
Jeffrey4lneed volunteer ;)16:18
sdake_need a blueprint16:18
sdake_work items in blueprint16:18
Jeffrey4lneed more guy to notice the gate failure and fix it ;)16:18
sdake_volunteers sign up for work items16:18
sdake_thats how we have always rolled16:18
Jeffrey4lsdake_, yep.16:18
inc0kk, I'll subit my blueprints after meeting, Jeffrey4l please do it too if you have anything in mind16:19
inc0(also everyone else;))16:19
inc0moving on16:19
inc0#topic post-repo split cleanups status16:19
*** openstack changes topic to "post-repo split cleanups status (Meeting topic: kolla)"16:19
*** rbak has quit IRC16:19
inc0#link https://etherpad.openstack.org/p/kolla-repo-split16:19
Jeffrey4lroger.16:20
inc0let's go from top16:20
inc01. removal of ansible code -> done16:20
inc0let's mark what is done and what's not16:20
inc02. fixing gates16:20
inc0can we call it done or still work to be done?16:21
sean-k-mooneythe ansible code is removed but we still need to remove the non ansible code form kolla-ansible correct?16:21
Jeffrey4lfixing gate is done.16:21
sp__sdake_: yes we will16:21
Jeffrey4lbut we need more gate ;), it is another thing.16:22
sdake_sp__ huh?16:22
Jeffrey4l3. doc split16:22
inc0sean-k-mooney, it seems we already merged docker removal from ansible16:22
inc0docs are very outdated and totally not changed16:22
sp__sdake_: sign up for work16:22
inc0I'd put this as #1 priority16:22
sdake_oh right16:22
Jeffrey4linc0, we can not maintain two copy of doc.16:23
inc0Jeffrey4l, I'd keep all docs in kolla for now16:23
*** makowals has quit IRC16:23
inc0no reason to add to confusion16:23
Jeffrey4lso all doc in kolla-ansible should be removed?16:23
sean-k-mooneyinc0: so going forward all docs reside in kolla. for kolla-ansibel and k8s16:23
*** zenoway has quit IRC16:23
inc0Jeffrey4l, maybe, that's good discussion to be had, I'll put it into dedicated topic in this meeting16:24
egonzalez90i would leave there and link from kolla to kolla-ansible repo, the same for k8s docs16:24
inc0egonzalez90, agree, and doc root in Kolla16:24
*** zenoway has joined #openstack-meeting-416:24
Jeffrey4lsean-k-mooney, kolla-ansible has its own doc right now. if we keep all docs in kolla, including k8s, we need move that doc16:24
Jeffrey4lkolla-ansibe/kolla-k8s16:24
*** Sukhdev_ has quit IRC16:24
inc0but for now we need to change quick start guide to work with repo split16:24
inc0QSG should be single doc tho16:25
inc0it's meant to be simple and easy to follow16:25
*** unicell has quit IRC16:25
inc0anyway, docs -> still to be done and #1 priority16:25
inc07. bugs and blueprints moved out of kolla16:26
inc0sdake_, you mentioned you took on that right? what's the status?16:26
sdake_actually jeffrey4l moved the bugs and coolsvap moved the blueprints16:26
sdake_i got them into an orderly state16:26
*** iyamahat has joined #openstack-meeting-416:26
inc0ok, thank you all then16:26
sdake_the blueprints part16:26
inc0so can we mark it as done?16:26
sdake_didnt' touch the bugs, done triaging for awhile :)16:27
inc0so bugs...will be harder16:27
*** andymaier has joined #openstack-meeting-416:27
inc0as people will keep adding bugs to kolla, and that's ok16:27
Jeffrey4lanother thing is: how we handle the bp after split. is there any better solution expect for register on each project?16:27
inc0as part of triaging we might need to add "moving bugs to appropriate project" part16:27
sean-k-mooneyinc0: sorry to go back to the split but what about the tools directory and kolla python module. im not sure the build code shoudl be duplicated in kolla-ansible16:28
Jeffrey4linc0, yep.16:28
sdake_project^deliverable :)16:28
inc0Jeffrey4l, well, blueptints for kolla-ansible will mostly be different than kolla16:28
inc0sean-k-mooney, there are tools for kolla and tools for kolla-ansible16:28
*** zenoway has quit IRC16:28
*** dkehn__ has joined #openstack-meeting-416:28
sean-k-mooneyblueprints could be decomposed into parts. one for the container to kolla and then one for each deployment type16:28
Jeffrey4linc0, yep. just wanna to check whether there is a better solution. it is different, but related.16:28
inc0I can't think of any overlap16:28
inc0liek tools for both16:29
Jeffrey4llike `implement nova service`16:29
sean-k-mooneyinc0: yes but the tools for anible still have the image build code16:29
inc0Jeffrey4l, that can be "implement nova container" -> kolla "implement nova ansible role" ->k-ansible "implement nova k8s chart" -> k-k8s16:29
inc0sean-k-mooney, why?16:30
inc0I mean16:30
inc0now for gates16:30
inc0but normally, not really16:30
inc0build is totally separate16:30
sean-k-mooneyinc0: well thats my point the repos has that code currently16:30
inc0ahh, so add this to cleanup right?16:30
inc0good catch16:30
inc0I'll make it separate point in etherpad16:30
sean-k-mooneyinc0: i think we should remove it from kolla ansible and just use the code in kolla16:30
portdirectkolla-k8s also currently relys on code that is in kolla-ansible for config gen afaik - gut agai i think this is just transitionary.16:30
sean-k-mooneyinc0: cool16:31
portdirect*but again16:31
Jeffrey4l inc0 re bp yep. that works.16:31
sdake_portdirect yup transitory16:31
inc0well16:31
inc0not exactly16:31
inc0I mean we want it changed16:31
Jeffrey4lportdirect, any idea on improving this?16:31
inc0but we don't know how to change it really16:31
inc0#link https://review.openstack.org/#/c/399147/16:32
inc0Jeffrey4l, ^16:32
* Jeffrey4l is checking16:32
sdake_inc0 you were going to write a spec for seperating the default configs?16:32
*** bogdando has quit IRC16:32
portdirectnot really - I'm open to suggestions - but inc0's just pointed to somthing i'd missed16:32
inc0sdake_, click da lin16:33
inc0k16:33
sdake_cool thanks16:33
inc0it's still sceleton, but I'll need more people to chime in16:33
inc0it's important16:33
inc0to be done right16:33
inc0as it will affect upgrades/ansible (which *has to work*) and stable releases16:34
*** ramishra has quit IRC16:34
inc0which means if we want to roll with it, it has to be bulletproof16:34
inc0I'd rather keep duplicated configs that break upgrades16:34
sdake_yup clearly16:35
inc0ok, bottom line, take a look at spec later and let's kick off this discussion16:35
inc0moving on16:35
inc0#topic documentation after split16:35
*** openstack changes topic to "documentation after split (Meeting topic: kolla)"16:35
portdirectinc0: that spec looks logical, I'll look later16:35
inc0So Jeffrey4l moved good topic, we need to decide which docs sits where16:35
inc0my suggestion: root doc, arch docs and stuff like that (also QSG) in kolla and links to kolla-k8s and kolla-ansible from there16:36
Jeffrey4lfyi, kolla-ansible has doc site right now http://docs.openstack.org/developer/kolla-ansible/16:36
sdake_i tend to think we should hash that out on the mailing list16:36
sdake_the docs are a fragile thing16:37
sdake_because we dont have a doc writer writing docs16:37
inc0yeah, agree, let's kick off discussion please tho16:37
sean-k-mooneyi think we are going to find more things that are common between k8s and ansible in the future not just docs and configs.16:37
inc0for one, we *need* QSG fixes asap16:37
*** zhubingbing__ has joined #openstack-meeting-416:37
inc0(especially that it still shows that stable branch needs ansible 1.9)16:38
Jeffrey4lQSQ? means?16:38
inc0(which is not true for newton)16:38
inc0QSG - quick start guide16:38
*** thorst has joined #openstack-meeting-416:38
Jeffrey4lroger.16:38
sdake_nah qsg has two sets of requirements16:38
sdake_if you read the docs :)16:38
Jeffrey4lwe added more thing in QSG, imo.16:38
sdake_ansible 2.0 and ansible1.916:38
*** thorst has quit IRC16:39
inc0https://github.com/openstack/kolla/blob/master/doc/quickstart.rst#install-dependencies16:39
*** zhubingbing has quit IRC16:39
inc0yes, and 1.9 is dependency *for stable branch*16:39
inc0which is no longer true16:39
sdake_i see what you mean16:39
duonghqiirc there is a ps in review queue fixing this16:39
sdake_yup that needs changing16:39
inc0also QSG should use bootstrap-servers16:39
inc0as it's much easier to handle than manual labor16:40
Jeffrey4lwe have this line, should mention stable branch thing in master doc http://docs.openstack.org/developer/kolla/newton16:40
Jeffrey4lneed fix it in stable branch doc.16:40
inc0that's also true, we can just link old docs and keep single versions in master16:40
inc0bottom line, QSG needs love, lots of it, we should rewrite it tbh now16:41
inc0v1k0d3n, also mentioned need to add "hacks to deploy with single interface"16:41
inc0also useful16:41
sdake_docs are #1 complaint, #2 complaint, and #3 compliant from operators16:42
sean-k-mooneyinc0: on that i need to extend the kolla-host script to be also able to bootrasp the build host.16:42
Jeffrey4lsdake_, lol that's true16:42
v1k0d3nah, yes. been playing with this.16:42
v1k0d3ninc0:16:42
inc0sean-k-mooney, not really16:42
inc0it's all working16:42
*** yamahata has joined #openstack-meeting-416:42
v1k0d3nstarted asking questions about some api strangeness (most likely a config error on my end) with sdake_yesterday, but there were too many convo's going on at that time.16:42
*** jichen has quit IRC16:42
inc0I mean it can download kolla, but that's a bit over the top imho16:43
v1k0d3nif someone can help me understand a little better, i can get this firmed up fairly quickly. over teh weekend perhaps16:43
v1k0d3n?16:43
inc0v1k0d3n, sure, after meeting16:43
portdirectthe kolla-k8s docs are esp bad at the moment; though I think we should discuss that when we get to that part of the meeting?16:43
sean-k-mooneyinc0: well ill submit a blueprint with what i was thinking and we cans discuss16:43
inc0sean-k-mooney, please, thanks16:43
v1k0d3nportdirect: sean-k-mooney sdake_ inc0 we are working on adding the pvc to halcyon...which is a big deal.16:44
inc0pvc?16:44
zhubingbing__i have two  questions about elk16:44
inc0as in volume claim?16:44
v1k0d3nif that helps? there is a workaround that kolla-k8s should be aware of...we needed a custom kubernetes-controller to make this work.16:44
portdirect^^16:44
v1k0d3nyes inc016:44
v1k0d3nbtw: https://github.com/att-comdev/dockerfiles/tree/master/kube-controller-manager16:45
*** yamamoto has quit IRC16:45
inc0ok, I think we naturally moved to16:45
inc0#topic kolla-kubernetes topics16:45
*** openstack changes topic to "kolla-kubernetes topics (Meeting topic: kolla)"16:45
v1k0d3nnot sure if in the future workarounds should be kolla provided?16:45
v1k0d3ni think this may actually be a good idea...16:45
v1k0d3nto prevent broken items in the future.16:45
v1k0d3n(reliance on upstream)16:45
sdake_#1 complaint I get from all the folks that want to do kolla-kubernetes dev is "how do I develop the thing"16:46
*** galstrom_zzz is now known as galstrom16:46
portdirect developer env: we need a common one16:46
portdirectand the docs to go with it16:46
inc0halcyon is promising in this space16:46
portdirect+116:46
v1k0d3nsource of truth halycon and we can doc?16:46
v1k0d3nor if someone wants to help...that's fine too16:46
v1k0d3nportdirect:  you've done a lot to help as well.16:46
portdirectv1k0d3n: I'd be up for helping there16:46
inc0let's start with doc16:46
sdake_https://launchpad.net/kolla/ocata16:47
sdake_woops wrong link :)16:47
v1k0d3nand as i've said before...it doesn't have to stay in this repo. if the source of truth is better in kolla-k8s...by all means!16:47
inc0I'd like to have it in gerrit one way or another at some point16:47
*** ad_rien_ has joined #openstack-meeting-416:47
sdake_https://launchpad.net/kolla-kubernetes/ocata16:47
inc0v1k0d3n, or dedicated "satelite" project in openstack16:47
sdake_have a look at ocata 2 (the milestone we are in at present)16:47
inc0logistics can be dealt with16:47
v1k0d3nhow can we make this happen?16:47
v1k0d3nor should say...what can we do to help?16:48
portdirectOk - leading on from sdake's comment - has anyone got a working deve env from kolla-k8s that they have propped up in the last few weeks?16:48
sdake_its easy, just follow the openstack workflow16:48
inc0v1k0d3n, 1hr of work really;) creating kolla-halcyon deliverable16:48
v1k0d3nthe doc is blueprint already.16:48
sdake_i think it makes more sense to just link then add a deliverable16:48
sdake_v1k0d3n agree16:48
v1k0d3nyou want halcyon to end up in a dev folder for kolla-k8s?16:48
sdake_we want o move fast making a deliverable takes forever16:49
v1k0d3nwe can make that happen if you want.16:49
portdirectthat woud be great from my point of view16:49
mgileshalcyon is limited to os's that support kube-adm though, right?16:49
sdake_v1k0d3n what I'd like is docs in kolla-kubernetes itself that shows how to use halcyon16:49
inc0ok, propose a patch then v1k0d3n please16:49
mgilesFine for dev, but might be a problem longer term for us16:49
inc0to kolla-k8s with halcyon in it, and docs16:49
v1k0d3ncurrently yes, but i was going to submit an update for some of the CoreOS happening currently.16:49
v1k0d3nmgiles: ^^^16:49
v1k0d3nmy comment16:50
portdirectI'm also working on Fedora Atomic support16:50
sdake_i think we treat halcyon a an upstream dev environment16:50
sdake_rather then somethign we maintain16:50
srwilkers_i think thats a better approach16:50
inc0well, it's going to be critical for our effort16:50
portdirectexactly - it just takes the strain of setting up a k8s cluster16:50
sdake_portdirect precisely16:50
sdake_then people can develop16:50
sdake_that unblocks that16:51
inc0ok, I'll shut up now;) I need docs at least16:51
inc0where code lives - we can discuss later16:51
sdake_ya16:51
sdake_so GOAL16:51
v1k0d3ninc0: sounds good16:51
sdake_1.0.0 = compute kit based upon spec ryan wrote16:51
sdake_its only going to happen with community support16:51
sdake_take a look at the blueprints16:51
sdake_they are well laid out16:52
sdake_sign up for what interests you16:52
sean-k-mooneyit would be nice if the bootstrap-servers command could bootrap for the k8s enviorment too. even if that is just use halcon after installing docker.16:52
sdake_sean-k-mooney oen thing at a time bro :)16:52
sdake_lets get it working in a dev env first16:52
duonghqI'm thinking I should give kubeadm another chance16:52
sean-k-mooneysdake_: sure thing16:52
sdake_duonghq whatever works for you16:53
duonghqkube-deploy is much better for me than kubeadm16:53
sdake_i'd like to thank jascott1 for helping get the blueprints into a state that make sense16:53
duonghqI'm not sure if  halcyon does something better16:53
sdake_they lead to a logical outcome of 1.0.016:53
duonghqsure16:53
sdake_and duonghq helped a bit too :)16:54
*** Kiall has joined #openstack-meeting-416:54
v1k0d3nduonghq: let's take offline or PM me so we can make it work.16:54
v1k0d3n?16:54
v1k0d3nunless we want to talk this now here...16:55
*** haleyb_ has joined #openstack-meeting-416:55
duonghqv1k0d3n, sure, it is already working but eat much IOPS16:55
v1k0d3nkube-deply meaning?16:55
sdake_for folks that are new to openstack16:55
sdake_i'll be happy to assist on workflow issues you have16:55
sdake_its key to learn the workflow if your a new contrib16:55
duonghqv1k0d3n, https://github.com/kubernetes/kube-deploy <- that is, Ryan recommended it for me16:55
sdake_that is item #2 of importance16:56
inc0sdake_, there is good doc for that in fact16:56
sdake_agree there are good docs16:56
*** andymaier has quit IRC16:56
portdirectthese discussions are exactly why I think we should avoid setting up the k8s cluster becoming part of the kolla-k8s scope (at least at this stage) - as there are so many options with pro's and cons to each of them16:56
*** ad_rien_ has quit IRC16:56
*** galstrom is now known as galstrom_zzz16:56
sdake_if you want help, ask for it16:56
v1k0d3nso the issue duonghq is with pvc...which you're going to run into.16:56
inc0portdirect, agree, minus dev env16:56
inc0we want docs for dev env setup16:56
sdake_portdirect agree16:56
inc0prod - I wouldn't touch it with 1m pole16:57
sdake_right we need a dev env 6 months ago16:57
duonghqv1k0d3n, I'll pm you after the meeting16:57
portdirectinc0: exactly :)16:57
v1k0d3nok16:57
v1k0d3njust one thing to note team...16:57
inc0or 3ft, if SI is hard16:57
portdirectim in europe...16:57
v1k0d3nthat out of the box there are issues with some of the rdb pvcs16:57
sdake_#3, sign up for work that interests you16:57
v1k0d3nhad to go with 1.5.0beta116:57
sdake_we have a solid core team and need to grow it16:57
sdake_#4. need reviews16:58
portdirectv1k0d3n: I think targetting 1.5 makes sense at this stage, esp with the changes it brings in16:58
v1k0d3nso there are some clear dependancies required. just so devs are aware. however you get there...that's fine. we're planning on making this easier for our kolla dev team internal.16:58
v1k0d3noh my... portdirect absolutely.16:58
v1k0d3nfor instance, dont put any stock in petsets.16:58
sdake_so - those are 4 guidelines i'd provide16:58
sdake_and we are out of time :)16:59
v1k0d3nthat would be tragic without a watchful eye.16:59
inc0allright guys, we're out of time16:59
v1k0d3nthings like that..will burn us16:59
v1k0d3nlater16:59
inc0thank you all for coming!16:59
duonghqthank you16:59
inc0let's move to #openstack-kolla16:59
inc0#endmeeting kolla16:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:59
openstackMeeting ended Wed Nov 23 16:59:43 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-11-23-16.02.html16:59
*** sean-k-mooney has left #openstack-meeting-416:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-11-23-16.02.txt16:59
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-11-23-16.02.log.html16:59
portdirectcheers - see you on the flipside16:59
*** mgiles has left #openstack-meeting-416:59
zhubingbing__hi17:00
zhubingbing__i have 2 problems about elk17:00
*** haleyb_ has quit IRC17:00
zhubingbing__1.https://blueprints.launchpad.net/kolla/+spec/bp-elasticsearch-upgrade17:00
*** sp__ has quit IRC17:00
zhubingbing__2.https://blueprints.launchpad.net/kolla/+spec/heka-deprecation17:00
*** egonzalez90 has left #openstack-meeting-417:01
*** bobh has quit IRC17:01
*** zhubingbing__ has left #openstack-meeting-417:02
*** bobh has joined #openstack-meeting-417:04
*** makowals has joined #openstack-meeting-417:06
*** thorst has joined #openstack-meeting-417:06
*** thorst_ has joined #openstack-meeting-417:07
*** beagles is now known as beagles-brb17:08
*** sdake_ is now known as sdake17:09
*** thorst has quit IRC17:11
*** thorst_ has quit IRC17:11
*** ricolin has quit IRC17:15
*** yamahata has quit IRC17:17
*** portdirect is now known as portdirect_away_17:21
*** portdirect_away_ is now known as portdirect_back_17:23
*** mandre has left #openstack-meeting-417:26
*** duonghq has quit IRC17:27
*** hogepodge has joined #openstack-meeting-417:28
*** matrohon has quit IRC17:30
*** sambetts is now known as sambetts|afk17:30
*** hogepodge has quit IRC17:33
*** nkrinner is now known as nkrinner_afk17:37
*** reedip_ has quit IRC17:39
*** hogepodge has joined #openstack-meeting-417:43
*** slaweq_ has quit IRC17:44
*** yamamoto has joined #openstack-meeting-417:45
*** slaweq_ has joined #openstack-meeting-417:46
*** matrohon has joined #openstack-meeting-417:46
*** degorenko is now known as _degorenko|afk17:50
*** yamamoto has quit IRC17:52
*** sdake has quit IRC17:54
*** iberezovskiy is now known as iberezovskiy|off17:55
*** dave-mccowan has joined #openstack-meeting-417:56
*** haleyb_ has joined #openstack-meeting-417:56
*** dave-mccowan has quit IRC17:57
*** ralonsoh has quit IRC18:00
*** haleyb_ has quit IRC18:01
*** beagles-brb is now known as beagles18:02
*** parora has joined #openstack-meeting-418:13
*** slaweq_ has quit IRC18:13
*** iyamahat has quit IRC18:13
*** pbourke has quit IRC18:14
*** pbourke has joined #openstack-meeting-418:14
*** prateek_ has quit IRC18:16
*** portdirect_back_ is now known as portdirect_18:20
*** prateek_ has joined #openstack-meeting-418:24
*** unicell has joined #openstack-meeting-418:24
*** unicell has quit IRC18:25
*** unicell has joined #openstack-meeting-418:27
*** parora has quit IRC18:27
*** iyamahat has joined #openstack-meeting-418:35
*** markvoelker has quit IRC18:35
*** prateek_ has quit IRC18:38
*** bpokorny has joined #openstack-meeting-418:46
*** sayantani01 has quit IRC18:46
*** portdirect_ is now known as portdirect_away18:46
*** dave-mccowan has joined #openstack-meeting-418:49
*** yamahata has joined #openstack-meeting-418:55
*** dave-mcc_ has joined #openstack-meeting-418:59
*** sukhdev has quit IRC19:01
*** ad_rien_ has joined #openstack-meeting-419:01
*** dave-mccowan has quit IRC19:02
*** jovon has joined #openstack-meeting-419:08
*** ad_rien_ has quit IRC19:08
*** asettle has quit IRC19:19
*** jichen has joined #openstack-meeting-419:21
*** beagles is now known as beagles_brb19:21
*** dtardivel has quit IRC19:24
*** ad_rien_ has joined #openstack-meeting-419:27
*** makowals has quit IRC19:29
*** therve has left #openstack-meeting-419:34
*** bpokorny has quit IRC19:45
*** bpokorny has joined #openstack-meeting-419:46
*** dave-mcc_ has quit IRC19:49
*** betherly_ has joined #openstack-meeting-419:50
*** bpokorny has quit IRC19:50
*** beagles_brb is now known as beagles19:55
*** ad_rien_ has quit IRC19:56
*** haleyb_ has joined #openstack-meeting-419:58
*** haleyb_ has quit IRC20:03
*** rods has quit IRC20:05
*** rods has joined #openstack-meeting-420:07
*** inc0 has quit IRC20:16
*** slaweq_ has joined #openstack-meeting-420:27
*** Sukhdev has joined #openstack-meeting-420:36
*** betherly_ is now known as betherly20:41
*** armax has quit IRC20:43
*** armax has joined #openstack-meeting-420:45
*** armax has quit IRC20:45
*** v1k0d3n has quit IRC20:46
*** baoli has quit IRC20:51
*** baoli has joined #openstack-meeting-420:51
*** flaper87 has quit IRC20:52
*** sdake has joined #openstack-meeting-420:54
*** baoli has quit IRC20:56
*** sbezverk has joined #openstack-meeting-420:59
*** vishnoianil has joined #openstack-meeting-421:04
*** spotz is now known as spotz_zzz21:10
*** bpokorny has joined #openstack-meeting-421:11
*** ad_rien_ has joined #openstack-meeting-421:11
*** inc0 has joined #openstack-meeting-421:13
*** unicell has quit IRC21:14
*** unicell1 has joined #openstack-meeting-421:21
*** armax has joined #openstack-meeting-421:27
*** jovon has quit IRC21:28
*** Jeffrey4l has quit IRC21:35
*** Jeffrey4l has joined #openstack-meeting-421:35
*** thorst_ has joined #openstack-meeting-421:47
*** srwilkers_ has quit IRC21:51
*** jovon has joined #openstack-meeting-422:16
*** thorst_ has quit IRC22:20
*** matrohon has quit IRC22:33
*** Julien-zte has joined #openstack-meeting-422:34
*** vishnoianil has quit IRC22:34
*** limao has quit IRC22:36
*** jichen has quit IRC22:36
*** JRobinson__ has joined #openstack-meeting-422:37
*** JRobinson__ has quit IRC22:38
*** JRobinson__ has joined #openstack-meeting-422:39
*** beagles is now known as beagles_brb22:43
*** vishnoianil has joined #openstack-meeting-422:47
*** inc0 has quit IRC22:51
*** ad_rien_ has quit IRC22:53
*** vishnoianil has quit IRC22:53
*** vishnoianil has joined #openstack-meeting-423:08
*** beagles_brb is now known as beagles23:14
*** bobh has quit IRC23:24
*** JRobinson__ is now known as JRobinson__afk23:26
*** dkehn__ has quit IRC23:29
*** bobh has joined #openstack-meeting-423:33
*** sdake has quit IRC23:37
*** bobh has quit IRC23:38
*** Julien-zte has quit IRC23:38
*** sdake has joined #openstack-meeting-423:40
*** lamt has quit IRC23:43
*** JRobinson__afk is now known as JRobinson__23:45
*** LouisF has joined #openstack-meeting-423:59

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