Tuesday, 2014-04-01

*** eghobo has quit IRC00:03
*** mfer has joined #openstack-meeting-300:08
*** banix has joined #openstack-meeting-300:09
*** mfer has quit IRC00:32
*** mfer has joined #openstack-meeting-300:33
*** banix has quit IRC00:37
*** peristeri has joined #openstack-meeting-300:37
*** banix has joined #openstack-meeting-300:38
*** xuhanp has joined #openstack-meeting-300:39
*** mfer has quit IRC00:43
*** markmcclain has quit IRC00:45
*** markmcclain has joined #openstack-meeting-300:53
*** Sukhdev has quit IRC00:58
*** zigo has quit IRC00:59
*** zigo has joined #openstack-meeting-301:01
*** xuhanp has quit IRC01:08
*** banix has quit IRC01:10
*** SumitNaiksatam has joined #openstack-meeting-301:23
*** peristeri has quit IRC01:45
*** garyduan has quit IRC01:56
*** gduan has joined #openstack-meeting-301:56
*** zehicle_at_dell has joined #openstack-meeting-302:03
*** zehicle has quit IRC02:15
*** banix has joined #openstack-meeting-302:19
*** banix has quit IRC02:24
*** amotoki_ has quit IRC02:30
*** tedchang has quit IRC02:38
*** david-lyle has joined #openstack-meeting-302:44
*** markmcclain has quit IRC02:59
*** lcheng has joined #openstack-meeting-303:06
*** yamahata has joined #openstack-meeting-303:13
*** alexpilotti has joined #openstack-meeting-303:40
*** banix has joined #openstack-meeting-303:42
*** eghobo has joined #openstack-meeting-303:44
*** alexpilotti has quit IRC03:52
*** lcheng has quit IRC04:03
*** banix has quit IRC04:50
*** rand738 has quit IRC04:52
*** rand738 has joined #openstack-meeting-304:53
*** saju_m has joined #openstack-meeting-306:21
*** tmazur has joined #openstack-meeting-306:33
*** Zhenguo has joined #openstack-meeting-306:41
*** Zhenguo has quit IRC06:42
*** mrunge has joined #openstack-meeting-306:56
*** jtomasek has joined #openstack-meeting-307:01
*** lpetrut has joined #openstack-meeting-307:08
*** jcoufal has joined #openstack-meeting-307:16
*** ttrifonov_zZzz is now known as ttrifonov07:25
*** MaxV_ has joined #openstack-meeting-307:39
*** MaxV_ has quit IRC07:39
*** eghobo has quit IRC07:45
*** MaxV_ has joined #openstack-meeting-308:01
*** saju_m has quit IRC08:43
*** Zhenguo has joined #openstack-meeting-308:50
*** d0ugal_ has quit IRC08:53
*** d0ugal_ has joined #openstack-meeting-308:53
*** d0ugal_ is now known as d0ugal08:54
*** d0ugal has quit IRC08:54
*** d0ugal has joined #openstack-meeting-308:54
*** d0ugal has quit IRC08:54
*** d0ugal has joined #openstack-meeting-308:54
*** saju_m has joined #openstack-meeting-308:56
*** Zhenguo has quit IRC09:02
*** overlayer has joined #openstack-meeting-309:07
*** zhenguo has joined #openstack-meeting-309:10
*** lpetrut has quit IRC09:13
*** jcoufal has quit IRC09:18
*** lpetrut has joined #openstack-meeting-309:20
*** zhenguo has quit IRC09:22
*** lpetrut has quit IRC09:43
*** jcoufal has joined #openstack-meeting-309:50
*** david-lyle has quit IRC09:55
*** lpetrut has joined #openstack-meeting-310:04
*** safchain has joined #openstack-meeting-310:10
*** tmazur has quit IRC10:12
*** yamahata has quit IRC10:24
*** overlayer has quit IRC10:26
*** overlayer has joined #openstack-meeting-310:31
*** overlayer has quit IRC10:34
*** overlayer has joined #openstack-meeting-310:40
*** overlayer has quit IRC10:42
*** overlayer has joined #openstack-meeting-310:45
*** MaxV_ has quit IRC10:45
*** MaxV_ has joined #openstack-meeting-310:53
*** overlayer has quit IRC10:59
*** alexpilotti has joined #openstack-meeting-311:34
*** saju_m has quit IRC11:44
*** d0ugal has quit IRC11:51
*** d0ugal has joined #openstack-meeting-311:51
*** akrivoka has joined #openstack-meeting-311:56
*** saju_m has joined #openstack-meeting-311:57
*** mrunge has quit IRC11:59
*** saju_m has quit IRC12:02
*** overlayer has joined #openstack-meeting-312:10
*** amotoki has quit IRC12:11
*** nacim has joined #openstack-meeting-312:13
*** overlayer has quit IRC12:18
*** tedchang has joined #openstack-meeting-312:20
*** saju_m has joined #openstack-meeting-312:21
*** saju_m has quit IRC12:23
*** markmcclain has joined #openstack-meeting-312:28
*** saju_m has joined #openstack-meeting-312:40
*** zhenguo has joined #openstack-meeting-312:43
*** overlayer has joined #openstack-meeting-312:47
*** lblanchard has joined #openstack-meeting-312:49
*** overlayer has quit IRC12:54
*** zhenguo has quit IRC12:54
*** rand738 has quit IRC13:08
*** rand738 has joined #openstack-meeting-313:08
*** saju_m has quit IRC13:15
*** zehicle_at_dell has quit IRC13:19
*** peristeri has joined #openstack-meeting-313:27
*** saju_m has joined #openstack-meeting-313:28
*** xuhanp has joined #openstack-meeting-313:30
*** julim has joined #openstack-meeting-313:38
*** russellb has joined #openstack-meeting-313:38
*** mrunge has joined #openstack-meeting-313:38
*** mwagner_zzz has quit IRC13:40
*** markmcclain has quit IRC13:45
*** banix has joined #openstack-meeting-313:52
*** lenrow has quit IRC13:53
*** lcostantino has joined #openstack-meeting-313:53
*** lenrow has joined #openstack-meeting-313:54
*** nacim has quit IRC14:04
*** saju_m has quit IRC14:14
*** markmcclain has joined #openstack-meeting-314:21
*** david-lyle has joined #openstack-meeting-314:35
*** jpomero has joined #openstack-meeting-314:53
*** pbelanyi has joined #openstack-meeting-314:59
*** devlaps has joined #openstack-meeting-315:00
*** TravT has joined #openstack-meeting-315:04
*** jpich has joined #openstack-meeting-315:05
*** jcoufal has quit IRC15:18
*** zehicle has joined #openstack-meeting-315:19
*** cjellick has joined #openstack-meeting-315:22
*** alexpilotti has quit IRC15:22
*** nacim has joined #openstack-meeting-315:26
*** zehicle has quit IRC15:26
*** zehicle has joined #openstack-meeting-315:27
*** cjellick has quit IRC15:32
*** cjellick has joined #openstack-meeting-315:38
*** xuhanp has quit IRC15:38
*** pbelanyi has left #openstack-meeting-315:40
*** mfer has joined #openstack-meeting-315:41
*** mrunge has quit IRC15:47
*** jcoufal has joined #openstack-meeting-315:48
*** akrivoka has quit IRC15:49
*** cjellick has quit IRC15:49
*** ttrifonov is now known as ttrifonov_zZzz15:51
*** cjellick has joined #openstack-meeting-315:51
*** clu_ has joined #openstack-meeting-315:56
*** doug-fish has joined #openstack-meeting-315:58
*** akrivoka has joined #openstack-meeting-315:59
*** tzumainn has joined #openstack-meeting-315:59
*** nacim has quit IRC16:00
david-lyle#startmeeting Horizon16:00
openstackMeeting started Tue Apr  1 16:00:52 2014 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: Horizon)"16:00
openstackThe meeting name has been set to 'horizon'16:00
*** lcheng has joined #openstack-meeting-316:01
david-lyleHello horizon minded folks16:01
jcoufalo/ hello16:01
jpichHello!16:01
tzumainnhiya16:01
devlapso/16:01
*** lsmola has joined #openstack-meeting-316:01
clu_hello!16:01
doug-fishHi16:01
akrivokahiya o/16:01
lsmolahello16:01
lblanchardhi all!16:01
lchenghello16:01
david-lyleRC1 was but on Monday \o/16:02
david-lyles/but/cut/16:02
david-lylemaster is open for Juno16:03
akrivokayay :)16:03
doug-fish:-D  hooray for us!16:03
lblanchardgreat job to you all!16:03
jpichGo us!16:03
david-lylelot's of great stuff went into Icehouse and a lot of good stuff just missed16:03
*** zehicle has quit IRC16:03
david-lyleI expect Juno-1 to pull in a lot of things that just didn't work out timing wise16:04
david-lyleIf you had a patch that got -2'd for Icehouse, it mostly likely was abandoned by gerrit16:04
*** eghobo has joined #openstack-meeting-316:04
julimhi all16:04
jpichCool. (Do other cores have a secret gerrit query to easily find the patch one -2d?)16:04
*** safchain has quit IRC16:04
david-lylePlease revitalize your patches and the person that -2'd it will remove the -216:05
david-lylejpich, unfortunately no, and unless it's in an active state, you can't remove the patch16:05
jpichdavid-lyle: Ok!16:05
jpichPlease feel free to ping the person that left it if the -2 isn't going away, sometimes people miss things......16:05
jpich:-)16:06
david-lyleSo one large item that is not in RC1 is a translation import, we will need an RC2 to pull those in16:06
david-lylewe want to limit what goes into RC2 to critical and very low risk fixes16:07
jpichI'd really like to see https://review.openstack.org/#/c/79456/ go into rc2 FWIW, the current way of updating host aggregates isn't safe16:07
david-lyleThere is not an RC2 window yet, so just tag the bugs with rc-potential16:08
* david-lyle should verify actual tag16:08
jpichThere's a pending question about the tests in that review (which I was planning on bringing up) but the fix itself looks fine16:08
jpichI've seen icehouse-rc-potential  used16:08
jpichso I've been using it too :-)16:08
david-lyleicehouse-rc-potential yes16:09
david-lyleI don't see any agenda items for today, so let's jump in16:10
*** JuanManuelOlle has joined #openstack-meeting-316:10
david-lyle#topic Open Discussion16:10
*** openstack changes topic to "Open Discussion (Meeting topic: Horizon)"16:10
david-lylejpich, what was the question?16:10
*** amotoki has joined #openstack-meeting-316:10
*** Sukhdev has joined #openstack-meeting-316:10
jpichAbout the tests on https://review.openstack.org/#/c/79456/, would people have objections to switching the openstack_dashboards logging handler to 'null' for the tests? (https://github.com/openstack/horizon/blob/master/openstack_dashboard/test/settings.py#L151 ). It can cause issues with unwanted output in the tests when testing failure paths. We do need to log the different clients for e.g. missing mocked calls, but I'm not sure of the value for16:11
jpich this one (I could be missing it though)16:11
jpichIt's a fix I'd really like to see ideally in the RC in my ideal world, or otherwise in the first stable icehouse point release. I appreciate your feedback :)16:11
*** johnma has joined #openstack-meeting-316:11
*** santibaldassin has joined #openstack-meeting-316:12
david-lyleare we missing an Exception type being caught?16:12
jpichdavid-lyle: I think it's because of using LOG.exception() instead of LOG.error() - which I had suggested in order to keep the details of the exception but perhaps it wasn't the best solution16:13
david-lyleah, ok16:14
jpichWithout the fix, we currently delete all the aggregates whenever the "Save" button is hit instead of only updating the list16:14
jpichI think this could be a real problem if Nova happened to become unreachable in the middle of this operation16:15
david-lylewhy not exceptions.handle?16:15
akrivokathe tests still pass, right? the only issue is that the traceback is displayed is the logs, but that's kinda the point of logging.exception()16:16
david-lyleagree, the problem should be fixed16:16
jpichdavid-lyle: It causes 2 message notifications to pop up instead of one16:16
*** mwagner_zzz has joined #openstack-meeting-316:16
jpichakrivoka: Yes, it's just a notification message in the output, the tests are correct and pass16:16
david-lylewe don't want noise in the test output though, or things like missing mocks get overlooked16:17
amotokiexceptions.handle leads to another popup menu. LOG.error looks good now and we need to investigate more about LOG.exception later.16:17
jpichamotoki: You do lose some details though, exception() keeps the strack trace16:18
jpichFrom what I understand the same problem should happen using LOG.error since they log at the same level (I will test)16:18
amotokijpich: yes. After chekcing the code, exception.handle with ignore=True suppress error popup.16:19
jpichAnyhow I don't mean to hijack the meeting with this, I would appreciate feedback on the review and I'll keep trying to look for a better solution myself as well16:19
jpichThank you16:19
jpichamotoki: it doesn't log the exception at all when ignore is True, which isn't ideal either16:19
*** tedchang has quit IRC16:20
*** mfer has quit IRC16:20
amotokijpich: I might miss something... i will check it later if i have time.16:20
jpichamotoki: Thank you!16:21
david-lylequiet today, post RC haze16:22
doug-fish:-)  so what's our string freeze state today, now that we've reached rc1?16:23
jpichamotoki: (I just confirmed that the log output is also shown when using LOG.error())16:24
jpichdoug-fish: Definitely hard freeze :)16:24
david-lyleand we plan to import the strings to master/RC2 on Monday16:24
doug-fishso ... no string changes unless I have a signed note from jpich?  (I'm not planning any)16:24
david-lyletranslated strings that is16:24
doug-fishwow, that's fast!16:25
jpichdoug-fish: A blessing in writing from the good folks at http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n :)16:25
david-lyleamotoki, previously discussed plan still works16:25
amotokidavid-lyle: thanks. most lang team do the great job and there seems no problem so far.16:26
akrivokajpich: amotoki: found this, might be useful http://stackoverflow.com/questions/5255657/how-can-i-disable-logging-while-running-unit-tests-in-python-django16:26
david-lyleexcellent16:26
jpichakrivoka: That kind of looks like the hammer solution, switching the one handler to null would avoid losing the missing mocked calls that pop up from time to time16:27
jpichthat disable all logging16:28
david-lyleregarding lang, the above would also hide unmocked api calls16:28
david-lylemaybe have to filter the log calls somehow when testing, but that wouldn't be an RC change16:28
akrivokahm right. seems like it needs further investigation.16:29
jpichRight. I'll play some more with exception.handle() as well16:29
david-lyleAny other items?16:31
jpichWhile I'm out here making requests... It'd be lovely if a non-Red Hat core could look at helping the initial integration tests patch to move along: https://review.openstack.org/#/c/77425/ . At this stage it doesn't need to be perfect, I think, we'll figure out best practices as we go. There are 4 people from 3 different companies who reached out to contribute integration tests, but everyone is blocked until that first patch that lays out the fou16:33
jpichndations merges16:33
*** Sukhdev has quit IRC16:33
jpichThank you for your consideration!16:33
david-lylejpich, thanks, got lost in the release shuffle, that is a high priority for me16:34
david-lyleadded to my list16:34
jpichdavid-lyle: Cheers!16:34
jpichI'm done asking for stuffs :-)16:34
amotokiwe have several number of new bugs now. i think it is time to check and classify all bugs. Bug day?16:35
david-lyleamotoki, good idea16:36
david-lylewe're fortunate to have a lot of new people looking at Horizon and submitting bugs16:37
david-lyleamotoki, have a day to propose?16:37
amotokii have no exact date.16:37
amotokiOr we can check bugs this week.16:38
amotokisome of bugs are not directly related to horizon and need to be forwarded to backend projects and some are feature requests.16:39
david-lylewe have over 100 bugs in the New state16:40
david-lyleI'll try to catch up on some of those this week, if others will do the same maybe we can get that number down quite a bit by next week16:40
david-lylethen access if we want to schedule a bug day16:41
doug-fishas a still new-ish person here I'm not certain how to contribute to bug handling16:41
akrivoka+1, I'll try to help out more on that front16:41
amotokii believe it works.16:41
doug-fishis there a triage wiki?16:41
*** zhenguo has joined #openstack-meeting-316:41
david-lyledoug-fish, the biggest assistance would be verifying that it is indeed a problem16:42
amotokidoug-fish: do you mean a wiki page describing tagging policy ?16:42
david-lyleas in can you reproduce it16:42
doug-fishdavid-lyle - good to know16:42
jpichdoug-fish: Not sure if you've seen https://wiki.openstack.org/wiki/BugTriage ?16:42
david-lyleif you can, and you consider it a bug then you can mark it confirmed16:42
david-lyleso items are reproducible, but may be a matter of opinion16:43
david-lyleleaving notes as to your findings is also very helpful, especially if you narrow down a cause16:43
amotokii found https://wiki.openstack.org/wiki/BugTags yesterday.16:43
david-lyleI believe only Horizon-Driver can set the importance16:44
*** zhenguo has quit IRC16:44
doug-fishjpich:  that wiki is generally quite helpful.  Thanks!16:44
amotokinova and neutron have a good list of tags. I think adding tags for horizon is a good idea.16:44
jpichdoug-fish: You're welcome!16:44
doug-fishI may become a Task 10 specialist.  :-)16:45
david-lylealways good to jump to Task 10 first16:45
amotoki:-)16:45
jpichamotoki: Yes. I find tagging by component can help people who favour another project to fix the related bugs (like you do with "neutron" related bugs for example)16:46
*** zhenguo has joined #openstack-meeting-316:46
amotokiAFAIK we don't have concrete policy on tagging now. let's add to the list. it must be helpful and we can improve it.16:47
amotokii will add some tags tomorrow.16:47
clu_hi everyone, i have an unrelated question: https://review.openstack.org/#/c/76107/16:47
clu_what are thoughts on validation on the front end?16:47
clu_for example, if the api checks for whether there is an existing name or not16:48
clu_should the front end do a check first?16:48
doug-fishgreat question clu_.  I've seen some confusion on that in other reviews.16:49
amotokiclu_: Apart from that a name is a good example, it sounds good as long as it works.16:50
david-lyleIf we can perform a sane check beforehand and provide a meaningful validation error, I think that's the best we can hope for, as long as it's not a non-deterministic check16:50
jpichclu_: I thought you meant doing a Javascript check first. I think we do this kind of checks usually when it can help showing a better error message16:50
lblanchardclu_: I don't know much about the feature here, but IMO it's always nice to let the user know about any errors or potential errors as soon as possible. This way they don't fill out an entire form only to find out that there was an error and they can't complete their task.16:51
clu_jpich: yes, this is what i'm referring to16:51
david-lyleThe hope with angular is we'll be able to provide that validation on the client side, the generalized framework for that is not in place yet though, I believe16:52
jpichWill that include making API calls?16:53
clu_david-lyle: are there any blueprints about the angular client side validation? i'd like to check that out16:53
david-lyleclu_, https://blueprints.launchpad.net/horizon/+spec/django-angular-integration16:54
clu_cool thanks david-lyle16:54
david-lylejpich, not entirely clear to me, need to dig back into that topic16:55
*** mrunge has joined #openstack-meeting-316:56
jpichOk16:56
david-lyleclu_, in the short term, I don't think we should block improving server side validation to wait for better client side validation, we can rework once we have a more generalized framework16:57
clu_david-lyle: thanks16:58
*** peristeri has quit IRC16:58
*** peristeri has joined #openstack-meeting-316:59
amotokiserver side and client side validations can co-exists. if we have duplicated check, we can remove it later.16:59
david-lyleexactly16:59
amotokibtw, my patch for milestone-proposed https://review.openstack.org/#/c/84204/ hits the same error on swift...... hope someone check it.16:59
*** SumitNaiksatam has quit IRC17:00
david-lyleWe're out of time.  Thanks everyone for all your hard work to get RC1.17:00
david-lyleHave a great week.17:00
david-lyle#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Tue Apr  1 17:00:46 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-04-01-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-04-01-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-04-01-16.00.log.html17:00
amotokithanks all! o/17:00
*** johnma has left #openstack-meeting-317:01
*** doug-fish has left #openstack-meeting-317:01
clu_thanks good bye17:01
lsmolathanks, goodbye17:01
jcoufalthanks guys, bye bye17:01
lblanchardbye all!17:01
*** lcostantino has left #openstack-meeting-317:01
devlapsthanks all!17:01
zhenguothanks, bye17:01
akrivokathanks everyone!17:01
akrivokabye17:01
*** nacim has joined #openstack-meeting-317:02
*** tzumainn has left #openstack-meeting-317:02
*** mrunge has quit IRC17:02
*** jcoufal has quit IRC17:04
*** JuanManuelOlle1 has joined #openstack-meeting-317:04
*** amotoki has quit IRC17:05
*** Sukhdev has joined #openstack-meeting-317:05
*** JuanManuelOlle has quit IRC17:06
*** Sukhdev has quit IRC17:09
*** clu_ has left #openstack-meeting-317:10
*** tedchang has joined #openstack-meeting-317:10
*** JuanManuelOlle1 has left #openstack-meeting-317:10
*** sarob has joined #openstack-meeting-317:12
*** zhenguo has quit IRC17:12
*** mwagner_zzz is now known as mwagner_17:14
*** ttrifonov_zZzz is now known as ttrifonov17:15
*** SumitNaiksatam has joined #openstack-meeting-317:15
*** david-lyle is now known as david-lyle_afk17:17
*** jpich has quit IRC17:18
*** alexpilotti has joined #openstack-meeting-317:25
*** sarob has quit IRC17:35
*** sarob has joined #openstack-meeting-317:36
*** MaxV_ has quit IRC17:36
*** mfer has joined #openstack-meeting-317:36
*** mfer has quit IRC17:37
*** TravT has quit IRC17:40
*** sarob has quit IRC17:40
*** TravT has joined #openstack-meeting-317:44
*** lenrow has quit IRC17:46
*** lpetrut has quit IRC17:53
*** ttrifonov is now known as ttrifonov_zZzz17:58
*** mwagner_ is now known as mwagner_afk18:00
*** julim has quit IRC18:04
*** julim has joined #openstack-meeting-318:06
*** rockyg has joined #openstack-meeting-318:08
*** sarob has joined #openstack-meeting-318:12
*** sarob has quit IRC18:12
*** Sukhdev has joined #openstack-meeting-318:14
*** MaxV_ has joined #openstack-meeting-318:21
*** lpetrut has joined #openstack-meeting-318:22
*** nacim has quit IRC18:24
*** ttrifonov_zZzz is now known as ttrifonov18:39
*** terrylhowe has joined #openstack-meeting-318:45
*** jamielennox has joined #openstack-meeting-318:56
*** Alex_Gaynor has joined #openstack-meeting-318:56
*** briancurtin has joined #openstack-meeting-318:58
*** jcoufal has joined #openstack-meeting-318:59
*** akrivoka has quit IRC19:00
briancurtin#startmeeting python-openstacksdk19:00
openstackMeeting started Tue Apr  1 19:00:22 2014 UTC and is due to finish in 60 minutes.  The chair is briancurtin. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** openstack changes topic to " (Meeting topic: python-openstacksdk)"19:00
openstackThe meeting name has been set to 'python_openstacksdk'19:00
briancurtinif anyone is here for the python-openstacksdk meeting, can they please state their name and affiliation?19:00
*** bknudson has joined #openstack-meeting-319:01
edleafeEd Leafe, Rackspace19:01
bknudsonBrant Knudson, IBM19:01
terrylhoweTerry Howe, HP19:01
Alex_GaynorAlex Gaynor, I have many affiliations.19:01
briancurtinBrian Curtin, Rackspace19:01
Alex_Gaynor(I'm also sitting in the middle of another meeting, so apollogies when I'm inatentive)19:01
jamielennoxJamie Lennox, Red Hat19:02
*** dtroyer has joined #openstack-meeting-319:03
*** jcoufal has quit IRC19:03
*** jcoufal has joined #openstack-meeting-319:03
dtroyerDean TRoyer, Nebula, jumping in late...19:04
briancurtin...and that's the usual crew, so moving on19:04
briancurtin#topic Progress - can we move forward toward a MVP?19:04
*** openstack changes topic to "Progress - can we move forward toward a MVP? (Meeting topic: python-openstacksdk)"19:04
briancurtinSince several of dtroyer's reviews are nearing merge, it feels like we have enough lower level plumbing to start building on top of19:05
briancurtinshortly we'll get into edleafe's design, but does it feel like we're at a point where we can start building services and pick up the pace a bit?19:05
dtroyerI hope so ;)19:06
briancurtinfor example, I'd like to revisit Alex_Gaynor's old "api_strawman" using some of this recent stuff19:06
edleafeif we assume that we will have a reliable way to get endpoints, etc., we can certainly start doing some of the other stuff19:06
briancurtinbesides these current reviews, is there anything else we must absolutely figure out before moving on?19:07
edleafeI think we can move on in parallel19:07
dtroyerI am hoping to finish the api discovery next, auth could happen in parallel to that19:07
edleafeno need to hold everything up19:07
briancurtinok cool, i like that19:07
dtroyerbut neither of those need to be hard blockers19:07
*** markmcclain has quit IRC19:08
briancurtinwith that said, let's talk for a bit on the proposed design19:08
briancurtin#topic https://wiki.openstack.org/wiki/PythonOpenStackSDK/ClassDesignDiscussion19:08
*** openstack changes topic to "https://wiki.openstack.org/wiki/PythonOpenStackSDK/ClassDesignDiscussion (Meeting topic: python-openstacksdk)"19:08
edleafeThe main goal of this design is separation of responsibilities to make development and testing easier, and avoid duplication across services19:09
briancurtinedleafe: one of the biggest things i dislike about this is duplication which ends up being heralded as flexibility19:10
dtroyermy initial reaction is to having a 'client' for each service…  we've discussed a single client (I think we used the word 'context' there) that handles multiple managers for the dispatching19:10
briancurtini'm not a huge fan of providing several ways to call one API19:10
*** eguz has joined #openstack-meeting-319:11
Alex_GaynorI'd like to specifically object to "Rather than have fixed attributes, its attributes should be populated with the information returned from the API." -- I think this basically makes it impossible to document really well19:11
dtroyer++19:11
jamielennoxare those common methods actually on client or on the managers/19:11
Alex_Gaynor(that's on resource)19:11
edleafebriancurtin: For end users it is a huge benefit. At the SDK level, only one path is followed to the API19:11
briancurtinedleafe: but at the SDK level i found we have the same lines of code copied & pasted everywhere to enable that19:13
edleafeAlex_Gaynor: that's certainly possible, but a lot more of a maintenance burden19:13
Alex_GaynorIn general, I'd like us to do hard work so our users' can have a great experience19:13
jamielennoxso this looks rather a lot like the current client's layouts. One of the things i was hoping to discuss here is if we could shift more burden onto the resource concept and away from the managers19:13
jamielennoxeg User.create(), User.update rather than client.users.update(id, **)19:13
terrylhowewell, managers need to list, get, create19:13
briancurtinseveral places end up delegating into a manager, so we have several places where we're just having a class with one method that sends itself elsewhere. some modules are fairly large but only fractions of the code actual do anything19:14
*** eghobo has quit IRC19:15
edleafebriancurtin: actually, most of the duplication is in the base class, so there is only one copy of a call.19:15
terrylhoweUser.create() would be nice if users could populate a resource rather than pass in a dictionary19:16
bknudsonit would be interesting to see the code that we'd like for creating a user.19:16
edleafeterrylhowe: that would be cool, but is that the most obvious way to create resources?19:16
jamielennoxedleafe: the manager design like the current clients have is very interdependant19:17
bknudsonis it like client.identity.user.create({'name': 'something', ... })  ?19:17
briancurtinbknudson: perhaps we rejuvenate the idea of the "api_strawman" and take one or more approaches to fill out an example?19:17
edleafeSo if I'm storing a blob in swift, I would populate a storage object locally, and then call .save()? Something like that?19:17
jamielennoxedleafe: ++, that's what i was thinking19:18
jamielennoxpassing dicts of attributes around is a pain19:18
edleafeSo more of an ORM-like approach19:18
Alex_GaynorPlease no dicts :/19:19
edleafejamielennox: re: interdependence - clients should create managers with all the info they need. Managers shouldn't need a reference back to the client.19:19
edleafeAlex_Gaynor: and no keyword params?19:19
Alex_Gaynorkeyword pramams are ok19:19
Alex_GaynorI don't want users passing dicts directly though19:19
edleafejust attributes?19:19
Alex_Gaynorit tends to make documentation really really hard19:20
Alex_Gaynorand also makes good error messages hard19:20
jamielennoxedleafe: just resource objects19:20
dtroyerI don't think the managers should need to contain any information…they're the logic for dispatching through the API19:20
jamielennoxdtroyer: right, we could even do client.list(User) and ditch the managers19:21
edleafeAlex_Gaynor:  I envisioned methods with keyword parameters; terrylhowe is proposing building an object attribute-by-attribute, and then saving it.19:21
bknudsonwhat's an example of a manager?19:21
jamielennoxbknudson: the users part of client.users.list()19:21
bknudsonwe're going to have a lot of manager19:22
bknudsonmanagers19:22
edleafebknudson: in the proposed design, the manager takes the user's request, determines the URI, headers, etc. that will be needed, and passes that to the http layer for the actual call19:22
edleafejamielennox: client.list(User) is just a different syntax19:25
briancurtinedleafe: do you think you could come up with a minimal example on top of dtroyer's session wrapper, once it's in?19:25
edleafethe question is where the logic goes for determining what the URI to call would go19:26
terrylhoweI like the idea of the save() method on the resource to save it, but the manager will still need a create() method to create a new resource19:26
edleafethat wouldn't be exposed to the dev/user19:26
jamielennoxedleafe: yes and no, it's a question of where you put all the information for how to build the urls19:26
terrylhoweI'd think the manager edleafe the resource would have to reference it19:26
bknudsonthere's only 1 manager for a resource, right?19:26
edleaferesources would have reference to their manager, just like the client19:27
bknudsonUser has a UserManager19:27
edleafebknudson: yes19:27
terrylhoweyep19:27
edleafebriancurtin: sure, but it would be fairly abstract without a service catalog19:27
edleafeis that OK?19:27
briancurtinedleafe: yeah, i think so. compare it to Alex_Gaynor's client.py example from the old api_strawman directory, just putting together simple swift operations19:28
edleafebriancurtin: ok, I can try to have something committed in the next few days19:29
briancurtinedleafe: cool, i think getting something into gerrit that we can see will help guide this better than an IRC talk (although maybe i'm wrong)19:30
edleafeit would probably answer some of the obvious stuff, and raise much more interesting discussions.19:30
briancurtinagreed. i think we could probably sit here and talk all day, but we'd be more productive to just get something on the board at this point and steer it from there19:31
edleafeI'd like to also see a proposal for the ORM-like resource design19:32
briancurtin#topic https://review.openstack.org/#/c/81882/ (Add requests.Session wrapper class)19:32
*** openstack changes topic to "https://review.openstack.org/#/c/81882/ (Add requests.Session wrapper class) (Meeting topic: python-openstacksdk)"19:32
briancurtin(oops, sorry to jump on top of that, edleafe, but that could also be cool)19:32
briancurtinwas that terrylhowe's thing?19:32
terrylhoweI'm ready to move on19:33
briancurtinanyway, with Alex_Gaynor here - is dtroyer's response on httpretty alright?19:34
Alex_Gaynor(The answer might be that everyone just disagrees with me :-))19:34
briancurtini think most people agreed the last time we talked about it, but didn't have a great solution to work with at the moment (or something like that)19:35
dtroyerI like the idea of httmock, but it needs to be proven yet, then added to the global requirements, and I didn't want to wait on that19:36
jamielennoxadmittedly i'm biased here, but i see using httpretty and patching global state as easier that mocking the requests.request interface19:36
jamielennoxi don't see how global state matters when you are running test code that will only run one test at a time19:36
terrylhowehttpretty makes me a little more confident things might actually work in this case19:37
briancurtinat this point, i'd like to see if we can reach a consensus that httpretty is fine to build off of, and like jamielennox said, that global state mucking is confined to tests for the time being19:37
bknudsonhttpretty seems to work so I'm fine with it.19:37
jamielennoxbriancurtin: global state mocking is ALWAYS limited to tests - you would never do this in the library19:37
briancurtinjamielennox: of course, i meant mucking, like doing dirty, dirty things with global state19:38
bknudsonat some point we're going to need a fake identity server19:38
briancurtinAlex_Gaynor: thoughts?19:39
bknudsonat what level does that get inserted19:39
bknudsonI assume we're not going to have httpretty simulate keystone19:40
terrylhoweA mock session would make sense for that19:41
briancurtini'm guessing Alex_Gaynor is busy in the other meeting - Alex_Gaynor, when you get back: speak now or forever hold your peace on httpretty19:44
briancurtin#topic https://review.openstack.org/#/c/81988/ (Add redirection handling to openstack.session.Session)19:44
*** openstack changes topic to "https://review.openstack.org/#/c/81988/ (Add redirection handling to openstack.session.Session) (Meeting topic: python-openstacksdk)"19:44
briancurtina couple of things left here, a quick s/assertTrue/assertEqual in a test. i think bknudson had mostly been addressed19:45
*** TravT has quit IRC19:45
dtroyerI see only one outstanding comment on that one, I have it addressed, am going to push it with the update to 8188219:45
briancurtini think that's probably good then19:46
briancurtin(i was wrong about couple of things - just my remaining comment)19:46
briancurtin#topic https://review.openstack.org/#/c/82646/ (Add API discovery support)19:47
*** openstack changes topic to "https://review.openstack.org/#/c/82646/ (Add API discovery support) (Meeting topic: python-openstacksdk)"19:47
dtroyerThis one is really still WIP…I'm moving more of the logic into the Version class...19:47
briancurtinthat one has a couple more things to address, but like was said earlier, can be done in parallel with the other work19:47
briancurtinah19:47
dtroyerand renaming the classes to make more sense19:48
briancurtincool19:48
briancurtinso at this point, i think we have more actionable items to move forward on19:49
briancurtin#action edleafe: prepare minimal example of manager-client-resource19:49
briancurtin#action revive Alex_Gaynor client19:50
briancurtin#action possible ORM-style client19:50
briancurtinanything else to build on at the moment?19:50
edleafecorrection: ORM-style resource19:51
briancurtinoops, yeah19:51
briancurtin9 min left - anything else to chat about while we're here?19:51
dtroyerFWIW, I plan on proposing an OpenStack program soon for client-side stuff that will initially include OpenStackClient.19:52
dtroyerI understand the TC wants to hold off including additional projects that are early in implementation, such as this one, but eventually that is where they would also live19:53
*** TravT has joined #openstack-meeting-319:54
briancurtindtroyer: what other types of projects would you foresee that including?19:54
dtroyerI am looking for a name that sounds general enough to include both19:54
dtroyermuch of what is currently in motion for not-REST-server stuff, except Horizon19:54
dtroyerthat wants to join19:54
*** yamahata has joined #openstack-meeting-319:55
bknudsonI'm surprised that https://review.openstack.org/#/c/81882/ didn't merge.19:56
bknudsonit's approved and verified19:56
dtroyerit couldn't with Alex's −2 still attached19:56
briancurtinbknudson: i think alex gaynor's original -2 was holding it up. he just changed it to -1 with recent comments19:56
briancurtindtroyer: would that program be something like "developer experience"?19:57
dtroyerit would include that, but the CLI is also 'user experience'19:57
briancurtindtroyer: cool, would like to know more as it develops19:58
dtroyerboth of those phrases carry additional expectations in the community and I want to be careful to not make people thing this program is all of those things19:58
briancurtintrue. naming isn't my specialty, but if i have anything, i'll let you know :)19:59
dtroyerok, thanks19:59
briancurtin#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Apr  1 20:00:07 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-04-01-19.00.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-04-01-19.00.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-04-01-19.00.log.html20:00
*** terrylhowe has left #openstack-meeting-320:00
*** markmcclain has joined #openstack-meeting-320:03
*** mwagner_afk has quit IRC20:03
*** gduan has quit IRC20:09
*** garyduan has joined #openstack-meeting-320:10
*** Sukhdev has quit IRC20:14
*** Alex_Gaynor has left #openstack-meeting-320:15
*** julim has quit IRC20:25
*** eguz has quit IRC20:27
*** eghobo has joined #openstack-meeting-320:28
*** bknudson has left #openstack-meeting-320:29
*** jcoufal has quit IRC20:37
*** gduan has joined #openstack-meeting-320:38
*** garyduan has quit IRC20:38
*** dtroyer has left #openstack-meeting-320:46
*** mfer has joined #openstack-meeting-320:47
*** briancurtin has left #openstack-meeting-320:50
*** MaxV__ has joined #openstack-meeting-320:53
*** MaxV___ has joined #openstack-meeting-320:56
*** MaxV_ has quit IRC20:57
*** MaxV__ has quit IRC20:58
*** david-lyle_afk is now known as david-lyle21:01
*** rockyg has quit IRC21:03
*** lpetrut has quit IRC21:06
*** mfer has quit IRC21:08
*** lblanchard has quit IRC21:10
*** santibaldassin has quit IRC21:31
*** peristeri has quit IRC21:37
*** enikanorov has joined #openstack-meeting-321:49
*** ttrifonov is now known as ttrifonov_zZzz21:49
*** cgoncalv1s has joined #openstack-meeting-321:54
*** DinaBelova2 has joined #openstack-meeting-321:54
*** ruhe has quit IRC21:54
*** jtomasek has quit IRC21:54
*** DinaBelova has quit IRC21:54
*** enikanorov_ has quit IRC21:54
*** cgoncalves has quit IRC21:54
*** DinaBelova2 is now known as DinaBelova21:54
*** jtomasek has joined #openstack-meeting-321:55
*** ruhe has joined #openstack-meeting-321:55
*** mfer has joined #openstack-meeting-321:57
*** mfer has quit IRC21:57
*** MaxV___ has quit IRC22:05
*** MaxV_ has joined #openstack-meeting-322:05
*** banix has quit IRC22:13
*** alexpilotti has quit IRC22:14
*** lsmola has quit IRC22:31
*** TravT has quit IRC22:36
*** markmcclain has quit IRC22:52
*** yamahata has quit IRC23:08
*** MaxV_ has quit IRC23:09
*** david-lyle has quit IRC23:20
*** mwagner_afk has joined #openstack-meeting-323:32
*** lcheng has quit IRC23:37

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