Tuesday, 2011-06-28

*** heckj has quit IRC00:01
*** adiantum has joined #openstack-meeting00:03
*** JordanRinke is now known as JordanRinke_AFK00:10
*** ohnoimdead has quit IRC00:10
*** dragondm has quit IRC00:10
*** s1rp has quit IRC00:10
*** ohnoimdead has joined #openstack-meeting00:13
*** dragondm has joined #openstack-meeting00:13
*** s1rp has joined #openstack-meeting00:13
*** adiantum has quit IRC00:21
*** ohnoimdead has quit IRC00:31
*** adiantum has joined #openstack-meeting00:33
*** adiantum has quit IRC00:42
*** Binbin has joined #openstack-meeting00:42
*** adiantum has joined #openstack-meeting00:54
*** dragondm has quit IRC00:56
*** Shubhangi has joined #openstack-meeting00:57
*** adiantum has quit IRC01:06
*** adiantum has joined #openstack-meeting01:10
*** adjohn has joined #openstack-meeting01:17
*** adiantum has quit IRC01:30
*** mattray has joined #openstack-meeting01:33
*** adiantum has joined #openstack-meeting01:43
*** msinhore has joined #openstack-meeting01:58
*** adiantum has quit IRC01:59
*** Shubhangi has quit IRC02:04
*** carlp has joined #openstack-meeting02:10
*** adiantum has joined #openstack-meeting02:12
*** adiantum has quit IRC02:30
*** adiantum has joined #openstack-meeting02:35
*** alekibango has quit IRC02:36
*** adiantum has quit IRC02:45
*** adiantum has joined #openstack-meeting02:51
*** mattray has quit IRC02:52
*** alekibango has joined #openstack-meeting02:59
*** JordanRinke_AFK is now known as JordanRinke03:04
*** Binbin has quit IRC03:23
*** Binbin has joined #openstack-meeting03:24
*** msinhore has quit IRC03:24
*** ohnoimdead has joined #openstack-meeting03:29
*** adiantum has quit IRC03:29
*** ohnoimdead has quit IRC03:30
*** msinhore has joined #openstack-meeting03:32
*** adiantum has joined #openstack-meeting03:36
*** adiantum has quit IRC03:45
*** adiantum has joined #openstack-meeting03:58
*** nati has joined #openstack-meeting04:03
*** adiantum has quit IRC04:14
*** adiantum has joined #openstack-meeting04:19
*** JordanRi1ke has joined #openstack-meeting04:27
*** ke4qqq has quit IRC04:27
*** JordanRinke has quit IRC04:27
*** ke4qqq_ has joined #openstack-meeting04:27
*** _cerberus_ has quit IRC04:28
*** _cerberus_ has joined #openstack-meeting04:28
*** adiantum has quit IRC04:30
*** adiantum has joined #openstack-meeting04:43
*** adiantum has quit IRC05:02
*** adiantum has joined #openstack-meeting05:07
*** adiantum has quit IRC05:14
*** adiantum has joined #openstack-meeting05:18
*** adiantum has quit IRC05:30
*** msinhore has quit IRC05:39
*** Shubhangi has joined #openstack-meeting05:41
*** adiantum has joined #openstack-meeting05:42
*** adjohn has quit IRC05:49
*** adjohn has joined #openstack-meeting05:52
*** exitdescription has left #openstack-meeting05:56
*** adiantum has quit IRC06:07
*** adiantum has joined #openstack-meeting06:13
*** Binbin has quit IRC06:15
*** Binbin has joined #openstack-meeting06:20
*** nati has quit IRC06:29
*** adiantum has quit IRC06:30
*** adiantum has joined #openstack-meeting06:35
*** adiantum has quit IRC07:01
*** adiantum has joined #openstack-meeting07:06
*** Shubhangi has quit IRC07:18
*** dragondm has joined #openstack-meeting07:27
*** adiantum has quit IRC07:31
*** adiantum has joined #openstack-meeting07:37
*** adiantum has quit IRC07:46
*** adiantum has joined #openstack-meeting07:59
*** nati has joined #openstack-meeting08:04
*** adiantum has quit IRC08:07
*** zul has joined #openstack-meeting08:39
*** nati has quit IRC09:32
*** adjohn has quit IRC09:43
*** Binbin has quit IRC10:06
*** dragondm has quit IRC10:31
*** nati has joined #openstack-meeting10:53
*** nati has quit IRC10:59
*** Shubhangi has joined #openstack-meeting11:34
*** zul has quit IRC12:07
*** dprince has joined #openstack-meeting13:18
*** zul has joined #openstack-meeting13:20
*** mattray has joined #openstack-meeting13:45
*** zul has quit IRC13:46
*** zul has joined #openstack-meeting13:50
*** jkoelker has joined #openstack-meeting13:55
*** dprince has quit IRC14:07
*** creiht has joined #openstack-meeting14:13
*** dprince has joined #openstack-meeting14:16
*** msinhore has joined #openstack-meeting14:31
*** ke4qqq_ is now known as ke4qqq14:45
*** ke4qqq has joined #openstack-meeting14:45
*** Shubhangi has quit IRC14:58
*** jmelesky has joined #openstack-meeting15:03
*** jmelesky has quit IRC15:28
*** jmelesky has joined #openstack-meeting15:31
*** heckj has joined #openstack-meeting15:36
*** dendrobates is now known as dendro-afk15:38
*** vladimir3p has joined #openstack-meeting15:55
*** dendro-afk is now known as dendrobates15:57
*** Shubhangi has joined #openstack-meeting16:09
*** dragondm has joined #openstack-meeting16:24
*** Shubhangi has quit IRC16:30
*** rnirmal has joined #openstack-meeting16:40
*** Shubhangi has joined #openstack-meeting17:10
*** zul has quit IRC17:12
*** Shubhangi has quit IRC17:16
*** joearnold has joined #openstack-meeting17:17
*** Shubhangi has joined #openstack-meeting17:19
*** joearnold has quit IRC17:44
*** joearnold has joined #openstack-meeting17:53
*** gholt has joined #openstack-meeting18:02
*** Shubh has joined #openstack-meeting18:13
*** dprince has quit IRC18:16
*** sjagarla has joined #openstack-meeting18:19
*** joearnold has quit IRC18:26
*** rminnear has joined #openstack-meeting18:29
*** sai has joined #openstack-meeting18:32
*** johnpur has joined #openstack-meeting18:32
*** joearnold has joined #openstack-meeting18:38
*** joearnold has quit IRC18:48
*** shwetaap has joined #openstack-meeting18:48
*** Shubhangi has quit IRC18:50
*** Shubh has quit IRC18:50
*** Shubhangi has joined #openstack-meeting18:50
*** Shubh has joined #openstack-meeting18:51
ShubhHi Everyone19:08
ttxShubh: o/19:09
saiis that meeting started?19:09
*** msinhore has quit IRC19:09
*** foxtrotgulf has joined #openstack-meeting19:10
ttxsai: the CI meeting ?19:10
saiyes19:10
*** msinhore has joined #openstack-meeting19:10
ttxmtaylor: around ?19:10
heckjIT's been all quiet today - nothing started19:10
ShubhCan anyone tell the specific format that we have to follow to create test cases19:11
Shubh?19:11
heckjShubh: termie had some great suggestions on it, and I think there was something stashed in the wiki or etherpad, but I don't have a link19:12
ttxShubh: ping westmaas about it -- his team worked on examples19:12
Shubhokay .Thank you heckj and ttx19:13
saiwhat are the test cases we can do on openstack?19:13
ttxLooks like this meeting is missing its chair -- so I think it's safe to cancel it19:14
heckjShubh: http://wiki.openstack.org/TestingGuideDraft , http://wiki.openstack.org/SmallTestingGuideDraft19:14
heckjttx: any fancy hash tags for the bot to assert a meeting is cancelled?19:15
ttxheckj: nope -- we just don't start it :)19:15
ttxsai: we have unit tests in the code and various smoketest harnesses19:16
ttxsai: the meeting that should have happened this hour is about making all those smoketest harnesses converge.19:17
saido we need install smoketest in our machine?19:17
ttxsai: no, smoketests are various deploy+run automated tests.19:17
ShubhSo I can see in the example ,the unittest getting imported but can not find the unittest package anywhere in the nova19:18
ttxShubh: that's standard Python: http://docs.python.org/library/unittest.html19:19
sai@ttx how to do the smoketest19:19
ttxsai: there is no single "smoketest", just various tests that different groups use. Not sure which one(s) are available to others19:20
ttxsai: we are still working on building a single official one19:20
Shubhohh okay .good .I will try to import that in the example and then try to run it19:20
ttxsai: if you're interested in that, you can contact mtaylor.19:21
saithanks ttx19:22
ShubhSo ttx how did u executed or tested the unit test cases .Is it through the run_test.sh or through python as mentioned in the link19:25
ttxI use the run_tests.sh19:26
ShubhSo we just have to import the unittest and the respective packages for the creating the unittest case19:26
Shubham I correct19:27
ttxShubh: we should have this discussion in #openstack, this channel is used for meetings, and one will start in 30min19:27
Shubhoh okay.I apologise .I thought this one is for Testing and CI19:28
ttxShubh: unfortunately there is no meeting today, apparently.19:28
Shubhohh okay.19:29
ShubhThanks anyways .I appreciate your help19:33
*** joearnold has joined #openstack-meeting19:36
*** ewanmellor has joined #openstack-meeting19:47
*** zdeng has joined #openstack-meeting19:49
*** dolphm has joined #openstack-meeting19:50
*** markvoelker has joined #openstack-meeting19:52
notmyname /letsdothis20:01
*** danwent has joined #openstack-meeting20:01
*** zns has joined #openstack-meeting20:02
*** jbryce has joined #openstack-meeting20:02
jbrycehello20:02
jbrycewho all is here?20:02
znsjbryce: hi20:02
johnpuro/20:02
heckj\o20:02
ttxo/20:03
ShubhHi20:03
ewanmellor\o/20:03
sjagarlahi20:03
saihi20:03
jbryceso 4 ppb members so far?20:03
*** bcwaldon has joined #openstack-meeting20:03
ttxjbryce: a bit short.20:04
*** jmckenty_ has joined #openstack-meeting20:04
jmckenty_sorry I'm late20:04
jbrycettx: yep20:04
ttxjbryce: soren is in vacation so won't be around -- dunno for any other20:04
notmynamehow many is quorum?20:04
jbryce720:05
jmckenty_How many are we?20:05
ttx520:05
notmynameI count 620:05
jbryce6 now actually20:05
jmckenty_where's anotherjesse?20:05
dendrobateso/20:06
notmynameI saw most of the anso people at rookie-o at rackspace yesterday20:06
jmckenty_what about purrier?20:06
jmckenty_I see ewanmellor20:06
jmckenty_and dendrobates20:06
ttxjmckenty: he is here20:06
notmynamewith dendrobates, I thinkwe are 720:06
jmckenty_doesn't that make 7?20:06
jmckenty_ah, cool20:06
jbryceit does now20:06
jbryce#startmeeting20:06
openstackMeeting started Tue Jun 28 20:06:43 2011 UTC.  The chair is jbryce. Information about MeetBot at http://wiki.debian.org/MeetBot.20:06
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.20:06
jbrycehttp://wiki.openstack.org/Governance/PPB - agenda at the bottom20:06
jmckenty_jbryce: can I suggest structured discussion on the project autonomy question?20:07
jbrycejmckenty_: sure20:07
jmckenty_e.g., one person to present for, one to present against, and then discussion?20:07
jbryceany volunteers for either side?20:08
jmckenty_Maybe using #info for relevant factoids20:08
jmckenty_I'll present against autonomy20:08
jmckenty_if no one else grabs it20:08
notmynameI'll volunteer for autonomy20:08
ttxjmckenty: I can help you with that.20:08
notmynameheh20:08
jbryceone thing to keep in mind to is that autonomy is kind of a gradient as well....20:08
jbrycethere are levels of autonomy20:08
notmynameof course20:08
jmckenty_true enough, I think if we argue the extremes,20:08
jbrycebut we can start with a flat for and against20:08
ttxyes, not sure it's a binary decision20:08
jmckenty_we'll end up identifying an ideal mid-position20:08
jbrycenotmyname: want to get it started since it was your topic?20:09
ttx(in fact, I'm wearing grey today)20:09
jbryce#topic Project autonomy20:09
notmynamesure20:09
*** openstack changes topic to "Project autonomy"20:09
notmynamemy thoughts, so as not to spam the channel: https://gist.github.com/1052036 (click the "raw" link to get nicely wrapped lines)20:09
notmynameit's short20:09
jbrycehttps://gist.github.com/1052036 - notmyname's summary of his position on project autonomy20:09
ttx"raw" doesn't work for me :)20:09
notmynamewe've made several decisions already that have tended towards autonomy. I'd like to continue that and allow each project to choose their own tools for their own work20:10
notmynamettx: https://raw.github.com/gist/1052036/33a6df89a37e6d29210806f61365c097a4b2e64b/gistfile1.txt20:10
ttxnotmyname: firefox displays that in very long lines. But I can handle it.20:10
jmckenty_So it seems like there are some buckets of "autonomy":20:10
jmckenty_ - Language20:10
jmckenty_ - Tools20:10
jmckenty_ - Release Cycle20:11
jmckenty_ - Philosophy20:11
jmckenty_ - Governance / Mgmt20:11
jmckenty_Did I miss anything substantive?20:11
notmynameI see the project management (openstack packaging/release) as a separate project and should choose their tools too20:11
notmynamejmckenty_: Philosophy kinda answers most of the others20:11
jmckenty_Not really - I'm using philosophy to mean "Project goals", e.g. scale and strong opinions20:11
jmckenty_aka who OpenStack will be useful for20:12
jmckenty_useful == designed for == ideal for20:12
*** primeministerp has joined #openstack-meeting20:12
jmckenty_There are actually a LOT of unique descriptions of openstack floating around now20:13
jmckenty_the launchpad.net one, the openstack.org one, the original novacc.org one20:13
jmckenty_Plus various things that have been said in the press (The operating system of the cloud, etc)20:13
jmckenty_Launchpad says "simple to implement "20:13
ttxNote that our best project autonomy definition so far is what we agreed at: http://wiki.openstack.org/ProjectTypes20:14
jmckenty_I agree with "so far",20:14
jmckenty_since we dodged the question of language, of philosophy, and of tools20:15
jmckenty_My strong (opinionated) position is this:20:15
jmckenty_Rackspace and NASA partnered on OpenStack originally, in large part, because we both had written in python20:15
jmckenty_A lot of the community engagement around OpenStack as a *unified* set of projects has been because of the language consistency20:16
jmckenty_Community portability (e.g., the ability for developers to move easily from nova to swift to glance, etc) will rest on common coding standards, including language20:16
jmckenty_And I think making that STRONGER rather than weaker will only help20:16
jmckenty_We've already agreed on unified governance (according to the project types doc)20:17
jmckenty_we *seem* to be converging on unified philosophy20:17
jmckenty_we've agreed on unified release cycles and packaging20:17
notmyname*20:17
jmckenty_If we agree on unified language, I'm happy to allow projects to have tool autonomyu20:18
jmckenty_provided we can agree on QUALITY gates20:18
jmckenty_e.g., everyone needs CI, everyone needs revision control, everyone needs review automation20:18
jmckenty_everyone needs measurement of unit test coverage20:18
ttxi don't really see the point of having autonomous projects calling themselves OpenStack, I guess. "OpenStack" must mean something, and that something is what we have in common.20:18
ttxnot just "being included in the release announcement"20:19
jmckenty_Right, we're just clarifying what the common ground is20:19
*** sjagarla has left #openstack-meeting20:19
jmckenty_I have a selfish reason, of course20:20
ttxI think it's one thing to diverge on code hosting... but for example differing on issue tracking (a user-facing tool) makes OpenStack look like a weird patchwork of separate pieces.20:20
jbryceon things like tools, i think it's important to consider the total audience of a specific tool20:20
*** sai has quit IRC20:20
jmckenty_I'm trying to make nova, swift and glance work together in much closer ways20:20
jmckenty_and having those three projects in different RCS makes it hard for me20:20
notmynameissue tracking is central to a dev workflow and should be chosen by those who use it (ie the devs for the project)20:20
jbrycesomething like the revision control system has a relatively small audience of the developers who are submitting code compared to issue-tracking/blueprints/release tracking which has developers, users, external tool builders20:21
jbryceissue tracking is not just a dev tool20:21
notmynameI agree with jmckenty_ about the quality gates, as long as they are descriptive guidelines rather than prescriptive requirements for projects20:21
jbryceit's used by many more people than just devs20:21
ttxjbryce: +120:21
dendrobatesI would say that issue tracking is a qa tool used by multiple groups20:21
johnpurmy view is that the dev community can drive the tools decision, but we need a *common* solution across openstack projects20:22
notmynamewe only currently have unified release cycles and packaging in the sense of the 6-month releases20:22
ewanmellornotmyname: Sorry, I disagree.  That's true as long as you're never expecting bugs that lie across components, but I fully expect bugs that need to move between Swift or Glance, or Nova and Quantum, or whatever.20:22
jbrycethere are a lot of people who enter and consume information from the bug reports and blueprints who are not submitting code20:22
jbrycei'd rather that all be centralized in one place that we can point everyone too20:22
ttxewanmellor: and accidentally, that's where Launchpad bugs really shine.20:22
jmckenty_ttx: let's avoid specific recommendations for the moment, if possible20:23
jbrycethey want to know what's going on in "openstack" not have to track down the information from an arbitrary number of authoritative sources20:23
ttxjmckenty: sure -- was just pointing out what we already had.20:23
jmckenty_jbryce: I think this is true, but also a major problem on the documentation and forums side as well20:23
creihthttps://wiki.ubuntu.com/Bugs/Watches#Watching%20Another%20Project20:23
jmckenty_notmyname: are you all right with all of us using the same system if it's github?20:24
jmckenty_b/c that's certainly the ideal for me20:24
notmynamejmckenty_: I think it raises the bar to entry for new projects20:25
jmckenty_nova was born on github, and I think it would be great to go back there20:25
notmynameI prefer github for my own project(s) but I think those who actually contribute to the projects shouldbe the ones to make that choice20:25
jbrycejmckenty_: what happened to avoiding specific recommendations for now?20:25
jmckenty_:p20:25
jmckenty_ttx threw a gaunlet20:25
ttxjmckenty: we are drifting away from "autonomy" into the next topic :)20:25
jmckenty_no, I think notmyname brought up autonomy originally only in the context of the github move, if I'm not mistaken20:26
notmynameyes, but it affects much more than code hosting or issues20:26
jmckenty_can we agree that there's no sense in projects having autonomous philosophy or language?20:26
jmckenty_e.g., if a project wants to be part of openstack, it needs to be cloud, and it needs to be simple to implement and massively scalable20:27
jmckenty_and it needs to be in python20:27
ttxjmckenty: is "philosophy" what is described in http://wiki.openstack.org/ProjectTypes ?20:27
notmynameexcept for the last part, I like that20:27
jbrycei can agree on philosophy. i think that is the foundation that binds openstack together.20:27
dendrobatesnotmyname: which last part?20:27
jmckenty_great. So what we're talking about is autonomy of TOOLS20:27
notmynamedendrobates: python20:27
jbrycebut how long is openstack going to last and grow? i hope for years maybe decades....i don't want to commit to 1 language forever20:27
ttxjmckenty: Openness, Transparency, Commonality, Integration, Respect of release deadlines, Facilitation of downstream distribution ?20:28
notmynamejmckenty_: to be part of openstack, a project should subscribe to the openstack philosophy20:28
ttxor a subset thereof ?20:28
jmckenty_ttx: I think the last is dangerous20:28
jmckenty_e.g., WHICH downstream?20:28
jmckenty_or how MANY downstreams20:28
jmckenty_jbryce: why not?20:29
ttxjmckenty: read that as "when contacted, the project devs should make their best to help downstream distributors" ?20:29
jmckenty_fair enough, though20:29
jmckenty_ttx: fair enough20:29
jmckenty_dendrobates: do you have a position on language?20:30
ttxi.e. if slackware comes knocking at our door, we should try to help them as much as we reasonably can.20:30
notmynameis openstack a single thing with subsystems or a collection of independent projects that work together for some level of integration and releases? I think the second20:30
jmckenty_ttx: so you're saying linux distros are the only downstreams?20:30
ttxI think the first.20:30
dendrobatesjmckenty: I think python is good enough for almost all situations20:30
jmckenty_What if someone wants to put openstack on an ASIC?20:30
ttxjmckenty: no, that was just an example :)20:30
ttxjmckenty: Puppet/Chef could also be considered downstreams.20:30
jmckenty_notmyname and ttx: I think the first as well20:30
jbrycei think somewhere in the middle. it's a collection of projects that can be used independently, but that will benefit from commonality.20:31
jbrycei'm wearing my grey shirt today, too. = )20:31
ttxjbryce: but that make sense as a whole, right ?20:31
jmckenty_can we each think of a comparable package?20:31
jmckenty_e.g., ubuntu would be the second, right?20:32
notmynameI see the packaging of openstack as another openstack project (meta project?). so I think that they should be able to choose tools they want. and the other projects should do what's possible to integrate (bug watches, code mirroring, etc)20:32
jmckenty_notmyname: My goal is to have it much more tightly integrated20:32
jmckenty_I think it's the primary differentiator of OpenStack from other attempts20:32
*** alandman has joined #openstack-meeting20:32
vishynotmyname: we could just fork all three projects and put them into a new project called openstack20:33
dendrobatesjmckenty: +120:33
jmckenty_vishy: I don't think you're allowed to use the spoon word20:33
vishynotmyname: but i think the idea is collaboration20:33
jmckenty_notmyname: is there a project that you think of as a comparable?20:34
notmynamevishy: I think collaboration is they key20:34
*** Tv_ has joined #openstack-meeting20:34
notmynamejmckenty_: I don't like trying to relate to other projects (it's like X except for Y) because we all have different perspectives on what X actually is. let's say what we want, not what we want it to be like20:34
jbrycewhen people want to get involved, it's much easier if there's more commonality rather than having to track their way around 10 projects that are using 100 combinations of revision control, issue tracking, roadmap tracking, release management. it's about much more than just the wishes of the few developers we have today.20:34
ttxjmckenty: I'd say something like "Linux kernel subsystems with slightly more independence for subsystem maintainers"20:34
jmckenty_I just find it easier to understand people's perspectives with an example20:35
ttxjmckenty: but as notmyname says, the metaphor is always bad20:35
gholtIf you have one set of "rules" you may have a lot fewer than 10 projects. ;)20:35
heckjor too subjective to be ultimately useful20:35
jmckenty_dendrobates et al: the thinking on a single language, aside from the cross-community aspects I mentioned earlier, it also keeps system dependencies down (and attendant security issues), coding conventions stronger, etc.20:36
ttxSo we have two options, #1 is "openstack is a single product made aof a lot of independent, but cooperating, components" and #2 is "a collection of independent projects that work together for some level of integration and releases"20:37
jmckenty_But I agree we have the potential need for C / Erlang / etc. for very low-level performance concerns, which is why we dodged this before20:37
dendrobatesjmckenty: I agree.  That was one of the original reasons20:37
jbrycegholt: raw quantity of projects is not a specific goal of mine...with that said, i would propose something similar to what we already agreed on for revision control20:37
ttxwe saw with the Burrow/erlang discussion that there is a lot of value in keeping the dev community around a single language20:37
jbrycein the different categories of tools we have options that projects can choose from that tie in well with the processes and overall systems to manage releases and information20:37
jbrycee.g. revision control can be bzr or git, issues can be launchpad or something that ties into launchpad mirroring (with the onus of making the mirroring work on the project team that wants to use the other tool), etc20:38
edayttx: that switch back was more for lack of performance gains :)20:38
creihtttx: How many people are actively developing on burrow?20:38
edaycreiht: just me so far! and one patch form some other guy20:38
ttxcreiht: I actually plan to help ;)20:38
* eday is getting lonely20:39
ttxThere is always somethign else to do though -- my point is that if I had to learn Erlang that remote possibility would even be less likely20:39
edayso, we started some of this discussions after the last summit, http://etherpad.openstack.org/PQ7dy5in2B, if we want to add autonomy specifics there20:39
creihtttx: big community there ;)20:39
jmckenty_jbryce: did I miss some previous decision on git issues v2.0, or has it not come up yet?20:39
gholtSo, say Swift was it's own non-OpenStack project, but considered needed by OpenStack as a whole. How would it be incorporated?20:39
edayat the time I though we had decided more integrated/less autonomous20:39
*** ymht has joined #openstack-meeting20:40
jmckenty_eday: this ended up being http://wiki.openstack.org/ProjectTypes right?20:40
*** ewanmellor has quit IRC20:40
jmckenty_which we ratified20:40
ttxjmckenty: at ODS we said we'd consider issue tracking once/when/if code hosting is migrated20:40
notmynameI don't subscribe to the idea of developer portability. in practice, having devs that move between projects is exceedingly rare and there will always be learning curves, even if tooling is identical20:40
eday(not saying I necessarily agree, just stating what was previously "decided")20:40
ttxnotmyname: Glance being an exception rater than the rule ?20:40
jmckenty_ttx: that's how I remembered it20:40
creihtI'll offer the opinion that if you make too strict of rules, you may miss out from contributions from the broader community as a whole, including projects20:41
ttxjmckenty: so in Boston in October.20:41
jmckenty_notmyname: I respectfully disagree.20:41
*** ewanmellor has joined #openstack-meeting20:41
jmckenty_notmyname: maybe on a day-by-day basis, but I've seen a TON of long-term migration between projects20:41
edayjmckenty_: ahh, yes. so it did20:41
jmckenty_creiht: if that's a trade-off for a quality bar, I'm okay with it20:41
creihtthe problem is, programming language != quality20:42
gholtIt's more a trade off for "not how I want it" bar. :)20:42
creihtwe are all for high quality projects20:42
jmckenty_sure, but <n> X language ~= low quality, in general20:42
dendrobatescreiht: no but familiarity with the language helps spot quality problems20:42
jmckenty_you end up with a shallow review group20:42
jmckenty_a shallower set of tools20:43
ttxjbryce: vote/decision/action ? 15min left.20:43
creihtand most programming languages have the tools that help meet high quality standards, including the standards you summarized at the beginning20:43
creihtdendrobates: that is quite the strawman20:43
jmckenty_creiht: can you name a multi-language project that has high quality?20:43
creihtI'm not talking about a multi-language project20:43
creihtgets back to philosophy20:43
jmckenty_and if you say Eucalyptus, I'm going to vote to have you ejected from the PPB :P20:43
dendrobatescreiht: just poorly typed.  see jmckenty's comment instead20:44
notmynamejmckenty_: if openstack recommends something, like python or bzr or launchpad, but allows projects to choose, that's fine. it's up to the projects to do the extra work required to integrate well20:44
creihtI've already been ejected from the PPB :{20:44
creiht:P20:44
notmynamejmckenty_: re: CI and code quality sutff20:44
jmckenty_right, that was the context that I brought it up in - 1 project, 1 language, a reasonably *minimal* set of tools20:44
creihtI would argue that most projects are going to have a core team that focus on that specific project20:44
ttxDid we lose our chair ?20:45
jmckenty_which can include multiple choices when necessary for dev workflow20:45
creihtjmckenty_: how much cross-polination is there between nova and swift now?20:45
jbrycettx: no20:45
ttxah!20:45
creihtalmost none20:45
jmckenty_creiht: I don't want to be a dick, but if you're not on the PPB, you're kind of out of turn20:45
creihtI believe this is an open meeting20:45
*** clayg has joined #openstack-meeting20:45
gholtOh, is this only for representatives?20:45
jmckenty_ah, my bad.20:45
creihtbut you don't have to listen to me, just offering my opinion20:45
jbrycejmckenty_: we've allowed external input in other meetings20:46
creihtindeed20:46
jbrycei'm not sure where the vote would be on this20:46
jmckenty_k, I have a hard time keeping track of the ppb members20:46
jbrycewe have different definitions of autonomy20:46
jbrycejmckenty_: http://wiki.openstack.org/Governance/PPB - all listed there20:46
notmynameI'm not sure that we even have soemthing that can be voted on20:46
jbryceright20:46
creihtjmckenty_: They are listed on a wiki page somewhere :)20:46
heckjswift and nova never cross polinated much, but glance is a bit different in that respect20:46
ttxjbryce: #1 is "openstack is a single product made aof a lot of independent, but cooperating, components" and #2 is "a collection of independent projects that work together for some level of integration and releases" ?20:46
creihtglance is also a very simple project20:47
creihtimho20:47
jmckenty_heckj: I'm working on some crazy swift things right now,20:47
*** murkk has joined #openstack-meeting20:47
jmckenty_and I'm a nova dev20:47
creihtnot at the same level as nova or swift20:47
heckjcreight: no argument there20:47
jmckenty_ditto for 0x4420:47
gholtjmckenty_: Really? Care to share with the Swift guys? :)20:47
creihtjmckenty_: it would be nice if that was done in the open ;)20:47
ttxjbryce: I think the question of "single product" vs. "collection of independent projects" is the central one20:47
jbryceok20:47
jmckenty_creiht: it's on github20:47
jmckenty_;)20:47
creihtyou know since we are supposed to  be a community and all20:47
gholthahahahhaha20:47
jbrycecan we pause the discussion for a minute20:48
heckjI would posit that you'd get more benefit longer term from more cross pollination, so encouraging that is useful/beneficial to the project20:48
jmckenty_sure20:48
jmckenty_jbryce: sure20:48
jbrycelet's take a vote on the options ttx laid out in terms of a general philosophy on autonomy20:48
jmckenty_+1 for #120:49
ttx+1 for #120:49
jbryce#topic VOTE: #1 is "member:openstack is a single product made aof a lot of independent, but cooperating, components" and #2 is "a collection of independent projects that work together for some level of integration and releases"20:49
*** openstack changes topic to "VOTE: #1 is "member:openstack is a single product made aof a lot of independent, but cooperating, components" and #2 is "a collection of independent projects that work together for some level of integration and releases""20:49
jbryce+1 for #120:49
jmckenty_+1 for #120:49
johnpur+1 for #120:49
notmyname+1 for #220:49
ttx+1 for #1 (for the record)20:49
jmckenty_dendrobates: ?20:49
eday+1 for #220:49
jmckenty_ewanmellor: ?20:49
dendrobates+1 for 120:50
jmckenty_vishy: ?20:50
ewanmellor+1 for #120:50
*** dabo has joined #openstack-meeting20:50
* vishy is thinking20:50
* jmckenty_ smacks vishy in his thinking-hole20:50
vishyI don't like forcing people to collaborate via policy20:50
vishybecause it leads to ill-will20:51
jmckenty_the doukhobors did it20:51
ttxvishy: it's not about forcing... it's about openstack being a single product or a collection of indep projects.20:51
vishyit is though20:51
jmckenty_they designed their villages to force people to run into each other on a daily basis20:51
vishywe're forcing detractors to take on our model of how things should work20:51
jmckenty_it kept conflict from festering20:51
jbrycethe policies can be flexible and include multiple viable options20:52
vishyI would prefer if we convince them to change their view20:52
*** pandemicsyn has joined #openstack-meeting20:52
jmckenty_vishy: the irony to me is that we moved nova to launchpad so that swift and nova would be on a common platform20:52
vishymy personal view is #1 is more valuable20:52
jbrycebut the tools need to roll into an integrated view and experience for all the audiences20:52
heckjjbryce: +120:52
vishyso +1 for #120:52
notmynamejmckenty_: we were both on git to start with! neither one of us wanted LP20:53
vishyanotherjesse says +1 for #120:53
jmckenty_There's some crazy crack-rock there that we should sort out at some point20:53
jmckenty_anyway20:53
jbryce#info philosophy is "openstack is a single product made aof a lot of independent, but cooperating, components" - vote 7-220:53
vishyI'll make a caveat that I don't think we should be heavy-handed on our plicies20:53
jbrycevishy: +120:53
vishy* policies20:53
dendrobatesvishy: I appreciate your concerns.  We do not want to be too pedantic20:53
jmckenty_jbryce: shall we vote on supporting multiple sets of tools (minimal sets) with equivalent function and strong integration?20:54
jmckenty_or is that a given?20:54
jbrycewell, that's item 3 on the agenda20:54
jmckenty_ah, right20:54
jbryce#topic Possibility for core projects to choose their own code hosting (free choice, no choice, or set of options vetted by PPB ?)20:54
*** openstack changes topic to "Possibility for core projects to choose their own code hosting (free choice, no choice, or set of options vetted by PPB ?)"20:54
jmckenty_and we still have 6 minutes left20:54
jbrycewe've got 5 minutes20:54
jmckenty_+1 for set of vetted options20:54
ttxok, I can explain the options20:54
notmynamejmckenty_: one project implies single code hosting and single toolset?20:54
jmckenty_no, I think it implies that as an ideal20:54
jbrycei'm for a vetted set of options20:54
jmckenty_but I think dev productivity trumps that20:55
*** jaypipes has joined #openstack-meeting20:55
jmckenty_I would make it a target to have everything in single hosting and toolset by the end of next year,20:55
*** masumotok_ has joined #openstack-meeting20:55
jmckenty_since it may involve writing the damn hosting platform to not suck20:55
ttxbasically "free choice" means the project choose and the integration tools must catch up, "no choice" is a bit out of fashion nowadays... and "set of options" allow to check for integration feasibility20:55
ttx...beforehand.20:55
ttxI obviously vote for "vetted set of options"20:56
*** johnpur has quit IRC20:56
dendrobatesI like a vetted set of options20:56
ttxsince neither of the extreme positions sound like a good idea to me20:56
jbrycelet's do an actual vote on it before we run out of time20:56
*** scotticu1 has joined #openstack-meeting20:56
jmckenty_#topic VOTE on integration tools20:57
jmckenty_+1 for vetted set20:57
ttx+1 for vetted set20:57
jbryce+1 for vetted set20:57
*** JordanRi1ke is now known as JordanRinke20:57
vishy+120:57
dendrobates+1 vetted set20:58
eday+1 for no choice - if we're going to be a "single project", lets not fragment. (we can still change the set, but keep it consistent)20:58
ttx(so, currently LP is the only option, but github should soon be an option, if mtaylor and termie work on it this week :)20:58
jbrycevishy: +1 for which?20:58
mtaylorttx: I'm not sure we're going to be doing much work this week - but it's coming real soon now20:58
jmckenty_ttx: I'd suggest that PPB / jbryce should make that more important than anything else they're doing20:59
vishyvetted20:59
*** Shubh has quit IRC20:59
jbryceso 5 for vetted, 1 for no choice20:59
jmckenty_notmyname: ?20:59
ewanmellor+1 for no choice -- I don't want to have to train my devs on git and bzr20:59
ttxewanmellor: note that we can actually turn "vetted" into "no choice" when we consider adding github to the set.20:59
notmyname+1 for no choice to be consistent with the previous vote (but I disagree with that ;-) )20:59
*** gholt has left #openstack-meeting20:59
jbryceok...we're out of time21:00
creihtwell that was convenient21:00
* jaypipes is a sad puppy for missing this...21:00
jbryce#info vetted set wins with 5 votes, no choice received 3 votes21:00
dendrobatesI change my vote to no choice. I agree with Ewan21:00
jbrycethat ties it up. we can discuss further next meeting. we've got to hand the room over for the larger team21:01
jbryce#info no final result21:01
jmckenty_I'll change to no choice if it's github21:01
jbryce#endmeeting21:01
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"21:01
openstackMeeting ended Tue Jun 28 21:01:23 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-06-28-20.06.html21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-06-28-20.06.txt21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-06-28-20.06.log.html21:01
ttxjaypipes: you can still retrospectively say what you would have voted for :)21:01
*** johnpur has joined #openstack-meeting21:01
johnpurback!21:01
jaypipesttx: reading back through the logs..21:02
ttxok... let's get started for the next meeting21:02
*** jwilmes has joined #openstack-meeting21:02
jmckenty_what's on the docket?21:02
jbrycehonestly, i think we need to discuss it more as well...21:02
ttx#startmeeting21:02
openstackMeeting started Tue Jun 28 21:02:51 2011 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.21:02
*** spectorclan_ has joined #openstack-meeting21:02
*** scotticu1 has left #openstack-meeting21:02
ttxWelcome to the OpenStack weekly team meeting...21:03
ttxToday's agenda is at:21:03
ttx#link http://wiki.openstack.org/Meetings/TeamMeeting21:03
ttx#topic Swift status21:03
*** openstack changes topic to "Swift status"21:03
*** jwilmes has quit IRC21:03
ttxnotmyname: any proposed date for 1.4.2 yet ?21:03
*** clayg has left #openstack-meeting21:03
*** joearnold has quit IRC21:03
*** jbryce has quit IRC21:03
notmyname1.4.2 will be between 7-20 and 7-2921:03
notmynameit's set in LP now for 7-2021:04
*** joearnold has joined #openstack-meeting21:04
ttxnotmyname: perfect!21:04
ttxnotmyname: Other announcements or comments ?21:04
notmynameprogress is going well21:04
notmynamecontainer sync is almost done21:04
notmynamestats/logging has been split out21:04
notmynameseveral bugs fixed21:05
*** adiantum has joined #openstack-meeting21:05
notmynameaccess log delivery is almost done21:05
notmynamegood stuff all around21:05
*** jwilmes has joined #openstack-meeting21:05
ttxcool. Anyone has questions on Swift ?21:05
*** joearnold has quit IRC21:06
*** alekibango has quit IRC21:06
ttxok, then, moving on to...21:06
*** joearnold has joined #openstack-meeting21:06
ttx#topic Glance status21:06
*** openstack changes topic to "Glance status"21:06
ttxjaypipes: Hi!21:06
*** alekibango has joined #openstack-meeting21:07
ttxdiablo-2 milestone-proposed branch was merged from trunk and test packages were produced21:07
*** cynb has joined #openstack-meeting21:07
ttxPackages up for testing at: https://launchpad.net/~glance-core/+archive/milestone-proposed21:07
*** reldan has joined #openstack-meeting21:07
ttxjaypipes: Looking at https://launchpad.net/glance/+milestone/diablo-2 you have 4 open milestone-critical issues listed already21:08
ttxjaypipes: do you still plan to get them all fixed by Thursday ? or does this need to be cleaned out ?21:08
*** dolphm has quit IRC21:08
ttxhrm. Looks like we lost Jay. vishy: you around ? Maybe we can do Nova first...21:09
vishyi see jay typing away21:09
vishybut sure21:09
vishy:)21:09
*** alekibango has quit IRC21:10
ttxvishy: throw soething at him. Mentos usually work well.21:10
jaypipesttx: ten things at once...21:10
*** alekibango has joined #openstack-meeting21:10
ttxjaypipes: welcome to the world of management :P21:10
daboso do darts21:10
jaypipesttx: I updated glance's d2 early this morning (or late last night, can't remember). I'll revisit them tonight.21:10
*** somik has joined #openstack-meeting21:10
ttxjaypipes: ok, just keep the list focused to what you actually want to include in d2 so that I can track how far we are from completion21:11
ttxn the deferred blueprints side, I guess we should defer refactor-stores to d3 ?21:11
ttx...21:12
*** troytoman-away is now known as troytoman21:12
*** adiantum has quit IRC21:13
ttxOk, I'll be back with this, let's do Nova.21:13
ttx#topic Nova status21:13
*** openstack changes topic to "Nova status"21:13
ttxvishy: yo21:13
*** smk has joined #openstack-meeting21:13
*** adiantum has joined #openstack-meeting21:13
vishyk21:13
ttxdiablo-2 milestone-proposed branch was also merged from trunk and test packages were produced21:14
vishyjust moving some blueprints :)21:14
ttxYou can grab them at: https://launchpad.net/~nova-core/+archive/milestone-proposed21:14
ttxPlease test and let us know if anything is utterly broken21:14
*** smk has quit IRC21:14
ttxvishy: any bug that you'd like to make milestone-critical and fixed before Thursday ?21:14
vishyi haven't found any yet21:14
vishybut I i'm going to email the list to see if anyone else has any21:15
ttxcool. I'll throw some tests up tomorrow, time permitting.21:15
ttxOn the deferred blueprints side... Unless you object I'll defer all those to d3:21:15
* ttx refreshes21:15
*** katkee has joined #openstack-meeting21:15
ttxsystem-usage-records, administrative-vms, kvm-block-migration, nova-virtual-storage-array21:16
ttxI think unittest-examples should be considered complete... westmaas ?21:16
dragondmusage records just merged21:16
ttxdragondm: ow, that was a bit late. Unless vishy wants to push it in diablo-221:17
vishyttx: yep21:17
westmaasI think we can do that, I'm working with anne to figure out where it should be.21:17
ttxvishy: could you propose a merge to milestone-proposed with that in and get it approved ?21:17
ttxthe sooner the better :/21:17
vishydragondm: any reason you would need it in d2?21:17
vishyIt is an isolated set of changes so i don't mind, but best to minimize potential for breakage21:18
ttxvishy: i'll let you two discuss that offline21:18
dragondmI'm not sure it's a crashing priority.   your csll.21:18
ttxwestmaas: What about error-codes ?21:19
ttxwestmaas: pushed to d3 ? Or completed as-is ?21:19
westmaas_cerberus_: I think we still have work on this one, right?21:19
dragondm(sorry about the late merge, btw, there was some bzr weirdnes that delayed it from yesterday)21:19
ttxmtaylor: should I push testing-jenkins-integration & testing-smoketests-documentation to d3 as well ? Or does it just not make sense ?21:20
westmaas_cerberus_: is that bp still valid?21:20
mtaylorttx: it just doesn't make sense - I'm working on the new ones at this moment (the discussion here turned to Themes/Epics)21:20
mtaylorttx: I will have this solved in the next 30 minutes21:21
ttxmtaylor: ok21:21
_cerberus_westmaas: no clue, TBH21:21
westmaashaha21:21
westmaascool21:21
*** ameade has joined #openstack-meeting21:21
westmaassounds done to me?21:22
ttxwestmaas: if nobody knows what would be left to do on this one... maybe means it's completed after all :)21:22
westmaasconcur!21:22
ttxwill mark done. And file the remaining issues as bugs anyway.21:22
ttxvishy: anything you wanted to mention ?21:22
*** johan_-_ has joined #openstack-meeting21:23
vishyyes21:23
vishyjust a warning which i will repeat on the ml21:23
vishyI decided to push multinic to after freeze so we maintain stability21:24
vishybut when it merges (in the next few days) it will likely break some things including other hypervisors21:24
tr3buchetwe can start pushing bugs for updating skipped tests etc21:24
ttxvishy: there is no such thing as a freeze, so please merge now :)21:25
vishyI'd like to have all of the issues fixed by d321:25
ttx(d3 is open)21:25
vishyyes, there are just a couple of issues still to be addressed and it will go in21:25
vishysorry i should have said after milestone branch21:25
ttxok :)21:25
vishythat's it21:25
ttxQuestions on Nova ?21:25
ttxjaypipes: are you back ?21:26
spectorclan_ttx: he is asking questions here21:26
ttxspectorclan: eh.21:27
*** zykes- has joined #openstack-meeting21:27
ttxLet's go to open discussion and plug him back when available21:27
ttx#topic Open discussion21:27
*** openstack changes topic to "Open discussion"21:27
ttxAnything/anyone ?21:27
*** adiantum has quit IRC21:27
spectorclan_Developer Summit - looks like the Boston Intercontinental Hotel; will confirm tomorrow21:27
ttxclassy.21:28
*** adiantum has joined #openstack-meeting21:28
spectorclan_ttx: soon we will be at the Ritz21:28
ttxspectorclan: I won't stop until we have a design summit on the ISS.21:29
*** zns has quit IRC21:29
*** zdeng has quit IRC21:30
ttxok, sounds like everyone is very busy with other things, so I'll close now21:30
*** spectorclan_ has left #openstack-meeting21:31
*** spectorclan_ has quit IRC21:31
ttx#endmeeting21:31
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"21:31
openstackMeeting ended Tue Jun 28 21:31:53 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-06-28-21.02.html21:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-06-28-21.02.txt21:31
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-06-28-21.02.log.html21:31
ttxThanks everyone :)21:32
*** adiantum has quit IRC21:33
*** ymht has quit IRC21:33
*** creiht has left #openstack-meeting21:35
*** adiantum has joined #openstack-meeting21:36
jaypipesttx: sorry man, nah...21:39
*** bcwaldon has left #openstack-meeting21:40
*** heckj_ has joined #openstack-meeting21:42
*** alekibango has quit IRC21:42
*** alekibango has joined #openstack-meeting21:42
*** dendrobates is now known as dendro-afk21:43
*** salv-orlando has joined #openstack-meeting21:43
*** alekibango has quit IRC21:44
*** alekibango has joined #openstack-meeting21:44
*** heckj has quit IRC21:45
*** heckj_ is now known as heckj21:45
*** ryu_ishimoto has joined #openstack-meeting21:48
*** midodan has joined #openstack-meeting21:51
*** adiantum has quit IRC21:56
*** jamesurquhart has joined #openstack-meeting21:57
*** ameade has quit IRC21:58
*** johan_-_ has left #openstack-meeting21:58
*** Jamey has joined #openstack-meeting21:58
*** Jamey has quit IRC22:00
*** heckj has quit IRC22:00
danwenthello netstack team22:00
salv-orlandohello22:00
danwentdendrobates has a conflict, cannot attend22:01
troytomanhowdy22:01
*** Jamey has joined #openstack-meeting22:01
jamesurquhartHey22:01
markvoelkero/22:01
danwentanyone else we know we need to wait for?22:01
danwenteveryone with an agenda item seems to be here22:01
danwent#startmeeting22:01
openstackMeeting started Tue Jun 28 22:01:37 2011 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
jamesurquhartRam is presenting to Cisco's world-wide engineers on OpenStack right now, so he won't make it.22:01
danwentcool22:01
somikhello all22:01
danwent(that he is presenting)22:01
danwentagenda: http://wiki.openstack.org/Network/Meetings22:02
Jameyhi22:02
*** Shubhangi has quit IRC22:02
*** SumitNaiksatam has joined #openstack-meeting22:02
danwent#topic netstack updates22:02
*** openstack changes topic to "netstack updates"22:02
danwentsince dendrobates is out we will skip incubation discussion22:02
danwentincubation is tied to us getting hudson access, as well22:03
danwentthough we're still trying to figure out the details.22:03
danwentanything else that is general netstack?22:03
danwent#topic quantum22:03
*** openstack changes topic to "quantum"22:03
danwentgeneral status, we're in a unit test/ system test/ bugfix stage right now.22:03
danwentmaking good progress I feel.22:03
danwentThree specific points on the agenda22:03
danwentMark Voelker's team has volunteered to take on the GUI blueprint22:04
danwenthttps://blueprints.launchpad.net/quantum/+spec/quantum-client-gui22:04
danwentAs part of that work, they will also take a crack at unifying the client code into a library22:04
markvoelkerTwo quick updates there....22:04
*** rminnear has quit IRC22:05
danwentthis library can be used by the GUI, cli, unit tests, and other services (e.g., donabe) that will orchestrate quantum22:05
danwenthttps://blueprints.launchpad.net/quantum/+spec/quantum-client-library22:05
danwenttake it away mark22:05
markvoelker1.) We've mocked up a little UI just to get a feel for where we'll going...we'll push that out somewhere later this week once we tie up a few loose ends22:05
danwentvery cool22:05
*** pandemicsyn has left #openstack-meeting22:06
markvoelkerOne point where we could use some feedback is how/where to deal with extended attributes (QoS, ACL's, etc) so we can discuss that once folks can see it22:06
*** alekibango has quit IRC22:06
salv-orlandois this UI integrated in Openstack dashboard or a separate gui?22:06
markvoelkerI'll set up an etherpad22:06
markvoelkerThe plan is to do a separate Django module that will be part of the Dashboard.22:06
somikthat sounds like the right approach22:07
*** eperdomo has joined #openstack-meeting22:07
danwentk, anything else to add on the GUI or client lib front?22:07
markvoelkerSecond update: we'll be working on the refactor starting later this week.  May be a tad slower than we'd have liked as one of our engineers is unexpectedly traveling out of the country.22:07
markvoelkerThat's all for me22:08
*** alekibango has joined #openstack-meeting22:08
danwentthanks mark.  will be great to have a GUI.22:08
danwentNext topic is API authn/authz22:08
*** adiantum has joined #openstack-meeting22:08
danwentSalvatore wrote a blueprint here: http://wiki.openstack.org/QuantumAuthSpec22:08
danwentI'd like to thank him for a very clearly written blueprint, very easy to follow22:09
danwentsalvatore, what is your preferred mechanism for feedback?22:09
*** ewanmellor has quit IRC22:09
danwent(I know you don't like etherpad ;P)22:09
salv-orlandoemail, possibly22:09
salv-orlandoor launchpad answers22:09
salv-orlandoetherpad is cool, but lacks notification22:09
danwentagreed.22:09
danwentlaunchpad answers is a clever idea.22:10
danwentmaybe give that a try?22:10
salv-orlandolaunchpad answsers are probably better than emails22:10
danwentdo you want to ask a question, then post the link?22:10
danwentso we can have a thread?22:10
salv-orlandoyes, sure22:10
danwentor do you want to handle individual questions.22:10
salv-orlandoI can post a general question, and then people can submit specific question as well.22:10
danwentgreat22:11
danwentThird and final quantum topic: nova changes and quantum integration.22:11
danwentSeems like the multi-nic code is still going through merge, but it very close now22:11
ryu_ishimotoright22:11
danwentryu's branch is: https://code.launchpad.net/~midokura/nova/network-refactoring22:12
ryu_ishimotoit is, and i have merged it into the refactoring branch to test it out with the current version of multi-NIC22:12
ryu_ishimotoand identified a few places that may cause problems with Quantum integration22:12
danwentI've pulled but have not tested much.  hoping to get to that over the long holiday (US) weekend22:12
danwentryu: please elaborate22:12
*** msinhore has quit IRC22:13
ryu_ishimotothe main issue was that 'virtual_interfaces' model is tied to the 'networks' model of Nova22:13
danwentah, you mean whether that reference is nullable?22:13
ryu_ishimotovirtual_interfaces is the VIF table that will be used to communicate with Quantum22:13
ryu_ishimotoright, we need to keep the current Nova networking but it is preferable to use this table as the VIF f or Quantum22:14
danwentryu: can you quickly repost your spec page for those listening in?22:15
danwentI don't have the link handy22:15
salv-orlandoryu_ishimoto: is that a data model issue?22:15
danwenthttp://wiki.openstack.org/network-refactoring22:15
danwentfound it.22:15
ryu_ishimotosure, it's http://wiki.openstack.org/network-refactoring  I haven't updated it with multi-NIC stuff but I will22:15
danwentgreat.22:15
*** jmckenty_ has quit IRC22:15
ryu_ishimotoTrey just told me today that he will make that network_id field nullable so that we can keep using VIF for Quantum22:16
tr3buchet:)22:16
salv-orlandocool22:16
tr3buchetbetter to do this now22:16
danwentagreed.22:16
danwentgreat work guys.22:16
danwent(and tr3buchet in particular... that was a monster patch)22:16
tr3buchetyou should see the merge conflicts ;)22:17
danwentOK, anything else for quantum?22:17
ryu_ishimototr3buchet: yeah seriously.  thanks Trey!22:17
danwenttr3buchet: ha22:17
ryu_ishimotothat's it for now22:17
danwentthanks ryu22:17
salv-orlandojusrt a quick passage on API extensions...22:17
danwentsure22:17
salv-orlandohas there been any progress? do we have an agrement on the extension model?22:17
danwentI think we agreed on following the openstack standard model22:18
* vishy notes that managing long-diverged branches in bzr often leads to re-fixing the same conflicts over and over again. bzr merge --weave helps sometimes.22:18
*** adiantum has quit IRC22:18
*** jmckenty_ has joined #openstack-meeting22:18
danwentwhoops22:18
danwentdo we have any update on jorge's work in general?22:18
tr3buchetvishy: yeah i played with --weave a bit22:18
danwentI'd really like to understand better where the existing extensions proposal differs.22:19
danwentI think we also need to figure out how plugins "register" an extension.22:19
troytomanI don't have an update from Jorge on the extensions documentation. I don't think there are changes pending as much as clearer documentation22:19
salv-orlandoI'd like to undestand these two things as well22:19
danwentSame call as last meeting:  if anyone wants to take a lead on this, please let me know.22:19
danwent(someone other than salv-orlando... he has already volunteered for too much :) )22:20
*** dendro-afk is now known as dendrobates22:20
jamesurquhartThe ask is to follow up on extensions progress with Jorge?22:20
salv-orlandoI might be wrong, but I think Ying was warking on this22:20
danwentI'm hoping to get cycles to do a quick review of the current work22:20
danwentit would be great for someone to scope out where the existing stuff falls short and call this out in the blueprint.22:21
*** rnirmal has quit IRC22:21
jamesurquhartYing and SumitNaiksatam were tracking this, I believe.22:21
danwentYes, both Ying and Somik have done a review.22:21
troytomanYing had a number of email exchanges with my team and with Jorge this week. I think the primary gap is with dynamic loading of extenstions22:21
danwentAh, great.22:21
troytomanI think it is agreed that should probably be handled in a separate blueprint. but, i don't know if everyone is agreed yet22:22
danwenttroytoman: dynamic loading be handled separately from the rest of the extension blueprint?22:22
jamesurquhartDo we need an online meeting to sort that out?22:22
jamesurquhartI can volunteer to get everyone together online if that is what is needed.22:23
somikanother thing is that the current extension code is falls short of jorge's extension proposal22:23
salv-orlandosomik: can you give us some details?22:23
troytomandanwent: yes. the current extension mechanism was never intended to address that space.22:23
danwentjamesurquhart: that could be helpful, though also just making sure that people are aware of the emails being sent is probably a good start.22:23
somiksal-orlando: the current code is modelled on existing extension mechanism in nova22:24
danwenttroytoman: ok, i haven't put much thought in on that front.22:24
danwentmaybe a meeting on the extensions stuff would make sense.22:24
*** cynb has quit IRC22:24
jamesurquharttroytoman I'll follow up with Ying, but can you see that I am cc'ed on the email thread/22:24
jamesurquhart?22:24
*** adiantum has joined #openstack-meeting22:24
troytomanjamesurquhart: will loop you in22:25
jamesurquhartOK. I'll get something together, starting with Ying and troytoman.22:25
danwentOk, that would be great.22:25
danwentDoes someone want to take a crack at a "dynamic API extension" blueprint?22:26
somiksalv-orlando: Jorge's extension proposal and our requirements are more than what nova supports. Our Pluggable backend presents additional challenges. Both these issues need to be addressed before we will be ready for merge.22:26
danwentor are we not on the same page about this being separate?22:26
salv-orlandosomik: got it, cool22:26
salv-orlando+1 for separation22:26
danwentis there a point in merging the rest of the stuff before the dynamic loading is implemented?22:26
danwentI'm not familiar enough with the code to know.22:26
somikwe might have to redo plugins an extensions22:27
danwentOtherwise I'd probably prefer to get the model right outside of trunk, then merge.22:27
danwentbut I don't feel that strongly about this, so if someone has another opinion, holler22:28
troytomanI think the dynamic piece should be separated. we will have to do some work to handle extensions.22:28
somikdanwent: that seems like a better idea to reduce churn therefore bugs.22:28
danwenttroy: since you have done the work here, I'm happy to yield to your take.22:28
troytomanwe can do that before or after a merge.22:28
troytomansounds like we want to make those changes before merging, correct?22:28
danwentI'd prefer that22:29
danwentSounds like a plan unless someone objects22:29
danwentgoing once, twice....22:29
danwentok, sounds like a plan :)22:29
danwentanything else on quantum?22:29
*** mattray has quit IRC22:29
danwent#topic melange22:29
*** openstack changes topic to "melange"22:29
danwenttroy?22:29
danwentgeneral update?22:29
*** agarwalla has joined #openstack-meeting22:30
troytomanwe continue to evolve the base functionality given feedback and example use cases22:30
danwentbtw, troy, can you create a blueprint for the dynamic stuff (or ask Ying/Sumit to do it?)22:30
danwentdynamic -> dynamic extension loading22:30
troytomanjamesurquhart and I will work that out since I think ying is best suited to spec it out22:31
danwentgreat, thanks.22:31
jamesurquharttroytoman agreed22:31
troytomanwe are bringing some rackspace nova core devs into the loop to help us figure out Nova integration22:31
troytomani am hoping we can get the project merged into Nova in the D3 timeframe. integration of the service within Nova can start after the nova network refactoring is merged.22:32
danwentcool.  any thoughts yet on a timeline?  I know the nova-network-refactoring is slotted for d3, which is coming up soon.  Do you see these changes as part of that?22:32
danwentsorry, crossed wires22:32
troytomani plan to get blueprints/wiki/etc. updated within the next week - i'm a bit behind there22:32
jamesurquhartdanwent: Are you creating actions via eavsdrop? With hash action?22:33
danwentI can :)22:33
jamesurquhartHey, I don't care. Just curious. ;)22:33
danwentno, its a good suggestion22:34
danwent#action jamesurquhart + troytoman will coordinate on dynamic api extension blueprint22:34
danwenttroy, do you expect that melange will replace existing nova code for IP allocation, or site along side it as an option?22:35
* salv-orlando danwent stole my question :-)22:35
troytomanwe are thinking it would likely replace the existing code. that was one of the drivers behind putting it into the Nova project.22:36
troytomanand a reason to wait for the refactoring work to be done22:36
danwentgreat to hear.  makes sense.22:36
danwentany other melange-related discussion points?22:36
danwent#action troytoman update nova melange blueprints22:37
danwent#topic donabe22:37
*** openstack changes topic to "donabe"22:37
*** adiantum has quit IRC22:37
danwentanyone around for an update?22:37
danwentI know dendrobates mentioned an API a while ago.22:37
jamesurquhartI'm just getting integrated into that effort, so I can't give update, but there is work underway.22:38
danwentWith quantum + multi-nic, I think we are to the point where we could at least create some interesting topologies as "containers"22:38
danwentOk, sounds good.22:38
danwent#topic open discussion22:38
*** openstack changes topic to "open discussion"22:38
danwentone question: are most people working next tuesday?22:39
salv-orlandoyes, I am... no holydays in the UK!22:39
somikjamesurquhart: it would be good to get some blueprints for discussion before writing too much code..22:39
markvoelkerdanwent: I likely will be22:39
danwentsalv: :)22:39
danwentOK, that sounds like quorum to me :)22:39
*** foxtrotgulf has quit IRC22:40
danwentany other open discussion?22:40
somiksalv-orlando: only monday is a holiday in US, tuesday is officially open for business here too :)22:40
salv-orlandoI'd really love to make some progress on incubation, is we need to move the meeting for having dendrobates it is fine for me22:40
jamesurquhartsomik: Right. That's the plan. Get some blueprints together quickly for discussion.22:40
danwentsalv: dendrobates was actually on vacation, then had a conflict today.  We'll ping him on that.  I believe he is making progress.22:41
salv-orlandocool22:41
danwent#action dendrobates to give update on quantum incubation for next meeting22:41
danwentlook at me using those action tags :)22:41
danwentanything else?22:41
jamesurquhartYou are a hash master, danwent. ;)22:42
danwentok, let's call it a meeting22:42
salv-orlandolaunchpad question for discussion on authN/authZ for quantum: https://answers.launchpad.net/quantum/+question/16309122:42
danwent#endmeeting22:42
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"22:42
openstackMeeting ended Tue Jun 28 22:42:31 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:42
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-06-28-22.01.html22:42
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-06-28-22.01.txt22:42
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-06-28-22.01.log.html22:42
salv-orlandoit got logged just in time :-)22:42
danwentsalv: I think that made the log22:42
danwent:)22:42
*** adiantum has joined #openstack-meeting22:42
danwentthanks all!22:43
salv-orlandocheers, bye!22:43
*** jamesurquhart has left #openstack-meeting22:43
*** markvoelker has left #openstack-meeting22:43
*** salv-orlando has quit IRC22:43
*** eperdomo has quit IRC22:44
*** jmckenty_ has quit IRC22:46
*** agarwalla has quit IRC22:48
*** SumitNaiksatam has quit IRC22:48
*** adiantum has quit IRC22:48
*** troytoman is now known as troytoman-away22:52
*** danwent has left #openstack-meeting22:52
*** jaypipes has quit IRC22:52
*** adiantum has joined #openstack-meeting22:55
*** shwetaap has quit IRC22:55
*** katkee has quit IRC22:58
*** Jamey has quit IRC23:01
*** adiantum has quit IRC23:04
*** vladimir3p has quit IRC23:08
*** adiantum has joined #openstack-meeting23:08
*** ryu_ishimoto has left #openstack-meeting23:09
*** reldan has quit IRC23:13
*** dragondm has quit IRC23:16
*** reldan has joined #openstack-meeting23:21
*** midodan has left #openstack-meeting23:22
*** adiantum has quit IRC23:24
*** dragondm has joined #openstack-meeting23:25
*** adiantum has joined #openstack-meeting23:37
*** jkoelker has quit IRC23:37
*** reldan has quit IRC23:39
*** reldan has joined #openstack-meeting23:41
*** adiantum has quit IRC23:48
*** jaypipes has joined #openstack-meeting23:52
*** adiantum has joined #openstack-meeting23:54
*** alandman has quit IRC23:56

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