Thursday, 2016-02-25

*** Jeffrey4l has joined #openstack-meeting-400:00
*** _ody has left #openstack-meeting-400:01
*** IlyaG has joined #openstack-meeting-400:01
*** bobh has quit IRC00:02
*** Sukhdev has quit IRC00:03
*** harshs has joined #openstack-meeting-400:04
*** prithiv has quit IRC00:05
*** bmoss has left #openstack-meeting-400:06
*** sdake has joined #openstack-meeting-400:07
*** yamahata has joined #openstack-meeting-400:07
*** cloudtrainme has quit IRC00:10
*** klindgren_ has joined #openstack-meeting-400:13
*** klindgren has quit IRC00:15
*** yamamoto_ has joined #openstack-meeting-400:17
*** IlyaG has quit IRC00:21
*** sdake has quit IRC00:23
*** Sukhdev has joined #openstack-meeting-400:24
*** Sukhdev has quit IRC00:27
*** bobh has joined #openstack-meeting-400:28
*** Sukhdev has joined #openstack-meeting-400:35
*** Sukhdev has quit IRC00:44
*** prashantD has quit IRC00:51
*** carolbarret has quit IRC00:52
*** banix has joined #openstack-meeting-400:56
*** prashantD has joined #openstack-meeting-400:57
*** delatte has joined #openstack-meeting-400:58
*** delattec has quit IRC01:00
*** Sukhdev has joined #openstack-meeting-401:01
*** ajmiller has quit IRC01:02
*** dingboopt has joined #openstack-meeting-401:03
*** iceyao has joined #openstack-meeting-401:06
*** JRobinson__ is now known as JRobinson__afk01:07
*** prithiv has joined #openstack-meeting-401:07
*** minwang2 has quit IRC01:08
*** harshs has quit IRC01:08
*** harshs has joined #openstack-meeting-401:09
*** Sukhdev has quit IRC01:10
*** harshs has quit IRC01:10
*** cloudtrainme has joined #openstack-meeting-401:10
*** iceyao has quit IRC01:11
*** harshs has joined #openstack-meeting-401:11
*** iceyao_ has joined #openstack-meeting-401:11
*** iceyao has joined #openstack-meeting-401:14
*** harshs has quit IRC01:15
*** prithiv has quit IRC01:16
*** iceyao_ has quit IRC01:16
*** SimonChung has quit IRC01:20
*** lakshmiS has quit IRC01:20
*** _sarob has quit IRC01:21
*** julim has joined #openstack-meeting-401:26
*** baohua has joined #openstack-meeting-401:26
*** jlk has quit IRC01:28
*** thorst has joined #openstack-meeting-401:28
*** thorst has quit IRC01:34
*** thorst has joined #openstack-meeting-401:34
*** blahRus has quit IRC01:34
*** JRobinson__afk is now known as JRobinson__01:35
*** cloudtrainme has quit IRC01:37
*** ninag has quit IRC01:38
*** gongysh has joined #openstack-meeting-401:38
*** thorst has quit IRC01:39
*** lakshmiS has joined #openstack-meeting-401:39
*** tfukushima has joined #openstack-meeting-401:44
*** zhurong has joined #openstack-meeting-401:45
*** jlk has joined #openstack-meeting-401:45
*** jlk has quit IRC01:45
*** jlk has joined #openstack-meeting-401:45
*** cloudtrainme has joined #openstack-meeting-401:49
*** bpokorny has quit IRC01:51
*** Liuqing has joined #openstack-meeting-401:51
*** dims has quit IRC01:52
*** iceyao_ has joined #openstack-meeting-402:01
*** iceyao has quit IRC02:03
*** Sukhdev has joined #openstack-meeting-402:05
*** xingchao has joined #openstack-meeting-402:08
*** Sukhdev has quit IRC02:09
*** xingchao has quit IRC02:10
*** galstrom_zzz is now known as galstrom02:14
*** xingchao has joined #openstack-meeting-402:16
*** gongysh has quit IRC02:18
*** IlyaG has joined #openstack-meeting-402:24
*** lakshmiS has quit IRC02:27
*** armax has joined #openstack-meeting-402:28
*** amotoki has joined #openstack-meeting-402:29
*** bobh has quit IRC02:29
*** iceyao has joined #openstack-meeting-402:37
*** bobh has joined #openstack-meeting-402:39
*** xingchao has quit IRC02:39
*** JRobinson__ has quit IRC02:40
*** vmahe has quit IRC02:40
*** vmahe has joined #openstack-meeting-402:41
*** iceyao_ has quit IRC02:41
*** banix has quit IRC02:41
*** yamamoto_ has quit IRC02:43
*** bobh has quit IRC02:43
*** galstrom is now known as galstrom_zzz02:44
*** JRobinson__ has joined #openstack-meeting-402:46
*** yamahata has quit IRC02:46
*** iyamahat has quit IRC02:47
*** tfukushima has quit IRC02:54
*** s3wong has joined #openstack-meeting-402:54
*** s3wong has quit IRC02:55
*** gongysh has joined #openstack-meeting-402:56
*** ajmiller has joined #openstack-meeting-402:57
*** xingchao has joined #openstack-meeting-403:00
*** zhurong has quit IRC03:01
*** zhurong has joined #openstack-meeting-403:02
*** tfukushima has joined #openstack-meeting-403:03
*** banix has joined #openstack-meeting-403:09
*** iyamahat has joined #openstack-meeting-403:15
*** amotoki has quit IRC03:19
*** salv-orlando has joined #openstack-meeting-403:27
*** prashantD has quit IRC03:27
*** salv-orlando has quit IRC03:28
*** amotoki has joined #openstack-meeting-403:30
*** salv-orl_ has quit IRC03:30
*** cloudtrainme has quit IRC03:30
*** baoli_ has quit IRC03:31
*** amotoki has quit IRC03:35
*** balajin_ has left #openstack-meeting-403:36
*** Liuqing has quit IRC03:37
*** cemmason1 has quit IRC03:38
*** ajmiller has quit IRC03:38
*** Liuqing has joined #openstack-meeting-403:38
*** yamamoto_ has joined #openstack-meeting-403:38
*** baoli has joined #openstack-meeting-403:40
*** amotoki has joined #openstack-meeting-403:40
*** baoli has quit IRC03:42
*** baoli has joined #openstack-meeting-403:43
*** neelashah has joined #openstack-meeting-403:45
*** baoli has quit IRC03:48
*** dingboopt has quit IRC03:57
*** anand has joined #openstack-meeting-403:58
anandHello I have a barbican question.04:00
anandI am at : dding support for configuring number of async worker processes          Adding new config parameter to control number of async worker     processes. Also removing existing parameter 'workers' as its not     used and was currently defined under DEFAULT config section.          Change-Id: I04af9d012ca86227171eecebdbf43999dd667ac5     Closes-Bug: #151915904:00
openstackbug 1519159 in Barbican "Barbican number of workers configuration does not work" [Undecided,Fix released] https://launchpad.net/bugs/151915904:00
*** harshs has joined #openstack-meeting-404:00
anandand04:01
anand# Number of asynchronous worker processes. # When greater than 1, then that many additional worker processes are # created for asynchronous worker functionality. asynchronous_workers = 604:01
*** amotoki has quit IRC04:01
anandin my barbican.conf04:01
anandbut i still dont see 6 worker processes04:01
anandI see just 104:02
*** JRobinson__ is now known as JRobinson__afk04:02
anandis there anything I am missing?04:03
*** amotoki has joined #openstack-meeting-404:13
*** JRobinson__afk is now known as JRobinson__04:14
*** Liuqing has quit IRC04:21
*** Liuqing has joined #openstack-meeting-404:22
*** salv-orlando has joined #openstack-meeting-404:29
*** banix has quit IRC04:31
*** neelashah has quit IRC04:38
*** salv-orlando has quit IRC04:39
*** bobh has joined #openstack-meeting-404:42
*** bobh has quit IRC04:47
*** iceyao has quit IRC04:47
*** iceyao_ has joined #openstack-meeting-404:47
*** SimonChung has joined #openstack-meeting-404:51
*** armax has quit IRC04:51
*** SimonChung1 has joined #openstack-meeting-404:53
*** SimonChung has quit IRC04:55
*** watanabe_isao has joined #openstack-meeting-405:03
*** Liuqing has quit IRC05:08
*** Liuqing has joined #openstack-meeting-405:08
*** sridhar_ram has joined #openstack-meeting-405:12
*** belmoreira has joined #openstack-meeting-405:12
*** sdake has joined #openstack-meeting-405:17
*** sdake has quit IRC05:22
*** anand has quit IRC05:30
*** javeriak has joined #openstack-meeting-405:38
*** javeriak has quit IRC05:39
*** javeriak has joined #openstack-meeting-405:39
*** irenab has quit IRC05:43
*** bobh has joined #openstack-meeting-405:43
*** numans has joined #openstack-meeting-405:46
*** cemmason has joined #openstack-meeting-405:47
*** bobh has quit IRC05:47
*** numan_ has joined #openstack-meeting-405:50
*** numan_ has quit IRC05:51
*** dims has joined #openstack-meeting-405:52
*** numan_ has joined #openstack-meeting-405:53
*** numans has quit IRC05:54
*** numan_ has quit IRC05:56
*** numans has joined #openstack-meeting-405:56
*** nkrinner has joined #openstack-meeting-405:58
*** salv-orlando has joined #openstack-meeting-405:58
*** numans has quit IRC06:01
*** gongysh has quit IRC06:03
*** salv-orlando has quit IRC06:03
*** javeriak_ has joined #openstack-meeting-406:05
*** v1k0d3n has quit IRC06:05
*** v1k0d3n has joined #openstack-meeting-406:05
*** javeriak has quit IRC06:07
*** numans has joined #openstack-meeting-406:13
*** harshs has quit IRC06:14
*** sridhar_ram has quit IRC06:17
*** galstrom_zzz is now known as galstrom06:23
*** miguelgrinberg has quit IRC06:25
*** miguelgrinberg has joined #openstack-meeting-406:27
*** mbound has joined #openstack-meeting-406:30
*** hdaniel has joined #openstack-meeting-406:31
*** mbound has quit IRC06:34
*** irenab has joined #openstack-meeting-406:37
*** javeriak_ has quit IRC06:40
*** dims has quit IRC06:43
*** bobh has joined #openstack-meeting-406:44
*** dave-mccowan has quit IRC06:45
*** javeriak has joined #openstack-meeting-406:45
*** minwang2 has joined #openstack-meeting-406:45
*** bobh has quit IRC06:48
*** fawadkhaliq has joined #openstack-meeting-406:50
*** gampel has joined #openstack-meeting-406:53
*** zeih has joined #openstack-meeting-406:53
*** Liuqing has quit IRC06:53
*** belmoreira has quit IRC06:53
*** gampel has left #openstack-meeting-406:54
*** fnaval has quit IRC06:54
*** gongysh has joined #openstack-meeting-406:56
*** JRobinson__ has quit IRC07:02
*** salv-orlando has joined #openstack-meeting-407:02
*** fnaval has joined #openstack-meeting-407:02
*** salv-orlando has quit IRC07:07
*** paul-carlton1 has joined #openstack-meeting-407:14
*** salv-orlando has joined #openstack-meeting-407:25
*** hdaniel has quit IRC07:26
*** salv-orl_ has joined #openstack-meeting-407:26
*** salv-orlando has quit IRC07:26
*** minwang2 has quit IRC07:29
*** tfukushima has quit IRC07:31
*** tfukushi_ has joined #openstack-meeting-407:32
*** zeih has quit IRC07:42
*** mbound has joined #openstack-meeting-407:43
*** belmoreira has joined #openstack-meeting-407:51
*** galstrom is now known as galstrom_zzz07:51
*** fawadkhaliq has quit IRC07:51
*** daneyon_ has quit IRC07:55
*** belmoreira has quit IRC07:58
*** zeih has joined #openstack-meeting-407:58
*** belmoreira has joined #openstack-meeting-408:00
*** bobh has joined #openstack-meeting-408:02
*** zeih has quit IRC08:03
*** mbound has quit IRC08:04
*** belmoreira has quit IRC08:06
*** bobh has quit IRC08:07
*** matrohon has joined #openstack-meeting-408:08
*** dtardivel has joined #openstack-meeting-408:14
*** evgenyf has joined #openstack-meeting-408:14
*** hdaniel has joined #openstack-meeting-408:14
*** britthouser has quit IRC08:21
*** watanabe_isao has quit IRC08:37
*** zhurong has quit IRC08:44
*** zhurong has joined #openstack-meeting-408:45
*** prithiv has joined #openstack-meeting-408:47
*** ihrachys has joined #openstack-meeting-408:51
*** tfukushi_ has quit IRC08:51
*** prithiv1 has joined #openstack-meeting-408:51
*** prithiv has quit IRC08:51
*** prithiv1 has quit IRC08:52
*** amotoki has quit IRC08:53
*** lijie has joined #openstack-meeting-408:57
*** zeih has joined #openstack-meeting-408:59
*** lijie has quit IRC09:04
*** tfukushima has joined #openstack-meeting-409:04
*** zeih has quit IRC09:04
*** Jerry has joined #openstack-meeting-409:05
*** Jerry has quit IRC09:05
*** JerryLi has joined #openstack-meeting-409:06
*** paul-carlton1 has quit IRC09:07
*** tfukushima has quit IRC09:09
*** JerryLi has quit IRC09:09
*** JerryLi has joined #openstack-meeting-409:10
*** amotoki has joined #openstack-meeting-409:10
*** tfukushima has joined #openstack-meeting-409:11
*** zhurong has quit IRC09:12
*** fawadkhaliq has joined #openstack-meeting-409:17
*** [1]evgenyf has joined #openstack-meeting-409:19
*** evgenyf has quit IRC09:21
*** [1]evgenyf is now known as evgenyf09:21
*** paul-carlton1 has joined #openstack-meeting-409:26
*** salv-orlando has joined #openstack-meeting-409:27
*** fawadkhaliq has quit IRC09:29
*** baohua has quit IRC09:29
*** salv-orl_ has quit IRC09:30
*** pbourke has quit IRC09:32
*** pbourke has joined #openstack-meeting-409:32
*** prithiv has joined #openstack-meeting-409:39
*** JerryLi has quit IRC09:41
*** salv-orlando has quit IRC09:43
*** zeih has joined #openstack-meeting-410:01
*** bobh has joined #openstack-meeting-410:03
*** zeih has quit IRC10:06
*** bobh has quit IRC10:08
*** tfukushima has quit IRC10:17
*** _degorenko|afk is now known as degorenko10:30
*** sambetts|afk is now known as sambetts10:32
*** baohua has joined #openstack-meeting-410:33
*** pcaruana has joined #openstack-meeting-410:42
*** zhurong has joined #openstack-meeting-410:43
*** belmoreira has joined #openstack-meeting-410:49
*** iceyao_ has quit IRC10:56
*** sdake has joined #openstack-meeting-410:58
*** salv-orlando has joined #openstack-meeting-410:59
*** salv-orlando has quit IRC10:59
*** salv-orlando has joined #openstack-meeting-410:59
*** baohua has quit IRC11:05
*** baohua has joined #openstack-meeting-411:06
*** xingchao has quit IRC11:13
*** britthouser has joined #openstack-meeting-411:13
*** bobh has joined #openstack-meeting-411:15
*** bobh has quit IRC11:19
*** fawadkhaliq has joined #openstack-meeting-411:27
*** gongysh has quit IRC11:28
*** sdake_ has joined #openstack-meeting-411:29
*** sdake has quit IRC11:30
*** dshakhray has joined #openstack-meeting-411:30
*** zeih has joined #openstack-meeting-411:32
*** baohua has quit IRC11:33
*** baohua has joined #openstack-meeting-411:34
*** zeih has quit IRC11:37
*** sdake_ has quit IRC11:37
*** Claudio1 has joined #openstack-meeting-411:43
*** Claudio2 has joined #openstack-meeting-411:44
*** Claudio1 has quit IRC11:45
*** baohua has quit IRC11:45
*** baohua has joined #openstack-meeting-411:46
*** claudio_ has joined #openstack-meeting-411:47
*** Claudio2 has quit IRC11:47
*** hayatb has joined #openstack-meeting-411:52
*** konstantinos has joined #openstack-meeting-411:54
*** thorst has joined #openstack-meeting-412:01
*** Liuqing has joined #openstack-meeting-412:03
*** prithiv has quit IRC12:06
*** berndbausch has quit IRC12:06
*** berndbausch has joined #openstack-meeting-412:07
*** yamamoto_ has quit IRC12:07
*** Liuqing has quit IRC12:16
*** iceyao has joined #openstack-meeting-412:18
*** berndbausch has quit IRC12:27
*** javeriak has quit IRC12:42
*** fawadkhaliq has quit IRC12:42
*** fawadkhaliq has joined #openstack-meeting-412:43
*** berndbausch has joined #openstack-meeting-412:45
*** prithiv has joined #openstack-meeting-412:46
*** fawadkhaliq has quit IRC12:47
*** prithiv has quit IRC12:51
*** prithiv has joined #openstack-meeting-412:53
*** ninag has joined #openstack-meeting-412:54
*** pcaruana has quit IRC12:55
*** baoli has joined #openstack-meeting-412:55
*** yamamoto has joined #openstack-meeting-412:55
*** salv-orlando has quit IRC12:56
*** dave-mccowan has joined #openstack-meeting-412:56
*** prithiv has quit IRC12:57
*** iyamahat_ has joined #openstack-meeting-412:59
*** prithiv has joined #openstack-meeting-412:59
*** yamamoto_ has joined #openstack-meeting-413:01
*** yamamoto has quit IRC13:01
*** iyamahat has quit IRC13:02
*** pcaruana has joined #openstack-meeting-413:09
*** neelashah has joined #openstack-meeting-413:10
*** klamath has joined #openstack-meeting-413:15
*** baoli_ has joined #openstack-meeting-413:26
*** baoli has quit IRC13:28
*** zeih has joined #openstack-meeting-413:33
*** zeih has quit IRC13:37
*** haleyb has joined #openstack-meeting-413:39
*** JerryLi has joined #openstack-meeting-413:42
*** armax has joined #openstack-meeting-413:47
*** dims has joined #openstack-meeting-413:47
*** fawadkhaliq has joined #openstack-meeting-413:53
*** bunting has joined #openstack-meeting-413:56
*** bobh has joined #openstack-meeting-413:57
*** salv-orlando has joined #openstack-meeting-413:58
*** avarner has joined #openstack-meeting-413:59
*** mfedosin has joined #openstack-meeting-413:59
flaper87Courtesy meeting reminder: ativelkov, cpallares, flaper87, flwang1, hemanthm, jokke_, kragniz, lakshmiS, mclaren, mfedosin, nikhil_k14:00
flaper87Courtesy meeting reminder: Nikolay_St, Olena, pennerc, rosmaita, sigmavirus24, sabari, TravT, ajayaa, GB21, bpoulos, harshs, abhishekk, bunting14:00
flaper87Courtesy meeting reminder: dshakhray, wxy, dhellmann, kairat14:00
flaper87#startmeeting Glance14:00
openstackMeeting started Thu Feb 25 14:00:15 2016 UTC and is due to finish in 60 minutes.  The chair is flaper87. 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: Glance)"14:00
openstackThe meeting name has been set to 'glance'14:00
flaper87o/14:00
avarnero/14:00
buntingo/14:00
mfedosino/14:00
dshakhrayo/14:00
kragnizo/14:00
*** kairat has joined #openstack-meeting-414:01
nikhilo/14:01
kairato/14:01
ninago/14:01
flaper87ok, I'd call that a quorum :D14:01
flaper87#topic Agenda14:01
*** openstack changes topic to "Agenda (Meeting topic: Glance)"14:01
flaper87#link https://etherpad.openstack.org/p/glance-team-meeting-agenda14:01
rosmaitao/14:01
flaper87There, as usual14:01
mfedosinwhere is agenda? :)14:01
flaper87Everything that's not in the agenda, let's keep it for Open Discussion14:01
mfedosinah14:02
flaper87there14:02
flaper87I forgot to update the date14:02
flaper87:D14:02
mfedosinyup, that's better14:02
flaper87#topic Updates Glare14:02
*** openstack changes topic to "Updates Glare (Meeting topic: Glance)"14:02
mfedosinokay, let's begin14:02
*** Steap has joined #openstack-meeting-414:02
mfedosinfirst, as it was promised the spec is here14:02
mfedosin#link https://review.openstack.org/#/c/283136/14:03
flaper87++14:03
*** salv-orlando has quit IRC14:03
mfedosinafter that I have several meetings with folks from murano and app-catalog14:03
*** haleyb has quit IRC14:03
mfedosinthey gave me several advice, but in general they like the proposal14:03
mfedosintoday we're going to join api-wg meeting with Nikhil14:04
flaper87ok, We can start reviewing those specs in a couple of weeks from now. As soon as FF is over and we have a tag14:04
flaper87that sounds great14:04
flaper87joining the API-WG meeting is definitely good14:04
mfedosinafter that I'll update the spec based on all comments14:04
*** pmesserli has joined #openstack-meeting-414:05
mfedosinsecond, Ina Vasilevskaya is back after maternity leave14:05
mfedosinAnd she's happy to join Glance/Glare team again14:05
flaper87w0000h000, glad to have her back :D14:05
mfedosinthere are several administrative issues14:06
mfedosinbut should get better next week.14:06
flaper87ok, got it! All good news14:06
flaper87thanks for working on the spec14:07
mfedosinnp, it's my job :)14:07
flaper87let's know the feedback from the api-wg14:07
flaper87anything else?14:07
nikhilthere was some ping14:07
nikhilabout plugins requirement from murano14:07
mfedosinthere is a couple of minor things14:07
nikhiland that hard coding was tough for them14:07
nikhilbut that's still in discussion I sup?14:08
flaper87plugins as in API extensions ?14:08
*** avarner has quit IRC14:08
*** avarner has joined #openstack-meeting-414:08
*** evgenyf has quit IRC14:08
mfedosinabout plugins and API extensions14:08
nikhilhm, not exactly. loosely coupling of the code with those of the artifacts types14:08
*** andymaier has joined #openstack-meeting-414:08
mfedosinWe don't like it14:08
mfedosincurrently we want that all plugins will be placed in glance/objects folder14:09
flaper87mmh, understood. I'll have to read their request a bit better14:09
mfedosinlike oslo.vo requires14:09
nikhilI just wanted to point this out, I did not intend to start a discussion (ftr)14:09
flaper87ok14:09
mfedosinbut Murano needs some external14:09
flaper87let's move on. We can discuss this further on the spec14:09
*** zhurong has quit IRC14:10
mfedosinI'll told you about our decision after this meeting in glance channel14:10
flaper87ok14:10
flaper87#topic updates nova v1->v214:10
*** openstack changes topic to "updates nova v1->v2 (Meeting topic: Glance)"14:10
flaper87There's not much to update here14:10
flaper87This work was moved to Newton14:10
mfedosinyeah14:10
flaper87the one thing I did want to mention is that we need to schedule a session or something with the nova team14:11
mfedosincode is still there, no review at all14:11
mfedosinflaper87: ++14:11
*** mclaren has joined #openstack-meeting-414:11
flaper87Also, we need to start the work on glanceclient to have that compatibility layer14:11
mfedosinflaper87: is it a final decision?14:11
flaper87mfedosin: what part?14:11
mfedosincompatibility layer14:12
flaper87oh, yeah. I mean, we were going to do it anyway. The thing is we wanted to postpone it for after the nova migration happened14:12
*** bobh has quit IRC14:12
flaper87We need to work on a compatibility layer that favors v2 and doesn't break v114:12
flaper87and then release it in glanceclient so we can move nova to v2 in N-114:13
flaper87The sooner we start this, the better14:13
mfedosinI see14:13
kairatSo we need to change Mike's code, do we?14:13
*** leecalcote has joined #openstack-meeting-414:13
mfedosinkairat: I hope no14:13
kairatAnd implement migration from scratch>14:13
kairatOk14:14
flaper87no14:14
kairatThat's good14:14
mfedosinwe can take the code from Nova and put in the client14:14
flaper87The compatibility layer should (hopefully) fit into what Mike did14:14
flaper87mfedosin: sorta, we might want to change it a bit14:14
*** yamamoto_ has quit IRC14:14
mfedosinwe just need to replace several utilities14:14
*** dslevin has left #openstack-meeting-414:14
flaper87anyway, that's the gist14:14
flaper87We should have a spec for this, tbh14:14
flaper87who wants to take this on?14:15
* mfedosin hides14:15
flaper87mfedosin: I won't let you >.>14:15
flaper87you have too many things on your plate14:15
flaper87:P14:15
flaper87no one?14:15
flaper87ping? :D14:15
nikhilI want to do it14:15
mfedosinCyril's here?14:15
flaper87nikhil: w000h00014:15
nikhilbut don't think people will like my dir in first place14:15
flaper87mfedosin: he's not here, I could ping him14:15
Steapmfedosin: yeah14:16
Steapnot the right nick though14:16
flaper87oh, he is14:16
flaper87:D14:16
mfedosinflaper87: it was fast14:16
flaper87nikhil: why's that?14:16
flaper87Steap: interested in taking the compatibility layer on?14:16
nikhilflaper87: I would like to know the details on putting the decision to add compat layer to client14:16
kairat++ to nikhil14:16
SteapWasn't there a feature freeze that blocked us on this ?14:16
mfedosinSteap: writing the spec, actually14:16
flaper87Steap: it's newton work14:17
flaper87we need to write the spec14:17
nikhilis this going in Nova or Glance?14:17
nikhilseems like we need at both places14:17
*** avarner_ has joined #openstack-meeting-414:17
Steapor glanceclient ?14:17
Steapnikhil: why would we have the compatibility layer in both places ?14:17
nikhilit's common for client14:17
flaper87nikhil: not really. On reason I'm asking for a spec is to also formalize this discussion14:17
nikhilSteap: I meant a spec in both places14:17
flaper87There have been several discussions about this14:18
Steapnikhil: oh right14:18
nikhilflaper87: gotcha14:18
flaper87especially on IRC14:18
flaper87but nothing is in a place we can reference14:18
nikhiloh14:18
Steapnikhil: a "define the layer" spec in glanceclient and a "use the layer" in Nova ? :p14:18
flaper87so, this would be a good way to do that14:18
nikhildates would work! :)14:18
*** irenab has quit IRC14:18
*** avarner has quit IRC14:18
nikhilflaper87: ah kk14:18
flaper87I'm on the side that thinks this should go into glanceclient14:18
Steapmakes sense to me14:18
nikhilSteap: I think nova is worried about long term eval of this14:18
nikhiland for client it's mostly about how to structure the code14:19
flaper87and nova shouldn't have any knowledge of this (a.k.a nova.images.glance shouldn't exist)14:19
Steapnikhil: what do you mean ?14:19
nikhilit will be impact on developers14:19
Steapflaper87: yeah14:19
Steapflaper87: it should be abstracted in glanceclient14:19
flaper87Steap: yup, that's what we need to work on in glanceclient14:19
flaper87ok, let's move on14:19
nikhilI am skeptical to put this in client tbh (but will have to read the logs)14:20
flaper87WE can discuss this further in -glance14:20
flaper87nikhil: I wish I remembered when this was discussed, really. :(14:20
flaper87I remember some in-person discussions14:20
*** fawadkhaliq has quit IRC14:20
nikhilnp14:20
flaper87And also over the reviews of mike's work14:20
flaper87and IRC with other nova folks14:20
flaper87anyway14:20
flaper87We need to formalize this discussion14:20
flaper87hence the request for a spec14:21
flaper87#topic Cross prj updates14:21
*** openstack changes topic to "Cross prj updates (Meeting topic: Glance)"14:21
nikhilo/14:21
nikhilJust a small update14:21
nikhilThe Cross prj initiative on quotas has started getting momentum14:21
rosmaitawatch out!14:22
*** spzala has joined #openstack-meeting-414:22
nikhilinitial spec14:22
nikhil#link https://review.openstack.org/#/c/284454/14:22
*** avarner_ has quit IRC14:22
nikhiland a weekly meeting14:22
*** avarner__ has joined #openstack-meeting-414:22
nikhil#link https://review.openstack.org/#/c/284478/14:22
flaper87that's good news14:22
nikhilI will announce to ML in a few14:22
nikhilNothing to discuss on the spec itself yet14:23
flaper87nice, glad to see this moving forward14:23
nikhilif there is interest, I can make it a point to buzz you prior to mtg :)14:23
flaper87it's been a long standing open task for several projects14:23
nikhil(done)14:23
*** JerryLi has quit IRC14:23
nikhilagreed14:23
flaper87I'm interested but I don't think I've the bandwidth to follow that mtg too :(14:24
flaper87plus, you'll update us anyway14:24
* flaper87 ducks14:24
* flaper87 ducks two times14:24
flaper87ok moving on14:24
nikhilheh14:24
flaper87#topic Design Summit sessions allocation14:24
*** openstack changes topic to "Design Summit sessions allocation (Meeting topic: Glance)"14:24
flaper87#link http://lists.openstack.org/pipermail/openstack-dev/2016-February/087433.html14:24
flaper87Sent that email... yday I htink14:24
flaper87think, even14:24
flaper87pls, if you have an opinion, do chime in14:25
flaper87nikhil: proposed we increase the number of workrooms to 614:25
flaper87we had 5 in tokyo14:25
nikhilI did14:25
nikhilWhat are the tentative FB sessions for us?14:25
flaper87OTOH, I guess it'd be something like Import Refactor, Quotas and something else (perhaps the compat layer so we can invite osclient folks )14:26
flaper87but again, nothing has been discussed yet on this14:26
mfedosinMaybe Glare will require 2 :)14:26
nikhilhmm14:26
flaper87I'd love to talk more with ppl that are going to run for the PTL position14:27
flaper87it's better to plan that way14:27
nikhilI think we will need 1/2 Workroom session for tasks (tbh)14:27
flaper87mfedosin: I think Glare can use  a workroom session14:27
flaper87In tokyo, we made a very good use of the meetup time14:27
nikhilflaper87: he meant 2 W for Glare (I think)14:27
flaper87we split the time and the team14:27
*** avarner__ has quit IRC14:27
flaper87mfedosin: oh, ok. weeeeeeell, I guess we could use 1 and some meetup time14:28
*** leecalcote has quit IRC14:28
flaper87It's quite blury still. I'll start putting more serious thoughts on this and come up with a plan for next week14:28
flaper87Since next week is FF anyway14:28
mfedosinI wanted to have a session about Glare architecture and another one with murano, app-catalog and heat14:28
flaper87That said, I want us to be very very careful with requesting more time as there are more projects this time around14:28
nikhiloh then , prolly 1 FB and 1 W14:28
flaper87so, just trying to be a good citizen14:29
nikhilyes, makes sense14:29
nikhilI was trying to be cautious that we didn't miss on imp topics14:29
flaper87mfedosin: in tokyo we shared the meetup time with app-catalog too14:29
nikhilwe are making some changes to glance and they are big ones!14:29
mfedosinit was on Friday14:29
nikhilfor example a lot of folks ask me about tasks14:29
nikhiland image sharing14:29
flaper87Also, considering the size of the glance team, there's so much we can plan for Newton, which means limiting the number of session might end up being good14:30
flaper87hahaha14:30
rosmaitaflaper87: nikhil: is friday set aside for working meetings like in tokyo?14:30
nikhilI think the contri meetup is on friday14:30
flaper87That said, we should also use the time at the summit to discuss things that *must* be discussed face to face14:30
flaper87rosmaita: yes14:30
flaper87rosmaita: we have a full day14:30
flaper87just like in tokyo14:30
rosmaitaok, everyone please make travel plans so that you can spend a full day14:30
flaper87ah yeah, that too14:31
flaper87do not live on friday at 8am14:31
rosmaitawe got a lot done in tokyo (though you wouldn't know it from the import refactor)14:31
nikhilleave*14:31
nikhilbut surely live :D14:31
flaper87lol, leave*14:31
flaper87hahaha14:31
flaper87nikhil: thanks :D14:31
*** leecalcote has joined #openstack-meeting-414:31
nikhil;)14:31
*** gongysh_ has joined #openstack-meeting-414:31
flaper87my brain is full of Freudian slips14:31
flaper87rosmaita: I agree14:31
flaper87I found the meetup in Tokyo to be super super helpful14:32
flaper87ok14:32
flaper87put some thoughts14:32
flaper87I'll start an etherpad and send an email so we can start collecting topics14:32
nikhilI think the next week in Austin is some sort of festival14:32
nikhilso that might be worth considering as well14:32
flaper87The week after the summit?14:32
nikhilI think so14:32
flaper87nnnnnice, good thing I'm booked for like a gazillion of days there14:33
flaper87hahahaha14:33
* nikhil double checking (remembers vaguely)14:33
flaper87anyway, moving on14:33
flaper87#topic Non client libraries freeze14:33
*** Jeffrey4l has quit IRC14:33
*** openstack changes topic to "Non client libraries freeze (Meeting topic: Glance)"14:33
flaper87Unfortunately, I think I forgot to mention this last week but this week is the non client libraries freeze14:33
flaper87This means that this week libraries like glance_store can be released for the last time during the Mitaka timeframe14:34
flaper87#link https://review.openstack.org/#/c/251851/14:34
flaper87Some patches landed yday14:34
mfedosinso kairat work with Swift driver moved to Newton14:34
*** baohua has quit IRC14:34
mfedosinit's sad14:34
flaper87but there are 2 big ones for the "trusts" work  that still can make it14:34
*** baohua has joined #openstack-meeting-414:34
flaper87mfedosin: check the link >.>14:34
mfedosinflaper87: ah14:35
flaper87We have until tomorrow to release it14:35
nikhiloh sorry, I was too tired last night to review that one14:35
flaper87I never do releases on friday but I'm happy to stay "on call" during the weekend in case things go south14:35
nikhilflaper87: is that still on?14:35
nikhil(I'll be online during the weekend too)14:35
flaper87not sure if sabari is around but there was also the vmware on python-requests one14:35
kairati got some comments from mclaren, but nothing more then.14:35
kairatso it would be perfect to have some comments tomorrow14:36
flaper87kairat: it's a big one :)14:36
*** berndbausch has left #openstack-meeting-414:36
kairatI am personally will try to review all patches for glance_store tomorrow14:36
mfedosinactually big two14:36
flaper87I'll review them with my limited knowledge of how the swift store works14:36
flaper87mfedosin: right14:36
flaper87it's always a problem with big patches14:36
mfedosinhere's the second part https://review.openstack.org/#/c/251850/1114:36
flaper87no promises made, it's possible they won't make it14:36
nikhilcan we have a list of the ones we are targeting ?14:37
*** amotoki has quit IRC14:37
flaper87mfedosin: I posted the top most one14:37
flaper87nikhil: I think just that one, TBH14:37
flaper87I don't think we've bandwidth for anything else today/tomorrow14:37
nikhilgreat14:37
flaper87ok, moving on14:38
flaper87#topic Preparing for Feature Freeze14:38
*** openstack changes topic to "Preparing for Feature Freeze (Meeting topic: Glance)"14:38
flaper87Now, next week is FF14:38
flaper87yup, it's that time of the cycle again14:38
flaper87crazy, isn't it?14:38
flaper87Anyway14:38
flaper87we don't have that many pending features in glance14:39
mfedosinfilters14:39
*** yamamoto has joined #openstack-meeting-414:39
mfedosinhttps://review.openstack.org/#/c/248359/14:39
flaper87mfedosin: I said "that many"14:39
mfedosinthere are 6 filters :)14:39
* flaper87 takes mfedosin's keyboard14:39
flaper87hahahha14:39
flaper87jokes apart14:39
flaper87yeha, filters is perhaps the biggest one we have now14:40
flaper87so, I wanted to propose having a review sprint on Monday (as early in the week as possible)14:40
kairat++ to review day14:40
mfedosinfilters review day :)))14:41
flaper87In addition to that day, I was thinking we should have reviews days every week until the end of the cycle14:41
flaper87but I'll let that for open discussion14:41
flaper87:D14:41
kairatI would love it personally14:41
flaper87All that said, I'm hoping to cut M-3 on Wednesday so, let's target that as a deadline14:41
*** leecalcote has quit IRC14:41
flaper87It'd be awesome to be able to do it on Tuesday but that might be too tight14:42
flaper87Questions ?14:42
flaper87otherwise we can move on14:42
flaper87ok, moving on14:43
flaper87#topic Spec lite proposal14:43
*** openstack changes topic to "Spec lite proposal (Meeting topic: Glance)"14:43
flaper87#link https://review.openstack.org/#/c/282517/14:43
flaper87jokke_: wrote this14:43
flaper87:D14:43
*** tsekiyama has joined #openstack-meeting-414:43
flaper87The proposal is quite small14:44
flaper87and easy to review and adopt14:44
flaper87LEt's drop comments there14:44
flaper87if there are no complaints, I'll proceed with approving it14:44
*** armax has quit IRC14:44
flaper87ok, unless there are comments, I think we can go into Open Discussion14:45
flaper87or as I prefer to call it: "Go nuts section"14:45
mclarendo we say why we're changing the spec lite process?14:45
flaper87mclaren: I think it's in the commit message14:46
flaper87if it's not, we can then put it there14:46
flaper87unless I misunderstood your question and you're actually asking why we're changing it14:46
*** Jeffrey4l has joined #openstack-meeting-414:47
flaper87mclaren: ^14:47
buntingI'm intrested why14:47
mclarenI don't see anything in the commit message. It adds overhead, so explaining the advantages would be useful14:47
kairatPerhaps it is worth mention in spec itself14:48
kairatto explain future supporters why it was chosen14:48
kairatand not to spent their time14:48
flaper87The TL;DR is: Using bugs doesn't seemed to work. Triaging them was sometihng we did in the drivers meeting which we don't have anymore. Using specs encourages a more distributed review process across core reviewers14:48
flaper87but yeah, I think we should have this in the spec14:48
rosmaitalet's just slap that into the commit message14:48
flaper87erm, commit message14:49
flaper87I don't think we need to put this in the contributions guidelines14:49
rosmaita+1 to keep out of guidelines14:49
*** lakshmiS has joined #openstack-meeting-414:49
flaper87I'll ping jokke_ and ask him to write this down14:50
*** lakshmiS_ has joined #openstack-meeting-414:50
jokke_also ... moving it to the glance-specs repo, we get all our specs listed in the same website14:50
flaper87maybe not using his words because we know what that commit message will look like14:50
flaper87jokke_: oh, HAI!14:50
jokke_;)14:50
*** baohua has quit IRC14:51
flaper87jokke_: ah listing, that was the other one. That one is actually super useful14:51
*** lakshmiS_ has quit IRC14:51
flaper87ok, 10mins left14:51
jokke_so one does not need to go hunting closed bugs and merged specs to figure out what new functionality has gone in14:51
flaper87#topic Open Discussion14:51
*** openstack changes topic to "Open Discussion (Meeting topic: Glance)"14:51
mfedosinwhat about deprecating use_user_token?14:51
mfedosinhttps://review.openstack.org/#/c/237742/14:51
flaper87So, I mentioned that I'd like to have 1 review day per week until the end of the cycle14:52
flaper87I obviously don't expect everyone to sign up for this14:52
flaper87but it'd be cool to establish a day for this.14:52
*** baohua has joined #openstack-meeting-414:52
flaper87The upcoming weeks will require bug fixing and reviews like crazy14:52
rosmaitai guess monday is as good as any14:52
flaper87rosmaita:14:52
flaper87ops14:53
flaper87rosmaita: ++14:53
nikhilmfedosin: that's a breaking change afaict14:53
flaper87on another note, a CVE fix broke something on how locations work: https://review.openstack.org/#/c/280789/14:53
flaper87we need to help reviewing that fix14:53
flaper87jokke_: ^14:53
jokke_flaper87: I'm aware of that :(14:53
flaper87jokke_: :(14:54
*** rbak has joined #openstack-meeting-414:54
kairatdo we have trusts now to avoid using that option?14:54
kairatmfedosin, ^14:54
mfedosinyes14:54
kairatOk, good14:54
mfedosinthis option was introduced to work with registry14:54
nikhilkairat: I think in some deployments may not be able to use trusts14:54
mfedosinwhen token expires14:54
nikhilcorrect14:54
mfedosinbut it doesn't work14:55
nikhilso there's a dependency here14:55
mfedosinif you disable it, you cloud will die14:55
kairatAlso v2 is deprecated already14:55
mfedosinbecause every person will behave as an admin14:55
nikhilit works for when the operation is concise (like trusts) performed using nova14:55
kairatwe need to consider that during Newton14:55
mfedosinplease read14:56
mfedosin#link https://wiki.openstack.org/wiki/OSSN/OSSN-006014:56
nikhilfor long running operations if the token is invalid and then this will allow the image to go to active (given you have the right setup)14:56
nikhilbut there's no getting rid of it yet so those who are using it will keep using it14:57
nikhilis the intention to remote it in Mitaka like the OSSN says?14:57
*** vikram_ has joined #openstack-meeting-414:58
*** RickA-HP has joined #openstack-meeting-414:58
nikhiland that's what I am aiming to talk about14:58
mfedosinno14:58
rosmaitasorry to interrupt, but looks like we are running out of time ... please open your browsers to:14:58
nikhilif we remove it then we need to send proper communication that people need to adopt trusts14:58
mfedosinwe will remove it in Newton14:58
rosmaita#link http://lists.openstack.org/pipermail/openstack-dev/2016-February/087519.html14:58
rosmaitait will take you 3 minutes to read, there's a link to an etherpad with more stuff if you want to dig, but it would be good to have a consensus on what the recommended behavior should be, since it's different in v1 and v214:58
mfedosinin Mitaka we deprecate it14:58
flaper87I need to take a better look at mfedosin's patch14:58
flaper87rosmaita: ++14:58
nikhilI remember that bug (btw)14:59
nikhiland I think hemanthm agreed with the deprecation14:59
mfedosinrosmaita: yeahm thanks. we need to remember about it in compat layer14:59
flaper87ok, that's it14:59
flaper87thank you all!14:59
nikhilI am just not sure the wider impact on this so removing in newton might be okay, let's start the broadcast on the deprecation this release14:59
flaper87tty next week14:59
flaper87and REVIEW ALL THE PATCHES15:00
nikhilok, thanks15:00
*** lei-zh1 has joined #openstack-meeting-415:00
flaper87PRETTY PLEASE!!!!!!!!!!!15:00
*** sjmc7 has joined #openstack-meeting-415:00
flaper87#endmeeting15:00
kairatheh15:00
kairatthanks15:00
*** rbak_ has joined #openstack-meeting-415:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Thu Feb 25 15:00:11 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2016/glance.2016-02-25-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2016/glance.2016-02-25-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2016/glance.2016-02-25-14.00.log.html15:00
*** TravT_ has joined #openstack-meeting-415:00
*** mclaren has quit IRC15:00
*** bunting has left #openstack-meeting-415:00
*** TravT_ is now known as TravT15:01
TravT#startmeeting openstack search15:01
openstackMeeting started Thu Feb 25 15:01:21 2016 UTC and is due to finish in 60 minutes.  The chair is TravT. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** yingjun has joined #openstack-meeting-415:01
*** openstack changes topic to " (Meeting topic: openstack search)"15:01
openstackThe meeting name has been set to 'openstack_search'15:01
*** kairat has left #openstack-meeting-415:01
RickA-HPo/15:01
yingjunhi15:01
TravTo/15:01
*** cemmason has quit IRC15:01
lakshmiSo/15:01
rosmaitao/15:01
lei-zh1o/15:01
nikhilo/15:01
*** tsekiyama has left #openstack-meeting-415:01
sjmc7hey15:01
TravThow is everybody this fine day?15:01
rosmaitabrb ... too much coffee during glance meeting15:02
TravTand that answers that... :-P15:02
*** lei-zh1 has quit IRC15:02
*** sridhar_ram has joined #openstack-meeting-415:02
TravTok, agenda here15:02
TravThttps://etherpad.openstack.org/p/search-team-meeting-agenda15:02
*** rbak has quit IRC15:03
TravT#topic Client Release15:03
*** openstack changes topic to "Client Release (Meeting topic: openstack search)"15:03
*** lei-zh has joined #openstack-meeting-415:03
*** haleyb has joined #openstack-meeting-415:03
TravTFinal release for client libraries: Mar 2 (we will tag no later than March 1 - next Tuesday)15:03
TravTThere are a couple of minor reviews out.15:03
TravTplease take a look15:03
TravTI've also been wondering if we needed any additional doc for it.15:03
*** yamamoto has quit IRC15:04
TravThttps://review.openstack.org/#/q/project:openstack/python-searchlightclient+status:open15:04
sjmc7usage type docs?15:04
TravTyeah15:04
sjmc7i can take a look at what other clients do (and where to put it)15:04
TravTsteve martinelli put in a request for us to do a few extra things on a patch review i put up awhile back15:05
TravThttps://review.openstack.org/#/c/270984/15:05
sjmc7ah, ok. i can take a look today15:05
*** Swami has joined #openstack-meeting-415:05
TravTcool15:06
TravTlooks like might need to modify the patch i already put up. if so, just go ahead and amend15:06
*** spotz_zzz is now known as spotz15:06
*** yamamoto has joined #openstack-meeting-415:06
sjmc7will do15:07
TravTawesome.15:07
*** yamamoto has quit IRC15:07
TravTi'll look to tag on Tuesday, if not Monday15:07
TravT0.215:07
TravT#topic Searchlight Panel status15:07
*** openstack changes topic to "Searchlight Panel status (Meeting topic: openstack search)"15:07
*** salv-orlando has joined #openstack-meeting-415:08
TravTwe presented searchlight concepts with some cool additions on Tuesday at the horizon mid cycle15:08
TravTwent over very well.15:08
TravTwe've landed a couple changes already this week that better enable it.15:08
sjmc7excellent15:08
TravTstill have a few dependency patches to go15:09
sjmc7you’re good at cracking the whip in person! :)15:09
TravT:)15:09
RickA-HPTravT: Are there any blockers to completing this work?15:09
TravTyesterday and today are basically review-a-thons15:09
sjmc7yeah, the midcycles are good for geting crazy amounts of reviews in15:09
TravTsearchlight enablement is on the list of things (among many) that are on the review priority list.15:10
TravTgetting the panel itself in will take a FFE on horizon.15:10
sjmc7it’s almost better at the end of a cycle; gives some time to avoid the backlog of reviews piling up before release15:10
TravTi hadn't formally requested that yet15:10
TravTbut will probably do that today15:10
TravTi have not created the repo (in case it doesn't go in)15:10
sjmc7we can do that quickly if need be15:11
TravTjust been too busy.15:11
sjmc7or i can do it15:11
TravTyeah, i think we'll know by tomorrow15:11
sjmc7i feel like a secretary15:11
TravTi'd rather think of you as superman15:11
TravT:)15:11
sjmc7he was a faster typist than me15:11
sjmc7ok, so hold off til the end of the horizon midcycle on that?15:12
TravTyeah, can let you know tomorrow morning.15:12
TravTthere is a swift panel rewrite that will be a heavy focus today.15:12
*** jmccrory has quit IRC15:12
TravTi integrated in the latest swift patches and tested with UI15:12
TravTit works, but has caused me to see some shortcomings with navigation15:13
*** jmccrory has joined #openstack-meeting-415:13
*** numans has quit IRC15:13
TravTbut in talking with r1chardj0n3s who is writing it, he definitely wants to add to his dedicated swift panel the ability to do searches with searchlight15:14
sjmc7as you know i’ve been talking to the swift team about this too15:14
TravTbut that would be newton to integrate that15:14
sjmc7they seem more open to discussing adding notifications to swift core than was the case in tokyo15:14
TravTyes, i mentioned this to him and he said he has a swift core he works with. he said he'd mention it to him as well.15:15
*** sigmavirus24_awa is now known as sigmavirus2415:15
*** salv-orlando has quit IRC15:15
TravTi'll try to talk to him more about that15:15
sjmc7ok. i’ve spoken to HP’s team so they keep an ear open at the swift meetup next week15:15
TravTcool15:15
sjmc7on the plus side, the patch i have does seem to work15:15
TravTlakshmiS: your patch doesn't seem to actually even try to listen to the notification steve's patch generates15:16
TravTright?15:16
TravTor did i miss something?15:16
*** nkrinner has quit IRC15:16
lakshmiSyeah its not linked yet. will update the patch today15:16
sjmc7ok. let me know if i need to tweak anything with it, it’s not set in stone15:16
TravTok15:18
TravTthat's all i have for search panel.  the mid cycle has been very productive.  great group of people at it.15:18
TravT#topic REVIEWS!!!!15:19
*** openstack changes topic to "REVIEWS!!!! (Meeting topic: openstack search)"15:19
sjmc7haha15:19
TravT    https://review.openstack.org/#/q/project:%255E.*searchlight.*+status:open,n,z15:19
TravTLet's just pound these out15:19
TravTthere are some small easies ones15:19
rosmaitaok, which to start wiht?15:19
RickA-HPI'm rebasing the Zero Downtime patch and will update it today.15:19
*** ajmiller has joined #openstack-meeting-415:20
TravTThis is priority order I propose15:20
*** baohua has quit IRC15:20
TravT    Can we do a virtual (using hangouts possibly review hackathon on 3/1/2016 - http://everytimezone.com/#2016-3-1,180,cn3)15:20
TravT    Remove extra infomation from ID field15:20
TravT    Fix role based indexing for designate15:20
TravT    Zero Downtime Re-indexing changes.15:20
TravT    Per resource policy control15:20
TravT    Neutron15:20
TravT    Cinder15:20
TravT    Swift15:20
TravT    Zaqar notification forwarding15:20
TravTFirst one just because it is small15:20
*** galstrom_zzz is now known as galstrom15:20
TravTget it out of the way15:21
TravTbut let's tackle some now15:21
TravTand i propose at review-a-thon next Tuesday at the time I listed15:21
sjmc7yep, i can do that15:22
RickA-HPThe review-a-thon works for me.15:22
*** gongysh_ has quit IRC15:22
*** Steap has left #openstack-meeting-415:22
*** blahRus has joined #openstack-meeting-415:22
rosmaitai can attend review-a-thon, but probably only intermittently15:23
*** klamath_ has joined #openstack-meeting-415:24
TravTok, i can do hour later too15:24
TravTanyway, i guess just start looking over reviews above and we can chat as needed15:25
sjmc7yingjun: you’re right, my suggestion on https://review.openstack.org/#/c/283424 was terrible :)15:26
*** spotz is now known as spotz_zzz15:26
*** klamath has quit IRC15:26
yingjunso i take your second suggestion, ensure _source[‘id’] always there15:27
sjmc7yep - given that it should always now be there, could line 117 be shortened?15:28
sjmc7i guess it’s a little safer that way if there is no id defined15:28
sjmc7either way - this looks good to me, will test it again quickly15:28
yingjunit could be15:29
yingjunyeah15:29
sjmc7not really a big deal15:29
*** Jeffrey4l has quit IRC15:31
sjmc7this works fine; i’m happy to +2 it as it is15:31
*** iceyao_ has joined #openstack-meeting-415:31
yingjunok, thanks15:31
*** iceyao has quit IRC15:32
TravTi looked at the code this morning as well.15:32
*** spotz_zzz is now known as spotz15:32
TravTwas waiting for your input steve15:33
sjmc7i’m honoured15:33
TravTsince you had the concerns.15:33
*** armax has joined #openstack-meeting-415:33
sjmc7yeah, i’m fine with it - it’s the same approach you’re using in the UI?15:33
sjmc7i think we can make it part of the contract that there’s always an “id” field15:34
*** zeih has joined #openstack-meeting-415:34
TravTwell, ui falls back to using the _id15:34
*** xingchao has joined #openstack-meeting-415:34
TravTbut prefers source.id15:34
*** prithiv has quit IRC15:34
TravTthe table row generation needs a unique identifier15:34
sjmc7would you be happier doing that in the CLI too?15:34
TravTi don't know if CLI needs it for same reason UI needs something15:35
sjmc7right now it would make no difference; everything has an id. conceivably we might have something in the future that doesn’t15:35
sjmc7no, it’s just for display15:35
*** galstrom is now known as galstrom_zzz15:35
TravTyeah, see in angular when you ng-repeat, if you have a unique identifier that you can track by, it improves performance when updating search results15:36
TravTso, i have to have something in the id field that is unique15:36
TravTor else it will just break and leave you angry and depressed.15:36
TravT:)15:36
*** sdake has joined #openstack-meeting-415:37
sjmc7:)  i think if we can say there will always be a source[“id”] then the cli patch is good15:37
sjmc7otherwise maybe we need the fallback logic15:38
*** iceyao_ has quit IRC15:38
TravTif it makes sense to add in a safeguard, then we could15:38
*** zeih has quit IRC15:38
TravT#chair sjmc715:40
openstackCurrent chairs: TravT sjmc715:40
*** cbits has joined #openstack-meeting-415:40
TravTsjmc7 i have to leave in a couple minutes15:40
TravTi'm the carpool driver to the horizon meeting15:41
sjmc7i’m drunk with power15:41
TravTuse it wisely15:41
*** sdake_ has joined #openstack-meeting-415:41
rosmaitajust don't be drunk with driving15:42
*** sdake has quit IRC15:42
sjmc7ok. we’ve got 20 minutes of everyone in the same place, so if anyone has questions about any of those reviews this is a great time to ask15:42
sjmc7rosmaita: i work from home, i don’t leave the house monday to friday, so no chance of that15:42
rosmaitadid you ever see the move "Raw Deal"? "You should not drink and bake!"15:43
sjmc7hahaha15:44
sjmc7no, that cultural touchstone passed me by15:44
rosmaitayou need to see it, arnold's best movie, lots of casablanca references15:44
rosmaitaplus, they never explain why this small-town sheriff has an outrageous austrian accent15:45
sjmc7i don’t know how i missed it15:45
rosmaitaok, so at least i did a movie review15:46
*** raofei has quit IRC15:48
*** MarkAtwood has joined #openstack-meeting-415:48
*** izaakk has joined #openstack-meeting-415:49
*** raofei has joined #openstack-meeting-415:49
TravTthx guys, i'm out of here.  thanks a ton for any reviews you can do!15:49
rosmaitaTravT: enjoy the midcycle15:50
* TravT off to horizon mid-cycle15:50
rosmaitaand drive carefully15:50
TravTthx15:50
*** TravT has quit IRC15:50
*** sshnaidm has joined #openstack-meeting-415:50
*** raddaoui has joined #openstack-meeting-415:51
sjmc7ok, if nobody’s got anything else they want to discuss i guess we can end here15:52
rosmaitaok, see you tuesday, i guess15:53
RickA-HPI have nothing else.15:53
sjmc7aye. we’ll be in #openstack-searchlight if there’s anything else15:53
sjmc7thanks all!15:53
*** RickA-HP has quit IRC15:54
sjmc7#endmeeting15:54
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:54
openstackMeeting ended Thu Feb 25 15:54:12 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_search/2016/openstack_search.2016-02-25-15.01.html15:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_search/2016/openstack_search.2016-02-25-15.01.txt15:54
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_search/2016/openstack_search.2016-02-25-15.01.log.html15:54
*** sjmc7 has left #openstack-meeting-415:54
*** lei-zh has left #openstack-meeting-415:55
*** daneyon has joined #openstack-meeting-415:56
*** daneyon_ has joined #openstack-meeting-415:57
*** sdake has joined #openstack-meeting-415:57
*** sdake_ has quit IRC15:58
*** angdraug has joined #openstack-meeting-415:58
*** yingjun has left #openstack-meeting-415:59
*** automagically has joined #openstack-meeting-415:59
*** KLevenstein has joined #openstack-meeting-416:00
*** mattt has joined #openstack-meeting-416:00
odyssey4me#startmeeting OpenStack-Ansible16:00
openstackMeeting started Thu Feb 25 16:00:37 2016 UTC and is due to finish in 60 minutes.  The chair is odyssey4me. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: OpenStack-Ansible)"16:00
openstackThe meeting name has been set to 'openstack_ansible'16:00
odyssey4me#topic Agenda and roll-call16:00
*** openstack changes topic to "Agenda and roll-call (Meeting topic: OpenStack-Ansible)"16:00
*** daneyon has quit IRC16:00
automagicallyo/16:00
spotz\o/16:00
izaakko/16:00
cloudnullo/16:01
palendaeo/16:01
jmccroryo/16:01
*** lakshmiS has quit IRC16:01
raddaouio/16:01
odyssey4me#link https://wiki.openstack.org/wiki/Meetings/openstack-ansible#Agenda_for_next_meeting16:02
KLevensteino/16:02
*** jmckind has joined #openstack-meeting-416:02
mattt\o16:02
*** prometheanfire has joined #openstack-meeting-416:03
prometheanfirehi16:04
odyssey4meHi everyone, welcome back after the week of absence due to the mid cycles.16:04
odyssey4meThere were no action items in our last meeting.16:05
odyssey4me#topic Define core team expectations/Add non-Rackspace cores16:05
*** openstack changes topic to "Define core team expectations/Add non-Rackspace cores (Meeting topic: OpenStack-Ansible)"16:05
*** prithiv has joined #openstack-meeting-416:05
* odyssey4me hands the mic to automagically :)16:05
automagicallyodyssey4me: Thanks! I added an agenda item about core expectations and the addition of non-Rackspace cores as I and others outside of Rackspace have a growing dependency on the fine work that you Rackers and the rest of the community have done here16:06
*** dims has quit IRC16:06
automagicallySo, wanted to raise the issue of documenting expectations for core contributors and assess the groups thinking on recruiting/adding Rackspace-external cores16:07
automagicallyAction items would be: wiki doc explaining core responsibilities and process for gaining/losing core status16:07
automagicallyThoughts?16:07
odyssey4meI like the idea of documenting expectations for cores and reviewers overall. I've also been wanting to document expectations of the PTL. We can perhaps also document what the launchpad drivers group should be doing.16:07
*** yamamoto has joined #openstack-meeting-416:08
hughsaunderso/16:08
odyssey4meI'd prefer it not to be wiki doc - I'd rather see it join the contributor guidelines in the docs.16:08
palendaeautomagically: I am all for people outside of Rackspace becoming core, but I do think you're right that the expectations need to be written down16:08
odyssey4meI'd like the wiki to largely be a place that points at the docs we have.16:08
automagicallyodyssey4me: Location matters much less to me than getting it agreed upon and written down16:08
*** jmckind has quit IRC16:09
spotzThere's definitely groups out there who have documented out their criteria already that could be adapted or used for a start16:09
odyssey4meI've also been wanting to suggest two new cores to the team. I have discussed them with the existing core members and there is a general agreement of approval.16:09
automagicallyAny ideas about how to best recruit/retain/attract cores from outside Rackspace?16:09
*** jmckind has joined #openstack-meeting-416:09
automagicallyI’m thinking the Austin event could be a good time/place to recruit16:10
odyssey4meAre we happy to discuss that now quickly, or would it be preferred that it's done through the ML (as is traditional).16:10
automagicallyspotz: Agreed16:10
automagicallyBelieve you and I discussed https://wiki.openstack.org/wiki/Heat/CoreTeam as a useful example16:10
palendaeodyssey4me: I'd caution that the cores probably want to discuss before nominating someone on the public ML who might not get approved16:10
*** SimonChung1 has quit IRC16:11
matttmy personal opinion is that this project needs to be a bit more flexible and fluid when it comes to cores16:11
odyssey4mein terms of recruiting cores - all cores need to start by being involved in the community first - we recruit new contributors at any events we are involved at16:11
palendaeThat's caused embarassment and hard feelings in the past16:11
mattti don't think we're in a position to start setting down hard requirements16:11
odyssey4meI'd be happy to have a session to discuss how better to grow our community at the summit16:11
*** sdake_ has joined #openstack-meeting-416:11
*** sdake_ has quit IRC16:11
*** daneyon_ has quit IRC16:11
odyssey4meI'd like this to be a group effort16:11
palendaemattt: I don't think there should be hard requirements, but definitely a target for people who want to be core16:11
*** sdake has quit IRC16:11
*** sdake_ has joined #openstack-meeting-416:12
automagicallypalendae: +116:12
odyssey4meyeah, not hard requirements - just expectation setting16:12
palendaemattt: to help answer, "What should I do to get that status?" Be active in reviews, contribute code, etc16:12
hughsaunders+1 for more cores, regardless of employer, we should also be working towards the diverse-affiliation tag16:12
matttpalendae: i think you summarised it very well right there :)16:12
automagicallyhughsaunders: How would we do so?16:12
spotz+1 palendae and hughsaunders16:12
odyssey4mebeing core is not a status - it is a responsibility and a role of service to the community16:12
automagicallyre: diverse-affiliation16:12
palendaeodyssey4me's point is accurate16:12
odyssey4mehughsaunders +116:12
palendaeThere is a bit more demand for a core reviewer16:13
*** yamamoto has quit IRC16:13
hughsaundersautomagically: https://github.com/openstack/governance/blob/master/reference/tags/team_diverse-affiliation.rst16:13
automagicallythx16:13
automagicallyAh, so that was very much my goal in raising this agenda topic16:13
automagicallyNice to see it formalized in the manner within the broader community16:14
odyssey4mehughsaunders automagically or better: https://governance.openstack.org/reference/tags/index.html16:14
automagicallySo #agreed that core contributor expectations be added to the project doc16:15
cloudnull+116:15
matttcan we move forward with bringing people on as cores or do we need further discussions, documentation, etc. in place first?16:15
mattti'd really love to see us adding cores sooner rather than later16:16
odyssey4mecan someone do some research into prior art and propose something for review - then we can adjust to suit us?16:16
cloudnullmattt:  +116:16
automagically#action - update contributor guidelines to describe core responsibilities/expectations and membership process16:16
*** fnaval has quit IRC16:16
cloudnullodyssey4me: https://wiki.openstack.org/wiki/Nova/CoreTeam#Membership_Expectations16:16
odyssey4meautomagically you need to have the first word be the person assigned to do so :)16:16
automagicallymattt: My belief is that it may be hard to accept a nomination without a good understanding of the level of responsibility16:17
spotzodyssey4me I think that link to Heat's the automagically posted is pretty good. I can look for the Doc team's16:17
odyssey4me#link http://docs.openstack.org/developer/neutron/policies/core-reviewers.html16:17
matttautomagically: but i'm also not sure all our cores at the moment would meet any sort of level ... which is why i say we have to be more fluid16:17
matttand as the project grows and our cores become more diverse we put down a proper framework for what this involves16:17
automagicallymattt: I’m good with the expectations being lax given the reality of current cores16:17
odyssey4meyeah, no worries - let's deal with the details in review16:18
automagicallyodyssey4me: Thx for the tip. So, who wants to own the action item on doc. spotz? you?16:18
odyssey4meautomagically can you put a suggested page together?16:18
odyssey4meotherwise spotz :)16:18
automagicallyautomagically #action automagically will submit patchset for review documenting core expectations16:18
automagicallyWhoops, thats a lot of automagicallys ;)16:19
spotzautomagically poke if you need help16:19
hughsaunderssuch magic so auto16:19
odyssey4mealright, let's move on from that16:19
automagicallyHappy to pass the mic, think the conversation went in a very useful direction16:19
odyssey4me#topic New core proposals16:19
*** openstack changes topic to "New core proposals (Meeting topic: OpenStack-Ansible)"16:19
odyssey4meI'd like to propose both jmccrory and automagically as new cores for OSA.16:19
hughsaundersI'd contest that this topic is the same as the last one.16:20
odyssey4meThey've both been regular committers, reviewers and been very helpful in identifying and fixing issues.16:20
cloudnulljmccrory: +116:20
cloudnullautomagically: +116:20
andymccr+1 on both16:21
cloudnullI think they'd both make fine additions to the core team.16:21
spotzhughsaunders last one was proceedure/policy this one is voting16:21
palendaeNot sure if only cores get a vote, but no objections to either16:22
hughsaunders+1 +116:22
mattti'm +1 on both also16:23
*** cemmason has joined #openstack-meeting-416:23
odyssey4med34dh0r53 and stevelle aren't active/present, but that's a majority16:23
odyssey4meso, welcome to both of you to the core team - I'll do the formalities afterwards?16:24
* automagically whoot16:24
jmccrorythanks16:24
odyssey4me#topic Pinning pip and related dependencies16:25
*** openstack changes topic to "Pinning pip and related dependencies (Meeting topic: OpenStack-Ansible)"16:25
odyssey4me#link https://etherpad.openstack.org/p/openstack-ansible-pip-conundrum16:25
* cloudnull high fives jmccrory and automagically16:25
spotzgrats guys16:26
matttjmccrory automagically welcome !16:26
odyssey4meOK, down to the business of improving repeatability.16:26
automagicallyLooking forward to continuing to contribute to such a great project16:26
odyssey4mein recent days we hit two issues which uncovered a failing in our build methods16:26
odyssey4methe genral idea we aim for is to ensure that whenever you build a tag, the result is the same16:27
*** pmesserli has quit IRC16:27
odyssey4metoday we are failing in terms of the repo server build and everything related to python bits before that16:27
*** belmoreira has quit IRC16:27
*** pmesserli has joined #openstack-meeting-416:27
odyssey4mein the solution options I've outlined some suggestion -but I'd like more discussion and ideas16:27
odyssey4mequestions, comments, etc16:28
odyssey4meplease add to the etherpad16:28
*** pmesserli has quit IRC16:28
automagicallyThe first solution in pip_install role seems like the cleanest16:28
*** iyamahat_ has quit IRC16:28
*** pmesserli has joined #openstack-meeting-416:28
*** fnaval has joined #openstack-meeting-416:28
odyssey4meit covers pip, wheels and setuptools - but it's a hard set. I'd like a neater way to do this.16:29
odyssey4methe first is probably something we need as a stop-gap, the second seems like a better long term view16:29
odyssey4mesomething that requires as little maintenance as possible is essential16:30
automagicallyodyssey4me: +1 on the low maintenance aspect16:30
*** pmesserli has quit IRC16:30
cloudnullcant we add this to the global-requirements.txt files in the main repo for the three branches16:30
*** pmesserli has joined #openstack-meeting-416:30
automagicallyThe second solution begs the question of how a user/deployer might override if needed16:31
cloudnullthen we dont have to mess with the package versions at the role level16:31
odyssey4mecloudnull the repo server install doesn't use any of the requirements set out anywhere16:31
odyssey4meit only uses the bits in its own pip_packages list16:31
*** bpokorny has joined #openstack-meeting-416:31
odyssey4mewe could change that16:32
cloudnullright. but if we set it in the global requirements pins it would get picked up everywhere as it pertains to an OSA isntall.16:32
odyssey4mebut maintaining requirements for the repo server which conflict with openstack requirements is also not ideal16:32
*** emagana has joined #openstack-meeting-416:32
odyssey4mecloudnull so the pinning is not actually an issue for any of the packages once the repo is built16:32
odyssey4methe issue is in building the repo server itself16:33
cloudnullseems like the simiplest solution would be to add the lines here https://github.com/openstack/openstack-ansible/blob/master/global-requirement-pins.txt16:33
odyssey4meit does not use global requirements, upper constraints, or anything like that16:33
cloudnullit does16:33
odyssey4mecloudnull how so?16:33
cloudnullthe lookup plugin py_pkgs indexes everything which instructrs the repo16:33
odyssey4methat is in building the repo, not installing the repo server16:34
matttcloudnull: installing packages in the repo_server prior to building stuff16:34
matttie. to be able to build wheels you need wheel installed16:34
jmccrorythese https://github.com/openstack/openstack-ansible-repo_server/blob/master/defaults/main.yml#L83-L92 ?16:34
matttall those packages at the minute are unconstrained16:34
hughsaundersjmccrory: yes16:34
cloudnullah i see now.16:35
odyssey4meso my suggestion is to do an upper constraints style thing16:35
odyssey4mewe take the output of a successful build, and publish it on openstack infrastructure16:36
*** sdake_ is now known as sdake16:36
*** cemmason has quit IRC16:36
*** cemmason1 has joined #openstack-meeting-416:36
odyssey4methe repo install then needs to use that as an upper constraint16:36
logan-i would much rather see it included in the osa repo than published elsewhere and pulled down. easier for operators to override and also makes life easier for operators doing offline deployments.16:37
automagicallylogan-: +116:37
cloudnulllogan-:  +116:37
* cloudnull was just writing that16:37
automagicallyI think we definitely need a solution that allows override capabilities similar to what we have elsewhere16:37
automagicallyThat said, I like the general approach of the upper bound constraints16:37
odyssey4methen we have to regularly patch it to keep it fresh16:38
cloudnullI think thats just something we have to do .16:38
odyssey4memy method can easily allow it to be optional -as was noted in the etherpad16:38
automagicallyWIth the force var?16:38
*** salv-orlando has joined #openstack-meeting-416:38
matttso is this effort better than just pinning a couple of packages in teh repo server role?16:38
odyssey4meI'd rather stay away from implementing caps - especially ones that duplicate those in openstack.16:38
matttwill it really result in playing whack-a-mole16:39
automagicallyThinking through this a bit, as a deployer how would I test a new set of constraints16:39
*** hdaniel has quit IRC16:39
automagicallyJust override the requirements file location var?16:39
odyssey4mesimple - set the var that ignores the upstream constraints16:39
automagicallyRight, but I’m talking about testing a new set of constraints16:39
odyssey4meand the location would be a var too, so you could set differing constraints16:39
odyssey4memattt the trouble with pinning that package list is that it misses pinning the deps of those packages - that is what creates the whack-a-mole situation16:40
automagicallyCould we use a lookup with the requirements url, so if I didn’t want to publish my new set of requirements, I can just override the var with a list?16:40
matttodyssey4me: in the last 2 days the issues have been with those packages specifically tho16:40
cloudnullI think we could add the same constraints in the repo server role as whats in the pip install role and be good.16:41
automagically^ thinking out loud obviously there16:41
odyssey4meI would rather we use our final complete pip repo version list as an upper constraint - it contains absolutely everything we use16:41
matttwe need to be careful of over-engineering this16:41
matttbecause we've hit 2 problems in 2 days16:41
odyssey4mecloudnull whack-a-mole again then for the next time we find a gap like this16:41
mattti don't recall this biting us until then16:41
*** salv-orlando has quit IRC16:41
*** cemmason has joined #openstack-meeting-416:41
*** paul-carlton1 has quit IRC16:41
cloudnullI'd like to get the requirement / constraint files published too but idk tat it needs to be an integral part of the build process16:41
*** salv-orlando has joined #openstack-meeting-416:41
*** cemmason1 has quit IRC16:42
cloudnulland if we pin them in the pip install role then the items here should already be resolved https://github.com/openstack/openstack-ansible-repo_server/blob/master/defaults/main.yml#L83-L92 IE wheel, setuptools.16:43
odyssey4mewe've had a lot of feedback from the infra and pypa crew that pinning these packages is not a good idea.16:43
odyssey4mebut we also need to ensure that we build the same thing every time and can rely on things to work16:43
matttbut you're pinning them using a constraints file right16:43
*** sridhar_ram has quit IRC16:43
mattti don't see the difference16:43
odyssey4mewhich is why I like the idea of updating requirements after successful builds16:43
odyssey4meor perhaps doing a nightly that updates the thing16:43
odyssey4memattt the difference is that one gets updated manually by a review - the other is updated dynamically and automatically16:44
cloudnullas long as we're locking pip to a specific version i think we have to pin the packages and doing it in the pip install role makes the most sense16:44
matttwell16:44
odyssey4meok, if that's the way we think is best - that's fine16:45
matttis there value outside of this specific problem to have our packages captured somewhere outside the env ?16:45
matttif there is we should do this and we can use it when we install teh repo server16:45
odyssey4mebear in mind that we then end up doing things differently from upstream16:45
odyssey4meopenstack tests all use the latest pip and the upper constraints for the rest16:45
palendaeAre they using pip8 now?16:46
odyssey4mepalendae yes16:46
matttyeah we're already doing something different now then16:46
palendaeThey must cause it breaks every time a new pip comes out16:46
odyssey4mefor stable/kilo and above16:46
palendaeYeah, makes sense16:46
odyssey4meyes - which is why sigmavirus24 has already adviced us not to do what we're doing16:46
cloudnulllooking at the global requirements the only named constraint they have is wheel16:46
odyssey4meas have the infra crew16:47
cloudnullhttps://github.com/openstack/requirements/blob/master/upper-constraints.txt16:47
cloudnullhttps://github.com/openstack/requirements/blob/master/upper-constraints.txt#L37616:47
odyssey4mecloudnull g-r has pip too16:47
cloudnullwhich is unpinned16:47
cloudnullhttps://github.com/openstack/requirements/blob/master/global-requirements.txt#L13916:47
sigmavirus24right16:47
*** vikram_ has quit IRC16:48
sigmavirus24it looks as though we're leaning towards uncapping pip?16:48
cloudnullso i dont see the harm in pinning the other bits so long as we're allowing pip to move forward16:48
cloudnull*we're NOT allowing ...16:48
odyssey4mesigmavirus24 no, the majority at this point want to cap pip, setuptools and wheel16:48
hughsaunderscloudnull: but thats how we ended up with the wheel > pip problem16:48
* sigmavirus24 shrugs16:48
sigmavirus24Have fun figuring out why things break when those are capped with upstream having them uncapped16:49
odyssey4mesigmavirus24 I would like to uncap these things and use a published upper constraint that's updated by the build process dynamically16:49
cloudnullhughsaunders:  idk if this is a problem if we're using the latest pip 8 -- sigmavirus24?16:49
*** cemmason1 has joined #openstack-meeting-416:49
sigmavirus24cloudnull: if what specifically is a problem?16:49
sigmavirus24if anything, I'd advocate blacklisting known bad versions16:49
matttsigmavirus24: well they break when you leave them uncapped also16:49
matttso what to do16:49
sigmavirus24(especially since the pip team is responsive to openstack breakage)16:49
odyssey4mesigmavirus24 which is already done upstream16:49
*** cemmason has quit IRC16:50
sigmavirus24mattt: every version of pip has broken us?16:50
matttsigmavirus24: no, but setuptools wasn't constrained and that broke a bunch of things yesterday16:50
mattti don't see the issue if you pin the three in tandem16:51
mattthand by tandem i mean the latest working version of all three at a point in time16:51
sigmavirus24mattt: we can constrain the world in conflict with upstream openstack. we could help a resource starved project (setuptools). we could use an upper-constraints-like system as  odyssey4me suggested16:51
odyssey4meSo the issue I have with capping is simple - openstack's testing all uses the current versions. There are no caps. If we do not follow that model, then we assume full responsibility of testing everything that the rest of openstack-ci has tested.16:51
*** minwang2 has joined #openstack-meeting-416:52
sigmavirus24mattt: the thing is that bounding them all in tandem is kind of silly since they're all independent pieces16:52
sigmavirus24pip needs a modernish version of setuptools which doesn't have to be the latest16:52
sigmavirus24we need a version of wheel that will generate wheel names that our version of pip can install16:52
matttright because we pinned pip without doing the same to wheel and setuptools16:53
matttwhich is why we hit that issue16:53
sigmavirus24they're related, absolutely, but not deeply tied together by any stretch of the imagination. Is the problem with setuptools tracked on their issue tracker? Have we tried fixing things?16:53
matttwheel was updated and wasn't compatible w/ pip16:53
cloudnullsigmavirus24:  what would be the best solutuin knowing that we have locked ourselves to pip7.x ?16:53
*** markvan has quit IRC16:53
odyssey4mesigmavirus24 a patch is in progress16:53
sigmavirus24cloudnull: we can cap the world, but it's a smell given that openstack itself isn't doing this16:53
sigmavirus24I would advocate for blacklists16:53
odyssey4mecloudnull we should not be locking ourselves to pip 7.x is the point16:53
*** bobh has joined #openstack-meeting-416:53
sigmavirus24pip!=8.0.0,!=8.0.116:53
matttso why did we pin pip to begin with and what could we have done to avoid that?16:53
matttbecause that decision is the source of this problem here16:54
cloudnullodyssey4me:  we currently are though .16:54
sigmavirus24mattt: 8.0.0 broke argparse16:54
odyssey4meyes, but it raised a broader problem which is that what we deply today is not what we deploy tomorrow16:54
*** dims has joined #openstack-meeting-416:54
sigmavirus24mattt: so the thing is that 8.0.0 wanted to remove support for uninstalling distutils installed packages16:54
*** markvan has joined #openstack-meeting-416:54
odyssey4methis is why I'd like to implement something to close the gap16:54
*** amotoki has joined #openstack-meeting-416:54
sigmavirus24that broke installing things with pip that might have installations pre-existing based on standard library or system packaging16:55
odyssey4mesimply blacklisting does not solve that issue16:55
*** Farhad has joined #openstack-meeting-416:55
cloudnullwhich would have to be an upper cap on setuptools and wheel so long as we have this https://github.com/openstack/openstack-ansible-pip_install/blob/master/defaults/main.yml#L2716:55
*** cemmason has joined #openstack-meeting-416:55
sigmavirus24odyssey4me: the issue of what we deploy today is not what we deploy tomorrow for the same version?16:55
odyssey4mepublishing the full pip requirements file from our repo per build will result in each tag having that set in stone16:55
*** minwang2 has quit IRC16:55
*** cemmason1 has quit IRC16:55
sigmavirus24odyssey4me: in that case, why not have vars that are generated when we create a tag that represent the versions of everything when that tag was created16:55
*** cathy_ has joined #openstack-meeting-416:56
odyssey4methis is the best way to ensure that each tag deployed will always result in the same thing16:56
matttodyssey4me: if you want to take that stance it has to be applied right through openstack-ansible, not just when it comes to deploying a specific container16:56
sigmavirus24odyssey4me: capping will?16:56
*** qwebirc47365 has joined #openstack-meeting-416:56
automagicallysigmavirus24: Hmm, interesting middle ground on the vars generation16:56
*** javeriak has joined #openstack-meeting-416:56
odyssey4mesigmavirus24 I'm suggesting something similar to what upper-constraints does for devstack16:56
sigmavirus24odyssey4me: I think we have similar ideas16:56
*** fsunaval has joined #openstack-meeting-416:56
odyssey4meif we can automate vars generation on every sha jump, tha'td do fine too16:56
sigmavirus24I'm saying that we should let the gate do whatever. Only when we tag the release should we update those constraints.16:57
*** iyamahat_ has joined #openstack-meeting-416:57
sigmavirus24See I also disagree with our sha bumps being a thing on stable branches that happens *after a tag* but that's just me16:57
sigmavirus24I know I'm the only person who thinks we should trust the small team of dedicated upstream stable maintainers16:57
odyssey4mewe're almost out of time16:57
sigmavirus24(This is also why I've kept out of these discussions)16:58
odyssey4meso we need to close off and continue in #openstack-ansible16:58
*** yamahata has joined #openstack-meeting-416:58
cloudnullcheers everyone !16:58
odyssey4meThank you all for your time and participation.16:58
*** LouisF has joined #openstack-meeting-416:59
odyssey4me#endmeeting#endmeeting16:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:59
openstackMeeting ended Thu Feb 25 16:59:43 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible/2016/openstack_ansible.2016-02-25-16.00.html16:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible/2016/openstack_ansible.2016-02-25-16.00.txt16:59
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible/2016/openstack_ansible.2016-02-25-16.00.log.html16:59
cathy_#startmeeting service_chaining17:00
openstackMeeting started Thu Feb 25 17:00:12 2016 UTC and is due to finish in 60 minutes.  The chair is cathy_. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: service_chaining)"17:00
openstackThe meeting name has been set to 'service_chaining'17:00
*** javeriak_ has joined #openstack-meeting-417:00
LouisFhi cathy_17:00
cathy_hi LouisF17:00
fsunavalhi cathy_17:00
cathy_hi fsunaval17:01
LouisFfsunaval: hi17:01
*** javeriak has quit IRC17:01
*** minwang2 has joined #openstack-meeting-417:01
fsunavalHi LouisF17:01
*** prometheanfire has left #openstack-meeting-417:01
*** vikram_ has joined #openstack-meeting-417:01
*** johnsom has joined #openstack-meeting-417:01
*** mohankumar_ has joined #openstack-meeting-417:01
vikram_hi17:02
cathy_hi vikram_ johnsom mohankumar_17:02
mohankumar_hi17:02
johnsomo/17:02
cathy_hi minwang217:02
minwang2hi17:03
*** singlethink has joined #openstack-meeting-417:03
*** raddaoui has quit IRC17:03
cathy_I have two topics for today. Any topic you would like to discuss today?17:03
*** raddaoui has joined #openstack-meeting-417:04
*** thorst is now known as thorst_afk17:04
*** automagically has left #openstack-meeting-417:04
pcarverhi. I'm in simultaneous voice call.17:04
cathy_hi pcarver raddaoui17:04
cathy_#topic propose for governance under big tent17:05
*** openstack changes topic to "propose for governance under big tent (Meeting topic: service_chaining)"17:05
mohankumar_cathy_ : could you elaborate the topic ?17:06
cathy_Given recent discussion on the change of Neutron stadium scope, we are thinking about proposing the SFC project under OpenStack Big Tent governance17:07
vikram_cathy_: means it won't be no longer neutron-official project?17:07
johnsomAlmost every project under neutron will no longer be an "neutron-official project".17:08
cathy_mohankumar_: Last few weeks, there have been heated discussion on Neutron big stadium projects. Basically all big stadium projects are not out of Neutron governance17:08
johnsomhttps://review.openstack.org/#/c/281628/17:08
johnsom#link https://review.openstack.org/#/c/281628/17:08
*** yamamoto has joined #openstack-meeting-417:09
cathy_johnsom: thanks for posting the links!17:09
pcarverThere seems to be a circular line of reasoning that only projects worked on by "the Neutron team" will be part of Neutron, but the definition of "the Neutron team" is "the people who work on projects that are part of Neutron"17:10
LouisFpcarver: +117:10
vikram_ok17:10
*** numans has joined #openstack-meeting-417:11
vikram_I can find Kuryr move to big tent also17:11
vikram_https://review.openstack.org/#/c/280522/17:11
cathy_Yes, SFC and L2GW seem to be the last few that people are still debating, but given that Neutron is being stripped to a bare minimum according to the patch, we are thinking about applying for governance under OpenStack big tent.17:12
LouisFthe discussion is around the overlap of neutron core members involved in sub-projects17:12
*** thorst_afk is now known as thorst17:12
pcarverSo basically the "big tent" still exists but the "Neutron stadium" doesn't17:12
cathy_Yes, so anyone has objection to applying networking-sfc for governance under OpenStack Big Tent?17:13
pcarverSo if SFC isn't a core part of Neutron we should get it categorized as a distinct "big tent" project17:13
amotokisurprisingly enough I am still waking up.  kuryr is a bit different situation. it is a consumer of neutron API.17:13
pcarverI suppose that means we need to come up with a cooler name than networking-sfc17:14
cathy_pcarver: yes17:14
cathy_amotoki: welcome back!17:14
amotokihehe17:14
*** yamamoto has quit IRC17:14
vikram_pcarver: +117:14
pcarverSo everyone start thinking analogies: Cinder is to block as ? is to chain17:14
LouisFdragonflow which is very closely related to neutron is also now in big tent17:14
cathy_amotoki: are you OK with applying for big tent?17:15
vikram_LouisF: Yup.. https://review.openstack.org/#/c/277153/17:15
amotokicathy_: I am not sure on this.17:15
*** prithiv has quit IRC17:16
amotokikuryr is a consumer of neutorn api and dragonflow is one of back-ends of neutron.17:16
*** paul-carlton1 has joined #openstack-meeting-417:16
cathy_amotoki: if not big tent, what other governance given existing Neutron inclusion result17:16
amotokii haven't followed the dissussion in the reviews of bit-tent inclusion of kuryr and dragonflow.17:17
amotokicathy_: i understand your concern.17:17
amotokiso I don't have a strong opinion just now...17:18
pcarveramotoki: I strongly feel that SFC (and BGPVPN) should be "part of Neutron" because Neutron should own the vendor/backend independent APIs. But there's a strong sentiment that Neutron should be defined by the list of people who contribute to a certain subset of networking functionality.17:18
amotokipcarver: yeah, i know it.17:18
vikram_pcarver: +117:19
vikram_I also have same feeling17:19
pcarverso if the criteria ends up being "who contributes to which repos" then we need to figure out where to place networking-sfc17:19
*** _sarob has joined #openstack-meeting-417:19
amotokii wonder how much of contributor overlapping and variety are required for neutron inclusion.17:19
cathy_amotoki: pcarver for inclusion of Neutron, I would suggest that we take it to the Neutron channel or the Neutron inclusion patch.17:20
cathy_since whatever we discussed here will be have any effect:-)17:20
cathy_Now let's come back to the name of the SFC for Big Tent17:20
pcarvercathy_: I agree and have posted my comments to the patches, but it keeps coming round to the point of who the contributors are.17:21
cathy_pcarver: I know and understand the frustration17:21
vikram_IMO, it's a weird requirement17:21
*** krtaylor has quit IRC17:21
pcarverIf the contributors to networking-sfc don't also contribute to the repos that constitute the "in Neutron" repos then networking-sfc isn't an "in Neutron" repo17:21
amotokii can be involved in the project, but i am not sure how it helps the project.17:22
pcarverof course if the functionality of SFC API were considered a "part of Neutron" then the contributor overlap would be 100% by definition. But it isn't.17:22
LouisFpcarver: also if the neutron cores feel they don't have regular insight into the design and governance of networking-sfc17:24
*** _sarob has quit IRC17:24
vikram_I have a question .... if we have to follow big tent way then do we need to revisit the proposed CLI?17:24
*** xingchao has quit IRC17:24
cathy_amotoki: you were once very involved in this project:-) Now matter whether it is under Neutron Stadium or OpenStack Big Tent, you are always welcomed to be involved:-)17:24
amotokiIMO contributor overlapping is one of big points, but layer overlapping with neutron is also a big point.17:24
pcarveramotoki: what exactly do you mean by "layer"?17:25
cathy_vikram_: no I don't think so. But we are always open to good suggestion17:25
pcarverI do think a high level of modularity should always be an objective regardless of which parts are "in" or "out"17:25
amotokipcarver: (i haven't got an appropriate word)17:25
*** s3wong has joined #openstack-meeting-417:25
*** Swami has quit IRC17:25
s3wongsorry, very late17:26
amotokipcarver: kuryr is a consumer of neutorn api and dragonflow can be a backend of neutorn, but networking-sfc is not .....17:26
vikram_cathy_: I asked this because all our current cli's starts with neutron *17:26
*** stevelle has joined #openstack-meeting-417:26
*** stevelle has left #openstack-meeting-417:26
pcarverso even if networking-sfc is "in Neutron" I think we're on the right path of plugging in via extension mechanisms that easily allow deployers to add or remove parts17:26
*** minwang2 has quit IRC17:26
amotokiwe are covering the same layer (API) as neutron covers.17:26
cathy_vikram_: there is always space for API enhancement/extension. Actually for second phase feature support, we will extend the API. Good thing is that the API already has place holders for the extensions17:26
cathy_vikram_: OK, I see what you mean. But I guess that is OK. Even we need to change, it is not a big deal17:27
pcarveramotoki: I agree on that. I view networking-sfc as extending the functionality of the Neutron API17:27
vikram_cathy_: ok .. just a query17:27
cathy_s3wong: hi17:27
amotokil2gw, sfc and (possibly bgp stuff) are in the similar situations.17:28
vikram_pcarver: +100017:28
s3wongcathy_: sounds like we are talking about moving out of Neutron to the tent?17:28
LouisFs3wong: yes17:28
*** julim has quit IRC17:28
*** markvan has quit IRC17:28
pcarvers3wong: more specifically, I think we're saying that if we're not allowed to stay in the stadium we'll have to move to the tent17:29
s3wongpcarver, LouisF: I see17:29
cathy_s3wong: yes17:29
cathy_folks, let's come back to the name of project.17:29
amotokias my hat of an operator i would like to see networking-sfc as a part of neutorn. we don't want to see SFC as a different layer :-(17:29
vikram_me to17:30
LouisFamotoki: +117:30
pcarverMy vote is that things that add new networking APIs to Neutron should be part of Neutron, but the discussion is focussing heavily on who the people are who make up the Neutron team17:30
*** markvan has joined #openstack-meeting-417:30
s3wongI agree with pcarver  and amotoki here --- networking-sfc is network plumbing APIs that logically should be part of Neutron17:30
cathy_As to Neutron inclusion, I suggest that we take it to the Neutron patch and post your comments there.17:30
vikram_cathy_: do you have the link handy?17:30
johnsomI think any code that is outside of the core neutron repo is going to be out of neutron17:31
LouisFsuggest we all post comments on that patch17:31
amotokidiscussion here thinks me a lot :-)17:31
cathy_s3wong: amotoki could you post your comments in that Neutron inclusion patch?17:31
cathy_LouisF: +117:31
amotokicathy_: sure17:31
johnsom#link https://review.openstack.org/#/c/281628/17:31
s3wongcathy_: sure17:31
cathy_vikram_: what link?17:31
vikram_johnsom: thanks17:32
johnsomcathy_ Sorry, I have to leave the meeting now, I have a conflict.17:32
vikram_cathy_: johnsomhas provided ;)17:32
cathy_johnsom: thanks17:33
cathy_johnsom: sure.17:33
*** johnsom has left #openstack-meeting-417:33
cathy_any good name suggestion for this project?17:33
*** krtaylor has joined #openstack-meeting-417:33
*** sdake_ has joined #openstack-meeting-417:34
*** zeih has joined #openstack-meeting-417:34
amotokias long as we focus on SFC (service function chaining), networking-sfc sounds good to me. it is clear and describes what we focus on.17:34
vikram_+1 for SFC17:35
cathy_vikram_: sorry I missed that. What is the name?17:35
amotokiisn't it good?17:35
*** rbak__ has joined #openstack-meeting-417:35
cathy_SFC or ServiceFunctionChain?17:35
vikram_cathy_: I was looking for #link https://review.openstack.org/#/c/281628/ , johnsom provided17:36
pcarveramotoki: It's too descriptive, unlike most OpenStack project names17:36
vikram_hmmm17:36
Farhadnetworking-sfc or networking-neutron-sfc or neutron-sfc to specifically say we are neutron based17:36
LouisFcatenate, catena (italian for chain)?17:36
amotokihmm.. i got your point, but...17:36
pcarverI like that Cinder relates to block and Glance to images, but most distinct OpenStack projects have a name that is not directly descriptive of what they do.17:36
*** sdake has quit IRC17:36
vikram_SFC might not convey the idea17:37
cathy_pcarver: Actually I think it is good to be descriptive17:37
vikram_I feel little bit of description would be better17:37
amotokiis there any name which assoicate traffic flows? or water flows :-)17:37
cathy_Otherwise new people or users will have a hard time searching for info they need17:37
vikram_amotoki; ;)17:38
cathy_vikram_: +117:38
mohankumar_catena ... lgtm !17:38
pcarvercathy_: I do to, but you have to admit that it's not common for OpenStack project names17:38
*** rbak_ has quit IRC17:38
cathy_pcarver: maybe we can give it a descriptive name. If the TC thinks we should have another name, then we can come up with another one17:38
-amotoki- time keeping. iirc we have another topic in the agenda17:38
vikram_How about "Flow"17:39
*** mfedosin has quit IRC17:39
pcarvercathy_: ok, that's fine with me17:39
vikram_I may sound stupid ;)17:39
pcarverActually I kind of like Flow17:39
cathy_Given that SFC is discussed in many forums and seems like a very desired feature, we would like people to know that OpenSTack also has support for SFC17:39
*** zeih has quit IRC17:39
amotokiwe cannot use 'ryu' (which means "water flows" in japanese) :-)17:39
vikram_amotoki: hehehe17:40
amotoki'ryu' also means 'dragon'17:40
cathy_amotoki: :-)17:40
LouisFamotoki: what is chain in japanese?17:40
amotokiwith different japanese character.17:40
amotokikusari is chain in japanese. hard to pronounce.17:41
s3wongamotoki: yes -- -that is my understand via the 'Ryu' character in street fighter (that his name is "dragon")17:41
amotokis3wong: famous game!17:41
cathy_how about FlowChain17:41
amotokigood candidate17:41
*** Farhad has quit IRC17:41
mohankumar_cathy_ : +117:41
vikram_Flow somehow holds the notion of chain implicitly..17:42
*** Swami has joined #openstack-meeting-417:42
pcarverHow about "Foxtail"? It's a type of chain used in jewlery. Sort of like Cinder is a type of block.17:42
cathy_vikram_: I don't feel Flow holds the notion of chain.17:42
LouisFcathy_: +117:42
cathy_For me Flow just means the traafic flow17:42
cathy_traffic flow17:42
vikram_cathy_: Different opinions ;)17:42
cathy_vikram_: :-)17:42
*** batman has joined #openstack-meeting-417:43
-amotoki- is googling foxtail17:43
*** s3wong has quit IRC17:43
*** s3wong has joined #openstack-meeting-417:44
*** spotz is now known as spotz_zzz17:44
fsunavalcathy: I like FlowChain17:44
pcarverHere's an image of a few types of chains https://s-media-cache-ak0.pinimg.com/736x/dc/2a/71/dc2a71cd3a3068c72bc080e694f65752.jpg17:44
*** batman has quit IRC17:44
vikram_Till now, I am also okay with FlowChain17:45
cathy_s3wong: pcarver amotoki OK with FlowChain?17:45
s3wongcathy_: +117:45
amotokinp for flowchain17:45
pcarvervikram_: I'm ok with FlowChain too, just trying to think along the analogy lines of Cinder and Glance17:45
vikram_pcarver: go ahead.. we can find something more interesting and attractive ;)17:46
-amotoki- thinks we are enjoying terminology puzzle17:46
cathy_Ok, let's go with FlowChain for now. If anyone think of a better name, we can exchange via email.17:46
cathy_amotoki: :-)17:46
*** sdake_ is now known as sdake17:46
cathy_#topic features for second phase17:47
*** openstack changes topic to "features for second phase (Meeting topic: service_chaining)"17:47
vikram_this is real fun ... I m loving it17:47
pcarverI really like Barbican actually, that's a good name for a security related project. I'd like to come up with something that's unambiguously related to chains17:47
cathy_we have touched this a little bit before. Let me summarize them17:47
*** prashantD has joined #openstack-meeting-417:48
cathy_pcarver: good exercise for you:-)17:48
LouisFpcarver: daisy as in daisy-chain?17:48
pcarverLouisF: maybe17:49
*** hdaniel has joined #openstack-meeting-417:49
LouisFa bit whimsical ;)17:49
cathy_We know that networking-sfc has completed integration with ONOS controller path and OVS driver Path. In second phase we got suggestions to integrate with more SDN Controllers via our southbound common driver API interface so that we can provide a unified API for end users no matter what SDN Controllers is plugged into the southbound17:50
*** raddaoui has quit IRC17:51
cathy_Another area is to support a mixed chain of VM, container, physical devices17:51
amotokiin addition, northband integration with projects like tacker (or possible MANO in NFV context)17:52
cathy_amotoki: yes17:52
pcarverespecially physical devices. We need to figure out how much of the problem is solved by l2gw project17:52
vikram_pcarver: good point17:52
LouisFpcarver: ironic provides the physical device integration17:52
*** minwang2 has joined #openstack-meeting-417:53
cathy_Tacker PTL joined the meeting before and he will work with us for that.17:53
vikram_LouisF: so no change for us?17:53
amotokiwe also need to check the progress of various things which networking-sfc requires17:53
*** paul-carlton1 has quit IRC17:53
amotokiincluding l2gw and container integration17:53
LouisFvikram_: i think phy ports appear as neutron ports17:53
*** SumitNaiksatam has joined #openstack-meeting-417:53
cathy_amotoki: yes17:53
vikram_LouisF: Ok then no problems for us17:54
LouisFvikram_: need to validate17:54
vikram_LouisF: Will do17:54
*** SimonChung has joined #openstack-meeting-417:54
*** matrohon has quit IRC17:54
fsunavalnested container support in kuryr will help us with integrating containers inside VMs17:54
*** sridhar_ram has joined #openstack-meeting-417:55
-amotoki- is crashing. night17:55
vikram_Better to list all the requirements as per priority...17:55
*** harshs has joined #openstack-meeting-417:55
vikram_amotoki: It's very late for you17:55
LouisFvikram_: you had a suggestion on classifier enhancements17:55
cathy_fsunaval: yes, there is another mechanism called somethinh like VLAN Aware port for adding Neutron port to containers17:56
vikram_LouisF17:56
*** amotoki has quit IRC17:56
vikram_LouisF: Yes17:56
cathy_time is up. Let me summarize the second phase features17:57
vikram_cathy_: OAM17:57
mohankumar_cathy_ : horizon17:57
LouisFcathy_: can we discuss in more depth at next meeting17:58
*** paul-carlton1 has joined #openstack-meeting-417:58
cathy_1. support integration with more backend SDN controllers, 2. support of a mixed chain of VM, container, physical device, 3. integration with upstream Tacker, 4. enhancement of Flow Classifier, 5. Horizon, 6. OAM17:58
cathy_wow, a lot on the plate:-)17:58
vikram_7. Heat17:58
cathy_vikram_: yes17:59
LouisFcathy_: tempest tests17:59
cathy_We need to assign people investigating each area and come up with a design spec for review. So please think about which area you have interest and would like to lead the design of that piece.17:59
vikram_1 min remaining ;)17:59
cathy_8. tempest tests17:59
cathy_Ok, let's continue the discussion next week. think about which piece you would like to take and lead the design. Thanks everyone. It is a good discussion.18:00
cathy_Bye now18:00
LouisFbye18:00
s3wongbye18:00
cathy_#endmeeting18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
openstackMeeting ended Thu Feb 25 18:00:48 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/service_chaining/2016/service_chaining.2016-02-25-17.00.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/service_chaining/2016/service_chaining.2016-02-25-17.00.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/service_chaining/2016/service_chaining.2016-02-25-17.00.log.html18:00
*** sdake_ has joined #openstack-meeting-418:01
*** cathy_ has quit IRC18:01
*** sridhar_ram has quit IRC18:02
*** sridhar_ram has joined #openstack-meeting-418:02
vikram_quit18:02
*** vikram_ has quit IRC18:03
*** sdake has quit IRC18:03
*** degorenko is now known as _degorenko|afk18:04
*** rbak__ has quit IRC18:05
*** woodard has joined #openstack-meeting-418:05
*** spzala has quit IRC18:05
*** s3wong has quit IRC18:06
*** spzala has joined #openstack-meeting-418:06
*** neelashah has quit IRC18:06
*** woodard has quit IRC18:06
*** woodard has joined #openstack-meeting-418:07
*** harshs has quit IRC18:07
*** harshs has joined #openstack-meeting-418:07
*** hdaniel has quit IRC18:08
*** julim has joined #openstack-meeting-418:10
*** yamamoto has joined #openstack-meeting-418:10
*** spzala has quit IRC18:11
*** spotz_zzz is now known as spotz18:14
*** spotz is now known as spotz_zzz18:15
*** yamamoto has quit IRC18:15
*** rbak has joined #openstack-meeting-418:15
*** qwebirc47365 has quit IRC18:17
*** neelashah has joined #openstack-meeting-418:18
*** cemmason has quit IRC18:19
*** cemmason has joined #openstack-meeting-418:19
*** neelashah has quit IRC18:19
*** neelashah has joined #openstack-meeting-418:20
*** rbak has quit IRC18:21
*** vhoward has joined #openstack-meeting-418:21
*** rbak has joined #openstack-meeting-418:21
*** evgenyf has joined #openstack-meeting-418:21
*** numans has quit IRC18:22
*** numans has joined #openstack-meeting-418:22
*** dshakhray has quit IRC18:23
*** ihrachys has quit IRC18:24
*** cemmason1 has joined #openstack-meeting-418:25
*** xingchao has joined #openstack-meeting-418:25
*** bobh has quit IRC18:25
*** spzala has joined #openstack-meeting-418:25
*** cemmason has quit IRC18:26
*** woodard has quit IRC18:26
*** woodard has joined #openstack-meeting-418:26
*** cemmason has joined #openstack-meeting-418:28
*** cemmason1 has quit IRC18:29
*** xingchao has quit IRC18:30
*** cemmason has quit IRC18:31
*** cemmason1 has joined #openstack-meeting-418:31
*** salv-orlando has quit IRC18:32
*** mohankumar_ has quit IRC18:33
*** woodard has quit IRC18:35
*** cemmason has joined #openstack-meeting-418:35
*** woodard has joined #openstack-meeting-418:35
*** cemmason1 has quit IRC18:35
*** salv-orlando has joined #openstack-meeting-418:39
*** cemmason1 has joined #openstack-meeting-418:39
*** cemmason has quit IRC18:39
*** piet has joined #openstack-meeting-418:41
*** paul-carlton1 has quit IRC18:42
*** cemmason has joined #openstack-meeting-418:42
*** cemmason1 has quit IRC18:42
*** cemmason1 has joined #openstack-meeting-418:46
*** cemmason has quit IRC18:46
*** piet has quit IRC18:46
*** sambetts is now known as sambetts|afk18:47
*** zeih has joined #openstack-meeting-418:48
*** lakshmiS has joined #openstack-meeting-418:51
*** emagana has quit IRC18:51
*** fsunaval has quit IRC18:51
*** cemmason has joined #openstack-meeting-418:52
*** cemmason1 has quit IRC18:52
*** emagana has joined #openstack-meeting-418:54
*** IlyaG has quit IRC18:54
*** LouisF has quit IRC18:55
*** evgenyf has quit IRC18:56
*** woodard has quit IRC18:56
*** woodard has joined #openstack-meeting-418:56
*** sridhar_ram has quit IRC18:57
*** piet has joined #openstack-meeting-418:58
*** cemmason has quit IRC18:58
*** spotz_zzz is now known as spotz18:59
*** s3wong has joined #openstack-meeting-418:59
*** sridhar_ram has joined #openstack-meeting-419:01
*** daneyon has joined #openstack-meeting-419:02
*** blahRus1 has joined #openstack-meeting-419:02
*** piet has quit IRC19:02
*** _sarob has joined #openstack-meeting-419:02
*** piet has joined #openstack-meeting-419:03
*** blahRus has quit IRC19:04
*** woodard has quit IRC19:05
*** jmckind has quit IRC19:05
*** woodard has joined #openstack-meeting-419:06
*** daneyon has quit IRC19:06
*** jmckind has joined #openstack-meeting-419:06
*** numans has quit IRC19:10
*** yamamoto has joined #openstack-meeting-419:11
*** baoli_ has quit IRC19:11
*** angdraug has quit IRC19:12
*** raddaoui has joined #openstack-meeting-419:13
*** haleyb has quit IRC19:14
*** yamamoto has quit IRC19:17
*** rbak_ has joined #openstack-meeting-419:20
*** rbak has quit IRC19:20
*** singlethink has quit IRC19:21
*** automagically has joined #openstack-meeting-419:21
*** zeih has quit IRC19:22
*** fawadkhaliq has joined #openstack-meeting-419:22
*** evgenyf has joined #openstack-meeting-419:22
*** raddaoui has quit IRC19:24
*** iyamahat_ has quit IRC19:24
*** markvan has quit IRC19:25
*** raddaoui has joined #openstack-meeting-419:25
*** woodard has quit IRC19:26
*** woodard has joined #openstack-meeting-419:27
*** markvan has joined #openstack-meeting-419:27
*** xingchao has joined #openstack-meeting-419:27
*** iyamahat_ has joined #openstack-meeting-419:27
*** Sukhdev has joined #openstack-meeting-419:29
*** salv-orlando has quit IRC19:29
*** andymaier has quit IRC19:30
*** neelashah has quit IRC19:31
*** xingchao has quit IRC19:32
*** bobh has joined #openstack-meeting-419:34
*** salv-orlando has joined #openstack-meeting-419:36
*** zeih has joined #openstack-meeting-419:38
*** zeih has quit IRC19:42
*** automagically has left #openstack-meeting-419:43
*** neelashah has joined #openstack-meeting-419:45
*** hdaniel has joined #openstack-meeting-419:47
*** woodard has quit IRC19:47
*** woodard has joined #openstack-meeting-419:47
*** haleyb has joined #openstack-meeting-419:48
*** baoli has joined #openstack-meeting-419:49
*** krotscheck is now known as krotscheck_dcm19:50
*** baoli has quit IRC19:51
*** jmckind has quit IRC19:54
*** emagana has quit IRC19:54
*** jmckind has joined #openstack-meeting-419:54
*** emagana has joined #openstack-meeting-419:57
*** haleyb has quit IRC19:58
*** haleyb has joined #openstack-meeting-420:00
*** emagana has quit IRC20:01
*** evgenyf has quit IRC20:01
*** raddaoui has quit IRC20:05
*** bpokorny has quit IRC20:06
*** minwang2 has quit IRC20:08
*** woodard has quit IRC20:08
*** woodard has joined #openstack-meeting-420:08
*** FallenPegasus has joined #openstack-meeting-420:09
*** piet has quit IRC20:11
*** fawadkhaliq has quit IRC20:13
*** yamamoto has joined #openstack-meeting-420:13
*** fawadkhaliq has joined #openstack-meeting-420:13
*** piet has joined #openstack-meeting-420:14
*** piet has quit IRC20:14
*** minwang2 has joined #openstack-meeting-420:15
*** bobh has quit IRC20:17
*** woodard has quit IRC20:17
*** yamamoto has quit IRC20:17
*** raddaoui has joined #openstack-meeting-420:18
*** salv-orlando has quit IRC20:18
*** bpokorny has joined #openstack-meeting-420:20
*** salv-orlando has joined #openstack-meeting-420:20
*** javeriak has joined #openstack-meeting-420:22
*** javeriak has quit IRC20:23
*** javeriak_ has quit IRC20:25
*** xingchao has joined #openstack-meeting-420:28
*** vhoward has quit IRC20:29
*** piet has joined #openstack-meeting-420:33
*** cloudtrainme has joined #openstack-meeting-420:34
*** xingchao has quit IRC20:34
*** dtardivel has quit IRC20:38
*** emagana has joined #openstack-meeting-420:38
*** thorst is now known as thorst_afk20:38
*** zeih has joined #openstack-meeting-420:39
*** angdraug has joined #openstack-meeting-420:39
*** emagana has quit IRC20:40
*** daneyon has joined #openstack-meeting-420:40
*** _degorenko|afk has quit IRC20:42
*** matrohon has joined #openstack-meeting-420:42
*** emagana has joined #openstack-meeting-420:42
*** _degorenko|afk has joined #openstack-meeting-420:43
*** emagana has quit IRC20:43
*** zeih has quit IRC20:47
*** emagana has joined #openstack-meeting-420:51
*** cloudtrainme has quit IRC20:51
*** piet has quit IRC20:51
*** thorst_afk is now known as thorst20:53
*** emagana has quit IRC20:55
*** cloudtrainme has joined #openstack-meeting-421:00
*** dshakhray has joined #openstack-meeting-421:00
*** jmckind has quit IRC21:02
*** jmckind has joined #openstack-meeting-421:02
*** raddaoui has quit IRC21:04
*** vishwanathj has quit IRC21:04
*** markvan has quit IRC21:06
*** markvan has joined #openstack-meeting-421:08
*** emagana has joined #openstack-meeting-421:08
*** piet has joined #openstack-meeting-421:08
*** _sarob has quit IRC21:10
*** emagana has quit IRC21:12
*** yamamoto has joined #openstack-meeting-421:14
*** yamamoto has quit IRC21:19
*** fawadkhaliq has quit IRC21:20
*** Sukhdev has quit IRC21:21
*** neelashah has quit IRC21:21
*** emagana has joined #openstack-meeting-421:24
*** matrohon has quit IRC21:25
*** woodard has joined #openstack-meeting-421:28
*** matrohon has joined #openstack-meeting-421:29
*** xingchao has joined #openstack-meeting-421:31
*** piet has quit IRC21:32
*** cloudtrainme has quit IRC21:33
*** sdake_ is now known as sdake21:35
*** bgmccollum has joined #openstack-meeting-421:36
*** xingchao has quit IRC21:36
*** thorst is now known as thorst_afk21:39
*** banix has joined #openstack-meeting-421:39
*** cloudtrainme has joined #openstack-meeting-421:40
*** thorst_afk has quit IRC21:43
*** thorst_afk has joined #openstack-meeting-421:43
*** woodard has quit IRC21:44
*** yamahata has quit IRC21:44
*** iyamahat_ has quit IRC21:45
*** woodard has joined #openstack-meeting-421:45
*** cloudtrainme has quit IRC21:46
*** neelashah has joined #openstack-meeting-421:47
*** jmckind has quit IRC21:49
*** jmckind has joined #openstack-meeting-421:49
*** piet has joined #openstack-meeting-421:51
*** woodard has quit IRC21:51
*** thorst_afk has quit IRC21:52
*** woodard has joined #openstack-meeting-421:53
*** emagana has quit IRC21:54
*** spzala has quit IRC21:59
*** pmesserli has quit IRC21:59
*** pmesserli has joined #openstack-meeting-421:59
*** delatte has quit IRC22:00
*** emagana has joined #openstack-meeting-422:01
*** _sarob has joined #openstack-meeting-422:01
*** emagana has quit IRC22:02
*** woodard has quit IRC22:02
*** emagana has joined #openstack-meeting-422:02
*** julim has quit IRC22:04
*** emagana has quit IRC22:06
*** _sarob has quit IRC22:06
*** _sarob has joined #openstack-meeting-422:08
*** emagana has joined #openstack-meeting-422:09
*** emagana has quit IRC22:11
*** emagana has joined #openstack-meeting-422:11
*** _sarob has quit IRC22:13
*** yamamoto has joined #openstack-meeting-422:15
*** prashantD has quit IRC22:16
*** prashantD has joined #openstack-meeting-422:18
*** piet has quit IRC22:18
*** fawadkhaliq has joined #openstack-meeting-422:19
*** yamamoto has quit IRC22:20
*** delatte has joined #openstack-meeting-422:25
*** Sukhdev has joined #openstack-meeting-422:28
*** cloudtrainme has joined #openstack-meeting-422:28
*** xingchao has joined #openstack-meeting-422:33
*** delattec has joined #openstack-meeting-422:33
*** cloudtra_ has joined #openstack-meeting-422:34
*** cloudtrainme has quit IRC22:35
*** delatte has quit IRC22:36
*** IlyaG has joined #openstack-meeting-422:36
*** xingchao has quit IRC22:38
*** MarkAtwood has quit IRC22:39
*** FallenPegasus has quit IRC22:42
*** armax has quit IRC22:43
*** FallenPegasus has joined #openstack-meeting-422:43
*** armax has joined #openstack-meeting-422:44
*** zeih has joined #openstack-meeting-422:44
*** FallenPegasus has quit IRC22:48
*** thorst_afk has joined #openstack-meeting-422:49
*** hdaniel has quit IRC22:50
*** neelashah has quit IRC22:52
*** zeih has quit IRC22:52
*** thorst_afk has quit IRC22:57
*** armax has quit IRC22:57
*** banix has quit IRC22:58
*** KLevenstein has quit IRC22:58
*** jmckind has quit IRC23:00
*** jmckind has joined #openstack-meeting-423:00
*** delatte has joined #openstack-meeting-423:01
*** klamath_ has quit IRC23:02
*** delattec has quit IRC23:03
*** spotz is now known as spotz_zzz23:04
*** jmckind has quit IRC23:07
*** salv-orl_ has joined #openstack-meeting-423:08
*** blahRus1 has quit IRC23:11
*** salv-orlando has quit IRC23:12
*** matrohon has quit IRC23:15
*** woodard has joined #openstack-meeting-423:15
*** yamamoto_ has joined #openstack-meeting-423:16
*** _sarob has joined #openstack-meeting-423:17
*** fnaval has quit IRC23:19
*** _sarob has quit IRC23:21
*** yamamoto_ has quit IRC23:22
*** sigmavirus24 is now known as sigmavirus24_awa23:23
*** pmesserl_ has joined #openstack-meeting-423:28
*** Sukhdev has quit IRC23:29
*** pmesserli has quit IRC23:29
*** woodard has quit IRC23:31
*** iyamahat_ has joined #openstack-meeting-423:34
*** xingchao has joined #openstack-meeting-423:35
*** _sarob has joined #openstack-meeting-423:36
*** yamahata has joined #openstack-meeting-423:36
*** Swami has quit IRC23:38
*** salv-orl_ has quit IRC23:39
*** haleyb has quit IRC23:39
*** xingchao has quit IRC23:41
*** _sarob has quit IRC23:41
*** banix has joined #openstack-meeting-423:41
*** angdraug has quit IRC23:43
*** sridhar_ram has quit IRC23:44
*** _sarob has joined #openstack-meeting-423:44
*** SumitNaiksatam has quit IRC23:46
*** fawadkhaliq has quit IRC23:47
*** _sarob has quit IRC23:49
*** JRobinson__ has joined #openstack-meeting-423:51
*** thorst_afk has joined #openstack-meeting-423:55
*** krtaylor has quit IRC23:58

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