Wednesday, 2015-08-19

*** masco has joined #openstack-meeting-300:04
*** lblanchard has joined #openstack-meeting-300:05
*** VW_ has quit IRC00:05
*** VW_ has joined #openstack-meeting-300:06
*** geoffarnold has quit IRC00:06
*** geoffarnold has joined #openstack-meeting-300:07
*** VW_ has quit IRC00:10
*** geoffarnold has quit IRC00:11
*** VW_ has joined #openstack-meeting-300:18
*** VW_ has quit IRC00:18
*** VW_ has joined #openstack-meeting-300:19
*** banix has quit IRC00:19
*** achippa_ has joined #openstack-meeting-300:22
*** achippa has joined #openstack-meeting-300:22
*** btully has quit IRC00:34
*** sridhar_ram has quit IRC00:34
*** salv-orl_ has quit IRC00:34
*** Piet has joined #openstack-meeting-300:36
*** Swami has quit IRC00:46
*** dims has joined #openstack-meeting-300:46
*** njohnston is now known as nate_gone00:46
*** dims_ has quit IRC00:47
*** masco has quit IRC00:48
*** baoli has joined #openstack-meeting-300:49
*** smccully has joined #openstack-meeting-300:51
*** achippa has quit IRC00:54
*** achippa_ has quit IRC00:54
*** baoli has quit IRC00:54
*** achippa has joined #openstack-meeting-300:54
*** achippa_ has joined #openstack-meeting-300:54
*** Piet has quit IRC00:55
*** dims has quit IRC00:56
*** dims has joined #openstack-meeting-300:56
*** achippa_ has quit IRC00:58
*** achippa has quit IRC00:58
*** jckasper has joined #openstack-meeting-301:06
*** mickeys has quit IRC01:08
*** zhenguo has joined #openstack-meeting-301:09
*** SumitNaiksatam has joined #openstack-meeting-301:09
*** SumitNaiksatam has left #openstack-meeting-301:09
*** VW_ has quit IRC01:10
*** bpokorny has quit IRC01:10
*** banix has joined #openstack-meeting-301:11
*** puranamr has quit IRC01:14
*** puranamr has joined #openstack-meeting-301:15
*** FallenPegasus has quit IRC01:16
*** s3wong has quit IRC01:16
*** yamamoto has joined #openstack-meeting-301:18
*** stanzgy has joined #openstack-meeting-301:18
*** achippa_ has joined #openstack-meeting-301:23
*** achippa has joined #openstack-meeting-301:23
*** julim has joined #openstack-meeting-301:24
*** yamamoto has quit IRC01:30
*** lblanchard has quit IRC01:31
*** banix has quit IRC01:32
*** ivar-lazzaro has joined #openstack-meeting-301:44
*** lazy_prince has joined #openstack-meeting-301:48
*** achippa has quit IRC01:53
*** achippa_ has quit IRC01:53
*** Piet has joined #openstack-meeting-302:04
*** neelashah has joined #openstack-meeting-302:13
*** yamahata has quit IRC02:14
*** baojg has joined #openstack-meeting-302:15
*** sankarshan_away is now known as sankarshan02:16
*** yamamoto has joined #openstack-meeting-302:16
*** lazy_prince has quit IRC02:21
*** neelashah has quit IRC02:28
*** neelashah has joined #openstack-meeting-302:34
*** geoffarnold has joined #openstack-meeting-302:35
*** baojg has quit IRC02:35
*** geoffarnold has quit IRC02:36
*** geoffarnold has joined #openstack-meeting-302:38
*** Poornima has joined #openstack-meeting-302:40
*** baojg has joined #openstack-meeting-302:48
*** salv-orlando has joined #openstack-meeting-302:49
*** shwetaap has joined #openstack-meeting-302:51
*** dims has quit IRC02:55
*** salv-orlando has quit IRC03:05
*** tellesnobrega has quit IRC03:17
*** tellesnobrega has joined #openstack-meeting-303:20
*** zz_natorious is now known as natorious03:28
*** tellesnobrega has quit IRC03:28
*** tellesnobrega has joined #openstack-meeting-303:30
*** jpomeroy_ has joined #openstack-meeting-303:31
*** jpomeroy has quit IRC03:31
*** jpomeroy_ has quit IRC03:36
*** yamamoto has quit IRC03:37
*** natorious is now known as zz_natorious03:39
*** yamahata has joined #openstack-meeting-303:40
*** yamamoto has joined #openstack-meeting-303:41
*** ajmiller has quit IRC03:43
*** julim has quit IRC03:59
*** salv-orlando has joined #openstack-meeting-304:04
*** shwetaap has quit IRC04:10
*** ivar-lazzaro has quit IRC04:11
*** tellesnobrega has quit IRC04:19
*** salv-orlando has quit IRC04:21
*** neelashah has quit IRC04:27
*** tellesnobrega has joined #openstack-meeting-304:28
*** puranamr has quit IRC04:28
*** puranamr has joined #openstack-meeting-304:28
*** sdake has quit IRC04:29
*** yamamoto has quit IRC04:33
*** ivar-lazzaro has joined #openstack-meeting-304:39
*** yamamoto has joined #openstack-meeting-304:41
*** shwetaap has joined #openstack-meeting-304:45
*** coolsvap|away is now known as coolsvap04:46
*** mrmartin has joined #openstack-meeting-304:51
*** irenab has quit IRC04:58
*** FallenPegasus has joined #openstack-meeting-304:58
*** baojg has quit IRC04:59
*** shwetaap has quit IRC05:06
*** carl_baldwin has joined #openstack-meeting-305:07
*** coolsvap is now known as coolsvap|away05:08
*** carl_baldwin has quit IRC05:08
*** JoshNang has quit IRC05:17
*** ivar-lazzaro has quit IRC05:18
*** ivar-lazzaro has joined #openstack-meeting-305:18
*** peristeri has joined #openstack-meeting-305:22
*** mickeys has joined #openstack-meeting-305:23
*** coolsvap|away is now known as coolsvap05:23
*** vgridnev has joined #openstack-meeting-305:24
*** JoshNang has joined #openstack-meeting-305:25
*** salv-orlando has joined #openstack-meeting-305:28
*** irenab has joined #openstack-meeting-305:30
*** vgridnev has quit IRC05:38
*** ivar-lazzaro has quit IRC05:41
*** ramineni has joined #openstack-meeting-305:41
*** ramineni has left #openstack-meeting-305:42
*** puranamr has quit IRC05:44
*** amotoki has joined #openstack-meeting-305:50
*** baojg has joined #openstack-meeting-305:58
*** peristeri has quit IRC06:03
*** armax has quit IRC06:05
*** FallenPegasus has quit IRC06:06
*** peristeri has joined #openstack-meeting-306:08
*** coolsvap is now known as coolsvap|away06:10
*** mrunge has joined #openstack-meeting-306:13
*** geoffarnold has quit IRC06:15
*** mickeys has quit IRC06:16
*** geoffarnold has joined #openstack-meeting-306:16
*** lsmola has joined #openstack-meeting-306:21
*** vgridnev has joined #openstack-meeting-306:22
*** sridhar_ram has joined #openstack-meeting-306:31
*** sridhar_ram has quit IRC06:35
*** lazy_prince has joined #openstack-meeting-306:36
*** nkrinner has joined #openstack-meeting-306:39
*** salv-orlando has quit IRC06:40
*** numan has joined #openstack-meeting-306:42
*** woodster_ has quit IRC06:49
*** jlvillal has quit IRC06:58
*** jlvillal has joined #openstack-meeting-306:58
*** vgridnev has quit IRC07:07
*** kzaitsev_mb has joined #openstack-meeting-307:14
*** peristeri has quit IRC07:18
*** jschwarz has joined #openstack-meeting-307:18
*** matrohon has joined #openstack-meeting-307:23
*** Poornima has quit IRC07:24
*** jtomasek has quit IRC07:26
*** matrohon has quit IRC07:27
*** belmoreira has joined #openstack-meeting-307:28
*** salv-orlando has joined #openstack-meeting-307:41
*** Poornima has joined #openstack-meeting-307:42
*** yamamoto has quit IRC07:46
*** yamamoto has joined #openstack-meeting-307:48
*** matrohon has joined #openstack-meeting-307:50
*** kzaitsev_mb has quit IRC07:53
*** kzaitsev_mb has joined #openstack-meeting-307:53
*** matrohon has quit IRC07:58
*** jcoufal has joined #openstack-meeting-308:02
*** bharath_ has quit IRC08:20
*** timbyr_ has joined #openstack-meeting-308:21
*** bharath_ has joined #openstack-meeting-308:21
*** markvoelker has quit IRC08:22
*** bharath_ has quit IRC08:26
*** vgridnev has joined #openstack-meeting-308:29
*** kzaitsev_mb has quit IRC08:35
*** bharath_ has joined #openstack-meeting-308:36
*** jschwarz is now known as jschwarz|lunch09:10
*** markvoelker has joined #openstack-meeting-309:23
*** bharath__ has joined #openstack-meeting-309:24
*** bharath_ has quit IRC09:24
*** ajo is now known as ajo\afk09:27
*** SumitNaiksatam has joined #openstack-meeting-309:28
*** markvoelker has quit IRC09:28
*** bharath__ has quit IRC09:43
*** egallen has joined #openstack-meeting-309:43
*** jaypipes has quit IRC09:46
*** killer_prince has joined #openstack-meeting-309:48
*** lazy_prince has quit IRC09:52
*** jtomasek has joined #openstack-meeting-309:55
*** tfukushima has joined #openstack-meeting-309:55
*** killer_prince has quit IRC09:58
*** egallen has quit IRC10:02
*** yamamoto has quit IRC10:04
*** sigmavirus24_awa has quit IRC10:06
*** zz_natorious has quit IRC10:06
*** eglute has quit IRC10:06
*** miguelgrinberg has quit IRC10:07
*** zz_natorious has joined #openstack-meeting-310:07
*** zz_natorious is now known as natorious10:08
*** miguelgrinberg has joined #openstack-meeting-310:08
*** eglute has joined #openstack-meeting-310:08
*** belmoreira has quit IRC10:08
*** belmoreira has joined #openstack-meeting-310:09
*** sigmavirus24_awa has joined #openstack-meeting-310:10
*** belmoreira has quit IRC10:14
*** tfukushima has quit IRC10:15
*** belmoreira has joined #openstack-meeting-310:15
*** tfukushima has joined #openstack-meeting-310:16
*** lazy_prince has joined #openstack-meeting-310:16
*** wimdc has joined #openstack-meeting-310:18
*** baojg has quit IRC10:26
*** kzaitsev_mb has joined #openstack-meeting-310:26
*** baojg has joined #openstack-meeting-310:27
*** jschwarz|lunch is now known as jschwarz10:29
*** baojg has quit IRC10:31
*** yamahata has quit IRC10:32
*** bharath_ has joined #openstack-meeting-310:43
*** belmoreira has quit IRC10:48
*** bharath_ has quit IRC10:48
*** stanzgy has quit IRC10:52
*** salv-orlando has quit IRC10:53
*** dims has joined #openstack-meeting-310:56
*** mwagner_lap has quit IRC10:57
*** peristeri has joined #openstack-meeting-310:58
*** yamamoto_ has joined #openstack-meeting-310:58
*** killer_prince has joined #openstack-meeting-310:59
*** lazy_prince has quit IRC11:03
*** dims_ has joined #openstack-meeting-311:03
*** baoli has joined #openstack-meeting-311:05
*** dims has quit IRC11:07
*** baoli has quit IRC11:10
*** doug-fish has joined #openstack-meeting-311:10
*** vgridnev has quit IRC11:19
*** jtomasek has quit IRC11:22
*** markvoelker has joined #openstack-meeting-311:24
*** vgridnev has joined #openstack-meeting-311:27
*** markvoelker has quit IRC11:28
*** dims has joined #openstack-meeting-311:29
*** dims_ has quit IRC11:31
*** dims_ has joined #openstack-meeting-311:31
*** dims has quit IRC11:34
*** robcresswell has joined #openstack-meeting-311:35
*** yamamoto_ has quit IRC11:35
*** yamamoto has joined #openstack-meeting-311:36
*** jtomasek has joined #openstack-meeting-311:37
*** yamamoto has quit IRC11:37
*** yamamoto has joined #openstack-meeting-311:37
*** ajo\afk is now known as ajo11:38
*** kzaitsev_mb has quit IRC11:42
*** tfukushima has quit IRC11:42
*** jaypipes has joined #openstack-meeting-311:53
*** tsufiev has joined #openstack-meeting-311:54
*** doug-fish has quit IRC11:54
*** jschwarz has quit IRC11:55
*** betherly has joined #openstack-meeting-311:55
*** irenab has quit IRC11:55
*** pc_m_ has joined #openstack-meeting-311:57
*** tmazur has joined #openstack-meeting-312:00
*** r1chardj0n3s has joined #openstack-meeting-312:00
david-lyle#startmeeting Horizon12:00
openstackMeeting started Wed Aug 19 12:00:45 2015 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot.12:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:00
r1chardj0n3shullo12:00
*** openstack changes topic to " (Meeting topic: Horizon)"12:00
openstackThe meeting name has been set to 'horizon'12:00
fnordahlo/12:00
tsufievhello12:01
mrungehello o/12:01
betherlyhello o/12:02
*** kzaitsev_mb has joined #openstack-meeting-312:02
kzaitsev_mbo/12:03
david-lyleok, let's get rolling12:03
david-lyleFirst and foremost, L-3 is in 2 weeks12:04
*** doug-fish has joined #openstack-meeting-312:05
david-lyleand there's a lot hanging out there12:05
david-lyleof the top priorities on12:06
david-lyle#link https://etherpad.openstack.org/p/YVR-horizon-liberty-priorities12:06
david-lylewe're looking pretty meek12:06
david-lylewhat was JSCS and now eslint is finally all merged and voting in the gate12:07
david-lyleso that one was completed12:07
david-lyleI owe plugin documentation still :( which I will have ready for L12:08
robcresswellThe angular translation stuff is mostly there folowing a fix the other day, I believe, so thats good too.12:08
*** neillc has joined #openstack-meeting-312:09
neillchello12:09
*** tosky has joined #openstack-meeting-312:10
david-lyleright that's done too12:10
david-lyleslow because looking at status on those12:10
*** julim has joined #openstack-meeting-312:10
betherlyI am new to openstack and working with HP. Will probably be working on horizon panels for Ironic but have been talking to hurgleburgler re CSS theming stuff also. Definitely up for helping Horizon meet targets for L-3.12:10
*** killer_prince has quit IRC12:10
david-lyleif anyone has updates note them12:10
david-lylebetherly: a large part is reviews12:11
david-lylewe are very close on django 1.812:11
r1chardj0n3sI got a system up and running today so I can run the selenium suite using firefox, so hope to make progress on that...12:11
david-lylemrunge: is there anything else missing12:11
robcresswellI thought dj18 was now done?12:11
david-lyler1chardj0n3s: I got derailed on that yesterday by the horrid state of our docs build12:11
david-lylealmost done with patches to fix12:12
betherlydavid-lyle: ok great. If theres any urgent ones please do ping me but I will keep my eye on them12:12
robcresswellah12:12
mrungedavid-lyle, it's not yet voting on the gate12:12
david-lylerobcresswell: I have to release d-o-a12:12
*** ducttape_ has joined #openstack-meeting-312:12
r1chardj0n3sdavid-lyle: I'll be focusing on it if you want to focus on other stuff12:12
david-lylewhich I have a couple of patches I'm waiting on for d-o-a, 1 has 2 +2s and could merge, the other is related and further12:13
robcresswellbetherly: Best bet is to review patches on https://etherpad.openstack.org/p/YVR-horizon-liberty-priorities, although they may not be terribly accessible to newer reviewers. Pull code, check it doesnt explode horizon, and comment on anything that looks odd.12:13
david-lylemight have to release without it12:13
mrungeah yes, david-lyle d-o-a release is due for django-1.8 support, too12:13
robcresswellGotcha.12:13
david-lylethen make that the minimum version in g-r12:13
david-lylerunning out of time on that one12:13
betherlyrobcresswell: will do :) will have horizon up and running successfully soon then will get started12:14
robcresswellWe have 2 weeks yet. Still time.12:14
*** marios_ has joined #openstack-meeting-312:14
david-lyledependent library releases and g-r changes usually get locked 2 weeks ahead of release12:14
robcresswelldavid-lyle: What was the state of docs after your patches? More work needed? I'd seen the bugs before, but not prioritised it over things12:15
david-lyleso we're about at the limit12:15
robcresswellAh, I see.12:15
*** marios_ has quit IRC12:15
david-lylerobcresswell: just one more patch required to handle duplicate object definitions12:15
david-lylethen, I think we can turn on doc errors in the build to block like pep812:16
david-lyleI think12:16
david-lylewithout it, it's just a mess12:16
david-lyleany other priority items people want to mention?12:16
*** amotoki_ has joined #openstack-meeting-312:17
mrungewe had this patch from rdopiera about using ini based configs12:17
david-lyleerr, updates on said items12:17
ducttape_the recent changes in the nav should be corrected12:17
mrungesince a configuration change requires changes with installers: now or never12:17
tsufievalso I'd like to discuss the state of integration tests12:17
david-lylemrunge: I think that one's very late in the release for such a change12:17
david-lyleand there's no real migration path defined12:18
mrungeyupp, as I said: now or never12:18
david-lyleI'm happy to revisit in M12:18
ducttape_I think never might be a bit strong of a word12:18
ducttape_;)12:18
mrungeagreed ;-)12:18
ducttape_the nav thing needs some fixing, around display of large data amounts and the multi region login thing.... not seeing that on the list12:19
david-lylewe lost rdopiera and with him a lot of the momentum on that12:19
mrungeI know r1chardj0n3s wanted to look ad Radomirs patch. I must admit I stopped with it.12:19
mrungeyes12:19
*** belmoreira has joined #openstack-meeting-312:19
*** belmoreira has quit IRC12:19
david-lyleI still think it's a good idea overall, but needs more12:20
david-lyleducttape_: just the look, or is there a functional problem?12:20
mrungedavid-lyle, for reference, https://review.openstack.org/#/c/100521/12:21
doug-fishducttape_: do you have bugs to link? I'm not aware of what "the nav thing" is?12:21
* tsufiev steps in with making integration tests voting again12:21
mrungethis patch already has 2 +212:21
ducttape_https://bugs.launchpad.net/horizon/+bug/1485764  was the one I saw a couple of days ago12:21
openstackLaunchpad bug 1485764 in OpenStack Dashboard (Horizon) "left hand nav border color does not work on big tables" [Undecided,New] - Assigned to Diana Whitten (hurgleburgler)12:21
doug-fishthx12:21
ducttape_there is another one Diana is looking at for multi region login stuff (which does not apply to me, but seems important none the less)12:22
david-lylemrunge, I hadn't seen the other12:22
david-lylelet me look again12:22
*** sankarshan is now known as sankarshan_away12:22
mrungedavid-lyle, *thank you*12:22
mrungetsufiev, thanks for stepping up with integration tests12:23
mrungewe should think about, how to integrate them even more, to get a faster feedback12:23
david-lylemrunge: I put a -2 on it, so I can take another look12:23
mrungeok, awesome12:24
david-lyleducttape_: I think there's a fix on that one too12:24
tsufievmrunge, I'm waiting for Jenkins feedback on last patchset, all should pass except 2 Sahara tests12:24
david-lyles/fix/patch/12:24
david-lyletsufiev: yes, thank you, I've wandered away from that :(12:25
david-lylethe 2 sahara tests may be my issue12:25
tsufievdavid-lyle, mrunge, as I said before, even if that commit gets merged, w/o making integration tests voting again, they soon will be broken12:25
david-lylebut not entirely sure12:25
*** salv-orlando has joined #openstack-meeting-312:25
mrungeit's so easy to switch off integration tests. if we could get them into other gates, we would be safer12:25
r1chardj0n3smrunge: hey, sorry I got called away. I did look at Radomir's ini patch, and it seemed pretty complex, and I didn't have time to get into the full ramifications of moving from python to ini - I reckon a pretty broad review of operators / deployers configs would be needed before making such a change12:25
ducttape_+1 r1chardj0n3s12:26
mrunger1chardj0n3s, thanks anyways. I agree, this change is pretty disruptive with deployers12:26
*** matrohon has joined #openstack-meeting-312:26
toskywell, if the other tests are fixed, checking the failing Sahara tests would be easier12:26
tsufievdavid-lyle, perhaps, we should somehow split sahara integration tests into a separate job?12:26
r1chardj0n3s(then I got distracted by trying to fix the selenium suite ;)12:26
toskyit could be related to some change in the page structure, but I couldn't check before12:26
tsufievgiven that sahara is moved to contrib12:26
david-lylemrunge, tsufiev I understand the push to reenable, that said, even when enabled they have been fragile12:27
mrungehahaha r1chardj0n3s12:27
r1chardj0n3shey, half of it is fixed now, so that's a thing12:27
*** amotoki_ has quit IRC12:27
toskydavid-lyle: but not fixing them would make them always fragile12:27
tsufievdavid-lyle, yes, I found one cause of such fragility - the tests were relying on exact ordering of fields in forms12:27
r1chardj0n3sphantomjs is a no-go tho, 'cos we test file uploads and that's not supported in ghostdriver :(12:27
tsufievfixed that for forms, should be fixed as well for table actions12:27
david-lylesome wonderful people look at all the gate failures every day, and our integration tests create a ton that are hard to categorize which means it keeps requiring work every time they fail12:28
mrungeunfortunately, being fragile is the nature of tests running on top of the stack12:28
david-lylenot sure that needs to be true, but to a degree yes12:29
tsufievdavid-lyle, mrunge: also there is an idea about untying integration tests selectors from horizon layout and use some special 'selenium-*' classes12:29
david-lyletsufiev: I would like to see at least a week of no failures before making voting again12:30
david-lyleno, being a very small percentage12:30
david-lylethere will always be random failures12:30
tsufievdavid-lyle, what if the patch where they fail introduces the breakage?12:30
david-lylethen reviewers should be looking at that12:31
doug-fishdavid-lyle: I don't know how to track integration test failures - is that striaghtforward?12:31
r1chardj0n3s... and at the moment it's very difficult indeed to figure out why selenium tests break, which is something else I need to look at fixing12:31
david-lyleif we think they are fixed, that should be a review consideration12:31
david-lyledoug-fish: there is a log for the integration tests on check runs12:32
*** yamamoto has quit IRC12:32
*** salv-orl_ has joined #openstack-meeting-312:32
tsufievdavid-lyle, doug-fish: also there is patch in progress to save screenshots on failures12:32
doug-fishright, but is there a way to get a summary of what's failed over the last day for example?12:32
tsufievhttps://review.openstack.org/#/c/194646/12:32
david-lylecurrently it dumps the html source12:32
*** salv-orlando has quit IRC12:33
doug-fishyeah, I've seen that12:33
david-lyledoug-fish: oh12:33
r1chardj0n3syeah, the failurs I was debugging yesterday just said "500 Error" in the browser window12:33
r1chardj0n3sso yeah12:33
*** bharath has joined #openstack-meeting-312:33
david-lylehttp://status.openstack.org//elastic-recheck/12:33
r1chardj0n3sscreenshots will help tho12:33
david-lylewhich is why recheck # is important over just recheck12:33
*** mwagner_lap has joined #openstack-meeting-312:33
doug-fishwill the source remain available as well? (I haven't looked at the screen shot patch yet)12:34
doug-fishdavid-lyle: thanks!12:34
tsufievdoug-fish, yes, I think they're orthogonal12:34
david-lylebeyond that ... logstash.openstack.org12:34
doug-fish agreed12:34
tsufievunfortunately, while fixing integration tests locally, I didn't find the html source very helpful12:35
doug-fishdavid-lyle: so I'm loosely aware of both of those sites, but I can't quite put together how I'd check how many Horizon integration tests failed today12:35
tsufievthe most useful was python stacktrace + examining tests sourcecode in debugger12:35
doug-fishtsufiev: I've had cases where the source was helpful - I could see the test was looking for a particular element, but it wasn't present on the page12:36
tsufievdoug-fish, yes, it's possible to find it there... just too inconvenient :)12:37
*** bharath has quit IRC12:38
doug-fishdavid-lyle: no reason we have to sort though teaching me to use the tool available during our meeting time. I think I know some people I can ask.12:38
david-lyledoug-fish: we could build a query for logstash, I just can't on the fly in the meeting :)12:38
doug-fishunderstood. Thx!12:38
tsufievdavid-lyle, mrunge, doug-fish: I'm going to create a blueprint for integration tests hardening - all the things to make them less fragile12:38
david-lyletsufiev: great, thank you12:38
mrungethank you tsufiev12:39
robcresswellThere is an item on the agenda btw, someone has put up a bp, just looking at time :)12:39
david-lyleso other reviews on off the radar but could use help12:39
david-lyle#link https://etherpad.openstack.org/p/sahara-reviews-in-horizon12:39
david-lyleand12:39
david-lyle#link https://etherpad.openstack.org/p/trove-reviews-in-horizon12:40
*** markvoelker has joined #openstack-meeting-312:40
wimdcIt's mine. There's not much text in the bp really, but it would be great if I could get some guidance on how to proceed from here. There's also a bunch of code in gerrit. But I'm kinda stuck without the blueprint approved.12:40
david-lylereminder that with trove and sahara in /contrib, +1s from the service team can account for 1 +212:40
david-lyleso just one horizon core is needed to +2, +A12:40
david-lyleI will be getting back to those soon too12:41
*** julim has quit IRC12:41
david-lylesorry wimdc12:42
david-lyleso the bp linked is neutron, no?12:42
*** julim has joined #openstack-meeting-312:42
*** yamamoto has joined #openstack-meeting-312:43
david-lyleis there a corresponding Horizon bp?12:43
wimdcoh, did I copy the wrong link... lemme see12:43
*** tfukushima has joined #openstack-meeting-312:43
wimdcIt's supposed to be the implementation of that neutron link in horizon :)12:44
wimdchttps://blueprints.launchpad.net/horizon/+spec/port-allowed-address-pairs-extension12:44
wimdcupdated the page.12:45
david-lyleSeems like a reasonable addition to me12:45
doug-fishagreed12:46
robcresswellOh nice, looks like the code is all done12:46
david-lylethe python-neutronclient code seemed to have been merged long ago12:46
david-lyleso no dependency issues12:46
wimdcYea I gave it a -1 myself cause I need to update a small thing though.12:46
david-lyleok, updated the status of the bp12:47
robcresswellNice12:47
*** amotoki_ has joined #openstack-meeting-312:47
wimdcThanks12:47
*** yamamoto has quit IRC12:47
david-lyleI would ask amotoki kindly for a review12:47
*** tfukushima has quit IRC12:48
david-lylelet me rephrase, wimdc, you should ask amotoki kindly for a review12:48
amotoki_oh, i was moving. which review? I will check.12:49
david-lylehttps://blueprints.launchpad.net/horizon/+spec/port-allowed-address-pairs-extension12:49
wimdchttps://review.openstack.org/#/c/193079/ is the gerrit link.12:49
david-lyleah even better12:49
david-lylethanks amotoki_12:49
david-lyle10 minutes left. Other topics?12:50
tsufievdo we have plan B for Keystone changes and LDAP :)?12:50
mrungedrop keystone?12:51
* mrunge runs...12:51
david-lyleLOL12:51
mrungetsufiev, it seems, we can not really fix it directly12:51
r1chardj0n3slol12:51
mrungeI'm counting on integration of searchlight12:51
r1chardj0n3swon't searchlight fix it for us? /ducks12:51
r1chardj0n3ssnap mrunge12:51
david-lyletsufiev: short answer, no12:52
mrunge:P12:52
tsufievmrunge, yeah, that's why I think time to rethink UX there...12:52
ducttape_the issue w ldap and keystone is the searching / pagination - right?12:52
r1chardj0n3swe do have a bunch of places in the UI where we just blindly list users, where a search might be more appropriate12:52
david-lyleso searchlight would be useful if keystone didn't punt on pagination across hthe board12:52
tsufievducttape_, yes12:52
david-lyle*the12:52
mrungeducttape_, yes12:52
robcresswellHa, I very much enjoyed this discussion on the mailer.12:52
david-lylebecause you could take a project list and build from there12:52
ducttape_I can't imagine that many deployments would be ok with keeping a shadow copy of ldap in the searchlight db12:53
ducttape_for security reasons12:53
david-lylewith out anything available in a complete list, there's no way to  do that12:53
mrungeshut up ducttape_12:53
ducttape_just saying ;P12:53
mrungeit's probably good ;-)12:53
robcresswelllol12:53
david-lylethat's not really the request12:54
tsufievso we need a couple of jedis to convince Keystone folks )12:54
ducttape_attn: lhcheng12:54
mrungetsufiev, there is no pagination in ldap-backend12:54
david-lyleI want a map of the user project assignments in the searchlight12:54
mrungeso, keystone can not fix it12:54
doug-fishI'm not sure they can be convinced - without changes to LDAP they just can't do it12:54
david-lyledoug-fish: not sure if can't or won't12:54
david-lylebut yeah12:55
ducttape_here is what I would say, as alternative.....12:55
ducttape_users almost always have at least one role assignment12:55
mrungeI wonder if it'd be ok to keep a cache of results somewhere for a short lived time12:55
ducttape_use the role assignment stuff as a psuedo user listing12:55
david-lyleducttape_: the things is there's no part of the v3 API that supports pagination12:55
mrungewe should keep in mind, there are installs out there with 10k of users12:56
david-lyleso always an incomplete list12:56
david-lyle10k in elastic search is trivial12:56
r1chardj0n3sand Active Directory will error if you ask for > 1000 results12:56
r1chardj0n3sfiltering (roles, I think is what ducttape_ was getting at) is the only solution with AD12:56
david-lyleagain, users is not the only way to build such a list12:56
david-lyleI want the project list12:57
ducttape_yep, we are all saying same thing :D12:57
david-lyleand index from there12:57
david-lyleyeah12:57
tsufievr1chardj0n3s, btw, Horizon is not robust against that kind of errors. Encountered a customer bug with stripping users of their roles while updating project quotas12:57
r1chardj0n3syep12:57
r1chardj0n3stsufiev: I know :(12:57
r1chardj0n3stsufiev: we had a customer run smack into that too. fortunately we could hard-code an LDAP filter12:57
*** tosky has quit IRC12:57
david-lylewe could take a keystone type stance and say you shouldn't do identity management in Horizon12:58
r1chardj0n3soooh12:58
* david-lyle kidding12:58
doug-fishha!12:58
ducttape_lolwut12:58
r1chardj0n3sd'oh!12:58
david-lylesort of12:58
r1chardj0n3sdavid-lyle for emperor12:58
fnordahlhehe. openldap/ad does indeed have paging though. so keystone should be able to cope with it. i'll try to have a look at what they're doing.12:58
*** jcoufal_ has joined #openstack-meeting-312:58
tsufievthe domino effect for refusals )12:59
ducttape_horizon: helpful for 87% of your cloud interactions™®12:59
doug-fishtsufiev: r1chardj0n3s is there a bug open for the role-stripping issue?12:59
robcresswellducttape_: hahaa12:59
r1chardj0n3sdoug-fish: sorry, was some time ago12:59
tsufievdoug-fish, think we should create it, the problem is that's hard to reproduce12:59
tsufievwithout LDAP with >1k of users12:59
doug-fishoh I see13:00
*** ducttape_ has left #openstack-meeting-313:00
r1chardj0n3shm, actually, the problem we had wasn't role stripping, it was just a basic UI break because of the error returned for the >1k user request13:00
mrungefnordahl, not for every backend, at least, what I know13:00
mrungefnordahl, and that's the issue13:00
david-lylefood for thought for the afternoon meeting, with plugins building on the REST API we've recently built, does the disclaimer that you can't count on this for anything really hold13:00
tsufievr1chardj0n3s, interesting... https://bugs.launchpad.net/horizon/+bug/1434241 like that?13:00
openstackLaunchpad bug 1434241 in OpenStack Dashboard (Horizon) " Internal Server Error while updating project quota when using Keystone LDAP backend" [Undecided,New]13:00
david-lyleafternoon meeting being Horizon Blueprint Roundtable chat13:00
r1chardj0n3stsufiev: yep, that's the one13:01
*** irenab has joined #openstack-meeting-313:01
david-lyleat the alternating horizon meeting time13:01
david-lylebecause our time is up for now13:01
tsufievr1chardj0n3s, so there are at least 2 problems13:01
doug-fishyou're asking if our REST API is truely an API with expectations like stability, deprecation cycles, etc?13:01
david-lyleThanks everyone! Feel free to move to #openstack-horizon13:01
*** egallen has joined #openstack-meeting-313:01
david-lyledoug-fish: yes13:01
david-lyle#endmeeting13:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:01
openstackMeeting ended Wed Aug 19 13:01:54 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-08-19-12.00.html13:01
*** jcoufal has quit IRC13:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-08-19-12.00.txt13:01
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-08-19-12.00.log.html13:02
*** r1chardj0n3s has left #openstack-meeting-313:02
mrungethanks all13:02
*** wimdc has quit IRC13:02
*** neillc has left #openstack-meeting-313:02
*** tsufiev has left #openstack-meeting-313:03
*** doug-fish has quit IRC13:06
*** puranamr has joined #openstack-meeting-313:12
*** banix has joined #openstack-meeting-313:14
*** pc_m_ has quit IRC13:15
*** egallen_ has joined #openstack-meeting-313:17
*** egallen has quit IRC13:17
*** egallen_ is now known as egallen13:17
*** jckasper has quit IRC13:20
*** doug-fish has joined #openstack-meeting-313:21
*** doug-fish has quit IRC13:21
*** doug-fish has joined #openstack-meeting-313:22
*** doug-fish has quit IRC13:22
*** doug-fish has joined #openstack-meeting-313:23
*** doug-fis_ has joined #openstack-meeting-313:24
*** doug-fish has quit IRC13:28
*** dims_ has quit IRC13:29
*** tfukushima has joined #openstack-meeting-313:29
*** jpomeroy has joined #openstack-meeting-313:29
*** dims has joined #openstack-meeting-313:29
*** singlethink has joined #openstack-meeting-313:32
*** lblanchard has joined #openstack-meeting-313:36
*** moshele has joined #openstack-meeting-313:43
*** lazy_prince has joined #openstack-meeting-313:44
*** yamamoto has joined #openstack-meeting-313:46
*** yamamoto has quit IRC13:46
*** yamamoto has joined #openstack-meeting-313:46
*** yamamoto has quit IRC13:46
*** dboik has joined #openstack-meeting-313:46
*** yamamoto has joined #openstack-meeting-313:47
*** killer_prince has joined #openstack-meeting-313:49
*** jcoufal_ has quit IRC13:49
*** robcresswell has left #openstack-meeting-313:50
*** jcoufal has joined #openstack-meeting-313:51
*** lazy_prince has quit IRC13:52
*** singleth_ has joined #openstack-meeting-313:55
*** yamamoto has quit IRC13:56
*** yamamoto has joined #openstack-meeting-313:56
*** yamamoto has quit IRC13:56
*** sdake has joined #openstack-meeting-313:56
*** yamamoto has joined #openstack-meeting-313:57
*** nate_gone is now known as njohnston13:57
*** sankarshan_away is now known as sankarshan13:58
*** sdake_ has joined #openstack-meeting-313:58
*** singlethink has quit IRC13:58
*** neelashah has joined #openstack-meeting-313:59
*** vgridnev has quit IRC14:00
*** doug-fish has joined #openstack-meeting-314:00
*** sdake has quit IRC14:01
*** dboik has quit IRC14:02
*** sfinucan has joined #openstack-meeting-314:03
*** yamamoto has quit IRC14:03
ajoping irenab  :)14:03
*** doug-fis_ has quit IRC14:03
*** jlibosva has joined #openstack-meeting-314:03
irenabhi14:03
jlibosvahello14:03
*** jschwarz has joined #openstack-meeting-314:04
ajolet's wait a bit for ihar :)14:04
*** ihrachyshka has joined #openstack-meeting-314:04
jschwarzsorry for being late... seems like I need to be reminded every week ;-)14:04
ihrachyshkahi. ajo are you chairing?14:04
ajohi :)14:04
jlibosvayeah, I don't have reminder either, always forget :)14:04
ajoihrachyshka, let's co-chair, I'm aware of some points, and I guess you're aware of a few others14:04
ihrachyshkaajo, chairing is not about knowing14:04
ihrachyshka:)14:04
ajo#startmeeting neutron_qos14:05
openstackMeeting started Wed Aug 19 14:05:10 2015 UTC and is due to finish in 60 minutes.  The chair is ajo. Information about MeetBot at http://wiki.debian.org/MeetBot.14:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:05
*** openstack changes topic to " (Meeting topic: neutron_qos)"14:05
openstackThe meeting name has been set to 'neutron_qos'14:05
ihrachyshkado it, ping me when there is smth for me, I may be off sometimes14:05
ajoihrachyshka, let's start with an status update, may be you're better for that14:05
ihrachyshkaok14:05
ihrachyshka#topic where we are14:05
ihrachyshkaajo, gimme a co-chain14:05
ihrachyshka*chair14:05
ajo#topic where we are14:05
*** openstack changes topic to "where we are (Meeting topic: neutron_qos)"14:06
ajoihrachyshka how do I do that? :)14:06
ajo#help14:06
ihrachyshkanah, whatever14:06
ihrachyshkaso where we are.14:06
ihrachyshkawe merged into master on Mon14:06
moshelehi14:06
ihrachyshkameaning, feature/qos is about to retire and hooks cleaned up from project-config: https://review.openstack.org/21247514:06
jschwarz#addmeeting ihrachyshka14:06
jschwarz;-)14:06
jschwarzsorry, #addchair ihrachyshka14:07
ajo#addchair ihrachyshka14:07
ihrachyshkanow, during merge we disabled gating for qos because master lacked the hooks in project-config14:07
ajoihrachyshka++ :-)14:07
ajoeverybody++14:07
*** kbyrne has quit IRC14:07
ihrachyshkaso the critical thing is to enable the gating before we introduce a regression14:07
ajoNOTE: disabled gating means: no api tests or tempest14:07
*** timbyr_ has quit IRC14:07
ihrachyshkafirst, we tried to make it in devstack: https://review.openstack.org/21245314:08
ajofunctional, unit, and fullstack may be ok14:08
ihrachyshkabut folks requested a devstack plugin. so here we go: https://review.openstack.org/21424914:08
*** ajmiller has joined #openstack-meeting-314:08
*** jckasper has joined #openstack-meeting-314:08
ihrachyshkaI need to enable the qos api tests in that same patch to check it worked as expected. (afaik it did not though)14:08
ihrachyshkaajo, how do you know what will affect API?14:09
ihrachyshkaanyway... gating is the thing we need like yesterday.14:09
ihrachyshkaso apart from it...14:09
ihrachyshkaajo started to report bugs in LP. ajo link to qos tag?14:09
ajoihrachyshka: what do you mean by "what will affect API?"14:10
ihrachyshkanow if anything buggy qos related in the product, please report a bug and mark with 'qos' tag for ease of searching14:10
* ajo looks for the link14:10
ajo#link https://bugs.launchpad.net/neutron/+bugs?field.tag=qos  neutron qos bugs14:10
ihrachyshkaajo, I mean, that you can't ever be sure changing some code that it won't affect api tests.14:10
ihrachyshkathanks ajo14:10
ajoihrachyshka: that's true14:11
ihrachyshkaI saw people actively fix qos bugs and send reviews.14:11
*** killer_prince is now known as lazy_prince14:11
*** kbyrne has joined #openstack-meeting-314:11
ihrachyshkaI suggest all patches to have marked with bp/quantum-qos-api top or whatever relevant14:11
ajoihrachyshka: may be we should hold those until api-tests are re-enabled to avoid later head-aches?14:11
ihrachyshkaso that it shows up in reviewer dashboard for L14:11
ajosounds like a good idea14:11
ihrachyshkaajo, I think we should hold merges before gating, yes.14:11
ajoI will set my patches on-hold for that reason14:12
ihrachyshkaanyone apart from the owner can change topic, so please check your lists14:12
ihrachyshkaajo, ok. I hope people will mind. if it's something clearly agent side, I think we are good to merge.14:12
ihrachyshkaso server side is problematic14:12
ihrachyshkaok, what else... ah right. THANKS ALL FOR YOU GREAT WORK14:13
*** sdake_ is now known as sdake14:13
ihrachyshkait's a pleasure to work with you folks :)14:13
ajoihrachyshka: makes sense14:13
ihrachyshkaso ajo I think you can now move to specific discussions14:13
ihrachyshkaajo, while I clear some stuff in donwstream14:13
ajoso server/db/api side -> let's hold until api-tests are back14:13
*** jreeves has joined #openstack-meeting-314:14
mosheleit was  pleasure to work with you guys as well :)14:14
ajoyeah :-)14:14
ajook14:14
ajoso, may be we could go over a couple of bugs, and then irenab and I were talking about nova integration with nova flavors14:14
ajo#topic Bugs14:15
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)"14:15
*** Ramanjaneya has joined #openstack-meeting-314:15
ajofirst, this bug, I think it's important:14:15
*** betherly has left #openstack-meeting-314:15
ajo#link https://bugs.launchpad.net/neutron/+bug/148603914:15
openstackLaunchpad bug 1486039 in neutron "Setting a policy to a network will limit the router/dhcp/net-device ports, that's not expected" [Undecided,New]14:15
ajobasically14:15
ajoif we set a rule to "private-net"14:16
ajopolicy with a bw limit rule, I mean14:16
ajoand then you create the router, and the dhcp port is created...14:16
ajoboth the inner leg of the router will be BW limited, and the dhcp port will be bw limited too14:16
ajowhich is not expected14:16
*** shwetaap has joined #openstack-meeting-314:16
ajotherea are use cases, where the tenant or admin could want to explicitly limit some of the device ports (router legs, etc...)14:17
irenabajo: would filtering out network types device owners will be ok?14:17
ajoso all the agreggated network connection to the outside world is limited, etc...14:17
*** doug-fish has quit IRC14:17
jlibosvaajo: if there is a usecase like kevinbenton pointed out - would it make sense to *not* limit router by default and if needed, they can update port with --qos-policy-id ?14:17
ajoirenab: it depends on where we do it14:17
ajojlibosva, irenab , correct14:17
ajo*but*14:17
ajo(sec)14:18
ajoI had a distracting monkey ;)14:18
ajo-kid- :)14:18
ajothe issue comes when we put other rules in play14:18
ajofor example14:18
ajoDSCP marking of a private network, could be desired for the inner router leg, or the dhcp leg14:18
*** Ramanjaneya has quit IRC14:18
*** vgridnev has joined #openstack-meeting-314:18
ajoas... that would also prioritize those packets in the switch14:19
*** doug-fish has joined #openstack-meeting-314:19
ajo(expected if you set a network to have a qos policy with dscp marking)14:19
ajoso14:19
ajoI think that a possible solution14:19
*** vgridnev has quit IRC14:19
ajocould be to provide a separate qos_profile_id in the get_info_for_devices with the network qos_profile_id14:19
irenabsounds like we should have per rule type policy if to apply settings on network ports14:19
ajonetwork_qos_profile_id ? ...14:19
ajoand let the rule handler at low level decide14:20
ajoor the plugin14:20
ajo:)14:20
ajoas the rules are network objects...14:20
ajomay be we can add an attribute like "apply_to_network_devices"14:20
ajoand then that's clear for all the stack up/down14:21
ajoit's a funny bug :)14:21
*** pavel_bondar has joined #openstack-meeting-314:21
ajolots of corner cases14:21
irenabajo: by attribute you don’t mean API wise?14:21
ajoirenab: yes, internal implementation attribute in the neutron object14:22
*** bharath has joined #openstack-meeting-314:22
ajoQoSBandwidthLimitRule in this case14:22
*** sigmavirus24_awa is now known as sigmavirus2414:22
ajounder neutron.objects.qos14:22
ajonot stored in db14:22
ajojust a static attribute of the rule14:22
ajook, let's not spend time on design stuff, as long as we are aware of the corner cases, and we agree on how to handle it..14:23
irenabajo: So back to basic use case, once compute port is created without policy on network that has associated policy, the port will inherit it?14:23
ajoyes14:23
*** absubram has joined #openstack-meeting-314:23
ajothat boils down to the other bug14:23
irenabajo: can you share the link to this bug?14:23
ajofrom the spec, we said:14:24
ajo1) if port has no qos policy, the policy from network is used14:24
ajo2) if port has an specific policy, the network policy is overriden14:24
ajonow, the other:14:24
ajo#link https://bugs.launchpad.net/neutron/+bug/1486028 network policy changes propagation14:24
openstackLaunchpad bug 1486028 in neutron "If you attach a QoS policy to a network, agents handling the port networks are not notified" [Undecided,New]14:24
ajoif port updates are propagated, I'd also expect that to happen14:25
ajootherwise we'd be violating the eventual consistency with the model14:25
irenabajo: regarding this, I am not sure updatedpolicy should be applied on the existing bound ports14:25
ajoirenab, I'm quite convinced that it should be the case, otherwise the current spec is missleading14:26
*** bharath has quit IRC14:26
ajoif the model says that a network with a policy will have the ports with no policy  controlled by such network policy...14:26
irenabajo: spec update patch is not merged yet :-)14:26
ajothe system will be left in an unconsistent state14:26
ajoirenab: true, we need a +A ':)14:27
*** edleafe has quit IRC14:27
*** yamamoto has joined #openstack-meeting-314:27
*** yamamoto has quit IRC14:27
ajoany other opinion on network policy updates to agent?14:28
ajoihrachyshka, jlibosva , jschwarz , moshele ?14:28
*** yamamoto has joined #openstack-meeting-314:28
*** doug-fish has quit IRC14:28
*** edleafe has joined #openstack-meeting-314:29
jlibosvaI like item 1) in the bug :) We just need to be careful not to update ports with already assigned policy14:29
*** doug-fish has joined #openstack-meeting-314:29
jlibosvain given network14:29
ajoyes, that's mandatory :)14:29
ajootherwise the model is again unconsistent with the system :)14:29
jlibosvayes, consistency++14:29
jschwarzno opinions here14:30
ajook14:30
ajolet's move on14:30
ajo#link https://review.openstack.org/#/c/199112/ qos-spec update14:31
ajowe need a +A there14:31
irenabajo: I just think no policy can be on intension as well…14:31
irenabbut lets move on14:31
ajoirenab, then we will have to extend the model to block policies14:31
ajoirenab, otherwise at next vm boot... the state will be changed14:32
*** doug-fish has quit IRC14:32
*** vgridnev has joined #openstack-meeting-314:32
ajoirenab: like "disable port security" -> "disable qos policies"14:32
*** doug-fish has joined #openstack-meeting-314:32
ajoor something like that14:32
ajoin that case, I'd advise the tenant not to set a policy on the net, and do it per-port14:32
ajoI will ping mestery/armax about the +A14:33
irenabajo: I would prefer we provide ‘idiot proof’ support14:33
ajoirenab, but, if you leave policy: None on the port, network_policy = A later14:33
ajoand not update the port14:34
irenabanyway, as long as its well documented,  it ok14:34
ajothen...14:34
ajosomebody stops/starts the VM...14:34
ajoor it's migrated14:34
ajothe policy get's applied14:34
ajowe should document it well,14:34
ajoand if the no-policy case comes up... we find a way to do it14:34
irenabajo: probably you are correct about disable-qos-policy, so its feature for next version :-)14:35
ajo:)14:35
ajoI guess the other bugs don't need much discussion14:36
ajoso probably we can move to the nova integration14:36
ajo#topic nova integration via flavors14:36
*** openstack changes topic to "nova integration via flavors (Meeting topic: neutron_qos)"14:36
ajoirenab, the stage is yours :)14:37
*** doug-fish has quit IRC14:37
irenabwe started etherpad with initial ideas here: https://etherpad.openstack.org/p/qos-nova-neutron14:37
ajo#link https://etherpad.openstack.org/p/qos-nova-neutron initial ideas for neutron-nova integration on qos14:37
irenabThe use case is to associate qos policy with nova flavor, so that tenant can deploy VM and get qos configured without additional commands14:38
jlibosvairenab: why it can't be part during port creation for nova instance? It calls neutron api to create port, right?14:38
*** doug-fish has joined #openstack-meeting-314:38
irenabaccording to some available documentation, there is already the following that supposed to work:14:39
irenabnova-manage flavor set_key --name m1.small  --key quota:vif_inbound_average --value 1024014:39
*** VW_ has joined #openstack-meeting-314:39
irenabas we discussed with ajo, it maybe modified to nova-manage flavor set_key --name m1.small --key quota:vif_qos_policy --value <the-policy-id>14:40
*** tmazur has quit IRC14:40
ajoyes, the other will work for nova network, or for neutron without qos-plugin14:40
irenabI am not sure what quota means here14:40
ajoyeah, the specific key must be decided by the nova team14:40
sfinucanIIRC, that 'vif_qos_policy' only works with libvirt-kvm/qemu14:40
sfinucanWould you be removing this feature?14:40
ajosfinucan, not removing, nova-net probably needs it14:41
*** sdake_ has joined #openstack-meeting-314:41
ajothe day nova-net is deprecated: AKA never :)14:41
irenabsfinucan: ajo :so this one only for nova-network?14:41
ajovif_qos_policy is what we'd be adding14:41
sfinucanajo: OK, just checking :)14:41
ajosfinucan: I think it works with any tap port coming from a VM with KVM14:41
irenaband as jlibosva mentioned it should be sent to neutron port create14:42
ajoirenab^ , sorry14:42
ajoyes14:42
ajoI agree, if we attach a neutron qos policy id to the flavor14:42
jlibosvaah, sorry. I asked before I read the etherpad carefully :)14:42
ajothen , the ports could be created in such policy, *but*14:42
ajothere's an issue14:42
ajoI think port creation from nova happens with the tenant credentials14:42
irenabajo: previously you raised a valid point regarding ownership of the policy14:42
ajoand qos policies, could be admin, and not shared14:43
ajo(for example, not shared because you don't want tenants to attach ports to those specific policies, and raise the flavor limits..)14:43
ajoexample:14:43
ajoflavor mini = 1CPU, 2GB, 10Mbps egress14:43
ajoflavor cool = 2CPU, 4GB, 100Mbps egress14:43
*** neelashah has quit IRC14:43
ajouser creates instance in flavor mini...14:43
ajothen ... looks for the port and does14:44
ajoneutron port-update <port-id> --qos-policy "100mbps-policy-id"14:44
*** sdake has quit IRC14:44
ajocheating the cloud provider :)14:44
ajoso,14:44
ajoIMO, one way to prevent that, could be done via RBAC, but we need to explore that14:44
ajoor, to let the admin leave the policies as not-shared14:45
ajoad nova does call neutron after port creation, to set the policy, with admin credentials14:45
*** jcoufal_ has joined #openstack-meeting-314:45
ajoad->and14:45
ajonot sure wether that's possible or not14:45
*** moshele has left #openstack-meeting-314:45
ajoagain, in the current state, tenant could go and do14:46
ajoneutron port-update <port-id> --no-qos-policy14:46
irenabajo: so basically nova should query neutron for policy owner and either port create or port update should set it14:46
ajoI guess we would need to add business logic to disallow port detachment, when it's a non-shared policy14:46
ajoirenab: I mean, nova would call neutron with admin credentials, to set the policy14:46
irenabajo: and if the policy is owned by tenant?14:47
ajoirenab: then admin can set it too :)14:47
ajoadmin can do anything14:47
ajowell, anything that makes sense...14:47
ajohmmm14:47
ajothis comes to another bug,14:47
ajoI'm just seeing14:48
irenabajo: this if feature!14:48
ajolol14:48
ajo:)14:48
ajofeature: tenant-cheating-capability14:48
ajo:D14:48
*** jcoufal has quit IRC14:48
ajoin the current state, imagine the CSP uses the network qos_policy_id to enforce a policy to tenants14:48
ajotenants could just go, and... neutron net-update <my-net> --no-qos-policy14:48
ajobye policy! ;)14:48
ajoSo I guess, we may generally want to prevent a non-shared-policy to be detached by a tenant who does not own such policy14:49
*** Poornima has quit IRC14:49
ajodoes it make sense?14:50
ajoI will fill it in the tracker, we could throw it away later,14:50
ajolet's go back to nova-neutron integration14:50
ajoirenab: how do we do it? , probably we should arrange a meeting with nova guys14:50
ajoor ask for a timeslot in one of their meetings?14:51
irenabajo: sounds great. Lets just put more content on the etherpad so we can share prior to discussion. I will try to do it asap14:52
*** egallen has quit IRC14:52
irenabajo: what about nova scheduler guarante for qos?14:52
*** egallen has joined #openstack-meeting-314:52
ajoirenab: yes, we should start talking about other rules14:53
ajowe had DSCP in the line, anybody from comcast?14:53
ajoand we had BandwidthGuarantees14:53
ajoprobably to start with14:53
ajoBandwidth Guarantees may require cooperation from nova scheduler, when those are not "best effort"14:54
njohnstonHi!  Yes, would you like me to update that etherpad with some DSCP info?14:54
ajofor example, to not plug (SUM(ports, port.min_limit)>interface limit)14:54
ajonjohnston, etherpad is for nova-neutron integration only,14:55
ajonjohnston, for DSCP, do we have a RFE already?14:55
ajo(bug with RFE mark?14:55
irenabajo: this would fail too late, need ‘not schedule if (SUM(ports, port.min_limit)>interface limit)'14:55
ajoI know vhoward submited a spec, but not sure about the RFE14:55
ajoirenab: correct, we need nova to be aware, and schedule the instance to the right place14:55
ajoor..14:56
ajoeven the port14:56
ajoimagine you have , in sriov 2 PF ports, with 10G each14:56
ajoand you are requested to plug 4VFs with 5G min limit14:56
ajoif you plug the 4VFs to the first PF...14:56
ajothe limit won't be met14:56
ajoI mean, the guarantee won't be met14:56
ajoso it has to be node-aware and port aware...14:57
irenabajo: agree14:57
ajoand I guess, nova has to query neutron and ask about the policy14:57
ajoto gather info14:57
*** puranamr has quit IRC14:57
njohnstonajo: I will check with vhoward and if it isn't there we'll get that in ASAP14:57
*** yapeng has joined #openstack-meeting-314:58
*** egallen has quit IRC14:58
ajonjohnston, if there's an RFE, please ask him to tag it with the qos tag too14:58
*** vgridnev has quit IRC14:58
njohnstonwill do14:59
irenabajo: lets see if we can chat with nova guys regarding scheduler14:59
*** yapeng has left #openstack-meeting-314:59
ajonjohnston: https://bugs.launchpad.net/neutron/+bug/146835314:59
openstackLaunchpad bug 1468353 in neutron "QoS DSCP marking rule support" [Undecided,In progress] - Assigned to James Reeves (james-reeves5546)14:59
ajo:-)14:59
irenablooks like we need to brainstorm it first14:59
*** egallen has joined #openstack-meeting-314:59
*** vgridnev has joined #openstack-meeting-314:59
ajoirenab: makes sense15:00
ajooops15:00
ajowe're at the top of the hour15:00
ajolet's release the channel,15:00
*** geoffarnold has quit IRC15:01
ajothanks everybody, keep rocking! ;)15:01
ajo#endmeeting15:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:01
*** dims has quit IRC15:01
openstackMeeting ended Wed Aug 19 15:01:09 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
njohnstonthanks!15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-08-19-14.05.html15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-08-19-14.05.txt15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-08-19-14.05.log.html15:01
*** dims has joined #openstack-meeting-315:01
ajonjohnston: if you want to make advance for this cycle in L, I guess it's quite tight, given that FF is end of this month15:01
*** peristeri has quit IRC15:01
*** vgridnev has quit IRC15:01
irenabsorry, I have another meeting. Bye15:02
ajonjohnston: feel free to ask me anything regarding the development of this, even if it's not for this cycle, we could get it at the start of next one?15:02
ajoirenab: thanks :)15:02
jreevesajo: we've already done some coding work on that spec, and we have more to do now in our current sprint cycle15:03
*** dims_ has joined #openstack-meeting-315:05
*** sfinucan has quit IRC15:05
*** ajmiller_ has joined #openstack-meeting-315:05
*** dims has quit IRC15:06
*** ajmiller has quit IRC15:09
*** jlibosva has left #openstack-meeting-315:12
*** mickeys has joined #openstack-meeting-315:12
*** coolsvap|away is now known as coolsvap15:18
*** yamahata has joined #openstack-meeting-315:18
*** bpokorny has joined #openstack-meeting-315:18
*** dims_ has quit IRC15:19
*** dims has joined #openstack-meeting-315:19
*** vgridnev has joined #openstack-meeting-315:21
*** coolsvap is now known as coolsvap|away15:22
*** irenab has quit IRC15:22
njohnstonajo: yeah, if we miss the deadline for this we'll have it ready early on for Mitaka15:22
njohnstonajo: And thanks for all your support!15:22
*** doug-fish has quit IRC15:24
*** doug-fish has joined #openstack-meeting-315:24
*** ajmiller_ is now known as ajmiller15:27
*** irenab has joined #openstack-meeting-315:31
*** FallenPegasus has joined #openstack-meeting-315:37
*** vgridnev has quit IRC15:37
*** Swami has joined #openstack-meeting-315:41
*** nkrinner has quit IRC15:41
*** singleth_ has quit IRC15:41
*** Piet has quit IRC15:42
*** VW_ has quit IRC15:43
*** numan has quit IRC15:48
*** singlethink has joined #openstack-meeting-315:49
*** dims has quit IRC15:49
*** sdake_ is now known as sdake15:49
*** dims has joined #openstack-meeting-315:49
*** dims_ has joined #openstack-meeting-315:53
*** dims has quit IRC15:54
*** Sukhdev has joined #openstack-meeting-315:54
*** yapeng has joined #openstack-meeting-315:55
*** inc0 has joined #openstack-meeting-315:56
*** yapeng has quit IRC15:59
*** geoffarnold has joined #openstack-meeting-316:03
*** mestery has joined #openstack-meeting-316:04
*** irenab has quit IRC16:07
*** irenab has joined #openstack-meeting-316:08
*** carl_baldwin has joined #openstack-meeting-316:08
*** carl_baldwin has quit IRC16:08
*** Piet has joined #openstack-meeting-316:08
*** amandap has quit IRC16:09
*** bharath has joined #openstack-meeting-316:10
*** VW_ has joined #openstack-meeting-316:11
*** amandap has joined #openstack-meeting-316:12
*** ajmiller has quit IRC16:13
*** bharath has quit IRC16:15
*** ajmiller has joined #openstack-meeting-316:18
*** jcoufal_ has quit IRC16:18
*** FallenPegasus has quit IRC16:22
*** lazy_prince has quit IRC16:26
*** VW_ has quit IRC16:27
*** VW_ has joined #openstack-meeting-316:28
*** VW_ has quit IRC16:29
*** VW_ has joined #openstack-meeting-316:29
*** sankarshan is now known as sankarshan_away16:32
*** kzaitsev_mb has quit IRC16:37
*** pballand has joined #openstack-meeting-316:38
*** dims_ has quit IRC16:39
*** puranamr has joined #openstack-meeting-316:39
*** dims has joined #openstack-meeting-316:39
*** puranamr has quit IRC16:40
*** puranamr has joined #openstack-meeting-316:41
*** jtomasek has quit IRC16:46
*** vgridnev has joined #openstack-meeting-316:54
*** doug-fish has quit IRC16:56
*** doug-fish has joined #openstack-meeting-316:56
*** rhagarty has quit IRC17:03
*** rhagarty_ has quit IRC17:04
*** ivar-lazzaro has joined #openstack-meeting-317:04
*** rhagarty_ has joined #openstack-meeting-317:04
*** rhagarty has joined #openstack-meeting-317:04
*** inc0 has quit IRC17:04
*** mpmsimo has joined #openstack-meeting-317:07
*** mpmsimo has quit IRC17:10
*** rhagarty has quit IRC17:10
*** rhagarty has joined #openstack-meeting-317:10
*** mrmartin has quit IRC17:10
*** VW_ has quit IRC17:11
*** VW_ has joined #openstack-meeting-317:12
*** mestery has quit IRC17:14
*** SumitNaiksatam has quit IRC17:15
*** VW_ has quit IRC17:16
*** sdake_ has joined #openstack-meeting-317:17
*** VW_ has joined #openstack-meeting-317:17
*** natorious is now known as zz_natorious17:18
*** sdake has quit IRC17:20
*** jckasper has quit IRC17:20
*** sbalukoff has quit IRC17:24
*** mpmsimo has joined #openstack-meeting-317:25
*** singlethink has quit IRC17:26
*** puranamr has quit IRC17:27
*** puranamr has joined #openstack-meeting-317:27
*** shwetaap1 has joined #openstack-meeting-317:28
*** singlethink has joined #openstack-meeting-317:29
*** shwetaap has quit IRC17:30
*** jschwarz has quit IRC17:32
*** yamahata has quit IRC17:34
*** Piet has quit IRC17:35
*** Piet has joined #openstack-meeting-317:36
*** sridhar_ram has joined #openstack-meeting-317:36
*** sdake has joined #openstack-meeting-317:37
*** krtaylor has quit IRC17:37
*** zz_natorious is now known as natorious17:39
*** sdake_ has quit IRC17:40
*** Piet has quit IRC17:41
*** natorious is now known as zz_natorious17:45
*** Piet has joined #openstack-meeting-317:45
*** sdake has quit IRC17:47
*** ihrachyshka has quit IRC17:48
*** armax has joined #openstack-meeting-317:50
*** sdake has joined #openstack-meeting-317:51
*** zz_natorious is now known as natorious17:51
*** mickeyspiegel has joined #openstack-meeting-317:54
*** Sukhdev has quit IRC17:54
*** Sukhdev has joined #openstack-meeting-317:56
*** yamahata has joined #openstack-meeting-317:56
*** B_Smith has quit IRC17:57
*** mickeys has quit IRC17:57
*** mpmsimo has quit IRC17:58
*** singleth_ has joined #openstack-meeting-318:02
*** singlethink has quit IRC18:04
*** bharath has joined #openstack-meeting-318:06
*** jckasper has joined #openstack-meeting-318:06
*** njohnston is now known as nate_gone18:09
*** FallenPegasus has joined #openstack-meeting-318:11
*** puranamr has quit IRC18:13
*** krtaylor has joined #openstack-meeting-318:13
*** puranamr has joined #openstack-meeting-318:13
*** FallenPegasus has quit IRC18:16
*** Piet has quit IRC18:16
*** puranamr has quit IRC18:18
*** puranamr has joined #openstack-meeting-318:18
*** natorious is now known as zz_natorious18:18
*** VW_ has quit IRC18:20
*** geoffarnold has quit IRC18:20
*** VW_ has joined #openstack-meeting-318:20
*** mrmartin has joined #openstack-meeting-318:23
*** VW_ has quit IRC18:24
*** achippa has joined #openstack-meeting-318:27
*** stevemar has joined #openstack-meeting-318:28
*** geoffarnold has joined #openstack-meeting-318:31
*** bapalm has quit IRC18:31
*** yamamoto has quit IRC18:32
*** bapalm has joined #openstack-meeting-318:32
*** tfukushima has quit IRC18:33
*** banix has quit IRC18:33
*** jwang has quit IRC18:34
*** achippa has quit IRC18:38
*** achippa has joined #openstack-meeting-318:39
*** jwang has joined #openstack-meeting-318:40
*** Piet has joined #openstack-meeting-318:41
*** mpmsimo has joined #openstack-meeting-318:41
*** achippa_ has joined #openstack-meeting-318:42
*** tfukushima has joined #openstack-meeting-318:42
*** achippa has quit IRC18:43
*** kebray has joined #openstack-meeting-318:46
*** sbalukoff has joined #openstack-meeting-318:46
*** achippa_ has quit IRC18:46
*** tfukushima has quit IRC18:46
*** puranamr has quit IRC18:50
*** puranamr has joined #openstack-meeting-318:50
*** geoffarnold has quit IRC18:52
*** puranamr has quit IRC18:52
*** puranamr has joined #openstack-meeting-318:52
*** banix has joined #openstack-meeting-318:53
*** geoffarnold has joined #openstack-meeting-318:54
*** nate_gone is now known as njohnston18:54
*** stevemar has quit IRC19:07
*** VW_ has joined #openstack-meeting-319:07
*** nikhil_k_ has quit IRC19:13
*** neelashah has joined #openstack-meeting-319:15
*** nikhil_k has joined #openstack-meeting-319:17
*** mpmsimo has quit IRC19:18
*** VW_ has quit IRC19:18
*** VW_ has joined #openstack-meeting-319:18
*** Piet has quit IRC19:19
*** geoffarnold has quit IRC19:20
*** VW__ has joined #openstack-meeting-319:23
*** VW__ has quit IRC19:23
*** Sukhdev has quit IRC19:23
*** VW_ has quit IRC19:23
*** VW_ has joined #openstack-meeting-319:23
*** tqtran has joined #openstack-meeting-319:27
*** VW_ has quit IRC19:27
*** B_Smith has joined #openstack-meeting-319:29
*** yamamoto has joined #openstack-meeting-319:32
*** yamamoto has quit IRC19:38
*** Sukhdev has joined #openstack-meeting-319:43
*** robcresswell has joined #openstack-meeting-319:43
*** e0ne has joined #openstack-meeting-319:45
*** zz_natorious is now known as natorious19:45
*** e0ne has quit IRC19:47
*** tsufiev has joined #openstack-meeting-319:48
*** mickeyspiegel has quit IRC19:49
*** FallenPegasus has joined #openstack-meeting-319:49
*** belmoreira has joined #openstack-meeting-319:50
*** natorious is now known as zz_natorious19:52
*** tqtran is now known as tqtran_19:53
*** tqtran has joined #openstack-meeting-319:53
*** kzaitsev_mb has joined #openstack-meeting-319:54
*** tqtran_ has left #openstack-meeting-319:55
*** puranamr has quit IRC19:55
*** puranamr has joined #openstack-meeting-319:56
*** geoffarnold has joined #openstack-meeting-319:56
*** FallenPegasus has quit IRC19:56
*** pauloewerton has joined #openstack-meeting-319:59
*** crobertsrh has joined #openstack-meeting-319:59
*** TravT has joined #openstack-meeting-319:59
*** clu_ has joined #openstack-meeting-320:00
*** achippa has joined #openstack-meeting-320:00
david-lyle#startmeeting horizon-drivers20:01
openstackMeeting started Wed Aug 19 20:01:58 2015 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:02
*** openstack changes topic to " (Meeting topic: horizon-drivers)"20:02
openstackThe meeting name has been set to 'horizon_drivers'20:02
david-lylewas looking up name to use, forgot20:02
david-lyleanyone here?20:02
robcresswello/20:02
robcresswellsleepily20:02
bpokornyo/20:02
TravTo/20:02
tsufievo/20:02
*** e0ne has joined #openstack-meeting-320:02
crobertsrhhello/20:02
clu_hi20:03
tqtran[=_=]?20:03
tqtran[=_=]/20:03
tsufievtqtran, is it a sleepy smile?20:03
tqtranhehe cat like face20:04
david-lyleAlright, to rehash purpose briefly for those who don't bounce timezones20:04
*** achippa has quit IRC20:04
david-lyleWe voted and created this meeting to clean up the bp backlog20:05
david-lyleit's too big for one person to manage and there are many that are stale20:05
david-lylewe will use this meeting to review/update bps and help align the developers/reviewers20:05
david-lylethat's my summary20:06
david-lylewe held the first on last week at 1200 UTC20:06
david-lyleand went through approx 10 bps20:06
david-lyleculling some and approving others20:06
david-lylewhich I forgot to #info in the logs20:06
david-lyleremind me this week20:06
david-lyleWanted to tackle the mound of angular bps this week20:07
robcresswellAgenda: https://wiki.openstack.org/wiki/Meetings/HorizonDrivers#Agenda_for_August_19_2000_UTC20:07
david-lylerobcresswell: put together a nice list20:07
david-lyle#link https://wiki.openstack.org/wiki/Meetings/HorizonDrivers#Agenda_for_August_19_2000_UTC20:07
robcresswellIt's not exhaustive, so feel free to volunteer others, but I just thought it would get us started20:07
robcresswelloops, forgot the link.20:07
david-lyleno worries20:07
*** puranamr has quit IRC20:08
*** puranamr has joined #openstack-meeting-320:08
david-lyleI cleaned up a couple of those this morning because they were already completed :)20:08
tqtranty robcresswell!20:08
*** FallenPegasus has joined #openstack-meeting-320:08
david-lyle#info https://blueprints.launchpad.net/horizon/+spec/jscs-cleanup completed20:08
david-lyle#info https://blueprints.launchpad.net/horizon/+spec/babel-translate-inner-tags completed20:09
tqtranyep yep20:09
TravT:)20:09
david-lyleno point in talking about those now20:09
david-lylenot sure about order, so we'll just start at the top20:09
david-lyleI do have one greater question regarding the angular work20:10
*** mrmartin has quit IRC20:10
TravTThai, this is the one that you filed as a result of our brainstorming at the mid-cycle right?20:10
david-lylehttps://github.com/openstack/horizon/blob/master/openstack_dashboard/api/rest/__init__.py#L1720:10
*** mrmartin has joined #openstack-meeting-320:10
*** mrmartin has quit IRC20:10
david-lyleif we are creating a plugin environment and encouraging devs to use angular for plugins, how can this hold true?20:11
tqtranTravT: yes20:11
*** Piet has joined #openstack-meeting-320:11
TravTdavid-lyle: i remember when we add that... similar statement here: https://wiki.openstack.org/wiki/Horizon/RESTAPI20:12
TravTback when we did it, i believe there was the following reasoning:20:12
tqtrandavid-lyle: are horizon plugins are still consider part of horizon?20:12
david-lyleI remember it being added20:12
david-lyletqtran: good question20:12
*** woodster_ has joined #openstack-meeting-320:13
tqtranwow that was super bad grammar lol20:13
TravT1) The work was early and we weren't sure if we were putting in the right APIs.20:13
*** smccully has quit IRC20:13
david-lyleif not should we expect the plugin to duplicate say all the keystone logic it needs?20:13
david-lylethat seems silly20:13
david-lyletwo APIs for the same thing20:13
david-lylesame holds true for widget structure20:14
TravT2) We were worried about how long we'd have to keep the API constant, because things like Nova API can't ever go away.20:14
david-lyleI take kfox1111 as a example20:14
*** stevemar has joined #openstack-meeting-320:14
tqtrani think we can just remove the message? i don't think there is any code out there that is 100% fool proof20:15
david-lylewell it becomes a question of support20:15
TravTI think we need to start considering versioning then20:15
tqtran>< i see......20:15
*** lhcheng has joined #openstack-meeting-320:15
TravTadditive changes aren't generally a problem.20:16
david-lylewhat versions of horizon will the plugin work with20:16
david-lyleno additive changes are fine20:16
tqtranso versioning atm is controlled by horizon's python layer20:16
david-lylebut they should probably be versioned20:16
tqtranand the REST simply taps into that same python layer, does it need its own?20:16
david-lylemicroversioned, but versioned20:16
TravTbut once an API is supported, if you change how it behaves, then you have ramifications.20:16
david-lyletqtran: and API is a contract20:17
david-lyles/and/an20:17
david-lyleit will do this when I do this20:17
david-lylechange the behavior randomly and noone has any idea what's going on20:17
david-lyleand what to trust20:17
*** e0ne has quit IRC20:18
david-lyleof all the angular supporting code, fortunately that has been the most stable20:18
TravTthese APIs already will have some differences in data based on the deployment environment (e.g. diff service version)20:18
david-lylebut I think we should make a plan20:18
TravTso, that makes this already a little bit of a different beast to talk through20:18
tqtranhold on, our REST api atm is dependent on the python layer, which does version control20:19
tqtranare we doing to have to modify that python layer for versioning as well?20:19
david-lylethat's different20:19
tqtranok i see what you're saying....20:20
david-lylewe just need to make sure a plugin can figure out if it can talk to the Horizon REST layer20:20
david-lyleor if it's speaking something different20:21
david-lylebut let's get back to the main review, and revisit in the regular meeting, just wanted to plant the notion in peoples' minds20:21
tqtranok then our REST layer is tightly coupled with whatever version of horizon you are using20:21
tqtranok20:21
david-lyletqtran: yes or no :)20:21
tqtranyes20:21
david-lyleno?20:22
tqtrani just wanted to understand a bit better :P20:22
david-lyleok, reviewing https://blueprints.launchpad.net/horizon/+spec/angular-workflow-plugin20:22
TravTit wouldn't hurt to do a real review of all these and make sure they are written in an extensible way.  I think there might be a few spots on the angular side where the functions take positional arguments rather than an object with options.20:22
*** ducttape_ has joined #openstack-meeting-320:23
TravTdavid-lyle: re: https://blueprints.launchpad.net/horizon/+spec/angular-workflow-plugin20:23
david-lylehere's a case where WIP on the code means I have no f'n clue what's going on20:23
tqtranlooks like justin has started work on it alreay20:23
TravTthat is the result of about 6 of us brainstorming at the whiteboard at the mid-cycle20:23
jpomeroyyup, have something you can look at, just don't have anything documented, that's the only reason for the WIP20:24
tsufievtqtran, I have a question about priorities thing in this BP20:24
jpomeroyi assume we will want some developer doc with examples i mean20:24
tqtrantsufiev: shoot20:24
david-lylejpomeroy: that's fine20:24
david-lylejust always confuses me20:24
* david-lyle is easily confused20:24
tsufievtqtran, you aren't going to reuse the contribute-depends concept from pythonic horizon workflows, are you?20:25
*** julim has quit IRC20:25
tqtran0_0 i have no idea what "contribute-depends concept from pythonic horizon workflows" is, you mean like inheritance?20:25
david-lyleI actually think the bp is reasonable, but I feel like it's definitely an M item20:25
tqtranyes agree20:26
tsufievbecause this priorities seem pretty arbitrary for the different steps of the same workflows... perhaps I missing how the new Angular workflows are going to work...20:26
david-lyle#info only 2 weeks in L-320:26
tqtranbasically, it lets you "inherit" and override/add/edit workflow steps20:26
robcresswelltqtran: I have a lot of +2s for code that does that20:27
david-lyletqtran: I'm guess tsufiev is saying two plugins could have priority 220:27
david-lyledepending on source20:27
tsufievtqtran, okay, I was thinking about workflows as a thing that pipelines steps so that a successive step is dependent on the data provided by previous20:27
tsufievand here the ordering comes20:27
tqtranah gotcha20:28
david-lyleblue and red may both be third parties20:28
*** singlethink has joined #openstack-meeting-320:28
tsufievdavid-lyle, and yes, nobody could restrict to declare the same priority )20:28
*** Piet has quit IRC20:29
tqtranyes, so the load order is important, so need to name your files in a way to ensure this load order20:29
tqtranmuch like our enabled files today20:29
*** e0ne has joined #openstack-meeting-320:29
tqtranas for dependent steps, angular has event propagation like DOM event propagation via $emit20:30
TravTthe data aspect is very interesting actually.  why the contribute depends is a good concept is that the steps may change in the base workflow you are extending, but often it is some data that you need to ensure is available.20:30
tqtranso dependent steps would get a chance to do something, it shouldn't be an issue20:30
tqtranwell, if the base step changes, you'd have to update your code.... thats just how it goes i think20:31
jpomeroycan't dependent steps just set up a $watch on the data?20:31
*** singleth_ has quit IRC20:31
tsufievtqtran, I got your point, need to examine it more carefullly - atm I'm not very familiar with modern angularized Horizon20:32
TravThere's my question: will this be far enough along in a few weeks that we'd want to support it forever?  Or should it delay to M?20:32
tqtrani vote for delay20:32
david-lyledelay20:32
tqtranits too rushed, 2 weeks is not enough time to hash out stuff20:32
david-lylewhich I already added to the comments20:32
*** Piet has joined #openstack-meeting-320:32
TravTi vote that too, mainly because I know I won't personally have time to put a lot of thought into it in the next few weeks.20:33
david-lyledo we want to approve or move to discussion?20:33
david-lyleI think the majority is in place20:33
david-lylebp wise20:33
*** mpmsimo has joined #openstack-meeting-320:33
david-lylesome implementation details are left to be figured out20:33
TravTjpomeroy, dissent?20:34
jpomeroyi did not realistically expect it to make L20:34
robcresswellagree with delay, I think the bp idea is okay, but implementation may need discussion...?20:34
david-lyleI ranked it High20:34
jpomeroydelay to M makes sense to me20:34
david-lylebut will approve unless there are objections20:35
robcresswellgo ahead20:35
TravTno, we'll figure out more details during code review.20:35
tqtranno objection20:35
*** e0ne has quit IRC20:35
david-lyle#info https://blueprints.launchpad.net/horizon/+spec/angular-workflow-plugin approved for Mitaka20:35
david-lyleok, next20:36
TravTi don't see a series goal on it?20:36
*** e0ne has joined #openstack-meeting-320:36
david-lyle#link https://blueprints.launchpad.net/horizon/+spec/angularize-identity-projects20:36
david-lyleTravT: on whiteboard, mitaka isn't a choice yet20:36
tqtranM isn't on the list yet20:36
*** VW_ has joined #openstack-meeting-320:36
*** VW_ has quit IRC20:38
david-lyleSo I don't think we have a reusable pattern fully in place yet to approve the projects panel angularization20:38
*** VW_ has joined #openstack-meeting-320:38
tqtranyeah, still working on that, i'm close to having something for review, we're close but not quite there yet20:39
*** geoffarnold has quit IRC20:40
david-lyleI favor pushing this bp until we have the standard20:40
pauloewertonmaybe we could consider pushing through the code for the panel enablement and table?20:41
pauloewertonin a same fashion as the users and images table20:41
TravTi'm not sure what all is missing from projects panel?20:41
pauloewertonTravT, the workflows basically20:41
tqtranright, the table code is all there20:41
tqtranjust the actions is missing20:41
david-lyleso what do I do with the table code?20:42
TravThave you looked at using the existing actions?20:42
*** VW_ has quit IRC20:42
pauloewertonyeah, I'm following the same pattern in https://review.openstack.org/#/c/202315/ for the actions20:42
david-lylethe big push for angular in tables was uniform filtering, sorting and pagination. Is that supported?20:43
david-lyleacknowledging that for v3 projects pagination is not possible20:43
tqtranyes, filtering sorting and paging all supported but also all client-side atm20:44
david-lylewhen I drop the 800 lines of code into the tree what do I get?20:44
*** belmoreira has quit IRC20:44
david-lyleI go back to this because there are few people doing active maintenance on horizon currently, and as one of them, I'm not excited about more work for uncertain gains20:45
david-lyleI think we've lost some focus on what we were doing and went all shotgun approach20:46
tqtranso we gave a demo of this a while back, the actions that you perform are extremely fast20:46
david-lyleall over the place and not really hitting the mark20:46
tsufievdavid-lyle, users, iirc20:46
tqtranright now, it doesn't seem like we're gaining much, but that is because of the infra and design work we are putting in to ensure quality20:46
TravTresponsive table, table drawers with extra info, etc20:46
TravTbut, my question goes back to what you asked david-lyle, can we use existing django actions / details pages20:47
TravTand then replace them gradually20:47
tqtranas i said, by the end of the week, i'll have something you can test out and see for yourself20:47
david-lyleTravT, it's just routing, I wouldn't see why not20:47
TravTso we focus on table without having to do complete panel.20:47
*** FallenPegasus has quit IRC20:48
david-lyletqtran: and that's fine, I think the users table was already approved as a bp20:48
david-lyleand that was it's purpose to define the pattern and infrastructure20:48
tqtranok i see what you're getting at20:48
ducttape_is the responsive table thing a css thing?  will css styles be the same across both?20:48
david-lyleit hides columns on resize20:49
david-lylecollapses the view, but leaves the actions available20:49
TravTit also has the hidden data show up in the table drawer when expanded20:49
TravTimages table does anyway...20:49
TravTusers table actually does not.20:50
ducttape_seems helpful for all the tables, maybe a can of worms.  but having two different experiences on pages is going to be wonky w users20:50
david-lylethere is no more data for users20:50
TravTI'm talking when resizing.20:50
TravTso if you have columns A - G20:50
TravTyou put a responsive priority on say EFG to disappear first.20:50
*** armax has quit IRC20:51
TravTand in the table drawer, you have that same data remain hidden with the same responsive priority20:51
ducttape_I guess that css could be added to older pages too?  stuff where responsive is more important than going through the angular rewrite pain20:51
TravTso, when you resize the screen, columns EFG go away, but the data is still visible by expanding the table drawer.20:51
tqtranso going back, i guess the question is, do we want to wait on approval until the pattern and infra work are in place? or is it ok to allow other works to go in parallel?20:51
david-lyletqtran: other work can progress, but I don't really want it in tree until we have a baked format20:52
david-lyleor we'll lose another release to moving all the files and refactoring again20:52
tqtranso going back to the feature branch idea?20:52
david-lyleit can remain straight patches too, but I think the functionality should forklift in when ready20:53
david-lylethat could be at the view level even20:54
*** geoffarnold has joined #openstack-meeting-320:54
tqtransorry im not following, what do you mean by straight patches? and forklift?20:54
TravTpatch dependencies20:54
david-lyletqtran: normal patch vs feature branch20:54
tqtranok20:55
david-lyleand complete feature dropped in20:55
david-lylenot an approximation20:55
david-lylethat hits and misses20:55
tqtrangot it20:56
david-lyleI have an almost ready launch instance workflow to demonstrate what I don't want to happen20:56
robcresswellheh20:56
TravTprogress?20:56
robcresswellIs Launch Instance going to be ready for L?20:56
david-lylebecause there is a ton of great work in there, that isn't quite ready to use20:56
david-lyleand it's idle20:57
lhchengIs anyone looking at the bugs reported?20:57
TravTspeaking of which robcresswell, did you open a BP on the add network workflow?20:57
TravTis that on your list?20:57
*** VW_ has joined #openstack-meeting-320:57
david-lyleMy vote is to push projects panel angularization to M too until we are relatively sure we have a solid framework and example to build from20:58
tqtranI'm fine with that20:58
robcresswellTravT: It is, Matt spoke to me about it last week20:59
david-lyledoesn't mean there's not good work in it and that it won't be valuable, but I want to set up a path for greater progress and success20:59
robcresswelldavid-lyle: Agreed20:59
*** armax has joined #openstack-meeting-320:59
tqtranso how will review for it work, do we hold off until the complete feature is there?20:59
*** mpmsimo has quit IRC20:59
*** neelashah has quit IRC20:59
robcresswellHave we agreed to use feature branches now btw?20:59
TravTno21:00
david-lyletqtran: if people want to review and provide feedback, even if it's looks like you're on the right track, there's value in that21:00
tqtranthat depends on dave's answer to he question above lol21:00
TravTrobcresswell, we discussed at mid cycle21:00
robcresswellAh, okay21:00
david-lylebut I don't want to merge it until done21:00
TravTfeature branches didn't seem necessary, yet21:00
david-lylerobcresswell: I'm in favor others aren't, both are workable21:01
robcresswellInteresting21:01
david-lylebygones21:01
*** jmckind has joined #openstack-meeting-321:01
robcresswellsure21:01
robcresswellwe're out of time21:01
robcresswellI've carried over the other bps to next weeks agenda, if that seems okay?21:01
*** jpomeroy has quit IRC21:01
david-lyle#info https://blueprints.launchpad.net/horizon/+spec/angularize-identity-projects approved but pushed to Mitaka pending the finalized users panel as example21:02
tqtranlol we only covered like 3 bps? hahaha21:02
robcresswellpsh :p21:02
robcresswellLast week we managed about 15 haha21:03
TravTthey were more about things that were old, though right?21:03
TravTnot active development ones21:03
robcresswellYeah21:03
david-lylebut most of those were stale or less controversial yea21:03
TravTend of release is always hard.21:04
robcresswellI've updated list for next week.21:04
robcresswellOh yeah. Its review mania time now.21:04
david-lyleThanks everyone! I hope people find this useful. It is much better than just me trying to walk through all of them on my own21:04
TravT+121:04
*** mickeys has joined #openstack-meeting-321:04
david-lyle2 weeks people for L21:04
tqtranThanks for going over them!21:04
david-lyledid I say that already21:04
david-lyle?21:04
david-lyle#endmeeting21:04
tqtrangot my seat belt on21:04
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:04
openstackMeeting ended Wed Aug 19 21:04:41 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:04
robcresswellThanks for meeting guys21:04
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon_drivers/2015/horizon_drivers.2015-08-19-20.01.html21:04
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon_drivers/2015/horizon_drivers.2015-08-19-20.01.txt21:04
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon_drivers/2015/horizon_drivers.2015-08-19-20.01.log.html21:04
*** VW_ has quit IRC21:04
*** stevemar has quit IRC21:05
*** VW_ has joined #openstack-meeting-321:05
*** ducttape_ has left #openstack-meeting-321:05
*** mpmsimo has joined #openstack-meeting-321:05
*** pauloewerton has left #openstack-meeting-321:06
*** mickeyspiegel has joined #openstack-meeting-321:06
*** tsufiev has left #openstack-meeting-321:06
*** lhcheng has left #openstack-meeting-321:06
*** mickeys has quit IRC21:08
*** lblanchard has quit IRC21:13
*** amotoki_ has quit IRC21:14
*** e0ne has quit IRC21:15
*** krtaylor has quit IRC21:18
*** e0ne has joined #openstack-meeting-321:19
*** crobertsrh is now known as _crobertsrh21:19
*** mpmsimo has quit IRC21:20
*** mpmsimo has joined #openstack-meeting-321:22
*** geoffarnold has quit IRC21:23
*** geoffarnold has joined #openstack-meeting-321:24
*** e0ne has quit IRC21:28
*** mpmsimo has quit IRC21:33
*** jpomeroy has joined #openstack-meeting-321:33
*** vgridnev has quit IRC21:35
*** njohnston is now known as nate_gone21:37
*** Piet has quit IRC21:38
*** Sukhdev has quit IRC21:43
*** s3wong has joined #openstack-meeting-321:44
*** sambetts has quit IRC21:51
*** sambetts has joined #openstack-meeting-321:51
*** doug-fish has quit IRC21:53
*** krtaylor has joined #openstack-meeting-322:00
*** shwetaap1 has quit IRC22:00
*** Swami has quit IRC22:02
*** absubram has quit IRC22:03
*** mrunge has quit IRC22:04
*** geoffarnold has quit IRC22:05
*** geoffarnold has joined #openstack-meeting-322:06
*** singlethink has quit IRC22:13
*** Sukhdev has joined #openstack-meeting-322:13
*** btully has joined #openstack-meeting-322:13
*** amotoki_ has joined #openstack-meeting-322:14
*** mickeyspiegel has quit IRC22:15
*** mickeys has joined #openstack-meeting-322:18
*** amotoki_ has quit IRC22:19
*** egallen has left #openstack-meeting-322:22
*** Piet has joined #openstack-meeting-322:28
*** mwagner_lap has quit IRC22:32
*** mickeys has quit IRC22:35
*** mickeys has joined #openstack-meeting-322:36
*** FallenPegasus has joined #openstack-meeting-322:36
*** sridhar_ram1 has joined #openstack-meeting-322:38
*** sridhar_ram has quit IRC22:39
*** mpmsimo has joined #openstack-meeting-322:39
*** mpmsimo has quit IRC22:40
*** FallenPegasus has quit IRC22:41
*** ajmiller_ has joined #openstack-meeting-322:46
*** mickeyspiegel has joined #openstack-meeting-322:46
*** mickeys has quit IRC22:49
*** ajmiller has quit IRC22:49
*** baoli has joined #openstack-meeting-322:51
*** Piet has quit IRC22:53
*** baoli has quit IRC22:56
*** geoffarnold has quit IRC22:57
*** mickeyspiegel has quit IRC23:00
*** VW_ has quit IRC23:00
*** mickeys has joined #openstack-meeting-323:00
*** VW_ has joined #openstack-meeting-323:01
*** VW_ has quit IRC23:02
*** banix has quit IRC23:02
*** btully has quit IRC23:02
*** VW_ has joined #openstack-meeting-323:02
*** tfukushima has joined #openstack-meeting-323:03
*** Sukhdev has quit IRC23:05
*** mpmsimo1 has joined #openstack-meeting-323:10
*** Piet has joined #openstack-meeting-323:12
*** amotoki_ has joined #openstack-meeting-323:15
*** mwagner_lap has joined #openstack-meeting-323:19
*** amotoki_ has quit IRC23:19
*** kzaitsev_mb has quit IRC23:29
*** geoffarnold has joined #openstack-meeting-323:29
*** banix has joined #openstack-meeting-323:31
*** flwang1 has quit IRC23:32
*** kzaitsev_mb has joined #openstack-meeting-323:32
*** Piet has quit IRC23:33
*** dims_ has joined #openstack-meeting-323:33
*** geoffarnold has quit IRC23:34
*** geoffarnold has joined #openstack-meeting-323:34
*** dims has quit IRC23:36
*** Piet has joined #openstack-meeting-323:37
*** kzaitsev_mb has quit IRC23:38
*** dims_ has quit IRC23:39
*** dims has joined #openstack-meeting-323:39
*** puranamr has quit IRC23:39
*** mpmsimo1 has quit IRC23:40
*** dims has quit IRC23:44
*** kebray has quit IRC23:47
*** Piet has quit IRC23:47
*** ajmiller_ has quit IRC23:51
*** elmiko-phone has joined #openstack-meeting-323:52
*** Piet has joined #openstack-meeting-323:53
*** geoffarn_ has joined #openstack-meeting-323:53
*** bharath has quit IRC23:54
*** geoffarnold has quit IRC23:54
sc68calwho's around for the fwaas meeting?23:57
*** flwang1 has joined #openstack-meeting-323:57
mickeysHi23:58
sc68cal#startmeeting networking_fwaas23:59
openstackMeeting started Wed Aug 19 23:59:45 2015 UTC and is due to finish in 60 minutes.  The chair is sc68cal. Information about MeetBot at http://wiki.debian.org/MeetBot.23:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.23:59
*** openstack changes topic to " (Meeting topic: networking_fwaas)"23:59
openstackThe meeting name has been set to 'networking_fwaas'23:59

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