Wednesday, 2016-01-06

*** rbak has quit IRC00:02
*** Jeffrey4l has joined #openstack-meeting-400:04
*** sdake has quit IRC00:06
*** baohua has quit IRC00:10
*** piet has quit IRC00:13
*** piet has joined #openstack-meeting-400:13
*** Sukhdev has joined #openstack-meeting-400:22
*** sdake has joined #openstack-meeting-400:32
*** uck_ has quit IRC00:40
*** Jeffrey4l has quit IRC00:43
*** bpokorny has joined #openstack-meeting-400:44
*** galstrom is now known as galstrom_zzz00:49
*** padkrish has quit IRC01:01
*** daneyon has joined #openstack-meeting-401:01
*** zehicle has joined #openstack-meeting-401:03
*** Sukhdev has quit IRC01:08
*** gomarivera has quit IRC01:09
*** bpokorny_ has joined #openstack-meeting-401:16
*** clayton has quit IRC01:17
*** clayton has joined #openstack-meeting-401:18
*** gampel1 has quit IRC01:18
*** bpokorny has quit IRC01:20
*** bpokorny_ has quit IRC01:21
*** stanchan has quit IRC01:21
*** Sukhdev has joined #openstack-meeting-401:29
*** julim has quit IRC01:30
*** clayton has quit IRC01:30
*** julim has joined #openstack-meeting-401:30
*** prashantD_ has joined #openstack-meeting-401:35
*** sridhar_ram has quit IRC01:36
*** prashantD has quit IRC01:38
*** sdake has quit IRC01:40
*** baohua has joined #openstack-meeting-401:42
*** banix has joined #openstack-meeting-401:47
*** shaohe_feng_ has quit IRC01:49
*** clayton has joined #openstack-meeting-401:50
*** Swami has quit IRC01:56
*** sridhar_ram has joined #openstack-meeting-402:02
*** gomarivera has joined #openstack-meeting-402:04
*** piet has quit IRC02:09
*** piet has joined #openstack-meeting-402:15
*** sridhar_ram has quit IRC02:17
*** stanchan has joined #openstack-meeting-402:21
*** sdake has joined #openstack-meeting-402:27
*** gomarivera has quit IRC02:29
*** yamamoto has joined #openstack-meeting-402:35
*** njohnst__ has joined #openstack-meeting-402:36
*** piet has quit IRC02:37
*** Sukhdev has quit IRC02:39
*** njohnsto_ has quit IRC02:40
*** yamamoto has quit IRC02:48
*** daneyon has quit IRC02:51
*** yamamoto has joined #openstack-meeting-402:54
*** yamamoto_ has joined #openstack-meeting-402:57
*** yamamoto has quit IRC02:57
*** dims has quit IRC02:59
*** s3wong has quit IRC03:01
*** Chaozhe has joined #openstack-meeting-403:03
*** chaozhechen_ has joined #openstack-meeting-403:03
*** yamamoto_ has quit IRC03:07
*** gjayavelu has joined #openstack-meeting-403:13
*** gjayavelu has quit IRC03:13
*** daneyon has joined #openstack-meeting-403:19
*** armax has joined #openstack-meeting-403:26
*** gomarivera has joined #openstack-meeting-403:46
*** prashantD_ has quit IRC03:49
*** daneyon has quit IRC03:49
*** yamahata has quit IRC03:52
*** bpokorny has joined #openstack-meeting-403:52
*** Kevin_Zheng has joined #openstack-meeting-403:57
*** yamamoto has joined #openstack-meeting-403:57
*** banix has quit IRC04:01
*** galstrom_zzz is now known as galstrom04:01
*** coolsvap|away is now known as coolsvap04:06
*** yamamoto has quit IRC04:06
*** kebray has joined #openstack-meeting-404:13
*** kebray has quit IRC04:15
*** kebray has joined #openstack-meeting-404:15
*** galstrom is now known as galstrom_zzz04:28
*** coolsvap is now known as coolsvap|away04:29
*** stanchan has quit IRC04:32
*** sdake has quit IRC04:38
*** sdake has joined #openstack-meeting-404:44
*** stanchan has joined #openstack-meeting-404:44
*** _ody has quit IRC04:44
*** prashantD has joined #openstack-meeting-404:47
*** Jeffrey4l has joined #openstack-meeting-405:02
*** kebray has quit IRC05:13
*** fawadkhaliq has joined #openstack-meeting-405:17
*** gjayavelu has joined #openstack-meeting-405:18
*** kebray has joined #openstack-meeting-405:18
*** coolsvap|away is now known as coolsvap05:35
*** gampel has joined #openstack-meeting-405:43
*** piet has joined #openstack-meeting-405:49
*** bpokorny has quit IRC05:52
*** irenab has joined #openstack-meeting-405:55
*** coolsvap is now known as coolsvap|away05:55
*** baohua has quit IRC06:00
*** baohua has joined #openstack-meeting-406:01
*** javeriak has joined #openstack-meeting-406:03
*** javeriak has quit IRC06:08
*** javeriak has joined #openstack-meeting-406:10
*** piet has quit IRC06:12
*** coolsvap|away is now known as coolsvap06:18
*** dslevin has quit IRC06:20
*** prashantD has quit IRC06:30
*** enowy_ has joined #openstack-meeting-406:31
*** Sukhdev has joined #openstack-meeting-406:37
*** gampel has quit IRC06:39
*** paul-carlton2 has joined #openstack-meeting-406:43
*** paul-carlton2 has quit IRC06:50
*** paul-carlton2 has joined #openstack-meeting-406:52
*** dslevin has joined #openstack-meeting-406:54
*** belmoreira has joined #openstack-meeting-406:59
*** kebray has quit IRC06:59
*** javeriak has quit IRC06:59
*** javeriak has joined #openstack-meeting-407:03
*** armax has quit IRC07:07
*** baohua has quit IRC07:12
*** gampel has joined #openstack-meeting-407:15
*** numans has joined #openstack-meeting-407:19
*** stanchan has quit IRC07:19
*** enowy_ has quit IRC07:31
*** baohua has joined #openstack-meeting-407:31
*** fawadkhaliq has quit IRC07:37
*** fawadkhaliq has joined #openstack-meeting-407:40
*** Sukhdev has quit IRC07:46
*** fawadkhaliq has quit IRC07:48
*** fawadkhaliq has joined #openstack-meeting-407:49
*** Sukhdev has joined #openstack-meeting-407:49
*** Sukhdev has quit IRC07:57
*** coolsvap is now known as coolsvap|away08:00
*** yamahata has joined #openstack-meeting-408:01
*** coolsvap|away is now known as coolsvap08:06
*** tfukushima has joined #openstack-meeting-408:06
*** stanchan has joined #openstack-meeting-408:26
*** gjayavelu has quit IRC08:28
*** dtardivel has joined #openstack-meeting-408:33
*** matrohon has joined #openstack-meeting-408:33
*** fawadkhaliq has quit IRC08:46
*** javeriak has quit IRC08:47
*** ihrachys has joined #openstack-meeting-408:55
*** fawadkhaliq has joined #openstack-meeting-408:56
*** sdake has quit IRC09:02
*** fawadkhaliq has quit IRC09:07
*** f13o has quit IRC09:09
*** baohua has quit IRC09:30
*** tfukushima has quit IRC09:30
*** tfukushima has joined #openstack-meeting-409:31
*** gomarivera has quit IRC09:32
*** fawadkhaliq has joined #openstack-meeting-409:35
*** fawadkhaliq has quit IRC09:36
*** fawadkhaliq has joined #openstack-meeting-409:43
*** javeriak has joined #openstack-meeting-409:58
*** zeih has joined #openstack-meeting-410:00
*** javeriak_ has joined #openstack-meeting-410:02
*** ildikov has joined #openstack-meeting-410:06
*** javeriak has quit IRC10:07
*** fawadkhaliq has quit IRC10:09
*** _ag has quit IRC10:27
*** _ag has joined #openstack-meeting-410:27
*** gjayavelu has joined #openstack-meeting-410:32
*** gjayavelu has quit IRC10:32
*** gjayavelu has joined #openstack-meeting-410:32
*** gjayavelu has quit IRC10:35
*** fawadkhaliq has joined #openstack-meeting-410:44
*** tfukushima has quit IRC10:44
*** gjayavelu has joined #openstack-meeting-410:45
*** fawadkhaliq has quit IRC10:45
*** dims has joined #openstack-meeting-410:47
*** f13o has joined #openstack-meeting-410:49
*** chaozhechen_ has quit IRC10:50
*** Chaozhe has quit IRC10:51
*** fawadkhaliq has joined #openstack-meeting-410:54
*** fawadkhaliq has quit IRC10:56
*** fawadkhaliq has joined #openstack-meeting-411:10
*** zeih has quit IRC11:10
*** gjayavelu has quit IRC11:11
*** fawadkhaliq has quit IRC11:24
*** Prithiv has joined #openstack-meeting-411:31
*** prithivm has joined #openstack-meeting-411:31
*** coolsvap is now known as coolsvap|away11:47
*** zeih has joined #openstack-meeting-411:51
*** javeriak_ has quit IRC12:11
*** zeih has quit IRC12:21
*** fawadkhaliq has joined #openstack-meeting-412:38
*** fawadkhaliq has quit IRC12:39
*** fawadkhaliq has joined #openstack-meeting-412:39
*** cdelatte has joined #openstack-meeting-412:53
*** gampel has left #openstack-meeting-412:59
*** javeriak has joined #openstack-meeting-412:59
*** javeriak has quit IRC13:03
*** javeriak has joined #openstack-meeting-413:03
*** woodard has joined #openstack-meeting-413:04
*** woodard has quit IRC13:05
*** baoli has joined #openstack-meeting-413:05
*** woodard has joined #openstack-meeting-413:05
*** baoli has quit IRC13:06
*** bobh has joined #openstack-meeting-413:06
*** baoli has joined #openstack-meeting-413:07
*** bobh has quit IRC13:08
*** javeriak_ has joined #openstack-meeting-413:08
*** javeriak has quit IRC13:09
*** klamath has joined #openstack-meeting-413:10
*** klamath has quit IRC13:10
*** klamath has joined #openstack-meeting-413:11
*** baoli has quit IRC13:11
*** gjayavelu has joined #openstack-meeting-413:14
*** baoli has joined #openstack-meeting-413:16
*** baoli_ has joined #openstack-meeting-413:17
*** gjayavelu has quit IRC13:19
*** baoli has quit IRC13:20
*** dslev has joined #openstack-meeting-413:22
*** iurygregory has left #openstack-meeting-413:27
*** piet has joined #openstack-meeting-413:38
*** dslev has quit IRC13:38
*** alexstav has joined #openstack-meeting-413:42
*** alexstav has left #openstack-meeting-413:48
*** trozet has quit IRC13:50
*** brunograz has joined #openstack-meeting-413:52
*** vincentfrancoise has joined #openstack-meeting-413:52
*** alexstav has joined #openstack-meeting-413:53
*** njohnst__ has quit IRC13:55
*** baohua has joined #openstack-meeting-413:56
*** zeih has joined #openstack-meeting-413:58
*** bzhou has joined #openstack-meeting-413:59
acabot#startmeeting watcher14:00
openstackMeeting started Wed Jan  6 14:00:07 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
*** jwcroppe has joined #openstack-meeting-414:00
acabothi14:00
dtardivelhi14:00
bzhouhi14:00
brunograzhi14:00
jed56hello14:00
acabotour agenda for today #link https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#01.2F06.2F201614:00
jwcroppe\o14:00
vincentfrancoiseo/14:00
sballeo/14:00
edleafe\o14:00
acabothappy new year !14:00
jwcroppeo/14:00
sballe+114:00
jwcroppegreetings14:00
tpeopleso/14:01
dtardivelbonne année !14:01
*** vtech has joined #openstack-meeting-414:01
acabota lot of things to do today, lets start14:01
acabot#topic annoucements14:01
*** openstack changes topic to "annoucements (Meeting topic: watcher)"14:01
*** seanmurphy has joined #openstack-meeting-414:01
acabot#info mid-cycle meetup details are available and shared with the community14:02
acabotplease register on eventbrite asap if you plan to joins us14:02
alexstavHi guys! :)14:02
*** julim has quit IRC14:03
edleafelink to eventbrite?14:03
acabot#info Intel POC has been demonstrated and we will submit a talk for the OpenStack summit related to the demo14:04
seanmurphyv cool - well done!14:04
acabot#link https://www.eventbrite.com/e/watcher-mitaka-mid-cycle-developer-meetup-tickets-1988518713014:04
sballethanks for you help with getting the poc ready114:04
*** vmahe has joined #openstack-meeting-414:05
jwcroppesballe: cool - any video/details we can see?14:05
vmahehello14:05
acabot#info you can look at the video of watcher UI on https://drive.google.com/file/d/0B_h5gjY7WQPMTHZ5dVYybTA3MlE/view14:05
sballethat will be the next step.14:05
sballejwcroppe: we are woking on the story around the demo and willl make a movie14:05
jwcroppesballe: great!14:05
edleafesballe: cool!14:06
jwcroppeedleafe: https://wiki.openstack.org/wiki/Watcher_mitaka_mid-cycle_meetup_agenda for link to event brite14:06
edleafejwcroppe: acabot beat you to it :)14:06
sballelol14:07
acabotafter the POC, we know that anyone can add a new strategy in Watcher :-)14:07
sballe+114:07
bzhou+114:07
jwcroppe+10014:07
edleafejwcroppe: I'll probably only be able to make it up for 1 day, though14:07
jwcroppeedleafe: no prob - would be good to have you14:07
acabotedleafe: if you can be there on wednesday14:07
sballeedleafe: we can custmize the agenda. I wil be there the 3rd and 4th14:08
acabot#topic Review Action Items14:08
*** openstack changes topic to "Review Action Items (Meeting topic: watcher)"14:08
sballeacabot: jwcroppe I am trying to have Thijs, Nishi and one more person attend the mid-cycle14:08
acabotjed56 & vincentfrancoise did a great clean-up in reviews before end of year14:09
sballe+114:09
jwcroppe+114:09
jwcroppethanks guys!14:09
sballe+10014:09
*** bobh has joined #openstack-meeting-414:10
acabotour current target is mitaka-2 set to January 20th14:10
dtardivelnew tag 0.22.0 has been created on watcher ( > new pypi package available)14:10
acabothttps://review.openstack.org/#/c/257189 has been merged but needs improvements (see comments)14:11
*** dslevin_ has joined #openstack-meeting-414:12
acabotbzhou: how to you plan to integrate comments ?14:12
bzhouyes, we will work on improvements based on demo feedback, thanks.14:12
acabotbzhou: do you need a new BP ?14:13
acabotthis BP https://blueprints.launchpad.net/watcher/+spec/optimization-threshold is one part14:13
bzhouacabot: no, the major code is there. Some comments are out of control of watcher, e.g. using nova scheduler filters/weighers14:14
acabotbzhou: I'm concerned about having (poc code) in Watcher master branch14:14
jwcroppeI think the thresholds are ultimately part of the host aggregate metadata, so that you can have different thresholds for different groups?14:15
*** pmesserli has joined #openstack-meeting-414:15
tpeoplesbzhou: we should still be calling into the scheduler to get the possible hosts from its point of view.  the fact that watcher doesn't define the filters doesn't matter14:15
sballeacabot: I am not sure it is a problem since it is work in progress and people don't have to use it14:15
bzhouthe threshold is not part of outlet strategy14:15
jwcroppetpeoples: +100014:16
tpeoplesisn't it taking action when the temp reaches a certain value?14:16
acabotsballe: ok but we have identified improvements on this code and I dont want to lose it as the review has been merged14:16
tpeoples+114:17
acabotsballe: I'd like to know how bzhou will continue working on it and be able to track it (BP or specs or bugs...)14:17
jed56+114:17
jwcroppeacabot: I agree, we need a plan to get that PoC code removed I think... would be nice pre end of Mitaka14:17
bzhoutpeoples: nova-scheduler has no energy aware filters or weighers14:18
bzhouso we have to use our own filters before we can upstream any energy aware filters/weighers14:18
acabotjwcroppe: I dont think we need to remove it, its one possible strategy that can be used but there is still work to do on it14:18
tpeoplesbzhou:  sure, that would be on the specific implementation to handle.  we can't be migrating VMs to hosts that the nova scheduler defines as not valid though14:18
tpeoplesthat's why we still need to use the scheduler14:18
sballeI suggest a BP to track14:18
tpeoplesto get the possible hosts14:19
jed56tpeoples:+114:19
jwcroppebzhou: right, we need the scheduler to get the possible hosts per its filters, and then you can add more filters/logic beyond the scheduler14:19
bzhoutpeoples: do we have nova api to get possible hosts?14:19
tpeoplesi.e., we can't ignore all the other filters that already exist14:19
edleafeyou can always add custom filters14:19
edleafein addition14:19
jwcroppebzhou: yes, scheduler API has 'select_destinations'14:19
bzhouis it a public API?14:19
jwcroppeyes, rpcapi14:19
acabotbzhou: ok could you submit a BP asap related to nova filters usage ?14:20
bzhoumaybe I am wrong, but I thought rpcapi is not designed to be used by other projects?14:20
edleafebzhou: correct14:20
acabotbzhou : we will have to write a spec for it and will iterate on it14:20
edleaferight now scheduler is internal to nova14:21
sballebzhou: I agree rpc is too low14:21
jwcroppeedleafe: it's standard practice for OpenStack projects to use rpcapis, IIRC ... same queue14:21
sballejwcroppe: it is?14:22
bzhouwe do plan to add energy aware filters into nova-scheduler, but I don't we can make it in Mitaka14:22
sballethe other issue we have with using rpcapi is that now we are really tied to openstak14:22
edleafejwcroppe: my understanding is that cross-project is via API14:22
acabot#action bzhou submit a BP to use nova filters in the inlet temperature strategy14:22
sballe+114:22
jwcroppesballe: I've seen it done several times.  And it's the only option right now for interacting with the scheduler14:22
bzhoujwcroppe: do you know where I can find it?14:23
edleafejwcroppe: a reference would be helpful14:23
sballeI thinkg we are better off not using rpcapi but let's discuss durign the review of the spec14:23
bzhouacabot: got it, thanks14:23
jwcroppeSorry, I don't want to go into the weeds here :)  But, I think the alternative of not using the scheduler rpcapi leaves us open to many 'gotchas' since we are making bad placement decisions14:23
sballejwcroppe: I disagree but we can discuss on the spec14:23
*** javeriak_ has quit IRC14:24
acabotlets move this tech discussion on gerrit14:24
edleafeI'll ask for ideas in #openstack-nova14:24
sballeand if you can get us some references it will help to14:24
*** neelashah has joined #openstack-meeting-414:25
jwcroppesballe: sounds good - my concern is that if there are 10 filters defined that indicate hosts should *not* be candidates, but we relocate VMs to them anyway, seems like we defied the placement rules.  From my experience so far, that would result in trying to placement VMs in locations they shouldn't be running14:25
jwcroppebzhou: I'll dig up some examples14:25
sballeI like the idea of using the nova filters14:26
sballeI am just not sure about rcpapi14:26
edleafesballe: +114:26
acabotlets move on watcher specs please14:26
jwcroppeacabot: +114:26
sballe+114:26
acabotcould we merge the spec related to Intel POC ? https://review.openstack.org/#/c/252268/14:27
sballeyes.14:27
acabotas it is already implemented14:27
bzhoujwcroppe: thanks14:27
seanmurphythe select destinations spec indicates that it is part of a larger effort to split out the scheduler - in this context, it would seem to be reasonable to use the rpcapi - https://specs.openstack.org/openstack/nova-specs/specs/kilo/approved/sched-select-destinations-use-request-spec-object.html (not from any particular deep knowledge/insight - just a quick search)14:27
jwcroppeacabot: I think so, let's give until EOW for final review comment?14:28
acabotsubmited in kilo and pending approval on launchpad :-(14:28
bzhouit's not implemented yet14:29
acabotjwcroppe: ok for EOW14:29
acabotwe need reviews on this spec https://review.openstack.org/#/c/257494/14:29
acabotto start implementing14:29
sballeare we talking EOW for https://review.openstack.org/#/c/252268/? i lost the context for EOW14:30
bzhouas I know, the current nova-scheduler subteam's focus on Mitaka is the mitaka/approved/request-spec-object-mitaka.rst14:30
acabotthis will allow anyone to add custom actions (the same way as we can add custom strategies)14:30
jwcroppewill look today14:30
sballesame here14:30
acabotsballe: yes https://review.openstack.org/#/c/252268/ for EOW14:30
acabot#action acabot merge https://review.openstack.org/#/c/252268/ by EOW14:31
acabotspecs from cdupont and brunograz must be reviewed also14:32
*** baohua has quit IRC14:32
edleafebzhou: the focus is on cleaning up the interface with nova; request-spec object is a part of that14:32
sballeok14:32
acabot#action sballe acabot jwcroppe review https://review.openstack.org/#/c/257494/ https://review.openstack.org/#/c/260552/ https://review.openstack.org/#/c/258608/14:33
*** baohua has joined #openstack-meeting-414:33
acabot#topic Blueprint/Bug Review and Discussion14:34
*** openstack changes topic to "Blueprint/Bug Review and Discussion (Meeting topic: watcher)"14:34
bzhouedleafe: agree, thanks14:34
seanmurphyacabot: we did not produce spec yet - iiuc we had until jan 2014:34
acabotseanmurphy: yes I have it in mind14:35
acabotwe will have to update the data model of Watcher to allows custom actions, do you think we need to handle a migration ?14:35
seanmurphycool - keeping on top of things ;-)14:35
alexstavGuys, I wanna to discuss bug with [user|project]_domain_name variable in watcher/common/keystone.py14:36
acabotas we are still in v0.x, I think we can drop the DB when updating14:36
alexstav#link https://bugs.launchpad.net/watcher/+bug/153079014:36
openstackLaunchpad bug 1530790 in watcher "making configurable user|project]_domain and [user|project]_domain_ID " [High,Confirmed] - Assigned to Alexander Stavitskiy (alexstav)14:36
tpeoplesimo, no acabot - too early.  but that may break the intel POC, so if they would want to migrate?14:36
jed56tpeoples : +114:37
tpeoplesalexstav:  can you hold that for open discussion14:37
jwcroppeacabot: +1 ... drop db for now14:37
acabotalexstav: we will come back to it after BPs review, thx14:37
sballejwcroppe: +114:37
acabotsballe bzhou : your opinion about db migration ?14:38
tpeoplesshe said +1 :)14:38
sballebut bzhou has the final say14:38
acabotok :-D14:38
sballeso I'll let him14:38
alexstavacabot tpeoples: Sorry, I thought topic is about bug/bp :)14:38
*** Swami has joined #openstack-meeting-414:38
*** piet has quit IRC14:39
bzhousorry, what is the db migration?14:39
*** piet has joined #openstack-meeting-414:39
acabotwe will start integrating taskflow in Watcher applier, just to confirm that we dont need a spec for it14:39
sballebzhou: can you answer the question above from acabot14:40
acabotbzhou: adding custom actions will impact the data model and we dont want to provide a migration tool14:40
acabotbzhou: I just want to be sure that you can drop the DB and recreate it for the POC14:40
bzhouI think it should be ok14:41
*** rbak has joined #openstack-meeting-414:41
acabotbzhou : ok could you also update the state of https://blueprints.launchpad.net/watcher/+spec/outlet-temperature-based-strategy ?14:41
tpeoplesacabot:  i think the other BP / spec that jed56 is working on can include using taskflow as part of the spec. they are intertwined14:42
acabottpeoples: yes it is14:42
acabottpeoples: we will try to separate the reviews14:42
jwcroppetpeoples: +1000 for task flow14:43
acabotthis BP (https://blueprints.launchpad.net/watcher/+spec/external-api-versioning) is targeted for mitaka-2 but has no Assignee, does anyone wants to start it ?14:43
bzhouacabot: I don't have permission to update the state14:43
acabotbzhou: OK strange, I set it as implemented as you will create a new one14:44
tpeoplesacabot: i can take that14:44
acabot#action tpeoples start working on https://blueprints.launchpad.net/watcher/+spec/external-api-versioning14:45
acabottpeoples: thx14:45
acabotalexstav: we need updates on your BPs  https://blueprints.launchpad.net/watcher/+spec/watcher-overload-underload & https://review.openstack.org/#/c/258608/14:46
acabotalexstav: there is still no spec submitted on watcher-specs14:46
acabotalexstav: is it still alive ?14:46
alexstavacabot: yes, it is. We'll start work on this BP after holidays.14:47
dtardivelbzhou: you are not member of Watcher Drivers team.14:47
*** javeriak has joined #openstack-meeting-414:47
acabotalexstav : the 2 BPs ?14:47
dtardivel#action dtardivel add bzhou into Wather Drivers team14:48
acabotalexstav: by the way thats a great news !14:48
alexstavacabot: overload/underload at first, than watcherclient :)14:48
acabotso lets have a 5 minutes bugs discussion14:48
bzhoudtardivel: thanks:-)14:48
acabothttps://bugs.launchpad.net/watcher/+bug/153079014:48
openstackLaunchpad bug 1530790 in watcher "making configurable user|project]_domain and [user|project]_domain_ID " [High,Confirmed] - Assigned to Alexander Stavitskiy (alexstav)14:49
*** julim has joined #openstack-meeting-414:49
alexstavThanks. I  solved the problem of authorisation in Keystone. Problem was not in my creds or keystone configuration.  When Watcher gets credentials for KeystoneClient() in /watcher/common/keystone.py, he sends keystone_authtoken params. Some of them he takes from watcher.conf file, and some sets manually (eg. user_domain_name and project_domain_name). So the problem was that I had domain name ‘Default’, but not ‘default’.14:49
alexstavSo why wouldn’t we add project_domain_id and user_domain_id to watcher.conf, like this is done in the configuration files of other projects (like nova.conf, neutron.conf, etc.)?14:49
dtardivelalexstav: yes this is the final solution14:50
jed56alexstav : +1 you can push a patchset14:50
bzhou+114:50
alexstavI created small patch at my local repo, it works with Liberty :)14:50
acabotok solved ? :-D14:50
alexstav:D14:50
bzhouas we are talking about keystone, I'd like to discuss https://review.openstack.org/#/c/260354/14:51
alexstavI had solved another problem in this patch.14:51
alexstavUps, sorry.14:51
jed56bzhou: yes with david will take a look we have to test it14:52
alexstav#link https://github.com/Stavitsky/watcher/commit/0ead5de97e5a102e7e1a0b4851d3aa753a4816f7 Here it is my small patch. Watcher didn't migrate VMs with shared storage.14:52
dtardivelbzhou: I will make some tests on devstack multi node conf to validate your assumption14:52
bzhouok, thanks14:52
jed56bzhou sorry for delay to response14:52
dtardivelalexstav: please submit a patchset to gerrit14:52
acabotalexstav: we use gerrit for code reviews, please read https://wiki.openstack.org/wiki/Watcher/Contributing14:52
alexstavCause in Primitives-class in watcher/decision_engine/planner/default.py there are no differ between LOVE_MIGRATE and COLD_MIGRATE values.14:53
alexstavYep, i'll do that. I wanna to discuss the problem.14:53
jed56how do you make love_migration ? :p14:53
acabotalexstav: thx14:53
alexstavАХАХХАХА14:53
alexstavahahah14:53
alexstavSorry, a mean LIVE_MIGRATION14:54
acabot:-D14:54
alexstav:D14:54
dtardivelhttps://bugs.launchpad.net/watcher/+bug/151017914:54
openstackLaunchpad bug 1510179 in watcher "Can not create an audit template with same name after deleting it previously." [Medium,Confirmed] - Assigned to Zhenzan Zhou (zhenzan-zhou)14:54
acabot#action alexstav submit patchset on gerrit for https://bugs.launchpad.net/watcher/+bug/153079014:54
openstackLaunchpad bug 1530790 in watcher "making configurable user|project]_domain and [user|project]_domain_ID " [High,Confirmed] - Assigned to Alexander Stavitskiy (alexstav)14:54
tpeoplesvincentfrancoise:  are you still working on https://blueprints.launchpad.net/watcher/+spec/tempest-basic-set-up ?  i passed that to you before break, but wondering if i can / should take it back unless you've made some progress?14:54
acabot#topic open discussions14:54
*** openstack changes topic to "open discussions (Meeting topic: watcher)"14:54
jed56alexstav : This code will be removed with the bp dynamic actions14:55
dtardivelbzhou: are you working on it ?14:55
alexstavjed56: what code?14:55
acabot#info sballe proposed 2 talks for the Austin summit (https://etherpad.openstack.org/p/Watcher_abstracts_austin2016)14:55
bzhouyes, but I'm blocked at db migration testing14:55
*** jmckind has joined #openstack-meeting-414:55
*** Ng has joined #openstack-meeting-414:55
*** zeih has quit IRC14:56
jed56alexstav: you talk it after the meeting on openstack-watcher14:56
vincentfrancoisetpeoples: yes I didn't work on it much but I'm currently on it, so I guess I'll carry on14:56
acabotI will propose an agenda for the mid-cycle for our next meeting14:56
bzhouare we going to use a new db schema?14:56
tpeoplesdtardivel: jed56: can you guys review the devstack plugin when you get time?  i'd like to get that merged14:56
bzhouthen I don't need to worry about db migration14:56
sballeacabot: I have a couple of items that I would liek to the agenda14:56
dtardiveltpeoples: I'm working on it this afternoon :)14:57
sballeI'll ping you Friday morning since I am traveling all day tomorrow.14:57
acabotsballe: OK feel free to add them on the wiki page14:57
tpeoplesthanks dtardivel14:57
acabotsballe: ok14:57
sballeacabot: ^^ or send you an email14:57
acabotsballe: ok too14:57
sballe:)14:57
tpeoplesok vincentfrancoise, thanks14:58
acabotany other subject in 2 minutes ?14:58
sballenot for me14:58
acabot#action jed56 dtardivel review devstack plugin14:58
*** sigmavirus24_awa is now known as sigmavirus2414:59
bzhouacabot: are we going to use a new db schema without migration?14:59
seanmurphyis there a set of features expected for the mitaka release/roadmap somewhere14:59
acabotbzhou: yes14:59
acabotseanmurphy: https://blueprints.launchpad.net/watcher/mitaka14:59
seanmurphythanks14:59
acabotthank you, bye15:00
sballebye15:00
bzhouthanks15:00
acabot#endmeeting15:00
brunograzbye15:00
dtardivelbye15:00
vincentfrancoisebye15:00
bzhoubye15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Wed Jan  6 15:00:18 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-01-06-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-01-06-14.00.txt15:00
alexstavbye, thanks15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-01-06-14.00.log.html15:00
*** alexstav has left #openstack-meeting-415:00
jasondotstar#startmeeting vahana15:00
openstackMeeting started Wed Jan  6 15:00:57 2016 UTC and is due to finish in 60 minutes.  The chair is jasondotstar. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: vahana)"15:01
openstackThe meeting name has been set to 'vahana'15:01
*** brunograz has left #openstack-meeting-415:01
jasondotstar#topic roll call15:01
*** openstack changes topic to "roll call (Meeting topic: vahana)"15:01
Ng.o/15:01
jasondotstaro/15:01
jasondotstargreetings, Ng15:01
Nghey :)15:01
jasondotstar#topic Introduction15:01
*** openstack changes topic to "Introduction (Meeting topic: vahana)"15:01
*** jwcroppe has left #openstack-meeting-415:02
jasondotstarAgain, this is a friendly remeinder that the OpenStack Vahana project15: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
*** zeih has joined #openstack-meeting-415:02
jasondotstarInterested parties are encouraged to join the #openstack-vahana IRC channel15:02
jasondotstarhopefully, we'll get to a point where I won't have to say that :-)15:03
Ng:)15:03
jasondotstar#topic Action Items from Last Meeting15:03
*** openstack changes topic to "Action Items from Last Meeting (Meeting topic: vahana)"15:03
jasondotstarso, it's our first meeting of the new year15:03
jasondotstarlots of ground to cover, if we're to get this truly off the ground15:04
jasondotstarguess it's time to kick the tires and light the fires15:04
jasondotstarwith that let's see where we are today....15:04
jasondotstarNg to make contact with the UX team15:04
jasondotstaranything yet?15:04
Ngjasondotstar: I have nothing to report, christmas got completely in the way of doing anything15:05
Ngbut I will have something for next week15:05
jasondotstaryeah, about the same here :-(15:05
*** baohua_ has joined #openstack-meeting-415:05
jasondotstarlet's put this on the agenda again then15:05
*** spotz_zzz is now known as spotz15:05
jasondotstar#action Ng to make contact with the UX team15:05
*** baohua has quit IRC15:05
jasondotstarnext one:15:05
jasondotstarjasondotstar to make contact with either the infra team or the horizon team to identify use cases15:05
jasondotstarI did make contact15:06
jasondotstarbut there's more discussion to have15:06
jasondotstarb/c I really need to capture the use cases in a doc somewhere15:06
jasondotstari mean, we've got the brainstorming etherpad15:06
jasondotstarbut is there a more 'official' place to put these atm?15:06
NgI don't think so15:06
jasondotstaror just capture them there, and then xfr them to a wiki page later15:07
jasondotstari couldn't think of a better place (for now)....ok15:07
jasondotstar#action jasondotstar to make progress on capturing use cases on the brainstorming etherpad15:08
jasondotstarnext up:15:08
jasondotstarjasondotstar to chat with -infra about public cloud API testing environment(s)15:08
jasondotstarthis one needs to simply move fwd.15:08
jasondotstarno progress on that ask yet...15:08
jasondotstar#action jasondotstar to chat with -infra about public cloud api testing enviros. Report findings at the next mtg.15:09
*** bzhou has quit IRC15:09
NgI feel like we should also get a repo :)15:09
jasondotstarype15:10
jasondotstar*yep15:10
jasondotstarthat's on the unassigned task list15:10
NgI can take an action to go and talk to infra about that15:10
jasondotstarcome up with a list of short-term MVP goals15:10
jasondotstaris also there.15:10
jasondotstar#action Ng to follow up with -infra about setting up a git repository for the project15:10
jasondotstarand I think we can continue capturing the short term goals, which in my mind is basically interfacing with one module at a time15:11
Ng+115:11
*** mhoppal has joined #openstack-meeting-415:12
jasondotstar#agreed Short-term goals are to iteratively work thru interfacing swift with each OS module API15:12
*** mhoppal has left #openstack-meeting-415:12
jasondotstarwe can list those out if need-be15:12
jasondotstarcool15:12
jasondotstarany other goals we need to add for this week?15:12
jasondotstarthat's probably a plenty15:13
jasondotstar:-)15:13
Ngyeah I think that'll do for now15:13
jasondotstar+115:13
jasondotstarok... moving on....15:13
jasondotstar#topic R&D15:13
*** openstack changes topic to "R&D (Meeting topic: vahana)"15:14
jasondotstarfor me personally..... the holiday was a friggin' wash. :-/15:14
jasondotstarso, Still catching up on my Swift-fu15:14
jasondotstaras i said before, I got alamofire working in a playground15:14
jasondotstarinterfacing with the HP public cloud atm15:15
Ngyeah I have a full holiday of zero R&D to report ;)15:15
*** numans has quit IRC15:15
jasondotstarcool. however.... you made a pretty awesome breakthru with the start of the vahana class structure15:16
jasondotstar#link http://pastebin.com/Fz9vcbw715:16
jasondotstarusing OSV at the class prefix.... do you see any conflicts with that?15:17
*** baohua_ has quit IRC15:17
NgI don't think so15:17
Ngdid you have something in mind?15:17
jasondotstarnah.. i couldn't think of anything15:17
jasondotstarjust want to ensure we have a unique namespace i guess :-/15:17
jasondotstarOSVIdentity (and the like) I assume isn't used anywhere else... hell Swift isn't used anywhere else for that matter15:18
Ngyeah I don't think we're going to clash with anything15:18
*** leecalcote has joined #openstack-meeting-415:18
jasondotstarbut i wonder if there are 3rd party libraries15:18
jasondotstar(non-OS related)15:19
Ngif you're worried, we could just abandon the three letter prefix thing and have VahanaBase, VahanaIdentity, etc15:19
jasondotstarnah not really, if you're set, I'm set.15:19
jasondotstari like the OSV distinction15:19
*** jwagner is now known as jwagner_wfh15:20
Ng:)15:20
jasondotstarmmmmmk that's probably it for R&D15:20
jasondotstaroh.... wait15:20
jasondotstarlocal dev environment i.e. local devstack15:20
*** vincentfrancoise has left #openstack-meeting-415:21
jasondotstarwanna see if I can get that working. i have one, but i want to see if i can document how to get the whole environment setup for testing everything locally15:22
jasondotstarI'll take that as a personal goal15:22
jasondotstar#action jasondotstar to report on documenting a vahana/devstack local test environment15:22
Ngyeah that's a good idea, get something we standardise on and make it easier for others :)15:22
*** jmckind_ has joined #openstack-meeting-415:23
jasondotstaryeah, that way when ppl decide it's a worthy cause, they can jump right in.15:23
jasondotstarany other R&D stuff? (we'll probably finish early today)15:24
Ngyeah, one thing15:24
jasondotstarok15:24
NgI'm a little concerned about how we deal with the myriad of possible openstack configurations/setups15:24
*** jmckind has quit IRC15:25
Ngeven in the lowest level classes, OSVIdentity could easily get very complex dealing with all the possible auth setups15:25
Nghow would we ever test them all?15:25
jasondotstartrue15:26
jasondotstaris it possible to read in a yaml file or something15:26
*** yamahata has quit IRC15:26
jasondotstarthat way we can have the configurations outside ?15:26
*** yamahata has joined #openstack-meeting-415:26
Ngperhaps, although ultimately it would be nice if we could discover stuff15:27
NgI'm not sure how reasonable that is though15:27
jasondotstarindeed.15:27
Ngand digging through python-openstackclient a bit, it's got an awful lot of architecture going on ;)15:27
jasondotstaryikes.15:27
NgI sort of feel like we should just get stuck in and get something that works against devstack, before trying to build layer upon layer that can cope with everything15:28
*** trozet has joined #openstack-meeting-415:28
*** iyamahat has joined #openstack-meeting-415:28
Ngagainst a stock devstack config, I mean15:28
*** galstrom_zzz is now known as galstrom15:28
jasondotstarsmall bites15:28
*** iyamahat has quit IRC15:28
Ngyeah15:28
jasondotstar+115:28
*** iyamahat has joined #openstack-meeting-415:29
jasondotstar#agreed working towards getting deals with a stock devstack configuration is the best course of action, prior to dealing with complex configurations15:29
jasondotstardamn typos....15:29
jasondotstars/getting/getting something that/15:30
jasondotstarany actions to take on this beside looking more into the python-openstackclient (eww)15:30
jasondotstar?15:30
NgI don't think so15:31
jasondotstaroki15:31
jasondotstar#topic Open Discussion15:32
*** openstack changes topic to "Open Discussion (Meeting topic: vahana)"15:32
jasondotstarso there's a local ios/cocoheads meetup group here in RTP15:32
*** AlanClark has joined #openstack-meeting-415:32
jasondotstarin the spirit of getting some helping hands, I've asked them to allow me to come to their meetup and present15:32
jasondotstarmy summit preso15:33
Ngnice!15:33
jasondotstarin hope to get a couple more folks15:33
*** leecalcote has quit IRC15:33
jasondotstargood group of guys/gals, so we'll see how that goes15:33
*** hdaniel has joined #openstack-meeting-415:33
jasondotstarother than that, that's all I've got15:34
NgI have nothing else15:35
jasondotstarcool. well, until next week15:35
jasondotstarthanks, Ng15:35
jasondotstarNg++15:35
jasondotstar#endmeeting15:35
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:35
Ngthanks jasondotstar :)15:35
openstackMeeting ended Wed Jan  6 15:35:25 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:35
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vahana/2016/vahana.2016-01-06-15.00.html15:35
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vahana/2016/vahana.2016-01-06-15.00.txt15:35
openstackLog:            http://eavesdrop.openstack.org/meetings/vahana/2016/vahana.2016-01-06-15.00.log.html15:35
*** Sukhdev has joined #openstack-meeting-415:40
*** zehicle_ has joined #openstack-meeting-415:41
*** zeih has quit IRC15:41
*** cloudtrainme has joined #openstack-meeting-415:47
*** devananda has quit IRC15:48
*** iyamahat has quit IRC15:51
*** iyamahat has joined #openstack-meeting-415:51
*** jmckind has joined #openstack-meeting-415:55
*** stanchan has quit IRC15:56
*** blahRus has joined #openstack-meeting-415:57
*** jmckind_ has quit IRC15:58
*** krtaylor has quit IRC15:58
*** neelashah has quit IRC15:59
*** neelashah has joined #openstack-meeting-416:00
*** devananda has joined #openstack-meeting-416:01
*** cloudtrainme has quit IRC16:03
*** cloudtrainme has joined #openstack-meeting-416:07
*** galstrom is now known as galstrom_zzz16:09
*** krtaylor has joined #openstack-meeting-416:11
*** prithivm has quit IRC16:11
*** Prithiv has quit IRC16:11
*** salv-orlando has joined #openstack-meeting-416:12
*** sdake has joined #openstack-meeting-416:14
*** kebray has joined #openstack-meeting-416:17
*** vhoward has joined #openstack-meeting-416:18
*** belmoreira has quit IRC16:18
*** rockyg has joined #openstack-meeting-416:20
*** prithivm has joined #openstack-meeting-416:22
*** alikwa has joined #openstack-meeting-416:22
*** Prithiv has joined #openstack-meeting-416:22
*** alikwa has quit IRC16:24
*** macsz1 has joined #openstack-meeting-416:25
*** akwasnie has joined #openstack-meeting-416:25
*** rockyg has left #openstack-meeting-416:26
*** rhallisey has joined #openstack-meeting-416:30
*** stvnoyes has joined #openstack-meeting-416:31
*** wznoinsk has quit IRC16:31
*** bpokorny has joined #openstack-meeting-416:31
*** wznoinsk has joined #openstack-meeting-416:32
*** bpokorny has quit IRC16:32
sdake#startmeeting kolla16:32
openstackMeeting started Wed Jan  6 16:32:07 2016 UTC and is due to finish in 60 minutes.  The chair is sdake. Information about MeetBot at http://wiki.debian.org/MeetBot.16:32
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:32
*** openstack changes topic to " (Meeting topic: kolla)"16:32
openstackThe meeting name has been set to 'kolla'16:32
sdake#topic rollcall16:32
*** openstack changes topic to "rollcall (Meeting topic: kolla)"16:32
SamYapleo/16:32
britthouser0/16:32
Jeffrey4lo/16:32
nihiliferhello16:32
rhalliseyhi16:32
elemoineo/16:32
sdakemorning folks \o/ :)16:32
akwasniehi16:32
Jeffrey4lsdake, mornings16:32
stvnoyeshi16:32
*** bpokorny has joined #openstack-meeting-416:32
akwasnie"Next meeting scheduled for January 6th, 1600 UTC" -> was afraid i missed the meeting16:33
SamYapleakwasnie: i fixed that :P16:33
akwasnie;)16:33
sdakewoops ;)16:33
jpeelerhi16:33
*** matrohon has quit IRC16:33
ajafohi16:33
sdakeok well we have a mountain of poeple16:33
sdakeso I will just  get started :)16:33
sdake#topic announcements16:33
*** openstack changes topic to "announcements (Meeting topic: kolla)"16:33
sdake1. milestone 1 was tagged.  I asked Sam Yaple to serve as backup in the case I am unable to tag the milestones.  Thanks for testing this first tag sam!16:34
*** dslevin_ has quit IRC16:34
sdake2. the midcycle is february 9th and february 10th, Tuesday/Wednesday.  Breakfast + lunch + coffee + soda are provided both days, dinner is provided Tuesday16:35
sdakeso the food costs should be minimal to zero16:35
sdakereallly the midcycle expense will be flight and hotel16:35
sdakeI am going to set up an invitation thing so I can see who is coming16:36
sdakeanyone is free to come if they like16:36
sdakeI think I had one more announcement but it escapes me atm16:37
sdakedoes anyone from the community have any announcements?16:37
*** Ng has left #openstack-meeting-416:37
SamYapleI have a new project bringing backups to openstack called ekko! #openstack-ekko16:37
SamYapleyou didnt say kolla specific :P16:37
sdakelol16:37
sdakeyes kolla specific please ;)16:37
sdake#topic midcycle planning16:38
*** openstack changes topic to "midcycle planning (Meeting topic: kolla)"16:38
*** kebray has quit IRC16:38
sdakeWe spent about 15 minutes in our lsat meeting before the end of 2015 proposing an agenda for the midcycle16:38
*** trumpetsherald has joined #openstack-meeting-416:38
sdakeI'd like to finish the job on that today - with a 10-15 minute timer16:39
sdakedoes anyone have the link handy of our last midcycle work?16:39
britthouserhttps://etherpad.openstack.org/p/kolla-mitaka-midcycle16:39
sdakethanks britt16:40
*** macsz1 has quit IRC16:40
sdake#link https://etherpad.openstack.org/p/kolla-mitaka-midcycle16:40
sdakeplese open that up and lets spend until 55 on the clock workign on it16:40
*** macsz has joined #openstack-meeting-416:40
britthousersamyaple and I need to armwrestle for that color. =P16:41
sdakeplease feel free to add your name so I know which color represents which author :)16:41
*** vishwanathj has quit IRC16:42
*** armax has joined #openstack-meeting-416:42
*** trumpetsherald_ has joined #openstack-meeting-416:43
*** dslevin_ has joined #openstack-meeting-416:44
*** pbourke_ has quit IRC16:44
*** pbourke_ has joined #openstack-meeting-416:44
*** hdaniel has quit IRC16:45
*** gjayavelu has joined #openstack-meeting-416:46
*** inc0 has joined #openstack-meeting-416:46
*** gjayavel_ has joined #openstack-meeting-416:47
SamYaplebritthouser: lol16:47
*** trumpetsherald_ has left #openstack-meeting-416:47
*** dslevin_ has quit IRC16:49
akwasniehttps://wiki.openstack.org/wiki/Sprints -> maybe we should add kolla to the list?16:49
*** galstrom_zzz is now known as galstrom16:49
*** piet has quit IRC16:50
*** gjayavelu has quit IRC16:51
*** prashantD has joined #openstack-meeting-416:52
sdakeok think time is up16:53
sdakeakwasnie I will take care of the sprints page16:53
sdakeI was gathering info yesterday and sorting out logistics16:53
sdakethey are all sorted otu now16:53
sdake(and obtaining budget for various things)16:53
akwasniesdake: ok :)16:53
sdakenext on agenda16:54
sdake#topic kolla-mesos TLDR update16:54
*** openstack changes topic to "kolla-mesos TLDR update (Meeting topic: kolla)"16:54
sdakenihilifer your up :)16:54
*** alexstav has joined #openstack-meeting-416:55
nihiliferthis week we were mainly focused on getting unlocked from images @ dockerhub16:55
nihiliferso i made our own16:55
nihilifer+ used ansible for they deployment16:55
sdakewhich type of images?16:55
nihiliferdocker images16:56
nihiliferfor zk, mesos(slave/master), marathon, chronos16:56
sdakecontaining what applciations?16:56
sdakeok got it16:56
sdakeyou don't want to use the upstream provided ones because they are deficient in some way?16:56
nihiliferthey're16:56
harmwnihilifer: based on centos/ubuntu?16:56
nihilifer1) not up to date16:56
nihilifer2) they run all things as root16:56
sdakeok well makes sense to me16:57
sdakeplus no wwe can make them for all the variou distros ;-)16:57
nihiliferharmw: the ones i pushed to kolla are for both centos and ubuntu16:57
*** salv-orlando has quit IRC16:57
nihiliferthis stuff i'm mentioning is in review now16:58
sdakeany other updates or shall I move on?16:58
harmware all required tasks in this area in LP?16:58
nihiliferafter getting that merged i think we may focus on bringing the other os services16:58
sdakenihilifer fwiw  Ithink it makes sense for us to provide  docker images for any software we expect to run in a kolla environment16:58
nihiliferthat's all from me :)16:58
*** salv-orlando has joined #openstack-meeting-416:58
harmwyes sdake, indeed16:58
sdake#topic elk containers - official images vs our own dockerfiles16:58
*** openstack changes topic to "elk containers - official images vs our own dockerfiles (Meeting topic: kolla)"16:59
sdakewhich leads us to -> :)16:59
akwasniewith transition from docker to kolla_docker an issue appeared16:59
britthouserofficial = rhel atomic ones? or something else?16:59
akwasniefor example, to deploy ELK services we use official images from dockerhub, which require additional param to be specified using ansible command16:59
sdakeofficial are thte upstream provided iamges of elkstack pre-configured16:59
SamYapleto bring the contaienrs in line with kolla images we really need to build our own (for things like COPY_ONCE and the like)17:00
harmw^^ yep17:00
britthouserok, I wasn't aware of those, only that RH now provides some as part of atomic.  They might be the same thing though17:00
*** dslevin_ has joined #openstack-meeting-417:00
akwasnieansible command is not available in kolla_docker, which force us to decide if we want to drop official images in favor of possibility of using configuration file (mechanism provided in kolla base image)17:00
inc0or we could implement it into kolla_docker17:01
inc0how hard is it?17:01
SamYapleakwasnie: adding the 'command' thing is no problem17:01
SamYaplebut do we want to is teh question17:01
*** Sukhdev has quit IRC17:01
harmwcan we tell official images which config file to load? if not, we should build our own17:01
SamYaplei want to keep our images in line with all the other structure (config.json COPY_ONCE etc)17:02
sdakei am in favor of using our own images for all kolla-specific things17:02
*** kebray has joined #openstack-meeting-417:02
akwasnieharmw: we can, but only using command,17:02
sdakeso the quesetion is, is anyone NOT in favor of using our own images?17:02
sdakeif someone is not in favor, then we need to see if that is a majority or not17:02
pbourke_+1 for using our own17:02
sdakebecause as stands now, we will be proceeding with our own images17:03
Jeffrey4l+1 for using ours.17:03
sdakebut we rule by majority ;)17:03
pbourke_the dockerhub ones strike me as more general purpose, it seems common enough to craft customs17:03
britthouserYeah our own makes sense. maybe we should have a test to use of when we'll use our own vs use others.17:03
harmw+1 (I can even help in this area, yay)17:03
SamYaple+117:03
akwasnie+1 :)17:03
nihilifer+117:03
rhalliseyseems fine with me though I don't quite understand what 'our images' are17:04
akwasnierhallisey, own dockerfiles17:04
harmwimages Kolla depends on/uses17:04
harmw?17:04
elemoineI guess extending kolla_docker when needeed makes sense too17:04
rhalliseywell what is changing then?17:04
akwasniefor example we use logstash official image from dockerhub, and if we want to drop official ones we have to create own configuration in dockerfiles17:05
pbourke_rhallisey: not much, but they follow our conventions17:05
sdakerhallisey  we were in the past trying to use standard elkstack provided images for docker things17:05
sdakenow we are not ogin to do that, we are going to roll our own that fit our API for start extension, config, etc17:05
rhalliseyoh I get it17:05
rhalliseykk cool17:06
inc0more work but we have control over it17:06
SamYaplemore uniform too. less code to know and understand17:06
inc0we won't run into same type of problems as we ran into with ansible+docker17:06
SamYapleon the deploy side that is17:06
sdakeinc0 frankly I think our team is of the size we can handle the work17:06
*** annilai has joined #openstack-meeting-417:06
inc0yeah, I think we can use dockerfiles from dockerhub as reference17:07
*** trumpetsherald has quit IRC17:07
inc0which means it will be even easier17:07
jpeelerexactly ^17:07
jpeeleri don't see this as big deal17:07
harmwI have containers for EFK already :)17:07
akwasniei can do it as a part of my work in ELKs blueprint17:07
harmwso adding in Kolla stuff should be fairly easy17:07
sdake#topic log processing engine bssed on Hek17:07
*** openstack changes topic to "log processing engine bssed on Hek (Meeting topic: kolla)"17:07
*** vtech has quit IRC17:07
sdakeelemoine I am not familiar with Hek, can you give us a quick overview?17:08
sdakekeep in mind we have about 12 minutes for this opic17:08
sdaketopic17:08
elemoinelet me introduce myself first17:08
elemoinemy name is Eric Lemoine, I work for Mirantis17:08
elemoineas a developer in the logging/monitoring team17:08
elemoineI've joined Mirantis 2 months ago, and I've been following Kolla since then (and I like it :)17:09
SamYapleHi Eric17:09
elemoineso17:09
rhalliseyhi17:09
sdakewelcome aboard ;-)17:09
pbourke_o/17:09
elemoinethanks17:09
harmwhi17:09
akwasniehi17:09
elemoineI just wanted to mention here that we (my team) are considering working on a blue print for Kolla17:09
elemoineproposing a scalable log processing solution based on Heka17:10
*** banix has joined #openstack-meeting-417:10
elemoinethis will build on the ELK work we just discussed17:10
SamYaplesince we have no solution for log processing, i think anything you propose that you will work on (that works) will be fine with us elemoine17:10
sdakeso not supplant elk, but be in addition to?17:10
elemoinethe blueprint will include more information, but I just wanted to know if people agreed with the general intent17:11
*** prithivm has quit IRC17:11
harmwwhere exactly does it fit in the ELK picture?17:11
elemoinesdake, good question17:11
sdakewhat is Heka17:11
inc0elemoine, whats hek?17:11
inc0heka17:11
elemoinewe also use Elasticsearch and Kibana17:11
elemoinebut use Heka instead of Logstash17:12
inc0how Heka is better than Logstash?17:12
inc0what are differences?17:12
nihiliferit's written in go :P17:12
harmwI use fluentd, so wondering the same as inc0 here :)17:12
elemoineand the architecture we want to propose is a bit different that the one based on Logstash17:12
akwasnieso basically you want to ELK -> EHK ?17:12
inc0akwasnie, yeah17:12
*** Prithiv has quit IRC17:12
elemoinewe think Heka is lightweight and can run on every node, for a distributed architecture that scales17:13
sdakesounds like a topic for midcycle discussion I think17:13
inc0so I'm not philosophically bound to logstash17:13
elemoinecool, that's what I wanted to know17:13
inc0we just threw a name, I don't think anyone else is, so it might be good to consider heka underneath17:13
inc0I would be -1 on having both17:13
sdakeunfortunately midcycle is 1 month out17:13
elemoineI could provide more details, but this is what the blueprint will be about17:13
*** stanchan has joined #openstack-meeting-417:13
sdakeelemoine a mailing list mail would be good or ya a detailed blueprint17:14
harmwI'm interested in this elemoine, please inform us with the BP :)17:14
inc0elemoine, so could you please provide good comparason between these two so we could decide on better one?17:14
elemoineI already started on the blueprint doc17:14
sdakeas in why this logstash repacement is necessary17:14
elemoineit should be ready soon17:14
britthouserdoes heka exist already, and we just want to integrated in Kolla, or heka is what you are writing?17:14
sdakewhat I dont wan tto do is introuce a bunch of chnge in our plan here for no good reason :)17:14
harmwand which crap in logstash it tries to fix17:14
elemoinethe doc will discuss Heka vs Logstash and why we use and want to propose Heka17:15
*** gjayavel_ has quit IRC17:15
harmw+117:15
sdakewho writes heka - mirantis?17:15
inc0also talk with akwasnie as she did fair amount of work on integrating logstash17:15
elemoineHeka is maintained by Mozilla17:15
*** seanmurphy has quit IRC17:15
sdakecool17:16
elemoineyes, I obviously want to talk to akwasnie about it17:16
sdakewell lets get an A/B comparison of Heka vs logstash on the mailing list as a fist step17:16
akwasniesure, will help17:16
akwasnieif you want :)17:16
*** neelashah has quit IRC17:16
sdake#action elemoine to post A/B comparison of Heka vs Logstash on the mailing list17:16
elemoinesure I'll write to the mailing list17:16
SamYapleall i know is there can be only one!17:16
sdakeyes, we need one, so lets make the best choice17:16
elemoineok, clear on that, and I agree with you17:16
elemoinewhat's important is the architecture we want to propose (for scaling)17:17
*** galstrom is now known as galstrom_zzz17:17
*** piet has joined #openstack-meeting-417:17
elemoinewe think that Logstash is a major bottleneck in the current architecture17:17
sdakemore theoretical scaling work17:17
* sdake groans17:17
elemoineso it's not only about the software17:17
harmwlogstash has issues, yes17:17
elemoineit's about the architecture17:18
elemoinea diagram will help17:18
elemoine:)17:18
sdakeok well lets start small with an A/B comparsion of logstash vs heka17:18
sdakebefore diving in to the architecture17:18
sdakeyou can follow up the on the ml with an architecture proposal chagne ifyou want :)17:18
elemoinehmm both are a bit mixed17:18
elemoinebut ok17:18
SamYaplewell do it the best we can17:18
elemoinecool17:18
sdakeok well do whatever yo ucan to get the information shared17:19
sdakebut lets do it on the mailing list at first pelase17:19
elemoinethat's all for me, I just wanted to let you know about my intent17:19
elemoinesdake, sure17:19
sdakecool welcome to the party :)17:19
elemoinethx again17:19
sdake#topic open discussion17:19
*** openstack changes topic to "open discussion (Meeting topic: kolla)"17:19
sdakefirst up is me :)17:19
*** salv-orlando has quit IRC17:19
sdakethe midcycle will include invitations for the regular event as well as dinner17:19
sdakeplease RSVP for dinner so I can get an accurate count17:20
sdakedinner is hosted by Cisco17:20
SamYapleRSVP17:20
*** salv-orlando has joined #openstack-meeting-417:20
*** kebray has quit IRC17:20
sdakelunch + the regular midcycle are hosted by Servosity17:20
sdakebreakfast is hosted by your PTL :)17:20
sdakewe are having bruegers bagels - yay :)17:20
SamYaplethere is coffee outside the office17:20
sdakeok that is all, please rsvp17:21
SamYaplei have one thing17:21
britthouserthere will be a link for RSVP?17:21
sdakecool well this comes with bagels and stuff17:21
britthouserI didn't miss it did I?17:21
sdakebritthouser  yes its coming17:21
sdakebefore week is out17:21
sdakei was workig non budget + logistics17:21
sdakeorganizign a midcycle is harder then it looks ;)17:21
britthouserok I'll watch for link17:22
britthouser=)17:22
SamYapleOk. so we now have pull playbooks17:22
pbourke_were upgrades brought up today?17:22
SamYaplepbourke_: yes17:22
pbourke_ok I'll check logs17:22
sdakesam is up first, pbourke up second17:22
sdake8 minutes guys share the time please :)17:22
SamYaplewith the pull playbooks you can prestage all the images. `kolla-ansible pull` instead of `kolla-ansible deploy`17:22
pbourke_that is nice17:23
SamYaplethat means you can test true multinode deploy time without the registry being a factor17:23
*** stanchan has quit IRC17:23
sdakecool and that preloads the docker images?17:23
SamYapleonly two reviews on this left, https://review.openstack.org/#/c/263861/ and https://review.openstack.org/#/c/263863/17:23
SamYaplesdake: yes17:23
sdakefantastic17:23
sdakeSamYaple  i will review now17:23
SamYaplei image it will also be useful during upgrade, prestage upgrade images17:23
sdakethat soundss like a killer feature17:23
SamYaplethat way down time is just a restart away17:23
sdakeye sthis will bbe huge for upgrades17:23
SamYapleanyway that was my thing, so everyone is aware17:24
sdakeso its kolla-ansible-pull - is it integrated with our shell tool?17:24
SamYaplesdake: it is17:24
sdakenice17:24
SamYapleinstead of deploy do pull17:24
sdakethat code is a bit long in the tooth :)17:24
inc0upgrades message: plese review and test: end of message17:24
SamYaple(if you do it know it will break kinda before you merge those patches17:24
SamYaple)17:25
sdakepbourke_  your up17:25
SamYapleanyway that was my thing17:25
pbourke_I just wanted to check what the status was on upgrades from inc0 but I think he pretty much summed it up!17:25
pbourke_inc0: do we just have keystone right now?17:25
inc0pbourke_, close17:25
sdakeinc0 can you give us a 3-4 minute tldr on upgrade status17:26
SamYaplepbourke_: keystone and nova POC17:26
*** kebray has joined #openstack-meeting-417:26
inc0we had till we moved to kolla_docker17:26
sdakeI am also very interested17:26
*** cloudtrainme has quit IRC17:26
inc0we need to rebase it, but that should be simple enough17:26
inc0we have nova up as well17:26
SamYapleinc0: ill do that real quick17:26
inc0with general logic17:26
sdakeinc0 3 minutes for state of ugprade please :)17:26
inc0but we changed few things in keystone and nova will have to follow17:26
sdakeshould have been in regular agenda - my apologies17:26
inc0so important thing is to get keystone merged asap17:27
inc0so we'll have solid schema for rest of plays17:27
pbourke_i'll try give that a burn tomorrow17:27
sdakeinc0 after meting post links for review in #kolla17:27
inc0and we can proceed with other projects17:27
inc0ok17:27
inc0and my request17:27
sdakeso the status is your just getting started with keystone?17:27
inc0I don't think I'll handle every project myself17:27
inc0so if anyone feel like helping, I'll gladly accept17:27
*** vmahe has quit IRC17:27
sdakeinc0 we wil ldistribute this like the drop root thing17:27
sdakelets sycn up after the meeting  to get the blueprint into the right shape and i'll post a call for help17:28
nihilifermaybe by working items on blueprint?17:28
inc0we have bps per service up thanks to rhallisey17:28
inc0so feel free to take on it17:28
*** avarner has joined #openstack-meeting-417:28
nihiliferah, ok17:28
sdakei think we need owkring items for this17:28
sdakeand close out the blueprints17:28
inc0just, let's first merge keystone17:28
inc0so everyone will have base to follow17:28
sdakeinc0 lets sycn up after the meeting and figure out best way to get the work distributed17:28
sdakeinc0 agreed17:28
inc0ok, thanks17:29
inc0that's it from me17:29
pbourke_cheers inc017:29
inc0I'll post links17:29
sdakeour new way of distributing work is work items - it worked well for drop root17:29
sdakeand kept all hte info in one place17:29
* nihilifer took neutron ;)17:29
SamYapleok upgrade keystone rebased take a look at https://review.openstack.org/#/c/25756817:29
sdakeok times out17:29
sdakethanks for coming folks17:29
inc0cyas17:30
sdakebig turnout ;) _ hopefully we see this many folks at the midcycle17:30
rhalliseybye17:30
pbourke_so long17:30
akwasniethanks bye17:30
elemoinethanks, talk next week17:30
nihiliferbye17:30
SamYaplebyw17:30
Jeffrey4lbye17:30
*** rhallisey has left #openstack-meeting-417:30
ajafobye17:30
sdake#endmeeting17:30
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:30
openstackMeeting ended Wed Jan  6 17:30:32 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-01-06-16.32.html17:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-01-06-16.32.txt17:30
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-01-06-16.32.log.html17:30
*** vtech has joined #openstack-meeting-417:31
*** sridhar_ram has joined #openstack-meeting-417:32
*** cloudtrainme has joined #openstack-meeting-417:33
*** alexstav has left #openstack-meeting-417:34
*** neelashah has joined #openstack-meeting-417:35
*** yamahata has quit IRC17:42
*** iyamahat has quit IRC17:44
*** gjayavelu has joined #openstack-meeting-417:48
*** Jeffrey4l has quit IRC17:49
*** spotz is now known as spotz_zzz17:49
*** bharathm has quit IRC17:52
*** cloudtrainme has quit IRC17:53
*** cloudtrainme has joined #openstack-meeting-417:56
*** iyamahat has joined #openstack-meeting-417:58
*** spotz_zzz is now known as spotz17:58
*** Swami has quit IRC18:00
*** yamahata has joined #openstack-meeting-418:05
*** neelashah has quit IRC18:08
*** salv-orlando has quit IRC18:08
*** salv-orlando has joined #openstack-meeting-418:09
*** ihrachys has quit IRC18:10
*** balajin has joined #openstack-meeting-418:11
balajinyo, sorry i am late18:11
*** gjayavelu has quit IRC18:13
*** daneyon has joined #openstack-meeting-418:14
*** dslevin_ has quit IRC18:14
*** daneyon_ has joined #openstack-meeting-418:15
*** stanchan has joined #openstack-meeting-418:16
*** jwagner_wfh is now known as jwagner_lunch18:18
*** daneyon has quit IRC18:19
*** zehicle has quit IRC18:19
*** bharathm has joined #openstack-meeting-418:20
*** dslevin_ has joined #openstack-meeting-418:22
*** Swami has joined #openstack-meeting-418:25
*** stanchan has quit IRC18:33
*** macsz1 has joined #openstack-meeting-418:36
*** akwasnie has quit IRC18:36
*** macsz has quit IRC18:36
*** zehicle has joined #openstack-meeting-418:37
*** bharathm has quit IRC18:38
*** stanchan has joined #openstack-meeting-418:39
*** macsz has joined #openstack-meeting-418:39
*** rockyg has joined #openstack-meeting-418:41
*** macsz1 has quit IRC18:42
*** bharathm has joined #openstack-meeting-418:44
*** armax has quit IRC18:46
*** paul-carlton2 has quit IRC18:50
*** fawadkhaliq has quit IRC18:50
*** krtaylor has quit IRC18:53
*** gjayavelu has joined #openstack-meeting-418:54
*** vhoward has quit IRC18:55
*** vhoward has joined #openstack-meeting-418:56
*** trumpetsherald_ has joined #openstack-meeting-418:58
trumpetsherald_I’m I in the right place / time for the os ops meeting?19:02
*** prashantD has quit IRC19:02
rockyg++19:02
*** paul-carlton2 has joined #openstack-meeting-419:03
*** prashantD has joined #openstack-meeting-419:05
trumpetsherald_Cool, I’m Nathaniel Kimball btw19:05
trumpetsherald_I use this handle just about everywhere so it should be easy to decode19:05
*** cloudtrainme has quit IRC19:06
*** SimonChung has joined #openstack-meeting-419:06
*** piet has quit IRC19:06
*** bpokorny has quit IRC19:06
*** fawadkhaliq has joined #openstack-meeting-419:06
*** krtaylor has joined #openstack-meeting-419:07
*** neelashah has joined #openstack-meeting-419:08
rockygcool.  I'm Rocky Grober.  Had my nick on IRC for at least two decades.19:09
rockygI think we might be on the non meeting alternating week.19:09
rockygbalajin, are you out there?19:10
rockygJJ doesn't seem to be here, though19:10
*** galstrom_zzz is now known as galstrom19:10
trumpetsherald_Yeah this would be an even week19:11
rockygbut we're a cool little group19:11
trumpetsherald_my bad, looks like the 13th is the next one19:11
rockygNot a problem.  There is also some strangeness with the calendars because there were 53 weeks last year.19:12
rockygAt least for how weeks are counted by the calendar programs19:12
balajini am here19:12
balajinjust messed up with my time / date19:12
trumpetsherald_Looks like the ICS file is not accurate http://eavesdrop.openstack.org/#OpenStack_OSOps/Monitoring_and_Tools_Working_Group19:13
trumpetsherald_hence my confusion19:13
*** neelashah1 has joined #openstack-meeting-419:13
*** fawadkhaliq has quit IRC19:13
rockygYeah.  The calendar thing19:14
*** galstrom is now known as galstrom_zzz19:14
*** neelashah has quit IRC19:14
*** gjayavelu has left #openstack-meeting-419:14
rockygso, meeting or no this week?19:15
*** cloudtrainme has joined #openstack-meeting-419:16
trumpetsherald_pretty sure no19:17
trumpetsherald_agenda is for next week on the 13th19:17
*** paul-carlton2 has quit IRC19:17
*** bharathm has quit IRC19:18
rockygcool.  Thanks.  I'm gonna get my ass to work so I can do the log wg meeting19:18
rockygSee you next week!19:18
trumpetsherald_sure thing, ciao19:18
*** trumpetsherald_ has left #openstack-meeting-419:18
*** bharathm has joined #openstack-meeting-419:20
balajinlater folks19:22
balajincia19:22
*** balajin has left #openstack-meeting-419:22
*** piet has joined #openstack-meeting-419:22
*** rockyg has left #openstack-meeting-419:23
*** piet has quit IRC19:23
*** piet has joined #openstack-meeting-419:24
*** seanmurphy has joined #openstack-meeting-419:26
*** jwagner_lunch is now known as jwagner19:26
*** seanmurphy has quit IRC19:26
*** bharathm has quit IRC19:31
*** macsz1 has joined #openstack-meeting-419:31
*** harshs has joined #openstack-meeting-419:33
*** macsz has quit IRC19:34
*** bharathm has joined #openstack-meeting-419:37
*** annilai has quit IRC19:40
*** kebray has quit IRC19:43
*** gjayavelu has joined #openstack-meeting-419:45
*** gjayavelu has quit IRC19:45
*** Sukhdev has joined #openstack-meeting-419:46
*** dslevin_ has quit IRC19:47
*** dslevin_ has joined #openstack-meeting-419:52
*** pmesserli has quit IRC19:53
*** bharathm has quit IRC19:55
*** baoli_ has quit IRC19:57
*** bharathm has joined #openstack-meeting-419:59
*** javeriak has quit IRC20:07
*** baoli has joined #openstack-meeting-420:10
*** AlanClark has quit IRC20:11
*** stanchan has quit IRC20:11
*** bharathm has quit IRC20:12
*** krtaylor has quit IRC20:13
*** cloudtrainme has quit IRC20:15
*** bharathm has joined #openstack-meeting-420:17
*** belmoreira has joined #openstack-meeting-420:22
*** stanchan has joined #openstack-meeting-420:22
*** jmckind_ has joined #openstack-meeting-420:24
*** jmckind has quit IRC20:26
*** prashantD has quit IRC20:38
*** armax has joined #openstack-meeting-420:40
*** prashantD has joined #openstack-meeting-420:41
*** krtaylor has joined #openstack-meeting-420:43
*** rocky has joined #openstack-meeting-420:46
*** vtech has quit IRC20:47
*** matrohon has joined #openstack-meeting-420:47
*** rocky_g has joined #openstack-meeting-420:48
*** baoli has quit IRC20:48
*** rocky has left #openstack-meeting-420:50
*** vishwanathj has joined #openstack-meeting-420:56
rocky_ganyone here for logging besides jokke_ ?20:56
*** baoli has joined #openstack-meeting-421:00
rocky_gstartmeeting log_wg21:01
rocky_g#startmeeting log_wg21:01
openstackMeeting started Wed Jan  6 21:01:27 2016 UTC and is due to finish in 60 minutes.  The chair is rocky_g. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** openstack changes topic to " (Meeting topic: log_wg)"21:01
openstackThe meeting name has been set to 'log_wg'21:01
rocky_gHi folks!21:02
*** macsz1 has left #openstack-meeting-421:02
rocky_ganyone here for logging?21:03
*** stanchan has quit IRC21:03
*** rbradfor has joined #openstack-meeting-421:04
rocky_gjokke_, you here?21:04
*** iyamahat has quit IRC21:04
*** Sukhdev has quit IRC21:05
rbradforrocky_g, hi21:05
rocky_gHey!21:05
rocky_gT#topic default config options for logging21:05
rocky_gI've been following the discussion, but need some clarification21:06
*** bharathm has quit IRC21:06
rbradforis this a ML discussion?21:07
rocky_gsupposedly the devstack config options are friendlier to humans, but do they scale for large installations?21:07
rocky_gIt is the one you started21:07
rbradforok21:07
*** spzala has joined #openstack-meeting-421:08
rbradforsure, this means devstack can change the logging_user_identity_format configuration option, to use names rather then ids21:09
*** stanchan has joined #openstack-meeting-421:09
rbradforbut the context and no context format strings are returned to defaults.21:10
rocky_gright.  but names can have duplicates, can't they?21:10
*** stanchan has quit IRC21:10
*** stanchan has joined #openstack-meeting-421:10
rbradforwithin a given project I hope not.21:11
rbradforwhere a user can be a duplicate in project/domain/tenant I am unsure of21:11
rocky_gah.  Then as long as the user_name:project_name tuple is there, it should be unique?21:11
*** baoli has quit IRC21:12
rbradforthe user_identity is defined as "%(user)s %(tenant)s %(domain)s %(user_domain)s %(project_domain)"   5 identifying attributes21:12
*** baoli has joined #openstack-meeting-421:13
rocky_gThat seems like a better option.  More verbose, but then Ops just changes if its too much info.  But better for large installations21:13
rbradforwhat do large installations use now.  I would be interested in knowing the configuration actually used on a site.21:14
rocky_gwe should start the discussion on the openstack-ops mailing list and see what replies we get.  We can also go to the large installation ops meeting and ask there/put it on their agenda.21:15
rbradforI want to work with submitting a devstack patch on changing the right logging configuration variable.  This needed https://review.openstack.org/#/c/261122/ which is now merged21:17
*** kragniz is now known as {^-^}21:17
*** {^-^} is now known as Guest4635321:18
*** Guest46353 is now known as kragniz21:18
rocky_gThe more default settings ops can use, the better as the configs get dynamically generated for new releases, then have to be reconciled during an upgrade.  And yeah, that requirements change is really important21:19
rocky_gAny suggestions on how to stay on top of when to change that version?21:20
*** bharathm has joined #openstack-meeting-421:21
rbradforthe change of oslo.log in global requirements should be already in projects. I've not verified21:21
rocky_gIt's automatic.  It's merged, so the builds all happen with the new value.  Being tested every gate run21:21
rocky_gUnless a project has specifically set it in their own requirements, and they shouldn't21:22
*** baoli has quit IRC21:24
*** baoli has joined #openstack-meeting-421:25
rocky_gHave you walked through the process of how the config files are generated for a build?  there is a ml discussion on that wrt Cinder happening now/last few days21:25
rbradforare you referring to the oslo-config-generator21:26
* rbradfor looking for ML discussion21:26
rbradfor#link http://lists.openstack.org/pipermail/openstack-dev/2016-January/083280.html21:27
rocky_gAh, thanks.21:27
*** julim has quit IRC21:27
rbradforcoming from prior experience (and not seeing a production OS system to validate), I do not like what I've seen about configuration generation and information about the configuration options.21:29
*** belmoreira has quit IRC21:29
rbradforI have yet to confirm, but I suspect the oslo-config-generator sets configurations options, or some of them, rather then comments of options.21:29
rbradforand so, an option is set, when indeed it's value is the system default.21:30
rocky_gNope.  The documentation is very poor and the generation has to happen via running tox21:30
rbradforI would (with my operator hat on), not what to see that in a config file, as it's clutter.21:30
rbradforthe second problem is, what are the configuration options of a service running now, or when it started.21:30
rocky_gYup.  One of the things the log wg wants to fix.  Once we figured out the issue21:31
rbradforeven the logging (when in DEBUG) does not log if a configuration option value is a default, or specified in a config file.21:31
rocky_gPoor ops have to go project by project to collect the options.  But, I think there is a cli for some of the projects to show current options21:32
rbradforgenerating a configuration file from source each release is I feel a brute force approach and as you point out, likely a more difficult upgrade approach21:32
rocky_gYup.  The projects used to generate sample config files, but couldn't keep them up to date.21:32
rbradforI have no yet researched, but the oslo reports guru meditation report is how a project can obtain this.21:32
rocky_gOh, there is a review on the config stuff, lemme find it.21:33
*** baoli has quit IRC21:36
rocky_garg!  still looking.  It's the dynamic config changes one21:37
*** baoli has joined #openstack-meeting-421:37
*** kebray has joined #openstack-meeting-421:38
rocky_goh, right.  checking wrong project.  just a sec...21:38
rocky_g#link https://review.openstack.org/#/c/251471/21:39
*** bharathm has quit IRC21:40
rbradforthis review is part of a larger discussion to enable reloading a config file to change just the overall logging level21:41
rocky_gAnd your up to speed on it.21:41
rocky_gnot just logging, but logging is the POC.  It will expand to all mutable options21:42
rocky_gBut what a pain to have to go project by project.21:42
rocky_gthere really needs to be a global config file.  That would reduce the size of project config files tremendously21:43
*** alexstav has joined #openstack-meeting-421:43
rocky_gAnd improve consistency across projects21:43
rbradforI am aware of the issues about reloading config files (ie. what's now defined and changed, and is or is not mutable), how is correctly triggered, how individual projects will need to change in order to enable this capability21:43
*** bharathm has joined #openstack-meeting-421:43
*** vhoward has quit IRC21:44
rbradforI would agree that a single common view of a "product" configuration is definitely important, but, there is a lot of issues in maintaining compatibility.21:44
rbradforI have not seen anybody push for using a global configuration file initially.21:45
rocky_gQuestion:  if there are changes needed within the projects, do all projects need to change?  And, if so, would it make sense to propose the global config file cascading to the project configs? to get done around the same time?21:45
rbradforadding [some] logging options to said file may be useful.21:45
rbradforthe issue with implementing the mutable capability is the loading/reloading of a configuration file, and maintaining backwards compatibility.21:46
rocky_gThe ops guys would love to be able to set the log format in one place.  And often the levels.  But until the levels are the same across all projects, it's hard to get the levels right.21:47
rbradforin my interpretration, when implemented a project must elected to enable having mutable options, and change this.21:47
*** dtardivel has quit IRC21:47
rocky_gThe mutable changes will be really hard with the multiple locations of config options.  How do you know when you've got them all, or do you list the projects you want the change for?21:48
rbradforin one regard I would agree with you, but if the global level was INFO, in a new global config,  and you wanted just DEBUG in nova,  you need to add that now to nova config and reload.  I think in theory this is a use case, it's just how to implement it that seems complex21:48
rocky_gAgreed.  But the implementation is hard because of the lack of federation across the projects.21:49
rbradforthe "concept" of a mutable option needs to first be implemented in code.21:49
rbradforthe choice of what options can then become "mutable" needs to happen across projects.21:50
rocky_gYeah.21:50
rbradforif it's say an Oslo Logging option, and Oslo logging is used by project, then that's sort of global.21:50
rbradforI suspect nobody may know what are the configuration options taxomony across all projects, and where can/should consolation occur.21:51
rbradforwe are only talking about a dozen logging options.21:51
*** baoli has quit IRC21:51
rocky_gThat's where I would like to start with global config options.  Start with all the oslo config options and defaults in one file or directory.  Then overlay the project specific options/defaults.  once we have that, we can start removing dupes in projects21:52
rocky_gAnd the config options are poorly documented for many of the projects.21:52
rbradforhas any work or discussion happened on global config files.21:52
*** baoli has joined #openstack-meeting-421:53
*** armax has quit IRC21:53
*** matrohon has quit IRC21:53
rbradforI concur *developer* documentation I have observed is poor. What I saw of *operator* docs was just as confusing.21:53
rbradforeven if the docs had a "global section", i.e. these options are in each project, would simplify the docs21:54
rocky_gNo.  Not even raised yet.  If we put together a spec and got some comments on it, we could have a summit session and target N for phase 121:54
*** kebray has quit IRC21:54
rocky_gYup.  I started that conversation with the docs ptl.  She's up for something like that.21:54
*** kebray has joined #openstack-meeting-421:55
*** baoli has quit IRC21:55
rocky_gAnd providing that info would go a long way in helping the ops guys and even the devs get a handle on what is the same and what is special per project21:55
*** baoli has joined #openstack-meeting-421:55
*** bharathm has quit IRC21:56
rocky_gQuestion:  would starting with the Nova opts documentation as a template/talking point be a good way to approach the docs team about the global stuff?21:57
rbradforI'm sure getting one project to adopt improvements makes it easier to persuade other projects.21:58
rbradforDo you know who is responsible for Nova docs.21:58
* rbradfor looking for actual link to reference21:59
rocky_gIt's the nova team.  There may be some dev folks that specifically focus on the docs, and there my be some specialists in the docs team, but I think it's project by project how docs are created.21:59
rbradforare you referring to http://docs.openstack.org/liberty/config-reference/content/list-of-compute-config-options.html22:00
rocky_gOslo has doc sprint days to add info.  It helped a lot from Kilo to Liberty.  But mostly it went into dev docs.22:00
rbradforI also have found http://docs.openstack.org/openstack-ops/content/logging_monitoring.html but this does not seem to refer to configuration22:01
*** bharathm has joined #openstack-meeting-422:01
rocky_gyp.  the first.22:01
rocky_gthe ops stuff is stuff generated by operations people.22:01
*** baoli has quit IRC22:01
rocky_gsorry.  No, it's not.22:02
*** baoli has joined #openstack-meeting-422:02
rocky_gThe config stuff is all supposed to be in the config-reference22:02
rbradfor#link http://docs.openstack.org/liberty/config-reference/content/list-of-compute-config-options.html22:02
rbradfor#link http://docs.openstack.org/liberty/config-reference/content/keystone-configuration-file.html22:02
rocky_gYou can see that there is huge variation project to project22:02
*** gjayavelu has joined #openstack-meeting-422:02
*** vishwana_ has joined #openstack-meeting-422:03
rbradforexamples of logging_context_format_string configuration for exmaple that is duplicated in config-reference, when ideally it should be a single source.22:03
*** woodard_ has joined #openstack-meeting-422:03
rocky_glink http://docs.openstack.org/liberty/config-reference/content/section_volume-misc.html22:03
rocky_gBut they also have a config files section, which may have more stuff22:04
*** baoli has quit IRC22:04
rocky_gSo, each project *should* have a section, but they're not consistent22:04
*** Kevin_Zheng_ has joined #openstack-meeting-422:04
*** raofei has quit IRC22:04
*** Kevin_Zheng has quit IRC22:04
*** bradjones has quit IRC22:04
*** dingboopt has quit IRC22:04
*** Kevin_Zheng_ is now known as Kevin_Zheng22:04
*** woodard has quit IRC22:04
*** bradjones has joined #openstack-meeting-422:04
*** bradjones has quit IRC22:04
*** bradjones has joined #openstack-meeting-422:04
*** baoli has joined #openstack-meeting-422:04
*** Swami has quit IRC22:04
*** _ag has quit IRC22:04
*** _ag has joined #openstack-meeting-422:05
*** Swami has joined #openstack-meeting-422:05
*** vishwanathj has quit IRC22:05
*** markvan has quit IRC22:05
*** junjie has quit IRC22:05
*** dougwig has quit IRC22:05
*** dingboopt has joined #openstack-meeting-422:05
rbradforthere needs to be a central body that need to set and enforce project consistency, looking at configuration files when I first installed a working OS showed there is no consistency (and for operators this must be very frustrating)22:05
*** markvan has joined #openstack-meeting-422:05
rocky_gYup.22:05
*** bharathm has quit IRC22:06
rocky_gI can maybe help drive some of it from the docs side.  But, maybe we should bring it up in cross-project meeting?22:06
*** raofei has joined #openstack-meeting-422:07
rocky_gI was also thinking that the Nova-API wg really should be the OpenStack-API wg and should apply across all projects22:07
*** junjie has joined #openstack-meeting-422:07
rbradforI feel there needs to be a use case, i.e. a collection of production operators supporting a request to standardize.22:07
*** angdraug has joined #openstack-meeting-422:07
rbradforbut I suspect one needs to first suggest to operators some examples, get feedback, and then take to the cross-project meeting, which then lead to a ML (dev) discussion22:08
rocky_gI can put together a user-story for the prod-wg and get it in and discussed.22:08
*** bharathm has joined #openstack-meeting-422:08
*** salv-orl_ has joined #openstack-meeting-422:09
rocky_gThe logging issues, the config issues, all trace back to the same root.22:10
*** baoli has quit IRC22:10
rocky_gAnd the Ops folks hit it first.22:10
rocky_gThe whole consistency thing is also where a real QA team would have focused on early.22:11
*** piet has quit IRC22:11
rbradforthe history is well history. what is important is where to start to produce consistency, and what key projects need to be onboard.22:11
*** salv-orlando has quit IRC22:12
rocky_gthe core:  nova, glance, cinder, keystone, neutron (would be nice to have swift, but not likely)22:12
rbradforI have not investigated nova in any detail, but is this the largest driving project for improvements like this22:12
rocky_gIt's also a good internship project, discovering current state including duplications22:13
rocky_gnova currently has a good core team, and a good number of cores who will understand the issues when presented.22:13
rocky_gand a good ptl22:13
rocky_gOslo needs more bodies.22:14
rbradforand what operators do you feel are a good voice22:14
rocky_gNeutron is too young and scattered.22:14
rocky_gKeystone could also do it.22:14
rocky_gSo, I would think a good approach would be to:  get all the oslo config opts and defaults identified/documented, then approach Nova and Keystone to work together.22:16
rocky_gThere are a number of ops folks who might work.  JJ Asghar, some of the Jessies, K Lindgren...22:17
rocky_gA few more.22:17
*** dougwig has joined #openstack-meeting-422:17
rocky_gJim Meyers might also be able to help.22:17
rocky_gThe rackspace guys, the comcast guys and the godaddy guys really would love to see improvements.22:18
rocky_gThose teams will help with the work.  JJ, some of the infra guys and one or two other Ops guys could be the voice.22:19
rocky_gJeremy Stanley.  Or whoever wrote infra's log parsing rules.22:20
rbradforI have heard and read a lot from the "developer" side, but I would like to hear it from operators.  Our top goal should be X first, how do we get that in the next release. With no contact I do not know what X is.22:20
rocky_gThat's why you should come to the Ops Midcycle ;-)22:20
rocky_gOh, a great voice for ops is Tom Fifield.  He's the foundation ambassador to those folks and the community manager.22:21
rbradforIs it first standardizing the values of a subset of config options (i.e. logging), ensuring it's clearly documented in developer/operations (not duplicated), and confirmation based on what operators actually use in production systems today.22:21
rocky_gAnd he might get you access to a working cloud or two.22:21
*** jmckind_ has quit IRC22:22
*** baoli has joined #openstack-meeting-422:22
*** dims has quit IRC22:22
rocky_gAlso, Tom knows who to reach out to.22:24
*** Sukhdev has joined #openstack-meeting-422:24
rocky_gSo, I'm gonna end this meeting, just about a half hour late.  But, we have the log.22:26
rocky_gAny last words you want recorded?22:26
rbradforas I get a better understanding of things it would be good to be introduced. I'm doing code cleanup and working the developer docs at present. I would like to see how to get information into the right operator docs, because operators should not need to look at deveoper docs22:26
rbradforI changed the wiki page to reflect the meeting time.22:26
*** inc0 has quit IRC22:27
rbradfor#link https://wiki.openstack.org/wiki/Meetings/log-wg   now 21:00 UTC22:27
rocky_gThanks!22:27
rocky_g#endmeeting22:28
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:28
openstackMeeting ended Wed Jan  6 22:28:15 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:28
openstackMinutes:        http://eavesdrop.openstack.org/meetings/log_wg/2016/log_wg.2016-01-06-21.01.html22:28
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/log_wg/2016/log_wg.2016-01-06-21.01.txt22:28
openstackLog:            http://eavesdrop.openstack.org/meetings/log_wg/2016/log_wg.2016-01-06-21.01.log.html22:28
*** baoli has quit IRC22:28
*** neelashah1 has quit IRC22:29
*** cloudtrainme has joined #openstack-meeting-422:36
*** alexstav has quit IRC22:42
*** alexstav has joined #openstack-meeting-422:43
*** alexstav has quit IRC22:48
*** jmckind has joined #openstack-meeting-422:49
*** gjayavelu has quit IRC22:49
*** bpokorny has joined #openstack-meeting-422:49
*** krtaylor has quit IRC22:51
*** baoli has joined #openstack-meeting-422:52
*** dims has joined #openstack-meeting-422:53
*** bharathm has quit IRC22:54
*** baoli has quit IRC22:56
*** baoli has joined #openstack-meeting-422:57
*** mhayden has quit IRC22:57
*** banix has quit IRC23:01
*** bharathm has joined #openstack-meeting-423:02
*** trozet has quit IRC23:02
*** spotz has quit IRC23:04
*** j^2 has quit IRC23:04
*** dims has quit IRC23:04
*** j^2 has joined #openstack-meeting-423:06
*** spotz has joined #openstack-meeting-423:07
*** bharathm has quit IRC23:07
*** jmckind has quit IRC23:08
*** j^2 has quit IRC23:08
*** j^2 has joined #openstack-meeting-423:09
*** baoli has quit IRC23:09
*** woodard_ has quit IRC23:11
*** bharathm has joined #openstack-meeting-423:11
*** bobh has quit IRC23:12
*** avarner has quit IRC23:13
*** klamath has quit IRC23:13
*** rocky_g has quit IRC23:14
*** docaedo has joined #openstack-meeting-423:20
*** stanchan has quit IRC23:21
*** mhayden has joined #openstack-meeting-423:25
*** sigmavirus24 is now known as sigmavirus24_awa23:25
*** iyamahat has joined #openstack-meeting-423:28
*** dims_ has joined #openstack-meeting-423:29
*** stanchan has joined #openstack-meeting-423:33
*** dims_ has quit IRC23:34
*** prithiv_ has joined #openstack-meeting-423:35
*** sridhar_ram1 has joined #openstack-meeting-423:36
*** dims_ has joined #openstack-meeting-423:36
*** sridhar_ram has quit IRC23:37
* prithiv_ slaps raofei around a bit with a large fishbot23:38
*** baoli has joined #openstack-meeting-423:38
*** kebray has quit IRC23:41
*** padkrish has joined #openstack-meeting-423:43
*** baoli has quit IRC23:43
*** alexstav has joined #openstack-meeting-423:44
*** krtaylor has joined #openstack-meeting-423:45
*** kebray has joined #openstack-meeting-423:46
*** rbak has quit IRC23:48
*** baoli has joined #openstack-meeting-423:49
*** alexstav has quit IRC23:50
*** spotz is now known as spotz_zzz23:50
*** blahRus has quit IRC23:55
*** stanchan has quit IRC23:56
*** spzala has quit IRC23:57
*** Sukhdev has quit IRC23:58
*** ajmiller has quit IRC23:59

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