Thursday, 2015-12-03

*** ScottMillward has joined #openstack-meeting-400:00
*** smillward has quit IRC00:01
*** rbak has quit IRC00:02
*** pmesserli has quit IRC00:04
*** dims has quit IRC00:04
*** mitchjameson has quit IRC00:04
*** klamath_ has quit IRC00:07
*** shakamunyi has joined #openstack-meeting-400:10
*** rbak has joined #openstack-meeting-400:12
*** xingchao has joined #openstack-meeting-400:22
*** xingchao has quit IRC00:26
*** salv-orl_ has joined #openstack-meeting-400:30
*** Prithiv has quit IRC00:31
*** salv-orlando has quit IRC00:33
*** dims has joined #openstack-meeting-400:33
*** bobh_ has joined #openstack-meeting-400:40
*** Sukhdev has quit IRC00:41
*** kebray has quit IRC00:42
*** Sukhdev has joined #openstack-meeting-400:44
*** Swami has quit IRC00:46
*** salv-orl_ has quit IRC00:53
*** bobh_ has quit IRC00:58
*** baoli has joined #openstack-meeting-400:58
*** shakamunyi has quit IRC01:02
*** xingchao has joined #openstack-meeting-401:02
*** IlyaG has quit IRC01:02
*** shakamunyi has joined #openstack-meeting-401:03
*** mitchjameson has joined #openstack-meeting-401:04
*** IlyaG has joined #openstack-meeting-401:05
*** IlyaG has quit IRC01:09
*** lianghuifei has joined #openstack-meeting-401:10
*** IlyaG has joined #openstack-meeting-401:20
*** gjayavelu has quit IRC01:21
*** markvoelker has quit IRC01:23
*** IlyaG has quit IRC01:24
*** u_kozat has quit IRC01:24
*** IlyaG has joined #openstack-meeting-401:25
*** mestery has joined #openstack-meeting-401:30
*** dims has quit IRC01:30
*** xingchao has quit IRC01:31
*** SimonChung has quit IRC01:33
*** Sukhdev has quit IRC01:33
*** xingchao has joined #openstack-meeting-401:36
*** mancdaz has quit IRC01:39
*** mancdaz has joined #openstack-meeting-401:40
*** yamamoto has joined #openstack-meeting-401:43
*** MarkAtwood has joined #openstack-meeting-401:44
*** yamamoto has quit IRC01:53
*** salv-orlando has joined #openstack-meeting-401:54
*** salv-orlando has quit IRC01:59
*** dims has joined #openstack-meeting-402:00
*** Piet has joined #openstack-meeting-402:19
*** sridhar_ram has quit IRC02:21
*** mestery has quit IRC02:22
*** s3wong has quit IRC02:23
*** ajmiller_ has joined #openstack-meeting-402:28
*** ajmiller has quit IRC02:30
*** ajmiller__ has joined #openstack-meeting-402:35
*** bpokorny_ has joined #openstack-meeting-402:37
*** ajmiller_ has quit IRC02:38
*** bpokorny has quit IRC02:40
*** yamamoto has joined #openstack-meeting-402:40
*** bpokorny_ has quit IRC02:41
*** jckasper has joined #openstack-meeting-402:42
*** bobh_ has joined #openstack-meeting-402:43
*** yamamoto has quit IRC02:46
*** iyamahat has quit IRC02:52
*** yamahata has quit IRC02:52
*** yamamoto has joined #openstack-meeting-402:54
*** prashantD has quit IRC03:00
*** tfukushima has joined #openstack-meeting-403:02
*** ajmiller__ has quit IRC03:02
*** bobh_ has quit IRC03:17
*** fawadkhaliq has joined #openstack-meeting-403:32
*** jckasper has quit IRC03:34
*** kexiaodong has joined #openstack-meeting-403:47
*** MarkAtwood has quit IRC03:53
*** baoli has quit IRC03:54
*** baoli has joined #openstack-meeting-403:55
*** rolandchan has joined #openstack-meeting-403:57
*** MarkAtwood has joined #openstack-meeting-403:59
*** jckasper has joined #openstack-meeting-404:02
*** xingchao_ has joined #openstack-meeting-404:09
*** xingchao has quit IRC04:09
*** prashantD has joined #openstack-meeting-404:10
*** ozstacker_ has joined #openstack-meeting-404:21
*** prashantD_ has joined #openstack-meeting-404:23
*** bobh_ has joined #openstack-meeting-404:23
*** prashantD has quit IRC04:23
*** bobh_ has quit IRC04:25
*** ozstacker_ has quit IRC04:28
*** tfukushima has quit IRC04:32
*** galstrom_zzz is now known as galstrom04:32
*** bobh_ has joined #openstack-meeting-404:39
*** baoli has quit IRC04:40
*** ozstacker has joined #openstack-meeting-404:40
*** numans has joined #openstack-meeting-404:42
*** fawadkhaliq has quit IRC04:50
*** dims has quit IRC04:52
*** jckasper has quit IRC04:52
*** bpokorny has joined #openstack-meeting-404:53
*** kavit has joined #openstack-meeting-404:54
*** prashantD has joined #openstack-meeting-404:59
*** SimonChung has joined #openstack-meeting-405:00
*** prashantD_ has quit IRC05:00
rolandchanDiversity WG meeting anybody?05:01
kavit#startmeeting Diversity Workgroup APAC 3rd Dec 201505:02
openstackMeeting started Thu Dec  3 05:02:39 2015 UTC and is due to finish in 60 minutes.  The chair is kavit. Information about MeetBot at http://wiki.debian.org/MeetBot.05:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:02
*** openstack changes topic to " (Meeting topic: Diversity Workgroup APAC 3rd Dec 2015)"05:02
openstackThe meeting name has been set to 'diversity_workgroup_apac_3rd_dec_2015'05:02
rolandchanRoll Call05:03
rolandchanRoland Chan, Aptira.05:03
kavitKavit Munshi, Aptira05:04
kavit#link https://etherpad.openstack.org/p/OpenStackDiversity.1805:04
*** IlyaG has quit IRC05:04
*** IlyaG has joined #openstack-meeting-405:04
*** IlyaG has quit IRC05:05
rolandchanok, so working through the agenda05:06
*** SimonChung has quit IRC05:06
*** SimonChung has joined #openstack-meeting-405:06
rolandchanOutreach: I think the plan was to look at providing materials to user group convenors05:07
kavitalso need to reach out to the TC to get help with the issues faced by new developers05:07
rolandchanit turns out nothing exists for UG people. I think we need someone to take on this task.05:07
kavitI think a few people from the TC were happy to help05:08
*** Sukhdev has joined #openstack-meeting-405:08
kavitthis could be a part of the outreach05:08
rolandchanOK. So, we need to pull the TC into the Diversity process. We had one volunteer, lets get the US based people to invite them all along to the meeting.05:08
rolandchan#action US team to invite TC members to Diversity WG meetings.05:09
rolandchanoh, yeah. Bot hates me.05:09
kavitrolandchan, we should talk to tom, there is some talk of a starter pack for new UG in the ambassadors group, we could work with them05:09
kavit#chair rolandchan05:09
openstackCurrent chairs: kavit rolandchan05:09
rolandchanexcellent.05:09
kavitplease try again05:09
rolandchan#action US team to invite TC members to Diversity WG meetings.05:09
rolandchanOpenstack bot is not very inclusive05:10
rolandchanmoving on05:10
*** SimonChung1 has joined #openstack-meeting-405:11
rolandchanOnboarding element. So I have reviewed the various "getting started" type content, and it's disorganised. there's some duplication and projects have many different ways of doing things05:11
rolandchanI think it would be useful to have some common formats/locations/style etc to getting people oriented.05:12
rolandchanobviously that's something that needs buy in from the various project teams.05:12
rolandchanand assuming that occurs, the remediation of existing content will be fairly onerous.05:13
rolandchanStill, I think it needs to be done.05:13
*** SimonChung has quit IRC05:13
rolandchanI'd like to hear what the rest of the WG thinks before we take it outside the group.05:13
*** ScottMillward has quit IRC05:14
kavitrolandchan, there was also talk of a Speaker's Bureau being created at the community track in Tokyo. idea was  to provide a database of regular speakers to the UGs and various events05:14
kavitwe should circle back and co-ordinate with that group also05:14
rolandchanyes, with respect to outreach.05:14
kavitsorry yes, this would be under outreach05:15
rolandchananything else for onboarding?05:15
kavitcant think of anything05:15
rolandchanok05:15
rolandchanCode of Conduct update.05:16
kavitdont have one05:17
*** bobh_ has quit IRC05:18
*** yamamoto has quit IRC05:19
*** rolandchan_ has joined #openstack-meeting-405:20
rolandchan_so, I'm happy to draft an email05:20
*** rolandchan has quit IRC05:20
rolandchan_and send it to the US team to review, update etc before they send it to jbryce05:20
*** yamamoto has joined #openstack-meeting-405:21
rolandchan_thats it for me.05:22
kavitOK05:23
kavitanyone else want to discuss anything?05:23
*** Sukhdev has quit IRC05:24
kavitok going to end the meeting05:24
kavit#endmeeting05:24
*** openstack changes topic to "Q&A (Meeting topic: openstack-vahana)"05:24
openstackMeeting ended Thu Dec  3 05:24:25 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)05:24
openstackMinutes:        http://eavesdrop.openstack.org/meetings/diversity_workgroup_apac_3rd_dec_2015/2015/diversity_workgroup_apac_3rd_dec_2015.2015-12-03-05.02.html05:24
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/diversity_workgroup_apac_3rd_dec_2015/2015/diversity_workgroup_apac_3rd_dec_2015.2015-12-03-05.02.txt05:24
openstackLog:            http://eavesdrop.openstack.org/meetings/diversity_workgroup_apac_3rd_dec_2015/2015/diversity_workgroup_apac_3rd_dec_2015.2015-12-03-05.02.log.html05:24
*** rolandchan_ has quit IRC05:25
*** markvoelker has joined #openstack-meeting-405:25
*** fawadkhaliq has joined #openstack-meeting-405:27
*** markvoelker_ has joined #openstack-meeting-405:28
*** markvoelker has quit IRC05:30
*** markvoelker has joined #openstack-meeting-405:31
*** tfukushima has joined #openstack-meeting-405:33
*** markvoelker_ has quit IRC05:34
*** markvoelker_ has joined #openstack-meeting-405:38
*** markvoelker has quit IRC05:38
*** shuquan has joined #openstack-meeting-405:38
*** tfukushima has quit IRC05:38
*** tfukushima has joined #openstack-meeting-405:41
*** salv-orlando has joined #openstack-meeting-405:43
*** tfukushima has quit IRC05:45
*** tfukushima has joined #openstack-meeting-405:46
*** salv-orlando has quit IRC05:47
*** irenab_ has joined #openstack-meeting-405:49
*** irenab has quit IRC05:49
*** irenab_ is now known as irenab05:49
*** markvoelker_ has quit IRC05:51
*** ScottMillward has joined #openstack-meeting-405:54
*** saneax_AFK is now known as saneax05:58
*** bpokorny has quit IRC05:59
*** saneax has left #openstack-meeting-406:07
*** galstrom is now known as galstrom_zzz06:10
*** jpekkari has joined #openstack-meeting-406:13
*** tfukushima has quit IRC06:14
*** kexiaodong has quit IRC06:20
*** kavit has quit IRC06:23
*** prashantD has quit IRC06:27
*** tfukushima has joined #openstack-meeting-406:28
*** sdake has quit IRC06:28
*** tfukushima has quit IRC06:33
*** harmw has quit IRC06:38
*** harmw has joined #openstack-meeting-406:38
*** markvoelker has joined #openstack-meeting-406:50
*** xingchao has joined #openstack-meeting-406:51
*** evgenyf has joined #openstack-meeting-406:52
*** xingchao_ has quit IRC06:53
*** markvoelker has quit IRC06:55
*** shuquan has quit IRC06:56
*** shuquan has joined #openstack-meeting-406:58
*** javeriak has joined #openstack-meeting-407:00
*** shuquan has quit IRC07:01
*** shuquan has joined #openstack-meeting-407:04
*** javeriak has quit IRC07:10
*** shuquan has quit IRC07:10
*** javeriak has joined #openstack-meeting-407:10
*** shuquan has joined #openstack-meeting-407:12
*** javeriak_ has joined #openstack-meeting-407:16
*** javeriak has quit IRC07:16
*** dshakhray has joined #openstack-meeting-407:17
*** sdake has joined #openstack-meeting-407:24
*** nkrinner has joined #openstack-meeting-407:31
*** shuquan has quit IRC07:34
*** paul-carlton1 has joined #openstack-meeting-407:35
*** shuquan has joined #openstack-meeting-407:37
*** fawadkhaliq has quit IRC07:39
*** fawadkhaliq has joined #openstack-meeting-407:39
*** armax has quit IRC07:44
*** flaper87 has quit IRC07:44
*** balajin has left #openstack-meeting-407:46
*** flaper87 has joined #openstack-meeting-407:49
*** fawadkhaliq has quit IRC07:50
*** fawadkhaliq has joined #openstack-meeting-407:53
*** iyamahat has joined #openstack-meeting-407:57
*** fawadkhaliq has quit IRC07:57
*** belmoreira has joined #openstack-meeting-408:04
*** matrohon has joined #openstack-meeting-408:05
*** fawadkhaliq has joined #openstack-meeting-408:05
*** fawadk has joined #openstack-meeting-408:07
*** fawadkhaliq has quit IRC08:08
*** salv-orlando has joined #openstack-meeting-408:08
*** salv-orlando has quit IRC08:12
*** paul-carlton1 has quit IRC08:12
*** MarkAtwood has quit IRC08:15
*** markvoelker has joined #openstack-meeting-408:25
*** paul-carlton1 has joined #openstack-meeting-408:26
*** javeriak_ has quit IRC08:27
*** fawadk has quit IRC08:28
*** fawadkhaliq has joined #openstack-meeting-408:29
*** markvoelker has quit IRC08:30
*** ozstacker has quit IRC08:32
*** ivar-laz_ has joined #openstack-meeting-408:32
*** ozstacker has joined #openstack-meeting-408:32
*** ivar-lazzaro has quit IRC08:34
*** sdake has quit IRC08:36
*** javeriak has joined #openstack-meeting-408:41
*** amotoki has joined #openstack-meeting-408:43
*** iyamahat has quit IRC08:51
*** zeih has joined #openstack-meeting-408:54
*** salv-orlando has joined #openstack-meeting-408:56
*** salv-orlando has quit IRC08:56
*** tfukushima has joined #openstack-meeting-408:56
*** salv-orlando has joined #openstack-meeting-408:56
*** gampel has joined #openstack-meeting-408:58
*** gampel has left #openstack-meeting-408:59
*** shuquan has quit IRC09:01
*** javeriak has quit IRC09:04
*** belmoreira has quit IRC09:04
*** paul-carlton1 has quit IRC09:08
*** sdake has joined #openstack-meeting-409:16
*** yamahata has joined #openstack-meeting-409:22
*** javeriak has joined #openstack-meeting-409:24
*** salv-orlando has quit IRC09:32
*** salv-orlando has joined #openstack-meeting-409:33
*** Prithiv has joined #openstack-meeting-409:34
*** zeih has quit IRC09:36
*** sdake has quit IRC09:49
*** yamahata has quit IRC09:56
*** sdake has joined #openstack-meeting-409:58
*** fawadkhaliq has quit IRC10:00
*** fawadkhaliq has joined #openstack-meeting-410:00
*** javeriak has quit IRC10:04
*** sdake has quit IRC10:07
*** evgenyf has quit IRC10:13
*** evgenyf has joined #openstack-meeting-410:18
*** dzamboni has joined #openstack-meeting-410:23
*** markvoelker has joined #openstack-meeting-410:26
*** macsz has joined #openstack-meeting-410:27
*** dilyin has quit IRC10:27
*** ativelkov has quit IRC10:29
*** markvoelker has quit IRC10:31
*** ativelkov has joined #openstack-meeting-410:32
*** yamamoto has quit IRC10:33
*** tfukushima has quit IRC10:36
*** belmoreira has joined #openstack-meeting-410:38
*** evgenyf has quit IRC10:42
*** evgenyf has joined #openstack-meeting-410:56
*** xingchao has quit IRC10:59
*** mbound_ has joined #openstack-meeting-411:03
*** rosmaita_ has joined #openstack-meeting-411:03
*** dims_ has joined #openstack-meeting-411:03
*** rosmaita has quit IRC11:03
*** mclaren has quit IRC11:34
*** mbound_ has quit IRC11:38
*** mbound_ has joined #openstack-meeting-411:41
*** masterbound has joined #openstack-meeting-411:47
*** mbound_ has quit IRC11:47
*** xingchao has joined #openstack-meeting-411:49
*** xingchao has quit IRC11:53
*** zeih has joined #openstack-meeting-411:58
*** masterbound has quit IRC12:01
*** mbound_ has joined #openstack-meeting-412:02
*** yamamoto has joined #openstack-meeting-412:03
*** qwebirc95913 has joined #openstack-meeting-412:08
*** qwebirc95913 has quit IRC12:08
*** yamamoto has quit IRC12:09
*** fawadkhaliq has quit IRC12:15
*** fawadkhaliq has joined #openstack-meeting-412:16
*** flaper87 has quit IRC12:17
*** flaper87 has joined #openstack-meeting-412:17
*** markvoelker has joined #openstack-meeting-412:27
*** bobh_ has joined #openstack-meeting-412:29
*** bobh_ has quit IRC12:31
*** markvoelker has quit IRC12:32
*** dilyin has joined #openstack-meeting-412:35
*** zeih has quit IRC12:52
*** zeih has joined #openstack-meeting-412:53
*** evgenyf has quit IRC12:57
*** evgenyf has joined #openstack-meeting-412:58
*** baoli has joined #openstack-meeting-413:04
*** njohnston has joined #openstack-meeting-413:07
*** njohnston has quit IRC13:11
*** njohnston has joined #openstack-meeting-413:11
*** njohnston has quit IRC13:12
*** klamath has joined #openstack-meeting-413:13
*** klamath has joined #openstack-meeting-413:14
*** baoli has quit IRC13:15
*** baoli has joined #openstack-meeting-413:17
*** njohnston has joined #openstack-meeting-413:17
*** baoli_ has joined #openstack-meeting-413:20
*** zeih has quit IRC13:21
*** yamamoto has joined #openstack-meeting-413:23
*** baoli has quit IRC13:23
*** yamamoto has quit IRC13:24
*** bunting has joined #openstack-meeting-413:26
*** bradjones has quit IRC13:27
*** markvoelker has joined #openstack-meeting-413:28
*** bradjones has joined #openstack-meeting-413:31
*** bradjones has quit IRC13:31
*** bradjones has joined #openstack-meeting-413:31
*** markvoelker has quit IRC13:32
*** dwc_ has joined #openstack-meeting-413:33
*** dwc_ has quit IRC13:34
*** zeih has joined #openstack-meeting-413:45
*** bpoulos has joined #openstack-meeting-413:46
*** yamamoto has joined #openstack-meeting-413:46
*** jpekkari has quit IRC13:49
*** markvoelker has joined #openstack-meeting-413:50
*** markvoelker_ has joined #openstack-meeting-413:52
*** paul-carlton1 has joined #openstack-meeting-413:52
*** markvoelker has quit IRC13:54
*** zeih has quit IRC13:57
*** salv-orlando has quit IRC13:58
*** Steap has joined #openstack-meeting-413:58
*** jckasper has joined #openstack-meeting-413:58
flaper87Courtesy meeting reminder: ativelkov, cpallares, flaper87, flwang1, hemanthm, jokke_, kragniz, lakshmiS, mclaren, mfedosin, nikhil_k13:59
flaper87Courtesy meeting reminder: Nikolay_St, Olena, pennerc, rosmaita, sigmavirus24, sabari, TravT, ajayaa, GB21, bpoulos, harshs, abhishekk, bunting13:59
flaper87Courtesy meeting reminder: dshakhray, wxy, dhellmann, kairat13:59
flaper87#startmeeting Glance13:59
openstackMeeting started Thu Dec  3 13:59:43 2015 UTC and is due to finish in 60 minutes.  The chair is flaper87. Information about MeetBot at http://wiki.debian.org/MeetBot.13:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:59
*** openstack changes topic to " (Meeting topic: Glance)"13:59
openstackThe meeting name has been set to 'glance'13:59
flaper87#topic Roll Call13:59
*** openstack changes topic to "Roll Call (Meeting topic: Glance)"13:59
ativelkovo/13:59
dshakhrayo/13:59
kragnizo/13:59
bpouloso/14:00
*** ninag_ has joined #openstack-meeting-414:00
*** lemondream has joined #openstack-meeting-414:00
ativelkovmfedosin will be here in a minute14:00
* flaper87 has a quite flaky internet connection... expect some lags14:00
*** kairat has joined #openstack-meeting-414:00
flaper87ativelkov: thanks14:00
kairato/14:00
*** mfedosin has joined #openstack-meeting-414:00
sabario/14:00
mfedosino/14:00
flaper87sabari: O.O14:00
*** lemondream is now known as avarner_14:00
flaper87sabari: glad to have you here14:01
nikhilo/14:01
flaper87:D14:01
avarner_o/14:01
* flaper87 hands a cup of coffee to sabari14:01
*** zeih has joined #openstack-meeting-414: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
sabariflaper87 The jetlag helped a bit :D14:01
flaper87That's our agenda for today14:01
*** javeriak has joined #openstack-meeting-414:01
dhellmanno/14:01
rosmaita_o/14:01
flaper87as usual, feel free to put stuff in there if you would like to talk about them14:01
*** yamamoto has quit IRC14:02
flaper87One thing w.r.t the agenda, now that we're talking about it. If you need to raise awareness on a specific spec, you should feel free to add it to the drivers agenda14:02
*** yamamoto has joined #openstack-meeting-414:02
flaper87It's fine and perfect to discuss it here if you need a broader community to chime in14:02
flaper87but, if it's just to raise awareness and ask for review, remember we meet on Tuesdays to talk about that14:02
kairatflaper87, ok, got it14:03
flaper87you're not required to attend the meeting, we'll review the spec even if you're not there14:03
flaper87:)14:03
flaper87#link https://etherpad.openstack.org/p/glance-drivers-meeting-agenda14:03
flaper87that's the link to the driver's agenda14:03
*** mclaren has joined #openstack-meeting-414:03
nikhilyou're spoiling the cats14:03
flaper87coolio, moving on14:03
flaper87:D14:03
flaper87#topic Updates14:03
*** openstack changes topic to "Updates (Meeting topic: Glance)"14:03
flaper87Artifacts:14:03
flaper87ativelkov: mfedosin ?14:03
nikhilwe met for a mins14:04
nikhilthe bot wasn't there14:04
nikhilhad a convo for about 20 mins14:04
flaper87nikhil: :(14:04
nikhilthe gist of it is that we are waiting for the spec14:04
ativelkovI am back to active work (sorry, took so long, but finally got the approve). We plan to have a Glance v3->Glarev0.1 spec to be ready by the next drivers meeting14:04
flaper87to be written or reviewed ?14:04
nikhiland some hint of thinking from ativelkov14:04
flaper87ativelkov: awesome14:04
ativelkovAnd so will the refactored API spec, hopefully14:05
nikhilwritten, but I will let ativelkov chat14:05
flaper87That sounds great!14:05
*** pmesserli has joined #openstack-meeting-414:05
* flaper87 is looking forward to that spec14:05
mfedosinand as I promised I will prepare a spec about moving v3 to standalone service14:05
ativelkovto be written, yes. We've also got some commitment from mfedosin and dshakhray to do the actual migration of code14:05
flaper87nice, sweet!14:06
flaper87Thanks folks14:06
nikhilativelkov: so to clarify, we are porting and not delete then write again ?14:06
ativelkovfor now - porting, yes14:06
*** julim has joined #openstack-meeting-414:06
flaper87I think I -2'd the deletion patch14:06
flaper87as I think porting is the way to go14:06
flaper87cool14:06
nikhilthanks, deletion sounds risky14:06
ativelkovJust moving the current v3 to glare v0.114:06
flaper87ok, drivers updates14:07
kairatI abandoned this patch14:07
nikhilexperimental prolly doesn't give us that contract right14:07
nikhilthanks14:07
flaper87Notm uch from our side. There have been more discussions on the new image import process and an attempt to simplify it14:07
flaper87A new PS will be proposed and I hope we'll reach an agreement before the next drivers meeting14:07
*** rosmaita_ is now known as rosmaita14:07
flaper87NExt week we'll start making decisions based on what we have because we need to move that forward14:08
nikhilI have solid feedback and 2-3 use cases that will help shape it well14:08
flaper87other than that, the db purge spec landed14:08
flaper87and more reviews to the rest of the specs are coming14:08
nikhilI have already communicated that to Brian and writing it down in a formatted manner14:08
flaper87nikhil: awesome :D14:08
flaper87thanks14:08
flaper87rosmaita: ^14:08
flaper87moving on14:08
flaper87Updates on the Nova v1 -> V2 work14:08
mfedosinI have good news14:09
flaper87One of the feedbacks I got was that we hadn't provided news on what's going on there14:09
flaper87Which is true14:09
flaper87so, here's some feedback14:09
*** yamamoto has quit IRC14:09
flaper87actually, mfedosin you go for it14:09
mfedosincurrently we're able to do listing with v214:09
*** yamamoto has joined #openstack-meeting-414:09
flaper87w0000h000000014:09
mclarennice!14:09
mfedosinchanges-since works perfect with new filters14:10
mclarenship it!14:10
rosmaitagreat!14:10
flaper87some patches have been merged already14:10
flaper87nnnnice14:10
flaper87nice nice nice14:10
mfedosinand all tempest tests pass14:10
sabariawesome!14:10
flaper87well done!14:10
mfedosindelete and download work as well14:10
ativelkovcool!14:10
flaper87The nova core team is falling behind with some reviews on this work but I'm working with them to make sure there's nothing blocking reviews14:10
mfedosinI need to concentrate and finish with 'update' today14:10
flaper87There's a series of patches up for review: https://review.openstack.org/#/c/231696/14:11
flaper87That is, things have been implemented and we mostly need to land them14:11
*** bobh_ has joined #openstack-meeting-414:11
flaper87mfedosin: thanks for the updates14:11
flaper87#topic Cross project: backwards compat for libraries and clients (nikhil) 14:11
mfedosinwelcome :)14:11
*** openstack changes topic to "Cross project: backwards compat for libraries and clients (nikhil)  (Meeting topic: Glance)"14:11
flaper87nikhil: floor is yours14:11
nikhilmfedosin et.al : excellent work14:11
nikhilon the x-prj topic14:12
*** zeih has quit IRC14:12
nikhilnow that we will be (semi-)enforced to implement this14:12
nikhil(I will let the spec talk the details)14:12
nikhilwhat do we all think about glance-store api refactor?14:12
flaper87#link https://review.openstack.org/#/c/22615714:13
nikhilI am not sure how feasible it is to keep that 100% back-compat!?14:13
nikhilthanks flaper8714:13
nikhilor do we mark this lib as an exception14:13
flaper87I still think we should do it. The whole point about this refactor was not to delete everything and re-implement. The idea is to write the new API alongside the old one14:13
flaper87so that it'll give time to consumers of the library to migrate14:14
flaper87I think our current API is pure crap (pardon my language)14:14
nikhilyeah, but then we need to maintain 2 APIs14:14
flaper87and it was thought for internal use in Glance14:14
flaper87nikhil: sure but we'll deprecate the old one14:14
flaper87it's just to give time to projects to move to the new one14:14
flaper87In openstack, glance is the only one using it for now14:15
flaper87which makes it easier14:15
nikhilso you are saying that store would need an exception14:15
flaper87I don't think that spec says we can't deprecate stuff14:15
*** macsz has quit IRC14:15
flaper87What it says is that we *have* to commit to deprecate stuff14:15
*** jproulx has joined #openstack-meeting-414:16
*** jproulx has left #openstack-meeting-414:16
mclarenis this a priority for mitaka?14:16
flaper87The plan with that refactor has always been to deprecate the old API and give time to migrate14:16
flaper87it is not14:16
flaper87but I believe nikhil is referring to the spec14:16
flaper87which needs lots of work14:16
flaper87I think it'll take a couple of months for that spec to be ready14:16
flaper87which means it'll fall into the N cycle14:17
nikhilflaper87: the back compat one or the refactor one?14:17
*** mbound_ has quit IRC14:17
flaper87nikhil: the refactor one14:17
nikhilok14:17
nikhilbut even with back compat one it's a painfully and hard to commit process14:18
nikhilfor instance supporting 2 APIs for 4 cycles is literally saying that you never get rid of it14:18
*** tsufiev has joined #openstack-meeting-414:18
nikhilthe amount of catch up needed is humoungous14:18
flaper87We can refactor the refactor spec and do a more progressive work towards something saner14:18
*** zeih has joined #openstack-meeting-414:18
nikhileven progressive work14:19
flaper87I hate to assume stuff but here I go: I'd assume that many issues since migrating glance to the new glance_store API is most of the work14:19
nikhildoesn't guarantee less catch required14:20
flaper87True but at least it makes it more manageable14:20
flaper87nikhil: may I ask what your suggestion is?14:20
nikhilsure the API is, but not the x-prj enforcement14:20
*** javeriak has quit IRC14:20
nikhilI think we have 3 choices:14:20
nikhil1. let things be as is and progress with x-prj requirements14:21
nikhil2. add exception to x-rpj list of libraries that do not warrant a API back compat contract, so that we can port it in a cycle or max 214:21
nikhil3. put back store in glance or mark it as private library (or one w/o API guidelines) (we can refactor the API if it remains married to glance)14:22
*** mbound_ has joined #openstack-meeting-414:22
kragnizI personally think we either need a new api, or to move it back into the glance tree14:22
flaper87so, to me, #3 is out of discussion14:22
kragnizcurrently the library is a real pain to use14:23
flaper87As of now, I'd go with #2 and add the exception14:23
sabarido we need an exception for glance_store ? The spec seems to say we need to adhere to semver and can make breaking changes, right ?14:23
flaper87Fix the API, make it consumable by other projects that still want to consume it (a.k.a Nova) and then commit to the backwards compat policy14:23
nikhilsure, but still sanely maintainable. I fear a large refactor could potentially disrput any perf/reliability enhancement done14:23
*** fawadkhaliq has quit IRC14:24
flaper87That we need to discuss on the spec. I think the whole way the spec started gave the wrong impression of what the goal is14:24
*** fawadkhaliq has joined #openstack-meeting-414:24
flaper87A fourth option would be to start a whole new library and let glance_store die14:24
flaper87That new library would do what glance_store is supposed to do but w/ a new API14:24
nikhilsabari: seems to have a hidden clause. the feeling I got was breaking directly wasn't allowed14:25
flaper87ok, we need to move on so, to have some action items14:25
nikhilflaper87: sure, #4 is a good option too14:25
flaper87Can we mention this on the x-proj spec?14:25
nikhilI will14:25
nikhilwanted to get early glance feedback, thanks/14:26
flaper87We need a way to be able to either refactor glance_store or create a new one14:26
flaper87I'm sure good feedback will come out from that spec and ppl following it14:26
flaper87nikhil: thanks for bringing this up14:26
flaper87#action nikhil to bring the glance_Store refactor discussion on the x-proj compat spec14:26
flaper87ok, moving on unless there's something else critical here14:27
flaper87#topic Cross-project work (flaper87)14:27
*** openstack changes topic to "Cross-project work (flaper87) (Meeting topic: Glance)"14:27
flaper87on a similar note to what nikhil just mentioned, I think we need to improve our x-proj presence14:27
flaper87nikhil: I believe you're the x-proj liaison, right?14:27
nikhilyes14:27
flaper87coolio14:28
flaper87what do you think about having x-proj updates at the beginning of our meeting ?14:28
flaper87Just like artifacts and drivers14:28
nikhilit's mostly formalizing the process and getting some chasers to put on the list of people14:28
nikhilflaper87: surely, I think the p14:28
nikhilthough the proposal was14:28
nikhilyou need to have a comment on the x-prj spec14:29
*** salv-orlando has joined #openstack-meeting-414:29
nikhilbut prolly still developing14:29
flaper87yeah14:29
nikhilI can request feedback in the meeting or outside depending on time constraints whatever you all prefere14:29
flaper87I'm currently worried about our presence in the x-proj meetings and how much feedback we're giving on that area14:30
*** Piet has quit IRC14:30
flaper87I'm wondering if we should have 2 liaisons so that you have some help there14:30
nikhilheh14:30
nikhilwe had one x-prj meeting in 3 weeks14:30
flaper87yup14:30
*** salv-orlando has quit IRC14:30
flaper87ok, lets start by having an x-proj specific topic in our meetings14:30
flaper87I think that'd help a lot14:31
nikhilok14:31
flaper87nikhil: btw, don't get me wrong. I think you're doing a great job. I hope this topic didn't come out the wrong way14:31
nikhiland I am just back settling in catching up with backlog :/14:31
nikhilflaper87: yeah, np14:31
flaper87coolio, moving on unless there's something else here14:32
*** salv-orlando has joined #openstack-meeting-414:32
flaper87#topic Community Recognitions14:32
*** openstack changes topic to "Community Recognitions (Meeting topic: Glance)"14:32
flaper87So, I don't really have a way to recognize ppl's work other than mentioning it publicly in our meetings. I think some folks have been doing an amazing job and I would like to, at the very least, recognize that here in a per-milestone basis14:33
flaper87Just a shutout for folks to know that we love them :D14:33
flaper87Here it goes:14:33
flaper87From a bug squashing POV, I'd like to give a special thanks to bunting and kairat14:34
flaper87They have been working like machines on killing as many bugs as possible14:34
flaper87and it's been amazing to review all those patches14:34
sabaribunting kairat ++14:34
buntingEvil bugs :) Cheers!14:34
kairatthanks)14:34
mfedosinthanks folks14:34
* nikhil claps14:34
flaper87Please, do keep it up and sorry for all those -1's/-2's and nitpicks14:34
flaper87Bare with us while we try to keep up with your work14:35
flaper87I'd like to make one more recognition for this milestone14:35
flaper87and it goes to mfedosin for his amazing work in making nova work with glance v2. It has not been easy and it's required a good deal of cross-project interaction, patience and tolerance14:36
flaper87That's one of our priorities for Mitaka and it's moving forward quite well14:36
flaper87So, thanks mfedosin again for your efforts there and please, don't give up. :D14:36
mfedosinoh... it's not done yet, actually14:36
mfedosinbut will be very soon14:37
flaper87I know it's not done, that's why I'm begging you to not give up14:37
flaper87:D14:37
mfedosinand trusts too14:37
mfedosinI won't give up for sure :)14:37
mfedosinthank you :)14:37
flaper87It goes without saying that the whole team did an awesome job for M-1 and the review rate has been way better! But, I think this 3 folks deserve a special thank from all of us this time :)14:37
*** njohnston has quit IRC14:38
* flaper87 sends beers to everyone14:38
flaper87moving on14:38
flaper87actually14:38
flaper87if you would like to recognize someone's work, please, feel free to add this topic to the agenda at any time14:38
*** njohnston has joined #openstack-meeting-414:38
flaper87I'll do it once per milestone at least14:38
flaper87ok, now, for realz, moving on14:39
flaper87#topic CORS headers in glance: https://review.openstack.org/#/c/219478/ (kairat)14:39
*** openstack changes topic to "CORS headers in glance: https://review.openstack.org/#/c/219478/ (kairat) (Meeting topic: Glance)"14:39
flaper87kairat: floor is yours14:39
kairatOk, please look into review14:39
kairatkrotscheck would like to clarify what headers are required for glance14:40
kairatbut after analyzing the question it turned out that we have a lot of headers, because we are passing metadata as headers14:40
kairatSo I am wondering what minimal set of headers we should set as default for CORS14:41
mclaren(that's v1 only I think?)14:41
flaper87kairat: that's v1 only, though.14:41
flaper87AFAIR14:41
flaper87:D14:41
flaper87mclaren: yup14:41
kairatThat's perfect14:41
mclarenprobably ok to support just v2?14:41
kairat+10014:41
flaper87mclaren++14:41
tsufievmclaren, no objections here14:41
mfedosinyes14:41
flaper87awesome, another happy customer. NEXT!14:41
flaper87:D14:41
kairatcool14:41
nikhilit looks fine14:42
flaper87kairat: tsufiev I take you're all set now14:42
tsufievstill, just enabling CORS headers is not enough to solve the task of Glance images upload from Horizon (the one that CORS is going to solve)14:42
kairatflaper87, yep14:42
tsufievflaper87, so, we're not ^^ :)14:42
* flaper87 reads14:42
flaper87tsufiev: what do you mean by "the task of glance images upload" ?14:43
kairattsufiev, I guess the next topic is about that14:43
flaper87"task" is a dangerous term in this team14:43
tsufievflaper87, see https://blueprints.launchpad.net/horizon/+spec/horizon-glance-large-image-upload14:43
flaper87:D14:43
nikhilflaper87: topic change14:43
tsufievthe last comment in w14:43
tsufiev*in Whiteboard14:43
nikhilI think we are talking about "multipart/form-data support in glance api "14:44
tsufievnikhil, yes14:44
nikhilnot that I want to shun this discussion :)14:44
mfedosinflaper87: if we want to upload files to glance from Horizon we have to deal with multipart/form-data14:44
flaper87nikhil: tsufiev ahhh14:44
flaper87tsufiev: you hijacked the topic14:44
flaper87bad bad bad tsufiev14:44
kairat:)14:44
mclarenI don't know much about this tbh -- is there anything here to consider around image import?14:44
flaper87#topic multipart/form-data support in glance api (tsufiev)14:44
*** openstack changes topic to "multipart/form-data support in glance api (tsufiev) (Meeting topic: Glance)"14:44
flaper87now we can talk about that14:44
tsufievflaper87, sorry, I'm not familiar with local policies )14:45
flaper87tsufiev: are you aware of the efforts going into revamp the import process for images?14:45
*** yamamoto has quit IRC14:45
flaper87tsufiev: np, I was joking14:45
flaper87I think this is something that will have to be considered as an enhancement for the new import process14:45
tsufievflaper87, I had a discussion with Brian Rosmaita in spec CR comments, but according to him, Glance wants to offload this thing to Swift14:45
tsufievand that's the point I disagree with14:46
flaper87tsufiev: oh yeah, that sounds outdated14:46
flaper87:P14:46
flaper87discussions have evolved since then14:46
flaper87and direct upload is not going away14:46
tsufievflaper87, good to hear :)14:46
flaper87Anyway, I think we'll have to take this under consideration for the revamped import process14:47
flaper87mclaren: agreed ?14:47
nikhilso, afair this is supported to an extent14:47
kairatSoo14:47
flaper87perhaps not in mitaka but at least for N14:47
tsufievhm...14:47
nikhiloh wait, that's just reads14:47
nikhilnvm14:47
tsufievflaper87, is there any blocker?14:47
kairatShould we allow to upload image without task?14:47
nikhilrange writes is different14:47
nikhiltsufiev: range writes is a complicated problem14:47
*** jmckind has joined #openstack-meeting-414:47
*** xingchao has joined #openstack-meeting-414:47
kairatbecause we need to deal multipart/form-data in this case14:48
nikhiltsufiev: I had a discussion with swift PTL and he mentioned it to be a PhD thesis14:48
flaper87tsufiev: yup, we're not going to modify the current upload path. That's our current blocker14:48
mclarenflaper87: yup14:48
flaper87we're almost at the end and there's one more topic14:48
tsufievnikhil, flaper87: I heard that multpart/form-data decoder could be implemented as an additional middleware14:48
tsufievI think it was ativelkov who told me that14:48
flaper87tsufiev: we'll explore that for sure, it just needs to wait a bit longer14:49
nikhillast write wins and when you enable multiple uploads, guaranteed success rate of a data write will be significantly low14:49
flaper87as we don't have cycles to discuss/implement that and it isn't part of the mitaka priorities14:49
flaper87ok, moving on! (sorry for cutting the discussion)14:49
nikhiltsufiev: ok, we should discuss this offline. I am interested in knowing more14:49
flaper87#topic SHA-2 and openssl dependency14:49
*** openstack changes topic to "SHA-2 and openssl dependency (Meeting topic: Glance)"14:49
flaper87no idea who added that14:49
tsufievnikhil, ok14:49
hemanthmthat's me14:50
flaper87hemanthm: hey! :D14:50
hemanthmhttps://github.com/openstack/glance/blob/master/glance/common/signature_utils.py#L43-L4814:50
* mclaren note to self: s3 objects seem to support multipart http://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectPOST.html14:50
hemanthmSo, image signing makes use sha-2 exclusively for digest14:50
flaper87bpoulos: ^14:51
hemanthmAnd, SHA-2 is supported by default on openssl 1.0.1 or higher versions14:51
hemanthmnow, on certain platforms like debian6, openssl only goes up to 0.9.814:51
flaper87ah mmh :(14:52
hemanthmwhich doesn't support SHA-2 by default14:52
*** Swami has joined #openstack-meeting-414:52
hemanthmso, glance build is broken on those platforms14:52
flaper87as dhellmann mentioned in the drivers meeting, can we pick the default based on the openssl version?14:52
flaper87bpoulos: ^14:52
* flaper87 throws some cookies in the channel to grab bpoulos attention14:53
nikhildoes anyone recollect what metadata is set?14:53
nikhilconfigurability might affect resiliency, so a bit curious14:53
bpouloshemanthm: I'll take a look14:53
bpoulosI wasn't aware of this dependency14:53
flaper87I knew cookies would work14:54
hemanthm:)14:54
bpouloshaha14:54
hemanthmbpoulos: thank you!14:54
*** yamamoto has joined #openstack-meeting-414:54
flaper87aaaaaaaaaaaaand another happy customer!14:54
flaper87:D14:54
hemanthmcan I get some cookies too?14:54
flaper87#action bpoulos to look into the openssl dependency for the default signature method14:54
* flaper87 gives hemanthm cookies and a cup of coffee14:54
flaper87I'd have thrown coffee in the channel but that'd have been a disaster14:55
flaper87#topic Open Discussion14:55
*** openstack changes topic to "Open Discussion (Meeting topic: Glance)"14:55
flaper87o/14:55
kairatflaper87, there is one more topic from bunting as I can see14:55
flaper87Last week I asked for feedback w.r.t the glance ocmmunity, thinks that are working and especially, thins that are broken14:56
buntingYeah14:56
buntingI was gonna bring up what we were talking about in the glance room earlier14:56
flaper87I've got some feedback but not as much as I'd love too. Here's another request for feedback :D14:56
*** TravT has joined #openstack-meeting-414:56
flaper87oh, I'm sorry, I didn't see it14:56
flaper87there are 4 mins left14:56
flaper87is that enough? or should we wait for next week?14:56
buntingThere might not be enought time14:57
flaper87or discuss it in -glance ?14:57
nikhilflaper87: may be carry over the discussion topics to next meeting (there are 3)14:57
nikhil?14:57
flaper87yup, I'll do that14:57
avarner_Can I get opinions on Bandit tests? Any particular tests that people think are important?14:57
*** sigmavirus24_awa is now known as sigmavirus2414:57
flaper87oh the Discussion Topics section14:57
flaper87I totally skipped that14:57
*** mestery has joined #openstack-meeting-414:57
* flaper87 slaps himself14:57
flaper87sorry about that14:58
nikhiland I thought it was the time14:58
*** rbak has quit IRC14:58
nikhil:P14:58
flaper87it was the time and my blindness14:58
* flaper87 freaks out when he's running out of time14:58
flaper87it's a dangerous situation to be in14:58
buntingHaha don't worry14:58
buntingIt seems we had two topic sections14:59
flaper87lets have a single section for all topics14:59
flaper87we can use sub-bullets14:59
flaper87ok, thanks folks14:59
flaper87#endmeeting14:59
*** openstack changes topic to "Q&A (Meeting topic: openstack-vahana)"14:59
openstackMeeting ended Thu Dec  3 14:59:43 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-12-03-13.59.html14:59
nikhilavarner_: not aware atm, I will get to review soon14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-12-03-13.59.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-12-03-13.59.log.html14:59
kairatthanks14:59
mclarenthanks15:00
*** avarner_ has left #openstack-meeting-415:00
*** kairat has left #openstack-meeting-415:00
*** mclaren has quit IRC15:00
*** bunting has left #openstack-meeting-415:00
TravT#startmeeting openstack search15:00
openstackMeeting started Thu Dec  3 15:00:39 2015 UTC and is due to finish in 60 minutes.  The chair is TravT. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: openstack search)"15:00
openstackThe meeting name has been set to 'openstack_search'15:00
*** yingjun has joined #openstack-meeting-415:01
*** sjmc7 has joined #openstack-meeting-415:01
TravTo/15:01
nikhilo/15:01
sjmc7ello15:01
yingjunhi15:01
*** mfedosin has quit IRC15:02
*** vikram has joined #openstack-meeting-415:02
TravTmaybe a smaller crowd here today.15:02
TravTHere's the agenda: https://etherpad.openstack.org/p/search-team-meeting-agenda15:02
nikhilwhat has happened to the world!?15:03
*** julim has quit IRC15:03
*** bpoulos has left #openstack-meeting-415:03
rosmaitao/15:03
*** mbound_ has quit IRC15:03
rosmaitanikhil: don't ask! bad shit is going on everywhere15:03
TravTyeah, seriously15:03
*** ninag_ has left #openstack-meeting-415:03
nikhilhow are things in chicago and fort collins?15:03
sjmc7cold15:03
TravTcan't complain too much... just a bit cold15:04
TravTnikhil, are you still in blacksburg?15:04
nikhilrosmaita: oh man! every-time I read news my faint in humanity sinks :(15:04
nikhilfaith*15:04
nikhilTravT: yeah15:04
TravTyingjun: where do you live?15:04
nikhilsjmc7: hope the snow situation is better15:04
nikhilhope lakshmi is doing fine (with flood situation)15:04
yingjunChina, Changsha15:05
nikhilhi yingjun, we've never met (even virtually)15:05
TravTcool, we're really happy to have you join in the fun here!15:05
yingjunHI, nikhil15:05
nikhilfun indeed15:05
yingjun:), nice to join15:06
nikhilTravT: glad to hear, things are better there.15:06
* nikhil shuts up15:06
*** julim has joined #openstack-meeting-415:06
TravTallright, let's get on with some topics. we seem to be missing a couple faces, but that happens.15:07
TravT#topic m1 is today15:07
*** openstack changes topic to "m1 is today (Meeting topic: openstack search)"15:07
TravTSo, there's this: https://openstack.nimeyo.com/66888/openstack-dev-release-preparing-your-mitaka-milestone-tag15:07
ekarlsohola15:08
*** zeih has quit IRC15:08
ekarlsoi'm lurking :P15:08
TravThowdy ekarlso!15:08
*** sdake has joined #openstack-meeting-415:08
*** mbound_ has joined #openstack-meeting-415:08
TravTi'll look at taking care of submitting a few things up15:08
TravTbut did have a couple questions15:08
TravTare we aware of any release notes that we missed before landing reno?15:09
sjmc7no, don’t think so15:09
TravTpossibly we should have had one for this patch15:10
TravThttps://review.openstack.org/#/c/245981/15:10
TravTbut i'm not thinking we need to stress over it.15:10
rosmaita+1 for no stress15:10
sjmc7:)15:10
nikhil:)15:11
TravTso then the next question is version...15:11
TravTwe had previously discussed whether to go to 1.0 with mitaka15:11
TravTi think that is the desired goal15:11
TravTbut right now setup.cfg os 0.215:12
sjmc7i suppose that depends what we want to call 1.015:12
TravTin reading that email, it seems like we should propose 0.2b1 because that is in setup.cfg15:12
TravTbut that might mess things up if we jump to 1.0 at the end of mitaka15:13
rosmaitaTravT: i am glad you are PTL, i am having a hard time understanding the process15:13
nikhilprocess is very dynamic15:14
TravTlol, yeah, there have been quite a few changes this last bit in how the release team wants to do things15:14
nikhilnot sure if we need to invent a new word for openstack process15:14
rosmaitai think i used a good word earlier15:14
TravT:D15:14
nikhilI may decide to use urban dictionary finally again after 3 years15:14
nikhilrosmaita: you go for it then15:15
TravT\o?15:15
nikhilTravT: I think it should be fine with the .2b115:15
TravTthat's my head scratching emoticon15:15
nikhilnice!15:15
TravTnikhil: yeah, i think so too.  we'll sort out 1.0 decision at the end of this release.15:15
nikhilcool15:16
rosmaitaworks for me15:16
nikhil(was just about to enter) TravT: why do you anticipate it to be an issue?15:16
nikhilbut cool now15:16
TravTfor me, 1.0 is a signal that we'll start formally handling deprecations and adhere to stability of plugin interfaces15:16
nikhilgotcha15:16
TravTnikhil: because this process is new that doug put out (including reno) and nobody has experience with it.15:16
nikhilmakes sense15:17
TravTok, well, i'll work on the tag etc today and ping in room if needed later.15:17
TravTso along these lines15:18
*** rbak has joined #openstack-meeting-415:18
TravT#topic searchlight client launchpad project15:18
*** openstack changes topic to "searchlight client launchpad project (Meeting topic: openstack search)"15:18
TravTyingjun: has been working on the client15:18
TravT\o/15:18
sjmc7i vote strongly not to have another launchpad project15:18
sjmc7and thanks yingjun for all the hard work15:19
yingjun+115:19
TravTi sent out an email http://lists.openstack.org/pipermail/openstack-dev/2015-November/080525.html15:19
nikhilyingjun: ++15:19
rosmaitayingjun: +++15:19
nikhilsjmc7: haha, nice. I think that's fine to have everything consolidated15:19
nikhilso, +1 from me too15:19
sjmc7i can’t see us ever having a huge number of client-specific issues open15:20
nikhilbtw15:20
nikhilTravT: do we plan to release client in M?15:20
TravTi'm happy to not use it for now. my only question was if this would cause us issues with release managment since the client doesn't have to follow the same release schedule.15:20
TravTnikhil: that would be the goal15:21
sjmc7ah. that, i don’t know15:21
TravTi added release onto that email, but only got crickets from them.15:21
nikhilTravT: I think you can rely on reno for rel mgmt but for milestone tracking no15:21
TravTi think they are dealing with changing the processes for every project right ow15:21
nikhilTravT: you prolly want to be aware about https://review.openstack.org/#/c/22615715:22
nikhilI brought that up in glance mtg15:22
nikhiland it adds a new clause for client back compat15:22
TravTcan you summarize for us?15:22
nikhilso, the client release timing would be essential15:23
nikhilsure15:23
*** numans has quit IRC15:23
nikhilit's mostly saying that all clients and libraries need to support back compat15:23
nikhilwell it mentions that you can deprecate it15:23
nikhilbut need to give that some time15:23
nikhilthe example suggests 4 cycles15:23
nikhilbut I don't anticipate if that would ever be true15:23
nikhilso, when we release something15:24
nikhilwe want to ensure that we absolutely want that API to exist for a long time15:24
nikhilif we need to have breaking changes the `process` will be quite painful15:24
nikhilso, for SL client15:24
nikhilif we need to have it in M15:24
*** markvoelker_ has quit IRC15:25
nikhilwe prolly should test a beta and commit to client API (CLI stuff) in M official release15:25
* nikhil done15:25
nikhilsorry I missed an imp point -- that sort of ties in with the LP project15:25
nikhilto determine the commitment that the project is giving to the API in a official project page (wherever that might be)15:26
* nikhil done for reals15:26
TravTthx nikhil15:27
TravTdid doug add reno to the python glanceclient?15:27
nikhilno15:27
nikhiland I don't think they expect15:27
nikhilbut some folks from IBM are requesting15:27
nikhiland that is a discussion item for me with mr. flavio15:28
nikhilthat I haven't gotten to yet (with backlog list growing)15:28
TravTok, so nikhil, does everything you just said and your experience with glance client keep your vote at a +1 to not have a separate launchpad project for searchlight client?15:29
nikhilTravT: nah, that bring me to 015:29
nikhil+1 for consolidation15:29
sjmc7i’m tremendously confused :)15:29
nikhil-1 for explicit communication15:29
*** dshakhray has quit IRC15:30
nikhilsjmc7: sorry, I realized a bit before that, I did that15:30
TravTwe might need the project just for somewhere to upload the releases of it15:30
nikhilTravT: well, what I meant to say is15:30
david-lyleI think it should be separate, to be contrarian15:30
TravTo/ david-lyle15:31
nikhilI gave some tradeoffs to you all and we can choose to prefer one way over other based on what we want to deal with later15:31
*** mancdaz has quit IRC15:31
*** julim has quit IRC15:31
TravTdavid-lyle: are you being contrarian for fun or is that your real opinion?15:31
*** mancdaz has joined #openstack-meeting-415:31
david-lylethe issues and releases are unique15:31
david-lyleonce people start piling on bugs and bps, it will get noisy15:32
david-lyleand harder to track15:32
*** julim has joined #openstack-meeting-415:32
TravTthe separate releases is the thing that makes me lean towards having its own project15:32
david-lylefor consumers and devs15:32
*** ajmiller has joined #openstack-meeting-415:33
TravTi think we need to record a vote here... but before doing, any more points to consider?15:33
sjmc7yeah, i’m leaning that way as well now15:33
nikhilI was told in a x-prj metg15:34
nikhilthat we are going to have some other tool for bugs15:34
nikhilnot LP15:34
nikhilnot sure how much has that been moved fwd15:34
david-lylenikhil: they've said that for 5 releases now15:34
david-lyleI'll believe it...15:34
nikhil:)15:34
*** dtardivel has joined #openstack-meeting-415:34
TravTi'm wondering how that'll help things at this point15:34
david-lylechange for the sake of change15:35
nikhilthe opinion they had was projects can have LP for their own tracking purposes15:35
*** blahRus has joined #openstack-meeting-415:35
nikhilbut some <tool> for bugs, spec for BPs, and reno for rel15:35
nikhilthat was my impression15:35
nikhilbut as a prj we can choose to have LP15:35
nikhiland like I said, there are tradeoffs to either15:36
nikhilwith my +015:36
david-lyleuntil the replacement is more than handwaving, launchpad is what we have15:36
TravTi fail to see how specs (gerrit) on its own actually is good enough for BPs. (no assignees, priority, etc)15:36
*** klamath has quit IRC15:37
* TravT worries that the wheels are coming off the bus for process management tools15:37
david-lylewe're on 3/4 now15:37
*** klamath has joined #openstack-meeting-415:37
*** klamath has quit IRC15:37
david-lylenothing mass confusion and chaos won't fix15:38
david-lyle:(15:38
TravTokay, to stay on track with current topic, i'm going to put out a irc vote.15:38
nikhil:D15:38
TravT#startvote (Should we use a separate LP project for python-searchlightclient)? yes, no15:38
*** klamath has joined #openstack-meeting-415:38
openstackBegin voting on: (Should we use a separate LP project for python-searchlightclient)? Valid vote options are yes, no.15:38
openstackVote using '#vote OPTION'. Only your last vote counts.15:38
david-lyle#vote yes15:39
rosmaita#vote yes15:39
nikhilI am fine w/ either15:39
TravT#vote yes15:39
sjmc7#vote yes15:39
TravTyingjun?15:39
yingjunfine for either too15:40
TravTekarlso: you still lurking and care at all?15:40
*** yamamoto has quit IRC15:40
TravT#endvote15:41
openstackVoted on "(Should we use a separate LP project for python-searchlightclient)?" Results are15:41
openstackyes (4): TravT, david-lyle, rosmaita, sjmc715:41
TravTokay, so we'll keep it...15:41
*** kebray has joined #openstack-meeting-415:41
yingjunI’ll update the doc..15:42
TravTthank you!15:42
TravT#topic client command brainstorming15:42
*** openstack changes topic to "client command brainstorming (Meeting topic: openstack search)"15:42
TravTyingjun: has a patch up with the first command on it15:42
TravThttps://review.openstack.org/#/c/249076/15:42
*** daneyon has joined #openstack-meeting-415:43
TravTi added a comment about starting to sketch out the full suite of commands (so we have a basic roadmap of where we are going even if the first patch is only the first command)15:43
*** jed56 has joined #openstack-meeting-415:43
TravTbut i think we should spend some time brainstorming that out15:43
TravTso, we don't have to do it here15:44
TravTbut here is an etherpad15:44
TravThttps://etherpad.openstack.org/p/searchlight-cli-brainstorming15:44
*** tsufiev has left #openstack-meeting-415:44
*** markvan has quit IRC15:45
TravTso, please take a look and add thoughts15:45
ekarlsotarya :p15:45
ekarlsoTravT: ..15:45
ekarlsoTravT: just busy busy -,,-15:46
TravTno worries15:46
TravT#topic specs15:46
*** openstack changes topic to "specs (Meeting topic: openstack search)"15:46
ekarlsoanyone started the cli yet that I can take a look at ?15:46
*** markvan has joined #openstack-meeting-415:46
TravTekarlso: yingjun has started it15:46
sjmc7https://review.openstack.org/#/c/247565/ ekarlso15:47
sjmc7and https://review.openstack.org/#/c/249076/15:47
ekarlsook, i'll go look alter :)15:47
TravTthank you!15:47
TravTre: specs15:47
TravTsjmc7 and I have been having some fun with two that are "essential" for mitaka15:48
TravTthey are admittedly kind of heavy to read15:48
TravTbut we do need to work through them and come to some conclusion so we can work them out15:48
TravTand get implemented this release15:49
TravTif you can take a look please do.  sjmc7 is actually going to be in fort collins next week, so we'll talk through them more in person next week15:49
TravT    Admin search fields unless already addresed above15:50
TravT      https://review.openstack.org/#/c/245357/15:50
TravT    Zero downtime re-indexing15:50
TravT      https://review.openstack.org/#/c/245222/15:50
TravTsjmc7: anything specific to bring up today?15:50
sjmc7about those? not really, except if anyone’s interested to look them over15:51
sjmc7though i did also want to briefly mention the elasticsearch client version palava15:51
TravT#topic elasticsearch client versioning15:51
*** openstack changes topic to "elasticsearch client versioning (Meeting topic: openstack search)"15:52
*** BjoernT has joined #openstack-meeting-415:52
sjmc7that’s the one!15:52
TravTmention away sjmc715:52
sjmc7apologies yingjun, i should’ve mentioned i’d already proposed a patch to openstack/requirements at https://review.openstack.org/#/c/252075/15:52
sjmc7capping the client version at 1.9.015:52
yingjunsjmc7, no worries15:53
sjmc7gordon chung seems ok with it15:53
sjmc7says they’ve only tested with 1.715:53
sjmc7and i don’t think anyone else uses it15:53
*** yamamoto has joined #openstack-meeting-415:54
sjmc7i’ll pick some random infra people today to add as reviewers15:54
TravTyeah, we need to get this through15:54
*** inc0 has quit IRC15:54
sjmc7we’ll need to do a small amount of work to be 2.0-compatbile15:54
sjmc7i’ll file a ticket15:54
TravTbecause searchlight doesn't work in out of the box devstack at the moment because of the 2.0 client release.15:55
david-lyleis the query syntax different between versions?15:55
sjmc7david-lyle - there’s one thing that isn’t supported in 2.0, which is deleting by document type15:55
sjmc7that’s the only thing i’ve found we do that doesn’t work as expected15:55
*** markvoelker has joined #openstack-meeting-415:55
david-lyleok, that's not too bad15:56
sjmc7and actually, a fresh devstack install should be ok unless i’ve missed something15:56
sjmc7unless the data already exists15:56
sjmc7but yes, needs fixing15:56
*** oneswig has joined #openstack-meeting-415:57
TravThttps://bugs.launchpad.net/searchlight/+bug/151541215:57
openstackLaunchpad bug 1515412 in OpenStack Search (Searchlight) "python elasticsearch must match server version" [High,Triaged] - Assigned to Liyingjun (liyingjun)15:57
TravTok, well, let's get the version capped for now, unless yingjun / sjmc7 come up with a searchlight fix first.15:57
sjmc7i think the version cap’s sensible anyway15:58
sjmc7while devstack and most people will be using 1.x15:58
TravTi think for now...15:58
TravTbut it can't stay that way.15:58
*** javeriak has joined #openstack-meeting-415:58
*** pbourke has quit IRC15:58
TravTok, thanks yingjun and sjmc715:58
TravTout of time.15:59
TravT#topic parting words15:59
*** jlk has left #openstack-meeting-415:59
*** openstack changes topic to "parting words (Meeting topic: openstack search)"15:59
TravTany last words?15:59
*** pbourke has joined #openstack-meeting-415:59
TravTthanks everybody!15:59
TravT#endmeeting16:00
*** openstack changes topic to "Q&A (Meeting topic: openstack-vahana)"16:00
openstackMeeting ended Thu Dec  3 16:00:08 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-12-03-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-12-03-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-12-03-15.00.log.html16:00
*** yingjun has left #openstack-meeting-416:00
*** sjmc7 has left #openstack-meeting-416:00
*** stevelle has joined #openstack-meeting-416:00
*** TravT has left #openstack-meeting-416:00
*** julim has quit IRC16:01
*** zeih has joined #openstack-meeting-416:01
*** mattt has joined #openstack-meeting-416:02
*** KLevenstein has joined #openstack-meeting-416:03
*** sdake has quit IRC16:03
*** KLevenstein has left #openstack-meeting-416:03
*** holser_ has joined #openstack-meeting-416:03
*** gjayavelu has joined #openstack-meeting-416:03
*** iyamahat has joined #openstack-meeting-416:03
*** holser_ has left #openstack-meeting-416:03
*** julim has joined #openstack-meeting-416:03
*** ajmiller has quit IRC16:05
*** ajmiller has joined #openstack-meeting-416:05
*** sdake has joined #openstack-meeting-416:07
*** daneyon has quit IRC16:08
*** yamamoto has quit IRC16:08
*** tfly has joined #openstack-meeting-416:08
*** tfly has joined #openstack-meeting-416:08
*** tfly has quit IRC16:08
*** xingchao has quit IRC16:08
odyssey4me#startmeeting OpenStack Ansible Meeting16:09
openstackMeeting started Thu Dec  3 16:09:05 2015 UTC and is due to finish in 60 minutes.  The chair is odyssey4me. Information about MeetBot at http://wiki.debian.org/MeetBot.16:09
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:09
*** openstack changes topic to " (Meeting topic: OpenStack Ansible Meeting)"16:09
openstackThe meeting name has been set to 'openstack_ansible_meeting'16:09
*** alextricity has joined #openstack-meeting-416:09
odyssey4me#topic Agenda & rollcall16:09
*** openstack changes topic to "Agenda & rollcall (Meeting topic: OpenStack Ansible Meeting)"16:09
odyssey4me#link https://wiki.openstack.org/wiki/Meetings/openstack-ansible#Agenda_for_next_meeting16:09
serverascodeo/16:09
alextricityhere16:09
oneswig\o16:09
palendaePresent16:09
stevelleo/16:09
*** Sam-I-Am has joined #openstack-meeting-416:09
javeriakhere16:09
Sam-I-Amyay two meetings at once16:09
*** tfly has joined #openstack-meeting-416:09
mattt\o16:10
*** fawadkhaliq has quit IRC16:10
odyssey4mesorry for the belated start16:10
jwagnero/16:10
hughsaundershey16:10
*** dandruta has joined #openstack-meeting-416:10
*** gomarivera has joined #openstack-meeting-416:11
*** yamamoto has joined #openstack-meeting-416:11
odyssey4meok, so a quick review16:12
*** prometheanfire has joined #openstack-meeting-416:12
odyssey4me#topic Review action items from last week16:12
*** openstack changes topic to "Review action items from last week (Meeting topic: OpenStack Ansible Meeting)"16:12
prometheanfirehi16:12
odyssey4me12.0.1 and 11.2.5 were released16:12
*** KLevenstein has joined #openstack-meeting-416:12
odyssey4mewe missed a meeting last week - I hope everyone had a great Thanksgiving :)16:13
odyssey4me#topic Release Planning and Decisions16:13
*** openstack changes topic to "Release Planning and Decisions (Meeting topic: OpenStack Ansible Meeting)"16:13
odyssey4meok, so today we need to make a call of 3 releases16:13
*** pabelanger has joined #openstack-meeting-416:13
odyssey4me#link https://launchpad.net/openstack-ansible/+milestone/mitaka-116:13
odyssey4me#link https://launchpad.net/openstack-ansible/+milestone/12.0.216:14
odyssey4me#link https://launchpad.net/openstack-ansible/+milestone/11.2.616:14
odyssey4mefor Mitaka-1 I had hoped that we'd have the upgrade work done by now, but unfortunately that hasn't really happened16:14
*** yamahata has joined #openstack-meeting-416:14
odyssey4meI think I can safely release it without much issue - any comments/thoughts/questions?16:15
*** klindgren has quit IRC16:16
*** evgenyf has quit IRC16:16
matttodyssey4me: upgrade work?16:16
odyssey4memattt https://blueprints.launchpad.net/openstack-ansible/+spec/liberty-upgrade-path / https://etherpad.openstack.org/p/openstack-ansible-upgrade-framework16:16
odyssey4meso far we have no-one biting on any of the work16:16
odyssey4meno input at all in the etherpad, except my own16:17
odyssey4meso we'll have to carry that to the next milestone16:17
odyssey4mebut I'd really like some input there in the next week, please16:17
matttyeah i think the last thing people are focusd on at the minute is upgrading liberty :P16:17
odyssey4memattt the idea is to prepare an upgrade framework which will act as the basis for all upgrades from now on16:18
odyssey4mewith the starting point being kilo -> liberty16:18
matttodyssey4me: ok makes sense16:19
palendaeodyssey4me: I think there was a group inside of Rackspace making a list of concerns for any type of upgrades, not just major -> major. I'm not sure who here is on that team though16:19
palendaeI know I've passed those links to them16:19
*** igordcard has joined #openstack-meeting-416:19
*** bpokorny has joined #openstack-meeting-416:20
*** yamamoto has quit IRC16:20
odyssey4mepalendae sure, and any efforts elsewhere can feed into this over time... but I think we already have some clear needs to work on and OSA can provide the appropriate tooling for downstream consumers to use16:20
palendaeYeah16:20
d34dh0r53I'm good with 11.2.616:23
odyssey4meI think that 12.0.2 needs https://review.openstack.org/25210016:23
*** salv-orl_ has joined #openstack-meeting-416:23
odyssey4meand yeah, 11.2.6 I think is good16:24
javeriakI'll give 252100 a review16:25
odyssey4methanks javeriak - that'd be great16:25
odyssey4me#startvote Release 11.2.6 today?16:26
openstackBegin voting on: Release 11.2.6 today? Valid vote options are Yes, No.16:26
openstackVote using '#vote OPTION'. Only your last vote counts.16:26
odyssey4me#vote yes16:26
alextricity#vote yes16:26
odyssey4me#vote Yes16:26
*** salv-orlando has quit IRC16:26
alextricity#vote Yes16:26
alextricity?16:26
odyssey4me:) it's case sensitive16:27
javeriak#vote Yes16:27
odyssey4med34dh0r53 palendae mattt hughsaunders ?16:27
odyssey4mecloudnull ?16:27
mattt#vote Yes16:27
mattt(since i'm not aware of any reason to not release??)16:27
*** paul-carlton1 has quit IRC16:27
stevelle#vote Yes16:28
cloudnull#vote Yes16:28
cloudnulltypie typie16:28
hughsaunders#vote yes16:28
palendae#vote yes16:29
odyssey4me#endvote16:29
openstackVoted on "Release 11.2.6 today?" Results are16:29
odyssey4melol16:30
alextricitythe suspense is killing me16:30
odyssey4meoh dear, we broke it16:30
odyssey4meI think it's clear. I'll tag after this meeting.16:30
alextricitynow we will never know16:30
jwagnerim gonna say its a yes16:30
cloudnullpushed till next week16:30
odyssey4menext -16:30
jwagneri demand a recount!16:30
d34dh0r53my chad was hanging16:31
odyssey4me#startvote Release 12.0.2 now, or wait until https://review.openstack.org/252100 merges into the Liberty branch? now, wait16:31
openstackBegin voting on: Release 12.0.2 now, or wait until https://review.openstack.org/252100 merges into the Liberty branch? Valid vote options are now, wait.16:31
openstackVote using '#vote OPTION'. Only your last vote counts.16:31
odyssey4me#vote wait16:31
cloudnull#vote Yes16:32
openstackcloudnull: Yes is not a valid option. Valid options are now, wait.16:32
cloudnull#vote Now!16:32
openstackcloudnull: Now! is not a valid option. Valid options are now, wait.16:32
odyssey4mehaha, cloudnull got reprimanded by a bot16:32
cloudnull#vote now16:32
cloudnull???16:32
cloudnullthank you openstack16:32
javeriakhaha oh man... you guys are going to drive the poor bot crazy16:32
alextricity#vote wait16:32
d34dh0r53#vote wait16:32
*** zehicle has quit IRC16:33
mattt#vote wait16:33
*** sridhar_ram has joined #openstack-meeting-416:33
BjoernT#vote Yes16:33
openstackBjoernT: Yes is not a valid option. Valid options are now, wait.16:33
BjoernT#vote now16:33
javeriak#vote now16:33
stevelle#vote now16:35
*** mestery has quit IRC16:35
hughsaunders#vote wait16:35
odyssey4meandymccr ?16:35
andymccr#vote now16:36
*** salv-orl_ has quit IRC16:36
*** kebray has quit IRC16:37
odyssey4meso there is a fair point to be made - tags are cheap, we can tag another release after the patch merges16:37
palendae#vote now16:37
*** mestery has joined #openstack-meeting-416:37
odyssey4meif that changes anyone's vote, that's cool16:37
odyssey4me#endvote16:38
openstackVoted on "Release 12.0.2 now, or wait until https://review.openstack.org/252100 merges into the Liberty branch?" Results are16:38
openstacknow (6): palendae, andymccr, javeriak, BjoernT, stevelle, cloudnull16:38
openstackwait (5): alextricity, d34dh0r53, mattt, odyssey4me, hughsaunders16:38
odyssey4mealright, I'll tag after the meeting :)16:38
*** dshakhray has joined #openstack-meeting-416:39
odyssey4mewe should probably actually discuss under what situations we would hold back a tag16:39
mattti think so16:39
matttbecause it feels a bit arbitrary at the moment16:39
odyssey4metags are cheap, and perhaps it should only ever be held back for a bug marked critical16:39
odyssey4meand critical would be for bugs that result in a seriously broken result16:39
cloudnullI'm good with that16:39
alextricityConsidering this is opensource...that works16:40
matttalextricity: haha16:40
*** aglarendil has quit IRC16:40
odyssey4me:)16:40
alextricitybut from the deploys perspective, it will suck to pull from the latest release tag only to result in a broken-stack16:40
*** aglarendil has joined #openstack-meeting-416:40
*** ashtokolov has quit IRC16:41
odyssey4mehaha, I see what you did there :)16:41
alextricity:)16:41
*** mmedvede has quit IRC16:41
odyssey4meall right16:42
odyssey4me#topic Open Discussion16:42
*** openstack changes topic to "Open Discussion (Meeting topic: OpenStack Ansible Meeting)"16:42
*** belmoreira has quit IRC16:42
odyssey4meanyone got anything specific to discuss?16:42
*** ashtokolov has joined #openstack-meeting-416:42
oneswigWhat should we do to get the ball rolling with multi-OS support?16:42
oneswigAs in, where can I help?16:42
palendaeoneswig: I think the biggest thing is a spec, and someone willing to spearhead it. As in, lead on the work16:43
cloudnull^ that16:43
cloudnullwe'd love to see Multi-OS16:43
BjoernT+116:43
odyssey4me#link https://etherpad.openstack.org/p/openstack-ansible-multi-os-support16:44
alextricity^^ That is definitely a good start.16:44
cloudnullwe just need some folks to want to help out with the work and to maintain it16:44
odyssey4methat's the working notes16:44
*** ajmiller_ has joined #openstack-meeting-416:44
BjoernTI'm a Fedora dude so I'm willing to help here16:44
alextricityWhat is this? https://blueprints.launchpad.net/openstack-ansible/+spec/multi-platform-host16:44
*** ajmiller has quit IRC16:44
odyssey4mewe are looking for someone to volunteer as the lead to co-ordinate the work16:44
palendaealextricity: afaik that's a placeholder right now16:45
odyssey4mewe're happy to orientate and coach, but no-one has yet stepped16:45
odyssey4meup16:45
cloudnulloneswig: I've done some work with RHEL/CentOS too but its a bit hacky at this point.16:45
odyssey4meoneswig how do you feel about taking up the lead?16:45
*** ajmiller__ has joined #openstack-meeting-416:45
oneswigI've previously worked on multi-distro ports of packaging, but won't have time to lead and do justice.16:45
palendaecloudnull: Is your Debian stuff up-to-date?16:45
cloudnullno16:45
oneswigI suggest we break it into pieces and spec those16:45
*** sdake has quit IRC16:46
odyssey4mealright, oneswig perhaps you can suggest that in the etherpad?16:46
cloudnulloneswig: ++16:46
cloudnullpalendae: i should rebase some of that16:46
cloudnullfor science :)16:46
odyssey4meadd your thoughts with regards to how the pieces would be broken up - we can all chime in16:46
palendaecloudnull: Mostly curious as some of that relates to getting ready for 16.04, too16:46
oneswigI'm already in the etherpad - I'll add notes16:46
palendaeLike systemd16:46
*** SimonChung1 has quit IRC16:46
oneswigIs there a means of testing what we do?16:46
oneswigCI for this stuff?16:46
odyssey4meBjoernT you can also add some notes into the etherpad16:47
cloudnullpalendae:  yea. the systemD stuff would be useful to get done16:47
odyssey4meprometheanfire as this is of interest for gentoo, I expect you'll have some thoughts too?16:47
palendaeoneswig: The current gates only do ubuntu right now, but openstack has infrastructure for red hat based distros16:47
cloudnullwe have a spce for that in Mitaka which I was supposed to work on but IDK if ill have time .16:47
odyssey4mepalendae yeah, CentOS/Fedora is easy right now in -infra16:48
*** ajmiller__ has quit IRC16:48
palendaecloudnull: My hunch is Mitaka's gonna miss getting 16.04 based on dates16:48
cloudnulli'd agree16:48
palendaeAlso since April is right before May, which I think is when Mitaka's out16:49
*** ajmiller_ has quit IRC16:49
odyssey4meyep, 16.04 I expect will need to be next cycle16:49
oneswigI am busy next week, but will pick up the week after16:50
*** KLevenstein is now known as KLev-away16:50
*** fawadkhaliq has joined #openstack-meeting-416:50
*** pbourke has quit IRC16:50
cloudnulloneswig: for general CI in OpenStack infra we're covered. If we get multi-OS convergence we can run tempest against the stack to validate functionality.16:50
cloudnulloneswig:  sweet !16:51
palendaecloudnull: Does infra allow us to add arbitrary distros?16:51
palendaeOr is it only Debian/Ubuntu and Red Hatty ones?16:51
cloudnulllast i remember, yes, if the distro being added was built using their image builder.16:51
palendaeAh, right16:51
cloudnulli think prometheanfire worked on some of that16:51
cloudnullhe may know more in that regards.16:51
odyssey4meyep, it takes some doing - but is not impossible16:52
palendaeSo there's tooling16:52
palendaeWhich is fine16:52
*** pbourke has joined #openstack-meeting-416:54
odyssey4mealright, unless anyone wants to raise anything else - we can continue chatting in #openstack-ansible16:54
odyssey4methank you all for your time today!16:54
*** mmedvede has joined #openstack-meeting-416:54
*** prithivm has joined #openstack-meeting-416:54
alextricitymaybe someone smarter than me can take a look at https://bugs.launchpad.net/openstack-ansible/+bug/152225016:54
openstackLaunchpad bug 1522250 in openstack-ansible "Ceilometer compute namespace drivers not loading" [Undecided,New]16:54
alextricityno rush though16:54
odyssey4mestevelle ^ ?16:55
*** erikwilson has joined #openstack-meeting-416:56
*** u_kozat has joined #openstack-meeting-416:56
cloudnullhe may know more in that regards. /16:56
cloudnullsorry ... .16:56
cloudnullalextricity:  is that liberty16:56
stevelleI'm thick in some other things right now with my ceilo workspace, testing that has to wait for me to clean it up a bit16:56
stevelleI did see it show up, and do intend to test it though16:57
alextricityim' working from master, but it probably affects liberty too16:57
alextricityI'm going to try it without venv to see if that fixes16:57
alextricityit16:57
cloudnullah. so python-libvirt likely needs to be installed in the venv16:57
alextricityprobably16:57
cloudnullsource the venv and install the libs to see if its fixed16:58
alextricityI'm little bit of a python noob when it comes to packaging things16:58
*** cathy_ has joined #openstack-meeting-416:58
alextricitywill do16:58
stevellesounds legit16:58
cloudnullonce you activate the venv, you can pip install python-libvirt and other things if needed16:58
alextricitysounds easy enough :)16:59
cloudnullif that fixes it, we can add the package to the ceilometer role and itll get picked up automatically.16:59
*** prithivm has quit IRC16:59
odyssey4mealrighty, we need to clear the room for the next meeting16:59
odyssey4methanks all :)16:59
*** oneswig has left #openstack-meeting-416:59
alextricitythank you!16:59
odyssey4me#endmeeting16:59
*** openstack changes topic to "Q&A (Meeting topic: openstack-vahana)"16:59
*** prithivm has joined #openstack-meeting-416:59
openstackMeeting ended Thu Dec  3 16:59:44 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-12-03-16.09.html16:59
cloudnullthanks odyssey4me16:59
cloudnullsee you all in the channel16:59
*** johnsom has joined #openstack-meeting-416:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-12-03-16.09.txt16:59
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-12-03-16.09.log.html16:59
cathy_#startmeeting service_chaining17:00
openstackMeeting started Thu Dec  3 17:00:04 2015 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
cathy_hi everyone17:00
*** Sam-I-Am has left #openstack-meeting-417:00
*** mohankumar has joined #openstack-meeting-417:00
vikramhi17:00
*** ozstacker_ has joined #openstack-meeting-417:00
mohankumarhi17:00
cathy_vikram: welcom back!17:00
johnsomo/17:00
vikramcathy_: thanx17:00
cathy_hi mohankumar johnsom17:00
*** s3wong has joined #openstack-meeting-417:01
*** qwebirc26088 has joined #openstack-meeting-417:01
pcarverhi17:01
cathy_hi s3wong17:01
cathy_hi pcarver17:01
*** alextricity has left #openstack-meeting-417:01
s3wonghello17:01
*** ozstacker has quit IRC17:01
cathy_any topic you would like to discuss today?17:01
Prithivsfc manager17:02
igordcardhi all17:02
vikramcathy_: I have raised a bug for that17:02
cathy_hi igordcard Prithiv17:02
vikramhttps://bugs.launchpad.net/networking-sfc/+bug/151336817:02
openstackLaunchpad bug 1513368 in networking-sfc "Introducing SFC manager" [Undecided,New] - Assigned to vikram.choudhary (vikschw)17:02
vikramcathy_: It will be great to have it17:03
s3wongwhat is SFC manager?17:03
*** BjoernT has quit IRC17:03
Prithivhi cathy... also, about the issue that i have posted in networking-sfc page17:03
*** ivar-laz_ has quit IRC17:03
cathy_vikram: yes, but we can deliver that in the second phase. Ok with you?17:03
Prithivhttps://review.openstack.org/#/c/233758/17:03
*** tfly has left #openstack-meeting-417:04
cathy_Prithiv: let me take a look at the link17:04
*** xingchao has joined #openstack-meeting-417:04
vikramcathy_: when is the second phase planned?17:04
prithivmthank you cathy17:04
cathy_vikram: could you change the bug name to something like "SFC OAM operation" since we already have a "SFC manager" terminology in our design to refer to management of the chain resources17:05
vikramcathy_: Sure I will17:05
*** mestery has quit IRC17:05
cathy_vikram: thanks.17:05
*** prithivm has quit IRC17:05
vikramcathy_: Done17:05
vikramcathy_: when is the second phase planned?17:05
vikramcathy_: Can you approve the bug so that we can start some initial write-up?17:06
*** mestery has joined #openstack-meeting-417:06
*** stevelle has left #openstack-meeting-417:06
mohankumars3wong , it monitor and helps debugging faults in SFC chain.17:06
vikrams3wong: Just changed the bug heading17:07
*** ScottMillward has quit IRC17:07
cathy_vikram: yes, I can do that17:07
s3wongvikram, mohankumar: OK... taking a look now. Thanks17:07
*** armax has joined #openstack-meeting-417:07
*** zeih has quit IRC17:07
cathy_Prithiv: the link in the comment is not valid. Could you check that and update the links? But anyway, we will take a look at the issue off line and get back to you.17:08
vikramcathy_: Thanks..17:08
Prithivsure. I will send you a detailed email about the error17:08
vikramCathy_: One help17:08
*** xingchao has quit IRC17:08
*** igordcard has quit IRC17:08
*** LouisF has joined #openstack-meeting-417:09
vikramCathy_: I feel most of the people are struggling testing our changes17:09
cathy_Prithiv: thanks. please, we will try it to see the problem, investigate that , and get back to you17:09
Prithivthank you cathy... no problem17:09
cathy_vikram: yes, we are doing the testing too.17:09
vikramCathy_: It would be better if can document the test procedure17:09
cathy_here are some update of our recent work17:09
pcarvervikram: +117:09
vikramCathy_: test + installation process17:10
cathy_I think most of the issues are related to the installation process.17:10
Prithivcathy: yes, i agree17:10
cathy_we spent quite some time getting it installed.17:10
pcarvervikram: I've been splitting my time between code review and trying to actually get the code working. I'm reluctant to spend too much time reviewing code when I can't get it to even install/work.17:10
*** igordcard has joined #openstack-meeting-417:10
*** mestery has quit IRC17:11
pcarverI'd spend more time reviewing code if I were spending less time just trying to get it installed/working.17:11
igordcardpcarver, +117:11
cathy_Now we have got it installed on multiple machines and start doing conprehensive end-to-end SFC setup/update/deletion functionality testing17:11
vikrampcarver: me either ;(17:11
Prithivpcarver: with you on that17:11
igordcardalso I can't seem to actually test it because the flow classifier is WIP17:11
LouisFigordcard: your email indicated that you have been able to install using your procedures17:11
igordcardLouisF, yes, it is running at the moment - however no flow classifier right?17:12
cathy_so looks like the devstack patch has some glitch integrating with the code17:12
LouisFigordcard: classifier should be there17:12
pcarverigordcard's latest procedure did work for me as far as installation, but I'm not sure I've actually reached functionally working.17:12
vikramcathy_: IMO, we must start getting the code in at the earliest17:13
PrithivLouis, i am not able to install with the latest commit of neutron (770624b13bf57fdab549bfb66ee9cc6781ae8d65) but am able to get the q-agt runnign with neutron older commit (commit 9b531b9e4eb6edfc1ad0d5ebfed6cd9b90e89422)17:13
LouisFigordcard: are you still having a problem starting the agent?17:13
igordcardLouisF, can you send some recommended API calls to deploy a simple working chain amongst 2 VMs, after the meeting?17:13
LouisFigordcard: ok17:13
igordcardLouisF, no, the agent is fine if I rollback neutron to some revisions earlier17:13
Prithivbut with the newer revision of neutron, the agent doesnt start17:14
LouisFigordcard: neutron or networking-sfc code?17:14
cathy_vikram: after we get the end-to-end functionality testing cases all passed, I will approve the codes. But before we get to that stage, I would rather not get the codes merged.17:14
Prithivit looks for the module create_agent_config_map17:14
Prithivand fails17:14
igordcardeverything seems to work from the outside, with the ovs driver enabled, but when I create a chain, I can only see MPLS decapsulation flows - I don't seen any MPLS encapsulation flows17:14
igordcardso traffic never gets steered17:14
mohankumarPrithiv ,+117:14
vikramcathy_: When we can start the review?17:14
igordcardLouisF, neutron code17:15
cathy_I understand that once we have the first patches of code in, the painful dependency issues are gone. So we are working hard everyday on the testing and bug fixes17:15
vikramcathy_: Is the patches ready for review?17:15
igordcardLouisF, recent neutron commits have made the error create_agent_config_map appear17:15
cathy_yes, they have been open for review for over one month.17:15
LouisFigordcard: so you are using master not stable/liberty?17:15
igordcardLouisF, yes, master17:15
pcarverDo we have a prioritized list of changes for merging?17:16
igordcardLouisF, will stick to stable/liberty then, no reason for master in this scenario17:16
cathy_vikram: I understand you have been on leave for several weeks.17:16
*** prometheanfire has left #openstack-meeting-417:16
LouisFigordcard: yes using master we will be affected by neutron commits17:16
pcarverI mean, if we were to merge changes one at a time, do we know what order we would like to tackle them?17:16
cathy_pcarver: yes, we have the dependency order17:16
vikramcathy_: plz let the team know when the patches are ready for review..17:17
vikramcathy_: we can help ;)17:17
igordcardpersonally I was going to review everything at once after I had successfully deployed a chain, but so far haven't been able17:17
cathy_pcarver: I think we will merge the patches that run on the Neutron server, then the patches running on the Compute node, then the patches of Horizon, CLI, Heat. make sense to you?17:17
igordcardcathy_, about Horizon, where are the patches?17:18
Prithivthe horizon patches by mohan seems to work when i tried17:18
vikramigordcard: it's there.. mohankumar can share17:18
cathy_mohankumar: could you post the link of the horizon patch to igordcard ?17:18
igordcardvikram, cathy_ thank you17:18
Prithivi have it igor17:18
igordcardPrithiv, I want to see it upstream or up for review17:18
pcarvercathy_: I think so. I just don't know if I've got the right list. My thought based on igordcard's install instructions would be to focus on 238428 and 23375817:18
*** matrohon has quit IRC17:19
vikramhttps://review.openstack.org/#/c/231868/17:19
pcarverbecause those are the two changes that his instructions pull in in order to get a working install17:19
vikramigordcad: https://review.openstack.org/#/c/231868/17:19
pcarverI don't want to give +1 or +2 to anything that I haven't pulled in locally to a working installation17:19
igordcardvikram, oh.. so horizon is the only one where support can go to the upstream project (Horizon)?17:20
cathy_pcarver: so you mean that the devstack patch that mohan posted does not work?17:20
mohankumarigordcard , https://review.openstack.org/#/c/231868/17:20
igordcardpcarver, same thought here17:20
vikramigordcard: mohankumar can update on this17:20
pcarvercathy_: I haven't checked it. I've been focussing on igordcard's instructions and getting them to work.17:21
igordcardvikram, mohankumar okay thanks, we can talk offline17:21
mohankumarigordcard , will ping you once meeting finished17:21
igordcardcathy_, I believe mohan's patch would work if the code was already merged17:22
cathy_pcarver: I would like us to have one destack patch that works and that everyone can use  to install the functionality.17:22
igordcardcathy_, I have left some comments on mohankumar devstack patch17:22
cathy_igordcard: OK, thanks for the info17:22
pcarvercathy_: agreed. I don't want redundant effort17:22
vikrampcarver: can you mention about the issue you are facing for the devstack patch17:22
cathy_pcarver: so let's use mohan's devstack patch to install it and post comments if something does not work or any modification suggestion. This will benefit other people having the same issue.17:23
*** njohnsto_ has joined #openstack-meeting-417:23
pcarvervikram: I've been following instructions that igordcard sent in email and got to the point that the services are running and the database tables are present.17:24
mohankumarcathy_ :  devstack changes will work , once all the code gets into sfc repo17:24
igordcardcathy_, not really possible until the code is merged - it's a chicken and egg problem - what we need now is cumbersome, but working, instructions, so we can test and try, then review and merge - and then a single devstack plugin enabling will be enough17:24
pcarvervikram: but I can't create VMs due to some other problem that may or may not be sfc related. I haven't dug into it yet, but it prevented me from setting up a service chain if I can't create a VM.17:24
mohankumartill then some manual efforts needs based on patch updates we having17:25
cathy_mohankumar: thanks. SO I guess the key issue is that we need to get all the codes merged into the repo, then the installation process pain will be gone.17:25
igordcardcathy_, oh yeah17:25
vikramcathy_:+++100017:25
igordcardpcarver, we can talk here on IRC afterwards to bring the VMs up as well17:26
*** Swami has quit IRC17:26
igordcardpcarver, but I can't help about the chaining itself, as I don't see the encapsulation flows on ovs-ofctl :(17:26
pcarverigordcard: Thanks, I'll try. Meetings are a persistent issue as well, today may be mostly a loss.17:27
*** njohnston has quit IRC17:27
igordcardwhich is why I was asking about the flow classifier readiness, even more because it is marked as WIP right now17:27
*** ujuc has joined #openstack-meeting-417:27
cathy_igordcard: vikram OK, I will approve the merge once all the end-to-end functionality test cases are all passed. Maybe another week or shorter since now we have got several testbeds up and the SFC installed and have progressed on the testing well.17:27
cathy_pcarver: we have got VM created and chained in on several of our testbeds.17:28
vikramcathy_: plz notify the team when to start the review before the merge17:28
cathy_pcarver: besides getting a VM installed, you also need to either have a SF running on the VM or do some config to fake the traffic hair-pin through the VM.17:29
igordcardvikram, +117:29
*** jlk has joined #openstack-meeting-417:29
cathy_vikram: you can start the review now. As I said before, all the patches have been open for review for over one month and we have incorporated most if not all comments17:30
vikramcathy_: thanks17:30
igordcardcathy_, what do you mean by that having a SF running on the VM?17:30
pcarvercathy_: yep, understood. My latest issue is just not being able to boot a VM and a bunch of errors on the q-agt screen. I haven't had time between meetings to get to the bottom of it.17:30
cathy_pcarver: that seems like a non-SFC issue.17:31
Prithivcathy: same question as igor17:31
pcarverigordcard, cathy_: I'm assuming something as simple as a Linux VM with IP forwarding enabled will suffice as an SF to demonstrate that the chaining works.17:32
Prithivpcarver: +117:32
Prithivfrom the demo vi, it sounded like that17:32
Prithivdemo vid17:32
igordcardpcarver, understood17:32
cathy_igordcard: Prithiv yes, pcarver stated what I meant:-)17:32
igordcardso, if I set up tcpdump in my VM I should see packets coming in right? even if I don't enable anything17:32
LouisFpcarver: correct17:32
pcarvercathy_: maybe, maybe not. One of the files in the traceback is /opt/stack/networking-sfc/networking_sfc/services/sfc/agent/agent.py but it's not the top of bottom of the traceback, so I'm not sure if it's the cause.17:33
pcarverbut we don't need to discuss that as part of this meeting17:33
cathy_igordcard: yes if you enable some "Ip forwarding" so that the traffic going into the VM will be fowarded out of the VM and can go to next SF VM per the API specification17:33
*** javeriak_ has joined #openstack-meeting-417:34
*** pabelanger has left #openstack-meeting-417:34
cathy_pcarver: let's discuss that offline after you did a little bit more investigation on the VM creation issue17:34
pcarvercathy_: agreed17:35
igordcardcathy_, this was my scenario: client VM - SF1 VM - Internet ; traffic was sent from the client VM, but was never captured in SF1 VM (in its ingress interface)17:35
igordcardI will share the flow list, at least for reference: http://paste.openstack.org/show/cIjekDRVyMxkyOQCZdYc/17:35
cathy_what chain API did you specify?17:35
igordcardI see pop_mpls flows, but I don't see any push_mpls flows17:36
cathy_did you set up the SF1 VM to do the "hairpin"?17:36
*** javeriak has quit IRC17:36
igordcardcathy_, so, SF1 was a port-pair-group with a single port-pair inside17:36
igordcardcathy_, and I matched all udp traffic going to 8.8.8.8, so I did a UDP iperf to 8.8.8.8 at my client VM and expected traffic to reach SF1, but it didn't17:37
*** dzamboni has quit IRC17:37
igordcardcathy_, no, it should at least receive traffic right? being capable of forwarding it would be my second test17:37
cathy_igordcard: maybe we can discuss and debug this offline? Shoot us an email? OK with you?17:38
igordcardcathy_, sure!17:38
vikramigordcard, cathy_: I feel a detailed documentation about installation and testing would be useful17:38
igordcardvikram, +1 I can post my current cumbersome instructions to the wiki if you want17:38
vikramigordcard: Great..17:39
vikramigordcard: We can update the devrefs as well17:39
*** SimonChung has joined #openstack-meeting-417:39
LouisFigordcard: please do that17:39
igordcardthanks to pcarver for all the feedback17:39
vikramigordcard: IMO, updating existing devref doc for this would be useful17:39
vikramigordcard: or we can add a separate one illustrating test/installation nits17:41
igordcardvikram, maybe, but the instructions I have are only relevant before merge...17:41
*** salv-orlando has joined #openstack-meeting-417:41
pcarvervikram: I think we need to update the installation devref, but I'm not sure we want to do that with the intermediate procedure that will go away once changes merge17:41
cathy_igordcard: thanks. could you post it on the SFC wik link and we will add ours?17:41
mohankumarpcarver: IMO  After merge will be good17:41
vikrampcarver, cathy_: i am okay with wiki as well17:42
igordcardafter merge it should literally be: git clone devstack; append networking-sfc plugin line to local.conf17:42
cathy_let me find the link and post it here17:42
LouisFigordcard: +10017:42
igordcardcathy_, yeah17:42
*** irenab_ has joined #openstack-meeting-417:42
vikramigordcard: I was mostly interested on the test process17:42
cathy_https://wiki.openstack.org/wiki/Neutron/ServiceInsertionAndChaining17:42
cathy_vikram: we will post the testing process17:43
vikramigordcard: For diff scenarios's, may be single / multiple node deployment17:43
vikramcathy_: Great!17:43
igordcardvikram, yes, I too am interested, very much, on the test process, as so far I haven't been able to have the right OF flows17:43
*** irenab has quit IRC17:43
*** irenab_ is now known as irenab17:43
cathy_igordcard: we will post the testing process17:43
igordcardcathy_, LouisF, thank you17:44
vikramigordcard: don't worry till cathy_ is there :-)17:44
cathy_now I would like to discuss the Neutron branch the SFC codes base on.17:44
*** prashantD has joined #openstack-meeting-417:45
*** salv-orlando has quit IRC17:45
*** Swami has joined #openstack-meeting-417:46
cathy_currently our codes are based on the master branch and we found that the functionality gets broken due to new changes on the master branch. This is slowed down our testing work. So we think we will rebase our code to a stable master branch label. Neutron M-1 cut is end of this week. So if there is a label for that cut, we will rebase our codes to that M-1 label17:47
mohankumarcathy_ : sounds good !17:48
cathy_does anyone know whether there is such a M-1 label?17:49
johnsomhttps://github.com/openstack/neutron/releases17:49
*** qwebirc26088 has quit IRC17:49
cathy_I have sent email to Kyle on that and hopefully there is such a label17:49
johnsom8.0.0.0b1 is M1 I think17:49
cathy_johnsom: great. Thanks for the info!17:50
Prithivyes17:50
Prithivhttps://launchpad.net/neutron/+milestone/mitaka-117:50
cathy_cool17:50
*** SumitNaiksatam has joined #openstack-meeting-417:51
cathy_Prithiv: thanks!17:51
mohankumarcathy_ : so we not incorporate any  master changes after M-1 ?17:51
cathy_no, we will incorporate master changes later17:52
mohankumarcathy_ : okay17:53
cathy_after we get the testing completed without much interference and then get our first patches merged to remove the dependency pain and the installation pain17:53
igordcardcathy_, so, will the code be merged after or before M1 rebase?17:53
cathy_after M1 rebase17:54
*** yamahata has quit IRC17:54
cathy_After rebase we will continue our testing and if all test cases passed, I will approve the merge and then we can start the bug filing process for any more issues we found, then we will rebase to incorporate changes on master and get ready for release. make sense to everyone?17:55
*** ivar-lazzaro has joined #openstack-meeting-417:56
*** yamahata has joined #openstack-meeting-417:56
mohankumarcathy_ +117:56
*** ivar-lazzaro has quit IRC17:56
pcarvercathy_ +117:57
*** banix has joined #openstack-meeting-417:57
igordcardcathy_, yes17:57
*** KLev-away is now known as KLevenstein17:57
LouisFcathy_: +117:57
*** jmckind has quit IRC17:57
*** ivar-lazzaro has joined #openstack-meeting-417:58
vikramcathy_:+117:59
cathy_Ok, time is up. Let's work hard together on the testing and "bug fixes"(we will not officially file bugs, but will keep a copy of the problems found and fix them), and get the codes ready. Also post comments if you have more.17:59
LouisFbye17:59
s3wongbye18:00
cathy_bye now.18:00
vikrambye18:00
igordcardbye18:00
*** vikram has quit IRC18:00
*** johnsom has left #openstack-meeting-418:00
cathy_#endmeeting18:00
*** s3wong has quit IRC18:00
*** openstack changes topic to "Q&A (Meeting topic: openstack-vahana)"18:00
openstackMeeting ended Thu Dec  3 18:00:21 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-12-03-17.00.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-12-03-17.00.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-12-03-17.00.log.html18:00
*** cathy_ has quit IRC18:01
*** javeriak has joined #openstack-meeting-418:03
*** u_kozat has quit IRC18:04
*** javeriak_ has quit IRC18:06
*** Piet has joined #openstack-meeting-418:06
*** gjayavelu has quit IRC18:07
*** u_kozat has joined #openstack-meeting-418:08
*** ramanjaneya_ has joined #openstack-meeting-418:08
*** njohnsto_ has left #openstack-meeting-418:12
*** erikwilson has quit IRC18:15
*** s3wong has joined #openstack-meeting-418:23
*** mbound_ has quit IRC18:27
*** mbound_ has joined #openstack-meeting-418:27
*** AlanClark has joined #openstack-meeting-418:30
*** javeriak_ has joined #openstack-meeting-418:39
*** javeriak has quit IRC18:40
*** javeriak has joined #openstack-meeting-418:41
*** javeriak_ has quit IRC18:44
*** javeriak has quit IRC18:55
*** jmckind has joined #openstack-meeting-418:58
*** gjayavelu has joined #openstack-meeting-418:58
*** mohankumar has quit IRC19:00
*** mohankumar has joined #openstack-meeting-419:08
*** ajmiller has joined #openstack-meeting-419:09
*** mestery has joined #openstack-meeting-419:11
*** bnemec has quit IRC19:16
*** mohankumar has quit IRC19:19
*** bnemec has joined #openstack-meeting-419:22
*** mbound_ has quit IRC19:24
*** mbound_ has joined #openstack-meeting-419:26
*** mbound_ has quit IRC19:30
*** numans has joined #openstack-meeting-419:31
*** Sukhdev has joined #openstack-meeting-419:31
*** prashantD has quit IRC19:33
*** dandruta has quit IRC19:34
*** prashantD has joined #openstack-meeting-419:35
*** dtardivel has quit IRC19:37
*** numans has quit IRC19:42
*** ivar-lazzaro has quit IRC19:47
*** ivar-lazzaro has joined #openstack-meeting-419:47
*** Prithiv has quit IRC19:49
*** krtaylor has quit IRC20:03
*** sdake has joined #openstack-meeting-420:04
*** ramanjaneya_ has quit IRC20:14
*** krtaylor has joined #openstack-meeting-420:15
*** salv-orlando has joined #openstack-meeting-420:16
*** SimonChung has quit IRC20:18
*** sambetts is now known as sambetts-afk20:19
*** salv-orlando has quit IRC20:22
*** salv-orlando has joined #openstack-meeting-420:22
*** u_kozat has quit IRC20:23
*** sridhar_ram has quit IRC20:29
*** avarner has quit IRC20:32
*** igordcard has quit IRC20:32
*** Piet has quit IRC20:35
*** fawadkhaliq has quit IRC20:41
*** fawadkhaliq has joined #openstack-meeting-420:42
*** fawadkhaliq has quit IRC20:44
*** vishwanathj has joined #openstack-meeting-420:53
*** yamahata has quit IRC20:55
*** banix has quit IRC20:55
*** iyamahat has quit IRC20:55
*** mancdaz has quit IRC20:58
*** mancdaz has joined #openstack-meeting-421:01
*** sridhar_ram has joined #openstack-meeting-421:04
*** delatte has quit IRC21:07
*** SumitNaiksatam has quit IRC21:10
*** SumitNaiksatam has joined #openstack-meeting-421:10
*** gomarivera has quit IRC21:12
*** SumitNaiksatam has quit IRC21:15
*** SimonChung has joined #openstack-meeting-421:15
*** yamahata has joined #openstack-meeting-421:17
*** Piet has joined #openstack-meeting-421:19
*** iyamahat has joined #openstack-meeting-421:19
*** julim has quit IRC21:24
*** u_kozat has joined #openstack-meeting-421:24
*** darrenc has joined #openstack-meeting-421:25
*** njohnston has joined #openstack-meeting-421:26
*** banix has joined #openstack-meeting-421:27
*** u_kozat has quit IRC21:28
*** cdelatte has joined #openstack-meeting-421:38
*** Sukhdev has quit IRC21:39
*** Sukhdev has joined #openstack-meeting-421:39
*** Piet has quit IRC21:59
*** jmckind has quit IRC22:00
*** jmckind has joined #openstack-meeting-422:03
*** sridhar_ram has quit IRC22:04
*** SimonChung has quit IRC22:04
*** SimonChung1 has joined #openstack-meeting-422:04
*** sridhar_ram has joined #openstack-meeting-422:06
*** sdake has quit IRC22:10
*** njohnsto_ has joined #openstack-meeting-422:18
*** vishwanathj has quit IRC22:18
*** sdake has joined #openstack-meeting-422:20
*** njohnston has quit IRC22:21
*** AlanClark has quit IRC22:30
*** jacalcat_ has joined #openstack-meeting-422:37
*** stanli has joined #openstack-meeting-422:42
*** jacalcat_ has quit IRC22:46
*** jacalcat_ has joined #openstack-meeting-422:47
*** jacalcat_ has quit IRC22:48
*** jacalcat has joined #openstack-meeting-422:50
*** sdake has quit IRC22:52
*** vishwanathj has joined #openstack-meeting-422:57
*** jacalcat has left #openstack-meeting-423:02
*** u_kozat has joined #openstack-meeting-423:03
*** klamath has quit IRC23:04
*** stanli has quit IRC23:06
*** prashantD has quit IRC23:08
*** jmckind has quit IRC23:09
*** KLevenstein has quit IRC23:12
*** bobh_ has quit IRC23:21
*** banix has quit IRC23:25
*** gjayavelu has quit IRC23:30
*** bnemec has quit IRC23:33
*** bnemec has joined #openstack-meeting-423:33
*** gjayavelu has joined #openstack-meeting-423:37
*** rbak has quit IRC23:47
*** jckasper has quit IRC23:48
*** Sukhdev has quit IRC23:52
*** yamamoto has joined #openstack-meeting-423:54
*** sigmavirus24 is now known as sigmavirus24_awa23:57
*** amotoki has quit IRC23:58
*** salv-orlando has quit IRC23:58

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