Wednesday, 2015-11-18

*** rbak has quit IRC00:04
*** Sam-I-Am has joined #openstack-meeting-400:09
*** Sam-I-Am has left #openstack-meeting-400:09
*** jckasper has joined #openstack-meeting-400:12
*** harshs has quit IRC00:17
*** dwalleck has joined #openstack-meeting-400:26
*** yamamoto has joined #openstack-meeting-400:30
*** dwalleck has quit IRC00:30
*** harshs has joined #openstack-meeting-400:31
*** harshs_ has joined #openstack-meeting-400:34
*** CheKoLyN has quit IRC00:35
*** harshs has quit IRC00:36
*** harshs_ is now known as harshs00:36
*** harshs has quit IRC00:37
*** Sukhdev has quit IRC00:41
*** itisha has quit IRC00:41
*** Sukhdev has joined #openstack-meeting-400:43
*** harshs has joined #openstack-meeting-400:44
*** Sukhdev has quit IRC00:44
*** harshs has quit IRC00:44
*** yamamoto has quit IRC00:48
*** iyamahat has quit IRC00:48
*** mestery has quit IRC00:50
*** shimura_ken has joined #openstack-meeting-400:52
*** armax has joined #openstack-meeting-400:57
*** SimonChung has joined #openstack-meeting-401:01
*** SimonChung2 has quit IRC01:01
*** SimonChung1 has joined #openstack-meeting-401:02
*** SimonChung has quit IRC01:02
*** SimonChung has joined #openstack-meeting-401:03
*** SimonChung1 has quit IRC01:03
*** woodard has joined #openstack-meeting-401:03
*** woodard has quit IRC01:13
*** SimonChung has quit IRC01:14
*** limao has joined #openstack-meeting-401:26
*** Swami has quit IRC01:28
*** baohua has joined #openstack-meeting-401:30
*** ivar-laz_ has joined #openstack-meeting-401:32
*** ivar-lazzaro has quit IRC01:36
*** yamamoto has joined #openstack-meeting-401:37
*** ivar-laz_ has quit IRC01:37
*** ivar-lazzaro has joined #openstack-meeting-401:38
*** ivar-lazzaro has quit IRC01:38
*** ivar-lazzaro has joined #openstack-meeting-401:39
*** ivar-lazzaro has quit IRC01:39
*** tpeoples_ is now known as tpeoples01:40
*** ivar-lazzaro has joined #openstack-meeting-401:40
*** ivar-lazzaro has quit IRC01:52
*** harshs has joined #openstack-meeting-401:52
*** mestery has joined #openstack-meeting-402:00
*** prashantD has quit IRC02:01
*** harshs has quit IRC02:02
*** baoli has joined #openstack-meeting-402:03
*** tfukushima has joined #openstack-meeting-402:07
*** bpokorny_ has joined #openstack-meeting-402:09
*** lazy_prince has joined #openstack-meeting-402:10
*** banix has joined #openstack-meeting-402:11
*** bpokorny has quit IRC02:12
*** bpokorny_ has quit IRC02:13
*** baoli_ has joined #openstack-meeting-402:25
*** bobh has joined #openstack-meeting-402:25
*** baoli has quit IRC02:28
*** sdake has joined #openstack-meeting-402:28
*** dims_ has quit IRC02:30
*** s3wong has quit IRC02:36
*** fawadkhaliq has joined #openstack-meeting-402:42
*** shimura_ken has quit IRC02:51
*** shimura_ken has joined #openstack-meeting-402:52
*** shimura_ken has quit IRC02:53
*** bobh has quit IRC02:53
*** yantarou____ has joined #openstack-meeting-402:53
*** tfukushima has quit IRC02:55
*** mestery has quit IRC03:03
*** yantarou____ has quit IRC03:17
*** prashantD has joined #openstack-meeting-403:26
*** banix has quit IRC03:26
*** tpeoples is now known as tpeoples_away03:27
*** sdake has quit IRC03:35
*** gjayavelu has joined #openstack-meeting-403:35
*** yantarou has joined #openstack-meeting-403:36
*** sdake has joined #openstack-meeting-403:45
*** lazy_prince has quit IRC03:55
*** prashantD_ has joined #openstack-meeting-403:55
*** prashantD has quit IRC03:56
*** lazy_prince has joined #openstack-meeting-404:05
*** fawadkhaliq has quit IRC04:06
*** SimonChung has joined #openstack-meeting-404:17
*** SimonChung1 has joined #openstack-meeting-404:19
*** SimonChung has quit IRC04:21
*** gjayavelu has quit IRC04:27
*** fawadkhaliq has joined #openstack-meeting-404:27
*** lazy_prince has quit IRC04:30
*** amotoki has joined #openstack-meeting-404:34
*** markvoelker_ has quit IRC04:40
*** amotoki has quit IRC04:49
*** harshs has joined #openstack-meeting-404:52
*** harshs_ has joined #openstack-meeting-404:52
*** harshs has quit IRC04:56
*** harshs_ is now known as harshs04:56
*** amotoki has joined #openstack-meeting-405:01
*** amotoki has quit IRC05:10
*** sridhar_ram has joined #openstack-meeting-405:11
*** amotoki has joined #openstack-meeting-405:14
*** Sukhdev has joined #openstack-meeting-405:17
*** iyamahat has joined #openstack-meeting-405:18
*** prashantD_ has quit IRC05:19
*** krtaylor has quit IRC05:29
*** amotoki has quit IRC05:40
*** harshs_ has joined #openstack-meeting-405:43
*** harshs has quit IRC05:44
*** harshs_ is now known as harshs05:44
*** salv-orl_ has joined #openstack-meeting-405:50
*** Sukhdev has quit IRC05:50
*** amotoki has joined #openstack-meeting-405:51
*** salv-orlando has quit IRC05:53
*** IlyaG_ has quit IRC05:54
*** salv-orl_ has quit IRC05:55
*** galstrom_zzz is now known as galstrom05:56
*** sridhar_ram has quit IRC06:16
*** sridhar_ram has joined #openstack-meeting-406:17
*** pbourke has quit IRC06:18
*** iyamahat has quit IRC06:19
*** pbourke has joined #openstack-meeting-406:19
*** todin has left #openstack-meeting-406:21
*** clayton has quit IRC06:22
*** clayton has joined #openstack-meeting-406:23
*** numans has joined #openstack-meeting-406:24
*** sridhar_ram has left #openstack-meeting-406:26
*** angdraug has joined #openstack-meeting-406:30
*** irenab has joined #openstack-meeting-406:38
*** markvoelker has joined #openstack-meeting-406:40
*** markvoelker has quit IRC06:45
*** tfukushima has joined #openstack-meeting-406:45
*** salv-orlando has joined #openstack-meeting-406:51
*** MarkAtwood has joined #openstack-meeting-406:53
*** tfukushima has quit IRC06:56
*** angdraug has quit IRC07:03
*** tfukushima has joined #openstack-meeting-407:04
*** tfukushima has quit IRC07:10
*** salv-orlando has quit IRC07:12
*** nkrinner has joined #openstack-meeting-407:14
*** armax has quit IRC07:16
*** subscope has joined #openstack-meeting-407:24
*** harshs has quit IRC07:36
*** markvoelker has joined #openstack-meeting-407:41
*** markvoelker has quit IRC07:46
*** angdraug has joined #openstack-meeting-407:46
*** jmccrory has quit IRC07:49
*** jmccrory has joined #openstack-meeting-407:54
*** galstrom is now known as galstrom_zzz07:55
*** belmoreira has joined #openstack-meeting-407:57
*** matrohon has joined #openstack-meeting-408:05
*** MarkAtwood has quit IRC08:14
*** alex_didenko has joined #openstack-meeting-408:17
*** salv-orlando has joined #openstack-meeting-408:19
*** salv-orlando has quit IRC08:27
*** yamamoto has quit IRC08:28
*** nihilifer has quit IRC08:36
*** nihilifer has joined #openstack-meeting-408:36
*** fawadkhaliq has quit IRC08:41
*** fawadkhaliq has joined #openstack-meeting-408:42
*** numans has quit IRC08:47
*** zeih has joined #openstack-meeting-408:53
*** zeih has quit IRC08:56
*** jpekkari has joined #openstack-meeting-408:57
*** numans has joined #openstack-meeting-408:57
*** fawadkhaliq has quit IRC08:57
*** zeih has joined #openstack-meeting-408:59
*** bogdando has joined #openstack-meeting-409:01
*** zeih has quit IRC09:12
*** zeih has joined #openstack-meeting-409:14
*** _degorenko is now known as degorenko09:14
*** Piet has quit IRC09:21
*** salv-orlando has joined #openstack-meeting-409:26
*** zeih has quit IRC09:35
*** salv-orlando has quit IRC09:36
*** salv-orlando has joined #openstack-meeting-409:37
*** zeih has joined #openstack-meeting-409:38
*** yamamoto has joined #openstack-meeting-409:39
*** markvoelker has joined #openstack-meeting-409:42
*** tfukushima has joined #openstack-meeting-409:43
*** yamamoto has quit IRC09:43
*** baohua has quit IRC09:45
*** markvoelker has quit IRC09:46
*** tfukushima has quit IRC09:50
*** spredzy|afk is now known as spredzy10:04
*** zeih has quit IRC10:05
*** dzamboni has joined #openstack-meeting-410:18
*** yamamoto has joined #openstack-meeting-410:26
*** yamamoto has quit IRC10:31
*** fawadkhaliq has joined #openstack-meeting-410:36
*** qwebirc72848 has joined #openstack-meeting-410:36
*** amotoki has quit IRC10:47
*** limao has quit IRC10:52
*** alex_didenko has quit IRC10:55
*** bogdando has quit IRC10:56
*** dims has joined #openstack-meeting-411:07
*** ziggypup has joined #openstack-meeting-411:10
*** ziggypup has left #openstack-meeting-411:10
*** dims has quit IRC11:12
*** prashantD has joined #openstack-meeting-411:17
*** dims has joined #openstack-meeting-411:18
*** prashantD has quit IRC11:21
*** bogdando has joined #openstack-meeting-411:31
*** alex_didenko has joined #openstack-meeting-411:31
*** yamamoto has joined #openstack-meeting-411:32
*** wojdev has joined #openstack-meeting-411:35
*** yamamoto has quit IRC11:36
*** subscope has quit IRC11:41
*** subscope has joined #openstack-meeting-411:42
*** markvoelker has joined #openstack-meeting-411:43
*** markvoelker has quit IRC11:47
*** amotoki has joined #openstack-meeting-411:48
*** amotoki has quit IRC11:49
*** subscope has quit IRC12:20
*** subscope has joined #openstack-meeting-412:21
*** subscope has quit IRC12:21
*** acabot has joined #openstack-meeting-412:30
*** baohua has joined #openstack-meeting-412:33
*** yamamoto has joined #openstack-meeting-412:39
*** fawadkhaliq has quit IRC12:42
*** markvoelker has joined #openstack-meeting-412:43
*** markvoelker has quit IRC12:48
*** acabot has quit IRC12:56
*** angdraug has quit IRC13:05
*** tfukushima has joined #openstack-meeting-413:06
*** tfukushima has quit IRC13:07
*** markvoelker has joined #openstack-meeting-413:09
*** jckasper has quit IRC13:13
*** nihilifer has quit IRC13:14
*** klamath has joined #openstack-meeting-413:14
*** klamath has quit IRC13:14
*** klamath has joined #openstack-meeting-413:15
*** nihilifer has joined #openstack-meeting-413:15
*** nihilifer has quit IRC13:15
*** nihilifer has joined #openstack-meeting-413:16
*** angdraug has joined #openstack-meeting-413:21
*** prashantD has joined #openstack-meeting-413:25
*** irenab_ has joined #openstack-meeting-413:26
*** irenab has quit IRC13:27
*** irenab_ is now known as irenab13:27
*** prashantD has quit IRC13:29
*** acabot has joined #openstack-meeting-413:29
*** prashantD has joined #openstack-meeting-413:30
*** prashantD has quit IRC13:31
*** woodard has joined #openstack-meeting-413:34
*** kbyrne has quit IRC13:36
*** kbyrne has joined #openstack-meeting-413:43
*** igordcard has joined #openstack-meeting-413:44
*** acabot has quit IRC13:45
*** acabot has joined #openstack-meeting-413:45
*** krtaylor has joined #openstack-meeting-413:46
*** acabot_ has joined #openstack-meeting-413:49
*** acabot has quit IRC13:52
*** jed56 has joined #openstack-meeting-413:54
*** julim has joined #openstack-meeting-413:55
*** jwcroppe_ has joined #openstack-meeting-413:55
*** gjayavelu has joined #openstack-meeting-413:57
*** alexchadin has joined #openstack-meeting-413:57
*** sudipto has joined #openstack-meeting-413:58
*** alexstav has joined #openstack-meeting-413:59
*** MarkAtwood has joined #openstack-meeting-413:59
*** bzhou has joined #openstack-meeting-414:00
*** samarinvv has joined #openstack-meeting-414:00
acabot_#startmeeting watcher14:01
*** tpeoples_away is now known as tpeoples14:01
openstackMeeting started Wed Nov 18 14:01:04 2015 UTC and is due to finish in 60 minutes.  The chair is acabot_. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: watcher)"14:01
openstackThe meeting name has been set to 'watcher'14:01
acabot_hi14:01
bzhouhi14:01
alexstavo/14:01
alexchadino/14:01
jwcroppe_o/14:01
*** ostroverkhov has joined #openstack-meeting-414:01
tpeopleso/14:01
samarinvvhi14:01
acabot_our agenda for today #link https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#11.2F18.2F201514:01
sudiptoo/14:01
jed56hi14:02
sballeo/14:02
*** brunograz has joined #openstack-meeting-414:02
brunograzo/14:02
acabot_feel free to add anything you like to discuss14:02
*** ashavskiy has joined #openstack-meeting-414:02
*** vmahe_ has joined #openstack-meeting-414:02
acabot_is Nishi here ?14:02
acabot_lets move on to our first topic14:03
acabot_#topic annoucements14:03
*** openstack changes topic to "annoucements (Meeting topic: watcher)"14:03
acabot_as mentioned in the agenda, we have 2 ad hoc meetings planned regarding the POC and academic contributions14:04
*** seanmurphy has joined #openstack-meeting-414:04
acabot_any other announcement ?14:04
*** ShillaSaebi has joined #openstack-meeting-414:05
*** ShillaSaebi has left #openstack-meeting-414:05
sballeI am still working with BU in the meetup14:05
sballeI should know tomorrow if they can host it.14:05
acabot_ok great14:05
*** limao has joined #openstack-meeting-414:05
jwcroppe_cool14:05
sballeThey have a workshp tomorrow and that has taken all the nergy they have14:05
acabot_can you remind us the dates ?14:05
*** jckasper has joined #openstack-meeting-414:05
sballeone sec14:05
alexchadinHello from Moscow, Servionica. We are working on rst-specs for overload-underload algorithms.14:06
*** vtech has joined #openstack-meeting-414:06
sballe1/20-21 or 2/3-4 0r 1/26-2714:07
acabot_alexchadin : great thanks, please send a public review as soon as you can14:07
sballealexchadin: +114:07
alexchadinWhere should we publish it?14:07
alexchadinlaunchpad?14:07
jwcroppe_review.openstack.org (watcher-specs project) and launchpad14:08
*** bapalm has joined #openstack-meeting-414:08
alexchadinjwcroppe_: yeap, thanks!14:08
sballehere is an example: https://review.openstack.org/#/c/246363/14:08
*** nishi has joined #openstack-meeting-414:09
acabot_in /specs/mitaka/approved/watcher-overload-underload.rst14:09
sballeacabot_: approved?14:09
*** ashavskiy has quit IRC14:09
sballeDoes it have to be reviewed before it is approved to move in "under approve"?14:10
jwcroppe_yes, approved ... it won't be in repo until it's merged14:10
nishiwhat has been approves14:10
*** Kevin_Zheng has joined #openstack-meeting-414:10
acabot_sable : yes sorry we only have a "implemented" folder14:10
jwcroppe_sballe: so it's implicitly approved if we merge it :)14:10
sballenishi: our poc is approved to move n14:10
bzhoumerged means approved:-)14:11
nishiok14:11
acabot_alexchadin : can we say your proposition is already "implemented" ?14:11
*** pmesserli has joined #openstack-meeting-414:11
Kevin_Zhengsorry Im late14:11
*** vincentfrancoise has joined #openstack-meeting-414:11
bzhouwelcome Kevin14:11
tpeoplesacabot_:  if it's not integrated into watcher i don't think it's implemented14:11
acabot_ok so lets do it in "approved" and we will merge it in the future14:11
*** angdraug has quit IRC14:12
tpeoples+114:12
sballebzhou: I understand. I just wanted to make sure it was in line with the watcher pylosophy around being just a plug-in before it is approved.14:12
jwcroppe_+114:12
alexchadinacabot_: implemented in watcher?14:12
acabot_alexchadin : forgive it ;)14:13
sballealexchadin: your stuff will have to be integrated inthe watcher framework. right?14:13
*** MarkAtwood has quit IRC14:13
sballeI am looking to seeing the specs that describe how everything fits within watcher14:13
acabot_sballe : +114:14
acabot_#topic review action items14:14
*** openstack changes topic to "review action items (Meeting topic: watcher)"14:14
acabot_jed56 : can you give us an update regarding telemetry integration ?14:15
alexstavsballe: For now it works with OpenStack Nova Compute, but we are planing to integrate in with watcher. The problem is to get stats from compute-nodes, but it is another watcher-blueprint.from14:15
bzhouA general comment for Telemetry integration:14:15
bzhouThe code is going to remove datasource (concept) and influxdb store and ONLY depends on ceilometer to provide meters.14:15
jed56yes14:15
jed56we have a first version we need to check that everying is working14:15
sballe+114:15
jed56we also start cleanup a bit the code14:16
sballejed56: one you have checked it let bzhou and junjie know14:16
sballemann too many typos this morning. I need more coffee14:16
jed56sballe: yes I hope before the end of the week14:16
sballeperfect14:16
*** iyamahat has joined #openstack-meeting-414:17
bzhoujed56: is there any background that we remove datasource and influxdb as store?14:17
jed56bzhou : yes exaclty14:17
*** limao has quit IRC14:17
bzhouI'm not sure if we could get every meters only from ceilometer14:17
jed56yes but we can custom metrics in ceilometer14:17
jed56add14:17
*** ashavskiy has joined #openstack-meeting-414:17
sballealexstav: we cannot merge your code if it doesn't fit in the wathcer framework which is why I am insisting on that point. But I am sure you understand that14:17
acabot_telemetry v2 allows us to create new metrics and store them14:18
sballe+114:18
jed56we don't to maintain influxdb store14:18
jed56because ceilosca project and ceilometer14:18
*** dtardivel has joined #openstack-meeting-414:19
bzhouso are we also going to drop watcher-metering-drivers?14:19
*** yamamoto has quit IRC14:19
sballejed56: next cycle I would like for us to add support for Monasca as the source of telemetry too14:19
jed56we can still use metering driver to push metrics into ceilometer14:19
jed56but we have a overlap with the project monasca14:19
alexchadinsballe: we are going to make patch with our spec-improvements14:19
jed56an14:19
*** skolekonov has left #openstack-meeting-414:20
jed56I think we don't to focus our work in the monitoring14:20
acabot_bzhou : this is something we will keep to inject additional metrics in telemetry but for devstack support, we need to give up our metering chain14:20
sballealexchadin: will you contribute to the watcher framework too?14:20
jed56want14:20
alexchadinsballe: yes, we will14:21
sballealexchadin: great!14:21
*** ashavskiy has quit IRC14:21
jed56sballe : this the idea to support Monasca and Ceilometer14:21
sballeMonasca will eventually take over IMHO14:22
acabot_a spec is available for review https://review.openstack.org/#/c/246363/14:22
sballeBut not today14:22
alexchadinsballe: Before we do that, we would like to make sure our specs have been approved by you:)14:22
sballe:)14:22
bzhouacabot_: why for devstack support, we need to give up our metering chain? Because watcher-metering-drivers is not managed by openstack?14:23
sballebzhou: we also thought that Ceilometer was the way to go for devstack since it is an openstak project and already part od devstack14:23
acabot_bzhou : because deploying Watcher today is too complex and we need to provide a quick install running on top of telemetry (available in devstack)14:24
*** katya has joined #openstack-meeting-414:24
jwcroppe_acabot_: +114:25
acabot_bzhou : watcher-metering-drivers will never be maintained by OpenStack as Ceilometer agent exists already14:25
sballeI am assuming if you want you can still use the watcher-metering-drivers with devstack but on a do it yourself basis14:25
bzhouSo the publisher is also going to be dropped, right?14:25
Kevin_ZhengI agree, we it will be better to focus on the main task14:25
Kevin_ZhengWe can make use of the existing project14:26
bzhoujust want to make sure I understand the architecture change14:26
tpeoplesspeaking of devstack, i have finally freed up from my ibm work and can start working on the devstack plugin shell script14:26
*** jmckind has joined #openstack-meeting-414:26
jed56bzhou : we can still use it to push it in ceilometer for specific metrics like kwapi14:26
acabot_bzhou : again we won't drop it, we will simply add Telemetry integration as a default solution for collecting metrics14:26
*** ashavskiy has joined #openstack-meeting-414:27
acabot_bzhou : the idea is to have Telemetry working as a "common framework" for metrics collection14:27
*** angdraug has joined #openstack-meeting-414:27
bzhouacbot_: got it, thanks. Will the project watcher-metering be maintained by OpenStack?14:28
acabot_bzhou : watcher-metering is maintained by b-com (on our own github repo)14:28
sballeI am assuming that if wathcer needs it we can fold it in under watcher14:29
sballeacabot_: ^^^14:29
tpeoples+114:29
acabot_sable : of course14:29
acabot_please review the proposed code here https://review.openstack.org/#/c/246363/14:30
*** ashavskiy has joined #openstack-meeting-414:30
sballethis is the spec.14:30
acabot_next topic is loading optimization strategies into watcher14:30
bzhouacabot_: thanks. So we may need to change the architecture doc:-)14:31
sballe+114:31
acabot_sorry, here is the link https://review.openstack.org/#/c/246534/14:31
sballewould it make sense to start a new arch doc kind of a v2?14:31
*** ashavskiy has quit IRC14:31
acabot_bzhou : yes vamp is working on it14:31
acabot_bzhou : vamp sorry14:32
bzhougreat14:32
*** edleafe has joined #openstack-meeting-414:32
acabot_sable : a new wiki page ?14:32
* edleafe joins late 14:33
sballemy nick is sballe14:33
sballeacabot_: ^^ FYI14:33
sballeyes a new wiki page would work14:33
*** ashavskiy has joined #openstack-meeting-414:33
sballeI like to keep the history of the architecture and how it evolves14:34
vmahe_FYI vamp is vmahe :-)14:34
sballe:-)14:34
bzhou:-)14:34
acabot_#action acabot_ start a new wiki page for Watcher architecture v214:34
sballeacabot_: get all our nicks wrng this morning. he needs more coffee'14:35
jed56lol14:35
jwcroppe_As we discussed, we want Watcher to be able to be fed custom metrics - but the reference arch should support basic telemetry/ceilometer.   Agree?14:35
acabot_sorry for that, my IRC client is cleaning all your nicks after sending the message...14:35
acabot_jwcroppe_ : agree14:36
sballe+114:36
Kevin_Zheng+114:36
bzhou+114:36
vmahe_+114:36
nishi+114:36
jwcroppe_cool14:36
jed56+214:36
edleafe+114:36
bzhoubut one question: we need to define a framework14:36
sballebzhou: +114:36
sballeMy thoughts were taht whatever is in Ceilomter can be used.14:37
acabot_bzhou : not sure to understand, what do you mean by a framework ?14:37
*** jckasper has quit IRC14:37
sballebut we do need a way to bring extra telemetry in14:37
bzhouI mean people can use it to easily feed custom metrics14:38
bzhoumaybe not from Telemtry14:38
sballeso are you saying we need to keep the wathcer metric agrent for that use case?14:38
acabot_bzhou : to my understanding with Telemetry v2 API, anyone can add any custom metrics in Telemetry14:38
jed56bzhou : you can use ceilometer to add custom metrics or14:38
jed56monasca14:39
acabot_bzhou : so except if you dont want to use Telemetry, you will never need our Watcher metering chain14:39
*** Swami has joined #openstack-meeting-414:39
bzhouagree14:40
acabot_ok lets move on loading strategies in Watcher14:40
jed56exactly14:40
dtardivelacabot_ +114:40
sballe+114:41
acabot_the review is here https://review.openstack.org/#/c/245903/14:41
acabot_I will add it to the agenda14:41
Kevin_ZhengLooks cool14:42
vmahe_FYI : we'll provide more details regarding the integration of Telemetry v2 in the associated spec and the impacts on the current Watcher components14:42
sballe+114:42
*** bapalm has quit IRC14:43
*** angdraug has quit IRC14:43
*** angdraug has joined #openstack-meeting-414:43
vmahe_See https://review.openstack.org/#/c/24636314:43
*** bapalm has joined #openstack-meeting-414:43
acabot_thanks vmahe_, can you jump on documentation topic ?14:44
vmahe_all right14:44
vincentfrancoiseSo regarding the loading of new strategies14:44
*** fawadkhaliq has joined #openstack-meeting-414:44
vmahe_I'm currently writing a Glossary to make sure that every one speaks the same language14:45
vincentfrancoiseit's still in progress14:45
vincentfrancoisewaiting for proper testing14:45
sballevincentfrancoise: I am assumign doc ill be added too14:45
vincentfrancoisesballe: Yes, there's a plugins.rst added in this changeset explaining how to implement a new strategy14:46
sballeI believe we will be testing it. taht was one of the actinos items we wee given at the poc meeting.14:46
sballecan you ping us when it is ready to be tested?14:46
bzhousballe:+114:46
vincentfrancoiseIn parrallel, we are thinking about adding a gloassary to the documentation to lay down the right terminology to use throughout the code / doc14:47
vincentfrancoisesee https://review.openstack.org/#/c/246370/14:47
*** ashavskiy has quit IRC14:47
vmahe_We need to mae sure everyone agrees on words such as "Action", "Meta-Action", ...14:48
tpeoplesi will take a look at that vincentfrancoise14:48
*** ilya has joined #openstack-meeting-414:48
vmahe_I'm currently reviewing it and will push a new patch set very soon14:48
*** ilya is now known as iashavskiy14:48
*** jckasper has joined #openstack-meeting-414:49
vmahe_I also did some testing with the tool used by the Nova team to generate some architecture diagrams14:49
vmahe_Which is named Dia14:49
*** iyamahat has quit IRC14:50
vmahe_they have put in the repo a source directory for the diagrams which is used to generate some SVG or PNG images14:50
*** jpekkari has quit IRC14:50
vmahe_The issue with Dia is that it is not human readable source code.14:50
vmahe_I need to do some testing also with PlantUML (which is also free)14:51
vmahe_and makes it possible to do any UML diagrams : class diagrams, sequence diagrams, ...14:51
sballesounds interesting14:52
*** sigmavirus24_awa is now known as sigmavirus2414:52
acabot_sballe : you plan to submit a spec for energy minimization POC ?14:52
sballeacabot_: yes Iwill be working with nishi, bzhou and the team on it. After yesterday's meeting we just needed to do some last minute adjustement to the poc14:52
acabot_sballe : great, please fill it in approved folder for review14:53
sballeI'll work on it as soon as I am back from SC'1514:53
vmahe_there is an extension for Sphynx which makes it possible to include PlantUML source code directly in the RST files : https://pypi.python.org/pypi/sphinxcontrib-plantuml14:53
acabot_#topic Blueprint/Bug Review and Discussion14:54
*** openstack changes topic to "Blueprint/Bug Review and Discussion (Meeting topic: watcher)"14:54
nishiwhat do we need to fill14:54
*** vtech has quit IRC14:54
acabot_nishi : you need to feel a spec file based on templates availble on watcher-specs14:54
acabot_fill not feel ;-)14:54
nishiok14:54
*** seanmurphy has quit IRC14:54
acabot_regarding blueprints14:55
*** Swami has quit IRC14:55
acabot_vmahe_ has submitted a new one https://blueprints.launchpad.net/watcher/+spec/watcher-add-actions-via-conf14:55
sballenishi: https://github.com/openstack/watcher-specs14:55
sballeI'll work with you14:55
nishigreat14:56
vmahe_we need to agree on the mechanism for adding new actions to Watcher14:56
nishiwhen do you come back from SC14:56
sballetomorow14:56
nishiok14:56
bzhounishi: I could help too if you need14:57
nishiook14:57
*** akwasnie has joined #openstack-meeting-414:57
Kevin_ZhengI'm also available :)14:57
sballelol14:57
acabot_jwcroppe_ sballe : can you look at this BP before next meeting to fix priority ?14:58
*** harshs has joined #openstack-meeting-414:58
acabot_#action jwcroppe_ sballe acabot_ set priority for BP https://blueprints.launchpad.net/watcher/+spec/watcher-add-actions-via-conf14:58
acabot_sorry but we wont have time for open discussions today14:58
bzhouacabot_: Kevin_Zheng wants to work on bp: https://blueprints.launchpad.net/watcher/+spec/make-watcher-use-graduated-oslo-lib14:58
*** brunograz has quit IRC14:59
*** Swami has joined #openstack-meeting-414:59
jwcroppe_will do14:59
acabot_bzhou : right there is review in progress on it, I will set it as started14:59
sballeacabot_: will do14:59
bzhouthanks14:59
acabot_bzhou : https://review.openstack.org/#/c/246153/ right ?15:00
Kevin_Zhengacabot: thanks15:00
*** vtech has joined #openstack-meeting-415:00
acabot_thank you guys for your time15:00
sballewe are out of time15:00
acabot_#endmeeting15:00
sballehave a great day!15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Wed Nov 18 15:00:44 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/watcher/2015/watcher.2015-11-18-14.01.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/watcher/2015/watcher.2015-11-18-14.01.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/watcher/2015/watcher.2015-11-18-14.01.log.html15:00
*** rbak has joined #openstack-meeting-415:01
tpeoplesttyl15:01
*** bruno has joined #openstack-meeting-415:01
bzhouhave a great day!15:01
*** bruno is now known as Guest210615:01
samarinvvHave a nice day!15:01
jed56thanks you too15:01
jwcroppe_ttyl15:02
*** seanmurphy has joined #openstack-meeting-415:03
*** alexchadin has quit IRC15:03
*** angdraug has quit IRC15:03
*** iashavskiy has quit IRC15:04
*** jckasper has quit IRC15:04
*** bobh has joined #openstack-meeting-415:05
*** subscope has joined #openstack-meeting-415:08
*** samarinvv has quit IRC15:10
*** harshs has quit IRC15:10
*** bzhou has quit IRC15:11
*** ostroverkhov has quit IRC15:12
*** cloudtrainme has joined #openstack-meeting-415:16
*** jckasper has joined #openstack-meeting-415:16
*** sarob has quit IRC15:16
*** sballe has quit IRC15:17
*** d34dh0r53 has quit IRC15:17
*** angdraug has joined #openstack-meeting-415:17
*** d34dh0r53 has joined #openstack-meeting-415:17
*** alexstav has quit IRC15:17
*** sballe has joined #openstack-meeting-415:18
*** akwasnie has quit IRC15:19
*** sarob has joined #openstack-meeting-415:19
*** yamamoto has joined #openstack-meeting-415:20
*** baohua has quit IRC15:20
*** blahRus has joined #openstack-meeting-415:20
*** sdake has quit IRC15:20
*** sdake has joined #openstack-meeting-415:20
*** sudipto has quit IRC15:20
*** mhoppal has joined #openstack-meeting-415:24
*** mhoppal has left #openstack-meeting-415:25
*** yamamoto has quit IRC15:25
*** jwagner_away is now known as jwagner15:27
*** salv-orlando has quit IRC15:30
*** salv-orlando has joined #openstack-meeting-415:31
*** lazy_prince has joined #openstack-meeting-415:32
*** duartea has quit IRC15:34
*** katya has quit IRC15:36
*** acabot_ has quit IRC15:42
*** bpokorny has joined #openstack-meeting-415:44
*** qwebirc72848 has quit IRC15:47
*** Sukhdev has joined #openstack-meeting-415:48
*** iyamahat has joined #openstack-meeting-415:58
*** yamahata has joined #openstack-meeting-415:59
*** gjayavelu has quit IRC16:00
*** CreaNet has joined #openstack-meeting-416:05
CreaNethi16:05
*** seanmurphy has quit IRC16:06
*** vtech has quit IRC16:06
*** acabot has joined #openstack-meeting-416:07
*** banix has joined #openstack-meeting-416:08
*** Guest2106 has quit IRC16:12
*** bruno_ has joined #openstack-meeting-416:15
*** akwasnie has joined #openstack-meeting-416:15
*** vtech has joined #openstack-meeting-416:16
*** stvnoyes has joined #openstack-meeting-416:20
*** fawadkhaliq has quit IRC16:20
*** rhallisey has joined #openstack-meeting-416:20
*** dims_ has joined #openstack-meeting-416:22
*** jwcroppe_ has quit IRC16:24
*** dims has quit IRC16:24
*** belmoreira has quit IRC16:24
*** yamamoto has joined #openstack-meeting-416:26
*** akwasnie has left #openstack-meeting-416:27
*** akwasnie_ has joined #openstack-meeting-416:27
*** macsz has joined #openstack-meeting-416:28
*** bmace has joined #openstack-meeting-416:28
*** CreaNet has quit IRC16:29
*** akwasnie_ has quit IRC16:29
sdake#startmeeting kolla16:30
openstackMeeting started Wed Nov 18 16:30:08 2015 UTC and is due to finish in 60 minutes.  The chair is sdake. Information about MeetBot at http://wiki.debian.org/MeetBot.16:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:30
*** openstack changes topic to " (Meeting topic: kolla)"16:30
openstackThe meeting name has been set to 'kolla'16:30
sdake#topic rollcall16:30
*** openstack changes topic to "rollcall (Meeting topic: kolla)"16:30
sdake\O/ !!16:30
SamYapleo/16:30
rhalliseyhello16:30
*** akwasnie has joined #openstack-meeting-416:30
nihiliferhi16:30
jpeelerhey16:30
akwasniehi16:30
stvnoyeshi16:30
sdakehey stvnoyes welcome - folks stvnoyes is one o f the  cats who wrote the cli along with bmace16:31
stvnoyesnice to be here16:31
sdakeI'll give it a couiple mor emins16:31
bmacehi16:31
SamYaplestvnoyes: good work on the cli btw. dont know if I have told you personally16:31
*** dmsimard has joined #openstack-meeting-416:32
stvnoyesthx16:32
pbourkehi16:33
sdake#topic 1.1.0 release16:33
*** openstack changes topic to "1.1.0 release (Meeting topic: kolla)"16:33
sdakeok folks I'd like to discuss what features we need for 1.1.0 which are not in the tracker16:33
sdakesec for tracker link:16:33
sdake#link https://launchpad.net/kolla/+milestone/mitaka-116:33
sdakeanything marked "Essential"16:33
sdakeplease open it up16:34
SamYaplesdake: thats for mitaka-116:34
SamYaplethe 1.1.0 is for liberty16:34
sdakewell yes we develop in mitaka-1 firt then backport16:34
sdakei was thinking our essential items for mitaka 1 would make up our 1.1.0 releae16:35
SamYaplewell things like zookeeper and drop root we arent backporting16:36
sdakethoswe aren't essential16:36
sdakethose are high16:36
SamYapleah i follow16:36
SamYaplesorry about the confusion16:36
sdakenp16:36
sdakeok now that everyone understands, is there anything misssing?16:36
*** numans has quit IRC16:36
sdakeso i can gte er in the tracker now16:37
*** britthouser has joined #openstack-meeting-416:37
sdakehey britthouser16:37
britthousersorry...late16:38
sdakewe are looking at the 1.1.0 feature list16:38
*** seanmurphy has joined #openstack-meeting-416:38
sdake#link https://launchpad.net/kolla/+milestone/mitaka-1 (ESSENTIAL marked items)16:38
*** Piet has joined #openstack-meeting-416:38
sdakeso I think we probably need someething around dupgrade of the openstack serices16:38
sdakedo folks agree or disagree with that?16:38
sdake(not infra services, but openstack-specific services like neutron, nova, glance, etc)16:39
SamYaplesdake: yea but that doesnt need to land before 1.1.016:39
sdakecool well if it doesn't needt o land for 1.1.0 then i'm good with leaving it out for now16:39
sdakeso sounds like we have th elist of essential features for mitaka-116:40
britthouserwe don't need it for 1.1.0 b/c we're not changing the pinning of any services in 1.1.0?16:40
sdakecan folks please take 1 blueprint each?16:40
nihilifersdake: but you mean creating new bp(s) for the upradability of OS services or what?16:40
sdakenihilifer yup16:40
SamYaplebritthouser: we are pinning the services to specific version in 1.1.0 (we arent currently doing that)16:40
dmsimardsdake: I'd love to see support for aodh in there16:40
sdakeaodh is what?16:40
dmsimardthe third component of telemetry16:40
dmsimardthere's ceilometer (collection), gnocchi (datastore) and aodh (alarming)16:41
sdakei see16:41
sdakeso our general lan is to finish th ebig tent in mitaka-2 and mitaka-316:41
dmsimardsure16:41
sdakeand reserve mitaka-1 for big ticket items16:41
dmsimardworks for me16:41
sdakestuf that could potentially take the entire cyclee16:41
*** acabot_ has joined #openstack-meeting-416:41
sdakedmsimard does gnocchi replace mongodb?16:42
dmsimardgnocchi interfaces mongodb16:42
*** jmccarthy has joined #openstack-meeting-416:42
* sdake sadfaces16:42
dmsimardgnocchi is the api between ceilometer and mongodb16:42
dmsimardkinda16:42
SamYapledmsimard: yea. the holdup for ceilometer is HA mongodb16:42
sdakeok well after this meeting  iwill record all of the big tent services a blueprints16:42
dmsimardsdake: +116:43
*** acabot has quit IRC16:43
sdakeSamYaple that isn't the ony holdup but one of them16:43
*** SimonChung1 has quit IRC16:43
sdakedmsimard the nfolks can take ownership of the big tent sesrvices as they like16:43
sdakeok so lets go through each of these individually16:44
*** inc0 has joined #openstack-meeting-416:44
sdake#link https://blueprints.launchpad.net/kolla/+spec/pin-ceph16:44
sdakethe job here is iterally installing a specific version of rpms16:44
sdakeinstead of yum install ceph16:44
sdakeyum install ceph-0.84.5-0.116:44
sdakeor something like that16:44
sdakei have checked upstream, they keep all copies and never deeleete old versions16:45
SamYaplefor the record, this is only affects centos16:45
sdakeso once we pin, we r egood to go16:45
sdakeSamYaple ack16:45
dmsimardsdake: that might not be true for delorean repos16:45
sdakeany takers on this super easy blueprint?16:45
dmsimardunless I'm mitaken16:45
sdakedmsimard w edodnt use delorean for ceph we use the ceph repos16:45
dmsimardmistaken*16:45
dmsimardright, we don't mirror ceph16:45
dmsimardmy bad16:46
*** britthouser has quit IRC16:46
sdake#link https://blueprints.launchpad.net/kolla/+spec/mariadb-lights-out16:46
sdakeif I wan't mistaken, I think Sam Yaple fearleessly agreeed to take this super complex blueprint on16:46
sdakewas that accurate?16:46
sdakeSamYaple ^^ ?16:47
*** lazy_prince has quit IRC16:47
SamYapleyea ill work on it. its just a special playbook instead of by hand stuff16:47
SamYaplethis means that if a lights out situation occurs then the operator must do special things16:47
sdakecool can you assign yourself16:47
*** lazy_prince has joined #openstack-meeting-416:47
sdake#link https://blueprints.launchpad.net/kolla/+spec/record-version16:48
sdakewas it pbourke who was working on recording the version tag?16:48
SamYaplesdake: that was me16:49
pbourkeno16:49
inc0how do we do it? did you agree on any approach?16:49
sdakenihilifer since you are likely to be our newest core, interested in that ceph hammer pinning blueprint? :)16:49
sdakewe have not agreed on  any approach but i'm not picky16:49
SamYapleinc0: no we didnt there is a WIP patch for the pinning16:49
nihiliferyep, you can assign this one to me16:49
sdakenihilifer pelae asign it to yourself16:49
sdakeif i assign it to you its not thee same a you assigning to yourself in launchpad tracker16:49
sdakei think you dont get credit for it in stackalytics and stuff16:50
nihilifersdake: i have no rights, you probably need to add me to kolla-drivers16:50
sdakenih will do after meeting ok?16:50
sdakeanyone can be in kolla-drivers16:50
nihilifersure16:50
inc0nihilifer, you should be able to assign yourself regardless of this16:50
sdakeinc0 not to bllueprints i think16:50
inc0launchpad is hard16:51
sdakeso the rest of mitaka-1 looks really solid16:51
sdakewe are making really good progressz16:51
nihiliferexactly, for bugs it's possible, for bps not16:51
inc0if noone works on version pinning I can take on it16:51
sdakeif I hadn't just jammed a bunch of work in at the last minute we would be on track :)16:51
inc0I'm back in action now;)16:51
sdakeinc0 you have #link https://blueprints.launchpad.net/kolla/+spec/sanity-check-container16:51
sdakewhich is "Not started"16:52
*** vincentfrancoise has quit IRC16:52
inc0ah so we pinned it to mitaka-116:52
inc0?16:52
inc0ok, I'll work on this one then16:52
sdakepinned what16:52
*** sudipto has joined #openstack-meeting-416:52
inc0bp for sanity16:52
sdakeoh you mean assignedto mitaka-1?16:52
inc0yeah16:52
sdakeI dont know who assigned it to mitak116:52
sdakeif it shoudl be in a different delivery chane it16:53
inc0I'm ok with that, I'll manage16:53
sdakeI just go off whats inthe tracker16:53
inc0let's keep it m-1, I'll start it right away16:53
sdakecool16:53
*** irenab has quit IRC16:54
sdake#topic using an extra base image instead of virtualenv16:54
*** openstack changes topic to "using an extra base image instead of virtualenv (Meeting topic: kolla)"16:54
*** britthouser has joined #openstack-meeting-416:54
sdakenihilifer this topic is for you to share your picture16:54
*** fawadkhaliq has joined #openstack-meeting-416:54
sdakefor th ezookeeper dependency16:54
sdakekazoo16:54
SamYaplesdake: nihilifer started on the virtualenv work16:55
*** fawadkhaliq has quit IRC16:55
SamYaplethat virtualenv stuff was a requirement from before kazoo16:55
*** fawadkhaliq has joined #openstack-meeting-416:55
sdakenihilifer did you decide to do virtualenv instead of the second thing?16:55
nihilifersdake: yeah, my first idea was https://drive.google.com/file/d/0B_WVU0_0Qd1rSUF6VUk3OXFrMGc/view?usp=sharing16:55
sdakethey are two orthogonal tasks16:55
nihiliferbut SamYaple convinced me to venvs16:55
sdakegot it16:55
nihiliferbecause kazoo is not the only problem16:55
sdakeso your not doing that anymore then?16:56
nihiliferyep, i'll go with venvs, mostly because ceph-common also brings conflicts to python libs16:56
inc0how about adding a hook for includes (here we go again..;))16:56
SamYapleand well have more as we add more features16:56
SamYapleconflicts that is16:56
sdakeok, nihilifer  can you please make a blueprint16:56
sdakeand dget it put in mitaka-116:56
inc0virtualenvs will only work for python packages16:56
sdakewe will probably slip it o mitaka-216:56
nihiliferi created b16:56
sdake(medium priority pelaes)16:56
nihiliferbp*16:57
nihiliferand i can move it to milestone16:57
sdakegood pelase do that - to d o that you need to be part of the drivers group16:57
SamYaplesdake: the work is already started16:57
sdakegood16:57
SamYaplei imagine itll merge in less than 2 weeks16:57
sdakewhatever works16:57
sdakedecember 4th is deadline for mitaka-116:57
*** prashantD has joined #openstack-meeting-416:58
sdakesince our gates are workign well now (yay) i'm going to stay pretty strict on the release dates16:58
inc0damn, no more merge-fests-after-release-like-there-is-no-tomorrow16:58
sdakeinc0 lol16:58
sdake#topic open discussion16:58
*** belmoreira has joined #openstack-meeting-416:59
*** openstack changes topic to "open discussion (Meeting topic: kolla)"16:59
SamYapleok got two things to talk about here16:59
inc0midcycle?16:59
sdakeok folks, any one want the foor?16:59
sdakesam has the floor16:59
SamYaplethanks, first is bugs/backports16:59
SamYaple#link https://bugs.launchpad.net/kolla/+bug/151755416:59
openstackLaunchpad bug 1517554 in kolla liberty "test bug" [Undecided,New]16:59
SamYapleif youll open that youll see it has a Liberty branch as affects16:59
SamYapleif a bug affects both master and liberty, select the "target to series" button and add liberty17:00
SamYaplethen when you backport the patch (or do an all new one if backport is not an option) the closes-bug tag willwork properly17:00
SamYaplefor bugs you do _not_ need the 'backport: liberty' tag17:00
SamYaplethat is for things that we cant track through the bug tracker17:01
*** igordcard has quit IRC17:01
SamYaplelike trivial fixes17:01
SamYapledoes this make sense to everyone?17:01
britthouserAnd in general do we backport all bugs?17:01
pbourkeyup17:01
*** igordcard has joined #openstack-meeting-417:01
SamYaplebritthouser: well if a bug affets the liberty branch then yes17:01
sdakebritthouser yes we backport all bugs17:01
sdakebut not features17:01
SamYaplenow when mitaka comes out and liberty is old-stable we may adopt a securityf-ix only policy17:02
sdakewe only backporting the essential mitaka-1 features17:02
*** bogdando has quit IRC17:02
SamYapleok if everyone is good with the bugs thing then im going to move on17:02
sdakeSamYaple17:03
SamYapleyes17:03
sdakeplease send an email to the mailing list17:03
sdakesince we have many missing cores from this meeting17:03
SamYapleok ill try to figure out how to start an email. i dont email17:03
SamYapleill get it done17:03
sdakei dont expect this wil go off without a hitch17:03
sdakei expect there wil be a learning curve here17:03
SamYaplenot a big deal. it takes 3 seconds to fix a mistake17:04
sdakethe reason we are doing this folks is becasue we need to be able to handle backports properly17:04
SamYaplenothing on the patchside even needs to change17:04
sdakeok #2 SamYaple17:04
SamYapleok next order of business17:04
SamYaple#link https://blueprints.launchpad.net/kolla/+spec/binary-ubuntu17:04
SamYapleI dont think this is going to happen in Mitaka17:05
SamYaple*maybe* cloud-archive will be doing this for the N release17:05
sdakewhy not get prepped for it now17:05
*** nishi has quit IRC17:05
sdakebesides maybe nobody is around to o the work17:05
SamYaplebecause cloud-archive has liberty packages right now17:05
nihiliferdo we have to use cloud-archive? can't we use just debian?17:06
SamYaplepackage names change from kilo to liberty to mitaka17:06
SamYaplenihilifer: no this is ubuntu17:06
sdakeyes but it should be a simple change to backport to mitaka at the end of the cycle17:06
nihiliferwe're installing delorean on all red hat famili distros17:06
SamYaplethe debian ones arent built for ubuntu (there are issues)17:06
nihiliferso why we can't install debian on debian family?17:06
SamYaplenihilifer: ubuntu packages have canonical support, debian ones do not17:07
*** matrohon has quit IRC17:07
sdakeok so lets just assume for a moment nihilifer  we use cloud archived17:07
nihiliferdelorean don't have support from oracle for delorean17:07
nihiliferand we're using it for oracle linux already17:07
nihiliferafaik17:07
sdakewhat is the harm in packaging liberty in the mitaka releae of kolla from binary packaging17:07
SamYaplei dont really care about centos though, ubuntu packages for ubuntu get support. this is important for busniess17:07
SamYaplebesides, as i stated before the debian openstack packages dont work on ubuntu. ive tried them before17:08
SamYaplesdake: yes the package names change17:08
sdakethe proposal on the table as I read it is to ship liberty paackages in the mitaka dockerfiles17:08
sdakeand do some rework at the nd of the cycle17:09
SamYaplei said this when this came up for liberty, if cloud-archive releases only after openstack i am not ok with including it17:09
nihilifercan we continue this topic on openstack-dev list? maybe if guys from debian and ubuntu packaging teams will see the topic, it will be better17:09
SamYaplebecause then we cant tag stable with the rest of openstack17:09
sdakenihilifer ca nyu start a thread please ssince sam is anti-mailing-list )17:09
nihilifersdake: lol, ok17:09
SamYaplei dont want to new fangled email17:10
SamYapleirc for me17:10
sdakeok anyone else want the floor now?17:10
britthouserbritthouser17:10
SamYaplelol17:10
sdakeshoot17:10
sdakebritthouser ure up17:10
*** vtech has quit IRC17:11
britthouserJust a quick question/survey.  I asked this earlier but figured I might get larger response here.  I'm curious what everyone uses for the dev environment?  Baremetal or VM?  VM in fusion/virtualbox/libvirt? VM in OpenStack?17:11
sdake4 node bare metal17:11
rhalliseybaremetal17:12
britthouserJust wanting to get a feel for what is used the most, so I don't start blazing any trails on my own..at least not yet. =)17:12
inc0mixture of all for me, but mostly vms17:12
pbourkelibvirt17:12
sdakeinc0 basically does baremetal in vms :)17:12
sdake(follows baremetal instructions)17:12
pbourkebug not with vagrant as vagrant-libvirt is a pile of @*!*17:12
jmccarthylibvirt, some virtualbox also17:12
inc0yeah we could look at fixing vagrant17:13
*** dzamboni has quit IRC17:13
inc0I got lots of flame coming my way with "I ran vagrant and it failed"17:13
britthouserOk...so majority is baremetal, which is what I was planning to.  So that gives me warm fuzzies. =)17:13
britthouserthx!17:13
pbourkei have a quick question17:13
pbourkeif that's ok17:13
sdakeinc0 pelase do - i would but I dont know how to usse vagrant17:13
sdakeI thought it got fixed but it did not17:13
jpeeleri happen to use vagrant-libvirt... but haven't deployed in a while17:13
sdakepbourke has floor17:13
inc0I don't use it as well17:13
pbourkeso Im back looking at adding plugin support for kolla17:14
pbourkeand would like to move kolla-build.conf to yaml17:14
pbourketo support this17:14
pbourkebut, it would cause some backwards compat concerns17:14
pbourkehow do people feel about this17:14
pbourkehttps://review.openstack.org/#/c/246942/17:14
sdakeyaml dependencies on deploy node are ok imo17:14
SamYapleim neutral17:14
sdakeif you make it work backward compat im good17:15
pbourkesdake: its more that existing build.confs will break17:15
pbourkeif people have their own17:15
nihiliferi use vagrant-libvirt mostly17:15
sdakepbourke use two different file names dude17:15
sdakeand implement both17:15
sdake(only get plugins with yaml)17:15
SamYaplesdake: im not ok with that17:15
inc0and mark ini as deprecated17:15
SamYaplethats worse17:15
SamYaplemark ini as deprecate is ok17:15
sdakey amark a deprecate but you can't jus tremove it in a cycle17:16
inc0lets keep one release of support of both and say ini stops working with N17:16
sdakeit needs to be deprecated for one entire cycle17:16
inc0for a moment we can check "if ini then do stuff, else do yaml stuff"17:16
pbourkethere are some alternatives but each have cons17:16
sdakethis is standard openstack practice17:16
pbourkee.g. put the plugin config in a separate file and keep the ini17:16
pbourkebut id rather just have one build conf17:17
inc0I dislike having 2 configs with 2 formats for one thing17:17
pbourkeyeah17:17
sdakepbourke lets go for one file, keep ini for one cycle, mark depreecated in docs/build.py17:17
sdakeand remove at start of N cycle17:17
inc0support both for a release and remove ini in N?17:17
pbourkeI hate to introduce a deprecation but...17:17
pbourkeits probably the best option17:17
pbourkeok thanks guys17:17
rhalliseygot a question also17:18
rhalliseydo you think we're ready to make the gate voting?17:18
sdakeholy christ no17:18
inc0haha17:18
pbourke:p17:18
sdakewe need local mirrors of evereything beefor the gate can vote17:18
pbourkeSamYaple is about to refactor the whole thing anyway17:18
rhalliseyuh it's been pretty solid though17:18
inc0we don't want delorean to paralyze our dev17:18
rhalliseyya that's true it will change later in the cycle17:19
sdakewe also need delorean going through upstream CI before we can gate on its deployment17:19
sdakebecause atm it breaks reguarlaly17:19
inc0we could somehow mirror it in CI17:19
sdakethe big problem with voting gates atm is local mirrors17:19
inc0but until we get 100% dependable dependencies (well...meh), I'm -1 on voting17:20
SamYapleits unlikely well ever make an binary packages master voting17:20
SamYaplewe may be able to maek the source gates voting after some mirrors are in place17:20
*** fitoduarte has joined #openstack-meeting-417:20
rhalliseyya it would be for source17:20
sdakei tend to agree with SamYaple it wil be difficult to make something that doesn't change per commit (delorean changfes every 3 days) voting17:20
inc0we can mirror binary as well17:20
SamYaplemirroring is not the issue inc017:21
SamYapleits the 'delorean is broken' is the issue17:21
sdakehere is what happens17:21
sdakebad commit hits master17:21
sdakedelorean rebuildds17:21
sdakebad commit in master reverted17:21
sdakedelorean bits stick around for 3 days17:21
sdakewhile the gate falls over17:21
sdakeuntil new delorean build is available17:21
pbourkecould just make source gates voting?17:22
pbourkefor now17:22
sdakethe source gates fail atm often17:22
pbourkedoh17:22
sdakei htink becasue of mirroring but i am not certain17:22
inc0it will fail a lot more often if we introduce deployment17:22
SamYaplesource gates do not fail often17:22
SamYapleunless there is an issue17:22
inc0also source gates have little impact tbh17:22
pbourkeinc0: how so17:23
inc0if it builds, it doesn't mean it works17:23
pbourkeinc0: we also deploy17:23
rhalliseywell gat deploys too17:23
*** nkrinner has quit IRC17:23
SamYapleyea but if the playbooks finish then it says ok17:23
inc0and that will be super problematic because we'll become CI for openstack17:23
SamYapleit doesnt currently check containers are up17:23
SamYapleworking on it17:23
inc0glance breaks packaging, we have our work paralyzed17:23
SamYapleinc0: if glance doesnt deploy, then they cant commit17:24
SamYaplethey run it through devstack too17:24
SamYapleany problems we feel others will17:24
inc0but devstack doesnt have lib separation17:24
*** nkrinner has joined #openstack-meeting-417:24
sdakeif other projects gated on kolla in a voting way17:24
SamYaplesure but they dont have a lib stomping issue anymore inc017:24
sdakethen thatwould make wense :)17:24
*** angdraug has quit IRC17:25
inc0it would then17:25
*** belmoreira has quit IRC17:25
inc0but "it worked on devstack" doesn't mean it works with us17:25
sdakeok quick info on midcycle17:25
inc0that's my point17:25
sdakeSamYaple has secured us a facility17:25
inc0so south carolina?;)17:25
sdakei will pubilsh a voting of the schedule17:25
*** lazy_prince has quit IRC17:25
rhalliseysweet17:25
sdakepeoplease, pleae vote17:26
sdakethere will be soda coffee lunch17:26
sdakeremote access will be possible but not ideal17:26
*** acabot_ has quit IRC17:26
sdakei may try to get u ssome bagels for the morning17:27
sdakedepends on how my flights 2work out and rental car situation17:27
inc0let's cook together;)17:27
SamYapletoo many cooks17:27
sdakeit wil be 2 days17:27
rhalliseyinc0, bring us some world famous texas BBQ17:27
sdaketuesday/wednedsay17:27
inc0rhallisey, I'm yet to try it tbh17:28
SamYaplerhallisey: carolina BBQ is also good ;)17:28
sdakenext meeting we will start working on the agenda17:28
rhalliseyI know!17:28
rhallisey:)17:28
britthouserplease no carolina BBQ17:28
britthouser=P17:28
SamYapledry rub vs tomato based17:28
inc0haha17:28
SamYapleNC has vinegar17:28
SamYaplesilly north carolina17:28
SamYapleok times up17:28
SamYapleback to #kolla17:28
rhalliseybye17:28
sdakeya times up17:28
sdakeenjooy17:29
sdake#endmeeting17:29
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:29
*** rhallisey has left #openstack-meeting-417:29
openstackMeeting ended Wed Nov 18 17:29:02 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:29
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kolla/2015/kolla.2015-11-18-16.30.html17:29
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2015/kolla.2015-11-18-16.30.txt17:29
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2015/kolla.2015-11-18-16.30.log.html17:29
*** jmccarthy has left #openstack-meeting-417:29
*** acabot has joined #openstack-meeting-417:30
*** Sukhdev has quit IRC17:31
*** alex_didenko has quit IRC17:33
*** acabot has quit IRC17:33
*** vtech has joined #openstack-meeting-417:36
*** mdorman has joined #openstack-meeting-417:36
*** Sukhdev has joined #openstack-meeting-417:36
*** banix has quit IRC17:37
*** seanmurphy has quit IRC17:39
*** wojdev has quit IRC17:40
*** mestery has joined #openstack-meeting-417:40
*** armax has joined #openstack-meeting-417:41
*** wojdev has joined #openstack-meeting-417:42
*** jwagner is now known as jwagner_away17:43
*** Swami has quit IRC17:44
*** vmahe_ has quit IRC17:45
*** SimonChung has joined #openstack-meeting-417:47
*** simon-AS5591 has joined #openstack-meeting-417:51
*** wojdev has quit IRC17:52
*** sarob_ has joined #openstack-meeting-417:57
*** bmace has left #openstack-meeting-417:58
*** degorenko is now known as _degorenko18:02
*** Swami has joined #openstack-meeting-418:03
*** watanabe_isao has joined #openstack-meeting-418:03
*** belmoreira has joined #openstack-meeting-418:04
*** belmoreira has quit IRC18:05
*** mestery has quit IRC18:05
*** sarob_ has quit IRC18:08
*** sdake has quit IRC18:08
*** gjayavelu has joined #openstack-meeting-418:12
*** s3wong has joined #openstack-meeting-418:12
*** inc0 has quit IRC18:13
*** watanabe_isao has quit IRC18:13
*** sdake has joined #openstack-meeting-418:13
*** mestery has joined #openstack-meeting-418:15
*** gjayavelu has quit IRC18:16
*** banix has joined #openstack-meeting-418:18
*** Sukhdev has quit IRC18:19
*** jmckind has quit IRC18:19
*** fawadkhaliq has quit IRC18:21
*** wojdev has joined #openstack-meeting-418:21
*** sarob_ has joined #openstack-meeting-418:22
*** wojdev has quit IRC18:24
*** sarob_ has quit IRC18:27
*** sdake has quit IRC18:28
xgermansc68cal ?18:30
sc68calxgerman: meeting-318:30
*** acabot has joined #openstack-meeting-418:30
*** stvnoyes has left #openstack-meeting-418:31
*** inc0 has joined #openstack-meeting-418:32
*** MarkAtwood has joined #openstack-meeting-418:37
*** sudipto has quit IRC18:38
*** acabot has quit IRC18:42
*** harshs has joined #openstack-meeting-418:43
*** inc0 has quit IRC18:44
*** cloudtrainme has quit IRC18:47
*** macsz has left #openstack-meeting-418:52
*** salv-orl_ has joined #openstack-meeting-418:54
*** salv-orl_ has quit IRC18:54
*** bpokorny has quit IRC18:56
*** bpokorny has joined #openstack-meeting-418:57
*** salv-orlando has quit IRC18:57
raginbajin#startmeeting operators_ops_tools_monitoring19:00
openstackMeeting started Wed Nov 18 19:00:21 2015 UTC and is due to finish in 60 minutes.  The chair is raginbajin. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** openstack changes topic to " (Meeting topic: operators_ops_tools_monitoring)"19:00
openstackThe meeting name has been set to 'operators_ops_tools_monitoring'19:00
*** balajin has joined #openstack-meeting-419:00
*** jmckind has joined #openstack-meeting-419:00
raginbajino/19:00
j^2o/19:00
*** klindgren has joined #openstack-meeting-419:00
klindgreno/ ?19:01
j^2hi!19:01
raginbajinhello friends.19:02
j^2raginbajin: i can run with this if you want19:02
raginbajinSounds like a plan.19:02
j^2perfect19:02
j^2can you give me #chair?19:02
raginbajin#chair j^219:03
openstackCurrent chairs: j^2 raginbajin19:03
j^2rock on19:03
j^2#topic Pre-Agenda19:03
*** openstack changes topic to "Pre-Agenda (Meeting topic: operators_ops_tools_monitoring)"19:03
j^2So i've been putting together a blog post about successful IRC meetings19:04
j^2the first thing involved is an agenda19:04
mdormanseems like a good start19:04
j^2I'd like to propose creating agendas via etherpad and posting them ahead of time19:04
*** Guest12059 is now known as med_19:04
j^2i have a template i used for #openstack-chef and we can work off that19:04
*** med_ has quit IRC19:04
*** med_ has joined #openstack-meeting-419:04
mdorman+119:05
j^2I also propose using the OSOps wiki page to host storewhatever the agendas19:05
*** ivar-lazzaro has joined #openstack-meeting-419:05
j^2anyone object to this? I can run with it if needed19:05
klindgrenNo objection from me19:06
raginbajinno objection19:06
*** jckasper has quit IRC19:06
*** ivar-lazzaro has quit IRC19:06
j^2rock on, i'll give a 20 more seconds before i'll take that action item19:06
j^2#action j^2 creates the agendas for the following meetings and adds them to OSOps. Create template and template email to pre announce the meetings19:07
j^2#topic Meeting times19:07
*** openstack changes topic to "Meeting times (Meeting topic: operators_ops_tools_monitoring)"19:07
j^2just to make sure we have it captured here i created two reviews today19:08
j^2one to remove the "Team Meeting"19:08
j^2and one to add OSOps to this meeting time19:08
j^2are there any other thoughts or objections to these actions?19:08
raginbajinno objections to it. already +1'ed it19:09
*** simon-AS5591 has quit IRC19:09
j^2awesome19:09
j^2and just to verify that this is a good time for all involed and it's every _other_ weeb19:09
j^2week*19:09
*** ivar-lazzaro has joined #openstack-meeting-419:10
j^2aka "odd weeks"19:10
j^2good?19:11
klindgrentypically I think this time works for me19:11
raginbajinI asked for as much input as i could and came up with this to make sure it works for west coast peoples19:11
j^2raginbajin: nice19:11
mdormanworks for me19:11
balajinworks for me19:12
j^2awesome19:12
j^2#topic Coding Standards19:12
*** openstack changes topic to "Coding Standards (Meeting topic: operators_ops_tools_monitoring)"19:12
j^2my can o'worms!19:12
j^2if yall have seen, the ML post about the coding standards for tools-generic19:13
j^2i'd like to open up this and start a discussion around it19:13
j^2I'm a rubyist and a sysadmin, so bash and ruby are the only things i have any real opinion on; what are the pythonists thoughts?19:13
raginbajinIs there an OpenStack standard for this?19:14
mdormani don’t have any strong opinions on this.  but for python why don’t we do the same standards as are on all the other openstack stuff?19:14
balajinno preference, some standard is good19:14
balajinusually the code i write is only readable by me19:15
balajinif we are looking at sharing and reusing, some standard is good19:15
*** MarkAtwo_ has joined #openstack-meeting-419:15
j^2raginbajin: from what i've seen there "isn't" but is at the same time. Every project has it's own ability to choose what they want19:16
mdormanmaybe we just use the same pep8 settings as nova uses, just as an arbitrary starting point19:16
*** MarkAtwood has quit IRC19:16
j^2mdorman: that's good enough for me19:16
j^2and if we stick with the pep8 then the bashpep8 thingy is another good starting point19:16
mdormanagreed.19:16
j^2does anyone here have a good grasp of the gating system with zuul?19:17
klindgrenyea - When I brought this up a while back - my only real concern was that the curated scripts functioned the same way.  IE they took the same command line options, or read from ENV's for auth19:17
j^2i have..an ok relationship with it, but if someone considers themselve an expert, id like to defer to them19:17
klindgrenno XP here with Zuul19:17
j^2klindgren: yeah i think that's deeper then we need to get for the moment. I think just basic linting is a good place to start19:18
balajinnot me either19:18
mdormanno zuul here either19:19
j^2ok, i guess i'll take the action item ;)19:19
j^2#action j^2 to figure out how to use zuul to validate against the pep8 (python|bash) and rubocop linters19:19
mdormanthanks man19:20
mdormanhappy to help review19:20
j^2perfect19:20
*** prashantD has quit IRC19:20
j^2see when we all decide on things then it's not really a can o'worms, is it :P19:20
*** cloudtrainme has joined #openstack-meeting-419:21
balajin:)19:21
j^2any other thoughts or objections to this topic? I'll give a minute for any extra thoughts or to keep the conversation going19:22
*** jckasper has joined #openstack-meeting-419:22
j^2nice19:23
*** prashantD has joined #openstack-meeting-419:23
j^2#topic Open Floor19:23
*** openstack changes topic to "Open Floor (Meeting topic: operators_ops_tools_monitoring)"19:23
j^2Those were the topics that i would have put on the agenda, what other topics would people like to talk about?19:23
*** bapalm has quit IRC19:23
mdormannot that i want to talk about this, but any comments/discussion needed around a mid-cycle.   sounds like people are mostly congregating around the idea of having the one in manchester19:24
mdormanrather than ‘regional’ ones.   (which i agree with)19:24
j^2yeah that's how i got it too19:24
balajin+1 for me, a single  midcycle19:24
raginbajinyep single midcycle but its going to interestign to see how an international one goes.19:25
j^2as i said in my post about it, they have been invaluable to me for the conversations alone. but being out of the country puts another layer of complexity for me to get on it19:25
mdormanright.19:25
j^2granted i think i can swing this one but i need to talk to my management chain19:25
*** bapalm has joined #openstack-meeting-419:26
*** jwagner_away is now known as jwagner19:27
klindgrenI dunno if the single meet-up is the best idea19:27
j^2klindgren: yeah? whys that?19:27
klindgrenI think ops is differnt in that instead of having say 20-30 people at a midcycle you have say 200+19:27
mdormani bet there will still be a fair amount of people from north america that will go19:27
klindgrenjust that I think when the midcycle is in a region - you are going to get more of those people in that region at the meetup (not bad)19:28
raginbajinI'm not sure about that especially have an international summit.19:28
klindgrenbut I think a number of the same topics are going to get rehashed19:28
klindgrenLike - monitoring, packaging, tooling19:28
*** vishwanathj has quit IRC19:29
mdormanso you’re saying it’s good to have a single meeting, rather than several parallel ones in each region?19:29
j^2the challange of a regional meetup though is that you need to find a sponsor of it. If we go through the openstack foundation they do all that stuff to make it happen. It's hard enough for us to get a project together, but a regional meetup that would be murder on logistics19:30
klindgrensorry I guess I am mixed on regional vs's single19:31
mdormani agree with the rehashing point19:31
klindgrenall I know is that the summit seemed rather underattended in the OP's things19:32
j^2true, every one we have we talk about a lot of the _same_ things19:32
j^2klindgren: it's because it's right at the same time as the other talks are going on. you're constantly at odds with what you want to see/do19:32
j^2drove me crazy to be honest19:32
mdormani think the rehashing is a different problem than the location of the meeting19:33
j^2mdorman: that's accurate19:33
mdormanand yeah i know there was a lot of feedback this summit about trying to keep the tracks from overlapping as much19:33
mdormanaustin goes back to the 4+1 days format, instead of 3+1, so it should be better19:33
klindgrenI think re-hashing will occur if you get a bunch of people who could other wise not attend because the meeting is more local19:33
klindgrenbut I would rather more people get invovled19:33
klindgrenso thats why I am split on it19:33
mdormani see what you’re saying19:33
mdormanyeah i mean the reality is no matter where it’s held, it’s going to be prohibitive to some people who are located far away19:34
klindgrenEitherway - I don't know if I will be able to make it to the meetup19:34
klindgrens/meetup/mid-cycle19:35
mdormanright.19:35
mdormananyway i don’t know that we need to discuss extensively more here.19:35
*** Guest89216 has joined #openstack-meeting-419:35
klindgrenyep yep19:35
klindgrenI am interested to see if it pans out -even if I can't make it19:36
klindgrenI would like to see people join more working groups19:36
mdorman+119:36
klindgrenand we can get more members doing stuff19:36
mdorman+1 to that too19:36
*** jckasper has quit IRC19:37
*** Guest89216 has left #openstack-meeting-419:37
mdormananybody else have any other topics?19:38
j^2not i19:38
*** John____ has joined #openstack-meeting-419:38
*** Sukhdev has joined #openstack-meeting-419:38
mdormanmy next topic: lunch!19:39
j^2ha!19:39
j^2i think we should share this, or at least run with the notes to the ML, raginbajin do you mind doing that or do you want me to?19:40
klindgrenmy next topic: Profile openstack-conductor!19:40
raginbajinj^2 Yeah I can do that.19:40
j^2awesome19:40
mdormanyup notes to ML is a great idea19:40
j^2show the community that we're making this happen19:40
j^2cool, anything else?19:41
j^2i think we've made some great progress already19:42
*** prashantD has quit IRC19:42
mdormani’m good19:42
j^2raginbajin: want to end the meeting?19:43
raginbajinI think that works for me unless anyone has anything else.19:43
mdormanthanks j^2 and raginbajin19:43
j^2:D19:44
*** fitoduarte has quit IRC19:44
*** prashantD has joined #openstack-meeting-419:44
*** fitoduarte has joined #openstack-meeting-419:44
*** MarkAtwo_ is now known as MarkAtwood19:45
j^2#link https://review.openstack.org/#/c/247075/19:45
j^2#link https://review.openstack.org/#/c/247070/19:45
j^2just so we have them in the notes19:46
raginbajinCool.19:47
raginbajinThen sounds like we are good then19:47
j^2yep19:48
raginbajin#endmeeting19:48
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:48
openstackMeeting ended Wed Nov 18 19:48:09 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:48
openstackMinutes:        http://eavesdrop.openstack.org/meetings/operators_ops_tools_monitoring/2015/operators_ops_tools_monitoring.2015-11-18-19.00.html19:48
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/operators_ops_tools_monitoring/2015/operators_ops_tools_monitoring.2015-11-18-19.00.txt19:48
openstackLog:            http://eavesdrop.openstack.org/meetings/operators_ops_tools_monitoring/2015/operators_ops_tools_monitoring.2015-11-18-19.00.log.html19:48
*** Sukhdev has quit IRC19:49
*** mdorman has left #openstack-meeting-419:50
*** jckasper has joined #openstack-meeting-419:50
*** jed56 has quit IRC19:54
*** MarkAtwood has quit IRC19:54
*** wojdev has joined #openstack-meeting-419:59
Jokke_Hello o/20:00
Jokke_Anyone up for log WG meeting?20:00
Jokke_#startmeeting log_wg20:01
openstackMeeting started Wed Nov 18 20:01:21 2015 UTC and is due to finish in 60 minutes.  The chair is Jokke_. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
*** openstack changes topic to " (Meeting topic: log_wg)"20:01
openstackThe meeting name has been set to 'log_wg'20:01
Jokke_#topic round call20:01
*** openstack changes topic to "round call (Meeting topic: log_wg)"20:01
*** Rockyg has joined #openstack-meeting-420:01
Rockygo/20:02
Jokke_hi Rocky20:02
RockygHey!  I'm tired.20:02
Jokke_looks like it's the two of us20:02
Rockygof course.20:02
Jokke_agenda for today? Sounds like something light and short :P20:02
Rockyg#startmeeting log_wg20:02
openstackRockyg: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.20:02
Jokke_#chair Rockyg20:03
openstackCurrent chairs: Jokke_ Rockyg20:03
Rockygoh.  ;P20:03
Jokke_we have meeting on already20:03
*** wojdev has quit IRC20:03
RockygGood.20:03
Jokke_I thought to leave note to the logs if no-one shows up :P20:03
Rockyg#topic Dev Progress20:03
*** openstack changes topic to "Dev Progress (Meeting topic: log_wg)"20:03
Rockyg#info the flexible user info patch got merged.  Forget what the review id is20:04
Rockyg#info  Work has started on dynamic reconfig20:05
*** igordcard has quit IRC20:05
Rockyg#info no progress on request-id propagated to log message spec20:05
RockygAnything else on this topic?20:05
Jokke_not that I know ... that was well tl;dr'd20:05
*** Sukhdev has joined #openstack-meeting-420:05
*** subscope has quit IRC20:06
Rockyg:-)20:06
*** subscope has joined #openstack-meeting-420:06
RockygSo, that means open discussion...20:06
Rockyg#topic Open Discussion20:06
*** openstack changes topic to "Open Discussion (Meeting topic: log_wg)"20:06
Jokke_I haven't seen any of the logging bugs coming in yet20:07
Rockyg#info still need to write up summary of log work for Mitaka and post to Dev and Ops ML20:07
Jokke_from those most annoying filter these out lists20:07
Rockyg#info  Still need to write fiery email to get Ops to file log level bugs20:07
RockygThere.  Haven't gotten to it yet.  Haven't gotten my dev ML mailbox below 200 messages yet. :P20:08
Jokke_ouch20:08
RockygYeah.  Lots of distractions.  Especially the stable release stuff.20:09
Jokke_the log rationalization ... should we prep specs for that for the wider direction or keep it in the bugs?20:09
*** subscope has quit IRC20:09
Jokke_I'd like to keep it in the bugs tbh to avoid crazy bikeshedding20:09
*** subscope has joined #openstack-meeting-420:10
RockygWell, Doug wants us to just file lots of bugs for log level fixes.  He thinks if we get that done this release, we could go for error code next.20:10
RockygSo, keeping in bugs is good.20:10
Jokke_it's so much easier to triage example by "Yes that is horrible indeed" than discuss about any wider concepts that would need to happen20:10
Jokke_yeah20:10
Jokke_I forgot about that20:10
*** MarkAtwood has joined #openstack-meeting-420:11
Jokke_so to get to work we really need those bugs20:11
*** salv-orlando has joined #openstack-meeting-420:11
RockygThe irritating thing is, if someone is in the code, changing levels, they could also be adding codes.20:11
Jokke_I know, but I guess that boat has sailed for OpenStack20:12
RockygYeah.  Until I get a couple of interns.  So, N.20:12
Jokke_need to wait until it's big enough painpoint for big enough deployers/support/service providers to get sufficient pressure on20:12
Jokke_:D20:13
RockygPain point is already there, but most devs don't hear.  And if as a dev, you're only focused on one project, you don't see the breadth of the problem.20:14
Jokke_I know as I said it's not big enough to get those execs telling that they are sick and tired of hearing about it, "Devs do something"20:15
RockygYeah.20:15
RockygSo, let me hijack this meeting.  Release.....20:16
Jokke_shoot20:16
RockygI'm thinking:  Get prod wg involved.  I also hear I need to get foundation mktg involved.20:16
Jokke_should we wrap the meeting and just use the time and empty room?20:16
*** subscope has quit IRC20:17
* Jokke_ is wondering if we have anything else that should be logged to log_wg minutes20:17
Rockygpossible plan:  juno: keep tree and do regular grenade testing to kilo; kilo:  get stable proj in shape to maybe try critical/security patches for 1.5 years?; liberty:  ready for 2 yrs support?20:18
*** MarkAtwood has quit IRC20:18
* Rockyg thinks we can push to next week for more log stuff. Unless I missed something in the ml about logging20:19
Jokke_I have difficulties to see that being agreed by tomorrow (even to the state "yes it's possible, lets postpone EOLing juno until we're sure")20:19
*** qwebirc90523 has joined #openstack-meeting-420:20
Jokke_#endmeeting20:20
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:20
openstackMeeting ended Wed Nov 18 20:20:08 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:20
openstackMinutes:        http://eavesdrop.openstack.org/meetings/log_wg/2015/log_wg.2015-11-18-20.01.html20:20
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/log_wg/2015/log_wg.2015-11-18-20.01.txt20:20
openstackLog:            http://eavesdrop.openstack.org/meetings/log_wg/2015/log_wg.2015-11-18-20.01.log.html20:20
Jokke_ok more of releases/stable20:20
Rockygmy problem is I need to get the logging stuff done before I can really focus on stable.20:20
RockygI don't want to stop EOL.  Just stop removal.20:20
Rockyg69% of prod clouds are on Icehouse or Juno20:21
*** yamahata has quit IRC20:21
RockygNeed to ensure Kilo backports don't break juno->kilo upgrades20:21
Jokke_do we have any statistics of how many of those are having realistic plans to move forward20:22
*** iyamahat has quit IRC20:22
RockygNo numbers on upgrade plans, but Ops thread on the subject says it takes 3-4months to get a new release qualified before upgrade work can begin.20:23
Jokke_I think that could be reasonable and I guess there is couple of hours in a week when CI is quiet enough to do the runs _if_ that doesn't mean that we need to keep dedicated infra for that20:23
Jokke_well clearly those who are still on icehouse haven't taken that on by rushing20:24
RockygJuno still supports 2.6python but I think we could make the case for only testing 2.720:24
Jokke_well relying on 2.6 will break your upgrade experience anyways20:24
RockygSo, done!20:25
Jokke_you convinced me conditionally ... you have what 16000 more to go20:25
RockygNo 2.6 support needed to do juno->kilo grenade testing20:25
RockygWell, the other issue is ubuntu 12.04  I don't think Kilo supports that, either, but not positive20:26
RockygSo we might need to keep a couple of those machines around for the grenade tests20:27
Jokke_so what's the next one we expect  to support?20:27
Jokke_and does juno support that?20:27
Rockyg14.04  And, yeah.  Juno should run on that.20:28
RockygSo, that might also be a done deal.20:28
*** evgenyf has joined #openstack-meeting-420:28
Jokke_so could test on 14.04 and py2720:28
RockygYeah.  Just that config.  And that should be enough.20:28
Jokke_so bare minimum to prove that if one has taken care of platform upgrades the software will not fall apart20:29
RockygSo, load up juno eol on 14.04 and py2.7, grenade test to kilo.  Any time a patch is submitted to the kilo stable branch (which should be seldom)20:30
Jokke_that might be pushing it, periodic job in the quiet moment of the week to run that test just might get through20:31
Jokke_and for most projects that's probably way more than what you are proposing20:31
RockygMy sentiments, too.20:31
RockygAlso, final push on kilo will be busy.  Unless the stable proj has come up with new processes already.20:32
Jokke_it still might be easier to get agreement on20:32
Jokke_lets see first if there will be stable project and what it will eventually do20:33
RockygShould be in place by kilo eol, though.  and yeah.  Grenade in quiet time is good.  Probably early Asia time.20:33
Jokke_I'm sure infra has good statistics of the loads20:34
RockygYeah.20:36
Jokke_so how to convince the rest?20:37
RockygWell, started the conv on a thread a couple of days ago.  Not much traffic on the thread, though.20:38
Jokke_that tends to be the trend20:38
Jokke_U got a reply 'though20:38
Jokke_if my memory doesn't fail me totally20:39
Rockygyup.  And a suggestion was just using the tarball for the eol.  That might work, but I bet it would be easier to use the tree...20:39
*** avarner has joined #openstack-meeting-420:40
Jokke_probably, as that's something we have everything done already20:40
*** avarner has quit IRC20:40
Jokke_Rockyg: do you want to collect this brainstorming to a reply for that?20:43
RockygYup.  I'd like to use infra as an example of why expecting lockstep moves is ignorant.  frinstance, infra went from gerrit 2.8- 2.1120:43
Jokke_but 2.8 wasn't years old yet :P20:43
RockygYah, but the reply ight be better from the guy who volunteered to be stable PTL ;-)20:44
*** iyamahat has joined #openstack-meeting-420:45
Jokke_I can try :P Not convinced that my word is any heavier than yours 'though :D20:45
RockygI bet it was at least a year, maybe 1.5 or so.20:45
Jokke_but tbh I could have formed the same question as do you want to do it or do you want me to do it :P20:45
RockygI'm trying to figure that out, but I'm having problems getting dates of release cuts.20:45
RockygYeah, but your word is a different word, plus you're a ATC20:46
Jokke_ok ... I'll try to word it sensibly for the ML20:47
RockygThanks!20:47
RockygSo, 2.8 looks to have come out a year ago.20:48
*** joonmyung has joined #openstack-meeting-420:48
Jokke_that's pretty good then20:49
Jokke_and 2.1120:49
RockygNope, sorry. 2 years ago.20:49
Rockygand 2.11 in June.20:50
*** John____ has quit IRC20:50
Jokke_2.8-rc3 was 2013-11-2220:51
RockygSo, 5-6months behind and rolling on a 1.5 year schedule?20:51
RockygTag was placed on2.8 on 12/4/201320:51
Jokke_2.8.1 2014-02-1820:51
Jokke_so yeah something between year and year & half between versions then20:52
Rockyg2.11 tag is 2015/4/1720:53
*** balajin has left #openstack-meeting-420:53
RockygAnd I believe that the changed didn't happen until there were enough desired features to outweigh the costs of changes to heavily used existing features20:54
*** vinsh has quit IRC20:54
RockygSo, if infra works that way, how can the community expect commercial entities to work differently?20:54
*** Sukhdev has quit IRC20:55
RockygHow many devs do you think upgrade their linux every release?20:55
RockygOh, look at the time!20:56
RockygSo, do you have enough fodder for the simple "keep the tree around but locked down" email reply?20:57
Jokke_:)20:58
Jokke_I should20:58
RockygI'm gonna get lunch then try to finish up my expense report stuff so I can concentrate on real stuff20:58
*** dwalleck_ has joined #openstack-meeting-420:58
RockygSee ya later!20:59
*** evgenyf has quit IRC20:59
*** dwalleck_ has quit IRC21:00
*** openstack has joined #openstack-meeting-421:04
-cameron.freenode.net- [freenode-info] channel trolls and no channel staff around to help? please check with freenode support: http://freenode.net/faq.shtml#gettinghelp21:04
*** ChanServ sets mode: +o openstack21:04
*** sdake has joined #openstack-meeting-421:08
*** simon-AS559 has joined #openstack-meeting-421:10
*** simon-AS5591 has joined #openstack-meeting-421:12
*** simon-AS559 has quit IRC21:14
*** alex_didenko has joined #openstack-meeting-421:20
*** klindgren has left #openstack-meeting-421:27
*** Rockyg has quit IRC21:31
*** woodard has quit IRC21:32
*** MarkAtwood has joined #openstack-meeting-421:50
*** yamahata has joined #openstack-meeting-421:51
*** jwagner is now known as jwagner_away21:51
*** julim has quit IRC21:51
*** salv-orl_ has joined #openstack-meeting-421:57
*** salv-orlando has quit IRC21:57
*** gjayavelu has joined #openstack-meeting-422:05
*** jmckind is now known as jmac22:10
*** jmac is now known as mkz22:10
*** mkz is now known as jmckind22:11
*** banix has quit IRC22:18
*** fitoduarte has quit IRC22:24
*** harshs has quit IRC22:26
*** Sukhdev has joined #openstack-meeting-422:26
*** MarkAtwood has quit IRC22:27
*** itisha has joined #openstack-meeting-422:30
*** jpeeler has quit IRC22:32
*** simon-AS5591 has quit IRC22:34
*** jpeeler has joined #openstack-meeting-422:36
*** gjayavelu has quit IRC22:52
*** sigmavirus24 is now known as sigmavirus24_awa22:53
*** mestery has quit IRC22:55
*** vtech has quit IRC22:57
*** jckasper has quit IRC23:03
*** Sukhdev has quit IRC23:04
*** Piet has quit IRC23:05
*** klamath has quit IRC23:12
*** Sukhdev has joined #openstack-meeting-423:15
*** sdake_ has joined #openstack-meeting-423:17
*** sdake has quit IRC23:18
*** cloudtrainme has quit IRC23:19
*** bpokorny_ has joined #openstack-meeting-423:21
*** alex_didenko has quit IRC23:22
*** jmckind has quit IRC23:23
*** harshs has joined #openstack-meeting-423:23
*** jmckind has joined #openstack-meeting-423:24
*** bpokorny has quit IRC23:25
*** rbak has quit IRC23:35
*** fitoduarte has joined #openstack-meeting-423:37
*** sdake_ has quit IRC23:40
*** sdake has joined #openstack-meeting-423:40
*** jmckind has quit IRC23:47
*** bpokorny_ has quit IRC23:47
*** bpokorny has joined #openstack-meeting-423:48
*** adduarte has joined #openstack-meeting-423:48
*** fitoduarte has quit IRC23:51

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