Wednesday, 2012-01-04

*** deshantm has quit IRC00:00
*** deshantm_ is now known as deshantm00:00
*** patelna has quit IRC00:04
*** dolphm has joined #openstack-meeting00:09
*** mjfork has left #openstack-meeting00:09
*** dragondm has quit IRC00:18
*** nati2 has quit IRC00:23
*** nati2 has joined #openstack-meeting00:24
*** zns has quit IRC00:29
*** dolphm has quit IRC00:34
*** gyee has quit IRC00:40
*** dolphm has joined #openstack-meeting00:56
*** jakedahn has quit IRC01:02
*** bhall has quit IRC01:06
*** sleepsonthefloo has quit IRC01:21
*** ayoung has joined #openstack-meeting01:22
*** SumitNaiksatam has quit IRC01:32
*** dendrobates is now known as dendro-afk01:35
*** dendro-afk is now known as dendrobates01:37
*** vladimir3p has quit IRC02:02
*** jog0 has quit IRC02:02
*** andrewbogott has quit IRC02:04
*** jdurgin has quit IRC02:05
*** jakedahn has joined #openstack-meeting02:07
*** westmaas has quit IRC02:22
*** ttx has quit IRC02:23
*** ttx has joined #openstack-meeting02:24
*** ttx has joined #openstack-meeting02:24
*** jakedahn has quit IRC02:24
*** westmaas has joined #openstack-meeting02:25
*** oubiwann has quit IRC02:38
*** danwent has joined #openstack-meeting02:41
*** danwent has left #openstack-meeting02:48
*** dendrobates is now known as dendro-afk02:54
*** dolphm has quit IRC03:01
*** dolphm has joined #openstack-meeting03:08
*** shang has quit IRC03:29
*** dayou has quit IRC03:39
*** lloydde has quit IRC03:46
*** ecarlin has joined #openstack-meeting03:46
*** shang has joined #openstack-meeting03:46
*** ecarlin has quit IRC03:46
*** nati2 has quit IRC03:48
*** nati2 has joined #openstack-meeting03:49
*** dayou has joined #openstack-meeting03:52
*** dolphm has quit IRC03:54
*** dolphm has joined #openstack-meeting03:59
*** lloydde has joined #openstack-meeting04:18
*** deshantm has quit IRC04:21
*** dendro-afk is now known as dendrobates05:16
*** HowardRoark has quit IRC05:17
*** dolphm has quit IRC05:38
*** nati2_ has joined #openstack-meeting05:44
*** nati2 has quit IRC05:44
*** sleepsonthefloo has joined #openstack-meeting05:53
*** nati2_ has quit IRC06:09
*** nati2 has joined #openstack-meeting06:09
*** nati2_ has joined #openstack-meeting06:24
*** nati2 has quit IRC06:25
*** nati2 has joined #openstack-meeting06:53
*** nati2_ has quit IRC06:56
*** nati2_ has joined #openstack-meeting07:10
*** nati2 has quit IRC07:11
*** sleepsonthefloo has quit IRC07:12
*** nati2 has joined #openstack-meeting08:13
*** nati2_ has quit IRC08:14
*** lloydde has quit IRC08:38
*** zul has quit IRC08:49
*** zul has joined #openstack-meeting09:14
*** darraghb has joined #openstack-meeting10:07
*** derekh has joined #openstack-meeting10:20
*** DuncanT has joined #openstack-meeting11:33
*** dendrobates is now known as dendro-afk12:19
*** markvoelker has joined #openstack-meeting12:42
*** dayou has quit IRC12:53
*** dayou has joined #openstack-meeting12:57
*** derekh has quit IRC13:13
*** dayou has quit IRC13:28
*** dayou has joined #openstack-meeting13:29
*** hggdh has quit IRC13:52
*** AlanClark has joined #openstack-meeting14:13
*** deshantm has joined #openstack-meeting14:15
*** derekh has joined #openstack-meeting14:16
*** dprince has joined #openstack-meeting14:22
*** zul has quit IRC14:32
*** zul has joined #openstack-meeting14:33
*** mdomsch has joined #openstack-meeting14:39
*** lloydde has joined #openstack-meeting14:43
*** chuck_ has joined #openstack-meeting14:48
*** zul has quit IRC14:48
*** chuck_ is now known as zul14:49
*** zul has joined #openstack-meeting14:49
*** rnirmal has joined #openstack-meeting14:53
*** troytoman-away is now known as troytoman14:53
*** zul has quit IRC14:54
*** hggdh has joined #openstack-meeting14:58
*** zul has joined #openstack-meeting14:59
*** danwent has joined #openstack-meeting15:09
*** danwent has left #openstack-meeting15:09
*** nati2 has quit IRC15:11
*** nati2_ has joined #openstack-meeting15:11
*** blamar has joined #openstack-meeting15:23
*** ayoung has quit IRC15:31
*** jaypipes has joined #openstack-meeting15:40
*** dolphm has joined #openstack-meeting15:43
*** ttx has quit IRC15:43
*** ttx has joined #openstack-meeting15:43
*** ttx has joined #openstack-meeting15:43
*** ttx has quit IRC15:45
*** ttx has joined #openstack-meeting15:45
*** ttx has joined #openstack-meeting15:45
*** blamar has quit IRC15:46
*** blamar has joined #openstack-meeting15:47
*** dragondm has joined #openstack-meeting15:57
*** ayoung has joined #openstack-meeting15:59
*** GheRivero_ has joined #openstack-meeting16:06
*** nati2 has joined #openstack-meeting16:23
*** nati2 has quit IRC16:25
*** nati2_ has quit IRC16:25
*** nati2 has joined #openstack-meeting16:25
*** nati2 has quit IRC16:39
*** GheRivero_ has quit IRC16:44
*** dwalleck has joined #openstack-meeting16:48
*** dwalleck has quit IRC16:48
*** dwalleck has joined #openstack-meeting16:49
*** ayoung has quit IRC16:50
*** rick-rackspace has joined #openstack-meeting16:57
*** rohitk has joined #openstack-meeting16:57
*** donaldngo_hp has joined #openstack-meeting16:59
*** donaldngo_hp has quit IRC16:59
*** donaldngo_hp has joined #openstack-meeting16:59
*** nati2 has joined #openstack-meeting16:59
nati2Hi guys! Happy New Year!17:00
jaypipesdwalleck, donaldngo_hp, nati2, rohitk: QA team meeting? :)17:00
*** oubiwann has joined #openstack-meeting17:00
jaypipesnati2: Happy new year to you!17:00
nati2jaypipes: Hi Jay17:00
dwallecksure!17:00
rohitkYup, Happy New Year to All!17:00
donaldngo_hphappy new year everyone!17:00
jaypipesindeed!17:00
* jaypipes happy to be back at home...17:00
*** mattray has joined #openstack-meeting17:00
nati2ok let's get started :)17:01
jaypipesindeed17:01
jaypipes#startmeeting17:01
openstackMeeting started Wed Jan  4 17:01:55 2012 UTC.  The chair is jaypipes. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.17:01
jaypipesAnyone want to give me a heads up on what was discussed the last 2 weeks?17:02
*** GheRivero_ has joined #openstack-meeting17:02
nati2We canceled previous meeting because of holiday.17:02
*** wwkeyboard has left #openstack-meeting17:03
jaypipesnati2: week before that?17:03
dwalleckThe week before we were talking again about test design style17:03
nati2We discussed about testing style on previous previous meeing17:03
jaypipesdwalleck: gotcha17:03
jaypipesdwalleck: any decisions?17:03
nati2hmm I counldn't remember, let me check logs17:03
dwalleckWhere we left off was asking for demos/brief examples so we could compare and contrast17:03
jaypipesdwalleck: right. I dropped the ball on that. apologies17:04
jaypipesdwalleck: I will make that my numero uno QA priority today.17:04
jaypipes#action jaypipes to make examples of sequential test case vs standalone test case to compare and vote on.17:05
dwalleckjaypipes: No problem! I sent out a few examples, which sparked some great conversation, but I think others wanted to show their examples as well17:05
jaypipesdwalleck: sent to the mailing list?17:05
dwalleckjaypipes: yessir. It seems like it went into everyone's junk mail for some reason17:05
*** donaldngo_hp has quit IRC17:05
*** donaldngo_hp has joined #openstack-meeting17:06
jaypipesdwalleck: hmm, ok, I'll check for it... didn't notice it yet17:06
AntoniHPI think you can access it in mailing list archives17:07
jaypipesdwalleck: so where are folks leaning at this point?17:07
AntoniHPthis is openstack-qa mailing list, not general openstack one17:07
jaypipesAntoniHP: aha!17:07
AntoniHPI will also work on some more examples, and send them to list as well - this format should be better to discuss then IRC meetings17:08
dwalleckjaypipes: I don't think we're close right now. I think we all need to talk a bit more on that one17:08
jaypipesthink we can send to the main mailing list?17:08
dwallecksure, I don't mind17:09
*** Gordonz has joined #openstack-meeting17:09
jaypipesAntoniHP: have a link to the archived thread?17:09
jaypipesis Sapan Kona here by any chance?17:09
AntoniHPhttps://lists.launchpad.net/openstack-qa-team/msg00022.html17:10
jaypipesAntoniHP: cheers17:10
jaypipesalright, well I'll follow up on the mailing list about the example test case stuff, let's move on...17:11
jaypipes#action discuss open Tempest bugs17:11
jaypipes#link https://bugs.launchpad.net/tempest17:11
jaypipesWe've got a bunch of open reviews: https://review.openstack.org/#q,status:open+project:openstack/tempest,n,z17:11
jaypipesWould be great to get folks' input on those reviews please17:12
jaypipesif you haven't done a code review before, would be a good place to start. All input is most welcome17:12
nati2sure I'll review17:12
jaypipeshere is a filtered list of bugs showing new test cases needing written: https://bugs.launchpad.net/tempest/+bugs?field.tag=test-needed17:12
*** sleepsonthefloo has joined #openstack-meeting17:12
jaypipesif you're looking for easy stuff to work on, those are good bugs to pick up.17:13
jaypipesJust assign yourself to unassigned bugs and go for it.17:13
jaypipesDoes anyone have any questions regarding the code submission process or code reviews?17:13
*** jog0 has joined #openstack-meeting17:14
dwalleckit's really not too rough. The squashing part was the only gotcha I ever hit17:14
jaypipesdwalleck: yup, and remembering to git commit -a --amend if it's a code review fixup...17:14
donaldngo_hpin what cases do we have to squash versus ammend17:15
dwalleckjaypipes: Exactly. Otherwise things get messy17:15
jaypipesdonaldngo_hp: good question. let me explain:17:15
jaypipesa) if someone has a small fixup request (style related or similar), then when you make a change locally, do a git commit -a --amend and then save the commit message17:15
*** joesavak has joined #openstack-meeting17:16
jaypipesb) If you do a set of fixes that are *dependent*, but are a logical set of additional changes from the original commit/changeset, then do not --amend, and it will be a new changeset when you do a git review.17:16
jaypipesdonaldngo_hp: so typically you will do a git commit -a --amend when you are addressing code review comments, and you will *not* do a git commit -a --amend when you want to create a logical, dependent series of changesets to be reviewed separately17:17
jaypipesdonaldngo_hp: that make sense?17:17
donaldngo_hpyea17:18
rohitkjaypipes: awesome explanation!17:18
donaldngo_hpthank you17:18
jaypipesdonaldngo_hp: don't worry. every one of us has been tripped up by it at least once :)17:18
annegentlethat's a great explanation17:19
donaldngo_hpyea ive abandoned a couple reviews ill get better at this17:19
jaypipesdonaldngo_hp:  no worries. you won't break anything in Gerrit :)17:19
donaldngo_hpis there a write up on the squash part?17:19
donaldngo_hpi think i have the ammend part down17:19
jaypipesdonaldngo_hp: there isn't, but there should be.17:19
donaldngo_hpsquash and rebase17:19
dwalleckI think there might be in the Gerrit guide...17:19
jaypipeslemme check...17:20
annegentle#link http://wiki.openstack.org/GerritWorkflow#Long-lived_Topic_Branches17:20
jaypipesdonaldngo_hp: http://wiki.openstack.org/GerritJenkinsGithub#squash_commits_first17:20
jaypipesdonaldngo_hp: both of those links above are good17:20
donaldngo_hpexcellent thank you17:21
jaypipesnp17:21
jaypipesdwalleck: have some time today to work with me on Skype on the open bug list? I think there's some that can be marked fix committed that we were just using to track stuff...17:22
dwalleckjaypipes: Sure, can do17:22
jaypipesfor instance: https://bugs.launchpad.net/tempest/+bug/90236617:22
uvirtbotLaunchpad bug 902366 in tempest "Testcase: Write Testcases for Rebuild Server" [High,Triaged]17:22
jaypipesdwalleck: cool, I'll ping you this afternoon?17:22
dwallecksounds good, I'll be here17:23
jaypipescool.17:23
jaypipesin the meantime, nati2, can I ask you to go through the bugs on https://bugs.launchpad.net/tempest/+bugs?field.tag=test-needed that have no priority or have a status of new and put them into Confirmed or Triaged status and set a priority/importance on them?17:24
nati2jaypipes: Ooops Yes sir! I got it17:24
jaypipesnati2: Confirmed for bugs that do NOT have a prescription for resolving the bug, Triaged for bugs that DO have a prescription.17:24
jaypipesnati2: thanks!17:24
lloyddeshould joining https://launchpad.net/~openstack-qa-team require approval? it currently does.17:25
jaypipeslloydde: yeah, requires moderation...17:25
jaypipeslloydde: you're now approved. :)17:25
jaypipesOK, everybody alright with moving on to open discussion?17:26
dwalleckSure17:26
jaypipes#topic Open Discussion17:26
*** openstack changes topic to "Open Discussion"17:26
jaypipesfire away, Anne :)17:26
annegentlethanks Jay!17:26
* annegentle is all about open discussion17:26
* lloydde grins17:27
annegentleSo a couple of items - one from docland, we're finalizing the approach on the API site17:27
jaypipesawesome17:27
annegentle#link http://heckj.github.com/api-site-mock/17:27
annegentlewe've added a search box there and the detail buttons should work now17:27
jaypipesoooooh, me likey.17:27
annegentlewhat we need is content, and the approach we're looking at is WADL>HTML17:28
annegentlefor this site17:28
annegentleand I know QA can use WADL too17:28
annegentleso I wondered if we can work towards having a WADL for each API stored in the APIs repo?17:28
nati2Super cooool!17:28
jaypipesannegentle: I think that's an excellent idea.17:28
annegentleI've talked to nearly all stakeholders I can think of, and wanted to talk to you all too.17:28
*** rohitk2 has joined #openstack-meeting17:28
dwalleckThat would definitely be helpful17:29
annegentleWith Rackspace's tools, WADL isn't as awful to edit, in Oxygen.17:29
annegentleso I'm told :)17:29
jaypipesannegentle: :)17:29
annegentleI want to take the ones in repos and add more explanatory content17:29
*** rohitk has quit IRC17:29
annegentleis that a good approach to you all?17:29
jaypipesannegentle: no objections from me :) how can our team members help?17:29
*** troytoman is now known as troytoman-away17:29
annegentleand I think Rohit has one waiting in one of the repos, awaiting review?17:29
annegentlealso the compute-api one Nati did got refactored but it's also checked in17:30
annegentleso what I'd like is for QA to review WADLs for accuracy (and usefulness to you all) even after me or a writer adds more content17:30
rohitk2anngentle: sorry, I just lost connectivity and context history, will check the logs17:30
annegentleso that's one help.17:30
nati2annegentle: You mean compute-api is WADL one?17:30
annegentleand second help is to ensure there are WADLs in compute-api (yes), identity-api (yes), image-api (not sure), object-api (none)17:31
jaypipesannegentle: That's no problem. We can add a bug to have the WADLs for each project reviewed by QA.17:31
annegentlenati2: I believe Jorge added one that does not contain extensions17:31
nati2I suppose Rohit is not working on WADL17:31
annegentlenati2: we also need to figure out what to do with WADL on extensions.17:31
jaypipesannegentle: someone (rohit?) was working on the images one IIRC17:31
rohitk2yes, that's right17:31
annegentlesorry that's a lot of ask for one meeting :)17:31
jaypipesannegentle: not a problem.17:32
annegentlebut I think the mockup is "blessed" so we want good content17:32
nati2annegentle: I submited extention WADL with compute-api WADL. And Jorge said to me he will split it from compute-api..17:32
annegentlenati2: yep, that sounds right. For extension WADL, I guess it has to be one WADL per extensions.17:32
jaypipesannegentle: I suspect the extension issue will be the major roadblock. what is the plan for dealing with WADLs/description docs for extensions to the compute and identity APIs?17:32
annegentleis one:one WADL:extension ok?17:32
annegentlejaypipes: yes it is a complete headache :) I'd like ideas honestly.17:33
annegentlewe can go another route (for getting the API site done) if WADL:extension is awful for maintenance. But it seems like a good reuse opportunity.17:33
jaypipesannegentle: I would think that as long as they are all displayed/searchable in a single website and are all well formatted and maintained, that is fine with me. It's when they get out of sync with the implmentation that things start to fall apart ;)17:33
annegentlejaypipes: yeah my hope is that WADL sync helps with implementation? But maybe that's wishful thinking?17:34
annegentle(helps with implementation sync)17:34
jaypipesannegentle: I think it depends on the vigilance of the respective PTLs...17:34
annegentleyeah17:34
annegentlewell and somewhat vigilance for WADL updates?17:35
jaypipesannegentle: yup17:35
annegentledoes anyone have enough experience with object-api to make a WADL for it?17:35
jaypipesannegentle: should probably be a step in the "release procedures", really... to check the updates to a WADL for the API.17:35
annegentlejaypipes: ah, great idea, I hadn't thought of that.17:36
jaypipesannegentle: I can probably do that...17:36
jaypipesannegentle: the object-api one...17:36
jaypipesannegentle: it's similar to the images-api in some ways.17:36
annegentlejaypipes: ok, thanks. I need to ask notmyname if they already have some ? Anyone know?17:36
jaypipesannegentle: no idea.17:36
annegentlejaypipes: ok17:36
annegentlenow my second item is Bug Squash days, starting with Feb 2nd17:36
jaypipesw00t.17:36
annegentle#link http://wiki.openstack.org/BugSquashingDay/2012020217:36
annegentleI was thinking of hosting in Austin, anyone think that would be fun in person?17:37
*** derekh has quit IRC17:37
annegentleBug squash sounds fun to me, I'd like to sit in the same room with people who are triaging and squashing so I can learn more17:37
jaypipesannegentle: yep.17:37
*** zigo has joined #openstack-meeting17:37
annegentleAlso we could squash in San Antonio in the same room :)17:37
jaypipesannegentle: but I think expanding to more than just Nova bugs would be good, too :)17:38
nati2That's cool day :)17:38
dwalleckThat would be interesting :)17:38
annegentlejaypipes: yep, that's definitely wanted :) expand the squash!17:38
annegentlethe goal is to go from 550 open bugs to 40017:38
jaypipesannegentle: in Nova, I assume?17:38
annegentlefor nova, yes, we need goals for glance, keystone, quantum too, I plan to reach out to PTLs today but wanted to talk to QA for sure17:39
jaypipesannegentle: there's 66 open ones in Tempest, 54 in Glance.17:39
annegentle#info Bug squash day Feb 2nd17:39
jaypipes86 in keystone17:39
jaypipesannegentle: yeah, I would definitely support that and can probably attend in person. Would be good to catch up with johnpur anyway ;)17:40
* annegentle should check openstack-manuals numbers too17:40
annegentlejaypipes: heh good thinking17:40
annegentleGreat, that's all I had.17:40
annegentle#info API site mockup blessed, need WADL for content17:41
annegentle(just for the notes)17:41
annegentlethanks all17:41
jaypipesannegentle: might be good to get someone like sleepsonthefloo or anotherjesse there, too. devstack has 28 open bugs and would be great to get some cross-training with QA and devstack stuff.17:41
dwalleckno problem!17:41
annegentleoh man that would be great17:41
jaypipesannegentle: just because I've found devstack to be invaluable in working with tempest...17:42
jaypipesannegentle: and the more folks we can get using the full devstack + tempest testing stack, the better in the long run for the robustness of the integration testing suite.17:42
jaypipesOK, anybody got any further questions? time to end the meeting?17:43
rohitk2Yes17:43
jaypipesrohitk2: got a question?17:43
rohitk2IIRC, is someone working on adding more clients to tempest?17:44
dwalleckJust one small thing from me. I'm working on a Keystone client right now17:44
jaypipesrohitk2: eventually :) I think we need to complete out the httplib2 client first ;)17:44
rohitk2not sure but glance and keystone were taken up17:44
dwalleck...strange timing17:44
rohitk2dwalleck: thanks for the info17:44
dwalleckYeah, we need to abstract the auth code out of the rest_client17:44
jaypipes++17:45
dwalleckA bug was filed last night that kicked me into gear17:45
AntoniHPis that already not implemented in python-novaclient lib?17:45
rohitk2dwalleck: Just the auth code or even the service+admin API clients for keystone tests17:45
rohitk2?17:45
dwalleckrohitk2: all of the Keystone API17:45
rohitk2dwalleck: cool17:46
*** dolphm has quit IRC17:46
dwalleckI may look into starting the glance one as well. Shouldn't be too hard17:46
jaypipesdwalleck: what exactly are we talking about here? are we discussing using novaclient and keystoneclient?17:47
dwalleckjaypipes: also wanted to talk to you about your exceptions branch. I think we really need to get that pushed in as well17:47
jaypipesdwalleck: or... something else?17:47
rohitk2dwalleck++17:48
jaypipesdwalleck: ++ on exceptions branch. I will get that proposed today (needed to be back home..)17:48
dwalleckjaypipes: no no, I meant filling out a new service/admin client code like we have for servers, flavors, and images in the Nova package of Tempest17:48
jaypipesdwalleck: ah, ok, that's what I thought too...17:49
dwalleckjaypipes: Awesome. I've been trying a branch locally with it for the last few weeks. It's been a huge help for debugging17:49
rohitk2jaypipes: that's what I asked :)17:49
jaypipesAntoniHP: I believe we are going to do python-novaclient after we get the straight HTTP one completed..17:49
* dwalleck hopes he's not confusing anyone. Too much benedryl 17:49
jaypipeslol17:49
dwalleckand I didn't even spell that right lol17:50
jaypipesalright, I'll head off to work on that exceptions branch then.17:50
jaypipesgood to quit meeting now?17:50
AntoniHPjaypipes: python-novaclient has straight HTTP client inside17:50
*** bhall has joined #openstack-meeting17:50
*** bhall has joined #openstack-meeting17:50
*** rick-rackspace has quit IRC17:51
jaypipesAntoniHP: yes, but it's a separate library (and has zone implementation stuff in it as well) and we want to limit the bugs to just the HTTP calls, not bugs in the novaclient library as well.17:51
*** dragondm has quit IRC17:51
dwalleckjaypipes: ++17:51
jaypipesAntoniHP: of course, we WILL definitely be adding a test suite/client that uses novaclient and not straight HTTP calls, but that will come after the straight HTTP stuff is done...17:52
rohitk2i think there's a lot of scope to add tests with just the httplib2 clients17:52
AntoniHPjaypipes: it's open source library and I think we can refactor code instead of handling two implementations, I'm not sure if bascic REST client is zone dependent17:52
jaypipesAntoniHP: good with you?17:52
*** nati2 has quit IRC17:52
AntoniHPI mean novclient already has tools for _straight_ http calls17:52
*** jdurgin has joined #openstack-meeting17:52
dwalleckThe problem with novaclient is that it hides the raw HTTP response from us17:52
jaypipesright.17:53
AntoniHPthis code is used for months now, so much less likely to have bugs17:53
*** nati2 has joined #openstack-meeting17:53
dwalleckAnd it stops me from injecting things I may need to inject (I'm talking to you Accept headers)17:53
dwalleckAnd only tests the json implementation17:54
AntoniHPwe can contribute XML implementation to librabry, in opensource it is possible for project to benefit two ways17:54
dwalleckI think we should (and will) test novaclient, but I don't want novaclient to interfere with the testing of Nova17:55
AntoniHPif we go this path, our tests could be derailed by python bugs17:55
dwalleckThe same could be said of novaclient17:56
dwalleckWe will certainly test novaclient from an external perspective, but I don't feel comfortable mixing the testing of it with the testing of Nova itself17:57
AntoniHPyes, that was my point - there is always some tool on which test depend17:57
AntoniHPI mean using this library in such was as you use httplib or linux kernel17:57
AntoniHPas it already implements basic HTTP client inside it, we can just contribute missing parts17:58
dwalleckBut by not using novaclient, I have the freedom to do what I need to do, without relying on trying to force a patch through Novaclient17:58
AntoniHPinstead of reimplemnting same17:58
dwalleckSo if we went with novaclient, how would I verify http headers returned with a response?17:58
dwalleckResponse codes (at least failures) could possibly be handled with exceptions, but anything else would be hidden17:59
rohitk2That would severly limit our negative tests17:59
dwalleckIf I want to muck with the headers (which you must do when submitting requests using bookmark links), I have no avenue to do so with novaclient18:00
jaypipesdwalleck: I suppose we could make a compromise with AntoniHP. We could use the base novaclient.client.HTTPClient class in place of tempest's restclient base class.18:00
dwalleckI know where you're coming from. That was the same approach I started with 8 months ago, until I started running into issues such as this18:00
*** troytoman-away is now known as troytoman18:00
jaypipesdwalleck: that base HTTPClient in novaclient raises all exceptions between 400 and 501 directly, allowing the caller of HTTPClient.request() to track exceptions specifically.18:01
jaypipesdwalleck: and it does auth already...18:01
dwalleckIt's just a bit late to be making changes like this. I have quite a few tests written already that I'm solidly relying on18:01
jaypipesdwalleck: so in essence, the only thing needing to change would be swapping out RestClient with novaclient.HTTPClient...18:01
jaypipesdwalleck: yes, I hear you...18:01
dwalleckI don't understand why making a change at this point would help anything18:02
AntoniHPthat is good argument, let's discuss it on list maybe as weel18:02
jaypipesdwalleck: I'm trying to find a compromise between your and AntoniHP's points that we could make happen in relatively short time period.18:02
AntoniHPas well18:02
jaypipesOK, well perhaps AntoniHP, you could email the main ML with the gist of your argument and we can have a public discussion about it there?18:04
AntoniHPOK18:04
jaypipesin the meantime, dwalleck please do continue as-is with the current approach.18:04
dwalleckjaypipes: I understand18:04
jaypipesalrighty then, any remaining issues to discuss before we end?18:05
*** ayoung has joined #openstack-meeting18:05
*** ayoung has quit IRC18:06
*** ayoung has joined #openstack-meeting18:06
jaypipesOK, bye all. See you next week. I will write a quick summary of our meeting to the ML. cheers.18:06
jaypipes#endmeeting18:06
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"18:06
openstackMeeting ended Wed Jan  4 18:06:24 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:06
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-04-17.01.html18:06
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-04-17.01.txt18:06
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-04-17.01.log.html18:06
*** darraghb has quit IRC18:06
*** rohitk2 has quit IRC18:11
*** dwalleck has quit IRC18:13
*** vandana has joined #openstack-meeting18:29
*** martine has joined #openstack-meeting18:30
*** zigo has quit IRC18:31
*** vandana has quit IRC18:46
*** deshantm_ has joined #openstack-meeting18:57
*** deshantm has quit IRC18:59
*** mattray1 has joined #openstack-meeting18:59
*** mattray has quit IRC19:00
*** dwalleck has joined #openstack-meeting19:03
*** troytoman is now known as troytoman-away19:04
*** donaldngo_hp has quit IRC19:08
*** Gordonz has quit IRC19:22
*** donaldngo_hp has joined #openstack-meeting19:26
*** donaldngo_hp has quit IRC19:26
*** dolphm has joined #openstack-meeting19:29
*** donaldngo_hp has joined #openstack-meeting19:38
*** dwcramer has joined #openstack-meeting19:38
*** deshantm_ has quit IRC19:56
*** rmk has quit IRC20:00
*** dolphm has quit IRC20:07
*** Gordonz has joined #openstack-meeting20:13
*** Gordonz has quit IRC20:13
*** Gordonz has joined #openstack-meeting20:14
*** dolphm has joined #openstack-meeting20:16
*** dolphm has quit IRC20:17
*** Gordonz has quit IRC20:26
*** dolphm has joined #openstack-meeting20:40
*** mattray1 is now known as mattray20:45
*** mattray has joined #openstack-meeting20:45
*** dprince has quit IRC21:00
*** troytoman-away is now known as troytoman21:01
*** dendro-afk is now known as dendrobates21:09
*** patelna has joined #openstack-meeting21:20
*** nati2 has quit IRC21:37
*** mattray has quit IRC21:38
*** joesavak has quit IRC21:53
*** bengrue has quit IRC21:54
*** Gordonz has joined #openstack-meeting22:00
*** martine has quit IRC22:07
*** troytoman is now known as troytoman-away22:26
*** GheRivero_ has quit IRC22:35
*** dolphm has quit IRC22:47
*** markvoelker has quit IRC22:47
*** Gordonz has quit IRC23:04
*** cdub has quit IRC23:05
*** cdub has joined #openstack-meeting23:07
*** nati2 has joined #openstack-meeting23:13
*** dwalleck_ has joined #openstack-meeting23:17
*** mdomsch has quit IRC23:18
*** nati2_ has joined #openstack-meeting23:19
*** dwalleck has quit IRC23:20
*** nati2 has quit IRC23:22
*** dragondm has joined #openstack-meeting23:29
*** gyee has joined #openstack-meeting23:29
*** ironcamel is now known as ironcamel223:31
*** ironcamel2 is now known as ironcamel23:32
*** dwcramer has quit IRC23:32
*** rnirmal has quit IRC23:41
*** gyee has quit IRC23:45

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