Wednesday, 2015-04-08

*** ivar-lazzaro has quit IRC00:00
*** ivar-lazzaro has joined #openstack-meeting-300:01
*** ivar-laz_ has joined #openstack-meeting-300:05
*** ivar-lazzaro has quit IRC00:05
*** baoli has joined #openstack-meeting-300:07
*** salv-orlando has quit IRC00:10
*** nelsnelson has joined #openstack-meeting-300:13
*** bpokorny has quit IRC00:14
*** sreshetn2 has joined #openstack-meeting-300:17
*** sreshetn2 has quit IRC00:21
*** wojdev has joined #openstack-meeting-300:25
*** jaypipes has quit IRC00:27
*** wojdev has quit IRC00:37
*** nelsnelson has quit IRC00:39
*** iben has quit IRC00:40
*** emagana has quit IRC00:46
*** Longgeek has joined #openstack-meeting-300:50
*** pavel_bondar has quit IRC00:51
*** pavel_bondar has joined #openstack-meeting-300:52
*** stevemar has joined #openstack-meeting-300:57
*** Sukhdev has quit IRC00:58
*** megm has joined #openstack-meeting-301:01
*** stendulker has joined #openstack-meeting-301:01
*** clu_ has quit IRC01:02
*** megm_ has quit IRC01:02
*** shwetaap has quit IRC01:04
*** alexsyip has quit IRC01:05
*** Longgeek has quit IRC01:07
*** Longgeek has joined #openstack-meeting-301:08
*** banix has joined #openstack-meeting-301:13
*** shwetaap has joined #openstack-meeting-301:23
*** banix has quit IRC01:23
*** yamamoto has joined #openstack-meeting-301:24
*** shwetaap1 has joined #openstack-meeting-301:24
*** ivar-laz_ has quit IRC01:25
*** shwetaap has quit IRC01:28
*** nelsnelson has joined #openstack-meeting-301:32
*** s3wong has quit IRC01:33
*** stanzgy has joined #openstack-meeting-301:34
*** haleyb_ has joined #openstack-meeting-301:37
*** melwitt has quit IRC01:40
*** baoli has quit IRC01:52
*** baoli has joined #openstack-meeting-301:52
*** jckasper has joined #openstack-meeting-301:57
*** salv-orlando has joined #openstack-meeting-301:59
*** cyeoh has quit IRC02:00
*** sankarshan_away has quit IRC02:00
*** haleyb_ has quit IRC02:01
*** lbragstad has quit IRC02:01
*** adam_g has quit IRC02:02
*** jroll has quit IRC02:02
*** salv-orlando has quit IRC02:04
*** sankarshan_away has joined #openstack-meeting-302:06
*** eghobo has quit IRC02:06
*** sreshetn2 has joined #openstack-meeting-302:06
*** jroll has joined #openstack-meeting-302:07
*** adam_g has joined #openstack-meeting-302:07
*** adam_g has quit IRC02:07
*** adam_g has joined #openstack-meeting-302:07
*** jroll has quit IRC02:08
*** jroll has joined #openstack-meeting-302:08
*** sreshetn2 has quit IRC02:10
*** lbragstad has joined #openstack-meeting-302:11
*** cyeoh has joined #openstack-meeting-302:11
*** stendulker has quit IRC02:11
*** julim has quit IRC02:12
*** yamahata has quit IRC02:16
*** jckasper has quit IRC02:17
*** etoews has joined #openstack-meeting-302:19
*** baoli has quit IRC02:24
*** baoli has joined #openstack-meeting-302:28
*** banix has joined #openstack-meeting-302:29
*** jckasper has joined #openstack-meeting-302:38
*** bpokorny has joined #openstack-meeting-302:44
*** banix has quit IRC02:45
*** gulic has joined #openstack-meeting-302:47
*** MarkAtwood has joined #openstack-meeting-302:48
*** jckasper has quit IRC02:48
*** MarkAtwood has quit IRC02:48
*** jckasper has joined #openstack-meeting-302:49
*** baoli has quit IRC02:56
*** nelsnelson has quit IRC02:57
*** jckasper has quit IRC02:58
*** pballand has quit IRC03:07
*** julim has joined #openstack-meeting-303:08
*** eghobo has joined #openstack-meeting-303:14
*** eghobo has quit IRC03:14
*** salv-orlando has joined #openstack-meeting-303:28
*** stendulker has joined #openstack-meeting-303:37
*** tqtran_ has quit IRC03:41
*** shwetaap1 has quit IRC03:44
*** pballand has joined #openstack-meeting-303:47
*** coolsvap|afk is now known as coolsvap03:48
*** pballand has quit IRC03:48
*** sreshetn2 has joined #openstack-meeting-303:55
*** alexsyip has joined #openstack-meeting-303:56
*** shwetaap has joined #openstack-meeting-303:58
*** sreshetn2 has quit IRC03:59
*** bpokorny has quit IRC04:00
*** salv-orlando has quit IRC04:08
*** sarob has joined #openstack-meeting-304:11
*** sarob has quit IRC04:15
*** Sayaji has quit IRC04:19
*** seizadi has joined #openstack-meeting-304:22
*** shwetaap has quit IRC04:24
*** shwetaap has joined #openstack-meeting-304:25
*** mrmartin has joined #openstack-meeting-304:28
*** coolsvap is now known as coolsvap|afk04:41
*** coolsvap|afk is now known as coolsvap04:53
*** mrmartin has quit IRC04:53
*** megm_ has joined #openstack-meeting-305:04
*** megm has quit IRC05:05
*** sreshetn2 has joined #openstack-meeting-305:10
*** salv-orlando has joined #openstack-meeting-305:11
*** sarob has joined #openstack-meeting-305:12
*** sreshetn2 has quit IRC05:15
*** julim has quit IRC05:15
*** sarob has quit IRC05:16
*** terrylhowe has quit IRC05:24
*** armax has quit IRC05:26
*** rushiagr_away is now known as rushiagr05:33
*** Poornima has joined #openstack-meeting-305:35
*** etoews has quit IRC05:39
*** wojdev has joined #openstack-meeting-305:47
*** wojdev has quit IRC05:48
*** salv-orlando has quit IRC05:49
*** emagana has joined #openstack-meeting-305:50
*** bradjones has quit IRC05:52
*** stevemar has quit IRC05:54
*** seizadi has quit IRC05:55
*** bradjones has joined #openstack-meeting-305:57
*** bradjones has quit IRC05:57
*** bradjones has joined #openstack-meeting-305:57
*** mrunge has joined #openstack-meeting-306:10
*** emagana has quit IRC06:42
*** sahid has joined #openstack-meeting-306:42
*** emagana has joined #openstack-meeting-306:42
*** jtomasek has joined #openstack-meeting-306:44
*** jcoufal has joined #openstack-meeting-306:47
*** emagana has quit IRC06:47
*** sreshetn2 has joined #openstack-meeting-306:56
*** banix has joined #openstack-meeting-307:01
*** sarob has joined #openstack-meeting-307:01
*** mrmartin has joined #openstack-meeting-307:03
*** zz_ttrifonov is now known as ttrifonov07:04
*** shwetaap has quit IRC07:10
*** alexsyip has quit IRC07:11
*** salv-orlando has joined #openstack-meeting-307:14
*** matrohon has joined #openstack-meeting-307:23
*** sergef has joined #openstack-meeting-307:31
*** sreshetn2 has quit IRC07:32
*** sankarshan_away is now known as sankarshan_07:37
*** mrda is now known as mrda-away07:41
*** e0ne has joined #openstack-meeting-307:41
*** e0ne has quit IRC07:48
*** amotoki has joined #openstack-meeting-307:50
*** salv-orl_ has joined #openstack-meeting-307:50
*** safchain has joined #openstack-meeting-307:51
*** sarob has quit IRC07:52
*** e0ne has joined #openstack-meeting-307:52
*** salv-orlando has quit IRC07:55
*** sreshetn2 has joined #openstack-meeting-307:56
*** e0ne is now known as e0ne_07:57
*** e0ne_ is now known as e0ne08:00
*** JeanBriceCombebi has joined #openstack-meeting-308:03
*** banix has quit IRC08:06
*** rushiagr has left #openstack-meeting-308:07
*** e0ne has quit IRC08:10
*** e0ne has joined #openstack-meeting-308:11
*** e0ne has quit IRC08:13
*** bradjones has quit IRC08:14
*** e0ne has joined #openstack-meeting-308:17
*** ivar-lazzaro has joined #openstack-meeting-308:20
*** bradjones has joined #openstack-meeting-308:20
*** bradjones has quit IRC08:21
*** bradjones has joined #openstack-meeting-308:21
*** e0ne has quit IRC08:21
*** mikal has quit IRC08:22
*** mikal has joined #openstack-meeting-308:23
*** e0ne has joined #openstack-meeting-308:24
*** MaxV has joined #openstack-meeting-308:29
*** e0ne has quit IRC08:31
*** ivar-lazzaro has quit IRC08:34
*** salv-orl_ has quit IRC08:47
*** JeanBriceCombebi has quit IRC08:54
*** JeanBriceCombebi has joined #openstack-meeting-308:55
*** vineetmenon has joined #openstack-meeting-309:00
*** megm has joined #openstack-meeting-309:06
*** megm_ has quit IRC09:06
*** goalotc has quit IRC09:15
*** goalotc has joined #openstack-meeting-309:16
*** e0ne has joined #openstack-meeting-309:16
*** JeanBriceCombebi has quit IRC09:23
*** nelsnelson has joined #openstack-meeting-309:28
*** JeanBriceCombebi has joined #openstack-meeting-309:36
*** e0ne is now known as e0ne_09:41
*** e0ne_ is now known as e0ne09:49
*** JeanBriceCombebi has quit IRC09:50
*** stendulker has quit IRC09:52
*** zz_johnthetubagu is now known as johnthetubaguy09:52
*** JeanBriceCombebi has joined #openstack-meeting-309:54
*** yamamoto has quit IRC09:58
*** iben has joined #openstack-meeting-309:59
*** jlvillal has quit IRC10:04
*** jlvillal has joined #openstack-meeting-310:05
*** ericksonfgds has quit IRC10:05
*** salv-orlando has joined #openstack-meeting-310:08
*** sankarshan_ is now known as sankarshan_away10:17
*** terrylhowe has joined #openstack-meeting-310:31
*** terrylhowe has left #openstack-meeting-310:31
*** sreshetn2 has quit IRC10:32
*** sergef has quit IRC10:33
*** stanzgy has quit IRC10:52
*** yamamoto has joined #openstack-meeting-310:53
*** JeanBriceCombebi has quit IRC11:03
*** mwagner_lap has quit IRC11:05
*** yamamoto has quit IRC11:14
*** sergef has joined #openstack-meeting-311:15
*** coolsvap is now known as coolsvap|afk11:15
*** sarob has joined #openstack-meeting-311:26
*** sarob has quit IRC11:30
*** sergef_ has joined #openstack-meeting-311:33
*** sergef has quit IRC11:33
*** sergef_ is now known as sergef11:33
*** sergef has quit IRC11:34
*** sergef_ has joined #openstack-meeting-311:35
*** sreshetn2 has joined #openstack-meeting-311:36
*** sergef_ has quit IRC11:36
*** iben has quit IRC11:36
*** sergef has joined #openstack-meeting-311:36
*** sergef has quit IRC11:39
*** sergef has joined #openstack-meeting-311:40
*** sergef has quit IRC11:41
*** sergef_ has joined #openstack-meeting-311:41
*** pbrooko has joined #openstack-meeting-311:42
*** sergef_ has quit IRC11:49
*** sergef has joined #openstack-meeting-311:50
*** yamamoto has joined #openstack-meeting-312:02
*** egallen has joined #openstack-meeting-312:02
*** sreshetn2 has quit IRC12:04
*** sankarshan_away is now known as sankarshan_12:05
*** e0ne is now known as e0ne_12:05
*** sankarshan_ is now known as sankarshan_away12:08
*** sankarshan_away is now known as sankarshan_12:08
*** VW_ has joined #openstack-meeting-312:12
*** e0ne_ has quit IRC12:15
*** bknudson1 has quit IRC12:16
*** baoli has joined #openstack-meeting-312:17
*** e0ne has joined #openstack-meeting-312:17
*** pbrooko has quit IRC12:18
*** VW_ has quit IRC12:20
*** baoli has quit IRC12:22
*** MaxV has quit IRC12:25
*** baoli has joined #openstack-meeting-312:25
*** MaxV has joined #openstack-meeting-312:27
*** pbrooko has joined #openstack-meeting-312:29
*** JeanBriceCombebi has joined #openstack-meeting-312:30
*** baoli_ has joined #openstack-meeting-312:30
*** baoli has quit IRC12:33
*** JeanBriceCombebi has quit IRC12:35
*** JeanBriceCombebi has joined #openstack-meeting-312:37
*** yamamoto has quit IRC12:37
*** sarob has joined #openstack-meeting-312:41
*** Poornima has quit IRC12:41
*** vineetmenon has quit IRC12:43
*** shwetaap has joined #openstack-meeting-312:44
*** sarob has quit IRC12:46
*** mattfarina has joined #openstack-meeting-312:52
*** Poornima has joined #openstack-meeting-312:54
*** mwagner_lap has joined #openstack-meeting-312:55
*** JeanBriceCombebi has quit IRC12:57
*** JeanBriceCombebi has joined #openstack-meeting-312:57
*** bknudson has joined #openstack-meeting-313:00
*** pbrooko has quit IRC13:01
*** jckasper has joined #openstack-meeting-313:06
*** pbrooko has joined #openstack-meeting-313:06
*** sankarshan_ is now known as sankarshan_away13:07
*** megm_ has joined #openstack-meeting-313:08
*** megm has quit IRC13:08
*** julim has joined #openstack-meeting-313:11
*** sankarshan_away is now known as sankarshan_13:11
*** sreshetn2 has joined #openstack-meeting-313:14
*** yamahata has joined #openstack-meeting-313:18
*** e0ne is now known as e0ne_13:19
*** stevemar has joined #openstack-meeting-313:19
*** mattfarina has quit IRC13:22
*** Longgeek has quit IRC13:23
*** ivar-lazzaro has joined #openstack-meeting-313:24
*** stevemar has quit IRC13:27
*** ivar-laz_ has joined #openstack-meeting-313:28
*** stevemar has joined #openstack-meeting-313:28
*** e0ne_ has quit IRC13:28
*** ivar-lazzaro has quit IRC13:29
*** ivar-laz_ has quit IRC13:30
*** ivar-lazzaro has joined #openstack-meeting-313:30
*** thomasem has joined #openstack-meeting-313:34
*** thomasem has quit IRC13:36
*** haleyb_ has joined #openstack-meeting-313:40
*** thomasem has joined #openstack-meeting-313:41
*** sergef_ has joined #openstack-meeting-313:44
*** sergef has quit IRC13:44
*** sergef_ is now known as sergef13:44
*** e0ne has joined #openstack-meeting-313:46
*** lblanchard has joined #openstack-meeting-313:46
*** jaypipes has joined #openstack-meeting-313:48
*** mrmartin has quit IRC13:52
*** jcoufal has quit IRC13:53
*** yamahata has quit IRC13:55
*** ChanServ changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:55
*** yamahata has joined #openstack-meeting-313:55
*** nelsnelson has quit IRC13:56
*** VW_ has joined #openstack-meeting-314:03
*** MarkAtwood has joined #openstack-meeting-314:03
*** killer_prince has joined #openstack-meeting-314:05
*** killer_prince is now known as lazy_prince14:05
*** VW_ has quit IRC14:08
*** ivar-lazzaro has quit IRC14:08
*** VW_ has joined #openstack-meeting-314:08
*** haleyb_ has quit IRC14:09
*** sigmavirus24_awa is now known as sigmavirus2414:11
*** salv-orlando has quit IRC14:12
*** zz_jgrimm is now known as jgrimm14:13
*** sankarshan_ is now known as sankarshan_away14:20
*** pbrooko has quit IRC14:22
*** Sukhdev has joined #openstack-meeting-314:24
*** yamamoto has joined #openstack-meeting-314:26
*** ivar-lazzaro has joined #openstack-meeting-314:27
*** sarob has joined #openstack-meeting-314:27
*** yamamoto has quit IRC14:31
*** sarob has quit IRC14:32
*** stevemar has quit IRC14:34
*** sergef has quit IRC14:40
*** mattfarina has joined #openstack-meeting-314:42
*** emagana has joined #openstack-meeting-314:46
*** carl_baldwin has joined #openstack-meeting-314:48
*** emagana_ has joined #openstack-meeting-314:49
*** emagana has quit IRC14:50
*** btully has joined #openstack-meeting-314:51
*** VW__ has joined #openstack-meeting-315:02
*** VW__ has quit IRC15:02
*** VW__ has joined #openstack-meeting-315:03
*** jaypipes has quit IRC15:03
*** VW_ has quit IRC15:05
*** JeanBriceCombebi has quit IRC15:05
*** jaypipes has joined #openstack-meeting-315:05
*** emagana_ has quit IRC15:05
*** emagana has joined #openstack-meeting-315:06
*** jaypipes has quit IRC15:06
*** e0ne is now known as e0ne_15:10
*** jcoufal has joined #openstack-meeting-315:11
*** salv-orlando has joined #openstack-meeting-315:12
*** JeanBriceCombebi has joined #openstack-meeting-315:13
*** stevemar has joined #openstack-meeting-315:13
*** bpokorny has joined #openstack-meeting-315:15
*** wojdev has joined #openstack-meeting-315:15
*** wojdev has quit IRC15:15
*** e0ne_ has quit IRC15:16
*** egallen has quit IRC15:21
*** mrunge is now known as mrunge_away15:22
*** Piet has joined #openstack-meeting-315:23
*** lazy_prince has quit IRC15:24
*** banix has joined #openstack-meeting-315:24
*** armax has joined #openstack-meeting-315:25
*** killer_prince has joined #openstack-meeting-315:29
*** e0ne has joined #openstack-meeting-315:29
*** killer_prince is now known as lazy_prince15:29
*** stendulker has joined #openstack-meeting-315:30
*** shwetaap has quit IRC15:33
*** ttrifonov is now known as zz_ttrifonov15:33
*** stendulker_ has joined #openstack-meeting-315:35
*** matrohon has quit IRC15:35
*** lazy_prince has quit IRC15:36
*** stendulker has quit IRC15:38
*** stendulker has joined #openstack-meeting-315:39
*** stendulker_ has quit IRC15:41
*** sarob has joined #openstack-meeting-315:43
*** nlahouti has joined #openstack-meeting-315:43
*** stendulker_ has joined #openstack-meeting-315:44
*** stendulker has quit IRC15:47
*** nlahouti has left #openstack-meeting-315:49
*** sarob has quit IRC15:51
*** shwetaap has joined #openstack-meeting-315:52
*** killer_prince has joined #openstack-meeting-315:55
*** killer_prince is now known as lazy_prince15:55
*** sarob has joined #openstack-meeting-315:57
*** yamahata has quit IRC15:58
*** yamahata has joined #openstack-meeting-315:58
*** marun has joined #openstack-meeting-315:59
*** igordcard has quit IRC16:00
*** igordcard has joined #openstack-meeting-316:01
*** absubram has joined #openstack-meeting-316:02
*** MaxV has quit IRC16:03
*** alexsyip has joined #openstack-meeting-316:10
*** absubram has left #openstack-meeting-316:10
*** julim has quit IRC16:14
*** Sukhdev has quit IRC16:24
*** Sukhdev has joined #openstack-meeting-316:25
*** Longgeek has joined #openstack-meeting-316:25
*** stendulker has joined #openstack-meeting-316:28
*** tqtran has joined #openstack-meeting-316:30
*** Longgeek has quit IRC16:30
*** stendulker_ has quit IRC16:30
*** gulic has quit IRC16:34
*** JeanBriceCombebi has quit IRC16:35
*** stendulker has quit IRC16:37
*** mwang2 has joined #openstack-meeting-316:43
*** clu_ has joined #openstack-meeting-316:47
*** sergef has joined #openstack-meeting-316:49
*** melwitt has joined #openstack-meeting-316:51
*** vineetmenon has joined #openstack-meeting-316:52
*** julim has joined #openstack-meeting-316:54
*** dheeraj-gupta-4 has joined #openstack-meeting-316:59
*** sergef has quit IRC16:59
alaski#startmeeting nova_cells17:00
openstackMeeting started Wed Apr  8 17:00:32 2015 UTC and is due to finish in 60 minutes.  The chair is alaski. 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: nova_cells)"17:00
openstackThe meeting name has been set to 'nova_cells'17:00
*** rockyg has joined #openstack-meeting-317:00
alaskianyone here for the cells meeting?17:00
vineetmenono/17:00
melwitto/17:00
dheeraj-gupta-4o/17:01
*** jckasper has quit IRC17:01
alaskibauzas: ?17:01
bauzasoh17:01
bauzas\o17:01
*** jckasper has joined #openstack-meeting-317:01
alaski#topic Cellsv1 Tempest Testing17:01
bauzasalaski: thanks for pinging me17:01
*** openstack changes topic to "Cellsv1 Tempest Testing (Meeting topic: nova_cells)"17:01
bauzassoooo17:01
alaskiso cells is green right now17:01
dansmitho/17:02
alaskibut.. https://review.openstack.org/#/c/171414/17:02
*** rockyg has left #openstack-meeting-317:02
alaskionce that gets in we'll be failing hypervisor tests again17:02
bauzaswho can we hassle for +W'ing it ?17:02
bauzas:)17:02
alaskiand then there's https://review.openstack.org/#/c/171306 and https://review.openstack.org/#/c/160506/ for those17:02
alaskibauzas: I'm not sure, could probably ask in -infra about it17:03
bauzasdheeraj-gupta-4: you asked me a question this morning about why cells job is just having a few tests, see https://review.openstack.org/#/c/171414/ for hte explanation17:03
bauzasalaski: yeah, that's good that we have at least one +217:04
dheeraj-gupta-4bauzas: Yes got it.17:04
alaskiI'd like to see that change in before the service objects changes are merged17:04
alaskiso we can see a good test run on them17:04
bauzasalaski: agreed17:04
*** Poornima has quit IRC17:04
bauzasalaski: but that would require a recheck for both17:04
alaskibauzas: yep17:05
alaskifortunately jenkins seems in good shape atm17:05
bauzasanyway, let's see what we can do soon17:05
bauzasRC1 is tomorrow :/17:05
*** mrunge_away is now known as mrunge17:06
alaskiyep.  we're close though17:06
alaskianything more on testing?17:06
melwittI'll ask in infra and see if we can get +W today17:06
alaskimelwitt: thanks17:07
bauzasmelwitt: cool17:07
alaski#topic Specs17:07
*** openstack changes topic to "Specs (Meeting topic: nova_cells)"17:07
alaskithis is mainly a reminder that there are some specs now17:07
alaskiand scheduling in particular is going to get a lot of feedback I think17:07
*** VW__ has quit IRC17:07
alaskiso the earlier that happens the better17:07
alaskihttps://review.openstack.org/#/c/141486/ https://review.openstack.org/#/c/136490/ https://review.openstack.org/#/c/169901/17:08
bauzasalaski: nit: you should amend https://wiki.openstack.org/wiki/Nova-Cells-v2 by modifying the Gerrit search URL17:08
alaskibauzas: ok17:08
alaski#action alaski update https://wiki.openstack.org/wiki/Nova-Cells-v2 with new specs/reviews/info17:09
alaskianything to discuss on specs today?17:10
vineetmenonalaski: since we are in scheduling..17:10
bauzasalaski: I saw jaypipes's point and I will put some notes17:10
alaskibauzas: thanks17:10
*** megm has joined #openstack-meeting-317:10
vineetmenonis it finalized that top level will schedule a new instance upto node level?17:10
bauzasalaski: because I think what cells v2 is trying to do with scheduling can directly benefit to scheduler17:10
bauzasvineetmenon: that's what's discussed in https://review.openstack.org/#/c/141486/17:11
vineetmenoni mean the scheduling decision (cell, host) will be entirely taken by top level17:11
alaskivineetmenon: nothing is finalized at this point17:11
*** megm_ has quit IRC17:11
alaskivineetmenon: but the idea is that asking to be  scheduled will return that17:11
alaskivineetmenon: and the scheduler might be broken into two levels behind the scenes.  that's up in the air now though17:11
bauzasalaski: I was thinking of an approach like Google Omega, ie. multiple optimistic schedulers sharing a global view17:11
vineetmenonalaski: kk17:12
bauzasalaski: but that's a scheduler approach - the biggest problem is what jaypipes said, ie. the current scheduler doesn't scale well17:12
bauzass/well/at all even17:12
alaskibauzas: I saw you post http://eurosys2013.tudos.org/wp-content/uploads/2013/paper/Schwarzkopf.pdf a while ago and have that in a tab to read17:13
bauzasalaski: that's a long long journey17:13
bauzasalaski: but I'm trying to move towards that direction17:13
alaskibauzas: but if you could distill that into comments on the spec that would be very helpful17:13
bauzasalaski: honestly, it's all about deliverables17:13
vineetmenon:)17:14
bauzasalaski: we can't barely assume that the nova scheduler will be able to cope by magic with thousands of nodes17:14
bauzasat least for L17:14
alaskiagreed17:14
bauzasalaski: so I think we should keep a divide and conquer approach as a short term solution17:14
alaskiwhat I'm looking at is can we get cells into the scheduler and have it cope with the load of a current non cells deployment17:15
alaskiI don't expect it to handle a rackspace or CERN load yet17:15
vineetmenonbauzas: I was thinking the same +!17:15
bauzaswith the magic Scheduler (with a big S) as a mid-term goal17:15
*** sreshetn2 has quit IRC17:15
*** stevelle has left #openstack-meeting-317:15
bauzasalaski: well, I think that the idea behind cells is duplication17:15
*** yamahata has quit IRC17:16
bauzasie. call it mitosis17:16
bauzasie. doesn't scale ? duplicate it17:17
alaskibauzas: I'm on board with keeping a two level approach, assuming that's what you mean by divide and conquer, if we abstract that properly17:17
alaskii.e. hide it behind a client api17:17
vineetmenon+1 with two level is that it can scale up to n levels.. if properly thought of..17:17
bauzasalaski: shard it, if you prefer17:18
alaskibauzas: gotcha.  I'm fine with that too, but that's a big change17:18
*** safchain has quit IRC17:18
alaskiand has to answer many of the same questions as cells, like how do we handle affinity/anti-affinity17:18
bauzasalaski: I think that's a tinier change than just a scalable scheduler17:18
*** yamahata has joined #openstack-meeting-317:19
bauzasalaski: IIUC, RAX is using one sched per cell ?17:19
alaskibauzas: yes17:19
bauzasokay, plus the cells scheduler for parenting this17:19
bauzasplus the CacheScheduler, got it17:19
*** amotoki has quit IRC17:20
bauzasokay, sounds like a big big thing anyway - either we scale up or we scale out17:20
alaskiI think we need to have an understanding of what requirements need to be met for scheduling, and then we can look at how to do it17:20
bauzasalaski: well, the scheduler itself is fairly easy to understand*17:21
bauzasalaski: the main problem is that it's racy17:21
alaskibecause while I agree that sharding is easier than scaling the scheduler as is, it needs to handle affinity which is then trickier17:21
bauzasalaski: so the bigger your deployment is, the higher you get retries17:22
bauzasalaski: agreed17:22
*** e0ne has quit IRC17:22
bauzasalaski: in particular if we consider that aggregates and servergroups are colocated with the cloud itself, not a child cell17:22
bauzasbut that question hasn't been answered AFAIK17:23
bauzasalaski: do you plan inter-cell migrations with cells ?17:23
alaskiit hasn't, but I agree17:23
alaskibauzas: that's tricky too.  I think Nova should support it, but you may want to turn it off.17:24
bauzasagreed17:24
vineetmenonbauzas: what does that mean, 'inter-cell migrations'?17:25
bauzasvineetmenon: do you want to live/cold migrate or evacuate VMs from cell1@hostA to cell2@hostB N17:25
bauzas?17:26
alaskithis actually gets into the next topic so let me switch real quick17:26
alaski#topic Cells Scheduling17:26
*** openstack changes topic to "Cells Scheduling (Meeting topic: nova_cells)"17:26
*** Sukhdev has quit IRC17:26
alaski:)17:26
bauzasalaski: that reminds me that I probably missed the biggest question : do we hide to the users the complexity of deployments and are we just showing instances - not cells17:26
bauzasalaski: or is it a segragation thing ?17:27
bauzas*segregation17:27
alaskiI don't want to hide it, not fully17:27
bauzasalaski: speaking of end-users, not admins of course17:27
alaskiit doesn't have to be exposed as cells though17:27
*** LouisF has joined #openstack-meeting-317:27
bauzasalaski: that's my thought17:28
bauzasalaski: but if it's hidden, then that's just like aggregates, an op thing17:28
alaskiI think it's useful to know if two instances are in the same or different cells17:29
melwittif I think about the use case of scheduling to a specific cell using a scheduler hint, then I think it would be nice to expose something about the cells17:29
*** armax has quit IRC17:29
*** armax has joined #openstack-meeting-317:29
alaskimelwitt: agreed17:30
bauzasmelwitt: that's the difference between AZs and aggregates17:30
bauzasanyway, I just want to ask those questions not to point out all the difficulties, just say that we'll need to make decisions and approximations17:31
alaskithis is a good question to get some operator feedback on17:31
bauzas+117:31
*** sarob has quit IRC17:31
*** jcoufal has quit IRC17:31
alaskiback to scheduling17:32
alaskiI think we should discuss some specifics to better shape what will be needed in the scheduler17:32
alaskiI started getting a list of scheduler filters, and alphabetically affinity is first17:33
alaskiI have two questions on it:  how do we revise the semantics for cells, and how do we implement it17:34
alaskifor the semantics I'm thinking about anti-affinity and cells17:34
alaskishould it mean anything as far as cells is concerned, like anti-affinity in same cell vs different cell?17:35
bauzasmmm, affinity is a big word17:35
bauzaswe have affinity for VMs, server groups and aggregates17:36
bauzasI'm fine with having a new level as cells, but that ties to the question I mentioned about cells scope17:36
*** sahid has quit IRC17:37
melwittI can think of it meaning anti-affinity within a cell. if a cell represents a group of instances belonging to a certain security zone for example. this kind of brings up the two level scheduling possibility I think, allowing in-cell schedulers to filter if they want to. at the top anti-affinity would mean different cells, in-cell it would be within the same cell17:38
alaskimost of the cells filters I deal with are primarily about the capabilities of a cell, this type of hardware for this type of flavor type thing17:38
alaskiso my initial thinking is that cells scope only deals with large things like that, everything else is global host level stuff17:38
*** MaxV has joined #openstack-meeting-317:38
bauzasmelwitt: that's just two filters, if we consider a top-level scheduler17:39
melwittbauzas: okay17:39
*** yamahata has quit IRC17:39
bauzasalaski: are you grouping per capabilities ?17:40
*** dheeraj-gupta-4 has quit IRC17:40
alaskibauzas: not sure what you mena17:40
alaskimean17:40
bauzasalaski: sorry, I was referring to what you mention as "capabilities of a cell"17:41
bauzasalaski: that implies homegeneous hardware17:41
alaskibauzas: ahh, gotcha17:41
alaskibauzas: doesn't have to be fully homogeneous, but close enough17:42
alaskilike all SSDs, but perhaps different cpus17:42
bauzasalaski: because I'm considering cells as just something for scaling Nova, not necessarly necessary for grouping17:42
bauzasalaski: because aggregates are used for that purpose17:42
alaskisure, but it is a grouping as well and I think it will be used that way17:43
*** iovadia has joined #openstack-meeting-317:43
*** iovadia has left #openstack-meeting-317:43
bauzasalaski: sorry but why not creating a big aggregate per cell, and leave as it is now ?17:43
alaskibut it's a good point that it doesn't need to be17:43
bauzasalaski: I'm asking that, because that sends a bad signal that cells are just aggregates17:44
bauzasalaski: but I agree with you on the colocation aspect17:44
bauzasalaski: I guess you tend to group cells by hardware proximity17:45
alaskiyeah17:45
alaskiI'm currently rethinking how much of a concept cells need to be in the scheduler17:45
alaskiwe do need to figure out how to migrate the concepts we currently have into something the scheduler can handle17:46
bauzasalaski: well, I'm considering cells as just a new colocation object17:46
alaskibut if can move cell capabilities into aggregates that could be a path17:47
alaskibauzas: yeah, but should that be different than an implicit aggregate?17:47
bauzasalaski: because of the affinity stuff you mentioned17:47
bauzasalaski: like saying that you have a DC with 3 floors17:48
bauzasalaski: you could use aggregates for grouping your SSD hosts which are not at the same floor17:48
bauzasalaski: but you could need to do a boot request saying 'I want to boot on a host at the 3rd floor, because I know that my power consumption is lower there"17:49
bauzasalaski: of course, it can be implicit17:49
bauzasso the affinity can be done orthogonallyt17:50
alaskiright17:50
bauzasalaski: and that would solve one big confusion about Nova AZs != AWS AZs17:51
bauzasbecause we could say that Nova cells are somehow related to AWS AZs17:51
alaskipossibly17:52
alaskithat's still up to the deployer I think17:52
bauzasagreed17:52
bauzasthat's why I'm saying that's just a new segregation object for the scheduler17:52
bauzasso new filters17:52
bauzas- leaving off the scaling problem, of course -17:53
*** LouisF has quit IRC17:53
alaskithe new filter would be at the same place other scheduler filters are at17:53
bauzasalaski: if the scheduler is a global scheduler, yes17:53
alaskigoing this route I'm not sure we're introducing a real scalability difference17:53
bauzasthat's just an abstraction that leaves the scalability problem unresolved17:54
alaskibauzas: right, I'm assuming global scheduler for now since that's what we have17:54
alaskibauzas: unresolved, but not any different than today right?17:54
bauzasalaski: exactly, and that's necessary to keep that abstraction if we want "orthogonal" filtering17:55
bauzasalaski: right, I'm just trying to say that's distinct efforts17:55
bauzas#1 scalability problem of a global scheduler17:55
bauzas#2 cells-related filters17:55
*** mrmartin has joined #openstack-meeting-317:55
alaskiokay.  agreed, though for this meeting I would reverse the ordering :)17:56
bauzaslol17:56
bauzasjust thinking about hash rings for scheduler, lol17:56
alaskiwell that felt productive to me, because I'm totally rethinking scheduling now17:56
alaskibauzas: heh, if we could do that it would be pretty cool17:57
bauzasyeah.... but claims are compute-based :/17:57
alaskiso my takeaway is that I need to rewrite my scheduling spec17:57
bauzaseh17:58
bauzasyou have to jump in on scheduler, as I have to do with cells :)17:58
alaskiI'm seeing that17:58
alaskiI'll look up the meeting time and start showing up17:59
*** yamahata has joined #openstack-meeting-317:59
bauzascool17:59
alaskiany last minute thoughts from anyone, since we didn't get an open discussion?17:59
melwittregex fix merged, I put rechecks on the two patches17:59
bauzasmelwitt: \o/17:59
alaskimelwitt: awesome!17:59
bauzasmens are chattering...17:59
bauzascongrats !18:00
melwittheh18:00
bauzasdoing rechecks now18:00
alaskishe already did them18:00
alaskithanks everyone!18:00
bauzasoh cool18:00
bauzasthanks18:00
alaski#endmeeting18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
openstackMeeting ended Wed Apr  8 18:00:40 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
vineetmenonciao18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-04-08-17.00.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-04-08-17.00.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-04-08-17.00.log.html18:00
*** sarob has joined #openstack-meeting-318:01
*** vineetmenon has quit IRC18:01
*** MarkAtwood has quit IRC18:02
*** mwang2 has quit IRC18:05
*** seizadi has joined #openstack-meeting-318:06
*** mwang2 has joined #openstack-meeting-318:06
*** seizadi1 has joined #openstack-meeting-318:06
*** seizadi has quit IRC18:06
*** seizadi1 has quit IRC18:07
*** sarob has quit IRC18:08
*** sarob has joined #openstack-meeting-318:08
*** seizadi has joined #openstack-meeting-318:08
*** sreshetn2 has joined #openstack-meeting-318:11
*** mrmartin has quit IRC18:14
*** VW_ has joined #openstack-meeting-318:14
*** SumitNaiksatam has joined #openstack-meeting-318:22
*** yushiro has joined #openstack-meeting-318:22
*** badveli has joined #openstack-meeting-318:27
*** SridarK has joined #openstack-meeting-318:28
SumitNaiksatamyushiro: badveli SridarK vishwanathj: hi18:30
*** johnthetubaguy is now known as zz_johnthetubagu18:30
vishwanathjHi All18:30
SridarKSumitNaiksatam: and all hi18:30
badvelihello sumit and all18:30
yamahatahello18:30
yushiroSumitNaiksatam, badveli SridarK hi  :-)18:30
badvelihello yushiro18:30
*** mrmartin has joined #openstack-meeting-318:30
SumitNaiksatamyamahata: hi18:30
SumitNaiksatam#startmeeting Networking FWaaS18:30
openstackMeeting started Wed Apr  8 18:30:56 2015 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:30
*** openstack changes topic to " (Meeting topic: Networking FWaaS)"18:30
openstackThe meeting name has been set to 'networking_fwaas'18:31
SridarKbadveli: yamahata: yushiro: hi18:31
badvelihello sridark18:31
SumitNaiksatam#topic Bugs18:31
*** openstack changes topic to "Bugs (Meeting topic: Networking FWaaS)"18:31
SumitNaiksatamthis is a doc bug: #link https://bugs.launchpad.net/openstack-manuals/+bug/144086418:32
openstackLaunchpad bug 1440864 in openstack-manuals "Firewall-as-a-Service (FWaaS) overview in OpenStack Cloud Administrator Guide - current" [Undecided,New]18:32
SumitNaiksatamwe need someone to look at it18:32
*** sreshetn2 has quit IRC18:32
SumitNaiksatamyushiro: regarding #link https://bugs.launchpad.net/neutron/+bug/143938318:33
openstackLaunchpad bug 1439383 in neutron "FWaaS - the action of firewall-policy "insert_rule" and "remove_rule" not exist in policy.json" [Undecided,New] - Assigned to Yushiro FURUKAWA (y-furukawa-2)18:33
*** pc_m has joined #openstack-meeting-318:33
SumitNaiksatampc_m: hi18:33
pc_mhi!18:33
SumitNaiksatamyushiro: are you planning to post a patch?18:33
yushiropc_m, hi18:33
pc_myushiro: Hi18:33
yushiroSumitNaiksatam, yes. I'll post the patch.18:33
SumitNaiksatamyushiro: thanks!18:34
SridarKSumitNaiksatam: i will look into 144086418:34
SumitNaiksatamthe following is another relatively minor bug: #link https://review.openstack.org/#/c/169239/18:34
SumitNaiksatamSridarK: thanks much18:34
SumitNaiksatami thought the change was good, not sure why the gate keeps failing on that, i havent investigated18:35
SumitNaiksatamwe have this high priority doc bug: #link https://bugs.launchpad.net/openstack-api-site/+bug/142565818:35
openstackLaunchpad bug 1425658 in openstack-api-site "FWaaS needs WADL doc to be available in the API reference" [High,In progress] - Assigned to Sumit Naiksatam (snaiksat)18:35
SumitNaiksatami posted a patch for that18:35
SumitNaiksatamstill little more work to do18:35
SumitNaiksatami also volunteered co-authors ;-P18:36
SumitNaiksatamso first priority is to bring it in sync with the older documentation18:36
SumitNaiksatamand then add the router insertion specific details18:36
SridarKSumitNaiksatam: I am trying to add some stuff into the common.ent file18:36
pc_mSumitNaiksatam: Gates on 169239 is because of Neutron UT changes.18:36
SumitNaiksatampc_m: ah ok, the recent changes18:37
SumitNaiksatampc_m: thanks18:37
pc_mSumitNaiksatam: Should be fixed by my commit https://review.openstack.org/171602. Just rebase.18:37
SridarKSumitNaiksatam: +1 to pc_m18:37
SumitNaiksatampc_m: was just going to say, not sure why he didnt try a rebase18:37
SumitNaiksatamperhaps we can post a comment with the suggestion18:38
pc_mSumitNaiksatam: Will do.18:38
vishwanathjshould not the Rebase Change button work from the patch link18:38
*** jcoufal has joined #openstack-meeting-318:39
pc_mvishwanathj: Might, but might not, as there may be conflict in test file.18:39
vishwanathjnevermind, When I do that, I get the error "The Change could not be rebased due to a patch conflict during merge"18:39
pc_mvishwanathj: :)18:39
SridarKtest_db_firewall.py shd have conflicts18:40
pc_mSumitNaiksatam: What;s the patch number for the doc change?18:40
SridarKthe day that button works always we will all be redundant :-)18:40
vishwanathj:)18:40
pc_mLoL18:41
SumitNaiksatampc_m: which one?18:41
*** e0ne has joined #openstack-meeting-318:41
pc_mYou mentioned the WADL, you have a patch? Or is it not up for review yet?18:41
SumitNaiksatam#link https://review.openstack.org/#/c/170733/18:41
SumitNaiksatampc_m: ^^^18:42
pc_mthanks18:42
SridarKpc_m: u had filled in the common.ent file manually for vpn ?18:42
SridarKi recall u saying something to that effect18:43
pc_mSridarK: yeah I did everything manually.18:43
*** sergef has joined #openstack-meeting-318:43
SridarKpc_m: i will ping u offline for some pointers on that18:43
* pc_m manual = cut and paste :)18:43
SumitNaiksatampc_m: :-)18:43
SridarKpc_m: boy that file makes my head spin :-)18:43
SumitNaiksatampc_m: i took that advice to heart ;-)18:43
pc_mSridarK: Sure we can chat. It makes sense once you play with it for a while.18:44
SridarKpc_m: ok thx18:44
SumitNaiksatamany other interesting bugs we missed today?18:44
vishwanathjI need to respond to Yushiro's patch set.....18:45
SridarKSumitNaiksatam: nothing else i believe18:45
SumitNaiksatamSridarK: okay18:45
SumitNaiksatamvishwanathj: link?18:45
vishwanathjhttps://review.openstack.org/#/c/147396/18:45
yushirovishwanathj, thank you!18:46
vishwanathjfor some reason, I am still able to reproduce the issue after I apply the patch18:46
*** SridarK_ has joined #openstack-meeting-318:46
vishwanathjyushiro, you may need to upload another patchset as Jenkins as failed with error "Patch in merge conflict"18:46
SumitNaiksatamvishwanathj: ah, yeah noticed your comment earlier, thanks for trying it out18:47
*** jcoufal has quit IRC18:47
SumitNaiksatam#topic Functional/Integration tests in the gate18:47
*** openstack changes topic to "Functional/Integration tests in the gate (Meeting topic: Networking FWaaS)"18:47
SumitNaiksatambadveli: you said wanted to give this a shot?18:48
badveliyes thanks for your pointers18:48
yushirovishwanathj, I see.  I will upload the patch. current my patch status is 'Merge Conflict'.  I don't know why..18:48
*** stevemar has quit IRC18:48
badveli i went through the test that you had mentioned18:48
SumitNaiksatamfor the basic test i was proposing last week, i was thinking something along the lines of what this is doing: #link https://github.com/openstack/neutron/blob/master/neutron/tests/functional/agent/linux/test_iptables_firewall.py18:48
SumitNaiksatambadveli: okay great18:49
SumitNaiksatambadveli: you want to discuss here your findings?18:49
*** doug-fish has joined #openstack-meeting-318:49
*** SridarK has quit IRC18:49
badveli looks to me we can do some thing similar as you had mentioned set up firewall and  do some functional test like allow or deny case18:50
SridarK_SumitNaiksatam: badveli: is this for Scenario tests ?18:50
badveli sent some traffic and check18:50
SumitNaiksatamSridarK_: this is for functional tests18:51
SridarK_SumitNaiksatam: so API or beyond ?18:51
SumitNaiksatamSridarK_: in the last week we discussed with pc_m as to how we can get some functional tests going18:51
SumitNaiksatamwith functional tests the idea is to not require the entire opesntack stack to be running18:51
SridarK_SumitNaiksatam: ok got it - sorry - will catch up on logs18:52
yamahataDo you have any idea on how to create packet?18:52
badvelisridark to check the functionality of the firewall in affect18:52
SumitNaiksatambut perhaps just exercise the fwaas code such that it triggers the configuration iptables rules18:52
SumitNaiksatamyamahata: do we need to create a packet?18:53
SumitNaiksatamyamahata: i was not thinking in terms of testing the datapath18:53
yamahatait depends on what firewall rule to be tested.18:53
yamahataOkay18:53
SumitNaiksatamyamahata: but testing that the expected iptables rules are applied18:53
SridarK_ok makes sense - we can actually just check the iptables to see if the rule manifests in iptables18:53
SumitNaiksatamSridarK_: yeah18:53
*** sbalukoff has joined #openstack-meeting-318:54
SumitNaiksatamsince we can rely that iptables is independently tested for the data path18:54
*** sarob has quit IRC18:54
SridarK_SumitNaiksatam: yes and easier and more light weight makes total sense18:54
SumitNaiksatamof course we need to ensure that we are validating against the right critieria (in terms of what we expect the rules to be applied)18:54
badvelisumit in the tests that you had mentioned they check ping traffic18:54
SumitNaiksatambadveli: ah okay18:55
SumitNaiksatamso they do test the datapath18:55
badveli they use some helper18:55
SumitNaiksatambadveli: good to know18:55
SumitNaiksatampc_m: i guess any tests that we now land will go into liberty, right?18:55
pc_myeah18:56
SumitNaiksatambadveli: let us know how your investigation goes18:57
badvelithanks to pc_m for reorganizing the unit test case18:57
SumitNaiksatambadveli: and once you have some plan around this, lets share with the rest of the team18:57
SumitNaiksatambadveli: that way we can split the work and get more people involved18:57
badveli yes, also one more question will the functional test fall in different path18:57
pc_mSure, np. I had to do VPN and had a script to help, so I used it on FW.18:57
SumitNaiksatamyamahata: i believe you have some experience in this as well18:58
yamahataSure, willing to get involved/help18:58
SumitNaiksatamyamahata: so please chime in with your suggestions18:58
SumitNaiksatamyamahata: awesome!!18:58
badveli yes sumit, i started looking at that test and will update18:58
*** matrohon has joined #openstack-meeting-318:58
SumitNaiksatambadveli: great, thanks!18:58
SumitNaiksatambadveli please keep yamahata in close loop, he has good experience with this18:59
yamahatabadveli: please Yalei too18:59
badveli the functional tests will be under which a seperate directory structure18:59
SumitNaiksatambadveli is also local (with reference to your location), so you can bug him ;-P18:59
badveli ok, thanks yamahata18:59
badveliok, thanks yamahata and sumit19:00
SumitNaiksatambadveli: we have made a start in terms of the directory structure #link https://github.com/openstack/neutron-fwaas/tree/master/neutron_fwaas/tests/functional19:00
badvelisorry i saw we have a directory structure19:00
*** lblanchard has quit IRC19:01
SumitNaiksatamSridarK_: you mentioned that Nikolay was working on the tempest tests (scenario tests?)19:01
badveli yes thanks sumit19:01
SumitNaiksatamSridarK_: that will be a different effort from this19:01
SridarK_SumitNaiksatam: yes he will be doing that19:01
SumitNaiksatamjust to make sure we are all on the same page19:01
SridarK_SumitNaiksatam: got it19:01
SumitNaiksatamSridarK_: and it would be good to track that effort here as well19:01
SumitNaiksatamSridarK_: i believe this is a bad time fo Nikolay19:02
SumitNaiksatamso may be you can proxy him (i believe pc_m is in close discussion with him as well)19:02
SridarK_#link https://review.openstack.org/#/c/16585919:02
SridarK_patch from him for insertion mode19:02
SumitNaiksatamSridarK_: bam!! sweet!!19:02
SridarK_but will probab go to L19:02
SridarK_SumitNaiksatam: yes i will proxy for Nikolay19:02
SumitNaiksatamseems like an ultra lite patch though ;-)19:03
*** lblanchard has joined #openstack-meeting-319:03
SridarK_SumitNaiksatam: yes wanted to get a patch out - but working with him to improve coverage19:03
SumitNaiksatamlooking at the most recent comment, i agree as well, perhaps need a separate test case19:03
pc_mSumitNaiksatam: FYI, Nikolay is in Russia.19:03
SridarK_SumitNaiksatam: yes and more work is needed19:04
SumitNaiksatampc_m: thanks, yes, good for everyone to know19:04
SumitNaiksatamSridarK_: its great that Nikolay is on this, i dont mean to belittle the work in any way19:05
SumitNaiksatamsorry if i sounded like that19:05
SridarK_SumitNaiksatam: no totally understand did not take it that way at all just wanted to clarify19:05
SumitNaiksatamits take a lot of time and effort to just get the environment setup to be able start writing and tests like these19:06
SumitNaiksatamso its fantastic that he is at this point19:06
SumitNaiksatambecause if you get one test going, then i think its relatively easier to add more19:06
SridarK_SumitNaiksatam: he is working with pc_m for vpnaas as well19:06
SumitNaiksatampc_m: on that, you mentioned there were some issues that other neutron cores had raised19:06
SumitNaiksatampc_m: has that been sorted out, and the feedback conveyed to Nikolay?19:07
pc_mSumitNaiksatam: Yeah, main issue was that tests were using tempest repo imports. Nikolay has been working on doing the test w/o tempest.19:08
SumitNaiksatampc_m: ah okay19:08
pc_mSumitNaiksatam: He just posting something today, but I haven't looked at it yet.19:08
pc_mSumitNaiksatam: I mentioned to him that in Neutron they now have "fixtures" (see Fake* classes), and that maybe that would help as well19:09
SumitNaiksatampc_m: okay19:09
pc_mSumitNaiksatam: I haven't looked into the Fixtures much, but seems like they have things for ports, routers, networks, etc.19:09
SumitNaiksatampc_m: okay, thanks for relaying that information19:10
pc_mSumitNaiksatam: In short, there's a bunch to be done for the scenario test, but we've got time, as it'll land in Liberty.19:10
SumitNaiksatampc_m: true19:10
SumitNaiksatamthe first test will take time, after that it will be much easier to scale this out to more people19:11
SumitNaiksatamanything more to discuss today on the topic of functional/integration tests?19:11
SumitNaiksatamok moving on19:12
SumitNaiksatam#topic Open Discussion19:12
*** openstack changes topic to "Open Discussion (Meeting topic: Networking FWaaS)"19:12
SumitNaiksatamas regards the design summit19:12
SumitNaiksatam#link https://etherpad.openstack.org/p/liberty-neutron-summit-topics19:13
vishwanathjDo any of the vendor have to refactor their code as a result of https://review.openstack.org/#/c/169239/ getting merged?19:13
SumitNaiksatamvishwanathj: i doubt it19:14
vishwanathjlooks like the Vyatta Firewall agent code might have to respin? I am investigating the impact and code changes19:14
vishwanathjSumitNaiksatam, Ok19:14
SumitNaiksatamvishwanathj: okay19:15
SridarK_vishwanathj: i would have thought this should not have any impact19:15
SumitNaiksatamthere seems to be a comment in the etherpad: “The future of FWaaS: What do we do with it, how it relates to security groups, etc.”19:15
SumitNaiksatamline item 4319:15
SridarK_SumitNaiksatam: interesting :-)19:16
*** mrmartin has quit IRC19:16
SumitNaiksatamyou can go through the time line and see who added that19:16
SumitNaiksatami am guessing its not someone from this team19:17
SumitNaiksatami cant tell clearly who it is19:17
SridarK_SumitNaiksatam: should the answer be "Bright" :-)19:17
SridarK_the future that is :-)19:17
SumitNaiksatamSridarK_: :-)19:17
vishwanathjSumitNaiksatam, SridarK_, vyattaFirewallAgent implements the method process_router() method, refer https://review.openstack.org/#/c/169239/....19:17
SumitNaiksatamvishwanathj: okay19:18
*** igordcard_ has joined #openstack-meeting-319:18
SumitNaiksatamso if you have any firewall related topics that you need to add, please add them to etherpad19:18
vishwanathjwrong link, refer https://github.com/openstack/neutron-fwaas/blob/master/neutron_fwaas/services/firewall/agents/vyatta/fwaas_agent.py19:19
vishwanathjthe patchset https://review.openstack.org/#/c/163222/6/neutron/agent/l3/agent.py removes the call to process_router()19:19
SridarK_vishwanathj: ok - i was getting really confused as that was a one line change19:20
vishwanathjSridarK_, I need to investigate what the corresponding change should be ....was wondering if the other vendor codes had already looked into it and assessed the impacts....19:21
SridarK_vishwanathj: we have our own agent so this should not impact us19:21
vishwanathjlooks like you guys may not be impacted and the Vyatta code might be....will approach you guys for guidance if needed19:21
SridarK_but other vendors may have a similar situation19:21
*** ivar-lazzaro has quit IRC19:21
vishwanathjpc_m, was the VPN code impacted?19:22
*** ivar-lazzaro has joined #openstack-meeting-319:22
pc_mvishwanathj: I don't think so.19:23
vishwanathjpc_m, Thanks19:23
pc_mTests pass, so it must work :)19:24
vishwanathj:)19:24
SumitNaiksatampc_m: :-)19:24
SumitNaiksatamokay anything else for today?19:24
badveli viswanathj i am looking at the agent patch, will update if we need to change in the mean time let me know how are you handling the removed process_router19:25
vishwanathjbadveli, I need to investigate, will keep you posted on what I find out19:25
badveli   ok, thanks19:26
vishwanathjbecame aware of this only this morning19:26
pc_mvishwanathj: VPN just listens for the events, which happen in _process_added_router() and _process_updated_router().19:26
pc_mvishwanathj: FW could do the same thing, and decouple from the agent, if desired.19:27
vishwanathjpc_m, thanks, let me spend some time trying to grasp this...will probably ping you on IRC if I have questions19:27
badvelithanks pc_m for the pointers19:27
pc_mIOW, VPN "subscribes" for notifications of various events from agent, and then has handlers for those events. FW can do the same thing, if action needed on the events.19:28
pc_mvishwanathj: sure19:28
*** mrmartin has joined #openstack-meeting-319:28
*** sreshetn2 has joined #openstack-meeting-319:28
SumitNaiksatampc_m: yes19:29
*** matrohon has quit IRC19:29
SumitNaiksatampc_m: thanks much for jumping in and fixing the UT failures19:29
SumitNaiksatampc_m: by the time i woke up and noticed that there was an issue, you had it fixed ;-)19:29
pc_mSure np. I did a fix for the check bash script thing too, but it'll have to wait for liberty19:29
SumitNaiksatampc_m: ok19:29
pc_myeah earlt bird gets the worm :)19:30
*** VW_ has quit IRC19:30
pc_mearly19:30
SumitNaiksatampc_m: :-)19:30
*** VW_ has joined #openstack-meeting-319:30
SumitNaiksatamthanks eveyrone19:30
SumitNaiksatambye!19:30
pc_mbye19:30
vishwanathjbye19:30
yushiroBye bye19:30
yamahatabye19:30
SumitNaiksatam#endmeeting19:30
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:30
openstackMeeting ended Wed Apr  8 19:30:57 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-04-08-18.30.html19:30
*** pc_m has left #openstack-meeting-319:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-04-08-18.30.txt19:31
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-04-08-18.30.log.html19:31
badvelibye19:31
badveli19:31
*** MaxV has quit IRC19:34
*** ivar-lazzaro has quit IRC19:34
*** Piet has quit IRC19:35
*** robcresswell has joined #openstack-meeting-319:41
*** Sukhdev has joined #openstack-meeting-319:41
*** MaxV has joined #openstack-meeting-319:41
*** e0ne has quit IRC19:43
*** absubram has joined #openstack-meeting-319:44
*** MaxV has quit IRC19:44
*** e0ne has joined #openstack-meeting-319:47
*** enikanorov has joined #openstack-meeting-319:51
*** Yi has joined #openstack-meeting-319:51
*** yushiro has quit IRC19:52
*** yamamoto has joined #openstack-meeting-319:52
*** SridarK_ has quit IRC19:53
*** Piet has joined #openstack-meeting-319:55
*** Rockyg has joined #openstack-meeting-319:56
*** btully has quit IRC19:57
*** lhcheng has joined #openstack-meeting-319:57
*** yamamoto has quit IRC19:57
*** mattfarina has quit IRC19:58
*** jwy has joined #openstack-meeting-319:59
*** crobertsrh has joined #openstack-meeting-319:59
*** VW_ has quit IRC19:59
david-lyle#startmeeting Horizon19:59
openstackMeeting started Wed Apr  8 19:59:36 2015 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot.19:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:59
*** openstack changes topic to " (Meeting topic: Horizon)"19:59
openstackThe meeting name has been set to 'horizon'19:59
david-lylehello horizon folks19:59
lhchengo/19:59
mrungeo/19:59
bpokornyHi20:00
crobertsrhHello/20:04
*** esp has joined #openstack-meeting-320:04
*** TravT_ has joined #openstack-meeting-320:04
david-lyleso much excitement an hour ago, so few hands20:04
*** mattfarina has joined #openstack-meeting-320:04
TravT_?20:04
robcresswellWrong time again? :p20:04
mrungeTravT_, you missed us trying to start the meeting one hour earlier20:04
robcresswellEvening all :)20:04
TravT_ahh, glad i missed it!20:04
david-lyleeveryone was wanting a meeting an hour ago20:04
TravT_let's pretend it was an hour now20:04
TravT_pretend it was an hour ago, and just call it good20:04
david-lyleAlright folks, we are almost done with RC-120:04
david-lyle#link https://launchpad.net/horizon/+milestone/kilo-rc120:04
espnice!20:04
david-lyle5 FFEs merged and 1 was deferred to Kilo20:04
robcresswellNice work20:04
doug-fishcool20:04
david-lyleerr libery20:04
*** matrohon has joined #openstack-meeting-320:04
* david-lyle failing20:04
*** e0ne has quit IRC20:04
david-lyleLiberty20:04
david-lylethere I can type it20:04
*** sreshetn2 has quit IRC20:04
david-lylea Few more bugs that would be nice to have fixed20:04
*** btully has joined #openstack-meeting-320:04
david-lyleat least the fixes for said bugs20:04
david-lylewe have enough bugs20:04
david-lylea couple more items for launch instance are not in that list for some reason20:05
david-lyleI blame the PTL20:05
*** sqchen has joined #openstack-meeting-320:05
david-lylewill look to remedy that20:05
mrungewe can elect a new ptl20:05
doug-fish:-)  I have more bugs on deck that I'm planning to spring on you over the next day or 2.  Related to hardcoded English strings.20:05
david-lyleI don't think any of the remaining bugs will block the RC20:06
mrungedoug-fish, I think we're already in string freeze?20:06
david-lylewhich I expect to be tomorrow or Friday20:06
doug-fishthat makes sense to me.20:06
david-lyleMonday at the latest20:06
mrungeif not, we're nearly there20:06
doug-fishI think we are only in _mostly_ string freeze at this point20:06
doug-fishright?20:06
doug-fishrc1 is the real freeze20:06
*** ivar-lazzaro has joined #openstack-meeting-320:06
david-lyleYes, we need to give the translators time to do the final translations20:06
TravT_we have fixes up for the launch instance bugs.20:07
*** gary-smith has joined #openstack-meeting-320:07
TravT_i just tested all of them.20:07
david-lylethat will hopefully be the only patch merged for RC220:07
mrungedavid-lyle, when you cut rc1, could you release another d-o-a, too?20:07
TravT_looks like a couple really minor styling things to fix up.20:07
mrungeI mean django_openstack_auth20:07
lhchengthere have been couple of bugs creeping in, but mostly bugs we think important enough to include and was already approved20:07
david-lylemrunge: I need to wait for the kilo release to finalize20:08
david-lyleI will right after that20:08
doug-fishdavid-lyle: will we hold up rc1 for https://bugs.launchpad.net/horizon/+bug/1436903 ?20:08
openstackLaunchpad bug 1436903 in OpenStack Dashboard (Horizon) "integration tests failing blocking gate" [Critical,Confirmed] - Assigned to David Lyle (david-lyle)20:08
david-lyledoug-fish: I don't think so20:08
*** stevemar has joined #openstack-meeting-320:08
david-lyleI certainly would like to have a fix, but I have not tracked down the root cause20:08
doug-fishyeah that was going to be my next question20:09
lhchengdavid-lyle: when do we consider kilo release finalized? is that after rc1 or even later?20:09
david-lylethe only patch I saw attempting to fix it other than mine was to lengthen the timeout20:09
david-lylewhich I'm loathe to do20:09
david-lylelhcheng: I think once most/all projects RC-1s are cut20:09
lhchengdavid-lyle: okay20:10
david-lylewe just don't want to cause gating issues as a side effect20:10
david-lyleso releasing now is frowned upon20:10
lhchengsounds reasonable20:10
*** emw has joined #openstack-meeting-320:11
lhcheng++20:11
david-lyleOk, other general items20:11
*** bradjones_ has joined #openstack-meeting-320:11
david-lyleThe PTL nomination season is upon us if you didn't see the email on the dev ML20:11
david-lyleI nominated myself again, it is always open to self-nomination20:12
david-lyleI think the deadline is 6:00 UTC tomorrow20:12
tqtranhow does one vote for it?20:12
*** smc7 has joined #openstack-meeting-320:13
*** jgravel has joined #openstack-meeting-320:13
*** bradjones has quit IRC20:13
*** bradjones_ is now known as bradjones20:13
*** bradjones has joined #openstack-meeting-320:13
david-lyleSo if someone declares their candidacy, there would be an election20:13
mrungetqtran, you'll just send a mail to openstack-dev and announce, you're running for PTL. Bonus points, for reasons to vote for you20:13
david-lyleand you would receive email about voting, otherwise if I am the only one running, no election20:13
mrungeat least, we'd then have an elected PTL20:13
tqtranno i meant, once the candidates are announced, how do we vote?20:13
lhchengmrunge: only folks that contributed to that project can vote?20:13
tqtranah ok20:14
mrungeyes20:14
*** ivar-lazzaro has quit IRC20:14
david-lyleyes ATCs would get the email20:14
mrungelhcheng, that's right, and only contributors can declare their candidacy20:14
*** ivar-lazzaro has joined #openstack-meeting-320:14
david-lyleA week after the PTL elections close is the TC self-nomination period20:15
mrungeso: folks, think twice, nominate yourself20:15
mrungejust to have an elected PTL20:15
david-lyleif you're interested in that20:15
* mrunge hides20:15
*** ivar-lazzaro has quit IRC20:15
david-lyleI meant the TC20:15
*** ivar-lazzaro has joined #openstack-meeting-320:16
TravT_Is TC only self-nominate?  or are all of these also things that others can nominate?20:16
david-lyleTravT_: I think only self nominate, but unsure20:17
david-lyleI think there is a willingness thing that comes into play :)20:17
david-lylethe board seats are true nominations20:17
david-lyleand you can decline the nomination20:17
david-lylethe PTL and TC elections are not that sophisticated20:17
TravT_Can one explain exactly what all the TC does?20:17
david-lyleTravT_: :/20:18
mattfarinalol20:18
mrungeTravT_, can we please move such merely unrelated questions to somewhere else?20:18
david-lyleno, the TC (Technical Committee) is the technical governing body of the developers in openstack20:18
mrungehttps://www.openstack.org/foundation/tech-committee/20:19
david-lylebut the prose mrunge linked will be better and more effective20:19
TravT_mrunge: thx20:19
ttxalso governance.oenstack.org for current data on TC20:19
ttxerr.. governance.openstack.org20:20
TravT_ttx: thx20:20
david-lyleok, release stuff in another room, back20:22
*** MaxV has joined #openstack-meeting-320:22
*** VW_ has joined #openstack-meeting-320:22
mrungewe have a single item on today's agenda20:23
mrungehttps://wiki.openstack.org/wiki/Meetings/Horizon#Agenda_for_April_8_2000_UTC20:23
david-lyle#chair mrunge20:23
openstackCurrent chairs: david-lyle mrunge20:23
david-lyleback in a minute20:23
mrungelhcheng, you put django-1.7 and d-o-a and python-2.6 there20:24
lhchengmrunge: yeah20:24
lhchengso we have some work to add support for Django1.7 for horizon20:25
david-lyleI think we'll be ok to drop 2.620:25
lhchenghowever, the DOA patch to update the django version to 1.7 have been failing: https://review.openstack.org/#/c/167942/20:25
david-lylejust trying to determine the timeline right now20:25
lhchengthis is due to some django tests classes code that doesn't work with py2620:25
mrungeyeah. correct. django-1.7 dropped py26 support20:26
mrungeso, django-1.6 is the last version supporting py2620:26
doug-fishso what happens with d_o_a for icehouse or juno? no updates are available if you have py26?20:27
mrungeI think "we" (as OpenStack) decided in Paris(?) to drop support for Python-2.6 during Kilo dev cycle, right?20:27
mrungedoug-fish, there was ttx email about stable branches for libs etc. today20:28
doug-fishk, thx (looking)20:28
david-lylenext release of doa will be 1.2.0 and not have python 2.6 support20:29
lhchengmrunge:  what if there are security patches needed for icehouse or juno, how do we distribute the fix?20:29
mrungelhcheng, I would expect via stable branch20:29
mrungelike for horizon20:29
doug-fishd_o_a doesn't have such a thing, does it?20:30
lhchengmrunge: ah so we backport to the last version and re-release it to pypi?20:30
mrungeI would expect e.g 1.1.x to be pre-kilo20:30
david-lylelhcheng: we don't now20:30
david-lylethose versions are capped20:30
mrunge1.2.x kilo20:30
mrungeand maybe 1.3.x for liberty (or so)20:30
david-lylestarting with kilo, we'll create a stable branch20:30
*** sreshetn2 has joined #openstack-meeting-320:31
doug-fishthat's a good plan.  I can understand that!20:31
mrungeI already have those for packages20:31
mrungestable branches20:31
*** badveli has quit IRC20:31
lhchengmrunge: ah 1.1.x sounds good, thanks!20:31
david-lyleok looks like 1.2.0 is a possibility for Kilo20:32
*** mwagner_lap has quit IRC20:32
mrungelhcheng, that's not set in stone yet20:32
david-lylemrunge: doa will have stable branch in its tree for kilo20:32
david-lylejust have to get there20:32
mrungeI would like to have some clearer versioning scheme20:33
david-lylethen kilo will have a capped version of d-o-a20:33
david-lylemrunge: than?20:33
mrungedavid-lyle, maybe like 2015.1.x for kilo20:33
mrunge2014.2.x for juno20:33
mrungeto have the clear relation20:33
*** mrmartin has quit IRC20:33
*** stevemar has quit IRC20:34
david-lylenot sure how that would work for requirements.txt20:34
mrungebut if we'd move d-o-a back in horizon, as mentioned sometime ago...20:34
*** stevemar has joined #openstack-meeting-320:34
david-lylemrunge: that's a conversation for the summit, but certainly a possibility20:35
mrunge1.1.x < 2014.2 < 2015.120:35
mrungeso capping should be possible20:35
mrungeback to d-o-a and py26: are we fine with dropping py26 support?20:36
mrungeand disabling py26 based tests?20:36
david-lylemrunge: yes, checked and we are ok to doing that20:36
david-lyleI have the patch almost ready20:36
mrungeok, great!20:36
david-lylewill push for review after the meeting20:36
mrungethanks, could you please add me, I will review it asap20:37
david-lylegoing to send an email to the dev ML to explain the requirements mismatch and the high possibility of a late release and g-r bump20:37
lhcheng++ thanks david-lyle20:37
mrungeyes, thank you!20:37
david-lyleI'm worried we'll have install problems with 1.6 and 1.7 competing requirements for django cap20:38
david-lyle#topic Open Discussion20:38
*** openstack changes topic to "Open Discussion (Meeting topic: Horizon)"20:38
mrungeas far as I understand that, we should be fine with django-1.720:39
david-lylemrunge: I was worried about dependency resolution20:39
david-lyledepending how the two are packaged20:40
mrungedavid-lyle, you mean, because of pip installing both?20:40
mrungepip overwrites installed files happily20:40
david-lylemrunge: I was more worried about distro packaging20:41
mrungedavid-lyle, yes, me too20:41
david-lyleso even though horizon supports 1.7 you would be limited to 1.620:41
david-lyleand hopefully the various packaging systems could handle that20:42
*** stevemar has quit IRC20:42
mrungedavid-lyle, I'm usually ignoring requirements.txt20:42
david-lylewhich I'm not confident of20:42
*** stevemar has joined #openstack-meeting-320:42
david-lylemrunge: ok, the library already works with 1.7 in 1.0.920:42
mrungeI just take it as recommendation, and run the test suite during package build again20:42
david-lylejust for the target python version?20:43
david-lyleor py26 as well20:43
mrungeyes20:43
mrungedavid-lyle, you can run run_tests.sh -N, which will run the test suite with installed versions20:44
david-lylemrunge: there is no run_test in django_openstack_auth20:44
mrungequite handy, and it gives me a more confidence20:44
david-lylebut you just run it for horizon20:44
mrungeyes, correct20:44
david-lyleok20:44
mrunged-o-a is quite simple here.20:45
mrungeeither works or not20:45
mrungebut this reminds me, we should integrate that more tightly in integration tests20:45
mrungeI mean, a d-o-a git checkout rather than released versions20:46
david-lylemrunge: that should be happening already as devstack clones d-o-a20:46
david-lyleerr, maybe not anymore20:47
david-lyle:(20:47
mrungedavid-lyle, we had the situation, that d-o-a broke horizon not that long ago20:47
mrungeimho lhcheng fixed that20:47
mrungeand he might have a better memory than me about that20:48
david-lylelooks like it's a configuration option in devstack now20:49
david-lylewill look into more how to turn it on20:50
*** sreshetn2 has quit IRC20:50
david-lylethe overall stability of the integration tests is not good20:50
david-lylewe need to rethink the tool sets a bit20:50
david-lyleI think20:50
mrungeyes!20:50
lhchengmrunge: I haven't done anything to fix the d-o-a checkout on devstack test20:50
*** gulic has joined #openstack-meeting-320:51
mrungehmm, I thought so20:51
lhchengmrunge: just did a fix where horizon tests were failing for 1.820:51
david-lylethe behavior changed in devstack20:52
david-lyleI think as part of the whole library stabilization efforts20:52
david-lyleas a reminder: #link https://etherpad.openstack.org/p/horizon-liberty-summit20:53
david-lylea few minutes left today, anyone else?20:54
david-lyles/anyone/anything/20:54
mattfarinadavid-lyle when are the proposed sessions for liberty summit due?20:55
david-lylemattfarina: the schedule is usually set a couple weeks before the summit20:55
david-lyleto make sure people have time to prep20:55
david-lylebut also want to make sure we get relevant/fresh topics20:56
david-lyleThe PTL for the cycle selects the sessions, so it can't happen until after election season20:56
*** lblanchard has quit IRC20:57
*** absubram has quit IRC20:57
*** sergef has quit IRC20:58
*** LouisF has joined #openstack-meeting-320:58
david-lyleok 2.6 removal patch up on DOA20:59
david-lylerunning tests in the gate20:59
david-lyleand we're out of time20:59
*** LouisF has quit IRC20:59
david-lyleThanks for all the hard work on RC-1, we'll be working on Liberty by the next meeting. That is once RC-1 is but, master is open for Liberty.21:00
david-lyle#endmeeting21:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:00
openstackMeeting ended Wed Apr  8 21:00:13 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-04-08-19.59.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-04-08-19.59.txt21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-04-08-19.59.log.html21:00
*** robcresswell has left #openstack-meeting-321:00
david-lyles/but/cut21:00
mrungethank you all21:00
*** esp has left #openstack-meeting-321:01
*** tqtran has left #openstack-meeting-321:01
*** crobertsrh is now known as _crobertsrh21:02
*** jwy has left #openstack-meeting-321:09
*** mrunge has quit IRC21:10
*** gary-smith has left #openstack-meeting-321:10
*** jckasper has quit IRC21:11
*** megm_ has joined #openstack-meeting-321:12
*** megm has quit IRC21:12
*** bryan_att has quit IRC21:14
*** Rockyg has quit IRC21:14
*** sqchen has left #openstack-meeting-321:16
*** lhcheng has left #openstack-meeting-321:17
*** SumitNaiksatam has quit IRC21:21
*** obondarev_ has joined #openstack-meeting-321:27
*** obondarev has quit IRC21:27
*** jtomasek has quit IRC21:29
*** Yi_ has joined #openstack-meeting-321:29
*** Yi has quit IRC21:29
*** s3wong has joined #openstack-meeting-321:30
*** mwagner_lap has joined #openstack-meeting-321:33
*** s3wong has quit IRC21:40
*** banix has quit IRC21:40
*** Sukhdev has quit IRC21:41
*** claired has joined #openstack-meeting-321:44
*** jckasper has joined #openstack-meeting-321:47
*** barbinderallcan has joined #openstack-meeting-321:48
*** MaxV has quit IRC21:48
*** claired has quit IRC21:52
*** jckasper has quit IRC21:52
*** reed_ has joined #openstack-meeting-321:52
*** barbinderallcan has quit IRC21:53
*** amotoki has joined #openstack-meeting-321:54
*** bknudson has left #openstack-meeting-321:58
*** carl_baldwin has quit IRC22:03
*** seizadi has quit IRC22:05
*** s3wong has joined #openstack-meeting-322:10
*** banix has joined #openstack-meeting-322:19
*** sigmavirus24 is now known as sigmavirus24_awa22:24
*** seizadi has joined #openstack-meeting-322:25
*** ivar-lazzaro has quit IRC22:27
*** seizadi has quit IRC22:29
*** stevemar has quit IRC22:30
*** banix has quit IRC22:32
*** baoli_ has quit IRC22:39
*** alexpilotti has quit IRC22:39
*** baoli has joined #openstack-meeting-322:39
*** salv-orlando has quit IRC22:47
*** salv-orlando has joined #openstack-meeting-322:48
*** salv-orlando has quit IRC22:50
*** baoli has quit IRC22:53
*** stendulker has joined #openstack-meeting-322:56
*** sarob has joined #openstack-meeting-322:58
*** VW_ has quit IRC23:00
*** absubram has joined #openstack-meeting-323:00
*** stendulker has quit IRC23:09
*** sarob has quit IRC23:15
*** absubram has quit IRC23:21
*** mrda-away is now known as mrda23:21
*** sarob has joined #openstack-meeting-323:22
*** mattfarina has quit IRC23:22
*** reed_ has quit IRC23:23
*** emagana has quit IRC23:25
*** sarob has quit IRC23:26
*** amotoki has quit IRC23:29
*** yamamoto has joined #openstack-meeting-323:30
*** yamamoto_ has joined #openstack-meeting-323:31
*** yamamoto has quit IRC23:31
*** baoli has joined #openstack-meeting-323:32
*** smc7 has quit IRC23:35
*** seizadi has joined #openstack-meeting-323:36
*** seizadi has quit IRC23:37
*** seizadi1 has joined #openstack-meeting-323:37
*** seizadi1 has quit IRC23:41
*** TravT_ has quit IRC23:42
*** Sukhdev has joined #openstack-meeting-323:44
*** emw has quit IRC23:49
*** emw has joined #openstack-meeting-323:50
*** emilyw has joined #openstack-meeting-323:52
*** btully has quit IRC23:55
*** watanabe_isao has joined #openstack-meeting-323:55
*** emw has quit IRC23:56
*** emilyw has quit IRC23:56

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