*** yogirackspace has left #openstack-meeting | 00:01 | |
*** somik_ has quit IRC | 00:01 | |
*** dolphm has joined #openstack-meeting | 00:27 | |
*** dolphm_ has joined #openstack-meeting | 00:28 | |
*** dolphm has quit IRC | 00:31 | |
*** zns has quit IRC | 00:39 | |
*** dragondm has quit IRC | 00:44 | |
*** Ravikumar_hp has quit IRC | 00:45 | |
*** zns has joined #openstack-meeting | 01:04 | |
*** bencherian has quit IRC | 01:16 | |
*** jdurgin has quit IRC | 01:23 | |
*** dolphm has joined #openstack-meeting | 01:29 | |
*** dolphm_ has quit IRC | 01:32 | |
*** bencherian has joined #openstack-meeting | 01:33 | |
*** vladimir3p has quit IRC | 01:37 | |
*** salv has quit IRC | 01:39 | |
*** dolphm has quit IRC | 01:56 | |
*** adjohn has quit IRC | 02:01 | |
*** dolphm has joined #openstack-meeting | 02:01 | |
*** mjfork has left #openstack-meeting | 02:08 | |
*** novas0x2a|laptop has quit IRC | 02:32 | |
*** edconzel has joined #openstack-meeting | 02:51 | |
*** danwent has left #openstack-meeting | 02:58 | |
*** dragondm has joined #openstack-meeting | 03:04 | |
*** bencherian has quit IRC | 03:09 | |
*** dolphm has quit IRC | 03:12 | |
*** wwkeyboard has left #openstack-meeting | 03:21 | |
*** zns has quit IRC | 03:27 | |
*** dolphm has joined #openstack-meeting | 03:42 | |
*** adjohn has joined #openstack-meeting | 03:56 | |
*** deshantm_laptop_ has joined #openstack-meeting | 04:15 | |
*** deshantm_laptop has quit IRC | 04:19 | |
*** deshantm_laptop_ is now known as deshantm_laptop | 04:20 | |
*** jakedahn has joined #openstack-meeting | 04:28 | |
*** adjohn has quit IRC | 05:00 | |
*** vladimir3p has joined #openstack-meeting | 05:03 | |
*** jog0 has joined #openstack-meeting | 05:03 | |
*** dolphm has quit IRC | 05:14 | |
*** vladimir3p has quit IRC | 05:22 | |
*** adjohn has joined #openstack-meeting | 05:30 | |
*** anotherjesse has quit IRC | 05:31 | |
*** lloydde has quit IRC | 06:14 | |
*** dragondm has quit IRC | 06:18 | |
*** jog0 has quit IRC | 06:37 | |
*** reed has quit IRC | 06:48 | |
*** deshantm_laptop has quit IRC | 06:57 | |
*** GheRivero has joined #openstack-meeting | 07:01 | |
*** GheRivero has quit IRC | 07:18 | |
*** GheRivero has joined #openstack-meeting | 07:26 | |
*** GheRivero has quit IRC | 07:29 | |
*** GheRivero has joined #openstack-meeting | 07:34 | |
*** adjohn has quit IRC | 07:40 | |
*** sleepsonthefloo has quit IRC | 07:50 | |
*** jakedahn has quit IRC | 08:00 | |
*** vladimir3p has joined #openstack-meeting | 08:09 | |
*** vladimir3p has quit IRC | 08:13 | |
*** darraghb has joined #openstack-meeting | 09:10 | |
*** shang has quit IRC | 10:09 | |
*** shang has joined #openstack-meeting | 10:13 | |
*** bencherian has joined #openstack-meeting | 10:19 | |
*** bencherian has quit IRC | 10:23 | |
*** shang has quit IRC | 10:33 | |
*** shang has joined #openstack-meeting | 10:49 | |
*** beekhof_ has joined #openstack-meeting | 11:31 | |
*** beekhof_ has quit IRC | 11:35 | |
*** beekhof has joined #openstack-meeting | 11:38 | |
*** beekhof has joined #openstack-meeting | 11:38 | |
*** adiantum has joined #openstack-meeting | 11:58 | |
*** SumitNaiksatam_ has quit IRC | 12:58 | |
*** zns has joined #openstack-meeting | 13:17 | |
*** zns has quit IRC | 13:19 | |
*** shang has quit IRC | 13:30 | |
*** zns has joined #openstack-meeting | 13:51 | |
*** dolphm has joined #openstack-meeting | 14:03 | |
*** lloydde has joined #openstack-meeting | 14:12 | |
*** dolphm has quit IRC | 14:31 | |
*** edconzel1 has joined #openstack-meeting | 14:32 | |
*** edconzel has quit IRC | 14:34 | |
*** deshantm_laptop has joined #openstack-meeting | 14:49 | |
*** AlanClark has joined #openstack-meeting | 14:59 | |
*** zns has quit IRC | 15:04 | |
*** zns has joined #openstack-meeting | 15:08 | |
*** reed has joined #openstack-meeting | 15:21 | |
*** dolphm_ has joined #openstack-meeting | 15:21 | |
*** GheRivero_ has joined #openstack-meeting | 15:22 | |
*** adjohn has joined #openstack-meeting | 15:54 | |
*** AntoniHP has joined #openstack-meeting | 15:55 | |
*** mikeyp has left #openstack-meeting | 15:57 | |
*** zns has quit IRC | 15:57 | |
*** dragondm has joined #openstack-meeting | 16:00 | |
*** zns has joined #openstack-meeting | 16:03 | |
*** danwent has joined #openstack-meeting | 16:07 | |
*** zns has quit IRC | 16:11 | |
*** rohitk has joined #openstack-meeting | 16:17 | |
*** dwalleck has joined #openstack-meeting | 16:20 | |
jaypipes | QA IRC meeting starting in 5 minutes on #openstack-meeting | 16:24 |
---|---|---|
jaypipes | dwalleck: heyo | 16:25 |
dwalleck | jaypipes: Howdy! | 16:25 |
dwalleck | In 5? It's not at in 35? | 16:25 |
jaypipes | dwalleck: so, I think Donald and I will just go over stuff today and then you, me, and Rick can go over stuff tomorrow.... | 16:25 |
jaypipes | dwalleck: no, it's in 5 mins AFAIK... | 16:26 |
jaypipes | dwalleck: we moved it back from 11am to noon EST | 16:26 |
dwalleck | Sure, that works | 16:26 |
dwalleck | Right, which is 35 minutes from now. Unless my clock is lying | 16:27 |
*** wwkeyboard has joined #openstack-meeting | 16:27 | |
dwalleck | Or I need more sleep | 16:27 |
jaypipes | dwalleck: oh, dang I must be losing it... | 16:27 |
jaypipes | QA IRC meeting starting in 33 minutes on #openstack-meeting | 16:28 |
dwalleck | Whew, good :) Glad to know I haven't totally lost it | 16:28 |
jaypipes | dwalleck: no, I must be losing it... | 16:28 |
*** zns has joined #openstack-meeting | 16:28 | |
AntoniHP | are we going to go back to 4pm or would it stay forever at 5pm? | 16:32 |
AntoniHP | UTC | 16:33 |
*** AlanClark has quit IRC | 16:33 | |
jaypipes | AntoniHP: good question :) would be up to the QA team. At least for the next 5 months it will remain at 5pm UTC... | 16:34 |
jaypipes | AntoniHP: when we get to the next daylight savings madness in the US, I'll ask for a vote to keep it at 5pm UTC... | 16:34 |
*** vladimir3p has joined #openstack-meeting | 16:36 | |
AntoniHP | I guess it would be best to stick to timezones where most of team members work, if it's mostly Americans then I guess let's have it fixed in your time | 16:38 |
jaypipes | AntoniHP: doesn't really matter, really. I think the west coasters would appreciate another hour to sleep in, regardless ;) | 16:40 |
*** donaldngo_hp has joined #openstack-meeting | 16:40 | |
*** reed has quit IRC | 16:47 | |
*** Ravikumar_hp has joined #openstack-meeting | 16:52 | |
*** markvoelker has joined #openstack-meeting | 16:55 | |
*** AlanClark has joined #openstack-meeting | 16:58 | |
jaypipes | QA IRC meeting starting in 2 minutes on #openstack-meeting | 16:58 |
jaypipes | dwalleck: just had a chance to look through integration.rst you sent me... | 17:00 |
jaypipes | dwalleck: looks excellent. | 17:00 |
jaypipes | dwalleck: we can go over your gerrit problems after this meeting. | 17:00 |
jaypipes | OK, let's get started | 17:00 |
jaypipes | #startmeeting | 17:00 |
openstack | Meeting started Wed Nov 30 17:00:52 2011 UTC. The chair is jaypipes. Information about MeetBot at http://wiki.debian.org/MeetBot. | 17:00 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic. | 17:00 |
dwalleck | jaypipes: Sounds good. Actually when I went to gerrit this morning, it shows my commit. strange | 17:01 |
jaypipes | westmaas, dwalleck: How's progress on identifying the missing functional tests? | 17:01 |
dwalleck | Missing as in the ones not committed yet? | 17:01 |
jaypipes | dwalleck: and missing as in "we should be testing this set of functional commands but we aren't" ;) | 17:02 |
dwalleck | I have one branch submitted for image meta tests. | 17:02 |
jaypipes | dwalleck: k, will review that one shortly. | 17:03 |
dwalleck | I have at least 3 other suites I need to bring over, but I wanted to make some of my team's work more generic so it works for everyone | 17:03 |
jaypipes | dwalleck: timeframe on that? | 17:03 |
dwalleck | Right now they're making some assumptions on what IP addresses an environment has | 17:03 |
jaypipes | k | 17:04 |
dwalleck | End of day friday would be safe. It's just some minor refactoring, and porting over the work from this week | 17:04 |
Ravikumar_hp | jaypipes: where we will put the list of missing tests | 17:04 |
jaypipes | Ravikumar_hp: that's what I'm trying to determine ;) | 17:04 |
dwalleck | I've started it as bugs for openstack integration | 17:04 |
jaypipes | dwalleck: k.. lemme grab link. | 17:04 |
jaypipes | #link https://bugs.launchpad.net/openstack-integration-tests | 17:04 |
dwalleck | I have the list on my team's Redmine. I started porting it over to bugs, but the holidays interrupted me | 17:04 |
dwalleck | That I'll commit to finishing by end of day today | 17:05 |
jaypipes | dwalleck: sounds good. I'll help with the assignment and prioritization on LP. | 17:06 |
dwalleck | And this list will only contain bugs for functionality we feel hasn't been tested yet for the sake of brevity | 17:06 |
jaypipes | dwalleck: just FYI, the reason it's important is to prevent duplication of effort with Ravikumar_hp's team... | 17:06 |
*** nati2 has joined #openstack-meeting | 17:06 | |
nati2 | Hi Sorry late | 17:06 |
dwalleck | jaypipes: Totally understood | 17:06 |
jaypipes | I will also create milestones for the openstack-integration-tests project... | 17:07 |
jaypipes | #action dwalleck to complete redmine -> LP bug migration | 17:07 |
jaypipes | #action jaypipes to create milestones in openstack-integration-tests project on LP. | 17:07 |
jaypipes | OK, continuing on integration tests topic, I'd like to discuss the documentation we're working on... | 17:08 |
dwalleck | Our team also brought up a point I wanted to bring up here. Their concern was that some of our tests might be considered almost white box, so I wanted to bring that topic here as well | 17:08 |
dwalleck | Maybe at the end | 17:08 |
jaypipes | dwalleck: sure, let's definitely discuss that right after docs. | 17:08 |
jaypipes | #link http://qa.openstack.org/ | 17:08 |
jaypipes | So, I put up some placeholder stuff and dwalleck has graciously filled out some instructions... I'm going to be uploading them shortly after this meeting. | 17:09 |
jaypipes | They will be going here: | 17:09 |
jaypipes | #link http://qa.openstack.org/integration.html | 17:09 |
jaypipes | Daryl has written details about the directory structure of tempest and how to write a new test case. | 17:10 |
nati2 | Cool | 17:10 |
jaypipes | These instructions should be helpful to anyone interested in writing new test cases (Ravi, anotherjesse, etc) | 17:10 |
Ravikumar_hp | jaypipes++ | 17:10 |
jaypipes | And FYI, for anyone who would like to contribute to the documentation efforts in QA, please do this: | 17:11 |
nati2 | Is there branch for openstack-qa-doc? | 17:11 |
jaypipes | Go to your Gerrit Settings area and make sure you have added openstack-dev/openstack-qa to your Watched Projects list | 17:11 |
jaypipes | nati2: github.com/openstack-dev/openstack-qa | 17:11 |
jaypipes | #link http://github.com/openstack-dev/openstack-qa | 17:11 |
nati2 | jaypipes: Thanks | 17:12 |
jaypipes | It is managed in Gerrit like the other core projects are. | 17:12 |
jaypipes | So please do contribute | 17:12 |
jaypipes | OK, dwalleck, let's discuss white box | 17:12 |
dwalleck | Right | 17:12 |
dwalleck | So as part of our tests for Nova, we've found that we've had to SSH into the server instances we've created to fully verify some actions | 17:13 |
nati2 | dwalleck: I agree. | 17:13 |
dwalleck | That immediately raised the white box flag for some people, but others feel that since the instance itself is a public facing entity, it is still black box | 17:14 |
rohitk | dwalleck: and the security groups and rules need to be created manually, right? | 17:14 |
dwalleck | It's a tricky spot. We've already ran into a few bugs where Nova has lied to us via the API about what its done :) | 17:14 |
dwalleck | rohtik: Those are things my team hasn't hit yet | 17:15 |
jaypipes | dwalleck: I would say that for the initial set of black box tests, we should steer clear of SSH'ing into the instances to verify state. At least for the top-priority tests, we are concerned with "does the API call take input and return output the way it is spec'd" | 17:15 |
*** zns has quit IRC | 17:15 | |
dwalleck | So for what goes into Tempest, how do you all feel? | 17:15 |
dwalleck | That's fair | 17:16 |
*** sleepsonthefloo has joined #openstack-meeting | 17:16 | |
AntoniHP | maybe looking at console output would a way to verify without depnding on network | 17:16 |
nati2 | AntoniHP: It also needed | 17:16 |
dwalleck | AtonioHP: Which console output? | 17:16 |
rohitk | #agree with jay for basic verification | 17:16 |
jaypipes | dwalleck: I think AntoniHP is referring to VNC console output | 17:17 |
AntoniHP | VM console, euca-get-console-output | 17:17 |
nati2 | And also, I wanna check server logs for negative case. | 17:17 |
dwalleck | Ahh, I see | 17:17 |
AntoniHP | like to check if metadata has been correctly fetched, or all devices are detected in VM | 17:17 |
nati2 | tempest also coulde be used for deployment setting check. So it is useful if we can check VM without NW | 17:18 |
dwalleck | Yes, there's a lot of different ways to go deeper. I just wanted to make sure what I'm committing now is generic enough for all to use | 17:18 |
jaypipes | AntoniHP: I don't have a problem with checking console output per-se, but I believe that should be a separate test case type. I think the test cases in tempest right now should stay at the "validate the API" level, and we should complete the set of those tests before diving deeper. But that's just my opinion... | 17:18 |
nati2 | jaypipes: I agree | 17:19 |
dwalleck | jaypipes: ++. We have seperate stories for console testing (which, if anyone has any thoughts on automating, I'd love to hear it :) | 17:19 |
jaypipes | AntoniHP: plus, IME, if an operation goes wrong that is only visible in white-box testing (and not in the output from an API call), I think that's a bug, too! :) | 17:19 |
dwalleck | Also, the SSH approach does not work for Windows instances of course | 17:19 |
dwalleck | Which is a whole other issue for another day | 17:19 |
jaypipes | dwalleck: ya :) | 17:20 |
rohitk | SSH would be required for many use cases, checking attached volumes, injected files etc, but those should probably fall under a different set of tests | 17:20 |
jaypipes | So, to be clear, I don't think anyone is against white-box testing approaches (like SSH or console output checks), but we're saying we should first get the API-only tests completed. | 17:20 |
dwalleck | So for now, I'll leave the SSH calls out of this | 17:20 |
dwalleck | And we can revisit later | 17:21 |
AntoniHP | jaypipes: it is asynchronous process, API calls just succeed if they are acceptable by server | 17:21 |
nati2 | We should have API-only tests milestone | 17:21 |
jaypipes | nati2: ++ | 17:21 |
jaypipes | nati2: dwalleck and I are going to get those done today. | 17:22 |
jaypipes | nati2: the milestones... | 17:22 |
nati2 | jaypipes: Thanks | 17:22 |
AntoniHP | jaypipes: it is not different then polling database later to see if changes have been reflected | 17:22 |
jaypipes | AntoniHP: sure, but a follow up call (for instance "show me the result of this prior reservation call" should return an error if an error happened. If the only way to determine an error happened is to log into a box, that's a bug :) | 17:22 |
jaypipes | AntoniHP: I think we understand each other :) | 17:23 |
jaypipes | AntoniHP: I'm just suggesting those *type* of tests be in a separate area than "tempest" | 17:23 |
jaypipes | s/area/directory or module/ | 17:23 |
nati2 | I think white-box test should be in separate directory or module on tempest in future | 17:24 |
AntoniHP | jaypipes: IMHO shoing console output falls into "how me the result of this prior (..) call" | 17:24 |
jaypipes | FYI, http://qa.openstack.org/integration.html now contains dwalleck's updates | 17:24 |
rohitk | cool | 17:25 |
jaypipes | AntoniHP: ok. what do others think? does console output fall into a separate category than SSHing to verify results? | 17:25 |
rohitk | IMO, yes since that is a different API call | 17:26 |
jaypipes | in other words, should we add methods in tempest base test classes to connect to a VNC console and verify output? | 17:26 |
dwalleck | To generalize, we could have a set of white-ish box tests which, for lack of a better term, test the side effects of API calls | 17:26 |
nati2 | dwalleck: #agreed | 17:26 |
nati2 | What's discussion point? | 17:27 |
jaypipes | dwalleck: no, I think AntoniHP is suggesting that in addition to validating the return of an API call, for some methods (like run_instance, etc), we do an assert in the test cases in tempest that connect to VNC and verify output. | 17:27 |
jaypipes | AntoniHP: did I summarize that correctly? | 17:27 |
AntoniHP | I meant accessing text-file where nova stores output from console using API call, rather than going to VNC | 17:27 |
AntoniHP | I understand that when I call this from boto library, all that I talk to i API server | 17:28 |
nati2 | AntoniHP: Yes, VNC not needed to check console output | 17:28 |
jaypipes | AntoniHP: ok. that would indeed be easier (still checking the same output, though, of course...) | 17:28 |
Ravikumar_hp | yes. vnc NOT needed | 17:28 |
jaypipes | dwalleck: thoughts? add in methods in server actions test cases that validate console output? | 17:28 |
AntoniHP | but there is no dependency on networking, unlike SSH and/or VNC | 17:28 |
jaypipes | dwalleck: AntoniHP is correct that this is a public API output that would be checked (not internal state) | 17:29 |
nati2 | jaypipes: If someone write the test code, it should be acceped | 17:29 |
jaypipes | nati2: yes... we're just having a bit of a theoretical/philosophical debate here ;) | 17:29 |
nati2 | jaypipes: gotcha | 17:30 |
dwalleck | jaypipes: I think I'm still on the wagon. By validating the console output, I'm just a bit unclear of where that occurs | 17:30 |
jaypipes | nati2: not about *whether* to accept the test code, but *where* to put it :) | 17:30 |
dwalleck | Is it logged within the server instance itself? | 17:30 |
*** zns has joined #openstack-meeting | 17:30 | |
jaypipes | dwalleck: there is an output file, yes | 17:30 |
jaypipes | dwalleck: so UIAM, we'd SSH into the server instance and read that output text file. | 17:31 |
nati2 | jaypipes: I got it. | 17:31 |
jaypipes | AntoniHP: right? | 17:31 |
*** bcwaldon has joined #openstack-meeting | 17:31 | |
dwalleck | jaypipes: Ahh, then that's clear now. That sounds reasonable | 17:31 |
nati2 | jaypipes: Console output is one of API result, so it should be go to the black-box,IMO | 17:31 |
AntoniHP | I think not, this is accessed by nova-compute code and provided to API server | 17:31 |
jaypipes | nati2, AntoniHP: ah.... was not aware of that! | 17:31 |
jaypipes | is this for both EC2 *and* OpenStack API? | 17:31 |
nati2 | jaypipes: I'm not sure, EC2 has that output | 17:32 |
* jaypipes checks real quick... one sec | 17:32 | |
AntoniHP | it basically call : please send me contents of specifica file from compute node | 17:32 |
rohitk | there is an OSAPI equivalent too | 17:32 |
nati2 | IMO, some discussion point is mixing now | 17:32 |
rohitk | do a GET on console | 17:32 |
jaypipes | rohitk: is it an undocumented extension? I can't see anything about it at http://docs.openstack.org/api/openstack-compute/1.1/content/ | 17:33 |
nati2 | 1 Console output checking is while or black ? 2 Where we put while-box test 3 milestone | 17:33 |
bcwaldon | sorry I showed up late, but what's the question here? | 17:33 |
jaypipes | nati2: we have decided console output checking is "black" | 17:33 |
nati2 | jaypipes: gotcha | 17:34 |
*** zns has quit IRC | 17:34 | |
dwalleck | bcwaldon: Talking about whether accessing an instance crosses the line between white and black box testing | 17:34 |
jaypipes | bcwaldon: to summarize, we were discussing where the white-box vs. black-box boundary was regarding methods of validating input and output of public interfaces | 17:34 |
rohitk | jaypipes: I did not see documentation for it but recall from an ML /<server_id>/consoles/<console_id> | 17:34 |
bcwaldon | ok, and the question about consoles? | 17:34 |
bcwaldon | to be clear, consoles is an undocumented extension (as jaypipes said) | 17:34 |
jaypipes | bcwaldon: is verifying console output black box testing? we decided "yes" after some discussion. | 17:35 |
AntoniHP | to my knowledge there is no call in basic openstack api for getting console output | 17:35 |
bcwaldon | and the interface *will* be changing | 17:35 |
nati2 | #https://servers.api.openstack.com/v1.1/{tenantId}/servers/{serverId}/consoles | 17:35 |
nati2 | I suppose console for Openstack API was an extension and undocumented | 17:35 |
bcwaldon | nati2: exactly | 17:35 |
jaypipes | alright, so that answers that question for now... | 17:36 |
bcwaldon | it probably shouldnt be tested in its current state | 17:36 |
jaypipes | but it brings up another big issue: EC2 vs OpenStack API. | 17:36 |
nati2 | bcwaldon: Ah sorry it was not in contrib directory,, but it is still undocumented | 17:36 |
nati2 | #https://docs.google.com/spreadsheet/ccc?key=0Ap9P99ymj9wLdEx2OEtyODNKOXpWODNObmpyR29LLUE#gid=0 | 17:36 |
nati2 | My API list covers that | 17:36 |
jaypipes | ok, everyone hold up for a second... let me summarize the discussion on this so far and get a vote from everyone. PLEASE WAIT. | 17:37 |
jaypipes | Please #agree if the following statement is correct: | 17:37 |
jaypipes | We agree that verifying console output is black-box testing and that we should aim to add methods to functional test cases (where applicable) that verify console output via API calls. | 17:38 |
nati2 | #agree | 17:38 |
rohitk | #agree | 17:38 |
Ravikumar_hp | #agree | 17:38 |
AntoniHP | #agree | 17:38 |
dwalleck | #agree | 17:38 |
donaldngo_hp | #agree | 17:38 |
jaypipes | Please #agree if the following statement is also correct: | 17:38 |
jaypipes | Currenttly EC2 supports console output API calls, but OpenStack API needs an extension. We shall document this in the integration test suite and have the afore-mentioned console output methods check to see if the OpenStack API extension is enabled before trying to gather console output in the OpenStack API tests | 17:39 |
bcwaldon | #agree | 17:39 |
AntoniHP | #agree | 17:39 |
dwalleck | #agree | 17:40 |
Ravikumar_hp | #agree - | 17:40 |
donaldngo_hp | #agree | 17:40 |
nati2 | Ah OpenStack API don't need extension for console | 17:40 |
nati2 | I checked the code, console was not in extension directory | 17:40 |
Ravikumar_hp | #info - we are writting OS API extension to support ec2 console ouput | 17:40 |
*** dolphm_ has quit IRC | 17:40 | |
nati2 | I'm not sure it is extension or not. But there is not docs in OS API | 17:40 |
bcwaldon | nati2: this is a best-case scenario, we will have to wait until consoles is documented as an extension | 17:41 |
Ravikumar_hp | it is NOT yet in OS API extension | 17:41 |
jaypipes | nati2: ok, thank you for checking that. may I assign you a task for finding out the facts about this extension? | 17:41 |
annegentle | I just logged a bug 898266 about the missing docs for console | 17:41 |
uvirtbot | Launchpad bug 898266 in nova "API command not documented - {tenantId}/servers/{serverId}/consoles" [Undecided,New] https://launchpad.net/bugs/898266 | 17:41 |
jaypipes | wow, that was fast! :) | 17:41 |
jaypipes | nati2: may annegentle assign that to you? | 17:41 |
bcwaldon | keep in mind it needs to first be converted to an extension, then it can be documented | 17:42 |
annegentle | if it's not in the contrib dir that's odd | 17:42 |
nati2 | jaypipes: gotcha, I'll talk with anne | 17:42 |
jaypipes | ah. | 17:42 |
annegentle | nati2: sounds good | 17:42 |
jaypipes | nati2: k, thx | 17:42 |
bcwaldon | and it seems like Ravikumar_hp is handling the first part | 17:42 |
nati2 | One question, who can decide it is extension or not? | 17:42 |
bcwaldon | nova-core and the nova-api team | 17:42 |
jaypipes | #action nati-san to determine current (and planned) status of the console output API extension/feature in OS API and work with annegentle to document it | 17:43 |
rohitk | question: get-console is there in OSAPI | 17:43 |
Ravikumar_hp | it has to be extension. | 17:43 |
nati2 | OK I'll ask it on mailing list | 17:43 |
rohitk | are we talking about moving it to an extension? | 17:43 |
bcwaldon | rohitk: yes | 17:43 |
bcwaldon | rohitk: it cannot exist in its current state | 17:43 |
*** zns has joined #openstack-meeting | 17:44 | |
rohitk | bcwaldon: ok | 17:44 |
jaypipes | OK, can I ask (for expedience's sake) that we take that particular discussion offline and report status back on ML? | 17:44 |
bcwaldon | absolutely :) | 17:44 |
Ravikumar_hp | yes | 17:44 |
jaypipes | alrighty, we have another big issue to discuss... | 17:44 |
jaypipes | #topic EC2 API tests not currently written in tempest | 17:45 |
*** openstack changes topic to "EC2 API tests not currently written in tempest" | 17:45 | |
jaypipes | so.... | 17:45 |
jaypipes | while dwalleck's team's focus is on the OS API, other teams need to focus on the EC2 API. | 17:45 |
jaypipes | and I'd like tempest to be able to run both sets of API tests of course | 17:45 |
bcwaldon | jaypipes: have you brought this to the attention of the ec2 api team? | 17:46 |
jaypipes | bcwaldon: one sec ;) | 17:46 |
nati2 | bcwaldon++ | 17:46 |
jaypipes | obviously, the next logical step would be to find individuals on the QA team that are interested in writing the EC2 test cases in Tempest to match the OS API ones... | 17:46 |
jaypipes | any takers? | 17:47 |
*** dolphm has joined #openstack-meeting | 17:47 | |
jaypipes | wow, hold on everybody! one at a time! ;) | 17:47 |
dwalleck | jaypipes: I need to look at the EC2 API, but how different is functionality? Are the workflows the same? | 17:47 |
bcwaldon | jaypipes: sounds like you should ask the ec2 api team | 17:47 |
dwalleck | If so, I might have an idea here | 17:47 |
jaypipes | dwalleck: no, quite different. especially around auth and other things | 17:47 |
dwalleck | Bah | 17:47 |
bcwaldon | humbug | 17:48 |
jaypipes | the alternative is to find an existing lib that stresses the EC2 API calls? boto have one perhaps? | 17:48 |
dwalleck | I have zero to test against, but I wouldn't mind giving it a try | 17:48 |
dwalleck | At least for some basic smoke tests | 17:48 |
jaypipes | dwalleck: well, to be fair, your charter is the OS API. It's what RAX will be running... so I'd prefer to have folks who have a stake in a production EC2 deploy on OpenStack... | 17:49 |
jaypipes | dwalleck: and let's not forget, nova-smoketests already does test the EC2 API (though it is white-box, not black-box, IIRC) | 17:49 |
bcwaldon | jaypipes: correct | 17:50 |
dwalleck | jaypipes: That's fair. I just didn't want to exclude the EC2 folks from Tempest | 17:50 |
jaypipes | OK, then we'll just have to backburner the EC2 API black box testing for now. I will talk with the nova EC2 team to check for interest in helping on test writing. | 17:50 |
nati2 | Is there a stake in a production EC2 deploy on OpenStack? EC2 team? | 17:50 |
jaypipes | #action jaypipes to write nova EC2 team to get help on writing black box EC2 API test cases | 17:50 |
jaypipes | nati2: that's what I'm trying to figure out :) I suspect Canonical will be a resource there... | 17:51 |
nati2 | jaypipes: Sounds cool | 17:51 |
bcwaldon | jaypipes, nati2: there were a lot of strong voices at the summit in favor of ec2 | 17:51 |
jaypipes | OK, so let's open the floor up for discussion. Anybody have things to bring up? | 17:52 |
jaypipes | #topic open discussion | 17:52 |
*** openstack changes topic to "open discussion" | 17:52 | |
*** jdurgin has joined #openstack-meeting | 17:52 | |
nati2 | I wanna make sure | 17:52 |
nati2 | White box test will be accepted on tempest? | 17:52 |
dwalleck | So I've been tinkering with implementing logging | 17:52 |
jaypipes | nati2: no | 17:52 |
AntoniHP | I have a question, is there openstack qa mailing list? | 17:52 |
jaypipes | AntoniHP: no, main mailing list, just post with [QA] in subject | 17:53 |
*** GheRivero_ has quit IRC | 17:53 | |
bcwaldon | there's a launchpad team, so there has to be a ML | 17:53 |
jaypipes | AntoniHP: there may be eventually, but not right now... | 17:53 |
rohitk | question: when are we going to mv to "tempest" in the github repo of openstack-integration-tests | 17:53 |
jaypipes | bcwaldon: trying to keep things unified for the time being | 17:53 |
dwalleck | What I've been logging so far is just requests and responses at info, and response failures as errors. | 17:53 |
nati2 | jaypipes: So some guy who needs white box test should create new project? | 17:53 |
bcwaldon | jaypipes: ok | 17:53 |
jaypipes | rohitk: good question... jeblair? | 17:53 |
jaypipes | nati2: or put in a separate directory (like kong is) | 17:54 |
jeblair | hi | 17:54 |
dwalleck | And with my next commit, I'll do the storm -> tempest transition | 17:54 |
jaypipes | nati2: eventually, we'll combine white-box stuff, too, but the priority right now is black box... | 17:54 |
rohitk | dwalleck: thanks | 17:54 |
jaypipes | jeblair: need to map out a time to migrate openstack-integration-tests to tempest... | 17:54 |
nati2 | jaypipes: Ah I got it. templest/white-some-thing. I agree with you about priority | 17:54 |
Ravikumar_hp | nati2: white box tests can go unit tests . Right? | 17:54 |
jaypipes | nati2: yes, exactly. | 17:54 |
rohitk | i also feel the top-level repository name should change too, any ideas | 17:54 |
nati2 | Ravikumar_hp: No it is not unit test | 17:55 |
dwalleck | Ravikumar_hp: They're not really unit tests since they go through the API | 17:55 |
*** edconzel has joined #openstack-meeting | 17:55 | |
jeblair | yep. i'm going to get back to work on that now | 17:55 |
jaypipes | rohitk: it was going to be tempest, right? | 17:55 |
donaldngo_hp | why do we consider sshing into a vm with public ip a white box test? | 17:55 |
jeblair | yes, tempest | 17:55 |
dwalleck | It's a pseduo white/black/? type test | 17:55 |
rohitk | yes, openstack-integration-tests --> tempest | 17:55 |
*** mdomsch has joined #openstack-meeting | 17:55 | |
jeblair | who is the best person to schedule timing with? | 17:55 |
jaypipes | donaldngo_hp: it's what you *do* with that SSH connection that determines if it's a white-box or black box test ;) | 17:56 |
jaypipes | jeblair: dwalleck and me | 17:56 |
*** edconzel1 has quit IRC | 17:56 | |
jeblair | jaypipes: cool, let's chat after meeting | 17:56 |
jaypipes | donaldngo_hp: I think anything that checks some program state that you would need knowledge of the internal workings of an application would be considered "white box" | 17:57 |
dwalleck | jaypipes: I sort of agree. To me, the real absolute white box line is if I directly access a compute node or the Xen API | 17:57 |
dwalleck | Then I'm really exploring behind the wall | 17:57 |
jaypipes | donaldngo_hp: but I agree, the lines can be blurred at times | 17:57 |
donaldngo_hp | imo sshing is no different then calling an api endpoint to spin up the vm | 17:58 |
donaldngo_hp | also SSHing seems to be a better check since the end user will need to so this as opposed to an api call | 17:59 |
donaldngo_hp | to check logs | 17:59 |
jaypipes | donaldngo_hp: SSHing into the instance, sure... SSHing into the host/dom0, not so much :) that's all I'm sayin. | 17:59 |
dwalleck | donaldngo_hp: The only problem our team has run into with the SSH methodology is that it only works for Linux. That's still going to be a vast majority of instances, but if you try to run the tests that way with a Windows instance, no luck | 18:00 |
jaypipes | donaldngo_hp: just clarifying that anything that checks the state of something that requires internal knowledge of the platform implementation (such as querying libvirt or XenAPI directly) would be white-box to me... | 18:00 |
dwalleck | Though I'm still trying to think of a clever way to inject a SSH server into a windows instance on creation :) | 18:00 |
nati2 | jaypipes: StackMonkey will do it, (kill process or something). So it should be separate directlry | 18:00 |
*** dolphm has quit IRC | 18:01 | |
jaypipes | nati2: yes, separate from the black-box tests currently in /tempest | 18:01 |
jaypipes | or /storm... | 18:01 |
jaypipes | soon to be /tempest | 18:01 |
nati2 | jaypipes: gotcha | 18:01 |
*** zns has quit IRC | 18:01 | |
jaypipes | OK, going to wrap up meeting... | 18:01 |
jaypipes | #endmeeting | 18:01 |
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/" | 18:01 | |
openstack | Meeting ended Wed Nov 30 18:01:53 2011 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 18:01 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-30-17.00.html | 18:01 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-30-17.00.txt | 18:01 |
*** rohitk has quit IRC | 18:01 | |
openstack | Log: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-30-17.00.log.html | 18:01 |
donaldngo_hp | thanks guys | 18:02 |
nati2 | Thanks Jay! | 18:02 |
*** Ravikumar_hp has quit IRC | 18:02 | |
jaypipes | donaldngo_hp: we on for 4pm today? | 18:02 |
dwalleck | Good chat :) | 18:02 |
nati2 | FYI I learn how to use ramstack in devstack. | 18:02 |
nati2 | I could be very useful to create CI env | 18:02 |
nati2 | and deployment | 18:02 |
jaypipes | donaldngo_hp: turns out dwalleck and rick can't make it at 4pm, but you and I can have a chat and I'll follow up with dwalleck and rick tomorrow... | 18:02 |
dwalleck | Sorry, in planning all afternoon :( | 18:02 |
jaypipes | dwalleck: hey, no worries man | 18:03 |
donaldngo_hp | jaypipes: sounds good | 18:03 |
*** jog0 has joined #openstack-meeting | 18:03 | |
dwalleck | But I'll definitely be available tomorrow. You both have my skype, just let me know when you guys want to gather up | 18:03 |
jaypipes | dwalleck: will do, depending on chat with donaldngo_hp this afternoon. | 18:04 |
dwalleck | sounds good! | 18:04 |
jaypipes | jeblair: chat about move of repo? | 18:05 |
jeblair | yes | 18:05 |
jeblair | so it's a hair process, and i may be making some of it up as i go along | 18:05 |
jaypipes | jeblair: there's a single changeset left around from Ravi, but I think that can be safely discarded.. | 18:05 |
*** dwalleck has quit IRC | 18:05 | |
jeblair | so let's say it may involve several hours where we say the repo isn't available | 18:06 |
jeblair | sorry, it's a "hairy" process. | 18:06 |
*** zns has joined #openstack-meeting | 18:06 | |
*** dolphm has joined #openstack-meeting | 18:06 | |
*** vandana has joined #openstack-meeting | 18:06 | |
jeblair | https://review.openstack.org/#change,1863 | 18:06 |
jeblair | what about that one? | 18:07 |
jeblair | jaypipes: ^? | 18:08 |
jaypipes | jeblair: lemme get that in right quick... | 18:10 |
jeblair | so next item: when would be a good time to do this, estimating 2 hours of repo unavailability? | 18:11 |
jaypipes | jeblair: OK, it's off to the test pit | 18:11 |
*** jog0 has quit IRC | 18:11 | |
*** jog0 has joined #openstack-meeting | 18:11 | |
jaypipes | jeblair: as soon as that changeset gets merged is fine. | 18:12 |
jaypipes | jeblair: and it is now done, so whenever you're ready, go for it. thx! | 18:12 |
jeblair | it's okay to do it without advance notice? | 18:12 |
*** dolphm has quit IRC | 18:12 | |
jeblair | jaypipes: ^ | 18:13 |
*** reed has joined #openstack-meeting | 18:14 | |
*** zns1 has joined #openstack-meeting | 18:14 | |
jaypipes | jeblair: yep. | 18:15 |
jaypipes | jeblair: me and dwalleck have pretty much been the only committers so far. | 18:15 |
jaypipes | jeblair: and once done, I'll send a note to the ML about the changed repo location. | 18:15 |
*** zns has quit IRC | 18:16 | |
jeblair | okay, sounds good | 18:16 |
jeblair | i'm starting now. i'll let you know when i'm done. | 18:17 |
jaypipes | cheers | 18:17 |
*** darraghb has quit IRC | 18:28 | |
*** jmckenty has joined #openstack-meeting | 18:36 | |
*** donaldngo_hp has quit IRC | 18:37 | |
*** rohitk has joined #openstack-meeting | 18:43 | |
*** adiantum has quit IRC | 18:55 | |
*** jmckenty has quit IRC | 18:57 | |
*** donaldngo_hp has joined #openstack-meeting | 18:58 | |
*** dolphm has joined #openstack-meeting | 19:04 | |
*** patelna has joined #openstack-meeting | 19:05 | |
*** bcwaldon has quit IRC | 19:08 | |
*** zns1 has quit IRC | 19:16 | |
*** zns has joined #openstack-meeting | 19:17 | |
*** zns has quit IRC | 19:28 | |
*** donaldngo_hp has quit IRC | 19:30 | |
*** zns has joined #openstack-meeting | 19:31 | |
*** anotherjesse has joined #openstack-meeting | 19:34 | |
*** zns has quit IRC | 19:35 | |
*** zns has joined #openstack-meeting | 19:42 | |
*** zns has quit IRC | 19:48 | |
*** zns has joined #openstack-meeting | 19:49 | |
*** zns has quit IRC | 19:53 | |
*** adiantum has joined #openstack-meeting | 20:00 | |
*** danwent has quit IRC | 20:01 | |
*** danwent has joined #openstack-meeting | 20:03 | |
*** zns has joined #openstack-meeting | 20:05 | |
*** bencherian has joined #openstack-meeting | 20:23 | |
*** rnirmal has joined #openstack-meeting | 20:28 | |
*** adiantum has quit IRC | 20:30 | |
*** danwent has quit IRC | 20:30 | |
*** jmckenty has joined #openstack-meeting | 20:34 | |
*** zns has quit IRC | 20:34 | |
*** zns has joined #openstack-meeting | 20:35 | |
*** novas0x2a|laptop has joined #openstack-meeting | 20:36 | |
*** vandana has quit IRC | 20:38 | |
*** GheRivero_ has joined #openstack-meeting | 20:41 | |
*** mdomsch has quit IRC | 20:45 | |
*** oubiwann1 has quit IRC | 20:49 | |
*** nati2 has quit IRC | 20:49 | |
*** sleepsonthefloo has quit IRC | 20:50 | |
*** anotherjesse_ has joined #openstack-meeting | 20:50 | |
*** anotherjesse has quit IRC | 20:51 | |
*** anotherjesse_ is now known as anotherjesse | 20:51 | |
*** oubiwann has joined #openstack-meeting | 20:51 | |
*** adjohn has quit IRC | 21:00 | |
*** donaldngo_hp has joined #openstack-meeting | 21:00 | |
*** adam_g has quit IRC | 21:06 | |
*** anotherjesse has quit IRC | 21:07 | |
*** reed has quit IRC | 21:07 | |
*** jog0 has left #openstack-meeting | 21:07 | |
*** jog0 has joined #openstack-meeting | 21:08 | |
*** jog0 has left #openstack-meeting | 21:08 | |
*** zns has left #openstack-meeting | 21:14 | |
*** reed has joined #openstack-meeting | 21:21 | |
*** dolphm has quit IRC | 21:28 | |
*** nati2 has joined #openstack-meeting | 21:28 | |
*** bencherian has quit IRC | 21:29 | |
*** nati2 has quit IRC | 21:36 | |
*** dolphm has joined #openstack-meeting | 21:38 | |
*** dolphm has quit IRC | 21:39 | |
*** HowardRoark has joined #openstack-meeting | 21:43 | |
*** deshantm_laptop has quit IRC | 21:47 | |
*** bencherian has joined #openstack-meeting | 21:51 | |
*** bencherian has quit IRC | 21:55 | |
*** HowardRoark has quit IRC | 22:06 | |
*** markvoelker has left #openstack-meeting | 22:18 | |
*** AlanClark has quit IRC | 22:30 | |
*** rnirmal has quit IRC | 22:38 | |
*** dolphm has joined #openstack-meeting | 22:41 | |
*** GheRivero_ has quit IRC | 22:42 | |
*** novas0x2a|laptop has quit IRC | 22:46 | |
*** jmckenty has quit IRC | 22:53 | |
*** danwent has joined #openstack-meeting | 22:53 | |
*** bengrue has quit IRC | 22:53 | |
*** bencherian has joined #openstack-meeting | 23:07 | |
*** rnirmal has joined #openstack-meeting | 23:13 | |
*** AlanClark has joined #openstack-meeting | 23:26 | |
*** AlanClark has quit IRC | 23:29 | |
*** adjohn has joined #openstack-meeting | 23:31 | |
*** rstarmer has joined #openstack-meeting | 23:39 | |
*** donaldngo_hp has quit IRC | 23:43 | |
*** danwent has quit IRC | 23:46 | |
*** patelna has quit IRC | 23:47 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!