Tuesday, 2012-04-03

*** openstack has joined #openstack-meeting18:58
*** ChanServ sets mode: +o openstack18:58
*** dolphm_ has quit IRC18:58
*** openstack` has joined #openstack-meeting18:59
*** openstack has quit IRC18:59
*** openstack has quit IRC18:59
LinuxJedigrr... ok, how to change it's nick?18:59
*** johnpur has joined #openstack-meeting19:00
*** openstack` is now known as openstack19:00
*** ChanServ sets mode: +o openstack19:00
mtaylorLinuxJedi rocks19:01
LinuxJedilol, not sure about that, but it is up and running at least :)19:01
*** openstack has quit IRC19:02
*** openstack` has joined #openstack-meeting19:02
*** openstack has quit IRC19:02
*** openstack has joined #openstack-meeting19:02
*** openstack has joined #openstack-meeting19:02
*** ChanServ sets mode: +o openstack19:02
*** ChanServ sets mode: +o openstack19:02
*** dolphm has quit IRC19:02
*** dolphm has quit IRC19:02
LinuxJediok, that wasn't me19:02
LinuxJediok, that wasn't me19:02
*** dolphm has joined #openstack-meeting19:03
*** dolphm has joined #openstack-meeting19:03
*** openstack has quit IRC19:03
*** openstack has quit IRC19:03
*** jsavak has joined #openstack-meeting19:03
mtaylorso - anybody want to talk about CI?19:03
*** openstack` is now known as openstack19:04
*** ChanServ sets mode: +o openstack19:04
*** openstack` has joined #openstack-meeting19:04
jeblairi am not opposed to that19:04
*** openstack has quit IRC19:04
*** openstack has quit IRC19:04
*** openstack has joined #openstack-meeting19:04
*** openstack has joined #openstack-meeting19:04
*** openstack has joined #openstack-meeting19:04
*** ChanServ sets mode: +o openstack19:04
*** ChanServ sets mode: +o openstack19:04
jeblairopenstack is, apparently.19:04
jeblairopenstack is, apparently.19:04
*** openstack has quit IRC19:05
*** openstack has quit IRC19:05
LinuxJedithe logs on it say the same as that, "Disconnected by services"19:05
*** openstack has joined #openstack-meeting19:05
*** openstack has joined #openstack-meeting19:05
*** openstack has joined #openstack-meeting19:05
*** ChanServ sets mode: +o openstack19:05
*** ChanServ sets mode: +o openstack19:05
* LinuxJedi wonders what services are kicking it off19:05
* LinuxJedi wonders what services are kicking it off19:05
LinuxJediWARNING 2012-04-03T19:05:40 Error message from FreeNode: Closing Link:       openstack/openstack (Disconnected by services)19:06
LinuxJediWARNING 2012-04-03T19:05:40 Error message from FreeNode: Closing Link:       openstack/openstack (Disconnected by services)19:06
jeblairwow.  helpful19:06
*** troytoman is now known as troytoman-away19:06
jeblairwow.  helpful19:06
*** troytoman is now known as troytoman-away19:06
*** openstack has quit IRC19:06
*** openstack has quit IRC19:06
*** openstack has joined #openstack-meeting19:06
*** openstack has joined #openstack-meeting19:06
*** ChanServ sets mode: +o openstack19:06
*** ChanServ sets mode: +o openstack19:06
*** joesavak has quit IRC19:07
*** joesavak has quit IRC19:07
jeblairLinuxJedi: do you have access to the MOTD?19:07
jeblairLinuxJedi: do you have access to the MOTD?19:07
jeblairor any other server messages, or messages from nickserv?19:07
jeblairor any other server messages, or messages from nickserv?19:07
LinuxJedijeblair: it doesn't log it, just that there is one.  Nickserv says "password accepted"19:07
*** openstack has quit IRC19:07
LinuxJedijeblair: it doesn't log it, just that there is one.  Nickserv says "password accepted"19:07
*** openstack has quit IRC19:07
LinuxJedijeblair: I *think* it is a ban19:07
jeblairit feels that way.19:08
*** openstack has joined #openstack-meeting19:08
*** openstack has joined #openstack-meeting19:08
*** openstack has joined #openstack-meeting19:08
*** ChanServ sets mode: +o openstack19:08
*** ChanServ sets mode: +o openstack19:08
*** openstack has quit IRC19:08
*** openstack has quit IRC19:08
LinuxJedianyone know any Freenode IRCops?19:08
mtaylorI don't19:08
jeblairnot anymore19:09
mtaylorI would not mind getting chanserv access to this room...19:09
*** openstack has joined #openstack-meeting19:09
*** openstack has joined #openstack-meeting19:09
*** ChanServ sets mode: +o openstack19:09
*** ChanServ sets mode: +o openstack19:09
LinuxJediwant me to kill meetbot for now?19:09
LinuxJediwant me to kill meetbot for now?19:09
jeblairLinuxJedi: if you have the creds for the nick, maybe startup an irc client from that server?19:09
jeblairLinuxJedi: if you have the creds for the nick, maybe startup an irc client from that server?19:09
LinuxJedijeblair: ++19:09
jeblairand see if you get a helpful message19:10
*** openstack has quit IRC19:10
LinuxJedijeblair: ++19:09
jeblairand see if you get a helpful message19:10
*** openstack has quit IRC19:10
*** openstack has joined #openstack-meeting19:10
*** openstack has joined #openstack-meeting19:10
*** openstack has joined #openstack-meeting19:10
*** ChanServ sets mode: +o openstack19:10
*** ChanServ sets mode: +o openstack19:10
*** openstack` has quit IRC19:10
*** dolphm has quit IRC19:10
*** openstack has joined #openstack-meeting19:11
*** ChanServ sets mode: +o openstack19:11
LinuxJediok, that should do it19:12
LinuxJedijeblair: I seemed to have accidentally spawned 2 meetbots before and they were fighting ;)19:12
*** dolphm has joined #openstack-meeting19:13
LinuxJedimtaylor: ok, so back to our regularly scheduled meeting I think ;)19:13
jeblairi did that with my audio and lighting control daemon last night... it was amusing.  :)19:13
*** dolphm has quit IRC19:13
LinuxJeditry it with MySQL, it is so much fun :)19:14
openstackMeeting started Tue Apr  3 19:14:56 2012 UTC.  The chair is LinuxJedi. Information about MeetBot at http://wiki.debian.org/MeetBot.19:14
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.19:14
LinuxJedi#topic CI meeting19:15
*** openstack changes topic to "CI meeting"19:15
LinuxJedimtaylor: meeting started, you have the chair ;)19:15
*** lloydde has quit IRC19:15
mtaylorhow's everybody doing?19:15
LinuxJedigood thanks19:15
jeblairsuper awesome19:15
*** dolphm has joined #openstack-meeting19:16
mtaylorso - let's start with LinuxJedi - wanna talk about jenkins job templates and api stuffs?19:16
LinuxJediso, I can't remember if I covered this last week but now in puppet we have a new module which will automatically spray Jenkins with our default jobs for any given project19:17
LinuxJedithere is one project on Openstack now using this and mtaylor has since fixed a few minor bugs and made some improvements19:17
*** dolphm has quit IRC19:17
mtaylorit's the bees knees19:18
LinuxJedithe current problem is any new project or change to any of the building blocks that makes the jobs means Jenkins is restarted19:18
LinuxJediso I'm working on getting it to fire the API call to reload Jenkins instead (I have a prototype of this working)19:18
jeblaironce that's taken care of, i think we can roll it out to more openstack projects; but we're going to have to do that carefully since they aren't all standardized yet.19:19
mtaylorjeblair: good way to ensure they're standardized :)19:19
LinuxJedinext steps are: 1. load Jenkins jobs in using the API instead of spraying files. 2. support builders other than oneiric.  3. support jobs other than python19:19
mtaylorLinuxJedi: add to todo list, an ensure param for the job class19:19
LinuxJedimtaylor: job class?19:20
mtaylorLinuxJedi: that can toggle the diabled button, and can also ensure gone19:20
LinuxJedimtaylor: ++19:20
mtaylorLinuxJedi: so that we can ensure => present , ensure => diabled, ensure => absent19:20
* mtaylor realized we need this with the gate-* rename patch19:20
LinuxJedimtaylor: that will be easier once I switch to Ruby instead of Puppet scripting19:20
* LinuxJedi is 90% there with that19:21
mtaylorwill you remind me (and the viewing public) what the ruby scripting was in support of?19:21
LinuxJedioh, so puppet being non-procedural doesn't support things like foreach...19:22
LinuxJedithere is a way around this using defined types and arrays19:22
LinuxJedibut it only works for one level of "foreach"19:22
LinuxJediafter that arrays get flattened19:22
*** reed has quit IRC19:22
LinuxJediplus we can do API stuff19:22
*** dolphm has joined #openstack-meeting19:23
LinuxJediwe need that so that we can have oneiric and natty jobs for certain projects19:23
*** dolphm has quit IRC19:23
jeblairLinuxJedi: is it worth doing this in puppet/ruby, or would everyone be happier if we had puppet just call out to a python program that did the work? :)19:23
*** troytoman-away is now known as troytoman19:23
mtaylorawesome. makes sense.19:23
LinuxJedijeblair: I would be a lot happier if I didn't get my hands dirty with Ruby here ;)19:24
mtaylordon't we have to do it in ruby though because this is about job template expansion?19:24
LinuxJedimtaylor: that depends on whether you want puppet to own the XML19:25
mtaylorso you can say "class job { 'python-glance-client': target => [oneiric,natty] }19:25
mtaylorand have target do something sensible19:25
LinuxJedimtaylor: yes, that is the plan19:25
mtaylor(or something - I made that up of course)19:25
*** dolphm has joined #openstack-meeting19:25
LinuxJedimtaylor: the bit that makes it harder is we would need an oneiric and natty job for some but not others (such as tarball)19:25
*** joesavak has joined #openstack-meeting19:25
LinuxJedimtaylor: I have a way of expressing that too which works19:26
*** lloydde has joined #openstack-meeting19:27
LinuxJedimtaylor: I think it will end up with jobs called 'gate-python-glance-client-oneiric-python27'19:28
LinuxJediand likewise for natty19:28
*** jsavak has quit IRC19:28
mtaylorI think that's fine if that's not how I actually have to manage them19:28
LinuxJedimtaylor: if there was a switch in the job to automatically change between them (no idea how we would do that) it would solve a lot of problems19:29
LinuxJedimtaylor: or if a job could build on multiple simultaneously (again I have no idea how to do that)19:29
jeblairthere's matrix jobs19:29
LinuxJedimatrix jobs?19:30
jeblairthere's one19:30
*** dolphm has quit IRC19:30
LinuxJediarse, ok I have been trying to solve a problem that doesn't exist then :)19:30
mtaylorjeblair: didn't we not like how that reported back to gerrit though?19:31
jeblairthe variable is provider there, but build slave is also something that can be varied19:31
jeblairmtaylor: i'm not sure we ever had a matrix job report to gerrit?19:31
mtaylorjeblair: we tested it19:31
jeblairmtaylor: okay, i don't recall that19:31
mtaylorjeblair: it reports the url of the top level job, and then it's several clicks to the specific thing19:31
mtaylorso you can't tell from gerrit whether it failed on natty or on oneiric19:32
mtaylor(we were thinking about it for python26/python27 IIRC)19:32
mtaylorand the thought was that we might want to have gerrit trigger grok matrix jobs differently or something19:32
jeblairmtaylor: okay, i'll take your word for it.  that's certainly true for post-build triggers, seems reasonable it would be for matrix jobs too19:32
LinuxJediso stick with multiple jobs instead of matrix jobs?19:33
jeblairwe didn't have both 26/27 jobs until a few weeks ago, so it hasn't been a problem until now19:33
annegentledo I want matrix jobs for doc jobs?19:33
*** milner has joined #openstack-meeting19:33
mtaylorannegentle: for the essex/diablo thing? or?19:34
annegentlemtaylor: yep, for essex diablo "root" or /trunk19:34
jeblairannegentle: i don't think so.  i haven't fully thought about your question, but my initial thought is we should treat it like the tarball jobs19:34
mtaylorannegentle: I believe we can do that more naturally19:34
annegentlejeblair: oh, interesting, yeah a lump of docs19:34
jeblairwhich know to build tarballs differently for different branches19:34
*** joesavak has quit IRC19:35
*** dolphm has joined #openstack-meeting19:35
jeblairLinuxJedi: so it sounds like matrix jobs would solve your problem, but not in a gerrit-friendly way19:35
LinuxJedijeblair: sure, so, should I not use it?19:36
jeblairi think not -- gerrit friendliness is important19:36
LinuxJedijeblair: my personal opinion would be it would be a lot cleaner (and easier to implement) at the cost that we may have to patch gerrit at some point19:36
LinuxJedidamn :)19:36
jeblairit's not gerrit that needs to be patched as much as the gerrit trigerr plugin19:36
jeblairthat's possibly easier19:37
mtayloryeah - I think it would be easier for us, but less good experience for the devs19:37
jeblairif we did that, it might be an opportunity to solve another problem i'd like to solve19:37
LinuxJediko, I will finish implementing the way I was doing it for now then19:37
jeblairi actually want only one job triggered in jenkins for a change, and i want it to trigger other jobs, but i want the report back to look nice.19:37
mtaylorcool. - but let's definitely keep our eyes on fixing the trigger plugin at some point19:37
LinuxJedimtaylor: in other news, I may bump finishing the meetbot replacement up my todo list ;)19:38
mtaylorjeblair: oh my, you're getting fancy19:38
jeblairi think those are _nearly_ the same issue as far as the plugin goes -- matrix jobs and job-triggered jobs.  they both produce composite output19:38
*** sandywalsh has quit IRC19:39
jeblairmtaylor: it's the only way i can think of to ensure the correct ordering of testing and merging of changes.19:39
jeblairwe don't do what we intend to at the moment, it just happens to work like that most of the time.  as we get more jobs that run longer, we'll get more changes merged out of order.19:39
mtaylorjeblair: it also would allow us to test merge before we bother testing other things19:39
LinuxJediI like that idea :)19:40
mtaylorshould that be your next major dev project?19:40
jeblairi think it would be a good one19:40
*** nati has joined #openstack-meeting19:40
mtaylork. works for me19:41
LinuxJediother things I have done this week: meetbot broke and I restarted it ;)19:41
jeblairLinuxJedi: i'm not sure this will get done in time to be useful for your current problem though.19:41
LinuxJedijeblair: it is OK, I can always switch the way it is done quite easily afterwards19:41
jeblairmeetbot still needs to be puppetized, right?19:42
LinuxJedijeblair: yep, I almost finished that in Seattle, but lots of more important things keep coming up19:43
LinuxJedijeblair: I have a branch in which it "works" but there needs to be a few finishing touches IIRC19:43
*** Madkiss has joined #openstack-meeting19:44
LinuxJedimtaylor: if it is OK with you, once the Jenkins Jobs improvements are out of the way I'd like to finish meetbot19:45
LinuxJedimtaylor: one main advantage is puppet will make sure it is running on every run ;)19:45
jeblairthat seems useful and timely.  :)19:46
*** dwalleck has joined #openstack-meeting19:47
annegentleso for Thursday, release day, should I just update the doc jobs I have or try to get help with treating them like tar ball jobs?19:47
annegentledo any of you have the bandwidth for helping me this week?19:47
*** dendro-afk is now known as dendrobates19:47
LinuxJedimtaylor: oh, whilst I remember, this says Ubuntu SSO is any day now: http://meta.askubuntu.com/questions/2837/moving-to-ubuntu-single-sign-on19:48
jeblairannegentle: i believe i can help19:48
annegentlejeblair: thank you thank  you19:49
annegentleI'm sorry if I'm interrupting your meeting flow :)19:49
*** dolphm has quit IRC19:49
jeblairannegentle: well, the chair doesn't seem to object.  :)19:49
LinuxJedimtaylor: so a job possibly for one of the new guys is to investigate moving over to Ubuntu SSO?19:49
jeblairso, um, quick update from me:19:51
jeblairi typed this up while LinuxJedi was typing. :)19:51
jeblairnew version of devstack gate that uses nodes from multiple providers is in production19:51
jeblairwe're much less likely to see node exhaustion19:51
jeblairthough at least one provider seems to be producing servers that run so slow we time out19:51
jeblairmore work is needed to document and collect stats on that19:51
jeblairthe process has, so far, identified a number of operation problems with the providers, and i've been providing feedback19:51
jeblairi opened a pull request for the ref-updated branch of the gerrit-trigger-plugin19:52
jeblairit still has outstanding issues that need to be addressed before it's likely to be merged19:52
jeblairbut at least the request is for the code we're using19:52
jeblaireventually we'll probably need to do some more work to get it merged19:52
jeblairand finally19:52
jeblairi'm planning on moving gerrit to a new (oneiric) server, but am waiting on a quota increase in the cloud servers account19:52
*** sandywalsh has joined #openstack-meeting19:52
mtayloris there any benefit in installing puppetmaster before you install the new gerrit server?19:53
*** ewindisch has joined #openstack-meeting19:53
LinuxJedittx: that would explain why your devstack timed out earlier ^19:53
jeblairLinuxJedi: thoughts on mtaylor's question?19:53
LinuxJedimtaylor, jeblair: it is not hard to switch between the two so I'm happy either way19:54
LinuxJedimtaylor: any news on devananda's gerrit tests?19:54
mtaylordevananda: ?19:54
devanandaLinuxJedi: i improved the GroupAdmin page load time by stopping the extra SET & SHOW commands, but would like it to reuse connections, too ...19:55
devanandait's opening 3k connections to mysql for that one page19:55
LinuxJedidevananda: that is an awesome start :)19:55
devanandai'm testing latest google branch of 2.3 now, then digging into the code to see if i can fix19:55
jeblairwe mostly need to be off of natty soon; i don't mind doing further upgrades as they're ready.19:56
LinuxJedidevananda: if you can make it use connection pooling like pretty much anything else written in Java I think it would be perfect ;)19:56
LinuxJedijeblair: ++ natty's puppet doesn't support a lot of what we are trying to do nowadays19:56
*** jdg has joined #openstack-meeting19:57
*** jdg is now known as jgriffith19:57
mtaylorwhen it becomes useful - I have a branch with our patches ported in to the 2.3 tree19:59
*** dolphm has joined #openstack-meeting19:59
LinuxJedimtaylor: I suspect it will be useful to devananda now ;)19:59
mtaylorBUT - I was thinking - perhaps we should import stock 2.3 into a branch in our gerrit, then propose each of our cherry-pick forward ports as a change?20:00
mtaylorI had to edit two of jeblair's patches in doing the rebase20:00
mtaylorwhich I _think_ I got right, but might not have20:01
*** Lance604 has quit IRC20:01
LinuxJedimtaylor: should we overrun the meeting due to the false start?  I believe PPB should be now20:01
jeblairwe should really upstream them.  :)20:01
mtayloranybody know - is the PPB meeting?20:01
devanandamtaylor: yea that may be useful soon. I'll poke you when I resolve the reconnect issue (would rather have a clean codebase to work on until then)20:01
mtaylorjeblair: well, yes20:01
mtaylordevananda: agree20:01
mtaylorjeblair: just trying to figure out how to model carrying local changes with tracking upstream in gerrit :)20:02
*** danwent has quit IRC20:02
jeblairi'd like to be able to continue to merge20:02
notmynameppb meeting today?20:04
mtaylorI've got my next thing ... I'm going to need to call this one a wrap from me20:04
LinuxJedimtaylor: cool, shall I endmeeting?20:04
*** dolphm_ has joined #openstack-meeting20:05
LinuxJedianyone have anything before I do?20:05
*** openstack changes topic to "Status and Progress (Meeting topic: keystone-meeting)"20:05
openstackMeeting ended Tue Apr  3 20:05:37 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:05
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-03-19.14.html20:05
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-03-19.14.txt20:05
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-03-19.14.log.html20:05
notmynameI don't think we've had a ppb meeting since before the last elections20:06
LinuxJedimaybe there should be an election for a ppb meeting :)20:06
notmynameprobably should be a mailing list discussion about that first20:07
*** jgriffith has quit IRC20:07
ttxthis time around, we didn't even have the email :)20:07
johnpuris jbryce around?20:08
*** dolphm has quit IRC20:08
*** danwent has joined #openstack-meeting20:11
devcamcaryea i think we need to meet at a minimum of at least once a month20:12
*** dendrobates is now known as dendro-afk20:12
devcamcareven if no formal agenda20:12
*** dolphm_ has quit IRC20:13
*** Yak-n-Yeti has quit IRC20:13
*** edconzel has joined #openstack-meeting20:14
notmynamea few things have been mentioned to talk about (I remember the emails, but not the topics)20:18
ttxjbryce mentioned starting the discussion on the Technical Committee draft20:18
ttxi.e. get comments on http://wiki.openstack.org/Governance/Foundation/TechnicalCommittee20:19
ttxbut I think that discussion should happen on the ML for everyone to see20:19
ttx(the Foundation ML)20:19
*** joshuamckenty has joined #openstack-meeting20:24
johnpurjosh mckenty; the man, the myth, the legend!20:25
*** bhall has joined #openstack-meeting20:27
*** bhall has quit IRC20:27
*** bhall has joined #openstack-meeting20:27
*** dprince has quit IRC20:29
*** bcwaldon has joined #openstack-meeting20:30
*** dolphm has joined #openstack-meeting20:30
*** nati has quit IRC20:45
*** lloydde_ has joined #openstack-meeting20:46
*** gyee has joined #openstack-meeting20:46
*** somik has joined #openstack-meeting20:47
*** lloydde__ has joined #openstack-meeting20:48
*** lloydde has quit IRC20:49
*** edconzel has left #openstack-meeting20:50
*** jgriffith has joined #openstack-meeting20:50
*** lloydde_ has quit IRC20:51
*** russellb has joined #openstack-meeting20:55
*** reed has joined #openstack-meeting20:57
*** reed has quit IRC20:57
*** reed has joined #openstack-meeting20:57
*** jmckenty has joined #openstack-meeting20:59
*** adam_g has joined #openstack-meeting21:00
ttxheckj, jaypipes, vishy, devcamcar: around ?21:01
devcamcarheckj may be in the air still in which case he asked me to fill in for him21:01
*** joesavak has joined #openstack-meeting21:02
ttxbcwaldon: are you filling in for Jay ?21:02
*** heckj has joined #openstack-meeting21:02
ttxhere he is21:02
bcwaldonttx: I can do whatever21:02
*** gabrielhurley has joined #openstack-meeting21:02
heckjjust through security...21:02
openstackMeeting started Tue Apr  3 21:02:32 2012 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.21:02
ttxToday's agenda: http://wiki.openstack.org/Meetings/ProjectMeeting21:02
ttxLast meeting before Essex release, so we'll be focusing on release candidate status for each project21:02
*** joshuamckenty has quit IRC21:02
jaypipesttx: yes21:03
ttx#info Plan is to have the last RC2s today, and spend the remaining time until release working on Release Notes and handling showstoppers.21:03
ttx#topic Keystone status21:03
*** openstack changes topic to "Keystone status"21:03
ttxheckj: o/21:03
ttxRC2 is still pending21:03
ttxWe need it out today, otherwise it won't see sufficient regression testing.21:03
*** jmckenty has quit IRC21:03
ttx#link https://launchpad.net/keystone/+milestone/essex-rc221:03
ttxIt's complete, waiting for 971592 to reach milestone-proposed21:04
ttxheckj: So that leaves us with a decision on the 3 bugs left on the "potential" list21:04
*** gyee has quit IRC21:04
ttx#link https://bugs.launchpad.net/keystone/+bugs?field.tag=essex-rc-potential21:04
heckjWe'll defer them given they haven't landed in master yet21:04
ttxheckj: Do we agree that none of them should block release ?21:04
heckjWe believe they're mostly nice to haves. The possible exception is 95929421:05
ttxheckj: We won't do an RC3 over them, right ?21:05
*** devcamcar_ has joined #openstack-meeting21:05
heckjhttps://bugs.launchpad.net/keystone/+bug/959294 is about not being able to delete users with the SQL backend - missed in earlier testing21:05
uvirtbotLaunchpad bug 959294 in keystone "Can't delete users" [High,In progress]21:05
heckjreview is up, but not through jenkins to get it included.21:06
*** gyee has joined #openstack-meeting21:06
heckjI'd like to have that in the release21:06
adam_gheckj: i think we can get that merged into master within the hour21:06
ttxheckj: is review approved ?21:06
zulcouldnt you beat jenkins into submission?21:06
ttxok, let's move it to the RC2 list then21:06
adam_gits definitely a blocker for anyone using a database that cares for FKs, IMHO21:06
ttxheckj: and let's drop the other two.21:07
*** devcamcar_ has quit IRC21:07
*** reed has quit IRC21:07
*** devcamcar_ has joined #openstack-meeting21:07
heckjadam_g - I'll be online for the next hour to help approve21:07
*** milner has quit IRC21:07
*** devcamcar_ has quit IRC21:08
ttxheckj: the last two could be included, in case we ahve to reroll an RC3 tomorrow because a kitten got killed by Keystone RC2 overnight21:08
ttxbut very unlikely21:08
heckjkeystone killing kittens? Bad business, that21:08
ttxI heard cloudstack does not kill kitten.21:09
ttxheckj: anything else ?21:09
joesavakthe get apache to do it?21:09
heckjnot from me21:09
ttxok, we are close :)21:09
ttxQuestions about Keystone ?21:09
ttx#topic Swift status21:10
*** openstack changes topic to "Swift status"21:10
ttxnotmyname: o/21:10
notmynameyay swift21:10
ttxStill planning to use 1.4.8 as Essex21:10
ttxnotmyname: Anything you wanted to mention ?21:11
notmynameindeed. we've landed some patches for the next release after essex, but 1.4.8 is still essex21:11
notmynamenothing in the past week has changed wrt swift and essex from our side21:11
ttxnotmyname: I saw good progress on the swift track content for the design summit21:12
notmynameyes, we've got about 30 minutes or so unscheduled21:12
ttxnotmyname: you might want to check the release notes contents21:12
notmynameI'm looking forward to good discussions21:12
ttx#link http://wiki.openstack.org/ReleaseNotes/Essex21:12
ttxto make sure they match reality21:12
notmynameah yes21:12
notmynamewhat's the deadline for that?21:12
ttxheckj: that's valid for you too ^21:13
*** de_ has joined #openstack-meeting21:13
ttxideally before Thursday, though we can make changes post-release to that document21:13
heckjttx: thank you21:13
ttxit needs to be correct by tomorrow EOB. Not necessarily complete, but correct and looking sane :)21:13
*** brian_parker has joined #openstack-meeting21:13
*** reed has joined #openstack-meeting21:14
ttxQuestions on Swift ?21:14
notmynameit looks mostly good for swift, but I'll check it more thoroughly later21:14
*** brian_parker has quit IRC21:14
ttx#topic Glance status21:15
*** openstack changes topic to "Glance status"21:15
ttxjaypipes: yo21:15
ttxRC2 is out, RC3 is baking at:21:15
ttx#link https://bugs.launchpad.net/glance/+milestone/essex-rc321:15
ttxjaypipes, bcwaldon: Looks ready to cut from my end21:15
bcwaldonttx: sounds like a plan21:15
ttxUnless someone has a last-minute blocker to suggest21:16
bcwaldonttx: not I21:16
ttxbcwaldon: will do immediately after the meeting21:16
bcwaldonttx: awesome, thank you21:16
ttxjaypipes, bcwaldon: you should use the remaining time polishing the release notes :)21:16
bcwaldonttx: as for folsom, I'm hard at work on python-glanceclient21:16
reed#info Glance RC2 is out, RC3 is baking at: https://bugs.launchpad.net/glance/+milestone/essex-rc321:17
bcwaldonttx: I'll look into that with Jay later today21:17
jaypipesk, thx ttx21:17
ttxjaypipes, bcwaldon: Anything else ?21:17
jaypipesttx: nope, not from me.21:17
heckjbcwaldon: ++!21:17
*** troytoman is now known as troytoman-away21:17
ttxQuestions on Glance ?21:17
bcwaldonheckj: :)21:17
reed#info <ttx> jaypipes, bcwaldon: you should use the remaining time polishing the release notes :)21:17
*** joesavak has quit IRC21:18
bcwaldonI'll follow up with someone to figure out where I would do that21:18
ttx#link http://wiki.openstack.org/ReleaseNotes/Essex21:18
*** lloydde__ has quit IRC21:18
ttx#topic Nova status21:18
*** openstack changes topic to "Nova status"21:18
heckjbcwaldon: http://wiki.openstack.org/ReleaseNotes/Essex21:18
ttxvishy: hey21:18
bcwaldonheckj: thank you, sire21:18
*** lloydde has joined #openstack-meeting21:19
ttxRC2 is out. 6 bugs on the essex-rc-potential list:21:19
ttx#link https://bugs.launchpad.net/nova/+bugs?field.tag=essex-rc-potential21:19
*** dwalleck has quit IRC21:19
ttxvishy: if we do a respin over some of those, we should complete it today21:19
vishyjust noticed that one is already merged bug got reset by hudson?21:19
uvirtbotLaunchpad bug 968066 in nova "Unable to create a snapshot if original image is not in Glance anymore" [Medium,In progress]21:20
vishyany idea why that would happen?21:20
bcwaldonnova looks up the original image to preserve disk/container formats21:20
bcwaldonso if it gets a 404, it blows up21:20
vishybcwaldon: I'm not wondering about the bug21:20
ttxmaybe someone filed a review pointing to that bug21:20
bcwaldonwell fine21:20
vishybcwaldon: i'm wondering why it went from fix-released back to in-progress21:20
reed#info RC2 is out. 6 bugs on the essex-rc-potential list:  https://bugs.launchpad.net/nova/+bugs?field.tag=essex-rc-potential21:21
vishyi'm going to set it back to fix committed then21:21
vishy* released21:21
vishyttx: we could back target it to rc-2 i guess21:21
ttxreferencing bug 66806621:21
uvirtbotLaunchpad bug 668066 in rapid "not reading XD-cards on Ubuntu vers. 0.3.3" [Undecided,Invalid] https://launchpad.net/bugs/66806621:21
vishyjust need review on https://review.openstack.org/#change,618921:22
vishyand i will push the patches into milestone proposed and recut21:23
ttxvishy: the two reviews I just mentioned are the reason why the bug was reopen by Jenkins21:23
*** lloydde has quit IRC21:23
*** lloydde has joined #openstack-meeting21:24
ttxif they should be ignored (and/or filed as another bug), maybe they should be abandoned to remove confusion21:24
vishyttx: ah looks like it is just because of the name of his branch?21:24
ttxwell, it claims to fix the bug too21:25
* ttx opens RC3 while you look into the fix21:25
vishyttx: ah i see that now21:26
vishyttx: so there were multiple patches and we only got the first one21:26
ttxmaybe. It's missing comments21:26
*** shwetaap has joined #openstack-meeting21:26
ttxbut if yes, we may want them in as well21:26
vishyok i will skip this one: https://review.openstack.org/#change,609421:27
vishybut 5950 seems fine21:27
*** dhellmann has quit IRC21:27
ttxmaybe abandon 6094 and ask to file a separate bug for clarity21:27
*** hggdh has quit IRC21:28
*** joshuamckenty has joined #openstack-meeting21:28
vishyalthough that one doesn't actually reference the bug in the message21:29
*** markvoelker has quit IRC21:29
ttxvishy: does that look complete: https://launchpad.net/nova/+milestone/essex-rc321:30
ttxmaybe I should add 96806621:30
ttxif you backport 595021:30
vishyyes add it21:30
uvirtbotLaunchpad bug 972583 in nova "network_get_all_by_uuids fails when requesting a network as admin" [Low,In progress]21:30
vishyjust propped the backport21:30
*** hggdh has joined #openstack-meeting21:32
ttxvishy: you want 972583 ?21:32
vishyi think target them all21:32
vishyi removed all the ones i don't want in21:32
ttxhttps://launchpad.net/nova/+milestone/essex-rc3 should be alright21:33
ttxvishy: so your mission, if you accept it, is to get all of these in milestone-proposed before the end of the day21:33
ttxso that I can cut Nova RC3 first thing tomorrow morning21:33
vishyttx: on it21:33
ttxvishy: Anything else ?21:33
ttxQuestions on Nova ?21:34
ttx#topic Horizon status21:34
*** openstack changes topic to "Horizon status"21:34
ttxdevcamcar: o/21:34
ttxRC2 is pending.21:34
ttx#link https://launchpad.net/horizon/+milestone/essex-rc221:35
devcamcarso we are down to one last issue and then rc2 drops21:35
ttxtwo bugs still missing21:35
*** novas0x2a|laptop has quit IRC21:35
devcamcarjohn is well underway on that one21:35
devcamcaroh not in milestone-proposed?21:35
ttxfrom milestone-proposed :)21:35
ttxwas the 971937 one backported yet ?21:35
gabrielhurleyno. just now merged to master21:36
devcamcarno that just landed in master a few moments ago21:36
ttxok, I'm on it21:36
* ttx is on fire21:36
devcamcarso i am feeling good about where we are at this point21:36
devcamcarwe will drop rc2 today and barring any unforeseeable  craziness this should be essex final21:36
heckjdevcamcar - look out, horizon will be killing kittens soon too...21:37
*** dolphm has quit IRC21:37
reed#info <devcamcar> so i am feeling good about where we are at this point, we will drop rc2 today and barring any unforeseeable  craziness this should be essex final21:37
ttxdevcamcar: you will have to backport the last one21:37
*** Yak-n-Yeti has joined #openstack-meeting21:37
ttxdevcamcar: since I'll probably be sleeping when it lands on master21:37
ttxhttps://launchpad.net/horizon/+milestone/essex-rc2 should look at the end of the day all FixReleased21:38
ttxand I'll pick it up tomorrow morning and publish21:38
ttxdevcamcar: Anything else ?21:39
ttxQuestions for Horizon ?21:39
*** jog0 has quit IRC21:39
*** jog0_ has joined #openstack-meeting21:39
ttx#topic Incubated projects and other Team reports21:39
*** openstack changes topic to "Incubated projects and other Team reports"21:39
annegentleI don't know if there's a section for Horizon in the release notes but it definitely needs attention there21:39
gabrielhurleyannegentle: agreed21:40
ttxannegentle: if there isn't, there should be21:40
annegentledevcamcar: I'll start the section but would like help with the messages21:40
ttxdoing release notes is a good exercise while waiting for eventual kittens to get killed21:40
gabrielhurleyunless devcamcar objects, I'll work on that21:41
lloyddewhat's with all the kitten refs today? ;-)21:41
devcamcarannegentle: that would be fantastic21:41
devcamcargabrielhurley: no objections21:41
ttxlloydde: regressions on release day -1 are called kitten killers21:41
* lloydde learnered21:41
ttxdanwent: yo21:41
danwentquantum essex rc2 went out today: https://launchpad.net/quantum/+milestone/essex-rc221:41
ttxQuantum had an RC2 published today!21:41
ttxdanwent: Unless I hear about you, I should use RC2 as the release on Thursday ?21:42
reed#info  quantum essex rc2 went out today: https://launchpad.net/quantum/+milestone/essex-rc221:42
danwentbattles are mostly now with docs, and with sorting threw issues with distro-specific packaging21:42
danwentttx: yes, sir21:42
danwentthrew->through… i'm tired :)21:42
ttxdanwent: anything else ?21:42
annegentledanwent: talking to jeblair about CI on the doc build jobs that'll get your docs from /incubation to /trunk after Essex goes out21:43
ttxstarting Friday I do 72 hours sleep21:43
ttxtroytoman: around ?21:43
danwentannegentle: thanks.  we'll definitely need a way to have a frozen version of essex docs available on the web, while drastically changing the docs as the code moves in Folsom21:43
ttxtroytoman, jkoelker: same for you guys, unless I hear otherwise, I will use Melange RC2 as the release21:44
annegentledanwent: ok.21:44
ttxannegentle: your turn :)21:44
ttxannegentle: apart from the release notes, how bad do we look from a doc perspective ?21:45
annegentlettx: plenty of missing content around config options, but tasked in doc bugs.21:45
annegentleI do like the forward movement on extension docs I'm seeing today21:45
ttxannegentle: so you continue work after release ?21:45
annegentleI just want to work the plan on config docs21:45
annegentlewe have to.21:45
*** GheRivero has quit IRC21:45
annegentleI've become accepting of this in the last week :)21:46
annegentledoc bugs are still coming in21:46
annegentlelast release I didn't stop working on the "prior" release for a while21:46
ttxannegentle: it's a bit of an artifact of releasing every 6 months21:46
reed#info documentation has plenty of missing content around config options, but tasked in doc bugs. Work will continue after release.21:47
annegentlettx: agreed, seems like it21:47
ttxannegentle: people don't really use non-releases, and devs don't read docs21:47
annegentledoc comments will open on docs.openstack.org/essex after Thursday, to encourage feedback loops21:47
ttxannegentle: so you get the bugs only when real people start using stuff, and it's too late to fix21:47
annegentlettx: 'zactly21:47
ttxannegentle: working on fixing that21:47
ttxannegentle: anything else ?21:47
annegentlereally, I feel we're in great shape because the release will be documentable, you know?21:48
*** ryanpetrello has quit IRC21:48
annegentle#info release is fully "documentable" meaning everything works and doc writers can get an environment that they write to21:48
annegentleany questions on docs?21:48
ttxAny other team lead with a status report ?21:48
ttx#topic Open discussion21:49
*** openstack changes topic to "Open discussion"21:49
ttx#info Most track leads started to review their track contents, so if you want to propose a session, you should do so ASAP21:49
ttx#link http://summit.openstack.org21:49
heckjttx: when will summit schedules be generally available for people to view?21:50
ttxheckj: when we (track leads) start scheduling21:50
* heckj tried to send some links, only to be told they weren't authorized for others to see21:50
ttxThe track layout should be official now21:51
reedttx, is there a chance to put the agenda of the summit together with http://www.openstack.org/conference/san-francisco-2012/sessions/ ?21:51
ttxreed: I guess so, you can certainly embed both ?21:51
ttxwork in progress is here: http://folsomdesignsummit2012.sched.org/21:52
reedttx, I can't, Todd is the master of the .org universe and I imagine he'll be busy with 100M other things21:52
*** shwetaap_ has joined #openstack-meeting21:52
*** nati has joined #openstack-meeting21:52
ttxreed: in the mean time, we can extend the oen on openstack.org with the track layout21:52
*** gyee has quit IRC21:53
ttxso that people know when, for example, the Swift sessions will be scheduled21:53
*** shwetaap has quit IRC21:53
*** shwetaap_ is now known as shwetaap21:53
ttxeven if they don't have the full detail of content21:53
reedI see ...21:53
ttxreed: will talk to you offline21:53
ttxAnything else, anyone ?21:53
reedthere is a question about java SDK21:54
reedbut probably that's mostly for PPB, right?21:54
ttxdepends on the question21:56
reedttx, it was on the mailing list...21:56
reedthe guy is asking for permission to package his java SDK as openstack.org21:56
ttxyeah, ppb question21:57
reednever mind though... we can talk about this on the list21:57
*** openstack changes topic to "Status and Progress (Meeting topic: keystone-meeting)"21:57
openstackMeeting ended Tue Apr  3 21:57:18 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-03-21.02.html21:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-03-21.02.txt21:57
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-03-21.02.log.html21:57
*** gyee has joined #openstack-meeting21:57
*** heckj has quit IRC21:59
*** dcramer_ has quit IRC22:00
*** salv-orlando has joined #openstack-meeting22:00
danwentok, hi folks22:01
openstackMeeting started Tue Apr  3 22:01:13 2012 UTC.  The chair is danwent. Information about MeetBot at http://wiki.debian.org/MeetBot.22:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.22:01
danwent#info  Agenda: http://wiki.openstack.org/Network/Meetings22:01
danwentwill hopefully be pretty quick, we have a lot to do before thursday :)22:02
danwent#info essex rc2 is out: https://bugs.launchpad.net/quantum/+milestone/essex-rc222:02
danwentthere are no currently known issues with RC2, and barring any major issues, it will be the final release.22:02
danwentphew… finally, someone said something.  I was beginning to wonder if I was talking to no one :)22:03
*** nati has quit IRC22:03
danwentOk, I just sent an email to the ML about some outstanding docs issues22:03
carlpI'm always here for you, Dan :)22:03
*** reed has quit IRC22:04
danwentok, remaining docs tasks are:22:04
*** ayoung has quit IRC22:04
danwent1) create updated version of the 1.1 API spec22:04
*** SumitNaiksatam has joined #openstack-meeting22:04
danwent2) review admin guide for any changes since E-4 (should be fairly minor)22:04
danwent3) make sure use of Quantum with distro packaging is documented (as this is how most people will consume quantum)22:05
*** gabrielhurley has left #openstack-meeting22:05
danwentIf you have cycles, please let me know so you can pitch in here.22:05
danwentThe other main area to help out is distro testing.22:05
danwentSince all packaging for quantum is new, there are some rough edges.22:05
danwentFedora packaging has gotten a lot of love, so I suspect that is in pretty good shape, but we need more testing on it.22:06
cdub*nod*  specifically, ucs plugin is basically untested22:06
cduband for ovs, we don't have real tunnelling support, so no bother testing that22:07
danwentcdub:  i'm upgrading my F16 kernel so I can hopefully test OVS plugin later today22:07
*** russellb has left #openstack-meeting22:07
cdubdanwent: great, we've done basic sanity testing on that and the bridge plugin.  not cisco, nvp or ryu22:07
danwentbut overall there has been a lot of work put into integrating quantum with fedora, much appreciated22:08
*** debo-os has joined #openstack-meeting22:08
cdubyeah, it's coming together pretty well (bug reports happily accepted of course ;)22:08
danwentOn Ubuntu, last night we got to the point where the quantum client could talk to the quantum server using the fakeplugin22:08
danwentbut there seem to be issues with the agents not being packaged as binaries.22:09
danwentthe underlying python classes are there, but there are no binaries, and no init scripts.22:09
cdubhmm, perhaps fallout from the setup.py changes22:09
danwentI'm working with Dave from canonical on this.22:09
danwentbut the summary is, both platforms could use a lot more eyeballs, since a lot of this packaging is brand new22:10
danwentremember that if people can't use quantum with the main distros, people will conclude that the underlying software doesn't work, so testing distro integration is important.22:10
danwentany other distros that we should be looking at testing on?  I believe there are debian packages, but I don't have any details on that.22:10
*** aabes has joined #openstack-meeting22:10
bhallshould we be testing ubuntu packaging with 11.10 or 12.04?22:11
debo-osI can help with ubuntu22:11
danwentsee the email I sent to the ML with the basic descriptions of the packages22:11
danwentI believe just doing apt-get install quantum-server will install the client and all other dependencies.22:12
danwentI'll shift my discussion of remaining packaging issues onlist, so we can avoid any duplicate troubleshooting/error reporting22:12
danwentanything else on distro testing?22:12
danwentrealistically, we have ONE MORE DAY before the release, so we really need to focus efforts22:13
danwent#info devstack + quantum is still broken due to config change, please review: https://review.openstack.org/#change,617822:13
danwentI don't really like this patch, but its a simple work around that doesn't require reverting the old patch.22:13
danwentif someone else from the quantum team could review it, I'd appreciate it.22:14
bhallI took a look at it earler.. I'll +1 it22:14
danwentthen I can hopefully corner some devstack people to approvide it.22:14
danwentman, I REALLY need to sleep more :)22:14
cdubdon't misunderestimate sleep deprecation22:15
danwentdebo-os: update on the devstack excercise script?  plan is that devstack folks will merge after essex branches?22:15
danwentcdub: i unfortunately have deprecated sleep22:15
debo-oswaiting for the merge ...22:15
bhalldanwent: you just need to start drinking coffee.. :)22:15
danwentbhall: i'll never give in22:16
cdubdanwent: in favor of sleepv2 i hope ;)22:16
bhallfirst one is free buddy22:16
carlpnever! non coffee drinkers untie!22:16
danwentuntie?  or unite?22:16
salv-orlandocarlp needs coffee as well22:16
danwentok, last topic, summit22:16
danwent#info hopefully everyone has seen the etherpad by now: http://etherpad.openstack.org/quantum-folsom22:16
*** novas0x2a|laptop has joined #openstack-meeting22:16
*** irctc989 has joined #openstack-meeting22:17
danwentI sent an email to the ML yesterday proposing some definition to help frame the many discussion topics related to "L3".22:17
*** irctc989 has quit IRC22:17
danwentso hopefully "L3" can be banned as a phrase in our discussion in favor of more concrete terms.22:17
danwentplease provide feedback via email or etherpad.22:17
danwentI'm starting to send emails to people signed up as drivers for the key topics, asking them to register summit sessions.22:18
carlpwill do, I'm hoping to have a proposal tomorrow afternoon to the list22:18
danwentI'll probably send an email out tomorrow about critical areas where we have yet been able to trick (er, i mean convince) someone into running the sssion.22:18
danwentcarlp: new topic, or just opinions on an existing topic?22:19
cdubdanwent: i expect we'll have ours in w/in the next day22:19
carlpopinions on the existing topic22:19
danwentok, any new topics, we definitely want to get those proposed ASAP.22:19
danwentopinions on existing topics can continue to flow in between now and summit22:19
cdubnew meaning not currently on etherpad?22:20
danwentbut remember, please don't let summit stuff distract you from the release work…. there will be plent of time to do stuff after the release22:20
danwentcdub: yes22:20
*** littleidea has quit IRC22:20
cdubdanwent: ok, thanks22:20
*** nati has joined #openstack-meeting22:21
*** mikal has quit IRC22:21
danwent#topic open discussion22:21
*** openstack changes topic to "open discussion"22:21
danwentplease think about how you can pitch in and help with testing + docs.22:21
carlpI'll see what I can do, I'm somwhat swamped with work ATM22:21
carlpI hate it when all the deadlines start converging22:22
danwentcarlp: yup :)22:22
aabesquick q: there are some topics on the list for sessions that almost cover it, but nothing specific for nova network parity.22:22
*** littleidea has joined #openstack-meeting22:22
danwentaabes: there won't be a specific session on it, but many of the sessions combine to approach that goal.  is there a specific topic you see as missing?22:23
*** mikal has joined #openstack-meeting22:23
danwentok, well aabes, feel free to sync with me offline.   I'll call the meeting to a close so everyone else can take off :)22:24
*** openstack changes topic to "Status and Progress (Meeting topic: keystone-meeting)"22:24
openstackMeeting ended Tue Apr  3 22:24:27 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:24
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-03-22.01.html22:24
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-03-22.01.txt22:24
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-03-22.01.log.html22:24
aabesdanwent: looking at the list again... seems that everything I can think about is there. Though it might be good to get nova folks in the room to make sure we're not missing somehting22:24
danwentkeep testing!  talk to you all later22:24
cdubperhaps a ptl state of the union that identifies the final gaps?22:24
cdubnoting that they will be discussed throught various sessions22:24
danwentaabes:  definitely.  in fact, we've combined the nova-network track and the quantum track, so tr3buchet, head of the nova-network subteam should be there for most/all discussions.22:25
danwentcdub:  i think that is probably a good idea.22:25
*** littleidea_ has joined #openstack-meeting22:25
danwentI think last time we had an informal summary + gap analysis meeting at the end.  making that an explicit session would probably be a good idea.22:26
aabesdanwent: there are some "features" in nova network, like multi-host, which probably don't translate into a feature in quantum... but the rational behind building them might apply in some other form22:26
aabesbut to cdub:'s point.. an agreement on state of the union would probably shake those out.22:27
danwentaabes:  yes, actually in quantum multi-host will be a property of a plugin (i.e., certain capabilities are implemented in a distributed manner).  I think it might make sense to have a session that talks about what functionality must be supported by an open source plugin by the end of Folsom.22:27
*** littleidea has quit IRC22:27
danwentok, added a not on that to the etherpad22:29
*** salv-orlando has quit IRC22:29
danwentthanks for the input on this22:30
* cdub hands danwent a silent 'e'22:30
danwenti'm too tired to get the joke22:30
cdub"added a not" ...22:31
danwentah, not -> note22:31
*** littleidea_ has quit IRC22:31
cdubdanwent: is the blurb bob put on etherpad sufficient for now?22:31
danwentcdub: looks like my kernel is upgraded.  I assume a reboot will do it?22:31
cdubyep, it should22:31
debo-osI had a small point22:32
debo-oswould it make sense to take the nova network api22:32
danwentcdub: might be helpful if it flushed it out a bit more via email.22:32
*** johnpur has quit IRC22:32
debo-osand group it into collectivity, l2, l3, services22:32
cdubdanwent: it's pretty cryptic, i agree22:32
danwentdebo-os: no using the term "l3" :)22:32
debo-osooops sorry ....22:33
danwentdebo-os: what's the goal you're shooting for?22:33
debo-osquantum will consume the apis but right now there are direct calls made to DBs etc which should be avoided ... if you have a more detailed structured grouped API, it might help refactor22:34
danwentsorry, don't follow22:35
cdubconsume or terminate?22:35
debo-osideally all networking related info should be obtained from the quantum via the nova network22:35
cdubi.e. currently it's like nova-compute -> nova-network -> quantum22:36
cdubwhich is kinda ugly22:36
*** mrmartin has quit IRC22:36
debo-osso nova network API is what I am referring to22:36
danwentdebo-os: I wrote a bit about this on the ML, and we'll talk more at the summit, but nova-network is likely going away when quantum is in use.22:36
debo-ossay we organize the API into L2, L3, Services22:36
cdubesp since it started as services -> scheduler...bouncing all over the place22:36
debo-osok ....22:37
debo-osthen it makes sense22:37
cdubworse when considering qunatum -> plugin -> agent22:37
danwentthinks will get a lot simpler in Folsom.  network config will happen directly against the quantum API.22:37
danwentnova <-> quantum communication should happen only when VMs are getting allocated and plugged into networks.22:37
debo-osI probably missed that thread ... . today the nova network api looks like one monolithic API22:37
debo-ostoday iptables is used directly22:37
debo-osby libvirt22:38
debo-osthats a network functionality, right?22:38
danwentdebo-os: yeah, its kind of a mess.22:38
debo-osif you exposed iptables via a quantum/novanetwork api it would be cleaner22:38
debo-oshence my comment22:38
debo-ossorry I didnt read that thread22:38
danwentbut firewalling (security groups, provider filters), floating ips, networking creation/deletion, all of that will move to being driving via quantum api22:38
danwentyes, definitely the direction we're headed.22:38
danwentindeed.  networking in openstack is a very confusing place right now, we need to make it simpler :)22:39
*** rafaduran has quit IRC22:39
debo-osmaybe then we should have a Q-API discussion for all the networking functionality needed, right?22:40
*** shwetaap has quit IRC22:40
debo-osby nova ...22:41
danwentdebo-os: my thinking is that part of discussion an item (e.g., "L3 Forwarding") includes discussing the API to control it (in fact, in many cases that will be the primary discussion point, since different plugins are free to implement things however they want.22:41
danwentwith "by nova", do you mean to replicate existing nova networking?22:42
debo-osyes needed by nova meant .... look at the current calls made to any network related entities22:42
debo-ossee if there is an api there ... if not we need one22:43
*** littleidea has joined #openstack-meeting22:43
debo-ose.g. direct reference to iptables22:43
danwentdebo-os: yeah, I think that will be a key driver in several of the sessions, particularly when we discuss L3 forwarding and NAT.  The goal is that we should never expose an API that is as implementation specific as iptables.   In fact, we've already refactored nova-network to use a more general python API internally within nova-network.22:44
danwentbtw, let me know if you need help getting ubuntu testing setup.22:44
debo-osyes .. would like to know what has been tested so far22:45
debo-osso that I dont replicate22:45
danwentwe definitely need more cycles there.  Dave M (see email to ML) and Chuck Short have been very helpful in responding to issues.22:45
debo-ose.g. singlehost/multihost22:45
*** ryanpetrello has joined #openstack-meeting22:45
danwentjust try to get any plugin up and running with an agent :)22:45
danwentsingle host to start22:45
debo-osok :)22:46
danwentbaby steps :)22:46
danwentk, gotta run.  will talk to you later.22:47
*** ryanpetr_ has joined #openstack-meeting22:47
danwentif you run into issues, send them to the ML, and I will do the same22:47
danwentso we don't trip over the same thing22:47
*** littleidea has quit IRC22:47
*** aabes has quit IRC22:49
*** ryanpetrello has quit IRC22:50
*** dendro-afk is now known as dendrobates22:50
*** Yak-n-Yeti has quit IRC22:51
*** SumitNaiksatam has quit IRC22:54
*** jog0 has joined #openstack-meeting22:54
*** jog0_ has quit IRC22:54
*** jog0 has joined #openstack-meeting22:55
*** dtroyer is now known as dtroyer_zzz23:01
*** novas0x2a|laptop has quit IRC23:03
*** dendrobates is now known as dendro-afk23:10
*** littleidea has joined #openstack-meeting23:11
*** littleidea_ has joined #openstack-meeting23:12
*** lloydde has quit IRC23:12
*** littleidea_ has quit IRC23:14
*** novas0x2a|laptop has joined #openstack-meeting23:15
*** dcramer_ has joined #openstack-meeting23:15
*** littleidea has quit IRC23:16
*** dendro-afk is now known as dendrobates23:19
*** adjohn has joined #openstack-meeting23:21
*** jgriffith has quit IRC23:23
*** sleepsonthefloor is now known as sleepsonzzz23:25
*** dhellmann has joined #openstack-meeting23:28
*** lloydde has joined #openstack-meeting23:34
*** debo-os has quit IRC23:46
*** bhall has quit IRC23:46
*** joshuamckenty has quit IRC23:47
*** Yak-n-Yeti has joined #openstack-meeting23:48
*** jakedahn is now known as jakedahn_zz23:49
*** shwetaap has joined #openstack-meeting23:49
*** ewindisch has quit IRC23:51
*** shwetaap has quit IRC23:54
*** shwetaap has joined #openstack-meeting23:55
*** lloydde has quit IRC23:56
*** kindaopsdevy has joined #openstack-meeting23:58
*** mnewby has quit IRC23:59
*** kindaopsdevy has left #openstack-meeting23:59

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