Tuesday, 2011-07-26

*** msinhore has quit IRC00:40
*** vladimir3p has quit IRC01:03
*** dantoni has quit IRC01:16
*** deshantm_away is now known as deshantm01:39
*** adjohn has quit IRC02:09
*** medberry is now known as med_out02:13
*** msinhore has joined #openstack-meeting02:18
*** LoriC has quit IRC02:33
*** cbeck has quit IRC02:59
*** cbeck has joined #openstack-meeting03:00
*** msinhore has quit IRC03:01
*** adjohn has joined #openstack-meeting03:27
*** adjohn has quit IRC03:49
*** adjohn has joined #openstack-meeting04:09
*** adjohn has quit IRC04:09
*** dendro-afk is now known as dendrobates04:17
*** martine has quit IRC04:23
*** cbeck has quit IRC06:28
*** cbeck has joined #openstack-meeting06:29
*** jaypipes has quit IRC07:11
*** jaypipes has joined #openstack-meeting07:24
*** cbeck has quit IRC07:34
*** cbeck has joined #openstack-meeting07:35
ttxnotmyname: ack08:05
*** darraghb has joined #openstack-meeting08:58
*** darraghb has quit IRC09:46
*** darraghb has joined #openstack-meeting09:47
*** markvoelker has joined #openstack-meeting11:18
*** gaitan has joined #openstack-meeting11:33
*** soren has joined #openstack-meeting12:16
*** msinhore has joined #openstack-meeting12:17
*** martine has joined #openstack-meeting12:29
*** LoriC has joined #openstack-meeting12:50
*** dolphm has joined #openstack-meeting13:19
*** creiht has joined #openstack-meeting13:41
*** troytoman-away is now known as troytoman13:44
*** vladimir3p has joined #openstack-meeting13:55
*** mattray has joined #openstack-meeting14:05
*** jkoelker has joined #openstack-meeting14:19
*** dolphm has quit IRC14:55
*** dolphm has joined #openstack-meeting14:56
*** rnirmal has joined #openstack-meeting15:00
*** rnirmal has quit IRC15:09
*** med_out is now known as medberry15:22
*** dendrobates is now known as dendro-afk15:25
*** cynb has quit IRC16:01
*** dendro-afk is now known as dendrobates16:02
*** cynb has joined #openstack-meeting16:04
*** johnpur has quit IRC16:12
*** darraghb has quit IRC17:14
*** joearnold has joined #openstack-meeting17:21
*** mattray has quit IRC18:11
*** dendrobates is now known as dendro-afk18:12
*** mattray has joined #openstack-meeting18:20
*** adrian17od has joined #openstack-meeting18:22
*** dendro-afk is now known as dendrobates18:24
*** dendrobates is now known as dendro-afk18:25
*** dendro-afk is now known as dendrobates18:49
*** adrian17od has quit IRC18:49
*** bengrue has joined #openstack-meeting18:50
bengrueHello, humans.18:50
*** adrian17od has joined #openstack-meeting18:51
jeblairhi, who's here for the openstack-ci meeting?19:00
bengrueI am.19:01
jeblairmonty asked me to chair the meeting today since he couldn't make it.19:01
jeblairwe might be a little thin, with oscon going on19:01
bengrueThis is my first meeting;  I did CI at IMVU, and have just joined up at PistonCloud.19:02
jeblaircool, welcome!19:03
jeblairlet's get started19:04
jeblair#startmeeting19:04
openstackMeeting started Tue Jul 26 19:04:17 2011 UTC.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.19:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.19:04
jeblair#topic Actions from last meeting19:04
*** openstack changes topic to "Actions from last meeting"19:04
jeblairso the first item was: jeblair Fix OpenID support in Gerrit19:04
jeblairi've patched gerrit so that it operates in a single-sign-on mode, like our jenkins install, with launchpad as the openid provider19:05
jeblairso we have SSO with launchpad, gerrit, and jenkins.  this should make it a bit easier to use all of those tools19:06
jeblairin a related note, the second item was: mtaylor Write script to sync launchpad users/teams to gerrit users/groups19:06
jeblairthat is mostly done; monty has written an initial version of a script that does that, so that developers should only have to register with launchpad19:07
jeblairthen all their (public) information is synced to gerrit19:07
*** tomeff has joined #openstack-meeting19:07
jeblairthere's a bit of optimization to do so that group membership changes are propogated quickly, but what is there now should be a big time saver for any projects that start using gerrit.19:08
jeblairfinally: mtaylor finish migrating jenkins jobs from running on master to running on slaves19:08
jeblairthis is _nearly_ complete at this point.  I believe there were some hiccups with the slaves being a little different from the previous config used on the master.19:09
jeblairi'll go ahead and put the last two items back on the stack for next week just to make sure they're closed out19:10
jeblair#action mtaylor Optimize script to sync launchpad users/teams to gerrit users/groups19:10
jeblair#action mtaylor finish migrating jenkins jobs from running on master to running on slaves19:10
jeblair#topic Blueprints are up19:11
*** openstack changes topic to "Blueprints are up"19:11
*** nati has joined #openstack-meeting19:11
*** dendrobates is now known as dendro-afk19:11
jeblairour roadmap and tasks are visible here:19:12
jeblair#link https://blueprints.launchpad.net/openstack-ci19:12
jeblairyou can see that right now, we're putting a lot of effort into getting a git based workflow operational19:12
*** Shubhangi has joined #openstack-meeting19:13
jeblairwe've started testing that with the keystone project, which is in the incubation stage19:13
jeblairthis morning Jenkins ran its first test out of that workflow (triggered by a change in gerrit)19:14
*** adjohn has joined #openstack-meeting19:15
jeblairso we're making progress, and writing documentation to help other projects if/when they transition19:15
jeblairanything regarding the blueprints before we move to open discussion?19:16
*** shwetaap has joined #openstack-meeting19:17
jeblair#topic Open Discussion19:17
*** openstack changes topic to "Open Discussion"19:17
jeblairanything else anyone wants to talk about?19:18
jeblairbengrue: are you going to be doing CI work at piston cloud?19:19
bengrueI will be.19:19
bengrueI might be able to assist with the git porting here too, after I get more familiar with the projects as a whole.19:19
bengrueIf help is needed/desired/welcome/etc.19:20
jaypipeshey guys, sorry, just got back from dentist... :(19:20
jeblairhi jay19:20
adrian17odWill the openstack-ci code be migrated to github at some point? it's a bit of a pain accessing bazaar+launchpad from behind a proxy.19:20
jeblairbengrue: right now we're in a sort of pilot/evaluation phase with keystone and glance19:21
jeblairif things work out, i imagine many of the openstack projects will move to git19:21
adrian17odcool19:21
bengruecool; how's that been going thusfar?19:21
alekibango+ 1 for git19:21
bengrueI think I've got +6 in this (physical) room for git.19:22
alekibango i never got used to bzr19:22
jeblairour gerrit/jenkins/github workflow seems to be functioning; since the keystone devs just started using it yesterday, it's probably a bit early for subjective reports19:23
bengrueIs everyone involved in that effort comfortable with the git workflow?19:23
jeblairthe workflow is based around a gated trunk -- so after each change is approved in code review, jenkins will run tests and the change is automatically merged only if it succeeds.19:24
jeblairthe keystone devs are existing git users, but they've been using only github without gerrit.19:24
bengrueI see.  I've not used gerrit myself, but this sounds relatively sane/simple.19:25
*** adjohn has quit IRC19:25
bengrueCool.  I look forward to seeing more and helping out in the future.  But for now, I look forward to lunch. ; )19:25
jeblair:)  great, let us know how we can facilitate your work19:26
creihtso wait... you will have to log into gerrit through launchpad openid?19:26
jeblairit hasn't shown up in this meeting, but we've also been helping folks integrate their local testing efforts into the openstack jenkins system19:26
jeblaircreiht: yes -- that way we can use launchpad's group system universally19:27
jeblairto manage ACLs in gerrit, jenkins, and launchpad19:27
creihtheh... alright.. just seems a bit wonky19:27
jeblairwe're aiming for "seamless".  :)  hopefully gerrit should have your group membership, username, real name, email address, and ssh key on your first visit19:28
jeblairso you don't have to do any registration, or otherwise duplicate effort19:29
creihtbut I will still have to log in to 2 systems19:29
creihtgithub and gerrit19:29
creihtbut I digress...19:30
*** dolphm has quit IRC19:31
jeblairadrian17od: we have moved openstack-ci to git19:31
jeblair#link https://github.com/openstack/openstack-ci19:31
jeblairi'm guessing we need to update the launchpad project to reflect that19:32
jeblair#action update launchpad project page for openstack-ci to point to github19:32
jeblairwe did that to eat our own dogfood with github and gerrit19:33
adrian17odthat's great. thanks jetblair19:33
jeblair#link https://github.com/openstack/openstack-ci-puppet19:34
jeblairwe put our puppet modules there as well19:34
jeblairso we've been reviewing changes to those with gerrit for about a week.19:34
jeblairit's not the same kind of use the other projects will see, but it does mean that we get to run into technical problems first19:35
jeblairdid i miss anything from anyone else?19:36
*** troytoman is now known as troytoman-away19:37
jeblairall right, i'll wrap it up then.  see you next week!19:38
jeblair#endmeeting19:38
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"19:38
openstackMeeting ended Tue Jul 26 19:38:23 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:38
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-07-26-19.04.html19:38
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-07-26-19.04.txt19:38
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-07-26-19.04.log.html19:38
jaypipescreiht: being logged in to two systems is all that bad? I'm logged into LP and GH pretty much all the time anyway.19:38
natibye :D19:38
jaypipesnati: hey, got some news for ya!19:39
*** joshuamckenty_ has joined #openstack-meeting19:39
natijaypipes: Wow!19:39
jaypipesnati, mtaylor: so.... looks like I've been able to secure hardware for FreeCloud. In addition, dendro-afk is working on getting 2 48-port switches donated from Cisco for the datacenter in Boston.19:39
natiCool!19:40
jaypipesnati, mtaylor: and looks like it will be more hardware than we originally planned for... 20 servers total.19:40
natiAmazing!19:40
jaypipesyeah, still waiting on a timeframe, but things are looking good..19:41
*** dolphm has joined #openstack-meeting19:41
natiI got visa,and I'll move SF at 8/1. :D19:43
natiIt is really good news, Thank you!19:43
jaypipesnati: hey, awesome! :)19:47
*** adjohn has joined #openstack-meeting19:48
natijaypipes: Thanks! Let's discuss about the details in freecloud meeting. :D19:48
jaypipesnati: sounds good :)19:50
*** dolphm has quit IRC19:52
*** dolphm has joined #openstack-meeting19:54
*** joshuamckenty_ has quit IRC19:55
*** zns has joined #openstack-meeting19:57
*** joshuamckenty_ has joined #openstack-meeting19:59
ttxDo we have a PPB meeting today ?19:59
ttx(Nothing on the agenda, loads of peeps at OSCON...)20:00
notmynameI'm not here (in an airport now)20:00
joshuamckenty_I'm available, but I think we're trumped by OSCON20:00
joshuamckenty_I sent out invites for the FITs working group20:00
joshuamckenty_Am late on the academic stuff20:00
notmynamejoshuamckenty_: are you at oscon?20:00
joshuamckenty_Will be late tonight20:00
notmynamesame here20:01
joshuamckenty_Nice.20:02
*** scott__ has joined #openstack-meeting20:03
*** jbryce has joined #openstack-meeting20:04
ttxjbryce: pass ?20:05
jbrycehello. any ppb members around?20:05
sorenish20:05
jbrycettx: i'm traveling to oscon and suffering from timezone confusion....20:05
*** dolphm has quit IRC20:05
jbrycei don't have any topics for this week20:05
ttxmight be difficult to get quorum today anyway20:06
jbrycei know john purrier is en route as well20:06
ttxfrom backlog you missed:20:06
ttx<joshuamckenty_> I'm available, but I think we're trumped by OSCON20:06
ttx<joshuamckenty_> I sent out invites for the FITs working group20:06
ttx<joshuamckenty_> Am late on the academic stuff20:06
jbrycethanks20:06
jbrycei'm fine with passing20:06
jbrycei did not finish my action item from last week which was to flesh out the autonomy statement and some more detail around vetted sets of options. hope to have it later this week and will put it on the list20:07
notmyname+1 for mailing list20:08
ttxlooks like "pass" wins20:09
jbryceall right20:09
jbrycenotmyname: you coming to portland?20:10
notmynamejbryce: in denver now waiting for my portland flight20:10
notmynameI'll land 5ish20:10
jbrycenotmyname: cool. my cell is 210-317-2438 if you want to connect later. there are quite a few rackers and openstack people arriving today20:12
*** jbryce has quit IRC20:13
*** nati has quit IRC20:14
*** Daviey has quit IRC20:14
*** dolphm has joined #openstack-meeting20:16
*** Daviey has joined #openstack-meeting20:17
*** Daviey has quit IRC20:22
*** dabo has joined #openstack-meeting20:28
*** Daviey has joined #openstack-meeting20:30
*** joshuamckenty_ has quit IRC20:32
*** shwetaap has quit IRC20:32
*** shwetaap has joined #openstack-meeting20:33
*** _adjohn has joined #openstack-meeting20:37
*** adjohn has quit IRC20:40
*** _adjohn is now known as adjohn20:40
*** thingee has joined #openstack-meeting20:41
*** clayg has joined #openstack-meeting20:45
*** msinhore has quit IRC20:45
*** User580 has joined #openstack-meeting20:51
*** User580 has quit IRC20:51
*** Tushar340 has joined #openstack-meeting20:52
*** Tushar867 has joined #openstack-meeting20:52
*** Tushar867 has quit IRC20:52
*** Tushar has joined #openstack-meeting20:53
*** primeministerp1 has joined #openstack-meeting20:53
*** Vek has joined #openstack-meeting20:55
*** mucawhite has joined #openstack-meeting20:55
*** danwent has joined #openstack-meeting20:56
*** jamesurquhart has joined #openstack-meeting20:58
*** joearnol_ has joined #openstack-meeting20:58
* ttx yawns20:59
*** asomya has joined #openstack-meeting20:59
dabottx: get some coffee!21:00
* Vek waves21:00
ttxnotmyname: can't see scotticus ?21:00
ttxjaypipes, vishy: around ?21:00
jaypipeso/21:01
*** joearnold has quit IRC21:01
vishyo/21:01
annegentleno yawning, that stuff's contagious.21:01
vishythat was kind of a painful fix21:01
cynb o/21:01
*** RamD has joined #openstack-meeting21:01
* Vek prepares a dirty sock for the next yawner21:01
*** scott__ is now known as scotticus21:01
ttxah, that clarifies it21:01
scotticussorry, didn't see my name didn't take.21:01
ttx#startmeeting21:01
openstackMeeting started Tue Jul 26 21:01:48 2011 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.21:01
ttxWelcome to the weekly OpenStack meeting...21:01
ttxToday's agenda:21:02
ttx#link http://wiki.openstack.org/Meetings/TeamMeeting21:02
*** troytoman-away is now known as troytoman21:02
ttx#topic Swift status21:02
*** asomya has left #openstack-meeting21:02
*** openstack changes topic to "Swift status"21:02
*** bcwaldon has joined #openstack-meeting21:02
ttxscotticus: hey!21:02
ttxSo we have a 1.4.2 release candidate standing in the milestone-proposed branch21:03
*** jk0 has joined #openstack-meeting21:03
ttxWhile trunk has been switched to 1.4.3 development21:03
ttxNo milestone-critical bug in https://launchpad.net/swift/+milestone/1.4.221:03
ttxSo... unless we have issues, are you OK if I release 1.4.2 Wednesday, as planned ?21:03
scotticusyes21:03
ttxcool :)21:03
ttxscotticus: do you already have plans/dates for the next milestone (1.4.3?) ?21:04
* creiht notes for the record that scotticus is stepping in for notmyname for those who do not know21:04
scotticusnot that i have noted.21:04
creihtwhile he is at oscon21:04
ttxcreiht: indeed21:05
ttxscotticus: Other announcements/comments ?21:05
*** adam_g has joined #openstack-meeting21:05
scotticusnope, thats all.21:05
scotticusthank you21:05
*** dendro-afk is now known as dendrobates21:05
ttxRaise your hand if you have questions on Swift...21:05
ttx#topic Glance status21:06
*** openstack changes topic to "Glance status"21:06
jaypipeshttps://launchpad.net/glance/+milestone/diablo-321:06
jaypipeshttps://launchpad.net/glance/+milestone/diablo-421:06
ttxdiablo-3 milestone branch was cut this morning21:07
ttxWe have 4 release-critical bugs on the list -- all assigned21:07
jaypipeswe're looking good on D3. got to get clayg's latest proposed bug fix in, and figure out some packaging snafus, but should be good to finalize by thursday21:07
ttxBug 816386 (jkoelker)21:07
uvirtbot`Launchpad bug 816386 in glance "test_scrubber functional tests fail on package build" [High,In progress] https://launchpad.net/bugs/81638621:07
ttxthis one is blocking PPA package builds, so needs to be fixed ASAP...21:07
jaypipesttx: the packaging crap is the stumbling block for two of those bugs... the S3 ones (boto versioning)21:07
*** adrian17od has quit IRC21:08
jaypipesttx: yes, I'm think jkoelker needs help from mtaylor or soren on that one.21:08
ttxApparently it's not just a timing issue, so you need some Ubuntu buildd foo to solve it21:08
jaypipesI'm think. Ugh, I'm tired...21:08
ttxsoren looks into it -- we might disable that specific test on buildds as a D3 workaround21:08
jkoelkerttx: yea i can't reproduce it on an ubuntu VM either,21:08
ttxjkoelker: no, it looks like it only happens on PPA build daemons21:09
vishyttx, jaypipes, soren: what is the best way to handle this: https://code.launchpad.net/~tr3buchet/nova/lp816612/+merge/69365 branch was made against trunk and went in but i think it should go in milestone as well21:09
ttxwhich makes debugging... a bit painful21:09
*** dolphm has quit IRC21:09
ttxvishy: anyone on openstack-release can approve it21:10
ttxvishy: will talk to you later21:10
jaypipesvishy: yeah, back off! :)21:10
vishyhehe, sorry jumped the gun a bit21:10
jaypipes:)21:10
ttxjaypipes: so you need to upgrade to boto2 to fix those s3 things ?21:10
ttxjaypipes: I pray it won't trigger as many issues as in nova21:10
jaypipesttx: ok, so I will work with soren on those two issues (3 of the 4 outstanding bugs..)21:11
jaypipesttx: Well, I'm not sure yet. All I know if the method signature of S3Connection.__init__() is different from 1.9 to 2.021:11
jaypipesttx: and the tests all pass on 2.0 and fail on 1.9. go figure.21:11
* ttx is getting a bit tired with boto, days are not long enough21:12
jaypipesyeah..21:12
ttxBug 71315421:12
uvirtbot`Launchpad bug 713154 in glance "S3 Backend doesn't support POST either." [Medium,In progress] https://launchpad.net/bugs/71315421:12
ttxBug 79471821:12
uvirtbot`Launchpad bug 794718 in glance "S3 requires seekable file. webob versions 0.9.8 through 1.0.7 make_body_seekable() method broken for chunked transfer requests" [Low,In progress] https://launchpad.net/bugs/79471821:12
jaypipesttx: yep, both boto.21:12
ttxok21:12
ttxBug 81498121:12
uvirtbot`Launchpad bug 814981 in glance "glance-api fails on image delivery: AttributeError: context" [Medium,Confirmed] https://launchpad.net/bugs/81498121:12
jaypipesttx: clayg gave a good solution to that one. I will work on that.21:13
ttxok, remember to land the fix in trunk before proposing it to milestone-proposed21:13
jaypipesttx: clayg's solution does not require packaging changes, thankfully..21:13
jaypipesttx: yep, will do.21:13
ttxiablo-4 plan at https://launchpad.net/glance/+milestone/diablo-4 looks reasonable21:13
ttxas in "just twice as many blueprints as the other milestones"21:13
jaypipesttx: yes, now that johannes and Vek are working with us ;)21:14
ttxjaypipes: Announcements, comments ?21:14
jaypipesttx: no21:14
VekI haven't looked at that bug 814981, but it relates to code I just merged into glance; fix is to update config files21:14
uvirtbot`Launchpad bug 814981 in glance "glance-api fails on image delivery: AttributeError: context" [Medium,Confirmed] https://launchpad.net/bugs/81498121:14
* ttx expects a busy wednesday.21:14
jaypipesVek: actually fix is to make request context noop-able...21:14
Veka more useful error message would probably be helpful, though...21:14
ttxRaise your hand if you have a question on Glance / for Jay21:14
Vekjaypipes: *nod*21:15
jaypipesVek: but have to solve the broader "how to upgrade ini/paste.deploy files" anyway..21:15
jaypipesVek: https://blueprints.launchpad.net/openstack-ci/+spec/glance-upgrade21:15
ttx#topic Nova status21:15
*** openstack changes topic to "Nova status"21:15
*** martine has quit IRC21:15
ttxvishy: yo!21:15
ttxdiablo-3 milestone branch was also cut this busy morning21:16
ttxWe have three release-critical bugs in the list, some needing urgent love21:16
ttxSee https://launchpad.net/nova/+milestone/diablo-321:16
ttxBug 81623621:16
uvirtbot`Launchpad bug 816236 in nova "Initial 'nova db sync' migration failure on mysql due to foreign key reference" [Critical,Triaged] https://launchpad.net/bugs/81623621:16
sorenAre the disabled unit tests part of that?21:17
ttxsoren: part of what ?21:17
soren"that" being "the set of critical bugs".21:17
sorenI guess not.21:17
vishysoren: they are not21:17
ttxsoren: list at https://launchpad.net/nova/+milestone/diablo-321:17
vishybut any that can be fixed would be great21:17
ttxI'll gladly accept any of them though :)21:18
ttxvishy: do you have a victim^Wassignee for that schema upgrade issue ?21:18
vishyso my question from earlier: the problem is that the fix is that it was done against trunk21:18
vishyttx: not yet21:18
ttxvishy: I has a quick look at it, but figured an SQL/sqlalchemy-migrate expert would fix it way faster than I could21:18
vishyit looks like there was a potential fix included21:19
* jaypipes hides21:19
vishyI actually haven't seen the bug manifest yet21:19
vishyso step one is reproducing it21:19
vishyperhaps it is oneiric only?21:19
adam_gi hit that migration bug on natty21:19
ttxsoren, jaypipes, mtaylor: anything preventing a branch from trunk to be proposed to milestone-proposed ?21:19
vishyadam_g: could you make a fix for it?21:20
* ttx is a beliver in DVCS "just works" magic21:20
sorenI'm not sure I understand what tha tmeans :-/21:20
jaypipesme neither.21:20
sorenIf you mean:21:20
vishyttx: the issue is that just merging it will merge in the other three branches that merged21:20
adam_gvishy: i was looking into it last night, but need to look at sqlachemy/migrate more to know how to fix it properly.21:20
soren"Can a branch that has been merged into trunk also be merged into somthing else", then yes.21:20
jaypipesvishy: ah...21:20
vishyso i don't know the best way to handle it in bzr21:20
vishyshould we do a feaux "cherry-pick"21:20
vishyand make a new branch?21:20
sorenYeah, that's fine.21:21
vishyand propose that one in?21:21
jaypipesvishy: no, I think the specific merge would have to be proposed to be merged into the milestone release branch...21:21
vishyjaypipes: you can't seem to do that through launchpad. i.e. propose just a specific revision21:21
sorenYou can't, no.21:21
vishyok i will remake trebs branch against milestone proposed21:21
jaypipesvishy: bzr merge -c REVNO21:21
vishyand propose that one against milestone21:21
ttxmtaylor: would the gerrit milestone-proposed magic you promised me solve that ?21:22
vishyanyone else around that wants to try to fix the mysql issue?21:22
primeministerp1what is is21:22
primeministerp1er is it again21:22
primeministerp1sorry21:22
ttxprimeministerp1: bug 81623621:22
uvirtbot`Launchpad bug 816236 in nova "Initial 'nova db sync' migration failure on mysql due to foreign key reference" [Critical,Triaged] https://launchpad.net/bugs/81623621:22
primeministerp1too many threads21:22
ttxpart of the "save the day, fix a RC bug !" campaign21:23
primeministerp1haha21:23
primeministerp1has someone reproduced it yet?21:23
primeministerp1sorry i can take that off line21:23
adam_gits easy to reproduce, install from trunk and try to migrate against a mysql database21:23
primeministerp1o ok21:24
adam_gmigrations against sqlite work fine21:24
tr3buchetisnt it the same as if you drop your database and start over?21:24
ttxadam_g: are you planning to work on it ? Would definitely be a good idea :)21:24
primeministerp1might be over my head but i'll try a poke at it21:24
ttxprimeministerp1, adam_g: ok, talk to each other to avoid duplication21:24
vishyadam_g: I've done that on maverick and it works btw21:24
adam_git would be easy to just remove with sqlalchemy migrate, however, its created with an autogenerated name does not match the name sqlalchemy use to find it on removal21:25
vishyadam_g: so it may be a natty+ issue?21:25
adam_gttx: i would like to, however, im at OSCOn currently and will not have a chance to look at it until tomorrow earliest21:25
ttxrha21:25
ttxwe'll get back to this one21:26
adam_gvishy: only tested on natty. will check at least oneiric this afternoon21:26
ttxBug 81436521:26
uvirtbot`Launchpad bug 814365 in nova "Should support boto 2.0 server-side (was: EC2 API fails with >=boto2.0)" [Wishlist,Confirmed] https://launchpad.net/bugs/81436521:26
ttxThis one also needs a friend, though I think vishy is closing on a solution21:26
ttxvishy: if you're close, maybe assign yourself to it21:26
vishyttx: I fixed it21:26
vishyttx: could use some reviews though21:26
mtaylorttx: yes21:26
mtaylorttx: branch from trunk to milestone-proposed is hard but possibly doable21:27
vishythat should fix oneric builds as well21:27
ttxvishy: so the cherrypicking stuff to milestone-proposed would probably be handled automatically in a gerrit new world order21:27
mtaylorttx: branch from milestone-proposed to trunk will soon magically happen21:27
mtaylorttx: ++21:27
ttxbug 810563 (tr3buchet)21:27
uvirtbot`Launchpad bug 810563 in nova "nova-manage lets you create broken networks (was: trying to add VLAN #100 to IF -:None:- error: No such device)" [Medium,Confirmed] https://launchpad.net/bugs/81056321:27
ttxtr3buchet: should propose a merge today for that one ?21:28
tr3buchetyes21:28
jaypipesvishy: fix looks good. I might have to go with a similar switch on boto.Version >= 2 in Glance as well..21:28
tr3buchetneed to make sure lvov's nova-manage stuff doesn't interfere (it shouldnt)21:28
*** _adjohn has joined #openstack-meeting21:29
ttxAny other candidates so far for the release-critical bug list ?21:29
vishytr3buchet: can you make the fix against milestone-proposed so it merges cleanly to both branches?21:29
*** msinhore has joined #openstack-meeting21:29
*** msinhore has quit IRC21:29
*** msinhore has joined #openstack-meeting21:29
tr3buchetsure thing21:29
tr3buchetis that two separate merge props then?21:30
*** liemmn has joined #openstack-meeting21:30
vishyyeah21:30
ttxtr3buchet: yes, though the other one is not "reviewed" in the same sense21:30
tr3buchetkk21:30
vishywoot cherry pick success https://code.launchpad.net/~vishvananda/nova/milestone816612/+merge/6936821:31
ttxprimeministerp1: if you want to poke at bug 816236, feel free to assign yourself to it21:31
uvirtbot`Launchpad bug 816236 in nova "Initial 'nova db sync' migration failure on mysql due to foreign key reference" [Critical,Triaged] https://launchpad.net/bugs/81623621:31
*** adjohn has quit IRC21:31
*** _adjohn is now known as adjohn21:31
ttxprimeministerp1: and maybe team up with adam_g on verification/reproduction21:31
primeministerp1ok21:32
primeministerp1see if i can help21:32
vishyappreciate it guys!21:32
ttxI'll try to pick the resulting pieces tomorrow morning21:32
primeministerp1we at misc stuff yet21:32
vishyif you have trouble, ping me21:32
primeministerp1have some hyperv notes to add21:32
adam_gprimeministerp1: i can pair with you on that one, i spent some time looking at it and have a good idea whats going on21:32
*** salv has joined #openstack-meeting21:32
primeministerp1we had some major progress w/ netwroking21:32
primeministerp1we have scripts now to build virtual switches on windows core21:32
ttxprimeministerp1: still on nova21:33
ttxjust a sec and I'll pass to open discussion21:33
primeministerp1we'll i'm speaking of nova-compute21:33
primeministerp1kk21:33
ttxquick note about nova diablo-421:33
ttxDue to all deferrals, plan for diablo-4 at https://launchpad.net/nova/+milestone/diablo-4 looks very unrealistic21:34
ttxSo I guess we'll trim it once diablo-3 is out of the door.21:34
ttxvishy: more comments ?21:34
ttxprimeministerp1: please continue :)21:34
primeministerp1o21:35
primeministerp1sorry21:35
primeministerp1so21:35
primeministerp1we had to drill some hyperv dev's to get the wmi21:35
primeministerp1and the sripts21:35
primeministerp1er script21:35
primeministerp1however21:35
primeministerp1we can now automate the building of the virtual switch on hyperv21:35
vishyprimeministerp1: cool!21:36
primeministerp1i know jordan was working on this stuff as well21:36
primeministerp1but he must be out21:36
primeministerp1hasn't gotten back to me21:36
primeministerp1anyway21:36
ttxprimeministerp1: did you sync with mtaylor on hooking your test rig to the Jenkins infra ?21:36
primeministerp1we still need to21:36
primeministerp1we needed to get this piece first21:36
tr3buchetttx: i've got a question about a flag in the nova-manage command. i'd like to change "--flat_network_bridge" to just "--bridge". the flat network part is a misnomer21:36
primeministerp1we want to move to all windows core21:36
primeministerp1for the hypervisor os21:36
primeministerp1and unfortunately21:37
primeministerp1you apparently couldn't configure networking21:37
primeministerp1on core21:37
primeministerp1properly21:37
primeministerp1but....21:37
primeministerp1now we can21:37
primeministerp1so i also wanted to share the wmi21:37
primeministerp1with jordan21:37
primeministerp1i know he was looking into the networking for hyperv21:38
ttxtr3buchet: so far we handled backward compat in nova-manage quite badly, so I guess one more break can't hurt... vishy might disapprove though21:38
vishytr3buchet: seems fine, no one is using that new style yet anyway21:38
ttxso that's ok ;)21:38
vishy(it just went in last night) :)21:38
tr3buchetvishy ttx: well i wanted to do it before the milestone so people don't start scripting against it21:38
ttxprimeministerp1: sounds good, just try to corner him somewhere21:38
tr3buchetor less people do anyway21:38
vishyagreed, change with your fix for that bug21:39
primeministerp1heheh21:39
salvprimeministerp1: will these scripts enable us to do VLAN networking in Hyper-V as we do with libvirt, xenapi, and ESX?21:39
tr3buchetvishy: will do21:39
primeministerp1yes21:39
primeministerp1it should21:39
primeministerp1we just need the right wmi21:39
primeministerp1and it might help us get bits of that as well21:39
ttxOther questions on Nova ?21:39
salvyou mean WMI script or object?21:39
sorenYes.21:39
ttxsoren: go ahead21:40
sorenI'd like to talk about the disabled unit tests.21:40
sorenI'll make it very short:21:40
sorenwtf?21:40
sorenDiscuss.21:40
tr3bucheti guess i started that one21:40
creihtyou should add a rule to tarmac to check for commented out unit tests21:40
creiht;P21:40
sorenWe should.21:40
sorenReally.21:40
* creiht shakes his head and hides in the corner21:40
sorenWe decided at the summit that noone was allowed to decrease test coverage.21:40
sorenYet here we are.21:41
tr3buchetbasically the vmware code doesn't work with nova since multinic21:41
vishysoren: the idea was to get multinic in because it was likely to cause some breakages, hoping that others could help in fixing the broken tests21:41
tr3buchetso their tests obviously don't either21:41
sorenSo why rush it?21:41
sorenWhy not fix those tests first?21:41
tr3buchetbecause we'd have to fix vmware21:41
sorenSomeone would.21:41
tr3buchetbut who?21:41
sorenif noone cares, rip the darn thing out.21:41
tr3buchet+121:42
sorenThis is not about VMWare.21:42
sorenThis is about the general problem.21:42
tr3bucheti agree, i just picked that one o ut of the blue21:42
sorenWhy does a new feature make it ok to disable tests?21:42
tr3buchetthe issue is handling things that change in nova which break many contituent pieces21:42
tr3buchetconstituent*21:42
sorenWhen people offer new patches and we ask them to provide tests as well, the reason I at least tend to give is that it's so that I don't break their stuff when I write new code.21:43
soren...but that really doesn't work if I just disable their tests if I happen to break their stuff anyway.21:43
ttxWe should at least have targeted the resulting issues to the milestone, to make sure I annoy people enough so that they fix the disabled tests21:43
ttxDiscovering them late was a problem21:43
sorenWe're basically saying "Our use case is more important than anyone else's."21:44
vishyagreed we definitely should have focused more on fixing the tests that broke21:44
sorenAnd that's bs.21:44
*** somik has joined #openstack-meeting21:44
tr3buchettrue21:44
tr3bucheti had assumed that the hypervisors would be quickly updated, and the tests rewritten21:45
sorenIf a test is not *supposed* to work anymore, then fine. Remove it. Disabling it because you broke it... Not fine.21:45
tr3buchetwell it isn't that we broke the testas21:45
tr3buchettests21:45
tr3buchetit's the the code the tests test is broken21:45
sorenThe way I see it, if someone thinks a feature is important enough they should spend the extra time getting the tests sorted out (or bugging others to help them get the tests sorted out).21:45
ttxsoren: I'm with you on this one, but to tr3buchet's credit, we kinda anticipated that things would break in areas where he couldn't fix them (aka "less-supported hypervisors")21:46
tr3buchetsoren: i agree if it were only about the tests21:46
sorenI have trouble imagining a feature that's important and cool enough that it warrants breaking a bunch of other things.21:46
creihtwho supports the vmware hypervisor?21:46
sorenThings whose authors took the time to write unit tests for, no less.21:46
vishysoren: disagree, I think there are some features21:46
vishythat are that important21:46
salvbut if code on less-supported hypervisors is now broken, as tr3buchet says, does this mean the less-supported hypervisors are broken as well?21:47
sorenIf there's a feature that we generally think is really important and it requires changes across the board, but noone wants to fix e.g. the VMWare driver... We remove the VMWare driver.21:47
tr3buchetsalv: until they are updated, yes21:48
creihtperhaps you need a chart like the JS frameworks have, where you have "1st class" hypervisors that are guaranteed to work, and others that work to as much as can be supported21:48
sorenUntested code == broken code.21:48
vishysoren: it was more that we didn't want to hold up the wmerge to wait for VMWare to be fixed21:48
sorenI think talking about VMware is bs.21:48
vishysoren: keeping a large change unmerged while the code is plowing ahead is extremely painful21:48
sorenThe libvirt driver got the same treatment.21:48
sorenAnd I can promise you that someone cares about libvirt.21:49
primeministerp1spectorclan:  question on the design summit?21:49
sorenMaybe not VMWare.21:49
sorenI don't care much about VMWare.21:49
tr3buchetsoren all of the hypervisors got the same treatment, except the one I know how to code for21:49
salvWell, this does not mean we should leave it to rot.21:49
tr3buchetthere are lieutenants for all the rest21:49
sorenvishy: Doing things right is painful sometimes. Writing tests is painful. But it's worth it.21:49
salvPeople who developed it are still active in the project. Have they been contacted for multi-nic integration?21:49
tr3bucheti spent time working with grid dynamics and some of the titan guys to get libvirt working as well21:49
sorensalv: Not at all, but if noone cares enough to maintain it, kill it.21:50
ttxhmm, ok we failed, recommendations on how to fix the mess ?21:50
*** agarwalla has joined #openstack-meeting21:50
sorentr3buchet: The unit tests remained disabled.21:50
alekibangonote: its best to start by tests!21:50
ttxand on how not to do it ever again ?21:50
tr3buchetsoren: no one is disagreeing with what you are saying about tests being important21:50
salvsoren: people do care, and there are people maintaining it!21:50
sorensalv: Great!21:50
vishysoren: so you feel that we should delay the merge until someone volunteers to fix the broken tests...21:51
sorentr3buchet: "important" seems to mean different things, then.21:51
tr3buchetbut if the tests for libvirt are being skipped for whatever reason in trunk, the libvirt lieutenant needs to see to that21:51
vishysoren: clearly this feature would never land21:51
tr3buchetthis is true21:51
sorenvishy: I call total bs on that.21:51
vishysoren: are the tests fixed?21:51
sorenvishy: No.21:51
*** agarwalla has joined #openstack-meeting21:51
vishysoren: it has been a whole month21:52
*** carlp has joined #openstack-meeting21:52
vishysoren: with people seeing the skips every day21:52
*** dendrobates is now known as dendro-afk21:52
sorenRefresh my memory:21:52
tr3buchetand obviously not caring...21:52
tr3buchet(or not caring enough)21:52
sorenDid we not all agree at the design summit that we'd increase test coverage for this release?21:52
tr3buchetwe did21:52
*** midodan has joined #openstack-meeting21:52
sorenOk.21:52
tr3buchetlook this is not about tests21:53
sorenThis is all about tests.21:53
tr3buchetit's about the code that is broken. the tests are being skipped because that code is broken21:53
sorenYes.21:53
tr3buchetwho is in charge of fixing that code, and afterwards, getting the tests to work21:53
sorenAnd the tests are supposed to expose that!21:53
sorenThat's the point of tests!21:53
vishyactually21:53
vishyin the case of libvirt21:53
sorenTests are supposed to expose when things are broken, not rub your back when things are fine.21:53
vishyit is the tests that are broken21:53
vishylibvirt works fine21:53
sorenHow do you know?21:53
vishybecause i use it and do smoketests against it21:54
Vekwould you prefer that the code be merged and the tests allowed to fail until the code is either fixed or removed?21:54
tr3buchetah that's true, there are some libvirt tests still be skipped21:54
sorenVek: Good god, no.21:54
* ttx whistles innocently and pushed to the next agenda item before there is no time left21:54
vishythey were skipped because tr3buchet didn't have the expertise to fix them.21:54
ttx#topic Open discussion21:54
*** openstack changes topic to "Open discussion"21:54
tr3buchetcorrect!21:54
sorenNot having expertise is fine.21:55
tr3buchetlook before this goes on: " < ttx> hmm, ok we failed, recommendations on how to fix the mess ?"21:55
sorenso you ask for hlep.21:55
sorenhelp, even.21:55
tr3buchetlet's discuss ttx's idea21:55
TusharI think  skipped libvirt test are fixed in merged prop:https://code.launchpad.net/~rohitkarajgi/nova/libvirt_unittests/+merge/6814421:55
ttxsoren: it was symptomatic of our inability to work as a unified project21:55
sorenI'm not sure we can.21:55
soren...because there doesn't seem to be consensus that there's a problem.21:55
vishysoren: to be fair, he asked for help many times21:55
tr3buchetwho here wants for there to be skipped tests?21:55
*** scotticus has left #openstack-meeting21:55
Vek-121:55
soren-121:56
*** zns has left #openstack-meeting21:56
tr3buchetconsensus reached21:56
tr3buchetlet's fix skipped unittests21:56
tr3buchetplan?21:56
sorenthat's not what I'm saying.21:56
sorenYes, we should fix them...21:56
soren...but they should never have been allowed to break to begin with.21:56
vishysoren: You would like a rule saying no putting skipped tests in trunk21:57
sorenAbsolutely.21:57
Davieyhorse + barn door = bolt.21:57
vishysoren: I'm ok with that but I think in this particular case it would have slowed us down tremendously21:57
tr3bucheteasy enough: remove the decorator, watch em all fail, get to work.21:57
ttxsoren: which brings back the issue of how to work across knowledge domain to push such a large change affecting multiple hypervisors in21:57
*** ryu_ishimoto has joined #openstack-meeting21:58
sorenvishy: It might.21:58
*** mucawhite has left #openstack-meeting21:58
vishysoren: all of the network stuff was dependent on multi_nic21:58
sorenThat's where the motivation to fix it comes in.21:58
*** EdgarPerdomo has joined #openstack-meeting21:58
DavieyIf someone lands a feature, are they responsible forever on to make sure it's updated to work on-par with the latest core changes?21:59
salvtr3buchet: ask people who developed ESX support to fix them21:59
ttxWe have to stop now, next meeting needs the room21:59
tr3bucheti brought this up many times before21:59
ttxI propose we continue to discuss how to avoid such situation in the future, in a future meeting21:59
VekDaviey: and if that person gets hit by a bus tomorrow, God forbid?21:59
ttxI'd like to make sure we can recover from the current mess though21:59
sorenDaviey: They are not.21:59
vishyI will attempt to fix the test_cloud tests22:00
sorenDaviey: That's why they provide unit tests and we do code review.22:00
Davieysoren: the 'breaker' has to do it? right?22:00
Davieyor at least co-ordinate it22:00
ttxvishy: maybe target all the bugs to diablo-4 to make sure they are on the radar22:00
*** Jamey has joined #openstack-meeting22:00
sorenDaviey: Code review should make sure that more people understand the code, and the unit tests are there to make sure that we don't accidentally break it anyway.22:00
tr3bucheti am available to assist (from the network side) anyone wanting to fix tests22:00
sorenDaviey: Absolutely.22:00
tr3buchetwasn't this way we made lieutenants?22:00
tr3buchetwhy*22:01
ttxsoren: the issue of how to push wide changes is certainly interesting, and I'd like to discuss it more22:01
ttxsoren: but enough for this meeting22:01
*** ying has joined #openstack-meeting22:01
ttx#endmeeting22:01
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"22:01
openstackMeeting ended Tue Jul 26 22:01:30 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-07-26-21.01.html22:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-07-26-21.01.txt22:01
*** SumitNaiksatam has joined #openstack-meeting22:01
sorenGetting complicated changes into already complicated code is complicated. News at 11.22:01
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-07-26-21.01.log.html22:01
danwentttx: thanks :)22:01
salvHi Dan!22:01
danwenthello netstackers :)22:02
markvoelkero/22:02
ttxdanwent: almost on time.22:02
*** Vek has left #openstack-meeting22:02
SumitNaiksatamGreetings!22:02
adjohnHello hello22:02
somikHello!22:02
ryu_ishimotohi everyone!22:02
danwentttx: you all have priority, but I appreciate the consideration22:02
troytomanHi all22:02
jk0o/22:02
*** asomya has joined #openstack-meeting22:02
carlpafternoon all22:02
jamesurquhartHey, Dan. Rick can't make meeting as he has OSCON duties. He is sending you and/or me updates, depending on connectivity. :)22:02
danwentchatty crowd today, I like this.22:02
*** bcwaldon has quit IRC22:02
creihtI think ttx was just tired of talking about it :)22:02
*** thingee has left #openstack-meeting22:02
danwentjames: thx, good to know.22:02
danwentok, let's get started22:03
danwent#startmeeting22:03
openstackMeeting started Tue Jul 26 22:03:09 2011 UTC.  The chair is danwent. Information about MeetBot at http://wiki.debian.org/MeetBot.22:03
ttxcreiht: nah! But I feel guilty too, since tr3buchet asked me how to best handle this22:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.22:03
danwentagenda: http://wiki.openstack.org/Network/Meetings22:03
danwent#topic netstack updates22:03
*** openstack changes topic to "netstack updates"22:03
danwentI sent an email out about the lack of a license file in quantum22:03
danwentI believe this was just an oversight, but wanted to check if there were any concerns about adding one.22:04
danwentI am not sure if this applies to melange and donabe as well, so wanted to bring it up for nestack as a whole22:04
*** creiht has left #openstack-meeting22:04
danwentOk.... sounds like we'll add it so we're aligned with nova and swift as far as licensing22:04
* markvoelker hears crickets22:04
troytomansounds like a good idea. we'll look at it for Melange22:04
jamesurquhartNo problems here.22:05
danwentanything else netstack wide?22:05
*** dabo has left #openstack-meeting22:05
jamesurquhartI'll forward to Rick for Donabe.22:05
danwent#topic quantum22:05
*** openstack changes topic to "quantum"22:05
danwentjames: thx22:05
danwentfirst, unit test status22:05
danwentwe're holding off merging things until the unit tests are clean, but I believe we have both the extensions and the client lib that are close to being ready to land, so I wanted to find out if there were any unit test blockers22:06
danwentsalvatore: I know you have fixes for some already22:06
somikI believe salvatore has created bugs to track unit test issues22:06
salvdanwent: Unit tests branch is merged. Many of them fail, for well-known bugs22:06
somikand the plan was to treat those bugs with highest priority before merging new features.22:07
salvA branch for fixing failures in unit tests is already proposed for merge22:07
danwentok, just waiting on review?22:07
salvyes.22:07
danwent#action core-devs need to review unit test fix branch22:07
salvafter merging that branch, 7 unit tests will still fail. I've created bugs for tracking those failures as well. Unfortunately I still don't have a fix for this.22:08
salvthe branch is lp:~salvatore-orlando/quantum/quantum-api22:08
danwentsalv: is it that we just haven't had the cycles to fix, or are there major questions?22:08
danwenti.e., could anyone pick off those tests?22:08
salvdanwent: they haven't been fixed because I took some days off last weel :)22:09
salv*week22:09
danwentsalv: you shouldn't have to be the only one fixing :P22:09
salvthe bugs are there... anyone can pick them :)22:09
danwentok, i see 4 that are "in progress"22:09
danwenthttps://bugs.launchpad.net/quantum22:10
salvthe bugs are #814012 and #81451722:10
jamesurquhart*enjoys listening to the crickets*22:11
danwentah, looks like the page I was viewing doesn't show them by default....22:11
*** ying has quit IRC22:11
danwentsilly launchpad.22:11
markvoelkersalv: I'll see if I can get some of my guys to break off some cycles to look at these this week....22:11
salvOn unit tests, dan in his wiki page made an interesting point on plugin-specific unit tests22:12
salvmarkvoelker: thanks!22:12
*** ying has joined #openstack-meeting22:12
salvI have been contacted by some developers asking me about them.22:12
danwent#action: target fix for #81401222:12
danwent#action target fix for #81451722:12
danwentmarkvoelker: thanks.  Please assign the bugs to you if you start working.  I'll try to get some cycles on them as well.22:13
markvoelkerdanwent: will do22:13
danwentyes, created a page on Quantum testing in general: http://wiki.openstack.org/QuantumTesting22:13
salvI think that if the plugin is part of the quantum source code tree, it makes sense to have unit tests. The only open question for me is whether this tests should be in the "tests" directory or in a plugin-specific directory22:14
danwentplease add your thoughts and comments.22:14
danwentsalv:  my thinking was that they would be in the plugins directory.22:14
salvdanwent:: agrred22:14
danwentsalv: but that's more of a gut feeling22:14
*** dendro-afk is now known as dendrobates22:15
danwentanyone have concerns with plugin-specific unit tests being in the plugin's directory?22:15
danwentrather, the plugin's own directory22:15
carlpdanwent: I think that makes sense22:15
*** gaitan has quit IRC22:16
danwentK.  Then we'll need to figure out how to make our unit-testing framework scan for an load them.22:16
jamesurquhartSeems logical to me. However, will they still be executed by default if that plugin is included in a test environment, or will they be executed separately?22:16
jamesurquhartdanwent: read my mind22:16
danwentjames:  my thought was that they would be executed by default.22:16
danwentwe want to be able to identify if a change to the main quantum code breaks a plugin.22:16
danwentbut this means that a plugin must be able to run on most people's system, at least well enough that they can confirm that unit tests pass22:17
SumitNaiksatamdanwent: good point22:17
jamesurquhartAlso, plug-in will likely have extensions that core Quantum tests won't understand.22:17
danwent(i.e., if you plugin has some crazy dependency, most devs won't install it, and then they won't know that they did something to break it)22:17
danwentthis isn't all that different than the previous nova discuss (duck!)22:18
carlplol22:18
SumitNaiksatamthese tests should work with a "default" plugin22:18
danwentsumit: certainly22:18
danwentbut ideally we'd even get coverage across other plugins22:19
SumitNaiksatamthere should separate tests for specific plugins (which can be run on demand)22:19
jamesurquhartIsn't it the plug-in developers responsibility to determine if a change to Quantum core breaks their plug-in?22:19
SumitNaiksatamjames: +122:19
somiki agree that individual plugins that are not part of quantum shouldnt be run by default.22:19
salvjames +1 with a but...22:19
somikespecially if the plugin requires some infrastructure that will not be available in jenkins22:19
*** Shubhangi has quit IRC22:19
salvWe should at least make sure that the plugins keep consistent with the interface enforced by Quantum22:20
jamesurquhartsomik: However, if the plug-in is installed, the test framework should find the unit tests for that plug-in and run them22:20
danwentjames:  that would be one path to go down.  certainly easier for other developers.  but it could lead to thinks being merged into trunk that break a particular plugin without that main quantum developer knowing it.22:20
somikjames: correct, agreed22:20
SumitNaiksatamdanwent: in that case still the responsibility of the plugin-developer22:20
danwentI think for now we can assume plugin unit tests are executed separately (e.g., we only load the unit tests for the plugin defined by the conf file)22:21
jamesurquhartdanwent: Not sure how I can see that being avoided except every core Quantum dev installing every plug-in…22:21
SumitNaiksatamdanwent: +122:21
danwentjames: I agree.... I was just trying to figure out if there might be a way around it, as its not ideal.22:21
danwentbut I think this is the best place to start.22:21
*** dragondm has joined #openstack-meeting22:21
jamesurquhartThen again, I'll admit some naivite when it comes to unit testing in OpenStack22:21
SumitNaiksatamplugins-specific tests can go in a plugin-specific directory22:21
danwentno need to design a solution to a problem that's only hypothetical anyway :)22:21
SumitNaiksatamthat can include tests for extensions as well22:22
jamesurquhartdanwent: Oh, c'mon. That's the definition of "silicon valley" ;)22:22
danwent:)22:22
jamesurquhartSumit: +122:22
danwent#action danwent create blueprint/bug to make unit test framework load tests for the "active" plugin.22:22
danwentok, anything else on testing?22:23
salvdanwent: we can bring this offline, but I see the concept of active plugin as something which has more to do with functional/system testing22:23
salvrather than unit testing22:23
danwentsalv: i see where you're coming from, I think it really just comes down to whether you can assume everyone is able to even load everyone else's plugin in order to execute system tests and commit code.22:24
jamesurquhartsalv: Include me. Unit testing of plug-in is for the plug-in, not Quantum, but may be dependent on Quantum tests.22:24
danwentlet's move this to the list?22:24
jamesurquhartYes22:24
salvyes22:24
danwentgreat.22:24
danwentSalv: you have an action item to review the API spec page and try to bring it inline with the implementation?22:25
*** glenc_ has joined #openstack-meeting22:25
danwentI believe there's already a bug for this, right?22:25
danwenthttps://bugs.launchpad.net/quantum/+bug/81343322:25
uvirtbot`Launchpad bug 813433 in quantum "Align API implementation with specifcation" [Undecided,New]22:25
salvI've reviewed the API spec and updated the wiki page. The bug has been created, but no progress on the code22:25
danwentanswering my own question :)22:25
danwentok, nothing else on that topic then.22:26
danwentNova work:22:26
*** joearnol_ has quit IRC22:26
danwentfirst off, congrats to ryu for sheparding in the vif-plugging code into D-322:26
salvthe API spec is much nicer now. And Troy sent an interesting feedback on the mailing list. Hope to reply ASAP.22:26
danwentit is now in trunk22:26
ryu_ishimotothe VIF plugin work was merged!22:26
salvcheers!22:26
ryu_ishimotowhew!22:26
SumitNaiksatamryu: great job!22:26
danwenthooray :)22:26
somikthanks ryu!22:27
ryu_ishimotothanks, esp Dan for your help!22:27
*** glenc has quit IRC22:27
danwentadditional vif-plugging is now possible, you don't even have to modify nova code if you don't want to.22:27
carlpthat's the best news I've heard all week22:27
danwentyou can just use the flag-file to point to a python class that implements the vif-plugging API for the particular virt driver.22:27
danwentvery cool stuff.22:28
salvVIF-plugging is supported for libvirt and xenapi, is that correct?22:28
danwentsalv: yes22:28
danwentsalv: we're looking for people to do it for vmware + hyperv as well, if that makes sense (we didn't have a pressing use case)22:28
salvI hope to get someone to work on ESX, but as you might have read from the previous meeting, it is going to be thougher than expected22:28
danwent:P22:29
*** mattray has quit IRC22:29
danwentD-4 will be a pretty busy period for quantum-related changes in nova.22:29
salvBasically for both ESX and Hyper-V we first need to support multi-nic, and then we can do vif-plugging.22:29
danwentryu will be doing some additional network refactoring work.22:29
danwentryu, you are targeting the changes that make all network access via the network API, correct?22:30
ryu_ishimotodanwent: yes that is my plan22:30
danwentgreat.22:30
ryu_ishimotoas well as VIF REST OpenStack API22:30
danwentYup.22:30
danwentWe also have the other blueprint, which we bumped from D-3 to D-4: https://blueprints.launchpad.net/nova/+spec/implement-network-api22:31
danwentno spec yet, but will update it soon22:31
ryu_ishimotodanwent: great thanks22:31
salvdanwent: I also saw you created a quantum blueprint for standardazing plugin/agent communication, is that correct?22:31
SumitNaiksatamdanwent: is there a place where we can lookup all that is lined up for D4?22:31
danwentthis work will focus on actually making calls to the quantum api22:31
danwentI will be updating the blueprint spec soon.22:32
salvSumitNaiksatam: https://launchpad.net/nova/+milestone/diablo-422:32
troytomanryu_ishimoto: do you have a blueprint for the VIF API ? we have been thinking about this too22:32
danwentsalv: yes... that has been behind the nova work so far.22:32
danwentsumit:  with respect to quantum, it is the above blueprint, plus ryu's original blueprint22:33
danwentryu, have a link?22:33
SumitNaiksatamsalv: thanks, meant Quantum22:33
SumitNaiksatamdanwent: thanks22:33
ryu_ishimototroytoman: not for VIF plugin, but there is one for network refactoring in general22:33
RamDhow about quantum related work..example:Openstack-dashboard changes for quantum, may be a nova-mange CLI support for Quantum and so on..where are we tracking22:34
danwentsumit: ah, I've just started putting together a potential roadmap... thinking more in terms of what we want to have for D6, then we can work backward.22:34
troytomanryu_ishimoto: we have been working on a proposal to expose /interfaces in the Nova API in the future. we should probably sync up22:34
danwentjust brainstorming right now: http://wiki.openstack.org/QuantumRoadmap22:34
*** glenc_ is now known as glenc22:34
RamDtroytoman: me interested as well...22:35
RamDdanwent: Cool Thanks22:35
danwentnetstack list ;)22:35
ryu_ishimototroytoman: https://blueprints.launchpad.net/nova/+spec/network-refactoring this is the blueprint22:35
ryu_ishimototroytoman: yes, let's do that22:35
RamDyep, netstack list :-)22:35
troytomanRamD, ryu_ishimoto: trying to get something out to mailing list but may circulate something to a smaller group initially22:35
danwentRamD:  I actually have been thinking that we may create quantum blueprints that track work happening in nova + dashboard that are critical to quantum deliverables.22:36
danwentthey would really just be "references" to other blueprints, but would make it easier for people to see everything we're hoping to deliver, even if the actual blueprint is elsewhere (e.g., in nova).22:36
RamDdanwent: I think its a good idea...that way you can include Quantum BPs to Quantum milestones22:36
danwentRamD:  yes, am hoping to start using milestones for D-4....22:37
danwentthough with my luck, the second i figure out how they work, we will shift to github :P22:37
RamDYep..let's take it to netstack and decide and agree for D422:37
danwentOk, anything else on quantum-related changes for nova?  expect some significant BP action on this in the next week or two.22:38
RamDIs there a plan for Quantum to move to github22:38
danwentRamD: ASAP :)22:38
danwentI'm assuming we'll move when the "bulk" of openstack moves22:38
SumitNaiksatamcan we postpone it to past diablo?22:38
salvdanwent: I don't want to lose my launchpad Karma points :) I was hoping to convert them into an Amazon voucher...22:38
danwentI think they are still kind of beta testing it on a few projects like dashboard.22:38
SumitNaiksatamunnecessary distraction22:38
danwentsalv: haha...  I think i have the most to lose there, but I still want to move to github :)22:39
danwentsumit:  definitely understand the concern.22:39
RamDSumit: +122:39
*** Shubhangi has joined #openstack-meeting22:39
danwentsumit: we'll see what openstack does.  It may be that we actually stay with launchpad for planning, I'm not sure.22:39
RamDbut if the openstack itslef moves we move as well, I guess22:39
danwentdoes anyone have more insight on this?22:39
* markvoelker has a little22:40
troytomankeystone has already moved22:40
*** joearnold has joined #openstack-meeting22:40
danwent#action danwent check with openstack folks about timing of move to github22:40
markvoelkerKeystone and Dashboard have moved already and mtaylor has some work going on wrt migration22:40
danwentI'm actually wondering if it might be MORE disruptive to do it around the time of a design summit... not sure.22:40
markvoelkerCode hosting and reviews would move, but most everything else is staying in LP IIRC.22:40
danwentsalv, your karma is safe :P22:41
* salv loves this discussion but thinks the ML is a better place for it22:41
danwentmark: thanks, that's good to know.22:41
danwentOk, done with nova22:41
danwentExtensions:22:41
troytomanwe should reach out to mtaylor and start the discussion. he's on point for migrations22:41
danwentI think this is proposed for merging?22:41
troytomanyes22:41
danwenttroy: sounds good, thanks.22:41
troytomanthe team pushed the merge prop this morning22:41
danwentso its lined up behind the unit test fixes?22:42
danwent(extra incentive :P)22:42
yingWe have tried with the latest extension framework, it works with our extensions22:42
danwentOk, if you're looking to review the extensions stuff again, please let it be known.22:42
danwentying: great to hear22:42
yingI'm reviewing the code and will provide more comments22:43
danwentOK, let's get reviews in during the next couple days, so we're ready to merge end of week if possible.22:43
yingdanwent: sure22:43
*** shwetaap has quit IRC22:44
danwentOk, client lib & GUI22:44
danwentI saw some sweet screenshots on the wiki22:44
danwentmark?22:44
asomyaPut some screenshots in this morning at :22:44
asomyahttp://wiki.openstack.org/QuantumClientGUI22:44
markvoelkerYes.  Check the whiteboard here:22:44
markvoelkerhttps://blueprints.launchpad.net/quantum/+spec/quantum-client-gui22:44
markvoelkerHas links to screenshots and some info on Arvind's net branch in GitHub22:44
markvoelkerThe screenshots are from an earlier rev so quite a bit has changed, but should give you a good idea22:45
markvoelkerWe'll update those as things develop this week22:45
asomyaThe screenshots are still based on the older dashboard code that has since undergone significant facial and structural changes.. the new one looks a lot better :)22:45
asomyaPreliminary integration of quantum + dashboard available here: https://github.com/CiscoSystems/dashboard-quantum-beta22:46
danwentGreat.  I think there is still some discussion about exact how interface-ids + network-ids will be exposed and bound to each other (per Ryu + Troy's previous comments)22:46
*** adam_g has left #openstack-meeting22:46
danwentso it would be good if you all are in the loop about that as well.22:46
RamDdanwent: How/where its being discussed? Netstack??:-)22:47
danwentI think from the screenshots it looks like you are using the VM name as the interface-id for now?22:47
danwentRamD: discussion hasn't started yet, but Troy and Ryu just said they wanted to talk about it.22:47
asomyaBased on the old nova code before multi nic.. it only exposed instances22:47
troytomanramd: hasn't been discussed yet. will be discussed because I think we are all thinking about it22:47
danwentSuch discussions should happen on netstack.22:47
SumitNaiksatamdanwent: +122:47
troytomanwill probably have to be on the openstack list because it involves Nova22:47
SumitNaiksatamkindly cc the netstack mailer22:47
RamDdanwent: on the interface-ID ..one thing we were thinking was to have option to add labels22:48
*** ying has quit IRC22:48
danwentRamD: can you expand?22:48
danwentor better yet, send an email to the list22:48
danwentas we're running out of time22:48
danwentAPI auth22:49
markvoelkerdanwent: Sure, throw a #action in for us to take that to the list and we'll make it so.22:49
salvdanwent: no progress on auth on my side. Have you heard from Keystone people?22:49
danwent#action markvoelker, ramd send email to netstack about labels with interface-id22:49
RamDin addition to a "quantum" spefic GUID, have a "facilty" to add labels..example my network external 1 for the client22:50
danwent#action troy, ryu, initiate discussion about interface-id, flow on netstack.22:50
*** ying has joined #openstack-meeting22:50
primeministerp1#freecloud22:50
danwentsalv: yes, I have a half written email on auth.  we can discuss more on the list.  Still need to think through it some more.22:50
primeministerp1whoos22:50
primeministerp1p22:50
danwentanything else on quantum?22:50
danwent#topic melange22:51
*** openstack changes topic to "melange"22:51
danwenttroy?22:51
danwentok, well troy mentioned that he and some of the nova devs are starting to work on integrating melange code into nova22:51
danwentsounds like nothing else to update on melange22:52
danwent#topic donabe22:52
*** openstack changes topic to "donabe"22:52
danwentany updates here?22:52
troytomandanwent: sorry slipped over to another conversation :-)22:53
danwentok, back to melange22:53
danwentignoring me again, huh troy?22:53
troytomannot much to update on melange, we're getting blueprints updated and specs put together22:53
troytomanplan to try and get the code dropped into the Nova project in D4.22:53
danwentk, great.22:53
troytomanthen look at how to start integrating it into the Nova system for managing IPs22:54
*** msinhore has quit IRC22:54
danwent#topic open discussion22:54
*** openstack changes topic to "open discussion"22:54
jamesurquhartDonabe: Rick will send details, but he told me a framework branch has been checked in, and APIs will be checked in as early as next week.22:54
troytomanwill probably just focus on the initial quantum/melange network manager22:54
danwentjames: thanks for the update22:54
jamesurquhartI was hoping to have more, but he's tied up with OSCON, and connectivity apparently stinks.22:54
danwentOn donabe: I've been talking to rick a bit about adding a donabe wiki page to start calling out the goals, how it differs from other projects, etc.22:55
somikcool, I did see the first check-in on donabe, it would be great to see how we integrate all this stuff using some blueprints22:55
jamesurquhartYes. Needs to be done.22:55
danwentother open discussion?22:55
jamesurquhartI can work with Rick to get the initial pages up.22:55
salvMay I suggest we rotate the project order for next meetings?22:56
danwentRick said he was going to talk to the openstack folks while at OSCON about getting us access to the main openstack jenkins22:56
danwentsalv: melange and donabe first?22:56
salvThis way we won't have to discuss Melange and Donabe in injury time.22:56
danwenthaha... that seems reasonable.22:56
danwentits just a few agenda edits away.22:57
danwentany other open discussion?22:57
danwent#action dendrobates provide update on jenkins infrastructure22:57
danwent#endmeeting22:57
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"22:57
openstackMeeting ended Tue Jul 26 22:57:56 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-07-26-22.03.html22:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-07-26-22.03.txt22:58
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-07-26-22.03.log.html22:58
danwentthanks folks22:58
jamesurquhartttyl, all22:58
*** jamesurquhart has left #openstack-meeting22:58
RamDThanks all22:58
*** troytoman is now known as troytoman-away22:58
SumitNaiksatamlater, bye!22:58
*** jk0 has left #openstack-meeting22:58
*** RamD has quit IRC22:58
*** SumitNaiksatam has quit IRC22:58
salvbye bye22:58
*** alekibango has quit IRC22:59
*** medberry is now known as med_out22:59
*** joearnold has quit IRC22:59
*** Tushar has quit IRC22:59
*** joearnold has joined #openstack-meeting23:00
*** nati has joined #openstack-meeting23:01
*** asomya has quit IRC23:01
*** salv has quit IRC23:03
*** nati has quit IRC23:05
*** somik has quit IRC23:08
*** jkoelker has quit IRC23:08
*** midodan_ has joined #openstack-meeting23:09
*** Shubhangi has quit IRC23:12
*** Shubhangi has joined #openstack-meeting23:12
*** midodan has quit IRC23:13
*** midodan_ is now known as midodan23:13
*** midodan_ has joined #openstack-meeting23:15
*** midodan has quit IRC23:15
*** midodan_ is now known as midodan23:15
*** tomeff has quit IRC23:16
*** liemmn has quit IRC23:24
*** joearnold has quit IRC23:24
*** ryu_ishimoto has left #openstack-meeting23:25
*** dragondm has quit IRC23:33
*** dragondm has joined #openstack-meeting23:35
*** Shubhangi has quit IRC23:38
*** markvoelker has quit IRC23:40
*** agarwalla has quit IRC23:46
*** danwent has left #openstack-meeting23:54

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