Wednesday, 2016-01-27

*** blahRus has quit IRC00:04
*** dims has quit IRC00:04
*** rbak has quit IRC00:04
*** baoli has quit IRC00:07
*** jmcbride has quit IRC00:08
*** woodard has quit IRC00:25
*** kebray has quit IRC00:35
*** kebray has joined #openstack-meeting-400:36
*** yamamoto_ has quit IRC00:39
*** xingchao has joined #openstack-meeting-400:50
*** markvoelker has quit IRC00:51
*** harshs has quit IRC00:51
*** baigk has joined #openstack-meeting-400:53
*** edleafe has quit IRC00:53
*** Swami has quit IRC00:55
*** edleafe has joined #openstack-meeting-400:55
*** markvoelker has joined #openstack-meeting-400:56
*** jmckind_ has joined #openstack-meeting-401:01
*** cemmason has joined #openstack-meeting-401:02
*** jmckind has quit IRC01:04
*** bpokorny_ has joined #openstack-meeting-401:07
*** bpokorny_ has quit IRC01:07
*** bpokorny has quit IRC01:07
*** uck has quit IRC01:07
*** bpokorny has joined #openstack-meeting-401:07
*** bobh has joined #openstack-meeting-401:07
*** sridhar_ram1 has joined #openstack-meeting-401:09
*** sridhar_ram has quit IRC01:09
*** spzala has quit IRC01:10
*** spzala has joined #openstack-meeting-401:10
*** baoli has joined #openstack-meeting-401:11
*** baoli has quit IRC01:11
*** woodard has joined #openstack-meeting-401:12
*** xingchao has quit IRC01:12
*** sdake has joined #openstack-meeting-401:13
*** bpokorny has quit IRC01:14
*** spzala has quit IRC01:15
*** sdake_ has joined #openstack-meeting-401:15
*** spotz is now known as spotz_zzz01:15
*** jmckind_ has quit IRC01:16
*** sdake has quit IRC01:17
*** spzala has joined #openstack-meeting-401:19
*** prithiv has quit IRC01:21
*** prithiv has joined #openstack-meeting-401:21
*** woodard has quit IRC01:22
*** woodard has joined #openstack-meeting-401:23
*** prithiv has quit IRC01:23
*** yasui has quit IRC01:23
*** yamamoto_ has joined #openstack-meeting-401:23
*** piet has joined #openstack-meeting-401:23
*** yasui has joined #openstack-meeting-401:26
*** woodard has quit IRC01:27
*** Jeffrey4l has joined #openstack-meeting-401:28
*** bobh has quit IRC01:28
*** lakshmiS has quit IRC01:30
*** Liuqing has joined #openstack-meeting-401:35
*** sdake has joined #openstack-meeting-401:36
*** david-lyle has quit IRC01:36
*** sdake_ has quit IRC01:37
*** sridhar_ram1 has quit IRC01:38
*** piet has quit IRC01:41
*** piet has joined #openstack-meeting-401:41
*** angdraug has quit IRC01:43
*** iceyao has joined #openstack-meeting-401:44
*** FallenPe_ has joined #openstack-meeting-401:44
*** FallenPegasus has quit IRC01:47
*** LouisF has quit IRC01:51
*** yasui has quit IRC01:56
*** baohua has joined #openstack-meeting-401:57
*** yasui has joined #openstack-meeting-401:57
*** fawadkhaliq has joined #openstack-meeting-401:58
*** bobh has joined #openstack-meeting-401:58
*** fawadkhaliq has quit IRC01:59
*** yasui has quit IRC02:04
*** yasui has joined #openstack-meeting-402:05
*** prashantD_ has quit IRC02:08
*** xingchao has joined #openstack-meeting-402:08
*** banix has joined #openstack-meeting-402:14
*** sdake has quit IRC02:16
*** zhurong has joined #openstack-meeting-402:18
*** dims has joined #openstack-meeting-402:24
*** kebray has quit IRC02:31
*** kebray has joined #openstack-meeting-402:36
*** FallenPe_ has quit IRC02:37
*** Jeffrey4l has quit IRC02:38
*** MarkAtwood has quit IRC02:42
*** yamahata has quit IRC02:44
*** iyamahat has quit IRC02:47
*** Jeffrey4l has joined #openstack-meeting-402:48
*** Jeffrey4l_ has joined #openstack-meeting-402:57
*** fnaval has quit IRC02:58
*** spzala has quit IRC03:00
*** Jeffrey4l has quit IRC03:00
*** spzala has joined #openstack-meeting-403:01
*** sdake has joined #openstack-meeting-403:04
*** piet has quit IRC03:04
*** jmcbride has joined #openstack-meeting-403:05
*** spzala has quit IRC03:05
*** sdake has quit IRC03:12
*** fnaval has joined #openstack-meeting-403:13
*** s3wong has quit IRC03:14
*** spzala has joined #openstack-meeting-403:15
*** woodard has joined #openstack-meeting-403:19
*** woodard has quit IRC03:23
*** jmcbride has quit IRC03:28
*** dims has quit IRC03:30
*** xingchao has quit IRC03:32
*** unicell has quit IRC03:36
*** baoli has joined #openstack-meeting-403:37
*** FallenPegasus has joined #openstack-meeting-403:38
*** haoli36 has quit IRC03:42
*** baoli has quit IRC03:42
*** haoli36 has joined #openstack-meeting-403:42
*** xingchao has joined #openstack-meeting-403:46
*** bobh has quit IRC03:48
*** xingchao has quit IRC03:57
*** xingchao has joined #openstack-meeting-403:58
*** xingchao_ has joined #openstack-meeting-404:00
*** xingchao has quit IRC04:00
*** baoli has joined #openstack-meeting-404:01
*** xingchao_ has quit IRC04:01
*** banix has quit IRC04:03
*** markvoelker has quit IRC04:04
*** salv-orl_ has quit IRC04:09
*** SamYaple has quit IRC04:11
*** baoli has quit IRC04:17
*** SamYaple has joined #openstack-meeting-404:18
*** spzala has quit IRC04:23
*** spzala has joined #openstack-meeting-404:24
*** david-lyle has joined #openstack-meeting-404:25
*** david-lyle has quit IRC04:25
*** spzala has quit IRC04:28
*** coolsvap|away is now known as coolsvap04:31
*** xingchao has joined #openstack-meeting-404:37
*** david-lyle has joined #openstack-meeting-404:37
*** xingchao has quit IRC04:39
*** fawadkhaliq has joined #openstack-meeting-404:46
*** chinnu has joined #openstack-meeting-404:47
*** piet has joined #openstack-meeting-404:49
*** chinnu has quit IRC04:56
*** FallenPegasus has quit IRC04:59
*** yamahata has joined #openstack-meeting-405:05
*** FallenPegasus has joined #openstack-meeting-405:05
*** markvoelker has joined #openstack-meeting-405:05
*** salv-orlando has joined #openstack-meeting-405:05
*** fnaval has quit IRC05:06
*** iyamahat has joined #openstack-meeting-405:06
*** piet has quit IRC05:08
*** markvoelker has quit IRC05:10
*** sdake has joined #openstack-meeting-405:13
*** javeriak has joined #openstack-meeting-405:13
*** salv-orlando has quit IRC05:13
*** krtaylor has quit IRC05:15
*** vishwanathj has joined #openstack-meeting-405:15
*** vishwanathj has quit IRC05:16
*** bsilverman has joined #openstack-meeting-405:16
*** unicell has joined #openstack-meeting-405:17
*** chinnu has joined #openstack-meeting-405:17
*** spzala has joined #openstack-meeting-405:24
*** kebray_ has joined #openstack-meeting-405:25
*** kebray has quit IRC05:28
*** chinnu has quit IRC05:28
*** krtaylor has joined #openstack-meeting-405:28
*** kebray_ has quit IRC05:28
*** kebray has joined #openstack-meeting-405:28
*** sdake has quit IRC05:29
*** spzala has quit IRC05:30
*** fawadkhaliq has quit IRC05:31
*** vishwanathj has joined #openstack-meeting-405:33
*** chinnu has joined #openstack-meeting-405:33
*** vishwanathj has quit IRC05:34
*** FallenPegasus has quit IRC05:36
*** FallenPegasus has joined #openstack-meeting-405:40
*** kebray_ has joined #openstack-meeting-405:45
*** kebray has quit IRC05:46
*** fawadkhaliq has joined #openstack-meeting-405:47
*** fawadkhaliq has quit IRC05:47
*** FallenPegasus has quit IRC05:48
*** fawadkhaliq has joined #openstack-meeting-405:50
*** lazy_prince has joined #openstack-meeting-405:51
*** sdake has joined #openstack-meeting-405:51
*** piet has joined #openstack-meeting-405:52
*** FallenPegasus has joined #openstack-meeting-405:57
*** nkrinner has joined #openstack-meeting-406:05
*** vishwanathj_ has joined #openstack-meeting-406:05
*** salv-orlando has joined #openstack-meeting-406:05
*** Satya_ has joined #openstack-meeting-406:08
Satya_Hi All06:09
*** salv-orlando has quit IRC06:10
*** FallenPegasus has quit IRC06:18
*** xingchao has joined #openstack-meeting-406:20
*** vishwanathj has joined #openstack-meeting-406:20
*** vishwanathj has quit IRC06:21
*** piet has quit IRC06:22
*** spzala has joined #openstack-meeting-406:27
*** chinnu has quit IRC06:27
*** chinnu has joined #openstack-meeting-406:30
*** spzala has quit IRC06:32
*** chinnu has quit IRC06:35
*** hdaniel has joined #openstack-meeting-406:39
*** sdake has quit IRC06:40
*** javeriak has quit IRC06:43
*** numans has joined #openstack-meeting-406:43
*** FallenPegasus has joined #openstack-meeting-406:47
*** sdake has joined #openstack-meeting-406:49
*** sdake has quit IRC06:50
*** iceyao_ has joined #openstack-meeting-406:51
*** javeriak has joined #openstack-meeting-406:54
*** iceyao has quit IRC06:55
*** prashantD_ has joined #openstack-meeting-406:56
*** salv-orlando has joined #openstack-meeting-406:57
*** salv-orlando has quit IRC06:57
*** salv-orlando has joined #openstack-meeting-406:58
*** markvoelker has joined #openstack-meeting-407:06
*** Shlomo_N has joined #openstack-meeting-407:08
*** javeriak has quit IRC07:10
*** javeriak has joined #openstack-meeting-407:10
*** markvoelker has quit IRC07:11
*** Shlomo_N has left #openstack-meeting-407:12
*** javeriak_ has joined #openstack-meeting-407:14
*** belmoreira has joined #openstack-meeting-407:15
*** javeriak has quit IRC07:15
*** paul-carlton2 has joined #openstack-meeting-407:15
*** xingchao_ has joined #openstack-meeting-407:17
*** hdaniel has quit IRC07:18
*** xingchao has quit IRC07:21
*** Jeffrey4l_ has quit IRC07:21
*** Jeffrey4l_ has joined #openstack-meeting-407:21
*** FallenPegasus has quit IRC07:28
*** cemmason has quit IRC07:28
*** iyamahat has quit IRC07:28
*** javeriak has joined #openstack-meeting-407:42
*** prashantD_ has quit IRC07:42
*** javeriak_ has quit IRC07:44
*** tkaczynski has quit IRC07:56
*** javeriak_ has joined #openstack-meeting-407:58
*** javeriak has quit IRC07:59
*** vtech has joined #openstack-meeting-407:59
*** zeih has joined #openstack-meeting-408:02
*** cemmason has joined #openstack-meeting-408:08
*** salv-orlando has quit IRC08:11
*** matrohon has joined #openstack-meeting-408:13
*** vishwanathj_ has quit IRC08:15
*** paul-carlton2 has quit IRC08:15
*** xingchao_ has quit IRC08:16
*** spzala has joined #openstack-meeting-408:28
*** paul-carlton2 has joined #openstack-meeting-408:28
*** hdaniel has joined #openstack-meeting-408:30
*** spzala has quit IRC08:35
*** dtardivel has joined #openstack-meeting-408:35
*** hdaniel has quit IRC08:35
*** evgenyf has joined #openstack-meeting-408:37
*** xingchao has joined #openstack-meeting-408:42
*** kebray_ has quit IRC08:43
*** armax has quit IRC08:45
*** Satya_ has quit IRC08:45
*** hdaniel has joined #openstack-meeting-408:47
*** ihrachys has joined #openstack-meeting-408:53
*** paul-carlton2 has quit IRC08:54
*** mbound has joined #openstack-meeting-409:00
*** armax has joined #openstack-meeting-409:04
*** salv-orlando has joined #openstack-meeting-409:04
*** markvoelker has joined #openstack-meeting-409:07
*** markvoelker has quit IRC09:12
*** prithiv has joined #openstack-meeting-409:14
*** prithiv has quit IRC09:17
*** prithiv has joined #openstack-meeting-409:18
*** armax_ has joined #openstack-meeting-409:19
*** paul-carlton2 has joined #openstack-meeting-409:20
*** armax has quit IRC09:21
*** armax_ is now known as armax09:21
*** Jeffrey4l_ is now known as Jeffrey4l09:30
*** baohua has quit IRC09:30
*** prithiv1 has joined #openstack-meeting-409:31
*** prithiv has quit IRC09:31
*** spzala has joined #openstack-meeting-409:31
*** akwasnie has joined #openstack-meeting-409:32
*** Liuqing has quit IRC09:33
*** spzala has quit IRC09:36
*** mfedosin has joined #openstack-meeting-409:40
*** prithiv1 has quit IRC09:41
*** amotoki has joined #openstack-meeting-409:41
*** prithiv has joined #openstack-meeting-409:42
*** prithiv has quit IRC09:44
*** prithiv has joined #openstack-meeting-409:44
*** xingchao has quit IRC09:51
*** baoli has joined #openstack-meeting-409:51
*** xingchao has joined #openstack-meeting-409:52
*** baoli has quit IRC09:57
*** iceyao_ has quit IRC10:01
*** ihrachys has quit IRC10:02
*** ihrachys has joined #openstack-meeting-410:03
*** salv-orl_ has joined #openstack-meeting-410:06
*** piet has joined #openstack-meeting-410:06
*** prithiv has quit IRC10:07
*** markvoelker has joined #openstack-meeting-410:08
*** salv-orlando has quit IRC10:08
*** markvoelker has quit IRC10:13
*** zhurong has quit IRC10:14
*** prithiv has joined #openstack-meeting-410:15
*** prithiv has quit IRC10:15
*** ihrachys has quit IRC10:17
*** prithiv has joined #openstack-meeting-410:17
*** prithiv has quit IRC10:18
*** piet has quit IRC10:25
*** killer_prince has joined #openstack-meeting-410:26
*** lazy_prince has quit IRC10:29
*** armax has quit IRC10:30
*** spzala has joined #openstack-meeting-410:32
*** salv-orl_ has quit IRC10:35
*** spzala has quit IRC10:37
*** ihrachys has joined #openstack-meeting-410:39
*** killer_prince has quit IRC10:40
*** lazy_prince has joined #openstack-meeting-410:41
*** xingchao has quit IRC10:52
*** akwasnie has quit IRC10:56
*** iceyao has joined #openstack-meeting-410:56
*** akwasnie has joined #openstack-meeting-410:59
*** sdake has joined #openstack-meeting-411:05
*** baoli has joined #openstack-meeting-411:07
*** prithiv has joined #openstack-meeting-411:11
*** prithiv has quit IRC11:12
*** baoli has quit IRC11:12
*** prithiv has joined #openstack-meeting-411:13
*** sdake has quit IRC11:20
*** akwasnie has quit IRC11:28
*** akwasnie has joined #openstack-meeting-411:30
*** spzala has joined #openstack-meeting-411:33
*** spzala has quit IRC11:38
*** fawadkhaliq has quit IRC11:42
*** fawadkhaliq has joined #openstack-meeting-411:42
*** pcaruana has joined #openstack-meeting-411:44
*** zz_ja has quit IRC11:46
*** baoli has joined #openstack-meeting-411:51
*** xingchao has joined #openstack-meeting-411:53
*** zz_ja has joined #openstack-meeting-411:53
*** prithiv has quit IRC11:54
*** prithiv has joined #openstack-meeting-411:55
*** baoli has quit IRC11:57
*** prithiv has quit IRC11:58
*** prithiv has joined #openstack-meeting-411:58
*** xingchao has quit IRC11:58
*** sdake has joined #openstack-meeting-412:01
*** prithiv has quit IRC12:01
*** javeriak_ has quit IRC12:02
*** pbourke has quit IRC12:02
*** prithiv has joined #openstack-meeting-412:03
*** pbourke has joined #openstack-meeting-412:03
*** prithiv has quit IRC12:04
*** ajmiller has quit IRC12:07
*** zhurong has joined #openstack-meeting-412:07
*** ajmiller has joined #openstack-meeting-412:07
*** markvoelker has joined #openstack-meeting-412:09
*** markvoelker has quit IRC12:14
*** baohua has joined #openstack-meeting-412:19
*** schwarzm has joined #openstack-meeting-412:19
*** dims has joined #openstack-meeting-412:23
*** spzala has joined #openstack-meeting-412:34
*** salv-orlando has joined #openstack-meeting-412:35
*** pcaruana has quit IRC12:37
*** spzala has quit IRC12:40
*** haoli36 has quit IRC12:40
*** salv-orlando has quit IRC12:40
*** baoli has joined #openstack-meeting-412:42
*** prithiv has joined #openstack-meeting-412:47
*** prithiv has quit IRC12:47
*** yamamoto_ has quit IRC12:49
*** prithiv has joined #openstack-meeting-413:05
*** david-lyle has quit IRC13:08
*** klamath has joined #openstack-meeting-413:09
*** markvoelker has joined #openstack-meeting-413:09
*** klamath has quit IRC13:10
*** klamath has joined #openstack-meeting-413:10
*** coolsvap is now known as coolsvap|away13:11
*** markvoelker has quit IRC13:14
*** edleafe has quit IRC13:32
*** spzala has joined #openstack-meeting-413:35
*** sdake_ has joined #openstack-meeting-413:40
*** spzala has quit IRC13:41
*** sdake has quit IRC13:42
*** krtaylor has quit IRC13:44
*** markvoelker has joined #openstack-meeting-413:45
*** prithiv has quit IRC13:46
*** bruno_ has joined #openstack-meeting-413:46
*** tkaczynski has joined #openstack-meeting-413:47
*** baohua_ has joined #openstack-meeting-413:47
*** baohua has quit IRC13:48
*** julim has joined #openstack-meeting-413:48
*** prithiv has joined #openstack-meeting-413:50
*** saggi has quit IRC13:50
*** seanmurphy has joined #openstack-meeting-413:52
*** bruno_ has quit IRC13:54
*** bruno_ has joined #openstack-meeting-413:54
*** bruno_ is now known as brunograz13:54
*** numans has quit IRC13:55
*** fawadkhaliq has quit IRC13:55
*** fawadk has joined #openstack-meeting-413:55
*** numans has joined #openstack-meeting-413:56
*** vishwanathj_ has joined #openstack-meeting-413:57
*** jwcroppe has joined #openstack-meeting-413:59
*** gzhai has joined #openstack-meeting-414:00
acabot#startmeeting watcher14:00
openstackMeeting started Wed Jan 27 14:00:49 2016 UTC and is due to finish in 60 minutes.  The chair is acabot. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: watcher)"14:00
openstackThe meeting name has been set to 'watcher'14:00
acabothi14:00
sballeo/14:01
jwcroppeo/14:01
vtecho/14:01
brunograzhi14:01
jed56hello14:01
dtardivelhi14:01
seanmurphyhi guys14:01
tpeoples\o14:01
*** ShillaSaebi has joined #openstack-meeting-414:01
acabotour agenda #link https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#01.2F27.2F201614:01
gzhaihi14:01
tkaczynskihello14:01
acabot#topic Announcements14:02
*** openstack changes topic to "Announcements (Meeting topic: watcher)"14:02
acabot#info mitaka-2 version of Watcher has been released on monday14:02
*** ShillaSaebi has left #openstack-meeting-414:02
acabot#info with 9 BPs implemented and 37 bugs fixed14:02
*** julim_ has joined #openstack-meeting-414:02
*** prithiv has quit IRC14:03
acabotthank you everyone for this great job14:03
*** ShillaSaebi_ has joined #openstack-meeting-414:03
*** edleafe has joined #openstack-meeting-414:03
acabotwe now have an idea of how many BPs we can manage during a serie14:03
*** reedip_ has joined #openstack-meeting-414:03
* edleafe rushes in late...14:03
acabot#info target is now mitaka-3 scheduled for 3rd of March14:04
acabot#info gzhai is now INTEL core contrib on Watcher14:04
*** vincentfrancoise has joined #openstack-meeting-414:04
acabotany other announcement ?14:04
sballeacabot: +114:04
*** sdake_ is now known as sdake14:05
acabot#topic Review Actions Items14:05
*** openstack changes topic to "Review Actions Items (Meeting topic: watcher)"14:05
*** julim has quit IRC14:05
acabotseanmurphy has shared specs for ZHAW algo https://review.openstack.org/#/c/271028/14:05
acabotand is looking for reviews14:06
*** pmesserli has joined #openstack-meeting-414:06
seanmurphythanks acabot14:06
jwcroppeI'll review14:06
acabotdid you guys start implementing ?14:06
seanmurphythanks jwcroppe14:06
seanmurphynot yet but soon14:06
sballesame here14:06
seanmurphyhave been v busy with other commitments14:06
acabot#action jwcroppe review https://review.openstack.org/#/c/271028/14:06
seanmurphyinto the next week or so14:06
seanmurphybut have been looking at the basic_consolidation example14:07
acabot#action sballe review https://review.openstack.org/#/c/271028/14:07
jed56seanmurphy you can maybe improve basic_consolidation implementation14:07
acabotvtech seanmurphy : is the doc clear enough ?14:07
seanmurphyjed56 - we can certainly try14:07
acabotdo not hesitate to give us feedback to improve the doc14:07
jed56it seem that what you want to do is near14:08
acabotyes jed56 suggest that you improve basic consolidation instead of building a new strategy14:08
*** mkoderer has joined #openstack-meeting-414:08
seanmurphyok - that could work14:09
tpeoplesyeah seems like the two are trying to do the same thing14:09
tpeopleswill take a closer look at the spec14:09
seanmurphyso - it prob looks like we should have offline discussion on it14:09
seanmurphyand perhaps it could be an option14:09
acabotok lets talk on irc before starting implementing a new strategy14:09
jed56if you prefer  we can  remove the current implementation she was here only for test14:09
*** yamamoto has joined #openstack-meeting-414:10
seanmurphyok14:10
seanmurphyall good with us14:10
acabotok14:10
sballeseanmurphy: that migth be faster for yu too since you have all the plumbing in place already14:11
seanmurphysballe: yep - good point14:11
*** yamamoto_ has joined #openstack-meeting-414:11
vtechIMO It would be nice to keep both and see how they performs14:11
vincentfrancoisethat would imply having the efficacy indicator then14:12
*** fawadk has quit IRC14:12
acabotvtech: in this case do not hesitate to get the plumbing from basic_consolidation14:12
*** neelashah has joined #openstack-meeting-414:12
*** woodard has joined #openstack-meeting-414:12
*** woodard has quit IRC14:13
acabotyes it could be a good way to test the efficacy indicator14:13
acabotwhen it will be implemented14:13
*** salv-orlando has joined #openstack-meeting-414:13
*** woodard has joined #openstack-meeting-414:13
acabotvmahe is working on specs for https://blueprints.launchpad.net/watcher/+spec/define-the-audit-scope14:13
sballewhat the ETA on the efficacy indicator14:14
sballeoh you answred my questn :)14:14
acabotsballe: the review is open but I need to add work items... I planned to do it this morning but ran out of time, I hope to have it by EOW14:14
sballeno rush... I know how time slips away14:15
vtechcool14:15
acabotwe need a status for https://blueprints.launchpad.net/watcher/+spec/watcher-overload-underload but I dont think alexstav is here14:15
*** yamamoto has quit IRC14:15
*** fawadkhaliq has joined #openstack-meeting-414:15
*** fawadkhaliq has quit IRC14:16
acabota patch from jed56 (https://review.openstack.org/#/c/270642/) needs review14:16
*** vhoward has joined #openstack-meeting-414:16
tpeoples#action tpeoples review https://review.openstack.org/#/c/270642/14:16
*** david-lyle has joined #openstack-meeting-414:17
*** bobh has joined #openstack-meeting-414:17
acabot#info jed56 added Voluptuous lib to validate action parameters14:17
acabot#info vincentfrancoise is adding tempest scenarios14:17
*** vhoward has quit IRC14:18
acabot#info tpeoples added global requirements14:18
*** piet has joined #openstack-meeting-414:18
*** vhoward has joined #openstack-meeting-414:18
acabotand needs review on https://review.openstack.org/#/c/269310/  https://review.openstack.org/#/c/269296/14:18
tpeopleswe need to get that merged before i can propose watcher to openstack/requirements.. +114:18
*** piet has quit IRC14:19
acabotcan we merge this by EOW ?14:19
*** piet has joined #openstack-meeting-414:19
jed56+214:19
jed56I will take a look14:20
jed56today14:20
tpeoplesthanks jed5614:20
acabot#action dtardivel review https://review.openstack.org/#/c/269310/ https://review.openstack.org/#/c/269296/14:20
acabot#action jed56 review https://review.openstack.org/#/c/269310/ https://review.openstack.org/#/c/269296/14:20
jed56welcome :)14:20
*** _degorenko|afk is now known as degorenko14:20
dtardiveltpeoples: there is an issue with olso.messaging 4.0.0 : we habe error on watcher.conf.sample generation14:20
*** dims has quit IRC14:21
tpeoplesok, can you give me details on the review?14:21
dtardiveltpeoples: no error with 3.1.0 previous version14:21
*** spzala has joined #openstack-meeting-414:21
dtardiveltpeoples: yes, of course14:21
tpeoplesthanks14:21
acabot#action dtardivel give details about oslo.messaging 4.0.0 error14:22
acabottpeoples : regarding https://review.openstack.org/#/c/270039/ I moved it to mitaka-3 as we need to do more testing14:22
tpeoples+114:22
sballe+114:22
acabot#info reviews are needed for https://review.openstack.org/#/c/270039/14:23
jwcroppe+q14:23
jwcroppe+114:23
*** cdupont has joined #openstack-meeting-414:23
dtardivelacabot: review ongoing in our side14:24
acabotok14:24
acabot#info tpeoples shared devstack plugin on openstack-dev ML14:24
acabotany other action items you want to share ?14:25
acabot#topic Blueprint/Bug Review and Discussion14:25
dtardiveltpeoples: what about your last bug about devstack doc #link https://bugs.launchpad.net/watcher/+bug/153829114:25
*** openstack changes topic to "Blueprint/Bug Review and Discussion (Meeting topic: watcher)"14:25
openstackLaunchpad bug 1538291 in watcher "Improve DevStack documentation" [Undecided,New] - Assigned to Taylor Peoples (tpeoples)14:25
tpeoplesdtardivel: i am going to update the docs to explain how to set up devstack from nothing14:26
tpeoplesinstead of just telling them to use the plugin14:26
sballeacabot: junjie and gzhai submitted some bps that we would like to start working n now14:26
vincentfrancoisetpeoples: +114:26
jed56+100014:26
tpeoplesthat way someone with no devstack experience should be able to set it up14:26
acabotsballe: yes this is something I'd like to discuss14:26
acabot+114:26
dtardiveltpeoples: it is a request coming from openstack-dev ?14:27
jed56our PhD will be able to run devstack !14:27
tpeoplesno, just from me :)14:27
dtardiveltpeoples: ok :)14:27
sballe+1 n devsack14:27
sballedevstack :)14:27
acabotso we have many new BPs that we will prioritize next week during our mid-cycle14:28
sballeperfect14:28
*** akwasnie has quit IRC14:28
acabotplease submit BPs before EOW if you want to have them included in mitaka-314:28
gzhaijust BP, not spec, right?14:28
sballeI believe mritika created a bp too around fingerprinting. I will follow up with her to make sure I know what she is doing14:28
tpeoples#info submit BPs before EOW if you want to have them included in mitaka-314:28
acabotgzhai: could you give us a quick overview of the 3 BPs you submitted ?14:29
*** baohua_ has quit IRC14:29
jed56sballe cool14:29
sballegzhai: I would suggest we start on the spec as well in parallel taht way we will be closer to be able to start implementing14:29
acabottpeoples: thx ;-)14:29
gzhaisballe: ok14:29
*** Swami has joined #openstack-meeting-414:29
acabotgzhai: yes BPs only14:30
sballeacabot: why not start on the spec for one of them?14:30
gzhaiacabot: we will start from the BP of airflow.14:30
acabotsballe gzhai : yes of course, I just want to check that we have all BPs referenced before the mid-cycle14:31
sballe+114:31
acabot#info gzhai submited 3 new BPs for 3 new optimization strategies14:31
gzhaiit check the airflows with power/temperature to see if something wrong or just high workload.14:32
sballeacabot: We are just startign the discussion around Watcher and TAP so I am hoping that we can move some of that work in as well as we get it defined.14:32
acabotsballe: sure this is something we will discuss next week14:32
sballeexactly. tkaczynski will be attending the summit as well as14:32
tkaczynskisballe it would be great, but we need quite a lot of discussion to get tothe same page14:33
sballetkaczynski: I agree but I want to make sure we can make progress an d not have to sit and wait around until the next cycle if we have some work taht can be dne14:33
sballebut as acabot said we'll discuss next week14:34
acabotif tkaczynski and jed56 can have f2f discussion next week, no doubt it will lead to something ;-)14:34
sballe+114:34
jed56+114:35
tkaczynski+114:35
*** galstrom_zzz is now known as galstrom14:35
*** dims has joined #openstack-meeting-414:36
acabottpeoples jwcroppe : any BPs you plan to add before the mid-cycle ?14:36
acabotsame question for brunograz14:37
tpeoplesacabot: will think about it, but i was planning on picking up some of the existing TBH14:37
acabotbrunograz cdupont : you wont be able to attend the mid-cycle but do not hesitate to submit BPs14:37
*** spzala has quit IRC14:38
sballeacabot: maybe we can get remote access to brunograz and cdupont when we talk about bps.14:38
*** xingchao has joined #openstack-meeting-414:38
sballeassumung they ae interested14:38
acabotsballe: yes sure, everything will be shared on an etherpad14:38
sballethat is true! I forgot14:39
brunograzacabot: yes sure14:39
seanmurphybrunograz and myself will be at a project meeting feb 2/314:39
seanmurphywe can try to be available but we will be a bit tied up14:39
acabotok, I will share the etherpad link on the agenda page on tuesday14:40
*** spzala has joined #openstack-meeting-414:40
acabotshould we keep our weekly meeting next week by the way ?14:40
sballeI think we should skip it since we have the meetup14:40
tpeoplesvote for skip14:41
sballe+114:41
brunograz+114:41
acabot#info no meeting next week as most of the team will be at the mid-cycle meetup14:41
*** yamamoto_ has quit IRC14:41
gzhai+114:41
acabotcross-project liaison, sballe, did you see the action last week ?14:41
sballebriefly.14:42
sballeWhen was the meeting?14:42
acabottpeoples suggested that we have a cross-project liaison14:42
sballeI saw that14:42
acabotfor watcher14:42
acabotand we are looking for a very nice person to do it ;-)14:42
sballeI am hapy to take on taht role but need jwcroppe to be my backup when I travel and cannot attend14:43
acabotas the meeting is at 10pm french time I'm not sure to be able to attend14:43
sballealso I am a nice person so I fit the criteria :)14:43
acabotsballe: right :-D14:43
jed56+114:43
acabotjwcroppe : what do you think as being the backup ?14:44
sballeas long as somebody can be a backup when I cannot attend I am cool with htis14:44
*** david-lyle has quit IRC14:44
acabotI can also be the backup of course14:44
sballeI am sure jwcroppe is fine with being the backyp14:45
jwcroppeacabot:+114:45
jwcroppeyes, that sounds good14:45
sballeacabot: sign me up and jwcroppe as backup14:45
acabot#action sballe start acting as the cross-projects liaison for Watcher (jwcroppe as backup)14:45
acabot#info final meetup agenda #link https://wiki.openstack.org/wiki/Watcher_mitaka_mid-cycle_meetup_agenda#Agenda14:46
acabotwe moved a couple of things from day 1 to 2 according to attendees presence14:46
sballeacabot: jut want to heck this is it right? https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting14:46
sballes/check14:46
tpeoplesyes sballe14:47
acabotyes14:47
sballethx14:47
acabotsballe: we will discuss mitaka priorities on day 1 so please send me an email about "your priorities"14:47
sballewill do14:48
tpeoplessballe: there is a list of CPLs on https://wiki.openstack.org/wiki/CrossProjectLiaisons that i think you should add yourself to too14:48
*** yamamoto has joined #openstack-meeting-414:48
acabotwe will probably adjust them on day 3 after 2 days of thinking...14:48
*** david-lyle has joined #openstack-meeting-414:48
sballeacabot: +114:48
acabotvincentfrancoise: experimental jobs and how to be automatic, do you have info on that ?14:49
*** javeriak has joined #openstack-meeting-414:49
tpeoplesthat was me14:49
tpeoplesawesome work by vincentfrancoise on getting the tempest plugin working14:49
acabotyes but I know that vincentfrancoise looked at it14:49
tpeoplesi think we should consider getting that running automagically14:50
tpeoplesok, cool14:50
vincentfrancoisewell, whenever the last batch of tempest tests qet merged14:50
*** automagically has joined #openstack-meeting-414:50
tpeoplessounds good vincentfrancoise14:50
vincentfrancoiseI will make a PS on project-config to make it automatic on the gate14:50
vincentfrancoiseso probably by EOW14:51
acabotwill it be a voting job automatically ?14:51
vincentfrancoise#link https://review.openstack.org/#/c/272551/14:51
tpeoplesi think it should be voting tbh14:51
acabottpeoples: +114:52
vincentfrancoisetpeoples: +1 will do14:52
*** david-lyle has quit IRC14:53
acabot#action vincent francoise set tempest test as a voting job on the gate14:53
acabot#action vincentfrancoise set tempest test as a voting job on the gate14:53
tpeoplessince there's nothing left on the agenda.. i have something random.  should we include translation with every patchset, or do it all end of release?14:53
tpeoplesinternally, we do translation as an after thought with an automated tool14:54
vincentfrancoisewith jed56, we decided to translate it in french as we go along14:54
acabottpeoples : easier to maintain if its done on every PS IMO14:54
jed56yes14:54
*** piet has quit IRC14:55
tpeoplesok, that'll work for now but we may want to consider changing that in the future, but we'll save that discussion14:55
acabottpeoples: but if we can run your tool just before releasing it could be great too14:55
dtardivel+114:55
*** sigmavirus24_awa is now known as sigmavirus2414:55
*** piet has joined #openstack-meeting-414:56
vincentfrancoisebut it's the same with the sample file which we will eventually remove from the codebase14:56
acabotok14:56
jed56vincentfrancoise: we can remove the sample file i think and add some documentaiton14:56
*** dandruta has joined #openstack-meeting-414:56
acabotjed56: you mean to help developers adding translation in the code ?14:57
vincentfrancoisejed56: dtardivel will make a wishlist bug on the matter anytime soon14:57
*** rbak has joined #openstack-meeting-414:57
jed56acabot no14:57
jed56watcher.conf.sample14:57
*** yamamoto has quit IRC14:57
dtardivelIMO, we will need to review translations just before the release to be sure all translated sentences are coherent14:58
acabot#action dtardivel add a wishlist bug to remove the sample file14:58
sballe+10014:58
acabotdtardivel: ok14:58
*** cemmason has quit IRC14:58
tpeoples+1 dtardivel, part of that automated preferably14:58
*** akwasnie has joined #openstack-meeting-414:59
tpeoplessee some of you next week in austin14:59
acabotyes see u in Austin14:59
acabotbye14:59
vincentfrancoisebye14:59
dtardivelbye14:59
seanmurphybye!14:59
sballebye see you next week14:59
gzhaibye14:59
brunograzbye14:59
seanmurphyhave fun in TX!14:59
jed56bye14:59
acabot#endmeeting14:59
tkaczynskibye14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:59
openstackMeeting ended Wed Jan 27 14:59:42 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-01-27-14.00.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-01-27-14.00.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-01-27-14.00.log.html14:59
*** gzhai has left #openstack-meeting-414:59
jasondotstar#startmeeting vahana15:00
openstackMeeting started Wed Jan 27 15:00:31 2016 UTC and is due to finish in 60 minutes.  The chair is jasondotstar. 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: vahana)"15:00
openstackThe meeting name has been set to 'vahana'15:00
jasondotstar#topic roll call15:00
*** openstack changes topic to "roll call (Meeting topic: vahana)"15:00
jasondotstaro/15:00
*** vincentfrancoise has left #openstack-meeting-415:02
*** spotz_zzz is now known as spotz15:02
jasondotstaralone today it looks like, but for documentation purposes, I'll update the meeting channel. :-)15:02
jasondotstar#topic Introduction15:02
*** openstack changes topic to "Introduction (Meeting topic: vahana)"15:02
jasondotstarAgain, this is a friendly reminder that the OpenStack Vahana project15:02
jasondotstarWe're building an iOS-based solution for OpenStack, in the form of one or more frameworks for interacting with the OS API, and *possibly* front end app15:03
jasondotstar#link https://etherpad.openstack.org/p/openstack-mobile-ios-brainstorm15:03
jasondotstar- Interested parties are encouraged to join the #openstack-vahana IRC channel15:03
jasondotstar#topic Action Items for Last Meeting15:03
*** openstack changes topic to "Action Items for Last Meeting (Meeting topic: vahana)"15:03
jasondotstar#link: http://eavesdrop.openstack.org/meetings/vahana/2016/vahana.2016-01-13-15.01.html15:03
*** dshakhray has joined #openstack-meeting-415:04
jasondotstarthere was no meeting last week nothing notable to update15:04
jasondotstarfirst one:15:04
jasondotstarjasondotstar to reach out to the user committee via the mailing list regarding the ops survey15:04
jasondotstarso, I've booked travel plans to the Manchester Ops Summit to conduct a focus group on the importance of mobile15:05
*** andymaier has joined #openstack-meeting-415:06
jasondotstarThanks to piet and others who are helping to organize this for us. we'll get some answers on the direction we should take15:06
jasondotstarwe're also put a bid in to add a question to the user survey. yet to hear a response on this.15:07
jasondotstars/we're/we have/15:07
*** MarkAtwood has joined #openstack-meeting-415:08
jasondotstarnext:15:08
jasondotstarjasondotstar to report on public api testing with trystack15:08
*** yamamoto has joined #openstack-meeting-415:08
jasondotstarthis one is quick - it works, but the 24 hour termination is concern15:09
*** jmckind has joined #openstack-meeting-415:09
jasondotstaras we develop more of the code, we'll have to see how it works out15:09
jasondotstarlast action item:15:10
jasondotstarjasondotstar to report on documenting a vahana/devstack local test environment15:10
jasondotstarthe plan is to start the documentation on it this week15:12
jasondotstar#action jasondotstar to continue reporting on the local dev documentation15:12
*** piet has quit IRC15:13
jasondotstaralso, there's a link to the brainstorming around crafting the focus group session as well:15:13
jasondotstar#link https://etherpad.openstack.org/p/mitaka-openstackux-mobile-interviews15:14
jasondotstar#link https://etherpad.openstack.org/p/mitaka-openstackux-mitaka-mobile-interviews <= CORRECTION15:14
jasondotstarok I'll finish up early here....15:15
jasondotstar#topic Open Discussion15:15
*** openstack changes topic to "Open Discussion (Meeting topic: vahana)"15:15
jasondotstaranyone (out there) have comments/feedback/etc ?15:16
jasondotstarbueller? :-)15:17
jasondotstarok, thanks for giving me the floor for 15mins.15:17
jasondotstar#endmeeting15:17
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:17
openstackMeeting ended Wed Jan 27 15:17:18 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:17
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vahana/2016/vahana.2016-01-27-15.00.html15:17
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vahana/2016/vahana.2016-01-27-15.00.txt15:17
openstackLog:            http://eavesdrop.openstack.org/meetings/vahana/2016/vahana.2016-01-27-15.00.log.html15:17
*** seanmurphy has quit IRC15:18
*** brunograz has quit IRC15:18
*** blahRus has joined #openstack-meeting-415:18
*** yamamoto has quit IRC15:19
*** jwcroppe has left #openstack-meeting-415:19
*** piet has joined #openstack-meeting-415:24
*** zhurong has quit IRC15:26
*** cdupont has quit IRC15:26
*** yamahata has quit IRC15:30
pietQuick question15:30
*** jmckind has quit IRC15:30
pietHi jasondotstar15:30
*** yamahata has joined #openstack-meeting-415:30
jasondotstarpiet: hi there15:30
jasondotstarpiet: shoot...15:31
pietDo you have a hadnful of operator/admins (~8) that would be interested in participating in an online interview?15:31
*** MarkAtwood has quit IRC15:31
*** iyamahat has joined #openstack-meeting-415:31
*** vishwanathj has joined #openstack-meeting-415:32
jasondotstarpiet: im sure we can solicit some15:32
jasondotstarI don't have any15:32
pietWe could do this stuff online and possibly be done before the summit15:32
pietsomething to think about15:32
*** jmckind has joined #openstack-meeting-415:36
*** krtaylor has joined #openstack-meeting-415:36
*** MarkAtwood has joined #openstack-meeting-415:38
*** yamamoto has joined #openstack-meeting-415:39
*** fawadkhaliq has joined #openstack-meeting-415:40
*** fawadkhaliq has quit IRC15:40
*** fawadkhaliq has joined #openstack-meeting-415:40
*** Sukhdev has joined #openstack-meeting-415:44
*** nkrinner has quit IRC15:44
*** daneyon has joined #openstack-meeting-415:49
*** matrohon has quit IRC15:51
*** javeriak has quit IRC15:52
*** daneyon_ has quit IRC15:53
*** vCloudernBeer has joined #openstack-meeting-415:55
*** javeriak has joined #openstack-meeting-415:58
*** akwasnie has quit IRC16:03
*** akwasnie has joined #openstack-meeting-416:03
*** numans has quit IRC16:04
*** akwasnie1 has joined #openstack-meeting-416:05
*** salv-orl_ has joined #openstack-meeting-416:06
*** akwasnie has quit IRC16:08
*** salv-orlando has quit IRC16:09
*** reedip_ has quit IRC16:09
*** banix has joined #openstack-meeting-416:10
*** ShillaSaebi_ has quit IRC16:10
*** david-lyle has joined #openstack-meeting-416:14
*** daneyon has quit IRC16:17
*** zeih has quit IRC16:18
*** mbound has quit IRC16:21
*** yantarou has quit IRC16:22
*** inc0 has joined #openstack-meeting-416:23
*** yantarou has joined #openstack-meeting-416:23
*** brendenblanco has quit IRC16:25
*** rhallisey has joined #openstack-meeting-416:27
*** avarner has joined #openstack-meeting-416:27
*** MarkAtwood has quit IRC16:28
sdake#startmeeting kolla16:29
openstackMeeting started Wed Jan 27 16:29:37 2016 UTC and is due to finish in 60 minutes.  The chair is sdake. Information about MeetBot at http://wiki.debian.org/MeetBot.16:29
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:29
*** openstack changes topic to " (Meeting topic: kolla)"16:29
openstackThe meeting name has been set to 'kolla'16:29
sdake#topic rollcall16:29
*** openstack changes topic to "rollcall (Meeting topic: kolla)"16:29
britthouser0/16:29
mkoderero/16:29
rhalliseyhi16:29
inc0o/16:30
sdake\o/16:30
Jeffrey4l\0/16:30
*** akwasnie1 has quit IRC16:30
unicello/16:30
pbourkeo/16:30
nihilifero/16:30
*** kproskurin has joined #openstack-meeting-416:30
*** akwasnie has joined #openstack-meeting-416:30
akwasniehi16:31
*** sambetts has joined #openstack-meeting-416:31
sdake#topic announcements16:31
*** openstack changes topic to "announcements (Meeting topic: kolla)"16:31
*** stvnoyes has joined #openstack-meeting-416:31
ajafoo/16:31
sdake#1. midcycle is february 9th and 10th.  if you haven't rsvped, please do so ASAP16:31
sdakebreakfast, lunch dinner provided the 9tih, breakfast lunch prvided the 10th, soda and coffee both days16:31
sdakeso food is taken care of :)16:31
britthouserthanks!16:32
sdake#2. small token of appreciation from foundation16:32
jpeelerhi16:32
sdakefor all current and post core reviewers of Kolla (including harmw and daneyon) the foundation and HP have a small token of appreciation for your dutiy as a core reviewer16:32
sdakeif your a core reviewer, please send me your mailing address and i'll send it out16:33
pbourke:)16:33
elemoineo/16:33
sdakethe smaall token of appreciation is not these: https://www.audeze.com/products/lcd-collection/lcd-416:33
*** MarkAtwood has joined #openstack-meeting-416:33
sdakebut you will like it anyway16:33
*** iyamahat has quit IRC16:33
sdakeeven ify our in a different country i will sort out how to get it to you16:33
sdakesay thanks to MarkAtwood16:34
nihiliferthank you MarkAtwood ;)16:34
sdakeif you donif you dont want to share your home address, i will bring some to the midcycle if i havet hem in time16:34
sdakeif not i will bring some to hte summit16:34
*** iyamahat has joined #openstack-meeting-416:35
sdakeany announcements from the community?16:35
pbourkenone here16:35
Jeffrey4lno16:36
*** sdake_ has joined #openstack-meeting-416:36
sdake_one last thing, i am currently remodeling my house16:37
sdake_i am nearly done, 1-2 weeks out16:37
sdake_but i am a bit distracted by the contractors, so if i'm ailing you in any way let me know and i'll fix that up16:37
sdake_i am also tkaing pto monday/tuesday pretty much unavailable all day16:37
sdake_possiby wednesday as well16:37
sdake_i'll syncup with rhallisey if he needs to run the wed meeting16:37
sdake_but i can probably take a break for that16:37
rhalliseysdake, kk16:38
sdake_#topic liberty 3 milestone review16:38
inc0next meeting will be almost midcycle anyway16:38
sdake_annoying16:38
*** belmoreira has quit IRC16:38
Jeffrey4lliberty? mitaka?16:38
sdake_ok well i can't chane tpics because my nick is different16:38
*** david-lyle has quit IRC16:38
sdake_Jeffrey4l huh?16:38
sdake_rather mitaka 3 milestoen review16:38
rhalliseylols16:38
sdake_sorry brain fart there :)16:38
sdake_old and tired16:38
kproskurin:-D16:38
Jeffrey4l:D16:38
sdake_#link https://launchpad.net/kolla/+milestone/mitaka-316:39
sdake_please open that up16:39
sdake_time boxed to 50 after16:39
sdake_as you can see my begging and pleading with the core review team to tackle upgrades has partially worked16:40
sdake_but I need m0ar help16:40
sdake_if folks could take 1 regular service and 1 infrastructure service that would rock16:40
*** sdake has quit IRC16:40
sdake_and we will come out of the midcycle with a plan for upgrading infrastructure services16:40
*** sdake_ is now known as sdake16:40
*** david-lyle has joined #openstack-meeting-416:40
sdake#topic mitaka-3 review16:41
*** openstack changes topic to "mitaka-3 review (Meeting topic: kolla)"16:41
Jeffrey4lUpgrade Manila from Mitaka to Newton -> why we have this? Wrong description?16:41
*** xingchao has quit IRC16:41
*** xingchao has joined #openstack-meeting-416:41
*** daneyon has joined #openstack-meeting-416:41
*** bpokorny has joined #openstack-meeting-416:41
sdakejeff manilla only came about in mitaka16:42
sdakebut we need to make sure database migrations work properly16:42
mkoderer"upgrade" means everything releated to a db schema update, right?16:42
sdakeright16:42
sdakeas well as applying configurtion changes16:42
*** bnemec has quit IRC16:42
mkoderersdake: k16:42
sdakethe applying configuration changes i htink happens uatomatically16:42
sdakebut inc0 woud know for sure16:42
inc0it does16:43
sdakeinc0 has got us kicked off with two kick-ass implemtntions - one simpe keystone nd one very ard nova16:43
*** zeih has joined #openstack-meeting-416:43
inc0it overrides old confs with new16:43
*** brendenblanco has joined #openstack-meeting-416:43
sdakeya we will have deploy and upgrade16:43
sdakeno update16:43
Jeffrey4lBut I am curiosity, puth the manilla here (midcycle 3) is properly?16:43
sdakemanila needs to be able to handle a dtabase migration update16:44
mkodererJeffrey4l: where do we have manila? midcycle ehterpad?16:44
sdakei dont even know if manila works, haven't tried it16:44
*** liyi has joined #openstack-meeting-416:44
mkoderersdake: the container builds16:44
sdakealso root drop needs some love16:44
mkodereransible isn't ready yet16:44
sdakewe hav edone about 25 of the todos16:44
sdakebut 5 remain16:44
Jeffrey4lsdake,  https://blueprints.launchpad.net/kolla/+spec/upgrade-manila  here, the target is m316:44
sdakeif some folks could pick up 1 or 2, i'd like to finish tht out before mitaka16:44
sdakeJeffrey4l yes that is correct16:45
sdakem3 is march 4th16:45
sdakei expect manila will be functional prior to then16:45
mkodererwithout manila support upgrading makes no sense :)16:45
sdakeanyone have any blueprints they wish to bring attention now that my begging is done :)16:45
sdakemanila is implemented16:45
sdakeplaybooks i think are in review or impemented16:45
Jeffrey4lBut the description is "Upgrade Manila from Mitaka to Newton", there is no Newton version before m316:46
mkoderersdake: https://review.openstack.org/#/c/269688/16:46
sdakemanila less priority then others16:46
*** galstrom is now known as galstrom_zzz16:46
unicellquick question, the "upgrade" is it for upgrade between kolla releases? how about source build? since it always uses master16:46
mkodererit's a wip16:46
sdakeunicell tht is what its for  as well16:46
sdakeupgrde liberty to master16:46
sdakeugprade mitaka to miaster16:46
sdakeupgrade master a to master b16:46
unicellmainly db schema?16:46
inc0unicell, in reality it is upgrade from latest stable kolla to master16:47
sdakewe have determined the hrd part of the upgrde is the db schema16:47
inc0but it will work on any kolla you have to master16:47
sdakeinc= goood point16:47
inc0we just support latest stable to current master16:47
unicellI see16:47
sdake2 more mins on time box16:47
inc0you can run upgrades every hour and it will work16:47
sdakesamyaple are you about?16:48
inc0I don't reccomend it, but it will;)16:48
*** iceyao has quit IRC16:48
mkodererinc0: old stable to new stable would make sense too16:48
unicellinc0: that means every commit in kolla master should be backward compatible?16:48
sdakeinc0 assuming master works ;)16:48
inc0mkoderer, new stable is a master from some point of time;)16:48
*** prashantD_ has joined #openstack-meeting-416:48
*** iceyao has joined #openstack-meeting-416:48
liyido we also have rollback in agenda?16:48
unicellinc0: I'm just thinking about your `run upgrades every hour` statement16:49
sdakeone area of concern i have is the data containers to hte named volumes16:49
sdakewe need to discuss tht at hte midcycle16:49
inc0unicell, depends how you define backward compatibility, we don't have running service or api16:49
*** bnemec has joined #openstack-meeting-416:49
inc0each run of plays is idempotent and atomic action16:49
sdakeliyl rollback si not in the meeting agenda no16:49
inc0and we don't have database16:50
sdakesamyaple ping16:50
sdakeyour up next16:50
*** bpokorny has quit IRC16:50
liyithanks sdake16:50
unicellinc0: assuming everytime we do fresh deploy, then yes. but what if I keep some containers running, while updating others16:50
sdake#topic Kolla-ansible config playbook16:50
elemoinesdake, your data containers vs named volumes concern is related to upgrades?16:50
*** openstack changes topic to "Kolla-ansible config playbook (Meeting topic: kolla)"16:50
*** bpokorny has joined #openstack-meeting-416:50
sdakeelemoine yes16:50
inc0unicell, let's move this to open discussion plz16:51
unicellinc0: sure16:51
sdakewell this is samyaple's topic - if  he wakes up we can move back to him :)16:51
nihiliferSamYaple: ?16:51
pbourkeIm not understanding that topic16:51
sdake#topic Logging with Heka spec16:52
*** openstack changes topic to "Logging with Heka spec (Meeting topic: kolla)"16:52
sdakepbourke its in the agenda16:52
sdakei dont know the details sorry16:52
pbourkenp16:52
sdakeI follow the agenda here:16:52
sdake#link https://wiki.openstack.org/wiki/Meetings/Kolla16:52
sdakefeel free to update it with your items16:52
elemoineshould I go ahead and talk about Heka spec?16:52
*** lakshmiS has joined #openstack-meeting-416:52
sdakeyou have the floor elemoine16:52
elemoineI updated the spec today, based on the good commeents I had16:53
sdakesee spec process hepful elemoine :)16:53
elemoinethe one missing bit is verify that I can handle haproxy and keepalived using Heka only16:53
elemoineI am prototyping this right now16:53
elemoineand it's promising :)16:54
elemoineI got it to work for haproxy16:54
sdakenice!16:54
sdakei think now we have no haproxy logging at all16:54
elemoineso I can't promise it but it sounds like we'll be able to do with just Heka16:54
elemoinesdake, correct16:54
*** iceyao has quit IRC16:54
sdakeakwasnie have any feedback?16:54
elemoinebut we want haproxy logging in the future16:54
nihilifergj elemoine16:54
*** iceyao has joined #openstack-meeting-416:54
*** prithiv has joined #openstack-meeting-416:55
britthouserRemind me: we decided heka can replace both rsyslog and one of the other services?16:55
akwasniejust one question elemoine: are you able to connect your patch with Heka with my patch with Elastic?16:55
elemoinewhen I am done with the prototyping work I'll update the spec again16:55
sdakebritt roger16:55
akwasnieI mean will it work together?16:55
elemoineakwasnie, I have no doubt about this16:55
inc0britthouser, if it can that is16:55
elemoinethis is why I did not focus on that16:56
sdakebritthouser logstash is gone now with heka16:56
britthousernice...two birds, one heka. =)  GJ  elemoine!16:56
sdakemy only concern with heka is reliability16:56
*** zeih has quit IRC16:56
nihiliferakwasnie: your elk patches will be merged soon, so elemoine will begin "ready to mege" work after that16:56
sdakeand my lack of experience with said reliability16:56
sdakebut if  folks say its solid i'll go with that16:57
akwasnienihilifer: great16:57
elemoinesdake, yeah new technology for you16:57
elemoinebut we've been using Heka for quite some time16:57
elemoineand we're confident it's reliable16:57
sdakewfm16:57
elemoineand Mozilla use it in production as well16:57
inc0and we don't have anything really now16:58
elemoineand we're committed to babysitting it :)16:58
*** galstrom_zzz is now known as galstrom16:58
sdakeelemoine can you link the spec please16:58
inc0we all will babysit it, but your help will be super useful16:58
*** hdaniel has quit IRC16:58
elemoinehttps://review.openstack.org/#/c/270906/16:59
sdakecore reviewers, specs require simple maoiryt approval16:59
elemoineinc0, right, I was joking here16:59
sdakeso I'd appreciate your time in reviewing the specs16:59
sdakeso  i don't have to track down votes16:59
sdake#link https://review.openstack.org/#/c/270906/16:59
elemoinesdake, I'll udpate the spec again tomorrow16:59
elemoinewhen I'm done I'll remove the [WIP] flag in the commit message16:59
elemoinewhen WIP is gone it'll mean "please review"17:00
elemoineworks for you?17:00
sdakeyup17:00
inc0you can always use workflow-1 for that17:00
sdakeworks for everyone :)17:00
inc0but either way works17:00
sdakemight as well review along the way17:00
elemoineok17:00
sdakei dont like specs to be reviewed at last minute17:00
sdakei'd like them continously reviewed by the core reviewer team17:01
sdakethis is why we dont use specs - alot of overhead17:01
elemoinethat's all on my side, I'm looking forward to integrating this with akwasnie's EK work17:01
sdake#topic open discussion17:01
*** openstack changes topic to "open discussion (Meeting topic: kolla)"17:01
sdakeso data containers to named volumes17:01
inc0having central logging this release would be wonderful17:01
sdakeinc0 me first then you :)17:01
unicellso we skipped "Kolla-ansible delegate_to vs run_once" topic as well?17:01
elemoineinc0, yep, agreee17:02
*** matrohon has joined #openstack-meeting-417:02
sdakeunicell samyaple isn't here17:02
sdakeand I dont know what he wants to discuss in that topic17:02
liyihow about the other guys get involved with that topic17:02
unicellsdake: ok..  I kind of hitting the issue with delegate_to vs run_once17:02
sdakeif the agenda topic leads aren't here in the meeting we will skip those17:02
unicellinterested to know what the direction would be to solve the problem17:03
sdakeunicell sync up with sam when he is in17:03
liyithe bug r really a pain in the ass now17:03
*** ppetit has joined #openstack-meeting-417:03
unicellguess we can discuss when Sam is online   yep17:03
liyiok17:03
sdakeso data containers to named volumes17:03
sdakei was thinking we could make a backup migration playbook17:04
sdakethat is run once17:04
*** vCloudernBeer has left #openstack-meeting-417:04
sdakethat migrates data containers to named volumes17:04
sdakethoughts/concerns?17:04
inc0one thin I have to say on this topic, we're switch docker version with this, kolla will not have backward compatibility17:04
sdake(needs to finish march)17:04
unicellsdake: is that part covered in any of the upgrade blueprints?17:04
sdakeinc0 why not17:04
inc0and yeah, migration play will have to happen and be part of upgrade play, good point17:04
*** vishwanathj_ has quit IRC17:05
nihilifersdake: that would be probably ansible module as well, but idea is good for me17:05
inc0sdake, just something to consider17:05
inc0I'm ok with that17:05
Jeffrey4lI think the backup is neccessary.17:05
sdakeno i mean when we switch to tdocker 1.10, why is there no backward compat?17:05
inc0sdake, can you pop a bp and connect it to main upgrade bp?17:05
inc0named volumes17:06
inc0thin containers17:06
sdakeyes well we need to solve that problem too17:06
sdakeinc0 can you write the blueprint, it hink you have a betteer handle o n the problem17:06
inc0if we switch to docker 1.10 and start using it's stuff right away, which we should17:06
inc0ok17:06
*** tkaczynski has quit IRC17:06
*** yamahata has quit IRC17:07
inc0we stop supporting older version of docker17:07
*** yamamoto has quit IRC17:07
sdakei am good with 1.10 of docker17:07
*** numans has joined #openstack-meeting-417:07
sdakemaybe docker inc hs finally gotten docker right this time ;)17:07
sdakeseems like it from my registry experiments17:07
inc0ma too, but we might need to put this as well to upgrade play17:07
*** paul-carlton2 has quit IRC17:07
elemoineso for upgrade we'll need something that copies the data from the old data container to the new named volume, right?17:07
inc0elemoine, maybe there is clean way to turn container to volume..17:08
sdakeyes but it ony needst orun if the data container is up17:08
*** automagically has left #openstack-meeting-417:08
sdakeand if it is up we backup restore kill old data container17:08
sdakeleft as an exercise to the reader17:08
sdakenamed volumes are already in teh code base17:08
sdakeso it needs to be handled17:08
elemoinefile owners/permissions might be the hard part17:09
*** vtech has quit IRC17:09
inc0I'll pop bp for both - upgrade docker and migration between version17:09
sdakei want popele to be able to deploy liberty and then upgrade to mitaka via kola with zero problems17:09
sdakedowntime is fine17:09
inc0downtime of API is fine*17:09
sdakenot the vms of course17:09
Jeffrey4lupgrade the docker will stop all the containers( especially the openvswitch and nova-libvit ) on a host. So we should move the vms on the host to another in the play?17:11
*** daneyon has quit IRC17:11
*** vishwanathj has quit IRC17:11
sdakenah libvirt will reonnect17:11
sdakei have tested this extensively17:11
sdakelibvirt can be upgraded without vm downtime17:11
*** andymaier has quit IRC17:12
inc0qemu can't tho17:12
inc0not sure about ovs17:12
Jeffrey4lqemu process and br-ex from openvswitch will be kill. at that time, the vms is unreachable.17:12
sdakea short network downtime is ok17:12
sdakelosing vm state is not good17:13
inc0I'd rather keep us of upgrading ovs right now17:13
sdakeqemu-kvm process is not killed17:13
*** jmckind_ has joined #openstack-meeting-417:13
inc0for me ovs upgrade is something we should handle outside of our play17:13
*** iyamahat has quit IRC17:13
sdakeinc0 your the boss ;)17:13
sdakeinc0 has taken lead on this folks, i'm just here to facilitate17:14
inc0as it's not upgraded every 6 months and is way more disruptive17:14
sdakeinc0 knows the tech well17:14
sdakeits a one time upgrade17:14
sdakeoh you mean ovs17:14
sdakeright17:14
unicellquick question: do we have a working sdn solution integraion in kolla, or it's just ovs with bridged network?17:14
sdakeovs is a infrastructure service17:14
sdakenot an openstack service17:14
sdakewe need a different strategy for infrastructure services then openstack services17:14
inc0+1 sdake17:14
Jeffrey4lI am talking about the docker service upgrade. When the docker service is stopped and all the container is down. The qemu process should be killed, in my understanding.17:15
inc0unicell, it's normal ovs+neutron way17:15
*** kebray has joined #openstack-meeting-417:15
*** kebray has quit IRC17:15
*** ihrachys has quit IRC17:15
inc0we also support linuxbridge17:15
sdakethat is what i talked about above, investigate the ifnrastructure services and come to the midcycle prepapred with a plan17:15
sdakeJeffrey4l 100% trust me qemu is not killed17:15
inc0good point Jeffrey4l17:15
*** prithiv has quit IRC17:15
sdakepid=host17:15
elemoinesdake, infrastructure upgrade is as important as openstack upgrade, no?17:15
*** kebray has joined #openstack-meeting-417:15
sdakeelemoine second in importance17:16
sdakewith pid=host, anything that goes into the host pid space docker cannot kill17:16
*** matrohon has quit IRC17:16
inc0elemoine, it doesn't have to be upgraded every 6 months, and that's easier17:16
*** salv-orl_ has quit IRC17:16
*** jmckind has quit IRC17:16
elemoineinc0, sdake, ok I see17:16
Jeffrey4lsdake, ok. I will make that test later.17:16
inc0Jeffrey4l, please do17:16
sdakeJeffrey4l yup double check that is still the case since docker is a movign targrt17:16
*** neelashah has quit IRC17:17
Jeffrey4l:D17:17
sdakebut fwiw 1.8 and below had this behavior17:17
sdakeif it does kill the ms we ned to fix that17:17
inc0unicell, about fresh deploy vs running kolla17:18
Jeffrey4lyup. I will show the result.17:18
inc0our upgrade stategy really means you redeploy containers, one at the time17:18
Jeffrey4lwhen finished.17:18
unicellinc0: was trying to understand better about the upgrade17:18
elemoinehttp://sdake.io/2015/01/28/an-atomic-upgrade-process-for-openstack-compute-nodes/ is what sdake wrote on the subject some time ago17:18
unicelldoes this upgrade allows us to upgrade some opernstack service while running others?17:19
inc0if you have 3 keystones, only 1 of them will be down in any given moment17:19
inc0unicell, that's how it works17:19
inc0we upgrade 1 service at the time17:19
unicellI mean, ceph could have dependency on kolla-ansible17:19
inc0first keystone, then after we're done we start with glance17:19
unicellnot the multiple instance of the same service part17:19
sdakeelemoine thanks i had forgot about that, it has screen hsots of proof that compute vms do not die during a libvirt upgrade17:19
inc0unicell, we try to keep containers independent17:20
inc0kolla-ansible is for example just run as a bootstraping tool, after that it just hangs in there17:20
inc0there is no container-to-container communication17:20
unicellthere's ansible module inside kolla ansible container17:21
inc0yeah, and it's main task is to create used for service in ks and so on17:21
inc0and that's not even run during upgrade, that's a bootstrap task17:22
Jeffrey4lkolla-ansible -> docker.sock(mount from the host) -> other container.   this is how it work.17:22
inc0it doesn't really do this even17:22
unicellok, I think I get your point, containers should be independent most of the time17:23
inc0it does call APIs17:23
inc0with shade which is ansible module for openstack17:23
sdakeok upgrades beaten to death17:23
sdakeanyone else have topics to discuss?17:23
inc0unicell, main benefit you have from containers is separation17:23
unicellthere's still cases openstack service have cross component dependencies, right?17:24
schwarzmsdake: there is this kolla-kubernetes bp .. is there any prior art ?17:24
*** dandruta has quit IRC17:24
sdakei am not familiar with this blueprint but i am not willing to take on something as complex as that at the end of the dev cycle17:24
inc0unicell, depends what do you mean17:24
sdakeespecially when we he so much work to do schwarzm17:25
sdakebut kolla started out as containers on kuberntes17:25
inc0in general services communicating either over API or queue, and both aren't contianer'ish dependency17:25
sdakeand it didnt work because kubernetes didnt support pid=host nd net=host17:25
sdakenow kubernetes supports those things from what i hear17:26
schwarzmthat is if the components using this are inside the containerized workload17:26
Jeffrey4lwhat looks like in the final? A web-base tools like fuel? Or a api-base service, which can be used by other deployment tool?17:26
rhalliseysdake, ya it does17:26
Jeffrey4lfor kolla17:26
schwarzmwe for instance would use a vcenter as backend17:26
nihiliferJeffrey4l: i guess we'll discuss this od midcycle17:26
schwarzmwhich would eliminate this need17:26
schwarzmbut ok if there is nothing i could look at i will keep an eye on the bp17:26
nihiliferJeffrey4l: but yes, at least for kolla-mesos i'd like to have an api to pass configuration without /etc files17:27
rhalliseyschwarzm, did you have any questions pertaining kolla-kube?17:27
sdakeschwarzm are you interested inworking on this work?17:27
rhalliseyschwarzm, it's still in the early stages17:27
nihiliferJeffrey4l: to make kolla consumable by i.e. fuel17:27
unicellinc0: I haven't give it try for tempest in kolla, but does it actually work and can ensure entire kolla setup working as expected?17:27
rhalliseyI'm going to make a run at it in Feb17:27
*** lazy_prince has quit IRC17:27
Jeffrey4lnihilifer, cook17:27
schwarzmi will take a good look at that17:27
Jeffrey4lcool.17:27
rhalliseyas long as updates and root priv stuff is done17:28
sdakeunicell the gates dont have enough ram to run tempest17:28
sdakeso if yo uwant ot solve that problem start by reducing ram in teh gates17:28
*** kebray has quit IRC17:28
unicellsdake: we don't have multinode setup in gate either, correct?17:29
inc0unicell, talk with pbourke about that, he is guy to talk to:)17:29
sdakeunicell not yet17:29
*** iyamahat has joined #openstack-meeting-417:29
sdakeok times up17:29
sdakelets flow over to #kolla17:29
sdake#endmeeting17:29
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:29
openstackMeeting ended Wed Jan 27 17:29:37 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:29
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-01-27-16.29.html17:29
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-01-27-16.29.txt17:29
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-01-27-16.29.log.html17:29
unicellthanks inc017:29
inc0thank you everyone17:29
akwasniethanks17:29
elemoinethanks17:30
rhalliseythanks17:30
*** rhallisey has left #openstack-meeting-417:30
Jeffrey4lthanks17:30
*** akwasnie has left #openstack-meeting-417:30
*** yamahata has joined #openstack-meeting-417:31
*** neelashah has joined #openstack-meeting-417:31
*** xingchao has quit IRC17:32
*** iyamahat has quit IRC17:33
*** iyamahat has joined #openstack-meeting-417:33
*** xingchao has joined #openstack-meeting-417:38
*** kproskurin has quit IRC17:38
*** jlk has joined #openstack-meeting-417:41
*** krtaylor has quit IRC17:41
*** armax has joined #openstack-meeting-417:42
*** kebray has joined #openstack-meeting-417:42
*** unicell1 has joined #openstack-meeting-417:42
*** jed56 has quit IRC17:43
*** mbound has joined #openstack-meeting-417:43
*** mbound has quit IRC17:44
*** unicell has quit IRC17:44
*** neelashah has quit IRC17:45
*** uck has joined #openstack-meeting-417:46
*** stvnoyes has left #openstack-meeting-417:47
*** degorenko is now known as _degorenko|afk17:50
*** fawadkhaliq has quit IRC17:51
*** xingchao has quit IRC17:51
*** sdake has quit IRC17:53
*** krtaylor has joined #openstack-meeting-417:53
*** salv-orlando has joined #openstack-meeting-417:53
*** mbound has joined #openstack-meeting-417:54
*** kebray has quit IRC17:58
*** dims has quit IRC17:58
*** xingchao has joined #openstack-meeting-417:58
*** Sukhdev has quit IRC17:59
*** dru has joined #openstack-meeting-417:59
*** dru is now known as anon03827418:00
*** anon038274 has left #openstack-meeting-418:00
*** kebray has joined #openstack-meeting-418:00
*** neelashah has joined #openstack-meeting-418:01
*** ajmiller has quit IRC18:02
*** armax has quit IRC18:02
*** ajmiller has joined #openstack-meeting-418:02
*** emagana has joined #openstack-meeting-418:02
*** Jeffrey4l has quit IRC18:02
*** kebray has quit IRC18:03
*** unicell1 has quit IRC18:05
*** sambetts has quit IRC18:06
*** Swami has quit IRC18:06
*** ppetit has quit IRC18:10
*** xingchao has quit IRC18:11
*** mbound has quit IRC18:18
*** fnaval has joined #openstack-meeting-418:18
*** dshakhray has quit IRC18:19
*** ihrachys has joined #openstack-meeting-418:20
*** sridhar_ram has joined #openstack-meeting-418:21
*** galstrom is now known as galstrom_zzz18:23
*** Swami has joined #openstack-meeting-418:25
*** vtech has joined #openstack-meeting-418:26
*** vhoward has quit IRC18:26
*** vhoward has joined #openstack-meeting-418:26
*** neelashah has quit IRC18:26
*** ihrachys has quit IRC18:28
*** kebray has joined #openstack-meeting-418:32
*** jmckind_ has quit IRC18:35
*** unicell has joined #openstack-meeting-418:36
*** jmckind has joined #openstack-meeting-418:38
*** cdelatte has joined #openstack-meeting-418:43
*** spzala has quit IRC18:49
*** galstrom_zzz is now known as galstrom18:50
*** spzala has joined #openstack-meeting-418:50
*** s3wong has joined #openstack-meeting-418:51
*** uck has quit IRC18:52
*** zeih has joined #openstack-meeting-418:53
*** spzala has quit IRC18:54
*** sdake has joined #openstack-meeting-418:54
*** mdorman has joined #openstack-meeting-418:56
*** klindgren has joined #openstack-meeting-418:56
j^2hi!19:00
docaedoyo!19:00
j^2#startmeeting operators_ops_tools_monitoring19:00
openstackMeeting started Wed Jan 27 19:00:46 2016 UTC and is due to finish in 60 minutes.  The chair is j^2. 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
j^2#topic Rollcall19:00
*** openstack changes topic to "Rollcall (Meeting topic: operators_ops_tools_monitoring)"19:00
j^2Hey everyone!19:01
docaedoHello!19:01
j^2please checkin or say hi to track you being here19:01
raginbajinHello19:01
raginbajino/19:01
mdormano/19:01
*** galstrom is now known as galstrom_zzz19:01
j^2unfortunately i’m being called away at the moment19:02
j^2raginbajin: can you run this or mdorman ?19:02
mdormani’m on a call also for another 30 min :(19:02
raginbajinI can that's fine.19:03
j^2rockon19:03
j^2thanks19:03
j^2#chair raginbajin19:03
openstackCurrent chairs: j^2 raginbajin19:03
raginbajinLet me pull up the meeting agenda19:03
docaedo#link https://etherpad.openstack.org/p/osops-irc-meeting-2016012719:03
raginbajinThank you19:03
docaedo^^ agenda (for the logging :) )19:03
docaedonp19:03
klindgreno/19:04
raginbajin#topic Previous Business19:04
*** openstack changes topic to "Previous Business (Meeting topic: operators_ops_tools_monitoring)"19:04
raginbajinJust want to review previous business from the last meeting to see if there is any additional information that we should discuss19:04
raginbajinThe first is Talk about releases for repos other than tools-contrib and tools-generic19:04
mdormanwas there any history on that?19:05
*** rockyg has joined #openstack-meeting-419:05
raginbajinThe discussion was that we would not be doing releases at this point.19:05
rockygo/19:05
raginbajinWe are still a pretty small group, and to handle releases would be a big task.19:05
mdormanyeah i kinda agree19:06
*** numans has quit IRC19:06
raginbajinIf there isn't anything additional to this to bring up, then the next would be - paulcz: talk about moving the terriform tooling to it's own repo19:06
rockygAlthough, it might be worth tagging some of the stuff when it's in a good and reviewed condition19:07
rockyga repo tag/label19:07
raginbajinrockyg: Ok good point.. We can review that once we get to a point where we actually have something that is tagged.19:08
raginbajinI mean needs tagging19:08
mdormanyeah i think something lightweight like that would be appropriate19:08
rockyg++19:08
raginbajinThe terriform tool wanted to move its tool over to its own repo under osops19:09
raginbajinWe have done this already for other tools and we didn't see it as any issue to bring it under the umbrella19:09
raginbajinAny new comments for this?19:09
klindgrennone from me19:10
raginbajinThe final item in the old business then is - balajin: Fixing the ical to reflect correct dates (it shows up on my calendar every week)19:10
mdormanso we’d have a osops-terriform repo?19:10
mdormansorry, late to that topic19:11
raginbajinYes, we would have an osops-terriform repo19:11
raginbajinand other bigger projects that want to hand these over to osops would use the same naming pattern.19:11
mdormangottcha.   ok makes sense.  thanks for the explanation19:11
rockyg++19:11
raginbajinIt looks like from the notes that the ical has now been corrected, but I'm not 100% sure if thats the case or not. balajin was the one reporting it and mentioned it was fixed.19:12
raginbajinNot sure if anyone has an info on this.19:13
docaedoI don't have a link to the review handy, but when I look in my google calendar I do not see the ops meeting noted19:13
docaedo#link http://eavesdrop.openstack.org/irc-meetings.ical19:14
rockygme either.  Hi, docaedo!19:14
docaedorockyg: hey!19:14
raginbajinand here's the link to the review19:14
raginbajin#link https://review.openstack.org/#/c/268326/19:14
raginbajinLooks like from the last comment that j^2 was still looking for some confirmation from openstack-infra group on it, but that's the last of the updates.19:15
*** piet has quit IRC19:15
docaedoraginbajin: thanks - then looks like that -1 from Tony needs to go away19:15
raginbajinWe'll keep it as an action item to follow-up with next meeting to make sure it gets resolved.19:16
raginbajinThat's it for previous business.   Does anyone have anything that I missed or would like to bring up?  I'll give everyone a minute or two before moving on.19:16
*** harshs has joined #openstack-meeting-419:17
rockygdocaedo, want to introduce yourself and your relevant project?19:17
docaedorockyg: sure (but I'll wait 'till the chair moves on to the next topic ;) )19:18
rockygAh, right.  Sorry.  Still old biz19:18
raginbajin#topic New Business19:18
*** openstack changes topic to "New Business (Meeting topic: operators_ops_tools_monitoring)"19:18
raginbajin#topic Talk about finding a place for Operator bits in the Community App Catalog (apps.openstack.org)19:18
*** openstack changes topic to "Talk about finding a place for Operator bits in the Community App Catalog (apps.openstack.org) (Meeting topic: operators_ops_tools_monitoring)"19:18
docaedoraginbajin: thanks!19:19
raginbajinyep!!19:19
raginbajinThe floor is yours I'm guessing19:19
docaedoI wanted to bring up the topic (suggested by rockyg) of adding Operator things to the openstack community app catalog19:19
docaedo#link https://apps.openstack.org19:19
docaedoj^2 has joined our meetings on occasion and has been active in the conversations we've had in the past19:20
docaedothe main thing that has come up was what exactly could be put in the catalog19:20
docaedoTo my mind the easiest way to think about the catalog is as an index of "things" that can be used with an OpenStack cloud19:20
docaedoThe idea of going to "apps.openstack.org" to find an installer for OpenStack (like fuel for instance) doesn't make much sense to me - BUT seems like there's room for other things that operators can use19:21
docaedoanyway, we'd had minor conversations kicking around from a few months back but they were pretty inconclusive19:21
raginbajinI guess I see apps.openstack.org as more for the users and not the operators.19:21
docaedoraginbajin: yes I mostly agree, but I think there's room (at least potentially) to include things in there for operators too,19:22
raginbajinI also wonder if we have another place for people to go, how do we manage that and how do we get operators to be be a part of our community.19:22
raginbajinfair enough.19:22
docaedoso thought it would be a good idea to get some input from the operators19:22
rockygWell, just like the apple and google stores have categories for music, games, apps, this catalog could have a category for "operations"19:22
*** Sukhdev has joined #openstack-meeting-419:23
mdormanmy question is how any of hte osops stuff would fit into a glance image, heat template, or murano package19:23
rockygIf the osops tagged repo gets tarballed, or just zipped if it's a single utility, then the catalog could point there, maybe?19:23
docaedoright - one of the things to keep in mind is that the three categories right now (heat, glance, murano) were just in a sense temporary, for launch, with the intention that they would be expanded upon19:23
mdormani see19:23
docaedowe're working to add Mistral and TOSCA assets right now19:23
*** ihrachys has joined #openstack-meeting-419:24
docaedoso the bigger question19:24
docaedois does it make sense to include things for operators too? and if so, what specific things would be there, what might it look like?19:24
docaedo(and if you as a group think it unnecessarily fragments the operator community, please say so :) )19:25
mdormanyeah i mean aside from the effort needed to maintain such a thing, seems like it might be useful.   i would imagine like a “tools” package that could kind of aggregate the whole tools repo somehow19:25
mdormanand another one for “monitors” for all teh monitoring scripts19:25
raginbajinI think we as an operators community are struggling to get enough support and/or tools added to our repos now.19:26
*** unicell has left #openstack-meeting-419:26
mdormanbut i’m wondering how much that stuff would actually be sourced from the app catalog, vs. operators just pulling them down from git.   i.e. is there actually demand for that stuff in the app catalog19:26
raginbajin+119:26
mdormanraginbajin:  i would agree with that as well.19:26
docaedoI don't think there's demand for that today, and might not ever be TBH19:26
docaedobut that's why I wanted to chat here with you all19:27
mdormanyeah probably the focus for now should be on getting more tools that are well-validated and curated in teh repos in the first place19:27
mdormanthen we could talk more about different ways to package and distribute19:27
docaedoseems reasonable to me - also I was not really sure what the current state was with respect to that (one more reason to have a quick conversation about it)19:28
rockygsounds like "not at the moment, but don't do anything to lock us out without first consulting us"19:28
raginbajin+119:28
*** bpokorny_ has joined #openstack-meeting-419:29
docaedorockyg: oh no way, it's now or never! if the operator group spurns the app catalog today we'll never work together again!!!! MUAHAHAHA19:29
*** bpokorny_ has quit IRC19:29
docaedojust kidding :) I feel like IRC meetings need more levity19:29
mdormansounds like a good plan to me19:29
docaedoI actually think that perfectly captures it19:29
*** bpokorny_ has joined #openstack-meeting-419:29
docaedoand I plan to stay in contact with you guys of course, and will keep the operator community in mind all the time19:30
* rockyg laughs but then the cold kicks in an makes me cough19:30
rockygYeah, I'm just a troublemaker, making sure the devs are aware of the other stakeholders.....19:31
raginbajinSo, it sounds like we the operators group is going to continue to concentrate on getting more validated and curated tools into our current repos and then look for different ways to package and distribute down the line.  This could include the app.openstack.org area eventually.19:31
docaedorockyg: it's much appreciated19:31
docaedoraginbajin: +119:31
mdorman+119:32
rockygSounds great.19:32
*** bpokorny has quit IRC19:32
docaedothanks for the conversation19:32
raginbajinThank you for talking with us for sure.19:32
rockygThanks!19:32
raginbajinThat's it for new business.  Does anyone have any additonal new business they would like to bring up?19:33
rockygMidcycle?19:33
raginbajin#topic Other new business19:33
*** openstack changes topic to "Other new business (Meeting topic: operators_ops_tools_monitoring)"19:33
raginbajin#topic Mid-Cycle19:33
*** openstack changes topic to "Mid-Cycle (Meeting topic: operators_ops_tools_monitoring)"19:33
mdormanthat’s waht i was going to say.  how much presense will we have there?19:33
*** jwang_ has quit IRC19:33
rockygI'm gonna be there.  I can advertise and promote.  Anything specific you want me and/or others to do?19:33
raginbajinI know I won't be able to attend. International trips are hard to get approved.19:33
*** hdaniel has joined #openstack-meeting-419:34
raginbajinI think just reminding people about any tools, monitors, scripts, etc are there for their contribution as well as use.19:34
mdorman+1 yeah that’s the main thing.  it’s really easy to contribute to the -contrib repo now, that’s a good first step for people19:35
*** jwang has joined #openstack-meeting-419:36
*** unicell1 has joined #openstack-meeting-419:36
*** piet has joined #openstack-meeting-419:36
rockygI'll get Tom to put it in the intro slides...19:36
mdormanis j^2  going, anybody know?19:37
rockygDo we have good readme.rst in each of the repos?19:37
raginbajin#action rockyg will talk with Tom F. about mentioning the OSOPS group in the introduction slides.19:37
j^2mdorman: yeah i couldn’t get the funds for it. :(19:37
*** spzala has joined #openstack-meeting-419:37
mdormanish on readmes19:37
rockygThat would be good to have in reasonable shape before the midcycle.  That way, quick reviews by ops to see what's already out there.19:38
mdormansomeplace there is a wiki page that explains it better.  but i can’t find it now19:39
raginbajinDo I have any volunteers to take on the task of updating the readmes19:39
mdormani can do that19:40
raginbajinawesome.. Thanks mdorman19:40
*** galstrom_zzz is now known as galstrom19:40
*** mfedosin has quit IRC19:40
rockygThanks mdorman19:40
raginbajin#action mdorman will update the osops repo's readme files to give a better description of their purpose.19:40
*** neelashah has joined #openstack-meeting-419:40
raginbajinDo we have anything else for the mid-cycle?19:41
raginbajinDo we have any other new business?19:42
raginbajinDoesn't sound like it... I'll give everyone another 1-2 minutes for any other business. Then close the meeting if there is nothing else to discuss19:43
rockygThanks!19:44
docaedothank you!19:44
raginbajinSounds like we are all done for today's meeting..19:44
mdormani’m good.  thanks raginbajin19:44
*** ihrachys has quit IRC19:44
raginbajinThank you everyone for coming and participating.19:44
raginbajinWe will see everyone again in 2 weeks..19:45
raginbajin#endmeeting19:45
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:45
openstackMeeting ended Wed Jan 27 19:45:22 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/operators_ops_tools_monitoring/2016/operators_ops_tools_monitoring.2016-01-27-19.00.html19:45
*** ihrachys has joined #openstack-meeting-419:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/operators_ops_tools_monitoring/2016/operators_ops_tools_monitoring.2016-01-27-19.00.txt19:45
openstackLog:            http://eavesdrop.openstack.org/meetings/operators_ops_tools_monitoring/2016/operators_ops_tools_monitoring.2016-01-27-19.00.log.html19:45
*** kebray has quit IRC19:46
*** mdorman has left #openstack-meeting-419:46
*** neelashah has quit IRC19:47
*** evgenyf has quit IRC19:49
*** javeriak has quit IRC19:50
*** neelashah has joined #openstack-meeting-419:51
*** uck has joined #openstack-meeting-419:53
*** dims has joined #openstack-meeting-419:54
*** uck has quit IRC19:55
*** uck has joined #openstack-meeting-419:55
*** javeriak has joined #openstack-meeting-419:55
*** Sukhdev has quit IRC19:57
*** ihrachys has quit IRC19:59
*** uck_ has joined #openstack-meeting-420:00
*** uck has quit IRC20:00
*** MarkAtwood has quit IRC20:01
*** barra204 has quit IRC20:06
*** dshakhray has joined #openstack-meeting-420:09
rockygshoot.  Lost track of time.  Anyone here for log_wg?20:11
rockygjokke_, rbradfor?20:13
rbradforsorry20:13
rockygno, I forgot, too.20:13
rbradforI have this in my calendar for 4pm ET.20:13
*** evgenyf has joined #openstack-meeting-420:13
rbradforand it's 3:13 ET now20:14
rockygOh, you're right.  I have got to get this straight in my head.  I keep doing this.20:14
*** vtech has quit IRC20:14
rockygGo back to getting the config stuff fixed.  We need that to get the log stuff fixed.20:14
rbradforI was on at 4pm ET last week aslo but there was no action!20:14
rockygI was sick.  I'll remember the 1pm pst this time20:15
rbradforok, so we can reconnect in 45 mins?20:15
*** Sukhdev has joined #openstack-meeting-420:16
*** neelashah1 has joined #openstack-meeting-420:16
*** neelashah has quit IRC20:16
*** julim_ has quit IRC20:17
rockygYup20:19
*** hdaniel has quit IRC20:20
*** bpokorny_ has quit IRC20:24
*** ihrachys has joined #openstack-meeting-420:24
*** bpokorny has joined #openstack-meeting-420:24
*** baoli has quit IRC20:26
*** salv-orlando has quit IRC20:27
*** ihrachys has quit IRC20:27
*** evgenyf has quit IRC20:28
*** mbound has joined #openstack-meeting-420:31
*** javeriak has quit IRC20:33
*** vtech has joined #openstack-meeting-420:34
*** matrohon has joined #openstack-meeting-420:41
*** vishwanathj has joined #openstack-meeting-420:42
*** Sukhdev has quit IRC20:44
*** vtech has quit IRC20:45
*** galstrom is now known as galstrom_zzz20:45
*** vtech has joined #openstack-meeting-420:46
*** vtech has quit IRC20:53
*** galstrom_zzz is now known as galstrom20:54
*** dtardivel has quit IRC20:57
*** mbound has quit IRC21:01
*** julim has joined #openstack-meeting-421:03
rbradforrockyg, knock knock21:03
*** rocky_g has joined #openstack-meeting-421:04
*** mbound has joined #openstack-meeting-421:04
*** dshakhray has quit IRC21:04
rocky_g#startmeeting log_wg21:05
openstackMeeting started Wed Jan 27 21:05:35 2016 UTC and is due to finish in 60 minutes.  The chair is rocky_g. Information about MeetBot at http://wiki.debian.org/MeetBot.21:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:05
*** openstack changes topic to " (Meeting topic: log_wg)"21:05
openstackThe meeting name has been set to 'log_wg'21:05
rbradforo/21:05
rocky_gsorry I'm late21:06
rocky_gjokke_, you there?21:06
jokke_yes21:06
jokke_o/21:06
jokke_sorry, just got in21:06
*** sridhar_ram has quit IRC21:06
jokke_so I was bit late as well21:06
rocky_gOK.  jokke_ meet rbradfor  and vice versa21:07
rbradforjokke_, hi,hi21:07
*** daneyon has joined #openstack-meeting-421:08
rocky_gand rbradfor, monty says hi!21:08
*** padkrish has joined #openstack-meeting-421:08
rbradformonty taylor?21:08
rocky_gyup21:08
jokke_hi rbradfor \o21:08
*** padkrish has quit IRC21:08
rocky_gwe were discussing logging and I mentioned you.21:09
rbradforyep, we have known each other, almost 10 years now.21:09
rocky_gWow.  So, monty was like four?21:09
jokke_:P21:10
rocky_g#topic status updates21:10
*** openstack changes topic to "status updates (Meeting topic: log_wg)"21:10
rocky_grbradfor, I know you're working on config stuff.  Whaere are you and how can we help?21:10
rbradforFrom an action item of last meeting I generated Sphinx docs of configuration options for 5 of 6 listed projects (swift doesn't play ball) to see what was possible.  My demo was at http://ronaldbradford.com/tmp/openstack-opts/21:11
rbradforI took this one step further and integrated Glance into full docs which provided some surprises. https://review.openstack.org/#/c/270920/ has merged, you can see the full glory at http://docs.openstack.org/developer/glance/opts.html21:11
rbradforsurprises are things we should discuss in relation to configuration reference guide21:11
rocky_gexcellent.  Get to them before the endusers see them21:12
jokke_rbradfor: oh that was you ;)21:12
*** daneyon_ has joined #openstack-meeting-421:12
rbradforjokke_, ??21:12
*** paul-carlton2 has joined #openstack-meeting-421:12
jokke_rbradfor: didn't realize to relate the nick and name together, that's all21:13
rocky_gjokke_'s main job is glance core21:13
jokke_I was looking that change but Flavio and Sabari were faster approving21:13
rbradforjokke_, ok, well I didn't know that either.21:13
*** galstrom is now known as galstrom_zzz21:13
jokke_so, thanks for that :D21:14
rbradforI just picked glance at random but the interaction with Sabari was very helpful towards decisions one may make in a operator config guide21:14
rocky_gplease elaborate..21:15
rbradforFlavio (who I did not know is PTL) gave a nice review feedback I appreciated.21:15
*** daneyon has quit IRC21:15
rbradforso, some points of discussion21:15
rbradfor1. what do you do when a project has multiple configuration files.21:15
rbradforin this case I put all files into one page.21:15
rbradforthis has advantages and disadvantages.21:16
rbradforthe main disadvantage is if you look at just one file, you don't see all possible options.21:16
*** salv-orlando has joined #openstack-meeting-421:16
rbradforwhat you get (and it took some formatting) is specific options and a "common libraries" section21:16
jokke_glance has actually at least 5 config files + policy and -paste.inis21:17
rbradforwhich is then linked to the end of the document.21:17
rbradforjokke_, I documented 5 I knew of (based on entry_points)21:17
jokke_cool21:17
rbradforwhat I learned is that you include other namespaces, via your opt/oslo-config-generator/<file> options (something knew I learned)21:18
rbradformy first instinct was to include all namespaces into each file, but I could not actually do that, I ended up with duplicate DEFAULT sections (a later topic)21:18
rbradforand, we would end up with what we are trying to avoid, repeating the same content.21:18
jokke_++21:19
rbradforso while a disadvantage you don't see all options possible, the advantage is I did not duplicate (for example logging options)21:19
*** harshs has quit IRC21:19
*** harshs has joined #openstack-meeting-421:19
*** harshs has quit IRC21:19
rbradforso, debatable if it should be one configuration file per page, and another page of "included namespaces", all linked nicely, or one page as it is now.21:20
jokke_glance is actually one of the rare projects still carrying example configs in tree, so in that perspective it does not make that huge of a problem either way21:20
rbradforand how it is now, could be achieved with present sphinx directives. creating one all encompassing file would have met a oslo.config code change21:20
rbradforjokke_, I liked the use of the oslo-config-generator conf file, I hope other projects use that.21:21
jokke_I personally like the idea of having the documentation all in single page so it's easy to search when you are crawling through those configs21:21
rbradforinfact, I'd propse we create a sphinx option to read these files specifically.21:21
rocky_g++21:21
jokke_rbradfor: I don't, but that's different story ... Hopefully we get the reason fixed in oslo-config-generator21:21
rbradforso the docs creatiion uses one conf file, and generates sample configs and matching docs.21:22
rbradforjokke_, whats the fix you speak of?21:22
jokke_well there is no fix yet, but the problem is that if you change something in the config options (at the code level) you get XX% different output from oslo config generator21:23
rbradforas I just fixed another bug in this area, happy to hear your input while it's fresh21:23
jokke_making config management absolute nightmare21:23
jokke_and thus upgrade as well21:23
rbradforok, well lets come back to this, because I'd like to know what it is so I can fix it21:23
rocky_gFYI here, Nova is working to merge all their config files into a single one, with clear "sections"21:24
jokke_IIUC Stuart McLaren opened bug against it just last week21:24
jokke_haven't got to look into it yet21:24
jokke_rocky_g: we are not :P21:24
rocky_gSo, I think there will be a trend in Newton to do the same in other projects.21:24
rbradforI've seen a lot of reviews on nova cleanup21:25
rocky_gYup.21:25
jokke_there has been push for that at least for 3 cycles now, and I'm happy to keep -2ing any proposed changes for such :P21:25
rbradforspeaking of sections, this is a problem I found, and I'm going to raise it in Austin, that is having logging not be in [DEFAULT] but in a [logging] section21:25
jokke_same with removing the examples from tree21:25
rocky_gAh.  Interesting.21:26
rbradforjokke_, silly to remove conf examples from code.21:26
jokke_rbradfor: that's purely because it comes from oslo_log, not from the project namespace21:26
rocky_gI'd love to see a proposal to have a "global" config that only gets overwritten by individaul project config files.  Right now, no global21:26
jokke_rbradfor: and tbh. I like the fact that all the config options are now under their own section, not scattered around [DEFAULT]21:26
rbradforyes, because it's a namespace, and a few others benefits21:27
rocky_gSo, instead of "default" how about "global" with sections?21:27
rbradfor1 is the generation of "common libraries". all others have there own section21:27
jokke_rocky_g: the problem with that is that it's great idea for devstack, but kind of pointless when you deploy the services to their dedicated machines21:27
rbradforand also if you want to move to rocky_g goal of a higher order global config I see sections as being beneficial21:28
rocky_gI think ops would take the config files from a repo and write a distribution script to put it on the appropriate iron.21:28
jokke_I think the oslo-config-generator is the right way to go if we get projects not to change those defaults what oslo__log offers21:29
jokke_that would give that global default and it would be up to deployer to change if they insist21:29
*** zeih has quit IRC21:30
rocky_gWell, it would be good to have a way to identify all the cross project config options separate from the project specific ones and have one place to change them...21:31
*** vhoward has quit IRC21:32
rbradforrocky_g, it will take some time to get standardization first across projects. the siloed approach now has some big effects in just naming things consistently.21:32
rocky_gSo far as I am aware, that's only oslo stuff at the moment.21:33
rocky_gYeah.  Don't I know.21:33
jokke_rbradfor: I'm bit afraid of that naming consistently part as well ... afraid that we will get even more collisions21:33
rocky_gThe cool thing about the generator is that it might be easier to identify conflicting options settings21:33
rocky_gcould we do it for oslo stuff, though?  And instead of a "default" or "global", just have an "oslo" section?21:34
jokke_well as long as they are in different sections I don't think it cares, nor should/can21:34
jokke_but when template update needs stuff like this https://twitter.com/epkuva/status/691669708756631552 naming collisions becomes really painful21:35
rbradforrocky_g, just to digress a moment on sections21:36
rbradforcheck out http://docs-draft.openstack.org/20/270920/4/check/gate-glance-docs/0e8ef17//doc/build/html/opts.html21:36
rbradforwhich I just discovered differs from http://docs.openstack.org/developer/glance/opts.html (something else to look at)21:36
*** matrohon has quit IRC21:36
rbradforyou can see inthe first, in the left menu, all the sections21:36
rbradforthere is already inconsistency in section headings for oslo, so I doubt we will get a common concensus, and I don't think having oslo is needed?21:37
rocky_goslo is only needed if there is a change from the oslo defaults21:38
rocky_gbut, there should be links to the relavent common, included other opts21:39
jokke_rbradfor: actually good example of that sorting issue I mentioned21:39
*** piet has quit IRC21:40
rbradforjokke_, are you talking about https://bugs.launchpad.net/oslo.config/+bug/153689921:40
openstackLaunchpad bug 1536899 in oslo.config "config generator sorting has changed" [Undecided,Fix released] - Assigned to Ronald Bradford (ronaldbradford)21:40
jokke_http://docs.openstack.org/developer/glance/opts.html if you look for enable_v*_api ... so we have enable_v1_api, enable_v2_api, enable_v2_registry and enable_v3_api ... but all those are scattered all over the place21:40
jokke_rbradfor: I think that would be the one, yes21:40
rbradforjokke_, I fixed that, it merged a few days back21:41
jokke_oh brilliant!!!!21:41
rbradfordocs regenerated will go back to "source code" order21:41
*** bpokorny_ has joined #openstack-meeting-421:41
jokke_rbradfor: will that be just for the docs or for the config files as well?21:41
*** bpokorny_ has quit IRC21:41
jokke_I mena for the generated example configs21:41
rbradforI'm more concerned with the draft docs and the final ones about the left menu, and section headings and formats, something is off there.21:41
rbradforjokke_, it's the same code so it would fix both.21:42
*** bpokorny_ has joined #openstack-meeting-421:42
jokke_rbradfor: that's best news I've heard for a while ... if you don't mind, drop link to that fix to the bug and feel free to mark it fixed or invalid, which ever way you prefer ;)21:42
rocky_gthe option group seems to clean up a lot of the toc stuff.  It drops a lot of the options out of the display level21:43
rbradforjokke_, https://review.openstack.org/#/c/272289/ has merged, so launchpad should mark this as closed automatically?21:43
rocky_gIt's marked fix released21:44
jokke_rbradfor: oh yeah, it actually has (Fix released)21:44
*** bpokorny has quit IRC21:44
*** baoli has joined #openstack-meeting-421:44
jokke_makes our life so much better for the future, specially upgrades21:44
rbradforjokke_, yeah, that came to Oslo attention at our meeting on monday. As I was in that code on Friday is was easy to identify, and not to much to fix21:45
rbradforjokke_, so let's talk about upgrades a bit.21:45
*** zeih has joined #openstack-meeting-421:45
rbradforlet me start with "deprecated" because I've had a ML discussion on this.  I want all options marked as deprecated to have a reason, and that reason is to list "in what release it is to be removed", but that's just text.21:45
*** kebray has joined #openstack-meeting-421:45
*** zeih has quit IRC21:45
*** baoli_ has joined #openstack-meeting-421:46
rbradforit seems to me, that new options, or changed defaults also merit applicable flagging, so it would be easier to generate docs,21:46
*** dims has quit IRC21:46
rbradfore.g. "Whats new", "Whats changed", "What's deprecated", "what's removed" sections of configuration options.21:46
rocky_gyeah.  release note stuff at a minimum21:46
rbradforthat IMO would help operators in upgrades21:46
rbradforI know there are release notes on this, but it's a human writing that.21:47
rocky_gright.  auto generate would be ideal21:47
rbradforif this was meta data, then the oslo-config-generator for example could have additional info at it's disposal21:47
jokke_rbradfor: I'd prefer instead of having "Deprecated; will be removed in release X.Y.Z" it having "Deprecated; will be removed on first release after 1.6.2016" or so21:48
jokke_that would give clear deprecation period regardless what has been released in between21:48
*** fitoduarte has joined #openstack-meeting-421:48
rbradforjokke_, I could see that reason. please add to ML21:48
jokke_rbradfor: will do tomorrow when I'm by my work mail again21:49
rbradforjokke_, sure21:49
rbradforso, back on the upgrade path.21:49
*** baoli has quit IRC21:49
rbradforwhat's at an operators disposal to know "whats changed/new/removed". do they simply diff sample confs between releases21:50
*** kebray has quit IRC21:50
*** spzala has quit IRC21:50
jokke_rbradfor: that's good one21:50
*** spzala has joined #openstack-meeting-421:51
jokke_specially when you look that bug you fixed ... good luck finding anything from those diffs21:51
jokke_before I mean21:51
*** piet has joined #openstack-meeting-421:51
rbradforyes, before was death, code introduced did not retain order21:52
rocky_gIt's one of the reasons I think it takes them 3-6 months to qualify an upgrade.  They have to find all this stuff.21:52
*** bpokorny_ has quit IRC21:52
*** bpokorny has joined #openstack-meeting-421:52
rocky_gThe other thing is that they can't allow their config files to be overwritten, or if they do, they then have to go back in and replace their changes21:52
jokke_rocky_g: I updated our templates, the tweet I linked was how I finally got it done and even then I missed some conditions there :(21:52
rocky_gjokke_, here's the link to the ml thread:  #link http://lists.openstack.org/pipermail/openstack-dev/2016-January/084126.html21:53
*** FallenPegasus has joined #openstack-meeting-421:53
jokke_the change for glance-api.conf + glance-registry.conf was give or take 3.5k lines :(21:53
jokke_thanks rocky_g21:54
*** Sukhdev has joined #openstack-meeting-421:55
rocky_gso, the config stuff is a really big painpoint for ops21:55
*** spzala has quit IRC21:55
jokke_yes and rbradfor fixing that bug will ease it up Newton forwards21:55
rocky_gthere was a huge thread on it when the samples were being removed.  I'll see if I can find it...21:55
jokke_as now folks gets version of configs from Mitaka and Newton will have just the real changes, not everything around the place21:56
*** spzala has joined #openstack-meeting-421:57
rbradforso, if each config option had the following attributes, (released, changed, deprecated, removal)  aka the cycle (sorry names for now), it would be infinitely easy to auto-generate all the lists an operator wants between releases21:57
*** harshs has joined #openstack-meeting-421:57
jokke_makes sense21:57
jokke_problem getting that released there at least21:58
*** harshs has left #openstack-meeting-421:58
jokke_as the release version will be mainly defined at the point when the release is cut based on the changes merged21:58
rbradforyes, it's some meta data, but it's a transition project during a full cycle, it's not trivial, but if a project got behind it, and then maintained it.21:59
jokke_and tracking such down will be too much to just throw at the release folks21:59
rbradfornew options when first merged are marked with "released"21:59
rbradforthen if changed, deprecated they are marked.  I'm sure the change/deprecate volume is way less22:00
jokke_ahh ... so you did not mean that those are fields with version defined when that happened22:00
rbradfortracking down should be determable via git blame or stable release tages.22:00
jokke_but rather state machine of the status of the option22:00
jokke_?22:00
rbradforit was just a thought now, let me describe it in an email with examples.22:01
jokke_sure22:01
jokke_good discussion folks ... unfortunately we're out of time22:02
rocky_goops.  you're right.  I've got a couple of mailing list links for rbradfor, then I'll call it.22:03
rocky_g#link http://lists.openstack.org/pipermail/openstack-operators/2014-December/005658.html22:03
*** spzala has quit IRC22:03
rocky_g#link http://lists.openstack.org/pipermail/openstack-operators/2015-January/005981.html22:03
rocky_gThis is a thread on how operators were going to try to deal with the confg opts changes/issues/lack of sample configs22:04
rocky_gThansk all!22:04
rocky_g#endmeeting22:04
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:04
openstackMeeting ended Wed Jan 27 22:04:35 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:04
openstackMinutes:        http://eavesdrop.openstack.org/meetings/log_wg/2016/log_wg.2016-01-27-21.05.html22:04
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/log_wg/2016/log_wg.2016-01-27-21.05.txt22:04
openstackLog:            http://eavesdrop.openstack.org/meetings/log_wg/2016/log_wg.2016-01-27-21.05.log.html22:04
*** salv-orl_ has joined #openstack-meeting-422:06
*** marcusvrn_ has quit IRC22:07
*** salv-orlando has quit IRC22:09
*** woodard_ has joined #openstack-meeting-422:10
*** bpokorny has quit IRC22:11
*** woodard has quit IRC22:14
*** woodard_ has quit IRC22:14
*** sridhar_ram has joined #openstack-meeting-422:22
*** lakshmiS has quit IRC22:22
*** paul-carlton2 has quit IRC22:25
*** jmckind_ has joined #openstack-meeting-422:26
*** piet has quit IRC22:28
*** jmckind has quit IRC22:30
*** bpokorny has joined #openstack-meeting-422:30
*** jmckind has joined #openstack-meeting-422:31
*** baoli_ has quit IRC22:33
*** jmckind_ has quit IRC22:33
*** daneyon has joined #openstack-meeting-422:34
*** banix has quit IRC22:34
*** bpokorny_ has joined #openstack-meeting-422:34
*** bpokorny_ has quit IRC22:35
*** daneyon_ has quit IRC22:35
*** bpokorny has quit IRC22:35
*** bpokorny has joined #openstack-meeting-422:36
*** daneyon_ has joined #openstack-meeting-422:36
*** daneyon has quit IRC22:40
*** jmckind has quit IRC22:41
*** neelashah1 has quit IRC22:42
*** sdake has quit IRC22:45
*** unicell1 is now known as unicell22:48
*** unicell has joined #openstack-meeting-422:48
*** dims has joined #openstack-meeting-422:51
*** dims has quit IRC22:54
*** Sukhdev has quit IRC22:57
*** lakshmiS has joined #openstack-meeting-423:00
*** davidlenwell has quit IRC23:06
*** davidlenwell has joined #openstack-meeting-423:08
*** JRobinson__ has joined #openstack-meeting-423:09
*** rocky_g has quit IRC23:11
*** bobh has quit IRC23:13
JRobinson__Good morning o/ The user guide team meeting is set to begin here in about 15 minutes.23:15
*** sigmavirus24 is now known as sigmavirus24_awa23:16
*** armax has joined #openstack-meeting-423:17
*** inc0 has quit IRC23:17
*** lwilliams_ has joined #openstack-meeting-423:18
*** sridhar_ram has quit IRC23:30
*** sridhar_ram1 has joined #openstack-meeting-423:30
*** dims_ has joined #openstack-meeting-423:30
JRobinson__Alright, let's begin23:30
JRobinson__#startmeeting docuserguides23:31
openstackMeeting started Wed Jan 27 23:31:09 2016 UTC and is due to finish in 60 minutes.  The chair is JRobinson__. Information about MeetBot at http://wiki.debian.org/MeetBot.23:31
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.23:31
*** openstack changes topic to " (Meeting topic: docuserguides)"23:31
openstackThe meeting name has been set to 'docuserguides'23:31
*** bpokorny_ has joined #openstack-meeting-423:31
JRobinson__The agenda is a short one, like late last year23:31
JRobinson__Three items to get through23:31
JRobinson__First, some role call time - who's hear for the user guide meeting today23:32
*** bpokorny_ has quit IRC23:32
*** bpokorny_ has joined #openstack-meeting-423:32
*** bpokorny has quit IRC23:35
JRobinson__Alright then onto the agenda23:35
JRobinson__#topic Collaborated with Murano, Trove, Sahara, and Magento23:36
*** openstack changes topic to "Collaborated with Murano, Trove, Sahara, and Magento (Meeting topic: docuserguides)"23:36
JRobinson__Last year there was some contact with the docs liasons of these four teams.23:36
JRobinson__#action Contact and follow up new content for administrators in the User Guides23:36
JRobinson__#action delegate contact with these teams23:37
JRobinson__That was the only point for collaboration at the moment.23:37
JRobinson__There have been no big changes since last year except for one Trove related patch to the Cloud Admin Guide23:37
JRobinson__#topic Information Architecture for the Guide23:38
*** openstack changes topic to "Information Architecture for the Guide (Meeting topic: docuserguides)"23:38
*** bpokorny_ has quit IRC23:38
JRobinson__Following patches to combined guide content, some of IA at the heading level is a bit confusing and unclear23:38
JRobinson__after more content is combined together, a review of the IA at the heading level would not go amiss here23:38
JRobinson__#action schedule a review of IA content on the combined guides with User Guide team23:39
JRobinson__#topic Contact the mailing list23:39
*** openstack changes topic to "Contact the mailing list (Meeting topic: docuserguides)"23:39
JRobinson__Some contributors have expressed an interest in contributing to the User Guide Reworking.23:39
JRobinson__The action here is to follow up with them.23:40
*** bpokorny has joined #openstack-meeting-423:40
*** spotz is now known as spotz_zzz23:40
JRobinson__#action Follow up with contributors interested in working on the User Guide reorg23:40
JRobinson__#topic open discussion23:40
*** openstack changes topic to "open discussion (Meeting topic: docuserguides)"23:40
JRobinson__That was all for the meeting. If there are no futher topics I'll close this down23:40
*** avarner has quit IRC23:42
JRobinson__Alright, thanks everyone o/23:42
JRobinson__#endmeeting23:42
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"23:42
openstackMeeting ended Wed Jan 27 23:42:41 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)23:42
openstackMinutes:        http://eavesdrop.openstack.org/meetings/docuserguides/2016/docuserguides.2016-01-27-23.31.html23:42
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/docuserguides/2016/docuserguides.2016-01-27-23.31.txt23:42
openstackLog:            http://eavesdrop.openstack.org/meetings/docuserguides/2016/docuserguides.2016-01-27-23.31.log.html23:42
*** bpokorny has quit IRC23:42
*** Sukhdev has joined #openstack-meeting-423:46
*** rbak has quit IRC23:46
*** bpokorny has joined #openstack-meeting-423:49
*** Sukhdev has quit IRC23:49
*** lwilliams_ has quit IRC23:49
*** Sukhdev has joined #openstack-meeting-423:51
*** Sukhdev has quit IRC23:52
*** Sukhdev has joined #openstack-meeting-423:52
*** klamath has quit IRC23:53
*** Sukhdev has quit IRC23:54
*** Sukhdev has joined #openstack-meeting-423:54
*** Sukhdev has quit IRC23:56
*** Sukhdev has joined #openstack-meeting-423:56
*** Sukhdev has quit IRC23:57
*** Sukhdev has joined #openstack-meeting-423:58
*** Sukhdev has quit IRC23:59

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