Thursday, 2012-07-05

*** anniec has quit IRC00:10
*** rkukura has joined #openstack-meeting00:18
*** carlp has joined #openstack-meeting00:38
*** carlp has quit IRC00:42
*** danwent has quit IRC01:02
*** Gordonz has joined #openstack-meeting01:03
*** sandywalsh has joined #openstack-meeting01:08
*** anniec has joined #openstack-meeting01:38
*** shang has joined #openstack-meeting02:17
*** dwcramer has quit IRC02:19
*** clarkb has quit IRC02:19
*** clarkb1 has joined #openstack-meeting02:19
*** ayoung has quit IRC02:23
*** clarkb1 has quit IRC02:27
*** anniec has quit IRC02:31
*** anniec has joined #openstack-meeting02:33
*** dwcramer has joined #openstack-meeting02:39
*** Gordonz has quit IRC02:41
*** ryanpetrello has joined #openstack-meeting02:43
*** dwalleck has joined #openstack-meeting02:48
*** anniec has quit IRC02:53
*** anniec has joined #openstack-meeting02:58
*** dwcramer has quit IRC03:09
*** anniec has quit IRC03:09
*** littleidea has joined #openstack-meeting03:10
*** rkukura has quit IRC03:10
*** ryanpetrello has quit IRC03:16
*** dwcramer has joined #openstack-meeting03:22
*** clarkb1 has joined #openstack-meeting03:44
*** anderstj has joined #openstack-meeting03:47
*** clarkb1 is now known as clarkb03:47
*** carlp has joined #openstack-meeting03:57
*** carlp has quit IRC04:02
*** sandywalsh has quit IRC04:10
*** garyk has quit IRC04:33
*** carlp has joined #openstack-meeting04:33
*** lloydde has joined #openstack-meeting04:33
*** carlp has quit IRC04:38
*** littleidea has quit IRC04:44
*** littleidea has joined #openstack-meeting04:45
*** dwalleck has quit IRC05:05
*** matiu has quit IRC05:08
*** carlp has joined #openstack-meeting05:17
*** sacharya has quit IRC05:17
*** carlp has quit IRC05:21
*** matiu has joined #openstack-meeting05:21
*** matiu has quit IRC05:21
*** matiu has joined #openstack-meeting05:21
*** anderstj has quit IRC05:31
*** danwent has joined #openstack-meeting05:39
*** rohitk has joined #openstack-meeting05:43
*** jakedahn_zz is now known as jakedahn05:43
*** danwent has quit IRC05:55
*** jakedahn is now known as jakedahn_zz06:18
*** lloydde has quit IRC06:19
*** jakedahn_zz is now known as jakedahn06:32
*** jakedahn is now known as jakedahn_zz06:37
*** garyk has joined #openstack-meeting06:49
*** littleidea has quit IRC07:08
*** matiu has quit IRC07:27
*** lloydde has joined #openstack-meeting07:29
*** lloydde has quit IRC07:34
*** matiu has joined #openstack-meeting07:39
*** darraghb has joined #openstack-meeting08:45
*** Mandell has quit IRC08:46
*** anniec has joined #openstack-meeting08:58
*** anniec_ has joined #openstack-meeting08:59
*** anniec has quit IRC09:03
*** anniec_ is now known as anniec09:03
*** matiu has quit IRC09:25
*** matiu has joined #openstack-meeting09:37
*** matiu has quit IRC09:37
*** matiu has joined #openstack-meeting09:37
*** markmcclain has joined #openstack-meeting10:46
*** shang has quit IRC11:17
*** sandywalsh has joined #openstack-meeting11:49
*** rohitk has quit IRC11:50
*** rohitk has joined #openstack-meeting11:51
*** sandywalsh_ has joined #openstack-meeting11:55
*** sandywalsh has quit IRC11:56
*** kiffer84 has quit IRC12:25
*** tongli has joined #openstack-meeting12:38
*** rohitk has quit IRC12:47
*** ncode has joined #openstack-meeting12:51
*** ncode has joined #openstack-meeting12:51
*** markmcclain has quit IRC12:52
*** matiu has quit IRC13:05
*** ryanpetrello has joined #openstack-meeting13:16
*** ryanpetrello has quit IRC13:21
*** ryanpetrello has joined #openstack-meeting13:22
*** ayoung has joined #openstack-meeting13:22
*** matiu has joined #openstack-meeting13:22
*** zul has quit IRC13:24
*** mnewby has joined #openstack-meeting13:25
*** ryanpetrello has quit IRC13:26
*** markmcclain has joined #openstack-meeting13:29
*** rohitk has joined #openstack-meeting13:32
*** zul has joined #openstack-meeting13:32
*** dprince has joined #openstack-meeting13:33
*** markmcclain has quit IRC13:34
*** rkukura has joined #openstack-meeting13:46
*** cp16net is now known as cp16net|away13:48
*** sandywalsh_ has quit IRC13:49
*** mdomsch has joined #openstack-meeting13:50
*** blamar has joined #openstack-meeting13:50
*** oubiwann has joined #openstack-meeting13:54
*** davidkranz_ has joined #openstack-meeting14:01
*** tongli has quit IRC14:03
*** lloydde has joined #openstack-meeting14:04
*** ryanpetrello has joined #openstack-meeting14:04
*** davidkranz has quit IRC14:04
*** troytoman-away is now known as troytoman14:11
*** zul has quit IRC14:13
*** zul has joined #openstack-meeting14:14
*** Mandell has joined #openstack-meeting14:19
*** dtroyer_zzz is now known as dtroyer14:28
*** mnewby has quit IRC14:29
*** dolphm has joined #openstack-meeting14:29
*** dwalleck has joined #openstack-meeting14:30
*** sacharya has joined #openstack-meeting14:30
*** mnewby has joined #openstack-meeting14:30
*** cp16net|away is now known as cp16net14:30
*** lloydde has quit IRC14:33
*** dwalleck has quit IRC14:38
*** sandywalsh has joined #openstack-meeting14:41
*** Mandell has quit IRC14:44
*** rnirmal has joined #openstack-meeting14:51
*** littleidea has joined #openstack-meeting14:52
*** mnewby has quit IRC14:57
*** markmcclain has joined #openstack-meeting15:00
*** garyk has quit IRC15:10
*** _ozstacker_ has joined #openstack-meeting15:10
*** hggdh has quit IRC15:12
*** ozstacker has quit IRC15:13
*** Gordonz has joined #openstack-meeting15:14
*** Gordonz has quit IRC15:18
*** Gordonz has joined #openstack-meeting15:19
*** hggdh has joined #openstack-meeting15:23
*** ryanpetrello has quit IRC15:38
*** markmcclain has quit IRC15:38
*** matiu_ has joined #openstack-meeting15:38
*** matiu_ has quit IRC15:38
*** matiu_ has joined #openstack-meeting15:38
*** matwood has joined #openstack-meeting15:40
*** dachary has joined #openstack-meeting15:41
*** matiu has quit IRC15:41
*** danwent has joined #openstack-meeting15:42
*** rohitk has quit IRC15:44
*** mnewby has joined #openstack-meeting15:50
*** rkukura has quit IRC15:51
*** dendrobates is now known as dendro-afk15:55
*** flacoste has joined #openstack-meeting15:57
*** flacoste has joined #openstack-meeting15:57
openstackMeeting started Thu Jul  5 16:00:13 2012 UTC.  The chair is nijaba. Information about MeetBot at
nijaba#meetingtopic Ceilometer16:00
nijaba#chair nijaba16:00
nijaba#info jd__ will unfortunately not be able to join us this week16:00
nijabaHello everyone! Show of hands, who is around for the ceilometer meeting?16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: Ceilometer)"16:00
openstackCurrent chairs: nijaba16:00
nijabajd___: I thought you could not join?16:00
nijabanice to see you!16:00
jd___for now I can, I may leave early16:00
nijabaflacoste: around?16:00
flacostei am16:01
nijabaok, great!, let's start!16:01
nijaba#topic actions from previous meetings16:01
nijabaI don't see any action from the last meeting.  Did I miss anything?16:01
*** openstack changes topic to "actions from previous meetings (Meeting topic: Ceilometer)"16:01
dhellmannIIRC the only thing that carried over was the discussion of the incubation proposal16:01
nijabaok, we have that as a topic for today16:02
dhellmannwell, that and "keep working on the code" :-)16:02
nijaba#topic Discuss and vote the incubation application proposal to be submitted to PPB16:02
nijabaAny remarks before we vote on this?16:02
*** openstack changes topic to "Discuss and vote the incubation application proposal to be submitted to PPB (Meeting topic: Ceilometer)"16:02
dhellmannI think it looks good, but do we have examples of the proposals other projects have put up (especially successful proposals)?16:02
jd___looks good to me16:03
nijabadhellmann: I don't think there has been any...16:03
dhellmannceilometer: breaking new ground, yet again16:03
nijabashall we vote then?16:03
nijaba#startvote Submit the incubation application to the PPB? Yes, No16:03
nijabaPlease note that to register a vote you have to use #vote yes or #vote no16:03
openstackBegin voting on: Submit the incubation application to the PPB? Valid vote options are Yes, No.16:03
openstackVote using '#vote OPTION'. Only your last vote counts.16:03
nijaba#vote yes16:04
dhellmann#vote yes16:04
openstacknijaba: yes is not a valid option. Valid options are Yes, No.16:04
openstackdhellmann: yes is not a valid option. Valid options are Yes, No.16:04
dhellmann#vote Yes16:04
nijaba#vote Yes16:04
jd___#vote yes16:04
openstackjd___: yes is not a valid option. Valid options are Yes, No.16:04
nijabaamazing these little tools... so picky ;)16:04
jd___#vote Yes16:04
jd___yeah yeah c'mon openstack!16:04
flacoste#vote yes16:04
openstackflacoste: yes is not a valid option. Valid options are Yes, No.16:04
*** whitt has joined #openstack-meeting16:04
flacoste#vote Yes16:04
* dhellmann lol16:05
nijabaok, that's a wrap for the vote16:05
openstackVoted on "Submit the incubation application to the PPB?" Results are16:05
openstackYes (4): nijaba, dhellmann, jd___, flacoste16:05
nijabaSo, I'll send a very formal email for our application ASAP16:05
nijaba#action nijaba to send an email to the PPB16:05
nijaba#topic PTL election process discussion16:06
nijabaWhen we had our first project meeting on April 26th, it was agreed that Loic Dachary and I would co-lead this project for the first 3 months. Time is soon up for those 3 months, so we should discuss what to do to.16:06
*** openstack changes topic to "PTL election process discussion (Meeting topic: Ceilometer)"16:06
dhellmannnijaba, is that a publicly readable mailing list?16:06
nijabait is, yes16:06
nijabathe archives are16:06
nijabaI propose that we:16:06
nijaba1/ Make a call for candidate next week, asking for applicants to do so on the general mailing list16:06
nijaba2/ Open a one week voting period from July 26th til Aug 2nd16:06
nijaba3/ Use the opavote voting as  it is less likely to produce ex-aequo16:06
nijaba4/ Limit voters and candidates to people that have contributed either to the code or to the wiki pages for ceilometer prior to the call for candidates16:06
nijabaComments? Remarks? Suggestions?16:06
* jd___ checks opavote16:07
dhellmannthe voting limits seem appropriate. do you already have a list of who those people are?16:07
* nijaba waits a couple minutes for people to digest16:07
nijabadhellmann: nope16:07
flacostenijaba: sounds good to me16:08
nijababut it would not be too hard to compile16:08
jd___not that many I guess16:08
jd___what's the voting system for other PTL elections?16:08
nijabathey were using civs, but are about to switch to opa16:08
jd___ok, that seems fine anyway :)16:09
*** anniec has quit IRC16:09
nijabalooks like we have a general agreement then?  Should we formally vote on this?16:10
jd___yes and if you want yes16:10
nijaba#startvote go ahead with the proposed PTL election process? Yes, No16:11
openstackBegin voting on: go ahead with the proposed PTL election process? Valid vote options are Yes, No.16:11
openstackVote using '#vote OPTION'. Only your last vote counts.16:11
dhellmann#vote Yes16:11
nijaba#vote Yes16:11
jd___#vote Yes16:11
flacoste#vote Yes16:11
openstackVoted on "go ahead with the proposed PTL election process?" Results are16:12
openstackYes (4): nijaba, dhellmann, jd___, flacoste16:12
nijabacool.  Do you want me to take the call for candidate action?16:12
nijabahowever, I'll be off until the 28th, so someone else will need to do the opa setup16:12
jd___I probably can do this16:13
nijabathanks jd___16:13
nijaba#action nijaba to send call for candidate to the general mailing list16:13
*** mestery has joined #openstack-meeting16:13
nijaba#action jd___ to setup opa voting system to start on 26th and end on Aug 3rd16:14
nijabaok, moving on16:14
nijaba#topic Discuss project's next priorities16:14
nijabaThis topic was suggested by dhellmann, so I let him drive it16:14
*** openstack changes topic to "Discuss project's next priorities (Meeting topic: Ceilometer)"16:14
dhellmannThanks, nijaba.16:14
dhellmannIt seems to me like we've reached another milestone now that we can actually store data. There are a couple of different directions we can go from here, either one at a time or in parallel.16:15
dhellmannThere are still quite a few plugins to write, and code to integrate with other projects (especially for notifications, but also for polling).16:15
dhellmannWe need to build the API server.16:16
nijabaI think we may need additional agents too?16:16
dhellmannyes, good point, we may need other agents depending on where the plugins need to run16:16
dhellmannwe need at least one more for polling services through their REST APIs16:16
dhellmannwe may also want to implement another db backend to ensure that the plugin layer API is not mongodb-specific16:17
nijabaI think we need to list these items on a roadmap wiki page, linking to bugs, that people can assign themselves to...16:17
jd___nijaba: +116:17
*** joearnold has joined #openstack-meeting16:17
dhellmanngood idea16:17
nijabaand then publicise it to try to recruit new coders16:17
nijabathat was the idea behing documenting how to write pludgins16:18
dhellmannI would like to finish writing some more dev docs before we try to recruit too many more contributors -- I am doing that today and hope to have a patch ready for review tomorrow16:18
nijabasounds great16:18
nijabaShould we start a general action to have a ceilometer/roadmap page populated?16:19
nijabaI can prime it16:19
dhellmanndoes anyone have any strong opinion about what we should make our next priority?16:19
nijaba#action nijaba to prime a roadmap page and invite others to populate it16:19
dhellmannI would like to have the data going end-to-end (agent -> collector -> db -> api -> consumer) soon16:20
nijabadhellmann: I'd think swift, but that will not match what YOU will want ;)16:20
jd___probably the API server16:20
flacostei think the api server is probably the missing piece there16:20
jd___and implement the meter type as we discussed several time I think it's still missing16:20
dhellmannnijaba, we'll get swift done, don't worry :-)16:20
dhellmannjd___ there's a field in the meter messages for "type" but nothing actually uses it right now16:21
nijabadhellmann: leave something for flacoste's team when it get there :)16:21
*** thingee has joined #openstack-meeting16:21
jd___dhellmann: yeah, I should really tackle this down instead of talking about it16:21
flacostenijaba: it's getting there :-)16:21
nijabajd___: feel free to assign an action to yourself ;)16:21
dhellmannnijaba, if flacoste wants to work on swift we can wait16:21
jd___#action jd___ handle counter/meter type for real16:22
nijabadhellmann: I suspect you will want to do someting with some other tech ;)16:22
dhellmannnijaba, yeah, I think ceph already has some monitoring in place, but that's up to another team to handle for now. :-)16:23
nijabaok, should we move on?16:23
dhellmannyes, I'm done and it sounds like we have a good plan for working out what to do next16:23
nijaba#topic Open Discusssion16:24
*** openstack changes topic to "Open Discusssion (Meeting topic: Ceilometer)"16:24
*** ryanpetrello has joined #openstack-meeting16:24
*** jakedahn_zz is now known as jakedahn16:24
nijabaI have one: External API. Based on the mailing list discussion16:24
nijabaI believe we reached an agreement on the purpose and limitations of the API, but wanted to make sure we were...16:24
flacostenijaba: i really appreciated your clarification email16:24
jd___I think so, for now at least :)16:24
flacosteand agree with it16:24
*** markmcclain has joined #openstack-meeting16:24
nijabaflacoste: thanks :)16:25
dhellmannyes, nijaba, thank you for that!16:25
nijabaI am assigning myself a documentation task for the API with a clear warning about the limitation of the sum and duration function16:25
*** dwcramer has quit IRC16:25
nijaba#action nijaba to document external API use with a clear warning about the limitation of the sum and duration function16:25
nijabawell, actually, I will start a doc, which will have to wait for completion hat we have something coded :)16:26
nijabadoes anyone want want to bring something else?16:27
* dhellmann shakes head no16:27
nijabasounds like a wrap...16:27
*** openstack changes topic to "OpenStack meeting channel. See for schedule and for meeting logs"16:27
openstackMeeting ended Thu Jul  5 16:27:40 2012 UTC.  Information about MeetBot at . (v 0.1.4)16:27
openstackMinutes (text):
*** thingee has left #openstack-meeting16:27
*** lloydde has joined #openstack-meeting16:27
jd___thanks guys!16:27
nijabathanks everyone! nice and smoth!16:27
nijabasmooth too!16:27
*** _ozstacker_ has quit IRC16:28
*** dachary has quit IRC16:29
*** flacoste has left #openstack-meeting16:29
dhellmannthanks, everyone!16:30
*** garyk has joined #openstack-meeting16:31
*** anderstj has joined #openstack-meeting16:31
*** anniec has joined #openstack-meeting16:35
*** mestery has quit IRC16:36
*** zvm-vlam has quit IRC16:42
*** zvm-vlam has joined #openstack-meeting16:44
*** littleidea has quit IRC16:45
*** littleidea has joined #openstack-meeting16:45
*** jakedahn is now known as jakedahn_zz16:45
*** zigo has joined #openstack-meeting16:46
*** dwcramer has joined #openstack-meeting16:46
*** jaypipes has quit IRC16:48
*** martines has joined #openstack-meeting16:49
*** donaldngo has joined #openstack-meeting16:50
*** reed has joined #openstack-meeting16:52
*** nati_ueno has joined #openstack-meeting16:55
*** dachary has joined #openstack-meeting16:56
*** dwalleck has joined #openstack-meeting16:57
*** jaypipes has joined #openstack-meeting16:59
jaypipesafternoone QAers.17:00
*** davidkranz_ is now known as davidkranz17:00
davidkranzGood afternoon.17:01
jaypipesdavidkranz: feel like running the meeting today?17:01
davidkranzJuly 4 on Wednesday should be banned.17:01
*** matiu_ has quit IRC17:01
dwalleckdavidkranz: +++++++++17:01
dwalleckit's totally messing me up17:02
davidkranzjaypipes: OK17:02
davidkranzAny one else here?17:02
davidkranzdwalleck: Do you have any comments about commonly used extensions in smoke tests?17:02
openstackMeeting started Thu Jul  5 17:03:05 2012 UTC.  The chair is jaypipes. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:03
* jaypipes currently doing the code review on rohit's branch.17:03
dwalleckdavidkranz: Not completely yet. I know it's a slippery slope to say which extensions are core and which are not. Unless there's a good criteria we can use17:04
* dwalleck is coughing his lungs back out17:04
*** rohitk has joined #openstack-meeting17:04
jaypipesdavidkranz, dwalleck: I don't have any problems per-se with dwalleck's smoke testing refactor/speedup branch. I still prefer smoke tests to be slighly different, with a sequential set of steps that follow numerous API calls (not just limited to servers or images or keypairs, etc17:04
davidkranzjaypipes: I think that makes some sense. We have to make sure that the smoke tests keep up with new apis.17:05
dwalleckjaypipes: Well, this was an initial, immediate solution17:05
davidkranzdwalleck: Sure. The reason I like Jay's suggestion is that the requirement that smoke test cases have to be subsets of full coverage is limiting.17:06
jaypipesdwalleck: oh, I totally understand (and support the patch)17:06
*** jdurgin has joined #openstack-meeting17:06
davidkranzdwalleck: If we adopt the scripted actions then we can control the use of expensive functions in a better way I think.17:07
dwalleckdavidkranz: What do you mean by scripted actions?17:07
jaypipesdavidkranz: sorry, could you elaborate on "adopt the scripted actions"?17:07
jaypipesdavidkranz: oh, I think I know what you mean...17:07
davidkranzdwalleck: Sorry, I just meant the kind of thing Jay was saying.17:07
* dwalleck is getting confused. I need more cold medicine. Or less17:07
jaypipesdavidkranz: you mean "adopt practice of using sequential series of common actions"17:08
davidkranzjaypipes: Yes :)17:08
jaypipesdwalleck: you shouldn't live with a cat if you have allergies :P17:08
dwalleckMy concern is how we control the flow of that. I know the numerical test ordering works, but I'd like to see something more explicit if we're really going to go in and fix this17:08
dwalleckjaypipes: Cats came with the fiance, no choice :-)17:09
jaypipesdwalleck: I'm actually more in favour of creating separate smoke tests entirely from the positive./negative/detailed test cases we currently have...17:09
jaypipesdwalleck: and these smoke tests would be simply sequential test methods (named test_00X_blah) that would exercise the default or common API actions17:10
dwalleckjaypipes: Right. I think what I'm trying to ask is what they will look like17:10
dwalleckwhich you just said :-)17:10
davidkranzdwalleck: I think Jay included an example in the code Rohit took over.17:10
jaypipescool. well, actually, rohit's patch actually used my original smoke test branch as a base...17:11
jaypipesso it might be worth looking into that next (after dwalleck's intermediate patch goes in)17:11
jaypipesand once we have that, we should modify the jenkins job to fire ./ --smoke instead of the whole shebangh17:11
jaypipesyou guys agree with that?17:11
jaypipesso, these steps:17:12
davidkranzjaypipes: But we would still run the whole thing nightly, right?17:12
jaypipes1) get dwalleck's patch for decreasing time of smoke down17:12
jaypipes2) edit the jenkins job to run smoke only17:12
jaypipes3) work on merging in rohit's patch17:12
jaypipes4) set up the separate jenkins "slave jobs" that would fire the entire test suite17:12
jaypipesthat amenable to you guys?17:13
davidkranzjaypipes: Sounds good17:13
jaypipesdwalleck: ?17:13
*** JoseSwiftQE has joined #openstack-meeting17:13
davidkranzjaypipes: What about soft reboot? It takes 2.5 minutes for me. Doesn't it kill you, and should it be in the smoke test?17:13
jaypipesdavidkranz: ah, goood point...17:13
jaypipesdwalleck: there was one tiny mistake in your patch to fix. What about fixing the soft reboot thing while you fix that mistake?17:14
dwalleckIn general I'm on board. I have concerns with using test naming as a means of ordering17:14
jaypipesdwalleck: basically, make sure only hard reboot is in any smoke tests...17:14
davidkranzi don't understand how Daryl got the time down so low if he has the same issue with soft reboot.17:14
jaypipesdavidkranz: still takes around 5 minutes IIRC17:14
dwalleckjaypipes: Not sure what you mean by fix soft reboot. it's currently commented out17:14
dwalleckFix as in add back in?17:15
jaypipesone sec, lemme double-check.17:15
*** dwcramer has quit IRC17:15
*** Mandell has joined #openstack-meeting17:15
davidkranzdwalleck: Arg. I forgot I did that!17:15
rohitkjaypipes: We wouldn't want to see any negative tests in smoke suite right?17:16
davidkranzrohitk: Right.17:16
jaypipesrohitk: correct17:16
jaypipesdavidkranz: yes, dwalleck is correct. it is skipped.17:16
jaypipesdavidkranz: verified. line 69 in test_servers_actions.py17:16
*** PotHix has joined #openstack-meeting17:24
jaypipesok, ok.17:24
davidkranzjaypipes: Yeah. I withdrew the skipping from my first commit but then we agreed it should be skipped because the spec is such a mess anyhway.17:24
jaypipesalright, you three (rohit, david, daryl): are we good to try and get #1 through #3 above done TODAY?17:24
* jaypipes can handle the review on rohitk's branch as well as the jenkins changes...17:24
jaypipesin fact, I can get the jenkins changes sorted in the next hour or so...17:24
*** matiu_ has joined #openstack-meeting17:24
*** matiu_ has quit IRC17:24
*** matiu_ has joined #openstack-meeting17:24
jaypipesgoing to ask jeblair for some help in resetting the data on the Tempest job after it switches to run smoke tests by default17:24
davidkranzjaypipes: Sounds good.17:24
davidkranzWhat about the issue of gating Tempest itself?17:24
jaypipesdavidkranz: Tempest  is already gated, but only on pep8 :(17:24
davidkranzWe still need a way to make sure tempest doesn't get broken.17:24
davidkranzBut we can't really run the whole thing.17:24
jaypipesdavidkranz: yeah, but unfortunately, it's not so easy... but I will work with jeblair on some options17:24
jaypipesdavidkranz: the reason is because of the interdependencies in the way that the job gets triggered...17:24
jaypipesbut regardless, I will chat with the CI team and see what we can do.17:24
davidkranzjaypipes: We may have to live with a nightly run.17:24
dwalleckbrb, cat's on fire17:24
davidkranzjaypipes: I just want there to be clarity on code reviews.17:24
jaypipesdavidkranz: perhaps -- but let's wait and see what's possible.17:24
jaypipesdavidkranz: agreed 100%17:24
davidkranzjaypipes: sure, let's see. BUt I think we should require that code reviewers *Not* have to think they are gonig to find every runtime bug that might happen.17:24
*** kiffer84 has joined #openstack-meeting17:24
jaypipesdavidkranz: ++17:24
davidkranzjaypipes: We will have to rely on the judgement of submitters that they run the right subset before checkin.17:24
jaypipesdavidkranz: let me chat with jeblair about the options here... perhaps we could have a commit to Tempest trigger the entire test suite and a commit to the core projects trigger only the smoke run? And also do nightly snapshot against full tempest?17:24
davidkranzjaypipes: That would be ideal but I am concerned that running the entire test suite will still consume too many resources.17:24
davidkranzjaypipes: We could have a 'slow' attribute that is skipped by everything but nightly tests. I have done that in past projects.17:25
*** troytoman is now known as troytoman-away17:26
jaypipesdavidkranz: but we don't want change to tempest passing the *tempest gate* that don't pass all tempest tests, right?17:26
jaypipesdavidkranz: the number of changes to tempest right now isn't all that much. I think I'd prefer to err on the side of correctness vs. efficiency for the tempest gate17:26
davidkranzjaypipes: OK, let's give it a shot. We can deal with the issue later if necessary.17:27
jaypipesJoseSwiftQE: any update for us, my man?17:27
JoseSwiftQEI looked over the review just this morning17:27
JoseSwiftQEWhat do you suggest for the rest client re: headers=None?17:28
jaypipesJoseSwiftQE: I was just saying that you can remove the =None on that particular line and pass in  headers=headers17:28
JoseSwiftQEAh, so that way it uses in the restclient default headers?17:29
jaypipesJoseSwiftQE: since the way it is now, you're overriding anything passed in to the function in the header param..17:29
*** dwcramer has joined #openstack-meeting17:29
JoseSwiftQEthat makes sense, thanks.17:29
jaypipesya, no worries17:29
davidkranzShould we move on to the testing Folsom features issue?17:29
JoseSwiftQEsure, i'm done17:29
jaypipesyes, let's.17:29
jaypipes#topic Testing new features when they come around17:30
*** openstack changes topic to "Testing new features when they come around"17:30
jaypipesdavidkranz: floor is yours17:30
davidkranzI think the first thing is to get the ptls to tell us when things are ready for "outsider" testing.17:30
*** gyee has joined #openstack-meeting17:30
jaypipesdavidkranz: that won't happen unless we bug them :)17:30
jaypipesdavidkranz: so we need a point person in the QA team (perhaps for each core project) that will bug the PTLs (in status meetings, on IRC, on ML, etc)17:31
davidkranzjaypipes: Right.17:31
davidkranzjaypipes: But I hope the PTLs will quickly decide it is easier to make a habit of "releasing" features to QA when they are ready in a proactive way.17:32
dwalleckcat longer on fire, back17:32
rohitkdavidkranz: ++17:32
*** jakedahn_zz is now known as jakedahn17:32
jaypipesdavidkranz: agreed. in order for PTLs to decide that we should have our process (of QA validation of new features) by explicit and well-defined on the wiki.17:33
davidkranzdavidkranz: I don't have a good feel for how the PTLs view the QA situation. Are they happy with the current state of affairs?17:33
dwalleckdavidkranz: While I agree on the idea, I'm wondering if we shouldn't be a bit more agile and start working on testing as the features are being worked on17:33
jaypipesdavidkranz: totally different between core projects (which is part fo the problem)17:33
jaypipesdwalleck: oh, I agree with that.17:33
dwalleckBut I know, baby steps17:33
davidkranzdwalleck: I didn't mean to imply otherwise.17:34
jaypipeslet's doc it up and then transfer to the wiki...17:34
dwalleckdavidkranz: well, you said releasing to QA, it just sounded linear17:34
davidkranzdwalleck: It's just that until a certain point, they rightly don't want to get bugged by questions about things that are still really in flux.17:34
dwalleckfair deal17:34
davidkranzdwalleck: Really this means when devs think an active QA involvement would be helpful.17:35
jaypipeslet's doc it up and then transfer to the wiki...17:35
davidkranzjaypipes: OK. My concern is that in every project I have worked on, there were developers who need to be reminded of the imoprtance of early QA involvement.17:36
davidkranzSometime I was one of those developers :)17:37
rohitkTracking how many bugs Tempest tests have found in Openstack would be a good way to please(or bug) the devs17:37
jaypipesdavidkranz: sure, no disagreement from me.17:37
davidkranzrohitk: Sure. The earlier Tempest is involved, the more bugs it will find.17:38
rohitkwe could probably tag 'tempest' in such bugs or just denote the test in the bug description(guess most of us do that already)17:38
rohitkdavidkranz: true17:38
davidkranzrohitk: Yeah. I am not sure we need a special tag for that.17:39
davidkranzSo I think we need the following things:17:39
davidkranz1. Work with PTLs to identify blueprints17:40
davidkranz2. Assign people to follow17:40
davidkranz3. Add QA info to the blueprint17:40
*** anniec has quit IRC17:40
davidkranz4. Document theh process.17:40
*** littleidea_ has joined #openstack-meeting17:40
davidkranzI think we would get a long way with just that.17:40
jaypipesdavidkranz: before 3., we need to flesh out precisely what information QA should track for each blueprint17:40
jaypipesdavidkranz: which is the reason for the questions on the etherpad :)17:41
davidkranzjaypipes: Right. It would be incredibly helpful if each PTL could give a small amount of mindshare to this.17:41
dwalleckI think it would be helpful if the blueprint could describe at least the acceptance criteria for functionality that should work as part of a blueprint17:41
*** littleidea has quit IRC17:42
*** littleidea_ is now known as littleidea17:42
jaypipesdavidkranz: how about we use Quantum or Glance as a guinea pig here? both of those PTLs have expressed interest in keener coop with QA17:42
dwalleckAnd if not in the blueprint, then somewhere. I think if that's decided between dev and qa, then it makes the testing phase much less painful17:42
davidkranzjaypipes: Can you bring this up at one of the weekly meetings?17:42
jaypipeswell, vishy has too, but Nova is kinda huge... better to start smaller :)17:42
jaypipesdavidkranz: I can definitely do that (as can you!) :)17:43
davidkranzjaypipes: Agreed. Since you used to be the PTL of glance, maybe we should start with that?17:43
jaypipesdwalleck: blueprint is the perfect place to log this kind of stuff (QA deliverables)17:43
davidkranzjaypipes: Or we could do both.17:43
jaypipeswe just need to create a template of QA devliverables that QA team members can follow when assigned to a BP17:43
davidkranzjaypipes: Yes, let's fill in the etherpad and then discuss more.17:44
jaypipesdavidkranz: I think perhaps it might be easier to just pick a blueprint from Nova and then use it to create the template we use17:44
*** littleidea has quit IRC17:44
*** littleidea has joined #openstack-meeting17:44
jaypipesdavidkranz: let me choose one. gimme a couple minutes. dwalleck, rohitk, davidkranz in the meantime, please add tot hose etherpad questions17:44
rohitkjaypipes: sorry, could you share the etherpad link, bit lost on that17:45
jaypipesf course :)17:45
jaypipesdwalleck, davidkranz, rohitk: what do you guys think of this one?
*** anniec has joined #openstack-meeting17:47
jaypipesI think it's perfect. It's a) important, b) easily testable, and c) represents something that has already been a pain in the ass for the QA teasm17:47
jaypipesand Yun is a colleague of mine :)17:47
*** anniec has quit IRC17:47
davidkranzjaypipes: ++17:48
rohitkjaypipes: good candidate17:48
dwalleckyes, that is very helpful!17:48
jaypipesok, excellent.17:49
davidkranzSo we create a process around this blueprint17:49
jaypipeslet's use this as the example17:49
dwalleckPlus it should help the doc team when they want to document the functionality. win/win/win17:49
jaypipesdavidkranz: right17:49
jaypipesdwalleck: yeah, exactly, especially this particular blueprint!17:49
davidkranzWhen we are ready, we advertise it as a general mechanism and try to get more people to sign on to "own" blueprints.17:49
* dwalleck still cries tears over the admin api17:49
davidkranzThat moves us in the direction of more "QA in the open".17:50
jaypipesjust asked Yun to join us...17:50
jaypipesneed to work with developer as much as possible... that's the whole point in this.17:50
*** maoy has joined #openstack-meeting17:50
jaypipesmaoy: hi! :)17:50
maoyjaypipes: yo17:50
jaypipesmaoy: so, you've been chosen as the lucky QA winner this week.17:50
jaypipesmaoy: :)17:50
jaypipesmaoy: let me fill you in.17:50
maoyjaypipes: is the price a new ipad? jk17:51
jaypipesmaoy: no, a new etherpad :)17:51
rohitk kind of tests the yun's new state mgmt17:51
jaypipesmaoy: basically, the QA team (in whose weekly meeting you are now in) is really keen to work better and closer with developers working on blueprints17:51
jaypipesmaoy: for reference:
jaypipesmaoy: and we have chosen your blueprint (task-management) as the blueprint to use as an example for better QA coordination with development17:52
jaypipesmaoy: since you are such a kick-ass engineer, we figured you'd be cool with being a guinea pig ;)17:52
maoyjaypipes: i see. sounds good.17:53
jaypipesmaoy: The QA team wants to make sure that for each major blueprint, there are QA deliverables attached to the blueprint in question that represent tasks for QA and development to work on together.17:53
jaypipesmaoy: these tasks will mostly be:17:53
jaypipes1) Identifying any changes in API requests or responses17:53
jaypipes2) Identifying any change in call behaviour17:53
jaypipes3) Ensuring tests in Tempest fully cover the change areas17:54
jaypipesThat's basically it... but we want to be a lot more methodical about how we coordinate. thus, we're using the task-management blueprint as an example17:54
davidkranz4) Ensuring proper allocation of unit tests and tempests tests based on aarchitectural knowledge17:54
jaypipesdavidkranz: ++17:55
*** cp16net is now known as cp16net|away17:55
jaypipesmaoy: which we hope is OK, since most of the work on the blueprint is completed, but we still need to check that functional integration testing is fully covering the new and changed task states17:55
davidkranzrohitk: Would you be willing to take this as you have already dived in?17:56
jaypipesmaoy: OK, so that's the story. Nothing for you to do right now -- just letting you know you will likely see us updating the blueprint with a set of tasks for QA (and some for you) to work on17:56
rohitkdavidkranz: Sure, I can17:56
maoyjaypipes: cool.17:56
jaypipesmaoy: and hopefully, if all goes to plan, we can present the workflow at the weekly status meeting with the PTL next week.17:56
*** jakedahn is now known as jakedahn_zz17:57
jaypipesdavidkranz: the other thing I thought of is: 5) Coordinate all findings with doc team to ensure changes to documentation correspond to changes in code17:58
davidkranzjaypipes: Yes, Daryl snuck that in a few minutes ago.17:58
*** mnewby has quit IRC17:58
davidkranzThe QA person can also be a more technical interface between doc team and dev.17:59
jaypipesOK, well it's time to wrap up the meeting. I feel we got some good stuff done here today...17:59
jaypipesdavidkranz: ++17:59
rohitkjaypipes: question17:59
jaypipesrohitk: go for it.17:59
*** mnewby has joined #openstack-meeting17:59
rohitkjaypipes: tempest stable/essex hasn't changed since Apr 1317:59
rohitkare we backporting core changes into it?17:59
jaypipesrohitk: besides the patch that went in today? ;)18:00
rohitkjaypipes: yup18:00
jaypipesrohitk: feel free to backport changes to it.18:00
davidkranzrohitk: I think with all the refactoring it would be pretty painful.18:00
*** sleepsonzzz is now known as sleepsonthefloor18:00
rohitkdavidkranz: exactly, i found quite painful18:00
jaypipesalright fellas, gonna close up this meeting...18:00
rohitkjaypipes: okie!18:00
*** openstack changes topic to "OpenStack meeting channel. See for schedule and for meeting logs"18:01
openstackMeeting ended Thu Jul  5 18:00:59 2012 UTC.  Information about MeetBot at . (v 0.1.4)18:01
openstackMinutes (text):
jaypipesI think there's another meeting starting now...18:01
jaypipesalright y'all keep updating that Etherpad (as will I) and focus on making that template for use int eh blueprints18:01
*** nati_ueno has quit IRC18:02
*** donaldngo has quit IRC18:06
*** markmcclain has left #openstack-meeting18:06
*** littleidea_ has joined #openstack-meeting18:08
*** markmcclain has joined #openstack-meeting18:08
*** novas0x2a|laptop has quit IRC18:10
*** littleidea has quit IRC18:10
*** littleidea_ is now known as littleidea18:10
*** darraghb has quit IRC18:11
*** dwalleck has quit IRC18:13
*** littleidea has quit IRC18:15
*** littleidea has joined #openstack-meeting18:16
*** littleidea_ has joined #openstack-meeting18:17
*** adjohn has joined #openstack-meeting18:17
*** anniec has joined #openstack-meeting18:20
*** littleidea has quit IRC18:20
*** littleidea_ is now known as littleidea18:20
*** anniec_ has joined #openstack-meeting18:20
*** mnewby has quit IRC18:21
*** anniec has quit IRC18:21
*** anniec_ is now known as anniec18:21
*** anniec has quit IRC18:23
*** anniec has joined #openstack-meeting18:23
*** johnpostlethwait has joined #openstack-meeting18:27
*** sleepsonthefloor is now known as sleepsonzzz18:27
*** cp16net|away is now known as cp16net18:28
*** rnirmal has quit IRC18:28
*** nati_ueno has joined #openstack-meeting18:32
*** cp16net is now known as cp16net|away18:33
*** cp16net|away is now known as cp16net18:33
*** mnewby has joined #openstack-meeting18:34
*** nati_ueno has quit IRC18:37
*** rohitk has quit IRC18:40
*** dendro-afk is now known as dendrobates18:41
*** rohitk has joined #openstack-meeting18:43
*** novas0x2a|laptop has joined #openstack-meeting18:45
*** rkukura has joined #openstack-meeting18:46
*** hggdh has quit IRC18:49
*** GheRivero_ has joined #openstack-meeting18:49
*** rohitk has quit IRC18:51
*** GheRivero has quit IRC18:52
*** GheRivero_ is now known as GheRivero18:52
*** hggdh has joined #openstack-meeting18:52
*** JoseSwiftQE has left #openstack-meeting18:53
*** novas0x2a|laptop has quit IRC19:11
*** sandywalsh has quit IRC19:13
*** carlp has joined #openstack-meeting19:18
*** cp16net is now known as cp16net|away19:18
*** carlp has quit IRC19:22
*** novas0x2a|laptop has joined #openstack-meeting19:26
*** littleidea has quit IRC19:31
*** littleidea has joined #openstack-meeting19:31
*** littleidea_ has joined #openstack-meeting19:33
*** cp16net|away is now known as cp16net19:33
*** sleepsonzzz is now known as sleepsonthefloor19:33
*** jakedahn_zz is now known as jakedahn19:34
*** littleidea has quit IRC19:36
*** littleidea_ is now known as littleidea19:36
*** matwood_ has joined #openstack-meeting19:45
*** matwood has quit IRC19:48
*** matwood_ has quit IRC19:49
*** mnewby has quit IRC20:00
*** matwood has joined #openstack-meeting20:04
*** nati_ueno has joined #openstack-meeting20:04
*** littleidea has quit IRC20:09
*** littleidea has joined #openstack-meeting20:09
*** dendrobates is now known as dendro-afk20:11
*** dendro-afk is now known as dendrobates20:15
*** dprince has quit IRC20:16
*** jakedahn is now known as jakedahn_zz20:17
*** dolphm has quit IRC20:20
*** nijaba has quit IRC20:34
*** GheRivero has quit IRC20:34
*** nijaba has joined #openstack-meeting20:35
*** nijaba has quit IRC20:35
*** nijaba has joined #openstack-meeting20:35
*** carlp has joined #openstack-meeting20:36
*** sleepsonthefloor is now known as sleepsonzzz20:41
*** rnirmal has joined #openstack-meeting20:50
*** jakedahn_zz is now known as jakedahn20:51
*** mnaser has joined #openstack-meeting20:56
*** sleepsonzzz is now known as sleepsonthefloor20:59
*** mnaser has quit IRC21:00
*** maoy has quit IRC21:02
*** zigo has quit IRC21:08
*** sleepsonthefloor is now known as sleepsonzzz21:11
*** matwood has quit IRC21:16
*** nati_ueno has quit IRC21:21
*** jakedahn is now known as jakedahn_zz21:22
*** sleepsonzzz is now known as sleepsonthefloor21:22
*** matwood has joined #openstack-meeting21:29
*** cp16net is now known as cp16net|away21:30
*** littleidea_ has joined #openstack-meeting21:30
*** littleidea_ has quit IRC21:33
*** littleidea has quit IRC21:33
*** jakedahn_zz is now known as jakedahn21:33
*** ryanpetrello has quit IRC21:36
*** ywu has joined #openstack-meeting21:36
*** nati_ueno has joined #openstack-meeting21:42
*** ywu has quit IRC21:46
*** cp16net|away is now known as cp16net21:50
*** jakedahn is now known as jakedahn_zz21:52
*** sleepsonthefloor is now known as sleepsonzzz21:55
*** sacharya has quit IRC21:57
*** nati_ueno has quit IRC21:59
*** ayoung has quit IRC22:05
*** rnirmal has quit IRC22:08
*** dendrobates is now known as dendro-afk22:11
*** nati_ueno has joined #openstack-meeting22:12
*** dendro-afk is now known as dendrobates22:12
*** sleepsonzzz is now known as sleepsonthefloor22:14
*** zigo has joined #openstack-meeting22:14
*** mdomsch has quit IRC22:15
*** dachary has quit IRC22:23
*** dtroyer is now known as dtroyer_zzz22:27
*** jakedahn_zz is now known as jakedahn22:29
*** anniec has quit IRC22:34
*** mnewby has joined #openstack-meeting22:35
*** sandywalsh has joined #openstack-meeting22:39
*** anniec has joined #openstack-meeting22:42
*** littleidea has joined #openstack-meeting22:49
*** jaypipes has quit IRC23:01
*** lloydde has quit IRC23:04
*** lloydde has joined #openstack-meeting23:04
*** ayoung has joined #openstack-meeting23:05
*** lloydde has quit IRC23:09
*** matwood has quit IRC23:09
*** gyee has quit IRC23:10
*** markmcclain has quit IRC23:11
*** zigo has quit IRC23:13
*** zigo has joined #openstack-meeting23:14
*** matwood has joined #openstack-meeting23:23
*** anniec has quit IRC23:40
*** anderstj has quit IRC23:43
*** anniec has joined #openstack-meeting23:43
*** devananda has joined #openstack-meeting23:45
*** anniec_ has joined #openstack-meeting23:46
*** nati_ueno has quit IRC23:48
*** anniec has quit IRC23:50
*** anniec_ is now known as anniec23:50
*** sleepsonthefloor is now known as sleepsonzzz23:50
*** nati_ueno has joined #openstack-meeting23:51

Generated by 2.14.0 by Marius Gedminas - find it at!