Tuesday, 2012-12-11

*** salv-orlando_ has joined #openstack-meeting00:00
*** annegentle__ has joined #openstack-meeting00:01
*** alexpilotti has quit IRC00:02
*** annegentle_ has quit IRC00:03
*** salv-orlando has quit IRC00:03
*** salv-orlando_ is now known as salv-orlando00:03
*** otherwiseguy has quit IRC00:06
*** annegentle_ has joined #openstack-meeting00:06
*** annegentle__ has quit IRC00:09
*** annegentle_ has quit IRC00:12
*** rafaduran has quit IRC00:18
*** stevemar has quit IRC00:21
*** dani4571 has quit IRC00:21
*** annegentle_ has joined #openstack-meeting00:24
*** mattray has quit IRC00:24
*** zykes- has quit IRC00:27
*** zykes- has joined #openstack-meeting00:28
*** vipul is now known as vipul|away00:30
*** anniec has joined #openstack-meeting00:31
*** salv-orlando has quit IRC00:34
*** vishy is now known as vishy_zz00:48
*** vipul|away is now known as vipul00:49
*** blamar has joined #openstack-meeting00:50
*** matiu has joined #openstack-meeting00:52
*** vishy_zz is now known as vishy00:52
*** metral has quit IRC00:54
*** martine_ has joined #openstack-meeting00:57
*** jcru is now known as jcru|away01:04
*** Kaiwei has quit IRC01:08
*** vishy is now known as vishy_zz01:14
*** vishy_zz is now known as vishy01:16
*** vishy is now known as vishy_zz01:23
*** jcru|away is now known as jcru01:26
*** newptone has joined #openstack-meeting01:28
*** vipul is now known as vipul|away01:29
*** vipul|away is now known as vipul01:29
*** anniec has quit IRC01:29
*** dprince has joined #openstack-meeting01:31
*** annegentle_ has quit IRC01:37
*** vishy_zz is now known as vishy01:37
*** jcru has quit IRC01:40
*** bearovercloud has left #openstack-meeting01:42
*** juice_ has quit IRC01:51
*** newptone_ has joined #openstack-meeting01:55
*** newptone has quit IRC01:57
*** Mandell has quit IRC02:01
*** arata has joined #openstack-meeting02:15
*** adjohn_ has quit IRC02:15
*** vishy is now known as vishy_zz02:19
*** colinmcnamara has quit IRC02:19
*** zhuadl has joined #openstack-meeting02:22
*** jcooley is now known as jcooley|away02:27
*** Edward_Zhang has joined #openstack-meeting02:28
*** markwash has quit IRC02:29
*** zhuadl has quit IRC02:42
*** zhuadl has joined #openstack-meeting02:42
*** wu_wenxiang has joined #openstack-meeting02:49
*** roadTripper has quit IRC02:52
*** jcooley|away is now known as jcooley03:01
*** nati_ueno has quit IRC03:04
*** novas0x2a|laptop has quit IRC03:08
*** danwent has quit IRC03:11
*** mlavalle has left #openstack-meeting03:12
*** shang has quit IRC03:22
*** mdomsch has joined #openstack-meeting03:25
*** arata has quit IRC03:36
*** colinmcnamara has joined #openstack-meeting03:41
*** markwash has joined #openstack-meeting03:42
*** shang has joined #openstack-meeting03:42
*** ayoung has quit IRC03:42
*** Linuturk_ has joined #openstack-meeting03:46
*** blamar has quit IRC03:47
*** dprince has quit IRC03:49
*** blamar has joined #openstack-meeting03:49
*** llu is now known as llu-away03:50
*** llu-away is now known as llu03:50
*** maurosr has quit IRC03:57
*** spzala has quit IRC04:03
*** markwash has quit IRC04:04
*** Mandell has joined #openstack-meeting04:11
*** Edward_Zhang has quit IRC04:11
*** zhuadl has quit IRC04:11
*** markwash has joined #openstack-meeting04:28
*** nati_ueno has joined #openstack-meeting04:38
*** stevebake has quit IRC04:40
*** markwash has quit IRC04:49
*** jdurgin1 has joined #openstack-meeting04:51
*** stevebake has joined #openstack-meeting05:03
*** gyee has quit IRC05:10
*** blamar has quit IRC05:11
*** martine_ has quit IRC05:22
*** juice_ has joined #openstack-meeting05:22
*** nati_ueno has quit IRC05:28
*** nati_ueno has joined #openstack-meeting05:28
*** Mandell has quit IRC05:31
*** jcooley is now known as jcooley|away05:41
*** adjohn has joined #openstack-meeting05:43
*** vishy_zz is now known as vishy05:50
*** vishy is now known as vishy_zz05:55
*** nati_ueno_2 has joined #openstack-meeting06:00
*** colinmcnamara has quit IRC06:01
*** nati_ueno has quit IRC06:03
*** anniec has joined #openstack-meeting06:09
*** davidkranz_ has joined #openstack-meeting06:16
*** davidkranz has quit IRC06:16
*** galthaus1 has joined #openstack-meeting06:21
*** galthaus has quit IRC06:21
*** anniec has quit IRC06:22
*** nati_ueno_2 has quit IRC06:46
*** nati_ueno has joined #openstack-meeting06:48
*** newptone_ has quit IRC07:05
*** newptone has joined #openstack-meeting07:06
*** garyk has joined #openstack-meeting07:07
*** soren_ has quit IRC07:11
*** soren_ has joined #openstack-meeting07:11
*** soren_ is now known as soren07:11
*** devananda has quit IRC07:13
*** salv-orlando has joined #openstack-meeting07:15
*** chunwang has joined #openstack-meeting07:17
*** llu has quit IRC07:29
*** salv-orlando has quit IRC07:36
*** afazekas has joined #openstack-meeting07:45
*** afazekas has quit IRC07:58
*** newptone has quit IRC08:00
*** rafaduran has joined #openstack-meeting08:01
*** llu has joined #openstack-meeting08:05
*** EmilienM has joined #openstack-meeting08:08
*** adam_g has quit IRC08:08
*** adam_g has joined #openstack-meeting08:08
*** adam_g has joined #openstack-meeting08:08
*** nati_ueno has quit IRC08:18
*** nati_ueno has joined #openstack-meeting08:20
*** afazekas has joined #openstack-meeting08:25
*** nati_ueno has quit IRC08:48
*** chunwang has quit IRC08:49
*** afazekas has quit IRC09:04
*** EmilienM has quit IRC09:06
*** juice_ has quit IRC09:07
*** EmilienM has joined #openstack-meeting09:16
*** mestery_ has joined #openstack-meeting09:16
*** mestery has quit IRC09:20
*** afazekas has joined #openstack-meeting09:20
*** darraghb has joined #openstack-meeting09:28
*** salv-orlando has joined #openstack-meeting09:31
*** wu_wenxiang has quit IRC09:32
*** mnewby has quit IRC09:36
*** adjohn has quit IRC09:37
*** derekh has joined #openstack-meeting09:41
*** mikal has quit IRC09:43
*** mikal has joined #openstack-meeting09:44
*** jhenner has joined #openstack-meeting09:49
*** salv-orlando has quit IRC09:52
*** garyk has quit IRC09:55
*** jdurgin1 has quit IRC10:23
*** maurosr has joined #openstack-meeting10:52
*** sandywalsh has joined #openstack-meeting11:43
*** EmilienM has quit IRC12:05
*** almaisan-away is now known as al-maisan12:23
*** garyk has joined #openstack-meeting12:24
*** martine has joined #openstack-meeting12:36
*** fifieldt has joined #openstack-meeting12:37
*** EmilienM has joined #openstack-meeting12:38
*** al-maisan is now known as almaisan-away12:38
*** roadTripper has joined #openstack-meeting12:45
*** dolphm has joined #openstack-meeting12:47
*** EmilienM has quit IRC12:57
fifieldtdoc team meeting in 3 minutes :)12:57
*** EmilienM has joined #openstack-meeting12:57
fifieldthello EmilienM12:58
*** annegentle_ has joined #openstack-meeting12:59
fifieldthello annegentle_12:59
annegentle_hi!12:59
fifieldthow are you?12:59
annegentle_good, you? It's cold here, like 22 F overnight which we hardly ever see. BR12:59
annegentle_My home office is not super well insulated let's just say :)13:00
fifieldtouch, that's a chilly morning13:00
EmilienMfifieldt: pong13:00
annegentle_EmilienM: welcome!13:00
EmilienMannegentle_: hey13:00
annegentle_Ok, shall we get started?13:00
fifieldtare we waiting for anyone in particular?13:01
EmilienMannegentle_: btw, I'm working on the basic install, I'll push it this week, with more and more stuffs13:01
fifieldtLorin, Razique, Daisy?13:01
EmilienMrelated to Quantum specially13:01
annegentle_fifieldt: no Daisy and no David cramer today, so maybe just look out for koolhead17, Lorin, Razique?13:01
annegentle_EmilienM: fantastic.13:02
annegentle_#startmeeting DocWebTeam13:02
openstackMeeting started Tue Dec 11 13:02:19 2012 UTC.  The chair is annegentle_. Information about MeetBot at http://wiki.debian.org/MeetBot.13:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:02
*** openstack changes topic to " (Meeting topic: DocWebTeam)"13:02
openstackThe meeting name has been set to 'docwebteam'13:02
annegentle_#link http://wiki.openstack.org/Meetings/DocTeamMeeting13:02
*** koolhead17 has joined #openstack-meeting13:03
annegentle_I probably should have looked up the last name for this meeting but oh well13:03
annegentle_welcome koolhead1713:03
annegentle_Ok, first item, actions from last meeting13:03
koolhead17hi annegentle_ fifieldt13:03
fifieldtargh!13:03
annegentle_#link http://eavesdrop.openstack.org/meetings/doc_web/2012/doc_web.2012-11-13-13.06.html13:04
* annegentle_ looks13:04
annegentle_ACTION: Anne to ask CI team if there's notification capability with a patch with DocImpact actually merges13:04
annegentle_Done, basically no. :)13:04
annegentle_I have been very specific on notifications on review.openstack.org Settings page and that helps me track API changes. But not code changes.13:04
annegentle_fifieldt: oh now I see why "argh!" :)13:05
annegentle_ACTION: fifieldt to send an followup email to the dev list thanking them for their response to the ":use docimpact" email13:05
fifieldtyes, unfortunately I didn't do this13:05
annegentle_fifieldt: you can do it this week, we're still seeing good response13:05
fifieldtthe good news is, it's still able to be done13:05
fifieldtyes miss13:05
annegentle_ACTION: Anne to send summary report of Google Analytics info to openstack-doc mailing list13:05
annegentle_Done. #link http://lists.openstack.org/pipermail/openstack-docs/2012-November/000304.html13:06
annegentle_http://lists.openstack.org/pipermail/openstack-docs/2012-November/000304.html13:06
annegentle_Der!13:06
annegentle_old paste :)13:06
annegentle_ACTION: Anne to investigate PDF file naming13:06
annegentle_Done. I'll report more on that during the Doc Tools portion.13:06
fifieldtcool13:07
annegentle_ACTION: Anne to send Dan Wendlandt a list of highest priority Quantum doc bugs13:07
annegentle_Done, Dan and team have been very responsive13:07
annegentle_ACTION: Anne to link to EmilienM's getting started doc from http://www.openstack.org/software/start/13:07
annegentle_Done, right EmilienM --13:07
annegentle_and last but not least.13:07
annegentle_ACTION: Anne to send email to Christian Berendt with proposal for moving forward with SLES OpenSuse install info13:07
annegentle_Done. This request was well-received, though I should follow up again.13:08
fifieldtooh, cool13:08
annegentle_They have an entire guide in German.13:08
fifieldt:O13:08
annegentle_yeah!13:09
fifieldtawesome13:09
annegentle_But I've asked them to integrate into the Adv. guide (The Install and Deploy one).13:09
fifieldtsounds good13:09
annegentle_so that there can be a separate SLES guide (like Ubuntu and RHEL/Centos/Fedora have)13:09
annegentle_Whew! That's all the Actions. Any questions?13:10
annegentle_I need to use my IRC nick for Action assignment, I had just used "Anne."13:10
annegentle_So! Let's switch topics to Doc Bug Squash Day13:10
fifieldt#link http://webnumbr.com/untouched-bugs-in-openstack-manuals-13:11
annegentle_thanks I was just looking for that fifieldt13:11
annegentle_I thought I went GREAT, thanks fifieldt for all your hard work13:11
annegentle_Only bit of follow up is to do a few more back ports I believe to stable/folsom.13:12
fifieldtindeed, I've not been doing well in that department13:12
annegentle_I'm in training all week this week (annegentle_ learns Python the Hard Way)13:12
fifieldtdo we need to go through say, the last month of commits, to check for backportability?13:12
annegentle_so realistically I won't get to it this week13:12
annegentle_fifieldt: yes we're nearly caught up but I keep having nagging feelings that it's not all there13:12
koolhead17annegentle_: fifieldt we need some cleanup as well :P13:12
annegentle_did anyone else sense that git's automatic merges were adding in spurious end tags?13:13
koolhead17from the docs and re drawing some of the diagrams/archs13:13
annegentle_or was that just me?13:13
fifieldtI only noticed that on that commit I commented on13:13
fifieldtit was strange13:13
* koolhead17 has not made commit for sometime13:13
fifieldtI guess that's an action for all - to check out for end tag weirdness ?13:14
annegentle_fifieldt: we merged in 15+ patches13:14
annegentle_fifieldt: yeah. I also was trying to ensure any given patch wasn't affecting the same file13:15
annegentle_koolhead17: get on it man! :) Just kidding.13:15
koolhead17annegentle_: :D13:15
annegentle_What should our plans be for Thursday's code bug squash?13:15
koolhead17was sick for few days. feeling great today13:15
annegentle_Ideas: Keep an eye out for DocImpact.13:15
koolhead17will do some bug fix13:16
annegentle_koolhead17: awesome. I had the worst upper respiratory infection last week but it's clearing now…13:16
koolhead17nice13:16
fifieldtouch13:16
fifieldtWell, we could also trawl the dev project's bugs looking for things which can be assisted by docs13:17
fifieldtbut that's a lot of work13:17
annegentle_fifieldt: wow yeah. But a good task for a bug day13:17
fifieldtand there might be more to gain by just fixing our existing bugs13:17
annegentle_fifieldt: yes absolutely13:17
koolhead17annegentle_: and api realted changes13:17
koolhead17and wiki page changes13:17
koolhead17achges13:17
koolhead17*changes13:18
annegentle_koolhead17: that's a good clean up -- wiki. Esp. before the migration13:18
annegentle_which is the next topic.13:18
annegentle_and I keep doing /topic but it's not changing the topic? Anyway.13:18
koolhead17annegentle_: did you like my idea of adding bold "only for A/B/C" release"13:18
fifieldttry #topic13:18
fifieldtrather than /topic13:18
koolhead17so people using that don`t get confused13:18
annegentle_#topic wiki migration13:18
*** openstack changes topic to "wiki migration (Meeting topic: DocWebTeam)"13:18
annegentle_thanks! fifieldt13:19
* fifieldt hat tip13:19
annegentle_Just wanted to put it on our agenda in case there are any questions13:19
*** EmilienM has quit IRC13:19
annegentle_I still need to respond to the question about the new contributor page13:19
annegentle_basically from talking to the CI team, waiting for the DNS switchover is the only likely "wait" period or delay for new contributors13:19
koolhead17annegentle_: i can work on the wiki page later tonight and add that extra line after going through all the pages about which version of OS it is supported13:19
annegentle_koolhead17: that would be great.13:20
annegentle_koolhead17 found that the "Flags" wiki page is for Essex13:20
annegentle_koolhead17: honestly you could just point it to the Folsom link13:20
annegentle_Add this code to wiki pages to indicate the page is outdated: <<Include(DeprecatedPage)>>13:20
annegentle_Since we don't really keep docs on the wiki, I'd prefer to prune more than keep.13:21
annegentle_I haven't done a wiki clean out for a while, so koolhead17 if you're up for it that would be great13:21
koolhead17annegentle_: yes i will do that as you suggested in your mail. and do you want me to add extra bold folt with one sence as well13:21
fifieldtawesome13:21
koolhead17saying limited to a/b/c release13:22
koolhead17i see some content for bexer release there13:22
koolhead17:)13:22
annegentle_koolhead17: see how http://wiki.openstack.org/Documentation just points to other places? That's the ideal to me.13:22
fifieldteek13:22
annegentle_koolhead17: yeah :) I found notes from an install fest from 2 years back13:22
koolhead17annegentle_: :D13:22
koolhead17so either clean up or add tag along with a warning saying its restricted to pervious version support13:23
annegentle_Ok, moving along if there's no questions?13:23
annegentle_koolhead17: yeah with a preference to just CLEAN :)13:23
fifieldtall good13:23
annegentle_cool13:23
annegentle_#topic Doc Tools Update13:23
*** openstack changes topic to "Doc Tools Update (Meeting topic: DocWebTeam)"13:23
annegentle_David Cramer had to get kids to school this morning so I got his report yesterday13:24
koolhead17annegentle_: cool. let me ping you later tonight with pages which i feel totally outdated13:24
koolhead17and we can take call on the same then13:24
annegentle_They work in 3 week sprints, and in this next sprint they are working on automatically generating site map.xml13:24
annegentle_#info Maven Plugin working on auto-generating sitemap.xml at build time13:24
annegentle_They're also moving into the OpenStack CI infrastructure13:24
annegentle_The other area of interest to us is the PDF output file naming.13:25
annegentle_They're fixing the "bug" that is in 1.6.0 that means we can't use it -- PDF files are named based on date metadata and we don't name our PDF files that way.13:25
annegentle_we name PDF files using the "release name" variable in the pom.xml.13:25
annegentle_So we should be good to go13:26
*** EmilienM has joined #openstack-meeting13:26
annegentle_but not until the release at the end of their 3 week sprint13:27
fifieldtok13:27
annegentle_when 1.6.1 comes out, we'll need to do a bunch of pom.xml work13:27
annegentle_to pull out the "postProcess" parts13:27
annegentle_since all that'll be automated13:27
annegentle_I hope to never open a bug again about the PDF link breaking!13:27
annegentle_and the site map.xml will help a bunch at release time, plus just make our google strength better13:28
koolhead17annegentle_: yeah :P13:28
annegentle_better/more accurate13:28
annegentle_ok snuck in one more agenda item before open discussion13:28
fifieldtbrilliant13:28
annegentle_#topic Outreach Program for Women13:28
*** openstack changes topic to "Outreach Program for Women (Meeting topic: DocWebTeam)"13:28
annegentle_Ok, we've been interviewing candidates and helping them with first patches.13:28
fifieldtoh cool!13:28
annegentle_Many are interested in coding, but I had a handful of doc candidates and I hope to get one!13:28
annegentle_I'll let you know if we get one! The selection process ends Dec 1113:29
annegentle_er. Today!13:29
annegentle_:13:29
annegentle_:)13:29
fifieldtyesterday ! :P13:29
koolhead17annegentle_: cool13:29
annegentle_I want to direct her mostly to API doc bugs, but that can change over the course of the internship.13:29
koolhead17so we will ahve some helping hand13:29
annegentle_The start period isn't until January.13:29
*** EmilienM has left #openstack-meeting13:30
koolhead17grr13:30
annegentle_koolhead17: yep! And we'll need to help her too - she's starting from zero OpenStack knowledge but already has a patch, it's a requirement of the program.13:30
koolhead17but if someone is really interested in contributing wont mind starting right away13:30
koolhead17IMHO13:30
annegentle_yeah I bet she will actually unless she has school obligations13:30
*** EmilienM has joined #openstack-meeting13:30
koolhead17annegentle_: cool.13:30
annegentle_The program is intended for students in the southern hemisphere at this time of year.13:30
annegentle_so she will be 40 hours a week on OpenStack docs.13:31
fifieldtI am on leave from work from ~today to January 14th ... I might have time to help13:31
* annegentle_ does a happy dance13:31
annegentle_fifieldt: fabulous!! I'll intro her when I can announce13:31
annegentle_Ok, good timing, at a half hour! Nice.13:31
annegentle_#topic Open discussion13:31
*** openstack changes topic to "Open discussion (Meeting topic: DocWebTeam)"13:31
fifieldtok13:31
koolhead17fifieldt: awesome :D13:32
fifieldtgot more for us Anne? or shall the rabble start pitching in now? :)13:32
koolhead17:D13:32
annegentle_sure!13:32
annegentle_:) That's all I got.13:32
fifieldtso, just throwing out one of the things from the ML13:32
fifieldtDo we want to try and set a Grizzly bug day13:32
fifieldtwell in advance13:32
fifieldtso we can all be free-ish13:32
koolhead17fifieldt: +113:33
koolhead17:D13:33
fifieldtto ensure that when grizzly goes live13:33
fifieldtthose listed against it's milestone are in13:33
fifieldts/those/those bugs13:33
koolhead17fifieldt: annegentle_  lets find someone who can help us with cleaning the arch diagram and some other stuff13:33
annegentle_fifieldt: great idea13:33
koolhead17am not sure in nova-network and nova-volume will b there in grizzly13:33
annegentle_fifieldt: do you have an idea of how much G1 is undocumented? I haven't really analyzed.13:34
fifieldtwell13:34
fifieldt#link https://launchpad.net/openstack-manuals/+milestone/grizzly13:34
fifieldtI've been not working on grizzly bugs13:34
koolhead17some features like nova-cells and also if vendors want we can add there drivers in cinder doc13:34
fifieldtin preference for ones that affect folsom13:34
annegentle_fifieldt: wow, 32 g1 doc tasks13:34
annegentle_koolhead17: did nova cells make it in finally? It didn't make G113:35
koolhead17annegentle_: it will to G hopefuuly :P13:35
annegentle_#info 32 G1 doc tasks recorded, ready for someone to work on13:35
* fifieldt is using cells in production :P13:35
annegentle_fifieldt: nice :)13:35
koolhead17fifieldt: :D13:35
koolhead17fifieldt: so can we add that somewhere to be added in the doc13:36
*** martine has quit IRC13:36
annegentle_I did want to mention that we'll try for an Operators Doc Sprint in Februrary 2014.13:36
koolhead17and removing many other stuff13:36
annegentle_eek! 2013!13:36
fifieldtalready got a bug lodged koolhead1713:36
fifieldttehehe13:36
koolhead17annegentle_: lets do that.13:36
koolhead17fifieldt: waoo cool13:36
fifieldtkoolhead17, https://bugs.launchpad.net/bugs/107566913:36
uvirtbotLaunchpad bug 1075669 in openstack-manuals "grizzly: Support for cells in Compute (nova)" [Undecided,New]13:36
annegentle_#action annegentle_ to write a proposal to Foundation requesting funding of Doc Sprint in Feb 2013 including Adam Hyde as facilitator13:37
annegentle_So how can we time a date in advance? Is it right around G2 that we'll want another doc bug sprint?13:37
fifieldt#link http://wiki.openstack.org/GrizzlyReleaseSchedule13:38
fifieldtI think after G313:38
*** topol has joined #openstack-meeting13:38
annegentle_Was a Tuesday a good day of the week? I liked it.13:38
fifieldtbecause there's a chance things change13:38
fifieldtI've already seen some options that changed names13:38
fifieldtin processing DocIMpacts13:38
koolhead17fifieldt: yeah correct13:39
fifieldtso we don't want to do it too early, imo13:39
annegentle_fifieldt: ok, that makes sense then.13:39
annegentle_fifieldt: it'll run up into that Doc Sprint proposed though, but maybe that's ok13:39
annegentle_and good timing even13:39
koolhead17annegentle_: so when are you thinking to have it after G313:39
annegentle_or what about Tues Feb 19, right before G3?13:40
*** minute has joined #openstack-meeting13:40
annegentle_the proposal for the Doc sprint is Feb 25-2913:40
fifieldtthat could work -13:40
annegentle_G3 is Feb 2813:40
fifieldtget a head start on doc bugs13:40
*** blamar has joined #openstack-meeting13:40
koolhead17yes works for me13:41
fifieldtthen do the doc sprint13:41
annegentle_it's tight but gives us good data13:41
annegentle_cool13:41
* annegentle_ needs to get that proposal done!13:41
annegentle_Okay, what else is going on?13:41
* annegentle_ thinks13:41
*** blamar has quit IRC13:41
annegentle_I'll try to do a doc status report tomorrow for the week13:42
annegentle_Seriously, great work on the doc bug day. That was fantastic.13:42
fifieldtbugs <100 before end of year?13:42
annegentle_fifieldt: YES.13:42
*** blamar has joined #openstack-meeting13:42
fifieldthow ? :D13:42
*** dprince has joined #openstack-meeting13:43
annegentle_fifieldt: let's see if the Intern can help in Dec… and I'll rally some groups at the Rack.13:43
fifieldt:)13:43
koolhead17annegentle_: cool13:43
annegentle_and? Maybe your mailing list post will inspire?13:43
fifieldthmm, maybe we need another mailing list post for inspiration13:43
koolhead17annegentle_: which mail?13:43
koolhead17:P13:43
annegentle_AT&T wants to contribute more, how can I match doc bugs with a person there?13:43
fifieldtasking for help from those devs in the know13:43
fifieldtwhat are they interested in?13:44
annegentle_fifieldt: your note of gratitude for using DocImpact13:44
fifieldtyup13:44
annegentle_fifieldt: not sure, that's a good starting question.13:44
koolhead17also here in meetup am expecting some contribution starting to happen soon13:44
koolhead17:)13:44
koolhead17met som eenthu folks/kids13:44
koolhead17*enthu13:44
annegentle_koolhead17: oh yeah?13:44
fifieldtAT&T:  "a developer-centric cloud." The service will be focused on providing developers of cloud apps low-cost entry into AT&T's hosting services, and a choice of public or private access, as well as an option for "bare-metal" provisioning of hardware for developers requiring specific server configurations, and options for cloud storage, network configuration and monitoring.13:44
annegentle_koolhead17: do we need a better "here's how you get started with docs?"13:45
koolhead17annegentle_: i will blog one tonight :P13:45
annegentle_fifieldt: yep, they're operating plenty… Essex I believe.13:45
annegentle_koolhead17: oh good idea13:45
fifieldtthey're involved in the bare metal stuff in grizzly?13:45
koolhead17and also planning to get the same published in some other blog pages too13:45
koolhead17fifieldt: it be great if they can help us including that part in our doc13:46
fifieldtaye13:46
fifieldtanyway, we have a wall of work13:46
fifieldtso they can work on their interest :)13:46
fifieldtThat's all from me13:46
koolhead17:P13:46
annegentle_okay, cool.13:47
annegentle_I'm good to go -- call it a wrap!13:47
annegentle_#endmeeting13:47
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"13:47
openstackMeeting ended Tue Dec 11 13:47:24 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/docwebteam/2012/docwebteam.2012-12-11-13.02.html13:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/docwebteam/2012/docwebteam.2012-12-11-13.02.txt13:47
openstackLog:            http://eavesdrop.openstack.org/meetings/docwebteam/2012/docwebteam.2012-12-11-13.02.log.html13:47
annegentle_thanks everyone13:47
fifieldtthank you13:47
* annegentle_ drives in to work now13:47
fifieldthave a great day :)13:48
*** annegentle_ has quit IRC13:48
*** koolhead17 has left #openstack-meeting13:50
*** garyk has quit IRC13:51
*** ewindisch has quit IRC14:05
*** afazekas has quit IRC14:05
*** fifieldt has quit IRC14:09
*** blamar has quit IRC14:17
*** annegentle_ has joined #openstack-meeting14:20
*** markmcclain has joined #openstack-meeting14:22
*** annegentle_ has quit IRC14:28
*** blamar has joined #openstack-meeting14:29
*** jaypipes has joined #openstack-meeting14:30
*** blamar has quit IRC14:30
*** ayoung has joined #openstack-meeting14:37
*** radez_g0n3 is now known as radez14:38
*** annegentle_ has joined #openstack-meeting14:43
*** jiajun has quit IRC14:48
*** mtreinish has joined #openstack-meeting14:49
*** garyk has joined #openstack-meeting14:50
*** colinmcnamara has joined #openstack-meeting14:51
*** devananda has joined #openstack-meeting14:54
*** jcru has joined #openstack-meeting14:55
*** blamar has joined #openstack-meeting14:58
*** devananda has quit IRC14:58
*** devananda has joined #openstack-meeting14:59
*** blamar_ has joined #openstack-meeting14:59
*** dkehn has joined #openstack-meeting15:00
*** blamar has quit IRC15:02
*** blamar_ is now known as blamar15:02
*** spn has joined #openstack-meeting15:05
*** galthaus1 has quit IRC15:06
*** spn has quit IRC15:06
*** mattray has joined #openstack-meeting15:07
*** spn has joined #openstack-meeting15:07
*** Linuturk_ is now known as Linuturk15:13
*** colinmcnamara has quit IRC15:13
*** almaisan-away is now known as al-maisan15:13
*** colinmcnamara has joined #openstack-meeting15:14
*** dolphm has quit IRC15:15
*** srini_g has joined #openstack-meeting15:19
*** colinmcnamara has quit IRC15:20
*** cp16net is now known as cp16net|away15:22
*** srini_g has quit IRC15:22
*** spn has quit IRC15:22
*** spn has joined #openstack-meeting15:23
*** dprince has quit IRC15:24
*** mattray has quit IRC15:24
*** cp16net|away is now known as cp16net15:24
*** luis_fdez has joined #openstack-meeting15:25
*** minute has quit IRC15:25
*** jd__ has quit IRC15:25
*** minute has joined #openstack-meeting15:26
*** jd__ has joined #openstack-meeting15:26
*** spn has quit IRC15:28
*** spn1 has joined #openstack-meeting15:28
*** spn1 has quit IRC15:28
*** minute has quit IRC15:30
*** jd__ has quit IRC15:30
*** zbitter has joined #openstack-meeting15:32
*** minute has joined #openstack-meeting15:32
*** jd__ has joined #openstack-meeting15:32
*** zaneb has quit IRC15:35
*** rnirmal has joined #openstack-meeting15:36
*** joe5081 has joined #openstack-meeting15:43
*** jcru has quit IRC15:43
*** joe5081 has quit IRC15:45
*** EmilienM has quit IRC15:46
*** jcru has joined #openstack-meeting15:47
*** dolphm has joined #openstack-meeting15:49
*** stevemar has joined #openstack-meeting15:51
*** mattray has joined #openstack-meeting15:51
*** pnavarro has joined #openstack-meeting15:52
*** dwcramer has quit IRC15:52
*** ewindisch has joined #openstack-meeting15:56
*** primeministerp has joined #openstack-meeting15:58
primeministerp#startmeeting hyper-v15:58
openstackMeeting started Tue Dec 11 15:58:41 2012 UTC.  The chair is primeministerp. Information about MeetBot at http://wiki.debian.org/MeetBot.15:58
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:58
*** openstack changes topic to " (Meeting topic: hyper-v)"15:58
openstackThe meeting name has been set to 'hyper_v'15:58
*** dprince has joined #openstack-meeting15:58
primeministerphmm, my clock is 2 min off15:58
primeministerppnavarro: how's it going15:59
primeministerpgoing to wait a couple more minutes for everyone to join15:59
pnavarroHi primeministerp !15:59
primeministerppnavarro: how's it going15:59
primeministerppnavarro: any progress on the cinder commands not responding16:00
pnavarroi'm doing well, and you?16:00
primeministerppnavarro: a bit tired, we got a dog this weekend16:00
pnavarroa dog ! oufff16:00
pnavarroa new baby16:00
primeministerppnavarro: and I'm coming off a lot of hours last week w/  the cloudbase team16:00
primeministerppnavarro:  yes, lucy the daschund16:00
*** topol has quit IRC16:01
primeministerppnavarro: so I saw that alex is going to create an installer for the cinder bits16:01
pnavarroabout cinder, I couldn't take a look this evening16:01
primeministerppnavarro: ok16:01
primeministerppnavarro: do we at least know if it's a bug?16:01
pnavarrowell, It looks like a bug, but I'm not sure16:02
primeministerpno alex yet16:04
*** juice_ has joined #openstack-meeting16:04
primeministerppnavarro: i just pinged tavi16:04
primeministerppnavarro: we made some progress last week16:04
primeministerpwe refactored all the puppet bits I started16:05
*** ociuhandu has joined #openstack-meeting16:05
primeministerpociuhandu: tavi!16:05
ociuhanduhello all16:05
primeministerpociuhandu: is alex going to join as well16:05
ociuhanduyes, he'll be joining in a couple of minutes16:05
*** alexpilotti has joined #openstack-meeting16:07
alexpilottihi guys16:07
pnavarrohi alexpilotti16:07
alexpilottisorry for being late!16:07
primeministerphey no worries16:08
primeministerpso16:08
primeministerpi guess we'll offically begin16:08
alexpilottimy Colloquy was disconnected, can u plz tell me what's teh current topic? :-)16:08
primeministerp#topic cinder16:08
*** openstack changes topic to "cinder (Meeting topic: hyper-v)"16:08
alexpilotticool16:08
primeministerppnavarro: and i were discussing the bug16:08
primeministerpalexpilotti: from the email16:08
alexpilottiwhat bug? :-)16:08
primeministerpalexpilotti: i wanted to confirm it's fit's a bug or not16:09
primeministerpalexpilotti: the non functioning cinder commands16:09
* primeministerp looks at the email16:09
primeministerpalexpilotti: that you found16:09
alexpilottisure16:09
*** EmilienM has joined #openstack-meeting16:10
alexpilottiit was a question. How to remove a cinder-volume service16:10
alexpilottithe case is simple:16:10
primeministerpalexpilotti: removing existing volumes16:10
alexpilottiyou run devstack16:10
primeministerpalexpilotti: is it definately a bug?16:10
alexpilottiok, I'm missing something :-)16:11
primeministerpalexpilotti: the email you sent16:11
alexpilottithe email I sent today?16:11
primeministerpOn the controller I didn't find a way to remove an existing cinder-volume service except editing the db.16:11
primeministerpyes16:11
alexpilottiyep16:11
alexpilottiso the case is simple:16:11
alexpilottiyou have e.g. devstack16:11
primeministerpi just want clarity on what the problem is16:12
alexpilottiyou stop the cinder-volume service16:12
alexpilottiyou add  cinder-volume running on Windows Storage16:12
alexpilottion the controller you'll still see both services16:12
*** martine has joined #openstack-meeting16:12
alexpilottiso if you run: cinder volume create 116:12
primeministerpahh gotcha16:12
alexpilottiit will try to use either one16:13
primeministerpit will try to create on the wrong vol server16:13
primeministerpi get it16:13
primeministerpnow16:13
primeministerpi thought it was on the target end16:13
primeministerpsomething in pnavarro bits16:13
primeministerpthat wasn't functioning16:13
alexpilottino, nothing on our side16:13
primeministerpo16:13
primeministerpgreat16:13
primeministerppnavarro: you're off the hook16:13
primeministerp;)16:13
pnavarrothanks16:13
primeministerphaha16:13
alexpilottipnavarro: do you have any clue? I'm going to ask the cinder guys otherwise16:13
primeministerpalexpilotti: any timeline on the installer?16:14
alexpilottilol16:14
primeministerpalexpilotti:sorry16:14
pnavarrosorry alex, no idea what's the problem...16:14
alexpilottiah yep. I'm going to release the installer today16:14
primeministerpalexpilotti: awesome16:14
alexpilottifor cinder-volume only, that's what we need16:14
primeministerppnavarro: no problem on our end16:14
primeministerppnavarro: just didn't automatically remove the linux service16:14
alexpilottiIMO we can leave out cinder-api and cinder-scheduler16:14
primeministerppnavarro: if i understand correctly16:14
primeministerpalexpilotti: why?16:15
*** hemna_ has joined #openstack-meeting16:15
alexpilottibecause I had some issues on running them with the latest Grizzly bits on Windows16:15
primeministerpalexpilotti: *nod*16:15
alexpilottiand because those services run usually on a controller, not on each volume node16:16
alexpilottilet's say that "cinder-volume" is for Cinder what "nova-compute" is for Nova16:16
primeministerpi get it16:16
primeministerpthx16:16
primeministerpok16:16
primeministerpguess we'll move on16:17
alexpilottiof course we want to have all the rest on WIndows as well ;-)16:17
alexpilottisure16:17
primeministerp;)16:17
primeministerp#topic quantum16:17
*** openstack changes topic to "quantum (Meeting topic: hyper-v)"16:17
alexpilottiahem16:17
primeministerp?16:17
alexpilottinext topic? :-)16:17
primeministerpquantum?16:17
primeministerpwas there something i missed?16:17
alexpilottikidding, due to the CI stuff I was not able to do more than looking at pnavarro's bits16:18
alexpilottipnavarro: do you have anything new?16:18
primeministerpalexpilotti: i was asking mostly for pnavarro's input16:18
primeministerppnavarro: you're on the hook again16:18
primeministerp;)16:18
alexpilottilol16:18
pnavarroalexpilotti: agent is running ok, i'm still testing agent- plugin communication16:18
alexpilottipnavarro: great!16:19
primeministerppnavarro: great16:19
pnavarroso, I'd appreciate any help16:19
alexpilottipnavarro: this week, I swear, I'm working on it :-)16:19
pnavarroperfect16:19
primeministerpand alexpilotti you'll start work again shortly16:19
primeministerpalexpilotti: will we be able to account for the nvgre bits16:20
alexpilottipnavarro: on the agent side, what hyper-V specific features did you test already?16:20
ociuhandusorry guys, i have to run now, will ba back in about 45 minutes16:20
ociuhanduprimeministerp: i'll ping you when i get back16:21
primeministerpociuhandu: ok, let's touch base re: ci16:21
primeministerpociuhandu: great16:21
pnavarroI tested ports updates16:21
ociuhandubye all & yalk to you later16:21
primeministerppnavarro: nice16:22
alexpilottipnavarro: this time, we should think about a FakePlugin since we don't have the rush16:22
pnavarroalexpilotti: yeah16:22
primeministerpalexpilotti: and by fake plugin?16:23
primeministerpfor my ignorance16:23
primeministerpplease16:23
primeministerpsame as the wmi test interface16:23
primeministerpbut for quantum only?16:23
alexpilottibasically a class that emulates the wmi calls, by creating an asbtarction layer on them16:23
primeministerpgotcha16:24
alexpilottiso in the code, instead of calling WMI we call this new layer16:24
*** gyee has joined #openstack-meeting16:24
alexpilottiwhich can be replaced by a fake one during tests16:24
alexpilottiwe have to do the same for Nova and Cinder of course16:24
pnavarroalexpilotti the wmi library creator gave you some hint about that?16:24
alexpilottipnavarro: nope :-(16:25
alexpilottipnavarro: but if we wrap all the calls we are fine16:25
primeministerpalexpilotti: aren't you wrapping them 2x then?16:25
alexpilottipnavarro: this IMO will not reach the level of coverage we had with the dynamic mocks, but it's ok16:25
alexpilottiprimeministerp: yes, no comment16:26
primeministerphahaha16:26
alexpilottiindeed we are not really wrapping them twice16:26
*** otherwiseguy has joined #openstack-meeting16:26
alexpilottithere while be a lower level fine grained layer16:26
primeministerp*nod*16:26
primeministerphehe16:26
alexpilottiand a high level (the driver itself)16:26
primeministerpfair enough16:27
alexpilottithe point is that we should test the low level one as well… that's the funny part16:27
primeministerpalexpilotti: maybe we can leverage the new relationship w/ tom for assistance16:27
primeministerpw/ getting you information16:27
primeministerpresources16:27
*** ewindisch_ has joined #openstack-meeting16:27
alexpilottiunfortunately the way in which WMI is done is the problem16:28
*** ewindisch_ has quit IRC16:28
alexpilottithe amazing flexibility it provides becomes a huge PINTA for testing16:28
primeministerp*nod*16:28
*** ewindisch has quit IRC16:28
primeministerpwe definately don't have it easy16:29
pnavarroyeah, we can't use mocks library16:29
primeministerpso why not specifically16:29
primeministerpthe nature of having to test the network itself?16:29
*** gongysh has quit IRC16:30
alexpilottisetting up the tests will be relatively easy, as we can take the OVS ones as a reference16:30
alexpilottipnavarro: is your repo updated?16:30
pnavarroyeah16:31
pnavarroalexpilotti: I've added the binary16:31
alexpilottipnavarro: this it the latest plugin? https://github.com/pnavarro/quantum/tree/master/quantum/plugins/windowsvswitch16:31
pnavarroyes16:31
primeministerp#link https://github.com/pnavarro/quantum/tree/master/quantum/plugins/windowsvswitch16:31
pnavarroIf you don't like the name, we can change it16:32
*** topol has joined #openstack-meeting16:32
primeministerppnavarro: name doesn't bother me16:32
alexpilottipnavarro: I'd go with hypervswitch, but that's a detail :-)16:32
pnavarrooki doki16:32
primeministerppnavarro: he's a bit right there16:32
primeministerpalexpilotti: ... and your the purist16:33
primeministerp;)16:33
primeministerpok16:33
primeministerpshould we move on?16:33
primeministerpto ci talk?16:33
alexpilottipnavarro: I'm loking at the utils.py, good work!16:33
pnavarrothanks alexpilotti !16:34
primeministerp#topic CI16:34
*** openstack changes topic to "CI (Meeting topic: hyper-v)"16:34
primeministerpalexpilotti: this will be quick16:34
primeministerpsince i'll have to catch up w/ tavi later16:34
alexpilottilol16:34
primeministerpbut I figure we'll coordinate16:35
primeministerpthen16:35
alexpilottisure, ociuhandu will be back in ca 1hr16:35
primeministerpi'm assuming you guys haven't picked up yet16:35
pnavarroi'll read the logs later, I have to go16:35
primeministerpfrom where we left off16:35
primeministerppnavarro: thanks for everything16:35
pnavarrociao !16:35
alexpilottiI resumed the work this afternoon (aka 2 hours ago)16:35
primeministerpalexpilotti: on the scripting?16:36
*** vishy_zz is now known as vishy16:36
alexpilottipnavarro: hasta luego!16:36
alexpilottiprimeministerp: yep, I'm polishing up the scripts for the controller16:36
primeministerpalexpilotti: ok16:36
primeministerpalexpilotti: i figured out why my post script wasn't running out of the preseed16:37
primeministerpalexpilotti: fixed and going test16:37
alexpilotticool16:37
primeministerpalso hoping to resume work on the windows unatted bit16:37
primeministerps16:37
primeministerpnext couple of days are going to be tough for me16:37
primeministerpdue to meetings16:37
alexpilottiprimeministerp: BTW VPN works fine also from this side of the "pond" :-)16:37
primeministerpand now the move16:37
primeministerpalexpilotti: great16:37
primeministerpalexpilotti: i resurected my asa at home16:38
primeministerpI'm going to put a static tunnel up for me16:38
primeministerpnow that I have to move16:38
primeministerpmy office16:38
primeministerpalso ordered sound protective bluetooth headset for working in the dc16:38
primeministerpanyway16:39
primeministerpo16:39
primeministerpmordred: ping16:39
primeministerpmordred: whats the best way for us to start the process of integration our hyper-v work16:39
primeministerpalexpilotti: i was thinking we can start adding the bits we've created16:40
*** pnavarro has quit IRC16:40
primeministerpalexpilotti: that way we don't dump a whole lot on top16:40
primeministerpalexpilotti: and can increment at a minimum the working parts16:40
primeministerpalexpilotti: any thoughts16:40
primeministerpalexpilotti: also then we'd be working out of git16:40
primeministerpwell mordred might be busy i'll try to follow up w/ him later16:41
alexpilottiprimeministerp: Since finishing the "layer 1" stuff is almost done, can we set up a meeting wit mordred this or next week?16:42
primeministerpok16:42
primeministerpalexpilotti: that's my thoughts16:43
primeministerpalexpilotti: i'll work on that16:43
alexpilotticool16:43
primeministerpalexpilotti: and let's plan on having a skype when tavi gets back16:43
primeministerpjust to touch base16:43
alexpilotticoo, I'll be here as well16:43
primeministerpok great16:43
primeministerpi've got to head in into the office16:43
primeministerpso i'll be offline for a while16:43
primeministerpok closing the meeting16:43
primeministerp#endmeeting16:44
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"16:44
openstackMeeting ended Tue Dec 11 16:44:03 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:44
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2012/hyper_v.2012-12-11-15.58.html16:44
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2012/hyper_v.2012-12-11-15.58.txt16:44
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2012/hyper_v.2012-12-11-15.58.log.html16:44
alexpilottiok bye!16:44
*** al-maisan is now known as almaisan-away16:45
*** EmilienM has left #openstack-meeting16:46
*** jhenner has quit IRC16:48
*** hemna_ has quit IRC16:53
*** roadTripper has quit IRC16:54
*** primeministerp has quit IRC16:56
*** adjohn has joined #openstack-meeting16:57
*** mnewby has joined #openstack-meeting16:57
*** danwent has joined #openstack-meeting17:00
*** hemna_ has joined #openstack-meeting17:06
*** vishy is now known as vishy_zz17:07
*** markwash has joined #openstack-meeting17:15
*** metral has joined #openstack-meeting17:21
*** metral has quit IRC17:23
*** metral has joined #openstack-meeting17:23
*** vishy_zz is now known as vishy17:24
*** jcru is now known as jcru|away17:26
*** dwcramer has joined #openstack-meeting17:26
*** jcru|away is now known as jcru17:26
*** dwcramer has quit IRC17:32
*** kaganos has joined #openstack-meeting17:37
*** Mandell has joined #openstack-meeting17:43
*** dwcramer has joined #openstack-meeting17:47
*** marek__ has joined #openstack-meeting17:52
*** kwss has joined #openstack-meeting17:53
*** hemna has quit IRC17:54
*** joe5081 has joined #openstack-meeting17:55
*** jcru has quit IRC17:56
*** rafaduran has quit IRC17:57
*** EmilienM has joined #openstack-meeting17:57
*** spzala has joined #openstack-meeting17:57
*** colinmcnamara has joined #openstack-meeting17:58
*** kaganos has quit IRC17:58
*** henrynash has joined #openstack-meeting17:59
*** annegentle_ has quit IRC17:59
*** brich has joined #openstack-meeting17:59
ayoung #startmeeting keystone18:00
ayoung#startmeeting keystone18:00
openstackMeeting started Tue Dec 11 18:00:12 2012 UTC.  The chair is ayoung. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: keystone)"18:00
openstackThe meeting name has been set to 'keystone'18:00
gyeeo/18:00
henrynashhi18:00
kwsshello18:00
ayoungdolphm is going to away for most, but should be joining us at the end18:00
ayoungAnd I don't see heckj around18:01
*** dwchadwick has joined #openstack-meeting18:02
ayoung#link http://wiki.openstack.org/Meetings/KeystoneMeeting18:02
henrynashayoung: I added the item of a reference implementation for groups to the agenda18:02
*** hemna has joined #openstack-meeting18:02
ayoungAlthough we are going to move the discussion of Module Refactoring to the end, to hopefully get dolph's input18:02
ayounghenrynash, sounds goodf18:02
*** hemna_ has quit IRC18:03
ayoungWe should also probably start doing a review of previous minutes in these, to make sure old "todo" items are covered.  But we had no #actions from last time18:03
dwchadwickDid we cover all the items from last week?18:04
*** colinmcnamara has quit IRC18:04
ayoungdwchadwick, lets see...18:04
ayoung#link http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-11-27-18.10.html18:04
*** nachi has joined #openstack-meeting18:05
*** nachi_ has joined #openstack-meeting18:05
ayoungI'd have to dig out the revision history in the Wiki to see what the agenda was.18:05
dwchadwicktunnel18:05
*** kaganos has joined #openstack-meeting18:05
henrynashdwchadwick: do you see the light at the end of the tunnel or is that a train going your way :-)18:06
ayoungold agenda was18:06
ayoungHigh priority bugs or immediate issues?18:06
ayoungOpen discussion18:06
ayoungGroups vs. attribute mappings18:06
ayoungAdding IDPs to service catalog18:06
ayoung    https://blueprints.launchpad.net/keystone/+spec/adding-idps-to-service-catalog18:06
ayoungDelegation18:06
ayoung    http://wiki.openstack.org/keystone/Delegation18:06
ayoungStatus/Timeframe of Federation integration18:06
ayoung    http://wiki.openstack.org/Keystone/Federation/Blueprint18:06
ayoung    https://blueprints.launchpad.net/keystone/+spec/adding-idps-to-service-catalog18:06
ayoungI think we covered all that.18:06
*** markvoelker has joined #openstack-meeting18:06
ayoungOK. let start with18:06
*** colinmcnamara has joined #openstack-meeting18:06
ayoung#topic High priority bugs or immediate issues18:06
*** openstack changes topic to "High priority bugs or immediate issues (Meeting topic: keystone)"18:06
ayoung2 new (untriaged) bugs, neither seem high priority:  One is a test bug the other is  https://bugs.launchpad.net/keystone/+bug/108723418:07
uvirtbotLaunchpad bug 1087234 in keystone "It should be possible to delete a tenant by its name" [Undecided,New]18:07
ayoungRFE18:07
*** dwchad2 has joined #openstack-meeting18:08
ayoungLooking at the high priority bugs:18:08
ayoung0 critical18:09
ayoung#link https://bugs.launchpad.net/keystone/+bugs?search=Search&field.importance=Critical&field.status=New&field.status=Incomplete&field.status=Confirmed&field.status=Triaged&field.status=In+Progress&field.status=Fix+Committed18:09
ayoung15 High18:09
ayounghttps://bugs.launchpad.net/keystone/+bugs?search=Search&field.importance=High&field.status=New&field.status=Incomplete&field.status=Confirmed&field.status=Triaged&field.status=In+Progress&field.status=Fix+Committed18:09
*** dwchadwick has quit IRC18:10
henrynashayoung: targets for bug squashing on Thursday?18:10
*** EmilienM has quit IRC18:10
ayounghenrynash, good question18:10
*** EmilienM has joined #openstack-meeting18:11
henrynashI'be got some IBMers coming up to speed on keystone…so could direct them at whatever we select18:11
ayounghenrynash, none of the high look like something we can just "knock out."18:11
ayounghenrynash, potentially this one https://bugs.launchpad.net/keystone/+bug/104069618:11
uvirtbotLaunchpad bug 1040696 in keystone "invalid EC2 signature authentication for requests without a port" [High,Triaged]18:12
ayoungOK,  let me give a quick status on the refactoring and then we can table the rest of the discussion until dolph is present18:12
ayoung#topic Module Refactoring18:12
henrynashand https://bugs.launchpad.net/keystone/+bug/106173818:12
*** openstack changes topic to "Module Refactoring (Meeting topic: keystone)"18:12
uvirtbotLaunchpad bug 1061738 in keystone "create_service() returns 500 Internal Server Error when bad keyword arg (XML only)" [High,Triaged]18:12
ayounghenrynash, yeah, that would be a good one to look at, too18:13
ayoungOk,  the service.py file was too fat18:13
henrynash:-)18:13
ayoungand, it was not quite possible to move the TokenController into the token module package  (keysteon/token) due to a circular dependency18:13
gyeeayoung, looks like you are doing massive refactoring, should I start on the token work now or wait for you?18:14
ayoungso I've been shuffling files around18:14
gyeeotherwise, one of us well be busy rebasing18:14
gyeewill18:14
ayounggyee, I think we all need to focus on understanding this refactoring before doing any more work on modules18:14
gyeek18:14
ayoungreview is this one18:14
ayoung#link https://review.openstack.org/#/c/17782/18:14
gyeeI see a cross from dolph18:15
henrynashayoung: agreed (although I have just about completed the changes for a reference implementation of groups on the server side - so refactoring, I gotta do!18:15
ayounggyee, right, which is why we need him here to discuss18:15
ayounghenrynash, if you push your changes as a WIP review, I can give you guidance how to reshuffle based on the refactoring18:16
henrynashayoung: great, thx18:16
ayoungOK,  keeping that in mind, let's table the rest of the discussion on the refactoring, and move on.18:16
henrynashayoung: you mean a git review -D ?18:16
ayounghenrynash, yes18:17
ayoungget review -w18:17
*** roadTripper has joined #openstack-meeting18:17
henrynashayoung: ok, thx18:17
ayoungit will show up as a WIP.  We'll be able to see it, but it won't be in danger of getting merged18:17
*** darraghb has quit IRC18:17
ayoung#topic Groups/Attributes18:18
*** openstack changes topic to "Groups/Attributes (Meeting topic: keystone)"18:18
henrynash(assuming we want the defence design in…but that's another topic)18:18
*** kaganos has quit IRC18:18
henrynashahh, I mean, this topic :-)18:18
ayoung#action henrynash submites WIP review of reference impl thus far18:18
ayounghenrynash, the floor is yours.  What are the issues?18:18
*** nachi has quit IRC18:19
henrynashso the fundamental question is whether it is in our best interest to start with a defence design based on current RBAC capabilities18:19
henrynash(sorry, I meant a "reference" design)18:19
*** malini has joined #openstack-meeting18:20
henrynash…and then start plugging in the attribute capabilities and cut out the bits of the reference design no lover needed18:20
henrynash(longer)18:20
ayounghenrynash, your typos are getting freudian18:20
henrynashI aim to amuse :-)18:21
*** kaganos has joined #openstack-meeting18:21
henrynashcurrent state is that the keystone client reference design is already up for review at https://review.openstack.org/#/c/17693/18:21
ayoung#link  https://review.openstack.org/#/c/17693/18:22
henrynash…and the server side will be ready for review (WIP as necessary) later this week18:22
dwchad2Henry, if you have spare development cycles, why not work with Kristy on attribute mapping18:22
ayounghenrynash, I think we need to see that.18:22
gyeeayoung, should we wait for henrynash's keystone impl before review the client changes?18:23
henrynashdwchad2: so have made comments to the attribute mapping api proposals18:23
*** EmilienM has quit IRC18:23
ayounghenrynash, link?18:23
dwchad2henry: been in london at a meeting all day so not had chance to see them yet18:24
kwsshenrynash: I got an email but can't see the comments in google docs18:24
henrynashkwss: sometimes they are in the comments button at the top - and could you post the link to your doc in this IRC?18:24
dwchad2what is the advantage of putting in groups now, if they are going to modified in a few weeks time?18:24
ayoung#link https://docs.google.com/a/kent.ac.uk/document/d/1cObK3P_ic9XSTwJRFsmimG94LDnFbsPbvx_H1aM1FPI/edit#18:25
ayoungIs that still the current doc?18:25
*** EmilienM has joined #openstack-meeting18:26
kwssyes18:26
kwssayoung: yes18:26
*** derekh has quit IRC18:26
henrynashdwchad2: I think we have to consider any attribute based implementation experimental until we get through all the details (which I have no doubt we will in the end)….but the RBAC solution is pretty simple, straightforward and we know will work18:26
henrynashkwss: so on my copy, my comments come up if you click the comments box at the top….18:27
dwchad2but your use of attribute mapping wont be experimental since it will map groups into roles and tenants. So there are no "attributes" involved (except that they are all attributes!)18:27
kwsshenrynash: I see them now, I'll respond after the meeting :)18:28
henrynashkwss: no problem, thx18:28
dwchad2attribute mapping is another way of implementing groups that can be made invisible to end users, and it a step on the way to federation, whereas groups on its own is not18:28
ayounghenrynash, I am going to kind of leave it up to you for now.  If you think you can get the groups impl working on top of attributes, and do so in the Grizzly time frame, I think that would be the best approach, but I can see that might be too tight a dependency18:29
henrynashdwchad2: agreed….and hence the proposal of the reference design that we then start using the attribute mapper to store the relationships...18:29
ayoungI'd almost like to do attributes like we did PKI:  get it in and usable in Grizzly, and then, in H, make it the default for all the things that are going to use them18:29
henrynashayoung: I'm happy to put the work in on top of the basic reference implementation so that we start exploring how we sue attributes for this18:30
ayoungI think once we have Attributes etc, retrofitting APIs to use them will be fairly straightforward, so we should hold things up waiting for them for fear of future work.18:30
henrynashayoung: agreed18:31
ayoungdwchad2, kwss, does that pass the sanity test?18:31
*** dkehn is now known as dkehn_afk18:31
dwchad2ayoung: did you mean not18:32
ayoungdwchad2, yes "we should *not* hold things up..."18:33
kwssmakes sense to me18:33
ayoung#agreed  Groups goes forward ontop of RBAC, gets retrofitted in H release18:34
dwchad2If Henry has spare dev cycles I would rather he works with Kristy on attributes now and they will have it finished in half the time18:34
ayoungdwchad2, yes, but then we still need to do the Groups implementation on top of it18:34
ayoungWhich will likely push it out of the Griz release18:34
dwchad2Since there are many many things to do in Keystone, creating extra work is a big issue to me18:35
ayoungunderstood18:35
ayoungbut we need to balance the demand from the other projects with the need to set things up for the long term....hard line to walk18:35
*** garyk has quit IRC18:35
dwchad2The groups work is the easiest bit once you have attribute mapping since all Henry needs to do is add roles to the backend and pull them out. No other API changes are needed18:36
henrynashdwchad2: I'll happily work with Kristy to add support for attributes once we have the reference design - I really think this is at the safer route18:36
dwchad2With Henry's current plan there is a lot of changes needed to  the APIs18:36
ayoungdwchad2  I am not sure I agree.  I think we are going to need a deliberate group api to give off to the other projects.18:36
ayoungdwchad2, that is fine, lets get them in the review.  I think the focus should be nailing down the APIs for groups18:37
dwchad2The group API you need is to add groups to users and retrieve groups from users18:37
dwchad2then the AM maps the groups into roles and tenants and domains and whatever else you need18:37
gyeealso, assigning roles to them18:38
ayounggyee, dwchad2 this is where things get gray18:38
ayoungwe can treat everything as an attribute internally18:38
dwchad2gyee: no, since you already have the apis for adding roles to users18:38
ayoungbut we need to export APIs to the end users that speak their language.18:38
ayoungdwchad2, but we don't have the API for adding roles to groups18:39
gyeewhole point of doing groups is we don't have to directly assigning roles to users18:39
dwchad2You dont add roles to groups. You set up attribute mappings for this18:39
ayoungI understand that we could do that with the mapping API, but I think it will be too low level18:39
gyeehow does attribute map API works?18:40
*** nati_ueno has joined #openstack-meeting18:40
ayoungdwchad2, gyee hold on18:40
ayounglets not get into a design discussion right now18:40
ayounghere is the chase18:40
ayoungwe need to expose an API that people will understand.  Educating them on ABAC and Attribute mapping will take time18:40
dwchad2we already have a published design, so we should discuss this after the meeting18:40
ayoungdwchad2, +118:41
dwchad2ayoung: +118:41
ayoungdwchad2, so I think we have an Education task as far as ABAC etc.  First thing is to get ABAC into the code base.  We can then show how we use it to do things that were more "hard coded" in the past. and then replace the hard coded implementations with ABAC18:41
dwchad2clearly having working code you can demonstrate is far better to end users than a blueprint :-=)18:42
dwchad2Just like it was with federation18:42
ayoungHowever, that does not mean we hold off on new features until ABAC is in.  While I know you have a good grasp on the implementation details, I still think it is going to take longer than you think to get to the point where we can depend on it18:43
dwchad2actually we are not adding ABAC initially18:43
dwchad2we are only adding AM18:43
dwchad2the authz is still RBAC using existing roles18:43
ayoungdwchad2, I am lumping attribute mapping into ABAC.  I realize I am being imprecise.18:43
dwchad2yes, its a multi step process. And AM is one way of implementing groups and RBAC which is an intercept strategy for ABAC and federation18:44
henrynashdwchad2: but the underpinning is the same entities (sets, mappings etc.) and the api to go with it - it will be important for us to really get that right…since once it is in there, we will depend on it for a longtime18:44
dwchad2So you dont waste any time and coding18:44
ayoungOK,  We need to make sure we talk about the Keyring thing.  I'm going to move us along....18:45
dwchad2the api we have designed is fully generic and extensible18:45
ayoung#topic Keyring18:45
*** openstack changes topic to "Keyring (Meeting topic: keystone)"18:45
dwchad2so adding domains becomes very easy18:45
henrynashayoung: I need to ask if the action you stated a while back still stands on this18:45
henrynash(to close it out)18:45
ayounghenrynash, well, understand I am not PTL, so it is just my call, not an official project call18:46
henrynashayoung: OK, understood18:46
*** colinmcnamara has quit IRC18:46
ayoungI'd take it as a suggestion for now, and drive forward with the groups work as is, especially since you already have the code nearly done.  We'll take it up again post code review?18:47
henrynashayoung: ok, agreed18:47
*** vishy is now known as vishy_zz18:47
ayoung#action revisit Groups once Attribute Mapping and Groups reviews are both posted18:47
ayoungOK,  Keysring18:47
gyeekeyring18:48
ayounggyee, here is my understanding18:48
ayoungwe want keyring as a long term tool, but we need to be sneaky about it.  And we got caught18:48
dwchad2what is keyring. Do you have a URL18:49
ayoungThere are many issues around credentials caching, probably most significantly when the user is an automated daemon18:49
gyeeayoung, disabling keyring by default means on one will use it, ever :)18:49
ayounggyee, can you summarize Keysring support18:49
*** ewindisch has joined #openstack-meeting18:49
ayounggyee, understood18:49
ayoungbut we need to do that initially18:49
ayounglike PKI tokens18:50
*** garyk has joined #openstack-meeting18:50
ayoungget it in, but disabled18:50
gyeewe added keyring support in keystoneclient so we can cache tokens in keyring18:50
gyeeadvantage #1 no need to keep requesting tokens18:50
ayoungthen work out the issues with explicitly  enabling it in Devstack.18:50
ayounggyee, to be specific18:50
gyee#2 no need to have passwords in env var18:50
ayoungif we cache the unscoped tokens, we only need to request a new one when they are about to time out, and we can continue to use them to request scoped tokens18:51
gyeeyes18:51
ayounggyee, so there is the rub...#218:51
*** ryanpetrello has joined #openstack-meeting18:51
ayoungfor an automated daemon, we need to be able to deal with initializing keyring without user interaction, much like a kerberos Keytab18:52
gyeeproblem is there are two usage of python-keystoneclient, interactively and non-interactive18:52
ayounggyee, right, so we need to keep it disabled by default until we clear up how to solve the non-interactive use cases18:52
gyeeayoung, I'll need to do some code diving18:53
gyeeI mean looking at the keyring impl18:53
ayoungdwchad2, I think I have a link to the upstream package we are pulling in for Keyring, but basically it is a python front end to things like nss databases, openssh keys, etc.  A (hopefully secure)  credential cache18:53
ayoung#link http://bitbucket.org/kang/python-keyring-lib18:55
gyeeif your login password is the same as your keyring password, ubuntu won't prompt for keyring password18:55
ayoungThat is from18:56
ayoung/usr/lib/python2.7/site-packages/keyring-0.9.2-py2.7.egg-info/PKG-INFO18:56
ayounggyee, there is also the question about whether tokens should get shared between applications that are all using keystone client.  My thought is "of course" but I suspect some people will object.  Also,  we need to figure out what to do if keyring is installed on a machine that is running horizon18:57
ayoungtokens should not get cached the same way from HTTPD....18:57
gyeethat's what keyring is for18:57
gyeethink of keyring as your browser cookie jar18:58
ayounggyee, can I ask you to write up what the overall strategy is for implementing keyring, and covere those 3 uses:  automates, HTTPD, CLI?18:58
ayoungI think we need to be able to point people at that doc when we try to educate them about the usage.18:59
gyeesure18:59
ayoung#action gyee to write up  strategy is for implementing keyring,  covering (at least) 3 uses:  automated , HTTPD, CLI19:00
ayoungOK, that is 2PM.  No dolphm so we are going to have to table the discussion on the refactoring.19:01
ayoungAny last points before we get kicked out?19:01
ayoung#topic Test Coverage19:01
*** openstack changes topic to "Test Coverage (Meeting topic: keystone)"19:01
ayoung#link http://admiyo.fedorapeople.org/openstack/covhtml/19:01
ayoungI'll update that post refactoring, but please take a look at the pieces you are working on, and try and expand the unit test coverage.  That is all.19:02
ayoung#endmeeting19:02
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"19:02
maliniWould not anyone with access to the login password be able to reset the keyring password?19:02
openstackMeeting ended Tue Dec 11 19:02:40 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-12-11-18.00.html19:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-12-11-18.00.txt19:02
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-12-11-18.00.log.html19:02
ayoungmalini, lets continue in #openstack-dev\19:03
fungici roll call?19:03
maliniOK! Take care19:03
clarkbo/19:03
*** dwchad2 has left #openstack-meeting19:03
jeblairo/19:03
*** marek__ has quit IRC19:03
fungitoddmorey? mordred?19:04
fungipabelanger?19:04
*** toddmorey has joined #openstack-meeting19:04
jeblairtodd's joining now...19:04
jeblairwe're on cafe wifi -- wish us luck19:04
toddmoreyjoined.19:04
fungiheh19:04
jeblair#startmeeting ci19:04
openstackMeeting started Tue Dec 11 19:04:59 2012 UTC.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.19:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:05
*** openstack changes topic to " (Meeting topic: ci)"19:05
openstackThe meeting name has been set to 'ci'19:05
*** malini has quit IRC19:05
jeblairlet's make an agenda now -- who has topics?19:05
fungicla stuff, git-review...19:06
clarkbnova testr, weekend project moves19:06
fungilooks agendafied enough to me19:06
*** nachi_ has quit IRC19:06
jeblairttx wants updates on stuff later in the meeting19:06
*** markmcclain has quit IRC19:07
jeblairso in order of least to most interest to ttx:19:07
jeblair#topic git-review19:07
*** openstack changes topic to "git-review (Meeting topic: ci)"19:07
fungiyep19:07
fungiso clarkb has put together a skeleton for a test suite: #link https://review.openstack.org/1755219:08
fungii've started playing with that some, want to see what we can plug in from #link https://etherpad.openstack.org/Exy0u2IYpO19:08
clarkbI am not entirely sure that it is worth much, but it was an itch I had to scratch19:09
fungialso, i've started conversing with marcin on #link https://review.openstack.org/1495319:09
clarkbat the very least it should help point out some of the difficulties in testing git-review with unit test like tests19:09
fungiyes, very promising19:09
fungias for 14953, i'm interested in feedback from the group on the direction there. he raises some excellent points19:10
clarkbok, if I manage to do one thing today I will make sure that looking at that change is the one thing19:10
fungiparticularly in respect to being able to define discrete error codes to enable easier feedback to gerrit admins from less-experienced users19:11
fungithat exhausts what i have on git-review for the moment. anybody else have anything for that topic?19:11
clarkbfor testing, it would be a whole lot easier if git-review became an importable python script19:12
clarkbso that may be something we want to look at doing if automated testing becomes important19:12
fungiyes, which could be as simple as wrapping in main(): and checking the calling namespace at the end of teh script19:12
jeblairclarkb: that sounds very reasonable19:12
clarkbthats all I had19:13
jeblair#topic nova testr19:13
*** openstack changes topic to "nova testr (Meeting topic: ci)"19:13
clarkbnova testr is really picking up steam. mordred's DB fixture change was merged, and all of my test bug fixes have been merged19:14
*** garyk has quit IRC19:14
clarkbmordred thinks we really need to continue having html test result output, so the next thing that I will be working on is making a subunit consumer that spits out html19:14
clarkbother than that run_tests needs to be ported (I feel like we will lose the battle if that doesn't happen) and run-tox.sh will need to be updated to hande nose and testr results19:15
jeblairyeah, i think that will be really helpful19:15
* fungi agrees19:16
jeblairthe html output will be helpful19:16
jeblairclarkb: i'd like to see run_tests.sh do less over time...19:16
jeblairto sort of head toward being a thinner and thinner wrapper around tox, at least for the important bits19:16
fungii'd like to see run_tests.sh be documentation of how ci invokes the testsuite, and nothing more19:16
jeblairto try to address the "tests are run two ways" problem19:17
clarkb++19:17
jeblairfungi: yeah19:17
jeblairclarkb: so i mean, not suggesting you solve all those problems right at first...19:17
clarkbthat is a good idea. It should be straightforward to push fungi's suggestion to run_tests.sh and see what reviewers say19:17
jeblairclarkb: but maybe that can influence your direction as you hack on run_tests,19:18
fungirun_tests.sh does have the benefit of being immediately obvious, easy to find, and something lots of people already know to run19:18
clarkblifeless has been super helpful and we have added features to fixtures and testrepository to help make this happen19:18
fungias opposed to burying invocation instructions in a HACKING file19:18
jeblairclarkb: lifeless said that you and mordred wanted to get rid of tox.  i'm assuming he was remembering the wrong word.19:19
funginpse?19:19
fungier, nose?19:19
mordrednose19:19
mordredwe want to get rid of nose19:19
clarkbmordred: I think you did mention how sourcing the tox venv and run testr run --failing19:20
jeblairgood.  glad we're on the same page. :)19:20
clarkbis useful. that doesn't get rid of tox just changes the workflow in places19:20
mordredclarkb: yes. I mean, people should learn how to use testr19:20
fungimordred also enjoys herding cats in his spare time19:21
clarkbtox will be sticking around I think.19:21
clarkbany other questions comments concerns about testr?19:21
jeblair#topic project moves / zuul server move19:22
*** openstack changes topic to "project moves / zuul server move (Meeting topic: ci)"19:22
jeblairmordred: your changes for the ci->infra rename ready?19:22
mordredjeblair: they can be by this weekend - they need a re-base19:22
mordred(a new project got added)19:22
jeblairi need to propose my zuul puppet changes this week.  let's assume i can get that proposed by the end of tomorrow19:23
jeblairthen we sholud be ready to do both of those at once19:23
jeblairmordred: 9am PST sunday good for you?  or should we do 10am?19:23
mordredjeblair: 9 is great19:24
fungiso 1700z19:24
jeblairttx: ping19:24
jeblairokay, i'll send out an email announcement today or tomorrow19:24
*** otherwiseguy has quit IRC19:25
*** alexpilotti has quit IRC19:25
fungijeblair: i'm assuming we want to block off ~3 hours given the list of changes19:25
jeblairfungi: yeah, a little more time is probably a good idea for this one.19:25
fungiwfm19:25
clarkband as a reminder I probably won't be able to participate19:25
clarkbas  Iwill have spent saturday in leavenworth19:26
jeblairclarkb: cool.  fungi: will you be around?  it's not necessary, but just wondering.19:26
fungiyes, wouldn't miss it19:26
fungihappy to help19:26
jeblaircool, anything else about sunday's outage?19:27
*** spzala has quit IRC19:27
*** stevebake has quit IRC19:28
fungisounds like no19:28
jeblair#topic CLA project19:28
*** annegentle_ has joined #openstack-meeting19:28
*** openstack changes topic to "CLA project (Meeting topic: ci)"19:28
fungittx may or may not care about this one19:28
jeblairyeah, i think he does.  hopefully he'll show up soon.19:28
fungii've got proposed documentation updates tracked at #link https://etherpad.openstack.org/cla-maintenance-201219:28
fungireview/input appreciated19:28
fungiproposed announcement draft there too, but with a made-up date for now19:29
fungistill working on the sphinx patch, since there's several places which need touching19:29
*** gyee has quit IRC19:29
*** stevebake has joined #openstack-meeting19:30
fungialso putting together a proposed mechanism to do group management within jeepyb/puppet, but no patch uploaded yet19:30
fungiwas looking for some direction there... would we want to do group management for projects within puppet rather than directly through the gerrit webui?19:30
jeblairfungi: no, i think we just need bootstrapping in puppet19:31
fungior just initial members to bootstrap new project groups?19:31
fungiokay, i'll go that route then19:31
fungihad one other question too, which may be more for foundation people...19:31
jeblairfungi: and then the core/drivers groups should be self-owned in gerrit19:31
fungiwhat's the plan with the ccla and the usgcla?19:31
fungileave those processes as-is for now?19:31
clarkbthe self ownership change is simple (change the flag on the create group call)19:31
jeblairfungi: but having said that.. maybe we sholud consider management in gerrit -- it would mean code review for adding new people, which is cool.  but i'm not sure it's necessary.19:32
*** anniec has joined #openstack-meeting19:32
jeblairfungi: i still lean toward self-management in gerrit.  but if someone feels strongly the other way, speak up.  :)19:32
fungijeblair: i can go either way. there are obvious benefits to either solution19:32
jeblairfungi: yes, i think we stay out of the ccla and usgcla...19:32
jeblairfungi: _because_ everyone, even those, still need to agree to the individual one19:33
jeblairfungi: which basically means that's all we care (or even can care) about19:33
clarkbfor self managed, the -drivers of -core group(s) would have permissions to add and remove people on their own?19:33
clarkbif so then I think that is the way to go19:33
jeblairclarkb: yep19:34
fungijeblair: okay. so that said, the usgcla instructions claim that the individual should *not* sign an icla. do we do group-cla for that then?19:34
jeblairfungi: oh how weird.  i guess if it comes up, sure.  :)19:34
fungimaybe that's something which is not implemented19:34
ttxpong19:34
fungiokay. cool enough with me19:34
fungittx!19:35
jeblairfungi: yeah, if we need it, we can just add it to the table real quick.19:35
*** joe5081 has quit IRC19:35
jeblairttx: we're talking about cla stuff19:35
ttxcatching up19:35
fungimordred: toddmorey: any updates on the foundation integration?19:36
jeblairtoddmorey: want to let people know about your efforts19:36
toddmorey  sure, sorry… colliding meetings19:36
toddmoreyok, so the site has a live endpoint that returns the status code for a member and logs that transaction. I believe Stef thought that was enough to store.\19:38
toddmoreyI'm bouncing back to this after the election nomination process, so I'm working to pull up my notes.19:38
*** cp16net is now known as cp16net|away19:39
fungito add, we have review-dev pointed at that contact store url as of a couple weeks19:39
*** jcru has joined #openstack-meeting19:39
ttxfungi: nice work on documentation19:39
fungittx: still in progress, of course19:39
jeblairfungi, toddmorey: is that the production or a dev site?19:39
toddmoreywell, the endpoint that hits the member database is production.19:40
fungijeblair: the url looks production to me, and i gather we're testing it with non-live appsec and gpg key19:40
fungiand we'll add a new appsec key and gpg keypair in hiera when we roll out the production change19:40
jeblairare there issues with combined dev and prod data?19:40
jeblairas in -- toddmorey do you need to clear out any data, and do we need to at some point stop pointing the dev gerrit at it?19:40
toddmoreyI'd like to know a clear cut-over so I can indicate it in the logs as such.19:41
jeblairokay, if it's just a matter of knowing the timestamp, that should be easy, i don't think it'll require special planning19:41
toddmoreybut they could be also manually reviewed if required. there's nothing destructive about the presence of the data, it would just pollute any reports…. but if I mark it, then we'll be good.19:42
jeblairwe'll have a definite cutover time when we reconfigure the production gerrit to do this19:42
toddmoreyminor coordination effort required, but easy to do19:42
fungiwill there be a dev system we want to repoint review-dev at then?19:42
clarkbhaving one would be nice as a way to work through potential problems (especially since this will be new)19:44
toddmoreyyeah, let me deploy that to staging and keep it stable for dev purposes19:44
*** vishy_zz is now known as vishy19:44
fungialso, i think we want some foundationy people to go over #link https://review-dev.openstack.org/static/cla.html (if they haven't already)19:44
jeblairtoddmorey: cool -- one of the things we'll definitely want to do is test new versions of gerrit on review-dev, so making sure the cla integration still works against a staging server will be important19:44
toddmoreyThat will be the first external interaction with the staging environment, so might need to figure out what happens if staging is down or maybe have another environment specifically for this purpose.19:44
*** sarob has joined #openstack-meeting19:45
ttxfungi: want a sanity-check that it's not different from the original ? Or are there any change we need to validate ?19:45
toddmoreyright, for sure. that makes sense. if it's okay for it to be occasionally in flux (for minutes, usually) then we can use the existing staging environment.19:45
*** dkehn_afk is now known as dkehn19:45
toddmoreyjeblair and I plan to talk more about how to bring the www into the ci processes, too, so they'll be more closely coupled.19:46
ttxtoddmorey: that should simplify a few updates where we are forced to put you in the loop19:46
jeblairoh, so i heard that the organization mentioned in the cla needs to change19:46
*** pabelanger has joined #openstack-meeting19:46
jeblairfungi: so my best info is that is currently wrong19:46
jeblair#action jeblair ask jbryce for the real official new CLA text19:47
*** vishy is now known as vishy_zz19:47
clarkb++ to www being more ci like19:47
fungito propose changes which might be needed before production19:47
fungiit was ripped from the wiki version, but some reformatting was necessary19:47
fungisince it's legalese, i don't want to do stuff without oversight19:47
fungichanges can be proposed against #link https://github.com/openstack/openstack-ci-puppet/blob/master/modules/openstack_project/files/gerrit/cla.html19:47
toddmoreyit will. we're eager, too. excited about being an official participant.19:47
fungiyikes. i think i just lagged heavily19:48
jeblairtoddmorey: yeah, we're getting pretty good at adding new projects, so it should be pretty easy once the code is ready for public consumption19:48
ttxtoddmorey: at least your contributions will be recognized as such :)19:48
*** vishy_zz is now known as vishy19:48
jeblairyeah, i keep seeing 12 second lags :(19:48
fungimine was, like, a minute or two19:49
jeblaircool, so it sounds like we have my action item...19:49
toddmoreysorry… lag time in the chat? Or hitting the www? what's lagging (besides my feeble mind)?19:49
*** brich has quit IRC19:49
fungiirc lag, sorry19:50
jeblairthen getting review of some of the docs and other changes fungi linked to...19:50
jeblairand then we're more or less _technically_ ready to make the change?19:50
toddmoreygotcha. the word 'lag' just makes me jumpy. The pagers in my head go off.19:50
jeblair(which will obviously involve planning/scheduling/notification, etc)19:50
toddmoreyright, with just a quick ping to me to let me know when we cross over.19:50
fungijeblair: toddmorey: works for me19:51
*** novas0x2a|laptop has joined #openstack-meeting19:51
*** AlanClark has joined #openstack-meeting19:51
*** vishy is now known as vishy_zz19:51
jeblaircool.  also toddmorey and i will chat with jbryce today and make sure we're all on the same page19:51
jeblairfungi: do you want to continue planning for the change?19:51
fungialso please clarify what's going to happen with the contributors page in the wiki (i assume it will be abandoned?)19:52
jeblairfungi: yes19:52
fungijeblair: yeah, i can continue planning, sounds like19:52
jeblair#action fungi plan CLA cutover19:52
fungiyay for movement~19:52
fungi!19:52
jeblair#topic ttx all-request 6 minutes19:52
*** openstack changes topic to "ttx all-request 6 minutes (Meeting topic: ci)"19:52
ttxyay19:52
ttxFirst thing is the wiki transition19:53
jeblair(i'm hoping "cla" was a big part of ttx's agenda)19:53
ttxThere are a few pages that grew organigally on wiki.openstack.org website19:53
ttxincluding http://wiki.openstack.org/releasestatus/19:53
ttxI think we should move that off-wiki to another alias19:53
jeblairttx: can you research and make a list of such pages?19:54
fungiwww seems like a good place to me for that sort of stuff... as a user that's where i'd expect it at least19:54
ttxjeblair: the only other is http://wiki.openstack.org/bugstats19:54
jeblairttx: what generates those?19:55
ttxI'm currently rewriting it so that it's actually more resuable and puppetable19:55
clarkbis there harm in that data moving to mediawiki then being transitioned to more permanent homes? or are we tring to get this done before we migrate?19:55
jeblairttx: is that a CGI, or a cron, or...?19:55
toddmoreywait, one other thing that comes to mind was the secure store of the keypair on a CI server (as I'm storing pieces of the data encrypted). Monty, do you remember talking that part out?19:55
ttxreleasestatus is generated on a cron19:55
jeblairclarkb: i think these are not wiki pages19:55
ttxtakes a few minutes to generate19:55
ttxthose are not wiki pages19:55
ttxthey just abuse apache conf. sorry about that19:55
clarkboh I see19:55
fungitoddmorey: we have the contact store keys securely stored in hiera on our puppet master server, if that's what you're asking19:55
jeblairtoddmorey: i think we were going t19:55
jeblairack.  what fungi said.19:56
toddmoreyright, that's exactly what I was (trying) to talk about. Thx.19:56
*** gabrielhurley has joined #openstack-meeting19:56
ttxso the idea would be to add a new host alias to the machine that currenbtly has wiki, so that we can advertise new url19:56
toddmoreyjust wanted to ensure the data was usable later. :)19:56
ttxand then we can move to do it correctly19:56
* fungi nods19:56
jeblairttx: good plan19:56
ttxstatus.openstack.org could host both19:57
jeblairttx: toddmorey may have thoughts about adding to to www.o.o... or19:57
ttxNo idea how to make that happen though19:57
jeblairttx: we can do that^19:57
jeblairttx: we have a general purpose host for static content called static.o.o19:57
ttxhmm19:57
jeblairttx: we could make status.openstack.org a vhost on that, and add your scripts in via puppet19:57
jeblairttx: (not suggesting your url be static.o.o, that's just the real hostname for reference)19:58
ttxjeblair: sure, that sounds like the long-term solution19:58
ttxin the mean time I don't want to lose the pages when we move the wiki19:58
jeblair#action jeblair register status.openstack.org in dns pointing to current wiki ip19:58
ttxlike I said, I'm actually rewriting the releasestatus code19:58
jeblair#action ttx pack up status scripts for installation on static.o.o via puppet19:59
ttxit's on bzr, will be on github when I'm done19:59
clarkband someone will need to add a redirect on new wiki.o.o to status.o.o for those two pages19:59
*** ayoung has quit IRC19:59
ttxclarkb: maybe yes19:59
jeblairyeah, the wiki cutover is coming up soon, so i think you're right clarkb20:00
clarkbI can edit the vhost for new wiki.o.o20:00
ttxnot a big deal as long as the new pages are linked from the wiki20:00
*** markmc has joined #openstack-meeting20:00
ttxwe are off-time, I'll complain more next week20:00
clarkb#action clarkb setup redirect from new wiki to status.o.o for bustats and releasestatus20:00
jeblair#action clarkb add redirects to status.o.o on new wiki host20:00
jeblairttx: thanks! it has been very helpful.20:01
clarkbttx: feel free to complain at us in -infra too :)20:01
jeblair#endmeeting20:01
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"20:01
openstackMeeting ended Tue Dec 11 20:01:18 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ci/2012/ci.2012-12-11-19.04.html20:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ci/2012/ci.2012-12-11-19.04.txt20:01
openstackLog:            http://eavesdrop.openstack.org/meetings/ci/2012/ci.2012-12-11-19.04.log.html20:01
*** pabelanger has left #openstack-meeting20:01
ttxclarkb: most of my complaints involved mordred anyway20:01
ttxand he is hiding20:01
ttxWho is around for the TC meeting ?20:01
jeblairtoddmorey: and thank you too.  :)20:01
toddmoreythanks guys. looking forward to being more involved here in the channel.20:02
danwentttx: i am20:02
markmcme me me20:02
ttxthat makes 3 of us.20:02
ttxlet's see if we can reach 7 and hold a quick meeting20:02
danwentttx: ok, ping me if they show up, i'll get some work done in the mean time :)20:03
ttxThe very boring reminder did not actually ancourage everyone to join20:03
russellbhere20:03
ttx420:03
ttxmordred: around ?20:03
russellbwe could have a gossip session about those that aren't here20:04
*** toddmorey has quit IRC20:04
ttxvishy, annegentf, jgriffith, bcwaldon, notmyname ?20:04
*** vishy_zz is now known as vishy20:04
notmynamehere20:04
vishyhi20:05
ttx620:05
gabrielhurleyttx: I'm here too20:05
ttxI knew I was missing someone20:05
ttxthat makes 720:05
* gabrielhurley feels special20:05
ttxshould be quick, especially if mordred is not around20:05
ttx#startmeeting tc20:05
openstackMeeting started Tue Dec 11 20:05:38 2012 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:05
*** openstack changes topic to " (Meeting topic: tc)"20:05
ttxdanwent: come back!20:05
openstackThe meeting name has been set to 'tc'20:05
ttxAgenda for today is (was):20:05
*** anniec_ has joined #openstack-meeting20:05
ttx#link http://wiki.openstack.org/Governance/TechnicalCommittee20:05
ttxNothing formal, only discussions20:06
*** anniec has quit IRC20:06
*** anniec_ is now known as anniec20:06
*** markmcclain has joined #openstack-meeting20:06
ttx#topic Quick update on the "Future of Incubation / core" joint committee20:06
*** openstack changes topic to "Quick update on the "Future of Incubation / core" joint committee (Meeting topic: tc)"20:06
ttxmarkmc: want to do the update, or should I ?20:06
markmcwell20:06
markmcthere's not much to say, really20:07
markmcwe had a meeting20:07
russellba meeting was held, didn't cover any new ground yet20:07
* AlanClark just noticed that the appointment for this weeks committee meeting didn't go out, goes to check webex to see why20:07
markmcspent much of the time discussing the scope of the committee, the schedule of next meetings20:07
*** otherwiseguy has joined #openstack-meeting20:07
ttxThe BoD is represented by 3 people, so we aligned our representation to match20:07
markmcthe basics of how incubation works20:07
markmcand ran out of time20:07
ttxHopefully we'll cover more ground next time20:07
markmcprediction is that it'll take 5 or so more meetings20:07
russellbttx: you're going to cover it, right?20:08
ttxnext time should be Thursday, in case you want to join20:08
russellb(spot #3)20:08
ttxrussellb: yes20:08
russellbok great20:08
markmcanother meeting this week20:08
markmcthere's an etherpad20:08
* markmc looks for it20:08
markmchttps://etherpad.openstack.org/IncUp20:09
markmcthat's my summary :)20:09
ttxquestions ?20:09
ttxHopefully next meeting we'll have more interesting progress to report20:10
ttx#topic Ongoing discussion: Distro & Python 2.6/3.x support policy20:10
*** openstack changes topic to "Ongoing discussion: Distro & Python 2.6/3.x support policy (Meeting topic: tc)"20:10
ttxI was kinda hoping mordred would be around to make progress on that20:10
ttxHe said he would push a clear motion to the ML to reboot the discussion20:11
ttxI hope he will do that before EOD tomorrow we could even vote on it next meeting, however I've had trouble cornering him lately20:11
jgriffithsorry...late20:11
ttxIn his absence I don't have a lot more to add on that topic20:11
*** maurosr has quit IRC20:12
ttxanything to add to that ?20:12
ttx#action mordred to push a clear motion to the ML to reboot the discussion on Distro & Python 2.6/3.x support policy20:12
ttx#topic Open discussion20:13
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:13
ttxThat's all we had on the agenda. Anything else anyone ?20:13
ttxFWIW the incubated projects are making good progress towards release integration20:14
markmccoolness20:14
ttxthat's a lot of effort, which make sthe discussion on incubation vs. core all the more important20:14
ttxok, if nobody has anything else to add...20:15
markmcwhen say a lot of effort20:15
markmcfor the projects themselves or you, or both?20:15
ttxI mean, we force those projects to go through a number of hoops20:16
ttxI feel bad if it's all for nothing in the end20:16
markmccool20:16
ttxso the current process really needs to be revisited to address that20:16
*** alexpilotti has joined #openstack-meeting20:16
markmcjust making sure you didn't mean "incubating projects are sucking up a lot of our resources"20:16
*** cp16net|away is now known as cp16net20:16
*** dkehn has left #openstack-meeting20:17
ttxmarkmc: no, not really. At least not on my side. They take up white space at the end of release meetings, basically20:17
markmcgreat20:17
ttxNot sure I could handle more than two at the same time, but it's going well20:17
ttxok... 42 minutes recess, then20:18
ttx#endmeeting20:18
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"20:18
openstackMeeting ended Tue Dec 11 20:18:17 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:18
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2012/tc.2012-12-11-20.05.html20:18
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2012/tc.2012-12-11-20.05.txt20:18
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2012/tc.2012-12-11-20.05.log.html20:18
*** MarkAtwood has joined #openstack-meeting20:18
*** sarob has quit IRC20:25
*** adjohn has quit IRC20:36
*** juice_ has quit IRC20:37
*** metral has quit IRC20:38
*** lloydde has joined #openstack-meeting20:38
*** kwss has quit IRC20:39
*** martine_ has joined #openstack-meeting20:44
*** martine has quit IRC20:47
*** juice_otg has joined #openstack-meeting20:48
*** Vek has joined #openstack-meeting20:50
*** ayoung has joined #openstack-meeting20:51
*** dwcramer has quit IRC20:53
*** sandywalsh_ has joined #openstack-meeting20:53
*** sandywalsh has quit IRC20:55
*** topol has quit IRC20:59
ttxmarkmc, heckj, notmyname, bcwaldon, jgriffith, vishy, gabrielhurley, danwent: around ?21:00
danwento/21:00
notmynamehere21:00
markmcyep21:00
gabrielhurley\o21:00
*** juice_ has joined #openstack-meeting21:00
stevebake\o21:00
bcwaldonttx: hey21:00
notmynamettx: I have to catch a plane this afternoon. can swift go first today (after the general stuff)?21:00
ttxnotmyname: sure21:01
notmynamethanks21:01
jgriffith\o21:01
ttxnotmyname: can even go before general announcements if you're short on time21:01
notmynamesure. thanks :-)21:01
ttxanyone from keystone ? I think heckj is in vacation21:02
ttxalso missing vishy, but let's start21:02
ttx#startmeeting project21:02
openstackMeeting started Tue Dec 11 21:02:24 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 #startvote.21:02
*** openstack changes topic to " (Meeting topic: project)"21:02
openstackThe meeting name has been set to 'project'21:02
ttxAgenda @ http://wiki.openstack.org/Meetings/ProjectMeeting21:02
ttxWe are 10 days away from the end of the world, and 4 weeks away from grizzly-221:02
annegentle_*snort*21:02
ttx#topic Swift status21:02
*** openstack changes topic to "Swift status (Meeting topic: project)"21:02
ttxnotmyname: o/21:03
notmynamettx: thanks21:03
ttx#link https://launchpad.net/swift/+milestone/1.7.621:03
*** juice_otg has quit IRC21:03
notmynameheh. that's rather empty :-)21:03
Vekone of these two things is substantially more likely than the other...21:03
ttxList is still a bit empty, anything you want to communicate should land / be fixed in that version ?21:03
notmynameI'll work on updating it this week. 1.7.6 is going to be mostly bug fixes21:03
ttxor that's still a bit early for that21:03
notmynamebut we do have some interesting patches (at least proposed)21:03
vishyo/21:03
* vishy requests going early since I have to leave soon21:04
ttx#action notmyname to update https://launchpad.net/swift/+milestone/1.7.6 with 1.7.6 objectives21:04
notmynamein talking with some contributors, I know there are some interesting features being worked on.21:04
ttxvishy: going on the same plane as John ?21:04
notmynamenope :-)21:04
ttxnotmyname: Still shooting for mid-January ?21:04
notmynameyes. 1.7.6 should be mid-january. no date yet21:05
ttxSounds good.21:05
ttxAnything more on Swift ?21:05
notmynameI hope to have one or 2 more releases before grizzly21:05
notmynameafter 1.7.621:05
notmynamebut if that happens or not depends on the state of the code21:05
ttxack21:05
notmynamegoal is 221:05
notmyname1.8 and 1.8.121:05
ttxnotmyname: I'll talk to you another day on the possibility to use RCs for the "final" grizzly one21:06
notmynamebut that's not official at all. just goals21:06
notmynameack21:06
notmynamethat's all I have21:06
ttxvishy: wanna go now or after general announcements ?21:06
ttxlet's do general announcements first, Nova next21:07
ttx#topic General announcements21:07
*** openstack changes topic to "General announcements (Meeting topic: project)"21:07
ttx#info Bug squash day coming this Thursday21:07
ttx#link http://wiki.openstack.org/BugDays/20121213BugSquashing21:07
vishyk21:07
annegentle_o/21:07
ttxIf you're available, join the crowd on #openstack-bugsquash to help with advice/review21:07
markmc#info Nova 2012.2.2 scheduled for Thursday December 1321:08
markmc#link https://launchpad.net/nova/+milestone/2012.2.221:08
ttxannegentle_: was the doc bug squash day any successful ?21:08
ttxmarkmc: Will also include the recent security fix that just landed on stable/folsom21:08
annegentle_yes, nearly 20 doc bugs squashed in a day21:08
markmcttx, yep21:08
annegentle_now we are back porting to folsom as needed21:08
annegentle_#info Outreach Program for Women accepted candidates announced today21:08
annegentle_#link https://live.gnome.org/OutreachProgramForWomen#OpenStack21:08
zykes-thanks to the stable team for backporting the nova floating ip with quantum stuff!21:08
annegentle_Welcome to Laura, Anita, Victora.21:08
markmcannegentle_, nice on both counts :)21:09
ttxWelcome!21:09
ttxmarkmc: did you analyze why automated testing didn't catch the stable/folsom regressions ?21:09
markmcannegentle_, irc nicks for them?21:09
markmcttx, yes21:09
markmcso, 2 bugs21:09
*** vipul is now known as vipul|away21:09
ttxmarkmc: any corrective actions ?21:09
*** vipul|away is now known as vipul21:09
markmchttps://bugs.launchpad.net/nova/folsom/+bug/108394421:09
markmcthat one came after the release21:09
annegentle_Anita is anteaya_i, not sure about Laura and Victoria off the top of my head.21:09
uvirtbotLaunchpad bug 1083944 in quantum/folsom "RPC exchange name defaults to 'openstack'" [Critical,In progress]21:09
annegentle_blog entry forthcoming, I'll include that info21:10
markmcbasically, unless we were testing notification consumption in the gate, it's unlikely the gate would have caught it21:10
markmcand https://bugs.launchpad.net/ubuntu/+source/nova/+bug/108183621:10
uvirtbotLaunchpad bug 1081836 in nova "nova-compute (folsom) fails to start, compute_driver is None" [Undecided,Confirmed]21:10
markmcthat wasn't caught because it was an issue with the default value of a config option21:10
markmcbut devstack explicitly sets the value of it21:10
markmcso, no - don't really have suggestions for either21:10
ttxfood for thoughts for QA folks21:11
*** dprince has quit IRC21:11
ttxmordred, annegentle, davidkranz: Anything to report from CI/QA/Docs land ?21:11
zykes-(clear21:11
* annegentle_ is in training all week, off IRC mostly21:11
ttxEveryone ready to go project-specific ?21:12
comstudyes sir21:12
ttx#topic Nova status21:12
*** openstack changes topic to "Nova status (Meeting topic: project)"21:12
ttxvishy: o/21:12
ttx#link https://launchpad.net/nova/+milestone/grizzly-221:12
vishyhi21:12
*** jhenner has joined #openstack-meeting21:13
ttxnot that much visible progress since last week21:13
ttxMostly due to a growing review queue, apparently ?21:13
* Vek is intending to do a pile of reviews tomorrow, fyi21:13
*** dani4571 has joined #openstack-meeting21:13
vishyi have been too busy to do my normal 70 reviews /wk21:13
russellbi've been down on my review amounts lately, too21:13
vishyhope to have some time to get to some over the next couple weeks21:14
ttx#info Focus on review for nova-core21:14
ttxnova-compute-cells: how are we doing there ?21:14
comstudi've been sick for a week, i'm back at it today21:14
comstudreworked a lot.. mostly have tests left21:14
comstudand whatever typos i made21:14
comstudthen the reviews will be updated21:15
*** stevemar has quit IRC21:15
ttxvishy/nova-core: it's your feeling that it's relatively close now ?21:15
comstudthere's not been a lot of new input/comments, holding off for my latest21:15
ttxrussellb: how is version-rpc-messages doing ?21:16
russellbpatch is up in oslo-incubator21:16
russellbI think it's pretty close ... i need to get it running though all the nova tests too21:16
ttxok21:16
markmcyeah, it's very close21:16
ttxIn other news, I've been chasing down a number of assignees to get milestone targets from them21:16
ttxGot answers from mostof them21:17
ttxdevananda mentioned that some of the DB blueprints might just not hit grizzly21:17
ttxsince he is focusing on baremetal stuff now21:17
markmcboo :(21:17
ttxvishy: he is supposed to communicate that to you while bumping some off Grizzly series goal21:18
russellbsad21:18
ttxI did not get answers (or updates) at all from Phil Day and TianTian Gao21:18
vishyok that makes sense21:18
ttxall in all fishing for updartes was successful21:18
ttxupdates*21:18
ttxThat's all I had on the Nova front. We need to make good progress over the next week21:19
vishycool21:19
ttxbecause I expect a slowdown at the end of December, somehow21:19
ttxAny question on Nova before we move on ?21:20
ttx#action devananda to defer Db blueprints he won't have time to cover21:20
ttx#topic Oslo status21:20
*** openstack changes topic to "Oslo status (Meeting topic: project)"21:21
ttx#link https://launchpad.net/oslo/+milestone/grizzly-221:21
ttxmarkmc: Almost on track...21:21
ttxmarkmc: About oslo-versioning, unfortunately mordred was nowhere to be seen today21:21
markmcyep, we're looking pretty good21:21
markmcyeah21:21
ttxI'll set up a meeting with him asap21:21
markmcI'm not really letting it block me21:21
ttx#action ttx to set up a meeting with mordred and markmc to make quick progress on oslo-versioning21:21
markmcAFAICT, we have a plan and it should just work21:21
markmcso it's really down to me to push ahead with oslo-config21:22
markmcbut confirming with mordred would be good21:22
ttxmarkmc: yeah, I just want that plan outlined so that I can tell if I'm fine with it :)21:22
markmcttx, cool21:22
mordredmarkmc: aroo?21:22
mordredreading21:22
ttxhere he is21:22
ttxmarkmc: In other news, I'm waiting on https://review.openstack.org/#/c/17672/ to start common-rootwrap21:22
ttxWould appreciate your review on that21:22
*** Ryan_Lane has joined #openstack-meeting21:22
markmcttx, yep, nova-core are slackers21:23
markmcoh wait, that's me too :(21:23
mordredmarkmc: yes, I believe we're in good shape in our plans - I would like to sync up with you to verify that my impl thoughts for it will work for you21:23
russellbnova-core is overwhelmed, that's what21:23
ttxmordred: maybe we can push that discussion offmeeting, just after this one ?21:23
ttxif markmc is still around21:23
markmcnah, I've got to disparu21:24
markmcmordred, quick summary ?21:24
ttxthat doesn't sound right in any language21:24
markmcdisparoo?21:24
*** vipul is now known as vipul|away21:24
* ttx parallelizes -- do we have someone from keystone crew to represent ?21:25
ttxmordred: if you push your thoughts to ML right now, markmc might be able to confirm and me to read it today21:26
ttxmordred: or if it's short and quick you can do it now21:26
ttx... ok, let's do Glance in the interlude21:27
ttx#topic Glance status21:27
*** openstack changes topic to "Glance status (Meeting topic: project)"21:27
ttxbcwaldon: o/21:27
bcwaldonttx: hey21:28
ttxThis is a chaotic agenda21:28
ttx#link https://launchpad.net/glance/+milestone/grizzly-221:28
* ttx refreshes21:28
ttxNot a lot of visible progress recently21:28
bcwaldonunfortunately little progress lately21:28
ttxapi-v2-property-protection and glance-api-v2-image-sharing are still not started ?21:28
*** dtalton has joined #openstack-meeting21:28
bcwaldonwe've had a few design discussions21:29
*** vipul|away is now known as vipul21:29
bcwaldonbut have been blocked on external things to actually work on them21:29
bcwaldonI'm still not worried about finishing them for g-221:29
ttxok21:29
ttxglance-domain-logic-layer: will it be complete once that last review lands ?21:29
ttxreview @ https://review.openstack.org/#/c/17512/21:29
bcwaldonthat's a question for markwash21:29
bcwaldonjust poked him21:30
markwashttx: not entirely21:30
ttxbcwaldon: will you have time to make good progress by next week ? Or intend to work during the holidays ?21:30
ttxmarkwash: ack21:30
bcwaldonttx: holi-day?21:30
bcwaldonyes I will be working ;)21:30
markwashttx: but it is very close, only two easier patches left21:31
ttxapparently some sort of evening, lasting a bit longer21:31
ttxok then, I don't sense panic in you yet, so probably fine21:31
ttxAnything more on Glance ?21:31
bcwaldonnot from me21:32
ttxStill no keystone folk ? dolphm, ayoung ?21:32
ttx#topic Quantum status21:32
*** openstack changes topic to "Quantum status (Meeting topic: project)"21:32
ayoungttx I can fill in21:32
ttxdanwent: hi!21:32
danwentttx: guess you're going to have to talk to me :)21:32
ttxayoung, cool, you're next21:32
ttx#link https://launchpad.net/quantum/+milestone/grizzly-221:33
ttxLooks on track to me... just needs some serious review work21:33
danwentas a general update, things are moving a bit slowly, as it seems like a lot of folks have pre-holiday internal deadlines that they are trying to hit21:33
ayoungyeah, we are cranking.21:33
danwentyes, key focus need to be on clearly several big reviews a week from here on out21:33
ttxquantum-db-upgrades: how is that going ?21:34
danwentoverally, seems managable, as long as we don't fall off a holiday cliff :)21:34
*** vishy is now known as vishy_zz21:34
*** markmc has quit IRC21:34
danwentttx: its been "about to be posted for review" for over a week now.  this is one of the items stalled due to other internal projects.  I'm confident mark will have it up soon.21:34
*** gyee has joined #openstack-meeting21:34
ttxok21:34
danwentand his stuff is always super high quality when it hits the review21:34
ttxdanwent: There was also this question for vishy and you about nova-network deprecation21:35
danwentso it tends to get reviewed and merged quickly.21:35
ttxon the ML @ http://lists.openstack.org/pipermail/openstack-dev/2012-December/003860.html21:35
ttxIs the idea still *not* to mark nova-net deprecated in Grizzly ?21:35
danwentttx: yes, nova-network will be fully supported in grizzly21:35
danwentsorry, if it doesn't have quantum in the subject-line, i tend to miss things on the ML21:36
ttxdanwent: ok, maybe drop a quick note on that thread21:36
danwentsure21:36
ttxdanwent: yes, that's why I mention it21:36
ttxThat's all I had. Anything else on Quantum, anyone ?21:36
danwentmaybe i'll update my filter to include "network" :)21:36
*** toddmorey has joined #openstack-meeting21:37
ttxsounds risky21:37
danwent:)21:37
ttx#topic Keystone status21:37
*** openstack changes topic to "Keystone status (Meeting topic: project)"21:37
ttxayoung: o/21:37
ttxThanks for filling in21:37
ayoungNo problem.21:37
ttx#link https://launchpad.net/keystone/+milestone/grizzly-221:37
ayoungWe had a pretty long discussion over the groups implementation earlier today.21:38
ayoung#link https://blueprints.launchpad.net/keystone/+spec/user-groups21:38
ayoungWe should have a proof of concept/reference implementation posted shortly21:38
ttxYeah, some progress since last week, but I'd say this is falling a bit behind due to impl discussions21:38
ttxaround user-groups and trusts21:39
ttxabout trusts: is that making progress ? It looks like it's still on the drawing table (which is not necessarily a bad thing)21:39
ttxbut maybe that means it's more likely to land in g3 ?21:39
ttx(trying to set expectations right)21:39
ayoungI think we are ok.  I have an Impl of trusts, but need to rebase it on the code review...21:39
ayoung#link https://review.openstack.org/#/c/17782/21:39
*** sarob has joined #openstack-meeting21:40
*** jcru has quit IRC21:40
ttxayoung: so that lengthy thread converged to a solution that was acceptable for everyone ?21:40
ttxayoung: or that covers something else ?21:40
ayoungTrusts are not that hard.  They are just another way to generate tokens.  Getting them in required working out a circular dependency issue.  I still need to get dolph's blessing. That is on the short list for this week21:40
*** sarob has quit IRC21:40
ayounglong thread?  You mean about groups?21:41
*** sarob has joined #openstack-meeting21:41
ttxayoung: the one on preauthed tokens21:41
ayoungttx, yes, we are OK with the approach21:41
ayoungsome quibbling over naming, but I think we are going to keep the name trusts21:42
ttxeh, ok21:42
ttxAnything more about Keystone ?21:42
*** sandywalsh has joined #openstack-meeting21:42
ayoungwe still need to finish the V3 api..21:42
*** cbaesema has joined #openstack-meeting21:42
ttxayoung: is that covered by a blueprint somewhere ?21:43
ayoungOh, and the Keyring support.  We are going to document clearly what the intention is with that21:43
ayoungttx, V3?  Yes.21:43
*** sandywalsh_ has quit IRC21:43
ttxayoung: not sure it appears as clearly though21:43
ttxayoung: if you have a pointer to it, I could use that21:44
ttxok, got to move on21:44
ttx#topic Cinder status21:44
*** openstack changes topic to "Cinder status (Meeting topic: project)"21:44
ttxjgriffith: hi!21:44
jgriffithhowdy21:44
ttx#link https://launchpad.net/cinder/+milestone/grizzly-221:44
jgriffithgetting there, expect a few more to close in the next couple of days21:44
ttxNot too bad, but not much progress since last week21:44
ttxok, great21:45
jgriffithttx: yeah, it became earily quiet after Friday :)21:45
ttxAbout local-storage: still no news ?21:45
jgriffithNo... I've got that and volume_backups targetted for removal tomorrow21:45
jgriffithpending the cinder meeting21:45
ttxok, sounds good21:45
ttxThat's all I had for you21:46
ttxAnything more in Cinder ?21:46
ttx#topic Horizon status21:46
*** openstack changes topic to "Horizon status (Meeting topic: project)"21:46
ttxgabrielhurley: hey21:47
gabrielhurleyhi21:47
ttx#link https://launchpad.net/horizon/+milestone/grizzly-221:47
ttxSame as others, slow progress overall21:47
*** adjohn has joined #openstack-meeting21:47
gabrielhurleysome progress on blueprints from me, and one bumped out (the implementor doesn't think it'll be done by the close of G2)21:47
gabrielhurleylots of good bugfixes in review, though, and only one or two new bugs21:47
*** bearovercloud has joined #openstack-meeting21:47
gabrielhurleyI'm gonna coordinate with the quantum team more closely to figure out what's happening with Quantum + Horizon in G2/G321:48
*** adjohn has quit IRC21:48
ttxsounds good21:48
*** adjohn has joined #openstack-meeting21:48
gabrielhurleyIf nthing else G2 may be a les feature rich but more bugfix-y milestone21:48
gabrielhurleyI still have hopes that I'll be able to hack a bunch later this month21:49
ttxyes, that's a decent buglist21:49
gabrielhurleyeh, I just roll the bugs I think are important from release to release21:49
ttxAnything more on Horizon ?21:49
*** mrunge has joined #openstack-meeting21:49
ttxgabrielhurley: suggestion: work on them this Thursday !21:49
gabrielhurleyindeed21:49
ttxyay for bug squashing day !21:49
ttx#topic Incubated projects21:50
*** openstack changes topic to "Incubated projects (Meeting topic: project)"21:50
ttxAnyone from Ceilometer team ?21:50
ttxstevebake: still around ?21:50
stevebakeyop21:50
ttx#link https://launchpad.net/heat/+milestone/grizzly-221:50
stevebakettx.py ran cleanly21:51
ttxIf I read this correctly you're feature-complete for g2 already ?21:51
stevebakeyes, focusing on testing, bugs, docs, packaging21:51
ttxor that's incomplete :)21:51
ttxok, great21:51
ttxYou still don't have a heat-tarball Jenkins job set up so I can't integrate you to common release management yet21:51
stevebakeresourcing will be messy until g-2 thanks to holidays21:51
ttxDid you push that request to the CI team ?21:51
stevebakettx: just yesterday, waiting for a review21:52
ttxstevebake: link ?21:52
stevebakehmm, actually that was only for python-heatclient https://review.openstack.org/#/c/17811/21:52
*** dolphm has quit IRC21:53
stevebakeI'll look into heat-tarball stuff21:53
ttxok, don't hesitate to ping CI folk on #openstack-infra for help/guidance21:53
ttxI might have to set a milestoen code to g2 at some point to support that21:54
ttxhttps://blueprints.launchpad.net/heat/grizzly looks good to me21:54
annegentle_stevebake: your team is one of the ones with docs on the wiki, is that right? Wanted to be sure you saw the email about the wiki migration.21:54
stevebakeDoes anyone have suggestion for first steps in getting heat into ppa:openstack-ubuntu-testing/grizzly-trunk-testing ?21:54
annegentle_stevebake: we can work on a "doc plan" more to get out of the wiki as you keep moving forward21:55
stevebakeannegentle_: yes, mostly reachable from http://wiki.openstack.org/Heat21:55
stevebakethat would be very much appreciated21:55
ttxstevebake: contacting jamespage would be a start. Not sure they would cover non-core stuff just yet. Do they have ceilometer in ?21:55
stevebakeceilometer is in21:55
* nijaba confirms21:56
ttxstevebake: ok, then I guess they could consider heat as well. Ask jamespage21:56
stevebakeannegentle_: I saw ceilo has some docs action happening too21:56
ttxnijaba: rady to talk Ceilometer ?21:56
ttxready*21:56
annegentle_#action annegentle_ to reach out to Heat (stevebake) via email re: doc plan21:56
nijabattx: I just got heat packaged in debian, could help21:56
nijabattx: sure21:56
ttx#link https://launchpad.net/ceilometer/+milestone/grizzly-221:56
* jamespage hears his nick21:57
ttxLooks on track to me. Who is planning to work on provide-meter-units ?21:57
nijabaguillaume pernot is on it21:57
ttxjamespage: see stevebake request above21:57
*** lcheng has joined #openstack-meeting21:57
jamespagettx: ack21:57
ttxnijaba: maybe add him as assignee then21:57
ttxnijaba: Your CI jobs are now up to par afaict, ready for me to handle your g2 milestone if you wish21:57
nijabawill do as soon as the bp is finished and approved21:57
ttxTo do that I'll need some of your time on that milestone week, as described in:21:57
ttx#link http://wiki.openstack.org/PTLguide#Special_actions_on_Milestone_delivery_week21:58
*** jcru has joined #openstack-meeting21:58
ttx(should be no issue given that we share a timezone)21:58
nijabaack21:58
ttxI would push it after the core projects release, and ping you so that you can make the announcement yourself21:58
*** martine_ has quit IRC21:58
nijabagreat, thanks a lot21:58
ttxLooking at Ceilometer general grizzly plan now:21:58
ttx#link https://blueprints.launchpad.net/ceilometer/grizzly21:58
ttxStill a few "unknown" status and missing priorities21:59
nijabayes, we have been concrentrating on g221:59
*** jpich has joined #openstack-meeting21:59
ttxAlso don't forget to set the series goal to "grizzly" for stuff that is targeted (for example, multi-publisher)21:59
*** grapex has left #openstack-meeting21:59
ttxotherwise the per-series and per-milestone views are not coherent21:59
nijabak21:59
ttxnijaba, stevebake: any quick question before we wrap up ?21:59
*** radez is now known as radez_g0n321:59
stevebakeall good22:00
nijabaall good here22:00
ttxcool22:00
ttx#endmeeting22:00
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"22:00
openstackMeeting ended Tue Dec 11 22:00:15 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/project/2012/project.2012-12-11-21.02.html22:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/project/2012/project.2012-12-11-21.02.txt22:00
openstackLog:            http://eavesdrop.openstack.org/meetings/project/2012/project.2012-12-11-21.02.log.html22:00
ttxgabrielhurley: floor is yours.22:00
nijabathanks ttx22:00
*** Vek has left #openstack-meeting22:00
gabrielhurleythanks22:01
gabrielhurley#startmeeting horizon22:01
openstackMeeting started Tue Dec 11 22:01:30 2012 UTC.  The chair is gabrielhurley. Information about MeetBot at http://wiki.debian.org/MeetBot.22:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:01
*** openstack changes topic to " (Meeting topic: horizon)"22:01
openstackThe meeting name has been set to 'horizon'22:01
gabrielhurleyHello folks. Welcome to the Horizon project meeting.22:01
gabrielhurleyIf there are any quantum folks in the channel, I'd love it if you could stick around for a couple minutes.22:02
*** patelna has joined #openstack-meeting22:02
gabrielhurleywe'll do the same as last time, general status, blueprints and bugs, open discussion22:03
*** ddemir has joined #openstack-meeting22:03
*** jcru has quit IRC22:03
gabrielhurley#topic General Horizon Status22:03
*** openstack changes topic to "General Horizon Status (Meeting topic: horizon)"22:03
gabrielhurleyoh, this will serve as recap of actions from last meeting too22:03
gabrielhurleyso last meeting I was supposed to do two things: talk to ceilometer, and talk to quantum, I've done one of the two22:04
gabrielhurleyI haven't talked to ceilometer, so I need to carry that action forward22:04
gabrielhurley#action gabrielhurley to talk to ceilometer team about moving message "subscription" code into oslo22:04
gabrielhurleyAs far as Quantum goes, it looks like there hasn't been heavy priority from the Quantum team on Horizon/interface concerns in G2. Most of the blueprints in Quantum haven't been started.22:05
gabrielhurleyConsequently there's been little forward progress on my side as well.22:05
gabrielhurleydanwent: still around?22:06
mrunge... and how should an interface for quantum should look like?22:06
gabrielhurleythere's already support for basic management of networks, subnets and ports... lemme find the list of Quantum BPs22:06
mrungeyes, that's right22:06
danwentgabrielhurley: around22:07
gabrielhurleyah, hi dan22:07
gabrielhurleydarnit, the list won't format nicely, but these are the ones Quantum has targeted:   ·         https://blueprints.launchpad.net/horizon/+spec/improve-quantum-summary-table  ·         https://blueprints.launchpad.net/horizon/+spec/quantum-floating-ip  ·         https://blueprints.launchpad.net/horizon/+spec/quantum-l3-support  ·         https://blueprints.launchpad.net/horizon/+spec/quantum-network-topology  ·22:07
gabrielhurleythere's 6 of them22:07
danwentto me, the floatingips, l3-support, and interface ordering are the most important22:08
danwent(I didn't see that last one posted)22:08
danwenthttps://blueprints.launchpad.net/horizon/+spec/quantum-vnic-ordering22:08
danwenthttps://blueprints.launchpad.net/horizon/+spec/quantum-security-group22:08
gabrielhurleythe vnic ordering https://blueprints.launchpad.net/horizon/+spec/quantum-vnic-ordering relies on https://blueprints.launchpad.net/horizon/+spec/orderable-mutiple-choice-field in horizon22:08
danwentgabrielhurley: we are trying to hire someone to work on quantum + horizon stuff22:09
gabrielhurleyso those two may slip to G3 unless somebody from the Quantum team can champion that. Sadly there isn't a quick off-the-shelf django form widget that'll work for what we need there.22:09
danwentif you know of any good leads, please have them contact me22:09
*** henrynash has quit IRC22:09
gabrielhurleygood to know. I'll let you know.22:09
gabrielhurleyThe Quantum security groups one should be a much easier change provided the work there is done in quantum22:10
danwentgabrielhurley: i am going to push amotoki and nati_ueno to give quantum + horizon some love in G-2, so you don't get dumped on by them in G-3 :)22:10
gabrielhurleyI'm perfectly happy to do the reviews whenever they've got the time to drop things in22:10
danwentgabrielhurley: great, thanks.22:10
*** mikal has quit IRC22:11
gabrielhurleydanwent: just keep in touch on how those are progressing.22:11
gabrielhurleyWe've already talked about blueprints some, but moving on...22:11
gabrielhurley#topic Blueprints and bugs22:11
*** openstack changes topic to "Blueprints and bugs (Meeting topic: horizon)"22:11
danwentgabrielhurley: will do.  i'm now going to have a weekly check-in from them during our team meeting on monday22:11
gabrielhurleygreat22:11
gabrielhurleyI made some progress on the one-click "simple" floating IP management blueprint. there's a code review up for that. https://review.openstack.org/#/c/17772/22:12
*** jcooley has joined #openstack-meeting22:12
*** henrynash has joined #openstack-meeting22:12
gabrielhurleyI also investigated the work involved in an orderable multiple choice field for https://blueprints.launchpad.net/horizon/+spec/orderable-mutiple-choice-field22:12
*** mikal has joined #openstack-meeting22:12
gabrielhurleyand determined that it was gonna be a bit of a pain (moreso than expected)22:13
gabrielhurleymy notes/thoughts are on the whiteboard there22:13
gabrielhurleyI also talked to Ray Sun about the per-project flavors blueprint and he indicated it would likely land in G3 since he's been very busy lately.22:13
gabrielhurleySo I bumped that one forward.22:13
*** henrynash has quit IRC22:13
gabrielhurleyOtherwise there hasn't been any significant changes in the BPs that I'm aware of.22:13
*** henrynash has joined #openstack-meeting22:14
gabrielhurleyjpich: any updates on the migrate instance blueprint? https://blueprints.launchpad.net/horizon/+spec/migrate-instance22:14
jpichgabrielhurley: I have the functionality working, but need to polish the user experience22:15
gabrielhurleyawesome22:15
gabrielhurleyglad to hear it22:15
jpichgabrielhurley: it should be all in time for g-222:15
gabrielhurleylet me know if you need any advice, or feel free to push draft versions to github/gerrit22:15
jpichgabrielhurley: Thanks, I will do that22:15
gabrielhurleygreat22:15
*** henrynash has quit IRC22:15
gabrielhurleyso in terms of bugs, we had lots of good bugfix reviews this week, thanks everyone for that22:16
*** jcooley|away is now known as jcooley_22:16
gabrielhurleyAll the "high" bugs are either in progress or fixed22:16
*** durnas has joined #openstack-meeting22:16
gabrielhurleynothing new of consequence22:16
mrungegreat to hear :D22:16
*** durnas has quit IRC22:16
*** durnas has joined #openstack-meeting22:17
gabrielhurleyI know people are working on more fixes which will be proposed this week too... not that it applies to the peope who I know are listening, but don't forget to update the bug statuses in launchpad when you're working on something.22:17
gabrielhurleyAny other notes on bugs from folks?22:17
gabrielhurley#topic General discussion22:17
*** openstack changes topic to "General discussion (Meeting topic: horizon)"22:17
gabrielhurleyI don't have a huge amount to discuss overall today, so questions and comments are welcome.22:18
*** almaisan-away has quit IRC22:18
* gabrielhurley gives it a minute or two22:19
jpichGeneral FYI: we have an OpenStack intern for OPW who has been accepted and is interested in working on Horizon, Victory / vkmc - https://live.gnome.org/OutreachProgramForWomen22:19
zykes-gabrielhurley: going to land reddwarf support or ?22:19
gabrielhurleyah, very cool!22:19
gabrielhurleyzykes-: I don't know anything about it22:19
*** jcooley has quit IRC22:19
zykes-awww22:19
gabrielhurleyI know what reddwarf is22:19
gabrielhurleyjust not about work being done to integrate wiht horizon22:19
zykes-:)22:19
gabrielhurleydo you have an update on that?22:19
zykes-nopp22:20
zykes-just wondering :)22:20
gabrielhurleylol22:20
gabrielhurleyno worries22:20
gabrielhurleyIt shouldn't be too hard, but since it's not even incubated yet I haven't been looking at it specifically22:20
jpich(self-correction, "Victoria", not Victory, sorry)22:20
gabrielhurleymight be even easier if I can land https://blueprints.launchpad.net/horizon/+spec/resource-introspection22:20
zykes-how come gabrielhurley ?22:20
gabrielhurleyjpich: is there anything I can do to help with the intern?22:20
gabrielhurleyzykes-: it'd just reduce the amount of code that'd need to be written to make reddwarf work for the basics22:21
zykes-ah22:21
jpichgabrielhurley: When you have time, I'd like to discuss with you and her what might be a nice blueprint for her to focus on during the 3 months she'll be with us22:21
gabrielhurleygreat. will do.22:22
jpichgabrielhurley: I thought perhaps https://blueprints.launchpad.net/horizon/+spec/tenant-deletion might fit, though there's a risk of it not making grizzly22:22
gabrielhurleyah, yeah, that'd be good22:22
gabrielhurleyanything else from anybody?22:23
jpichgabrielhurley: Cool, I'll catch you by email about it later22:24
gabrielhurleygreat. I'll let y'all get back to your day, then. :-)22:24
gabrielhurley#endmeeting22:24
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"22:24
openstackMeeting ended Tue Dec 11 22:24:20 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:24
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2012/horizon.2012-12-11-22.01.html22:24
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2012/horizon.2012-12-11-22.01.txt22:24
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2012/horizon.2012-12-11-22.01.log.html22:24
*** jcru has joined #openstack-meeting22:25
*** gabrielhurley has quit IRC22:25
*** henrynash has joined #openstack-meeting22:28
*** dolphm has joined #openstack-meeting22:28
*** dolphm has quit IRC22:30
*** dolphm has joined #openstack-meeting22:31
*** mrunge has quit IRC22:31
*** patelna_ has joined #openstack-meeting22:32
*** toddmorey has quit IRC22:32
*** sandywalsh has quit IRC22:35
*** vkmc has joined #openstack-meeting22:35
*** patelna has quit IRC22:36
vkmchi!22:36
*** markvoelker has quit IRC22:37
annegentle_vkmc: hey! Welcome!22:37
vkmcannegentle_, hi there! thx :)22:37
vkmcannegentle_, i'm afraid i'm too late for the meeting, i've just read about it22:38
annegentle_vkmc: no worries :) I think they just started weekly this week anyway!22:38
*** dolphm has quit IRC22:39
annegentle_vkmc: The Horizon meeting is at the bottom of this list, for future reference http://wiki.openstack.org/Meetings22:39
vkmcannegentle_, right :) well, i'll add it to my schedule :) i would really like to get more involved with the community22:39
annegentle_vkmc: we'll get you there!22:40
vkmcannegentle_, nice!22:40
*** fungi has quit IRC22:40
*** dolphm has joined #openstack-meeting22:40
*** annegentle_ has quit IRC22:43
jpichvkmc: Hi! Sorry for the reaaally short notice, I'll do better next time :)22:44
*** fungi has joined #openstack-meeting22:44
*** annegentle_ has joined #openstack-meeting22:46
*** nati_ueno has quit IRC22:46
*** EmilienM has left #openstack-meeting22:46
*** nati_ueno has joined #openstack-meeting22:47
*** Ryan_Lane has left #openstack-meeting22:47
*** colinmcnamara has joined #openstack-meeting22:49
*** mattray has quit IRC22:52
*** blamar has quit IRC22:53
*** sarob has quit IRC22:54
*** jcru has quit IRC22:57
*** mtreinish has quit IRC23:04
*** annegentle_ has quit IRC23:04
*** dtalton has quit IRC23:06
*** markwash_ has joined #openstack-meeting23:08
*** jpich has quit IRC23:09
*** markwash has quit IRC23:11
*** bearovercloud has left #openstack-meeting23:13
*** ddemir has left #openstack-meeting23:16
*** EmilienM has joined #openstack-meeting23:20
*** EmilienM has left #openstack-meeting23:21
*** jhenner has quit IRC23:22
*** nati_ueno_2 has joined #openstack-meeting23:23
*** nati_ueno has quit IRC23:24
*** lcheng has quit IRC23:26
*** alexpilotti has quit IRC23:36
*** alexpilotti has joined #openstack-meeting23:36
*** cp16net is now known as cp16net|away23:43
*** cp16net|away is now known as cp16net23:43
*** colinmcnamara has quit IRC23:45
*** alexpilotti has quit IRC23:45
*** alexpilotti has joined #openstack-meeting23:45
*** alexpilotti_ has joined #openstack-meeting23:49
*** alexpilotti has quit IRC23:50
*** alexpilotti_ is now known as alexpilotti23:50
*** blamar has joined #openstack-meeting23:55

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