Tuesday, 2012-02-14

*** nati2 has quit IRC00:01
*** novas0x2a|laptop has quit IRC00:01
*** mestery has joined #openstack-meeting00:08
*** novas0x2a|laptop has joined #openstack-meeting00:10
*** sleepsonthefloo has quit IRC00:25
*** zns has quit IRC00:33
*** zns has joined #openstack-meeting00:34
*** sandywalsh has quit IRC00:35
*** dendrobates is now known as dendro-afk00:48
*** ravi has quit IRC00:49
*** sandywalsh has joined #openstack-meeting00:50
*** zns has joined #openstack-meeting01:04
*** dolphm has joined #openstack-meeting01:10
*** sleepsonthefloo has joined #openstack-meeting01:10
*** AlanClark has quit IRC01:17
*** danwent has quit IRC01:28
*** danwent has joined #openstack-meeting01:30
*** ravi has joined #openstack-meeting01:34
*** oubiwann has quit IRC01:38
*** ayoung has quit IRC01:45
*** ravi_ has joined #openstack-meeting01:56
*** ravi has quit IRC01:57
*** ravi_ is now known as ravi01:57
*** ravi has quit IRC02:00
*** ravi has joined #openstack-meeting02:04
*** mestery has quit IRC02:04
*** jakedahn has quit IRC02:07
*** danwent has quit IRC02:09
*** dolphm has quit IRC02:17
*** novas0x2a|laptop has quit IRC02:17
*** deshantm has joined #openstack-meeting02:33
*** jog0 has left #openstack-meeting02:35
*** zns has quit IRC02:44
*** jakedahn has joined #openstack-meeting02:47
*** ravi has quit IRC02:52
*** ravi has joined #openstack-meeting02:52
*** reed has quit IRC02:55
*** jog0 has joined #openstack-meeting02:58
*** jog0 has left #openstack-meeting02:59
*** jdurgin has quit IRC03:03
*** dubsquared has quit IRC03:03
*** nati2 has joined #openstack-meeting03:06
*** dwcramer has quit IRC03:28
*** danwent has joined #openstack-meeting03:50
*** dolphm has joined #openstack-meeting03:54
*** danwent has quit IRC04:24
*** LinuxJedi has joined #openstack-meeting05:15
*** uvirtbot has quit IRC05:19
*** journeeman has quit IRC05:20
*** uvirtbot has joined #openstack-meeting05:26
*** VinayP has joined #openstack-meeting05:35
*** VinayP is now known as vinayp05:36
*** littleidea has joined #openstack-meeting05:38
*** dolphm has quit IRC05:44
*** jakedahn has quit IRC05:46
*** dolphm has joined #openstack-meeting05:49
*** mestery has joined #openstack-meeting05:56
*** mestery has joined #openstack-meeting05:57
*** zns has joined #openstack-meeting05:58
*** vishy has quit IRC06:02
*** xtoddx has quit IRC06:02
*** comstud has quit IRC06:02
*** sleepsonthefloor has quit IRC06:03
*** vishy has joined #openstack-meeting06:03
*** dolphm has quit IRC06:03
*** xtoddx has joined #openstack-meeting06:04
*** comstud has joined #openstack-meeting06:04
*** sleepsonthefloor has joined #openstack-meeting06:04
*** vishy has quit IRC06:11
*** devcamcar has quit IRC06:11
*** xtoddx has quit IRC06:11
*** sleepsonthefloor has quit IRC06:11
*** devcamcar has joined #openstack-meeting06:12
*** comstud has quit IRC06:12
*** comstud has joined #openstack-meeting06:13
*** sleepsonthefloor has joined #openstack-meeting06:13
*** vishy has joined #openstack-meeting06:13
*** xtoddx has joined #openstack-meeting06:14
*** deshantm has quit IRC06:17
*** comstud has quit IRC06:20
*** devcamcar has quit IRC06:20
*** sleepsonthefloor has quit IRC06:20
*** vishy has quit IRC06:21
*** comstud has joined #openstack-meeting06:21
*** vishy has joined #openstack-meeting06:21
*** xtoddx has quit IRC06:21
*** xtoddx has joined #openstack-meeting06:22
*** devcamcar has joined #openstack-meeting06:22
*** sleepsonthefloor has joined #openstack-meeting06:23
*** mestery has quit IRC06:26
*** vishy has quit IRC06:30
*** vishy has joined #openstack-meeting06:31
*** xtoddx has quit IRC06:32
*** xtoddx has joined #openstack-meeting06:32
*** danwent has joined #openstack-meeting06:43
*** xtoddx has quit IRC07:00
*** devcamcar has quit IRC07:00
*** vishy has quit IRC07:00
*** vishy has joined #openstack-meeting07:00
*** xtoddx has joined #openstack-meeting07:01
*** devcamcar has joined #openstack-meeting07:01
*** vishy has quit IRC07:08
*** sleepsonthefloor has quit IRC07:08
*** xtoddx has quit IRC07:09
*** devcamcar has quit IRC07:09
*** devcamcar has joined #openstack-meeting07:10
*** sleepsonthefloor has joined #openstack-meeting07:10
*** vishy has joined #openstack-meeting07:11
*** xtoddx has joined #openstack-meeting07:11
*** devcamcar has quit IRC07:17
*** sleepsonthefloor has quit IRC07:17
*** vishy has quit IRC07:18
*** xtoddx has quit IRC07:19
*** devcamcar has joined #openstack-meeting07:19
*** sleepsonthefloor has joined #openstack-meeting07:19
*** vishy has joined #openstack-meeting07:20
*** zigo has joined #openstack-meeting07:20
*** xtoddx has joined #openstack-meeting07:20
*** zns has quit IRC07:21
*** zns has joined #openstack-meeting07:28
*** devcamcar has quit IRC07:36
*** sleepsonthefloor has quit IRC07:37
*** xtoddx has quit IRC07:37
*** zns has quit IRC07:38
*** sleepsonthefloor has joined #openstack-meeting07:38
*** xtoddx has joined #openstack-meeting07:38
*** devcamcar has joined #openstack-meeting07:39
*** nati2 has quit IRC07:50
*** vishy has quit IRC07:52
*** sleepsonthefloor has quit IRC07:52
*** xtoddx has quit IRC07:53
*** vishy has joined #openstack-meeting07:54
*** devcamcar has quit IRC07:54
*** xtoddx has joined #openstack-meeting07:54
*** devcamcar has joined #openstack-meeting07:55
*** sleepsonthefloor has joined #openstack-meeting07:55
*** littleidea has quit IRC08:06
*** shang has quit IRC08:07
*** ravi has quit IRC08:08
*** sandywalsh has quit IRC08:11
*** zigo-_- has joined #openstack-meeting08:13
*** zigo has quit IRC08:13
*** shang has joined #openstack-meeting08:35
*** sandywalsh has joined #openstack-meeting09:02
*** shang has quit IRC09:30
*** shang has joined #openstack-meeting09:35
*** shang_ has joined #openstack-meeting09:46
*** zigo-_- has quit IRC09:58
*** zigo has joined #openstack-meeting09:59
*** derekh has joined #openstack-meeting10:19
*** danwent has quit IRC10:24
*** darraghb has joined #openstack-meeting10:32
*** zigo has quit IRC10:42
*** zigo has joined #openstack-meeting10:45
*** derekh_ has joined #openstack-meeting10:46
*** jeblair has quit IRC10:56
*** s1rp_ has quit IRC10:56
*** jeblair has joined #openstack-meeting10:56
*** s1rp has joined #openstack-meeting10:57
*** Gordonz_ has quit IRC11:26
*** dayou has quit IRC11:26
*** dovetail1an has quit IRC11:26
*** Kiall has quit IRC11:26
*** tightwork has quit IRC11:26
*** sleepsonthefloor has quit IRC11:26
*** sleepsonthefloo has quit IRC11:26
*** nyov has quit IRC11:26
*** jeremyb has quit IRC11:26
*** mancdaz has quit IRC11:26
*** shang has quit IRC11:26
*** westmaas has quit IRC11:26
*** _cerberus_ has quit IRC11:26
*** soren has quit IRC11:26
*** martines has quit IRC11:26
*** zigo has quit IRC11:26
*** shang_ has quit IRC11:26
*** xtoddx has quit IRC11:26
*** nikhil_ has quit IRC11:26
*** dendro-afk has quit IRC11:26
*** Daviey has quit IRC11:26
*** derekh_ has quit IRC11:26
*** tr3buchet has quit IRC11:26
*** mjfork has quit IRC11:26
*** devcamcar has quit IRC11:26
*** mikal has quit IRC11:26
*** phantomcircuit has quit IRC11:26
*** comstud has quit IRC11:26
*** uvirtbot has quit IRC11:26
*** yehudasa has quit IRC11:26
*** ameade has quit IRC11:26
*** jamespage has quit IRC11:26
*** bpg has quit IRC11:26
*** pknouff has quit IRC11:26
*** LinuxJedi has quit IRC11:26
*** ghe_ has quit IRC11:26
*** jkoelker has quit IRC11:26
*** jeremydei has quit IRC11:26
*** kpepple_ has quit IRC11:26
*** mtaylor has quit IRC11:26
*** dabo has quit IRC11:26
*** ke4qqq has quit IRC11:26
*** glenc has quit IRC11:26
*** carlp has quit IRC11:26
*** termie has quit IRC11:26
*** derekh_ has joined #openstack-meeting11:32
*** zigo has joined #openstack-meeting11:32
*** shang_ has joined #openstack-meeting11:32
*** shang has joined #openstack-meeting11:32
*** sleepsonthefloor has joined #openstack-meeting11:32
*** devcamcar has joined #openstack-meeting11:32
*** xtoddx has joined #openstack-meeting11:32
*** comstud has joined #openstack-meeting11:32
*** uvirtbot has joined #openstack-meeting11:32
*** LinuxJedi has joined #openstack-meeting11:32
*** sleepsonthefloo has joined #openstack-meeting11:32
*** _cerberus_ has joined #openstack-meeting11:32
*** Gordonz_ has joined #openstack-meeting11:32
*** mjfork has joined #openstack-meeting11:32
*** westmaas has joined #openstack-meeting11:32
*** nikhil_ has joined #openstack-meeting11:32
*** dayou has joined #openstack-meeting11:32
*** tightwork has joined #openstack-meeting11:32
*** Kiall has joined #openstack-meeting11:32
*** dovetail1an has joined #openstack-meeting11:32
*** ghe_ has joined #openstack-meeting11:32
*** mikal has joined #openstack-meeting11:32
*** jeremyb has joined #openstack-meeting11:32
*** mancdaz has joined #openstack-meeting11:32
*** nyov has joined #openstack-meeting11:32
*** dendro-afk has joined #openstack-meeting11:32
*** jkoelker has joined #openstack-meeting11:32
*** phantomcircuit has joined #openstack-meeting11:32
*** jeremydei has joined #openstack-meeting11:32
*** Daviey has joined #openstack-meeting11:32
*** soren has joined #openstack-meeting11:32
*** martines has joined #openstack-meeting11:32
*** ameade has joined #openstack-meeting11:32
*** kpepple_ has joined #openstack-meeting11:32
*** tr3buchet has joined #openstack-meeting11:32
*** yehudasa has joined #openstack-meeting11:32
*** mtaylor has joined #openstack-meeting11:32
*** jamespage has joined #openstack-meeting11:32
*** bpg has joined #openstack-meeting11:32
*** dabo has joined #openstack-meeting11:32
*** ke4qqq has joined #openstack-meeting11:32
*** glenc has joined #openstack-meeting11:32
*** carlp has joined #openstack-meeting11:32
*** pknouff has joined #openstack-meeting11:32
*** termie has joined #openstack-meeting11:32
*** ghe_ is now known as GheRivero11:40
*** vinayp has quit IRC12:01
*** uvirtbot has quit IRC12:04
*** uvirtbot has joined #openstack-meeting12:06
*** vinayp has joined #openstack-meeting12:14
*** zigo has quit IRC12:19
*** zigo has joined #openstack-meeting12:19
*** adiantum has joined #openstack-meeting12:46
*** markvoelker has joined #openstack-meeting12:48
*** zigo has quit IRC12:54
*** zigo has joined #openstack-meeting12:55
*** nati2 has joined #openstack-meeting12:57
*** dprince has joined #openstack-meeting12:59
*** nati2_ has joined #openstack-meeting13:07
*** nati2 has quit IRC13:08
*** sandywalsh has quit IRC13:10
*** zigo has quit IRC13:18
*** zigo has joined #openstack-meeting13:20
*** sandywalsh has joined #openstack-meeting13:23
*** zigo has quit IRC13:35
*** zigo has joined #openstack-meeting13:36
*** zigo has quit IRC13:36
*** deshantm has joined #openstack-meeting13:44
*** hggdh has quit IRC14:03
*** nati2_ has quit IRC14:05
*** nati2 has joined #openstack-meeting14:06
*** hggdh has joined #openstack-meeting14:07
*** derekh has quit IRC14:10
*** mattray has joined #openstack-meeting14:19
*** uvirtbot has quit IRC14:24
*** vinayp has quit IRC14:29
*** uvirtbot has joined #openstack-meeting14:31
*** vinayp has joined #openstack-meeting14:39
*** littleidea has joined #openstack-meeting14:44
*** DuncanT has joined #openstack-meeting14:49
*** dwcramer has joined #openstack-meeting14:50
*** AlanClark has joined #openstack-meeting14:54
*** dendro-afk is now known as dendrobates14:58
*** ayoung has joined #openstack-meeting15:12
*** dolphm has joined #openstack-meeting15:18
*** GheRivero_ has joined #openstack-meeting15:20
*** jaypipes has joined #openstack-meeting15:21
*** dolphm has quit IRC15:22
*** dolphm has joined #openstack-meeting15:32
*** ttx has quit IRC15:43
*** yamahata has quit IRC15:44
*** gregburek has quit IRC15:44
*** mjfork has quit IRC15:44
*** gregburek has joined #openstack-meeting15:45
*** Adri2000 has quit IRC15:45
*** ttx has joined #openstack-meeting15:45
*** ttx has joined #openstack-meeting15:45
*** Adri2000 has joined #openstack-meeting15:45
*** dendrobates is now known as dendro-afk15:45
*** yamahata has joined #openstack-meeting15:45
*** littleidea has quit IRC15:49
*** mestery has joined #openstack-meeting15:50
*** zigo has joined #openstack-meeting15:54
*** nati2 has quit IRC15:55
*** nati2 has joined #openstack-meeting15:56
*** littleidea has joined #openstack-meeting16:02
*** danwent has joined #openstack-meeting16:05
*** nati2_ has joined #openstack-meeting16:08
*** oubiwann has joined #openstack-meeting16:09
*** dolphm has quit IRC16:09
*** nati2 has quit IRC16:10
*** joesavak has joined #openstack-meeting16:11
*** littleidea has quit IRC16:19
*** Yak-n-Yeti has joined #openstack-meeting16:21
*** nati2_ has quit IRC16:23
*** LinuxJedi has quit IRC16:30
*** mestery has quit IRC16:31
*** dolphm has joined #openstack-meeting16:32
*** mestery has joined #openstack-meeting16:32
*** martine has joined #openstack-meeting16:35
*** ravi has joined #openstack-meeting16:36
*** zigo has quit IRC16:44
*** johnpur has joined #openstack-meeting16:44
*** LinuxJedi_tablet has joined #openstack-meeting16:45
*** zigo has joined #openstack-meeting16:46
*** markvoelker has quit IRC16:54
*** dolphm has quit IRC16:56
*** dolphm_ has joined #openstack-meeting17:01
*** nati2 has joined #openstack-meeting17:01
*** AndChat| has joined #openstack-meeting17:04
*** LinuxJedi_tablet has quit IRC17:04
*** AndChat| is now known as LinuxJedi_tablet17:05
*** nati2_ has joined #openstack-meeting17:06
*** vladimir3p has joined #openstack-meeting17:07
*** nati2 has quit IRC17:09
*** apontes has joined #openstack-meeting17:14
*** mattray has quit IRC17:18
*** darraghb has quit IRC17:24
*** LinuxJedi_tablet has quit IRC17:25
*** deshantm has quit IRC17:32
*** joesavak has quit IRC17:37
*** joesavak has joined #openstack-meeting17:39
*** zigo has quit IRC17:39
*** apontes has quit IRC17:40
*** hggdh has quit IRC17:41
*** s1rp has quit IRC17:41
*** troytoman-away has quit IRC17:41
*** medberry has quit IRC17:42
*** s1rp has joined #openstack-meeting17:44
*** jeblair has quit IRC17:47
*** blamar has quit IRC17:47
*** gregburek_ has joined #openstack-meeting17:49
*** joesavak has quit IRC17:50
*** ogelbukh has quit IRC17:50
*** ogelbukh has joined #openstack-meeting17:55
*** danwent has quit IRC17:55
*** gregburek has quit IRC17:55
*** uvirtbot has quit IRC17:55
*** dprince has quit IRC17:55
*** bengrue has quit IRC17:55
*** pvo has quit IRC17:55
*** dwcramer has quit IRC17:55
*** Gordonz_ has quit IRC17:56
*** dayou has quit IRC17:56
*** dovetail1an has quit IRC17:56
*** Kiall has quit IRC17:56
*** tightwork has quit IRC17:56
*** AlanClark has quit IRC17:56
*** sleepsonthefloor has quit IRC17:56
*** sleepsonthefloo has quit IRC17:56
*** nyov has quit IRC17:56
*** jeremyb has quit IRC17:56
*** mancdaz has quit IRC17:56
*** ttx has quit IRC17:56
*** shang has quit IRC17:56
*** westmaas has quit IRC17:56
*** vladimir3p has quit IRC17:56
*** GheRivero_ has quit IRC17:56
*** ayoung has quit IRC17:56
*** _cerberus_ has quit IRC17:56
*** soren has quit IRC17:56
*** martines has quit IRC17:56
*** mestery has quit IRC17:56
*** adiantum has quit IRC17:56
*** shang_ has quit IRC17:56
*** xtoddx has quit IRC17:56
*** nikhil_ has quit IRC17:56
*** dendro-afk has quit IRC17:56
*** Daviey has quit IRC17:56
*** Yak-n-Yeti has quit IRC17:56
*** Adri2000 has quit IRC17:56
*** vinayp has quit IRC17:56
*** derekh_ has quit IRC17:56
*** tr3buchet has quit IRC17:56
*** sandywalsh has quit IRC17:56
*** devcamcar has quit IRC17:56
*** mikal has quit IRC17:56
*** phantomcircuit has quit IRC17:56
*** yamahata has quit IRC17:56
*** openstack has joined #openstack-meeting17:58
*** ChanServ sets mode: +o openstack17:58
ayoungI'm Here for the Keystone meeting17:58
*** adjohn has joined #openstack-meeting18:00
jsavakhi ayoung!18:00
jsavak#startmeeting keystone-meeting18:00
openstackMeeting started Tue Feb 14 18:00:19 2012 UTC.  The chair is jsavak. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.18:00
*** openstack changes topic to " (Meeting topic: keystone-meeting)"18:00
jsavakanyone else here for keystone meeting?18:00
jsavak#link agenda and meeting notes: http://wiki.openstack.org/Meetings/KeystoneMeeting18:00
jsavak#link essex 4 bp and bugs: https://launchpad.net/keystone/+milestone/essex-418:01
jsavak#topic Status and Progress18:01
*** openstack changes topic to "Status and Progress (Meeting topic: keystone-meeting)"18:01
jsavakAll looks ok on https://launchpad.net/keystone/+milestone/essex-4 but I admit I've been out of the loop recently...18:02
jsavakhi termie18:03
ayoungjsavak, I've only been working on LDAP support.  My current code is on https://github.com/admiyo/keystone/tree/ldap218:03
termiewe're currently trying to finish the merge across, we ran into jenkins bugs last night that have resolved into some new bug18:03
ayoungI'm feeling pretty good about it, have something ready for code review shortly18:03
jsavak#link ldap support being worked on by ayoung  https://github.com/admiyo/keystone/tree/ldap218:03
termiebut the outstanding code in merge proposals is the required stuff for us to merge across legacy18:03
*** Guest1895 is now known as med_18:04
*** med_ has quit IRC18:04
*** med_ has joined #openstack-meeting18:04
jsavakok cool. Quick convo with a few people resulted in the abandon of #link https://review.openstack.org/#change,3985 which was a 401/403 disabled-user change18:05
jsavakthe review has a few links to explain why the change was abandoned18:05
*** ravi has left #openstack-meeting18:05
jsavaktermie - so the merge will still happen ok by end of e4?18:05
termiejsavak: the merge should happen today18:06
jsavaktermie thanks!18:06
*** zns has joined #openstack-meeting18:06
*** gyee has joined #openstack-meeting18:06
jsavakany other status updates?18:06
jsavaklooks like we covered some of #topic Keystone Light Progress (redux branch)18:07
jsavak#topic Keystone Light Progress (redux branch)18:07
*** openstack changes topic to "Keystone Light Progress (redux branch) (Meeting topic: keystone-meeting)"18:07
jsavakanything else for KSL progress?18:07
jsavak#topic Open-Discussion18:08
*** openstack changes topic to "Open-Discussion (Meeting topic: keystone-meeting)"18:08
jsavakany issues, questions, complaints, asks?18:08
termiei've been -2ing anything aimed at master and asking them to use redux instead18:08
jsavakwho's been pushing against master?18:09
termiejsavak: various code reviews come in18:09
jsavakthey'll be able to push to master again post merge though (tomorrow), right?18:09
termiejsavak: yes, though not with any of the existing reviews, obviously, since the code base is radically different18:10
termiejsavak: my statement was only meant to say i am preventing work being done before the erge18:10
termieso if somebody has a large problem with that they should probably let me know18:11
jsavaktermie: ok. Maybe an email out to the mailing list may help?18:11
*** ayoung_ has joined #openstack-meeting18:12
*** markvoelker has joined #openstack-meeting18:12
jsavakanything else for the open discussion?18:13
jsavaktaking that as a no. :)18:14
jsavakthanks y'all18:14
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"18:14
openstackMeeting ended Tue Feb 14 18:14:19 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:14
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-02-14-18.00.html18:14
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-02-14-18.00.txt18:14
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-02-14-18.00.log.html18:14
*** vladimir3p has quit IRC18:15
*** ayoung has quit IRC18:15
*** _cerberus_ has quit IRC18:15
*** soren has quit IRC18:15
*** martines has quit IRC18:15
*** joesavak has joined #openstack-meeting18:18
*** uvirtbot has joined #openstack-meeting18:20
*** westmaas_ has joined #openstack-meeting18:20
*** vladimir3p has joined #openstack-meeting18:21
*** _cerberus_ has joined #openstack-meeting18:21
*** soren has joined #openstack-meeting18:21
*** martines has joined #openstack-meeting18:21
*** niven.freenode.net changes topic to "Status and Progress (Meeting topic: keystone-meeting)"18:21
*** shang__ has joined #openstack-meeting18:26
*** dprince_ has quit IRC18:27
*** uvirtbot` has quit IRC18:27
*** jsavak has quit IRC18:27
*** ttx has quit IRC18:27
*** shang has quit IRC18:27
*** westmaas has quit IRC18:27
*** dprince has joined #openstack-meeting18:30
*** ttx has joined #openstack-meeting18:30
*** mattray has joined #openstack-meeting18:30
*** martine_ has joined #openstack-meeting18:38
*** martine_ has quit IRC18:38
*** adiantum has quit IRC18:39
*** zns has quit IRC18:39
*** martine_ has joined #openstack-meeting18:40
*** anotherjesse has joined #openstack-meeting18:41
*** jog0 has joined #openstack-meeting18:45
*** zns has joined #openstack-meeting18:46
*** zns has joined #openstack-meeting18:46
*** bcwaldon has joined #openstack-meeting18:52
*** novas0x2a|laptop has joined #openstack-meeting18:59
*** mestery has quit IRC19:02
openstackMeeting started Tue Feb 14 19:02:27 2012 UTC.  The chair is mtaylor. Information about MeetBot at http://wiki.debian.org/MeetBot.19:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.19:02
mtaylor#topic OpenStack CI19:02
*** openstack changes topic to "OpenStack CI"19:02
mtaylorone sec19:03
LinuxJediyay, I actually made the meeting today! :)19:03
jeblairyay meeting!19:04
LinuxJediit only took 22 hours of traveling to do it!19:04
mtaylorsee - how easy is that19:05
mtaylorso - I don't have a whole lot to report here today19:05
mtaylorLinuxJedi and jeblair are in Seattle with me this week, so we'll be doing a good amount of face-to-face meeting19:05
mtaylorother than last weeks fires on jenkins and then moving jenkins to a new server19:05
LinuxJediyou mean we are also doing work type stuff this week?19:05
mtaylorLinuxJedi: (ssssh)19:05
mtaylorjeblair is going to fix the gerrit trigger plugin so that we can use it for post-merge events so that we can stop polling repos19:06
jeblairyes, we, uh, "improved" a lot of infrastructure last week.  :)19:06
jeblairyep, making progress on that19:06
*** PaulTashima has joined #openstack-meeting19:06
*** mrmartin has joined #openstack-meeting19:06
mtaylorI've also got to sort out upgrading virtual envs when pip-requires change in submitted commit19:07
jeblairwe'll probably move gerrit to a new server soon; it's not as urgent as jenkins was, but still a good idea19:08
LinuxJedido I see more puppet work on the horizon for that?19:09
jeblairit's like half-puppetized19:10
LinuxJedihehe :)19:10
jeblairit's _managed_ by puppet, but the initial install is not handled by puppet19:10
mtayloralso - jeblair ... the venv jobs don't show their url trigger plugin config19:10
jeblairmtaylor: that may mean the don't have one?19:10
mtaylorjeblair: those were the only jobs that _did_ have url triggers19:11
mtaylorjeblair: so we should put that on our list of things to investigate19:12
jeblairi know, i mean you said they don't _show_ their config.  i think if they don't show it then they don't have it anymore.19:12
mtayloroh, sorry19:12
mtaylorI agree with you19:12
mtaylorthe question is - where did it go?19:12
mtaylorjeblair: job config history shows that you deleted it when you removed the throttle concurrent builds config19:14
mtaylorjeblair: https://jenkins.openstack.org/view/All/job/nova-venv/jobConfigHistory/showDiffFiles?histDir1=%2Fvar%2Flib%2Fjenkins%2Fjobs%2Fnova-venv%2Fconfig-history%2F2012-02-10_07-37-51&histDir2=%2Fvar%2Flib%2Fjenkins%2Fjobs%2Fnova-venv%2Fconfig-history%2F2012-02-14_19-13-2119:14
mtayloroh wait19:14
* mtaylor shuts up19:14
mtaylorit shows the opposite of that19:15
*** jk0 has joined #openstack-meeting19:15
LinuxJedimtaylor: it shows you removed it ;)19:15
mtaylorand shows that I removed the old config but didn't add the new one19:15
pvomtaylor: are you still having any build issues?19:16
pvojust wanted to double check .19:16
mtaylorpvo: with rax cloud? jeblair?19:16
jeblairmtaylor: i added it back to nova, and glance looks okay.  are you aware of others?19:16
pvomtaylor: yes, with rax cloud.19:16
mtaylorjeblair: well, keystone didn't have it19:16
jeblairpvo: let me check19:17
pvojeblair: no rush. just ping me oob if you need help19:17
jeblairpvo: great, will do.  it looks like the image builds have been more reliable the past few days:19:18
pvojeblair: excellent19:18
jeblairpvo: https://jenkins.openstack.org/job/devstack-update-vm-image/19:18
jeblairyou can see the history there, with one failure yesterday19:18
jeblair(it runs daily)19:18
pvojeblair: is that a rax specific build?19:19
jeblairthat's us trying to create an image from a running server in rs public cloud19:19
jeblairyou can see the error it returned there19:19
jeblairit also looks like vm launching is fairly happy now as well: https://jenkins.openstack.org/job/devstack-launch-vms/19:21
pvojeblair: got it.19:21
jeblair(that job launches vms based on the image created in the other job)19:22
mtaylorpvo: stupid question - is it possible to talk to rax cloud with python-novaclient?19:22
*** anotherjesse has left #openstack-meeting19:27
*** anotherjesse has joined #openstack-meeting19:28
bcwaldonmtaylor: it is possible19:28
mtaylorbcwaldon: neat. can I loop up with you on what settings I should give it?19:29
bcwaldonmtaylor: maybe...19:29
bcwaldonmtaylor: yeah, let's catch up after this19:29
*** westmaas_ is now known as westmaas19:39
*** ayoung_ is now known as ayoung19:40
mtaylorok. I think that's good for today19:42
*** openstack changes topic to "Status and Progress (Meeting topic: keystone-meeting)"19:42
openstackMeeting ended Tue Feb 14 19:42:36 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:42
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-02-14-19.02.html19:42
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-02-14-19.02.txt19:42
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-02-14-19.02.log.html19:42
*** blamar_ is now known as blamar19:48
*** adjohn has quit IRC19:54
*** jbryce has joined #openstack-meeting19:55
*** ewanmellor has joined #openstack-meeting19:57
*** GheRivero_ has joined #openstack-meeting19:58
*** esker has joined #openstack-meeting19:59
openstackMeeting started Tue Feb 14 19:59:59 2012 UTC.  The chair is jbryce. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.20:00
jbryceroll call. who's here?20:00
ewanmellorRed 1, standing by.20:00
jbryceso that's 6...will we get a 7th?20:02
jbrycethere we go20:02
jeblairmtaylor is on his way20:02
znszns here20:02
jbryceok, we'll wait a couple of minutes20:02
jbryce#topic Quantum core promotion20:02
*** openstack changes topic to "Quantum core promotion"20:02
jbrycedanwent updated the previous proposal with some updates from the incubation time period20:03
danwentI think key take-away is that bleeding-edge openstack shops have already started using quantum to counter some of the key networking issues they are seeing.20:03
johnpurI support the promotion... the project is being run well, is becoming a key target, and is supported by ttx from a release standpoint20:04
danwentmeanwhile, we've been making good progress toward integrating into openstack processes, thanks to folks like ttx, mtaylor, annegentle20:04
danwenthappy to answer questions / take comments.20:05
jbrycedanwent: it looks like a pretty good list of developers on there. how spread out are the actual volume of contributions?20:05
mtaylorthe quantum guys have been very responsive and have integrated well into the tooling20:05
anotherjessedanwent: is the goal to phase out nova-network (being core would mean recommendation/requirement that openstack clouds use quantum instead of nova-network)?20:06
danwentjbryce:  those are people who have contributed "regularly", though some from cisco team have had other responsibilities lately20:06
pvojbryce: we've been working closely with them, but I understand the implications there.20:06
johnpurhaving a standardized networking set of layers will be key to getting to future states of federation, cross-cloud resource management, etc.20:06
*** jakedahn has joined #openstack-meeting20:07
danwentI think there are very strong contribution already from cisco, citrix, nicira, and rackspace, as well as openstack infrastructure folks like monty and james blair20:07
pvoanotherjesse: I understood the transition to be somewhat like auth was. Or should have been .20:07
danwentanotherjesse:  have talked with vish about this.  he would like to evaluate whether we can rip out nova-network in folsom.20:07
anotherjessepvo: with diablo we deprecated the nova built-in auth and are removing in folsom20:07
danwentI think doing so in 6-months will take a commitment from existing nova team members as well as quantum members though20:07
anotherjessepvo: err, removing in essex or folsom20:07
anotherjessedanwent: a transition phase is great :)20:08
mtaylorI do like the idea of having quantum in core _before_ we start that transition phase20:08
jbrycedanwent: what do you think the essex quantum release will look like. even though quantum won't be part of the core, i think we saw that with the timing of core promotions people expected the new projects to "just work" even if they aren't core for essex. i'd like to make sure we can set expectations properly20:09
johnpuranotherjesse: agree on transition phase, the question is when20:09
danwentanotherjesse: I agree. my main concern would be people trying to move to quickly to rip out nova-network.  we have a decent "half-and-half" strategy right now.20:09
jbrycedanwent: i know you guys have been following all the e milestones already20:09
anotherjessedanwent: I'm primarily asking from an API perspective - if we remove/deprecate nova-network, users of openstack clouds could keep using the existing APIs and if they wanted richer network APIs could switch to using quantum directly?20:09
danwentthough half-and-half sucks long-term20:09
anotherjessedanwent: kinda like how you can use "image-list" in nova (which calls out to glance), or if you need a richer API use glance directly20:09
pvoanotherjesse: I was guess remove by or at folsom20:10
danwentjbryce:  the targeted use case of driving network creation + port attachment (what is documented in our admin guide) should be solid for essex20:10
danwentanotherjesse:  that's another thing I've been talking about with vish.  one model would be to let APIs like the ec2 API proxy to quantum for backward compat20:11
devcamcarmtaylor: +1 to having quantum in core and then migrating20:11
danwentanotherjesse: though new functionality would likely be exposed only via Quantum API.20:11
johnpurdanwent: +120:11
danwentanotherjesse:  yes, glance analogy is a good one.  In a sense, that is what we've done already, as you can drive quantum using nova-manage commands for creating networks.  Gives good backward compat.20:12
anotherjessemtaylor / devcamcar: I think we need to have a well documented plan of what existing nova network APIs will work in Folsom (or whenever quantum becomes core) with both quantum & nova-network20:12
mtayloranotherjesse: ++20:12
devcamcaris the goal to have quantum replace all of the relevant nova-network pieces by folsom release?20:13
pvodoes quantum really mean quantum+melange?20:13
anotherjessedevcamcar: core means it is a part of openstack, we've learned with keystone being half pregnant is harmful to developers and users20:13
mtaylorI don't think we necessarily need to migrate by folsom - I thnk that's a call for vish - I just think that if we do migrate, all of the migration steps should be done once quantum is core20:13
mtaylorwhat anotherjesse said20:14
mtaylorpvo: good question ...20:14
danwentdevcamcar:  that is the goal long-term, but would need commitment from nova team to achieve it in such a short time frame20:14
mtaylordanwent: can we accept quantum without accepting melange or should we be considering both?20:14
* anotherjesse is texting vishy20:14
*** adjohn has joined #openstack-meeting20:14
* mtaylor should add an IRC-bot to SMS gateway...20:14
devcamcarso probably by G release nova-network goes away and is fully replaced by quantum/melange would be my assumption20:14
pvoanother option is to merge them into a single project.20:14
danwentpvo:  that's a good question.  I've been talking with troy about options for more closely coupling melange and quantum20:15
pvosince they are intertwined.20:15
devcamcarpvo: ideologically that would make sense - fewer boundaries and moving parts is always preferable to 200 different projects ...20:15
anotherjessedevcamcar: having it so removal of nova-network can be done without any users having to know would be the issue20:15
danwentdevcamcar:  I would feel much more confident about G.  Not that I wouldn't love to do it by F, if enough people pitch in.20:15
devcamcaranotherjesse: shudder20:16
danwentdevcamcar:  definitely from a tenant API perspective a closer coupling of quantum + melange makes sense.20:16
danwenttroy and I have chatted about this on several occassions.  Plan was to propose something concrete at F summit.20:16
devcamcarmelange becomes core in folsom or g?20:16
pvodanwent: I might agree on your timeline for G, but would hope for F.20:16
jbrycei talked to troy as well and i think it's probably a separate question from promotion for quantum itself20:17
pvojbryce: it may be, but it surely affects the timeline for integration20:17
pvoif we take quantum but not melange that might be … interesting20:18
*** steve426f has joined #openstack-meeting20:18
tr3buchetfully replaced20:18
anotherjessedanwert: I think it might be good to have a section on the details of the migration plan for nova-network.  my only concern with saying +1 to core is the question of what network APIs does an openstack cloud need to expose to be considered "openstack"20:18
johnpurpvo: if that is true it argues for collapsing/integrating the projects20:19
devcamcaranotherjesse: +1 - i'm not sure i've ever seen it articulated in detail.  i think i know, but maybe i dont know what i dont know :)20:19
danwentanotherjesse:  right now a lot of the nova non-ec2 network apis are extensions, right?20:19
anotherjessedanwent: it is already a little confusing, and I would prefer that we clean up our position on network APIs in nova (with and without quantum) instead making it more complicated (adding quantum to the mix without a definitive plan for transitions)20:20
tr3buchetanotherjesse: +120:20
pvoanotherjesse: is network enough functionality to be standalone? Is that the question?20:20
anotherjessedanwent: yep!  although they are on by default.  I know bcwaldon was hoping on removing the "extension" label in folsom20:20
jbryceanotherjesse: is it worth delaying promotion to core another 6 months to have that laid out, or something that we should make a priority for the 6 months?20:21
danwentOk, from talking with vish I believe his plan is to be pretty aggressive about avoiding additional network capabilities in nova, assuming the long term plan is quantum.20:21
johnpurcan we get a clear design/go-forward plan in shape to discuss in SF?20:21
pvojohnpur: ++20:21
danwentI think so.  The key thing is that we need nova people on board as well as quantum people.20:21
anotherjessejbryce: I don't know if it will take 6 months - it could be that it is a relatively small task20:22
danwentanotherjesse: I agree.20:22
pvoanotherjesse: I think the hinge is melange20:22
anotherjesse(most of) nova people want to move quantum, just want it to be orderly20:22
pvoanotherjesse: maybe not though.20:22
pvoI haven't tested splitting that functionality.20:22
danwentpvo:  what functionality?20:22
anotherjessejbryce: when does the core vs. not decision need to happen?20:22
jbrycesince the promotion time windows are only pre-release every 6 months, then i'd be in favor of promoting it to core for folsom and marking out some these things as critical tasks to work on20:22
anotherjesse(for folsom)20:23
jbryceanotherjesse: next couple of weeks20:23
pvohaving nova manage ips and quantum manage networking20:23
pvowithout melange20:23
danwentpvo:  this works already20:23
devcamcarpvo: sounds reasonable20:23
pvodanwent: cool… I hadn't worked with it in that config20:23
danwentin fact, it is the default mode of running quantum.20:23
anotherjessejbryce: so we can add success criteria to the proposal that "assuming X (api, melange, …)" it goes core20:23
anotherjesseand work through that in the next week20:23
danwentthough I do believe long-term the flexibility + APIs of melange are what we want.20:24
jbryceso what are the key things we'd like to have to feel comfortable promoting it for folsom?20:24
jbryce1) plan for transition with nova-network20:24
jbryce2) draft for melange integration20:24
jbryce3) documentation of desired network api end state20:25
jbrycedid i miss anything?20:25
devcamcar4) documentation of delta of capabilities with vanilla nova-network vs nova-network + quantum20:25
devcamcar5) bonus points: #4 + melange20:25
*** reed has joined #openstack-meeting20:25
devcamcarlet the community have a clear roadmap20:26
johnpur** able to have in place to discuss in April and plan for the Folsom release20:26
danwentOk, I'll start out by setting up a more in-depth dicussion with vishy20:26
jbrycedanwent hit some of those as bullets on his updated proposal but basically we'd like to get more details20:26
danwentjbryce: ok, sounds good.  thanks for the feedback everyone20:27
jbrycewhat else? any other concerns that we think we'd like answered before approving a promotion?20:27
jbrycei think that quantum has done an awesome job so far in incubation20:27
johnpurjbryce: they are the standard so far...20:28
danwentthanks guys.  so next week, same bad channel :) ?20:28
ewanmellorjbryce: Was about to say the same thing.  We should thank Dan for running his project so well!20:28
*** _adjohn has joined #openstack-meeting20:28
jbryceyes...thanks, dan. it's made openstack look like we're figuring out what we're doing with this incubation thing.  = )20:28
johnpurhe he20:29
jbryceso let's plan on discussing again next week20:29
jbryce#topic open discussion20:29
*** openstack changes topic to "open discussion"20:29
jbryceanything else?20:29
jbrycebreak early?20:29
mtaylorI got nothing20:29
johnpurdo we have any further progress or direction on fits testing?20:29
jbrycejohnpur: i just got to cloud connect and am eating cotton candy from hp cloud services20:29
johnpurjbryce: :)20:30
anotherjessejohnpur: fits would need to know our network api plan :)20:30
*** adjohn has quit IRC20:30
*** _adjohn is now known as adjohn20:30
jbrycejohnpur: i think it's stalled a little20:31
johnpuralso, are we going to address/comment on the foundation thoughts from Red Hat that was posted?20:31
jbrycei'll send a note out and see if what our next step with it should be20:31
jbrycejohnpur: are you referring to markmc's proposal? we actually incorporated a couple of ideas from there in the draft structure we put up friday and my plan is to continue iterating from that draft structure (with the mailing list, meetup tomorrow, webinars, etc)20:33
johnpurjbryce: yes, good to hear. there was some good ideas there.20:33
jbryceanything else?20:34
*** _adjohn has joined #openstack-meeting20:35
jbryceall right. thanks everyone!20:35
*** openstack changes topic to "Status and Progress (Meeting topic: keystone-meeting)"20:36
openstackMeeting ended Tue Feb 14 20:36:02 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:36
* mtaylor will now find a sandwich20:36
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-02-14-19.59.html20:36
*** _adjohn_ has joined #openstack-meeting20:36
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-02-14-19.59.txt20:36
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-02-14-19.59.log.html20:36
*** adjohn has quit IRC20:37
*** jk0 has left #openstack-meeting20:38
*** _adjohn has quit IRC20:39
*** edconzel has joined #openstack-meeting20:46
*** sandywalsh has quit IRC20:46
*** ewanmellor has quit IRC20:49
*** mjfork has joined #openstack-meeting20:57
*** esker has quit IRC20:59
*** YorikSar has joined #openstack-meeting21:00
openstackMeeting started Tue Feb 14 21:00:33 2012 UTC.  The chair is jaypipes. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.21:00
jaypipesHello all, I'm filling in for ttx today.21:00
termiehello jaypipes21:01
jaypipesBased on some input from ttx, I'd like to mostly focus today on Keystone redux + Nova.21:01
jaypipesso... unless notmyname, you have anything urgent to bring up, I'd like to move that Glance and Swift be skipped in today's meeting?21:01
*** steve426f has quit IRC21:01
anotherjessenotmyname: I'd love to get your input on https://review.openstack.org/#change,3712 in #openstack-dev21:02
jaypipesas a quick status update, Glance has a few bugs, but nothing major and is tracking fine for E4 thx to good work from Eoghan Glynn, Stuart McLaren and others21:02
jaypipesanotherjesse: is swift the only CLI tool left to standardize?21:02
anotherjessejaypipes: YES! :)21:03
anotherjessehappy dance21:03
jaypipesanotherjesse: ah, nice work dtroyer!21:03
jaypipesOK, termie, ready to chat about redux?21:03
jaypipesanotherjesse: and you :)21:03
*** jwalcik has joined #openstack-meeting21:03
termieCurrent Keystone (redux) Status!21:04
termiedo we need to do some thing with the meeting topic21:04
termieto make the bots happy21:04
jaypipesso, ttx has some valid concerns about the merge-readiness of the redux branch in relation to the ongoing feature freeze.21:04
jaypipes#topic Keystone Redux status21:04
*** openstack changes topic to "Keystone Redux status"21:04
jaypipestermie: ttx was looking for an overall status on redux and a description of any blockers21:04
termieready whenever you are21:05
termie(if you are done prefacing the question)21:05
jaypipestermie: yes, please go ahead21:05
termieCurrent Keystone (redux) Status!21:05
anotherjessethe suspense is killing me21:06
termiewe planned on haaving the marge prop in flight this morning, however due to some setbacks in the CI world most of our patches from yesterday are only now landing21:06
termiewe previously discussed a list of blockers, all of which are addressed by the patches in the queue21:06
termieonce they land we'll ask jeblair to nicely re-roll the merge prop21:06
termieform redux to master21:06
anotherjessethe primary focus of the patches were migration paths from diablo 5, diablo final and essex to redux21:07
*** dtroyer has joined #openstack-meeting21:07
jaypipestermie, anotherjesse: is https://review.openstack.org/#q,status:open+project:openstack/keystone+branch:redux,n,z an accurate depiction of remaining items to go in?21:07
jaypipestermie, anotherjesse: and I see quite a few bugs tagged with redux: https://bugs.launchpad.net/keystone/+bugs?field.tag=redux21:08
termieand https://bugs.launchpad.net/keystone/+bugs?field.tag=redux21:08
termiethose marked "critical" the blockers21:08
anotherjessejaypipes: I believe so - the major deltas that might block merge is what state of XML support people require before the merge vs before E421:08
termieall of which are either committed or waiting on CI21:08
jaypipestermie, anotherjesse: the two critical bugs that are in New status...21:08
jaypipestermie: let's take the bugs one at a time... one sec21:08
termiejaypipes: both committed or in the queu21:08
jaypipes#link https://bugs.launchpad.net/keystone/+bug/92855821:08
uvirtbotLaunchpad bug 928558 in keystone "remove keystoneclient functionality from keystone-manage" [Critical,New]21:08
anotherjessetermie: want to update the https://bugs.launchpad.net/keystone/+bug/928558 (it has landed)21:09
jaypipestermie: that one needs a status update? or...?21:09
anotherjesseit was merged in https://review.openstack.org/#change,409521:09
jaypipesanotherjesse: this one: https://bugs.launchpad.net/keystone/+bug/931837 is Critical, but I'm not sure it's really critical (doc fix)21:09
uvirtbotLaunchpad bug 931837 in keystone "update docs to talk about keystone-manage & cli" [Critical,In progress]21:09
anotherjesseadded a comment21:09
jaypipescool, thx21:09
termiethe doc fix is already associated with a change in the queue21:09
jaypipestermie: gotcha. thx21:10
anotherjessejaypipes: we wanted to make sure we had documentation for the differences (termie noted a couple tweaks and sleepsonthefloo is updating them now)21:10
jaypipesanotherjesse: got it. just wasn't sure about the Critical priority, but if it's already in-flight, totally cool.21:10
anotherjessejaypipes: yeah, the large thing was hoping to make the documentation reflect reality21:11
*** vladimir3p has quit IRC21:11
anotherjesseanotherjesse: to minimize confusion during the transistion process21:11
jaypipestermie: is this one covered in the patch that has other docs in it? https://bugs.launchpad.net/keystone/+bug/92804321:11
uvirtbotLaunchpad bug 928043 in keystone "document how to configure keystone (redux) with swift auth" [High,Confirmed]21:11
jaypipesanotherjesse: talkin' to yourself again? ;)21:12
termiejaypipes: that is not in our blocker category but the general expectation is that nothing has changed21:12
anotherjessejaypipes: swift + keystone is a work in progress regardless of keystone implementation21:12
jaypipesanotherjesse, termie: k21:12
anotherjessejaypipes: chmouel has been helping with the swift middleware & documentation21:12
jaypipestermie, anotherjesse: ok, so looks like all critical and most high bugs are in progress or already taken care of...21:13
termiejaypipes: that is our feeling as well21:13
anotherjessewe've been doing pretty regular sweeps of keystone bugs to re-catagorize21:13
jaypipestermie, anotherjesse: when do you expect the final merge prop?21:13
*** jbryce has quit IRC21:14
termiejaypipes: we think jeblair should be able to roll a new one within the next hour or so21:14
jaypipesanotherjesse: and the devstack-related changes for redux? those all good? have we smokestacked it all yet?21:14
jaypipestermie: excellent.21:14
anotherjesseassuming no more gotchas in the CI environment I think within an hour to gerrit then an email to #openstack21:14
anotherjessejaypipes: we have been keeping a devstack branch in gerrit as well (it is used as the merge to redux gate)21:15
termiejaypipes: the devstack changes are still going to require hand-holding, we have a new devstack branch but they are inter-dependent with the redux branch of keystone21:15
termiejaypipes: but it has been being used as the gating branch and we have kept it up to date with amster21:15
jaypipesOK, good to hear.21:15
termiejaypipes: so when the merge is approved we'll have to get mtaylor or jeblair to ninja them both in at once21:15
anotherjessejaypipes: the only concerns I have with getting the merge in is: if the community thinks that XML is a blocker for mereg21:16
jaypipesanotherjesse, termie: so, looks like you both have a great handle on redux stuff. Could I ask one of you to send a post to the ML when the merge goes through with an update for the cmomunity and what (if anything) it means to folks?21:16
anotherjessethus far I've not gotten any feedback saying that21:16
zulubuntu/debian packages should start appear tomorrow for what its worth21:16
*** martine has quit IRC21:16
termiezul: cool!21:17
jaypipesanotherjesse: had a question offline... about Swift + Keystone. Could you elaborate on what you meant by they are a work in progress above?21:17
znsanotherjesse: are you still planning on sending an email to the ML to ask about XML? Seems like that idea has been abandoned if we're merging in an hour?21:17
anotherjessejaypipes: yes, as soon as mtaylor & termie are done with the merge prop we will send an email with - summary of open issues (xml, ldap), how to try it out (devstack branch), ...21:17
anotherjessezns: YEP!21:17
znsanotherjesse: k. tx.21:18
jaypipesanotherjesse: thx on email. that will be appreciated.21:18
anotherjessezns: proposing to merge in an hour, not merging …  the community can review −1 or −2 requiring xml21:18
znsanotherjesse: excellent. Thanks.21:18
*** reed has quit IRC21:18
jaypipesanotherjesse: had a question offline... about Swift + Keystone. Could you elaborate on what you meant by they are a work in progress above?21:18
anotherjessejaypipes: keystone + swift has been the slowest for us (as a community) to get working well together21:19
anotherjessehence the volume of questions about key+swift on the mailing list21:20
johnpuranotherjesse: are there issues with keystone and swift 1.4.6?21:20
anotherjessejohnpur: I don't think the issues have been with the projects, but the middleware & documentation21:20
*** dgribble has joined #openstack-meeting21:21
devcamcarwhich is funny since swift was the only project that supported multiple auth middlewares from the get go21:21
jaypipesanotherjesse: I think what johnpur is looking for is whether the issues are real blockers to implementing Swift with a Keystone API-compatible identiity layer.21:21
johnpuranotherjesse: thx. jaypipes: yes!21:22
anotherjesseI know devstack has been putting the two together for months now,21:22
anotherjessehttps://github.com/cloudbuilders/devstack/blob/master/stackrc#L10 <- for instance we've been working on the middleware here21:22
anotherjessejohnpur: chmouel has been working on it from our side21:22
*** jdg has joined #openstack-meeting21:22
jaypipesanotherjesse: to be clear, then, redux and KSL has had no influence on the Swift + Keystone stuff? These issues existed prior?21:23
*** mrmartin has quit IRC21:23
anotherjessejaypipes: correct21:23
jaypipesanotherjesse: k, thx21:23
anotherjessejaypipes: the contract between services haven't changed21:23
jaypipesjust want to understand completely.21:23
anotherjesseso this was a pre-existing issue that folks from swift + rcb (and others) are working on21:23
*** dendro-afk is now known as dendrobates21:24
*** somik has joined #openstack-meeting21:24
jaypipesalrighty. OK, does anyone have any Keystone stuff to bring up?21:24
jaypipes#action anotherjesse to send post to ML after redux is merged into trunk explaining its impact21:24
jaypipesvishy: you're on deck.21:24
jaypipesalrighty, on to Nova.21:25
jaypipes#topic Nova Status21:25
*** openstack changes topic to "Nova Status"21:25
jaypipes#link https://launchpad.net/nova/+milestone/essex-421:25
anotherjessejohnpur: an email to the openstack list would probably be good to clear up questions.  Sicne if you have questions about keystone+swift I'm sure others do as well21:25
jaypipesvishy: looking at #link above, looking pretty good for E4.21:26
johnpuranotherjesse: +121:26
vishythere are three outstanding FFes21:26
jaypipesvishy: the two Blocked blueprints, any update on those?21:26
jaypipesvishy: is the keystone export blocked on redux I assume?21:26
vishyIf they aren't merged by next week, I'm going to push them21:26
jaypipessame with depr auth?21:26
zuli need another +1 for the lxc block support btw21:27
vishyjaypipes: they are blocked waiting for redux21:27
jaypipesvishy: gotcha21:27
vishyzul: post link21:27
vishyso the netapp driver and zeromq both have outstanding changes needed21:27
vishyzul: that was previously approved and failed a pep8, so just needs a rubber stamp21:28
vishythe big question is the zones code21:28
jaypipesvishy: before discussing zones, how about the libvirt/KVM one from nati2_ ? https://review.openstack.org/#change,347721:28
vishyoh has that not merged yet?21:29
jaypipesvishy: looks like that one was pretty far along in reviews?21:29
*** markwash has joined #openstack-meeting21:29
*** martine has joined #openstack-meeting21:29
vishyjaypipes: yeah that should make it21:29
*** wwkeyboard has joined #openstack-meeting21:29
vishythere was one outstanding issue.  I thought it had been handled but not quite yet21:30
jaypipesvishy: ok, well looks like that should be able to get in shortly. let's discuss the zones, then, eh?21:30
jaypipescomstud: around?21:30
comstudjaypipes: yep21:30
*** mestery has joined #openstack-meeting21:30
jaypipescomstud: update on the zones stuff?21:30
jaypipesor vishy ..21:30
vishyso the code is in review21:31
vishythe concern is whether it is too broad21:31
vishyI looked over it and the core changes are relatively minor21:31
vishya couple database migrations adding new fields21:31
nati2_Yes I have fixed version on my laptop21:31
nati2_After testing it, I'll do review request again21:31
jaypipesnati2_: k, thx21:31
comstud1 of the migrations is to the zones table itself21:31
vishyand a few changes in compute.api21:32
comstudthe other migration is 1 column added to instances21:32
vishyIMO these are fine to go in21:32
vishythe rest of the code is all separate21:32
comstudthe compute.api change is just moving code into a separate method21:32
vishyso here is what i'm thinking21:32
vishycomstud: can you split into two patches?21:32
comstudthere's an openstack API change regarding network cache21:32
vishyone with core changes and the second with all of the added stuff?21:32
comstudI can.. if you want nova/zones/* a separate patch21:33
vishylets get the core stuff in right away21:33
comstudthat's easy21:33
vishythen the other stuff can go in if necessary21:33
vishywe just have to make sure that we let people know that the feature is expiremental21:33
markwashI have a few questions about getting this in21:33
comstudso, the instance migration is a part of the core ?21:33
jaypipesdo we have updates to documentation that are needed for this? cc annegentle21:33
comstudzones migration is 2nd patch or 1st?21:33
vishycomstud: I would do the migrations in the first21:33
jaypipesmarkwash: pls do speak up :)21:34
annegentlejaypipes: there's no doc that I know of21:34
comstudthere's some documentation in the nova code base itself21:34
vishywe need to remove all of the references to the old zones code21:34
comstudwhich gets removed in the 'zone removal' branch21:34
jaypipescomstud: no, I was referring to docs in doc/source21:34
markwashso #1, I'm wondering if the motivation for getting this in is really there if it is experimental and no one is presently extensively functional testing it21:34
comstudvishy: done. in sandy's branch21:34
vishycomstud: good21:34
jaypipesmarkwash: excellent question.21:35
markwashmaybe it is, I dont know as much about the deployers who want it in essex21:35
annegentlecomstud: one concern I had was the name change in the code - everything's now named zones. It's like a big barrier to understanding to begin with, to me.21:35
markwashrackspace of course is not limited to letter releases21:35
jaypipesannegentle: ++21:35
annegentlecomstud: "name change" I mean is it zones21:35
vishymarkwash: the 2nd patch can wait for folsom afaic21:35
comstudannegentle: we may want to leave it 'zones' for essex to make it easier21:35
jaypipescomstud: I think that is a good idea.21:36
*** johan_-_ has joined #openstack-meeting21:36
vishymarkwash: but the code will hard to maintain separately otherwise21:36
markwashcomstud: I definitely think zones is confusing, but I also think changing it could be more confusing at the moment21:36
comstudmarkwash: nod21:36
markwashedit: the name "zones"21:36
vishymarkwash: so FFeing the minor core changes to make it work seems fine21:36
comstudmarkwash: i don't want to change it on a whim21:36
*** mestery has quit IRC21:36
vishymarkwash: as for the new code, it could go in a branch21:36
*** sandywalsh has joined #openstack-meeting21:37
comstudvishy: I can live with that.. I'm going to change a FLAG name to match the new branch, also, though.  FLAGS.21:37
comstudFLAGS.enable_zone_routing -> FLAGS.enable_zones21:37
vishycomstud: that seems fine21:37
markwashwhat are we considering "core" in the change, again?21:37
vishydb migrations21:37
markwashah, okay21:37
vishyapi change to network cache21:37
comstudmarkwash: the 2 DB migrations, the minor change to OS API for network cache, and I moved some code in compute.api into a new method21:38
vishyminor change to compute api (which is just better error recovery)21:38
vishyyou cool with that plan markwash?21:38
markwashI like that better, I'm still curious about whether or not the deployers clamoring for this really want an experimental implementation21:38
markwashI'm sort of playing devils advocate on the "experimental" thing21:39
vishymarkwash: the main one is mercadolibre21:39
vishymarkwash: and their other option is to write something themselves21:39
vishywhich isn't good for anyone21:40
vishybut they said they were happy experimenting using a branch21:40
comstudi don't have a problem keeping a branch updated for a couple months until F opens21:40
markwashso we might basically collaborate with them on the branch?21:40
comstudthe DB migrations are my main concern about keeping it working21:40
*** lloydde has joined #openstack-meeting21:41
vishythat was the hope yeah21:41
jaypipescomstud: yes, but if the mirgations are done in patch 1 (and into trunk branch), then things are good, right?21:41
comstudjaypipes: Yep, that solves my issue21:41
markwashI like this plan. The core changes seem like a good foundation for us to continue to build out and prove the zones implementation21:41
jaypipesthen I think that makes the most sense21:41
anotherjessecomstud: if we kept the branch open until F, would we still remove the existing zone stuff?21:41
comstudanotherjesse: sounds like it (the existing stuff) should stay in essex21:42
markwashI think removing existing zones adds a fair performance gain to the api21:42
comstudi'd really love to remove it ;)21:42
vishyi really don't want people using the zones stuff if we are trashing it21:42
markwashand a good deal of complexity removed from the codebase21:42
anotherjessecomstud: can we "remove" it by removing the API (not the code)21:42
comstudvishy: Good to hear.. I'd love to remove it21:43
anotherjesseI agree with vishy: having people deploy it in F would mean we would have to support it21:43
comstudit cleans things up considerably21:43
*** russellb has joined #openstack-meeting21:43
vishyok to summarize21:43
vishy1) remove old zones code (approve sandy's branch)21:43
vishy2) comstud splits core changes out of his patch and proposes21:44
vishy3) FFe for comstud's branch21:44
vishy4) added zones code goes into a separate branch21:44
anotherjesse5) critical bug update python-novaclient to remove zone stuff?21:44
anotherjesse(or at least hide it)21:45
jaypipesanotherjesse: ++21:45
comstudremove it.. most of it will be not needed in new version21:45
*** salv-orlando has joined #openstack-meeting21:45
comstudI will be re-adding a zones extension, but it'll provide some different functionality21:46
*** davlap has joined #openstack-meeting21:46
anotherjessevishy / comstud - need to alert Anne / doc team to remove zone from docs (if it was ever doc'd)21:46
jaypipesk, vishy would you mind sending a short post to the ML summarizing the above and the outlined steps that are to be taken?21:46
jaypipesvishy: of course, emphasizing that we're doing this to ensure long-term stability of the code base for service deployers, etc...21:47
markwashthis all sounds great to me21:47
*** bhall has joined #openstack-meeting21:47
*** bhall has quit IRC21:47
*** bhall has joined #openstack-meeting21:47
*** dendrobates is now known as dendro-afk21:47
annegentleanotherjesse: really doc's all in the code, so far, but we could make it a priority for Doc Day if needed21:47
vishyjaypipes no problem21:48
jaypipesvishy: k, any other things you'd like to highlight in Nova-land before we move on?21:48
jaypipesdevcamcar: you're on deck...21:48
jaypipesalrighty, onwards to Horizon...21:49
jaypipes#topic Horizon Status21:49
*** openstack changes topic to "Horizon Status"21:49
jaypipesdevcamcar: ping21:49
jaypipes#link https://launchpad.net/horizon/+milestone/essex-421:50
jaypipesdevcamcar: status report?21:50
devcamcarso we are moving right along - today we want to take a moment and talk about design in general21:50
devcamcarpaul tashima has been working on the human interaction guidelines which outlines general design decisions that the community has made21:50
devcamcarpaul want to jump in?21:50
PaulTashimaso we are currently trying to formulate the best way to create a process for design for the openstack project21:51
PaulTashimathe current idea can be viewed here: http://bit.ly/zjbuFQ21:51
*** dprince has quit IRC21:51
PaulTashimato help implement this process we've been working on the human interface guidelines doc to create evaluation criteria21:51
PaulTashimawe also have the current dashboard model documented (though slightly out of date): http://bit.ly/vgMmiA21:52
devcamcarour goal with all of this is so that other teams can help contribute to horizon and make sure their projects are well represented21:52
annegentledevcamcar: ++21:52
PaulTashimayeah, hopefully this process will unify the user experience for openstack21:53
*** davlap has quit IRC21:53
jaypipesnice stuff, guys!21:53
PaulTashimafeel free to provide any kind of feedback on this stuff21:53
devcamcarand for us to not be the bottleneck for design - this way we can set the foundation and guidelines and make it much easier for others to jump in and know they are using the right approaches21:53
jaypipesPaulTashima: great start. I encourage you to share with the mailing list.21:53
PaulTashimacool, thanks!21:53
devcamcarwe will definitely be getting feed back as well on ML21:54
devcamcarany questions for us this week?21:54
jaypipesdevcamcar: re: the E4 milestone, there are a ton of Confirmed bugs...21:55
jaypipesdevcamcar: and a bunch of Not Started blueprints21:55
devcamcarjaypipes: yes there are a number that are nice to haves and not necessary for essex. i'll be re-triaging this week and moving out a few of the visual enhancements to folsom21:55
jaypipesdevcamcar: probably good to re-target some of them to a later milestone?21:55
jaypipesdevcamcar: gotcha.21:56
devcamcarour goal is to have a solid functioning and polished version out for essex21:56
devcamcarwe'll add more fancy craziness for folsom21:56
jaypipesexcellent. I noticed the testing system was overhauled today21:56
jaypipeslooked like a good refactoring.21:56
devcamcaryes, a lot of effort has gone into improving test coverage in essex21:57
*** jlm^r has joined #openstack-meeting21:57
jaypipesdevcamcar: FWIW, I've created a blueprint for separating the Glance client into its own package/project. Hoping that F1 timeframe that will  be done.21:57
*** mcohen_ has joined #openstack-meeting21:57
jaypipesdevcamcar: that should help Horizon -- at least with dependencies and such.21:58
devcamcarawesome :)21:58
jaypipesdevcamcar: and dtroyer has done an excellent job aligning all the CLIs authentication.21:58
jaypipesdtroyer: ty!21:58
devcamcarthanks dean!21:58
devcamcarhorizon is the team that gets to find all the discrepencies in how all the clients work21:59
*** mandeep has joined #openstack-meeting21:59
devcamcarso that is always appreciated21:59
jaypipesOK, on a final note, I'm not sure about the status of the design summit. I believe ttx will be sending a note out in the next week or so explaining the invitation process and any changes from Boston that have occurred.21:59
*** davlap has joined #openstack-meeting21:59
jaypipesOur little community has grown quite a bit, and there is only so much room at the design summit, so I expect there will be some disappointments as far as how many folks can actually go. But, c'est la vie with a growing project such as ours.22:00
jaypipesAlright everyone, time to wrap up. See you on the ML.22:01
*** openstack changes topic to "Status and Progress (Meeting topic: keystone-meeting)"22:01
openstackMeeting ended Tue Feb 14 22:01:13 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-02-14-21.00.html22:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-02-14-21.00.txt22:01
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-02-14-21.00.log.html22:01
*** jwalcik has left #openstack-meeting22:01
devcamcarlater all22:01
*** YorikSar has left #openstack-meeting22:01
*** PaulTashima has left #openstack-meeting22:01
danwento/ netstack22:02
salv-orlandosalv here. Hello everybody.22:02
wwkeyboarddanwent: sorry about the confusion yesterday,22:02
danwentwwkeyboard:  phew, for a second i thought I was by myself :)22:02
*** nati2_ has quit IRC22:02
danwentwwkeyboard: no worries22:02
wwkeyboardbefore we start, could someone with core +2 that patch?22:02
*** dtroyer has left #openstack-meeting22:03
danwentthat patch has lots of reviews, we just need some nova core devs to +222:03
wwkeyboardI think jason and I have some more testing we want to follow that22:03
danwentwe should figure out a why that someone can be a core dev for the network portion of the nova code....22:03
danwentwwkeyboard: awesome22:03
openstackMeeting started Tue Feb 14 22:03:35 2012 UTC.  The chair is danwent. Information about MeetBot at http://wiki.debian.org/MeetBot.22:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.22:03
danwent#link agenda: http://wiki.openstack.org/Network/Meetings22:03
danwent#info  E-4 branch point is only one week out:  Feb 21st22:04
danwentI'm extremely nervous about how much proposed work there is22:04
salv-orlandoI am scared by the plugins22:04
salv-orlandothey are growing on a daily basis :)22:05
danwentsalv: yeah.  real concern is that plugin code grows while team of core people who review plugin code does not :(22:05
GheRivero_how many plugins can we count now?22:05
danwenthopefully we can get more people to join the core team, contributing beyond plugins.22:06
wwkeyboardShould we try to pull the plugin code out of core?22:06
salv-orlando3 in, 3 in review22:06
danwentstill just 3 merged.22:06
salv-orlandoI mean 3 in trunk - 3 under review22:06
wwkeyboardand just provide a set of tests that a plugin must conform to?22:06
GheRivero_love it :)22:06
danwentwwkeyboard:  its definitely possible to not be merged into core and things will run just fine22:06
danwentthere are several people who do this already, I believe :)22:07
wwkeyboardindeed :)22:07
danwentat the same time, having plugins in the core repo help people contribute and improve them.22:07
*** russellb has left #openstack-meeting22:07
mandeepmore plugin just indicate wider adoption of quantum22:07
danwentmandeep: I agree22:07
danwentits definitely my goal to get a healthy set of plugins into the quantum code base22:08
wwkeyboardmandeep: +1, but it also puts a burdon on the core quantum code22:08
danwentthey also serve as examples to future plugin writers22:08
mandeepAnd by design plugin do not destabalize the code base, since they only "exist" if enabled22:08
danwentmandeep:  I worry that an argument like that is an argument for a code base with a lot of lightly reviewed, low quality code.22:09
danwentwe need to make sure plugins are reviewed22:09
mandeepSorry if that was how it spounded22:09
danwentmandeep:  no worries :)22:09
danwentdidn't mean to be critical, only explaining the root of my concerns22:10
wwkeyboardSorry to derail the meeting, maybe this would be better handled on the ML?22:10
mandeepI agree that plugins need review, ... just that they allow us to move faster without destabalizing the trunk22:10
wwkeyboardWe have a lot of points to consider22:10
*** johnpur has quit IRC22:10
danwentits a balance between getting more plugins to show adoption, and building the core team to support owning the larger codebase22:10
*** martine has quit IRC22:10
salv-orlandoMost of the times reviewing is no more harder than read-proofing a document, but it still takes time, especially with larger patches, as reviewers have to figure out what the code does.22:10
mandeepI understand22:11
danwentwwkeyboard: I'm fine with that.  I don't mean to say that we can't merge all of these plugins, only that the review load will be high, and I want to make sure we don't repeat the mistake of E-3 where were were reviewing code until the last minute, and didn't have enough time to be testing quantum prior to the release.22:11
danwentOk, to the ML22:11
*** troytoman-away is now known as troytoman22:11
danwentI want to make sure we talk about the non-plugin changes for E-422:12
danwentso they aren't overlooked22:12
*** Yak-n-Yeti has left #openstack-meeting22:12
danwentfirst, salv, v1.1 client changes?22:12
salv-orlandoWorking on them right now22:12
danwentsalv: btw, I apologize, still have a half written response to your email about client unit tests.22:12
salv-orlandoI expect to commit code on friday at least for supporting error codes and changes for operational status22:13
salv-orlandodanwent: no worries.22:13
danwentsalv: great22:13
danwentsalv: on unit tests, I suspect that mocking out the server is a fair amount of work, so for the time being I don't see a problem with requiring the server to run client unit tests.22:13
danwentyou'll always have to worry about the case when the server mock differs from the server anyway.22:13
salv-orlandodanwent: agreed.22:14
danwentok, let's stick with that for now.22:14
salv-orlandoI will send an email to the mailing concerning filter specification on the CLI (something that as far as I can see not even python-novaclient does)22:14
danwentsalv: yeah, quatum's ahead of the game :)  good work salv22:14
danwentat some point I'd like to give the client better arg parsing capabilities, similar to what python-novaclient does22:15
bhallyes that would be nice22:15
danwentbut I suspect that this is more work than we have time for in E-4, unless you were already viewing that as a requirement for adding filters22:15
salv-orlandoagreed but recent feedback (see blogs, twitter) suggest on the client side priority should be given to horizon support22:16
danwentinteresting… hadn't heard that, but seems reasonable.22:16
danwentwe'll get to horizon later in the agenda22:17
danwentNext topic: ryu controller plugin22:17
danwentthis poor guy has been sitting in review for weeks now.22:17
danwentI will give first round of reviews tonight22:17
danwentsince this patch breaks code out of openvswitch plugin to a shared dir22:18
danwentone point of feedback I wanted to ask the team22:18
danwentdoes it make sense to have one large "common" directory in quantum/plugins, or several more specific "common-X" directories?22:18
danwenttheir patch has an "openvswitch-common" dir I believe, but I was thinking more along the lines of a single common dir, that we tell packages to always include with every plugin.22:19
somikI prefer Apache commons style with one large common dir22:19
mandeepI agree22:19
*** edconzel has left #openstack-meeting22:19
danwentok, sounds good.  will give that feedback as part of review.22:19
danwentits worth noting that we also have several reviews languishing on gerrit: https://review.openstack.org/#q,status:open+project:openstack/quantum,n,z22:20
danwentincluding some bug fixes from Salv, and a build fix from Monty.22:20
danwentif you have time to knock out a few of these, it will clear some pipeline for the rush at the end.22:21
danwentNVP plugin:  bhall, is this close to being reviewed?22:21
bhalldanwent: getting there22:22
danwentOk, by thursday?22:22
bhallyeah, sounds likely22:22
danwentk, great22:23
danwentis debo-os here?22:23
danwentdoes anyone know status of quantum excercise script in devstack?22:24
danwentwould be nice to have people using that to validate changes when doing E-4 reviews22:24
*** rkukura has joined #openstack-meeting22:24
danwent#action #danwent contact #debo-os about progress integrating quantum script into devstack22:24
danwentOk, quantum manager unit tests are still in review in nova: https://review.openstack.org/385822:25
danwentlots of +1s, but we're looking for some final +2 from nova core devs22:25
danwentwwkeyboard:  any chance we're going to get melange coverage soon?22:25
wwkeyboarddanwent: I have no idea whats up with that.22:26
wwkeyboardI think jkoelker just added support for melange, but no special devstack tests22:26
danwentI think we need to stub out melange like we did for quantum.  currently the code coverage for the melange portion of quantum manager is quite low.22:26
danwentwwkeyboard: sorry, I was talking about unit tests in nova22:27
wwkeyboardTests for the melange_ipam_lib?22:27
jkoelkerwwkeyboard yea melange support is in devstack, still needs some love with configuring ip policies so it doesn't hand out the broadcast22:27
jkoelkerno excersice scripts yet, kinda waiting to see if we all go, devstack2 or not22:28
danwentjkoelker:  maybe create a wiki page with how to enable, or update the Quantum devstack wiki page?22:28
jkoelkerdanwent: I'll update the Quantum on, you just put m-svc and melange in your ENABLED_SERVICES22:29
danwentsounds simple enough.  thx.22:29
danwentok, is mjfork here?22:30
danwentI know nebula folks are hoping to do some quick clean-up of horizon + quantum integration22:30
danwentbut clock is really ticking on e-422:30
danwentmjfork:  any update on plans?22:31
danwentwhat is state of horizon branch-point/freeze?22:31
mjforki have code here that is shuold be ready for review22:31
mjforkI will read up on the gerrit workflow and get it submitted22:31
danwenta horizon review, I assume?22:31
mjforkyes.  the template used for selecting multiple networks was the edit rules support22:32
danwentmjfork:  sure.  feel free to ping netstack list if you have problems with workflow (or the main OS list)22:32
mjforkwill do. i may work on that a bit later.22:33
danwentmjfork:  k, great.  when you push the review, maybe drop a note to netstack list, as most of us won't get email for a horizon review22:33
mjforkdanwent: ok.22:33
danwentAn not to side-track things again, but as I mentioned, two new plugin proposals:22:33
danwentLocaweb contacted me last week.  Still haven't had a chance to look at code in detail though.22:34
danwentseems to have a lot of extensions.22:34
danwentand is based on OVS.22:34
danwentAlso, bigswitch: https://answers.launchpad.net/quantum/+question/18770022:34
salv-orlandodid they sorted the problem they were having with pushing into github? (I'm referring to locaweb)22:34
danwentmandeep, is that you, I believe?22:34
salv-orlandosorry I meant pushing into gerrit22:35
mandeepI am working in the bigswitch plugin22:35
danwentsalv-orlando: I think they figured it out.  They haven't pushed because I basically told them that I didn't think we'd have time to review it for E-4, so there was no rush22:35
salv-orlandodanwent: ok22:35
danwentmandeep:  good to have you on the team.22:35
mandeepdanwent: thanks ...22:35
*** phantomcircuit has quit IRC22:36
danwentping the netstack list if you need pointers on things.  developer documentation needs some work (please do improve it if you have a chance)22:36
mandeepdanwent: and now that I am on the project, I am happy to help with other bugfixes/reviews that need resources22:36
mandeepdanwent: will do22:36
danwentmandeep:  that would be great :)  As I said, that's the best way to encourage others to review your code22:36
mandeepdanwent: ;-)22:36
danwentOk, anything else on E-4?22:37
danwentgoing to be a stickler here, as I don't want another problematic release like e-3 :)22:37
*** zns has quit IRC22:37
danwentok, last topic before open discussion22:38
danwenttalked with the PPB earlier today about Quantum becoming a core project22:38
*** zns has joined #openstack-meeting22:38
danwentpeople were receptive, but wanted us to first come up with a concrete plan working with people from nova + melange on how quantum woudl interact with those projects moving forward22:39
danwentparticularly on the nova front, would quantum be replacing nova-network (and if so, when).  Would all network-related functionality like floating IPs, etc. move over the Quantum (and if so, when).22:39
wwkeyboardyea and soon? :)22:40
danwentI think it is likely that we will be approved (no one objected), but I think it was a good suggestion that we hash these details out first.22:40
salv-orlandodo you have a deadline for coming back with this plan?22:40
danwentnext tuesday :)22:40
danwentgood thing we don't have a bunch of code to write and review between now than then :P22:40
salv-orlandolots of things happening next tuesday. Including Napoli playing Chelsea (not that that should bother you on the other side of the Ocean though :))22:41
danwentI'm going to talk to jbryce if it seems like we need another week.22:41
danwentsalv: sounds like you have your priorities right :)22:41
danwentok, any questions about the application?22:41
danwentI'm going to ask vishy to help come up with a proposal that we can send out for comments.22:42
rkukuraIs there still talk of melange becoming part of quantum?22:42
danwentI don't think the PPB requires that we have this entirely locked down, but that we at least have a concrete proposal that all parties can agree to.22:42
danwentrkukura:  that's the second main question they have.22:43
danwentIt is possible to run Quantum without Melange (using QuantumManager + Nova IPAM), but I think the goal is to have Melange + Quantum more tightly integrated (perhaps to the point of being the same project, with a shared API)22:43
danwentwe were hoping to discuss this at the summit, but it sounds like we at least need to put the plan together soon than that.22:44
*** markvoelker has quit IRC22:44
danwentI think it makes sense from a tenant API perspective to have a single API, and hence to track them as largely one project.  Back-end implementations should still be fairly decoupled though, in my opinion.22:45
danwent#topic open discussion22:45
*** openstack changes topic to "open discussion"22:45
danwentanyone going to the cloud connect openstack party on wed night?22:45
danwentor maybe its that everyone who is going is currently attending cloud connect, and hence isn't at this meeting :)22:46
danwentany other open discussion?22:46
wwkeyboardI agree they should be more closely tied, the fractures of the data are not along the same lines we have split the services22:46
danwentwwkeyboard:  yeah, agreed.22:47
danwentok, thanks folks.  Have a good week, happy hacking (and reviewing!)22:47
*** zns has quit IRC22:47
*** openstack changes topic to "Status and Progress (Meeting topic: keystone-meeting)"22:47
wwkeyboardbut those changes are much bigger than before Tuesday.22:47
openstackMeeting ended Tue Feb 14 22:47:36 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-02-14-22.03.html22:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-02-14-22.03.txt22:47
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-02-14-22.03.log.html22:47
*** mandeep has quit IRC22:47
danwentwwkeyboard:  yes, I think its more about having a high-level plan by tuesday.  people were worried about what it meant for quantum to be core, if melange was still incubated, for example.22:48
*** mcohen_ has left #openstack-meeting22:48
wwkeyboardthe code seems to be there to run the QuantumManager with the nova_ipam_lib, but I have not tried it22:49
danwentthe exact details of how the APIs might merge would be something we could talk about at the summit.  the plan that they should merge is something that we should at least propose for next tuesday22:49
danwentwwkeyboard:  yeah, that is mostly how I run QuantumManager, as until the devstack integraiton of Melange, it was much easier than manually setting up Melange.22:50
danwentnova ipam has lots of limitations though, so its not the right long-term approach22:50
danwentand I'd prefer to limit the degress to which we have to support both IPAM approaches22:50
danwentmy original goal was to remove support for nova IPAM lib by the end of folsom, in favor of melange.22:51
wwkeyboardI agree with that, having only one would simplify those interfaces.22:52
wwkeyboardand be sufficient until we have to move to IPv822:52
*** davlap has quit IRC22:54
*** jlm^r has left #openstack-meeting22:56
*** bengrue has quit IRC22:56
*** bhall has quit IRC22:59
*** bengrue has joined #openstack-meeting23:00
*** ayoung has quit IRC23:00
*** nati2 has joined #openstack-meeting23:01
*** lloydde has quit IRC23:20
*** joesavak has quit IRC23:27
*** GheRivero_ has quit IRC23:35
*** Guest59459 has joined #openstack-meeting23:35
*** AlanClark has quit IRC23:38
*** Guest59459 has quit IRC23:44
*** dwcramer has quit IRC23:49
*** mattray has quit IRC23:51
*** phantomcircuit has joined #openstack-meeting23:53
*** jdg has left #openstack-meeting23:56

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