Wednesday, 2012-01-11

*** adjohn has quit IRC00:03
*** adjohn has joined #openstack-meeting00:04
*** AlanClark has quit IRC00:15
*** salv-orlando has quit IRC00:19
*** nati2 has quit IRC00:19
*** Guest36549 has quit IRC00:20
*** ayoung has joined #openstack-meeting00:47
*** dendro-afk is now known as dendrobates00:53
*** bcwaldon has quit IRC01:02
*** heckj has joined #openstack-meeting01:03
*** gyee has quit IRC01:04
*** bcwaldon has joined #openstack-meeting01:08
*** dcramer_ has joined #openstack-meeting01:18
*** sleepsonthefloo has quit IRC01:21
*** bengrue has quit IRC01:29
*** reed has quit IRC01:38
*** jakedahn has quit IRC01:40
*** jakedahn has joined #openstack-meeting01:40
*** bhall has quit IRC01:44
*** novas0x2a|laptop has quit IRC01:47
*** novas0x2a|laptop has joined #openstack-meeting01:49
*** davlap has quit IRC01:49
*** dragondm has quit IRC01:55
*** edgarmagana has quit IRC01:57
*** dcramer_ has quit IRC01:58
*** jdurgin has quit IRC02:02
*** ohnoimdead has quit IRC02:07
*** jakedahn has quit IRC02:09
*** adjohn has quit IRC02:11
*** oubiwann1 has quit IRC02:12
*** dcramer_ has joined #openstack-meeting02:14
*** novas0x2a|laptop has quit IRC02:38
*** dendrobates is now known as dendro-afk02:38
*** dendro-afk is now known as dendrobates02:39
*** dragondm has joined #openstack-meeting02:50
*** jakedahn has joined #openstack-meeting02:51
*** deshantm_ has quit IRC03:41
*** adjohn has joined #openstack-meeting04:12
*** bcwaldon has quit IRC04:14
*** dolphm has joined #openstack-meeting04:15
*** adjohn has quit IRC04:24
*** adjohn has joined #openstack-meeting04:24
*** bengrue has joined #openstack-meeting04:26
*** adjohn has quit IRC04:26
*** dcramer_ has quit IRC04:59
*** dragondm has quit IRC05:08
*** dolphm has quit IRC05:10
*** jakedahn has quit IRC05:16
*** scottsanchez has quit IRC05:25
*** scottsanchez has joined #openstack-meeting06:38
*** bengrue has quit IRC07:04
*** hggdh has joined #openstack-meeting08:26
*** zul has joined #openstack-meeting08:31
*** carlp has quit IRC08:39
*** carlp has joined #openstack-meeting08:40
*** zul has quit IRC08:40
*** zul has joined #openstack-meeting08:44
*** nevrax has joined #openstack-meeting08:44
*** darraghb has joined #openstack-meeting09:45
*** derekh has joined #openstack-meeting10:10
*** scottsanchez has quit IRC10:28
*** mikal has joined #openstack-meeting11:02
*** GheRivero has quit IRC11:11
*** zul has quit IRC11:59
*** hggdh has quit IRC12:01
*** derekh has quit IRC12:20
*** derekh has joined #openstack-meeting12:29
*** zigo has joined #openstack-meeting12:56
*** dolphm has joined #openstack-meeting13:00
*** zul has joined #openstack-meeting13:07
*** hggdh has joined #openstack-meeting13:12
*** rkukura has joined #openstack-meeting13:23
*** dolphm has quit IRC13:59
*** dprince has joined #openstack-meeting14:03
*** deshantm has joined #openstack-meeting14:14
*** mdomsch has joined #openstack-meeting14:41
*** mattray has joined #openstack-meeting14:47
*** nevrax has quit IRC14:55
*** deshantm_ has joined #openstack-meeting15:09
*** deshantm has quit IRC15:11
*** deshantm_ is now known as deshantm15:11
*** zigo has quit IRC15:11
*** dolphm has joined #openstack-meeting15:12
*** dolphm has quit IRC15:15
*** dolphm has joined #openstack-meeting15:32
*** yamahata_ has joined #openstack-meeting15:32
*** rnirmal has joined #openstack-meeting15:49
*** wwkeyboard has left #openstack-meeting15:57
*** adjohn has joined #openstack-meeting15:59
*** bcwaldon has joined #openstack-meeting16:08
*** mahmoh has joined #openstack-meeting16:11
*** hggdh has quit IRC16:15
*** yehudasa has quit IRC16:16
*** carlp has quit IRC16:16
*** hggdh has joined #openstack-meeting16:18
*** adjohn has quit IRC16:19
*** dendrobates is now known as dendro-afk16:20
*** danwent has joined #openstack-meeting16:22
*** adjohn has joined #openstack-meeting16:23
*** adjohn has quit IRC16:23
*** dolphm has quit IRC16:25
*** dragondm has joined #openstack-meeting16:26
*** dendro-afk is now known as dendrobates16:27
*** Ravikumar_hp has joined #openstack-meeting16:36
*** dwalleck has joined #openstack-meeting16:36
*** dwalleck_ has joined #openstack-meeting16:37
*** dwalleck has quit IRC16:41
*** nati has joined #openstack-meeting16:51
*** donaldngo_hp has joined #openstack-meeting16:56
*** rickl has joined #openstack-meeting16:57
*** zul has quit IRC16:59
natiHi all!17:00
AntoniHPHi17:00
jaypipesnati: hi! :)17:00
dwalleck_Hello!17:00
jaypipesAntoniHP: g'day17:00
natijaypipes: U 2!17:00
donaldngo_hphello17:00
jaypipesdonaldngo_hp: morning17:01
Ravikumar_hpgood morning Jay17:01
*** rnirmal has quit IRC17:01
*** oubiwann has joined #openstack-meeting17:01
jaypipeswe'll start in a couple minutes...17:02
natik17:02
jaypipesRavikumar_hp: is Nayna around?17:05
jaypipes#startmeeting17:05
openstackMeeting started Wed Jan 11 17:05:19 2012 UTC.  The chair is jaypipes. Information about MeetBot at http://wiki.debian.org/MeetBot.17:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.17:05
jaypipesOK, so there are two separate topics I'd like to discuss first:17:06
Ravikumar_hpnayna is another meeting17:06
jaypipes1) Test case style17:06
*** renuka has joined #openstack-meeting17:06
jaypipes2) Using code from novaclient for basic REST client17:06
jaypipesboth topics based on email from AntoniHP today...17:06
*** dwalleck has joined #openstack-meeting17:07
*** dwalleck_ has quit IRC17:07
jaypipes#topic Test case style17:07
*** openstack changes topic to "Test case style"17:07
jaypipesso, has everyone seen AntoniHP's email from this morning?17:08
*** heckj has joined #openstack-meeting17:08
AntoniHPhere is link https://lists.launchpad.net/openstack-qa-team/msg00023.html17:08
jaypipesthere are a number of points AntoniHP raises, and I think we should discuss them here now in order. AntoniHP, ok with you?17:09
Ravikumar_hpI have not seen . may be not sent to the gruo email17:09
dwalleckIt went to the group email list, which seems a bit flaky for some reason17:09
nati[Openstack-qa-team] Implementing tests ?17:09
jaypipesRavikumar_hp: yeah, I did not get notified of it either... see link above.17:10
jaypipes#link https://lists.launchpad.net/openstack-qa-team/msg00023.html17:10
Ravikumar_hpok17:10
AntoniHPI think yes, we can discuss it here, or if more time is needed discussus it on the end of meeting?17:10
*** carlp has joined #openstack-meeting17:10
*** yehudasa has joined #openstack-meeting17:10
jaypipesAntoniHP: so, let's start with 1) Dependability of test case on each other17:10
heckjAntoniHP has a good point - there is a NOSE test driver that alleviates some of that concern however: http://pypi.python.org/pypi/proboscis/1.017:12
heckj#link http://pypi.python.org/pypi/proboscis/1.017:12
jaypipesheckj: there is no need for a test driver...17:12
jaypipesheckj: nose already supports skipping based on conditions just fine17:12
jaypipesheckj, AntoniHP: as an example, see https://github.com/openstack/tempest/blob/master/tempest/tests/test_list_servers.py17:12
heckjit is an addition to Nose - an extension, not a test driver, that allows specifications of dependencies between tests17:12
natiI suppose we already discussed about Dependability. Class way and method way17:13
natiIs this different topic17:13
nati?17:13
dwalleckI think the core issue is not whether we can have dependencies between tests, but should we17:13
heckjjaypipes: please take a look at it before you just dismiss it. I've been using it with some success to resolve some  dependency issues between tests17:13
jaypipesheckj: I have looked at it. :)17:13
*** johnpur has joined #openstack-meeting17:13
natiheckj: This moudle looks cool.17:14
heckjdwalleck - is that the concern? If so, apologies for the random link. It wasn't clear from AntoniHP's email17:14
dwalleckI think the better question is "what is the problem we are trying to solve by having test dependencies"17:14
jaypipesso, basically, I'd like to know from AntoniHP what about nosetests does not allow for 1) to be taken care of..17:15
*** vandana has joined #openstack-meeting17:15
dwalleckheckj: No, but the "should we" question is the one we need to answer here as a group17:15
*** sleepsonthefloo has joined #openstack-meeting17:15
jaypipesright17:15
AntoniHPit does, within nosetests the tests could be easily depndable17:15
dwalleckI think we have some philosophical differences on test design, so the goal is to find a solution that will either directly address everyones concerns, or allow people to use Tempest in different ways to ease those concerns17:16
natiDependency could be occur by nature when we wanna resuse testcode or exisiting resource.17:16
AntoniHPit is possible to be implemented in different ways, within nose, without nose, with extra driver etc17:17
natiSo I think this is a matter of code style. "Class vs Method"17:17
dwalleckSo if we want to reuse existing resources, wouldn't it be easier to have an external library/process handling that?17:17
AntoniHPbut as nati says this is about style, what nose test case should NOT be equal to test case17:18
dwalleckIt seems like that would be a more robust solution, and addresses the concern of execution time and reuse of resources17:18
natihmm. I suppose we are doing same discussion. I suppose both of Class style and Method style has merit and demerit.17:19
jaypipesAntoniHP: I guess I'm failing to see how the 001_, 002_ test method examples in your email would be of benefit over something like this: http://pastebin.com/2pdV34Ph17:19
natiThen I think our next action is discuss with actual code example.17:19
natithen vote it?17:20
dwalleckBut if reuse of resources isn't the core problem, help me understand where the desire for test dependencies comes from17:20
AntoniHPif there is some code between asserts and first assert fails then code is not executed17:20
dwallecknati: Actually, I think the easier idea would be for someone to submit a patch to Tempest17:20
dwalleckThat way it can follow the traditional code acceptance path, and make it easily visible17:20
jaypipesAntoniHP: but why would you have separate test methods for things that are dependent on each other to be done in an order?17:20
natidwalleck: Yes. I suppose reuse is core problem and right way to solve it is use libs.17:20
jaypipesAntoniHP: you can't parallelize them, and so you only add fragility to the test case because now dependencies between test methods must be tracked.17:21
jaypipesAntoniHP: the only advantage that your approach gives is more verbose output on successful test methods, AFAICT17:22
dwallecknati: I'm working on that solution as part of my next sprint. There's varying levels of complexity to how it could be implemented, but it will be done in some form or fashion17:22
AntoniHPjaypipes: they can be paralellized as classes17:22
jaypipesAntoniHP: and I'm confused why anyone would care about successful methods -- I only care about stuff that errors or fails?17:22
dwalleckjaypipes: ++17:22
Ravikumar_hpjaypipes +117:23
jaypipesAntoniHP: but in the case where you put a series of dependent actions in a single test method, the methods of a class can be run in parallel even with a shared resource...17:23
Ravikumar_hpi care sucess or failed .17:23
AntoniHPjaypipes: it provides context to results17:23
jaypipesAntoniHP: how so?17:23
jaypipesAntoniHP: could you provide example?17:23
Ravikumar_hpi want to fail dependent tests also instead of skiipinf17:23
vandanaAntoniHP: most of the asserts are dependent on the previous assert to have passed so would it be useful to run the second assertion if the first one failed?17:23
Ravikumar_hpskiiping17:23
natiI think by using class way. The test log looks more easy to read without adding logging code.17:24
nati#sorry typo17:24
natiThe merit of Class way is the log looks more easy to read without adding logging code.17:24
AntoniHPjaypipes: sometimes yes, and sometimes no - this also provides easy entry point for automated handling of errors17:24
dwalleckAntonioHP: So what if, regardless of test design practice, you could see the results of all assertions in the results. Is that the goal you're trying to reach?17:24
AntoniHPvandana: yes, in my example a failed response to API call could still create new object17:25
Ravikumar_hpfor reporting purpose - Success , Failed ... 1) I will fail volume-attachment tests if create volume is failed ,17:25
AntoniHPdwalleck: yes, that is why I'm totally not insitent on using this way - I proposed different solutions17:25
jaypipesAntoniHP: sorry, perhaps this is just lost in translation :) could you provide some example output that shows the benefit for automated handling of errors?17:26
AntoniHPcreate oject call -> verify response from call -> verify that object exists17:26
jaypipesRavikumar_hp: our point is that if you need to "skip" a dependent set of actions based on an early bailout or failure, the dependent set of actions should be in the same test case method...17:27
jaypipesAntoniHP: but if those calls were in the same test method, the assert message would indicate which step failed...17:28
vandanabut won't there be a lot of overhead in figuring out these dependent assertions17:28
*** nati_ has joined #openstack-meeting17:28
AntoniHPso result .F. would point to problems with API, FSS network connectivity, ..F to nova scheduler not working17:29
*** nati has quit IRC17:29
AntoniHPand then .FF would be different to .F.17:29
jaypipesAntoniHP: but so would a single F, with the error output message indicating the step that failed...17:29
dwalleckjaypipes: Right, like you did with images based on what's in the system. It makes sense for the test suite to be aware of it's surroundings and resources17:29
dwalleckSo right now I get failures like this....17:30
dwalleck======================================================================17:30
dwalleckERROR: The server should be power cycled17:30
dwalleck----------------------------------------------------------------------17:30
dwalleckTraceback (most recent call last):17:30
dwalleck  File "/var/lib/jenkins/jobs/zodiac chicago smoke/workspace/zodiac/zodiac/tests/servers/test_server_actions.py", line 33, in setUp17:30
dwalleck    self.server = ServerGenerator.create_active_server()17:30
dwalleck  File "/var/lib/jenkins/jobs/zodiac chicago smoke/workspace/zodiac/zodiac/tests/__init__.py", line 27, in create_active_server17:30
dwalleck    client.wait_for_server_status(created_server.id, 'ACTIVE')17:30
dwalleck  File "/var/lib/jenkins/jobs/zodiac chicago smoke/workspace/zodiac/zodiac/services/nova/json/servers_client.py", line 193, in wait_for_server_status17:30
dwalleck    raise exceptions.BuildErrorException('Build failed. Server with uuid %s entered ERROR status.' % server_id)17:30
dwalleckBuildErrorException: u"u'Build failed. Server with uuid e0845137-61d7-48b8-9db8-128db00cd7b5 entered ERROR status.'17:31
AntoniHPwe aim to automate, so if such logic is not in test, we would need to parse output messages then17:31
dwalleckAck17:31
dwalleckhttps://gist.github.com/3da4cc395268f5ca36cb17:31
dwalleckTry that instead, bit easier to read :)17:31
jaypipesAntoniHP: automate what exactly? the reading of test results to put on some report? Then we can just use xunit output, no?17:31
AntoniHPjaypipes: exactly !17:31
AntoniHPjaypipes: by having separate entries in units, we do not need to be very smart about parsing error messages17:32
jaypipesAntoniHP: but all that would mean is a simple --with-xunit17:32
AntoniHPjaypipes: no, because you need to parse a message in result17:32
AntoniHPto see which case has happend17:32
dwalleckI can't really post a link to my Jenkins reports, but that's pretty much what I have now with the --with-xunit17:33
AntoniHPotherwise you have a code that pinpoints failure, and captured output could be used for technical data17:33
jaypipesAntoniHP: If your automation depends on the sequence of E, F, ., and S in the test output, then something is more fundamentally wrong than the order of the test method execution IMHO17:33
nati_jaypipes: Create server sometimes fails sometime oK. And some test fails not because of this.17:34
jaypipesAntoniHP: for instance, what happens when you insert a new 00X method and F.. becomes F.F.? How does your automated reporting handle that?17:34
jaypipesAntoniHP: you would have to make a corresponding change to your automation report, no?17:35
AntoniHPthat is question to donaldngo_hp17:35
jaypipesnati_: that's a totally separate issue :)17:35
AntoniHPbut still this allows for a) continuing execution of following steps17:36
jaypipesAntoniHP: I guess my hesitation is to change to a test class/method style in order to just support a certain type of output to the test run.17:36
donaldngo_hpcant we achieve what antoni wants (which is each test class is a testing scenario with dependent steps) and what tempest provides which is code resusabitlity through service classes17:36
AntoniHPjaypipes: I agree with that statement17:36
dwalleckAntonioHP: My case is that if an assertion fails, I probably don't want to make any more assertions, and the rest will likely fail and dirty my results17:37
jaypipesdonaldngo_hp: but what we are saying is that test *methods* should contain all dependent series of actions, not the class. That way, there is no need to have dependency tracking.17:37
AntoniHPI think fundamentally this problems goes from using unit testing framework for working on other types of tests17:37
jaypipesAntoniHP: virtually every functional/integration testing framework derives from unit test frameworks.17:37
vandanadwalleck: +117:37
Ravikumar_hpjaypipes: yes . current test methods already contains dependent actions.17:38
AntoniHPyes, but I have a feeling that we are still quite bound by thinking of those tests as single unit tests17:38
jaypipesAntoniHP: they aren't. :) test *methods* are single functional tests.17:38
donaldngo_hpjaypipes: there will be still dependencies in one way or another. in antonis approach i think its a logical grouping of steps to run. using methods you still have to keep track that you need to do a before b before c ect17:39
jaypipesAntoniHP: with the test class housing shared resources the test methods use.17:39
AntoniHPjaypipes: my proposal is test *classes* are single functional tests with few test *methods* or generators (implementation detail)17:39
*** carlp has quit IRC17:39
dwalleckI don't think switching frameworks would solve that problem. Whether unit, integration, or functional, each test has a goal. It makes assertions towards that result and then ends17:39
jaypipesdonaldngo_hp: no, that's wrong. if the test method is a series of dependent actions, assertions in a or b will mean c will not be executed...17:40
jaypipesdonaldngo_hp: sorry, shouldn't say that's "wrong"... :) just my opinion...17:40
dwalleckI think what we're talking about only applies to some tests as well. I'm not sure I could see that style in use for negative tests, say one verifying that if I use an invalid image, a server won't build17:40
dwalleckWould it be fair to say that we care most about these results for the more core/smoke/positive tests that we have?17:41
dwalleckerr, more=most17:41
jaypipesAntoniHP: and in your approach, if test method 002_xxx failed, then test method 003_xxx should be skipped, right?17:41
*** carlp has joined #openstack-meeting17:41
AntoniHPno17:41
AntoniHPif 1) fails then 2) and 3) skips, if 1) succeeds then 2) and 3) execute17:42
AntoniHPbecause we can get malformed API response, yet be able to actually boot VM17:42
dwalleckbut then if 3 depends on 2 and it not skipped, 3 will fail, which would be a false positive17:42
jaypipesAntoniHP: right, and we are arguing that those three steps are assertions that should be in a single test method called test_basic_vm_launch(), otherwise you need to add stuff to test case framework to handle dependencies between test methods17:43
AntoniHPdwalleck: yes, there are different scenarious possible, sometimes test would be just like assertions and sometimes not17:43
dwalleckI think we need code here...17:43
*** gyee has joined #openstack-meeting17:43
AntoniHPjaypipes: that is false statement, generators allow to execute logical flows wihtout any nosetest additions17:44
dwalleckI can assert that I can create tests that give the same results, but are not dependent17:44
jaypipesAntoniHP: and putting the assertions in a single test method allows to execute logical flows without generators ;)17:44
dwalleckWhich then break the dependency chain, allow for class level parallel execution, and for isolated test execution17:44
AntoniHPjaypipes: no, because first raised assetion stops the test method17:45
jaypipesAntoniHP: yes, that's what you want!17:45
AntoniHPjaypipes: not in case of integration test, as I mentioned before malformed response from REST call does not indicate final result of initial call17:45
dwalleckAntoniHP: So how about this...why not re-write some of the core servers tests in the style you propose17:45
jaypipesAntoniHP: that's a totally diffrerent test than "launch this VM in a normal operation" though :(17:46
dwalleckThat way we're talking about concrete things instead of concepts17:46
jaypipesdwalleck: ++17:46
AntoniHPok, I will do this17:46
dwalleckI think it would be easier to be able to put this all on the table and compare things with real world examples17:46
jaypipesagreed17:47
dwalleckAnd that way we can see the results, compare the output, and see what is different and/or lacking17:47
jaypipesalrighty, let's let AntoniHP put some example code up to a pastebin/gist...17:48
dwalleckUntil then, I don't think further discussion will help much17:48
AntoniHPok17:48
*** hggdh has quit IRC17:49
dwalleckGood, I think that will help quite a bit17:52
donaldngo_hphow about we set up some time where we can see the code on someones desktop? i think we would all reach the end goal a lot faster then our current approach of code pasting17:52
*** oubiwann1 has joined #openstack-meeting17:52
nati_donaldngo_hp++17:53
*** carlp has quit IRC17:53
dwalleckdonaldngo_hp: I think that's a good idea. I'd still like to have a chance to see and run it before as well17:53
donaldngo_hpwe can discuss real time17:53
*** derekh has quit IRC17:53
jaypipesdonaldngo_hp: I think I'd actually prefer pastes and the public mailing list for discussion...17:54
dwalleckAnd it may help if I also share what the tempest results I'm using now look like. I think there's quite a bit that comes out of the --with-x-unit results that are fairly helpful17:54
*** oubiwann has quit IRC17:55
donaldngo_hpdwallect: would love to see what your report looks like17:56
dwalleckawesome, I'll find a way to get that viewable17:56
jaypipesdonaldngo_hp: are you using xUnit output for the feed into your reports?17:56
dwalleckAnd then we can see better what we have, and what is missing17:56
donaldngo_hpjaypies: yea we are using xunit to product xml and then aggregate into junit style report17:57
donaldngo_hp*produce17:57
*** AlanClark has joined #openstack-meeting17:57
jaypipesdonaldngo_hp: k17:57
*** carlp has joined #openstack-meeting17:57
dwalleckdonaldngo_hp: Ahh, then you're probably seeing pretty much what I am17:58
donaldngo_hpi can send our report out to the group as well17:58
jaypipesdonaldngo_hp: yes, please do! :)17:58
jaypipeslet's use the main mailing list, though, with a [QA] subject prefix... the team mailing list is proving unreliable at best :(17:58
dwalleckThough I'd like to add more...for example, my devs love that I say that a server failed to build, but without more info (the server id, IP, etc), it's not much help. I'm trying a few things to make that better17:59
* dwalleck ideally would like to pull error logs directly from the core system, but not today17:59
*** yehudasa has quit IRC17:59
*** carlp has quit IRC17:59
jaypipesdwalleck: that's what the exceptions proposed branch starts to address :)17:59
dwalleckjaypipes: yup!18:00
jaypipesdwalleck: and I've been creating a script that does a relevant log file read when running tempest against devstack...18:00
*** yehudasa has joined #openstack-meeting18:00
*** yehudasa has quit IRC18:01
dwalleckjaypipes: I was thinking along the lines of that. It's good start, but I'm afraid of how verbose it could be18:01
jaypipesdwalleck: well, the script I have grabs relevant logs, cuts them to the time period of the test run, and then tars them up :)18:02
*** yehudasa has joined #openstack-meeting18:02
*** rnirmal has joined #openstack-meeting18:02
jaypipesdwalleck: figured it would be useful for attaching the tarball to bug reports, etc18:02
dwallecknice!18:03
dwalleckThat sounds very useful18:03
jaypipesdwalleck: yeah, just can't decide whether the script belongs in devstack/ or tempest!18:03
dwalleckgood question18:03
*** jdurgin has joined #openstack-meeting18:04
AntoniHPwhen you decide can you post link to it on the list?18:04
dwallecksounds like an alternate plugin for tempest for those using devstack18:04
*** mdomsch has quit IRC18:04
jaypipesdwalleck: speaking of that... one other thing we all should decide on once we come to consensus on the style stuff is when to have tempest start gating trunk :) currently, only some exercises in devstack are gating trunk IIRC...18:04
*** nati_ has quit IRC18:04
jaypipesAntoniHP: absolutely!18:04
dwalleckjaypipes: I was thinking of the same thing. When I saw the gating trunk email, I was excited until I realized it wasn't on Tempest :)18:05
jaypipesdwalleck: right.. I added the tempest/tools/conf_from_devstack script recently to allow someone to generate a tempest config file from a devstack installation... very useful after running stack.sh ;)18:05
jaypipesdwalleck: since stack.sh wipes everything and installs new base images, which are needded in the tempest conf :)18:06
* jaypipes needs to blog about that...18:06
*** carlp has joined #openstack-meeting18:06
dwalleckHmm...I would say once we can confidently say we have a solid set of smoke tests that we consider to be reliable. That seems like a reasonable goal18:06
jaypipesdwalleck: ++18:07
jaypipesdwalleck: we're getting there...18:08
dwalleckI think we're close. The one thing I'm wrestling with is that it's bit hard to visualize coverage based on the bug list in Launchpad18:08
jaypipesdwalleck: agreed. though the tags help a bit..18:09
*** novas0x2a|laptop has joined #openstack-meeting18:09
dwalleckjaypipes: They do. I'm still going to keep bouncing that idea around in my head18:10
*** jdurgin has quit IRC18:10
dwalleckWell good folks I need to bow out, off to the next meeting18:10
*** yehudasa has quit IRC18:10
*** yehudasa has joined #openstack-meeting18:11
dwalleckOr not :) Jay is stepping away for a sec18:11
dwallecknati_: Are you still here?18:12
jaypipesAntoniHP: how about we just comment on the code on the mailing list? ok with you?18:13
*** jdurgin has joined #openstack-meeting18:13
AntoniHPI think using list would be more productive, as it is less interactive and code needs time to be read18:13
jaypipesAntoniHP: not a problem.18:13
jaypipesok good discussion so far, we will continue on the ML.18:13
jaypipes#endmeeting18:13
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"18:13
openstackMeeting ended Wed Jan 11 18:13:56 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:13
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-11-17.05.html18:13
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-11-17.05.txt18:14
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-11-17.05.log.html18:14
dwallecksounds good!18:14
*** dwalleck has quit IRC18:14
*** Ravikumar_hp has quit IRC18:14
AntoniHPok, then c u on mailing list18:15
*** Ravikumar_hp has joined #openstack-meeting18:15
*** jdurgin has quit IRC18:16
*** yehudasa has quit IRC18:17
*** carlp has quit IRC18:17
*** bengrue has joined #openstack-meeting18:18
*** rickl has quit IRC18:18
*** yehudasa has joined #openstack-meeting18:18
*** yehudasa has quit IRC18:19
*** carlp has joined #openstack-meeting18:20
*** yehudasa has joined #openstack-meeting18:20
*** yehudasa has quit IRC18:21
*** carlp has quit IRC18:21
*** jdurgin has joined #openstack-meeting18:22
*** Ravikumar_hp has quit IRC18:22
*** yehudasa has joined #openstack-meeting18:22
*** jdurgin has quit IRC18:22
*** darraghb has quit IRC18:23
*** yehudasa has quit IRC18:23
*** yehudasa has joined #openstack-meeting18:24
*** vandana has quit IRC18:24
*** yehudasa has quit IRC18:24
*** dendrobates is now known as dendro-afk18:25
*** vandana has joined #openstack-meeting18:25
*** carlp has joined #openstack-meeting18:26
*** yehudasa has joined #openstack-meeting18:26
*** yehudasa has quit IRC18:27
*** yehudasa has joined #openstack-meeting18:27
*** jdurgin has joined #openstack-meeting18:27
*** dendro-afk is now known as dendrobates18:28
*** jdurgin has quit IRC18:28
*** carlp has quit IRC18:28
*** yehudasa has quit IRC18:28
*** yehudasa has joined #openstack-meeting18:29
*** sean_roberts has joined #openstack-meeting18:29
*** yehudasa has quit IRC18:30
*** yehudasa has joined #openstack-meeting18:31
*** jdurgin has joined #openstack-meeting18:32
*** yehudasa has quit IRC18:32
*** carlp has joined #openstack-meeting18:32
*** jdurgin has quit IRC18:33
*** carlp has quit IRC18:33
*** yehudasa has joined #openstack-meeting18:33
*** yehudasa has quit IRC18:34
*** yehudasa has joined #openstack-meeting18:35
*** carlp has joined #openstack-meeting18:35
*** yehudasa_ has joined #openstack-meeting18:37
*** yehudasa has quit IRC18:37
*** carlp has quit IRC18:37
*** donaldngo_hp has quit IRC18:38
*** yehudasa_ has quit IRC18:38
*** yehudasa_ has joined #openstack-meeting18:38
*** jdurgin has joined #openstack-meeting18:38
*** jdurgin has quit IRC18:39
*** yehudasa_ has quit IRC18:39
*** carlp has joined #openstack-meeting18:39
*** yehudasa_ has joined #openstack-meeting18:40
*** carlp has quit IRC18:40
*** adjohn has joined #openstack-meeting18:40
*** yehudasa_ has quit IRC18:41
*** yehudasa_ has joined #openstack-meeting18:41
*** jdurgin has joined #openstack-meeting18:42
*** yehudasa_ has quit IRC18:42
*** yehudasa_ has joined #openstack-meeting18:44
*** jdurgin has quit IRC18:44
*** yehudasa__ has joined #openstack-meeting18:45
*** yehudasa_ has quit IRC18:45
*** carlp has joined #openstack-meeting18:46
*** yehudasa__ has quit IRC18:46
*** jdurgin has joined #openstack-meeting18:48
*** carlp has quit IRC18:48
*** carlp has joined #openstack-meeting18:49
*** jdurgin has quit IRC18:49
*** carlp has quit IRC18:52
*** heckj has quit IRC18:53
*** jdurgin has joined #openstack-meeting18:55
*** donaldngo_hp has joined #openstack-meeting18:57
*** jdurgin has quit IRC18:57
*** jdurgin has joined #openstack-meeting18:58
*** jdurgin has quit IRC18:59
*** deshantm has quit IRC19:01
*** rnirmal has quit IRC19:01
*** bcwaldon has left #openstack-meeting19:02
*** jdurgin has joined #openstack-meeting19:05
*** jdurgin has quit IRC19:07
*** jdurgin has joined #openstack-meeting19:09
*** jdurgin has quit IRC19:10
*** jdurgin has joined #openstack-meeting19:15
*** jdurgin has quit IRC19:15
*** dolphm has joined #openstack-meeting19:17
*** jdurgin has joined #openstack-meeting19:21
*** jdurgin has quit IRC19:24
*** jdurgin has joined #openstack-meeting19:26
*** mahmoh has left #openstack-meeting19:35
*** rnirmal has joined #openstack-meeting19:53
*** renuka has quit IRC19:56
*** AlanClark has quit IRC20:03
*** danwent has left #openstack-meeting20:32
*** yehudasa has joined #openstack-meeting20:47
*** dwalleck has joined #openstack-meeting20:59
*** dwalleck has joined #openstack-meeting21:05
*** bengrue has quit IRC21:09
*** AlanClark has joined #openstack-meeting21:16
*** bhall has joined #openstack-meeting21:18
*** bhall has joined #openstack-meeting21:18
*** reed has joined #openstack-meeting21:20
*** dwalleck has quit IRC21:29
*** dprince has quit IRC21:32
*** heckj has joined #openstack-meeting21:34
*** rnirmal has quit IRC21:57
*** _adjohn has joined #openstack-meeting21:58
*** adjohn has quit IRC21:58
*** _adjohn is now known as adjohn21:58
*** dwalleck has joined #openstack-meeting22:09
*** adjohn has quit IRC22:20
*** adjohn has joined #openstack-meeting22:21
*** Kiall_ has quit IRC22:26
*** dolphm has quit IRC22:27
*** dwalleck has quit IRC22:32
*** markvoelker has quit IRC22:44
*** adjohn has quit IRC23:01
*** reed has quit IRC23:01
*** sleepsonthefloo has quit IRC23:01
*** sleepsonthefloo has joined #openstack-meeting23:05
*** reed has joined #openstack-meeting23:05
*** adjohn has joined #openstack-meeting23:06
*** mattray has quit IRC23:43
*** AlanClark has quit IRC23:49

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