Tuesday, 2011-06-07

*** Binbin has joined #openstack-meeting00:31
*** jakedahn has quit IRC00:47
*** jakedahn has joined #openstack-meeting00:47
*** adjohn has joined #openstack-meeting01:06
*** dcramer_ has joined #openstack-meeting01:14
*** kd9261 has joined #openstack-meeting01:17
*** spectorclan_ has joined #openstack-meeting01:51
annegentlewe'll get started in about a minute, hi everyone01:59
spectorclan_hi01:59
*** alandman has joined #openstack-meeting01:59
deshantmhi01:59
dcramer_Hello.02:00
deshantmo/02:00
annegentleglad the time didn't throw everyone off too much :) I've got 9:00 so I'll get started02:01
annegentle#startmeeting02:01
openstackMeeting started Tue Jun  7 02:01:30 2011 UTC.  The chair is annegentle. Information about MeetBot at http://wiki.debian.org/MeetBot.02:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.02:01
annegentle#Goal-setting for this meeting02:01
*** toddmorey has joined #openstack-meeting02:02
annegentleI basically wanted to get doc/web aficionados together regularly to talk about what's going on with docs and the website02:02
*** med_out is now known as med02:02
*** med is now known as medberry02:02
annegentleespecially now that we're looking for ways to open up the openstack.org site for more people to work on it02:03
annegentleI think it's good to review doc bugs, too.02:03
annegentlePlus, try to coordinate doc tasks.02:03
spectorclan_annegentle: can you clarify your open up the openstack.org site for others to work on02:04
annegentleAny other goals you want to bring up? Have for this meeting? I'm open to suggestions and agenda items02:04
kd9261I think it would be beneficial to standardize a layout for tutorial wiki pages. i.e. installation guides02:04
annegentlesure, toddmorey has been working on ways to get a core group of reviewers for the openstack.org site just like we do code reviews02:04
spectorclan_annegentle: that makes sense, ok. had not heard that before02:05
annegentlekd9261: honestly, I think my hope is to consolidate installation information to just a few pages02:05
*** j1mc has joined #openstack-meeting02:05
annegentlekd9261: I like wiki templates and all, but MoinMoin (our wiki engine) just isn't robust enough for end-user docs really, it's better suited for project docs02:06
kd9261annegentle: That's a good idea, there are just some specifics b/w different distributions/OS02:06
annegentlekd9261: yes, I'd love to start a separate installation guide in fact in DocBook in the openstack-manuals project, but possibly the instructions are quite ready for that? Any thoughts?02:06
annegentlekd9261: I appreciate the wiki edits if you're the one who worked on 'em today by the way :)02:07
annegentleVish asked me to consolidate install information this release, so it's certainly a good doc task02:08
kd9261annegentle: I am a strong believer of readbility. Especially when new Open Stack users come along (I am one)02:08
j1mcannegentle: did you mean that the installation instructions "aren't" quite ready for that?02:08
annegentlej1mc: more like, are the installations on distros equivalent yet?02:08
annegentlej1mc: oh yes, "are/aren't" thanks :)02:08
j1mcah, ok - thanks for clarifying02:08
kd9261annegentle: From my [little] experience, they are different enough to justify having separate pages, the landing page is very clear though02:09
annegentleone additional goal for this meeting is to get input on doc priorities02:09
annegentlekd9261: ok, good to know02:09
annegentlekd9261: and I think your instinct is correct02:09
annegentleI think for installation instructions for each distribution, we need a pre-req of a nice page for downloads. Todd and I have talked about this being on openstack.org, any thoughts?02:10
*** troytoman is now known as troytoman-away02:10
annegentlewe like this as a model, anyone else have good examples? http://www.postgresql.org/download/02:11
spectorclan_So, have a listing of distros on the product download page which has different instructions?02:11
*** mattray has quit IRC02:11
annegentlespectorclan_: yes, or at least installation instructions can consistently point to the correct place02:12
spectorclan_ok, just saw the link. It makes sense and works easily. I like very much02:12
annegentleneed to redo the topic, hang on02:12
* j1mc looks at a couple of 'installation doc' examples that come to mind...02:12
annegentle#topic Goal-setting for this meeting02:12
*** openstack changes topic to "Goal-setting for this meeting"02:12
kd9261something like this is very appealing: http://www.ubuntu.com/download02:12
kd9261the postgres is more "professional" looking02:13
spectorclan_kd9261: I think it just depends on the look/feel of the existing site02:13
kd9261#agree02:13
annegentlekd9261: yeah, to me, ubuntu appeals to any end-user, we need to appeal to cloud/server admins02:13
deshantmannegentle: agree that audience matters, I was just going to make a similar comment02:14
annegentlespectorclan_: true, we already have an established look and feel to openstack.org. Right now our "downloads" are somewhat hosted on the wiki. Should they stay there?02:14
spectorclan_No, they need to move to openstack.org; I agree with your thinking02:14
annegentlekd9261: but simple is good too :)02:14
toddmoreythe problems occur when instructions 'branch' to account for variances across installs. So it's good to have some sort of tool to get your target platform, etc, so that the instructions / links can be very clear and very specific02:15
medberryI see no dependencies on the Postgresql page. Is that your intent.02:15
j1mchttp://docs.fedoraproject.org/en-US/Fedora/14/html/Installation_Guide/02:15
kd9261medberry: those should be in the specific distro page02:15
j1mcannegentle: i know that the ubuntu folks are also working on ensemble and cloud documentation. it is in the early stages, but it might be worthwhile to see where you can work together around infrastructure or general topics.,02:15
alandmanI think there needs to be something more clearly organized then the wiki since finding the content on it can be far from easy02:15
annegentlemedberry: ah good point, but yeah they change based on OS, right?02:15
medberryannegentle, kd9261: nod.02:16
spectorclan_annegentle: I assume we mean the released versions and not daily production? Relased go on main site and daily development off wiki02:16
annegentlej1mc: ok, I'll reach out, Jim Campbell was at the Open Help conference with me this weekend and we talked some about Ubuntu's server doc - they do like our webhelp output example02:16
annegentlespectorclan_: yes, released, tested, from 3rd party sources, that sort of category02:17
spectorclan_3rd party? Hmm, would we then post a release from StackOps?02:17
j1mcyes! the lead of the server group liked it a lot! kudos to the anne and the others (??) who worked on getting the current openstack docs set up.02:17
annegentlej1mc: yes that's a great install guide, guess it might be time to separate out to a new install guide02:17
annegentlej1mc: awesome, thanks to toddmorey and dcramer_02:18
annegentleok, I think we're okay with goal-setting, on to next (thanks for the input on install as well)02:18
j1mcannegentle: that fedora docs setup is done in docbook, and it all output through fedora/redhat's publican02:18
annegentleoh and should I do some actions for install doc and download page? Anyone?02:18
annegentlej1mc: yes I learned a bit about publican this weekend at Open Help as well :)02:19
annegentle#topic General documentation status - RST on each project02:19
*** openstack changes topic to "General documentation status - RST on each project"02:19
kd9261annegentle: I have 3 months to dedicate to wiki install doc editing02:20
kd9261my group is very active on an Open Stack trunk02:20
annegentlekd9261: you hooked on wiki? :) Can we talk more about an install book in docbook or you like wiki better?02:20
kd9261annegentle: I am not up to speed on terminlogy, sorry02:21
annegentlekd9261: ok, no worries :)02:21
kd9261I like the install book a lot, however it would have to gaurantuee complete accuracy otherwise lessons learned by one user don't propogate as well02:21
annegentle#link http://wiki.openstack.org/Documentation/HowTo02:21
annegentlethat page describes the areas where doc lives, wiki is just a small part02:21
annegentleaccuracy is a huge part of Vish's request, answering the same questions over and over is no fun02:22
annegentleso I completely agree02:22
annegentleSo the swift.openstack.org site is built from RST housed in the Swift source code, and it was updated with their 1.4 release02:23
annegentleOther than the swift RST docs, that is the only activity so to speak that I know of.02:23
kd9261annegentle: from a new user perspective, it is nice to have lots of documentation but confusing when it is duplicated in multiple places02:24
kd9261its unclear which is most accurate, despite that install book looks much mre polished02:24
annegentlekd9261: agreed.02:24
annegentlekd9261: the install docs are the top priority there02:24
annegentlekd9261: as far as removing duplicates02:25
annegentleideally, the RST pages host the dev information and the automated doc from doc strings, the "polished" guides are built from docbook in the lp:openstack-manuals project02:25
annegentlekd9261: so that gives the high-level overview of what goes where and also hints at why duplication occurs - both audiences need to know some information02:25
deshantmit's an audience thing again. devs vs. sysadmins right?02:26
annegentle#topic General documentation status - DocBook docs in openstack-manuals project02:26
*** openstack changes topic to "General documentation status - DocBook docs in openstack-manuals project"02:26
kd9261annegentle: agreed. Being a new developer and user I can appreciate both views. Development hinges on being able to successful install first.02:27
annegentledeshantm: yes, and it's further segmented as Python devs should be the audience for RST sites, web devs using the APIs are also audience for docbook02:27
annegentlekd9261: yes, absolutely. I find the sysadmins can install no problem but configuration confounds them.02:27
annegentleThe status of the DocBook docs - I have merged all requests in and I busily update it about daily.02:28
kd9261annegentle: this is exactly the case.02:28
deshantmkd9261: agreed.. there is actually a different problem with some of the XenServer docs in that dev docs exists, but the story for sysadmins is not that good yet02:28
annegentleI'm working on incorporating CC licensed content in the DocBook content from bloggers whom I've contacted, such as kpepple02:29
* deshantm is working to fix that one02:29
annegentleI learned alot about DocBook and translations over this past weekend and would also like to take steps towards doc translations (though maybe organizing the English base is a higher priority)02:30
kd9261There is very little in the way of Dashboard as well. I am working alongside a colleague who has come to this realization02:30
annegentlethere are maybe 3 code branches in the lp:openstack-manuals project that have no merge request, but I've talked with all the authors to get the status.02:31
j1mcannegentle: I just emailed you the contact info for the Ubuntu translations coordinator in case it might be helpful.02:31
annegentlej1mc: thanks a bunch :)02:31
annegentletoday I added a short chapter about hypervisors02:32
annegentleand we now have automated builds that automatically copy the trunk docs to docs.openstack.org/trunk, but there is no landing page with CSS yet02:33
annegentle#link http://docs.openstack.org/trunk/02:33
annegentle(yep, ugly, but automated is good)02:33
kd9261#agreed02:33
annegentleI'll work on the CSS this week, should it just be a simple listing, or should I add a "trunk" option to the docs.openstack.org page?02:34
toddmoreythat's what I was wondering...02:34
deshantmmaybe better to have the trunk look different02:35
toddmoreyMaybe on docs.openstack, but visually separated just a bit02:35
toddmoreyand below the other options, I would think02:35
deshantmso that users don't think it is official by mistake when it is still in progress02:35
annegentlealso, the automated builds do not activate comments, my ideal is to keep comments with a release and have people log bugs against trunk rather than commenting02:35
annegentledeshantm: good point02:35
spectorclan_would a user really want to see the trunk docs version?02:35
toddmoreyI like the idea of some sort of "trunk" banner at the top of those pages… just in case you stumble into one via google search02:36
deshantmspectorclan_: OpenStack users probably will02:36
annegentlespectorclan_: I think so, one example of a Diablo thing you can do that you can't do in Cactus (silly example) is that you can get the version number easily02:36
toddmoreyshoot, we could even tell google not to spider trunk… not sure how people feel about that02:36
deshantmannegentle: agree with that02:36
spectorclan_ok, just checking. As long as we clarify what each section is, we should be fine02:36
annegentlespectorclan_: but for the most part, it's best for people to read the Cactus docs as they are still being constantly updated as if they are trunk02:37
dcramer_We've added support for a banner to the webhelp format recently.02:37
annegentledeshantm: yes I like the idea of a banner02:37
annegentle#link http://docs.openstack.org/cactus/openstack-compute/developer/openstack-compute-api-1.1/content/index.html02:37
annegentleshows the - DRAFT - banner on the API 1.1 document02:38
spectorclan_cool02:38
annegentletoddmorey: I like telling Google not to search trunk, it only adds to the "duplication" I scream in my head :)02:38
annegentleoh one other status update for the lp:openstack-manuals project, we can now get Site Search analytics and the top search within the docs.openstack.org site is... wait for it...02:39
annegentlebilling!02:39
deshantmannegentle re: Google ...yeah, clouds, you can't trust them ;)02:39
annegentledeshantm: hee02:39
toddmoreybilling?02:40
j1mcannegentle: neat idea in telling google to not search trunk02:40
annegentlemy guess is, they want to know if you get plug-n-play billing when you get OpenStack running02:40
deshantmtoddmorey: yeah, service providers just want to make money off of our work :)02:40
spectorclan_hey stop being a socialist Todd, Money makes the world go around!02:41
spectorclan_:)02:41
toddmoreyah… yes indeed. and here I thought altruism powered the world02:41
annegentlesoon, I hope we'll also be tracking searches on individual books though none have come through the system yet so we probably need to troubleshoot that02:41
*** dcramer_ has quit IRC02:41
annegentletoddmorey: do you mind talking some about the openstack.org project's status?02:42
annegentle#topic General status for openstack.org project02:42
*** openstack changes topic to "General status for openstack.org project"02:42
toddmoreyI get it now. I was thinking from a user perspective, and wondering who had CC statements with OpenStack, LCC on them. :)02:42
toddmoreySure thing!02:42
annegentletoddmorey: heh, right. This is the words being input on docs.openstack.org in the Google Custom Search Engine02:42
annegentlethanks02:42
toddmoreyWe recently launched an update to openstack.org that brought the site into a CMS. The idea was to prepare it for having more folks collaborate on the project. I'm documenting how to get involved with that piece as we speak.02:43
deshantmtoddmorey: which CMS did you guys go with?02:44
toddmoreyFirst priority is setting up a launchpad project for the website. The big beni there is having a place to track bugs / issues.02:44
spectorclan_does this replace the existing launchpad tracking?02:44
toddmoreyThe CMS is called Silverstripe. It's an open source PHP framework… the closest thing in PHP to django.02:45
toddmoreyThe site now has versioned content and consumes other data via RSS or JSON, depending on the source02:45
toddmoreythat's how we pull things like the latest commits from launchpad or photos from flickr. If anyone has more ideas for data sources, I'd love to start adding more. General theme is hilighting the activity of the community.02:46
spectorclan_we need to bring in slideshare as well as vimeo - people love videos02:47
toddmoreyspectorclan_: I mean a project to show up here: https://bugs.launchpad.net/openstack/+filebug02:48
j1mctoddmorey: intersting. i'd certainly like to know when you get the documentation in place. where is the documentation at now? is it available somewhere?02:48
annegentle#link http://wiki.openstack.org/Website02:49
toddmoreyj1mc: it will be in the wiki. Anne's got the right place, I have a lot more to add that I've written. I just wanted to proofread it first. :)02:49
spectorclan_toddmorey: sorry, still confused. Are you saying we need a documentation bug project on the Project list?02:49
*** dwcramer has joined #openstack-meeting02:50
toddmoreyno, sorry… I mean the website itself should be a (minor) openstack project, the way manuals currently is. Make sense?02:50
annegentleI'm thinking more like we need a project for openstack-web (or something) so bugs can be listed like https://bugs.launchpad.net/openstack-manuals02:50
spectorclan_toddmorey: yep, get it02:51
*** Binbin has quit IRC02:51
toddmoreywhat Anne said. :)02:51
toddmoreybugs and to have ammo for these meetings to prioritize the next projects for the site02:51
deshantmoh i found a bug the participating companies is different on the home page and community page02:52
* j1mc nods02:52
deshantm76 vs. 6502:52
toddmoreyfor example, one of the big priorities in my mind is listing all the openstack projects on the site, not just the core ones. That's one thing I'm working on now.02:52
annegentledeshantm: good catch02:52
spectorclan_deshantm:  we add about 2 or 3 partners a day - very busy getting legal processing completed;02:53
toddmoreythat is a good catch. I only made one auto-update. I need to fix the other so it increments, too.02:53
spectorclan_deshantm: also working with Todd on idea for a Solution Search Catalog instead of just a partner listing02:53
j1mci'm afraid that i'm a bit on the sleepy side for now. if the meeting minutes / log will be posted somewhere, i will be sure to read through them, though.02:53
annegentleok, do we name the project openstack-web, openstack-website?02:53
spectorclan_openstack-website sounds better to me02:54
deshantmbetter do website02:54
annegentlej1mc: yeah we'll put the notes up02:54
deshantmweb might be a admin panel someone write02:54
annegentletrue, who knows it might be taken02:54
toddmoreyopenstack-website: very clear02:54
annegentle#action toddmorey and annegentle to work with ttx on making openstack-website project02:55
j1mcthanks... it sounds like you're off to a good start. i'll catch up with you all later.02:55
annegentlej1mc: thanks Jim02:55
toddmoreythanks, j1mc!02:55
j1mcyw :)  good night!02:55
annegentleok, last topic, bugs02:55
spectorclan_toddmorey: we need to put translations onto our long term list so we can have multiple languages02:55
*** zul has quit IRC02:55
annegentle#topic Doc bugs02:55
*** openstack changes topic to "Doc bugs"02:55
annegentleFor example, see https://bugs.launchpad.net/nova/+bugs?field.tag=documentation02:56
toddmoreyspectorclan_: translation support is ready when we are!02:56
annegentleWe are currently tracking doc bugs per project and also within the lp:openstack-manuals project02:56
spectorclan_toddmorey: ok, let's talk offline as I have people ready to help us now02:56
annegentleThe bug lists are managed by ttx and myself mostly, we move them between projects as needed also02:56
annegentleBugs are a great starting point for trying out your DocBook and RST skills, and learning the project landscapes as well.02:57
* annegentle sells people on starting with doc bugs when just getting going!02:57
annegentleand I will wrap up in 3 minutes, with the last topic02:57
annegentle#topic Open discussion02:58
*** openstack changes topic to "Open discussion"02:58
toddmoreyannegentle: good sell!02:58
medberrytx annegentle02:58
spectorclan_awesome!02:58
medberrythanks all.02:58
annegentlemedberry: thanks for the comments on the doc site, keep 'em coming :)02:58
deshantmannegentle: is there RSS subcribe for bugs?02:58
annegentledeshantm: hm, good question, there's a link on the page to subscribe by email but dunno about RSS02:59
annegentle#action annegentle to ask ttx about RSS and subscribing to doc bug feeds02:59
spectorclan_i only see bug email02:59
deshantmI have a lot of emails that I filter so I might miss the bugs in email03:00
deshantmI would rather have a way to make sure I get all xen-related documentation things03:00
annegentledeshantm: yeah and I'm realizing I'd like to flag doc bugs in my email so it's a good question03:00
deshantmI follow the XenServer wiki page via email, so that is OK03:00
medberryyou can probably use a 3rd party RSS-izer...03:01
deshantmbut I don't like launchpad bug mail since it tends to be noisy and hard to filter03:01
annegentleOK, good. Well thanks everyone for coming.03:01
toddmoreythanks, annegentle! this is a good step forward.03:01
annegentleI'll post notes to the wiki page linked from http://wiki.openstack.org/Meetings/DocTeamMeeting03:01
spectorclan_exit03:01
spectorclan_oops03:01
annegentle#endmeeting03:01
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"03:01
openstackMeeting ended Tue Jun  7 03:01:58 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)03:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-06-07-02.01.html03:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-06-07-02.01.txt03:02
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-06-07-02.01.log.html03:02
*** spectorclan_ has quit IRC03:02
annegentletoddmorey: yes, I'm jazzed!03:02
deshantmbye03:02
annegentledeshantm: g'night03:02
*** alandman has quit IRC03:02
medberrygnite03:02
*** medberry is now known as med_out03:02
*** toddmorey has quit IRC03:03
*** dwcramer has quit IRC03:08
*** j1mc has quit IRC03:09
*** kd9261 has quit IRC03:32
*** Binbin has joined #openstack-meeting03:48
*** Binbin has quit IRC04:09
*** dovetaildan has quit IRC04:43
*** dovetaildan has joined #openstack-meeting04:44
*** Binbin has joined #openstack-meeting05:14
*** Binbin has quit IRC05:48
*** Binbin has joined #openstack-meeting05:57
*** Binbin has quit IRC06:32
*** Binbin has joined #openstack-meeting06:35
*** Binbin has quit IRC06:42
*** mancdaz has quit IRC08:47
*** Binbin has joined #openstack-meeting08:49
*** mancdaz has joined #openstack-meeting08:49
*** mancdaz has quit IRC08:54
*** mancdaz has joined #openstack-meeting08:55
*** adjohn has quit IRC09:03
*** Binbin has quit IRC09:22
*** zul has joined #openstack-meeting10:14
*** JordanRinke has quit IRC11:32
*** JordanRinke has joined #openstack-meeting11:37
*** Binbin has joined #openstack-meeting11:54
*** dwcramer has joined #openstack-meeting12:00
*** soren has quit IRC12:06
*** dprince has joined #openstack-meeting12:11
*** soren has joined #openstack-meeting12:13
*** dwcramer has quit IRC12:31
*** Binbin has quit IRC12:49
*** Binbin has joined #openstack-meeting13:20
*** mattray has joined #openstack-meeting13:29
*** edconzel has joined #openstack-meeting13:46
*** med_out has quit IRC13:50
*** Binbin has quit IRC13:56
*** medberry has joined #openstack-meeting14:11
*** medberry has joined #openstack-meeting14:11
*** rnirmal has joined #openstack-meeting14:15
*** medberry has quit IRC14:19
*** dwcramer has joined #openstack-meeting14:20
*** medberry has joined #openstack-meeting14:21
*** medberry has joined #openstack-meeting14:21
*** johnpur has joined #openstack-meeting14:49
*** jkoelker has joined #openstack-meeting14:52
*** markwash has quit IRC15:10
*** markwash has joined #openstack-meeting15:10
*** dendrobates is now known as dendro-afk15:28
*** dendro-afk is now known as dendrobates15:30
*** troytoman-away is now known as troytoman15:33
*** dendrobates is now known as dendro-afk15:58
*** dendro-afk is now known as dendrobates15:58
*** dendrobates is now known as dendro-afk16:11
*** dendro-afk is now known as dendrobates16:18
*** mattray has quit IRC16:27
*** dendrobates is now known as dendro-afk16:36
*** s1rp has quit IRC16:41
*** mattray has joined #openstack-meeting17:05
*** jakedahn has quit IRC17:37
*** carlp has joined #openstack-meeting18:11
*** dendro-afk is now known as dendrobates18:18
*** Tv has joined #openstack-meeting18:20
*** jakedahn has joined #openstack-meeting18:30
*** dwcramer has quit IRC18:51
*** zul has quit IRC19:22
*** dprince has quit IRC19:43
*** dendrobates is now known as dendro-afk20:01
*** markvoelker has joined #openstack-meeting20:01
*** AWR has joined #openstack-meeting20:02
*** creiht has joined #openstack-meeting20:03
termiettx: is there a public calendar i can subscribe to in gcal to see when the openstack meetings are?20:08
termienotmyname, vishy: ^^20:08
notmynameya. just a sec20:09
notmynamehttp://tinyurl.com/openstack-meetings20:09
termieyeah that gives me direct to an ics20:09
termiebut i'd rather just add the user it belongs to20:09
termiemaybe that will just work though20:10
*** dragondm has joined #openstack-meeting20:15
termieya, that works20:15
termiethanks20:15
mtaylortermie: wow. that so didn't do anything for me on google calendar20:22
*** ohnoimdead has joined #openstack-meeting20:24
termieyou have to get the acutal link20:33
termiehttps://www.google.com/calendar/ical/bj05mroquq28jhud58esggqmh4%40group.calendar.google.com/public/basic.ics20:33
termiemtaylor: ^20:33
ttxtermie: interesting. I guess I should just give the full URL on the wikipage then20:40
*** bcwaldon has joined #openstack-meeting20:42
*** dabo has joined #openstack-meeting20:48
*** spectorclan_ has joined #openstack-meeting20:50
*** vladimir3p has joined #openstack-meeting20:50
*** alandman has joined #openstack-meeting20:55
*** primeministerp has joined #openstack-meeting20:55
notmynametermie: PPB schedule https://www.google.com/calendar/ical/6i49nddt8eqqi1kv0uoc8noh94%40group.calendar.google.com/public/basic.ics20:56
ttxmtaylor: just added the testing and CI meeting on it20:57
notmynamettx: so your calendar will now have the PPB meetings?20:58
ttxnotmyname: I gave jbryce admin access to the common "meeting" one20:58
notmynameah ok20:58
notmynamethanks.20:58
notmynameI much prefer only one calendar :-)20:58
ttxit should be all set now20:58
ttxmtaylor: I can give you access to it too, if you want to be able to change every week :)20:58
annegentlettx: can I have access? I am likely to change the doc/web team meeting to not-so-late20:59
*** jakedahn has quit IRC21:00
*** Vek has joined #openstack-meeting21:00
bcwaldonannegentle: good idea. I was planning to attend but it totally slipped my mind21:00
*** mgius has joined #openstack-meeting21:00
ttxannegentle: sure -- it's a google calendar thing, if you have an account for that21:00
annegentlettx: coolio, anngentle@gmail.com21:01
*** jk0 has joined #openstack-meeting21:01
*** danwent has joined #openstack-meeting21:01
ttxannegentle: should be ok now21:01
annegentlethanks21:01
ttxjaypipes, vishy: around ?21:02
*** dubs has joined #openstack-meeting21:02
*** anotherjesse has joined #openstack-meeting21:02
*** anotherjesse is now known as jesse_andrews21:02
sorenannegentle: Really? Not annegentle@ (note the extra e)?21:02
ttxvishy is traveling, I'll stand in for him as much as I can21:02
ttxlet's start21:03
ttx#startmeeting21:03
openstackMeeting started Tue Jun  7 21:03:08 2011 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.21:03
*** s1rp has joined #openstack-meeting21:03
ttxWelcome to the OpenStack team meeting...21:03
ttxThe agenda for today lives at:21:03
ttx#link http://wiki.openstack.org/Meetings/TeamMeeting21:03
ttx#topic Actions from previous meeting21:03
*** openstack changes topic to "Actions from previous meeting"21:03
ttx* ttx to create webnumbrs for Swift/Glance21:03
ttxThat was done at:21:03
ttx#link http://wiki.openstack.org/releasestatus/swift.html21:03
ttx#link http://wiki.openstack.org/releasestatus/glance.html21:04
ttxnot enough data to make it interesting yet21:04
*** byeager has joined #openstack-meeting21:04
*** johan___ has joined #openstack-meeting21:04
ttx* dabo to make progress towards merging the nova python client library projects21:04
ttxdabo: wanna talk about the status ?21:04
dabostill in discussion with jacobian about adding committers from OpenStack to his project on GitHub21:05
jesse_andrewsdabo: what is the general though?21:05
dabohe's all for combining21:05
jesse_andrewsdabo: as for which is the basis?21:05
ttxjesse_andrews: his project21:05
dabowe thought keeping it external would be a good check on the APIs21:06
*** ewanmellor has joined #openstack-meeting21:06
dabobut allow for OpenStack committers so that he's not a bottleneck21:06
ttxdabo: cool21:06
dabohe was +1 for that21:06
jesse_andrewsdabo: cool - our team has been working on making his project exensible (to make it easy to make client api extensions to make server extensions)21:06
jesse_andrewsto *MATCH* server extensions21:07
ttx* mtaylor to set up a "functional testing" meeting to coordinate efforts21:07
ttxmtaylor: around ?21:07
daboI only asked for sandy, jk0 and myself to be added. Let me know whatever github names you will also need as committers21:07
*** User432 has joined #openstack-meeting21:07
ttxThat was done, meeting will be Tuesdays at 1900 UTC21:07
*** Tushar has joined #openstack-meeting21:07
devcamcardabo: i'd like to be added as well21:07
bcwaldondabo: same here21:07
dabook - send me your github names and I'll pass 'em along21:08
ttx#topic Swift status21:08
*** openstack changes topic to "Swift status"21:08
devcamcardabo: it's ... wait for it ............ devcamcar21:08
jk0dabo: jk0 :)21:08
*** somik has joined #openstack-meeting21:08
devcamcar:)21:08
dabowhoda thunk it?21:08
ttxnotmyname: hi! Any updated plans for 1.4.1 ?21:08
*** masumotok has joined #openstack-meeting21:08
notmynamettx: no updates yet. We're still working on the same stuff from last week. I hope to have a better idea of date for 1.4.1 by next week21:09
ttxack21:09
jesse_andrewswe don't need everyone to be added since we can just send pull requests right?21:09
ttxWe also need to decide in which PPA to put 1.4.0...21:09
pvojesse_andrews: the bottleneck was him incorporating those reqs. iirc.21:09
devcamcarjesse_andrews: don't be a code blocker21:09
notmynamettx: indeed21:09
ttxI think we need a PPA tracking the last Swift milestone/release, and one PPA tracking the last OpenStack coordinated release21:09
ttxFor Swift we already have a "Release PPA" with 1.3.0... That means two solutions:21:10
jesse_andrewspvo: right - i'm just saying a few added people is good21:10
* pvo nods.21:10
ttx1/ reuse the "Release PPA" for 1.4.0, and create a "OpenStack release PPA" with 1.3.021:10
ttx2/ create a "Milestone PPA" for 1.4.0 and leave the Release PPA as-is.21:10
dabojesse_andrews: pvo: yeah, as long as one of the stackers can merge into the project21:10
ttxnotmyname: Any preference ?21:10
notmynamettx: I prefer the first since our milestones are stable releases21:10
ttxRight, I think (2) would confuse people around what is a Swift release21:10
jesse_andrewsdabo: did we setup a launchpad project to pull from the githubs?21:10
jesse_andrewsdabo: for ppa21:11
ttxFor (1) we would probably set up a common "OpenStack release PPA" containing all core projects21:11
dabojesse_andrews: not that I know of21:11
notmynameyes21:11
ttx#action ttx to push update of Swift release PPA to 1.4.0 and creation of a common OpenStack release PPA21:11
ttxnotmyname: Another question I had -- should we mark the fixed-in-1.4.0 bugs "FixReleased" ? Or wait for the common OpenStack release ?21:12
notmynamethey should be marked fixed released21:12
ttxnotmyname: ok, will make that happen, expectr bugnoise.21:12
ttxnotmyname: Other announcements or comments ?21:12
notmynamenothing yet21:13
ttxQuestions for the Swift team ?21:13
ttxjaypipes: around ?21:13
jaypipesttx: yes sir!21:13
ttx#topic Glance status21:13
*** openstack changes topic to "Glance status"21:13
ttxjaypipes: hi! So same question for you...21:13
Vek(of course he's round, he's a pipe!)21:13
* Vek ducks quickly21:13
ttxDo you think we should mark the fixed-in-diablo-1 bugs "FixReleased" ? Or leave them "FixCommitted" until the final release ?21:14
ttxFor Nova/Glance the latter probably makes more sense...21:14
*** antonyy has joined #openstack-meeting21:14
jaypipesbcwaldon and myself had a good chat today splitting up D2 tasks. I'm going to be focusing on auth (keystone integration) and brian's focusing on refactoring the WSGI stuff to pull in some goodies from the latest nova code, plus some XML-ification of the API21:14
jaypipesttx: fix committed is fine for now.21:14
johnpuris keystone integration complete in d2 for glance?21:15
ttxjaypipes: Plan at https://launchpad.net/glance/+milestone/diablo-2 looks good to me21:15
jaypipesI've been working pretty hard on understanding Keystone and have been logging issues like crazy over on github...21:15
ttxjaypipes: I assume status is up-to-date, i.e. most things are not started ?21:15
ttx(still in investigation phase)21:15
jaypipesthe spec and API are changing quite rapidly, which makes things challenging, but making progress nonetheless21:15
jaypipesttx: exactly.21:15
devcamcarfolks on swift team, what is your timeframe for keystone support?21:15
ttxjaypipes: Do you agree we should switch to milestone-proposed one day earlier, to give ~2 days for testing/fixes ?21:16
notmynamedevcamcar: diablo release, I believe21:16
jaypipesttx: expect bcwaldon and me to put some of those bps into a started status tomorrow through friday21:16
jaypipesttx: that's fine, sure21:16
jesse_andrewsnotmyname: is gholt around? he has said he would be able to do a middleware pretty easy21:16
ttxThat means features for Glance diablo-2 must get merged before EOD June 27... Mark your calendars.21:16
jesse_andrewsnotmyname: that does lazy provisioning21:16
jaypipesttx: yes, that is correct21:16
devcamcarnotmyname: know which milestone by chance? its a dependency for swift support in dashboard21:17
notmynamedevcamcar: jesse_andrews: I'll check with gholt21:17
devcamcarthx21:17
jaypipesttx: that's it from me.21:17
jesse_andrewsdevcamcar: at the summit gholt thought it should just take less than a day to knock it out, since it is very similar to what already exists21:17
ttxAny question about Glance ?21:17
jesse_andrewsjaypipes: the thought by D2 to have private image support?21:18
ttxjesse_andrews: was that before or after beer oclock ?21:18
jesse_andrewsttx: before21:18
jaypipesjesse_andrews: no. I pushed the shared-image-groups blueprint out to D3 because I've had to spend a lot of time logging issues in Keystone and weriting unit tests... taking longer than I'd planned.21:18
jaypipesjesse_andrews: but I think very doable for D3.21:18
ttxother Glance questions before we move on to Nova ?21:19
jaypipesjesse_andrews: to be clear: authn and basic integration with keystone will be done in D2. but not the shared-image-groups middleware/extension piece.21:19
jesse_andrewsjaypipes: cooleo21:19
*** ying has joined #openstack-meeting21:19
ttx#topic Nova status21:20
*** openstack changes topic to "Nova status"21:20
ttxunless vishy makes a surprise entry, I'll talk for him21:20
johnpurvishy is turining japanese!21:20
ttxThe plan is also to branch Nova milestone-proposed 2+ days before release, so features for Nova diablo-2 should land before the end of Monday, June 27.21:21
pvojohnpur: you really think so?21:21
pvo;p21:21
ttxI've been busy sanitizing the diablo-2 plan, trying to see what should be reasonably done by then, and checking out assignees21:21
ttxA bit scary with like 27 blueprints targeted21:21
ttxSee plan @ https://launchpad.net/nova/+milestone/diablo-221:21
ttxI'm still missing some input, the plan should be finalized in the next days.21:21
jaypipesttx: markwash told me he'd pick up 10 or 12 blueprints.21:22
ttxIf you're assigned something on this plan and you know you won't deliver by June 27, please let me or vishy know.21:22
* jaypipes runs and hides...21:22
*** dendro-afk is now known as dendrobates21:22
pvottx: I'll make sure I get our plans to you soon.21:22
ttxQuestions ?21:22
jesse_andrewsttx: my assumption was the "low" ones were icing on the cake21:22
ttxjesse_andrews: yes -- we could actually keep them untargeted and target them retrospectively when they land21:23
tr3buchetseems cleaner that way21:23
jesse_andrewspvo / ozone folks - how risky is multi-nic landing?21:24
ttxjesse_andrews: I'll give that a thought. They were originally targeted by Vish, will talk to him21:24
pvojesse_andrews: I know the tests are being cleaned up now.21:24
jesse_andrewspvo: nice :)21:24
tr3buchetjesse_andrews: as to multi-nic it depends on review respoonse21:24
ttx#action ttx to consider untargeting/retrotarget Low specs to decrease noise21:25
ttxalso, congrats to nova-core for decreasing the review queue to 12 open reviews21:26
ttxanything else on Nova ?21:26
ttxah! down to 10 now.21:26
annegentlewow, nice job team21:27
tr3buchetwhich means i surely need to merge trunk again21:27
tr3buchet;)21:27
devcamcarhah, yea21:27
jaypipeshehe21:27
ttx#topic Doc status21:27
*** openstack changes topic to "Doc status"21:27
ttxannegentle: floor is yours.21:27
annegentleThanks. We held our first doc/web meeting last night, and went through goals for the meeting and team.21:27
annegentleI have a fresh perspective on and respect for the talents inherent in running meetings on IRC. :)21:27
annegentleA couple of items of interest to the larger team:21:27
ttxheh21:27
annegentletoddmorey is working on tracking website bugs and issues through Launchpad, so we'll create an openstack-website project so you can log bugs against http://openstack.org. ttx, Todd'll probably get in touch with you for assistance if needed.21:28
johnpurannegentle: no doubt you are awesome!21:28
annegentletoddmorey has also implemented the site in Silverstripe which should enable more contributors21:28
ttxannegentle: coolio21:28
annegentleThe http://docs.openstack.org site now includes selected blog entries from kpepple, thanks to Ken releasing those with Creative Commons licensing.21:28
*** agarwalla has joined #openstack-meeting21:29
annegentleIt's an experiment in collaborative docs where I'm contacting authors with CC-licensed content to see if they want to put their content on http://docs.openstack.org.21:29
annegentleThe next set of CC-licensed contributions are from CSS Corp Open Source Services, hoping to get those in next week.21:29
annegentleLastly, doc builds are now happening automatically when merge props are reviewed/accepted.21:30
jkoelkerinetrY6o21:30
annegentleI'll probably move the time to North America daytime, but we'll continue to meet monthly.21:30
ttxannegentle: ok21:31
annegentleAny doc/website questions?21:31
bcwaldonjkoelker: it showed up as all *'s to me21:31
tr3buchet:)21:31
jkoelkerrigggghhht21:31
jkoelkerfocus follows mouse is bad21:31
Veknow there's a religious war!21:31
* tr3buchet puts on his wizard hat and robe21:32
ttxannegentle: apparently not. Thanks for that update21:32
ttx#topic Open discussion21:32
*** openstack changes topic to "Open discussion"21:32
johnpurjkoelker: lol, no-one can access all your bank accounts now!21:32
spectorclan_Design Summit (looking like Oct 3-5) & Conference (looking like Oct 6-7) ; both events (marketed separately at Boston Sheraton Hotel next to Hynes Convention Center. Contracts not signed but in review21:32
ttxjohnpur: especially since he uses SecurID21:32
johnpurspectorclan: how firm is this location?21:33
carlpquick question: is that 1900UTC meeting on Tuesdays for the larger distributed automated testing environment using jenkins?21:33
ttxspectorclan: oh, that's very new21:33
spectorclan_Pretty firm - not many places available and this is a popular spot; hotel was just redone and great location21:33
Vekand right on the green line21:34
notmynamedevcamcar: jesse_andrews: https://github.com/rackspace/keystone/blob/master/docs/swift-quick-start.txt21:34
* ttx looks it up21:34
notmynamesee the bottom of that page for keystone/swift integration notes21:34
johnpurspectorclan: can we open the floor to suggestions about 'e' names for the next release?21:34
edayspectorclan_: are those dates+boston firm for sure? (even if hotel changes)21:34
jesse_andrewsnotmyname: NICE21:34
spectorclan_Yes, dates are firm21:34
notmynamejesse_andrews: all gholt :-)21:34
spectorclan_ttx: those are the dates you gave me, correct?21:35
jesse_andrewsgo gholt, it is your birthday!21:35
* ttx doublechecks21:35
devcamcarnotmyname, gholt: word21:35
ttxspectorclan: yes!21:35
*** medberry is now known as med_out21:36
ttxjohnpur: let's keep that for the next meeting21:36
spectorclan_Any questions on the CLA process I started today?21:36
ttxthough suggestions are ok :)21:36
johnpurttx: ok, i am just excited about what the next name will be!21:37
notmynamettx: johnpur: https://secure.wikimedia.org/wikipedia/en/wiki/List_of_cities_in_Texas#E21:37
*** AlexNeef has joined #openstack-meeting21:37
edayhttp://massachusetts.hometownlocator.com/cities/listcitiesalpha,alpha,e.cfm  if we want a 'E' name near boston :)21:37
creihtEvil21:37
johnpurspectorclan: the cla process looks good to me.21:37
spectorclan_ttx: I thought E comes from Massachusetts and not Texas?21:37
ttxnotmyname: we need to pik somewhere in MA, preferably in Boston area21:37
carlpAll I can think of is Easton21:38
Vekeverett?  (doubt I have the right spelling)21:38
johnpuri bet we have a lot of folks in the NE that can help with naming!21:38
jesse_andrewsEdgeworth21:38
spectorclan_Essex21:38
Vekthere's one I never heard of.21:38
*** ramd has joined #openstack-meeting21:38
johnpurprimeministerp: around?21:39
spectorclan_There is a Mount Everett21:39
pvoheh. Egypt.21:39
ttx"Everett"21:39
*** SumitNaiksatam has joined #openstack-meeting21:39
spectorclan_Eagle Hill River21:40
creihtof course if we use the Texas form of the word close, you could include several states in the search :)21:40
ttxspectorclan: multiple words are not ok21:40
Vekhaha :)21:40
alandmanjohnpur: primeminsterp's not around21:40
johnpurttx: as a Seattle native... Everett is west coast21:40
ttxjohnpur: http://en.wikipedia.org/wiki/Everett,_Massachusetts21:40
ttxnot that one ^21:40
ttxCan be a city or a county21:41
ttxsee http://wiki.openstack.org/ReleaseNaming21:41
johnpuralandman: have opinion on 'e' names close to Boston?21:41
ttxMA is small, that won't leave so many options21:41
spectorclan_Essex is the only county21:41
ttxspectorclan: yep21:42
notmynameEliot is a Boston suburb21:42
ttxthat could work.21:43
alandmannotmyname: Where is Eliot21:43
creihtThere is an Eden, Vermont21:43
notmynamealandman: http://massachusetts.hometownlocator.com/ma/middlesex/eliot.cfm21:43
notmynamecreiht: and eden texas :-)21:43
creihtindeed21:43
Vekhmmm...21:44
tr3buchetEdinburgh, UK21:44
alandmannotmyname: Noone I know that lives here would ever use that name for that area21:44
VekEastham, Easthampton, Easton, Edgartown, Egremont, Erving, Essex, and Everett are all the single-word E names for Massachusetts.21:44
notmynamealandman: "suburb of Boston"? just looks close on the map to me21:44
Vek(municipality names)21:45
alandmannotmyname: People would call that area Netwon, from the town21:45
ttxfeel free to edit the wiki with your preferred candidates21:45
Vekthere used to be an Enfield, MA...21:45
ttx#endmeeting21:45
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"21:45
openstackMeeting ended Tue Jun  7 21:45:50 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-06-07-21.03.html21:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-06-07-21.03.txt21:45
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-06-07-21.03.log.html21:45
*** spectorclan_ has left #openstack-meeting21:46
*** jk0 has left #openstack-meeting21:46
Vekhttp://en.wikipedia.org/wiki/List_of_municipalities_in_Massachusetts21:46
*** mgius has left #openstack-meeting21:46
*** jesse_andrews has quit IRC21:47
VekEast Boston has the nickname "Eastie"21:48
soren"East Boston" sounds great.21:48
Vektwo words, though.21:48
sorenEastBoston.21:48
sorenWin.21:48
ttxsoren: East%20Boston doesn't, though.21:48
Vekheh :)21:49
*** salv-orlando has joined #openstack-meeting21:51
carlpThere are a lot of "East %" locations in MA21:51
*** midodan has joined #openstack-meeting21:51
*** bcwaldon has left #openstack-meeting21:52
*** masumotok has quit IRC21:53
*** dendrobates is now known as dendro-afk21:55
*** dendro-afk is now known as dendrobates21:55
*** eperdomo has joined #openstack-meeting21:55
*** ewanmellor has quit IRC21:56
*** johnpur has quit IRC21:56
*** Vek has left #openstack-meeting21:56
*** alekibango has joined #openstack-meeting21:59
*** rnirmal has quit IRC21:59
dendrobateso/22:00
danwenthello22:00
markvoelkero/22:00
danwentlook, real internet connectivity :)22:00
AlexNeefhi22:00
somikhello all22:01
danwentFYI: brad from nicira is afk right now22:01
dendrobateslets wait a few minutes for people to show up22:02
danwentsure, much quieter than usual today.22:02
salv-orlandoHi everybody!22:02
midodanhi guys22:02
AWRhay!!22:02
*** romain_lenglet has joined #openstack-meeting22:03
alekibangohello :)22:03
salv-orlandoI see a few new names today (or just the usual ones with different nicks)...22:03
AWRhow is everyone?22:03
danwentgreat :)22:03
AlexNeefgood22:03
SumitNaiksatamhello22:04
carlpnot too bad22:04
danwentsalv: agreed.  if you're new, care to introduce yourself?22:04
AWRill start22:04
dendrobatesor if you changed your nick, tell us who you are?22:04
AWRhi im AWR ;)22:04
danwent:)22:04
AWRim semi new to openstack22:05
AWRworking on setting up now22:05
AWRand figured i woudl see what the team meetings were like22:05
danwentah, great.  We're the "NetStack" team, focused on networking for openstack.22:06
*** mattray has quit IRC22:06
danwentstill in its very early stages, not an official project yet.22:06
dendrobatesAWR: the main openstack meeting just ended22:06
dendrobatesbut this one is more exciting anyway22:07
byeagerI am not new, but I haven't been around much lately, trying to get plugged back in...22:07
dendrobateshey blake22:07
dendrobateswelcome back22:07
danwenthi blake22:07
byeagerthanks rick, good to be back around22:07
dendrobatesshall we start?22:08
AWRt dendrobates: i know, i was silent through it since i really didnt have anything to ad22:08
carlpsure!22:08
danwenti say we're good to go22:08
dendrobates#startmeeting22:08
openstackMeeting started Tue Jun  7 22:08:31 2011 UTC.  The chair is dendrobates. Information about MeetBot at http://wiki.debian.org/MeetBot.22:08
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.22:08
dendrobates#topic project update22:08
*** openstack changes topic to "project update"22:08
dendrobatesI believe some code has been pushed by Rackspace22:09
dendrobatesIs anyone here to talk about it?22:09
*** jakedahn has joined #openstack-meeting22:09
danwentto what project?22:09
danwentis this the quantum extensions stuff?22:09
dendrobatesdanwent: the quantum stuff22:09
dendrobatesyes22:09
somikI just saw a merge proposal for extensions22:09
danwentOk, was going to bring that up in the quantum section.22:09
danwentor perhaps we're there already :) ?22:09
dendrobatessure, go ahead22:10
danwentcool22:10
danwentstill need to update all blueprints, but a basic experimental version of quantum is ready to be poked at:  https://code.launchpad.net/~netstack/network-service/quantum22:10
danwentthis does not include the extensions.22:10
danwentincludes functioning API, data model, sample plugins, and CLI.  OVS plugin can be run end-to-end on XenServer.  If you just want to run API, data model, and play with CLI, you can just install the service standalone.22:10
danwentplease see the README22:10
danwentno packaging for now.22:10
danwentno tenant auth.  no GUI22:11
danwentanyone who would like to see such things, let me know ;)22:11
salv-orlandodo we have any form of integration with nova? or a tweaked version of nova?22:11
danwentRunning with OVS plugin doesn't require a tweaked version of nova, standalone nova will work.22:11
danwentI think the README for the OVS plugin describes that.22:11
salv-orlandogood22:12
danwentworking with libvirt will require some tweaks.22:12
carlpCan the OVS plugin be run on KVM?22:12
danwentto nova, we'll probably post a nova branch to do that soon.22:12
carlpdanwent: can we talk about that later?22:12
danwentcarlp: sure22:12
carlpdanwent: I'm interested to see what I can help contribute22:12
*** edconzel has quit IRC22:12
danwentcarlp: basic point is that you need to generate the libvirt XML a little differently.22:12
danwentcarlp: sounds good.22:12
dendrobatescarlp: Cisco is interested in libvirt/kvm support as well22:13
danwentWhat dendrobates was mentioning is that there was a recent merge request from santhosh: https://code.launchpad.net/~santhom/network-service/quantum_framework/+merge/6371122:13
danwentthis arrived this morning.  I don't now if anyone has had time to take a look yet (we haven't).22:13
dendrobatesis troytoman around?22:13
salv-orlandoI had a quick look at that22:13
carlpdendrobates: good to know22:13
danwentit apparently includes code from nova on extensions, plus some unit test improvements, plus some pep8 fixes.22:14
dendrobatesI looked at it, and am gettng a few other cisco devs on it.22:14
danwentI suspect most of the interest will be with respect to the exstensions.22:14
danwentdendrobates: great.22:14
salv-orlandoyeah the extension model allows for defining new resources, new methods and new methods on existing resources22:14
danwentif the extension stuff is contentious, we'll probably try to split it out from the unit test + pep8 stuff.22:14
danwentas that seems pretty vanilla.22:15
dendrobatesdanwent: that is a good idea22:15
danwentI know other people had registered interest in how extensions work, so I want to make sure there's time for review.22:15
danwentis santhosh around?22:15
dendrobateshello rackspace?22:16
danwentok, i'll assume not, troy or any other rackers?22:16
dendrobateswe will have to follow up with them in email.22:16
danwentagreed.22:16
yingdanwent: yes, I'm interested. Just briefly looked it today and will follup with emails22:16
danwentying: I figured :)  sounds good.22:17
danwentin other news, I'm drafting a "what is quantum" doc based on http://www.slideshare.net/danwent/quantum-diablo-summary .  Goal is to get across key points to new people joining the project who were not at the Diablo summit.22:17
danwentplan to have something by end of this week.22:17
*** creiht has left #openstack-meeting22:18
danwentOverall, quantum should be in a place were other people can start playing with it.22:18
danwentthings like donabe or other services should be able to start developing against it.22:18
dendrobatesgreat22:18
salv-orlandodanwent: the doc would be great. let me know if you want help preparing/reviewing it22:18
danwentwe still need more effort around system test, docs, etc.22:18
danwentsalv: yes, definitely, everyone should collaborate on it.  agreed.22:19
salv-orlandoand since we had the first merge proposal I would like to set aside some time to discuss the review process.22:19
*** alandman has quit IRC22:19
dendrobatessalv-orlando: sure, Dan are you done?  We could do it now.22:19
salv-orlando* current trunk has pep8 errors...22:20
danwentsalv:  Yes, agreed.22:20
dendrobates#topic Netstack review process22:20
*** openstack changes topic to "Netstack review process"22:20
danwentsalv: on pep8: yes, santhosh fixed some of those in his branch, so we did not want to introduce merge conflicts by fixing them.  I'd rather have him split it out from the extension stuff and merge that.22:20
danwentdendrobates: yes, done :)22:21
dendrobatesIs there any reason that we should not follow the openstack core processes?22:21
danwentI think this just comes down to defining the "core" devs.22:21
salv-orlandonot from me. I think we just need to define the "netstack-core" now22:21
danwentbut i don't see a reason to diverge from opestack common practice.22:22
dendrobatesI recieved emails from only 2 people about core dev status22:22
dendrobatesWhy don't I draft a core-team list and we can review it at the next meeting22:22
dendrobatesbefore I create it22:23
salv-orlandodendrobates: agreed22:23
danwentI'm fine with that.22:23
dendrobatesif anyone wants to be sure to be on it, please send me an email22:23
salv-orlandoIs there a "python reviews for dummies" manual available somewhere :-)22:24
salv-orlando?22:24
somiksure.. we havesome code and as people start creating patches and submitting merge proposals we can expand the core.22:24
danwentdendorbates: as part of that, can you put together pointers to the materials used by nova (style guides, etc?)22:24
troytomansorry guys ... i'm a bit late ... firefighting day for me!22:24
dendrobatesIt is just one line.  " be fascist about pep8"22:24
danwent:)22:24
dendrobatesdanwent: yes I can22:24
alekibangodendrobates: fascism = merge of corporations + government.. we maybe should use the word as it deserve22:25
dendrobatesone place tha tnova has fallen down, IMHO , is with naming standards.  I suggest we take a stab at that too22:25
danwentdendrobates: in what sense?22:25
danwentvariables?22:25
dendrobatesdanwent: yes22:26
danwentk22:26
dendrobatesthe goal is ease of understanding and a quick path to contribution22:26
danwentok, open discuss?22:27
dendrobates#topic open discussion22:27
*** openstack changes topic to "open discussion"22:27
salv-orlandosince troy is here now, we can probably have an update on melange22:28
dendrobatesthe dmtf has some standards for defining  network parameters that is being included with OVF 2.022:28
troytomansure. We have been cleaning up our first pass and looking at integration options. we hope to have something we can merge into Nova in the next couple of weeks.22:29
dendrobatesIf they are good, I suggest we standardize on them22:29
danwentdendrobates: is there a link available yet?  I'm unfamiliar with this.22:29
troytomanOtherwise, we are waiting for multi-nic and network refactoring to figure out how to integrate melange into Nova22:29
dendrobatesdanwent: It might still be in the working group22:30
somikI think OVF 2.0 is still under discussion22:30
danwentdendrobates: should we consider trying to be part of the discussion?22:30
dendrobatesdanwent: I think it is too late, but we should at least look at it and comment22:31
danwentk22:31
salv-orlandotroytoman: I was looking at the IPAM protocol proposal on github.22:31
carlptroytoman: Let me know when/if you would like us to look that over too22:31
Tvsalv-orlando: url please?22:31
salv-orlandoDoes this protocol replaces normal DHCP discovery/request/offer process?22:31
salv-orlandotv: I think is this: https://github.com/tv42/melange-discovery/blob/master/melange-discovery.rst22:33
troytomanslv-orlando: the github proposal on the protocol is being done by tv22:33
salv-orlandosorry I'm not at my work laptop22:33
troytomanmy team has been focused on the address tracking part22:33
Tvok just wanted to know if that's what you're talking about22:33
salv-orlandotroytoman: I see. Apologies for misunderstanding...22:33
Tvsalv-orlando: that is intended to look like dhcp to the vm22:33
troytomancarlp: when we have the integration proposal together, I'll send it out more broadly. probably before end of the week22:33
carlptroytoman: cool, thanks22:33
Tvsalv-orlando: while delegating all the decision making to the melange ipam22:34
salv-orlandotv: that means, for instance, VM sends DHCP request, and it is then translated into Melange IPAM message?22:35
Tvsalv-orlando: roughly, yes22:35
danwentone concern I had with the proposal is that it would seem to prevent a VM on a private network from running its own DHCP servers, is that true?22:35
Tvdanwent: private networks are basically L2 without IPAM services, so no22:35
danwentthough it seems like one valid approach if you did not care about that use case.22:35
Tvdanwent: i'd expect those interfaces are not subject to this processing at all22:35
Tvdanwent: my thinking is, it's the customer's L2, they run DHCP if they want etc, *nothing* should touch the packets22:36
danwentOK, so this would be enabled only for certain interfaces.22:36
Tvdanwent: including the host firewall22:36
danwentOk, that seems reasonable :)22:36
Tvdanwent: more like, your VPC L2 networks are separate vifs22:36
Tv(want to run non-IP in your private L2? go right ahead!)22:37
Tvi guess the spec could talk of VPCs22:37
salv-orlandotv: but I can still run melange ipam on my L2 network if I don't want to have my DHCP or some non-ip network... is that correct?22:38
Tvsalv-orlando: i haven't considered that use case22:38
Tvsalv-orlando: that would be.. "interesting" for the ipam component, i guess22:38
Tvsalv-orlando: like, completely different from its primary purpose of managing the outside-visible addresses22:39
Tvsalv-orlando: i'd rather ignore that for now, say that you manage the LAN as you wish22:39
danwentYeah, I think you basically need to be able to enable it or disable it for certain interfaces.  I'm not sure nova will have a notion of what is "private" vs. "public".22:39
salv-orlandotv: agreed.22:39
danwentso is IPAM only about managing public IPs?22:39
Tvdanwent: i think of VPCs as something the cloud provider should not touch, at all22:40
Tvthere may be other opinions on that22:40
danwentTv: sure.  don't want to derail the who meeting on this.  we can move this offline :)22:40
Tvdanwent: but i wouldn't say IPAM is only about "public" IPs.. as in, it would be useful for managing 10.x.x.x too22:40
Tvdanwent: yes22:40
danwentTv: agreed.22:40
salv-orlandoI think as a consumer of cloud services I might enjoy a service provided by the CSP to manage IPs in my own network...22:41
Tvsalv-orlando: sure, i'm just inclined to postpone that; the code should be reusable, but i'd rather focus on one thing at a time22:41
salv-orlandotv: I agree with you. I don't want to push this :-)22:41
troytomansalv-orlando: not in scope for the initial release. but, it could evolve that way22:42
Tvand that brings harder concepts like realms (whose 10.x.x.x are you talking about) etc22:42
troytomanalso, we are setting it up to be able to track both private and public IPs. Also, track NAT relationships between the two22:42
Tvit'd be nice to find out that that wasn't ultimately needed at all ;)22:42
danwentok, any other open discussion?22:44
dendrobatesnot from me22:44
salv-orlandoA couple of bits on Quantum API:22:44
Tvi have a question about quantum22:44
* Tv waits for salv-orlando22:44
salv-orlandogo ahead tv22:44
danwentTv: shoot22:44
Tvhah!22:44
Tvok so.. vlans?22:44
salv-orlandoI registered a blueprint today22:45
Tvwill quantum have other means of identifying networks on the physical network that connects the hypervisor hosts than vlans?22:45
danwentTv: definitely.22:45
Tvdanwent: i'd be interested in more detail22:45
danwentTv:  plugins should be able to use any type of mechanism for L2 segmentation.22:45
danwentTv: openvswitch for example can do cool things with L2-in-L3 tunneling.22:45
danwentTv: happy to talk more about this, but don't want to commandeer the meeting.22:46
Tvi see just one openvswitch plugin that seems to have vlans pretty tied into the core of it22:46
ramdsalv: Are you planning the "VLAN manager port" as default-plugin?22:46
Tvdanwent: i'd very much like to know more, after the meeting22:46
danwentTv: yes, for the experimental plugin we just wanted to get something out the door, vlans are by far the easiest thing.22:46
salv-orlandoramd: no I was just thinking it would be good to have it22:46
danwentTv: shoot me an email and we can chat.22:48
ramdsure. I agree with dan; for quantum api level physical segmentation scheme could be anything22:48
ramdfor starters it happens to be vlan22:48
danwentthat was the whole goal of having it be a logical API.22:48
danwentany technology could be behind it.22:48
salv-orlandoI have registered a blueprint for a porting to quantum of the 'traditional' nova's vlan manager over linux bridge.22:48
salv-orlandoI thought it would be good to have it as well.22:49
ramdsalv: +122:49
ramdIn the design summit we also talked about retaining current network-manager as well22:50
dendrobatesanything else?22:50
Tvdanwent: my only concern is seeing "openvswitch" plugin be vlan.. should that be "openvswitch-vlan", or should it have plugins below it, or what?22:50
danwentTv: my guess is that we will make the openvswitch plugin be able to handle both vlans and other segmentation mechanisms22:51
danwentTv: that is, config options rather than separate plugins.22:51
dendrobatesTv: do you mean should openvswitch own the vlan namespace?22:52
Tvdendrobates: i don't mean it should; i mean that what it looks like now22:52
danwentTv: you'll need some plugin logic that decide who owns vlans.22:52
dendrobatesbut that multiple plugins could perform that function22:53
Tvdanwent: ok so code in the most essential alternative implementations, that'll work22:53
somikdendrobates: correct22:53
Tvdendrobates: no you're thinking this kinda the other way22:53
Tvdendrobates: i want to have openvswitch-but-not-vlan22:53
dendrobatesah22:53
danwentTv: people can definitely write other plugins that use openvswitch as well.22:53
*** jkoelker has quit IRC22:53
danwentor they can extend the openvswitch plugin, whichever makes sense.22:54
danwentSome people have already contacted us about building a plugin that extends the OVS plugin as a python class.22:54
danwentyou can also introduce new things into the data model, etc.  code sharing is a beautiful thing :)22:55
Tvdanwent: hence my question on whether there's code there that should be shared across openvswitch-vlan and openvswitch-tunnel, and your answer of just putting the two implementations in the same plugin22:55
danwentTv: K.  I think either approach would work.  Happy to chat more with you.22:55
Tvbut yeah, good to hear that the non-vlan case is still in general awareness22:55
danwentTv: k22:56
dendrobatesI have another question, but it can wait until next time22:56
danwentwow, 4pm already :)22:57
salv-orlandoI too have a question on Quantum API but will send an email22:57
dendrobates6pm for some and later for others22:57
danwenthaha :)22:57
markvoelker7 for us east coasters =)22:57
salv-orlandomake it midnight for me :-)22:57
dendrobates#endmeeting22:57
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"22:57
danwentok, i get it :)22:57
openstackMeeting ended Tue Jun  7 22:57:45 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-06-07-22.08.html22:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-06-07-22.08.txt22:57
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-06-07-22.08.log.html22:57
ramdquit22:57
*** ramd has quit IRC22:58
somikhave a good one everybody!22:58
salv-orlandobye, talk to you next tuesday!22:58
dendrobatesbye22:58
*** AlexNeef has quit IRC22:58
*** markvoelker has quit IRC22:58
danwentsee you all!22:58
*** salv-orlando has left #openstack-meeting22:58
*** ramd_ has joined #openstack-meeting22:58
*** SumitNaiksatam has quit IRC22:58
*** ying has quit IRC22:58
*** ramd_ has quit IRC22:58
carlpdanwent: still there?22:58
danwentbtw, carlp, I think you wanted to follow-up as well.  send me email if you like.22:58
danwenthaha :)22:58
carlpOK, I think I have your address somewhere....22:58
carlpyes, yes I do :)22:59
danwentdan@nicira.com22:59
danwentI've actually got to run to another meeting.  Is it OK to talk later?22:59
*** danwent has left #openstack-meeting23:00
carlpyeah, no problem23:00
*** agarwalla has quit IRC23:00
*** antonyy has quit IRC23:07
*** troytoman is now known as troytoman-away23:13
*** toddmorey has joined #openstack-meeting23:15
*** dendrobates is now known as dendro-afk23:15
*** toddmorey has quit IRC23:19
*** dragondm has quit IRC23:22
*** toddmorey has joined #openstack-meeting23:25
*** dwcramer has joined #openstack-meeting23:37
*** somik has quit IRC23:41
*** Tushar has quit IRC23:42
*** ohnoimdead has quit IRC23:49
*** Tv has left #openstack-meeting23:57

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