Tuesday, 2012-01-03

*** jog0 has joined #openstack-meeting01:25
*** jog0 has left #openstack-meeting01:25
*** davlap has quit IRC02:57
*** nati2 has joined #openstack-meeting03:06
*** shang_ has quit IRC03:36
*** shang_ has joined #openstack-meeting03:36
*** shang_ has quit IRC03:52
*** nati2 has quit IRC03:53
*** shang_ has joined #openstack-meeting04:00
*** cmagina has joined #openstack-meeting04:09
*** byeager has quit IRC04:09
*** cmagina_ has quit IRC04:10
*** deshantm has joined #openstack-meeting04:12
*** shang_ has quit IRC04:16
*** shang_ has joined #openstack-meeting04:16
*** shang_ is now known as shang04:20
*** deshantm has quit IRC05:01
*** nati2 has joined #openstack-meeting05:06
*** nati2 has quit IRC05:10
*** deshantm has joined #openstack-meeting05:14
*** nati2 has joined #openstack-meeting05:48
*** shang has quit IRC06:05
*** shang has joined #openstack-meeting06:19
*** nati2_ has joined #openstack-meeting06:33
*** nati2 has quit IRC06:35
*** shang has quit IRC06:44
*** shang has joined #openstack-meeting06:58
*** lloydde has quit IRC07:01
*** nati2_ has quit IRC07:05
*** nati2 has joined #openstack-meeting07:07
*** deshantm has quit IRC07:09
*** nati2_ has joined #openstack-meeting07:17
*** nati2 has quit IRC07:18
*** nati2 has joined #openstack-meeting07:19
*** nati2_ has quit IRC07:21
*** shang has quit IRC07:39
*** shang has joined #openstack-meeting07:53
*** nati2 has quit IRC08:15
*** nati2 has joined #openstack-meeting08:17
*** nati2 has quit IRC08:21
*** derekh has joined #openstack-meeting09:03
*** zigo has joined #openstack-meeting09:26
*** shang has quit IRC09:34
*** shang has joined #openstack-meeting09:57
*** derekh has quit IRC10:54
*** derekh has joined #openstack-meeting11:04
*** GheRivero has quit IRC11:54
*** zigo has quit IRC11:57
*** GheRivero has joined #openstack-meeting12:09
*** markvoelker has joined #openstack-meeting12:25
*** reed has quit IRC12:57
*** dayou has joined #openstack-meeting13:13
*** dolphm has joined #openstack-meeting13:26
*** hggdh has quit IRC13:31
*** dolphm has quit IRC13:32
*** hggdh has joined #openstack-meeting13:35
*** dolphm has joined #openstack-meeting13:37
*** dprince has joined #openstack-meeting14:02
*** deshantm has joined #openstack-meeting14:03
*** dolphm has quit IRC14:14
*** sandywalsh has joined #openstack-meeting14:22
*** dolphm has joined #openstack-meeting14:23
*** lzyeval has joined #openstack-meeting15:01
*** rnirmal has joined #openstack-meeting15:05
*** mdomsch has joined #openstack-meeting15:14
*** troytoman-away is now known as troytoman15:37
*** dayou is now known as help15:48
*** help is now known as dayou15:48
*** dolphm has quit IRC15:56
*** AlanClark has joined #openstack-meeting16:00
*** troytoman is now known as troytoman-away16:02
*** lloydde has joined #openstack-meeting16:27
*** dolphm has joined #openstack-meeting16:32
*** dolphm_ has joined #openstack-meeting16:37
*** dolphm has quit IRC16:40
*** nati2 has joined #openstack-meeting16:44
*** dprince has quit IRC16:51
*** hggdh has quit IRC16:59
*** dprince has joined #openstack-meeting17:08
*** oubiwann has joined #openstack-meeting17:09
*** byeager has joined #openstack-meeting17:12
*** zigo has joined #openstack-meeting17:13
*** jakedahn has joined #openstack-meeting17:30
*** andrewbogott has joined #openstack-meeting17:31
*** dolphm has joined #openstack-meeting17:36
*** dolphm_ has quit IRC17:40
*** nati2_ has joined #openstack-meeting17:40
*** ayoung has joined #openstack-meeting17:41
*** jog0 has joined #openstack-meeting17:41
*** nati2 has quit IRC17:43
*** dolphm_ has joined #openstack-meeting17:43
*** jk0 has joined #openstack-meeting17:46
*** dolphm has quit IRC17:46
*** zns has joined #openstack-meeting17:49
*** derekh has quit IRC17:49
*** dolphm_ has quit IRC17:57
*** jdurgin has joined #openstack-meeting17:57
*** zns has quit IRC17:57
*** dolphm has joined #openstack-meeting18:00
*** zns has joined #openstack-meeting18:01
znsAnyone here for Keystone?18:02
ayoungzns, yes18:02
dolphmyep18:02
zns#start-meeting Keystone Team Meeting18:03
znsOK. Starting meeting.18:03
znsAgenda:18:03
zns- Update on E3 progress18:04
zns- Open questions18:04
zns#topic Update on E318:04
znshttps://launchpad.net/keystone/+milestone/essex-3 contains all blueprints and bugs for E3.18:04
znsWe've made good progress in the last two weeks with almost all blueprints implemented or in progress.18:05
znsWe've updated many blueprints and bugs (just now) with new assignees who have taken on E3 work.18:05
znsNo update from HP on their blueprints yet.18:06
znsayoung: anotheresse had mentioned seeing if we can get some help on IPv6, EC2, and some other features. Would you know anything about that? Or have status?18:06
*** dolphm has quit IRC18:06
*** dolphm has joined #openstack-meeting18:07
ayoungzns, I can probably help on IPv618:07
*** dolphm_ has joined #openstack-meeting18:07
znsThat would be awesome! I checked on https://bugs.launchpad.net/nova/+bug/850443 and it looked unsimple...18:07
uvirtbotLaunchpad bug 850443 in nova "Nova API does not listen on IPv6" [Undecided,New]18:07
ayoungzns, yeah,  I have some IPv6 background.   That should not be that bad.18:08
znsayoung: need anything from me (or anyone on the team) to get that done or should we look for you to pick up the bug?18:08
ayoungzns, I can tak e it.  If it really is eventlet code changes I'll come back around and ask for guidance on the process there18:09
zns#action ayoung to pick up IPv6 for Keystone18:09
znsGreat! Thanks18:09
znsAnything else on progress/status?18:09
zns#topic Open Questions18:10
znsAny questions for Keystone team? The floor is open.18:10
ayoungzns, so...it seems to me the HP proposal on Domains  is overlapping with the definition of Tenancy.  Why the split?18:11
znsWhat HP is targeting is functionality that appears more like multiple instances of Keystone running in the same process. The idea is to be able to have multiple 'domain' admins that can manage/CRUD tenants and global roles within their domain and be isolated from and not impact each other.18:12
znsYou "could" implement it by running multiple instances of Keystone, but not really by managing multiple tenants. It also makes federation easier by tying a federated directory to a domain. All valid use cases that are hard to address without a higher-level concept like domains.18:14
znsDid I answer your question? If not, tell me more about where you see the overlap is...18:14
ayoungzns, still processing18:14
ayoungI'm coming from working with FreeIPA,  and, after looking at Keystone,  I wrote up a multitenacy  feature set for that there...  Trying to reconcile what I understand18:15
ayoungSo,  it seems to me that Tenancy is the cloud administrator view of things (top level) and Domain is really delegating the mgmt of the Tenancy to someone in the tenants organization?\18:16
*** lloydde has quit IRC18:16
znsWe did discuss in Boston about tying Domains to DNS domains (kind of how Kerberos and Active Directory do). So the concepts are similar.18:16
ayoungzns  the thing from the proposal that caught my attention was that Domains contained tenants,  and it seems to me that  the revers should be true18:18
znsYes….  or delegating 'partial' tenancy to a reseller, for example.18:18
ayoungzns, yeah...the client of the reseller get a subset of the domains allocated to the reseller18:19
znsThe use case is, I (say Rackspace, a cloud operator) want to allow a reseller of mine to create and manage their own tenants. I do that by creating a domain for them inwhich they can create tenants for their customers.18:19
znsHow can I delegate the CRUD of tenants if domains are contained in tenants?18:20
zns* is reading about Free IPA meanwhile *18:20
zns* and disappointed it about isn't free beer… *18:21
ayoungzns, specifically http://freeipa.org/page/Multitenancy18:21
ayoungzns, it is all about free beer18:21
*** gyee has joined #openstack-meeting18:21
zns* reading *18:22
ayoungso the other question I have is what is going to enforce RBAC  in a keystone deploy?  in IPA  we have the benefit of working with SSSD on the managed hosts18:23
znsMaybe the confusion is about where the multi-tenancy is happening. Tenants in Keystone support an operator servicing individual tenants, but there is only one operator. Domains is about supporting multiple operators (multi-tenancy at the operator level).18:23
ayoungFreeIPA calls is HBAC18:23
znsHBAC?18:24
ayoungHost based18:24
znsWhere host is the operator? A 'hoster' of multiple tenants?18:24
ayoungAccess is based on the host you log in from,  you log in to,  and what groups you belong to\18:25
ayoungzns, IPA is not strictly a cloud solution....think more like ActiveDirectory,  but for Linux/Unix18:25
znsSo host (in IPA terminology) is mapped to domain (in the Keystone blueprint terminology)?18:25
ayoungzns, in IPA,  there are Hosts,  which are machines,  and there is DNS management.  There is a relationship between DNS hosts,  but not a 1-118:26
ayoung1 to 118:26
ayoungThink "hostname"  from the command line versus  nslookup18:26
znsOh, OK. I think this is all about getting on the same taxonomy. Do we need to add more meet to the blueprint to help with that?18:27
ayoungzns  probably...18:27
ayoungI'm stil jump starting my brain from our Shutdown.18:27
znsHow would you like to proceed? Should we schedule some time to discuss?18:28
ayoungI think that the term Domain  might not be the best choice,  as we will want to talk about  DNS18:28
znsRealm?18:28
ayoungzns, I like tenant as an abstraction18:28
ayoungI think we just need to be more specific about what we are talking about18:28
ayoungTenants to me are top level groups18:29
ayoungOne tenant can't see into another tenent18:29
ayounga Tenant might host a slew of DNS domains18:29
ayoungand now,  we have subtenancy18:29
ayoungbut I think the current terms still work18:29
znsTenants are top-level constructs in Nova, Glance, etc… intentionally. And domains should be transparent to those services. Domain, as proposed, is a Keystone-only construct to support multiple administrative namespaces in Keystone…18:30
ayoungnamespaces.18:31
*** lloydde has joined #openstack-meeting18:31
zns… so domains won't need to be implemented in Nova, Glance, Swift, etc…  but they could at some point be used by the schedulers.18:31
ayoungzns, seems to me that domains are really a way to specify roles for tenants.  I don't like adding new names for old concepts.  I'm having trouble convincing myself that they are really separate things18:32
znsAs for RBAC, your question above, what RBAC are you asking about? RBAC for OpenStack in genenral (who can create servers) or RBAC to control who has access to which domain in Keystone?18:32
ayoungzns, heh..caught me out...I'm still coming up to speed on it.  I didn't realize there was a distinction.  In IPA,  we distinguish between things that are enro4rced by the LDAP server Accesds Controls and the things that have to bemanaged exteranlly.  I assume the same type of breakdown here18:33
ayoungI was mapping HBAC to the Keystone RBAC18:34
znsSo you're saying that you can achieve the separation that domains provides by assigning roles to tenants?18:34
ayoungzns, yes.18:34
ayoungzns, think about standard Unix groups18:34
ayoungthe major drawback that the Unix implementation had was delegation18:35
ayoungThe ops should be:  create group,  manage members of group18:35
ayoungto do both,  you traditionally need to be root.18:35
znsYes, you could do that.  There would be some compromises. How do you manage multiple domains, how can you tie domains back to different backends or directories, how do you separate global roles between operators, etc...18:36
ayoungSo  if group maps to tenant,  the Cloud Provider creates tenants,  including an admin user for tenant,  and allows them to manage the member ship there18:36
ayoungimagine if the unix model were this18:36
ayoungeach groups is a file in /etc/groups.d18:36
ayoungroot creates a new group by creating a new file,  and that maps to the group name18:37
znsWho is the cloud provider in your use case? The top-level provider (Rackspace) or a reseller?18:37
ayoungzns, well,  if tenants can be nested...it could be both18:37
ayoungwe need a mechanism to delegate down18:37
ayoungso say DNS is managed by rackspace18:38
ayoungthe reseller then  buys  myhostname.edu18:38
znsDomains addresses a form of tenant nesting.18:38
ayoungand  so at the rackspaces level,  the tenant is the reseller18:38
ayoungzns, yes,  I see that.  Just not sure we benefit from a new term18:38
ayoungAnyway,  I've hijacked the meeting enough.  I understand the issue now and will comment on the ticket18:39
ayoungblueprint18:39
znsOK. Sounds good. Might be a good ML topic...18:40
ayoungzns, one last point...FreeIPA supports nested groups.  Tenants are like that,  but without visibility18:40
ayoungif you are a member of a subgroup,  in IPA you gain member ship in the parent group....18:41
znsThe good thing about the blueprint is it is an extension. Opt-in or out with your configuration. If they build it well and it gets adopted then we're good to go, if not, it never was in the core API….18:41
znsvisibility?18:41
ayoungzns, thanks for clarifying.18:41
ayoungzns, visibility18:41
ayoungthe idea that a member of a group knows who the other members are18:41
*** dolphm_ has quit IRC18:41
ayoungtenants should probably not be able to enumerate the other tenants18:41
ayoungright?18:41
znsright18:41
ayoungzns, what other features beside IPv6 and EC2 needed attention?18:43
znsNote also that the Keystone API spec does not imply any relationship between identities and tenants. Tenant is grouping of IaaS resources more than it is a grouping of identities. The spec then allows identities to be assigned roles on hose resources...18:43
znsclients.18:44
ayoungzns, https://blueprints.launchpad.net/keystone/+spec/keystone-client  ?18:45
znsWe've just moved python-keystoneclient to Gerrit. We need to figure out how best to make it the defacto client for Keystone. Probably by importing it as a library in middlewares, novaclient, etc….18:45
znsYes. And http://wiki.openstack.org/CLIAuth18:45
ayoungzns, so there is the  openstack common effort18:46
ayoungseems CLI belongs underthat18:46
ayoungif not the specific APIs,  then at least the enumeration and marshalling mechanisms18:47
*** dolphm has quit IRC18:47
znsJesse knows more than I do about that ass he has been driving it. But it seems like it. Gettgin openstack-common going would be great.18:47
znsayoung, our time is up. Hit me up if you want to discuss more. My calendar is open at 4PM central today..18:47
zns#end-meeting18:47
zns#endmeeting18:47
znsjust noticed I may not have started the meeting correctly. Anyway...18:47
*** notmyname has quit IRC18:50
*** notmyname has joined #openstack-meeting18:50
ayoungzns, is this the first meeting of the new year?  http://eavesdrop.openstack.org/meetings/openstack-meeting/18:51
*** zigo has quit IRC18:51
*** zigo has joined #openstack-meeting18:51
*** liemmn has joined #openstack-meeting18:53
*** mattray has joined #openstack-meeting18:55
*** dprince has quit IRC18:56
mtaylormorning all19:00
jeblairhiya19:01
mtayloranybody wanna chat about CI stuff?19:01
*** davlap has joined #openstack-meeting19:01
notmynamemtaylor: you're working on my bug report? ;-)19:01
mtaylornotmyname: yup19:01
*** hggdh has joined #openstack-meeting19:01
notmynameyay :-)19:01
mtaylornotmyname: sadly, work on that brought up the need for unittests, which is a whole other can of worms19:01
notmynameone other thought...if git-review is managed by git-review, how is one supposed to submit patches if git-review is broken?19:02
jeblairnotmyname: git review is managed by gerrit19:02
mtaylornotmyname: well, it's managed by gerrit19:02
jeblairit's fairly simple to use gerrit without git-review19:03
mtaylornotmyname: so if it's monumentally broken, you can always just git push to gerrit19:03
jeblairespecially if a repo is already set up.19:03
mtaylorto submit a review19:03
* mtaylor and jeblair are saying the same thing at the same time. :)19:03
notmynameya, ok. that makes sense. those things would need to be documented somewhere (rather than "use git-review -v")19:03
notmynamenot saying they aren't...19:03
mtayloragree19:04
notmynameI havent' spent a long time looking at it, just something that struck me as funny when reading the emails19:04
jeblairnotmyname: a workaround for your bug is not to run "git review -s".  the case where you run git review for the first time on a new repo with a committed change is correctly handled currently.19:04
*** scottsanchez has quit IRC19:04
jeblairhttp://wiki.openstack.org/GerritJenkinsGithub#Pushing_Changes_from_Git19:04
jeblairnotmyname: ^ there's the docs on manually working with gerrit19:05
*** nati2_ has quit IRC19:05
mtaylorI suppose this could technically be part of the meeting19:05
mtaylor#startmeeting19:05
openstackMeeting started Tue Jan  3 19:05:19 2012 UTC.  The chair is mtaylor. Information about MeetBot at http://wiki.debian.org/MeetBot.19:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.19:05
notmynamejeblair: thanks19:05
notmynamemtaylor: meh. that's all I have ;-)19:05
mtaylor#link http://wiki.openstack.org/GerritJenkinsGithub#Pushing_Changes_from_Git19:05
mtaylorjeblair: I think you're right about assert_one_change, btw19:06
mtaylorjeblair: I tried something else, and that doesn't work either19:06
jeblairso, what's our current topic? :)19:09
mtaylorwell, I suppose we could chat about the stuff we did over the break19:10
mtayloris anyone here other than you and I though?19:11
jeblairwell, then, for the record, i'd like to talk about trunk gating for a minute.19:12
mtaylorawesome19:12
mtaylor#topic trunk gating19:12
*** openstack changes topic to "trunk gating"19:12
jeblairso i've actually set the devstack trunk gating job to run on all branches now19:12
jeblairit just hasn't run since i've done that because no-one has approved anything yet.  :/19:12
jeblairit's also set up to archive syslogs from the machines19:13
jeblairbut there's a bug in devstack that causes keystone to fail to start when sysloging19:13
mtaylorawesome19:13
mtaylorhave we filed the keystone devstack syslog bug yet?19:14
jeblairi have a patch in review for that.  as soon as it's added, we can turn syslog back on for the job19:14
jeblairand, yes, there's a bug too.  let me dig it up19:14
jeblair#link https://bugs.launchpad.net/devstack/+bug/91043619:14
uvirtbotLaunchpad bug 910436 in devstack "keystone (master) fails to start with syslog on" [Undecided,In progress]19:15
*** dendrobates has joined #openstack-meeting19:15
jeblair#link https://review.openstack.org/#change,272019:15
jeblairhopefully that will get merged soon, and then i believe devs should have a lot of info available to them in the case that the integration job errors out.19:15
jeblairthat's about it for that.19:16
mtaylorexcellent19:16
mtaylordid you see markmc's email on the subject earlier today/19:17
mtaylor?19:17
*** scottsanchez has joined #openstack-meeting19:17
jeblairyes, i think ttx replied to it; i don't have much more to add other than i can go into detail about the problems and our solutions...19:17
*** Gordonz has joined #openstack-meeting19:18
mtaylornope, I think that's fine - I just wanted to mention it while we were on the subject19:18
mtaylorI suppose...19:18
mtaylor#topic using tox for virtualenvs19:18
*** openstack changes topic to "using tox for virtualenvs"19:18
mtaylorI got tox.ini files submitted for most of the projects, although there are a couple of 2.6 bugs out there19:19
mtaylornova had the m2crypto issues, but pointing it at a working repo for m2crypto seems to have a tox build working for it19:20
mtaylorand swift doesn't have a venv-based setup at all19:20
mtaylorso I haven't really even begun to think about that one yet (and think I'll hold off on submitting a patch there until I've got something final and clean - no need to add half-baked things)19:21
mtaylortox itself needs a patch to be used with our venv pre-caching on jenkins, which I have working and am working through feedback from upstream on19:21
*** patelna has joined #openstack-meeting19:21
mtaylorat which point we'll need to make a version of the jenkins venv scripts that pre-generate the venv using tox19:22
mtayloranyway - that's pretty much where that is19:22
jeblairmtaylor: have a link for the upstream work?19:22
mtayloryup. one sec...19:22
mtaylor#link https://bitbucket.org/mordred/relocate19:22
mtaylorit's being done in a mercurial patch series at the moment (lemme tell you how much fun that was to learn about)19:23
mtaylorso actually, if you want to look at it:19:23
mtaylor#link https://bitbucket.org/mordred/relocate/qseries19:23
mtayloris probably a better choice19:23
mtaylorat the moment19:23
jeblairhow does upstream feedback work there?19:24
mtaylorhttps://bitbucket.org/hpk42/tox/pull-request/9/relocatable-support-without-the-json19:24
mtaylorthat's where the conversation is going on19:24
jeblaircool, thanks!19:24
mtayloras with many things I write, I've hit the fun place where I now get to figure out how to test it19:25
mtaylorwhich is for _this_ patch to tox, going to be hard, as the test framework existing doesn't sit at a place in the stack where one is pointing at a particular tox venv19:25
mtaylorso moving one means I've got to figure out a new set of fixtures. yay19:26
* mtaylor cries a little19:26
*** mattray has quit IRC19:26
*** mattray has joined #openstack-meeting19:26
*** mattray has joined #openstack-meeting19:26
mtayloron the other hand, when it lands there's a bunch of little hacky stuff in our jenkins jobs that can go away, so that'll be nice19:27
jeblairyes, sounds fun!19:27
mtaylor#topic open discussion19:27
*** openstack changes topic to "open discussion"19:27
mtayloranything else from anybody/19:27
jeblairnegative19:27
*** yogirackspace has joined #openstack-meeting19:29
mtaylorawesome19:30
mtaylor#endmeeting19:30
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"19:30
openstackMeeting ended Tue Jan  3 19:30:39 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-03-19.05.html19:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-03-19.05.txt19:30
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-03-19.05.log.html19:30
*** ecarlin has joined #openstack-meeting19:47
*** dendrobates is now known as dendro-afk19:54
*** ecarlin has quit IRC19:55
*** troytoman-away is now known as troytoman19:56
*** dendro-afk is now known as dendrobates19:58
ttx.o020:00
*** ewanmellor has joined #openstack-meeting20:00
ewanmellorHey hey hey!20:01
ttxewanmellor: yo20:01
ewanmellorAre we going to PPB today?20:01
ttxlooks like only the two of us so far20:01
*** dolphm has joined #openstack-meeting20:01
jk0o/20:01
ttxewanmellor: I have a minor point on the agenda if we can get quorum, no news from jbryce today20:02
mtayloro/20:02
ttx4/1420:03
ttxLooks like we won't have quorum today.20:05
znsHere! Sorry I'm late.20:05
ttx5/1420:06
*** ecarlin has joined #openstack-meeting20:06
notmynamehi20:07
ttx6/1420:07
*** ecarlin_ has joined #openstack-meeting20:07
* ttx reads http://wiki.openstack.org/Governance/Model: "PPB members are expected to participate in at least 75% of these meetings during their term"20:08
ttxbut there are no rules for when that's not the case :)20:09
*** ecarlin_ has joined #openstack-meeting20:09
*** jmckenty has joined #openstack-meeting20:09
notmyname"or else..."20:09
*** lloydde has quit IRC20:10
*** ecarlin has quit IRC20:10
*** ecarlin_ is now known as ecarlin20:10
ttxjmckenty makes 7/14, but without chair we need one more :)20:11
pvoo/20:11
ewanmellorYey!20:11
pvosorry, double meetings today20:11
ewanmellorpvo is the weeener!20:11
pvowhat'd in win?20:12
ttx8/1420:12
pvoI win..20:12
medberrya meeting.20:12
ttxpvo: quorum20:12
*** andrewbogott has quit IRC20:12
jmckentyboom20:12
ttxDo all present members wish to have a short meeting with the one point on the agenda ?20:12
pvo+120:12
*** andrewbogott has joined #openstack-meeting20:13
zns+1. What's on the agenda?20:13
pvoMoving the weekly PPBs to montly? :)20:13
ttxSpring election process (ttx)20:13
pvomonthly… can't type. Out of practice.20:13
ttxok, I'll start it20:13
ttx#startmeeting20:13
openstackMeeting started Tue Jan  3 20:13:58 2012 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:13
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.20:14
ttxOnly item on http://wiki.openstack.org/Governance/PPB:20:14
ttx#topic Spring election process20:14
*** openstack changes topic to "Spring election process"20:14
ttxI'd like to quickly talk about the next round of PPB elections.20:14
ttxUnless something happened that I don't know about, it looks like the foundation won't be set up by March...20:14
ttxSo we'll need to elect replacements for 5 PTLs and 2 community members.20:14
ttxWe need them elected at least one month before the next design summit (April 16), and roughly 6 months after the last election (September 4).20:15
ttxSo I propose the following dates:20:15
ttxNomination: February 16 -> Sunday, February 26, 23:59 UTC20:15
ttxElection: February 28 -> Thursday, March 8, 23:59 UTC20:15
ttxAnd have Stefano Maffulli (reed) serving as the election official20:16
ttxAny objection ?20:16
ttxor comment ?20:16
pvothat seems fine20:16
znssounds good20:17
jk0+120:17
ttxOk, I'll pass the baby to reed with the dates :)20:17
mtaylor+120:17
*** blamar has quit IRC20:18
jmckentyum20:18
ttxjmckenty: um um ?20:18
jmckentyas long as stefano isn't running20:18
ttxjmckenty: obviously. I'll ask him. Anyone else you would suggest ?20:18
*** jmckenty has quit IRC20:18
ttx(in case Steafno wants to be free to run) ?20:18
*** jmckenty has joined #openstack-meeting20:20
ttx<ttx> jmckenty: obviously. I'll ask him. Anyone else you would suggest ?20:20
ttx<ttx> (in case Steafno wants to be free to run) ?20:20
jmckentylloyd dewolf would be happy to do it20:20
ttxjmckenty: noted. I guess we can have two election officials anyway20:21
ttxanything more on that subject ?20:22
ttx#action ttx to pass the dates to Stefano and Lloyd so that they organize the election20:23
ttx#topic Open discussion20:23
*** openstack changes topic to "Open discussion"20:23
ttxAnything else ?20:23
pvoAre these weekly meetings needed or can we move them to monthly?20:23
pvoor as needed?20:24
mtaylorseems like they're mostly running as-needed at the moment anyway20:24
sorenAre there any updates at all on the foundation front?20:24
jmckentyI have a hunch they'll ramp up as we get towards foundation news20:24
pvoI show up every week (or most every week) only to have them cancelled last minute20:24
jk0+1 ^20:24
mtaylorpvo: ++20:24
zns++20:24
ttxpvo: I think one issue is that we are a bit stalled on the foundation front apparently, which leaves the PPB is a bit of an awkward situation20:25
ttxin* a bit20:25
jmckentyLet's assume that the foundation preserves the existing PPB structure20:25
pvottx: sure. I think it'll ramp up as the foundation moves forward. If it isn't, then there isn't much to meet on.20:25
ewanmellorI think it's reasonable for us to ask jbryce to cancel with advanced notice, not just at the last minute.20:25
ttxpvo: maybe we should mandate that the PPB meeting is confirmed on the poc list at least one day before20:25
jmckentyttx ++20:26
mtaylor++20:26
znsewanmellor: yes!20:26
jk0that sounds reasonable +120:26
ttxbecause showing up to see it cancelled is not exactly fun on this side of the Atlantic20:26
pvoI would almost assume cancelled unless an agenda is sent out the day before20:26
ttx+120:26
pvoI guess that is the same as what you said, ttx.20:26
ttxyes. Must be confirmed at least before Monday 2000 UTC20:27
pvo+120:27
ttxWe could also say "confirmed on Monday" but that's a bit unclear.20:27
ttx#info PPB meetings should happen only if agenda is confirmed on the -poc list at least one day before the meeting (Monday, 2000 UTC)20:28
*** dprince has joined #openstack-meeting20:29
ttxok, anything else ?20:29
znsAny activity, news on openstack-common?20:29
znsWill iot be a project? Who drives it?20:29
znsit20:29
*** sleepsonthefloo has joined #openstack-meeting20:30
jmckentyzns: that's been answered a few times20:30
jmckentyand voted on by the ppb20:30
ttxI think we said "yes, with collegial PTL leadership"20:30
znsSo we (PTLs) drive it? OK. Thanks.20:30
mtayloryes. I need to move it in to gerrit, actually... sorry, I thought I'd done that part already. darned holidays.20:31
ttxanything else before we close ?20:31
znsmtaylor: that would be good. The code needs cobwebs removed from it and moving it to Gerrit 'feels' like a good revival step.20:32
*** lloydde has joined #openstack-meeting20:32
mtayloryeah. it also makes it a little more stable for other projects to actually depend on20:32
ttxok then20:33
ttx#endmeeting20:33
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"20:33
openstackMeeting ended Tue Jan  3 20:33:15 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:33
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-03-20.13.html20:33
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-03-20.13.txt20:33
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-03-20.13.log.html20:33
*** ewanmellor has quit IRC20:33
ttxProject and Release status meeting starts in 27min.20:33
*** jwalcik has joined #openstack-meeting20:47
*** ecarlin_ has joined #openstack-meeting20:50
*** vladimir3p has joined #openstack-meeting20:50
*** tylesmit has joined #openstack-meeting20:50
*** ecarlin has quit IRC20:51
*** ecarlin_ is now known as ecarlin20:51
*** vish1 is now known as vishy20:55
*** Gordonz has quit IRC20:57
*** markmc has joined #openstack-meeting20:57
ttxo/20:59
carlpo/20:59
znso/20:59
sorenGreetings.21:00
ttxnotmyname, jaypipes, vishy, devcamcar: around ?21:00
*** edconzel has joined #openstack-meeting21:00
*** wwkeyboard has joined #openstack-meeting21:00
notmynamehere21:00
*** bhall has joined #openstack-meeting21:01
*** jdg has joined #openstack-meeting21:01
ttxHm, looks like Jay is not around. Anyone feeling up to represent Glance ?21:01
ttxour star substitute is not around either.21:02
ttxvishy, devcamcar: ?21:02
vishyo/21:02
zigohi21:02
ttxok, let's start and see what we can do21:03
ttx#startmeeting21:03
openstackMeeting started Tue Jan  3 21:03:09 2012 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.21:03
ttxHappy new year everyone !21:03
ttxEnough holiday slacking, now let's get back to work :)21:03
ttxToday's agenda: http://wiki.openstack.org/Meetings/ProjectMeeting21:03
ttx#topic Actions from previous meeting21:03
*** openstack changes topic to "Actions from previous meeting"21:03
ttx* zns the raise a thread on the ML about RBAC potentially being deferred to F21:03
*** Vek has joined #openstack-meeting21:04
ttxML thread at https://lists.launchpad.net/openstack/msg06267.html21:04
ttxNo comment there...21:04
*** Gordonz has joined #openstack-meeting21:04
znsNope. It's a done deal.21:04
zigottx: May I add Kronos status to the agenda?21:04
ttxnotmyname, vishy, devcamcar: Deos that mean you don't have any issue with that ?21:04
vishyno problem21:04
ttxzigo: I'll keep time to talk about that in open discussion.21:04
zigoOk.21:05
ttx* ttx to discuss options for getting a sane list of reviews with CI guys21:05
*** mjfork has joined #openstack-meeting21:05
ttxSo the CI team wants to get a usable review list in Gerrit directly.21:05
ttxSo I filed a bug to track this at: https://bugs.launchpad.net/openstack-ci/+bug/90776421:05
uvirtbotLaunchpad bug 907764 in openstack-ci "A usable list of reviews" [Wishlist,Confirmed]21:05
ttx* markwash to raise future of Trusted Computing bp on ML to get nova-core consensus21:05
ttxDone today @ https://lists.launchpad.net/openstack/msg06466.html21:05
ttx#topic Keystone status21:06
*** openstack changes topic to "Keystone status"21:06
ttxzns: o/21:06
ttxzns: Can you confirm that you intend to use essex-3 as a FeatureFreeze ?21:06
znsGood progress. https://launchpad.net/keystone/+milestone/essex-3 is updated as of this AM.21:06
znsttx: confirmed.21:06
ttx#info Last feature milestone for Keystone will be Essex-321:06
ttxSo that leaves 3 weeks for Essex keystone features.21:07
ttxzns: About https://blueprints.launchpad.net/keystone/+spec/service-endpoint-location21:07
znsA few of them are listed as bugs in https://launchpad.net/keystone/+milestone/essex-3, BTW. IPv6, for example.21:07
ttxDid you get any news from HP ? Is this still planned for Essex-3 ?21:07
znsttx: no update from HP on that.21:07
ttxzns: could someone take an action of contacting them ? I can, if you tell me who I should ask21:08
znsI just pinged them.21:08
mtaylorttx: need me to poke someone?21:08
mtaylorok. good21:08
ttxzns: ok21:08
ttxzns: What's the priority/status of:21:08
ttxhttps://blueprints.launchpad.net/keystone/+spec/keystone-internal-authorization21:08
znsMedium21:08
ttxand "Not started" ?21:09
zns… same priority we have for the other refactoring blueprints.21:09
znsYes, we just added it this AM. Will start this week...21:09
* ttx updates21:09
ttxzns: Anything else ?21:09
znsNo21:10
ttxQuestions for Keystone ?21:10
*** Gordonz has quit IRC21:10
Vekzns: check my comment on bug 85688721:10
uvirtbotLaunchpad bug 856887 in keystone "Keystone cannot listen on IPv6" [High,Confirmed] https://launchpad.net/bugs/85688721:10
*** Gordonz has joined #openstack-meeting21:10
znsVek: saw that. ayoung has volunteered to help us with that.21:11
Vekthat, by the way, is going to affect pretty much every openstack project, unless they bypass eventlet's built-in name service resolution.21:11
Vekexcellent.21:11
ttx#topic Swift status21:11
*** openstack changes topic to "Swift status"21:11
ttxnotmyname: o/21:11
notmynamehi21:12
ttxnotmyname: any news / sight of Swift 1.4.5 yet ?21:12
notmynameI've been getting caught up (first day back in the office)21:12
notmynamewe've been getting reviews caught up21:12
*** ecarlin has quit IRC21:12
notmynameand I'd like to talk to our team about when we feel a release is warranted21:13
notmynameI hope to have a better answer next week21:13
ttxok21:13
ttxnotmyname: Anything else ?21:13
notmynameI don't think so21:14
ttxQuestions on Swift ?21:14
ttxLet's skip Glance for the moment, hopefully Jay will join or someone else will volunteer to represent Glance21:15
ttx#topic Nova status21:15
*** openstack changes topic to "Nova status"21:15
ttxvishy: hey hey21:15
ttxvishy: Last week bcwaldon hinted that Nova would use essex-3 as feature freeze. Can you confirm ?21:15
ttxhm, that should read "last year"21:16
*** markwash has joined #openstack-meeting21:16
vishyoops sorry21:17
vishy:)21:17
vishyconfirmed21:17
ttxIs it a "disruptive work" freeze, a "major feature" freeze, or a "all features" freeze ?21:17
vishyI'd like to call it a soft feature freeze21:17
vishyno public api changes ore major changes21:17
vishycleanup features21:17
vishyadmin apis etc21:17
vishyi think are fine in e421:17
vishya totally isolated extension seems fine as well21:18
ttx#info Nova will start a "soft feature freeze" at E3 (no public api changes or major changes)21:18
ttxvishy: and a hard feature freeze at E4 ?21:18
vishyabsolutely21:18
ttxsounds good.21:18
ttx#link https://launchpad.net/nova/+milestone/essex-321:19
ttxI'd like to review the status of the Essential stuff:21:19
ttxhttps://blueprints.launchpad.net/nova/+spec/volume-type-scheduler (vladimir3p)21:19
ttxvladimir3p: not started ?21:19
ttxhttps://blueprints.launchpad.net/nova/+spec/separate-nova-volumeapi (sleepsonthefloor)21:20
ttxsleepsonthefloo: just started ?21:20
ttxhttps://blueprints.launchpad.net/nova/+spec/interim-nova-authz-service (vishy)21:20
ttxvishy: Good progress, though I can't see any code proposed yet ?21:20
*** danwent has joined #openstack-meeting21:20
vishyI have code21:20
vishyworking on docs today21:20
vishyproposing21:20
sleepsonthefloottx - yes, just started21:20
vishynot sure what happened with the volume type scheduler21:21
ttxsleepsonthefloo: on track to meet the Essex-3 deadline ? (in 3 weeks)21:21
vishyi will try and get in touch with vladimir3p21:21
ttxvishy: yeah. essential not started stuff makes me nervous.21:21
sleepsonthefloottx - yes21:21
vishyttx: i think it is started21:22
ttx#action vishy to ping vladimir3p about volume-type-scheduler status21:22
vishybut i will verify21:22
ttxvishy: There are also a few blueprints that were proposed for E3/E4 that you might want to confirm:21:22
ttxEssex-3:21:22
ttxhttps://blueprints.launchpad.net/nova/+spec/multiple-floating-ip-ranges21:22
ttxhttps://blueprints.launchpad.net/nova/+spec/nova-parity-floating21:22
ttxhttps://blueprints.launchpad.net/nova/+spec/scaling-zones21:22
ttxEssex-4:21:22
ttxhttps://blueprints.launchpad.net/nova/+spec/adaptive-network-cfg-injection21:22
ttxhttps://blueprints.launchpad.net/nova/+spec/injecting-network-configuration-file-to-windows-vm21:23
ttxvishy: can you look them up soon and set the series goal to essex if OK ?21:23
tr3buchetis someone planning on working the multiple-floating-ip-ranges?21:23
ttxvishy: (or unset the milestone if not)21:23
vishysure21:23
vishytr3buchet: me21:23
tr3buchetkk21:24
tr3buchetmade a note of it21:24
vishystarting it as soon as I prop the initial rbac branch21:24
ttx#action vishy to look up unplanned E3/E4 blueprints and confirm/unconfirm them21:24
ttx(also set priority for nova-parity-floating and scaling-zones while you're at it)21:25
ttxvishy: Anything on your side ?21:25
vishyttx: only a -- Welcome back everyone!21:25
ttxNova subteam leads: comments ?21:25
tr3buchetnothing from, i'm still catching up from vacation21:26
tr3buchetme ---------^21:26
ttxQuestions on Nova ?21:26
ttxDo we have devcamcar or anyone from Horizon core team to replace him ?21:27
*** mcohen has joined #openstack-meeting21:28
ttxLet's do incubation / other teams first21:28
ttx#topic Incubated projects and other Team reports21:28
*** openstack changes topic to "Incubated projects and other Team reports"21:28
ttxdanwent, troytoman: o/21:28
danwentsorry ttx, I can't stall for devmancar… not much to report on the quantum front.21:28
ttx#info About doing Melange/Quantum E3 milestone under release team management, it's still blocked on getting working tarball jobs.21:28
*** edconzel has left #openstack-meeting21:28
danwentwe're spinning up a number of good design discussion on the netstack ML for quantum21:28
ttxRelated CI bugs, for reference:21:28
ttxhttps://bugs.launchpad.net/bugs/907768 and https://bugs.launchpad.net/bugs/89788221:29
uvirtbotLaunchpad bug 907768 in openstack-ci "Needs working melange-tarball job" [Wishlist,Confirmed]21:29
danwentbhall, can you comment on the setup.py?21:29
bhallout for review21:30
bhalllemme find a link21:30
ttxhttps://review.openstack.org/#change,198821:30
danwenti know monty filed a similar bug.  we'll make sure our change is good for monty, and we'll make sure it gets pushed ASAP.21:30
bhallttx: thanks21:30
ttxAny other team lead with a status report ?21:31
troytomanon melange, we cut the first release last week for E221:31
troytomanfocused on testing/bug fixing and docs21:31
troytomanalso looking at some performance improvements for E3/E421:31
ttxtroytoman: still ok to try to do E3 on the common milestone date ?21:31
ttx(target date : January 26)21:32
troytomanttx: yes. that should work21:32
ttxok, back to Glance for a quick status update, unless some PTL shows up21:33
znsttx, troytoman: 26 is the release date. Code is cut 25th. so 'dev' deadline is really more like 24. ttx?21:33
ttxzns: yes.21:33
znstroytoman: FYI. Bit us in keystone. You have till 24 effectively...21:33
troytomanwe don't have a lot targeted for E3 (client separation and bug fixes mostly.) so , we should be fine21:33
ttx#topic Glance status21:33
*** openstack changes topic to "Glance status"21:33
troytomangood to know the details thought21:33
ttxso without a PTL or substitute, I'll just point out the recent announcement that Image API 2.0 work is postponed to F21:34
ttx#link https://lists.launchpad.net/openstack/msg06421.html21:34
annegentleDoc team will meet next Monday 1/9, 2:00 CST (noon PST).21:35
ttxMore next week21:35
ttxdevcamcar: still not around ? If not, we'll skip until next week21:36
annegentleA few more updates to the API site mock at http://heckj.github.com/api-site-mock/, including a search box.21:36
*** edconzel_ has joined #openstack-meeting21:36
ttxannegentle: anything more ?21:36
annegentleThat's all I can think of in docland.21:36
ttx#topic Open discussion21:36
*** openstack changes topic to "Open discussion"21:36
ttxWe plan to have a big bug squashing day for Nova on February 2.21:37
ttxThe goal is to get rid of as many bugs (closed as invalid or fixed) as possible over a day, as a good way to trim down the list just after E321:37
ttxOther projects are of course welcome to join on that same day.21:37
ttx(or set up their own bugsquashing day)21:37
ttx#link http://wiki.openstack.org/BugSquashingDay21:37
ttx#link http://wiki.openstack.org/BugSquashingDay/2012020221:37
ttxvishy: you had a theme for that one ?21:38
vishyyup21:38
vishyGroundhog Day bug squash!21:38
vishyhopefully we don't see our shadow21:38
Vekdoes that mean we'll be doing it over and over again?21:38
ttxyeah21:38
vishyor we have 2 more weeks of bug squashing21:38
vishy!21:38
ttxVek: yes21:38
vishyVek: we're thinking of setting them up every month or two21:39
ttxzigo: you wanted to talk about Kronos ?21:39
Vekmakes sense; I was just making a lame movie reference for the humor effect.21:39
zigoWell, basically, I've uploaded XenAPI into SID right before christmas.21:39
ttxvishy: the theme and objectives could slightly change though21:39
zigoAnd started to test it with Nova.21:39
zigoIt kind of works, but there are things to fix.21:39
zigoLike this one: http://paste.debian.net/150865/21:40
zigoPRODUCT_VERSION from XCP isn't reporting well.21:40
*** edconzel_ has quit IRC21:40
zigoI'm not sure how to fix, but I home Mike will help.21:40
ttxzigo: did you file bugs for those ? If yes, feel free to paste their links to ahere to attract attention to them21:40
zigoI did, but I don't have the # handy.21:41
ttxs/to ahere/here21:41
zigoThen, I could (with few other fixes) start instances on XCP using Nova.21:41
zigoBut I have no network connectivity or console access to the VMs.21:41
*** dragondm has joined #openstack-meeting21:41
zigoI'd need help from people working on Openstack support for XenServer / XCP.21:41
zigoI'm more doing packaging than core dev.21:42
zigoAnd I don't really know who to get in touch with.21:42
_cerberus_+++++621:42
zigottx: Who's the guys doing XCP + Nova that I should get in touch with?21:42
vishyzigo: people are mostly using XenServer atm21:43
ttx#help zigo wants Nova/Xen specialists help to get Nova/XCP working on Debian21:43
vishyzigo: but I think that most xen experts are from the cloudservers team21:43
vishyzigo: People will probably have more time to help after jan2621:44
zigoWell, wouldn't it be nice to have all fixed for the release?21:44
zigoI'm quite sure we aren't far from a completely working result...21:44
ttxjan 26 is, helpfully, not the final release :)21:45
zigo:)21:45
vishyzigo: release isn't until april, and yes it would be great21:45
zigok21:45
vishyzigo: it is just everyone is working like mad on features right now21:45
vishy:)21:45
zigoGot it.21:45
ttxAnything else, anyone ?21:47
ayoungbeuhler21:47
ttxbeuhler?21:48
annegentleanother movie reference :)21:48
ayoungnevermind21:48
ttxah :)21:48
zigoIs there currently a way in Nova to do accounting/reporting?21:49
ttxGoogle was surprisingly unhelpful with that one.21:49
zigoI've noticed that the nova-instance-monitor package is gone...21:49
markwashttx: http://www.youtube.com/watch?v=NP0mQeLWCCo21:49
ttxzigo: there is a notification firehose that you can plug your own system on, IIRC21:49
ttxzigo: ping dragondm about it21:50
dragondmya21:50
zigodragondm: Is this documented somewhere?21:50
*** somik has joined #openstack-meeting21:50
znszigo: there was a proposal a while back that started addressing this (it's where we came up with the tenant concept). See here: https://github.com/openstack/keystone/blob/a02fa988a4bdbfa05197078faa905f13274d82b8/doc/design/tenants.pdf?raw=true21:50
dragondmya. http://wiki.openstack.org/SystemUsageData21:51
dragondmzingo ^21:51
dragondmer zigo, sorry.21:51
zigoI might be interested to work on that...21:51
ttxLooks like this discussion can continue over #openstack-dev.21:52
zigoThat's it, I'm done and going to sleep.21:52
ttx#endmeeting21:52
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"21:52
openstackMeeting ended Tue Jan  3 21:52:32 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-03-21.03.html21:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-03-21.03.txt21:52
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-03-21.03.log.html21:52
ttxThanks everyone21:52
*** jdg has quit IRC21:52
zigoI'm not sure I can do more 5am meetings ... :)21:52
*** lzyeval has left #openstack-meeting21:52
*** jk0 has left #openstack-meeting21:53
ttxzigo: come back to France and make them 11pm ones.21:53
*** Vek has left #openstack-meeting21:53
zigo:)21:53
*** jwalcik has left #openstack-meeting21:53
*** zigo has quit IRC21:56
*** dprince has quit IRC21:59
danwenthello netstackers22:00
* mestery waves hi!22:00
danwentanybody home :)22:00
*** edconzel_ has joined #openstack-meeting22:00
mesteryHey danwent, hope your holidays were fun.22:01
danwent#startmeeting22:01
openstackMeeting started Tue Jan  3 22:01:06 2012 UTC.  The chair is danwent. Information about MeetBot at http://wiki.debian.org/MeetBot.22:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.22:01
danwentmestery: yes, freezing cold b/c I was in your neck of the woods :)22:01
*** liemmn_ has joined #openstack-meeting22:01
danwentI don't know you how do it :)22:01
mesteryhahaha22:01
*** liemmn has quit IRC22:02
danwentok, most of the action is probably going to be on the ML this week22:02
danwent#info agenda http://wiki.openstack.org/Network/Meetings22:02
danwent#topic Melange Status22:02
*** openstack changes topic to "Melange Status"22:02
*** SumitNaiksatam has joined #openstack-meeting22:03
danwenthopefully you saw the note about melange being released22:03
danwent#info: melange is now up as a full incubated project: http://launchpad.net/melange22:03
*** Salv-orlando has joined #openstack-meeting22:04
Salv-orlandoHello!22:04
danwentsounds like troy isn't here for any additional updates, but based on comments during main meeting they are focusing on perf improvements and separating out the client lib during E322:05
*** liemmn_ has quit IRC22:05
*** liemmn_ has joined #openstack-meeting22:05
danwenthey salv!22:05
danwentthought you were going to make it :)22:05
danwent#topic Quantum Status22:05
*** openstack changes topic to "Quantum Status"22:05
*** edgarmagana has joined #openstack-meeting22:05
danwentessex-3 is 3 weeks away: https://launchpad.net/quantum/+milestone/essex-322:05
Salv-orlandoFound an open network in the restaurant!22:05
*** liemmn has joined #openstack-meeting22:06
edgarmaganahi, little bit late  :-)22:06
bhalls/restaurant/pub/22:06
bhall:)22:06
danwentsince this is our last chance to get significant changes into nova, the most critical issues are probably those related to nova parity.22:06
danwentright now there are a lot of issue with status 'unknown'.  please update those statuses by next meeting, as everything should at least be started by then.22:07
danwentif anyone knows of something that is definitely not going to make it already, please bump it out.22:07
danwentGoal from last meeting was to start up ML threads on many of the topics that went cold due to essex-2 release & holiday.22:08
danwentSee the agenda for a list of all of them.22:08
danwentI think I'm about half-way through going through the issues as providing feedback (trying to adhere to rough chronological order).22:09
*** liemmn has quit IRC22:09
danwentwould be great if others could review as well.22:09
*** liemmn has joined #openstack-meeting22:09
danwentSalv: one question I sent to the list that I think is pretty important is when we think we will finalize API v 1.122:09
danwenttags where one thing we had talked about that hasn't been done yet.  Has anyone talked to ying?  I think she was going to do that.22:10
Salv-orlandoApi 1.1 in terms of specification is just 1.0 plus operational status22:10
danwentthe other things was that wwwkeyboard talked about changing the HTTP error codes.22:10
danwentsalv: don't filters need to be in 1.1 spec?22:11
Salv-orlandoThen there are the other things you're listing22:11
Salv-orlandoIncluding filters22:11
wwkeyboardI thought we were going to hold off on changing error codes?22:11
Salv-orlandoSorry i'm slow on mobile22:11
Salv-orlandoChanging error codes scares me a little22:12
danwentwwkeyboard: I don't remember if there was a firm conclusion… woudl have to look at thread.22:12
Salv-orlandoBut if we want to do it this is the tine22:12
Salv-orlandoTime22:12
danwentSalv-orlando: we don't have to do it at all if we don't think its important.22:12
danwentthe default is that it will stay the same, unless someone is really motivated to change it :)22:12
wwkeyboarddanwent OK, I thought we were going to wait for the changes in the API spec, but I may be confused22:12
danwentwwkeyboard: 1.0 is current spec.  We're putting together and finalizing 1.1, and I was trying to figure out if code changes would be part of that change.22:13
wwkeyboardWill they need to be implemented before that?22:13
wwkeyboardbefore the spec is finalized?22:13
Salv-orlandoI wanted more feedback on error codes. The discussion is still open- even if dornant in the last few weeks22:14
danwentdormant ML discussions…. seems like a trend :)22:14
*** debo-os has joined #openstack-meeting22:14
*** liemmn has quit IRC22:14
Salv-orlandoBottom line is: if we want to follow os api spec we need to change them22:15
*** liemmn has joined #openstack-meeting22:15
Salv-orlandoWe are not compliant at the moment22:15
danwentwwkeyboard: I suspect this comes down to whether you are sufficiently motivated to make the change, and whether the rest of the team is convinced its a good thing.  Probably best to bring it up on the ML again, and do it in E-3.22:15
danwentSalv-orlando:  ah, didn't realize it was that cut-and-dried22:15
*** pringles has quit IRC22:15
danwentsalv: so is it your feeling that we should do it?22:16
Salv-orlandoDanwent: assign me action to resume thread22:16
cdubdownside only being clients which have hardcoded around existing errors?22:17
danwent#action #Salv-orlando resume thread on changing API error codes22:17
Salv-orlandoI feel we should do it if our, priority is to comply with os API22:17
Salv-orlandoCdub: old error codes will still be there for 1'0 clients22:18
danwentThat seems pretty important to me.  Especially if we want many of the clients to be able to share common code (per email about openstack-common)22:18
*** liemmn has quit IRC22:18
cdub*nod*22:18
*** liemmn has joined #openstack-meeting22:18
Salv-orlandoAgreed22:18
*** edconzel_ has quit IRC22:19
danwentOk, I was flying this morning and am behind on some of the ML discussion this morning, so I vote for just continuing the rest of the topics on the ML, unless there's something in particular people want to bring up in IRC.22:19
danwentbhall:  can you comment on what ttx brought up during the main meeting?22:20
danwentsetup.py issues (bugs #897882 and #897943 and #910267)22:20
uvirtbotLaunchpad bug 897882 in quantum "Quantum needs proper setup.py (was: command 'egg' not found when running install_venv.py)" [High,In progress] https://launchpad.net/bugs/89788222:20
uvirtbotLaunchpad bug 897943 in quantum "Our setup.py needs to be a real setup.py" [Medium,In progress] https://launchpad.net/bugs/89794322:20
uvirtbotLaunchpad bug 910267 in quantum "Quantum setup.py does not use setuptools" [High,Triaged] https://launchpad.net/bugs/91026722:20
danwenttwo are from you, one from monty.22:20
danwentunclear if they are all the same issue, several different issues, etc.22:20
bhallyeah, there is a change out for review: https://review.openstack.org/#change,198822:20
danwentbut it seems like its blocking the infrastructure team.22:20
danwentOk, and that handle's monty's issue as well?22:20
bhallbasically, we need to conform to the rest of the openstack projects (i.e. python setup.py sdist needs to produce a tarball)22:20
bhallyes, I believe so22:21
danwentOk.  I will do a review on that tonight.  If someone else from the team could pitch in as well so we're not holding up the CI folks, that would be great.22:21
danwentOther Quantum comments before open discussion?22:21
danwent#topic open discussion22:22
*** openstack changes topic to "open discussion"22:22
*** jmckenty has quit IRC22:22
davlaphi folks! just wanted to say hello. i'm going to be helping out with quantum. look forward to working with you all!22:22
danwentwhere are you from davlap?22:22
danwent:P22:22
davlap:)22:22
davlapi work with dan and brad22:22
mesteryWelcome davlap!22:22
danwentwelcome to the team davlap!22:23
davlapthanks! great to be here!22:23
wwkeyboardwelcome!22:23
Salv-orlandoWelcome on board!22:23
*** debo-os has quit IRC22:23
danwentOk, any other open discussion?22:23
bhall#action danwent figure out hazing ritual for new netstackers22:23
danwenthaha22:23
davlap:)22:23
cdubheh22:23
danwentI thought being part of netstack WAS hazing :P22:24
bhallhah22:24
carlpThat was my experience :)22:24
danwenthey carlp!  btw, will be trying to get you a basic test for CI infrastructure this week.22:24
*** tylesmit has quit IRC22:24
danwentwas hoping santa would give me one, but turns out I need to do it myself22:24
danwentok, final call for open discussion22:25
carlpdanwent: awesome!22:25
*** debo-os has joined #openstack-meeting22:25
danwentremember to keep an eye on the ML … lots of action on there this week.22:25
danwentOk, thanks folks!22:25
danwent#endmeeting22:25
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"22:25
openstackMeeting ended Tue Jan  3 22:25:49 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:25
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-03-22.01.html22:25
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-03-22.01.txt22:25
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-03-22.01.log.html22:25
Salv-orlandoHave a good one guys!22:26
danwentthrow one down the hatch for our Salv!22:26
danwentour -> us22:26
Salv-orlandoSure22:26
*** Salv-orlando has quit IRC22:26
somikhave a good one folks!22:26
*** markvoelker has left #openstack-meeting22:27
*** liemmn has quit IRC22:27
*** troytoman is now known as troytoman-away22:28
*** liemmn has joined #openstack-meeting22:28
*** edgarmagana has quit IRC22:29
*** pringles has joined #openstack-meeting22:32
*** liemmn_ has joined #openstack-meeting22:33
*** liemmn has quit IRC22:33
*** liemmn__ has joined #openstack-meeting22:37
*** liemmn_ has quit IRC22:37
*** somik has quit IRC22:37
*** markmc has quit IRC22:40
*** liemmn__ has quit IRC22:40
*** liemmn__ has joined #openstack-meeting22:40
*** vladimir3p has quit IRC22:43
*** dolphm has quit IRC22:43
*** liemmn_ has joined #openstack-meeting22:46
*** liemmn__ has quit IRC22:46
mtaylordanwent, bhall: hey! sorry I missed the meeting ...22:47
mtaylordanwent, bhall: good test is, grab a tox.ini that I've tossed in to one of the other projects and see if you can run tox22:47
mtaylordanwent, bhall: it uses some setuptools features like --single-version-externally-managed22:48
mtaylordanwent, bhall: but is nice, because not only does it make a virtualenv, it actually makes the sdist target of your current tree and uses that to install the code into the virtualenv, so you get dist testing as well22:48
*** liemmn__ has joined #openstack-meeting22:51
*** liemmn_ has quit IRC22:51
danwentmtaylor: sorry, i miss you missing me :P  will make sure bhall sees this.22:53
bhallmtaylor: great, I'll try it out22:54
*** liemmn__ has quit IRC22:54
*** liemmn__ has joined #openstack-meeting22:54
*** danwent has left #openstack-meeting22:55
*** liemmn__ has quit IRC22:59
*** liemmn__ has joined #openstack-meeting22:59
*** ayoung has quit IRC23:01
*** lloydde has quit IRC23:04
*** liemmn__ has quit IRC23:04
*** liemmn__ has joined #openstack-meeting23:04
*** lloydde has joined #openstack-meeting23:06
*** rnirmal has quit IRC23:09
*** HowardRoark has joined #openstack-meeting23:09
*** liemmn__ has quit IRC23:09
*** liemmn__ has joined #openstack-meeting23:10
*** debo-os has quit IRC23:14
*** liemmn__ has quit IRC23:14
*** liemmn__ has joined #openstack-meeting23:14
*** mdomsch has quit IRC23:16
*** liemmn_ has joined #openstack-meeting23:19
*** liemmn__ has quit IRC23:19
*** Gordonz has quit IRC23:22
*** liemmn__ has joined #openstack-meeting23:23
*** liemmn_ has quit IRC23:23
*** nati2 has joined #openstack-meeting23:25
*** liemmn_ has joined #openstack-meeting23:27
*** liemmn__ has quit IRC23:27
*** lloydde has quit IRC23:29
*** mcohen has left #openstack-meeting23:30
*** liemmn__ has joined #openstack-meeting23:34
*** liemmn_ has quit IRC23:34
*** lloydde has joined #openstack-meeting23:36
*** liemmn_ has joined #openstack-meeting23:39
*** liemmn__ has quit IRC23:39
*** liemmn_ has quit IRC23:40
*** dolphm has joined #openstack-meeting23:43
*** dolphm has quit IRC23:47
*** vladimir3p has joined #openstack-meeting23:47
*** mattray has quit IRC23:50
*** AlanClark has quit IRC23:56
*** deshantm_ has joined #openstack-meeting23:57

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