Wednesday, 2015-04-29

*** peristeri has quit IRC00:00
*** melwitt has quit IRC00:03
*** wojdev has quit IRC00:07
*** nickchase has joined #openstack-meeting-300:09
*** nickchase has left #openstack-meeting-300:09
*** salv-orlando has quit IRC00:16
*** armax has joined #openstack-meeting-300:29
*** eghobo has joined #openstack-meeting-300:30
*** bknudson has quit IRC00:31
*** david-lyle has quit IRC00:32
*** shwetaap has joined #openstack-meeting-300:34
*** eghobo_ has joined #openstack-meeting-300:37
*** eghobo has quit IRC00:40
*** alexsyip has quit IRC00:56
*** kan_afk has left #openstack-meeting-301:04
*** emagana has joined #openstack-meeting-301:06
*** banix has joined #openstack-meeting-301:06
*** banix has quit IRC01:09
*** emagana has quit IRC01:10
*** emagana has joined #openstack-meeting-301:11
*** bpokorny has quit IRC01:12
*** salv-orlando has joined #openstack-meeting-301:17
*** david-lyle has joined #openstack-meeting-301:20
*** salv-orlando has quit IRC01:22
*** yamamoto has quit IRC01:24
*** yamamoto has joined #openstack-meeting-301:24
*** markvoelker has quit IRC01:36
*** marun has quit IRC01:38
*** zhenguo has joined #openstack-meeting-301:38
*** stanzgy has joined #openstack-meeting-301:40
*** s3wong has quit IRC01:46
*** banix has joined #openstack-meeting-301:47
*** yamahata has quit IRC01:48
*** mwagner_lap has quit IRC01:49
*** baoli has joined #openstack-meeting-301:49
*** mwang2_ has quit IRC01:52
*** baoli has quit IRC01:53
*** baoli has joined #openstack-meeting-301:53
*** xuhanp has joined #openstack-meeting-301:53
*** xuhanp_ has joined #openstack-meeting-301:53
*** yamamoto has quit IRC01:56
*** Networkn3rd has joined #openstack-meeting-301:56
*** shwetaap has quit IRC02:02
*** mwagner_lap has joined #openstack-meeting-302:06
*** VW_ has joined #openstack-meeting-302:07
*** baoli has quit IRC02:11
*** baoli has joined #openstack-meeting-302:12
*** Swami_ has quit IRC02:24
*** eghobo_ has quit IRC02:29
*** banix has quit IRC02:29
*** david-lyle has quit IRC02:30
*** david-lyle has joined #openstack-meeting-302:31
*** shwetaap has joined #openstack-meeting-302:35
*** david-lyle has quit IRC02:36
*** emagana has quit IRC02:40
*** markvoelker has joined #openstack-meeting-302:41
*** banix has joined #openstack-meeting-302:42
*** VW_ has quit IRC02:53
*** VW_ has joined #openstack-meeting-302:54
*** ilyashakhat has quit IRC03:14
*** salv-orlando has joined #openstack-meeting-303:14
*** Networkn3rd has quit IRC03:16
*** salv-orlando has quit IRC03:25
*** coolsvap|afk is now known as coolsvap03:27
*** yamahata has joined #openstack-meeting-303:27
*** banix has quit IRC03:28
*** david-lyle has joined #openstack-meeting-303:32
*** Swami has joined #openstack-meeting-303:33
*** ivar-laz_ has joined #openstack-meeting-303:34
*** baoli has quit IRC03:34
*** ivar-lazzaro has quit IRC03:38
*** ivar-laz_ has quit IRC03:38
*** egon has joined #openstack-meeting-303:52
*** Swami has quit IRC03:53
*** Swami has joined #openstack-meeting-303:56
*** shwetaap has quit IRC03:58
*** fallenpegasus has joined #openstack-meeting-303:59
*** shwetaap has joined #openstack-meeting-304:00
*** ivar-lazzaro has joined #openstack-meeting-304:01
*** eghobo has joined #openstack-meeting-304:01
*** armax has quit IRC04:09
*** btully has quit IRC04:11
*** Swami_ has joined #openstack-meeting-304:15
*** Swami has quit IRC04:18
*** VW_ has quit IRC04:18
*** stevemar has joined #openstack-meeting-304:19
*** rushiagr_away is now known as rushiagr04:21
*** mwagner_lap has quit IRC04:36
*** btully has joined #openstack-meeting-304:39
*** rushiagr is now known as rushiagr_away04:45
*** eghobo has quit IRC04:48
*** mwagner_lap has joined #openstack-meeting-304:52
*** nkrinner has joined #openstack-meeting-304:57
*** mrmartin has joined #openstack-meeting-305:05
*** fallenpegasus has quit IRC05:08
*** Nikolay_St has quit IRC05:09
*** salv-orlando has joined #openstack-meeting-305:15
*** xuhanp_ has quit IRC05:16
*** xuhanp has quit IRC05:16
*** yamamoto has joined #openstack-meeting-305:18
*** salv-orlando has quit IRC05:26
*** shwetaap has quit IRC05:27
*** eghobo has joined #openstack-meeting-305:33
*** eghobo_ has joined #openstack-meeting-305:36
*** yamamoto has quit IRC05:37
*** eghobo has quit IRC05:39
*** yamamoto has joined #openstack-meeting-305:40
*** mwagner_lap has quit IRC05:46
*** wojdev has joined #openstack-meeting-305:50
*** wojdev has quit IRC05:50
*** stevemar has quit IRC05:54
*** yamamoto has quit IRC05:54
*** mrunge has joined #openstack-meeting-305:54
*** yamamoto has joined #openstack-meeting-305:54
*** Longgeek has joined #openstack-meeting-306:03
*** mwagner_lap has joined #openstack-meeting-306:03
*** igordcard_ has quit IRC06:06
*** Longgeek has quit IRC06:08
*** yamamoto has quit IRC06:08
*** Swami has joined #openstack-meeting-306:13
*** jlvillal has quit IRC06:14
*** Swami_ has quit IRC06:14
*** igordcard_ has joined #openstack-meeting-306:14
*** jlvillal has joined #openstack-meeting-306:16
*** eghobo has joined #openstack-meeting-306:19
*** pkoniszewski has joined #openstack-meeting-306:19
*** eghobo_ has quit IRC06:21
*** xuhanp has joined #openstack-meeting-306:25
*** xuhanp_ has joined #openstack-meeting-306:25
*** salv-orlando has joined #openstack-meeting-306:34
*** Swami has quit IRC06:38
*** salv-orlando has quit IRC06:42
*** eghobo_ has joined #openstack-meeting-306:42
*** eghobo has quit IRC06:46
*** evgenyf has joined #openstack-meeting-306:46
*** fallenpegasus has joined #openstack-meeting-306:47
*** jcoufal has joined #openstack-meeting-306:49
*** eghobo has joined #openstack-meeting-306:49
*** eghobo_ has quit IRC06:51
*** Longgeek has joined #openstack-meeting-306:56
*** ajo has quit IRC07:01
*** Longgeek has quit IRC07:02
*** Longgeek has joined #openstack-meeting-307:06
*** sahid has joined #openstack-meeting-307:06
*** MaxV has joined #openstack-meeting-307:13
*** stanzgy has quit IRC07:13
*** stanzgy has joined #openstack-meeting-307:15
*** safchain has joined #openstack-meeting-307:17
*** xuhanp_ has quit IRC07:21
*** xuhanp has quit IRC07:21
*** btully has quit IRC07:26
*** jtomasek has joined #openstack-meeting-307:28
*** mwagner_lap has quit IRC07:28
*** scheuran has joined #openstack-meeting-307:39
*** iovadia has joined #openstack-meeting-307:43
*** mwagner_lap has joined #openstack-meeting-307:46
*** eghobo has quit IRC07:46
*** Nikolay_St has joined #openstack-meeting-307:49
*** ajo has joined #openstack-meeting-307:51
*** wojdev has joined #openstack-meeting-307:57
*** JeanBriceCombebi has joined #openstack-meeting-308:00
*** zz_ttrifonov is now known as ttrifonov08:02
*** Longgeek has quit IRC08:05
*** salv-orlando has joined #openstack-meeting-308:08
*** fallenpegasus has quit IRC08:22
*** ttrifonov is now known as zz_ttrifonov08:23
*** zz_ttrifonov is now known as ttrifonov08:25
*** yamahata has quit IRC08:25
*** ttrifonov is now known as zz_ttrifonov08:28
*** zz_ttrifonov is now known as ttrifonov08:30
*** zz_johnthetubagu is now known as johnthetubaguy08:36
*** johnthetubaguy is now known as zz_johnthetubagu08:44
*** zz_johnthetubagu is now known as johnthetubaguy08:45
*** JeanBriceCombebi has quit IRC08:47
*** ttrifonov is now known as zz_ttrifonov08:47
*** zz_ttrifonov is now known as ttrifonov08:50
*** ttrifonov is now known as zz_ttrifonov08:51
*** JeanBriceCombebi has joined #openstack-meeting-308:52
*** zz_ttrifonov is now known as ttrifonov08:54
*** mwagner_lap has quit IRC08:55
*** JeanBriceCombebi has quit IRC09:01
*** JeanBriceCombebi has joined #openstack-meeting-309:04
*** e0ne has joined #openstack-meeting-309:06
*** Longgeek has joined #openstack-meeting-309:06
*** e0ne is now known as e0ne_09:06
*** mwagner_lap has joined #openstack-meeting-309:11
*** egallen has joined #openstack-meeting-309:12
*** Longgeek has quit IRC09:12
*** Longgeek has joined #openstack-meeting-309:13
*** MaxV has quit IRC09:13
*** e0ne_ is now known as e0ne09:14
*** JeanBriceCombebi has quit IRC09:15
*** MaxV has joined #openstack-meeting-309:16
*** JeanBriceCombebi has joined #openstack-meeting-309:18
*** JeanBriceCombebi has quit IRC09:32
*** JeanBriceCombebi has joined #openstack-meeting-309:32
*** JeanBriceCombebi has quit IRC09:41
*** JeanBriceCombebi has joined #openstack-meeting-309:44
*** aswadr has joined #openstack-meeting-309:44
*** markmcclain has quit IRC09:49
*** reed has quit IRC09:56
*** markmcclain has joined #openstack-meeting-309:59
*** e0ne is now known as e0ne_10:03
*** e0ne_ is now known as e0ne10:05
*** mtreinish has quit IRC10:07
*** wojdev has quit IRC10:09
*** reed has joined #openstack-meeting-310:28
*** mwagner_lap has quit IRC10:41
*** wojdev has joined #openstack-meeting-310:50
*** stanzgy has quit IRC10:52
*** akrivoka has joined #openstack-meeting-310:57
*** mwagner_lap has joined #openstack-meeting-310:59
*** egallen has quit IRC11:10
*** JeanBriceCombebi has quit IRC11:21
*** igordcard has joined #openstack-meeting-311:23
*** overlayer has joined #openstack-meeting-311:23
*** e0ne is now known as e0ne_11:30
*** coolsvap is now known as coolsvap|afk11:33
*** overlayer has quit IRC11:34
*** igordcard has quit IRC11:34
*** irenab has joined #openstack-meeting-311:35
*** igordcard has joined #openstack-meeting-311:37
*** igordcard has quit IRC11:40
*** egallen has joined #openstack-meeting-311:42
*** baoli has joined #openstack-meeting-311:50
*** baoli has quit IRC11:53
*** baoli has joined #openstack-meeting-311:54
*** igordcard has joined #openstack-meeting-311:54
david-lyle#startmeeting Horizon11:57
openstackMeeting started Wed Apr 29 11:57:16 2015 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot.11:57
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.11:57
*** openstack changes topic to " (Meeting topic: Horizon)"11:57
openstackThe meeting name has been set to 'horizon'11:57
sambettsHi all o/11:57
*** bradjones has joined #openstack-meeting-311:59
*** doug-fish has joined #openstack-meeting-312:00
david-lylewill let people trickle12:00
david-lylein12:00
*** robcresswell has joined #openstack-meeting-312:01
david-lylealright, let get going12:02
mrungehey o/12:03
akrivokahi12:03
robcresswello/12:03
bradjones\o12:03
doug-fishhello12:03
david-lyle#topic General12:04
*** openstack changes topic to "General (Meeting topic: Horizon)"12:04
*** scheuran has quit IRC12:04
david-lyleSo as most saw, I added doug-fish, robcresswell and TravT to Horizon core, welcome and thank you12:04
doug-fishthank you! I'm happy to be part of the team.12:05
*** igordcard has quit IRC12:05
mrungedavid-lyle, I was a bit astonished, as in the past current cores were asked to vote for this kind of change12:05
*** bauzas is now known as bauzas_notme12:05
david-lyleI forewent the usual informal vote on the mailing list to help reduce the overall number of emails, I reached out to as many cores as I could ping12:06
*** bauzas_notme is now known as bauzas12:06
*** igordcard has joined #openstack-meeting-312:06
mrungeah, I see12:06
mrungeseriously, new cores, you are more than welcome from my side12:06
robcresswellThanks :)12:07
david-lyleI think these additions are overdue, but I was trying to create a lot of turmoil at the end of the release cycle12:07
david-lylenot to create12:07
david-lyleI wanted to save turmoil for now :)12:08
*** mrmartin has quit IRC12:08
doug-fishwell done!12:08
david-lyleWe published RC-2 for Horizon last week12:09
david-lyleand I haven't seen an issue that would block it being used as the final release12:09
mrungedo we expect a rc3?12:09
robcresswelldavid-lyle: Is this not a blocker? https://bugs.launchpad.net/horizon/+bug/144728812:09
openstackLaunchpad bug 1447288 in OpenStack Dashboard (Horizon) "create volume from snapshot using horizon error" [Critical,In progress] - Assigned to Masco Kaliyamoorthy (masco)12:09
mrungedavid-lyle, I was able to reproduce the nova-network issue in launch instance12:09
doug-fishrobcresswell: yeah, I was going to bring up the same bug12:10
david-lylerobcresswell: that one is marked critical, but I'm not sure I would classify it that way12:10
david-lyleto be honest, I'm not sure it was working in the last 6-12 months12:10
david-lylelooking at the changes in the appropriate files12:11
david-lyleWe can fix on master and backport12:11
doug-fishisn't the problem that volumes created from snapshots don't have the expected contents?12:11
mrungeimho this is not fixed here: https://bugs.launchpad.net/horizon/+bug/144442112:11
openstackLaunchpad bug 1444421 in OpenStack Dashboard (Horizon) kilo "Launch instance fails with nova network" [High,In progress] - Assigned to David Lyle (david-lyle)12:11
david-lylemrunge: sorry reading through comments12:13
david-lyledo you have a trace to add?12:14
mrungedavid-lyle, I proposed a fix12:14
mrungehttps://review.openstack.org/17816312:14
mrungewith that fix, the issue doesn't happen any more12:14
mrungeat least, one can create instances with nova network enabled12:17
david-lylehmm, that might require an rc312:18
mrungeis a rc3 really required?12:19
david-lyleto get that fix into kilo it would be12:19
mrungeah, ok12:19
david-lylenot being able to launch an instance on nova-net seems like a huge regression12:19
david-lyleI'm not sure why that step is even being called12:20
mrungeyes, same here12:20
david-lyleis it network profile stuff?12:20
mrungethis method is called from launch instance wizard initialization step12:21
mrungehttps://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/instances/workflows/create_instance.py#L73112:22
* mrunge assumes, permission check is wrong here12:22
mrungehttps://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/instances/workflows/create_instance.py#L72712:22
mrungeas this issue only occurs, when you have admin credentials12:23
*** igordcard has quit IRC12:25
*** igordcard has joined #openstack-meeting-312:25
david-lyleso you have a network service in your catalog for admin for some reason12:25
*** ivar-lazzaro has quit IRC12:25
mrungeno I don't12:26
*** e0ne_ is now known as e0ne12:26
mrungeif I'm listing keystone endpoints (even with admin credentials), I don't have a network service listed12:26
*** ivar-lazzaro has joined #openstack-meeting-312:28
david-lylehmm, we're calling a templatetag for the permissions check for some reason12:28
david-lylebut that hasn't changed since 201212:29
mrungeinteresting12:29
*** JeanBriceCombebi has joined #openstack-meeting-312:30
david-lyleand has_perms in d-o-a hasn't changed since 201312:30
david-lylenot sure what changed here12:31
mrungehmm, then I'll double check again here12:31
mrungeand since nobody else could reproduce this12:31
mrunge...12:31
david-lyleI set up devstack with nova-net and couldn't reproduce the first time either, but I'd like to know why you're seeing it12:32
david-lyleif you can reconfirm, I'll set up the test env again and try again12:32
david-lylereally don't want to ship with that broken12:32
david-lyleok12:32
mrungemy backend is juno, but that shoulnd't harm anyways12:33
david-lyleshouldn't think so12:33
mrungethanks12:33
david-lylethat was the live bug triage portion of the meeting :)12:33
mrungeuhm, I have something else to discuss12:34
david-lylesure12:34
mrungewhat happens with old bugs in launch instance workflow?12:34
mrungei.e. if I discover an issue in old laucnh instance in juno?12:34
mrungefixes are supposed to be in kilo or liberty first, then to be backported12:34
david-lylemrunge: until we're comfortable making the angular workflow the default, the old workflow is still the default12:35
mrungeok, no change yet12:35
doug-fishI'd say we need to fix in master until we actually remove the old workflow and not allow it as an option12:35
david-lyleI don't see us removing that code in L even if we switch12:35
mrungebut sooner or later, that'd be the case12:35
david-lyleif we do remove the old workflow, we would need to patch the stable branches directly12:36
mrungeyes, makes sense12:36
david-lylerather than cherry pick12:36
*** shwetaap has joined #openstack-meeting-312:36
mrungeok, thanks!12:37
david-lylesure12:37
david-lyledoug-fish: the cinder bug is good for a backport to the first stable follow on to Kilo12:37
doug-fishdavid-lyle: yes, agreed12:37
david-lyleit's broken for sure, but at this point it's not destructive and I can't really determine that it's a regression12:38
david-lylefinal release is tomorrow12:38
david-lyleso the bar is pretty high12:38
doug-fishyeah understood12:38
david-lylethen it's all liberty all the time12:38
doug-fishit's important; but getting it in the first fix pack seems appropriate12:39
doug-fish:-)12:39
david-lylemore common items12:39
david-lylereminder that TC voting closes later today, eligible voters should have received an email12:39
david-lylethis is your chance to pick over half of the TC membership for a year12:40
david-lyle#topic Summit planning12:42
*** openstack changes topic to "Summit planning (Meeting topic: Horizon)"12:42
david-lyle#link https://etherpad.openstack.org/p/horizon-liberty-summit12:42
*** lifeless has quit IRC12:43
david-lylewe need to start voting on topics12:43
david-lyletype and overall interest12:43
david-lylecopied from the top of that etherpad12:43
*** MaxV has quit IRC12:44
david-lyle3 Fishbowls (Large crowd.)12:44
david-lyle8 Working sessions (Small room. 40 minutes)12:44
david-lyle2 Half day contributor meetups (All day Friday)12:44
david-lyleso we should have plenty of time12:44
david-lylehelp prioritize the items12:44
david-lyleNext week we would like to have the schedule set12:45
*** shwetaap1 has joined #openstack-meeting-312:45
david-lyleso people have time to prepare12:45
robcresswellI'd really like to get some of the Angular sessions in. This is a good time to introduce people to the process, existing reusable components, and take away that "fear factor" from a new approach.12:45
david-lyleand attendees can plan their schedule12:45
david-lylerobcresswell: +1, maybe one working is intro to angular dev12:45
mrungeyes, that makes sense12:46
robcresswellThats what me and tqtran are planning out. I'm working on docs now too; plan to have them merged by summit.12:46
david-lylerobcresswell: is that on the etherpad?12:46
mrungethere are new folks coming in, asking the same questions again and again...12:46
david-lyleI see it on the etherpad12:47
robcresswellJust under tqtran, at the bottom12:47
david-lylelin3 4912:47
robcresswellOr under TravT. There is some duplication there.12:47
david-lyleah, Thai has more details12:47
david-lylealways is12:47
david-lyle:)12:47
david-lyleafter I write release notes today, I'll try to pare down the duplication at least12:48
*** shwetaap has quit IRC12:48
robcresswellBut yes, plan is to get solid docs up, I'm aiming for first pass on Thursday, then the team will iterate over. At summit, if there is session time available, we will talk people through the process, explain docs, answer questions.12:48
robcresswellHopefully move away from this sub-team idea, and introduce wider community to the angular process.12:49
david-lylerobcresswell: agreed12:49
*** MaxV has joined #openstack-meeting-312:50
david-lyleI will say, we needed concrete progress this release, lest we go 18 months with nothing tangible from the efforts12:50
david-lylebut we needed the effort to broaden12:51
david-lylehopefully we've learned from the process12:51
david-lyledoug-fish: did you mark that HMT and Domain tokens were resolved in Kilo?12:52
doug-fishhmm12:52
david-lyleon the etherpad?12:52
doug-fishI did12:52
*** VW_ has joined #openstack-meeting-312:52
doug-fishmaybe that was an overstatement?12:52
david-lyletell me how that turned out12:52
david-lyle:)12:52
david-lylethose two are still moving targets12:52
doug-fishI've focused the resolved parts a bit more12:53
david-lylebetter12:53
david-lyleglass half full12:53
david-lyleok, running out of time, vote on sessions you would like to see12:53
david-lyle#Open Discussion12:53
doug-fishIt's kind of hard to vote right now12:53
doug-fishthere are overlaps12:53
david-lyle#topic Open Discussion12:53
*** openstack changes topic to "Open Discussion (Meeting topic: Horizon)"12:53
robcresswellmrunge: I agree with your comment on etherpad. (I think it is yours). Plan is to get docs merged into repo, then will update relevant contributing docs, wikis etc.12:54
david-lyledoug-fish: sure, will work on cleaning up12:54
mrungerobcresswell, yes, it was mine12:54
mrungedoug-fish, go ahead, condense topics12:54
mrungemaking easier to vote for topics12:54
david-lyleoh yeah12:54
*** e0ne is now known as e0ne_12:54
david-lylefeel free12:55
david-lylenothing sacred12:55
david-lyletry not to delete, if something seems off-topic or low priority just move to the bottom of the page12:55
doug-fishI'm cutting + pasting to try to bring similar discussions together12:56
robcresswellSeems like a good time to ask. Are there any rules/guidelines/advice for new cores, to make sure we're following the correct process?12:56
*** asahlin_afk is now known as asahlin12:56
doug-fishrules?!12:57
robcresswellhaha12:57
david-lyleI typically send an email12:57
david-lyleI will do that too12:57
robcresswellCool. Thankyou.12:57
david-lyleI haven't done the access rights bits yet12:58
*** VW_ has quit IRC12:58
david-lyleso I'm buying time12:58
david-lyleok, time's up. Thanks everyone for a great Kilo release. Looks like RC-2 will stick as final. Lots of hard work and reviews made this happen.12:58
david-lyle#endmeeting12:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"12:59
openstackMeeting ended Wed Apr 29 12:59:01 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-04-29-11.57.html12:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-04-29-11.57.txt12:59
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-04-29-11.57.log.html12:59
mrungethanks everyone!12:59
*** moshele has joined #openstack-meeting-312:59
sambetts\o12:59
*** robcresswell has left #openstack-meeting-312:59
*** lblanchard has joined #openstack-meeting-313:00
*** ir2ivps7 has quit IRC13:01
*** julim has joined #openstack-meeting-313:05
*** e0ne_ is now known as e0ne13:06
*** julim has quit IRC13:06
*** bknudson has joined #openstack-meeting-313:06
*** julim has joined #openstack-meeting-313:08
*** jckasper has joined #openstack-meeting-313:13
*** julim has quit IRC13:18
*** mattfarina has joined #openstack-meeting-313:23
*** mattfarina has quit IRC13:24
*** qwazerty is now known as Qwazerty13:24
*** peristeri has joined #openstack-meeting-313:25
*** vhoward has joined #openstack-meeting-313:26
*** matrohon has joined #openstack-meeting-313:30
*** ir2ivps7 has joined #openstack-meeting-313:31
*** wojdev has quit IRC13:33
*** e0ne is now known as e0ne_13:38
*** VW_ has joined #openstack-meeting-313:38
*** lifeless has joined #openstack-meeting-313:38
*** e0ne_ is now known as e0ne13:39
*** MaxV has quit IRC13:39
*** VW_ has quit IRC13:39
*** VW_ has joined #openstack-meeting-313:40
*** wojdev has joined #openstack-meeting-313:42
*** gsagie has joined #openstack-meeting-313:47
*** nmj3e has joined #openstack-meeting-313:53
*** mtreinish has joined #openstack-meeting-313:54
*** wojdev has quit IRC13:55
*** roeyc has joined #openstack-meeting-313:55
*** wojdev has joined #openstack-meeting-313:55
*** JamesR has joined #openstack-meeting-313:58
*** vikram__ has joined #openstack-meeting-313:58
*** sadasu has joined #openstack-meeting-314:00
ajohi :)14:01
vikram__hi14:01
ajo#startmeeting neutron_qos14:01
openstackMeeting started Wed Apr 29 14:01:30 2015 UTC and is due to finish in 60 minutes.  The chair is ajo. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: neutron_qos)"14:01
openstackThe meeting name has been set to 'neutron_qos'14:01
sadasuHello!14:01
*** zz_jgrimm is now known as jgrimm14:01
gsagiehi14:01
ajo#topic Announcements14:01
ajo#link https://wiki.openstack.org/wiki/Meetings/NeutronQoS14:01
*** openstack changes topic to "Announcements (Meeting topic: neutron_qos)"14:01
ajo#link https://etherpad.openstack.org/p/neutron-liberty-qos-code-sprint14:01
ajo:-) I wanted to spam as usual about the sprint, if anybody want to join and didn't sign up yet, do it :)14:02
ajo#topic High level api/cmdline overview, to share with operators14:02
ajo#link https://etherpad.openstack.org/p/neutron-qos-api-preview14:02
*** openstack changes topic to "High level api/cmdline overview, to share with operators (Meeting topic: neutron_qos)"14:02
*** garyk has joined #openstack-meeting-314:02
garykhi14:02
moshelehi14:02
irenabhi14:02
ajohi garyk, sorry, may be I was running too much :)14:02
ajoI just posted: https://etherpad.openstack.org/p/neutron-qos-api-preview14:03
gsagiejust a suggestion as i wrote in message, make the unit a field and then "max", "max_burst"...14:03
gsagieand unit can be Kb, Mb...14:03
ajogsagie, yes I thought of it, but I believe we shall not complicate ourselves adding unit management14:03
sc68calhi14:03
garykajo: is that egress or ingress or both directions?14:03
ajoif we pick one , it's uniform across all14:04
vhowardhey ajo14:04
ajogaryk, the current definition is egress,14:04
ajobut we could extend it in the future, as we plan to do with protocol / port matching, etc14:04
*** marun has joined #openstack-meeting-314:04
garykok, thanks, any reason why we do not allow for igress?14:04
*** rushiagr_away has quit IRC14:05
ajogaryk, I didn't have time to experiment with the ref implementation to provide ingress, but we could extend to support it14:05
*** alexpilotti has joined #openstack-meeting-314:05
*** mtreinish has quit IRC14:05
garykajo: ok, thanks14:05
garyksorry for jumping in very late… but does not harm to ask14:05
-openstackstatus- NOTICE: gerrit has been restarted to clear a stuck events queue. any change events between 13:29-14:05 utc should be rechecked or have their approval votes reapplied to trigger jobs14:05
ajoI guess it's just basically adding another queue, and moving traffic going to the mac into the queue14:05
irenabajo: shall we have direction as part of API?14:05
ajoirenab, may be we should consider that field in this first iteration14:06
ajoto make it clear14:06
ajoI believe it's a good suggestion14:06
vikram__+114:06
ajo#action ajo add direction field to QoSRules (ingress/egress)14:06
garykajo: irenab: one more question (which maybe i missed) is this per port per network?14:07
ajogaryk per port14:07
garykok, thanks14:07
ajogaryk, you could attach a policy to a network, but that means all ports in that network will be applied the policy14:07
ajono consideration for agregated bandwidth at this time14:07
irenabper network qos will just be applied on each port that does not have its own qos policy associated14:07
garykwould it be possible to define it globally on the network and then each port can inherit the global policy?14:07
garykirenab: ok, thanks, that answers the question :)14:07
vikram__i have a doubt..14:07
ajogaryk, that's the plan, but bandwidth is accounted locally to each port.14:08
garykok14:08
*** btully has joined #openstack-meeting-314:08
vikram__if ratelimiting for network-100mbps and for port=200mbps which will be considered14:08
*** cbits has joined #openstack-meeting-314:08
ajogaryk, may be at a later time we can come out with a way to have "agregated network bw limits" but not sure how to do it on the low level I guess is a complicated topic14:08
sc68calport overrides network policy14:08
garykajo: ok14:09
ajothe spec currently says, port config overrides network config14:09
vikram__but overall n/w is configured to support only 10014:09
vikram__is this a misconfiguration?14:09
vikram__do we need to handle14:09
sc68calvikram__: so every port on the network except that port gets 10014:09
garykvikram__: i think that is per virtual port14:09
sc68calthe port with the 200 gets 20014:09
*** sigmavirus24_awa is now known as sigmavirus2414:09
ajoIn some cases we could think of blending rules...14:10
ajoif that makes sense14:10
irenabI think the idea of per network setting is some sort of ‘use network setting as port default setting if not specified otherwise'14:10
ajoI considered it at the start, but I had negative comments in the spec14:10
ajofor the bw limiting case, it's easy to do, just get the min of all parameters14:10
*** pkoniszewski has quit IRC14:11
ajofor other cases, for example dscp marking, it couldn't be blended14:11
ajowhat do you think about blending policies?14:11
vikram__ok14:11
ajoI'm ok with port setting overrides net setiting14:11
ajosetting14:11
ajoany feedback related to blending?14:12
ajoif anybody thinks blending is important, please think about use cases, and how to handle conflicts in other rule types14:13
ajook, let's move on14:13
ajo#topic Update on latest changes to models14:13
*** openstack changes topic to "Update on latest changes to models (Meeting topic: neutron_qos)"14:13
ajoI have modified the models to be14:13
ajoQoSPolicy and QoSRule14:13
ajobefore they were QoSProfile and QoSPolicy14:13
ajoI believe this is more similar to the language of security groups14:14
ajoand thus be more usable because we're sharing the concepts14:14
vikram__easy to understand as well:)14:14
ajo:-)14:14
irenabajo: sound fine14:14
sc68calajo: sounds good14:14
gsagiesounds good to me14:14
*** yamahata has joined #openstack-meeting-314:14
ajothanks :)14:14
ajo#topic Ideas for generic RPC mechanisms14:14
*** openstack changes topic to "Ideas for generic RPC mechanisms (Meeting topic: neutron_qos)"14:15
ajook, this is still an inmature idea14:15
ajobased on the ML feedback on the topic,14:15
ajowe keep adding more RPC messages /calls from to/from agents with every new thing14:15
*** rmschn has joined #openstack-meeting-314:15
garykajo: it may be too early to jump into implementation details if the api is still in discussion14:15
ajowhat if we were able to have a common interface to send updates on different types of objects14:15
ajogaryk, you're probably right14:16
*** rushiagr_away has joined #openstack-meeting-314:16
ajoI just wanted to drop the idea to let others think about it and see if it makes some sense14:16
sc68calajo: I think I see where you are going, I agree with garyk, it's big enough to warrant its own spec14:16
garykajo: i think that it would also be a driver implementation detail14:16
ajosc68cal, that's right,14:16
sc68calajo: but I see the merit in it, for sure!14:16
gsagieajo: are we considering using a no-agent approach or thats currently off topic?14:17
*** zhenguo has quit IRC14:17
ajobasically I was thinking of something similar to callbacks but via agents/rpc,14:17
ajobut14:17
ajolet's move on14:17
irenabajo:  would this be part of the ref impementation spec discussion?14:17
*** wojdev has quit IRC14:18
ajoirenab, I guess if we propose such a thing, as sc68cal was saying it deserves it's own spec14:18
vikram__ajo: can you share the details about ur idea14:18
ajobut if we're going to add new rpc methods and calls... well.. may be it's a good moment14:18
ajovikram__, this is just the high level overview, didn't have more time to look at it14:18
irenabjust to undestand the way to proceed, we have API/Data Model spec, with no real backend implementation14:19
vikram__ok14:19
sc68caljust have to be careful about how many dependencies we insert before we start the actual work on QoS, otherwise we'll be in Zeta release ;)14:19
irenabthen there will be ref implementation spec (OVS based, I guess)14:19
vikram__:-)14:19
ajosc68cal, I totally agree on that, I was just trying to address the concern of "we keep adding more rpc calls for every single feature" :)14:19
ajoyes, I guess it's time to move onto that topic14:20
irenabso you think there should be another spec? or just some work to be done related to one of these two specs?14:20
ajo#topic inter-related specs which should happen after the API14:20
*** openstack changes topic to "inter-related specs which should happen after the API (Meeting topic: neutron_qos)"14:20
garykajo: if this is bundeled in as part of a neutron port then we do not need additional calls. just the payload needs to change14:20
ajogaryk, not exactly,14:20
garykwhy?14:20
ajogaryk, this is similar to the security groups14:20
sc68calgaryk: still need RPC for fetching policy stuff14:21
ajogaryk, for example, if a policy is updated, we need the changes applied to the ports14:21
sc68calunless we're going to pack *more* data onto rabbitmq14:21
irenabI thought we agreed not to talk about implementation details yet :-)14:21
ajo'':D14:21
garykok, now i understand. i was just thinking of the port creation :)14:21
ajook, let's talk about implementation in the future :)14:21
ajoirenab +114:21
garykfew dumb questions14:22
ajook, specs we need for sure...14:22
*** wojdev has joined #openstack-meeting-314:22
ajoml2-ovs ml2-sriov, ml2-lb implementations14:22
garykwill the api be in the neutron code base or an external project?14:22
ajogaryk, that's still on debate,14:22
ajoirenab, and sc68cal believe that's going to be faster,14:22
ajoif we go the service-plugin way, that's probably an option14:23
garykas an external project?14:23
ajogaryk, what do you think about the topic?14:23
irenabsimilar to advanced services14:23
vikram__+114:23
ajogaryk, my opinion is that it's something which should be available to all plugin implementors...14:23
sc68calRegardless - we're going to need a patch that adds an extension in neutron/extensions14:23
garyki feelt hat it is part of the core14:23
sc68calor a shim14:23
*** akrivoka has left #openstack-meeting-314:23
ajoif it's well tested in coordination with neutron core stuff, I'm ok14:24
garykbut being able to develop out of tree is certainly a lot faster14:24
garykthe glue is what concerns me. i am not sure about the service hook14:24
ajogaryk it's my feeling also that this is part of the core, as we're defining port & net properties14:24
garykthat is more something that uses the ports etcs14:24
ajogaryk, that's my feeling too14:24
*** nkrinner has quit IRC14:24
garyki also think that the sec group model is very messy and in retrospect we should have done that differently14:25
ajogaryk, but I'm not sure we have better mechanisms to decouple the code af this moment14:25
garykagree14:25
garykwill there be a session at the summit so that maybe we can bash this through14:25
irenabI think its more DB Mixin versus Service plugin discussion, not totally independent service discussion14:25
ajogaryk, if we find a better way we can follow that path14:25
garykok14:25
*** asrangne has joined #openstack-meeting-314:26
ajogaryk, I'm still trying to understand the internals of neutron at this level so I'll be able to provide any beter idea, right now... I'm not able :D14:26
sadasuthis is an area where a design session at the summit could help?14:26
ajobut I agree, it feels like it's not a service making use of ports, it's just the best way to decouple we have now14:26
ajosadasu. could be,14:26
irenabajo: +114:27
sc68calajo: I can teach you the ways of the force ;)14:27
ajowe have a slot for QoS, but probably such topic would take a whole session :)14:27
ajomestery ^14:27
garyki am not familiar enough with the services to be able to have an opinion here. i just know that they create and delete ports.14:27
mesteryajo: ++14:27
garykhere we need to be part of the port creation (and update)14:27
sadasuajo: agree with your service dilemma14:28
ajoI guess the idea with the service is to register for the port creation/update callbacks, being able to notify where necessary..14:28
*** aswadr has quit IRC14:28
irenabsorry, have to leave. Will catch up later14:28
ajogaryk, sadasu , please feel free to add ideas to the ML Thread bout the QoS service plugin or not  ;)14:28
ajobout->about :)14:29
ajook, so14:29
ajoabout specs14:29
ajoor devref's ;)14:29
sc68cal;)14:29
ajowe may need to define how we're going to do it in the low level14:29
garykajo: will do14:29
ajo-ovs is clear to me14:29
ajoI think moshele will take care of -sriov14:30
sadasuajo: will do, have a bit of catching up to do regarding what has happened in the ML14:30
ajoanybody for -lb?14:30
garykwhat is -lb?14:30
ajolinux bridge :)14:30
garykthat is so 80's14:30
garyknew black is ovn14:30
mosheleajo: yes I will take sriov14:30
vikram__i can take up14:30
ajo:) yeah, but in previous iterations people had an interest on QoS/LB support :)14:30
garykthen again retro is in14:30
ajogaryk +114:31
ajo:D14:31
*** julim has joined #openstack-meeting-314:31
ajoI guess, -OVN work will come later in time when they have a working implementation14:32
vikram__ajo: linux bridge i can take up14:32
ajovikram__, that would be nice14:32
ajovikram__, I was planning to use ovs  queues with htb, which is what ovs supports14:32
ajonot sure what was the plan for LB, or what's the best plan14:33
vikram__ok. I used linux bridge long back need to refresh :D14:33
gsagieyou can leverage iptables for the rate limit14:33
gsagiein linux bridge i believe14:33
ajoI was planing to take on the -ovs low levels, but help is accepted14:34
ajotalking of which... gsagie was proposing to try an agent-less approach to do the QoS14:34
ajovia ovsdb interface14:34
vikram__gsagie: +114:34
gsagieheh no comments sounds bad... ;)14:35
ajo:-)14:35
ajogsagie, I believe it's better if we have the same approach in the different levels instead of mixing :)14:35
* sc68cal hopes he can assist ajo on the ovs low levels14:35
vikram__agent-less? what's that..14:35
ajoalso it would require good coordination with the current ovs-agent :)14:35
gsagieajo: not sure what you mean different levels, i believe some backends will implement this agentless as well14:36
ajogsagie, may be it's where OVN is going to do better than the current ovs implementation :)14:36
ajotrue gsagie , but I mean, for ml2-ovs we would be mixing14:36
ajofor ml2-ovn, probably that's the way to go14:36
gsagienp14:37
ajovikram__, agentless means you control the ovsdb + openflow rules from your neutron-server14:37
*** JeanBriceCombebi has quit IRC14:37
ajoinstead of sending rpc commands to an agent14:37
vikram__ok14:37
gsagiei can probably provide help as well for the ovs and maybe also the linux bridge if needed14:38
ajogsagie, am I correct?14:38
ajogsagie, thanks a lot14:38
gsagiei havent looked at the QoS settings, but i believe its only with OVSDB, but yeah thats the concept14:38
ajogsagie, it could involve some rules if we want to control ingress too14:39
ajofor egres it's just attaching a queue to the port14:39
ajoand of course, it requires some rules to do the same with different types of traffic14:39
ajook, to sumarize14:40
ajo#action vikram__ will take care of the ml2-linuxbridge implementation14:40
ajo#action moshele will take care of the ml2-sriov implementation14:40
ajo#action ajo will take care of the ml2-ovs implementation, gsagie and sc68cal offer help14:41
ajoalso gsagie you offered help to vikram__ regarding linux bridge14:41
vikram__What all QoSPolicy we will be implementing at the first go now?14:41
ajoratecontrol14:41
ajobut, with the new more open RFE process14:41
ajowe could propose other types as we finish ratecontrol14:42
vikram__ok14:42
ajoI hope that goes forward ;) mestery++14:42
ajook , we had a conflicting proposal so far (But this is looking into the future of supported types)14:43
*** wznoinsk has joined #openstack-meeting-314:43
ajoI'd like to comment now at least, since we have time14:43
ajo#topic conflicting type proposals14:43
*** openstack changes topic to "conflicting type proposals (Meeting topic: neutron_qos)"14:43
ajovikram__, I believe it was you, who proposed to use IPv6 flow labels to put QoS levels, right?14:43
vikram__yes14:43
ajothere's some RFC about using IPv6 flow labels for QoS, do you have the reference?14:44
ajoThere are other RFCs proposing ot use the flow labels for tenant isolation in virtual networks14:44
vikram__i have can send after the meeting14:44
ajoianwells was proposing that ... let me look for it14:44
*** mtreinish has joined #openstack-meeting-314:45
vikram__https://www.ietf.org/rfc/rfc3697.txt14:46
ajo#link https://etherpad.openstack.org/p/IPv6Networks14:46
sc68calyes but he was using them for tenant isolation14:46
ajo#link https://www.ietf.org/rfc/rfc3697.txt14:46
ajo#link https://tools.ietf.org/html/rfc643714:47
sc68calMy concern about using packet headers is contention over how they are used, and if we are adding new meanings14:47
ajocorrect sc68cal , this is why I think it's conflicting14:47
*** banix has joined #openstack-meeting-314:47
vikram__yes14:47
ajoyes, I think we can decide at a later time,14:47
ajobased on the status of the different RFCs14:48
ajoI just wanted to raise the issue so you're able to discuss with the right people14:48
ajovikram__, if you'll be able to come to the Summit, I can put you in contact with Ian14:48
ajo#topic free discussion14:49
*** openstack changes topic to "free discussion (Meeting topic: neutron_qos)"14:49
vikram__Thanks. I am travelling14:49
*** alexpilotti has quit IRC14:49
ajook, something important you believe we should talk about?14:49
ajoor ideas for the next agenda?14:49
vikram__how about packet priority marking and ecn14:49
ajovikram__, I believe we can discuss those in the future14:49
*** mtreinish has quit IRC14:49
ajowhen we have the basic building blocks14:49
ajoit's written in the current spec14:50
ajoas future ideas14:50
*** bradjones has quit IRC14:50
*** rmschn has quit IRC14:52
ajoA comment I had from irena as to standarize the parameters dict in command line14:52
ajoas some other cmdline commands do14:52
ajoI need to look into that14:52
*** vikram___ has joined #openstack-meeting-314:52
ajoah, and I was thinking14:52
ajoif it made sense to have a low level "qos_driver"14:52
ajoas we have for the "firewall_driver" in security groups14:53
ajosc68cal, what do you think about such thing ?14:53
*** pkoniszewski has joined #openstack-meeting-314:53
*** roeyc has quit IRC14:53
*** garyk has quit IRC14:53
ajofor example, in the OVSHybrid thing, we could use lb or ovs to do QoS14:53
*** roeyc has joined #openstack-meeting-314:53
ajoso.. having some sort of modular driver would help there14:53
*** vikram__ has quit IRC14:54
sc68calajo: yeah my old code had a abstract driver class, that the dscp driver inherited from14:54
ajoif one works better than the other, people just switch14:54
*** vikram___ has quit IRC14:54
ajosc68cal, ok, that sounds like we thought the same way14:54
*** tteggel_ has quit IRC14:54
*** rmschn has joined #openstack-meeting-314:55
sc68calajo: https://github.com/netoisstools/neutron/tree/comcast_milestone_proposed/neutron/services/qos/drivers14:55
*** garyk has joined #openstack-meeting-314:55
*** vikram__ has joined #openstack-meeting-314:55
ajosc68cal, exactly14:55
*** emagana has joined #openstack-meeting-314:55
ajo#link https://github.com/netoisstools/neutron/tree/comcast_milestone_proposed/neutron/services/qos/drivers14:56
*** tteggel has joined #openstack-meeting-314:56
ajothis way, if this is finally developed as a service, we can keep the drive implementation at the same place14:56
ajoand extend the agent in a modular way14:56
ajovia the same interface14:56
ajook, anything else, or shall we end meeting? :)14:56
*** garyk has quit IRC14:57
*** roeyc has quit IRC14:57
*** roeyc has joined #openstack-meeting-314:57
ajo#endmeeting14:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:57
openstackMeeting ended Wed Apr 29 14:57:52 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-04-29-14.01.html14:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-04-29-14.01.txt14:57
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-04-29-14.01.log.html14:57
*** sirushti has left #openstack-meeting-314:58
*** roeyc has quit IRC14:58
ajothanks gsagie , vikram__ , garyk, irenab , moshele , sadasu14:58
ajothanks sc68cal  ;)14:58
*** roeyc has joined #openstack-meeting-314:58
vikram__bye14:58
ajoI'm sure I'm forgetting peopel :D14:58
sadasuthank you all!14:59
*** nmj3e has quit IRC14:59
rmschntis ok.. they are just lurking like me. :)14:59
gsagiethanks ajo!14:59
rmschnthx for running the show. appreciated.15:00
*** nfedotov has joined #openstack-meeting-315:00
*** garyk has joined #openstack-meeting-315:01
*** nelsnelson has joined #openstack-meeting-315:02
ajothanks rmschn  ;D15:02
*** Networkn3rd has joined #openstack-meeting-315:03
*** peristeri has quit IRC15:04
*** JamesR has quit IRC15:04
*** vikram__ has left #openstack-meeting-315:05
*** iben__ has joined #openstack-meeting-315:05
rmschndefinitely.. hoping to put my mgt hat down a bit and drop back into dev mode some :)15:05
rmschnlater15:05
*** sadasu has quit IRC15:05
*** alexpilotti has joined #openstack-meeting-315:11
*** gsagie has left #openstack-meeting-315:14
*** wznoinsk_ has joined #openstack-meeting-315:14
*** rmschn has quit IRC15:16
*** banix has quit IRC15:16
*** wznoinsk__ has joined #openstack-meeting-315:18
*** jckasper has quit IRC15:22
*** carl_baldwin has joined #openstack-meeting-315:22
*** jckasper has joined #openstack-meeting-315:23
*** Nikolay_St has quit IRC15:23
*** wznoinsk has quit IRC15:23
*** wznoinsk__ has quit IRC15:24
*** wznoinsk_ is now known as wznoinsk15:24
*** banix has joined #openstack-meeting-315:24
*** bpokorny has joined #openstack-meeting-315:25
*** jckasper has quit IRC15:27
*** jckasper has joined #openstack-meeting-315:27
*** moshele has quit IRC15:28
*** evgenyf has quit IRC15:32
*** peristeri has joined #openstack-meeting-315:33
*** VW__ has joined #openstack-meeting-315:36
*** moshele has joined #openstack-meeting-315:37
*** VW_ has quit IRC15:37
*** VW__ has quit IRC15:41
*** stevemar has joined #openstack-meeting-315:42
*** julim has quit IRC15:43
*** Piet has joined #openstack-meeting-315:44
*** armax has joined #openstack-meeting-315:45
*** jcoufal has quit IRC15:45
*** rushiagr_away is now known as rushiagr15:46
*** garyk1 has joined #openstack-meeting-315:48
*** igordcard has quit IRC15:48
*** garyk has quit IRC15:50
*** ttrifonov is now known as zz_ttrifonov15:52
*** asrangne has quit IRC15:53
*** Sukhdev has joined #openstack-meeting-315:55
*** jckasper has quit IRC15:56
*** lblanchard has quit IRC15:57
*** banix has quit IRC15:57
*** jckasper has joined #openstack-meeting-315:59
*** shwetaap1 has quit IRC16:01
*** igordcard has joined #openstack-meeting-316:02
*** shwetaap has joined #openstack-meeting-316:03
*** wojdev has quit IRC16:04
*** VW_ has joined #openstack-meeting-316:04
*** igordcard has quit IRC16:05
*** sarob has joined #openstack-meeting-316:06
*** eghobo has joined #openstack-meeting-316:06
*** wojdev has joined #openstack-meeting-316:06
*** jtomasek has quit IRC16:10
*** moshele has quit IRC16:11
*** eghobo has quit IRC16:12
*** alexsyip has joined #openstack-meeting-316:12
*** eghobo has joined #openstack-meeting-316:13
*** wojdev has quit IRC16:16
*** julim has joined #openstack-meeting-316:17
*** Swami has joined #openstack-meeting-316:18
*** alexpilotti has quit IRC16:20
*** wojdev has joined #openstack-meeting-316:21
*** banix has joined #openstack-meeting-316:23
*** nfedotov has left #openstack-meeting-316:24
*** btully has quit IRC16:28
*** wojdev has quit IRC16:29
*** lblanchard has joined #openstack-meeting-316:31
*** ivar-lazzaro has quit IRC16:32
*** iovadia has quit IRC16:33
*** mattfarina has joined #openstack-meeting-316:34
*** mattfarina has quit IRC16:34
*** eghobo__ has joined #openstack-meeting-316:35
*** eghobo has quit IRC16:36
*** VW__ has joined #openstack-meeting-316:38
*** VW__ has quit IRC16:38
*** VW__ has joined #openstack-meeting-316:39
*** roeyc has quit IRC16:39
*** garyk1 has quit IRC16:39
*** VW_ has quit IRC16:40
*** lblanchard has quit IRC16:41
*** sahid has quit IRC16:43
*** armax has quit IRC16:46
*** armax has joined #openstack-meeting-316:48
*** safchain has quit IRC16:49
*** matrohon has quit IRC16:50
*** mwang2 has joined #openstack-meeting-316:53
*** btully has joined #openstack-meeting-316:59
*** pkoniszewski has quit IRC17:01
*** ivar-lazzaro has joined #openstack-meeting-317:03
*** rockyg has joined #openstack-meeting-317:04
*** rockyg has quit IRC17:06
*** rockyg has joined #openstack-meeting-317:06
*** igordcard has joined #openstack-meeting-317:07
*** bpokorny has quit IRC17:08
*** bpokorny has joined #openstack-meeting-317:09
*** rockyg has left #openstack-meeting-317:10
*** mwang2_ has joined #openstack-meeting-317:10
*** yamahata has quit IRC17:11
*** mwang2 has quit IRC17:11
*** igordcard has quit IRC17:12
*** s3wong has joined #openstack-meeting-317:12
*** eghobo__ has quit IRC17:13
*** igordcard has joined #openstack-meeting-317:13
*** igordcard has quit IRC17:13
*** igordcard has joined #openstack-meeting-317:14
*** ivar-lazzaro has quit IRC17:14
*** ivar-lazzaro has joined #openstack-meeting-317:15
*** ivar-lazzaro has quit IRC17:16
*** fallenpegasus has joined #openstack-meeting-317:16
*** ivar-lazzaro has joined #openstack-meeting-317:17
*** igordcard has quit IRC17:17
*** VW__ has quit IRC17:17
*** melwitt has joined #openstack-meeting-317:19
*** sbalukoff has quit IRC17:19
*** banix has quit IRC17:23
*** eghobo has joined #openstack-meeting-317:23
*** shwetaap has quit IRC17:24
*** banix has joined #openstack-meeting-317:27
*** LouisF has joined #openstack-meeting-317:31
*** moshele has joined #openstack-meeting-317:31
*** yamahata has joined #openstack-meeting-317:32
*** moshele has quit IRC17:33
*** emagana has quit IRC17:33
*** sbalukoff has joined #openstack-meeting-317:37
*** shwetaap has joined #openstack-meeting-317:41
*** fallenpegasus has quit IRC17:43
*** fallenpegasus has joined #openstack-meeting-317:43
*** fallenpegasus has quit IRC17:48
*** banix has quit IRC17:51
*** wojdev has joined #openstack-meeting-317:52
*** Sukhdev has quit IRC17:55
*** SumitNaiksatam has joined #openstack-meeting-317:56
*** e0ne has quit IRC17:57
*** shwetaap has quit IRC18:00
*** emagana has joined #openstack-meeting-318:01
*** eghobo_ has joined #openstack-meeting-318:02
*** s3wong has quit IRC18:03
*** eghobo has quit IRC18:04
*** beagles is now known as beagles_brb18:04
*** s3wong has joined #openstack-meeting-318:05
*** davidlenwell has quit IRC18:05
*** davidlenwell has joined #openstack-meeting-318:05
*** dhellmann has quit IRC18:05
*** banix has joined #openstack-meeting-318:05
*** banix has quit IRC18:10
*** banix has joined #openstack-meeting-318:10
*** shwetaap has joined #openstack-meeting-318:12
*** moshele has joined #openstack-meeting-318:12
*** wojdev has quit IRC18:16
*** beagles_brb is now known as beagles18:21
*** SridarK has joined #openstack-meeting-318:24
*** badveli has joined #openstack-meeting-318:26
*** VW_ has joined #openstack-meeting-318:27
*** markvoelker has quit IRC18:28
*** badveli1 has joined #openstack-meeting-318:29
vishwana_hello18:30
SridarKHi All18:30
badveli1hello all18:30
SumitNaiksatambadveli: SridarK vishwana_: hi18:30
badveli1hello sumit and all18:30
*** badveli has quit IRC18:31
SumitNaiksatam#startmeeting Networking FWaaS18:31
openstackMeeting started Wed Apr 29 18:31:29 2015 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:31
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:31
*** e0ne has joined #openstack-meeting-318:31
*** e0ne is now known as e0ne_18:31
*** openstack changes topic to " (Meeting topic: Networking FWaaS)"18:31
openstackThe meeting name has been set to 'networking_fwaas'18:31
*** Nikolay_St has joined #openstack-meeting-318:31
*** cbits has left #openstack-meeting-318:31
SumitNaiksatam#info the liberty release schedule was posted: #link https://wiki.openstack.org/wiki/Liberty_Release_Schedule18:32
*** e0ne_ is now known as e0ne18:32
*** e0ne is now known as e0ne_18:32
*** e0ne_ is now known as e0ne18:32
*** e0ne has quit IRC18:32
SumitNaiksatamplease take note18:32
SumitNaiksatamany other announcements?18:32
SumitNaiksatam#topic Bugs18:33
*** openstack changes topic to "Bugs (Meeting topic: Networking FWaaS)"18:33
SumitNaiksatamyoshiro had posted a couple of bugs and patches18:34
SumitNaiksatam#link https://bugs.launchpad.net/neutron/+bug/144607418:34
openstackLaunchpad bug 1446074 in neutron "FWaaS - Missing tenant_id validation between firewall and firewall_policy in creating/updating firewall" [Undecided,In progress] - Assigned to Yushiro FURUKAWA (y-furukawa-2)18:34
SumitNaiksatamthe above looks good to me18:34
SumitNaiksatam#link https://bugs.launchpad.net/neutron/+bug/144743518:34
openstackLaunchpad bug 1447435 in neutron "FWaaS - Missing port-range validation for firewall-rule" [Undecided,In progress] - Assigned to Yushiro FURUKAWA (y-furukawa-2)18:34
SumitNaiksatami thouhgt we were already validating the above, so i need to check the patch more carefully18:34
vishwana_I had email exchange with Yishiro on bug repr steps a while back...18:35
SumitNaiksatamvishwana_: yeah, i believe you are referring to 144607418:35
vishwana_Yes, Looks like he has updated instructions in the bug now, I need to go try it out18:35
SridarKSumitNaiksatam: that was my understanding too - i think we discussed this in the context of insertion as well18:35
SumitNaiksatamany other bugs on the implementation side that we need to discuss?18:36
*** emagana has quit IRC18:36
SridarKSumitNaiksatam: nothing else critical that i noticed18:36
SumitNaiksatamoh this one #link https://bugs.launchpad.net/neutron/+bug/144843918:37
openstackLaunchpad bug 1448439 in neutron "fwaas iptables driver does not work with plugins without DVR support" [High,In progress] - Assigned to Akihiro Motoki (amotoki)18:37
SumitNaiksatambut i already reviewed it18:37
SridarKI saw Akihiro push18:37
SridarKok18:37
SumitNaiksatamneeds one more core18:37
SridarKu got it :-)18:37
SumitNaiksatamSridarK: :-)18:37
SumitNaiksatammoving on to docs - this one is still pending #link https://bugs.launchpad.net/openstack-api-site/+bug/142565818:38
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:38
SridarKSumitNaiksatam: i finally got this going18:38
SumitNaiksatamSridarK: okay great18:38
SridarKSumitNaiksatam: i am making changes to address pc_m's comments18:39
*** iben__ has quit IRC18:39
*** marun has quit IRC18:39
SridarKSumitNaiksatam: i think i finally understood the layout of this :-(18:39
SumitNaiksatamSridarK: ah okay, i was actually going to address that today18:39
SridarKSo i will address his 2nd comment for the params18:39
SridarKthen i will address his first comment for policy and rules18:39
SumitNaiksatamSridarK: you mean update this one: #link https://review.openstack.org/#/c/170733/8/api-ref/src/wadls/netconn-api/src/os-fwaasv2.0-ext.wadl18:40
SridarKyes we need to add some more stuff into common.ent18:40
SridarKand then update the above18:40
vishwana_SridarK, SumitNaiksatam, sorry have not had a chance to work on 1425658...I maybe able to contribute from Monday next week though18:40
SumitNaiksatamSridarK: yeah, that one is slightly less painful18:40
SumitNaiksatamvishwana_: sure, np18:41
SridarKSumitNaiksatam: but sigh - i think there is some automation here - but don't know - unfortunately i was out last week and i was going to catch pc_m this week but he is out18:41
SridarKbut this is finally moving18:41
SumitNaiksatamSridarK: okay18:41
SridarKwill shoot to get a patch out today18:42
SumitNaiksatamSridarK: have you already on: #link https://review.openstack.org/#/c/170733/8/api-ref/src/wadls/netconn-api/src/os-fwaasv2.0-ext.wadl ?18:42
SridarKSumitNaiksatam: updates there first will take care of Firewall resource18:42
*** moshele has left #openstack-meeting-318:43
SridarKthen do policy and rules18:43
*** emagana has joined #openstack-meeting-318:43
SridarKpc_m had a comment on the param being used - i believe i have fixed that now18:43
SumitNaiksatamSridarK: okay, if you have already started working on that, then i wont work on that18:43
SridarK&svcListResponse18:43
SumitNaiksatamthe more tricky one though is adding something similar to: #link https://review.openstack.org/#/c/167609/8/api-ref/src/wadls/netconn-api/src/common.ent18:44
SridarKSumitNaiksatam: yes - i will do this - apologies should have gotten this down earlier18:44
SumitNaiksatamis that the one you are referring to?18:44
SridarKSumitNaiksatam: yes18:44
SridarKwe need to describe all the attributes in the message18:44
SumitNaiksatamso to step back - we have to do two updates:18:44
SridarKSumitNaiksatam: yes18:45
SumitNaiksatam(1) we need to add operations to #link https://review.openstack.org/#/c/170733/8/api-ref/src/wadls/netconn-api/src/os-fwaasv2.0-ext.wadl18:45
SridarKSumitNaiksatam: yes18:45
SumitNaiksatam(2) we need to add content similar to #link https://review.openstack.org/#/c/167609/8/api-ref/src/wadls/netconn-api/src/common.ent (in the context of FWaaS018:45
SridarKSumitNaiksatam: exactly18:45
SridarKfor the attributes/parameters18:45
SumitNaiksatamSridarK: so you have currently touched both?18:45
SridarKI am working thru (2) first18:46
SridarKthen in can refer to that in (1)18:46
SridarKand also add methods for policies and rules in (1)18:46
*** iben_ has joined #openstack-meeting-318:46
SumitNaiksatamSridarK: ah okay, i was thinking that i would have been able to do (1) independent of (2), perhaps not18:46
SumitNaiksatamSridarK: lets sync up offline on this18:47
SridarKSumitNaiksatam: that may be possible - we can discuss more offline18:47
SridarKyes :-)18:47
SumitNaiksatam:-)18:47
SumitNaiksatami think that covers the bugs18:48
*** e0ne has joined #openstack-meeting-318:48
vishwana_In general for bugs, we should review to see if bug authors have provided adequate issue repro steps to make the review go through smoother and faster18:48
SridarKvishwana_: +118:48
*** Piet has quit IRC18:48
*** matrohon has joined #openstack-meeting-318:48
SumitNaiksatam#topic Liberty Features18:48
*** openstack changes topic to "Liberty Features (Meeting topic: Networking FWaaS)"18:48
SumitNaiksatamas a logistical note - we need to update #link https://wiki.openstack.org/wiki/Meetings/FWaaS#Liberty_Charter18:49
SumitNaiksatami made some preliminary updates in the blueprints section18:49
SumitNaiksatamas a team we need to further populate it18:49
SridarKSumitNaiksatam: nice18:50
SumitNaiksatamalso kindly update the vendor blueprints section18:50
SumitNaiksatamjust fixed the broken link for fwaas rules18:50
SumitNaiksatamdirections18:50
SumitNaiksatamis slawek here?18:51
SumitNaiksatami think we owe him a vote on this, it seemed fine the last we discussed it in this meeting18:51
SridarKSumitNaiksatam: yes - i am basically good on this - i had responded to him on email he had sent me18:51
SumitNaiksatamSridarK: great18:52
vishwana_will review and vote on that BP this week18:52
SumitNaiksatambadveli1: if you have an updated patch for your “service objects” spec, please update the wiki page #link https://wiki.openstack.org/wiki/Meetings/FWaaS#Blueprint_Tracking18:52
badveli1sumit i am trying to figure out on the link18:52
SumitNaiksatambadveli1: thanks18:52
badveli1that mentions how to move over the same spec to liberty18:53
SumitNaiksatamSridarK: are you planning to repurpose the earlier zones spec, and repost it?18:53
SridarKSumitNaiksatam: yes i will do that18:53
SumitNaiksatambadveli1: i already sent you the email about how to repurpose18:53
SumitNaiksatamrepurpose -> move18:53
badveli1thanks sumit, yes i am referring to it,18:53
SumitNaiksatambadveli1: i forwarded the email to you about a couple of weeks back i think18:53
SumitNaiksatambadveli1: ah ok, thought you were saying you were still trying to find the email18:54
badveli1no thanks sumit for the link18:54
SumitNaiksatamvishwana_: i believe last meeting you mentioned you wanted to post a spec on refactoring for the notifications?18:54
badveli1it was not very straight forward/ trying to understand more on this18:55
vishwana_SumitNaiksatam, you mean the FirewallService object right?18:55
SumitNaiksatamvishwana_: yeah18:55
vishwana_ok, thanks for the reminder, will try to get a draft out sometime next week18:55
SumitNaiksatamvishwana_: thanks, if i recall pcm was also interested in collaborating on this18:57
vishwana_will reach out to him next week, since he is out this week18:57
SumitNaiksatamvishwana_: thanks18:57
SumitNaiksatamwhat other features are we planning?18:57
SridarKSumitNaiksatam: yushiro mentioned there were somethings he was considering - will ping him too18:58
yamahataIs enhancing FWaaS API to L4-7 the scope of Liberty?18:58
SumitNaiksatamyamahata: hi, thanks for joining18:58
yamahataSumitNaiksatam: hi.18:58
SumitNaiksatamyamahata: i dont see why it should not be18:59
SumitNaiksatamyamahata: if there is interest at your end in pushing forward with the spec and implementation, that would be great18:59
yamahataSure.18:59
badveli1SumitNaiksatam: iptables does it support this kind of functionality19:00
SumitNaiksatamdoes anyone else in the team have thoughts on this19:00
SridarKyamahata: there is considerable interest on this for sure - i think finding an open source implementation etc were some challenges19:00
yamahatawith spec, we can argue common denominator or vendor specific api19:00
SridarKyamahata: i am happy to help on this too19:00
SumitNaiksatambadveli1: SridarK: good points19:00
SumitNaiksatamL4-7 was a part of our original manifesto19:00
SridarKbadveli1: i think Yi mentioned interest on this as well19:00
yamahataSridarK: Yeah. and blob api was rejected as evil.19:00
SridarK:-)19:00
SumitNaiksatambut, like badveli1 and SridarK mentioned, one of the reasons it hasnt progressed is to find the right open source backend to support this19:01
*** emagana has quit IRC19:01
SridarKyamahata: good that u brought this up  - this will be a good discussion to have19:01
SumitNaiksatamyamahata: have you indentified what would be the reference implementation for these features?19:02
*** mrmartin has joined #openstack-meeting-319:02
yamahataSumitNaiksatam: Unfortunately no.19:02
*** ivar-laz_ has joined #openstack-meeting-319:02
*** ivar-laz_ has quit IRC19:02
SumitNaiksatamyamahata: okay19:02
*** mrunge has quit IRC19:03
*** LouisF has quit IRC19:03
yamahataFWaaS service insertion is important topic. On the other hand, several parties are interested in service function chaining.19:03
*** ivar-laz_ has joined #openstack-meeting-319:03
yamahataDo we want to cope with them?19:03
*** Nikolay_St has quit IRC19:03
*** bpokorny_ has joined #openstack-meeting-319:03
SridarKyamahata: +119:03
SumitNaiksatamyamahata: as for insertion, we already have some form of that19:04
*** emagana has joined #openstack-meeting-319:04
SumitNaiksatamin the context of providing the router context19:04
*** ivar-lazzaro has quit IRC19:04
*** dhellmann has joined #openstack-meeting-319:06
SumitNaiksatamplease also keep in mind the design summit etherpad for neutron: #link https://etherpad.openstack.org/p/liberty-neutron-summit-topics19:06
*** jaypipes has quit IRC19:06
SumitNaiksatam#topic Vendor drivers19:06
*** openstack changes topic to "Vendor drivers (Meeting topic: Networking FWaaS)"19:07
SumitNaiksatamany concerns on this front that we need to discuss?19:07
*** bpokorny has quit IRC19:07
SumitNaiksatam#topic Functional Tests19:07
*** openstack changes topic to "Functional Tests (Meeting topic: Networking FWaaS)"19:07
SumitNaiksatambadveli1: you mentioned you were looking at this, any update to share with the team?19:07
badveli1yes sumit, as i had mentioned we use the exec on the name space19:08
badveli1to generate traffic and check if the functionality works19:08
SumitNaiksatambadveli1: okay19:09
SumitNaiksatamso are you planning to implement a test with that knowledge?19:10
*** VW_ has quit IRC19:10
badveli1yes sumit, as  you had mentioned we will have this in liberty correct?19:10
*** wojdev has joined #openstack-meeting-319:10
SumitNaiksatambadveli1: yes, liberty is already open (has been for sometime now), so please feel free to post a patch if you have one (it could be WIP to begin with)19:11
badveli1fine sumit19:11
SumitNaiksatambadveli1: thanks19:11
badveli1thanks sumit19:12
SumitNaiksatamwe are missing pcm today for the discussion on this :-)19:12
SumitNaiksatamSridarK: any updates on the integration tests (for testing the insertion)?19:12
SridarKSumitNaiksatam: Nikolay will be doing more - when he is back from PTO19:12
SumitNaiksatamSridarK: ah ok19:13
SumitNaiksatam#topic Open Discussion19:13
*** openstack changes topic to "Open Discussion (Meeting topic: Networking FWaaS)"19:13
SridarKSumitNaiksatam: so we will plan for a meetup of FWaaS folks at Vancouver ?19:14
SumitNaiksatamif there is enough interest we can create a separate etherpad for FWaaS topics to discuss in the summit19:14
SumitNaiksatamSridarK: ah right on cue :-)19:14
SridarK:-)19:14
SumitNaiksatamSridarK: we should definitely19:14
*** lblanchard has joined #openstack-meeting-319:14
*** rushiagr is now known as rushiagr_away19:15
SridarKbadveli1: are u going to be there ?19:15
SridarKor Yi ?19:15
vishwana_SridarK, do you mean a social meetup?19:15
badveli1no we are not going to be there19:15
*** banix has quit IRC19:15
badveli1but wish you all the best19:15
SumitNaiksatambadveli1: oh thats a big bummer!19:15
SridarKvishwana_: no - white board,19:15
vishwana_ok, sure19:15
SridarKbadveli1: oh thats bad19:16
badveli1let me know if you need any help19:16
SumitNaiksatambadveli1: so not even Yi or Gary planning to be there?19:16
badveli1no sumit19:16
SumitNaiksatambadveli1: ah ok19:16
badveli1let me know if you need any help before summit19:16
*** ivar-laz_ has quit IRC19:16
SumitNaiksatambadveli1: sure19:17
SumitNaiksatamanything else we need to discuss today?19:17
SridarKSumitNaiksatam: nothing else from me19:17
SumitNaiksatamSridarK: okay19:17
*** ivar-lazzaro has joined #openstack-meeting-319:17
SumitNaiksatamthanks all for joining!19:17
SumitNaiksatambye19:17
badveli1bye19:17
vishwana_bye all19:17
badveli1bye all19:17
SumitNaiksatam#endmeeting19:17
SridarKthanks bye all19:17
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:17
openstackMeeting ended Wed Apr 29 19:17:55 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:17
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-04-29-18.31.html19:17
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-04-29-18.31.txt19:17
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-04-29-18.31.log.html19:18
yamahatabye19:18
*** salv-orl_ has joined #openstack-meeting-319:18
*** SridarK has quit IRC19:18
*** eghobo_ has quit IRC19:19
*** wojdev has quit IRC19:21
*** salv-orlando has quit IRC19:22
*** jaypipes has joined #openstack-meeting-319:23
*** VW_ has joined #openstack-meeting-319:28
*** wojdev has joined #openstack-meeting-319:28
*** nkrinner has joined #openstack-meeting-319:29
*** banix has joined #openstack-meeting-319:30
*** Nikolay_St has joined #openstack-meeting-319:31
*** lblanchard has quit IRC19:34
*** badveli1 has left #openstack-meeting-319:34
*** Nikolay_St has quit IRC19:36
*** wojdev has quit IRC19:39
*** egallen has quit IRC19:40
*** eghobo has joined #openstack-meeting-319:40
*** david-lyle has quit IRC19:44
*** sarob has quit IRC19:44
*** david-lyle has joined #openstack-meeting-319:44
*** sarob has joined #openstack-meeting-319:45
*** bpokorny has joined #openstack-meeting-319:48
*** bpokorny_ has quit IRC19:52
*** ivar-lazzaro has quit IRC19:54
*** Nikolay_St has joined #openstack-meeting-319:54
*** ivar-lazzaro has joined #openstack-meeting-319:54
*** wojdev has joined #openstack-meeting-319:55
*** Rockyg has joined #openstack-meeting-320:08
*** ivar-lazzaro has quit IRC20:10
*** ivar-lazzaro has joined #openstack-meeting-320:11
*** emagana has quit IRC20:11
*** emagana has joined #openstack-meeting-320:14
*** iben_ has quit IRC20:21
*** e0ne has quit IRC20:26
*** banix has quit IRC20:26
*** marun has joined #openstack-meeting-320:26
*** ivar-lazzaro has quit IRC20:32
*** ivar-lazzaro has joined #openstack-meeting-320:32
*** banix has joined #openstack-meeting-320:36
*** e0ne has joined #openstack-meeting-320:36
*** mrmartin has quit IRC20:39
*** e0ne has quit IRC20:44
*** jcoufal has joined #openstack-meeting-320:45
*** mtreinish_ has joined #openstack-meeting-320:45
*** matrohon has quit IRC20:48
*** shwetaap has quit IRC20:49
*** mtreinish_ is now known as mtreinish20:51
*** ajo has quit IRC20:51
*** praveens has joined #openstack-meeting-320:52
*** belmoreira has joined #openstack-meeting-320:55
alaskibauzas: ping21:00
*** fallenpegasus has joined #openstack-meeting-321:00
alaski#startmeeting nova_cells21:00
openstackMeeting started Wed Apr 29 21:00:29 2015 UTC and is due to finish in 60 minutes.  The chair is alaski. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
bauzas\o21:00
*** openstack changes topic to " (Meeting topic: nova_cells)"21:00
openstackThe meeting name has been set to 'nova_cells'21:00
melwitto/21:00
dansmitho/21:00
alaskigood <regional time of day> everyone21:00
belmoreirao/21:00
alaski#topic Tempest testing21:01
*** openstack changes topic to "Tempest testing (Meeting topic: nova_cells)"21:01
*** VW_ has quit IRC21:01
alaskiso there are still some intermittent failures21:01
alaskibut nothing has merged yet to address them, so totally expected21:01
*** shwetaap has joined #openstack-meeting-321:02
edleafeo/21:02
alaskihttps://review.openstack.org/#/c/177356/ will hopefully help, but it's hard to say for sure at this point21:02
bauzasalaski: to be clear, we should see if your patch helps that21:02
*** Networkn3rd has quit IRC21:02
alaskiyeah21:03
bauzasso another week round before proposing it to vote ?21:03
*** iben_ has joined #openstack-meeting-321:03
*** jcoufal has quit IRC21:03
alaskiI also want to dig into some of the failures, but there's been a lack of hours in the day21:03
bauzastrying to remember the logstash query for checking the intermittent ratio21:03
alaskihttp://goo.gl/AlgZRa21:04
bauzasgotcha "build_name:"check-tempest-dsvm-cells" AND message:"Worker Balance" AND build_status:"FAILURE" "21:04
alaskiwell, that shows failures21:04
bauzasalaski: agreed but that counts per hour21:04
*** geoffarnold has joined #openstack-meeting-321:04
alaskithere are two bugs opened https://bugs.launchpad.net/nova/+bug/1448316 and https://bugs.launchpad.net/nova/+bug/144830221:05
openstackLaunchpad bug 1448316 in OpenStack Compute (nova) "cells: Object action destroy failed because: host changed" [Medium,Confirmed] - Assigned to tianzichen306 (tianzichen306)21:05
bauzasalaski: so if we have like 5/h, we just need to know how many runs per hour and we get the max error ratio21:05
openstackLaunchpad bug 1448302 in OpenStack Compute (nova) "cells: intermittent KeyError when deleting instance metadata" [Low,Confirmed]21:05
alaskiif anyone fancies looking at some point21:05
bauzasalaski: by saying that, I mean that if we are below 0.1% error rate, why not just consider the job as voting ?21:06
bauzasbecause a recheck would be worth it21:06
*** banix has quit IRC21:06
bauzaswe should just face the failures and mark them in e-r21:06
bauzasonce the job is voting21:07
alaskiI'm not sold on that at this point, I'd want to see something saying the rate is really really low first21:07
bauzaswe spiked at 7 per hour during the last 7 days21:07
dansmiththe last thing we want,21:07
bauzasbut with an average around 2 or 321:08
alaskithat's a fair amount21:08
dansmithis to turn it on prematurely and gain the scorn of our colleagues :)21:08
dansmithIMHO.21:08
*** marun has quit IRC21:08
bauzasdansmith: agreed21:08
alaskiright21:08
bauzasdansmith: my point is just to identify the balance between waiting for any magical solution and how much it costs to get it voting21:08
dansmithyep21:08
alaskiI think we just have a couple of issues left, which may be resolved with my patch21:09
dansmiththere's definitely a balance there21:09
*** peristeri has quit IRC21:09
bauzasanyway don't get me wrong, the prio is alaski's patch21:09
bauzasbefore even thinking about voting21:09
alaskibauzas: if it got to a handful of failures a day I think we shoudl have a conversation on it21:09
bauzasie. https://review.openstack.org/#/c/177356/21:09
bauzasalaski: agreed21:10
alaskianything else on testing?  I think for now it's waiting on that patch and digging in on the lp bugs when there's time21:10
bauzasanyway, let's chase another guru and then see how it reduce the failures21:11
bauzasalaski: +121:11
alaski#topic Specs21:11
*** openstack changes topic to "Specs (Meeting topic: nova_cells)"21:11
alaskishamefully I have not updated any specs recently21:11
bauzasso, maybe nothing to say ?21:12
alaskiwell, one thing21:12
bauzasunless someone takes the opportunity to ask questions ?21:12
alaskiperhaps I misread something, but I felt like there might be some question about https://review.openstack.org/#/c/176078/ being enough21:12
alaskibecause while it works for scheduling, it doesn't work for an API response21:13
bauzasalaski: then I need to be more clear21:13
bauzasalaski: I think persisting the whole object in the API db is good to me21:14
*** Sukhdev has joined #openstack-meeting-321:14
bauzasalaski: then, it could maybe be done like instance.save(), ie. being synced21:15
bauzasmaybe I'm foolish21:15
alaskiI was thinking we would pick the db based on context21:15
bauzasmy point is that if the scheduling stuff is magically working on the parent cell, why do we need to get it to the child cell ?21:16
alaskiso with cell_db_context: req.save()21:16
bauzasI perhaps missed it21:16
alaskithe primary reason IMO is we don't want to store much data per instance in the api db21:17
bauzaswell the instance <=> req_spec is thin21:17
bauzasan instance can have a request_spec dependency21:18
alaskibut there can be one reqest spec per instance21:18
bauzasergh s/dep/relationship21:18
bauzasalaski: yeah21:18
bauzasalaski: but then, you only need to care about how to get the reqspec reference21:18
bauzasalaski: you don't need to store the whole object21:18
bauzasI mean nested in the instance21:19
alaskito be clear, are you suggesting the request spec in the api db, and a ref to it in the instance?21:19
bauzasalaski: yup21:19
*** VW_ has joined #openstack-meeting-321:20
belmoreiraI have concerns about https://review.openstack.org/#/c/141486/ but maybe I'm misunderstanding it. A spec iteration would be good.21:20
alaskimy concern is that for scaling it's better to have that in the cell, so the api db doesn't store much data per instance21:20
belmoreirabauzas: thanks for the comments21:21
bauzasalaski: then the context is a good option21:21
bauzasI mean a cell context related save()21:21
bauzasalaski: will amend my comment then21:21
alaskibelmoreira: I will iterate that.  sorry for the delay21:22
bauzasbelmoreira: I know that we probably have kind of misunderstanding between us21:22
bauzas:)21:22
bauzasbelmoreira: I know you would like some cell-only scheduling options21:23
alaskifor the request spec, it will need to be stored in the api db originally.  and then additional data will need to be stored to satisfy an instance list/show21:23
bauzasalaski: agreed21:23
melwittI had a similar albeit vague thought as alaski. I'm not very clear on the interactions for things like a migrate where we want to refer to the req spec, if keeping it in the cell would help save things converging on the api db constantly21:23
bauzasmelwitt: to be clear, migrations are not using requestspec now, just because we're not persisting it yet :)21:25
*** iben_ has quit IRC21:25
melwittbauzas: yes, I mean assuming we persist21:25
*** nkrinner has quit IRC21:25
bauzasmelwitt: MHO is that migrating comes from the API anyway21:26
belmoreirabauzas: yes :)21:26
bauzasmelwitt: the conductor is being called, but that's still coming in from the api21:26
melwittbauzas: that's what I was getting at. if it's in the api anyway, it wouldn't help much. so I was trying to say, if there are scenarios where we need to use request spec and we're not already at the api21:27
bauzasmelwitt: there is no periodic task related to migrations done on the conductor, AFAIK21:27
*** praveens has quit IRC21:27
melwittjust trying to get clear on, is this a current need or are we just thinking to cover that case for the future, if something comes up21:27
*** praveens has joined #openstack-meeting-321:27
bauzasmelwitt: I think we are pretty clear that automatic evacuation should not be done in Nova21:28
dansmithalaski: I thought we said store the req spec in the api db until we schedule, then delete and move it to the cell db?21:28
alaskidansmith: right, that's my thinking21:28
bauzasthat can work too21:28
alaskibauzas: was making a case for keeping it in the api21:28
dansmithokay, above it sounded like maybe you meant not delete from the api db21:28
dansmithpermanently/21:28
*** Longgeek has quit IRC21:29
bauzasdansmith: that depends on where you query the DB to get the spec when migrating21:29
dansmithI think having it in the api db makes it clear it's looking for a home, and once it's scheduled, it's in the other one21:29
*** marun has joined #openstack-meeting-321:29
dansmithbauzas: right, I don't think it really needs to be in the api db though, especially if the scheduler was external, we'd just grab the req from the current home, provide it to the scheduler and let it move21:29
bauzasdansmith: if that's done in the API, then there is a need for keeping it locally, but that goes down to the conductor and then being readed, it's actually better to have it in the cell db IMHO21:29
dansmithso, migration/resize would be moving the instance/reqspec from once cell to another (if it moves cells)21:30
bauzasdansmith: well, we need to read the spec for calling the scheduler right ?21:30
*** Rockyg has quit IRC21:30
dansmithokay, I don't follow that conductor line of thinking, but sounds like it's not important21:30
dansmithyes21:30
alaskibauzas: the api can read from the cell db21:30
*** julim has quit IRC21:30
dansmiththat's the point yeah :)21:30
bauzasdansmith: then, it's just a matter of finding where to call that21:31
bauzasalaski: but not the contrary, right ?21:31
alaskibauzas: correct21:31
dansmithcontrary what?21:31
bauzasalaski: given the current process of migrating21:31
alaskidansmith: reverse I'm assuming21:31
dansmithcell things reading from the api db?21:31
bauzasdansmith: the cell can't read the api db21:31
bauzasyeah, French hitted21:31
dansmithI'm not sure we'll be able to completely ban it, but it would be great if we can pass enough information down so that it doesn't21:32
bauzasso21:32
alaskidansmith: that's my goal.  but I agree it could be added if necessary21:32
bauzasthe current process is that a migration request comes to the API, which calls the conductor methods asynchronouslyu21:32
bauzasthat's a cast I mean21:32
dansmithyeah, I can see some things needing to rendezvous at the api db, but if we can avoid it, it's nice separation21:32
bauzasso, speaking about cells, conductor methods will be run on the cell side21:33
bauzasso they won't have access to the api db, unless we explicitely allow that21:33
alaskia migration within a cell could be handled without coordination of the api21:34
bauzasalaski: who would trigger the migration ?21:34
alaskithe api would cast to conductor as you said21:35
dansmithalaski: but it's the same, right?21:35
dansmithalaski: api passes the destination info, which might be the current cell21:35
*** marun has quit IRC21:35
dansmither, no21:36
*** stevemar has quit IRC21:36
bauzasdansmith: unless the user specifies no destination, and then it goes to a scheduler call21:36
dansmithI guess api calls to conductor to trigger, conductor calls scheduler, and then conductor will need the deets of the destination cell21:36
alaskiI think we need to be clear about inter vs intra cell21:36
dansmithwhich goes back to my conductor might need to call back up21:36
dansmithalaski: why? isn't that a scheduler thing?21:36
bauzasalaski: intra-cell conductor would call the inter-cell scheduler, I don't see that as a problem21:37
alaskithere's more needed for intra-cell21:37
* dansmith groks "intra-cell conductor" for a minute21:37
bauzasalaski: when migrating ?21:37
dansmithI say we just punt on inter-cell migrations for the moment21:37
bauzasalaski: or unshelving or whatever ?21:37
alaskidansmith: right, that's what I want to do21:38
dansmiththey'll be possible, but not supported today in v1 so we might as well punt on this21:38
bauzasfair point21:38
alaskithey're punted in cells v1 too21:38
alaskiif you're looking at intra cell you just pass the request into the cell, bam21:38
dansmithright21:38
bauzasyup21:38
bauzasalaski: well, there is just a flaw in that21:39
bauzasalaski: since the user can specify a dest host, it bypasses the scheduler and then calls the compute21:39
*** mattfarina has joined #openstack-meeting-321:40
bauzasalaski: so we just need to make sure that if the user specifies a dest, it's one within the same cell as the source21:40
bauzasbut I'm nitpicking for now21:40
*** mattfarina has quit IRC21:40
alaskiright.  that would fail currently because the two computes can't talk to each other21:40
alaskiand in the new setup21:41
alaskiso are we agreed that the request spec lives in a cell? :)21:41
bauzasalaski: in the new setup, that's just a check that the target is in the same cell than the source21:41
dansmithalaski: it lives in the cell after scheduling...21:41
bauzasalaski: after scheduling21:41
bauzasaaaarh21:42
* bauzas jinxed21:42
alaskidansmith: right, that's totally what I meant21:42
dansmithokay :)21:42
bauzasbut yeah, I'm fine with that approach21:42
alaskicool21:42
alaskimoving on21:42
alaski#Open discussion21:42
bauzascool21:42
alaskidammit21:42
alaski#topic Open discussion21:43
*** openstack changes topic to "Open discussion (Meeting topic: nova_cells)"21:43
*** praveens has quit IRC21:43
*** SumitNaiksatam has quit IRC21:43
*** marun has joined #openstack-meeting-321:43
alaskianyone have a topic to discuss?21:43
alaskiI need to iterate some specs and get some more things down on paper21:44
bauzaswe at least need to have a plan for the summit :)21:44
alaskiahh, yeah21:44
bauzasfor showing that and discuss21:44
alaskiso we're split between scheduling topics and everything else21:44
bauzasyou're toasted21:45
*** egallen has joined #openstack-meeting-321:45
alaskitoasted?21:45
bauzasmmm21:45
bauzassandwitched21:45
alaskiahh, yeah21:46
* bauzas tries to invent words at 11.40pm - always a bad idea21:46
bauzasso, it will depend on how it goes with the scheduler stuff21:46
bauzasbut we actually have 2 sessions back-to-back for cells v221:47
bauzasone for discussing about the scheduling needs, and one for the other stuff21:47
bauzaswhich is good IMHO21:47
alaskiyeah21:47
alaskigetting scheduling right is a big part of this21:47
bauzasand at least, people won't get boring just because we'll be speaking about scheduler all the morning...21:48
alaskioutside of that is getting the interactions between the api and cell right, and migrating data properly21:48
bauzasalaski: I would rather make a call to discuss how we can scale21:48
bauzasalaski: I just wonder if we should also poke the neutron guys21:48
bauzasalaski: since we haven't yet agreed on the plan for network requests21:48
alaskiI've been thinking on that21:49
bauzasalaski: and since neutron doesn't have cells also21:49
bauzasalaski: yeah I know21:49
alaskiif you assume a global neutron everything should just work21:49
bauzasalaski: would it be not facing the same problems as nova ?21:49
alaskiit has scaling concerns, and cells might be a good approach for them21:49
bauzasalaski: like the queues and so on21:49
alaskithere's definitely things to talk about there, but we're not blocked on it I think21:50
bauzasalaski: that's my point, it would just be horrible to do all the efforts and then being pushbacked just because neutron doesn't scale21:50
bauzasalaski: well, n-net is not deprecated yet, right ? :)21:51
alaskiheh21:51
alaskirealistically it would help if someone could help liason that stuff right now21:51
bauzasso indeed, let's do the assumptions that everything will scale, and at the end, n-net will be there for us :)21:51
*** egallen has left #openstack-meeting-321:52
alaskiI speak with some networking folks occasionally, but don't have the bandwidth to drive it very far at the moment21:52
bauzasshould we maybe engage some discussions with s68cal since he's the liaison ?21:52
alaskioh, was that figured out.  my email went wonky for a few days21:52
bauzashe's the neutron guy enough foolish to visit Nova21:53
alaskigotcha.  is there anyone on the nova side yet?21:53
bauzasnone I heard about21:53
bauzasI mean, network guys are creepy21:54
* bauzas kidding21:54
alaskiokay.  I can reach out to s68cal to give him a heads up on our efforts21:54
bauzaswe could at least give him a wish list21:55
alaskiback to the summit: does the data migration part of cells, getting instances and cells mapped, seem like a good topic to y'all?21:56
bauzasthat's a fair point to discuss, if the consensus is getting reached quickly, that's even better21:56
alaskiI want to touch on a few other things, but in the time allowed we can probably only hit one/two big things21:57
bauzasalaski: I seriously need to see what we should discuss for the scheduler efforts, so I could help you on that by giving you time if I can21:57
alaskiokay21:58
bauzasI seriosuly doubt people will be liking having all the morning kinda dedicated to scheduling21:58
bauzasbecause that's a beast21:58
bauzasthe last session is about RT, I still need to figure out what to fill in there21:59
dansmiththey'll get over it21:59
bauzasbecause there are good points to raise, but few chances to work on for Lib21:59
alaskiyep, that's what we're there for21:59
alaskiwell this was a bit disorganized, sorry.  I'll be more prepared next week22:00
alaskithanks all!22:00
alaski#endmeeting22:00
bauzassee ya22:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:00
openstackMeeting ended Wed Apr 29 22:00:29 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-04-29-21.00.html22:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-04-29-21.00.txt22:00
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-04-29-21.00.log.html22:00
*** mwang2_ has quit IRC22:00
*** melwitt has quit IRC22:02
*** melwitt has joined #openstack-meeting-322:02
*** VW_ has quit IRC22:03
*** Piet has joined #openstack-meeting-322:03
*** Swami has quit IRC22:04
*** rcleere is now known as rcleere_away22:04
*** VW_ has joined #openstack-meeting-322:06
*** VW_ has quit IRC22:09
*** VW_ has joined #openstack-meeting-322:09
*** VW_ has quit IRC22:16
*** belmoreira has quit IRC22:18
*** nelsnelson has quit IRC22:18
*** salv-orlando has joined #openstack-meeting-322:19
*** salv-orl_ has quit IRC22:23
*** jckasper has quit IRC22:27
*** shwetaap has quit IRC22:27
*** mwang2 has joined #openstack-meeting-322:30
*** fallenpegasus has quit IRC22:40
*** melwitt has quit IRC22:41
*** melwitt has joined #openstack-meeting-322:41
*** geoffarnold has quit IRC22:46
*** bknudson has quit IRC22:46
*** Swami has joined #openstack-meeting-322:47
*** bpokorny_ has joined #openstack-meeting-322:47
*** bpokorny has quit IRC22:51
*** carl_baldwin has quit IRC22:51
*** mwang2 has quit IRC22:56
*** bpokorny has joined #openstack-meeting-323:07
*** bpokorny_ has quit IRC23:10
*** cgoncalves has quit IRC23:10
*** cgoncalves has joined #openstack-meeting-323:12
*** Shamail has joined #openstack-meeting-323:13
*** Sukhdev has quit IRC23:14
*** ivar-lazzaro has quit IRC23:18
*** ivar-lazzaro has joined #openstack-meeting-323:19
*** ivar-lazzaro has quit IRC23:20
*** baoli has quit IRC23:20
*** ivar-lazzaro has joined #openstack-meeting-323:20
*** Rockyg has joined #openstack-meeting-323:20
*** fallenpegasus has joined #openstack-meeting-323:22
*** sarob_ has joined #openstack-meeting-323:24
*** banix has joined #openstack-meeting-323:33
*** fallenpegasus has quit IRC23:33
*** melwitt has quit IRC23:33
*** elmiko has joined #openstack-meeting-323:37
*** marun has quit IRC23:39
*** emagana has quit IRC23:40
*** wojdev has quit IRC23:55
*** stevelle has joined #openstack-meeting-323:58

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