Wednesday, 2011-10-19

*** nati2 has quit IRC00:00
*** nati2 has joined #openstack-meeting00:00
*** HowardRoark has quit IRC00:01
*** vladimir3p has quit IRC00:06
*** HowardRoark has joined #openstack-meeting00:44
*** ohnoimdead has quit IRC00:45
*** bcwaldon has joined #openstack-meeting00:52
*** jdg_ has joined #openstack-meeting00:54
*** jdg_ has quit IRC01:02
*** bencherian has joined #openstack-meeting01:03
*** bencherian_ has joined #openstack-meeting01:14
*** bencherian has quit IRC01:17
*** bencherian has joined #openstack-meeting01:20
*** bencherian_ has quit IRC01:21
*** bcwaldon has quit IRC01:33
*** kbader has joined #openstack-meeting01:33
*** kbader has quit IRC01:35
*** tsuzuki_ has joined #openstack-meeting01:39
*** kbader has joined #openstack-meeting01:41
*** kbader has quit IRC02:07
*** hisaharu has quit IRC02:19
*** novas0x2a|laptop has quit IRC02:19
*** nati2 has quit IRC02:19
*** nati2 has joined #openstack-meeting02:20
*** novas0x2a|laptop has joined #openstack-meeting02:21
*** nati2 has quit IRC02:22
*** jdg_ has joined #openstack-meeting02:41
*** novas0x2a|laptop has quit IRC02:41
*** novas0x2a|laptop has joined #openstack-meeting02:45
*** medberry is now known as med_out02:55
*** kbader has joined #openstack-meeting03:11
*** jdg_ has quit IRC03:12
*** HowardRoark has quit IRC03:50
*** nati2 has joined #openstack-meeting03:51
*** nati2 has quit IRC03:59
*** nati2 has joined #openstack-meeting04:08
*** nati2 has quit IRC04:09
*** nati2 has joined #openstack-meeting04:37
*** kbader has quit IRC04:55
*** adjohn has joined #openstack-meeting04:59
*** novas0x2a|laptop has quit IRC05:17
*** nati2 has quit IRC05:22
*** jakedahn has quit IRC05:27
*** sandywalsh has quit IRC05:39
*** sandywalsh has joined #openstack-meeting05:52
*** danwent has joined #openstack-meeting05:54
*** bencherian has quit IRC05:59
*** Kiall has quit IRC06:04
*** danwent has left #openstack-meeting06:06
*** jakedahn has joined #openstack-meeting06:21
*** bencherian has joined #openstack-meeting06:27
*** Kiall has joined #openstack-meeting06:45
*** adjohn has quit IRC07:49
*** shang has quit IRC08:29
*** shang has joined #openstack-meeting08:30
*** tsuzuki_ has quit IRC11:46
*** dolphm has joined #openstack-meeting12:21
*** gaitan has joined #openstack-meeting12:27
*** darraghb has joined #openstack-meeting12:32
*** bencherian has quit IRC12:40
*** dolphm has quit IRC12:48
*** dolphm has joined #openstack-meeting13:10
*** markvoelker has joined #openstack-meeting13:11
*** dendrobates is now known as dendro-afk13:33
*** bcwaldon has joined #openstack-meeting13:37
*** rohitk has joined #openstack-meeting13:41
*** dprince has joined #openstack-meeting13:50
*** dendro-afk is now known as dendrobates13:51
*** gaitan has quit IRC14:06
*** dolphm has quit IRC14:09
*** dolphm has joined #openstack-meeting14:20
*** jakedahn has quit IRC14:24
*** dolphm has quit IRC14:27
*** mdomsch has joined #openstack-meeting14:28
*** dendrobates is now known as dendro-afk14:29
*** dolphm has joined #openstack-meeting14:30
*** hggdh has quit IRC14:33
*** deshantm_laptop has joined #openstack-meeting14:37
*** hggdh has joined #openstack-meeting14:40
*** bcwaldon has left #openstack-meeting14:40
*** hggdh has quit IRC14:54
*** reed has joined #openstack-meeting14:55
*** clayg has left #openstack-meeting14:55
*** hggdh has joined #openstack-meeting14:57
*** dolphm has quit IRC14:58
*** dragondm has joined #openstack-meeting15:00
*** dolphm has joined #openstack-meeting15:01
*** jakedahn has joined #openstack-meeting15:07
*** vladimir3p has joined #openstack-meeting15:09
*** nati2 has joined #openstack-meeting15:09
*** danwent has joined #openstack-meeting15:09
*** HowardRoark has joined #openstack-meeting15:13
*** bencherian has joined #openstack-meeting15:16
*** nati2 has quit IRC15:20
*** nati2 has joined #openstack-meeting15:21
*** wwkeyboard has joined #openstack-meeting15:26
*** mtaylor has quit IRC15:27
*** mtaylor has joined #openstack-meeting15:28
*** GavinB has joined #openstack-meeting15:56
*** Ravikumar_hp has joined #openstack-meeting15:57
*** bencherian has quit IRC15:58
jaypipesQA meeting starting in 1 minutes...16:00
*** patelna has joined #openstack-meeting16:00
jaypipesnati2, patelna, rohitk: please round up your cohorts :)16:00
patelnasure...16:00
nati2Hi Jay!16:00
*** donaldngo_hp has joined #openstack-meeting16:00
GavinBGavin is here so +1 for Nayna :)16:01
rohitkHello16:01
jaypipesGavinB: :)16:01
Ravikumar_hpRavi for Nayna16:01
jaypipesrohitk: evening!16:01
patelnaNayna is here...hey16:01
donaldngo_hpHello Donald is here I am also on Nayna's team16:02
jaypipeswestmaas, wwkeyboard: meeting time.16:02
patelnaRohit - I am going to be in India16:02
rohitkevening/afternoon, aah16:02
patelnawe should meet F2F16:02
rohitkthat's great16:02
rohitkabsolutely16:02
rohitkwe did at the ODS, if you remember :-)16:02
* jaypipes looks around for gigi and daryll...16:02
Ravikumar_hpRohit in Pune right?16:02
rohitkthats right16:02
patelnayes...but now work on execution plans16:02
rohitksure16:03
nati2Hi Donald16:03
jaypipesOK, let's get started then...16:03
jaypipes#startmeeting16:03
openstackMeeting started Wed Oct 19 16:03:38 2011 UTC.  The chair is jaypipes. Information about MeetBot at http://wiki.debian.org/MeetBot.16:03
patelnayes16:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.16:03
jaypipes#topic Action items from last week...16:03
*** openstack changes topic to "Action items from last week..."16:03
*** HowardRo_ has joined #openstack-meeting16:03
jaypipesone sec, grabbing last week's link..16:04
jaypipeshttp://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-10-12-16.05.log.txt16:04
donaldngo_hphello16:04
jaypipeshttp://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-10-12-16.05.txt16:04
*** HowardRoark has quit IRC16:04
jaypipesjeblair: ping16:05
jaypipesOK, let me go over all the stuff I failed to get done this past week... :(16:05
rohitkis anyone from Grid Dynamics here?16:05
*** mahmoh has joined #openstack-meeting16:05
rohitkok16:05
jaypipesjaypipes to grab all other test suites code and put into openstack-integrated-tests project, each in its own subdirectory.16:06
jaypipesunfortunately, I did not get around to this. :(16:06
patelnaany ETA?16:06
jaypipesI should have time to do this today, however, as past week been working on glance stuff.16:06
*** dwalleck_ has joined #openstack-meeting16:06
jaypipespatelna: today/EOB tomorrow at latest.16:06
nati2OK, rohitk: can you do that?16:06
patelnaok...thanks16:06
jaypipesdwalleck_: afternoon :)16:06
*** ranjang has joined #openstack-meeting16:06
dwalleck_Sorry I'm late, couldn't get connected for some reason16:07
rohitknati2: ok16:07
jaypipesjaypipes to get this meeting listed on the openstack meetings ics calendar16:07
dwalleck_Gigi is shoulder surfing me also16:07
patelnaah...nice16:07
rohitkjaypipes: Is this the structure? http://paste.openstack.org/show/2689/16:07
jaypipes^^ also failed to get that done... will do right after this meeting with ttx16:07
uvirtbotjaypipes: Error: "^" is not a valid command.16:07
jaypipesrohitk: yep16:07
jaypipesdwalleck_: cool, no worries16:08
rohitkjaypipes: cool16:08
nati2jaypipes: ok, please assign this action for rohit16:08
patelnado anyone know if we have tests for Swift16:08
wwkeyboardjaypipes: I added a new test runner that should simplify moving to that new directory structure16:08
jaypipes#action jaypipes to create blueprint for integration test merging and assign to rohitk16:08
*** Badri has joined #openstack-meeting16:08
jaypipespatelna: integration tests or .. ?16:09
donaldngo_hphttps://github.com/openstack/openstack-integration-tests (Kong) is this the framework that we are agreeing to utilize and develop moving forward?16:09
nati2thanks16:09
*** kbader1 has joined #openstack-meeting16:09
patelnayes...swift integration tests16:09
jaypipesdonaldngo_hp: no. kong is one of many... we are integration about 6 of them.16:09
jaypipespatelna: not that I know of, no.16:09
Ravikumar_hpalso swift functional tests16:09
jaypipesRavikumar_hp: depends what you mean by functional tests :)16:10
dwalleck_jaypipes: Have we decided what the structure of the tests/test framework is going to be going forward? This is something I'm really itching to help with16:10
dwalleck_I have a lot of spare time and nothing to do but design, develop and test :-)16:10
jaypipesdwalleck_: wwkeyboard and westmaas are working on that. I would advise getting involved in the code reviews for openstack-integration-tests. :)16:10
*** dendro-afk is now known as dendrobates16:10
jaypipesdwalleck_: westmaas is leading the effort to complete a best practice test runner. I would definitely hope you collaborate with wwkeyboard (Aaron Lee) and Gabe on it!16:11
dwalleck_jaypipes: Sure, of course16:11
*** danwent has left #openstack-meeting16:11
patelnalJaypipes: how can we ensure we get all the tests consolidated for core products - swift, nova & glance16:11
jaypipesI believe jeblair sent out an email about membership for integration tests....16:12
jaypipespatelna: integration tests are going into the openstack-integration-tests project. Those tests will stress the integration points between the core projects.16:12
jaypipespatelna: and each project has zero, some, or a lot of its own functional tests.16:12
jaypipespatelna: the thing that is missing is really integration tests against a cluster running a bunch of openstack projects... and that is what the openstack-integration-tests project is attempting to solve.16:13
patelnatoday, we need to talk about this...16:13
rohitkjaypipes: did jeblair create this group on LP/gerrit?16:13
jaypipespatelna: please, let's. what specific questions do you have?16:13
dwalleck_jaypipes: By functional tests, do you mean black-box style or white box style? I wasn't aware there was a seperate black box test suite for Nova or other projects16:13
donaldngo_hpjaypipes: right now i see only Kong in the integration test project. just be clear we are going to add more frameworks into this repo?16:13
nati2openstack-integration-tests project++16:13
jaypipesrohitk: yes16:13
jaypipesdwalleck_: blackbox16:14
patelnaconsolidate all the tests that are still not contributed back to the openstack16:14
zykes-what meeting is going now ?16:14
patelnablackbox tests for core products16:14
jaypipesdwalleck_: and Glance has black box tests. /glance/tests/functional/16:14
rohitkzykes: openstack-qa16:14
patelnahow about swift?16:14
jaypipespatelna: one sec...16:15
dwalleck_donaldngo_hp: I would hope as opposed to adding more frameworks, we'd be consolidating them to a single unified platform16:15
rohitkdwalleck_: +116:15
GavinBHas anyone defined what we would like to see in a suitable framework ?16:15
GavinBI have some definite opinions :)16:16
donaldngo_hpdwalleck: i agree a single framework. but each of these "frameworks" currently develop differ in their approach16:16
nati2dwalleck_:  Even if so we should share our effort at first :)16:16
rohitkGavinB: I too was of that opinion that we need to have a list (checklist) of features needed in that framework16:16
rohitkor pull in the best from the rest16:16
jaypipespatelna: Swift has "functional tests" (tests/functional/) but AFAICT, they are not black box. In other words, they don't spin up Swift servers and test the public API. They use internal interfaces.16:16
dwalleck_gavinB: As do I. I've passed around a few things internally, as well as loosely discussed it on the list16:16
patelnaGot it...16:17
jaypipesGavinB: we don't have a lack of frameworks :) We have too many of them... we just need to settle on one or combine the best of breed and focus on writing tests, not test frameworks :)16:17
rohitkdwalleck_, GavinB: Test data generation and data sources are high on my list16:17
patelnathis needs to be actioned then...adding more swift tests on a runnign server?  Gigi - can u take this?16:18
nati2rohitk: Would you write blueprint about Test data generation and data sources?16:18
patelnaNati2 +116:18
GavinBjaypipes: Totally agree - but that argues for a flexible platform that can cope with tests in many forms ... so pretty high level.16:18
*** AntoniHP has joined #openstack-meeting16:18
donaldngo_hpI think a good framework to start with is Kong it tests the core REST APIs16:18
dwalleck_rohitk: And for me, the test code structure and design is what I'm most worried about. I think that's going to be the key to the scalability and strength of the suite going forward16:18
jaypipesGavinB: sure, though I think the first step is just to get *something* going...16:18
Ravikumar_hpalso test results in blueprint16:18
rohitknati2: Sure, will need to discuss the specifics and scope16:19
jaypipeswe can get into analysis paralysis trying to create the Uber-Framework and actually not get any test writing done :)16:19
Ravikumar_hp1) Nose 2) KONG to standarize api & functional /integarion16:19
dwalleck_Kong doesn't really provide a framework. It's just directly using http requests16:19
patelnaRavikumar_hp +116:20
GavinBjaypipes: Agree there also. We should select something and get moving - but recognise it will not solve all our needs16:20
jaypipesI actually don't care what it is :) I just want it done.16:20
dwalleck_When I'm saying framework, I mean more along the lines of Stacktester or Zodiac did in terms of design16:20
jaypipeswwkeyboard: is westmaas around?16:20
nati2Before test code we need specs and test scenario16:20
GavinBdwakkeck_ +116:20
patelnaagree with jaypipes...we need tests that we can run16:20
GavinBdwallek_ +1 (sorry !)16:20
nati2We didn't have API specs which we can use yet16:20
wwkeyboardjaypipes: He is in a different office.16:20
jaypipeswwkeyboard: oh, sorry...16:20
dwalleck_nati2: I think we have docs for the API 1.1 spec16:21
nati2Yes, I checked it in this week16:21
rohitkjaypipes: soren's branch is fine enough to begin contributing to, however the finer issues of 'no novaclient', etc remain16:21
nati2But it is not cover all features in the code16:21
westmaashey, sorry, bit late16:21
rohitkhi westmaas16:21
jaypipesrohitk: well that's why we're bringing in the other test suites... some of them like backfire use the novaclient. others use httplib2 calls.16:22
nati2Many parameters are not documented and we only have examples16:22
patelnanati2 - should we do traceability matrix on that API spec to ensure we have tests?16:22
nati2patelna++16:22
nati2spec and traceability matrix on that API spec16:22
jaypipesOK everyone.... hold up a minute... this is getting a bit freeform... let me try to give some structure to this meeting.16:22
jaypipesEVERYBODY STOP. :)16:22
patelnathat's the 1st step16:22
nati2jaypipes++16:22
jaypipesLet us get one thing done at a time.16:22
jaypipes#topic integration tests status.16:22
*** openstack changes topic to "integration tests status."16:22
jaypipeswestmaas: Gabe, would you care to provide a quick status update?16:23
westmaassure, daryl aaron and I met just after the last meeting, and we talked through a few options, and finally settled on a lightweight runner16:23
notmynamejaypipes: patelna: whoever: swift's functional tests do create instances of the servers and test public APIs16:24
westmaasthe goal of the runner is to give a unified entry point to run all suites in the project as of now16:24
westmaaswith the expectation that those suites will be folded into a common suite as quickly as possible16:24
westmaasits really just a bash script that runs another script in each directory, really really straightforward16:24
jaypipesnotmyname: the functional tests use internal objects (liek swift.Account). They are not black box -- i.e. they don't do straight HTTP calls.16:25
westmaasnext step is a two step process I think.  1) Identifying what we are testing right now16:26
westmaas2) Select how we should test moving forward16:26
Ravikumar_hpwestmass: 3) identify the test gaps. missing tests16:26
jaypipeswestmaas: OK, thx for the update. Question: would you prefer that rohitk simply copy/paste the other suites into directories, or copy in the test cases and in the process, convert them to use the new test runner/client?16:26
westmaassounds good16:26
rohitkwestmaas: 'all suites in the project' means that the script would identify and execute the test suites pulled in from various frameworks?16:26
patelnawestmass; Ravikumar_hp +116:27
rohitkjaypipes: that's what I implied16:27
rohitkthnx16:27
westmaasjust bringing them in is fine for a first step, since we haven't selected how to move forward16:27
westmaasrohitk: they just look in each directory for a certain script name, nothing more16:27
wwkeyboardwestmaas: ++16:27
nati2westmaas: ++ nice start16:28
jaypipeswestmaas: k. is there a wiki or etherpad you're using with wwkeyboard and dwalleck_ to track thoughts on how you'd like to move forward?16:28
rohitkoh, k16:28
wwkeyboardJust get them in one place, and running will be a start16:28
patelnashould we organize dir structure and consolidate in one place16:28
westmaaspatelna: yes soon16:28
westmaasjaypipes: no, not yet16:28
patelnais that waht Rohit will do?16:28
rohitkpatelna: i'll work on that16:29
westmaasjaypipes: we can do that, but honestly, I think the most important thing is an inventory of what we have16:29
jaypipeswestmaas: no probs, and agreed.16:29
patelnaagree - we need inventory16:29
westmaasjaypipes: in terms of both what is covered and how its covered16:29
nati2westmaas++  for inventory16:29
jaypipes++16:29
rohitkwestmaas: getting the various suites together is alright, but i doubt that they would all run from the unified script16:29
westmaasrohitk: if you bring them in, can you also add to this page: http://wiki.openstack.org/openstack-integration-test-suites?highlight=%28integration%29%7C%28tests%2916:29
donaldngo_hpeach test framework has configuration that needs be done editing config files creating objects for swift and images for nova. How will we deal with that?16:30
rohitksince they were designed for different runners - nose, dtest, etc16:30
donaldngo_hpits not a plug and run type of thing16:30
rohitkdonaldngo_hp: exactly16:30
jaypipesdonaldngo_hp: the config files will depend on what system the tests are run against.16:30
westmaasrohitk, donaldngo_hp: right now that's all being kept inside each test suites directory16:30
wwkeyboarddonaldngo_hp: For now they well need to be configured in their own dirs16:30
nati2rohitk: we should discuss it with reading test code.16:30
jaypipesdonaldngo_hp: would be good to have example configs, but more than that I'm not sure will be useful.16:30
AntoniHPdonaldngo_hp: that is not as difficult, tests we run now try to detect environment they are in and the proceed accordingly16:31
wwkeyboardI think it will be easier/more prudent to move the missing functionality into the One True Framework than try and configure the rest automatically.16:31
patelnacan we action this to westmass, Rohit and donald?16:31
westmaasanother piece of inventory is what each suite cares about in terms of configuration - my guess is it is all very common with different names, all of which will inform the One True suite16:31
dwalleck_westmaas: I would think as we consolidate tests, we should probably be able to consoldate configurations16:33
jaypipesOK, so AntoniHP, dwalleck_, rohitk: please all of you go to your Gerrit settings, click Watched Projects, and make sure you have openstack/openstack-integration-tests under your project list, and that you check all the checkboxes for notification!16:33
jaypipesdonaldngo_hp: you too :)16:33
rohitkjaypipes: gotcha16:33
donaldngo_hproger that16:33
dwalleck_will do16:34
nati2jaypipes: please include me :)16:34
AntoniHPok16:34
jaypipesnati2: it's up to you! you have to edit your settings in Gerrit yourself ;)16:34
jaypipeswestmaas, all: OK, are there other issues you'd like to talk about re: integration tests?16:34
nati2gotcha! I misunderstood :)16:34
jaypipesnp16:35
rohitkjaypipes: yes!16:35
patelnayes...approach to add more coverage?16:35
jaypipespatelna: you mean approach to track the "inventory of tests" that cover project functionality?16:35
rohitknot sure if many of us have  really looked at lettuce, westmaas, have you?16:35
*** dolphm has quit IRC16:36
patelnajaypipes - yes + add gaps16:36
westmaaspatelna: I think we need to triage getting things running and a generic approach, I'm not sure this meeting is the right forum to plan beyond that16:36
westmaaspatelna: at least until we have those in place16:36
westmaaspatelna: although I 100% agree its super important16:36
jaypipespatelna: I think it would be useful to log bugs in the openstack-qa project on launchpad for those gaps, similar to how nati-san's team is doing for the unit test coverage16:36
dwalleck_rohtik: I think moving to BDD would be a huge shift, that's something we'd really have to look into16:37
patelnaagree16:37
jaypipespatelna: agree on BDD or bugs in LP? ;)16:37
rohitkdwalleck_: i thought so too, it might be kind of late for that16:37
westmaasrohitk: I have not looked16:37
Ravikumar_hpjaypipes : or blueprints to add/fill test gaps?16:37
patelnajaypipes bugs on LP16:37
*** dolphm has joined #openstack-meeting16:37
jaypipesRavikumar_hp: I think bugs would be better... blueprints are more for large things... of course, we could track "Find Gaps in Swift <-> Glance Integration" in a blueprint and then have multiple bugs for the individual gaps identified, etc...16:38
jaypipesbut I think bug reports is a good first start.16:38
jaypipespatelna: OK, well we made you an admin on the openstack-qa project, so you can add, assign, and target bugs in that project. I'll work with you offline to set some up to get you familiar with the proces.16:39
patelnaok Jaypipes16:39
jaypipesalright, shall we move on to a status report from nati2 on unit testing progress?16:39
nati2topic "integration tests status." is finised?16:39
dwalleck_But to some degree we're going to need to make some shift. We need to have one agreed-upon way of of developing these16:39
dwalleck_okay, done :016:40
dwalleck_:)16:40
jaypipes:), ok...16:40
wwkeyboardthat topic will never be done16:40
jaypipes#topic status report from nati2 on unit tests16:40
*** openstack changes topic to "status report from nati2 on unit tests"16:40
wwkeyboard:)16:40
jaypipesnati2: you're up!16:40
nati2ah, my irc stopped16:40
nati2I added details of blueprint https://blueprints.launchpad.net/openstack-qa/+spec/nova-manager-api-policy16:41
nati2https://blueprints.launchpad.net/openstack-qa/+spec/nova-input-value-validation-policy16:41
nati2For input validation, we have a Idea.16:41
nati2We are developing struts like input validation framework for nova16:41
nati2We'll share it16:41
jaypipesnati2: could you elaborate a bit more on that?16:42
nati2for blueprint?16:42
nati2OK, I'll add more detail for each blueprints16:43
jaypipesnati2: :) sorry, I meant could you explain to the group here a bit more about what those blueprints are about.16:43
nati2I see16:44
nati2For QA, our workflow is like this.  Make a spec clear, analyze gap between specs and code , write test code and fix16:45
nati2But for coding level, we have no resource to make the spec clear. So we set policies.16:45
nati2Nova-manager-api-policy is policy for the use of manger methods16:45
nati2See this bug https://bugs.launchpad.net/openstack-qa/+bug/872445 (it is already solved for essex)16:46
uvirtbotLaunchpad bug 872445 in nova "nova.compute.manager calls methods in nova.volume.manager directly" [Undecided,Fix committed]16:46
nati2In this case, the compute manager directly calls volume manager without using it's API.16:46
nati2These codings should be avoided16:47
nati2Is this make sence?16:47
jaypipesnati2: yes, much better, thx.16:47
jaypipesnati2: question, though: Why is the Nova bug there marked Fix Committed?16:47
nati2OK next nova-input-value-validation-policy16:47
nati2Because it is fixed for essex trunk16:48
nati2not for diablo stable16:48
patelnaso u are requestign for backport into stable?16:48
nati2Ah, it is problem. We are lacking workflow for bug backport16:49
nati2ttx manages bug for essex16:50
patelna@Jaypipes?  Do we have this process - any idea...backport from esses to stable branch?16:50
patelnasorry typo esses = essex16:51
jaypipesnati2: no, I'm wondering why it is marked Fix Committed, but there is no link or reference to the commit that fixed it...16:52
nati2jaypipes: ah, ttx marked it as fix commied without link16:52
jaypipespatelna: the "process" is to propose the patch for merging into the stable-diablo branch. For these types of things, if the patch just adds test cases, I'm not sure it's a high priority backport, but if the patch fixes a known high priority bug, it should definitely be proposed for merging into stable-diablo16:53
jaypipesnati2: OK, no worries. I'm just curious to see if you and your team have started using Gerrit16:53
jaypipesnati2: I've been concerned to see a number of bazaar branches put up on Launchpad instead of git branches to Gerrit...16:54
patelnaThanks Jaypipes16:54
jaypipespatelna: no worries. probably something worth putting here: http://wiki.openstack.org/StableBranch16:54
nati2Yes we will going to use git and gerrit. Thanks Jay. I shared how to use it for my japan team16:54
jaypipesnati2: ok, excellent. pls do let me or jeblair know if anyone needs assistance with understanding git/gerrit.16:55
jaypipesnati2: final question for you on the unit testing bugs...16:55
jaypipesnati2: Are you going to be updating the status of the openstack-qa bugs? (hint, hint) :)16:55
nati2Ah, I should do it. Thanks16:56
jaypipesnati2: right now, they are mostly New status and unassigned...16:56
*** ohnoimdead has joined #openstack-meeting16:56
jaypipesnati2: OK, I'll bug you about that later :)16:56
jaypipesalright, any further questions for nati-san on unit testing?16:56
nati2Yes! It my action item. There are large queue on me to translate japanese bug to english ;(16:56
jaypipeshehe, indeed16:56
*** hisaharu has joined #openstack-meeting16:57
rohitknati2: I'll be there to help you16:57
jaypipesOK, all, we have 3 minutes left...16:57
jaypipes#topic Open Discussion16:57
*** openstack changes topic to "Open Discussion"16:57
jaypipesanybody have anything to bring up? any concerns?16:57
nati2Yes I have two16:58
Ravikumar_hpjaypipes: is there any docs on best practices for bugs/blueprint and git/gerrit16:58
jaypipesRavikumar_hp: git/gerrit here: http://wiki.openstack.org/GerritWorkflow and http://wiki.openstack.org/GerritJenkinsGithub16:59
nati2ah, we should write it. jaypipes: do you have time today? How about to create some screencast with me?16:59
Ravikumar_hpjaypipes: thanks16:59
jaypipesRavikumar_hp: bugs here: http://wiki.openstack.org/BugTriage16:59
jaypipesRavikumar_hp: and I'll put something together about blueprints and bugs for the qa team.16:59
*** hisaharu has quit IRC16:59
nati2It was a little bit difficult to understand http://wiki.openstack.org/GerritWorkflow.. But may be screencast is too much16:59
jaypipesnati2: not today, but tomorrow, yes.17:00
rohitkwestmaas: any pointers on the location of the entry point script?17:00
jaypipesnati2: also, jeblair may be able to come to the office to help with that.17:00
nati2jaypipes: Thanks! I'll access to the  jeblair k17:00
westmaasrohitk: just merged today17:00
nati2I added a blueprint to API specs17:01
nati2https://blueprints.launchpad.net/openstack-qa/+spec/api-specs17:01
nati2and17:01
jaypipesOK all, I have to run... I will send a short summary to the ML about our meeting. Goodbye fo rnow!17:01
jaypipes#endmeeting17:01
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"17:01
openstackMeeting ended Wed Oct 19 17:01:12 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-10-19-16.03.html17:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-10-19-16.03.txt17:01
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-10-19-16.03.log.html17:01
nati2Integration test scenario https://blueprints.launchpad.net/openstack-qa/+spec/integration-test-scenario17:01
westmaasrohitk: to run just do ./run_tests.sh kong17:01
westmaas(for example)17:01
nati2Bye Jay!17:01
*** HowardRo_ has quit IRC17:01
westmaaspatches accepted if you want to improve it - its really simple right now, not intended to be fancy!17:01
patelnaBye Jay17:01
rohitkwestmaas: ok, ill check it out, i'd have quite a few questions on the unified runner, hope to get some answers on the ML!17:02
*** AntoniHP has left #openstack-meeting17:02
rohitkjaypipes: thnx and cya!17:02
westmaasrohitk: sorry sir swamped by emails this week :)17:02
*** Tushar has joined #openstack-meeting17:02
*** GavinB has quit IRC17:02
rohitkwestmaas: no problemo, as you get the time17:02
*** Badri has quit IRC17:02
nati2OK i'll mail you about my new blueprints17:03
nati2Bye!17:03
donaldngo_hpnice meeting you guys and look forward to working with you in the future17:04
*** rohitk has quit IRC17:04
*** Tushar has quit IRC17:04
*** rohitk has joined #openstack-meeting17:04
*** nati2 has quit IRC17:08
*** HowardRoark has joined #openstack-meeting17:09
*** ranjang has quit IRC17:11
*** cmagina_ has quit IRC17:13
*** cmagina has joined #openstack-meeting17:13
*** darraghb has quit IRC17:16
*** dolphm has quit IRC17:22
*** rohitk has quit IRC17:36
*** dolphm has joined #openstack-meeting17:36
*** novas0x2a|laptop has joined #openstack-meeting17:37
*** rohitk has joined #openstack-meeting17:47
*** dwalleck_ has quit IRC17:54
*** donaldngo_hp has quit IRC17:59
*** donaldngo_hp has joined #openstack-meeting18:00
*** bencherian has joined #openstack-meeting18:00
*** bencherian has quit IRC18:01
*** rohitk has quit IRC18:05
*** bencherian has joined #openstack-meeting18:06
*** bencherian has quit IRC18:17
*** bencherian has joined #openstack-meeting18:25
*** med_out is now known as med18:26
*** med is now known as medberry18:26
*** dendrobates is now known as dendro-afk18:30
*** patelna has left #openstack-meeting18:34
*** danwent has joined #openstack-meeting18:38
*** donaldngo_hp has quit IRC18:39
*** bencherian has quit IRC18:42
*** jaypipes has quit IRC18:47
*** dendro-afk is now known as dendrobates18:48
*** bencherian has joined #openstack-meeting18:55
*** danwent has left #openstack-meeting18:56
*** rnirmal has joined #openstack-meeting19:05
*** jaypipes has joined #openstack-meeting19:08
*** michaelkre has joined #openstack-meeting19:16
*** dwalleck has joined #openstack-meeting19:21
*** dprince has quit IRC19:49
*** novas0x2a|laptop has quit IRC19:52
*** novas0x2a|laptop has joined #openstack-meeting19:52
*** novas0x2a|laptop has quit IRC19:57
*** novas0x2a|laptop has joined #openstack-meeting19:58
*** novas0x2a|laptop has quit IRC19:58
*** novas0x2a|laptop has joined #openstack-meeting19:59
*** novas0x2a|laptop has quit IRC19:59
*** novas0x2a|laptop has joined #openstack-meeting19:59
*** dwalleck has quit IRC20:31
*** deshantm_laptop has quit IRC20:40
*** jakedahn has quit IRC20:56
*** debo_os_ has joined #openstack-meeting20:56
*** dolphm has quit IRC20:57
debo_os_Time for the Donabe meeting21:00
*** debo_os_ is now known as debo_os21:00
dendrobateso/21:01
dendrobateswe'll see if anyone else remembers.  We didn't send out a reminder21:02
debo_os#startmeeting21:02
openstackMeeting started Wed Oct 19 21:02:34 2011 UTC.  The chair is debo_os. Information about MeetBot at http://wiki.debian.org/MeetBot.21:02
* markvoelker lurks because he has to leave in a few minutes 21:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.21:02
debo_os#topic Donabe21:02
*** openstack changes topic to "Donabe"21:02
*** danwent has joined #openstack-meeting21:03
dendrobateshi danwent21:04
debo_oshi Dan!21:04
danwenthey21:04
markvoelkero/21:04
debo_oshi Mark21:04
mtaylordanwent: I'm supposed to be working with you on something, aren't I?21:04
debo_os#info Agenda21:04
danwentmtaylor:  maybe packaging or jenkins releated?  both are things we're working to take care of for quantum21:05
debo_osAPI design issues•Database layer•Transactional semantics – should we post the whole topology in 1 shot in a xml chunk or in pieces•Model driven …. Define primitives for 1) compute 2) network 3) storage•Plugins for the above primitives. Declarative languages•Pluggable module•We choose 1 default one21:05
debo_ossorry I cut pasted the agenda too soon21:05
debo_osare we the 4 of us here?21:07
dendrobateslooks like it21:07
debo_os:)21:07
debo_osmaybe we give 2 more mins and then get started?21:08
glenc\o21:08
dendrobatesdebo_os: sure21:08
debo_osdebo.sleep(2m)21:08
zykes-question, what is donabe in a easy description? a overlaying service for the netstack ?21:08
debo_oswell21:09
debo_osdonabe is an abstraction of app containers that leverages services like nova and quantum21:09
dendrobateszykes-: or an abstraction for groups of cloud resources21:09
debo_osthat too! Thanks Dan21:10
zykes-hmm, i wonder what the usage of it is21:10
*** markvoelker has quit IRC21:10
debo_osthere are several usage models21:11
glencDoes Donabe only address the cloud resources themselves, or does it also work with applications within them? (i.e., can it configure an app in a virtual server)21:11
debo_osone possible way is http://www.slideshare.net/ddutta1/donabe-models-openstack-essex-summit21:11
debo_osyes Donabe is geared towards describing app behavior too21:12
glencFYI, http://panelpicker.sxsw.com/ideas/view/1049721:12
dendrobatesglenc: we are mostly concerned with the abstraction and the ability to package that abstraction so it can be deployed21:12
dendrobatesglenc: that is a very similar concept21:13
glencGood - just making sure I'm on the right track21:13
glencwhich is why I wanted to be here21:13
dendrobatesglenc: I have even used oracle financials as an example21:14
glencgreat minds think alike21:14
dendrobates:)21:14
dendrobatesdebo_os: ok, go21:14
zykes-dendrobates: werent you with rackspace earlier on ?21:15
debo_osgood guess :)21:15
dendrobateszykes-: yes21:15
debo_os#topic agenda21:15
*** openstack changes topic to "agenda"21:15
debo_os1. A little more about whats Donabe .... in case we need it21:16
debo_os2. API and data model21:16
debo_os3. Declarative languages21:16
debo_osanything more?21:16
debo_osRick?21:16
debo_osDan?21:16
debo_osanyone?21:16
dendrobatesgood for me21:17
*** wwkeyboard has left #openstack-meeting21:17
debo_osShall we skip 1.21:17
danwentsound good for me… i'm mostly just listening in :)21:17
debo_os#topic API21:17
*** openstack changes topic to "API"21:17
debo_osDuring the summit, we agreed upon 1) recursive/nested containers21:18
debo_os2) simple use case -> scalableweb<-->scalable db tiers21:18
debo_os3) for essex leverage quantum and nova to stitch the containers21:18
debo_os4) use a declarative language for describing configs21:19
debo_osfor recursive containers, we need a data model21:20
debo_osthe simple API takes in a graph (with nodes = containers, edges = container pairs that communicate)21:21
debo_osthe data model leads to semi structured data21:21
debo_oshence we need a data model that will be suitable21:21
debo_osany comments on that>21:21
debo_os?21:21
glenccould you also use a bill of materials type model?21:21
debo_ospossible approaches could be xml dbs or neo4j21:21
debo_osglenc: in bom like models we would still need the relationships or edges21:22
debo_osso this graph structure is like a BOM21:23
glencit is, but it doesn't have to be recursive (I'm just thinking out loud here)21:23
debo_osassume its non recursive for a moment ...  its a good debate to have ....21:24
debo_osyou still need a semi structured way of representing a graph21:24
debo_osthats why people have been looking at graph databases21:24
debo_osbut if there is a relational way of looking at it that covers the use cases, it might be good21:25
debo_osin that case our higher layer graph model would then need to be mapped21:25
debo_osany other suggestions21:26
debo_osplease send more suggestions to the list21:27
debo_osthe next thing is transactional semantics21:27
debo_osfor defining a higher layer container, you need to group smaller containers21:27
debo_osnow we could implement the API in 2 ways21:28
debo_os1st define smaller container types ... then build higher ones21:28
debo_osbut an alt way is to define it in 1 shot ... do a POST with a blob describing the graph21:28
debo_osactually OVS has an app prpoosal with a graph structure too :)21:29
debo_osthoughts?21:29
*** jakedahn has joined #openstack-meeting21:29
danwentOVS != open vswitch i assume?21:29
debo_ossorry OVF21:29
danwent:)21:29
dendrobatesI'm concerned about posing a big blob21:29
dendrobatesis that your preference?21:30
debo_osI am ok as long as we note that there will be transactional issues21:30
*** jakedahn has quit IRC21:30
debo_oswe will need to have a fix for that21:30
*** jakedahn has joined #openstack-meeting21:30
debo_oselse we need a blob ....21:31
debo_osI prefer the blob to keep the implementation is simpler21:31
dendrobatescan you explain the transactional issues in detail21:31
debo_oswell say you have a big container request that has 3 smaller containers21:31
debo_osyou need to create the smaller container requests 1st21:32
debo_osthen the bigger one21:32
debo_osso you will have 4 requests21:32
debo_osideally you want this is as a part of a single transaction21:32
glencyes, with orchestration and rollback on error, right?21:32
debo_osyes21:33
glencis the blob where it would contain the declarative language?21:33
debo_osblob would have the graph structure ... and a reference to the manifest21:34
debo_osbecause the manifest could be common for several containers21:34
glencI tend to read blob as a BINARY large object, which makes me nervous -21:35
glencI would hope it would be editable with standard tools21:35
debo_ossorry ... I should have clarified21:35
debo_oshere a blob would mean a big xml blob21:35
debo_os:)21:35
dendrobatescan we not assume xml21:35
debo_oswe could .... I just didnt want to offend JSON people21:36
debo_oshence I am trying to use generic terms21:36
debo_os;)21:36
glencI tend to visualize it as XML (hey, I've been in IT for 20+ years) and convert mentally to json21:37
dendrobatesI would say the representation of the containers (blobs) is up for discussion21:37
glencI'm cool with it as long as it isn't really binary21:37
glencor Visual BASIC21:38
debo_os:)21:38
debo_osso these are the primary things I wanted to point out form the design point of view21:38
debo_osplease punt feedback21:39
dendrobatesawesome21:40
debo_osthe other things are slightly long temrs21:40
debo_oslike what declarative languages to use21:40
debo_osand we want the donabe engine to be at a higher layer21:41
debo_osusing model driven stuff21:41
debo_osso that we could have plugins for say things like declarative behavior engines etc21:41
debo_osbut all that might be relevant for later discussions21:42
debo_osAs DanW keeps saying, we need a simple demos21:42
danwent:)21:42
debo_osthats all from me21:42
dendrobatesshould we take one part and delve into it next meeting?21:43
debo_osI think once we have rough consensus about the graph backend, the demo is going to happen soon21:43
dendrobatesthe model perhaps21:43
debo_osyes ....21:43
glencyes21:43
debo_osand the data backend21:43
debo_osif time permits21:43
debo_osany more thoughts/advice?21:44
dendrobatessounds good to me21:44
dendrobatesnext week we should advertise the meeting a bit more.21:45
debo_osall right ... bye for now21:45
danwentone thing...21:45
debo_ossure21:45
danwenti've heard juju brought up several times in this context.21:45
danwentI don't know enough about the details to know the difference, but crisp messaging of donabe vs. juju (spelling?) would be nice.21:45
debo_osI will let Rick answer too but juju doesnt do containers21:46
dendrobatesdebo_os: that was what I was going to say.21:46
debo_osIt can be compared to chef / puppet21:46
dendrobatesit's all orchestration21:46
danwentbut orchestration of single elements only?21:46
debo_osfor now21:47
*** mahmoh has left #openstack-meeting21:47
dendrobatesI will be meeting the juju guys in a couple weeks to see where we can work together21:47
danwentok, good to know.  I've just been asked several times and didn't know enough to explain the difference21:47
danwentthat's all21:47
dendrobatesok, now I just need to find a place to watch the world series21:48
debo_os#endmeeting21:48
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"21:49
openstackMeeting ended Wed Oct 19 21:48:59 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-10-19-21.02.html21:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-10-19-21.02.txt21:49
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-10-19-21.02.log.html21:49
danwentdendrobates, ah does that start tonight?21:49
glencGO RANGERS21:49
danwenthaha21:49
*** danwent has left #openstack-meeting21:49
dendrobatesGo Cards!21:49
glency'all have a good evening21:50
dendrobatesbye21:51
*** debo_os has quit IRC21:53
*** bengrue has quit IRC22:18
*** RichiH has quit IRC22:20
*** RichiH has joined #openstack-meeting22:21
*** HowardRoark has quit IRC22:41
*** jdg_ has joined #openstack-meeting22:41
*** nati2 has joined #openstack-meeting22:48
*** dendrobates is now known as dendro-afk22:52
*** bencherian has quit IRC23:02
*** bencherian has joined #openstack-meeting23:07
*** rnirmal has quit IRC23:17
*** jdg_ has quit IRC23:18
*** mdomsch has quit IRC23:27
*** jdg_ has joined #openstack-meeting23:27
*** dendro-afk is now known as dendrobates23:42
*** michaelkre has quit IRC23:54
*** kbader1 has quit IRC23:54

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