Wednesday, 2016-01-13

*** rbak has joined #openstack-meeting-400:00
*** spzala has quit IRC00:00
*** kebray has quit IRC00:01
*** jmccrory has quit IRC00:04
*** bharathm has joined #openstack-meeting-400:04
*** baoli has quit IRC00:07
*** dims has joined #openstack-meeting-400:09
*** gjayavelu has quit IRC00:09
*** cemmason has joined #openstack-meeting-400:14
*** harshs has quit IRC00:14
*** cemmason1 has quit IRC00:15
*** salv-orl_ has quit IRC00:16
*** piet has quit IRC00:17
*** salv-orlando has joined #openstack-meeting-400:17
*** piet has joined #openstack-meeting-400:20
*** bpokorny_ has quit IRC00:20
*** bpokorny has joined #openstack-meeting-400:21
*** sigmavirus24 is now known as sigmavirus24_awa00:21
*** xingchao has joined #openstack-meeting-400:24
*** spzala has joined #openstack-meeting-400:24
*** sdake has joined #openstack-meeting-400:24
*** rbak has quit IRC00:25
*** spzala has quit IRC00:28
*** irenab_ has joined #openstack-meeting-400:30
*** cemmason has quit IRC00:31
*** cemmason has joined #openstack-meeting-400:31
*** Swami has joined #openstack-meeting-400:32
*** irenab has quit IRC00:33
*** irenab_ is now known as irenab00:33
*** bharathm has quit IRC00:33
*** bharathm has joined #openstack-meeting-400:34
*** cemmason1 has joined #openstack-meeting-400:35
*** cemmason has quit IRC00:36
*** vikasc has quit IRC00:44
*** spotz_zzz is now known as spotz00:50
*** markmcclain has quit IRC00:53
*** Sukhdev has quit IRC00:55
*** markmcclain has joined #openstack-meeting-400:55
*** cemmason1 has quit IRC00:56
*** cemmason has joined #openstack-meeting-400:56
*** cemmason1 has joined #openstack-meeting-400:59
*** cemmason has quit IRC00:59
*** Jeffrey4l has joined #openstack-meeting-401:03
*** piet has quit IRC01:07
*** ekarlso has quit IRC01:10
*** xingchao has quit IRC01:14
*** prashantD has quit IRC01:14
*** cemmason has joined #openstack-meeting-401:15
*** cemmason1 has quit IRC01:15
*** cemmason has quit IRC01:18
*** xingchao has joined #openstack-meeting-401:18
*** cemmason has joined #openstack-meeting-401:18
*** xingchao has quit IRC01:23
*** bharathm has quit IRC01:26
*** dims has quit IRC01:38
*** spzala has joined #openstack-meeting-401:40
*** cemmason has quit IRC01:44
*** cemmason has joined #openstack-meeting-401:45
*** banix has quit IRC01:45
*** piet has joined #openstack-meeting-401:47
*** xingchao has joined #openstack-meeting-401:49
*** piet has quit IRC02:01
*** baohua has joined #openstack-meeting-402:01
*** bpokorny_ has joined #openstack-meeting-402:06
*** bpokorny has quit IRC02:09
*** bpokorny_ has quit IRC02:10
*** Swami has quit IRC02:13
*** cemmason has quit IRC02:14
*** cemmason has joined #openstack-meeting-402:14
*** natarajk has left #openstack-meeting-402:16
*** tfukushima has joined #openstack-meeting-402:18
*** armax has joined #openstack-meeting-402:21
*** tfukushima has quit IRC02:25
*** tfukushima has joined #openstack-meeting-402:26
*** tfukushima has quit IRC02:28
*** piet has joined #openstack-meeting-402:28
*** tfukushima has joined #openstack-meeting-402:29
*** tfukushima has quit IRC02:31
*** tfukushima has joined #openstack-meeting-402:31
*** tfukushima has quit IRC02:33
*** tfukushima has joined #openstack-meeting-402:34
*** tfukushima has quit IRC02:36
*** tfukushima has joined #openstack-meeting-402:36
*** avarner has joined #openstack-meeting-402:37
*** tfukushima has quit IRC02:38
*** markmcclain has quit IRC02:39
*** tfukushima has joined #openstack-meeting-402:39
*** markmcclain has joined #openstack-meeting-402:40
*** tfukushima has quit IRC02:41
*** tfukushima has joined #openstack-meeting-402:42
*** cemmason has quit IRC02:42
*** cemmason has joined #openstack-meeting-402:43
*** tfukushima has quit IRC02:43
*** tfukushima has joined #openstack-meeting-402:44
*** spotz is now known as spotz_zzz02:44
*** tfukushima has quit IRC02:46
*** cemmason1 has joined #openstack-meeting-402:46
*** cemmason has quit IRC02:47
*** tfukushima has joined #openstack-meeting-402:47
*** tfukushima has quit IRC02:49
*** cemmason1 has quit IRC02:49
*** cemmason has joined #openstack-meeting-402:49
*** tfukushima has joined #openstack-meeting-402:49
*** piet has quit IRC02:50
*** tfukushima has quit IRC02:51
*** tfukushima has joined #openstack-meeting-402:52
*** cemmason1 has joined #openstack-meeting-402:53
*** cemmason has quit IRC02:53
*** tfukushima has quit IRC02:54
*** tfukushima has joined #openstack-meeting-402:55
*** tfukushima has quit IRC02:56
*** tfukushima has joined #openstack-meeting-402:57
*** dtardivel has quit IRC02:57
*** tfukushima has quit IRC02:59
*** tfukushima has joined #openstack-meeting-402:59
*** tfukushima has quit IRC03:01
*** tfukushima has joined #openstack-meeting-403:02
*** sigmavirus24_awa is now known as sigmavirus2403:02
*** tfukushima has quit IRC03:04
*** spzala has quit IRC03:04
*** spzala has joined #openstack-meeting-403:04
*** tfukushima has joined #openstack-meeting-403:05
*** cemmason1 has quit IRC03:05
*** tfukushima has quit IRC03:06
*** yamamoto_ has joined #openstack-meeting-403:07
*** tfukushima has joined #openstack-meeting-403:07
*** spzala has quit IRC03:09
*** tfukushima has quit IRC03:09
*** tfukushima has joined #openstack-meeting-403:10
*** tfukushima has quit IRC03:12
*** tfukushima has joined #openstack-meeting-403:12
*** markmcclain has quit IRC03:12
*** tfukushima has quit IRC03:14
*** tfukushima has joined #openstack-meeting-403:15
*** markmcclain has joined #openstack-meeting-403:15
*** tfukushima has quit IRC03:17
*** dingboopt has quit IRC03:17
*** yamahata has quit IRC03:17
*** dims has joined #openstack-meeting-403:17
*** tfukushima has joined #openstack-meeting-403:17
*** tfukushima has quit IRC03:17
*** tfukushi_ has joined #openstack-meeting-403:17
*** xingchao has quit IRC03:19
*** tfukushi_ has quit IRC03:19
*** ekarlso has joined #openstack-meeting-403:20
*** tfukushima has joined #openstack-meeting-403:20
*** xingchao has joined #openstack-meeting-403:20
*** tfukushima has quit IRC03:22
*** woodard has quit IRC03:22
*** tfukushima has joined #openstack-meeting-403:23
*** neelashah has joined #openstack-meeting-403:23
*** tfukushima has quit IRC03:24
*** tfukushima has joined #openstack-meeting-403:25
*** sigmavirus24 is now known as sigmavirus24_awa03:32
*** dims has quit IRC03:33
*** coolsvap|away is now known as coolsvap03:37
*** markmcclain has quit IRC03:37
*** markmcclain has joined #openstack-meeting-403:38
*** Jeffrey4l has quit IRC03:40
*** vikasc has joined #openstack-meeting-403:44
*** markmcclain has quit IRC03:52
*** Jeffrey4l has joined #openstack-meeting-403:53
*** banix has joined #openstack-meeting-404:03
*** bpokorny has joined #openstack-meeting-404:09
*** salv-orl_ has joined #openstack-meeting-404:10
*** Jeffrey4l has quit IRC04:11
*** salv-orlando has quit IRC04:13
*** Jeffrey4l has joined #openstack-meeting-404:23
*** woodard has joined #openstack-meeting-404:24
*** markmcclain has joined #openstack-meeting-404:24
*** bharathm has joined #openstack-meeting-404:27
*** woodard has quit IRC04:28
*** markmcclain has quit IRC04:29
*** bharathm has quit IRC04:31
*** xingchao has quit IRC04:33
*** tfukushima has quit IRC04:40
*** tfukushima has joined #openstack-meeting-404:41
*** sdake_ has joined #openstack-meeting-404:47
*** sdake has quit IRC04:48
*** woodard has joined #openstack-meeting-404:49
*** xingchao has joined #openstack-meeting-404:50
*** sdake_ has quit IRC04:53
*** tfukushima has quit IRC04:53
*** sdake has joined #openstack-meeting-404:55
*** neelashah has quit IRC04:58
*** numans has joined #openstack-meeting-405:00
*** GB21 has joined #openstack-meeting-405:01
*** baohua has quit IRC05:02
*** Sukhdev has joined #openstack-meeting-405:03
*** baohua has joined #openstack-meeting-405:04
*** piet has joined #openstack-meeting-405:04
*** GB21 has quit IRC05:08
*** Swami has joined #openstack-meeting-405:08
*** markmcclain has joined #openstack-meeting-405:12
*** sdake has quit IRC05:16
*** sridhar_ram has joined #openstack-meeting-405:18
*** xingchao_ has joined #openstack-meeting-405:19
*** markmcclain has quit IRC05:21
*** xingchao has quit IRC05:22
*** GB21 has joined #openstack-meeting-405:37
*** piet has quit IRC05:38
*** tfukushima has joined #openstack-meeting-405:39
*** apoorv has joined #openstack-meeting-405:47
*** markmcclain has joined #openstack-meeting-405:50
*** bpokorny has quit IRC05:53
*** avarner has quit IRC05:54
*** xingchao_ has quit IRC05:54
*** markmcclain has quit IRC05:56
*** prashantD has joined #openstack-meeting-405:56
*** GB21 has quit IRC06:05
*** banix has quit IRC06:06
*** javeriak has joined #openstack-meeting-406:08
*** javeriak has quit IRC06:10
*** javeriak has joined #openstack-meeting-406:10
*** xingchao has joined #openstack-meeting-406:14
*** javeriak_ has joined #openstack-meeting-406:14
*** xingchao_ has joined #openstack-meeting-406:15
*** javeriak has quit IRC06:15
*** xingchao has quit IRC06:19
*** GB21 has joined #openstack-meeting-406:24
*** hdaniel_ has joined #openstack-meeting-406:24
*** markvoelker has quit IRC06:27
*** dshakhray has joined #openstack-meeting-406:32
*** prashantD has quit IRC06:34
*** amit213 has quit IRC06:35
*** amit213 has joined #openstack-meeting-406:35
*** xingchao has joined #openstack-meeting-406:37
*** xingchao_ has quit IRC06:40
*** yamahata has joined #openstack-meeting-406:47
*** mrunge has joined #openstack-meeting-406:48
*** Sukhdev has quit IRC06:52
*** baohua has quit IRC06:53
*** hdaniel_ has quit IRC06:55
*** hdaniel_ has joined #openstack-meeting-406:55
*** tfukushima has quit IRC07:02
*** sridhar_ram has quit IRC07:02
*** tfukushima has joined #openstack-meeting-407:04
*** sridhar_ram has joined #openstack-meeting-407:06
*** Swami has quit IRC07:10
*** med_ has quit IRC07:12
*** med_ has joined #openstack-meeting-407:14
*** med_ is now known as Guest7712107:14
*** tfukushima has quit IRC07:17
*** hdaniel_ has quit IRC07:18
*** tfukushima has joined #openstack-meeting-407:19
*** paul-carlton2 has joined #openstack-meeting-407:24
*** markvoelker has joined #openstack-meeting-407:28
*** apoorv has quit IRC07:31
*** markvoelker has quit IRC07:33
*** paul-carlton2 has quit IRC07:34
*** nkrinner has joined #openstack-meeting-407:44
*** paul-carlton2 has joined #openstack-meeting-407:47
*** woodard has quit IRC07:49
*** hdaniel_ has joined #openstack-meeting-407:56
*** salv-orl_ has quit IRC08:04
*** salv-orlando has joined #openstack-meeting-408:04
*** Jeffrey4l has quit IRC08:12
*** paul-carlton2 has quit IRC08:12
*** paul-carlton2 has joined #openstack-meeting-408:25
*** hdaniel has joined #openstack-meeting-408:26
*** dtardivel has joined #openstack-meeting-408:28
*** matrohon has joined #openstack-meeting-408:29
*** Jeffrey4l has joined #openstack-meeting-408:29
*** hdaniel_ has quit IRC08:29
*** GB21 has quit IRC08:30
*** yamahata has quit IRC08:32
*** apoorv has joined #openstack-meeting-408:41
*** ihrachys has joined #openstack-meeting-408:43
*** paul-carlton2 has quit IRC08:46
*** mbound has joined #openstack-meeting-408:51
*** javeriak_ has quit IRC08:51
*** tfukushima has quit IRC08:53
*** markvoelker has joined #openstack-meeting-408:54
*** tfukushima has joined #openstack-meeting-408:55
*** markvoelker has quit IRC08:59
*** salv-orlando has quit IRC09:02
*** salv-orlando has joined #openstack-meeting-409:03
*** amotoki has joined #openstack-meeting-409:10
*** shz has quit IRC09:10
*** hdaniel has quit IRC09:12
*** mbound_ has joined #openstack-meeting-409:20
*** mbound has quit IRC09:20
*** zeih has joined #openstack-meeting-409:24
*** hdaniel has joined #openstack-meeting-409:25
*** mfedosin has joined #openstack-meeting-409:25
*** GB21 has joined #openstack-meeting-409:25
*** salv-orlando has quit IRC09:28
*** salv-orlando has joined #openstack-meeting-409:28
*** paul-carlton2 has joined #openstack-meeting-409:28
*** javeriak has joined #openstack-meeting-409:31
*** mfedosin has quit IRC09:33
*** _degorenko|afk is now known as degorenko09:41
*** coolsvap is now known as coolsvap|away09:56
*** tfukushima has quit IRC10:07
*** GheRiver1 has joined #openstack-meeting-410:08
*** salv-orl_ has joined #openstack-meeting-410:09
*** GheRiver1 has quit IRC10:12
*** GheRiver1 has joined #openstack-meeting-410:12
*** salv-orlando has quit IRC10:13
*** salv-orl_ has quit IRC10:16
*** GheRiver1 has quit IRC10:17
*** salv-orlando has joined #openstack-meeting-410:17
*** GheRiver1 has joined #openstack-meeting-410:17
*** baigk has quit IRC10:19
*** baigk has joined #openstack-meeting-410:25
*** markvoelker has joined #openstack-meeting-410:55
*** markvoelker has quit IRC11:00
*** markvan has quit IRC11:09
*** xingchao has quit IRC11:09
*** xingchao has joined #openstack-meeting-411:09
*** markvan has joined #openstack-meeting-411:10
*** hughsaunders has quit IRC11:10
*** hughsaunders has joined #openstack-meeting-411:12
*** xingchao has quit IRC11:15
*** GheRiver1 has quit IRC11:18
*** mjblack has joined #openstack-meeting-411:19
*** GheRiver1 has joined #openstack-meeting-411:21
*** sdake has joined #openstack-meeting-411:29
*** dingboopt has joined #openstack-meeting-411:30
*** sdake has quit IRC11:34
*** markvoelker has joined #openstack-meeting-411:56
*** markvoelker has quit IRC12:00
*** javeriak has quit IRC12:04
*** GheRiver1 has quit IRC12:05
*** salv-orlando has quit IRC12:05
*** baoli has joined #openstack-meeting-412:05
*** salv-orlando has joined #openstack-meeting-412:05
*** rbak has joined #openstack-meeting-412:07
*** baoli has quit IRC12:08
*** devananda has quit IRC12:08
*** xingchao has joined #openstack-meeting-412:11
*** devananda has joined #openstack-meeting-412:13
*** rbak has quit IRC12:16
*** baoli has joined #openstack-meeting-412:16
*** xingchao has quit IRC12:17
*** baoli has quit IRC12:18
*** vikasc has quit IRC12:19
*** apoorv has quit IRC12:25
*** GB21 has quit IRC12:27
*** sdake has joined #openstack-meeting-412:27
*** dims has joined #openstack-meeting-412:28
*** julim has joined #openstack-meeting-412:33
*** salv-orlando has quit IRC12:37
*** salv-orlando has joined #openstack-meeting-412:37
*** woodard has joined #openstack-meeting-412:43
*** woodard has quit IRC12:49
*** fhermeni has joined #openstack-meeting-412:50
*** qwebirc44923 has joined #openstack-meeting-412:51
*** qwebirc44923 has left #openstack-meeting-412:52
fhermenihello12:52
*** markvoelker has joined #openstack-meeting-412:57
*** markvoelker has quit IRC13:02
fhermeniIs this the meeting room for the watcher project ?13:10
*** klamath has joined #openstack-meeting-413:13
*** klamath has quit IRC13:13
*** klamath has joined #openstack-meeting-413:14
*** dslevin has quit IRC13:15
*** javeriak has joined #openstack-meeting-413:23
*** javeriak has quit IRC13:23
*** javeriak has joined #openstack-meeting-413:24
*** baoli has joined #openstack-meeting-413:25
*** dims has quit IRC13:25
*** dims has joined #openstack-meeting-413:26
*** dslev has joined #openstack-meeting-413:27
*** pbelamge__ has joined #openstack-meeting-413:29
*** javeriak_ has joined #openstack-meeting-413:30
*** javeriak has quit IRC13:31
*** markvoelker has joined #openstack-meeting-413:31
*** cdupont has joined #openstack-meeting-413:34
*** baoli_ has joined #openstack-meeting-413:37
*** baoli has quit IRC13:40
*** javeriak has joined #openstack-meeting-413:40
*** javeriak_ has quit IRC13:41
*** vincentfrancoise has joined #openstack-meeting-413:45
*** numans has quit IRC13:49
*** shawnlee has joined #openstack-meeting-413:52
*** dslev has quit IRC13:55
*** gjayavelu has joined #openstack-meeting-413:55
*** javeriak_ has joined #openstack-meeting-413:57
*** ShillaSaebi has joined #openstack-meeting-413:58
*** ShillaSaebi has left #openstack-meeting-413:59
*** javeriak has quit IRC13:59
jed56fhermeni : yes14:00
acabot#startmeeting watcher14:00
openstackMeeting started Wed Jan 13 14:00:30 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
jed56o/14:00
dtardivelHi14:00
tpeopleso/14:00
vincentfrancoiseo/14:00
acabotagenda for today #link https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#01.2F13.2F201614:00
fhermenihi14:01
edleafe\o14:01
*** bzhou has joined #openstack-meeting-414:01
cduponthi14:02
acabot#topic Annoucements14:02
*** openstack changes topic to "Annoucements (Meeting topic: watcher)"14:02
*** yamamoto_ has quit IRC14:02
acabot#info 1st draft of mid-cycle agenda is available https://wiki.openstack.org/wiki/Watcher_mitaka_mid-cycle_meetup_agenda#Agenda14:02
sballeo/14:02
acabotfeel free to change timings and subjects14:03
sballeacabot: Do you know if we can do working lunches? I think an hour for lunch is a long time.14:03
*** brunograz has joined #openstack-meeting-414:04
sballemaybe we do lunch in 30 minutes14:04
acabotsballe: thats my french spirit ;-)14:04
*** pmesserli has joined #openstack-meeting-414:04
sballelol14:04
jed56Maybe we can a topic regarding ceilometer ( performance, cache, .. )14:05
sballe+114:05
acabotI will ask jwcroppe14:05
acabot#action acabot add a topic regarding ceilometer to the agenda14:05
sballejed56: I would add that topic to open discussions. Not sure we 2 hours for open discussions14:05
acabotthe Nova mid-cycle will take place in Bristol in 2 weeks and they plan to discuss scheduler improvements https://etherpad.openstack.org/p/mitaka-nova-priorities-tracking14:06
jed56sballe : I am just wondering what we're doing to make us think Ceilometer won't pose a performance problem? Is there some other caching that's happening somewhere?14:06
acabotI wont be able to attend but we should look at the etherpads between the 2 meetings14:06
acabotany other announcement ?14:07
sballeacabot: I cannot go either to the Nova meeting. I hope jwcroppe can go14:07
edleafeI won't be at the Nova mid-cycle either14:07
sballejed56: I think Ceilomter is a problem so I would like for us to discss that14:07
acabot#topic Review Action Items14:08
*** openstack changes topic to "Review Action Items (Meeting topic: watcher)"14:08
sballejed56 I think we said it wasn't a problem for the poc since we weren't doing produciton liek stuff14:08
tpeoplesi don't think jwcroppe was planning on making it to the nova midcycle14:08
acabotok14:08
acabotsballe: maybe we should discuss also Monasca integration ;-)14:09
jed56acabot: +114:09
sballeok. acabot since you guys are kind of local could you send somebody just so our voice is heard14:09
sballeMonasca and Ceilosca should be considered.14:09
*** dslev has joined #openstack-meeting-414:10
acabotsballe: unfortunately I cant but I had a discussion with bauzas who will attend about our requirements, I'm also in discussion with him to submit a talk for the summit14:10
sballeok cool!14:10
acabotlets move to Watcher specs now14:10
*** neelashah has joined #openstack-meeting-414:11
acabot#info Intel POC specs have been merged14:11
*** gjayavelu has left #openstack-meeting-414:11
*** GB21 has joined #openstack-meeting-414:12
acabot#info dynamic actions specs have been merged and there is a lot of code moving right now14:12
sballeyeah +1 thx to everybody who contributed to make that happen14:12
*** GB21 has quit IRC14:12
acabot#link https://review.openstack.org/#/q/status:open+project:openstack/watcher+branch:master+topic:bp/watcher-add-actions-via-conf14:12
acabotall these reviews will have to be merged at the same time14:13
acabotjed56: do you think we can do it by end of week ?14:13
sballeok14:13
jed56yes I think a waiting for last reviews14:13
acabotthere are still 2 specs open regarding consolidation grammar and constraints management14:14
acabotsballe: did you have a look at them ?14:14
dtardiveltpeoples: we waiting for another +2 on these patchsets ;)14:15
acabotcdupont: do you handle both of them ?14:15
cdupontyes14:15
cdupontthey are in our hands14:15
tpeopleslooking dtardivel14:15
*** woodard has joined #openstack-meeting-414:15
sballeacabot: I will look at them today/ I have been traveling and it messes up my todos14:15
cdupontit's a proof of concept for a strategy using BtrPlace14:15
acabotcdupont: as I said in my last comment, I dont think we should have our own system dealing with constraints14:16
*** woodard has quit IRC14:16
cdupontOK14:16
sballe+114:16
cdupontI'm not sure I understood your comment :)14:16
cdupontWhere would the constraints come from?14:16
*** woodard has joined #openstack-meeting-414:16
acabotcdupont : Nova14:16
cdupontbut the implementation/solver could be in Watcher?14:17
jed56cdupont: yes14:17
cdupontOK14:17
cdupontso this work should be paused?14:17
acabotcdupont : yes but the way you have written specs, you dont get constraints from Nova14:17
cdupontI see14:17
jed56IMHO, we have to pull the constraints from (congress, nova, ... )14:17
jed56and then use it we any strategies or sovler14:18
acabot+1 and then deal with consolidation through algorithms in Watcher14:18
cduponthow the constraints are solved at the moment?14:18
sballe+1 on what jed56 said14:18
*** salv-orlando has quit IRC14:18
jed56cdupont : we don't :p14:18
cdupontI mean, this is an NP hard problem, so only using filters is limited14:18
*** salv-orlando has joined #openstack-meeting-414:18
jed56we have to call nova filters  for the P.OC14:19
jed56https://blueprints.launchpad.net/watcher/+spec/helper-nova-select-destinations14:19
*** njohnston has joined #openstack-meeting-414:19
jed56cdupont : +114:19
*** jpeeler has joined #openstack-meeting-414:19
*** jpeeler has quit IRC14:19
*** jpeeler has joined #openstack-meeting-414:19
acabotcdupont : we are looking at how to get these constraints from Nova #link https://blueprints.launchpad.net/watcher/+spec/helper-nova-select-destinations14:19
cdupontusing a solver like CP solver / linear integer etc. can lead to better placements14:19
edleafejed56: remember, though, there is no public interface to Nova's filtering14:19
acabotcdupont: but its a tricky question14:20
jed56edlefe : yes sadly14:20
edleafejed56: and there isn't any planned in the future14:20
jed56I think we can deal with contraints without nova filter but something it can be nice to use it14:20
acabotedleafe: right, we need to discuss it at the mid-cycle14:20
edleafethe best way to work with nova is to select a host and then call live-migrate. If the host doesn't match the filter requirement, catch that and retry14:21
cdupontSo I'll wait that this question is stabilised to make progress14:21
bzhouremeber, scheduler select_destinations() only returns one host per instance14:21
sballeI agree this is a good topic for the mid-ccyle14:21
jed56bzhou : +114:21
sballebzhou: +114:21
edleafebzhou: remember too that there is no way to call select_destinations from outside of Nova.14:21
acabotcdupont: I will keep your BPs in discussion state for now14:21
cdupontacabot: OK14:21
sballeacabot: We should bring this up as an issues at the nova mid-cycle. can you pass this on to your contact14:22
bzhouas we use live migration in watcher, we can leverage nova's bp: check_destination14:22
jed56IMHO, the first thing is to find the best way to collect the constraints14:22
acabotsballe: I will14:22
bzhouwhich will fail if the specified target host cannot pass filters14:22
sballeacabot: thx14:22
jed56if we want to solve it14:22
*** baoli_ has quit IRC14:22
edleafebzhou: yes, that seems to be the only way. Select a host, and let check_destination reject it if necessary14:22
acabot#action acabot give bauzas a more detailed view of our requirements on Nova scheduler14:23
*** baoli has joined #openstack-meeting-414:23
*** pbelamge__ has quit IRC14:23
tpeoplesthat's definitely going to have scale issues edleafe , but i understand currently that would be our only option.  i think we should at least try to work with nova to get something better14:23
bzhoutpeoples: +114:23
acabottpeoples : +114:23
edleafetpeoples: agreed. But when I spoke with people there after last week's meeting, they didn't seem very eager14:24
edleafeUnfortunately, the scheduler is strictly internal to Nova for the foreseeable future14:24
edleafe:(14:24
bzhouedleafe: I read your discussion. I heard Neutron also wants a similar feature?14:24
tpeoples:( acabot  can we work with bauzas to understand if using the scheduler filters in the way we want is out of the picture?14:25
edleafeNeutron, Cinder, and one or two others all have generic scheduling needs14:25
acabotbzhou : yes Neutron has pretty much the same use case and they plan to discuss it full day during the nova mid-cycle14:25
sballetpeoples: +114:25
edleafeBut nova's scheduler is specific to compute resources14:25
edleafeit can't handle anything else14:25
sballe+114:25
edleafeit even has a very hard time with ironic14:25
sballelol +114:26
tpeoplesis that the goal of the super scheduler by harlowja, to fill this void?14:26
tpeoplesi haven't had time to look into that much14:26
edleafetpeoples: not familiar with that. Link?14:26
sballeIMO we don't need a super scheduler We just need ApI to the various schedulers14:26
acabothttps://review.openstack.org/#/c/210549/14:26
jed56#link https://review.openstack.org/#/c/210549/14:26
acabotfhermeni is working on this review14:27
sballethx I hadn't seen that work14:27
acabotit is done on "OpenStack global specs"14:27
*** baoli_ has joined #openstack-meeting-414:27
tpeoplesno acabot, i don't want to go into the deep end with that super scheduler, just wanted to mention it.14:27
fhermenitpeoples: the purpose of the « super-scheduler » is to provide a unique entry point to every scheduling aspects. The implementation at the backend might handle the scheduling completely or split and forward to different schedulers (nova, neutron …)14:28
sballeok just added myself as a reviewer14:28
acabot#info there is a super-scheduler wip https://review.openstack.org/#/c/210549/14:28
fhermenitpeoples: it just exposes an entry point where users specify their expectations in terms of scheduling14:28
*** dslev has quit IRC14:29
acabotsorry, I'm coming back to the agenda14:29
tpeoplesthanks fhermeni14:29
acabot#info devstack plugin has been merged14:29
sballecool! +114:29
sballegreat job tpeoples14:29
tpeoplesdo we want to send a note to the ML about this ?14:30
sballedefinetly14:30
acabotthx for that, it was one of our Mitaka priorities14:30
bzhoutpeoples: great, thanks14:30
*** baoli has quit IRC14:30
tpeoples#action tpeoples send note to ML regarding devstack14:30
acabotthx14:30
acabotdtardivel started working on Watcher CLI14:31
acabotto bring Watcher evolutions in our client14:31
dtardiveltpeoples: we have to validate again live migration triggered by Watcher on devstack14:31
*** vhoward has joined #openstack-meeting-414:31
acabot#info Watcher client launchpad is now set up https://blueprints.launchpad.net/python-watcherclient14:31
dtardiveltpeoples: this is an opened bug on it :)14:31
tpeopleslink?14:32
tpeoplesah yes14:32
dtardivel#link https://bugs.launchpad.net/watcher/+bug/153191214:32
openstackLaunchpad bug 1531912 in watcher ""MIGRATE" action triggered by Watcher Applier failed on devstack" [High,Confirmed] - Assigned to David TARDIVEL (david-tardivel)14:32
tpeoplesi have a workaround for that, but i was waiting for jed56's refactoring stuff to merge first14:32
acabotnow, when you submit a BP, please think about where it is the most suitable (Watcher or Watcher CLI)14:32
acabot#topic14:33
*** openstack changes topic to " (Meeting topic: watcher)"14:33
acabot#topic Blueprint/Bug Review and Discussion14:33
*** openstack changes topic to "Blueprint/Bug Review and Discussion (Meeting topic: watcher)"14:33
tpeoplessame as you dtardivel, so OK :)14:33
acabotcould everyone update the delivery field of its BPs ? https://blueprints.launchpad.net/watcher14:34
acabotit would be much easier for me to track progress !14:34
dtardivelacabot: +114:34
tpeopleswill do14:35
acabot#action jed56 seanmurphy vmahe acabot tpeoples vincentfrancoise bzhou update delivery field on launchpad for affected blueprints14:35
acabotany update on BPs from alexstav ?14:36
tpeoplesdoesn't look like he's here14:36
acabottpeoples : thx ;-)14:36
tpeoplesif i see him on irc i'll ask him during the US day14:37
acabotwe need to create a new repo for Watcher UI (in horizon)14:37
*** dingboopt has quit IRC14:37
*** piet has joined #openstack-meeting-414:37
acabotcan we agree on naming it "Watcher dashboard" as it is the common name used by other openstack projects ?14:37
tpeopleswatcher-dashboard, watcher-ui14:38
tpeoplesi'm fine with either14:38
acabotor anyone wants another name ?14:38
*** dslevin has joined #openstack-meeting-414:38
jed56watcher-ui14:38
jed56the other projects => monasca-ui, magnum-ui ,  zaqar-ui14:38
vincentfrancoisewatcher-dashboard14:38
tpeoples:D14:39
vincentfrancoisebut doesn't matter to me really14:39
sballeI like to follow the rest of openstack14:39
acabotjed56 : ok murano-dashboard, cloudkitty-dashboard ;-)14:39
jed56yes  : )14:39
sballelol14:39
jed56vincentfrancoise:+114:39
dtardivelI prefer watcher-ui. this is the name used internaly14:40
sballedashboard is probably better in case we later get a ops-console14:40
sballeui can be dashboard and console14:40
sballebut I can go either way14:40
acabot#startvote Watcher UI name ? watcher-ui, watcher-dashboard, dont care14:41
openstackBegin voting on: Watcher UI name ? Valid vote options are watcher-ui, watcher-dashboard, dont, care.14:41
openstackVote using '#vote OPTION'. Only your last vote counts.14:41
dtardivel#vote watcher-ui14:41
acabot#vote watcher-dashboard14:41
vincentfrancoise#vote watcher-dashboard14:41
brunograz#vote watcher-dashboard14:41
sballe#vote watcher-dashboard14:41
jed56#vote watcher-ui   :p14:41
tpeoples#vote watcher-ui14:41
openstackjed56: watcher-ui   :p is not a valid option. Valid options are watcher-ui, watcher-dashboard, dont, care.14:41
edleafe#vote watcher-dashboard14:41
jed56#vote watcher-ui14:42
bzhou#vote watcher-dashboard14:42
acabot#showvote14:42
openstackwatcher-dashboard (6): bzhou, vincentfrancoise, sballe, acabot, edleafe, brunograz14:42
openstackwatcher-ui (3): tpeoples, dtardivel, jed5614:42
fhermeni#vote watcher-ui14:42
tpeoplesdashboard it is14:42
sballe:)14:42
acabot#endvote14:42
openstackVoted on "Watcher UI name ?" Results are14:42
tpeopleseven with fhermeni ^14:42
openstackwatcher-dashboard (6): bzhou, vincentfrancoise, sballe, acabot, edleafe, brunograz14:42
openstackwatcher-ui (4): tpeoples, dtardivel, jed56, fhermeni14:42
acabotlets go with watcher-dashboard14:43
acabotthx14:43
jed56good luck dtarvidel for the refactoring !14:43
tpeopleshaha14:43
sballeups!14:43
jed56I was in your side :p14:43
dtardiveljed56: :(14:43
fhermeni:D14:43
sballedtardivel: sorry about that :(14:43
acabot#info bugs status for mitaka-2 https://launchpad.net/watcher/+milestone/mitaka-214:44
acabotwe should freeze mitaka-2 around January 20th14:44
*** Swami has joined #openstack-meeting-414:44
acabot#info we will need someone on this one https://bugs.launchpad.net/watcher/+bug/152718914:45
openstackLaunchpad bug 1527189 in watcher "Update the documentation to explain how to change the ceilometer API backend" [High,New]14:45
acabot#topic Open Discussion14:46
*** openstack changes topic to "Open Discussion (Meeting topic: watcher)"14:46
acabot14 minutes left14:46
sballeCan we talk about the talk submisisons14:46
acabotProposed talks are still in review https://etherpad.openstack.org/p/Watcher_abstracts_austin201614:46
acabotand sballe wants to submit them asap14:47
acabotcan we submit them by end of week ?14:47
sballeI just need the email addresses people use with openstack.14:47
sballeplease add them to the etherpad14:47
acabotok14:48
acabotglobal requirements https://bugs.launchpad.net/watcher/+bug/153328214:48
openstackLaunchpad bug 1533282 in watcher "Watcher should use openstack global requirements" [Undecided,New] - Assigned to Taylor Peoples (tpeoples)14:48
sballeWho else should be onthe "Watcher a Resource Manager for OpenStack: Plans for the N-release and beyond" talk14:48
*** yamamoto has joined #openstack-meeting-414:48
sballeI have acabot, jwcroppe and sballe14:48
tpeoplesi'd be interested in talking for the demo regarding devstack sballe14:48
acabottpeoples: put your name on the hands-on lab14:49
sballe+114:49
tpeoplesalright14:49
tpeoplesdtardivel and I discussed yesterday and agreed that we should be included in openstack/requirements project14:49
sballefor the hands on we will need more people to help.14:49
tpeopleswhich basically makes sure our requirements are always in sync with openstack14:49
tpeoples's global requirements14:50
vincentfrancoise+114:50
tpeoplesbut it looks like we'll need to move our requirements to master, not liberty14:50
tpeoplesare we OK with that?14:50
jed56what are the difference  ?14:51
jed56the version are more updated ?14:51
tpeoplesjust different versions essentially14:51
*** ahelkhou has joined #openstack-meeting-414:51
tpeoplesi can change them locally and do a smoke test and make sure nothing major is broken14:51
dtardiveltpeoples: what is the risk ? :)14:51
sballeacabot: tpeoples I'll check on the status of the etherpad on friday and submit EOD friday. ok?14:51
tpeoplesnothing really, i think we need to do it dtardivel14:51
tpeoplesso i'll move forward14:51
sballeacabot: Can you add jed56 or dtardivel  to the hands on lab?14:52
acabotsballe: submit 2 talks for the summit before friday EOD14:52
*** spzala has joined #openstack-meeting-414:52
jed56tpeoples: +214:52
acabotsballe: not clear about how many people we will have at the summit14:52
acabotany other discussion ?14:53
sballeacabot: understood. In the past various companies were only sending people ot Openstack that had a talk so this is why I have been pushing for adding people :)14:54
acabotcdupont : do you think we could add btrPlace as a new strategy in Watcher ?14:54
acabotsballe: thats a good way to do ;-)14:54
cdupontI think so14:55
sballeRackspace and HP are operating taht way14:55
sballeand I believe so is Intel14:55
cdupontfhermeni might also have an opinion on that14:55
*** avarner has joined #openstack-meeting-414:55
cdupontbut we need to translate the Nova constraints to BtrPlace constraints14:56
acabotcdupont fhermeni : would you be interested in working on this ?14:56
fhermeniacabot: it would be great but on my side, it is too soon. I am working on the scheduler spec for the moment14:56
cdupontActually in CN the next months will be very hard14:56
acabotcdupont : yes, we need to solve the constraints pb before but as btrPlace is in Java, it will take time to have it in Python14:56
*** bobh has joined #openstack-meeting-414:57
cdupontyes14:57
fhermeniacabot: I will have agenda issues as well :D. I will first make BtrPlace compatible with the spec language for fun for the moment14:57
acabotcdupont : it was a suggestion14:57
*** davidlenwell has quit IRC14:57
acabotfhermeni : ok ths14:57
*** yamamoto has quit IRC14:57
cdupontacabot: so I can work at spec level but implementation is not possible at the moment for resource reasons :(14:58
acabotcdupont : thx14:58
*** davidlenwell has joined #openstack-meeting-414:59
acabottime to end the meeting14:59
acabotthanks everyone14:59
tpeoplesbye14:59
cdupontthanks, bye!14:59
sballebye thx14:59
acabotbye14:59
acabot#endmeeting14:59
vincentfrancoisebye14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:59
openstackMeeting ended Wed Jan 13 14:59:35 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-13-14.00.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-01-13-14.00.txt14:59
*** piet has quit IRC14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-01-13-14.00.log.html14:59
*** shawnlee has quit IRC14:59
*** GheRiver1 has joined #openstack-meeting-414:59
fhermenibye15:00
*** piet has joined #openstack-meeting-415:00
*** Ng has joined #openstack-meeting-415:00
*** avarner has quit IRC15:00
jasondotstar#startmeeting vahana15:01
openstackMeeting started Wed Jan 13 15:01:05 2016 UTC and is due to finish in 60 minutes.  The chair is jasondotstar. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: vahana)"15:01
openstackThe meeting name has been set to 'vahana'15:01
jasondotstar#topic roll call15:01
*** openstack changes topic to "roll call (Meeting topic: vahana)"15:01
jasondotstaro/15:01
Ng.o/15:01
jasondotstarhowdy Ng15:01
Nghey :)15:01
jasondotstar#topic Introduction15:01
*** openstack changes topic to "Introduction (Meeting topic: vahana)"15:01
*** sridhar_ram has quit IRC15:01
jasondotstarAgain, this is a friendly reminder that the OpenStack Vahana project15:02
*** brunograz has left #openstack-meeting-415:02
jasondotstarWe're building an iOS client for OpenStack, in the form of one or more frameworks for interacting with the OS API, and *possibly* front end app15:02
jasondotstar#link https://etherpad.openstack.org/p/openstack-mobile-ios-brainstorm15:02
jasondotstarInterested parties are encouraged to join the #openstack-vahana IRC channel15:02
*** bzhou has quit IRC15:02
jasondotstarok....15:03
jasondotstar#topic Action Items from Last Meeting15:03
*** openstack changes topic to "Action Items from Last Meeting (Meeting topic: vahana)"15:03
jasondotstarNg to make contact with the UX team15:03
NgI have (only just) kicked off the process of that15:03
jasondotstarthis was carried over from last meeting. any movement this past week?15:03
jasondotstarthat's cool.15:03
*** vincentfrancoise has left #openstack-meeting-415:03
jasondotstarmovement!15:04
jasondotstar:-P15:04
Ng:)15:04
jasondotstarnext:15:04
jasondotstarjasondotstar to make progress on capturing use cases on the brainstorming etherpad15:04
jasondotstark so, I had to basically *remind* myself what we needed15:04
jasondotstarand if you remember, we were going to kick off an Operators survey15:04
jasondotstarto see if we can assess what the use cases might be15:04
jasondotstardhellmann agreed to 'support' me wrt being introduced to the user committee15:05
Ngnice15:05
jasondotstarthe folx who run the surveys15:05
jasondotstarwe spoke briefly yesterday via IRC and he just responded this am in an email.....15:06
jasondotstarwe're going to try an email to the user committee mailing list15:06
jasondotstar(im drafting it now)15:06
jasondotstarand then if that doesn't work, he'll 'pinch hit'15:06
Ng\o/15:06
NgI think that's a baseball reference?15:06
jasondotstaroh yeah15:06
jasondotstarlol15:06
jasondotstaryes, that is a baseball ref15:06
NgI am so bad at sportsball jargon ;)15:06
* jasondotstar chuckles15:07
jasondotstarcall in 'air support'?15:07
jasondotstardoes that work?15:07
jasondotstarlol15:07
Nghah, yes15:07
*** kebray has joined #openstack-meeting-415:07
jasondotstarsorry, I played CoD some over the holiday....15:07
jasondotstaranyway, we'll see how that goes15:08
jasondotstar#action jasondotstar to reach out to the user committee via the mailing list regarding the ops survey15:08
jasondotstarok..... next:15:08
jasondotstarjasondotstar to chat with -infra about public cloud api testing enviros. Report findings at the next mtg.15:08
jasondotstarso I talked to clarkb and mordred yesterday on -infra15:09
jasondotstarbasically they suggested to use trystack, and/or any other free/publicly available openstack deployment.15:09
jasondotstartrystack *does* give me API access15:09
Ngoh cool15:10
jasondotstarand I'm in the process of trying it out today.15:10
*** fhermeni has quit IRC15:10
*** kebray has quit IRC15:10
jasondotstarI've got the API token15:10
jasondotstarbut that's abt as far as I've got this am.15:10
jasondotstar#action jasondotstar to report on public api testing with trystack15:11
jasondotstarok next up:15:11
jasondotstarNg to follow up with -infra about setting up a git repository for the project15:11
Ng#link https://review.openstack.org/#/c/266549/215:12
jasondotstarwoooooot! \o/15:12
Ngwe need to get our project irc channel in order, then it should be good to go15:12
jasondotstarvery well15:12
jasondotstarwe can take care of that today if you like.15:12
*** yamamoto has joined #openstack-meeting-415:13
Ngyes please :)15:13
jasondotstarack.15:13
jasondotstarI saw that one of the reviewers mentioned applying for Big Tent15:13
jasondotstaris that something we need to look at as well?15:13
NgI'm not sure15:14
NgI mean, we dont need it to get a repo15:14
jasondotstar+115:14
jasondotstarIIUC, Big Tent is sorta the 'catch-all' place for.... well.... non core module projects?15:15
*** kebray has joined #openstack-meeting-415:15
Ngaiui, yep15:15
jasondotstarmmml15:15
jasondotstarmmmk15:15
jasondotstarnothing to worry about now then15:15
jasondotstar(unless you suggest otherwise)15:16
NgI think let's get a bit further down the road and then look at it15:16
jasondotstar#agreed Wait until the project matures prior to applying for Big Tent15:17
jasondotstarok15:17
jasondotstarlast action item:15:17
jasondotstarjasondotstar to report on documenting a vahana/devstack local test environment15:17
jasondotstarnot ready yet. progressing, but not ready for prime time.15:17
jasondotstar#action jasondotstar to report on documenting a vahana/devstack local test denvironment15:18
jasondotstarmoving that one fwd to next week's mtg15:18
jasondotstari think that's it for action items from last meeting15:19
jasondotstar#topic R&D15:19
*** openstack changes topic to "R&D (Meeting topic: vahana)"15:19
jasondotstark so for me, I'm concentrating on getting my AlamoFire/Playground setup15:19
jasondotstarto work against TryStack15:19
jasondotstarand still consuming the python-openstackclient code15:20
*** spotz_zzz is now known as spotz15:20
NgI've been fiddling around with my OSVIdentity class a bitm and reading python-openstackclient15:21
jasondotstarnothing interesting to report yet15:21
jasondotstarcool.15:21
jasondotstaralthough we're iterating through each module15:22
jasondotstarim hoping that the results of the survey15:22
jasondotstarcan give us a use case to poc15:22
jasondotstari.e. if the operators say 'i'd launch/terminate instances from a mobile device'15:23
jasondotstarthen that's a small poc we could demo15:23
Ngyeah that would be cool15:23
jasondotstarso I think we may get a clue on things to expose via our client libraries15:24
jasondotstarbased on things operators indicate are useful to see on a iOS device15:25
Ng+115:25
*** yamamoto has quit IRC15:25
jasondotstarother than that, there's not much else for me to report (yet). I'll get the ball rolling by completing the documentation15:26
NgI have nothing else to report15:26
jasondotstarand toying with trystack15:26
jasondotstarcool.15:26
jasondotstar#topic Open Discussion15:26
*** openstack changes topic to "Open Discussion (Meeting topic: vahana)"15:26
jasondotstaronly thing I have here is that I haven't heard back from the local iOS/CocoHeads meetup group.  Waiting to hear back.15:27
jasondotstarthey do think it's a worthy topic to bring to the meeting though.15:27
*** zeih has quit IRC15:27
*** zehicle has joined #openstack-meeting-415:27
jasondotstarso we'll see what happens there.15:28
*** armax has quit IRC15:28
*** MarkAtwood has joined #openstack-meeting-415:28
jasondotstarif nothing else..... we can give 30mins back15:28
Ngnothing from me15:29
jasondotstarcool15:29
jasondotstarthanks, until next week.15:29
Ngthanks!15:29
jasondotstar#endmeeting15:30
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:30
openstackMeeting ended Wed Jan 13 15:30:00 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vahana/2016/vahana.2016-01-13-15.01.html15:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vahana/2016/vahana.2016-01-13-15.01.txt15:30
openstackLog:            http://eavesdrop.openstack.org/meetings/vahana/2016/vahana.2016-01-13-15.01.log.html15:30
*** yamahata has joined #openstack-meeting-415:30
*** Ng has left #openstack-meeting-415:30
*** galstrom_zzz is now known as galstrom15:31
*** zeih has joined #openstack-meeting-415:31
*** cdupont has quit IRC15:32
*** iyamahat has joined #openstack-meeting-415:32
*** acabot_ has joined #openstack-meeting-415:34
*** FallenPegasus has joined #openstack-meeting-415:35
*** zehicle has quit IRC15:38
*** acabot_ has quit IRC15:39
*** Sukhdev has joined #openstack-meeting-415:40
*** fawadkhaliq has joined #openstack-meeting-415:40
*** mbound_ has quit IRC15:41
*** acabot_ has joined #openstack-meeting-415:41
*** avarner has joined #openstack-meeting-415:41
*** yamamoto has joined #openstack-meeting-415:44
*** harshs has joined #openstack-meeting-415:45
*** armax has joined #openstack-meeting-415:48
*** MarkAtwood has quit IRC15:51
*** AlanClark has joined #openstack-meeting-415:51
*** matrohon has quit IRC15:54
*** sridhar_ram has joined #openstack-meeting-415:56
*** yamamoto has quit IRC15:59
*** devananda has quit IRC15:59
*** gema has joined #openstack-meeting-416:00
*** leecalcote has joined #openstack-meeting-416:01
*** devananda has joined #openstack-meeting-416:02
*** bobh has quit IRC16:03
*** harshs has quit IRC16:05
*** gema has left #openstack-meeting-416:06
*** sigmavirus24_awa is now known as sigmavirus2416:07
*** salv-orl_ has joined #openstack-meeting-416:10
*** salv-orlando has quit IRC16:13
*** zehicle has joined #openstack-meeting-416:16
*** bobh has joined #openstack-meeting-416:18
*** acabot_ has quit IRC16:18
*** dims_ has joined #openstack-meeting-416:18
*** yamamoto has joined #openstack-meeting-416:18
*** dims has quit IRC16:21
*** acabot_ has joined #openstack-meeting-416:21
*** ihrachys has quit IRC16:22
*** sdake_ has joined #openstack-meeting-416:22
*** angdraug has joined #openstack-meeting-416:23
*** akwasnie has joined #openstack-meeting-416:24
*** sdake has quit IRC16:25
*** sdake_ is now known as sdake16:25
*** acabot_ has quit IRC16:28
elemoinehi sdake16:28
sdakehello :)16:29
sdakemeeting starts in 1 minute16:29
*** kproskurin has joined #openstack-meeting-416:29
*** inc0 has joined #openstack-meeting-416:29
elemoineread your email, will respond later tonight or tomorrow16:29
*** dratushnyy has joined #openstack-meeting-416:29
sdakeroger16:29
dratushnyyroger16:29
sdake#startmeeting kolla16:30
openstackMeeting started Wed Jan 13 16:30:06 2016 UTC and is due to finish in 60 minutes.  The chair is sdake. Information about MeetBot at http://wiki.debian.org/MeetBot.16:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:30
*** openstack changes topic to " (Meeting topic: kolla)"16:30
sdake#topic rollcall16:30
openstackThe meeting name has been set to 'kolla'16:30
*** openstack changes topic to "rollcall (Meeting topic: kolla)"16:30
*** yamamoto has quit IRC16:30
akwasniehi16:30
sdake\o!/ hi!!16:30
elemoineo/ hi16:30
Jeffrey4l\o/16:30
dratushnyy\?/16:30
SamYapleo/16:31
*** rhallisey has joined #openstack-meeting-416:32
rhalliseyhi16:32
inc0o/16:32
jpeelerhi16:32
sdake#topic announcements16:32
*** openstack changes topic to "announcements (Meeting topic: kolla)"16:32
*** galstrom is now known as galstrom_zzz16:33
sdake1. midcycle is february 9th, february 10th in greenville sc16:33
sdakeI will publish full wiki info today if I can - have had contractors at my hosue dealing with my reemodel so i've been distracted16:33
sdakethere will be breakfast, lunch both days16:34
sdakethere will be dinner on tuesday night16:34
*** hdaniel has quit IRC16:34
sdakeso your real only expenses should be travel and hotel16:34
sdakeif someone is on the fence bout not being able to make it because of budget, I am willing to share rooms if you can handle the snoring - just ping me later16:34
sdakealong with the share rooms, i'll pick up the full tab16:35
sdakefor the room so that just leaves airfare16:35
sdakewoud like to have a good turnout for our core reviewers16:35
sdakeany other announcements sfrom the community?16:35
sdakeoh one more16:35
sdake2. I have assked sam to act as a backup tagger in case I fall off a cliff like which happened in december16:36
sdakehe tagged milestone 116:36
sdakeeveryone give sam a round of applause please :)16:36
inc0<round of applause>16:36
* kproskurin claps16:36
* Jeffrey4l claps16:36
rhalliseyyay!16:36
* elemoine claps16:37
jpeeleryay sam16:37
dratushnyy*claps*16:37
sdakefinally 3. january 21 is our deadline for mitaka 2 - so please finish up any tasks you want to tackle :)16:37
sdake#topic midcycle planning16:37
*** openstack changes topic to "midcycle planning (Meeting topic: kolla)"16:37
sdaketimebox 10 minutes16:37
sdakelets finalize the agenda for the mitaka midcycle16:38
sdakeanyone have the link handy where we have been doing that work?16:38
sdakei had to reset chrome and lost all my cached pages16:38
elemoinehttps://etherpad.openstack.org/p/kolla-mitaka-midcycle ?16:38
sdake#link https://etherpad.openstack.org/p/kolla-mitaka-midcycle16:39
sdakeplease open and we will run until 50 after16:39
sdakeif your a new contributor, please add your name to the list of contributors16:39
sdake(to the planning)16:39
*** kebray has quit IRC16:40
rhalliseysdake, do we want to have some ordering here on importance?16:40
*** njohnston has left #openstack-meeting-416:40
sdakerhallisey i have that later in the agenda16:40
sdakeand i'll combine those16:40
rhalliseykk16:40
*** bpokorny has joined #openstack-meeting-416:42
*** dshakhray has quit IRC16:42
*** dshakhray has joined #openstack-meeting-416:43
sdakeactually rhallisey good point16:43
sdakeI'd like peoiple to vote on sessions they want - just in case time is tight16:43
sdakewe hae done this in the past - and I forgot we did, but it worked well16:43
sdakeso please add your nick followed by +1/-116:43
rhalliseysdake, let me organize it real quick16:43
sdakedont organize it16:44
sdakejust leave as is16:44
SamYaplehear that harmw. no alphabetizing!16:45
rhalliseysdake, can't really read it16:45
*** yamamoto has joined #openstack-meeting-416:45
sdakerhallisey i will sort it out after the meeting16:45
rhalliseypl16:45
rhalliseyok16:45
sdakewe only ahve 5 minutes left, i'd like to ge the evoting in16:45
sdakelook at my exampless16:45
sdake+0 is a vote as well :)16:45
*** harshs has joined #openstack-meeting-416:47
*** cdelatte has joined #openstack-meeting-416:47
*** paul-carlton2 has quit IRC16:47
sdakefolks please vote quickly - 2 minutes left16:48
sdakeok i'll send followup to the ml asking for our team to vote :)16:48
*** bradjones has quit IRC16:49
sdake1 more minute16:49
sdakeok timers up :)16:50
sdake#topic heka discussion16:50
*** openstack changes topic to "heka discussion (Meeting topic: kolla)"16:50
sdakesorry this is out of order because inc0 has to leae shortly16:50
sdakeso apparently heka get rid of rsyslog16:50
*** bradjones has joined #openstack-meeting-416:50
*** bradjones has quit IRC16:50
*** bradjones has joined #openstack-meeting-416:50
sdakewhich seems good16:50
SamYaplesdake: you are not following the agenda16:50
sdakeSamYaple i know, see abovve16:50
elemoinenot fully sure16:51
SamYapleah there you go16:51
elemoineabout removal of rsyslog16:51
inc0elemoine, you mentioned it will listen on stdout16:51
sdakeSamYaple  all good now?16:51
*** dratushnyy has quit IRC16:51
elemoineright16:51
sdakesome services don't output to sstdout16:51
SamYaplefor the record inc0 im not sold on listening on stdout for logs16:51
*** macsz has joined #openstack-meeting-416:51
SamYaplei rasied some concerns about that16:51
elemoineyeah, mariadb writes to /dev/log (syslog) for example16:51
SamYaplein the case of say neutron there is neutorn and dnsmasq logs16:52
sdakeelemoine do you have a solution in mind for that problem?16:52
SamYapleone container16:52
inc0SamYaple, right, however if we make this work (that's my requirement) it might be better than rsyslog16:52
inc0can heka support both?16:52
inc0at the same time?16:52
*** spzala has quit IRC16:52
inc0some containers stdout some /dev/log?16:52
inc0or other streams if needed?16:52
*** spzala has joined #openstack-meeting-416:53
elemoineat the moment, and given sdake's latest email, keeping rsyslog may make sense actually16:53
sdakeif heka can't capture /dev/log in some cases, it seems like a non starter16:53
inc0with rsyslog we can handle more-or-less everything. It's not ideal but it's working16:53
elemoineinc0, right and we can easily log to files as well16:53
*** lexholden has joined #openstack-meeting-416:53
elemoinewhich is a requirement as I understand16:53
sdakeya thats the other thing, we need logs to files per node16:54
inc0elemoine, file logging is actually temp solution16:54
inc0before we get centralized logging in place16:54
SamYapleinc0: no.. it was permanat16:54
SamYapleeven with central logging16:54
SamYaplelogs stay per node too16:54
sdakeinc0 i'd like to keep it for mitaka at minimum16:54
elemoinewe want both: log to local files + send logs to ES16:54
inc0ok, in any case, we want it as well before we get centralized logging16:54
sdakeelemoine  SamYaple  agree +116:54
*** prashantD has joined #openstack-meeting-416:54
SamYapleoperator side central logging is good, but local logging is required16:54
elemoineyep, agree16:54
kproskurinLocal loging will require this logs rotation and so on16:55
inc0but both heka and rsyslog does that, so I guess that's that16:55
sdakethe other requirement is multiline logs16:55
inc0what I'm interested in is logging sources16:55
SamYaplewell thats more parsing than anything sdake16:55
kproskurinAnd local logs will eat space16:55
*** leecalcote has quit IRC16:55
*** leecalcote has joined #openstack-meeting-416:55
inc0kproskurin, you can turn it off, but you should be able to have it16:55
sdakekproskurin we decided long ago we need locl node logging16:55
SamYaplekproskurin: understood. and maybe we have an option to turn it off16:55
SamYaplebut it has to be there16:55
sdakei'm good with an option16:55
sdakebut it needs to be present16:56
kproskurinOh with turn off switch I guess its ok16:56
akwasniewith my ELK patch we give user a choice rsyslog or ELK16:56
*** leecalcote has quit IRC16:56
inc0anyway, I'm -1 on having heka AND rsyslog as heka require compute node agent16:56
elemoineakwasnie, one may want both16:56
sdakeakwasnie do you disable rsyslog entirely then?16:56
inc0and I want to limit this as much a as possible16:56
*** spzala has quit IRC16:56
sdakeit sounds like we need to have more mailing list discussion16:57
SamYapleI think this is still complex. well need a working implemntation i think16:57
akwasnieno, I can have both or each of them,16:57
sdakei knwo everyone just got up in the us16:57
inc0akwasnie, you need something that will forward logs from node to ELK16:57
*** spzala has joined #openstack-meeting-416:57
sdakeso please, lets sort it out on the mailing list16:57
elemoinesdake, no, with akwasnie's path logs go to files if elk is not enabled, and they go to ES if elk is enabled16:57
sdakei think elemoine has an idea of the requirements we have16:57
elemoineyeah it's quite clear, thank you sdake for putting those requirements together16:57
sdakeare there other requirements we have which are unstated thus far?16:57
*** woodard has quit IRC16:57
akwasnieelemoine: yes,16:57
sdakeinc0 akwasnie ?16:58
sdakei dont want to wait to the midcycle to begin implementation on a poc of this work16:58
inc0I don't want 2 agents for logging on compute node16:58
inc0either or16:58
*** woodard has joined #openstack-meeting-416:58
sdakeinc0 which two agents - could you define them please16:58
elemoinesdake, I'd like to fully understand the multiline logs problems you have16:58
sdakeSamYaple can you explain thato elemoine ?16:58
inc0hega agent and rsyslog agent16:59
sdakebasiclly backtraces are multiline16:59
sdakeand rsyslog eats them i think16:59
inc0sdake, it does not now16:59
*** leecalcote has joined #openstack-meeting-416:59
inc0but it doesn't break lines16:59
sdakeoh cool you fixed that?16:59
inc0so we have rsyslog traces but ugly16:59
inc0not me, dims did16:59
SamYaplesdake: its not the logging agent that logs them thats teh problem, its the log parser that needs to PARSE them thats the issue16:59
inc0it was bug on oslo side16:59
sdakenice well thats solid then16:59
elemoinesdake, rsyslog currently replaces newline chars with a special char16:59
*** MarkAtwood has joined #openstack-meeting-416:59
sdakeelemoine so the last unstated requirement it sounds like is we dont want *both* rsyslog and heka17:00
sdakehas to be one or the other17:00
sdakeSamYaple ack on the agent parsing17:00
SamYapleclarkb did make a good point on the mailing list about replacing logstash. if we do we can't benefit from the logstash code that currently parses the openstack logs17:00
SamYapleso i think we should acknowleged that at the very least17:01
*** lexholden has quit IRC17:01
sdakeSamYaple agree i must have missed that point17:01
sdakethat sounds like another requirement for heka17:01
SamYaplewe will have to write new filters and maintain them17:01
*** ppetit has joined #openstack-meeting-417:01
SamYapleit may be worth it, but it may not. i dont know17:01
sdakeour team is big enough to handle thta SamYaple17:02
elemoinewe do have heka code for decoding openstack logs17:02
sdakeelemoine fantastic17:02
sdakeok, i'll take an action to parsse this discussio nand publish the requirements in a new thread17:02
elemoinewe've been relying on them for some time now, and we know they work well17:02
sdake#action sdake parse irc discussion and get requiremetns on the mailing list for the record17:02
SamYaplecool elemoine. i beileve you. I jsut wanted to point it out17:02
*** salv-orl_ has quit IRC17:03
sdakeok anything else on this topic?  we are running short on time ;)17:03
*** nkrinner has quit IRC17:03
*** salv-orlando has joined #openstack-meeting-417:03
elemoinelet's continue on the mailing list then17:03
akwasniefor me nothing more17:03
sdakeelemoine i'd like the spec started asap please17:03
elemoinelet's finish the current ml discussions first17:04
sdakeour specs process requires majority vote of core reviewers for approval17:04
elemoinethen I'll start working on the specs17:04
sdakeelemoine sounds good17:04
elemoineok, cool17:04
*** lexholden has joined #openstack-meeting-417:05
sdakemoving on now17:05
sdake#topic Kolla-mesos code sharing with kolla and kolla-ansible17:05
*** openstack changes topic to "Kolla-mesos code sharing with kolla and kolla-ansible (Meeting topic: kolla)"17:05
SamYapleill start this one17:05
sdakeSamYaple was this you that added to agenda?17:05
SamYapleyes17:05
SamYapleSo me and nihilifer have notice a great deal of duplicate code in kolla-mesos and (what will be) kolla-ansible17:05
SamYaplethe code has been copy-paste moved17:06
sdakeSamYaple  you have the floor ;)17:06
SamYaplewhat this has caused is things that get fixed in kolla-ansible code do not get fixed in kolla-mesos17:06
SamYaplethanks sdake17:06
SamYapleso we need to figure out a better way of code sharing so that doesnt happen17:06
*** lexholden has quit IRC17:06
sdakeshould this be a midcycle discussion topic?17:06
*** galstrom_zzz is now known as galstrom17:07
SamYaplevery possible it should be17:07
nihiliferi see at least 2 potential things to share17:07
*** woodard has quit IRC17:07
nihilifer1) major, sharing ansible modules17:07
rhalliseyerr this may be a problem we can't wait on then17:07
nihilifer2) minor, sharing vagrant17:07
*** woodard has joined #openstack-meeting-417:07
*** zehicle has quit IRC17:07
sdakejust added to the etherpad17:07
SamYaplehmm nihilifer this is more comlpicated, should we just wait for the midcycle?17:08
rhalliseyI thought this could be punted until N, but maybe not17:08
sdakefor midcycle further discussion17:08
rhalliseySamYaple, I think so17:08
SamYaplesdake: can we get an assured block of time?17:08
sdakedepends on the voting17:08
SamYaplerhallisey: i think it needs to be discussed long before N17:09
SamYapleits only getting worse17:09
* jpeeler agrees17:09
*** leecalcote has quit IRC17:09
sdakethe more votes the sessions get, moves up to tuesday in the agenda and at primier times17:09
rhalliseySamYaple, I was hoping we wouldn't need to do until N, but given what you're saying probably can't wait17:09
SamYapleif we cant get a block of time for the midcycle we should really do it now17:09
sdakei am not keen to split the repos until upgrades are done17:09
SamYaplethat requires reviews17:10
* SamYaple should make a bot17:10
sdakeok if this is something mandatory that needs discussion, I'll make time in the agenda for it17:10
sdakesounds mandatory17:10
SamYapleI believe it is17:10
SamYapleif so then we can move on right now17:10
sdakeok moving on then :)17:10
sdake#topic python-kollaclient - are we proceeding with this?17:11
*** openstack changes topic to "python-kollaclient - are we proceeding with this? (Meeting topic: kolla)"17:11
*** zeih has quit IRC17:11
*** amotoki has quit IRC17:11
sdakei am not sure if folks read my email thread related to the abandonment of the cli codebase waiting on mesos and ansible integration17:11
sdakeif you didn't, you should read it please17:11
SamYapleI added that before the ML thread when fungi asked about it17:11
SamYaplethe topic that is17:12
*** banix has joined #openstack-meeting-417:12
sdakebut in essence the maintainers of the cli don't want to commit to one cli when mesos is on the horizon17:12
sdakeso for hte time being, we are putting this work on hold17:12
sdakeunless unicorns come and implement it for us17:12
sdakei am removing it as a deliverable from our governance repository17:12
sdakethis can always be undone later17:12
fungithanks again SamYaple for bringing it up for discussion. i mostly wanted to make sure it wasn't hiding under a different name or something such that i was missing counting your contributors17:13
SamYapleappreciate that fungi17:13
sdakefungi appreciated :)17:13
sdakefungi did you see my mailing list discussion on the topic?17:13
sdakeit wasn't really a discussion more like an announcement17:14
fungisdake: yep, appreciated the details. 5 months in governance with no corresponding repo or even a patch to create it struck me as anomalous17:14
*** AlanClark has quit IRC17:14
sdakefungi it was going to go in then i had the tooth infection17:14
sdakethen mesos picked up steam and the contributors of the cli dont want to commit to it any longer17:14
fungii remember, that sounded terrible and dangerous. glad we've got you back now17:14
sdakeok then any questions or shall I move on?17:16
SamYaplemove on i think17:16
SamYaplemy questions have been answered17:16
sdake#topic priorities discussion17:16
*** openstack changes topic to "priorities discussion (Meeting topic: kolla)"17:16
sdakeso I added a midcycle session for this, please vote on it :)17:17
*** jmckind has joined #openstack-meeting-417:17
*** spzala has quit IRC17:17
sdakebut basically my #1 priority is upgrades, my #2 priority is diagnostics17:17
sdakeI wanted to poll the core reviewers for their list of priorities17:17
sdakepart of this is to help me ramp back up from my december hiatus17:17
*** spzala has joined #openstack-meeting-417:17
SamYaple#1 upgrades #2 split repo for kolla-ansible (this will also help kolla-mesos)17:18
sdakei'd like all core reviewers to respond please17:18
sdakeand in fact an ycontributors as well17:18
sdaketime box 7 inutes - so start typing :)17:18
nihilifer#1 upgrades #2 split repo17:18
rhalliseyditto SamYaple17:18
*** GheRiver1 has quit IRC17:19
jpeeler#1 upgrades, #2 split repo17:19
sdakenobody seems to care about diagnostics :)17:19
jpeelermaybe17:19
jpeeler#317:19
SamYaplei do, its just not top priorites17:19
SamYaplethats #3 for me (tied with ssl)17:20
jpeelersee17:20
*** paul-carlton2 has joined #openstack-meeting-417:20
elemoineI do care, but I'm not able to go to midcycle :)17:20
akwasniesdake: #1 upgrade, #2 diagnostics for me:)17:20
sdakeelemoine roger what is your opinion on prioirties then17:20
nihiliferditto, diagnostics is #3 for me17:20
sdakeso we have upgrades, diags, split repo, ssl17:21
elemoine#1 upgrades, #2 diagnostics & split repo17:21
sdakeany other candidates?17:21
Jeffrey4l#1 upgrade #swift #diagnostics :) ( care the produce issue more.)17:21
SamYaplewhen docker 1.10 lands we can do neutron thin containers17:21
sdakeJeffrey4l what do you mean swift?17:21
SamYaplethats kinda a priority17:21
Jeffrey4ls/produce/product/17:21
Jeffrey4lyep.17:21
sdakeSamYaple cool17:21
elemoineSamYaple, what Docker feature do you want to leverage?17:22
*** spzala has quit IRC17:22
SamYapleelemoine: private/shared mount namespaces17:22
*** jmckind_ has joined #openstack-meeting-417:22
sdakeJeffrey4l what part of swift doessn't work for you now with kolla?17:22
SamYapleit merged in 1.7-rc1 and was removed in 1.7-rc3. itttsss baaaaccckk17:23
elemoineSamYaple, thanks, I need to look into that17:23
sdakenice ;)17:23
*** GheRiver1 has joined #openstack-meeting-417:23
sdakeya thin containers for neutron would be win - need to sort out how to get that implemented17:23
Jeffrey4lsdake, I haven't tested it detailly. But i am care about it.17:23
sdakeany other candidates for priorities?17:23
sdakeJeffrey4l it worked when I tested it17:24
SamYapleelemoine: https://github.com/docker/docker/pull/1703417:24
elemoineand https://github.com/docker/docker/issues/1008817:24
sdakeok sounds like we are all pretty much on same page17:24
Jeffrey4lsdake, so why it is in the topics.17:24
sdakeso I'm going to move on17:24
sdakeJeffrey4l  for autobuilding rings17:24
sdakei think that can wait until N17:25
Jeffrey4lroger17:25
*** jmckind__ has joined #openstack-meeting-417:25
sdake#topic open discussion17:25
*** openstack changes topic to "open discussion (Meeting topic: kolla)"17:25
sdake5 minutes17:25
*** krtaylor has quit IRC17:25
sdakesorry so little time for open discussion - we had a packed agenda17:25
*** jmckind has quit IRC17:25
sdakeanyone want the floor?17:26
*** krtaylor has joined #openstack-meeting-417:26
ajafogot short question - maybe it'll need to discuss -  does we care about situation with rebuild only one container with for example added some packages (e.g. someone want to have sth additional installed in some docker container), because if yes it can broke dependencies in some situations17:26
*** bobh has quit IRC17:26
sdakewe can rebuild just one container with our current build tools ajafo17:27
ajafoI know but17:27
ajafolets imagine that someone want only rebuild nova_compute container with add some package in dockerfile, in the meantime were some updates in repository distribution repository, now if he is in ubuntu he get 404 no such package, and he know that he need to rebuild everything, but if he use centos then this one container will update own dependencies and install packages in other version than are in other containers, so we care about it or no? Is the rule17:27
SamYapleajafo: we do that though17:28
SamYapleeven now17:28
*** jmckind_ has quit IRC17:28
sdakewe rebuild all dependent cotnainers17:28
sdakethat is required for correct operation17:28
sdakeso that scenario yo ujust laid out, I am pretty sure can't happen17:28
ajafoit just happend17:29
ajafowith ubuntu17:29
sdakeok, ajafo please post a discussion on the mailing list17:29
*** javeriak_ has quit IRC17:29
sdakewe are out o time :)17:29
elemoinemaybe another subject for the mailing list17:29
ajafook17:29
sdakethanks for your time folks :)17:29
sdakeand lets rock greenville :)17:29
sdake#endmeeting17:29
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:29
openstackMeeting ended Wed Jan 13 17:29:53 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-13-16.30.html17:29
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-01-13-16.30.txt17:29
elemoinethx everyone (for the heka discussions on the ml as well!)17:30
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-01-13-16.30.log.html17:30
*** pc_m has joined #openstack-meeting-417:30
*** rhallisey has left #openstack-meeting-417:30
dougwigfloating this today... kevin isn't here yet, and henry is in the air.17:31
pc_mhi17:31
*** Swami has quit IRC17:31
dougwigpc_m: hiya17:32
dougwigpc_m: at lbaas midcycle today.  do you have a burning issue?17:32
*** iurygregory has left #openstack-meeting-417:32
*** fesp has joined #openstack-meeting-417:32
pc_mI have a bunch of questions posted in the open discussion section.17:32
*** bobh has joined #openstack-meeting-417:33
pc_mMostly, need reviews, and need to know what else I can work on, as I have some time available.17:33
dougwig#startmeeting networking_lib17:34
openstackMeeting started Wed Jan 13 17:34:21 2016 UTC and is due to finish in 60 minutes.  The chair is dougwig. Information about MeetBot at http://wiki.debian.org/MeetBot.17:34
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:34
*** openstack changes topic to " (Meeting topic: networking_lib)"17:34
openstackThe meeting name has been set to 'networking_lib'17:34
dougwig#topic Open discussion17:34
*** openstack changes topic to "Open discussion (Meeting topic: networking_lib)"17:34
dougwig"Would like to discuss how we can mark the status of modules in the library for users."17:34
*** yamamoto has quit IRC17:34
*** fesp has quit IRC17:34
dougwigcan you explain what you mean here?17:34
pc_mHow we can let developers know that some functionality is available for use.17:35
pc_mFor example, callbacks, we named the dir _callbacks.17:35
*** galstrom is now known as galstrom_zzz17:35
dougwigi'd like master to remain publishable to pypi at any time, so i don't want stuff in progress to not have an _.  IMO.17:35
pc_mWondering what the process is to transition something from work in progress to ready.17:36
*** prashantD has quit IRC17:36
*** kebray has joined #openstack-meeting-417:36
dougwiga review to do a git rename on a function or module should be all that's needed to make it ready to export.17:36
pc_mok. So for validators/convertors, add in a _ for the directory.17:36
pc_mconverters17:37
*** prashantD has joined #openstack-meeting-417:37
dougwigif you need to iterate on it, yes.17:37
*** ahelkhou has quit IRC17:37
pc_mdougwig: OK. I don't think that needs to be iterated on. Thought, with Neutron activity, we need to update it soon.17:38
dougwigwe'll have some lag and catch-up, just the nature of the beast during the transition.17:38
pc_myup.17:38
pc_mSecond item is upstreamed. Thanks for reviewing.17:38
pc_mThird is the validators. Needs review.17:39
dougwigok, i'll add it to my list for today.17:39
pc_mWondering how we want to apply that to neutron.17:39
pc_mDo we want to push a commit on top of 242219 that uses this capability in neutron?17:40
pc_mditto with others, like the callback mechanism?17:40
dougwigpc_m: yes, exactly that.17:40
pc_mOK will do that for the validators/converters.17:41
dougwigok17:41
pc_m#action pc_m to apply validators/converters to 242219 in neutron17:41
dougwigon the arg question, i'd suggest pinging kevin/henry directly, as they have opinions.17:41
pc_mFor the callbacks, I did the following - https://review.openstack.org/#/c/265997/17:42
pc_mOK. I'll ask him to look at ^^^17:42
dougwigsaw that; let's get henry and kevin to comment.17:43
pc_mRoger that17:43
dougwignext item?17:43
dougwig(folks here are about to head to lunch, so i'm in sprint mode.)  :)17:43
pc_mOn 242219, it's failing a few tests, do you know what is up there? I think you expected it?17:44
pc_munderstood.17:44
dougwigno, i'm not sure why. i'm guessing i'm missing a helper hook to pull in the lib properly. do you want to take a peek?  or i'll look soon.17:44
pc_mI'll try to look.17:45
dougwigin terms of what needs looking at, i'd suggest taking a peek at the aas unit tests, and how they currently rely on some neutron stuff.  which parts should be dup'ed into the repos, which parts are useful parts of the lib?17:45
pc_mIf there are additional neutron-lib items that I can look at, let me know. I have time this week, and some next week (On PTO a few days).17:45
pc_m#action pc_m to try to see what is causing 242219 test failures.17:46
dougwigok, did you see the note about the unit test dependencies?17:46
dougwigfirst step is an analysis of what to move or dup.17:46
pc_m#action pc_m to ping kevinbenton and HenryG on my commit for callbacks17:46
dougwigthen move/change/dup/whatnot.17:46
pc_mno I didn't see that note.17:47
*** macsz has quit IRC17:47
*** Sukhdev has quit IRC17:47
pc_mWhere is this note at?17:47
*** kebray has quit IRC17:47
dougwig11:45am: "in terms of what needs looking at, i'd suggest taking a peek at the aas unit tests, and how they currently rely on some neutron stuff.  which parts should be dup'ed into the repos, which parts are useful parts of the lib?"17:47
dougwigany other items?17:48
pc_mno that's it.17:48
*** kproskurin has quit IRC17:49
pc_mThanks!17:49
dougwigcool.  i'm apparently about to be escorted to a crappy burrito. i can't wait.17:49
pc_mEnjoy lunch!17:49
dougwigi'll be on irc this afternoon.  cool, later!17:49
pc_m:)17:49
dougwig#endmeeting17:49
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:49
openstackMeeting ended Wed Jan 13 17:49:18 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_lib/2016/networking_lib.2016-01-13-17.34.html17:49
pc_mbye17:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_lib/2016/networking_lib.2016-01-13-17.34.txt17:49
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_lib/2016/networking_lib.2016-01-13-17.34.log.html17:49
*** pc_m has left #openstack-meeting-417:49
*** paul-carlton2 has quit IRC17:50
*** paul-carlton2 has joined #openstack-meeting-417:51
*** javeriak has joined #openstack-meeting-417:51
*** bobh_ has joined #openstack-meeting-417:51
*** yamamoto has joined #openstack-meeting-417:53
*** sridhar_ram has quit IRC17:54
*** bobh has quit IRC17:54
*** kebray has joined #openstack-meeting-417:57
*** bobh has joined #openstack-meeting-417:58
*** yamamoto has quit IRC17:58
*** bobh_ has quit IRC18:01
*** akwasnie has quit IRC18:03
*** Swami has joined #openstack-meeting-418:05
*** jmckind has joined #openstack-meeting-418:06
*** ppetit has quit IRC18:07
*** yingjun has quit IRC18:08
*** jed56 has quit IRC18:08
*** chigang has quit IRC18:08
*** dtardivel has quit IRC18:08
*** junjie has quit IRC18:08
*** briancurtin has quit IRC18:08
*** dougwig has quit IRC18:08
*** raofei has quit IRC18:08
*** xgerman has quit IRC18:08
*** elemoine_ has quit IRC18:08
*** carl_baldwin has quit IRC18:08
*** skath_ has quit IRC18:08
*** patrickeast has quit IRC18:08
*** meteorfox has quit IRC18:08
*** sweston has quit IRC18:08
*** kexiaodong has quit IRC18:08
*** nick-ma has quit IRC18:08
*** sballe has quit IRC18:08
*** ashtokolov has quit IRC18:08
*** britthouser has quit IRC18:08
*** tpeoples has quit IRC18:08
*** j^2 has quit IRC18:08
*** serverascode has quit IRC18:08
*** aglarendil has quit IRC18:08
*** zhiyan has quit IRC18:08
*** leo_wang has quit IRC18:08
*** ChrisPriceAB has quit IRC18:08
*** masteinhauser has quit IRC18:08
*** jmckind__ has quit IRC18:08
*** jmckind_ has joined #openstack-meeting-418:09
*** j^2 has joined #openstack-meeting-418:10
*** jmckind has quit IRC18:12
*** serverascode has joined #openstack-meeting-418:15
*** kebray has quit IRC18:15
*** ChrisPriceAB has joined #openstack-meeting-418:16
*** sweston has joined #openstack-meeting-418:16
*** sridhar_ram has joined #openstack-meeting-418:16
*** bobh has quit IRC18:17
*** kebray has joined #openstack-meeting-418:17
*** leo_wang has joined #openstack-meeting-418:17
*** chigang has joined #openstack-meeting-418:19
*** meteorfox has joined #openstack-meeting-418:20
*** piet has quit IRC18:20
*** carl_baldwin has joined #openstack-meeting-418:21
*** sballe has joined #openstack-meeting-418:21
*** patrickeast has joined #openstack-meeting-418:23
*** skath_ has joined #openstack-meeting-418:23
*** zhiyan has joined #openstack-meeting-418:24
*** tpeoples has joined #openstack-meeting-418:24
*** zehicle has joined #openstack-meeting-418:24
*** Jeffrey4l has quit IRC18:25
*** xgerman has joined #openstack-meeting-418:25
*** aglarendil has joined #openstack-meeting-418:25
*** dougwig has joined #openstack-meeting-418:25
*** briancurtin has joined #openstack-meeting-418:25
*** kexiaodong has joined #openstack-meeting-418:26
*** raofei has joined #openstack-meeting-418:26
*** masteinhauser has joined #openstack-meeting-418:26
*** degorenko is now known as _degorenko|afk18:27
*** ashtokolov has joined #openstack-meeting-418:27
*** rlpple has joined #openstack-meeting-418:27
*** bobh has joined #openstack-meeting-418:28
*** paul-carlton2 has quit IRC18:28
*** dtardivel has joined #openstack-meeting-418:29
*** junjie has joined #openstack-meeting-418:29
*** britthouser has joined #openstack-meeting-418:29
*** javeriak_ has joined #openstack-meeting-418:29
*** jed56 has joined #openstack-meeting-418:29
*** dims_ has quit IRC18:30
*** mgagne has quit IRC18:30
*** elemoine_ has joined #openstack-meeting-418:30
*** mgagne has joined #openstack-meeting-418:31
*** javeriak has quit IRC18:31
*** mgagne is now known as Guest8280318:31
*** dims has joined #openstack-meeting-418:32
*** nick-ma has joined #openstack-meeting-418:32
*** yingjun has joined #openstack-meeting-418:32
*** Guest82803 is now known as mgagne18:32
*** mgagne has quit IRC18:33
*** mgagne has joined #openstack-meeting-418:33
*** ahelkhou has joined #openstack-meeting-418:33
*** bobh has quit IRC18:33
*** bobh has joined #openstack-meeting-418:34
*** sridhar_ram has quit IRC18:35
*** sridhar_ram has joined #openstack-meeting-418:35
*** piet has joined #openstack-meeting-418:35
*** yamahata has quit IRC18:35
*** iyamahat has quit IRC18:36
*** bobh has quit IRC18:39
*** lexholden has joined #openstack-meeting-418:42
*** ig0r_ has joined #openstack-meeting-418:43
*** rlpple has quit IRC18:45
*** bharathm has joined #openstack-meeting-418:45
*** lexholde_ has joined #openstack-meeting-418:47
*** bobh has joined #openstack-meeting-418:48
*** javeriak has joined #openstack-meeting-418:49
*** sridhar_ram1 has joined #openstack-meeting-418:50
*** simon-AS5591 has joined #openstack-meeting-418:50
*** lexholden has quit IRC18:50
*** javeriak_ has quit IRC18:51
*** s3wong has joined #openstack-meeting-418:51
*** kebray has quit IRC18:52
*** mclaren has quit IRC18:52
*** sridhar_ram has quit IRC18:54
*** simon-AS5591 has quit IRC18:56
*** iyamahat has joined #openstack-meeting-418:57
*** jamespd has joined #openstack-meeting-418:57
*** lexholden has joined #openstack-meeting-418:59
j^2#startmeeting operators_ops_tools_monitoring19:00
openstackMeeting started Wed Jan 13 19:00:02 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
*** simon-AS559 has joined #openstack-meeting-419:00
j^2#topic rollcall19:00
*** openstack changes topic to "rollcall (Meeting topic: operators_ops_tools_monitoring)"19:00
j^2hey everyone!19:00
raginbajino/19:00
raginbajinHey there.19:00
j^2like normal i’ll give everyone ~5 mins to trickle in19:00
*** yamahata has joined #openstack-meeting-419:01
* jamespd waves.19:01
j^2#link https://etherpad.openstack.org/p/osops-irc-meeting-2016011319:01
j^2that is the agenda ^^19:01
*** lexholde_ has quit IRC19:03
j^2i take the responsibility for not sending out the reminder email, my bad :(19:03
*** balajin has joined #openstack-meeting-419:03
*** lexholde_ has joined #openstack-meeting-419:04
balajinhello19:04
j^2hi!19:04
j^2going to officially start in about 2 mins19:04
balajinokay19:04
j^2#topic Talk about releases for repos other than tools-contrib and tools-generic19:05
*** openstack changes topic to "Talk about releases for repos other than tools-contrib and tools-generic (Meeting topic: operators_ops_tools_monitoring)"19:05
j^2we punted on this last time19:05
*** klindgren has joined #openstack-meeting-419:05
j^2has anyone else come up with any thoughts or ideas about this?19:06
j^2?19:07
*** lexholden has quit IRC19:07
*** lexhold__ has joined #openstack-meeting-419:07
* jamespd didn't catch the last meeting. was there a particular point of contention?19:07
*** PaulCzar has joined #openstack-meeting-419:07
j^2jamespd: creating releases for the different repos19:07
j^2there’s a plus side to it, and a few negitives19:07
*** dtardivel has quit IRC19:07
jamespdby creating releases are you talking about tagging commits or packaging?19:08
j^2we state in the wiki we won’t but EmilienM was asking for us to19:08
j^2i think both19:08
j^2#link https://wiki.openstack.org/wiki/Osops19:08
j^2we state: We don't plan on having releases, but we do plan on collecting useful resources for anything ranging from Junior to Senior level administrators.19:08
*** galstrom_zzz is now known as galstrom19:08
j^2there is a lot of overhead with creating releases and getting in the pipelines, and i lean towards saying our community isn’t large enough to have that level of overhead19:09
j^2it’s a nice to have when we grow, but hell…4? people are here right now19:09
PaulCzarIdon't really see any value in either releases or packages19:09
*** bobh has quit IRC19:09
raginbajinI have to agree. That is what I immediately think about when it comes to managing by release19:09
jamespdYeah... I agree about that at this point.19:10
PaulCzarunless its for a specific tool inside osops19:10
raginbajinespecially if there are code changes and back porting, etc19:10
PaulCzargive our ops focus, many of the tools will be written for older releases of openstack19:10
j^2yep19:10
*** lexholde_ has quit IRC19:10
balajinso far we have been seeing primarily scripts19:11
j^2so with this input i’m getting that we _aren’t_ going to support creating releases19:11
balajincan we have it loock for the versions in the script or have it called out there19:11
balajinwhen we are building tools which needs interop, we can evaluate the need for releases19:12
balajinmy 2cents19:12
raginbajinI think that's a great idea once we get more continous commits.19:12
j^2raginbajin: agreed19:12
balajinprimarily given the amount of people involved and the effort it is needed for the release19:12
raginbajinI think we are fortunate to get what we have.19:12
jamespdraginbajin: agreed19:12
balajinraginbajin: it is only the begining19:12
j^2balajin: that’s true, but we still need to get involvement19:13
j^2it’s not   growing at a constant rate by any standard; we built it…but the aren’t coming19:13
*** lexholden has joined #openstack-meeting-419:13
raginbajinI think it goes back to the work load to do this at this point in time.   I think it's a great idea, just not at this junction19:13
jamespd+!19:14
jamespd+119:14
j^2raginbajin: works for me19:14
j^2anything else or continue on?19:15
j^2#topic Talk about osops-coda19:15
*** openstack changes topic to "Talk about osops-coda (Meeting topic: operators_ops_tools_monitoring)"19:15
j^2we have another official osops project:19:15
j^2#link https://github.com/openstack/osops-coda19:16
*** bobh has joined #openstack-meeting-419:16
j^2i just wanted to make sure everyone saw it and we are slowly growing the namespace19:16
*** lexhold__ has quit IRC19:16
raginbajinI think it's great.19:16
j^2this one specifically we haven’t gotten gates in yet, but that’s still slowly happening19:16
*** lexholden has quit IRC19:17
PaulCzarinteresting.  would this be useful for say cleaning up after rally runs ?19:17
j^2PaulCzar: that’s an interesting use case19:17
balajinnice19:17
j^2i could see a great opportunity there come to think of it19:17
j^2if y’all take some time to check it out that would be awesome19:18
PaulCzarI could totally see something like coda moving towards release/packaging19:18
j^2PaulCzar: yep, that’s why it’s in it’s own repo19:19
raginbajinPaulCzar: +119:19
*** javeriak_ has joined #openstack-meeting-419:19
j^2the previous topic was about tools-generic or tools-contrib19:19
j^2which causes…challenges19:19
raginbajinWill the HPE team manage the commits, etc19:20
*** javeriak has quit IRC19:20
j^2raginbajin: nope, they gave it to us to run with it after they get the gates in19:20
j^2they wanted the exposure to our community because they realized that if they spun up their own project no one would ever look at it19:21
raginbajinahh.  Do we fear that since none of us really work on Coda that it will eventually go stale or we can't keep up with any blueprints or bugs19:21
jamespd^^ I worry about this.19:22
*** spzala has joined #openstack-meeting-419:22
j^2yeah that’s a challenge, it’s something that we’ll have to see happen et al. just the exposure alone is the most important part19:22
PaulCzartotally ...  is this repo "upstream" for the HPE team ... or do they work on their own repo and push up to it ?19:22
j^2neither, the project is dead at HPE19:22
PaulCzarahhh19:23
PaulCzarglhf ?19:23
jamespdheh19:23
j^2they wanted to give it to OS as something that we could use if we wanted to19:23
PaulCzarwas there talk about it becoming part of horizon ?19:23
j^2PaulCzar: in essence yeah.19:23
j^2that too19:23
j^2this is a place where we could if we see the use cases19:24
j^2we just need to see if the project takes off19:24
j^2ok, we have a couple more things to go through before we get to new business19:25
j^2#topic notes4chairs19:25
*** openstack changes topic to "notes4chairs (Meeting topic: operators_ops_tools_monitoring)"19:25
j^2#link https://wiki.openstack.org/wiki/OSOpsNotes4Chairs19:25
*** piet has quit IRC19:26
j^2I created this wiki page so we can start helping out Chairs for this meeting19:26
j^2I don’t want to be the chair forever, and i hope someone else will be willing to take it and run with it19:26
j^2we can take it out of this meeting and talk about a way to get volunteers to step up19:26
*** Sukhdev has joined #openstack-meeting-419:27
j^2any thoughts or questions? going to wait for 3 mins before moving on…..19:27
raginbajinBut j^2 you've done a great job. why would you not do this forever? You are much better than me..19:27
j^2raginbajin: ha!19:27
balajin+119:27
*** rockyg has joined #openstack-meeting-419:27
*** piet has joined #openstack-meeting-419:28
PaulCzarI will add,while projects are in their infancy it's pretty important to have a strong and consistent leader19:28
balajinunless not a big burden for you j^2, i would like you to continue until we gain momentum19:28
PaulCzarwhich j^2 fits the bill19:28
raginbajinSee even balajin thinks you are better than me.. Even though my last name is almost his username..19:28
raginbajin:)19:28
j^2raginbajin, PaulCzar, balajin: wow, thanks, ok, i’ll continue on, i had no idea I was worried that i was playing too much of a dictator19:28
balajinraginbajin: sorrythat came out of context19:29
balajinit is for j^2 doing a good job and asking to continue19:29
j^2:D19:29
j^2ok, cool, thanks guys19:29
balajinsorry, no inner readings please :)19:29
j^2#topic Waiting on so we can add the bashte jobs to tools generic19:30
*** openstack changes topic to "Waiting on so we can add the bashte jobs to tools generic (Meeting topic: operators_ops_tools_monitoring)"19:30
j^2so we’ve added bashte jobs to tools-generic as a gate19:30
*** sridhar_ram1 is now known as sridhar_ram19:30
j^2#link https://review.openstack.org/#/c/229031/19:30
j^2#link -> https://review.openstack.org/#/c/229043/19:30
*** fawadkhaliq has quit IRC19:30
rockyghey, sorry Im late..19:30
j^2which is what we are expecting19:30
j^2i need to add the pep8 to tools-generic also19:30
j^2unless someone can take that action item19:31
j^2http://www.youtube.com/watch?v=f4zyjLyBp6419:31
j^2it’s funnier if you get the title after the fact19:31
* jamespd giggles19:32
j^2heh, ok, so i’ll take getting pep8 in19:32
j^2ok, new businees19:32
j^2business19:32
*** bobh has quit IRC19:33
j^2#topic paulcz: talk about moving the terriform tooling to it's own repo19:33
*** openstack changes topic to "paulcz: talk about moving the terriform tooling to it's own repo (Meeting topic: operators_ops_tools_monitoring)"19:33
j^2PaulCzar: make your case :D19:33
PaulCzarI don't feel too strongly about it ...  but I think it might make sense to have an official terraform repo19:33
rockygWe're getting enough repos, maybe we should go for our own tree?  like openstack-ops?19:34
rockygI bet infra would be up for it.  And they're the ones who maintain this...19:34
j^2rockyg: that makes sense, but at the same time we need more involvement before we “break away” or whatever19:35
j^2as a reminder, the ultimate goal of this project is to get Operators an “easy way” to get ATC19:35
PaulCzarwe should probably get more participation before getting it its own repo tho19:35
rockygI think we can up participation by socializing at the midcycle.  Any of you gonna be ther?19:35
j^2PaulCzar: agreed19:35
PaulCzarATC is an interestingpoint19:35
j^2rockyg: couldn’t get the funds to make it happen. England was too far :(19:36
PaulCzarI don't get a lot of time to contribute upstream because I'm always fighting the tire fire that is operating openstack19:36
rockygFull agreement.  But infra  repos=ATC (and defcore doesn't)19:36
PaulCzarand not getting ATC for doing this ...   makes me less inclined to do it19:36
PaulCzarwhen I could work elsewhere upstream and get ATC19:36
PaulCzarROI and all that19:36
rockygCan we put together an etherpad I can socialize at the midcycle?  I'll be there.19:37
j^2yep, we need involvement and a “group” of people before we can ask to get approved to get ATC. It was/is a chicken and egg problem19:37
rockygAlso, on folks running for board, JJ and I are not the only ones who want ATC for Ops participants.... Just so you know where to put your votes;-019:37
j^2ha! well said rockyg19:38
rockygAnd, yeah.  The TC holding the power is kinda difficult.19:38
rockygBut FYI, TC is looking to update the OpenStack mission to include Ops/User community as part of mission statement19:39
balajini recall j^2 mentioning something about ops getting ATC19:39
balajinand that was the primary reason we were going for osops under big tent19:39
balajinam i missing someting19:39
rockygYeah.  Lots of user community oriented folks are pushing.19:40
j^2balajin: yep :D that was the ultimate goal19:40
balajinor was it for the openstack-chef stuff19:40
rockygNope.  Ops code contributions should count.19:40
j^2balajin: that’s true, openstack-chef you do already19:40
*** piet has quit IRC19:40
balajineveryone need to realize that ops support is as critical as code19:40
j^2balajin: yep, that’s more true then most anything19:41
raginbajinagreed19:41
rockyg+1000 and that the projects are writing code for ops and apps dev, not themselves19:41
j^2we kinda went off topic here19:42
j^2is there any objection to moving PaulCzar ’s changes to it’s own repo?19:42
rockygSpeaking of which, fYI, if you're not aware, I'm the person puushing log improvements, but I've realized we have to fix config options global, and locations, etc to all be talking about the same thing19:42
rockyg++ to new repo19:43
j^2cool, i’ll make that happen asap19:43
j^2last topic then open floor19:44
j^2#topic balajin: Fixing the ical to reflect correct dates (it shows up on my calendar every week)19:44
*** openstack changes topic to "balajin: Fixing the ical to reflect correct dates (it shows up on my calendar every week) (Meeting topic: operators_ops_tools_monitoring)"19:44
balajinyah, just added that19:44
j^2yep, that annoys the hell out of me too19:44
balajinthere were several folks in this irc last week19:44
balajinincluding  me19:44
rockygand me...19:44
balajin:)19:44
j^2I’ve been posted on the mailing list pretty regularly ;)19:44
rockygand I keep getting the time wrong :-(19:44
j^2ok, i’ll take the item to clean that up19:45
j^2(i’m starting to think this is a chance for y’all just to point out where I’ve fucked up or missed something)19:45
j^2:P19:45
j^2anyway, i’ll make it happen :D19:45
rockygWell, in that case.....19:45
j^2#topic open floor19:45
*** openstack changes topic to "open floor (Meeting topic: operators_ops_tools_monitoring)"19:45
j^2ok, so selfishly, if y’all haven’t voted yet, please consider me as a candidate :D19:46
j^2JJ Asghar19:46
rockygYour doing great and thanks for your hard work and I'm voting for you....and me....and Stephano19:46
j^2I’d love to continue this work and a macro level; and i think i can :D19:46
*** piet has joined #openstack-meeting-419:46
j^2rockyg: +1+19:46
balajinj^2: i have done my bit for you19:47
rockygAnd please consider me, too.  I think JJ and I could make a great team ;-019:47
j^2:D19:47
*** macsz has joined #openstack-meeting-419:47
* jamespd makes notes19:47
j^2does this image make sense?19:48
j^2https://wiki.openstack.org/w/images/5/5a/Osops-tools-process.png19:48
rockygGuys, I'm gonna try to put together a spreadsheet of all the config opts out there, what the defaults are, where they get set/reset/changed, etc.  If I can get it together before the midcycle, I'd love you guys to edit/comment19:48
rockygItll be a google sheet19:48
balajinok19:49
jamespdj^2: yeah, I like the image.19:49
j^2jamespd: :D19:49
rockygNova is making there stuff more consistent, so I think we can get global configs in N.  and I like the image, too.  Can you merge that in as a readme image (as opposed to readme.rst)?19:50
j^2rockyg: not sure tbh19:50
j^2getting that image up there was a lot harder then it should have been19:51
rockygThe file would just a binary instead of text.  It *should* work, but that doesn't mean it *will*19:51
rockygCan't do diffs across versions, but....don't really need that.19:51
j^2time check 8 mins19:52
j^2anyone who hasn’t spoken up, is there anything you’d like to talk about?19:52
rockygetherpad for what you want me to report to midcycle...19:52
rockygj^2, could you put something together for me?19:53
PaulCzarrockyg: I'll likely be at midcycle as well19:53
j^2rockyg: yeah i’m not 100% sure on this tbh.  what’s an email addy i can talk to you off line?19:53
rockygGreat! and if we have a start of etherpad, we can discuss at next meeting.  rockyg at gmail dot com19:54
j^2kk, will do19:54
rockygkewl!19:54
rockygI just try to juggle too many tasks to make things better....tend to drop/forget them19:54
j^2cool, anything else?19:55
j^2awesome, thanks everyone, i’ll put notes and all together19:56
*** davidlenwell has quit IRC19:57
rockygDoing a great job j^219:57
jamespdthanks j^2.19:57
j^2and send something to the the ML probably tomorrow19:57
j^2#endmeeting19:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:57
openstackMeeting ended Wed Jan 13 19:57:23 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/operators_ops_tools_monitoring/2016/operators_ops_tools_monitoring.2016-01-13-19.00.html19:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/operators_ops_tools_monitoring/2016/operators_ops_tools_monitoring.2016-01-13-19.00.txt19:57
openstackLog:            http://eavesdrop.openstack.org/meetings/operators_ops_tools_monitoring/2016/operators_ops_tools_monitoring.2016-01-13-19.00.log.html19:57
balajinthanks everyone19:57
*** PaulCzar has left #openstack-meeting-419:57
balajinhave a great day19:57
*** balajin has left #openstack-meeting-419:57
*** sridhar_ram has quit IRC19:58
*** davidlenwell has joined #openstack-meeting-419:58
*** avarner has quit IRC19:59
*** avarner has joined #openstack-meeting-419:59
*** jmckind has joined #openstack-meeting-419:59
*** baoli_ has quit IRC20:00
*** klamath_ has joined #openstack-meeting-420:00
*** klamath has quit IRC20:01
*** jmckind_ has quit IRC20:02
*** bobh has joined #openstack-meeting-420:03
*** jmckind_ has joined #openstack-meeting-420:03
*** bharathm has quit IRC20:04
*** stanchan has joined #openstack-meeting-420:05
*** kproskurin has joined #openstack-meeting-420:05
*** jmckind has quit IRC20:06
*** macsz has quit IRC20:09
*** bobh has quit IRC20:14
*** dims has quit IRC20:18
*** dims has joined #openstack-meeting-420:18
*** bobh has joined #openstack-meeting-420:19
*** lakshmiS has joined #openstack-meeting-420:20
*** macsz has joined #openstack-meeting-420:21
*** kebray has joined #openstack-meeting-420:21
*** Sukhdev has quit IRC20:26
*** jamespd has left #openstack-meeting-420:27
*** bharathm has joined #openstack-meeting-420:31
*** markmcclain has joined #openstack-meeting-420:38
*** jmckind has joined #openstack-meeting-420:45
*** jmckind_ has quit IRC20:46
*** sridhar_ram has joined #openstack-meeting-420:47
*** simon-AS559 has left #openstack-meeting-420:53
*** zehicle has quit IRC20:55
*** belmoreira has joined #openstack-meeting-420:56
*** armax has quit IRC20:56
*** avarner has quit IRC20:57
*** baoli has joined #openstack-meeting-420:59
*** jmckind_ has joined #openstack-meeting-420:59
*** avarner has joined #openstack-meeting-421:00
*** jmckind has quit IRC21:01
*** ekarlso has quit IRC21:01
*** ekarlso has joined #openstack-meeting-421:01
*** rockyg has quit IRC21:03
*** lexholden has joined #openstack-meeting-421:04
rbradforIs there a Logging WG meeting today?21:04
*** lexholde_ has joined #openstack-meeting-421:05
*** rockyg has joined #openstack-meeting-421:07
rockyghey.  anybody here for logging?21:07
*** lexholden has quit IRC21:09
*** baoli has quit IRC21:09
*** baoli has joined #openstack-meeting-421:10
*** spzala has quit IRC21:11
*** zehicle has joined #openstack-meeting-421:11
*** spzala has joined #openstack-meeting-421:11
rbradforyes21:13
*** ig0r_ has quit IRC21:14
dhellmannrockyg: o/21:14
rockygkewl21:15
rockyg#startmeeting log_wg21:15
openstackMeeting started Wed Jan 13 21:15:17 2016 UTC and is due to finish in 60 minutes.  The chair is rockyg. Information about MeetBot at http://wiki.debian.org/MeetBot.21:15
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:15
*** openstack changes topic to " (Meeting topic: log_wg)"21:15
openstackThe meeting name has been set to 'log_wg'21:15
rockyg#topic Open Discussion21:15
*** openstack changes topic to "Open Discussion (Meeting topic: log_wg)"21:15
rbradforo/21:15
rockygdhellmann, do you have something?21:16
rockygor rbradfor ?21:16
SamYapleo/21:16
dhellmannrockyg : nothing new, just finally making it to the meeting again to catch up :-)21:16
rbradforI have some updates.21:16
rockygOooh!  SamYaple , too.21:16
*** spzala has quit IRC21:16
rockygSo, glad dhellmann  could make it as I'd like to fly something by you.21:17
rockygBut lets start with updates!21:17
rockyg#topic Update from rbradfor21:17
*** openstack changes topic to "Update from rbradfor (Meeting topic: log_wg)"21:17
rbradforI've got several documented examples for various oslo projects, starting with oslo.log and https://review.openstack.org/#/c/264977/21:17
rbradfor#link http://docs.openstack.org/developer/oslo.log/usage.html21:17
rbradforI'm working on next iteration that provides Context examples and usage, and then varying format strings valid parameters.21:18
rbradforI also have several patches for deprecated logging options, to get them removed, and unclutter the docs a bit.21:19
rbradforand just submitted a patch to correctly generated deprecated documentation of options, https://review.openstack.org/#/c/267151/21:19
rockygExcellent!21:19
rockygApps developers will be so happy21:20
rbradforI will be proposing via ML later suggestions for identifying a what to better document what release option is deprecated and when it is to be removed. I have a high road nad low road21:20
*** lakshmiS has quit IRC21:21
rbradforthis is just some ground work for providing better information to devs and ops on logging capabilites.21:21
*** kproskurin has quit IRC21:21
rockygmake sure you include the ops ML when you post21:21
*** baoli has quit IRC21:21
rbradforthis first email will be about how developers should identify this information.21:22
*** baoli has joined #openstack-meeting-421:22
rockygAny questions/comments for rbradfor?21:22
rbradforhow that is then presented will be of benefit to the operators21:22
rbradforone more thing.21:22
rbradfor#link https://review.openstack.org/#/c/263468/21:23
*** ig0r_ has joined #openstack-meeting-421:23
rbradforthis has now greatly simplified how projects extend the default logging levels on startup, as in the now produced docs.  This will help to remove confusion and duplication, bringing an future oslo.log changes available to projects that implement this new method21:23
rockyg#link https://review.openstack.org/#/c/264977/21:24
rockyg#link http://docs.openstack.org/developer/oslo.log/usage.html21:24
rockyg#link https://review.openstack.org/#/c/267151/21:24
rockyg#link https://review.openstack.org/#/c/263468/21:24
*** mbound has joined #openstack-meeting-421:25
rockygexcellent!  This actually dovetails into what I think the next topic is and bringing dhellmann into the discussion21:26
*** lakshmiS has joined #openstack-meeting-421:26
rockygOK to move to next topic?21:26
rbradforyep!21:26
*** lakshmiS_ has joined #openstack-meeting-421:26
*** sdake has quit IRC21:26
rockyg#topic Config options -- prerequisite for sane logging21:27
*** openstack changes topic to "Config options -- prerequisite for sane logging (Meeting topic: log_wg)"21:27
rockygrbradfor and I have been discussing the state of config options21:27
*** jmckind has joined #openstack-meeting-421:28
*** angdraug has quit IRC21:28
rockygWe realize that it will be hard to get log levels in good shape if we don't have consistency in the configuration (among other issues, but this is a biggie)21:28
*** jmckind_ has quit IRC21:29
*** stanchan has quit IRC21:29
rockygWe both (and many Ops guys) see the lack of a good, documented way of providing global opts with local overides a major shortcoming to OpenStack.21:29
*** kebray has quit IRC21:30
rockygbut first, before we can do much here, we need to document the current state21:30
*** stanchan has joined #openstack-meeting-421:30
*** armax has joined #openstack-meeting-421:30
*** lakshmiS has quit IRC21:30
rockygSo, this sounds a little off topic for logging, but it's important for logging.21:30
*** ig0r_ has quit IRC21:31
rockygI want to throw together a spreadsheet that documents all the config options, what their defaults are, where the opts are defined and where they are set/reset, an values21:31
rockygStarting with the core six projects.21:32
*** javeriak_ has quit IRC21:32
rockygThen open the spreadsheet up for edits to get it better representative of what's really out there.21:32
*** lexholde_ has quit IRC21:32
rockygFrom there, discussion can arise on whether the values are right, whether individual projects should change/remove/add opts in their config files, etc.21:33
*** baoli has quit IRC21:33
dhellmannwhat do you mean by "global opts with local overrides"?21:34
*** baoli has joined #openstack-meeting-421:34
rbradforrockyg, I feel that running oslo-config-generator for the projects, and then perhaps aggregating this via some simple scripting will provide the "all the config options"21:34
rockygactually, all of them.  The project specific ones and the global.  The table/spreadsheet would have the global first, but then also have the project specific21:34
*** salv-orlando has quit IRC21:34
*** salv-orlando has joined #openstack-meeting-421:35
dhellmannI don't know what a "global"  option is, though. Do you mean an option that applies to all projects?21:35
rockygrbradfor, that was one of my next questions!21:35
rockyg"global" is pretty much the olso config opts.  They have defaults, but also get set in lots of projects21:35
*** zehicle has quit IRC21:35
dhellmannok21:36
rockygAnd you're right, we all agree that there aren't "global" config opts as yet.  Oslo is as close as it gets21:36
rbradforso perhaps a suggestion is find common options21:37
rbradforthat later may be a candidate for a possible global conf file21:37
rbradforand definitely for a global docs section on common options21:37
rockygI'm thinking that until we have something that documents the current state, we really can't do a good analysis to see if there are any improvements we can make or what the impacts would be21:37
rbradforrockyg, is your first goal to simplify docs?21:38
rockygAnd getting these (all of them) documented for ops/enduser docs for Mitaka would be something we think worthwhile21:38
rockygFirst goal is to get the current state documented and in such a way as the docs folks can propagate this infor in the current docs.  What you said, plus letting devs and community know what's what21:39
dhellmannwe added code to oslo.config to integrate with the documentation build for projects last cycle. that same code can be used to generate a document describing all of the options by running it against all of the projects instead of just one project.21:39
*** ajmiller has quit IRC21:40
rockygFantastic!  I bet the docs folks will be happy.  It also means that oslo *can* have a separate section in the config doc.21:40
dhellmannhttp://docs.openstack.org/developer/oslo.log/opts.html21:41
dhellmannthat's an example of the output for oslo.log21:41
rockygOnce we have all this, ops folks and others can see if the values make sense and file bugs on ones that don't.21:41
rockygThis also may help the nova config opts effort.21:41
dhellmannis there a separate config guide?21:42
dhellmannor is that part of the install guide?21:42
rockygthere is a separate config guide21:42
dhellmannfound it in http://docs.openstack.org/liberty/config-reference/content/21:42
rockygIt currently has no oslo section, just projects that have multiple sections on how to config various things21:42
dhellmannit looks like they're still using docbook for that, so we'll have to wait for the migration to sphinx21:43
rbradforrockyg, one thing you mentioned as a concern was "what are new options" or "changed values of options" in the next release. I guess you want this in this doc too.21:43
rockygYeah.21:44
*** ajmiller has joined #openstack-meeting-421:44
*** ig0r_ has joined #openstack-meeting-421:44
rockyg and that goes towards the discussion of ReNo and DocImpact that is happening now.21:44
*** ig0r_ has quit IRC21:45
rockygHopefully all config add/change/remove will get ReNo.21:45
*** baoli has quit IRC21:45
rockygBut the docs folks also have to incorporate.21:45
*** baoli has joined #openstack-meeting-421:45
rbradforI feel we need to get the docs folks to start with exsting docs and having a "common" or "Oslo" options section21:46
rbradforsimply reducing the documentation is an effective benefit for operators.21:46
rockygYup.  I started that discussion with Lana and Anne at the summit.  Lana is up for it and explained why to Anne.21:46
rbradforcan what you propose in this config guide be incoporated into already existing and known documentation people at least use and my be familar with21:46
rockygI think ops are familiar with the config ref.  They need to be if they want to change any values.  Which lots of them do.21:47
*** jmckind has quit IRC21:48
rockygdhellmann, do you think this is a reasonable prerequisite for getting options more consistent across a deployment, along with providing a base for identifying misleveled log messages?21:48
*** piet has quit IRC21:49
*** Sukhdev has joined #openstack-meeting-421:49
*** jmckind has joined #openstack-meeting-421:49
rockygAlso, we can bring Ops and UC folks into the discussion once we have generated the pieces of docs21:49
*** zehicle has joined #openstack-meeting-421:50
dhellmannthere will need to be an updated config reference for mitaka, so getting that into good shape seems like a good place to start21:50
dhellmannwe should look into how that guide is built now, and whether the doc team has it on their sphinx conversion plan already21:50
rockygGreat!21:51
dhellmannand then start contributing to it to update it21:51
dhellmannlike rbradfor said, having a completely new guide is likely to confuse folks as much as anything21:51
rockyg#action configuration reference doc discussion with docs team21:51
rockygA concatenated list of options could always be added as an adendum this round.21:52
*** pbourke_ has quit IRC21:53
*** sdake has joined #openstack-meeting-421:53
*** pbourke_ has joined #openstack-meeting-421:53
rockygOK.  rbradfor could you generate the doc files from the configs you are aware of?  I'll go searching to see if there are strays elsewhere and also discuss this with the nova config opts lead?21:53
rbradforrockyg, are you seeking a http://docs.openstack.org/developer/oslo.log/opts.html format of options for projects, rather then a sample.conf file?21:54
rockygI will also go through and find dupes/changed values/etc once we have the list.  Good place to start the discussions.  And a good way to make devs aware of the oslo opts.  And, yeah.  If we can get the html format for the core six projeccts, that would be great.21:55
dhellmannrockyg : my comment about generating that documentation for all projects in one guide depends on a tool change by the docs team21:56
rockygNova, cinder, Neutron, Keystone, Glance, Swift  Am I missing any?21:56
*** sdake_ has joined #openstack-meeting-421:56
dhellmannthat's why I brought up the sphinx conversion plan21:56
rbradfordhellmann, whats the sphinx conversion plan?21:56
dhellmannrbradfor : the docs team is converting from docbook to sphinx, one manual at a time21:56
dhellmannI don't know what the schedule is, or the order.21:57
*** dshakhray has quit IRC21:57
rockygRight. I'm not yet read for the docs, but if we can get the html files, that will let us do some analysis while we talk to docteam21:57
dhellmannthe thing we're using in oslo.log to generate that table depends on being integrated into sphinx, not the docbook tool chain they are using now21:57
rockygnot yet ready...21:57
*** baoli has quit IRC21:57
*** sdake has quit IRC21:57
dhellmannas an interim measure we could add a similar page to all of the individual projects in their developer documentation21:58
*** baoli has joined #openstack-meeting-421:58
rockygSo, nova uses sphinx for a bunch of their stuff.  Is that enough, or are there specific things?21:58
*** vhoward has quit IRC21:58
dhellmannsome folks have started doing that, and are keeping notes in https://etherpad.openstack.org/p/automating-oslo-config-documentation21:58
rockygdhellmann, ++  That gives *us* what we need to start.21:59
dhellmannrockyg : someone needs to add instructions to the nova docs that say "put the configuration options here"21:59
rockyg#link https://etherpad.openstack.org/p/automating-oslo-config-documentation21:59
rockygI expect that is what is needed for each of the projects?21:59
dhellmannright22:00
rockygYou just need someone to go down the list and hit every project?  I can certainly work on that.22:00
dhellmannyep22:00
rockygkewl.22:01
rbradfordhellmann, of those projects in the etherpad, docs.o.o/developer/project are already sphinx generated22:01
dhellmannyes, they should be22:01
dhellmannso for these cases we just need to add the page containing the directive from oslo.config to spit out the options22:01
rockygSo, it's just adding the directive/matching the example.22:01
rockygOK.  I think rbradfor and I have our work cut out for us.  And we are past time.22:02
rockygWe all good?22:02
rbradforrockyg, I can take a look at this for one project to see what the output comes out like. is nova (biggest and hardest) the place to start22:02
*** spzala has joined #openstack-meeting-422:03
rockygYup  and the team working on making the opts better has an etherpad with team member names and stuff here:  #link https://etherpad.openstack.org/p/config-options22:03
rockygYay! I'm calling it.22:04
rockygThanks all and dhellmann22:04
rockyg#endmeeting22:04
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:04
openstackMeeting ended Wed Jan 13 22:04:27 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-13-21.15.html22:04
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/log_wg/2016/log_wg.2016-01-13-21.15.txt22:04
openstackLog:            http://eavesdrop.openstack.org/meetings/log_wg/2016/log_wg.2016-01-13-21.15.log.html22:04
rockyggotta run to a NY video shoot for the company....22:04
*** belmoreira has quit IRC22:05
*** piet has joined #openstack-meeting-422:05
*** spzala has quit IRC22:07
*** rbak has joined #openstack-meeting-422:09
*** salv-orl_ has joined #openstack-meeting-422:09
*** baoli has quit IRC22:09
*** baoli has joined #openstack-meeting-422:10
*** salv-orlando has quit IRC22:12
*** galstrom is now known as galstrom_zzz22:14
*** yamahata has quit IRC22:14
*** baoli_ has joined #openstack-meeting-422:21
*** bobh_ has joined #openstack-meeting-422:21
*** dingboopt has joined #openstack-meeting-422:22
*** Sukhdev has quit IRC22:22
*** bobh has quit IRC22:23
*** baoli__ has joined #openstack-meeting-422:24
*** bobh has joined #openstack-meeting-422:24
*** baoli has quit IRC22:24
*** armax has quit IRC22:25
*** bobh has quit IRC22:25
*** avarner has quit IRC22:26
*** baoli_ has quit IRC22:26
*** bobh_ has quit IRC22:27
*** baoli__ has quit IRC22:27
*** baoli has joined #openstack-meeting-422:28
*** baoli has quit IRC22:30
*** baoli has joined #openstack-meeting-422:30
*** zehicle has quit IRC22:33
*** sridhar_ram has quit IRC22:33
*** Sukhdev has joined #openstack-meeting-422:33
*** sridhar_ram has joined #openstack-meeting-422:33
*** rockyg has quit IRC22:34
*** Sukhdev has quit IRC22:34
*** spzala has joined #openstack-meeting-422:35
*** piet has quit IRC22:35
*** spzala has quit IRC22:35
*** spzala has joined #openstack-meeting-422:36
*** bobh has joined #openstack-meeting-422:38
*** spzala has quit IRC22:40
*** baoli has quit IRC22:42
*** baoli has joined #openstack-meeting-422:43
*** jmccrory has joined #openstack-meeting-422:43
*** neelashah has quit IRC22:49
*** kebray has joined #openstack-meeting-422:51
*** armax has joined #openstack-meeting-422:54
*** baoli has quit IRC22:54
*** baoli has joined #openstack-meeting-422:55
*** sigmavirus24 is now known as sigmavirus24_awa22:55
*** kebray has quit IRC23:01
*** armax has quit IRC23:01
*** spzala has joined #openstack-meeting-423:04
*** spotz is now known as spotz_zzz23:04
*** banix has quit IRC23:06
*** baoli has quit IRC23:06
*** baoli has joined #openstack-meeting-423:07
*** klamath_ has quit IRC23:07
*** jmckind has quit IRC23:08
*** spzala has quit IRC23:09
*** ahelkhou has quit IRC23:14
*** baoli_ has joined #openstack-meeting-423:18
*** baoli__ has joined #openstack-meeting-423:20
*** baoli has quit IRC23:21
*** baoli_ has quit IRC23:23
*** spzala has joined #openstack-meeting-423:25
*** bobh has quit IRC23:27
*** inc0 has quit IRC23:27
*** amotoki has joined #openstack-meeting-423:28
*** baoli__ has quit IRC23:29
*** spzala has quit IRC23:29
*** spotz_zzz is now known as spotz23:34
*** armax has joined #openstack-meeting-423:37
*** spotz is now known as spotz_zzz23:37
*** dratushnyy has joined #openstack-meeting-423:38
*** macsz has quit IRC23:39
*** rbak has quit IRC23:41
*** Swami has quit IRC23:46
*** jmckind has joined #openstack-meeting-423:51
*** mbound has quit IRC23:51
*** armax has quit IRC23:51
*** amotoki has quit IRC23:52
*** amotoki has joined #openstack-meeting-423:52
*** amotoki has quit IRC23:53
*** armax has joined #openstack-meeting-423:58

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