Tuesday, 2011-11-15

*** cdub has quit IRC00:00
*** zns has joined #openstack-meeting00:03
*** yogirackspace has left #openstack-meeting00:03
*** adjohn has joined #openstack-meeting00:03
*** dendrobates is now known as dendro-afk00:12
*** cdub has joined #openstack-meeting00:16
*** sleepsontheflo-2 has joined #openstack-meeting00:18
*** sleepsontheflo-2 has quit IRC00:22
*** sleepsontheflo-1 has quit IRC00:22
*** zns has quit IRC00:24
*** sleepsontheflo-1 has joined #openstack-meeting00:33
*** reed has quit IRC00:33
*** adjohn has quit IRC00:44
*** jakedahn has quit IRC00:44
*** dolphm_ has quit IRC00:45
*** sleepsontheflo-1 has quit IRC00:45
*** novas0x2a|laptop has joined #openstack-meeting00:55
*** novas0x2a|laptop is now known as Guest3748400:55
*** reed has joined #openstack-meeting00:56
*** sleepsontheflo-1 has joined #openstack-meeting00:57
*** dendro-afk is now known as dendrobates00:59
*** reed has quit IRC01:04
*** reed has joined #openstack-meeting01:05
*** jakedahn has joined #openstack-meeting01:06
*** jakedahn has quit IRC01:08
*** sleepsontheflo-1 has quit IRC01:09
*** dragondm has quit IRC01:11
*** Binbin has joined #openstack-meeting01:11
*** dendrobates is now known as dendro-afk01:17
*** Guest37484 has quit IRC01:30
*** dendro-afk is now known as dendrobates01:36
*** ohnoimdead has quit IRC01:42
*** gyee has quit IRC01:47
*** nati2 has quit IRC02:04
*** nati2 has joined #openstack-meeting02:04
*** reed has quit IRC02:07
*** mdomsch has joined #openstack-meeting02:29
*** cdub has quit IRC02:38
*** dendrobates is now known as dendro-afk02:40
*** mdomsch has quit IRC02:53
*** cdub has joined #openstack-meeting02:58
*** jdurgin has quit IRC03:02
*** dendro-afk is now known as dendrobates03:13
*** adjohn has joined #openstack-meeting03:28
*** cdub has quit IRC03:28
*** reed has joined #openstack-meeting03:42
*** reed has quit IRC03:58
*** cdub has joined #openstack-meeting04:09
*** dendrobates is now known as dendro-afk04:10
*** adjohn has quit IRC04:13
*** nati2_ has joined #openstack-meeting04:27
*** nati2 has quit IRC04:29
*** nati2 has joined #openstack-meeting04:38
*** nati2_ has quit IRC04:38
*** adjohn has joined #openstack-meeting05:12
*** cdub has quit IRC05:24
*** cdub has joined #openstack-meeting05:57
*** nati2_ has joined #openstack-meeting06:54
*** nati2 has quit IRC06:55
*** dolphm has joined #openstack-meeting06:55
*** cdub has quit IRC07:07
*** nati2_ has quit IRC07:12
*** dolphm has quit IRC07:20
*** dolphm has joined #openstack-meeting07:35
*** bengrue has quit IRC07:37
*** dolphm has quit IRC08:06
*** adjohn has quit IRC08:33
*** cdub has joined #openstack-meeting09:06
*** darraghb has joined #openstack-meeting09:33
*** cdub has quit IRC10:22
*** cdub has joined #openstack-meeting10:38
*** dendro-afk is now known as dendrobates12:54
*** deshantm_laptop has joined #openstack-meeting13:06
*** dendrobates is now known as dendro-afk13:14
*** Binbin has quit IRC13:29
*** AlanClark has joined #openstack-meeting13:38
*** royh has left #openstack-meeting14:07
*** joesavak has joined #openstack-meeting14:26
*** deshantm_laptop has quit IRC14:33
*** blakeyeager has quit IRC14:34
*** dendro-afk is now known as dendrobates14:35
*** dolphm has joined #openstack-meeting15:17
*** mwhooker_ has joined #openstack-meeting15:18
zulsorry anyone here for the nova ec2 api meeting?15:23
zulgot my timezones mixed up15:23
*** jwalcik has joined #openstack-meeting15:23
mwhooker_zul: I am. can't tell if it ended already15:26
zulmwhooker_: actually it needs to start15:26
zulanyone else?15:26
zul#startmeeting15:26
openstackMeeting started Tue Nov 15 15:26:52 2011 UTC.  The chair is zul. Information about MeetBot at http://wiki.debian.org/MeetBot.15:26
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.15:26
zulsorry for being late, welcome to the nova ec2 api team meeting15:27
zulThe agenda for this meeting is the following:15:27
zul1. Introduction15:27
zul2. Bug Workflow15:27
zul3. Testing15:27
zulso lets get started15:28
zul#topic15:28
*** openstack changes topic to ""15:28
zul#topic Introduction15:28
*** openstack changes topic to "Introduction"15:28
zulso the purpose of the nova ec2 api team is to take care of the EC2 API on nvoa15:28
zulin diablo, alot of work was done for the Openstack API but the EC2 API was left a bit to lag15:29
*** nati2 has joined #openstack-meeting15:29
zulso the nova ec2 api team is a group of interested developers parties that want to use the EC2 API on nova15:29
zulany questions so far?15:30
*** troytoman-away is now known as troytoman15:30
zulso we have a lp team called the nova-ec2-api team which is free for anyone to join15:31
zulso lets get to the second topic15:31
zul#topic Bug Workflow15:31
*** openstack changes topic to "Bug Workflow"15:31
zulso there is a number of bugs on launchpad that deals with especially with the EC2 API,  this week i am going to start going through the bugs on nova, glance, and swift and start tagging them specifically as ec215:32
zulafter that happens then we can start to follow the regular bug worklfow, getting them reviewed in git and getting them fixed for essex15:32
zulany comments so far?15:33
zulis there any bugs that people want to bring up if not I can go into testing as well15:34
zul...15:34
mwhooker_I may have one15:35
zulok then15:35
mwhooker_one sec15:35
zulsure15:35
mwhooker_https://bugs.launchpad.net/nova/+bug/81368515:35
uvirtbotLaunchpad bug 813685 in nova "EC2 API input validation is poor" [Wishlist,In progress]15:35
mwhooker_there's not much to say other than this died during the switch to git/gerrit15:35
zulright15:36
mwhooker_but wanted to call it out so people know I'll be porting it15:36
zulsweet!15:36
ttxkewl15:36
zulhow far along are you?15:36
mwhooker_and I'd welcome a review from ec2-api team15:36
zulill be happy to do it15:36
zuland im sure other people from canonical would be happy to review it as well15:37
mwhooker_I just need to merge HEAD (and resolve a fair bit of hairiness)15:37
zulill look forward to it15:37
zulwhich leads me to the last topic which is testing15:37
zul#topic testing15:37
*** openstack changes topic to "testing"15:37
zulso there are a couple of testing frameworks that i am aware of that we can use. I think it would be important to have those tests in jenkins so we can run a regular automated test on the EC2 API15:38
zulthis would require help from the openstack-ci team15:39
zulttx: what do you think?15:39
zulI think I would need to talk to mtaylor about getting that started somehow15:39
mtaylorarro?15:40
mtaylorreading15:40
mtayloryes15:40
mtaylorwe should definitely test things15:40
zulok ill poke you after the meeting then15:40
mtaylorshould we incorporate those into openstack-integration-tests?15:41
mtayloror are you talking about third-party ec2 api test things?15:41
zulcloudscaling i believe has a pretty comprenhensive testsuite that takes care of it as well15:41
mtaylorand are you talking unittest-level testing? or are we talking about testing against an installed openstack?15:41
zulthird-party testing...ill poke you about it after the meeting15:41
mwhooker_I'm representing cloud scaling and will plug our tests in a bit15:41
mtaylorok. great.15:41
mtaylorawesome15:41
mwhooker_sorry, autocorrect "Cloudscaling"15:42
zulmwhooker_: awesome15:42
mtaylorthe quick response here is a) awesome on integrating - b) I also plan on getting some jobs going running the test suits from various connectors, like libcloud and jclouds15:42
zulmwhooker_: if you want to plug your tools now would be a good time15:42
mtaylorso - hopefully between all of that things will be happy making15:42
mwhooker_aws-compat, our testing tools is available here: https://github.com/cloudscaling/aws-compat15:43
mtaylorzul: sorry for joining late... are you focusing primarily on in-tree ec2 stuff?15:43
zulmtaylor: yes we are15:44
mwhooker_it's a functional test: it runs through some use-cases and tries to tell you which of the cases aren't working15:44
zulmwhooker_: cool...how does the nova ec2 api looking so far?15:44
*** smoser has joined #openstack-meeting15:44
mwhooker_it has two failing tests15:44
mtaylormwhooker_: lovely. looks like something that could at least physically be merged in with openstack-integration-tests ... whether or not that's the right choice I'll leave as a different conversation15:44
mwhooker_mtaylor: could be.15:45
mwhooker_one test is a known bug, the other I'd like someone to verify before I add it as a bug15:45
zulsounds like a todo item15:45
mwhooker_the other thing I'd like to do is get someone else to run it ;)15:46
zulmwhooker_: its actually on my todo list for this week as well15:46
mwhooker_excellent15:46
mwhooker_I'll be available if you have any troubles15:47
zulcool..15:47
zulso the last thing i want to bring up is this is a good time for everyone, this is the first meeting and we are going to get some more traction in the long run, I do want this to become a weekly meeting as well15:48
zulwhat do others think?15:48
smoserzul, sorry for being late.  i was thinking this was a bit later in the day.15:48
smoserdoes anyone know if ec2 api is now functional out of the box on devstack ?15:48
mtaylorjeblair: ^^15:49
smoserit was not a couple weeks ago when i tested, and having that functional is a major helping hand15:49
mwhooker_weekly meeting sounds great, though I wonder if we could move it back a bit15:49
zulmwhooker_: i was thinking 18 UTC15:50
* mtaylor does not know that ... although we're working on getting devstack hooked in to gating, so a) it should be easy enough to add support once we do and b) I guess we'll need that before we can start running ec2 api tests in jenkins15:50
ttxzul: another meeting at that time15:50
ttx(Keystone)15:50
zulson of a..15:50
mwhooker_sounds good15:50
zulis there a list of when meetings happen?15:50
ttxmaybe another day15:50
dolphmhttp://wiki.openstack.org/Meetings15:50
ttxthere is even a gcal.15:51
zulyeah ill send out an email15:51
zulsmoser: its on my todo list as well :(15:52
smoserok. thank you.15:52
zul#topic Open Floor15:52
*** openstack changes topic to "Open Floor"15:52
zulis there anything else someone wants to bring up15:52
smoseris there *any* documentation on how you set up a functional ec2 api end point given keystone ?15:53
zulnot that i know of15:53
smoserit didn't "just work" and i didn't know where to go from there when i was playing with devstack.15:53
*** cdub has quit IRC15:53
zulsmoser: maybe hunt down the keystone developers15:54
smoseralright. maybe i play with this today.15:54
Davieysmoser: I believe koolhead is looking at doing it at the moment.15:55
zuli think the keysone ppa needs some love as well at least15:55
joesavaklink: http://keystone.openstack.org/configuration.html15:56
joesavaksee "Creating Keystone Credentials"15:56
*** cdub has joined #openstack-meeting15:56
joesavaker.. "Creating EC2 Credentials"15:56
ttxMy other area of concern is the EC2-compatible way of registering images (objectstore/S3 wrapping)15:56
smoserjoesavak, does that also work for the public and private key path ?15:57
ttxIf that's to be kept in nova, it needs some love15:57
zulttx: right15:57
smoserwhich is what is required for registering images15:57
joesavaksmoser: not sure15:57
ttxzul: I wonder how it can even work, with bugs like https://bugs.launchpad.net/nova/+bug/89048615:59
uvirtbotLaunchpad bug 890486 in nova "Cannot create image with kernel_id and ramdisk_id in S3ImageService" [Low,In progress]15:59
*** adjohn has joined #openstack-meeting15:59
*** pringles_ has joined #openstack-meeting15:59
zulttx: we need to start tagging ec2 stuff more16:00
ttxwill do16:00
DavieyIt seems apparet that testing and certification is currently weak.16:00
zuland with that we have run out of time thanks for coming can we continue this conversation on #openstack-dev16:00
zul#endmeeting16:00
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"16:00
openstackMeeting ended Tue Nov 15 16:00:42 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-15-15.26.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-15-15.26.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-15-15.26.log.html16:00
Davieyzul: i thought the meeting should have been starting now?16:00
zulno started an hour ago16:01
zulbut i was late16:01
*** troytoman is now known as troytoman-away16:01
Davieyahh16:02
mwhooker_I'll work on encoding bug #890486 into aws-compat16:02
uvirtbotLaunchpad bug 890486 in nova "Cannot create image with kernel_id and ramdisk_id in S3ImageService" [Low,In progress] https://launchpad.net/bugs/89048616:02
*** dragondm has joined #openstack-meeting16:05
*** dolphm has quit IRC16:06
*** deshantm_laptop has joined #openstack-meeting16:06
ttxmwhooker_: do you think your work will land for essex-2 ?16:07
mwhooker_ttx: which part?16:07
ttxaws-api-validation16:08
mwhooker_ttx: for december? I should hope so. I'll try to get the blueprint added to the milestone16:10
ttxmwhooker_: I'll mention it to Vish today16:12
mwhooker_thanks16:12
*** medberry has quit IRC16:13
*** medberry has joined #openstack-meeting16:13
*** medberry has joined #openstack-meeting16:13
*** mwhooker_ has quit IRC16:31
*** dprince has joined #openstack-meeting16:46
*** nati2 has quit IRC16:46
*** dolphm has joined #openstack-meeting16:46
*** dprince has quit IRC16:50
*** cdub has quit IRC16:53
*** hggdh has quit IRC17:11
*** sleepsontheflo-1 has joined #openstack-meeting17:12
*** gyee has joined #openstack-meeting17:13
*** gyee has quit IRC17:15
*** gyee has joined #openstack-meeting17:15
*** hggdh has joined #openstack-meeting17:15
*** gyee has quit IRC17:16
*** rnirmal has joined #openstack-meeting17:17
*** adjohn has quit IRC17:20
*** adjohn has joined #openstack-meeting17:22
*** jog0 has joined #openstack-meeting17:34
*** jog0 has quit IRC17:35
*** jog0 has joined #openstack-meeting17:36
*** ohnoimdead has joined #openstack-meeting17:46
*** jdurgin has joined #openstack-meeting17:51
*** oubiwann has joined #openstack-meeting17:55
*** adjohn has quit IRC18:01
*** carlp has joined #openstack-meeting18:13
*** novas0x2a|laptop has joined #openstack-meeting18:16
*** novas0x2a|laptop is now known as Guest1489618:16
*** rmk has joined #openstack-meeting18:19
*** dwcramer has joined #openstack-meeting18:23
*** jakedahn has joined #openstack-meeting18:31
*** mdomsch has joined #openstack-meeting18:31
*** darraghb has quit IRC18:35
*** dprince has joined #openstack-meeting18:36
*** jsavak has joined #openstack-meeting18:38
*** joesavak has quit IRC18:41
*** jakedahn_ has joined #openstack-meeting18:44
*** jakedahn has quit IRC18:46
*** jakedahn_ is now known as jakedahn18:46
*** vladimir3p has joined #openstack-meeting18:47
*** donaldngo_hp has quit IRC18:51
*** Guest14896 has quit IRC18:57
jeblairhi19:00
jeblairanyone here for a ci meeting?19:00
mtaylorhey all19:00
mtaylor#startmeeting19:00
openstackMeeting started Tue Nov 15 19:00:48 2011 UTC.  The chair is mtaylor. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.19:00
mtaylorI'm here :)19:00
jsavaki'm here too19:01
mtaylorcheck that out - it's a party19:01
jeblairyay19:01
annegentleyay ci19:01
jsavak#idea beer19:01
mtaylorhehe19:01
mtayloryou know what - I think I want to start with ...19:02
mtaylor#topic rearranging servers a little bit19:02
*** openstack changes topic to "rearranging servers a little bit"19:02
mtaylorwe're really close to rolling some code into production that creates and deletes cloud servers accounts as needed19:02
mtaylorso it seems like a terrible idea to have things arranged such that a bug in a script could just delete the jenkins server19:03
jeblairor the gerrit server19:03
jsavakha!19:03
mtaylorto that end, we've set up a couple of additional cloud servers accounts - one to hold ephemeral script-created servers19:03
mtaylorand one to hold dev resources - jenkins, gerrit, the servers that hold the dev docs and I think the ones that hold the irc bots19:04
mtaylorthe other ones web resources that are in the current openstacak account I think should stay there - because they're not really things that fall under openstack-ci team management19:05
mtayloranybody have any general dissent to that plan or concerns about it?19:05
mtaylorawesome19:05
*** novas0x2a|laptop has joined #openstack-meeting19:06
mtaylor#agreed we'll move the servers around into a set of web-resources, a set of dev-driving machines, and a set of ephemeral machines19:06
*** novas0x2a|laptop is now known as Guest752919:06
mtaylor#topic state of integration testing19:06
*** openstack changes topic to "state of integration testing"19:06
mtaylorjeblair: you wanna update us on where integration testing is?19:06
jeblairsure19:07
jeblairi'm quite close to having on-demand devstack configured vm testing of changes we can use for gating19:08
jeblairbasically that means:19:08
jeblairwe'll have a job that launches a vm, has devstack configure it, and run tests on it, then destroy it19:08
jeblairfor now, the tests we're going to run are just the "exercises.sh" tests in devstack19:09
jeblairbut that's really a placeholder for the openstack-integration-test suite19:09
jeblaironce that's ready for gating, we'll switch to that19:09
jeblairfor the moment, i'm only focusing on the stable/diablo branch19:09
jeblairsince i don't believe devstack can configure trunk at the moment19:09
mtaylorfantastic19:10
jeblairi'm working with jesse on moving devstack into gerrit, and i believe he'll be ready to focus on trunk soon19:10
jsavakare there plans to run off of essex1?19:10
*** donaldngo_hp has joined #openstack-meeting19:10
jeblairthe test job will be just like the others, eventually it will run on every branch19:11
jsavakcool. :)19:11
jeblairso that'll be master, and milestone proposed19:11
jeblairbut not specifically essex1, which is now just a tag since it was released19:11
jeblair(future development should happen on master)19:12
jeblairthe scripts are all here: https://github.com/openstack/openstack-ci/tree/master/slave_scripts19:12
jeblairdevstack-*19:12
jeblairand the jenkins job is here: https://jenkins.openstack.org/view/All/job/dev-gate-integration-tests-devstack-vm/19:12
jeblair#link https://github.com/openstack/openstack-ci/tree/master/slave_scripts19:13
jeblair#link https://jenkins.openstack.org/view/All/job/dev-gate-integration-tests-devstack-vm/19:13
dolphmwhat's the timeline for gating with openstack-integration-tests?19:13
jeblairit's obviously not done yet19:13
jeblairas in, i'm literally in the middle of configuring it19:13
jeblairbut it is demonstrating a couple of new things we're doing with jenkins:19:13
jeblairit's triggered on multiple projects; so a change to any of nova, glance, keystone will all trigger the job19:14
jeblairand it's running in 'silent mode'19:14
jeblairwhich means that it does not report its output back to gerrit, and does not vote on changes19:14
jeblairthat's an important feature for us to get complicated jobs like this up and running without interfering with ongoing development19:15
mtaylorthe multiple-job trigger is pretty bad-ass19:15
jeblairdolphm: i'm not sure anyone has dates, but:19:15
jeblairi think this setup should be ready to go this week.  we want to get python-novaclient and devstack into gerrit before we get too serious, hopefully this week or next.  after that, as soon as openstack-integration-tests say they're ready19:16
jeblairwe want all the important components, devstack included, gated on this job so that we know if someone changes devstack, it still works for testing19:17
*** mrmartin has joined #openstack-meeting19:17
jeblairmtaylor: yes, since we can trigger on multiple jobs, that means this one jenkins job can be used to gate all the projects19:17
jeblair(all the projects we're interested in gating, that is)19:17
mtaylorjeblair: that's so much nicer than having a bazillion different jobs19:18
jeblairand it means we can ensure changes to them are serialized across all projects19:18
jeblair(is that clear, or should i elaborate on that?)19:18
mtaylormakes sense to me19:18
dolphmvery clear19:19
dolphm(and awesome)19:19
jeblaircool.  so that's the current status.  sorry i don't have green lights in jenkins to show yet.  but at this point all the individual components have been tested.  just assembling them now.19:19
jeblairoh, one more thing19:19
jeblairwe're going to try an idea ttx had at uds:19:20
jeblairif a change fails the devstack driven integration tests,19:20
jeblairwe install the developer's key on the vm and hand it to them.19:20
dolphmso the vm isn't deleted?19:21
jeblairthey have, say, 24 hours to work on the very VM where the test failed and see what went wrong and try to fix it.19:21
dolphmbut is deleted on success?19:21
jeblairdolphm: that's the idea19:21
dolphmthat's pretty damned cool19:21
jeblair(up to a point)19:21
jeblairyeah, i think it'll be pretty neat. :)19:21
*** yogirackspace_ has joined #openstack-meeting19:22
jeblairany other questions about this?19:22
dolphmif the dev is asleep for those 24 hours, how do they re-run the job to get a failed vm back up?19:22
jeblairyou can re-trigger a job in jenkins, or by +2'ing it again in gerrit19:23
dolphmno everybody can +2.. can everybody retrigger?19:23
dolphmnot*19:24
jeblairdolphm: I'm not positive about that.19:24
mtaylorI do not believe everyone can retrigger19:25
mtaylorBUT19:25
mtaylorI betcha we can figure something out there19:25
dolphmi'm just thinking, as this becomes a popular/necessary workflow, if 24 hrs isn't sufficient, I'd like devs to be able to get a failed vm on their own, with minimal effort19:25
vishyjeblair: have a branch that works with trunk fyi19:25
jeblairvishy: awesome19:25
* mtaylor makes out with vishy19:26
jsavak...19:26
* dolphm hides19:26
vishyhad to disable one test because python-novaclient is out of date19:26
mtaylordo we have a date for moving python-novaclient over yet?19:27
vishywe should have devstack tagged diablo/stable and have a master running trunk in the next couple days19:27
jeblairno, i proposed tomorrow morning to sandy, but haven't heard back19:27
*** dolphm has quit IRC19:27
mtaylorI'm going to try to get the git-based pip-requires up and going for all the projects this week too, and finish moving the other projects to using pip-based unittest builders19:27
mtaylorso we should be consistent across the board real soon now19:28
jeblairvishy: i emailed jesse about moving devstack to gerrit; we need to do that soon too, before we can start using it to gate19:28
jeblairmtaylor: yay!19:29
*** Adri2000 has quit IRC19:30
*** Adri2000 has joined #openstack-meeting19:30
*** yogirackspace_ has quit IRC19:31
*** sleepsontheflo-1 has quit IRC19:31
mtaylorso I think that's where we're at with just about everything19:32
mtaylor#topic anything else19:33
*** openstack changes topic to "anything else"19:33
*** dolphm has joined #openstack-meeting19:33
*** dolphm has quit IRC19:33
notmynameI have a gerrit question19:34
notmyname(not sure if this is the right forum)19:34
mtaylorgo for it!19:34
*** dolphm has joined #openstack-meeting19:34
notmynamewhen is -1 vs -2 appropriate?19:34
jeblair-2 functionally blocks it from being merged19:35
notmynameforever?19:35
mtayloruntil the -2 is lifted/changed19:35
notmynameby another review from that same person?19:35
mtaylorin fact - -2 sticks around even after a new change is pushed19:35
mtayloryes19:35
notmynameok19:35
mtaylorso -2 is throwing your weight down and saying NO19:35
notmynamebut, "this is mostly ok but fix A,B,and C" should probably be -1, then?19:36
mtaylorprobably19:36
jeblairi think so, and your -1 will be automatically removed when there is a new patchset.19:36
notmynameand -2 is "no, I don't think adding the ability to make toast is a good feature to ever add to nova"19:37
jeblairnotmyname: you might consider using it also as a way to ensure that you review a subsequent change19:37
notmynameok. makes sense. thanks19:38
jeblairas in: "I want you to fix this, and make sure that it's fixed to my satisfaction before it goes in"19:38
mtaylorwe could consider suggesting a policy around -2 similar to +2 ...19:38
mtaylorlike, people vote in general, and a core member +2's or -2's based on the general consensus of the voting?19:38
mtaylorbut yeah - we can also just try playing with it for a while and seeing how we like it19:39
jeblairmtaylor: i want core people to all be able to +2 eventually19:39
jeblairie, we should support multiple +2 votes19:39
jeblaironce we have the gerrit trigger plugin updated19:39
mtaylorjeblair: yes.19:39
jeblairso i don't want to build too much policy around what is currently a technical limitation :/19:39
mtaylor++19:40
jeblairor if we do, understand where we're going in the future19:40
vishyI also have a gerrit question / feature request19:40
jeblairvishy: go for it19:41
vishyi find it quite annoying that repushing covers up previous reviews, especially when the push is just a rebase19:41
mtayloryes. I do too19:42
vishyi don't have a solution, but it would be nice to be able to say, just a rebase when merging19:42
jeblairright, the trivial rebase problem...19:42
mtaylorwe have a todo list item on that19:42
vishyand it keeps the previous +1s19:42
jeblairhttps://bugs.launchpad.net/openstack-ci/+bug/88118419:42
uvirtbotLaunchpad bug 881184 in openstack-ci "consider trivial rebase hook for gerrit" [Wishlist,Confirmed]19:42
mtaylor#action mtaylor translate all of the gerrit/jenkins todo list items into bugs/blueprints19:42
jeblairwow, mtaylor, that was quick! :)19:43
notmyname(all the "trivial" rebasing also makes the master branch look ugly)19:43
jeblairso what that hook does is:19:43
jeblair"This hook is designed to detect when a patchset uploaded to Gerrit has the same git patch-id as the previous patchset. It then reapplies reviews onto the new patchset using the Gerrit SuExec and Approve commands."19:43
mtaylorthere's also been talk about a UI patch to make some of the review data show more prominiently by default, rather than needing to expand a section19:43
vishynotmyname: I disagree with your comment about toast19:44
* vishy has been waiting for the toast patch for a while now19:44
jeblairwhich i believe would solve vishy's problem.19:44
jeblairobviously it should be easy to install, we just need to make sure it does what it advertises19:44
jeblairand works with our workflow19:44
notmynamevishy: well that's where the -1 or -2 levels come in ;-)19:45
*** jakedahn has quit IRC19:46
ttxHmmm. Toast...19:46
*** adjohn has joined #openstack-meeting19:47
*** joshuamckenty_ has joined #openstack-meeting19:47
* mtaylor is hungry now19:47
notmynamemtaylor: turns out that brazillian food in brazil is exactly the same as brazillian food in the US. I suggest you go get some churisca (sp? whatever.) tonight19:48
mtaylornotmyname: yes. it's quite tasty isn't it?19:48
jeblairmeeting over? :)19:48
mtaylorI think so19:49
mtaylor#endmeeting19:49
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"19:49
openstackMeeting ended Tue Nov 15 19:49:14 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-15-19.00.html19:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-15-19.00.txt19:49
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-15-19.00.log.html19:49
*** sleepsontheflo-1 has joined #openstack-meeting19:49
notmynamemtaylor: but I don't recommend the chicken hearts19:49
mtaylornotmyname: good advice19:50
notmynamemtaylor: they're like liver wrapped in a tough, chewy shell. so if you like that sort of thing...19:50
mtaylornotmyname: well, I do like liver - but wrapping it in a tough, chewy shell does not sound pleasant19:51
notmynameyou should probably at least try one. but I make no promises about it :-)19:53
mtaylornotmyname: tomorrow is feijoada day (traditionally served on wed and sat) ... you should try to find somewhere that's serving it for lunch19:55
mtaylornotmyname: it's not fancy, but it is tasty19:55
*** joshuamckenty_ has quit IRC19:57
*** ewanmellor has joined #openstack-meeting19:57
*** zns has joined #openstack-meeting19:59
ttxo/19:59
*** dendrobates is now known as dendro-afk20:00
*** anotherjesse has joined #openstack-meeting20:00
znsttx: which meeting is this? Just checking my timezones.20:00
ttxPPB20:01
znsCool. zns here.20:01
vishyo/20:01
* anotherjesse is here .. and sad he missed ci meeting ;(20:01
ttxMissing our chair20:01
notmynamehi20:01
* ewanmellor Ready for PPB goodness20:02
ttxanotherjesse: will you be around for the next meeting ? We'll discuss if keystone stable/diablo branch is in a usable state20:02
anotherjessettx: sure thing20:02
ttx(enough to warrant a tag and a tarball cut)20:02
ttxcool.20:02
*** jakedahn has joined #openstack-meeting20:03
jaypipeso/20:03
mtayloro/20:03
mtayloranotherjesse: we missed you too!20:03
mtayloranotherjesse: but we chatted with vishy20:03
anotherjessewill go read the meeting notes20:04
mtayloranotherjesse: the level of bad-assery that we're about to collectively unleash here is pretty massive20:04
*** dwalleck has joined #openstack-meeting20:04
anotherjessenice20:04
ttxmtaylor: we are missing jbryce, but I guess you can talk about the state of gating and integration testing...20:04
anotherjesseexcited20:04
ttxor we can wait.20:04
ewanmelloranotherjesse is too busy now that he's "sort of a defacto CTO"20:05
mtayloranotherjesse: is that your new title?20:05
jaypipesreally?20:05
ttxewanmellor: is that a quote ?20:05
ewanmellorhttp://www.networkworld.com/community/blog/openstack-cloud-builders-and-future-cloud?source=nww_rss20:05
anotherjesseewanmellor: i'm working moving day to day to sleepsontheflo-1 so that I can actually talk/meet with others ;)20:05
* ttx reads to pass the time20:05
anotherjessehaha - nice title20:06
ttxheh20:06
mtayloranotherjesse: you should TOTALLY put that on business cards20:06
notmynameit's on the internet. it must be true20:06
mtaylorI love the "sort of" in front of it20:06
anotherjessemtaylor: so - we are working on jenkins + devstack + openstack-integration-tests right?20:07
anotherjesse(looking for the notes from the meeting still)20:07
mtayloranotherjesse: yup. you have a nice long email from jeblair about it in your inbox somewhere20:07
mtaylorbut also:20:07
mtaylorhttp://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-15-19.00.log.html20:07
mtaylorfor anyone who is bored20:07
jaypipesmtaylor: when can we chat about a jenkins + chef/puppet + openstack-integration-tests setup?20:08
*** joshuamckenty_ has joined #openstack-meeting20:08
mtaylorjaypipes: when we've got the first thing working20:08
mtaylor:)20:08
ttxLooks like the man that used to live with clocks set to UTC at home got confused.20:08
ttxShould we just cancel the meeting ?20:09
mtaylorjaypipes: I believe that adding additional deployment methods will be much easier once we've got this first guy done20:09
notmynamesurely someone has his phone number20:09
ttxnotmyname: surely, but not me.20:09
joshuamckenty_Sorry, who are we missing? Jbryce?20:09
notmynameya20:09
ttxyep20:09
joshuamckenty_I've got his number20:09
joshuamckenty_I'll txt him20:10
ttx"sort of de facto PPB chair"20:10
mtaylorhahaha20:10
anotherjessehahaha20:10
anotherjessemtaylor / jeblair  have you played with build_xs stuff?20:10
mtaylorwhat is build_xs?20:10
anotherjesserunning integration tests against "devstack-styled" xen server20:10
anotherjessebasically follow along with https://github.com/cloudbuilders/devstack/blob/master/tools/xen/README.md20:10
anotherjesseand you can get jenkins running against xs20:10
*** ArseneRei has joined #openstack-meeting20:11
mtaylorwell - we'd also need a xen server :)20:11
anotherjesseyou just need hardware and then XS free licenses20:11
joshuamckenty_Bryce has hard drive problems.20:11
anotherjessethe link to the download is on the readme and you can get a license20:11
joshuamckenty_Ttx, do you want to chair?20:11
mtayloranotherjesse: I think that sounds like something we shold put on the list for the 'vendor supplied test environments'20:12
ttxjoshuamckenty_: not really, I have a meeting to chair just after that one.20:12
jaypipesmtaylor: when do we get devstack into gerrit?20:12
ttxjoshuamckenty_: go for it :)20:12
anotherjessejaypipes: I got an email from jeblair about steps to do that20:12
mtaylorjaypipes: short version: looks like possibly this week if all goes well20:13
jaypipesexcellent20:13
jaypipesthx :)20:13
mtaylorjaypipes: we're actually further along than we thought even this morning ... as vish apparently has a branch working wiht trunk20:13
jaypipesmtaylor: a branch of devstack working with trunk?20:14
jaypipesmtaylor: wasn't it always working with trunk?20:14
mtaylorjaypipes: yes20:14
mtaylorjaypipes: no. it's been focused on diablo so far20:14
*** jbryce has joined #openstack-meeting20:14
mtaylorjaypipes: moving forward, we'll have a stable/diablo and a master branch of devstack20:14
* jaypipes must have missed that...20:15
mtaylorjaypipes: so that as master makes changes that require deployment changes, we can handle them without losing ability to test diablo20:15
jbrycehi everyone. sorry i'm late.20:15
jaypipesI thought it was tracking trunk20:15
ttxjbryce: welcome :)20:15
mtaylorhey jbryce!20:15
jaypipesmtaylor: check PM.20:16
jbrycewho all is present? did we get started with anything already?20:16
ttxnope, were waiting for you20:17
jbryce#startmeeting20:17
openstackMeeting started Tue Nov 15 20:17:14 2011 UTC.  The chair is jbryce. Information about MeetBot at http://wiki.debian.org/MeetBot.20:17
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.20:17
mtayloranotherjesse: but once we get this first one up - I really want to start spending more time on the plan of getting better/fuller hardware/environment coverage from vendors, which we've got good ideas on doing20:17
anotherjessenice20:17
jbrycemy hard drive started rattling like a pair of castanets. i think that's a bad sign. yay for backups, though20:17
anotherjessejbryce: backup to the cloud20:17
mtaylorjbryce: unless you like castanets20:17
jbrycemtaylor: true...20:18
jbrycehttp://wiki.openstack.org/Governance/PPB - agenda20:18
jbryce#topic Foundation update20:18
*** openstack changes topic to "Foundation update"20:18
jbrycethierry asked about an update on foundation progress since things have been quiet on the mailing list20:18
jbrycesince we made the announcement, we've seen a lot of interest from a lot of different people. we've been meeting with different companies and foundations and getting feedback and trying to get as many of them as possible to join up on the mailing list also20:19
jbryceone consistent piece of feedback that we've gotten is that we should come forward with a drafting process and timeline for putting it all together, so that's something we've been working on with several lawyers from rackspace and elsewhere20:20
ttxjbryce: should we encourage the presentation of existing models on the ML ?20:20
ttx(copying an existing model is a good way to reduce the base work)20:21
ttxjbryce: or are your private discussions already past that ?20:21
jbrycemark or i will be sending out a more detailed email to the foundation list but the basic process is to publish a draft of the high level goals and philosophies and get feedback on that over the rest of November, then move into an actual legal document drafting process. that will probably consist of 2 drafting periods where we publish a draft and accept comments over the course of several weeks and the re-draft20:22
*** andrewbogott has joined #openstack-meeting20:22
jbrycettx: discussing existing models is definitely something we can do on the list20:23
ttxjbryce: do you want the "goals and philosophies" defined first, before the actual governance and foundation model ? Or in parallel ?20:23
jbrycei think it makes sense to get the high level done first as it will affect the details of the legal structure20:23
ttx(because the existing models are obviously more about governance structure than about goals/scope/philosophy)20:23
jbrycetrue20:24
ttxso imho that's two separate discussions, dunno if you want to have them in parallel or define the goals first20:24
jbrycei think i'd prefer goals first20:25
ttxjbryce: ok, would be good to send out some progress note saying the first step is to discuss/define goals/philosophy/scope20:25
jbrycein summary, there's been a small amount of progress in actual documentation, but quite a bit of input and feedback that has been offered from a variety of source that we're trying to aggregate and publish20:25
ttx(so that the discussion can focus on that first)20:26
jbrycegood feedback20:26
jbryceanything else? question or suggestions?20:27
jbryceok. moving on20:28
jbryce#topic Quality for Essex20:28
*** openstack changes topic to "Quality for Essex"20:28
mtaylorso...20:28
mtaylorfirst of all: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-15-19.00.log.html20:28
ttx+120:28
*** dolphm has quit IRC20:28
*** jakedahn has quit IRC20:29
mtaylorwe had a great summary of where we were on this during the CI meeting in the last hour20:29
mtayloras a much briefer summary - current status is that jeblair has the infrastructure/integration pieces working to launch fresh cloud servers, run devstack on them and then run exercise.sh against those20:29
*** joshuamckenty_ has quit IRC20:30
mtaylorcurrently immediately outstanding todo items to get those tests up and going are getting devstack working against trunk (which vishy apparently already has done) and getting devstack and python-novaclient moved over to gerrit20:30
anotherjessemtaylor: also devstack has a config.ini generator20:31
mtaylor(we actually don't need trunk working before we start - those are just the immediate tasks)20:31
anotherjesseso you can run the openstack-integration-tests against them20:31
anotherjesse(we do that on our jenkins)20:31
mtaylorgreat20:31
anotherjessemtaylor: was there talk about how to run larger scale tests (launch vms non-stop for a week, ...)20:31
mtaylorthat's the next step after the above, is once we're satisfied that exercise.sh can run consistently, we'll start adding openstack-integration-tests20:32
*** dolphm has joined #openstack-meeting20:32
jaypipeswhy are we using 2 jenkins again?20:32
mtayloranotherjesse: at the moment I think running tests of that nature are going to need folks to pony up labs in which to run them in20:32
anotherjessejaypipes: we push everything we do back to mtaylor / jeblair20:33
jbrycehow much of the core functionality do you think will be covered by the time we start getting to the end of essex?20:33
mtaylorjaypipes: anotherjesse has been helping prototype devstack jenkins stuff20:33
anotherjessejaypipes: should we stop?20:33
anotherjessewe don't want to break the core jenkins server20:33
jaypipesjust dont understand why there is a need for 2 jenkins...20:33
anotherjessejaypipes: everyone else runs their own jenkins - is it bad for us to as well?20:33
mtaylorjaypipes: too many cooks in the kitchen - basically that way anotherjesse can do things and show them to us20:33
jbryce#info will need better lab environments to do larger scale and longer-running tests20:33
*** jakedahn has joined #openstack-meeting20:34
jaypipesanotherjesse: the direction should be the central jenkins out to secondary jenkins, not the other way around.20:34
anotherjessemtaylor: getting the integration tests running and alerting of basic failures is great, but then there is things like the rax cloud hit in early essex - after many vm launches it various api commands got really slow20:34
mtaylorjaypipes: dude. totally different thing20:34
*** yogirackspace has joined #openstack-meeting20:34
jaypipesmtaylor: no, it's not.20:34
mtaylorjaypipes: it is20:34
mtayloranotherjesse's jenkins is a dev jenkins20:34
jaypipesmtaylor: and what is the point of that?20:34
mtaylorit's a sandbox where he can play with different jobs and not worry about breaking the core element of the entire dev process20:34
mtaylordoing tons of dev directly on the core jenkins is, well - if things break, then things BREAK, right?20:35
jbryceit's staging vs production...don't break the live one that gates the development process for everyone20:35
anotherjessejaypipes / mtaylor we can move this talk about ways we can help the ci process externally20:35
anotherjessesince we had asked mtaylor / jeblair at the last summit and we thought it was a good idea20:36
anotherjessemove this talk to another time - outside pbb20:36
jaypipessure20:36
mtayloryeah. perhaps next week CI?20:36
anotherjessemtaylor: ya - setting alarm now - didn't update time20:36
jbryceso the process sounds great, but can i re-ask my question? = )20:36
jbrycehow much of the core functionality do you think will be covered by the time we start getting to the end of essex?20:36
mtaylorjbryce: that's actually a question that's out of my scope20:36
anotherjessejbryce: I worry about testing large scale VMs launches20:36
anotherjessebut - there is lots of parties (hp, rax and others) talking about it20:37
mtaylorjbryce: my main bit is making sure stuff gets run consistently - the integration tests guys will need to get good coverage in their work20:37
anotherjessewe have a great plan for the general stuff20:37
mtaylorand then the thing anotherjesse is mentioning20:37
mtaylorbecause honestly the jenkins control-center model isn't going to be terribly useful for week-long tets20:37
mtaylortests20:37
jbrycemtaylor: that's fine. not saying it's your scope, but i'd love to know that someone is thinking about it.20:37
mtaylortotally20:37
ttxdo we know how the integration-tests development is going so far ?20:38
mtaylorI think it's going to wind up being a discussion between folks like rax, dell and hp - folks who have the resources to spin up a lab somewhere that can run such a test20:38
anotherjessettx: bcwaldon had gotten the basics working20:38
jaypipesmtaylor: to be blunt, it's pointless trying to design large scale performance testing of Nova until a deployment Jenkins job that uses real deployment things like chef/puppet is completed.20:38
jbryceand also find out if we should go really prod some people to work on this as a form of the strategic contributions that ttx has talked about20:38
*** jk0 has joined #openstack-meeting20:38
mtaylorand then we have to figure out how to collaborate on that between us20:38
ttxjbryce: the teams are up and are open20:38
mtaylorand how to report back findings in a sensible manner20:38
ttxanyone can join and help20:39
*** dendro-afk is now known as dendrobates20:39
mtaylorjaypipes: again, I disagree - I think we can design the process modularly20:39
anotherjessemtaylor: agreed20:39
mtaylorjaypipes: the long-term test is just something that needs to run against a cloud20:39
anotherjessemtaylor: the process of deploy is independant of the tests20:39
mtaylorhow that cloud got there is a different engineering problem to solve20:39
jaypipesmtaylor: ok, I'll reserve (any more) judgment until I see that then20:39
anotherjesseyes20:39
mtaylorand in this case20:40
mtayloreven though we're actually doing a good job along the lines of automated deployment of cloud onto bare metal from jenkins- that work specifically isn't going to be as directly applicable to a week-long test20:40
jbrycei know that the teams are open and anyone can help, but if it's not happening and we get to the end of essex and these tests are not helping us have a much better release, i think that's a big failure on our part.20:41
mtaylorbecause I don't want a week-long test taking up threads in my crazy java app called jenkins :)20:41
jaypipesjbryce: couldn't agree more.20:41
ttxjbryce: that's why I was asking on progress on the integration-tests side -- see if more resources are needed there and a call for help is warranted20:41
mtaylorjbryce: I would say that if we don't have integration tests running by essex-2 we should all book time in a hotel somewhere, get together and have a celebrity death match20:41
mtaylorintegration-tests is a little chicken-and-egg at the moment20:41
jaypipesmtaylor: the point is that you won't be taking up threads on *your* jenkins. The tests will be running on large HP (or other) clusters. But those clusters absolutely are a no-go until deployment jobs that use real ddeployment methods are done.20:42
mtayloras soon as we get this next jenkins job deployed, then we'll have somewhere we can point their work at so that they can get consistent feedback on their tests running20:42
anotherjessemtaylor: really? we've been running them in jenkins for a couple weeks  - will ping you after20:42
ttxmtaylor: the devil is in the number of those tests, not their simple existence.20:42
mtayloranotherjesse: I meant dev-process-wise20:42
anotherjessemtaylor: ?20:42
anotherjesseoh - in gating them20:42
anotherjesseyes - understood now20:42
mtayloranotherjesse: yes20:43
jaypipesttx: for integration tests, dwalleck, westmaas, wwkeyboard, bcwaldon, nati, and a number of others have been contributing to them.20:43
ttxjaypipes: is more help needed ?20:43
ttxjaypipes: or are you confident we can have decent coverage before the last milestones of Essex ?20:43
jaypipesttx: of course. that's what we discuss in our wednesday meetings...20:43
anotherjessemtaylor: is there a philosophy about broken tests in the integration suite?20:44
mtayloranotherjesse: yes20:44
anotherjessemtaylor: eg, when we write a test, can it merge if it is "broken"20:44
jaypipesttx: I'm confident we'll have decent coverage of some stuff... depends on how much APIs and implementations change between now and then.20:44
westmaasttx: decent coverage by last milestone of essex is well within reach20:44
anotherjessebut the test isn't what is broken, it could be underneath20:44
mtayloranotherjesse: the thing we discussed at the ods was having a blessed suite of gating tests20:44
westmaasbut more help is useful20:44
anotherjessemtaylor: cools20:44
ttxjaypipes: ok20:44
mtayloranotherjesse: so that withing the test suite, there will be the full thing, and the meta-suite that's what we believe is solid enough to block trunk on20:44
anotherjessemtaylor: cool20:45
mtayloranotherjesse: and hopefully a simple process for promoting test cases20:45
mtayloroh, btw...20:45
ttxjbryce: so yes, I guess I could call for more practical "put your foot where your mouth is and join the QA team"20:45
mtaylorso, one of the pieces that has come out of jeblair's work this past week on this are jobs in jenkins that are triggered by multiple gerrit projects20:45
* jaypipes noticed commits to kong recently, well after kong was integrated into the main test suite...20:46
ttxjbryce: but convincing all the companies around the PPB table sounds more efficient than a blogpost on my personal website :)20:46
mtaylorso - in this case, we can have one that gates nova, keystone, glance, devstack and openstack-integration-tests ... so that a change to any of them is tested against trunk of the others20:46
mtaylorin a very elegant manner20:46
jbrycettx: i agree. part of why i wanted to raise it here20:47
jbrycettx: if you blog though, i bet you'll get some decent retweeting of that post. = )20:47
znsWon't we need to be able to submit cross-project patches for that to really work?20:47
jaypipesalso, there's commits to cloudbuilders/openstack-puppet dated Oct 30, while the main openstack/openstack-puppet hasn't changed since 20th Oct.20:47
ttxjbryce: let's try that, should improve my klout score.20:47
*** sleepsontheflo-1 has quit IRC20:48
*** anotherjesse has quit IRC20:48
jbryceok20:48
*** dolphm has quit IRC20:48
jbrycelet me try to summarize and see if i've got it all straight20:48
mtaylorzns: shouldn't need to. if you add apis to one thing, then consume them in the next patch... ensures that people are writing to specs cross-project20:48
vishyjaypipes: i don't think the deploy team has confidence in openstack-ci yet20:48
jaypipesvishy: awesome20:48
mtaylorzns: BUT - we will definitely keep our eyes on that20:48
*** sleepsontheflo-1 has joined #openstack-meeting20:49
znsmtaylor: ok20:49
jbryce1) we have continuous integration testing infrastructure in place now that is able to do basic testing and gate contributions on things really functionining20:49
*** KyleM1 has joined #openstack-meeting20:49
*** KyleM1 has left #openstack-meeting20:49
*** anotherjesse has joined #openstack-meeting20:50
mtaylorjbryce: (1) yes - give or take a couple of days, we've got a little cross-team coordination to do20:50
jbryce2) we are going to start including the intergration-tests in to that gating which will improve the coverage and give better testing20:50
*** KyleM1 has joined #openstack-meeting20:50
*** Vek has joined #openstack-meeting20:50
jbryce3) we could use additional contributions to the integration-tests and should reach out and try to get more involvement from people. getting more tests here will be a big help in improving the quality before release time comes around20:51
jbryce4) there's some basic work going on to do not just functional tests (item A works) but also longer running and larger scale tests, but it doesn't sound like that effort is as defined or as far along yet20:51
jaypipesjbryce: good summary20:51
ttx+120:52
*** jog0 has quit IRC20:52
*** mikeyp has joined #openstack-meeting20:52
*** masumotok has joined #openstack-meeting20:53
*** GheAway has joined #openstack-meeting20:53
jbryceok. i'm going to go lobby for this on my own with the companies and people i talk to. i think we should all do it. i'm really keen to make essex the one that we can be super proud of20:53
jbryce#info 1) we have continuous integration testing infrastructure in place now that is able to do basic testing and gate contributions on things really functionining20:53
jbryce#info 2) we are going to start including the intergration-tests in to that gating which will improve the coverage and give better testing20:53
jbryce#info 3) we could use additional contributions to the integration-tests and should reach out and try to get more involvement from people. getting more tests here will be a big help in improving the quality before release time comes around20:53
jbryce#info 4) there's some basic work going on to do not just functional tests (item A works) but also longer running and larger scale tests, but it doesn't sound like that effort is as defined or as far along yet20:53
jbrycegrr...should have done that the first time around, but better late than never20:54
mtaylorhehe20:54
jbrycei think we should discuss this again when we get towards essex-2 and see how things are progressing20:54
jaypipes++20:54
jbrycei really worry about not having a drastic improvement and how it will impact the community and credibility of openstack. i'd even be open to considering treating some level of functional quality testing like an essential blueprint that could delay the release.20:56
ttxjbryce: one issue is that it's never really finished20:57
jbrycettx: i know. i agree on that for sure. i like to ship, but there's a different between never really finished and really not working20:57
ttxand there are organizational things around development that can't support long delays. Like design summits.20:57
ttxso we should get our act together and just make it shine in the timeframe we have20:58
jbrycei agree on that too. that's why i want to raise it now. if we get ahead of it, there shouldn't need to be a delay.20:58
*** johnpur has joined #openstack-meeting20:58
*** robertn has joined #openstack-meeting20:58
ttxit won't be perfect, but it needs to be better !20:58
*** dabo has joined #openstack-meeting20:58
jbrycethanks for all the info. i'm going to go on a campaign. = )20:59
*** dprince has quit IRC20:59
jbryceanyone have anything for our final 40 seconds?20:59
*** Tushar has joined #openstack-meeting20:59
jbrycethanks everyone20:59
ttxnope20:59
jbryce#endmeeting20:59
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"20:59
openstackMeeting ended Tue Nov 15 20:59:58 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-15-20.17.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-15-20.17.txt21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-15-20.17.log.html21:00
ttxzns, notmyname, jaypipes, vishy, devcamcar: around ?21:00
notmynamehere21:00
*** somik has joined #openstack-meeting21:00
jaypipesttx:  not here.21:00
vishyaqui21:00
*** thingee has joined #openstack-meeting21:00
*** joesavak has joined #openstack-meeting21:01
* ttx waits a bit for zns and devcamcar 21:01
*** ArseneRei has left #openstack-meeting21:01
znszns here21:02
ttxok, let's start, devcamcar goes last anyway21:02
ttx#startmeeting21:03
openstackMeeting started Tue Nov 15 21:03:05 2011 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.21:03
ttxWelcome to our weekly general meeting... Today's agenda:21:03
ttx#link http://wiki.openstack.org/Meetings/TeamMeeting21:03
ttx#info The main focus for today is looking at essex-2 plans and make sure they are current21:03
ttx#info Next week we'll extend that focus to the rest of the Essex plans, as the demand for clear roadmap is getting stronger21:03
ttx#topic Keystone status21:03
*** openstack changes topic to "Keystone status"21:03
ttxzns: Looking at:21:03
ttx#link https://launchpad.net/keystone/+milestone/essex-221:04
ttxzns: Do you agree with those 6 targets ?21:04
ttxIncluding global-templates, keystone-swift-acls and service-endpoint-location ?21:04
*** dolphm has joined #openstack-meeting21:05
*** jsavak has quit IRC21:05
znsYes.21:05
ttxOK, I'll set the series goal for those last three to "Essex" then21:05
ttxzns: Anything else on your essex-2 radar that is missing from the list ?21:05
znsWe still have an outstanding *concern* about stability/documentation. Dolph is in California now trying to help nail that down. It's nebulous right now.21:06
*** jbryce has quit IRC21:06
ttxzns: Who is supposed to work on endpoint-identifiers ? The spec has no assignee.21:06
*** Terminus|Work has joined #openstack-meeting21:07
znsDolph or Yogi.21:07
znsMaybe put Yogi there for now?21:07
*** danwent has joined #openstack-meeting21:07
ttxzns: yes, or some team like "Rackspace Integration"21:07
ttxit's ok to change assignees later.21:08
znsworks. Rackspace Integration. You got it?21:08
*** anotherjesse has quit IRC21:08
ttxyep21:08
ttxAlso does anyone know the current state of service-endpoint-location ? Started ? Not started ?21:08
*** anotherjesse has joined #openstack-meeting21:08
*** jakedahn has quit IRC21:08
ttxwill try to find someone at HP to update that21:09
ttxOur second keystone topic for today is the state of the stable/diablo branch21:09
ttxI'd like to make sure every downstream is fine with it the way it stands, before it's tagged21:09
ttx(and a tarball is made of it)21:09
znsttx: is that what anotherjesse is speaking to at the PPB next week?21:09
*** mcohen has joined #openstack-meeting21:09
ttxzns: hmmm... no? I asked anotherjesse to be present to /this/ meeting to discuss it.21:10
anotherjessei'm here21:10
anotherjessejust dropped for 3 minutes21:10
znsAh. OK. Good.21:10
anotherjessethe stable/diablo proposed branch works for us21:10
ttxanotherjesse: great news21:11
ttxIdeally I'd like to hear devcamcar as well21:11
joesavak+121:11
joesavak(yay)21:11
jaypipesttx: wasn't there a patch applied to diablo/stable before trunk?21:11
anotherjessettx: agree to devcamcar would be good21:11
anotherjessettx: perhaps the canoncial guys as well?21:11
ttxjaypipes: not sure what you mean21:11
jaypipesttx: thought I saw something this morning about a changeset being applied to keystone's stable/diablo before hitting trunk...21:12
jaypipesthat was causing a block?21:12
jaypipesmaybe I'm going crazy (definitely could be true)21:12
dolphmjaypipes: yes, that was my mistake... i put them into both branches together, and jenkins issues caused them to land backwards21:12
*** bhall has joined #openstack-meeting21:12
ttxjaypipes: it's not causing a block. There is a change that was pushed to both branches... but only merged successfully in stable/diablo21:13
jaypipesoh, ok, sanity restored :)21:13
jaypipesgot it.21:13
jaypipesok, carry on21:13
*** dendrobates is now known as dendro-afk21:13
ttx#action ttx to contact Canonical folks to make sure stable/diablo keystone looks good for them21:13
ttxlet's see if we can get devcamcar by the end of this meeting21:14
ttxzns: Anything else ?21:14
znsttx: not from me.21:14
znsTx21:14
devcamcarttx: i'm here now21:14
ttxdevcamcar: did you have the opportunity to test Keystone stable/diablo branch ?21:14
devcamcarttx: we've been using it internally for a bit now and it's good to go as far as we can tell21:15
*** dendro-afk is now known as dendrobates21:15
* ttx sees red lights turn to green with pleasure.21:15
dolphmgood to hear21:15
znsawesomeness21:16
ttxdolphm: I'll try to get Ubuntu folks to sign off on it as well21:16
ttxand then we should be good21:16
dolphmgreat21:16
ttxDaviey: around ?21:16
ttxOther questions for Keystone ?21:16
ttxs/Ubuntu/distro/ actually21:17
ttxnot necessarily limited to Ubuntu21:17
ttx#topic Swift status21:17
*** openstack changes topic to "Swift status"21:17
ttxnotmyname: o/21:17
notmynamehi21:17
ttxLooks like we are on track for branching to milestone-proposed on Friday and releasing next Tuesday ?21:17
notmynameeverything looks good. a few more patches to merge21:18
ttx#link https://launchpad.net/swift/+milestone/1.4.421:18
notmynameour internal QA will be taking a whack at it starting soo21:18
notmynameshould be a good release. good features and bug fixes21:18
ttxnotmyname: if anything is blocking, make sure to use the 1.4.4 target sothat it appears on the page21:18
*** YWC has joined #openstack-meeting21:19
ttxso that I know that it's blocked without having to ping someone about it :)21:19
ttxnotmyname: Anything else ?21:19
notmynameI think we're good. I'll check again in the morning, but it looks good21:19
notmynamethe memory leak I mentioned last week21:19
notmynamejust wanted to give an update21:19
*** adjohn_ has joined #openstack-meeting21:20
notmynamewe (meaning mostly gholt) have been looking at a lot of stuff. we've patched several things in swift and eventlet. the eventlet patch is good, but probably not the major problem we were seeing21:20
notmynametesting is continuing21:20
notmynamebut things are looking promising21:20
*** jmeredit has joined #openstack-meeting21:21
ttxcool, continue to keep us posted21:21
notmynamethe eventlet summary is that you should upgrade when the patch hits mainline, but not huge rush there (especially if you aren't using it under very high load like we are)21:21
*** masumotok has quit IRC21:21
jaypipesnotmyname: symptoms?21:21
notmynamelast thing21:21
notmynamejaypipes: proxy servers running out of memory21:22
jaypipesk.21:22
*** bengrue has joined #openstack-meeting21:22
notmynamejaypipes: after <redacted> req/sec for a while21:22
jaypipesnotmyname: just proxy servers? not the other servers?21:22
notmynameya21:22
jaypipesgot it.21:22
notmynamewell, they see the highest load since there are much less of them21:22
notmynamelast thing from me:21:22
jaypipesnotmyname: and they also have to deal with disconnects with the end client the most, right?21:23
*** adjohn has quit IRC21:23
notmynameI'm working on setting up a swift-focused meetup in the bay area in early december. stay tuned for details21:23
ttxOther questions on Swift ?21:23
notmynamejaypipes: it's mostly the asymmetry in the deployment. but disconnects are an issue too21:23
jaypipesnotmyname: no more questions, but I'll follow that stuff closely since Glance uses quite a bit of Swift code...21:24
jaypipesthx21:24
ttxGood transition !21:24
ttx#topic Glance status21:24
*** openstack changes topic to "Glance status"21:24
jaypipeslol21:24
ttx#link https://launchpad.net/glance/+milestone/essex-221:24
jaypipesDanger Will Robinson.21:24
ttxjaypipes: 11 blueprints ! Sounds ambitious.21:24
jaypipesYeah, E2 was a bit of a dumping ground21:24
jaypipesttx: I'll take a gander through them and retarget some to E3.21:25
ttxdoes that mean you need to refine it a bit ?21:25
ttxok21:25
*** salv has joined #openstack-meeting21:25
jaypipesttx: mostly was a braindump for me making blueprints after feedback on the API 2 drafts.21:25
ttxYou should have assignees for all those you keep for E221:25
jaypipesyup.21:25
jaypipesttx: I'll clean up by next week.21:25
ttx#action jaypipes to refine E2 list and set assignees21:25
ttxAnother question: Do you agree https://blueprints.launchpad.net/glance/+spec/swift-location-credentials is complete and already delivered in essex-1 ?21:26
jaypipeslooking...21:26
jaypipesttx: yep, I'll update that one.21:27
ttxjaypipes: Anything else ?21:27
jaypipesttx: just that draft 3 of the API 2 proposal is in progress... thx to all who responded with feedback21:27
ttxjaypipes: I'm on it (the update)21:27
jaypipesttx: ok, thx21:27
ttxQuestions on Glance ?21:28
ttx(a bit tricky this I have to reactivate e1 to retarget things to it)21:29
ttx#topic Nova status21:29
*** openstack changes topic to "Nova status"21:29
ttxvishy: yo21:30
ttx#link https://launchpad.net/nova/+milestone/essex-221:30
ttxvishy: There are a few BPs in there assigned to a generic Nova subteam...21:30
vishyhi21:30
ttxWhich sounds like a recipe for nobody actually doing it.21:30
vishyttx: yes I'm trying to clean those up currently21:30
ttxI'm ok to keep the team as the "Drafter", but I'd prefer to have a more precise developer name or group assigned to actually write the code for it21:30
ttx(at least for the current milestoneà21:31
ttx)21:31
vishywoah21:31
ttxwoah?21:31
vishyyes I will contact all of the teams and get those updated21:31
*** masumotok has joined #openstack-meeting21:31
vishy(my irc client didn't like the encoding on your last comment)21:31
*** tylesmit has joined #openstack-meeting21:31
ttx#action vishy to turn team-owned E2 blueprints into more precise assignments)21:32
Vekheh21:32
ttxà à à21:32
ttxvishy: There are a few things started, without a target, that may actually apply to essex-2:21:32
ttxhttps://blueprints.launchpad.net/nova/+spec/remove-virt-driver-callbacks (blamar?)21:32
ttxhttps://blueprints.launchpad.net/nova/+spec/internal-uuids (Titan team?)21:32
ttxhttps://blueprints.launchpad.net/nova/+spec/nova-volume-snapshot-backup-api (Nova volume ?)21:32
*** mwhooker_ has joined #openstack-meeting21:32
ttxvishy: do you know if those should be complete by E2 ?21:33
vishytargeted21:33
vishyyes they should all be21:33
sorenWhiteboard of https://blueprints.launchpad.net/nova/+spec/remove-virt-driver-callbacks says it's done.21:33
sorenGerrit agrees: https://review.openstack.org/#change,110021:33
*** dwalleck_ has joined #openstack-meeting21:34
vishyyes was merged21:34
*** dwalleck has quit IRC21:34
*** mestery has joined #openstack-meeting21:34
ttxsoren: too bad it wasn't set to Implemented then21:34
* ttx goes to steal more LP karma21:34
ttxyay21:34
* Vek thinks ttx still won't surpass tr3buchet's karma21:34
ttxvishy: last thing: what priority should https://blueprints.launchpad.net/nova/+spec/melange-notifications have ?21:34
vishydarn you beat me21:34
vishyi think we are obsoleting that one21:35
vishysince melange moved to path to incubation21:35
ttx#action vishy to confirm melange-notifications obsolescence and remove it from E221:35
ttxI also wanted to ask about reviews...21:35
tr3buchetttx: i had planned on updating the melange blueprints to that effect21:35
vishytr3buchet is working with melange guys to get that stuff removed (and recreated in the melange project?)21:35
ttxyou can actually reassign a blueprint to another project.21:36
tr3buchetttx: i've confirmed that any of the melange stories which are associated with nova-network are removable21:36
ttxtr3buchet: if needed, ping me off-meeting21:36
tr3buchetwill do21:36
ttxThere are 60 open reviews on Nova, apparently due to too many stale reviews21:36
ttxWith LP we had some convenient way to shelve out of sight those things needing work before being reproposed, by setting back to WorkInProgress21:36
ttxShould we find some way to emulate that with Gerrit ? (mtaylor, jeblair ?)21:37
westmaasttx: is your script that generates ordered reviews still usable after the sqitch?21:37
westmaasswitch*21:37
ttxwestmaas: no. But I guess I could make it extract data from Gerrit21:37
mtaylorttx: you can abandon a review21:37
vishyttx: ooh, i like the idea of WiP21:37
mtaylorttx: we have a todo list item to add a work in progress state21:37
Vekmtaylor: can you abandon a review that someone else has proposed, though?21:38
*** troytoman-away is now known as troytoman21:38
mtaylorVek: I believe that _I_ can :)21:38
devcamcarmtaylor: i've been meaning to ask you  -  i don't get notifications for gerrit merge proposals (i have checked like every-darn-thing)21:38
ttxmtaylor: I just want the "open" reviews to reaklly be the dashboard of reviewable things.21:38
mtaylorttx: I agree21:38
devcamcarmtaylor: but can ask in a bit :)21:38
westmaasttx: I liked that view, not sure if others did, nor do I know the level of work needed to make it work21:38
mtaylordevcamcar: hrm. let's circle back on that after the meeting21:38
ttxwestmaas: I'll have a shot at it.21:38
Vekmtaylor: glance isn't sending notifications of new reviews either, but I'm getting them for nova.21:39
ttxwestmaas: code was at https://code.launchpad.net/~ttx/+junk/reviewlist fwiw :)21:39
*** jwalcik has quit IRC21:39
ttx#action mtaylor to raise prio on implementing a WiP state21:40
ttx#action ttx to see how reviewslist can be revived21:40
mtaylorVek: are you subscribed to the glance project ?21:40
ttxvishy: Anything else ?21:40
mtaylorVek: in https://review.openstack.org/#settings,projects ?21:40
mtaylordevcamcar: ^^21:40
*** mwhooker_ has left #openstack-meeting21:40
Vekmtaylor: dunno what that means.  I remember I used to get them, now I don't...21:40
vishyttx: the thing you emailed me about?21:41
ttxVek, mtaylor, devcamcar -> off-meeting please21:41
bhallmtaylor: I have the same issue.. I subscribe to nova reviews but it keeps losing my setting21:41
mtaylorok. off meeting21:41
vishyttx: for targetting blueprints differently21:41
mtaylorfind me in openstack-dev in a sec21:41
ttxvishy: want to mention that ?21:41
vishyttx: seems like it would be good to mention it in an info21:41
ttxvishy: we can JFDI and write an email too :)21:41
vishyemail is fine21:41
vishycontinue21:41
ttxNova subteam leads: anything you want to mention ?21:42
*** mcohen has quit IRC21:42
ttxQuestions on Nova ?21:42
*** YWC has quit IRC21:43
ttx#topic Horizon status21:43
*** openstack changes topic to "Horizon status"21:43
ttxdevcamcar: o/21:43
devcamcaro/21:43
ttx#link https://launchpad.net/horizon/+milestone/essex-221:43
ttxLooks good -- though you should have assignees.21:43
ttxIf you know for example the team at Nebula will take care of it, but don't know who exactly will do it, you should assign to some Nebula group21:43
ttxand then you can change to someone more precise when you know who.21:44
ttxI just need to know who I can ping for status updates :)21:44
devcamcarhave assignees for blueprints, though the huge number of UX bugs that were filed recently haven't been triaged yet21:44
ttx"null" never answers to me.21:44
devcamcarfair enough21:44
devcamcari'll get assignees on those21:44
devcamcarwe're tearing into the visual re-design, may have some cool screenshots by next week's meetings21:44
ttxdevcamcar: again, you can set a supergroup if you know "someone in that group" will do it21:44
ttx#action devcancar to get assignees for the E2 plan21:45
ttx#action devcamcar  to get assignees for the E2 plan21:45
ttxdevcamcar: Anything else ?21:45
devcamcarttx: nope, pretty quiet week for us, just tearing everything apart and putting it back together :)21:46
ttxdevcamcar: sounds like fun21:46
devcamcaroh yea21:46
ttxQuestions for Horizon ?21:46
*** mcohen has joined #openstack-meeting21:46
ttxdevcamcar, mtaylor: we need to get the repo split (python-module / ref impl) done by E2, btw21:47
*** somik has quit IRC21:47
devcamcarttx: i seriously will fight you guys to the death on that, no offense21:47
mtaylordevcamcar: oh? heckj lied to us then21:47
devcamcarit makes development about an order of magnitude more difficult21:47
devcamcarmtaylor: that is certainly possible21:48
ttxdevcamcar: I thought there was an agreement around that21:48
*** liquidgold has joined #openstack-meeting21:48
devcamcarthat's how it used to be21:48
ttxmtaylor: back to the bribe table21:48
devcamcarused to be 2 separate projects21:48
devcamcari combined them because of what a gargantuan pain it was21:48
devcamcarboth on the dev and on the support side21:48
mtaylordevcamcar: the issue is that it makes distribution/packaging harder - but this might be a longer conversation than in here21:48
mtaylor(plus, you didn't have me automating your life away back then :) )21:49
devcamcarmtaylor: agreed, is a longer conversation21:49
ttx#action mtaylor devcamcar to discuss and converge to a common view on the need to split repos for horizon (or not)21:49
devcamcari'm not completely opposed but it can't be like it was before21:49
devcamcartoo painful21:49
mtaylorI agree. I want to solve problems, not create them21:49
mtayloralthough I know some people probably disagree :)21:49
ttxI know some distros are waiting for the dust to settle before packaging Horizon.21:50
*** wwkeyboard has joined #openstack-meeting21:50
ttxso I'd like the decision taken in time for E221:50
mtaylorI imagine we can sort it out in short order - just probably not in here21:50
ttxagreed21:50
ttx#topic Incubated projects and other Team reports21:50
*** openstack changes topic to "Incubated projects and other Team reports"21:50
ttxdanwent, troytoman: o/21:50
danwent#info Quantum essex-1 dropped last week (https://launchpad.net/quantum/+milestone/essex-1).  Major new items included packaging support (RPM/DEB), DHCP support in Quantum Manager, keystone middleware, and devstack integration.  If you are interested in packaging Quantum for your distro, please contact us.21:50
danwentother than that, essex-2 is now open: https://launchpad.net/quantum/+milestone/essex-221:51
danwentwe'll be coordinating with Trey and the nova-network folks on some more work that needs to be done on QuantumManager in nova.21:51
ttxdanwent: you mean you include packaging code in Quantum itself ?21:51
* ttx downloads tarball.21:52
danwentyes, the ability to generate debs/rpms21:52
bhallyep21:52
danwentis that not kosher? :)21:52
*** jrouault has joined #openstack-meeting21:52
soreneep21:52
sorenNot quite :)21:52
ttxdanwent: it's generally frowned upon21:52
sorenIt's less of a problem nowadays, but it's still frowned upon.21:52
ttx#action distro people to look into Quantum packaging integration effort to see if it can work with them21:53
danwentOk, who should we work with on this?21:53
danwentgreat21:53
ttxdanwent: I'll make them contact you21:53
danwentsounds good21:53
ttxtroytoman: any news on Melange side ?21:53
troytomanwrt melange, have mostly been focused on getting the project set up on launchpad and moving over blueprints21:54
troytomanthis week will engage with mtaylor on gerrit integration21:54
ttxtroytoman: I'll have a circular look and see if anything needs to be set up additionally21:54
ttx#action ttx to look up Melange setup and help where needed21:55
troytomanthanks ttx21:55
ttxtroytoman: do we have code up yet ?21:55
troytomanit is on github but needs to be moved into the openstack repo21:55
ttxok21:55
ttxAny other team lead with a status report ?21:56
*** somik has joined #openstack-meeting21:56
annegentleme!21:56
ttxannegentle: go for it!21:56
annegentleA couple of doc items to report, we met yesterday for our monthly meeting.21:56
annegentleA new feature in the doc tool chain lets us publish an RSS feed for a manual based on a hand-maintained revision history.21:56
annegentleSee it at http://docs.openstack.org/api/openstack-compute/1.1/content/  and I'll also send an email to the mailing list to solicit feedback.21:56
annegentleOn Friday 11/11/11 a few Rackers held a Hackathon in Austin and experimented with epub output through our toolchain.21:57
annegentleJust a few bugs to work through for "prettiness" but a decent output to add to the tool box.21:57
*** SumiNaiksatam has joined #openstack-meeting21:58
*** debo_os has joined #openstack-meeting21:58
ttxsounds cool21:58
annegentleLastly, we have a new blueprint for a site that helps people learn the OpenStack APIs, with wireframe design coming soon and feedback is welcome. https://blueprints.launchpad.net/openstack-manuals/+spec/api.openstack.org21:58
ttxsounds übercool.21:58
ttx#topic Open discussion21:58
*** openstack changes topic to "Open discussion"21:58
*** jog0 has joined #openstack-meeting21:58
ttxAnything, anyone ?21:58
ttxPoll: is #openstack-dev channel too noisy with all the notifications for all the projects sent there ?21:59
jaypipesttx: not IMHO21:59
annegentleI think it's okay21:59
jk0yeah, it's not bad22:00
*** sleepsontheflo-2 has joined #openstack-meeting22:00
ttxok then.22:00
ttxTime to give the floor to the network dudes.22:00
ttx#endmeeting22:00
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"22:00
openstackMeeting ended Tue Nov 15 22:00:48 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-15-21.03.html22:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-15-21.03.txt22:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-15-21.03.log.html22:00
*** adjohn_ has quit IRC22:00
ttxThanks everyone !22:00
*** edgarmagana has joined #openstack-meeting22:01
danwentthanks ttx, right on time22:01
danwent#startmeeting22:01
openstackMeeting started Tue Nov 15 22:01:09 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
edgarmaganaHola!22:01
*** Vek has left #openstack-meeting22:01
*** jk0 has left #openstack-meeting22:01
ttxedgarmagana: hola!22:01
danwenthello all!22:01
salvHi all!22:01
somikHello folks!22:01
GheAwayhi everyone22:01
danwent#info agenda : http://wiki.openstack.org/Network/Meetings22:01
*** GheAway is now known as GheRivero22:01
tylesmithi22:01
danwenthey tyler, glad you could make it22:01
debo_oshi22:01
danwentok, troy, you around?22:02
carlplong time no see everyone22:02
danwentthis is the part where I skip the melange update and start on quantum, only to have troy then appear22:02
danwent#topic quantum status22:02
*** openstack changes topic to "quantum status"22:02
*** Tushar has quit IRC22:02
danwent#info great work on essex-1, it was released on thursday22:03
danwentnow we're on to essex-222:03
*** sleepsontheflo-1 has quit IRC22:03
*** anotherjesse has quit IRC22:03
danwentwe already have some reviews of things we decided not to do in essex-1: https://review.openstack.org/#q,status:open+project:openstack/quantum,n,z22:03
*** thingee has left #openstack-meeting22:03
danwentparticularly, Salvatore's API framework stuff would be good to get reviewed ASAP, so we can make progress on other API work.22:04
*** anotherjesse has joined #openstack-meeting22:04
danwentsalv says that this was refactored for the packaging work since the last set of reviews, so we should re-review and retest.22:04
salvI'm not particularly concerned but the more the eyes, the better the code22:05
danwent#info please target any essex-2 work using launchpad: https://launchpad.net/quantum/+milestone/essex-222:05
*** ying has joined #openstack-meeting22:05
danwentA few areas that I think are missing blueprints for essex-2 are 1) jenkins + system test, 2) dashboard work.22:05
danwentcarlp, can you comment on plans for jenkins/system test?22:06
carlpdanwent: sure22:06
*** joesavak has quit IRC22:06
carlpso we have the jenkins slave in place, and there are two nodes ready for testing22:06
carlpAt this point what we need are tests :)22:06
danwentOk, so let's get a BP for that.22:07
carlpI think I already set one up22:07
*** mikeyp has quit IRC22:07
danwentgreat… is it targeted for essex-2?  (i.e., do i need to refresh) :P22:07
carlpAn excellent question22:07
*** dwalleck_ has quit IRC22:07
carlpI have this one: https://blueprints.launchpad.net/quantum/+spec/quantum-functional-tests22:08
carlpit's kind of the master, I believe the quantum-functional-test-environment is what needs to be targeted to this release22:08
danwentyes, that makes sense.22:09
danwentI'll target it.22:09
carlpSalvatore had some plans in Boston, but I don't know if they made it to code or even a BP22:09
*** anotherjesse has quit IRC22:10
salvsorry I droppe for a bit.22:10
danwentcarlp: are you planning on creating functional tests yourself, or are you looking for others to do that?22:10
*** jmeredit has quit IRC22:10
salvPlans around what?22:10
carlpTo start with, I did not want to create some functional tests myself.  I was going to leave that to the experts :)22:10
carlpThat said, my long term goal is to become an expert22:11
danwentOk22:11
*** mrmartin has quit IRC22:11
carlpsalv: plans around functional testing22:11
danwent#todo #danwent create BP and find owner for initial set of functional tests targeted at essex-222:11
salvcarlp: Ok. I haven't made any progress on that, and I don't think I'll have cycles to work on testing before essex-322:11
carlpok, good to know22:12
edgarmaganado the functional tests include both plugins?22:12
danwentyeah, salv is pretty loaded with API work this cycle22:12
salvI honestly hoped somebody else would pick the whole testing story (functional/integration/and scale)22:12
danwentyup, we're looking for volunteers.  nicira will definitely be picking up some of the work, but would be great if others pitched in.22:12
danwentedgar:  original plan was to just use OVS so there was no dependency on physical network gear22:13
carlpI would like to do that, my day job has been eating a lot more of my time recently than I would like.  That will probably change as we get closer to the end of the year22:13
*** uri_ has joined #openstack-meeting22:13
edgarmaganadan: thanks!22:13
danwentI believe mark voelker was planning on replicating a jenkins environment that had the right cisco hardware22:13
carlpedgarmagana: The environment I've built can support OVS and the new VLAN manger.  Other stuff will need different environments.22:14
edgarmaganaFYI. Mark is on temporal LOA (He just became a father)22:14
salvcarlp: the new VLAN manager being the one I'm trying to build? :)22:14
carlpI recall that as well, and if you're around Mark, shoot me an email and I'll help get you started22:14
carlpsalv: I believe so, yes22:14
danwentedgar:  yup, you all should see the awesome pic22:14
salvcarlp: ok.22:15
edgarmaganacarlp: got it22:15
*** KyleM1 has left #openstack-meeting22:15
danwenthttp://t.co/oV5vUZC22:15
danwentOk, anything else on jenkins work?22:15
carlpNope, I think that is about it22:16
danwentk, salv: API work for essex-2, particular around "operational status"22:16
salvOkay, the plan is to put into Essex-2 two items:22:16
salv1) Operational Status22:16
salv2) Filters for request22:17
salvWhile I see Item #2 technically more challenging, it is actually easier as I just need to "borrow" code from Openstack API22:17
danwentGreat.  I talked with Anne.  She sent an email to the main openstack list about how to handle repos for future versions of API specs.22:17
salvItem #1 is instead technically less challenging, but there's more discussion on it. I received good feedback on the spec I proposed, but (shame on me) never updated it.22:18
danwentDo you plan on flushing out the API changes as modifiecations to the API docs in the repo, or do you want to publish them some other way?22:18
salvdanwent: good question. I will do whatever Openstack API has done for transition from 1.0 to 1.122:18
salvbut I need to sync up with Anne on that22:19
danwentgreat22:19
salv#action Salvatore to sync up with Anne on best way for updating API doc22:19
*** masumotok has quit IRC22:19
danwentOk, anything else on API?22:19
salvNow, on the operational status, the only thing we haven't probably thoroughly discussed is what the API should do if the plugin does not support22:19
danwentYing, were you looking at doing "tags"?22:20
salvthe concept of Operational status22:20
salvbut we can discuss that on the mailing list.22:20
danwentsorry salv:  yes, ML is probably best for design discussions22:20
danwentsalv, anything else on API front?22:20
yingdanwent: I will check on tags for API,22:21
salvno, that is all on the API22:21
danwentying: great.  is there already a BP for this?22:21
danwentif not, please create one and target it22:21
yingdanwent: no, not yet.22:21
danwent#action #ying create blueprint for API tags work22:22
danwentOk, mark is not here, but perhaps arvind or tyler can comment on plans around Quantum + Dashboard?22:22
tylesmitI don't see Arvind here, and I'm not in the loop on Dashboard.22:22
danwentthanks tyler22:23
danwent#action #danwent send email to ML about dashboard work for essex-222:23
*** dendrobates is now known as dendro-afk22:23
*** dendro-afk is now known as dendrobates22:23
*** dwalleck has joined #openstack-meeting22:23
danwentI think this is a really important area to make progress on in essex-2, as dashboard is the most visible way to demo Quantum22:23
danwentOk, somik, do you need to fill-out the BP for the authz work?22:24
somikI have a placeholder BP with the non ideal mechanism to handle authZ22:24
*** shwetaap has joined #openstack-meeting22:24
somikbut I will fill out the ideal way, where we would require nova changes as well.22:24
danwent#action #somik complete authz blueprint, send out for feedback22:25
danwentAnd last but not least, nova parity.22:25
danwentBrad will be working on L3 gateway + NAT using the nova-network mechanism, right?22:25
danwentthis is the same mechanism supported by the VLANManager, but QuantumManager needs some updates to work correctly with it.22:26
danwent#action: #danwent confirm with #bhall about L3 + NAT work22:26
danwentand debo, you're planning on working on the cloudpipe VPN stuff?22:27
danwentapparently everyone is ignoring me :)22:27
salvUpdate from me on nova-parity: I'm working on security groups and about to push a driver for implementing them on XenAPI22:27
danwent#action #danwent work with #debo_os on cloudpipe vpn22:28
salvwill circulate an email in the next days about how to do that through Quantum22:28
mesteryWe're not ignoring you Dan :)22:28
bhalldanwent: yup22:28
danwentsalv: cool.  there's been a lot of chatter around security groups, so yes, probably good to raise that to the ML.22:28
salvdanwent: we're not ignoring you, we're trolling you :)22:28
bhalldanwent: bp is filed (sent you a link already)22:28
danwentmestery:  ah, now that you've spoken, can we start assigning tasks to you? :P22:28
danwentbhall: k, thanks.22:29
debo_osdanwent: sorry, I had stepped out for 2m. Yes I am going to do the CP work22:29
danwentdebo_os: great.22:29
danwentdebo_os: let's target BP for essex-2, just so we keep tracking it.22:30
danwentwork may be split across essex-2 and essex-322:30
debo_osdanwent: sure, that works22:30
danwentok, any other nova-parity work?22:30
bhallI think thats it for e2 that I'm aware of22:31
danwentYup, a pretty full plate22:31
danwentThere's also a proposal to fold plugins.ini into Quantum.conf .  We didn't want to do this right before the milestone release, but is anyone violently opposed?22:31
danwentthe goal is just to have few config files, and be able to specify all config by specifying a path to a file (not a hardcoded file location)22:32
danwentfew -> fewer22:32
danwentOk.  We'll definitely give the ML a heads up before doing it, as it make break some automation scripts.22:33
danwentAnd finally, I will be doing some super fun documentation work in essex-2.22:33
bhalldanwent: I have some notes for you on installing from packages/etc22:34
carlpdanwent: and we love you for that :)22:34
bhallmay have taken some of the fun out of your work, sorry22:34
danwentmainly focusing on getting all content out of the README and into "official" documentation22:34
salvdanwent: you're the quantum hero :022:34
edgarmaganasalv: +122:34
danwentwell, if you really loved me you'd write some docs :P22:34
danwentand don't forget that salv wrote the API spec22:35
danwentthat was a beat22:35
danwentbeast22:35
* salv just remembered I'm supposed to do the wadl22:35
annegentledanwent and salv have you gotten Oxygen licenses? If not let me know. That might take some pain out :)22:35
danwentanyway, I will send an email to the list with info on how to modify the docs.  hopefully people will see that it is easy and fun, then decide to pitch in :)22:35
danwentannegentle: no, but that would be fantastic22:35
salvannegentle: yup, I have one22:35
annegentlegreat, cool22:36
danwentsalv: didn't nachi provide a wadl description?22:36
salvOh right!22:36
danwentI didn't end up having time to confirm that it was correct, but it definitely should be a good starting point22:36
*** rnirmal has quit IRC22:36
salvDid we merged it into the doc repository?22:36
annegentlesalv: I'll send you the Oxygen Rackbook framework which should help with WADL authoring too22:37
danwentsalv: don't think so… so thanks for remembering it.22:37
danwentsalv: can you add an item to track this work (even if you don't assign it to yourself?)22:37
salvannegentle: that would be supergreat as I previously could use Oxygen only as a cool XML editor and was pretty much disappointed I couldn't do proper authoring22:37
salvdanwent: targeting essex-3, yes I can22:38
danwentgreat22:38
*** andrewbogott has left #openstack-meeting22:38
danwentOk, anything else folks are looking at targeting for essex-2?22:38
salvI want to raise awareness on a long-standing bug22:38
salvhttps://bugs.launchpad.net/quantum/+bug/83753522:38
uvirtbotLaunchpad bug 837535 in quantum "plugins do not comply with quantum_plugin_interface" [Medium,In progress]22:38
uri_so will L3 + NAT not be integrated w Quantum during essx2?22:38
danwentessex-2 ends 12/1522:38
*** martines has joined #openstack-meeting22:39
martinesi, you there?22:39
martiness/i/hi22:39
*** dendrobates is now known as dendro-afk22:39
bhalluri_: do you mean in nova?22:39
danwenturi_: that should already be targeted22:39
martinessorry folks, wrong focus :(22:39
danwenthttps://blueprints.launchpad.net/quantum/+spec/nova-parity-nat22:39
uri_was trying to understand from above, if L3 integrates w Nova or Quantum in the essx2 timeframe22:40
danwentsalv: yes, I think targeting the bug makes sense.22:40
salvdanwent: k, thanks22:40
bhalluri_: nova for e222:41
danwenturi_: in essex-2, which is completed Dec. 15th, we're targeting the QuantumManager being able to support L3 gateways + NAT with Quantum networks.22:41
danwentthese L3 gateways + NAT will be implemented using the exact same mechanism that the nova-network VLANManager uses22:41
danwentthis is so we can quickly get to parity with nova networking, which is one of our primary goals for essex.22:42
*** dendro-afk is now known as dendrobates22:42
uri_thx22:42
danwentsalv:  to be clear, the plan for that bug is to change the definition of the plugin API to match the "de facto" standard?22:42
*** yogirackspace has left #openstack-meeting22:43
salvdanwent: this looks the simplest way so far22:43
danwentsalv: yup, I agree22:43
danwentOk, and one last topic is that during the main openstack meeting, ttx mentioned that storing packaging code with the main project source is "not preferred"22:43
danwentI think their goal is to have all packaging code separate, maintained by the distro itself.22:44
danwenthowever, this definitely doesn't mean all the packaging work will be lost22:44
*** anotherjesse has joined #openstack-meeting22:45
danwentI think we'll probably just end up moving some of the packaging only files out once external distros have completely taken up the task of packaging Quantum22:45
tylesmitCorrect me if I'm wrong, but doesn't that pretty much just mean not having a unified setup.py?22:45
*** jmeredit has joined #openstack-meeting22:45
danwenttylesmit: I'm guessing it refers to the setup.py files and the corresponding config files, but to be honest I'm not sure.22:45
danwentttx + soren said they would contact us with thoughts.22:46
danwentwe'll keep the list looped into the discussion22:46
danwentOk, any other quantum questions/topics?22:46
danwent#topic open discussion22:47
*** openstack changes topic to "open discussion"22:47
danwentok, anything more generally?22:47
danwentDid folks see the DNS-as-a-service proposal?22:47
salvsaw the email, did not read it yet22:48
danwenthttp://etherpad.openstack.org/HkEvt4crw922:48
carlpHeard it was proposed, haven't looked22:48
danwentanyway, just wanted to make sure folks were aware.  I don't know of anyone else currently working on this type of stuff.22:48
danwent#info DNS-as-a-service proposal: http://etherpad.openstack.org/HkEvt4crw922:48
danwentOk, anything else?22:48
danwentok, that's a wrap.  have a good one folks.22:49
danwent#endmeeting22:49
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"22:49
openstackMeeting ended Tue Nov 15 22:49:20 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-15-22.01.html22:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-15-22.01.txt22:49
carlpthanks all!22:49
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-15-22.01.log.html22:49
salvthanks, talk to you next week!22:49
somikhave a good one stackers!22:49
*** tylesmit has left #openstack-meeting22:49
*** debo_os has quit IRC22:50
uri_who is driving DNSaaS?22:50
danwenturi_: this was just an informal proposal22:50
danwentemail was from: endre.karlson@gmail.com22:50
uri_from you?22:50
danwentnope, I was just bringing this to folks attention22:51
uri_i see thx. have a good one!22:51
*** SumiNaiksatam has quit IRC22:51
*** cdub has joined #openstack-meeting22:51
*** jog0 has left #openstack-meeting22:51
*** jog0 has joined #openstack-meeting22:52
*** GheRivero has quit IRC22:52
*** jog0 has left #openstack-meeting22:52
*** ying has quit IRC22:52
*** somik has quit IRC22:52
*** mestery has left #openstack-meeting22:54
*** dwcramer has quit IRC22:54
danwenturi_: yup, bye!22:55
*** mcohen has left #openstack-meeting23:02
*** aclark_ has joined #openstack-meeting23:03
*** AlanClark has quit IRC23:03
*** carlp has quit IRC23:03
*** aclark_ is now known as AlanClark23:07
*** jmeredit has quit IRC23:07
*** uri_ has quit IRC23:08
*** bhall has quit IRC23:09
*** troytoman is now known as troytoman-away23:11
*** dendrobates is now known as dendro-afk23:20
*** adjohn has joined #openstack-meeting23:22
*** edgarmagana has quit IRC23:22
*** dendro-afk is now known as dendrobates23:23
*** bhall has joined #openstack-meeting23:42
*** bhall has quit IRC23:42
*** bhall has joined #openstack-meeting23:42
*** carlp has joined #openstack-meeting23:45
*** nati2 has joined #openstack-meeting23:46
*** ewanmellor has quit IRC23:47
*** jakedahn has joined #openstack-meeting23:56

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