Thursday, 2012-04-05

*** Yak-n-Yeti has joined #openstack-meeting00:05
*** lloydde has joined #openstack-meeting00:17
*** heckj has quit IRC00:22
*** dtroyer_zzz is now known as dtroyer00:24
*** lloydde has quit IRC00:36
*** dtroyer is now known as dtroyer_zzz00:42
*** Yak-n-Yeti has quit IRC00:42
*** ayoung has quit IRC00:44
*** adjohn has joined #openstack-meeting00:48
*** dwalleck has joined #openstack-meeting00:49
*** dwalleck has joined #openstack-meeting00:50
*** dwalleck has quit IRC00:57
*** novas0x2a|laptop has quit IRC01:05
*** adjohn has quit IRC01:07
*** dwcramer has joined #openstack-meeting01:08
*** debo-os has quit IRC01:09
*** Yak-n-Yeti has joined #openstack-meeting01:13
*** pengyong has quit IRC01:19
*** dtroyer_zzz is now known as dtroyer01:31
*** mnewby has quit IRC01:36
*** pengyong has joined #openstack-meeting01:37
*** mnewby has joined #openstack-meeting01:59
*** zigo has joined #openstack-meeting02:18
*** LanceR604 has quit IRC02:22
*** Lance604 has joined #openstack-meeting02:31
*** dolphm has joined #openstack-meeting02:45
*** sandywalsh has quit IRC02:46
*** sleepsonzzz is now known as sleepsonthefloor02:47
*** dolphm has quit IRC03:09
*** dwcramer has quit IRC03:12
*** sandywalsh has joined #openstack-meeting03:30
*** jog0 has joined #openstack-meeting03:38
*** jog0 has quit IRC03:54
*** garyk has quit IRC04:29
*** Yak-n-Yeti has quit IRC04:36
*** dtroyer is now known as dtroyer_zzz04:55
*** kindaopsdevy has joined #openstack-meeting04:57
*** garyk has joined #openstack-meeting05:03
*** ewindisch has quit IRC05:13
*** sandywalsh has quit IRC05:17
*** ewindisch has joined #openstack-meeting05:21
*** adjohn has joined #openstack-meeting05:22
*** kindaopsdevy has quit IRC05:23
*** kindaopsdevy has joined #openstack-meeting05:30
*** sandywalsh has joined #openstack-meeting05:31
*** kindaopsdevy has left #openstack-meeting05:35
*** ravi has joined #openstack-meeting05:42
*** Lance604 has quit IRC05:43
*** jakedahn is now known as jakedahn_zz05:48
*** littleidea has quit IRC06:05
*** sleepsonthefloor is now known as sleepsonzzz06:06
*** zigo has quit IRC06:12
*** ravi has quit IRC06:32
*** ravi has joined #openstack-meeting06:33
*** ravi has quit IRC06:35
*** ewindisch has quit IRC06:42
*** mnewby has quit IRC06:43
*** Lance604 has joined #openstack-meeting07:00
*** Lance604 has quit IRC07:10
*** adjohn has quit IRC07:25
*** adjohn has joined #openstack-meeting07:27
*** adjohn has quit IRC07:29
*** adjohn has joined #openstack-meeting07:35
*** adjohn has quit IRC07:54
*** darraghb has joined #openstack-meeting08:00
*** derekh has joined #openstack-meeting08:25
*** journeeman has joined #openstack-meeting08:48
*** adjohn has joined #openstack-meeting08:54
*** adjohn has quit IRC08:55
*** zigo has joined #openstack-meeting09:09
*** adjohn has joined #openstack-meeting09:34
*** adjohn has quit IRC09:46
*** zigo has quit IRC10:13
*** pengyong has quit IRC10:29
*** markvoelker has joined #openstack-meeting11:44
*** mancdaz1203 has quit IRC12:10
*** Lance604 has joined #openstack-meeting12:10
*** mancdaz has joined #openstack-meeting12:11
*** sandywalsh has quit IRC12:12
*** littleidea has joined #openstack-meeting12:13
*** dolphm has joined #openstack-meeting12:20
*** Lance604 has quit IRC12:21
*** sandywalsh has joined #openstack-meeting12:25
*** dprince has joined #openstack-meeting12:48
*** pengyong has joined #openstack-meeting12:56
*** pengyong has quit IRC13:01
*** shwetaap has quit IRC13:11
*** littleidea has quit IRC13:17
*** pengyong has joined #openstack-meeting13:20
*** dwcramer has joined #openstack-meeting13:25
*** ayoung has joined #openstack-meeting13:32
*** shwetaap has joined #openstack-meeting13:33
*** deshantm has joined #openstack-meeting13:46
*** dtroyer_zzz is now known as dtroyer13:56
*** debo-os_ has joined #openstack-meeting13:59
*** kindaopsdevy has joined #openstack-meeting14:22
*** kindaopsdevy has quit IRC14:23
*** davlaps has joined #openstack-meeting14:25
*** jog0 has joined #openstack-meeting14:27
*** Yak-n-Yeti has joined #openstack-meeting14:29
*** dendro-afk is now known as dendrobates14:30
*** lloydde has joined #openstack-meeting14:33
*** adjohn has joined #openstack-meeting14:36
*** davlaps has quit IRC14:37
*** davlaps has joined #openstack-meeting14:38
*** Yak-n-Yeti has quit IRC14:42
*** lloydde_ has joined #openstack-meeting14:43
*** lloydde has quit IRC14:44
*** deshantm_ has joined #openstack-meeting14:45
*** davlaps_ has joined #openstack-meeting14:47
*** rnirmal has joined #openstack-meeting14:48
*** davlaps has quit IRC14:48
*** deshantm has quit IRC14:49
*** sandywalsh has quit IRC14:52
*** littleidea has joined #openstack-meeting14:54
*** zigo has joined #openstack-meeting14:54
*** lloydde_ has quit IRC14:55
*** dendrobates is now known as dendro-afk15:03
*** dendro-afk is now known as dendrobates15:03
*** dwcramer has quit IRC15:03
*** journeeman has quit IRC15:07
*** sandywalsh has joined #openstack-meeting15:07
*** adjohn has quit IRC15:09
*** zigo has quit IRC15:10
*** ryanpetrello has quit IRC15:11
*** byeager has joined #openstack-meeting15:13
*** Yak-n-Yeti has joined #openstack-meeting15:18
*** heckj has joined #openstack-meeting15:20
*** lloydde has joined #openstack-meeting15:25
*** littleidea has quit IRC15:26
*** dtroyer is now known as dtroyer_zzz15:30
*** ravi_ has joined #openstack-meeting15:31
*** ravi_ has left #openstack-meeting15:31
*** davlaps_ has quit IRC15:36
*** dwcramer has joined #openstack-meeting15:36
*** deshantm_ is now known as deshantm15:38
*** dtroyer_zzz is now known as dtroyer15:43
*** hggdh has quit IRC15:43
*** hggdh has joined #openstack-meeting15:45
*** littleidea has joined #openstack-meeting15:49
*** dwalleck has joined #openstack-meeting15:53
*** dendrobates is now known as dendro-afk15:53
*** hazmat is now known as kapilt15:58
*** dwalleck has quit IRC15:59
*** dwalleck has joined #openstack-meeting16:01
*** jog0 has quit IRC16:02
*** gyee has joined #openstack-meeting16:02
*** sleepsonzzz is now known as sleepsonthefloor16:07
*** pengyong has quit IRC16:22
*** garyk has quit IRC16:22
*** mattray has joined #openstack-meeting16:23
*** ryanpetrello has joined #openstack-meeting16:26
*** ravi_ has joined #openstack-meeting16:27
*** ravi_ has left #openstack-meeting16:28
*** dendro-afk is now known as dendrobates16:30
*** pengyong has joined #openstack-meeting16:33
*** rohitk has joined #openstack-meeting16:34
*** dolphm has quit IRC16:42
*** sandywalsh has quit IRC16:48
*** dwalleck has quit IRC16:52
*** garyk has joined #openstack-meeting16:58
*** jog0 has joined #openstack-meeting16:58
*** dwalleck has joined #openstack-meeting16:59
*** davidkranz_ has joined #openstack-meeting17:00
*** sandywalsh has joined #openstack-meeting17:01
*** rohit-k has joined #openstack-meeting17:02
*** rohitk has quit IRC17:02
dwalleckPing for quorum for QA meeting? Jay? David?17:04
davidkranz_Here.17:04
rohit-kpong17:04
dwalleckWe can start then. Only have a few things for today I think17:05
dwalleck#startmeeting17:05
openstackMeeting started Thu Apr  5 17:05:14 2012 UTC.  The chair is dwalleck. Information about MeetBot at http://wiki.debian.org/MeetBot.17:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.17:05
dwalleck#topic Current Reviews17:05
*** openstack changes topic to "Current Reviews"17:05
*** sandywalsh has quit IRC17:05
dwalleckSo the only thing under review that is of any contention is https://review.openstack.org/#change,622717:06
dwalleckWhich really boils down to how to we want to configure/execute authorization tests, correct?17:06
rohit-kdwalleck: yes17:07
rohit-kand also probably structure them17:07
rohit-kPersonally, I was more comfortable with the older design of the manager init17:08
dwalleckSo the issue that came up last week was concern over the number of changes made to the config file17:08
rohit-kokay17:08
dwalleckI personally like it too. I think the only thing that might raise some concern is the moving of the admin credentials back into the main compute config17:09
dwalleckdprince might throw something heavy at me :)17:10
davidkranz_What was the motivation for moving them out in the first place?17:10
rohit-kdwalleck: so is it not ok to be able to set admin credentials in tempest.conf?17:11
jaypipescrap, sorry guys, got caught up in a review...17:11
jaypipes#startmeeting17:11
dwalleckI think the idea was to keep the compute section as stable and basic as possible, and if people wanted additional configs, they would be seperate17:11
openstackjaypipes: Error: Can't start another meeting, one is in progress.17:11
dprincedwalleck: its all good sir.17:11
rohit-kdwalleck: aah, got it17:11
jaypipesoh, poop... sorry about that17:11
* dprince dprince likes stable config files17:11
rohit-khello, jay17:11
rohit-k!17:11
jaypipeshi :)17:11
dwalleckYup, that's the key17:11
dwalleckSo are we in agreement that being able to create an instance of a manager with whatever configs you want is fine, that it's just where that data comes from is what we need to solve?17:12
dwalleckI'm on cold meds, so I hope that made sense :)17:12
jaypipesdwalleck: adding additional things into the config is much easier for dprince to deal with than changing existing config options :)17:12
jaypipesdwalleck: yes, that makes sense to me above.17:13
rohit-kdwalleck: trying to understand, are we saying move admin configs out of the main config file (tempest.conf) ??17:14
davidkranz_dwalleck: I think so. Some tests might just want to instantiate a Manager in  different way. The stress tests do this.17:14
jaypipesrohit-k: no, we're saying keep admin configs in a different section of the tempest.conf ([compute-admin], [image-admin], etc17:14
jaypipesrohit-k: and not prefixing the username, password or tenant_name with "admin_"...17:15
rohit-kjaypipes: aah, ok, I think I agree with that, contrary to my proposed changes in the patch17:15
dwalleckrohit-k: No, not at all. The admin config was previously in the compute-admin section, and your change moved it into the compute section17:15
dwalleckThat's the part I want to sort out17:15
jaypipesdwalleck: *back* into the compute section :)17:15
rohit-kdwalleck, jaypipes: Yup, I am going to withdraw that change, I understand the reasons better17:16
jaypipesdwalleck: or rather, didn't we have a nonadmin_user1 or something? that is now the alt_username in the main [compute] section17:16
dwalleckyeah, what jay said lol17:16
rohit-khowever the manager object is what Im more interested in17:16
jaypipesrohit-k: ok, sounds good. or just amend the commit... either way.17:16
davidkranz_Can we agree that you should be able to create a Manager, that represents a (user, tenant), without having to use global config state?17:16
rohit-kjaypipes: yes17:16
*** mdrnstm has quit IRC17:16
dwalleckdavidkranz_: ++17:17
jaypipesdavidkranz_: I'm not so sure. I think creating clients separately from the global config might be a better way to go.17:17
jaypipesdavidkranz_: as in what dwalleck recently did in the test_authorization patch17:17
rohit-kThe concern that I see is that we would be having many client objects within manager that would be uused17:18
*** kindaopsdevy_ has joined #openstack-meeting17:18
dwalleckjaypipes: The only thing that would concern me is having to create many clients for one user for more complex scenarios17:18
jaypipesdavidkranz_: but I could be persuaded otherwise if you guys want to return to the place where you have optional __init__ args to the Manager...17:18
*** jdurgin has quit IRC17:18
*** kindaopsdevy_ has left #openstack-meeting17:18
rohit-kdwalleck: +117:18
*** sandywalsh has joined #openstack-meeting17:19
jaypipesdwalleck: sure, I understand you. What about, instead, passing in just an "alt=False" arg to the manager, then? that would load the clients using the alt_XXX confgs?17:19
davidkranz_jaypipes: I think so. Otherwise you have to create all the clients. In Daryl's case only a server client was needed.17:19
jaypipesdavidkranz_: what would you think about the alt=False param?17:19
jaypipesdavidkranz_: instead of passing username, password, tenant?17:19
*** derekh has quit IRC17:20
dwalleckjaypipes: Hmm...I'm trying to think if there's a scenario where that wouldn't work. Really the most you need for authz tests would be 2 normal users and 1 admin user17:20
dwalleckFor basic tests at least17:20
rohit-kjaypipes: I think the question is, would we want the tests to access config objects directly?17:20
jaypipesrohit-k: well, they all currently do...17:20
davidkranz_jaypipes: I was just thinking that there might be more complex scenarios that would find config files too much of a pain.17:20
jaypipesrohit-k: via the manager.config...17:20
rohit-kor let the manager do that17:20
jaypipesdavidkranz_: yeah, I hear ya..17:20
rohit-kjaypipes: ok17:21
rohit-kjaypipes: makes sense too17:21
davidkranz_I don't have a strong opinion about where the admin user goes in the config file.17:21
rohit-kI'm in a dilemma on this one :P17:22
jaypipesdavidkranz_: how about a compromise, then? start with the alt=False single parameter to openstack.Manager.__init__() and then, if we find that does not provide an appropriate level of configurability, we take another look at it?17:22
dwalleckjaypipes: That sounds reasonable17:22
davidkranz_jaypipes: We could do that. I just don't see the harm in providing keyword arguments for the others.17:22
jaypipesdavidkranz_: for the admin user, tests really shouldn't be run with them... unless it is an admin-only API (like flavor CRUD), which is why I separated out that into a separate config section [compute-admin], thinking that eventually we'd want to carve out a /tempest/tests/compute/admin/* set of tests17:23
davidkranz_jaypipes: alt would be fine for now.17:23
dwalleckjaypipes: ++ on admin tests. I'd love to find some docs on those to flesh out that area out17:24
jaypipesdavidkranz_: ok, thx. the advatage to alt=False is a) less verbose and b) enables the manager to control how it looks up alternate creds (instead of the caller having to remember...17:24
jaypipesdwalleck: heh, you and me (and davidkranz_) both!17:24
jaypipesdwalleck: it's a pain in the ass trying to find that kind of api docs :(17:24
*** ryanpetrello has quit IRC17:24
* dwalleck begins casting Retrieve Invisible Docs....17:25
jaypipesOK, so who's going to tackle this? rohit-k, you want to do it on your existing changeset?17:25
jaypipesrohit-k: clear on what the changes would be?17:25
rohit-kjaypipes: alt=False is only to lookup the alt_credentials?17:25
jaypipesrohit-k: correct.17:25
jaypipesrohit-k: basically something like:17:26
jaypipesif alt:17:26
jaypipes    username = config.compute.alt_username17:26
jaypipesetc, etc17:26
jaypipeswhere username gets passed to the client classes..17:26
rohit-kjaypipes: how about using config.compute_admin.username?17:26
jaypipesrohit-k: damn it. davidkranz_ is right.17:26
jaypipes:)17:26
rohit-k:)17:26
dwallecklol17:26
jaypipesok, back to the passing the creds in the __init__ of the Manager... I submit! I submit! Uncle!17:27
rohit-kI need a manager object that can be used for admin ops, simple :)...lol17:27
jaypipesrohit-k: hmm, well that's also a possibility too... hold on a sec. I have an idea... (uh oh!)17:28
rohit-kscratching my head17:28
dwalleckthe only other thing I could think of would be to expand on Jay's idea and instead of making it bool, make it a role name: alt, admin, etc17:29
dwalleckThat would take magic in the backend to work it, but it might be cleaner17:29
rohit-kdwalleck: works17:29
dwalleckBut magic can be bad as well....not sure if the ends justifies the means17:30
dwalleckI'm interested in what Jay's cooking up. He's quiet :)17:31
jaypipeshttp://pastie.org/373420317:31
jaypipesthat would give us both brevity and configurability... :)17:31
jaypipesthoughts?17:32
fattarsijaypipes: ++17:32
rohit-kjaypipes: ++17:32
dwalleckThat is a much less hackish version of what I mentioned :) ++17:32
jaypipeswe could even have the AdminManager install additional clients that are admin-only ...17:32
jaypipesdavidkranz_: thoughts?17:32
davidkranz_jaypipes: Works for me.17:33
jaypipesdavidkranz_: and if there WAS a need for even more configurability, we could just call Manager with args directly...17:33
*** jog0 has left #openstack-meeting17:33
dwalleckPlus it may be good to have these users that we can almost refer to as avatars, so that when we talk about strange scenarios, we're all speaking the same language17:33
rohit-kjaypipes: we still are having the args17:33
davidkranz_jaypipes: Yes, that was my point before.17:33
jaypipesrohit-k: right, but you only have to do: cls.manager = openstack.AdminManager()17:33
jaypipesrohit-k: no need to pass args... :))17:33
jaypipesdavidkranz_: k, cool...17:34
davidkranz_What about the issue I put in the ticket about whether admin-only is part of an api or could vary with implementation?17:34
davidkranz_I think it should be part of the API but obviously others differ.17:35
jaypipesdavidkranz_: heh, that's a wholly separate issue, and I don't think it will be resolved until the Nova API has some level of discoverability/metadata about that kind of thing :(17:35
jaypipesdavidkranz_: otherwise, we're going to be stuck with a whole crap-ton of things like api_flavors_crud_admin_only = False in the config file! :(17:35
davidkranz_jaypipes: So for now we will assume the defaults define which apis are admin?17:35
jaypipesdavidkranz_: yes, I believe that is the only thing we can feasibly do for now.17:36
jaypipesdavidkranz_: good topic for the design summit, though.17:36
*** davlaps has joined #openstack-meeting17:36
jaypipesOK, so back to my question.. who will do this work? rohit-k, are you comfortable incorporating these changes into your patch?17:37
*** jdurgin has joined #openstack-meeting17:38
rohit-kjaypipes: yes, it looks good to me, just fear that the base class be misued with something like cls.manager = openstack.Manager(alt_credentials)17:38
jaypipesrohit-k: sure, but that's for reviewers to catch ;)17:39
rohit-kright17:39
rohit-kjaypipes: Could you post that change?17:39
jaypipesrohit-k: the one I just pasted?17:39
rohit-kjaypipes: I think that looks great, that solves my problem17:39
rohit-kyep17:39
jaypipesrohit-k: ok, no worries. will do right after this meeting.17:40
rohit-kjaypipes: thanks!17:40
jaypipesnp!17:40
jaypipesdwalleck, fattarsi, davidkranz_, rohit-k: any other thoughts before we wrap up?17:40
davidkranz_dwalleck: Daryl, do you have an ETA for your ssh-to-guests stuff. I would like to use it in the stress tests when it lands.17:40
rohit-ki'd also like to discuss where we place the admin tests!17:40
*** kapilt is now known as hazmat17:41
rohit-kjaypipes: like what was discussed in lp:9733817:41
rohit-klp:97333817:41
dwalleckJust one comment with no good answer: so yesterday brought up the difficult question of how to handle tests when bugs are fixed :)17:41
dwalleckI wish we could do something on the fly, but without a build number or something from OpenStack to tell if you should have this bug fixed in your environment, I don't see a good solution...17:42
jaypipesrohit-k: I suggested /tempest/tests/compute/admin/. Wondering if others are cool with that?17:42
jaypipesdwalleck: other than a config section like [bugs-fixed]? that lists fixed bugs? Not sure there's a good solution :(17:42
rohit-kjaypipes: cool with me17:43
dwalleckdavidkranz_: That depends on which solution I use. If we're okay with (for now) manually setting which interface we ssh in over, by end of day tomorrow17:43
jaypipesrohit-k: I say just use that directory...17:44
dwalleckjaypipes: Yeah, I know...it bugs (no pun intended) me, so I'll keep thinking on it17:44
fattarsiis anyone working on swift tests?17:44
davidkranz_dwalleck: I thing that would be fine.17:44
jaypipesrohit-k: if these guys don't like it, we can bring it up on review :)17:44
jaypipesfattarsi: yes, Jose from RAX is.17:44
jaypipesdwalleck: speakign of which :) any updates on that?17:44
rohit-kjaypipes: sure :)17:44
dwalleckMaybe instead of naming that group "broken tests", maybe it's a "it should be failing but if it does pass, great!"17:45
dwalleckI was going to ping Jose and toss that to him, but he's not here....17:45
jaypipesAlso, please go voice support for my patch to devstack here: https://review.openstack.org/#change,6248,patchset=1  It gets the tempest config working again for our Jenkins job here: https://jenkins.openstack.org/view/Tempest/job/dev-gate-tempest-devstack-vm/17:45
davidkranz_jaypipes: The nova bug I filed about that change in return code was never addressed so I guess the new value is what it is and we should fix and reenable the test.17:46
jaypipesdavidkranz_: sorry, which bug again?17:46
*** jog0 has joined #openstack-meeting17:46
dwalleckI need see what's going on there. I don't want to hold up work, but it would be really valuable to be able to port their tests in17:46
*** darraghb has quit IRC17:47
jaypipesdwalleck: k. check with Jose... would indeed be great to demo Tempest Swift tests in design summit.17:47
davidkranz_jaypipes: https://bugs.launchpad.net/nova/+bug/96324817:47
*** jog0 has quit IRC17:47
uvirtbotLaunchpad bug 963248 in nova "Return code for rebuild with non-existent image changed" [Undecided,New]17:47
jaypipesaha!17:47
dwalleckBut on the ssh front, are folks okay with temporarily setting something like ssh_network and ssh_ip_version vars?17:47
*** jog0 has joined #openstack-meeting17:47
jaypipesdavidkranz_: yeah, I will comment on the bug.17:48
jaypipesdwalleck: in the [compute] config section? or ... somewhere else?17:48
dwalleckI'm working on a clever way to just use the first reachable interface the tests can find, but I'm trying to take this slowly because if it doesn't work right, it can be very confusing17:48
dwalleckjaypipes: it would probably go in the [compute] config section since it's only relevant to Nova. Or I could create a compute-network or compute-ssh config section as well17:49
davidkranz_dwalleck: Well, we just 'ssh ip-address' to the guest usually so we could just use that as the default.17:49
dwalleckdavidkranz_: ? I don't follow17:50
dwalleckHow do you know if that IP address is reachable from your current network?17:50
davidkranz_dwalleck: If the machine has a floating ip address and was created with an ssh key why can't we just ssh in like we would manually?17:50
davidkranz_dwalleck: Of course this onlyh works in an encolsed test environment.17:51
dwalleckdavidkranz_: In a lot of the environments I work in, just because you have an assigned IP doesn't mean you can reach it17:51
dwalleckSome of the IPs can even be fakes....so to make sure I can reach the instance, I manually set an interface per environment that I want to use SSH17:52
davidkranz_dwalleck: But if the point is to have the test ssh to verify stuff you have to be able to get there, right?17:52
jaypipesdwalleck: yeah, compute section is fine with me. was just curious...17:52
dwalleckdavidkranz_: it is! Actually, I can give you a real example....17:52
dwalleckIn one of my test environments, I have a public IPv4 address (which is fake), a public IPv6 address, and a private IPv4 address which is in a network I can't reach17:53
*** mnewby has joined #openstack-meeting17:53
dwalleckSo ideally I'd want to use the public IPv6 address since it's the only one that would be accessible17:53
davidkranz_dwalleck: I understand.17:54
dwalleckIn another environment I have publicly reachable IPv4 addresses but no IPv6 routing, so I need to use IPv417:54
*** ryanpetrello has joined #openstack-meeting17:54
dwalleckSo I just want to make sure if we add this functionality, we can be explicit enough to make sure it's going to work17:55
dwalleckAnd if it doesn't work, it's a failure. You have no idea the headache I went through the first time I hit that wall :)17:56
dwalleckSo what is the group think? Is manual okay for now or do you want auto config?17:57
davidkranz_dwalleck: Manual today, auto tomorrow...17:57
jaypipessounds like a good compromise, yes.17:58
fattarsiagreed17:58
jaypipesI'd gladly pay today for an automation tomorrow ;)17:58
dwalleckokay, good deal. I'll knock it out17:58
jaypipesrock on.17:58
dwalleckI'm excited :) This is where a lot of the work we've done is. We're doing some cool deep validation17:58
davidkranz_jaypipes: But tomorrow is not Tuesday.17:58
dwalleckOkay, I need to rush off to another meeting17:59
jaypipeslol :)17:59
jaypipesKeep an eye out for https://jenkins.openstack.org/view/Tempest/job/dev-gate-tempest-devstack-vm/, BTW. I'm going to work with jeblair to get that damn thing passing today!17:59
dwalleck#endmeeting17:59
*** openstack changes topic to "Status and Progress (Meeting topic: keystone-meeting)"17:59
openstackMeeting ended Thu Apr  5 17:59:21 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-05-17.05.html17:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-05-17.05.txt17:59
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-05-17.05.log.html17:59
jaypipessee y'all!`17:59
davidkranz_jaypipes: Great!17:59
dwalleckAdios!17:59
rohit-ksee ya!17:59
fattarsiciao17:59
*** davidkranz_ has quit IRC17:59
*** esker has joined #openstack-meeting18:01
eskerHello18:01
jdurginhi18:02
*** jgriffith has joined #openstack-meeting18:02
jgriffithanybody here todya?18:02
rnirmaljgriffith: here early today18:03
rnirmalusually I realize in like the last 10 mins18:03
jgriffith:)18:03
jgriffithI know the feeling18:03
jgriffithMaybe I should email out reminders18:04
jdurginesker and I are here too18:04
*** dwalleck has quit IRC18:04
*** rohit-k has quit IRC18:04
jgriffithOk... sounds like enough interest18:04
jgriffith#startmeeting18:04
openstackMeeting started Thu Apr  5 18:04:25 2012 UTC.  The chair is jgriffith. Information about MeetBot at http://wiki.debian.org/MeetBot.18:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.18:04
jgriffithBefore I start does anybody have anything they want to bring up?18:04
rnirmalyou are going to talk about summit discussions right18:05
jgriffithYep...18:05
jgriffithSo I'll go ahead and start18:05
jgriffith#topic summit18:05
*** openstack changes topic to "summit"18:05
jgriffithSo as of right now I have 3 submissions for summit topics18:06
*** mdrnstm has joined #openstack-meeting18:06
jgriffith1. Gluster demo 2. BootFromVolume (Renuka) 3. BootFromVolume(me)18:06
jgriffithI'll be adding a brainstorm on BlockStorage As a Service as well18:06
rnirmalyeah that's the one I wanted to bring up18:07
rnirmalso there's a conference panel session on that too.18:07
jgriffithrnirmal: cool, let's talk about that one first then18:07
rnirmalwould be would to have a design session first before the conference starts to get all the dev opinions18:07
eskerThere's another one on summit.openstack.org18:07
eskerpertains to shared filesystems18:07
eskerhttps://blueprints.launchpad.net/nova/+spec/nova-sharedfs18:08
rnirmalyeah those are the sessions I see right now18:10
rnirmaljgriffith: were you planning on proposing a brainstorm session for splitting out nova-volumes18:11
eskerThere's of course several proposed for splitting up Nova18:11
*** jgriffith has quit IRC18:12
*** jgriffith has joined #openstack-meeting18:12
jgriffithStill here?18:12
rnirmalyeah18:12
jgriffithSorry about that18:12
eskerI'm here...18:13
jgriffithMy machine locked up18:13
rnirmaljust was asking abt splitting up nova-volume.. .and esker mentioned there's other sessions for splitting up nova18:13
jgriffithAre there specific proposals under nova/other?18:14
jgriffithHaven't looked in a few days18:14
rnirmalhere's one http://summit.openstack.org/sessions/view/2118:14
jgriffithAhh... yes18:15
rnirmaland this one http://summit.openstack.org/sessions/view/3818:15
jgriffithI saw these but they weren't specifically Volume18:15
jgriffithI was thinking of a brainstorm to focus specifically on Volume18:16
jgriffithIt seems that there a number of projects people are interested in spinning18:16
jgriffithUnfortunately it would be nice to have these two sessions before ours but that isn't going to work out18:16
jgriffithDo you guys feel these two sessions would be sufficient?18:17
rnirmalwell based on which one gets accepted... the brainstorm session may be enough... if we are just going to talk about splitting18:17
rnirmalbut if we want to also discuss abt plans for folsom18:18
rnirmalwe may need a different session18:18
jgriffithThe good thing is as far as the volume track I can approve18:18
jgriffithI would like to discuss for Folsom18:19
jgriffithPrimarily try and actually get some momentum to make this happen18:19
jgriffithThere are also some good features around boot from volume, glance backing store etc that we'll need to do the seperation piece first18:19
rnirmalyes essex got some interest initially but essentially tailed off18:19
jgriffithYeah, we need to try and keep that from happening again18:20
jdurginjgriffith: made a couple blueprints about that https://blueprints.launchpad.net/nova/+spec/create-volumes-from-images and https://blueprints.launchpad.net/nova/+spec/efficient-volumes-from-images18:20
jdurginwe can probably discuss those as part of the boot from volume sessions18:21
jgriffithjdurgin: Yeah, I saw those... looks good.  and that brings me to the "problem" I have  :)18:21
jgriffithSo Renuka (is Renuka here today?) has proposed a session as well and specifically didn't want it in the Volume Track18:21
jgriffithShe has a blue print as well18:21
jdurginyou mean the xenapi-boot-from-volume one?18:22
jgriffithJust a sec.. pulling it up now18:23
jgriffithnova/nova-create-bootable-volume18:23
jdurginok, sounds pretty similar18:25
jgriffithjdurgin: yeah18:26
jgriffithSo I was thinking, maybe we should work before the summit to pull the two together and have something in common to work off of?18:26
jgriffithThere are multiple blueprints out there with the same idea18:28
jgriffithSo the other option I considered was having both sessions18:28
jdurginmaybe just point that one to the wiki page (http://wiki.openstack.org/CreateVolumesFromImages) and close my first one?18:28
jgriffithSince it's likely to be a lengthy discussion18:28
jgriffithjdurgin: That's your call, if they're similar enough and you're happy with that cool18:28
jgriffithbut I don't want to make that call for you18:29
jgriffithIs there anything else that people want to see as far as volume sessions at the summit?18:29
jdurginI don't really care whose blueprint is where, as long as we retain all the ideas18:29
eskerI'm definitely interested in the shared storage proposal.18:30
eskerWhich incidentally has import for boot from volume (or in this case... from filesystem).18:30
jgriffithSo the good thing is we have enough time for everything that's been proposed, my question is do we have other sessions topics (other than BSAAS) to bring up?18:31
jgriffithAfter this week I think we should finalize this18:31
rnirmalI'd like to see all the virt drivers volume code consolidated... xen/libvirt etc has their one client side iscsi code... it would like to float the idea of a volume client18:31
rnirmalthat the virt code could use18:31
rnirmalI'll write up a blueprint for it... haven't done it yet18:32
jgriffithrnirmal: Sounds like a good idea, do you want to propose a brainstorming session?18:32
*** jog0 has left #openstack-meeting18:32
rnirmalyeah was thinking of that18:32
rnirmalhow about I follow up on that with you on Monday.. I don't have anything written up right now18:32
eskerjgriffith: did you see what I typed wrt https://blueprints.launchpad.net/nova/+spec/nova-sharedfs ?18:33
eskerthat would be a session topic beond BSaaS18:33
eskerbeyond rather18:33
jgriffithMake you a deal.... I'll submit the proposal and approve it and you handle it next week when you have time :)18:33
jgriffithesker: Yes, Adnrew's proposal you mean?18:34
eskercorrect18:34
eskerhttp://summit.openstack.org/sessions/view/318:34
jgriffithesker: I fully plan on that being approved and in for sure.18:34
rnirmalI think it would be good to extend that to a 55 mins brainstorm session... for a general discussion of shared filesystems beyond their demo/pres18:35
jgriffithrnirmal: Problem is I don't want to take away from Andrews demo18:36
jgriffithOnce we open it up to brainstorm we eat a bunch of time... mabye an additional/related session... something like "how to extend it"18:37
rnirmalsure...18:37
eskerRight, it should be separate.18:37
jgriffithOk... then we're getting closer to filling our allotted time slots18:37
eskerIs there one expressly intended to structure Folsom priorities / efforts?18:38
eskerWe're talking about a number of semi-abstract things that could get implemented... but what would align to Folsom?18:38
jgriffithSo we'd have:  SharedFSDemo(25min) SharedFSExtensionBrainstorm(55min) BootFromVolume(55min), BSAAS(55min)18:38
*** mnewby has quit IRC18:38
jdurginesker: that sounds like a great idea18:38
*** novas0x2a|laptop has joined #openstack-meeting18:38
jgriffithesker: So my goal would be to come up with plans to what goes in Folsom18:39
eskerA worth goal ;-)18:39
jgriffithHonestly all of these things IMHO should be in18:39
eskerworthy... damn typos18:39
jgriffith:)18:39
jgriffithIt's the details that become problematic18:39
eskerMy thought is that we ought aim to recap the design summit towards the end of the last day (or perhaps as a breakout if everyone is staying for the ensuing conference) to project manage priorities and such for Folsom18:40
jgriffithesker: +1 Breakouts for sure!!!!18:40
jgriffithI was also planning on some informal meetings... maybe over a beeer here and there :)18:41
jgriffithOk... so the proposals I've called out above use up all of the time we have for volume18:42
jgriffithIf we want to add we have to take away....  or use breakouts to the fullest extent18:42
rnirmalk sounds good.18:42
jgriffithAlright, then that settles summit sessions I think18:42
jgriffithI'll be contacting folks next week probably to sync up on how we want to run them.18:43
jgriffithinparticular get some of the ideas you already have out as a foundation for the discusssions18:43
jgriffithAnything else WRT the summit?18:43
jgriffithCool!!!18:44
jgriffithI have another selfish topic, but I'll let others jump in before I start :)18:44
jgriffithgoing once...18:45
jgriffithtwice...18:45
eskerwrt the summit... sounds good18:45
jgriffithesker: Ok... great.18:45
jgriffithIf anybody thinks of anything just email me!!18:46
jgriffithI think I need to finalize this by the end of the week probably18:46
*** mattray has quit IRC18:46
jgriffithOk...18:46
jgriffith#topic volume_uuid conversion18:46
*** openstack changes topic to "volume_uuid conversion"18:46
jgriffith:)18:46
jgriffithI've started working on this again and needed some input...18:47
DuncanTUgh, sorry, I didn't notice the time18:47
jgriffithThe approach I took was to just add a uuid column to the database18:47
jgriffithDucanT: No problem...18:47
DuncanTSessions look to be well sorted though :-)18:47
jgriffithI don't think we did anything controversial18:47
jgriffithWe just finalized our plans regarding summit sessions18:48
jgriffithCheck the notes, if you have any changes or requests send me an email18:48
DuncanTCheers18:48
jgriffithBack to uuid's18:48
rnirmalleaving it as a uuid column is fine, but would be better to replace the existing id.18:48
jgriffithOk.. that's what I discovered today trying to debug18:49
jgriffithHaving two columns and two ways to do it is a PITA18:49
jgriffithrnirmal: The only concern was ec2...18:49
rnirmalit's been problematic in nova :)18:49
jgriffithLOL18:50
*** ryanpetr_ has joined #openstack-meeting18:50
rnirmalah it breaks ec2 compatibility... well I hope to hear a lot more on ec2 compatibility this summit18:50
jgriffithSo I've been able to get most of the tests working... there are some problems I'm running into with snapshots and the ec2 calls18:50
jgriffithrnirmal: Yeah, the ec2 thing is what screws the "easy" path up18:51
*** dwcramer has quit IRC18:52
jgriffithOne thing I'm trying to figure out though, I'm assumign that as long as I don't change the method signature in ec2/api I should be able to make things work18:52
jgriffithassuming18:52
rnirmalare they like volume-000000001 type id18:52
jgriffithrnirmal: yes18:52
*** ryanpetrello has quit IRC18:53
jgriffithBut the good thing is we have an ec2_id column in the volume table18:53
rnirmaldo we, is that something that got added in essex?18:53
jgriffithBut backreferencing to snapshot, metadata etc is weird.18:54
jgriffithrnirmal: I just noticed it a minute ago, don't know when it was introduced or if it's even necessarily what I think it is :(18:54
jgriffithIt's in the version of devstack I pulled down yesterday18:54
jgriffithMay be in an older version as well... dunno18:55
rnirmalk looks like it's there even in diablo.. just haven't used it18:55
jgriffithinteresting18:55
jgriffithSo it sounds like the preference is to have just a single id column and have it be the primary key AND convert it to UUID?18:55
*** dwalleck has joined #openstack-meeting18:55
rnirmalyeah that'd be the best route to go... unless there are big hurdles18:56
jgriffiththere are... BUT I'd rather jump those hurdles than the mess of having both18:56
*** nati has joined #openstack-meeting18:56
jgriffithAt least I think I would18:57
rnirmalyeah I biggest concern there is migration existing environments... not sure how many are using volumes right now18:57
*** mattray has joined #openstack-meeting18:57
jgriffithrnirmal: That's what I was just typing :)18:57
rnirmalthere's probably going to be a bump up in usage with Essex18:57
heckjrnirmal: we're seeing quite extensive use of the volume mechanisms18:58
jgriffithI suppose we could introduce a column that's like "legacy_id" or something and provide a DB/api call to get_legacy_from_uuid?18:58
jgriffithIn other words we'd still have both, but the 'id' column would be a uuid18:59
*** dwalleck has quit IRC18:59
rnirmalyeah that would be good.18:59
jgriffithSo for example... what I do is if you pass in an id to the db/api and it's an int I'll do the conversion/lookup for you19:00
jgriffithIt's really the same thing I have in there already but I get over this crappy primary_key issue I'm having19:00
rnirmalyeah that should be fine... just not sure what all drivers use the int id in the backend and how they use it19:00
jgriffithYeah, but everybody agreed before that it's up to vendors to test/vix their drivers :)19:01
rnirmaljgriffith: If that's the case... lets do it19:01
jgriffithI've been able to get almost all of the unit tests to pass w/ the exception of ec219:01
jgriffithrnirmal: Ok... I'll give it a shot this afternoon and see what happens.19:02
jgriffithQuick quesiton... is there an sqlalchemy call to change the type on a column or do I need to drop and recreate?19:02
rnirmaljgriffith: I think there's a alter19:02
jgriffithrnirmal: Ok, I'll google it19:03
jgriffithAlright... we're over on time19:03
rnirmalbut not sure how well it would work for converting from int to string.. you may have to migrate data19:03
DuncanTI think you'll need to migrate19:03
jgriffithI'll play with it, if somebody sees a better way than what I end up doing we can change the migration easy enough19:03
eskerApologies... I have to run.19:04
jgriffithesker: NP, thanks!!19:04
eskerbye19:04
*** esker has quit IRC19:04
jgriffithDuncanT: So drop and recreate in the migration file?19:04
DuncanTjgriffith: Or add a new column of type string, copy the data over, remove the old column then rename the new one19:05
DuncanTTwo passes through the data but it shouldn't be big enough to be a problem I'd ahve thought19:06
jgriffithDuncanT: I think I'll go that route... easier to undo for the revert piece19:06
jgriffithDucnanT: Cool... like I said, if somebody reviews it and sees a better way it's fairly easy to change the migration as long as it does the right thing  :)19:06
*** dwcramer has joined #openstack-meeting19:06
jgriffithOk, I better give up the room :)19:07
DuncanTI'll keep an eye out for it19:07
jgriffith#endmeeting19:07
*** openstack changes topic to "Status and Progress (Meeting topic: keystone-meeting)"19:07
openstackMeeting ended Thu Apr  5 19:07:13 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:07
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-05-18.04.html19:07
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-05-18.04.txt19:07
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-05-18.04.log.html19:07
jgriffithDucanT: I've been pushing to my own repo on github19:07
*** novas0x2a|laptop has quit IRC19:07
jgriffithNow that essex is out I may not have to do that any more though19:07
DuncanTWhere are you on github sorry?19:08
jgriffith#link https://github.com/j-griffith19:08
jgriffithThis is similar to what we're talking about but I added a uuid column19:09
*** blamar has joined #openstack-meeting19:09
jgriffithTrouble is then I got into going through and changing every call that had volume_id or volume['id'] to uuid and it gets ugly/confusing19:10
DuncanTI get what you mean19:10
jgriffithOk... I gotta run out for a bit, but if anybody wants to discuss this more with me I'll be back on irc in about an hour and would LOVE to chat more about it and get some feedback19:11
DuncanTIt's heading towards late evening here I'm afraid, so I'm unlikely to be back on until Tuesday19:11
jgriffithAhhh... ok, then.  Have a nice long week-end :)19:12
DuncanTThanks :-)19:12
jgriffithsee yaa19:12
*** jgriffith has quit IRC19:12
*** debo-os_ has quit IRC19:18
*** novas0x2a|laptop has joined #openstack-meeting19:22
*** mdomsch has joined #openstack-meeting19:23
*** blamar has quit IRC19:25
*** blamar has joined #openstack-meeting19:28
*** dhellmann has quit IRC19:31
*** dhellmann has joined #openstack-meeting19:33
*** hggdh has quit IRC19:34
*** mnewby has joined #openstack-meeting19:37
*** mnewby has quit IRC19:37
*** mnewby has joined #openstack-meeting19:37
*** mnewby has quit IRC19:44
*** dhellmann has quit IRC19:48
*** hggdh has joined #openstack-meeting19:52
*** zigo has joined #openstack-meeting19:54
*** dprince has quit IRC19:54
*** mikeyp has joined #openstack-meeting19:55
*** kindaopsdevy_ has joined #openstack-meeting19:56
*** n0ano has joined #openstack-meeting19:59
*** sriramhere has joined #openstack-meeting20:00
*** joesavak has joined #openstack-meeting20:00
*** maoy has joined #openstack-meeting20:01
*** novas0x2a|laptop has quit IRC20:01
n0anoanybody here for the orchestration meeting?20:02
maoyyes20:03
mikeypyes20:03
*** jgriffith has joined #openstack-meeting20:03
maoyhi n0an0 and mikeyp20:03
maoyi mean n0ano. :)20:03
mikeyphi, maoy20:04
n0anomaoy, NP, nobody gets it right, although most get it as nano20:04
mikeypand everyone else20:04
n0ano#startmeeting20:04
openstackMeeting started Thu Apr  5 20:04:17 2012 UTC.  The chair is n0ano. Information about MeetBot at http://wiki.debian.org/MeetBot.20:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.20:04
maoydo we have any update on the summit session?20:04
n0anoI believe sriram is working on the BP for the Orchestration session, do we have anything else to discuss today?20:04
maoyis he here?20:05
n0anohe hasn't chimed in yet20:05
mikeypI dont have anything specific20:05
mikeypwaiting for more info on the SpiffWorkflow research20:05
maoyright20:06
n0anoI saw the emails on SpiffWorkflow, I am concerned that it might be overkill but let's wait for the detailed researc h20:06
maoyi should look deeper in spiffworkflow. my first impression was it's more complicated than we need. but i could be wrong20:06
mikeypFrom my initial research, most of the others were _very_ limited20:07
*** sriramhere_ has joined #openstack-meeting20:07
sriramhere_hello there20:07
n0anosriramhere, good to hear from you20:07
sriramhere_my msgs were not going through, and logging in as sriramhere_20:07
n0anoany news on the BP for the session?20:08
n0ano#topic Orchestration session at the summit20:08
*** openstack changes topic to "Orchestration session at the summit"20:08
sriramhere_I updated BP with the session topics as we discussed last week20:08
*** sriramhere has quit IRC20:08
sriramhere_session is still under review20:08
sriramhere_also, you might have seen from the email threads, our submission is 'complete' for session proposal. but we can work on prototyping.20:09
sriramhere_Ziad was mentionng abt abt using Zookeeper. is around?20:10
maoyI saw it as "Unreviewed" in summit.openstack.org20:10
maoyi mean I'm still seeing it as unreviewed right now20:10
sriramhere_sorry, i meant 'Unreviewed'20:10
sriramhere_not 'under review'20:10
n0anodo we need to ping Vish about it?20:11
maoynot sure if there is a deadline for that20:11
n0anoyeah but it's getting close (less than 2 weeks away) I don't want to slip through the cracks20:12
sriramhere_I can, but I am sure he is swamped with too many proposals. Let me send an email rt away20:12
*** pengyong has quit IRC20:12
*** hggdh has quit IRC20:12
sriramhere_vishvananda@gmail.com is his eamil, er?20:12
sriramhere_rt?20:13
n0anojust a quick `did you see it, do you need anything else' should be sufficient20:13
n0anoyep, that's the email I used last time I talked to him20:13
mikeypI think we will see movement now that Essex is out.20:13
sriramhere_I agree.20:14
n0ano#action sriramhere_ to ping Vish about the Orchestration session20:14
sriramhere_done20:15
sriramhere_i also started working on a branch; just got started20:15
n0anoI think that pretty much covers the session for now, anything else we need to discuss?20:15
sriramhere_if u have any pointers regarding the same, please shoot me an email offline20:16
sriramhere_let us also wait for Ziad's updtes20:16
maoysriramhere_: what exactly are you coding towards?20:16
sriramhere_trying to mimick aws workflow, per Sandy's suggestion.20:18
sriramhere_having OS as a separate service.20:18
sriramhere_i am currently thinking just be an observer of states.20:18
*** mnewby has joined #openstack-meeting20:19
sriramhere_still not very clear. playing around now. my intent is to show two things20:19
sriramhere_1) as a separate service how it tracks the states in a wf20:20
*** mnewby has quit IRC20:20
*** mnewby has joined #openstack-meeting20:20
sriramhere_2) to see wat r the touch points with core, network20:20
sriramhere_no real logic for now20:21
*** mnewby has quit IRC20:21
*** mnewby has joined #openstack-meeting20:21
maoygot it20:23
maoyby aws workflow, you mean the SWF stuff?20:23
sriramhere_yes20:23
maoyperfect20:24
* sandywalsh lurks :)20:24
sandywalshsriramhere_, you may want to look at stacktach/worker.py for how to monitor the notification queue20:24
sandywalshhttps://github.com/rackspace/stacktach/blob/master/worker.py20:25
sriramhere_thanks Sandy20:26
sandywalshnp20:26
sriramhere_maoy - u had a point on zookeeper in the email thread. want to elaborate?20:27
*** hggdh has joined #openstack-meeting20:27
maoywhich email? I already forget. :)20:27
sriramhere_in response to Ziad's email on Zookeeper.20:28
maoyzookeeper is a highly available service for distributed naming, synchronization, (configuration) state management, etc20:28
sriramhere_? I'm slightly concerned that  > SpiffWorkflow might be an overkill and bring unnecessary complexity  > into the game.20:28
sriramhere_sorry tried pasting from your email20:29
maoysandywalsh mentioned "bitkeeper", is that a typo for zookeeper?20:29
n0anoI hope so, bitkeeper is a git competetor, not what we're looking for.20:30
sandywalshmaoy, yup, sorry20:30
maoygreat. now we are on the same page20:31
maoyi'm curious about the same issue. but when I glanced through spiffworkflow, I didn't see any mentioning of where state is stored, etc20:31
*** zigo has quit IRC20:32
sriramhere_ok - so nobody seems to have concers abt zookeeper as of now, is that rt?20:33
sriramhere_i will continue working on the branch and update as appropriately20:33
n0anowell, I think we are all concerned that it might be overkill and we'd like to know more about it.20:33
maoyi think there is always a concern when we introduce a new component. but the only workaround is to put the state in mysql20:34
n0anocontinuing on the branch seems like a great idea, let's see where that goes.20:34
sriramhere_ok20:34
n0anoand your problem with mysql is...20:34
maoy:)20:34
* n0ano thinks distributed databases do a pretty good job20:35
maoymysql doesn't have a watch function20:35
maoyso the client side will have to periodically poll to check for state change20:35
n0anoI'm not an expert on DBs (I have some stories about that) but mysql doesn't have triggers?20:36
maoyfunctional-wise, that's the biggest difference i see20:36
maoytriggers can only trigger db actions, not to outside component20:36
sriramhere_triggers can compenseate lack of watches, rt?20:36
sriramhere_which DB  has this kind of watch that can trigger a out-of-db action?20:37
n0anowell, polling (with the right period) is not the worst solution possible but it does mean looking at something like zookeeper becomes more likely20:38
maoythe other practical difference is that zookeeper is designed for HA. But because we rely on mysql on so many places, it doesn't make a huge gain by using zookeeper for just orchestration.20:38
*** deshantm has quit IRC20:38
sriramhere_ok; appears that we are all looking towards Ziad's updates on zookeeper experiment. any other agenda items today?20:39
sriramhere_maoy - r u proposing we move out mysql as persistence store for entire system?20:39
maoynot really20:40
maoythere are mysql addons to make mysql HA20:40
maoyperhaps not as robust and easy to use as zookeeper but acceptable20:40
sriramhere_ok20:41
maoymy impression is that ziad is trying spiffworkflow, not zookeeper?20:42
sriramhere_sorry again. lost track on email. Yes, Ziad is playing woth spiffwf.20:43
n0anoso are we trying to decide between 3 options - 1)zookeeper, 2)spiffworkflow, 3)homegrown with mysql?20:43
mikeypdon't think so.20:44
maoyzookeeper and mysql are for state persistence20:44
mikeypthe workflow engine (spiff or other) will need to store state20:44
maoyspiffworkflow is extra workflow business logic on top.20:45
*** zigo has joined #openstack-meeting20:45
maoymy take is that spiffworkflow is too big, lack of production users, so it may pay off just fine if we write our own specifically for nova20:45
n0anoso there's 2 questions: 1) spiffworkflow or homegrown and then 2) store state in zookeeper or mysql?20:46
sriramhere_and there are two efforts in progress now20:46
maoyn0ano that's my take too.20:46
sriramhere_1) ziad's on spiff20:46
sriramhere_and my mock on swf20:47
n0anoI like competing projects, may the best man win20:47
sriramhere_:)20:47
maoy3 efforts: I'm working on another one based on the BP here:http://wiki.openstack.org/TransactionalTaskManagement20:47
*** joesavak has quit IRC20:47
maoyand i'm using mysql as persistent state for simplicity20:48
sriramhere_maoy - do u want to include this for Folsom session proposal?20:49
maoyhopefully the backend is plugable20:49
maoysure.20:49
n0anopersonally, simple is good (especially since mysql is already there).20:49
maoyagreed20:49
maoysriramhere_: let me know what i need to do to get it into the session proposal. thanks.20:50
sriramhere_maoy - i can update the proposal with link to your BP if its OK with you20:50
maoysounds good20:50
sriramhere_any thing else?20:51
n0anoanything else for today?  I would propose that we finalize the session proposal/agenda next week20:51
maoysecond that20:51
sriramhere_+120:51
n0anopassed by unanimous consent (it is election season :-)20:51
n0anotalk to everyone next week20:52
maoy:)20:52
*** maoy has quit IRC20:52
n0ano#endmeeting20:52
*** openstack changes topic to "Status and Progress (Meeting topic: keystone-meeting)"20:52
openstackMeeting ended Thu Apr  5 20:52:42 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-05-20.04.html20:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-05-20.04.txt20:52
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-05-20.04.log.html20:52
sriramhere_thanks bye20:53
*** donaldngo_hp has joined #openstack-meeting20:57
*** sriramhere_ has quit IRC20:57
*** ryanpetr_ has quit IRC20:58
*** novas0x2a|laptop has joined #openstack-meeting20:59
*** zigo has quit IRC21:16
*** shwetaap has quit IRC21:22
*** markvoelker has quit IRC21:23
*** novas0x2a|laptop has quit IRC21:38
*** shwetaap has joined #openstack-meeting21:41
*** dhellmann has joined #openstack-meeting21:46
*** ryanpetrello has joined #openstack-meeting21:47
*** novas0x2a|laptop has joined #openstack-meeting21:47
*** dwcramer has quit IRC21:50
*** ryanpetrello has quit IRC21:54
*** dendrobates is now known as dendro-afk21:55
*** dendro-afk is now known as dendrobates21:59
*** mikal has quit IRC22:02
*** ayoung has quit IRC22:03
*** dhellmann has quit IRC22:05
*** mdomsch has quit IRC22:12
*** dhellmann has joined #openstack-meeting22:18
*** dhellmann has quit IRC22:28
*** shwetaap_ has joined #openstack-meeting22:29
*** shwetaap has quit IRC22:30
*** mattray has quit IRC22:31
*** shwetaap_ has quit IRC22:33
*** shwetaap has joined #openstack-meeting22:34
*** shwetaap has quit IRC22:37
*** davlaps has quit IRC22:42
*** davlaps has joined #openstack-meeting22:46
*** davlaps has quit IRC22:48
*** kindaopsdevy_ has quit IRC22:49
*** Yak-n-Yeti has quit IRC22:49
*** pvo has quit IRC22:54
*** heckj has quit IRC22:56
*** mikeyp has left #openstack-meeting22:58
*** lloydde has quit IRC23:08
*** dtroyer is now known as dtroyer_zzz23:12
*** donaldngo_hp has quit IRC23:13
*** rnirmal has quit IRC23:14
*** pvo has joined #openstack-meeting23:18
*** sleepsonthefloor is now known as sleepsonzzz23:25
*** nati has quit IRC23:27
*** dtroyer_zzz is now known as dtroyer23:28
*** dtroyer is now known as dtroyer_zzz23:34
*** lloydde has joined #openstack-meeting23:40
*** Yak-n-Yeti has joined #openstack-meeting23:52
*** deshantm has joined #openstack-meeting23:53
*** pvo has quit IRC23:54
*** nati has joined #openstack-meeting23:56

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